NTR: mitochondrion proliferation

Hi
It seems like the role of mitochondria in the cell is not well described in GO.
Their role in apoptosis is captured and yet the idea of increasing the activity of a mitochondria or increasing the number of mitochondria is not.
I would like to see 2 new parent terms created (and their regulation child terms) (I have created another ticket for the other term. https://github.com/geneontology/go-ontology/issues/21538)

Suggested term label:mitochondrial proliferation
Definition (free text)
The multiplication of mitochondria, resulting in the expansion of the number of mitochondria within a cell.

*with the note that This term should not be used directly

Reference, in format PMID:28301064

Parent term(s)
possibly  GO:0007005 mitochondrion organization

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?

Suggested term label: regulation of mitochondrial proliferation

Definition (free text)
Any process that modulates the rate, frequency or extent of mitochondrial proliferation within a cell.

*with the note that The use of this term should be limited to the occassions where the number of mitochondria changes within a cell rather than changes associated with cell proliferation or apoptosis

Suggested term label: positive regulation of mitochondrial proliferation
Definition (free text)
Any process that increases the rate, frequency or extent of mitochondrial proliferation which that leads to an increase in the number of mitochondria in a cell.

*with the note that The use of this term should be limited to the occassions where the number of mitochondria increased within a cell rather than an increase due to a cell proliferation

Suggested term label: negative regulation of mitochondrial proliferation
Definition (free text)
Any process that decrease the rate, frequency or extent of mitochondrial proliferation.

*with the note that The use of this term should not be used when the regulation is associated with apoptotic processes where child terms of  GO:0008637 apoptotic mitochondrial changes may be more relevant

Justification
https://pubmed.ncbi.nlm.nih.gov/28301064/ describes: The activation of this PGC-1α - NRF -Tfam pathway leads to synthesis of mitochondrial DNA and proteins and generation of new mitochondria. While the proteins associated with this pathway could be annotated as GO:0090297 positive regulation of mitochondrial DNA replication this term is not linked to the key aspect of why there an increase in mitochondrial DNA replication is occuring, ie because the cell is increasing the number of mitochondria.

Another option might be to use  GO:0090141 positive regulation of mitochondrial fission, note that GO:0000266 mitochondrial fission has the related synonym: mitochondrial proliferation. But again while the mitochondrion will divide, presumably by fission the key aspect of regulating the number of mitochondria is missed. The annotation of proteins involved in the regulation of fission should surely be limited to those that are closely related to the process, not to proteins in the PGC-1α - NRF -Tfam pathway.
Thanks Ruth

Hi Ruth
mitochondrial proliferation sounds like a phenotype, and it is used in multiple ways:
It is the outcome of the process of "increased mitochondrial fission" (creation of more smaller mitochondria) or increased 'mitochondrion biogenesis" increase in the number of new mitochondria (we do not have this term, this would be valid as it would keep the distinction).
Proliferation could be a related synonym for these  terms.

I disagree with this being a 'phenotype'.
I think mitochondrial fission is equivalent to the cell term 'cytokinesis'. It doesn't really capture how some cells need more mitochondria than other cells and that therefore the number of mitochondria / cell needs to be regulated.
I would be happy with the term 'mitochondrion biogenesis'. However as mitochondria have their own DNA and as such are like mini-cells I am not sure that the definition: A cellular process that results in the biosynthesis of constituent macromolecules, assembly, and arrangement of constituent parts of mitochondrion. Really describes the process. But mitochondrial biogenesis does seems to be an accepted term, the phrase identifies >90,000 articles in PMC eg:https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3883043/ https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7205802/. So this seems to be the easiest option.
BTW I was looking at the regulation of cell division and regulation of cytokinesis and I think these definitions need to be edited to be in line with the parent terms:
regulation definitions:

reg cell division: Any process that modulates the frequency, rate or extent of the physical partitioning and separation of a cell into daughter cells.
reg cytokinesis: Any process that modulates the frequency, rate or extent of the division of the cytoplasm of a cell and its separation into two daughter cells.

Term definitions:

cell division: The process resulting in division and partitioning of components of a cell to form more cells; may or may not be accompanied by the physical separation of a cell into distinct, individually membrane-bounded daughter cells.
cytokinesis: The division of the cytoplasm and the plasma membrane of a cell and its partitioning into two daughter cells.

Thanks for looking at this request so quickly
Ruth

A bit more infomation/clarification.
In single-celled organisms (and presumably most cells), during interphase the mitochondria fuse together into a very small number of large mitochondria. There is no mechanism for partitioning, so at mitosis the mitochondria undergo lots of fission to create a large number of smaller mitochondria. This ensures that at cell division each cell is likely to receive some mitochondria at division (and probably also so that the mitochondria are not ruptured by the cleavage machinery. So the 'process which occurs at  the end of interphase could be called 'proliferation' because it results in more mitochondria.
After division, during the next interphase, the number of mitochondria will need to increase as the cell doubles its contents. This process is relatively unstudied at the molecular level which is why we currently have no term for this.  Will involve making/ moving  membrane material via ERMES?, DNA replication and translating/importing proteins (Both nuclear and mitochondrial encoded).
So, 'proliferation'  could refer to 2 distinct processes, one of growth, and one of division (it's just the observation that there are a larger number of mitochondria). I guess 'proliferation' could be a parent of biogenesis and fission if it is useful.
mitochondrial DNA replication (GO:0006264)
mitochondrial translation (GO:0032543)
protein import into mitochondrial matrix (GO:0030150)
other import terms
would need to be placed under the biogenesis term.

I'm only commenting on this because I fairly recently reviewed all of our mitochondrial annotation, and I just wanted to make sure that any changes to the structure are consistent with
the existing annotation.

Hi Val
as always your insight is so helpful. There is also the aspect of some cells requiring more mitochondria as they differentiate or are activated maybe to enable them to perform their new role.
What would be nice about what you have suggested above is that there would be a grouping term which might be useful when proteins required for these specific processes are all coregulated and therefore the overall goal of mitochondrial DNA replication is seen.

I was just going to comment on this ticket again. I think the proliferation term you suggested will be fine in this context. I think I have an aversion to 'proliferation because of all the problems the "cell proliferation" terms caused for single-celled organisms, but here it is a cell level process, so it's fine!

Thanks to both for the useful discussion.
@RLovering Do you need the regulation terms? Seems like mitochondrial proliferation would be sufficient to capture the paper you mention?

yes this is fine - thanks


RFC: Rebalancing Seed Rewards for Unripe Assets

Problem
Beanstalk has been unable to bring the price of Bean back to $1 after the most recent cross below peg on September 19, despite sufficient assets available for conversion in the Silo. The magnitude of the deviation from peg is far greater than the trading fee on the Curve pool, which suggests that Silo incentives are less than optimal.
Currently, Unripe assets in the Silo are allocated Stalk and Seed proportionate to new deposits made to the Silo. For example, urBEAN deposits to the Silo are allocated Stalk and Seed at a 1:2 ratio, just like BEAN deposits. Similarly, urBEAN3CRV deposits to the Silo are allocated Stalk and Seed at a 1:4 ratio, just like BEAN3CRV deposits.
The opportunity cost presented by this imbalance is a significant deterrence to conversions from urBEAN3CRV to urBEAN below peg. The quantity of Seeds lost in the process will produce the amount of Stalk earned within days. Unless a Silo member anticipates being able to quickly convert back to urBEAN3CRV, they will lose ground to other Silo members, diminishing their share of future Bean seignorage.
Additionally, since Beanstalk's replant, new participation in the Silo has been lackluster. Although there was an initial spike in Silo participation after the replant, with >$5M BEAN3CRV deposited then, Silo participation has since dwindled to <$1M BEAN3CRV. It is likely that the similarity in the Stalk:Seed allocation between Unripe assets and new assets deposited to the Silo may be a deterrent to new users considering engaging in Beanstalk, as new deposits currently accrue Grown Stalk at the same rate as their counterpart Unripe assets, despite the fact that new deposits are more markedly supporting the protocol's growth and stability since the replant vis-a-vis their provision of non-BEAN liquidity.
Proposed Solution
Given that it is likely that the majority of the liquidity represented by Unripe LP tokens will remain in the Curve pool until those assets ripen, there is less need to use Seed rewards to incentivize liquidity for Bean to trade against. By equalizing the Stalk:Seed allocation for all Unripe assets, the opportunity cost in the loss of Seeds when converting from urBEAN3CRV to urBEAN when BEAN is trading below peg would be removed, thus reducing friction and fostering a greater incentive to participate in peg maintenance by Unripe asset holders.
Solution: Reduce the Stalk:Seed allocation for all Unripe assets deposited to the Silo down to 1:1. This would incentivize Unripe asset holders to more actively participate in peg maintenance, while also acknowledging and incentivizing greater participation of new users in the Silo.

For reference, changing the # of Seeds per BDV of a Silo Whitelisted asset is something that has never been performed before. Unfortunately, Silo V2 does not natively support the modification of the number of Seeds per BDV of a Whitelisted Silo asset.
For transparency purposes, here is our thoughts on the technical
Technical Walkthrough
A user's balance of Seeds is set to the summation of the seedsPerBDV * bdv at the time of deposit (Not the current seedsPerBDV) for all their Deposits.
If Stalk Holders decrement the s.ss[token].seeds stalk variable (seedsPerBDV of a given token), all new Deposits will use the new s.ss[token].seeds, but old Deposits will not automatically be updated to use the new value. Functions that remove Deposits (enrootDeposit(s), convert, transferDeposit(s), withdrawDeposit(s)) will burn the incorrect amount of Seeds when removing old Deposits because these Deposits were Deposited with a different s.ss[token].seeds value.
This proposal proposes to decrement s.ss[token].seeds of two different Whitelisted ERC-20 tokens.
Technical Implementation
In order to facilitate this, we need to:

Decrement s.ss[token].seeds value in storage'
Migrate all Deposits with a new s.ss[token].seeds value in an account before they interact with enrootDeposit(s), convert, transferDeposit(s) and withdrawDeposit(s)

(1) is quite trivial through a 1 time function call, but (2) is not.
There are two technical ways to do this (2):
a. Permissioned Automatic Migration: Migrate every account at the time of modification
b. Permissionless Manual Migration: Force accounts to manually migrate before they can interact with the Silo.
Permissioned Automatic Migration
Permissioned Automatic Migration Migration would require trust that a specific account (Ex. the BCM) performs the migration correctly at the time that (1) happens. This would be far cheaper gas wise. Permissioned migration could be done through a 1 time migration script. Permissioned on-chain action is never ideal.
Permissionless
Permissionless Manual Migration would mandate that a Farmer update their Seeds balance through a migrate function before they use the Silo. Any account could migrate any account and thus a public goods actor could still manually perform the migration as soon as (1) occurs (Ex. BF/BS). Thus, the Farmer user experience could still feel seemless as they won't have to manually migrate. Migration could also be automated at the UI level such that the UI would automatically call migrate through a farm function call when a Farmer first interacts with the Silo. In this case, bots would still have to manually figure out how to migrate. Manual Migration would require a full upgrade of the Silo.
Permissionless Migration requires be on-chain verification of Seed balances, which means:

Farmers would have to submit all of their non-zero Token, Season Silo Deposit pairings in a function, which could be hard for users to do without the aid of an off-chain script/UI.
Migration Is far less gas efficient. The migrate function would be relatively more expensive as it would need to read the value of all of their Deposits on-chain (Requires a $G_{coldsload}$, which is 2100 gas).

Additional Thoughts

If done once, this process could easily be generalized to perform again if in the future Stalk Holders wanted to change another seedsPerBDV function.
A Stalk Gauge system is proposed in Silo V3, which will make this process unnecessary, so such a feature would only be useful in the short term. Development of Silo V3 will possibly start after the completion of Wells, but will take a substantial amount of time to build.


Implement partial customize

If delta traffic only affects several cells, we can speed up the customize process by only process this affected cells.

It's better to add a command line parameter to enable/not-enable this function.

Task has been implemented here:
https://github.com/Telenav/osrm-backend/issues/49#issuecomment-534803683


Allow several settings.json

Proposed feature
VSCode should not only read the standard settings.json, but also additional settings files. I can imagine different ways how to specify these files. For example:

All *.json files in a predefined folder like ~/.config/Code/User/settings
All files matching a regex like settings.*\.json (matching settings.json, settings1.json, settingsReadOnly.json, settingsTeamWide.json, settingsCheckedInToGitRepo.json, etc.)
Files given on the command line like code --additional-settings=path/to/additional/settings.json

This way, different sets of settings can be specified editor-wide. These would have to be merged with some notion of precedence, similar to how workspace settings are merged with user settings.
Context
I'm trying to improve the VSCode experience on NixOS/Home Manager. There, one configures the editor declaratively, producing a config file that is not writable by the editor. It would be great if there were two settings files, one read-only file produced by Home Manager, and an editor-writable file (the standard settings.json).
Other use cases

Software development teams might want to share some of their settings (across multiple workspaces) by checking them into version control. On top, some team members want their own settings.
For debugging, one could turn a set of settings on or off by extracting them to a file.

It seems you are using VSCodium and this project is VS Code and both are not same. I would request to file issue against VSCodium project.

Sorry, I accidentally posted the VSCodium paths because I tested whether the issue is there as well. But the issue is about VSCode. Can we reopen?

There is a duplicate of this request, please search for existing issues. Thanks.

I have searched through >300 issues here: https://github.com/microsoft/vscode/issues?q=is%3Aissue+settings.json+is%3Aopen.
I found some related ones:

https://github.com/microsoft/vscode/issues/80972
https://github.com/microsoft/vscode/issues/17634
https://github.com/microsoft/vscode/issues/15909


Allow PHPUnit 11

@shadowhand I'm pinging you directly since this repo isn't very active. I don't think phpunit 11 has introduced any failures.

Released in version 2.2.0.


Create generic health check functions

For every type of supported health check, we will need a function to perform the check. So far, these are:

[ ] :tcp - a simple TCP "ping-like" functionality (e.g., TCP CONNECT-only) - connect to host and port
[ ] :http - an HTTP health check - do an HTTP GET against a specified endpoint and parse results
[ ] :docker - check the status of a running Docker container
[ ] :cpu - check the CPU usage of a process-based service

Ultimately, these would be used like so at the system-component-level:
[{:name :mock-echo :type :tcp :frequency 30000}
 {:name :mock-echo :type :http :frequency 5000}
 {:name :elasticsearch :type :docker :frequency 10000}

But directly, these functions would probably be utilized by a new health method supported by service components -- those would be responsible for setting/configuring the proper hosts, ports, endpoints, containers, etc.
As such, dev tasks might be this:

[ ] Create generic TCP ping function ... maybe return {:connects? <bool>}
[x] Create generic HTTP GETter with response body-parsing and HTTP status code-checking ... maybe return {:status <int> :value <parsed body>}
[ ] Create generic Docker container checker ... maybe return {:container-up? <bool>}
[ ] Create a generic process CPU checker ... maybe return {:cpu <float>}
[ ] Update ProcessRunner component to support a health method
[ ] Update DockerRunner component to support a health method
[ ] Implement health methods for each service type to call the appropriate generic health functions, dispatched on type

HTTP GETer done in b79c041.

Docker checker done in 06d8eca.

Added TCP ping support in 261f564.


Fix water heater, add EVU lock switch, and extend SG ready

Adapt integration setup to latest HA
Extend SG-Ready selection to support all cases
Add new EVU lock switch to set EVU Lock from HA
Fix Water Heater mode change

fixes #107


I was import the sdk and get errors

The step I done below, can someone help me with this error
install
npm install orbiter-sdk --save
and import the sdk in code (I am using nodejs)
const { Bridge, BridgeChain, BridgeToken } = require("orbiter-sdk")
then I am getting this error
error: ENOENT: no such file or directory, open '/**/node_modules/orbiter-sdk/dist/zksync-crypto-node_bg.wasm'

Same here

same here

Same here

Same here

same here

Same here. Has anyone fixed the issue?

Same here, any fix for this??

same here

Has this been fixed? Why has the team not addressed this?

same here

same here!
I found the simplest solution for me, remove everything unnecessary from the example folder and write what I need right inside it, importing everything from folders, and not from sdk. Let's see if what works will work fine.

Gm sir, did this work for you? ty @Naughty1905

For anyone struggling with the issue, it seems that the team is abandoned this SDK based their response on discord:

I find the solve.
first

add zksync to the external of rollup config
then

change version of "@rollup/plugin-commonjs" to ^22.1.0

To solve this issue you can download the last version of orbiter-sdk from github, build it, and put dist folder with node_modules into your project

git clone https://github.com/Orbiter-Finance/orbiter-sdk
cd orbiter-sdk
modify file rollup.config.ts line 19     external: ['ethers', 'web3', 'lodash','zksync','zksync-web3'],
modify file package.json line 87    "@rollup/plugin-commonjs": "^24.1.0",
npm install
npm run build
copy dist file to your project -> node_modules/orbiter-sdk     replace the dist dir

git clone https://github.com/Orbiter-Finance/orbiter-sdk
cd orbiter-sdk
modify file rollup.config.ts line 19     external: ['ethers', 'web3', 'lodash','zksync','zksync-web3'],
modify file package.json line 87    "@rollup/plugin-commonjs": "^24.1.0",
npm install
npm run build
copy dist file to your project -> node_modules/orbiter-sdk     replace the dist dir

Hi sir, does this still work? tried this approach in order to integrate into a nodeJS project but didnt reach any success. Got some provider issues from the SDK even though i tried both ethers and web3js?


Differences between graphemes in case of diatrics

I am not a font specialist but my understanding of glyphs in OpenType is that they can be defined either as a standalone character or as a combinations of other glyphs (the components array attribute of the glyph).
Now in this case, I would expect for both to have the same path and bounding box.
My example uses Node.js 9.x, opentype.js 0.10.x on OSX and the font is "Menlo Regular" that can be found here: https://github.com/hbin/top-programming-fonts/blob/master/Menlo-Regular.ttf
e.g:
> const opentype = require('opentype.js');

> const font = opentype.loadSync('/Some/Path/Downloads/Menlo-Regular.ttf')

> font.charToGlyph('ў')
Glyph {
  index: 916,
  name: 'uni045E',
  unicode: 1118,
  unicodes: [ 1118 ],
  advanceWidth: 1233,
  components:
   [ { glyphIndex: 651,
       xScale: 1,
       scale01: 0,
       scale10: 0,
       yScale: 1,
       dx: 0,
       dy: 0 },
     { glyphIndex: 92,
       xScale: 1,
       scale01: 0,
       scale10: 0,
       yScale: 1,
       dx: 0,
       dy: 0 } ] ... }

> font.stringToGlyphs('y\u0306')
[ Glyph {
    index: 92,
    name: 'y',
    unicode: 121,
    unicodes: [ 121 ],
    advanceWidth: 1233 ... },
  Glyph {
    index: 651,
    name: 'uni0306',
    unicode: 774,
    unicodes: [ 774 ],
    advanceWidth: 1233 ... } ]

Since the glyph at index 916 is defined as the sum of the glyphs at index 92 and 651, I would expect for both bounding boxes to be identical but that doesn't seem to be the case.
e.g:
> font.getPath('y\u0306', 0, 0, 12).getBoundingBox()
BoundingBox { x1: 0.609375, y1: -9.421875, x2: 12.673828125, y2: 2.49609375 }

> font.getPath('ў', 0, 0, 12).getBoundingBox()
BoundingBox { x1: 0.609375, y1: -9.421875, x2: 6.755859375, y2: 2.49609375 }

If we look at the path, they look to be identical besides the fact that the order of the diatric (\u0306) compared to the letter (y) is inverted. The user input string has the diatric after the letter but the "components" of the glyph has it before the letter.
e.g: https://www.diffchecker.com/gCdoMNrU
Is this a misconception by me or this considered to be a bug?
Visually they seem identical so it seems weird for the paths
Thanks in advance!

Hi!
It looks like a bug but I won't be able to investigate more unfortunately.
Note: You can check the glyphs visually with the Glyph Inspector

@Jolg42 Thanks for the quick reply. I'll try to find a different way then, thanks.


cf s command very slow since 6.35

Hello,
the cf s command is much slower in version 6.35.2, compared to 6.34.1.
Command
cf s
What occurred
With version 6.34.1: cf s  0.18s user 0.04s system 4% cpu 4.647 total
With version 6.35.2: cf s  0.26s user 0.10s system 1% cpu 30.341 total
CLI Version
cf version 6.34.1+bbdf81482.2018-01-17
cf version 6.35.2+88a03e995.2018-03-15

CC API Endpoint Version
api version:    2.101.0
Platform & Shell Details
MacOS 10.13.3 (also occured on Windows 10 x64)
Any other relevant information
Also occurred with CF CLI version 6.35.0, however the command resulted in an error message (see https://github.com/cloudfoundry/cli/issues/1342).

Yup! In CF 6.35.0, the CF CLI switched from using a single /spaces/summary API call to individual /service, /service_instance, etc. API calls. Due to the increased number of API calls, the services request is much slower.
Why did it switch? The /services/summary API call breaks when there are more than 50 services or apps. Additionally, the break returns back a successful status code, so the CLI can't tell the difference between 51+ services/apps and 0 services/apps. So it would appear that all your services are gone!
There might be a way to cache some of these requests if they happen to be looking up duplicate objects, but overall the speed increase may be negligible.

Hi @choffm thanks for creating this issue. We are closing this issue but please do not hesitate to reach out if this issue becomes too problematic. Thanks.

Reopening because we've received feedback that this command was actually returning the correct number of services/apps if there are more than 50. And the change we made introduced higher latency.

Hi,
as @abbyachau  stated, the change which slowed down the cf s command wasn't even necessary, but it is a real pain for people who use the cli on a daily basis. In some of my spaces, it takes up to 90 seconds for the command to return the list of services.
Can you please revert the changes or provide another fix for the performance degradation?
Thanks

Hi @choffm thanks for your note! For now, we're planning to fix this (and  cf m which can also become quite slow) in V3 of the API and not V2.

I'll close this out for now. :)

Are you planning to release this soon?

Hi @Kiemes this is slated for the next release which we hope to release soon.


AMD ROCm Debian repositories add versioning

Please add versioning to the Debian http://repo.radeon.com/rocm/apt/debian/ ROCm repositories.
Currently only the latest ROCm version and depending packages seems to be available in the Debian repository.
Otherwise a necessary downgrade or deployment with a specified ROCm version is very hard to achieve.
In this specific case ROCm 1.9.2 is needed as Tensorflow has issues with ROCm 2.0.

Here is another use case, where a downgrade avoids regressions with gfx900 / Vega GPUs:
https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/issues/343#issuecomment-470282471

thanks for the hint to the archive, this made my darktable working again :) ( #846 )

Is this still an issue?  If not; can we please close it?  Thanks!

If you go to the following link:
http://repo.radeon.com/rocm/apt/debian/pool/main/r/
All the components and their versions can be found.  Closing issue but if you need further assistant. You can open a new ticket and we will be more than happy to help.


Update Configuration when master conf changed

What changes are proposed in this pull request?
Related to #17296

I think there are still many issues that need to be resolved here:

When pulling the cluster configuration from the Master node, it will be merged with the current node's configuration. However, since the configurations defined in the configuration file have a higher priority than those in the cluster configuration, it is impossible to change configurations that have already been defined in the configuration file.
If using the current method of cluster configuration to dynamically update Worker node configurations, it seems that only updating some of them cannot be achieved.
Proxy users are a security-related feature and there are security concerns when receiving their settings over a network.

I retried the failing tests and they still fail. One of them is
2023-05-18T02:05:08.5219898Z 02:05:08.519 [ERROR] alluxio.job.master.LostWorkerIntegrationTest.lostWorkerReregisters  Time elapsed: 15.559 s  <<< FAILURE!
2023-05-18T02:05:08.5220426Z java.lang.AssertionError
2023-05-18T02:05:08.5220872Z 	at org.junit.Assert.fail(Assert.java:87)
2023-05-18T02:05:08.5221256Z 	at org.junit.Assert.assertTrue(Assert.java:42)
2023-05-18T02:05:08.5221657Z 	at org.junit.Assert.assertTrue(Assert.java:53)
2023-05-18T02:05:08.5222347Z 	at alluxio.job.master.LostWorkerIntegrationTest.lostWorkerReregisters(LostWorkerIntegrationTest.java:70)
2023-05-18T02:05:08.5223006Z 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2023-05-18T02:05:08.5223655Z 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2023-05-18T02:05:08.5224305Z 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2023-05-18T02:05:08.5225139Z 	at java.lang.reflect.Method.invoke(Method.java:498)
2023-05-18T02:05:08.5225871Z 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
2023-05-18T02:05:08.5291615Z 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
2023-05-18T02:05:08.5292761Z 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
2023-05-18T02:05:08.5293432Z 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
2023-05-18T02:05:08.5294224Z 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
2023-05-18T02:05:08.5294871Z 	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
2023-05-18T02:05:08.5295484Z 	at alluxio.testutils.LocalAlluxioClusterResource$1.evaluate(LocalAlluxioClusterResource.java:202)
2023-05-18T02:05:08.5296530Z 	at alluxio.heartbeat.ManuallyScheduleHeartbeat$1.evaluate(ManuallyScheduleHeartbeat.java:81)
2023-05-18T02:05:08.5297279Z 	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:288)
2023-05-18T02:05:08.5297978Z 	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:282)
2023-05-18T02:05:08.5298866Z 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
2023-05-18T02:05:08.5300059Z 	at java.lang.Thread.run(Thread.java:748)

@maobaolong could you take a look? Thanks!


Fix typo

Description of the Change
Change shuould by should
Alternate Designs
None
Why Should This Be In Core?
Good spelling
Benefits
Fix typo
Possible Drawbacks
None
Applicable Issues
Typo

thanks @faustinoaq


Please use ${CXX} instead of hardcoding g++ because in different systems C++ compiler has different executable names

Additionally, when the compilation command fails because the compiler is non-existent the script continues and prints bogus messages. You probably want to add set -x to make scripts stop on errors.

Thank you for the advice.
I've changed the Makefile.
https://github.com/herumi/xbyak/commit/6989aea9460557bf0d4aec4681ea73f0a05cfd96

Thank you.


How to animate scrollTo

I was wondering what would be the best practice for animating the scrollTo function? Thanks for this great library!

Check the source and you'll notice the top position of an index is calculated by getSpaceBefore(index), so you can use that to get the raw target scrollTop (though it's not documented). Once you have that just use your favorite animation library to set whatever your scrollable element is to animate toward that scrollTop.

My solution for react-scroll:
import { animateScroll as scroll } from 'react-scroll';

const y = reactListRef.current.getSpaceBefore(target);

scroll.scrollTo(y, {
  container: reactListRef.current.scrollParent,
  isDynmic: true,
  duration: 400,
  smooth: 'easeInOutQuad',
});


Added a Matrix Hello World Greeting

First Julia Program
What does the program do ?
Basic Hello World Program. Banner style printing using matrix.
In what programming language it is written?
Julia

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Kirkstone

This fixes vsdbg, aspnet-core and dotnet-core syntax and build issues for branch kirkstone and pull request #47
Summary
I was facing the issue thas vsdbg and aspnet-core were unbuildable.
vsdbg used old Bitbake syntax and the link to use visual Studio 2019 causes errors.
aspnet-core and dotnet-core had issues with liblttng-ust.so.0.
@jacobusvanzyl  please confirm the changes takes affekt and add them to your pull request #47.
aspnet-core and dotnet-core fix for liblttng-ust.so.0 issue
Fixed errors
aspnet-core:
ERROR: aspnet-core-6.0.8-r0 do_package_qa: QA Issue: /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.8/libcoreclrtraceptprovider.so contained in package aspnet-core requires liblttng-ust.so.0()(64bit), but no providers found in RDEPENDS:aspnet-core? [file-rdeps]
ERROR: aspnet-core-6.0.8-r0 do_package_qa: Fatal QA errors were found, failing task.

dotnet-core
ERROR: dotnet-core-6.0.8-r0 do_package_qa: QA Issue: /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.8/libcoreclrtraceptprovider.so contained in package dotnet-core requires liblttng-ust.so.0()(64bit), but no providers found in RDEPENDS:dotnet-core? [file-rdeps]
ERROR: dotnet-core-6.0.8-r0 do_package_qa: Fatal QA errors were found, failing task.

Solution
I've added a hack to files recipes-runtime/aspnet-core/aspnet-core_6.x.inc and recipes-runtime/dotnet-core/dotnet-core_6.x.x.inc which  removes the liblttng-ust.so-0 library in libcoreclrtraceptprovider.so that causes this error. This hack must be removed if the issue was fixed.
Changes:

recipes-runtime/aspnet-core/aspnet-core_6.x.x.inc
recipes-runtime/aspnet-core/aspnet-core_6.x.x.inc
recipes-runtime/dotnet-core/dotnet-core_6.x.x.inc

vsdbg
Fixed errors
Visual Studio 2019 link issue:
@jacobusvanzyl Visual Studio 2019 is obsolete with release of Visual Studio 2022. You also can comment the part of link creation out in file recipes-devtools/vsdbg/vsdbg_17.x.inc for users which want tot use it.
I highly recommend to disable Visual Studio 2019 support by default.
 absolute symlink: /root/.vs-debugger/vs2019 -> /root/.vs-debugger/vs2022
 Recognition of file /home/test/yocto/build/tmp/work/cortexa53-crypto-linux/vsdbg/17.2.10518.1-r0/package/root/.vs-debugger/vs2019 failed: mode 120777 broken symbolic link to /root/.vs-debugger/vs2022 (Permission denied)

vsdbg old syntax issues
install: cannot stat '/home/test/yocto/build/tmp/work/cortexa53-crypto-seconorth-linux/vsdbg/17.2.10518.1-r0/vsdbg-17.2.10518.1/vsdbg': No such file or directory

Solution
Changes:

recipes-devtools/vsdbg/vsdbg_17.2.10518.1.inc
recipes-devtools/vsdbg/vsdbg_17.x.inc

@electroScorpion This compiles without issues, although it did so before in my environment.

@jacobusvanzyl Thanks for merging. Did you have included vsdbg, aspnet-core and dotnet-core in your testimage?
Indeed i'm surprised that you have not faced with the same problems. Excluding the vs2019 link issue.

@electroScorpion I only needed aspnet-core. The other required libs were provided by recipes from other layers i suspect. Perhaps what is needed is a layer dependency on layers that contain the required recipes. What i do get during my build is this:

lttng-modules-2.13.7-r0 do_package: lttng-modules: no modules were created; this may be due to CONFIG_TRACEPOINTS not being enabled in your kernel.

I suspect the whole tracing aspect was thus not included in my image in any case.


V0.5rc: Improve overlap/overdue alert messages.

Coverage remained the same at 80.608% when pulling e6adc2b1df19cb946187b3f9a9c33dd655e711d5 on V0.5rc_overdue-alert into 61cbe2d782ce5348d465af5a3f762e551fcab8e2 on V0.5rc.

I'll merge first since it's a small change and to allow dogfooding.


Service Discovery: set label on service containers

As a part of this PR:

"labels" field (Map<String, String>) is introduced on the "container" object. So labels can be set through this field on per standalone container basis, as well as on the services' containers as their launchConfig is of type "container". All affinity rules user defines in the compose, get translated into lables on launchConfig. Expected format: "affinity:container==" - for affinity rules, "constraint:label_key==bar" - for placement rules

When ServiceDiscovery manager builds launch data for container, it copies all labels defined on services launch config, and set them per each service container ("labels" field on the container)+ adds one more extra label with key="container_label" and value=

@ibuildthecloud Darren, let me know if the above is what you expected, or if anything is missing. @will-chan suggested that we use service name, not uuid for defining the service container. The reason is - at the moment compose file is defined, user doesn't know service's uuid, only name; so we stick to name so we don't have to do any name to uuid translation
@sonchang Son, let me know if the format for labeling the service container (key="container_label" and value=) is what the allocator expects.

I separated putting container.labels field to a separate PR: https://github.com/rancherio/cattle/pull/415


From existing code fixes

Bunch of fixes to from existing code template.

Give the user the ability to select the language the project is targeting and add appropriate files (js/jsx vs. ts/tsx) in each case.
Save the project file next to the source files, this fixes a whole host of issues, since VS assumes the project file is the root folder for the source files.
Make sure the From Existing Code wizard has the right accessibility properties set on each control.

This fixes the following issues:

#1540
#1439
#1443
#1440
#1367
#1366
#1365
#1594
#1615

        catch (UnauthorizedAccessException)

This one can't be IOException?

Refers to: Nodejs/Product/Nodejs/Project/ImportWizard/ImportSettings.cs:525 in 919e9da. [](commit_id = 919e9da2c3674454a749bef759cb96b4f840b8e2, deletion_comment = False)

            .Where(path => path.StartsWith(source, StringComparison.Ordinal))

Why is this comparison case sensitive?

Refers to: Nodejs/Product/Nodejs/Project/ImportWizard/ImportSettings.cs:548 in 919e9da. [](commit_id = 919e9da2c3674454a749bef759cb96b4f840b8e2, deletion_comment = False)


ContinuousPHP Public IP

The continuousPHP platform use three IP for outside connection.
We should list them into the documentation :

<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>

@Pierozi agreed. Can be useful for opening firewalls.


invite members

Included invite members flow

@jerae-duffin The images aren't rendered correctly in the Netlify Preview. Could you also check and fix any broken links?


Fix ExclusivityManager synchronization bug (#543)

The ExclusivityManager was using DispatchQueue.initiated, which returns a global queue that is a concurrent queue, however its internals are dependent upon serial execution of add/remove.
Fixed to create and use a serial queue.
(Reported by @myexec in #543.)

StressTests failed because of the issue that is fixed in PR #544.

Thanks @swiftlyfalling - simple fix is often the best. Can discuss later how to minimise unintended misuse of the DispatchQueue extension. Possibly get rid of it, or maybe wrap the statics inside a Global struct?
Something like:
extension DispatchQueue {
    public struct Global {
        public static var `default`: DispatchQueue {
            return DispatchQueue.global(qos: DispatchQoS.QoSClass.default)
        }
        private init() { }
   }
}


Fix data obfuscation and ID field issues in updateUser function

Issue Description
The updateUser function in controllers/users.js has two critical issues:

It merges obfuscated email and phone number data into the user record.
It incorrectly includes an id field when updating user data, potentially causing conflicts with the document's actual ID.

Expected Behavior

The function should merge unobfuscated email and phone number data into the user record.
The id field should be excluded when updating user data.

Current Behavior

Obfuscated email and phone number data from fetchProfileDiff are being merged into the user record.
An id field is included in the data used to update the user record, which may interfere with the document's actual ID.

Screenshots
N/A
Reproducibility

[x] This issue is reproducible
[ ] This issue is not reproducible

Steps to Reproduce

Call the updateUser function with a valid profileDiffId.
Check the updated user record in the database.
Observe that the email and phone number are obfuscated and an extra id field is present.

Severity/Priority

[ ] Critical
[x] High
[ ] Medium
[ ] Low

Additional Information
The fetchProfileDiff function returns obfuscated data for UI purposes, but this data is being directly used to update the user record. We need to implement a way to get both obfuscated (for UI) and unobfuscated (for database updates) data.
Proposed Solution

Create a new function in profileDiffsQuery that returns unobfuscated data for database updates.
Modify the updateUser function to use this new function for getting unobfuscated data.
Implement a filtering step to remove the id field before updating the user record.

Checklist

[x] I have read and followed the project's code of conduct.
[x] I have searched for similar issues before creating this one.
[x] I have provided all the necessary information to understand and reproduce the issue.
[x] I am willing to contribute to the resolution of this issue.

Hello,
Code Reference : models/users.js - addOrUpdate function
In addOrUpdate function, we are setting 2 objects in firestore. As per my understanding, user.data() takes in current data and re sets it in the document and then userData updates the profileDiff fields. If i am correct, then to resolve the above issue, should i also remove id field from user.data() object as well and userData because if i only remove it from userData then if a document has an id set previously due to bug, it would still continue to exist even after setting profile diff with filtered out id field.


Setup linter

I apparently didn't set up linting at all? We should use the cli to do the linting, as a form of integration testing

I've labelled this one with all the packages, but we don't have to have a single, mega pr to do all of them -- I'll take one for any one package (or even file, I guess).


Add support for Market / Limit Maker orders in Gate.io Perpetual

Description

As described in Hummingbot Roadmap item #6210, we plan to support more order types for the Gold and Silver exchange connectors
Add support for market and limit maker orders in the gate_io_perpetual connector, a Silver CEX connector for Epoch 4
Investigate if support already exists, and add support if it doesn't
Modify unit tests to ensure they pass
Refer to this PR which add market orders to Binance: https://github.com/hummingbot/hummingbot/pull/6279, as well as the binance_perpetual connector

Bounty

Sponsor: Hummingbot Foundation
Bounty amount: 10,000 HBOT
Developer portion: 100%
Status: OPEN

i'd like to accept this ticket

This Bounty is assigned to @yancong001, thank you for your contribution

here https://github.com/hummingbot/hummingbot/pull/6305

Closing this bounty as paid


Adding support for 12Mhz crystal oscillator in init.py

Please add in init.py support for a crystal oscillator running at 12Mhz.
I would like to use on a WaveShare RP2040-PiZero  with a WaveShare RS485 CAN HAT for Raspberry Pi which uses a 12Mhz oscillator. This HAT exists in to variants, one with 8Mhz and one with 12Mhz.

As mentioned in adafruit_mcp2515/init.py, I used the CAN bus timing calculator and inserted in init.py before the 10Mhz definition the following:
    # 12MHz Crystal oscillator (used on the WaveShare RS485 CAN HAT)
    12000000: {
        #        CNF1, CNF2, CNF3
        1000000: (0x00, 0x88, 0x01),
        500000: (0x00, 0x9A, 0x03),
        250000: (0x00, 0xBF, 0x06),
        200000: (0x02, 0x92, 0x02),
        125000: (0x01, 0xBF, 0x06),
        100000: (0x02, 0xB5, 0x05),
    },

and was able to receive frames with correct data on a Raspberry Pi5 with a CAN-USB dongle (USB ID 1d50:606f) at 500kbits/s.


StaticInjectorError[MzToastService]

Getting to following error after update to 1.7.1
Error: StaticInjectorError[MzToastService]:
  StaticInjectorError[MzToastService]:
  NullInjectorError: No provider for MzToastService!

Your Environment

Version used: 1.7.1
Angular version used: 4.4.6 / 5.0.3
Browser Name and version: chrome
Operating System and version (desktop or mobile): desktop
Link to your project (if appropriate): https://github.com/Liad91/VeganNearby

@Liad91 Thank for the PR!

@Liad91 your fix has been released with v1.7.2


Generation fails assuming next xjc argument is an argument to the plugin

Hi Mirko,
Starting with the version of 1.16.0 of the plugin I can't generate classes out of a wsdl definition. The generation fails with the following output:
...
[INFO] jaxws:wsimport args: [-keep, -s, C:\Users\drusdi1\workspace\ias-api-test\target\generated-sources\java, -d, C:\Users\drusdi1\workspace\ias-api-test\target\classes, -encoding, UTF-8, -extension, -Xnocompile, -B-Xcommons-lang, -B-Xfluent-builder, -B-Ximmutable, -b, C:\Users\drusdi1\workspace\ias-api-test\src\main\xjb\jaxb-binding.xml, -b, C:\Users\drusdi1\workspace\ias-api-test\src\main\xjb\jaxws-binding.xml, "file:/C:/Users/drusdi1/workspace/ias-api-test/src/main/resources/META-INF/wsdl/administration.wsdl"]
fluent-builder: Argument "-B-Ximmutable" not supported by "fluent-builder" plugin.

Usage: wsimport [options] <WSDL_URI>

where [options] include:
  -b <path>                 specify jaxws/jaxb binding files or additional schemas
                            (Each <path> must have its own -b)
  -B<jaxbOption>            Pass this option to JAXB schema compiler
  -catalog <file>           specify catalog file to resolve external entity references
                            supports TR9401, XCatalog, and OASIS XML Catalog format.
  -d <directory>            specify where to place generated output files
  -encoding <encoding>      specify character encoding used by source files
  -extension                allow vendor extensions - functionality not specified
                            by the specification.  Use of extensions may
                            result in applications that are not portable or
                            may not interoperate with other implementations
  -help                     display help
  -httpproxy:<proxy>        set a HTTP proxy. Format is [user[:password]@]proxyHost:proxyPort
                            (port defaults to 8080)
  -keep                     keep generated files
  -p <pkg>                  specifies the target package
  -quiet                    suppress wsimport output
  -s <directory>            specify where to place generated source files
  -target <version>         generate code as per the given JAXWS spec version
                            Defaults to 2.2, Accepted values are 2.0, 2.1 and 2.2
                            e.g. 2.0 will generate compliant code for JAXWS 2.0 spec
  -verbose                  output messages about what the compiler is doing
  -version                  print version information
  -fullversion              print full version information
  -wsdllocation <location>  @WebServiceClient.wsdlLocation value
  -clientjar <jarfile>      Creates the jar file of the generated artifacts along with the
                            WSDL metadata required for invoking the web service.
  -generateJWS              generate stubbed JWS implementation file
  -implDestDir <directory>  specify where to generate JWS implementation file
  -implServiceName <name>   local portion of service name for generated JWS implementation
  -implPortName <name>      local portion of port name for generated JWS implementation

Extensions:
  -XadditionalHeaders              map headers not bound to request or response message to
                                   Java method parameters
  -Xauthfile                       file to carry authorization information in the format
                                   http://username:password@example.org/stock?wsdl
  -Xdebug                          print debug information
  -Xno-addressing-databinding      enable binding of W3C EndpointReferenceType to Java
  -Xnocompile                      do not compile generated Java files
  -XdisableAuthenticator           disable Authenticator used by JAX-WS RI,
                                   -Xauthfile option will be ignored if set
  -XdisableSSLHostnameVerification disable the SSL Hostname verification while fetching
                                   wsdls

Examples:
  wsimport stock.wsdl -b stock.xml -b stock.xjb
  wsimport -d generated http://example.org/stock?wsdl

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.893 s
[INFO] Finished at: 2016-08-17T17:10:32+02:00
[INFO] Final Memory: 9M/150M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jvnet.jax-ws-commons:jaxws-maven-plugin:2.3:wsimport (default) on project ias-api-test: Mojo failed - check output -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
...

 But I need the immutability feature.
What am I doing wrong?
Regards,
Dimitrij

There seems to be something wrong in the way the argument line is parsed. The jaxws plugin seems to add a "-B" before every option, and that seems to cause problems. Maybe you could try a different order of the  options? I'll have a look at the code to see if it is a bug that can be fixed in the jaxb2-rich-contract plugin.

Before v1.16.0 of the plugin, everything is working as expected, without the need of reordering the arguments. Btw. reordering does not help.

Have you tried with version 1.17.0?

Sorry for the belated answer. Yes. 1.16.0 and 1.17.0 both lead to the same error. The error does not appear with 1.15.0 and below.

I've submitted the following pull request for this.

@martijn-van-tilburg It is only partially solved. Look into workaround in:
https://github.com/mklemm/jaxb2-rich-contract-plugin/issues/47
Gradle + Ant wsimport task + wsdllocation + fluent API fail with: "Argument
"-wsdllocation" not supported by "fluent-builder" plugin".
https://github.com/mklemm/jaxb-plugin-lib/issues/2
AbstractPlugin.parseArgument is greedy for options. This breaks wsimport utility.

Issue was fixed in 4.0.0 which requires prefixing all plugin command line options with the plugin name. See README.md


Update typings.d.ts

Accept AsyncStorage as storage when to use Typescript. AsyncStorage from react-native core will be removed on the next version and this lib use it as alternative.

Thanks!

Published  at 4.0.0


Istio CNI should ignore pods injected with istio-init

Since https://github.com/istio/istio/pull/17044, the istio-init container doesn't clean up the iptables chains at startup anymore. If Istio's iptables chains are already created before istio-init executes, istio-init now fails. This can happen in two cases: istio-init already executed but failed and is restarted by kubelet, or Istio CNI is installed and already initialized iptables.
The iptables initialization should be performed exactly once, since the initialization is not idempotent even with the chain cleanup that was previously done. Therefore, we should make sure that it is done exactly once in normal cases.
Therefore, Istio CNI should exclude any pod that has already been injected with an istio-init container. Currently, it injects any pod that has been injected, regardless of whether it has an istio-init container, cf. https://github.com/istio/cni/blob/774dea7a1d3872bff22c7dd06fd10a16be552301/cmd/istio-cni/main.go#L191-L231.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Version (include the output of istioctl version --remote and kubectl version)
master (due to https://github.com/istio/istio/pull/17044) and release-1.4 (due to https://github.com/istio/istio/pull/17989). Older releases are not affected.

@rlenglet @fpesce Do you mind if I work on this?

@abhide sounds good to me.

Thanks @rlenglet and @howardjohn. Will start taking a look.

Fixed by https://github.com/istio/cni/pull/218


update personal information

Update info for fengbeihong at t2cloud

Thank you for contributing to openstack/stackalytics!
openstack/stackalytics uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


usm: http2: Split http2_frame_parser to http2_headers_parser and http2_eos_praser

What does this PR do?
The PR splits the program socket__http2_frames_parser into socket__http2_headers_parser and socket__http2_eos_parser.
The program socket__http2_headers_parser will be responsible on processing HEADER frames.
The program socket__http2_eos_parser will be responsible on processing End Of Stream frames, and RST frames, including enqueuing streams on the perf-event mechanism.
The PR allows us to theoretically process up to 468 frames for a single packet, instead of a theoretical limit of 203 today.
Today we can parse (both headers and EOS) up to 7 frames in a single tail call, and we have 29 free tail calls, thus we can process 203 (7*29).
After the change, in socket__http2_headers_parser we can parse up to 18 frames in a single tail call, and we can have up to 26 tail calls, thus 468 frames in total. While for socket__http2_eos_parser we can parse up to 200 frames in a single tail call, and 3 tail calls can give us a limit of 600 frames in total. We take a minimal value and get 468 as an upper bound.
At the moment, we can parse up to 120 (the current limit), so we adjust the number of tail calls allowed per program to respect that limit (7 for socket__http2_headers_parser and 1 for socket__http2_eos_parser).

Motivation
The change serves us in 2 ways:

Allows to bump the frames limit for parsing (a current goal of us)
Reduces the complexity of socket__http2_frames_parser and allow us to add new code and features, without dealing with -EBIG from the verifier (as the program is too complicated for the verifer to track).

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


I went with alphabetically by surname as a way to sort people.
Yet more for #44

LGTM

Added the github handles.

Oh, I missed this! Can we highlight Chad & Zannah a bit more since they pretty much wrote the whole thing?

What about now?

R+ 💯 💃 👯

🚀+1

What is R+?

Positive review! Sorry, some internal lingo around code review. We finish a review with an R+/R-

👍 That wiki page doesn't explain r+/- I don't think, but I think I get it :)


How is this different then Modal?

Curious

Modal offers hosted compute, while Runhouse allows you to send your app to your own compute or cloud accounts. We actually plan to support Modal as a compute backend underneath Runhouse sometime soon. We're focused on different things. Modal is focused on fixing the cloud experience itself, including the DevX, while we're focused on allowing you to deploy and share backend apps anywhere. We spend most of our effort making it possible to deploy any python app to any infra, and bundle it with auth, certs, telemetry, automation, etc. such that it's production-grade and sharable out of the box. That also means that we're also a bit more aggressive about being agnostic to existing code (e.g. we don't use decorators or special call signatures), and care a lot about lineage, governance, and collaboration. Modal really shines on almost every aspect of the cloud experience - cold start times, scaling, deployment, etc. - so we're eager to integrate with it to offer the best of both of our platforms.


Add basic navigation functionalities

DO NOT ENABLE AUTO-MERGE
Planning to update some test cases after TypicalAddressBook is merged.
Implements the navigation functionalities
GoToCommand

[x]  Can only display 1 module at a time
[x] Input by user is case-insensitive
[x] Displays an empty list when module selected does not exist.

Possible Future work:
Cohesion with contact for v1.3
Consider other implementations of how an empty list should be handled
HomeCommand

[x] Returns unfiltered Module and Person list

Issues faced that needs to be discussed and fixed by v1.3

After filtering module list and person list, adding a module displays all the modules in the module list (unfiltered list) while person list remains unchanged
After filtering module list and person list, adding a person displays every person in the person list (unfiltered list) while module list remains unchanged

Possible issues that extends from issues indicated above

Adding tasks or links displays all the modules in the module list

Possible Solution:

Removal of updateFilteredPersonList and updateFilteredModuleList from addContact and addModule

Would like to hear your thoughts before implementing the solution proposed! 😄

You could just mark as draft, then nobody can enable auto-merge.

Codecov Report
Base: 71.20% // Head: 71.45% // Increases project coverage by +0.25% :tada:

Coverage data is based on head (82d745e) compared to base (ce6fb0f).
Patch coverage: 75.67% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #64      +/-   ##
============================================
+ Coverage     71.20%   71.45%   +0.25%
- Complexity      461      481      +20
============================================
  Files            82       87       +5
  Lines          1396     1433      +37
  Branches        145      150       +5
============================================
+ Hits            994     1024      +30
- Misses          364      371       +7
  Partials         38       38

Impacted Files
Coverage Δ

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
76.19% <0.00%> (-8.03%)
:arrow_down:

...ress/model/person/NameMatchesKeywordPredicate.java
0.00% <0.00%> (ø)

...java/seedu/address/logic/commands/GoToCommand.java
100.00% <100.00%> (ø)

...java/seedu/address/logic/commands/HomeCommand.java
100.00% <100.00%> (ø)

.../seedu/address/logic/parser/GoToCommandParser.java
100.00% <100.00%> (ø)

...odel/module/ModuleCodeMatchesKeywordPredicate.java
100.00% <100.00%> (ø)

...c/main/java/seedu/address/model/module/Module.java
78.72% <0.00%> (+2.12%)
:arrow_up:

...in/java/seedu/address/model/module/ModuleCode.java
81.81% <0.00%> (+9.09%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Yes indeed I should have uploaded it as a draft... AHAHAHA I've totally forgotten that GitHub provided such functionalities 😛


🐛 Bug Report: TS errors when running tsc:full with @types/react 17.0.58

📜 Description
yarn tsc:full currently produces compilation errors inside Mui when the installed version of @types/react is 17.0.58. To work around this issue, upgrade to 17.0.60 (I suspect 17.0.59 will work too).
👍 Expected behavior
Since the create-app package.json resolves @types/react versions to ^17, I'd expect any version compatible with that range to compile.
👎 Actual Behavior with Screenshots
With version 17.0.58, compilation errors are produced. Here's an example error:
node_modules/@mui/base/useTabs/TabsProvider.d.ts:18:71 - error TS2694: Namespace 'React' has no exported member 'JSX'.

18 export default function TabsProvider(props: TabsProviderProps): React.JSX.Element;

👟 Reproduction steps

Scaffold a new Backstage instance
Ensure the version of @types/react installed is 17.0.58
Run yarn tsc:full

📃 Provide the context for the Bug.
It looks like this is caused by Mui depending on the JSX namespace introduced to @types/react in https://github.com/DefinitelyTyped/DefinitelyTyped/pull/64464.
🖥 Your Environment
Observed the issue in a Github actions build.
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR! Would like to discuss options for fixing though. It seems like the simplest fix might be to update the resolution inside create-app to be more restrictive, but this won't help for existing instances. Perhaps worth also exploring whether it makes sense to open an upstream issue against Mui.

Potentially something to report to MUI, at least for the error you highlight in your example: https://github.com/mui/material-ui/blob/3cab2428c9ede4507c3040023aff31fd07eff76b/packages/mui-base/package.json#L44
That fix wouldn't help us because of the resolutions though. I think the way to go is to bump our resolution range to ^17.0.60 for @react/types. That'll at least make it visible for anyone keeping an eye on the upgrade helper, while the rest that run into this issue would hopefully find this issue or simply bump @react/types themselves. Don't think there's a lot else we can do here, no way to ship this to existing projects without manual intervention.


Fix 508 compliance issue when there are no CMS records

Closes #1086
Saw a minor bug on the deployed version. This should be a small fix to get it back to compliant

:+1:


manpages in releases

would be nice

Sure.

The HTML version of the man pages is included in the releases now.


Generate AST from code

What's done:
Build code from text and generate a sub tree.
closes #167

Another important task for this parser is ability to insert generated nodes into AST provided by framework. Actually, this is the main goal we had starting this.

@kentr0w did you fix this? create an issue if not


Cannot sign in with AD account(SSO)

Type: Bug

Log into a company account in Windows
Click Account icon, choose "Sign in to sync settings"
In the pop-up window, choose the account you already logged in
It says "You are signed in now and can close this page."

I'm not sure, how do I verify with the Microsoft Authentication output?
I do have a corporate proxy/VPN and that comes along with the AD account. But the problem is, I was able to log in initially right after VS code got installed, but when I tried sign off, and sign in again, this issue happened.
@8ueye8 I do see the same error message pop up. ('Network failure'.)

No VPN's that I know of were active at the time. There may be a corporate proxy in the background but that shouldn't be an issue since I was able to login before on my previous laptop. The issue only started when I was issued a new laptop and tried to login and sync my settings.

No VPN's that I know of were active at the time. There may be a corporate proxy in the background but that shouldn't be an issue since I was able to login before on my previous laptop. The issue only started when I was issued a new laptop and tried to login and sync my settings.

In my case I logged in succesfully and actualy automatically when I first install VS code to my machine. It only happens when I logged out and try to log back in.

I have the same issue, also on a company account. I see this error in the logs:

I have a same issue too.In my company PC,I can sign success with Microsoft AD;Bug in my own PC,I can't sign.

I've resolved this issue by reimaging by PC with Windows 10, signing in and then upgrading to Windows 11. I know it's not the best solution but hopefully helps diagnose the issue.
When I previously encountered the issue, I had just reset the laptop from within Windows 11 and tried to sign in once the reset was done.
Maybe it's a Win10 vs Win11 issue?

I can't reimage my system as I'm running a corporate system, rebuild will lose everything. It acquired the login successfully in the initial try, but failed in the following attempts. If it succeeded once, it should have no permission issue. When it failed in the second attempt, maybe it was looking at the wrong plate? I mean for the authorization process.

Do you have any proxy-related settings set in VS Code? Do you have a system environment variable like HTTP_PROXY set?

I have the same issue, also on a company account. I see this error in the logs:

@8ueye8 "certificate has expired" suggests that you have an old certificate in the root certificates registered with your OS (or it is part of the built-in certificates in Electron). Could you try opening https://login.microsoftonline.com/ with the Edge browser (to see if it connects, this might also update the root certificate in the OS, not sure if other browsers would do that) and then retry?

I have the same issue, also on a company account. I see this error in the logs:

@8ueye8 "certificate has expired" suggests that you have an old certificate in the root certificates registered with your OS (or it is part of the built-in certificates in Electron). Could you try opening https://login.microsoftonline.com/ with the Edge browser (to see if it connects, this might also update the root certificate in the OS, not sure if other browsers would do that) and then retry?

As I mentioned earlier, I resolved my issue when I reimaged my device. https://login.microsoftonline.com/ worked for me on edge when I had the issue.

Some other proxy related ideas: https://github.com/microsoft/vscode/issues/160649#issuecomment-1489176027

I have tried https://github.com/microsoft/vscode/issues/160649#issuecomment-1489176027
And checked my environment variables with nothing there. Still cannot login to GitHub, but my MS account works fine.

@MH-ABE would you mind trying out @chrmarti's proxy debugging extension:
https://github.com/microsoft/vscode-remote-release/issues/8248#issuecomment-1494127068
and let me know how it goes

Certainly @TylerLeonhardt, here is the output:
Settings: (Let me know if I need to test other settings)
- http.proxy:
- http.proxyAuthorization: null
- http.proxyStrictSSL: true
- http.proxySupport: off
  - globalValue: off
- http.systemCertificates: true

Environment variables:

Sending GET request to https://containers.dev/static/devcontainer-index.json...
vscode-proxy-agent: DIRECT
Received error: unable to get local issuer certificate

Sending GET request to https://containers.dev/static/devcontainer-index.json (allowing unauthorized)...
vscode-proxy-agent: DIRECT
Received response code: 200
Certificate chain:
- Subject: containers.dev
  Subject alt: DNS:containers.dev, DNS:www.containers.dev
  Validity: Mar 22 19:22:30 2023 GMT - Jun 20 19:22:29 2023 GMT
  Fingerprint: 28:F2:4F:7A:Bxxxxxxxxxxxxxxxxxxx
- Subject: gk-de-hub
  Subject alt: DNS:gk-de-hub
  Validity: Jun 25 11:52:11 2021 GMT - Nov 29 00:41:25 2025 GMT
  Fingerprint: 63:47:BF:FC:CD:xxxxxxxxxxxxxxxxxxxxxxxxxxx
  Issuer certificate not found: mhsca (<- looks like the company CA)

@MH-ABE This looks like we don't pick up your company's CA up from the OS. Which OS are you on? Could you check if and where the company's CA is registered in the OS?

@chrmarti Im on Windows_NT x64 10.0.19044 and we use Edge.
I can see the company root cert in certmgr.msc, and mhsca is an intermediate CA. Hope that answers your question, otherwise let me know where to look.
Thanks

@MH-ABE Could you update the Network Proxy Test extension to the latest version (0.0.3) and run F1 > Network Proxy Test: Show OS Certificates to see if that certificate is loaded from the OS?

mhrca: found
mhsca: not found
gk-de-hub: not found
Probably best to send the full list privately?
Cant find most of these intermediate CAs in the test output:

Make sure you have the last one in the chain mhrca in the Trusted Root Certification Authorities ("Betrodda rotcertifikatutfärdare" I guess).

I cannot move them, access denied. I don't think IT want people messing with the certs ;) Any other way I can get them to the right place?

Can you export them (context menu on the cert > All Tasks > Export...) and then import (context menu on Trusted Root Certification Authorities > All Tasks > Import...) them?

@MH-ABE Looking at it again, I would expect mhrca to also be in the Trusted Root Certification Authorities (I think the browser would otherwise complain). Could you check again?
The certificate chain you posted in https://github.com/microsoft/vscode/issues/177139#issuecomment-1495439725 suggests that the (transparent?) proxy you are are connecting through did not send the full certificate chain. Browsers seem to handle this more gracefully than Node.js. Could you check with your IT if this is true and if they could change that to be the full certificate chain?

@chrmarti mhrca is in the TRCA folder, and it is picked up by your test plugin. Seems to be doubled up since its in the intermediate folder too.
Export worked fine, but it seems that the root folder is write protected so the import failed.
I did manage this eventually, I had been using certlm.msc now I tried certmgr.msc but I also only moved the specific intermediate only certs and not all of the company ones in the intermediate folder. Don't know what solved it, but in any case I cannot overwrite existing certs but am able to add new ones to the root folder.
So when trying to login to GitHub in VSCode now with the intermediate certs also in the root folder, it works!
I don't know a lot about CAs, but this intermediate cert folder seems like a standard use, right? Would it be possible for VSCode to also import this folder? Unless of course it is only my company doing it this way.
Thanks for your assistance!
TLDR; If you can't login due to CAs, move relevant intermediate certs to the root folder using certmgr.msc.

The discussion at https://security.stackexchange.com/a/72085 makes me think that it would be best for your proxy to return the complete certificate chain (the root certificate may be omitted from what I understand).
We could improve our client implementation by also using the trusted intermediate CAs from the Windows credential store, but going by https://learn.microsoft.com/en-us/answers/questions/882257/revoked-certificate-shows-as-valid-in-the-certific, we would have to use certutil to make sure revocations are applied.


Add Stream count

#129

This apparently does the same thing as #368 .
I want to give priority to the one submitted first, but is there any objection?

@k-nasa no objection; both PRs are really good, but sadly we can only merge one.


CAS in the granularity of file

I'd like to propose an alternative image layer format that is content-addressable in the granularity of file, rather than in the granularity of tar.
(Of course not proposing for image-spec v1.0.0 :-), just a baby step toward the future spec)
This is a continuation of the previous discussion about lazy-pulling.
Now I refined my proposal focusing on CAS in the granularity of file, rather than just sticking to lazy-pulling.
CAS in the granularity of file also has a benefit of higher concurrency in pulling images.
For distribution, even though I prefer IPFS, I intentionally kept my idea agnostic to a certain distribution method (which is out of scope of OCI mission currently).
Proposal
TLDR: Just use @stevvooe 's continuity instead of tar.
Regular files would be stored as OCI blobs and accessed via the digest value recorded in the continuity manifest.
For the whole idea, please refer to
https://github.com/AkihiroSuda/filegrain/tree/v20170217

My answers to @cyphar 's questions at ML ( https://groups.google.com/a/opencontainers.org/d/msg/dev/ocsaii6-P0k/0QcwrF3wCgAJ )

Now I refined my proposal focusing on CAS in the granularity of file,
rather than just sticking to lazy-pulling.
CAS in the granularity of file also has a benefit of higher
concurrency in pulling images.

But also higher latency if you have many small files.

A continuity layer and traditional tar layer can be composed together.
So you can put many small files into a single traditional tar.

For distribution, even though I prefer IPFS, I intentionally kept my
idea agnostic to a certain distribution method (which is out of scope
of OCI mission currently).

As an aside, distribution is something that we're already having trouble
coming to a decision on (and it's something that is being held out of
scope, which is leading to fragmentation of distribution methods). So
note that if your proposal includes some distribution method, expect it
to be delayed for a while longer. ;)

So, I intentionally omitted distribution method from my proposal. :smile:

The idea is interesting, and it would be nice to get away from tar
archives. However, my main concern with this idea is that it means you
can no longer easily be certain you have all of the blobs you need for
an image to be "complete" -- in other words the image is no longer
self-contained.

Please elaborate?
Isn't it just achieved by parsing continuity manifest file? (Maybe its format should be JSON rather than PB for ease of implementation?)

How do you envision this scheme working for usecases where network
access is not possible, or is otherwise restricted? What happens if the
blob store you're pulling from goes offline -- how will you get your
file blobs when ImageStore Inc. eventually goes bankrupt or gets acquired?

This is not a new issue w.r.t. non-lazy pulling.
For lazy-pulling, network failure would result in EIO.
If you fear ImageStore Inc, can shutdown, you can use IPFS or something similar.

There's also the question of how will you store the history of an image
-- are diff layers something that you would want?

You can just use continuity as diff layers (requires on-going PR by @dmcgowan https://github.com/stevvooe/continuity/pull/39#issuecomment-270580840).
However, since having many continuity layers is redundant, maybe it should be better to have annotation field for representation of the history.

Another valid concern is that this will make "simple" distribution of
OCI images (something I've been working on recently, to see if you can
effectively package all of the blobs as separate .rpm or .deb packages)
quite difficult. On the SUSE side, getting maintainence to approve
several thousand packages containing a single file is not going to
go over well :wink:.

Could you please elaborate why you need to build RPMs for each of blobs?

@AkihiroSuda

Please elaborate?
Isn't it just achieved by parsing continuity manifest file? (Maybe its format should be JSON rather than PB for ease of implementation?)

Yes you're right. I misunderstood your initial proposal as being effectively "put links where blobs used to be so that you fetch everything". What you're actually proposing is that we have another level of manifest (continuity or whatever else) and then you still use the old blob store but store many more blobs inside it. For skopeo (or eventually umoci pull) this would involve some sort of recursive parsing to find all blob references and then pull everything necessary -- which is totally fine and to be expected.

However, since having many continuity layers is redundant, maybe it should be better to have annotation field for representation of the history.

I'd be a bit hesitant about using annotations for history representation, because of their limited scope (they can only be JSON strings). But if we adopt this sort of proposal in the future I would expect that it would be implemented with some sort of descriptor tag describing the history of the thing referenced -- sort of like Camlistore's history model (though without requiring an indexer).

Could you please elaborate why you need to build RPMs for each of blobs?

This is for the actual distribution of OCI images, not for the internal representation. The argument from my side is that distribution was solved ~20 years ago with the various distribution formats, and it would be great if we could just use the existing infrastructure for sending around OCI images. In order to achieve deduplication (the whole reason diff layers exist) you need to split up all of the blobs into separate RPMs so that each RPM is only installed once.
I'm planning on hacking on this idea near the end of March. The idea would be to make this as agnostic to package format as possible so that everyone can use it. CoreOS already has something similar for their image distribution, but I would like to leverage existing package formats rather than coming up with my own.

On Fri, Feb 17, 2017 at 12:50:16AM -0800, Akihiro Suda wrote:

For distribution, even though I prefer IPFS, I intentionally kept my
idea agnostic to a certain distribution method (which is out of
scope of OCI mission currently).

IPFS-the-ecosystem is build out of several layers 1.  The data
model, which is distribution agnostic, is only one of those layers
(and the IPFS folks are in the process of peeling it off into a
stand-alone spec with IPLD 2).  The (poorly documented) filesystem
model is another layer on top of the generic IPLD framework 3.  If
the current unixfs models don't cut it for you (e.g. poor metadata
support), you can recycle a lot of existing IPFS-ecosystem groundwork
by proposing a different/improved unixfs model on top of the existing
IPLD base, and easily share and transport those blobs via the existing
IPFS ecosystem or alternative naming/exchange/routing/network
implementations.
In the OCI ecosystem, there is also work towards supporting generic
transports (e.g. containers/image#125, containers/image#216).  There's
no base data model that I'm aware of here, although SHOULDing
descriptors for references 4 is a step in that direction (e.g. you
can automate most graph walking if you trust things which look
descriptor-ish to be Merkle links 5).
To me it seems like these are parallel efforts which would benefit
from more cross-pollination.  But without agreement on the base model
(the thing that gets hashed for content addressability), clients can't
swap blobs back and forth between the two systems and stay content
addressable.  So thinking the IPLD model is tied to a particular
distribution method is not a good reason to be dropping it, but “I
need something which I can distribute via existing OCI CAS
implementations and which can be walked by a descriptor-sniffer” may
be.

@AkihiroSuda Is this something that we need for milestone==v1.0.0 or could this be considered for milestone==post-v1.0.0 ?

@AkihiroSuda This is post 1.0.

Update: I implemented an initial POC of this: https://github.com/AkihiroSuda/filegrain/tree/v20170504
Your feedback is welcome :smile:

general: https://github.com/AkihiroSuda/filegrain/issues would be preferred
something needs to be worked on this image-spec repo: this github issue

Usage
Build a FILEgrain image from a raw rootfs directory:
$ filegrain build /tmp/raw-rootfs /tmp/filegrain-image

Mount the image with lazy-pulling:
(This is not practically useful ATM because the image already exists on the local filesystem. In future, it should support remote registry of course. Anyway, using a local image here seems enough for POC.)
$ filegrain mount /tmp/filegrain-image /tmp/bundle/rootfs

You can run runC with this bundle, without waiting for all the blobs to be "pulled".
Experimental result (using docker.io/library/java:8)

Full image size (uncompressed): 633 MB
Blobs needed for running sh: 4.4 MB
For java -version: 87 MB
For javac Hello.java: 136 MB

ohman
On Wed, May 3, 2017 at 1:28 PM, Akihiro Suda<EMAIL_ADDRESS>wrote:

Update: I implemented an initial POC of this: https://github.com/
AkihiroSuda/filegrain/tree/v20170504
Your feedback is welcome 😄

general: https://github.com/AkihiroSuda/filegrain/issues would be
preferred
something needs to be worked on this image-spec repo: this github
issue

Usage
Build a FILEgrain image from a raw rootfs directory:
$ filegrain build /tmp/raw-rootfs /tmp/filegrain-image
Mount the image with lazy-pulling:
(This is not practically useful ATM because the image already exists on
the local filesystem. In future, it should support remote registry of
course. Anyway, using a local image here seems enough for POC.)
$ filegrain mount /tmp/filegrain-image /tmp/bundle/rootfs
You can run runC with this bundle, without waiting for all the blobs to be
"pulled".
Experimental result (using docker.io/library/java:8)

Full image size (uncompressed): 633 MB
Blobs needed for running sh: 4.4 MB
For java -version: 87 MB
For javac Hello.java: 136 MB

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/opencontainers/image-spec/issues/577#issuecomment-298979714,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEF6SzdAdeHczaiynx6259m7IVqNrPsks5r2LlVgaJpZM4MEA1T
.

Originally I designed this proposal to be agnostic to distribution protocols, because the standardization of distribution was out of the scope of OCI's mission at that time.
But the situation has changed now, and I think I found alternative way, although it is specific to Docker/OCI registry API: https://github.com/AkihiroSuda/filegrain/issues/21


Improve the UI. Currently the UI only shows plain texts.

Close in favor of https://github.com/0xkarl/vite-extension/issues/27


fix: use correct custom properties for table t-shirt sizing

Description
This fixes a slew of incorrect custom properties which changed due to the addition of t-shirt sizes.
Additionally, this adds:

New examples for compact and spacious
A new example for small

How and where has this been tested?

Manually visually compared against the existing production site.
Visual regression tests are a bit unhelpful because the HTML examples did not have the correct IDs when the baseline snapshots were generated, and the addition of new examples throws off all of the snapshots by one test.
This change also impacts the ActionBar's example, so I've manually checked my changes there, as well.

To-do list

[X] If my change impacts other components, I have tested to make sure they don't break.
[ ] If my change impacts documentation, I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.

[ ] This pull request is ready to merge.

@pfulton


bower.json main is incorrect in release 3.7.0

The main was updated from src to dist, but the bower release file structure was never updated.
Thanks,
Max
{
  "name": "ngQuill",
  "version": "3.7.0",
  "main": ["dist/ng-quill.js"],
  "description": "AngularJS directive for the QuillJS rich text editor",
  "authors": [
    "Bengt Weiße<EMAIL_ADDRESS>  ],
  "ignore": [
    "bower_components",
    "node_modules",
    "spec",
    "demo.html",
    "package.json",
    "Gruntfile.js"
  ],
  "dependencies": {
    "quill": "^1.1.5",
    "angular": "^1.5.8"
  },
  "keywords": [
    "quill",
    "rich text",
    "angularjs",
    "angular",
    "directive",
    "editor",
    "wysiwyg"
  ],
  "license": "MIT"
}

I Do Not care about bower.  This change were made by PR. Change it back and
send me a PR and IT will be There This evening ;)
finneym<EMAIL_ADDRESS>schrieb am Fr., 13. Apr. 2018, 16:23:

The main was updated from src to dist, but the bower release file
structure was never updated.
Thanks,
Max
{
"name": "ngQuill",
"version": "3.7.0",
"main": ["dist/ng-quill.js"],
"description": "AngularJS directive for the QuillJS rich text editor",
"authors": [
"Bengt Weiße<EMAIL_ADDRESS>],
"ignore": [
"bower_components",
"node_modules",
"spec",
"demo.html",
"package.json",
"Gruntfile.js"
],
"dependencies": {
"quill": "^1.1.5",
"angular": "^1.5.8"
},
"keywords": [
"quill",
"rich text",
"angularjs",
"angular",
"directive",
"editor",
"wysiwyg"
],
"license": "MIT"
}
https://user-images.githubusercontent.com/4526874/38739885-13a9dbec-3f2e-11e8-83c6-4b1e6369f6b1.png?raw=true
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/KillerCodeMonkey/ng-quill/issues/154, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACKOYFs69jgwrPU8m4gD4Z7VVhcFepadks5toLT6gaJpZM4TTiff
.

I did Not dist Folder. I have a build process so You are using npm only the
dist Folder is published. A Sourcecode repository should only Contain the
plain Sourcecode.
I Do Not have that possibility with bower :)
Am 14.04.2018 9:18 nachm. schrieb "Rui Freitas"<EMAIL_ADDRESS>Yeah I also noticed that when I update the version to the latest. May I ask
why you decided to remove the dist folder/min version?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/KillerCodeMonkey/ng-quill/issues/154#issuecomment-381353381,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACKOYFZFxU2rlWUsgMT1Roke8hKvx9cbks5tokt7gaJpZM4TTiff
.


Getting bot material but just not working. please help

I'm trying to calculate the material advantage the bot has and the method returns -78 at the start and adds each value after any piece is captured (So when any knight is captured it return -75).
I tried making 2 variables for white and black materials and subtracting them from each other but it returned the same thing.
I also tried switching += and -= but that just makes it 78 instead of -78.
    private int CalculateMaterial(Board board, bool botsTurn)
    {
        int netMaterial = 0;

        foreach (PieceList list in board.GetAllPieceLists())
        {
            if (list.TypeOfPieceInList == PieceType.Pawn)
            {
                if (list.IsWhitePieceList && BotIsWhite(board, botsTurn))
                {
                    netMaterial += 1 * list.Count;
                }
                else
                {
                    netMaterial -= 1 * list.Count;
                }
            }
            if (list.TypeOfPieceInList == PieceType.Knight || list.TypeOfPieceInList == PieceType.Bishop)
            {
                if (list.IsWhitePieceList && BotIsWhite(board, botsTurn))
                {
                    netMaterial += 3 * list.Count;
                }
                else
                {
                    netMaterial -= 3 * list.Count;
                }
            }
            if (list.TypeOfPieceInList == PieceType.Rook)
            {
                if (list.IsWhitePieceList && BotIsWhite(board, botsTurn))
                {
                    netMaterial += 5 * list.Count;
                }
                else
                {
                    netMaterial -= 5 * list.Count;
                }
            }
            if (list.TypeOfPieceInList == PieceType.Queen)
            {
                if (list.IsWhitePieceList && BotIsWhite(board, botsTurn))
                {
                    netMaterial += 9 * list.Count;
                }
                else
                {
                    netMaterial -= 9 * list.Count;
                }
            }
        }

        return netMaterial;
    }

    private bool BotIsWhite(Board board, bool botsTurn)
    {
        if (board.IsWhiteToMove && botsTurn)
        {
            return true;
        }

        return false;
    }

what is botsTurn?

A variable saying if it's the bots move

I think the problem is that you wrote (list.IsWhitePieceList && BotIsWhite(board, botsTurn)) while if you want to add when it's the bot's move then you should do (list.IsWhitePieceList==board.isWhiteToMove).
Aldough I whould not recomend doing it this way, because it requires a lot of tokens.
This code for example does the same:
int[] pieceValues = {0,1,3,3,5,9}
int eval = 0;
foreach (PieceList pieces in board.GetAllPieceLists()){
   eval += pieceValues[(int)pieces.TypeOfPieceInList] * pieces.Count * (pieces.IsWhitePieceList==board.IsWhiteToMove ? 1 : -1);
}

return eval;

Thanks, that worked


How do I get forward to the task

Problem Description
As we known, we can use CTRL+Z to make our operations back. How can we use an opposite approach to make operations forward.

Versions

Spyder version: 4.0.0
Python version: 3.6.8
Qt version: 5.9.7
PyQt version: 5.9.2
Operating System name/version: Ubuntu16.04

Dependencies

PASTE DEPENDENCIES HERE

You need to use Ctrl+Y.


Convert res to JSON by default

All other libraries have it, it's just another step that people have to do, and change it by default can save time and code length if someone is making many requests.

No.
We are following the fetch specification.
And everything is not json.

Oh ok. 🦄


Create flanneld config file with using SNAP_DATA env variables

Currently args/flanneld is being created with a the fixed path of the currently installed snap. Ex:
--iface=""
--etcd-endpoints https://<IP_ADDRESS>:12379
--etcd-cafile /var/snap/microk8s/982/certs/ca.remote.crt
--etcd-certfile /var/snap/microk8s/982/certs/server.remote.crt
--etcd-keyfile ${SNAP_DATA}/certs/server.key
--subnet-file=${SNAP_COMMON}/run/flannel/subnet.env

The paths for --etcd-cafile and --etcd-certfile become invalid after the snap upgrades and flanneld fails to start.

Thank you for spotting this issue and working on the PR @strigona-worksight


mcuboot-related STM32 fix

This series helps Zephyr be chain-loaded by mcuboot on STM32 again. (This is currently broken on at least 96b_carbon for multiple reasons, some of which need to be addressed in other pull requests).

An implementation which was trying to be more careful about power management might track whether HSI was turned on to serve as SYSCLK source while the PLL was configured, and turn it back off again after switching to the PLL if the PLL's source was HSE or some other non-HSI clock.
I thought about doing that, but it's not clear to me what Zephyr's PM plans are, and I thought I'd keep this simple for now. Please let me know if that was the wrong call.

Minor comment fix, otherwise looks good

Thanks for the reviews; now updated.


Generation 2 in Azure reference added

@MikeBazMSFT Please fix merge conflict and I will approve and publish this pull request.  Thanks!

Hmm.  Generation 2 is still only preview as far as I know, which makes the use of "supported" in the other version potentially problematic.  But the two are basically saying the same thing so I'm not sure my change makes sense now, two months after proposing it, so I'm going to close and let the existing version stand.


add alias grmi, rm files from ignore file

add alias grmi
rm files but still tracked. it's useful when update ignore file.

Too niche and too infrequent. You can put it in your zshrc file though.


Separate SMTP and IMAP servers

Hello,
I would like this configuration: two different servers/nodes, one handling the outbound mail (Postfix) and one the inbound one (Dovecot).
Would it be possible, using this Docker instance, or at least to only have the outbound one?
If you point me in the correct direction, I could work on it and try to document the steps to achieve it.

Sorry, I noticed only later another question about it: https://github.com/tomav/docker-mailserver/issues/1692
Anyway, I was asking for a Swarm Docker solution, not K8.


Exception when try to save kafka avro data into clickhouse

i tried to use this connector to save kafka topic data into clickhouse with kafka connector,  encountered below exceptions.
Caused by: java.lang.NullPointerException\n\tat com.clickhouse.kafka.connect.sink.db.ClickHouseWriter.validateDataSchema(ClickHouseWriter.java:150)\n\tat com.clickhouse.kafka.connect.sink.db.ClickHouseWriter.doInsertRawBinary(ClickHouseWriter.java:266)\n\tat com.clickhouse.kafka.connect.sink.db.ClickHouseWriter.doInsert(ClickHouseWriter.java:128)\n\tat com.clickhouse.kafka.connect.sink.processing.Processing.doInsert(Processing.java:45)\n\tat com.clickhouse.kafka.connect.sink.processing.Processing.doLogic(Processing.java:102)\n\tat com.clickhouse.kafka.connect.sink.ProxySinkTask.put(ProxySinkTask.java:80)\n\tat com.clickhouse.kafka.connect.sink.ClickHouseSinkTask.put(ClickHouseSinkTask.java:60)\n\tat org.apache.kafka.connect.runtime.WorkerSinkTask.deliverMessages(WorkerSinkTask.java:584)
kafka-avro-console-consumer can consume the data from the topic, and the data shows like
{"entity":"Random1","v":0.5467754725010544}
my kafka connector config is
{     "connector.class": "com.clickhouse.kafka.connect.ClickHouseSinkConnector",     "tasks.max": "1",     "topics": "simulation",     "ssl": "false",     "hostname": "clickhouse-db",     "database": "sampledatabase",     "port": "8123",     "exactlyOnce": "false",     "username": "default",     "value.converter": "io.confluent.connect.avro.AvroConverter",     "key.converter": "org.apache.kafka.connect.storage.StringConverter",     "value.converter.schema.registry.url": "http://schema-registry:8081" }
Did i miss something for the whole solution?

I looked into the source code, and found the root cause is the type mismatch, Also in com.clickhouse.kafka.connect.sink.db.mapping.Column, it only includes only a few types in clickhouse.
If there's some avro type and clickhouse type mapping document, it will be helpful for the user.

configuration issue, not a bug, maybe should deliver an enhancement

configuration issue, not a bug, maybe should deliver an enhancement

@licongchao what would you suggest adding to the documentation to improve the user experience?

@mshustov Cause Avro has only a few Primitive Types, but there's lots of data types in ClickHouse. If these types are ignored when using, exceptions will occur according to the current implementation.
It has several possible solutions, the first one is to mapping all types within ClickHouse data type. but i think it will cause lots of efforts. The second one is to point out which data types in ClickHouse is already implemented. The root cause of my exception is UINT64 which i'm using but it hasn't been covered, and it cannot pass the data schema validation.
Hope it works, the connector is helpful. thank you.

The only types currently not supported by the Sink are bytes & struct as value. We introduce some implicit conversions within Dates see #63 issue [#57]. If you see any other need to implicit conversions, please open an issue, and we will address it.


Demo

A live running demo/example of this would be great. It should help visualize what is going on.

@jpadilla let me know if you want any help setting it up? Ive set up a few drf/ember-cli projects on heroku now using this.. not too painful

@erichonkanen before actually doing anything I'd like to figure out what would help others understand JWT + Authentication in general using this package and djangorestframework-jwt and figure out how we can visually demonstrate how it works.

For JWT, showing the contents of the token would be a big plus. I like what http://jwt.io/ does in terms of visualising the content bit of the token.

First attempt at this using a dummy app.
https://jpadilla.github.io/ember-cli-simple-auth-token/

@jpadilla looks good... are you using CORS for that? just curious bc I notice the OPTIONS pre-flight request... on my heroku apps I have been using proxy between backend django / client ember.. interested to know how you set that up...
as far as the blacklist subapp PR, a simple demo of it could be as easy as a button to blacklist yourself which makes the request to auth-token-blacklist endpoint (should log you out after next refresh attempt)... Or if you have another idea to tie it in let me know... The use case I described previously could be expanded to when you need to ensure someone's access is revoked immediately

@erichonkanen yea using CORS. The API is just a simple express app that mimics what we're doing for the mock endpoints here. For Django, you might want to try using django-cors-headers.
That sounds good. I'll probably write a demo based on this that uses DRF+JWT so we can try out the new things including blacklisting. Will try to do that this weekend.

@jpadilla sounds good... let me know if I can help with anything.. it's interesting Im working on a new project using microservices and the topic of blacklisting came up and I got input that it'd be useful although as someone on the drf thread stated it might be difficult in a services architecture.. I think since it's an optional feature and just has a base implementation, it leaves it open ended

@erichonkanen feel free to take this one if you'd like. I haven't had as much time as I'd hope for it. IM me if you want to chat about it.

@jpadilla which version of this package is the demo using? if it is using the latest tagged release 0.7.2 with ember-simple-auth 0.8.0-beta.2+ then that might clue me in that my local test app is broken in relation to the ongoing issue with restore


paginate triggers when filters by a given service

When select page 2, we are going on page 2 off all the triggers

fixed de6478dda0aef7a19e58ac024d9c253ff4548242


Fix for StoredValue::ContractPackage not json-deserializable

Fixed issue with StoredValue::ContractPackage variant being not json-deserializable. The underlying issue is that a Map in the structure is using a tuple as a key, which serde doesn't know how to turn into json. This functionality was in place before but it seems to be lost in the 2.0 transition.
Also renamed BytesDeserHelper to HumanReadableDeserHelper and BytesSerHelper to HumanReadableSerHelper since those helper structures are only used in case of serializing to a human-readable format, not a byte representation.

bors merge


Add Time Axis only when time related chart is opened

Signed-off-by: muddana-satish<EMAIL_ADDRESS>