Xlm didn't get deposit

Hi
I try to moved 60.8459314 xlm from WazriX to CODEBASE but I gave the wrong memo and till now it didn't got credit into my codebase account

Please help me the right address will be
GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37
Memo I'd
4028278296
Please help me

Hello,
It's impossible to change the memo once the transaction is submitted.
You need to contact the Coinbase support team and provide a link to your
transaction. They can process your deposit manually.
Regards,
OL
On Wed, Dec 16, 2020 at 9:46 PM smsyed1982<EMAIL_ADDRESS>wrote:

Hi
I try to moved 60.8459314 xlm from WazriX to CODEBASE but I gave the wrong
memo and till now it didn't got credit into my codebase account
[image: Screenshot_2020-12-17-01-14-31-324_com wrx wazirx]
https://user-images.githubusercontent.com/76127461/102398398-3d285680-4005-11eb-9ff6-64424ce7a36a.jpg
Please help me the right address will be
GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37
Memo I'd
4028278296
Please help me
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/orbitlens/stellar-expert-explorer/issues/265, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBJTML6NZIIN4EDYOERSN3SVEFATANCNFSM4U6P4NKQ
.


Fix sourceTree of RCTActionSheet.xcodeproj

File not found occurs in AppCode.
sourceTree of RCTActionSheet.xcodeproj is <absolute>. Because path is ../../Libraries/ActionSheetIOS/RCTActionSheet.xcodeproj, that sourceTree is wrong.
Closes #338

Merged internally, thanks! Should be out with next sync


fix(plugin-ledger-connector): Some of the plugin-ledger-connectors are using wrong Interface  Types in their class definitions

Describe the bug
Some of the plugin-ledger-connectors are using wrong Interface  Types in their class definitions where the types for the deployContract() and the transact() functions are getting defined.
To Reproduce
In plugin-ledger-connector-quorum for example the class definition needs to implement "IPluginLedgerConnector<
DeployContractSolidityBytecodeV1Request, DeployContractSolidityBytecodeV1Response,
RunTransactionRequest, RunTransactionResponse >" but the deployContract() is using DeployContractSolidityBytecodeV1Request and RunTransactionResponse instead of the interface definition pair DeployContractSolidityBytecodeV1Request, DeployContractSolidityBytecodeV1Response.
Similar is the case for the besu connector.
Expected behavior
For all the connector class definitions the implementation needs to follow their interface definition and need to match in consistent way for all the connectors.

@m-courtin Sounds good to me. My only nit: keep branches all lower-case if possible. (some git tooling/operating systems do not take kindly to certain edge cases that stem from mixed-case branch names)


lack of dedicated timer for ngx_resolver

Makes resolver to hang forever on failure

Fixed, test case in t/01-resolver.t.
Similar issue with SSL got fixed as well. No test case yet though.


[LS] KXI-36337, KXI-36622, KXI-36758, KXI-36708, KXI-36571

Changes introduced by this PR

KXI-36337: Comment colorization issues
KXI-36622: Linter: Declared after use false positive
KXI-36758: The extension includes GPL code
KXI-36708: All variables in square brackets are parsed as parameters
KXI-36571: Linter: This param was declared then never used

for: KXI-36337, still happening with functions

There are tickets listed in this PR that aren't solved

There are tickets listed in this PR that aren't solved

36708 is about “This param was declared, then never used” it is fixed, the new hint is true it is not used as ordinary variable.


feat(observe-content): refactor so logic can be used without directive

Comments addressed. I also removed the part where we observe outside the zone. I think if it's a public API that returns an Observable, users will probably expect that Observable to emit inside the zone. Does this make sense to you guys?

PTAL

@jelbourn I moved the @Output() back outside the zone for now. This can be re-presubmitted


Integrate webpack bin

Have we talked about integrating webpack bin yet? I think it would be cool to get an interactive playground on the site without needing to install anything. We talked about that a little bit at #32 already.
Maybe @christianalfoni wants to join that discussion?

Related commentary: https://github.com/webpack/webpack.js.org/pull/222#issuecomment-253502068 .

If you check #222, you can see we can get something limited fairly easily up and running. It's not the same, but I have a feeling it would get us close to a cool solution without having to rely on a third party service and while keeping it light.

(Sorry, I forgot that I mentioned it already ^^. I searched for webpack bin in our issues but couldn't find anything)
Can you bundle webpack with webpack 😀 ?

If anyone wants to see a quick example of what webpackbin would look like on the splash page, or maybe in Getting Started would be better, you can grab the iframe that I removed in 2c6c1563609 to get a general idea. I know we don't want to go with an <iframe> long term but it just gives a rough idea of what an embed might look like.
If we do decide to go custom, I think we'd just have to flesh out what @pksjce did in #222. I like the idea of a simple, relatively static example on the splash/landing page (like we have) with a more robust, possibly interactive example in Getting Started.

What would you think if we skipped this one? There are tons of open issues and webpackbin would require update to webpack 2 for this to make any sense.
It would be likely smarter for us to build something limited for demonstration purposes like @pksjce did earlier. We can get something interactive going.
In any case this is a secondary issue.

Would definitely work on this if the decision made is favorable!

Closing this for now as we've moved away from this idea a bit. I really like webpackbin and am even starting to use it instead of codepen from time to time, but, as mentioned before, there hasn't been much activity in that repo recently. I think we should re-open down the road if anything.
@pksjce let me know if you start working on your interactive editor components again for the splash or getting-started page. I'd be happy to help with design or whatever else.


Implement Electricity Maps HTTP Client

Description
As a Carbon Aware SDK Developer, I want to login and connect to Electricity Maps API service, so that I can use Electricity Map as a data source.

Acceptance Criteria

[x] Verify that the client can pass credentials to Electricity Map API
[x] Ensure that the Electricity Maps client can connect to https://api.electricitymap.org endpoints.
[ ] Ensure that the Electricity Maps API can be called through a proxy [similar to WattTime data source]
[x] Ensure that any errors returned from Electricity Maps is forwarded to the consumer layer
[ ] Unit Tests are completed and code passes tests
[ ] Ensure Electricity Map client documentation is added.
[ ] A strategy exists for how and when to update the mappings between API endpoints should Electricity Map update their API at some point in the future (i.e. versioning support)

Dependencies
GSF Backlog Reference
https://github.com/Green-Software-Foundation/carbon-aware-sdk/issues/71
Task List

[x] Implement HTTP client that can handle HTTP requests
[x] Enhance HTTP Client Configuration, so credentials can be passed on.
[x] Implement Error Handling
[x] Implement lookup for Routes supported for HTTP Client.
[x] Implement Proxy Service
[ ] Add unit tests.
[ ] Add documentation.

Sprint-Ready Checklist

[x] Acceptance criteria defined
[x] Acceptance criteria is verifiable / testable
[x] External / 3rd Party dependencies identified
[ ] Engineering team understands acceptance criteria
[ ] Is the user story small enough to be implemented in a short amount of time, but large enough to provide value?

Approving. Please take a look at the full acceptance criteria list since I added a note in there about versioning.

Work will continue in  #167


Bump queue version

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 29.134%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
791

Relevant Lines:
2715

💛  - Coveralls


weex 版本升级说明在哪 ？

https://weex.apache.org/cn/releasenote.html
这里只有 0.13

已经更新了  关掉

HI @xiaolongyuan ,thanks for watch weex ! Weex has joined apache, so we can discuss about weex on https://issues.apache.org/jira/projects/WEEX.

hi @gurisxie i'm told that i have no permission to login

how can i discuss about weex on https://issues.apache.org/jira/projects/WEEX.  ?

@chenzefeng09   I'm sorry for that jira' user is not synchronized with github。 You need register one.


Investigate genome browser issue

Further details TBC but initial review notes below:

Could it be an issue with the cttv_gwas, specifically lines 285-286 - are some SNPs dropped and not sent in the ensembl_call_snps API call?
Also worth looking at gwas_updater and common

Upon further review of the targetGenomeBrowser repo, there are two specific issues that have been identified.
Issue 1: Not all variants are shown in the browser
* Note: the browser view is not connected to the data displayed on the data table as they rely on different API calls and the logic that processes the data is different, as noted below
As noted in the NOD2 and IBD example on QA, not all of the variants are visible in the genome browser. This is because not all variants are requested and sent to Ensembl.
The genome browser logic is "target-centric" and it takes all of the genes found within the browser window and makes a call to our /evidence/filter API endpoint for any ot_genetics_portal or phewas_catalog data regardless of disease. The browser then parses this response for the variants and generates a list that it uses to call the Ensembl /variation/human API endpoint. The browser then uses the Ensembl response to generate the variant lollipops and position the tooltips.
For the majority of cases, this logic works fine. But when viewing a dense region of the genome, not all variants are returned from the initial call to our /evidence/filter API endpoint - and therefore, are not included in the call to Ensembl.
So in the NOD2 and IBD example on QA, we send the following 48 gene IDs to our /evidence/filter API endpoint:
0: "ENSG00000205423"
1: "ENSG00000259843"
2: "ENSG00000261835"
3: "ENSG00000273829"
4: "ENSG00000260298"
5: "ENSG00000155393"
6: "ENSG00000279356"
7: "ENSG00000202124"
8: "ENSG00000260381"
9: "ENSG00000287444"
10: "ENSG00000260031"
11: "ENSG00000252526"
12: "ENSG00000121274"
13: "ENSG00000121281"
14: "ENSG00000274969"
15: "ENSG00000166164"
16: "ENSG00000261393"
17: "ENSG00000261092"
18: "ENSG00000260573"
19: "ENSG00000140807"
20: "ENSG00000260029"
21: "ENSG00000278909"
22: "ENSG00000205414"
23: "ENSG00000260249"
24: "ENSG00000167208"
25: "ENSG00000167207"
26: "ENSG00000270120"
27: "ENSG00000261644"
28: "ENSG00000083799"
29: "ENSG00000264947"
30: "ENSG00000260616"
31: "ENSG00000261703"
32: "ENSG00000261241"
33: "ENSG00000260042"
34: "ENSG00000199771"
35: "ENSG00000261637"
36: "ENSG00000260605"
37: "ENSG00000260620"
38: "ENSG00000287718"
39: "ENSG00000261282"
40: "ENSG00000103449"
41: "ENSG00000261238"
42: "ENSG00000285367"
43: "ENSG00000280344"
44: "ENSG00000287256"
45: "ENSG00000261047"
46: "ENSG00000260818"
47: "ENSG00000260850"

The response to this call is capped at 1,000 but the API notes that we have 1,867 records:

If you alter the call and obtain all records, you will find all of the correct variants, including the ones identified by @DSuveges as missing in the browser view.
However, this can cause performance issues as the various API calls are chained together. So if it takes longer to call our /evidence/filter API endpoint and process that data, it delays the call to the Ensembl API - and this call is limited to 200 variants per API call.
Issue 2: Browser not correctly labelling variants
In cases where the browser works as intended and displays the relevant variants, there are examples where the variant lollipops are not correctly coloured red or dark cyan.
For example, in the case of CCND1 and multiple myeloma, rs9344 should be coloured red as multiple myeloma is one of the associated diseases shown in the tooltip.
It looks as though the logic in the foreground_colour function is not properly assigning the colours. In this case, it appears that the gB.gene() === d.target.geneid conditional check on line 271 fails but it passes the d.highlight check on line 273 - hence the dark cyan colour.
I believe that it fails because the variant - rs9344 - has been "assigned" to both CCND1 and LTO1 (the other target visible in the browser on the right-hand side) based on the Open Targets Genetics Locus2Gene scoring pipeline. Because there are entries where the d.target.geneid === CCND1 and d.target.geneid === LTO1, the widget incorrectly assigns the colour when it encounters an entry where d.target.geneid === LTO1.

After reviewing the issue further, I am going to recommend that we do not make any changes to the existing visualisation for 20.04 or 20.06. Long-term, we should do one of the following:

Drop the browser view from the evidence page
Consider another alternative (e.g. locus plot in Genetics Portal but it does not have the rare variant track)
Invest in expanding the browser so that it can account for the differences brought on because of the Open Targets Genetics Portal data while reducing the number of API calls made and potentially the scope of the call (e.g. to just the gene in question rather than all genes in the browser view)

As noted in my comment above, the increase in evidence strings from the Open Targets Genetics Portal means that we will have more cases like NOD2 and IBD where the browser does not load all the variants because not all variants are requested in our API call. While we could increase the call to 2000 evidence strings, this will have unintended performance consequences on the evidence and target profile pages in both the Angular and React applications. And it will make the BRCA2 browser issue more widespread and will also increase the number of targets and evidence pages where the Ensembl calls fails the first time it is made - but then works if the user refreshes the page.
It is also worth noting that increasing the size of the call will not resolve the issue entirely. If we do not have an RSID for the evidence string (e.g. ERLIN1 in lean body mass, the Ensembl API returns no data for that variant and there is no variant lollipop in the browser.
Also, the logic that categorises and colours the variant lollipops does not work as intended because a variant can have multiple assigned genes depending on the L2G pipeline. If the variant only ever has one gene, as was the case with GWAS Catalog data and the closest gene assignment, then the logic would work properly. Rewriting this logic to account for multiple assigned genes for one variant would take considerable time because the application would have to store details about the variant and refer to this as it iterates through the variants returned in the evidence strings.

Issue closed as broader discussion about use case for genome browser would help decide which option to select


Revise granule cell hierarchy to add more detail.

The general class 'granule cell' now has a definition, but this is necessarily vague given that this is a grouping of likely unrelated neuron types, all of which are small.
This means that 'granule cell' is  uninformative as a genus.  The logical and textual definitions of types of granule cell should therefore be revised from the very simple genus-type definitions currently present.
e.g.
cerebellar granule cell
http://purl.obolibrary.org/obo/CL_0001031
Granule cell that is part of the cerebellum.
Wikipedia has nice potted descriptions of these.  e.g. https://en.wikipedia.org/wiki/Granule_cell#Cerebellar_granule_cell
-> A neuron with a very small soma located in the granule cell layer cerebral cortex.  It develops from precursors in the rhombic lip. These cells have several short dendrites which terminate with claw-shaped endings and a single axon that ascends into the molecular layer where it splits to form parallel fibers.
Updates to logical axoms

consider restricting soma location to granular layer of cerebellar cortex http://purl.obolibrary.org/obo/UBERON_0002956
add develops_from axiom to 'rhombic lip' (Note - there is an extensive literature on this that could potentially be mined for details
add has_part relationship to parallel fiber http://purl.obolibrary.org/obo/GO_1990032

Class
Revisions

cerebellar granule cell
See above

cortical granule cell
Broad / general class. No change.

hippocampal granule cell
Broad / general class. No change.

dentate gyrus of hippocampal formation granule cell
Promote comment to definition.

Island of Calleja granule cell
Done

olfactory granule cell
TBD

See #1980 for examples of classification based on derivation from upper/lower rhombic lip.

Edits for 'cerebellar granule cell'

[ ] Edit text definition:

CURRENT: "Granule cell that is part of the cerebellum."
PROPOSED: "An excitatory granule cell with a soma located in the granular layer of cerebellar cortex. In an adult, a cerebellar granule cell has short dendrites with a characteristic claw-like appearance and a long axon that ascends to the molecular layer where it bifurcates and extends mediolaterally to form parallel fibers."
doi:10.3389/fncir.2020.611841
doi:10.12688/f1000research.15021.1

[ ] Add axioms:

SubClass of some 'glutamatergic neuron'

'directly develops from' some 'granule cell precursor' (relabel object to cerebellar granule cell precursor'

[ ] Add comment:
It has been noted in at least some mammalian species that granule cells are the most numerous cell type in the cerebellum and in the brain, with at least 99% of all cerebellar neurons being granule cells.
doi:10.3389/fncir.2020.611841

Related edits for 'granule cell precursor':

[ ] Edit label of 'granule cell precursor':

CURRENT: 'granule cell precursor'
PROPOSED: 'cerebellar granule cell precursor'
REASON: The text def and dbxref are specific to cerebellar granule cell precursors.

[ ] Add synonyms to relabeled class:

"granule cell precursor", broad, doi:10.3389/fncir.2020.611841

"granule cell progenitor", exact, doi:10.3389/fncir.2020.611841

"GCP", related, abbr, doi:10.3389/fncir.2020.611841

[ ] Edit text def of 'granule cell precursor':

change "NK-1 positive" to "HNK1-positive" (keep PMID dbxref)

[ ] Add axiom to 'granule cell precursor':

'part of' some 'upper rhombic lip' (import term)

Edits for ‘dentate gyrus of hippocampal formation granule cell’

[ ] Edit text definition:

CURRENT: "The principal cell type of the dentate gyrus."
PROPOSED: “A granule cell that has soma location in the dentate gyrus cell layer of the hippocampal formation and has an elliptical cell body and characteristic cone-shaped tree of spiny apical dendrites. The branches extend throughout the molecular layer and the distal tips of the dendritic tree end just at the hippocampal fissure or at the ventricular surface. The dentate gyrus of hippocampal formation granule cell is the principal cell type of the dentate gyrus.” PMID:17765709

[ ] Edit logical definition (make more precise):

CURRENT: 'granule cell'
and ('has soma location' some 'dentate gyrus of hippocampal formation')
PROPOSED: ‘hippocampal granule cell'
and ('has soma location' some 'dentate gyrus granule cell layer’)

[ ] Edit comment:

CURRENT: “The granule cell has a characteristic cone-shaped tree of spiny apical dendrites.”
PROPOSED: “As far as can be determined, all dentate granule cells appear to project to CA3 and the axon trajectory is partially correlated with the position of the parent cell body.”
PMID:17765709
Related edits for dentate gyrus mossy fiber:

[ ] delete has_exact_synonym “granule cell axon” (consider ‘parallel fiber’)
or
make it a broad synonym

[ ] Edit axiom:

CURRENT: 'part of' some 'granule cell'
PROPOSED: 'part of' some 'dentate gyrus of hippocampal formation granule cell’

Edits for 'cerebellar granule cell'

Once all axioms are in place please check whether the DL query 'develops from' some 'upper rhombic lip' returns this cell type.

Edits for ‘dentate gyrus of hippocampal formation granule cell’

Looks good but please simplify name: suggest: dentate gyrus granule cell

Added to action items above. Will add current label as an exact syn.

Edits for 'cerebellar granule cell'

Once all axioms are in place please check whether the DL query 'develops from' some 'upper rhombic lip' returns this cell type.

Looks like it does:

I wonder if hippocampal granule cell and dentate gyrus granule cell should be exact synonyms.
That is, are there hippocampal granule cells not of dentate gyrus?
Not in these two articles.
https://en.wikipedia.org/wiki/Hippocampus_anatomy
https://en.wikipedia.org/wiki/Granule_cell

I wonder if hippocampal granule cell and dentate gyrus granule cell should be exact synonyms.
That is, are there hippocampal granule cells not of dentate gyrus?
Not in these two articles.
https://en.wikipedia.org/wiki/Hippocampus_anatomy
https://en.wikipedia.org/wiki/Granule_cell

Thanks for the suggestion, @raymond91125.
A cursory online literature search revealed at least one instance of granule cells described in the hippocampus outside of the DG: https://www.jneurosci.org/content/30/24/8296

Edits for 'olfactory granule cell'

[ ] Edit text definition:

CURRENT: "Granule cell that is part of the olfactory bulb."
PROPOSED: "A granule cell that has a soma located in an olfactory bulb granule cell layer. An olfactory granule cell is an interneuron that lacks an axon, makes reciprocal dendro-dendritic synapses with mitral cells and tufted cells and is involved in the fine spatio-temporal tuning of the responses of these principal olfactory bulb neurons to odors."
DOI:10.1038/s41598-018-27692-8

[ ] Add synonyms:

"olfactory bulb granule cell" (exact, DOI:10.1038/s41598-018-27692-8)
"GCs" (related, plural, DOI:10.1038/s41598-018-27692-8)

[ ] Change logical definition:

CURRENT: 'granule cell' and ('has soma location' some 'olfactory bulb')
PROPOSED: 'granule cell' and ('has soma location' some 'olfactory bulb granule cell layer')

[ ] Remove SubClass Of 'granule cell' (redundant)

[ ] Add axioms:

SubClass Of some interneuron

‘synapsed by’ some ‘mitral cell’

‘synapsed to’ some ‘mitral cell’

‘synapsed by’ some ‘olfactory bulb tufted cell’

‘synapsed to’ some ‘olfactory bulb tufted cell’

‘involved in regulation of’ some ‘sensory perception of cell’

[ ] Add comment:

"Granule cells are the most abundant neuronal population in the olfactory bulb and are continuously renewed throughout life."
DOI:10.1038/s41598-018-27692-8


Write guidelines for "Elettronica"

In templates/form.xhtml, in the area marked with <!-- TODO: this -->

Done, PR created.

Deployed


Update all.json

Omg look at the font kerning and logo size of the first one, "worst scam ever" award haha!


incorrect buckets with group_by.duration: 1d and span.start: month

Checklist

[X] I updated the card to the latest version available
[X] I cleared the cache of my browser
[X] I verified that I'm really running the lastest version in my browser console
[X] I checked if there is another issue opened with the same problem

Description
When rendering daily aggregated values for the current month the bucket boundary time seems to be always 10:30. This is independent of the data displayed (I used temperature values in my example with plenty of values without gaps).
When not using span: {start: month} the boundary as at the current time (which is also not always desirable).
Version of the card
Version: v1.9.0-dev.1 (same behavior with version v1.8.2)
To Reproduce
This is the configuration I used:
type: 'custom:apexcharts-card'
graph_span: 1 month
span: {start: month}
series:
  - entity: sensor.north_out_temperature
    group_by: {func: avg, duration: 1d}

Screenshots

Expected behavior
If span: {start: month} and group_by: {duration: 1d} buckets should start at 00:00
Desktop (please complete the following information):

Browser any

Smartphone (please complete the following information):

Device: any

graph_span: 1 month is not a round number (because the duration of 1 month is variable depending on which month it is).
Can you try with graph_span: 31 days?

Your fast response has almost blown me from my chair.
Your suggestion fixes my issue. I'm happy.
(Might be worth to add a note in the description)


Talier: add clear_checkpoint flag

add a Boolean arg to clear the checkpoint for the given patterns.

The feature is in release 0.1.1


Suggest support expressions

As an alternative to #21489

Any news?

Ping @strega-nil-ms for review this PR.

This one is "easy" enough I think we should consider just bulk fixing them and truly deprecating...

There are "easy" cases, but there are also ports where there is an existing supports expression and a vcpkg_fail_port_install call, but they differ in semantics. So you have to fix all this ports manually. Currently vcpkg_fail_port_install is used in 293 ports.

There are "easy" cases, but there are also ports where there is an existing supports expression and a vcpkg_fail_port_install call, but they differ in semantics. So you have to fix all this ports manually. Currently vcpkg_fail_port_install is used in 293 ports.

I'm down to 161 remaining and they've been relatively straightforward...

OK I have submitted PRs to eliminate all the calls; I would prefer to merge those then adopt https://github.com/microsoft/vcpkg/pull/21489 (outright deprecation) instead.

There are officially no more vcpkg_fail_port_install calls in master so I think we should do https://github.com/microsoft/vcpkg/pull/21489 instead.

Agreed with @BillyONeal, closing this in favor of #21489.


Horrible Memory usage in integrated dev environment

I am now using react native in a Swift project, most of my functions are written in react native, and some of my native function written in Swift and I bridge them to react native by Objective C. After I finish my whole project, I found a horrible thing is that the memory usage in my App is REALLY HORRIBLE.
Here is my screen shot of XCode. I tested on my latest iPod touch. The memory usage can easily goes over 600M in several minutes, even if you just open the App and not touching the device. After several minutes my app got terminated by system because of high memory usage.

I have think about if my application and JSX construction is not really good, but I try to boot my App with the code below, and the memory keep raising in a speed about 1M/s even I don't touch my device.

'use strict';

import React from 'react-native';
var {
  Text,
  Component,
  } = React;

class Test extends Component {
  render() {
    return (
        <Text>Hello</Text>
    );
  }
}

React.AppRegistry.registerComponent('test', () => Test);

And when I removed the react native view controller and restart my App, nothing's gonna happen anymore.
I am wondering if the memory control is exist / enabled in integrated environment or how can I manually enable them?

my version is react native 0.16 installed by cocoapods

I think those leaks in dev mode have been fixed in 0.17

@moooji thanks i will try in 0.17!

@moooji Thanks for guiding.
I just tried 0.17 and it still exists, but later I tried updating to 0.19rc, and this memory leak no longer happens!


Model checkpoint files

Hi, thank you for sharing the code!
I believe in order to run inference I would need the checkpoint files, could you add them as well?
Thank you

Hi @tenpercent , we are working on releasing the checkpoint but the legal process will take some time.


Can set expired allowances

In the library Allowance, neither updateAll nor updateAmountAndExpiration check that the expiration passed is not in the past.
That means it's possible to set an approval expiration timestamp that ends up being lower than block.timestamp (and greater than 0, which is the special case), and have the call succeed.
Seems like a minor oversight - I don't think it has worrying consequences. As long as user sets a reasonable expiration for the allowance, things should be fine. Worst case scenario the expired allowance is stored, the user notices the problem, and submits another tx to update the allowance.
Here's a simple test case to reproduce:
function testApproveExpired() public {
    vm.warp(block.timestamp + 1000);
    uint48 expiredTimestamp = uint48(block.timestamp - 1);
    vm.prank(from);
    vm.expectEmit(true, true, true, true);
    emit Approval(from, address(token0), address(this), defaultAmount, expiredTimestamp);
    permit2.approve(address(token0), address(this), defaultAmount, expiredTimestamp);

    (uint160 amount, uint48 expiration, uint48 nonce) = permit2.allowance(from, address(token0), address(this));
    assertEq(amount, defaultAmount);
    assertEq(expiration, expiredTimestamp);
    assertEq(nonce, 0);
}

Interesting point - thanks for raising!
My initial take is that the behavior is exactly the same whether we revert on already-expired allowance or succeed and store it anyways.
Reverting saves a little gas for the user who made the mistake, and is a little more clear that the approval is not going to be usable. But I'm not sure it's even worth the added (admittedly tiny) gas to every other permit/approval to check+revert in this rare case. Esp given its a check that can/will be easily caught in interfaces/sdk integrations

@snreynolds want to double check my thoughts here?


Add function to find zero crossings

Bisection method to find zero crossing of event indicators.

Added in commit c95570e152839352ce9c67ea4823b6533e47d6ce


check if caching server is reachable before using

:bulb: Description
If a caching server is given but is unreachable, Mist will fail to download the installer.
:white_check_mark: Proposed solution
Check if a given caching server is reachable, and failover to not using the caching server if it is not.
:adhesive_bandage: Alternatives Solutions + Workarounds
Currently this can be accomplished with a script outside of Mist, then calling mist-cli with the appropriate option (or lack thereof)
:information_source: Additional context

Would you also like to see this implemented in Mist.app?:x:

Makes sense! I'll see how much work is involved to default to no caching server, if the specified one is not accessible 👍


Empty Function

Hi I need help why the "Function" is empty. I have the correct JAR.
The code need to have something special to be recognize by the plugin?
Can you share some example of a java code that will work?

Hi.
The JAR will be evaluated on AWS server, when downloaded (only basic validation is performed in plugin - not zero size and that it is zip-archive),
There is nothing special supposed to be in your logic, to upload JAR. You can also try to upload your JAR to AWS Lambda with AWS web-interface.
To be able to AWS Lambda running your component - verify you specified correct handler function name in the field "Handler" (in the section "Function Configuration")
Also check messages in the "Local Log" tab.
The function dropdown box (wich I assume you mentioned) is populated from your list of functions. Please check following:

Creadentials profiles have been available on you PC for users, where your AWS Lambda function is located
In the Region dropdown - the region is selected, where your AWS Lambda function is located
In Profiles dropdown - a profile is selected for a user, which has access to your AWS Lambda function is located
NB: profiles can be created with AWS CLI

I have uploaded the JAR in AWS web-interface and test it and it works fine.
Same profile and region.
In my local terminal it show the function:
$ aws lambda list-functions --profile adminuser
FUNCTIONS	xxxxxxxxxxxxx	2671	Hello World	arn:aws:lambda:us-east-xxxxxx:xxxxxxx:function:helloWorldJava	helloWorldJava	hello.world.aws.Hello::handleRequest2018-09-14T13:27:13.413+0000	xxx	xxxxxxxxxxxxxxxxxxxxx	arn:aws:iam::xxxxxxxxxxx:role/service-role/rolHelloWorldJava	java8	15	$LATEST
TRACINGCONFIG	PassThrough
VPCCONFIG
FUNCTIONS	xxxxxxxxxxxxxxx
In Plugin Logs:
INFO: FUNCTION is not selected.

I careted the credentials with this:
aws configure --profile adminuser
(with the correct Access key and Secret key)

Could you tell if this is correct:

in the "Profile" list - you should be able to see this profile and select it (hit "Refresh" to update the list)
In the "Region" list - the region is selected, where the AWS Lambda function is created
You do not work behind proxy. If you do - please setup proxi in IDEA settings
After hitting the "Refresh" button - you do not see your function (any functions) in the Function list?

Could you tell if this is correct:

in the "Profile" list - you should be able to see this profile and select it (hit "Refresh" to update the list)
In the "Region" list - the region is selected, where the AWS Lambda function is created
You do not work behind proxy. If you do - please setup proxi in IDEA settings
After hitting the "Refresh" button - you do not see your function (any functions) in the Function list?

I try this:
(I dont have proxy)
Yes the Function list is empty cant select anything, my region is us-east virginia.

Just to be sure - the function is in "arn:aws:lambda:us-east-1" - not in "us-east-2" (it is not seen in your info), correct?
I do not see any reason the plugin does not show functions.
I can suggest:

Restart IDEA (probably you did already)
Try to temporarily install a latest plugin release from the releases - it has some irregular issue with my latest IDEA - this is why I did not publish it yet.
Check if there is anything reported in AWS Log (in AWS console interface).

I would also suggested in Local Log tab - set the log level from INFO to DEBUG

I would also suggested in Local Log tab - set the log level from INFO to DEBUG

I try restarting IDEA and also the PC, but same problem.
Changing the log to DEBUG the only interesting is this when I refresh the Function:
DEBUG: Refresh list of AWS Lambda functions DEBUG: Refresh function list. DEBUG: Found 0 Java-8 functions. DEBUG: Function not set. DEBUG: Refresh role list. DEBUG: Found 0 roles. DEBUG: Refresh JAR-artifact list. INFO: Selected JAR-artifact: "helloWorld-1.0-SNAPSHOT.jar" INFO: Function is not selected.

Please share the IDEA and plugin versions you use, I will try check on my side.

Please share the IDEA and plugin versions you use, I will try check on my side.

IntelliJ IDEA 2018.2 (Ultimate Edition)
Build #IU-182.3684.101, built on July 24, 2018
Plugin Version: 1.6 & 1.7.RC2

Do i need a Main class? because i don't have one.
And in this example you have one: https://github.com/satr/aws-amazon-shopping-bot-lambda-demo1/blob/master/src/io/github/satr/aws/lambda/shoppingbot/Main.java

No, you do not need a Main class. That one was just for testing.

Please note - when you create a profile with aws CLI, key/secret is stored in the file .aws/credentials , but region and output format are stored in the file .aws/config. However, the region is not loaded from it automatically (this is why you may see "(no region)" next to the profile name). But if the region is put to the .aws/credentials within its profile (in text editor) - it is loaded fine. Probably I need to double-check my code in this logic as well.

An issue has been fixed in the release v1.7.RC3


Allow any class to be a markup extension.

System.Xaml allows any class to be a markup extension, but as far as I can tell to be a markup extension in OmniXAML, for a markup extension called e.g. "Foo" the class needs to be called FooExtension.
In WPF, the Binding class is itself a markup extension:
http://referencesource.microsoft.com/#PresentationFramework/src/Framework/System/Windows/Data/BindingBase.cs,63
This would eliminate having to create e.g. a BindingExtension class which then copies its properties to a Binding object in ProvideValue.
This isn't high priority, just a difference I noticed.

Yes, I know! But how could I map markup to a runtime type? I currently do it adding "Extension" to the text. I have looked for how System.Xaml does it, but I found nothing. Also, I think Binding is the only that doesn't end in "Extension".

You could at first search for a Type "BlaBlaExtension", if no one found search for "BlaBla". I think WPF does it the same way. (C# does it the same with Attributes). And in WPF every MarkupExtension derrives from MarkupExtension.

Nice approach. I will implement that in OmniXAML V2


Fix Storage stress run and issues with fault injector

Description
Fixes issues causing the memory stress tests to fail to run and fixes live tests using HTTP fault injector.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/azp run java - storage - tests

/azp run java - storage - tests

/azp run java - storage - tests

/azp run java - storage - tests

API change check
API changes are not detected in this pull request.

/azp run java - storage - tests

/azp run java - storage - tests

/azp run java - storage - tests

/azp run java - storage - tests


[Feat]: ADDING A FEED BACK SECTION

What feature?
I have an idea
Add screenshots
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

As there is no database, we cannot store the feedback anywhere. Therefore, I think we cannot implement this feature for now.

I can create using react js and can show it below the feedback section

Hey can you provide me your email , as it is required.

<EMAIL_ADDRESS>

Are you working under GSSOC23 @kharshita590

Yes


eltwise ops fail PCC when broadcasting [GS][WH]

Describe the bug

ttnn.add fails with "Low Pcc" in Whisper model.

Input shapes of tensor_a : [8, 1500 [1504], 512] and tensor_b : [1500 [1504], 512]

On GS(e150):
E       AssertionError: 0.20598982372530486
On WH(n300):
E       AssertionError: 0.17328692806300294

To Reproduce
Steps to reproduce the behavior:

Pick the test from the commit.
Run pytest tests/ttnn/unit_tests/operations/test_add.py::test_whisper_add.

Expected behavior
Expected to pass the test case.
Please complete the following environment information:

OS: [e.g. Ubuntu 20.04]
Devices: GS(e150), WH(n300)

I believe this is because broadcasting is not supported, we also see this bringing up llama 3.2 with the following test failing for all elementwise ops:
@pytest.mark.parametrize(
    "dtype",
    [
        ttnn.bfloat16,
    ],
    ids=[
        "bfloat16",
    ],
)
@pytest.mark.parametrize(
    "test_func_name, torch_func_name",
    [(ttnn.add, torch.add), (ttnn.sub, torch.sub), (ttnn.mul, torch.mul)],
)
def test_run_elt_binary_broadcast(dtype, test_func_name, torch_func_name, device):
    b, nh, s, d = 1, 8, 32, 128
    shape_a = (b, nh, s, d)
    shape_b = (b, 1, s, d)

    torch.manual_seed(10)

    mem_config = ttnn.MemoryConfig(ttnn.TensorMemoryLayout.INTERLEAVED, ttnn.BufferType.L1)

    in0 = torch.randn(shape_a).bfloat16().float()
    in1 = torch.randn(shape_b).bfloat16().float()
    in0_t = torch2tt_tensor(in0, device, tt_memory_config=mem_config, tt_dtype=dtype)
    in1_t = torch2tt_tensor(in1, device, tt_memory_config=mem_config, tt_dtype=dtype)

    out_t = test_func_name(in0_t, in1_t)
    out = tt2torch_tensor(out_t)

    passing, output = comp_pcc(out, torch_func_name(in0, in1), 0.9999)
    logger.info(output)
    assert passing

Suggest we rename the issue to "ttnn binary elementwise ops fail with bad pcc when broadcasting"

This is related to #13643 in that we are not truly doing broadcasting properly.  We need kernel development on this effort.  Going to see where we can prioritize this work.

FYI @kkeerthana0573,
tested the shapes mentioned in this issue on the latest main.

@KalaivaniMCW,
Thanks for the workaround.

@kkeerthana0573 shall I close this issue ?

@KalaivaniMCW,
We proceeded with the workaround, so there’s no blocker now. However, the underlying broadcasting issue remains unresolved. This issue can be closed since it’s no longer blocking.

@kkeerthana0573 Yes https://github.com/tenstorrent/tt-metal/issues/13643 is still in progress and being tracked.
Thanks.

Closed with workaround
https://github.com/tenstorrent/tt-metal/issues/13643 is still in progress


Grief Prevention plugin support

I would like to reference a few things using depenizen and grief prevention.
How many claim blocks a player has.
How many claims a player has.
The locations of each claim a player has.
A tag to treat a claim like a cuboid.
The total blocks of each claim.
The current rate of accruing blocks for claiming can be modified in config, can we adjust it with denizen/depenizen per player or by flag?
List the access and access levels of each player listed to a claim.
Ability to modify those levels of access and the players with access using denizen/depenizen.
Ability to adjust claim blocks via depenizen/denizen.

[16:28:17] <irbDylan> GriefPrevention tags? Yessss +1
[16:28:35] <irbDylan> That'd be awesome, I'd use them.

I'll get started I guess

Some things I'd suggest if they're easy:
Ability to delete claims with denizen/depenizen
Transferring claims/setting new owner

Ability to modify those levels of access and the players with access using denizen/depenizen.
Ability to adjust claim blocks via depenizen/denizen.

@GravityX

Half done. Will need to add all the metadocs and will update with more content soon :)

i updated some things, again if i did things wrong sorry im so noob. but the updated list has more precise requests especially after playing with the first update and using the tags in place. This will work wonderfully and does so far no glitches found. Thanks Thanks Thanks.

Can already adjust owner. !mechamism cpclaim.owner

In regards to events, we are very limited to only what grief prevention a provides us, will take a look when I get time or @Morphan1 can

@Fortifier42 you forgot meta in places and mislabeled things. You have griefprotection instead of griefprevention as tags for example.

Oh :/ I thought I replaced all those :(
Sent from my iPhone

On 16 Feb 2016, at 10:18 AM, mcmonkey<EMAIL_ADDRESS>wrote:
@Fortifier42 you forgot meta in places and mislabeled things. You have griefprotection instead of griefprevention as tags for example.
—
Reply to this email directly or view it on GitHub.

A tag to know the total blocks of each claim.
<EMAIL_ADDRESS>will return the size of the claim in blocks. (Was already implemented.

Only events which are in GriefPrevention which are related to the claims:

Claim Deleted
Claim expired

I updated the events idea due to more knowledge about the area.

I'd like to add a new event to depenizen listening for players entering grief prevention claims

on player enters gpclaim:

Yeah - go ask the dev... :/

@Fortifier42 that one can definitely be added by us 0.o

@mcmonkey4eva then u do it, I'm busy >:(

Added meself ya lazy nub

I only turned my computer on for the first time last night @mcmonkey4eva D:

Consider turning it on more often.

What still needs to be done here? Removing @Fortifier42 because he died


OP: Aggregated GH repo metrics

What would you like to see? Please provide a clear and concise description of what you want
For Retro Funding 5, could we get some  aggregate github repo metrics like:

How many unique contributors are we rewarding?
How many years in development?
How many forks/stars?

Is there any additional context you can share? Feel free to include notes or screenshots that can help us research and track the issue.
I'm wondering if this is useful information to showcase the results of the round "Retro Funding 5 has rewarded more than 1 billion full time contributors"
Is there a write-up or doc associated with this issue? Please link to it.
No response

Added a notebook here: https://github.com/opensource-observer/insights/blob/main/analysis/optimism/retrofunding5/RF5_ConsolidatedMetrics.ipynb
Metrics:

Forks: 38021
Stars: 132856
Developer years: 194
Developers (all time): 566
Developers (last 2 years): 461
Contributors (all time): 11903
Contributors (last 2 years): 4991

@ccerv1 could we get this for the R5 scope timeline? October 2023 - Aug 2024?
So we can make statements like "Retro Funding 5 rewarded 400 developers for their work on the OP Stack"

Updated @JSeiferth

Forks: 38021
Stars: 132856
Developer years: 194
Developers (all time): 566
Developers (RF period): 374
Contributors (all time): 11903
Contributors (RF period): 2596


Guide not clear?

Hi! Me and my friends have been trying to get GreenLuma to work for a while now, it was working for one of us a few days ago but for some reason it now doesn't work, and because the page hasn't been updated in yoinks we aren't sure what to do.
All Youtube videos are from 2015 and different files so that doesn't help either...
For one, the guide isn't clear. Once you get to step 3, it tells you that the DLLInjector.exe is not in the path. But the guide doesn't actually tell you properly where to put things... So I've been sat here for hours trying to figure out where everything goes and it still doesn't work. I've had to redownload the zip multiple times only for it to later on break and not give me the whole file. I am so confused so a little help would be greatly appreciated :D

Greenluma can be downloaded and extracted anywhere you want it to be, preferably not in the Steam folder though as some games may check for it there. Then open the manager, give it the path to Steam and then the path to GreenLuma's DLLInjector.exe when it asks, and you should be good iirc.

There is no DLLInjector in the GreenLuma files?

I really need to come up with better naming for this stuff, it keeps getting confused... GreenLuma as in the actual unlocker, that you have to download else where. The Manager, as in the tool that manages the game/dlc lists for GreenLuma.

Oh my I’m so sorry I didn’t realise, where can I download the actual unlocker? I apologise for this 😭

Oops lol.

It's linked in the readme.

Okay thank you, I apologise for this x

The GitHub readme, here

Thank you so much 😭😭😭


error occured and there is no file named domLink.cfg. I have added key in domLink.cfg.example which i got in repo.

Traceback (most recent call last):
File "domLink.py", line 218, in
main()
File "domLink.py", line 147, in main
api_key = args.api if args.api else read_key_from_config()
File "domLink.py", line 44, in read_key_from_config
return config.get('API_KEYS', 'whoxy')
File "/usr/lib/python2.7/ConfigParser.py", line 330, in get
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'API_KEYS'

hello @rajeshk28
i had the same problem and  fortunately i was able to solve the problem
you just need to rename the config file to domlink.cfg


where is the "tip" of a probe?

We want to combine the probe interface specification of a probe with the surgical coordinates for translation, rotation and depth (e.g. from Pinpoint) to get the anticipated electrode positions on an atlas brain. The surgical coordinates are with respect to the "tip" of the probe. To combine these, we would need an indication of where the "tip" is on each probe.
You might think to make the tip (0,0), however in the probeinterface library, it looks like of the the electrodes is (0,0). Is there any to indicate where the tip is in probe interface? Could the tip be the location of the first contour point? Otherwise, could we indicate the coordinates of the tip in a separate field?

Hi Ben.
very often the 0,0 is the depper contact.
We should have an optional attribute for the tip position I think.
We could infer it by the minimmum on the contour but for multi shank we have several tips.

I think that we can safely assume that the tip is the deepest contour point. In case of multiple-shanks, we could write a simple function that estimates the tip for each shank based on the x-coordinates.


Update of WebDriver plugin to 4.8.0

Added a new entry to point the Webdriver plugin to latest 4.8.0 Selenium libs.

Please pull from master, let's see if it helped

My merge from master was successful and then the build that was triggered
in master afterwards was successfully completed!
Thanks Andrey!
Le jeu. 16 févr. 2023 à 23:06, Andrey Pokhilko @.***> a
écrit :

Please pull from master, let's see if it helped
—
Reply to this email directly, view it on GitHub
https://github.com/undera/jmeter-plugins/pull/567#issuecomment-1433232883,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHYHH6QHSUG7XIAM7QUHZZLWXY7ABANCNFSM6AAAAAAU3AP7WM
.
You are receiving this because you authored the thread.Message ID:
@.***>


fix(HomePageSearchBar): fix missing search context issue

Signed-off-by: Phil Kuang<EMAIL_ADDRESS>Hey, I just made a Pull Request!
Fix a regression caused by https://github.com/backstage/backstage/pull/8656 resulting in the following error with the HomePageSearchBar:

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

We are running into this issue and are blocked from upgrading to the latest release until this is fixed. Will this make the January 6th 2022 release?

@awanlin a workaround we're using for now is to just wrap your HomePageSearchBar with <SearchContextProvider>

We are running into this issue and are blocked from upgrading to the latest release until this is fixed. Will this make the January 6th 2022 release?

I'll be around to make sure this gets in, yes.
But you can also temporarily workaround it by wrapping your instance of this search bar in a <SearchContextProbider>, if you want to be on the latest.

updated with @iamEAP 's suggested solution applied directly on SearchBarBase which allows this component to not be externally coupled with SeachContextProvider as @emmaindal suggested


Handle undefined statusText in react native

Remove .replace(/\s+/g, " ") to make it work on react native
Fixes https://github.com/Yaffle/EventSource/issues/94

@yufeih,
thanks for the report, but please do not remove "replace".


pub update: Class 'int' has no instance getter 'buffer'.

~> pub update
Resolving dependencies...
Dependencies updated!
Class 'int' has no instance getter 'buffer'.
NoSuchMethodError : method not found: 'buffer'
Receiver:<PHONE_NUMBER>4108
Arguments: []
~>
<IP_ADDRESS> r21094
Here's the fun bit:
with --trace: no problem
with --verbose: no problem
pubspec yaml/lock attached

Attachment:
pubspec_all.zip (681 Bytes)

This issue has been moved to dart-lang/pub#506.


Have the player choose which color to play.

Only let them move pieces of the color they chose.

ec3afd604b0781271ea5b746b5613a2c5d38d1e7


CheckBasicAuth does not url decode the client_id and client_secret

According to the OAuth 2.0 RFC spec, the client_id and client_secret are first separately URL encoded according to application/x-www-form-urlencoded. The CheckBasicAuth function does not properly decode these segments.

Created a pull request to address this issue: #175

Merged.


Add id to input

Sorry if this is a dumb question or has already been answered, but I haven't seen it anywhere.
But is there a way to add an id to the input that gets rendered?
My controller looks like....
                <Datetime                     id={input.name}                     value={dispdate}                     inputProps={inputProps}                     timeFormat={false}                     closeOnSelect={true}                     onChange={(value) => input.onChange(value)}                     onBlur={input.onBlur}                     isValidDate={isValidDate}                     {...custom}                 />
But the id doesn't get passed along.

<input type="text" class="form-control" value="" placeholder="Graduation year">

‹	2010-2019	›

2009	2010	2011	2012

2013	2014	2015	2016

2017	2018	2019	2020

I'd like it to be `
Main reason for doing this is to make it more accessible. Currently not having the id is giving me quite a bit of accessibility failures.

@shogan94 I was experiencing the same issue, if you pass the option as inputProps then that should solve your problem.
<Datetime inputProps={{ id: 'yourInputID', name: 'yourInputName'}} ... />

Ah thank you! That did the trick


Is there a reason not to use stable Rust?

Diesel currently fails to compile on Rust nightly due to a bug in Rust. I fully suspect that this will be resolved before the current version becomes stable, but I really didn't expect this to cause the docs.rs build to fail. Is there a reason that docs.rs isn't using the normal, distributed, stable version of Rust?

Docs.rs uses a custom-patched rustdoc (right now i think the only patch is to redirect cross-crate links, but i could be wrong), so it requires having master to do that. I also imagine there are nightly-only crates that appreciate being able to distribute docs via docs.rs, and much fewer crates in diesel's situation.

Makes sense. Thanks!


Some helpful functions for Media::Photo, Media::Document and PhotoSize.

Support size() for Media::Photo to get the real size of the photo.
Support thumbs() for Media::Document.
Support download to memory for thumb.
Support get specific type of photo thumb in VecExt.

Ok, I've completely migrated download methods in PhotoSize to download_media and iter_download.
The usage is the same as other media
let downloadable = Downloadable::PhotoSize(photo_size);
let mut download = client.iter_download(&downloadable);

I also implemented download for PhotoSize::Progressive. It's actually the same as PhotoSize::Size. Now users can use largest() to get the largest thumb(for photos it's usually progressive) and download it.
And there was a bug in the download() of PathSize, that the param path was shadowed by the variable mut path. But it's not needed anymore.

The new function DownloadIter::new_from_photo_size is ugly, since request is not needed, I have to fake a useless one. If you think it's ok to make request to Option<tl::functions::upload::GetFile>, I'll do that.

From a quick look, as long as it gets the job done, then it's fine.


Gitea Issues link are formated using localhost:3000 and not the actual name of the site used from the internet.

Gitea version (or commit ref): 1.14.0+dev-782-gfaf775c55
Git version:
Operating system:

docker based using official (docker.io/)gitea/gitea(:latest) image (more exactly the image sha256:831a7ce1c8566419b53f7a8044aac4c24cd4a70937fc73cf60c74efba6e0bfef).
The image is hosted on a amd64/x86_64 server.
The server is accessed threw a nginx frontend generating https using a certificated delivered by letsencrypt.
The screen capture are from a clean install of gitea after discovering the problem on a real life installation.

Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No

Description
I have tryed without a proxy as the problem is interaction with the proxy, but doesn't seems to be a configuration problem of the proxy.
This was reprocduced from scratch after:

Creating a new instance of gitea (hosted on for example https://gitea-test.example.com/)
Creating a admin account
Creating a user account
Creating a repo with the user account

Steps to reproduce:

Create an issue
Go to the issue tabs

Expected result:

The link to the issue goes to something like https://gitea-test.example.com/test-user/barfoo/issues/1

Actual result:

The link to the issue goes to something like http://localhost:3000/test-user/barfoo/issues/1

Screenshots

While hovering the link:

Notes

I haven't yet tryed to update to the latest image, but the image should date back from last saturday. I'll try and post a follow up
I haven't been able to find a similar issue here
The problem exists at least in both issues page a projects as in global issues, but you can access the issues correctly threw the dashboard.

The issue issue is still present with latest version of the docker image:

gitea/gitea:latest : sha256:1aa3a172b0fe66ab5e0e3fa5ca8ce548251b45023451507984ea09031a34ed9b
gitea version : 1.14.0+dev-786-gf0e15250b

You need to set ROOT_URL in app.ini, see https://docs.gitea.io/en-us/config-cheat-sheet/#server-server
If the problem persists, feel free to reopen


fallout-ce: 1.0.0 -> 1.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/alexbatalov/fallout1-ce/releases.
meta.description for fallout-ce is: A fully working re-implementation of Fallout, with the same original gameplay, engine bugfixes, and some quality of life improvements
meta.homepage for fallout-ce is: https://github.com/alexbatalov/fallout1-ce
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.0 in filename of file in /nix/store/3y055826jzcr84spxwmiysrr8fs4jv9l-fallout-ce-1.1.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
fallout-ce

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3y055826jzcr84spxwmiysrr8fs4jv9l-fallout-ce-1.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A fallout-ce https://github.com/r-ryantm/nixpkgs/archive/b13480113c55d055fd83c39dad18875d5c7795ae.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b13480113c55d055fd83c39dad18875d5c7795ae#fallout-ce

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3y055826jzcr84spxwmiysrr8fs4jv9l-fallout-ce-1.1.0
ls -la /nix/store/3y055826jzcr84spxwmiysrr8fs4jv9l-fallout-ce-1.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

fallout-ce

Maintainer pings
cc @hughobrien @TheBrainScrambler for testing.

Result of nixpkgs-review pr 293147 run on x86_64-linux 1

1 package built:

fallout-ce


Add more missing dependencies

What kind of changes does this PR include?

Something else!

Description
I missed some dependencies that should be installed (used in the local integrations).
I also moved the deps specified in .npmrc into package.json so Astro's smoke test should now pass. Should unblock https://github.com/withastro/astro/pull/5193
Added the notes for these special dependencies in MAINTAINERS.md
Notes:
It might be good in the future to split out local integrations and markdown plugins as separate packages monorepo-style to keep the root package.json clean.

The github-slugger might have to wait till we move off Astro-flavored markdown as I can't find a quick way to prevent it (and it's also deprecated).
For canvaskit-wasm, it might be a bit hard since it's not bundle-friendly (uses __dirname), so it shouldn't be bundled. But because we need to bundle astro-og-canvas, it creates a problem where the final bundle would try to import canvaskit-wasm directly (not possible in strict dep installation). So the workaround is needed.
My work on the dependency walker (coming soon™) wouldn't help with this case though. It'll only help removing the custom viteSsrFix integration we added in https://github.com/withastro/docs/pull/1895

Oh man, I hadn’t actually looked at the glue code in canvaskit-wasm — ironically I picked it with the idea that wasm might be more friendly to different environments. I guess you could technically use the compiled .wasm directly, but not exactly sure.
Anyway thanks for the summary! Feel free to merge this when you need to 🙌

In some Vite discussion we also toyed of the idea of resolving the canvaskit-wasm to a nested path so it works with pnpm too even if it's externalized. I feel that it's a bit dangerous but it's definitely another potential path.
Merging this one for now. Thanks for the review!


[Update Request]: How to run wingetbot for Automatic submission of update for Vanity URL

What type of update are you requesting?
A new version of an existing package
Current Package Identifier
WHONET.2023
Package Version
23.11.30
Please describe the changes you would like to see
I don't want to manually submit pull request. Package has vanity URL and new version is available which leads to hash mismatch.
How to configure wingetbot for automatic submitting pull request when this happens?

@drshtmstry - @wingetbot IS working on this issue. Please be patient as moderators (sorry, I'm not) should manually validate and then approve the pull request.

Resolving by https://github.com/microsoft/winget-pkgs/pull/128724

@drshtmstry - @wingetbot IS working on this issue. Please be patient as moderators (sorry, I'm not) should manually validate and then approve the pull request.

Resolving by Automatic update of WHONET.2023 from 23.11.27 to 23.11.30 #128724

Sorry about that.
I didn't see that PR was created.
I thought I need to configure wingetbot manually for updating package.


Use correct country in email

Use the shippingCountry when generating the confirmation email

Good spot. Thanks @Rockerby 👍


Extract resource cost

Add the ability to extract more data from the API

Would be great to have list and amortized prices as well.

Extract resources is in, not the amortized prices.

You can specify the MetricType, this will require two calls as we cannot get the data combined.


Adds a delegate method to prevent scrolling to the previous/next view on selection

Some users may want to restrict the auto-scrolling to the previous / next month, but still maintain the ability to manually scroll (either by calling the loadNextView or dragging). This PR adds a delegate method to lock the scrolling when an 'out' dayView gets selected. I've updated both sets of files (demo & root level)

Hello @Paulo-Branco,
Thank you for adding the useful feature!
Please, update the documentation as well.
Regards,
Eugene

I've updated the wiki to include the new delegate method.

Thank you! :]

when i scroll one month to another month my dot markers not showing in that month view. how to refresh dot markers when i scroll on other month.


custom columns for functions

Would you mind adding custom columns for functions? Like SMA for volume, not only for close
Can't understand such humans who do huge work but are still completely useless, nevertheless people appreciate those(2500 stars)
Dear God help me!!!

@AndreyStille,

Would you mind adding custom columns for functions?

You can do it through the use of a custom study().
# Set EMA's and SMA's 'close' to 'volume' to create Volume MAs, prefix 'volume' MAs with 'VOLUME' so easy to identify the column
# Take a price EMA and apply LINREG from EMA's output
volmas_price_ma_chain = [
    {"kind":"ema", "close": "volume", "length": 10, "prefix": "VOLUME"},
    {"kind":"sma", "close": "volume", "length": 20, "prefix": "VOLUME"},
    {"kind":"ema", "length": 5},
    {"kind":"linreg", "close": "EMA_5", "length": 8, "prefix": "EMA_5"},
]
vp_ma_chain_ta = ta.Study("Volume MAs and Price MA chain", cores=0, ta=volmas_price_ma_chain)

df = # ohlcv
df.ta.study(volmas_price_ma_chain)
print(df.columns)

But I assume that is not enough? As the most active maintainer of this package, I always appreciate others that chip in when they can to support the package for all users whether they incorporate additional features, fix bugs, improve documentation, et al. This is beyond a free solo project. 😎
You are more than welcome to fork, edit and make a PR to

Can't understand such humans who do huge work but are still completely useless

Thanks for the backhanded compliment!
Kind Regards,
KJ


Inventory

Hi!
I was able to create a db cluster and loadgenerators, but then no scripts can work with I guess inventory:
./ec2-terminate.sh
ERROR! Specified --limit does not match any hosts

How does ansible knows where stuff is?

It gets it from your AWS credentials.
On Thu, Apr 6, 2017 at 4:20 PM, Roman Naumenko<EMAIL_ADDRESS>wrote:

I was able to create a db cluster and loadgenerators, but then no scripts
can work with I guess inventory:
./ec2-terminate.sh
ERROR! Specified --limit does not match any hosts
How does ansible knows where stuff is?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scylladb/cassandra-test-and-deploy/issues/126, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABp6RRLH1com-02MU5-YVdSLFLyo5oxQks5rtXMqgaJpZM4M2SHK
.

Ok, it makes sense - since scripts do create hosts.
But still load tests and ec2_terminate fail. Where would you usually look to figure it out? Sorry, my ansible skills are bit rusty.

On Apr 6, 2017, at 4:26 PM, Dor Laor<EMAIL_ADDRESS>wrote:
It gets it from your AWS credentials.
On Thu, Apr 6, 2017 at 4:20 PM, Roman Naumenko<EMAIL_ADDRESS>wrote:

I was able to create a db cluster and loadgenerators, but then no scripts
can work with I guess inventory:
./ec2-terminate.sh
ERROR! Specified --limit does not match any hosts
How does ansible knows where stuff is?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scylladb/cassandra-test-and-deploy/issues/126, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABp6RRLH1com-02MU5-YVdSLFLyo5oxQks5rtXMqgaJpZM4M2SHK
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm puzzled that the creation did work and terminate didn't.
Please run the script with max verbosity (both ansible and the shell) and
we'll see what's the problem.
On Thu, Apr 6, 2017 at 4:39 PM, Roman Naumenko<EMAIL_ADDRESS>wrote:

Ok, it makes sense - since scripts do create hosts.
But still load tests and ec2_terminate fail. Where would you usually look
to figure it out? Sorry, my ansible skills are bit rusty.

On Apr 6, 2017, at 4:26 PM, Dor Laor<EMAIL_ADDRESS>wrote:
It gets it from your AWS credentials.
On Thu, Apr 6, 2017 at 4:20 PM, Roman Naumenko<EMAIL_ADDRESS>wrote:

I was able to create a db cluster and loadgenerators, but then no
scripts
can work with I guess inventory:
./ec2-terminate.sh
ERROR! Specified --limit does not match any hosts
How does ansible knows where stuff is?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scylladb/cassandra-test-and-deploy/issues/126,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABp6RRLH1com-02MU5-
YVdSLFLyo5oxQks5rtXMqgaJpZM4M2SHK>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/scylladb/cassandra-test-and-deploy/issues/126#issuecomment-292362629,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABp6RctnDEEvGYRSD_m4_uYbdYRNr8vSks5rtXeygaJpZM4M2SHK
.

I forgot to mention, I've disabled public IPs assignment. Maybe roles relying on it or something?
This is how create looks like, there are lots of skipped tasks.
./ec2-setup-scylla.sh -e "instance_type=i2.xlarge" -e "cluster_nodes=3"
TASK [Give everyone a minute or two] *******************************************
task path: cassandra-test-and-deploy/roles/scylla-config/tasks/start.yaml:19
skipping: [x.x.1.57] => {
    "changed": false,
    "skip_reason": "Conditional check failed",
    "skipped": true
}

PLAY RECAP *********************************************************************
x.x.1.181                 : ok=4    changed=0    unreachable=0    failed=0
x.x.1.205                 : ok=4    changed=0    unreachable=0    failed=0
x.x.1.57                  : ok=4    changed=0    unreachable=0    failed=0
localhost                  : ok=14   changed=6    unreachable=0    failed=0

Err, this doesn't look right.

@tzach, our Ansible and cassandra-test-and-deploy expert should have a look

Lots of skipped tasks is fine, every time there is an Ansible condition, non-selected tasks are skipped.
My guess is you have a problem with your EC2 inventory, which is used only in terminating and running stress (not in the setup phase.)
Once you have a running cluster, please run ./inventories/ec2/ec2.py and paste the results - which should include all your running servers.
Also please check you set the env-var ANSIBLE_EC2_PREFIX, it is used to tag your EC2 instances.

./inventories/ec2/ec2.py just prints all instances in the account.
Prefix was also exported.

It looks like its loading inventory first time this runs, because there is a 10 or so seconds delay.
echo "tag_user_`echo $ANSIBLE_EC2_PREFIX`"
tag_user_xxx-scylla-test

ansible-playbook -vvvv -i inventories/ec2/ terminate.yaml --limit "tag_user_`echo $ANSIBLE_EC2_PREFIX`"
Using /Users/xxx/cassandra-test-and-deploy/ansible.cfg as config file
ERROR! Specified --limit does not match any hosts

Is that inventory dynamically fetched or it's stored somewhere?

./inventories/ec2/ec2.py just prints all instances in the account.

This is the expected result.
Can you attach the full result here?

echo "tag_user_echo $ANSIBLE_EC2_PREFIX"
tag_user_xxx-scylla-test

is xxx your user name? if so, this is fine.

There is a lot of internal information in the output, I'll reply over email.

I've looked at the output carefully and noticed that it returns only hosts with public IPs. Is it intentional? How to make it return private ones only?

I've looked at the output carefully and noticed that it returns only hosts with public IPs. Is it intentional? How to make it return private ones only?

Its probably it, and may be related to a parameter in inventories/ec2/ec2.ini
I'm looking into it

the following updates to inventories/ec2/ec2.ini
-destination_variable = public_dns_name
+destination_variable = private_dns_name
-vpc_destination_variable = ip_address
+vpc_destination_variable = private_ip_address

expose internal IP instead of external, and list servers with out external IP as well.
I tested ./ec2-terminate.sh with the above change, and it works for servers with and without external IP, but I have not yet run a full test including stress with the new config.

Thanks! I found it as well (except that destination_variable = private_ip_address) since there is no name resolution from laptops.
Running now into ansible problems now.
It lists them correctly but fails to delete, maybe I should try full cycle, create-test-destroy
ansible-playbook -vv --check -i inventories/ec2/ terminate.yaml --limit "tag_user_`echo $ANSIBLE_EC2_PREFIX`"
Using cassandra-test-and-deploy/ansible.cfg as config file
...

PLAY [loadgen_nodes] ***********************************************************

TASK [Terminate instance(s)] ***************************************************
task path: cassandra-test-and-deploy/terminate.yaml:31
skipping: [xx.xx.1.146] => {"changed": false, "msg": "remote module (ec2) does not support check mode", "skipped": true}
skipping: [xx.xx.1.130] => {"changed": false, "msg": "remote module (ec2) does not support check mode", "skipped": true}

PLAY RECAP *********************************************************************
...
xx.xx.1.63                  : ok=1    changed=0    unreachable=0    failed=0
xx.xx.1.66                  : ok=1    changed=0    unreachable=0    failed=0

and when actually applying change:
fatal: [xx.x.1.44]: FAILED! => {
    "changed": false,
    "failed": true,
    "invocation": {
        "module_args": {
            "assign_public_ip": false,
            "aws_access_key": null,
...
            "zone": null
        },
        "module_name": "ec2"
    },
    "msg": "boto required for this module"
}

Hmmm. Any idea what else ansible wants?
pip list boto | grep boto
boto (2.46.1)

I have boto (2.45.0)
What ansible version are you using?

Maybe its a mac related issue like the one presented here
https://github.com/ansible/ansible/issues/5734
or
http://stackoverflow.com/questions/37253793/boto-required-for-this-module-ec2-elb-lb
The second suggest setting PYTHONPATH
I will need to find a mac to validate.

Seems like this fixed the problem with "boto not found":
sudo /usr/bin/python -m pip install boto
Ansible was the latest version
ansible --version
ansible <IP_ADDRESS>

Are you using this for any serious work?

Glad it's working now!

Are you using this for any serious work?

We are using this script daily to test Scylla. We are not yet using it to deploy Scylla production clusters ourselves, altho similar Ansible playbooks are used for that by others.

I also noticed that everything installed into the same zone, so such tests are not simulating anything close to real world scenarios. Were there any difference in performance for multi-zone setup?

There is an option to setup a multi region cluster, not a multi zone. I assume multi zone will introduce some latency between nodes.

Yeah, finally ansible doing useful stuff (these never working as expected
configuration management systems)
I wanted to confirm the results: 3 x i2.xlarge data + 5 x m3.large produced
15k/s "row rate" for each loadgen instance
Does it mean total for cluster was 60k/s?
replication(factor=2)
Populate=5000000
Command=mixed
But disk util was only few GB (from 800GB available for this instance
size).
What would happen if data consume 80% of disk and there is a failed node(s)?
On Thu, Apr 13, 2017 at 1:40 PM Tzach Livyatan<EMAIL_ADDRESS>wrote:

Glad it's working now!
Are you using this for any serious work?
We are using this script daily to test Scylla. We are not yet using it to
deploy Scylla production clusters ourselves, altho similar Ansible
playbooks are used for that by others.
I also noticed that everything installed into the same zone, so such tests
are not simulating anything close to real world scenarios. Were there any
difference in performance for multi-zone setup?
There is an option to setup a multi region cluster, not a multi zone. I
assume multi zone will introduce some latency between nodes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scylladb/cassandra-test-and-deploy/issues/126#issuecomment-293970960,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AENT-lzMEKrUn0xTPE3zNybN0EHXXNz3ks5rvl3_gaJpZM4M2SHK
.

I wanted to confirm the results: 3 x i2.xlarge data + 5 x m3.large produced
15k/s "row rate" for each loadgen instance
Does it mean total for cluster was 60k/s?

Yes. Note that each writes update two servers (RF=2)

What would happen if data consume 80% of disk and there is a failed node(s)?

Not sure what you mean.

its always recommended to keep 50% of the disk free for compaction and some extra space
a fail node does not mean other will take it place automatically. For that, you need to decommission the node.

@rokka-n since the original issue is solved, I'm closing this issue. I suggest to continue this discussion on the Scylla user list:
https://groups.google.com/forum/#!forum/scylladb-users

Thank you!
On Thu, Apr 13, 2017 at 2:18 PM Tzach Livyatan<EMAIL_ADDRESS>wrote:

I wanted to confirm the results: 3 x i2.xlarge data + 5 x m3.large produced
15k/s "row rate" for each loadgen instance
Does it mean total for cluster was 60k/s?
Yes. Note that each writes update two servers (RF=2)
What would happen if data consume 80% of disk and there is a failed
node(s)?
Not sure what you mean.

its always recommended to keep 50% of the disk free for compaction
and some extra space
a fail node does not mean other will take it place automatically.
For that, you need to decommission the node.

@rokka-n https://github.com/rokka-n since the original issue is solved,
I'm closing this issue. I suggest to continue this discussion on the Scylla
user list:
https://groups.google.com/forum/#!forum/scylladb-users
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scylladb/cassandra-test-and-deploy/issues/126#issuecomment-293980684,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AENT-uaQ3adcXIshITQUGSuojbtrfqtVks5rvmcRgaJpZM4M2SHK
.


Dashboard

TODO

~enable storing tvl information in db~
record token total supply in db
record fees generated in db
record total token holder information in db

Codecov Report

Merging #41 (b4cf639) into main (e3e2cc7) will increase coverage by 0.22%.
The diff coverage is 28.20%.

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
+ Coverage   20.76%   20.99%   +0.22%
==========================================
  Files          21       22       +1
  Lines        1247     1286      +39
==========================================
+ Hits          259      270      +11
- Misses        944      972      +28
  Partials       44       44

Impacted Files
Coverage Δ

dashboard/dashboard.go
28.20% <28.20%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #41 (b4cf639) into main (e3e2cc7) will increase coverage by 0.22%.
The diff coverage is 28.20%.

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
+ Coverage   20.76%   20.99%   +0.22%
==========================================
  Files          21       22       +1
  Lines        1247     1286      +39
==========================================
+ Hits          259      270      +11
- Misses        944      972      +28
  Partials       44       44

Impacted Files
Coverage Δ

dashboard/dashboard.go
28.20% <28.20%> (ø)

Continue to review full report at Codecov.

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

I'm goign to go ahead and merge this and will tackle the remaining dashboard stuff later

I'm goign to go ahead and merge this and will tackle the remaining dashboard stuff later


Opaque error message when Kubernetes environment variables clash

I have a little installation of Registry in a small Kubernetes installation, and am using cesanta/docker_auth to provide authentication.
Inside a single namespace I created two services:

registry, for the image registry (registry)
registry-auth, for the authentication provider (cesanta/docker_auth)

In this scenario, Kubernetes creates a handful of environment variables that allow software to locate their neighbouring services within the same namespace. One of these is REGISTRY_AUTH_PORT which contains a URI-styled string in the pattern tcp://12.3.4:80.
However, this seems to clash with the auth: section of the Registry configuration, despite there being no child item named port.
The registry spits out the following error message:
configuration error: error parsing /etc/docker/registry/config.yml: yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `tcp://1...` into configuration.Parameters

Usage:
  registry serve <config> [flags]
Flags:
  -h, --help=false: help for serve

Additional help topics:

This is an incredibly opaque message that appears to point the blame at a YAML file on disk, rather than the true source of the value, an environment variable. I have spent about two and a half hours tonight trying to figure out where on earth tcp://1... came from as it wasn't in my config.yml and it wasn't in the default config.yml and it doesn't appear to be a default value within the Registry.
To reproduce my night of pain and sorrow, you can run:
docker run --rm -it --env=REGISTRY_AUTH_PORT=tcp://12.3.4:80 registry:2

Whilst I'm not sure what can be done about being more resilient in the case of this environment variable clash, I am certain that there is room for improvement in the error message to better describe what the invalid value is and where it came from.

Hi @yaakov-h can you please open an issue in https://github.com/distribution/distribution
This repo is only tracking the official image for distribution. Also, please use 2.8.1 image, not 2

opened at https://github.com/distribution/distribution/issues/3653, thanks.


Implements API service accounts

What this PR does / why we need it:
Implements API service accounts
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #445
* API Server now supports kubernetes service accounts tokens

/retest

/retest

/retest


Add update version script.

I've made a bash script that update's version number a cross some files if the current TDLib version in CMakeLists.txt is modified.
By default, the script updates:

README.md.
example/cpp/CMakeLists.txt.
example/uwp/extension.vsixmanifest.
td/telegram/OptionManager.cpp.

And you can easily drop these files from changing version by specifying argument -i. You can also pass unlimited number of files to change.
After making changes to these files, the script will execute git diff [FILES...] which will help you to ensure that everything is changed correctly.

If N/n there is something wrong, undo changes and exit.

All thanks goes to @levlam.

Thank you, @AYMENJD!


how to fine tune the model

hello , i am using your model to extract informations from invoices
can u provide a notebook that fine tune the mistral model  to get thet model mychen76/mistral7b_ocr_to_json_v1
Thanks

hello , i am using your model to extract informations from invoices can u provide a notebook that fine tune the mistral model to get thet model mychen76/mistral7b_ocr_to_json_v1 Thanks

Hi,
here's the experimental training notebook i used:  https://github.com/minyang-chen/LLM_convert_receipt_image-to-json_or_xml/tree/main/train_ocr
may be a bit old by now, hope you still find useful.
thank

Hello, would you mind to share the notebook to fine tune the Image to json/xml too? Thanks!😊


@Visible not working for embedded page object containers

@Visible works only for native page objects. If a container page object is defined as a field of a parent pageobect, then the visibility of its child page objects will be checked even if it is by its own not annotated with @Visible.

Fixed by #23


Provide dual-sim support for TextSecure

Maybe TextSecure whould even be a default messaging app? Anyway, it does not integrate correctly with Fairphone dual sim (https://github.com/WhisperSystems/TextSecure/issues/555). Is there any specification/documentation for dual-sim API provided by Fairphone so that other software could use it?

Textsecure (now named Signal), seems to provide dual sim functionality since the latest commit. Want to reconsider now to integrate it as the default messaging app? Would be great I think, as Signal seems to have promising future also as secure messenger.

https://github.com/WhisperSystems/Signal-Android/issues/555 was resolved and TextSecure/Signal now has dual-sim support. Sadly, it uses only official API which is available from 5.1 on.
Is there any specification on how dual-SIM API looks like on Fairphone 1? If it is, we could make support for it maybe into the TextSecure/Signal as well.


Init

Switch to yarn
Update sass version
Update Netlify toml NODE_VERSION

👷 Deploy Preview for ecstatic-rosalind-63612a processing.
🔨 Explore the source changes: 5ab34cc049e7dd7064479252c91c0faed3ee2eb5
🔍 Inspect the deploy log: https://app.netlify.com/sites/ecstatic-rosalind-63612a/deploys/621ba5e822658700077f6f4c


/subjects/queued endpoint is scrambling subject locations

Subject locations should match the order specified when the subject was created.
zooniverse/Panoptes-Front-End#3577 shows that this is fine for subjects requested by ID from the /subjects endpoint, but the array order is not being preserved for subjects requested from /subjects/queued.

I've done some minor digging. Looks like SubjectSelectorSerializer.page({}, Subject.where(id: 6532831)).to_json exhibits this issue. But not SubjectSelectorSerializer.resource({}, Subject.where(id: 6532831)).to_json.

@marten i've got a PR up to solve this, #2294


Understanding: Using Dart Frog with Discord and Twilio

Description
I'm designing a server for facilitating communication between coordinators and families at https://continual.care and I'm unsure whether or not I'm using this tool correctly.
This is what I'm seeking to do:

I'm envisioning that we can instance a new server for each conversation, with the inputs of discord channel and phone number. Logistically, does that make sense? I imagined using something like a brick to generate this.

I've read through a few issues

#223
#142
#226
and I'm wondering if I'm running into the same issue here : I'm attempting to connect to the discord channel upon startup and it doesn't seem to happen until I visit https://localhost:8080 . Is this because of these referenced issues?

Hi @Gene-Dana 👋
Thanks for opening an issue!
Yes, #226 is blocking you from being able to run arbitrary code on startup. I'm planning to get to this sometime next week but in the meantime I recommend using a piece of middleware to lazily establish a connection and cache the connection for the lifetime of the application. Hope that helps!

Okay ! Does the lazy creation in the middleware mean that this code is fired only once that route is visited?

Okay ! Does the lazy creation in the middleware mean that this code is fired only once that route is visited?

Yes 👍

Is there a way to fire a route without actually visiting it in a browser?
Also, is this a pattern that you would typically avoid? If so, how?

Is there a way to fire a route without actually visiting it in a browser?
Also, is this a pattern that you would typically avoid? If so, how?

You need to make a request to the server for that endpoint. You can do that via cURL, visiting the url in the browser, etc...

Gotcha. This is just temporary anyways, so it doesn't matter too much ! Thanks !


fix: referred to axios via an absolute path to fix build error

I got an error when building my own project using TypeScript 3.1.6:
node_modules/circleci-api/dist/types/util.d.ts:2:36 - error TS2307: Cannot find module '../node_modules/axios'.

2 import { AxiosRequestConfig } from "../node_modules/axios";
                                     ~~~~~~~~~~~~~~~~~~~~~~~

Just changing how the code refers to axios seems to fix it, though!

That's super weird, not sure how the relative path got snuck in there... Thanks for the fix!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Texture from a GLuint texture ID

Hi,
I have an issue with the "new" way to render an external texture.
I was previously using the deprecated but working Stream way like this:
val stream = Stream.Builder()
    .stream(externalTextureId.toLong())
    .width(width)
    .height(height)
    .build(lifecycle)
cameraTexture = Texture.Builder()
    .sampler(Texture.Sampler.SAMPLER_EXTERNAL)
    .format(Texture.InternalFormat.RGB8)
    .build(lifecycle)
    .apply {
        setExternalStream(stream)
    }

But when moving to:
cameraTexture = Texture.Builder()
    .importTexture(externalTextureId.toLong())
    .width(width)
    .height(height)
    .sampler(Texture.Sampler.SAMPLER_EXTERNAL)
    .format(Texture.InternalFormat.RGB8)
    .build(lifecycle)

I have a green flickering issue:
https://user-images.githubusercontent.com/6597529/166959628-aa29a6bd-be74-44b7-a75b-fbba20cc4758.mp4
Do you have any idea why the first call works perfectly but not the second one?
Thanks

See https://github.com/google/filament/issues/5498 for the solution

Hi,
I have an issue with the "new" way to render an external texture. I was previously using the deprecated but working Stream way like this:
val stream = Stream.Builder()
    .stream(externalTextureId.toLong())
    .width(width)
    .height(height)
    .build(lifecycle)
cameraTexture = Texture.Builder()
    .sampler(Texture.Sampler.SAMPLER_EXTERNAL)
    .format(Texture.InternalFormat.RGB8)
    .build(lifecycle)
    .apply {
        setExternalStream(stream)
    }

But when moving to:
cameraTexture = Texture.Builder()
    .importTexture(externalTextureId.toLong())
    .width(width)
    .height(height)
    .sampler(Texture.Sampler.SAMPLER_EXTERNAL)
    .format(Texture.InternalFormat.RGB8)
    .build(lifecycle)

I have a green flickering issue: https://user-images.githubusercontent.com/6597529/166959628-aa29a6bd-be74-44b7-a75b-fbba20cc4758.mp4
Do you have any idea why the first call works perfectly but not the second one?
Thanks

Hi, @ThomasGorisse. Have you try the inporttexture api to sample an SAMPLER_2D opengl texture? it seems invalid after i import to filament

Hi @dandingol03
You can have a look at how we handle it for the AR Camera stream here: https://github.com/SceneView/sceneview-android/blob/main/arsceneview/src/main/java/io/github/sceneview/ar/camera/ArCameraStream.kt
Note that we still got some glitches maybe not due to Filament but more to our Camera position update.

thanks, i finally solve this problem. The reason i can't bind the opengles texture to filament side is that the filament texture i created is also associated with stream, after i remove that it worked

Hi @dandingol03 You can have a look at how we handle it for the AR Camera stream here: https://github.com/SceneView/sceneview-android/blob/main/arsceneview/src/main/java/io/github/sceneview/ar/camera/ArCameraStream.kt Note that we still got some glitches maybe not due to Filament but more to our Camera position update.

thanks, i finally solve this problem. The reason i can't bind the opengles texture to filament side is that the filament texture i created is also associated with stream, after i remove that it worked

Can you explain (show code) a little more?
It could interest us.

Can you explain (show code) a little more? It could interest us.

code below:
fun createTexture() {
  val textures = IntArray(1)
  GLES30.glGenTextures(1, textures, 0)
  val result = textures[0]

  val textureTarget =  GLES30.GL_TEXTURE_2D
  GLES30.glBindTexture(textureTarget, result)
  GLES30.glTexParameteri(textureTarget, GLES30.GL_TEXTURE_WRAP_S, GLES30.GL_CLAMP_TO_EDGE)
  GLES30.glTexParameteri(textureTarget, GLES30.GL_TEXTURE_WRAP_T, GLES30.GL_CLAMP_TO_EDGE)
  GLES30.glTexParameteri(textureTarget, GLES30.GL_TEXTURE_MIN_FILTER, GLES30.GL_NEAREST)
  GLES30.glTexParameteri(textureTarget, GLES30.GL_TEXTURE_MAG_FILTER, GLES30.GL_NEAREST)
  return result
}

fun bindContent() {
  val externalTextureId = createTexture()
  val bitmap = BitmapFactory.decodeResource(resources, R.drawable.basic_color)
  GLES30.glBindTexture(GLES30.GL_TEXTURE_2D, externalTextureID)
  GLUtils.texImage2D(GLES20.GL_TEXTURE_2D, 0, bitmap, 0)
  GLES30.glBindTexture(GLES30.GL_TEXTURE_2D, 0)
}

fun import2Filament() {
  filamentTexture = Texture.Builder()
      .width(resolution.width)
      .height(resolution.height)
      .levels(1)
      .sampler(Texture.Sampler.SAMPLER_2D)
      .format(Texture.InternalFormat.RGBA8)
      .importTexture(externalTextureId.toLong())
      .build(filamentEngine)
}

mat change:
change the type of videoTexture in lit.mat from samplerExternal to sampler2d

@dandingol03 Thanks a lot!

I've met the question as you too.Thank you for your solution.


Derive monoids and semigroups

An idea by @deepfire - we could use generic-deriving in PartialTypes to derive monoids and semigroups.
We could also do it by using http://hackage.haskell.org/package/generic-monoid which is what seems simpler.

Sounds like we won!


Fix performance issue in progress bar

Instead of logging the metrics in parallel during the pipeline run, they are logged sequentially so that the worker threads are not split.
Fixes #667
Description of what I changed

E2E test

TESTED:
The pipeline batch run is tested after and before the fixes. Below are the statistics.
Testing made in a 24 core machine for 8K patients.

Checklist: I completed these to help reviewers :)

[x] I have read and will follow the review process.

[x] I am familiar with Google Style Guides for the language I have coded in.
No? Please take some time and review Java and Python style guides.

[x] My IDE is configured to follow the Google code styles.
No? Unsure? -> configure your IDE.

[ ] I have added tests to cover my changes. (If you refactored existing code that was well tested you do not have to add tests)

[x] I ran mvn clean package right before creating this pull request and added all formatting changes to my commit.

[ ] All new and existing tests passed.

[x] My pull request is based on the latest changes of the master branch.
No? Unsure? -> execute command git pull --rebase upstream master

@chandrashekar-s Thanks for the changes. Did we test with 8k patients and can you please share the performance benchmarks before and after this change. By before, I meant before progress bar was introduced.


AttributeError: 'MyCustomLogger' object has no attribute 'experiment'

Bug description
I have a custom logger subclassing lightning.fabric.loggers.Logger that was working in 2.0.3, but now fails in 2.0.5 with this error:
 File "/opt/conda/lib/python3.10/site-packages/lightning/pytorch/trainer/call.py", line 78, in _call_setup_hook
 _ = logger.experiment
 AttributeError: 'MyCustomLogger' object has no attribute 'experiment'

It seems from lightning 2.0.3 to 2.0.5, a requirement was introduced for Logger instances to have an experiment attribute, in lightning/pytorch/trainer/call.py _call_setup_hook(trainer):
# Trigger lazy creation of experiment in loggers so loggers have their metadata available
for logger in trainer.loggers:
    _ = logger.experiment

However, this new property is not specified as required in lightning.fabric.loggers.Logger, and as my custom logger does not have that property, it causes an AttributeError.
Adding a dummy experiment = None property to my logger resolves the issue.
What version are you seeing the problem on?
v2.0
How to reproduce the bug
This works in 2.0.3, but fails in 2.0.5 with `AttributeError: 'MyCustomLogger' object has no attribute 'experiment'`:

from lightning.pytorch.loggers import Logger

class MyCustomLogger(Logger):
    @property
    def name(self) -> Optional[str]:
        return ''

    @property
    def version(self) -> Optional[Union[int, str]]:
        return None

    @rank_zero_only
    def log_metrics(self, metrics: Dict[str, float], step: Optional[int] = None) -> None:
        ...

    def log_hyperparams(self, params: Union[Dict[str, Any], Namespace], *args: Any, **kwargs: Any) -> None:
        pass

trainer = Trainer(
    ...,
    logger=[MyCustomLogger()],
)

trainer.fit(...)

Error messages and logs
 File "/opt/conda/lib/python3.10/site-packages/lightning/pytorch/trainer/call.py", line 78, in _call_setup_hook
 _ = logger.experiment
 AttributeError: 'MyCustomLogger' object has no attribute 'experiment'

Environment

Current environment
- Lightning Component: Trainer, Logger
- PyTorch Lightning Version: 2.0.5
- Lightning App Version: 2.0.5
- PyTorch Version: 2.0.1
- Python version: 3.10
- OS: Linux
#- CUDA/cuDNN version:
#- GPU models and configuration:
- How you installed Lightning: pip
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response
cc @tchaton @justusschock @awaelchli @borda @Blaizzy

@austin-bowen
I'm sorry, I assumed that since all our loggers have this experiment property implemented, we had it as part of the base class. We can modify this code here
https://github.com/Lightning-AI/lightning/blob/00496da92d9e7d17c81f51c9abfb54583ba2817f/src/lightning/pytorch/trainer/call.py#L82C1-L85
to check whether the attribute exists and only call it when it does.


Selectable Api Server endpoints aka ExposureClasses [Part 4]

How to categorize this PR?
/area control-plane open-source
/kind enhancement
What this PR does / why we need it:
This PR implements the step 4 of the Selectable Api Server endpoint story. This story will be implemented in several steps, see: #3505 (comment) The previous PR can be found here: #3951 and here https://github.com/gardener/gardener/pull/4117
This PR adds an Admission Plugin for Shoots which will unite the seed selector and tolerations of the Shoot with the referenced ExposureClass.
Please check the implementation proposal for more details.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
I will open this PR as draft until my test completed but to gather already feedback.
Release note:

/invite @rfranzke @timuthy

/assign

/uninvite @timuthy due to OOO

Thank you @rfranzke for your review.
I have still to run a view test. Once this is done I will mark it as ready.

I have completed all test. This PR is meanwhile ready.
cc @rfranzke


Bug: Original filename isn't saved in UTF-8

What happened?
Steps to reproduce:

Upload a file with non-Latin letters in the name, for example: тест.png
Try to use {file.originalName}

Expected: тест.png
Actual: ÑÐµÑÑ.png
Checked the database, it gets saved with the wrong encoding there.
Version
upstream (ghcr.io/diced/zipline:trunk)
What browser(s) are you seeing the problem on?
No response
Zipline Logs
No response
Browser Logs
No response
Additional Info
No response

Does it affect zipline in any way? I saved the file with that original name and noticed no issues

I mean, it doesn't break Zipline, it just shows up gibberish in the Discord embeds.

I see, thanks for clarifying the problem.