v2 wishlist

Dividends
Allow for all holders of a token to receive future rewards / dividends / airdrops.
And/or a method for sending to all holders of said token.
Grouping / Unique assets
somewhat NFT-related. Be able to create ITEM token, and an additional token can be attached/grouped accordingly. for example ITEM.sword , ITEM.shield, etc.
anyone who looks up sword/shield would see they're a part of ITEM. and ITEM.sword.asdf might be the only sword of that type in existence.
Messaging
Some form of protocol or compatibility with an existing broadcast system. The token would have a 'feed' or a channel to send messages/news updates transmitted based on the token_id. Every on chain transaction can be a hash of the actual message/update for time-stamping and censorship-resistance.
Voting
built in voting protocol for anyone who creates a token to easily use w/o any programming knowledge required.
Update-able Metadata
native support for updating website, email, etc.
TICKER and maybe name should be static.
Licensing
A spec/protocol to follow so services can query an address to quickly verify the authenticity of a token representing a license. Some licenses might expire after 1 year, some may be considered invalid if they are moved more than once, etc.
Private assets
An issuer broadcasts that NEW token can only be held by person A,B,C and D. Their identities are encrypted (or maybe CDS is used) but only the issuer knows who A,B,C,D are.
Freeze / Unfreeze
ability to 'banlist' or freeze certain bad actors' addresses.

Addition to Freeze
An additional use case for Freeze functionality would be memento tokens. Think of buying a t-shirt at a concert to prove you were there. That kind of use case. Proof that someone acknowledge you by sending you a token, but which should have no monetary value and should not be transferable.
The token should

show up in the wallet
not be transferable

Fraud proofs
If SLP included a mandatory field that said which inputs were to be used for tokens, and there was a rule that all such declared inputs must be valid, then it would make it much simpler to have proofs of invalid SLP transactions.

Multi-sends
It could be nice to add support for sending multiple token types in one transaction. This was considered during SLPv1 design but dropped due to the technical complications.

If one token type input is invalid, is the entire SLP invalid? This makes SLP transaction validity relationship DAG overlap between different token types! Alternative: SLP has distinct validity judgement for each token type, for no overlap.
More token types need to be declared, increasing the message size. Unlikely that more than 4 tokens could be practically sent at once.

Updating token document URI/Hash
At least 2 users have requested the ability to update the token document's URI and hash details.  Here is a link to our previous discussions on how this could be accomplished in PR https://github.com/simpleledger/slp-specifications/pull/11

Tree NFT
Continuation of the NFT extension type 1 here https://github.com/simpleledger/slp-specifications/blob/master/NFT.md, allow a "Type 3" where the descendant "NFT" are also their own groups of "fungible tokens" that can generate descendants. An example will be an origin "items" groups of tokens that can be burned to generate "sword", "bow", "hammer"... tokens, which can then themselves generate NFTs, and so on, e.g. item.sword.flame.fiery_sword_of_doom
While it's relatively easy to extend existing protocol in a strictly hierarchical way (item tokens can genesis sword tokens exactly once), a desirable feature might include making descendants that can increase in supplies by burning more parent tokens. It's unclear exactly how to do that right now and may require some exploration.

Dividends for BCH holders
Allow for all BCH holders to receive future rewards / dividends / airdrops of a certain token.
And/or a method for sending to all BCH holders this token.
Declaratively, without the need to actually send a transaction to everyone. For instance we could have a token BCH_clone_at_X which in its genesis transaction has a script that says a minting transaction is valid, if it mints Y amount to an address which held Y BCH at block X. Then anyone could broadcast such a valid minting transaction.

I'm unclear on the scope of this issue:

Are we discussing a second version of the SLP protocol?

or

Are we discussing Token Type 2 withing the scope of the current SLP protocol

Each version/type of token is essentially a different token protocol.  For example, NFT1 is not token type 1 because it has more rules than Token Type 1.
Version 2 would be a total rewrite of a token protocol.  If the new token type is a minor ruleset extension, like NFT1, then the spec writing can be handled like NFT1 was.

It's worth emphasizing though, it's not a complete rewrite as future SLP2 transactions are supposed to be detected by existing SLP wallets, which should flag all those transaction outputs as 'possibly tokens' and hence not spend them. So, it should be safe to send SLP2 tokens to any simpleledger: address with the knowledge that the recipient won't accidentally burn them, and hence, we don't need yet another simpleledger2: format.
It may be a good idea to carefully get wallet devs all on board with this idea, and specify carefully the rules that future SLP versions will absolutely follow, so that they know which transactions need to be flagged as do-not-spend.
For example one question I am wondering is whether SLP2 will still require the OP_RETURN to be on position 0. After all, the most elegant way to do multitoken is if standardness rules allow multiple OP_RETURNs, and each one can deal independently with a different token type. But that would mean that even if a transaction is valid SLP1, then it still might need to be flagged as do-not-spend because another output had an SLP2 OP_RETURN on it.

Good clarification, the new v2 spec would have to keep SLP lokad id and version fields for general compatibility.
To your second point, it would be valuable to come up with a test plan for checking all of the existing wallet implementations to see how they handle SLPX type transactions.
Based on the current implementations we have it seems like SLP1 would never be able to safely support multi-token sends and this could only be supported with a new token specification.  So, in this case, wouldn't the safest path forward to have the new token version's metadata starting on vout=0, since all existing wallets look there first and don't look anywhere else.
The new token version could have the possibility of having additional metadata on vout > 0, but keeping in mind none of the additional metadata could be a SLP1.  It's definitely a good thing to bring up, and now I will be keeping in mind moving forward.

wouldn't the safest path forward to have the new token version's metadata starting on vout=0, since all existing wallets look there first and don't look anywhere else.

Seems like the best path forward to me.
Food for thought:
I'm a huge fan of the memo.cash protocol. It's a damn shame it doesn't comply with the Lokad spec, but putting that aside, the structure of the protocol is extremely expressive. I think that structure could provide inspiration for incorporating some of the ideas on this wish list, and essentially passing commands to SLPDB or other token validation software.
https://memo.cash/protocol

Based on the current implementations we have it seems like SLP1 would never be able to safely support multi-token sends and this could only be supported with a new token specification. So, in this case, wouldn't the safest path forward to have the new token version's metadata starting on vout=0, since all existing wallets look there first and don't look anywhere else.

Could be, but we can easily amend SLP design requirements for wallets that they need to scan all outputs. (This isn't a change to SLPv1 spec, which would still require its message to live on vout 1)
Note that if SLP2 doesn't require its OP_RETURN to live on vout 0, then SLP1 indeed could participate in a multitoken send with an SLP2 token, just not with other SLP1 tokens. Also you could do SLP2-SLP2 multitoken transaction, or SLP2-wormhole multitoken, or whatever.

Could be, but we can easily amend SLP design requirements for wallets that they need to scan all outputs. (This isn't a change to SLPv1 spec, which would still require its message to live on output 0) Given how far away SLP2 is from existing if we did this now then it would give ample time for wallets to conform to this requirement.

I was going to write a rebuttal type response, but then I realized that there is no way to enforce a wallet to respect multi-send on a consensus level regardless of the specification rules.  Yes, I agree. we should add this v1 wallet implementation requirement to respect multiple OP_RETURNs.

Food for thought:
I'm a huge fan of the memo.cash protocol. It's a damn shame it doesn't comply with the Lokad spec, but putting that aside, the structure of the protocol is extremely expressive. I think that structure could provide inspiration for incorporating some of the ideas on this wish list, and essentially passing commands to SLPDB or other token validation software.

As long as the lokad and version bytes line up with the existing parsers, then there probably isn't a reason we couldn't change it up a bit for the rest of the fields in v2.

I think it would be a good idea to extend a minting function within the GENESIS tx. It could default to the current functionality for backward compatibility, but then allow anyone to define how toxens can be minted. I'm building a proposal that would require an anyone can mint capability. christroutner
above seemed to need this capability as well with his use case.
I can further elaborate on my use case if interested

And by this I mean that you could have a script which dictates how MINT can be called.

Unless I'm missing something in your specific use case, I think its already possible in v1.  There are a couple of us working on some minting smart contracts implementations.
https://github.com/simpleledgerinc/slp-mint-contracts

Nice

I should have elaborated that I'm thinking of a generic minting function which would make the architecture smoother for NFT. It should be possible to use a script instead of a baton to define who can mint to achieve an anyone-can-mint use case.
I've written a high level view of the project I'm building - I really would appreciate initial feedback especially if there is a better way, this could be a waste of time but it's something I think would have value in the ecosystem.
https://github.com/robert-muncaster/prptoken

Another potential enhancement. Mark brought up the fact that it can be difficult to verify your SPICE because anyone can create a SPICE token with identical parameters (name, url, ...). This is especially bad in the neighbourhood for stablecoins (quick look for USDH on simpleledger.at and I see tons of USDH and USDT, etc... this could really really make scams mega easy.
I believe in badger wallet the developers filter tokens but that doesn't really scale, nor is it transfereable.
What about extending the hierarchy proposed for NFT1 a bit more rigidly to have authoritative tokens the same way that we have signing authorities (root CAs)? Not sure how governance / auditability would work for those, but it's forseeable that this concept must emerge at some point. This should be an easy enough update to the spec.
Such a system would create a market for authorities. ticker symbols could still be reused but differentiated based on their signer and the authoritator would be responsible for ensuring that there can't be dup tickers under their watch, and consensus rules could be built around this. We could implent a POS system to disincentivize authorities acting bad

You can already become an authority yourself, just set up a website and publish some token ids you trust, no need for fancy specs. Your wallet is likely already such an authority by being selective about which icons to use.

The whole point of this is 'on chain'?
We're trying to evolve and mature a standard. Some guy saying "I have an authoritative list" will not be standardized. Everyone who implements such a site will have different APIs, have potential downtime, different return formats and ultimately make it harder for wallets to integrate and impossible to scale.

I'm proposing evolving a spec for it to scale to mass use

In the BCH dev meeting #18, we discussed the possibility of using the OP_RETURN in a more general-purpose way so that it could encompass multiple protocols, like SLP.
Something to think about for a future protocol change. Make the SLP protocol in a way that is extensible and the OP_RETURN can be used for other things too.
Personally, I like using OP_RETURN to reference data in IPFS. That is a great way to expand the protocol infinitely off-chain.


Dropdown Menu Doesn't Stay Open, Should Open Up, Not Down

When the bottom of the options box extends below the browser window, the options block does not stay open when clicked unless your mouse happens to be hovering over the box's scroll bar. If you click in the middle of the dropdown menu, it just snaps back up immediately, selecting whatever your house happens to have been hovering over.
You can see what I am talking about here: http://what-key-am-i-in.herokuapp.com/ and click on the 'fretBoard' link, then try to change the dropdown showing keys (lower left dropdown menu) with the bottom of your browser window only slightly below where the menu is.
Shouldn't the menu open upwards instead? Thanks!

I know this is a closed issue, but your fix didn't actually fix it for me. It worked fine in IE8+, but not in Chrome or Firefox. I had to add some browser detection and update a few lines in the positionDropdown function:
if (above) {
if (navigator.browserInfo.browser != 'IE' && navigator.browserInfo.browser != 'MSIE')
dropTop = offset.top - dropHeight - 45;
else
dropTop = offset.top - dropHeight;
this.container.addClass("select2-drop-above");
$dropdown.addClass("select2-drop-above");
}

Now that we're on version ~> 4.0.1, have we arrived to a solution for this issue? Should I create a new issue since this appears to be recurring.

I have the same problem on chrome, the dropdown opens above the selector and disappears immediately...

Having the same issue on all browsers when the browser window is shorter than the browser height.

I found the solution to my problem. I set margin-top to 50px on the .select2-container
Removing the margin allowed the dropdown to stay open.


Add support of Symfony 3.0

Q
A

Bug fix?
no

New feature?
no

BC breaks?
no

Deprecations?
no

Tests pass?
yes

Fixed tickets
#84

License
MIT

Doc PR
~

A new inspection was created.

There is no job on Travis performing a build with Symfony 3.

The inspection completed: 26 Issues, 0 Patches

A new inspection was created.

It's done.

Travis test Symfony 3.0 with PHP 5.4. What is the config for testing Symfony 3.0 with PHP 5.5 and greater?

The inspection completed: 26 Issues, 0 Patches

A new inspection was created.

The inspection completed: 26 Issues, 0 Patches

The config of Travis is fixed now.

:+1: LGTM
The Travis CI configuration can be improved but that should better be done in a separate pull request.

Ok, I'm interested by your optimization of the Travis config.

@francoispluchino You can take a look at my changes in #86 (one job is currently failing because of a YAML syntax error that will be fixed by #87).

@xabbuh Thanks!

A new inspection was created.

The inspection completed: 26 Issues, 0 Patches

It's ok for you now?

@kmfk

@francoispluchino Thanks!


Graphql schema generation

This PR adds a sub command to generate for getting schemas in graphql

Codecov Report

Merging #161 into master will decrease coverage by 0.10%.
The diff coverage is 53.33%.

@@            Coverage Diff             @@
##           master     #161      +/-   ##
==========================================
- Coverage   82.23%   82.13%   -0.11%
==========================================
  Files         144      144
  Lines        6385     6380       -5
==========================================
- Hits         5251     5240      -11
- Misses        761      764       +3
- Partials      373      376       +3

Impacted Files
Coverage Δ

pkg/transport/graphql/graphql.go
66.01% <0.00%> (-0.65%)
:arrow_down:

pkg/codec/json/json.go
75.67% <50.00%> (+0.67%)
:arrow_up:

pkg/transport/http/caller.go
75.22% <55.55%> (-2.56%)
:arrow_down:

pkg/transport/http/http.go
33.33% <100.00%> (-24.25%)
:arrow_down:

pkg/transport/http/proxy.go
50.00% <0.00%> (-50.00%)
:arrow_down:


reduce test_dependencies

Also add comments for why we need all these 3 random functions for Windows, and the old Linux syscall interface.

@bors r+

:pushpin: Commit 1ae97809bd30d347f9b976254f49e6000330d69c has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 1ae97809bd30d347f9b976254f49e6000330d69c with merge 4ddbd300e1a9a34c3380cc5c0daaaf83f548c113...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 4ddbd300e1a9a34c3380cc5c0daaaf83f548c113 to master...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 4ddbd300e1a9a34c3380cc5c0daaaf83f548c113 to master...


Change pip to pip3 in build-s3-dist.sh

Is your feature request related to a problem? Please describe.

The README makes it clear that the dependencies for these automations include Python 3.8
However, some people may still have two different versions of Python installed, with pip pointing to Python 2.7.
The build-s3-dist.sh script uses pip and therefore all packages could be installed with Python 2.7 accidentally

Describe the feature you'd like

Force Python 3.x package installation by changing pip to pip3 in build-s3-dist.sh

Thanks for your contribution. We have added your request to our backlog and it will be considered in future releases as needed.

Hi!
We just released v3.2.0 of the solution, and this issue has been fixed.


Python version for new cluster?

How to set python version 3 which ties back to Databricks Cluster Configurations? Unfortunately, there's no documentation for that! Here's what I am trying to achieve:
o Create Azure Datafactory Pipeline which:
a. Copies Data from on-prem to BLOB, a connected Databricks notebook activity which reads from this BLOB and persist the data in DBFS. I cannot specify Python Version = 3 in 'Databricks Notebook' Activity

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a176f27b-f9fc-e0ff-0a48-aa42036051f2
Version Independent ID: d2356b83-3101-4b56-baaf-8bdf31e3bb57
Content: Run a Databricks Notebook with the Databricks Notebook activity in Azure Data Factory
Content Source: articles/data-factory/transform-data-using-databricks-notebook.md
Service: data-factory
GitHub Login: @nabhishek
Microsoft Alias: abnarain

@hiteshtulsani Thanks for the feedback! We are currently investigating and will update you shortly.

@hiteshtulsani I do not believe what you are describing regarding python version is possible at this time.  I do not see a way to pass the 'spark_env_vars' key to the Databricks API through ADF.  Take a look at the "spark_env_vars" here:
https://docs.azuredatabricks.net/api/latest/examples.html#create-a-python-3-cluster
@nabhishek this might be a documentation opportunity as there is no mention of the 'Additional cluster settings' or the 'Advanced' section in the UI:

The environment variable to specify Python 3 is documented, is it possible to pass that to the Databricks API through ADF?:
https://docs.databricks.com/api/latest/clusters.html#clustereditcluster

@hiteshtulsani We currently do not support 'spark_env_vars' using which you would be able to specify '/databricks/python3/bin/python3' while using a job cluster (create new cluster option in ADF). This should be made available around Sep 2018.
For now, please use an Interactive cluster (existing cluster in ADF) with Python3 environment enabled. Even if the interactive cluster is turned off, the notebook activity execution would turn it on, and you can set a TTL (inactivity time before cluster shuts down) in Databricks cluster UI.

Thanks for the reassurance! The workaround to have a cluster created upfront is what we went with eventually. Would keep a tab on Sep 2018 release. Cheers!

@nabhishek This still doesn't seem to be an option or documented anywhere?
Is there a way to set a new job cluster version with Python 3? or is the current work around still using an interactive cluster.

@fusionet24 in principle you should be able to set that via spark environment variables, more concretely, setting PYSPARK_PYTHON to /databricks/python3/bin/python3

@jarandaf  Yes we can do that. Sorry, I forgot to come back and update. If you set up a Python 3 cluster, it should automatically set those Environmental variables in the Linked Service.


Investigate performance issues with dispatch-service

I submitted the BiGG projects again to update the biosimulations-bigg repo, which is tracking what the BiGG simulation runs. Several hours later 8 several runs are still running, 5, simulation failed, and 1 failed to publish to BioSimulations. The logs show a number of issues. See error-log.txt. One of the Redis replicas appeared to die (and is still degraded). Unless this was due to a temporary issue (there do appear to have been some issues connecting to UConn HPC), it seems there may still be performance issues.

Stuck in processing (8):

620d621c9c2803ef8a22a07c
620d621e9c2803ef8a22a07f
620d62399c2803ef8a22a0c1
620d62428dda8ca4122e993d
620d6252362ac03746b1eff9
620d626e8dda8ca4122e99bf
620d6293c904db6986a248f8
620d62edc904db6986a249f6

Failed (5):

620d62459c2803ef8a22a0e5
620d625092c0f14f91cfefd3
620d62a992c0f14f91cff086
620d62ac362ac03746b1f109
620d62c092c0f14f91cff0c2

Failed to publish to BioSimulations (1):

620d62f4c904db6986a24a1d

Errors
Some of the most frequent errors I noticed. The number of occurrences is at the beginning of each bullet. In decreasing order of frequency:

125: Request failed with status code 502 for Patch operation on path. Example https://api.biosimulations.org/runs/620d6232c904db6986a247f4
25: Error: Missing lock for job. Example 620d6264362ac03746b1f05a
20: Request failed with status code 409 for Post operation on path. Example https://api.biosimulations.org/logs/620d62a992c0f14f91cff086 for simulation run 620d62a992c0f14f91cff086
15: Error: Job is not in the active state. delayed. Example 620d628cc904db6986a248f1
12: An error occurred in submitting an HPC job for simulation run. Example '62066a569c2803ef8a229ab7'
10: Request failed with status code 502 for Post operation on path. Example https://api.biosimulations.org/specifications/620d62ec362ac03746b1f1c7
10: Request failed with status code 502 for Post operation on path. Example https://api.biosimulations.org/metadata/620d62f2c904db6986a24a0d
3: Request failed with status code 502 for Post operation on path. Example https://api.biosimulations.org/files/620d620e362ac03746b1ef40 for simulation run 620d620e362ac03746b1ef40
3: Request failed with status code 502 for Post operation on path. Example https://api.biosimulations.org/files/620d62b4362ac03746b1f124

A few things that I am noticing that are different from the example runs

Redis memory usage shoots much higher
Combine API goings down often, causing the retries and memory issues on the dispatch-service
API has a lot of 502s, despite not actually going down. I think this is due to the loadbalancer assuming no response is coming for some of the larger requests of logs etc that may be a bit slow

Plans to address this

[ ] Determine why combine API fails.
[ ] Clean out jobs from Redis as soon as the processing is complete
[ ] Reduce the concurrency of the CPU intensive jobs
[ ] Get the Redis backups connected to bull. Look into deploying redis sentinel
[ ] Restore larger node sizes

@jonrkarr Could we reduce the warnings logged by the simulators/turn them off in the Sbatch script?
It seems like the vast majority of the logs size is coming from this sort of message repeated over and over
BioSimulatorsWarning: \u001b[33mCOMBINE/OMEX archive may be invalid.\r\n
 - The manifest does not include its parent COMBINE/OMEX archive. Manifests should include their parent COMBINE/OMEX archives.\u001b[0m\r\n  warnings.warn(termcolor.colored(message, Colors.warning.value), category)\
 - r\n/usr/local/lib/python3.9/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: \u001b[33mThe SED document is potentially incorrect.\r\n  - Model `model` may be invalid.\r\n    - The model file `iCHOv1_DG44.xml` may be invalid.\r\n
 - In situations where a mathematical expression refers to a compartment, species or parameter, it is necessary to know the units of the object to establish unit consistency. In models where the units of an object have not been declared, libSBML does not yet have the functionality to accurately verify the consistency of the units in mathematical expressions referring to that object. \r\n
 -  The units of the <compartment> 'c' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - If neither the attribute 'units' nor the attribute 'spatialDimensions' on a Compartment object is set, the unit associated with that compartment's size is undefined.\r\n        Reference: L3V1 Section 4.5\r\n
 -  The <compartment> 'c' has no discernable units.\r\n        \r\n      - In situations where a mathematical expression refers to a compartment, species or parameter, it is necessary to know the units of the object to establish unit consistency. In models where the units of an object have not been declared, libSBML does not yet have the functionality to accurately verify the consistency of the units in mathematical expressions referring to that object. \r\n
 - The units of the <compartment> 'x' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n
 - If neither the attribute 'units' nor the attribute 'spatialDimensions' on a Compartment object is set, the unit associated with that compartment's size is undefined.\r\n        Reference: L3V1 Section 4.5\r\n
 -    The <compartment> 'x' has no discernable units.\r\n        \r\n
 -   - In situations where a mathematical expression refers to a compartment, species or parameter, it is necessary to know the units of the object to establish unit consistency. In models where the units of an object have not been declared, libSBML does not yet have the functionality to accurately verify the consistency of the units in mathematical expressions referring to that object. \r\n         The units of the <compartment> 'r' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n
 -    - If neither the attribute 'units' nor the attribute 'spatialDimensions' on a Compartment object is set, the unit associated with that compartment's size is undefined.\r\n        Reference: L3V1 Section 4.5\r\n
 -      The <compartment> 'r' has no discernable units.\r\n        \r\n
 -  - In situations where a mathematical expression refers to a compartment, species or parameter, it is necessary to know the units of the object to establish unit consistency. In models where the units of an object have not been declared, libSBML does not yet have the functionality to accurately verify the consistency of the units in mathematical expressions referring to that object. \r\n         The units of the <compartment> 'm' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n
 -   \r\n      - If neither the attribute 'units' nor the attribute 'spatialDimensions' on a Compartment object is set, the unit associated with that compartment's size is undefined.\r\n        Reference: L3V1 Section 4.5\r\n
 -        The <compartment> 'm' has no discernable units.\r\n        \r\n      - In situations where a mathematical expression refers to a compartment, species or parameter, it is necessary to know the units of the object to establish unit consistency. In models where the units of an object have not been declared, libSBML does not yet have the functionality to accurately verify the consistency of the units in mathematical expressions referring to that object. \r\n
 -   The units of the <compartment> 'mm' cannot be fully checked. Unit consistency reported as either no errors or further unit errors related to this object may not be accurate.\r\n        \r\n      - If neither the attribute 'units' nor the attribute 'spatialDimensions' on a Compartment object is set, the unit associated with that compartment's size is undefined.\r\n        Reference: L3V1 Section 4.5\r\n         The <compartment> 'mm' has no discernable units.\r\n        \r\n
 -  - In situations where a mathematical expression refers to a compartment, species or parameter, it is necessary to know the units of the object to establish unit consistency. In models where the units of an object have not been declared, libSBML does not yet have the functionality to accurately verify the consistency of the units in mathematical expressions referring to that object. \r\n

The logs are largely coming from libSBML. 13mb doesn't seem like a lot. I don't think its unreasonable to support logs of this size.

I reduced the size of logs that simulation tools generate. For flux balance and MASS models, the logs should now be much smaller and more easily read by humans.


On ckks calculation

In the same ckks scheme, it seems that the larger the floating-point number is, the less accurate the result of homomorphic encryption is.
For the same polynomial, the result calculated with a smaller floating-point number such as 56.32 is very close to the real value, but if a larger floating-point number such as 14556132.156, the difference between the calculated result and the real value will always be more than 1000 (or even greater). Is this normal?

For a given polynomial p = a_0+a_1x+a_2x^2... the variance of the error of the underlying plaintext m + e after its homomorphic evaluation will be affected by the variance of the coefficients a_i.
For example, take p = a_0 + a_1x + a_2x^2, with x = m+e, x^2 = m'+e', then the final error will be a_1e + a_2e'. Hence larger a_i will necessarily imply a larger variance in the error, and therefore a lower resulting precision.
Also check that you do not get a plaintext overflow, which will happen if m gets larger (at any point in the computation) than your ciphertext modulus.

For a given polynomial p = a_0+a_1x+a_2x^2... the variance of the error of the underlying plaintext m + e after its homomorphic evaluation will be affected by the variance of the coefficients a_i.
For example, take p = a_0 + a_1x + a_2x^2, with x = m+e, x^2 = m'+e', then the final error will be a_1_e + a_2_e'. Hence larger a_i will necessarily imply a larger variance in the error, and therefore a lower resulting precision.
Also check that you do not get a plaintext overflow, which will happen if m gets larger (at any point in the computation) than your ciphertext modulus.

What if x is very large? For example, P = 0.4 + 1.2 * x + 1.5 * x ^ 2 +... (x = 156351521.662).
Is it the same problem?

For a given polynomial p = a_0+a_1x+a_2x^2... the variance of the error of the underlying plaintext m + e after its homomorphic evaluation will be affected by the variance of the coefficients a_i.
For example, take p = a_0 + a_1x + a_2x^2, with x = m+e, x^2 = m'+e', then the final error will be a_1_e + a_2_e'. Hence larger a_i will necessarily imply a larger variance in the error, and therefore a lower resulting precision.
Also check that you do not get a plaintext overflow, which will happen if m gets larger (at any point in the computation) than your ciphertext modulus.

What if x is very large? For example, P = 0.4 + 1.2 * x + 1.5 * x ^ 2 +... (x = 156351521.662).
Is it the same problem?

x is the ciphertext encrypted by seal

As @Pro7ech said, the noise growth speed in CKKS (also in BFV) depends on the magnitude of the encrypted message.

If you want a more precise results, you can use a larger scaling factor (e.g., ~ 2*80)

But as a side effect, you have to keep at least two modulus before the decryption.

As @Pro7ech said, the noise growth speed in CKKS (also in BFV) depends on the magnitude of the encrypted message.

If you want a more precise results, you can use a larger scaling factor (e.g., ~ 2*80)

But as a side effect, you have to keep at least two modulus before the decryption.

As @Pro7ech said, the noise growth speed in CKKS (also in BFV) depends on the magnitude of the encrypted message.

If you want a more precise results, you can use a larger scaling factor (e.g., ~ 2**80)

But as a side effect, you have to keep at least two modulus before the decryption.

OK thanks

As @Pro7ech said, the noise growth speed in CKKS (also in BFV) depends on the magnitude of the encrypted message.

If you want a more precise results, you can use a larger scaling factor (e.g., ~ 2**80)

But as a side effect, you have to keep at least two modulus before the decryption.

OK thanks


added extra metrics for scheduler threads

Scope & Purpose
Added scheduler thread creation/destruction metrics:

arangodb_scheduler_threads_started: Number of scheduler threads started

arangodb_scheduler_threads_stopped: Number of scheduler threads stopped

[ ] :hankey: Bugfix

[x] :pizza: New feature

[ ] :hammer: Refactoring

[x] :book: CHANGELOG entry made

[x] :muscle: The behavior in this PR was manually tested

[ ] :computer: The behavior change can be verified via automatic tests

Backports:

[ ] No backports required
[x] Backports required for: 3.7

Testing & Verification

[x] This change is a trivial rework / code cleanup without any test coverage.

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/11866/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/11871/

Tests blue


Allow importing for nodes from a CSV file

We will need to define the format for this.

Could be related to https://github.com/chairemobilite/transition/issues/112


Karate Framework's karate-apache does not have release 1.0.

Hi there,
I use karate as part of tests. While trying to upgrade to 1.*, I ran into issue with
Could not find artifact com.intuit.karate:karate-apache:jar:1.0.0

@qcloop  you only need one dependency from 1.0.0 which will be karate-core singe dependency
please read the 1.0 upgrade guide for more details


date invalid error msg inaccurate

wait but the inputed date is not in yyyy-MM-dd format, bc the month is wrong

thats fair

close liao


missing dependency for symfony/debug cause below error when migration taken place

Fatal error: Uncaught Error: Class 'Symfony\Component\Debug\Exception\FatalThrowableError' not found in /usr/local/zendphp7/var/apps/http/maintenance.zenddev.ftr.com/80/1.1.4_2334/vendor/symfony/console/Application.php:134
Stack trace:
#0 /usr/local/zendphp7/var/apps/http/maintenance.zenddev.ftr.com/80/1.1.4_2334/vendor/zendframework/zend-expressive-migration/bin/expressive-migration(20): Symfony\Component\Console\Application->run()
#1 {main}
thrown in /usr/local/zendphp7/var/apps/http/maintenance.zenddev.ftr.com/80/1.1.4_2334/vendor/symfony/console/Application.php on line 134
when checked in vendor/symfony debug was missing. It was exist there before running " ./vendor/bin/expressive-migration migrate". got removed after running migrate command.

This repository has been closed and moved to mezzio/mezzio-migration; a new issue has been opened at https://github.com/mezzio/mezzio-migration/issues/1.


Thank you, @JensRantil.
Please check out the instructions in CONTRIBUTING.md to see how to update github-accessors.go. (Basically, go generate ./....) Then, after you push the new changes, the Travis CI build should pass.


#700: refactored file names as per Flutter's convention

Thanks for your PR, but we already have someone from our team working on it! I am sorry to close this in favor of #706.


Update google-api-services-bigquery to v2-rev20200625-1.30.10

Updates com.google.apis:google-api-services-bigquery from v2-rev20190917-1.30.3 to v2-rev20200625-1.30.10.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.apis", artifactId = "google-api-services-bigquery" } ]

labels: library-update

needs to match https://github.com/spotify/scio/blob/v0.9.2/build.sbt#L63


solana integ bugfix

📝 Description
Solana fixing integ, one integ im not sure about the add of prepareTransaction on global though
❓ Context

Impacted projects: live-common
Linked resource(s): ``

✅ Checklist

[ ] Test coverage
[ ] Atomic delivery
[ ] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Integ tests are running : https://github.com/LedgerHQ/ledger-live/actions/runs/3289848772


docs(releases): hide no longer supported versions

Replaces #184.

Armory supports only the most recent 3 minor versions
Release notes href path doesn't change

Thanks @kevinawoo  - this is really cool!!


Per-step gate negative offset

Hi,
I'd love to be able to do a negative gate offset on a step. Currently you can only go between 0 and 87. 5%, but you can't make the step trigger earlier. The screen also puts the 0% mark in the middle, so I assumed that you can go to negative values.
Many thanks!

Hi, I have a PR with negative offsets implemented and I need some help testing it, would you mind trying my changes out?
https://github.com/westlicht/performer/pull/234

Hey there,
Sure! Thanks for asking
---------------Music: http://www.bachelard.bandcamp.com
On Monday, November 30, 2020, 8:13:34 p.m. EST, vafu<EMAIL_ADDRESS>wrote:

Hi, I have a PR with negative offsets implemented and I need some help testing it, would you mind trying my changes out?
#234
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hey @vafu - your latest version has a glitch. In the Step mode/page, normally, you can only turn on/off a step gate when you're on the Gate menu/page (1st tab, 1st item), and you need to press on the step + encoder when you're on any other  menu (Retrig, Note, etc). But with your latest version, you can activate gate on/off from any page. Not sure if that's what you want - I personally prefer to be able to alter the gate sequence only in the Gate menu, so it's harder to accidentally alter the gate pattern while I'm trying to just change note values or gate lengths, etc.
I reloaded the official 0.1.39 firmware to confirm, because that's what I remember, and confirm that's the case.

@hotelbachelard yes, thanks! I've added this as my own preference but I accidentally added these changes to the firmware update, sorry about that, I'm going to remove that asap!

Hey @vafu - I found a lil bug in your 1.39: the Gate Probability bar doesn't show up in your version. :(

it's there in 1.40 (and the official 1.39)


main-vertical/horizontal behaves unexpectedly

Bug description
Whenever I start a project with the layout main-vertical or main-horizontal, I get the main pane about 80% instead of the the size it should have (50%). When I run select-layout main-vertical I get the appropriate sizing. But this doesn't happen when the project starts, rather with the wrong sizing.
To Reproduce
name: project
root: ~/
windows:
    - null:
        layout: main-vertical
        panes:
        -
        -
        -
        -
    - null:
        layout: main-horizontal
        panes:
        -
        -
        -

This is an example of how to reproduce it. What will happen is that the main pane will be significantly larger than it should be.
And this works for all the windows in the session btw, not just the first one
Environment

tmuxinator Version: 2.0.1
tmux Version: 3.0a
Ruby Version: ruby 2.7.1p83
OS: Fedora

This isn't an issue when using even-vertical or tiled. They behave perfectly fine

I should mention that I don’t have any commands in my .tmux.conf that control the main pane’s width or height meaning that this:
set -g main-pane-width width
set -g main-pane-height height

Isn’t in my tmux conf

This issue seems similar to #568 and #651.
Have a look at my workaround.


tasks not being run during a job

 Issue by bacongobbler
2017-07-06 23:40:00

So I just got my first job running and completed. Woo! 🎉
Unfortunately, it looks like the tasks that were requested in acid.js weren't actually run. The job was considered successful as soon as it checked out the source code via the vcs-sidecar image.
For reference, I was following the user guide, tweaking the example acid.js file a bit to accommodate a Go project.
events.push = function(e) {
  // A slightly better log message.
  console.log("===> Building " + e.repo.cloneURL + " " + e.commit);

  // Create a new job
  var node = new Job("go-tester")

  node.image = "golang:1.8.1"

  // Now we want it to run these commands in order:
  node.tasks = [
    "export GOPATH=/src:$GOPATH",
    "cd /src",
    "make bootstrap",
    "make test"
  ]

  // We're done configuring, so we run the job
  node.run()
}

What I Expected to Happen
I expected the commands requested in the "tasks" field to be run to properly test my Go project.
What Really happened
acid spun up a vcs-sidecar container to fetch the source code, succeeded, then ran /hook/main.sh in the pod (which exited 0), then returned a success message on github.
My guess is that /hook/main.sh wasn't actually hooked up to the tasks requested according to https://github.com/deis/acid/blob/27f698d9b4afa831c1dab7ce74a099a2abc9089e/js/run.js#L108-L114, so it sounds like this is something that still needs to be implemented. :)

Comment by bacongobbler
2017-07-06 23:46:42

Indeed, seems like the tasks aren't getting added to main.sh. I just created a new pod using the dumped output of kubectl get po go-tester-abc123... and found that main.sh was empty:
><> k exec go-tester cat /hook/main.sh

Comment by bacongobbler
2017-07-06 23:50:19

the config map deployed by acid also seems to confirm this, so it appears that this would be during the time when the engine writes out the tasks to the config map:
><> k get cm go-tester-1499383405196-e10d89c5 -o yaml
apiVersion: v1
data:
  main.sh: ""
kind: ConfigMap
metadata:
  creationTimestamp: 2017-07-06T23:23:24Z
  labels:
    heritage: Quokka
  name: go-tester-1499383405196-e10d89c5
  namespace: default
  resourceVersion: "6710"
  selfLink: /api/v1/namespaces/default/configmaps/go-tester-1499383405196-e10d89c5
  uid: 1bd8cba3-62a2-11e7-9c43-000d3a19aed0


Cropping polygons are sometimes blurry near edge

Hello! I'm using TiledImage.setCroppingPolygons to crop an overlay that appears on top of a main image, and I'm seeing some weird behavior. As you zoom, the edge sometimes gets blurry and pulls away from the polygon edge a little bit (maybe 10-20px of the main image), but then will snap back as you zoom in. If the viewer is rotated at all, the cropped overlay can jump several hundred pixels, typically up and to the left relative to the unrotated main image.
These seem very related but are quite confusing; if it was just the offset I'd think we were computing the overlay position of the polygons incorrectly but the blurred edge issue (which seems to happen at the same zoom level but rotation 0) is a whole different story. Based on this condition and TODO I'm guessing the issue has something to do with the "sketch canvas".
Any help I could get with this issue would be greatly appreciated!

Any chance you can link to an example (codepen or similar) that reproduces the issue?

Difficult to get an env set up but here's a quick video of it:
https://user-images.githubusercontent.com/299163/223173234-7debf539-ba6c-4129-8e4e-2a298495ad53.mov

And here is it jumping when the image is rotated:
https://user-images.githubusercontent.com/299163/223174271-d9743f2d-0209-4b76-a29d-85496ab4ce5c.mov

Thanks for the videos. Can you provide some more detail about the overlay layer(s) - both the red/transparent layer, and the polygon? Are you using one of the overlay plugins?

The polygon is actually being drawn by a different library on a different canvas (something we'd like to fix in the future but for now it shouldn't be relevant). The overlays are just their own DZIs being added as tiled images with opacity and fitBounds set.

I'm happy to help with a fix here if someone can give me some guidance on what's going on! I sent a message in the Discord #help channel as well if it's easier to discuss there.

If it's any help, commenting out this entire block of code seems to fix the problem:

Though obviously that's probably breaking something else less obvious to me. Pretty difficult to isolate where things are going wrong because nearly every branch of that function references sketchScale and sketchTranslate.

You can try setting smoothTileEdgesMinZoom to Infinity to disable that block. Does it generate seams in your tiled image(s) if you do so?

Oh that's quite convenient. I'm unable to see any seams; in what scenario would they be visible?

I'm not entirely sure. It seems from the comment in the code you included that, for some tile sources at least, high zoom levels can lead to visible seams between tiles.
Coincidentally, I've been working on a PR (https://github.com/openseadragon/openseadragon/pull/2310) that addresses a lot of the problems related to visual tiling artifacts by moving towards WebGL based rendering. You may find that to be of interest!

smoothTileEdgesMinZoom was introduced with https://github.com/openseadragon/openseadragon/pull/764 which fixed https://github.com/openseadragon/openseadragon/issues/755. It only affects when you are zoomed in more than full resolution, and you only really see the effects when you're zoomed in a lot past full resolution (which generally is never the case).
I think disabling it in this scenario is a fine workaround, but of course hopefully someone can look into fixing this bug as well!

To fix the blurring/jitter during zoom, hard-coding sketchScale=1 instead of the computed value `` does the trick:
        if (lastDrawn.length > 1 &&
            imageZoom > tiledImage.smoothTileEdgesMinZoom &&
            !tiledImage.iOSDevice &&
            tiledImage.getRotation(true) % 360 === 0 && // TODO: support tile edge smoothing with tiled image rotation.
            $.supportsCanvas && this.viewer.useCanvas) {
            // When zoomed in a lot (>100%) the tile edges are visible.
            // So we have to composite them at ~100% and scale them up together.
            // Note: Disabled on iOS devices per default as it causes a native crash
            useSketch = true;
            // sketchScale = tile.getScaleForEdgeSmoothing();                                        // Instead of this
            sketchScale = 1;                                                                                // Just set the scale to 1
            sketchTranslate = tile.getTranslationForEdgeSmoothing(sketchScale,
                this.getCanvasSize(false),
                this.getCanvasSize(true));
        }

To fix the mis-positioning when rotated, adding the lines highlighted below works:
        if (tiledImage._croppingPolygons) {
            var self = this;
            this.saveContext(useSketch);
            try {
                var polygons = tiledImage._croppingPolygons.map(function (polygon) {
                    return polygon.map(function (coord) {
                        var point = tiledImage
                            .imageToViewportCoordinates(coord.x, coord.y, true)
                            .rotate(-tiledImage.getRotation(true), tiledImage._getRotationPoint(true));
                        var clipPoint = self.viewportCoordToDrawerCoord(point);
                        if (sketchScale) {
                            clipPoint = clipPoint.times(sketchScale);
                        }
                        if (sketchTranslate) {                                                   // NEW LINES
                            clipPoint = clipPoint.plus(sketchTranslate);         // NEW LINES
                        }                                                                                // NEW LINES
                        return clipPoint;
                    });
                });
                this.clipWithPolygons(polygons, useSketch);
            }

Note that this entire snippet is copied from my ongoing implementation that separates drawing from positioning etc, and the surrounding code may have been modified from current OSD core code (and thus to be applied to current OSD it would have to be modified as well).
Something I noticed while testing is that if smoothTileEdgesMinZoom is set to a value below 1 (0.1 demonstrates this nicely), the sketchCanvas path gets very messed up and truncates zoomed-out images, suggesting the entire code path either needs some guards or needs to be re-thought.
However, when fixing the issue with the changes above (which avoid calculating a scale factor for the sketchCanvas), even at extreme zoom levels I do not see tiling issues... has the fix that introduced this code been superseded by subsequent fixes? Or maybe by improvements in canvas implementations by supported browsers? Even without these changes, I haven't been able to reproduce the original issue with tiling even at extreme zoom levels, with the fix using sketchCanvas disabled. I am not sure what I should to expect to be broken by removing the calculation of sketchScale from the equation.

@pearcetm Interesting! It certainly would be cool if we didn't need the edge smoothing aspect of sketchCanvas anymore. Note that we still need sketchCanvas for semi transparent images regardless.
As for reproducing the issue, the top comment in https://github.com/openseadragon/openseadragon/issues/755 has a screenshot at 800% that shows it. Maybe try something like that (if you want to verify the repro or lack thereof).

@pearcetm I suppose the blurring us because the polygon is being applied in the sketch canvas, so when it's blown up to the main canvas, it becomes blurry? If that's the case, the solution would be to apply the polygon during the transfer to the main canvas. I'm not sure how involved that change would be.
Even without that fix, fixing all of the other buggy behavior seems worthwhile! Do you want to make a PR with that?

the solution would be to apply the polygon during the transfer to the main canvas. I'm not sure how involved that change would be.

Yes, that's exactly the problem. The refactoring needed to address it is not entirely trivial, since tiles are composited onto the main canvas from the (scaled) sketch canvas individually at the moment. Applying cropping during transfer would seem to require adding an intermediate canvas scaled to match the main canvas, which the sketch would need to be drawn onto, cropped, and then drawn to the main canvas. This would double the number of drawing operations and require an extra canvas. Doable, though with a performance cost.
A PR that addresses at least the translation-based bug has been submitted: https://github.com/openseadragon/openseadragon/pull/2316

#2316 fixed the translation issue but not the blur. I'll reopen this in case someone wants to tackle the blur. That said, it sounds like @maxbogue doesn't need it at the moment.


Provide promises interface

Hi,
I've read #929  -- that discussion happened a while ago, and now two things have changed:

We have native promises in node
We have await/async -- a lot more people now want to use promises

So... if anything, I think this would be a good time to release a native promise interface for this wonderful library!
Thanks for listening :D

Makes sense for sure! It's on my list, but if someone is willing to put together all the changes, I can take a look and even accept! I'm not trying to be mean by closing your issue, but we have #1687 as the Promises support tracking issue :)

In the interim you can use the wrapper https://www.npmjs.com/package/promise-mysql

I think you probably mean https://github.com/sidorares/node-mysql2 - the promise-mysql wrapper forces bluebird and doesn't allow for native promises to be used ;)

Yea, there are a few to choose from. Whichever works best for you :)

@eslachance I hope you understand that bluebird out performs native promises, while also providing features not available yet in native promises. ;)
I'm glad to see this is being considered though, would really like to see promises directly from this module.


Unable to sign up / login

When trying to login or signup i get the error:
Error: Cannot find module 'fibers'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.renderComponentToStringWithAsyncState (/Users/freeslugs/Desktop/express-passport-app/node_modules/react-async/index.js:73:17)
    at module.exports (/Users/freeslugs/Desktop/express-passport-app/helpers/react/render-markup-to-string.js:19:16)
    at Stream._generator (/Users/freeslugs/Desktop/express-passport-app/node_modules/highland/lib/index.js:3671:15)
    at Stream._runGenerator (/Users/freeslugs/Desktop/express-passport-app/node_modules/highland/lib/index.js:870:10)
    at Stream.resume (/Users/freeslugs/Desktop/express-passport-app/node_modules/highland/lib/index.js:735:22)
    at Stream._checkBackPressure (/Users/freeslugs/Desktop/express-passport-app/node_modules/highland/lib/index.js:637:17)

I tried installing fibers, npm install fibers but that gives an error
and npm install -g fibers succeeds, but I still get the fibers error.

Having the same issue

Which node version are you guys running?

i believe v0.12.2

I haven't upgraded/tested this on 0.12 I'm afraid :( 0.10.x should work though.


[Dataflow Streaming Engine] Turn on --useWindmillIsolatedChannels and --useSeparateWindmillHeartbeatStreams by default

Turn on --useWindmillIsolatedChannels and --useSeparateWindmillHeartbeatStreams by default on streaming engine
useWindmillIsolatedChannels: Each windmill grpc stream will use a separate
underlying HTTP2 connection
useSeparateWindmillHeartbeatStreams: Separate windmill GetData streams
will be used for heartbeats and key data requests
If required the features can be turned off by passing --useWindmillIsolatedChannels=false and --useSeparateWindmillHeartbeatStreams=false

R: @scwhittle

Pending ongoing discussions internally on how to deploy

Closing as this is being done with new job setting path.


How to increase density of vehicles in an environment?

I've made an environment like highway-v0, which vehicle's action space is continuous, and it tries to reach a goal while avoiding a crash. Here's an episode of a learned agent with the SAC model.

As the density of vehicles in the environment is low, the agent has not a difficult job avoiding them(and it seems it is the IDM vehicle which is avoiding the agent?). I tried to make it harder for the agent by increasing the number of vehicles, but the density of vehicles around remains the same. How can I make it harder, like the animation in the README file from the highway-v0 environment?

There has been a changed in the repartition of vehicles, I switched it back to something closer to what it used to be. You can still control the density by changing the "initial_spacing" environment config

Nice environment, by the way! :+1:

Oh, and I do not think that other vehicles are trying to avoid the ego-vehicle (unless you set the POLITENESS parameter, but it is 0 by default). However, the 3rd vehicle may be trying to avoid the landmark (I can't remember how we handled it, but I think it is considered as a fixed object rather than ignored, or was it only for obstacles?). For the two first I don't really know, 2nd one might change lane if it started on the same as 1st, but I can't really tell here. MOBIL can sometimes be quite unstable at start, and needs a few seconds to reach an equilibrium.

However, the 3rd vehicle may be trying to avoid the landmark (I can't remember how we handled it, but I think it is considered as a fixed object rather than ignored, or was it only for obstacles?).

Yes, they try to avoid the landmark, and the strange thing is sometimes IDM vehicles literally stop before it. See this for example(The ego vehicle's training is incomplete)

Such behavior is a blocker to an agent's exploration.

And when IDM's stop before the landmark, we have a crash :joy:

But when they make maneuvers around the landmark, the agent reacts by slowing down:

I've seen this behaviour before: once it sees an obstacle, the IDM model starts braking, and this causes the MOBIL model to consider a lane change.

If a lane change is possible (it would not cut-in in front of another vehicle), a lane change is triggered and the vehicle avoids the obstacle/landmark
Else (would cut-in), the vehicle cannot change lane and can only brake and stop. Once it is stopped at the obstacle, the MOBIL now recommends a lane change, but IDM still outputs an acceleration of 0 (since the obstacle is close), so the vehicle is stuck.


Update package.json

npm package update

I will update deps it regularly, this job does not require pr, and I hope you can contribute more meaningful pr, thanks.


feat: Change Container image to Ubuntu

Description
Changed the base image to ubuntu, instead of node with Debian.
Instead of running a Node+Debian image and installing the .NET Core, I used a .NET Core image and installed the NodeJS package.
The base image size is 400Mb smaller.

Task Item
#minor

Docker build is failing at when it tries to start. Cannot find a module.

I'll try to merge with the orchestrator branch,

Created a new PR #4516 based on Main Branch, because of too many changes from tachau/orchestrator branch.
I wasn't able to identify from where was the issues comming.


Issue in React-vizgrammar 0.7.25

Description:

I have two bar charts with different chart config. The chart config of both are given below.
    this.ChartConfig = {
        x: "username",
        charts: [
            {
                type: "bar",
                y: "duration",
                color: "sessionId",
                colorScale: ["#00e600"],
                orientation: "left",
            }
        ],
        yAxisLabel: ' Duration (s)',
        xAxisLabel: 'Username',
        maxLength: 10,
        legend: false,
        append: false,
    };

The above config is to display the session with highest duration followed by all the sessions of that particular user and the next session with highest duration. It is Bar Chart with Color Categorization.
    this.ChartConfig = {
        x: "username",
        charts: [
            {
                type: "bar",
                y: "duration",
                fill: "#00e600",
                mode: "stacked",
                orientation: "left",
            }
        ],
        yAxisLabel: ' Duration (s)',
        xAxisLabel: 'Username',
        maxLength: 10,
        legend: false,
        append: false,
    };

The above chart config displays users with average duration. It is Horizontal Bar Chart.
Both configs have common issues like x axis labels cutoff and tip cutoff where the first config has an additional issue in sorting values with respective to the duration. The following images illustrate the issues. These are relevant to version 0.7.23.

I get the following error in the console.
bundle.js:formatted:118148 TypeError: Cannot read property 'x' of undefined
at eval (eval at  (bundle.js:formatted:47639), :1:174888)
at eval (eval at  (bundle.js:formatted:47639), :6:799501)
at Array.reduce ()
at Object.getBaseProps (eval at  (bundle.js:formatted:47639), :6:799168)
at Function.C [as getBaseProps] (eval at  (bundle.js:formatted:47639), :6:226576)
at u.value (eval at  (bundle.js:formatted:47639), :6:291026)
at u.value (eval at  (bundle.js:formatted:47639), :6:290499)
at u.value (eval at  (bundle.js:formatted:47639), :6:289626)
at updateClassInstance (bundle.js:formatted:116607)
at beginWork (bundle.js:formatted:117156)
Suggested Labels:

Suggested Assignees:

@CharukaK
Affected Product Version:
React-vizgrammar 0.7.25
OS, DB, other environment details and versions:
Steps to reproduce:
X axis labels cutoff and tip cutoff should be solved in both configs and the Bar Chart  with Color Categorization should sort the values of duration(Y-axis) in descending order.
Related Issues:

Issue occurs in line https://github.com/wso2/react-vizgrammar/blob/056d29c17efc220690db19aaa834c094ddfe5cae/src/components/ChartContainer.jsx#L63

Axis ticks trim as expected in 0.7.25.

Can you check the config https://stackblitz.com/edit/react-vizgrammar-time-bar-qaqwj7

This issue is only for an empty data set. @CharukaK could we do a validation on this at the line pointed by Sajith(@this)?


[stable/hazelcast] bump to hazelcast 3.12 and adds YAML configuration support

Signed-off-by: Mesut Celik<EMAIL_ADDRESS>
What this PR does / why we need it:

bump hazelcast version to 3.12
add YAML support

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] title of the PR contains starts with chart name e.g. [stable/chart]

cc: @davidkarlsen @leszko

@leszko Should this chart rather be deprecated and eventually removed *) - and the efforts put into https://github.com/hazelcast/charts/?
*) Deprecating charts at https://github.com/helm/helm/blob/master/docs/charts.md

@davidkarlsen technically yes, but there is also the marketing side of this. Meaning that we're still in the official repo, so that a user could install hazelcast without needing to add hazelcast helm repo.
What are the plans for other similar cases, I checked e.g. redis, they're also in both their own repo and in the official one. Any comments on that?

/approve

/lgtm

closing this one... will send another one...


On Windows the path is not correctly updated after saving

after save:

how to fix it ?

Could you try using forward slashes in the settings e.g. C:/Users/user/nuclei-templates instead of C:\Users\user\nuclei-templates?

Update: I have actually implemented a fix in the associated PR, could you maybe give it a try to confirm it works as expected?

Bug still exists

更新：我实际上已经在相关 PR 中实施了一个修复程序，您可以尝试确认它按预期工作吗？

Bug still exists


WAV files with 32 bits per file don't work with sf::Music when 16 bits per file WAV files do.

Here are two example files:

32 bits per file example
16 bits per file example

The easiest way to test these is by replacing the orchestral.ogg file with these and then run the sound example.
The two sample files were generated using libsndfile based on an original WAV file that I have. If you have any more questions then please let me know.

This issue was discovered while looking into: https://github.com/LaurentGomila/SFML/issues/541

Thanks for the report, I'll have a look.

Thankyou for looking so quickly! I meant to say 32 bits per sample but obviously you worked out what I meant.
SFML is awesome BTW. Nice work on this library. If you need testing help then just let me know.

The fix is in #835.

You rock @LaurentGomila.


macOS Installation Script issue with virtualenv

Hello Yogesh,
while using the macOS Installation Script "mac_aptInstall-macOS-v21.sh" I am getting an error: "The folder in Line 118 does not exist" and mac_apt won't install properly. It seems to be an issue dealing with virtualenv. Changing line 112 from "virtualenv --python python3 env &> /dev/null" to "python3 -m venv env &> /dev/null" did solve this problem. I am using the latest macOS 11.6, with Python 3.7.0 and latest hombrew updates. Maybe I am not the only one ;-)
Kind Regards
Stefan
my4n6

I will have to check this and confirm the behaviour. Thanks for reporting.

I can't seem to reproduce it, nor have I heard about this from others who've used the script. The script installs virtualenv on line 92, so there should not be a problem. There is a newer version of the script that logs to the /tmp folder. Try that (to debug), and reopen the issue if you think the bug persists.
New install script is here:
https://drive.google.com/uc?id=1dRoN58J7d6EdTZ4YISCWQ_ZCuA5R-0c4&export=download


ClassNotFoundException

Getting this crash on server startup:
https://gist.github.com/Time6628/68f68d3e61c1a8d5249d656adb5cdd3b

Numina server side crash. Really should have tested that.

Any ETA on when this will be fixed?

Not really. Looking at it now. As soon as I figure out the issue I'll upload a fixed version.

Fixed version of Numina and new MPS to go with it should be up in about an hour or so.

I'll test it out when I get a chance, thanks. :D

Another fix will be up in about an hour
On Tue, Nov 29, 2016 at 7:53 AM Time6628<EMAIL_ADDRESS>wrote:

I'll test it out when I get a chance, thanks. :D
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MachineMuse/Numina/issues/20#issuecomment-263562633,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABCLz9d4gZ2sISyoNtCJkSFyWKpLvfTZks5rDCBQgaJpZM4K9Ub1
.

Works. Thanks for fixing!

I just got this exact same error on the 1.10.2 alpha 001 build, both server side and client side.
crash-2017-03-11_11.41.11-client.txt
crash-2017-03-11_11.39.34-server.txt

The 1.10.2 version of Numina is in the MPS Alpha jar (numina{0.12.2-001} [numina] (ModularPowersuits-0.12.2-001.jar) ). I may end up just merging the code, I don't know yet.  Oddly enough, I've been running the mod for about 4 days and haven't encountered that error, even in multiplayer. I did just try it on a dedicated server from my dev environment, that error does not show there either.

I installed using Curse, it auto installed Numina too. I'll try again
without Numina.
On Sat, Mar 11, 2017 at 12:35 PM, lehjr<EMAIL_ADDRESS>wrote:

The 1.10.2 version of Numina is in the MPS Alpha jar (numina{0.12.2-001}
[numina] (ModularPowersuits-0.12.2-001.jar) ). I may end up just merging
the code, I don't know yet. Oddly enough, I've been running the mod for
about 4 days and haven't encountered that error, even in multiplayer. I did
just try it on a dedicated server from my dev environment, that error does
not show there either.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MachineMuse/Numina/issues/20#issuecomment-285894257,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABpz4AxrucWfePoh6uZUFZMbVOHUliJPks5rkvdwgaJpZM4K9Ub1
.

--
mu'o mi'e .aionys.
.i.e'ucai ko cmima lo pilno be denpa bu .i doi.luk. mi patfu do zo'o
(Come to the Dot Side! Luke, I am your father. :D )

O.o That's something that I did not account for.

I got an "are you sure, powersuits needs this" error, but yup, no errors loading. I don't have time to test any more right now. Gotta go to work.

OK. Thanks. Looks like I'll need to either split these or merge them for the next build.

i removed Numina as a "required library" for the next build.


How i can enable or disable ?

I would like to know how I can enable or disable check update

If you have the plugin installed, it will automatically check for updates on app launch.
Using the SirenAlertType and AndroidUpdateAlertType preferences, you have a little bit of control over how forcefully the updates are presented (either mandatory updates, or optional).

I installed the plugin and it automatically checks when opening the app. I wanted to be able to enable or disable this check.is it possible?

No, the plugin is coded so that it checks for updates immediately when launching the app. There is no JavaScript API exposed to control when the update checking happens.


Made code PEP8 complaint

Pull Request Test Coverage Report for Build 240

21 of 22 (95.45%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.7%) to 98.328%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

nexmo/init.py
21
22
95.45%

Files with Coverage Reduction
New Missed Lines
%

nexmo/init.py
4
98.33%

Totals

Change from base Build 222:
-0.7%

Covered Lines:
294

Relevant Lines:
299

💛  - Coveralls

Pull Request Test Coverage Report for Build 240

21 of 22 (95.45%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.7%) to 98.328%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

nexmo/init.py
21
22
95.45%

Files with Coverage Reduction
New Missed Lines
%

nexmo/init.py
4
98.33%

Totals

Change from base Build 222:
-0.7%

Covered Lines:
294

Relevant Lines:
299

💛  - Coveralls

Pull Request Test Coverage Report for Build 240

21 of 22 (95.45%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.7%) to 98.328%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

nexmo/init.py
21
22
95.45%

Files with Coverage Reduction
New Missed Lines
%

nexmo/init.py
4
98.33%

Totals

Change from base Build 222:
-0.7%

Covered Lines:
294

Relevant Lines:
299

💛  - Coveralls

@judy2k The original code is also failing for python 2. Not sure what's going on. Can you please take a look?

I'm looking in to why it's failing, but I'm afraid I can't accept this PR. Our code is formatted with black, so manual code style edits would be overwritten when we next run it.

Okay, @xadahiya, I re-ran the failing test run, and it passed, so I think it was just a blip. But please also see my comment above when I closed this PR.


[SPARK-25253][PYSPARK] Refactor local connection & auth code

This eliminates some duplication in the code to connect to a server on localhost to talk directly to the jvm.  Also it gives consistent ipv6 and error handling.  Two other incidental changes, that shouldn't matter:

python barrier tasks perform authentication immediately (rather than waiting for the BARRIER_FUNCTION indicator)
for rdd._load_from_socket, the timeout is only increased after authentication.

Test build #95303 has started for PR 22247 at commit c232ec6.

@jiangxb1987 @HyukjinKwon @mengxr

Test build #95303 has finished for PR 22247 at commit c232ec6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95303/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2621/
Test PASSed.

Test build #95354 has started for PR 22247 at commit d07d21d.

Test build #95365 has started for PR 22247 at commit b0c4483.

Test build #95354 has finished for PR 22247 at commit d07d21d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95354/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2642/
Test PASSed.

Test build #95380 has started for PR 22247 at commit 65ed777.

Test build #95365 has finished for PR 22247 at commit b0c4483.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95365/
Test FAILed.

Test build #95380 has finished for PR 22247 at commit 65ed777.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged to master.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95380/
Test PASSed.

@squito Thanks for the refactor!


Update registry image

Coverage increased (+0.02%) to 54.82% when pulling cf0f75e0241b3b5c6488b0faa4a8936b96fa3efe on wy65701436:update-registry-image into 6e6bb80b872ce1cdd1438bbcc7767372c7b1fa68 on vmware:master.

Coverage increased (+0.05%) to 54.853% when pulling b21dc0086b5f1a9da83adf4cea87cad320971687 on wy65701436:update-registry-image into 6e6bb80b872ce1cdd1438bbcc7767372c7b1fa68 on vmware:master.

Coverage increased (+0.06%) to 54.862% when pulling b21dc0086b5f1a9da83adf4cea87cad320971687 on wy65701436:update-registry-image into 6e6bb80b872ce1cdd1438bbcc7767372c7b1fa68 on vmware:master.


Update Active Calls in live map to proper position and not 0,0 unless…

Feature

Update live map render to use gtaMapPosition data to set marker on the map.

Thanks!


[RESOLVED] High ICMP ping response time

Problem started at 08:21:29 on 2023.06.29
Problem name: High ICMP ping response time
Host: HP_iLO
Severity: Warning
Operational data: Value: 763ms
Original problem ID: 31959
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23268&eventid=31959

Problem has been resolved in 7m 0s at 08:28:29 on 2023.06.29
Problem name: High ICMP ping response time
Host: HP_iLO
Severity: Warning
Original problem ID: 31959


Fixed #34034 -- Allow setting HTML attributes on Select widget options.

Trac ticket number

Related to ticket-34034
Branch description
Picks up on @khink's previous work to add the option_attrs parameter for widgets inheriting from ChoiceWidget.
I've updated the ChoiceWidget.__deepcopy__ method and the test for it ChoiceWidgetTest.test_deepcopy and added a test for RadioSelect RadioSelectTest.test_constructor_option_attrs to ensure that option_attrs takes precedence.
Checklist

[x] This PR targets the main branch.
[ ] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.
[ ] I have added or updated relevant docs, including release notes if applicable.
[ ] I have attached screenshots in both light and dark modes for any UI changes.

Hello @marianaasilva! Thank you for this work :star2:
This PR needs some code style fixing (see CI errors). Once you solved those, please unset the relevant ticket flags following these docs so this PR gets added back to the "branches needing review" section of the Django Developer Dahsboard .


Update to remove URLs removed by Intune

Remove the two URLs from the list of endpoints that iOS Device features > Single sign-on app extension > Microsoft Azure AD sends down behind the scenes.
URLs to remove:
login.windows.net
login.usgovcloudapi.net

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


on systemstart Ventura shows me always added to login items

that issue is since Ventura

same here

Same here

same here

same here

+1

+1

same here
MacOS 13.0.1 on MacBookPro 2019

I am not a Swift/macOS programmer, so I won't provide a fixed version, since I don't know if the solution is completely valid. I managed to build from the develop branch after a huge amount of trial and error and finally found a solution applying the following patch:
diff --git a/Clipy/Sources/AppDelegate.swift b/Clipy/Sources/AppDelegate.swift
index af0736f..11ae80c 100644
--- a/Clipy/Sources/AppDelegate.swift
+++ b/Clipy/Sources/AppDelegate.swift
@@ -153,7 +153,7 @@ class AppDelegate: NSObject, NSMenuItemValidation {

     private func toggleAddingToLoginItems(_ isEnable: Bool) {
         let appPath = Bundle.main.bundlePath
-        LoginServiceKit.removeLoginItems(at: appPath)
+        // LoginServiceKit.removeLoginItems(at: appPath)
         guard isEnable else { return }
         LoginServiceKit.addLoginItems(at: appPath)
     }

This solution by @arubdesu worked for me https://github.com/Clipy/Clipy/issues/517#issuecomment-1268009048

Workaround for this:

Open Clipy preferences.
Uncheck 'launch at login'
Log out of macOS
On login, a prompt will pop up: do you want Clipy to run at startup? Say no don't run at startup and don't ask again.

This is the problem, where its 'run at startup' method is deprecated, as noted above.
If you directly add Clipy to the Login Items now, it will run one time, but because you said not to run it every time, it will remove itself and never run after that.

Now open Automator.
New Document
Application
Utilities on left column
Run Shell Script on right column
There paste open -a Clipy
Save that as "Clipy Run" in Applications folder and Close
Now add your Clipy Run Automator app to Login Items.

Great ! @ngaretou
It works fine, thank you.

Please fix this issue!

@ngaretou Thanks, worked for me too!

Would be great to provide a fix in a new release.
Does someone forked the project?

Merci/Thanks @ngaretou, facile et simple à mettre en place. Souhaitons une version à jour bientôt de la part des guerriers du code! / easy and simple to set up. Hope for an updated version soon from the code warriors!

@Econa77 Do you think you could create a new build with this bugfix (the one proposed in the comment above)?

I for myself now switched to https://github.com/p0deje/Maccy

I for myself now switched to https://github.com/p0deje/Maccy

Same on my side

@ngaretou Thanks for that tip. Using your logic, I used Lingon X to add the command open -a Clipy as a launch agent, seems to work as well, another option for users.

Workaround for this:

Open Clipy preferences.

Uncheck 'launch at login'

Log out of macOS

On login, a prompt will pop up: do you want Clipy to run at startup? Say no don't run at startup and don't ask again.

This is the problem, where its 'run at startup' method is deprecated, as noted above.
If you directly add Clipy to the Login Items now, it will run one time, but because you said not to run it every time, it will remove itself and never run after that.

Now open Automator.

New Document

Application

Utilities on left column

Run Shell Script on right column

There paste open -a Clipy

Save that as "Clipy Run" in Applications folder and Close

Now add your Clipy Run Automator app to Login Items.

I am not particularly familiar with Automator but I am usually game for new experiences especially when there are nice clear instructions like these, however, when I open Automator I do not see "New Document" anywhere. There is a list of options such as "Workflow", "Application", "Quick Action", "Folder Actions" one of which I have to choose to continue. So I chose "Application" since it is the next step in the instructions anyway. I then see and choose "Utilities" and then choose "Run Shell Script" but I can find no way to paste "open -a Clipy". Did Automator change since these directions were written? Thanks

@jmilt7 you should be able to achieve the same thing using the 'Launch application' workflow, instructions here:
https://learn.adafruit.com/launch-deck-trellis-m4/app-launching

@jmilt7 you should be able to achieve the same thing using the 'Launch application' workflow, instructions here:
https://learn.adafruit.com/launch-deck-trellis-m4/app-launching

Thanks. Haven't tried this yet as I am debating whether just closing the notification once a day or once every couple of days is a big inconvenience or not in the whole scheme of things but I do like the idea of playing with Automator as I have never tried it before and I like to try new things. So thanks again for this.


[FEATURE] Give the option to define different instance_profile_name per host type

This change gives the ability to have instance_profile_name defined depending on the host type. The option to have a generic instance_profile_name per cluster is kept.
This was successfully tested in the scenarios below:

2 different host types with 1 instance_profile_name each
3 different host types:  1 host type had 1 instance_profile_name and other 2 had generic instance_profile_name
Regression tests:
no instance_profile_name
generic instance_profile_name

The code looks good, haven't tested it


Minor README typos fixed

Fix for wrong config parameter and also s/potal/portal/.

@microsoftopensource, please, take a look.


can't select and unfollwing only one account at a time

been using your code for ages but today when i tried it , instead of done it showed me 101% and i couldn't select , so i went into dev tools and the button was disabled so i changed it to enabled and clicked on unfollow and it only unfollowed 1 account and stopped working

Duplicate #65 & #66


Build with GHC 9.2.8.

Summary
This PR adjusts our nix configuration to build with GHC version 9.2.8 by default.
Related Issues

https://github.com/cardano-foundation/cardano-wallet/pull/4172
https://github.com/cardano-foundation/cardano-wallet/pull/4173
https://github.com/cardano-foundation/cardano-wallet/pull/4181

Closing in favor of https://github.com/cardano-foundation/cardano-wallet/pull/4396 .


debug-log-flag

adding a debug log flag to hide unneeded logs

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Holograms Disappearing

My holograms will disappear after a couple of minutes or so after their creation. If I teleport from one world, then back to the world with holograms, some would reappear, but others wouldn't. The only way to make them all reappear is to reload the plugin, but that only keeps them visible for a couple of minutes until some of them start disappearing.
Plugin Version: 2.12
Server Version: Paper 105

I have the same problem.
Version 2.12
Spigot 1.15.1

Same
Version: 2.12
Spigot: 1.8

@Tathkage @ApocalypticWanderer @TheMixaDev please post plugin lists ran on the server, this may be a conflicting plugin issue.

saintxx help me my holos r dissapearing but it comes back when i do /h reload


vimUtils: buildVimPluginFrom2Nix renamed to buildVimPlugin

the from2Nix suffix is a legacy from vim2nix but we dont use that anymore. It makes the name of the function unusual and long.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

nixpkgs-review:
1 package blacklisted:
nixos-install-tools

1 package built:
vimPlugins.vim2nix


Enhance deployment metrics

What would you like to be added:
I want to keep track of status and events for each application. For example, I'm considering the following:

Add labels for application(like application name, id, etc...) to deployment metrics introduced in v0.44.0
Add metric like argocd_app_info in ArgoCD

This contains labels such as sync_status and health_status that reflect the application state in ArgoCD

Why is this needed:
This is because the additional application information makes it easier to understand the status of each application.

@kanata2 Thanks for raising the issue!
Can you separate this issue into 2 different ones? So we can handle one by one 👍

Done :)


Overridable get_dynamic_repo/0

Dynamic repos don't work well with libraries that take a repo and make queries on your behalf in async tasks, which is the case with Absinthe and Dataloader.
I think the easiest workaround is to make get_dynamic_repo/0 overridable and let the user figure out how to track the current repo across child processes. Here's an example implementation that works with put_dynamic_repo/1:
def get_dynamic_repo do
  [self() | Process.get(:"$callers", [])]
  |> Enum.find_value(fn pid ->
    {:dictionary, dictionary} = Process.info(pid, :dictionary)
    Enum.find_value(dictionary, fn
      {{__MODULE__, :dynamic_repo}, repo} -> repo
      _ -> nil
    end)
  end)
  |> case do
    nil -> super()
    repo -> repo
  end
end

But one could also just completely hand off dynamic repo management to an external multi tenancy library (which is my team's use case):
def get_dynamic_repo do
  MyMultiTenancyLibrary.get_current_tenant()
  |> tenant_to_dynamic_repo()
end

Then you don't have to worry about the implementation of put_dynamic_repo/1.
Thanks!

Thanks for the example! I understand the use case but ideally we want to push a callback upstream to those libs, so you control the spawning, meanwhile you can mark it as overridable yourself. :)

meanwhile you can mark it as overridable yourself.

Can you explain how to do that? I didn't realize that was a feature.

I believe you can call defoverridable yourself or, in worst case scenario, do so inside a @before_compile hook.

Omg, it never occurred to me this would just work...
defmodule Repo do
  use Ecto.Repo

  defoverridable get_dynamic_repo: 0

  def get_dynamic_repo do
    # ...
  end
end

Well, I hit my embarrassment quota for the month... :D


Instructions only generate API for "mkapi"?

(Edit: Found a bug, will make a PR)
I couldn't find instructions on how set the package (sorry if I'm missing something). I am only able to generate mkdocs itself.
Name: mkapi
Version: 1.0.12
Summary: An Auto API Documentation tool.
Home-page: https://mkapi.daizutabi.net
Author: daizutabi
Author-email<EMAIL_ADDRESS>License: MIT
Location: /home/t/work/python/libvcs/.venv/lib/python3.7/site-packages
Requires: jinja2, markdown
Required-by:

libvcs on  new-docs [✘!] ❯ python -V
Python 3.7.7
libvcs on  new-docs [✘!] ❯ pip show mkdocs
Name: mkdocs
Version: 1.1.2
Summary: Project documentation with Markdown.
Home-page: https://www.mkdocs.org
Author: Tom Christie
Author-email<EMAIL_ADDRESS>License: BSD
Location: /home/t/work/python/libvcs/.venv/lib/python3.7/site-packages
Requires: PyYAML, Jinja2, tornado, livereload, lunr, click, Markdown
Required-by: mkdocstrings, mkdocs-material

mkdocs.yml:
# mkdocs.yml
site_name: libvcs
site_url: https://libvcs.git-pull.com
repo_url: https://github.com/vcs-python/libvcs
repo_name: 'GitHub'
theme:
  name: "material"
  custom_dir: .
  logo: assets/images/libvcs.svg
  favicon: assets/images/favicon.ico

plugins:
  - search
  - mkapi

nav:
  - index.md
  - API: mkapi/api/mkapi
  #   - API: mkapi/api/libvcs will crash

Closing.  After #23 I am getting my module to generate properly


Adding next steps to README

Coverage remained the same at 79.435% when pulling c6104b36f2bc893c562c99e5a88461ae9a2b244f on social into 799a2cdeb46343083894f28782fc3178ab6800d8 on develop.


Use Correct cluster type, and add a TODO.

FS4ResourcePool will probably be removed before fixing the TODO

I know, that is why I just added the TODO and didn't fix it.


Protect casted vote

I was wondering how the app and the contract can be changed to protect what a voter chose but still enable anyone to check their vote was casted correctly.

@leog
You can use the queryByKey function and pass in your voterId. One of the fields of the voter object is ballotCast which indicates if they have voted or not, and what was indicated on the ballot.
You could create access control attributes / smart contract logic so that only the voter with their ID can query their own voter Object.
There is an example of attribute-based access control here: https://github.com/IBM/fabric-contract-attribute-based-access-control


Updating to Meteor v1.2 doesn't support less version used

Maybe I'm doing something wrong, but Meteor update isn't letting me update to the latest version of this package.  It actually looks like it downgraded the package in an update, and now meteor update yields:
The following top-level dependencies were not updated to the very latest version
available:
 * joshowens:shareit 0.0.3 (0.3.1 is available)

I tried to force to the latest version with:
meteor remove joshownes:shareit
meteor add<EMAIL_ADDRESS>
But it resulted in the following error:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by less 2.5.0_2.
Constraints on package "less":
*<EMAIL_ADDRESS><- top level
*<EMAIL_ADDRESS><- joshowens:shareit 0.3.1

Any advice?

+1

All that needs to be done is to change api.versionsFrom to api.versionsFrom("METEOR@1.2");

I face similar problem here

Having the same issue. @pmwisdom Where does that change need to be made? Thanks!

Package.js, Ill fork it and make the change for others if theres enough interest.

Use this one : https://github.com/dolgarev/meteor-shareit/

All these suggestions and no PR, eh? :)


Localizations | Bug in dictionary harvester for themes.

The code in DefaultLocalizedStringManager.cs harvests dictionary files for ALL themes on the system; regardless of whether or not the theme is enabled. This can cause issues with multitenant systems where localizations for one site will be visible on other sites in the tenant; or situations where sites are single tenant but themes folders are shared.
Acceptance Critieria:

Localizations from Theme A that is not enabled on a site are not visible when the site is running theme B.

What does this mean:

localizations for one site will be visible on other sites in the tenant

Repro ?

Repro Steps:

create 2 themes with localization dictionaries
prop them to the same Orchard installation
observe how all dictionary files get harvested and localizations from inactive themes bleed over into your active site.

I have a PR I'll try to get up this week.


Migrate the Layout from Module to CompositeModule

As we discussed in our Codesprint last week, the Layout contains only information for instances of CompositeModule.
This PR migrates the Layout from the Module class to the CompositeModule class.
Please review and merge.

:+1:


Better grids, including better RegularCartesianGrid

I see a few things to improve with the grid right now.

We need to add some kind of type information that indicates whether a given dimension is 'flat'. One way to do this could simply be to add the grid sizes in each dimension as parameters in the abstract type Grid, aka:

abstract type Grid{T, Nx, Ny, Nz} end

struct RegularCartesianGrid{T, R, Nx, Ny, Nz} <: Grid{T, Nx, Ny, Nz}
    ...
end

Functions can then dispatch when one of Nx, etc is 1 (including halo-filling functions, which I think may fail when the size of the halo is 0). Another option is to use flags for each dimension rather than the actual size of the grid. In my opinion using the size makes the most sense. Using the actual size could have future advantages; for example, if some optimizations are possible when Nz=2. It is also nice to see the size of the grid from the type signature. A disadvantage is that we then could not have mutable grid types, but I'm not sure we want that.

There is a lot of redundant information in the RegularCartesianGrid struct: cell areas, volumes, total number of grid points, etc. I think it would be better --- meaning that our code would be shorter, easier to read, easier to maintain, easier to reason about (since storing them implies they cannot be computed, which is incorrect) and more computationally efficient --- to add functions that compute these quantities on the fly, rather than storing them in memory.

Related: #287.

Just wanted to point out that PR #283 addresses your second point.
https://github.com/climate-machine/Oceananigans.jl/blob/2176be86be80fb4b9de2c3051c4ea09c74ed00c9/src/operators/areas_and_volumes.jl#L1-L38

I have a revision to my original post.
Rather than add the size of the grid as types in the RegularCartesianGrid signature, we perhaps should come up with a Topology type indicator, eg:
abstract type AbstractTopology end

struct Bounded <: AbstractTopology end
struct Flat <: AbstractTopology end
struct Periodic <: AbstractTopology end

AbstractGrid then becomes
abstract type AbstractGrid{FT, Tx, Ty, Tz} end

where (Tx, Ty, Tz) denote the "topology" of the grid in their respect directions.
For Flat grids, differentiation will return 0, and interpolation will be reduced to an identity function. Distinguishing between Periodic and Bounded topologies will be useful for the implementation of higher-order operators that need to limit to a second-order derivative near non-periodic boundaries (this is important for avoiding the dreaded "halo filling explosion").
I think this also corresponds more closely to the mathematical meaning of a "Periodic" and "Flat" dimension.
Another thought is that we should make the constructor more verbose, eg
RegularCartesianGrid(size=(Nx, Ny, Nz), length=(Lx, Ly, Lz), topology=(Tx, Ty, Tz)).


Use the same author as previous blog posts

Something we missed in the review.

Deploy preview for openbuildservice ready!
Built with commit c6f204c922d4bcba862d7e1f0fcff65fcddbea25
https://deploy-preview-189--openbuildservice.netlify.com

 P2: Blog about new azure upload feature


Fix in object detection task to support train and predict on cpu node.

Issue #, if available:
Description of changes:
PR provides a fix in object detection task when ngpus_per_trial is set to 0 for detector.
Error observed
ind, prob, loc = detector.predict(image_path)

File "/usr/local/lib/python3.6/site-packages/autogluon/task/object_detection/detector.py", line 171, in predict
net.collect_params().reset_ctx(ctx=mx.cpu())
File "/usr/local/lib/python3.6/site-packages/mxnet/gluon/parameter.py", line 929, in reset_ctx
i.reset_ctx(ctx)
File "/usr/local/lib/python3.6/site-packages/mxnet/gluon/parameter.py", line 493, in reset_ctx
"has not been initialized."%self.name)
ValueError: Cannot reset context for Parameter 'mobilenet0_conv0_weight' because it has not been initialized.

Fix
To set the cpu context if num of gpus == 0
Verification script
Verified by passing ngpus_per_trial=0 to the detector
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-697-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-697/2/index.html

Job PR-697-3 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-697/3/index.html


e2e, persistent-ip: Add primary-UDN tests

What this PR does / why we need it:
This PR adds the needed tests needed in order to cover ipam-extentions operation on VMI/VMs using primary-UDN.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

Added commit to prevent the e2e from failing on restart scenario.
@qinqon perhaps this is also needed in the secondary case?

Added commit to prevent the e2e from failing on restart scenario. @qinqon perhaps this is also needed in the secondary case?

for now they are stable, i wouldnt suggest to add unless we see either by code reading or by a failure that it is really needed
not sure if the exact code / flow is there (well you know better as you derived from there)

Added commit to prevent the e2e from failing on restart scenario. @qinqon perhaps this is also needed in the secondary case?

for now they are stable, i wouldnt suggest to add unless we see either by code reading or by a failure that it is really needed not sure if the exact code / flow is there (well you know better as you derived from there)

ah no no ... my bad.

Change: Rebase

@RamLavi let's refactor current tests a little to parameterize role and VM's interface (so we can pass the proper primary UDN network binding).

closing in favor of https://github.com/kubevirt/ipam-extensions/pull/72


Support range search for HNSW

Signed-off-by: yudong.cai<EMAIL_ADDRESS>Issue: #182

/assign @PwzXxm please help on review it~

/lgtm