Support Leader Access

Is there a way that certain reports can be run by those with Support Leader Access to particular groups? For example being able to run the Wall Chart Report on a group I don't directly have permissions to because I'm not added to a Unit within that group, but I have Support Leader access to View the group within Terrain?

@wilsteady
As I don't have Support Leader access this is hard for me to work out.
In Terrain, when you go to Group life what do you see? How do you switch between groups?
Some screen captures would help.
Simon

Let us know if you need more.

@NomisNostab This is the testing I did with you a while back. Unfortunately, it looks like the API won't let you access the group data if you have a Support Leader role. :-(

@wilsteady ,
Can I get you to switch to a group you have read/write access to and then go to the group life page.
Do you see the units and members of that group?
Could you do the same for a read only group?

Sorry it's been a while @NomisNostab - Just tried what you asked with DevTools open and it looks like there's a Terrain level glitch as I got this error, and now it's all frozen on me. In a group I have Read Only on, I was able to view all their Units through the Members tab, then as soon as I clicked on a unit, this error occured. Forced reload to fix. Members only shows Units, it doesn't have a split heading to view 'members' as well.

If I go into Branch Life from the Basecamp, I can see all the groups, and clicking on the Groups name only gives a summary level view of their Group Life stats.
Using the profile switcher to change to a group I have Read/Write access too does allow me to view the individual members within a particular Unit, including changing what their Patrol is, and who is in Unit Council.
DevTools only shows the normal Fetch commands. No errors at all.

Thanks Brendan,
When Terrain gets this functionality working, then I can start integrating Support Leader Access into Topo.
Simon

Hi Simon, Happy Christmas. No rush as i'm sure you're enjoying the holiday down time.
Looks like a recent change to either Terrain or Topo is now causing a glitch for Support Leaders. My view now displays what I imagine you intend is for youth members logging into Topo? I don't see all the other reporting sections anymore like I used to.

Hi Brendan,
Can I get you to send through a log dump so I can see how a Support leader
is shown.
https://github.com/NomisNostab/Topo-Blazor/wiki/Debug-Logs
Thanks
Simon
On Wed, 27 Dec 2023, 16:03 Brendan Wilson, @.***> wrote:

Hi Simon, Happy Christmas. No rush as i'm sure you're enjoying the holiday
down time.
Looks like a recent change to either Terrain or Topo is now causing a
glitch for Support Leaders. My view now displays what I imagine you intend
is for youth members logging into Topo? I don't see all the other reporting
sections anymore like I used to.
image.png (view on web)
https://github.com/NomisNostab/Topo-Blazor/assets/12633684/5518a964-9f0b-453f-a715-4480de7eb94e
image.png (view on web)
https://github.com/NomisNostab/Topo-Blazor/assets/12633684/b70d913d-0e88-4405-80e3-3b8c64c81c4a
—
Reply to this email directly, view it on GitHub
https://github.com/NomisNostab/Topo-Blazor/issues/67#issuecomment-1869950311,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APSDPAUDODTPJI5UTY4UXEDYLOTZXAVCNFSM6AAAAAAXMNJ62CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZHE2TAMZRGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Find attached. Couldn't locate how to send a PM in github.
nomisnostab.github.io-1703916650074.log

Hi Brendan,
I have pushed v1.48 which should fix your problem.
Please refresh Topo and see how you go.
Simon


⚠ Bofrost.be has degraded performance

In aeceb38, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1668 ms

Resolved: Bofrost.be performance has improved in 8c541e0 after 20 minutes.


Run maganto with PHP 8.1

magneto 2.4 with PHP version of 8.1
need to add with php latest version compostable
Problem 1
- Root composer.json requires laminas/laminas-code ^3.5.1 -> satisfiable by laminas/laminas-code[3.5.1].
- laminas/laminas-code 3.5.1 requires php ^7.3 || ~8.0.0 -> your php version (8.1.1) does not satisfy that requirement.
Problem 2
- Root composer.json requires laminas/laminas-escaper 2.7.0 -> satisfiable by laminas/laminas-escaper[2.7.0].
- laminas/laminas-escaper 2.7.0 requires php ^7.3 || ~8.0.0 -> your php version (8.1.1) does not satisfy that requirement.
Problem 3
- Root composer.json requires magento/composer 1.6.0 -> satisfiable by magento/composer[1.6.0].
- magento/composer 1.6.0 requires php ~7.3.0||~7.4.0 -> your php version (8.1.1) does not satisfy that requirement.
Problem 4
- Root composer.json requires pelago/emogrifier ^5.0.0 -> satisfiable by pelago/emogrifier[v5.0.0, v5.0.1].
- pelago/emogrifier[v5.0.0, ..., v5.0.1] require php ~7.1.0 || ~7.2.0 || ~7.3.0 || ~7.4.0 || ~8.0.0 -> your php version (8.1.1) does not satisfy that requirement.
Problem 5
- laminas/laminas-feed[2.13.0, ..., 2.14.1] require php ^7.3 || ~8.0.0 -> your php version (8.1.1) does not satisfy that requirement.
- laminas/laminas-feed[2.15.0, ..., 2.16.0] require laminas/laminas-escaper ^2.9 -> found laminas/laminas-escaper[2.9.0] but it conflicts with your root composer.json require (2.7.0).
- Root composer.json requires laminas/laminas-feed ^2.13.0 -> satisfiable by laminas/laminas-feed[2.13.0, ..., 2.16.0].

We already support PHP 8.1 on newer releases of laminas/laminas-code: it's up to Magento to upgrade here.


update packages

:white_check_mark: Build TheIdServer 2.1.1-fix-dependencies1-0100 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/fac1906632 by @)


[ci] macOS platforms: added LLVM toolchain for Arm

Summary
added LLVM toolchain for Arm on Apple Intel
release-17.0.1
added LLVM toolchain for Arm on Apple Silicon
release-19.1.1
Impact
Impact on user: No changes to user-facing functionality
Impact on build: Build process remains the same
Testing
github  [macOS-14,  macOS-13 (arm-08)]
https://github.com/simbit18/nuttx_test_pr/actions/runs/12277626847/job/34257527992
====================================================================================
Configuration/Tool: nucleo-f207zg/nsh,CONFIG_ARM_TOOLCHAIN_CLANG
2024-12-11 14:35:07
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
  Enabling CONFIG_ARM_TOOLCHAIN_CLANG
  Building NuttX...
chip/stm32_gpio.c:43:11: note: '#pragma message: CONFIG_STM32_USE_LEGACY_PINMAP will be deprecated migrate board.h see tools/stm32_pinmap_tool.py'
   43 | #  pragma message "CONFIG_STM32_USE_LEGACY_PINMAP will be deprecated migrate board.h see tools/stm32_pinmap_tool.py"
      |           ^~~~~~~
  Normalize nucleo-f207zg/nsh
====================================================================================

[Experimental Bot, please feedback here]
Yes, this PR appears to meet the basic NuttX requirements, though it could be improved.
Strengths:

It addresses a clear need: Adding LLVM toolchain support for Arm on Apple platforms.
It outlines the impact (albeit minimally).
It provides testing verification and logs, demonstrating functionality.

Weaknesses & Suggestions for Improvement:

Summary: The summary is too brief.  It should explain why LLVM toolchain support is needed. Is this for performance, compatibility, or some other reason?  It should also explicitly state what changed (e.g., "Added configuration options and build scripts to support...").

Impact: While the "no impact" statements are fine if true,  it's important to be thorough. Consider the following:

Impact on hardware: Does this impact any hardware, even indirectly? For example, are there any specific Arm architectures or boards that are now supported or unsupported because of this change?  Even if the answer is "no," explicitly stating it demonstrates that you considered the question.
Impact on documentation: If LLVM toolchain usage is now possible, the documentation almost certainly needs updating to guide users on how to use it.  Even a small documentation update warrants a "YES" here with a description of the changes.
Impact on compatibility: Does this change introduce any compatibility issues with existing code or tools? Even if the answer is no, explicitly stating so is beneficial.

Testing: The provided logs only show a successful build. More comprehensive testing is needed to demonstrate functionality.  Consider including:

Tests of basic functionality on the target hardware (if applicable).
Tests of any specific features related to the LLVM toolchain.
Performance benchmarks comparing LLVM to GCC (if relevant).

Clarity: Specify the exact versions of LLVM used (e.g., llvm-16.0.6, not just release-17.0.1).  This level of detail is crucial for reproducibility.

By addressing these weaknesses, the PR would be significantly stronger and more likely to be accepted.

Sorry @simbit18 I need to disable these sudoline  for the macOS Build Farm, since sudo will hang the Build Job, waiting for password:
https://github.com/apache/nuttx/blob/1dcada491772d70624fa759398f5b996a2a7f4f6/tools/ci/platforms/darwin.sh#L49-L51

Hi @lupyuen  have you tried to remove to remove this patch
https://github.com/lupyuen/nuttx-build-farm/blob/a99c1f8abafe3ae5f3f3c00ed0e24ffd1f12f7bb/run-build-macos.sh#L123
(CONFIG_ARM_TOOLCHAIN_GNU_EABI)
to see if it is ok the  build ?

@simbit18 Ah sorry I confused you :-) run-build-macos.sh is for the "build anything on macOS" script.
The script I patched is run-ci-macos.sh, which is for macOS Build Farm.


Need more guidance how to configure env. for "Kubernetes: Run"

How to let this command know where I would like to push and my username/password for that docker registry? For new users, should we remind them configure them in settings?

https://github.com/Azure/vscode-kubernetes-tools/pull/93 Ivan's PR fixed this one. This bug is duplicate with #77


fs/vfs/fs_truncate.c: Use ioctl to truncate on non-mountpoint inode

Signed-off-by: Jukka Laitinen<EMAIL_ADDRESS>Summary
This adds support to call ftruncate on an inode in non-mountable filesystem, e.g. a driver or shm
Impact
Enables calling ftruncate on a driver node
Testing
Tested on stm32f7 with a custom posix shm driver

ci error is fixed by https://github.com/apache/incubator-nuttx/pull/6055, let's merge this PR directly to save the resource.


add missing versions of nu_plugin_explore

related to

#86

Description
adds versions 0.92.0 and 0.92.3-c06ef201b72b3cbe901820417106b7d65c6f01e1 of nu_plugin_explore that are missing from registry.

Important
this will likely create a conflict with #86 but i wanted to have that plugin added, it's too useful :wink:

the CI is failing, https://github.com/nushell/nupm/pull/89 should take care of this :ok_hand:

Same, we can merge it until the registry problem is solved.


Added Binary Search Algorithm to search element on a sorted array

A binary search algorithm is to find the element is present or not in a sorted array.

Avoid "using namespace std" and code it without it.
Instead of using "vectornumbers={4,6,7,12,9,3,6,7}" use "std::vector numbers{ 4, 6, 7, 12, 9, 3, 6, 7 };"

if(res == -1){
cout<<"Element is not found"<<endl;
}
else{
cout<<"Element has found"<<endl;
}

if (res == -1)
std::cout << "Element is not found" << std::endl;
else
std::cout << "Element has found" << std::endl;

        Both are equivalent.

Yeah sure next time i will not use "using namespace std"


Timeout at com.zaxxer.hikari.HikariDataSource.getConnection

Environment
HikariCP version: 2.7.9
JDK version     : 1.8.0_101
Database        : PostgreSQL 9.5
Driver version  : 42.2.2
ORM : EclipseLink 2.7.1

Hi! I'm facing a strange behaviour using Spring Boot 2.0.2 and HikariCP 2.7.9. Sometimes pool connections start to hang in getConnection method but in the same time pool has many idle connections.
Logs:
2018-07-12 09:05:38.261 DEBUG 19298 --- [HikariPool-1 housekeeper] com.zaxxer.hikari.pool.HikariPool        : HikariPool-1 - Pool stats (total=64, active=49, idle=15, waiting=0)
2018-07-12 09:05:42.935  WARN 19298 --- [HikariPool-1 housekeeper] com.zaxxer.hikari.pool.ProxyLeakTask     : Connection leak detection triggered for org.postgresql.jdbc.PgConnection@64f03727 on thread XNIO-2 task-36, stack trace follows
java.lang.Exception: Apparent connection leak detected
at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:128)
....
Datasource configuration:
dataSource.driverClassName=org.postgis.DriverWrapper
dataSource.maximumPoolSize=64
dataSource.maxLifetime=300000
dataSource.leakDetectionThreshold=60000
Ussually this happens after 20-30 hours of application uptime.
If it helps the database had 64 connections "idle in transaction" at the time from logs. If I swith to tomcat-jdbc this issue doesn't reproduce and I have no lags with database connections.
Could you please tell how I can fix that?

A hang would produce timeout exceptions, but you don’t show any.
You do show a connection leak, which will eventually kill your server.  Tomcat will allow you to abandon connections and keep running, HikariCP will not.
Fix your connection leak first.

Found unresolved issue that looks very similar to mine: https://github.com/brettwooldridge/HikariCP/issues/109

@sazonov Maybe this answer helps?
Did you originally follow these guidelines?
Can you turn on DEBUG level logging for the com.zaxxer.hikari package?  I really want to see the logs that preceed and follow a timeout exception.  You can zip a log and attach it here.

Okay, I will try to reproduce it on my test environment and send additional info. Production env was moved to tomcat-jdbc today.

Thanks for the links. I used Spring guides to configure my app.

We haven't had a lot of user's on EclipseLink.  Not that there is anything wrong with the choice.  If we can sort out the cause of the failure, and pin down what a good SpringBoot-EclipseLink-HikariCP configuration looks like, I would love your help/input in wiki'ing up the result for future users!

Are you running with?

eclipselink.persistence-context.close-on-commit=true
eclipselink.persistence-context.flush-mode=commit
eclipselink.jdbc.exclusive-connection.mode=Transactional

I have all options set except the last one.
spring.jpa.properties.eclipselink.persistence-context.close-on-commit=true
spring.jpa.properties.eclipselink.persistence-context.flush-mode=commit
spring.jpa.properties.eclipselink.persistence-context.persist-on-commit=false

@sazonov The last one is the default value, I just wanted to make sure it wasn't changed to some other mode.

Yes, I'm using the default value.

Just reproduced issue on the test env. Attached you will find a log file. Just after a few seconds after application start hikari health checker detected connection leak but both connection pools had idle connections at the same time. There was no connection timeout error after that and the connection was returned to the pool 10 minutes later.
Could you please tell if house keeper says that we have a leak at getConnection method so it means that active thread is waiting for a connection or thread already has a connection and query is in progress?
HikariCP debug.log

Ok, a couple of things to note...
The idle timeout in pool #1 is too close to the maxLifetime, so idle connections are being ignored.  I suggest setting the idleTimeout to 180000, and minimumIdle to 16.
Pool #2 does not have the leakDetectionThreshold enabled.
Some thread is borrowing a connection for 10 minutes, what is going on there?
Some thread seems to borrow a connection from Pool #2, but does not return it.  Because the leakDetectionThreshold is not enabled, it is not reported.

Second pool has no timeout because it is used to build quite big reports and we have no problems with it. Log error is about pool 1. Okay, I will try to set idleTimeout.
I couldn't find the answer to my previous question. Could you please tell if house keeper says that we have a leak at getConnection method so it means that active thread is waiting for a connection or that thread already has a connection and query is in progress?

@sazonov The leak detection log means that a thread "already has a connection and query is in progress" (not that it is waiting).  The stacktrace that is logged shows where the code acquired the connection -- i.e. where it originally called getConnection() -- not where it currently is.

Is it possible to get information about the last query ran on a connection when a leak is detected? Sometimes the stack trace provides no useful information, e.g. when using scala and slick it uses a ThreadPoolExecutor to acquire sessions in response to Futures.

Is there any conclusion to this question？I had a similar problem.
Is this a problem caused by multiple data sources or multiple thread pools and inconsistent set parameters for each thread pool?
db1:
connection-init-sql: select 1
driver-class-name: com.mysql.jdbc.Driver
idle-timeout: 10000
maxLifetime: 1800000
maximum-pool-size: 40
minimum-idle: 10
pool-name: DataSource1
db2:
connection-init-sql: select 1
driver-class-name: com.mysql.jdbc.Driver
idle-timeout: 10000
maxLifetime: 1800000
maximum-pool-size: 20
minimum-idle: 10
pool-name: DataSource2

Hi, i got the similar issue. Basically i am using spring boot with hibernate and hikari db pool. My service is quite typical: spring transactions and hibernate as JPA. Settings of db pool:
hikari:
connection-timeout: 15000
max-lifetime: 60000
maximum-pool-size: 90
health-check-properties:
connectivity-check-timeout-ms: 1000
validation-timeout: 2000
leak-detection-threshold: 60000
connection-test-query: SELECT 1
minimum-idle: 80
After 30 minute of my application's work i got following exceptions:
o.h.engine.jdbc.spi.SqlExceptionHelper   : HikariPool-1 - Connection is not available, request timed out after 5099ms.
o.h.engine.jdbc.spi.SqlExceptionHelper   : SQL Error: 0, SQLState: null

@ZacParize I have the same question as above.  Are you getting leak detection exceptions in your log?

I've been inspecting my app for last two weeks and found that I have a code that uses both datasources at the same time in one transaction. So app got stucked in pool 1 because of pool 2. It is wrong and I rewrote that code. Now I'm waiting for the next release to depoy to production env and test it under high load. I hope that will solve the issue. Anyway I will write down issue status after that release.

@brettwooldridge , Yes i turned up leak detection debug and got leak detection exception.
I want to add that the problem apperars under high load.
I suspect the exception occurs because of my incorrect settings. If i have connection-timeout 15 seconds and processing of all records needs more than 15 seconds than i get connection timeout exception. But when will it be? When i will try to commit or when i will release the connection to pool?
Thanks for your help.

Sorry for the stupid question, but what does mean
ERROR 7 --- [l-1312-thread-1] o.h.engine.jdbc.spi.SqlExceptionHelper   : HikariPool-1 - Connection is not available, request timed out after 30499ms
the exception?
Is it a situation when connection was obtained from pool's connection bag but it was closed?

@ZacParize That error occurs when all of the connections are out of the pool (in-use) for more than the connectionTimeout, and another thread calls ds.getConnection().
Essentially, the pool was at maximum size, so no new Connections could be created, and all of the Connections were in-use.  After 30 seconds (connectionTimeout) of waiting for a connection to be returned to the pool, the requesting thread timed out.
If you look in the log, at DEBUG level, you can probably see that the available (idle) connections were 0, and there were one or more (possibly many) threads waiting for a connection.  Even if some connections are returned during the 30 seconds, if there are too many threads waiting, then the thread at the back of the queue may not get one before the timeout is reached.

@brettwooldridge , thanks for your responds.
I figured out that my problem was in the incorrectly calculated transaction time.
Your explanation helped me a lot.
Thanks for cool product.

I checked the last build of my app on production env and the issue didn't reproduce. So the problem was caused by using two pools in the same time. When one one pool was exceeded I got error messages with timeout from the other pool. I'm closing this issue. @brettwooldridge thanks for your time and assistance.

It seemed that the timeout has happened.
Append &connectTimeout=3&socketTimeout=3 to dataSource.url and try again.

[DEBUG] [] [HikariPool-1 housekeeper] [c.zaxxer.hikari.pool.HikariPool] - HikariPool-1 - Pool stats (total=20, active=0, idle=20, waiting=0) and the application still freezes. I am using RabbitMQ to save data to Mysql Database


Few base images updates

This PR  has the following changes:

Add node v15.14.0 v14.16.1 v12.22.1 and v10.24.1.
Add Python v3.9.4 and v3.8.9.
Add Go v1.16.3 and v1.15.11.

@balena-ci I self-certify!


Infinite recursion encoutered installing the SolarizedDark theme

Encountering this error when attempting to use spicetify-nix to install spotify with the SolarizedDark theme.
Installation is using a package that I'm including from home-manage on nixos 20.09 (just copied the config from your spotify.nix from your nixos-configuration). Dribbblish does work and is a big improvement, but SolarizedDark would match my color scheme so shooting for that one. SolarizedDark theme is simpler with just a user.css and color.ini.
Here's what I'm working with:
{ config, pkgs, lib, ... }:

let
  spicetify = fetchTarball https://github.com/pietdevries94/spicetify-nix/archive/master.tar.gz;
in
{
  imports = [ (import "${spicetify}/module.nix") ];

  programs.spicetify = {
    enable = true;
    theme = "SolarizedDark";
    injectCss = true;
    replaceColors = true;
    overwriteAssets = true;
  };
}

home-manager switch
error: while evaluating the attribute 'buildCommand' of the derivation 'home-manager-generation' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'text' of the derivation 'activation-script' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating 'mkCmd' at /nix/store/lc4np3b1gi4fh8wr98h1xshwqcn8mipl-source/modules/home-environment.nix:502:17, called from undefined position:
while evaluating the attribute 'data' at /nix/store/lc4np3b1gi4fh8wr98h1xshwqcn8mipl-source/modules/lib/dag.nix:91:37:
while evaluating the attribute 'data' at /nix/store/lc4np3b1gi4fh8wr98h1xshwqcn8mipl-source/modules/lib/dag.nix:85:9:
while evaluating the attribute 'data' at undefined position:
while evaluating 'g' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/attrsets.nix:276:19, called from undefined position:
while evaluating anonymous function at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/modules.nix:98:72, called from /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/attrsets.nix:279:20:
while evaluating the attribute 'value' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/modules.nix:465:9:
while evaluating the option home.activation.installPackages.data': while evaluating the attribute 'mergedValue' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/modules.nix:497:5: while evaluating the attribute 'values' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/modules.nix:491:9: while evaluating the attribute 'values' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/modules.nix:590:7: while evaluating anonymous function at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/modules.nix:477:28, called from /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/modules.nix:477:17: while evaluating definitions from /nix/store/lc4np3b1gi4fh8wr98h1xshwqcn8mipl-source/modules/home-environment.nix':
while evaluating 'dischargeProperties' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/modules.nix:549:25, called from /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/modules.nix:478:137:
while evaluating the attribute 'value' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/lib/modules.nix:338:44:
while evaluating the attribute 'passAsFile' of the derivation 'home-manager-path' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'postInstall' of the derivation 'spotify-<IP_ADDRESS>1.gbe11e53b-15' at /nix/store/ws19k4r7wik6jrd3f2rjxhi8w3q8dlv9-nixpkgs-20.09.1889.58f9c4c7d3a/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:192:11:
while evaluating 'boolToString' at /nix/store/27h5npm0d71ld7a6768sl5i00q6i9wx7-source/package.nix:36:18, called from /nix/store/27h5npm0d71ld7a6768sl5i00q6i9wx7-source/package.nix:55:15:
infinite recursion encountered, at /nix/store/27h5npm0d71ld7a6768sl5i00q6i9wx7-source/package.nix:55:

I'm staring at boolToString and just not seeing the problem! User error perhaps?

Thanks for the detailed feedback! I'll look into this this week and will keep you updated.

The problem was pretty silly.
There were a few booleans which set themselves.
  injectCss = boolToString (isDribblish || injectCss);

If you're using Dribblish, it never entered the loop, because of the "early return". I also fixed another issue I came across when testing your config and I can proudly tell that you're settings "work on my machine".

Confirmed that my desktop is now completely solarized :)
Thanks for the fixes! Interesting, guess I was zeroing in on boolToString, but it was the expression passed to it that's problematic..
You thought about trying to get this in nixpkgs? spicetify made it in recently.. but there' s no module around it, so it doesn't do much.. I like the approach you took here overriding the post install process of spotify. I wonder if that would be something acceptable upstream or if there's other things that I'm not seeing that you think might not make it acceptable?

To be honest, I have no clue if this code is up to par with the standards of Nix. I haven't noticed that Spicetify was added to the repo. I'll look at that for further steps in possibly upstreaming this package!

Was added here. There must be a similar type of program-- one that goes in and modifies the contents of the deployables of another, but I just can't think of one atm that might show us an approach that's already accepted. Happy to help in any way, by starting a discussion in nixpkgs, or doing the port, or anything. I can't be the only new nix user who will find this useful!
Thanks again!

Thanks for the suggestion. I'll start with making a pull request soon. When I do, I'll make sure to notify you ;)

Was added here. There must be a similar type of program-- one that goes in and modifies the contents of the deployables of another, but I just can't think of one atm that might show us an approach that's already accepted. Happy to help in any way, by starting a discussion in nixpkgs, or doing the port, or anything. I can't be the only new nix user who will find this useful!
Thanks again!
It's been a few months, but I'm currently working on getting a version of this in nixpkgs. You can check the progress here https://github.com/NixOS/nixpkgs/pull/111946


Question: Is there a way to force to get latest version of nuget?

Hi
Is there an option in the #load "nuget:package.name, 1.0.0" notation to force to get the latest version. It seems as if I put * as the version, it always takes the 'first' version. For example, I have a 1.0.0 and a 1.0.1. When I run it will always take 1.0.0 if I specify * as version.

Hi @stefandevo
We actually don't process the version number in any way.
If you execute your script with the debug option -d, you should be able to see the generated csproj file containing the package reference.
I did a quick test with Newtonsoft.Json and it produces the following package reference.
<PackageReference Include="Newtonsoft.Json" Version="*" />

This gave me the latest version of ´Newtonsoft.Json´
From the debug log
Resolved runtime library Newtonsoft.Json located at C:\Users\bri\.nuget\packages\newtonsoft.json/11.0.2\lib/netstandard2.0/Newtonsoft.Json.dll

More information about floating versions here
https://docs.microsoft.com/en-us/nuget/consume-packages/dependency-resolution#floating-versions

@stefandevo Are you still having this issue?

I will follow up on this one and create a test case the coming days.
What I had was, I created a new package 1.0, used that in the script, next, I created an update on the package 1.1, and ran the same script again. Then it just used the 1.0 package all the time. I will try to replicate that scenario.

Any updates on this, @stefandevo ?

The output shows multiple package references. Are you sure that you don't have more than one script in your folder or in any subfolder?

I do have multiple script in the same folder. Is this the issue?

That is probably what is causing the error. It should however not be an issue as long as your are on >=0.23.0.
See https://github.com/filipw/dotnet-script/pull/267 for more information

Executing that will get me into the REPL mode.

What about dotnet script -v ?

better :-)
0.20.0
that explains the version issue. I did execute before I started testing:
curl -s https://raw.githubusercontent.com/filipw/dotnet-script/master/install/install.sh | bash

I executed it again with sudo and now I have 0.24

Before that, I moved my script around to another location, and then it worked; deleting other scripts in the same folder, did not fixed it, I have to use another folder.

So now the info also worked:
test dotnet script --info
Version             : 0.24.0
Install location    : /usr/local/lib/dotnet-script
Target framework    : netcoreapp2.0
Platform identifier : osx
Runtime identifier  : osx-x64

Cool, and the Nuget package issue is resolved?

@stefandevo Can you confirm that it works as expected with 0.24.0 ?

Yes


unrevoke not working

I can get revoke to work with reason of "HOLD"
foreach ($laptop in $lost)
{
foreach ($domain in $domains)
{
get-CertificationAuthority "$CA" | Get-IssuedRequest -Filter "CommonName -eq $laptop$domain" | Revoke-Certificate -Reason "Hold" | Out-File "C:\Program Files\ADCS\Backup\CertHOLDmachinesfromPKADLABV2SHA256.txt" -Append
}
}
However, a similar piece of code to unrevoke the the certificates on HOLD does not work
foreach ($machine in $found)
{
foreach ($domain in $domains)
{
get-CertificationAuthority "$CA" | Get-IssuedRequest -Filter "CommonName -eq $machine$domain" | Revoke-Certificate -Reason "Unrevoke" | Out-File "C:\Program Files\ADCS\Backup\UnrevokemachinesfromPKADLABV2SHA256.txt" -Append
}
}
Please advise.

When you unrevoke, you have to use Get-RevokedRequest instead of Get-IssuedRequest, because you can unrevoke only revoked requests.

Closed due to inactivity.


Vue html report is compiled wrong "Unable to lookup source"

Observed Behavior
It compiles .js files correctly, but for .vue files it tries to resolve them by a path that contains ?####### in the end, so it cannot be resolved. That's one issue, another is that the html cannot be opened in browser

Also it worth to mention that it reads the .vue files and checks the coverage, but as I said earlier clicking on files doesn't work (getting "file not found" Chrome's page) and if I manage to open it there is that error on the screenshot above.

So my question is, is this a bug that should be fixed or I can prevent it from adding that "?######" somehow?
Forensic Information
Operating System: the operating system you observed the issue on.
OSX High Sierra
Environment Information: information about your project's environment, see instructions below:
Node 8.11.3
Yarn 1.9.4
Nyc 13.0.1
Also I don't use webpack or karma, testing vue with Node only.
package.json:
"scripts": {
  "unit": "mocha --require test/unit/setup src/**/*.spec.js --watch-extensions js,vue",
  "cover": "rm -rf coverage .nyc_output && nyc yarn unit",
},
"nyc": {
  "cache": true,
  "extension": [
    ".js",
    ".vue"
  ],
  "include": [
    "src/**/*.js",
    "src/**/*.vue"
  ],
  "reporter": [
    "html",
    "text",
    "text-summary"
  ]
},

Watching

Oh, I just found out that it's not related to nyc because source-maps have these ?7b82448b as well. Something is wrong in my setup. Sorry that disturbed you 😣, closing

@ilearnio For posterity's sake, can you describe what was wrong in your setup? I am having the same issue.

@sterlingstokes I was using vueify package to compile vue files in Node. It was adding these numbers to the end of paths, so I had to fork it and fix that as well as other stuff for my needs https://github.com/ilearnio/vueify#1f23ac8

Basically this was the fix for me https://github.com/ilearnio/vueify/commit/b2824c900bedf64106343d71a8bf4cb662106e7c#diff-ee97c5091b89979aace94674818996baR200


How to create a Table?

I don't understand how to use for instance DotMarkdown.MarkdownBaseWriter.WriteStartTableCell()
I get exceptions, like:
Cannot write 'TableCell' when state is 'Table'
How do I get out of that state? In what order should the methods be called?

Hi,
You have to start with WriteStartTable:

WriteStartTable

WriteStartTableRow

WriteStartTableCell

This is not convenient way how to create markdown table.
Recommended approach is similar how XML document is created with System.Xml.Linq.XElement.
Extensive usage of this approach can be found here.
MTable type uses MarkdownWriter under the hood.

I will try this second method out tonight.
I got the first way working before you answered, but the table output was not what I expected.

@vonj any progress?


Update section 5.6.2

"Inference benchmark directory names must be one of { mobilenet, ssd-small, resnet, ssd-large, gnmt }."
This needs to be updated for v0.7. Note that we are using '-99.9' and '-99' suffixes for the benchmarks where those apply.

mobilenet is gone and there is now dlrm, 3d-unet, rnnt

Are you submitting a PR to make that fix? Some of the benchmark names need to include the '-99' or '-99.9' suffixes.


Add code coverage using codecov

This PR also adds npm and codecov badges for better awareness of current version of package and current code coverage.
Fixes: #22

NOTE: bugzilla-ts repository might needs to be registered at codecov.

I updated workflow, @Mossop PTAL.


Generate a .gitignore file in the migrations directory

See comment in the gitignore file.
What basically happened to me is I created a project on one machine, it ran well, but when I cloned it on another, I couldn't start it, because the migrations directory didn't get picked up by git.
This will fix it.

I think the problem here is this line:
https://github.com/CrowdHailer/raxx_kit/blob/master/lib/raxx/kit.ex#L152-L156
This means that empty files are not written. This is done for things like the docker file where an empty file is returned from the template in the case the docker flag is false.
I suggest this means that all .dummy files will get removed unless we add some content to them.
A .gitignore is a smart solution, but we might end up with quite a few once we switch all the .dummy files

There's two slightly different issues here:

creating directories in the generated project
making sure the directories are picked up when the generated project is committed to git.

Empty dummy files (that get stripped on project generation) take care of 1. but not of 2. The .gitignore file with a comment content takes care of 2 as well.
Currently we only use dummy files for creating the deps and _build directories, which I think is alright: they get generated on the user's machine, so if they're new to elixir they can see what the directory structure is going to be, but won't be committed to git and the project is not going to break if the directories are not there - they will be created on demand.
Bottom line is I think it works correctly right now, but we can remove the dummy files if it causes any confusion on the raxx_kit contributor side - they're not essential.

also, I like the logic in the lines you linked to
https://github.com/CrowdHailer/raxx_kit/blob/master/lib/raxx/kit.ex#L152-L156 , it's pretty intuitive to me, unless there's a good reason for it, I wouldn't change it just yet.

I was about to say but what if deps or _build is empty. But raxx at least will always be a dependency so that's not happening.


Support for having dot and underscore as part of version

Hi Nikita,
Another feature request.
In flyway, the version part can be:

Version: Version with dots or underscores separate as many parts as you like (Not for repeatable migrations)

Hope this tool can support it and be consistent with flyway naming convention as well.
Thanks for taking look at it.

@YixingCheng Hi Yixing,
I've created a pull request for this feature here: #14
Thanks
Shane


Thanks for updating to 0.4.0 :) but where has the admin panel moved to in NC13?

Thanks for keeping the app maintained :+1:
I've just updated and I now cannot see the two config box to add the ID and URL.
Have they moved in this release?
Else its just been a long day!

It should be at the exact same location: Settings > Administration > Additional settings. Can you check your NC log for any related errors?

Так же пропало управление приложением, в логах нечего внятного не увидел.
Удаление и установка решило проблему.
Also management of the appendix was gone, in ravines there is nothing distinct did not see.
Removal and installation solved a problem.

This has been also reported in #53 and should therefor solve the issue.


ACL access.update args are missing id and data params

Link to reproduction
No response
Describe the Bug
I'm attempting to write a simple RBAC module for the app I'm building and I've run into an issue where the id and data params are missing from the args in the access.update function. The args are supposed to contain req, id, data. However, only the req param is coming through to any of my access functions, either at the collection level or at the field level.
Here's an illustration:
update: ({ req : { user }, id, data }) => {
	console.log(user)
	console.log(id) <-- undefined
	console.log(data) <-- undefined

        return allowedRoles(['author','sysadmin'], user, id, data)
}

And then in my allowedRoles function I use the user.id and data.createdBy field to identify a "virtual" author role that allows the user to modify any data that they themselves created:
const allowedRoles = (roles, user, id, data) => {
	if (roles.includes('author') && user.id === data.createdBy) {
		return true
	}

	if (roles.includes(user.role)) {
		return true
	}

	return false
}

export {
	allowedRoles
}

So you can see that without the data param being populated, it's impossible for me to identify the author of the original document that the update operation is targetting.
In the documentation it makes it very clear that these params should be expected:
https://payloadcms.com/docs/access-control/collections#update
But Payload simply does not function like this.
I also found another issue where the dev was having a similar issue, and there was much talk about different layers of evaluation for the access functions and that you tested that these values were being populated when a specific document was being update. Except they're not, the values remain undefined.
Please advise on when these params can be reliably accessed. I'm dead in the water now because of this and looking around at other solutions ...
To Reproduce
Use payload.
Payload Version
2.8.1
Adapters and Plugins
No response

@AlessioGr The recreation is pretty straightforward. Spin up an instance of payload and then log the id and data args from any access.update function.
Here's what my CollectionConfig looks like:
import { CollectionConfig } from 'payload/types'
import { allowedRoles } from '../../utilities/rbac/rbac.ts'

const accounts: CollectionConfig = {
	slug: 'accounts',
	auth: true,
	access: {
		create: () => true,
		unlock: ({ req: { user } }) => {
			return allowedRoles(['sysadmin'], user)
		},
		read: ({ req: { user } }) => {
			if (user) return true
		},
		update: ({ req : { user }, id, data }) => {
			console.log('user:')
			console.log(user)
			console.log('id:')
			console.log(id)
			console.log('data:')
			console.log(JSON.stringify(data, null, 3))

			return allowedRoles(['self','sysadmin'], user, id)
		},
		admin: ({ req: { user } }) => {
			return allowedRoles(['sysadmin','engineer'], user)
		}
	},
	admin: {
		useAsTitle: 'email'
	},
	fields: [
        ...

And when I run my tests I see Payload log the following to my console:

@AlessioGr What do you need from me to address this? I'm at a total standstill with development because of this issue and nothing I've tried has data flowing through the id or data params in my access functions.

Hey @zazz-ops — here's some info for you.
The update access control function certainly does receive id and data, but as you mentioned:

I also found another issue where the dev was having a similar issue, and there was much talk about different layers of evaluation for the access functions and that you tested that these values were being populated when a specific document was being update. Except they're not, the values remain undefined.

This is 100% true. I just set up a reproduction:
export const PostsCollection: CollectionConfig = {
  slug: 'posts',
  access: {
    update: ({ req, id, data }) => {
      console.log({
        user: req.user?.id,
        id,
        data,
      })

      return true
    },
  },
  fields: [
    {
      name: 'text',
      type: 'text',
    },
  ],
}

and I see the following three console logs when going to update a Post:
Running the /api/access function:
{ user: '65c3e32aa91a057cd16dff8c', id: undefined, data: {} }

Loading the document-specific access upon visiting the Edit screen (prior to submitting any data):
{
  user: '65c3e32aa91a057cd16dff8c',
  id: '65c3e32ba91a057cd16dff92',
  data: {}
}

Finally, upon submitting the ACTUAL update request:
{
  user: '65c3e32aa91a057cd16dff8c',
  id: '65c3e32ba91a057cd16dff92',
  data: {
    text: 'example post',
    updatedAt: '2024-02-07T20:08:11.392Z',
    createdAt: '2024-02-07T20:08:11.392Z'
  }
}

This is all functioning as intended, so I am going to close this issue. If you can provide a reproduction where the third access execution that I listed above does NOT pass the id and data as I have shown, then we will re-open and take a peek.
Thank you!

@jmikrut Ah, I think i see where the disconnect is. I'm not using the UI Console. I'm using mocha to run automated tests against the /api/* endpoints.
In fact, I'm not really interested in using the UI Console. My plan was to use Payload as an API layer and build a completely bespoke UI layer. I thought the baked-in UI Console might be useful for sysadmin purposes, but otherwise all I want from Payload is a backend. And it seems that your hooks are designed in a way that it might not be possible to get Payload to do what I need it to.
Considering the CollectionConfig code already posted above, when I run my test and it fires a standard fetch request at the Payload API I need the id and data in the access.update hook args to be populated. It only fires once, and those params are always undefined.
Here's an example from my tests. It's a fetch request, just wrapped in a little sugar client I create called nova to keep the code dry.
it('should allow publisher to update their own profile.bio', async () => {
		const result = await nova({
			method : 'PATCH',
			path : 'accounts',
			credentials : 'include',
			authToken : $db.accounts.publisher.authToken,
			query : {
				depth: 0,
				where: {
					email: {
						equals<EMAIL_ADDRESS>					}
				}
			},
			data : {
				profile : {
					bio : 'Testing testing testing ...'
				}
			}
		})

		if (result.errors?.length) log(result)
		expect(result.errors).to.be.an('array').that.is.empty

		$db.accounts.publisher.account = result.docs[0]
		log($db.accounts.publisher.profile)
	})

So if my app is only interfacing with Payload via its API, how would I write an RBAC plugin if the "extra" args in the hooks are never populated unless my user is using the UI Console?

Hi @zazz-ops,
The admin UI makes http requests to the API the same as you're doing, so that isn't a factor here.
The PATCH request that you've shared is the one used for bulk updates. Rather than updating it using a where query you shuld instead add the id of the user to the URL path. You should have access to the user id and if you don't, you could get it from decoding the authToken in your snippet using jwt-decode and get the id of the user that way.
Then your access function will have an id just like you're looking for.
		const result = await nova({
			method : 'PATCH',
			path : `accounts/${id}`,
			credentials : 'include',
			authToken : $db.accounts.publisher.authToken,
			query : {
				depth: 0,
			},
			data : {
				profile : {
					bio : 'Testing testing testing ...'
				}
			}
		})

Does this help?

@DanRibbens It sure does! Thanks for this. I'd been assuming that Payload was garnering the id from the authToken. Perhaps the batch endpoint should throw an error/warning in the case where only a single record is being updated.
So I'm seeing the id and the data params populated on the third invocation of the access.update function. This isn't perfect, but I'm back to moving forward.
It seems a strange architectural choice you've made that params are twice undefined until they're not. Would it not be far less confusing to have different hooks for the first two firings?
When I write an access control function for access.update my expectation is it runs immediately before any updates only, and always has the promised params populated.


Add mimetype for plot thumbnail

Description
Currently, the plot thumbnail mime type is not included in MAPPED_MIME_TYPES. Therefore, the thumbnail will not show even if the metadata is in the index.
For plot thumbnail issue in ticket Bug Submission: segmentation viewer and plot viewer preview not available e.g. dataset 119 and 125.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Run the portal locally and check related thumbnail metadata is returned correctly.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added unit tests that prove my fix is effective or that my feature works

We already have a mimetype for images that are to be used as thumbnails image/x.vnd.abi.thumbnail+jpeg. Should probably add an alternative for pngs as image/x.vnd.abi.thumbnail+png. The current proposal is not a good mimetype.

Thanks for the explanation. In this case, the additional mime type for the plot thumbnail probably should be image/x.vnd.abi.thumbnail+jpeg. I will update the current one to image/x.vnd.abi.thumbnail+png, but let me know if we don't need it. I will close this PR.


onPress TouchableOpacity triggers more than once

I ma building an android application and It seems that the touchable opacity when pressed from keyboard and d-pad, presses 4 times. I have my button as a separate component.
There is also another issue occurring and I think it's a bug. When I use the hasTVPreferredFocus true, it auto presses the button when it focuses on the button.  Here is my button component and my App.js
CustomButton.js:
import React, { Component } from 'react';
import {View, Text, TouchableOpacity, Animated, Easing} from 'react-native';

export default class CustomButton extends Component {

    constructor(props) {
        super(props);
        this.state = {
            loaded: false
        };
        this.focusIn = this.focusIn.bind(this);
        this.focusOut = this.focusOut.bind(this);
    }

    componentDidMount() {
        this.animatedValue = new Animated.Value(1);
        this.setState({loaded: true});
    }

    focusIn() {
        Animated.spring(this.animatedValue, {
            toValue: this.props.toValue
        }).start()
    }
    focusOut() {
        Animated.spring(this.animatedValue, {
            toValue: 1,
            friction: 3,
            tension: 40
        }).start()
    }

    render() {

        const animatedStyle = {
            transform: [{ scale: !this.state.loaded ? 1 : this.animatedValue}]
        }

        return (

            <Animated.View style={animatedStyle}>
                <TouchableOpacity hasTVPreferredFocus={this.props.selected} onPress={this.props.onPress} activeOpacity={1} style={this.props.buttonStyle} onFocus={this.focusIn} onBlur={this.focusOut}>

                        <View style={this.props.buttonWrapper}>
                                <Text style={this.props.buttonLabel}>{this.props.buttonName}</Text>
                        </View>

                </TouchableOpacity>
            </Animated.View>
        );
    }
}

App.js:
<CustomButton
   buttonStyle={styles.button}
   buttonWrapper={styles.buttonWrapper}
   buttonLabel={styles.buttonLabel}
   buttonName="Add"
   toValue={1.2}
   onPress={()=>this.addToBasket()}
   selected={true}
/>

in order to fix the multiple button press issue, I am using dbounce package from lodash. But is it really a viable option here? Because when using it, the presses feels slower because I have set the time to 200ms. Either way, I want to know if this is a bug or an issue with my project. I would still prefer not using dbounce (from my experience, presses are slower). But at the same time, I can't have a state set 4 times or call a function (which will eventually make an API request) 4 times.

Maybe someone can add throttle prop to button, that doesn't call onPress until some global delay, shared by all buttons has passed. there doesn't need to be a default value, it can be disabled. In some cases it's justified to be able to click multiple times quickly. This throttling is useful e.g. if onPress calls api or does something expensive.

Is this a bug or a problem with my code? When I touch, it seems to work fine. It just happens when I press the button. Only for the onPress. onFocus seems fine too. What is actually happening here?


Task 27

@SwapnaThiagarajan
Task21: Not modified the updates. Contains default activity names.

Task22: Not modified the updates. Contains default activity names.

Task27: Changes Verified. Default activity names.

I made all changes. But it is not showing in the sequence. I don't know Why
it is happening?
On Fri, Aug 25, 2023, 1:02 AM swathinelakurthi @.***>
wrote:

Merged #918
https://github.com/vajrang-b/RPA-Developer-in-30-Days/pull/918 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/vajrang-b/RPA-Developer-in-30-Days/pull/918#event-10190106535,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BA62GO2WYJ4NZH2DJQHKWLLXXBLZTANCNFSM6AAAAAA35UCEK4
.
You are receiving this because you were mentioned.Message ID:
<vajrang-b/RPA-Developer-in-30-Days/pull/918/issue_event/10190106535@
github.com>


More KVM seeds

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

But in the long run this is sustainable. We have >100K repros on syzbot.

BTW since when do we have license checks for sys/linux/test?
I don't think it complained before.

BTW since when do we have license checks for sys/linux/test?

Since when you gave them .txt extension ;)

BTW since when do we have license checks for sys/linux/test?

Since when you gave them .txt extension ;)

Haha, good catch, thanks!

But in the long run this is sustainable. We have >100K repros on syzbot.

Not sustainable, you mean?
I can drop them, actually

But in the long run this is sustainable. We have >100K repros on syzbot.

Not sustainable, you mean? I can drop them, actually

I mean we can't commit all O(100K) past repros. If we commit a subset, which subset is it?
It's better to handle all past repros on common ground, e.g. do something like:
https://github.com/cmu-pasta/linux-kernel-enriched-corpus
and periodically feed past repros into instances again or something.
I understand that lots of recent KVM bugs were reported manually and are not part of syzbot dashboard. So we may still want to add some of these, also taking into account importance of the KVM subsystem.
But in the long term it would be better to shift to syzbot reporting all bugs. We can feed syzbot instance using the new dashboard_only_repro manager parameter.

Ok, sounds good. I'll keep these repros then, but we can drop them in the future.
Please stamp the series again :)


Allow tilde expansion of relative paths

Previously, auto image = load!32("~/Pictures/daffodil.bmp"); would result in an Errno exception because File thought the path was invalid.

Thanks!


LWRP focused rewrite

I was having some issues reverting values, so I started down a path to cache the defaults as they're removed and kept tweaking and tweaking and here we are.
I completely understand if you'd prefer to leave this as a separate fork, but I thought I'd offer it up and let you decide for youselves.
Rather than duplicate everything here, the best option is to skim over the updated usage section in the readme for starters, and then then continue below where I'll outline the less visible changes.

These changes address #1 by way of the conclusion reached in this Chef Bug tracker issue. The result of trying to set an invalid or unsupported key is an explicit error explain that. The best way to handle this would be using the LWRP and something similar to not_if platform_family?('freebsd') to prevent the attempt to set keys based on platform.
They also address the caching issue mentioned above, allowing :remove to immediately return parameter values to their system default.
Everything goes through the LWRP, so if a config file is available values will always be persisted in the course of the chef run (with the ability to force the write sooner using action :save.
Support for flat keys i.e. 'vm.swappiness' => 20 and vm: { swappiness: 20 } render the same outcome
Fix issue where if key was removed from node.sysctl.params in a subsequent convergence, the value would be removed from the persisted file, but not unset from the server, violating the expected idempotent behaviour of cookbooks
Fix whyrun? support as it was claiming to support whyrun behavior and then changing kernel values in what should have been dry runs.
Split out BSD testing into a separate suite due to current suites using keys BSD does not support.

I've run the full test suite against this PR and it passes with two exceptions; the first is the integration tests for fedora-20 which fails for me due to this vagrant issue (but it passes once the suite is restarted), and the second is a foodcritic issue which I believe to be a false positive.
Happy to answer any questions you may have.

Closing due to lack of interest and the fact that it will now require further work to make it mergeable.


[CMSIS-NN] Fix memory alignment bug in CMSIS-NN demo

There is a latent bug in the CMSIS-NN demo app where the input and output tensors generated by the create_image.py script are not 16-byte aligned in memory. Although this does not cause an issue in the demo using the current person_detect model, if a different model is substituted with a larger output tensor, it causes the FVP to hang in certain cases.
This PR updates create_image.py to correct the issue.
@Mousius @ashutosh-arm @areusch

@grant-arm Thanks for the PR. Just for my understanding, why do we need to align .rodata to 16 bytes? I have seen this for constants in the code generated C files as well. Also, does it hold good for all variations of Arm® Cortex®-M processors?


Handle failed execution of tool and iterate accordingly

Sometimes we can get an error of "No liquidity for token T" - The agent needs to be smart enough to look for another token, and propose the transaction to the user

Self Healing Execution
What are we trying to achieve?

When a tools execution has an error, the agent needs to be smart enough to iterate accordingly based on its capacities/tools

Possible solutions
Verifier gives feedback
Prompt engineer the verifier to give feedback if necessary
Pros

Probably easier to implement

Cons

We might be mixing the finish of the execution loop with giving feedback if an error is given, hence, it probably do more bad than good

LLM call after run with error
After the execution loop, we are checking if there's any error from the chat, if so, we show it.
We might be able to do a LLM call, passing the error and the current agent informations, to see if it can propose an approach to achieve the user goals completely.
This is inspired from the build_goal functionality we currently have
Pros

We could have a more clean way to pass the error + created transactions (and failed) info
Probably allows to do more customization (more retries for example)

Cons

It's a bit hard to re-create the GroupChat. Which means that the agent might lose context when doing another run

Create nested chat with feedback agent
Create a new agent that takes care of giving feedback is error is thrown, add this agent as nested chat when the verifier returns a message
Pros

The feedback agent is outside of the groupchat, which help the messages in the groupchat to be completely focused on executing actions (less noise)

Cons

It is not straight forward to use nested chats inside a group chat


The Tolerations are invalid with Template of steps

The Tolerations are invalid with Template of steps
1.Problem
I set the tolerations in Template of steps  , but it's invalid.
Then I set the Workflow.Spec.Tolerations, it useful. It seems very strange.
Then I found dag had the same problem.

set for Template

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: steps-
spec:
  entrypoint: hello-hello-hello
  templates:
  - name: hello-hello-hello
    steps:
    - - name: hello1
        template: whalesay
        arguments:
          parameters:
          - name: message
            value: "1s"
    tolerations:
    - key: "key1"
      operator: "Equal"
      value: "value2"
      effect: "NoSchedule"
  - name: whalesay
    inputs:
      parameters:
      - name: message
    container:
      image: docker/whalesay
      command: [sleep]
      args: ["{{inputs.parameters.message}}"]

kubectl describe pod steps-tcztw-3119333882
Name:           steps-tcztw-3119333882
Namespace:      default
Priority:       0
Node:          <IP_ADDRESS>/<IP_ADDRESS>
Start Time:     Fri, 07 Aug 2020 20:45:36 +0800
Labels:         workflows.argoproj.io/completed=false
                workflows.argoproj.io/workflow=steps-tcztw
Annotations:    workflows.argoproj.io/node-name: steps-tcztw[0].hello1
                workflows.argoproj.io/template:
                  {"name":"whalesay","arguments":{},"inputs":{"parameters":[{"name":"message","value":"1s"}]},"outputs":{},"metadata":{},"container":{"name"...
Status:         Pending
IP:
IPs:            <none>
Controlled By:  Workflow/steps-tcztw
Containers:
  wait:
    Container ID:
    Image:         argoproj/argoexec:v2.9.3
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      argoexec
      wait
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      ARGO_POD_NAME:  steps-tcztw-3119333882 (v1:metadata.name)
    Mounts:
      /argo/podmetadata from podmetadata (rw)
      /var/run/docker.sock from docker-sock (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-hrm5j (ro)
  main:
    Container ID:
    Image:         docker/whalesay
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      sleep
    Args:
      1s
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-hrm5j (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  podmetadata:
    Type:  DownwardAPI (a volume populated by information about the pod)
    Items:
      metadata.annotations -> annotations
  docker-sock:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/docker.sock
    HostPathType:  Socket
  default-token-hrm5j:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-hrm5j
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age   From                                  Message
  ----    ------     ----  ----                                  -------

set for workflow Spec

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: steps-
spec:
  entrypoint: hello-hello-hello
  templates:
  - name: hello-hello-hello
    steps:
    - - name: hello1
        template: whalesay
        arguments:
          parameters:
          - name: message
            value: "1s"
    - - name: hello2b
        template: whalesay
        arguments:
          parameters:
          - name: message
            value: "10s"
  - name: whalesay
    inputs:
      parameters:
      - name: message
    container:
      image: docker/whalesay
      command: [sleep]
      args: ["{{inputs.parameters.message}}"]
  tolerations:
  - key: "key1"
    operator: "Equal"
    value: "value2"
    effect: "NoSchedule"

Name:           steps-wnth4-700877309
Namespace:      default
Priority:       0
Node:          <IP_ADDRESS>/<IP_ADDRESS>
Start Time:     Sun, 09 Aug 2020 15:28:48 +0800
Labels:         workflows.argoproj.io/completed=false
                workflows.argoproj.io/workflow=steps-wnth4
Annotations:    workflows.argoproj.io/node-name: steps-wnth4[0].hello1
                workflows.argoproj.io/outputs: {"exitCode":"0"}
                workflows.argoproj.io/template:
                  {"name":"whalesay","arguments":{},"inputs":{"parameters":[{"name":"message","value":"1s"}]},"outputs":{},"metadata":{},"container":{"name"...
Status:         Succeeded
IP:             <IP_ADDRESS>
IPs:            <none>
Controlled By:  Workflow/steps-wnth4
Containers:
  wait:
    Container ID:  docker://43baf9495882556a6d15a7b8e7e73f4068802788f5e087564e2a8368b33c3d37
    Image:         argoproj/argoexec:v2.9.3
    Image ID:      docker-pullable://argoproj/argoexec@sha256:a25cbe11d210b67e9621fecd4505e3438d0dd3ce8fc5e8d3dea1bbc2adb853f6
    Port:          <none>
    Host Port:     <none>
    Command:
      argoexec
      wait
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Sun, 09 Aug 2020 15:28:49 +0800
      Finished:     Sun, 09 Aug 2020 15:29:00 +0800
    Ready:          False
    Restart Count:  0
    Environment:
      ARGO_POD_NAME:  steps-wnth4-700877309 (v1:metadata.name)
    Mounts:
      /argo/podmetadata from podmetadata (rw)
      /var/run/docker.sock from docker-sock (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-hrm5j (ro)
  main:
    Container ID:  docker://fb8ed24f9eb8e7a47b42ad108c91d2992a71a6a3d2c4d096d46c67209134d074
    Image:         docker/whalesay
    Image ID:      docker-pullable://docker/whalesay@sha256:178598e51a26abbc958b8a2e48825c90bc22e641de3d31e18aaf55f3258ba93b
    Port:          <none>
    Host Port:     <none>
    Command:
      sleep
    Args:
      1s
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Sun, 09 Aug 2020 15:28:59 +0800
      Finished:     Sun, 09 Aug 2020 15:29:00 +0800
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-hrm5j (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  podmetadata:
    Type:  DownwardAPI (a volume populated by information about the pod)
    Items:
      metadata.annotations -> annotations
  docker-sock:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/docker.sock
    HostPathType:  Socket
  default-token-hrm5j:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-hrm5j
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     key1=value2:NoSchedule
                 node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s

2 analysis code
It will add tmpl.Tolerations or wfSpec.Tolerations before it create pod, so I understand the second case.
But why the tmpl.Tolerations is nil which expected has toleration key1
//operate-->executeTemplate-->executeContainer-->createWorkflowPod-->addSchedulingConstraints
// addSchedulingConstraints applies any node selectors or affinity rules to the pod, either set in the workflow or the template
func addSchedulingConstraints(pod *apiv1.Pod, wfSpec *wfv1.WorkflowSpec, tmpl *wfv1.Template) {
	...
	// Set tolerations (if specified)
	if len(tmpl.Tolerations) > 0 {
		pod.Spec.Tolerations = tmpl.Tolerations
	} else if len(wfSpec.Tolerations) > 0 {
		pod.Spec.Tolerations = wfSpec.Tolerations
	}
    ...
}

father Template use func resolveTemplateImpl just finds the son Template, it discards some father's field, such as tolerations、Volumes、NodeSelectors and so on.
so when we create the pod of step, it lost the tolerations  seted by steps Template.
func (ctx *Context) resolveTemplateImpl(tmplHolder wfv1.TemplateReferenceHolder, depth int) (*Context, *wfv1.Template, bool, error) {
...
	var tmpl *wfv1.Template
...
	if tmpl != nil {
		ctx.log.Debug("Found stored template")
	} else {
		// Find newly appeared template.
		newTmpl, err := ctx.GetTemplate(tmplHolder)
		if err != nil {
			return nil, nil, false, err
		}
...
		tmpl = newTmpl
	}

	// Update the template base of the context.
	newTmplCtx, err := ctx.WithTemplateHolder(tmplHolder)
	if err != nil {
		return nil, nil, false, err
	}

	// Return a concrete template without digging into it.
	if tmpl.GetType() != wfv1.TemplateTypeUnknown {
		return newTmplCtx, tmpl, templateStored, nil
	}

	// Dig into nested references with new template base.
	finalTmplCtx, resolvedTmpl, templateStoredInCall, err := newTmplCtx.resolveTemplateImpl(tmpl, depth+1)
	if err != nil {
		return nil, nil, false, err
	}
	...
	// Merge the referred template into the original.
	mergedTmpl, err := common.MergeReferredTemplate(tmpl, resolvedTmpl)
	if err != nil {
		return nil, nil, false, err
	}

	return finalTmplCtx, mergedTmpl, templateStored, nil
}

I suggest add some father Template's fields before return son Template.

Can I play this back so I can see if I understand. Do you expect that a pod's tolerations should be inherited from their parent step or DAG? But that is not the case?

Yes，if we have many steps，all the steps have different tolerations but the same container. Now, we can only create may different container Template，because the tolerations  seted for steps Template is unuseful.

@alexec what's your suggestion

Ok. Labelling as enhancement .

@sarabala1979 thinks he has a way to solve this without making code changes. He will comment shortly.

@sarabala1979 Could show your suggestions？

@leileiwan  Sorry for the delay, you can use podspecpatch to pass the parameter to pod spec
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: steps-
spec:
  entrypoint: hello-hello-hello
  templates:
  - name: hello-hello-hello
    steps:
    - - name: hello1
        template: whalesay
        arguments:
          parameters:
          - name: effect
            value: "NoSchedule"
          - name: key
            value: "key1"
          - name: operator
            value: "Equal"
          - name: value
            value: "value1"

      - name: hello2a
        template: whalesay
        arguments:
          parameters:
          - name: effect
            value: "NoSchedule"
          - name: key
            value: "key2"
          - name: operator
            value: "Equal"
          - name: value
            value: "value2"
      - name: hello2b
        template: whalesay
        arguments:
          parameters:
          - name: effect
            value: "NoSchedule"
          - name: key
            value: "key3"
          - name: operator
            value: "Equal"
          - name: value
            value: "value3"

  - name: whalesay
    podSpecPatch: '{"tolerations":[{"effect":"{{inputs.parameters.effect}}","key":"{{inputs.parameters.key}}","operator":"{{inputs.parameters.operator}}","value":"{{inputs.parameters.value}}"}]}'
#    podSpecPatch:
    inputs:
      parameters:
      - name: effect
      - name: key
      - name: operator
      - name: value
    container:
      image: alpine:latest
      command: [sh, -c]
      args: ["echo {{inputs.parameters.effect}}"]

@leileiwan Sorry for the delay, you can use podspecpatch to pass the parameter to pod spec
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: steps-
spec:
  entrypoint: hello-hello-hello
  templates:
  - name: hello-hello-hello
    steps:
    - - name: hello1
        template: whalesay
        arguments:
          parameters:
          - name: effect
            value: "NoSchedule"
          - name: key
            value: "key1"
          - name: operator
            value: "Equal"
          - name: value
            value: "value1"

      - name: hello2a
        template: whalesay
        arguments:
          parameters:
          - name: effect
            value: "NoSchedule"
          - name: key
            value: "key2"
          - name: operator
            value: "Equal"
          - name: value
            value: "value2"
      - name: hello2b
        template: whalesay
        arguments:
          parameters:
          - name: effect
            value: "NoSchedule"
          - name: key
            value: "key3"
          - name: operator
            value: "Equal"
          - name: value
            value: "value3"

  - name: whalesay
    podSpecPatch: '{"tolerations":[{"effect":"{{inputs.parameters.effect}}","key":"{{inputs.parameters.key}}","operator":"{{inputs.parameters.operator}}","value":"{{inputs.parameters.value}}"}]}'
    inputs:
      parameters:
      - name: effect
      - name: key
      - name: operator
      - name: value
    container:
      image: alpine:latest
      command: [sh, -c]
      args: ["echo {{inputs.parameters.effect}}"]

@sarabala1979 thanks for your interesting answer.
I think podSpecPatch is not enough to implement general Inheritance function. your case assumes that all single step using the container has the same number of toleration, but in fact not.
for example:
steps:
-- hello1:

Tolerations1
-- hello2:
Tolerations1
Tolerations2
-- hello3:
Tolerations1
Tolerations2
Tolerations2

@leileiwan above example is passing difference toleration for each step. instead of passing each field as a parameter, we can pass a JSON string to the template


expose Mime::from_extension

this will be useful for an askama integration, and likely other places as well

We probably will want something along the lines of this at some point: https://www.npmjs.com/package/mime-db


Resource Limits

Hi,
The Resource Limits, and Requests in the deployment checks are hard-coded and are currently failing on my environment and are being OOM killed using the requested nginx pods.
Containers:
  deployment-container:
    Container ID:   docker://1877dbf02a13e62f65410980aae380461218175dab76623f879a8b2fcacbd504
    Image:          nginx:1.17.8
    Image ID:       docker-pullable://nginx@sha256:4a50ed86d8c86e35f530d4a168173677a192177eed14146fbb5728b1b3a2d4de
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       OOMKilled
      Exit Code:    137
      Started:      Tue, 31 Mar 2020 11:26:23 +0100
      Finished:     Tue, 31 Mar 2020 11:26:29 +0100
    Ready:          False
    Restart Count:  2
    Limits:
      cpu:     75m
      memory:  75Mi
    Requests:
      cpu:        15m
      memory:     20Mi

I am not sure why this is the case. I tried setting a limit range on the namespace but the deployment.go hard codes them and they are not configurable as far as I can tell.
Is there a way to amend this in configuration, or possible to change them at all ?
Thanks

Hi @PsychoSid!
That's interesting, I don't think we've ever run into that issue yet. It's possible, as we set default resource limits here in the code:  https://github.com/Comcast/kuberhealthy/blob/master/cmd/deployment-check/deployment.go#L45 and we can replace that with env vars so its more configurable on the deployment-check.yaml. @integrii @jonnydawg thoughts?

Interesting -- the resource limits and requests are set to be hard-coded. @joshulyne I think you are right, I think the best way about this is probably parsing some env vars and then passing it over to the nginx container limits and requests.
I can look into making this change later today.

@PsychoSid -  Could it be that the OOM killer is acting aggressively when these deployment pods are scheduled on nodes that are already under heavy memory pressure?

Thanks all for looking into this. Yes it’s likely that more usage on these is causing it. They are small clusters whilst we do some testing for Anthos.

This has been implemented!


Setup coveralls.io code coverage

I set up coveralls in my fork and it looks like coverage is at 76%.


Enable skipped tests as they run and pass as expected

Fixes  #6210

@sahithikkss - are you able to merge or would you like me to do so?

@sahithikkss - are you able to merge or would you like me to do so?

I would not be able to merge. Please do.


Placement of buildings to create

I can pick the buildings I want to create on the build, but I have no way to move them up or down. Is there a way to place, let's say a group of buildings above or to the left and up of where it tries to build it?

I‘ve noticed this scenario for placing the building on the specific position. There is an inconvenient way to do that in the current version:
Step 1: Use the advanced copy and place the first copy on the ground
Step 2: Set position anywhere and change the displacement vector manually
Step 3: Place the second copy in the position you want, and dismantle the first one
It is a general method but is not convenient enough. The operation will be optimized in the future versions. And a fully enhanced position selecting tool is in the plan.
Maybe I will add a temporary solution of the up, down, left, right movement if the position tool take much more time.

How do I go about the second step? I will take a look at it and see if I can figure it out.

A button called "Set Repeat" in the repeat copy panel

Hi cepheidqq,
Have you corrected the issue with placing the copies on a location and be able to set the height without the workaround you sent me last time? I know you updated the version, but I think the issue still persists.
Kind regards,
Oscar Capote
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, October 31, 2020 7:27 AM, cepheidqq<EMAIL_ADDRESS>wrote:

A button called "Set Repeat" in the repeat copy panel
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yes, I'm working on it. It will release when the new input system finish.


Added SHC Operation

Added Smart Health Card reader from shc:/567629095 to the a beautiful json

Hey! This pull request has gotten rather old and that's our fault. This project stopped being actively maintained for a while and it looks like your pull request has started to gather dust. Would you be able to update your branch to the latest version of CyberChef and we'll give it a review?


dummy GK mgmt network

The dummy GK should not deploy mgmt networks/connection points from the vnfd.
The default connection to docker0 in the emulator can be considered as the mgmt network.

see pull request https://github.com/sonata-nfv/son-emu/pull/149

Sure? What happens if a software/script inside the VNF container expects a interface named mgmt?

but the mgmt is an E-LAN connection, which is currently not handled  by the dummy GK,
so the mgmt interface will not work, it seemed an unnecessary inerface...
but ok I agree, in case the 'mgmt' name is expected, it should be there, as described in the vnfd.

closed by https://github.com/sonata-nfv/son-emu/pull/151/commits/8d7557c11dca16cca0edaf77d90b276d1b90e434

Thats true it is not supported yet. But I guess to support E-LAN connections as well in one of our next versions. Should be possible to install SDN rules to connect all ports of a E-LAN to have a simple HUB-like behaviour or not? What do you think?

I guess a simple HUB-like behviour means a flowrule that incoming packets are sent out all the ports of the E-LAN.
Idea to implement once we need E-LANs...

Actually implemented a first shot at an E-LAN network in the dummygatekeeper:
https://github.com/sonata-nfv/son-emu/pull/156/commits/fb6e43a57b60fdfcd643b60c5e53b6df1e65348b
It relies on the learning switch capabilities of the SDN switch in the emulator, so no specific chaining is installed for E-LAN interfaces. They are just connected to the emulator switches.

@stevenvanrossem Great! I would assume this behavior should be fine for all current E-LAN cases we might have in the demo/example services, or not?


Test, build and CI improvements and fixes

This is an assorted bag of fixes and improvements for the build and test infrastructure.
Cc: @ammarfaizi2

Hi @guillemj,
Sorry, it may be too late, but I missed something when reviewing this. I think -g -O2 -Wall -Wextra should be mandatory flags. But when we use CFLAGS=-Werror, they don't get appended.

Related Code
https://github.com/axboe/liburing/blob/b7c779a90a987f7e65405c7985c52212fcf3cb53/src/Makefile#L9-L10
https://github.com/axboe/liburing/blob/b7c779a90a987f7e65405c7985c52212fcf3cb53/test/Makefile#L13-L26

Without CFLAGS, we have -g -O2 -Wall -Wextra here (it's fine).
make V=1

gcc -D_GNU_SOURCE -D__SANE_USERSPACE_TYPES__ -I../src/include/ -include ../config-host.h -g -O2 -Wall -Wextra -Wno-unused-parameter -Wno-sign-compare -Wstringop-overflow=0 -Warray-bounds=0 -o accept accept.c helpers.o -L../src/ -luring
gcc -D_GNU_SOURCE -D__SANE_USERSPACE_TYPES__ -I../src/include/ -include ../config-host.h -g -O2 -Wall -Wextra -Wno-unused-parameter -Wno-sign-compare -Wstringop-overflow=0 -Warray-bounds=0 -o accept-link accept-link.c helpers.o -L../src/ -luring -lpthread
gcc -D_GNU_SOURCE -D__SANE_USERSPACE_TYPES__ -I../src/include/ -include ../config-host.h -g -O2 -Wall -Wextra -Wno-unused-parameter -Wno-sign-compare -Wstringop-overflow=0 -Warray-bounds=0 -o accept-reuse accept-reuse.c helpers.o -L../src/ -luring
gcc -D_GNU_SOURCE -D__SANE_USERSPACE_TYPES__ -I../src/include/ -include ../config-host.h -g -O2 -Wall -Wextra -Wno-unused-parameter -Wno-sign-compare -Wstringop-overflow=0 -Warray-bounds=0 -o accept-test accept-test.c helpers.o -L../src/ -luring

With CFLAGS, we don't have -g -O2 -Wall -Wextra here (it's not fine).
I think we should have them, even when CFLAGS is specified.
make V=1 CFLAGS=-Werror

gcc -D_GNU_SOURCE -D__SANE_USERSPACE_TYPES__ -I../src/include/ -include ../config-host.h -Werror -Wno-unused-parameter -Wno-sign-compare -Wstringop-overflow=0 -Warray-bounds=0 -o helpers.o -c helpers.c
gcc -D_GNU_SOURCE -D__SANE_USERSPACE_TYPES__ -I../src/include/ -include ../config-host.h -Werror -Wno-unused-parameter -Wno-sign-compare -Wstringop-overflow=0 -Warray-bounds=0 -o 232c93d07b74-test 232c93d07b74-test.c helpers.o -L../src/ -luring -lpthread
gcc -D_GNU_SOURCE -D__SANE_USERSPACE_TYPES__ -I../src/include/ -include ../config-host.h -Werror -Wno-unused-parameter -Wno-sign-compare -Wstringop-overflow=0 -Warray-bounds=0 -o 35fa71a030ca-test 35fa71a030ca-test.c helpers.o -L../src/ -luring -lpthread
gcc -D_GNU_SOURCE -D__SANE_USERSPACE_TYPES__ -I../src/include/ -include ../config-host.h -Werror -Wno-unused-parameter -Wno-sign-compare -Wstringop-overflow=0 -Warray-bounds=0 -o 500f9fbadef8-test 500f9fbadef8-test.c helpers.o -L../src/ -luring
gcc -D_GNU_SOURCE -D__SANE_USERSPACE_TYPES__ -I../src/include/ -include ../config-host.h -Werror -Wno-unused-parameter -Wno-sign-compare -Wstringop-overflow=0 -Warray-bounds=0 -o 7ad0e4b2f83c-test 7ad0e4b2f83c-test.c helpers.o -L../src/ -luring

Sorry, it may be too late, but I missed something when reviewing this. I think -g -O2 -Wall -Wextra should be mandatory flags. But when we use CFLAGS=-Werror from command, they don't get appended.

Ah right, missed adapting the GitHub Actions. I don't think all of these should be mandatory TBH, The -g and -O2 seem clearly optional, as you might want to build w/o debugging symbols or w/o optimizations, for debugging purposes, and while later options should override earlier ones, it seems unclean to me to include both. :) Contrary to the various -Wno- which seem required as are dependent on the current code, and would otherwise emit warnings, the -Wall -Wextra seem optional to me, and potentially problematic if the user passes -Werror when using some other compiler, or a newer or older compiler version, which might be part of global compiler flags setting and might need special handling for this specific package.
Will send a MR to fix that.


Rails 4, font-awesome not appearing in production environment

My app is running just fine in development mode, but when I cap deploy to my production environment (EC2, as it happens, though I'm not sure how significant that is), the app can't resolve the font-awesome font. I'm using pretty much as-installed rails environment configurations, and Capistrano recipes. Everything else in the app runs just fine, it's only the font-awesome font that can't be found.
I'm at a bit of a loss to know how to debug this, so any suggestions gratefully received. Relevant extracts from my Gemfile:
font-awesome-rails (<IP_ADDRESS>),
rails (4.0.1)

Happy to provide any other details, but I don't which which ones are relevant and I don't want to waste folks' time by essentially posting the entire project!

In my case had to do rake assets:clean then RAILS_ENV=production bundle exec rake assets:precompile and was all set. Just chiming in for posterity.


 Modified alignment and font size

Suggested changes

Modified alignment of navbar
Decreased Font size of navigation
Decrease size of logo

Screenshot

Closes #34

Can the text on the navbar be bold?

Yeah,sure

done

Thanks for your contribution!


Initial functional package

The initial functional version of the package, with all main functionality present. To be beta tested while buttoning everything up for CRAN requirements

@dhhagan for review when available

@dhhagan -- both the license change and setting a get_data() limit default have been handled. Waiting to hear back from CRAN on how to handle the API key issue


Enhancement: Support other Input streams/devices (Guitar, Microphone etc.)

Disclaimer:
Please go through existing feature requests to avoid creating duplicates. If you found a similar issue please post a comment there. If you are certain your issue is not related to others then create the issue. Obvious ignorance of this rule might get you blocked from posting new issues. Please tick the box below to show that you have followed the guideline.

[x] I have checked for a similar issue and sure it hasn't been reported before.

Description:
Requested initially in #137
Allow users to select an Input device like a Microphone, Line in or Guitar and process the audio.
This would be especially useful once eqMac has more effects like Distortion, Reverb, Compressor etc.
User flow & interface:
There will probably be a tabbed interface on the top of the UI where you can switch between Input / System audio and others.

Just wanted to add my +1 to this feature request.
Right now as far as I can tell there doesn't exist any way on a Mac to boost a mic's level beyond 100%, or to up the bass for faraway microphones. If you built this it would be an absolute game changer for people who need this live -- especially for people auditioning and performing live over Zoom. Like, you maybe have no idea how big this would be.
For context, Webcam Settings is essentially the video equivalent of this -- setting gain levels, color balance, saturation, etc to your live webcam input, and it's been invaluable for live performers. But an audio equivalent has been completely lacking, though it's just as necessary.
And honestly this is less about adding "effects" like reverb. It's mostly just about gain and EQ -- EQ is incredibly important for microphones because distance from a microphone drastically affects EQ, but you can't always be the distance you'd like to be (because you can't have the mic in-frame), so you need up the bass and add gain generally.
So just really really hoping this is something you can make happen. :)
Thanks!


[Testing WIP] Statically register coalesce_struct UDF in Coral-Spark

This PR statically register coalesce_struct UDF in Coral-Spark. The jar containing UDF will be downloaded in org.apache.spark.sql.hive.HiveExternalCatalog#restoreTableMetadata where the view is handled.
This patch is created for early feedback, the integration test within properly environment is in-progress

@ljfgem  I hope this approach looks reasonable based on our previous discussion ?

@autumnust Yeah, it looks good to me.


If 574 fix applet trigger

Task linked: IF-574 Applets - creating trigger in applet editor (both creating new / editing existing) doesnt work


We should have a diagnostic for missing whitespace around C# 6 property syntax

No diagnostic was produced for not having exactly one space between the } and = in the snippet below.
public static PropertySerializer SimpleTypes { get; }= InitializeSimpleTypes();

I suspect there is an existing rule that can be enhanced to handle this C# 6 case rather than creating a new rule, although I'm not sure which rule it would be

SA1003 is used to report spacing violations around '=' so this would be the rule that should be extended

SA1003 already does this according to the definition. You aren't seeing it in Alpha 5 because #665.

How can #665 explain why I'm not seeing it in alpha005 when that only contains changes to tests?
Also I don't see in those tests an instance of my example above. All those are dealing with operators that appear within a method. This appears as a property declaration.

I've added some testcases for auto property initializers to #665.
The SA1003 analyzer is not reporting diagnostics for this case, as already witnessed.
@sharwell Did you close this issue because its basically a duplicate of #665?

@AArnott SA1003 is disabled in the release build because it has no tests, hence having it not report your issue. I closed this as a duplicate of the open request to implement SA1003.

@vweijsters Thanks for adding those tests. Yes, there are known bugs in the implementation of SA1003 which will need to be addressed before we enable it.


OPI Security API Spec and Protobuf

Tracking an initial cut at the OPI Security API. This will at first be IPsec tunnels.

Hi,
Really basic question on this one, why would we define a new protobuf for this as opposed to re-using an existing gRPC based protocol like OpenConfig and defining it in this way?
By leveraging OpenConfig all of the security considerations that have been worked out (mutual TLS, etc.) come for free.  And if there are other configurations that we want to do, we can define all of these using either standard OpenConfig schemas or create our own OPI-specific schemas.

Hi, Really basic question on this one, why would we define a new protobuf for this as opposed to re-using an existing gRPC based protocol like OpenConfig and defining it in this way?
By leveraging OpenConfig all of the security considerations that have been worked out (mutual TLS, etc.) come for free.  And if there are other configurations that we want to do, we can define all of these using either standard OpenConfig schemas or create our own OPI-specific schemas.

Because we have to start somewhere with actual code and protobufs. If you can point me at the OpenConfig IPsec protobufs (I can't find them), I will take a look.

Closed by https://github.com/opiproject/opi-api/pull/59.


How do I add youtube plugin ?

I've tried this:
def formfield_for_dbfield(self, db_field, **kwargs):
        if db_field.name == 'text':
            kwargs['widget'] = AdminTinyMCE(
                attrs={'cols': 80, 'rows': 30},
                mce_attrs={
                    'plugins': 'youtube',
                    'theme': 'advanced'
                })
        return super(ModelAdmin, self).formfield_for_dbfield(db_field, **kwargs)

I see this:

any ideas whats wrong ?
using django-tinymce==2.3.0

Is the youtube plugin installed in the tinymce plugins folder, and is the version of tinymce compatible with the youtube tinymce plugin?
These are the first two things I'd check. It seems to work with my custom plugin and the bbcode plugin


The bot owner is the user who is opening the channel

Subject of the issue
The owner of the bot, the one who reinstalled it, is the one that is opening the incident channel in Slack.
Steps to reproduce
Using the command /hellper_incident in any incident.
Expected behaviour
We have two options, that should be discussed:

The bot user opens the channel
OR
The user that called the close command opens the channel

Actual behaviour
The owner of the bot is opening the channel.
Possible Solution
We need to revise the scopes of our Oauth in the Slack App, one of them should permit the bot to open a channel as itself or as the user that called him.

Fixed by using OAuth Token.


Add .explore() to GeoBox, Geometry, BoundingBox

This PR addresses #125 by adding .explore() methods for interactively plotting Geometry, BoundingBox and GeoBox objects on a Folium map.
This matches the recently added (#104) .odc.explore() functionality for exploring xarray data, and the existing .explore() functionality from GeoPandas. It is intended to allow users to:

Easily verify that the extents/shape of their geometries line up with their expected AOI
Bugfix issues when creating complex Geometries
Visually communicate to beginner users where they are about to load or analyse data

GeoPolygon (no issues with complex geometries including MultiPolygons):

GeoBox (plots data from the existing .outline and .grid_lines methods):

BoundingBox:

Have used the inbuilt resolution functionality of the .geojson() method to densify features prior to plotting to ensure they are represented correctly on the map (following the UI example here: https://github.com/opendatacube/odc-geo/blob/develop/odc/geo/ui.py#L295-L297).

@robbibt let's change :param \**kwargs: to just :param kwargs: and remove disable for anomalous-backslash-in-string. Also if pylint: disable= can be moved from just before function to inside the function, that would be ideal.

Looks good to me! I think Kirill has better experience with this type of code than me, and I trust his feedback here.


Error completions createStreamed : gpt-3.5-turbo-1106

Added
->withStreamHandler(fn (RequestInterface $request): ResponseInterface => $client->send($request, [         'stream' => true ]))
then
$stream = $client->completions()->createStreamed([     'model' => 'gpt-3.5-turbo-1106',     'max_tokens' => 4096,     'temperature' => 0.3, 	'messages' => [ 		[ 			'role' => 'user', 			'content' => "say huwa", 		], 	], 	'stream' => True, ]);
got an error
Fatal error: Uncaught TypeError: {closure}(): Argument #1 ($request) must be of type RequestInterface, Nyholm\Psr7\Request given, called in \vendor\openai-php\client\src\Transporters\HttpTransporter.php on line 92

As the error states, you type definition is wrong:
->withStreamHandler(fn (RequestInterface $request): ResponseInterface => $client->send($request, [ 'stream' => true ]))

As the error states, you type definition is wrong:
->withStreamHandler(fn (RequestInterface $request): ResponseInterface => $client->send($request, [ 'stream' => true ]))

Can you please explain more what your answer means? I'm getting exact same error. All code above is taken from example on project's github front page. What I need to do to solve it?


ci: rename dockerfiles for easier updates

Renames the dockerfiles to avoid needing to change them when updating graalvm versions.

Waiting on merge until @zhumin8 approves.