Setting prometheus pod memory in values yaml

I've installed kube-prometheus with a helm chart and a minor changes to the config.
From Grafana I see that prometheus-prometheus-kube-prometheus-prometheus-0 takes 1.5 Gig although it's set to 50 mg.  I did a test to find the value to change in the values.yaml.  I found the following to be set to 50mg by default and thought it might be the values to change since i found nothing else :

 # resource config for prometheusConfigReloader
 prometheusOperator:
   prometheusConfigReloader:
     resources:
       requests:
         memory: 100Mi
       limits:
         memory: 100Mi

When i logged on to see the data in grafana, I now had 3 of the prometheus pods with that value as a limit.  This is a problem because pod 1 is over 1G and would like to change the memory limit.

prometheus-prometheus-kube-prometheus-prometheus-0
prometheus-kube-prometheus-operator-9d6b8c497-jjxjn
The prometheus config reloader

Why would all three have the same values. The other 2 seem fine and hover at 50-60 mg, while the other is much bigger.

It seems that by default the config-reloader sidecar is set to 50m:
https://github.com/prometheus-community/helm-charts/blob/cdc9e43a8c9507980f7cf475288327f89bee828c/charts/kube-prometheus-stack/values.yaml#L2375
Since config-reloader is a sidecar to prometheus-prometheus as well as the alert-manager statefulsets, it makes it seem like these pods are exceeding limits. I see this as well in grafana as well as the GCP monitoring dashboard.

Ah I see, so I did look inside the yaml and the prometheus container has no limit.  Grafana was misleading.  Thanks


Add Quote::nonce() fn

Add Quote::nonce() + Quote::verify_signature() fn's
At the moment the nonce is mixed in the message and not available to api users. There are situations in which different components validate signature and nonce. We can expose the nonce in a non-breaking fashion.
Drive-by fix: removed a redundant VerifyError enum which was a leftover from refactoring.
How to use
The additional fn's can be used in addition to the existing Quote::verify() fn that takes a pubkey + nonce.
Testing done
Unit tests for quote validation using the nonce() fn passed, so this path is covered by a test.

removing the unused error enum is a breaking change in semver :(
 cargo semver-checks
     Parsing az-cvm-vtpm v0.4.0 (baseline)
    Checking az-cvm-vtpm v0.4.0 -> v0.4.0 (no change)
   Completed [   0.044s] 55 checks; 54 passed, 1 failed, 0 unnecessary

--- failure enum_missing: pub enum removed or renamed ---

Description:
A publicly-visible enum cannot be imported by its prior path. A `pub use` may have been removed, or the enum itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.26.0/src/lints/enum_missing.ron

Failed in:
  enum az_cvm_vtpm::vtpm::VerifyError, previously in file /home/magnuskulke/.cargo/registry/src/index.crates.io-6f17d22bba15001f/az-cvm-vtpm-0.4.0/src/vtpm/mod.rs:160
       Final [   0.045s] semver requires new major version: 1 major and 0 minor checks failed

so I add this back and open an issue


Breakpoints don't stop countdown.

Describe the bug
When a countdown is active, breakpoint don't stop its execution.

Repro in Chrome and Edge on my Surface Book.

All fibers need to pause when breakpoint is hit

Fix is likely don't hand control of the environment when there is a breakpoint hit

Fixed


Request for new API under Storage class to list all conversations for a specific conversation id

Hi,
I am looking for a new API under Storage class to list all conversations for a specific conversation id.
I am not if that already exists. If not it will be helpful to have something like as shown below
bot.storage.get_conversations(conversation_id),. where bot is an bot of a chatterbot class
Thanks

Hi @faraazc, development of a feature similar to this is planned. It will allow filtering to be done based on a named conversation, for example:
statement_for_conversation = bot.storage.filter(conversation='<string>')

I hope this is close enough to your use-case to be useful?

conversation='' is a conversation id right?.
and if the statement_for_conversation = bot.storage.filter(conversation='' call returns me a list of statements under a particular conversation id, then solves my requirement.
Thanks for quick response.

conversation will be a string. With the new changes, each statement will have an conversation attribute to label the conversation that it is a part of. The conversation string can be anything though, including an id.


How to keep refreshing the refresh_token?

It randomly gives me "unauthorized error" "The security token included in the request is expired".
I observed that, in the Credentials.php there is getLWAToken() function which does the job of refreshing the token however it returns access token only.
I am not sure if we have to manually make some calls to refresh the token or the library does that for me?
Anyone knows?

Ok. If anyone still having this issue. I think solution is just to truncate the temporary aws-tokens i.e. SimpleTokenStorage file.
Everytime you run the code just truncate the file. I don't think contents of this file are rechecked for if its still valid or not.
TODO: Perhaps a simple check in SimpleTokenStorage class/function would solve the issue without doing any further actions to be taken outside the class.
Please correct me if I am wrong.

Hi there,
I run to the same problem - will think of something and will implement it.
My situation however is a little bit special - long running proces which uses only one instance of a client
| I don't think contents of this file are rechecked for if its still valid or not.
This is not true. The file is checked whenever a fresh credentials are made

Hi there, I run to the same problem - will think of something and will implement it. My situation however is a little bit special - long running proces which uses only one instance of a client

I don't think contents of this file are rechecked for if its still valid or not.

This is not true. The file is checked whenever a fresh credentials are made

I end up creating different temporary files per user so that they don't cause problems with any other accounts as effect of multiple instance of same script running.

Well - the TokenStorage accepts configuration. The user can specify
different storage files for different workers
Kind Regards,
Lyubomir Slavilov
On Mon, Jan 10, 2022 at 9:18 AM aniruddhaad @.***>
wrote:

Hi there, I run to the same problem - will think of something and will
implement it. My situation however is a little bit special - long running
proces which uses only one instance of a client
I don't think contents of this file are rechecked for if its still valid
or not.
This is not true. The file is checked whenever a fresh credentials are made
I end up creating different temporary files per user so that they don't
cause problems with any other accounts as effect of multiple instance of
same script running.
—
Reply to this email directly, view it on GitHub
https://github.com/double-break/spapi-php/issues/41#issuecomment-1008596771,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEGJUIBVIDPHQTSWGHMYOTUVKB3RANCNFSM5E5UXTYQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Syncing stuck when using Reth as Execution client - Reth reporting Bad Block

Describe the bug
My Lodestar client stopped syncing around 6 days ago. It seems to know about new blocks but is stuck processing slot 8066879 I'm using Reth as the execution client and it is erroring about block 18872589 which is in slot 8066888. The lodestar client logs are:
lodestar-beacon_node-1  | Jan-02 16:56:41.023[]                 info: Syncing - 280000000 days left - 2.04e-9 slots/s - slot: 8115881 - head: 8066879 0x0b5f…3899 - exec-block: valid(18872581 0x4d41…) - finalized: 0x996a…6acc:252088 - peers: 26
lodestar-beacon_node-1  | Jan-02 16:56:47.192[execution]        info: Execution client is synced oldState=SYNCING, newState=SYNCED
lodestar-beacon_node-1  | Jan-02 16:56:52.785[execution]        warn: Execution client is syncing oldState=SYNCED, newState=SYNCING
lodestar-beacon_node-1  | Jan-02 16:56:53.147[]                 info: Syncing - 280000000 days left - 2.04e-9 slots/s - slot: 8115882 - head: 8066879 0x0b5f…3899 - exec-block: valid(18872581 0x4d41…) - finalized: 0x996a…6acc:252088 - peers: 23
lodestar-beacon_node-1  | Jan-02 16:57:04.082[execution]        info: Execution client is synced oldState=SYNCING, newState=SYNCED
lodestar-beacon_node-1  | Jan-02 16:57:05.020[]                 info: Syncing - 280000000 days left - 2.04e-9 slots/s - slot: 8115883 - head: 8066879 0x0b5f…3899 - exec-block: valid(18872581 0x4d41…) - finalized: 0x996a…6acc:252088 - peers: 23
lodestar-beacon_node-1  | Jan-02 16:57:07.887[execution]        warn: Execution client is syncing oldState=SYNCED, newState=SYNCING
lodestar-beacon_node-1  | Jan-02 16:57:14.151[execution]        info: Execution client is synced oldState=SYNCING, newState=SYNCED
lodestar-beacon_node-1  | Jan-02 16:57:17.068[]                 info: Syncing - 280000000 days left - 2.06e-9 slots/s - slot: 8115884 - head: 8066879 0x0b5f…3899 - exec-block: valid(18872581 0x4d41…) - finalized: 0x996a…6acc:252088 - peers: 21
lodestar-beacon_node-1  | Jan-02 16:57:19.847[execution]        warn: Execution client is syncing oldState=SYNCED, newState=SYNCING
lodestar-beacon_node-1  | Jan-02 16:57:29.001[]                 info: Syncing - 280000000 days left - 2.06e-9 slots/s - slot: 8115885 - head: 8066879 0x0b5f…3899 - exec-block: valid(18872581 0x4d41…) - finalized: 0x996a…6acc:252088 - peers: 22

Reth logs are:
024-01-02T16:50:46.147207Z  INFO try_insert_validated_block{block=(18872584, 0xd76bbb604027fdd59233d74897e5ae7b2b25cbc6875a0efbed9d35cf2ce05132)}: blockchain_tree: return=Ok(Valid)
2024-01-02T16:50:46.147340Z  INFO reth::node::events: Block added to canonical chain number=18872584 hash=0xd76bbb604027fdd59233d74897e5ae7b2b25cbc6875a0efbed9d35cf2ce05132
2024-01-02T16:50:47.187506Z  INFO try_insert_validated_block{block=(18872585, 0xc868ca2532a7b3b1fa2dab8591bde59e4fca09f7ef72941333181444779136c7)}: blockchain_tree: return=Ok(Valid)
2024-01-02T16:50:47.187653Z  INFO reth::node::events: Block added to canonical chain number=18872585 hash=0xc868ca2532a7b3b1fa2dab8591bde59e4fca09f7ef72941333181444779136c7
2024-01-02T16:50:48.356198Z  INFO try_insert_validated_block{block=(18872586, 0x2e73316a3901975439e80337d8aa188f3e30d198b20680a15ee6ca35ebfadc08)}: blockchain_tree: return=Ok(Valid)
2024-01-02T16:50:48.356288Z  INFO reth::node::events: Block added to canonical chain number=18872586 hash=0x2e73316a3901975439e80337d8aa188f3e30d198b20680a15ee6ca35ebfadc08
2024-01-02T16:50:50.623799Z  INFO try_insert_validated_block{block=(18872587, 0x48bca92dda4d9476b0ebbf024c50bf002e1ced833c3e52215475174f411dbc14)}: blockchain_tree: return=Ok(Valid)
2024-01-02T16:50:50.623930Z  INFO reth::node::events: Block added to canonical chain number=18872587 hash=0x48bca92dda4d9476b0ebbf024c50bf002e1ced833c3e52215475174f411dbc14
2024-01-02T16:50:51.847464Z  INFO try_insert_validated_block{block=(18872588, 0xe66a09516ef5ab3aecd4a49d9bb5e63be07cee22f1d4efffbac9fd07f83db72c)}: blockchain_tree: return=Ok(Valid)
2024-01-02T16:50:51.847572Z  INFO reth::node::events: Block added to canonical chain number=18872588 hash=0xe66a09516ef5ab3aecd4a49d9bb5e63be07cee22f1d4efffbac9fd07f83db72c
2024-01-02T16:50:53.070649Z  INFO try_insert_validated_block{block=(18872589, 0x476f922d904f88ad8bc2013875f1c16361c11ceef028c4264b798c4e96f3f520)}: blockchain_tree: return=Err(InsertBlockError { error: Consensus(BodyStateRootDiff { got: 0xac80d9cfaf5e0842ec26c5f5b7b4281e6f142823ae6556c112655bde06815c82, expected: 0x83599347964caf6a248341fb285a1012e917215d8c6d856a67f553f1da3b0560 }), hash: 0x476f922d904f88ad8bc2013875f1c16361c11ceef028c4264b798c4e96f3f520, number: 18872589, parent_hash: 0xe66a09516ef5ab3aecd4a49d9bb5e63be07cee22f1d4efffbac9fd07f83db72c, num_txs: 165, .. })
2024-01-02T16:50:53.070711Z  WARN consensus::engine: Bad block with header hash: 0x476f922d904f88ad8bc2013875f1c16361c11ceef028c4264b798c4e96f3f520, invalid ancestor: Header { parent_hash: 0xe66a09516ef5ab3aecd4a49d9bb5e63be07cee22f1d4efffbac9fd07f83db72c, ommers_hash: 0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347, beneficiary: 0x95222290dd7278aa3ddd389cc1e1d165cc4bafe5, state_root: 0x83599347964caf6a248341fb285a1012e917215d8c6d856a67f553f1da3b0560, transactions_root: 0xba2c7529ae77c0c08f51d93290ac90a4425ae2763b3e8437b1aa117123eb8697, receipts_root: 0xd655c33ec864e90eff3f5eba2711bbb256c86266061de4e4c4f6f3cb52dc81b2, withdrawals_root: Some(0xba0675d648eb450abee4630ad917b927ac1de78ba5bdb40adac4b4afe342d768), logs_bloom: 0x30f3d072e14d1120b08190eae5c956a101562856380684e4000384383c023813455d95a1a4a5a126550819211002ed0e27053d189e547bb10798a335916b410cc5c0b81d2d48882a683ac37eca98ace4428701d4aec88f87e96e1652a965500107267478c266286380bc110310233c79e091395f2a9d4c06ce5ad3d5600a61658f368fdc3a83d3d8014db95b57abb1240a3204618d5da26e747166c030f1083b8af429f75e027926427cd0ca9490c449652a618804711f077551372a142636787bf020f2a51d88c903408890023dbd0f4b215de934010978098d814f68f220a208bbaff82cc8a083015e968c08171a05aa3c9b3831beb6c270093e587820f469, difficulty: 0x0000000000000000000000000000000000000000000000000000000000000000_U256, number: 18872589, gas_limit: 30000000, gas_used: 19268495, timestamp:<PHONE_NUMBER>, mix_hash: 0xd492600e498605957ed0969c405c5a8b05813ab55753e01f01f130d118726009, nonce: 0, base_fee_per_gas: Some(19970162705), extra_data: Bytes(0x6265617665726275696c642e6f7267) }

I tried unwinding the last 5 blocks of Reth in case it was having issues and it's still error'ing on that same block.
Expected behavior
I expect Lodestar and Reth to sync correctly.
Steps to reproduce

Run Lodestar using latest docker container
Run Reth using latest docker container
See errors in logs about this block not syncing.

Additional context
No response
Operating system
Linux
Lodestar version or commit hash
v1.13.0/1a816b4

I realized there were more debug logs for lodestar in the logs folder. They are this:
Jan-03 07:33:41.561[chain]           debug: Block error slot=8066888, code=BLOCK_ERROR_EXECUTION_ERROR, execStatus=INVALID, errorMessage=Block state root (0xac80d9cfaf5e0842ec26c5f5b7b4281e6f142823ae6556c112655bde06815c82) is different from expected: (0x83599347964caf6a248341fb285a1012e917215d8c6d856a67f553f1da3b0560)
Error: BLOCK_ERROR_EXECUTION_ERROR
    at verifyBlockExecutionPayload (file:///usr/app/packages/beacon-node/src/chain/blocks/verifyBlocksExecutionPayloads.ts:321:25)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at verifyBlocksExecutionPayload (file:///usr/app/packages/beacon-node/src/chain/blocks/verifyBlocksExecutionPayloads.ts:158:28)
    at async Promise.all (index 0)
    at BeaconChain.verifyBlocksInEpoch (file:///usr/app/packages/beacon-node/src/chain/blocks/verifyBlock.ts:91:70)
    at BeaconChain.processBlocks (file:///usr/app/packages/beacon-node/src/chain/blocks/index.ts:75:68)
    at JobItemQueue.runJob (file:///usr/app/packages/beacon-node/src/util/queue/itemQueue.ts:101:22)
Jan-03 07:33:41.561[sync]          verbose: Batch process error id=Finalized, startEpoch=252090, status=Processing, code=BLOCK_ERROR_EXECUTION_ERROR, execStatus=INVALID, errorMessage=Block state root (0xac80d9cfaf5e0842ec26c5f5b7b4281e6f142823ae6556c112655bde06815c82) is different from expected: (0x83599347964caf6a248341fb285a1012e917215d8c6d856a67f553f1da3b0560)
Error: BLOCK_ERROR_EXECUTION_ERROR
    at verifyBlockExecutionPayload (file:///usr/app/packages/beacon-node/src/chain/blocks/verifyBlocksExecutionPayloads.ts:321:25)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at verifyBlocksExecutionPayload (file:///usr/app/packages/beacon-node/src/chain/blocks/verifyBlocksExecutionPayloads.ts:158:28)
    at async Promise.all (index 0)
    at BeaconChain.verifyBlocksInEpoch (file:///usr/app/packages/beacon-node/src/chain/blocks/verifyBlock.ts:91:70)
    at BeaconChain.processBlocks (file:///usr/app/packages/beacon-node/src/chain/blocks/index.ts:75:68)
    at JobItemQueue.runJob (file:///usr/app/packages/beacon-node/src/util/queue/itemQueue.ts:101:22)
Jan-03 07:33:41.561[sync]          verbose: Batch validation error id=Finalized, startEpoch=252089, status=AwaitingValidation

I was able to get it syncing again with the flags --forceCheckpointSync --checkpointSyncUrl https://sync-mainnet.beaconcha.in. I guess it now has the latest blocks and is syncing backwards.

seems like your reth was corrupted and was considering possibly a "canonical block" as bad, this would cause lodestar to stall, checkpoint syncs make lodestar jump ahead and reth starts the backfill and not sure probably resolve the block
however it would be wise to raise this issue to reth team

I was able to get it syncing again with the flags --forceCheckpointSync --checkpointSyncUrl https://sync-mainnet.beaconcha.in. I guess it now has the latest blocks and is syncing backwards.

any update on this?

It's working fine again now. I think Reth was working correctly as it didn't need any changes, it just wouldn't proceed because Lodestar was saying the block had a different state root than what it computed.

Will close this as it doesn't seem to be an issue with Lodestar here.


Make deprecation of autoconf/automake more visible

Print the error/warning message to standard error and require the user of the script to pass an additional argument to get past the warning message, making it clearer that the autotools build system is deprecated and building with CMake is strongly preferred.
This is a follow-up to #88.
New standard behavior (exits with a non-zero exit code):
$ ./autoconfiscate.sh
*** Autoconf/automake is deprecated for Openwsman and might not fully work.
*** Please use CMake instead!

*** To ignore this warning and proceed regardless, re-run as follows:
***   ./autoconfiscate.sh --ignore-deprecation-warning

If invoked with the option, will still print the first part of the message and then proceed as before.

Thanks for merging!


Not Implementing IWAE?

Hi,
Thanks for your good work and repo. May I ask did you implement the exact IWAE as a tighter lower bound, in case I missed it?
See the reference: https://github.com/XavierXiao/Likelihood-Regret/blob/5517c9bac5992b116e55bb61cad8171e0d585063/train_pixel.py#L130

We don't train the VAE by IWAE objective, we simply use the plain ELBO (or IWAE with k=1). We only compute the likelihood estimate by IWAE during test time.

I see. Btw, should we only max among the samples of z? In https://github.com/XavierXiao/Likelihood-Regret/blob/5517c9bac5992b116e55bb61cad8171e0d585063/compute_LR.py#L64

I see. Btw, should not we only max along the dim of samples z?
https://github.com/XavierXiao/Likelihood-Regret/blob/5517c9bac5992b116e55bb61cad8171e0d585063/compute_LR.py#L64


Lease events drop off after some time

Any old deployments that has been running for sometime fails to return the lease events. It's been an issue since launch I believe, but some customers are complaining about it and find it confusing.

I think lease-events disappear (on the K8s level) after some time (probably like 15 minutes or so).
=> https://github.com/akash-network/support/issues/246


feat(dot): add bashls and shellcheck

I work with shell files a lot , so this basically adds support for shell files

Thanks!


DQN_HRL object has no attribute 'num_input_extra'

Its seems to be a bug in the file HCG/core/agent.py , line 33:
self.num_inputs = num_inputs + self.num_input_extra
the variable self.num_input_extra is not defined. Please clarify.

Again, in a similar way, I am getting error:
HCG/core/utils.py, line 1165
DQN_HRL object has no attribute 'extra_pred_dim'

I got a workaround to this problem.  I called the following function in the file HCG/experiments/config.py, at the end:
process_cfg()
But, Now getting the runtime error. The error logs are as follow:
==== loaded scene: scene_1 target: 021_bleach_cleanser idx: 8
Traceback (most recent call last):
File "/home/prem/anaconda3/envs/prem3/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/home/prem/anaconda3/envs/prem3/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/prem/prem_workspace/HCG/HCG/core/test_offline.py", line 413, in
test(run_iter=run_iter)
File "/home/prem/prem_workspace/HCG/HCG/core/test_offline.py", line 281, in test
gt_traj=input_exec_traj)
File "/home/prem/anaconda3/envs/prem3/lib/python3.7/site-packages/torch/autograd/grad_mode.py", line 49, in decorate_no_grad
return func(*args, **kwargs)
File "/home/prem/prem_workspace/HCG/HCG/core/agent.py", line 190, in select_action
actions = self.policy.sample(feature)
File "/home/prem/prem_workspace/HCG/HCG/core/network_arch.py", line 223, in sample
mean, log_std, extra_pred = self.forward(state)
File "/home/prem/prem_workspace/HCG/HCG/core/network_arch.py", line 208, in forward
x = F.relu(self.linear1(state))
File "/home/prem/anaconda3/envs/prem3/lib/python3.7/site-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/home/prem/anaconda3/envs/prem3/lib/python3.7/site-packages/torch/nn/modules/linear.py", line 87, in forward
return F.linear(input, self.weight, self.bias)
File "/home/prem/anaconda3/envs/prem3/lib/python3.7/site-packages/torch/nn/functional.py", line 1370, in linear
ret = torch.addmm(bias, input, weight.t())
RuntimeError: size mismatch, m1: [1 x 513], m2: [577 x 256] at /pytorch/aten/src/THC/generic/THCTensorMathBlas.cu:290

Could you show me which commands you are running? I think the size mismatch is due to no plan latent is provided (64 dim). Could you try the demo scripts and see if those work.

Hi,
Thanks for the response.
I am running the demo script itself as advised --> bash experiments/scripts/test_demo.sh
Yes, I am able to guess that the problem is due to no plan latent being provided. But I don't know why it's happening. I didn't do any other modification and just followed the steps given.

I think maybe the config file has some issues based on this and your first post. Could you try re-downloading the model files and double-check pyyaml==3.12.

Okay, it's working now.  The problem was that the model files were not properly downloaded previously using the script. I downloaded and extracted them manually. Now the demo code is working correctly without any modification to the code. Even I don't need to call the process_cfg() function explicitly as mentioned in my earlier comment.
Thanks for your great reply and your patience !! :)

Hi,
Unfortunately, I got the same size mismatch error while testing. My pyyaml version is also set to now to 3.12 as suggested.
command - bash experiments/scripts/test_ycb.sh demo_model_clutter
here are the logs:-

echo Logging output to output/demo_model_clutter/test_log.txt.2022-04-27_20-45-45
Logging output to output/demo_model_clutter/test_log.txt.2022-04-27_20-45-45
++ basename experiments/scripts/test_ycb.sh
python -m core.test_offline --pretrained output/demo_model_clutter --test --record --log --load_test_scene --egl --load_goal --test_script_name test_ycb.sh --test_episode_num 300 --num_runs 2 --model_surfix latest
pybullet build time: Apr 26 2022 03:11:02
This module depends on PyOpenGL.
Please run "!pip install -q pyopengl" prior importing this module.
Let's use 3 GPUs!
net_name: traj_feature_extractor
=== net option: 4 trainable param: [975232, 139840]  ===
schedule: [20000, 40000, 60000, 80000, 100000]
net_name: traj_feature_sampler
=== net option: 2 trainable param: [352800, 527360]  ===
schedule: [20000, 40000, 60000, 80000, 100000]
net_name: state_feature_extractor
=== net option: 2 trainable param: [352768, 527360]  ===
=== net option: 2 trainable param: [352768, 527360]  ===
schedule: [20000, 40000, 60000, 80000, 100000]
output_time: demo_model_clutter logdir: output/demo_model_clutter/PandaYCBEnv_DQN_HRL
video output: YCB_dqn_0w_16g_gaddpg_ycb_mix stat output: rollout_success.script_dqn_0w_16g_gaddpg_ycb_mix.yaml.txt
DEBUG: 1 1024
DEBUG: 1089 256
DEBUG: 1089 256
load policy weight: 1.460 from output/demo_model_clutter/DQN_HRL_actor_PandaYCBEnv_latest !!!!
load critic weight: 0.500 !!!!
load traj feature weight: 1.203 from output/demo_model_clutter/DQN_HRL_traj_feat_PandaYCBEnv_latest !!!!
load traj sampler weight: 1.156 from output/demo_model_clutter/DQN_HRL_traj_sampler_PandaYCBEnv_latest !!!!
load feature weight: 1.6373310089111328 !!!! from: output/demo_model_clutter/DQN_HRL_state_feat_PandaYCBEnv_latest step :220001
Let's use 3 GPUs!
net_name: state_feature_extractor
=== net option: 0 trainable param: [345152, 1053184]  ===
=== net option: 0 trainable param: [345536, 1053184]  ===
schedule: [8000, 16000, 30000, 50000, 70000, 90000]
DEBUG: 1 512
DEBUG: 513 256
DEBUG: 513 256
load policy weight: 0.863 from output/demo_model/DDPG_actor_PandaYCBEnv_latest !!!!
load critic weight: 0.439 !!!!
load feature weight: 12.371764183044434 !!!! from: output/demo_model/DDPG_state_feat_PandaYCBEnv_latest step :249921
start test time: 27_04_2022_20:45:56
==== loaded scene: scene_1 target: 021_bleach_cleanser idx: 8
Traceback (most recent call last):
File "/home/prem/anaconda3/envs/antipodal/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/home/prem/anaconda3/envs/antipodal/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/prem/prem_workspace/HCG/HCG/core/test_offline.py", line 413, in
test(run_iter=run_iter)
File "/home/prem/prem_workspace/HCG/HCG/core/test_offline.py", line 281, in test
gt_traj=input_exec_traj)
File "/home/prem/anaconda3/envs/antipodal/lib/python3.7/site-packages/torch/autograd/grad_mode.py", line 49, in decorate_no_grad
return func(*args, **kwargs)
File "/home/prem/prem_workspace/HCG/HCG/core/agent.py", line 190, in select_action
actions = self.policy.sample(feature)
File "/home/prem/prem_workspace/HCG/HCG/core/network_arch.py", line 223, in sample
mean, log_std, extra_pred = self.forward(state)
File "/home/prem/prem_workspace/HCG/HCG/core/network_arch.py", line 208, in forward
x = F.relu(self.linear1(state))
File "/home/prem/anaconda3/envs/antipodal/lib/python3.7/site-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/home/prem/anaconda3/envs/antipodal/lib/python3.7/site-packages/torch/nn/modules/linear.py", line 87, in forward
return F.linear(input, self.weight, self.bias)
File "/home/prem/anaconda3/envs/antipodal/lib/python3.7/site-packages/torch/nn/functional.py", line 1370, in linear
ret = torch.addmm(bias, input, weight.t())
RuntimeError: size mismatch, m1: [1 x 1025], m2: [1089 x 256] at /pytorch/aten/src/THC/generic/THCTensorMathBlas.cu:290

Could you try using only one GPU and see if that works? Sorry the test code assumes that only one GPU is used. Also does the script work previously when you load the correct model and config?

Hi,
I tried running with one GPU, still getting the same error. Yes, the demo script worked previously. But, this test script is not working now.

The test_ycb.py is for testing the low-level policy, so it should be encoding the expert plan as the plan latent for the low-level policy. Could you check if the plan latent has been encoded.

@liruiw
Thanks for guiding the error cause.
The issue was that in file core/utils.py, line 43 - "from OMG.ycb_render.robotPose import robot_pykdl"
Because this line is within a try clause, the error was not detected earlier.
During OMG installation, the kdl module didn't installed properly. I reinstalled it correctly and everything is working properly now.


[Removal]: Bald Marigold Walrus

Hotspot Name
bald-marigold-walrus
Hotspot b58 Address
11R25Uh4TaWDonGZYAGYWL7hEqbTGtFVSMqXdCeDwzgAtwNeunP
Discord Handle
No response
Hotspot Manufacturer
PantherX
Removal Reason
I set up the hotspot in the real location to provide the real coverage
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
Dear Helium Team:
I am a beginner to the helium network, and i am also work in a IOT company, when i first time heard of helium, i really think its a genius idea that running a network by people. So i brought some helium hotspots on the second-hand market on 12 Feb. But after running few days, i noticed they are not generating any reward, and not making any connection between other hotspots (witness others and send beacons). Then i searched some materials and joined the discord community last Friday. I realized there is a mechanism of deny list, and they are both in the list. However, i put them in the real location to provide the real coverage. Please check my set up and help me remove from the deny list. Thank you.

IoT company, more like mining farm.
Know nothing except how to mining in your basement.
Place your hotspot besides metal screen, what a genius

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


v6.3.0: Please remove gcloud namespace warning

What happened?
After upgrading to v6.3.0, Devspace seems to be utilizing the new gke-gcloud-auth-plugin under the hood.
There is an annoying feature of this auth plugin that prompts the user to confirm that they are targeting the correct namespace:
$ devspace build

warn Are you using the correct namespace?
warn Current namespace: 'argocd'
warn Last    namespace: 'default'

? Which namespace do you want to use?  [Use arrows to move, type to filter]
> argocd
  default

What did you expect to happen instead?
Just proceed without verifying the GKE namespace.
The build step doesn't even deploy anything to GKE, so I am guessing that this is some sort of peculiarity with the gcloud auth mechanism employed by Devspace.
Hopefully, this functionality is toggleable, and can be disabled when Devspace utilizes gcloud for authentication.
How can we reproduce the bug? (as minimally and precisely as possible)
Swap namespaces with kubectl, and try building an image that will be pushed to a Google Artifact Registry.
My devspace.yaml:
version: v2beta1

...
images:
  app:
    image: europe-west1-docker.pkg.dev/my-org/artifacts/my-image  # Google Artifact Registry
    dockerfile: ./Dockerfile

pipelines:
  build: |-
    build_images --all
...

Local Environment:

DevSpace Version: 6.3.0
Operating System: linux
ARCH of the OS: AMD64
Kubernetes Cluster:
Cloud Provider: google
Kubernetes Version: v1.25.3

Anything else we need to know?

@djfinnoy thanks for creating this issue! This warning comes directly from DevSpace and signals that the build was previously run in a different namespace, which shouldn't be related to gcloud. Since there a builds that require a kubernetes cluster (Kaniko etc.) Kubernetes is sometimes needed. You can disable this warning with:
devspace build ... --no-warn

Ah, I see. My mistake. Is it possible to build --no-warn into pipelines, or will we need to include it everytime we use the CLI?

@djfinnoy yes you can also do:
vars:
 DEVSPACE_FLAGS: '--no-warn'

which will always include this

Excellent, thank you.


Docker image build for servers, Jenkins release build trigger

Hi!
I created a docker build repository and would like to ask if you could put a docker build trigger inside your Jenkins release-build.
I would also like to add some branches like 'unstable' or other tweaks to build multiple docker images for testing purposes.
Basically I started this https://github.com/qwc/docker-terasology repo quite some time ago, but lost track of versions due to other tasks, so I thought about asking for a build trigger so I just do not have to keep track of current changes, except a dependency fails.
Maybe I am able configure a warning email inside docker when a build fails. :)
This is the docker repository: https://registry.hub.docker.com/u/qwick/terasology/
The repo description and surroundings are still in a draft state, but to get it really running I want to automate the process with the triggers, when this is running I plan to beautify the repo itself. :)
So, tell me your thoughts.

Sounds interesting. I'm not sure what exactly you would need. Just send a notification ping your way or is it neccessary to run the script from your repository from within Jenkins?
I don't think that running docker on Jenkins (slaves) is possible, but maybe @Cervator (our DevOps specialist) might know better.

Totally could with the right size, one of the DigitalOcean images comes pre-baked with Docker set up and everything :-)
Super neat topic and so much we could play with, just arghtime

Nah, a build on your jenkins server is not necessary, but possible. :)
I need you to do only one thing: to call a specific URL everytime a build succeeds, here some examples:
        # Trigger all tags/branchs for this automated build.
        $ curl -H "Content-Type: application/json" --data '{"build": true}' -X POST https://registry.hub.docker.com/u/qwick/terasology/trigger/<trigger-hash>/

        # Trigger by docker tag name
        $ curl -H "Content-Type: application/json" --data '{"docker_tag_name": "master"}' -X POST https://registry.hub.docker.com/u/qwick/terasology/trigger/<trigger-hash>/

        # Trigger by Source branch named staging
        $ curl -H "Content-Type: application/json" --data '{"source_type": "Branch", "source_name": "staging"}' -X POST https://registry.hub.docker.com/u/qwick/terasology/trigger/<trigger-hash>/

        # Trigger by Source tag named v1.1
        $ curl -H "Content-Type: application/json" --data '{"source_type": "Tag", "source_name": "v1.1"}' -X POST https://registry.hub.docker.com/u/qwick/terasology/trigger/<trigger-hash>/

(I've removed the trigger hash, so no external user is able to trigger builds atm.)
Through this docker API we could build every type of successful build: release, testing, nightly and different types if necessary: server (which I built the repo for), client (yes you can use docker even for GUI programs) and other which did not yet come to my mind.
Btw. this api looks like it's not so old, when I first started the terasology docker repo this menu option was not available at the docker system, or I've overlooked it completly... :D
The only thing for which you would need to contact me through a pull request would be to change dependencies in the Dockerfile  or maybe I'm able to add you to the docker-repo (not the github one!) too so you could manage the builds, tags and branches.
@Cervator Yes, time, that's why I lost track of the terasology releases between the creation of the Dockerfile and my post here. And the reason I want to automate that further. ;)

Cool stuff, that doesn't seem too bad :-)
I understand Artifactory also supports serving as a Docker registry, and in turn Bintray as well. We're thinking about setting up our formal binary distribution that way (in addition to GitHub as a secondary and Jenkins as tertiary). Any interest in helping out with that? :D

Oh, interesting that Artifactory is able to host docker repositories. Didn't see that coming. :D
For now I just wanted to automate the builds of my docker repo, but when you want to take the approach to a whole new level it's your decision to do that.
Well of course I can help a bit, Docker itself is quite easy, easier than I expected myself, when I started tinkering with it. I'm sure you will learn how to use it efficiently quite fast. ;)
But for Artifactory docker repo hosting you need the Pro or SaaS version, do you get that for the open-source project terasology? o.O

Hmm .. there's a plugin for Jenkins that sends out notifications, but not too configurable.
Maybe we'd really need to add a post-build step and use curl instead? Sounds like a cheap hack and also won't work on Windows machines..

Who needs windows machines these days? ;)
As long as the output of your build is platform independed, which is provided through using java.
Docker in the end is a linux (bsd too? o.O) only thing, so...

I meant that the machine that runs Jenkins could be a Windows machine, so curl wouldn't work. That said, my main concern is about running "arbitrary" shell scripts on Jenkins.
There's a Docker plugin for Jenkins - does it provide what you need?

Reading the description of the plugin you mentioned, it's more for the other way around, that a dockerhub repo hook triggers a Jenkins build (which may also build a docker image and uploading it). I need the opposite of that for my current approach. That Jenkins triggers a docker image build at dockerhub.
We could also write a small java program, which is executed by jenkins and which sends the required data to dockerhub.
Advantage: It runs on windows and doesn't need a linux tool. And you do not have to worry about docker on windows, because dockerhub builds the image not your jenkins.
Of course not suitable when you want to build the docker image yourself on your build server. ;)
Is your OS, where Jenkins runs, changing often?

A quick search on google resulted in docker-build-publish-plugin. What do you think of it?

That looks very promising.
But with that plugin you will build the docker image on your jenkins server and not on dockerhub. Which results in quite a bit traffic for the base images and only a little load for plugging the parts together.
And you need to configure a dockerhub account with all credentials.

Wouldn't we still publish the image to the registry? Yeah I don't think we'd want to host it in Jenkins but it would be nice to have a proper process in there to create it. Account shouldn't be too much hassle :-)
But yeah, it is more work, sure, I get that. Web trigger is easy for current setup. Should we just add a single trigger to the end of the DistroOmegaRelease job for now? Then when somebody has time and energy to mess with Jenkins we can get fancier there later.

Yeah, that was my goal with this issue! ;)
I'll send you the trigger links and json data for the curl calls during the weekend (can't predict when I'll have time for managing the dockerhub repo/project).
Regarding the docker-build-publish-plugin: I have my own little server where I want to install a jenkins (through docker, hehehe) anyway, so I may have time the upcoming weeks for playing around with this plugin.

To continue this path, let me know when you have time to set up the triggers. :)

Triggers set up in a dedicated new Docker job: http://jenkins.terasology.org/job/DistroOmegaReleaseDocker/

After I've set up a own jenkins instance I've also put a job up which monitors your build page for build number changes to build the image tagged as 'latest'.
The only thing I'm still missing is a properly tagged image with the version as a tag.
Thought about parsing the github release page of the project to get the version tag without checking out the complete repository. But I've put that aside because it's too errorprone when you're tagging the successful build later than my job runs (which is daily ~midnight).
If you have the git tag available at your "DistroOmegaReleaseDocker" job, you could change the source_name to "master" and the docker_tag to the current version tag.

@qwc would the version file at http://jenkins.terasology.org/job/Terasology/lastSuccessfulBuild/artifact/build/resources/main/org/terasology/version/ help?
That's generated for every engine build, admittedly, while the download goal is the Omega zip with all modules added. That usually becomes available a few minutes after the version file is updated.
There is some logic in our Launcher project that goes and scrapes some info out of the paired Jenkins jobs to make a series of stable/unstable builds available in a drop-down, like https://github.com/MovingBlocks/TerasologyLauncher/blob/develop/src/main/java/org/terasology/launcher/game/TerasologyGameVersions.java#L86

Yep, that should work. Thanks for the hint! :+1:
I'll test that as soon as I'm back at home. ;)
When this job works too, you could delete your docker job because I'm then providing a solution for all image build possibilities by myself.

Well, after months with no time at all for things like terasology, etc. I've finally managed to set up a versioned build of the image.
Sorry for the delay, in the end it's all hobby. ;)
So, the "latest"-build is built by dockerhub through a build-trigger from my own jenkins instance which checks your "versionInfo.properties" from your stable build periodically ( once daily, midnight).
Another job, also checking the TerasologyStable build, builds the image on my server and tags it with the current version extracted from the "versionInfo.properties", the resulting tag is: $engineVersion-$displayVersion
At the time of writing this is "1.2.1-alpha".
So that I've now managed to set this all up (1 hour of playing around...) I would like you to disable the "DistroOmegaReleaseDocker" build job on your jenkins, because this is now completly handled through my own jenkins instance. :)
Already more than 175 pulls of the image, hopefully more happy users in the future.
Sooo, thanks for your support in making this film ... errr... docker image.
If anything goes wrong (with the image), or when there are further questions, don't hesitate to ask. :)

And last but not least I've also created a build job to build the nightly Omega release.
docker tag "dev-latest" or versioned with (at the moment): "dev-1.2.2-SNAPSHOT"
see: https://hub.docker.com/r/qwick/terasology/tags/
Happy headless server debugging for those of you who might use linux and docker for developtment. :)

Thanks again for sticking with this so long! We're all here for the hobby so we understand things take time. Heck this one only took a little longer than a year to finish! :D
I've added some info to our Playing.md covering this approach, and will consider that the commit that'll finish this issue :-)
Disabled our Jenkins job for now and also added you to the credits for good measure!
175 pulls already? Where are all these users hiding :8ball:
I wonder if we should try to default this server's config to use JoshariasSurvival, since it has a fair bit more content than the default Core.

Cool, thanks. All the important information is covered by the doc, nice! :)
Yeah, more than a year. Well, better late than never. xD

Cool, thanks. All the important information is covered by the doc, nice! :)
Yeah, more than a year. Well, better late than never. xD


generate_bundle: add logging

use absolute dir for REL
specify default value for OPERATOR_SDK
pass a logfile
use -x for more debug info

This is required for https://github.com/infrawatch/smart-gateway-operator/pull/143, due to the changes in build/stf-run-ci/tasks/create_catalog.yml


Critical error: negative currency not allowed

Running Sia 1.0.4
Critical error: negative currency not allowed
Please submit a bug report here: https://github.com/NebulousLabs/Sia/issues
goroutine 93688 [running]:
runtime/debug.Stack(0x7a, 0x0, 0x0)
        /usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
        /usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Critical(0xc42e4445b0, 0x1, 0x1)
        /home/luke/go/src/github.com/NebulousLabs/Sia/build/critical.go:19 +0xb7
github.com/NebulousLabs/Sia/types.Currency.Sub(0xc420120a00, 0x0, 0x0, 0x0, 0x0, 0xc432981140, 0x2, 0x5, 0x0, 0x0, ...)
        /home/luke/go/src/github.com/NebulousLabs/Sia/types/currency.go:183 +0x16c
github.com/NebulousLabs/Sia/modules/host.(*Host).removeStorageObligation(0xc4202b6100, 0xdae0b8, 0x0, 0x0, 0x0, 0xc432981140, 0x2, 0x5, 0x0, 0xc432981170, ...)
        /home/luke/go/src/github.com/NebulousLabs/Sia/modules/host/storageobligations.go:528 +0x1ca0
github.com/NebulousLabs/Sia/modules/host.(*Host).threadedHandleActionItem(0xc4202b6100, 0xdd75cb2b0505aa3e, 0x6aea30a358f92b4f, 0x2ba5294c49f3fc82, 0x3018102fbbc64d5a, 0xc43ddc64f0)
        /home/luke/go/src/github.com/NebulousLabs/Sia/modules/host/storageobligations.go:671 +0x2ebf
created by github.com/NebulousLabs/Sia/modules/host.(*Host).ProcessConsensusChange
        /home/luke/go/src/github.com/NebulousLabs/Sia/modules/host/update.go:309 +0x249

These errors are generally benign. It means that the host tried to subtract some number of siacoins and it underflowed. So your hosting metrics may be skewed a little, but it won't affect anything important.
We have a fairly large host refactor open (#1501), so we can revisit this bug if it's reproducible after the refactor is merged.
Thanks!

I don't think that the refactor touches this bug, but I have a decent idea of what is causing the failure. I'll open this until I believe I have fixed the root cause.
But as @lukechampine it's just an accounting thing, the host is incorrectly computing revenue.

Now I'm getting this error on day basis, and to me seems that after it the host.log file freeze
is there any more info that you may need in order to debug it?
here my host.log last lines

2017/01/01 15:31:49.531672 storageobligations.go:527: Rejecting storage obligation expiring at block 85072, current height is 85075. Potential revenue is<PHONE_NUMBER>21153409884225536.
2017/01/01 16:39:30.645876 storageobligations.go:669: Full time has elapsed, but the revision transaction could not be submitted to consensus, id eb037ba88b0446134844477d63253e179ff9f3651e51153a07106ddd7f6468ae
2017/01/01 16:39:30.645939 storageobligations.go:527: Rejecting storage obligation expiring at block 85077, current height is 85080. Potential revenue is<PHONE_NUMBER>14753412937678848.
2017/01/03 20:50:11.335568 host.go:258: SHUTDOWN: Logging has terminated.
2017/01/03 20:51:47.416140 dependencies.go:105: STARTUP: Logging has started.
2017/01/03 20:51:47.451836 persist.go:182: WARN: NetAddress '' loaded from persist is invalid: missing port in address
2017/01/03 20:52:03.250356 upnp.go:109: WARN: could not automatically forward port 9982: no UPnP-enabled gateway found
2017/01/03 20:52:03.250396 network.go:85: ERROR: failed to forward port: no UPnP-enabled gateway found
2017/01/04 23:16:11.745186 storageobligations.go:669: Full time has elapsed, but the revision transaction could not be submitted to consensus, id 8b231b553aa60fd19f2675c62ea33828e302f4dd1198631699978123482d5ca8
2017/01/04 23:16:11.761466 storageobligations.go:527: Rejecting storage obligation expiring at block 85576, current height is 85579. Potential revenue is<PHONE_NUMBER>14753412937678848.

Yeah I think that error is appearing as you complete your contracts. It will keep producing annoying output. Unfortunately I'm not sure there's much we can do in the short term, I'm not even sure there's a way to clear the inconsistent state within your machine that's causing the problems.
I will reiterate that I'm 90% confident it's purely a cosmetic bug - it thinks it has 0 revenue when it's actually got revenue (revenue which IS hitting the wallet, despite the host's confusion). Therefore it's fairly low priority vs. v1.1 coming out in January.
But we will do our best to have this fixed in v1.2 (Feb-March target)

@DavidVorick was this ever fixed?

Still getting it sometimes on the latest master build. But it's less frequent than in 1.2.2

Duplicate of #2346
Recommendation to devs: Close


Rebuilt environment pages

The documentation is currently very much out of sync with the docstrings. I rebuilt all markdown files from the master branch of the Gym repository. Unless I'm mistaken, there is still no versioning, so we should probably keep the docs close to the master branch (?).

Im surprised this isn't done by some automated system on commit or build etc. @trigaten Any ideas?


setPrototypeOf not supported in IE10

using root method causes exception in IE10 test:
IE 10.0.0 (Windows 7 0.0.0) ERROR
  Object doesn't support property or method 'setPrototypeOf'

https://travis-ci.org/wix/stylable-components/builds/259848237?utm_source=github_status&utm_medium=notification

@idoros  @nadavov should we support IE10?

the answer was no


2024 winter

Create pull request from edited branch of to main branch of your fork
By the way, see example in repo readme, format is wrong


Update information about mailing lists

Just a quick change to the documentation about the mailing lists.  I was unable to get the site running locally (seems to require a "global" 0.12.3 Elm, that cannot be satisfied via building from source), so this will need to be checked.

Okay, should be resolved by ae85893dd4782d18452aac3864025944c208f230, thank you for the PR!


Dequantization doesn't work for AnimatedMorphCube

Foudn in #10314. The AnimatedMorphCube model loads and animates as expected in its normal glTF format, but its quantized version renders much smaller.

Normal
Quantized

When the cube is then animated, it is very skewed. I thought it may be because it's actually morphing to the correct positions, but this is only happening along one axis (the cube does not grow in size vertically).

Removing the animations array from the glTF does not make a difference, so something must be off with the dequantization itself.

As of the 1.97 release, it looks like the regular AnimatedMorphCube model is no longer extremely large. However, the quantized version is still buggy:

regular
quantized


raw_observe_property (string expected, got function)

mpv 0.27.0-416-g386e8cd16d (C) 2000-2017 mpv/MPlayer/mplayer2 projects
 built on Fri Nov 24 16:14:12 EST 2017
ffmpeg library versions:
   libavutil       56.0.100
   libavcodec      58.4.102
   libavformat     58.2.102
   libswscale      5.0.101
   libavfilter     7.2.100
   libswresample   3.0.101
ffmpeg version: N-89178-ga1630b40e8

When trying to start the script with Shift+w I get the following error.
[webm]
[webm] stack traceback:
[webm]  [C]: in function 'raw_observe_property'
[webm]  mp.defaults:351: in function 'observe_property'
[webm]  /home/flat/.config/mpv/scripts/webm.lua:791: in function 'observe_properties'
[webm]  /home/flat/.config/mpv/scripts/webm.lua:813: in function </home/flat/.config/mpv/scripts/webm.lua:811>
[webm]  (tail call): ?
[webm]  mp.defaults:202: in function 'fn'
[webm]  mp.defaults:60: in function 'handler'
[webm]  mp.defaults:339: in function 'handler'
[webm]  mp.defaults:458: in function 'call_event_handlers'
[webm]  mp.defaults:495: in function 'dispatch_events'
[webm]  mp.defaults:451: in function <mp.defaults:450>
[webm]  [C]: ?
[webm]  [C]: ?
[webm] Lua error: mp.defaults:351: bad argument #3 to 'raw_observe_property' (string expected, got function)

Should be working now, see 9bbae70. I wonder how that didn't cause an error for me...

Works fine now, thanks! Was it changed upstream recently, or has it always required three arguments?

It always required three arguments (git blame on defaults.lua says observe_property wasn't touched in the last 4 years), I just forgot it, and it, somehow, worked without crashes for me.


NPE crash when disconnecting from Multiplayer server, loops to crash screen.

When disconnecting from a multiplayer server, I get a null pointer exception that seems to be related to Clef. I am unsure if the issue is with Clef or with VanillaFix, but when clicking the "Back to Main Menu" button, the game seems to loop back to the same crash, and I am forced to close the client and re-launch the game each time.
Crash report:
https://paste.dimdev.org/uwocahihih.mccrash
Minecraft version: 1.12.2
Forge version: <IP_ADDRESS>50
VanillaFix version: 1.0.9-97
Clef version: 7.0.0
iChunUtil version: 7.1.4
See also https://github.com/iChun/Clef/issues/13

Not an issue, Clef just keeps crashing when you go to the main menu, and VanillaFix is just catching all the crashes.

Uh, I also have a similar issue - is there a way to get this to be a bit less sensitive?

It's clef's fault, without VF it'll still crash, like Runemoro said it just catches all the crashes happening.


cli: flynn remote add

CLI for managing git remotes for flynn applications
Closes #1762

@titanous comments addressed and tests added.

It looks like the command needs to be added to the list in main.go

LGTM pending my last two comments.


Update README.md

changed to reflect new dev portal readme and new documentation links

This one looks good.


get SharedPrefrences for update value

Hi,
i need to update some values in sharedPreferences in onRunJob(Params params) method but i don't have a context in Job class. How can i do it ?
Is there an info that calls me when my periodic job has run ? (last time)
Thx for support ! Good Lib ;)
F.

You can use getContext() inside of onRunJob(params).


GHC 8.8.4 & 8.10.2

Thanks! Did you investigate if any extra deps can be removed?

/azp run

CI rerun seems broken - could you rebase or push an empty commit to force a rerun please?

Might be related to https://www.stackage.org/blog/2020/08/ghc-8-10-2-windows-workaround

Yup: zlib             > ghc.exe: could not execute: C:/GitLabRunner/builds/2WeHDSFP/0/ghc/ghc/inplace/mingw/bin/ld.exe

ping @jneira help!

ugh, that workaround would be doable with some sed magic over the ghc config file but i think the ghc team ia gonna release a new version 8.10.3 with the fix so maybe the easy way is to exclude 8.10 from ci temporary:
https://github.com/haskell/ghcide/blob/84af588fa00717ad5f624dd600bfd0b0c6060090/.azure/windows-stack.yml#L8-L9
... or keep a stack8101.yaml and use it for windows until 8.10.3 is released (more user firendly)

I'm happy with a temporary exclusion @jneira, why don't you send a separate PR to do that?
Or alternatively @domenkozar you can make the change in this PR.

Yeah, will do but i would prefer to keep a stack yaml for ghc-8.10.1

Hopefully this will pass now :)

Merged, thanks!


E S LINT!!!!

Important rules:

Imports order: https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/order.md
Maximum lines (200 lines) and maximum statements (22 statements)
Camel case variable names, always
Arrow function declaration, always
Use === instead of ==, always

All these rules support auto-fixing.

Maybe let's wait until Bradley's PR is in, because it's likely to cause merge conflicts or issues passing checks if not. What do you think?

hahahahahahaha might want to restart this one...

hahahahahahaha might want to restart this one...

Ahhh :dizzy_face:

@tim-macphail Let's merge this now

@cloudyyoung my only concern is that it will make it harder for other devs to pass CI checks, so we'll have to make sure everyone's VSCode format on save is doing what it should be doing and all that with stuff in .vscode

@cloudyyoung my only concern is that it will make it harder for other devs to pass CI checks, so we'll have to make sure everyone's VSCode format on save is doing what it should be doing and all that with stuff in .vscode

If all devs have all recommended plugins installed then we should be good


Issue 322

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
[x] Make sure you are making a pull request against the dev branch. Also you should start your branch off dev branch.
[x] Check you have added tests that prove your fix is effective or that your feature works.
[ ] Check your code additions will fail neither code linting checks nor unit test.
[x] Check you added any notable changes to the CHANGELOG.md file.

Description
Please describe your pull request.
💔Thank you!

Codecov Report

Merging #347 into dev will increase coverage by 0.46%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##                dev     #347      +/-   ##
============================================
+ Coverage     81.87%   82.33%   +0.46%
- Complexity      268      276       +8
============================================
  Files            91       94       +3
  Lines           866      889      +23
============================================
+ Hits            709      732      +23
  Misses          157      157

Impacted Files
Coverage Δ
Complexity Δ

app/Http/Requests/EventStoreRequest.php
100% <100%> (ø)
2 <2> (?)

app/Repositories/EventRepository.php
100% <100%> (ø)
3 <3> (?)

app/Http/Controllers/EventController.php
100% <100%> (ø)
3 <2> (?)

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 111cf6a...4fabb1f. Read the comment docs.

@James-N-M looks like github is having a problem https://status.github.com/messages

@James-N-M looks like github is having a problem https://status.github.com/messages

@James-N-M github having some issues https://status.github.com/messages

@Hasnayeen what could the conflict on change log be though ???

@Hasnayeen the issues with github really messed me up last night, I'm honestly going to fork again and submit a new pr for this issue, after i copy paste all of this changed code in my new fork branch 👍

closing to open a new one


Add caffemodel loading and parsing

Implements #267
I decided to create a PR to merge the current status of developement, as the next steps (parsing deploy.prototxt and creating a static operations DAG) require some bigger changes and more input from you. This PR adds the ability to load and parse *.caffemodel files directly within JavaScript (using protobuf decode) and extract the weights for usage in deeplearn.js.
In scripts/build-caffe-proto.sh, the latest caffe.proto file is pulled from https://github.com/BVLC/caffe/blob/master/src/caffe/proto/caffe.proto and converted into a JavaScript and a Typescript definition file using protobuf.js and stored in src/contrib/caffe.
Caffemodel
The *.caffemodel file contains the model definition, layer parameters and weights after a specific phase (train, test), as well as the preprocessing offset (training mean, crop parameters, etc.). Unfortunately, many *.caffemodel files contain all layer definitions (and model graph) from the training phase (e.g. cross validation splits, labels, etc.) without the correct information about the phase (train, test). The *.caffemodel is a binary proto and can be parsed with the caffe.proto definition and protobuf.js as a dependency.
Prototxt
The *.prototxt file contains the model definition and parameters for a specific phase (train, test). Most of the times, authors provide a deploy.prototxt file containing the test definition of the model - which contains only the relevant layers for inference. The *.prototxt is a textual proto definition and can be parsed with a custom parser (e.g. https://github.com/brotchie/protobuf-textformat/blob/master/src/parser.js) and the parser dependency (e.g. Parsimmon).
Recommendation for Deeplearn.js
In my opinion, the best way to support Caffe (models) would be to integrate caffemodel parsing into the core of deeplearn.js (as implemented in this PR) - such that properly generated caffemodel files (that contain the correct phase variables per layer) can be loaded directly. It would be nice to also provide a script to convert caffemodels with missing phase variables to correct caffemodels e.g. using python, and eventually host these models on https://storage.googleapis.com/learnjs-data/checkpoint_zoo/ as well.
As a second option, one could provide a seperate module (e.g. deeplearn-caffe-utils.min.js), to load and parse *.prototxt files and apply the test structure to the caffemodel. This way, the parser dependency would not affect the size of deeplearn.js while making it possible to easily load all available caffe models directly within JavaScript (without compiling).
Testing the SqueezenetCaffe model
Compile models/squeezenet and replace the following line in demos/imagenet/imagenet.ts
import {SqueezeNet} from 'deeplearn-squeezenet';

with
import {SqueezeNetCaffe as SqueezeNet} from 'deeplearn-squeezenet';

Unfortunately I couldn't run this anymore after the rebase on master.

A simple example for debugging
This is a simple snippet to load SqueezeNet weights from the original model:
<!doctype html>
<html>
  <head>
    <script src="dist/deeplearn.js"></script>
  </head>
  <body>
    <script>
      var GITHUB_CDN = 'https://rawgit.com/DeepScale/SqueezeNet/master/SqueezeNet_v1.1/';
      var model = new deeplearn.CaffeModel(GITHUB_CDN + 'squeezenet_v1.1.caffemodel');
      model.loadVariables();
    </script>
  </body>
</html>

Now you can open the developer tools and see the parsed model definition in model.caffemodel.
TODOs
There a few TODOs that I marked directly in the source code, e.g.

[ ] storing variables as Maps instead of objects
[ ] naming concentions for the weights (besides conv), e.g. batchnorm, etc.
[ ] support more general preprocessing, such as cropping

This change is

Wow, this is wonderful. Thank you for the detailed notes, it is really helpful with this large PR.
The comments I have are high level:

I'm a little hesitant putting the typings and parser in src/ because of bloat (we compile every file and serve it with every bundle request). We've moved models out to their own npm packages so they can be used independently, and it seems like we'll only need to use the caffe files when we've got a model that's being ported from caffe. Would it be possible to put these utils in models somewhere to be shared among multiple caffe models?
Can you put the caffe squeezenet in its own npm package? I don't want to bloat that one either since people will be directly using it.
caffe.js does automatic model parsing and execution right? I think it would be nice to see an end to end demo of that of some model (something other than squeezenet would be cool). I can put the weights on GCP for you.

Overall this is amazing. Thank you for putting this together!

Review status: 0 of 11 files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

scripts/build-caffe-proto.sh, line 16 at r1 (raw file):

# limitations under the License.
# =============================================================================
set -e

can you put a big comment at the top here explaining what this is for

src/index.ts, line 57 at r1 (raw file):

export {GPGPUContext} from './math/webgl/gpgpu_context';
export {Model} from './model';
export {CaffeModel} from './contrib/caffe_model';

this is what worries me since we'd be unconditionally compiling this into the bundle

src/contrib/caffe_model.ts, line 26 at r1 (raw file):

  // TODO Map structure not compatible with object structure used in
  // models.Squeezenet

what exactly isn't compatible?

src/contrib/caffe_model.ts, line 31 at r1 (raw file):

   * @type {Map<string, NDArray>}
   */
  protected variables: Map<string, NDArray>;

we should try to avoid map, you can just use a regular associative array:
protected variables: {[varName: string]: NDArray};

Comments from Reviewable

Follow up thought:
We should make a new directory in models for Caffe with its own package.json. Any caffe model will depend directly on that public API. This makes dependencies much saner and allows us to version the Caffe logic.
Does this make sense?

Review status: 0 of 11 files reviewed at latest revision, 4 unresolved discussions.

Comments from Reviewable

One more follow up thought:
I think we're going to separate our repository into several repositories under a deeplearnjs github organization. We were thinking all of your Caffe porting logic would live in its own deeplearn-caffe repo, with its own npm package that we can let you own.
Would that make sense?

Review status: 0 of 11 files reviewed at latest revision, 4 unresolved discussions.

Comments from Reviewable

Hi @nsthorat
Thanks for reviewing the code and for your suggestions.
I think putting this code in a separate module is a very good idea (e.g. similar to the model code), as it contains a lot of code that most users might not need (the proto compiled src/contrib/caffe/caffe.js file is gigantic). Then Caffe models can depend on this code and use it when needed - I like this a lot. I think, separating into different projects is definitely good idea in the long term.
However, from my point of view I think it might be too early to separate code into different repos instead of a monorepo (with multiple modules). Just think about that this code and all models will strongly depend on a common model interface and a common build tool chain. I am pretty sure that both things will change quite a bit in the common weeks and synchronous changes throughout multiple repos are a nightmare.
Hence, my recommendation would be to put the code of this MR into a models/caffe directory and build a models/squeezenet_caffe that uses the caffe weights, but in the same repo. It can be separated out anytime once the interfaces are stable. What do you think about this? Of course if you want to split it to a separate repos I am perfectly fine ;)
One more thing that I am struggeling with. Could you point me into the right direction of naming conventions for layer weights when dumping the weights to files (scripts/dump_checkpoints/tensorflow_checkpoint_dumper.py#var_name_to_filename) which you also  use in model::variables? I am a bit lost especially for non Conv/FC layers. Thanks a lot!
Best,
Christoph

Review status: 0 of 19 files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

models/caffe/caffe_model.ts, line 26 at r1 (raw file):
Previously, nsthorat (Nikhil Thorat) wrote…
what exactly isn't compatible?

I used ES6 Maps, but replaces them with associative arrays

models/caffe/caffe_model.ts, line 31 at r1 (raw file):
Previously, nsthorat (Nikhil Thorat) wrote…
we should try to avoid map, you can just use a regular associative array:
protected variables: {[varName: string]: NDArray};

Done.

models/caffe/scripts/compile-proto.sh, line 16 at r1 (raw file):
Previously, nsthorat (Nikhil Thorat) wrote…
can you put a big comment at the top here explaining what this is for

Done.

src/index.ts, line 57 at r1 (raw file):
Previously, nsthorat (Nikhil Thorat) wrote…
this is what worries me since we'd be unconditionally compiling this into the bundle

Done, moved to models/caffe for now.

Comments from Reviewable

We're actually going to be splitting the toolchain up, it's getting really out of hand to figure out where things intersect. It seems like most ML libraries are making a separate models repository, so I think we're going to follow suit. It will also logically separate them so when we try to build things we realize that we should try to test them with unit tests and not directly with demos.
For checkpoint dumping, we just replace any non-alphanumeric characters with "_". As long as you follow that you should be okay.
Quick question - is there an example of automatic model structure porting? Am I missing that somehow?

Reviewed 2 of 30 files at r3.
Review status: 1 of 19 files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

models/caffe/caffe_model.ts, line 22 at r3 (raw file):

import {Model, NDArray} from 'deeplearn';

export class CaffeModel implements Model {

can this be abstract?

models/caffe/caffe_model.ts, line 26 at r3 (raw file):

  /**
   * Model weights per layer
   * @type {{[varName: string]: NDArray}}

no need for type

models/caffe/caffe_model.ts, line 32 at r3 (raw file):

  /**
   * Preprocessing Offset
   * @type {NDArray}

no need for type

models/squeezenet-caffe/demo.html, line 15 at r3 (raw file):

    resultElement.innerText = 'Loading squeezenet...';

    // If dl isn't loaded, wait 1 second.

you can remove this now

Comments from Reviewable

Hi guys, here is a short update on my (very good) progress:

I added support for parsing prototxt models and protobinary files (e.g. mean files)
I added Caffe model parsing to Deeplearn.js math operations (using the math module)
I added a CPU implementation for LRN (which is needed for many models of Caffe Model Zoo)
I added a few models to test (GoogLeNet, GoogLeNet with Batchnorm, AgeNet, GenderNet, VGG16 crashes the browser unfortunately)
I moved a lot of functionality to separate reusable packages (https://www.npmjs.com/package/prototxt-parser, https://www.npmjs.com/package/dag-iterator, https://www.npmjs.com/package/caffe-proto)

I had/still have a lot of problems with the issue that Caffe computes the output dimensions of Conv and Pool layer (https://github.com/BVLC/caffe/issues/1318 and https://github.com/BVLC/caffe/issues/4252) differently to Deeplearn.js (almost in every model). This is something that we should fix somehow.
I actually believe, that the code of this branch should go into a separate repo, so I can faster fix some rough edges, use demos on gh-pages, include the caffe_models in the same repo etc. What do you think about this idea?
One more thought: I think, that we could easily add pure support to a lot of other DL frameworks (Caffe2, TF, Keras) in the same way this library does (like deeplearn-kears, deeplearn-tensorflow, etc.) - as many of them also use protobuf under the hood. I will put together a demo of Tensorflow once I am through with this commit.
Here are to samples to show you how cool and easy the caffe models can be used:
// AgeNet from https://gist.github.com/GilLevi/c9e99062283c719c03de
// Weights are served locally, mean and model are served from Github
export class AgeNet extends CaffeModel {

  // download model from
  // https://gist.github.com/GilLevi/c9e99062283c719c03de
  static caffemodel = 'age_net.caffemodel';
  static prototxt = 'GilLevi/c9e99062283c719c03de/raw/ddd9cf649c323041ee6e4731ff45636a09261597/deploy_age.prototxt';
  static meanfile = 'GilLevi/AgeGenderDeepLearning/master/models/mean.binaryproto';

  // Target labels
  static labels = ['(0, 2)','(4, 6)','(8, 12)','(15, 20)','(25, 32)','(38, 43)','(48, 53)','(60, 100)'];

  constructor(math: NDArrayMathGPU) {
    super(math, MODEL_DIR + AgeNet.caffemodel, GITHUB_GIST + AgeNet.prototxt, GITHUB_CDN + AgeNet.meanfile);
  }
}

// SqueezeNet from https://github.com/DeepScale/SqueezeNet/tree/master/SqueezeNet_v1.1
// Served entierly from Github
export class SqueezeNet extends CaffeModel {

  // model served entirely from github.com
  static caffemodel = 'DeepScale/SqueezeNet/master/SqueezeNet_v1.1/squeezenet_v1.1.caffemodel';
  static prototxt = 'DeepScale/SqueezeNet/master/SqueezeNet_v1.1/deploy.prototxt';

  // Target labels
  static labels = IMAGENET_CLASSES;

  constructor(math: NDArrayMathGPU) {
    super(math, GITHUB_CDN + SqueezeNet.caffemodel, GITHUB_CDN + SqueezeNet.prototxt);
  }
}

Cheers guys!

Hey Christoph,
Thanks for the detailed notes. I just wanted to let you know we haven't forgotten about you, we've just been busy with NIPS / vacations / etc. Daniel and I are going to both be back in the office and Tuesday and we'll chat about this work in person since it's a large change. I'm so sorry about the delay, but I promise we'll sync soon!

no worries, I assumed that you guys must be crazy busy catching up with everyone after NIPS; congrats btw. also from me for the best demo award ;) let me know when you are back and want to discuss current state and next steps for this feature!


Cannot read property 'type' of null

Every time I type and/or save a file I get the following message which is quite frustrating.

I disabled all extensions then it went away, so I re-enabled them till I found out that it was  eslint.
I've done some research and found that it might be related to eslint.nodePath setting.
However, I'm not entire sure what to put there I tried several things and none fix the issue.
None of the eslint settings have been modified in vscode.
This is our package.json file: https://gist.github.com/Rojoss/416dd4474ccbdd7d1cc2237b6e124214
If you need any other information let me know would love to see this fixed.
Here is the full stack trace from the console.
messageService.ts:126 Cannot read property 'type' of null
e.doShow @ messageService.ts:126
e.show @ messageService.ts:105
(anonymous function) @ mainThreadMessageService.ts:64
n.Class.derive._oncancel @ winjs.base.raw.js:1641
t.showMessage @ mainThreadMessageService.ts:34
t.$showMessage @ mainThreadMessageService.ts:28
e.handle @ abstractThreadService.ts:34
s @ ipcRemoteCom.ts:275
f @ ipcRemoteCom.ts:231
_combinedTickCallback @ internal/process/next_tick.js:67
_tickCallback @ internal/process/next_tick.js:98

I thought I fixed this a while ago. Which version of ESLint extension and VS Code are you using?
Can you share the whole project? Would help to investigate why you see this.

Ugh, I didn't get a notification for this so I'm sorry for the extremely late reply.
ESLint version is 3.19.0
VSCode is the latest version 1.11.2
I'm not really able to share the project as it's private for work.
If it's really needed I could probably set up a repo with a similar project to reproduce the issue.
Hopefully I'll be able to receive notifications next time.

@Rojoss you need to update the ESLint VS Code extension as well (1.2.8 is latest).
Will close if you can still reproduce the error on latest setup.

Since this has been happening for us from 1.11.2 through 1.2.11, @Rojoss' silence likely didn't mean "fixed". If more help is needed with reproduction steps, let me know.


Update Leeway to 0.8.1

Description

Updates Leeway to 0.8.1
Related Issue(s)

N/A
How to test

N/A
Documentation

N/A

@aledbf How do I build a new VM image?

Hi @mads-hartmann , this should help you build an image: https://www.notion.so/gitpod/Running-Github-runners-in-GCE-VMs-6ccd9c876abb4061b62671548279bca7

I see there's a target in the makefile but I wasn't sure which GCP project to use for this ☺

I believe it uses this project, https://console.cloud.google.com/compute/instances?authuser=0&project=public-github-runners to run the VMs. You can see images at https://console.cloud.google.com/compute/images?tab=images&authuser=0&project=public-github-runners.

@mads-hartmann I just built gh-runner-202312112146 from this branch via
gcloud auth application-default login --no-launch-browser
gcloud auth login --no-launch-browser
gcloud config set project public-github-runners
cd vm
make build-actions-runner-image

Thanks @kylos101 - I bumped the VM image with the one you created and updated the READMEs to link to the notion document so it's easier to discover in the future 🧡


CHANGELOG.md

Hey guys, I'm implementing opentelemetry and every time I access this repo a new version exists (at least a bug fix version).
It is really difficult to know what is going on if a simple change log is absent. I would be really nice to have one.

Should be solved as part of https://github.com/open-telemetry/opentelemetry-helm-charts/issues/78


(Option to) remove red border

Is your feature request related to a problem? Please describe.
This theme is practically perfect, it's just that the red border is very distracting, caused by the following JSON:
        /* https://code.visualstudio.com/api/references/theme-color#window-border */
        "window.activeBorder": "#ff0000",
        "window.inactiveBorder": "#ff0000",

Describe the solution you'd like
If you'd like to remove it I wouldn't mind: otherwise, you could just provide a second theme in the bundle that removes it, eg: signed-dark-pro-borderless.color-theme.json
Describe alternatives you've considered
I do just have them commented out in my local copy of the json file. Not a big need, just wanted to request!

@samgovier Would please give me steps to reproduce? Perhaps a screenshot even?

I made a pull request with the changes that also has screenshots. Feel free to change it yourself if you prefer.
#2 : red window border removal
Are you using Linux or Mac? I'm guessing it doesn't show up on those systems: I can see it on Windows.

I'm on Linux, and it doesn't show. Thanks for the PR

I've just released a minor update, v1.1.0, check it out the close this issue if it's addressed

Yep looks great. Thanks Alex!


[honister] Complete Milestone 17

Merged to other branches as well:
53d3b8f59..5402d5d1d  honister -> honister-next


[Feature Request] - Assets caching and loading on demand

[X] Review the documentation: https://docs.viromedia.com/
[X] Search for existing issues: https://github.com/viromedia/viro
[X] Use the latest ViroReact release: https://docs.viromedia.com/docs/releases

Description
It's crucial that there should be some caching mechanism for assets on application start for faster loading times and for assets reuse.
Also It will be great to have some kind of bundling for assets to load them on demand. Something like AssetBundles in Unity

Hey Vlad,
This is a limitation of React Native itself.
If you'd like to "bundle" assets, you can either build in release, or include them in the iOS/Android projects. Then when you refer to them in React Native, simply pass in the filepath to the files on disk using { uri : file://path/to/file } rather than a require().
Something that might help with the slow loading times is to use your local IP address (rather than the ngrok address) or, if you have an Android device, you can consider attaching the device to your computer using USB and reverse tether with adb reverse tcp:8081 tcp:8081.
You can also see if there are 3rd party React-Native libraries that help with this bundling issue too.


LibreCores CI Styling

[ ] - Create a custom theme Simple Theme plugin
[ ] - Deploy this theme to the repo and then setup automatic deployment

Not actually required for the demo. Just a look-and-feel (+) maybe some UI enhancements


Adding some new functions to the calculator.

I have added these two functions, binary to decimal and decimal to binary conversion to the calculator. please assign me this issue.

@saransh484 when adding new functions to this calculator. please declare those buttons inside the other function div. By doing this the responsiveness will be there.

Thanks for the advice, I'll keep that in check.


AttributeError when calling model_dump on string response

Describe your question
I installed it through git, not docker.
I have built successfully, and I can see the user page at http://localhost:3000. When I input, the response is as follows
Additional context
File "/home/eric/.cache/pypoetry/virtualenvs/opendevin-B_QcU69S-py3.11/lib/python3.11/site-packages/litellm/llms/openai.py", line 414, in completion
raise e
File "/home/eric/.cache/pypoetry/virtualenvs/opendevin-B_QcU69S-py3.11/lib/python3.11/site-packages/litellm/llms/openai.py", line 374, in completion
stringified_response = response.model_dump()
^^^^^^^^^^^^^^^^^^^
AttributeError: 'str' object has no attribute 'model_dump'
I run in WSL2

@ZDYnb what LLM are you using? Can you tell us more about your config?

I don't think it has anything to do with the llm I'm using. I've tried many LLMs. All is the same attributeError

My fault, I am not using a dirt

My fault, I wrongly enter my base URL, sorry  for your time


[BP-1.12][FLINK-22014][ha] Make sure that AbstractHaServices delete first the HA data before deleting blobs on closeAndCleanupAllData

Backport of #15468 to release-1.12.

Thanks for the review @zentol. Merging this PR now.

Merged via 709c4110370b845f42d916a06e56c6026cf2fac8


feat: Support multi-modal input and multi-modal output in one agent

Description
Mainly implements 4 multi-modal parts:

Building an agent to support multiple image inputs (see examples/vision/object_recognition.py)
Building an agent to call DALL-E to generate images (see examples/vision/image_crafting.py)
Building an agent to support calls to DALL-E to generate images while understanding multiple image inputs (see examples/vision/multi_condition_image_crafting.py)
Build two agents one for generating the image and one for suggesting ways for the other to fix the image. (see examples/vision/multi_turn_image_refining.py)

Motivation and Context
Part of #454
also will fix https://github.com/camel-ai/camel/issues/541
https://github.com/camel-ai/camel/issues/324

[x] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds core functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[x] Example (update in the folder of example)

Implemented Tasks

Supports multi-image input
Support DALLE function call
To allow an agent to receive image inputs and output images at the same time, a new FunctionCallingVisionConfig is built to adapt the ChatGPTVisionConfig
Create image crafting task type and example
Create multi-condition  image crafting task type and example

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] I have read the CONTRIBUTION guide. (required)
[ ] My change requires a change to the documentation.
[ ] I have updated the tests accordingly. (required for a bug fix or a new feature)
[ ] I have updated the documentation accordingly.

Hey @Zhoues , whether it's ok for you to let other contributor working on this PR?

Hey @Zhoues , whether it's ok for you to let other contributor working on this PR?

Of course, I'd be more than happy to let other contributors work on this PR！

Close this, since there is a new PR for people to keep working on this.


fix docs home page on mobile renders poorly

Before:

After:

#19671

/assign @sftim
/assign @php-coder

Hi @Arhell
To review this, I'll want to check that the code changes match the PR description. Could you summarize what changes this PR makes and (briefly) why those are useful?
Thank you for the screen grabs.
If you can provide before and after links, that will make reviewing even easier.

@sftim sure
check on mobile 320+
Before: https://kubernetes.io/docs/home/
After: https://deploy-preview-19686--kubernetes-io-master-staging.netlify.com/docs/home/ this PR

/assign @kbhawkey

/lgtm

@sftim @kbhawkey done & rebase

/lgtm

@sftim, Do you have additional comments?


Adam and EVE-OS initial deploy issue

Hi, I am trying to run a PoC with EVE-OS + Adam controller.
EVE-OS runs in a qemu VM while adam within a docker container.
First, I generated certs for Adam controller:
mkdir adam && cd adam
docker run -v $PWD:/adam/run -p 8080:8080 lfedge/adam generate server --cn adam-controller.lab.local --hosts adam-controller.lab.local

Then ran the controller using the following docker-compose:
version: '3.8'

services:
  adam:
    image: lfedge/adam
    container_name: adam
    command: server --conf-dir /adam/run/config --db-url /adam/run/adam --server-cert /adam/run/private/adam-controller.lab.local.pem --server-key /adam/run/private/adam-controller.lab.local-key.pem
    ports:
      - "8080:8080"
    volumes:
      - .:/adam/run
    extra_hosts:
      - "adam-controller.lab.local:<IP_ADDRESS>"
    restart: unless-stopped

It seems the controller runs normally but when trying to reach the web UI at https://adam-controller.lab.local:8080 it gives just a blank page.
I placed the generated adam certs under the conf directory of the repository and copied root-certificate.pem to v2tlsbaseroot-certificates.pem (understand these should be identical?). Then built EVE-OS by using installer-raw build target as below:
sudo make ROOTFS_VERSION=snapshot ZARCH=amd64 HV=kvm installer-raw

The installation is done successfully and I can confirm also that the Adam controller sees registration attempts from the edge device. Below are the logs from the Adam controller:
2024/07/10 11:50:47 404 returned for /api/v2/edgedevice/certs
2024/07/10 11:50:48 404 returned for /api/v2/edgedevice/ping
2024/07/10 11:50:53 404 returned for /api/v2/edgedevice/ping
2024/07/10 11:50:54 404 returned for /api/v2/edgedevice/ping
2024/07/10 11:50:55 404 returned for /api/v2/edgedevice/ping
2024/07/10 11:50:55 404 returned for /api/v2/edgedevice/certs

I generated the device onboarding key-pair with:
./pkg/pillar/scripts/generate-onboard.sh -c edge1516 -o LAB

Then went to the adam controller with docker exec and ran the following:
adam admin --server https://adam-controller.lab.local:8080 --server-ca run/config/root-certificate.pem device add --path run/config/onboard.cert.pem
adam admin --server https://adam-controller.lab.local:8080 --server-ca run/config/root-certificate.pem onboard add --path run/config/onboard.cert.pem

Then listing the device I see the following:
adam admin --server https://adam-controller.lab.local:8080 --server-ca run/config/root-certificate.pem device list
f8815e88-622f-496d-9b24-f4292661ebd3

adam admin --server https://adam-controller.lab.local:8080 --server-ca run/config/root-certificate.pem onboard list
edge1516

So I have two issues:

The adam controller is giving me no web content (blank page)
The EVE-OS VM seems to be contacting the adam controller but registration seems to fail.

AM I missing sth? I would appreciate your assistance to overcome this and complete the onboarding. Will eventually check to request a demo account at the commercial controller.
Thank you.

have you looked at https://github.com/lf-edge/eden ? it's a harness that we use for testing EVE and it's basic functionality is running an EVE instance in QEMU with Adam in a container, which looks like what you are trying to achieve. maybe try following these steps and you should get a running EVE and Adam instances around the eden start step. And then you can compare this approach with the one you are following or if you are unsure about the certificates for example, you can copy those from the instances inside Eden to yours.
let me know if this was helpful or we should investigate further!

Thanks I will try this approach. I will eventually need to run it manually using separate instances so as to understand the requirements better.

@rightkick have you tried https://lfedge.org/resources/lf-edge-sandbox/ ?

Thanks I will try this approach. I will eventually need to run it manually using separate instances so as to understand the requirements better.

@rightkick I managed to onboard EVE in Adam, here is how to do it.
1- First you need to generate the required certificates using Eden, Adam has --auto-cert option but EVE won't accept those certificates  because they are not chained with root-certificate (I'll send a PR to fix Adam, but in the meanwhile). Make sure the domain is right otherwise eve will reject the certs if it is not matching the domain in  conf/server.
git clone git@github.com:lf-edge/eden.git
cd eden
make build
# generate the certs, use your own domain name or localhost
./eden utils certs --domain zedcontrol.local.zededa.net
# copy certs to adam path
cp ~./eden/certs <adam_path>

2- Copy the Eden generated root-certificate.pem to eve /eve/conf.
3- Run Adam with Eden generated certs.
4- Onboard and add a device to the Adam.
5- Change eve conf/server to point to Adam.
6- Run EVE, it should onboarded itself to Adam.
for the stepst 2 to 4 I have fashioned a script together, feel free to use, but don't forget to adjust SERVER, and EVE_CONFIG with the correct values.
#!/bin/sh
set -x

PORT=9090
SERVER=zedcloud.local.zededa.net:$PORT
SERVER_URL=https://$SERVER
EDEN_CERTS=~/.eden/certs
EVE_CONFIG=/home/shah/shah-dev/eve/conf

STORE=run/adam
CERTS=run/certs
ADAM_BIN=./bin/adam
ADAM_CMD="$ADAM_BIN admin --server $SERVER_URL --server-ca $CERTS/server.pem"

initdev() {
    # wait for adam to run, then add and onboard a device
    sleep 3
    $ADAM_CMD device add --path $EVE_CONFIG/onboard.cert.pem
    $ADAM_CMD onboard add --path $EVE_CONFIG/onboard.cert.pem --serial '*'
    rm -f $EVE_CONFIG/root-certificate.pem
    cp $CERTS/root-certificate.pem $EVE_CONFIG/
}

rm -rf $STORE
# generate from eden using:
#./eden utils certs --domain zedcontrol.local.zededa.net
cp -r $EDEN_CERTS run/

initdev &
$ADAM_BIN server \
    --server-cert $CERTS/server.pem \
    --server-key $CERTS/server-key.pem \
    --signing-cert $CERTS/signing.pem \
    --signing-key $CERTS/signing-key.pem \
    --encrypt-cert $CERTS/encrypt.pem \
    --encrypt-key $CERTS/encrypt-key.pem \
    --conf-dir run/adam \
    --port $PORT

Please check this and close the issue if it answered your question.

Thank you for providing this nice tutorial.
Hi, I am trying to implement the tutorial given in the following website:
https://github.com/shantanoo-desai/EVE-OS-tutorials/blob/master/02-Eve-Eden-RPi4-nginx.md
I am using Ubuntu (WSL2 under Windows 11), and Raspberry Pi 4.
i am on my private network with DSL from Vodafone.
EVE live.img is flashed on an SD Card using balenaEtcher.
My network detects Raspberry / EVE very well.
But EVE registration with Adam fails, the following error is always displayed:
INFO[0380] Adam waiting for EVE registration (19) of (20)
FATA[0400] Eve onboard failed: error onboarding onboarding timeout. You may try to run 'eden eve onboard' command again in several minutes. If not successful see logs of adam/eve
Could you please help? Or am missing something?
thanks

Thank you very much for the reply,
I have tried with the latest version of Eden, but i am still getting the same error:
INFO[0380] Adam waiting for EVE registration (19) of (20)
FATA[0400] Eve onboard failed: error onboarding onboarding timeout. You may try to run 'eden eve onboard' command again in several minutes. If not successful see logs of adam/eve
Could you please assist again? Or am I missing something?
Thanks


Waypoint: Manipulate Arrays With shift

It complains "removedFromOurArray is not defined" in the console.
The exercise code has issue on line #3; it doesn't declared with var keyword, and exercise instructs change only certain line, but the error is not related to that section.

This has been fixed by PR #4870 and is awaiting deployment to the prod website.
Thanks and happy coding!

Got it. Thanks for quick response!!


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1261

Questions ?
Please refer to the Backport tool documentation


load_tracking: rewrite get_task_duty_cycle_pct

Rewrite get_task_duty_cycle_pct using task analysis methods. It seems
that the Bart method for obtaining a tasks's run time on a CPU
sometimes fails to provide a correct value.
Given that we're using task analysis methods on all other tests with this
function being the only one remaining using a Bart (SchedAssert) method,
rewrite this function to use a more reliable method to obtain a task's
run time.
Signed-off-by: Ionela Voinescu<EMAIL_ADDRESS>

This line can also be removed now:
from bart.sched.SchedAssert import SchedAssert

LGTM, waiting for @valschneider ack

Got the ack from @valschneider in person.


added FCM getToken as native module

Emarsys includes Firebase Cloud Messaging (FCM) so that it does not need to be installed additionally. Emarsys will retrieve the token from FCM automatically. However, there are situations where we want to retrieve the token manually. For this case, a native module is provided to access the getToken() method of FCM.

Hi @RyanLinXiang ,
Thanks a lot for creating the pull request.
However, the suggested change is out of Emarsys SDK scope.
We recommend adding the native module in your own project, or using React Native Firebase
I will close this PR for now.
Please feel free to create a Emarsys Zendesk ticket, and let us know if there are further questions.
Regards,
Bianca .


added fctvprintf() - vprintf with output function

Thanks for nice printf() implementation :)
The vprintf with output function may help integration where printf like function has already been declared.

Codecov Report

Merging #65 into master will decrease coverage by 0.82%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #65      +/-   ##
==========================================
- Coverage     100%   99.17%   -0.83%
==========================================
  Files           1        1
  Lines         359      362       +3
==========================================
  Hits          359      359
- Misses          0        3       +3

Impacted Files
Coverage Δ

printf.c
99.17% <0%> (-0.83%)
:arrow_down:

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 21eea6c...fdba0a0. Read the comment docs.


detailing Multi_hit in oncoplot?

Describe the issue
Hey, first thanks for such an incredible package for analysis and visualization!
I have a  question regarding oncoplot function, for genes that have multi_hit mutations, is there a way to colorize the rectangle based on different types of variant_classification instead of having a single color indicating a multi_hit mutation? Something similar to plots combining SNV and CNV for a specific gene in the vignette
Thanks!

Hi,
This was also asked in one of the previous issues. Unfortunately, it is hard to implement it and wasn't really worth the effort :|


codegen on Windows use backslash

Hi,
when I run ./generate-groups.sh on my Windows, I got an error message:
W1126 17:22:17.589739   27540 import_tracker.go:46] Warning: backslash used in import path 'k8s_customize_controller\pkg\client\clientset\versioned\scheme', this is unsupported.
I found someone also met this problem in last year : https://github.com/kubernetes/sample-controller/issues/40
But I want to know, is there any fix for this issue?
Thanks a lot.

Are there any updates on this one?
We have the requirement to use the generator in developer environments on windows. We also haven't found a workaround yet.


Compilation Error: registry.go:79: not enough arguments in call to transport.NewTransport

I tried to compile Flannel today using command:
docker run -i -t google/golang /bin/bash -c "go get github.com/coreos/flannel"
I got the following error:
Digest: sha256:03469dc0dbbd2209b53c38b123bb2780320815b64addfdee603da37e3ce51c44
Status: Downloaded newer image for google/golang:latest
github.com/coreos/flannel/subnet
../github.com/coreos/flannel/subnet/registry.go:79: not enough arguments in call to transport.NewTransport
OS Info:
cat /etc/os-release
NAME=CoreOS
ID=coreos
VERSION=1068.8.0
VERSION_ID=1068.8.0
BUILD_ID=2016-07-18-0616
PRETTY_NAME="CoreOS 1068.8.0 (MoreOS)"
ANSI_COLOR="1;32"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"

I have also tried to build on Ubuntu machine, and couldn't find the ".build" file.
Kindly help!


feat: improve Windows OS detection

As presented by @tralston in https://github.com/twpayne/chezmoi/pull/395.
This improves the detection of Windows from the output of uname.
Review appreciated as I don't have access to a Windows system to test, but it looks reasonable given the documentation of uname output on Wikipedia.

Looks like CI failed due to GitHub issues:
...
go mod download
...
go<EMAIL_ADDRESS>git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /home/travis/gopath/pkg/mod/cache/vcs/6466505548ed0f0b2b825c1ba6b822fa76675aa03269697c2b442d0c1c44678d: exit status 128:
fatal: unable to access 'https://github.com/alecthomas/units/': Failed to connect to github.com port 443: Connection timed out
...
go<EMAIL_ADDRESS>git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /home/travis/gopath/pkg/mod/cache/vcs/253f89932658a8a0e3613c7e24ffc23bc34cd50d4d37cb48b40091e9f2dfa8dc: exit status 128:
fatal: unable to access 'https://github.com/hashicorp/vault-plugin-secrets-ad/': Failed to connect to github.com port 443: Connection timed out
...
go<EMAIL_ADDRESS>git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /home/travis/gopath/pkg/mod/cache/vcs/23e0dd951cbf609fd9bc602de4fded61a90c546e85b158e46491581750cd788c: exit status 128:
fatal: unable to access 'https://github.com/hashicorp/vault-plugin-auth-gcp/': Failed to connect to github.com port 443: Connection timed out
...

I'll re-push the commit to trigger a rebuild.

I'll check the CI thing :)
thanks for the PR

Thanks for merging! Do you know when the scripts returned by the goreleaser service (e.g. https://install.goreleaser.com/github.com/twpayne/chezmoi.sh) will include this change?

hmm, seems like build failed on some project...
I'll see what we can do

@caarlos0 Any update? https://install.goreleaser.com/github.com/goreleaser/goreleaser.sh is not updated?

Gentle ping... it seems that this change is not yet deployed. Please tell me if I can help somehow.

@twpayne gometalinter seems to be the culprit for deployment on travis. I think it's an unrelated behavior since Travis has updated it's based image (maybe wrong).
As the GitHub Actions look promising, I will create a PR to integrate them into our process if you are interested.

Some project is failing the build... not sure how to fix it


Add doc.find()

This PR adds basic support for CouchDB's /db/_find API (see issue https://github.com/redgeoff/slouch/issues/101).
It also includes a simple test. Please let me know if something should be changed or extended. The additional function has not been added to any example or documentation file yet.

This looks good on the surface, but the tests are failing. (Click on the details in the "checks area of this PR" to see why).
Also, could you please tell me if you have a way of modifying the documentation at https://github.com/redgeoff/slouch/wiki#table-of-contents?

This looks good on the surface, but the tests are failing. (Click on the details in the "checks area of this PR" to see why).

I ran the tests locally, and they were fine but it turned out const was not supported in the setup used by CircleCI. Thanks for the heads-up! I fixed it and tests are passing now.

Also, could you please tell me if you have a way of modifying the documentation at https://github.com/redgeoff/slouch/wiki#table-of-contents?

It doesn't look like I'm able to edit the wiki: It wasn't included in the fork. I can clone it locally but I don't see a way to submit pull request for it and also can't push branches or any changes:
$ git push --set-upstream origin enhancement/update-wiki
ERROR: Permission to redgeoff/slouch.wiki.git denied to andreassiegel.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Nice work, thanks!
BTW, I'm working on moving the docs to markdown files so that they can be modified within a PR in the future.