Update classgraph to 4.8.50

Updates io.github.classgraph:classgraph from 4.8.47 to 4.8.50.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.github.classgraph", artifactId = "classgraph" } ]

labels: semver-patch

See #77


The colours of the bandwidth graph and gauges for in/out are switched

The orange is incoming on the gauge but out on the timeline graph. The look great otherwise :smile:

derp derp derp. Thank you for vigilance @lanzafame

caveat, i am not sure whether the entire graph is entirely wrong or if just the legend is, so I will leave that to you to figure out :slightly_smiling_face:


Improved readability for Spanish speaking users

Just little grammatical changes to improve the reader's experience.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thanks for the contribution! An older PR already fixed a bunch of things in the description, so if you still find something wrong with the latest version, please submit a change against that.


Ruby version is out of date

the ruby version is out of date by a few years. can it be updated to 3.0?

Also with Racket...
Current version of Racket is 8.9 (8.10 near the end of this month) but the TIO version is 6.x from 2016... Math functions have even changed as well... Here are the docs for log in Racket v6.5 (web archive link) and here are the current docs for log.
In the previous versions of Racket, we couldn't supply a second argument to log to tell it what the base it. So to port back (log 15 3), we need to use (/ (log 15) (log 3)) for TIO.
Python on TIO is at version 3.7.4 according to platform.python_version(). Node.js is at version 11.6.0 (current is 20.4.0, LTS is 18.16.1).  Go on TIO is at version go1.11.13 released in 2019, current is at go1.20.6.


test coverage upload dashapi

It tests the Dashboard.CreateUploadURL.
It internally calls "create_upload_url" method of the dashboard "/api" interface.
This dashboard API requires GlobalConfig.UploadBucket option to specify the bucket.
Dashboard generates the $bucket/$uuid.upload URL and returns it to the client.

I updated this PR description.

https://github.com/google/syzkaller/issues/5635 to test more challenging APIs.


Support adding multiple weights using build_model

Discussion from the BMZ meeting, proposed by @ivan-ea
Would be nice to support adding multiple weights in the build_model function.
cc @constantinpape @FynnBe

For context:
I was not sure if it was possible to generate models with multiple weight files with the build_model function.
Also I wondered if I missed something, since the website has the option to choose between several weight formats to download.
Some models have 2 weights in the rdf (for example impartial-shrimp), so I was curious how they might have built them.

Thanks @constantinpape  the add_weights function seems exactly what I was missing.
I was following the model creation notebook, since I need to get the
deepimagej_config too. Maybe I could add the add_weights to the example notebook
once I figure out how to use it.

Maybe I could add the add_weights to the example notebook
once I figure out how to use it.

That would be great!


Share diagram

Let's say I'm creating a diagram and I would like to share the link direct to the diagram something like this http://localhost:3001/documentation?diagramId=123
The interface should load the data and mark that diagram select on the open diagram

Fixed like this:
http://localhost:3001/diagram?id=061da907-772c-4e42-95ed-b736abfd541a


#219: wrong executable extension linux

Fixes: #219
NOTE: work in progress
Approach:
different executable extension priority lists depending from the os.
Changes:
Splits the list EXTENSION_PRIORITY in EXTENSION_PRIORITY_WIN and EXTENSION_PRIORITY_WIN to have different priorities for the choice of the executable extension depending from the OS.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
29 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 56.248%

Files with Coverage Reduction
New Missed Lines
%

com/devonfw/tools/ide/common/SystemPath.java
29
52.63%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
3752

Relevant Lines:
6416

💛  - Coveralls

I fixed this in https://github.com/devonfw/IDEasy/pull/238/commits/78151534ae74dedb3637f380ffc834a56ded499d in PR #238
Usually I very much prefer that we have small stories and PRs fixing exactly that story but my time is very limited and the pressure is high to get this test-infrastructure available that blocks the entire team, so I assume, my merge will come first and thereby replace some other PRs.

IMHO this PR can now be closed. @mvomiero thanks for creating the issue and this PR. I could fix this very fast based on your work 👍


Update openj9 branches to v0.30.0-release in aqa-tests v0.8.0-release branch

Signed-off-by: lanxia<EMAIL_ADDRESS>

https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/3014
[2022-01-17T22:46:05.501Z] get functional test material...
[2022-01-17T22:46:05.501Z] git clone --depth 1 -b v0.30.0-release https://github.com/eclipse-openj9/openj9.git

FYI @pshipton

This is good for OpenJ9. I assume the other repos are going to separately get tagged for the release as well?

Any preference of what we should tag https://github.com/eclipse-openj9/openj9-systemtest with? v0.8.0 or v0.30.0-release? If not, I am thinking to tag it with v0.8.0, so it aligns with the rest test material.


Placeholder changes to input value in readonly input.

Fixes #34017

Thanks! Could you check there're no other occurrencies of such readonly inputs missing a value, either in the docs or the examples, please? If not, we'll take care of it 🙂

@ffoodd - yes, I think changes to the CSS are needed too. If you change the placeholder to a value then the displayed 'Readonly input here...' text is not the lighter grey as the Disabled inputs above.
Screenshot here by changing the HTML elements in Dev Tools (Edge 90 for Windows):

@coliff AFAIC that's acceptable since:

readonly is meant to be read, so better contrast are fine,
readonly and disabled aren't the same, so this helps reduce the confusion IMHO.
However that's more of a UX decision. Maybe some accessibility insights too, @patrickhlauke?

@rajesh2kumar96 Were you able to check if there were other readonly inputs missing a value, both in our docs and in examples? If you can't, I'll try to.

going purely by WCAG, nominally disabled fields / controls are exempted from 4.5:1 (regular) / 3:1 (large) contrast requirements. readonly fields aren't. even for disabled fields, a ratio of at least 3:1 or better is still best practice, the closer it can get to 4.5:1, the better. beyond that, it's down to aesthetic choices.

@coliff AFAIC that's acceptable since:

readonly is meant to be read, so better contrast are fine,
readonly and disabled aren't the same, so this helps reduce the confusion IMHO.
However that's more of a UX decision. Maybe some accessibility insights too, @patrickhlauke?

@rajesh2kumar96 Were you able to check if there were other readonly inputs missing a value, both in our docs and in examples? If you can't, I'll try to.

I will do this.

@ffoodd I changed readonly inputs with value. Please check.


The sequence of function then is wrong

The returned data has not been converted to html.
joFetch('https://www.google.com.tw/', {}, { returnType: 'html' })
    .then(data => console.log(data))

It has been fixed in v1.0.5.


Why some functions return Future<void>, while others Future<dynamic> or Future

Hello,
I noticed that some functions like ui.loadFontFromList return Future<void>, while
io.IOSink.flush, io.Socket.close, ..., return Future<dynamic>
Is there any specific reason for this, like performance, of pass-by-value or something,
Thanking you...

@gintominto5329
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and ask questions like this.
You may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it. Thank you!


405 Method Not Allowed doesn't include Allow headers

The definition for the 405 response code indicates that it must include a list of valid methods for the requested resource. When I make a request using a method that's not the allowedMethods list in the configuration, I get a response with these headers:
Cache-Control →must-revalidate,no-cache,no-store
Content-Length →275
Content-Type →text/html;charset=iso-8859-1
Date →Wed, 28 Dec 2016 00:57:24 GMT
Conversely, making a request using a method that isn't in allowedMethods and isn't supported by my API returns these headers:
Content-Length →52
Content-Type →application/json
Date →Wed, 28 Dec 2016 00:54:28 GMT
This is with version 1.0.2 of Dropwizard.
Using 0.8.2 of Dropwizard, making a request using an forbidden method responds with the expected headers:
Allow →GET,OPTIONS
Cache-Control →must-revalidate,no-cache,no-store
Content-Length →327
Content-Type →text/html; charset=ISO-8859-1
Date →Fri, 23 Dec 2016 16:54:43 GMT
Can we add back functionality to include the Allow header as required by w3?

It looks like this functionality were removed by Jersey during a regular update and we picked it up without our knowledge. I will need to look up the reasons behind it in the Jersey changelogs. Maybe some folks had security concerns about exposing too much information for the bad guys poking around in the web with shell scripts.

@arteam, I think this is actually a bug on our end as if I set registerDefaultExceptionMappers: false in the config, curl reports the following headers:
< HTTP/1.1 405 Method Not Allowed
< Date: Sat, 28 Jan 2017 05:40:23 GMT
< Allow: POST,OPTIONS
< Cache-Control: must-revalidate,no-cache,no-store
< Content-Type: text/html;charset=iso-8859-1
< Content-Length: 250

I have a fix for this, I'll submit a PR later today for review.


Roadmap for the project

As I get a little more involved with the project, I'm wondering if another 0.16.x release is planned, or if we should focus on 0.17.x, which will bring some changes anyway.
I would prefer a final release under 0.16.x (maybe addressing #144 and #146 and all previous changes), maybe fixing #134 and #141 might be a useful addition.
But I would probably want to concentrate on wlroots 0.17.x
Do you have any roadmap for this project?

Thanks for the question! There isn't a particularly firm roadmap for the project other than to serve the needs of whatever libraries are using it and ideally stay as up-to-date as possible. The main user I know of is qtile, but there could be more that I don't know about, so any changes on 0.16 should at least not break that. If there are some good changes to make on 0.16 then I'd be happy to cut a release with those based on all of the PR's that you have put up. Whenever 0.17 is able to compile, we can cut over the main branch to that (there is some work in that direction in the 'wlroots-nextbranch that @m-col started, but it still needs some work AFAIK), but even then, there is the0.16.x` branch that we can cut releases off.

Sounds good! I'll work on merging your other open PRs in the meantime, just
let me know when would be convenient to cut a release!
On Sat, Mar 16, 2024, 07:45 Lars @.***> wrote:

Thank you for your message. Another 0.16.x release would be great.
I will probably submit another pull request for the OutputState API (issue
#149 https://github.com/flacjacket/pywlroots/issues/149), but it should
be compatible with all previous 0.16.x releases.
I have a project that is based on pywlroos and it would be nice if I could
specify a fixed pywlroots version, since I also rely on some boolean return
values etc., which is currently only implemented in the main branch.
I'll look into the OutputState API and come back to you.
—
Reply to this email directly, view it on GitHub
https://github.com/flacjacket/pywlroots/issues/148#issuecomment-2001960644,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFGJBIARB7D5P5B7OFFH3DYYQWEZAVCNFSM6AAAAABETALCDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBRHE3DANRUGQ
.
You are receiving this because you commented.Message ID:
@.***>

Sure! Sorry for letting those pile up. Is there anything else that would be good to get in for a 0.16 release?


Cleanup HADOOP1 support

As some people are confused about why we encountered some build error while running alluxio tests.
I will suggest them to remove the HADOOP1 related code to pass the build.

Thanks for the work!

+1 to removing hadoop 1.

alluxio-bot, merge this please

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to dora please

alluxio-bot, cherry-pick this to main please


Unexpected CSS token

What is described in https://github.com/FortAwesome/Font-Awesome/issues/5043 is occurring in Safari Version 9.0 (106<IP_ADDRESS>) on OS X Yosemite 10.10.5 (14F27)

@notmessenger so this issue is a bit weird, I fix in when I do a bower install and have the bower components folder in my local directory but there is no way to actually hot fix the source code of font-awesome. we can do 2 things, wait until it gets bundled into a new version of font awesome and update the dependency or fork font-awesome and reference our forked fixed version. If I'm missing something let me know, thanks

Or, we can possibly bower install font-awesome --save-dev, and modify ember-cli-build.js to do less compile.  We could then add a less file inside the dummy app that overrides the mixin at fault.
I was attempting to do this, but hit a brick wall.  Can't figure out the ember-cli-build.js file vs the index.js

Does this ever occur in an consuming app or is it only ever in the dummy app of this repo?  If it never occurs in the consuming app I'm not worried about it and will close this issue.

dummy app only

Moving to the v1.0.0 milestone which is for the redevelopment of the demo application. Can likely be closed at that point.


Sympy above 1.0 may not work properly (see #6392)

Thanks for your contribution. This needs to go against our 3.x branch, not master, because master is for Spyder 4, which is still a year away.
So please open a new PR against 3.x.


[Addition]: Spoof 20 hotspots in Thailand (San Sali, Chiang Rai)[cluster no.1]

Hotspot b58 Addresses
112Sj5vHbAp8BjScXDzxB4Jis8Q2kuPno56hyUw1zf2N37UnzkfG
11QSu2WbDHncid8YNnjnJk84ME2qVojRMUCr5UZbR92mY4a2a8j
11k6UwEC8TtNEJcXob4ywNEgS6MsGhrheoo5kzmiDwfxnvhNiJm
11NyyDaKzGFtjr36NK24BVWGmNMtuu1ZhgPKQSYdwG8D5V8XQJ9
11Da4A5y7ZCW45tzLUj5ut9nZM2QdChPDr8VDcs5tqikWWpxV3x
11qjLbjVR3ncSQWBKiSN7sVjdPzLAUc7c7ayr5ifx9AANu5UWbH
11FDUTsdhRy7rrUowshCRw9dDNnEp8LpveCfTbVsrFTtur864Sy
1127FmVEeNfnaBzroSALjJPBxcBeBh9h6B7Nrozd5cTZwDrnYmRV
11QSu2WbDHncid8YNnjnJk84ME2qVojRMUCr5UZbR92mY4a2a8j
11LhpCbQDw6cDLUzU858qWh9vueX5V66A6gKKSGCTWYbrTCbYJw
112Ap4etuprhKsHfv6DC8yFbk1JjTqBhzdomPC3qqtECnCbAhMjH
112Hnyc8SHMWLTLBbDsyPYmNNzYwYwNwwkSii5RLxj3hJLbuzNZd
117V7692FV52w3mZDF4jCLrL1NBigxwY2u4cDWnJfC4XwdzpHfn
11vsRYHUX9s924tLCWn35XASqxKbJ7M3nDdGXyJNjkey9esPeqs
112BRnHn5VeB96trRWCvcmPm4S5u8CretsTZe6qvakA5zus56F2j
11238AqecMiFBRvmKivE7BfohcLHS3VnZZeVr5gm5DjX4KoKRAgV
11fLPC58tFyFutNhkMn3EUb2gvpMZbfyhfF7JZKktdnGg2GcY94
11GLXA8VyRGEgSBKbvH6dgxVqZDrtFpD5MaHUCTdPPY4EdZXD32
112r8xJa4S95DKGdVYzxmdctrM92JVPhAEcDk6RPw3wYoPdeAPqG
112oAKwEqhfXdH5MVzxC6XSU7idQYLWNPVc4iZhYuW2ELPNes8PT
112wiwa86y6BJPwoAPGynCRAX1jbSBCn3Sfrh39nr7T1drJZzERk
Discord Handle
od808#4617
Reason(s)

All listener hotspot IP are located in Hong Kong and Singapore, all list in table 13:17 Friday, May 6, 2565 BE (UTC)
They are all just witnessing each other

This whole chain of clusters is clearly suspicious, but can you provide harder evidence they are spoofed?
E.g. can you find any that give unusual RSSI / SNR data via crowdspot?
https://crowdspot.herokuapp.com/hotspots/11LhpCbQDw6cDLUzU858qWh9vueX5V66A6gKKSGCTWYbrTCbYJw
(which doesn't seem to display data for some of them right now)
Other details e.g. all same brand, all in a cluster asserted in rapid timeframe, etc? (which aren't proof in themselves).
I assume this whole chain will have a similar issue.

This whole chain of clusters is clearly suspicious, but can you provide harder evidence they are spoofed? E.g. can you find any that give unusual RSSI / SNR data via crowdspot? https://crowdspot.herokuapp.com/hotspots/11LhpCbQDw6cDLUzU858qWh9vueX5V66A6gKKSGCTWYbrTCbYJw (which doesn't seem to display data for some of them right now)
Other details e.g. all same brand, all in a cluster asserted in rapid timeframe, etc? (which aren't proof in themselves). I assume this whole chain will have a similar issue.

I don't have RSSI/SNR chart for those suspicious and don't trust RSSI/SNR value. The one of harder evidence  is the location of IP address because it's can't be fake. There is no good reason for hide IP address with other country IP address.
please check the suspicious by heliumtracker.io https://www.heliumtracker.io/hotspots/767299

I agree they are extremely suspicious and that the IP details add to that, but I'm not sure that it will be enough for a denylist reviewer (I don't know).
If gamers could be proven by comparing asserted location vs IP address lookup location then it would presumably be simple to query this and deny many hotspots en-mass? I'm not aware of this happening, so I'd assume it's not considered sufficient evidence?
Realistic RSSI/SNR can be faked for sure, but worth checking to see if it's not being faked realistically?
The variation in earnings by cluster is potentially a clue, as it's not clear why if they were legit deployments there would be this stark difference between clusters. The difference in itself isn't proof, but the cause of the difference might be something one could uncover and give as evidence? You can see the older cluster below does much better and much more witnessing is going on than the newer one

Another angle is following the wallets. The newer cluster has HS recently transferred from this wallet
https://explorer.helium.com/accounts/13tKLzW9cUB2t8pWgTmvDhRWnDk9ML6bciMPSMHaRnk3hoDBxFG/activity
which you can see does a lot of transferring and asserting - again this isn't proof of anything beyond someone managing loads of HS, but I expect someone knows a way of digging into this?

I agree they are extremely suspicious and that the IP details add to that, but I'm not sure that it will be enough for a denylist reviewer (I don't know).
If gamers could be proven by comparing asserted location vs IP address lookup location then it would presumably be simple to query this and deny many hotspots en-mass? I'm not aware of this happening, so I'd assume it's not considered sufficient evidence?
Realistic RSSI/SNR can be faked for sure, but worth checking to see if it's not being faked realistically?
The variation in earnings by cluster is potentially a clue, as it's not clear why if they were legit deployments there would be this stark difference between clusters. The difference in itself isn't proof, but the cause of the difference might be something one could uncover and give as evidence? You can see the older cluster below does much better and much more witnessing is going on than the newer one

Another angle is following the wallets. The newer cluster has HS recently transferred from this wallet https://explorer.helium.com/accounts/13tKLzW9cUB2t8pWgTmvDhRWnDk9ML6bciMPSMHaRnk3hoDBxFG/activity which you can see does a lot of transferring and asserting - again this isn't proof of anything beyond someone managing loads of HS, but I expect someone knows a way of digging into this?

I agreed with you that the IP address is not 100% for evident. However, the IP location is the first and easy step to filter out the spoof hotspot. if the IP location is wrong so there are 99% possibility to be fake hotspot. I think, the spoof hotspot owner can't acquire Thailand IP address because it's expensive and hard to find for foreign gamer.
All hotspot IP address in that wallet are located in Hong Kong/Singapore that should be enough reason to confirm those hotspot is not locate in Thailand.  Please add it in deny list.

These are first five RSSI/Distance

These are RSSI/SNR of the first five

I've compiled a list of Heltec and Midas HS in Thailand that asserted at a similar times around 2-3 weeks ago.  #4567


[Enhancement] Support overflow mode for decimal type

Main work
Support error reporting when decimal overflow by introducing a OverflowMode, which has three different modes:

IGNORE
OUTPUT_NULL
REPORT_ERROR

What type of PR is this:

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[x] 2.5
[ ] 2.4

[BE Incremental Coverage Report]
:disappointed: fail : 66 / 109 (60.55%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/decimal_binary_function.h
0
14
00.00%
[64, 78, 80, 83, 85, 87, 88, 92, 94, 98, 102, 187, 218, 223]

:large_blue_circle:
src/exprs/arithmetic_expr.cpp
8
25
32.00%
[71, 77, 83, 89, 114, 115, 138, 139, 141, 142, 143, 145, 146, 160, 180, 204, 205]

:large_blue_circle:
src/exprs/cast_expr.cpp
8
19
42.11%
[1086, 1088, 1109, 1110, 1111, 1112, 1113, 1114, 1119, 1121, 1289]

:large_blue_circle:
src/exprs/math_functions.h
1
2
50.00%
[377]

:large_blue_circle:
src/exprs/function_context.cpp
4
4
100.00%
[]

:large_blue_circle:
src/exprs/decimal_cast_expr.h
44
44
100.00%
[]

:large_blue_circle:
src/runtime/runtime_state.h
1
1
100.00%
[]

[BE Incremental Coverage Report]
:disappointed: fail : 66 / 109 (60.55%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/decimal_binary_function.h
0
14
00.00%
[64, 78, 80, 83, 85, 87, 88, 92, 94, 98, 102, 187, 218, 223]

:large_blue_circle:
src/exprs/arithmetic_expr.cpp
8
25
32.00%
[71, 77, 83, 89, 114, 115, 138, 139, 141, 142, 143, 145, 146, 160, 180, 204, 205]

:large_blue_circle:
src/exprs/cast_expr.cpp
8
19
42.11%
[1086, 1088, 1109, 1110, 1111, 1112, 1113, 1114, 1119, 1121, 1289]

:large_blue_circle:
src/exprs/math_functions.h
1
2
50.00%
[377]

:large_blue_circle:
src/exprs/function_context.cpp
4
4
100.00%
[]

:large_blue_circle:
src/exprs/decimal_cast_expr.h
44
44
100.00%
[]

:large_blue_circle:
src/runtime/runtime_state.h
1
1
100.00%
[]

[FE Incremental Coverage Report]
:disappointed: fail : 2 / 3 (66.67%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
2
3
66.67%
[2527]

[BE Incremental Coverage Report]
:disappointed: fail : 66 / 109 (60.55%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/decimal_binary_function.h
0
14
00.00%
[64, 78, 80, 83, 85, 87, 88, 92, 94, 98, 102, 187, 218, 223]

:large_blue_circle:
src/exprs/arithmetic_expr.cpp
8
25
32.00%
[71, 77, 83, 89, 114, 115, 138, 139, 141, 142, 143, 145, 146, 160, 180, 204, 205]

:large_blue_circle:
src/exprs/cast_expr.cpp
8
19
42.11%
[1086, 1088, 1109, 1110, 1111, 1112, 1113, 1114, 1119, 1121, 1289]

:large_blue_circle:
src/exprs/math_functions.h
1
2
50.00%
[377]

:large_blue_circle:
src/exprs/function_context.cpp
4
4
100.00%
[]

:large_blue_circle:
src/exprs/decimal_cast_expr.h
44
44
100.00%
[]

:large_blue_circle:
src/runtime/runtime_state.h
1
1
100.00%
[]

[FE Incremental Coverage Report]
:disappointed: fail : 2 / 3 (66.67%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
2
3
66.67%
[2527]

[BE Incremental Coverage Report]
:disappointed: fail : 66 / 109 (60.55%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/decimal_binary_function.h
0
14
00.00%
[64, 78, 80, 83, 85, 87, 88, 92, 94, 98, 102, 187, 218, 223]

:large_blue_circle:
src/exprs/arithmetic_expr.cpp
8
25
32.00%
[71, 77, 83, 89, 114, 115, 138, 139, 141, 142, 143, 145, 146, 160, 180, 204, 205]

:large_blue_circle:
src/exprs/cast_expr.cpp
8
19
42.11%
[1086, 1088, 1109, 1110, 1111, 1112, 1113, 1114, 1119, 1121, 1289]

:large_blue_circle:
src/exprs/math_functions.h
1
2
50.00%
[377]

:large_blue_circle:
src/exprs/function_context.cpp
4
4
100.00%
[]

:large_blue_circle:
src/exprs/decimal_cast_expr.h
44
44
100.00%
[]

:large_blue_circle:
src/runtime/runtime_state.h
1
1
100.00%
[]

[FE Incremental Coverage Report]
:disappointed: fail : 2 / 3 (66.67%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
2
3
66.67%
[2520]

[BE Incremental Coverage Report]
:disappointed: fail : 66 / 109 (60.55%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/decimal_binary_function.h
0
14
00.00%
[64, 78, 80, 83, 85, 87, 88, 92, 94, 98, 102, 187, 218, 223]

:large_blue_circle:
src/exprs/arithmetic_expr.cpp
8
25
32.00%
[71, 77, 83, 89, 114, 115, 138, 139, 141, 142, 143, 145, 146, 160, 180, 204, 205]

:large_blue_circle:
src/exprs/cast_expr.cpp
8
19
42.11%
[1086, 1088, 1109, 1110, 1111, 1112, 1113, 1114, 1119, 1121, 1289]

:large_blue_circle:
src/exprs/math_functions.h
1
2
50.00%
[377]

:large_blue_circle:
src/exprs/function_context.cpp
4
4
100.00%
[]

:large_blue_circle:
src/exprs/decimal_cast_expr.h
44
44
100.00%
[]

:large_blue_circle:
src/runtime/runtime_state.h
1
1
100.00%
[]

[BE Incremental Coverage Report]
:disappointed: fail : 54 / 104 (51.92%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/expr_context.cpp
0
2
00.00%
[189, 190]

:large_blue_circle:
src/exprs/decimal_binary_function.h
0
15
00.00%
[61, 78, 79, 80, 82, 83, 86, 87, 88, 90, 91, 92, 97, 100, 101]

:large_blue_circle:
src/exprs/function_context.cpp
0
2
00.00%
[159, 160]

:large_blue_circle:
src/runtime/runtime_state.h
0
2
00.00%
[342, 343]

:large_blue_circle:
src/exprs/arithmetic_expr.cpp
0
12
00.00%
[109, 111, 114, 157, 158, 160, 174, 176, 179, 199, 201, 204]

:large_blue_circle:
src/exprs/math_functions.h
0
3
00.00%
[376, 378, 381]

:large_blue_circle:
src/exprs/cast_expr.cpp
8
16
50.00%
[1086, 1087, 1088, 1091, 1102, 1110, 1118, 1285]

:large_blue_circle:
src/exprs/decimal_cast_expr.h
46
52
88.46%
[75, 94, 112, 212, 319, 366]

[FE Incremental Coverage Report]
:disappointed: fail : 2 / 3 (66.67%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
2
3
66.67%
[2520]

[FE Incremental Coverage Report]
:disappointed: fail : 2 / 3 (66.67%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
2
3
66.67%
[2520]

[FE Incremental Coverage Report]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
3
3
100.00%
[]

[BE Incremental Coverage Report]
:disappointed: fail : 54 / 104 (51.92%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/expr_context.cpp
0
2
00.00%
[189, 190]

:large_blue_circle:
src/exprs/decimal_binary_function.h
0
15
00.00%
[61, 78, 79, 80, 82, 83, 86, 87, 88, 90, 91, 92, 97, 100, 101]

:large_blue_circle:
src/exprs/function_context.cpp
0
2
00.00%
[159, 160]

:large_blue_circle:
src/runtime/runtime_state.h
0
2
00.00%
[342, 343]

:large_blue_circle:
src/exprs/arithmetic_expr.cpp
0
12
00.00%
[109, 111, 114, 157, 158, 160, 174, 176, 179, 199, 201, 204]

:large_blue_circle:
src/exprs/math_functions.h
0
3
00.00%
[376, 378, 381]

:large_blue_circle:
src/exprs/cast_expr.cpp
8
16
50.00%
[1086, 1087, 1088, 1091, 1102, 1110, 1118, 1285]

:large_blue_circle:
src/exprs/decimal_cast_expr.h
46
52
88.46%
[75, 94, 112, 212, 319, 366]

[FE Incremental Coverage Report]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/qe/SqlModeHelper.java
1
1
100.00%
[]

[BE Incremental Coverage Report]
:disappointed: fail : 54 / 104 (51.92%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/expr_context.cpp
0
2
00.00%
[189, 190]

:large_blue_circle:
src/exprs/decimal_binary_function.h
0
15
00.00%
[61, 78, 79, 80, 82, 83, 86, 87, 88, 90, 91, 92, 97, 100, 101]

:large_blue_circle:
src/exprs/function_context.cpp
0
2
00.00%
[159, 160]

:large_blue_circle:
src/runtime/runtime_state.h
0
2
00.00%
[342, 343]

:large_blue_circle:
src/exprs/arithmetic_expr.cpp
0
12
00.00%
[109, 111, 114, 157, 158, 160, 174, 176, 179, 199, 201, 204]

:large_blue_circle:
src/exprs/math_functions.h
0
3
00.00%
[376, 378, 381]

:large_blue_circle:
src/exprs/cast_expr.cpp
8
16
50.00%
[1086, 1087, 1088, 1091, 1102, 1110, 1118, 1285]

:large_blue_circle:
src/exprs/decimal_cast_expr.h
46
52
88.46%
[75, 94, 112, 212, 319, 366]

[BE Incremental Coverage Report]
:disappointed: fail : 54 / 112 (48.21%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/expr_context.cpp
0
2
00.00%
[189, 190]

:large_blue_circle:
src/exprs/decimal_binary_function.h
0
17
00.00%
[62, 68, 71, 84, 85, 86, 88, 89, 92, 93, 94, 96, 97, 98, 103, 107, 108]

:large_blue_circle:
src/exprs/function_context.cpp
0
2
00.00%
[159, 160]

:large_blue_circle:
src/runtime/runtime_state.h
0
2
00.00%
[342, 343]

:large_blue_circle:
src/exprs/arithmetic_expr.cpp
0
12
00.00%
[109, 111, 114, 157, 158, 160, 174, 176, 179, 199, 201, 204]

:large_blue_circle:
src/exprs/math_functions.h
0
3
00.00%
[376, 378, 381]

:large_blue_circle:
src/exprs/arithmetic_operation.h
0
6
00.00%
[81, 83, 85, 91, 93, 97]

:large_blue_circle:
src/exprs/cast_expr.cpp
8
16
50.00%
[1086, 1087, 1088, 1091, 1102, 1110, 1118, 1285]

:large_blue_circle:
src/exprs/decimal_cast_expr.h
46
52
88.46%
[75, 94, 112, 212, 319, 366]

[FE Incremental Coverage Report]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/qe/SqlModeHelper.java
1
1
100.00%
[]

[BE Incremental Coverage Report]
:disappointed: fail : 54 / 112 (48.21%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/expr_context.cpp
0
2
00.00%
[189, 190]

:large_blue_circle:
src/exprs/decimal_binary_function.h
0
17
00.00%
[62, 68, 71, 84, 85, 86, 88, 89, 92, 93, 94, 96, 97, 98, 103, 107, 108]

:large_blue_circle:
src/exprs/function_context.cpp
0
2
00.00%
[159, 160]

:large_blue_circle:
src/runtime/runtime_state.h
0
2
00.00%
[342, 343]

:large_blue_circle:
src/exprs/arithmetic_expr.cpp
0
12
00.00%
[109, 111, 114, 157, 158, 160, 174, 176, 179, 199, 201, 204]

:large_blue_circle:
src/exprs/math_functions.h
0
3
00.00%
[376, 378, 381]

:large_blue_circle:
src/exprs/arithmetic_operation.h
0
6
00.00%
[81, 83, 85, 91, 93, 97]

:large_blue_circle:
src/exprs/cast_expr.cpp
8
16
50.00%
[1086, 1087, 1088, 1091, 1102, 1110, 1118, 1285]

:large_blue_circle:
src/exprs/decimal_cast_expr.h
46
52
88.46%
[75, 94, 112, 212, 319, 366]

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


DEA error

Hello Mr.Zhang,
For some reason, I am getting an error in the DEA steps.
Error in tximport(files, type = "salmon", txOut = TRUE, countsFromAbundance = "no") :
all(file.exists(files)) is not TRUE
Calls: DEA -> tximport -> stopifnot
Execution halted
[Mon Sep 12 11:16:57 2022]
Error in rule DEA:
jobid: 1
output: output/WT/trans/dea/DEA/transcript-level/dea_wt_ko.tsv, output/WT/trans/dea/DEA/transcript-level/deg_wt_ko.tsv, output/WT/trans/dea/DEA/gene-level/dea_wt_ko.tsv, output/WT/trans/dea/DEA/gene-level/deg_wt_ko.tsv
RuleException:
CalledProcessError in line 40 of /mnt/d/RNAseq/qhd2/workflow/dea_trans.rules:
Command ' set -euo pipefail;  Rscript scripts/dea_trans.R ' returned non-zero exit status 1.
File "/mnt/d/RNAseq/qhd2/workflow/dea_trans.rules", line 40, in __rule_DEA
File "/home/wbc/miniconda3/envs/ranseqSnakemake/lib/python3.6/concurrent/futures/thread.py", line 56, in run
Shutting down, this might take some time.
Exiting because a job execution failed. Look above for error message
Complete log: /mnt/d/RNAseq/qhd2/.snakemake/log/2022-09-12T110512.827029.snakemake.log
DEA is done!
Visualization is not required and RASflow is done!
Building DAG of jobs...
Nothing to be done.
Complete log: /mnt/d/RNAseq/qhd2/.snakemake/log/2022-09-12T110510.915007.snakemake.log
Any help is appreciated. Thank you.

As I can understand from the error message,
Error in tximport(files, type = "salmon", txOut = TRUE, countsFromAbundance = "no") :
all(file.exists(files)) is not TRUE

it seems that the quantity files (output from salmon) are not there, please check whether you have output/WT/trans/quant/[sample]/quant.sf

thank you sir！

No problem. I will then close it. Feel free to reopen it if the same error remains there. And also feel free to open new issues if some new error occurs.


Changing the value of your parameter is a code smell

Challenge Factorialize a Number has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
I don't believe we should encourage beginners to change the value of a parameter of a method. In the proposed code, the function factorialize returns "num". It would be better form to create a var "result" to return it at the end - teaching good coding practices.
My code:

function factorialize(num) {
  var result = 1;
  for(var i=1;i<=num;i++) {
    result *= i;
  }
  return result;
}

factorialize(5);

@JonathanScher agreed. We can change the seed code to:
function factorialize(num) {
  var result;

  return result;
}

factorialize(5);

@erictleung I can take this. But is challengeSeed the only thing that needs to be modified? Or should solutions be modified as well?

@Manish-Giri just the challengeSeed. The solution doesn't modify the input parameters.

@erictleung cool! Will do.

Would we not need to change this for every single instance? Like in Title Case a Sentence, Return Largest Numbers in Arrays, Confirm the Ending and so on...

@Bouncey mmm good point.
@FreeCodeCamp/issue-moderators what do you guys think about changing challenges so that it doesn't modify the input parameters?

I don't believe we should encourage beginners to change the value of a parameter of a method.

It is also perfectly acceptable to change that value.
The goal of the challenge is for the camper to develop an algorithm, how they do that is up to the user. At this point we are not trying to teach campers best practice. This comes up every once in a while and I understand why some would think that, but best practices is often more about opinion then clear cut fact.
We should concentrate on the substance of a challenge. Does this challenge teach something valuable? Yes. Does changing the value of num harm anything? No.

I disagree that modifying input param is a bad practice, unless some one can point me to a concrete reference.
For instance, someone can rightly argue that each variable you declare is adding a new reference to the same object on the stack.
var actualVariable = 10;
var myVariable = actualVariable;
var yourVariable = myVariable;

All the above point to the location where 10 is stored, just with different references (variable names);
This is rather, waste of resources (not in this challenge), but when you do any memory intensive computing (visual renders, etc.)
IMHO modifying input param should be completely acceptable. JavaScript lets us do that and leveraging it should be the best practice not the other way round.

While I agree with @BerkeleyTrue's point that the aim of the challenge is to help the camper to develop an algorithm and not necessarily talk about best practices in general, I don't think it's a good idea to modify method parameters. Here's an interesting article that I found on this context.

When I approved the change, I was thinking in a functional way, whereby you don't/can't modify input parameters 😄
However, thinking functionally is outside the scope of this challenge and the challenges that @Bouncey has listed. So I change my mind on having these challenges to not modify the input parameters and agree with @raisedadead and @BerkeleyTrue's stance on the matter.

Cool. This was really fun though, I might be biased from belonging to a C++ and native programming world (memory and execution speed is the most valuable resource for me), but on that note since all of us feel that we should NOT modify the input parameters, lets keep it that way! I can live with that :wink:
@Manish-Giri thanks for the share, its a good read!

@Manish-Giri Thanks for the article. It was an interesting read. It reminds me of an article I read when I first starting coding.
The arguments object is a tricky beast if you don't know what you are doing. But the author came to the wrong conclusion, best practice is to always typecast the arguments object to an array.
function() { var args = Array.prototype.slice.call(arguments); };

or with new and improved JavaScript es2015
function(...args) { };

This is common and indeed best practice when ever working with the arguments object. You can see that in the first couple of comments on that post.


KeyError on custom action not present in PERMISSIONS_ACTION_MAP

Environment

Nautobot version (Docker tag too if applicable): 2.0.0rc3
Python version: 3.11
Database platform, version:
Middleware(s):

Steps to Reproduce

Create UI viewset with additional action
Attempt to use additional action

Expected Behavior
View works

Observed Behavior
KeyError exception for action not being in PERMISSIONS_ACTION_MAP

Just for the sake of clarity we're talking about custom view actions derived from viewset methods. Thanks for this submission.

Yes

Solving via #4529


add multipart-mode request option

HttpMultipartMode supports several multipart modes (see org.apache.http.entity.mime),
yet clj-http uses only STRICT mode.
This pulls request allows to optionally select HttpMultipartMode (e.g. HttpMultipartMode/RFC6532 is required for Mailgun)

@dakrone please consider adding this, as this is a long standing issue which prevents using correct internationalization support

Merged this, thanks @juskrey!


Use upstream Cobra package

We had been using a fork of Cobra to allow us to redefine the shorthand
flag for hep (using "?" instead of "h"). The upstream package changed
the way it auto-added the help flags that allows us to go back to using
the upstream package now.
Switching to the upstream packages fixes #743.  The problem there was always that the help output implied that the boolean flag could be used as either true or false. In reality, we default to false, and only take action when set to true. Explicitly setting to false is not intended to affect a behavior.
Before this change:
rexray help volume ls
....
Flags:
      --attached[=false]: A flag that indicates only volumes attached to this host should be returned
      --available[=false]: A flag that indicates only available volumes should be returned
      --path[=false]: A flag that indicates only volumes attached to this host should be returned, along with their path info
...

After:
rexray help volume ls
...
Flags:
      --attached    A flag that indicates only volumes attached to this host should be returned
      --available   A flag that indicates only available volumes should be returned
      --path        A flag that indicates only volumes attached to this host should be returned, along with their path info
...

Codecov Report

Merging #786 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #786      +/-   ##
=========================================
+ Coverage    7.41%   7.41%   +<.01%
=========================================
  Files          21      21
  Lines        2590    2589       -1
=========================================
  Hits          192     192
+ Misses       2381    2380       -1
  Partials       17      17

Impacted Files
Coverage Δ

cli/cli/usage.go
0% <ø> (ø)
:arrow_up:

cli/cli/cmds_00_other.go
2.17% <0%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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

@akutz
I did some more testing with this, using GCE, and didn't run into any CLI problems. I tested create,remove, attach/detach, mount/unmount, ls, and used flags like --path, --format jsonp, etc. All printed output as normal.
You and I discussed that the best thing to do here would be to remove the "help for "+c.c.Name() part of the help flag initialization, which would just leave the help description blank rather than always printing "Help for rexray". Before I do that, I have one other suggestion for you to consider.
If you look at the help descript for the help command itself, here's what it prints:
REX-Ray:
  A guest-based storage introspection tool that enables local
  visibility and management from cloud and storage platforms.

Usage:
  rexray [flags]
  rexray [command]

Available Commands:
  adapter     The adapter manager
  device      The device manager
  env         Print the REX-Ray environment
  flexrex     The FlexVol REX-Ray plug-in manager
  help        Help about any command

It is always Help about any command. Would you rather see that instead? So to be clear, which is better:
(1)
Global Flags:
  -c, --config string     The path to a custom REX-Ray configuration file
  -?, --help
  -h, --host string       The libStorage host.

or (2)
Global Flags:
  -c, --config string     The path to a custom REX-Ray configuration file
  -?, --help              Help about any command
  -h, --host string       The libStorage host.

(2) is consisent with the help command description, but it is repetitive.

Hey @akutz. I have this rebased in my local branch. Just wanting to hear from you whether you like the empty help string better, or the string "Help about any command". See my previous comment.

I saw. Why don't you change to Help about the current command for the flag? Also, please be careful on the rebase due to the dependency conflicts introduced once I merged RR 0.8.2.

@akutz I like that idea, re: help text, and have made that change.
As for the dependencies, I hope I've done the right thing. Were you just worried that I would downgrade libStorage? That got caught by the rebase.  But I did do glide up and check in a new glide.lock to pick up anything new from cobra/pflag. If there is another way I need to approach it, I'll need your guidance.

Hi @codenrhoden,
Yeah, I was wanting to make sure you just rm glide.lock and performed a glide up after you updated / merged glide.yaml. The glide.lock files cannot merge cleanly since they have a calculated hash at the top based on the contents of the corresponding glide.yaml file.

@akutz this is ready for your re-review, and has been rebased so that it can be merged.


Create a windows installer

We could create a simple windows installer for pixi. That way people that are less comfortable with Cargo or the command line (students?) could very easily install the tool.
We could use https://github.com/volks73/cargo-wix for this.

I just tried cargo-wix and it seems quite promising. I got a working installer in just a few minutes. We just need to tweak some of the settings generated for wix and add some imagery.

Adding it to chocolatey or scoop might also help. I don't know though if they accept projects this young yet.


[NOT SOLVED] Can't register a new subscriber : "Origin 'null' is therefore not allowed access."

Hello,
I use NodeJS and I want to add new subscriber with API.
But when I call the route, I have this error :

Failed to load https://myApp.herokuapp.com/addSubscriber: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://myWebsite.com' is therefore not allowed access. The response had HTTP status code 503.

So this is my code :
ANGULARJS :
[$scope.addSubscriber = function(mail,surname){
    $scope.subscriberSurname = surname;
    $scope.subscriberMail = mail;

    console.log($scope.subscriberSurname,$scope.subscriberMail);

    $.post(SERVER_SIDE_MAIL, {

              mail: $scope.subscriberMail,

              surname: $scope.subscriberSurname,

              list_id: 5

          }, function(res) {}
 })

}](url)
And NODEJS Route :
[](app.post('/addSubscriber', function(req, res, next){
res.header("Access-Control-Allow-Origin", "*");
res.header("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept");
next();
var client = new Mailin("https://api.sendinblue.com/v2.0","MyAPIKey");
console.log(req.body);
var mail = req.body.mail;
var surname = req.body.surname;
var list_id = req.body.listid;
data = { "email" : mail,
"attributes" : {"PRENOM":surname},
"listid" : listid
}
client.create_update_user(data).on('complete', function(data) {
console.log(data);
});
});)
Is something wrong ? Please, help me ...
Thank you.
PS : NodeJS code is in server side, I specify this because my previous post was closed even before the problem was solved.
Please do not close this one until the problem is solved. Thank you.

Hi @Yngdev31
It seems that CORS is not enabled for accessed URL https://myapp.herokuapp.com/addSubscriber from https://myWebsite.com.
That is why you received below error:

Failed to load https://myApp.herokuapp.com/addSubscriber: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://myWebsite.com' is therefore not allowed access. The response had HTTP status code 503.

Hope that helps!
Thanks
SendinBlue Team


Test our implementations against libgcc

This won't work on msvc because there is no libgcc_s.so there. Instead we can link to msvcrt.lib, which contains the intrinsics we want to test against. However, the intrinsics in msvcrt.lib are named differently from the ones in gcc_s/compiler-rt. This is good because we can statically link against that library without worrying about name collisions but it's also annoying because we must now translate from msvcrt naming to compiler-rt naming.
@retep998 has provided us with a list of the intrinsics available in msvcrt.lib. But we still need to translate the names from msvcrt to compiler-rt. That can be done by looking into llvm source code. For example there are code sections like:
// lib/Target/X86/X86ISelLowering.cpp

  if (Subtarget.isTargetKnownWindowsMSVC()) {
    // Setup Windows compiler runtime calls.
    setLibcallName(RTLIB::SDIV_I64, "_alldiv");
    setLibcallName(RTLIB::UDIV_I64, "_aulldiv");
    setLibcallName(RTLIB::SREM_I64, "_allrem");
    setLibcallName(RTLIB::UREM_I64, "_aullrem");
    setLibcallName(RTLIB::MUL_I64, "_allmul");
    setLibcallCallingConv(RTLIB::SDIV_I64, CallingConv::X86_StdCall);
    setLibcallCallingConv(RTLIB::UDIV_I64, CallingConv::X86_StdCall);
    setLibcallCallingConv(RTLIB::SREM_I64, CallingConv::X86_StdCall);
    setLibcallCallingConv(RTLIB::UREM_I64, CallingConv::X86_StdCall);
    setLibcallCallingConv(RTLIB::MUL_I64, CallingConv::X86_StdCall);
  }

that contain the msvcrt names. And other sections like this one:
// lib/Target/ARM/ARMISelLowering.cpp

    } LibraryCalls[] = {
      // ...

      // Integer division functions
      // RTABI chapter 4.3.1
      { RTLIB::SDIV_I8,  "__aeabi_idiv",     CallingConv::ARM_AAPCS, ISD::SETCC_INVALID },
      { RTLIB::SDIV_I16, "__aeabi_idiv",     CallingConv::ARM_AAPCS, ISD::SETCC_INVALID },
      { RTLIB::SDIV_I32, "__aeabi_idiv",     CallingConv::ARM_AAPCS, ISD::SETCC_INVALID },
      { RTLIB::SDIV_I64, "__aeabi_ldivmod",  CallingConv::ARM_AAPCS, ISD::SETCC_INVALID },
      { RTLIB::UDIV_I8,  "__aeabi_uidiv",    CallingConv::ARM_AAPCS, ISD::SETCC_INVALID },
      { RTLIB::UDIV_I16, "__aeabi_uidiv",    CallingConv::ARM_AAPCS, ISD::SETCC_INVALID },
      { RTLIB::UDIV_I32, "__aeabi_uidiv",    CallingConv::ARM_AAPCS, ISD::SETCC_INVALID },
      { RTLIB::UDIV_I64, "__aeabi_uldivmod", CallingConv::ARM_AAPCS, ISD::SETCC_INVALID },
    };

that contain the compiler-rt names. Using that information you can conclude that RTLIB::UDIV_I64 === __aeabi_uldivmod === _allmul.
With that background information, here are the next steps:

Create a msvcrt crate that links to msvcrt.lib and binds to the msvcrt intrinsics. That crate must expose the same API as the gcc_s crate. Basically, it must provide functions like __muldi3: fn() -> Option<extern unsafe fn(u64, u64) -> u64>. The crate must handle the differences in naming and signature of intrinsics between msvcrt and compiler-rt.
Then, probably, we only need to add a #[cfg(target_env = "msvc")] extern crate msvcrt as gcc_s to the root of the rustc-builtins crate (for tests only).


enforce-one: takes in list of any type and returns the first item in list

enforce-one seems to allow for passing in a list of any types (i.e. [true, false], [3, 4]). When this occurs, it returns the first item of the list. See examples below.
pact> (enforce-one "some" [false, true])
false
pact> (enforce-one "some" [true, false])
true
pact> (enforce-one "some" [false, false])
false
pact> (enforce-one "some-error-message" ["true","false","false","false","false","false"])
"true"
pact> (enforce-one "some" [3, 4])
3

It seems that enforce-one should only accept a list of other enforce statements.
Docs should be updated.

I think the problem here is that the Pact type for enforce-one, [bool] -> bool, is simply wrong - it does not have enough data to tell people that the list of bool must be tests, otherwise it has suprising behavior. The solution to this would be to either document the spooky behavior entirely (which does not scale), or to write tx-failing enforcement types into the type system.


Devise user creation with accepts_nested_attributes_for : belongs_to relation requires "optional: true" for validations to pass

Scenario:

User can have many Roles
3 Models: User -< Userrole >- Role
User+Userrole are created using the "nested models" approach (accepts_nested_attributes_for)
Validation fails with: "Userroles user must exist"

Models:
class User < ApplicationRecord
  has_many :userroles
  accepts_nested_attributes_for :userroles
end

class Userrole < ApplicationRecord
  belongs_to :user, optional: true  # <--- This seems to be required and disables the foreign_key check
  belongs_to :role
end

class Role < ApplicationRecord
  has_many :userroles
end

The failed validation seems to be the result of how Devise interacts with Rails 5's enforced foreign_key presence validation. (I wrote a test script that represents this situation, but as a "pure" version, not based on/including the Devise account creation mechanism - the script passed without errors (change the file extension from .txt to .rb): record_creation_test_script.txt)
The mode Userrole thus currently requires "optional: true" and therefor disables the foreign_key check.

optional: true is a feature of rails 5 to check associated objects are present. May i know what is the problem that you are facing with devise on this.

The problem is that if I use Devise's user creation mechanism to create a User in the scenario explained above (meaning: with the nested attributes of Userroles), then the User is not created - its validation fails with "Userroles user must exist". The validation does however pass if I add the "optional: true" as explained above.

John is right...the optional: true on a has_one model had the same problem.  It's super irritating and I wasted half a day trying to figure it out.

Hi @john-999, thank you for the report.
I've changed your script to include Devise and still seems to work. Please let me know if I missing something. This is the code I've used:
begin
  require "bundler/inline"
rescue LoadError => e
  $stderr.puts "Bundler version 1.10 or later is required. Please update your Bundler"
  raise e
end

gemfile(true) do
  source "https://rubygems.org"
  gem "rails", "~> 5.0"
  gem "sqlite3"
  gem "devise"
end

require "active_record"
require "minitest/autorun"
require "logger"
require 'rack/test'
require 'action_controller/railtie'
require 'devise/rails/routes'
require 'devise/rails/warden_compat'

# This connection will do for database-independent bug reports.
ActiveRecord::Base.establish_connection(adapter: "sqlite3", database: ":memory:")
ActiveRecord::Base.logger = Logger.new(STDOUT)

Devise.setup do |config|
  require 'devise/orm/active_record'
  config.secret_key = 'secret_key_base'
end

class TestApp < Rails::Application
  config.root = File.dirname(__FILE__)
  config.session_store :cookie_store, key: 'cookie_store_key'
  secrets.secret_token    = 'secret_token'
  secrets.secret_key_base = 'secret_key_base'
  config.eager_load = false

  config.middleware.use Warden::Manager do |config|
    Devise.warden_config = config
  end

  config.logger = Logger.new($stdout)
  Rails.logger  = config.logger

end

class User < ActiveRecord::Base
  devise :database_authenticatable
  has_many :userroles
  accepts_nested_attributes_for :userroles
end

class Userrole < ActiveRecord::Base
  belongs_to :user #, optional: true  # <--- This seems to be required with Devise, and it disables the foreign_key check
  belongs_to :role
end

class Role < ActiveRecord::Base
  has_many :userroles
end

Rails.application.initialize!

ActiveRecord::Schema.define do
  create_table :users, force: true do |t|
    t.string :name
    t.string :email,              null: false
    t.string :encrypted_password, null: true
  end

  create_table :userroles, force: true do |t|
    t.integer :user_id
    t.integer :role_id
  end

  create_table :roles, force: true do |t|
    t.string :name
  end
end

Rails.application.routes.draw do
  devise_for :users

  get '/' => 'test#index'
end

class ApplicationController < ActionController::Base
end

class TestController < ApplicationController
  include Rails.application.routes.url_helpers

  before_action :authenticate_user!

  def index
    render plain: 'Home'
  end
end

class BugTest < Minitest::Test
  def test_parent_child_record_creation_with_nested_attributes
    role = Role.create!(name: 'Administrator')
    user = User.create!(name: 'Dan', email<EMAIL_ADDRESS>password: '123', password_confirmation: '123', userroles_attributes: [role_id: role.id])

    assert_equal 1, Role.count
    assert_equal 1, User.count
    assert_equal role.id, user.userroles.first.role_id
  end
end

I'm closing this issue because it has not had recent activity.
If you're still facing this on the latest version, please open a new one with all the information requested in the template.
Thank you!


Initial implementation

Implementation
Unit tests
Documentation
Code coverage
CI

Current coverage is 100.00%

Branch #1 has no coverage reports uploaded yet.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.


Label issues according to comments

Short description:
Github actions workflow which listens to comments on issues, and labels accordingly.

/assign myakove

/assign  @rnetser

@AdiZav this can be closed


APM Agent enhacements

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[ ] Bug
[ ] Requirement
[ X ] Feature or performance improvement

Requirement or improvement
Hi, I would like to add the following plugins in order to be able to monitor better the Java application.

dropwizard plugin - we have some old services who use Dropwizard as framework, we would like to have some close integration as Spring application has
Hibernate plugin
MyBatis plugin
add total time spent queying DB(sql/mongo), currently there is only the prepare statement and the commit, it would be better if could get the whole time
same goes for external http request

and the last thing is still far ahead but it is something to think on
currently there is a big project in process - OpenTelemtry, which is merge between opentracing and opencensus, 2 of the largest tracing platforms, maybe think on a way to integrate with their agent as well, for better understanding of the  applicaiton perfomance.
willing to help in whatever i can(would need some reference though)
in general great project and great work!!!!

For plugins, we are open to accept, take a ref to plugin development document.
For DB, whole access time is logically, it is different. I think more reasonable metrics are transaction time metrics, but it is not easy.
Speaking external http, it is shows in topo, just don't show endpoint level. It looks like a little too much payload to analysis and storage. Because at the agent perspective, there is not real external call.
OpenTelemetry, I would not be too optimistic. I am a member OpenTracing Specification Council for long time, that thing is not that good as it described. Due to we have auto instrumentation plugin, OpenTelemetry  and OpenTracing things should be treated as an manual instrument API in business codes only, but not in framework level. We have OpenTracing toolkit for that purpose. You could use it today.

Plugin should be easy to start.

For plugins, we are open to accept, take a ref to plugin development document.
For DB, whole access time is logically, it is different. I think more reasonable metrics are transaction time metrics, but it is not easy.
Speaking external http, it is shows in topo, just don't show endpoint level. It looks like a little too much payload to analysis and storage. Because at the agent perspective, there is not real external call.
OpenTelemetry, I would not be too optimistic. I am a member OpenTracing Specification Council for long time, that thing is not that good as it described. Due to we have auto instrumentation plugin, OpenTelemetry and OpenTracing things should be treated as an manual instrument API in business codes only, but not in framework level. We have OpenTracing toolkit for that purpose. You could use it today.

can we have opencensus toolkit as well?
or it is to big assignment
i will look on the documentation and will see how i can build plugins
thanks!

Toolkit is also open to contribute, but build one takes time. Today, core committers at least are not working on this. I just even added bootstrap auto instrumentation. Most users, if they want codes level instrumentation, they choose skywalking annotation to target method.


Filetype for all PlantUML diagrams

Description
Filetype specification for all PlantUML diagrams
Type of change

Documentation update

Testing steps
N/A

Codecov Report

Merging #166 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #166   +/-   ##
=======================================
  Coverage   40.20%   40.20%
=======================================
  Files          11       11
  Lines        1343     1343
=======================================
  Hits          540      540
  Misses        795      795
  Partials        8        8

Impacted Files
Coverage Δ

storage/errors.go
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


huynn-2311420

Can you contribute to my repo https://github.com/Ngochuy2137/AttractingContributors-fruits/tree/main ?


Batch conversion out of order.

When following the video conversion procedure (substituting avconc for ffmpeg) the frames are out of order.
The extracted frames in the "frames" folder are right.
The frames in the "new-frames" folder are out of order so when the video is rebuilt, it is out of order.

Did you sort the input file list?
find ./frames -name "*.png" |sort > data/frame.txt

Yes, I have linked the sort.txt file so you can look over it if you like.
http://pastebin.com/cWpUWsyS

Sorry for replying late.
Can you try to use -o new_frames/%08d.png option?
For example,
# cleanup ./new_frames first. ; rm new_frames/*
th waifu2x.lua -m noise -noise_level 1 -resume 1 -l data/frame.txt -o new_frames/%08d.png
ffmpeg -f image2 -r 24 -i new_frames/%08d.png -i audio.mp3 -r 24 -vcodec libx264 -crf 16 video.mp4

I was not able to reproduce this issue. But I guess that is caused by the filename format.

I'll try that, it may take some time to respond due to it taking a while for the upscaling.

From what I can tell, it looks like that fixed it.  Only ~1500 of the ~9000 frames are done so far but it all looks good.
As always, thanks for you hard work.

NAVER - http://www.naver.com/
<EMAIL_ADDRESS>님께 보내신 메일 <Re: [waifu2x] Batch conversion out of order. (#53)> 이 다음과 같은 이유로 전송 실패했습니다.

받는 사람의 메일박스 용량이 가득 찼습니다.


Dockerize CRD code generation to fix regression with Go modules

Fixes #996
Signed-off-by: Qiu Yu<EMAIL_ADDRESS>

Thank you for your PR. In future, please do not send code until the design has been discussed on the issue. FWIW, adding a go mod vendor before running update generated would probably have worked.

@davecheney Thanks for the quick comment! Please consider it as a PoC as I hit the issue myself and tried several ways to remediate. Hence sent out the PR for further comments / feedbacks.
go mod vendor ignores all non-go files, hence the generate-groups.sh file from k8s.io/code-generator is gone missing. Meanwhile, code-generator project itself not seem to be go module ready[1], so figured Docker approach could be a good workaround till there's a better solution.
[1] https://github.com/kubernetes/code-generator/issues/57

go mod vendor ignores all non-go files, hence the generate-groups.sh file from k8s.io/code-generator is gone missing.

Sigh, I really wish dependency managers would get out of the business of deciding what is and is not source code.

Thanks for the comments. Fair enough points.
I understand that we don't want to carry the maintenance burden for a less infrequent thing. But before we close on this and move to the document approach, feel like several other points worth to be mentioned just to ensure that we all on the same page.
The whole idea of the proposed change is to have

repeatable build

For instance, same code-generator version has to be used, no excess code generated after running the code generation by anyone who cloned the project, etc.

easy to repeat build process

After the introduction of Go modules, and the fact of code-generator itself not Go module ready, it requires Contour to be placed under GOPATH[1]. The dependency of code-generator itself needs to be properly ensured (for that specific version of code-generator). Plus the fact generate-groups.sh actually runs go install[2].
All that craziness and the knowledge for getting things to build can be contained in a Docker image. If we choose to document all these details into text, that'll be lengthy for all the details in this PR, but not runnable.
I can close the PR if you still feel document is the right way to do. Optionally, if you don't like the way this change is touching the makefile targets, I can also add Dockfile to apis/generated and add document regarding how to use that Docker image for CRD generation and leave Makefile as is.
[1] https://github.com/kubernetes/code-generator/issues/57
[2] https://github.com/kubernetes/code-generator/blob/kubernetes-1.12.6/generate-groups.sh#L53

Thank you for your reply.
Fundamentally this debate is why we have our talk, then code policy. I am grateful for your contributions, but now we're in the situation where you have done some work which you are emotionally invested in and I am in the position of feeling like the bad guy because I am refusing work you have already done.
If you had discussed your implementation on #996 then I would have told you that I don't want to see docker mixed into this. I may have mentioned that I'm not really impressed with go modules and this bug was something that made me consider reverting to dep.
@glerchundi has proposed #1010 which is a simpler fix and offers less maintenance burden in the future. I'm not happy that they did this without declaring their intentions on #996, I do not wish to create a combative environment on this project.
I've explained that compared to things which we do all the time during a development cycle, like update the envoy grpc definitions, regenerating the CRD definitions happens far less frequently. In an ideal world rebuilding the generated code is something that might happen on each build so that we never check it in, but being pragmatic the generated code has never once caused a problem when bumping the kubernetes dependencies and the envoy gRPC definitions are a constant pain in the rear. Given the velocity goals of this project -- small incremental releases every month or so -- I just can't get that excited about investing engineering time in being able to hermetically reproduce the CRD definitions.
As I said previously I would be perfectly fine with a simple written process in a markdown file, I think that is a reasonable tradeoff of complexity for its infrequent usage. However @glerchundi has proposed #1010 which is an overall simpler solution than this PR.
However, before I review #1010 I want to conclude this discussion. You may not agree with my decision here, but I hope to at least explain my reasoning clearly, and hopefully direct your attentions to issues which will have a higher payoff for Contour users.

Thank you Dave for the detailed explanation. It totally makes sense to me. I'll close this PR and instead watch #1010 for how it goes.

Thank you for your understanding.


requires PIP but doesn't install it

Error: Could not set 'present' on ensure: Could not locate the pip command. at 33:/tmp/modules/awscli/manifests/init.pp
Error: Could not set 'present' on ensure: Could not locate the pip command. at 33:/tmp/modules/awscli/manifests/init.pp

What $::osfamily are you using? If pip is not installed or managed in the node catalog, it will install it on debian, redhat, or osx:  https://github.com/justindowning/puppet-awscli/tree/master/manifests/deps.


include snippets not working

@braaannigan the include snippets in the new optimizations page doesn't seem to be loading.
https://pola-rs.github.io/polars-book/user-guide/lazy-api/lazy-query-plan.html

P.S. join_asof and groupby_dynamic are not supported streaming.
explode, melt are.

Changes applied in #291


[10.x] Fixes retrying failed jobs causes PHP memory exhaustion errors when dealing with thousands of failed jobs

fixes laravel/framework#49185

Problem fixed ✅


Profil page headline/user name

What’s missing (but in the design already) is the addon „Diagnostic Laboratory“/„Research Laboratory“/„Qualified Volunteer“.

See for example here: https://www.figma.com/file/2P0PFrxgSIXC7L1Hj1IHb1/Platform-Design?node-id=231%3A1317


[Question] Can I have multiple models in one flow

Seems I can only have one model in one flow now, but just wondering can langflow chain together multiple models? Or this task should belong to langchain but not langchain? Thanks

Hi @anovazzi1 , this is perfect! I think we are on same picture, evaluating https://docs.langflow.org/components/custom it now :-)

You are welcome, call me if you need ;)


logger.error without pattern

StreamData._buildErrorMessage = function (error) {
logger_1.Logger.error(error);
logging the error without a message pattern.
when the network is lost.
Uncaught TypeError: Cannot read property 'replace' of undefined  in the Logger class
logger_1.Logger.error("error occurred: {0}", error);

Hi @zhangyuezhong ,
Thank you for testing our demo.
I understand that you have an error when your api connection is lost.
Could you please tell us which demo did you test and on which browser?
Guillaume


keras-contrib only work with Keras 2.x, not 1.x?

will it also support Keras 1.x?
Thanks.

keras-contrib is currently only unit tested against the keras master branch.


New translation added: Tajik

Added localization file for Tajik language

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

Comparison is base (c09021d) 99.89% compared to head (9d6b6a8) 99.89%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master     #440      +/-   ##
============================================
- Coverage     99.89%   99.89%   -0.01%
  Complexity      379      379
============================================
  Files            25       25
  Lines           970      966       -4
============================================
- Hits            969      965       -4
  Misses            1        1

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


Bump version for next release

Bump version for next release

Codecov Report

Merging #1138 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop    #1138   +/-   ##
==========================================
  Coverage      35.53%   35.53%
  Complexity       540      540
==========================================
  Files            103      103
  Lines           4595     4595
  Branches         710      710
==========================================
  Hits            1633     1633
  Misses          2814     2814
  Partials         148      148

Continue to review full report at Codecov.

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


[T7][F11-C2]

V0.0 only.

@njyjn @imhongw @marinirah @wengkiat  some replies given to your replies ~ do view it and close PR after review.

btw ~ where are your dev guides? can you guys do a PR on that so that I can give you guys some review?


Ln force no weight sharding

Sharding affine transformation weights in TE is currently unsupported. This PR forces replication of gamma/beta in the case of LayerNorm and gamma in the case of RMSNorm even if they are sharded as inputs.

/te-ci jax


Fix diff3 markers

I have in my .gitconfig:
[merge]
    conflictstyle = diff3

And in conflicts:

Without merge-conflicts package:

It seems markers are detected correctly, but headers are misplaced. It might happen without diff3.

@ypresto and missed changes after ====== markers

It has same color to background. So it looks missing but is actually shown there.

It can be confirmed by that only one = is shown (and rests are overlapped with header).

:wave: Thanks for taking the time to file an issue here! Unfortunately, this repository is being deprecated, so I won't be getting to this one here.
This one should be taken care of by the new git and GitHub package for Atom. If you see something similar, please file an issue there to let us know. Thanks 🙇


Cant create new bots, Error calling npm to fetch template.

When creating a new bot, I receive the next error:
Error calling npm to fetch template. Please ensure that node and npm are installed and available on your system. Full error message: Command failed with exit code 1: npm install -g --prefix C:\Users\RY36863\AppData\Roaming\BotFrameworkComposer\.yo-repository --loglevel error --no-optional @microsoft/generator-bot-empty@*

At first the software was not detecting nodejs, so after running again the installation the installation error was not prompted again. Now I am facing some error with the npm and can not figure out why.
Version
Release: 2.1.2
SDK 4.12.0
Browser

[ ] Electron distribution
[ x ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[ x ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to 'Create New'
Click on 'Empty Bot'
Click on 'create', using the default options: Name "empty", Runtime type "Azure web App", Location "anywhere"
Note the windowd of "downloading template"
See error

Expected behavior
Bot created
Screenshots

Please run the following commands and report what is returned:

npm -v
node -v

Also, if you try and run the command on its own, does it work?
npm install -g --prefix %userprofile%\AppData\Roaming\BotFrameworkComposer.yo-repository --loglevel error --no-optional @microsoft/generator-bot-empty@*

Closing as duplicate of:
https://github.com/microsoft/BotFramework-Composer/issues/9769
Please monitor and comment there.


ATD API 31

Codecov Report

Merging #294 (6d56736) into main (09c570d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #294   +/-   ##
=======================================
  Coverage   71.81%   71.81%
=======================================
  Files          74       74
  Lines        3378     3378
  Branches      551      551
=======================================
  Hits         2426     2426
  Misses        634      634
  Partials      318      318

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


using (scroll) on any other element causes Maximum call stack size exceeded

If I use (scroll) on any other element in the ui, where I also use angular2-multiselect-dropdown, I get following error:
core.js:6456 ERROR RangeError: Maximum call stack size exceeded
at SafeSubscriber._tryOrUnsub (Subscriber.js:191:32)
at SafeSubscriber.next (Subscriber.js:122:1)
at Subscriber.next (Subscriber.js:72:1)
at Subscriber.next (Subscriber.js:49:1)
at EventEmitter.next (Subject.js:39:1)
at EventEmitter.emit (core.js:25946:1)
at ScrollDirective.onClick (angular2-multiselect-dropdown.js:1014:1)
at ScrollDirective_scroll_HostBindingHandler (angular2-multiselect-dropdown.js:1019:97)
at executeListenerWithErrorHandling (core.js:15285:1)
at Object.wrapListenerIn_markDirtyAndPreventDefault [as next] (core.js:15323:1)
Version 5.0.4
Angular 12.1
example use:
"<div (scroll)="onScroll($event)">"

Same here. Have you found a way around it?


[WIP] Eliminate witness table accessors.

Witness table accessors return a witness table for a given type's
conformance to a protocol. They are called directly from IRGen
(when we need the witness table instance) and from runtime conformance
checking (swift_conformsToProtocol digs the access function out of the
protocol conformance record). They have two interesting functions:

For witness tables requiring instantiation, they call
swift_instantiateWitnessTable directly.
For synthesized witness tables that might not be unique, they call
swift_getForeignWitnessTable.

Extend swift_instantiateWitnessTable() to handle both runtime
uniquing (for #2) as well as handling witness tables that don't have
a "generic table", i.e., don't need any actual instantiation. Use it
as the universal entry point for "get a witness table given a specific
conformance descriptor and type", eliminating witness table accessors
entirely.
Make a few related simplifications:

Drop the "pattern" from the generic witness table. Instead, store
the pattern in the main part of the conformance descriptor, always.
Drop the "conformance kind" from the protocol conformance
descriptor, since it was only there to distinguish between witness
table (pattern) vs. witness table accessor.
Internalize swift_getForeignWitnessTable(); IRGen no longer needs to
call it.

Reduces the code size of the standard library (+assertions build) by
~149k.

BinaryFloatingPointPropertiesBinade
114
105
-7.9%
1.09x

ArrayOfPOD
846
782
-7.6%
1.08x

ObjectiveCBridgeStubDateMutation
771
714
-7.4%
1.08x

CStringLongAscii
3636
3369
-7.3%
1.08x

Code size: Swift libraries

TEST
OLD
NEW
DELTA
RATIO

Regression

libswiftSwiftOnoneSupport.dylib
217088
221184
+1.9%
0.98x

Improvement

libswiftObjectiveC.dylib
20480
16384
-20.0%
1.25x

libswiftCoreGraphics.dylib
65536
61440
-6.2%
1.07x

libswiftAVFoundation.dylib
69632
65536
-5.9%
1.06x

libswiftAppKit.dylib
81920
77824
-5.0%
1.05x

libswiftStdlibUnittest.dylib
409600
405504
-1.0%
1.01x

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

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


[WARNING] Plugin without mojos.

I am able to generate output for the confluence-summary report, but I don't get
any output for the plugin-confluence-summary report.  I notice that there are
warnings in the log regarding no mojo's found, but I am not sure what the real
issue is.

I have attached the output from maven.  I am running on Ubuntu 11.10, Sun JDK
1.6.x, and maven 3.x.

Let me know what else you might need to help troubleshoot this issue.

thanks,
Garrett

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 6 Jan 2012 at 1:41
Attachments:

site.out

Having a similar issue

[INFO] --- confluence-reporting-maven-plugin:4.6:deploy (default-cli) @ x-maven-plugin ---
[INFO] executeReport isSnapshot = [true] isRemoveSnapshots = [false]
Site
Page: my-site-generation-test - jar:file:/c:/Data/.m2/repository-m3/org/bsc/maven/confluence-reporting-maven-plugin/4.6/confluence-reporting-maven-plugin-4.6.jar!/defaultTemplate.confluence
[WARNING] Plugin without mojos. No mojo definitions were found for plugin: com.y:x-maven-plugin.
MojoScanner:class org.apache.maven.tools.plugin.scanner.DefaultMojoScanner

With Maven 3.3.3  and
confluence-reporting-maven-plugin:4.6  as a build plugin
site:3.4
maven-plugin-plugin:3.4
running from command line   mvn confluence-reporting:deploy
after mvn clean package site
Initially I thought it was due to using maven2 style comment annotations, so updated to java1.5 style annotations which didn't help.


Top N query: postAggregations has a bug

when i use postAggregations, I select the type is "arithmetic", but the post data is  "cardinality"

Hello @zhangfangkai
Thank you for the report! Indeed there is a typo there https://github.com/grafadruid/druid-grafana/blob/master/src/builder/postaggregation/Arithmetic.tsx#L64
I'll provide a fix ASAP

@zhangfangkai  here it is, freshly baked https://github.com/grafadruid/druid-grafana/releases/tag/v1.0.3
Feel free to close the issue if it's all right for you :)

@zhangfangkai had you any chance to give that release a try? all is fine ?

i haven't try the new release, but thanks for your modify, i think it will be ok!


Support other encodings on read failure

Sometimes files can contain characters in a enconding different from UTF-8. In such cases you can try reading with other encodings until no decode error is encountered instead of terminating the program. Latin-1 is a common encoding for the Portuguese language.

Great idea @eduardomdc . Will work for the most common cases and the user won't need to manually set encoding on each application.
However, existing code that sets encodings might fail, since iterating on a string is also possible, and would fallback to trying each character as an encoding. Maybe you could add a type-check before iterating? Something like (inside each read function body):
if type(cls.ENCODING) == str:
    cls(reader.read(content, cls.ENCODING, *args, **kwargs))
else:
    # your new implementation

We might add a deprecation warning and drop the support for str types in a future major release, but for now it won't break some applications that might use this.

Indeed, well thought @rjmalves . I overlooked this possibility.


feat: stack with linked list

This is an implementation of a singly linked list and a stack based on a singly linked list.
Additional note: I had some trouble with the tests of the stack implementation. All tests passed when running them individually, but however they failed when running them "all at once" (testing the whole file). The issues that came seemed weird, as for example there was a "Stack overflow" error when popping the element from the stack. I think and hope this is a local issue with my machine. If it is one with the tests I wrote, feel free to correct me.
And, just to clarify it here, I adjusted the test cases of the linked list from the doubly linked list (and verified their functionality), because the operations are basically the same and I think the test cases fulfilled everything. So credits to @zFl4wless for writing these tests.

Looks good. I wonder whether you could reasonably deduplicate the tests by applying the singly linked list tests to the doubly linked list as well?

Do you mean I should merge them in one single file and execute the tests for both lists there?

If the singly linked list has the same interface as the doubly linked one (where of course some operations will be linear rather than constant time): Yes, you can use one file and a test parameterized in terms of the constructor to use. You might as well use three files though: One for the parameterized tests and two (trivial) files which just import the parameterized test and execute it for a given implementation. For an example of this, see the queue tests consolidated in https://github.com/TheAlgorithms/TypeScript/commit/124890c73e5cb188d13d26a2c619c160364d982e: Both the ArrayQueue and the LinkedQueue use the same tests.
However, if you want to support only a subset of the doubly linked list operations, you should still keep the "doubly linked list"-only tests for the doubly linked list; the common tests should however be deduplicated using the parameterization described above.

Odd. The tests are failing due to something that hasn't even been touched. Perhaps you need to rebase?

Alright, I check this out

Well yeah, seems logical that after the first test, a stack overflow occurred, when pushing three new elements before each test run.


Moved all dashboard code to widgets module

Makes it easier to use in other projects

A couple of small things:
cfchecker can now be installed using pip, so the git install can be removed in requirements.txt (unless you want the dev version).
We have no test coverage for the widgets/visualisation, but I assume this is OK as they're so dependent on running in a note book (I'm not too sure how we'd adequately test them).
Can be merged without these if needed.


Codefix doesn't rename discriminated property correctly

Bicep version
v0.3.255
Describe the bug
See gif:

Gif shows both the bug and expected behavior.
To Reproduce

Decompile the MonitoringApp.template.json (don't want to share it publicly) from our internal repo
Scroll to the lines in the gif

Additional context
Add any other context about the problem here.

This turns to be only happening on discriminated property keys, which is why we did not catch it earlier.


access token console log

https://github.com/MatheusBViana/my-lolla/blob/bc456b63a10bfb4eaa5fd868a28e39965eae8d36/authorization_code/public/app.js#L87
hey I think you forgot this log on your code 😁.
Best regards,
Victor.

Thanks, fixed!


WIP: Add Android build

[x] Build VTK in CI in 64-bits ARM and x86 architectures
[x] Build libf3d with minimal modules in CI
[x] Add JNI wrapper in CI (expose libf3d-java.so artifacts)

Will be done later:

[ ] Create Java or Kotlin interface
[ ] Create Gradle build system
[ ] Generate .apk (expose in CI artifacts)
[ ] Add Exodus module
[ ] Add Assimp module
[ ] Add OCCT module
[x] Add 32-bits architectures

Current status:

VTK is building fine on arm64 and x64, fixed here but fails for 32-bits architectures.
libf3d is building properly without OCCT/Assimp modules (it's currently 42MB, we need to strip unused symbols)
JNI native wrapper is done and working
VTK multitouch interactor style is really bad, we will need to create one ourselves
Java interface prototype is done, but will need a complete rewrite (ideally in Kotlin) to create a good user experience (let's discuss the specs)

FYI @mwestphal @jpouderoux

Java interface prototype is done, but will need a complete rewrite (ideally in Kotlin) to create a good user experience (let's discuss the specs)

What does this mean ?

Java interface prototype is done, but will need a complete rewrite (ideally in Kotlin) to create a good user experience (let's discuss the specs)

What does this mean ?

Basically, define the interface. Right now, I have a single OpenGL view in full screen. We may want to have a big + button for opening files, a previous and next button, a button to play/stop animations, etc...
We need to sketch the user interface basically.

Current status:
https://user-images.githubusercontent.com/6069752/186754316-5d9a3186-c151-49e3-89f8-4fe67fecca54.mp4

nice, the zoom is a bit janky, is it a FPS issue or interaction issue ?

It's an interaction issue

Android build is merged here: #382
New required APIs here: #383
This PR will now focus on java bindings

Actually, closing this one for #390


[BPF] tcpdump-like debug expressions for tc programs

Description
If BPFLogFilters is set only specified packets on specified devices
trigger log actions. In any other case packets go through without the
overhead of logging.

A filter program is called by the preamble and that program decides
whether packets should be processed by a set of programs with or without
logging. This effectively means that there are two paths that a packet
can take when logging is enabled.

If BPFLogFilters is not specified, that filter program matches all
packets and every program logs for every packet like the current
firehose.

As CTLB logging also goes to the same trace pipe, it mixes with tc logs
and thus CLTB logging must be explicitly enabled if BPFLogFilters is
specified by including 'ctlb=on' to avoid logging more than desired.
CTLB is still a firehose.

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

BPFLogFilters allow specifying fine grained log filters that reduce the amount of logs emitted when debugging.

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

errors in CI are unrelated


Added isObjectID function

Simple but efficient & useful (checks whether a string is a valid Mongo ObjectID or just a normal string

Coverage decreased (-0.32%) to 99.03% when pulling 308d6e268e8ec9836910bbd722fd0e39e2ee6f29 on perfaram:master into bb406b8f480824d6bfb120dae2d7d7a633463248 on kissjs:master.

Coverage increased (+0.0%) to 99.35% when pulling a812ea09005ee60268cf7b3c05e3c39a607ab542 on perfaram:master into bb406b8f480824d6bfb120dae2d7d7a633463248 on kissjs:master.

Coverage increased (+0.0%) to 99.35% when pulling a812ea09005ee60268cf7b3c05e3c39a607ab542 on perfaram:master into bb406b8f480824d6bfb120dae2d7d7a633463248 on kissjs:master.

Okay, I caught up on the test, now it's the same as before.

+1
Thanks!


[eval] refactor process instance logic into update_progress

Short description of the problem this fixes or functionality that this introduces. This may be used for the CHANGELOG
The fixes in https://github.com/All-Hands-AI/OpenHands/pull/3854 fix most multi-processing issue, but at some point, we'd get errors like:
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-109' coro=<Runtime.on_event() done, defined at /home/xingyaow/OpenDevin-dev/openhands/runtime/runtime.py:111> exception=HTTPError('404 Client Error: Not Found for url: https://21ca5bc7-c846-49b5-a77a-1287ad5d6069.runti
me.all-hands.dev/alive')>

Because we never directly called future.result() which cause asyncio to complain - this gets evaluation to stuck.
See relevant info here.

Give a summary of what the PR does, explaining any non-trivial design decisions
This PR tries to fix this by:

(1) refactoring all the exception handling into update_progress function, and get rid of the previous process_instance wrapper.
(2) always call future.results() inside update_progress and handle exception from there

Link of any specific issues this addresses

Just ran 200+ instances without error - this fix should be effective

I still got one. 😢
The run started on this branch, prior to merge:
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-271' coro=<Runtime.on_event() done, defined at /Users/enyst/repos/odie/openhands/runtime/runtime.py:109> exception=HTTPError('503 Server Error: Service Temporarily Unavailable for url: https://db4e7849-a925-4010-90fb-165ff5e1c6d9.runtime.all-hands.dev/alive')>
Traceback (most recent call last):
  File "/Users/enyst/repos/odie/openhands/runtime/runtime.py", line 115, in on_event
    observation = self.run_action(event)
                  ^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/enyst/repos/odie/openhands/runtime/remote/runtime.py", line 238, in run_action
    self._wait_until_alive()

...

requests.exceptions.HTTPError: 503 Server Error: Service Temporarily Unavailable for url: https://db4e7849-a925-4010-90fb-165ff5e1c6d9.runtime.all-hands.dev/alive

Remote runtime, 12 instances queue, num_workers = 4
Cc @xingyaoww

@enyst ugh 😣 ... Let's debug on this again.. this is very weird


[SPARK-16182] [CORE] Utils.scala -- terminateProcess() should call Process.destroyForcibly() if and only if Process.destroy() fails

What changes were proposed in this pull request?
Utils.terminateProcess should destroy() first and only fall back to destroyForcibly() if it fails. It's kind of bad that we're force-killing executors -- and only in Java 8. See JIRA for an example of the impact: no shutdown
While here: Utils.waitForProcess should use the Java 8 method if available instead of a custom implementation.
How was this patch tested?
Existing tests, which cover the force-kill case, and Amplab tests, which will cover both Java 7 and Java 8 eventually. However I tested locally on Java 8 and the PR builder will try Java 7 here.

Test build #61469 has started for PR 13973 at commit 50ee5b6.

Test build #61469 has finished for PR 13973 at commit 50ee5b6.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61469/
Test PASSed.

Merged to master/2.0. I went ahead with this as I think it's a reasonably important fix for something that only manifests in Java 8, that we hard-kill executors and don't let them for example finish shutdown hook cleanup at all.

@srowen Seems this commit breaks 1.6 builds (https://amplab.cs.berkeley.edu/jenkins/view/Spark QA Test (Dashboard)/job/spark-branch-1.6-test-sbt-hadoop-1.0/248/)?

Oh, I think @vanzin fixed that and it wasn't then back-ported to 1.6: https://github.com/apache/spark/pull/14056 I can do that.


[openssl] Build error

Package: openssl[core]:x64-windows -> 3.2.1
Host Environment

Host: x64-windows
Compiler: MSVC 19.34.31935.0
vcpkg-tool version: 2022-11-10-5fdee72bc1fceca198fb1ab7589837206a8b81ba
vcpkg-scripts version: 345ac44ab 2024-02-09 (2 days ago)

To Reproduce
vcpkg install open62541
Failure logs
-- Using cached openssl-openssl-openssl-3.2.1.tar.gz.
-- Cleaning sources at C:/Users/Juan/vcpkg/buildtrees/openssl/src/nssl-3.2.1-8707343470.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Users/Juan/vcpkg/downloads/openssl-openssl-openssl-3.2.1.tar.gz
-- Applying patch script-prefix.patch
-- Applying patch windows/install-layout.patch
-- Applying patch windows/install-pdbs.patch
-- Applying patch unix/android-cc.patch
-- Applying patch unix/move-openssldir.patch
-- Applying patch unix/no-empty-dirs.patch
-- Applying patch unix/no-static-libs-for-shared.patch
-- Using source at C:/Users/Juan/vcpkg/buildtrees/openssl/src/nssl-3.2.1-8707343470.clean
-- Found external ninja('1.11.0').
-- Getting CMake variables for x64-windows
-- Using cached nasm-2.16.01-win64.zip.
CMake Error at scripts/cmake/vcpkg_extract_archive.cmake:19 (message):
  C:/Users/Juan/vcpkg/downloads/tools/nasm was an extraction target, but it
  already exists.
Call Stack (most recent call first):
  scripts/cmake/vcpkg_find_acquire_program.cmake:203 (vcpkg_extract_archive)
  ports/openssl/windows/portfile.cmake:60 (vcpkg_find_acquire_program)
  ports/openssl/portfile.cmake:74 (include)
  scripts/ports.cmake:170 (include)

Additional context

Duplicate of https://github.com/microsoft/vcpkg/issues/35746


Does it do Full ISO rebuild as original version?

subj

Can you please tell me a bit more about what a "full ISO rebuild" is? I'm not a real xbox 360 hacker :)
iso2god-rs is mostly a rewrite of  https://github.com/eliecharra/iso2god-cli; with a couple of features tacked on. So if a "full ISO rebuild" is not possible with https://github.com/eliecharra/iso2god-cli (this version specifically, not the original Windows one), then it is not currently possible with iso2god-rs either.

I think i got it. You mean the "backwards", GOD -> ISO conversion, right? If so, it is not currently possible, but a valid feature request. I will try to add this feature when I have the time.

Full rebuild - removing all empty sectors

The code is there from the decompile of the original windows version but wasn't exposed in the cli version.  This is very useful feature as full xbox 360 iso are all 7 to 8 GB in size but can be much smaller once the padding is removed.

Until this may be implemented the redump ISO can be processed with extract-iso to build an optimized xiso then processed with iso2god.  An extra step but a way until iso2god can preform this step.
https://github.com/XboxDev/extract-xiso
-r                  Rewrite xiso(s) as optimized xiso(s).

In the newest v1.5.0 version, I've added a --trim option to remove unused space from the end of the ISO.
It is not a "full rebuild", because it does not remove space between the files, only at the end. But I feel it should still good enough for most use cases.

@iliazeus As a suggestion, maybe you should mention that in the readme and when parameter --help is entered. I was looking for the answer what the --trim command actually doing. Removing only space at the end is for me the better method any ways since it doesn't break compatibility usually.