Escape function name to allow < and >

Issue #, if available:
Description of changes:
Currently when CBMC-viewer encounters a name like <Sheep as Animal>::noise (a Rust name), the angled brackets are treated as HTML tags, causing the name to be displayed incorrectly in viewer traces. This patch escapes HTML characters in the function names to avoid this issue in the future.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Current status: In coverage reports, < and > are displayed as < and >. Need to find where else this could be happening and fix.

Fixed issue with coverage reports; have not found issue present anywhere else.

Removed dependency on source-language-flag PR.


How to block access to the app service for non-Teams/CC app users?

Hi there - my security team is concerned that the creation of the app service with FQDNs ccxxx.azurefd.net and ccxxx.azurewebsites.net published to the internet presents a security risk. Since Company Communicator should only be used by the Teams client, how can I ensure that only the Teams app can access the app service?
They would like to see an unauthorised/blocked response when accessing  ccxxx.azurewebsites.net and ccxxx.azurefd.net with a web browser.
I have tried implementing an access restriction allowing only the Azure front door service tag but this blocks access from the Teams app as well. I have also tried to see if an Azure conditional access policy could help, however, I do not see the app service listed as a cloud app.
I know that this may be a little off-topic but I can't seem to find any guidance elsewhere.
Please help!

Hi @infinitesimalinfo ,
Thanks for raising the query. We will get back to you with proper response soon.

Hi @gsv022,
Thanks, I'm looking forward to your response.

I guess I'm looking forward to @v-royavinash's response?

@infinitesimalinfo  As rightly pointed out the default implementation of CC does not provide any option to restrict it with in the same network. From technical point of view, app service can be configured to be accessible within the same organization. The overall idea is that the app service should be able to communicate with the Author and User bot.
However, we won't be able to help in configuring the customization as we provide support with the default version of CC.

Hi @infinitesimalinfo ,
We are closing this request as the we have provided the inputs for the query raised. If you face any issue with company communicator please raise a new issue for further assistance.


Redis update to 0.12.1

Update to 0.12.1 and fix some bugs.

redis/redis.d.ts
to authors(@soywiz @CodeAnimal). could you review this PR?
:+1: or :-1:?
check list

[ ] pass the Travic-CI test?

:+1:

ping @vvakame @soywiz @CodeAnimal

@MugeSo thanks mate!

:smile:


More efficient conversion from Python int to fmpz

It looks like Python 3.13 will provide public C API for efficiently converting to and from a PyLong. These should be compatible with mpz_import/mpz_export rather than converting between hex strings:
https://github.com/python/cpython/pull/121339
https://github.com/flintlib/python-flint/blob/430b8e50f4d8e697d4f5c7666d7b75f3e440a260/src/flint/types/fmpz.pxd#L15-L23
https://github.com/flintlib/python-flint/blob/430b8e50f4d8e697d4f5c7666d7b75f3e440a260/src/flint/types/fmpz.pyx#L16-L27

It looks like Python 3.13 will provide public C API

Nit: 3.14.  Maybe.


[FolhaDeSaoPauloBridge]: Small improvements

This is a feed expander that does an HTML request per item, which is a bit slow. The problem is that the original feed has 100 items.
Brought it down to a default 15 items, and allows for configuring the per-item request.

BTW, I did the bridge originally, but I'm pretty sure the feed had only 20 or 30 items before.

Just checked the output, LGTM


Replace urllib by request for the muspy api

Request seems easier, and will allow to add easily a force-accept for self signed certificates, useful for a self-hosted MuSpy instance.

Fixed in 806d6fb
Waiting for more tests before merging.


✨FIx the README.md

Before:

After:

Literally all i did was remove the unnecessary width tag that wasnt even being implemented in the image

Amazing! thanks for this!


Rename version-specific resource folders

Fixes #185
This removes the ambiguity in where the separation between components in version numbers lies. This would become even more of a problem should SemVer be used.
A hyphen is chosen since it is a clear separator and has no special meaning in either regular expressions (outside of character classes, which is a non-issue) or in filepaths on any sane filesystem.

(yes, the Changelog has the correct PR number despite this only being a single commit - magic!)

...failing test >.<


audioMasterProcessEvents deadlock and crash on plugin/window close fixes.

Fixed audio thread deadlock when audioMasterProcessEvents was generated from the plugin audio thread. audioMasterProcessEvents are now process async to avoid thread switching from the host/vst plugin.
Fixed issue upon X11 async message that causes plugin to hang host. Also fixed multiple airwave plugin that crash on unload if it was not in the right order.

@asb2m10 thanks for the PR, but I am not able to build your version:
[ 27%] Linking CXX executable airwave-host-32
/usr/bin/ld: skipping incompatible //usr/lib/x86_64-linux-gnu/libX11.so when searching for -lX11
/usr/bin/ld: skipping incompatible //usr/lib/x86_64-linux-gnu/libX11.a when searching for -lX11
/usr/bin/ld: cannot find -lX11
collect2: error: ld returned 1 exit status
winegcc: g++ failed
src/host/CMakeFiles/airwave-host-32.dir/build.make:251: recipe for target 'src/host/airwave-host-32' failed
make[2]: *** [src/host/airwave-host-32] Error 2
CMakeFiles/Makefile2:142: recipe for target 'src/host/CMakeFiles/airwave-host-32.dir/all' failed
make[1]: *** [src/host/CMakeFiles/airwave-host-32.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

Any idea? I am on Ubuntu 18.04 x64. rodlie's version builds fine...

Either disable the 32bit build of Airwave or install the X11 libs 32bit bindings to make it work. I'm not on ubuntu but I think if you "apt install libx11-6:i386" it should work.

Will try, thanks...

Probably a world record in slow response :smile:
Long story short: Not been doing music since 2020ish and did not get/notice any notifications regarding this repo. Anyway, wanted to fiddle a bit with some synths and noticed your PR.
The PR looks good (limited testing) and has been merged. Thanks :+1:


Implementation of the application layer

Can I assist in implementing the application layer? This way, our controllers can utilize application services instead of directly accessing repositories, thereby shifting the dependency from the infrastructure layer to the application layer

That is a fair point - there are already a lot of "Service" folders in the Web Project.
The idea is that, if you have a feature "XYZ" then there should be "XYZ/Services" to contain that logic.
If that stuff is shared across multiple features, it should reside in the "root" Service folder.
I guess you have a specific use case in mind, don't you?

I was considering implementing it as a best practice, though the project's scale is a crucial factor. The positive aspects I envision for incorporating an application layer include:
Better separation of concerns
Easier maintainability
I would love to hear your thoughts on this

I was considering implementing it as a best practice, though the project's scale is a crucial factor. The positive aspects I envision for incorporating an application layer include:
Better separation of concerns Easier maintainability I would love to hear your thoughts on this

Sorry, my question was misleading. I did grasp the general idea behind that.
I would love to know your concrete use case in mind - you said you want to access/expose something via controller that is currently internal logic of one of the Blazor components.
I am a bit reluctant to introduce a whole new layer. The current goto is to move stuff into the services. There isn't much "business" logic going on to be honest. I was also thinking of removing the Blog.Domain project at one point, as it doesn't really bring much of benefit to the table.

Don’t mention it, mate. Your question was spot on. I agree with you that adding a new layer just to implement a best practice is unnecessary. I wasn’t considering a new use case scenario, but now that you’ve mentioned it, I’ll think about one. If I come up with a fantastic use case, I’ll let you know via issues.


Curly brackets in 'Search in files' / 'files to include' field does not work as intended ?

VS Code Version: 1.89.1
OS Version: Win10 22h2 x64

Steps to Reproduce:

I have two folders in D:\data : next, other

both folders have same two files, named: C_P101F01.log, P101F01.txt

all four files contain string: 5C4266900201

in VS Code I open folder: D:\data

I try to search '5C4266900201' in 'Search in files' (Ctrl+Shift+F) ... all files are listed (that is OK):

now I try to put this '{next, other}/{*.txt, *.log}' in 'files to include' field ... the results should be the same, right? ... but no ... only first file in first folder is listed:

you have a space after the comma ,
spaces are not whitespace
they are included in the path name

Ok, I did not know that.
Maybe it should be mentioned (more) in docs.
Thank you


Gradle Tooling API handles system properties in addJvmArguments incorrectly

I've used ProjectConnection.newBuild().addJvmArguments() to define system properties on-the-fly, specifically proxy-related JVM properties. The system has certain setup in the user ~/.gradle/gradle.properties, but I wanted to one-time override these settings. The override is possible when using CLI gradlew: ./gradlew -Dhttps.proxyHost= -Dhttps.proxyPort= build effectively disables proxy for the build, although gradle.properties configures one. When launching the build programmatically, using Tooling API, this is not the case.
-D is documented as

Using the -D command-line option, you can pass a system property to the JVM which runs Gradle. The -D option of the gradle command has the same effect as the -D option of the java command.

Specifically I was trying to disable http proxy for the build run. This could be done when running the build manually from the commandline, but I was not able to achieve that when launching Gradle using its Tooling API. This is an inconsistency - whichever behaviour is correct (I believe ./gradlew is), should be applied in all cases.
Note: a possible alternative, to pass -Porg.gradle.jvmargs=... did not work either.
Expected Behavior
Tooling API will override gradle.properties values using command line parameters.
Current Behavior
Tooling API either does not apply commandline-passed system properties at all, or gave precedence to gradle.properties values over parameters configured by addJvmArguments.
Context
I am working on NetBeans support for Gradle build system. I attemtped to implement an assistive feature for the user in the case a corporate proxy is used - so the IDE detects the effective proxy settings (used, which one or not used) . If a mismatch between Gradle configuration and the actual environment is found, I've planned to offer the user an option to run the build without affecting the permanent configuration . With this bug, that option is not possible.
Steps to Reproduce
I've prepared a small sample launcher utility that passes -Dhttp.proxyHost= -Dhttp.proxyPort= through Tooling API to gradle.
tooling-api-sample.zip
Preparation:

Build the 'toolingapi' project (from the attached archive), e.g. ./gradlew distZip
Make sure the gradle distribution is installed, e.g. run ./gradlew build from the usewrapper subdirectory. Installation behind the proxy has its own issues, not covered here.
Clear the ~/.gradle/caches/modules*
Unpack the ZIP distribution from the toolingapi project somewhere
make an erroneous ~/.gradle/gradle.properties file with some arbitrary nonexistent proxy settings (assuming you test this on a proxy-free network, configured proxies will fail the build)

systemProp.http.proxyHost=aaaemea-proxy.acme.org
systemProp.http.proxyPort=80
systemProp.https.proxyHost=aaaemea-proxy.acme.org
systemProp.https.proxyPort=80

Now:

For comparison, go to usewrapper directory, run ./gradlew -Dhttps.proxyHost= -Dhttps.proxyPort= build. The build should succeed, although user gradle.properties specify a proxy
note the userwapper directory path
clear ~/.gradle/caches/modules* again to force downloads
with the built toolingapi project, run toolingapi /path/to/the/userwrapper/noted/above - this will attempt to build usewrapper project through Tooling API

The build will fail, the output will contain debugging messages similar to:
2022-11-25T14:33:28.873+0100 [DEBUG] [org.gradle.internal.resource.transport.http.HttpClientHelper] Performing HTTP GET: https://plugins.gradle.org/m2/com/github/johnrengelman/shadow/com.github.johnrengelman.shadow.gradle.plugin/6.1.0/com.github.johnrengelman.shadow.gradle.plugin-6.1.0.pom
2022-11-25T14:33:28.873+0100 [DEBUG] [org.apache.http.client.protocol.RequestAddCookies] CookieSpec selected: default
2022-11-25T14:33:28.873+0100 [DEBUG] [org.apache.http.client.protocol.RequestAuthCache] Auth cache not set in the context
2022-11-25T14:33:28.873+0100 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection request: [route: {tls}->http://aaaemea-proxy.acme.org:80->https://plugins.gradle.org:443][total available: 0; route allocated: 0 of 20; total allocated: 0 of 20]
2022-11-25T14:33:28.873+0100 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection leased: [id: 10][route: {tls}->http://aaaemea-proxy.acme.org:80->https://plugins.gradle.org:443][total available: 0; route allocated: 1 of 20; total allocated: 1 of 20]
2022-11-25T14:33:28.873+0100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Opening connection {tls}->http://aaaemea-proxy.acme.org:80->https://plugins.gradle.org:443
2022-11-25T14:33:28.875+0100 [DEBUG] [org.apache.http.impl.conn.DefaultHttpClientConnectionOperator] Connecting to aaaemea-proxy.acme.org/<IP_ADDRESS>:80
2022-11-25T14:33:29.017+0100 [DEBUG] [org.apache.http.impl.conn.DefaultHttpClientConnectionOperator] Connection established <IP_ADDRESS>:34024<-><IP_ADDRESS>:80
2022-11-25T14:33:29.159+0100 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-10: Close connection
2022-11-25T14:33:29.159+0100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] CONNECT refused by proxy: HTTP/1.1 400 Bad Request
2022-11-25T14:33:29.159+0100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Connection discarded

The messages indicate that the gradle.properties defined proxy was actually used.
Your Environment

OS Linux Ubuntu 20.04
Java(TM) SE Runtime Environment 18.9 (build 11.0.5+10-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.5+10-LTS, mixed mode)
gradle 7.4.2 and 7.5.1

Thank you for providing a valid reproducer.
The issue is in the backlog of the relevant team and prioritized by them.

There's a new API introduced in Gradle 7.6 that might solve the problem. We'll get back to you.
https://docs.gradle.org/7.6/release-notes.html#added-support-for-passing-system-properties-to-the-build-with-the-tooling-api

The issue is valid, the Tooling API cannot overwrite system properties the same way it's possible on the command line. Unfortunately, the new LongRunningOperation.withSystemProperties() method has the same semantics.

@sdedic I take my previous comments back. It seems like the Tooling API behavior is consistent with the command-line scenario, but you have to call addArguments("-Dhttp.proxyHost=") (and not addJvmArguments).

OK, will try


SR-10555 foreignCopyUTF8 should do bulk access

@swift-ci please smoke benchmark

@swift-ci please smoke benchmark

@swift-ci please smoke test

Oops, forgot to make that conditional for ObjC

https://ci.swift.org/view/Pull Request/job/swift-PR-osx-smoke-perf/902/

Performance: -O

TEST
OLD
NEW
DELTA
RATIO

Regression

EqualSubstringSubstring
34
37
+8.8%
0.92x (?)

EqualStringSubstring
34
37
+8.8%
0.92x (?)

EqualSubstringSubstringGenericEquatable
34
37
+8.8%
0.92x (?)

LessSubstringSubstring
35
38
+8.6%
0.92x (?)

Performance: -Osize

TEST
OLD
NEW
DELTA
RATIO

Regression

DataReplaceLarge
18200
19800
+8.8%
0.92x (?)

LessSubstringSubstring
35
38
+8.6%
0.92x (?)

EqualSubstringSubstringGenericEquatable
35
38
+8.6%
0.92x (?)

EqualSubstringString
35
38
+8.6%
0.92x (?)

LessSubstringSubstringGenericComparable
35
38
+8.6%
0.92x

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 8-Core Intel Xeon E5
  Processor Speed: 3 GHz
  Number of Processors: 1
  Total Number of Cores: 8
  L2 Cache (per Core): 256 KB
  L3 Cache: 25 MB
  Memory: 16 GB

Alas, will have to write some new benchmarks

@swift-ci please smoke benchmark

Performance: -O

TEST
OLD
NEW
DELTA
RATIO

Regression

LessSubstringSubstring
39
43
+10.3%
0.91x (?)

DataReplaceLarge
20400
22400
+9.8%
0.91x (?)

ObjectiveCBridgeStubToNSDate2
1370
1480
+8.0%
0.93x (?)

EqualSubstringSubstring
38
41
+7.9%
0.93x (?)

EqualStringSubstring
38
41
+7.9%
0.93x (?)

EqualSubstringSubstringGenericEquatable
38
41
+7.9%
0.93x (?)

LessSubstringSubstringGenericComparable
39
42
+7.7%
0.93x (?)

Improvement

ObjectiveCBridgeASCIIStringFromFile
171
66
-61.4%
2.59x

Performance: -Osize

TEST
OLD
NEW
DELTA
RATIO

Regression

LessSubstringSubstringGenericComparable
39
43
+10.3%
0.91x

EqualSubstringSubstring
38
41
+7.9%
0.93x (?)

EqualSubstringSubstringGenericEquatable
39
42
+7.7%
0.93x (?)

EqualSubstringString
39
42
+7.7%
0.93x (?)

Improvement

ObjectiveCBridgeASCIIStringFromFile
171
66
-61.4%
2.59x

Performance: -Onone

TEST
OLD
NEW
DELTA
RATIO

Regression

EqualSubstringSubstringGenericEquatable
44
49
+11.4%
0.90x (?)

Improvement

ObjectiveCBridgeASCIIStringFromFile
171
66
-61.4%
2.59x

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

2.6x win, that’s more like it!

This seems related:
[ RUN      ] StringUTF8Tests.Contiguous Access
stdout>>> abcd
stdout>>> abcdefghijklmnop
stdout>>> abcdéfghijk
stderr>>> Fatal error: invalid Collection: less than 'count' elements in collection: file /Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/swift/stdlib/public/core/ContiguousArrayBuffer.swift, line 643
stderr>>> Current stack trace:
stderr>>> 0    libswiftCore.dylib                 0x0000000109dfb020 _swift_stdlib_reportFatalErrorInFile + 116
stderr>>> 1    libswiftCore.dylib                 0x0000000109d14b80 specialized closure #1 in closure #1 in closure #1 in _fatalErrorMessage(_:_:file:line:flags:) + 304
stderr>>> 2    libswiftCore.dylib                 0x0000000109d14dc0 specialized closure #1 in closure #1 in _fatalErrorMessage(_:_:file:line:flags:) + 110
stderr>>> 3    libswiftCore.dylib                 0x0000000109cd2ff0 specialized closure #1 in _fatalErrorMessage(_:_:file:line:flags:) + 124
stderr>>> 4    libswiftCore.dylib                 0x0000000109cd3420 specialized _fatalErrorMessage(_:_:file:line:flags:) + 643
stderr>>> 5    libswiftCore.dylib                 0x0000000109cda0a0 specialized _copyCollectionToContiguousArray<A>(_:) + 900
stderr>>> 6    libswiftCore.dylib                 0x0000000109bbdf50 _StringGuts._foreignGrow(_:) + 56
stderr>>> 7    libswiftCore.dylib                 0x0000000109bbe170 _StringGuts.prepareForAppendInPlace(otherUTF8Count:) + 1323
stderr>>> 8    libswiftCore.dylib                 0x0000000109bbebf0 _StringGuts.append(_:) + 324
stderr>>> 9    libswiftCore.dylib                 0x0000000109cdb050 specialized _StringGuts.append(_:) + 230
stderr>>> 10   libswiftCore.dylib                 0x0000000109a5d8c0 static String.+= infix(_:_:) + 21
stderr>>> 11   String                             0x00000001090eb250 String.makeNative() + 49
stderr>>> 12   String                             0x00000001090eb3e0 closure #1 in  + 3736
stderr>>> 13   libswiftStdlibUnittest.dylib       0x00000001096fa890 specialized TestSuite._runTest(name:parameter:) + 584
stderr>>> 14   libswiftStdlibUnittest.dylib       0x00000001096b8ef0 _childProcess() + 846
stderr>>> 15   String                             0x00000001090ead30 main + 667
stderr>>> 16   libdyld.dylib                      0x00007fff62cc9ed8 start + 1
stderr>>> CRASHED: SIGILL
the test crashed unexpectedly
[     FAIL ] StringUTF8Tests.Contiguous Access
StringUTF8Tests: Some tests failed, aborting
UXPASS: []
FAIL: ["Contiguous Access"]
SKIP: []
To debug, run:
$ /Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/buildbot_incremental/swift-macosx-x86_64/validation-test-macosx-x86_64/stdlib/Output/StringUTF8.swift.tmp/String --stdlib-unittest-in-process --stdlib-unittest-filter "Contiguous Access"

Yeah, definitely something wrong around the edges of this. Will figure out what and land it on Monday :)

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - cf78d2499a2c65f6c08947b50057e48f6b4ec7eb

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - cf78d2499a2c65f6c08947b50057e48f6b4ec7eb

Build failed
Swift Test Linux Platform
Git Sha - cf78d2499a2c65f6c08947b50057e48f6b4ec7eb

Linux failure is a known unrelated hang

@swift-ci please smoke test linux platform

@swift-ci please test linux platform

oops. Guess those both worked >.<

What was the bug and why did this fix it? Also, can you test and make sure it gives the same result if the foreign string has unpaired surrogates?


Adding Storage Classes in CPP

Description
Adding storage classes page to the CPP course
Screenshots
No response

Hi @Jayanth-MKV, Please complete #220 and this in the same PR. Assigning you


Aligned wording for linked ressources. Fixes #112.

Please rebase so I can merge this in. Thank you!


Launching react app in Atom ?

Hi. I've started to use Atom recently.
With my react app, i see a debug icon to test my program on chrome, but when i launch it i get this.

I have no clue how to how to configure chrome and node inside of Atom to work.
 I'm used to go to the directory, launch "npm start" from cmd and it just works...
It's not a deal breaker, but it would be cool if it worked

Change the localhost to 3000 and try?


Value is undefined, expected an object

Hi,
during my development I have a strange issue after hot reloading (on Android - with hermes) on calling getArrayBufferForBlob:
Value is undefined, expected an object
I have to restart metro after any code change

To precise, it appears not on every reload, just when there is an issue in last edited code

I close it, I am no more able to reproduce it

@mlecoq I also reproduce it.

I'm seeing this problem too, so far only tested on iOS 16.4 Simulator. If code is hot reloaded, I get this error until I force quit the app and reopen, at which point all is good in the world until the next reload. Makes using this library while developing pretty painful.
Here's my code:
const blob = await fetch(url).then(r => r.blob());
const arrayBuffer = getArrayBufferForBlob(blob);
// error here

@mrousavy can this be reopened please?

@alexstanbury waiting for your repro !

Love the reproduction steps 😄  thank you so much for providing a reproduction 😊

Thanks for the repro! Can you throw a breakpoint there in Xcode and step through one by one and let me know in which line it fails?
https://github.com/mrousavy/react-native-blob-jsi-helper/blob/1d016b62e43ce44b4c5d0a810335567d9992e023/ios/BlobJsiHelper.mm#L36

Hi Marc, it fails on this line:
https://github.com/mrousavy/react-native-blob-jsi-helper/blob/1d016b62e43ce44b4c5d0a810335567d9992e023/ios/BlobJsiHelper.mm#L44

Ah hold on I got a fix

Done, released in v0.3.1!

Confirming fix works, thank you! 🍻


Imported accounts appear to create invalid blocks

Description of bug:
After importing a set of accounts from backup json file any rpc call with those accounts returns a block that never makes it anywhere.
Steps to reproduce the issue:
Wiped everything in /root/RaiBlocks except the backup dir.
synched,
then created a  new wallet
then --wallet_import --file --wallet.
The accounts show up when I --wallet_list
The accounts correctly show that they have their correct balance when I curl wallet_balances.
When I curl account_history it has all the blocks that the block explorer thinks should be there.
Describe the results you received:
When I try and do something that would create a new block it returns a block id.
However that block id never makes it out to the lattice. If I try and send from one account in my wallet to another, and then receive the block nano responds that it can't receive that block; it doesn't exist.
If I call block with the return value of a send call, immediately after sending, the node returns Block not found.
It looks very much like nano is creating invalid blocks for imported accounts. Meaning that all nano from my imported accounts is un-usable.
Describe the results you expected:
Blocks get stored and broadcast.
Additional information you deem important (e.g. issue happens only occasionally):
Environment:
Linux using latest docker.
logs
The logs don't contain any reference of the block that's being created incorrectly.
I do see this log message right after trying to send
[2018-02-16 19:05:06.370022]: Cached work invalid, regenerating

Can you use the RPC to get the contents of the apparently invalid block?
Also, are both nodes fully synced?

Can you use the RPC to get the contents of the apparently invalid block?
I ran the following python code:

block = self.client.send(wallet, source, dest, ammount)
print(block)
print(self.client.block(block))

Saw the correct rpc calls in the logs. However the block call came back with Block does not exist.

Any movement on this? This bug means that all xrb in my wallet is totally lost despite following the instructions on the wiki. Seems like being able to backup and import a wallet on linux would be important

Could you enable ledger processing logging then try to generate a block?

I've seen this type of corruption once in the past. If I recall correctly, they recovered the key by logging it in the backup import procedure. I'll see if that could help your problem.
Unfortunately I don't know why this issue exists in the first place.

This doesn't seem to be a race or anything like that. I've created, imported, and destroyed wallets lots of different times.
However putting debug logging into wallet_store::import does allow me to then use --wallet_add_adhoc. Not sure what that means for where the bug is.


added the WikiSQL data and code to read the data

For reading the data, this all looks good to me.


freeze() prevents gradients in non-frozen layers

I'm trying to fine-tune a pretrained model following the transfer learning tutorial. When I create a Sequential layer and train both it and the encoder, the whole model learns - great. But when I try freezing the encoder with self.encoder.freeze() before creating the Sequential the loss ceases to be differentiable and I get the error RuntimeError: element 0 of tensors does not require grad and does not have a grad_fn
The class:
class MLPReadout(pl.LightningModule):

    def __init__(self,
                 sizes: Tuple[int, ...],
                 use_bias: bool = True,
                 act=nn.LeakyReLU,
                 encoder: nn.Module = None,
                 train_only_readout: bool = True, ):

        super(MLPReadout, self).__init__()
        self.encoder = encoder
        self.train_only_readout = train_only_readout
        self.act_callable = act()
        if self.train_only_readout:
            # THIS IS THE PROBLEMATIC LINE
            self.encoder.freeze()

        mlp_layers = []
        for i in range(len(sizes) - 1):
            mlp_layers.append(nn.Linear(sizes[i], sizes[i + 1], bias=use_bias))
            if i < len(sizes) - 2:
                mlp_layers.append(act())
        self.readout = nn.Sequential(*mlp_layers)

    def forward(self,
                x: torch.Tensor,
                ) -> torch.Tensor:
        if self.encoder is not None:
            # Need to explicitly call forward because some models (e.g. SwAV) doesn't call its head
            x = self.encoder.forward(x)
            if isinstance(x, list) or isinstance(x, tuple):
                x = x[-1]
            x = self.act_callable(x)
        return self.readout(x)

CUDA:
- GPU:
- TITAN Xp
- TITAN Xp
- TITAN Xp
- TITAN Xp
- TITAN Xp
- TITAN Xp
- TITAN Xp
- TITAN Xp
- TITAN Xp
- TITAN Xp
- available:         True
- version:           10.2
Packages:
- numpy:             1.19.5
- pyTorch_debug:     False
- pyTorch_version:   1.10.0+cu102
- pytorch-lightning: 1.5.5
- tqdm:              4.62.3
System:
- OS:                Linux
- architecture:
- 64bit
- ELF
- processor:         x86_64
- python:            3.6.10
- version:           #203-Ubuntu SMP Wed Jan 15 02:55:01 UTC 2020

Edit: I found the cause. The problem is elsewhere.


💡[Feature]: Add Pet's Image classification

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Simple approach is to use infamous pet's images dataset provided by google to train a CNN model, that can be used to train & classify all 36 different pet's from their images.
Use Case
It can be used to distinguish the different pets of look like are of same breed or class. Also a visual file of the trained model.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

can this issue be assigned to me @sanjay-kv

its already there, please read pinned issuee


New version: Microsoft.OneDrive version 22.111.0522.0002

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.1 schema?

Microsoft Reviewers: Open in CodeFlow

@lechacon missed OneDrive PR (Last one =))


Code cleanup in composite ops

[x] Add operator() in some composite ops implementation and remove extra structs like done here https://github.com/tenstorrent/tt-metal/pull/10719

[x] #10883
[x] #10891

[x] #10823

All sub issues merged to main


Stride of [f32; 4] fields in struct

Pretty new to this so bear with me
wgsl
struct Light {
    position: vec4<f32>,
    color: vec4<f32>,
}

rust
#[repr(C)]
#[derive(Debug, Copy, Clone, PartialEq, encase::ShaderType)]
pub struct Light {
    pub position: [f32; 4],
    pub color: [f32; 4],
}

When I try to use Light in a uniform buffer, I get this failed assertion from Light::assert_uniform_compat():
panicked at 'array stride must be a multiple of 16 (current stride: 4)
[f32; 4] is 16 bytes, yeah? It looks to me that instead of treating each struct field as 16 byte aligned data, it looks into the arrays and treats it like a stride per f32 instead of striding each [f32; 4] whole.
Would it be possible to make Light (as written, with [f32; 4]s) pass assert_uniform_compat?
I looked in the docs  and found there is an impl<T> ShaderType for [T]. Maybe this precludes special treatment of [f32; 4]? Is the only solution to pick one of the matrix/vector libraries (like mint or nalgebra) and use that instead of raw [f32; 4]? If so, maybe we can add another example to ShaderType::assert_uniform_compat() to shed light on this scenario?

Since the wgsl spec supports arrays and vectors/matrices have a different layout than bare arrays there had to be a way to distinguish those at the type level.
Arrays used in the uniform address space are required to have a stride that is a multiple of 16, whereas elements of a vec4 do not.
You can either use vector/matrix types from crates supported by encase or create your own newtype around an array and implement the required traits or derive them.


Added support for 'application/x-www-form-urlencoded'

Currently this library supports only 'application/json' as content-type, This PR aims in adding support to the other content-type supported by Github for webhooks i.e. 'application/x-www-form-urlencoded'.
This support makes python-github-webhook fully compatible with the github webhooks.
Signed-Off-By: Shibani Mahapatra<EMAIL_ADDRESS>

@alexchamberlain Please review this PR, and let know if any changes are required.

@alexchamberlain
The reason for supporting this content-type is to provide support for users who are already using 'application/x-www-form-urlencoded' as the content-type instead of 'application/json', so that they can also seamlessly integrate with github webhooks with this library.
Since github supports two content-type, it will be good to provide support for those two types. Earlier this library was supporting only 'application/json'.
So finally this library will support both 'application/json' and 'application/x-www-form-urlencoded' as content-type.
Also, I have committed testcases for the 'application/x-www-form-urlencoded' content-type.
Please review it. Thanks.

Released as 1.0.3; @ShibaniMahapatra Thank You for your contribution; really appreciate it!

Thank you @alexchamberlain. Looking forward to many such contributions. 👍


Calltip traceback while using Jedi

From contrebasse on 2014-06-16T07:40:36Z
Spyder Version:  2.3.0rc (3722: r5420c4859aaf )
Python Version:  2.7.6
Qt Version    :  4.8.5, PyQt4 (API v2) 4.10.4 on Linux
IPython >=0.13  :  2.0.0 (OK)
pyflakes >=0.5.0:  0.5.0 (OK)
pep8 >=0.6      :  1.4.6 (OK)
pygments >=1.6  :  1.6 (OK)
sphinx >=0.6.6  :  1.2.2 (OK)
psutil >=0.3    :  2.1.1 (OK)
jedi >=0.8.0    :  0.8.0-final0 (OK)
matplotlib >=1.0:  1.3.1 (OK)
sympy >=0.7.0   :  0.7.5 (OK)
pylint >=0.25   :  1.2.1 (OK)
What steps will reproduce the problem?
No idea, I just noticed a traceback in the internal console.
What is the expected output? What do you see instead?
I saw nothing wrong in the editor, only the following traceback in the internal console:
Traceback (most recent call last):
File "/data/prog/spyderlib/spyderlib/widgets/editor.py", line 467, in show_object_info
at_position=position)
File "/data/prog/spyderlib/spyderlib/widgets/mixins.py", line 108, in show_calltip
self.calltip_widget.show_tip(point, tiptext, wrapped_textlines)
File "/data/prog/spyderlib/spyderlib/widgets/calltip.py", line 163, in show_tip
args = wrapped_tiplines[0].split('(')[1]
IndexError: list index out of range
Please provide any additional information below
.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1850

From contrebasse on 2014-06-25T02:02:55Z
I found how to reproduce it. In a new file, type:
class Foo(

From<EMAIL_ADDRESS>on 2014-06-27T18:46:05Z
This actually happens for any class or function definition now.  The value of "signature" ends up being the name of the file.  The easiest way to fix was to do this:
diff -r 322acad67d8c spyderlib/widgets/editor.py
--- a/spyderlib/widgets/editor.py	Mon Jun 23 15:36:47 2014 -0500
+++ b/spyderlib/widgets/editor.py	Fri Jun 27 20:43:52 2014 -0500
@@ -457,8 +457,11 @@
"send_to_inspector(QString,QString,QString,QString,bool)"),
obj_fullname, '', '', '', not auto)
if signature:

       try:
       self.editor.show_calltip('Arguments', signature, signature=True,
                                at_position=position)

       except IndexError:

           pass

def go_to_definition(self, position, regex=False):
"""Go to definition"""

From ccordoba12 on 2014-06-27T10:40:31Z
Great! It happens with both jedi and rope or just with jedi?
@-steven: Could you take a look at it, given that you are our code completion expert? :)
Summary: Calltip traceback   (was: calltip traceback)
Cc<EMAIL_ADDRESS>Labels: MS-v2.3.1

From<EMAIL_ADDRESS>on 2014-06-27T19:07:09Z
Whoops, this only occurs with jedi.  I assume @-contrebasse pulled jedi_plugin.py from my PR.  I updated the PR to fix this in jedi_plugin.py.  The above fix is no longer necessary.

From contrebasse on 2014-06-30T15:43:53Z
Yes, I pulled your jedi branch, sorry. I should have checked with the default branch first...

From ccordoba12 on 2014-07-02T08:05:07Z
Well, we're living in the future :) This is the first bug fixed for 2.3.1 without having released 2.3!
Summary: Calltip traceback while using Jedi   (was: Calltip traceback)
Status: Fixed

From contrebasse on 2014-07-02T07:11:55Z
This one can be closed, it is the wrong branch and is fixed in the PR.

From ccordoba12 on 2014-07-15T15:18:59Z
Labels: -MS-v2.3.1 MS-v2.4


add ENA to initialism list w/ preventions

Issue #, if available:
https://github.com/aws-controllers-k8s/ec2-controller/pull/17
Description of changes:

Add ENA to initialism list and prevent "Enable" -> "ENAble" and "Enabling" -> "ENAbling"

Grep to find other Ena words in aws models:
$ grep -r 'Ena[a-zA-Z]*' -o .  | sort | uniq | grep -v "Enabl"
./ec2/2016-11-15/api-2.json:EnaSupport
./ec2/2016-11-15/docs-2.json:EnaSupport
./ec2/2016-11-15/examples-1.json:EnaSupport

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hopefully no-one is enamoured enough with this prefix to enact a new policy to enable it in any other models.
But don't quote me on that.
/lgtm

I see what you did there.


Error: android.view.InflateException: Binary XML file line #28: Error inflating class de.hdodenhof.circleimageview.CircleImageView

Hi,
Thank you for your project ^^;
I found an crash.
I just add [compile 'com.google.android.gms:play-services-analytics:8.3.0'] in my gradle, and add code in my main activity.
however, if I delete that code my app is ok.
this is my build.gradle
apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services'

android {
    compileSdkVersion 23
    buildToolsVersion "23.0.1"

    defaultConfig {
        applicationId "com.xxx.xxx"
        minSdkVersion 15
        targetSdkVersion 23
        versionCode 152
        versionName "4.4.1"
        multiDexEnabled true
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
    packagingOptions {
        exclude 'META-INF/LICENSE'
        exclude 'META-INF/NOTICE'
        exclude 'META-INF/LICENSE.txt'
        exclude 'META-INF/NOTICE.txt'
    }
    /*productFlavors {
        dev {
            minSdkVersion 15
        }
        prod {
            minSdkVersion 15
        }
    }*/
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.android.support:appcompat-v7:23.1.0'           //Support Library
    compile 'com.android.support:cardview-v7:23.1.0'            //CardView Library
    compile 'com.android.support:gridlayout-v7:23.1.0'          //GridLayout Library
    compile 'com.android.support:recyclerview-v7:23.1.0'
    compile 'com.android.support:palette-v7:23.1.0'
    compile 'com.android.support:design:23.1.0'                 //Design Support Library

    compile 'com.github.rey5137:material:1.2.1'                 //Material Design Support/ https://github.com/rey5137/material

    compile 'com.squareup.retrofit:retrofit:1.9.0'              //Network Library
    compile 'com.squareup.okhttp:okhttp-urlconnection:2.4.0'
    compile 'com.github.bumptech.glide:glide:3.6.1'             //Network Image Library/    https://github.com/bumptech/glide
    compile 'com.github.bumptech.glide:okhttp-integration:1.3.1'
    compile 'com.squareup.okhttp:okhttp:2.5.0'                  //Network Client/           http://square.github.io/okhttp/

    compile 'de.hdodenhof:circleimageview:2.0.0'                //Circle Image             https://github.com/hdodenhof/CircleImageView

    compile 'com.facebook.android:facebook-android-sdk:4.1.0'   //facebook sdk

    compile 'com.google.android.gms:play-services-analytics:8.3.0'
}

and my Application.java
 private Tracker tracker;

    synchronized public Tracker getDefaultTracker() {
        if (tracker == null) {
            GoogleAnalytics analytics = GoogleAnalytics.getInstance(this);
            tracker = analytics.newTracker(R.xml.global_tracker);
        }

        return tracker;
    }

and my MainActivity.java
Application application = (Application) getApplication();
        Tracker tracker = application.getDefaultTracker();
        tracker.setScreenName(MainActivity.class.getName());
        tracker.send(new HitBuilders.ScreenViewBuilder().build());

and than Exception message
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.xxx.xxx/com.xxx.xxx.activity.MainActivity}: android.view.InflateException: Binary XML file line #28: Error inflating class de.hdodenhof.circleimageview.CircleImageView
    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2067)
    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2092)
    at android.app.ActivityThread.access$600(ActivityThread.java:138)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1203)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:137)
    at android.app.ActivityThread.main(ActivityThread.java:4874)
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:511)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
    at dalvik.system.NativeStart.main(Native Method)
Caused by: android.view.InflateException: Binary XML file line #28: Error inflating class de.hdodenhof.circleimageview.CircleImageView
    at android.view.LayoutInflater.createView(LayoutInflater.java:613)
    at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:687)
    at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
    at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
    at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
    at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
    at android.view.LayoutInflater.parseInclude(LayoutInflater.java:830)
    at android.view.LayoutInflater.rInflate(LayoutInflater.java:736)
    at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
    at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
    at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
    at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
    at android.support.v7.app.AppCompatDelegateImplV7.setContentView(AppCompatDelegateImplV7.java:256)
    at android.support.v7.app.AppCompatActivity.setContentView(AppCompatActivity.java:109)
    at com.xxx.xxx.activity.MainActivity.onCreate(MainActivity.java:96)
    at android.app.Activity.performCreate(Activity.java:5008)
    at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2031)
    ... 11 more
Caused by: java.lang.reflect.InvocationTargetException
    at java.lang.reflect.Constructor.constructNative(Native Method)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
    at android.view.LayoutInflater.createView(LayoutInflater.java:587)
    ... 28 more
Caused by: java.lang.NoClassDefFoundError: de.hdodenhof.circleimageview.R$styleable
    at de.hdodenhof.circleimageview.CircleImageView.<init>(CircleImageView.java:71)
    at de.hdodenhof.circleimageview.CircleImageView.<init>(CircleImageView.java:65)
    ... 31 more

thank you,

ah,lollipop is ok.
Test Android Verison

4.1.2: Fail
4.4.2: Fail
5.0.1: OK
5.1.1: OK

The error is probably caused by an incorrect implementation of multidex in your application. Read Android's documentation regarding multidex. There you'll find an explanation about the subject and a tutorial for implementing multidex support to android versions prior to 5.0.
http://developer.android.com/intl/pt-br/tools/building/multidex.html

I have the same issue and don't even have multidex enabled

Same here !, Any Fix ?

Here too, same problem

Hello, man  @Prographer   Any Fix ??

i think it's not google play-services-analytics but it's facebook sdk fault, i have some problem can anyone help for this ?? @Prographer any clue or sugestion about this???

I have some way to fix this problem. Why this problem is coming.

problem. This article explain we have method more than 65k.
how to fix.
how to fix if we use google analytic.
I hope this realy helpful. sorry for my bad english.

It's been almost half a year and it's still an issue

The original author's issue is most likely related to an incorrect implementation of multidex and should be solved by following http://developer.android.com/intl/pt-br/tools/building/multidex.html and http://developer.android.com/intl/pt-br/tools/support-library/features.html#multidex.
If you are having this issue without using multidex, please provide a full stack trace and more details about your setup.

I've sent you an email regarding all the information about the subject

I tried to upgrade google analytics library. (8.3.0 --> 8.4.0, It works fine.)
compile 'com.google.android.gms:play-services-analytics:8.4.0'
thank you

I'm not even using it but I think I found what was wrong in my project
On 01/05/16 04:42, Jiho Heo wrote:

I tried to upgrade google analytics library. (8.3.0 --> 8.4.0, It
works fine.)
|compile 'com.google.android.gms:play-services-analytics:8.4.0'|
thank you
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/hdodenhof/CircleImageView/issues/96#issuecomment-216011033

The issue is solved by following http://stackoverflow.com/questions/32110859/fatal-exception-java-lang-noclassdeffounderror-android-support-v7-appcompat-r this post answer.

i have enable MultiDex but still in below lollipop Error is showing.

In my case it was just wrong placing an icon image! when I pasted it to drawable, I didn't notice ".../drawable-v21" in the confirm dialog. AndroidStudio was just keep repeating "Error inflating class de.hdodenhof.circleimageview.CircleImageView". It takes about 2 hours for me to find it! Anyway...

Same for me.
My solution was to move my shapes (xml background) from drawable-v21 to drawable.

defaultConfig {
applicationId "xxxx"
minSdkVersion 16
targetSdkVersion 23
versionCode 17
versionName '1.9.0'
// Enabling multidex support.
multiDexEnabled true
}
app class:
public class MyApp extends MultiDexApplication
and add at the end of MyApp.java
@Override
protected void attachBaseContext(Context base)
{
    super.attachBaseContext(base);
    MultiDex.install(this);
}

gradle dependencies:
compile 'com.android.support:multidex:1.0.1'

For Android Studio 3.0.1
I have got the same issue and I have resolved finally Opening the gradle.properties and added following line:
android.enableAapt2=false

Thank you to give advice to me i love find it and send to you after
Vào 13 thg 2, 2018 2:50 CH, "Shahid Aslam"<EMAIL_ADDRESS>đã
viết:

For Android Studio 3.0.1
I have got the same issue and I have resolved finally Opening the
gradle.properties and added following line:
android.enableAapt2=false
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hdodenhof/CircleImageView/issues/96#issuecomment-365177921,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AirY_OqWTX2aUvFD0zZZl9vUEzVp16dfks5tUT7KgaJpZM4Gv139
.

I just remove android:scaleType="fitCenter" from imageview xml and its working fine now.

I just remove android:scaleType="fitCenter" from imageview xml and its working fine now.

I can't explain why, but when I removed android:scaleType="centerInside" the error was over ...

i fixed the issue ,project change to andoridx its Coming
change the multidex support to dependencies
implementation 'androidx.multidex:multidex:2.0.1'
defaultConfig {
multiDexEnabled = true
}
i hope its useful to all


os/exec: Command with arguments does not behave well if those are not trimmed

What version of Go are you using (go version)?
go1.6.2
What operating system and processor architecture are you using (go env)?
linux/amd64
What did you do?
I'm trying to run an external binary through the os/exec package and feed it with an argument (coming from another external binary, but it's a detail)
Here is the minimal example I could build after finally finding the problem :
 package main

 import (
     "fmt"
     "os/exec"
 )

 func main() {
 cmd := exec.Command("ls","-l ")
 _ , err := cmd.Output()
 if err != nil {
     fmt.Println(err)
 }
 fmt.Println("input:", cmd)
 }

What did you expect to see?
I would expect the Command to run as if it were typed in a shell, or to exit with an explicit error in case of a problem.
What did you see instead?
The Output() function exited with an "Exit status 1" error or an "Exit status 2" one depending on the binary it was given and even when panicking on its error, the trace is of no use.
And actually in my case it seems like it were some white-space which was causing the problem.
Here is my real case : I'm feeding to a Command an argument coming from the Output of another Command, this other program outputs its result through a Printf ("%s\n", result) and it causes the exact same problem to exec : it fails when I try to run using this output fetched from .Output() as an argument.
I tried to take a look at the code of the exec package but I wasn't able to spot why it is failing like this.
I think it would be a good idea to explicitly enforce in the Documentation that white-spaces in an argument are to be avoided and to implement more explicit errors maybe for this case ?

I would expect the Command to run as if it were typed in a shell

Sorry, that's not how this package works.
You also can't do redirection to files, piping into other programs, etc.
We never mention anywhere in the docs the word "shell", which at least to me suggests it doesn't act like a shell.
I'm inclined to do nothing here documentation-wise, but I'm open to disagreements. We're definitely not changing the behavior to trim.

Alright, I must confess I should not have been expecting it to behave like a shell, since it does not make so much sense indeed. But still, here is what I was expecting, I think :
When calling for example /bin/ls with "-l " as argument -- remark the space at the end --, instead of just an "exit status 2" error, I would expect it to output the error as /bin/ls does :
/bin/ls: invalid option -- ' '
But then I realized that .CombinedOutput() is doing exactly this, so I guess I should use CombinedOutput when doing debugging, it would have saved me hours. Hope someone will find this post helpful once.
In the end, effectively the only thing I missed documentation-wise, was an explicit mention of Output() ignoring the Stderr in case of errors. But I won't argue it is necessary in the documentation.
Sorry for bothering you and many thanks Brad!


HDDS-1935. Improve the visibility with Ozone Insight tool

Visibility is a key aspect for the operation of any Ozone cluster. We need better visibility to improve correctnes and performance. While the distributed tracing is a good tool for improving the visibility of performance we have no powerful tool which can be used to check the internal state of the Ozone cluster and debug certain correctness issues.
To improve the visibility of the internal components I propose to introduce a new command line application ozone insight.
The new tool will show the selected metrics / logs / configuration for any of the internal components (like replication-manager, pipeline, etc.).
For each insight points we can define the required logs and log levels, metrics and configuration and the tool can display only the component specific information during the debug.
h2. Usage
First we can check the available insight point:
{code}
bash-4.2$ ozone insight list
Available insight points:
scm.node-manager                     SCM Datanode management related information.
scm.replica-manager                  SCM closed container replication manager
scm.event-queue                      Information about the internal async event delivery
scm.protocol.block-location          SCM Block location protocol endpoint
scm.protocol.container-location      Planned insight point which is not yet implemented.
scm.protocol.datanode                Planned insight point which is not yet implemented.
scm.protocol.security                Planned insight point which is not yet implemented.
scm.http                             Planned insight point which is not yet implemented.
om.key-manager                       OM Key Manager
om.protocol.client                   Ozone Manager RPC endpoint
om.http                              Planned insight point which is not yet implemented.
datanode.pipeline[id]                More information about one ratis datanode ring.
datanode.rocksdb                     More information about one ratis datanode ring.
s3g.http                             Planned insight point which is not yet implemented.
{code}
Insight points can define configuration, metrics and/or logs. Configuration can be displayed based on the configuration objects:
{code}
ozone insight config scm.protocol.block-location
Configuration for scm.protocol.block-location (SCM Block location protocol endpoint)

ozone.scm.block.client.bind.host
default: <IP_ADDRESS>
current: <IP_ADDRESS>

The hostname or IP address used by the SCM block client  endpoint to bind

ozone.scm.block.client.port
default: 9863
current: 9863

The port number of the Ozone SCM block client service.

ozone.scm.block.client.address
default: ${ozone.scm.client.address}
current: scm

The address of the Ozone SCM block client service. If not defined value of ozone.scm.client.address is used
{code}
Metrics can be retrieved from the prometheus entrypoint:
{code}
ozone insight metrics scm.protocol.block-location
Metrics for scm.protocol.block-location (SCM Block location protocol endpoint)
RPC connections
Open connections: 0
Dropped connections: 0
Received bytes: 0
Sent bytes: 0
RPC queue
RPC average queue time: 0.0
RPC call queue length: 0
RPC performance
RPC processing time average: 0.0
Number of slow calls: 0
Message type counters
Number of AllocateScmBlock: 0
Number of DeleteScmKeyBlocks: 0
Number of GetScmInfo: 2
Number of SortDatanodes: 0
{code}
Log levels can be adjusted with the existing logLevel servlet and can be collected / streamd via a simple logstream servlet:
{code}
ozone insight log scm.node-manager
[SCM] 2019-08-08 12:42:37,392 [DEBUG|org.apache.hadoop.hdds.scm.node.SCMNodeManager|SCMNodeManager] Processing node report from [datanode=ozone_datanode_1.ozone_default]
[SCM] 2019-08-08 12:43:37,392 [DEBUG|org.apache.hadoop.hdds.scm.node.SCMNodeManager|SCMNodeManager] Processing node report from [datanode=ozone_datanode_1.ozone_default]
[SCM] 2019-08-08 12:44:37,392 [DEBUG|org.apache.hadoop.hdds.scm.node.SCMNodeManager|SCMNodeManager] Processing node report from [datanode=ozone_datanode_1.ozone_default]
[SCM] 2019-08-08 12:45:37,393 [DEBUG|org.apache.hadoop.hdds.scm.node.SCMNodeManager|SCMNodeManager] Processing node report from [datanode=ozone_datanode_1.ozone_default]
[SCM] 2019-08-08 12:46:37,392 [DEBUG|org.apache.hadoop.hdds.scm.node.SCMNodeManager|SCMNodeManager] Processing node report from [datanode=ozone_datanode_1.ozone_default]
{code}
The verbose mode can display the raw messages as well:
{code}
[SCM] 2019-08-08 13:16:37,398 [DEBUG|org.apache.hadoop.hdds.scm.node.SCMNodeManager|SCMNodeManager] Processing node report from [datanode=ozone_datanode_1.ozone_default]
[SCM] 2019-08-08 13:16:37,400 [TRACE|org.apache.hadoop.hdds.scm.node.SCMNodeManager|SCMNodeManager] HB is received from [datanode=ozone_datanode_1.ozone_default]:
storageReport {
storageUuid: "DS-bffe6bee-1166-4502-acf5-57fc16c5aa98"
storageLocation: "/data/hdds"
capacity:<PHONE_NUMBER>76
scmUsed: 16384
remaining:<PHONE_NUMBER>36
storageType: DISK
failed: false
}
{code}
h2. Use cases
Ozone insight can be used for any kind of debuging. Some problem examples from my yesterday

Due to a cache problem the volumes were created twice without any error at the second time. With this tool I can check the state of the internal cache, or check if the volume is added to the rocksdb itself.

After fixing this problem we found an DNS caching issue. The OM responded with an error but it was not clear where the error was propagated from (it was created in OzoneManagerProtocolClientSideTranslatorPB.handleError). With checking the traffic between SCM and OM it can be easy to track the origin of a specific error.

After fixing this problem we found some pipline problem (reported later at HDDS-1933). With this tool I could check the content of the reports and messages to the pipeline manager.

h2. Implementation
We can implement the tool without any significant code change as it uses existing features:

Metrics can be downloaded from the /prom endpoint
Log Level can be set with the existing /logLevel servlet endpoint (from hadoop-common)
Log lines can be streamed with a very simple new servlet
Configuration can be displayed based on configuration points

A new interface can be introduced for InsightPoints where all the affected logs/levels, metrics and config classes can be defined for each components.
Prometheus servlet endpoint can be changed to be turned on by default.
See: https://issues.apache.org/jira/browse/HDDS-1935

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
53
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

0
shelldocs
1
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

0
mvndep
32
Maven dependency ordering for branch

+1
mvninstall
647
trunk passed

+1
compile
398
trunk passed

+1
checkstyle
79
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
760
branch has no errors when building and testing our client artifacts.

+1
javadoc
167
trunk passed

0
spotbugs
415
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
610
trunk passed

_ Patch Compile Tests _

0
mvndep
37
Maven dependency ordering for patch

+1
mvninstall
536
the patch passed

+1
compile
369
the patch passed

+1
javac
369
the patch passed

+1
checkstyle
77
the patch passed

+1
mvnsite
0
the patch passed

+1
shellcheck
26
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
6
The patch has no ill-formed XML file.

+1
shadedclient
630
patch has no errors when building and testing our client artifacts.

+1
javadoc
154
the patch passed

-1
findbugs
419
hadoop-ozone in the patch failed.

_ Other Tests _

+1
unit
301
hadoop-hdds in the patch passed.

-1
unit
1977
hadoop-ozone in the patch failed.

+1
asflicense
47
The patch does not generate ASF License warnings.

7760

Reason
Tests

Failed junit tests
hadoop.ozone.om.TestKeyManagerImpl

hadoop.hdds.scm.pipeline.TestRatisPipelineProvider

hadoop.ozone.client.rpc.TestMultiBlockWritesWithDnFailures

hadoop.ozone.om.TestScmSafeMode

hadoop.ozone.client.rpc.TestSecureOzoneRpcClient

hadoop.ozone.client.rpc.TestOzoneRpcClient

hadoop.ozone.client.rpc.TestBlockOutputStreamWithFailures

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/1/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml shellcheck shelldocs

uname
Linux 127495e05306 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 63161cf

Default Java
1.8.0_212

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/1/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/1/testReport/

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

modules
C: hadoop-hdds/common hadoop-hdds/config hadoop-hdds/framework hadoop-hdds/server-scm hadoop-ozone hadoop-ozone/common hadoop-ozone/dist hadoop-ozone/insight hadoop-ozone/ozone-manager U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/1/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Let us sync up some time. If I get an overview of the code layout, it will be easier for me to review this. I really appreciate you doing this. Thank you ... I will sync with you when you are back

This is a very useful addition @elek. Is there any documentation or slides that I can look at to understand this more?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
43
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

0
shelldocs
0
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

0
mvndep
69
Maven dependency ordering for branch

+1
mvninstall
604
trunk passed

+1
compile
386
trunk passed

+1
checkstyle
75
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
783
branch has no errors when building and testing our client artifacts.

+1
javadoc
168
trunk passed

0
spotbugs
428
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
618
trunk passed

_ Patch Compile Tests _

0
mvndep
36
Maven dependency ordering for patch

+1
mvninstall
564
the patch passed

+1
compile
395
the patch passed

+1
javac
395
the patch passed

+1
checkstyle
72
the patch passed

+1
mvnsite
0
the patch passed

+1
shellcheck
26
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
7
The patch has no ill-formed XML file.

+1
shadedclient
620
patch has no errors when building and testing our client artifacts.

+1
javadoc
162
the patch passed

-1
findbugs
420
hadoop-ozone in the patch failed.

_ Other Tests _

+1
unit
310
hadoop-hdds in the patch passed.

-1
unit
2044
hadoop-ozone in the patch failed.

+1
asflicense
51
The patch does not generate ASF License warnings.

7892

Reason
Tests

Failed junit tests
hadoop.ozone.TestStorageContainerManager

hadoop.ozone.client.rpc.TestFailureHandlingByClient

hadoop.ozone.client.rpc.TestCommitWatcher

hadoop.ozone.client.rpc.Test2WayCommitInRatis

hadoop.ozone.container.server.TestSecureContainerServer

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/4/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml shellcheck shelldocs

uname
Linux 74081c66ba67 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 8aaf5e1

Default Java
1.8.0_212

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/4/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/4/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/4/testReport/

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

modules
C: hadoop-hdds/common hadoop-hdds/config hadoop-hdds/framework hadoop-hdds/server-scm hadoop-ozone hadoop-ozone/common hadoop-ozone/dist hadoop-ozone/insight hadoop-ozone/ozone-manager U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/4/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
42
Docker mode activated.

_ Prechecks _

+1
dupname
2
No case conflicting files found.

0
shelldocs
0
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

0
mvndep
74
Maven dependency ordering for branch

+1
mvninstall
657
trunk passed

+1
compile
388
trunk passed

+1
checkstyle
77
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
791
branch has no errors when building and testing our client artifacts.

+1
javadoc
188
trunk passed

0
spotbugs
464
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
704
trunk passed

-0
patch
513
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

0
mvndep
44
Maven dependency ordering for patch

+1
mvninstall
577
the patch passed

+1
compile
393
the patch passed

+1
javac
393
the patch passed

-0
checkstyle
43
hadoop-ozone: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1
mvnsite
0
the patch passed

+1
shellcheck
26
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
8
The patch has no ill-formed XML file.

+1
shadedclient
667
patch has no errors when building and testing our client artifacts.

+1
javadoc
174
the patch passed

-1
findbugs
429
hadoop-ozone in the patch failed.

_ Other Tests _

+1
unit
304
hadoop-hdds in the patch passed.

-1
unit
2388
hadoop-ozone in the patch failed.

+1
asflicense
49
The patch does not generate ASF License warnings.

8502

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestBlockOutputStreamWithFailures

hadoop.ozone.container.server.TestSecureContainerServer

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/5/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml shellcheck shelldocs

uname
Linux 89c76896c261 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 217e748

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/5/artifact/out/diff-checkstyle-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/5/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/5/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/5/testReport/

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

modules
C: hadoop-hdds/common hadoop-hdds/config hadoop-hdds/framework hadoop-hdds/server-scm hadoop-ozone hadoop-ozone/common hadoop-ozone/dist hadoop-ozone/insight hadoop-ozone/ozone-manager U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/5/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
42
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

0
shelldocs
1
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

0
mvndep
28
Maven dependency ordering for branch

+1
mvninstall
607
trunk passed

+1
compile
375
trunk passed

+1
checkstyle
82
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
800
branch has no errors when building and testing our client artifacts.

+1
javadoc
170
trunk passed

0
spotbugs
444
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
648
trunk passed

-0
patch
490
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

0
mvndep
36
Maven dependency ordering for patch

+1
mvninstall
545
the patch passed

+1
compile
389
the patch passed

+1
javac
389
the patch passed

-0
checkstyle
41
hadoop-ozone: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1
mvnsite
0
the patch passed

+1
shellcheck
26
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
6
The patch has no ill-formed XML file.

+1
shadedclient
676
patch has no errors when building and testing our client artifacts.

+1
javadoc
161
the patch passed

-1
findbugs
416
hadoop-ozone in the patch failed.

_ Other Tests _

+1
unit
291
hadoop-hdds in the patch passed.

-1
unit
1714
hadoop-ozone in the patch failed.

+1
asflicense
44
The patch does not generate ASF License warnings.

7559

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestBlockOutputStreamWithFailures

hadoop.hdds.scm.pipeline.TestRatisPipelineCreateAndDestory

hadoop.ozone.scm.pipeline.TestSCMPipelineMetrics

hadoop.ozone.container.server.TestSecureContainerServer

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/6/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml shellcheck shelldocs

uname
Linux 6741578cdaa4 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / ee7c261

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/6/artifact/out/diff-checkstyle-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/6/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/6/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/6/testReport/

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

modules
C: hadoop-hdds/common hadoop-hdds/config hadoop-hdds/framework hadoop-hdds/server-scm hadoop-ozone hadoop-ozone/common hadoop-ozone/dist hadoop-ozone/insight hadoop-ozone/ozone-manager U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/6/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
0
Docker mode activated.

-1
patch
13
https://github.com/apache/hadoop/pull/1255 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/7/console

versions
git=2.17.1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
42
Docker mode activated.

_ Prechecks _

+1
dupname
2
No case conflicting files found.

0
shelldocs
0
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

0
mvndep
80
Maven dependency ordering for branch

+1
mvninstall
697
trunk passed

+1
compile
406
trunk passed

+1
checkstyle
98
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
808
branch has no errors when building and testing our client artifacts.

+1
javadoc
189
trunk passed

0
spotbugs
449
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
674
trunk passed

-0
patch
521
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

0
mvndep
50
Maven dependency ordering for patch

+1
mvninstall
588
the patch passed

+1
compile
412
the patch passed

+1
javac
412
the patch passed

+1
checkstyle
94
the patch passed

+1
mvnsite
0
the patch passed

+1
shellcheck
32
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
8
The patch has no ill-formed XML file.

+1
shadedclient
682
patch has no errors when building and testing our client artifacts.

+1
javadoc
193
the patch passed

-1
findbugs
440
hadoop-ozone in the patch failed.

_ Other Tests _

+1
unit
299
hadoop-hdds in the patch passed.

-1
unit
2262
hadoop-ozone in the patch failed.

+1
asflicense
63
The patch does not generate ASF License warnings.

8627

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

hadoop.ozone.client.rpc.TestWatchForCommit

hadoop.ozone.container.common.statemachine.commandhandler.TestBlockDeletion

hadoop.ozone.client.rpc.TestCloseContainerHandlingByClient

hadoop.ozone.client.rpc.TestOzoneRpcClientForAclAuditLog

hadoop.ozone.client.rpc.TestOzoneClientRetriesOnException

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/8/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml shellcheck shelldocs

uname
Linux 252630c31851 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / b1eee8b

Default Java
1.8.0_222

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/8/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/8/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/8/testReport/

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

modules
C: hadoop-hdds/common hadoop-hdds/config hadoop-hdds/framework hadoop-hdds/server-scm hadoop-ozone hadoop-ozone/common hadoop-ozone/dist hadoop-ozone/insight hadoop-ozone/ozone-manager hadoop-ozone/tools U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/8/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

This is a very useful addition @elek. Is there any documentation or slides that I can look at to understand this more?

I think all the CLI parameters are well documented. But I will definitely create new doc pages if the patch is accepted.
@anuengineer @arp7: Do you have any more comments? Can you please review?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
0
Docker mode activated.

-1
patch
14
https://github.com/apache/hadoop/pull/1255 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help.

Subsystem
Report/Notes

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/9/console

versions
git=2.17.1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Can you please rebase this patch? The patch is not applying cleanly to the head of trunk.
ListSubCommand.java

Could be a camel case problem on osx. I think earlier the camele case usage was not consistent. Base on github there are no rebase problem. Can you please try to delete your local insight folder and retry?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
42
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

0
shelldocs
0
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

0
mvndep
68
Maven dependency ordering for branch

+1
mvninstall
592
trunk passed

+1
compile
380
trunk passed

+1
checkstyle
79
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
871
branch has no errors when building and testing our client artifacts.

+1
javadoc
180
trunk passed

0
spotbugs
449
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
668
trunk passed

-0
patch
499
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

0
mvndep
40
Maven dependency ordering for patch

+1
mvninstall
566
the patch passed

+1
compile
463
the patch passed

+1
javac
463
the patch passed

+1
checkstyle
103
the patch passed

+1
mvnsite
0
the patch passed

+1
shellcheck
38
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
12
The patch has no ill-formed XML file.

+1
shadedclient
892
patch has no errors when building and testing our client artifacts.

+1
javadoc
226
the patch passed

+1
findbugs
851
the patch passed

_ Other Tests _

+1
unit
358
hadoop-hdds in the patch passed.

-1
unit
1971
hadoop-ozone in the patch failed.

+1
asflicense
55
The patch does not generate ASF License warnings.

8718

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestContainerStateMachine

hadoop.hdds.scm.pipeline.TestSCMPipelineManager

hadoop.ozone.om.snapshot.TestOzoneManagerSnapshotProvider

hadoop.ozone.client.rpc.TestContainerStateMachineFailures

hadoop.ozone.om.TestOzoneManagerHA

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/10/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml shellcheck shelldocs

uname
Linux 5bbd24f32b4f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / c749f62

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/10/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/10/testReport/

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

modules
C: hadoop-hdds/common hadoop-hdds/config hadoop-hdds/framework hadoop-hdds/server-scm hadoop-ozone hadoop-ozone/common hadoop-ozone/dist hadoop-ozone/insight hadoop-ozone/ozone-manager U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1255/10/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.


Documentation: how do you decode into a record?

for example, the equivalent of aeson's eitherDeode.

ah good point. probably each module should grow its own README with some more explanation.
in the interim though, you do this via aeson-better-errors, so following the README example it'd be something like:
import Composite.Aeson (fromJsonWithFormat)
import Composite.Record (
import Data.Aeson.BetterErrors (ParseError, parseValue)
import Data.Aeson.QQ (aesonQQ)

eitherParseErrorOrAlice :: Either (ParseError e) (Record User)
eitherParseErrorOrAlice =
  parseValue (fromJsonWithFormat userFormat)
    [aesonQQ|{"id": 1, "name": "Alice"}|] -- val @"id" 1 :& val @"name" "Alice" :& RNil

thanks!
Yeah, I can add that to the docs, and any other examples. This package is
awesome.
On Nov 19, 2017 11:31 AM, "Ross MacLeod"<EMAIL_ADDRESS>wrote:

ah good point. probably each module should grow its own README with some
more explanation.
in the interim though, you do this via aeson-better-errors, so following
the README example it'd be something like:
import Composite.Aeson (fromJsonWithFormat)import Composite.Record (import Data.Aeson.BetterErrors (ParseError, parseValue)import Data.Aeson.QQ (aesonQQ)
eitherParseErrorOrAlice :: Either (ParseError e) (Record User)
eitherParseErrorOrAlice =
parseValue (fromJsonWithFormat userFormat)
[aesonQQ|{"id": 1, "name": "Alice"}|] -- val @"id" 1 :& val @"name" "Alice" :& RNil
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ConferHealth/composite/issues/13#issuecomment-345542794,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACNoMYpnvDEgxVJkrPQTB6fTFa7VfmPqks5s4IIBgaJpZM4QjfSc
.

double thanks! any help is of course appreciated! glad you're enjoying it so far, please do let us know if you have any improvements you think are good to have or other feedback

also, how do nested records work? for example,
type CardRecord = Record Card
type Card =
         [ "name"          ::: Text
         , "legalities"    ::: List (Record [ "format"   ::: Text
                                            , "legality" ::: Text
                                            ])
         ]

type LegalityRecord = Record Legality
type Legality =
  [ "format"   ::: Text
  , "legality" ::: Text
  ]

I understand the but it's the wrong kind, but why does DefaultJsonFormatRecord take the raw type level list, instead of the record or a proxy-record? my schema has several nested records, and I'd like to derive a formatting to initially explore the json.

nested record encoding is a bit annoying at present because we don't to force all records to have 'DefaultJsonFormat' typed field values, and instancing 'DefaultJsonFormat' for whatever your particular record type requires funny instance resolution extensions. We typically either use newtypes or explicitly format the subrecord.
newtypes:
data Legality = LegalityBanned | LegalityRestricted | LegalityLegal
  deriving (Bounded, Eq, Generic, Ord, Show)

legalityJsonFormat :: JsonFormat e Legality
legalityJsonFormat = enumJsonFormat "Legality"

instance DefaultJsonFormat Legality where defaultJsonFormat = legalityJsonFormat

type LegalityForFormat = '[ "format" :-> Text, "legality" :-> Legality ]
makeRecordJsonWrapper "LegalityForFormatJson" ''LegalityForFormat

type Card = '[ "name" :-> Text, "legalities" :-> [LegalityForFormatJson] ]
makeRecordJsonWrapper "CardJson" ''Card

pro: fairly easy to do, con: "infects" your data with json-ness, you need to navigate the wrappers
explicit formats:
data Legality = LegalityBanned | LegalityRestricted | LegalityLegal
  deriving (Bounded, Eq, Generic, Ord, Show)

legalityJsonFormat :: JsonFormat e Legality
legalityJsonFormat = enumJsonFormat "Legality"

instance DefaultJsonFormat Legality where defaultJsonFormat = legalityJsonFormat

type LegalityForFormat = '[ "format" :-> Text, "legality" :-> Legality ]
type Card = '[ "name" :-> Text, "legalities" :-> [Record LegalityForFormat] ]

cardJsonFormatRecord :: JsonFormatRecord e Card
cardJsonFormatRecord
  =  field @"name" defaultJsonFormat
  :& field @"legalities" (arrayJsonFormat (recordJsonFormat defaultJsonFormatRecord))
  :& RNil
makeRecordJsonWrapperExplicit "CardJson" ''Card [| cardJsonFormatRecord |]

pro: totally separates JSON-ness from data model, can more easily have more than a single canonical encoding for a particular data model, con: more typing/boilerplate

@Dridus How funny are the instance resolution extensions? Could you show a quick example similar to the ones above?

@torgeirsh it's been a while so my mental cache of the concerns here isn't fresh, but I'll think about it and try to get back to you. my vague recollection is that you'd need IncoherentInstances to define the instances it's looking for, since you're defining them for types you didn't define here


"Cancel" action like nano's ctrl-c

Description of the problem or steps to reproduce
I rebound the keys to match Nano's defaults (ie., ctrl-o to save). But when saving, the only way to cancel a save is escape, something I avoid because my escape key is occasionally wonky. It'd be ideal if there was a bindable action to cancel an operation. Unless I've missed it?
Specifications
Commit hash: cfcb2e45
OS: Linux 5.9 (Manjaro BSPWM 20.1)
Terminal: Terminator 2.0.1

If you are referring to the action escape is bound to in the command bar, that would be the AbortCommand action. To rebind in settings.json:
{
    "command": {
        "Ctrl-c": "AbortCommand"
    }
}

See > help keybindings for details (specifically the section "Pane type bindings").

oh God, it's been One of Those Days. Thanks!


Using the nested structure in the summarizer

How can I change the Reporter to use the nested structure without changing code in node_modules/nyc/index.js file?
Is there an argument to be passed with the nyc cli (e.g. --nested) or can I change options in .nycrc file or change package.json?
Thanks in advance

@JaKXz thanks for the quick replay.
451. tree = libReport.summarizers.pkg(map) -> tree = libReport.summarizers.nested(map) is there a way to change it from the nyc console like adding a --nested or something without the need to change the code

@AmeCode I'm not quite sure I understand what you mean... are you using the text reporter?

I'm planning some related changes to the istanbul-lib-report / istanbul-reports API's for nyc@15.  The primary goal of this will be to allow the report to request a specific summarizer rather than having nyc give it one.  I will keep this request in mind as I'm working on that feature.

@coreyfarrell thanks

There is any update on this?


Feature Request: Kanban board view

Is your feature request related to a problem? Please describe.
I want to display my tasks list in a Kanban board View
Describe the solution you'd like
Support a Kanban view board like https://www.atlassian.com/agile/kanban/boards
Describe alternatives you've considered
Using SyncFusion Blazor and wanting to migrate to Razden to open source parts of the project

Isn't that similar to the RadzenDropZone?
https://blazor.radzen.com/dropzone

Yep, the DropZone can be used to create Kanban board .


Macbook Air Window too big

Using a Macbook Air, and the window is too large to resize, exit minimize and prettymuch use at all in resizable mode. looks like it's defaulting to fit a 1920x1080 screen, not the 1440x900 on the macbook air
Thanks

Disable custom window chrome


¿How to add middleware to a resource route?

Thats it How can I add the midleware Role or Permission to a Route::resource()

Wrap it in a group: Laravel Documentation


GUI - X , Y, Z, position indicators not properly updated.

After running a protocol , the X and Y indicators of the stage contol submenu nor the Z position indicator of the Focus indicator show the correct, current position. They are not updated after the protocol is complete. In the figure, if you set X&y manually and then run a protocol. Returning to the stage control submenu shows the previously entered coordinates, not the current position at the end of the protocol

.

Tested, fixed.

For the Z axis, if you load a previously saved protocol and go to the first step , the X & Y coordinates in the white boxes are correct, however in the Focus tab, the Z-coordinate is zero. For creating protocols I feel the need to know where I am at all times. A floating or bottom menu bar with xy&z would be helpful.

appears to have been fixed


Suppress Allstar reports on trusted binaries

Add Allstar config override in order to suppress spurious bug reports about binary files stored in our repository. Those binary files are fetched as-is from trusted upstream repositories.
This fixes #786.

LGTM - possible nit: not sure if these files end with a \n (I think they generally should) - in the review it looks like they don't, but IIRC Github might just omit any ending newline characters and instead complain if they are absent)

The files do have a trailing newline in my local checkout, so I presume it's just GitHub UI that doesn't display them.


The default encoding for gradle6.7 is not utf8

Expected Behavior

I didn't add any configuration. Expect it to default on utf8
Current Behavior

groovy:
//tasks.withType(JavaCompile) { options.encoding = "UTF-8" }
test {
    System.getProperties().findAll{k,v -> k.contains("encoding")}.forEach{k,v -> println(k+" "+v)}
    println(System.getProperties().getProperty("file.encoding",""))
    println(getDefaultCharacterEncoding())
//    setDefaultCharacterEncoding("utf-8")
    useJUnitPlatform()
}

output:
> Configure project :jdk8
file.encoding GBK
sun.jnu.encoding GBK
sun.io.unicode.encoding UnicodeLittle
GBK
GBK

Context

Steps to Reproduce

run a java application with idea+gradle
and it compile error

Your Environment

Build scan URL:
https://gradle.com/s/lrx2bu5xfyg3s

Agreed. This isn't quite easy without breaking too many people but certainly something we're interested in. For now, I'll mark this as a duplicate of #16763


RuntimeError: No pretrained fasttext intent_model provided

train.py script with default configuration file config.json raises the next error:
Traceback (most recent call last):
  File "train.py", line 49, in <module>
    model = KerasMulticlassModel(opt)
  File "/home/ilivans/projects/intent_classifier/intent_model/multiclass.py", line 73, in __init__
    embedding_url='http://lnsigo.mipt.ru/export/intent/reddit_fasttext_model.tar.gz')
  File "/home/ilivans/projects/intent_classifier/intent_model/embedding_inferable.py", line 38, in __init__
    self.load(embedding_fname, embedding_url)
  File "/home/ilivans/projects/intent_classifier/intent_model/embedding_inferable.py", line 83, in load
    raise RuntimeError('No pretrained fasttext intent_model provided')
RuntimeError: No pretrained fasttext intent_model provided

I thought it should download the fasttext model and it actually goes through this line but fails here requiring embedding file name. It looks like the problem can be solved just by passing embedding_fname argument to the EmbeddingInferableModel constructor.

Thank you!
This is already fixed.
I also provided embedding file for pre-trained model on SNIPS dataset.


rockdove-20240921_232416

rockdove

this event should be sent twice and red for one of them

this event should be sent twice and red for one of them

amazing, it works

one final success test

testing an empty payload override

testing payload with no sender

testing payload with no sender

testing payload with no sender - this time with the secret set


Ability to deny specific modules

I'd like to be able to ban std::sync::Mutex in my codebase, preferring parking_lot::Mutex.
Describe the solution you'd like
I'd like to be able to ban specific modules or identifiers.
Wanted to surface this use case as a possibility for cargo-deny. It does involve parsing the code like a linter.

We do exactly this in our codebase! We use Clippy and the disallowed_methods disallowed_types lint for this together with clippy.toml configuration. This is how that part of our clippy.toml looks like:
# for `disallowed_method`: https://rust-lang.github.io/rust-clippy/master/index.html#disallowed_method
disallowed-methods = [
    # std functions
    { path = "std::env::temp_dir", reason = "we use the tempdir crate instead through ark_file_system::TempDir" },
    { path = "std::env::home_dir", reason = "deprecated in std, and we use app_dirs2 crate" },
    { path = "std::env::set_current_dir", reason = "don't change the current working directory, it usually leads to shared sadness" },
    { path = "std::env::var_os",  reason = "use std::env::var and UTF-8 strings instead, including for paths" },
    { path = "std::env::env_os",  reason = "use std::env::var and UTF-8 strings instead, including for paths" },
    { path = "std::env::args_os", reason = "use std::env::var and UTF-8 strings instead, including for paths" },

    { path = "futures::executor::block_on", reason = "Use ark_future::block_on instead, our single function for blocking highlights the functions in profilers and require naming the blocking operations" },

    { path = "sha1::Digest::new", reason = "SHA-1 is cryptographically broken, and we are building new code so should not use it" },
]

# for `disallowed_type`: https://rust-lang.github.io/rust-clippy/master/index.html#disallowed_type
disallowed-types = [
    { path = "std::sync::Mutex",    reason = "Use the faster & simpler non-poisonable primitives in `parking_lot` instead" },
    { path = "std::sync::RwLock",   reason = "Use the faster & simpler non-poisonable primitives in `parking_lot` instead" },
    { path = "std::sync::Condvar",  reason = "Use the faster & simpler non-poisonable primitives in `parking_lot` instead" },

    { path = "ring::digest::SHA1_FOR_LEGACY_USE_ONLY", reason = "SHA-1 is cryptographically broken, and we are building new code so should not use it" },
]

So try that out!
And think we can close this request to cargo-deny

Yes, like @repi said this is already covered by clippy, thanks!

awesome. Thanks for sharing your configuration


Extract secrets out to environment vars

#13
Out from config/default.js and into environment variables.

suggested implementation in #13


WinHTTP transport adapter can't run the injector server tests

Tried to run the tests with winHTTP but there are two issues with it:

It does not support allowing insecure certs, so we can't test HTTPS until we update winHTTP to support this.
For HTTP, winHTTP throws an exception even before the injector server prompt the response options.  This needs to be debugged further.

@ahsonkhan  FYI
Originally posted by @vhvb1989 in https://github.com/Azure/azure-sdk-for-cpp/issues/2265#issuecomment-840917735

callstack
 	KernelBase.dll!00007ffb34a54b89()	Unknown
 	vcruntime140d.dll!00007ffb0f22b460()	Unknown
>	azure-core-test-fault-injector.exe!GetErrorAndThrow(const std::string & exceptionMessage) Line 200	C++
 	azure-core-test-fault-injector.exe!Azure::Core::Http::WinHttpTransport::SendRequest(std::unique_ptr<Azure::Core::Http::_detail::HandleManager,std::default_delete<Azure::Core::Http::_detail::HandleManager>> & handleManager) Line 373	C++
 	azure-core-test-fault-injector.exe!Azure::Core::Http::WinHttpTransport::Send(Azure::Core::Http::Request & request, const Azure::Core::Context & context) Line 577	C++
 	azure-core-test-fault-injector.exe!FaultInjectionClient::Send(Azure::Core::Http::Request & request, const Azure::Core::Context & context) Line 66	C++
 	azure-core-test-fault-injector.exe!main() Line 95	C++


Support for other micros.

I would be willing to help with support for Atmel controllers like the ATTiny and ATMega. If these can be emulated you could in theory use this for arduino development without an arduino.

Sounds good. For now the zmu cli tool and the building has been done with single target only, but adding another architecture would help to remove the possible assumptions from the tool.
My base idea for the tool is that you compile it for your specific target by defining needed feature flags. This is done for maximizing the simulation performance as it removes the need for do dynamic checks at runtime.
What would be the best minimal first target you could work on?

Considering the current fork rust-avr that adds support for atmel micros to the rust compiler i feel this would be pretty simple. I'd probably start with an attiny85 and work my way up to some sort of atmega. Although as you say with args users can just define what controller they want and you can just have a lookup table of micro specs that can be fed into the emulator. I have to review your code to see if what I'm proposing is even possible for me to do. I'll let you know.

To be clear, the support for avr should be separated to its own lib,
parallel to zmu_cortexm. This way the main cli can be built with either
library.
la 9. maalisk. 2019 klo 8.56 Chad Baxter<EMAIL_ADDRESS>kirjoitti:

Considering the current fork rust-avr that adds support for atmel micros
to the rust compiler i feel this would be pretty simple. I'd probably start
with an attiny85 and work my way up to some sort of atmega. Although as you
say with args users can just define what controller they want and you can
just have a lookup table of micro specs that can be fed into the emulator.
I have to review your code to see if what I'm proposing is even possible
for me to do. I'll let you know.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jjkt/zmu/issues/5#issuecomment-471152496, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADThhbKXMm64mbNKhDxKbJdMxagaGHQ1ks5vU1sRgaJpZM4bmJXV
.

Ok currently pretty busy I'll get around to looking into it this coming week.


is this code blocking?? lol

use something like libev or libuv or libevent to do actual non-blocking io...

too busy