Dasharo Performance: CPU temperature measure test gets wrong value

Both test cases return:
56.0Â' cannot be converted to a floating point number: ValueError: could not convert string to float: '56.0Â'
Tested on Novacustom nv41 ADL. Branch novacustom-wip.

cpu-temperature_log.zip
Same problem on MSI® PRO Z690-A DDR4
Dasharo v1.1.3

This test needs to be improved and tested on all platforms. Currently, when someone corrects this test for a given platform, it ruins it for another.
VP4650:
'100.0°C)
' cannot be converted to a floating point number: ValueError: could not convert string to float: '100.0°C)\n'

We have something here: https://github.com/Dasharo/open-source-firmware-validation/pull/341
Could be verified on a few different platforms to ensure the proposed solution works fine @BeataZdunczyk


[BUG] Set-PnPSite -NoScriptSite $false does not do anything

Notice
I have a script that makes the following call:
Set-PnPSite -Identity $SiteFullURL -NoScriptSite $false
Later in the script, I try to set a property bag value:
Set-PnPPropertyBagValue -Key "$MYKEY" -Value "$MYVALUE" -Indexed
But I get the following error:       | Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Site might have NoScript enabled, this prevents setting some property bag values.
Expected behavior
I expect it to do what it says in the documentation!
Actual behavior
Jack eff all
Steps to reproduce behavior
What I listed above.  Create a site, enable scripting, try to set a property bag value.
What is the version of the Cmdlet module you are running?
(you can retrieve this by executing Get-Module -Name "PnP.PowerShell" -ListAvailable)
1.11.46 nightly
Which operating system/environment are you running PnP PowerShell on?

[ ] Windows
[ ] Linux
[ X] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

@iloving Is the site "user-created"? You may need to enable a setting via the SharePoint admin center, before running the above PnP cmdlet:
To allow custom script on OneDrive or user-created sites

a) I'm not just some user.  I'm the global admin
b) That setting was enabled a long time ago, and things had been working fine until I updated my PnP module to the latest 1.11.0

@iloving when you say enabled, you mean you've already set it to "Allow users to run custom script on self-service created sites"?

I did have problems with that argument, but I still use:
Set-PnPTenantSite -Connection $newSiteConnection -Url {parameter:h_URL} -DenyAddAndCustomizePages:$true
which works, even with 1.11.0

Here is what I am doing:
PS> New-PnPTenantSite -Url $SiteFullURL -Owner $SiteOwner -Title $SiteTitle -Template $SiteTemplate -TimeZone $TimeZone -RemoveDeletedSite -Wait #this works fine
PS> $Connection = Connect-PnPOnline -Url $SiteFullURL -ReturnConnection -Credentials $Credential
PS> Set-PnPTenantSite -Connection $Connection -Url $SiteFullURL -DenyAddAndCustomizePages:$false #This used to work...
PS> Set-PnPPropertyBagValue -Key "$PropertyKey" -Value "$SiteType" -Indexed
Set-PnPPropertyBagValue: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Site might have NoScript enabled, this prevents setting some property bag values.
PS> Set-PnPSite -Identity $SiteFullURL -NoScriptSite:$false #this never worked
PS> Set-PnPPropertyBagValue -Key "$PropertyKey" -Value "$SiteType" -Indexed
Set-PnPPropertyBagValue: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Site might have NoScript enabled, this prevents setting some property bag values.
This used to work and now it doesn't work anymore.  I don't understand why.

Ok, I have confirmed that this functionality is indeed broken in 1.11.0.  I reverted back to 1.10.0 and my code works perfectly.

@iloving - can you please also pass the -Connection parameter to the failing cmdlet as well and check ? Or maybe remove -ReturnConnection parameter and then remove -Connection parameter from subsequent cmdlets and check ?

Okay, I've uninstalled 1.10.0 and reinstalled 1.11.0.  I don't know what changed from the last time I tried, but suddenly any cmdlet I used but forgot to explicitly provide the $Connection parameter, got very upset and threw an error about missing context.  (For the record, I am very happy about this.  Tracking connections through side-effect changes should never have been permitted in the first place, IMO)
So I've gone through all the code and made sure every command has a -Connection explicitly specified... and now the Set-PnPTenantSite command is working even though I made no changes to it.  So....   🤷♀

@iloving - Have a look at #2071 for an explanation of what changed in 1.11 for the connection.

Ah I see!  Yes, that's wonderful news.  This will definitely clear up a lot of confusion.  TYVM


add new feature Config-Template assignment for apstra_freeform_config_template

Hi,
Currntly terrafrom provider not already assignment config template to system.
if i check in api apstra this example :

SSXOei_RYGUEpTDeAKg : this system id
j0LBK2RzArOx5ulaT6A : this id for template.
if see on apstra freefrom UI, after import device from terrafrom by default config template not assigment:

our use case terraform can be assign template also to device system internal

Prioritizing these features would be easier if we understood your project, timeline, and so forth.
Would you please send an email so we can set up a time to discuss<EMAIL_ADDRESS>

hi, i already email to<EMAIL_ADDRESS>we can discus in detail on call.

Hi there,
You do realize that you do not need to assign config templates to the device to be able to use them. They can be "not assigned" and you can still include them / use them in the devices.  We demonstrated this in the Freeform Labs in cloudlabs.
If you still need it, please explain the use case in detail for us. (Maybe you want to use specific config template for specific devices? in that case you could just name the CT on a per device basis and include them via a %include <devicename_ct.jinja> %)

/api/blueprints/{blueprint_id}/config-templates-assignments


not no curve error

throw  not on curve error, barely could not run in some cpu type.

 Do better:-) Closing for now.


Unexpected behavior when "+" character is included in the request payload

Description:
$title
The following example image 1 shows a case where using character + , a   is added instead of the + and it doesn't return the desired result, thus needs to be encoded to %2B, the result is acquired.
import ballerina/http;

type Dependency readonly & record {|
    string name;
    string hash;
|};

table<Dependency> key(name) dependencies = table [
    {name: "abcd+efgh", hash: "3e658c4207d316bf4df3c87a66caa96bef94d202"},
    {name: "abcd efgh", hash: "3e658c4207d316bf4df3c87a66caa96bef94d202"}
];

service / on new http:Listener(9090) {

    resource function get dependencies(string name) returns Dependency[] {
        return from Dependency dependencies in dependencies
            where dependencies.name == name
            select dependencies;
    }
}

The table dependecies shows 2 values, abcd+efgh and abcd efgh. In the example the real dependency is abcd+efgh and we've used abcd efgh as a 2nd dependency to replicate/explain the behaviour noticed.
Image 1-

Image 2 -

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):
Suggested Labels (optional):
module/http
Suggested Assignees (optional):

There is a similar behavior in post requests as well. If the + character is in the json payload, it gets replaced with an empty string and gets stored in the DB at the backend.

I think this is the correct behavior. When sending a special character as a query parameter it must be encoded accordingly. So when '+' sign is added in the query part of the URL, it is decoded as the ' '. Please refer,
https://stackoverflow.com/questions/2678551/when-should-space-be-encoded-to-plus-or-20
If you want to send the '+' sign, as it is a special character, you have to encode it accordingly as given in Image 2.

Closing the issue as per the above comment. Please reopen if you any concerns.


DCOS-10984: volume mounts

This is a great piece of work and it is actually working (I tested), please consider my comments and 🚢 !

I noticed a few problems:

Adding a volume and then editing it in the JSON editor seems to duplicate the volume in the form.

Adding a volume with the mountPath set to a value, and then removing the volume, leaves the values in the containers.volumeMounts array.

I pushed a minor change regarding the use of FormGroupContainer :)

Regarding the duplication issue that @jfurrow mentioned I'd say that even though that it seems wrong at the first glance it looks like the least error prone attempt to deal with different volume/mount values.

We need to add a few info blocks to the form as the volume section looks highly confusing at the moment...

rebased on https://github.com/dcos/dcos-ui/pull/1528

Could you move Volumes right under the networking tab Networking like on the designs

Could you also match the form styles like the designs please

Fixed here:

Retest this please

I fixed the bug, LGTM 🚀


Use permanent errors in the pipelinerun reconciler

Changes
Instead of returning nil on error during reconcile, if the error
is transient return it, so that the key is requeue. If the error
is permanent return a permanent error, so that the key is not
requeued.
Partially addresses #2474
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
/kind cleanup
/cc @bobcatfish @vdemeester @mattmoor

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

All my feedback is suuuuper minor and I don't think it should block anything.
This is great!!
(side note: the flakiness level of the integration tests is really starting to worry me, im starting to be concerned there might be an actual problem since this is happening so much across so many different tests - ill add something to the productivity working group agenda)
/lgtm
/approve
/meow

/test pull-tekton-pipeline-build-tests

i think something might be really wrong with the integration tests
/test pull-tekton-pipeline-integration-tests

/lgtm

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests


It works fine on etc mordor, but the block cannot be read on etc mainnet.

It works fine on etc mordor, but the block cannot be read on etc mainnet.Can anyone help me analyze the cause?

ipfs_1        | Changing user to ipfs
postgres_1    |
postgres_1    | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_1    |
ipfs_1        | ipfs version 0.10.0
postgres_1    | 2022-08-16 13:43:19.773 UTC [1] LOG:  starting PostgreSQL 14.5 (Debian 14.5-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres_1    | 2022-08-16 13:43:19.774 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
postgres_1    | 2022-08-16 13:43:19.774 UTC [1] LOG:  listening on IPv6 address "::", port 5432
ipfs_1        | Found IPFS fs-repo at /data/ipfs
ipfs_1        | Initializing daemon...
ipfs_1        | go-ipfs version: 0.10.0-64b532f
ipfs_1        | Repo version: 11
ipfs_1        | System version: amd64/linux
ipfs_1        | Golang version: go1.16.7
postgres_1    | 2022-08-16 13:43:20.009 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1    | 2022-08-16 13:43:20.256 UTC [25] LOG:  database system was shut down at 2022-08-16 13:41:46 UTC
postgres_1    | 2022-08-16 13:43:20.293 UTC [1] LOG:  database system is ready to accept connections
ipfs_1        | Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
ipfs_1        | Swarm listening on /ip4/<IP_ADDRESS>/udp/4001/quic
ipfs_1        | Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
ipfs_1        | Swarm listening on /ip4/<IP_ADDRESS>/udp/4001/quic
ipfs_1        | Swarm listening on /p2p-circuit
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/tcp/4001
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/udp/4001/quic
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/tcp/4001
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/udp/4001/quic
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/tcp/4001
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/udp/4001/quic
ipfs_1        | API server listening on /ip4/<IP_ADDRESS>/tcp/5001
ipfs_1        | WebUI: http://<IP_ADDRESS>:5001/webui
ipfs_1        | Gateway (readonly) server listening on /ip4/<IP_ADDRESS>/tcp/8080
ipfs_1        | Daemon is ready
graph-node_1  | Aug 16 13:43:35.025 INFO Graph Node version: 0.27.0 (2022-08-01)
graph-node_1  | Aug 16 13:43:35.025 WARN GRAPH_POI_ACCESS_TOKEN not set; might leak POIs to the public via GraphQL
graph-node_1  | Aug 16 13:43:35.025 INFO Generating configuration from command line arguments
graph-node_1  | Aug 16 13:43:35.025 WARN No fork base URL specified, subgraph forking is disabled
graph-node_1  | Aug 16 13:43:35.025 INFO Starting up
graph-node_1  | Aug 16 13:43:35.025 INFO Trying IPFS node at: http://ipfs:5001/
graph-node_1  | Aug 16 13:43:35.035 INFO Creating transport, capabilities: archive, traces, url: https://www.ethercluster.com/etc, provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:35.036 INFO Successfully connected to IPFS node at: http://ipfs:5001/
graph-node_1  | Aug 16 13:43:36.695 INFO Connecting to Postgres, weight: 1, conn_pool_size: 10, url: postgresql://graph-node:HIDDEN_PASSWORD@postgres:5432/graph-node?sslmode=prefer, pool: main, shard: primary
graph-node_1  | Aug 16 13:43:36.695 INFO Pool successfully connected to Postgres, pool: main, shard: primary, component: Store
graph-node_1  | Aug 16 13:43:36.711 INFO Setting up fdw, pool: main, shard: primary, component: ConnectionPool
graph-node_1  | Aug 16 13:43:36.714 INFO Running migrations, pool: main, shard: primary, component: ConnectionPool
graph-node_1  | Aug 16 13:43:36.716 INFO Migrations finished, pool: main, shard: primary, component: ConnectionPool
graph-node_1  | Aug 16 13:43:36.716 INFO Mapping primary, pool: main, shard: primary, component: ConnectionPool
graph-node_1  | Aug 16 13:43:36.799 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:41.773 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:42.433 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:43.243 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:43.675 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:43.840 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:44.598 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:44.692 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:47.618 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:52.064 WARN Trying again after net_version RPC call failed (attempt #14) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:43:53.564 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:44:04.711 WARN Trying again after net_version RPC call failed (attempt #15) with result Err(failed to deserialize response: data did not match any variant of untagged enum Output), provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:44:06.801 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: etcmainnet-rpc-0
graph-node_1  | Aug 16 13:44:06.808 ERRO No store configured for Ethereum chain etcmainnet; ignoring this chain
graph-node_1  | Aug 16 13:44:06.873 INFO Creating LoadManager in disabled mode, component: LoadManager
graph-node_1  | Aug 16 13:44:06.873 INFO Starting firehose block ingestors with 0 chains []
graph-node_1  | Aug 16 13:44:06.873 INFO Starting firehose block ingestors with 0 chains []
graph-node_1  | Aug 16 13:44:06.873 INFO Starting firehose block ingestors with 0 chains []
graph-node_1  | Aug 16 13:44:06.874 INFO Starting job runner with 4 jobs, component: JobRunner
graph-node_1  | Aug 16 13:44:06.880 INFO Starting JSON-RPC admin server at: http://localhost:8020, component: JsonRpcServer
graph-node_1  | Aug 16 13:44:06.881 INFO Starting GraphQL HTTP server at: http://localhost:8000, component: GraphQLServer
graph-node_1  | Aug 16 13:44:06.881 INFO Starting index node server at: http://localhost:8030, component: IndexNodeServer
graph-node_1  | Aug 16 13:44:06.881 INFO Starting metrics server at: http://localhost:8040, component: MetricsServer
graph-node_1  | Aug 16 13:44:06.881 INFO Starting GraphQL WebSocket server at: ws://localhost:8001, component: SubscriptionServer
graph-node_1  | Aug 16 13:44:06.881 INFO Started all assigned subgraphs, node_id: default, count: 0, component: SubgraphRegistrar

ipfs_1        | Changing user to ipfs
ipfs_1        | ipfs version 0.10.0
ipfs_1        | Found IPFS fs-repo at /data/ipfs
postgres_1    |
postgres_1    | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_1    |
ipfs_1        | Initializing daemon...
ipfs_1        | go-ipfs version: 0.10.0-64b532f
ipfs_1        | Repo version: 11
ipfs_1        | System version: amd64/linux
ipfs_1        | Golang version: go1.16.7
postgres_1    | 2022-08-16 13:55:30.815 UTC [1] LOG:  starting PostgreSQL 14.5 (Debian 14.5-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres_1    | 2022-08-16 13:55:30.815 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
postgres_1    | 2022-08-16 13:55:30.815 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1    | 2022-08-16 13:55:30.964 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1    | 2022-08-16 13:55:31.240 UTC [26] LOG:  database system was shut down at 2022-08-16 13:54:17 UTC
postgres_1    | 2022-08-16 13:55:31.387 UTC [1] LOG:  database system is ready to accept connections
ipfs_1        | Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
ipfs_1        | Swarm listening on /ip4/<IP_ADDRESS>/udp/4001/quic
ipfs_1        | Swarm listening on /ip4/<IP_ADDRESS>/tcp/4001
ipfs_1        | Swarm listening on /ip4/<IP_ADDRESS>/udp/4001/quic
ipfs_1        | Swarm listening on /p2p-circuit
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/udp/48020/quic
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/tcp/4001
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/udp/4001/quic
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/tcp/4001
ipfs_1        | Swarm announcing /ip4/<IP_ADDRESS>/udp/4001/quic
ipfs_1        | API server listening on /ip4/<IP_ADDRESS>/tcp/5001
ipfs_1        | WebUI: http://<IP_ADDRESS>:5001/webui
ipfs_1        | Gateway (readonly) server listening on /ip4/<IP_ADDRESS>/tcp/8080
ipfs_1        | Daemon is ready
graph-node_1  | Aug 16 13:55:39.319 INFO Graph Node version: 0.27.0 (2022-08-01)
graph-node_1  | Aug 16 13:55:39.319 WARN GRAPH_POI_ACCESS_TOKEN not set; might leak POIs to the public via GraphQL
graph-node_1  | Aug 16 13:55:39.319 INFO Generating configuration from command line arguments
graph-node_1  | Aug 16 13:55:39.319 WARN No fork base URL specified, subgraph forking is disabled
graph-node_1  | Aug 16 13:55:39.319 INFO Starting up
graph-node_1  | Aug 16 13:55:39.319 INFO Trying IPFS node at: http://ipfs:5001/
graph-node_1  | Aug 16 13:55:39.328 INFO Creating transport, capabilities: archive, traces, url: https://www.ethercluster.com/mordor, provider: etcmordor-rpc-0
graph-node_1  | Aug 16 13:55:39.330 INFO Successfully connected to IPFS node at: http://ipfs:5001/
graph-node_1  | Aug 16 13:55:40.738 INFO Connecting to Postgres, weight: 1, conn_pool_size: 10, url: postgresql://graph-node:HIDDEN_PASSWORD@postgres:5432/graph-node?sslmode=prefer, pool: main, shard: primary
graph-node_1  | Aug 16 13:55:40.739 INFO Pool successfully connected to Postgres, pool: main, shard: primary, component: Store
graph-node_1  | Aug 16 13:55:40.756 INFO Setting up fdw, pool: main, shard: primary, component: ConnectionPool
graph-node_1  | Aug 16 13:55:40.758 INFO Running migrations, pool: main, shard: primary, component: ConnectionPool
graph-node_1  | Aug 16 13:55:40.765 INFO Migrations finished, pool: main, shard: primary, component: ConnectionPool
graph-node_1  | Aug 16 13:55:40.766 INFO Mapping primary, pool: main, shard: primary, component: ConnectionPool
graph-node_1  | Aug 16 13:55:40.847 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: etcmordor-rpc-0
graph-node_1  | Aug 16 13:55:41.699 INFO Connected to Ethereum, capabilities: archive, traces, network_version: 7, provider: etcmordor-rpc-0
graph-node_1  | Aug 16 13:55:42.070 INFO Creating LoadManager in disabled mode, component: LoadManager
graph-node_1  | Aug 16 13:55:42.070 INFO Starting block ingestors with 1 chains [etcmordor]
graph-node_1  | Aug 16 13:55:42.070 INFO Starting block ingestor for network, network_name: etcmordor
graph-node_1  | Aug 16 13:55:42.071 INFO Starting firehose block ingestors with 0 chains []
graph-node_1  | Aug 16 13:55:42.071 INFO Starting firehose block ingestors with 0 chains []
graph-node_1  | Aug 16 13:55:42.071 INFO Starting firehose block ingestors with 0 chains []
graph-node_1  | Aug 16 13:55:42.071 INFO Starting job runner with 4 jobs, component: JobRunner
graph-node_1  | Aug 16 13:55:42.076 INFO Starting JSON-RPC admin server at: http://localhost:8020, component: JsonRpcServer
graph-node_1  | Aug 16 13:55:42.077 INFO Starting GraphQL HTTP server at: http://localhost:8000, component: GraphQLServer
graph-node_1  | Aug 16 13:55:42.078 INFO Starting index node server at: http://localhost:8030, component: IndexNodeServer
graph-node_1  | Aug 16 13:55:42.078 INFO Started all assigned subgraphs, node_id: default, count: 0, component: SubgraphRegistrar
graph-node_1  | Aug 16 13:55:42.078 INFO Starting metrics server at: http://localhost:8040, component: MetricsServer
graph-node_1  | Aug 16 13:55:42.078 INFO Starting GraphQL WebSocket server at: ws://localhost:8001, component: SubscriptionServer
graph-node_1  | Aug 16 13:55:42.425 INFO Downloading latest blocks from Ethereum, this may take a few minutes..., provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:57:42.209 INFO Syncing 10 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 10, blocks_behind: 10, latest_block_head: 6973666, current_block_head: 6973656, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:57:49.274 INFO Syncing 2 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 2, blocks_behind: 2, latest_block_head: 6973668, current_block_head: 6973666, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:58:05.022 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973669, current_block_head: 6973668, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:58:11.752 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973670, current_block_head: 6973669, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:58:27.798 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973671, current_block_head: 6973670, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:58:30.027 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973672, current_block_head: 6973671, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:58:44.396 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973673, current_block_head: 6973672, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:58:54.883 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973674, current_block_head: 6973673, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:59:01.061 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973675, current_block_head: 6973674, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:59:09.197 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973676, current_block_head: 6973675, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:59:13.320 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973677, current_block_head: 6973676, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:59:23.355 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973678, current_block_head: 6973677, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:59:30.276 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973679, current_block_head: 6973678, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:59:40.691 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973680, current_block_head: 6973679, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 13:59:50.929 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973681, current_block_head: 6973680, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 14:00:05.654 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973682, current_block_head: 6973681, provider: etcmordor-rpc-0, component: BlockIngestor
graph-node_1  | Aug 16 14:00:20.313 INFO Syncing 1 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 6973683, current_block_head: 6973682, provider: etcmordor-rpc-0, component: BlockIngestor


Doest aiXcoder-7B support Rust?

RT

Hey, aiXcoder-7B supports Rust completion, welcome to try it out, and look forward to your valuable experience in your daily work.


Ability to customize retrolab interface

Problem

I'm running retrolab on a computer where the user cannot run terminals (it's an iPad). To avoid user confusion, I would like the ability to remove the "New Terminal" button (and "New Console", too). In Jupyterlab, setting terminals_enabled to False will remove the "New Terminal" button in the Launcher tab. I haven't found a similar feature in retrolab (I think it's because the buttons are generated directly in Javascript, which makes a very compact system, at the expanse of customization).
Proposed Solution

I would like to suggest introducing a way to disable individual buttons in the interface. Possibly through a variable, that the user could set in a configuration file?
Additional context
Current user interface:

Desired user interface (after customization):

Well I'll be damned! It works! I'm in awe.
For a more permanent solution, I ended up creating the config file Library/etc/jupyter/labconfig/page_config.json, which contains:
{
  "disabledExtensions": {
    "@retrolab/tree-extension:new-console": true,
    "@retrolab/tree-extension:new-terminal": true
  }
}

(which is the same, but stored as settings). Thank you so much!
While we're on the topic of customization, is there a way to add extra buttons to the top toolbar for a notebook? I would need two extra buttons to account for the specificities of iOS.

which is the same, but stored as settings

Yes that also works.

While we're on the topic of customization, is there a way to add extra buttons to the top toolbar for a notebook? I would need two extra buttons to account for the specificities of iOS.

Yes this is possible via an extension: https://jupyterlab.readthedocs.io/en/latest/extension/notebook.html#adding-a-button-to-the-toolbar. There is an example in the extension examples repo: https://github.com/jupyterlab/extension-examples/tree/master/toolbar-button

Closing as fixed by https://github.com/jupyter/notebook/pull/6336
In the next Notebook v7 pre-release it will be possible to more easily customize the file browser toolbar items via the settings system, just like in JupyterLab.
@holzschu feel free to open new issues in the notebook directly if you think this needs to be iterated on more. Thanks!


GitHub Sync

This is an automatically generated pull request.

Forcing merge. Will fix ahead if necessary.


ERROR: torch-1.13.1-cp38-none-macosx_11_0_arm64.whl is not a supported wheel on this platform

I'm running the mnist test script on an mac M1. Without GPU.
Agent comand: clearml-agent daemon --queue default --cpu-only
Error during requirements installation
Why does it happen, how can I solve this problem?
My logs:
Log - 609a78a54534461a888614044dee9604 (2).txt

Hi @skyandd,
Notice that it is using python3.8 - you can see the list of wheels here:
https://pypi.org/project/torch/#files
Are you sure you are running macosx 11+?
If you were to install it manually would that work? Because it seems it located the correct wheel and package

I am using macosx 12.3
Yes, sure, I have local env and it's working well.
I did another experiment. Made a dependency freeze, pushed and launched a new experiment
Log - 1cefa16992d7426bb770ca2ca54f0453.txt

Can you install torch-1.13.1-cp38-none-macosx_11_0_arm64.whl manually?
Could you also provide the full pip freeze for your working python environment, including the python version?

Yes, I can. Manually it is install.
requirements.txt
(venv) (base) anton@MacBook-Pro-Anton clear_ml % python
Python 3.8.9 (default, Apr 13 2022, 08:48:06)
[Clang 13.1.6 (clang-13<IP_ADDRESS>.5)] on darwin

@jkhenning https://clearml.slack.com/archives/CTK20V944/p1673521998776139
In parallel, I wrote in slack and followed the advice from the comments. It worked. Added a block from the image to coreml.conf and this solved the problem.


Release v2.11.1

This release updates Idle app to use v4 contracts and Sablier app to add mUSD token

Travis automatic deployment:
https://pr1366--safereact.review.gnosisdev.com/app

@francovenica already checked the changes in this PR.
I had a conversation with him while doing the testing.
Had to close fast because we need it to be deployed today


Made all private methods/fields protected

Users may want to modify some behaviour of the library in sub classes. Making the inner workings accessible make that easier.
Eg. in my case I needed to modify the getDomainPath() method.

👍 but I agree with #25 close this and merge #25 since #25 has this in it.

Done


Spike on which Youtube Api is most relevant to project

The Youtube Analytics Api is very useful for information on channels and videos, such as views, ad revenue, etc.

The Youtube data api is useful for allowing users to  search YouTube content, upload videos, create and manage playlists, and more.

The Youtube iframa api can be used to allows users to watch youtube videos on my website.


404 not found

I have the latest version of Lumen 5.8 and installed the library but i am getting the following error
[HTTP/1.1 404 Not Found 4ms]

app.php
<?php

require_once __DIR__.'/../vendor/autoload.php';

(new Laravel\Lumen\Bootstrap\LoadEnvironmentVariables(
    dirname(__DIR__)
))->bootstrap();

/*
|--------------------------------------------------------------------------
| Create The Application
|--------------------------------------------------------------------------
|
| Here we will load the environment and create the application instance
| that serves as the central piece of this framework. We'll use this
| application as an "IoC" container and router for this framework.
|
*/

$app = new Laravel\Lumen\Application(
    dirname(__DIR__)
);

// $app->withFacades();

// $app->withEloquent();

/*
|--------------------------------------------------------------------------
| Register Container Bindings
|--------------------------------------------------------------------------
|
| Now we will register a few bindings in the service container. We will
| register the exception handler and the console kernel. You may add
| your own bindings here if you like or you can make another file.
|
*/

$app->singleton(
    Illuminate\Contracts\Debug\ExceptionHandler::class,
    App\Exceptions\Handler::class
);

$app->singleton(
    Illuminate\Contracts\Console\Kernel::class,
    App\Console\Kernel::class
);

/*
|--------------------------------------------------------------------------
| Register Middleware
|--------------------------------------------------------------------------
|
| Next, we will register the middleware with the application. These can
| be global middleware that run before and after each request into a
| route or middleware that'll be assigned to some specific routes.
|
*/

/*
|--------------------------------------------------------------------------
| Register Service Providers
|--------------------------------------------------------------------------
|
| Here we will register all of the application's service providers which
| are used to bind services into the container. Service providers are
| totally optional, so you are not required to uncomment this line.
|
*/

// $app->register(App\Providers\AppServiceProvider::class);
// $app->register(App\Providers\AuthServiceProvider::class);
// $app->register(App\Providers\EventServiceProvider::class);

/*
|--------------------------------------------------------------------------
| Load The Application Routes
|--------------------------------------------------------------------------
|
| Next we will include the routes file so that they can all be added to
| the application. This will provide all of the URLs the application
| can respond to, as well as the controllers that may handle them.
|
*/

$app->configure('cors');

$app->register(Barryvdh\Cors\ServiceProvider::class);

$app->middleware([
    // ...
    \Barryvdh\Cors\HandleCors::class,
]);

$app->router->group([
    'namespace' => 'App\Http\Controllers',
], function ($router) {
    require __DIR__.'/../routes/web.php';
});

return $app;

routes web.php
<?php

/*
|--------------------------------------------------------------------------
| Application Routes
|--------------------------------------------------------------------------
|
| Here is where you can register all of the routes for an application.
| It is a breeze. Simply tell Lumen the URIs it should respond to
| and give it the Closure to call when that URI is requested.
|
*/

$router->get('/', function () use ($router) {
    return $router->app->version();
});

$router->post('/api/stripe', 'StripeController@update');

This would probably a easy solve

I'm closing this due to inactivity. If this issue is still relevant on the latest version (2.0.1 at the moment), please open a new issue with detailed information.


update any instance of address validation to use InputAddress

Description
We have several places in our app where we have an input for FLOW addresses which we want to validate against the FLOW blockchain and sometimes run additional validation logic on it. This PR moves all those custom <input> to use our shared <InputAddress> so styling is consistent and to minimize places to update.
Demo / Test Result

Everything looks good, although I noticed that on your branch i'm unable to click Create Safe, despite having the required fields populated.

Everything looks good, although I noticed that on your branch i'm unable to click Create Safe, despite having the required fields populated.

Small bug, should be updated now!


build: port set_utils and dependency_utils from oiio cmake scripts

For those who didn't see this get added in OIIO land a few months back, the highlights are:

Variable setting utilities, including replacements/wrappers for set(CACHE) and option() that have a few extra bells and whistles, including that they allow environment variables of the same name to override the default values.

An end-of-config dependency report that prints which dependencies were found and their versions, which were found but were too old, which were missing.

The skeleton of an automatic local dependency build facility.  The short story is that if a dependency is not found or is too old AND it can find a file called src/cmake/build_PACKAGE.cmake, it will run that file and expect it to download and build the dependency on the fly. I haven't added any of those scripts here yet, but on the OIIO side we already have a few to build certain critical dependencies. Future PRs to OSL will also add the missing pieces to build the dependencies.

Here's what the "dependency report" looks like in the CI logs, which is immensely helpful:
-- =========================================================================
-- = Dependency report                                                     =
-- =========================================================================
--
-- The following dependencies were found externally:
--     BISON 3.0.4
--     FLEX 2.6.1
--     LLVM 15.0.7
--     OpenEXR 3.1.11
--     OpenImageIO <IP_ADDRESS>
--     pugixml 1.11
--     Python 3.10.11
--     Qt5 5.15.9
--     ZLIB 1.2.11
-- The following dependencies were not found:
--     Qt6
--
-- =========================================================================
--

As soon as this little organizational change is reviewed and merged, right on top of that I will have PRs that at long last bump our C++, Python, and Imath requirements.

No objections -> merging


Still Move Crazy

I were tested on your project. Try to pull top left corner to center faster and faster. It will appear 2 arrow top and left and not scroll back.

Hi and sorry for the delay. Did you figure it out already? If you compile this project everything should be fine, it's how I tested it.

Yes, I run into the same problem also where it can get stuck in a diagonal scroll

Exciting Job Opportunity at Microsoft!
Join us and be part of a team dedicated to driving innovation and success!
How to Apply:
To apply for this exciting opportunity, please click here.
Job Description:

Position: Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan
Company-contributed retirement plan
Flexible working hours
Collaborative and inclusive work environment

Requirements:

Proven experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Familiarity with frameworks such as React, Angular, or Vue.js
Problem-solving skills and ability to work in a team

Note: This position is open to candidates from anywhere in the world.t-aburasoba, @Jae-eun, @j178, @YixuanFranco, @amielucha, @Thisdick69, @ngoct47449, @martinraag, @wujun, @nhuttrung, @kcnickerson, @y-harikita, @gemasergey, @fishlerd, @yzhaoyu, @danparamov, @hennersz, @xzhangRepo, @TraderWithPython, @adamyarger


fix contractor.IsOffline

Previously, the contractor's IsOffline method would report that contracts that did not exist in the contractor database were online.

I think the rationale here was to avoid punishing a host if we don't actually have any records. It made a little more sense when (IIRC) IsOffline took a host pubkey as an argument instead of a contract ID. But yeah, if the contract doesn't exist, something's definitely wrong.

We've also added a few other protections related to resetting the hostdb

LGTM


sveltekit:prefetch potentially loads a wrong page when an anchor link is involved

Describe the bug
When using a link with sveltekit:prefetch that contains an anchor-link e.g. '/blog#modal' the page gets requested on hover, which is the intended behaviour.
But if you then decide to not click on that link and visit the same page without the anchor-link /blog you will see the contents of the link you hovered before.
In this implementation the onMount hook accesses the $page store which holds a wrong value.
I would assume when using prefetch sveltekit only loads the necessary load functions and components.
The $page store should get updated when you actually click on the link.
Reproduction
Here is the link to a Repo showing the issue: https://stackblitz.com/edit/sveltejs-kit-template-default-uubxoo

load the homepage
hover over one of the last two links
click the first link

You should see that the page was loaded with some content that belongs to the other links
Logs
No response
System Info
System:
    OS: Windows 10 10.0.22000
    CPU: (12) x64 Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz
    Memory: 16.90 GB / 31.73 GB
  Binaries:
    Node: 16.13.2 - ~\AppData\Local\Volta\tools\image\node\16.13.2\node.EXE
    Yarn: 1.22.17 - ~\AppData\Local\Volta\tools\image\yarn\1.22.17\bin\yarn.CMD
    npm: 8.1.2 - ~\AppData\Local\Volta\tools\image\node\16.13.2\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (100.0.1185.50), ChromiumDev (99.0.1141.0)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.37
    @sveltejs/kit: next => 1.0.0-next.320
    svelte: ^3.46.0 => 3.47.0

Severity
serious, but I can work around it
Additional Information
No response

@Rich-Harris
Created #4773 as this seems extremely straightforward. Feel free to toss it or provide feedback if the solution doesn't cover all of the edge cases -- though I think it's fine!


Can't get plugin to start

Describe Your Problem:

Installed plugin and edited config.json accordingly.  When I launch Homebridge, it doesn't seem to load the plugin and I get the following error:
[4/22/2020, 08:59:53] Error: The requested platform 'config' was not registered by any plugin.
    at API.platform (/usr/lib/node_modules/homebridge/lib/api.js:134:13)
    at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:327:45)
    at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:90:36)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:59:10)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:1156:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
    at Module.load (internal/modules/cjs/loader.js:1000:32)
    at Function.Module._load (internal/modules/cjs/loader.js:899:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
    at internal/main/run_main_module.js:18:47
[4/22/2020, 08:59:54] Got SIGTERM, shutting down Homebridge...

Logs:

Show the Homebridge / Homebridge Config UI X logs here.

Homebridge Config:

"platforms": [
    {
      "platform": "config",
      "name": "Config",
      "port": 8080,
      "sudo": false
    }
]

Screenshots:

Environment:

Node.js Version:
v12.16.2

NPM Version:
6.14.4

Homebridge Version:
0.4.53

Homebridge Config UI X Version:

Operating System: Raspbian / Ubuntu / Debian / Windows / macOS / Docker / other
Raspbian Jesse

Process Supervisor: Docker / Systemd / init.d / pm2 / launchctl / hb-service / other / none
none

Your logs suggest the UI was not installed; or you have multiple copies of Node.js running which is causing strange things to happen.
sudo npm install -g --unsafe-perm homebridge-config-ui-x

Thanks for replying!
That's how I installed the plugin originally.  Ran the command again - this is the output:
pi@study:~/.homebridge $ sudo kill 11176
[4/22/2020, 09:34:23] Got SIGTERM, shutting down Homebridge...
pi@study:~/.homebridge $ sudo npm install -g --unsafe-perm homebridge-config-ui-x
/usr/local/bin/homebridge-config-ui-x -> /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
/usr/local/bin/hb-service -> /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/hb-service.js
+<EMAIL_ADDRESS>updated 1 package in 136.633s
[1]+  Exit 143                homebridge -U /home/pi/.homebridge
pi@study:~/.homebridge $

Still the same error I'm afraid:
[4/22/2020, 09:40:17] Error: The requested platform 'config' was not registered by any plugin.
    at API.platform (/usr/lib/node_modules/homebridge/lib/api.js:134:13)
    at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:327:45)
    at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:90:36)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:59:10)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:1156:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
    at Module.load (internal/modules/cjs/loader.js:1000:32)
    at Function.Module._load (internal/modules/cjs/loader.js:899:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
    at internal/main/run_main_module.js:18:47

Anything else I can try?
Do I need hb-service to be running?

It looks like you have a copy of node at two locations:
/usr/bin/node and /usr/local/bin/node.
It
Might be easier if you message me on the Homebridge Discord, then I can walk you through fixing everything up.

I just wrote this guide up, as I've had a few similar issues recently as people upgrade their old installs.
https://github.com/homebridge/homebridge/wiki/How-To-Fix-Node.js-Install-Issues-On-Linux


Release a new version

The last release was 1.0.3 almost a year ago. There have a been a number of changes since then:
https://github.com/google/google-authenticator-libpam/compare/1.03...master
Could you  please make a new release?

Seems like a good idea. Done.

Thank you!


fix(rule): add i18n test with pural

Closes #504

I'm not sure of my fix. Seems to be doing the job.


Add .Net Standard 2.0 target

According to Open-source library guidance it would be good to target .Net Standard 2.0 to benefit from having a smaller package graph.
I would appreciate to help with it.

We'd then loose targetting older versions of .net

That could be an option then. Happy to take a PR especially if it's a quick one.
I think the reason why I dropped back to netstandard 1.6 at the time was for net core 1.0 support. It's probably fine to drop support for that now.
https://docs.microsoft.com/en-us/dotnet/standard/net-standard

https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/cross-platform-targeting
“❌ AVOID including a netstandard1.x target
.NET Standard 1.x is distributed as a granular set of NuGet packages, which creates a large package dependency graph and results in developers downloading a lot of packages when building. Modern .NET platforms, including .NET Framework 4.6.1, UWP and Xamarin, all support .NET Standard 2.0. You should only target .NET Standard 1.x if you specifically need to target an older platform.”


Update index.mdx

added a link to env var reference page

The page you added a link to does not have specific details about "environment variables".
I would suggest an admonition that mentions that there is a reference of environment variables that can be used to influence and configure Prisma (CLI, Client, Studio etc.).


boards: shields: frdm_kw41z: Fix reference to undefined Kconfig symbol

Fixes a reference to a now undefined Kconfig symbol in the frdm_kw41z
shield document.
Signed-off-by: Maureen Helm<EMAIL_ADDRESS>Partial fix for #12144

Codecov Report

Merging #13333 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13333   +/-   ##
=======================================
  Coverage   48.76%   48.76%
=======================================
  Files         319      319
  Lines       46892    46892
  Branches    10840    10840
=======================================
  Hits        22867    22867
  Misses      19391    19391
  Partials     4634     4634

Continue to review full report at Codecov.

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


About page

stats
app links

Well I don't know really, where it should point to, it's just mistake haha

@krystofex could you please revisit this PR and take a look at @bigint's comments? Also, please, as per my comment remove the pointer cursor.

A bit sus @krystofex

@krystofex are you still going to work on this or should I close this and implement it later?

I can finish it


Configure base URL + use source URL from same host

Hi there,
In our current implementation of imgproxy (using helm), we're setting IMGPROXY_BASE_URL. We'd like to start serving images from S3 in conjunction with images on a legacy server (which is our current base URL e.g. https://my-legacy-server.com).
The first step of this change would be to remove our base URL configuration, and start passing fully qualified source URLs to imgproxy (e.g. /plain/https://my-legacy-server.com/images/test.jpg). But obviously it's hard to do this without breaking our images between deployments, because you can't have a base URL configured and pass in a fully qualified source URL at the same time.
It would be nice if you could have both at the same time, if the hostname of the source URL matches your base URL. What do you think?

Hi Joel,
Sorry for the late response.
I'm preparing the 3rd version of imgproxy so v2 is kind of feature-freezed now. I could add this feature to v3 but I don't think you can wait for its release.
Since you need this functionality for a short time only, I'd recommend using a fork. The patch is really simple, you should add the following lines before this one https://github.com/imgproxy/imgproxy/blob/master/processing_options.go#L358
if strings.HasPrefix(unescaped, conf.BaseURL) {
	return unescaped, format, nil
}

@jebax I had to make a release, so I added this feature to v2.17.0


Change lock screen logo and ensure correct contrast

Bug Report
The Java_Suite and iOS lock screen logos are currently different. The Java_Suite logo should change to align with the iOS logo (attached). Additionally, the iOS library does contrast checking against the background color of the lock screen to flip the logo color between white and black. The Java_Suite library should do the same thing.

Reproduction Steps

[Step 1]
[Step 2]
[Step 3]

Expected Behavior
[Some expected behavior]
Observed Behavior
[Some observed behavior]
OS & Version Information

Android Version: [What version of Android are you using when the bug occurred]
SDL Android Version: [What version of the library has this bug been seen on]
Testing Against: [What you tested with to observe this behavior]

Test Case, Sample Code, and / or Example App
[Paste a link to a PR, gist, or other code that exemplifies this behavior]

closed by PR #1355


Update generate_data progress bar more regularly

The progress bar in generate_data only updates once, whereas the generate_phsp bar does update regularly:
Generating phase space sample: 22it [00:00, 22.95it/s]
Generating intensity-based sample:   0%|                                                                                | 0/0.6 [00:00<?, ?it/s]
.../site-packages/tqdm/std.py:522: TqdmWarning: clamping frac to range [0, 1]
  full_bar = Bar(
Generating intensity-based sample: 16it [00:12,  1.29it/s]

Closed by #151


Card onClick for container

https://github.com/yandex-cloud/uikit/blob/bd52a232dbcf913d5101a45ce5bed01873a46a69/src/components/Card/Card.tsx#L18
Hi, I have encountered some problems implementing onCLick of Card. It seems it is explicitly disabled. But our design says todo a container type Card with click handler.
Is there any way we could enable click handler for container type?

Waiting design for hover/active states

For actions we have type action. Not planning add click handler on other types. Feel free to reopen for further discussion


Rollbar.error has less context than uncaught exceptions

Uncaught exceptions in Rails are reported to rollbar with stacktrace and context such as request parameters.
However if we replace :
may_raise_exception()

by
begin
  may_raise_exception()
rescue TheExceptionClass => error
  return if should_fail_silently(error) # sometimes the exception should not be raised
  Rollbar.error(error)
end

I noticed a loss of context, I no longer have request param for example. I still have the proper stacktrace though so the part of the doc I read did not really helped me and I was wondering if it was a known issue and if there was something I could do to keep the maximum amount of context.

I am also interested

Hi all, I haven't been able to reproduce this. When calling Rollbar methods with the default Rollbar instance, during the request lifecycle, the request context does get added to the request. If anyone has details that might help reproduce this, I'll try it.
In case it's helpful, here is some background on how the request context is added.
This is implemented in rollbar-gem using scopes. https://docs.rollbar.com/docs/ruby#the-scope
The initialization of the scope that is used with uncaught exceptions is here: https://github.com/rollbar/rollbar-gem/blob/master/lib/rollbar/middleware/rails/rollbar.rb#L20-L22
That scope, containing the request and context, is added to the default Rollbar instance, and should be available for payloads anywhere Rollbar.log, Rollbar.error, etc. are called using the default Rollbar instance during the execution of the request. This also works when sending messages with no exception, e.g. Rollbar.info('Test message').
Exceptions to this:
The scope is set when entering the Rollbar middleware (request path) and removed when exiting (response path). Outside of this, the scope is cleared. This should work as expected for any Rollbar calls during the request lifecycle, but will be empty after the response is sent.
If multiple Rollbar instances are created, they will inherit the current scope of the parent instance at the time they are created, but their scope will not be updated later when the default instance is updated. Generally, their scope will not be automatically updated with each new incoming request.
Some job queues (Sidekiq, DelayedJob) have plugins that add their own scope. These are typically not executing during the request, though some senders have a synchronous option.

Ok, I could not reproduce by directly putting this code in a controller, however I could reproduce when putting it in a sidekiq::job. I do not event need to be in a rescue, if I create a job directly calling Rollbar.error, I loose context such as the name of the job or the parameters it was called with.


lock the rest of the mounts behind traits

[ ] Ampithere (busted af, lock behind something high tier)
[ ] Dragon
[ ] Horse(?)
[ ] Hippogryph
[ ] Hippocampus
[ ] Tier 1 Dinos
[ ] Tier 2 Dinos

we could use incontrol to set the mob default speed to stop the busted AF mobs. I find a lot of the flying mounts have ridonculous speeds anyway and don't really offer a great exprience in any context

also added tame-locking for some mobs. will deal with amphithere speed in another release.


Unexpected behaviour when using no-restricted-paths

I want a certain directory to only be able to import from one other directory or child directories.
I have the following config:
    "import/no-restricted-paths": ["warn", {
      "zones": [
        {
          "target": "./src/blah/scripts/*",
          "from": "./src/**",
          "except": [
            "**/src/sdk/*",
            "**/src/blah/scripts/**/*"
          ],
          "message": "Scripts must only use the \"sdk\" module."
        }
      ]
    }],

I wouldn't expect to need the ** at the front of the except rules.
Am I doing something wrong?

What happens if you omit the **/ part?

The message is show even for the excepted paths

Is there any chance you could set up a repro repo? That would help a lot.

I have the same problem
have a look at the repo
I nave commented the rule - uncomment it for you


Request/Response pair not saved for promoted findings

Bug description
similar to #7015 , this time for findings that are promoted (from potential findings to findings).
When a potential finding is promoted to 'finding', anything that is written in request/response pairs is not saved.
Steps to reproduce
Steps to reproduce the behavior:

Go to a test and create a Potential Finding
Promote it to "finding"
Enter any text in REQUEST and/or RESPONSE fields
Save the Finding
view the finding and observe those fields (request/response) were not saved and are empty.

Expected behavior
Request/response fields should be saved
Deployment method (select with an X)

[ x] Docker Compose
[ ] Kubernetes
[ ] GoDojo

Environment information

Operating System: Debian
DefectDojo version (see footer) or commit message: 2.23.2

Logs
NA
Sample scan files
NA
Screenshots
NA
Additional context (optional)
Add any other context about the problem here.

Could you also try this with the latest Version please?


vuejs.org documentation for filter

Reproduction link
https://012.vuejs.org/guide/custom-filter.html
This is my top google hit when I search for vue.js custom filter.
What is expected?
Documentation should have version number.
The two way filter guide is not working/depricated, should be labeled removed/depricated/replaced and link to solution in documentation
(remove or indicate old/outdated documentation)
What is actually happening?
The two way filter guide is not working
On the link provided, the only thing nearly indicating any version number is the text: "Looking for 0.11 docs.

Hm, a couple (not mutually exclusive) options come to mind. We could:

Add a banner to all previous versions of the docs, making it clearer that it does not refer to the most recent version of Vue.
Somehow tweak the SEO so that older docs will only show up in search results when that specific version number is included in the search. Not sure if this is possible. 😕
Add noindex to all previous versions of the docs. This would be pretty extreme, so I probably don't see it happening.

Btw I found 6 legacy docs in different versions & languages:

https://011.vuejs.org
https://012.vuejs.org
https://012-cn.vuejs.org
https://v1.vuejs.org
https://v1-cn.vuejs.org
https://v1-jp.vuejs.org

We should do the same thing to all of them if any action decided.
Thanks.

Easy and effective implementation as @chrisvfritz commented: some kind of indication/banner that this documentation is obsolete and a referance to updated/current version. Frustrating to spend time on an implementation, to later find out that the implementation is outdated/not working.

Sorry for the delay. Just created a script that will inject a small notification on the pages where it is included. I will be adding PRs to the places mentioned by @Jinjiang over the next few days.
<EMAIL_ADDRESS>

This has now been fixed. 🙂 Thanks @shentao!!

At last 😞


allow load on Xcode 8+ not working

if you close the app and open again the option gets unchecked and afloat(only plugin I'm using) is not loading in Xcode 9.

This option has been removed and replaced with an AMFI toggle and some info about that.


tests: Add tests for issue 3490

This PR adds test cases for the issues identified in 3490
Companion Suricata PR

Merged after rebase, thanks Jeff.


[ENHANCEMENT] Seamless upgrade for vm-dhcp-agent

Is your enhancement related to a problem? Please describe.

No matter what means are used to upgrade vm-dhcp-controller, either doing it via Helm or manually updating the image tag, there are no mechanisms to roll out the upgrade for agents. The result is the inconsistency of controllers and agents. We need a more robust operator pattern.
Describe the solution you'd like

Add additional fields in the pod-reference struct to record the current version of the running agents. Reconcile the information and the running Pod.
Describe alternatives you've considered

N/A
Additional context

Manually removing the agent Pods will cause the controller to recreate them in the new version. This could be the workaround at the moment.

Create Harvester test environment based on Vagrant from ipxe-examples repo.

3 nodes
500GiB virtio root drive

Built images and deployed harvester-vm-dhcp-controller using helm:
values.yaml:

# Default values for harvester-vm-dhcp-controller.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

replicaCount: 1

image:
  repository: mrohrich/harvester-vm-dhcp-controller
  pullPolicy: IfNotPresent
  # Overrides the image tag whose default is the chart appVersion.
  tag: "test1-head"

agent:
  image:
    repository: mrohrich/harvester-vm-dhcp-agent
    pullPolicy: IfNotPresent
    tag: "test1-head"

webhook:
  replicaCount: 1
  image:
    repository: mrohrich/harvester-vm-dhcp-webhook
    pullPolicy: IfNotPresent
    tag: "test1-head"
  httpsPort: 8443
  service:
    type: ClusterIP
    port: 443
  resources: {}

imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""

serviceAccount:
  # Specifies whether a service account should be created
  create: true
  # Automatically mount a ServiceAccount's API credentials?
  automount: true
  # Annotations to add to the service account
  annotations: {}
  # The name of the service account to use.
  # If not set and create is true, a name is generated using the fullname template
  name: ""

podAnnotations: {}
podLabels: {}

podSecurityContext: {}
  # fsGroup: 2000

securityContext: {}
  # capabilities:
  #   drop:
  #   - ALL
  # readOnlyRootFilesystem: true
  # runAsNonRoot: true
  # runAsUser: 1000
 service:
  type: ClusterIP
  metricsPort: 8080

ingress:
  enabled: false
  className: ""
  annotations: {}
    # kubernetes.io/ingress.class: nginx
    # kubernetes.io/tls-acme: "true"
  hosts:
    - host: chart-example.local
      paths:
        - path: /
          pathType: ImplementationSpecific
  tls: []
  #  - secretName: chart-example-tls
  #    hosts:
  #      - chart-example.local

resources: {}
  # We usually recommend not to specify default resources and to leave this as a conscious
  # choice for the user. This also increases chances charts run on environments with little
  # resources, such as Minikube. If you do want to specify resources, uncomment the following
  # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
  # limits:
  #   cpu: 100m
  #   memory: 128Mi
  # requests:
  #   cpu: 100m
  #   memory: 128Mi

autoscaling:
  enabled: false
  minReplicas: 1
  maxReplicas: 100
  targetCPUUtilizationPercentage: 80
  # targetMemoryUtilizationPercentage: 80

# Additional volumes on the output Deployment definition.
volumes: []
# - name: foo
#   secret:
#     secretName: mysecret
#     optional: false

# Additional volumeMounts on the output Deployment definition.
volumeMounts: []
# - name: foo
#   mountPath: "/etc/foo"
#   readOnly: true

nodeSelector: {}

tolerations: []

affinity: {}

│ ~/repos/harvester/vm-dhcp-controller │► helm --namespace harvester-system install harvester-vm-dhcp-controller ./chart/ -f ./chart/values.yaml
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/moritz/Downloads/local.yaml
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/moritz/Downloads/local.yaml
NAME: harvester-vm-dhcp-controller
LAST DEPLOYED: Tue Mar  5 11:48:10 2024
NAMESPACE: harvester-system
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
  export POD_NAME=$(kubectl get pods --namespace harvester-system -l "app.kubernetes.io/name=harvester-vm-dhcp-controller,app.kubernetes.io/instance=harvester-vm-dhcp-controller" -o jsonpath="{.items[0].metadata.name}")
  export CONTAINER_PORT=$(kubectl get pod --namespace harvester-system $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
  echo "Visit http://<IP_ADDRESS>:8080 to use your application"
  kubectl --namespace harvester-system port-forward $POD_NAME 8080:$CONTAINER_PORT

Configure VM Network (NetworkAttachmentDefinition), create IPPool and VirtualMachineNetworkConfig

│ ~/repos/harvester/vm-dhcp-controller │► cat <<EOF | kubectl apply -f -
> apiVersion: k8s.cni.cncf.io/v1
> kind: NetworkAttachmentDefinition
> metadata:
>   annotations:
>     network.harvesterhci.io/route: '{"mode":"auto","cidr":"<IP_ADDRESS>/24","gateway":"<IP_ADDRESS>","connectivity":"true"}'
>   labels:
>     network.harvesterhci.io/clusternetwork: mgmt
>     network.harvesterhci.io/ready: "true"
>     network.harvesterhci.io/type: L2VlanNetwork
>     network.harvesterhci.io/vlan-id: "1"
>   name: net-48
>   namespace: default
> spec:
>   config: '{"cniVersion":"0.3.1","name":"net-48","type":"bridge","bridge":"mgmt-br","promiscMode":true,"vlan":1,"ipam":{}}'
> EOF
network-attachment-definitions.k8s.cni.cncf.io created
│ ~/repos/harvester/vm-dhcp-controller │► cat <<EOF | kubectl apply -f -
> apiVersion: network.harvesterhci.io/v1alpha1
> kind: IPPool
> metadata:
>   name: net-48
>   namespace: default
> spec:
>   ipv4Config:
>     serverIP: <IP_ADDRESS>
>     cidr: <IP_ADDRESS>/24
>     pool:
>       start: <IP_ADDRESS>
>       end: <IP_ADDRESS>
>       exclude:
>         - <IP_ADDRESS>
>     router: <IP_ADDRESS>
>     dns:
>       - <IP_ADDRESS>
>     domainName: foo.bar
>     domainSearch:
>       - foo.bar
>     ntp:
>       - pool.ntp.org
>     leaseTime: 300
>   networkName: default/net-48
> EOF
ippool.network.harvesterhci.io/net-48 created
│ ~/repos/harvester/vm-dhcp-controller │► cat <<EOF | kubectl apply -f -
> apiVersion: network.harvesterhci.io/v1alpha1
> kind: VirtualMachineNetworkConfig
> metadata:
>   name: test-vm
>   namespace: default
> spec:
>   vmName: test-vm
>   networkConfigs:
>     - networkName: default/net-48
>       macAddress: fa:fb:fc:50:51:52
> EOF
virtualmachinenetworkconfig.network.harvesterhci.io/test-vm created

Confirm that the expected versions of images was deployed successfully:

│ ~/repos/harvester/vm-dhcp-controller │► kubectl -n harvester-system get deployments.apps harvester-vm-dhcp-controller -oyaml
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
    meta.helm.sh/release-name: harvester-vm-dhcp-controller
    meta.helm.sh/release-namespace: harvester-system
  creationTimestamp: "2024-03-05T10:48:13Z"
  generation: 1
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: harvester-vm-dhcp-controller
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: harvester-vm-dhcp-controller
    app.kubernetes.io/version: 0.1.0
    helm.sh/chart: harvester-vm-dhcp-controller-0.1.0
  name: harvester-vm-dhcp-controller
  namespace: harvester-system
  resourceVersion: "185395"
  uid: 46039ca5-c902-4d56-8a6a-51773dda1ce0
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app.kubernetes.io/instance: harvester-vm-dhcp-controller
      app.kubernetes.io/name: harvester-vm-dhcp-controller
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        app.kubernetes.io/component: controller
        app.kubernetes.io/instance: harvester-vm-dhcp-controller
        app.kubernetes.io/managed-by: Helm
        app.kubernetes.io/name: harvester-vm-dhcp-controller
        app.kubernetes.io/version: 0.1.0
        helm.sh/chart: harvester-vm-dhcp-controller-0.1.0
    spec:
      containers:
      - args:
        - --name
        - harvester-vm-dhcp-controller
        - --namespace
        - harvester-system
        - --image
        - mrohrich/harvester-vm-dhcp-agent:test1-head
        - --service-account-name
        - harvester-vm-dhcp-controller-agent
        image: mrohrich/harvester-vm-dhcp-controller:test1-head
        imagePullPolicy: IfNotPresent
        name: harvester-vm-dhcp-controller
        ports:
        - containerPort: 8080
          name: metrics
          protocol: TCP
        resources: {}
        securityContext: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      serviceAccount: harvester-vm-dhcp-controller
      serviceAccountName: harvester-vm-dhcp-controller
      terminationGracePeriodSeconds: 30
status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: "2024-03-05T10:48:41Z"
    lastUpdateTime: "2024-03-05T10:48:41Z"
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  - lastTransitionTime: "2024-03-05T10:48:13Z"
    lastUpdateTime: "2024-03-05T10:48:41Z"
    message: ReplicaSet "harvester-vm-dhcp-controller-785b596c7f" has successfully
      progressed.
    reason: NewReplicaSetAvailable
    status: "True"
    type: Progressing
  observedGeneration: 1
  readyReplicas: 1
  replicas: 1
  updatedReplicas: 1
│ ~/repos/harvester/vm-dhcp-controller │► kubectl -n harvester-system get pods default-net-48-agent -oyaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    cni.projectcalico.org/containerID: 4ddc6cf5ad6ae4c47ca6d7c5b15c0042f8d7931d185fe98410ef0f08a88a7941
    cni.projectcalico.org/podIP: <IP_ADDRESS>/32
    cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
    k8s.v1.cni.cncf.io/network-status: |-
      [{
          "name": "k8s-pod-network",
          "ips": [
              "<IP_ADDRESS>"
          ],
          "default": true,
          "dns": {}
      },{
          "name": "default/net-48",
          "interface": "eth1",
          "mac": "ba:5b:03:49:07:77",
          "dns": {}
      }]
    k8s.v1.cni.cncf.io/networks: '[{"namespace":"default","name":"net-48","interface":"eth1"}]'
  creationTimestamp: "2024-03-05T10:55:48Z"
  labels:
    network.harvesterhci.io/ippool-name: net-48
    network.harvesterhci.io/ippool-namespace: default
    network.harvesterhci.io/vm-dhcp-controller: agent
  name: default-net-48-agent
  namespace: harvester-system
  resourceVersion: "194509"
  uid: 42a23d2c-4aed-4eb4-a5ef-1b24920016ae
spec:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: network.harvesterhci.io/mgmt
            operator: In
            values:
            - "true"
  containers:
  - args:
    - --ippool-ref
    - default/net-48
    env:
    - name: VM_DHCP_AGENT_NAME
      value: default-net-48-agent
    image: mrohrich/harvester-vm-dhcp-agent:test1-head
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 3
      httpGet:
        path: /healthz
        port: 8080
        scheme: HTTP
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 1
    name: agent
    readinessProbe:
      failureThreshold: 3
      httpGet:
        path: /readyz
        port: 8080
        scheme: HTTP
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 1
    resources: {}
    securityContext:
      capabilities:
        add:
        - NET_ADMIN
      runAsGroup: 0
      runAsUser: 0
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-2kxqd
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  initContainers:
  - command:
    - /bin/sh
    - -c
    - |2

      #!/usr/bin/env sh
      set -ex

      ip address flush dev eth1
      ip address add <IP_ADDRESS>/24 dev eth1
    image: busybox
    imagePullPolicy: Always
    name: ip-setter
    resources: {}
    securityContext:
      capabilities:
        add:
        - NET_ADMIN
      runAsGroup: 0
      runAsUser: 0
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-2kxqd
      readOnly: true
  nodeName: harvester-node-1
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: harvester-vm-dhcp-controller-agent
  serviceAccountName: harvester-vm-dhcp-controller-agent
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - name: kube-api-access-2kxqd
    projected:
      defaultMode: 420
      sources:
      - serviceAccountToken:
          expirationSeconds: 3607
          path: token
      - configMap:
          items:
          - key: ca.crt
            path: ca.crt
          name: kube-root-ca.crt
      - downwardAPI:
          items:
          - fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
            path: namespace
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2024-03-05T10:56:28Z"
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2024-03-05T10:57:23Z"
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2024-03-05T10:57:23Z"
    status: "True"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2024-03-05T10:55:48Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - containerID: containerd://19e0181234cc88d3fa7e63e20d81f1d11b28c3bf89e920f43a2c2f2c67aa28d2
    image: docker.io/mrohrich/harvester-vm-dhcp-agent:test1-head
    imageID: docker.io/mrohrich/harvester-vm-dhcp-agent@sha256:097258ab33aad9723141aab4200ec73dff57eccfa84b77596a35644755977856
    lastState: {}
    name: agent
    ready: true
    restartCount: 0
    started: true
    state:
      running:
        startedAt: "2024-03-05T10:57:23Z"
  hostIP: <IP_ADDRESS>
  initContainerStatuses:
  - containerID: containerd://8b1605ac214916a6c30f3f3dfaf445766cc973100ef776cb1ce3a32f4058e90f
    image: docker.io/library/busybox:latest
    imageID: docker.io/library/busybox@sha256:6d9ac9237a84afe1516540f40a0fafdc86859b2141954b4d643af7066d598b74
    lastState: {}
    name: ip-setter
    ready: true
    restartCount: 0
    state:
      terminated:
        containerID: containerd://8b1605ac214916a6c30f3f3dfaf445766cc973100ef776cb1ce3a32f4058e90f
        exitCode: 0
        finishedAt: "2024-03-05T10:56:28Z"
        reason: Completed
        startedAt: "2024-03-05T10:56:28Z"
  phase: Running
  podIP: <IP_ADDRESS>
  podIPs:
  - ip: <IP_ADDRESS>
  qosClass: BestEffort
  startTime: "2024-03-05T10:55:48Z"

Build new version of images and upgrade chart:
values.yaml:

# Default values for harvester-vm-dhcp-controller.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

replicaCount: 1

image:
  repository: mrohrich/harvester-vm-dhcp-controller
  pullPolicy: IfNotPresent
  # Overrides the image tag whose default is the chart appVersion.
  tag: "test2-head"

agent:
  image:
    repository: mrohrich/harvester-vm-dhcp-agent
    pullPolicy: IfNotPresent
    tag: "test2-head"

webhook:
  replicaCount: 1
  image:
    repository: mrohrich/harvester-vm-dhcp-webhook
    pullPolicy: IfNotPresent
    tag: "test2-head"
  httpsPort: 8443
  service:
    type: ClusterIP
    port: 443
  resources: {}

imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""

serviceAccount:
  # Specifies whether a service account should be created
  create: true
  # Automatically mount a ServiceAccount's API credentials?
  automount: true
  # Annotations to add to the service account
  annotations: {}
  # The name of the service account to use.
  # If not set and create is true, a name is generated using the fullname template
  name: ""

podAnnotations: {}
podLabels: {}

podSecurityContext: {}
  # fsGroup: 2000

securityContext: {}
  # capabilities:
  #   drop:
  #   - ALL
  # readOnlyRootFilesystem: true
  # runAsNonRoot: true
  # runAsUser: 1000

service:
  type: ClusterIP
  metricsPort: 8080

ingress:
  enabled: false
  className: ""
  annotations: {}
    # kubernetes.io/ingress.class: nginx
    # kubernetes.io/tls-acme: "true"
  hosts:
    - host: chart-example.local
      paths:
        - path: /
          pathType: ImplementationSpecific
  tls: []
  #  - secretName: chart-example-tls
  #    hosts:
  #      - chart-example.local

resources: {}
  # We usually recommend not to specify default resources and to leave this as a conscious
  # choice for the user. This also increases chances charts run on environments with little
  # resources, such as Minikube. If you do want to specify resources, uncomment the following
  # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
  # limits:
  #   cpu: 100m
  #   memory: 128Mi
  # requests:
  #   cpu: 100m
  #   memory: 128Mi

autoscaling:
  enabled: false
  minReplicas: 1
  maxReplicas: 100
  targetCPUUtilizationPercentage: 80
  # targetMemoryUtilizationPercentage: 80

# Additional volumes on the output Deployment definition.
volumes: []
# - name: foo
#   secret:
#     secretName: mysecret
#     optional: false

# Additional volumeMounts on the output Deployment definition.
volumeMounts: []
# - name: foo
#   mountPath: "/etc/foo"
#   readOnly: true

nodeSelector: {}

tolerations: []

affinity: {}

│ ~/repos/harvester/vm-dhcp-controller │► helm --namespace harvester-system upgrade harvester-vm-dhcp-controller ./chart/ -f ./chart/values.yaml
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/moritz/Downloads/local.yaml
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/moritz/Downloads/local.yaml
Release "harvester-vm-dhcp-controller" has been upgraded. Happy Helming!
NAME: harvester-vm-dhcp-controller
LAST DEPLOYED: Tue Mar  5 12:22:10 2024
NAMESPACE: harvester-system
STATUS: deployed
REVISION: 2
NOTES:
1. Get the application URL by running these commands:
  export POD_NAME=$(kubectl get pods --namespace harvester-system -l "app.kubernetes.io/name=harvester-vm-dhcp-controller,app.kubernetes.io/instance=harvester-vm-dhcp-controller" -o jsonpath="{.items[0].metadata.name}")
  export CONTAINER_PORT=$(kubectl get pod --namespace harvester-system $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
  echo "Visit http://<IP_ADDRESS>:8080 to use your application"
  kubectl --namespace harvester-system port-forward $POD_NAME 8080:$CONTAINER_PORT

:white_check_mark: Confirm that the controller has been successfully upgraded

│ ~/repos/harvester/vm-dhcp-controller │► kubectl -n harvester-system get deployments.apps harvester-vm-dhcp-controller -oyaml
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "2"
    meta.helm.sh/release-name: harvester-vm-dhcp-controller
    meta.helm.sh/release-namespace: harvester-system
  creationTimestamp: "2024-03-05T10:48:13Z"
  generation: 2
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: harvester-vm-dhcp-controller
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: harvester-vm-dhcp-controller
    app.kubernetes.io/version: 0.1.1
    helm.sh/chart: harvester-vm-dhcp-controller-0.1.1
  name: harvester-vm-dhcp-controller
  namespace: harvester-system
  resourceVersion: "220331"
  uid: 46039ca5-c902-4d56-8a6a-51773dda1ce0
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app.kubernetes.io/instance: harvester-vm-dhcp-controller
      app.kubernetes.io/name: harvester-vm-dhcp-controller
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        app.kubernetes.io/component: controller
        app.kubernetes.io/instance: harvester-vm-dhcp-controller
        app.kubernetes.io/managed-by: Helm
        app.kubernetes.io/name: harvester-vm-dhcp-controller
        app.kubernetes.io/version: 0.1.1
        helm.sh/chart: harvester-vm-dhcp-controller-0.1.1
    spec:
      containers:
      - args:
        - --name
        - harvester-vm-dhcp-controller
        - --namespace
        - harvester-system
        - --image
        - mrohrich/harvester-vm-dhcp-agent:test2-head
        - --service-account-name
        - harvester-vm-dhcp-controller-agent
        image: mrohrich/harvester-vm-dhcp-controller:test2-head
        imagePullPolicy: IfNotPresent
        name: harvester-vm-dhcp-controller
        ports:
        - containerPort: 8080
          name: metrics
          protocol: TCP
        resources: {}
        securityContext: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      serviceAccount: harvester-vm-dhcp-controller
      serviceAccountName: harvester-vm-dhcp-controller
      terminationGracePeriodSeconds: 30
status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: "2024-03-05T10:48:41Z"
    lastUpdateTime: "2024-03-05T10:48:41Z"
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  - lastTransitionTime: "2024-03-05T10:48:13Z"
    lastUpdateTime: "2024-03-05T11:22:11Z"
    message: ReplicaSet "harvester-vm-dhcp-controller-799bd876dc" is progressing.
    reason: ReplicaSetUpdated
    status: "True"
    type: Progressing
  observedGeneration: 2
  readyReplicas: 1
  replicas: 2
  unavailableReplicas: 1
  updatedReplicas: 1

:white_check_mark: Confirm that the agent is successfully upgraded

:exclamation: It may take a little bit of time (~2 minutes) until the resources are reconciled and the upgraded agent is deployed. This is expected, but the amount of time to wait is not specified in test procedures or documentation.
│ ~/repos/harvester/vm-dhcp-controller │ 1 ► kubectl -n harvester-system get pod default-net-48-agent -oyaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    cni.projectcalico.org/containerID: 570a294444f34e75f89747a496c758139d10d208b73ead7a83de8932050efed9
    cni.projectcalico.org/podIP: <IP_ADDRESS>/32
    cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
    k8s.v1.cni.cncf.io/network-status: |-
      [{
          "name": "k8s-pod-network",
          "ips": [
              "<IP_ADDRESS>"
          ],
          "default": true,
          "dns": {}
      },{
          "name": "default/net-48",
          "interface": "eth1",
          "mac": "9a:05:4e:67:7a:a9",
          "dns": {}
      }]
    k8s.v1.cni.cncf.io/networks: '[{"namespace":"default","name":"net-48","interface":"eth1"}]'
  creationTimestamp: "2024-03-05T11:23:28Z"
  labels:
    network.harvesterhci.io/ippool-name: net-48
    network.harvesterhci.io/ippool-namespace: default
    network.harvesterhci.io/vm-dhcp-controller: agent
  name: default-net-48-agent
  namespace: harvester-system
  resourceVersion: "221780"
  uid: bfdeb227-08ac-4493-80a9-c9e745acf3a4
spec:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: network.harvesterhci.io/mgmt
            operator: In
            values:
            - "true"
  containers:
  - args:
    - --ippool-ref
    - default/net-48
    env:
    - name: VM_DHCP_AGENT_NAME
      value: default-net-48-agent
    image: mrohrich/harvester-vm-dhcp-agent:test2-head
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 3
      httpGet:
        path: /healthz
        port: 8080
        scheme: HTTP
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 1
    name: agent
    readinessProbe:
      failureThreshold: 3
      httpGet:
        path: /readyz
        port: 8080
        scheme: HTTP
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 1
    resources: {}
    securityContext:
      capabilities:
        add:
        - NET_ADMIN
      runAsGroup: 0
      runAsUser: 0
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-l2bzm
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  initContainers:
  - command:
    - /bin/sh
    - -c
    - |2

      #!/usr/bin/env sh
      set -ex

      ip address flush dev eth1
      ip address add <IP_ADDRESS>/24 dev eth1
    image: busybox
    imagePullPolicy: Always
    name: ip-setter
    resources: {}
    securityContext:
      capabilities:
        add:
        - NET_ADMIN
      runAsGroup: 0
      runAsUser: 0
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-l2bzm
      readOnly: true
  nodeName: harvester-node-2
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: harvester-vm-dhcp-controller-agent
  serviceAccountName: harvester-vm-dhcp-controller-agent
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - name: kube-api-access-l2bzm
    projected:
      defaultMode: 420
      sources:
      - serviceAccountToken:
          expirationSeconds: 3607
          path: token
      - configMap:
          items:
          - key: ca.crt
            path: ca.crt
          name: kube-root-ca.crt
      - downwardAPI:
          items:
          - fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
            path: namespace
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2024-03-05T11:23:28Z"
    message: 'containers with incomplete status: [ip-setter]'
    reason: ContainersNotInitialized
    status: "False"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2024-03-05T11:23:28Z"
    message: 'containers with unready status: [agent]'
    reason: ContainersNotReady
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2024-03-05T11:23:28Z"
    message: 'containers with unready status: [agent]'
    reason: ContainersNotReady
    status: "False"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2024-03-05T11:23:28Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - image: mrohrich/harvester-vm-dhcp-agent:test2-head
    imageID: ""
    lastState: {}
    name: agent
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        reason: PodInitializing
  hostIP: <IP_ADDRESS>
  initContainerStatuses:
  - image: busybox
    imageID: ""
    lastState: {}
    name: ip-setter
    ready: false
    restartCount: 0
    state:
      waiting:
        reason: PodInitializing
  phase: Pending
  qosClass: BestEffort
  startTime: "2024-03-05T11:23:28Z"

:white_check_mark: validated successfully with:

Harvester v1.3.0-rc3
Harvester vm-dhcp-controller main@208a3d2e53a60ea0e43c69a7c269c48d4f5cf0d6


✨ Upgrade to TF 0.13

Example stopped working:
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

Error: Provider configuration not present

To work with module.elasticsearch.google_storage_bucket.backup_repository its
original provider configuration at provider["registry.terraform.io/-/google"]
is required, but it has been removed. This occurs when a provider
configuration is removed while objects created by that provider still exist in
the state. Re-add the provider configuration to destroy
module.elasticsearch.google_storage_bucket.backup_repository, after which you
can remove the provider configuration again.

Error: Provider configuration not present

To work with module.elasticsearch.kubernetes_cron_job.backup_cleanup its
original provider configuration at
module.elasticsearch.provider["registry.terraform.io/-/kubernetes"] is
required, but it has been removed. This occurs when a provider configuration
is removed while objects created by that provider still exist in the state.
Re-add the provider configuration to destroy
module.elasticsearch.kubernetes_cron_job.backup_cleanup, after which you can
remove the provider configuration again.


Website: Add flutter example

Currently there is only react, vue and html/css. Please add an example for flutter.
A template can be:
Icon(PhosphorIcons.example)

Will do, thanks @CodeDoctorDE. We plan to rework this section soon.

Added Flutter snippets in 4137a8b5c198a14861aabe74104ae05a48802dcb, more thorough rework to happen later.


More e2e

Added tests for summary and more annotations.
Delete test wasn't working for some reason. I'll work on that separately.
Noticed a bug with the annotation update - it seems to clear out the createdBy/createdOn values which is obviously wrong.

Codecov Report

Merging #10 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #10   +/-   ##
=======================================
  Coverage   76.19%   76.19%
=======================================
  Files          17       17
  Lines         336      336
  Branches       17       17
=======================================
  Hits          256      256
  Misses         77       77
  Partials        3        3

Impacted Files
Coverage Δ

src/app/em/em-viewer-route.component.ts
55.55% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Some documentation fixes

Please resolve the merge conflicts. Thanks :tada:

Merge conflicts resolved.

This looks to be closely related to the format refactoring suggested in #395. Let's wait a bit before pushing.

What's the status of this PR? Still relevant after #395 has been merged?

I think the new formats documentation is now explicit enough about csv import/export options. Sorry for taking too long to review.


Debug files

Hello,
I installed v<IP_ADDRESS>14. It seems to work again after the latest RSL path (i.e. no errors in the log).
I miss the updated files in the account directory (_index, academy, account, arena, artifacts, heroes and resources) - in a former reply you called them debug files. The files in the static directory are updated though.
Is it intended, is there a minor bug or can I activate the creation or update of these files by starting the RTK SDK using a certain parameter?
Best Regards
Efro

Unfortunately same with v<IP_ADDRESS>661

same with v<IP_ADDRESS>999 and v<IP_ADDRESS>65

v<IP_ADDRESS>070 still does not create the debug files.
Any help is appreciated.
Regards Efro

Got them, thanx!


mailing list

I hate to file an issue for this, but I can't find another place to ask this.
Is there a TypeScript mailing list where people can ask questions?
My search for one came up empty and I don't see a Google Group.

We don't have a mailing list.
Good communication channels include:

StackOverflow for technical questions
Gitter (https://gitter.im/Microsoft/TypeScript) for general discussion
This issue tracker for bugs / implementation details

If you don't have a mailing list, how do you publish your announcements?
How does one go about requesting features and etc? Get answers to common questions or advance topics?

how do you publish your announcements?

https://twitter.com/typescriptlang

How does one go about requesting features and etc?

This issue tracker?

Get answers to common questions or advance topics?

StackOverflow

You seriously advocate Twitter and Roadmap?
Can I also find you guys on Facebook, Gab, Google+, Instagram, LinkedIn, Pinterest, Reddit, Snapchat, Tumblr, Twitter, Viber, VK, WeChat, Weibo, WhatsApp, Wikia, and YouTube.
I mean seriously, I rather just get a RSS feed without having to signup for some social media account and be feed the many adds.
As for StackOverflow... Gosh... where do I start with the pollution of bad answers on there. That'll waste your users more time trying to filter through spam rather than get a straight answer.
Anyways, thank you for your time.

Sorry we can't serve every venue; we already get enough traffic from the issue tracker. To be frank though, I don't see what's wrong with the Roadmap or the blog. Our website and wiki also have "What's New" pages if you're interested.

Reddit

Yup

Facebook

If I can dig up the account credentials, maybe.

VK...Weibo

If I spoke Russian and Mandarin, you probably would!

I mean seriously, I rather just get a RSS feed

Here y'go! https://blogs.msdn.microsoft.com/typescript/feed/
The thing is that these venues require little-to-no moderation on our part. We already get so much traffic over GitHub that we don't have the bandwidth to moderate and respond on a mailing list.

You can't serve it because you don't allow the user community to answer their own questions as you're lacking a mailing list.
Take for example Apache Wicket:
https://wicket.apache.org/help/#questions
Notice how simple the user support is delegated to the user community while the developers are doing what they do best, implement the new features:
https://wicket.apache.org/help/email.html

Yes, a mailing list! StackOverflow isn't the best place to build a community around typescript. Github issues is not the best place for general discussion about typescript... We need a mailing list!

I'd recommend the TypeScript community discord if you'd like to have general discussion, links are in: http://www.typescriptlang.org/docs/home.html

This is hopeless and also the reason why I don't use any of Microsoft's products home. Wish my job would stop deploying Windows and switch to Linux desktop.
The one think Microsoft almost got right was to fix the web scripting tech (TS) after the messy IE. And then... No user mailing list...