CUDA RUNTIME ERROR

Hi,
Thanks for updating the multi-GPU instructions. I am wondering since there is no CUDA toolkit installed during the default installation, do I need to install this aside from the bio-transformers main packages? Also, when I try to run with multi-GPUs, I get this error
RTX A6000 with CUDA capability sm_86 is not compatible with the current PyTorch installation.
The current PyTorch install supports CUDA capabilities sm_37 sm_50 sm_60 sm_70.
If you want to use the RTX A6000 GPU with PyTorch, please check the instructions at https://pytorch.org/get-started/locally/

Hi, you still have this configuration?
Conda torch 1.8.1
NVIDIA-SMI Driver Version: 460.67 CUDA Version: 11.2
Conda cudatoolkit 11.0.221

Yes, I found this seems to be a problem with A600 GPUs only. Others are fine. Thank you for your help.


python312Packages.dnfile: 0.15.0 -> 0.15.1

Diff: https://github.com/malwarefrank/dnfile/compare/refs/tags/v0.15.0...v0.15.1
Changelog: https://github.com/malwarefrank/dnfile/blob/v0.15.1/HISTORY.rst

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

x86_64-linux

:white_check_mark: 18 packages built:

everest-mons
everest-mons.dist
python311Packages.dnfile
python311Packages.dnfile.dist
python311Packages.karton-autoit-ripper
python311Packages.karton-autoit-ripper.dist
python311Packages.karton-config-extractor
python311Packages.karton-config-extractor.dist
python311Packages.malduck
python311Packages.malduck.dist
python312Packages.dnfile
python312Packages.dnfile.dist
python312Packages.karton-autoit-ripper
python312Packages.karton-autoit-ripper.dist
python312Packages.karton-config-extractor
python312Packages.karton-config-extractor.dist
python312Packages.malduck
python312Packages.malduck.dist


Display available keyboard shortcuts in flyouts

Fixes #1492

Can you check if this causes the event to be fired twice?

@tsvietOK This issue occurs on master as well.
More precise steps to reproduce:

Switch to grid view
Select an item
Press F2 to rename
Rename the item
Switch to tiles view
Rename the same item again by selecting it and pressing F2
Switch back to grid view
Select the same item
Press F2 to rename
See error

Can't reproduce your issue.

@tsvietOK If you referred to a dialog box popping up saying that you can't have 2 files with the same name, this appears in master as well.

No, i can't reproduce your issue at all. I am able to rename files without any problem on master branch.

Issue i mentioned before still exists with your changes.

@tsvietOK And I can't reproduce any issue you have.

@tsvietOK This commit might fix your issue (at least it fixes mine)

Issue reported by me still present.

I still have no crash. How should we continue since I can't reproduce your crash after renaming a file?

That is because of double event call.

Hey, how are you? I a new at this whole coding business. . . But was wondering, is there a way to set "Files - preview" as the default file explorer? And how can I change the icon, as I was able to do it with all my other apps by using properties but it doesn't seem to work with yours. . . Thanks so much and keep it up!

Hey, how are you? I a new at this whole coding business. . . But was wondering, is there a way to set "Files - preview" as the default file explorer? And how can I change the icon, as I was able to do it with all my other apps by using properties but it doesn't seem to work with yours. . . Thanks so much and keep it up!

@coheneli98 Please don't ask questions like this in PRs. File an issue or use Discord instead!

Can't delete file.
Steps:

Open GridView mode
Select file
Press Delete button
Crash

Now Delete button is not working in ListView mode/

@tsvietOK I can't reproduce a bug with the delete item in context menu. A screenshot would be helpful.

I am talking about Delete button on your keyboard.

When paste file it shows several copies of these files(PasteItem() called twice), but it fixes when pressing F5.

@tsvietOK Please check if there are any other issues in this PR so I can fix them all at once.

@Thomas1664 Sure

Cut item called twice.

"Copy item" called twice.


Can't stop the time tracker once it's started

Fedora34/KDE
Starting a time tracker grays out Pause/Finish/Cancel buttons, and wont allow for any change. Can still edit the task title.
Restarting the app doesn't fix the issue, and the timer is still running.

@magikmw can you please post a screenshot/video from this bug?

Here you go (youtube)

Here you go (youtube)

Thank you for the video, well, this is more an UX issue, you have to long press them. Can you please try and confirm that the long press is working? Thank you!

Ha. Well then, I haven't thought to long-click. It does indeed work.
Indeed, the UX is problematic here. Reminds me of iOS lists with hidden 'swipe-to-delete' interactions.
However, I've stumbled on another bug. Reproduction steps:

Start a timer.
Pause a timer.
Either finish or cancel a timer.
Start a new timer.
The new timer wont tick in UI. It seems that the timer is running, as evidenced by restarting the app - the timer resumes several seconds in, and the bug is purely in presentation.

I found this one too, seems as if the timer starts paused, if you "pause" it again and then long-click continue, then it works again.


Validate connection URIs

Any extra information that a ConnectionService needs (e.g. a username / password) would be passed via the Properties object.


[HOLD] MenuItem - external URLs handling

Details

Fixed Issues

$ GH_LINK
Tests

QA Steps

Tested On

[ ] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Closing as it was decided we don't need this


Nightly builds, ci/cd, nuget packages, and new MSBuild format for rocket projects

and also .sln projects fixes

The copy pastas is real


Allow beneficiaries to view outcomesets

When a beneficiary is provided a JWT it details a particular meeting the beneficiary can edit. It should also provide read access to the outcomeset associated with that meeting. This is needed for the frontend to present the meeting to the user.

 Self assessment (via link)


Partial-interactive graph

Feature request - support an option for drag&drop nodes, but prevent the user from creating new edges (connect between two nodes).
In general - I think the lib should support control for each of those:
<ReactFlow
    ...
    dragNodes={true/false}
    linkNodes={true/false}
/>

This way it's possible to control all options and mix between them.
One might want to allow all (same as what the lib supports now), but another might want to have the nodes fixed and allow creation of new edges/links, or maybe support moving around the nodes, but prevent create new connections between nodes.
Giving an option to control each of them allows much more flexibility to the lib.

If you don't implement an onConnect handler, no edges will be created. So your first request should already work.
If you want an inactive chart but be able to connect nodes that's not possible for now. Do you think this is really a use case?

No implementing the onConnect is indeed an option, however this is really frustrating to the user (because it's looks like a bug in the system - "why do I have an option to start drag a new edge, but it will never connect to anywhere).
In my case - yes, I need this. I want to give some users permissions to only view the graph without the ability to link between the nodes (and I do want them to be able to drag/drop/rearrange the graph structure).

Ah, you are right. We are still drawing the connection line even if there is no on connect handler. For this case we could introduce a new option like isConnectable. Do you also have the use case where you want to show an inactive graph where users can connect nodes?

Sure, this is also a valid option:
I want the nodes to be fixed (in place) and give the user the ability to connect them (but now allowing drag and drop of nodes).
The reason is that sometimes flows should be handled by one person (and the position of the elements explains the flow of the data in the system), and some other person have the ability to create the connection, but not changing the position of the elements.

Ok, got it. I will see how we can achieve this.

You can now use the properties nodesDraggable, nodesConnectable and elementsSelectable in order to adjust the interaction level.


trigger flow for github PR when it is opened with commits

it has opened action

added but needs veritication

works


IPV6 Issues with ha.pool.sks-keyservers.net

Have multiple people getting:
+ gpg --keyserver ha.pool.sks-keyservers.net --recv-keys 0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D
gpg: keybox '/tmp/tmp.7GlY5wPunO/pubring.kbx' created
gpg: keyserver receive failed: Cannot assign requested address

When trying to build this image
See: https://gitlab.com/meltano/meltano/merge_requests/53
See: https://github.com/nodejs/docker-node/issues/380
So we need to do something like https://gitlab.com/meltano/meltano/blob/443ea69880dc7a86f099df2ddc0a7718a7587d61/docker/vendor/python/keyservers.patch

See https://github.com/docker-library/python/pull/311 for how we combat this (both in Travis and on the official build servers).


NaN label in MultiIndex is assigned a non NaN value when writing to excel file

Given a DataFrame which has a MultiIndex. When a label of the MultiIndex has the value NaN and the DataFrame is written to an excel file, the label will have a value which is not NaN in the excel file.
Code Sample, a copy-pastable example if possible
df = pd.DataFrame({'c1': [1,1,2,2],
                   'c2': [None] + "b a b".split()})
df

returns a DataFrame where the first element of column 'c2' is NaN:
	c1	c2
0	1
1	1	b
2	2	a
3	2	b

Set both columns as the index:
df_midx = df.set_index(['c1', 'c2'])
df_midx

returns
c1	c2
1
1	b
2	a
2	b

Write DataFrame to excel file and read it back in:
df_midx.to_excel('df_midx.xlsx')
df_midx_from_xlsx = pd.read_excel('df_midx.xlsx')
df_midx_from_xlsx

returns
	c1	c2
0	1.0	b
1		b
2	2.0	a
3		b

The first element of column 'c2' is now set to 'b' instead of NaN.

Interested in trying to look for a fix?

this is prob a duplicate of #6322 or #5286

I think the bug is in the method pandas.formats.format.ExcelFormatter._format_hierarchical_rows() which is called by the public method pandas.formats.format.ExcelFormatter.get_formatted_cells(). More precisely the problem is the statement
values = levels.take(labels)

(here) where each of levels and labels correspond to the same level in a MultiIndex. levels contains the possible labels for that level (e.g. ['bar', 'foo']) and labels contains indices (e.g. [0,0,0,1,1,1,1]) which point to elements in levels. If a label is null, it is represented by -1 in labels (e.g. [0,0,-1,1,1,1], if the label of the third row is null). The problem in the above statement is that it doesn't treat the index -1 as a special value.
To fix the bug, the above statement could be replaced by
if levels._can_hold_na:
    values = levels.take(labels, fill_value=True)
else:
    values = levels.take(labels)

What follows is an example:
df = (pd.DataFrame({'c1': [1,1,2,2],
                    'c2': [None] + "b c d".split(),
                    'v' : [6,7,8,9]})
        .set_index(['c1', 'c2']))

df

yields
c1	c2	v
1		6
1	b	7
2	c	8
2	d	9

df.index

yields
MultiIndex(levels=[[1, 2], [u'b', u'c', u'd']],
           labels=[[0, 0, 1, 1], [-1, 0, 1, 2]],
           names=[u'c1', u'c2'])

for levels, labels in zip(df.index.levels, df.index.labels):
    print levels.take(labels)
    print levels._can_hold_na
    if levels._can_hold_na:
        print levels.take(labels, fill_value=True)
    print levels
    print labels
    print "------"

yields
Int64Index([1, 1, 2, 2], dtype='int64', name=u'c1')
False
Int64Index([1, 2], dtype='int64', name=u'c1')
FrozenNDArray([0, 0, 1, 1], dtype='int8')
------
Index([u'd', u'b', u'c', u'd'], dtype='object', name=u'c2')
True
Index([nan, u'b', u'c', u'd'], dtype='object', name=u'c2')
Index([u'b', u'c', u'd'], dtype='object', name=u'c2')
FrozenNDArray([-1, 0, 1, 2], dtype='int8')
------

I'd like to fix that bug, but I haven't found any unit tests for pandas.formats.format.ExcelFormatter. Shall I create one in pandas.tests.formats.test_format.py? And do you have any suggestions on how to assert that the correct ExcelCells are returned by get_formatted_cells()?

That looks like a very reasonable explanation! PR very welcome.
For the tests, I don't think we have tests for ExcelFormatter directly, but tests for read_excel/to_excel are in https://github.com/pydata/pandas/blob/master/pandas/io/tests/test_excel.py. The basic tests are eg here: https://github.com/pydata/pandas/blob/master/pandas/io/tests/test_excel.py#L1311. Those typically read the written file back in to check it's correctness. That approach should be possible here as well.


Use compiler builtins instead of manually counting

This is much faster and more concise than using an entire chain of ternary operations
In swift, the current code asks if there is a more efficient std implementation to count leading zeros. Although there is not, LLVM, GCC, and MSVC have it, so let’s use it.

@xymus could you please initiate a test?

Sure, a regular smoke test should do right?
@swift-ci Please smoke test

Thank you

What is the reason behind using intrinsics here instead of marking the LLVM functions countLeadingZeroes and countTrailingZeroes as constexpr and using them directly?

What is the reason behind using intrinsics here instead of marking the LLVM functions countLeadingZeroes and countTrailingZeroes as constexpr and using them directly? I think it would be preferable to fix the code upstream if possible.

I looked at the implementations and they don’t seem to qualify for constexpr, but I will try.

@varungandhi-apple do those functions qualify for constexpr or will they have to be refactored?

I think you should try it; since most of the operations are just bit operations and looping, I think it ought to work (although, I don't know what the status of different compilers is wrt constexpr support, I just tried Clang). Here's the patch I tried and it seems like it compiled fine.
diff --git a/llvm/include/llvm/Support/MathExtras.h b/llvm/include/llvm/Support/MathExtras.h
index 16da3046c8ce..e04f78a12628 100644
--- a/llvm/include/llvm/Support/MathExtras.h
+++ b/llvm/include/llvm/Support/MathExtras.h
@@ -91,3 +91,3 @@ namespace detail {
 template <typename T, std::size_t SizeOfT> struct TrailingZerosCounter {
-  static unsigned count(T Val, ZeroBehavior) {
+  static constexpr unsigned count(T Val, ZeroBehavior) {
     if (!Val)
@@ -115,3 +115,3 @@ template <typename T, std::size_t SizeOfT> struct TrailingZerosCounter {
 template <typename T> struct TrailingZerosCounter<T, 4> {
-  static unsigned count(T Val, ZeroBehavior ZB) {
+  static constexpr unsigned count(T Val, ZeroBehavior ZB) {
     if (ZB != ZB_Undefined && Val == 0)
@@ -131,3 +131,3 @@ template <typename T> struct TrailingZerosCounter<T, 4> {
 template <typename T> struct TrailingZerosCounter<T, 8> {
-  static unsigned count(T Val, ZeroBehavior ZB) {
+  static constexpr unsigned count(T Val, ZeroBehavior ZB) {
     if (ZB != ZB_Undefined && Val == 0)
@@ -156,3 +156,3 @@ template <typename T> struct TrailingZerosCounter<T, 8> {
 template <typename T>
-unsigned countTrailingZeros(T Val, ZeroBehavior ZB = ZB_Width) {
+constexpr unsigned countTrailingZeros(T Val, ZeroBehavior ZB = ZB_Width) {
   static_assert(std::numeric_limits<T>::is_integer &&
@@ -165,3 +165,3 @@ namespace detail {
 template <typename T, std::size_t SizeOfT> struct LeadingZerosCounter {
-  static unsigned count(T Val, ZeroBehavior) {
+  static constexpr unsigned count(T Val, ZeroBehavior) {
     if (!Val)
@@ -184,3 +184,3 @@ template <typename T, std::size_t SizeOfT> struct LeadingZerosCounter {
 template <typename T> struct LeadingZerosCounter<T, 4> {
-  static unsigned count(T Val, ZeroBehavior ZB) {
+  static constexpr unsigned count(T Val, ZeroBehavior ZB) {
     if (ZB != ZB_Undefined && Val == 0)
@@ -200,3 +200,3 @@ template <typename T> struct LeadingZerosCounter<T, 4> {
 template <typename T> struct LeadingZerosCounter<T, 8> {
-  static unsigned count(T Val, ZeroBehavior ZB) {
+  static constexpr unsigned count(T Val, ZeroBehavior ZB) {
     if (ZB != ZB_Undefined && Val == 0)
@@ -225,3 +225,3 @@ template <typename T> struct LeadingZerosCounter<T, 8> {
 template <typename T>
-unsigned countLeadingZeros(T Val, ZeroBehavior ZB = ZB_Width) {
+constexpr unsigned countLeadingZeros(T Val, ZeroBehavior ZB = ZB_Width) {
   static_assert(std::numeric_limits<T>::is_integer &&

Looking at the other functions there, it seems like more could be marked constexpr.

Every attempt I have tried to do upstream doesn't work with Windows because of the BitScanForward not being constexpr

https://reviews.llvm.org/D107240 Upstream

Thanks for trying. It's unfortunate that MSVC doesn't offer a constexpr way to do this. However, I noticed that __lzcnt/__lzcnt64 (the latter is used in this patch) also cannot be used in constexpr. https://godbolt.org/z/x86YE317v
That makes it seem like this Swift patch also won't work on Windows where IIUC we are compiling with MSVC.
Is that a fair assessment/Am I misunderstanding something? We can try testing this patch on Windows.
@swift-ci test Windows

Doesn't work. unfortunately windows is the culprit, so there is no way to continuing.

I mean there is a way, but it would involve C++20, so that is a no-go for now.


Missing Post Data when rehasing mod versions.

Hey there,
I'm here to report a (quite annoying) bug i found after updating solder to the latest version:
As the title says, when rehashing any mod versions i get a red message that reads:
"Error: Missing Post Data".
Thanks,

This is fixed in the dev branch. Issue usually tends to be a CloudFlare redirect.

Oh. I'll probably use the dev branch, then. Thanks a lot!

Did you ever get this figured out?

Did you ever get this figured out?

To point out the obvious - did you in fact read the previous comments?  Like for example @GenPage comment being and I quote;

This is fixed in the dev branch. Issue usually tends to be a CloudFlare redirect.

Yes I read the post. The question I have comes from the fact that using version <IP_ADDRESS> (the stable release) on the server that I actually host my modpack from works fine. I setup a test server for something else, setup solder with the same version and ran into this issue. I installed the dev-master branch to a clean instance to test and see if this was any different, it was not. Same issue arose. The reason I ask is that this issue was closed by mysterio in October, according to Git and packgist there have not been any changes to any branch since the beginning of September.
So if this is fixed in a dev branch, is there a different way to get it than the way that is listed in the solder documentation? Or is there a different source somewhere?
If there is no alternative repo anywhere, how did misterio get around this?


[BUG] deep_equals fails on sklearn RandomForestRegressor unfitted instances

See https://github.com/sktime/sktime/issues/6048:
deep_equals now fails on sklearn RandomForestRegressor unfitted instances, or more generall on objects that have __len__ defined but may raise an exception depending on state.
It is suprising that this happens with a common sklearn object, but it is so.
In consequence, we need to safeguard against that possibility, suggestion of a "safe length" function is discussed in the linked sktime issue.
FYI @MBristle

MRE:
from sklearn.ensemble import RandomForestRegressor
from skbase.utils.deep_equals import deep_equals

deep_equals(RandomForestRegressor(), RandomForestRegressor())


Configurable root paths for CD/CI - db/config

To better support continuous delivery the db root path 'db' must be configurable. Applies to the configuration root 'config' as well.

db path is now configurable, the system configuration files will load from config/. To share config between installations it is recommended to use symbolic links.


LDAP Auth Backend Breaks Upon Upgrading from 2.0 to 2.1

After following https://docs.stackstorm.com/install/upgrades.html to upgrade from St2 2.0 to 2.1 I found that the st2auth service would not start when the LDAP auth backend was configured.
2017-02-10 15:10:09,435<PHONE_NUMBER>22672 ERROR __init__ [-] Invalid authentication backend specified: ldap
Traceback (most recent call last):
  File "/opt/stackstorm/st2/lib/python2.7/site-packages/st2auth/backends/__init__.py", line 51, in get_backend_instance
    invoke_on_load=False)
  File "/opt/stackstorm/st2/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__
    verify_requirements=verify_requirements,
  File "/opt/stackstorm/st2/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__
    self._init_plugins(extensions)
  File "/opt/stackstorm/st2/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins
    (self.namespace, name))
RuntimeError: No 'st2auth.backends.backend' driver found, looking for 'ldap'

Doing the following fixed it.
st2ctl stop
yum remove st2-auth-ldap -y
yum install st2-auth-ldap bwc-enterprise -y
st2ctl start

Thanks for the report @jhull123. It's a definite bug, and I'm pretty sure I've tracked down the packaging problem.
The .spec file contains this:
%postun
  echo y | %{pip} uninstall st2-enterprise-auth-backend-ldap 1>/dev/null || :

The problem is that the %postun step gets run at the end of an upgrade, not just when doing an uninstall.
It needs an additional hook in there to check if it's an upgrade or uninstall, and only run that step if it's the last package getting removed. I'll submit a PR for this.
Your workaround is OK. You could also re-run the postinst script with this:
/opt/stackstorm/st2/bin/pip install --find-links /opt/stackstorm/share/wheels --no-index --quiet st2-enterprise-auth-backend-ldap

PRs have been submitted. Not sure if this will make v2.2 or not. May still need to execute manual workaround for v2.1.1 -> v2.2 upgrade. But it will definitely make whatever version comes after v2.2.

This has been resolved with 2.2. Updated packages have been published.


1.1.0-sdk33 release branch

I've opened this PR to document history for the dev.chrisbanes.paparazzi:paparazzi:1.1.0-sdk33-FOO released artifacts. This branch is based on the top-of-tree of the master branch of cashapp/paparazzi (currently commit https://github.com/cashapp/paparazzi/commit/24b11b528d0cfcedb6bd1d3c5e43176127bd1f09), with the necessary fixes to unblock teams which need to use a compileSdkVersion of 33. Primarily, that is a cherry-pick of the fix from https://github.com/cashapp/paparazzi/pull/605.
I have tested this fork on the Twitter for Android codebase, and successfully ran our Paparazzi tests using Compose UI 1.3.0-rc01 (which is requires to be built against SDK 33).
Future of this fork
To be very clear here, the artifacts that I have published below are published without any guarantees, or commitment to support. I am only publishing these to unblock teams right now. I have not modified the package name, or anything like that, to re-enforce that this is a short-term fork of the CashApp team's great work.
The work to upgrade layoutlib in Paparazzi is already tracked in https://github.com/cashapp/paparazzi/issues/604, which will mean native SDK 33 support. Once that is fixed (and released), this fork will no longer be necessary, and people can swap their dependencies back.
Any unrelated bugs should be directed to the upstream cashapp/paparazzi repository.
Artifacts
To use these artifacts, you can change your dependency to the following:
Using plugin application:
buildscript {
  repositories {
    mavenCentral()
    google()
  }
  dependencies {
    classpath 'dev.chrisbanes.paparazzi:paparazzi-gradle-plugin:1.1.0-sdk33-alpha02'
  }
}

apply plugin: 'dev.chrisbanes.paparazzi'

Using the plugins DSL:
plugins {
  id 'dev.chrisbanes.paparazzi' version '1.1.0-sdk33-alpha03'
}

https://central.sonatype.dev/artifact/dev.chrisbanes.paparazzi/paparazzi/1.1.0-sdk33-alpha03

Hi @chrisbanes, it seems that artifacts are no longer present on maven central.

Maven central doesn't allow for artifact deletion, I suspect you're looking at the wrong coordinates.
They can be found here: https://repo1.maven.org/maven2/dev/chrisbanes/paparazzi/

I face build failures could not resolve plugin artifact (somewhere where it was merged and working before). Next, I was clicking the link in the Chris's PR description: https://central.sonatype.dev/publisher/dev.chrisbanes.paparazzi
But I just got a CI build failure of some other plugin so exploring rn.

The build failures sound like network failures connecting to Maven Central.
I've updated the URL. Looks like Sonatype's URLs have changed

Should this branch support targetSdk 33?

If I change the plugin ID, won't that stop the plugins DSL from working?
plugins {
  id 'dev.chrisbanes.paparazzi' version '1.1.0-sdk33-alpha02'
}

Uhhhhh I guess? I don't use plugins.
What about shipping support for the app.cash.paparazzi plugin ID inside the Gradle plugin but not as a plugin marker? Would only require a src/main/resources/META-INF/gradle-plugins/app.cash.paparazzi.properties with:
implementation-class=app.cash.paparazzi.gradle.PaparazziPlugin

That would allow me to only update my dependency coordinates and not have to touch any build files.

I'm not sure if that will work, as there will then be two properties files in there, pointing to different ids. I'm not precious about keeping the current ID, so I'll just revert it.
It will mean that the plugins DSL will no longer work, but people can just use alpha03 for that.

It works. Here's an old version of Kotlin (before they switched to generating these files):

https://github.com/JetBrains/kotlin/blob/1.3.0/libraries/tools/kotlin-gradle-plugin/src/main/resources/META-INF/gradle-plugins/kotlin.properties
https://github.com/JetBrains/kotlin/blob/1.3.0/libraries/tools/kotlin-gradle-plugin/src/main/resources/META-INF/gradle-plugins/org.jetbrains.kotlin.jvm.properties

This allowed/allows both 'kotlin' and 'org.jetbrains.kotlin.jvm' to work.

Ah nice! That sounds easy. I'll give it a try now

Done! I tested it via Maven Local, and it seemed to work. Hopefully it works after being pushed up to Maven Central too.

Sweet! I'll let you know in 5-55 minutes when it shows up.

With Paparazzi 1.2.0 now out, this fork should no longer be required, so I'm going to close this 🫡
https://github.com/cashapp/paparazzi/blob/master/CHANGELOG.md#version-120

Works for me, it looks like your workaround is no longer needed!


Docs(contrib) : Add how to write links to Writers guide

fix - #3480

[x] Read and sign the [CLA][1]. PRs that haven't signed it won't be accepted.
[x] Make sure your PR complies with the [writer's guide][2].
[x] Review the diff carefully as sometimes this can reveal issues.
[x] Do not abandon your Pull Request: [Stale Pull Requests][3].

Thanks!


Looking for clarification on JmxReporter comment

There is a warning here:
https://metrics.dropwizard.io/4.1.0/manual/core.html#man-core-reporters-jmx
that says

We don’t recommend that you try to gather metrics from your production environment. JMX’s RPC API is fragile and bonkers. For development purposes and browsing, though, it can be very useful.

Is this implying the JmxReporter isn't ready for production use, or it's the opinion of the metrics team that JMX itself or metrics in general shouldn't be used in production?

@markaalvaro It's the opinion of the original author of the Dropwizard Metrics library:
https://github.com/dropwizard/metrics/blame/4.1-development/docs/source/manual/core.rst#L356
I would agree with him that JMX might not be the most suited protocol go gather metrics from an application nowadays, given that it's specific to Java and good alternatives for fetching metrics exist.


Assoc item resolution refactoring + resolve T::Item

This adds resolution of 'unselected' associated types for type parameters, e.g. in foo<T: Iterator>() -> T::Item. I actually thought rustc allowed this for any type, but as far as I can see, if you try to do it for a concrete type, it always results in 'ambiguous associated type'. So we only resolve associated types from traits in where clauses.
There's also a bunch of refactoring in preparation of resolving trait items in value NS (sorry for mixing that in here); in particular I removed the redundant and incomplete type-level resolution that was happening for the segments before the value, and made it call the type lowering code instead. Also I changed the assoc_resolutions to contain a new AssocItem enum instead of ImplItems, since they will sometimes resolve to TraitItems as well.

@matklad rebased and applied your suggestions. I did end up removing the TypeRef variant and hence the lifetime from the resolve function return again, because we also need to handle type-relative paths in the type context anyway.

bors r+

Looks like it stack overflows pretty badly, I've rolled back the commit from master

specifically,  cargo run --release -p ra_cli -- analysis-stats . fails

specifically, cargo run --release -p ra_cli -- analysis-stats . fails

Maybe run it on CI by default.

I am debating this. It'll make CI much slower :( It would be a great idea to run that during release process, once we have release process :thinking:


[enhancement request] Advanced configuration for Sandbox and Container in CRI

Task tracking
Sandbox related

[x] Sysctl configuration for sandbox #654
[x] DNS configuration for sandbox #912
[x] Port mapping configuration for sandbox #730

Container related

[x] Basic volume and device adding for container #717
[x] Mount propagation support for container #717
[x] AppArmor support for container #672
[x] Capabilities setting for container #680
[x] NoNewPrivs support container #935

Sandbox & Container Both

[x] Namespace option for sandbox & container #753
[x] Supplemental Group support for sandbox & container #753
[x] RunAsUser support for sandbox & container #722
[ ] RunAsUserName support for sandbox & container
[x] ReadOnlyRootfs support for sandbox & container #935
[x] Privileged mode support for sandbox & container #691
[x] Seccomp support for sandbox & container #701
[ ] SELinux support for sandbox & container

NOTE
The list may not be complete yet, we should supplement it anytime as the development going on :)
cc @allencloud

Any update on this ? @YaoZengzeng

Do we finish RunAsUserName support for sandbox & container and SELinux support for sandbox & container?
If the answer is yes, please close this issue. Thanks. @YaoZengzeng @Starnop

All tasks have been finished, close now.


Does not work on https pages

As the script is loaded from non https website it is blocked so can you configure your github pages website to use https?

Thanks for feedback, I'll try to configure it :)

It's very easy to configure and enforce it: Enforcing HTTPS for your GitHub Pages site

I misconfigured some options in my domain provider panel. Updated them, will see again in 24 hours. :)

https://github-profile.com/ works fine now :)
I'm going to update README with links soon with new default.

Thanks


Reasonable caching of downloaded conda packages when --use-conda and --use-singularity together

Is your feature request related to a problem? Please describe.
Installing conda environments can be slow, which makes troubleshooting a problematic one very frustrating. It would be nice if package downloads were cached during install, in order to speed up subsequent environment building.
Describe the solution you'd like
I would like to be able to set the necessary environmental variable with e.g. export SINGULARITYENV_CONDA_PKGS_DIRS=$HOME/.snakemake/conda/pkgs, which should be enough to cache downloaded packages to this location. However, the current implementation overrides this environmental variable for all singularity runs: https://github.com/snakemake/snakemake/blob/41175b3001ff59db5d7ea8bf91354decea04f74d/snakemake/deployment/conda.py#L605-L607. What's more, it sets it to a different directory with every run, so no packages get cached at all.
Just amending this line in the snakemake source seems to be sufficient to get the behavior I'm requesting. However, I don't know why the existing implementation was put into place, so I'm not sure this is a sustainable solution.
Describe alternatives you've considered
A variety of other interfaces would be acceptable, e.g. a CLI flag. Alternatively, get_singularity_envvars could hardcode a cache path in $TMPDIR or something. The current location ("/tmp/conda/{}".format(uuid.uuid4())) seems like the worst of all worlds (doesn't respect $TMPDIR, different every time and therefore doesn't help with caching).
Additional context
n/a

This is peripherally related (apologies if this is derailing the main issue!), but this would be great to have for containerizing workflows as well.  I work on a shared HPC and my colleague determined that executing workflows with the container set in the main workflow was failing due to permissions on the head node's /tmp/conda path.  It appears that the first person to try to execute a containerized workflow ( eg snakemake --use-singularity --use-conda ...) causes the creation of /tmp/conda on the head node, and without changing the permissions of that path any other users attempting to write to that path would fail.
There is also a sub-issue where using the default --conda-frontend mamba ends up trying to write to my $TMPDIR, erroring in the process, but using --conda-frontend conda does not use $TMPDIR, writing instead to /tmp/conda if it happens to have permission.
# first time running containerized workflow, no /tmp/conda exists yet
$ ls -lah  /tmp/conda/
ls: cannot access /tmp/conda/: No such file or directory
# execute without singularity
$ snakemake -s test/Snakefile --cores 4 --directory test_out --use-conda
# runs fine; still no issue with /tmp/conda, remains non-existant
$ ls -lah  /tmp/conda/
ls: cannot access /tmp/conda/: No such file or directory

# running with singularity results in a curious issue where mamba cannot create temp dirs (my $TMPDIR is set to /scratch/watersn/
$ rm -r test_out ; snakemake -s test/Snakefile --cores 4 --directory test_out --use-conda --use-singularity
Creating specified working directory test_out.
Building DAG of jobs...
Pulling singularity image docker://condaforge/mambaforge:4.12.0-0.
Creating conda environment ../test/envs/samtools.yaml...
Downloading and installing remote packages.
CreateCondaEnvironmentException:
Could not create conda environment from /lila/home/watersn/GitHub/vdblab-pipelines/test/rules/../envs/samtools.yaml:
Command:
SINGULARITYENV_CONDA_PKGS_DIRS=/tmp/conda/d19ae122-5ded-4832-94bb-b536827a2ea6 singularity  exec --home /lila/home/watersn/GitHub/vdblab-pipelines/test_out  /lila/home/watersn/GitHub/vdblab-pipelines/test_out/.snakemake/singularity/487a72edc080f28be9d6fa74dcc90b96.simg sh -c 'conda config --set channel_priority strict && mamba env create --quiet --file "/lila/home/watersn/GitHub/vdblab-pipelines/test_out/.snakemake/conda/8a4b67f2bd88f4485c9862bcd85f1291.yaml" --prefix "/lila/home/watersn/GitHub/vdblab-pipelines/test_out/.snakemake/conda/8a4b67f2bd88f4485c9862bcd85f1291"'
Output:
error    libmamba Error opening for writing "/scratch/watersn/mambafpbcIjJHiVl": No such file or directory
error    libmamba Error opening for writing "/scratch/watersn/mambafmRUfiscyMo": No such file or directory
error    libmamba Error opening for writing "/scratch/watersn/mambaf5gu21jzX6a": No such file or directory
error    libmamba Error opening for writing "/scratch/watersn/mambafswihDDfX0S": No such file or directory
error    libmamba Error opening for writing "/scratch/watersn/mambafmlCUIPDfko": No such file or directory
error    libmamba Error opening for writing "/scratch/watersn/mambafj3NUbn2R7T": No such file or directory
error    libmamba Error opening for writing "/scratch/watersn/mambafpbcIjJHiVl": No such file or directory
error    libmamba Could not open file for download /scratch/watersn/mambafpbcIjJHiVl: No such file or directory

running with singularity forcing the conda frontend fixes the
$ rm -r test_out ; snakemake -s test/Snakefile --cores 4 --directory test_out --use-conda --use-singularity --conda-frontend conda
runs without error, but creates /tmp/conda/ that no one else can write to
$ ls -lah  /tmp/conda/
total 84K
drwxr-xr-x    4 watersn brinkvd   94 Jun 27 22:45 .
drwxrwxrwt. 866 root    root    416K Jun 27 22:48 ..
drwxr-xr-x   24 watersn brinkvd 4.0K Jun 27 22:47 4b10257a-f757-4c5b-b3fe-504f44c083fc
drwxr-xr-x    3 watersn brinkvd   35 Jun 27 22:43 d19ae122-5ded-4832-94bb-b536827a2ea6

This might be related to https://github.com/snakemake/snakemake/pull/1588.  I'm running snakemake 7.8.3 and singularity 3.7.1, btw.


Add a validation split to label chunks

Add a validation set. This is now a 60/20/20 train/val/test split, indicated by the dataset flag in the metastore.

LGTM - only suggestion I can think of would be to use an enum rather than a string for the three dataset names.

Updated to use an enum instead.


request: spectrograph~ method for changing background canvas color

it'd be pretty amazing if one could change the color of the background canvas of spectrograph~ either by a message or during initializing the object..

closing in favor of https://github.com/porres/pd-else/issues/1364


WIP: Change the search view to a post method view

This will prevent the 414 Request-URI Too Long you can get from having lots of instances sent as exclusions in the GET request.

Closing this PR as I somehow totally messed up this branch. See https://github.com/wagtail/wagtail-autocomplete/pull/128 for correct PR, sorry!


clean up whitespace

There's only like... 7000 linting errors dealing with whitespace.  Can we clean this up?

2 spaces

Nice

This was completed with #87


Fix various bugs for "install" page

TLDR

Fix the broken page / broken image problem when click "Install"
Close #20089
Fix the Password Hash Algorithm display problem for #22942
Close #23183
Close #23184

Details
The broken page / broken image problem when click "Install" (Redirect failed after install gitea #23184)
Before: when click "install", all new requests will fail, because the server has been restarted. Users just see a broken page with broken images, sometimes the server is not ready but the user would have been redirect to "/user/login" page, then the users see a new broken page (connection refused or something wrong ...)
After: only check InstallLock=true for necessary handlers, and sleep for a while before restarting the server, then the browser has enough time to load the "post-install" page. And there is a script to check whether "/user/login" is ready, the user will only be redirected to the login page when the server is ready.
During new instance setup make 'Gitea Base URL' filled from window.location.origin #20089
If the "app_url" input contains localhost or <IP_ADDRESS>, use current window's location href as the app_url (aka ROOT_URL)
Fix the Password Hash Algorithm display problem for "Provide the ability to set password hash algorithm parameters #22942"
Before: the UI shows pbkdf2$50000$50

After: the UI shows pbkdf2

GET data: net::ERR_INVALID_URL #23183
Cause by empty data: in <link rel="manifest" href="data:{{.ManifestData}}">

Codecov Report

Merging #23194 (b8f3880) into main (443dcc2) will increase coverage by 47.40%.
The diff coverage is 18.75%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##           main   #23194       +/-   ##
=========================================
+ Coverage      0   47.40%   +47.40%
=========================================
  Files         0     1140     +1140
  Lines         0   151014   +151014
=========================================
+ Hits          0    71595    +71595
- Misses        0    70944    +70944
- Partials      0     8475     +8475

Impacted Files
Coverage Δ

routers/install/install.go
1.89% <0.00%> (ø)

routers/install/routes.go
41.46% <22.22%> (ø)

modules/auth/password/hash/setting.go
68.18% <50.00%> (ø)

modules/queue/setting.go
26.13% <0.00%> (ø)

modules/migration/issue.go
63.63% <0.00%> (ø)

routers/web/misc/swagger.go
100.00% <0.00%> (ø)

modules/log/log.go
58.02% <0.00%> (ø)

modules/util/legacy.go
40.00% <0.00%> (ø)

modules/git/tree.go
85.36% <0.00%> (ø)

models/repo_transfer.go
43.46% <0.00%> (ø)

... and 1133 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


'Loading panel' is shown during assertion execution (closes #1011)

/cc @AlexanderMoskovkin @AndreyBelym

/cc @inikulin

@testcafe-build-bot \retest

@testcafe-build-bot \retest

FPR

@inikulin  Is that what you mean about renaming and moving?

@inikulin what do you think about this variant?

@testcafe-build-bot \retest

@testcafe-build-bot \retest

@testcafe-build-bot \retest

FPR


Support POM exclusions with implicit wildcard

A POM exclusion can specify only the groupId or the artifactId, implying
that the other one is set as "*".

@melix Investigating the perf regression ... but thinking about it, I am not so surprised.

After checking the previous perf failure, I do not see how the change would affect it. There are no implicit wildcards in the test project, so there should be nearly no effect, aside from the two added null checks.
And running an adhoc test did pass.


Updating The Frequently Asked Questions Section

Current Behavior

Currently the frequently asked questions section is not having the proper visual appearance. And also have very minimal hover effect
Desired Behavior

I would add effective css style which will solve these issue.
Screenshots / Mockups

@akshathar-navada please assign these issue to me

Yes sure, go ahead @Keyuri-19 . Please add required screenshots before opening a PR


nvm throw error while switch node version from 15 to 8

Operating system and version:
macOS BigSur
11.0.1
nvm debug output:

nvm --version: v0.35.3
$TERM_PROGRAM: iTerm.app
$SHELL: /bin/zsh
$SHLVL: 1
${HOME}: /Users/flowfire
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: ${HOME}/.deno/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'zsh 5.8 (x86_64-apple-darwin20.0)'
uname -a: 'Darwin 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64 x86_64'
OS version: macOS 11.0.1 20B29
curl: /usr/bin/curl, curl 7.64.1 (x86_64-apple-darwin20.0) libcurl/7.64.1 (SecureTransport) LibreSSL/2.8.3 zlib/1.2.11 nghttp2/1.41.0
wget: /usr/local/bin/wget, GNU Wget 1.20.3 在 darwin19.0.0 上编译。
sed: /usr/bin/sed
cut: /usr/bin/cut
basename: /usr/bin/basename
rm: /bin/rm
mkdir: /bin/mkdir
xargs: /usr/bin/xargs
git: /usr/local/bin/git, git version 2.27.0
ls: grep:: No such file or directory
grep: grep: aliased to grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn,.idea,.tox} (grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn,.idea,.tox}), grep (BSD grep) 2.5.1-FreeBSD
awk: /usr/bin/awk, awk version 20200816
nvm current: system
which node: /usr/local/bin/node
which iojs: iojs not found
which npm: /usr/local/bin/npm
npm config get prefix: /usr/local
npm root -g: /usr/local/lib/node_modules

nvm ls output:

         v8.9.4
        v8.12.0
       v12.18.3
       v14.15.1
        v15.3.0
->       system
default -> 8 (-> v8.12.0)
node -> stable (-> v15.3.0) (default)
stable -> 15.3 (-> v15.3.0) (default)
iojs -> N/A (default)
unstable -> N/A (default)
lts/* -> lts/fermium (-> v14.15.1)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.23.0 (-> N/A)
lts/erbium -> v12.20.0 (-> N/A)
lts/fermium -> v14.15.1

How did you install nvm?

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.0/install.sh | bash

What steps did you perform?
switch the node version from 15.3.0 to 8.12.0
nvm use 8

What happened?
nvm throw an error
TypeError: Cannot destructure property `stat` of 'undefined' or 'null'.
    at Object.<anonymous> (/Users/flowfire/.nvm/versions/node/v8.12.0/lib/node_modules/npm/node_modules/@npmcli/node-gyp/lib/index.js:2:29)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/flowfire/.nvm/versions/node/v8.12.0/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script-pkg.js:4:55)
    at Module._compile (module.js:653:30)
/Users/flowfire/.nvm/versions/node/v8.12.0/lib/node_modules/npm/node_modules/@npmcli/config/lib/index.js:163
      throw new Error('call config.load() before reading values')
      ^

Error: call config.load() before reading values
    at Config.get (/Users/flowfire/.nvm/versions/node/v8.12.0/lib/node_modules/npm/node_modules/@npmcli/config/lib/index.js:163:13)
    at process.errorHandler (/Users/flowfire/.nvm/versions/node/v8.12.0/lib/node_modules/npm/lib/utils/error-handler.js:177:32)
    at emitOne (events.js:116:13)
    at process.emit (events.js:211:7)
    at process._fatalException (bootstrap_node.js:391:26)
nvm is not compatible with the npm config "prefix" option: currently set to ""
Run `npm config delete prefix` or `nvm use --delete-prefix v8.12.0` to unset it.

What did you expect to happen?
switch to 8
Is there anything in any of your profile files that modifies the PATH?

no

You're using an outdated version of nvm - can you please upgrade to v0.37.1?
Separately, the npm installation on node v8.12.0 on your machine seems broken, and to fix it you'd need to uninstall and reinstall that version of node.

You're using an outdated version of nvm - can you please upgrade to v0.37.1?
Separately, the npm installation on node v8.12.0 on your machine seems broken, and to fix it you'd need to uninstall and reinstall that version of node.

I'v upgraded the nvm to v0.37.1 version and problem is solved. Thanks.


With/From field needs to allow for multiple entries

Curators may need to enter multiple values in the With/From field.
These values may be either comma- or pipe-separated.
Maintaining the comma or pipe is essential for correctly interpreting the meaning of the entry, i.e. treat the entries as text and copy exactly how the curator enters the value(s).
In either case, if there is more than one With/From value, all values should appear in the same line in the annotation (summary table, graph editor, and annotation preview).

Added the with as a string. So far no validations

Thanks @tmushayahama
I've tested two WB entries and they look okay.

@vanaukenk let's link this one to the proposed with field constraint


Border around chat context might not be needed?

Personal preference - I do not like the border around the attached context.
Does not align with the rest of the UI.
Do we really need the border? Have we tried this without the border?

fyi @daviddossett @roblourens

Yeah, I've tried this because I don't love the weight it adds either. It does cause some weirdness when there are follow ups and lots of pills. But I'll keep playing with it to see if I can get to a place where we don't need it.

Thank you David!


Update WriteToVectorDBStage to re-raise errors from the underlying database

Description

Fixes issue where the WriteToVectorDBStage catches/logs exceptions from the underlying database allowing failures to go unnoticed.
This is a behavior change, where previously errors were stored in the control message's metadata (although there was a bug in this part too so not all errors were stored in the metadata).

Closes #1882
By Submitting this PR I confirm:

I am familiar with the Contributing Guidelines.
When the PR is ready for review, new or existing tests cover these changes.
When the PR is ready for review, the documentation is up to date with these changes.

/merge


Use named interface types for User.app_metadata and User.user_metadata to allow declaration merging

Chore
Describe the chore
Currently, the app_metadata and user_metadata fields of the User interface are defined as anonymous types like this:
 app_metadata: {
    provider?: string
    [key: string]: any
  }
  user_metadata: {
    [key: string]: any
  }

These fields often contain app specific data and each app has different expectations of what this data might contain. Hence, each app can provide its own types for each of these fields by using TypeScripts declaration merging (https://www.typescriptlang.org/docs/handbook/declaration-merging.html).
However, declaration merging is ONLY possible for named interface types - NOT for anonymous types, like the ones currently used.
The necessary change to support this scenario is simple and backwards compatible. Here is what the proposed change might look like:
// In gotrue-js/types.ts
export interface AppMetadata {
    provider?: string
    [key: string]: any
};

export interface UserMetadata {
    [key: string]: any
};

export interface User {
  id: string
  app_metadata: AppMetadata
  user_metadata: UserMetadata
  aud: string
...
}

// In myapp.ts
declare module '@supabase/gotrue-js' {
  interface UserMetadata {
    myField?: number;
  }
}

supabaseClient.auth.user()?.user_metadata.myField --> TS type checker and linters now know about myFIeld

Thanks again for the great suggestion. The PRs #464 and #465 should be handling this, thus closing the issue.


have error when growing network[32x32 to 64x64]

I train another data set which is cell Pathological image，and  it doesn‘t work well.I set the --trns_tick to 80 and --stab_tick to 40 because my data set is very small and other config is default.when the training is begining to grow network from 32x32 to 64x64,the program is stop and point out a error :
Traceback (most recent call last):
File "trainer.py", line 352, in
trainer.train()
File "trainer.py", line 258, in train
self.resl_scheduler()
File "trainer.py", line 150, in resl_scheduler
self.G.module.grow_network(floor(self.resl))
File "/media/sdc/zhanpeng/PycharmProjects/GAN/PG_GAN/pggan-pytorch/network.py", line 142, in grow_network
inter_block, ndim, self.layer_name = self.intermediate_block(resl)
File "/media/sdc/zhanpeng/PycharmProjects/GAN/PG_GAN/pggan-pytorch/network.py", line 105, in intermediate_block
layers = deconv(layers, ndim*2, ndim, 3, 1, 1, self.flag_leaky, self.flag_bn, self.flag_wn, self.flag_pixelwise)
File "/media/sdc/zhanpeng/PycharmProjects/GAN/PG_GAN/pggan-pytorch/network.py", line 13, in deconv
if wn:  layers.append(equalized_conv2d(c_in, c_out, k_size, stride, pad))
File "/media/sdc/zhanpeng/PycharmProjects/GAN/PG_GAN/pggan-pytorch/custom_layers.py", line 103, in init
self.conv = nn.Conv2d(c_in, c_out, k_size, stride, pad, bias=False)
File "/home/panzhanpeng/sdc_link/anaconda3/lib/python3.5/site-packages/torch/nn/modules/conv.py", line 273, in init
False, _pair(0), groups, bias)
File "/home/panzhanpeng/sdc_link/anaconda3/lib/python3.5/site-packages/torch/nn/modules/conv.py", line 33, in init
out_channels, in_channels // groups, *kernel_size))
TypeError: torch.cuda.FloatTensor constructor received an invalid combination of arguments - got (float, float, int, int), but expected one of:
* no arguments
* (int ...)
didn't match because some of the arguments have invalid types: (float, float, int, int)
* (torch.cuda.FloatTensor viewed_tensor)
* (torch.Size size)
* (torch.cuda.FloatStorage data)
* (Sequence data)
so what should i do?how to improve the network?

I solved the problem by modify the code，please see ：https://github.com/nashory/pggan-pytorch/pull/28

Hello zhanpengpan, I am also training my custom dataset. Could you tell me how large your dataset is? And how is your --TICK set? Still 1000?


Make the value of the watch command available for logging again.

I think we want to log the full command we run.  Including all the nvm stuff in front of it.  Also, in the watch case we should log the fact that we're running a shell command.

I'll take a look at this later today. I'll maintain consistency with the regular build commands.


Fix storage range issue during snapsync

PR description
Besu currently has a problem where, if it receives all storage slots at once without an accompanying proof, it correctly sets the end of the range to 0xFFF...FFFF. However, if all storage and a proof are received simultaneously, the logic mistakenly treats the end of the range as the last slot received rather than the expected end of the range. This discrepancy results in incomplete persistence of storage trie nodes.
Fixed Issue(s)

Thanks for sending a pull request! Have you done the following?

[ ] Checked out our contribution guidelines?
[ ] Considered documentation and added the doc-change-required label to this PR if updates are required.
[ ] Considered the changelog and included an update if required.
[ ] For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

[ ] unit tests: ./gradlew build
[ ] acceptance tests: ./gradlew acceptanceTest
[ ] integration tests: ./gradlew integrationTest
[ ] reference tests: ./gradlew ethereum:referenceTests:referenceTests

Not sure how feasible it would be but would love to get an automated test around this. I think it should go in the next release regardless as it has passed a lot of manual sync testing https://github.com/hyperledger/besu/issues/7620#issuecomment-2375692417 so is a clear improvement

added a new tests and also modified the AccountHealingTrackingTest class in order to verify and match the new behavior

@matkt worth a changelog?

@matkt worth a changelog?

don't think it is needed for this one


Issue 14543 std.algorithm.searching.until does not handle range sentinels nicely

Implemented: https://issues.dlang.org/show_bug.cgi?id=14543
This is somewhere between a bug fix and a new feature because you could argue the old behaviour is wrong.

BTW if you think this PR fixes the issue, make sure  the title of (one of) the commit's message starts with Fix issue 14543: followed by the title of the issue.

Might be worth submitting a draft PR that just changes OpenRight.no to include the full sentinel, and see if any of the projects tested on Buildkite break. If we can get away with it, that would be a much cleaner solution.
cc @atilaneves, this introduces a new public symbol.

I will do that.

The problem has been fixed here https://github.com/dlang/phobos/pull/8570


Add Guide to install via Powershell or CMD

This commands are not working for Windows which you find in the description

For windows the simplest way is to use wsl

go to command prompt for windows and type wsl --install

Then hook up the backend of docker desktop to wsl

go to docker desktop
go to settings (gear icon)
checkmark the (Use WSL 2 Backend)

Once this is all setup you want to restart your computer
Then use this command in command prompt (everything is converted to be used by windows)
set ANTHROPIC_API_KEY=your_api_key
docker run ^
-e ANTHROPIC_API_KEY=%ANTHROPIC_API_KEY% ^
-v %USERPROFILE%.anthropic:/home/computeruse/.anthropic ^
-p 5900:5900 ^
-p 8501:8501 ^
-p 6080:6080 ^
-p 8080:8080 ^
-it ghcr.io/anthropics/anthropic-quickstarts:computer-use-demo-latest
replace your_api_key with the actual Anthropic API Key


Add support for mev-rs

There's another implementation of a relay written in Rust we should add support called mev-rs.

Duplicate of #36


Autocrop creates one-line image in some situations

Expected Behavior
The image.autocrop() function should remove the transparent parts around the object in the image.
Current Behavior
Instead, in some rare cases, it creates a seemingly empty, one line graphic.
Failure Information (for bugs)
I cannot tell when exactly the source image causes autocrop to fail, but in the image in the example down below this is the case.
Steps to Reproduce
Image:
Imgur: https://imgur.com/a/Vroj0JN
Data URL: https://pastebin.com/kBHZE3Bq

Setup an environment with the Jimp version 0.5.5.
Run this code. Use the string from pastebin as variable "dataUrl".

Jimp.read(Buffer.from(dataUrl, 'base64')).then((image) => {
	image.autocrop()
	console.log({x: image.bitmap.width, y: image.bitmap.height})
});

The function logs the dimensions of the image, which will result in > x: 118, y: 1. Rendering the result image would confirm this.

Context
Running Jimp in Electron 2.0.0. The example image was created in a WebGL canvas using canvas.toDataURL()

Jimp Version: v0.5.5
Operating System: Windows 10
Node version: v8.9.3

I have this bug, too.
For reproducing: just create a white canvas in paint and draw a line only in the lower right.
Current Jimp ... current Node ... Win10
.oO( ... issue open since 2018 ... i guess i'll have to code that myself now ... )


Add support for jti claim

Hi all,
I'd like to add the support for jti claim to the package. The idea basically would be to store a list of expired jti's somewhere on the server side, and allow to blacklist specific tokens.
The way I'm thinking about the implementation is:

Use pymongo to store the blacklist (rather than a django specific mongo package, makes our solution portable to vanilla python or other frameworks)
Generate a long enough jti claim that will have negligible probability of being produced twice before the first one expired (string of 20 random ascii_letters and digits maybe?)
Store the jti and the entire payload in mongodb, this will help us clean up the collection when a JWT is past the expiry date (so we don't grow the collection ad infinitum)
Add a flag in api_settings.JWT_ENABLE_BLACKLIST, if True we add the jti claim to the payload in jwt_payload_handler()
Check against the mongodb collection everytime we decode a JWT (if JWT_ENABLE_BLACKLIST is True) and if the jti is blacklisted treat it as if the JWT is expired

I have made an initial commit to a fork of the package, with my suggestion on how to implement this, you can find it here: https://github.com/avimeir/django-rest-framework-jwt/commits/master
Happy to discuss this!
Cheers,
Avi

@erichonkanen maybe you'd like to check this out

Interesting, I hadn't heard of JWT ID before...  seems like this overlaps with my earlier search for a way to invalidate a token. What are your thoughts on adding mongo as a dependency to this package? The implementation looks good at first glance

Mongo as a dependency is definitely a no. We should probably just include a default implementation that uses Django cache backend, like how throttling in DRF works.

I believe Django cache is not the right solution since cache contents can be evicted or lost at any time. If I understand correctly, when you blacklist a token that token should be blacklisted forever. In that case using the DB is right choice.
I suggest creating a model DRFJWTBlacklist and store blacklisted tokens there. With this solution enabling a token blacklist feature will require DB access on all protected HTTP request. This should be an option and not the default behavior.

@gcollazo what are you suggesting for the default behavior?

Yeah that sounds about right. But having said that we should provide handlers like what @avimeir did. We shouldn't care where the user stores and checks for blacklisted tokens. Optional default implementation could definitely be provide a model, properly indexed, unique constraints, etc.
Also, I think UUID's might better for the actual jti.

:+1: for what @jpadilla said. Consumers of this package should be able to store and check for backlisted token wherever they want.
Providing a basic implementation that used django models sounds like a good idea but should be disabled by default. Users must enable this feature (if they want it) and specify if they want to use the bundled model backed implementation of token blacklist or use a custom one they can implement themselves.

Good read about Blacklisting JSON Web Tokens.

So to summarize the main changes you would make:

move from mongo to a model that uses the default django ORM settings
use UUID for the jti instead of the random string I've created

Am I missing something?
Happy to fix my code and issue a pull request, unless someone from the core contributors wants to take ownership. As long as it gets done and we can use it in our project - all solutions are fine with me

@avimeir yeah that sounds good. Feel free to submit a PR. No one else is working on this right now.

I pulled down @avimeir code so far and tweaking it to use a model with UUIDField (either through django-uuidfield or native if > 1.8).. seeing if I can get it working etc.. if @avimeir has update before then i'll check it out

@avimeir @jpadilla touched up the code to provide default get and set handlers for blacklisting and a default model implementation... let me know your thoughts
https://github.com/GetBlimp/django-rest-framework-jwt/commit/0c0f946d8ff72c2ac4b1c0425649b14a29f493b6
PS havent tested yet but will this weekend

Is JTI meant to be used as a session identifier?

@tachang per the spec:
The jti (JWT ID) claim provides a unique identifier for the JWT. The identifier value MUST be assigned in a manner that ensures that there is a negligible probability that the same value will be accidentally assigned to a different data object; if the application uses multiple issuers, collisions MUST be prevented among values produced by different issuers as well.

So essentially yes, which might be confusing since the whole point of using jwt is for a stateless auth mechanism... This page helped...

Cool. Makes a lot of sense. Kind of like old school session cookies where you stored each cookie in the database. Or a certificate revocation list.
I like the idea of using Django's default database since the biggest issue with blacklists is always propagating them.
Just a thought but the main reason I'd want to invalidate a token is because a user is marked inactive. I assume then I'd have to iterate through all tokens generated for a specific user and then add them to the blacklist? This is probably the most common use case for this feature.

@tachang yeah I think you're right about the primary reason for invalidating a token is an inactive user... previously I was thinking of implementing an activity-based auth mechanism that could log out a user and invalidate the jwt and this seems precisely fit for that...
If you are storing all the tokens generated in the db then yes you might want to iterate through any previous non-expired ones and blacklist them. However at least in my case I don't store the tokens at all and would probably just use the default implementation here where a blacklist token obj is created manually when blacklisting a token.

@jpadilla  Any plan to merge this into a future release?

@avimeir sorry this is taking so long but I think we'll get it in soon.. pending hooking it into a demo app

Thanks!

After taking a look at the awesome demo put together by @erichonkanen and talking with him at the different use cases for this feature and how it fits together with this package I'm inclining more that this feature be released as a separate package. I'm failing to see this now fit into the purpose of this(django-rest-framework-jwt) package which is basically just enabling auth with JWT.
There are many benefits of this being released as another package. We don't currently have a use case for the feature so maintaining further along it would be harder. @avimeir Would you be interested in taking charge? All of the work is already there, it just needs to be placed in a new package and someone willing to maintain it.

additionally, i'd like to hear more about the use cases and thoughts on validity of doing jwt revocation after reading conflicting accounts online...

@erichonkanen's demo is really cool, and I'd keep it anyway, maybe evolving it into a demo explaining JWT for new users?
As per blacklisting- my main use case was to force logout users even if they hold a valid JWT. I will consider taking it out to a new package, especially if more people are interested in it (currently I'm using a fork that enables this, but it's not open-source ready yet).
Anyway, I agree that it might fit better outside of django-rest-framework-jwt. Thank guys!

@avimeir Im curious, @jpadilla brought up the fact that an alternate approach to force-logging them out would be to just delete their jwt from the client storage/cache, what are your thoughts on that?

Won't work for applications where you must ensure that the user is logged out indeed, a smart user could copy the token client-side and keep using it until it expires.

that makes sense... so yeah I think the blacklist feature makes sense still but haven't heard anyone else wanting to use it which makes me wonder if it would make sense in the main repo.. I do like the fact that it is just optional anyways so it is opt-in
if anyone else watching and has feedback plz reply

Why not check if the user is active after the authentication is done? This seems an authorization question, rather then an authentication question. Just my 2 cents.

@gabn88 this can probably be closed... I did end up implementing a blacklist token feature but we decided it wasn't best to be included in the main package, and also at the time I personally didn't have the need or understanding to use it (although it did work nice).

Sorry to bump this old thread, but I still find the JWT blacklisting highly valuable. Best use case is a mitigation scenario whenever a token was compromised (and maybe you'd have the user force all connected devices/browser to log out before changing her credentials and logging in again from a safe place).
@erichonkanen I'm about to dig up your old PR and try to adapt your program to the changed codebase. Should I know anything before I do? (I'm thinking maybe you've learned new valuable things since then).
Cheers

@dheavy go right ahead! one thing I did that might impact it is I think I abstracted part of the view stuff out from how it was before... i'd have to look into it again and Im not sure what has changed since then but let me know if you want me to look at anything! it was working well at time it was submitted...

@dheavy https://github.com/erichonkanen/django-rest-framework-jwt/blob/4306ab9916a82e77c29c30256249b4e4f178c251/rest_framework_jwt/views.py#L59 (and L19) I had made those staticmethod so you can override it easily in a subclassed view such as here, that said it was just an idea at the time!

Can we close this one?


Error Compile nginx 1.13.4+modsecurity

my folder :

cd /usr/src/nginx-1.13.4
and i try #./configure --user=www-data --group=www-data --add-module=/usr/src/ModSecurity/nginx/modsecurity --with-http_ssl_module --with-http_v2_module
and next i try make

this error i see is :
cc: error: /usr/src/ModSecurity/nginx/modsecurity/../../standalone/.libs/standalone.a: No such file or directory
objs/Makefile:253: recipe for target 'objs/nginx' failed
how to fix it ? thanks

Hi @kulitkerang,
Make sure you have followed the compilation recipes stated here:
https://github.com/SpiderLabs/ModSecurity/wiki/Compilation-recipes-for-v3.x

ohh okay thanks
On Tue, Jun 4, 2019 at 7:47 PM Felipe Zimmerle<EMAIL_ADDRESS>wrote:

Closed #2108 https://github.com/SpiderLabs/ModSecurity/issues/2108.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SpiderLabs/ModSecurity/issues/2108?email_source=notifications&email_token=AGIGXDH7DYKOMFTBREDAVW3PYZP6NA5CNFSM4HSAOZZ2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORZLABTY#event-2388000975,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGIGXDAVTL3KIYXU5BZYLFLPYZP6NANCNFSM4HSAOZZQ
.


Update for laravel 5.1

The list method has changed for laravel 5.1, this change causes a fail every time a slug is created or retrieved
Laravel upgrade guide says :
"The lists method now returns a Collection instance. If you would like to convert the Collection into a plain array, use the all method"
i made a check for L5 and 5.1 with "method_exists" i'm not sure if is clean, but it works.

I ran into the same problem and Bouhnosaure's solution is better than mine. Works with Laravel 5.1 for me too. Haven't personally tested it with Laravel 5.0 to see if its backwards compatible.
But it is necessary since upgrading to Laravel 5.1 causes a breaking change if eloquent-sluggable is installed.

thanks for this :+1:

The PR for #145 fixes this for Laravel 5.0 and 5.1, and (sorry) is a bit of a cleaner solution I think.  I'll be merging it shortly.

No problem ! :)
Thanks for response !


Button overlaying on IE11

In IE11 the both buttons are overlaying, in Chrome it's well

Hi! It happens to me as well in IE11 and also in IE10.
Any help is appreciated!


JS optimized implementation of ProtocolWidget and ProtocolState

We spend a lot of CPU encoding changes from Redwood. Right now the guest code goes through our very nice Kotlin APIs for ChangeSink and Change. Unfortunately kotlinx.serialization is not particularly inefficient here.
I’d like to try to write a new implementation of the guest versions of these classes that’s optimized for Kotlin/JS. I would like to skip directly to producing plain JS objects rather than creating Kotlin objects and then using kotlinx.serialization to convert ’em. (I will still need to use kotlinx.serialization to encode property values.)

I don't think plain objects is the right answer because they still need to undergo JSON encoding. It'll be faster, since it's C code instead of JS-hosted Kotlin code, but it's still JSON encoding.
We can instead teach each Change subtype to JSON "encode" itself directly to a string and build up the JSON in a buildString directly, only calling out to kotlinx.serialization for user types like you said.
I mean look at what we generate:
https://github.com/cashapp/redwood/blob/89eb7bec5e4b2a2f8d48f5f057c85f468cdb2b23/redwood-protocol/src/commonTest/kotlin/app/cash/redwood/protocol/ProtocolTest.kt#L92-L99
The Create class can get a member
public fun appendJsonTo(builder: StringBuilder) {
  builder.append("""["create",{"id":""")
  builder.append(id.value)
  builder.append(""","tag":""")
  builder.append(tag.value)
  builder.append("}]")
}

and we're done. Repeat for all the other subtypes.
Then with a custom serializer for List<Change> we can do the top-level buildString + comma insertion, and then write that as an unsafe raw string into the JsonEncoder.
An even more efficient version of this bypasses allocating any Change instances and simply builds the raw JSON string directly. Unfortunately this breaks the current API unless we do something crazy like
class RawJsonChange : Change {
  val json = StringBuidler()
}

and only have this single allocation per set of changes.

Doing JSON encoding in JS would be more efficient if we had a good StringBuilder on QuickJS. Sigh.

True. We could do a List and write them all sequentially to the underlying stream.

True. We could do a List and write them all sequentially to the underlying stream.

I used a sampling profiler to measure just how much time we’re spending in serialization code. For one sample I took it’s about 19% of the samples:

With this optimization implemented that drops down to about 3% of the samples:

Is this done?

Yup.


#184752084 Setup docker for backend application

What does this PR do?

Using docker set up the environment in which the e-commerce-bn will run into

Description of Task to be completed?
Using docker compose, set up a ymal file that will run two services :

express server
postgres db

How should this be manually tested?

Want to test each image/container individually ?

Run docker build -t <imageName> .  to build the Image for the Container
Run docker images to list all the images in the computer
Run docker run --name <containerName> -p 5005:5005 <imageName>  the -p tag is for port number
Run docker start <containerName> to start a container

You can learn more about Docker here
What are the relevant pivotal tracker stories?

#184752084

After merging and rebasing develop ,i have a bug on the config property  on index.js  of the database in the container.

Note:   i think it is not the environment variable that are not visible in the container because i tried to console.log them and i saw them . I m not seeing where is the problem


export com.sun.management.internal when running Druid under JRE11 and JRE17

Fixes #12312 which was reported half a year ago.
This PR has:

[X] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[X] been tested in a test Druid cluster.

Couple questions:

Is this still needed after the changes to JvmMonitor in #12481?
Is it --add-exports or --add-opens that we need?

Is this still needed after the changes to JvmMonitor in Use MXBeans to get GC metrics #12476 #12481?

Yes, we need it. The AllocationMetricCollector differs from the JvmMonitor that we changed before, and I have not found a management API to replace it.

Is it --add-exports or --add-opens that we need?

Basically, add-opens can be seen as a super set of add-exports. The former one allows us to access non-public methods via reflection while the latter one allows us to access public methods only. Use add-opens makes the things simpler.


Fix window holes behind transparent objects

Without this change, the transparent objects composed over the opaque
background creates the transparency of the entire window through which
the desktop wallpaper could be seen.
This problem manifested itself with glow backend and wayland compositor
(gnome).
This patch completely eliminates this problem. With it, the final image
produced by glow backend corresponds to the image produced by the wgpu
backend.
Fixes #1018

This is not correct solution. I'll continue to dig in.


Rework Image cache

Some shows don't have a poster on either fanart.tv or tmdb. TVDB seems to have the most extensive poster collection for all the tv shows so it should probably be implemented as the default image source.
API documentation: https://api.thetvdb.com/swagger

https://github.com/flownzu/TraktTV-UpdateClient/commit/6dde64d97c457836a5cfc9b117271ac6585b3ecf


Refactor component tests with beforeEach() to render the component

Everytime we add new required props, we have to add these props to every single test.
To save time, we render the component within beforeEach().
If we need a different prop value than the default, we use rerender.

Done with InputColorCode.test.js


Cookbook http_stub_status_module not found

I am trying to write a cookbook to install my rails application and I get the following error when I run vagrant provision
==> default: [2015-01-18T15:24:03+00:00] INFO: Forking chef instance to converge...
==> default: [2015-01-18T15:24:03+00:00] INFO: *** Chef 12.0.3 ***
==> default: [2015-01-18T15:24:03+00:00] INFO: Chef-client pid: 13888
==> default: [2015-01-18T15:24:09+00:00] INFO: Setting the run_list to ["recipe[apt]", "recipe[build-essential]", "recipe[rvm::vagrant]", "recipe[rvm::system]", "recipe[rvm::gem_package]", "recipe[nginx::source]"] from CLI options
==> default: [2015-01-18T15:24:09+00:00] INFO: Run List is [recipe[apt], recipe[build-essential], recipe[rvm::vagrant], recipe[rvm::system], recipe[rvm::gem_package], recipe[nginx::source]]
==> default: [2015-01-18T15:24:09+00:00] INFO: Run List expands to [apt, build-essential, rvm::vagrant, rvm::system, rvm::gem_package, nginx::source]
==> default: [2015-01-18T15:24:09+00:00] INFO: Starting Chef Run for nginx-berkshelf
==> default: [2015-01-18T15:24:09+00:00] INFO: Running start handlers
==> default: [2015-01-18T15:24:09+00:00] INFO: Start handlers complete.
==> default: /tmp/vagrant-chef/cd3bbd54c0efcf612e706f9728d04ed6/cookbooks/rvm/libraries/rvm_chef_user_environment.rb:49: warning: class variable access from toplevel
==> default: [2015-01-18T15:24:11+00:00] INFO: execute[Guard resource] ran successfully
==> default: [2015-01-18T15:24:11+00:00] WARN: Cloning resource attributes for group[rvm] from prior resource (CHEF-3694)
==> default: [2015-01-18T15:24:11+00:00] WARN: Previous group[rvm]: /tmp/vagrant-chef/cd3bbd54c0efcf612e706f9728d04ed6/cookbooks/rvm/recipes/vagrant.rb:34:in `from_file'
==> default: [2015-01-18T15:24:11+00:00] WARN: Current  group[rvm]: /tmp/vagrant-chef/cd3bbd54c0efcf612e706f9728d04ed6/cookbooks/rvm/recipes/system.rb:33:in `from_file'
==> default: [2015-01-18T15:24:11+00:00] INFO: gem_package resource has been patched to use provider Chef::Provider::Package::RVMRubygems and will install gems to the ruby-1.9.3-p429 RVM Ruby.
==> default: [2015-01-18T15:24:11+00:00] INFO: ohai plugins will be at: /etc/chef/ohai_plugins
==> default: [2015-01-18T15:24:12+00:00] INFO: ohai[custom_plugins] reloaded
==> default: [2015-01-18T15:24:12+00:00] WARN: MissingCookbookDependency:
==> default: Recipe `http_stub_status_module` is not in the run_list, and cookbook 'http_stub_status_module'
==> default: is not a dependency of any cookbook in the run_list.  To load this recipe,
==> default: first add a dependency on cookbook 'http_stub_status_module' in the cookbook you're
==> default: including it from in that cookbook's metadata.
==> default:
==> default: ================================================================================
==> default: Recipe Compile Error in /tmp/vagrant-chef/cd3bbd54c0efcf612e706f9728d04ed6/cookbooks/nginx/recipes/source.rb
==> default: ================================================================================
==> default:
==> default:
==> default: Chef::Exceptions::CookbookNotFound
==> default: ----------------------------------
==> default: Cookbook http_stub_status_module not found. If you're loading http_stub_status_module from another cookbook, make sure you configure the dependency in your metadata
==> default:
==> default:
==> default: Cookbook Trace:
==> default: ---------------
==> default:   /tmp/vagrant-chef/cd3bbd54c0efcf612e706f9728d04ed6/cookbooks/nginx/recipes/source.rb:91:in `block in from_file'
==> default:
==> default:   /tmp/vagrant-chef/cd3bbd54c0efcf612e706f9728d04ed6/cookbooks/nginx/recipes/source.rb:90:in `each'
==> default:
==> default:   /tmp/vagrant-chef/cd3bbd54c0efcf612e706f9728d04ed6/cookbooks/nginx/recipes/source.rb:90:in `from_file'
==> default:
==> default: Relevant File Content:
==> default: ----------------------
==> default: /tmp/vagrant-chef/cd3bbd54c0efcf612e706f9728d04ed6/cookbooks/nginx/recipes/source.rb:
==> default:
==> default:  84:    code <<-EOH
==> default:  85:      tar zxf #{::File.basename(src_filepath)} -C #{::File.dirname(src_filepath)}
==> default:  86:    EOH
==> default:  87:    not_if { ::File.directory?("#{Chef::Config['file_cache_path'] || '/tmp'}/nginx-#{node['nginx']['source']['version']}") }
==> default:  88:  end
==> default:  89:
==> default:  90:  node['nginx']['source']['modules'].each do |ngx_module|
==> default:  91>>   include_recipe ngx_module
==> default:  92:  end
==> default:  93:
==> default:  94:  configure_flags       = node.run_state['nginx_configure_flags']
==> default:  95:  nginx_force_recompile = node.run_state['nginx_force_recompile']
==> default:  96:
==> default:  97:  bash 'compile_nginx_source' do
==> default:  98:    cwd  ::File.dirname(src_filepath)
==> default:  99:    code <<-EOH
==> default: 100:      cd nginx-#{node['nginx']['source']['version']} &&
==> default:
==> default: [2015-01-18T15:24:12+00:00] ERROR: Running exception handlers
==> default: [2015-01-18T15:24:12+00:00] ERROR: Exception handlers complete
==> default: [2015-01-18T15:24:12+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> default: [2015-01-18T15:24:12+00:00] ERROR: Cookbook http_stub_status_module not found. If you're loading http_stub_status_module from another cookbook, make sure you configure the dependency in your metadata
==> default: [2015-01-18T15:24:12+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

Could you solve this error? I am getting the same issue.

nginx::http_stub_status_module

The issue looks like at the time that you were using this recipe that node['nginx']['source']['modules'] had http_stub_status_module included without fully qualifying it. If you take a look at this test within the cookbook:
https://github.com/chef-cookbooks/nginx/blob/22a1b6365755782e82067d61ab34a0569c5c1704/test/cookbooks/test/recipes/modules.rb


MessageBox: Add "mud-message-box" class

Description

Adds a class to MudMessageBox so you can apply styles to it and its children.
How Has This Been Tested?

none
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] 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.
[ ] I've added relevant tests.

Replaces #7807 because I broke the branch

Just visually from another project. Unsure what tests would be added.

The test would be basically to test if the specified style is applied in the html, a really simple test.

Just visually from another project. Unsure what tests would be added.

The test would be basically to test if the specified class is applied in the html, a really simple test.

@ScarletKuro
That makes sense! Are the tests I just added appropriate?

Thanks!


Update kind image to 1.20.2

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@ericvn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio

@ericvn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-helm-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-security-k8s-tests_istio

integ-pilot-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-distroless-k8s-tests_istio

integ-helm-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-helm-tests_istio

integ-security-k8s-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-security-k8s-tests_istio

integ-pilot-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
1ea099e1ccc1f6efb027d6bb38c376067fd82dd7
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


feat(data/int/order): delete int.order and prove all commented out lemmas

TO CONTRIBUTORS:
Make sure you have:

[x] reviewed and applied the coding style: coding, naming
[x] make sure definitions and lemmas are put in the right files
[x] make sure definitions and lemmas are not redundant

For reviewers: code review check list

Thanks for the review. I noted connections for the ones that you missed.

I've got rid of all the duplicate lemmas and removed the import from files that imported data.int.order


Typescript use of React SFC (stateless functional component) usage generates spurious error highlighting

VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T17:15:57.756Z)
OS Version: Darwin x64 16.4.0
Extensions:

Extension
Author (truncated)
Version

vscode-color
ans
0.4.5

Steps to Reproduce:

create a new directory with a file called main.tsx with the following contents

import * as React from 'react';
import * as ReactDOM from 'react-dom';

interface WelcomeProps {
  name: string,
 }

 const Welcome: React.SFC<WelcomeProps> = (props) => {
  return
Hello, {props.name}
;
 }

 class Test extends React.Component<any, any> {
  constructor(props: any) {
      super(props);
  }

  render() {
      return

              <Welcome name="Mike"/>

;
  }
}

may need to npm install the react typings to reproduce the problem

npm init
npm install --save react react-dom @types/react @types/react-dom

running tsc --jsx react main.tsx gives no compilation errors.   (I'm running tsc version 2.4.2)

in VS Code, there's a red squiggly under :

It's not clear to me why the JSX element should need to have any "construct or call signatures", but this pattern seems to compile with tsc fine and run fine in the browser.
for reference, I also get the same error highlighting in Sublime Text, so perhaps it's an issue with the underlying Language Services server?  I could not find a separate repo for that server, so it was not clear if I should log the issue under vscode versus the Typescript repo, so please feel free to send me elsewhere if this issue does not seem like it belongs here.

A few questions:

What version of TypeScript is active in the workspace. This is shown in the status bar next to the language mode:

If you run go to definition on something like React.Component, which file does it open up?

Thanks, your question lead me to a resolution of this problem.   In the corner it said it was running Typescript 2.0.0.  I assumed that it would run whichever version of typescript my project declared in the package.json file.  Clicking on that in the corner brought me to the page which explained that the typescript.tsdk user setting can be used to point to a specific typescript installation.   After switching this setting and restarting VSCode, it said 2.4.2 in the corner and I no longer had the spurious "no construct or call signatures" error over the use of the SFC.
Incidentally, switching to 2.4.2 also made auto-completion on React Props working so I will close the other issue that I opened, #33641


async load

if me network not good, or other reason lead to discord RPC response slowly, then vimsence will waiting for response long time, at this moment the vim will hang. I can't do any. Please fix it, thank you

Alternatively, a timeout of 1 second would be nice.


Negative zero hashes to a different value than zero

In F32 and F64, the number -0.0 has a different bit pattern than 0.0. Although the hardware instructions automatically take care of -0.0 == 0.0 returning true, they don't take care of making sure hash(-0.0) == hash(0.0).
To fix this, we should special-case hash(-0.0) to return whatever the answer to hash(0.0) is. (Hopefully inlining and constant propagation will result in the return value being effectively hardcoded rather than computed it at runtime, which will help compensate for the performance cost of the branch misprediction.)
We must apply this special-casing in code generation rather than in Zig, to make sure that we only run the conditional when the Layout is either F64 or F32. It's very important not to do this -0.0 check for other layouts, because for them, whatever the bit pattern is for -0.0 has a totally different meaning, and should not be treated as equivalent to another bit pattern - otherwise we would be explicitly causing hash collisions, and paying a performance cost to cause them too!

I don't see anything about hashing floats in the docs. Is this still relevant @rtfeldman?


Kadane's Algorithm

Kadane's Algorithm
Used for finding the longest contiguous sub-array sum.
Languages supported

Python
C [@raksha009]
CPP
Java
C#
Golang
JavaScript

@GSNCodes Can I work on it?

@harsh-9in
Hey!
I'm not a reviewer. I've raised an Issue so that it can be assigned to me to work on.
You can maybe ask the reviewer to assign the same in another language.

okay, No Problem :)

Hi! @harsh-9in would you be able to write the code in another language?

@GSNCodes, you can submit the algo in Python :)

@ricardoprins I can submit it Using c++.

Perfect, game on @harsh-9in !

Alright, is anyone here up for a challenge?

Hello everyone, I am new to this repository. It will be my first contribution to this repo.
@ricardoprins
Can I work on this issue in Java.

@ricardoprins Please assign me this task.

@parjanyaacoder Go ahead with Java.

I also wanna contribute to this I wanna contribute to it in java

Hello, I am new to this repository. I haven't contributed anything to this repo.
I can work on this issue in C, C++ & Python.
@VijayaGB98 can you please assign me this task?

I can work on Python, C and Java.

I can work on this using C.

I can work on this in Javascript.

Hi, I created an issue #352  .. but I am not assigned the task here. Plz asssign it to me.

plz assign me this issue @atarax665 @Kajol-Kumari

@raksha009 please go with C

I would like to work in Golang, @Kajol-Kumari  please assign me :)