Updating from EF Core 2 Preview 1 to EF Core 2 Preview 2 issue

Hi
I'm trying to update my project from EF Core 2 Preview 1 to  EF Core 2 Preview 2 but when I do so I get the following exception:
Exception message: Severity	Code	Description	Project	File	Line	Suppression State
Error		Could not install package 'Microsoft.EntityFrameworkCore.SqlServer 2.0.0-preview2-final'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.6.1', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
Can anyone please tell me what do I need to do to make it work?
Best Regards
JC

@jmjcoelho I saw the same issue on one of my machines before I installed the .NET Core 2.0 Preview 2 SDK from https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.0-preview2-download.md and the latest preview of Visual Studio 2017 (15.3 Preview 3) from https://www.visualstudio.com/vs/preview/.
There are other workarounds mentioned at https://stackoverflow.com/questions/44394243/entity-framework-core-2-0-on-net-4-6-1, but those were not necessary for me, I assume because I got a very recent version of NuGet as part of either the SDK or Visual Studio.
cc @bricelam

I tried all the mentioned workarounds and none worked for me, the only one I haven't tried was to install the latest latest preview of Visual Studio 2017 (15.3 Preview 3), I'm going to do that and try again.
Many thanks
JC

@jmjcoelho While there may other workarounds/hacks, the only version of Visual Studio that is intended to work is 15.3 Preview 3. Also, the .NET Core 2.0 Preview 2 SDK will need to be installed regardless of using command line or VS.


Add validation during training

I think the paper mentioned using validation dataset, so this may be something worth adding.
This may require some changes on AudioReader. Right now it's hardcoded to load all files in a directory, looks to me it would be better to give it a generator, and move load_generic_audio and similar to train.py since they're training details.

My current goal is to refactor everything that's specific to certain datasets into AudioReaders so that the rest of the implementation can be more generic.
(And the train.py and generate.py scripts should become as small as possible, as they're tricky to test properly)
I can imagine that we could give the AudioReader a method to get a train and a test batch, like this:
reader = MyAudioReader('./directory')
X = reader.train_batch()
X_test = reader.train_batch()

X and X_test would be TensorFlow ops that we can pass to the network.

So the idea is to have a AudioReader superclass, and allow extension by subclassing?

@jrao1: Yeah, AudioReader can define the interface that's expected by the model.

@ibab I have a preliminary version here: https://github.com/jrao1/tensorflow-wavenet/tree/add_validation, let me know this fits your ideas.

@jrao1 Thank you for your implementation, but when I tried to use it (but implementing another class instead of DirectoryAudioReader for another type of data), it looked like the execution was stuck within wavenet.audio_reader.AudioReader#thread_main, not actually reaching the training phase.
I've added an output of processed filenames and it repeats names of training and validation files all over again.
Would you be so kind to help to overcome this issue, because I'm not very much acquainted to  the TF queues and threading.

@lukovkin Could you provide a way to reproduce this issue?

@jrao1 Yes, I made a branch which have code closest to your initial implementation (as I believe) - https://github.com/DeepGnosis/tensorflow-wavenet.git#jrao1
Command line I've used:
python train.py --data_dir=data --sample_size 50000 --val_size 3329
I could provide sample train and validation files also.

@lukovkin This is probably because your sample size is bigger than the data size from the file, it's sort of a bug, the logic under if sample_size: in method get_audio_iterator assumes sample_size is always smaller than the size of the audio, so it needs to cut audio into pieces, it never considered the case where sample_size is bigger than audio, in which case yield never got executed. You can add a line:
print 'train', train, 'sample_size', sample_size, 'audio size', audio.shape, 'buffer size', buffer_.shape
under if sample_size: to verify this

@jrao1 Looks like you're quite right!
Actually, in my case the data size was exactly equal to the sample size, but the loop condition was '>'.
I've changed to:
while len(buffer_) >= sample_size:
and it looks to be working.
Thank you.

@lukovkin No problem, glad i could help.


[pseudometric] add aname_to_localname(); fix bug in init_context()

check for errors returned from krb5_init_context()
add glue call to krb5_aname_to_localname()

Thanks for writing this; it looks like it will be quite useful for us!
– Richard Silverman<EMAIL_ADDRESS>

I ran your GitHub workflow myself on this; it passes, although there are some unrelated errors on older versions of MacOS that I believe must already be issues you know about.

https://github.com/jborean93/pykrb5/pull/20 should work around the macOS testing problem, just push a new commit and hopefully it will pick it up.

I reverted the krb5.init_context() fix on this branch, and opened a separate PR for it. It's ready to go and shouldn't wait for me to get time to finish work on the krb5.aname_to_localname() addition.


new group:  Lynx

host location
http://lynxbllrfr5262yvbgtqoyq76s7mpztcqkv6tjjxgpilpma7nyoeohyd.onion/leaks
group name
Lynx
group information
Based on Inc Ransom code source
Also a clearnet : http://lynxblog.net/leaks
host
v3 (onion)
parser
grep -oP '(?<=
).*?(?=
)' source/lynx-*.html

Hi, this group is named "lynx" on group lists but his posts are sent with "lynxblog" name.
Can you fix it?


fix the typo in the entrypoint for rest_api docker container

There is a typo in the entrypoint for rest_api docker container. It should be --bind and not -bind

The commit message is missing the required Signed-off-by line.  This can generally be fixed with "git commit --amend -s" and re-pushing to github.

Hi @vaporos,
I have amended the commit message as required by you.
Regards & thanks
Kapil


[PEP] Reduce PEP CLS & Support Multiple Segment IDs

Load css first and added support for both stage and prod ids to be authored together
Resolves: https://jira.corp.adobe.com/browse/MWPW-137828
Test URLs:

Before: https://stage--express--adobecom.hlx.page/express/feature/image/remove-background
After: https://pep-perf--express--adobecom.hlx.page/express/feature/image/remove-background

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (7d5a20e) 34.06% compared to head (95734f1) 34.20%.

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #632      +/-   ##
==========================================
+ Coverage   34.06%   34.20%   +0.14%
==========================================
  Files         132      132
  Lines       25406    25406
==========================================
+ Hits         8654     8691      +37
+ Misses      16752    16715      -37

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Any reason to publish the package in a subdirectory

Is there any reason to publish the ounziw_osm Concrete package in the ounziw_osm directory instead of the root of the git repository?
If the package is present in the root directory of the repository, we could add this package to packagist (and we could install it in Concrete with a simple composer require).

Thank you for correction.
I merged your PR.


subscriber settings gives error

login as subscriber go to account-> settings - get the error

It was because the user does not had the ROLE_USER assigned. This role is now assigned automatically to all new users.

After solving #143 an ADMIN will be able to do it in the User Management.


from_bcolz added usecols= keyword

Added usecols= keyword to read selected columns only, that reduces a run time significantly especially for wide tables. Started in #1432 .

This looks good.  It could use a test.  It would be good to verify that the following hold:

The resulting dataframe has column names that match usecols
The bcolz.ctable within the .dask attribute also only has these columns.  I would iterate through df.dask.values() to find the ctable and then run the check on that
This provides nice error messages if someone provides a usecols keyword argument that contains columns that aren't found in the ctable

Won't columns fit better than usecols? I think it's used in other places for a similar purpose.

I was inspired by pandas.read_csv(usecols=...) keyword,  though I can switch to 'columns' to be consistent with dask naming style.

Sorry for the lapse in responses here. Either columns or usecols sounds fine to me. This should be good to go once Matt's comments above are addressed, and the merge conflicts fixed. Do you still have time/interest in finishing this up?

Closing this as stale.  Please feel free to speak up if anyone would like to take this on again.


echoscu.py lacks feature parity with dcmtk

Missing Features:

General

Connection request timeout

ACSE timeout

DIMSE timeout

Setting max PDU size

Repeating echo

Abort association instead of release

TLS/Security

All

Documentation

Info page

TLS is not a priority at the moment, will leave it for later


HTTP Error 500: Internal Server Error for one particular video that works on a browser

Checklist

[ ] I'm reporting a broken site support issue
[ ] I've verified that I'm running youtube-dl version 2020.01.24
[ ] I've checked that all provided URLs are alive and playable in a browser
[ ] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ ] I've searched the bugtracker for similar bug reports including closed ones
[ ] I've read bugs section in FAQ

Verbose log

PASTE VERBOSE LOG HERE

Description

WRITE DESCRIPTION HERE

Sorry, I couldn't find out how to delete this accidental copy of this post on my browser.


Power Draw Does Not Provide a UtilizationData type for Graphing #723 - Still effecting certain types of power configs

Environment

Python version: 3.6.13
Nautobot version: 1.1.2

Steps to Reproduce

Create Rack
Add power allocation with 3 phase power
Get AttributeError when viewing the rack

Expected Behavior
To view the rack.

Observed Behavior
Attribute error:
<class 'AttributeError'>

'str' object has no attribute 'numerator'

Python version: 3.6.13
Nautobot version: 1.1.2

This is related to https://github.com/nautobot/nautobot/issues/723, there is a second scenario that needs to be updated.

Thanks for the report! This looks like missing logic in the case where the power draw is not manually defined (https://github.com/nautobot/nautobot/blob/develop/nautobot/dcim/models/device_components.py#L336).


Bulk Pocket item note creation

Have the possibility to bulk create note from the Pocket sync by CTL+click or check box with.

I don't understand what you're describing. Can you describe it more clearly?

Also, is this a duplicate of #36?

Unless I'm doing something wrong here is my understanding of the actual process of creating notes from the pocket plugin in Obsidian:
calling the plugin selecting one article and repeat the process if you have multiple articles.
It will be time consuming if you want to important 200 Pocket saved articles in Obsidian this way.
I will like to have a check box in the Obsidian plugin to select all the articles that are needed to be created as notes.
It could work also like in a window explore by control clicking on multiple entry or by shift clicking two entry in the plugin to create all the not that are in between.

Are you basically trying to save your entire Pocket list onto Obsidian notes, so that you can clear out your Pocket list, but still have all of the URLs saved in Obsidian?

Yes, in a way.

Okay I understand now. I think that how this would work is not really straightforward, for the following reason: if two Pocket items have the same title (e.g. if you save two different Twitter threads from the same author, the title defaults to the author's name), what should be the right behavior?

Oh just noticed this feature request is the same as mine. My issue should be merged with this one.

How I see it is a way to know what items have been synced or not, in order to have a clear view of what have been imported and what's new. Maybe mark imported pocket items as 'imported' so that the user knows what has been done or not ?
In this case there would be an action like "sync non-imported items" that would act as bulk import but only for non-imported items. What do you think ?

@rezgi and I talked about this over DMs and got to a clear definition of what they are asking for, which is: make it possible to create Obsidian notes for all synced Pocket items that don't already have one. This functionality could be exposed as a command.
Also, the terms we used are:

syncing -> refers to syncing with the Pocket API
creating an Obsidian note -> refers to creating an Obsidian note that is associated with a particular Pocket item

We are going to avoid using the term "imported" because it was ambiguous.
@rezgi LMK if there's anything I got wrong or missed.

That's exactly it, thanks !

Hey I'm revisiting this, because #66 is done and allows for handling of Pocket items with duplicate names, amongst other challenges.
I am thinking about implementing it as follows (make the functionality as simple as possible):

A command to create Pocket item notes for all Pocket items that do not yet have notes.
A setting to automatically create Pocket item notes when new Pocket items are synced.

Please LMK if you have any feedback/comments/questions about that. I'll try to get going on that shortly.

Your suggestion #2 is exactly what I was about to add a feature request for.

This is released and available now in 0.8.0. LMK if you have any issues and if this meets your needs.

It's perfect!


Fix sporadic blacklist spec

Even though we stub_const for our classes (so they go away) It isn't for a number of gc cycles until it will get cleared up
in the meantime, it will be returned from Class#subclasses
Solution: punt. let it return from subclasses.
But put a more robust implementation into our temporary ExtManagementSystem So they behave properly and don't freak out the blacklist specs
Fixes #23152
reproducer:
SPEC_OPTS="--seed 3896" beer rspec spec/models/mixins/supports_feature_mixin_spec.rb spec/models/blacklisted_event_spec.rb

update:

removed extra tracker code that is no longer necessary (since we've upgraded to rails 7.0/ruby 3.1)
fix indentation/single line method definition (cops)

update:

fixed trailing whitespace

update:

Documented why we defined blacklisted_event_names class.


Fix lower limit for number of cases; y-ticks are now just numbers

This MR addresses #33, though I'm not sure if I fixed all cares. I only checked Germany and a random country.
Also I added ScalarFormatter to improve readability of y-axis: now there are just numbers (1, 10, 100), not powers (10⁰, 10¹, 10²).
Before:

After:

Closes #33.

Codecov Report

Merging #43 into master will decrease coverage by 0.00%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##           master      #43      +/-   ##
==========================================
- Coverage   86.17%   86.16%   -0.01%
==========================================
  Files           3        3
  Lines         593      600       +7
==========================================
+ Hits          511      517       +6
- Misses         82       83       +1

Impacted Files
Coverage Δ

coronavirus/coronavirus.py
84.76% <77.77%> (+0.01%)
:arrow_up:

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 ec99d24...9bb7ad7. Read the comment docs.

Thanks!
2 issues:
(i) Unfortunately, we have some duplication in the code at the moment, and a function make_compare_plot for countries of the wold and a function make_compare_plot_germany.
The corrections in this pull request are only done for make_compare_plot_germany'.  The same should be applied to the make_compare_plot` function (lines ~892 and following). Maybe the setting of yc_limit should then be done in a function that is called from all 4 places where the (similar) code is needed?
(ii) You have set the lower limit for deaths to 0.1, and for infections to 1.0. For both, the values <1 would originate in a rolling average, and are thus possible. I don't know if we should allow 0.1 for both? Or we argue that such small numbers are meaningless anyway. But then again we allowed 0.1 for deaths (in Germany) because that was useful for data in Hamburg.
On balance, I am tempted to try 0.1 as the lower limit for infections and cases, and to see what plots we get with this. One example that would benefit from this change is the attached (Southampton Korea, see https://oscovida.github.io/html/Korea, South.html).

I tried 0.1 as y-limit already, but then I didn't find a good usage for that and removed that part eventually. I also agree that the duplication looks bad. I'll refactor both issues tomorrow.

In the last commit I place a setup function for the lower y-limit to the plot_logdiff_time.
We use bisect now, and with it we define the lower boundary as one of the following: `[0.1, 1, 10, 100]. Right now it's unlikely we will need anything else.
NB: on some plots we may see zero as a lower boundary, but in fact that's 0.1 rounded to the closest int by ScalarFormatter.

Great, and nice idea with the bisection method. Works well for South Korea as hoped.
I have added one commit (e9f5891) to show 0.1 instead of 0.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/43095

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/43872

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/53092


On cave update lets backup the config file so pythonpath does not need to be specified again

Found some bugs, reopening


def2 bases should use the universal j and k fitting sets.

This bug in PySCF appears to be analogous to the one I recently addressed in Psi4, see https://github.com/psi4/psi4/pull/1804. It looks like the basis set exchange has erroneously had separate fitting sets for the def2 basis sets - which have not been equivalent! - whereas only a single fitting set has ever been parametrized for these basis sets.

The test failure fixed by the update is suspicious. The test case is for H2O, and the H and O Coulomb fitting basis sets have not changed at all in the update; the only changes are to the contraction coefficients of free primitives: comparing the H and O auxiliary basis sets, where for the old weigend_cfit (cfit.txt) vs def2-universal-jfit (jfit.txt)
--- cfit.txt	2020-03-08 16:11:36.988267144 +1300
+++ jfit.txt	2020-03-08 16:11:42.786312007 +1300
@@ -1,4 +1,4 @@
 BASIS "ao basis" PRINT
 #BASIS SET: (5s,2p,1d) -> [3s,1p,1d]
@@ -7,14 +7,14 @@ H    S
       3.6063578              0.0631670
       1.2080016              0.1204609
 H    S
-      0.4726794              1.0000000
+      0.4726794              0.0592485
 H    S
-      0.2018100              1.0000000
+      0.2018100              0.0051272
 H    P
-      2.0281365              1.0000000
-      0.5358730              1.0000000
+      2.0281365              1.0
+      0.5358730              1.0
 H    D
-      2.2165124              1.0000000
+      2.2165124              0.0033116
 #BASIS SET: (12s,5p,4d,2f,1g) -> [6s,4p,3d,1f,1g]
 O    S
    2876.8216605              0.1443558
@@ -25,34 +25,34 @@ O    S
      24.3864983              2.3737865
      10.6622662              0.0489414
 O    S
-      4.8070437              1.0000000
+      4.8070437             -0.1295186
 O    S
-      2.2210770              1.0000000
+      2.2210770              0.7747158
 O    S
-      1.0447795              1.0000000
+      1.0447795              0.7647816
 O    S
-      0.4968425              1.0000000
+      0.4968425              0.2369803
 O    S
-      0.2371384              1.0000000
+      0.2371384              0.0208099
 O    P
      64.2613382             -0.0126659
      16.3006076             -0.0378744
 O    P
-      4.3550542              1.0000000
+      4.3550542              0.0638078
 O    P
-      1.2019554              1.0000000
+      1.2019554              0.0169516
 O    P
-      0.3354196              1.0000000
+      0.3354196              0.0065743
 O    D
       9.2146611             -0.0597914
       2.8435251             -0.0846724
 O    D
-      0.9955759              1.0000000
+      0.9955759             -0.0466066
 O    D
-      0.3649441              1.0000000
+      0.3649441             -0.0096978
 O    F
-      2.6420115              1.0000000
-      0.7345613              1.0000000
+      2.6420115              1.0
+      0.7345613              1.0
 O    G
-      1.3931000              1.0000000
+      1.3931000             -0.0016533

which should not affect any results. Does PySCF not normalize (auxiliary) basis functions?

Pyscf normalizes AO basis but does not change the phase of the basis. So this line
 +      4.8070437             -0.1295186

can lead to different sign in the integrals


DUPLO-20994 TF provider: Azure: Storage Account: Add support for  Blobs, Queues and Tables.

Overview
Implementation of storage class resources
Summary of changes
Implementation of 'duplocloud_azure_storageclass_blob', 'duplocloud_azure_storageclass_queue', 'duplocloud_azure_storageclass_table' resources
This PR does the following:

Implemented CURD operations of 'duplocloud_azure_storageclass_blob', 'duplocloud_azure_storageclass_queue', 'duplocloud_azure_storageclass_table' resources
Added example
Updated documentation

Testing performed

[ ] Using unit tests
[ ] Manually, on my local system
[ ✓] Manually, on a remote test system

Describe any breaking changes

...

Task linked: DUPLO-20994 TF provider: Azure: Storage Account: Add support for  Blobs, Queues and Tables.


Put a line in middle

Hi,
How do I put a specific line into view in the middle on screen?
Regards,

What I mean is I want to move/scroll the yellow line to the middle of screen:

I haven't tested it, as it's just an idea but I'm imagining that if you get the line number, then get the position of a line that is half of the visible line count down the page, and use the ScrollCaret to go to that line, you could do it. You could even then reset the caret's position to the line you wanted afterwards.

I use Lines[lineNumber].EnsureVisible(); to make sure the line is always visible. But that puts it to the last line of the view.
How do I know how many lines can be displayed in my view?

I can see FirstVisibleLine but what is the last visible line?

Scintilla.FirstVisibleLine + Scintilla.LinesOnScreen. See Issue #141.
I'm not sure this is what you're looking for, but Scintilla also has ways of restricting the caret from going to close to the edge of the screen -- which could help to center your line on the screen -- but I'm not sure. You can read a little about it in the original Scintilla documentation under the topics, SCI_SETXCARETPOLICY and SCI_SETVISIBLEPOLICY. I've never implemented these features in ScintillaNET because I honestly can't make sense of the documentation...

Thanks LinesOnScreen was what I was after.


JAVA-720: Surface the co-ordinator used on query failure.

Summary of changes:

New interface CoordinatorException that exposes the coordinator address.
Existing exceptions have been retrofitted to implement the new interface where applicable (binary compatibility is preserved).
A new copy(InetSocketAddress) method was added to exceptions that are instantiated when decoding error responses (UnavailableException, ReadTimeoutException, WriteTimeoutException, AlreadyExistsException); the rationale behind is that the coordinator address is not available when they are decoded, but the already-existing copy mechanism could be easily extended to allow injection of the coordinator address in the copied exception. (See Responses.Error.asException(InetSocketAddress).
ExceptionsTest: moved to exceptions subpackage, unit tests were redesigned.

Looks ready to go.

This is looking good to me :+1:!  I've added additional tests to test all the other exceptions using scassandra in commit 3331a2c7 that i'll incorporate once a version of scassandra is released that contains that functionality.


tts,stt: add FallbackAdapter

usage:
text_to_speech = tts.FallbackAdapter(
    openai.TTS(),
    cartesia.TTS(),
    # any others that you may want...
    cooldown=30,
)

notes:

[TTS] relies on sample rate and channel being the exact same across all TTS providers. won't initialize if not the case
only sets capabilities.streaming to true if all providers support it
doubles as a timeout adapter, if you only set one provider (update: we've decided providers should handle their own timeouts)
if cooldown > 0 then it reactivates a provider after cooldown seconds

issues:

[x] doesn't work with openai for some reason? it publishes data fine but then after it's done RTC complains about mismatched audio sources
[x] TTS streaming throws an error after it's done (see note in source)
[x] i haven't actually checked that it switches when a provider fails, yet. dunno how to make that happen

[ ] switches tested working between transcriptions, still haven't tested what happens mid-transcription

[x] timeouts are currently not preset to anything, need to figure out what a good threshold is set to 5s/120s to match our OpenAI timeout
[x] STT FallbackAdapter untested with plain recognize, will test later, but streaming works great
[x] need to remember to write tests when it's ready

feedback, nits, etc appreciated

this is almost ready to review, just one bug left to squash:
with unlucky enough timing, a new sentence could be pushed to the stream just as the timeout hits 0, but since the stream is active it thinks it timed out. need to figure out a way to refresh the timer

this should be the entire FallbackAdapter implementation done. can be merged once streams handle their own timeouts, which i'll do in a different PR

Awesome. Cartesia went down during a user test yesterday, so I'm excited for this!

Any update on this?

we're now working on this over here: https://github.com/livekit/agents/pull/1074


HADOOP-19001. LD_LIBRARY_PATH is missing HADOOP_COMMON_LIB_NATIVE_DIR

Description of PR
LD_LIBRARY_PATH is missing HADOOP_COMMON_LIB_NATIVE_DIR
JIRA: HADOOP-19001
How was this patch tested?
Test in a production environment
For code changes:
Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

@zhuzilong2013 I think you can use hadoop_add_ldlibpath in your shell profile.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
17m 14s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 22s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
38m  0s

trunk passed

+1 :green_heart:
compile
18m 23s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
16m 48s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
mvnsite
2m 34s

trunk passed

+1 :green_heart:
javadoc
2m 12s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 48s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
shadedclient
41m 30s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 28s

the patch passed

+1 :green_heart:
compile
17m 22s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
17m 22s

the patch passed

+1 :green_heart:
compile
16m 33s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
16m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
2m 29s

the patch passed

+1 :green_heart:
shellcheck
0m  4s

No new issues.

+1 :green_heart:
javadoc
2m  6s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 47s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
shadedclient
42m 56s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
19m 41s

hadoop-common in the patch passed.

+1 :green_heart:
unit
5m 40s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
asflicense
0m 58s

The patch does not generate ASF License warnings.

261m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6367/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6367

Optional Tests
dupname asflicense mvnsite unit codespell detsecrets shellcheck shelldocs compile javac javadoc mvninstall shadedclient xmllint

uname
Linux 5fe6c806baf5 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 723d10ba6f5a32bc6b0b3c3e427ae2e8ede70633

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6367/1/testReport/

Max. process+thread count
2144 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6367/1/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@iwasakims Thank you for your reply！
Can I consider the 'export LD_LIBRARY_PATH' in function 'hadoop_finalize_libpaths' to be redundant?


Only evaluate julia lazily in flake.nix

fixes #410

Hey can you run alejandra on the repo and push a new commit? The CI is failing because of the linter.
alejandra is in the devShell so you can run
nix develop
pre-commit run --all

Great suggestions I will update the MR, thanks

Sorry for the force push I wasn't aware of the other commits made. I hope it's Ok now

Sorry for the force push I wasn't aware of the other commits made. I hope it's OK now

No worries. I had just caught the branch up to main so the CI would run properly. Looks like you did the same.

Thanks for the fix @djacu


I can't get rspec to run

Hi,
I've just installed a new rails project with orats using version 5.1.1 (thank you). However I keep getting an error when I attempt to run the test suite, I've installed RSpec as normal and added a simple test spec. I've tried modifying this a few times with no luck, heres the error:
An error occurred while loading ./spec/features/test_spec.rb.
Failure/Error: require File.expand_path('../../config/environment', __FILE__)

LoadError:
  cannot load such file -- /app/spec/config/environment
# /usr/local/bundle/gems/activesupport-5.1.1/lib/active_support/dependencies.rb:292:in `require'
# /usr/local/bundle/gems/activesupport-5.1.1/lib/active_support/dependencies.rb:292:in `block in require'
# /usr/local/bundle/gems/activesupport-5.1.1/lib/active_support/dependencies.rb:258:in `load_dependency'
# /usr/local/bundle/gems/activesupport-5.1.1/lib/active_support/dependencies.rb:292:in `require'
# ./spec/support/database_cleaner.rb:3:in `<top (required)>'
# /usr/local/bundle/gems/activesupport-5.1.1/lib/active_support/dependencies.rb:292:in `require'
# /usr/local/bundle/gems/activesupport-5.1.1/lib/active_support/dependencies.rb:292:in `block in require'
# /usr/local/bundle/gems/activesupport-5.1.1/lib/active_support/dependencies.rb:258:in `load_dependency'
# /usr/local/bundle/gems/activesupport-5.1.1/lib/active_support/dependencies.rb:292:in `require'
# ./spec/rails_helper.rb:9:in `block in <top (required)>'
# ./spec/rails_helper.rb:9:in `each'
# ./spec/rails_helper.rb:9:in `<top (required)>'
# ./spec/features/test_spec.rb:1:in `<top (required)>'

Below is the gemfile I'm using:
source 'https://rubygems.org'

git_source(:github) do |repo_name|
  repo_name = "#{repo_name}/#{repo_name}" unless repo_name.include?('/')
  "https://github.com/#{repo_name}.git"
end

gem 'rails', '~> 5.1.1'
gem 'puma', '~> 3.9'
gem 'rack-timeout', '~> 0.4'
gem 'jbuilder', '~> 2.5'
gem 'pg', '~> 0.21'
gem 'redis-rails', '~> 5.0'
gem 'sidekiq', '~> 5.0'
gem 'sass-rails', '~> 5.0'
gem 'uglifier', '>= 1.3.0'
gem 'jquery-rails', '~> 4.3'
gem 'turbolinks', '~> 5'
gem 'font-awesome-rails', '~> 4.7'
gem 'foundation-rails', '~> 6.3', '>= <IP_ADDRESS>'
gem 'simple_form', '~> 3.5'
gem 'devise', '~> 4.3'
gem 'pundit', '~> 1.1'
# gem 'clockwork', '~> 2.0'
# gem 'kaminari', '~> 0.17'

group :development, :test do
  gem 'byebug', platform: :mri
  gem 'rspec-rails', '~> 3.6'
  gem 'capybara', '~> 2.14'
  gem 'selenium-webdriver'
  gem 'factory_girl_rails', '~> 4.8'
  gem 'reek', '~> 4.7', '>= 4.7.1'
end

group :development do
  gem 'rack-mini-profiler', '~> 0.10'
  gem 'web-console', '~> 3.3.0'
  gem 'listen', '>= 3.0.5', '< 3.2'
  gem 'spring'
  gem 'spring-watcher-listen', '~> 2.0.0'
end

group :test do
  gem 'database_cleaner', '~> 1.6', '>= 1.6.1'
  gem 'shoulda-matchers', '~> 3.1', '>= 3.1.1'
  gem 'faker', '~> 1.7', '>= 1.7.3'
  # gem "simplecov"
  # gem "codeclimate-test-reporter", "~> 1.0.0"
end

gem 'tzinfo-data'

My fault, I didn't notice it was referring to database_cleaner in the trace, removing the database_cleaner.rb file made it work apologies!

No problem. Glad to see all is working with rspec (I don't use it personally but I know a lot of people do).


Camera rotation around specified origin

When rotating the camera about a specified origin, it slowly (but exponentially) gets further away from said origin.

Deleted the function, use lookAt() in combination with moving to reproduce rotating around a focused origin


Fix README

org-auto-tangle-mode symbols value is nll. I think you forgat '.

Thank you again @kamoii.


discoverSomeServicesAndCharacteristics order

I'm trying to use discoverSomeServicesAndCharacteristics but I can't understand in which order characteristics are returned...
Any suggestion on how to find and use just few characteristics?
Thanks

@llemtt

I'm trying to use discoverSomeServicesAndCharacteristics but I can't understand in which order characteristics are returned...

The order should match the order the peripheral has them set to.


Duplicates with Microsoft.Extensions.* / System packages

I think we can omit duplicated lines for these packages.

It's a good suggestion that may improve the readability of the generated file. However, they are still third-party dependencies, even if they come from Microsoft and they are under the MIT license, so they should be included. I think it's not possible to just ignore them because they are coming from the same publisher as they are shipped as separate products.
However, we could group them together so it's easier to read.


Any guideline?

Thanks for your well-structured code. But the current readme is too concise. Could you add some guidelines? Even a usage example is very helpful!

Em... Even the dataset file is missing. Without detailed instruction, it's really hard to use this project.😭

Also, what is args.nbr_file in this line?
https://github.com/RockyLzy/TextDefender/blob/cc60d0a9841781a09ddc6e281b80048a4a6137af/main.py#L586

Also, what is args.nbr_file in this line?
https://github.com/RockyLzy/TextDefender/blob/cc60d0a9841781a09ddc6e281b80048a4a6137af/main.py#L586

I guess it's this file. Not really sure.

No. It should be this file.
https://github.com/RockyLzy/TextDefender/blob/901977e29ea9f7b10add3b1425c75e508fa6d5e9/trainer/dne.py#L40
Please provide this json!

Ohhhh! I find it here https://github.com/dugu9sword/dne/blob/master/external_data/euc-top8-d0.7.json

Looks like this project is out of maintenance. Close this issue.

Also, what is args.nbr_file in this line?
https://github.com/RockyLzy/TextDefender/blob/cc60d0a9841781a09ddc6e281b80048a4a6137af/main.py#L586

I guess it's this file. Not really sure.

Reading the paper carefully I noticed that in 4.2. Specifically, we use the counter-fitting vectors (Mrkši´ cet al., 2016) to generate the synonym set for attackers, and use vanilla Glove Embedding (Pennington et al., 2014) to generate synonym set for defender. This means we do not need external resource for fair comparison. And this resource is only used to create Table 6. So code is commented.


running errors: GLSL 4.30 is not supported.

When running the codes, it showed the errors
Status: Using GLEW 1.13.0
--> Shader laden...
Compiling Vertex shader
vertexShaderErrorMessage: 0:1(10): error: GLSL 4.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, 3.10 ES, and 3.20 ES

Compiling Fragment shader
fragmentShaderErrorMessage: 0:1(10): error: GLSL 4.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, 3.10 ES, and 3.20 ES

programErrorMessage: error: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shader
Compiling Compute shader
computeShaderErrorMessage: 0:1(10): error: GLSL 4.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, 3.00 ES, 3.10 ES, and 3.20 ES
0:0(0): error: Compute shaders require GLSL 4.30 or GLSL ES 3.10

Then, I checked my computer with glxinfo and it shows
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (CHV)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.2.6
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 20.2.6
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 20.2.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

It seems that my computer supports 4.6 Core profile.   How do I know if my computer supports GLSL 4.30 or not? Thank you!

The issue seems to be, that I don't explicitly ask for an OpenGL core version 4.3, but pretty much any version (which should default to the highest available normally). In your case, it seems like it returns a compatibility context instead. And your non-core OpenGL context seems to only support GLSL in version 1.3 (line "OpenGL shading language version string: 1.30").
That should easily be fixed by requiring the actual OpenGL core context.
I tried that, but get an invalid window handle, so there is another issue somewhere (probably in my code somewhere).
What you could try is:

Comment the line 230 in file io.c ("glfwDefaultWindowHints()")
Add the following lines instead at the same position:glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE);
glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 4);
glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);
glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE);

See, if it runs like that. If it segfaults, we have the same issue and I'll see, if I can fix it..

The issue seems to be, that I don't explicitly ask for an OpenGL core version 4.3, but pretty much any version (which should default to the highest available normally). In your case, it seems like it returns a compatibility context instead. And your non-core OpenGL context seems to only support GLSL in version 1.3 (line "OpenGL shading language version string: 1.30").
That should easily be fixed by requiring the actual OpenGL core context.
I tried that, but get an invalid window handle, so there is another issue somewhere (probably in my code somewhere).
What you could try is:

Comment the line 230 in file io.c ("glfwDefaultWindowHints()")
Add the following lines instead at the same position:glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE);
glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 4);
glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);
glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE);

See, if it runs like that. If it segfaults, we have the same issue and I'll see, if I can fix it..

Thank you! A great job!  I guess it is my hardware is too outdated.
Cheers


Support customized instance name by a new UUID naming policy.

The new naming policy of register UUID.
Instance uuid is the identity of an instance, SkyWalking treat same instance uuid as one instance.if empty, SkyWalking agent will generate an 32-bit uuid. Using NAME: as UUID prefix could set the customized instance name. Such as, set it as NAME:SVR-INSTANCE-A,  SVR-INSTANCE-A is the instance name. Otherwise, use ServiceName-pid:id@hostname as the instance name.
To be noticed, this policy will be used in client-js subproject. As the browser side, it should not register based on client IP, that will be uncountable. At the same time, the agent user could use this if they don't like our existing name policy.

Codecov Report

Merging #4148 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #4148      +/-   ##
==========================================
- Coverage   27.18%   27.18%   -0.01%
==========================================
  Files        1145     1145
  Lines       25100    25105       +5
  Branches     3629     3631       +2
==========================================
  Hits         6824     6824
- Misses      17670    17675       +5
  Partials      606      606

Impacted Files
Coverage Δ

...ovider/handler/v6/grpc/RegisterServiceHandler.java
0% <0%> (ø)
:arrow_up:

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 6af14a3...62a92b7. Read the comment docs.


fix: conversation screen padding

This PR resolves [https://artsy.slack.com/archives/C02BAQ5K7/p1733774877736639?thread_ts=1733472979.842869&cid=C02BAQ5K7]
Description
This PR fixes the header padding issues on the conversation screen.

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a [feature flag], or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an [app state migration], or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
#nochangelog

Warnings

:warning:

✅ No changelog changes

  Generated by :no_entry_sign: dangerJS against c7f59bec90dbdee1b14e530ec2cdef5988af9785


[z3] Update to 4.8.16

Describe the pull request

What does your PR fix?
Nothing in particular, but Z3 now uses Python3 which might be relevant to #24190 (edit: looks like that issue is for the error message related to Homebrew and not related to a Python2-3 version change)

Which triplets are supported/not supported? Have you updated the CI baseline?
Yes

Does your PR follow the maintainer guide?

Yes

Getting rid of Python2 use == <3 from me! Thanks for the update!


Uncaught TypeError: Cannot read property 'focusTerminal' of null

[Enter steps to reproduce:]

...
...

Atom: 1.15.0 x64
Electron: 1.3.13
OS: Mac OS X 10.12.3
Thrown From: termination package 0.5.0
Stack Trace
Uncaught TypeError: Cannot read property 'focusTerminal' of null
At /Users/Gibson/.atom/packages/termination/lib/status-bar.coffee:26

TypeError: Cannot read property 'focusTerminal' of null
    at /packages/termination/lib/status-bar.coffee:26:46)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/app.asar/src/command-registry.js:259:29)
    at /app.asar/src/command-registry.js:3:59
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:599:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:390:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/app.asar/src/window-event-handler.js:106:36)
    at /app.asar/src/window-event-handler.js:3:59)

Commands
     -0:04.6.0 termination:focus (input.hidden-input)

Non-Core Packages
atom-fix-path 0.1.0
atom-terminal 0.8.0
atomic-emacs 0.10.0
autocomplete-haskell 0.7.2
build 0.67.0
busy 0.7.0
busy-signal 1.3.0
haskell-ghc-mod 1.19.7
ide-haskell 1.9.6
ide-haskell-cabal 1.9.0
ide-purescript 0.15.3
ink 0.6.5
intentions 1.1.2
language-babel 2.56.2
language-elm 1.5.0
language-haskell 1.12.1
language-matlab 0.2.1
language-purescript 0.8.2
linter 2.1.0
linter-elm-make 0.23.1
linter-eslint 8.1.4
linter-hlint 1.0.1
linter-stylelint 3.9.0
linter-ui-default 1.1.0
lisp-paredit 0.5.5
Parinfer 1.17.0
proto-repl 1.4.17
Stylus 3.1.0
termination 0.5.0

Thanks for the report! I'll look into it.
I don't have a mac so I might need you to do some testing; is that okay?

(Sorry, didn't mean to close it.)

No worries, I'm happy to help.  I was attempting to switch to the terminal window (cmd-option-f) when it wasn't open.  As long as the terminal window is open (ctrl-~) then atom won't throw the error.  Perhaps you catch the error and display a friendly "No terminal window is open" message before atom throws throws the error?  Thanks!

@adkelley I've just added a PR from upstream that should hopefully fix this. Can you do
apm uninstall termination
apm install Fred-Barclay/termination

to get the latest code in this repo and see if it works?
Currently it's just set to do nothing if a terminal window isn't opened, but I might change that based on how well this works. 😄
Thanks!

Yes. It's working for me.  Thank you!

Awesome, thanks!
I'll push out a new version in a few hours, then.

Glad that my fix helped! :)

@pietrodn Thanks so much! 😁


add true can-i check to make sure the operator has the permissions it needs

fixes: https://github.com/kiali/kiali/issues/3241
associated Helm Chart PR: https://github.com/kiali/helm-charts/pull/70
Do NOT merge until the Ansible Operator SDK we are using has the community.kubernetes collection with the bug fix (we need at least 1.1). Right now we only have 0.11 so the bug fix isn't available for us to use yet:
$ docker run -it --rm  --entrypoint ''  quay.io/openshift/origin-ansible-operator:4.7.0 cat /opt/ansible/.ansible/collections/ansible_collections/community/kubernetes/MANIFEST.json | grep version
  "version": "0.11.1",

This should be ready for review. To test this, install the operator via helm with the option --set clusterRoleCreator=false. Then create a Kiali CR with spec.deployment.accessible_namespaces=['**']. The operator should abort with an understandable error.

Hmm.. this worked a couple months ago when I put this together, but now with the latest stuff I can't see to get it to work.

I don't understand what's going on. Since this is not really needed, putting this on the backburner for now. Do not merge.
For some reason, that can-i check says it is not allowed, but it is allowed when operator is installed with the proper role. I don't know why this is.
If I run this in a standalone playbook, it all works as expected:
- hosts: localhost
  gather_facts: no
  vars:
    ansible_python_interpreter: python3
  collections:
  - community.kubernetes

  tasks:

  - k8s:
      state: present
      definition:
        apiVersion: authorization.k8s.io/v1
        kind: SelfSubjectAccessReview
        spec:
          resourceAttributes:
            group: rbac.authorization.k8s.io/v1
            resource: clusterroles
            verb: create

$ ansible-playbook -v ansible-test.yaml
No config file found; using defaults
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not
match 'all'

PLAY [localhost] *************************************************************************************************

TASK [k8s] *******************************************************************************************************
changed: [localhost] => {"changed": true, "method": "create", "result": {"apiVersion": "authorization.k8s.io/v1", "kind": "SelfSubjectAccessReview", "metadata": {"creationTimestamp": null, "managedFields": [{"apiVersion": "authorization.k8s.io/v1", "fieldsType": "FieldsV1", "fieldsV1": {"f:spec": {"f:resourceAttributes": {".": {}, "f:group": {}, "f:resource": {}, "f:verb": {}}}}, "manager": "OpenAPI-Generator", "operation": "Update", "time": "2021-07-28T19:21:31Z"}]}, "spec": {"resourceAttributes": {"group": "rbac.authorization.k8s.io/v1", "resource": "clusterroles", "verb": "create"}}, "status": {"allowed": true}}}

PLAY RECAP *******************************************************************************************************
localhost                  : ok=1    changed=1    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

Notice  "status": {"allowed": true}
But when I run that task within the operator (and the operator can create the clusterroles), that can_i check says it is not allowed:
TASK [default/kiali-deploy : Determine if the operator can support accessible_namespaces=** - can_i create clusterroles] ***
changed: [localhost] => {"changed": true, "method": "create", "result": {"apiVersion": "authorization.k8s.io/v1", "kind": "SelfSubjectAccessReview", "metadata": {"creationTimestamp": null, "managedFields": [{"apiVersion": "authorization.k8s.io/v1", "fieldsType": "FieldsV1", "fieldsV1": {"f:spec": {"f:resourceAttributes": {".": {}, "f:group": {}, "f:resource": {}, "f:verb": {}}}}, "manager": "OpenAPI-Generator", "operation": "Update", "time": "2021-07-28T19:16:26Z"}]}, "spec": {"resourceAttributes": {"group": "rbac.authorization.k8s.io/v1", "resource": "clusterroles", "verb": "create"}}, "status": {"allowed": false}}}

Notice: "status": {"allowed": false}
But the operator's ClusterRole has that permission:
$ kubectl get clusterrole kiali-operator -o jsonpath={.rules[10]} | jq
{
  "apiGroups": [
    "rbac.authorization.k8s.io"
  ],
  "resources": [
    "clusterrolebindings",
    "clusterroles",
    "rolebindings",
    "roles"
  ],
  "verbs": [
    "create",
    "delete",
    "get",
    "list",
    "patch",
    "update",
    "watch"
  ]
}

I found the problem - do not specify the version in the group. So this:
        spec:
          resourceAttributes:
            group: rbac.authorization.k8s.io/v1

should be this:
        spec:
          resourceAttributes:
            group: rbac.authorization.k8s.io

I tested with and without the permission on both minikube and OpenShift, everything works now.
To test on minikube, follow the instructions above in this comment: https://github.com/kiali/kiali-operator/pull/307#issuecomment-888467835


[Feature] Support for Auto-Injection of traceId in JsonLayout for log4j2

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Is your feature request related to a problem? Please describe.
Currently, apm-toolkit-log4j-2.x only supports the auto-injection of traceId for logs using PatternLayout. As a result, logs that use JsonLayout do not include the traceId, which makes tracing of log events challenging when logs are in JSON format.
https://logging.apache.org/log4j/2.x/manual/layouts.html#JSONLayout
Feature Description
It would be beneficial to enhance apm-toolkit-log4j-2.x to support the auto-injection of traceId in logs using JsonLayout. This feature would ensure that traceId is included in log events, regardless of whether PatternLayout or JsonLayout is used, thus making the tracing of log events consistent across different log formats.
Describe alternatives you've considered
A workaround for this issue is to manually insert the traceId into each log event that uses JsonLayout. However, this approach is not optimal, as it requires additional coding effort and can lead to inconsistencies in how traceId is included in log events.
Additional context
Enabling support for auto-injection of traceId in JsonLayout will be highly advantageous for applications that rely on JSON-formatted logs, and it will enhance the adaptability and usability of Skywalking APM in varied logging environments.
Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?

[X] Yes I am willing to submit a pull request on my own!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@yankooo Do you have an estimated time for this?

No update in 2 weeks. This seems a feature suggestion only.


Who wins when two extensions change the DrillDownPageId property of a table?

I have two extensions.
Both change the DrillDownPageId property of the same table.
who wins?

Duplicate of #19132


Create Bishop moves  for light pieces

A function for Bishop moves, it generates all possible for Bishop pieces
while making sure pieces doesn't go off board and jump over pieces
it captures enemy pieces (dark) and stop at that square.

will make changes


redis: 7.2.3 -> 7.2.4

Description of changes
Fixes CVE-2023-41056.
https://github.com/redis/redis/releases/tag/7.2.4

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

Also built pkgsStatic.redis.

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

I'm a bit surprised by the amount of rebuilds. The last upgrade in #264857 was far more reasonable. Did I miss something?

Rebased on top of staging.

Tested when still on master. Builds, macos 12 x86_64. passthru.tests passes nixos x86_64. pkgsStatic, pkgsCross.aarch64-multiplatform, pkgsi686Linux variants build.

Sadly this doesn't include https://github.com/redis/redis/pull/12887 and I currently cannot compile redis...

I have a strong suspicion that this is because of #264024


Adding anes2020

Documented topics

Might be a way to check the spelling on a website. Maybe a vscode plugin. Would be awesome if we could do it as a GH action on PRs...


How can I check if the font file contains certain font?

I use the libgdx-freetype extension to load .ttf font file.
I have multiple fonts files. And I want to load different fonts from different files.(For example,loading Japanese fonts from a Japanese font file,loading English fonts from a English font file)
But I did not find a way for libgdx-freetype to check whether the font glyph exists.
How can I do it? Thanks.

Adding to that it would be cool if the generator could  support fallback fonts on its own for this reason.

So, this is definitely hacky, but...
GlyphLayout glyph = new GlyphLayout(font, char);
if (glyph.width > 0) exists = true;
else exists = false;

I've written some code before to iterate something similar; it used this type of thing:
public static boolean exists(BitmapFont font, char c) {
  return font.getData().getGlyph(c) != null;
}

Fair warning, I don't know how well this behaves if there is a non-null missingGlyph set in the font's data. This would require the BitmapFont to already have been generated by gdx-freetype, so that might be an issue in your case (not sure).
Regarding the earlier answer, glyph.width can be 0 in some cases, but I'm not sure if gdx-freetype correctly handles them anyway. Combining marks generally have zero width, as do the appropriately-named zero-width space, zero-width joiner, etc.

I've written some code before to iterate something similar; it used this type of thing:
public static boolean exists(BitmapFont font, char c) {
  return font.getData().getGlyph(c) != null;
}

Fair warning, I don't know how well this behaves if there is a non-null missingGlyph set in the font's data. This would require the BitmapFont to already have been generated by gdx-freetype, so that might be an issue in your case (not sure).
Regarding the earlier answer, glyph.width can be 0 in some cases, but I'm not sure if gdx-freetype correctly handles them anyway. Combining marks generally have zero width, as do the appropriately-named zero-width space, zero-width joiner, etc.

I noticed that the FreeTypeFontParameter has a characters field with comment "The characters the font should contain". (ref: https://github.com/libgdx/libgdx/wiki/Gdx-freetype#how-to-use-gdx-freetype-in-code)
And "generator.generateFont(parameter);" will only return the font specified in "characters" field.
It is still impossible to know whether a font file contains a glyph.

If you want all characters present in a .ttf file, long ago in the distant past I found a Windows utility called cmaptofile. The cmap table is part of a TTF font (maybe OTF too, not sure) that stores all glyphs present in the font. The tool is easy to use; extract the one .exe file and drag+drop a .ttf font on it. It will output a .txt file in the same folder with the full contents, which you can paste directly into Hiero or the characters field. I am sure a similar tool could be written in Java, but no one has yet to my knowledge. Here's the zipped Windows .exe for cmaptofile:
cmaptofile.zip
I'd like to find the author's site again, but if I remember it right, this file was no longer linked from the main page, and was just in an unsorted pile of binaries useful for font manipulation. I also think I found the author's site from a typography forum that no longer is online.

I noticed that freetype privodes FT_Get_Char_Index function to check whether the font exists.
I also found the com.badlogic.gdx.graphics.g2d.freetype provides getCharIndex method.
This may only require a small modification.
Should I fix it? @Frosty-J @tommyettinger @lyze237

Sure, why not? This isn't an informed opinion - I just like to see things happen, both good and bad.

I noticed that I need modify change file.
How do I modify this file? What's the version number?
Thanks. @Frosty-J

You can just write a brief description of your change in there when making the rest of the pull request. New changes are being written under the 1.10.1 section.
The next version should be 1.11.0 due to breaking changes, but there doesn't seem to be any rhyme or reason to libGDX version numbers for the most part so just go with 1.10.1.

Fixed. #6703
Geart :->


Adding english-language description of final policy expr boolean evaluation

With RFD#0004, Hipcheck can handle an unlimited number of analyses, but we lose the hard-coded semantic information that made the report human-readable (i.e. the knowledge of concern format / output units and meaning was embedded into the code). When a plugin analysis fails by comparison, all we do currently is say "X was the output, the policy was Y". Printing these policies raw in the report output is not very ergonomic.
By necessity, the top of the AST for a policy expression must be an operation that returns a boolean. Investigate to what extent we can provide english language descriptions for this final operation, combined with the default_query_explanation() that each plugin provides, to give a generated explanation of why the policy fails. To start, I think limiting this to just the top-level boolean-returning op and its immediate operands is a good goal.
e.g.
entropy, (eq 0 (count (filter (gt 8.0) $))) --> "expected the number of commit entropies passed through (count (filter (gt 8.0) $)) to equal 0, was X"
review (lte $ 0.05) --> "expected the percent of commits receiving review  to be less than 0.05, was X"

This will likely rely on #371 , as we need a structured JSON-pointer type to know which operand of the top-level boolean expression contains the metric data.
Also, should be able to "collapse" any portion of the expression that does not rely on JSON-pointer data. So when we handle (eq (sub 10 5) ..) we should be able to evaluate the entire first operand


Overriding Object#method

In dsl/endpoint you are overwriting http://ruby-doc.org/core-2.2.3/Object.html#method-i-method and preventing it from being called. I'd suggest renaming

There is an option to turn it off, along with http_method being another way to access the same information. It hasn't seemed to cause an issue yet.


Master

Support global environment HDRCubeTexture type.

Added parsedData.environmentTextureType = “BABYLON.HDRCubeTexture”
option

Added parsedData.environmentTextureSize HDR option

Added parsedData.environmentTextureRotationY HDR option

I guess so... didnt know you added to CubeTexture. I originally added to
HDRCubeTexture to fix the 90 degress rotation issue when use panorama hdr
images.
But your right, it should rotate via the matrix so would be fine to add
that support for general purpose reflection rotation support
On Tue, Apr 24, 2018, 7:54 AM sebavan<EMAIL_ADDRESS>wrote:

@sebavan commented on this pull request.
In src/Loading/Plugins/babylon.babylonFileLoader.ts
https://github.com/BabylonJS/Babylon.js/pull/4201#discussion_r183825232:

@@ -680,7 +680,16 @@

             // Environment texture
             if (parsedData.environmentTexture !== undefined && parsedData.environmentTexture !== null) {

               scene.environmentTexture = CubeTexture.CreateFromPrefilteredData(rootUrl + parsedData.environmentTexture, scene);

               if (parsedData.environmentTextureType && parsedData.environmentTextureType === "BABYLON.HDRCubeTexture") {

                   var hdrSize:number = (parsedData.environmentTextureSize) ? parsedData.environmentTextureSize : 128;

                   var hdrTexture:BABYLON.HDRCubeTexture = new BABYLON.HDRCubeTexture(rootUrl + parsedData.environmentTexture, scene, hdrSize);

                   if (parsedData.environmentTextureRotationY) {

Would it not help if ppl wanted to rotate the environment lighting with
prefiltered data ?
We added the support for rotationY in cubeTexture as well for this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BabylonJS/Babylon.js/pull/4201#discussion_r183825232,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEx_p2gtnbU52LvbBYSCL6VT5rI7a1sbks5tr2bZgaJpZM4ThyKF
.


JSON-RPC: Validate Req.Params is either an array or an object and not a primitive type

JSON RPC 2.0 specs dictate request parameters to be structured; either an array or key/value pairs. We need to have a validator function in a common place (jsonrpc/message.go) as it is both used by jsonrpc/client.go and jsonrpc/sender.go.

Moved https://github.com/neptulon/jsonrpc/issues/7


Update CHANGELOG.md

Description

Notes the existence of NFRs.
Notes the recent increase in density in NFR scenarios.

Release note
This is that.
Tests
Rendered the markdown.

Closing this as this note made it into the rc CHANGELOG by other means.


Add 'no plots were produced'  warning message to mv_batch_on_aws.sh

Describe the Enhancement
If no pots were produced on AWS the command that copies the results trows an error which is misleading for users. Need to add a better message
Time Estimate
Estimate the amount of work required here.
Issues should represent approximately 4h of work.
Relevant Deadlines

NONE.*

Funding Source
NONE.
Define the Metadata
Assignee

[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required

Labels

[ ] Select component(s)
[ ] Select priority
[ ] Select requestor(s)

Projects and Milestone

[ ] Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
[ ] Select milestone to next major version milestone or "Future Versions"

Define Related Issue(s)
Consider the impact to the other METplus components.

[ ] METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy

Enhancement Checklist
See the METplus Workflow for details.

[ ] Complete the issue definition above, including the Time Estimate and Funding Source.
[ ] Fork this repository or create a branch of develop.
Branch name: feature_<Issue Number>_<Description>
[ ] Complete the development and test your changes.
[ ] Add/update log messages for easier debugging.
[ ] Add/update unit tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into develop.
Pull request: feature <Issue Number> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s), Project(s), Milestone, and Linked issues
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Close this issue.

The implementation is in METviewer-scripts repo

The implementation is in METviewer-scripts repo


error: 'rawhidData' was not declared in this scope

Hi Travis, this repo looks great!
I tried messing around with it on an Arduino Leonardo,
I'm using Arduino IDE 2.2.1
When I run the code, I get an error message:
error: 'rawhidData' was not declared in this scope
I see that in the setup function
RawHID.begin(rawhidData, sizeof(rawhidData));
Any idea where rawhidData gets declared/populated?
Thanks!

Hi! Thanks for being interested in this project! I've not looked at it in a while but I'll try to make some time over the next couple days to dive back in and clean up the project. I'll get back to you as soon as I can!

It looks like I did a code cleanup at some point and removed the declaration. I've added that back in now. The project builds, but I've not had a chance to test it on hardware yet.

Hey Travis, I messed with it a bit, though I have way more to do so I don't have anything to submit as a pull request.
but what seemed to work was replacing this:
RawHID.begin(rawhidData, sizeof(rawhidData));
with this:
RawHID.begin(writeBuffer, sizeof(writeBuffer));
I got far enough to see that Run8 recognizes it as a Raildriver, so that's awesome, now I just need to get some pots and wire up a few more controls.. Never thought I'd say it but I miss radioshack for that kind of stuff!


[slides] cp

Job d2l-zh/PR-817/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-817/


brew repository contains the old version

> brew info robscott/tap/kube-capacity
robscott/tap/kube-capacity: stable 0.5.0
kube-capacity provides an overview of the resource requests, limits, and utilization in a Kubernetes cluster

/opt/homebrew/Cellar/kube-capacity/0.5.0 (5 files, 31.0MB) *
  Built from source on 2021-04-27 at 13:56:04
From: https://github.com/robscott/homebrew-tap/blob/HEAD/Formula/kube-capacity.rb

Thanks for the tip! It looks like https://github.com/robscott/kube-capacity/pull/39 broke this. I'm not a goreleaser/homebrew expert but I may have some time to try to unbreak this in the coming weeks. Also commented in #45 with a bit more detail.


Geometry of the cone-beam projection

Hi I tried the cone-beam projection in LEAP, the detector had 200 rows and the centerRow is 100.5 (see below):

proj = Projector(use_gpu=True, gpu_device=device)
proj.leapct.set_volume(256, 256, 100, 1, 1, 0, 0, 0)
proj.leapct.set_conebeam(360, 200, 256, 1, 1.5, 100.5, 128.5, proj.leapct.setAngleArray(360, 360.0), 1000, 1500, tau=0.0, helicalPitch=0.0)
...
sino = proj.leapct.project(sino,img)
plt.imshow(sino[100,:,:].cpu().numpy(), cmap='gray')

However, the displayed projection in the 101 view looks like:

Seems that the parameter of centerRow doesn't work properly?

Actually, there ain't nothing wrong with the centerRow parameter.  It works just fine.
The problem here is how the z-slice positions were set.
There is a new release (v1.1) that I just published that uses a new definition of the z-slice positions that is much more intuitive.  I actually realized the way I was specifying z-slice locations was very strange about a week ago and made a change to the code.
Anyway, please pull the latest code (or download the latest release) and run your code again.  Everything should be centered as expected.  Sorry for the hassle.

Actually, there ain't nothing wrong with the centerRow parameter. It works just fine.
The problem here is how the z-slice positions were set.
There is a new release (v1.1) that I just published that uses a new definition of the z-slice positions that is much more intuitive. I actually realized the way I was specifying z-slice locations was very strange about a week ago and made a change to the code.
Anyway, please pull the latest code (or download the latest release) and run your code again. Everything should be centered as expected. Sorry for the hassle.

Thanks for your work! The v1.1 works now!


Update readme & user guide

Added description for GPU specific configuration files and its usage.

Hi @jkottiku ,
What is the difference between ug1main.md and this file? https://github.com/ROCm/ROCmValidationSuite/blob/master/docs/install/installation.rst?plain=1
installation.rst is what's published on the docs site. I think your updates should go there instead

Also, I'm not sure what this is about: installarchive.rst.
https://github.com/ROCm/ROCmValidationSuite/blob/master/docs/install/installarchive.rst
I'm assuming this is deprecated documentation? Is there a reason to keep this around -- not sure if this is confusing to users

Hi @jkottiku ,
What is the difference between ug1main.md and this file? https://github.com/ROCm/ROCmValidationSuite/blob/master/docs/install/installation.rst?plain=1
installation.rst is what's published on the docs site. I think your updates should go there instead

ug1main.md - User guide in github (https://github.com/ROCm/ROCmValidationSuite/blob/master/docs/ug1main.md)
docs site - Was done recently by Roopa. We are unaware how it works exactly.
Updated installation.rst as well.


add support for new session extension handling

electron 9 deprecates the use of BrowserWindow extension handling so I implemented the new way for handling extensions

Can you share a link to docs/announcement about the deprecation?

Can you share a link to docs/announcement about the deprecation?

The deprecation is documented here:

https://www.electronjs.org/docs/api/browser-window#browserwindowgetdevtoolsextensions-deprecated
https://www.electronjs.org/docs/api/browser-window#browserwindowadddevtoolsextensionpath-deprecated

Thanks :)


Ahrs doesn't work in flight.

Is it an known issue that this doesn't work in flight? I set mine on the floor and did steep turns and the roll indication of the Stratux page didn't change by more than a degree. On the other hand if I wiggled it on the floor the wiggle showed up as rolling.  I'm running v5 with the RY835AI. I assume it's only detecting uncoordinated turns.
-Robert

Yep, that's a known issue. AHRS is still very much a work in progress.
On Wed, Dec 16, 2015 at 9:37 PM, RobertGary1<EMAIL_ADDRESS>wrote:

Is it an known issue that this doesn't work in flight? I set mine on the
floor and did steep turns and the roll indication of the Stratux page
didn't change by more than a degree On the other hand if I wiggled it on
the floor the wiggle showed up as rolling I'm running v5 with the RY835AI I
assume it's only detecting uncoordinated turns
-Robert
—
Reply to this email directly or view it on GitHub
https://github.com/cyoung/stratux/issues/149.

--
Steven Sokol
408 Camelot Drive
Liberty, MO 64068
mobile: +1<PHONE_NUMBER>
fax: +1<PHONE_NUMBER>


sg OpenID slowness.

Search guard: 6.4.0-23.0
Elasticsearch: 6.4.0
Kibana: 6.4.0-14
Kibana: 6.4.0
Everything works in docker. Base images - official elastic images.
Kibana image:
FROM docker.elastic.co/kibana/kibana:6.4.0
USER root
RUN yum install wget -y
RUN wget https://search.maven.org/remotecontent?filepath=com/floragunn/search-guard-kibana-plugin/6.4.0-14/search-guard-kibana-plugin-6.4.0-14.zip
-O /tmp/search-guard-kibana-plugin-6.4.0-14.zip
RUN bin/kibana-plugin install file:///tmp/search-guard-kibana-plugin-6.4.0-14.zip
RUN chown -R kibana /usr/share/kibana
Elasticsearch image:
FROM docker.elastic.co/elasticsearch/elasticsearch:6.4.0
RUN bin/elasticsearch-plugin install -b repository-s3
RUN bin/elasticsearch-plugin install -b com.floragunn:search-guard-6:6.4.0-23.0
RUN bin/elasticsearch-plugin install -b mapper-size
RUN yum install apr -y &&
yum install openssl -y
RUN wget -O /usr/share/elasticsearch/plugins/search-guard-6/netty-tcnative-openssl-1.0.2-dynamic-2.0.7.Final-fedora-linux-x86_64.jar https://bintray.com/floragunncom/netty-tcnative/download_file?file_path=netty-tcnative-openssl-1.0.2-dynamic-2.0.7.Final-fedora-linux-x86_64.jar
Number of nodes: 39, i3.2xlarge
Kibana is working very very slow after openid integration implementation.
sg_config.yml(with openID):
searchguard:
dynamic:
license: "blabalbla"
authc:
basic_internal_auth_domain:
enabled: true
order: 0
http_authenticator:
type: "basic"
challenge: false
authentication_backend:
type: "internal"
openid_auth_domain:
http_enabled: true
transport_enabled: true
enabled: true
order: 1
http_authenticator:
type: "openid"
challenge: false
config:
subject_key: "preferred_username"
openid_connect_url: "https://blabalbla/.well-known/openid-configuration"
authentication_backend:
type: "noop"
config:
skip_users:
- "blabalbla"
- "blabalbla"
- "blabalbla"
- "blabalbla"
authz:
roles_from_myldap:
enabled: true
authorization_backend:
type: "ldap"
config:
enable_ssl: false
enable_start_tls: false
enable_ssl_client_auth: false
verify_hostnames: false
hosts:
- "blabalbla:389"
bind_dn: "cn=blabalbla,ou=blabalbla,dc=blabalbla,dc=blabalbla"
password: "{{ blabalbla}}"
rolebase: "ou=blabalbla,dc=blabalbla,dc=blabalbla"
userbase: "cn=blabalbla,dc=blabalbla,dc=blabalbla"
usersearch: "(userPrincipalName={0})"
username_attribute: "userPrincipalName"
rolesearch: "(member={0})"
userroleattribute: null
userrolename: "none"
rolename: "CN"
resolve_nested_roles: true
skip_users:
- "blabalbla"
- "blabalbla"
- "blabalbla"
- "blabalbla"
- "blabalbla"
- "blabalbla"
roles_from_another_ldap:
enabled: false
authorization_backend:
type: "ldap"
kibana.yml (with OpenID):
xpack.security.enabled: false
xpack.monitoring.enabled: true
xpack.graph.enabled: false
xpack.reporting.enabled: false
xpack.ml.enabled: false
searchguard.basicauth.login.brandimage: "/plugins/searchguard/assets/blablabla.jpg"
searchguard.basicauth.login.title: ""
searchguard.basicauth.login.subtitle: ""
searchguard.auth.type: "openid"
searchguard.openid.connect_url: "https://blablabla.okta.com/.well-known/openid-configuration"
searchguard.openid.client_id: "blablabla"
searchguard.openid.client_secret: {{ blablabla }}
elasticsearch.requestHeadersWhitelist: ["Authorization", "sgtenant"]
server.port: 80
server.host: ${HOSTNAME}
server.name: ${HOSTNAME}
elasticsearch.url: http://blablabla:9200
elasticsearch.username: "blablabla"
elasticsearch.password: {{ blablabla }}
kibana.index: ".kibana"
logging.dest: "/var/log/kibana/kibana.log"
elasticsearch.requestTimeout: 300000
=========================================================
sg_config(with ldap auth - works good):
searchguard:
dynamic:
license: "blablabla"
authc:
ldap:
http_enabled: "true"
authentication_backend:
type: "ldap"
config:
bind_dn: "cn=blablabla,ou=blablabla,dc=blablabla,dc=blablabla"
verify_hostnames: "false"
password: "blablabla"
usersearch: "(sAMAccountName={0})"
enable_ssl_client_auth: "false"
hosts:
- "blablabla:389"
username_attribute: "sAMAccountName"
skip_users:
- "blablabla"
- "blablabla"
- "blablabla"
- "blablabla"
- "blablabla"
userbase: "cn=blablabla,dc=blablabla,dc=blablabla"
enable_start_tls: "false"
enable_ssl: "false"
transport_enabled: "false"
http_authenticator:
type: "basic"
challenge: "true"
enabled: "true"
order: "1"
basic_internal_auth_domain:
http_enabled: "true"
authentication_backend:
type: "intern"
transport_enabled: "true"
http_authenticator:
type: "basic"
challenge: "true"
enabled: "true"
order: "2"
authz:
roles_from_another_ldap:
authorization_backend:
type: "ldap"
enabled: "false"
roles_from_myldap:
http_enabled: "true"
transport_enabled: "false"
authorization_backend:
type: "ldap"
config:
bind_dn: "cn=blablabla,ou=blablabla,dc=blablabla,dc=blablabla"
verify_hostnames: "false"
userroleattribute: null
rolebase: "ou=blablabla,dc=blablabla,dc=blablabla"
hosts:
- "blablabla:389"
rolename: "CN"
userrolename: "none"
enable_start_tls: "false"
enable_ssl: "false"
rolesearch: "(member={0})"
password: "blablabla"
enable_ssl_client_auth: "false"
skip_users:
- "blablabla"
- "blablabla"
- "blablabla"
- "blablabla"
- "blablabla"
resolve_nested_roles: "true"
enabled: "true"
kibana.yml (with ldap auth):
xpack.security.enabled: false
xpack.monitoring.enabled: true
xpack.graph.enabled: false
xpack.reporting.enabled: false
xpack.ml.enabled: false
searchguard.basicauth.login.brandimage: "/plugins/searchguard/assets/blablabla.jpg"
searchguard.basicauth.login.title: ""
searchguard.basicauth.login.subtitle: ""
server.port: 80
server.host: ${HOSTNAME}
server.name: ${HOSTNAME}
elasticsearch.url: http://blablabla:9200
elasticsearch.username: "blablabla"
elasticsearch.password: blablabla
kibana.index: ".kibana"
logging.dest: "/var/log/kibana/kibana.log"
elasticsearch.requestTimeout: 300000
elasticsearch.healthCheck.delay: 300000
elasticsearch.pingTimeout: 25000
=======================================================
There is no errors or something special in kibana and elasticsearch logs.
Slowness feels every where... Open dashboard (before do some queries) we see "loading..." prints on visualizations few seconds... Move between tags almost impossible - very slow. Open monitoring tag take forever.
When we changed configuration back to do ldap auth everything acting fast again...
How can we investigate and resolve this issue?

OpenID per se should be fast because after the user has logged in to the IdP and Kibana finally receives the identity token, everything is just JSON web token based.
Couple of questions:

Besides the slowness, is everything else working fine? Means, does the OpenID user has the correct Search Guard roles and can access indices according to the roles?

In the OpenID config I see that you have LDAP authorization still enabled, is this on purpose? The combination OpenID and LDPA authorization is quize unusual, so I wonder if the slowness stems from Search Guard constantly trying to fetch the role from LDAP and fails.

What always helps is to get the ES logs on debug level. Can you try to set the log level to debug:
https://docs.search-guard.com/latest/troubleshooting-setting-log-level
And then log in with OpenID again, click around, and send us the logs? If you don't want to attach the logs here, you can also send them to<EMAIL_ADDRESS>

@anton-xqz friendly ping

Closing due to inactivity.


Angular build failing in unix environment (tested on Linux AWS EC2 instance)

When trying to build aot on Linux EC2 instance the following error happens:
ERROR in<EMAIL_ADDRESS>Module build failed: Error<EMAIL_ADDRESS>is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property. The missing file seems to be part of a third party library. TS files in published libraries are often a sign of a badly packaged library. Please open an issue in the library repository to alert its author and ask them to package the library using the Angular Package Format (https://goo.gl/jB3GVv).     at AngularCompilerPlugin.getCompiledFile (/home/ec2-user/rnd/khushi-portal/node_modules/@ngtools/webpack/src/angular_compiler_plugin.js:674:23)     at plugin.done.then (/home/ec2-user/rnd/khushi-portal/node_modules/@ngtools/webpack/src/loader.js:467:39)     at <anonymous>
## Version info
Angular CLI: 1.7.3
Node: 9.5.0
OS: linux x64
Angular: 5.2.8
... common, compiler, compiler-cli, core, forms, http
... language-service, platform-browser, platform-browser-dynamic
... router

@angular/animations: 4.4.6
@angular/cdk: 5.2.4
@angular/cli: 1.7.3
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.4.2
webpack: 3.11.0

How to reproduce these conditions
Steps to set up and reproduce
Create a new project using @angular/cli (using 1.7.3)
Install angularfire2 and firebase as dependencies and connect them to the app
Run either ng serve or ng build -prod
Debug output
ERROR in<EMAIL_ADDRESS>Module build failed: Error<EMAIL_ADDRESS>is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.
The missing file seems to be part of a third party library. TS files in published libraries are often a sign of a badly packaged library. Please open an issue in the library repository to alert its author and ask them to package the library using the Angular Package Format (https://goo.gl/jB3GVv).
    at AngularCompilerPlugin.getCompiledFile (/home/ec2-user/rnd/khushi-portal/node_modules/@ngtools/webpack/src/angular_compiler_plugin.js:674:23)
    at plugin.done.then (/home/ec2-user/rnd/khushi-portal/node_modules/@ngtools/webpack/src/loader.js:467:39)
    at <anonymous>

Expected behavior
The app should build properly.
Actual behavior
The app doesn't build
NB
This works properly on windows, no issues at all. I can connect to my firebase instance and also use login with facebook feature.
I tried to follow the steps mentioned in this  Issue 1499. But it did not work for me

I can't seem to reproduce this on my PC running arch. Builds just fine, like all of my projects with angularfire2.

Issue with the Firebase JS SDK, open an issue with their github repo if it still persists; they did completely rehaul their polyfills recently.


Use collect instead of a for+insert/push.

Also, use range syntax.
This change is purely stylistic and I'm not really convinced it's cleaner than
the old version. Comments?

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks!


Added functionality to allow for multiple keys to be kept pressed and continue performing the action mapped to that key continuously. Refactored code and integrated changes with those made by Paul.

…

@bisson2000 --> I'll let you do the sanity check to ensure these can merge without issue in Unity


cannot download a file with phoenix

upload a file
try to download the file using phoenix

Result:
no output in the browser
ocis logs:
2020-10-28T11:57:59+05:45 ERR could not retrieve signing key error="{\"id\":\"com.owncloud.api.store\",\"code\":404,\"detail\":\"could not read record\",\"status\":\"Not Found\"}" service=proxy

downloading using basic auth works


Update Postman API publish on tag

Context
The Postman Git integration does not recognize tags as branches, and as a result, fails to publish the API in the Github Action.
Instead of publishing the API version from the ref being the tag, we can just publish from main when we make a new Rafiki release.

https://github.com/interledger/rafiki/actions/runs/6261328355/job/17001192672


DMR: Setup CI

AS A Developer
I WANT TO be sure my changes can be built, and tests pass when merged with the main branch
SO THAT the main branch is always functioning and 'shippable'.
Acceptance Criteria

[ ] Create Github actions which build and test the code in the DMR repo

Depends on https://github.com/buerokratt/Cross-functional-requirements/issues/18

Dependant on the design task. To be refined.

Done as part of another task


Property 'domain' not implemented to RegistroBR parser

The property 'domain' is not implemented on RegistroBR parser.
> record = Whois.whois("casarobertomarinho.org.br")
> parser = Whois::Parser.new(record)
> parser.domain
Whois::AttributeNotImplemented: Unable to find a parser for property `domain'

Correct, it's not.
https://github.com/weppos/whois-parser/blob/master/lib/whois/parsers/whois.registro.br.rb
Feel free to provide a PR. Actually, the domain property has little sense to me as it's basically whatever query you passed to the whois argument.
Any reason for needing it?

My commit fixes it:
https://github.com/anacarolinacastro/whois-parser/commit/03042612ac25792f7c8a3b1bb6241ebcf809c11b

Closed by #77


[#3067] separate message for unanticipated outage

Resolves #3067
Pull Request Checklist:

[x] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case
Difficult to test this on a local develop rig...

Deploy to one of the servers that uses nginx
Then add return HttpResponse(status=503) in one of the views. For example the dashboard.
Modify the 50X status code to check for 500, 503, 503, 504

METRIC
VALUE

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4687

thanks Scott, will revise


User defined proptype source

This is a WIP PR, The basic implementation is ready, I still need to test:

Component refs and component collections
Element collections
ref collections

Looks good so far :)

This is a WIP PR, The basic implementation is ready, I still need to test:

Component refs and component collections
Element collections
ref collections

Tests finished, this PR is ready to re review/merge


fix(README): grammar

Signed-off-by: Archit<EMAIL_ADDRESS>I found some Improper word choice as well as Improper formatting for that I have made changes and corrected that so, now It will be easier for everyone to read.
Please Merge this

@irmerk Thanks for review I updated changes and added DCO

One change, then this can be merged.

Needs DCO again

@irmerk Done

@irmerk I have Updated all changes

Thank You @irmerk

Thank You @irmerk


⚠ ClamAV has degraded performance

In 8785188, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 66 ms

Resolved: ClamAV performance has improved in 222e2f1.


How to close agent after work is done?

Hello,
I am fiddling around with build agents in docker and my target is to get a fresh agent every time.
Running the agent in Docker for Windows works as expected but the agent keeps running after a build i finished.
My question is: Can I force the agent to shutdown after his first job is finished?
Thanks for your help.
KirK

https://hub.docker.com/r/microsoft/vsts-agent/

@TingluoHuang thanks for the answer, but I do not understand.
I use this image already but this agent also keeps running after finishing his work. Maybe I got something wrong.
What I want to achieve is the same behavior like the hostet agents in VSTS. I start an agent, The agent waits for a job. After the job is done the agent should close. So my Docker environment can provide a new agent.
thanks,
KirK

@kirkone what's docker command you run? if you just docker run, the agent should got unconfigure after every build.

I run the container with
docker run -e VSTS_ACCOUNT=kirkone -e VSTS_TOKEN=xxxx...xxxx
qvkopq -it kirk/vsts-agent:windows-10.0.14393

and the agent keeps waiting for new jobs after finishing the first one.

@kirkone sorry, i was misunderstand your question, since VSTS machine management service provide similar feature for our hosted build. I don't think the agent has ability to stop after every job at this point.
What's the reason you want a fresh agent for every build? are you not only care about the working folder of each build?

the reason behind this is that people tend to break our agents by installing custom programs at build time. For example the install a new version of npm global and than other projects will fail on our "shared agents".
I thought it would be a good idea to start with a fresh copy every time.
Maybe it is a better idea to solve the root cause of our problems by convince the people not to do such things.
Regardless, I think a "use only one time" switch can provide some extra benefits to the agents in general. I'm not experienced with such things but I will try to provide a PR for this if you want.
Thank you very much,
KirK

@kirkone we have the concept of running each job inside a docker container. i think that should give you most of the isolation you want.
We have a doc here: https://github.com/Microsoft/vsts-agent/blob/master/docs/preview/runtaskindocker.md

looks promising, I will have a look.
Thank you


[MRG+1] New DICS implementation

Picking up from #4797. This is a rebased version that only contains the changes that apply to the DICS code.
Closes #3249.

I've set the defaults of make_dics to match Jan Kujala's pipeline, meaning mode='vector', normalize_fwd=True, weight_norm=False. I've documented in the notes fields of make_dics that these defaults are different from the make_lcmv ones and that it's up to the user to choose. In the DICS tutorial, we now demonstrate computing the power maps using both sets of defaults, to communicate clearly to our users that multiple approaches exist and they are encouraged to try different ways.
We should really do the simulation study sometimes. Any master students looking for a master thesis project?

See updated tutorial: https://7583-1301584-gh.circle-artifacts.com/0/html/auto_tutorials/plot_dics.html

will do tomorrow, @larsoner

@britta-wstnr +1 for merge from you?

(current Travis error is unrelated timeout)

I think I addressed all outstanding comments.

Agreed, all of my comments have been addressed even though some of them did not collapse.
@britta-wstnr @agramfort just need to agree and it can go in!

good that's quite fast !

I fear I do not have the time for another iteration today - but I had a thorough look end of last week, so good to go from my end!

As a summary, I would use option: foo, bar, or None (defaults bar) to be consistent with the rest of the codebase.

For some reason, we settled on not including the (defaults bar) at the top, but only in the narrative for the option.

@massich @agramfort Are we go for merge?

@wmvanvliet you need to rebase.

Great work!!! Looking forward to test the new code. Thanks for all your work

🍻 for @wmvanvliet !


Initial implementation of IstioControlPlane and unit tests

Includes IstioControlPlane, tests and associated helm charts, values and golden files.
helm charts are necessarily copied here because some modification are currently needed (missing separators) and some stability is needed for the tests.
Long term, need to figure out how to make the dependency more dynamic, including merging the istio/installer and operator repos.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-lint.sh
803cadedb3ab8f8ec953d293b4d0af8933c740bd
link
/test operator-lint-master

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

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-lint.sh
29af19ee29c8c240c16920b44226be211af615af
link
/test operator-lint-master

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


'do' command with script-local functions

Seeing https://github.com/junegunn/vim-plug/pull/450#issuecomment-199315671, I want to update function! BuildYCM(info) to function! s:BuildYCM(info). But it seems that, when { 'do': function('s:BuildYCM') } has been called, it has different scope.
Following is test.vimrc for testing:
set nocompatible
filetype off

call plug#begin()

function! s:Foo(info)
  echohl ErrorMsg
  echomsg 'Foo'
  echohl NONE
endfunction

Plug 'junegunn/gv.vim', { 'do': function('s:Foo') }

call plug#end()

Then running vim -u /path/to/test.vimrc immediately raises an error:
Error detected while processing /path/to/test.vimrc:
line   12:
E700: Unknown function: s:Foo

And I found a workaround trying to export Funcref variable to outside and remove it.
set nocompatible
filetype off

call plug#begin()

function! s:Foo(info)
  echohl ErrorMsg
  echomsg 'Foo'
  echohl NONE
endfunction

let FooRef = function('s:Foo')
Plug 'junegunn/gv.vim', { 'do': FooRef }
unlet FooRef

call plug#end()

I confirm that it works by running :PlugInstall! and then looking at :mess, But I'm not sure that this is a good way to invoke a script-local function on do command. Is there any simpler, cleaner way to do this?

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Mar 26 2016 21:41:37)
MacOS X (unix) version
Included patches: 1-1655
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl             +cmdline_compl   +digraphs        +folding         +libcall         +mouse_dec       +netbeans_intg   +reltime         +tag_old_static  +virtualedit     -xim
+arabic          +cmdline_hist    -dnd             -footer          +linebreak       -mouse_gpm       +packages        +rightleft       -tag_any_white   +visual          -xsmp
+autocmd         +cmdline_info    -ebcdic          +fork()          +lispindent      -mouse_jsbterm   +path_extra      +ruby            -tcl             +visualextra     -xterm_clipboard
-balloon_eval    +comments        +emacs_tags      -gettext         +listcmds        +mouse_netterm   +perl            +scrollbind      +terminfo        +viminfo         -xterm_save
-browse          +conceal         +eval            -hangul_input    +localmap        +mouse_sgr       +persistent_undo +signs           +termresponse    +vreplace        -xpm
++builtin_terms  +cryptv          +ex_extra        +iconv           -lua             -mouse_sysmouse  +postscript      +smartindent     +textobjects     +wildignore
+byte_offset     +cscope          +extra_search    +insert_expand   +menu            +mouse_urxvt     +printer         +startuptime     +timers          +wildmenu
+channel         +cursorbind      +farsi           +job             +mksession       +mouse_xterm     +profile         +statusline      +title           +windows
+cindent         +cursorshape     +file_in_path    +jumplist        +modify_fname    +multi_byte      +python          -sun_workshop    -toolbar         +writebackup
-clientserver    +dialog_con      +find_in_path    +keymap          +mouse           +multi_lang      -python3         +syntax          +user_commands   -X11
+clipboard       +diff            +float           +langmap         -mouseshape      -mzscheme        +quickfix        +tag_binary      +vertsplit       -xfontset
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation:
/usr/bin/clang -c -I. -Iproto -DHAVE_CONFIG_H   -F/usr/local/Frameworks -DMACOS_X_UNIX  -Os -w -pipe -march=native -mmacosx-version-min=10.11 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: /usr/bin/clang   -L. -fstack-protector -L/usr/local/lib -L/usr/local/opt/openssl/lib -L/usr/local/opt/readline/lib -L/usr/local/opt/libyaml/lib -L/usr/local/opt/gdbm/lib -L/usr/local/lib -
F/usr/local/Frameworks -Wl,-headerpad_max_install_names -o vim        -lm  -lncurses -liconv -framework Cocoa   -fstack-protector  -L/System/Library/Perl/5.18/darwin-thread-multi-2level/CORE -lperl
 -F/usr/local/Cellar/python/2.7.11/Frameworks -framework Python   -lruby-static -framework CoreFoundation -lobjc -L/Users/yous/.rubies/ruby-2.3.0/lib

Type:

[ ] Bug
[ ] Enhancement
[ ] Feature Request
[x] Question

OS:

[ ] All/Other
[x] Linux
[x] OS X
[ ] Windows

Vim:

[x] Terminal Vim
[ ] GVim
[ ] Neovim

Oh, right, it was my oversight. Updated the code snippet in the link. Script-local functions or variables are evaluated in the scope of plug.vim (what!?), so we need to use global ones. Likewise, this also doesn't work as expected:
call plug#begin('/tmp/plugged')
let s:opts = { 'do': 'echo 1234' }
Plug 'junegunn/gv.vim', s:opts
call plug#end()
" E121: Undefined variable: s:opts

I'm not aware of an elegant workaround. It's a bummer, but then again, let's not forget that Vimscript is merely a tool for configuring an editor. We'll probably just have to deal with it.

Thanks for the confirmation. I'm satisfied with simple let-unlet wrapping now.


Run compathelper less often

The Actions tab is full of CompatHelper runs. Running once a week should be often enough.

Auto-merge won't work because failures due to upstream things. Can you force merge manually?