doc: board_porting: Provide guideline on MPU activation

Provide a rule to settle on MPU activation by default.
Request is to activate it by default if board resources allow.
Signed-off-by: Erwan Gouriou<EMAIL_ADDRESS>

Seems reasonable as long as this is not eventually going to be a recommendation to enable userspace by default.

User space is a different story. With basic MPU we are able to catch lots or errors related to accessing restricted memory areas, executing from RAM on XIP, stack overflows, etc., so it is very useful, and the footprint is limited.

to not enabled it.

"to disable it" if you are going this route

to not enabled it.

"to disable it" if you are going this route

Agreed

@ioannisg

"For ARM Cortex-M boards"

Is that really restricted to this specific arch ? Don't other archs have similar features?

@ioannisg

"For ARM Cortex-M boards"

Is that really restricted to this specific arch ? Don't other archs have similar features?

I believe so, yes; x86 and high-end Cortex-A,R have MMU, which is different from MPU.
ARC does have MPU but such boards should not be accounted as low-end devices, so the comment should not be applicable, IMHO.

@ioannisg

ARC does have MPU but such boards should not be accounted as low-end devices

So, MPU enabling recommendation is not limited to Cortex-M. Only the on resources basis disabling applies to Cortex-M. Which is true today, but some time later a new type of arch can show up with similar issues, isn't it ? I don't see the gain in not making this more generic.

Which is true today, but some time later a new type of arch can show up with similar issues, isn't it ?

Well, I would only think of low-end RISC-V platforms, adding MPU support in the future; then the comment could apply for such platforms. It's fine with me if you want to make the sentence more generic (but it definitely applies only to cortex-m, atm).

Well, I would only think of low-end RISC-V platforms, adding MPU support in the future; then the comment could apply for such platforms. It's fine with me if you want to make the sentence more generic (but it definitely applies only to cortex-m, atm).

Thanks. Would you mind approving then ?

Sure, I'd still want to hear opinions from other ARM board maintainers, though. FYI @MaureenHelm @galak :)

@erwango perhaps you can still update based on my recommendation above (excluding the part about cortex-m). Makes it more clear about what sort of limitations we consider :)

@erwango perhaps you can still update based on my recommendation above (excluding the part about cortex-m). Makes it more clear about what sort of limitations we consider :)

Sure, Done!


Signature is not valid: Signature was created at XXX and is therefore not yet valid at XXX

Hello, im trying to verify messages that were signed on a computer with time shifted forwards. As this is a realtime system the messages are verified within seconds since creation and the messages fail to verify with error below. It is not possible for me to guarantee that all clients wll have times synced in seconds and thus need way to accept these messages.
Problem can be easily reproduced by shifting the time forwards, createing the message and then verifying it once the time was set back to normal.
I get an error like
Signature is not valid: Signature was created at Wed Jul 24 19:25:38 CEST 2024 and is therefore not yet valid at Wed Jul 24 11:26:47 CEST 2024
I get no such error when using gnupg, neither with bouncypgp I used until now. The behaviour is not necessarily wrong, but it should be possible to override it, either by setting a threshold or disabling this kind of verification.
Version

pgpainless-core:

Thank you for great library!

Hey!
Thank you for your report!
The problem you are describing is quite an edge case. I think it will be hard to come up with a clean change to the API to allow for the creation time check to be disabled.
I guess the best way would be to add a method to ConsumerOptions to set a reference date for signature validation.
That way you could set the reference time to the signatures creation time, or take a known delay period into account.
Note though, that GnuPG is pretty much the only other OpenPGP implementation that ignores a future creation time (see https://tests.sequoia-pgp.org/#Detached_signature_with_Subpackets ).
I will put this on the roadmap for a future release, but don't hold your breath :D

Yes, it seems reasonable to configure it using the ConsumerOprions.
Thank you!


CC69817-69831: Adding break-lines to separate titles from code

Hello, @natemcmaster,
This proposed file change comes from https://github.com/dotnet/docs.zh-tw/pull/185.
Could you review this contribution and help to merge if agreed?
Many thanks in advance.

I'll take care of it @natemcmaster. Don't worry!

Thanks @mairaw


Investigate why we get undefined from getCell method

Description

Investigate why we get undefined from getCell method. Should we fix Handsontable or the wrapper?
Steps to reproduce

https://github.com/handsontable/handsontable/commit/b911bab7daa6d726bddba699fed82dc1b6a3b769

Your environment

Vue wrapper version: unknown
Handsontable version: unknown
Browser Name and version: unknown
Operating System: unknown

This looks like an issue with Handsontable, not the wrapper.
I've opened an issue for this in the main repo: handsontable/handsontable#5608


evaluate the gulpfile.js when something changes

instead of reinventing the wheel, it's better to use an external application such as http://nodemon.io/. Triaging this issue as a doc instead of a bug


Improving the navbar and Search feature

🖥 Frontend Issue

Description

Expected behavior

A proper Navbar should be there for easy understanding and working.The search option is even not working
Actual behavior

-Search option not working .Poor navbar feature
Screenshots or Video

https://github.com/user-attachments/assets/6fd072a7-13db-4c24-9c1e-7a3f35850f23
Are you participating in GSSoC?

[x] Yes
[ ] No

Assigned @hritika2409
Please update me in 24 hours with work

https://github.com/user-attachments/assets/073528ad-9d49-43fc-88fd-4ae0a298b7a9
Is this fine for you & can you please remove the search from the background image

if its fine @dhairyagothi for you then can i make a merge request?

Good to go @hritika2409 just remove behind one search icon

Also sync fork and pull origin before making PR @hritika2409

@dhairyagothi the background search icon is not a icon i guess it is the part of image but i will try

@dhairyagothi the background search icon is not a icon i guess it is the part of image but i will try

Let it be for now i will do. I have merged PR don't make a new PR for same issue
Good luck


SQL exec order by and desc feedback result may hung

Sharding-proxy version: 4.0.0-RC3

Problems encountered 1：Query SQL select association,rounds,election_time as electionTime,title from zhyxh where doctor_id = 848224 order by association,election_time desc feedback results hung.
Query SQL select association,rounds,election_time as electionTime,title from zhyxh where doctor_id = 848224 feedback results ok.
logs:  no error in logs

Problems encountered 2：Query SQL select rtitle_ch,rn_ch,r_data,rstatus_ch,rtype_ch,researcher_ch,researcher_phone,researcher_email,researcher_addr_ch,researcher_unit_ch,exp_org_ch,applicant_ch,applicant_unit_ch,study_disease_ch from chictr where id in                (                         '2443'                ,                        '2615'                )                order by r_data desc feedback results error 10002 - 2Unknown exception: [No signature of method: java.lang.String.mod() is applicable for argument types: (java.lang.Integer) values: [2].
logs: [DEBUG] 16:12:04.484 [ShardingSphere-Command-3] o.a.s.s.f.m.c.MySQLCommandExecutorFactory - Execute packet type: COM_QUERY, value: MySQLComQueryPacket(sql=select rtitle_ch,rn_ch,r_data,rstatus_ch,rtype_ch,researcher_ch,researcher_phone,researcher_email,researcher_addr_ch,researcher_unit_ch,exp_org_ch,applicant_ch,applicant_unit_ch,study_disease_ch from chictr where id in                (                         '2443'                ,                        '2615'                )                order by r_data desc) [ERROR] 16:12:04.536 [ShardingSphere-Command-3] o.a.s.s.f.c.CommandExecutorTask - Exception occur:  groovy.lang.MissingMethodException: No signature of method: java.lang.String.mod() is applicable for argument types: (java.lang.Integer) values: [2] Possible solutions: drop(int), find(), any(), take(int), use([Ljava.lang.Object;), find(groovy.lang.Closure)       at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:58)       at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:49)       at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)       at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:58)       at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)       at Script109$_run_closure1.doCall(Script109.groovy:1)       at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)       at java.lang.reflect.Method.invoke(Method.java:498)       at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)       at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)       at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294)       at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1019)       at groovy.lang.Closure.call(Closure.java:426)       at groovy.lang.Closure.call(Closure.java:420)       at org.apache.shardingsphere.core.strategy.route.inline.InlineShardingStrategy.execute(InlineShardingStrategy.java:90)       at org.apache.shardingsphere.core.strategy.route.inline.InlineShardingStrategy.doSharding(InlineShardingStrategy.java:72)       at org.apache.shardingsphere.core.strategy.route.inline.InlineShardingStrategy.doSharding(InlineShardingStrategy.java:59)       at org.apache.shardingsphere.core.route.type.standard.StandardRoutingEngine.routeDataSources(StandardRoutingEngine.java:200)       at org.apache.shardingsphere.core.route.type.standard.StandardRoutingEngine.route0(StandardRoutingEngine.java:188)       at org.apache.shardingsphere.core.route.type.standard.StandardRoutingEngine.routeByShardingConditionsWithCondition(StandardRoutingEngine.java:118)       at org.apache.shardingsphere.core.route.type.standard.StandardRoutingEngine.routeByShardingConditions(StandardRoutingEngine.java:112)       at org.apache.shardingsphere.core.route.type.standard.StandardRoutingEngine.getDataNodes(StandardRoutingEngine.java:97)       at org.apache.shardingsphere.core.route.type.standard.StandardRoutingEngine.route(StandardRoutingEngine.java:75)       at org.apache.shardingsphere.core.route.router.sharding.ShardingRouter.route(ShardingRouter.java:107)       at org.apache.shardingsphere.core.route.StatementRoutingEngine.route(StatementRoutingEngine.java:54)       at org.apache.shardingsphere.core.SimpleQueryShardingEngine.route(SimpleQueryShardingEngine.java:58)       at org.apache.shardingsphere.core.BaseShardingEngine.executeRoute(BaseShardingEngine.java:91)       at org.apache.shardingsphere.core.BaseShardingEngine.shard(BaseShardingEngine.java:74)       at org.apache.shardingsphere.shardingproxy.backend.communication.jdbc.wrapper.StatementExecutorWrapper.doShardingRoute(StatementExecutorWrapper.java:78)       at org.apache.shardingsphere.shardingproxy.backend.communication.jdbc.wrapper.StatementExecutorWrapper.route(StatementExecutorWrapper.java:64)       at org.apache.shardingsphere.shardingproxy.backend.communication.jdbc.JDBCDatabaseCommunicationEngine.execute(JDBCDatabaseCommunicationEngine.java:77)       at org.apache.shardingsphere.shardingproxy.backend.text.query.QueryBackendHandler.execute(QueryBackendHandler.java:54)       at org.apache.shardingsphere.shardingproxy.frontend.mysql.command.query.text.query.MySQLComQueryPacketExecutor.execute(MySQLComQueryPacketExecutor.java:73)       at org.apache.shardingsphere.shardingproxy.frontend.command.CommandExecutorTask.executeCommand(CommandExecutorTask.java:86)       at org.apache.shardingsphere.shardingproxy.frontend.command.CommandExecutorTask.run(CommandExecutorTask.java:66)       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)       at java.lang.Thread.run(Thread.java:745)

@lklkxcxc How many rows will be return for the Problem 1?
Can you have a try with the version 4.0.0?

@tuohai666 Three rows return for Problem 1. The same problem when I used  the version 4.0.0.

@tuohai666 Can you help me in this situation? We are using sharding at present

@lklkxcxc For Problem 1, I think we don't support order two items. Can you change SQL to:
select association,rounds,election_time as electionTime,title from zhyxh where doctor_id = 848224 order by association desc ?
For Problem 2, I think Id is the sharding key, please change where id in ( '2443' , '2615' ) to where id in ( 2443 , 2615 )

@tuohai666 Thanks！ For problem 2 ，It is ok that number removed single quotation marks.

@tuohai666 When sharding to support order two items ？

@tuohai666 Looking forward to your reply.

@lklkxcxc The root cause of this problem is an exception fired when query via a existing stream resultset. A stream resultset must be closed before a new query.
This problem only occur when order by a String column, because the String order by clause need the collation which is obtained by a SQL query.
To avoid the additional SQL query I set useDynamicCharsetInfo = false, and Connector/J will cache the collation instead of send a query to the MySQL server.

Test is a sharding table.
5.x support order two items as follow.

@tuohai666 The problem was sloved that add up parm to JDBC connect .

@lklkxcxc set useDynamicCharsetInfo = false is a work around, I will submit a pr to resolve this problem. After that we don't need to set the parameter any more.


1.16.4 Compatibility

Is there a way I can use this? Or does the developer have to merge it first?

Is there a way I can use this? Or does the developer have to merge it first?

Is there a way I can use this? Or does the developer have to merge it first?

Sure, you can download it here, I published the jar file in a github release this very minute :) https://github.com/Aurelien30000/Inventory-Rollback/releases/tag/1.4.1

Is there a way I can use this? Or does the developer have to merge it first?

Sure, you can download it here, I published the jar file in a github release this very minute :) https://github.com/Aurelien30000/Inventory-Rollback/releases/tag/1.4.1

This is very much appreciated. Thank you very much!

This is very much appreciated. Thank you very much!

This is very much appreciated. Thank you very much!

This is very much appreciated. Thank you very much!


Add support to new block height (-64)

Plugin Version:
Better RTP Version 3.2.1-1
Request:
I request the compatibility of the new block height (-64) for the use of datapacks and world generation plugins for the new caves and servers in production
How/Why:
Because if not, the plugin would fail (as it currently does) as it teleports underground and users die
Additional Context:
I have no image or video, but I think you have an idea

I would like to add this very soon, since 0 is the forced limit everywhere I will need to grab each worlds height limit when doing so. I'll try to get a patch out soon


Adjusted bitcoin core service, especially how to run the rpc in a sec…

Changes

Adjusted bitcoin core service for the RPC connection to be more secure.
Allowing host connection and making it possible to scrape data through localhost

In the old version it was needed to create a bitcoin.conf and that was a super tedious process. Now the service will run as a true one click install
Issues

missing docs

missing better docs* but now since the service was improved, it might not be the case.

@ALsJourney I am not sure if the image is still maintained as it was last updated 2 years ago? Maybe we need to change the image?

Hmm, this is the first on top of the Google list, so I took it, and it works for me.
Also, what's weird is on the overview page it says updated 2 years ago, but when you click on it to get to the detail page it says updated last year.
What do you suggest, write my own bitcoin core docker compose yaml? Or do you, at first glance, see any alternatives pop up?
I think you could run the bitcoin core software on Linux from scratch and then try to containerize it.

I could not find a viable alternative while quickly checking, so we will leave it for now.


Improve resolution notification with some additional information

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
New Notification, Other
🔖 Feature description
Improve resolution notification with some additional information:

DOWN DATE
DATE OF UP(ALREADY PRESENT)
TOTAL DOWN DURATION

✔ Solution
Improve resolution notification with some additional information:

DOWN DATE
DATE OF UP(ALREADY PRESENT)
TOTAL DOWN DURATION

❓ Alternatives
NC
📝 Additional Context
NC

Forgive my ignorance, how does this feature request get performed? We just wait for someone to work it or does louislam have to add this feature?

Bump
This would be awesome. It would allow me to stop using HetrixTools entirely. It's really handy to have all this info so that you don't have to do a bunch of math in your head, especially when you have lots of monitored services.

@honestlai @EdyDeveloper
Please refrain from posting +1 / requests for updates things on issues, as this makes issue-management harder.
Issues are for discussing what needs to be done how by whom.
We use 👍🏻 on issues to prioritise work.

@mabed-fr
What exactly is your feature request?
Is this a duplicate of Templating (#975) or #2362?
If it is not, please edit your issue to make it more clear ^^

@lazyjeffllc

Forgive my ignorance, how does this feature request get performed? We just wait for someone to work it or does louislam have to add this feature?

The Contribution guide is at https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

Yes these are the same features, but none are started. Unfortunately I don't have the required skills. I can only be useful for the system network and DevOps side

Yes these are the same features

Please close this PR then 😉
Duplicates just make managing issues harder

none are started.

My plan to improve upon this state is:

reformat the monitors see PR #3182
make sure that all notification providers code looks similar (see zoho-cliq vs telegram for what I mean)
fix that some monitors handle down/up vs general notifications differently
after upon improving on the code quality in this area, these features will be easier

I can only be useful for the system network and DevOps side

As mentioned in #1349, this project was lacking in this department. In the past year, it got better a lot, but we are not quite in a place I would call happy.
Louis seems to like manual processes for release management (see https://github.com/louislam/uptime-kuma/pull/213), but all testing PRs have been accepting ⇒ A PR adding more (unit)tests would likely be accepted and improve future reviews.
Also note #2720

Yes these are the same features

@mabed-fr ?

Yes these are the same features

Closing as a duplicate as discussed above


Add Background Sync

AFAIK it is supported only by Chrome (and Chrome Canary) at the moment.
I guess this would be added as feat=backgroundsync.

https://github.com/WICG/BackgroundSync

It's in development in Edge and Firefox now.

Shipped in Edge 15 per https://docs.microsoft.com/en-us/microsoft-edge/dev-guide#new-apis-in-edgehtml-15

@cvrebert as per this it's still in development
https://developer.microsoft.com/en-us/microsoft-edge/platform/status/backgroundsyncapi/?q=sync

Now available at https://caniuse.com/#feat=background-sync


Only the first 2 lines of the Crontab are saved

yiCam Outdoor camera running firmware version 0.2.7 for model y211ga
The Crontab configuration is only saving the first two lines that are entered.
This appears to be caused by the bash replace only replacing the first instance of \n with \t here: https://github.com/roleoroleo/yi-hack-Allwinner-v2/blob/3d11161a9e958561c48a9a476fb7c3e099d9d03d/src/www/httpd/cgi-bin/set_configs.sh#L79C28-L79C28 so anything past the 2nd newline gets discarded.
I believe the first forward slash needs to be doubled up for a global replace like this: POST_DATA="${POST_DATA//\n/\t}"

Thank you for your time.
Fixed here: https://github.com/roleoroleo/yi-hack-Allwinner-v2/commit/e5e998e05f8968d5fbad6438b61728f5195a5fed


name collision

FYI, looks like there is already a project called 'stoq' in the pypi index.
https://pypi.org/project/stoq/

Thanks for the heads up. We are aware of this..stoQ isn't currently a pip and the two projects are considerably different, so the overwhelming majority of people will probably not run into any issues with this naming conflict.


Time-less-than-or-equal-to operator pulls in too many milliseconds

A time filter like '2016-01-08T20:53:37.000Z' <= __time AND __time <= '2016-01-08T20:53:38.000Z' should resolve to intervals = 2016-01-08T20:53:37.000Z/2016-01-08T20:53:38.001Z but it actually resolves to 2016-01-08T20:53:37/2016-01-08T20:53:39.

man, what ever happens on exact milliseconds :-p


Unable to start FluentD

I have installed fluentD(td-agent) version 2.3.6 in CentOs 7. Now I'm unable to start td-agent. While starting td-agent it was throwing some error
[root@localhost ~]# /etc/init.d/td-agent start
Starting td-agent (via systemctl):  Job for td-agent.service failed because the control process exited with error code. See "systemctl status td-agent.service" and "journalctl -xe" for details.
                                                           [FAILED]
[root@localhost ~]# journalctl -xe
--
-- Unit td-agent.service has failed.
--
-- The result is failed.
Feb 02 17:10:05 localhost systemd[1]: Unit td-agent.service entered failed state.
Feb 02 17:10:05 localhost systemd[1]: td-agent.service failed.
Feb 02 17:10:05 localhost systemd[1]: td-agent.service holdoff time over, scheduling restart.
Feb 02 17:10:05 localhost systemd[1]: Starting td-agent: Fluentd based data collector for Treasure Data...
-- Subject: Unit td-agent.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit td-agent.service has begun starting up.
Feb 02 17:10:05 localhost fluentd[10544]: /opt/td-agent/embedded/lib/ruby/site_ruby/2.1.0/rubygems.rb:271:in `find_spec_for_exe': can't find gem fluentd (>= 0.a) (Gem::GemNotFoundException)
Feb 02 17:10:05 localhost fluentd[10544]: from /opt/td-agent/embedded/lib/ruby/site_ruby/2.1.0/rubygems.rb:299:in `activate_bin_path'
Feb 02 17:10:05 localhost fluentd[10544]: from /opt/td-agent/embedded/bin/fluentd:23:in `<main>'
Feb 02 17:10:05 localhost systemd[1]: td-agent.service: control process exited, code=exited status=1
Feb 02 17:10:05 localhost systemd[1]: Failed to start td-agent: Fluentd based data collector for Treasure Data.
-- Subject: Unit td-agent.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit td-agent.service has failed.
--
-- The result is failed.

I have tried to install fluentD gem using td-agent-gem install fluentD, but that doesn't make any difference.

Please follow CONTRIBUTING guide: https://github.com/fluent/fluentd/blob/master/CONTRIBUTING.md
Closed for now.

@rolindroy I have same problem in ubuntu 16.04. Do you know how to deal?

+1

I have resolved the issue by removing td-agent completely and re-installed with td-agent3.sh script.
Now Its working perfectly.
curl -L https://toolbelt.treasuredata.com/sh/install-redhat-td-agent3.sh | sh

Hi.
In /lib/systemd/system/td-agent.service, GEM_HOME and GEM_PATH have been set following.
Environment=GEM_HOME=/opt/td-agent/embedded/lib/ruby/gems/2.4.0/
Environment=GEM_PATH=/opt/td-agent/embedded/lib/ruby/gems/2.4.0/
I uninstalled td-agent3, and I installed td-agent2 again.
I changed version 2.4.0 to 2.1.0 in this file to resolve.
And,
# systemctl daemon-reload
# systemctl start td-agent
I have resolved the issue.
I guess that is occurred to uninstall "td-agent3" and to install "td-agent2".

@sesame thank you

https://toolbelt.treasuredata.com/sh/install-redhat-td-agent3.sh

This works for me.


Change run.sh to work when called from any folder

Hi
please change run.sh so it can be called from any folder. Now it only works when called from the folder, where bot is installed.
thanks!

The run.sh file is intended as a quick launch from the respective folder. I would advise creating a specialized run script if there is need to start the bot from outside this folder. (i.e. you can create a script that contains the following line: /path/to/TriviaBot/run.sh or cd /path/to/TriviaBot && node index.js to accomplish this)

The run.sh file is intended as a quick launch from the respective folder. I would advise creating a specialized run script if there is need to start the bot from outside this folder. (i.e. you can create a script that contains the following line: /path/to/TriviaBot/run.sh or cd /path/to/TriviaBot && node index.js to accomplish this)


Refactor AgentId, IslandId, and BoundaryLinkId into truly unique IDs.

Previously, we just randomly generated a number and panicked if the ID was already in a set. Now, we are using slotmap to have truly unique IDs. We've in fact completely removed the dependency on rand!

Codecov Report
Attention: Patch coverage is 99.27007% with 3 lines in your changes missing coverage. Please review.

Project coverage is 98.3%. Comparing base (1540180) to head (7b396a3).

Additional details and impacted files

Files
Coverage Δ

src/agent.rs
100.0% <ø> (ø)

src/avoidance.rs
95.8% <100.0%> (+<0.1%)
:arrow_up:

src/avoidance_test.rs
99.2% <100.0%> (-0.1%)
:arrow_down:

src/debug.rs
98.5% <100.0%> (ø)

src/island.rs
65.5% <ø> (ø)

src/lib.rs
90.8% <100.0%> (-0.6%)
:arrow_down:

src/lib_test.rs
100.0% <100.0%> (ø)

src/nav_data.rs
99.4% <100.0%> (+<0.1%)
:arrow_up:

src/nav_data_test.rs
99.5% <100.0%> (+<0.1%)
:arrow_up:

src/path_test.rs
100.0% <100.0%> (ø)

... and 5 more


Production code and ITs and Transactions

ITs should replicate the transactional status of the production code they are covering.

@frankhuster @larubbio punt?

punt
On Tue, Jul 7, 2015 at 11:49 AM, Lauren Lavoie<EMAIL_ADDRESS>wrote:

@frankhuster https://github.com/frankhuster @larubbio
https://github.com/larubbio punt?
—
Reply to this email directly or view it on GitHub
https://github.com/motech-implementations/mim/issues/355#issuecomment-119301490
.


Added copy to clipboard button to resource URL

Fixes https://github.com/projectkudu/ARMExplorer/issues/41

Actually, looks like that broke the build:
D:\home\site\repository\ng\manage.ts(711,12): error TS2339: Build:Property 'copyResUrlToClipboard' does not exist on type 'ArmTreeScope'. [D:\home\site\repository\ARMExplorer.csproj]
D:\home\site\repository\ng\manage.ts(720,20): error TS2339: Build:Property 'resUrlColor' does not exist on type 'ArmTreeScope'. [D:\home\site\repository\ARMExplorer.csproj]
D:\home\site\repository\ng\manage.ts(722,24): error TS2339: Build:Property 'resUrlColor' does not exist on type 'ArmTreeScope'. [D:\home\site\repository\ARMExplorer.csproj]

Can you take a look?

fixed in a48efcd0c144955acc8c8d5daca7481d196fae14

Ok, it's in Prod!

Thanks @ahmelsayed! I didn't get any error/warning in Visual Studio, but I compiled and tested in Debug so maybe VS was pulling some magic..


Cache does not load int values

Cached int values and propably also some other primitive values, can not be cast to the original type after loading them from cache.
Investigating this bug, I found out that Newtonsoft.Json does deserialize the int values by default as System.Int64 value types.
Our manipulation logic below
public void ManipulateState(object parameter)
{
    if (parameter is TConditionStateType cast)
     {
         ManipulateState(cast);
     }
}

fails because we can not implicitly cast object to int, we would first need to cast object to long and then long to int. But that is not very convenient.
So, because we don't explicitly deserialize to the desired types, we hit problems like that. We need to find a way how to preserve types on serialization so that we can then deserialize them back to those types.

Found this solution on Stackoverflow, which after testing it seems to work and fix this problem.


does brave support async call?

i want to use async client, does brave can support async client?
thanks!

Here's a related issue https://github.com/openzipkin/zipkin/issues/1189
Most importantly, we need to capture what the scenario here is, and what problems are trying to be solved. Currently, as mentioned above, we can "fake" rpc by treating the producer activity as the client side of an RPC and the consumer activity as the server side. That will work for sure between now and such time an alternate method exists.

async is via the "flush" method. Here's example: https://github.com/openzipkin/brave/tree/master/brave/src/test/java/brave/features/async

thanks very much!


CNF-14955: Adding postgres resources to controller

This adds the ability to manage the Kubernetes resources related to the Postgres database.  This is a first iteration which does not include the management of the PV/PVC for the persistent data.  It handles only the establishment of the deployment and the user credentials.  PV/PVC handling will come in a later commit.

/cc @mlguerrero12

/hold
having an issue with the bundle-run testing

/hold cancel
...false alarm, problem between keyboard and chair.

/lgtm

/lgtm
/approve


Could not initialize offscreen context!

| Camera Model                       |D435 |
| Operating System & Version | Ubuntu 16.04 |
| Kernel Version (Linux Only)    |  4.4.0-143-generic |                                        |
| Platform                                 | PC  |
Hi,
I bought a intel realsense depth camera D435 and trying to install realsense .
I followed this : https://github.com/IntelRealSense/librealsense/blob/development/doc/distribution_linux.md
When I am running realsense-viewer , I am getting the following error :
Could not initialize offscreen context!
I checked the command : ldd $(which realsense-viewer) | grep 'realsense2' :
Output :  librealsense2-gl.so.2.23 => /usr/lib/x86_64-linux-gnu/librealsense2-gl.so.2.23 (0x00007f5278f01000)
librealsense2.so.2.23 => /usr/lib/x86_64-linux-gnu/librealsense2.so.2.23 (0x00007f5277537000)
Thanks in advance for the help .
Vaibhav

Please make sure GPU (OpenGL) drivers are correctly installed on your system.
What type of GPU are you using?

I am using this GPU -
product: GP102 [GeForce GTX 1080 Ti]

Do you have nvidia drivers installed?
This is not strictly related to RealSense, various textual examples will work, but for graphical examples you need your Linux system to be able to properly handle OpenGL.

Yes, Its installed properly .

@Vaibhavjolly Could you please double check if glfw3, mesa and gtk packages were installed? These packages are required according to https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md
*glfw3*, *mesa* and *gtk* packages are required if you plan to build the SDK's OpenGl-enabled examples.

@Vaibhavjolly Any other questions for this issue? Looking forward to your update. Thanks!

@Vaibhavjolly If no other questions, will close it accordingly. Thanks!


WARNING ABOUT @BRANTJE

Just a friendly warning, as today this user (Sander 'aka' @brantje) was flooding our mqtt map channel with faulty information for literally no reason whatsoever. I posted all the proof, chat logs and screenshots on slacked before being removed by this very same person from slack, but I have everything saved.  If anyone needs more information before his removal from not only this team, but this entire branch, please let me know.
The last thing we need is toxic community members trying to ruin the fun for everyone.
Thanks.

To anyone landing on this page from a google search for @brantje (government name "Sander Brant") because you are looking for information on hiring this individual, do not risk your time or your money on this fraud.

Cross check this information with time stamps and your mqtt logs for confirmation ;)

Instead of listening to us (The #amsterdam channel).
You pushed social too hard, we said there was a big possibility for fake data.
Niantic implementing honey pots and such, you didn't listen and i made a PoC

I'm glad you posted this @BreezeRo : it shows how vulnerable the MQTT is to faulty information injection and possibly providing Niantic with a way to spot sniping-bots. They'd send in a few "S-Tier" pokemon locations (faulty ofcourse) and watch whoever moves to that location...

@faegan exactly my point, he just didn't listen, so i made a poc, that got out of hand.

Fack tab close issue

I'm leaving this here in the open and in public as I feel the community should know about how nasty this so called "team member" is. We don't need him around.

wft ?

Same thing I said @cbogithub I really don't know why he would take his anger out on the entire community when the community has done nothing to him.


Field decorator in Constructor field Parameters

Search Terms
Field, Decorator, Constructor.
Suggestion
This should be just syntax sugar. The idea is to allow defining in the constructor a decorator that will be applied to the field defined in the constructor.
So, my suggestion is to create something like a @field:decorator that would be applied to field parameter definitions on the constructor.

class MyType {
	constructor(
		@field:decorator public field: FieldType) {
	}
}

// what would be the same as

class MyType {
	@decorator field: FieldType;

	constructor(field: FieldType) {
		this.field = field;
	}
}

Use Cases
For example, suppose you are defining a class using Mobx. Sometimes, you want to receive some values in the constructor. That new syntax would help to build this kind of "data types" easily.
Examples

class Car {
	constructor(
		@field:observable public name: string,
		@field:observable public pilot: Pilot) {
	}
}

Instead of having to write this:

class Car {
	@observable
	name: string;

	@observable
	pilot: Pilot;

	constructor(name: string, pilot: Pilot) {
		this.name = name;
		this.pilot = pilot;
	}
}

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[ ] This feature would agree with the rest of TypeScript's Design Goals.

I don't know if there is something similar proposed for the decorators in new  EcmaScript versions.

The potential for syntactic confusion here with decorators on the parameters themselves is just too high, plus it's possible that @foo:bar gains some additional meaning in the future. This would best be left alone.


Cant log sessions after the update

Hello,
Thank you for this amazing plugin.
I use the plugin together with tasks. It had been working just fine until today. After the update, I can run the timer but cant see any of my logs in the log file. I tried different things like:

restart obsidian
removing the current task, ran timer, logging failed.
added text to the last line in the log file, ran timer, logging failed.
toogled "prefer saving to task file" option, tested with both on/off version, logging failed.
toogled "enable task tracking" option,  tested with both on/off version, logging failed.

Once the timer is done I get a pop-up message: "Folder already exists".
I cant see any messages in the developer tools.
Am I missing something obvious?

Hi， @natarslan
I'll look into it soon, have you tried changing the log file path

wow, egregious error, thank you for reporting!

Sorry for the inconvenience caused by the bug. I have launched a new release. Please let me know if the issue is resolved.

Wow! Super quick fix. I can confirm that its working now.


Add yamlencode / yamldecode

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
It would be helpful to have yaml functions corresponding to the jsonencode / jsondecode functions
Affected area/feature

Thanks for the suggestion.
Related comment: https://github.com/pulumi/pulumi-std/issues/17#issuecomment-1409410086


Fixes #134

This adds an auto-commenting feature for the new PRs raised.
Fixes #134
@Dev-tanay Kindly review and merge it.
Also, add "gssoc" and "level1/2/3" labels to this.
Thank you!

@Dev-tanay Please add a gssoc label and a level (1,2,3) to this.
Thank you!

@Dev-tanay Kindly add a level1 / level2 / level3 label to this, otherwise it's not counting towards the leaderboard!
Thank you!


Changes GitHub to Guild.xyz

Related Issue

Information about the related issue

Closes: #344
Describe the changes you've made
Updated the url to https://guild.xyz/webx-dao , changed logo as mentioned in the comment and changed the text to Guild.xyz
Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update.
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented on my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)
Before:

After:

Code of Conduct

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

OhMyPunkGuild!!! :fire: :fire_engine: :fire: :fire: That's gwrreeet!!!

Any updates on this? or need some help?

Any updates on this? or need some help?

Yeah I've implemented the above changes: updated the link to siteconfig and also implemented a rounded full image but am figuring out how to add an image to a group of objects: Icons.guild cause rendering it directly gives me error

Hello, thanks you for your contribution!  🚀 Your PR still requires changes from @Mustafiz04.

The link for guild.xyz line 42 in app/pages.tsx should not be hardcoded. Kindly ask you to add this in config/site/ts :

// config/site.ts

...

 links: {
    //twitter: "https://twitter.com/WebXDAO",
    //github: "https://github.com/WebXDAO",
    webxdao_gh: "https://github.com/WebXDAO/",
    webxdao_getstarted: "https://github.com/WebXDAO/start-here",
    webxdao_discord: "https://discord.webxdao.xyz/",
    webxdao_twitter: "https://twitter.com/WebXDAO",
    webxdao_linkedin: "https://www.linkedin.com/company/webxdao/",

    // Add this 👇
    webxdao_guild: "https://guild.xyz/webx-dao"
  },

Don't use <img> inside a Next.js application. You need to use <Image /> component.

Icons.guild cause rendering it directly gives me error

Can you share your error?
This should work with this snippet:
 <div className="flex justify-center gap-4">
          <Link
            href={siteConfig.links.webxdao_getstarted}
            target="_blank"
            rel="noreferrer"
            className={buttonVariants({ size: "lg" })}
          >
            Get started
          </Link>
          <Link
            target="_blank"
            rel="noreferrer"
            href={siteConfig.links.webxdao_guild}
            className={buttonVariants({ variant: "outline", size: "lg" })}
          >
            <Image alt="guild.xyz logo" src="/guild-logo.png" className="mr-2 h-5 w-5" width={150} height={150}/>
              Guild.xyz
          </Link>
</div>

Thanks for clarifiying
I already implemented the link part but what i was trying to do was to add an image and then export it in the Icons.tsx file in order to use Icons.guild and was faced by an error Usnupported Server Component
P.S: Implemented the changes

Thanks for clarifiying I already implemented the link part but what i was trying to do was to add an image to group of object under Icons and then export it in the Icons.tsx file in order to use Icons.guild and was faced by an error Unsupported Server Component Was confused with this #346 (comment)
P.S: Implemented the changes

Yes, I'm having issues too with using /public image inside the Icons component... Thanks for trying! :)


build: Update SPIRV dependencies

CI CrashDiagnosticLayer build queued with queue ID 280040.

CI CrashDiagnosticLayer build # 262 running.

CI CrashDiagnosticLayer build # 262 passed.


webp handling and storage adapters

Issue Summary
The newest templates expect to be able to serve images via format="webp"
This means the newest templates will NOT work with any sort of storage adapters other than local. To make matters worse, the local storage adapter seems to label everything as a .jpg when they are .webp (this was, at some point, for backward compatibility I believe).
The problem here seems to be that ghost only generates the webp images on request. Instead this should be moved to generating the actual webp (with .webp extension) during upload. From what I understand, this means the storage adapter would automatically write the new images at the request of Ghost.
The .jpg naming, I believe, should also be considered a bug since this is very odd and unexpected operation.
I am labeling this as a bug and not a feature request because at this time Ghost simply does not work correctly with any new template including templates like Source. All of your uploaded images, when using a storage adapter, will not be found.
Steps to Reproduce

Add a storage adapter
Upload an image
Use a recent template
Your images are broken

Ghost Version
5.0x
Node.js Version
any
How did you install Ghost?
ghost install
Database type
MySQL 8
Browser & OS version
Any
Relevant log / error output
No errors - simply 404s for the images.

Code of Conduct

[X] I agree to be friendly and polite to people in this repository

Happy to have a go at fixing this

Hey @elijahsgh Could you please expand a bit on what the issue is with Ghost? I'm not clear on what is Ghost doing incorrectly that doesn't allow these storage adapters to work.
As for the local storage adapter renaming to jpg, I believe this is working as intended - I'll check with the rest of the team and get back to you

I'd like to follow this issue, with a different kind of upload error (video upload), but I guess the cause is the same.
Step to reproduce:

Add a storage adapter
Upload a video
See 404 error, but preview / save anyway
Video is still playable, file is uploaded, but no thumbnail

This does not happen with local storage. My guess is same with Elijah, if Ghost generate the thumbnail before uploading both (video & thumb) to storage adapter it should be fine.

It seems to me to make more sense to have Ghost generate the webp at the same time that it generates the resolutions. The resolutions work as expected (calls the storage adapter save / saveraw). If the webps were generated at this time and used save/saveraw from the storage adapter then this issue would be resolved, I think.

It appears that when an image is uploaded the storage adapter is called to store the raw image and new image but it is NOT called to store the webp versions newer templates are serving. It seems the webps are created when the image is first retrieved from Ghost - which will never happen in the case of a storage adapter

All resized/alternative format images in Ghost are generated at time of request, this is very much intentional because we don't know ahead-of-time which sizes a selected theme or the image's use within post content will require.
Are you able to share the storage adapter code that you are using? It sounds like perhaps it's missing some of the methods required for resized images to work fully, namely the saveRaw() method (LocalImagesStorage example).

With a storage adapter the expectation is images will be served through, for example, a bucket serving all requests to /content so Ghost will never be triggered to generate the webp.

This sounds like an incorrect assumption to me. Storage adapters are a means for Ghost to read/write to a storage layer. Requests for images, especially content/images/size/* which is a dynamic endpoint should always hit Ghost so that it can generate the requested size/format images.
Ghost can't know ahead-of-time what image sizes or formats the at-time-of-request loaded theme will use or specifics of how the image will be used within post content. As such, images are generated at time of request.
The only way to avoid image requests needing to go through Ghost is to have your storage server handle the dynamic image generation itself by following the same URL format of /size/{wXhY}/format/{format}/{path}

It seems the webps are created when the image is first retrieved from Ghost - which will never happen in the case of a storage adapter

All resized/alternative format images in Ghost are generated at time of request, this is very much intentional because we don't know ahead-of-time which sizes a selected theme or the image's use within post content will require.
Are you able to share the storage adapter code that you are using? It sounds like perhaps it's missing some of the methods required for resized images to work fully, namely the saveRaw() method (LocalImagesStorage example).

This is my storage adapter slightly tweaked from the one linked from the Ghost website:
https://github.com/elijahsgh/ghost-google-cloud-storage
It's not much different than the one literally advertised by Ghost as an integration that Ghost supports.
If you install this storage adapter, configure it, and set a path to the bucket then Ghost will never get image requests - which is what we want. This was fine until themes started including format="webp"
If there's an error with the storage adapter let me know and I'll fix it. Otherwise Ghost has a very serious bug because you cannot successfully use Ghost "out of the box" with a modern theme that includes format="webp" (which is almost all of them).
I may be crazy or not noticing something in the editor that might fetch the images but it seems like during upload a lot of the resized image files are present in the bucket as soon as I upload. The dimensions for those images are based on whatever dimensions the theme has configured. The formats/webp stuff is never created.


remove torch max requirement

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


replicate.files is undefined

Tried to upload a file, but getting replicate.files is undefined.
Just console.log(replicate.files) to reproduce.

Hi @treeder. What version of the library are you using? The files API was first added in v0.30.0.

I'm using 0.30.2

Ah, I see what happened. Thanks for pointing this out. Got a fix in https://github.com/replicate/replicate-javascript/pull/278.

Thanks again for opening an issue about this @treeder. This should now be fixed in v0.31.0

Awesome, thanks for the quick fix!


Added module declaration for typescript users.

Added index.d.ts typescript declaration file to declare the project as a module.

Thanks for the contribution, but we do not support Typescript typedefs in the pino org. We recommend to upload these on DefinitelyTyped.


Morphosyntax: avoid requesting unavailable MWT models

Hi!
I tried the morphotag pipeline on Lithuanian (lit or lt) and bumped into an instance of Stanza's UnsupportedProcessorError that said the following:

Processor mwt is not known for language lt.  If you have created your own model, please specify the mwt_model_path parameter when creating the pipeline.

Given that it is certainly not just Lithuanian that will trigger this error with no justifiable reason, could I propose checking with Stanza's resources.json instead of manually maintaining a list of all languages without a MWT model?
Note: it is not really "instead of" but "alongside" the manually curated list for the purposes of this PR, because I could not safely assume that all of MWT models that had been deemed unnecessary here were actually absent from Stanza's standard repository. Perhaps there had been unrelated reasons to exclude them?

Thanks! This is super helpful. Will merge in a few days after testing.


Azure.Storage.Queues/README.md has incorrect example for accessing Queues using AzureIdentity

This example code is incorrect:
https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/storage/Azure.Storage.Queues/README.md#authenticating-with-azureidentity
// Create a QueueClient that will authenticate through Active Directory
Uri accountUri = new Uri("https://MYSTORAGEACCOUNT.blob.core.windows.net/");
QueueClient queue = new QueueClient(accountUri, new DefaultAzureCredential());

It should be like:
// Create a QueueClient that will authenticate through Active Directory
Uri accountUri = new Uri("https://MYSTORAGEACCOUNT.queue.core.windows.net/QUEUENAME");
QueueClient queue = new QueueClient(accountUri, new DefaultAzureCredential());

Tagging and routing to the team best positioned to assist.

Looks like a typo, thanks for letting us know!


Getting InvalidArgumentException when creating a new composer project inside container

The reason being that the target folder is not empty.

hmm which file do you have inside this folder?

A mapped /var folder as specified in docker-compose.yml.

your totally right - i have adopted the create-project documentation to use docker image of composer before starting the application containers - see https://github.com/wachterjohannes/sulu-docker/pull/32


Title bar doesn't work properly in case its size differs from the size of borders

Steps to reproduce:

Open ~/.config/way-cooler/init.lua
Change way_cooler.windows.borders.size to 10
Run binary

Result: container title bar is too narrow. There is a hole below.

Thanks for the report, there's probably a hardcoded number somewhere that's incorrect.
For anyone wanting to work on it, the problem is probably somewhere in here

If I had to guess, it's probably this little number

I think the issue may be in this line, the height of the drawing geometry is being set to thickness, which is always the edge thickness times 2, not considering at all the title bar height.


Links on Sample Record Set are confusing.

@carlkesselman commented on Tue Nov 01 2016
If you clink on one of the linked fields, it does what is expected.  However, if you click on an unlinked column, it doesn't go to the record.  That seems inconsistent to me.  Also, we have elements on the recordset that could be linked but aren't (biomass, creator).
In general, I think we may want to rethink the strategy for linking on the recordset pages.  Combining explicit links with click somewhere on the row to get to the details may not be the most intuitive strategy, especially when I also have a column that is a link that is the assecion number for the record.  If we have a record identifier for the row, then perhaps that should be the only way to get to the record?  Otherwise, having a tooltip that says "Click to see record details" would be helpful.

@hongsudt commented on Thu Nov 03 2016
@karlcz @robes what do you think?

One suggestion here:

no longer make the whole row a clickable target to go to the record page
introduce an explicit target for each row to drill down to record page
continue to allow column-specific targets based on markdown columns

Yes, and if there is nothing obvious like a record id or assecssion number to click on, then we should have an icon that indicates that this will expand the record.
Carl

Dr. Carl Kesselman
Dean’s Professor, Epstein Department of Industrial and Systems Engineering
Fellow, Information Sciences Institute
Viterbi School of Engineering
Professor, Preventive Medicine
Keck School of Medicine
University of Southern California
4676 Admiralty Way, Suite 1001, Marina del Rey, CA  90292-6695
Phone:  +1<PHONE_NUMBER>
Email:  carl<EMAIL_ADDRESS>Web: http://www.isi.edu/~carl
On Nov 4, 2016, at 5:29 AM, robes <notifications<EMAIL_ADDRESS>wrote:
One suggestion here:

no longer make the whole row a clickable target to go to the record page
introduce an explicit target for each row to drill down to record page
continue to allow column-specific targets based on markdown columns

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/informatics-isi-edu/chaise/issues/743#issuecomment-258279850, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADbjXoKe7tFhic1Q7qKfVAtMQrju4hC4ks5q6lJKgaJpZM4Ko7mp.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/informatics-isi-edu/chaise","title":"informatics-isi-edu/chaise","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/informatics-isi-edu/chaise"}},"updates":{"snippets":[{"icon":"PERSON","message":"@robes in #743: One suggestion here:\r\n\r\n1. no longer make the whole row a clickable target to go to the record page\r\n2. introduce an explicit target for each row to drill down to record page\r\n3. continue to allow column-specific targets based on markdown columns"}],"action":{"name":"View Issue","url":"https://github.com/informatics-isi-edu/chaise/issues/743#issuecomment-258279850"}}}

In fact, for consistency, we might always consider having such a column.
Carl

Dr. Carl Kesselman
Dean’s Professor, Epstein Department of Industrial and Systems Engineering
Fellow, Information Sciences Institute
Viterbi School of Engineering
Professor, Preventive Medicine
Keck School of Medicine
University of Southern California
4676 Admiralty Way, Suite 1001, Marina del Rey, CA  90292-6695
Phone:  +1<PHONE_NUMBER>
Email:  carl<EMAIL_ADDRESS>Web: http://www.isi.edu/~carl
On Nov 4, 2016, at 5:29 AM, robes <notifications<EMAIL_ADDRESS>wrote:
One suggestion here:

no longer make the whole row a clickable target to go to the record page
introduce an explicit target for each row to drill down to record page
continue to allow column-specific targets based on markdown columns

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/informatics-isi-edu/chaise/issues/743#issuecomment-258279850, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADbjXoKe7tFhic1Q7qKfVAtMQrju4hC4ks5q6lJKgaJpZM4Ko7mp.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/informatics-isi-edu/chaise","title":"informatics-isi-edu/chaise","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/informatics-isi-edu/chaise"}},"updates":{"snippets":[{"icon":"PERSON","message":"@robes in #743: One suggestion here:\r\n\r\n1. no longer make the whole row a clickable target to go to the record page\r\n2. introduce an explicit target for each row to drill down to record page\r\n3. continue to allow column-specific targets based on markdown columns"}],"action":{"name":"View Issue","url":"https://github.com/informatics-isi-edu/chaise/issues/743#issuecomment-258279850"}}}

Ah, that's what I meant but may not have stated well. Always have an "explicit target" which would be a synthetic column, could be a button, could be a 'click to expand' text link, etc.
I also am suggesting we may want to reconsider even making the ID column (even if there is one only) a link to the record page. I'm not sure our users will guess that they can click there to go to the record page. Something for us to consider.

We will be adding an action column to recordset. View will be one of them. Once the view button is on, we can disable the row-click event.

I am closing this issue as there are other issues to address this problem already.


Add API error handling similar to supplier app

Currently 404s returned by the API are resulting in 500s on the buyer app for invalid supplier requests. This change takes the model used in the supplier frontend to automatically handle uncaught APIErrors. It is not identical to the supplier app version because the default template data is generated in a different way.

:+1:


Keras Model does not converge

Hi, I’m using Petastorm and trying to train a Keras (using tf) model.
I’ve created a dataset using materialize_dataset, then I’ve used make_reader to create a data iterarator.
Using this iterator, I’m trying to train a Keras model, thought the model doesn’t seem to converge:
def get_data_iterator(dataset_path):
    with make_reader(dataset_path, num_epochs=None, cur_shard=0, shard_count=1) as reader:
        for row in reader:
           ....
            if i == batch_size:
                yield data

train_data = get_data_iterator(train_data_path)
history = model.fit_generator(train_data, steps_per_epoch=160,
                              epochs=20, validation_steps=8)

Epoch 1/20
160/160 [==============================] - 446s 3s/step - loss: 0.4831
Epoch 2/20
160/160 [==============================] - 415s 3s/step - loss: 0.4299
Epoch 3/20
160/160 [==============================] - 465s 3s/step - loss: 0.4509
Epoch 4/20
160/160 [==============================] - 456s 3s/step - loss: 0.4332
Epoch 5/20
160/160 [==============================] - 412s 3s/step - loss: 0.4385
Epoch 6/20
160/160 [==============================] - 458s 3s/step - loss: 0.4074
Epoch 7/20
160/160 [==============================] - 689s 4s/step - loss: 0.4337
....

When I’m reading the iterator to memory, and then train the model, it does seem to converge:
def read_generator_to_memory(generator):
    X_train = np.zeros(...)
    y_train = np.zeros(...)
    i = 0
    for row in generator:
        if i == steps_per_epoch:
            break
    X, y = sample
    X_train[i*batch_size:(i+1)*batch_size] = X
    t_train[i*batch_size:(i+1)*batch_size] = y
    i += 1

train_data = get_data_iterator(train_data_path)
X_train, y_train = read_generator_to_memory(train_data)
history = model.fit(X_train, y_train, batch_size=32, epochs=20)

Epoch 1/20
4800/4800 [==============================] - 120s 25ms/sample - loss: 0.4831
Epoch 2/20
4800/4800 [==============================] - 120s 25ms/sample - loss: 0.3678
Epoch 3/20
4800/4800 [==============================] - 141s 29ms/sample - loss: 0.2921
...

Just to clarify, the entire dataset does not fit into memory, I just used a small part (~5K rows) of the dataset for these two training attempts, and for some reason the first training does not converge, but the second does, even though I would expect the results to be the same.
Any idea what could be the reason for that?
Thanks, Stav

I would guess that there could be multiple model-related reasons for a model not to converge on a full dataset but converge on a subset of the full dataset. Maybe a comparable experiment would be to try and train from an iterator when you use only a single shard? Then the same experiment with reading all the shard to memory. At least then, we would know that we are trying to fit the model on the same data.
You can easily take just one shard of the dataset (say 1/10 of the data) by call make_reader(..., cur_shard=0, shard_count=10).

Hi, thank you for the response. Both training attempts were the exact same data.
After few more attempts, it seems that passing workers=0 (which causes generator to be executed on the main thread) to fit_generator call, seems to solve the issue and the model converges.
history = model.fit_generator(train_data, steps_per_epoch=160,
                              epochs=20, validation_steps=8, workers=0)
Epoch 1/20
160/160 [==============================] - 1008s 6s/step - loss: 0.3591
Epoch 2/20
160/160 [==============================] - 801s 5s/step - loss: 0.1909
Epoch 3/20
160/160 [==============================] - 563s 4s/step - loss: 0.1459
...

Could the assumption that executing the generator on the main thread resolved the issue be true?
Thanks, Stav

Hmmm. The getting next sample from the reader should be fully threadsafe starting release 0.7.0 - before that there was a synchronization issue (the fix is in commit 1a24452dc9d0d09e48e1ad177504e364ff73a615). Can you please confirm you are working with a version > 0.7.0?

I'm working with version 0.7.2, and it includes this commit.

This is concerning. I am not aware of any thread safety issues at the moment, but will try to reproduce your failure locally. Instead of training the model, I am planning to dump all the data that passes to Keras from some toy dataset and compare the bits Keras receives. Hope that to expose the issue, if there is one.


Can multiple cameras be connected as slaves to a signal generator

Can a signal generator (generating a standard pulse wave) be used with multiple cameras as slaves thereby making use of no master cam using this SDK?
I am trying to connect 3 cameras in sync but without having one of the cameras as a master. The setup instead will use a signal generator as a trigger for the 3 cameras.

Yes, this should be doable.  It is a feature we have added recently. You should be able to use the code in the branch called external_trigger. Hope this helps. Let us know if you have issues using it.
Cheers,
Vik

Thanks Vik. I am trying to build the external-trigger code but getting the following CMake Error.
Could not find a package configuration file provided by "trigger_msgs" with any of the following names:
trigger_msgsConfig.cmake
trigger_msgs-config.cmake

Try removing trigger_msgs from CMakeLists.txt under catkin required components (line 27).  The idea is that if you have the package it would use it otherwise it won't.

Yes I did that, but it then gives me the following error:
/home/demo/catkin_ws/src/spinnaker_sdk_camera_driver/src/capture.cpp:1172:30: error: ‘sync_message_queue_vector_’ was not declared in this scope
if(img_q->empty() || sync_message_queue_vector_.at(cam_no).empty()){
^~~~~~~~~~~~~~~~~~~~~~~~~~
/home/demo/catkin_ws/src/spinnaker_sdk_camera_driver/src/capture.cpp:1182:43: error: ‘sync_message_queue_vector_’ was not declared in this scope
if (abs((int)img_q->size() - (int)sync_message_queue_vector_.at(cam_no).size()) > 100){
Invoking "make -j8 -l8" failed

This is super wierd.  I just downloaded the repo fresh on a computer and removed line 27 from CMakeLists and was able to compile fine. Also, sync_message_queue_vector_ is declared in the capture.h file, so that error doesn't make sense.  Can you try starting from a clean slate. commenting line 27 and compiling.

Yes tried it. Works! Thanks Vik.
 While it says ACQUISITION on the terminal there are no updates after that to show images are being taken.
There is a particular warning about trigger_msgs.
Pasting it below, is this expected to work despite that warning? is one of the acquisition.launch parameters configured wrong?
process[acquisition_node-2]: started with pid [25670]
[ INFO] [1584371320.197257931]: [ OK ] USB memory: 1500 MB
[ INFO] [1584371320.197986024]: *** PARAMETER SETTINGS ***
[ INFO] [1584371320.198020138]: ** Date = 20200316
[ INFO] [1584371320.198304735]:   Save path set via parameter to: /home/demo
[ INFO] [1584371320.198337380]:   Camera IDs:
[ INFO] [1584371320.198645886]:     17416721
[ INFO] [1584371320.198668764]:     17416723
[ INFO] [1584371320.198964673]:   Camera Aliases:
[ INFO] [1584371320.198986965]:     17416721 >> cam0
[ INFO] [1584371320.198997755]:     17416723 >> cam1
[ INFO] [1584371320.199284913]:   External trigger: true
[ WARN] [1584371320.199306197]:   Using 'external_trigger'. Trigger msgs package not found, will use machine timestamps
[ INFO] [1584371320.199575928]:   Unique time stamps for each camera: false
[ INFO] [1584371320.199814226]:   color set to: true
[ INFO] [1584371320.200046860]:   Exporting images to ROS: true
[ INFO] [1584371320.200267405]:   Showing live images setting: true
[ INFO] [1584371320.200450630]:   Showing grid-style live images setting: true
[ INFO] [1584371320.200704065]:   Max Rate Save Mode: false
[ INFO] [1584371320.200906774]:   Displaying timing details: true
[ INFO] [1584371320.201119020]:   No. of images to skip set to: 20
[ INFO] [1584371320.201335687]:   Init sleep delays set to : 1.00 sec
[ WARN] [1584371320.201547525]:   'fps' Parameter not set, using default behavior: fps=20.00
[ INFO] [1584371320.201755497]:   'exposure_time'=0, Setting autoexposure
[ INFO] [1584371320.201965135]:   'target_grey_value'=0, Setting AutoExposureTargetGreyValueAuto to Continuous/ auto
[ INFO] [1584371320.202170359]:   Binning set to: 2
[ INFO] [1584371320.202378549]:   Using Software rate control, rate set to: 30
[ INFO] [1584371320.202586208]:   Saving images set to: 0
[ INFO] [1584371320.202767523]:     save_type set as: bmp
[ INFO] [1584371320.203254184]:   tf_prefix set to:
[ INFO] [1584371320.204002868]:   Camera coeffs not provided correctly, camera info messges will not be published.
[ INFO] [1584371320.204027871]: Creating system instance...
[ INFO] [1584371320.205332037]: Retreiving list of cameras...
[ INFO] [1584371321.269132461]: Numer of cameras found: 2
[ INFO] [1584371321.269229690]:  Cameras connected: 2
[ INFO] [1584371321.269373965]:   -17416721
[ INFO] [1584371321.269458658]:   -17416723
[ INFO] [1584371321.310479005]: Dynamic Reconfigure: Level :<PHONE_NUMBER>
[ INFO] [1584371321.311123284]: *** FLUSH SEQUENCE ***
[ INFO] [1584371321.311143590]: Initializing cameras...
[ INFO] [1584371323.790295136]: Deinitializing cameras...
[ INFO] [1584371324.204446857]: All cameras deinitialized.
[ INFO] [1584371326.204972989]: Initializing cameras...
[ INFO] [1584371328.389388063]: *** ACQUISITION ***

First step to debug is making sure that your hardware setup work with SpinView with the same external trigger. Have you tried that?


added impl statements for SPIM and UARTE interfaces on nrf9160

Added impl statements for SPIM and UARTE interfaces for the nrf9160

Thanks!
bors r+


qa_crowbarsetup: rewrite onadmin_get_ip_from_dhcp in perl

we now have roundup tests covering this function

Hm. According to our cloud-dev-language-strategy Python or Ruby should be used...

If it was a python tool then maybe, but this is a shell script so use default linux tools:
awk '/^lease /{ip=$2} /ethernet/{if ($3=="52:54:07:77:77:07;")res=ip } END{print res}' /var/lib/dhcp/db/dhcpd.leases

Or use instead: https://github.com/SUSE-Cloud/automation/pull/217

closing in favour of #217


Add IndexStore to Solution File

@quantumagi this looks like another PR on something that was merged by @dangershony.
Can you please update this ?

@quantumagi  I think Stratis.Bitcoin.IntegrationTests.csproj is also missing the reference to IndexStore.


source code migration (TFS to TFS) using GIT

Hello Team
i am currently doing migration of source code present in TFS server (2010) to TFS server 2015 with version history using GIT, here i am able to migrate my source code from first TFS server to GIT repository in second TFS server with the help of this document (https://github.com/git-tfs/git-tfs/blob/master/doc/usecases/migrate_tfs_to_git.md) with version history, now i want to transfer this source code (with  version history) to another project in TFS 2015 where we will use TF as version control can you please help me how can i proceed further
Thanks and Regards
Dushyant Padhya

git-tfs was not created to do that and can't do it due to the way it is
built.
Have a look to the tool 'git-tf' and deep checkin but if you have branches,
you're done and will loose the branches histories.
Good luck (and you will need it!)

Hello Philippe
Can you please help me with above issue ?
Regards
Dushyant Padhya


Fixed an issue where viewport width and height were populated as strings in some environments

Description
This change coerces viewport height and width strings into integers. Also, I updated the logic in the browserDetails section to match. I realized that nulls were being reported as 0 instead of undefined.

Related Issue
https://jira.corp.adobe.com/browse/PLATIR-23966

Motivation and Context

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (non-breaking change which does not add functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA or I'm an Adobe employee.
[x] I have made any necessary test changes and all tests pass.
[x] I have run the Sandbox successfully.

Nice! Are the unit tests failures real?

They are Saucelabs issues—the Github test runner can't connect to Saucelabs. I ran them all locally and they pass on Chrome.


basmallah broken on ie

internet explorer 11 has the basmala as broken

if i had to guess, the eot file is missing.

@ahmedre probably is!

@ahmedre is this still broken?

@ahmedre fixed?

Yes @mmahalwy
Looks like it's still broken.

this was fixed long ago!


Browsers and Operating System

During unzipping the archive the error occurred: Source Path Too Long
source-path-too-long

You are experiencing a not uncommon issue with NodeJS on Windows. It doesn't have anythingn to do with Aurelia. Please ask about this in the Gitter channel and someone will likely be able to recommend a course of action for you.


chore: fix dead code warning in a branch_updater

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#476
#475  👈
#473
#472
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @pepyakin and the rest of your teammates on  Graphite


Allow copied yaml to be edited in the create policy wizard

Previously, if you copied in YAML from another policy you had already created (ie copied from the "Edit Policy" page), you were unable to edit many of the fields. Now, you can edit those fields as needed.

/retest

Finally ready for review! Hopefully I didn't do anything too unusual to get the test in...
/cc @mprahl @KevinFCormier @willkutler

87.6%!! Congrats on beating sonarcloud @JustinKuli

/cc @jeswanke


tech(wmg): validate and record census schema version

Motivation:
Avoid inadvertently running the WMG pipeline on a Census data release with a new major version, since this may require schema and code updates for the WMG snapshot and pipeline, respectively. Ingesting Census data from a new major schema version should be an intentional act.  WMG snapshots should also track the provenance of the source data, to aid in any troubleshooting or data quality concerns that may arise later on.
Tasks:

[ ] Add constant that defines the major version of the Census that is admissible for the WMG pipeline
[ ] Add an initial pipeline step to check the Census schema version against the pipeline's admissible version and fail if not equal
[ ] Record the Census data release tag and the Census schema version in the WMG snapshot (e.g. as a TileDB Array metadata attributes).

This seems to indicate an either or - @atolopko-czi can you weigh in here? It seems to me like this ticket should both log the schema version AND not auto update on major upgrades.

This seems to indicate an either or - @atolopko-czi can you weigh in here? It seems to me like this ticket should both log the schema version AND not auto update on major upgrades.

Agreed, should clarify that it's both. Updated the issue.


[BUG] Review and update recommended Cluster info in metadata json file

Describe the bug
PR https://github.com/NVIDIA/spark-rapids-tools/pull/1216  (came from https://github.com/NVIDIA/spark-rapids-tools/issues/1143)  added a qualification_summary_metadata.json file. It has a recommendedCluster field in there that I think could enhanced to be more clear to the user.
We need to talk though all the CSPs/cluster types and decide what we want that output to be.
I think it should include the platform in the metadata file as well.
For instance on Databricks the executor instance type might be enough and we don't need the number of gpus, but we would want a number of worker nodes, not the number of executors.  But on prem could be different since we don't know the executor instance types available and generally just use number of executors.  GCP we may want to see a number of gpus and number of local ssds to use.

Another thing to revisit is the name of this file "qualification_summary_metadata.json".  Perhaps app_metadata would be more obvious to the user..
Also similar as above output figure out what we want the SourceCluster output to be.  Generally I would expect it to match the recommendedCluster output

Thanks @tgravescs  for the comments.

open questions on naming - use "worker" or "executor"? Or does it change based on csp?

Dataproc, DB-AWS and DB-Azure use the worker terminology. EMR uses core/task. We should probably use worker/workerNode/workerNodeType

Another thing to revisit is the name of this file "qualification_summary_metadata.json". Perhaps app_metadata would be more obvious to the user..

app_metadata.json makes sense

Currently here are the cluster info generated in the metadata json file (ps: similar structure for source cluster)
Dataproc
"recommendedCluster": {
  "driverInstance": "n1-standard-16",
  "executorInstance": "n1-standard-32",
  "numExecutors": 4,
  "gpuInfo": {
    "device": "nvidia-tesla-t4",
    "gpuPerWorker": 1
  },
  "additionalConfig": {
    "localSsd": 2
  }
}

Databrick AWS
"recommendedCluster": {
  "driverInstance": "m6gd.xlarge",
  "executorInstance": "g5.2xlarge",
  "numExecutors": 2
}

Databricks Azure
"recommendedCluster": {
  "driverInstance": "Standard_E8ds_v4",
  "executorInstance": "Standard_NC8as_T4_v3",
  "numExecutors": 2
}

EMR
"recommendedCluster": {
  "driverInstance": "i3.2xlarge",
  "executorInstance": "g5.4xlarge",
  "numExecutors": 16
}

OnPrem and Dataproc GKE  (after #1241)
"recommendedCluster": {}

Comments

For instance on Databricks the executor instance type might be enough and we don't need the number of gpus, but we would want a number of worker nodes, not the number of executors.

For Databricks we are showing only the executor instance type.
numExecutors refer to number of worker nodes (we should rename this if we decide to move with worker)

GCP we may want to see a number of gpus and number of local ssds to use.

We show the gpuPerWorker and localSsd to use (though its value is hard coded to '2')

But on prem could be different since we don't know the executor instance types available and generally just use number of executors.

We need to decide the cluster recommendation for OnPrem

If we want to include platform, we could probably have the structure as:

"clusterInfo": {
  "platform": "databricks-aws",
  "sourceCluster": {
    "driverInstance": "m6gd.xlarge",
    "executorInstance": "m6gd.2xlarge",
    "numExecutors": 2
  },
  "recommendedCluster": {
    "driverInstance": "m6gd.xlarge",
    "executorInstance": "g5.2xlarge",
    "numExecutors": 2
  }
},

Agree with the platform at the clusterInfo level.
I would lean towards workerNodeType, but we may also want to make this consistent.  I think the rapids_4_spark_qualification_output_cluster_information.json uses numExecutorNodes.  Can you check if its referred to anywhere else in actual user visible output?  I'm not as concerned about it matching terminology CSPs use as its concistent in our usage.
For on prem, I think we make some assumptions on number of gpus per node and number of nodes so we should output what those are and fill in the recommendedCluster.   We need to decide if we want the executorInstance to just not be there or say something like Not applicable.  Its sometimes nice to always have some output there.

Can you check if its referred to anywhere else in actual user visible output?

I checked the output files. We refer to numExecutors only in the rapids_4_spark_qualification_output_cluster_information and the metadata file.
I think the following structure looks reasonable

"recommendedCluster": {
  "driverNodeType": "m6gd.xlarge",
  "workerNodeType": "g5.8xlarge",
  "numWorkerNodes": 2
}

Now, executor term will always refer to spark executors
For OnPrem, we can have the following structure:

"recommendedCluster": {
  "driverNodeType": "Not Applicable",
  "workerNodeType": "Not Applicable",
  "numWorkerNodes": 2,
  "gpuInfo": {
      "device": "nvidia-tesla-t4",
      "gpuPerWorker": 1
   }
}

Its sometimes nice to always have some output there.

I agree. Fields driverNodeType, workerNodeType and numWorkerNodes should be present for all platforms.

Action Items:

[ ] Add cluster recommendation for onprem
[ ] Ensure correct gpuPerWorker is recommended for eligible platforms (dataproc, onprem)
[ ] Renaming of cluster shape columns to use worker prefix
[ ] Rename summary file to app_metadata.json
[ ] (maybe) Add local ssd recommendation: #657

@tgravescs Does the above list look good?

looks good, thanks!

For the follow up, I plan to improve the cluster recommendation for OnPrem and Dataproc as follows:
Part 1: Include 'calculated' GPU and 'hardcoded' SSD information in the metadata json file
File: qual_2024xxx/app_metadata.json

 File Output for `--platform dataproc`

  {
    "appId": "app-20240311074805-0000",
    "appName": "organic_email_fact_load",
    "eventLog": "file:/Users/psarthi/Work/event-logs/kuhu/EventLogsBundle/spark_ae_cdm_fact_email_organic_revenue_organic_0311-074258-rw3nb6o5/0311-074258-rw3nb6o5_100_64_57_59/5194506306351835588",
    "clusterInfo": {
      "platform": "dataproc",
      "sourceCluster": {
        "driverNodeType": "n1-standard-16",
        "workerNodeType": "n1-standard-8",
        "numWorkerNodes": 9
      },
      "recommendedCluster": {
        "driverNodeType": "n1-standard-16",
        "workerNodeType": "n1-standard-32",
        "numWorkerNodes": 9,
        "gpuInfo": {
          "device": "nvidia-tesla-t4",
          "gpuPerWorker": 4
        },
        "ssdInfo": {
          "numLocalSsds": 2
        }
      }
    },
    "estimatedGpuSpeedupCategory": "Medium",
    "fullClusterConfigRecommendations": "/Users/psarthi/Work/tools-run/qual_20240805222947_F2b32E83/rapids_4_spark_qualification_output/tuning/app-20240311074805-0000.conf",
    "gpuConfigRecommendationBreakdown": "/Users/psarthi/Work/tools-run/qual_20240805222947_F2b32E83/rapids_4_spark_qualification_output/tuning/app-20240311074805-0000.log"
  },

 File Output for `--platform onprem`

  {
    "appId": "app-20240311074805-0000",
    "appName": "organic_email_fact_load",
    "eventLog": "file:/Users/psarthi/Work/event-logs/kuhu/EventLogsBundle/spark_ae_cdm_fact_email_organic_revenue_organic_0311-074258-rw3nb6o5/0311-074258-rw3nb6o5_100_64_57_59/5194506306351835588",
    "clusterInfo": {
      "platform": "onprem",
      "sourceCluster": {
        "driverNodeType": "N/A",
        "workerNodeType": "N/A",
        "numWorkerNodes": 9
      },
      "recommendedCluster": {
        "driverNodeType": "N/A",
        "workerNodeType": "N/A",
        "numWorkerNodes": 9,
        "gpuInfo": {
          "device": "L4",
          "gpuPerWorker": 1
        }
      }
    },

Part 2: Improve Console Output to include

 Console Output for `--platform onprem`

+----+----------------------+-------------------------+-----------------+---------------------------------------+------------------------------+-----------------------------+
|    | App Name             | App ID                  | Estimated GPU   | Qualified Cluster Shape               | Full Cluster                 | GPU Config                  |
|    |                      |                         | Speedup         | Recommendation                        | Config                       | Recommendation              |
|    |                      |                         | Category**      |                                       | Recommendations*             | Breakdown*                  |
|----+----------------------+-------------------------+-----------------+---------------------------------------+------------------------------+-----------------------------|
|  7 | test_app_xxxxxx      | app-20240312004315-0000 | Large           | 9 workers (1 L4 each)                 | app-20240312004315-0000.conf | app-20240312004315-0000.log |
|  6 | test_app_xxxxxx      | app-20240312004328-0000 | Medium          | 25 workers to 50 workers (1 L4 each)  | app-20240312004328-0000.conf | app-20240312004328-0000.log |
|  3 | test_app_xxxxxx      | app-20240311085743-0000 | Medium          | 2 workers (1 L4 each)                 | app-20240311085743-0000.conf | app-20240311085743-0000.log |
|  4 | test_app_xxxxxx      | app-20240311074805-0000 | Small           | 9 workers (1 L4 each)                 | app-20240311074805-0000.conf | app-20240311074805-0000.log |
|  0 | test_app_xxxxxx      | app-20240311181337-0000 | Small           | 2 workers (1 L4 each)                 | app-20240311181337-0000.conf | app-20240311181337-0000.log |

 Console Output for `--platform dataproc`

+----+----------------------+-------------------------+-----------------+---------------------------------------------------------------------+------------------------------+-----------------------------+
|    | App Name             | App ID                  | Estimated GPU   | Qualified Cluster Shape                                             | Full Cluster                 | GPU Config                  |
|    |                      |                         | Speedup         | Recommendation                                                      | Config                       | Recommendation              |
|    |                      |                         | Category**      |                                                                     | Recommendations*             | Breakdown*                  |
|----+----------------------+-------------------------+-----------------+---------------------------------------------------------------------+------------------------------+-----------------------------|
|  3 | test_app_xxxxxx      | app-20240304225609-0000 | Large           | 15 X n1-standard-32 (4 nvidia-tesla-t4 each)                        | app-20240304225609-0000.conf | app-20240304225609-0000.log |
|  2 | test_app_xxxxxx      | app-20240312151736-0000 | Large           | 2 X n1-standard-32 (4 nvidia-tesla-t4 each)                         | app-20240312151736-0000.conf | app-20240312151736-0000.log |
| 15 | test_app_xxxxxx      | app-20240312033441-0000 | Large           | 5 X n1-standard-16 to 5 X n1-standard-64 (4 nvidia-tesla-t4 each)   | app-20240312033441-0000.conf | app-20240312033441-0000.log |
|  0 | test_app_xxxxxx      | app-20240311181337-0000 | Large           | 2 X n1-standard-32 (4 nvidia-tesla-t4 each)                         | app-20240311181337-0000.conf | app-20240311181337-0000.log |
|  6 | test_app_xxxxxx      | app-20240312004328-0000 | Large           | 25 X n1-standard-32 (4 nvidia-tesla-t4 each)                        | app-20240312004328-0000.conf | app-20240312004328-0000.log |
|  1 | test_app_xxxxxx      | app-20240311195738-0000 | Medium          | 2 X n1-standard-32 (4 nvidia-tesla-t4 each)                         | app-20240311195738-0000.conf | app-20240311195738-0000.log |
|  8 | test_app_xxxxxx      | app-20240312004315-0000 | Medium          | 9 X n1-standard-8 to 9 X n1-standard-32 (4 nvidia-tesla-t4 each)    | app-20240312004315-0000.conf | app-20240312004315-0000.log |

 Console Output for `--platform dataproc-aws`

+----+----------------------+-------------------------+-----------------+--------------------------------------+------------------------------+-----------------------------+
|    | App Name             | App ID                  | Estimated GPU   | Qualified Cluster Shape              | Full Cluster                 | GPU Config                  |
|    |                      |                         | Speedup         | Recommendation                       | Config                       | Recommendation              |
|    |                      |                         | Category**      |                                      | Recommendations*             | Breakdown*                  |
|----+----------------------+-------------------------+-----------------+--------------------------------------+------------------------------+-----------------------------|
|  0 | test_app_xxxxxx      | app-20240312151736-0000 | Medium          | 2 X r5d.2xlarge to 2 X g5.2xlarge    | app-20240312151736-0000.conf | app-20240312151736-0000.log |
|  8 | test_app_xxxxxx      | app-20240304225609-0000 | Medium          | 15 X r6gd.4xlarge to 45 X g5.2xlarge | app-20240304225609-0000.conf | app-20240304225609-0000.log |
|  5 | test_app_xxxxxx      | app-20240312004328-0000 | Small           | 25 X r5d.8xlarge to 150 X g5.2xlarge | app-20240312004328-0000.conf | app-20240312004328-0000.log |
|  6 | test_app_xxxxxx      | app-20240312004315-0000 | Small           | 9 X i3.2xlarge to 9 X g5.2xlarge     | app-20240312004315-0000.conf | app-20240312004315-0000.log |
|  7 | test_app_xxxxxx      | app-20240311122222-0000 | Small           | 2 X r5d.2xlarge to 2 X g5.2xlarge    | app-20240311122222-0000.conf | app-20240311122222-0000.log |
|  4 | test_app_xxxxxx      | app-20240311195738-0000 | Small           | 2 X r5d.2xlarge to 2 X g5.2xlarge    | app-20240311195738-0000.conf | app-20240311195738-0000.log |


In-order prerequisite verification

Some other testing libraries enable the user to specify some flag such that the prerequisites must happen in the given order. This comes in handy every once in a while.

I don't understand. Example?

(fact "emails in alphabetical order"
  (email-three-people :god :alex :brian ) => nil
  (provided
    (email :alex) => irrelevant :times 1 :in-order true
    (email :brian) => irrelevant :times 1 :in-order true
    (email :god) => irrelevant :times 1 :in-order true))

Something along these lines.

I'm going to close this because it's not going to happen, realistically.


Adding multiple file support to AddDataAPIBuilder()

Closes #187
It is required that Data API builder accept more than one configuration file. This is imperative to support Cosmos DB and important to support developers using Data API builder against multiple data sources.
Changes

Removed AddDataAPIBuilder(string, string, int?) as it is redundant to new methods (below).
Added AddDataAPIBuilder(string, int?, params string[]) overload to support multiple configuration files.
Added AddDataAPIBuilder(string, params string[]) support without specifying port or named arguments.
Updated readme.md with new and additional samples & documentation.
Added Unit Tests against new signature(s).
Included configuration files for testing purposes.
Modified PublicAPI.Unshipped.txt to reflect the updated AddDataAPIBuilder method signature(s).
Updated code and docs to support HTTP endpoints and explicitly not support HTTPS in dev.

Previous signature
public static IResourceBuilder<DataApiBuilderContainerResource> AddDataAPIBuilder(
    this IDistributedApplicationBuilder builder,
    [ResourceName] string name,
    string configFilePath = "./dab-config.json",
    int? port = null)

New signature
public static IResourceBuilder<DataApiBuilderContainerResource> AddDataAPIBuilder(
    this IDistributedApplicationBuilder builder,
    [ResourceName] string name,
    int? httpPort = null,
    params string[] configFilePaths)

New usage (multiple files, parameter names required - when no port)
var dab = builder
    .AddDataAPIBuilder("dab", configFilePaths: "./dab-condig.json", "./dab-condig-2.json");

Also added overload
public static IResourceBuilder<DataApiBuilderContainerResource> AddDataAPIBuilder(
    this IDistributedApplicationBuilder builder,
    [ResourceName] string name,
    params string[] configFilePaths)

New usage (multiple files, no parameter names required)
var dab = builder
    .AddDataAPIBuilder("dab", "./dab-condig.json", "./dab-condig-2.json");

@JerryNixon do you think this is something we can tackle before the 13th? I'd like to have it in the stable DAB release.

Looks like all tests are passing. @JerryNixon @FBoucher I'm happy with this to merge - if either of you wants to give it a once over and click the button go ahead!


get_colors fix

Small fix to DeviceStateAPI.get_colors().

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/73


Any chance you can ensure React 16.2 is supported

We are using this library in a project that needs/uses React & React Dom 16.2 - any chance you can ensure react-trix supports React 16.2..? That would be awesome thanks..

@netflakes I'll do some testing with React 16.2 and release an update if everything works flawlessly.


Brings up application when clicking on notifications

Description
When I click on the notifications, they simply disappear instead of bringing up the application from background. Is this the expected behavior?

If yes, I found it rather inconvenient. It would be much nicer if clicking on notifications brings up the app.
If not, what could it be that I'm doing wrong?

Specifications

Version of Electron: v1.4.10
OS: Arch Linux kernel 4.8.11, GNOME 3.22.2

Dup #327


Tests do not pass with fresh master

I did a fresh npm install, pulled master, and ran grunt buster. I get the following errors:
  TypeError: 'undefined' is not a function (evaluating 'Delegate.prototype.handle.bind(this)')
    at Delegate (./build/dom-delegate.js:9)  Exception should be thrown when no handler is specified in Delegate#on

  ReferenceError: Can't find variable: assert
    at ./test/tests/delegateTest.js:285

The first is due to the fact that PhantomJS does not support Function.prototype.bind().

@lazd this was fixed in PR #81, please reopen if you have any further issues.


Sui

Adding Exchange Integration FAQ topic

Update exchange-integration-faq.md

Update doc/src/learn/exchange-integration-faq.md

Co-authored-by: ronny-mysten<EMAIL_ADDRESS>
Update doc/src/learn/exchange-integration-faq.md

Co-authored-by: ronny-mysten<EMAIL_ADDRESS>
Update doc/src/learn/exchange-integration-faq.md

Co-authored-by: ronny-mysten<EMAIL_ADDRESS>
Update doc/src/learn/exchange-integration-faq.md

Co-authored-by: ronny-mysten<EMAIL_ADDRESS>
Update doc/src/learn/exchange-integration-faq.md

Co-authored-by: ronny-mysten<EMAIL_ADDRESS>
Update doc/src/learn/exchange-integration-faq.md

Co-authored-by: ronny-mysten<EMAIL_ADDRESS>
Update doc/src/learn/exchange-integration-faq.md

Co-authored-by: ronny-mysten<EMAIL_ADDRESS>
Update doc/src/learn/exchange-integration-faq.md

Co-authored-by: ronny-mysten<EMAIL_ADDRESS>
Update exchange-integration-faq.md

Co-authored-by: ronny-mysten<EMAIL_ADDRESS>

thanks

spam


Add support for fluent-plugin-aws-elasticsearch-service

Is your feature request related to a problem? Please describe.
If you want to use Elasticsearch in AWS you need IAM signing which is supported by the plugin above
Describe the solution you'd like
Support for https://github.com/atomita/fluent-plugin-aws-elasticsearch-service
Describe alternatives you've considered
Using https://github.com/abutaha/aws-es-proxy or fluentbit https://github.com/fluent/fluent-bit/pull/1852

Closing as it seems it's not maintained

Oops actually it is

https://github.com/banzaicloud/logging-operator/pull/536


Null explanation values

i'm having issues with deepexplain being all 0 or -0 for some classes, i thought LRP is based on the taylor decomposition so there is no way that it could be all values 0 if the prediction value is not 0.

Does this only happens with e-LRP?
All 0s might be caused by either all inputs at zero (independently on the output, as the output might be affected by biases) or by all gradients at zero (possibly also because of a problem in the network architecture or the way DeepExplain is used). I would need some more details to help.

tryed this with e-LRP, it's not null inputs for sure and i don't think that i have a problem with gradients decay, this is the code i'm runing with the transformation needed:
`from sqlalchemy import create_engine
import numpy as np
from pandas import DataFrame
from sklearn.preprocessing import LabelEncoder, StandardScaler
import keras.models
import pandas as pd
engine=create_engine('mysql://root:@localhost/claims')
connection=engine.connect()
#proxy=connection.execute('select * from valid')
proxy=connection.execute('select * from valid')
df=DataFrame(proxy.fetchall())
df.columns =[i.upper() for i in proxy.keys()]
df = df.replace('?', pd.np.nan).dropna(axis=0, how='any', subset=df.columns)
data=df
rem=['INCIDENT_LOCATION','INSURED_ZIP','POLICY_ANNUAL_PREMIUM','POLICY_BIND_DATE','POLICY_NUMBER','INCIDENT_DATE','ID','FLAG']
#rem=['INCIDENT_LOCATION','INSURED_ZIP','POLICY_ANNUAL_PREMIUM','POLICY_BIND_DATE','POLICY_NUMBER','INCIDENT_DATE','FRAUD_REPORTED']
for i in rem:
del data[i]
#cater sex
data['INSURED_SEX']=data['INSURED_SEX'].replace("MALE","1")
data['INSURED_SEX']=data['INSURED_SEX'].replace("FEMALE","0")
data['INSURED_SEX'].describe()
data['INSURED_SEX']=data['INSURED_SEX'].astype(int)
cleanup={'POLICY_STATE':{'OH':2,'IL':1,'IN':0},
'INCIDENT_STATE':{'OH':2,'NY':0,'SC':1,'WV':2,'VA':4,'NC':5,'PA':6},
'AUTHORITIES_CONTACTED':{'Police':0,'Fire':1,'Other':2,'Ambulance':3,'None':4},
'POLICY_CSL':{'100/300':0,'250/500':1,'500/1000':2},
'INCIDENT_TYPE':{'Single Vehicle Collision':3,'Multi-vehicle Collision':2,'Parked Car':1,'Vehicle Theft':0},
'INCIDENT_SEVERITY':{'Minor Damage':0,'Trivial Damage':1,'Major Damage':2,'Total Loss':3},
'PROPERTY_DAMAGE':{'YES':1,'NO':0},
'POLICE_REPORT_AVAILABLE':{'YES':1,'NO':0}}
data.replace(cleanup,inplace=True)
for i in cleanup.keys():
data[i]=data[i].astype(int)
lb_make=LabelEncoder()
label=['INSURED_EDUCATION_LEVEL','INSURED_OCCUPATION','INSURED_HOBBIES','INSURED_RELATIONSHIP','COLLISION_TYPE','INCIDENT_CITY','AUTO_MAKE','AUTO_MODEL']
for i in label:
data[i]=lb_make.fit_transform(data[i])
sc=StandardScaler()
relevent=list(data)
data=sc.fit_transform(data)
import numpy as np
import keras.models
from keras.models import model_from_json
import tensorflow as tf
#loading model
json_file = open('C:/Users/user/Desktop/demos/Release_version/model/model.json','r')
model_json = json_file.read()
json_file.close()
model = model_from_json(model_json)
model.load_weights("C:/Users/user/Desktop/demos/Release_version/model/model.h5")
print("Loaded Model from disk")
model.compile(loss='binary_crossentropy',optimizer='adam',metrics=['accuracy'])
graph = tf.get_default_graph()
#ind is the value to change
ind=0
x=data[ind]
with graph.as_default():
pred=model.predict(x.reshape(1,32))
print(pred)
from deepexplain.tensorflow import DeepExplain
from keras import backend as K
from keras.models import Model
with DeepExplain(session=K.get_session()) as de:
input_tensors=model.inputs
fModel=Model(inputs=input_tensors, outputs=model.outputs)
target_tensor=fModel(input_tensors)
attributions=de.explain('elrp',target_tensor,input_tensors,x.reshape(1,1,32))
print('input: ',x)
print('')
for layer in model.layers:
print(layer.get_weights()[1])
print('****************************************************************************************************')
print('')
print('Attributions: ',attributions)`
and for the execution you can visite this link to see the output: https://ibb.co/crMGPH i don't think it's a hight bias problem cause the null values i get them only for hight probability.

Does the model have multiple inputs? If not, the "input_tensor" param should be a single tensor, not a list.
What about other methods (eg. grad*input), do you see the same phenomenon?

I don't see the model from your comment above, but your screenshot show that the library outputs Model with multiple inputs: True. The call model.inputs returns a list, not a Tensor. Please see this example to pick a single tensor: https://github.com/marcoancona/DeepExplain/blob/master/examples/mint_cnn_keras.ipynb
If the "normal" input to the network has shape (1, 32), the same shape should have the input when calling de.explain(), while you have (1, 1, 32)
Still, I am not sure this is the problem. What kind of non-linear activation functions are used in the layers?

relu for all layers and sigmoid for the output layer, and you are mistaken sorry mislead you with the first imput it was intended to show u that the input values are not null as for the input layer it's a tensor,
model.inputs:
[<tf.Tensor 'dense_1_input:0' shape=(?, 32) dtype=float32>]

even after i updated the input calling for de.explain() in my code to have the shape of (1,32) still having the same results.

Ok, then I am afraid I would need to test myself to understand what is happening here.  Can you provide a minimal functional code that reproduces the problem and that I can run?

i have uploaded the model with minimal functional code that reproduces the same problem, i even added 2 other cases one of them it works and the other same problem:
https://drive.google.com/file/d/1sWWjZcb6onhnTVriDUfN726C5z9wUqwZ/view?usp=sharing

Thanks, I managed to reproduce it. However, I found that is the expected behavior. If your print the output of the second last layer with the following code
    fModel=Model(inputs=input_tensors, outputs=model.layers[2].output)
    print(fModel.predict(x.reshape(1,32)))

you can see that all outputs are 0, meaning that all ReLUs are not activated (with zero gradient) and no gradient-based method attribute credits to the input. The "probability" in output is only due to the bias.
Since you have only a small number of features and therefore performance is not an issue, I would suggest to use the occlusion method instead.

how did i miss that, i'm so sorry for the trouble and thank you allot for bearing with me and thank you for the advice it makes more sens now that i read the occlusion description.