fix: show format as PNG if it's not an APNG

In the current implementation, if we use QImageReader::setDecideFormatFromContent(true), regular PNG files will also be handled by this plugin, and in this case, this plugin will always return "apng" as its format whether it's a regular PNG file or an APNG file. This patch is intended to fix this issue.
Another way to fix this is not handling regular PNG files at all, since I'm not familiar with APNG file structure, I choose the simplest way for now. Feel free to close this PR if you think this is not the right way to resolve this issue.
p.s. I got a question I'd like to ask. When manually renaming a valid xxx.apng file to xxx.png, this plugin will no longer recognize if it's an animated PNG or not even if we did QImageReader::setDecideFormatFromContent(true), not sure why. Should I open a separate issue for this? Thanks.

Regarding your second question: The built-in PNG image handler is always preferred to the custom defined plugins, so at least in Qt 5, there was no way of "overriding" the PNG with the APNG handler


Crashlytics: Add dispatch_once for opening sdk log file

Resolves #5903
I had a more complicated change earlier, but settled on this. The file is never closed, so this will work, and should be better than using a queue or semaphore.

@googlebot I signed it!


FR: Add Makefile to project root

Opening this for ease of tracking progress on this feature.
Ideally the Makefile would allow a user to clone the repo, run make and have all the compiled languages end up in something like a bin/ file in the root. And then for langs that don't need to be compiled, probably just copy the source code. This could also be a good step towards implementing CI and release tarball generation, so that this project will be more end-user friendly.

Closed by #7. Thanks @amyavi!


npm package needs to be updated

seems current npm package doesn't have latest commits

Agreed - we are waiting to do a complete v1.0.0 update (checklist mentioned below)
https://github.com/toranb/ember-cli-auto-complete/issues/22
To get what's in master today you can npm install the beta 1 of v1.0.0
npm install<EMAIL_ADDRESS>


Remove the use of '/' in addons paths.

Now that the standard way of describing paths inside the state tree is by using dots like this: some.deep.path I think it is a good idea to remove the use of slashes inside addons path descriptions. The :/ makes it look like an uri when it is not. Users then tend to write state:/some/deep/path and get confused on why it does not work.
Proposition: simply remove all '/' and use input:some.deep.path:
const re = /^(input|output|state):(([a-zA-Z_]+\.?)*)$/
const [ _, scheme, path ] = re.exec ( 'input:some.dee.path' )

Yeah, I think the url-scheme was a good start, but as we know have much confident in its use I think we can take the liberty to make it a "Cerebral thing". It should also be easy to migrate as you do a search and replace on input:/ and state:/.
If we vote up this I change I suggest we implement inside Cerebral. And we make Cerebral aware of what and input, an output and the state is. The state differs as we use both the get and set method on it. What that basically comes down to is that input and output use normal JS mutation, but everything else use this signature: whateverSet(path, value) and whateverGet(path).
this means that any context provider adding something to the context with a set and a get method will be usable by these "addons".
An example of this would be modules provider, which adds module to the context. Since module.state has a get and set method, it will work using: module.state:some.path

+1

So I guess we'll leave behind the URL format for something more cerebral specific.
If we move this to cerebral core then maybe it's time to move some of the "core" addons over also?

@christianalfoni Strangely, my debounce solution seems ok. Not having the ignored actions go anywhere is maybe not so good with cerebral internals but I did not see anything bad happening.
Anyway, I think you proposal is better and ignored, accepted seems like nice choices for all the a/b actions (instead of true, false, continue, etc).

What I suggest we do is implement, as also suggested by @bfitch , is implement a concept of "operators" in Cerebral core. That means we keep cerebral-addons as is, but we can deprecate it later.
The operators is inspired by cerebral-addons, but uses this new syntax and we create a convention on naming paths. To give some more insight I am thinking we can implement like this: https://gist.github.com/christianalfoni/1ab82be5d4d7c58805a0a09acf032695.
import {set, copy} from 'cerebral/operators';

export default [
  set('state:foo', 'bar'),
  copy('input:foo', 'state:bar')
]

Sounds like a doable task for the weekend

done


Bugfix from #197

Proposed Change:
Fix a bug with the demo
Change type
Put an x in the boxes that apply

[x] Bugfix

Already fixed - was looking at an out-of-date branch :)


Portable Kerberos SSPI module in Rust

Hello, I've implemented the Kerberos protocol and added C-bindings to make this crate exportable as a dynamic C library.
Kerberos implementation details:

Currently two encryption types are supported: AES256_CTS_HMAC_SHA1_96 and AES128_CTS_HMAC_SHA1_96.
Kerberos is integrated into the CredSSP too.
Can send Kerberos messages to the KDC server directly or to the KDC proxy.
It reaches KDC using the NetworkClient instance. This trait has two methods: send and send_http. The first one uses for sending messages to the KDC and the second one is for sending messages to the KDC proxy.
In restricted environments where our NetworkClient implementation is not usable, user can pass their own implementation through KerberosConfig.
In FreeRDP, where users are unable to pass the custom KerberosConfig structure, it looks for two environment variables: KDC_TYPE and SSPI_RS_KERBEROS_URL. The first one can have two possible values (KDC and KDC_PROXY) and the second specifies how it should reach the KDC. The second one contains the Kerberos destination address.

C-bindings implementation details:

all C-bindings has written in separate crate csspi in the workspace
We export two function tables with functions pointers: SecurityFunctionTableA and SecurityFunctionTableW. On Windows FreeRDP uses W-table and A-table on Linux.
The same types have different sizes on Windows and Linux. This is why I've added os-dependent macros for some structures.
Functions that are not used for RDP (CredSSP) authentication return UnsupportedFunction error.

Useful links:

RFC 4120 - Kerberos RFC.
MS-KILE is a specification that contains all information about any Windows behavior that differs from the original Kerberos Protocol.
RFC 3961 - Encryption and Checksum Specifications for Kerberos 5.
RFC 4121 - The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism.
SSPI functions list.

I improved the organization of the csspi, but I'm not sure if it's exactly what you wanted.

Sorry, I think I wasn’t specific enough. If it’s okay for you, I’ll just clean the last bits before merging (update to published dependencies and small details related to workspace). It looks to me otherwise!


Default implementation of ModelicaServices

Reported by anonymous on 4 Dec 2012 16:14 UTC
The HTML documentation of package ExternalReferences in the default implementation of ModelicaServices says
This implementation is targeted for Dymola.

but it should not be targeted for any special tool.

Migrated-From: https://trac.modelica.org/Modelica/ticket/919

Comment by dietmarw on 4 Dec 2012 16:25 UTC
FIXED in de55a183f8a396945734f11705959e855cfbfbc6


Fix implementation of GET_CURRENT_FRAME_ID on Linux

GET_CURRENT_FRAME_ID is used by the stack walker on Linux to figure out
the start of the frame. However, the implementation was still using the
win32 x64 implementation which use the return address as the frame
id. This broke the stack walker on Linux which is based on the x86
one. Changed the x64 linux implementation to match the x86 implementation.

:shipit:

LGTM


Request: Horizontal Window Scaling

HI koekeishiya,
thanks for your great work on the windowmanager so far. I lam absolutely in love with it.
I am using it since a month and have one small request/question.
currently the windows are splited 50/50 as in fig.1
this is sometimes unpractical, when I use a browser in the mainarea (marked m)
would it be possible to adjust the horizontal splitting and define one focused/main area with variable scaling? see fig. 2

this would get me closer to have a DWM like setup, which I have been using on my old thinkpad all those years.
I hope it made sense what I just typed.
greetings

You can manually adjust the split ratio using these commands (for the selected container):
kwmc window -c reduce 0.05
kwmc window -c expand 0.05

You can adjust the default split ratio using this command in your kwmrc:
kwmc config split-ratio 0.5

hi thanks for the reply, reducing and expanding nested in vertical adjustments and not horizontal. :/
I will have to try the split-ratio later at home though.

reducing and expanding nested in vertical adjustments and not horizontal

What border gets moved depends on what container is selected. You can also specifically say which border to move. Relevant snippet from the kwmc man page:
 Modify container split-ratio of window in direction
        kwmc window -c reduce <opt> <arg>
        kwmc window -c expand <opt> <arg>
        <opt>: 0 < floating point number < 1
        <arg>: north | east | south | west

The commands mentioned by @dominiklohmann should be able to do what you want. The commands are abit clunky at this moment.
I will probably tweak them to be more intuitive, in the far future. Currently working on rewriting the entire Kwm core for stability maintainability purposes.

I'd also love to see the ability to be able to hit a key and be able to use the mouse to drag around window borders and adjust other windows accordingly. I was used to doing this with Awesome.

This is not very likely to happen due to the fact that nearly all applications have a minimum window size, making it highly likely that the internal node sizes and the actual window size is not equal.
This would cause some trouble and it would not become a smooth action like it is with Linux window managers.


Coffee to ES6 ctd: Tooltips, ext pledges

I rule and have completed some work on Case Manager that's ready for review!
Picks up #1732 to put a nail in the system test failures. Starts with a lint and thenruns with it from there.
This pull request makes the following changes:

place JS changes to get build to pass from #1732

It relates to the following issue #s:

Fixes #1682

I think this ran afoul of #1686 which was making a whole host of stuff choke. My hope is that by skipping that one the rest of these will be fine.

test failures in these system tests:
submit pledge test
activity log test
display pledge errors
tooltips

Tooltips is failing because tooltip is a bootstrap method; submit pledge is failing because it relies on a vendored library that hasn't been bumped in a few years 😬

I was experimenting iwth ways to get those tests to pass by vendoring just the tooltips part of bootstrap, but it might not be possible. In the medium to long term we might have to completely mercy-kill sprockets in here before we can perfectly complete this, or rewrite a decent chunk of javascript.

This breaks the navbar dropdowns for reasons I can't figure out. Next step might be to get bootstrap out of sprockets. Sorry I couldn't untangle this.

It's with an extremely heavy heart that I'm going to close this PR - I think the problems here come from double bootstrap interactions and we'll have to untangle that before tackling this.


As a user, I want to see a chronological list of membership activities for a single library member so that I can see the complete subscription activity for that person.

Notes for testing
When you select a member from the member list and go to their detail page, the activities tab should now be clickable and will take you to the membership activity list by default (for now). This page should display a table of all membership activities (subscriptions and reimbursements).

events should be ordered chronologically by default
the table heading should be clickable to re-order the events
you should be able to click a table heading twice to sort in the reverse direction
the icons should indicate the current sort column and order
dates and durations should sort logically (i.e. duration should sort 3 months, 6 months, 1 year; look at Flecker for a good account to test this with)

If a member has no documented membership activity, you should see brief text to that effect and not an empty table. Examples to look at (no need to check all of these):

Louis Aragon
Cyrille Arvanon
Baswick
Sylvia Beach
Walter Benjamin

Check how the page looks for members with lots of subscription activity. Examples:

Pougaud
Colens, Fernand
Seurre, J
Flecker

Members with lots of events
--> I checked Hemingway first, just because! (We Love Ernest, he loved Beach)

Yes, the events are ordered chronologically
Yes, I could click through the tabs to re-order and also click to reverse. I first put in duration (shortest to longest, then longest to shortest), then tried start and end date. The only problem was with amount: when I did amount in largest to least, the renewals went 150, 20, 30, 50, 86. Same thing happened with Flecker: all the other tabs worked fine, but the amount was wonky: went 144, 16 (16 x 10 in a row), then 35, 48, 81, 81, 81. 9.69.6. Is this messed up or am I perhaps not taking price per month into account?
Yes, when I click a tab arrow it is highlighted in green to show me that I have it on

Members with no events

Yes, there is text that says "No documented membership activity." Tried this on Baswick, Beach, and Benjamin.

@clmahoney good catch! The amounts are sorting alphabetically rather than numerically. I'll flag it as needs work and add a fix.

@clmahoney this is fixed and ready for testing again.
I should have thought of this before, but please also check some accounts that include a reimbursement event: it should display and sort as negative. (Abreu, Simone (de Bretteville) is one example; you could look at reimbursement events in the admin to find others.)

OK, I checked Flecker and Pougaud and was able to sort them by amounts, both increasing and decreasing -- it's working great!
I first checked D.S.S. Mackenzie, who has 3 reimbursements and 2 renewals. The reimbursements show a negative number, which is correct, and I'm able to sort it in increasing (-100, -100, -50, 20, 180) and decreasing (180, 20, -50, -100, -100) amounts. I tested C. Barton, too, who has 1 reimbursement and 1 subscription amount. It's sorting well too!


test/counter: Fix test failures on AppVeyor due to rounding errors.

This patch fixes the test cases in test/counter/test_client.rb which are constantly
failing on AppVeyor right now. For examples:

https://ci.appveyor.com/project/fluent/fluentd/build/3009/job/linub6g6b83d4t3c
https://ci.appveyor.com/project/fluent/fluentd/build/3008/job/6ng3not4p900fxrc
https://ci.appveyor.com/project/fluent/fluentd/build/3007/job/gyxnqulia1eknc6q

Problem
Evidently, Timecop.travel induces flogting-point errors to Time.now on
Windows environment:
>>> Time.freeze(Time.parse('2016-09-22 16:59:59 +0900'))
>>> Timecop.travel(6)
>>> printf("#{Time.now.to_i}.#{Time.now.nsec}\n")
1474531204.999999999

... and this seems to be the cause of these test failures.
Solution
This patch fixes the issue by introducing a helper method travel() that
allows to travel back/forward without such errors.

Target tests are passed. Thanks!


Asset Locator: Coherence between maps: If an AssetLocator is not necessary, Unload it. If it was already loaded, remain as it is.

Move the references to AssetLocators currently in BaseMapLocator into a different place.
Then, the BaseMapLocator should only keep booleans to know if they should be Loaded or not.

AssetManager with all the references to AssetLocators. And maybe we can solve the dependency with DI.


panic: interface conversion: interface {} is float64, not string

Curious if anyone has some across this before. Have 2 separate partners who occasionally crash our system by encountering an error on their end and sending through the websocket pipe to ocpp-go
This causes ocpp-go to panic thus restarting our container. Below is a full Grafana snapshot of what occurs.

Really comes down to
parse message: [4<PHONE_NUMBER> 3 An internal server error has occurred. map[associatedException:map[ClassName:System.Exception Data:<nil> ExceptionMethod:<nil> HResult:-2.146233088e+09 HelpURL:<nil> InnerException:<nil> Message:An error has occurred, please see details. RemoteStackIndex:0 RemoteStackTraceString:<nil> Source:<nil> StackTraceString:<nil> WatsonBuckets:<nil>] occurenceDateTime:2023-02-23T16:43:41.3998122Z]]

Leading to:
2023-02-23 11:43:41 | dev.azure.com/atompower/cobblestone/_git/ocpp.git/ocppj.(*Endpoint).ParseMessage(0xc0032f4c00, {0xc00377a540, 0x5, 0x449e92}, {0xbac178, 0xc0030aa280}) |
-- | -- | --
  |   | 2023-02-23 11:43:41 | goroutine 1226 [running]: |
  |   | 2023-02-23 11:43:41 |   |
  |   | 2023-02-23 11:43:41 | panic: interface conversion: interface {} is float64, not string

Hey @sc-atompower and thanks for submitting the issue.
To make sure this isn't an issue in the library I would need a more detailed log message, which allows seeing the raw incoming message. To enable debug logs you can:
ocppj.SetLogger(log.WithField("logger", "ocppj"))
ws.SetLogger(log.WithField("logger", "websocket"))

The logger can be be anything, as long as it conforms to the interface specified in logging.go/Logger (which should be fine with logrus and zap at least, otherwise you'll need to write a tiny adapter).

I'll have more data shortly.

@lorenzodonini
I attached the logger to the ws client and set the log level to debug.
We received no new data to explain the crash.
{"level":"debug","ts":1681532159.2912889,"msg":"enqueued CALL [2114071548, StopTransaction]"}
{"level":"debug","ts":1681532159.2913153,"msg":"queuing data for server","logger":"websocket"}
{"level":"debug","ts":1681532159.2913272,"msg":"sending data","logger":"websocket"}
{"level":"debug","ts":1681532159.2914004,"msg":"written 222 bytes","logger":"websocket"}
{"level":"debug","ts":1681532159.3255785,"msg":"ping sent","logger":"websocket"}
{"level":"debug","ts":1681532159.4100168,"msg":"ping sent","logger":"websocket"}
{"level":"debug","ts":1681532159.412674,"msg":"pong received","logger":"websocket"}
{"level":"debug","ts":1681532159.4139264,"msg":"ping sent","logger":"websocket"}
{"level":"debug","ts":1681532159.493899,"msg":"pong received","logger":"websocket"}
{"level":"debug","ts":1681532159.497917,"msg":"pong received","logger":"websocket"}
{"level":"debug","ts":1681532159.5719092,"msg":"received 426 bytes","logger":"websocket"}
panic: interface conversion: interface {} is float64, not string

goroutine 290118 [running]:
github.com/lorenzodonini/ocpp-go/ocppj.(*Endpoint).ParseMessage(0xc0012ece00, {0xc00020b9e0, 0x5, 0xc0012de918}, {0xbb1498, 0xc00054f810})
	/go/pkg/mod/github.com/lorenzodonini/ocpp-go@v0.16.0/ocppj/ocppj.go:423 +0x10f3
github.com/lorenzodonini/ocpp-go/ocppj.(*Client).ocppMessageHandler(0xc0002b0780, {0xc0012ece00, 0x0, 0x0})
	/go/pkg/mod/github.com/lorenzodonini/ocpp-go@v0.16.0/ocppj/client.go:207 +0xfa
github.com/lorenzodonini/ocpp-go/ws.(*Client).readPump(0xc00051c9a0)
	/go/pkg/mod/github.com/lorenzodonini/ocpp-go@v0.16.0/ws/websocket.go:886 +0x1e2
created by github.com/lorenzodonini/ocpp-go/ws.(*Client).Start
	/go/pkg/mod/github.com/lorenzodonini/ocpp-go@v0.16.0/ws/websocket.go:1005 +0x705


libjack2: fix source url

Description of changes
c733f0bf8ad39186b9d14d4fb4d0bc1394b93940 switched JACK to using overlay-style
mkDerivation, but forgot to change a reference to version to finalAttrs.version.
This wasn't caught at eval time because with lib was used, making the
source derivation try to fetch (at the time of writing) tag "23.05pre-git",
which obviously doesn't exist :D
Thanks to V for catching this 0.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Not sure how I feel about mentioning the same issue twice in commits that come in sequence. I'd mention the commit hash instead, but I tend to not use those since I rebase and merge. 🤷♀

Thanks for removing with from most of the file. :heart:


Nginx worker process segfault when using SecAuditEngine

MODSEC-374: When having SecAuditEngine set to On or RelevantOnly, everytime a ModSec rule (I'm using OWASP CRS rules) matches, the nginx worker segfaults and does not write to SecAuditLog (I have SecAuditLogType set to Serial), the request is properly handled though and the ModSec debuglog shows the matched CRS rule.
Logfiles:
==> /var/log/nginx/error.log <==
2013/01/08 14:24:33 [info] 7558#0: [client <IP_ADDRESS>] ModSecurity: Warning. Pattern match "(?i:(?:union\s*?(?:all|distinct|[(!@]?)?\s?[([]?\s?select)|(?:\w+\s+like\s+["'\xc2\xb4\xe2\x80\x99\xe2\x80\x98])|(?:like\\s*?[\"'\xc2\xb4\xe2\x80\x99\xe2\x80\x98]\%)|(?:["'\xc2\xb4\xe2\x80\x99\xe2\x80\x98]\\s*?like\\W*?[\"'\xc2\xb4\xe2 ..." at ARGS:foo. [file "/etc/nginx/mod_security.rpx.real.jaggi.info.conf.d/activated_rules/modsecurity_crs_41_sql_injection_attacks.conf"] [line "223"] [id "981245"] [msg "Detects basic SQL authentication bypass attempts 2/3"] [data "Matched Data: select from found within ARGS:foo: select from"] [severity "CRITICAL"] [tag "OWASP_CRS/WEB_ATTACK/SQL_INJECTION"] [hostname "standalone"] [uri "/ip/?foo=select%20from"] [unique_id "12345"]
==> /var/log/nginx/rpx.real.jaggi.info-ip.access.log <==
<IP_ADDRESS> - - [08/Jan/2013:14:24:33 +0100]  "GET /ip/?foo=select%20from HTTP/1.1" 200 27 "-" "curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5" 0.038
==> /var/log/nginx/error.log <==
2013/01/08 14:24:33 [alert] 7554#0: worker process 7558 exited on signal 11
ModSec Debug Log:
[08/Jan/2013:14:24:33 +0100] [standalone/sid#19d3470][rid#22e8db0][/ip/?foo=select%20from][2] Warning. Pattern match "(?i:(?:union\s*?(?:all|distinct|[(!@]?)?\s?[([]?\s?select)|(?:\w+\s+like\s+["'\xc2\xb4\xe2\x80\x99\xe2\x80\x98])|(?:like\\s*?[\"'\xc2\xb4\xe2\x80\x99\xe2\x80\x98]\%)|(?:["'\xc2\xb4\xe2\x80\x99\xe2\x80\x98]\\s*?like\\W*?[\"'\xc2\xb4\xe2 ..." at ARGS:foo. [file "/etc/nginx/mod_security.rpx.real.jaggi.info.conf.d/activated_rules/modsecurity_crs_41_sql_injection_attacks.conf"] [line "223"] [id "981245"] [msg "Detects basic SQL authentication bypass attempts 2/3"] [data "Matched Data: select from found within ARGS:foo: select from"] [severity "CRITICAL"] [tag "OWASP_CRS/WEB_ATTACK/SQL_INJECTION"]

Also having this issue with nginx 1.7.11 with modsecurity 2.9.0.
Only thing that seems to work is disabeling ModSecurityEnabled, to completely disable mod security....
dmesg
[ 1263.527387] nginx[5982]: segfault at e0 ip<PHONE_NUMBER>466486 sp 00007fff53951bd0 error 4 in nginx[400000+181000]
[ 1263.567512] nginx[6199]: segfault at e0 ip<PHONE_NUMBER>466486 sp 00007fff53951b90 error 4 in nginx[400000+181000]
[ 1263.634073] nginx[6201]: segfault at e0 ip<PHONE_NUMBER>466486 sp 00007fff53951bd0 error 4 in nginx[400000+181000]
[ 1263.677549] nginx[6202]: segfault at e0 ip<PHONE_NUMBER>466486 sp 00007fff53951b90 error 4 in nginx[400000+181000]
[ 1263.768463] nginx[6205]: segfault at e0 ip<PHONE_NUMBER>466486 sp 00007fff53951bd0 error 4 in nginx[400000+181000]
[ 1263.802768] nginx[6211]: segfault at e0 ip<PHONE_NUMBER>466486 sp 00007fff53951b90 error 4 in nginx[400000+181000]
[ 1263.880352] nginx[6213]: segfault at e0 ip<PHONE_NUMBER>466486 sp 00007fff53951bd0 error 4 in nginx[400000+181000]
[ 1263.902990] nginx[6215]: segfault at e0 ip<PHONE_NUMBER>466486 sp 00007fff53951bd0 error 4 in nginx[400000+181000]

error.log
2015/04/06 19:31:28 [alert] 5921#0: worker process 5923 exited on signal 11
2015/04/06 19:31:28 [alert] 5921#0: worker process 5956 exited on signal 11
2015/04/06 19:31:28 [alert] 5921#0: worker process 5958 exited on signal 11
2015/04/06 19:31:28 [alert] 5921#0: worker process 5963 exited on signal 11
2015/04/06 19:31:28 [alert] 5921#0: worker process 5969 exited on signal 11
2015/04/06 19:31:28 [alert] 5921#0: worker process 5975 exited on signal 11
2015/04/06 19:31:29 [alert] 5921#0: worker process 5979 exited on signal 11
2015/04/06 19:31:29 [alert] 5921#0: worker process 5981 exited on signal 11

Hi @trojanc, please try the nginx_refactoring branch.
https://github.com/SpiderLabs/ModSecurity/tree/nginx_refactoring

Hi @zimmerle I gave that branch a go, but didn't help.
I'll put together a vagrant/ansible test setup on github in the next couple of days.
Any other info I can give in the meanwhile that might be useful?

I have the same problem with modsecurity_nginx_refactoring.
I try to configure modsecurity with concurrent log mode then it can write attack log to my audit log file, it ok.
But when I try to configure modsecurity with serial mode then it can not write log to file and error log message that is: worker process 6523 exited on signal 11.
I read this page: http://sourceforge.net/p/mod-security/mailman/message/30405571/, He said that problem is caused by permission of worker. But I grant root permission to worker in configure file, it seem to not OK.
Please help me @zimmerle  @rcbarnett

I use mods_nginx_refactoring + nginx 1.6.3

Hi @taibd we are working in a new version of ModSecurity for nginx. It is available here:
https://github.com/SpiderLabs/ModSecurity-nginx

It makes usage of libmodsecurity. It is not 100% workable with OWASP yet. In the meanwhile you can either restart your server or clean up the semaphores:
for i in `ipcs -s | grep $me | awk '{print $2}'`; do echo "Removing $i..."; ipcrm -s $i; done

(make sue to run this command with the same user of your worker)
It seems to me that your issue is related to the leak of semaphores.

Thanks @zimmerle,
we are deploying your project for many website systems (more than100 websites), so upgrading or updating version is so difficult.
Addition, I want to know how many bugs modsec_nginx have in now, I cannot control this.
My opinion that you can provide a function to update version manual or automatically instead of build sourcecode again.
Modsecurity + nginx is a good solution for waf and I think If it's more convenient, It can help many people.
go this bug again, I try to restart server but it is not OK.
I want to debug this bug but I i don't know how to do this. If i want to see deeply about modsec_nginx, example: debug, developing, testing,...how I can do that?

Hi @taibd, ModSecurity update depends on your distro. If you are running that number of server I recommend the creation of an internal repository, so that it will be easy to deploy new servers and configurations. Also, updates like that in ModSecurity will be easy to be performed, as you will just need to compile it once.
The nginx_refactoring branch is the most stable version (from the 2.x line). Depending on the configuration of your server, it may lead to crashes. There are merge requests, such as nginx_refactoring_def that may solve your specific issue. All the issues are documented here in github.


Add passphrase to ledger signing api

This addresses #168; Instead of having the passphrase for signing
hardcoded to "Ledger.Crypto PassPhrase", allow the passphrase to be
provided. This way we aren't prevented from using private keys
created with tools like cardano-address and cardano-cli

Any progress on this?

Tried to build from PR branch - and it fails
src/Cardano/Wallet/Mock/Handlers.hs:128:23: error:
• Couldn't match expected type ‘Eff effs MockWallet’
with actual type ‘BS.ByteString -> Eff effs0 MockWallet’
• Probable cause: ‘newWallet’ is applied to too few arguments

@silky @Yasuke sorry for urging you, but this issue is a blocker for other work, could we prioritize merging this once it builds?

Hi @gege251 ; sorry to hear it is blocking you. As you can see, we are working on it, and it will be merged in due course :)

Thank you for the feedback and review @silky! I have make Passphrase a distinct type, added prime functions that don't require a password, added some tests (and instances needed to make them work) for signing in both the ledger and oracle.

I also generalized the ledger signing function to work with any ByteArrayAccess instead of just TxIds

Pending CI, required adjustments have been made, thanks @sjoerdvisscher for the review

Rebased on current main

hello, when this PR are planned to be merged?

Thanks for the reminder!


Aspirational middleware scripts

I thought we ended up merging all of these ideas in separate PRs. @bhuga can you confirm?

I thought we ended up merging all of these ideas in separate PRs. @bhuga can you confirm?

Yeah, we discussed this and we decided that we wanted a lot of it to be in scripting.md instead of patterns.md. The actual auth example in this PR made it into patterns.md somehow or another. I think we can close this one out.


Language switcher: review design and behaviour

We don't like the tooltip, one idea could be a dropdown


sgx: make SGX NFD kustomization overlay independent

With the addition of SGX webhook in the operator, full SGX stack
depends on having the operator deployed first. SgxDevicePlugin CRD
is set to get intel-sgx-plugin and intel-sgx-initcontainer deployed
by the operator.
As a pre-requisite, node-feature-discovery must be deployed but it
is currently deployed via sgx_plugin kustomization overlay only.
It's better to allow NFD with the SGX specific settings deployed with
a kustomization of its own.
Signed-off-by: Mikko Ylinen<EMAIL_ADDRESS>

/cc @ipuustin


SwiftWebVC never loads some urls, Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service

Trying SwiftWebVC out for the first time and I'm having a problem loading certain pages. This is how I show it:
let webVC = SwiftWebVC(urlString: "http://www.udwa.org/our-union/")
webVC.delegate = self
self.navigationController?.pushViewController(webVC, animated: true)

The delegate call back tells me that it started loading, after 30 seconds I get the following in the console:

2017-10-14 11:57:05.941522-0700 udw[61741:29492827] Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service
2017-10-14 11:57:05.942308-0700 udw[61741:29492827] Could not signal service com.apple.WebKit.Networking: 113: Could not find specified service

I tried several other URLs:

https://www.google.com/ : worked, doesn't print the WebContent error above
https://github.com/meismyles/SwiftWebVC : worked, doesn't print the WebContent error above
http://www.inadaydevelopment.com : failed. This is my company's website, a WP site hosted in Google's cloud.
http://herdboss.com/ : failed. This is another company I'm part of, a drupal site hosted at Rackspace.
http://garyjohnston.com/ : failed. A friend's website, a WP site. Not sure where it's hosted, but it's a different server from 3 and 4 above.

I get the same behavior when using the SwiftModalWebVC.
Any help is appreciated.

Turns out that it was because my App Transport Security wasn't configured. So, not your bug.
However, if you potentially intercept the ios error that indicates and print something to the console that would be helpful. I discovered the problem by just trying to use the old UIWebView to see if those sites would load normally that way and that's when I got the error in the console that led me to the answer.


opt Make the case stable. (#44195) (#43203)

What problem does this PR solve?
pick from master (#44195) (#43203)
Problem Summary:
Release note
None
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall


Intall the package in Laravel 8

What if I want it to install in laravel version 8, is there any option I can do? thanks.

@DannJohnrem no sorry we support only Laravel 9


Tutorials still mention boosted_trees_classifier_train_in_memory

URL(s) with the issue:
https://github.com/tensorflow/docs/blob/master/site/en/tutorials/estimator/boosted_trees_model_understanding.ipynb
Description of issue (what needs changing):
The tutorials says

For performance reasons, when your data fits in memory, we recommend use the boosted_trees_classifier_train_in_memory function.

However, function boosted_trees_classifier_train_in_memory doesn't exist. It's actually removed in ffc25308ce2be84240ec90502b38800bc5a4dd60.
Submit a pull request?
I'm not sure whether it's fine to simply remove the sentense. You guys may want to add something else.

@gqqnbig I think that there is a new arg train_in_memoryat  https://www.tensorflow.org/api_docs/python/tf/estimator/BoostedTreesClassifier.
Can you send a small PR to refactor that sentence?

Closing this issue since the associated PR has merged and fixes it. Thanks!


ci: show globs, not files

:bulb: @stevendanna's idea. Hoping to strike a middleground between information overload and usefulness.

I've added a commit to this PR to also fix a small issue in which we weren't printing out things that were built only because one of their hab dependencies were also rebuilt.

@stevendanna my bad! thank you 🎊


add a wrapper for concept type and return THING if concept type is not set

[ ] joeferner
[ ] mwizeman joeybrk372 jharwig sfeng88

Points of Regression: graph check tool, diff panel
CHANGELOG
Changed: When a concept type is null, return thing

This scares me a little since it will mask errors of truly missing concept types. Can you explain in the commit message why we are doing this again so that future us will remember by looking at the commit logs.

@joeferner I added a more detailed description to the commit message to describe why we did this.


chore: release main

:robot: I have created a release beep boop
biblo: 0.12.0
0.12.0 (2023-01-13)
Features

New logo (28544df)

docs: 0.8.0
0.8.0 (2023-01-13)
Features

New logo (28544df)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/saxofonsolo/biblo/releases/tag/biblo-v0.12.0 :sunflower:

:robot: Release is at https://github.com/saxofonsolo/biblo/releases/tag/docs-v0.8.0 :sunflower:


Fetch OSM Points of Interest

Implemented functionalities to fetch points of interests from OpenStreetMap using osmnx that can be found from pois.py file. Tests were written in tests/test_osmnx.py. All functions include docstrings and are written following the same style as other osmnx functionalities.
The implemented functions in pois.py are:

def pois_from_place(place, amenities=None)
def pois_from_point(point, distance=None, amenities=None)
def pois_from_address(address, distance, amenities=None)
def pois_from_polygon(polygon, amenities=None)

amenities parameter allows to filter specific types of OSM amenities such as restaurant, school etc.

Coverage decreased (-0.3%) to 93.382% when pulling 2071cd7f943ce5891049cf325c314f3b65e2ad68 on HTenkanen:1-osm-poi-dev into a32ebebdb5a9e464f44b220fc244219f430c15b4 on gboeing:master.

resolves #116

I really need to read more of GitHub before diving into stuff. I've been doing something similar with osmosis for pre-filtering. This is a great feature

@gboeing Done now with the minor edits according your comments! 👍 Very happy to contribute, this is a great package! 🙂


PATCH: updated go.mod to go1.21

RHOAIENG-8649
What this PR does / why we need it:
Updated go version in go.mod to 1.21
Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):
Fixes #
Checklist:

[ ] Docs included if any changes are user facing

/retest


Update README.md for v0.2.0

@rs, here are some final updates to the REAME. If there are any more changes you want to the README.md  before the v0.2.0, please comment it in this review.
I have created some release drafts I am planning to release as soon as this PR is in if that's alright with you @rs. A release for rest-layer-mongo will follow, probably adding a go.mod as well.
@rs do you (or anyone else) have a setup to sanity check rest-layer-es and do a release there as well, preferably with the right go.mod deps?

Clears & Updates Breaking Changes section, including a link to release
notes for v0.2.0. Mainly the list is moved to Release Notes for v0.2
in particular, as the list is incomplete. For v0.3, we can consider to
keep the list in the READEME post release.
Moves HTTP Request Headers / HTTP Method methods section to right
above Querying.
Fix a few minor linting/spelling issues.

LGTM. I don’t have a setup in place to test the es module.

LGTM. I don’t have a setup in place to test the es module.

Me neither. We could perhaps document it as untested for now? I haven't heard of anyone actively using it or reporting issues.

Sounds good

E.g. something like this:
Main Storage Handlers

[x] MongoDB
[x] Memory (test only)

Alternate Storage Handlers

ElasticSearch (no longer tested)
SQL (third party)
Google Datastore (third party)
Kubernetes ConfigMap (third party)

I will need to do some more changes before this is worth re-approving.

@Dragomir-Ivanov, would you mind read over to see if the features you have contributed with are now documented correctly? E.g. in the Request Header section.

@smyrman Everything seems fine from my side.

Ok, this should be ready for review again @rs.
There was some duplicated documentation added as part of a rebase that have no been removed.
We have also got to run the exact code pointed to by this branch in our dev environment (with mongo-db) for some days to filter out any obvious issues; we haven't found any so far.
There are probably more cleanups that can and should be done to the README, but this can be done over time. At some point it might be good to actually split it up to improve maintenance. E.g. move some documentation to the package docs. However let's discuss this later.
Once this is merged, I hope we can tag the release.

@rs, do you have some time to have another look? Would be great to push out that release, (and start worrying about the next one).


add ability to not have a drift hamiltonian

Is your feature request related to a problem? Please describe.
Currently, if a problem doesn't have a drift Hamiltonian a matrix of zeros must be passed in its place.
Describe the solution you'd like
It would be nice to have a constructor method that omits the drift term.

Sparse quantum system matrices in version 0.2.0


feat: add file component

This PR adds support of File component.
UCC doc ref: https://splunk.github.io/addonfactory-ucc-generator/entity/components/#file

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


Added package.xml generator

The package.xml generator searches through folders within src and writes it to the package.xml. Currently, the following metadata-types are part of the generator:

ApexClass
ApexComponent
ApexPage
ApexTrigger
Community
CustomApplication
CustomLabel
CustomObject
CustomSite
CustomTab
Document
HomePageComponent
HomePageLayout
Layout
PermissionSet
Queue
RemoteSiteSetting
ReportType
Role
StaticResource
Workflow

See following blogpost for more information:
http://www.koenwesselman.com/automatic-package-xml-generation-salesforce/

Excellent contribution, can you also update the README to describe it further along with the other tools?

Sure! I'll look into doing so when I find some time.


Python 3.8 Literal shape

Ran into this issue using Python 3.8, not sure there is a solution though:
from phantom_tensors import parse
from phantom_tensors.numpy import NDArray
from typing import Literal, NewType
import numpy as np
X = NewType("X", int)
x = np.zeros((1, 2))
parse((x, NDArray[Literal[1], X]))
TypeError: Got shape-type (typing.Literal[1], <function NewType.<locals>.new_type at 0x7f60a5aab430>) with dim typing.Literal[1]. Valid dimensions are `type[int] | Unpack | TypeVar | NewType | Literal`

Hmm.. This seems to run just fine in Python 3.9. Probably a fiddly runtime detail for literals in earlier versions of Python. It is surprising, though, because I run CI vs older version of Python. Can you try using typing_extensions.Literal instead?
It looks like there are some CI failures that I need to get to for this project. Maybe I will unearth what is going on here when I do.


Unit and regression testing plan

This issue it outlines the steps necessary to incorporate the best practices of unit testing and regression testing into development of the OG-USA model. Below is a proposed outline of the sequential steps for updating OG-USA automatic testing.

Write code for pytest to test each function in the OG-USA model

This testing includes the  get_TPI() function.
We should measure and report code coverage.

Update Travis CI to run some subset of the pytest tests.

We'll want to keep the Travis CI testing under 15 minutes of run time.

Create regression tests that have standardized output.  See OG-USA Issue #232

Some of this output will need to be placed in the comments to any pull request and pass review before that PR can be merged.
Some of this output will need to be checked into the repo and to be compared against prior output.  See webapp-public Issue #539.
This step cannot be incorporated into Travis CI because the computation time takes too long for the equilibrium transition path.

@jdebacker @MattHJensen @hdoupe @PeterDSteinberg

A couple of notes on the procedure above:
Regarding 3):

We will view the a paste of the regression test results into the github PR discussion as a requirement before merging, inclusive also of discussion related to divergence of the results from standards, if any, but on a case by case basis we may agree that a PR can be merged without the regression test results (e.g a documentation PR)

One more point on procedure from the meeting:

When writing tests and new code in OG-USA, try to follow PEP8 for new code, then around October 1 or so, let's revisit the idea of automated PEP8 check in the Travis CI, perhaps with some exceptions like Tax-Calculator has specified in its setup.cfg

Near term TODO list for this issue:

[ ] Finish the discussion on @rickecon started above on procedures, and then write out in a README markdown at top level of repo the procedure for how to create the standardized regression test results, what to paste into an PR, and any notes about configuration/setup/install for running that regression test suite.
[ ] Make a script that runs the regression test(s) so it is a simple one-liner ideally to make the standard regression test results, e.g. source activate aei_dropq && python run_regression_test.py default_regression_reforms.json or similar command.  I think we already have something like that in here we can modify.
[ ] Update Travis CI configuration to do the following now (I'll (Peter) do this part):

[ ] Use conda build and conda install --use-local as shown in the example Earthio Travis build scripts here and here
[ ] Loop over Python 2.7, 3.5, 3.6 in the Travis build matrix setup, but for now set the Python 3.X builds to expected failures/skips.  Make a reminder in .travis.yml for when we do the Python 3 compatibility PR merges to uncomment/undo whatever setting is setting the Python 3.X builds to skip.

@jdebacker Can you assign this issue to yourself mainly to make the README on regression testing and ensure we have a simple command line tool for running the typical regression tests.  I'll open a PR later this week with the Travis CI changes of the "Near term TODO" list above - let me know if I'm holding anybody up.

Yes, @rickecon and I will spell out what the regression tests should contain and will put that in a README.

I'm looking at the tests that we currently have in the tests directory.  Are you all comfortable with the tests that are already there?  Do we need to scrap any and start over there?
There are two places where I'm interested in getting started here.

Break down the run_micro_macro function in test_run_ogusa.py into several functions so that the SS and TPI functionalities can be tested separately.  Then from there try to test functions on a lower level (ie SS_solver, SS_fsolve, SS_fsolve_reform, etc. ).

Begin doing unit tests on modules like household.py, firm.py, fiscal.py etc.

What do you all think?  I'm pretty new to all of this and open to all suggestions and advice.  Just point me in the right direction and I'll get to work.
@rickecon @PeterDSteinberg @PeterDSteinberg

@hdoupe let me outline what I understand and find useful in the current test infrastructure:
In test_basic.py:

test_run_small() is something that's been useful to be sure the model runs through without error.  This test uses a scaled down version of the model to improve run time.
test_get_micro_data_get_calculator() is helpful to be sure that the model plays well with the Tax-Calculator version that is used.  In particular, it checks that the format for the reform dictionary does  not cause an error.  This could probably be written more robustly to check not just the format of inputs, but also outputs.
I'm not sure about all the test of pickle files here, but we did have some cross-platform issues early on so they may be related to that.

In test_parameters.py:

Not sure what this is doing exactly.

In test_run_ogusa.py:

This runs the baseline and reform through to the computation of the final outputs (a table of percent differences between the baseline and reform policies for macro aggregates and prices).
Like test_basic.test_run_small() this uses a scaled down version of the model and pre-estimated tax function parameters (i.e., run_micro=False).  Both these things improve run time.

In test_sstpi.py:

Not sure what this does. Looks like it runs some version of the full model though.

I'm no expert on testing, but am happy to answer any questions about the model and offer suggestions on how to improve the speed of tests (either by scaling down the size of the state space or choosing parameterizations and starting values that will yield quick convergence).
I generally like your idea of where to get started.  I'm not sure your preference, but my thought was that starting with the smaller functions and working out might be a good way to go because they are easier bites swallow and will help you understand things before moving up to the larger fruntions like SS_fsolve and get_TPI.

@jdebacker Thanks, that's very helpful.  I'll get started on the smaller, less complex modules.

I'm going to close this broad issue.  We now have 100+ unit tests and a decent regression testing harness.  We can use some more code coverage with the unit tests and we might be able to streamline the regression testing a bit, but we can discuss particulars in new issues.


Update README.md

PR Description 📜
This PR addresses issue, which involves improving the user experience and presentation of the Color_Crush_Game project by replacing the link to the link with an image. The steps taken include capturing a new screenshot of the game, adding it to the repository, and updating the README.md file to display this image directly.
Fixes #3825

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[ ] I have added entries for my game in main README.md
[ ] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸
BEFORE CHANGES :

AFTER CHANGES :

@kunjgit Thank you !

Thank you soo much for contributing to our repository 💗

Thank you @Bindusree1515 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @Bindusree1515 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Submission2311080_2311906_2311124 (Group 142)

BRIEF DESCRIPTION
1.  Team members:

Name
ID
Task Distributions
Completed Percentage

Trần Nguyễn Kim Hoàng
2311080
GA - LaTeX - Case Study
100%

Nguyễn Hoàng Long
2311906
GA  - LaTeX - Evaluation
100%

Bùi Quang Huy
2311124
BSSF - LaTeX - Modeling
100%

2. Genetic Algorithm Introduce:
Approach:
The Genetic Algorithm (GA) is a fascinating approach inspired by the principles of natural evolution. What makes it particularly compelling is its emphasis on diversity and randomness during the search for solutions.
Implement Steps:
-  Step 1: Initialize the Population:

Randomly generate an initial population of potential solutions (chromosomes). Each solution represents a possible answer to the problem.

- Step 2: Evaluate Fitness:

Assess the fitness of each solution in the population based on a predefined fitness function that measures the quality of the solution.

- Step 3: Selection:

Select the best-performing solutions (parents) based on their fitness scores. In our implement, we used tournament selection to ensure the  diversity of populations.

- Step 4: Crossover (Recombination):

Combine pairs of parent solutions to produce offspring. This step ensures genetic diversity by mixing characteristics of the parents.

- Step 5: Mutation:

Introduce small random changes  in the offspring to maintain diversity and explore new areas of the solution space. We use two approach are moving products slightly and rotating product, both in random.

- Step 6: Replacement:

Form a new population by replacing the least fit solutions with the newly generated offspring.

- Step 7: Repeat:

Repeat the process of evaluation, selection, crossover, and mutation for multiple generations until a stopping criterion is met (e.g., maximum number of generations or convergence to a satisfactory solution).

- Output:

Return the best solution found during the optimization process.

Animation for GA

3. Best Sort Side Fit Algorithm Introduce:
Approach:
The Best Short Side Fit (BSSF) algorithm is a deterministic approach used for solving packing and layout problems, focusing on minimizing wasted space. Its central idea is to place items by comparing the shorter side of each stock with the dimensions of the item to be placed
Implement Steps:

Initialize Stocks:

Begin with a set of available stock areas (e.g., rectangles) where items can be placed.

Sort Items:

Sort all items to be placed by size (e.g., in descending order of width or height) or priority if needed.

Select an Item:

Pick the next item to be placed from the sorted list.

Find Best Stock Placement:

For the current item:

Compare the dimensions of the item (e.g., width and height) with the available stocks' short sides.
Choose the stock where the item fits best with the least amount of wasted space.
(If multiple stocks qualify, additional rules like minimizing the remaining height or width can break ties.)

Place the Item:

Place the item into the selected stock and update the stock’s available space. Split the remaining space into smaller regions if necessary.

Repeat for All Items:

Continue steps 3–5 until all items are placed or no suitable stock is left.

Handle Unplaced Items (if needed):

If some items cannot fit into any stock, either:

Add new stock(s) and repeat the process.
Mark the items as unplaced.

Animation for BSSF

4. Evaluation:

Algorithm
Fill Ratio
Trim Loss
Execute time(s)
Seed

Greedy
0.23
0.450762848
13.86
42

Random
0.44
0.686124382
10.41
42

BestShortSideFit
0.19
0.360690994
12.64
42

GeneticAlgorithm
0.19
0.294859866
27.56
42

Thank you for taking the time to review this work.  Your feedback is greatly appreciated! 😄

Please revise the PR in Dec 16. Otherwise, your group will get 0 score for code.

Please revise the PR in Dec 16. Otherwise, your group will get 0 score for code.

Dear Teachers,
I’m not sure what specific issues are preventing the PR from being merged. Could you kindly clarify so we can address them before the deadline?
Thank you!

Dear Teacher,
Thanks for your reply.
On Tue, 17 Dec 2024 at 20:11 Duc Quang Nguyen @.***>
wrote:

Merged #234 https://github.com/martinakaduc/MM241-Assignment/pull/234
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/martinakaduc/MM241-Assignment/pull/234#event-15685898166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHAH3G6ZS7RVHWGUX5TGWNL2GAPJXAVCNFSM6AAAAABTUNDUPCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGY4DKOBZHAYTMNQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***
.com>


Memory Allocation in Operating Systems in Java

🚀 Feature
[DWOC Contribution]
Memory Allocation in Operating Systems

First-Fit Memory Allocation
Best-Fit Memory Allocation
Worst-Fit Memory Allocation

Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
The operating system must keep a list of each memory location noting which are free and which are busy. Then as new jobs come into the system, the free partitions must be allocated.
These partitions may be allocated by 3 ways:
best fit: smallest hole (contiguous space) the segment can fit in
first fit: first hole (contiguous space) the segment can fit in
worst fit: largest hole (contiguous space) the segment can fit in
Pitch
(Please explain why this feature should be implemented and how it would be used.)
Can you please label this issue as DWOC?
Also please add the level.

Please assign me this issue and add the level of the PR for DWOC.

Please assign me this issue and add the level of the PR for DWOC.

Can you assign


react-native-paper

Error: Unable to resolve module react-native-paper
It seems overkill to pull react-native-paper library to have custom dropdown component?

Yes, I agree.
But I created this dropdown extension for react-native-paper. Also, some of the react-native-paper components are reused in this like chips and icons.
Maybe I should mention clearly this components extension for react-native-paper.

Yes, I agree.
But I created this dropdown extension for react-native-paper. Also, some of the react-native-paper components are reused in this like chips and icons.
Maybe I should mention clearly this components extension for react-native-paper.

Since this component developed using most of the react-native-paper components making it clear in the readme file that this component is an extension for the react-native-paper

Since this component developed using most of the react-native-paper components making it clear in the readme file that this component is an extension for the react-native-paper


Using Get-WinEvent with Hashtable instead of Get-Eventlog increases performance

https://github.com/microsoft/CSS-Exchange/blob/2fce81069fc0686a00eb5fa6accb280ccce2ebe7/Security/Test-Hafnium.ps1#L45
I replaced line 45 where the eventlog is searched using CMDlet "Get-Eventlog" with CMDlet "Get-WinEvent" using FilterableHashtable as follows:
$eventLogs = Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='MSExchange Unified Messaging'; Level='2'} | Where-Object { $_.Message -like "*System.InvalidCastException*"}
This speeds up the query approx by  factor 10 on my systems. Eventlog search now only takes about 3 minutes per system instead of 30 minutes

Looks like it throws an error when the event log is clean, so we will need to handle that gracefully.
PS C:\>  Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='MSExchange Unified Messaging'; Level='2'} | Where-Object { $_.Message -like "*System.InvalidCastException*"}
Get-WinEvent : No events were found that match the specified selection criteria.
At line:1 char:2
+  Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName= ...
+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (:) [Get-WinEvent], Exception
    + FullyQualifiedErrorId : NoMatchingEventsFound,Microsoft.PowerShell.Commands.GetWinEventCommand

That is true, but I experience the same when the eventlog is clean using the Get-Eventlog CMDlet

Ah you're right, we just need to tack on the SilentlyContinue like the other command had.

Thank you!

Right, forgot to take parameter "-ErrorAction SilentlyContinue" into my command


REMOVE THE CONTENT, JUST KEEP THE COMMENTS

https://github.com/UoA-eResearch/ResBaz24Python/blob/8a50006e601dd9d716b446a7607674329628b5fc/ResBaz_Intro_to_Python.ipynb#L1

one of the last steps (once the dev is ready) will be to copy-paste-strip a lot of code; just leaving a skeleton structure that will then be populated within the session

this is referred to as the 'skeleton structure' to be used in the live coding session. main has a Start_here... file where solutions to live-demos are removed from


Registering Next Version

@CheukHinHoJerry and @wcwitt  --  I'd like you feedback on the following question please:
I now have ACEpotentials v0.8-dev mostly compatible with ACE1. This is purely to confirm that it has ACE1 as a subset of its capabilities. I would now like to remove JuLIP, ACE1, ACE1x entirely from the repository and keep the compatibility only as part of the test suite.
I see two options:

register the current version as 0.8.0, then remove ACE1, ACE1x, and register this as 0.9.0.
remove ACE1, ACE1x immediately and then register as 0.8.0

I tend towards the second option as I don't really see much value keeping both implementations running in parallel now that we know they are essentially compatible. But I wanted to get 1-2 additional opinions before I proceed.

Given that we keep compatibility tests I agree that the second option is better.

I don't think we have the energy or manpower to worry about these things too much. So do whatever seems simplest to you.
On the other hand, in addition to the compatibility tests it would be nice to ensure we can reproduce the error tables from the ACEpotentials paper.

Yes that's a good point. In fact I would be grateful for an extended test suite.


There may be some bugs in the current version of the code

Thank you for dual-radar daraset contribution.
The following are the possible bugs that I have found through debugging. I hope the author can follow and reply. I hope the author can follow and reply. If I am not mistaken, you can update them:
@liulin813 @WangYichen222
1.Dual radar data laser coordinate system with y-axis as the front and kitti coordinate system with x-axis as the front:
When converting the label to gt'box_lidar, use kitti's conversion function directly - groundtruth with a 90 ° difference
2. When converting pred-box to the camera system to obtain the rotation angle, use kitti's conversion function directly - the rotation angle differs by 90 °
3. During data augmentation, the x-axis flipping was still used, causing the original up and down mirror image of the point cloud to change to the left and right flipping, which was then removed out of range - the training point cloud was heavily cut off
4. There may be about ten nan files in the point cloud, so I will delete them first (I think the impact should not be significant)

There are lots of gt_boxes with no radar point cloud (negative examples), which can cause bad training results.


Improve UX via text improvements

The change
Done as per discussion in the issues linked below.
Closes #58.
Closes #59.
🔥
Output from local test
===> Looking for dependencies to update in rebar.config...
===> gun (profile default) can be updated from 2.0.0-rc1 to 2.0.1
===> After applying the changes listed above, don't forget to run rebar3 upgrade [-a] [<package>]

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

From my perspective, these changes doesn't justify a new release just yet, but… do you need one, @paulo-ferraz-oliveira? If so, I can create one.

I don't need a new release, but thanks for asking.


schildichat: use electron 25

Description of changes
Electron 24 is now EOL and refuses to build.
Bumping the electron version functions properly and lets it build.
In my testing, it works just fine.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

nitpick: the commit message should look like schildichat-desktop: .... to match the attribute name.


deprecated constants prevent the integration from loading in new Home Assistant for RPI5

I'm using the integration (0.10.0) with my RCT solar power system, with Home Assistant on Raspberry PI 3B
@weltenwort It has been working perfectly for me for months now, tremendous piece of work, thank you very much!
We are currently beta testing the next Home Assistant release to enable the jump onto the Raspberry PI 5 platform
Currently running RPI5 HA with
Core 2024.1.0b2
Supervisor 2023.12.1
Operating System 11.3.rc1
Frontend 20231228.0
On HA startup the integration fails to load, with these warnings in the protocol:
POWER_VOLT_AMPERE was used from rct_power, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfApparentPower.VOLT_AMPERE instead, please create a bug report

POWER_WATT was used from rct_power, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead, please create a bug report

TEMP_CELSIUS was used from rct_power, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please create a bug report

TEMP_FAHRENHEIT was used from rct_power, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.FAHRENHEIT instead, please create a bug report

TEMP_KELVIN was used from rct_power, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.KELVIN instead, please create a bug report

Do you think that this can be adjusted, to ensure compatibility with the new HA for RPI5?
You also might want to take a look at the HA developer discussion: https://github.com/home-assistant/operating-system/discussions/2844#discussioncomment-7976705

Thanks for reporting this! I just released https://github.com/weltenwort/home-assistant-rct-power-integration/releases/tag/v0.11.0, which should remove these deprecation warnings.


BotFrameworkAdapter.createConversation fails to handle group conversation requests

Versions
What package version of the SDK are you using: 4.6 (master)
What nodejs version are you using: v10.16.0
What browser version are you using: n/a
What os are you using: Windows 10.
Describe the bug
According to the Bot Connector protocol, create conversation allows the bot to request that a channel create a group conversation. However, the BotFrameworkAdapter.createConversation implementation seems to limit requests to direct, one-on-one conversations.

Also, this diverges with the .NET implementation, which does allow the bot to request a group conversation.

To Reproduce
Steps to reproduce the behavior:

Read the code inside BotFrameworkAdapter.createConversation:
https://github.com/microsoft/botbuilder-js/blob/8bd254a4dbb3e94937a7b8d748f7365c70f44574/libraries/botbuilder/src/botFrameworkAdapter.ts#L265-L287
Error: note that on line 276 this is always assumed to be a direct conversation, whether or not the initial value of the reference property indicates this should be a group conversation.

Expected behavior

The protocol supports the creation of group conversations, the method signature does not prohibit the creation of group conversations, the implementation should allow the creation of group conversations.
The implementation should match/support the functionality of the underlying protocol here.
I think the behavior of this method could be corrected without introducing a breaking change.

Additional context
Add any other context about the problem here.
Here's commentary from Dan, taken from an email thread:

If the channel “agrees” to create the conversation, the ResourceResponse returned contains an id containing the ID of the conversation the channel created.

[Dan] Correct, and the concepts you’re describing are correct

Q: If the conversation is created, is the channel expected to send conversationUpdate activities?

[Dan] Typically, but not necessarily in all cases, depending on what is most appropriate for the channel and what is possible.
For example, creating a conversation in SMS yields a successful conversation ID (think of it as an idempotent create request) and it does not create a conversationUpdate because SMS conversations do not really have a beginning nor an end.
Channels that can send conversation on create typically do.

The bot can try to create a group conversation, but this isn’t supported by most channels.

[Dan] Correct

Q: If the CreateConversation request payload includes an activity, who is the intended recipient of that activity, that is, should the channel send that to the bot when the conversation is created, or to the non-bot members of the conversation?

[Dan] Activities sent to channels do not have an intended recipient. The bot includes the Activity in the request and the channel handles the work of enumerating the recipients and changing the Activity for them. Typically bot participants do not receive any Activities they originated. Bots may or may not receive Activities originated by other bots depending on the channel.

Presumably, the channel will update the activity’s conversation property (and any other conversation-specific fields) before sending the activity.

[Dan] Yes – the correct way to think about this is that the Activity that a bot sends to a channel is merely a request to send content. The channel receives it and, if it accepts the request, stores or records the content as part of the conversation. Then, as a subsequent operation, the channel creates new Activities that reflect that the message/content was accepted into the conversation. These Activities are the ones that are sent to users/other bots/etc.
In many cases these two Activities (the one the bot sent and the one the client receives) appear or act as if they are the same Activity, possibly with some fields changed. However the channel is not bound to that concept, and a more correct interpretation is that these two Activities are different, but closely related.!

[bug]

Any thoughts on this? This should get fixed sooner rather than later.

Hey @Kaiqb,
I just ran across this issue. I don't know who it should belong to, but can you route it to the right person?

@JonathanFingold - is this still an issue in 4.8?

@Kaiqb - yes, here's what's in master now. the inner isGroup parameter is still hard-coded to false.
I'm not sure why this hasn't created problems with the Teams channel.
        const response = await client.conversations.createConversation(parameters);

        // Initialize request and copy over new conversation ID and updated serviceUrl.
        const request: Partial<Activity> = TurnContext.applyConversationReference(
            { type: 'event', name: 'createConversation' },
            reference,
            true
        );

        const conversation: ConversationAccount = {
            id: response.id,
            isGroup: false,
            conversationType: null,
            tenantId: reference.conversation.tenantId,
            name: null,
        };
        request.conversation = conversation;
        request.channelData = parameters.channelData;

        if (response.serviceUrl) { request.serviceUrl = response.serviceUrl; }

        // Create context and run middleware
        const context: TurnContext = this.createContext(request);
        await this.runMiddleware(context, logic as any);

Here's an updated code link, as the file was edited (but the bug still remains)
https://github.com/microsoft/botbuilder-js/blob/c39c7744eaf1bc82e897789202420659a03c460f/libraries/botbuilder/src/botFrameworkAdapter.ts#L369-L392

We added support for passing Partial<ConversationParameters> in the createConversation parameter list. See the code on main here. This should resolve the issue, feel free to reopen this issue if that is not the case.

Perhaps I'm not reading this correctly, and please correct me if I'm wrong, but at line 511 isGroup is hard coded to false on the conversation account, then that account is added to request and sent out without further modification. Won't this always result in a non-group conversation?
https://github.com/microsoft/botbuilder-js/blob/3b772bbb59ce3b5bd328b890696a17a92b8194e6/libraries/botbuilder/src/botFrameworkAdapter.ts#L509-L525

Good point, I'll have a PR shortly.

@JonathanFingold okay, it should be resolved now on main. That code will be published in a daily build tomorrow.


Cannot perform helm init

Output of helm version: 2.11.0
Output of kubectl version: 1.12.1
Cloud Provider/Platform (AKS, GKE, Minikube etc.):  bare metal
$ ./helm init
Creating /home/xxxxxxxx/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Adding local repo with URL: http://<IP_ADDRESS>:8879/charts
$HELM_HOME has been configured at /home/xxxxxxxx/.helm.
Error: error installing: Post https://10.xxx.xx.xx:6443/apis/extensions/v1beta1/namespaces/kube-system/deployments: Forbidden

Looks like an issue with your cluster. What is the status of your nodes: kubectl get nodes?

ping

Thanks for the support every. Good call from hickeyma.
I am behind the proxy, so i was missing the "no_proxy" env setting....

I had the same issue, but running following command resolved it:
on master node:
export no_proxy=$(hostname -i)
then
helm init ..........................


chore: Code refactoring in the collections

Describe your changes
We can leverage some of the new JS/TS functionality to refactor the internal code of the collection library.
The main change is using async/await instead of promises. This is a lot easier to read.
I've also used Optional Chaining instead of checking for undefined.
iteratorResult?.value; // Will return undefined if value doesn't exist otherwise value

How best to test these changes
All the existing tests should pass
Issue ticket number and link
None

Codecov Report
Base: 90.54% // Head: 90.58% // Increases project coverage by +0.03% :tada:

Coverage data is based on head (a2b9ece) compared to base (83d2d4a).
Patch coverage: 81.81% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #201      +/-   ##
==========================================
+ Coverage   90.54%   90.58%   +0.03%
==========================================
  Files          24       24
  Lines        4189     4174      -15
  Branches      505      501       -4
==========================================
- Hits         3793     3781      -12
+ Misses        389      386       -3
  Partials        7        7

Impacted Files
Coverage Δ

src/collection.ts
97.47% <81.81%> (+0.35%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Hardware resources for large scale

Hello!
Sorry this is not really an issue but would be interested in knowing if this would work on a large scale and what kind of hardware we would be looking at in order to make it feasible .
Let's assume a rate of 500 images every 3 seconds or so, can it be done and with what kind of server specs if this is the case ?
Thanks in advance, great project !

Please read the large scale face recognition section in the read me. It might satisfy your requirements.

Hello !
Thanks for the fast reply :)
I did read that section and watched the video about elasticsearch but couldn't find anything that mentioned the benchmarks / server requirements , which is why I posted this question . From what I understand it's definitely possible but was hoping you could give me an idea of what kind of hardware would be needed to support 500 images every 2 or 3 seconds, or lets say 10000 images per minute .

elasticsearch can handle it with a limited hardware. do not think the hardware limit.

elasticsearch can handle it with a limited hardware. do not think the hardware limit.

Thanks for clarifying that ! Does this also apply for gender, age and race estimation calculations?
I do not plan to run face recognition but I am interesting in determining gender and age .

Also I should have mentioned that I was planning to run this on a headless server without GPU , would it be feasible to process this many images with analyze ?

running on gpu is totally fine.
Age and gender are easier tasks.

running on gpu is totally fine.
Age and gender are easier tasks.

"Also I should have mentioned that I was planning to run this on a headless server without GPU"
Without Gpu in this case , therefore my concern :)
I am deciding whether to base a project on this repo so evaluating the feasability of working with certain resources is really important for me before deciding to proceed with testings, which always takes a lot of time on its own .
I appreciate your patiente , I will try to be more specific to avoid losing your time . If I ran this on a dedicated server WITHOUT gpu , let's say an E3-1245 with 32gb RAM and I deployed elasticsearch would that be able to handle verification (age and gender) of about 10000 images per minute ?
Thanks again!

Elasticsearch can definetely handle it without GPU. If you watched the elasticsearch video, that would help you understand how it works.

Elasticsearch can definetely handle it without GPU. If you watched the elasticsearch video, that would help you understand how it works.

I did, I just wasn't aware if the verify age and gender functions also worked the same way face verification does
Great , tyvm and keep up the great work :) 👍

thank you for your adoption. please do not forget to star the repo.


BUG: Cannot see dotfiles

Thanks to Vinadon#0410: it is currently impossible to edit dotfiles.
Expected: typing gitignore in the extensions field shows the .gitignore file that is present.
Actual: The file is not shown.

Usually that could be a little tricky depending on how you read your directory, since these files don't have a main file name, just the extension, so to speak.
I've not looked at your code, but adding support for dotfiles, usually means some conceptual changes, as you would need to allow specific file patterns to be scanned for. One way of handling this would be to add a specific option in your settings which would trigger a flag, so that when you're scanning the directories you also scan for those starting with a leading dot, and allow that into the file name pattern otherwise used.
Some care need to be taken related to directories vs files, which I'm assuming you're already handling somehow, and some care need to be taken since dotfiles usually are text files, but they could really be binary files as well, so you do not want to open them with any kind of auto-save enabled, as that might risk destroying the file entirely.


Add documentation using spinhx, readthedocs

Documentation that should be added:

working with configuration
creating basic plugin
commiting and PRs
lifetime explanation
permissions explanation and list

Also everything in BaseLib, BaseLib.Implementations and CommandsLib should be documented in code.


Fix recursvie let terms in the term parser

There was a problem in the term parser for recursive let parsing. A let clause inside a let clause is allowed in the SMT standard, but was not supported by the term parser. The proposed bug fixes enhances the term parser regarding parsing of recursive let definitions.

Thanks for the PR. Looks good. I added some comments I think we should address before merging. Can you comment/fix?

I refactored the code according to your comment. Please have a look on the update.

Looks good to me! Thanks for contributing! :)


request

DearDavid，
I'm studing at Jilin University in China and Majored in Face Recognition. Could  you please tell me which paper this code is based on? And may I have the model that has trained already?  It would be so great of you. Thanks a lot.

This repo is not based on one particular paper, but is related to a number of them.
If you specifically want to read a paper, I suggest reading https://arxiv.org/abs/1609.04802 which does reference this repo as their method is somewhat similar to this.
Sorry I can't provide you with a trained model. I no longer maintain this repo.


chore(package): update faker to version 4.1.0

https://greenkeeper.io/

Storybook Hub is building storybooks for every commit in this PR.
Latest Storybook: https://10eb0b94-9966-4f7e-b716-7c7ccff5d5f4.sbook.io/
( Visit here for more info )

This comment is automatically added by Storybook Hub


[fastlane_core] add clearer error message when incorrectly defining tests that need xcodebuild

Checklist

[ ] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

This is to prevent issues like: https://circleci.com/gh/fastlane/fastlane/36544

Description

Testing Steps

But, I now noticed that we have tests running on macOS with Xcode installed, so, why this parameter?

          1 Warning

:warning:
Pull Request is Work in Progress

  Generated by :no_entry_sign: Danger

Hmm, I didn't pay much attention to the OS, and maybe I incorrectly thought that they failed on macOS.

The GH run you linked to was Ubuntu, so it would make sense.
Did I understand correctly that you added additional tests, and did not set requires_xcodebuild thus giving you this error message? Then you changes may be useful after all - although in theory this would have to be output at all locations where we use Xcode/xcodebuild. Not optimal.
Btw: I think require_xcode and require_xcodebuild might be different things, you have to check the codebase.

The GH run you linked to was Ubuntu, so it would make sense.

Exactly. So https://github.com/fastlane/fastlane/pull/15475#issuecomment-541015559 came out of confusion, so it should be ignored.

Did I understand correctly that you added additional tests, and did not set requires_xcodebuild thus giving you this error message?

Yes, and it took me quite a while to figure it out. Hence, this change.

although in theory this would have to be output at all locations where we use Xcode/xcodebuild. Not optimal.

What do you mean by this? If x tests that indirectly use xcodebuild, don't specify that parameter, the error message that I added will be output x times.

Btw: I think require_xcode and require_xcodebuild might be different things, you have to check the codebase.

Meaning that the PR title is a bit misleading? (I updated it now ⬆)

What do you mean by this? If x tests that indirectly use xcodebuild, don't specify that parameter, the error message that I added will be output x times.

Only if this exact code is executed. There are x other locations that also use xcodebuild or Xcode and which do not output this error message.

I don't think that this is needed anymore, hence, closing it.


Fix timeouts caused by infrequently used Meters

TY for the review! Pushed an update fixing the once a day ticking. It was also making the tests fail so that's a big help.


Documentation bug: dgl_csr_neighbor_non_uniform_sample doesn't have parameter seed_arrays

Description
In the documentation of these 8 APIs listed below, there is a parameter seed_arrays listed in Parameter section. But it is not in the signature and not accepted by the functions, and passing them gives abort, which crashes the program.

mxnet.contrib.ndarray.dgl_csr_neighbor_non_uniform_sample: https://mxnet.apache.org/versions/1.6/api/python/docs/api/contrib/ndarray/index.html#mxnet.contrib.ndarray.dgl_csr_neighbor_non_uniform_sample
mxnet.contrib.ndarray.dgl_csr_neighbor_uniform_sample: https://mxnet.apache.org/versions/1.6/api/python/docs/api/contrib/ndarray/index.html#mxnet.contrib.ndarray.dgl_csr_neighbor_uniform_sample
mxnet.contrib.symbol.dgl_csr_neighbor_non_uniform_sample: https://mxnet.apache.org/versions/1.6/api/python/docs/api/contrib/symbol/index.html#mxnet.contrib.symbol.dgl_csr_neighbor_non_uniform_sample
mxnet.contrib.symbol.dgl_csr_neighbor_uniform_sample: https://mxnet.apache.org/versions/1.6/api/python/docs/api/contrib/symbol/index.html#mxnet.contrib.symbol.dgl_csr_neighbor_uniform_sample
mxnet.ndarray.contrib.dgl_csr_neighbor_non_uniform_sample: https://mxnet.apache.org/versions/1.6/api/python/docs/api/ndarray/contrib/index.html#mxnet.ndarray.contrib.dgl_csr_neighbor_non_uniform_sample
mxnet.ndarray.contrib.dgl_csr_neighbor_uniform_sample: https://mxnet.apache.org/versions/1.6/api/python/docs/api/ndarray/contrib/index.html#mxnet.ndarray.contrib.dgl_csr_neighbor_uniform_sample
mxnet.symbol.contrib.dgl_csr_neighbor_non_uniform_sample: https://mxnet.apache.org/versions/1.6/api/python/docs/api/symbol/contrib/index.html#mxnet.symbol.contrib.dgl_csr_neighbor_non_uniform_sample
mxnet.symbol.contrib.dgl_csr_neighbor_uniform_sample: https://mxnet.apache.org/versions/1.6/api/python/docs/api/symbol/contrib/index.html#mxnet.symbol.contrib.dgl_csr_neighbor_uniform_sample

Error Message
(Paste the complete error message. Please also include stack trace by setting environment variable DMLC_LOG_STACK_TRACE_DEPTH=10 before running your script.)
terminate called after throwing an instance of 'dmlc::ParamError'
  what():  Cannot find argument 'seed_arrays', Possible Arguments:
----------------
num_args : int, required
    Number of input NDArray.
num_hops : long, optional, default=1
    Number of hops.
num_neighbor : long, optional, default=2
    Number of neighbor.
max_num_vertices : long, optional, default=100
    Max number of vertices.
, in operator _contrib_dgl_csr_neighbor_non_uniform_sample(name="", max_num_vertices="5", num_hops="1", num_args="3", num_neighbor="2", seed_arrays="
[0 1 2 3 4]
<NDArray 5 @cpu(0)>", probability="
[0.9 0.8 0.2 0.4 0.1]
<NDArray 5 @cpu(0)>", csr_matrix="
<CSRNDArray 5x5 @cpu(0)>")
Aborted (core dumped)

To Reproduce
(If you developed your own code, please provide a short script that reproduces the error. For existing examples, please provide link.)
This is the exact example provided in the documentation.
import mxnet as mx
import numpy as np
shape = (5, 5)
prob = mx.nd.array([0.9, 0.8, 0.2, 0.4, 0.1], dtype=np.float32)
data_np = np.array([1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20], dtype=np.int64)
indices_np = np.array([1,2,3,4,0,2,3,4,0,1,3,4,0,1,2,4,0,1,2,3], dtype=np.int64)
indptr_np = np.array([0,4,8,12,16,20], dtype=np.int64)
a = mx.nd.sparse.csr_matrix((data_np, indices_np, indptr_np), shape=shape)
seed = mx.nd.array([0,1,2,3,4], dtype=np.int64)
out = mx.nd.contrib.dgl_csr_neighbor_non_uniform_sample(csr_matrix=a, probability=prob, seed_arrays=seed, num_args=3, num_hops=1, num_neighbor=2, max_num_vertices=5)

The same error when calling the rest 7 APIs.
Environment
We recommend using our script for collecting the diagnositc information. Run the following command and paste the outputs below:
curl --retry 10 -s https://raw.githubusercontent.com/dmlc/gluon-nlp/master/tools/diagnose.py | python

# paste outputs here

OS: ubuntu 18.04
Python: 3.7.6
pip: 20.0.2
numpy: 1.18.5
mxnet: 1.6.0

cc @lingfanyu

cc'ed @zheng-da here. All these APIs should have been supported in DGL. We could have a discussion on whether to continue support them in MXNet or deprecate them.

@jermainewang it's ok to deprecate them in 2.0. for 1.x since it's already in the code base, we will need to fix the doc.

I found this issue on ovio.org and would love to contribute! I've never contributed before.

@hadevin thanks for offering to help. The contribution guide for our project can be found at: https://mxnet.apache.org/versions/master/community#contribution-guides
For this issue, I think we need to add a note on the documentation that the expected number of arrays for seed_arrays is the num_args minus two (csr matrix and probability).
The operators with documentation problems are in https://github.com/apache/incubator-mxnet/blob/v1.x/src/operator/contrib/dgl_graph.cc. For example:
https://github.com/apache/incubator-mxnet/blob/787416b23a1d5730fce995a6b662a51cee45e20f/src/operator/contrib/dgl_graph.cc#L866-L935
Feel free to ask here if you have any question.


Strange bug with transparency and window not using gnome styling

I was wondering if this is an issue on my machine, and if so how would I go about fixing it?

Switching to Xorg did fix the issue, good to know. Thanks guys!


Create a Release

I was wondering if you guys could publish a release (perhaps version 0.1.0 or something). This would make it easier to use with meson, since I would be able to link to the source tarballs to download automatically in my code.

The projects also already packaged in some repositories and I plan to package it for FreeBSD to use instead of bundled version in bonzomatic, and having official versioned releases would make is much easier to track updates and vulnerabilities.

I've created a v1.0.0 release. I'm trying to pick up maintaining the project and work on existing open issues. All bug fixes will be in v1.x.


[NEW FEATURE] about column layout

container names are on the right side of the table, plus and trunkated even if there's some space so it not too easy to understand what  its a container name

(on the image above, first line is "bitwarden" and second is "cloudflared")
Maybe its some idea behind, but at least have an option to switch to more "regular" view with "names" as first column, aligned to left side and trunkated to... 15-20 characters will be very helpful

Yeah I can see the issue, the images name can also get especially long (looking at you VS Code dev containers).
The logs section includes both the current log line that you have selected, and the currently selected container name, to help with this issue.
I think there is more information that should be displayed, there's an open issue for listing a containers open ports, so maybe need to look into making the view a little more compact or efficient.

I think having the container name first will be more intuitive to me. Its the first thing my eyes scan

Yeah that probably makes sense, what order do you think the columns should be?
name, state, status, cpu, mem, id, image, rx, tx
Also think the image name should be truncated to 32 chars, the same approach as with the container name.

Yeah makes sense. Maybe more usage of nerd font icons can make even more terse. Or stuff like "45 minutes" -> "45m" etc.

nerd font icons?

https://www.nerdfonts.com/
Some terminals support them out of the box, some require users to patch their font to add these extra symbols to it.

This layout seem reasonable?
Also, an ellipsis added to the image/container name if it has 30 or more characters?

a little off-topic: any hope for option (switch) to change text alignment to "more traditional" left?..

In terms of the headers and content?
Can be done with relative ease, could put it behind a --left flag, unless it looks substantially better than now on which case it would be default.

a little off-topic: any hope for option (switch) to change text alignment to "more traditional" left?..

Can you open this as a new issue?


fix: improve logging for message API

We could save messages that fail parsing, however current process is to queue and resend API failures. That in itself seems problematic. The process is fine for periods when the archive does not receive / respond to requests, say during a deployment or outage. But if parsing fails and responds with 415 or 400, the message is doomed to queue and retry indefinitely, or until manual intervention provides a resolution, which could cause disk issues if every attempt gets saved on the archive end.


Need INI Update for 10.0.17134.48

The latest build has been updated to .48 (there was also a .5) but the INI file does not reference it and the installer just quits on launch.
Out of curiosity, would it make sense to have the last entry be a 'default' of some sort, or is there too much risk involved?

Please provide a diagnostics screenshot (use RDPConf).

The latest build has been updated to .48

No, it was not updated - see version on your screenshot.

MSI installer version and it flashed up briefly and just went away.

Don't use it, it doesn't work in Windows 10 (#377).
Closed as a duplicate of #456.


Generated AVI file not playing in windows media player.

Hi Rolinh,
I'm using libgwavi  and generating avi file. It is playing fine with VLC player but fails in windows media player version 12 (tried in other versions also but without any luck).
Test AVI file : http://www.mediafire.com/download/39yn0rw1yqogjx4/noname1.avi
Regards,
Rajan.M

Development Environment


Add validation when a gRPC service is configured on a HTTP/1 cluster

When we were prototyping using the ext_authz filter, we configured it to use gRPC to a "self cluster", i.e. one that points at a socket on the local Envoy sidecar. This is perhaps non-standard, but the reason we did this is that we wanted the requests to run through our typical egress filter chain.
We forgot to set http2_protocol_options on this cluster, and were quite confused when our gRPC upstream service was returning OK status codes, and we were still seeing requests get denied by the filter. What happened was the filter was making HTTP/1 requests to the self cluster, and then they were upgraded to http2 before being sent to the gRPC upstream. The response then had the gRPC trailers stripped, so the filter failed the requests.
The clue to what was happening was that our egress logs were showing HTTP/1 rather than HTTP/2, everything else including gRPC trailers in the access log looked fine!
Sample log: ( the -/0 is the grpc-status header followed by grpc-status trailer)
[2020-02-27T00:27:45.898Z] "POST /envoy.service.auth.v2.Authorization/Check HTTP/1.1" 200 -/0 - 2979 11 57 57 "-" "797296e2-5515-428a-945f-3459265494fa" "multipass_safe--staging" "-" "-" "<IP_ADDRESS>:32508"

This is probably an obscure enough issue to be low priority, but I have 2 possible suggestions:

validate that the filter can only be configured with an h2 capable cluster when using gRPC (although this raises questions about when the validation should happen)
force gRPC client requests to h2 even when the cluster is not configured for h2

cc @snowp @alyssawilk this is related to common ALPN/protocol misconfiguration in the cluster config, related to work you have both been doing recently. Anything we can do here to make this better would be great.

+1; I had the similar issue.

I think I prefer the second option outlined, since iirc there aren't any cases where you wouldn't use HTTP/2 for gRPC.
Would we eventually want to support HTTP/3? If so, validating that its either HTTP/2 or HTTP/3 might be be best option.

@snowp — I would like to work on this issue; I too prefer the second option outline in the issue.

@cthumuluru do you have something on this already? WIP or anything? I can assign this issue to you.

@dio, I've not started on this yet. I'll start looking at it this week and provide an update next week.

Hm, this makes me wonder if we should have required that one of
explicit | downstream | alpn be configured when using the new protocol options.
I think it's new enough we could force one of them to be set.  It wouldn't necessarily prevent misconfiguration but it would at least make it visible at a glance that the cluster had http/1 config vs http/2 config.
@mattklein123 @htuch  think it's worth it, or should we just do the grpc => H2 checks and call it a day?

It would definitely be clearer, would this be a breaking change though?

It would definitely be clearer, would this be a breaking change though?

Yeah it sounds like a breaking change to me. Often gRPC would be configured as prior knowledge H2 and plenty of time without TLS/ALPN, so it seems like just checking for H2 would be great?

It would be a breaking change on config which landed 7 days ago: https://github.com/envoyproxy/envoy/pull/14079
I'm good either way, making it explicit (now, before folks pick up the new config) or someone can just do the H2 checks later on.

It's a good point that this landed only recently. For security issues we have a defined window where we just fix on master. @envoyproxy/api-shepherds should we add some similar grace period for breaking changes or is this going to be hard for consumers?

I'd be in favor of a small grace period, like maybe a couple of weeks.  It seems like within that window, anyone who has started using the new fields will still have enough context to make whatever changes are needed fairly easily.  And I'd rather do that than have to deprecate something that we just recently added.

Sorry I just read this thread again and I didn't fully understand before what was being proposed.'

I think it's new enough we could force one of them to be set. It wouldn't necessarily prevent misconfiguration but it would at least make it visible at a glance that the cluster had http/1 config vs http/2 config.

I think I suggested this during the original code review so +1 from me.

I'm good with this, but we should clarify this and make it explicit in https://github.com/envoyproxy/envoy/blob/master/api/API_VERSIONING.md. I'll take it offline with API shepherds.


Upgrades for Ogmios 6

Apologies for this PR being so huge. It's basically an entire rewrite of Kogmios because of the upstream changes in Ogmios v6.
Any disabled tests were manually tested by me as they only work a single time because they are spending a utxo for example.

Note: I just want to make sure that you are aware that these exists: https://github.com/CardanoSolutions/ogmios/tree/master/server/test/vectors in case you need to test serializer/deserializers against fuzzed values.