Changes to enable FlowingLiquids module

The block data assigned to liquid information is currently only accessible via LiquidData, which restricts its uses in alternative systems. This PR adds getRawLiquid and setRawLiquid methods corresponding to all of the existing getLiquid and setLiquid methods. It also exposes as APIs 2 enums used for rendering that are necessary for the implementation of custom instances of BlockMeshGenerator.
API Changes
This PR only adds things to the engine API, so the only backwards-compatibility issue would be if modules implemented the extended interfaces, and these implementations became incomplete. This seems unlikely in these cases, but if it's a problem then it can just wait for v2.

Hooray Jenkins reported success with all tests good!

Poking some potentially interested reviewers. Linked with https://github.com/Terasology/FlowingLiquids :-)
Looks really cool, thanks for the work @4Denthusiast. Good heads-up on the API concern, luckily we are in v2 development so this is the perfect timing anyway. I ran a build test in a mega-workspace and nothing came up as problematic 👍

As justification for changing how chunks are marked dirty in WorldProviderCoreImpl.setBlocks, collecting them all into a list to avoid duplicates probably made it less efficient in the first place, as calling Chunk.setDirty multiple times is probably no more expensive than checking whether the updated chunk is already in the list. Also the code is neater this way.

Hooray Jenkins reported success with all tests good!

Another potential change which would be handy but also break the API more would be to not require acknowledgement of the previous liquid state in order to set a new one. That check doesn't actually seem that useful and it's mostly just a pain.

@skaldarnar @mkienenb The rendering-related APIs are exposed because FlowingLiquids replaces the normal BlockMeshGenerator on liquids with a custom one that deals with varying the height of the block according to the amount of liquid in it. In order to do this, it's necessary to refer to ChunkVertexFlags and ChunkMesh.RenderTypes in order to pass them to BlockMeshPart.appendTo. I agree that the current values seem quite ad-hoc, but I don't think that's enough of a reason to prevent their actual use in a module.
What do you mean by rawLiquidData being a hard-coded field on blocks? I'd be perfectly happy with it being renamed to something more generic (i.e. not referring to liquids, such as "extraData", which is what it's called internally in ChunkImpl).

As BlockMeshGenerator is itself API, it seems as though custom implementations of this are meant to be possible, but they currently aren't.

What do you mean by rawLiquidData being a hard-coded field on blocks? I'd be perfectly happy with it being renamed to something more generic (i.e. not referring to liquids, such as "extraData", which is what it's called internally in ChunkImpl).

I suspect that @skaldarnar means that it doesn't need to be part of the Chunk data but instead should be part of a component system. (stored in a Component).

@mkinenenb The problem with that would be that as water is so common, there could easily be over 10^5 liquid blocks loaded at once, which I expect would end up often using more memory from all those extra block entities, as well as taking considerably more time to access for liquid calculations. It might be worth benchmarking as I'm not really sure, but having a more lightweight way to store a small amount of per-block data seems sensible.

@skaldarnar may have made the same mistake that I made, thinking you were adding new data to chunk.   I see now that you are just changing how the byte used to construct LiquidData is made accessible.   There's only half-a-byte left free.
It seems to me that you have two options.   Either make the other half-a-byte available as extra-data for any system to use, or make it available as extra storage in LiquidData.
if you're going to make it generally available, then your getExtraData method (formerly getRawLiquid) has to prevent reading-from and changes-to the first 4 bits of the byte
Othewise, move the methods from Chunk to LiquidData and bit-shift access as appropriate.
I think either approach is fine, depending on how generous you want to be with potentially sharing the data storage space.  I'd probably put it in LiquidData myself.

@mkienenb The newest version (not yet pushed) of FlowingLiquids uses all of the bits available (and a few more would be useful, but that would mean moving up to short which would at least be its own discussion). When you say "LiquidData", do you mean org.terasology.world.liquid.LiquidData or org.terasology.flowingliquids.world.block.LiquidData? The problem I found with Terasology's LiquidData is that the encoding it uses makes only some bytes valid, losing usable space, and its encoding is non-trivial and unrelated to what I actually want to use it for, so going via LiquidData instead of directly is pointlessly inefficient. I also don't want to route things through LiquidData that would make it more essential, given that the feature it was clearly intended to support isn't actually implemented (and would in any case be itself incompatible with FlowingLiquids).
Trying to split up the available data into  portions for different systems to use on every block seems possible, but impractical, as the allocation of data would need to be managed to avoid overlaps between modules. A more sensible way to split the data would be to have each module that uses the extra data deal with some particular set of blocks (e.g. growth & nutrition information for plants or mineral composition of stones & ores), in which case it's reasonable to assume that liquids generally won't have additional functionality beyond flowing.
Anyway, I'll do the renaming & things.

I've tried to speak in general terms as I've never looked into the specifics of liquid support.  And anything I would have known about it would be 4-years out-of-date.

FlowingLiquids uses all of the bits available (and a few more would be useful

It was not possible to tell what you needed since your code wasn't committed :).   At the time I looked at the FlowingLiquids module yesterday, it only stored (more precise?) depth info in extraData.

given that the feature it was clearly intended to support isn't actually implemented

I was unaware that LiquidData/LiquidType was unused in the engine (and I'm guessing unused in modules).   I did wonder why it had a bit indicating water/lava since that seemed to duplicate info elsewhere.   If that's the case, you should rewrite the existing LiquidData (drop LiquidType?) in the engine instead of adding a second view of the data.    I think identifying what the data is used for is important for clarity rather than extraData.   Or instead of calling it liquid, call it FlowData if that more accurately describes what you are doing with it.   Liquid blocks could use flow-data one way, and air blocks could use flow-data a different way.   (wind simulation module!)
I wouldn't worry about adding API for some other kind of system to reuse the same data area at this time.
In summary:  if we're not using the extraData byte, use it but get rid of any of the unused code that previously referenced it.  And indicate what you're using it for.

And because intentions are not always clear in written communication, let me clarify that my intention is to enable you do this the best possible way, not to make your life difficult by putting unnecessary roadblocks in your path.   I apology that my misunderstandings and lack of knowledge in certain areas has dragged this out.

Unrelated side note:  I wonder if liquid flows could be more effectively computed using a gpu shader?

So I'm going to perhaps also recommend another change.
Currently the only two bits of data you cam store on a block are Biome and Liquid data. I'm proposing to change this to allow modules to set additional data points into them. For instance, if I wanted to do a heat simulation I could set Heat Data onto the block.
In doing this the liquid and biome data would be merged into this new field.
If we still keep the existing Liquid data and Biome data methods then the api would be backwards compatible as well.

More discussion on slack about providing per-block storage.
Reviewing https://forum.terasology.org/threads/modding-per-block-storage-extensions.806/ and https://github.com/mbrotz/Terasology/tree/per-block-storage proposal

Yeah this is becoming a fun little brainstorming topic :-) Sorry to drag out your PR @4Denthusiast !
The big question in the short term would be whether to continue on this path with a right-now improvement and sidelining a potential extra-block-data project for sometime down the road or wait to do both at once. I'm not sure. Might depend a bit on how well @mbrotz's code has aged and how good a fit it would be for current needs. I miss that guy, he should totally come back! ;-)
For a bit more background info: way back in the early ages the engine-level liquid block data was used for the very first round of propagating water. That was eventually removed/broken and the SimpleLiquids module was the most recent attempt at re-implementing before this PR, and didn't use the engine system at all.
For a little while @LinusVanElswijk (DizzyDragon) also had a really cool finite water project going, also led to a "game of life " simulation-in-a-chunk. That was sometime between the loss of the original engine support and SimpleLiquids. I think that might have used the engine system but it has been so long I'm really not sure.

Here's manually-cleaned up diffs of @mbrotz's work.
Four files.
per-block-storage-patch.txt is a patch file of changes against currently-existing files.  Some of them looked like they would merge without issues.  Others would need more work.
per-block-storage-patch.txt
ModInfo-patch.txt contains changes that need to be applied to gestalt or reworked to be supported by gestalt.
ModInfo-patch.txt
persistence-patch.txt shows changes made to the old way of persisting data.   These would have to be rewritten to the new way to persist data.   Might be trivial.  Might be difficult.  The old files were replaced in this commit:
persistence-patch.txt
AdvancedConfig-patch.txt allows you to configure per-block-storage.   Might not be needed.  If it were needed, it'd need to be folded into the new FlexibleConfig.
AdvancedConfig-patch.txt

After sleeping on it, I realized there had to be a better way to make the changes available.
Here it is:
https://github.com/MovingBlocks/Terasology/compare/a7584d11bd94fc60d399424f6b813699fe1b2b6d...mkienenb:per-block-storage

Assuming #3476 is merged, this is no longer relevant. The remaining small parts not relating to data access have been made a separate PR: #3477.


Properly initialize datasetWithout$ and attachments$

Description
Short description of the pull request
Motivation
Background on use case, changes needed
Fixes:

Items added

Changes:

changes made

Tests included/Docs Updated?

[ ] Included for each change/fix?
[ ] Passing? (Merge will not be approved unless this is checked)
[ ] Docs updated?
[ ] New packages used/requires npm install?
[ ] Toggle added for new features?
[ ] Requires update of catamel API?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
8 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 72.516%

Files with Coverage Reduction
New Missed Lines
%

src/app/shared/modules/shared-table/shared-table.component.ts
8
69.43%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
3484

Relevant Lines:
4391

💛  - Coveralls

Oh, sorry I must have missed these variables.


Minor refactoring.

Open Question:

As per issue #1 should this project be considered an extra?

@BrandonArp any remaining heart-burn over this?


ModuleNotFoundError: No module named 'ConfigParser'

Hi!  Tried to run your agent but found an error - "ModuleNotFoundError: No module named 'ConfigParser'" - seems that this file was not committed
ah, okay - it's python 2.7

Sure! 😄
Hey! please checkout the dev branch of this repository. It contains recently updated code with improved model performance. It also provides docker support for running the code directly.

thank you!   I will definitely look at it!


command not found in Ubuntu 17.04

Did you fix this?

Adding "home/.local/bin/get-pomodori" to the enviroment variable PATH fixes command not found error in Ubuntu.


PCs and NPCs pronouns

Character elements need to have a line for pronouns in the frontmatter so that they appear in the summary block together with their portrait, goals, etc,

Pronoun added to NPC info table and Synopsis (both PC and NPC).
Required the frontmatter pronoun: set to 'T'/'S'/'H' (They/She/He)
Release in v0.3.12


Add block-by-id and id-by-height consensus endpoints

This PR adds 2 endpoints.

the /consensus/blocks/:id endpoint which allows a user to retrieve a whole block by id
the /consensus/headers/:height endpoint. This might return the whole header in the future but only returns the BlockID at the moment.

I chose 2 separate wildcards since one endpoint returns a block and the other one is mostly used to return information about the block. In the future we might also add /consensus/blocks/:height or consensus/headers/:id in case it becomes necessary.

Maybe you want add IDs(hashes) as keys then?
I think this is really useful. Since external apps cant calculate it on demand like it work in Sia wallet.
Using it for explorer.siahub for example.
https://github.com/NebulousLabs/Sia/pull/2046

I believe this violates a standard API goal, which is that you should be able to fetch what you need in a single API call. If you want a block at a given height, you currently need to make 2 queries, one to get the header, and then another to get the block resulting from that header.
Some people want to be able to get the raw block. Some want to be able to get the json block. Some want the header, and some want the id. I think we might be able to return all 4 things (potentially a fifth if we return both the raw header and the json header) each block. It means that a query has a lot of data, but typically if you are making a query for a block you are expecting a lot of data.
I'm guessing @lukechampine has some thoughts.

I think it is not unreasonable to have 1 wildcard for blocks and 1 for headers. That way you can get a whole block by id and height and also just the header by id and height. At the moment the header endpoint only returns the id and the consensus/blocks/:height and consensus/headers/:id endpoints are missing, but that can be extended/added on demand.

@DavidVorick and I discussed this offline and we agree that a single endpoint is probably the best approach. For now, it will support only two query params:
/consensus/blocks?id=foo
/consensus/blocks?height=1

Later, we can add a &raw=true param for returning base64-encoded binary blocks, and perhaps startheight and endheight params for returning a range of blocks. (That's why it's blocks and not block.) But for now, just those two are fine.

is there any chance to have this PR rewritten (in terms of documentation only) and merged?


Wireguard 'Table = off' should be an option in the GUI

There is a very useful Wireguard Interface option called 'Table' that allows you to control what routes get inserted into the kernel routing table when a wireguard interface is brought up. Table = off allows a tunnel to accept AllowedIPs = <IP_ADDRESS>/0 without also making itself the default gateway. This is critical for situations where you have routing over a wireguard tunnel (say with FRR), but don't want the wireguard tunnel to be a default gateway...you just want it to behave like a point-to-point link.

There is already Disable Routes checkbox acailable

That box does not do what Table = off does.

Looks like the conf template is supposed to set Table = off, but it doesn't appear to be working for me.

So when you tick the checkbox the Table = off is present in your wgX.conf?

Okay so yes, it does appear that Table = off is present in my wgX.conf. It seems that when disable routes is checked, it is mandatory to also create a gateway and define it under the advanced wireguard>local configuration. Which begs the question, why is the disable route option not also hidden behind the advanced configuration switch if it is useless without also defining a gateway?


⚠ Bofrost.at has degraded performance

In fadc691, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 901 ms

Resolved: Bofrost.at performance has improved in 825b6e1.


Add an option to crawl the latest published version

Reffy crawls the latest Editor's Drafts of specifications. It may be useful to crawl the latest published versions of W3C specifications instead to make sure that the "published" Web platform does not have inconsistencies.

Option created. I also added a new "w3c-tr" report to the list of reports generated by npm run all, and pushed first version in reffy-reports.
@dontcallmedom, could you adjust your cron job to also update that report?

Closing the issue as reports now include the "w3c-tr" view.


[IOTDB-3512] Region leader during heartbeat

Coverage decreased (-0.03%) to 44.082% when pulling 54f960599c5fe1bbf274847606f8b439fc49dfdd on jira3512 into a7466e551a1e6aef41ab45d1630b611f6ed33097 on master.


Run And Parameters Tabs

Overview

Update the UI
Mapping the parameters with swimpy_functions_mapping.md file

Thanks for this, will merge and amend on the swim-dashboard branch!


starting guess for solve

SciPy's iterative solvers like scipy.sparse.linalg.cg optionally accept x0, a ‘starting guess for the solution’.  This could be passed to skfem.utils.solver_iter_krylov or similar, but in some situations, e.g. a transient simulation with unchanging evolution operator, the previous solution might be a good guess and this changes at each time.  One could reconstruct the solver at each time step (saving the preconditioner and other constant options), but maybe it would be tidier to be able to pass x0 directly to skfem.utils.solve after the LinearOperator A and right-hand side b?

Resolved by #304 .


footer section not working properly

I have noticed in footer section , while clicking on any of the option signup page is opening only , want to improve this , please assign me this issue under GSSOC'23

I want to work on this Project. Plzz assign it to me.

Yeah..I know..Contact us and testimonials page is already assigned to someone..So, if you want to work on a particular button in footer section and redirect it there instead of sign-in page?

Yeah..I know..Contact us and testimonials page is already assigned to someone..So, if you want to work on a particular button in footer section and redirect it there instead of sign-in page?

Yes

Hey @MonalikaPatnaik ,
In the footer I would like to work on contact us page, please assign it to me if no one is working.

hey @MonalikaPatnaik I would like to work upon directing it to the social sites pages as they are not working

Contact Us page is already assigned...and there are no social sites as of now!


Introduce OTEL_EXPORTER_OTLP_TRACES_PROTOCOL for traces

This PR addresses the deprecation of otlp_proto_grpc and otlp_proto_http in the python SDK v0.36b0. OTEL_EXPORTER_OTLP_PROTOCOL is set default to grpc. We set default for traces as http/protobuf

Why do we need to set the default instead of using python's default?

Why do we need to set the default instead of using python's default?

The current default behavior of the lambda instrumentation is to use OTLP/HTTP for traces due to that setting in the wrapper. Leaving that to  default gRPC may be a breaking change for users who had a collector configuration listening for HTTP and not gRPC.

Ok, I think we should consider that breaking change. But that shouldn't hold up this PR since it isn't changing the behaviour, I'll bring this up separately.


Added override EOL option for JS , JSX

What does this implement/fix? Explain your changes.
[+] Added override EOL option for JS (Supported js-beautifier and Pretty Diff)
[+] Centralized getDefaultLineEnding code and supported alias CRLF, LF parameters.
[-] Removed unnecessary comment. [#issue , #TODO in js-beautifier.coffee]
Does this close any currently open issues?
Issue 1457
Previously, this error had been reported by affanshahid in Issue Issue 1009
Any other comments?

I've closed the previous pull request since the scope was changed.
Could @Glavin001 explain to me, how do I make EOL option only appears in Javascript and JSX configuration? (Currently, This option appears in multiple places such as ' Vue , CoffeeScript and so on.')
options.md file which I've commit seem to be incorrect (too many deletions). This mean I have to manually integrate new one from a generated file, is that right?
if I have language-babel installed as Atom-package, it seems atom-beautifier always prioritize JSX over JS even though it is .js file. This will cause the selected language become JSX as well as using JSX configuration.

Checklist
Check all those that are applicable and complete.

[ ] Merged with latest master branch
[ ] Added examples for testing to examples/ directory
[ ] Travis CI passes (Mac support)
[ ] AppVeyor passes (Windows support)

Could @Glavin001 explain to me, how do I make EOL option only appears in Javascript and JSX configuration? (Currently, This option appears in multiple places such as ' Vue , CoffeeScript and so on.')

So far what you have done looks correct. It is likely a result of using fallback in those languages, such as Vue and CoffeeScript, etc.

options.md file which I've commit seem to be incorrect (too many deletions). This mean I have to manually integrate new one from a generated file, is that right?

I expect insertions, not deletions. You should be able to automatically generate the options.md file complete, even if you delete it first. No manual changes required, in fact manual changes would be highly discouraged.

if I have language-babel installed as Atom-package, it seems atom-beautifier always prioritize JSX over JS even though it is .js file. This will cause the selected language become JSX as well as using JSX configuration.

I'm not yet sure what to do about this. It is rather an Atom grammar bug in the sense that JavaScript files should be recognized as JS not JSX. However, I am not sure how this is decided. After Atom determines the grammar, then Atom-Beautify uses it. Therefore, this is out of Atom-Beautify's hands and the issue lies in either the language package or Atom itself.

I expect insertions, not deletions. You should be able to automatically generate the options.md file complete, even if you delete it first. No manual changes required, in fact, manual changes would be highly discouraged.

I just found out that EOL option in js-beautifier seems to be the cause. Could you review on js-beautify.coffee and check if I have applied global language option correctly.

I expect insertions, not deletions. You should be able to automatically generate the options.md file complete, even if you delete it first. No manual changes required, in fact, manual changes would be highly discouraged.

I think I understand why the document is generated that way.
In beautifier.coffee, there is one logic which I don't fully understand yet.
    if @options._?
      **globalOptions = @options._**
      delete @options._
      # Only merge if globalOptions is an object
      if typeof globalOptions is "object"
        # Iterate over all supported languages
        for lang, options of @options
          #
          if typeof options is "boolean"
            if options is true
              **@options[lang] = globalOptions**
          else if typeof options is "object"
            @options[lang] = _.merge(globalOptions, options)
          else
            @warn("Unsupported options type #{typeof options} for language #{lang}: "+ options)

because of this code, if I used
    _:
      eol: ['end_of_line', (end_of_line) ->
        if (end_of_line == 'CRLF')
          '\r\n'
        else if (end_of_line == 'LF')
          '\n'
        else
          null
      ]

in js-beautifier.coffee then everything will become mess up. This because globalOptions(aka. _ ) will replace previous options object that retrieves from the setting (if that language is set to 'true' in beautifier).
This mean, I can't use ( _ ) to initiate the value but I have to put it somewhere else, right?

I expect insertions, not deletions. You should be able to automatically generate the options.md file complete, even if you delete it first. No manual changes required, in fact manual changes would be highly discouraged.

It seems there is something wrong with my code. If I didn't put eol under ._ in js-beautify.coffee and instead I've put it like this in function beautify()
    end_of_line : options.end_of_line
    options.eol = (end_of_line) ->
        if (end_of_line == 'CRLF')
          '\r\n'
        else if (end_of_line == 'LF')
          '\n'
        else
          @getDefaultLineEnding('\r\n','\n')

then everything seems to be alright. However, If I use the code as I had commit then the generated file will be broken as you saw.
I also found out something amiss, when I debugging to view option arguments that pass to prettydiff.coffee in Atom-beautify current published version. I saw that there aren't any values from setting option in function beautify unless you'd declared its first as a global option.
so, in order to get those options, I have to put the code like this
options: {
._ :
default_beautifier : default_beautifier
.
.
.
}
Do you have any idea why it becomes like this? Instead of merge parameters from settings, it seems to discard all setting parameter unless I've predefined every option I required as I mentioned above.

@Glavin001 , I have changed my logic to make EOL option not to override those options in setting and update the document.
please review and let me know if there's anything need to be changed.

Thank you for contributing!

Published to v0.29.20


Re-organizing src/progress.rs

https://github.com/pingcap/raft-rs/issues/125
Divide src/progress.rs into src/progress/{mod.rs, inflights.rs, progress.rs, progress_set.rs}

Thank @Fullstop000
why do you close it?

It extends my own repo's branch not pingcap's so this includes a lot verbose commits which should not be pushed😂.  I'll make another PR instead.


refreshAndListen for Providers

Is your feature request related to a problem? Please describe.
Yes, see my meanwhile closed issue here.
In short: With Firestore persistenceEnabled and relistening to a StreamProvider gives me as first value the cached (and probably not current anymore) value and only in a second event the current docs or its changes.
In some cases however i need the most recent value from database in the first event.
I already mentioned that calling
ref.refresh(contractorAccountsStreamProvider('contractorId'));

on disposing the provider seems to solve the issue (invalidate does not work), but you told me not to do that at this point.
Describe the solution you'd like
What about a new function call 'refreshAndListen' which does refreshing (and therefore not deliver a cached value as first event) and after that listen to the mentioned provider in one step?
Since the listen action then gets the most recent value from the database the refresh performed before does not have to retrieve that value as well, it just should make sure that the provider does not deliver a cached value and therefore behaves as if it was listened to for the first time.
Describe alternatives you've considered
Mentioned above but not advised to do that.
Additional context
If you have another and/or easier way to handle it please let me know.

I'm really struggling to understand the problem here.
And since I don't understand the problem, there's no way for me to evaluable whether this proposal makes sense.
Could you please reformulate the problem in something clear, not firebase specific?

It also took me quite some time to understand it.
Since the problem is tied to Firestore's caching feature i have to explain my problem by including it.
When disposing a stream provider (marked with .autoDispose) on e.g. leaving a view and therefore the provider has no listeners anymore the connected stream of a Firestore collection is not reset/disposed as well, which means that on relistening the stream provider (by entering the view again) it gives me in the first notification the cached list of elements from when the disposal happened (.isLoading is false btw.) and only in a second notification the current list of elements (or changes when i'm interested in docChanges).
This seems to be normal behaviour, therefore i've closed the other ticket.
But in my case for certain views i have to rely on that i get the most recent list of elements in the first notification of the relistened stream provider (as if a would listen to it for the very first time) and not in one of the subsequent notifications.
That's why i tried e.g. to refresh the mentioned stream provider in order to get rid of a cached version when relistening it.
Since doing that when disposing it is not a good idea i thought why not doing that right before (re-)listen the stream provider (and where a view needs it), and here we are with my feature request.
I hope you understand now my problem.

I'm sorry but I still don't understand what you've described.
To begin with, I don't understand how to use your example. So I can't follow what you say
It'd really help me if you could do a normal "bug" report, with steps to reproduce. Abstract explanations of the problem in English won't help.

Hmmmmm, well it's not a (Riverpod) bug anymore to me, that's why i've switched to this feature request.
I "just" need a way to tell a stream provider's underlying stream to behave as if it was started again when relistening the provider. This is what ref.refresh(myStreamProvider) seems to do, that's why i came up with this request.
If you have Firebase available on your side i could send you a list of steps to do.

Ok i guess that my feature request can be skipped.
Today i debugged my test application and also entered Riverpod's code.
For some reasons the stream provider doesn't seem to be disposed when the view (model) is disposed, although i see it in the list of providers to be disposed.
Only when i manually call mayNeedDispose() in the view model (which i probably also shouldn't do) it works:
_ref.onDispose(() {
    print('disposing...');   _ref.container.readProviderElement(contractorAccountsStreamProvider('contractorId')).mayNeedDispose();
    });

If i do that i see these 4 states to be disposed:

The stream provider appears twice there. I don't know if something goes wrong while disposing the first one or if there are actually two stream providers which need to be disposed.


Links on introduction page don't work on website

On this website the links that link locally within the site don't work - unless you browse to the site using this url.
Fails: https://lucascheller.github.io/VFX-UsdSurvivalGuide/
Works: https://lucascheller.github.io/VFX-UsdSurvivalGuide/introduction/overview.html

They seem to to link to for example: ../introduction/motivation.md which takes the site from:
https://lucascheller.github.io/VFX-UsdSurvivalGuide/
to:
https://lucascheller.github.io/introduction/motivation.md
As such I assume the link has to be changed to introduction/motivation.md or alike. I wanted to create a PR for that. However, the current link does work in the previews on Github and will likely break the other URL that does work currently. As such I wasn't sure what the preferred way of fixing it was and instead opened this issue. :)

Hey, thanks for flagging it. I don't have time to look into it in the next two weeks as I'm taking a small break after Siggraph. I'll look into it after, should hopefully be an easy fix.

Should be fixed now, the links broke because the page was used as the index.html and introduction/overview.html at the same time. I moved the introduction/overview to be the index.html and redirectred the old page to index.html, that should hopefully do the trick :)


does not connect to localhost:9200

hi
Kopf does not connect to localhost:9200 on ELK 5.0.0.alpha4.
Probably not (yet) supported ?
tnx Ron

hey,
I assume you are running kopf either as standalone or directly from the public URL(as ES >= 5.0 won't allow you to install site plugins).
In this case, you would need to allow CORS on your ES config(check https://github.com/lmenezes/elasticsearch-kopf/issues/358 for example)


tee -p hasn't been implemented

$ ./target/debug/coreutils tee -p
error: Found argument '-p' which wasn't expected, or isn't valid in this context

       -p     diagnose errors writing to non pipes

Used by https://github.com/coreutils/coreutils/blob/master/tests/misc/tee.sh#L83=

This ticket can be marked as closed as it's PR has been merged.


Can't access .dev domains on port 80

I've been using Pow without problems for a long time, and today, suddenly, it stopped working. I tried reloading, restarting, rebooting, reinstalling, everything I could. I can't access my .dev domains.
Not on port 80, anyway. When I explicitly state foo.dev:20559, it works fine. But not without it.
I tried doing  sudo pfctl -f /etc/pf.conf; sudo pfctl -e, but it doesn't work. I get a message:
pfctl: Use of -f option, could result in flushing of rules
present in the main ruleset added by the system at startup.
See /etc/pf.conf for further details.

No ALTQ support in kernel
ALTQ related functions disabled
No ALTQ support in kernel
ALTQ related functions disabled
pfctl: pf already enabled

Not sure if it's normal.
I'm on Yosemite.
Any clues?

Okay. I figured it out. Looks like this app: https://github.com/SelfControlApp/selfcontrol was screwing with pf.conf. Works now, anyway. ¯_(ツ)_/¯


feat: unocss module

This PR should make the use of unocss with WXT a fair share easier, see reference issues: #522 #1026
Makes the need for this obsolete: #596
@aklinker1 Any way we can have the vite:devServer:extendConfig have entrypoints as well because then I can get rid of the "Entry module not found." warning you will get when it runs over entrypoints you don't want to use.
Also I am a bit uncertain but I think that unocss.entrypoints should be required so that you don't run it on files where it's not used, what's your opinion?

@Timeraa I made some changes to simplify things:

Convert entrypoints to excludeEntrypoints and use entrypoint names instead of paths
Add configOrPath option to pass config into the vite plugin
Added plugin to demo extension for testing.

Any way we can have the vite:devServer:extendConfig have entrypoints as well because then I can get rid of the "Entry module not found." warning you will get when it runs over entrypoints you don't want to use.

There isn't unfortunately :/. I see the warning you're talking about, don't know how to remove it.

Also I am a bit uncertain but I think that unocss.entrypoints should be required so that you don't run it on files where it's not used, what's your opinion?

I think leaving it as optional is fine. I added a default of ["background"] for it, so at least the background will be automatically removed. The majority of the time, people will use unocss in most entrypoints. The main reason to add a CSS framework is because you've got lots of CSS, and you want to use it. So I'm not too concerned about that. Someone will create an issue, we'll point them to the line in the docs about it, and everyone else will see that as well.
I have plans to clean up Vite's logs in general, after that it should be possible to improve the warning message and tell them to add the entrypoint to excludedEntrypoints.

Ignore the failing Continuous Publish / build check, that happens for new packages.

Everything looks fine to me!


[Secure JSON RPC] Added a missing README file for the lightweight JsonRpcClient.

Motivation
This PR adds the missing README file to the secure json-rpc directory. This file gives a brief overview of the secure json rpc client and should help readers better understand the role the client plays in our ecosystem.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Viewed the file locally in markdown and everything appears to render correctly.
Related PRs
None.

Thanks, David! 😄

/land

:broken_heart: Test Failed - Build images and run cluster test

FYI - We hit DockerHub's rate limit in LBT. LBT is unplugged for now.  Please re-land when you are ready.

FYI - We hit DockerHub's rate limit in LBT. LBT is unplugged for now. Please re-land when you are ready.

No worries! Thanks @sausagee!

/land


Build error following README tutorial

It appears that the requirements for interface names has changed since the README steps were written. It now fails to run if an interface name doesn't begin with an I.
Steps

Follow along with the README through to creating a new component.
Run the project with npm run start.

Expected
App should run with new Hello component rendered.
Actual
App fails to compile with the following error in the browser.

Failed to compile
…/my-app/src/components/Hello.tsx
(3,18): interface name must start with a capitalized I
This error occurred during the build time and cannot be dismissed.

Workaround
I haven't used enough TypeScript to know if this is an appropriate workaround, but renaming the Props interface to IProps (and its usage) will resolve this issue. I suppose there could be a setting somewhere that can be changed to start ignoring this error instead, but I'm just getting started with this tutorial.
export interface IProps { … }

…

function Hello({ name, enthusiasmLevel = 1 }: IProps) { … }

Additionally, this also affects the class-based variant of the Hello component as well as later examples working on this component.

Judging from this response to the PR I submitted, the workaround may not be valid. Is there some way to tell TypeScript to allow non-I interfaces so these instructions work again?

This is because of tslint, not the ts-compiler. In general any tslint error such as styling issues prevent running the program. I posted a similar issue for this, but there hasn't been a reply yet. A workaround is to remove all content from tslint.json, meaning no rules are then enforced for tslint.

That's good to know. It seems like there must be a disconnect between the default tslint settings and the TypeScript contribution guidelines. I've bailed on picking up TypeScript, but there is probably a single tslint rule that could be altered rather than the entire linting process.
In the case of this tutorial, either set of steps should probably be added to help new users.

Same thing is happening to me right now. Thanks @kaba2.

@dieferrari Probably a matter of restarting "npm start", if tslint reads its config once when started?

So, a barrier to entry here...
I did the same, found this issue, now 🤷♀

Ran into this as well. The tslint rule that is causing this is https://palantir.github.io/tslint/rules/interface-name/.
You can add a rule to tslint.json that disables linting interface names. Here's the contents of my working tstlint.json file:
{
  "extends": ["tslint:recommended", "tslint-react", "tslint-config-prettier"],
  "linterOptions": {
    "exclude": [
      "config/**/*.js",
      "node_modules/**/*.ts"
    ]
  },
  "rules": {
     "interface-name":[false]
  }
}

@linelson very good. Not sure why tslint is so strict. It's a bit of a hinderance. Who cares if the interface doesn't start with 'I'

Not sure why tslint is so strict. It's a bit of a hinderance. Who cares if the interface doesn't start with 'I'.

Well, the idea is of the rule is good (see Rationale): Makes it easy to differentiate interfaces from regular classes at a glance.
Perhaps it's not such a big issue with Props, but it can save a bit of mental processing time elsewhere.


Race condition when playing/pausing audio

Checklist

[X] I read the troubleshooting guide before raising this issue
[X] I made sure that the issue I am raising doesn't already exist

Current bug behaviour
When AudioPlayer.pause() is called a short time after AudioPlayers.play() is called, the pause will not take effect. The sound file will play in its entirety.
Same goes for AudioPlayer.stop() instead of .pause().
Expected behaviour
When pause() is the latest call to an AudioPlayer, the audio doesn't play.
Steps to reproduce

Execute flutter run on the code sample
Play any sound from the Sources tab. You'd expect the audio won't play since it's paused 5 milliseconds after being played. But in fact, it plays to completion.

Code sample

Code sample
Go to the official example's lib/tabs/sources.dart file and replace the _play() method with the following:
  Future<void> _play(Source source) async {
    await player.stop();
    Timer(const Duration(milliseconds: 5), () {
      // Imagine this is a handler to some event that
      // happens independently.
      player.pause();
    });
    await player.play(source);
    toast(
      'Set and playing source.',
      textKey: const Key('toast-set-play'),
    );
  }

Affected platforms
Android, iOS, web, Windows, Linux, macOS
Platform details
No response
AudioPlayers Version
main, 5.2.0
Build mode
debug
Audio Files/URLs/Sources
No response
Screenshots
No response
Logs
No response
Related issues / more information
Note that everything works as expected if you do something like:
await player.play(source);
await player.pause();

But in an app or game, events come from different sources. For example, settings can be updated (read from file) on startup, at almost the exact same moment as music is started. This can lead to the following:

Game starts
Game asks for settings (async)
Music starts (because that's the default) --- play(...)
Settings are finished reading from something like shared_preferences, and they say "no audio"
Music is immediately asked to stop --- stop()
Music continues to play indefinitely because the stop() finishes before the play() can get to the resume() step

FWIW, I couldn't replicate the behavior when using resume() (i.e. the source is already loaded). So I think the problem stems from the steps included in the play() method, which is not atomic.
Related Discord discussion: https://discord.com/channels/509714518008528896/533299043686940692/1168866344742162463
Working on PR
no way

Despite my arguments on Discord (no network, error, etc.) I think it's more consistent to set the state at the beginning before any async processing is happening (as you proposed). If an error occurs the the playing state should be reset. Tests for both of the cases should be included, if possible.

FWIW, I couldn't replicate the behavior when using resume() (i.e. the source is already loaded). So I think the problem stems from the steps included in the play() method, which is not atomic.

Now that I think about: setting the source simply takes much longer than just doing the resume, so pause is called before finishing setting the source in the event loop. So it might not even help to move setting to playing state at the beginning of the resume method.
So we may introduce another variable, which stores the intention to play and check it if it's still valid right before the native resume call.

That works for me, thanks!
FWIW, my current workaround is something like this:
  Future<void> _playCurrentSongInPlaylist() async {
    _log.info(() => 'Playing ${_playlist.first} now.');
    try {
      await _musicPlayer.play(AssetSource('music/${_playlist.first.filename}'));
    } catch (e) {
      _log.severe('Could not play song ${_playlist.first}', e);
    }

    // Settings can change while the music player is preparing
    // to play a song (i.e. during the `await` above).
    if (!_settings!.audioOn.value || !_settings!.musicOn.value) {
      try {
        _log.fine('Settings changed while preparing to play song. '
            'Pausing music.');
        await _musicPlayer.pause();
      } catch (e) {
        _log.severe('Could not pause music player', e);
      }
    }
  }

@filiph can you confirm that #1705 fixes your issue? Thx ;D

I'm not able to run this at this time to confirm, but looking at the code and at the test — yes, this will solve my issue.


Change version of async dep to ~2.6.3 for IE compatibility.

@Atinux
We've been sorting out the Node and IE compatibility issue in https://github.com/Atinux/schema-inspector/issues/77. By now, we've reached consensus that version 1.6.9 of schema-inspector accidentally had breaking changes because of its udnerlying async dependency.
I think moving from the version 3 branch to version 2 branch of async is a great next step because it resolves the breaking changes issue and async's maintainers have committed to maintaining their version 2 branch with IE compatibility and it will receive patches for CVEs until further notice: https://github.com/caolan/async/issues/1661#issuecomment-634374314
This PR changes us to 2.6.3 of async, and should keep us on the version 2 branch because of specifiying ~2.6.3. It doesn't use ^2.6.3, because we don't need new async features, just patches for CVEs. The PR does not increment the version of schema-inspector, because I notice you do the version increment in separate commits, so I'm respecting that pattern.

@mattwelke great work opening the review 👏
@Atinux can we get this approved and release a hotfix 🙏

@Atinux  ☝ :prettyplease:

Can someone accept this?

Released, sorry for delay, my wife had our newborn child last week

No problem. Thanks for releasing this today. And congratulations!

@Atinux Yes! We'll be using this library at my work for the foreseeable future and it seems to have a narrow, stable focus that will be easy to maintain without too many feature requests.
@jcdesousa may be interested too.

Invited!
Could you also tell me you npm username?

@Atinux NPM username is the same as my GitHub username: mattwelke. I recently remade my NPM account since I used to use one that was shared between personal stuff and my work stuff. So this new one is completely separate from my work stuff and should be safe to use for open source. Let me know if you'd like me to create a dedicated NPM account though. I've never maintained an open source project so I'm not familiar with best practices for NPM accounts for them yet.

No worries, just added you :)


prototype: reusing an open telemetry instrumentation module

This PR is a prototype for reusing an open telemetry instrumentation module in the Node.js Agent.
At a high level, to reuse these instrumentation, we need to

Create and register a delegate trace provider
Create and register a delegate tracer for starting spans
Create a delegate span object that wraps our elastic-spans
Instantiate the Instrumentation Class

Since we're starting spans with the agent APIs, our current context handling should be sufficient to handle this.
Possible cons here include

These instrumentation classes are not covered by any of the OpenTelementry GA backwards compatibility guarantees -- we may be signing up for a lot of upkeep if these classes change how they work (or go away completely).  We'd probably want to hard-pin the opentelemtry dependencies

Unknown perf. implications -- the base OpenTelemetry instrumentation classes do a bunch of extra work to register metrics handlers (and other work). We'd probably want to feature/config flag this feature as experimental and do load testing.

Next steps:

Move the trace provider out of the individual instrumentation
Test with a few more open telemetry instrumentation modules
fully implement the interfaces for our delegate objects
test assumptions about span context handling

Summarizing a conversation with @trentm -- we'll have some extra work to do here re: startSpan and the active context.  Elastic's Node.js Agent automatically makes a started span the active span, whereas OpenTelemetry does not.  It becomes the active span in OpenTelemetry via trace.setSpan -- you can see the sequelize instrumentation do this here
const newSpan: Span = self.tracer.startSpan(`Sequelize ${operation}`, {
                kind: SpanKind.CLIENT,
                attributes,
            });

            const activeContextWithSpan = trace.setSpan(context.active(), newSpan);

If an instrumentation is doing some complex things like starting span but not immediatly making them active we may end up with odd ball results.
Supporting Span.spanContext() may also be tricky -- we'll need a mock/delegate object for this at minimum.
Also,

Our agent.setSpan() can return null (e.g. if there is no current transaction). OTel has a concept of a NonRecordingSpan() for this. We'd need to handle that case.


Forwarding refs to -component in ffe-form-react

Which package is this issue related to: ffe-form-react
Describe your issue (screenshots welcome!)
This is more of a technical feature request. I am working on another internal component at SB1, that adds managed formatting to an input. I want to use the Input from ffe-form, but need to access the DOM ref to manage selection/cursor position. I currently achieve this with ReactDOM.findDOMNode().
There are two potential ways to improve this:

Give Input a new property inputRef, that takes a callback and passes it to ref on the contained .

Upgrade to React 16.3.0 and use the new forwardRef API.

If there is consensus on such a change, I could make a PR.
BR, Preben Ludviksen

Input spreads all given props except className, inline, and textLike (which are used to build the className value) to the input element, so I think what you need is supported already.
const Input = ({ className, inline, textLike, ...rest }) => {
    return (
        <input
            className={classNames(
                'ffe-input-field',
                { 'ffe-input-field--inline': inline },
                { 'ffe-input-field--text-like': textLike },
                className,
            )}
            {...rest} {/* <-- This stuff right here */}
        />
    );
};

So if you set a ref property on Input in your code you should get the ref for the input element.
<Input
   inline={true}
   textLike={true}
   ref={_ref => { this._refs.input = _ref; }}
/>

I thought the ref prop was kinda magic and never actually passed to the component, like key?

Oh, I see.
Then it would be nice to use the new forwardRef feature from React to avoid reinventing the wheel with a custom prop. That means a breaking change, but it's a no-hassle upgrade so it should be fine I'd say :)

+1 on the forwardRef approach. I'll submit a PR shortly - I have a few minutes to spare anyways, and I've longed for an excuse to try out this API =)

So I've fixed this in the PR, but enzyme (our React testing framework) doesn't support the feature yet.
I've fixed this temporarily by disabling tests for two components, but I'm not sure if this is good enough for a merge. The fix is merged to master, but not released yet (hasn't been for 3 months).


bittrex.ltd

https://www.reddit.com/r/CryptoMarkets/comments/6wmod5/bittrex_phishing_alert_pls_upvote/

Google was fast on this one


Where does the magic happen with fragment ViewModels?

It works fine with API 19 and higher, but I'm converting it to API 15 and got it to work except for the automatic ViewModel loading that this solutions seems to have somewhere.... Where does the ViewModel instance come from (ie; the LoginViewModel), because it suddenly is created after Fragments base.OnCreate(savedInstanceState) ?
I can do it in "public override void Show(MvxViewModelRequest request)" like normal, but I realy want to know how its done at your end.
PS: I'm using a fork of the 3.5 MVVMCross.

I suspect you need to look at the generics that where introduced in 3.5 and in this example after #2

@martijn00 I used this example after #2 and there isn't anything to find that loads the ViewModels (like viewModelLoader.LoadViewModel(request, mvxBundle) ).
And also I'm using the 3.5 MVVMCross version, so I haven't got a clue where its going wrong.

I think it would be better if you explain your problem on StackOverflow so we can discuss it there. But anyways, this is how the MvxFragment looks like in this example:
public class MailListView : MvxFragment<MailListViewModel>
As you can see the MailListViewModel is used as generic parameter. MvvmCross hereafter does the loading in the code. You don't see anything for that in your own code.

@martijn00 Your right, lets continue on StackOverflow because it seems to be more a MVVMCross thing


docs: add a microunit design draft

Try to formalize the design of microunit.

Let's merge this and add more details later.


feat(CX-3203): Add Tracking For Inquiry Tap and Sent

The type of this PR is: Feature

This PR resolves CX-3203
Description

Adds the necessary interface for tracking ConsignmentInquiry button tapped and ConsignmentInquiry sent

PR Checklist (tick all before merging)

[x] If I've added a new file to the tree I've exported it from the common index.ts
[x] I've added comments with examples for any new interfaces and ensured that they're in the docs
[x] No platform-specific terminology has been used outside of click and tap (platform is inferred by the DB storing events)

:rocket: PR was released in v4.84.0 :rocket:


Cannot open popups in Excel Web Addin project

Hello,
I am working on an Excel Addin project using asp.net core 3.1. I want to open a popup to enable users to log in to the system. I use window.open("url") but this always returns null regardless of the fact that I already disable popups blocker in IE.
I am using Excel 365, Window 10 enterprise version 1809, Internet explorer version 11.1577.17763.0
Can anyone provide me some hints on this issue?

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

ID: 00c430f1-bbf5-53b8-a225-4fbe8fc39c3b
Version Independent ID: 0a069a0d-4d35-71ee-53af-8c55fe8548a0
Content: Browsers used by Office Add-ins - Office Add-ins
Content Source: docs/concepts/browsers-used-by-office-web-add-ins.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

We use the issues of this repo to track errors in the documentation. For technical programming questions, like this, please ask on Stack Overflow and be sure you tag your question with office-js. In this case, we recommend that you use our Dialog API for log in.

We use the issues of this repo to track errors in the documentation. For technical programming questions, like this, please ask on Stack Overflow and be sure you tag your question with office-js. In this case, we recommend that you use our Dialog API for log in.

Thank you for the instruction. I will post the question in Stack Overflow.

Thank you for the instruction. I will post the question in Stack Overflow.


[Docs] Clarify Saved Data Location on Mac

Currently, this section of the docs exists but is blank. New users might not understand how to view hidden folders, but @JohnGriffiths explained that this is done as part of an existing convention.
Location in Docs: https://neurotechx.github.io/eeg-notebooks/getting_started/loading_and_saving.html?highlight=saving#macos
Full Clarification for location on Mac:
You can find recording files for all experiments in a folder called .eegnb in the User's Home folder, as seen in the following screenshot.

I like the language already in place for the windows file location:

The default directory is found at the location C:\Users*USER_NAME*.eegnb an example of which is pictured below.

On Mac, the default directory is found at the location [HDD]/Users/Richard/.eegnb/data, as seen in the picture below.
[Use Picture Attached to this Issue]

John suggests maybe just copying this data to the Documents folder.
It's still important for data to be stored in these hidden folders, as this is a standard used by applications.

@retiutut - do you need any help / pointers / discussion in implementing this?

I think there is enough info here to implement a solution.


preprocessors are not invoked when resolving dependencies

jest-resolve-dependencies does not seem to make use of preprocessors, so if you're using something like https://github.com/mwolson/jest-webpack-alias it will not work for watching tests and jest -o.
Is there some other way to work around this?

Not really, this is by design because we cannot make this run efficiently otherwise. In this case you can run jest or jest <pattern> to match against tests you would like to run. I don't recommend using jest-webpack-alias; please try out the moduleNameMapper feature instead.

Just saw the backreference ability, that would work. Thanks!


feature request - better coin control and transaction visibility

@cryptolawjunkie on telegram suggested that having better visibility of the available transactions within an address would be really good. Particularly when making payments from a wallet which contains stake addresses - would be nice to know in advance which transactions will be used and what will remain in the source address afterwards. Seems like a very good idea.

@nikmit thank you for the suggestion, but could you describe it a little bit more?
For sending funds from staking addresses has Arizen "Batch Withdrawal" method - which allows you send all funds over a selected threshold (e.g. 42 ZEN).

Sorry for the late response - must have missed the response notification. Yes - the "Batch Withdrawal" method should do it. Should have checked what's available myself before submitting this here :)


Minnesota Light Rail App

Guys I've got what you have all been waiting for A MINNESOTA LIGHT RAIL APP!! This simply has the user input the STOPID and Station Name from their local station which can easily be obtained from the metro transit website. I have the URL in the schema section so the user easily knows where to go to find station name and STOP ID.  The app then grabs depatrure time from the Metro transit API and displays that also along wiith the color of the train line and the 3 letter destination as well!
Fair warning i submitted this through the github Desktop App so if things are messed up please let me know. I'm trying it a different way this time as I learn the wonderful world of git! GIFS and pics attached so you know what this bad boy looks like!

HI @betterengineering

Lint keeps failing, but build and test passed. Im sure its formatting related, but i cant for the life of me get buildifier to work on vscode? if you have any advice id greatly appreciate it.

Hi @AmillionAirs. Happy to help out with the lint. However, there's another issue we're going to have.
It looks like we're using the NexTrip version 1 API here, and that's going out of service very soon:

NOTICE: NexTrip version 1 (https://svc.metrotransit.org/nextrip/) is deprecated and will be removed at the end of June '22.
Version 2 documentation can be found at https://svc.metrotransit.org/swagger.

(from svc.metrotransit.org)
Could you please switch to the V2 API?

Alright sir i went ahead and updated all the calls for ya! let me know how that goes

O jeez i was messing around with a new app i made and i guess it committed that to this project? any chance we can just remove the countdown app stuff im not sure how to do that im so sorry.

TAKE THAT LINT!!!!

Great, merging now. I think a good improvement to add before a big release would be caching the data for at least 30 seconds.


[Contextual Menu] Can inspect running instances of a ComponentType

Can inspect running instances of a ComponentType when right click a component type.

Two point of view:

static - list of implementors
dynamic - running instances


Challenge http://www.freecodecamp.com/challenges/waypoint-add-borders-around-your-elements has an issue

I'm getting a error "Your image should have a border with a width of 10 pixels." In my code i have 10px border color green and solid..

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.

This seems to be passing in Safari, Firefox and Chrome on Mac. I don't know what issue you are experiencing.


Move connect and disconnect to gateway topic and set retain=1

On Gateway connect:

publish ConnectMessage on <gateway-id>/conn topic (retained=1)
set will to DisconnectMessage on <gateway-id>/conn topic (retained=1)

This way, the bridge can see whether the gateway is connected or disconnected when it restarts.
Unfortunately, it's not possible to detect wheter a protobuf is one or the other, so we will need a ConnectDisconnect message with a oneof.

Having a pub/sub broker to track connection state feels a bit hacky but it is going to work.
If it really is the connection state, why not using a message with a boolean field whether the gateway is active/available?

In my opinion the pub/sub broker already keeps track of the connection state, so this proposal only adds a way to inform the bridge of this state (and of the auth information). The bridge also needs the auth information from the gateway (which is stored in the connect message) in order to start the connection with the backend.
The proposed solution is the most elegant solution I could think of. Let me know if you have a better solution that (a) informs the bridge of the connection state and (b) informs the bridge of the information needed for auth and (c) survives restarts.

Ideally, the less hacky approach imo, is that (a) and (b) are handled by the authentication plugin on connect/disconnect, and (c) on reconnect, and it reports this not through the pub/sub messaging but through another endpoint. It depends on the concerning broker whether an authentication plugin is capable of this and here lies the constraint. So it is going to work, and it is portable across brokers, so let's do it.

iceboxing this for now


GH-113 Added link to edit pages

Fixes #113

This will use https://github.com/rtCamp/gitbook-plugin-edit-link:

:+1:

👍


Password with a pipe

I guess this was Murphy waiting to pop up or I have to brush up mos dos skills
When there is a pipe symbol the command line complains as this is a special character
fore example:
service.exe install -username:domain\accoount-password:abc|def -servicename:servicename
Is it currently possible to use passwords with a pipe symbol in them?

Does quoting work?
Pipe usually has a special meaning in Consoles/Shells.
(Piping stdout to stdin of a second tool)
C:\Windows\System32>echo bla
bla

C:\Windows\System32>echo bla|bla
bla not found

C:\Windows\System32>echo "bla|bla"
"bla|bla"

@buckleyGI did the quoting help? That is a CMD type issue more than likely. If I don't hear back in 30 days (4/21/2015) I will close the issue. Thank you. :)


The server hangs, but does not crash

Describe the bug
When you run the command, the server stops, but does not crash.
To reproduce
command /zulfbungeetest:
    trigger:

        broadcast "&aPrinting all players on the bungeecord network..."
        broadcast "&b%all bungeecord players%"

        broadcast "&aPrinting the name of this client:"
        broadcast this server's name

        broadcast "&aSending all players on the network a message through iteration..."

        loop all of the bungeecord players:
            proxy message loop-proxyplayer the message "&b&oWhy hello there! I am a message!"

        broadcast "&aPrinting all the servers connected to the proxy..."
        set {_servers::*} to all of the online servers

        broadcast "&b%{_servers::*}%"

        broadcast "&aSending all servers a message (this is used for inter-server communication)..."

        loop {_servers::*}:
            proxy message loop-value the message "Sample Text" called "Sample Title"

        broadcast "&aSetting a network variable..."
        set network variable {zulfbungee::test::*} to 1, 2, 3, 4 and 5

        broadcast "&a...adding to it..."

        add 6 to network variable {zulfbungee::test::*}

        broadcast "&a...and printing it! Expected values should be 1 through 6."
        broadcast "%network variable {zulfbungee::test::*}%"

        broadcast "&aDeleting that variable... :("

        delete network variable {zulfbungee::test::*}

        broadcast "&c&lCongrats! The test is done! Please send results back!"

Expected behavior
The variable appears as  and `Congrats! The test is done! ‘Please send results back!’ appears and the server stops.
Screenshots
No screenshot but error in the message
Spigot server information (in this order)

Plugin version : 0.9.9-pre4
Minecraft Version :git-Pufferfish-22 (MC: 1.20.1)
Skript Version : 2.6.4
Java Version : 17

Proxy information (in this order)

Proxy Type : Velocity
Plugin Version : 0.9.9-pre4
Minecraft Version : 1.20.1
Java Version : 17

Additional context
# - Key Setup -

# This chooses what communication method ZulfBungee uses.
# pluginmessage requires no setup, but requires you to enter a connection name (see below).
# socket requires more setup but allows for more flexible setups.
# Generally, if you don't know what this means, leave it as pluginmessage.
transport-type: "pluginmessage"

# This will toggle the display of detailed messages about what is going to the console.
# When filing a bug report / checking for issues, this is extremely useful to know what exactly went wrong!
debug: false

# Enables or disables global scripts.
global-scripts: true

# - Socket Setup -

# This is the port that this server will bind to, which will it listen for incoming connections on.
port: 8000

# The IP that this server will bind to. Similar to the "client-host" in the Spigot config.
# This should usually be left as <IP_ADDRESS>, or <IP_ADDRESS>, but feel free to change this if you need to -
# (i.e. you are on shared hosting / Pterodactyl)
host: "<IP_ADDRESS>"

# - Storage -

# What kind of database should be used to store network variables.
# Currently, supported databases: MySQL, H2

# If you have no clue what this does, just leave this as the default.
storage-type: "MySQL"

# Skript by default is case-insensitive for variable names.
# If you want this functionality, enable it here.
case-insensitive-variables: false

# Each option should be self-explanatory if you know what you are doing.

# If you are using H2, this will not apply - these two settings only apply to remote databases like MySQL.
storage-host: "localhost"
storage-port: 3306

# !! Change these from the default to improve security !!
storage-username: "***"
storage-password: "***"

storage-database: "***"

# - MySQL Setup -

mysql-use-ssl: false
mysql-verify-certificate: true

Error Log
This log appears when you turn off the server.
[04:31:34] [Server thread/ERROR]: Nag author(s): '[zulfen]' of 'ZulfBungee v0.9.9-pre4' about the following: This plugin is not properly shutting down its async tasks when it is being shut down. This task may throw errors during the final shutdown logs and might not complete before process dies.
[04:31:34] [Server thread/ERROR]: Craft Scheduler Thread - 34 - ZulfBungee Stacktrace
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/jdk.internal.misc.Unsafe.park(Native Method)
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/java.util.concurrent.LinkedTransferQueue$Node.block(LinkedTransferQueue.java:470)
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463)
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434)
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/java.util.concurrent.LinkedTransferQueue.awaitMatch(LinkedTransferQueue.java:669)
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/java.util.concurrent.LinkedTransferQueue.xfer(LinkedTransferQueue.java:616)
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/java.util.concurrent.LinkedTransferQueue.transfer(LinkedTransferQueue.java:1256)
[04:31:34] [Server thread/ERROR]:   ZulfBungee.jar//com.zulfen.zulfbungee.universal.util.BlockingPacketQueue.offer(BlockingPacketQueue.java:16)
[04:31:34] [Server thread/ERROR]:   ZulfBungee.jar//com.zulfen.zulfbungee.spigot.socket.ClientConnection.sendDirect(ClientConnection.java:113)
[04:31:34] [Server thread/ERROR]:   ZulfBungee.jar//com.zulfen.zulfbungee.spigot.socket.ClientConnection.handshakeTask(ClientConnection.java:63)
[04:31:34] [Server thread/ERROR]:   ZulfBungee.jar//com.zulfen.zulfbungee.spigot.socket.ClientConnection$$Lambda$12211/0x00000008031906a8.run(Unknown Source)
[04:31:34] [Server thread/ERROR]:   org.bukkit.craftbukkit.v1_20_R1.scheduler.CraftTask.run(CraftTask.java:101)
[04:31:34] [Server thread/ERROR]:   org.bukkit.craftbukkit.v1_20_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:57)
[04:31:34] [Server thread/ERROR]:   com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22)
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[04:31:34] [Server thread/ERROR]:   java.base@17.0.1/java.lang.Thread.run(Thread.java:833)

more
As a result, both h2 and mysql show the same symptoms and work well in Release v0.9.8 version.

Latest pre-release might fix this!


Two usage problem

Description
There are two problems i found out in latest version.

Some warnings while create nodes in docker
Rabbit error while setup nodes in docker

Create nodes warning in docker
$ bin/cita  create --super_admin "0x4b5ae4567ad5d9fb92bc9afd6a657e6fa13a2523" --nodes "<IP_ADDRESS>:4000,<IP_ADDRESS>:4001,<IP_ADDRESS>:4002,<IP_ADDRESS>:4003"

Output:
/opt/cita/scripts/config_tool/create_init_data.py:101: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  data = yaml.load(cfg)
/opt/cita/scripts/config_tool/create_genesis.py:123: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  contracts_list = yaml.load(stream)
/opt/cita/scripts/config_tool/create_genesis.py:137: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  data = yaml.load(stream)
Initializing chain from provided state
/opt/cita/scripts/config_tool/create_genesis.py:308: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  data = yaml.load(stream)
INFO:cita.block	Block pre-sealed, 2246273 quota used
INFO:cita.chain	Adding to head head=4c29c1f1

Setup nodes error in docker
$ ./bin/cita setup test-chain/1

Output:
Start docker container cita_run_container ...
WARNING: Published ports are discarded when using host network mode
9cc92cb42e02170ef3ba43b4636b62bde0fb0ebd2ada4716193f3d9b53930850

$ ./bin/cita setup test-chain/2

Output:
Error: unable to connect to node rabbit@WPF: nodedown

DIAGNOSTICS
===========

attempted to contact: [rabbit@WPF]

rabbit@WPF:
  * connected to epmd (port 4369) on WPF
  * epmd reports node 'rabbit' running on port 25672
  * TCP connection succeeded but Erlang distribution failed

  * Authentication failed (rejected by the remote node), please check the Erlang cookie

current node details:
- node name: 'rabbitmq-cli-20@WPF'
- home dir: /var/lib/rabbitmq
- cookie hash: Fz6UWNE5Yqu++tcrPtCKxg==

Error: unable to connect to node rabbit@WPF: nodedown

Versions
Latest
Addition Information
I am not sure the reason it caused, may be my local environment or a system defect.

Some warnings while create nodes in docker

We'll fix this.

Rabbit error while setup nodes in docker

Remove the container and try again.

Rabbit error while setup nodes in docker

Remove the container and try again.

I have tried deal this way. Not worked, /bin/cita bebop setup test-chain/1 is ok.

/bin/cita bebop setup test-chain/1 is ok.

Stop the rabbitmq service on your own pc.


Add test related files to .vscodeignore

Test related files should not be bundled in VSIX.

Codecov Report

Merging #714 into main will increase coverage by 0.63%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #714      +/-   ##
==========================================
+ Coverage   94.43%   95.06%   +0.63%
==========================================
  Files         272      268       -4
  Lines       11445    11306     -139
  Branches       12        0      -12
==========================================
- Hits        10808    10748      -60
+ Misses        637      558      -79

Flag
Coverage Δ

#dotnet
95.06% <ø> (-0.14%)
:arrow_down:

#typescript
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...cep.Core.UnitTests/FileSystem/FileResolverTests.cs
71.69% <0.00%> (-28.31%)
:arrow_down:

src/Bicep.Core.UnitTests/Utils/CompilerFlags.cs
60.00% <0.00%> (-6.67%)
:arrow_down:

...Bicep.Core.UnitTests/FileSystem/PathHelperTests.cs
100.00% <0.00%> (ø)

src/vscode-bicep/src/language/client.ts

src/vscode-bicep/src/extension.ts

src/vscode-bicep/src/utils/telemetry.ts

src/vscode-bicep/src/utils/logger.ts


[DNM] [SDP-772] Rework metrics for TSS

What

Added a set of metrics for monitoring varying states of payment tx's in TSS - see here.
Modified transaction worker to report the new metrics as appropriate
Added codified grafana dashboard to visualize reported metrics.

Why
[TODO: Why this change is being made. Include any context required to understand the why.]
Known limitations
[TODO or N/A]
Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).
[ ] This PR's title starts with the name of the package, area, or subject affected by the change.

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[ ] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[ ] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr21.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr21.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr21.previews.kube001.services.stellar-ops.com


Feature request : currying

I would suggest to add in a future version the ability to have currying in function in order to be able to write such function calls :+1:
let dummy = myfunc(3, 6) {
        // something to do
}

with a function declaration sucha as :
function myfunc(a:number, b:number, c : ()=> void)

Essentially this is a variant of the existing JavaScript .bind() functionality and would be difficult to meet the design goals of TypeScript.  Of course that is just my personal opinion.

In what is it a variant of the bind feature?
By enabling my proposal , we could easily and clearly create Groovy-like builders, for instance to create such a code
´´´
body {
div {
a( href="anurl") {
..
}
}
}
Envoyé de mon iPhone

Le 18 oct. 2015 à 22:40, Kitson Kelly<EMAIL_ADDRESS>a écrit :
Essentially this is a variant of the existing JavaScript .bind() functionality and would be difficult to meet the design goals of TypeScript. Of course that is just my personal opinion.
—
Reply to this email directly or view it on GitHub.

Hey @xmehaut, check out a previous discussion of this on #486.


Gradle build error (Failed to resolve: com.github.dibakarece:dmaudiostreamer:v1.0.4)

When I insert the  dependency (compile 'com.github.dibakarece:dmaudiostreamer:v1.0.4' ) to build.gradle, it gives an error like below:
Failed to resolve: com.github.dibakarece:dmaudiostreamer:v1.0.4

Have you added
allprojects {
repositories {
maven { url 'https://jitpack.io' }
}
} In your global build.gradle


entire project lost!!

Describe the bug
i wans working on a site and an a site error occured (presumed your end) when reloaded my whole project was gon and it imported as new but lost everythin!
Link to the Bolt URL that caused the error
https://bolt.new/~/bolt-nextjs-shadcn-npnzam
Steps to reproduce
no steps
Expected behavior
NOT TO LOOSE MY PROJECT!
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 139746382,
  "usedJSHeapSize": 113203726,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = karlhfr
Chat ID = 8edc38449cc9

Additional context
No response

Sorry to hear this! Are you able to find your past project by as follows: Go to stackblitz.com, login (same credentials as Bolt), click Collections on the left-hand side, click Bolt Collection.
Alternatively, with that chat of interest open on Bolt, mouseover the left-hand side of the page to open the settings menu, click Settings, then open Backups and select a backup of interest to revert to that state.


Plugins: Couldn't open Assets/Firebase/Plugins/x86_64/FirebaseCppApp-6_10_0.bundle, error: dlopen(Assets/Firebase/Plugins/x86_64/FirebaseCppApp-6_10_0.bundle, 2): no suitable image found.  Did find: 	Assets/Firebase/Plugins/x86_64/FirebaseCppApp-6_10_0.bundle: code signature in (Assets/Firebase/Plugins/x86_64/FirebaseCppApp-6_10_0.bundle) not valid for use in process using Library

Please fill in the following fields:
Unity editor version:  2019.03.0f6
Firebase Unity SDK version:  6.10.0
Firebase plugins in use (Auth, Database, etc.): Auth, Database, Stroage, Messaging
Additional SDKs you are using (Facebook, AdMob, etc.): None
Platform you are using the Unity editor on (Mac, Windows, or Linux):  Mac OS 10.15.3
Platform you are targeting (iOS, Android, and/or desktop): Android, iOS and desktop
Scripting Runtime (Mono, and/or IL2CPP): Both
Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
I import the latest version of Firebase Unity SDK 6.10 to the project. When I press play button throws an error and pause the app and also popup a native waring message from os.
I also try to delete Firebase and reimport it but cannot fixed the issue.
Says “FirebaseCppApp-6_10_0.bundle”, Cannot open because the developer could not be verified.
macOS, cannot verify that this application does not contain malware.
If I build the project with MONO and IL2CPP both arm7 and arm64  selected there is no problem
I tried to resolve and  force resolve it return successfully but the problem is still there. I check the dll files on Plugin folder.
Here is the console log messages
Plugins: Couldn't open Assets/Firebase/Plugins/x86_64/FirebaseCppApp-6_10_0.bundle, error: dlopen(Assets/Firebase/Plugins/x86_64/FirebaseCppApp-6_10_0.bundle, 2): no suitable image found.  Did find: 	Assets/Firebase/Plugins/x86_64/FirebaseCppApp-6_10_0.bundle: code signature in (Assets/Firebase/Plugins/x86_64/FirebaseCppApp-6_10_0.bundle) not valid for use in process using Library
DllNotFoundException: FirebaseCppApp-6_10_0
Firebase.AppUtilPINVOKE+SWIGExceptionHelper..cctor () (at Z:/tmp/tmp.5kTaS2UUGh/firebase/app/client/unity/proxy/AppUtilPINVOKE.cs:117)
Rethrow as TypeInitializationException: The type initializer for 'SWIGExceptionHelper' threw an exception.
Firebase.AppUtilPINVOKE..cctor () (at Z:/tmp/tmp.5kTaS2UUGh/firebase/app/client/unity/proxy/AppUtilPINVOKE.cs:137)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.AppUtilPINVOKE' threw an exception.
Firebase.AppUtil.SetLogFunction (Firebase.LogUtil+LogMessageDelegate arg0) (at Z:/tmp/tmp.5kTaS2UUGh/firebase/app/client/unity/proxy/AppUtil.cs:64)
Firebase.LogUtil..ctor () (at Z:/tmp/tmp.5kTaS2UUGh/firebase/app/client/unity/proxy/LogUtil.cs:80)
Firebase.LogUtil..cctor () (at Z:/tmp/tmp.5kTaS2UUGh/firebase/app/client/unity/proxy/LogUtil.cs:36)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.LogUtil' threw an exception.
Firebase.FirebaseApp..cctor () (at Z:/tmp/tmp.5kTaS2UUGh/firebase/app/client/unity/proxy/FirebaseApp.cs:62)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.FirebaseApp' threw an exception.
LoginSceneManager.Awake () (at Assets/Scripts/LoginSceneManager.cs:79)
Please answer the following, if applicable:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)? Haven't tried yet
What's the issue repro rate? (eg 100%, 1/5 etc)
%100

Thanks for reporting the issue @ctykaya. It seems that this has something to do with your Unity setup. To resolve the issue, you can try the following:

Disable "Enable Auto Resolution" under Asset > Play Services Resolver > Android Resolver > Settings
Ensure that your JDK and SDK in your Unity Preferences are updated.

You can also follow along #559 and see if the developer's solution can apply for your case.
If none of these worked, please share a minimal, reproducible example of your project. You can do this using Google Drive via shareable link

Thanks @paulinon  I Disable "Enable auto Resolution" and force to resolve and re install the Unity with jdk and sdk packages but the problem continues. When I add a new project and import firebase sdk it works. What could I do to solve this problem?

You can try following along #514. There are various solutions in this thread that could help you out. You can also try making use of the quickstart to see if the issue still persists. If you're still facing issues, could you share a minimal, reproducible example of your project? Thanks.

@paulinon  I tried all advices at #514  but nothing helps. Here is the the link of google drive of the example project which you can reproduce the issue.  https://drive.google.com/file/d/1IMmJ3jPf8FOldBvzyjiEDtpJTKAYxm1z/view?usp=sharing

Hi @ctykaya. It seems that you're facing an issue with your OS (probably similar to #515). Firebase could be blocked for this case. Simply go to your Security and Privacy Settings and allow Firebase.

yepp @paulinon  thanks for your help. It works 👍


not an issue: feedback

hello Greg
Firstly, this is not an issue! Its more of understanding python constructors
thanks for sharing the example code. I am looking for a way to code a constructor which can be more modular. In your code, I see its a long function with quite a few things. How can I define some functions which constructor can call?
I tried calling other class methods but I am getting scope error (undefined)
such breakdown is more modular and maybe reusable elsewhere
thanks
Sriram

Sorry, try posting your question on StackOverflow.


Typescanner creates resources multiple times in load balanced environment

Hi,
I could not test this issue myself, but in an environment where there were no resources yet created and DbLocalizationProvider tried to create all 2051 resources defined in code, created 141 resources two times and 6 resources even three times. We have 6 servers, all were started paralelly.
I was hoping maybe you have an idea on this, is the registration load-balance safe? (Apparently there is no unique constraint on ResourceKey)
Using version 5.6.0 with Episerver.
Thanks!

hi,
indeed, it is tricky. will check where constraints gone. are you on dxc? this is gray area with almost no investment..

Not dxc, but there are multiple servers. Easy workaround could be maybe that only the server configured as event replication master can create the new resources - just an idea.

yes, there has to be some sort of sync primitive in between the servers. will need to look for something.. I like idea how webjobs and az functions do it - via storage blob blocking feature.

hi,
can you verify what indexes you do have on resource table?
https://github.com/valdisiljuconoks/localization-provider-aspnet/blob/master/src/DbLocalizationProvider.AspNet/LanguageEntities.cs#L56 should do the trick
.HasColumnAnnotation(IndexAnnotation.AnnotationName,
                     new IndexAnnotation(new IndexAttribute("IX_ResourceKey", 1)
                                         {
                                             IsUnique = true
                                         }));

Hi,
I only have the clustered index for the primary key on the resource table,
nothing else.
This new index IX_ResourceKey should work, thanks!
Regards,
Zsolt
On Sun, Aug 4, 2019 at 11:32 PM valdis iljuconoks<EMAIL_ADDRESS>wrote:

hi,
can you verify what indexes you do have on resource table?
https://github.com/valdisiljuconoks/localization-provider-aspnet/blob/master/src/DbLocalizationProvider.AspNet/LanguageEntities.cs#L56
should do the trick
.HasColumnAnnotation(IndexAnnotation.AnnotationName,
new IndexAnnotation(new IndexAttribute("IX_ResourceKey", 1)
{
IsUnique = true
}));
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/valdisiljuconoks/localization-provider-epi/issues/38?email_source=notifications&email_token=ALSGVLX4GFUX6VSXIORRXOLQC5DIFA5CNFSM4IIPS262YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3QKEFI#issuecomment-518038037,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALSGVLSPRQFUBXR7STEKNELQC5DIFANCNFSM4IIPS26Q
.


add implemented kinesis method describe_stream_summary

Dear moto team.
I added implementation of the describe_stream_summary method for kinesis.

Nice one


Exclamation mark in path ("../!/..") breaks java — "D:\Program Files\Warcraft III!\Wurst\WurstSetup.jar"

Hi,
First run of WurstSetup.jar crashed because I had a /!/ in the path. (I keep all my tools in a folder named "!", for example C:\Warcraft III\!\JNGP\ — but Java tools don't like that.) Workaround: I simply moved Wurst to \Documents\Wurst\ to fix the crash. Works fine now.
The crash was:
"Sorry, Exception occured :(" — SunAwtDialog — javaw.exe
Please report this crash with the following info:
Version: <IP_ADDRESS>-jenkins-WurstSetup-71
java.lang.IllegalArgumentException: input == null!
	at javax.imageio.ImageIO.read(Unknown Source)
	at ui.MainWindow$exitIcon$2.invoke(MainWindow.kt:42)
	at ui.MainWindow$exitIcon$2.invoke(MainWindow.kt:40)
	at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
	at ui.MainWindow.getExitIcon(MainWindow.kt)
	at ui.MainWindow.access$getExitIcon$p(MainWindow.kt:40)
	at ui.MainWindow$UI.<init>(MainWindow.kt:106)
	at ui.MainWindow$ui$2.invoke(MainWindow.kt:49)
	at ui.MainWindow$ui$2.invoke(MainWindow.kt:40)
	at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
	at ui.MainWindow.getUi(MainWindow.kt)
	at ui.MainWindow.init(MainWindow.kt:68)
	at ui.UiManager$initUI$1.run(UiManager.kt:13)
	at java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
	at java.awt.EventQueue.access$500(Unknown Source)
	at java.awt.EventQueue$3.run(Unknown Source)
	at java.awt.EventQueue$3.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.run(Unknown Source)

occured is spelled occurred, by the way :) Two r's. (The title of that SunAwtDialog above)
I make the same mistake all the time. One r feels right:
occur + ed
But I assure you (and myself over and over...) that it's two: google.com/search?q=occured vs google.com/search?q=occurred
occur + red

Another device, same problem:
The location I ran the jar from was again, not simple enough:
"D:\Program Files\Warcraft III\!\Wurst\WurstSetup.jar"
I continue to believe that the single exclamation mark in the path (as a folder name) is the cause. It's not handled properly. This is either a bug in a library (javax? kotlin? awt? security?) or Wurst (or java itself.)
After adding the "!" folder as a network drive to get a simpler path: "W:\Wurst\WurstSetup.jar", everything works!
(W:\ is symlinked to "D:\Program Files\Warcraft III\!")
Not sure if we want to even fix this at all. Ignore and forget as a Known bug.
Who else but me has folders named "!" after all? No one, that's who.
But definitely an interesting, unexpected crash.
Sincerely,
Daniel "3ICE" Berezvai
p.s.: Similar issue:
http://gex.eeve.org/board/viewtopic.php?f=23&t=3346
p.p.s.: Protip: Github escapes \! to !, so to keep \! you should instead write \\! (Oh, and and to write that last  \\! ... I had to actually write \\\\! haha double escape nightmare.)
p.p.p.s.: Github employee reading this, please compare:
Warcraft III!\Wurst (\!\ not escaped)
Warcraft III\!\Wurst (\!\ correctly escaped as \\!\)
And document accordingly. Thank you.
\\\\!\\)

Yeah, the exception is mysterious. I personally have not experienced it on several devices, and I'm not sure what's the cause.
Stack-overflow threads etc. don't yield any solution. Really strange.
Anyway thanks, I will take a look regarding the ! in filepaths. 👍


Support for wagtail 1.5

Have you tested it agaist Wagtail 1.5?
In my installation it shows the char input and no map appears. It loads only map-field.js, but it fails to insert a link to the google api.

Does it happen in wagtail 1.6?

It's happening to me with wagtail 1.9

Try with wagtailgeowidget instead, I think is very good.

@pyMan we have a Wagtail 1.9 site running with this at https://github.com/springload/madewithwagtail/blob/4512a1faddae5570518bb7a7c9a3b411ab7245b2/madewithwagtail/settings/base.py#L83, could you compare this to your set up and report back on what is different?

We've release v0.3 and formalised which versions are supported. Wagtail 1.5 isn't part of it but given this issue was quite old, I imagine this is no longer needed anymore.


docs: improve useContextProvider's wording.

Overview
Hey 👋
Typo, me confused. 😕
What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests / types / typos

Description
So so confused.
Use cases and why
Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

thanks @igalklebanov ! 🙏


lalal

stuff with *mark* **down**
*formatted* **heading** with [a](link)
---
{{stamdard 3-backtick code block omitted from here due to escaping issues}}
Collapsible until here.

stuff with *mark* **down**
*formatted* **heading** with [a](link)
---
{{stamdard 3-backtick code block omitted from here due to escaping issues}}
Collapsible until here.


refresh jwt token when it is epired

What would you like to be added?
When jwt token is expired, client app can't be recovered without deleting cookie
Why is this needed?
From the viewpoint of users, this is bad UX.

https://learn.microsoft.com/ja-jp/Azure/app-service/configure-authentication-oauth-tokens#refresh-auth-tokens


the UI does not show data after login

The  dashboard UI does not show any data after login. Sometime it just hangs/stucks after pressing login button with the secrete token .
We have installed the NodePort version of the k8dash (kubernetes-k8dash-nodeport.yaml).
Please check and assists at earliest .
OS : Ubuntu 16.04.5 LTS
root@ubuntu03: kubectl get svc k8dash -n kube-system
NAME     TYPE       CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
k8dash   NodePort   <IP_ADDRESS>           4654:31330/TCP   12h
root@ubuntu03:
Brower URL :
http://<IP_ADDRESS>:31330/#!
<IP_ADDRESS> is a worker node .
root@ubuntu03: kubectl get nodes --all-namespaces
NAME       STATUS   ROLES    AGE    VERSION
ubuntu01   Ready       5d2h   v1.16.2
ubuntu02   Ready       12d    v1.16.2
ubuntu03   Ready    master   12d    v1.16.2
root@ubuntu03:
root@ubuntu03:/new-softwares/metrics-server/deploy/1.8+# kubectl get pods -n kube-system
NAME                                      READY   STATUS    RESTARTS   AGE
calico-kube-controllers-dc6cb64cb-x97cv   1/1     Running   4          12d
calico-node-9zzkq                         0/1     Running   1          5d2h
calico-node-csx7b                         1/1     Running   4          12d
calico-node-p2lvb                         1/1     Running   1          12d
coredns-5644d7b6d9-7fpl8                  1/1     Running   4          12d
coredns-5644d7b6d9-l69xb                  1/1     Running   4          12d
etcd-ubuntu03                             1/1     Running   4          12d
k8dash-58c77f9d45-dg84m                   1/1     Running   0          113s
kube-apiserver-ubuntu03                   1/1     Running   4          12d
kube-controller-manager-ubuntu03          1/1     Running   4          12d
kube-proxy-46986                          1/1     Running   1          5d2h
kube-proxy-7cg6x                          1/1     Running   1          12d
kube-proxy-gzg2d                          1/1     Running   4          12d
kube-scheduler-ubuntu03                   1/1     Running   4          12d
kubernetes-dashboard-7c9d8bcbbc-wrk99     1/1     Running   3          10d
metrics-server-8fc66cfdf-mkfhv            1/1     Running   0          21s
root@ubuntu03:/new-softwares/metrics-server/deploy/1.8+#
k8dash pod logs
root@ubuntu03:/new-softwares/metrics-server/deploy/1.8+# kubectl logs k8dash-58c77f9d45-dg84m -n kube-system
OIDC_URL:  None
API URL:  https://<IP_ADDRESS>:443
[HPM] Proxy created: /  ->  https://<IP_ADDRESS>:443
[HPM] Subscribed to http-proxy events:  [ 'error', 'close' ]
Server started
(node:6) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.

I have resolved by creating the service account in the namespace kube-system instead of default. My metric-server is in kube-system
apiVersion: v1
kind: ServiceAccount
metadata:
  name: k8dash-sa
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: k8dash-sa
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: k8dash-sa
  namespace: kube-system