Compilation with amdflang fails

On a system with ROCm 6.0.1 installed, attempts to install with spack install feq-parse % rocmcc fails with the following error
3 errors found in build log:
     49    [  2%] Building Fortran object src/CMakeFiles/feqparse.dir/FEQParse.F90.o
     50    cd /tmp/root/spack-stage/spack-stage-feq-parse-2.1.0-mj5pd3fuk5pau3org24ulsw7tedhwmo6/spack-build-mj5pd3f/src && /opt/spack/lib/spack/env/rocmcc/amdflang -Dfeqparse_EXPORTS  -O3
           -DNDEBUG -J../include -fPIC -c /tmp/root/spack-stage/spack-stage-feq-parse-2.1.0-mj5pd3fuk5pau3org24ulsw7tedhwmo6/spack-src/src/FEQParse.F90 -o CMakeFiles/feqparse.dir/FEQParse.F
           90.o
     51    F90-S-0026-Unmatched quote (/tmp/root/spack-stage/spack-stage-feq-parse-2.1.0-mj5pd3fuk5pau3org24ulsw7tedhwmo6/spack-src/src/FEQParse.F90: 271)
     52      0 inform,   0 warnings,   1 severes, 0 fatal for tokenize
     53    F90-S-0026-Unmatched quote (/tmp/root/spack-stage/spack-stage-feq-parse-2.1.0-mj5pd3fuk5pau3org24ulsw7tedhwmo6/spack-src/src/FEQParse.F90: 1642)
     54      0 inform,   0 warnings,   1 severes, 0 fatal for priority
  >> 55    make[2]: *** [src/CMakeFiles/feqparse.dir/build.make:78: src/CMakeFiles/feqparse.dir/FEQParse.F90.o] Error 1
     56    make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-feq-parse-2.1.0-mj5pd3fuk5pau3org24ulsw7tedhwmo6/spack-build-mj5pd3f'
  >> 57    make[1]: *** [CMakeFiles/Makefile2:123: src/CMakeFiles/feqparse.dir/all] Error 2
     58    make[1]: Leaving directory '/tmp/root/spack-stage/spack-stage-feq-parse-2.1.0-mj5pd3fuk5pau3org24ulsw7tedhwmo6/spack-build-mj5pd3f'
  >> 59    make: *** [Makefile:139: all] Error 2

Testing with v2.2.0 of feq-parse fails installation with rocmcc with the following error
3 errors found in build log:
     47    cd /tmp/root/spack-stage/spack-stage-feq-parse-2.2.0-3fpb6fg7jvhuzuccwyzti6zuai2z4f7f/spack-build-3fpb6fg/src && /opt/spack/lib/spack/env/rocmcc/amdflang -Dfeqparse_EXPORTS  -O3
           -DNDEBUG -J../include -fPIC -c /tmp/root/spack-stage/spack-stage-feq-parse-2.2.0-3fpb6fg7jvhuzuccwyzti6zuai2z4f7f/spack-src/src/FEQParse_TokenStack.F90 -o CMakeFiles/feqparse.dir
           /FEQParse_TokenStack.F90.o
     48    /usr/bin/cmake -E cmake_copy_f90_mod include/feqparse_tokenstack.mod src/CMakeFiles/feqparse.dir/feqparse_tokenstack.mod.stamp Flang
     49    [  1%] Building Fortran object src/CMakeFiles/feqparse.dir/FEQParse.F90.o
     50    cd /tmp/root/spack-stage/spack-stage-feq-parse-2.2.0-3fpb6fg7jvhuzuccwyzti6zuai2z4f7f/spack-build-3fpb6fg/src && /opt/spack/lib/spack/env/rocmcc/amdflang -Dfeqparse_EXPORTS  -O3
           -DNDEBUG -J../include -fPIC -c /tmp/root/spack-stage/spack-stage-feq-parse-2.2.0-3fpb6fg7jvhuzuccwyzti6zuai2z4f7f/spack-src/src/FEQParse.F90 -o CMakeFiles/feqparse.dir/FEQParse.F
           90.o
     51    F90-F-0155-Derived type has not been declared - indepvar (/tmp/root/spack-stage/spack-stage-feq-parse-2.2.0-3fpb6fg7jvhuzuccwyzti6zuai2z4f7f/spack-src/src/FEQParse.F90: 57)
     52    F90/x86-64 Linux Flang - 1.5 2017-05-01: compilation aborted
  >> 53    make[2]: *** [src/CMakeFiles/feqparse.dir/build.make:78: src/CMakeFiles/feqparse.dir/FEQParse.F90.o] Error 1
     54    make[2]: Leaving directory '/tmp/root/spack-stage/spack-stage-feq-parse-2.2.0-3fpb6fg7jvhuzuccwyzti6zuai2z4f7f/spack-build-3fpb6fg'
  >> 55    make[1]: *** [CMakeFiles/Makefile2:461: src/CMakeFiles/feqparse.dir/all] Error 2
     56    make[1]: Leaving directory '/tmp/root/spack-stage/spack-stage-feq-parse-2.2.0-3fpb6fg7jvhuzuccwyzti6zuai2z4f7f/spack-build-3fpb6fg'
  >> 57    make: *** [Makefile:139: all] Error 2

Moving the declaration of indepVar type to the top of the private types section of FEQParse.F90 resolves this issue, but all rank 2 and higher rank tests fail with segmentation faults.. There's a bit to resolve here.


Remove placeholder after a option has been selected

Is there any 'Quick fix' to remove the :placeholder"" after a option has been selected?

Fixed together with #379.

Hi, the placeholder still shows when :searchable="false". Is this expected for this mode or will get fixed ?

I also see this behavior on version 2.0.2. The placeholder only goes away after I select a second item, but not on the first selected item. This is with :searchable="true"

Has this been fixed? I'm still seeing it on 2.0.8.

Sorry @patricknavarro don't think its fixed.
https://jsfiddle.net/shentao/jqofkzxc/

Still seeing this in v2.1.0.

I'm using version for vue 1, and i done this with this css rule
.multiselect__tag~.multiselect__loading-transition~.multiselect__input{
width: 1px;
color: transparent;
}
P.S. It can't be display:none because it loses focus event and closing starts working not correct.
Hope this helps somebody


Is this based on the new document format?

I follow along the automerge project quite I while. I am still waiting for a stable documen format. I looks like the work on the performance branch is related to this new format. Are you implementing already the new format in rust or still the old one.
Nevertheless great idea of brining automerge to rust. I am looking forward to use it in an iOS App.

Right now we're implementing the old format. I need to update the README a bit but we're making good progress on building a WASM module which can be used by the current javascript implementation.
Once the performance work is stabilised we'll build a rust implementation of that as well.

Sound great.


Auto reload causes debuggers not to attach properly

Describe the bug
When in debug mode, the auto reload functionality seems to break debuggers such as PyCharm.
Expected behavior
Auto reload and debugger support.
Environment (please complete the following information):

OS: MacOS
Version: 0.8.3

@mackeyja92 thanks for your report!
There's an ongoing discussion related to the auto_reload feature in the community forums. You should definitely check it out - although it started as a Windows support for this feature, it aims to contemplate all OSes :wink:

https://github.com/watchexec/watchexec May be a good candidate to support all OSes.

Closing in favor of #1346 and the community discussion linked above.

Why is this closed? This is a bug for all I know.
Setting debug=True or auto_reload=True breaks PyCharm debugging. I like to have debug logging and use PyCharm to debug my code, but that's not possible right now because setting debug=True will also enable the auto_reload stuff.
Please fix this


How to user onEntitySaving feature?

I dont want the video to be saved by default , anyone has any idea how can i use this code? it shows error.

There is no example related to this as well

#31


Describe accounting terms and systems

Describe how the accounting system works, what it consists of and how to work it.
Also make a small list of terms and words and what they mean.

When starting accounting, some base information needs to be provided if the organization has already done bookkeeping. Usually you would import your bookkeeping information from your previous software, saved in a SIE format, but some software also have a manual way of getting started. Either way, what is inputted is the starting balance of each account, so how much is in them from start, the duration that the bookkeeping should cover (fiscal year) and the Chart of Accounts to use for the bookkeeping.
When bookkeeping, you will create new transactions into a fiscal year that is open (i.e. it hasn't been finalized/isn't completed), uploading verifications to those transactions and selecting accounts from the Chart of Accounts to balance it with.
Very important point is that a transaction, once saved and added to the fiscal year, is not editable or deletable - rather, if a verification needs to be revoked or edited, a new transaction is made specifically to revert and correct a previous one. These will officially be counted as two different transactions, but most software shows their connection in some manner. This is a legal requirement for electronical bookkeeping systems in Sweden to be counted as a valid program to use for bookkeeping.
Once all transactions has been made for the fiscal year, and the accountant has checked that everything is correct, it is time to close the bookkeeping. This process entails creating some final transactions and locking the year. This is a step which differs depending on what kind of organization it is, so to keep it simple for now, this step will be kept manual. All that remains is therefore to lock the  year, making it non-editable and finalized. Some software also allow you to unlock a year and make edits, but require that the previous bookkeeping has been closed and locked before starting a near year.
When creating a new year, the input settings needed are fetched from the previous fiscal year's bookkeeping, making the process smoother.
When closing the books and when the books has been closed, that is when Balance Reports and Result Reports are generated - before as a preview to verify the accounting looks OK, and after to create the "official" reports.

@AlexanderTarler please have a look at this and see if it makes sense!

Note: our system will probably only support Kontantmetoden at first, if the Fakturametoden is too different or requires additional features.

I'm late to the party, but this looks great! Simple yet efficient. Well done!


extendable config for dcos-history

@cmaloney please add this one to your next train. test failures are all unrelated flakiness

:ship:


Create NFCorpus benchmark

Create nfcorpus benchmark. It is about retrieval dataset for Medical Information Retreieval.
Dataset Link
https://ir-datasets.com/nfcorpus.html#nfcorpus/test
Dataset official website
https://www.cl.uni-heidelberg.de/statnlpgroup/nfcorpus/
Paper
https://link.springer.com/chapter/10.1007/978-3-319-30671-1_58

Close issue because too many gts per one question. And questions


Error detected while processing function

Error detected while processing function 71_Output_cb[3]..lsp#handlers#ProcessMessages[32]..lsp#handlers#ProcessNotif[32]..72_ProcessDiagNotif[1]..lsp#diag#DiagNotification[64]..lsp#diag#Pro
cessNewDiags[21]..74_DiagsRefresh[1]..BufWinEnter Autocommands for "*"..function 53_Highlight_Matching_Pair:
line  149:
E801: ID already taken: 3
Arises randomly during opening files.

The Highlight_Matching_Pair() function is defined in the matchparen plugin.  The LSP plugin doesn't use the match ID 3.  It looks like when the LSP plugin loads a buffer using bufload(), it somehow leads the matchparen plugin to add the match with the ID 3 again leading to this error.  Is there a list of steps/configuration that you use when you see this error?

@yegappan maybe the modlines, specially some files had some chars looked like modlines (but actually it is not)
then err or unexpected cases happened...
so maybe should avoid modlines when bufload(), but:
1, not sure how or is it ok?
2, i think silent! was not an ok solution for it.

but even no lsp, that file may have err/unexpected cases still when directly open it, so not sure if worthy to fix it.

I have committed d7d29b63960f4f591068f6f67230c9e8740e053c to silence the error messages when loading a buffer.  Does this commit fix this issue?

This seems to be solved


Added and updated strings for Update 16

Looks good! Sorry for taking so long on this. 🙃

No problem mate :D


File-level private vals of a type from an external dependency result in that dependency requiring to be an api dependency

Plugin version
1.31.0
Gradle version
8.7
(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version
Kotlin 1.9.23
(Optional) reason output for bugs relating to incorrect advice
Source: main
------------
* Exposes 1 class: some.externa.dependency.ExternalEnum (implies api).

Describe the bug
When declaring file-level private val variables which are typed with some type from some dependency, that dependency is required to be an api() dependency, even though that file-level variable is only used in non-public contexts, such as a constructor argument to an internal class
private val FOO_ENUMS = ExternalEnum.entries.filter { it.name.startsWith("Foo") }

internal class MyClass(private val foos: Set<ExternalEnum> = FOO_ENUMS)

To Reproduce
Steps to reproduce the behavior:
In on project, declare some type
enum class ExternalEnum {
  FOO_ONE
  FOO_TWO
  BAR
}

In a second project, declare a class and a file-level private val variable
private val FOO_ENUMS = ExternalEnum.entries.filter { it.name.startsWith("Foo") }

internal class MyClass(private val foos: Set<ExternalEnum> = FOO_ENUMS)

Now run
./gradlew :second-project:reason --id :first-project
Expected behavior
The output of :reason should be that ExternalEnum is a used class, implying implementation
Additional context
An existing work around is to move the file-level private val variables to the companion object of the class, eg
internal class MyClass(private val foos: Set<ExternalEnum> = FOO_ENUMS) {
  companion object {
    private val FOO_ENUMS = ExternalEnum.entries.filter { it.name.startsWith("Foo") }
  }
}

This class will result in the command giving the expected output.

Thanks for the report.

Interestingly enough, this only happens with the exact setup you have. If your internal class instead looks like
internal class MyClass(private val foos: List<ExternalEnum>)
then DAGP doesn't advise changing the dependency declaration. I think there's some kind of synthetic bridge class that is actually public in the bytecode. Investigating...

I created another repro in my project and decompiled it to Java. Here's what it looks like. You can clearly see the public methods that "expose" the private property.
// DeleteMe.java
package com.autonomousapps;

import kotlin.Metadata;
import kotlin.jvm.internal.DefaultConstructorMarker;
import kotlin.jvm.internal.Intrinsics;
import okio.Buffer;
import org.jetbrains.annotations.NotNull;

@Metadata(
   mv = {1, 8, 0},
   k = 1,
   xi = 48,
   d1 = {"\u0000\u0012\n\u0002\u0018\u0002\n\u0002\u0010\u0000\n\u0000\n\u0002\u0018\u0002\n\u0002\b\u0002\b\u0000\u0018\u00002\u00020\u0001B\u000f\u0012\b\b\u0002\u0010\u0002\u001a\u00020\u0003¢\u0006\u0002\u0010\u0004R\u000e\u0010\u0002\u001a\u00020\u0003X\u0082\u0004¢\u0006\u0002\n\u0000¨\u0006\u0005"},
   d2 = {"Lcom/autonomousapps/DeleteMe;", "", "okio", "Lokio/Buffer;", "(Lokio/Buffer;)V", "dependency-analysis-gradle-plugin"}
)
public final class DeleteMe {
   @NotNull
   private final Buffer okio;

   public DeleteMe(@NotNull Buffer okio) {
      Intrinsics.checkNotNullParameter(okio, "okio");
      super();
      this.okio = okio;
   }

   // $FF: synthetic method
   public DeleteMe(Buffer var1, int var2, DefaultConstructorMarker var3) {
      if ((var2 & 1) != 0) {
         var1 = DeleteMeKt.access$getOKIO$p();
      }

      this(var1);
   }

   public DeleteMe() {
      this((Buffer)null, 1, (DefaultConstructorMarker)null);
   }
}
// DeleteMeKt.java
package com.autonomousapps;

import kotlin.Metadata;
import okio.Buffer;
import org.jetbrains.annotations.NotNull;

@Metadata(
   mv = {1, 8, 0},
   k = 2,
   xi = 48,
   d1 = {"\u0000\b\n\u0000\n\u0002\u0018\u0002\n\u0000\"\u000e\u0010\u0000\u001a\u00020\u0001X\u0082\u0004¢\u0006\u0002\n\u0000¨\u0006\u0002"},
   d2 = {"OKIO", "Lokio/Buffer;", "dependency-analysis-gradle-plugin"}
)
public final class DeleteMeKt {
   @NotNull
   private static final Buffer OKIO = new Buffer();

   // $FF: synthetic method
   public static final Buffer access$getOKIO$p() {
      return OKIO;
   }
}

It might be possible to detect this and provide more accurate advice. Might also be non-trivial.


Several tickers return Exception when getting historical data with period="max" and interval="1mo"

Several tickers return Exception when getting historical data with period="max" and interval="1mo"
I had code that used yfinance to get monthly max period close price data for a small number of tickers. The code worked fine for yfinance version 0.1, but I ran it again using yfinance version 0.2.9 and for several of the tickers it was returning the exception below. It worked just fine for several of the tickers, but then returned the exception below for others. I checked the yahoo! finance website and the data is all there for those tickers that are returning the exception. Oddly enough, it seemed to work fine when I changed either the period or interval - it just didn't seem to like having both period="max" and interval="1mo" for some reason.
Examples
Works fine
yf.Ticker("ABBV").history(period="10y", interval="1mo")["Close"]
yf.Ticker("ABBV").history(period="max", interval="1wk")["Close"]
Returns Exception
yf.Ticker("ABBV").history(period="max", interval="1mo")["Close"]

Exception                                 Traceback (most recent call last)
~\AppData\Local\Temp/ipykernel_13864/234900509.py in
----> 1 yf.Ticker('ABBV').history(period="max", interval="1mo")["Close"]
~\Anaconda3\lib\site-packages\yfinance\base.py in history(self, period, interval, start, end, prepost, actions, auto_adjust, back_adjust, repair, keepna, proxy, rounding, timeout, debug, raise_errors)
709         df = quotes.sort_index()
710         if dividends.shape[0] > 0:
--> 711             df = utils.safe_merge_dfs(df, dividends, interval)
712         if "Dividends" in df.columns:
713             df.loc[df["Dividends"].isna(), "Dividends"] = 0
~\Anaconda3\lib\site-packages\yfinance\utils.py in safe_merge_dfs(df_main, df_sub, interval)
631             df = _pd.concat([df, df_sub_missing], sort=True)[col_ordering]
632         else:
--> 633             raise Exception("Lost data during merge despite all attempts to align data (see above)")
634
635     return df
Exception: Lost data during merge despite all attempts to align data (see above)

Thanks for detail. Simple problem, simple fix. Can you try branch hotfix/prices-merge-events?

@ivan23kor FYI. Can you create the PR?


[Bug]: Missing Method System.IO.FileStream

All of the following criteria must be met

[X] All Requirements must be installed.
[ ] Full Latest.log file included. If no file exists then leave this unchecked and state so.

All of the following are optional to answer

[x] Tried reinstalling the Game.
[X] Tried reinstalling MelonLoader.
[x] Tried restarting PC.
[ ] Was able to see the Start Screen.

Describe the issue.
Hello i was installing melonloader on firewatch and then i finished the installation and then ı tried launching the game and an error screen popped up

it was really fast i had to record it and slow it down and i tried everything but it just doesnt work it didnt even create a log file.
Did you attach your log file?

[ ] Yes, I attached my log file to the text box above.
[X] No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

i had this too

does anyone have a solution

Hey guys! Melon Loader v0.5.7 works with Firewatch. Try downgrading to that version and trying again.

why doesnt it work with other versions tho

why doesnt it work with other versions tho

It's probably some change in the v0.6.1 release that broke it.

Ok thanks


conda 4.4 adds "conda activate", "conda deactivate" commands

see https://github.com/conda/conda/blob/master/CHANGELOG.md#new-features
completion for the command names (even without the environment names) would be nice.

fixed by #11

I just installed this, but I still can't get activate and deactivate to show up:

@diego898 can you open a new issue for this one? It seems like there are several commands not being picked up.

@esc - sure! I opened #14


Fix MediaBlock SVG icon size in the rich text editor

Fixes #6142
Fixes the .icon style specifically, not https://github.com/wagtail/wagtail/issues/6142#issuecomment-644175830

Do the tests still pass? (https://docs.wagtail.io/en/latest/contributing/developing.html#testing) ✅
Does the code comply with the style guide? (Run make lint from the Wagtail root)✅
For Python changes: Have you added tests to cover the new/fixed behaviour? N/A
For front-end changes: Did you test on all of Wagtail’s supported browsers? Please list the exact versions you tested.

Firefox 77, Chrome 83, Safari 13.1.1

For new features: Has the documentation been updated accordingly? N/A

Merged in via b77f1b75ce0114fe6738c774864533dfc7c7ff43
I did not add a new changelog entry as this is just a regression on a future feature.
Thanks for fixing @zerolab


[DOC] doc string determine_local_basis is missing

hello,
I would like to use the determine_local_basis function in curvature.py. but i'm confused about the inputs and the outputs format.
For example how should I reshape  my input "normal" . How to define the proj_matrix and which tolerance should i use ?
I understand that this function is used in the function fit_curvature but i dont understand how to initiate my imputs arguments
thanks for your help,

Hello @MaximeDdnn ,
The function is confusing indeed: I propose to add some comments to clarify. Briefly:

the normal vector should be 3 x1
the proj_matrix is obtained through the curvature_fit function. There is no tolerance but the if in determine_local_basis_function is there to avoid a projection to a null vector if the normal equal [[1],[0],[0]]


Merging updates with deploy version

Yep, need to synch. I did a no-no and pushed to main and not to deploy first.


Memory leak using Gstreamer pipelines as video input

There is memory leaks issues when using video inputs like:

Webcam as a gstreamer pipeline: "v4l2src device=/dev/video0 ! video/x-raw, framerate=30/1, width=640, height=360 ! videoconvert ! appsink"
Raspberrypi cam : "nvarguscamerasrc ! video/x-raw(memory:NVMM),width=1280, height=720, framerate=30/1, format=NV12 ! nvvidconv ! video/x-raw, format=BGRx, width=640, height=360 ! videoconvert ! video/x-raw, format=BGR ! appsink"

It seems related to OpenCV and VideoCapture API .
Filled two issue on nvidia forum and darknet:

https://devtalk.nvidia.com/default/topic/1064350/jetson-nano/memory-leak-running-darknet-yolo-with-opencv-on-a-gstreamer-input/
https://github.com/AlexeyAB/darknet/issues/4031

One thing that would be good would be to repro the bug with OpenCV 3.4.7 (latest) and fill an issue on the OpenCV repo.

-c 1 did not help :(, it still grows darknet memory till it freezes around 55% of usage in my jetson tx2 case.

Hi @muukkivi . I had the same experience with TX2 while testing last friday. With either -c 1 or gstreamer pipeline I had a leak... Whereas with the jetson nano I don't with -c 1.. I even tried to update to OpenCV latest 2.4.7 ..
I have no time to investigate more right now... I think the way forward will be to use Deepstream: https://github.com/opendatacam/opendatacam/issues/112

ok, will try that. I might be able to test something on this issue for the future releases if you need?
I tried i cannot run the separate darknet with -c 1 version, it asks for gstreamer and errors pop up. Anyway if you need testing let me know.

interesting got myself a jetson nano, and exactly the same problem - in 10 to 11 minutes the system freezes. I wonder how many people are there who do not have this problem? I mean they an run the system for hours or days? And if yes, what is the difference in set up?

tried something similar on nano but it did not change things:
https://devtalk.nvidia.com/default/topic/1057460/jetson-tx2/custom-built-opencv-3-4-0-following-nvidia-advice-not-working/post/5363355/#5363355
still if some of us are not getting the memory leak, then it would be great to know what is the difference with their nano or jetson tx2 configuration.

Considering this - if by following exactly the opendatacam installing instructions on how to implement the software on jetson tx2 and jetson nano - the result is in average 4-15min of working time. Then this should be well-stated on the projects main page that currently the solution is not stable due to memory leakage and therefore system cannot be functionally used but only for short testing periods (anyone who wants to help in testing and developing feel free to contribute). I mean I've put in over thousand euros on this and over 100 hours of trying to get it working from June 2019 with no good results. No offence but everyone should be aware of this leakage before starting to buy nvidia cards including the high end xavier for only vehicle counting purpose as is my case for example. I mean the information should be very clear that the program currently probably will not function.

I have the solution running on multiple devices, yes, its crashes, but its works longer than in your case.
Regress to earliest commits of the code(if you want to make the code running), as from my experience, in the last 6 months, alot had changed from Jetpack to Cuda to all the surrounding libraries, and the documents do not reflect that. Right now I think the focus for this project on my part in to get deepstream running and linked (alot of the issues related to this upgrade).

Also, as a temp fix, make sure you have a swap partition on your jetson nano, it might help with runnin time: https://github.com/opendatacam/opendatacam/blob/master/documentation/jetson/JETSON_NANO.md#3-setup-a-swap-partition

yes, did that already before proceeding to test the opendatacam

Seems there was some improvements on the darknet side, the author added an alternative way to run darknet which seems to improve things for some people: https://github.com/AlexeyAB/darknet/issues/4453#issuecomment-569513695
Also Jetpack now ships with OpenCV v4 and gstreamer support built in
I'm gonna update everything and try if the runtime and memory usage is improved. cc @shams3049

After installing on a nano with Jetpack latest (4.3) and making the latest version of darknet with OpenCV v4 and gstreamer (default from this jetpack version) I found out that:

Running darknet with ./darknet detector demo - original C implementation of detection on video that is built-in darknet , is still leaking like previously, crashed after only 10 min on a jetson nano

Running darknet with ./uselib - a new C++ implementation of detection on video that was made by the author of the darknet fork, is not leaking 🎉🎉 , still running with no memory increase after 2 hours

This confirms that the problems comes from darknet and not from OpenCV / Gstreamer.
The less good news is that this new way of running darknet with ./uselib is lacking essentials features we need to integrate to opendatacam:

Beeing able to run without a GUI
Beeing able to foward the video as a MJPEG stream
Beeing able to send detections as a json stream
Beeing able to input a gstreamer pipeline

This "theoretically" shouldn't be that hard to integrate as we would "just" need to port them from the old C API if I were a bit more proficient with C / C++  . I answered the author of the fork for some pointers: https://github.com/AlexeyAB/darknet/issues/4453#issuecomment-593450826  , will see as he is generally very responsive.
This is definitely very promising to be able to get rid of this issue and make OpenDataCam much more reliable. cc @b-g

Good news 🎉, I have been able to enhance this new ./uselib API for darknet with missing things, still a work in progress: https://github.com/tdurand/darknet/pull/1/files
I'm still figuring out some details for the JSON stream of detections to be able to hook opendatacam node app to it but it is mostly under control, and adding things didn't seem to create any memory leak at first sight.
Will finish tomorrow and hopefully have a first build of opendatacam to test without this infamous memory leak.

Some update on this, I've finished the first integration (see changes to be made to darknet: https://github.com/tdurand/darknet/pull/1/files) and was able to run properly opendatacam using this new darknet API on both Jetsons and Ubuntu CUDA machine.
So far no sign of memory leaks from the tests I did. (ran more than 10 hours on a jetson nano)
I'm now working on providing a build installable via Docker, and also on updating the documentation for a non-docker install.. I aim to have something ready to be tested by end of this week.
The Docker build is a bit more work to do than expected because with this new darknet API our docker pipeline for jetson's isn't working out of the box (cause of opencv versions I think). Instead of patching even more an already pretty hacky way of dockerize opendatacam on jetson's, I'm looking into using the newly released Jetpack base container for docker, which should simplify the pipeline (and unify between CUDA machine and jetsons) and also normally gives us the possibility to use CSI camera (raspberry pi cam for example) from docker.
cc @b-g

Mega! 🎉 + 🤞!!

Some update,  switching to the new "dockerization" pipeline for jetson turns out to be trickier than expected: https://github.com/opendatacam/opendatacam/issues/178
That said, I successfully managed to generate a build for jetson nano with our current pipeline after fixing another issue 😎..  So build v3.0.0-alpha.1 is on its way, I will be available by tomorrow to test as I'm uploading it to dockerhub right now
Also I've updated the documentation to run v3.0.0-alpha.1 without docker: https://github.com/opendatacam/opendatacam/blob/v3.0.0-alpha.1/documentation/USE_WITHOUT_DOCKER.md

Looking for people to test OpenDataCam v3.0.0-alpha.1 on Jetson nano to see if memory leak problem is fixed
Docker setup
Build only available on jetson nano for now.
Should work from jetpack 4.2.x , if not please flash to 4.3
# Remove previous install files or run setup from a new folder

Remove config.json, install-opendatacam.sh, run-docker.sh, run-opendatacam.sh

# Download install script
wget -N https://raw.githubusercontent.com/opendatacam/opendatacam/v3.0.0-alpha.1/docker/install-opendatacam.sh

# Give exec permission
chmod 777 install-opendatacam.sh

# NB: You will be asked for sudo password when installing the docker container

# Install command for Jetson Nano
./install-opendatacam.sh --platform nano

Non-docker setup:
If you want to install without docker (on another platform than jetson nano), follow this documentation:
https://github.com/opendatacam/opendatacam/blob/v3.0.0-alpha.1/documentation/USE_WITHOUT_DOCKER.md

@tdurand That is great! Many thanks!! Could you also share here how to track the memory usage / potential leaks in an easy way?

Yes you can use htop from terminal
sudo apt-get install htop

htop

It will display the processes and the memory usage, you will have a line with ./uselib blabalbalbala which should be on top and on the left you have the memory usage..

Also this change might have introduced other bugs, interested if you can test a bit all the features... I've seem for example that the FPS indicator wasn't very reliable.

Ok, this seems to be fixed, closing in favor of : https://github.com/opendatacam/opendatacam/issues/182


Safari rendering bug causes upward offset of tool shelf color picker

There is a Safari bug affecting our color picker popover for the tool shelf's working colors input. It causes Safari to render the popover by about a 130px upward offset. However, the click targets and devtools hover highlight visualizations for the elements in this popover do show up in the correct location, so this only affects how Safari paints the content.
https://github.com/GraphiteEditor/Graphite/assets/4388688/575d079d-803d-4fc5-8194-8ec977142a32

It only occurs if there exists a scrollbar in the Properties panel

But strangely, it doesn't happen if there exists a scrollbar in the Layers panel— something must somehow be different between those two panels

It only occurs if the tool shelf has at least two columns

However, it being two or three columns doesn't affect how tall the ~130px upward offset is
Deleting the .tools container will visibly shrink the shelf back to a width of 1 column, but doesn't stop the issue from occurring until the web page gets resized

Disabling container-type: size; on the .shelf-and-table element prevents the issue from occurring

We need to investigate this further, ideally create a minimal reproduction test case, and report this. Then hope it's fixed. Or, find a particular way that we can change things to mitigate this on our end.
This is tested on Safari 16.5, and I've more recently tested it on 17.3.
container-type was added in Safari 16 (released 2022-09-12).

Reproduction steps:

Open https://editor.graphite.rs/
Make a new document
Reduce the height of the web page such that the drawing tools on the left become two columns (this happens via container-type: size and some calc() magic)
Draw a rectangle and make sure it's selected, in order to populate the top-right Properties panel such that it has enough content to overflow and cause a vertical scrollbar
Click either of the black or white color circles beneath the drawing tools at the bottom left of the UI
This should be drawn at the bottom left corner of the web app, but it gets painted ~130px higher than it's supposed to be— but hover over the correct locations of buttons and you'll see it interact with the incorrectly offset painted buttons
Resize the Properties panel downwards so it has enough space to avoid needing scrollbars for its content (but don't resize the page to cause the drawing tools to become single-column)— and notice that the offset bug goes away, even though the Properties panel has no child/ancestor relationship with the tools and color picker

https://bugs.webkit.org/show_bug.cgi?id=274144

It sounds like this has been fixed in the latest Safari code but hasn't yet made its way into a Technical Preview or full release. So it's just a matter of waiting an indeterminate (and unfortunately, likely rather long) until it reaches users.

This is fixed in the beta version of Safari 18, which is apparently set for a release this fall. So once that rolls out, and reaches more users over the following months and years, it shouldn't be as much of a problem anymore (especially once we require WebGPU to run Graphite soon, which will also require the latest Safari browser or a switch to Chrome or Firefox).


ADLS Gen2 Access Model description does not take User Delegation SAS tokens into account

The paragraph 'Shared Key and Shared Access Signature (SAS) authorization` does not take User Delegation SAS tokens into account. It says that "no identity is associated with the called and therefore security principal permission-based authorization cannot be performed", but this is not true for User Delegation SAS tokens, as those are associated with an identity.
The problem is that User Delegation SAS tokens do not seem to work as described in the diagram on this page. A User Delegation SAS token with only the skoid parameter and not a suoid or saoid parameter will perform the RBAC check (step 1 in the diagram), but will not perform an ACL check (step 4 in the diagram).
Please mention User Delegation SAS tokens in the paragraph 'Shared Key and Shared Access Signature (SAS) authorization`, and describe their limitation in that they only perform check 1 (the RBAC check) and not step 4 (the ACL check).

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 3894c552-8352-bf04-6c86-d0ef222b43c8
Version Independent ID: ee3cd458-852d-8afb-fe5b-64c947e5b5d6
Content: Access control model for Azure Data Lake Storage Gen2 - Azure Storage
Content Source: articles/storage/blobs/data-lake-storage-access-control-model.md
Service: azure-data-lake-storage
GitHub Login: @normesta
Microsoft Alias: normesta

@jurjenoskam
Thank you for bringing this to our attention.
I've delegated this to content author @normesta, who will review it and offer their insightful opinions.

Thanks for your contribution to our documentation
We are making overall enhancements to our content. As part of that effort, we are creating a content request in our backlog to address this gap and are closing this GitHub issue. The updated content will be published shortly.

Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Add Modular Math Operation

mm. i'm not a fan of this pattern? Not the operation, just the pattern. And it's called modulus, not modular


Could you please share the code on how to get semantic and spatial information in the .hdf5 files?

Hi, this is a great job. I' very interested in the 'image_adj_matrix' and 'semantic_adj_matrix' which represent the spatial and semantic information,respectively. But in your project, this two important information had write in the .hdf5 files, so could you please share the code or pretrained models on how to get this two information. I'm looking forward for your reply, thanks!
Best wishes for you!

Same question here...

Hi,
Thank you for your interests in this project and sorry about the slow response.
For spatial adj matrix, please refer to #9
For semantic adj matrix, we are not releasing the model at the moment. But it is a very small and simple classification model trained on Visual Genome, you can refer to this paper:
http://openaccess.thecvf.com/content_ECCV_2018/papers/Ting_Yao_Exploring_Visual_Relationship_ECCV_2018_paper.pdf


Incorrect dark mode shadow color

Version used: 0.3.0
Devices/Android versions reproduced on: Samsung Galaxy S9+, OneUI 2.5, Android 10

As can be seen from the image, light mode works fine, while dark mode does not, which would require some nasty workarounds to get that working as expected.
I have this as my main theme:
<style name="Theme.ControllerHub" parent="Theme.Neumorph.DayNight.NoActionBar">
That particular element is an ImageButton which I've set up following the sample code in the Readme. This also happens for the regular button.
Am I doing something wrong here?

I solved this issue by myself, I didn't understand how theme/style inheritance work, but I got it working now, I just needed to use <style name="Theme.**Neumorph**.ControllerHub" parent="Theme.Neumorph.DayNight.NoActionBar">


Input/Output separation

Hello,
Thank you very much for the library.
I'm trying to find a way to separate input and output in a case like this:
func main() {

    cmd := exec.Command("sh", "-c", "mongo --quiet --host=localhost test") // user input, could be any shell command
    f, _ := pty.Start(cmd)
    cmd.Start()

    time.Sleep(1 * time.Second)

    for ;; {

        io.WriteString(f, "sleep(1000);Date.now();\n")
        stdoutScanner := bufio.NewScanner(f)

        go func() {
            for stdoutScanner.Scan() {
                text := stdoutScanner.Text()
                println(text)
            }
        }()

        time.Sleep(2000 * time.Millisecond)
    }
}

This code produces the following output:
> sleep(1000);Date.now();sleep(1000);Date.now();
1559185677551
sleep(1000);Date.now();
1559185679053
1559185691069
now();
1559185692573
);Date.now();sleep(1000);Date.now();
1559185694074
ep(1000);Date.now();sleep(1000);Date.now();

What I need is just
1559185677551
1559185679053
1559185691069
1559185692573
1559185694074

I can filter out all scanned text which contains user input, but that does not work stable - in the example you can find pieces like ep(1000);Date.now();
I would really appreciate if you can suggest a better solution

If you just want the result, I'd suggest to not use a pty.
This sample yields the output you expect:
package main

import (
        "bufio"
        "io"
        "os/exec"
        "time"
)

func main() {
        cmd := exec.Command("sh", "-c", "mongo --quiet --host=localhost test") // user input, could be any shell command
        stdin, _ := cmd.StdinPipe()
        stdout, _ := cmd.StdoutPipe()
        _ = cmd.Start()

        time.Sleep(1 * time.Second)

        stdoutScanner := bufio.NewScanner(stdout)
        go func() {
                for stdoutScanner.Scan() {
                        text := stdoutScanner.Text()
                        println(text)
                }
        }()

        for {
                io.WriteString(stdin, "sleep(1000);Date.now();\n")
                time.Sleep(2000 * time.Millisecond)
        }
}

Now, if really you do need a tty, then you'll have to filter out. This is an issue with the mongo CLI though, not with the lib.
The way to achieve what you describe is to disable the ECHO ioctl,
however, mongo resets that setting regardless of the previous state, so it will always print back the input in tty mode.
Here is an example to show that sh behaves as expected when disabling the ECHO ioctl.
package main

import (
        "bufio"
        "io"
        "os"
        "os/exec"
        "time"

        "github.com/kr/pty"
        "golang.org/x/sys/unix"
)

func echoOff(f *os.File) {
        fd := int(f.Fd())
        //      const ioctlReadTermios = unix.TIOCGETA // OSX.
        const ioctlReadTermios = unix.TCGETS // Linux
        //      const ioctlWriterTermios =  unix.TIOCSETA // OSX.
        const ioctlWriteTermios = unix.TCSETS // Linux

        termios, err := unix.IoctlGetTermios(fd, ioctlReadTermios)
        if err != nil {
                panic(err)
        }

        newState := *termios
        newState.Lflag &^= unix.ECHO
        newState.Lflag |= unix.ICANON | unix.ISIG
        newState.Iflag |= unix.ICRNL
        if err := unix.IoctlSetTermios(fd, ioctlWriteTermios, &newState); err != nil {
                panic(err)
        }
}

func main() {
        // cmd := exec.Command("mongo", "--quiet", "--host=localhost", "test") // user input, could be any shell command
        cmd := exec.Command("sh")
        pty, _ := pty.Start(cmd)
        echoOff(pty)

        stdinR, stdinW := io.Pipe()
        go io.Copy(pty, stdinR)

        time.Sleep(1 * time.Second)

        stdoutScanner := bufio.NewScanner(pty)
        go func() {
                for stdoutScanner.Scan() {
                        text := stdoutScanner.Text()
                        println(text)
                }
        }()

        for i := 0; i < 10; i++ {
                //io.WriteString(stdinW, "sleep(1000);Date.now();\n")
                io.WriteString(stdinW, "sleep 1; date\n")
                time.Sleep(2000 * time.Millisecond)
        }
}

Closing the issue as it is not related to the library.

Thank you very much for the explanation!


Configure Server/Client External Module for Distance

In the main arkouda repository, examples/cos_dist.py demonstrates how to use Arkouda to compute cosine distance. We want to take this one step further and configure an example that will demonstrate how to add this functionality as an external Arkouda module with components on both the server and client.
Cosine Distance
Euclidean Distance

This has been updated to utilize a pip install on the module. This requires a setup.py be provided, but is much cleaner and able to operate the same as the server commands.

It looks like this issue did not get linked to the PR correctly. This was closed by #7


[docs] no hard-coding cuda

What does this PR do?
This PR adds xpu besides cuda and replaces the hard-coded cuda with device-agnostic device.
@muellerzr

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Thanks for the suggestion! Code Updated. @muellerzr


Deserialize/Serialize undetected libnodes/transformations properly

If a library node or a transformation that is not in the current loaded set is loaded with an SDFG, dace raises an exception during loading.
If the transformations are not applied or the library nodes are not expanded, there is no need to actually have them. The idea is to create a class for UninitializedObject (one for transformation and one for library node) that keeps the JSON property dictionary, which will raise the exception only upon expansion (libnodes) or when trying to apply it (transformations). Whenever the SDFG is serialized again, the properties will be dumped as-is so that there is no difference between the loaded and saved SDFG.

Done by @phschaad


Show node nickname in channel form if we know it

When using the new suggested channels, when clicking a node the form shows me the node displayed in pubkey@host format. If we know some name for this node, we should display it instead of the IP, giving a better user experience.

you mean the Alias, Yes probably you are right about UX but if you want to manual check you need that visualization format. Maybe ip is useless and so just replace Ip part with alias and leave Uri as manual check ?

sounds good. i'll replace the ip by alias 🙌


Please advise when will v0.29.0 tag be released? Currently it's labeled prerelease for 23 days.

Feature request
Please advise when will v0.29.0 tag be released? Currently it's labeled prerelease for 23 days.
Why it is needed
We are looking forward to upgrade to v0.29.0 to have fixes for some current bugs. Currently, we see this being published in NPM but are not sure why it is hanging with a Prerelease tag?
Is this just an overlook or is there a valid reason for the tag v0.29.0 to be not labeled as Latest Release?
Thanks in advanced for an update on this.

You can still install the pre release. It’ll be published as the latest versions once properly tested.


[Regression] do not modify Cookie::$path on Response::sendCookies()

What steps will reproduce the problem?

Make codeception tests that test sending form data(get CSRF token and submit form)
see it fail

What is the expected result?
I should be able to test my beautiful form
What do you get instead?
It fails because codeception does not CSRF cookie any more since Cookie:: $sameSite is appended to Cookie::$path
Additional info
https://github.com/Codeception/module-yii2/issues/47

Q
A

Yii version
2.0.35

PHP version
5.6.x, 7.0.x, 7.1.x, 7.2.x, 7.3.x

Operating system
Docker(really does not matter)

Awesome 👍


Introduce tooling-api for all embedders

Expected Behavior
One module which can be used across all embedders to run detekt.
Configuration is made via a Spec dsl.
The tooling api defines interfaces to run detekt according to the plugin needs.
The goal is to unify using detekt in: cli, gradle-plugin, maven-plugin, bazel-plugin, intellij-plugin, sonar-detekt and the compiler-plugin,
Current Behavior
Every plugin creates internal core and cli classes like ProcessingSettings, DetektFacade and loadDefaultConfig to load and run detekt. Most often CliArgs is used to setup detekt making the cli module more core than core.
Context
When making changes to core or cli there are often breaking change for the Intellij or Sonarqube plugins.

DSL I came up with
Using the tooling-api in the cli module:
internal fun CliArgs.createSpec(output: Appendable, error: Appendable): ProcessingSpec {
    val args = this
    return ProcessingSpec {

        logging {
            debug = args.debug
            outputChannel = output
            errorChannel = error
        }

        project {
            inputPaths = args.inputPaths
            excludes = asPatterns(args.excludes)
            includes = asPatterns(args.includes)
        }

        rules {
            autoCorrect = args.autoCorrect
            activateExperimentalRules = args.failFast
            maxIssuePolicy = RulesSpec.MaxIssuePolicy.NonSpecified // not yet supported; prefer to read from config
            excludeCorrectable = false // not yet supported; loaded from config
            runPolicy = args.toRunPolicy()
        }

        baseline {
            path = args.baseline
            shouldCreateDuringAnalysis = args.createBaseline
        }

        config {
            useDefaultConfig = args.buildUponDefaultConfig
            shouldValidateBeforeAnalysis = false
            knownPatterns = emptyList()
            // ^^ cli does not have these properties yet; specified in yaml config for now
            configPaths = config?.let { MultipleExistingPathConverter().convert(it) } ?: emptyList()
            resources = configResource?.let { MultipleClasspathResourceConverter().convert(it) } ?: emptyList()
        }

        execution {
            parallelParsing = args.parallel
            parallelAnalysis = args.parallel
        }

        extensions {
            disableDefaultRuleSets = args.disableDefaultRuleSets
            fromPaths { args.plugins?.let { MultipleExistingPathConverter().convert(it) } ?: emptyList() }
        }

        reports {
            args.reportPaths.forEach {
                report { it.kind to it.path }
            }
        }

        compiler {
            jvmTarget = args.jvmTarget.description
            languageVersion = args.languageVersion?.versionString
            classpath = args.classpath?.trim()
        }
    }
}

Detekt interface to run analysis
/**
 * Instance of detekt.
 *
 * Runs analysis based on [io.github.detekt.tooling.api.spec.ProcessingSpec] configuration.
 */
interface Detekt {

    fun run(): AnalysisResult

    fun run(path: Path): AnalysisResult

    fun run(sourceCode: String, filename: String): AnalysisResult

    fun run(files: Collection<KtFile>, bindingContext: BindingContext): AnalysisResult

    fun run(files: Collection<KtFile>, bindingTrace: BindingTrace): AnalysisResult
}

Runs analysis based on [io.github.detekt.tooling.api.spec.ProcessingSpec] configuration.

Which ProcessingSpec there is not ProcessingSpec in this interface. and, do we need 5 different functions? Can't we just have one and then add extension funcitions for the other ones? Or default implementations? This way the core just do it's thing. It doesn't know how the clients use it.

Oh, it's the detekt provider interface which needs the ProcessingSpec to construct a Detekt instance.
interface DetektProvider {

    /**
     * Configure a [Detekt] instance based on given [ProcessingSpec].
     */
    fun get(processingSpec: ProcessingSpec): Detekt

The run methods are convenience methods for the clients. Else they have no way to run a detekt analysis just on in-memory sourcecode or with a custom BindingContext. They would need to dig in the core module and use internals.

One thing I want to add (since we might use this in the Bazel rule) — please don’t forget about the documentation. Right now we don’t copy-paste Detekt options documentation and redirect to the CLI API description. It would be useful at least for Gradle, Maven, Bazel and CLI to have a glossary of sorts to continue doing this. I. e. instead of documenting option A in a Maven plugin have an ability to state that it configures the Z Detekt option.

Is this tooling API documented anywhere? I am attempting to bump Detekt in Sputnik, but am struggling to find exactly how to replace the previous invocation with using the new API.

@snooze92 glad you found it :).
There are some properties of the Spec which do not change any behavior and using the AnalysisResult does require to @OptIn. When we smooth out these edges documentation will follow :).

OK, makes sense. You can see my proposal for bumping Detekt in Sputnik, mostly here.

OK, makes sense. You can see my proposal for bumping Detekt in Sputnik, mostly here.

Nice to see the tooling-api in action outside of detekt :).


Flyway source won't build due to missing sqlline indirect dependency

I've pulled the latest source as of March 14, 2016 (commit# 36091a0eba2f0dc2f3860b029fa617412247bb7f) and am attempting to build/test a change.
I've been looking at the Dev Environment Setup and Database Setup pages to get the process going but keep hitting the error below when compiling flyway-core using the command-line:
C:\Dropbox\Projects\3rdParty\flyway>mvn -U clean install -DskipTests -Dmaven.tes
t.skip=true -P-InstallableDBTest,-CommercialDBTest,-CommandlinePlatformAssemblie
s

[ERROR] Failed to execute goal on project flyway-core: Could not resolve dependencies for project org.flywaydb:flyway-core:jar:0-SNAPSHOT: Could not find artifact sqlline:sqlline:jar:1.1.8 in nexus

Full output available at out.txt.
The code I'm interested in is really the command-line client so I really don't need/want any of the database stuff at this point, so I've attempted to prevent all tests from both compiling (-Dmaven.test.skip=true) or running (-DskipTests) per the Surefire documentation, but the error still happens.
The only version of sqlline available in Maven Central is sqlline:sqlline:1.1.9 and I'm unaware of another way to get v1.1.8.

Please give the latest version a go. Thanks, Axel


Duplicate test-run element

Using the latest package from NuGet (3.4.0-beta-3) I'm getting a test-run element nested inside another test-run element (containing the same data) inside the TestResult.xml file. This is causing problems for AppVeyor to parse it. Looking at the spec (https://github.com/nunit/docs/wiki/Test-Result-XML-Format) there should only be a single test-run element.
If I switch to the 3.4.0-beta-2 package then the TestResult.xml file is as expected and can be parsed by AppVeyor.
I've attached my output and project.json - the output is produced by running the dotnet test command.
DuplicateRootTest.zip

The XML file you attached show a single test-run element.  Was the wrong file attached or is it another element that is causing problems?
Nonetheless, the issue may lie with the agent (https://github.com/nunit/nunit.portable.agent).  The most recent release of dotnet-test-nunit used an updated version of NUnitLite  To isolate the issue, build a local copy of dotnet-test-nunit from (https://github.com/dougkpowers/dotnet-test-nunit).  This fork has the latest dotnet-test-nunit changes, but still uses the old agent.  If it works, the issue is related to the agent (and you should open your issue within that project).  If it still doesn't work, then that would indicate the problem does actually like with dotnet-test-nunit, which would be odd.

Sorry about the wrong file, it was generated from the beta2 which worked.
I built the fork you mentioned and that produces the correct output so I'll close this issue and try to repro it in the nunit.portable.agent project.
Thanks for your help though in isolating the issue

Reopening, as although the portable agent change caused the problem, the fix might be best made here.
Previously the agent could only run one assembly at a time. This was changed for use in the xamarin runners, and to prevent that code needing to be duplicated in multiple places.
The dotnet-test runner (I believe) is still running assemblies one-by-one and amalgamating the results. I thought that would still stand up, however, looking again there are multiple different implementation of the ResultSummary and ResultReporter classes across projects, which may have confused me last time.
The most sensible fix, is probably to have the dotnet-test runner load and run all the assemblies together, and have the portable agent control this. I don't know how easily that will just slot in however. Alternatively, whichever resultsummary/resultreporter are in use here, could control merging test-runs, but the former seems more sensible.
I initially marked this pri:critical, although given the console/VS runner are unaffected, perhaps that was OTT. I'm not sure I'd have the time to put in a fix before next week, if anyone else is able to, please go ahead.

I can confirm that the dotnet-test-runner does run the assemblies one-by-one.  In other words, it tests one project at a time.  More accurately, the dotnet-test-runner is a slave of the dot net core test harness, which runs tests one project at a time.  That also is by design.  You can actually have different test runners for each project, which makes test configuration (and running) project specific rather than solution specific.  The dotnet-test command doesn't even have an option for running tests for more than one project at a time (https://docs.microsoft.com/en-us/dotnet/articles/core/tools/dotnet-test)
As a result, I do not believe it is feasible to have the dotnet-test runner load and run all the assemblies together.  Therefore, whenever there is another tool running tests across multiple projects, it will have to be responsible for merging the results.

@dougkpowers - if that's the case, then sounds like I'm barking up the wrong tree. 😄 I'm not familiar with dotnet tooling, just looking at the code in this repo.
https://github.com/nunit/dotnet-test-nunit/blob/master/src/dotnet-test-nunit/TestRunner.cs#L151
I was looking at the above method, which loops through _options.InputFiles and loads/runs each one. If, as I believe your suggesting, _options.InputFiles can only ever contain a single file, then what I was assuming is irrelevant.

@ChrisMaddock -- Ah yes, if you run the dotnet-test-nunit command directly then you can test multiple assemblies at once.  I was assuming that the dotnet-test-nunit runner would actually be invoked via the dotnet-test command, which in turn, runs dotnet-test-nunit.  In this scenario, I believe it would only test one project at at time.  Of course, I suppose you could have one test project with more than one test assembly (head starting to hurt).
So there are several scenarios to consider:
1- Two projects (one assembly each) with tests being invoked via dotnet-test
2- Two projects (one assembly each) with tests being invoked directly via dotnet-test-nunit
3- One project (multiple assemblies...suppose this is possible) with tests being invoked via dotnet-test (I suspect this may be a way to get dotnet-test to run tests across multiple assemblies in one run)

Have verified this - it also happens on every run, and isn't limited to cases with multiple assemblies.
Unfortunately it's possibly a little nontrivial - as the TestListeners in dotnet-test-nunit have the assembly path passed in, so setting up a single testlistener for everything may not work out. :-/ Meaning the better option may be to not use the ResultSummary as is done, in either agent, or dotnet-test-nunit.
Not sure yet, will try and have a look this weekend. Any thoughts, @rprouse?

Ok, I've dug further.
In an ideal world, the agent would take care of running multiple assemblies, however, this isn't possible with dotnet-test-nunit as each assembly requires it's own testlistener, for the line-number information etc. So instead, we'll need to keep running the input files individually in this runner, and the issue is just summarising the results accurately.
It's actually simpler than I first thought - there's just a bug in ResultSummary.cs in the agent, which doesn't correctly summarise multiple test-run elements. PR incoming for that, we'll then need to update this project to use a new agent.

Rather than trying to handle multiple test-run elements, I think you need to question why you have them in the first place. Consider that the standard nunit runners never have to deal with this situation. What's different in this runner that causes the situation to arise in the first place?

The latest agent now returns a full test-run rather than a test-suite - this allows it to run multiple assemblies, and prevents that functionality needing to be implemented in multiple runners.
Unfortunately dotnet-test-nunit currently needs to integrate on a per-assembly level, to provide correct code-navigation data. Therefore it still needs to run the assemblies one-by-one, and amalgamate the test-run nodes it now receives from the agent, rather than the test-suites it previously received.
The main point that persuaded me this was the right course of action, was that ResultSummary.cs already has partial functionality to amalgamate test-run's - it just had a bug. (See https://github.com/nunit/nunit.portable.agent/pull/16) I suppose the other way-around this would be to revert the agent changes to allow multiple assemblies, and instead re-implement the multiple-assembly code in the nunit.xamarin project, however, it does seem cleaner to me if the agent can take care of that.

I guess in many ways this is a discussion as to the role of the agent. Is it going to be a simple, version-agnostic pipe to the framework, or is it going to provide more functionality required in all runners, and work as a lightweight-'engine'?
I'd favour the latter - reduce the code we duplicate, and provide a simple clean possible interface to runners.

If it's a lightweight engine then life will be simpler I think if it works similarly to the engine. The engine returns multiple assembly results without use of a wrapping top-level element. Only the master test runner applies that final wrapper.
Is it the case that the engine was originally created as a simple wrapper that you're now trying to make into a more complete engine?
I'm interested in this because I'm hoping we'll someday merge all this back into the engine.

Sorry @CharliePoole - had to go back to work earlier! Will answer this with your other comment over on https://github.com/nunit/nunit.portable.agent/pull/16 - save us having the conversation over two different places!

@samcragg , you sure it works w/ beta2? I get nothing out of AppVeyor for beta2.
https://ci.appveyor.com/project/JohnKorsnes/nocommonsnet/build/1.0.25

@johnkors In my project.json I'm using "dotnet-test-nunit": "3.4.0-beta-2", and it works fine on my build, however, I am manually uploading the test results (detailed here), as the build didn't pick them up automatically. So in my build script I have this (in PowerShell) after running the tests:
$wc = New-Object 'System.Net.WebClient'
$wc.UploadFile("https://ci.appveyor.com/api/testresults/nunit3/$($env:APPVEYOR_JOB_ID)", (Resolve-Path .\TestResult.xml))

Here's the output:
https://ci.appveyor.com/project/samcragg/crest/branch/master/tests
The problem I had with beta3 was even manually uploading them didn't work, as there was an extra test-run element so their parser couldn't handle the input.
Hope it helps

Akward to talk to Appveyor - in a Appveyor build at Appveyor - thru their public API instead of it just.. working oob :) Ah well. I'll wait this one out, I think :)
Thx for the fix, though! :)


GCC and Clang not updating

Previously it seemed that GCC and Clang trunk versions were updated every night. However it now appears that they haven't updated since Dec 19th.  Is this intended? Should these still be updating nightly?

It is intended. Daily building is stopped now.
Daily building is heavy, and the server is same as Wandbox runtime server.
So, Wandbox is very slow while the server build compilers.
However gcc and clang is used by many users.
I put back only gcc and clang daily building.
the compilers will be updated within one day.
I'm trying separate building and runtimer server.
If it is completed, all daily building will be returned.

However gcc and clang is used by many users.
I put back only gcc and clang daily building.

Awesome! Thank you!
I work with a bunch of GCC and Clang developers and we really appreciate melpon.org having daily builds. It allows us to send compile results to other developers which may not have the newest compilers.

Closing since this has since been fixed.


feat: Add estimated instance warmup and ability to use deprecated marketplace images for ASG, change default PAN-OS versions to 10.1.12

Description
PR delivers changes:

in ASG module:

extend the ability to use deprecated marketplace images
introduce new variable scaling_estimated_instance_warmup used to define time time until a newly launched instance can contribute to the CloudWatch metric
update default VM-Series image to 10.1.12

in VM-Series and Panorama modules:

update default VM-Series & Panorama image to 10.1.12

in examples:

extend 3 autoscaling examples about variable scaling_estimated_instance_warmup
use VM-Series & Panorama image 10.1.12 in examples

Motivation and Context
Initially PR was raised because of #35, but while testing changes there were noticed problems with deprecated VM-Series & Panorama images, so in order to fully test changes there were required improvements in other modules and examples.
How Has This Been Tested?
Code was tested locally in the lab and via ChatOps.
Types of changes

New feature (non-breaking change which adds functionality)

Checklist

[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes if appropriate.
[x] All new and existing tests passed.

/idempotence paths="examples/centralized_design_autoscale examples/combined_design_autoscale examples/isolated_design_autoscale" tf_version="1.2"

/idempotence paths="examples/centralized_design_autoscale examples/combined_design_autoscale examples/isolated_design_autoscale examples/centralized_design examples/combined_design examples/isolated_design"


Build python 3k

Todo:

[x] call 'conda smithy rerender'

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@kynan I think the recipe is fine. The is issue is getting the build servers to top acting up.
We can try to force the rebuild some other time, perhaps during the day when it is not too busy.

@sodre seems it has got even worse, rebuild has been queued for 8h now...

We will need to wait until the whole readd processing is finished :(
This will get better.
Sent from my iPhone

On Aug 29, 2017, at 11:28 AM, Florian Rathgeber<EMAIL_ADDRESS>wrote:
Merged #1.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Include "Strategy rewards" disclaimer on Vaults page

Improvement suggestion:
Include a "Strategy rewards" disclaimer at the bottom of the vaults page that explain how we reward strategists. A call to action for people to write strategies for Yearn per se.
Example on NEAR protocol website

I like this idea - is there docs on what the rewards are? If not, it can link to a new page in the docs and incorporate @x48-crypto starter pack on https://gov.yearn.finance/t/request-for-knowledge-base-howto-learning-steps-for-becoming-a-strategy-writer/7007


"Cannot convert undefined or null to object" with postcss-simple-vars

The error occurs when the globalVariables option is also in use and the postcss-simple-vars config is empty or has an empty fileOptions array:
"postcss-simple-vars": { },
"postcss-simple-vars": {
  "fileOptions": [  ]
},

I've stumbled upon this problem too. Is there any workaround? My current config is like this:
  "cssModules": {
    "postcssPlugins": {
      "postcss-import": {},
      "postcss-mixins": {},
      "postcss-each": {},
      "postcss-cssnext": {},
      "postcss-simple-vars": {
        "fileOptions": ["style-globals.json"]
      },
      "postcss-modules-local-by-default": {},
      "postcss-modules-extract-imports": {},
      "postcss-modules-scope": {}
    },
    "ignorePaths": [
      "node_modules"
    ],
    "explicitIncludes": [
      "node_modules/react-toolbox/lib"
    ],
    "extensions": [
      "scss",
      "css"
    ],
    "globalVariables": [
      "style-globals.json"
    ]
  }

And style-globals.json is:
{
  // colors
  "color-white-two": "#f5f5f5"
}

I get the same error you mentioned. As you can see, I tried to add fileOptions, so it isn't empty, but error stays.

I've tried to remove globalVariables, leaving only fileOptions, but it's all the same.

Actually, I get same error whenever I try to use explicitIncludes for react-toolbox. and ignorePaths on whole node_modules folder. Simple-vars configuration is irrelevant.

And I try to use explicitIncludes instead of just including whole node_modules without tests, because of very long compilation time if I do that.

So, when I do that:
 25   "cssModules": {
 26     "postcssPlugins": {
 27       "postcss-import": {},
 28       "postcss-mixins": {},
 29       "postcss-each": {},
 30       "postcss-cssnext": {},
 31       "postcss-simple-vars": {},
 32       "postcss-modules-local-by-default": {},
 33       "postcss-modules-extract-imports": {},
 34       "postcss-modules-scope": {}
 35     },
 36     "extensions": [
 37       "scss",
 38       "css"
 39     ],
 40     "ignorePaths": [
 41       "node_modules"
 42     ],
 43     "explicitIncludes": ["node_modules/react-toolbox/lib"]
 44   }

I get that:
=> Errors prevented startup:

   While processing files with nathantreid:css-modules (for target web.browser):
   native: Not a string or buffer
   at TypeError (native)
   at Hash.update (crypto.js:70:16)
   at sha1 (packages/mss/sha1.js:5:8)
   at IncludedFile.getSourceHash (packages/mss/included-file.js:76:12)
   at CssModulesBuildPlugin.getCacheKey (packages/mss/css-modules-build-plugin.js:268:47)
   at packages/caching-compiler/multi-file-caching-compiler.js:91:55
   at Array.forEach (native)
   at CssModulesBuildPlugin.processFilesForTarget (packages/caching-compiler/multi-file-caching-compiler.js:88:16)
   at CssModulesBuildPlugin.processFilesForTarget (packages/mss/css-modules-build-plugin.js:58:5)

Any ideas on how could I use explicitIncludes? Because including whole node_modules leads to very slow compilation time.

There's a bug in explicitIncludes; I'll publish a fix later, but explicitIncludes is really a holdover from the days before Meteor supported importing files from node_modules. I'd recommend modifying your ignorePaths option instead to the following regular expression which will ignore all node_modules except the react-toolbox/lib folder:
    "ignorePaths": [
      "node_modules/(?!react-toolbox/lib)"
    ]


Options Documentation in README

For options README gives this example:
// webpack.config.js
{
  loader: 'worker-loader',
  options: { fallback: false }
}

But that doesn't look like a webpack.config.js. Can you please give us more of a hint as to where this goes in the webpack config file?

Close in favor https://github.com/webpack-contrib/worker-loader/issues/253


Create an abstract Constraints class to support different types of constraints via inheritance

Task
Create an abstract interface for different types of constraints supported in OpenTurbine.
Why
To treat the constraints uniformly as member of the base class, rather than duplicating code to acknowledge the different types.
Done means

[ ] Refactoring of the constraints classes to establish an inheritance hierarchy
[ ] Unit tests exist for all derived classes

I gave this a bit more thought and I don't think the inheritance based approach will work well with the Kokkos parallelism. If we could define a vector of Constraint type, it would be a good solution, but inevitably we'll need all the data to generate Phi and B in the GPU and we won't want to copy that in at every iteration. I do think this may be a great opportunity to define a View of Constraint structs that we can do a parallel_for over. Let's get together and come up with a list of constraint types that the struct will need to implement.


Added options table for some event funcs

I have added the options table for

$oldRole
$oldMember
$newMember

Also edited the $newRole to add id, name to options table.
I hope nothing is wrong here.
Thanks

Thanks for the contribution.


patch-shebangs: respect cross compilation for 18.09

Motivation for this change
This is a version of https://github.com/NixOS/nixpkgs/pull/43833 made more conservative to only affect cross builds (well, anything enabling strictDeps). I hope that makes it conservative enough to land in 18.09. Sorry I didn't make this earlier, pre-fork.
The idea is that if strictDeps isn't defined, HOST_PATH is defined exactly the same as PATH. This means that patchShebangs, patchShebangs --build, and patchShebangs --host are all defined the same as each other and as patchShebangs is today.
I still like @matthewbauer's version for staging and 19.03 and beyond. The breakage it creates points us to things worth fixing, just not as part of the 18.09 deadline!
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

Timed out, unknown build status on x86_64-linux (full log)
Attempted: stdenv
Partial log (click to expand)
cannot build derivation '/nix/store/5nlybjij7qvxaf9wj8zmd06j4f1fksj6-help2man-1.47.6.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/z8ihiai14dik7af92k18a4ymygmvxksa-binutils-wrapper-2.30.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/hbcf7dzg9ajhkwsvx9cxjp143w02814q-diffutils-3.6.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/1zkyfc7cmkd6lg475777m3kjbm6y19ra-findutils-4.6.0.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/11cc22sh46nv3qfyv6b0mbf31chz724d-libtool-2.4.6.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/0ax7048h5k873ghkgj22nzdarw215xh4-gcc-wrapper-7.3.0.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/vxhj0jwm82dbw43bpykalzbmifgv1xpy-hook.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/hnjimxn482yismhqqic3psvvp5f4in86-patch-2.7.6.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/kvz4sdp8s9xd4bcy1wkv4xqx3lqfnkas-stdenv-linux.drv': 23 dependencies couldn't be built
error: build of '/nix/store/kvz4sdp8s9xd4bcy1wkv4xqx3lqfnkas-stdenv-linux.drv' failed

Maybe we should merge #43833 first just to make sure the changes work. I don't want to break patch shebangs in 18.09. This can be backported a little bit later.

@matthewbauer err you mean merge this into staging first? Your can indeed break native builds, but this is only capable of breaking cross builds which somehow relied on the broken behavior.

Success on aarch64-linux (full log)
Attempted: stdenv
Partial log (click to expand)
shrinking /nix/store/47wvfxxmipwzsjhbr7qp39vjm0wai0q6-findutils-4.6.0/bin/find
gzipping man pages under /nix/store/47wvfxxmipwzsjhbr7qp39vjm0wai0q6-findutils-4.6.0/share/man/
strip is /nix/store/8zbl35kgg8v7gircl3pvy9027vslll1q-bootstrap-tools/bin/strip
stripping (with command strip and flags -S) in /nix/store/47wvfxxmipwzsjhbr7qp39vjm0wai0q6-findutils-4.6.0/libexec  /nix/store/47wvfxxmipwzsjhbr7qp39vjm0wai0q6-findutils-4.6.0/bin
checking for references to /build in /nix/store/47wvfxxmipwzsjhbr7qp39vjm0wai0q6-findutils-4.6.0...
shrinking RPATHs of ELF executables and libraries in /nix/store/mfg6a2bmwjyj79w1f3s4813szixi337f-findutils-4.6.0-info
strip is /nix/store/8zbl35kgg8v7gircl3pvy9027vslll1q-bootstrap-tools/bin/strip
checking for references to /build in /nix/store/mfg6a2bmwjyj79w1f3s4813szixi337f-findutils-4.6.0-info...
building '/nix/store/kwgrkg6z99nq9j2flashhc9jl0gbk207-stdenv-linux.drv'...
/nix/store/syn3p6a0xk1livqsqv41avdddh7660ww-stdenv-linux

Timed out, unknown build status on x86_64-linux (full log)
Attempted: dhcpcd, stdenv
Partial log (click to expand)
cannot build derivation '/nix/store/5kb2175p39bi3j41cl16kxv0nnw62izz-meson-0.46.1.drv': 10 dependencies couldn't be built
cannot build derivation '/nix/store/kzxsm8b0908952w9g7n4wg25h203qvk8-python3.6-lxml-4.2.4.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/f6zwwvpvinm4zq512g987gs3wc7l5b0d-gnome-doc-utils-0.20.10.drv': 10 dependencies couldn't be built
cannot build derivation '/nix/store/fh8jsrambn0aq06rvigyz87vb6kghsqg-python3-3.6.6-env.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/g8mi9wp6sn9lnczqb6qx3sqbjgm625z5-shadow-4.6.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/lpx53k26nfx9h1jc9bcyh3hjzv1j0l9k-util-linux-2.32.1.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/ypx34axxbd3xqv9j936l3flb0p8zy716-glib-2.56.0.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/ajn3f20hd6nmkf6vbbxhx475bwwm14sk-systemd-239.drv': 42 dependencies couldn't be built
cannot build derivation '/nix/store/qkj11c06is3p2a1w0kdny4clk7q5aqk5-dhcpcd-7.0.8.drv': 4 dependencies couldn't be built
error: build of '/nix/store/kvz4sdp8s9xd4bcy1wkv4xqx3lqfnkas-stdenv-linux.drv', '/nix/store/qkj11c06is3p2a1w0kdny4clk7q5aqk5-dhcpcd-7.0.8.drv' failed

Success on aarch64-linux (full log)
Attempted: dhcpcd, stdenv
Partial log (click to expand)
shrinking /nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8/sbin/dhcpcd
gzipping man pages under /nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8/share/man/
strip is /nix/store/830hkkm6q88wx7zfrilbkl9xmv5n8yrg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8/lib  /nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8/libexec  /nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8/sbin
patching script interpreter paths in /nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8
/nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8/libexec/dhcpcd-run-hooks: interpreter directive changed from "/bin/sh" to "/nix/store/1sdylxi5pq4ja5dr5g4m83bv1m3hc92f-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8...
moving /nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8/sbin/* to /nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8/bin
/nix/store/a0pk7218d5skq55yg8a4sp820l22z9zx-dhcpcd-7.0.8
/nix/store/syn3p6a0xk1livqsqv41avdddh7660ww-stdenv-linux

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: stdenv
Partial log (click to expand)
[ 56%] Building CXX object lib/Target/Hexagon/CMakeFiles/LLVMHexagonCodeGen.dir/HexagonCFGOptimizer.cpp.o
[ 57%] Building CXX object lib/Target/Hexagon/CMakeFiles/LLVMHexagonCodeGen.dir/HexagonCommonGEP.cpp.o
[ 57%] Building CXX object lib/Target/Hexagon/CMakeFiles/LLVMHexagonCodeGen.dir/HexagonConstPropagation.cpp.o
[ 57%] Building CXX object lib/Target/Hexagon/CMakeFiles/LLVMHexagonCodeGen.dir/HexagonCopyToCombine.cpp.o
building of '/nix/store/dzbnwpxv7xwhr2yicsd44ax9mxmpa5rd-llvm-5.0.2.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/838bnnmcj14kibbfr7z3w0yvyik5nd8k-clang-5.0.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/3f0agwbd4842fvhck86hl4c4kydp2zxz-compiler-rt-5.0.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/724bry6jw2a8vb0abq6gxr4l82jg0cad-clang-wrapper-5.0.2.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/z9xdq92n2p9hbzkq1zqdj0fw5gni020d-stdenv-darwin.drv': 4 dependencies couldn't be built
error: build of '/nix/store/z9xdq92n2p9hbzkq1zqdj0fw5gni020d-stdenv-darwin.drv' failed

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: stdenv
The following builds were skipped because they don't evaluate on x86_64-darwin: dhcpcd
Partial log (click to expand)
[ 66%] Building NVPTXGenSubtargetInfo.inc...
[ 66%] Updating NVPTXGenSubtargetInfo.inc...
[ 66%] Built target NVPTXCommonTableGen
Scanning dependencies of target LLVMNVPTXCodeGen
building of '/nix/store/dzbnwpxv7xwhr2yicsd44ax9mxmpa5rd-llvm-5.0.2.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/838bnnmcj14kibbfr7z3w0yvyik5nd8k-clang-5.0.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/3f0agwbd4842fvhck86hl4c4kydp2zxz-compiler-rt-5.0.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/724bry6jw2a8vb0abq6gxr4l82jg0cad-clang-wrapper-5.0.2.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/z9xdq92n2p9hbzkq1zqdj0fw5gni020d-stdenv-darwin.drv': 4 dependencies couldn't be built
error: build of '/nix/store/z9xdq92n2p9hbzkq1zqdj0fw5gni020d-stdenv-darwin.drv' failed

OK I think I see. It's fine if staging breaks a little since we want to fix the misbehaving packages anyways, and we still get some sanity checking of does the code do the right thing. :+1:.

Alright!

Changed the order so that https://github.com/NixOS/nixpkgs/pull/46542 for regular staging can share a commit.

Timed out, unknown build status on x86_64-linux (full log)
Attempted: dhcpcd, stdenv
Partial log (click to expand)
cannot build derivation '/nix/store/5kb2175p39bi3j41cl16kxv0nnw62izz-meson-0.46.1.drv': 10 dependencies couldn't be built
cannot build derivation '/nix/store/kzxsm8b0908952w9g7n4wg25h203qvk8-python3.6-lxml-4.2.4.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/f6zwwvpvinm4zq512g987gs3wc7l5b0d-gnome-doc-utils-0.20.10.drv': 10 dependencies couldn't be built
cannot build derivation '/nix/store/fh8jsrambn0aq06rvigyz87vb6kghsqg-python3-3.6.6-env.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/g8mi9wp6sn9lnczqb6qx3sqbjgm625z5-shadow-4.6.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/lpx53k26nfx9h1jc9bcyh3hjzv1j0l9k-util-linux-2.32.1.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/ypx34axxbd3xqv9j936l3flb0p8zy716-glib-2.56.0.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/ajn3f20hd6nmkf6vbbxhx475bwwm14sk-systemd-239.drv': 42 dependencies couldn't be built
cannot build derivation '/nix/store/qkj11c06is3p2a1w0kdny4clk7q5aqk5-dhcpcd-7.0.8.drv': 4 dependencies couldn't be built
error: build of '/nix/store/kvz4sdp8s9xd4bcy1wkv4xqx3lqfnkas-stdenv-linux.drv', '/nix/store/qkj11c06is3p2a1w0kdny4clk7q5aqk5-dhcpcd-7.0.8.drv' failed

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: stdenv
The following builds were skipped because they don't evaluate on x86_64-darwin: dhcpcd
Partial log (click to expand)
cannot build derivation '/nix/store/34w061dgh6rb31lhs60mg93v82qh1arb-cctools-port-895.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/knh9nayqr6y15r2mq3gzqvlhakh3kk28-hook.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/ygc58kc2xzf3vaxn98ygzd4rm8qp7fci-ICU-osx-10.10.5.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/806gwymraxmd8favdz3qs13c0n79fvsh-cctools-binutils-darwin.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/cfk18hqiw8y0h9fw6inj7ivdzbxg7dk7-gnutar-1.30.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/dylfb5nmsmczaih39crprqg91nzlgjk8-CF-osx-10.10.5.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/k7mrps05qnxvlghh2xg3ji0pdf3ssylc-cctools-binutils-darwin-wrapper.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/724bry6jw2a8vb0abq6gxr4l82jg0cad-clang-wrapper-5.0.2.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/z9xdq92n2p9hbzkq1zqdj0fw5gni020d-stdenv-darwin.drv': 36 dependencies couldn't be built
error: build of '/nix/store/z9xdq92n2p9hbzkq1zqdj0fw5gni020d-stdenv-darwin.drv' failed

@Ericson2314 Looking at this now, I think I have found a bug in this. Lots of packages have bash scripts in their outputs but don't directly list bash as an input. Instead they get it from initialPath. But initialPath goes into PATH but not HOST_PATH. We need to find a way to make sure that a runtime Bash gets in HOST_PATH. I think defaultBuildInputs is the easiest way to go.
But for now, this will break in unexpected ways. I am going to revert this in staging-18.09 just to be safe.

 Sure complicates everything. Good catch


color of procedures in types that share name with intrinsic function

Hi there,
When one writes procedures in types, and when this procedure has the name of an intrinsic function, coloration is wrong. See example below:

log should be white.
It seems to me that any word preceded by % should be considered as non-intrinsic.
Best wishes,

I'm pretty sure I can modify either the intrinsic function definition or the variable definition to not mark functions following % as being intrinsic. I'll see what I can do tonight.

This seems to be not only true for intrinsic procedures (see log example above), but also for kinds, like real, int, etc.

Thanks @tomedunn  :).

No problem @maxlevesque. If you're feeling adventurous be sure to try the new Fortran - Free Form grammar. In principle it should work almost identically to the Fortran - Modern grammar with some minor differences. It highlights all of my static test programs perfectly but sometimes bugs only pop up when actively typing.


[Proposal] switch to camelCase for function and variable names

Hello. Thanks for the great library. One thing that bothers me is that most of the code is written with underscore style which is not so widely adopted code style in the JS world. Can you consider moving to cameCase for function and variable names? Also, it will be good idea to set up eslint with some community adopted style guide such as Airbnb JavaScript Style Guide. Thanks.

@aganov Thanks for your feedback! We really appreciate your concern over code standards :)
I do agree that the style used in non-standard in JavaScript, and it sure is a possible reason that may make using it in other projects difficult. This project was actually an outcome of something we ourselves needed in our product, which had a different code style. Seeing that it was easy to use, we worked the best we could to release it as a potential library; unfortunately amongst planning out the arch and builds, changing the style didn't gain as much priority. There are quite a few things missing that'd make it a perfect project (tests, docs ...), and during these initial stages, we are working on getting them done :)
Even so, changing names is a straightforward change if planned, given the small size of the project; and we'd sure appreciate help :) (the utils would be good place to start).

Some progress, utils are out of the way. The main code base will be after refactoring.

The code base just went through a rewrite, with the release of v1. A style guide would surely be the next step, contribution guidelines are on the way. Thanks for the review :)


Add mini chartbot to the website.

it gives Answers of users questons and give fast resoonse to the users

@ruchikakengal I’ve assigned this issue to you. Please go ahead and start working on it.

can you assign this issue to me

@ruchikakengal Thanks for creating the issue in BuddyTrail!!! The issue has been assigned to you.
Before you start working on your PR, please make sure to:

⭐ Star the repository if you haven't already.
Pull the latest changes to avoid any merge conflicts.
Attach before & after screenshots in your PR for clarity.
Include the issue number in your PR description for better tracking.

Contributors will start at Level 1, and their level will increase based on the quality and quantity of their contributions. The more effort and value you bring, the faster you'll progress. Put forth your best effort to unlock new levels and opportunities!
I'm excited to see your contribution as part of GSSOC EXTENDED 2024! 🎉
Don't forget to follow me on GitHub for more updates.
Happy open-source contributing! 🚀


Road to v0.20.0rc

We've got some:

bugs to squash
dependencies to sort out
backwards compatibility to mettle-test
nearly-there performance improvements to ship

@kwigley can you add a list of what additional items that aren't feature work here please?


[Relay][Frontend][ONNX] Add ConvInteger support and fix some ConvTranspose padding bugs.

While playing with onnxruntime's quantization tools I found that ConvInteger nodes were heavily used and pretty easy to map to qnn.conv2d. This PR adds support for that op.
While working with convolutions, I found some unrelated issues in how we were doing autopadding for ConvTranspose. Specifically, padding can't always be treated as a two step process where inputs are padded and then conv_transpose is performed since padding in conv_transpose actually removes outputs. I simplified the autopadding ConvTranspose and found that this new implementation passes more of the onnx node tests.

@mbrookhart @AndrewZhaoLuo can you guys take a look at this PR?

I'm having trouble getting the docker images in CI updated due to a TF update.

@mbrookhart that makes sense, I've removed all changes to convtranspose from this PR.

Thanks @jwfromm @AndrewZhaoLuo


Remove listener module

Description
Remove listener module
Fixes
https://github.com/wso2-enterprise/choreo/issues/13186
https://github.com/ballerina-platform/ballerina-extended-library/issues/407
Please delete options that are not relevant.

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Security checks

[x] Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
[x] Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

Do we need to remove https://github.com/Chuhaa/module-ballerinax-sfdc/blob/main/salesforce/metadata/sfdc.json#L770 too

Do we need to remove https://github.com/Chuhaa/module-ballerinax-sfdc/blob/main/salesforce/metadata/sfdc.json#L770 too

@SkNuwanTissera Do you think still this metadata json is used by someone?
If not we can remove it.


Trigger benchmarking with Bors commands

Turing's benchmarking is not used often at the moment. I think part of the reason is that the benchmarking process is a bit complicated, even with Nanosoldiers. Would it make sense to try to

trigger benchmarking for PRs using bors bot, with a customised command (see below)
replace Nanosoldier with PkgBenchmark , which is designed specifically for track performance changes of Julia packages.

Ps: some references:

bors try arguments: these arguments are stored as commit message, and can be extracted by the benchmarking script.
perhaps: bors try --benchmarking?

Maybe https://github.com/tkf/BenchmarkCI.jl could be useful. The trigger of the Github action could be adjusted to whatever we think would be suitable.

Closed in favour of https://github.com/TuringLang/DynamicPPL.jl/pull/346


about the play store

I have a doubt, I understand that the project is open source and the license allows commercial use.
Is this project compatible to upload to the play store?
Are there any known problems or incompatibilities that do not allow the application to reach the play store successfully?
If there are cases of success it would also be good to share them.
I really appreciate your answers.

you can easily upload the app to the play store under your signature.
there are few issues reported regarding store publishing, you can look here - #114 #49 #118


OSC Leap motion not working together with a Max Patcher with udpreceiver

Hi guys,
Great device ! Thanks ! Everything works just find.
However, I fail to make it work together: Ableton with Osc leap motion + A max Patcher receiving the same OSC port from ManosOsc. It either works only one side. But when I open the device in edit mode inside Max, both patcher receive the OSC messages. So, it must be possible as I desired, am I correct ?  Any advice will be much appreciated.
Cheers.
Alois.

Hi aloisyang,
We will soon be disabling this 'Issues' section, since the page is not regularly monitored.
If the OSC Leap Motion issue persists, please contact Ableton Support and we'll be happy to help.
Best regards,
Lillia
Max for Live Content Specialist


distutils deprecation (in Python 3.10)

distutils is deprecating in Python 3.10 so we should get ready for it.
https://www.python.org/dev/peps/pep-0632/
NumPy: https://github.com/numpy/numpy/issues/18588
SciPy: https://github.com/scipy/scipy/issues/13615
Thanks @leofang for letting us know 😄

SciPy has been successfully built with the new build system Meson: https://labs.quansight.org/blog/2021/07/moving-scipy-to-meson/

Python 3.10.0 stable release is planned on 2021-10-04.
Currently, most of distutils hacks in cupy_setup_build.py is to run nvcc from within the Extension build process.
I'm currently assuming we can avoid (direct) use of distutils only by changing the build order as follows:

Compile *.cu files as CUDA object files using NVCC. This is done by our script (maybe in custom_build_ext).
Pass the above object files to extra_objects argument of setuptools.Extension.
Run setuptools.setup() and let setuptools build Python modules and link CUDA object files.

I feel using an external build system is overkill for step 1., as it is quite simple. The only thing we have to implement on our own is to compare the timestamp between *.cu and *.o to avoid building it when the file is not modified.

Use of distutils has been removed from CuPy modules (cupy, cupyx and cupy_backends) in #6025.
https://github.com/cupy/cupy/issues/4983#issuecomment-915357337 has been implemented in #6273.

The remaining distutils usages are in the installer. So far they have no replacement in setuptools.

install/cupy_builder/_compiler.py: distutils.ccompiler.gen_preprocess_options -> Very simple logic, so I think it's better to implement it on our own.
install/cupy_builder/cupy_setup_build.py: distutils.{ccompiler,sysconfig} -> Maybe keep it as-is...
install/cupy_builder/install_build.py: distutils.util.split_quoted -> Rewrite with shlex


2.0.0-beta.2 fails to new Stage

TODO

[x] Is this a question or bug? Stack Overflow is a much better place to ask any questions you may have.

[x] Did you search the issues to see if someone else has already reported your issue? If yes, please add more details if you have any!

[x] If you're using an older version, have you tried the latest?

[ ] If you're requesting a new feature; provide as many details as you can. Why do you want this feature? Do you have ideas for how this feature should be implemented? Pseudocode is always welcome!

Issue Details

Version used (Ex; 1.0):
2.0.0-beta.2

Describe whats happening (Include any relevant console errors, a Gist is preferred for longer errors):

import { Stage } from '@createjs/easeljs';

export default class Canvas {
    constructor() {
        this.stage = new Stage('canvasId');
    }
}

Error:
easeljs.module.js:1904 Uncaught TypeError: Illegal constructor
    at createCanvas (easeljs.module.js:1904)
    at<EMAIL_ADDRESS>(easeljs.module.js:3160)
    at __webpack_require__ (bootstrap 8cba5b6e973429fc89a0:678)

code where throw error
function createCanvas(width = 1, height = 1) {
  let c;
  if (window.createjs !== undefined && window.createjs.createCanvas !== undefined) {
    c = window.createjs.createCanvas();
  }
  if (HTMLCanvasElement) {
    // this line throw error "Illegal constructor"
    c = new HTMLCanvasElement();
  }
  if (c !== undefined) {
    c.width = width;
    c.height = height;
    return c;
  }
  throw "Canvas not supported in this environment.";
}

OS & Browser version (Please be specific) (Ex; Windows 10 Home, Chrome 62.0.3202.94):
Chrome Version 69.0.3497.100 (Official Build) (64-bit)

Do you know of any workarounds?
HTMLCanvasElement is sub interface of HTMLElement, it should not be used as constructor

Provide any extra details that will help us fix your issue. Including a link to a CodePen.io or JSFiddle.net example that shows the issue in isolation will greatly increase the chance of getting a quick response.

This my pr for this issue.
https://github.com/CreateJS/EaselJS/pull/988#issue-219197170

Fixed in beta.4


2.0 quarkus.quartz.store-type=db should be replaced with quarkus.quartz.store-type=jdbc-cmt

The deprecated config value StoreType.DB was removed. quarkus.quartz.store-type=db should be replaced with quarkus.quartz.store-type=jdbc-cmt

Fixed by: https://github.com/openrewrite/rewrite-quarkus/commit/7ea7d5b7cb9e034381a047143e8b49f258afadfb


Router switch example should be converted to a suite of tests

Context from @hgzimmerman:

Come to think of it, the switch example really isn't an example and is more of a mediocre/manual test suite. Its not meant to be ran in the browser.
I think it should be converted into a test/ directory instead - but that's outside of the scope of this PR.

I guess I'll take care of this in #1559. I intended to remove it entirely first but reusing it as a test makes sense.