CosmWasm Pool Type

Background
poolmanager currently only supports Gamm and Concentrated Liquidity pool types, which limits flexibility for adding/upgrading pool types without chain upgrades. This proposal suggests integrating the CosmWasm pool type into the Osmosis poolmanager to address this limitation.
Proposed Design
At high level, we need cosmwasm-pool module and adding CosmWasm to poolmanager's PoolType
cosmwasm-pool expose CreateCosmWasmPool where MsgCreateCosmWasmPool contains

CodeId: uint64
InstantiateMsg: []byte

So that it can instanitate contract with codeId and instantiateMsg and store the contract address in the pool.
It requires implementation of PoolI and SwapI associated to CosmWasm pool type.
For PoolI, except from GetAddress String, GetId and GetType; the following methods are delegated to the contract queries with the following spec.
// query msg:
// { "get_swap_fee": {} }
// response:
// { "swap_fee": <swap_fee:string> }
GetSwapFee(ctx sdk.Context) sdk.Dec

// query msg:
// { "get_exit_fee": {} }
// response:
// { "exit_fee": <exit_fee:string> }
GetExitFee(ctx sdk.Context) sdk.Dec

// query msg:
// { "is_active": {} }
// response:
// { "is_active": <is_active:boolean> }
IsActive(ctx sdk.Context) bool

// query msg:
// { "get_total_shares": {} }
// response:
// { "total_shares": <total_shares:number> }
GetTotalShares() sdk.Int

// query msg:
// { "get_total_pool_liquidity": {} }
// response:
// { "total_pool_liquidity": [{ "denom": <denom:string>, "amount": <amount:string> }>,..] }
GetTotalPoolLiquidity(ctx sdk.Context) sdk.Coins

// query msg:
// { "spot_price": { quote_asset_denom: <quote_asset_denom>, base_asset_denom: <base_asset_denom> } }
// response:
// { "spot_price": <spot_price:string> }
SpotPrice(ctx sdk.Context, quoteAssetDenom string, baseAssetDenom string) (sdk.Dec, error)

For SwapI, except for InitializePool that only will just set pool model in KVStore and GetPool that all the info is available on the module, the following methods are delegated to the contract sudos/queries with the following spec where response data refers to this.
// sudo msg:
// {
//   "swap_exact_amount_in": {
//     "sender": <sender:string>,
//     "token_in": { "denom": <denom:string>, "amount": <amount:string> },
//     "token_out_denom": <token_out_denom:string>,
//     "token_out_min_amount": <token_out_min_amount:string>,
//     "swap_fee": <swap_fee:string>
//   }
// }
// response data:
// { "token_out_amount": <token_out_amount:string> }
SwapExactAmountIn(
  ctx sdk.Context,
  sender sdk.AccAddress,
  pool PoolI,
  tokenIn sdk.Coin,
  tokenOutDenom string,
  tokenOutMinAmount sdk.Int,
  swapFee sdk.Dec,
) (sdk.Int, error)

// query msg:
// {
//   "calc_out_given_in": {
//     "token_in": { "denom": <denom:string>, "amount": <amount:string> },
//     "token_out_denom": <token_out_denom:string>,
//     "swap_fee": <swap_fee:string>,
//   }
// }
// response data:
// { "token_out": { "denom": <denom:string>, "amount": <amount:string> } }
CalcOutAmtGivenIn(
  ctx sdk.Context,
  poolI PoolI,
  tokenIn sdk.Coin,
  tokenOutDenom string,
  swapFee sdk.Dec,
) (tokenOut sdk.Coin, err error)

// sudo msg:
// {
//   "swap_exact_amount_out": {
//     "sender": <sender:string>,
//     "token_in_denom": <token_in_denom:string>,
//     "token_in_max_amount": <token_in_max_amount:string>,
//     "token_out": { "denom": <denom:string>, "amount": <amount:string> },
//     "swap_fee": <swap_fee:string>
//   }
// }
// response data:
// { "token_in_amount": <token_in_amount:string> }
SwapExactAmountOut(
  ctx sdk.Context,
  sender sdk.AccAddress,
  pool PoolI,
  tokenInDenom string,
  tokenInMaxAmount sdk.Int,
  tokenOut sdk.Coin,
  swapFee sdk.Dec,
) (tokenInAmount sdk.Int, err error)

// query msg:
// {
//   "calc_in_given_out": {
//     "token_in_denom": <token_in_denom:string>,
//     "token_out": { "denom": <denom:string>, "amount": <amount:string> },
//     "swap_fee": <swap_fee:string>,
//   }
// }
// response data:
// { "token_in": { "denom": <denom:string>, "amount": <amount:string> } }
CalcInAmtGivenOut(
  ctx sdk.Context,
  poolI PoolI,
  tokenOut sdk.Coin,
  tokenInDenom string,
  swapFee sdk.Dec,
) (tokenIn sdk.Coin, err error)

Pending Questions

Should we store pool assets in contract account or module account? I think it's better to store in contract account so that managing pool assets is all done in contract if there is no any other concerns.

Quick thoughts:

We need to be careful about who is the instantiator of the contract. Importantly, it cannot be a module account that is reused for any other purpose.
I think we should be careful to only allow contracts meeting the interface to be used. (E.g. imagine a contract that only implements join pool, but no exit) Some ideas for this:

Separately whitelist / maintain a registry for contracts that meet the interface
Permissionlessly "test" that a code ID satisfies an interface.

We need to be careful about who is the instantiator of the contract. Importantly, it cannot be a module account that is reused for any other purpose.

I imagine CreateCosmWasmPool will also register the contract to get poolmanager's msgs routed to, meaning, even though random person instantiate the contract, that contract will not be part of the active pool.

I think we should be careful to only allow contracts meeting the interface to be used. (E.g. imagine a contract that only implements join pool, but no exit) Some ideas for this:

Separately whitelist / maintain a registry for contracts that meet the interface

Right. So it's like a 2-step gov process where we need to 1. store code and 2. register the code id as valid CosmWasm pool. But as poolmanager only have restriction on swap interface, do we want to define standard for join and exit interface for cosmwasm pool? or should we just leave it case by case for flexibility.

Permissionlessly "test" that a code ID satisfies an interface.
Should be technically possible.

Are you proposing having this method on PoolI. I don't think it makes sense to have it for some pool types (e.g. concentrated liquidity) but if nothing else works, we can make this return "not implemented" error from CL or panic

// query msg:
// { "get_total_shares": {} }
// response:
// { "total_shares": <total_shares:number> }
GetTotalShares() sdk.Int

I imagine CreateCosmWasmPool will also register the contract to get poolmanager's msgs routed to, meaning, even though random person instantiate the contract, that contract will not be part of the active pool.

I think that makes sense. If the contract is already instantiated, we fail pool creation, making it only successful if the cosmwasm-pool module account creates it

Should we store pool assets in contract account or module account? I think it's better to store in contract account so that managing pool assets is all done in contract if there is no any other concerns.

Storing them in the contract makes sense to me

@p0mvn The GetTotalShares was from a snapshot of PoolI at the point of that writing. Thanks for clarifying for the rest!

@iboss-ptk
I would like to better understand how Go side coswasmp-pool's interfaces and messages are going to translate into Cosmwasm pool implementations.

What are the examples of some future CosmWasm pools that we are expecting other than transmuter?

Is transmigrator also going to be implemented as a pool type and plugged into this model?

Are they all going to have the same interface? What are some common interfaces and where do they differ?

For example, I see that transmuter has JoinPool , ExitPool and Transmute execute message entrypoints.

In the context of transmuter, does MsgSwapExactAmountIn in poolmanager translate to MsgExecute::Transmute?
What does poolmanager's MsgSwapExactAmountOut translate to?
For JoinPool and ExitPool do we need to create corresponding messages in the coswasm-pool Go module?

Also, would appreciate ideas on how to integration test this Go side if there are any

@iboss-ptk initial draft is ready here: https://github.com/osmosis-labs/osmosis/pull/4675
Please review

@p0mvn

What are the examples of some future CosmWasm pools that we are expecting other than transmuter?

Is transmigrator also going to be implemented as a pool type and plugged into this model?

I don't think transmigrator is a pool type, it doesn't have anything resemble pool by any means, only interacting with other pools.
There is yet to have any other type of CosmWasm pool type in the pipeline.

Are they all going to have the same interface? What are some common interfaces and where do they differ?

For example, I see that transmuter has JoinPool , ExitPool and Transmute execute message entrypoints.

In the context of transmuter, does MsgSwapExactAmountIn in poolmanager translate to MsgExecute::Transmute?
What does poolmanager's MsgSwapExactAmountOut translate to?

both MsgSwapExactAmountIn & MsgSwapExactAmountOut can be transmute since it has no slippage

For JoinPool and ExitPool do we need to create corresponding messages in the coswasm-pool Go module?

My initial thought was to keep PoolI the way it is and establish other interfaces on cosmwasm side as needed.
If there is any extension from PoolI needed, I think having either:

proxy execute/query contract and abstract away querying contract address and send execute/query directly, or
retrieving contract address
would be required

@iboss-ptk ACK, thanks for the replies.
I have some more questions around transmuter. Will keep updating this message as questions come up. Please get back at your convenience.

Seeing swap fee as hard-coded to zero. Is this final?


C++ Generated Code Fails to Compile

Description
No generated C++ code compiles using default (or any) compilation tools.
Steps to Reproduce

Create simple test.ump file e.g.

class Person { }

Using command-line tool: run java -jar <path_to_umple_jar> -g RTCpp test.ump to generate C++ code
Compiling using any of: cmake . ;  make, or g++ test_Model.cpp -o model.o, or even clang++ test_Model.cpp does not compile due to (seemingly legitimate) C++  syntax errors.

Expected Results
Successful compilation of the generated C++ code to an executable as in (v1.26)
Actual Result
Log output is very long but to give a flavour the last error returned is always an issue with passing strings to std::exceptions.
In file included from Person.cpp:12:
./master_Model.h: In instantiation of ‘PT* AutoPtr<PT>::operator->() [with PT = DelegateBase]’:
./master_Model.h:1330:14:   required from here
./master_Model.h:773:18: error: no matching function for call to ‘std::exception::exception(const char [23])’
       throw std::exception("Null Pointer Exception");
                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/c++/8.2.1/exception:38,
                 from /usr/include/c++/8.2.1/ios:39,
                 from /usr/include/c++/8.2.1/istream:38,
                 from /usr/include/c++/8.2.1/sstream:38,
                 from ./master_Model.h:34,
                 from Person.cpp:12:
/usr/include/c++/8.2.1/bits/exception.h:63:5: note: candidate: ‘std::exception::exception()’
     exception() _GLIBCXX_USE_NOEXCEPT { }
     ^~~~~~~~~
/usr/include/c++/8.2.1/bits/exception.h:63:5: note:   candidate expects 0 arguments, 1 provided
/usr/include/c++/8.2.1/bits/exception.h:60:9: note: candidate: ‘constexpr std::exception::exception(const std::exception&)’
   class exception
         ^~~~~~~~~
/usr/include/c++/8.2.1/bits/exception.h:60:9: note:   no known conversion for argument 1 from ‘const char [23]’ to ‘const std::exception&’
Person.cpp: In function ‘bool operator==(Person&, Person&)’:
Person.cpp:61:1: warning: control reaches end of non-void function [-Wreturn-type]
 }

Comments
**The last working version I could find was v1.26 (breaking at v1.26.1). **
Am I missing something obvious or is this just bad C++ code being generated?

@ahmedvc Please respond to this and fix if something is broken.

Some further information I have found through some digging:
The issue seems to have been introduced when this file was modified: here. I've highlighted the line which causes one (of the many) syntax errors thrown by the compiler. It should be replaced with Exception("Null Pointer Exception") as there is an additional class created by the author to pass strings to std::exceptions.
Modifying the generated code resolves that error but leaves a litany of others I just do not have the time to debug.
From the looks of things I would say that it would be best to revert the code and work from the c++ templates in v1.26 iteratively recompiling adding the features that have been added prior to the 1.26 release.
I can't help but think I may be missing a compilation step or something more trivial as I am sure this issue would've been thrown up before - I'm not an expert c++ programmer by any means - any advice would be appreciated

Some of this has been fixed in recently merged PR #1866 although there are still plenty of cases that don't work.


feat: add linux support.

Experimental branch:
seems to work fine with chrome, but with macOS can only see one-way video Linux => macOS ok,  macOS => Linux no video/audio
Tested interactively with Windows/macOS/Android, all functionality appears to work.
tested platform
Ubuntu 20.04.5 x64
Ubuntu 20.04.5 arm64
Ubuntu 22.04.2 x64
Ubuntu 22.04.2 arm64
Linux

Windows

macOS

client-sdk-flutter implements support for all mainstream OS.

The files in the PR are actually generated by flutter create . --platforms linux.
all functional tests are fine, so I'm merging it now.


feat(RLS): RESTful apis and react view for RLS

SUMMARY

Update RLS view to use React and REST apis.
this PR only migrates old view to new without any additional features like,

ownership
import export support.
toggle like in alerts/reports to enable/disable RLS rules.
can add this in a separate PR.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Empty state

Add rule modal

Populated list

Bulk select to delete

TESTING INSTRUCTIONS

Before merging this PR, create few RLS rules.
Then merge PR and check they are correctly shown on the new UI.
Delete all, create new and check correctly shown.
test filters in the list view.
Create chart on the table rule is set with the role and check its correctly getting applied.
Set RLS_FILTER_RELATED_FIELDS in the config.py as below

{
    "tables": [["table_name", filters.FilterStartsWith, "birth"]],
    "roles": [["name", filters.FilterContains, "Admin"]]"
}

When adding a new rule, in the table dropdown table names starting with birth should be shown and roles dropdown should only show roles containing text Admin.

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[x] Introduces new feature or API
[x] Removes existing feature or API

@rusackas @dpgaspar this is ready for review.
will add breaking change info about RLS_FORM_QUERY_REL_FIELDS in updating.md.

this PR only migrates from old view to new without any additional features which lacks features like

ownership access
import export support.

will add this in a separate PR.

thanks for reviews!!
will get back today or tomorrow as early as possible.

updated as per review comments + added amazing tests for rule modal on the frontend.

/testenv up

@mayurnewase I was just giving the React UI a test, and it's SO MUCH NICER!!!
I like the addition of the Name field... gives the user a chance to add something descriptive... as does the description field as well. Now people can better reason about what roles they're discussing within a deployment, and give some historical context as to why they exist or who created/owns them.
Heads up that changing RLS_FORM_QUERY_REL_FIELDS to RLS_FILTER_RELATED_FIELDS may affect deployments that customize this value in various ways - are we OK with this change or would this constitute a breaking change (even if it's easy to correct)? CC @eschutho @john-bodley @dpgaspar

Also... for good measure
CC @yousoph and @kasiazjc for any feedback needed on the added (or I should say surfaced) Name/Description fields.
CC @lauderbaugh since this brings us one step closer to SPA
CC @jinghua-qa for a heads up on any QA implications of this new React view for RLS
CC @tugceoz in case this warrants a revisit of any pertinent docs.

thanks for the ephemaeral env, tested few things on it found few issues, fixed them in last commit.
might need to redeploy it.

thanks for the review, will update today.
may also push fix for failing flaky tests in this PR if needed.

Hi @mayurnewase! Thanks for this PR!
I see you created a new UI page and we have a #22330 discussion about the new structure of UI pages.
What do you think about it?

is it approved?

Hi @mayurnewase! This discussion is in progress and your opinion and feedback is important there!
I guess we'll start migrating the pages in month.

Heads up that changing RLS_FORM_QUERY_REL_FIELDS to RLS_FILTER_RELATED_FIELDS may affect deployments that customize this value in various ways - are we OK with this change or would this constitute a breaking change (even if it's easy to correct)? CC @eschutho @john-bodley @dpgaspar

yeah, I would consider this a breaking change, because it changes the name of a config. I noticed the comment in "Breaking changes" in UPDATING.MD as well. I think we're going to run into issues in the 2.1.0 release for our users. Can we try adding a new config, and reading either flag for now in order to make this backward compatible, and then remove the old config in 3.0?

We didn't talk about removing views in the semantic versioning SIP  but  in the future, we may want to consider that as an additional override/extension point to the application and only remove views in major version bumps.

@eschutho When are we planning the 3.0 release? in 2024?

I'll let @michael-s-molina answer that question.

Hi @EugeneTorap. We're currently discussing the 3.0 date and our LTS support guidelines. We'll announce the official date to the community pretty soon but the current thinking (which may change) is April/2023.

so no major features can be pushed to master if a major release isn't planned?
thats a bummer :(

Oh no, you can push major features any time, just not with any of the breaking changes as outlined in the semantic versioning SIP  to follow convention.

@eschutho Maybe it's better to add a feature flag for the new breaking changes of RLS instead of reverting the PR?

created PR to revert, although if it breaks any action in CI I will need some time to fix, so feel free to push in my branch if its urgent.
thank you all for your time on this.

Thank you @mayurnewase. If you want to put up a new pr, I would suggest a few things to make it backward compatible:

deprecate, don't remove old views. Change the client side to use react but still keep the old views for backward compatibility. You can even change the client side route if you need to.
Instead of changing the naming on configs, you can add new ones and deprecate the old ones, but make sure that wither will work for now.
Same with permission names, add new ones and deprecate old ones, making sure that both still work.

@eschutho Maybe it's better to add a feature flag for the new breaking changes of RLS instead of reverting the PR?
I don't believe a feature flag specifically would work in this case, but I've outlined some other options.

@mayurnewase Now that the window for breaking changes is open (until May 15th), would you like to submit these changes again and update its status on the Apache Superset 3.0 board?


[PUPIL-800] Lesson overview and lesson review colour updates

Description
Music year: {owa_music_year}
Updates Oak components to bring in new background colours and background svgs.
Updates the Overview and Review areas to change colour based on phase
Updates the quizzes to show a svg background when the question has been answered correctly.

Screenshots

Checklist

[x] Added or updated tests where appropriate
[x] Manually tested across browsers / devices
[x] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[x] Does this PR update a package with a breaking change

Looking good - one little thing - maybe for @messmike to confirm, on tablet view if you look closely you can see the confetti, which on the designs shows no confetti (screenshots below) Are we happy to keep this?

Looking good - one little thing - maybe for @messmike to confirm, on tablet view if you look closely you can see the confetti, which on the designs shows no confetti (screenshots below) Are we happy to keep this?

Good spot @RBrownsett - if it's easy to hide the svg backgrounds on tablet then that would be good

@messmike Can do, will involve a change to oak components first. I'll push that now.

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


[ problem ] Chatbot did not process the pdf + got stuck

Description:
When using the chatbot, I uploaded a pdf (uploaded successfully). However, when I wrote a message and clicked enter, the message disappeared, and the result didn't load. It seems that the output did not go through.
Steps to reproduce the behavior:

Go to chatbot
Attach a pdf.
Write a question about the pdf.
See error

@parmi02 could you upload the pdf you got an error with? or was it any pdf?

any pdf

@parmi02 this works for me, can you upload your server logs and the file you attempted to upload?
docker compose logs > logs.txt

https://github.com/user-attachments/assets/a807f1bb-1e35-4523-bdc3-d61a3393224d

Eidolon -- AI Agent Server for the Enterprise.pdf
This was the pdf I uploaded. Let me try again to see if the issue perists.

@flynntsang to try to repo

@parmi02 @LukeLalor I could not reproduce. I have a Macbook running Linux Mint (Ubuntu 24.04), 16GB RAM. I uploaded and conversed using my own PDFs and the attachment to this issue.

It worked, wasn't able to reproduce.


Some files in gerber.zip are not recognized by JLCPCB.

When I uploaded this 4 layers gerber zip file to JLCPCB I am getting an error messages that some of the files were not recognized.  Not sure what they are and why there are in the .zip file but would think naively that since this a JLC specific plugin, it should include only files JLC needs when it accepts a .zip file.
The main thing is that I don't know if this is normal or if somebody is missing from my order because of dropped files.

gerber.zip

what version of kicad are you using?

Application: KiCad x64 on x64
Version: 7.0.1, release build
Platform: Windows 10 (build 19044), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
Date: Mar 11 2023 03:41:46
On Wed, May 17, 2023 at 2:29 PM stormyweathers @.***>
wrote:

what version of kicad are you using?
—
Reply to this email directly, view it on GitHub
https://github.com/bennymeg/JLC-Plugin-for-KiCad/issues/61#issuecomment-1552110772,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQVMQNOYNROOAM6UQBKU3LXGU7MJANCNFSM6AAAAAAYDBLGGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

That's fine. I'm adding all the necessary files for production to the zip. So it acts like a full production artifact. JLC will use the files it needs for your selected setup.

Thanks Benny.  The issue is that 1) I need to know which files are
necessary for JLCPCB and which ones are not and 2) I need to go over the
JLCPCB list and verify that all the rejected files are unnecessary.
How about having 3 'clean' files for JLCPCB and an additional zip file or a
subdirectory with all the artifacts?
On Wed, May 17, 2023 at 11:10 PM Benny Megidish @.***>
wrote:

That's fine. I'm adding all the necessary files for production to the zip.
So it acts like a full production artifact. JLC will use the files it needs
for your selected setup.
—
Reply to this email directly, view it on GitHub
https://github.com/bennymeg/JLC-Plugin-for-KiCad/issues/61#issuecomment-1552488431,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQVMQOIZXD4WE4UNNRPMJLXGW4ONANCNFSM6AAAAAAYDBLGGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

@bennymeg this should be closed because it has been addressed

Thanks Benny. Closing.

Thanks @Fisheiyy,
I will publish it in the next release.


Preserve Kube APIServer resource requests

This satisfies the requirement by IBM Cloud of allowing adjustments to
resource requests of the Kube API server by preserving any changes made
to said resource requests and not stomping them with the defaults.

/test e2e-aws-pooled

/test e2e-aws


Trigger selection

@katush @mijar
Please check once in the matrix filter if it is correctly working or not.

@bikramkawan I am going through this and #51 is still not working, should it be working or did you pass on it?

#78 is OK


HELP

I'm using Windows 10, Pi Pico, VS Code and Platform IO (latest versions)
Using the the stock platform for the Pi on PIO was giving me the error of  reseting the connectiong of the Pi and opening as a drive device and platformio trying to upload .elf file.
After watching your PR and all the drama I tried to change the platform to your Fork. but ive been trying since yesterday even deleting the C:/user/.platformio/tmp file to force it to download everything again.
This is the error appearing
Submodule 'hidapi' (https://github.com/signal11/hidapi) registered for path 'pico-sdk/lib/tinyusb/tools/uf2/hidapi'
Cloning into 'C:/Users/[USER]/.platformio/.cache/tmp/pkg-installing-861qm122/pico-sdk/lib/tinyusb/tools/uf2/hidapi'...
Submodule path 'pico-sdk/lib/tinyusb/tools/uf2/hidapi': checked out 'a6a622ffb680c55da0de787ff93b80280498330f'
fatal: Unable to checkout '17761f5cf9dbbf2dcf665b7c04934188add20082' in submodule path 'pico-sdk/lib/tinyusb/hw/mcu/wch/ch32v307'
fatal: Failed to recurse into submodule path 'pico-sdk/lib/tinyusb'
From https://github.com/earlephilhower/bearssl-esp8266

branch            f294aa022f82833941ffdf3b0f306c2072e3a26c -> FETCH_HEAD

Submodule path 'tools/libbearssl/bearssl': checked out 'f294aa022f82833941ffdf3b0f306c2072e3a26c'
Submodule path 'tools/pyserial': checked out '0e7634747568547b8a7f9fd0c48ed74f16af4b23'
fatal: Failed to recurse into submodule path 'pico-sdk'
Error: VCS: Could not process command ['git', 'clone', '--recursive', '--depth', '1', 'https://github.com/earlephilhower/arduino-pico.git', 'C:\Users\[USER]\.platformio\.cache\tmp\pkg-installing-861qm122']

fatal: Failed to recurse into submodule path 'pico-sdk/lib/tinyusb'

You must follow https://arduino-pico.readthedocs.io/en/latest/platformio.html#important-steps-for-windows-users-before-installing


HTTP404 (broken link)

On page https://www.getmonero.org/get-started/mining/ there's a link under text 'More details in the announcement post.' that leads here: https://www.getmonero.org/get-started/mining/{{ site.baseurl }}/2021/10/05/p2pool-released.html which is not found (HTTP404)
As far as I found it - the correct link should be https://www.getmonero.org/2021/10/05/p2pool-released.html

Please close, issue fixed :+1:


test this, mostly tag

Description
Follow-up for https://github.com/dockstore/dockstore/commit/7b1890dce0e9926176f3823521d428c638020555
now that it has been merged into develop. Mostly just referencing tags instead of workflowversions
This has been breaking the nightly cli builds
Review Instructions
Nightly cli builds should pass again
Issue
https://github.com/dockstore/dockstore/issues/5605
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running ./mvnw clean install
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

Ended up with https://github.com/dockstore/dockstore-cli/pull/260


Dynamics equation change using lateral controller in reverse

In lat_controller.cc when in reverse mode the matrix_a_coeff_(0, 2)  is given a non zero value and matrix_a_coeff_(0, 1)  a zero value.
Matrix_a is top matrix in this equation from Rajamani:

where:

The two numbers highlighted in red are swapped when in reverse mode.
This would result in the change in lateral error equal to the heading error. I don't understand why matrix_a_coeff_(0, 2)  is non-zero in reverse mode.

In the reverse-driving model, due to the inaccuracy of the lateral translational motion which was originally designed for forward driving, we replace this dynamic equation with the following kinematic equation:
y_dot  = V * sin(phi-phi_des)
by simplification and small-angle assumption, it is given by:
e1_dot = V * e2
Thus, we have
matrix_a_coeff_(0, 2) = 1  (when gear_reverse)
matrix_a_(0, 2) = matrix_a_coeff_(0, 2) * v  (when gear_reverse)

Thanks for the reply, would it not be more accurate to use the same kinematic model with rear wheel steering and the heading rotated 180 degrees?

Based on our design principle, the autonomous driving car is assumed to be the front-wheel steering which may cover most of the car models in market.
However, if the car in your project happened to be a rear-wheel steering car, then directly applying the forward-driving dynamics (with some variables changed by 180 degrees) will be a good fit. Thanks.


Bump mbedTLS to 2.16.6

@ceolin https://github.com/zephyrproject-rtos/mbedtls/pull/11 is merged, please update the manifest with a SHA.

@ceolin zephyrproject-rtos/mbedtls#11 is merged, please update the manifest with a SHA.

done


Http4+get with body

Added support for GET with body content on camel-http4. This is triggered with the 'getWithBody=true' uri parameter.

Hey there, thanks for the contribution!
It seems a backport of https://issues.apache.org/jira/browse/CAMEL-14118 in particular https://github.com/apache/camel/commit/cf8c9a6505556e0df7ab426d787de4c1ced24131
Do you mind backporting, from that commit, the test as well (and check if it does pass)?
Also as a general note please run mvn -DskipTest -Psourcecheck in the component you modified (i.e. camel-http4) and see if there are code style violations.

Did you get a chance to work on this?

Unfortunately not yet.  Will do as soon as I can.

Hi!  I need a bit of advice here.  The commit "cf8c9a6" applies to camel-http while the current PR treats of camel-http4.  Backporting the above commit to the camel-http component of v2.25 is not that straightforward as the component has changed quite a lot in the meantime.  The commit "cf8c9a6" complemented the inclusion of a deleteWithBody feature, but this feature does not exist yet in camel-http 2.25 (while it exists on camel-http4).
I had heard that in v2 we were encouraging camel-http4 rather than camel-http, but I could see that in v3 the components converged and camel-http4 disappeared.
So I would say it would be better to keep those 2 changes separate: one PR to update camel-http4 in v2, then another one to both backport getWithBody and add deleteWithBody to camel-http .
What do you think?
PS. In case, I've just added a commit to this PR branch to add the required unit test to camel-http4.

Only focus on camel-http4 in camel 2.x, the other camel-http is deprecated as its based on a very old EOL http client.

Ok got it.  So it's actually camel-http4 v2 that led to the new camel-http in v3.  Makes more sense now.

Done.


chore: fix demo links in readme

Demo links were broken in the readme.

Thank you! We first import your changes into Meta's source control and it is then exported to GitHub, so you won't see this PR directly merged, but your contribution will be shortly merged and correctly attributed to you.


GCP: Add support Google App Engine Resources

Would love to work on this. I was just about to roll my own by hand since we're leveraging App Engine and terraformer didn't seem to support App Engine Resources. If this work isn't already in flight I'd love to take this on.

Importing App Engine ressources does not seem to be available as of yet, right? Would love to see that

My team wants this as well. @willmadison did you ever end up rolling your own solution?

@ChelseaKR we didn't. We ended up replatforming to GKE.


Review breakpoint type resolving scope

Hello. Please consider https://github.com/dart-lang/sdk/issues/56300.

Summary: The is operator in Dart evaluates to true when checking against an unresolved identifier, instead of throwing an error. This behavior is observed in Flutter, but not in standalone Dart, leading to unexpected results in conditional breakpoints and expression evaluation.

Now, if this ends up being fixed as non-Flutter Dart, for every type that is not in scope:

For non-Flutter dart, you get a reasonable error:

I'd like to question here if there could be a way for breakpoint expressions to "ignore" that scope.
Use case:
I have an extension of FocusNode, wich is a Flutter (third party/package) class. But as an extended class, some of the logic is done inside Flutter files and they have no way of knowing about my subclass. I'd like to place a breakpoint there and only stop there when my class stops there so I can see if I made anything wrong or I am missing anything. But in my case, all FocusNode/FocusScopes in my screen stop there and that makes me have to skip a lot of breaks and hope for me to not missclick on the right one.
In this specific case, I can of course do a simple empty wrapper on the exact method I'd like to see and break point there and go inward to see whats going on. Well, two more things here:

If the method I'd like to see is private (which in this case I know there are some - and made an issue about that already), I'm not able to do that.
If I'd like to test the behaviour inside a Flutter Widget (third party interacting class), I'm not able to do so as well since I would then need to basically rewrite all of the inner workings of TextFormField, for example, (which has a lot going on) just to get to the Focus widget State (aka FocusState).

Maybe if we could indicate what it should import in some way?

cc @jensjoha

Not sure if this is a VM issue, as indicated in comment-2243272766 the client tool would have to build scopes appropriately.

@DanTup, if you make use of the evaluteInFrame RPC, the type should be in scope without having to explicitly provide it.

@bkonyi we do use evaluateInFrame, but the issue here is that the class used in the expression is not in-scope.
The issue here is not a bug, but a request to try and improve the situation where you have a variable of some type and want to do an is check (for example in a conditional breakpoint), but there's nothing you can write for the type that will work, because it isn't imported and in-scope.
I've hit this myself before, and often end up rewriting the expression to be .runtimeType.name == 'Foo', but it's not equivalent so isn't always possible. As far as I know, there's no expression we can write to reference a type that's not in scope (for example like .NET's global::Namespace.Type).
I suspect for the huge majority of cases, "the first class found anywhere with the name Foo" would do just what the user wanted, but ofc that's not very sound (or understandable to the user).
I'm not sure (without having some way to reference a type that's not in scope) there's a lot we can do here, but maybe others have ideas? 🤔

@DanTup can you share some sample code to help me better understand the context?

@bkonyi this is a bit contrived, but imagine this code:
void main() {
  foo(<String>{});
}

void foo(Set s) {
  print(s); // Conditional breakpoint here "s is LinkedHashSet"
}

If I add a breakpoint to the marked line with the condition s is LinkedHashSet, it doesn't work because LinkedHashSet isn't in scope (even though it is the type of the variable):

While the error is clear (at least for Dart - https://github.com/dart-lang/sdk/issues/56300 makes this really confusing for Flutter, because it just silently doesn't trigger), besides adding an unused import to your code and reloading, there's not a clear what to make the breakpoint trigger when you want.
I don't know what a good fix it, but it would be nice if there was a way to fix this, by being able to write an expression like s is LinkedHashSet (and have some way to specify where LinkedHashSet comes from) without having to add an unnecessary import and reload the app.

Is this a problem if the declaration or import is present in the file? Or is this only a problem with types defined in dart:core?

Or is this only a problem with types defined in dart:core?

It happens with any type that the declaration is unknown.

Is this a problem if the declaration or import is present in the file?

No. When this happens, it does work.
The following example works for both B and C because their types are in the scope of the breakpoint.
File bug.dart:
import 'c.dart';

void main() {
  foo(<String>{});
  bar(B());
  bar(C());
}

void foo(Set s) {
  print(s); // Conditional breakpoint here "s is LinkedHashSet"
}

void bar(A a) {
  print(a); // Conditional breakpoint here "a is B" or "a is C"
}

class A {}

class B extends A {}

File c.dart:
import 'bug.dart';

class C extends A {}

Just to be clear, about DanTup comment above:

While the error is clear (at least for Dart - https://github.com/dart-lang/sdk/issues/56300 makes this really confusing for Flutter, because it just silently doesn't trigger), [...]

It should be:
For Flutter, currently (until #56300 is resolved) it silently (does) triggers.

I'll explain this with a Flutter case but any third party package would fit here.
Which is really weird, it means that for the current state, it behaves strangely.
Lets say Flutter has a type B and a type D that extends/implements B.
If I'm debugging my Flutter project and I've created some class C for example, extending B because some Flutter widget accepts any B.
Now I go inside that widget to see the current behaviour of it with my new class instance (that is C) and do this test (foo is C), it sounds to me like every instance of the type the widget accepts (B) is an instance of my new class C. Even when the framework itself passes a D instance somewhere else.

@bkonyi

Is this a problem if the declaration or import is present in the file? Or is this only a problem with types defined in dart:core?

My example may have been slightly misleading - LinkedHashSet is not in dart:core but in dart:collection, so that name is not in-scope for this file/frame because there's no import for it. In any case where you have a variable of type X but X is not imported and in-scope causes the issue (and any time the type is in scope, it's fine).
@FMorschel

For Flutter, currently (until https://github.com/dart-lang/sdk/issues/56300 is resolved) it silently (does) triggers.

Sorry yes, I got it the wrong way around. That bug results in the condition returning true even when it's not, and that is more confusing than the opposite, because it pauses the debugger and you assume the variable is of the type you wrote, but it might not be. Hopefully that's an easy fix though, whereas this request seems a little tricker 😄

Maybe if we could indicate what it should import in some way?

Like the following:

Currently, it gives an error:
Debugger failed to evaluate breakpoint condition "import 'dart:collection'; s is LinkedHashSet": evaluateInFrame: (113) Expression compilation error
org-dartlang-debug:synthetic_debug_expression:1:1: Error: Undefined name 'import'.
import 'dart:collection'; s is LinkedHashSet
^^^^^^
org-dartlang-debug:synthetic_debug_expression:1:8: Error: Expected one expression, but found additional input.
import 'dart:collection'; s is LinkedHashSet
       ^^^^^^^^^^^^^^^^^

It is not the best possible option, but it would at least make sure that we could run these evaluation tests in breakpoints and such.


IBC enabled token registry module

IBC enabled Digital Token Identifier
To build a digital token identifier registry on the Cosmos blockchain, you will need to define the methods and fields for the protocol buffer (proto) file that describes the data structure. Below is an example of how you can define the proto file for your token identifier registry:
syntax = "proto3";
package token;
message Token {
string id = 1;
string name = 2;
string symbol = 3;
string owner = 4;
uint64 total_supply = 5;
uint64 decimals = 6;
}
message RegisterTokenRequest {
string id = 1;
string name = 2;
string symbol = 3;
string owner = 4;
uint64 total_supply = 5;
uint64 decimals = 6;
}
message RegisterTokenResponse {
bool success = 1;
string message = 2;
}
message GetTokenRequest {
string id = 1;
}
message GetTokenResponse {
Token token = 1;
}
message UpdateTokenRequest {
string id = 1;
string owner = 2;
}
message UpdateTokenResponse {
bool success = 1;
string message = 2;
}
service TokenRegistry {
rpc RegisterToken(RegisterTokenRequest) returns (RegisterTokenResponse);
rpc GetToken(GetTokenRequest) returns (GetTokenResponse);
rpc UpdateToken(UpdateTokenRequest) returns (UpdateTokenResponse);
}
This white paper introduces the concept of a Digital Token Identifier Registry, which leverages the power of blockchain technology to provide a decentralized and secure method for identifying and verifying digital tokens. The registry aims to address the challenges associated with token identification and enable interoperability among various tokenized ecosystems. By utilizing the Cosmos blockchain framework, the Digital Token Identifier Registry offers a reliable and scalable solution that promotes transparency, immutability, and trust within the tokenized economy

Introduction
1.1 Background
The emergence of blockchain technology has revolutionized the way we transfer and store value digitally. With the rise of tokenized assets and decentralized applications (dApps), there is a growing need for a standardized and secure method to identify and verify digital tokens. The existing token ecosystems lack a unified approach to token identification, leading to issues such as token confusion, fraud, and limited interoperability.
1.2 Problem Statement
The absence of a comprehensive token identification system hinders the seamless integration and efficient functioning of tokenized ecosystems. Token projects face challenges in establishing trust, verifying token ownership, and ensuring interoperability across different platforms. The lack of standardized token identification also limits the potential of decentralized finance (DeFi) applications and cross-chain interactions.
1.3 Objectives
The primary objective of the Digital Token Identifier Registry is to establish a decentralized and reliable system for token identification and verification. This registry aims to:
◦ Provide a standardized method to uniquely identify digital tokens.
◦ Enable efficient verification of token ownership and authenticity.
◦ Facilitate interoperability among various tokenized ecosystems.
◦ Promote transparency, immutability, and trust within the token economy.
Token Identification Challenges
2.1 Lack of Standardization
The absence of a standardized token identification system leads to ambiguity and confusion. Tokens may have similar names or symbols across different platforms, making it difficult to differentiate between them. This lack of standardization hampers the development of robust token ecosystems.
2.2 Trust and Verification Issues
Verifying the authenticity and ownership of digital tokens is often a challenging task. Without a decentralized registry, users must rely on centralized authorities or intermediaries, which introduces trust issues. Fraudulent tokens and fake issuers pose a significant risk to token holders and investors.
2.3 Interoperability Constraints
Interoperability is a crucial aspect of a thriving tokenized economy. However, the absence of a standardized token identification system makes it challenging for tokens from different blockchains or platforms to interact seamlessly. This limits the potential for cross-chain transactions and inhibits the growth of decentralized applications.
Digital Token Identifier Registry
3.1 Overview
The Digital Token Identifier Registry is a decentralized solution that leverages the Cosmos blockchain framework. It acts as a comprehensive and secure database for token identification and verification. By utilizing the unique features of blockchain technology, the registry establishes a trusted and transparent system for token ecosystem participants.
3.2 Key Features
3.2.1 Token Registration
The registry enables token issuers to register their tokens by providing essential information such as token ID, name, symbol, total supply, decimals, and initial owner. This process ensures that each token is uniquely identified within the registry.
3.2.2 Token Metadata
The registry allows token issuers to manage metadata associated with their tokens, including descriptions, images, contract addresses, and other relevant information. This metadata enhances token visibility and provides users with comprehensive details about each token.
3.2.3 Token Ownership
The registry maintains an immutable record of token ownership, facilitating secure and auditable

Digital Token Identifier Registry is a needed and highly useful project in the context of the rapidly evolving tokenized economy. Here are several reasons why:

Standardization and Clarity: The absence of a standardized token identification system creates confusion and hampers the development of robust token ecosystems. By providing a unified approach to token identification, the registry brings clarity and standardization to the tokenized economy. It enables users to easily distinguish between different tokens, reducing ambiguity and enhancing overall user experience.
Trust and Verification: Trust and verification are critical aspects of the token economy. The registry establishes a decentralized and secure method for verifying token ownership and authenticity. By leveraging blockchain technology, which is inherently transparent and tamper-resistant, the registry enhances trust among token holders, investors, and ecosystem participants. It mitigates the risks associated with fraudulent tokens and fake issuers, promoting a more secure and reliable tokenized environment.
Interoperability and Cross-Chain Transactions: Interoperability is crucial for the growth and expansion of the token economy. The Digital Token Identifier Registry facilitates interoperability by providing a standardized identification system that can be adopted across different blockchain platforms. This allows tokens from various blockchains to interact seamlessly, enabling cross-chain transactions and fostering collaboration between different tokenized ecosystems. As a result, the registry opens up new possibilities for innovation, liquidity, and scalability within the token economy.
Transparency and Immutability: By utilizing the Cosmos blockchain framework, the registry ensures transparency and immutability of token information. The token data stored in the registry is cryptographically secured and cannot be altered or manipulated without consensus from the network participants. This transparency and immutability promote accountability, reduce the risk of data tampering, and provide a reliable source of truth for token information.
Scalability and Efficiency: The Cosmos blockchain framework offers scalability and efficiency advantages, making it well-suited for the Digital Token Identifier Registry. As the token economy continues to grow, scalability becomes a crucial factor in handling the increasing number of tokens and transactions. The registry's implementation on Cosmos enables seamless scalability, ensuring that it can accommodate a large number of tokens and support high transaction volumes without compromising performance.

Overall, the Digital Token Identifier Registry addresses significant challenges in the tokenized economy, enhances trust and verification, promotes interoperability, and provides a standardized and secure method for identifying and verifying digital tokens. It serves as a foundational infrastructure that fosters innovation, improves user experience, and drives the growth of the token economy
why IBC enabled digital token identifier registry
In an IBC-enabled digital token identifier registry, one of the key benefits is the ability to share the registered token information on other chains within the network. The IBC protocol facilitates the secure communication and transfer of token information between independent blockchains.
Here's how the sharing of registered token information occurs:

Token Registration: Tokens are registered on a specific blockchain within the digital token identifier registry. This blockchain acts as the source chain for the tokens.
IBC Channels: The digital token identifier registry establishes IBC channels with other participating blockchains within the Cosmos network or other IBC-enabled networks. These channels serve as communication pathways between the source chain and the destination chains.
Token Information Sharing: The digital token identifier registry shares the registered token information, such as token ID, name, symbol, and metadata, with the connected destination chains through the established IBC channels. This sharing of information ensures that the destination chains have access to the standardized token data.
Synchronization and Updates: As the registered token information is updated on the source chain, such as changes to token metadata or ownership, the digital token identifier registry propagates these updates to the connected destination chains via the IBC channels. This synchronization ensures that the token information remains consistent and up-to-date across all participating chains.
Token Utilization on Other Chains: With the shared token information, the destination chains can leverage the registered tokens for various purposes. This includes using the tokens in decentralized applications, integrating them into smart contracts, or facilitating cross-chain transactions and interoperability.

By leveraging IBC, the digital token identifier registry enables the sharing of registered token information across multiple independent chains. This promotes transparency, standardization, and interoperability, as token data can be accessed and utilized on different chains within the network. It enhances the overall token ecosystem, expands token liquidity, and fosters collaboration and integration among different blockchain communities
In an IBC-enabled digital token identifier registry, it is possible to register a token on a specific blockchain within the registry and then share the token information with all other IBC-enabled chains within the network, Here are some ways in which it helps token users;

Enhanced Accessibility: By sharing token information across multiple chains, token users gain increased accessibility to their registered tokens. They can interact with and utilize their tokens on various chains within the network, depending on their specific needs and preferences. This widens the range of platforms, applications, and services available to token users, providing them with more options for token utilization.
Expanded Market Reach: Sharing token information across multiple chains enables token users to tap into a broader market reach. Tokens can be traded and used on different chains and decentralized exchanges within the network, potentially reaching a larger user base. This increased market reach can enhance token liquidity and facilitate broader adoption and usage of the tokens.
Cross-Chain Compatibility: The shared token information ensures cross-chain compatibility, allowing token users to seamlessly transfer and utilize their tokens across different chains. Token holders can transfer their tokens from one chain to another through the established IBC channels, enabling cross-chain transactions and interactions. This flexibility provides token users with more freedom and versatility in managing their token holdings.
Interoperability and Integration: The shared token information promotes interoperability and integration between different chains within the network. Token users can leverage their registered tokens in various decentralized applications, services, and platforms that are available on different chains. This fosters collaboration and synergy between different blockchain communities, opening up new opportunities and functionalities for token users.
Consistency and Standardization: The shared token information ensures consistency and standardization of token data across multiple chains. Token users can rely on consistent token identification, verification, and metadata regardless of the chain they are using. This simplifies token management and reduces confusion, providing a seamless experience for token users.

Overall, sharing token information with all IBC-enabled chains within the network in an IBC-enabled digital token identifier registry greatly benefits token users by enhancing accessibility, expanding market reach, enabling cross-chain compatibility, promoting interoperability, and ensuring consistency and standardization of token data. It empowers token holders with more choices, opportunities, and a seamless user experience within the tokenized ecosystem.

Take a look at this material
https://www.iso.org/obp/ui/#iso:std:80602:en


don't send a window update after the final offset was received

Fixes #989.
Receiving a final offset means the peer is done sending on that stream, and there's no need to grant additional flow control credit.

Codecov Report

Merging #990 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #990      +/-   ##
==========================================
+ Coverage   90.75%   90.75%   +<.01%
==========================================
  Files          99       99
  Lines        6539     6541       +2
==========================================
+ Hits         5934     5936       +2
  Misses        389      389
  Partials      216      216

Impacted Files
Coverage Δ

internal/flowcontrol/stream_flow_controller.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


v1

model and dataset configs
base dataset
logging
cli
docs and api v1

I will close this and re-open if needed in the future


Change FFmpeg build to GyanD's "essentials" compile

Hello,
I would suggest using the "essentials" GPLv3 build of FFmpeg by @GyanD. From a brief look, it appears to contain all the libraries required for FFMPEG-Audio-Encoder, but with an executable size reduction of 35.65%; this translates to ~115 MB being reduced to ~74 MB).
You can find the source and compiled releases here, and more information here.
Regards,
Piers

I plan to do some work soon to the program. I have some things I'd like to do, a new feature among other things. I will test with the essential build and as long as it supports all the codecs then I will change the ffmpeg to that. A reduction in file size would be great. Thanks for bringing this to my attention.

I did some testing, the essential build has everything that is needed and I will certainly add it to the program in place of the full ffmpeg build. Thank you for pointing this out!


crash on large magnitude Integer literals

General and specific issues:

The spec does not limit the size of integer values; it is backend specific. For example, the Ceylon/JS Integer range extends well beyond that of Java's long.
Even for the JVM (64-bit Integer), the full range is not currently supported by ceylon.ast; -9223372036854775808 appearing in code results in an assertion error.

IntegerLiteral.integer is of type Integer, but should be Whole or String. I suggest we go with String for now (or simply remove the integer property?), and use Whole in 1.3 if Whole goes cross-platform.

The stacktrace:
Exception in thread "main" ceylon.language.AssertionError "Assertion failed
	violated exists _integer = parseInteger(radix == 10 then text else text.rest, radix)"
	at ceylon.ast.core.IntegerLiteral.<init>(IntegerLiteral.ceylon:23)
	at ceylon.ast.redhat.integerLiteralToCeylon_.integerLiteralToCeylon(IntegerLiteral.ceylon:21)
	at ceylon.ast.redhat.literalToCeylon_.literalToCeylon(Literal.ceylon:35)
	at ceylon.ast.redhat.atomToCeylon_.atomToCeylon(Atom.ceylon:33)
	at ceylon.ast.redhat.primaryToCeylon_.primaryToCeylon(Primary.ceylon:38)
	at ceylon.ast.redhat.valueExpressionToCeylon_.valueExpressionToCeylon(ValueExpression.ceylon:24)

Done, IntegerLiteral.integer gone.


Unable to mount first shared volume

Errors mounting very first volume and now log spews bunch of error though volume is deleted.
root@u-1:~# docker volume inspect doesitwork1
[
    {
        "Driver": "vfile:latest",
        "Labels": {},
        "Mountpoint": "/mnt/vfile/doesitwork1/",
        "Name": "doesitwork1",
        "Options": {},
        "Scope": "global",
        "Status": {
            "Clients": null,
            "File server Port": 0,
            "Global Refcount": 0,
            "Service name": "",
            "Volume Status": "Ready"
        }
    }
]
root@u-1:~# docker run --rm -it -v doesitwork1:/x busybox
docker: Error response from daemon: error while mounting volume '/mnt/vfile/doesitwork1/': VolumeDriver.Mount: Failed to blocking wait for Mounted state. Error: Timeout reached; BlockingWait is not complete.
ERRO[0042] error waiting for container: context canceled
root@u-1:~#

From vFile.log
2017-08-25 06:36:19.76009732 +0000 UTC [INFO] Attempting to change volume state to Mounting
2017-08-25 06:36:24.798841058 +0000 UTC [INFO] Checking status of file server container...
2017-08-25 06:36:24.806640127 +0000 UTC [INFO] File server not running for volume doesitwork1
2017-08-25 06:36:29.798760213 +0000 UTC [INFO] Checking status of file server container...
2017-08-25 06:36:29.804070783 +0000 UTC [INFO] File server not running for volume doesitwork1
2017-08-25 06:36:34.798926048 +0000 UTC [INFO] Checking status of file server container...
2017-08-25 06:36:34.809954321 +0000 UTC [INFO] File server not running for volume doesitwork1
2017-08-25 06:36:39.798648045 +0000 UTC [INFO] Checking status of file server container...
2017-08-25 06:36:39.80520654 +0000 UTC [INFO] File server not running for volume doesitwork1
2017-08-25 06:36:44.798918106 +0000 UTC [INFO] Checking status of file server container...
2017-08-25 06:36:44.806325808 +0000 UTC [INFO] File server not running for volume doesitwork1
2017-08-25 06:36:49.798784148 +0000 UTC [INFO] Checking status of file server container...
2017-08-25 06:36:49.80634023 +0000 UTC [INFO] File server not running for volume doesitwork1
2017-08-25 06:36:49.807108924 +0000 UTC [WARNING] Timeout reached while waiting for file server container for volume doesitwork1
2017-08-25 06:36:59.827002073 +0000 UTC [INFO] Watcher on global refcount returns event type=PUT
2017-08-25 06:36:59.828133378 +0000 UTC [ERROR] name=doesitwork1 error="Failed to blocking wait for Mounted state. Error: Timeout reached; BlockingWait is not complete."
2017-08-25 06:36:59.828665677 +0000 UTC [ERROR] Failed to mount name=doesitwork1 error="Failed to blocking wait for Mounted state. Error: Timeout reached; BlockingWait is not complete."
2017-08-25 06:36:59.829108093 +0000 UTC [INFO] Detaching doesitwork1 - it is not used anymore
2017-08-25 06:37:00.827970333 +0000 UTC [INFO] Attempting to change volume state to Unmounting
2017-08-25 06:37:00.855648518 +0000 UTC [INFO] Volume not in proper state for the operation: Error

I noticed smb container was running on different node after above errors.
Deleting volume using docker volume rm failed with "volume in use" error.
Removed smb container and then successfully remvoed volume.
However, log continues to spew errors;\
2017-08-25 07:19:49.299714501 +0000 UTC [INFO] VolumeDriver Get: InternalVoldoesitwork1
2017-08-25 07:19:49.361141773 +0000 UTC [INFO] Volume not found: InternalVoldoesitwork1
2017-08-25 07:19:49.361253167 +0000 UTC [ERROR] Failed to get volume meta-data error="No such volume" name=InternalVoldoesitwork1
2017-08-25 07:19:49.388447773 +0000 UTC [INFO] VolumeDriver Get: InternalVoldoesitwork1
2017-08-25 07:19:49.45516289 +0000 UTC [INFO] Volume not found: InternalVoldoesitwork1
2017-08-25 07:19:49.45538344 +0000 UTC [ERROR] Failed to get volume meta-data name=InternalVoldoesitwork1 error="No such volume"
2017-08-25 07:19:49.457042605 +0000 UTC [WARNING] Failed to remove internal volume for volume doesitwork1. Reason: Error response from daemon: {"message":"get InternalVoldoesitwork1: no such volume"}. Failed to inspect internal volume. Error: Error: No such volume: InternalVoldoesitwork1.

Even you see the volume still in use error, it's from the base plugin,
we will still continue delete the vFile volume.
And the garbage collector will eventually delete the service along with the internal volume.
Do you mean the errors will continue and won't stop?

2017-08-25 06:37:00.855648518 +0000 UTC [INFO] Volume not in proper state for the operation: Error

Even the volumes is not mounted due to timeout, the status should not be error.
I will look into this one.

The upcoming PRs https://github.com/vmware/docker-volume-vsphere/pull/1819 and https://github.com/vmware/docker-volume-vsphere/pull/1799 should be able to alleviate the symptom here.


Logitech Webcam C920 - Issues with video for MS Teams

ℹ Computer information

PowerToys version: 0.22
PowerToy Utility: VideoConf
Running PowerToys as Admin: Yes
Windows build number: 19041.450

📝 Provide detailed reproduction steps (if any)

Enable VideoConf in PowerToys
Change default camera in Power Toys Video Conf to Logitech Webcam C920
Change default camera in Teams to Powertoys camera

✔ Expected result
Expected result is for video to display during a Teams call
❌ Actual result
Video content actually looks like a strobe light rather than webcam video
Notes
I've tested this with Zoom meetings and the Video Conference feature works great in Zoom.  However, in Teams it is unusable right now.

Happened to have a call with Goto Meeting and it said that it couldn't recognize the camera.  So to summarize:
Teams - Flashing strobe light
Zoom - Works perfectly
Goto Meeting - Camera not recognized

@titleist380
can you also try the Windows 10 Camera app? Thanks.

Issue tracked in https://github.com/microsoft/PowerToys/issues/6246

I have the same issue with the Windows 10 Camera app - thanks!
On Fri, Sep 4, 2020 at 11:11 AM Enrico Giordani<EMAIL_ADDRESS>wrote:

@titleist380 https://github.com/titleist380
can you also try the Windows 10 Camera app? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/6338#issuecomment-687210226,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQDVIHJWXUQYP73NLCIXZDSED7STANCNFSM4QVHLDPA
.

Does the issue still there in the latest version?

It's still problematic.  When I use the Win10 camera app, the camera is on,
but the overlay tells me the camera is not in use (just mute is an
option).  I did a quick test with Zoom and when I try to enable the camera,
I get zoom errors saying the camera cannot be started.  I'm more than happy
to try anything else that might help.  Note that I'm using 0.36 since I
didn't see this as part of 0.37.
On Thu, May 6, 2021 at 11:36 AM Andrey Nekrasov @.***>
wrote:

Does the issue still there in the latest version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/6338#issuecomment-833621246,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQDVIAACJPN2CXATSNTQW3TMKZORANCNFSM4QVHLDPA
.

@titleist380
the VCM starting from 0.36.0 doesn't support anymore the camera app, just video conference apps.

is this an issue with the inconsistent behaviour/support for 50hz/60hz (aka Powerline) support/settings in Windows - even for some apps/drivers that have support for it, it's not always handled well.
Skype and Zoom have explicit settings and seem to handle it well, Teams has no setting (and seems to ignore a RegEdit hack to fix)
Would be a great feature if the Powertoy could 'fix' the poor behaviour across the board for us on non-US power ;)
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/35661376-allow-selection-of-camera-flicker-frequency-betwee

Thanks for the feedback but VCM is moving to maintenance only in the 0.67 timeframe. Our team will only directly address critical bugs, security and accessibility issues.
We'll accept community PRs for enhancements.


LightmapGI: Fix shader data alignment after #89919

Fixes shader data alignment after the bicubic sampling PR (whoops)

Thanks!


Allows retrieving the tasks output from operator client terminal

This PR allows retrieving the tasks output from the operator client terminal.
In addition to printing the task output to be seen in CloudWatch, the agent lambda uploads the task output to S3. Then, the output can be retrieved by the operator client using the --get-task option.

This is great - thanks for the contribution!


Enhance user experience when artifacts are deleted from repositories

Currently, if an artifact is deleted, Gradle (correctly) only attempts to retrieve it from that same repo, even if other repositories have it. Unfortunately, this isn't very obvious to end users, who will only see Gradle using one repository and wonder why it isn't checking the others.
Gradle should indicate in some way that this is happening, and provide advice on how to fix it (content filters, removing the relevant cached metadata file, reordering repositories).

We should see if this is the case when just an artifact is deleted, artifact+metadata or something else.

I couldn't figure out how to reproduce this. It may be fixed now.


Test how raw queries actually work

[x] Add Querier helpers query_wasm_{smart,raw}
[x] Expose raw query on reflect so we can double check this

Looks good overall. A few minor changes are here: #568.


Prepare 1.12.5

Prepare 1.12.5 and fix some errors in the spec file.
Still to be done:

[x] #2 should be merged before this PR.
[x] update changelog and bump version.

So before merging this we need to figure why the manpage and the license file are not installed while they are in the RPM. (tested using centos:7 docker image)

So before merging this we need to figure why the manpage and the license file are not installed while they are in the RPM. (tested using centos:7 and centos:6 docker images)
So it's due to https://github.com/CentOS/sig-cloud-instance-build/blob/98aa8c6f0290feeb94d86b52c561d70eabc7d942/docker/centos-6.ks#L80.
Installing with rpm -i --includedocs lcg-info*.rpm works fine.


Verify new users with email verification

Game Plan so far

Implement Email verification right after registration.
Abstract email verification as webhook post registration.
Make Route to re-call email verification on-demand (rate limited).


Model examples

MRF
Linear CRF
Skip-chain CRF
Bayes Net
LDA
Min-Cut
Correlation Clustering

This is too dated and lacks detail for action. Let's close this and reopen or create a new issue if needed.


Importing 2+ React Components into the same module fails

I have a file that looks like:
module Arrow = {
  /* Module with the JS component to be wrapped. */
<EMAIL_ADDRESS>"components/images/Arrow.jsx"]
  /* The make function will be automatically generated from the types below. */
  external make:
    (~fill: string=?, 'children) =>
    ReasonReact.component(
      ReasonReact.stateless,
      ReasonReact.noRetainedProps,
      ReasonReact.actionless,
    ) =
    "";
};

module Legal = {
  /* Module with the JS component to be wrapped. */
<EMAIL_ADDRESS>"components/Legal/Legal.jsx"]
  /* The make function will be automatically generated from the types below. */
  external make:
    (~active: bool=?, ~errorTryAgain: bool=?, 'children) =>
    ReasonReact.component(
      ReasonReact.stateless,
      ReasonReact.noRetainedProps,
      ReasonReact.actionless,
    ) =
    "";
};

However it produces the following output:
/* Untyped file generated by genType. */

import Arrow from 'components/images/Arrow.jsx';

import * as React from 'react';

import Legal from 'components/Legal/Legal.jsx';

// Export 'make' early to allow circular import from the '.bs.js' file.
export const make = function (fill, children) { return ReasonReact.wrapJsForReason(Arrow, {fill: fill}, children); };

// Export 'make' early to allow circular import from the '.bs.js' file.
export const make = function (active, errorTryAgain, children) { return ReasonReact.wrapJsForReason(Legal, {active: active, errorTryAgain: errorTryAgain}, children); };

As you can see the make function is exported over and over which means that Webpack fails with the following error:
[start-js-no-clear] Failed to compile.
[start-js-no-clear]
[start-js-no-clear] ./src/components/JsSvgs.gen.js
[start-js-no-clear] Syntax error: `make` has already been exported. Exported identifiers must be unique. (37:13)

Workaround
make them all separate files.

@justgage thanks for pointing this out.
Externals in the language are not scoped, no matter if they're declared in different sub modules, so  both externals refer to make from ThisFile.gen.
Supporting 2 component imports in the same file would require at least to use 2 different names (and relaxing the convention that a component is a function called make).

@cristianoc oh, very cool, didn't know that. Thanks for pointing that out!


Structs in PIL

This PR implements structs based on the issue #1016.
To avoid ambiguity with the grammar, for creating an instance of a struct and for accessing its fields, a temporary variation of the grammar is used which should be discussed.
Currently, an instance of struct X {x: int, y: int} is created using X with {x: 1, y:0}.

It would be nice to fix struct expression parsing - we can do this in a separate PR that potentially also just parses it into nothing (so that we don't need all the other ast types).

Ah sorry, you already made a PR for that. Will take a look!

Ah sorry, you already made a PR for that. Will take a look!

Sorry, it's my fault, I should have specified the PR order somewhere.
So. this is the base PR. Then, I will recommend the follwoing order:

#1591
#1586
#1585

I started the simplification of this PR:

Definitions and statement processor: #1906
Field checking before type checking: #1907

This has been simplified into the following PRs:

Definitions and statement processor: #1906
Field checking before type checking: #1907
Type inference: #1910
Condenser & Evaluator: #1911


[Question] Is Compass Widget available ?

Is there any Compass widget available to display North ?

Ummm, current no. What information should this compass widget provide? How compass widget is related to user location or direction?


Error while recovering original scaffolding

Hello again,
after last times succesful and quick bug handling (again, many thanks!), I've encountered a new error message while trying to recover the original scaffolding after shredding. My workflow is :
agouti.py shred -assembly genome.fasta -gff genome.gff -p scaffold

bwa index -p contigmapping -a bwtsw scaffold.ctg.fasta

bwa mem -t 80 -T 30 -P -k 20  contigmapping R1_reads.fastq R2_reads.fastq > mapping.ctg.sam

samtools view -Sb mapping.ctg.sam > mapping.ctg.bam

python agouti.py scaffold -assembly scaffold.ctg.fasta -bam mapping.ctg.bam -gff scaffold.ctg.gff -outdir ./run1 -shredpath scaffold.shred.info.txt

The error i get is

2016-08-04 06:36:27,146 - INFO - AGOUTI_PATH PROGRESS - Analyzing scaffolding paths
2016-08-04 06:36:27,148 - INFO - AGOUTI_PATH PROGRESS - [BEGIN] Reading file with shred info
2016-08-04 06:36:27,931 - ERROR - AGOUTI_PATH PROGRESS - Number of shredded contigs parsed: 242231
2016-08-04 06:36:27,931 - INFO - AGOUTI_PATH PROGRESS - [DONE]
2016-08-04 06:36:27,931 - INFO - AGOUTI_PATH PROGRESS - [BEGIN] Recovring original scaffolding
Traceback (most recent call last):
File "agouti.py", line 283, in
main()
File "agouti.py", line 280, in main
args.func(args)
File "agouti.py", line 219, in run_scaffolder
prefix)
File "src/agouti_path.py", line 38, in agouti_path_main
agPathDebug)
File "src/agouti_path.py", line 114, in recover_untouched_sequences
preIndex = int(preGeneID.split('_')[1])
ValueError: invalid literal for int() with base 10: 'shred'

I'm under the impression it tries to recover unshredded genes from the gff but somehow still gets the shredded ones and therefore has trouble with the ID. My workaround so far is:
`if curCtg in dGFFs:
    curCtgGeneModel5 = dGFFs[curCtg][0]
    if not curCtgGeneModel5.fake:
        curGeneID = curCtgGeneModel5.geneID
        if curGeneID.split('_')[1] != "shred":
            curIndex = int(curGeneID.split('_')[1])`

starting line 116 in agouti_path.py, but the rerun has not reached that phase yet, because it is still graph building. Which brings me to the question, whether there is a way to recover the outcome of

INFO - AGOUTI_SCAFFOLDING PROGRESS - Building graph from joining reads pairs

from a previous run.
Cheers,
Nico

oh and if it helps here is a line in the gff of an untouched gene

Scaffold22931   I5K     gene    213     938     .       -       .       ID=BGER028140;Name=Dmel-Tmp-reg-2;Dbxref=i5kP_homolog_AGAMB:AGAP004954-PA;Dbxref=i5kP_homolog_AMEL:GB46617-PA;Dbxref=i5kP_homolog_BMORI:BGIBMGA002078-PA;Dbxref=i5kP_homolog_CELEG:K01G5.10;Dbxref=i5kP_homolog_DMELA:FBpp0072460;Dbxref=i5kP_homolog_HSAPI:ENSP00000238379;Dbxref=i5kP_homolog_MMUSC:ENSMUSP00000036337;Dbxref=i5kP_homolog_TCAST:TC003205;Dbxref=i5kP_homolog_DMELA:FBpp0070645;

and this is of a shredded gene:

Scaffold1_0_0   I5K     gene    7742    21351   .       -       .       ID=agouti_shred_gene_1_0;

Hello Nico,
I don't think the error came from your command line.
This line below seems strange:
Scaffold1_0_0 I5K gene 7742 21351 . - . ID=agouti_shred_gene_1_0;
Is the scaffold ID in your scaffold Fasta like "Scaffold1", and the AGOUTI shred gave your "Scaffold1_0_0"? Also the shredded gene ID should be "BGER028140_0" instead of "agouti_shred_gene_1_0".
Please give me some time to find where it goes wrong. I will let you know.
Simo

Thanks for taking care of it. If it helps, my original scaffold name was indeed scaffold1_0 because i had to manually cut out something in between and make the initial scaffold1 into scaffold1_0 and scaffold1_1. I could easily change the underscore to anything else if it messes with the program

I might know where it goes wrong. Let me see if I can make a quick fix.
Meanwhile, I just updated my comment upstairs. Could you give a look and provide me the file, just in case the quick fix I am thinking fails. You can send the debug file to<EMAIL_ADDRESS>

I'll run the debug version and let you know when it finishes. Will take some time though, the genome is quite large and lots of reads

Can I also ask you what version of AGOUTI you are using? I think you might use an older version.
File "src/agouti_path.py", line 114, in recover_untouched_sequences preIndex = int(preGeneID.split('_')[1]) ValueError: invalid literal for int() with base 10: 'shred'
In the current version I have locally I don't have this line in my recover_untouched_sequences anymore.
And your quick workaround:
if curCtg in dGFFs:     curCtgGeneModel5 = dGFFs[curCtg][0]     if not curCtgGeneModel5.fake:         curGeneID = curCtgGeneModel5.geneID         if curGeneID.split('_')[1] != "shred":             curIndex = int(curGeneID.split('_')[1])
My current version is:
`if curCtg in dGFFs:
curCtgGeneModel5 = dGFFs[curCtg][0]
if not curCtgGeneModel5.fake:
tmpName = curCtgGeneModel5.geneID.split('_')
curGeneID = tmpName[:-1]
'
Could you git pull the lastest repo?

yep. restartign job right now with the newest version. Will let you know how it goes

Please run it with --debug just in case. If you type
python agouti.py --version
it should give you something like AGOUTI v0.3.3-dirty.

its v 0.3.3 for me. is currently runnign in debug mode

So i had it run with the newest version and without the initial scaffold_1 underscore names. everything ran just fine

That's good to hear.
But I think it should also work for the initial scaffold_1 underscore names. AGOUTI appends the index at the end of the names, and it always read index from the last element split by underscore.

Hello Nico,
I am wondering does AGOUTI work for your scaffold with prefix scaffold_1?
Simo

Hi Simo,
tried it on a test dataset and seemed to have worked. Maybe the old
agouti version was the only issue here
Cheers,
Nico
On 12.08.2016 19:58, Simo V Zhang wrote:

Hello Nico,
I am wondering does AGOUTI work for your scaffold with prefix
|scaffold_1|?
Simo
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/svm-zhang/AGOUTI/issues/7#issuecomment-239516677,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH9VMABUBuhNAnOKtJ0xPnnVJ8fNxz7uks5qfLRjgaJpZM4Jcf-v.

--
Nicolas Arning
MSc-Student
Evolutionary Bioinformatics Group
Institute for Evolution and Biodiversity
Westfälische Wilhelms-Universität
Room 100.19, Hüfferstrasse 1, 48149 Münster
Tel: +49-(0)251 - 83-21633
Group page: http://www.bornberglab.org

Hi Nico,
That's good to hear. Thanks for letting me know.
I am closing this thread now. Let me know if other issues pop out.
Simo


Go-Machine-Service errors out and keeps restarting

Rancher v0.18.2
Docker Version 1.5.0
I set up an EC2 machine using this AMI (ami-1ecae776), which is the required AMI that a user had. I just re-checked my instance and it looks as if go-machine-service is restarting every day. Is this normal?
Logs for my instance:
time="2015-05-07T08:08:20Z" level=info msg="Exiting go-machine-service..."
time="2015-05-07T08:08:22Z" level=info msg="Setting log level" logLevel=info
time="2015-05-07T08:08:22Z" level=info msg="Starting go-machine-service..."
time="2015-05-07T08:08:22Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-07T08:08:22Z" level=info msg="Connection established"
2015-05-07 08:35:23,224 ERROR [:] [] [] [] [utorService-177] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-07T20:08:30Z" level=info msg="Exiting go-machine-service..."
time="2015-05-07T20:08:31Z" level=info msg="Setting log level" logLevel=info
time="2015-05-07T20:08:31Z" level=info msg="Starting go-machine-service..."
time="2015-05-07T20:08:31Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-07T20:08:32Z" level=info msg="Connection established"
2015-05-07 20:35:36,184 ERROR [:] [] [] [] [utorService-325] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-08T08:08:42Z" level=info msg="Exiting go-machine-service..."
time="2015-05-08T08:08:43Z" level=info msg="Setting log level" logLevel=info
time="2015-05-08T08:08:43Z" level=info msg="Starting go-machine-service..."
time="2015-05-08T08:08:43Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-08T08:08:44Z" level=info msg="Connection established"
2015-05-08 08:35:56,233 ERROR [:] [] [] [] [utorService-419] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-08T20:08:54Z" level=info msg="Exiting go-machine-service..."
time="2015-05-08T20:08:55Z" level=info msg="Setting log level" logLevel=info
time="2015-05-08T20:08:55Z" level=info msg="Starting go-machine-service..."
time="2015-05-08T20:08:55Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-08T20:08:56Z" level=info msg="Connection established"
2015-05-08 20:36:15,019 ERROR [:] [] [] [] [utorService-515] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-09T08:09:07Z" level=info msg="Exiting go-machine-service..."
time="2015-05-09T08:09:09Z" level=info msg="Setting log level" logLevel=info
time="2015-05-09T08:09:09Z" level=info msg="Starting go-machine-service..."
time="2015-05-09T08:09:09Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-09T08:09:09Z" level=info msg="Connection established"
2015-05-09 08:36:29,812 ERROR [:] [] [] [] [utorService-634] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-09T20:09:19Z" level=info msg="Exiting go-machine-service..."
time="2015-05-09T20:09:21Z" level=info msg="Setting log level" logLevel=info
time="2015-05-09T20:09:21Z" level=info msg="Starting go-machine-service..."
time="2015-05-09T20:09:21Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-09T20:09:21Z" level=info msg="Connection established"
2015-05-09 20:36:43,586 ERROR [:] [] [] [] [utorService-746] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-10T08:09:31Z" level=info msg="Exiting go-machine-service..."
time="2015-05-10T08:09:33Z" level=info msg="Setting log level" logLevel=info
time="2015-05-10T08:09:33Z" level=info msg="Starting go-machine-service..."
time="2015-05-10T08:09:33Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-10T08:09:33Z" level=info msg="Connection established"
2015-05-10 08:36:57,382 ERROR [:] [] [] [] [utorService-856] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-10T20:09:41Z" level=info msg="Exiting go-machine-service..."
time="2015-05-10T20:09:42Z" level=info msg="Setting log level" logLevel=info
time="2015-05-10T20:09:42Z" level=info msg="Starting go-machine-service..."
time="2015-05-10T20:09:42Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-10T20:09:43Z" level=info msg="Connection established"
2015-05-10 20:37:13,174 ERROR [:] [] [] [] [utorService-942] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-11T08:09:53Z" level=info msg="Exiting go-machine-service..."
time="2015-05-11T08:09:54Z" level=info msg="Setting log level" logLevel=info
time="2015-05-11T08:09:54Z" level=info msg="Starting go-machine-service..."
time="2015-05-11T08:09:54Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-11T08:09:55Z" level=info msg="Connection established"
2015-05-11 08:37:26,010 ERROR [:] [] [] [] [torService-1014] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-11T20:10:03Z" level=info msg="Exiting go-machine-service..."
time="2015-05-11T20:10:04Z" level=info msg="Setting log level" logLevel=info
time="2015-05-11T20:10:04Z" level=info msg="Starting go-machine-service..."
time="2015-05-11T20:10:04Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-11T20:10:04Z" level=info msg="Connection established"
2015-05-11 20:37:44,600 ERROR [:] [] [] [] [torService-1114] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-12T08:10:15Z" level=info msg="Exiting go-machine-service..."
time="2015-05-12T08:10:16Z" level=info msg="Setting log level" logLevel=info
time="2015-05-12T08:10:16Z" level=info msg="Starting go-machine-service..."
time="2015-05-12T08:10:16Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-12T08:10:16Z" level=info msg="Connection established"
2015-05-12 08:37:54,378 ERROR [:] [] [] [] [torService-1219] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-12T20:10:25Z" level=info msg="Exiting go-machine-service..."
time="2015-05-12T20:10:25Z" level=info msg="Setting log level" logLevel=info
time="2015-05-12T20:10:25Z" level=info msg="Starting go-machine-service..."
time="2015-05-12T20:10:25Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-12T20:10:26Z" level=info msg="Connection established"
2015-05-12 20:38:12,981 ERROR [:] [] [] [] [torService-1331] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]
time="2015-05-13T08:10:35Z" level=info msg="Exiting go-machine-service..."
time="2015-05-13T08:10:35Z" level=info msg="Setting log level" logLevel=info
time="2015-05-13T08:10:35Z" level=info msg="Starting go-machine-service..."
time="2015-05-13T08:10:35Z" level=info msg="Initializing event router" workerCount=10
time="2015-05-13T08:10:36Z" level=info msg="Connection established"
2015-05-13 08:38:25,773 ERROR [:] [] [] [] [torService-1433] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [1] count [1]

Is this related: #672
Both mention gms restarting.

Nope, completely separate issues. Mine was kind of stumbled upon accidentally. The person also had issues with gms restarting over and over.

Always 12 hours apart?  Weird.  There's nothing in GMS that does that so something else is causing it to re-subscribe.

Please re-test.

Tested and could not reproduce. Bouncing to @sangeethah

Closing as not reproducible


🎉 3.0.0

ℹ About this release

Version: 3.0.0
Type: major
Last Release: 2.0.5 (2/8/2023, 8:32:05 PM) [?]
Commits to merge: 35 [?]

Build System

Deprecate node.js 12 (426588b)

⚡ BREAKING CHANGES

From now on, only node.js ^14.8.0 || >=16.0.0 are supported

📦 Dependencies

Update ical-generator from ^3.6.1 to ^4.0.0

📦 Development Dependencies

Added tsup ^6.7.0
Update @qiwi/semantic-release-gh-pages-plugin from ^5.2.4 to ^5.2.5
Update @sebbo2002/semantic-release-docker from ^2.1.0 to ^3.0.0
Update @semantic-release/changelog from ^6.0.2 to ^6.0.3
Update @semantic-release/npm from ^9.0.2 to ^10.0.2
Update @types/node from ^18.13.0 to ^18.15.11
Update @typescript-eslint/eslint-plugin from ^5.51.0 to ^5.57.0
Update @typescript-eslint/parser from ^5.51.0 to ^5.57.0
Update c8 from ^7.11.3 to ^7.13.0
Update eslint from ^8.33.0 to ^8.37.0
Update eslint-plugin-jsonc from ^2.6.0 to ^2.7.0
Update typedoc from ^0.23.24 to ^0.23.26
Update typescript from ^4.9.5 to ^5.0.3

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
Docker container (sebbo2002/fitness-first-ical-proxy:3.0.0)
v3.0.0

Your semantic-release bot :package::rocket:


Unable to delete archivable and timestampable objects

Trying to delete() object, which has both archivable and timestampable behaviours.
It seems that _archive tables don't inherit created_at and updated_at columns / methods.
PropelException: Call to undefined method: setCreatedAt in /WWW/vendor/propel/runtime/lib/om/BaseObject.php on line 400

Call Stack:
    0.0008     650064   1. {main}() /WWW/admin/ajax/user-remove.php:0
    0.0072    1615872   2. BaseUser->archive() /WWW/admin/ajax/user-remove.php:8
    0.0093    2052040   3. BaseUser->copyInto() /WWW/build/classes/project/om/BaseUser.php:3000
    0.0094    2064880   4. UserArchive->setCreatedAt() /WWW/build/classes/project/om/BaseUser.php:1571
    0.0095    2065232   5. BaseObject->__call() /WWW/build/classes/project/om/BaseUser.php:1571

@fzaninotto any ideas ?


torii adapter not being invoked

I have an adapter:
https://github.com/wayne-o/sonatribe/blob/torii/src/sonatribe-ui/app/torii-adapters/facebook-oauth2.js
Which follows the convention for adding an adapter so that I can send the auth code to the server to log in on my api once authenticated. However the adapter isn't being invoked. Should this still work when using torii with the simple auth stuff?

Please post these kinds of general questions on stackoverflow.com and use this for issues. If it is an issue it should probably go into the Vestorly/torii issue tracker.

done: http://stackoverflow.com/questions/27890654/ember-simple-auth-and-torii

Hi @wayne-o  Have you found a solution? I think that I have the same problem but the link to SO is dead

I am getting there - I am doing this for an OS project - here is the UI part of the code:
https://github.com/wayne-o/sonatribe-ui
I'm about to do some refactoring though to clean it up so you may want to hold off lifting any code from it.


Ability to sign created word lists

Idea: Add a feature to let users cryptographically sign created word lists. Could be inline or separate file?
Could use a PGP library or minisign, using a crate like this one.
Or maybe best to leave this task to other tools.... Tidy can pipe to or from them.

Tabling this for now. Not sure if it's needed ahead of other feature requests.


[Event Request] Report 5692 Calculate Depreciation - OnAfterGenJnlLineInsert #3536

This event does not exist, but is marked as closed. Can you implement it in new release?

Please always put the full detailed signature of the requested events.
If you use AL code copied from VSCode instead of screenshots it will speed up the process of implementation.


Error trying to segment with trained model

I'm trying to use a model I've trained on my own data, but I'm getting an error. This is the command I used to train the model:
$ python -m cellpose --train --train_size --dir train_data --pretrained_model None --chan 1 --chan2 2
And this is the command and output trying to segment a couple images with it:
$ python -m cellpose --dir test/ --pretrained_model train_data/models/cellpose_residual_on_style_on_concatenation_off_train_data_2021_07_16_10_57_23.505527 --chan 1 --chan2 2 --save_png
>>>> using CPU
>>>> using diameter 30.00 for all images
>>>> running cellpose on 2 images using chan_to_seg RED and chan (opt) GREEN
parsing model string to get cellpose options
Running test snippet to check if MKL-DNN working
see https://pytorch.org/docs/stable/backends.html?highlight=mkl
** MKL version working - CPU version is sped up. **
  0%|                                                                                | 0/2 [00:00<?, ?it/s]time spent: running network 12.20s; flow+mask computation 14.36
  0%|                                                                                | 0/2 [00:27<?, ?it/s]
Traceback (most recent call last):
  File "/home/jckern/anaconda3/envs/cellpose/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/jckern/anaconda3/envs/cellpose/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/jckern/anaconda3/envs/cellpose/lib/python3.7/site-packages/cellpose/__main__.py", line 252, in <module>
    main()
  File "/home/jckern/anaconda3/envs/cellpose/lib/python3.7/site-packages/cellpose/__main__.py", line 159, in main
    interp=(not args.no_interp))
ValueError: not enough values to unpack (expected 4, got 3)

There were no errors during training, so I'm not sure what the problem is.

I think this is an error from the old version of the code, can you try updating? pip install cellpose --upgrade going to close for now, let me know if it's still not working


apparmor: allow readby and tracedby

Fixes audit errors such as:
type=AVC msg=audit(1550236803.810:143):
apparmor="DENIED" operation="ptrace" profile="docker-default"
pid=3181 comm="ps" requested_mask="readby" denied_mask="readby"
peer="docker-default"
audit(1550236375.918:3): apparmor="DENIED" operation="ptrace"
profile="docker-default" pid=2267 comm="ps"
requested_mask="tracedby" denied_mask="tracedby"
peer="docker-default"
Please do not send pull requests to this docker/docker-ce repository.
We do, however, take contributions gladly.
See https://github.com/docker/docker-ce/blob/master/CONTRIBUTING.md
Thanks!

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:goldwynr/docker-ce.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Please submit PR to https://github.com/moby/moby

Yup @AkihiroSuda, thank you for the contribution but please submit it to the correct repository!

Ok, submitted at:
https://github.com/moby/moby/pull/39121


Video summarization

Fisrt of all, saying that you have built something really cool. I've tried a bit the demo and works pretty decently considering the hard task.
However, I'm interested in the video summarization part but I can't find out how to do it.
Is there any inference example for that part?

Same question! Could you tell me how to inference for video summarization on a video? @QinghongLin


unable to debug in safari with kit 2.92

SyntaxError: Unexpected keyword 'const'. Const declarations are not supported in strict mode.

Apologies for the generic response, but I've released a new v3.0 kit, which has been re-written from the ground up.
It bumps the ReactQL stack to Webpack 4, React 16.4, Apollo Client 2.0, and adds Styled Components, full SSR (even in development), and has been re-written in Typescript. It's leaner, faster and has been brought completely up-to-date.
If you're still using ReactQL (and I appreciate you may not be, given the time lag in my response), I'd recommend checking out the new kit to see if your issue has been answered. If not, please feel free to post a new issue at https://github.com/leebenson/reactql


Can it stream audio from url?

Yes, please see the README. You need to pass Uri object to setDataSource.

This is url http://easemypay.in/jobs/admin/uploads/jobaudios/airland.mp3
audioView.setDataSource(Uri.parse("http://easemypay.in/jobs/admin/uploads/jobaudios/airland.mp3"));
The seekbar keeps loading & shows an infinity symbol at bottom right


Update translation source file for v26.0 string freeze

This PR updates the src/qt/locale/bitcoin_en.xlf translation source file according to Release schedule for 26.0.
Note for reviewers: it is expected to get a zero diff after running make -C src translate locally.

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews
See the guideline for information on the review process.
A summary of reviews will appear here.

Friendly ping @stickies-v @jarolrod :)


Make touchID public

Thanks for the great library.
A small suggestion - the touch ID is really useful to have available from user code.  The reasoning being is that when there are two touches, each may be put into the IC's 1st touch register or the 2nd touch register seemingly at random as the two fingers are moved around (the IC just does this, it is not a problem with your library).  The touch ID is, however, consistent.  Using the touch ID, it becomes easy to work out whether the data in the 1st touch register or the 2nd touch register really represents the first or second touch.  It tells you which of the registers are reporting which finger.
The first finger to be touched will have a touch ID of zero, and it will stay as zero as long as the finger touches the screen.  Similarly with the second finger to be touched, except it will have a touch ID of 1.  Each point read from your library has a touch ID associated with it, this will tell you whether the XY position in the registers is associated with the first finger or the second.
Also, when there is a touch with one finger, then a second (so two touches) and then the first is released, the two touch IDs for the registers operate as follows:
0 15 (first finger down, 15 is no touch)
0 1 (second finger down, this could also flip back and forth to 1 0 at random, depending on which registers are reporting which finger)
1 15 (first finger lifted but the 1st touch register is now reporting the position of the second finger to touch the screen)
All that is needed to make the touch ID available from user code is to move the touchID[2] array to the public section of the class definition.  Not worth creating a PR for!
Thanks again

Sure... this is not a major change in the repo. I'll see when I have time to do this :)

Seems I had some time now ;)
92fb1c4


SVPI-518: split vault-init into vault-init, spi-init, and remote-secret-init scripts

What does this PR do?
The present PR splits vault-init of service-provider-integration-operator repo into vault-init, spi-init, and remote-secret-init in order to create a new set of scripts designed for specific infra-deployments use cases for develop environment.
With this change, the infra-deployments repo will have the spi scripts and it will not call the script in service-provider-integration-operator repo.
What issues does this PR fix or reference?
https://issues.redhat.com/browse/SVPI-518
How to test this PR?
Install RHTAP through bootstrap-cluster script

Set the required environment variables, such as: MY_GIT_FORK_REMOTE, MY_GITHUB_ORG, and MY_GITHUB_TOKEN
Run ./hack/bootstrap-cluster.sh preview --keycloak --toolchain script on infra-deployments dir

Install RHTAP through e2e-tests repo
Before following the steps on https://github.com/redhat-appstudio/e2e-tests#install-appstudio-in-e2e-mode, please set the following environment variables:
export INFRA_DEPLOYMENTS_ORG=rsoaresd
export INFRA_DEPLOYMENTS_BRANCH=SVPI-518

I've tried upgrading from the current version to the one from this PR and it seems to be ok. :+1:

/retest


Does GitHub use this gem?

Just curious, does GitHub use this gem to generate their GraphQL API reference?
https://developer.github.com/v4

Yes. I built that site, and the tooling.

@gjtorikian I was actually looking for a project that would generate a documentation site like GitHub’s, and stumbled upon this project!
Thanks a lot for open sourcing this tool! Any tips or gotchas when replacing the existing SCSS with my own?

I think the only thing that comes to mind--one thing people don't realize--is that you can pass in your own HTML template.
For example, here is the generic default format for an object. But this is a configuration option, and you can just provide your own path to a template to make use of.
I probably should at least update the default SCSS to make it look a little nicer. The current demo site is a little blech...

@gjtorikian Nice! I would add this to the README. I saw the template files when reading the source code but I don't think a casual viewer of the repo would know this is supported!