[SPARK-9504][Streaming][Tests]Fix o.a.s.streaming.StreamingContextSuite.stop gracefully again

The test failure is here: https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-SBT/3150/AMPLAB_JENKINS_BUILD_PROFILE=hadoop1.0,label=centos/testReport/junit/org.apache.spark.streaming/StreamingContextSuite/stop_gracefully/
There is a race condition in TestReceiver that it may add 1 record and increase TestReceiver.counter after stopping BlockGenerator. This PR just adds join to wait the pushing thread.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #217 has started for   PR 7934 at commit cfd7973.

Merged build triggered.

Merged build started.

Test build #39784 has started for   PR 7934 at commit cfd7973.

Test build #39784 has finished for   PR 7934 at commit cfd7973.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test build #217 has finished for   PR 7934 at commit cfd7973.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

LGTM.

Thanks @zsxwing, merged in master and branch-1.5


How to Install Software

I'm trying to debug a HandBrake issue and I wanted to try running a later version through Conty than what I can run on my host distro due to older libraries. I'm not too familiar with Arch, but found pacman -S handbrake complains that I'm not root. Both sudo and su seem to not be configured.
Is it possible to install software like HandBrake to the conty system? I suppose I'm fine also compiling manually, but I wouldn't be able to install it to the system without root.
Also, does root work within the container? If so, how do I become root or gain root privileges?
Thanks for the great container! I use it most days for steam (I didn't want to take my host distro multilib).

Hi,
Yes, installing packages is possible by using the -u argument. For example, to install handbrake: ./conty.sh -u handbrake.
Removing packages is also possible by adding minus sign before package names. Te remove handbrake:  ./conty.sh -u -handbrake.
Using just -u without any additional arguments will just update all packages inside the container.
This will take some time because the whole image need to be rebuilded. After that you can run handbrake (handbrake binary name is ghb):  ./conty.sh -u ghb

Perfect!
I'm assuming this is unique to each release I download? So if I need this in a future release, I would need to rerun the command against that conty release?
Also, if I am adding HandBrake in future releases, does it matter if I use the regular or lite versions of conty? I remember seeing the lite removes things like gcc, meson, cmake, etc. When I install software, would it need to download those packages or is that done outside of the container?

So if I need this in a future release, I would need to rerun the command against that conty release?

Yes, you would need to rerun the command against each new release. The command only affects the file against which you execute it.

Also, if I am adding HandBrake in future releases, does it matter if I use the regular or lite versions of conty? I remember seeing the lite removes things like gcc, meson, cmake, etc.

No, it doesn't matter what version to use.

I remember seeing the lite removes things like gcc, meson, cmake, etc. When I install software, would it need to download those packages or is that done outside of the container?

It's done inside the container, it would download software you install each time for each new release. Gcc, meson, cmake and others won't be downloaded and installed to the lite version unless software you install depend on them or you explicitly specify them.


fix(tekton): final GA review changes

Signed-off-by: Brian Gleeson<EMAIL_ADDRESS>PR summary
Final review of API has resulted in the following changes

Remove offset option from API docs, when fetching pipeline runs
Remove default values for booleans in PATCH requests
Clean up related Strings for the above

PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

:tada: This PR is included in version 0.1.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


site seems to be down

giving me an ERR_TIMED_OUT when trying to load the site

+1

+1

back up


Other to do items before submission

[ ] Discuss prospects for RV and astrometry follow-up

[ ] Quantitatively compare to other survey results

[ ] Add a corner plot to the section about parameter estimation

[ ] Discuss potential for the discovery of moons, rings, Trojans, etc.

[ ] Send to co-authors for comments

[ ] Send to friends for comments

A few more suggestions:

[ ] Label the y-axis of the signals in Figure 1
[ ] Include some discussion about the potential scientific interest of the "box" signals.  Some of these could very well be secondary eclipses of WDs, that would be super-easy to find with a very modest level of RV follow-up! For how many signals is the box model is the best explanation?  These might even be worth a separate table.
[ ] Label the units of the y-axis (at least in the first column) in Figure 3.
[ ] In the OR section (or conclusion), mention/discuss the implied integrated occurrence rate over the two bins---something like 1.5-2 planets per star?  This is interesting because (a) the Solar System has 2, and (b) it maybe jives with microlensing searches finding lots of sub-Jupiters on longer periods (would need to check references for this)?  This is good to connect with because most people don't have intuition for a differential rate in log units.
[ ] Table 6 should also have the epoch, as well as the period, for observers' convenience.

Thanks. Added to the list.

The square ones would be worth searching for candidate microlensing events.
Eric Agol
Astronomy Professor
University of Washington

On Jul 15, 2016, at 2:26 PM, Timothy Morton<EMAIL_ADDRESS>wrote:
A few more suggestions:
Label the y-axis of the signals in Figure 1
Include some discussion about the potential scientific interest of the "box" signals. Some of these could very well be secondary eclipses of WDs, that would be super-easy to find with a very modest level of RV follow-up! For how many signals is the box model is the best explanation? These might even be worth a separate table.
Label the units of the y-axis (at least in the first column) in Figure 3.
In the OR section (or conclusion), mention/discuss the implied integrated occurrence rate over the two bins---something like 1.5-2 planets per star? This is interesting because (a) the Solar System has 2, and (b) it maybe jives with microlensing searches finding lots of sub-Jupiters on longer periods (would need to check references for this)? This is good to connect with because most people don't have intuition for a differential rate in log units.
Table 6 should also have the epoch, as well as the period, for observers' convenience.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Are there even any known non-astrophysical effects in the data that will create square signals?  If not, these are all of interest.

The vast majority are non-physical. A box + GP can fit a lot of things!

I think that it's opening a whole can of worms to go down the path of trying to understand the distribution of non-transit signals and I'm really not set up to do that right now. Perhaps Figure 1 is misleading because most signals that are best fit by the box don't look quite so distinctly box-shaped!  I think that a more careful job would have to be done to try to get a sample to follow up.

Fair enough.  Are there at least a few large SNR box signals that are sitting in a table somewhere that you could point out?  No need to do anything comprehensive/systematic...


contrib/raftexample: save snapshot to WAL first

Save the snapshot index to the WAL before saving the snapshot to the
filesystem. This ensures that wal.Open is only ever called with a
snapshot that was previously saved to the WAL.
Fixes #8082.

@jbowens LGTM. Thanks!
/cc @xiang90 @heyitsanthony

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3993f37). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #8088   +/-   ##
=========================================
  Coverage          ?   76.55%
=========================================
  Files             ?      342
  Lines             ?    26568
  Branches          ?        0
=========================================
  Hits              ?    20340
  Misses            ?     4773
  Partials          ?     1455

Continue to review full report at Codecov.

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


Data.bin is not working correctly

Related to #9
Since some of the values are close together, but within tolerances, attempting to sort Q is not successful. Instead, each column needs to be sorted separately to use the np.searchsorted() function.

Addressed by 357e8db3edb4254d6f7a425d343780989333858d


rebuild for updated dependencies

scotch 6.0.7, libgfortran 4

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.


AudioUnits plugin broken.

I downloaded the macOS AU 1.0.0 version of the plugin and tried it on Ableton 10.1.42, Ableton 11.0.10, and Reaper 6.53.
The plugin is available to the host application but not able to load it.
Ableton error message

In Reaper the plugin can't be activated once in a track

I checked the logs of the Ableton session and got:
2022-05-13T14:14:49.301615: info: Au: Going to create: DDSP Effect
2022-05-13T14:14:49.311306: error: Au: Failed: DDSP Effect
2022-05-13T14:14:49.445141: info: MemoryUsage: V: 6.4 GB, R: 601.5 MB, P: 0 Bytes
2022-05-13T14:15:04.385984: info: Au: Going to create: DDSP Synth
2022-05-13T14:15:04.392137: error: Au: Failed: DDSP Synth

Any insights?
Thank you.

Thanks for letting us know, and sorry it's not working for you. Could you provide more information about the OS? We're collecting a table of configurations that work and don't yet work in https://github.com/magenta/ddsp-vst/blob/main/Builds.md.
We've seen it work on M1 + Intel Macs for OSX 12.3.1 but it's possible there may be some signing issues for earlier OSs.

Yeah, I forgot to add that :)
macOS 10.15.7
Thank you!

Hello! Adding to the thread, I am running into a similar issue:

macOS 11.2.3; 2018 Intel MacBook Pro; Ableton Live Suite 11.1.1
I'm planning to update my macOS version in a few weeks, so I'll post an update if that fixes it.
Thanks again for making this! Really looking forward to getting it up and running for some creative projects.

Thanks for providing this info! Could you also add it to Builds.md so that we can keep track? Thanks!

I have the same thing on my Mojave machine (10.14.16 - intel)
This is what the console prints at the moment of the error:

It works fine on my Monterey (12.0.1 - intel) system

Adding as well, AU isn't passing auval
Error Message:
validating Audio Unit DDSP Effect by Magenta:
AU Validation Tool
Version: 1.8.0
Copyright 2003-2019, Apple Inc. All Rights Reserved.
Specify -h (-help) for command options

--------------------------------------------------
VALIDATING AUDIO UNIT: 'aufx' - 'Ranj' - 'Mage'
--------------------------------------------------
Manufacturer String: Magenta
AudioUnit Name: DDSP Effect
Component Version: 1.0.0 (0x10000)

* * PASS
--------------------------------------------------
TESTING OPEN TIMES:
COLD:
dyld: warning, LC_RPATH @executable_path/Frameworks in /Users/skysupertone/Library/Audio/Plug-Ins/Components/DDSPEffect.component/Contents/MacOS/DDSP being ignored in restricted program because of @executable_path (Codesign main executable with Library Validation to allow @ paths)
dyld: warning, LC_RPATH @executable_path/../Frameworks in /Users/skysupertone/Library/Audio/Plug-Ins/Components/DDSPEffect.component/Contents/MacOS/DDSP being ignored in restricted program because of @executable_path (Codesign main executable with Library Validation to allow @ paths)
dyld: warning, LC_RPATH @executable_path/Frameworks in /Users/skysupertone/Library/Audio/Plug-Ins/Components/DDSPEffect.component/Contents/MacOS/DDSP being ignored in restricted program because of @executable_path (Codesign main executable with Library Validation to allow @ paths)
dyld: warning, LC_RPATH @executable_path/../Frameworks in /Users/skysupertone/Library/Audio/Plug-Ins/Components/DDSPEffect.component/Contents/MacOS/DDSP being ignored in restricted program because of @executable_path (Codesign main executable with Library Validation to allow @ paths)
FATAL ERROR: OpenAComponent: result: -1,0xFFFFFFFF

validation result: couldn’t be opened

macOS 11.6 M1 Macbook Pro 2020
Logic Pro Version 10.7.2 running on Rosetta

Same issue here. The website describes it as a VST plugin, but when you download it, it's actually AU. But then the AU cannot be loaded in Logic. The validation tool gives the following output:
`validating Audio Unit DDSP Effect by Magenta:
AU Validation Tool
Version: 1.8.0
Copyright 2003-2019, Apple Inc. All Rights Reserved.
Specify -h (-help) for command options

VALIDATING AUDIO UNIT: 'aufx' - 'Ranj' - 'Mage'
Manufacturer String: Magenta
AudioUnit Name: DDSP Effect
Component Version: 1.0.0 (0x10000)

PASS

TESTING OPEN TIMES:
COLD:
dyld: warning, LC_RPATH @executable_path/Frameworks in /Library/Audio/Plug-Ins/Components/DDSPEffect.component/Contents/MacOS/DDSP being ignored in restricted program because of @executable_path (Codesign main executable with Library Validation to allow @ paths)
dyld: warning, LC_RPATH @executable_path/../Frameworks in /Library/Audio/Plug-Ins/Components/DDSPEffect.component/Contents/MacOS/DDSP being ignored in restricted program because of @executable_path (Codesign main executable with Library Validation to allow @ paths)
dyld: warning, LC_RPATH @executable_path/Frameworks in /Library/Audio/Plug-Ins/Components/DDSPEffect.component/Contents/MacOS/DDSP being ignored in restricted program because of @executable_path (Codesign main executable with Library Validation to allow @ paths)
dyld: warning, LC_RPATH @executable_path/../Frameworks in /Library/Audio/Plug-Ins/Components/DDSPEffect.component/Contents/MacOS/DDSP being ignored in restricted program because of @executable_path (Codesign main executable with Library Validation to allow @ paths)
FATAL ERROR: OpenAComponent: result: -1,0xFFFFFFFF
validation result: couldn’t be opened
`
macOS 11.6.6 (Intel), Logic Pro 10.7.4

Hi, we just released a new version that should work with older versions of macOS (https://g.co/magenta/ddsp-vst-mac) can you try it out and see if it works for you?
Also, sorry for the confusion, VST version is on it's way :)

Yes it works for me now!

This is also working in my setup. Thanks @jesseengel.

Great, glad it works!


Improve docs for edition = "2018" rustfmt requirement

Hi there,
I had an issue with rustic which had been documented, but which I couldn't find! I thought I'd improve the message a little and link to a bug report I've submitted on rustfmt to encourage a more intuitive error message.

Thanks!


Disabling horizontal scrollbars

Is there any way we could disable horizontal scrollbars and use auto carriage return on lines, without incrementing the line numbers count?

@Sadkit sorry for the long time for response, I don't have the cycles for this but would be happy to offer advice or help sketch out an implementation plan


TypeError: get_project() missing 1 required positional argument: 'is_eval' when uploading

When uploading a dataset, upload.py raises a TypeError stating that get_project() is missing is_eval argument.
$ autonlp upload --project sentiment_detection --split train \
               --col_mapping review:text,sentiment:target \
               --files ~/datasets/train.csv
> INFO    Uploading files for project: sentiment_detection
Traceback (most recent call last):
  File "/Users/sb/.pyenv/versions/test/bin/autonlp", line 8, in <module>
    sys.exit(main())
  File "/Users/sb/.pyenv/versions/test/lib/python3.9/site-packages/autonlp/cli/autonlp.py", line 54, in main
    command.run()
  File "/Users/sb/.pyenv/versions/test/lib/python3.9/site-packages/autonlp/cli/upload.py", line 82, in run
    project = client.get_project(name=self._name)
TypeError: get_project() missing 1 required positional argument: 'is_eval'

If I manually revise upload.py as follows
project = client.get_project(name=self._name, is_eval=False)

things work as they should. Likewise, this happens when trying to run the train command.
$ autonlp train --project sentiment_detection
> INFO    Starting Training For Project: sentiment_detection
Traceback (most recent call last):
  File "/Users/sb/.pyenv/versions/test/bin/autonlp", line 8, in <module>
    sys.exit(main())
  File "/Users/sb/.pyenv/versions/test/lib/python3.9/site-packages/autonlp/cli/autonlp.py", line 54, in main
    command.run()
  File "/Users/sb/.pyenv/versions/test/lib/python3.9/site-packages/autonlp/cli/train.py", line 34, in run
    project = client.get_project(name=self._name)
TypeError: get_project() missing 1 required positional argument: 'is_eval'

I'm using autonlp version 0.3.0.
$ autonlp --version
0.3.0

Hi @suminb !
This is a bug introduced in 0.3.0. We'll fix it as soon as possible.
Sorry for the inconvenience!

That was blazing fast! Thanks for the quick fix.


Caught error... 65: Screenshots not building for more than one device

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

Snapshot throws a Exit 65 error, tests failed when I try to do it for 2 devices, "iPad Pro (12.9-inch) (2nd generation)", "iPhone X". If I run it for one device it runs perfectly fine but not for two devices.
Command executed

fastlane snapshot
Complete output when running fastlane, including the stack trace and command used

Failing tests:
HansSoloUITests.test_Snapshot_All()
** TEST FAILED **
[17:52:21]: Exit status: 65
[17:52:21]: Copying '/Users/Hans/Documents/HansSolo/fastlane/screenshots/es-MX/iPad Pro (12.9-inch) (2nd generation)-02_CategoryScreen.png'...
[17:52:21]: Copying '/Users/Hans/Documents/HansSolo/fastlane/screenshots/es-MX/iPad Pro (12.9-inch) (2nd generation)-04_MemoryGameScreen.png'...
[17:52:21]: Copying '/Users/Hans/Documents/HansSolo/fastlane/screenshots/es-MX/iPad Pro (12.9-inch) (2nd generation)-05_HardGameScreen.png'...
[17:52:21]: Copying '/Users/Hans/Documents/HansSolo/fastlane/screenshots/es-MX/iPad Pro (12.9-inch) (2nd generation)-01_MainScreen.png'...
[17:52:21]: Copying '/Users/Hans/Documents/HansSolo/fastlane/screenshots/es-MX/iPad Pro (12.9-inch) (2nd generation)-03_PracticeScreen.png'...
[17:52:21]: Tests failed while running on: iPad Pro (12.9-inch) (2nd generation), iPhone X
[17:52:21]: For more detail about the test failures, check the logs here:
[17:52:21]: /Users/Hans/Library/Logs/snapshot/HansSolo-HansSolo.log
[17:52:21]:
[17:52:21]: You can also find the test result data here:
[17:52:21]: /var/folders/ys//T/Logs/Test
[17:52:21]:
[17:52:21]: You can find the incomplete screenshots here:
[17:52:21]: /Users/Hans/Library/Caches/tools.fastlane/screenshots
[17:52:21]: /Users/Hans/Documents/HansSolo/fastlane/screenshots
[17:52:21]: Caught error... 65

+----------------------------+-------+
|          snapshot results          |
+----------------------------+-------+
| Device                     | es-MX |
+----------------------------+-------+
| iPad Pro (12.9-inch) (2nd  |  ❌   |
| generation)                |       |
| iPhone X                   |  ❌   |
+----------------------------+-------+

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.13.6

Ruby
2.2.4

Bundler?
false

Git
git version 2.17.2 (Apple Git-113)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.13.6 (17G4015)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
10.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.115.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
2.3.5

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.6.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

public_suffix
2.0.5

addressable
2.5.1

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.6

excon
0.55.0

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.1.3

json
1.8.1

mini_magick
4.5.1

multi_json
1.12.1

multi_xml
0.6.0

rubyzip
1.2.2

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.6

faraday_middleware
<IP_ADDRESS>

naturally
2.2.0

simctl
1.6.4

uber
0.0.15

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

jwt
1.5.6

signet
0.11.0

memoist
0.16.0

os
0.9.6

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

google-cloud-env
1.0.5

google-cloud-core
1.2.7

digest-crc
0.4.1

google-cloud-storage
1.15.0

emoji_regex
0.1.1

libxml-ruby
3.0.0

psych
2.0.8

generated on: 2019-02-06

 [REPLACE THIS WITH YOUR INFORMATION]

The way I got around this is by:

Removing all the device names from the snapfile.

Adding the below to the snapfile:
reinstall_app true
clean true
erase_simulator true

Writing a bash script for the devices

#!/bin/bash
fastlane snapshot --devices "iPhone X"
fastlane snapshot --devices "iPhone XS Max"
fastlane snapshot --devices "iPad Pro (12.9-inch) (2nd generation)"
fastlane snapshot --devices "iPad Pro (9.7-inch)"
fastlane snapshot --devices "iPhone 4s"
fastlane snapshot --devices "iPhone SE"
fastlane snapshot --devices "iPhone 7"
fastlane snapshot --devices "iPhone 7 Plus"
It all seems to work fine by using this bash script.

I had the same issue. Resolved disabling concurrent simulators:
fastlane snapshot --concurrent_simulators false


Require Splash Feedback Speed Control for Container Widgets

https://github.com/EnsembleUI/ensemble/issues/1546

Require Enhancements on this Ticket.
New Requirements:

Require Additional Speed Control Property on Splash Feedback
Proposed speed unit is Milliseconds.

Commtited https://github.com/EnsembleUI/ensemble/commit/944dd2f94c5276babafcf3573631e4a203fe8343. Studio and Ensemble Go has also been updated (Android coming soon).
Studio's typeaheads also explain the new usage but here's the summary of the newly added styles:

splashDuration - The duration in ms when tap and release on the widget. This is the duration it takes to fill the widget's surface with the splashColor.
splashFadeDuration - The duration it takes to fade out once tapped. Since a typical tap starts and ends immdiately, this splashFadeDuration executes almost at the same time as the splashDuration, so ideally it should be equal or longer than splashDuration to see the entire effect.
unconfirmedSplashDuration - This happens when the user tap and hold (not yet released). It is called unconfirmed since the tap will be cancelled if the user moves out of the tap area and release. Usually this should be longer (around 1 secs) to signify that the user has not confirmed the tap.

The combination of these 3 should give more flexibility to control the animation.


Tanks get destroyed by throwing any item at them

They explode/get destroyed from any damage source - even if it's a thrown chocolate bar

For reference: https://gyazo.com/b3863fbb5c522dcae083e0baa920db19


Close the file in case of an IOException in AbstractMemoryHttpData.renameTo.

Motivation:
An IOException may be thrown from FileChannel.write or FileChannel.force, and cause the fd leak.
Modification:
Close the file in a finally block.
Result:
Avoid fd leak.

@netty-bot test this please

@netty-bot test this please

@seedeed thanks a lot


Add shouldRender and allow a function to be passed to ignoredTags.

Closes #691.

[clabot:check]

I'll try to figure out the decrease in code coverage.

It seems that even if I checkout the master branch, running yarn test:jest:coverage locally still gives only about 85% coverage. The codecov bot on GitHub seemed to report 93% (after reporting about 85% yesterday) after I merged earlier, and continues to report 93%. I'm not sure why codecov is still reporting 85% on my computer, and why the codecov bot reported 85% yesterday and 93% today.

@leungbk Codecov result includes coverage from screenshot tests and we don't strictly enforce code coverage changes, especially on contrib extensions. So you don't need to worry about them.

Closing due to inactivity. Please feel free to reopen or create a new PR.


Custom losses, coherent embeddings

Nice property of TSNE, that is not exploited in most of implementations, is that it can be treated as a combination of two orthogonal components: loss function and optimization algorithm. For example one may visualize set on temporally varying vectors with a sequence on coherent embeddings by adding a loss term that penalizes unnecessary movement of each vector between those embeddings. Is it possible to have provide such flexibility to use additional constrains with UMAP?

How to obtain the matrix P from UMAP? Is it self.graph_ from fuzzy_simplicial_set function?
Thanks!

That is the equivalent of it, yes.


3D Delaunay input

I'm trying to implement your delaunay triangulation in my code, but everytime i build it visual studio shows me this error

The input data is degenerate. It appears to exist in 4 dimensions, but it is a 3 dimensional set (i.e. the point of collinear, coplanar, or co-hyperplanar.)

Here is the code I'm using
DefaultVertex[] v = new DefaultVertex[5];

v[0] = new DefaultVertex();
v[0].Position = new double[3] { 5.1, 5.8, 0.0 };
v[1] = new DefaultVertex();
v[1].Position = new double[3] { 7.0, 2.8, 0.0 };
v[2] = new DefaultVertex();
v[2].Position = new double[3] { 4.8, 0.1, 0.0 };
v[3] = new DefaultVertex();
v[3].Position = new double[3] { 1.5, 1.4, 0.0 };
v[4] = new DefaultVertex();
v[4].Position = new double[3] { 1.7, 4.9, 0.0 };

 ITriangulation<DefaultVertex, DefaultTriangulationCell<DefaultVertex>> r = Triangulation.CreateDelaunay(v);

Any fix for this?

The error is correct. All the points are co-planar as they all have the same z-value. Please submit 2D points (without the z-value) instead. The library recognizes that the data is 3D, so is attempting to generate tetrahedra - which would all be degenerate (having zero volume). You likely want triangular information.
((Sorry for the delay in responding.))


As the training goes on, sup_acc decrease. Is this normal?

As the training goes on, sup_acc decrease. So I reduce learning rate, this case still exists.
such as: sup_acc from 0 increase to 96, then decrease to 90 finally.  I think sup_acc is train_sup_acc, in supervised learning, it should be 99.99, But in semi-supervised learning here, it just 90. this case is normal?
Below is current training log:
2021-09-17 05:31:05,999 - mmdet.ssod - INFO - Iter [50/14400]	lr: 7.828e-07, eta: 10:59:29, time: 2.757, data_time: 0.266, memory: 25005, ema_momentum: 0.9800, unsup_weight: 4, sup_loss_rpn_cls: 0.6633, sup_loss_rpn_bbox: 0.3303, sup_loss_cls: 1.8455, sup_acc: 53.1849, sup_loss_bbox: 0.1501, unsup_loss_rpn_cls: 2.6062, unsup_loss_rpn_bbox: 1.7301, unsup_loss_cls: 6.1416, unsup_acc: 52.6421, unsup_loss_bbox: 6.4742, loss: 19.9412
2021-09-17 05:33:10,237 - mmdet.ssod - INFO - Iter [100/14400]	lr: 1.237e-06, eta: 10:24:42, time: 2.485, data_time: 0.095, memory: 25005, ema_momentum: 0.9900, unsup_weight: 4, sup_loss_rpn_cls: 0.6543, sup_loss_rpn_bbox: 0.3205, sup_loss_cls: 0.3482, sup_acc: 94.9533, sup_loss_bbox: 0.1464, unsup_loss_rpn_cls: 2.6226, unsup_loss_rpn_bbox: 0.6446, unsup_loss_cls: 1.0436, unsup_acc: 94.7202, unsup_loss_bbox: 3.6727, loss: 9.4529
2021-09-17 05:35:11,839 - mmdet.ssod - INFO - Iter [150/14400]	lr: 1.954e-06, eta: 10:07:31, time: 2.432, data_time: 0.094, memory: 25005, ema_momentum: 0.9933, unsup_weight: 4, sup_loss_rpn_cls: 0.6318, sup_loss_rpn_bbox: 0.3099, sup_loss_cls: 0.3127, sup_acc: 96.4278, sup_loss_bbox: 0.1446, unsup_loss_rpn_cls: 2.5320, unsup_loss_rpn_bbox: 0.2281, unsup_loss_cls: 0.4462, unsup_acc: 97.9240, unsup_loss_bbox: 1.4821, loss: 6.0875
2021-09-17 05:37:15,827 - mmdet.ssod - INFO - Iter [200/14400]	lr: 3.087e-06, eta: 10:00:46, time: 2.480, data_time: 0.093, memory: 25550, ema_momentum: 0.9950, unsup_weight: 4, sup_loss_rpn_cls: 0.5977, sup_loss_rpn_bbox: 0.3097, sup_loss_cls: 0.3398, sup_acc: 96.8026, sup_loss_bbox: 0.1584, unsup_loss_rpn_cls: 2.3346, unsup_loss_rpn_bbox: 0.1046, unsup_loss_cls: 0.2784, unsup_acc: 98.9751, unsup_loss_bbox: 0.7072, loss: 4.8303
2021-09-17 05:39:19,786 - mmdet.ssod - INFO - Iter [250/14400]	lr: 4.877e-06, eta: 9:55:51, time: 2.479, data_time: 0.094, memory: 25550, ema_momentum: 0.9960, unsup_weight: 4, sup_loss_rpn_cls: 0.5481, sup_loss_rpn_bbox: 0.3087, sup_loss_cls: 0.4070, sup_acc: 96.1583, sup_loss_bbox: 0.1731, unsup_loss_rpn_cls: 2.0273, unsup_loss_rpn_bbox: 0.0322, unsup_loss_cls: 0.1416, unsup_acc: 99.3099, unsup_loss_bbox: 0.2865, loss: 3.9245
2021-09-17 05:41:26,675 - mmdet.ssod - INFO - Iter [300/14400]	lr: 7.705e-06, eta: 9:54:11, time: 2.538, data_time: 0.094, memory: 25550, ema_momentum: 0.9967, unsup_weight: 4, sup_loss_rpn_cls: 0.4768, sup_loss_rpn_bbox: 0.2862, sup_loss_cls: 0.4715, sup_acc: 95.4132, sup_loss_bbox: 0.1895, unsup_loss_rpn_cls: 1.5952, unsup_loss_rpn_bbox: 0.0332, unsup_loss_cls: 0.1408, unsup_acc: 99.2302, unsup_loss_bbox: 0.2120, loss: 3.4052
2021-09-17 05:43:31,341 - mmdet.ssod - INFO - Iter [350/14400]	lr: 1.217e-05, eta: 9:50:54, time: 2.493, data_time: 0.097, memory: 25550, ema_momentum: 0.9971, unsup_weight: 4, sup_loss_rpn_cls: 0.3821, sup_loss_rpn_bbox: 0.2393, sup_loss_cls: 0.4525, sup_acc: 95.4919, sup_loss_bbox: 0.2048, unsup_loss_rpn_cls: 1.0449, unsup_loss_rpn_bbox: 0.0105, unsup_loss_cls: 0.0925, unsup_acc: 99.6831, unsup_loss_bbox: 0.1227, loss: 2.5492
2021-09-17 05:45:35,516 - mmdet.ssod - INFO - Iter [400/14400]	lr: 1.923e-05, eta: 9:47:38, time: 2.483, data_time: 0.096, memory: 25550, ema_momentum: 0.9975, unsup_weight: 4, sup_loss_rpn_cls: 0.3323, sup_loss_rpn_bbox: 0.2170, sup_loss_cls: 0.3843, sup_acc: 94.6693, sup_loss_bbox: 0.2592, unsup_loss_rpn_cls: 0.5614, unsup_loss_rpn_bbox: 0.0019, unsup_loss_cls: 0.0643, unsup_acc: 99.9102, unsup_loss_bbox: 0.0942, loss: 1.9144
2021-09-17 05:47:41,790 - mmdet.ssod - INFO - Iter [450/14400]	lr: 3.038e-05, eta: 9:45:43, time: 2.525, data_time: 0.101, memory: 25550, ema_momentum: 0.9978, unsup_weight: 4, sup_loss_rpn_cls: 0.3164, sup_loss_rpn_bbox: 0.2000, sup_loss_cls: 0.3019, sup_acc: 94.1454, sup_loss_bbox: 0.2831, unsup_loss_rpn_cls: 0.3070, unsup_loss_rpn_bbox: 0.0008, unsup_loss_cls: 0.0534, unsup_acc: 99.9551, unsup_loss_bbox: 0.0819, loss: 1.5445
2021-09-17 05:49:45,712 - mmdet.ssod - INFO - Iter [500/14400]	lr: 4.799e-05, eta: 9:42:40, time: 2.479, data_time: 0.098, memory: 25550, ema_momentum: 0.9980, unsup_weight: 4, sup_loss_rpn_cls: 0.2811, sup_loss_rpn_bbox: 0.1882, sup_loss_cls: 0.2738, sup_acc: 93.7461, sup_loss_bbox: 0.2917, unsup_loss_rpn_cls: 0.2128, unsup_loss_rpn_bbox: 0.0009, unsup_loss_cls: 0.0527, unsup_acc: 99.9358, unsup_loss_bbox: 0.0587, loss: 1.3600
2021-09-17 05:51:49,614 - mmdet.ssod - INFO - Iter [550/14400]	lr: 7.582e-05, eta: 9:39:48, time: 2.478, data_time: 0.096, memory: 25550, ema_momentum: 0.9982, unsup_weight: 4, sup_loss_rpn_cls: 0.2607, sup_loss_rpn_bbox: 0.1927, sup_loss_cls: 0.2887, sup_acc: 92.5063, sup_loss_bbox: 0.3307, unsup_loss_rpn_cls: 0.1707, unsup_loss_rpn_bbox: 0.0006, unsup_loss_cls: 0.0539, unsup_acc: 99.9426, unsup_loss_bbox: 0.0351, loss: 1.3331
2021-09-17 05:53:56,824 - mmdet.ssod - INFO - Iter [600/14400]	lr: 1.198e-04, eta: 9:38:19, time: 2.544, data_time: 0.096, memory: 25550, ema_momentum: 0.9983, unsup_weight: 4, sup_loss_rpn_cls: 0.2264, sup_loss_rpn_bbox: 0.1813, sup_loss_cls: 0.2817, sup_acc: 92.0654, sup_loss_bbox: 0.3322, unsup_loss_rpn_cls: 0.1481, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0487, unsup_acc: 99.9492, unsup_loss_bbox: 0.0178, loss: 1.2362
2021-09-17 05:56:04,359 - mmdet.ssod - INFO - Iter [650/14400]	lr: 1.892e-04, eta: 9:36:52, time: 2.551, data_time: 0.099, memory: 25771, ema_momentum: 0.9985, unsup_weight: 4, sup_loss_rpn_cls: 0.2320, sup_loss_rpn_bbox: 0.1866, sup_loss_cls: 0.2628, sup_acc: 91.9623, sup_loss_bbox: 0.3182, unsup_loss_rpn_cls: 0.1389, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0415, unsup_acc: 99.9572, unsup_loss_bbox: 0.0042, loss: 1.1842
2021-09-17 05:58:10,804 - mmdet.ssod - INFO - Iter [700/14400]	lr: 2.989e-04, eta: 9:34:57, time: 2.529, data_time: 0.100, memory: 25771, ema_momentum: 0.9986, unsup_weight: 4, sup_loss_rpn_cls: 0.2091, sup_loss_rpn_bbox: 0.1693, sup_loss_cls: 0.2708, sup_acc: 91.4751, sup_loss_bbox: 0.3258, unsup_loss_rpn_cls: 0.1178, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0388, unsup_acc: 99.9464, unsup_loss_bbox: 0.0028, loss: 1.1344
2021-09-17 06:00:21,075 - mmdet.ssod - INFO - Iter [750/14400]	lr: 4.722e-04, eta: 9:34:11, time: 2.605, data_time: 0.098, memory: 25771, ema_momentum: 0.9987, unsup_weight: 4, sup_loss_rpn_cls: 0.1575, sup_loss_rpn_bbox: 0.1760, sup_loss_cls: 0.3080, sup_acc: 90.4690, sup_loss_bbox: 0.3467, unsup_loss_rpn_cls: 0.0788, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0440, unsup_acc: 99.9194, unsup_loss_bbox: 0.0026, loss: 1.1136
2021-09-17 06:02:27,567 - mmdet.ssod - INFO - Iter [800/14400]	lr: 7.459e-04, eta: 9:32:10, time: 2.530, data_time: 0.096, memory: 25990, ema_momentum: 0.9988, unsup_weight: 4, sup_loss_rpn_cls: 0.1327, sup_loss_rpn_bbox: 0.1582, sup_loss_cls: 0.3051, sup_acc: 91.1122, sup_loss_bbox: 0.3199, unsup_loss_rpn_cls: 0.0556, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0405, unsup_acc: 99.9432, unsup_loss_bbox: 0.0052, loss: 1.0170
2021-09-17 06:04:36,759 - mmdet.ssod - INFO - Iter [850/14400]	lr: 1.178e-03, eta: 9:30:51, time: 2.584, data_time: 0.101, memory: 25990, ema_momentum: 0.9988, unsup_weight: 4, sup_loss_rpn_cls: 0.1169, sup_loss_rpn_bbox: 0.1577, sup_loss_cls: 0.3170, sup_acc: 90.6921, sup_loss_bbox: 0.3281, unsup_loss_rpn_cls: 0.0559, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0476, unsup_acc: 99.9694, unsup_loss_bbox: 0.0024, loss: 1.0256
2021-09-17 06:06:44,521 - mmdet.ssod - INFO - Iter [900/14400]	lr: 1.861e-03, eta: 9:29:05, time: 2.555, data_time: 0.096, memory: 25990, ema_momentum: 0.9989, unsup_weight: 4, sup_loss_rpn_cls: 0.1147, sup_loss_rpn_bbox: 0.1601, sup_loss_cls: 0.3094, sup_acc: 90.1847, sup_loss_bbox: 0.3461, unsup_loss_rpn_cls: 0.0394, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0446, unsup_acc: 99.9753, unsup_loss_bbox: 0.0029, loss: 1.0173
2021-09-17 06:08:52,724 - mmdet.ssod - INFO - Iter [950/14400]	lr: 2.940e-03, eta: 9:27:23, time: 2.564, data_time: 0.098, memory: 25990, ema_momentum: 0.9989, unsup_weight: 4, sup_loss_rpn_cls: 0.1129, sup_loss_rpn_bbox: 0.1692, sup_loss_cls: 0.3062, sup_acc: 90.2303, sup_loss_bbox: 0.3335, unsup_loss_rpn_cls: 0.0469, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0439, unsup_acc: 99.9579, unsup_loss_bbox: 0.0050, loss: 1.0174
2021-09-17 06:11:00,656 - mmdet.ssod - INFO - Saving checkpoint at 1000 iterations
2021-09-17 06:11:02,006 - mmdet.ssod - INFO - Exp name: soft_teacher_faster_rcnn_r50_caffe_fpn_custom_full.py
2021-09-17 06:11:02,006 - mmdet.ssod - INFO - Iter [1000/14400]	lr: 4.644e-03, eta: 9:25:53, time: 2.586, data_time: 0.103, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.1149, sup_loss_rpn_bbox: 0.1767, sup_loss_cls: 0.3226, sup_acc: 89.3570, sup_loss_bbox: 0.3590, unsup_loss_rpn_cls: 0.0448, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0449, unsup_acc: 99.9805, unsup_loss_bbox: 0.0049, loss: 1.0678
2021-09-17 06:13:09,327 - mmdet.ssod - INFO - Iter [1050/14400]	lr: 4.671e-03, eta: 9:23:55, time: 2.546, data_time: 0.098, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0947, sup_loss_rpn_bbox: 0.1611, sup_loss_cls: 0.3244, sup_acc: 89.1538, sup_loss_bbox: 0.3506, unsup_loss_rpn_cls: 0.0365, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0456, unsup_acc: 99.9851, unsup_loss_bbox: 0.0125, loss: 1.0256
2021-09-17 06:15:15,928 - mmdet.ssod - INFO - Iter [1100/14400]	lr: 4.655e-03, eta: 9:21:46, time: 2.532, data_time: 0.095, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0900, sup_loss_rpn_bbox: 0.1601, sup_loss_cls: 0.3162, sup_acc: 88.7713, sup_loss_bbox: 0.3548, unsup_loss_rpn_cls: 0.0318, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0414, unsup_acc: 99.9675, unsup_loss_bbox: 0.0048, loss: 0.9990
2021-09-17 06:17:22,186 - mmdet.ssod - INFO - Iter [1150/14400]	lr: 4.640e-03, eta: 9:19:34, time: 2.525, data_time: 0.097, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0999, sup_loss_rpn_bbox: 0.1507, sup_loss_cls: 0.3243, sup_acc: 88.5658, sup_loss_bbox: 0.3543, unsup_loss_rpn_cls: 0.0462, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0457, unsup_acc: 99.9852, unsup_loss_bbox: 0.0050, loss: 1.0261
2021-09-17 06:19:31,772 - mmdet.ssod - INFO - Iter [1200/14400]	lr: 4.624e-03, eta: 9:17:59, time: 2.592, data_time: 0.096, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0969, sup_loss_rpn_bbox: 0.1458, sup_loss_cls: 0.3263, sup_acc: 88.5438, sup_loss_bbox: 0.3582, unsup_loss_rpn_cls: 0.0503, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0507, unsup_acc: 99.9736, unsup_loss_bbox: 0.0132, loss: 1.0413
2021-09-17 06:21:41,134 - mmdet.ssod - INFO - Iter [1250/14400]	lr: 4.608e-03, eta: 9:16:19, time: 2.587, data_time: 0.102, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0904, sup_loss_rpn_bbox: 0.1604, sup_loss_cls: 0.3366, sup_acc: 87.5838, sup_loss_bbox: 0.3819, unsup_loss_rpn_cls: 0.0362, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0480, unsup_acc: 99.9461, unsup_loss_bbox: 0.0234, loss: 1.0770
2021-09-17 06:23:48,864 - mmdet.ssod - INFO - Iter [1300/14400]	lr: 4.592e-03, eta: 9:14:21, time: 2.555, data_time: 0.095, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0820, sup_loss_rpn_bbox: 0.1481, sup_loss_cls: 0.3262, sup_acc: 87.5965, sup_loss_bbox: 0.3754, unsup_loss_rpn_cls: 0.0333, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0410, unsup_acc: 99.9516, unsup_loss_bbox: 0.0486, loss: 1.0546
2021-09-17 06:25:57,272 - mmdet.ssod - INFO - Iter [1350/14400]	lr: 4.576e-03, eta: 9:12:28, time: 2.568, data_time: 0.097, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0713, sup_loss_rpn_bbox: 0.1393, sup_loss_cls: 0.3126, sup_acc: 87.4847, sup_loss_bbox: 0.3748, unsup_loss_rpn_cls: 0.0245, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0343, unsup_acc: 99.9417, unsup_loss_bbox: 0.0523, loss: 1.0092
2021-09-17 06:28:05,727 - mmdet.ssod - INFO - Iter [1400/14400]	lr: 4.561e-03, eta: 9:10:34, time: 2.569, data_time: 0.097, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0787, sup_loss_rpn_bbox: 0.1475, sup_loss_cls: 0.3314, sup_acc: 86.9955, sup_loss_bbox: 0.3917, unsup_loss_rpn_cls: 0.0270, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0443, unsup_acc: 99.9356, unsup_loss_bbox: 0.0590, loss: 1.0797
2021-09-17 06:30:15,212 - mmdet.ssod - INFO - Iter [1450/14400]	lr: 4.545e-03, eta: 9:08:49, time: 2.590, data_time: 0.099, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0729, sup_loss_rpn_bbox: 0.1376, sup_loss_cls: 0.3080, sup_acc: 87.7220, sup_loss_bbox: 0.3806, unsup_loss_rpn_cls: 0.0266, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0381, unsup_acc: 99.9128, unsup_loss_bbox: 0.0915, loss: 1.0554
2021-09-17 06:32:25,458 - mmdet.ssod - INFO - Iter [1500/14400]	lr: 4.529e-03, eta: 9:07:08, time: 2.605, data_time: 0.100, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0745, sup_loss_rpn_bbox: 0.1389, sup_loss_cls: 0.3179, sup_acc: 87.0793, sup_loss_bbox: 0.3934, unsup_loss_rpn_cls: 0.0250, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0333, unsup_acc: 99.9277, unsup_loss_bbox: 0.1138, loss: 1.0968
2021-09-17 06:34:35,229 - mmdet.ssod - INFO - Iter [1550/14400]	lr: 4.513e-03, eta: 9:05:22, time: 2.595, data_time: 0.100, memory: 25990, ema_momentum: 0.9990, unsup_weight: 4, sup_loss_rpn_cls: 0.0700, sup_loss_rpn_bbox: 0.1389, sup_loss_cls: 0.3169, sup_acc: 87.1831, sup_loss_bbox: 0.3859, unsup_loss_rpn_cls: 0.0237, unsup_loss_rpn_bbox: 0.0000, unsup_loss_cls: 0.0387, unsup_acc: 99.9144, unsup_loss_bbox: 0.1404, loss: 1.1146

@duany049 First of all, I think you should update the code. There is a bug in the native code that makes the weight of unsupervised loss is always 4 while it should be controlled by semi_wrapper.train_cfg.unsup_weight.
Back to your case, the trend of the accuracy is determined mainly by the weight of unsupervised loss. When the weight is too large, the accuracy will go down first and raise later. So instead of adjusting the learning rate, I think you can adjust the weight at first. (Appending --cfg-options semi_wrapper.train_cfg.unsup_weight=<YOUR_WEIGHT> to the training command and change the value)

OK.
I'll try you propose.I have two question, can you help me.
Q1: The final result is: unsup_acc: 94.8121,  sup_acc: 94.1457;    What should I do, increase the unsup_weight or lower it ?
Q2:  How to confirm normal results？  both unsup_acc and sup_acc indicators exceed 99, right?

@duany049 First of all, I think you should update the code. There is a bug in the native code that makes the weight of unsupervised loss is always 4 while it should be controlled by semi_wrapper.train_cfg.unsup_weight.
Back to your case, the trend of the accuracy is determined mainly by the weight of unsupervised loss. When the weight is too large, the accuracy will go down first and raise later. So instead of adjusting the learning rate, I think you can adjust the weight at first. (Appending --cfg-options semi_wrapper.train_cfg.unsup_weight=<YOUR_WEIGHT> to the training command and change the value)

OK.
I'll try you propose.I have two question, can you help me.
Q1: The final result is: unsup_acc: 94.8121, sup_acc: 94.1457; What should I do, increase the unsup_weight or lower it ?
Q2: How to confirm normal results？ both unsup_acc and sup_acc indicators exceed 99, right?

You can try to decrease it. But it may not reflect the real performance of the detector. So instead of tuning for better training acc, it Is better to prepare a validation set and see the true performance on the validation set. It is not necessary to tune the model for accuracy over 99.

You can try to decrease it. But it may not reflect the real performance of the detector. So instead of tuning for better training acc, it Is better to prepare a validation set and see the true performance on the validation set. It is not necessary to tune the model for accuracy over 99.

Thank you.
This is the first time I use semi-supervised learning, I don't know if I understand it correctly.
Below is what I think:
Unlike the low precision of the training set in supervised learning, which means that the model fitting ability is insufficient, the low precision of the training set in semi-supervised learning is normal
Besides, I have two question for you:
Q1: If I have a large amount of unlabeled data, do I need to increase the sampling ratio of (unlabeled data / labeled data)
Q2: doese train.sample_ratio=[1, 1] represent labeld and unlabeled num respectively ?

Q1: I think a larger sampling ratio is more efficient when the unlabeled data is far more than labeled data.
Q2: Yes. For example, if you change it to [1,2], then it will sample 1/3 labeled data and 2/3 unlabeled data in each batch.

Q1: I think a larger sampling ratio is more efficient when the unlabeled data is far more than labeled data.
Q2: Yes. For example, if you change it to [1,2], then it will sample 1/3 labeled data and 2/3 unlabeled data in each batch.

Happy Mid-Autumn Festival~
Besides, unsup_weight have little effect on the final performance, they essentially adjust the learning rate of the model across different data sets, so I don't have much need to adjust them, do I ?

It is hard to say the unsup_weight has little or heavy effect on the final performance. I think you should still try to adjust it when you find other factors are ready. ( Such as learning rate, pseudo label threshold, sampling ratio)

It is hard to say the unsup_weight has little or heavy effect on the final performance. I think you should still try to adjust it when you find other factors are ready. ( Such as learning rate, pseudo label threshold, sampling ratio)

Thank you very much !


Add more types from lumeod

Moved some of the types from lumeod. All of them are communications between lumeod and API server.
Corresponding PR in lumeod: PR.

Wasn't the plan to use lumeo-types only to re-export the other three crates?

Wasn't the plan to use lumeo-types only to re-export the other three crates?

Hm, missed that somehow. Where it was discussed?

Ok, now it simplified to just two event types with all dependent types stored inside those event modules.


Constraint Refactor

This refactor concerns the constraint library.
We will be splitting the constraint library into the following:

The constraint type + external combinators
The constraint solver
The constraint inference for constraint "computations"

We will be exploring a new abstraction "Arrow" for the constraint inference for computing constraints.
This is designed to alleviate the issues discovered when implementing inference in #5

The above commits have the following changes:

Refactor constraints library style. Renaming modules + using import.ml trick for common dependencies.
Implements the abstract notion of a "constraint computation", a Kleisli Arrow. The interface closely follows that of Jane Street's Bonsai
Implements an external interface for the constraints library, only exporting: abstract constraints + combinators, computations and solve.


Get julia working on aarch64-darwin

Description of changes

(General) Updates the julia JULIA_CPU_TARGET based on upstream binary flags from https://github.com/JuliaCI/julia-buildkite for both all systems Moved to https://github.com/NixOS/nixpkgs/pull/318350
(Darwin) Gets the julia package working on aarch64-darwin:

(Many thanks to Julia community on https://discourse.julialang.org/t/building-julia-for-nix/115304?u=milescranmer for helping get this working)
Enables USE_BINARYBUILDER=1 on darwin. I couldn't get the dependencies compiled from source yet, so I think this is a good solution for the time being, since the only other option is julia-bin which pre-packages the entire binary
Creates ./patches/1.10/0001-hardcode-macos-SDK.patch which hardcodes the macOS SDK to get around the issue of the Makefile calling sw_vers
Adds a few dependencies which are only turned on for darwin

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

This looks cool! Does julia.withPackages work?

This looks cool! Does julia.withPackages work?

I'm new to nix (I'm learning it to make building Julia easier). How should I try this syntax with this version of the build files?

I usually run the following (in a Nixpkgs checkout):
nix run --impure --expr 'with import ./. {}; ((julia_19.withPackages) ["Plots"])'

Hm, I get this as output:
nix run --impure --show-trace --expr 'with import ./. {}; ((julia_110.withPackages) ["Plots"])'
error: builder for '/nix/store/rmjl5q8xxh65w3nlplk73ds11gyb45lh-julia-package-closure.yml.drv' failed with exit code 137;
       last 25 log lines:
       >             push!(orig_pkgs, pkg)
       >             ctx.env.project.deps[name] = uuid
       >             entry = Pkg.Types.manifest_info(ctx.env.manifest, uuid)
       >             orig_pkgs[length(orig_pkgs)] = update_package_add(ctx, pkg, entry, false)
       >         end
       >
       >         global pkgs, deps_map = _resolve(ctx.io, ctx.env, ctx.registries, orig_pkgs, PRESERVE_NONE, ctx.julia_version)
       >     end
       > end
       >
       >
       > open(ENV["out"], "w") do io
       >   for spec in pkgs
       >     println(io, "- name: " * spec.name)
       >     println(io, "  uuid: " * string(spec.uuid))
       >     println(io, "  version: " * string(spec.version))
       >     if endswith(spec.name, "_jll") && haskey(deps_map, spec.uuid)
       >       println(io, "  depends_on: ")
       >       for (dep_name, dep_uuid) in pairs(deps_map[spec.uuid])
       >         println(io, "    \"$(dep_name)\": \"$(dep_uuid)\"")
       >       end
       >     end
       >   end
       > end
       > '
       For full logs, run 'nix log /nix/store/rmjl5q8xxh65w3nlplk73ds11gyb45lh-julia-package-closure.yml.drv'.
error:
       … while calling the 'derivationStrict' builtin
         at <nix/derivation-internal.nix>:9:12:
            8|
            9|   strict = derivationStrict drvAttrs;
             |            ^
           10|

       … while evaluating derivation 'julia-1.10.4-env'
         whose name attribute is located at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:331:7

       … while evaluating attribute 'artifactsNix' of derivation 'julia-1.10.4-env'
         at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/development/julia-modules/default.nix:181:11:
          180|   inherit minimalRegistry;
          181|   inherit artifactsNix;
             |           ^
          182|   inherit overridesJson;

       … while calling the 'getAttr' builtin
         at <nix/derivation-internal.nix>:19:19:
           18|       value = commonAttrs // {
           19|         outPath = builtins.getAttr outputName strict;
             |                   ^
           20|         drvPath = strict.drvPath;

       … while calling the 'derivationStrict' builtin
         at <nix/derivation-internal.nix>:9:12:
            8|
            9|   strict = derivationStrict drvAttrs;
             |            ^
           10|

       … while evaluating derivation 'julia-artifacts.nix'
         whose name attribute is located at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:331:7

       … while evaluating attribute 'buildCommand' of derivation 'julia-artifacts.nix'
         at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/build-support/trivial-builders/default.nix:68:17:
           67|         enableParallelBuilding = true;
           68|         inherit buildCommand name;
             |                 ^
           69|         passAsFile = [ "buildCommand" ]

       … while calling the 'getAttr' builtin
         at <nix/derivation-internal.nix>:19:19:
           18|       value = commonAttrs // {
           19|         outPath = builtins.getAttr outputName strict;
             |                   ^
           20|         drvPath = strict.drvPath;

       … while calling the 'derivationStrict' builtin
         at <nix/derivation-internal.nix>:9:12:
            8|
            9|   strict = derivationStrict drvAttrs;
             |            ^
           10|

       … while evaluating derivation 'dependency-uuid-to-repo.yml'
         whose name attribute is located at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:331:7

       … while evaluating attribute 'text' of derivation 'dependency-uuid-to-repo.yml'
         at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/build-support/trivial-builders/default.nix:103:17:
          102|       ({
          103|         inherit text executable checkPhase allowSubstitutes preferLocalBuild;
             |                 ^
          104|         passAsFile = [ "text" ]

       … while calling the 'toJSON' builtin
         at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/development/julia-modules/default.nix:109:12:
          108|     name = "dependency-uuid-to-repo.yml";
          109|     text = lib.generators.toYAML {} dependencyUuidToRepo;
             |            ^
          110|   };

       … while calling the 'mapAttrs' builtin
         at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/development/julia-modules/default.nix:106:26:
          105|     if lib.hasAttr info.name packageOverrides then (info // { src = lib.getAttr info.name packageOverrides; }) else info;
          106|   dependencyUuidToRepo = lib.mapAttrs util.repoifyInfo (lib.mapAttrs fillInOverrideSrc dependencyUuidToInfo);
             |                          ^
          107|   dependencyUuidToRepoYaml = writeTextFile {

       … while calling the 'mapAttrs' builtin
         at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/development/julia-modules/default.nix:106:57:
          105|     if lib.hasAttr info.name packageOverrides then (info // { src = lib.getAttr info.name packageOverrides; }) else info;
          106|   dependencyUuidToRepo = lib.mapAttrs util.repoifyInfo (lib.mapAttrs fillInOverrideSrc dependencyUuidToInfo);
             |                                                         ^
          107|   dependencyUuidToRepoYaml = writeTextFile {

       … while calling the 'import' builtin
         at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/development/julia-modules/default.nix:103:26:
          102|   # This is also the point where we apply the packageOverrides.
          103|   dependencyUuidToInfo = import dependencies { inherit fetchgit; };
             |                          ^
          104|   fillInOverrideSrc = uuid: info:

       … while realising the context of path '/nix/store/8wdjspzg69qrqwchz9c3216krradn3gv-julia-sources.nix'

       error: 1 dependencies of derivation '/nix/store/q3qczbxxnb57i6k947lq1l9llr4mxg7y-julia-sources.nix.drv' failed to build

Oh, there are some issues at the moment with Julia 1.10 and withPackages. You'd need to use 1.9.

Okay I think I got the scopes right. Let me know how this looks now.

Also trying the earlier suggestion of just putting darwin directly in buildInputs. It seems to say that darwin is impure, but darwin.DarwinTools is okay. Let's see...

Okay I just greatly reduced the PR. Now there's no patching at all; it just loads darwin.DarwinTools and xcbuild directly into nativeBuildInputs. Seems to fix the linking errors I saw earlier and is probably much more robust + future proof!
Let me know how this looks.

Trying to test the julia_19.withPackages but ran into this:
nix run --impure --expr 'with import ./. {}; ((julia_19.withPackages) ["Plots"])'
error:
       … while calling the 'derivationStrict' builtin
         at <nix/derivation-internal.nix>:9:12:
            8|
            9|   strict = derivationStrict drvAttrs;
             |            ^
           10|

       … while evaluating derivation 'julia-1.9.4-env'
         whose name attribute is located at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:331:7

       … while evaluating attribute 'artifactsNix' of derivation 'julia-1.9.4-env'
         at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/development/julia-modules/default.nix:181:11:
          180|   inherit minimalRegistry;
          181|   inherit artifactsNix;
             |           ^
          182|   inherit overridesJson;

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: The ‘env’ attribute set can only contain derivation, string, boolean or integer attributes. The ‘NIX_CFLAGS_COMPILE’ attribute is of type list.

any idea?

Hm, complaining about codesign not found. I see this which might help?
nix run --impure --expr 'with import ./. {}; ((julia_19.withPackages) ["Plots"])'
error: builder for '/nix/store/8ylhk87si5d38ywjvs6lr60kls9yvspd-julia-1.9.4.drv' failed with exit code 2;
       last 25 log lines:
       > rm -f /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/share/julia/stdlib/v`cut -d. -f1-2 < /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/VERSION`/*/source-extracted
       > rm -f /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/share/julia/stdlib/v`cut -d. -f1-2 < /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/VERSION`/*/build-configured
       > rm -f /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/share/julia/stdlib/v`cut -d. -f1-2 < /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/VERSION`/*/build-compiled
       > rm -f /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/share/julia/stdlib/v`cut -d. -f1-2 < /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/VERSION`/*/build-checked
       > # Copy in beautiful new man page
       > /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/install.sh 644 /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/usr/share/man/man1/julia.1 /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/share/man/man1/
       > # Copy .desktop file
       > mkdir -p /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/share/applications/
       > /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/install.sh 644 /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/julia.desktop /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/share/applications/
       > # Install appdata file
       > mkdir -p /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/share/appdata/
       > /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/install.sh 644 /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/julia.appdata.xml /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/share/appdata/
       > # Update RPATH entries and JL_SYSTEM_IMAGE_PATH if ../lib/julia != ../lib/julia
       > # Set rpath for libjulia-internal, which is moving from `../lib` to `../lib/julia`.
       > install_name_tool -add_rpath @loader_path/../ /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/lib/julia/libjulia-internal.dylib
       > install_name_tool -add_rpath @loader_path/../ /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/lib/julia/libjulia-codegen.dylib
       > # Fix rpaths for dependencies. This should be fixed in BinaryBuilder later.
       > # Next, overwrite relative path to libjulia-internal in our loader if $(LOADER_BUILD_DEP_LIBS) != $(LOADER_INSTALL_DEP_LIBS)
       > MSYS2_ARG_CONV_EXCL='*' /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/usr/tools/stringreplace $(strings -t x - '/nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/lib/libjulia.1.9.dylib' | grep "libgcc_s.1.1.dylib:libopenlibm.dylib:@:@libjulia-internal.1.dylib:@libjulia-codegen.1.dylib:$" | awk '{print $1;}') "julia/libgcc_s.1.1.dylib:julia/libopenlibm.dylib:@:@julia/libjulia-internal.1.dylib:@julia/libjulia-codegen.1.dylib:" 255 "/nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/lib/libjulia.1.9.dylib"
       > # Codesign the libjulia we just modified
       > /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/codesign.sh "" "/nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/lib/libjulia.1.9.dylib"
       > Codesigning with identity -
       > Codesigning /nix/store/8h471gz5hs1nb6b59xshhh8glnv5bmc5-julia-1.9.4/lib/libjulia.1.9.dylib...
       > /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/codesign.sh: line 37: codesign: command not found
       > make: *** [Makefile:292: install] Error 127
       For full logs, run 'nix log /nix/store/8ylhk87si5d38ywjvs6lr60kls9yvspd-julia-1.9.4.drv'.
error: 1 dependencies of derivation '/nix/store/30axaibgd30qfayr6lf49w76and80kwf-julia-package-closure.yml.drv' failed to build
error:
       … while calling the 'derivationStrict' builtin
         at <nix/derivation-internal.nix>:9:12:
            8|
            9|   strict = derivationStrict drvAttrs;
             |            ^
           10|

       … while evaluating derivation 'julia-1.9.4-env'
         whose name attribute is located at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:331:7

       … while evaluating attribute 'artifactsNix' of derivation 'julia-1.9.4-env'
         at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/development/julia-modules/default.nix:181:11:
          180|   inherit minimalRegistry;
          181|   inherit artifactsNix;
             |           ^
          182|   inherit overridesJson;

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: 1 dependencies of derivation '/nix/store/m77rmbc2ahpzv7d25mq8f9fxpnxjcgm5-julia-sources.nix.drv' failed to build

@ofborg build julia_19 julia_110

I finally figured out where codesign is; it is in darwin.sigtool.

@ofborg build julia_19 julia_110

What is the default make target that nix runs? I think it's trying to build the mac app or something...
The only place the current error could come from is contrib/mac/app/Makefile within the Julia source, which is for building the dmg file.
 529   │ app:
 530   │     $(MAKE) -C contrib/mac/app
 531   │     @mv contrib/mac/app/$(JULIA_BINARYDIST_FILENAME).dmg $(BUILDROOT)

What is the default make target that nix runs?

Just the default target, as if running make with no arguments.

Thanks. Very odd. This is the current error it's stuck at:
nix run --impure --expr 'with import ./. {}; ((julia_19.withPackages) ["Plots"])'
error: builder for '/nix/store/8pwim6gghwada1n3y84bnm1lip1admc2-julia-1.9.4.drv' failed with exit code 2;
       last 25 log lines:
       > rm -f /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/share/julia/stdlib/v`cut -d. -f1-2 < /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/VERSION`/*/build-configured
       > rm -f /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/share/julia/stdlib/v`cut -d. -f1-2 < /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/VERSION`/*/build-compiled
       > rm -f /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/share/julia/stdlib/v`cut -d. -f1-2 < /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/VERSION`/*/build-checked
       > # Copy in beautiful new man page
       > /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/install.sh 644 /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/usr/share/man/man1/julia.1 /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/share/man/man1/
       > # Copy .desktop file
       > mkdir -p /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/share/applications/
       > /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/install.sh 644 /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/julia.desktop /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/share/applications/
       > # Install appdata file
       > mkdir -p /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/share/appdata/
       > /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/install.sh 644 /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/julia.appdata.xml /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/share/appdata/
       > # Update RPATH entries and JL_SYSTEM_IMAGE_PATH if ../lib/julia != ../lib/julia
       > # Set rpath for libjulia-internal, which is moving from `../lib` to `../lib/julia`.
       > install_name_tool -add_rpath @loader_path/../ /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/lib/julia/libjulia-internal.dylib
       > install_name_tool -add_rpath @loader_path/../ /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/lib/julia/libjulia-codegen.dylib
       > # Fix rpaths for dependencies. This should be fixed in BinaryBuilder later.
       > # Next, overwrite relative path to libjulia-internal in our loader if $(LOADER_BUILD_DEP_LIBS) != $(LOADER_INSTALL_DEP_LIBS)
       > MSYS2_ARG_CONV_EXCL='*' /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/usr/tools/stringreplace $(strings -t x - '/nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/lib/libjulia.1.9.dylib' | grep "libgcc_s.1.1.dylib:libopenlibm.dylib:@:@libjulia-internal.1.dylib:@libjulia-codegen.1.dylib:$" | awk '{print $1;}') "julia/libgcc_s.1.1.dylib:julia/libopenlibm.dylib:@:@julia/libjulia-internal.1.dylib:@julia/libjulia-codegen.1.dylib:" 255 "/nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/lib/libjulia.1.9.dylib"
       > # Codesign the libjulia we just modified
       > /private/tmp/nix-build-julia-1.9.4.drv-0/julia-1.9.4/contrib/codesign.sh "" "/nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/lib/libjulia.1.9.dylib"
       > Codesigning with identity -
       > Codesigning /nix/store/i7yl2z44xy4dsnwxshhnamixizhd82j0-julia-1.9.4/lib/libjulia.1.9.dylib...
       > The following arguments were not expected: --deep --timestamp -vvv --option=runtime
       > Run with --help for more information.
       > make: *** [Makefile:292: install] Error 109
       For full logs, run 'nix log /nix/store/8pwim6gghwada1n3y84bnm1lip1admc2-julia-1.9.4.drv'.
error: 1 dependencies of derivation '/nix/store/x4cwrwrpbvdd00zbncs75fgdw4w7a7qf-julia-package-closure.yml.drv' failed to build
error:
       … while calling the 'derivationStrict' builtin
         at <nix/derivation-internal.nix>:9:12:
            8|
            9|   strict = derivationStrict drvAttrs;
             |            ^
           10|

       … while evaluating derivation 'julia-1.9.4-env'
         whose name attribute is located at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:331:7

       … while evaluating attribute 'artifactsNix' of derivation 'julia-1.9.4-env'
         at /Users/mcranmer/PermaDocuments/nixpkgs/pkgs/development/julia-modules/default.nix:181:11:
          180|   inherit minimalRegistry;
          181|   inherit artifactsNix;
             |           ^
          182|   inherit overridesJson;

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: 1 dependencies of derivation '/nix/store/q6zxqwi04vi67qcsjj6yh6jwzcbakwqg-julia-sources.nix.drv' failed to build

For that specific error, the only place it could come from is (via https://github.com/search?q=repo:JuliaLang/julia /codesign.*option%3Druntime/&type=code) here:
https://github.com/JuliaLang/julia/blob/8a7d8f444ace6156fb73ce5a23ade9ff692fb678/contrib/mac/app/Makefile#L61
Which means it's trying to build the dmg file. Is that expected/desired? I would have thought it would just build the binary?

What is the default make target that nix runs?

Just the default target, as if running make with no arguments.

The correct location is https://github.com/JuliaLang/julia/blob/v1.9.4/contrib/codesign.sh, github search only works with the master branch. Does this also affect 1.10?

Oops, indeed that looks like the right one. Forgot I was testing the build on 1.9.4.
Alright I'll see if I can add a patch..

@ofborg build julia_19 julia_110

Alright, now it gets all the way to building and installing which succeed. But the actual julia_19.withPackages fails:
Resolving Julia packages with the following inputs
Julia: /nix/store/jh288dvjm6wwpchv1w424ylhzy6bq4iy-julia-1.9.4
Registry: /nix/store/gxv9wz6knd4a651ydnn98bilk76anl1d-source
/private/tmp/nix-build-julia-package-closure.yml.drv-0/.attr-0l2nkwhif96f51f4amnlf414lhl4rv9vh8iffyp431v6s28gsr90: line 124: 52453 Killed: 9               julia -e 'import Pkg
Pkg.Registry.add(Pkg.RegistrySpec(path="/nix/store/gxv9wz6knd4a651ydnn98bilk76anl1d-source"))

Is that an issue elsewhere or could it mean the codesigning is incorrect now? Not sure what else to try.

I've never seen a SIGKILL issue before. Can you confirm basic Julia functionality works before trying .withPackages?

It's weird, it goes through all the Julia tests in make test. I can see the LinearAlgebra tests running fine.
Although I will note I can't actually start the Julia binary stored in ./result/bin/julia from my regular terminal – I get the SIGKILL issue there too. I assumed it was due to not understanding nix and from missing things on LD_PRELOAD or something, since the tests within the build run fine. But now I'm not sure.

I don't have a Mac with Nix to test on, but some googling indicates that OS X may kill processes with improper code signing--it sounds like you might see something like EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)).
To debug further maybe you want to use something like dtruss. Maybe you can also try turning off "System Integrity Protection"?


[test/plugin] immigrate elasticsearch-5.x scenario

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[x] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

/run agent-plugin-test-3

Related to #3583


Bugfix/icon font reference check exists

I signed the CLA!

Sorry for not reviewing this earlier, but we've made the icon font manual!


Speed-up html-escaping using jetscii

$ cargo bench --bench escape

Before the PR:           [3.6464 µs 3.6512 µs 3.6564 µs]
Impl. without `jetscii`: [3.4837 µs 3.4899 µs 3.4968 µs] ~ 95 % of baseline
Impl with `jetscii`:     [2.0264 µs 2.0335 µs 2.0418 µs] ~ 55 % of baseline

Until portable SIMD gets stabilized, I don't think we can do much for non-X86 platforms. And even after it is stabilized, I guess any optimizations should be implemented upstream in memchr and/or jetscii.

I'll take a look once rebased. ;)

Rebased. For now, that's the last one in my "let's make it speedy" series. :)

I excluded x86 (32bit). That makes the code a bit more readable, and if you still use a 32bit x86 system in 2024, then yeah, chances are that you run your code on some aching VIA processor without SSE 4.2 support.


Click on the magnifying glass to enter the user ID user name, determine the backfill to the form

https://stackblitz.com/edit/angular-oprfhy

Field id in bullets may be inconsistent with the form, how to write a generic method

The dialog field is also dynamically generated by the clicked field

hi,
thanks for the example but it's not clear to me what are you asking for, can you please clarify a little bit thanks!

Sorry, English is not good, so it is difficult to describe clearly. My purpose is to have a bullet when clicking on the magnifying glass, which is the query data, select a row to bring the data to the present form

I understand now but what's the issue there ?

No problem, thanks, but I did not expect a better solution


Dark Mode for Vessel Information page

This issue depends on #368 being completed.
When Dark Mode is on - the Vessel Information page should look like this:  https://mongodb.invisionapp.com/share/PCYZ6ZW7FR8#/screens/433591787_Boarding_-_Vessel   (Note that there is a separate issue for pull-down menus.)
Color key for light mode: https://mongodb.invisionapp.com/share/PCYZ6ZW7FR8#/screens/433591768_Color_Key_-Light_Mode
Color key for dark mode: https://mongodb.invisionapp.com/share/PCYZ6ZW7FR8#/screens/433591769_Color_Key-Dark_Mode
Component Color specs for light mode: https://mongodb.invisionapp.com/share/PCYZ6ZW7FR8#/screens/433591770_Component_Colors-Light_Mode
Component Color specs for dark mode: https://mongodb.invisionapp.com/share/PCYZ6ZW7FR8#/screens/433591771_Component_Colors-_Dark_Mode
Both dark and light modes should follow the color key and specs above (it is possible that the current light mode is not), and colors should be stored in:
app/src/main/res/values-night/colors.xml
app/src/main/res/values/colors.xml
Please make sure to TEST your build on a device or emulator to verify everything has changed - you can get a login and realm-app-id with easy instructions at https://wildaid.github.io/contribute/sandbox.html

Just submitted a PR solving this issue =)


Implementing GLora

Feature request
Implementing GLORA in PEFT as a superset of LORA, reference:
https://arxiv.org/abs/2306.07967
Motivation
This is a superset of regular LORA and performs better in some circumstances.
Your contribution
I can help with implementation if given guidance.

Duplicate of #780. Do you have experience with GLoRA, did it work well for your use cases?
Also, note that there is a PEFT fork that contains a GLoRA implementation but it the fork is a bit out of date by now. Maybe you could still try to give it a go and see if it leads to improvements on your use cases.

I had used GLora with mixed results in Kohya SS SDXL dreambooth scripts. The results are mostly qualitative and some models were better than Lora. Thanks for the pointers! will have a look.


Created an Ansible Playbook

Hi (again),
I'm also a huge fan of Ansible and automating system builds, so I created an Ansible playbook to install MusicBot and enable it as a service on an Ubuntu 16.04 system:
https://github.com/dmuth/MusicBot-Ansible
I'd be interested in knowing what you think, and if you'd like me to do any more with it (other distros), etc.
All the best,
-- Doug

Update: Ubuntu 14.04 is now supported, Munin support has been added for generation of performance graphs, and I added support for configuring Digital Ocean hosts as well.

Thanks! 👍
We've added this to our wiki page and will be closing this issue for the time being. If anyone has an issue with this distribution, contact dmuth directly or leave an issue in this repository.


ClickHouse as destination

Add support of ClickHouse as a destination.

Hey, thanks for great tool! Is there any ETA for this feature?

Hey, thank you very much!
@xtreding is working very hard now to roll out CH integration next week! Stay tuned

Hi @aslubsky!
We've added ClickHouse support. For more information visit https://docs.eventnative.dev/configuration/clickhouse-destination

Thanks guys, you are awesome ))


Make transaction pool limits for sender based on pool size

PR description
Limit the portion of the transaction pool that a single sender can occupy to a percentage

defaults to 0.1%, or default of 5 per sender with default max txpool size
moves this config out of BesuCommand and into TransactionPoolOptions

This PR will see the default txpool configuration restrict the number of transactions from a single sender in the pool from 64 to 5.  This should decrease the cost of transaction eviction during transaction processing, and yield a transaction pool with a greater percentage of executable transactions for building a block.
Fixed Issue(s)

relates to #4401
Documentation

[ ] I thought about documentation and added the doc-change-required label to this PR if
updates are required.

Changelog

[ ] I thought about the changelog and included a changelog update if required.

Please just update the CHANGELOG

burned in on mainnet along with 4423, 4425


Greaseweazle host tools is now available in guix

This is just for information, please close when read.
The greaseweazle host tools are available as a guix package: https://packages.guix.gnu.org/packages/greaseweazle-host-tools/

Many thanks!


[Feature] Able to customize product page and more payement options

Hi everybody,
about the product page:

it will be good that Casdoor support customized UI for product page, as the product page is very ugly and has many information that are not relevant for customers/users (as the actual stock, how many items already sold, etc.) ;
actually, the only currencies available are the USD and Yuan, what offer a very limited choice if we wish to use it in countries that are not using those two currencies (as in the Euro zone for example). As Casdoor is able to integrate Stripe and Paypal payement systems, it will be nice to be able to choose a default currency from many different currencies ;
a page (or a menu item on the user dashboard) where users/customers could manage their subscriptions (cancel, upgrade, etc.). Because actually, users can subscribe to a product (with a recurrent payement) but are unable to manage such subscription and can't cancel it for example...

I think by changing and upgrading products page and payment options in such a way will give to Casdoor a serious advantage compare to the other IAM, IdP and SSO platform, as many developers are looking to link payement systems with IdP platform in a simple and seamless way, in order to monetize external contents (as website, page, blogs, articles, files, game, etc.).

The Pricing page is not working properly neither: if we clic on any plan of the Pricing Page (even on the Demo site, but on a live site too), the link forward the return URL of the product, but not to the product page itself.
So, that makes it impossible to pay a subscription...

And it will be good to customize the buttons of payment on the product page: to have something like "buy now" or have the option to set what is write on those buttons, as not everyone would like to show "Stripe" or PayPal words...

@pzguillaume "Stripe" or PayPal is the payment channel. You should let customers know what channel they are using.

@pzguillaume "Stripe" or PayPal is the payment channel. You should let customers know what channel they are using.

@hsluoyz Actually many customers don't know Stripe and it could be confusing for them.
Almost all the pay websites offer a payment button without specifying the payement platform used by the website. Or they offer a buy button like "Payement/Credit Cards" and/or a button "Paypal". As almost everybody knows Paypal but not the other payement providers.
So, I think it will be good to be able to customized the name of the "Buy Button", than to use necessarily buttons with "Stripe" or "Paypal" showing on them...


README.md has a bug

README.md has a bug in example implementation:
command.Alert = Alerts.Once;
should be:
command.Alert = Alert.Once;
command.Effect = Effects.ColorLoop;
should be
command.Effect = Effect.ColorLoop;
Also it is very unclear how one should Register the Application with:
var appKey = await client.RegisterAsync("mypersonalappname", "mydevicename");
It will throw exception right away as button on the bridge was not pressed. What is intended use case scenario with this? I think it should be at least mentioned here (I know I'm a bit stupid, in original Philips implementation it is done by callbacks, here I have no clue).

Ok, thanks. I fixed it and added a comment that it will throw an exception if you did not press the bridge button.

Thanks, looks great!
BTW. Is this the correct way of handling the press? If so - is there any way to get a feedback that user pressed the button (so we don't have to wait any longer)? (sorry for asking here, not sure where I supposed to ask):

create the client (LocalHueClient)
wait for the user to press the button
call RegisterAsync

yes, but you don't know when the user has pressed the button. So you have to fix that yourself in your app UI. For example you can make a button in your app that says press this button after you pressed the bridge button. Or you can call RegisterAsync every 5 seconds untill it succeeds.
Different ways to handle this and it's up to the app to make a nice implementation.

Thank you for your answer!


There is no response when executing "Start Streaming Logs" action for a Linux Function App

OS: Ubuntu 22.04
Build Version: 20220819.8
Repro Steps:

Create a Linux Function App.
Right click this Linux Function App and execute "Start Streaming Logs" action.
Check whether it opens the live metrics stream in the portal or not.

Expect:
It opens the live metrics stream in the portal.
Actual:
There is no response when executing "Start Streaming Logs" action.
More Info:

This issue does not reproduce for a Windows Function App.
This issue does not reproduce on Windows OS.

I'm seeing similar behavior as with #3294, where it works with the existing Functions extension with VS Code but not with VS Code Insiders, and on Ubuntu but not Windows.  I'm going to say it's likely the same underlying issue.

Verified this issue on current VS Code Stable 1.71.2 and VS Code Insiders 1.72.0 with the latest Function extension 20220922.1 installed, this issue has fixed, close it.


Update TOC.yml

@Juliako : Thanks for your contribution! The author, @, has been notified to review your proposed change.

@Juliako This pull request has been closed. Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the reviewers know the updates are ready to be merged. Read about authors working in the public repo for more information. Thank you.


how to use filter in alert_text_args

for example ：
    name: admin_test1111
    type: frequency
    owner: admin
    description: 2018-06-11 16:38:53
    index: logstash-*
    num_events: 1
    is_enabled: true
    timeframe:
      minutes: 60
    filter:
    - query:
        query_string:
          query: 'kubernetes.labels.name: hello'
    - query:
        query_string:
          query: 'kubernetes.namespace_name: admin'
    - query:
        wildcard:
          log: '*Listening*'
    alert:
    - email
    smtp_host: smtp.exmail.qq.com
    smtp_port: 465
    smtp_ssl: true
    from_addr:
    smtp_auth_file: /opt/config/email_config.yaml
    email:
    alert_text_args:
    - name
    - kubernetes.labels.name
    - filter
    - num_hits

question：if i want user “the filter query wildcard log” in alert_text_args ，
alert_text_args:
- filter[2].query.wildcard.log ??????????

This is not supported right now. You'll have to either duplicate the text in the alert definition or, if you want it slightly more standardized, you could perhaps use YAML anchors.

For the above configuration, can you give an example？

It's a bit convoluted, but this would let you have only a single place where a query is defined.
filter:
 - query:
        query_string:
          query: &query1 'kubernetes.labels.name: hello'
query1: *query1
alert_text: "You queried for {}"
alert_text_args: [query1]

Thank you very much,This is enough to solve my problem,
thanks again


Typeshed support does not load 3.x version of unittests

assertLogs is defined in https://github.com/python/typeshed/blob/master/stdlib/3/unittest/init.pyi rather than in unittest.pyi

Actually it does, my fault.


fix: add managed image properties to packer templates for cvm build fix

What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR adds 'managed_image_name' and 'managed_image_resource_group_name' to all packer templates. The absence of these two properties resulted in failed CVM builds.
Which issue(s) this PR fixes:
Azure was not recognizing CVMs as managed images.
Requirements:

[x ] uses conventional commit messages
[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2626

Relevant Lines:
3455

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2626

Relevant Lines:
3455

💛  - Coveralls

what are CVMs ?

what are CVMs ?

@djsly CVMs are Confidential Virtual Machines.


v1.8.0

Addresses #138
Decouple dbt-core and the base adapter and use a stable adapter interface i.e. dbt-adapters

database key in profile.yml is still optional for all but one of the dbt-oracle workflows.  Without database name in profile.yml the generated catalog used for project documentation will be empty.
Prior dbt 1.8, we could inject database name in the manifest because of only dependency on dbt-core. From dbt-oracle 1.8, the adapter can use only the stable interface i.e. dbt-adapters. Catalog generation task is implemented in dbt-core and it seems difficult to inject database at runtime. There is no way to override a function in dbt-core. Adapters should not in any way refer to dbt-core.
For now, to circumvent the problem, I detect that database key is missing from profile.yml and issue a warning message to the user to add an entry in profile.yml for catalog generation The warning message also shows the database name that dbt-oracle expects. That way users don't have to worry about "what" the database name is and "how" to get it.

The warning message displayed is as shown below:


CB Command button taking an exceptionally long time to process

MCEdit-Unified (version <IP_ADDRESS>) takes an exceptionally long time to process even one chunk selection when I click on CB Commands, even if there are no command blocks in that chunk.  A completely empty chunk (void) takes 15+ seconds to process.

On my side, it takes about 2 seconds to process a chunk without command block in. (Tested a PC 1.10.2 and 1.12-pre7 worlds).
What is your OS (Linus, windows, OSX) ?
What game version is the world you're working with?

Windows 10, and it is a 1.10.2 world.

Thank you for the information.
I'll test on my side as soon as I can get a Windows system :smile:


[APIM 3.0.0][UI] Publishing an API without an Endpoint assigned is allowed

the UI allows publishing an endpoint without an endpoint.
step 1 generates an error in the server console " ERROR - APIUtil Unable to parse endpoint config JSON org.json.simple.parser.ParseException: null"
Shows a UI error, which is hard to read.

Fixed in APIM 3.0.0 beta


Vmi log statuses

VMI: log statuses changes in wait_for_status

/cherry-pick v4.14

/cherry-pick v4.13

/verified


Add poster images to new A/V ingests

See also: wellcometrust/platform#3718.

according to @rsehr this is already part of #255


DSP gas giant

Dyson Sphere Program calculator uses gas giant extraction as a single recipe tapping two resources at the same time (fire ice or deuterium, and hydrogen), this causes weird behavior in the calculator, since it thinks that even when you're only getting one of the resources, you're getting a proportionate excess of the other one. Could be easily solved by having the 4 gas giant resources (3, but hydrogen has different gains on the two different types, so should be treated separately) as 4 different recipes instead of just 2.

I've seen this request before, which makes me think I must be missing something. Can orbital collectors be configured to collect only one resource at a time? My understanding was that they always collect hydrogen and either fireice or deuterium.

They collect permanently and store it in their inventory. But you can request either one of those resources for a production line with ILS, and this doesn't affect the collection of either resource (unlike for example with oil refinement, where if one line gets filled, the other also can't function, due to the factory shutting down if either resource is full).
The issue is that the calculator treats the orbital collectors' output the same as the refineries', so if you request only fire ice, hydrogen will nonetheless automatically show up as excess. This can be an issue further down the line, where you create graphene and hydrogen from the fire ice, and you want to dump the exact amount of extra hydrogen created, but the calculator shows weird values, since it thinks it also has hydrogen from the gas giant too.

Ok, that lines up with my understanding. One thing you can do is expand the hydrogen step and it will tell you exactly how much hydrogen comes from orbital collectors vs other sources. I still think it's appropriate to treat it as an excess, since it is still another source of hydrogen that can be tapped.

So it feels like there are two different classes of surplus.

The traditional: items produced as a byproduct that must be disposed or stored explicitly otherwise production will back up
This case: extra items can be produced by this recipe, but if unused, they do not need to be disposed or stored

I still think of the second case as a surplus, it's not exactly like an untapped vein because it is already tapped; it doesn't require any extra factories to produce the other items. I'll give it some thought, perhaps there's a way to distinguish the two types of surplus, e.g. preserve the recipes as they are but ignore surpluses from the gas giant recipes.

This is a specific problem only for gas giant products, since Hydrogen is generated by 6 recipes, 2 of those being the gas giant extraction, and used in 8 recipes, with 7 of them having a chance of overlapping with the other product's production chain too. If they were treated as separate mining facilities, there are very few things that would change. One is that if you add both of them deliberately to the chain, is the amount of Orbital Collectors shown at the overview at the end. But that is useless in the first place, since the mining rates are variable, and when you tap a gas giant, you pretty much always want to just plonk down the 40 extractors and forget about it. The other change would be that the two recipes would have to still be on the same toggle in the recipe disable menu.
I also still think it should be treated as an untapped vein, it's pretty much the same as if you dropped down a miner on a mineral vein, built some storage and left it there, with 0 intention of using it. The only issue is that its mere existence screws up some calculations, because the calculator thinks that you already have that resource available in the chain. The real fancy and nice solution to all of this would be if I could mark specific sources of products to be ignored. This would also solve the similar problem with the Blender in Satisfactory, since most fluid outputs from that can be used for power generation, which can't be added to the calculator (yet?).
On a side note, when I thought up that miner comparison, I also realized that after finalizing the other product's utilization, you can add the extra from the gas giant as a product to be made in the top, and this solves the original issue in most cases. The dumb part is that H2 can be used to create even more H2, and if you want to include that in the calculator, it can still mess up with this, but that is really an edge case.

Closed in #843


Use .NET dev container

The currently used universal image is very large (> 10GB) and contains many unneeded dependencies.
It did not help to resolve #118.
Furthermore, the version 0-linux is now outdated (microsoft/vscode-dev-containers#675).
In contrast to the universal image, the .NET image only requires around 800MB of space.

This pull-request is still up-to-date, @NotMyself .
It only needs an update of the used container image if #165 is merged beforehand.


⚠ Bofrost.de has degraded performance

In 3e3dcdb, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1278 ms

Resolved: Bofrost.de performance has improved in ff9ee60.


Initialized .travis.yml

We currently plan to run unit tests with nose but any other suggestions for linters/static checkers are welcome! Right now tests are configured for 2.7 and 3.4 and I'll assume we will want to match all the supported Python versions of Iris.
Note that unit tests for plotting will also be possible once @philippjfr PR is merged into Iris.

The tests should go green soon at which point I think this is ready to merge.

The pr build is passing and the failure of the push build is expected. Ready to merge!

Looks good, merging.


Pagination of project members

GitLab API per default defines 20 items per_page for the returned result. Now if a project has more than 20 members we have an issue with increasing the number of items to max i.e. 100.
Therefore I complemented your code.
Many thanks!

Sorry, I just tried to pull it using an old version.
I will create a new fork and do my changes again.
Thanks for your understanding =)


Updated references in Identity Migration Doc

Updated references in Identity Migration to use the final namespaces of components:
"Microsoft.AspNetCore.Identity.EntityFrameworkCore":  "1.0.0",
"Microsoft.AspNetCore.Authentication.Cookies": "1.0.0",

Removed workaround to assure that database is created in Entity Framework Core

Hi @Tanato, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

@Rick-Anderson done the requested changes. I took the liberty of wrap the line because seems to me that helps a little in readability.

Thanks


BUG: UI can't show full screen on iPhoneX .

There's screenshot below, how should I solve this issue ?
Maybe because of safe-area I guess.

@XiaoWuTongZhi, this is not related with the control but with the Xcode project. In the example project (or in your own project) add a launch image for iPhone X.
Please get help in this answer in Stack Overflow.

I got it , missing iPhoneX launch image....


No LSP suggestions in Rails functions (data: {action: ""})

Hi,
For example:
<%= link_to root_path, data: {action: "click->hello#hello"} %>

This is not getting picked up by the LSP. It is a common pattern in Rails so definitely worth adding this support, I would think?

Hey @Gert-JanPeeters, thanks for reporting this! Yes, I definitely want to support this as well, but it requires some more work.
One of the first steps was to implement the JavaScript visitors for Prism (https://github.com/ruby/prism/pull/1769) so we can parse the Ruby code from Node.
Next up is to integrate this into the Stimulus LSP so we can prose and look for ERB in HTML files.


Test file not found

Has the test file been removed? I get an error of no such file or directory while using docker ( on macOS)

cd $GOPATH/src/github.com/schollz/find3/server/main/testing
-bash: cd: /src/github.com/schollz/find3/server/main/testing: No such file or directory

Input on the shell
go env

Search for GOPATH in the output, you'll get directory.


Auto create CMakelist from seed if not present

Allows for very nice demos by just creating service.cpp. cmake config is then copied from seed.

Can one of the admins verify this patch with one of the following commands:

"jenkins test please" for a one time test run
"ok to test" to accept latest and future commits on this pull request for testing
"add to whitelist" to add the author to the whitelist

add to whitelist