DRBG without derivative function and full entropy

The NIST standards talk about requiring full entropy when not using the df version. In NIST SP800-90C they have a General_DRBG_Generate that's a wrapper around DRBG_Generate that adds an extra full_entropy_request parameter. I was planning to just add that extra parameter to our generate function, but then I don't see how we would internally ever call it with that parameter set unless we have functions like get_entropy() also have that parameter. I currently don't see an other way to implement those requirements.

It's good to record this, but 1.1.1 is not the FIPS release :)  What we have is much much better than what we used to have.

The problem is that we support not using a DF, but the FIPS standard will only allow it for the current code with the master DRBG and with the callbacks changed. It will not work for a DRBG that uses an other DRBG as entropy source without changing the API.
@mspncp: Do you have any opinion on this?

My first thought is do we even need to support the full entropy request at all?  I've a recollection that it might be permissible to not have but if you do, you get the rest of the baggage.  Memory is fallible of course.
I'm even less sure about the DF part.  A question for the validation lab is the usual result.
My head always hurts when reading the 800-90's :(

My opionion to your specific question
As stated already in the review thread https://github.com/openssl/openssl/pull/5461#pullrequestreview-100987383, it is legal to disable the derivation function if one has a true random source with full entropy.

Assuming I have a hardware RNG device then I could replace the callbacks entirely and seed the DRBG using no_df. Same holds when I do external conditioning. So no_df is not useful for us at the moment but might be useful for others.

The RAND_DRBG is a building block for implementing a CSPRNG. In order to work correctly, it is necessary to obey the rules in the NIST standard. Of course it is possible for a programmer to misuse the API to create a non-cryptographically-secure random generator. For example the programmer could disable the derivation function without having a full entropy random source. But is our code able to detect this? Should we even attempt to detect it? There are thousands of places in our library where a programmer could misuse the OpenSSL API to produce lousy cryptography. But it is not possible and not feasible to check all cases. In the end, we have to trust the programmer to know what he is doing.
So it's perfectly ok to offer the no_df df flag without having a full entropy source yet. Because the developer might have one (e.g., a hardware TRNG).
My general opinion
We should take a break now from discussing DRBG issues and work with all our capacities on the 1.1.1 release. A lot of questions you are bringing up are related to a future FIPS evaluation. But the first and most important question is: What are the requirements of the FIPS certification? The NIST SP 800-90 documents provide recommendations, but it is not stated that all presented features need to be implemented. For example, the standard allows that a DRBG does not support prediction resistance. But if it supports it, it must follow the rules in NIST SP 800-90C. And there are many more features that might not be a must-have for FIPS certification.
I have never participated in a FIPS evaluation, so I know nothing about the procedure. I just know that the two Steve's who were involved in it are gone now. So who will figure out the precise requirements? Who answers questions like:

Is it required to support prediction resistance?
Is it required to provide a full entropy random output?
Is it required to offer the NRBG construction (Section 9 NIST SP 800-90C) which effictively turns a 'normal' DRBG into a full entropy random generator?

Will we just guess what is necessary and wait for the critics of the auditors? Or will we blindly implement every thinkable feature? Before starting to gallop we should be clear in our mind about the right direction. So we should pause for a few weeks to give everybody time to reread NIST SP 800-90A-C, and then start with a general discussion on openssl-dev. And not with very specific, narrowly focused pull requests.

Of course I meant 'openssl-project', not 'openssl-dev'.

I really like what you wrote, @mspncp

@kroeckx is this still an issue worth addressing?

I don't think this is worth keeping open.  We have the capability of using the derivation function or not (via OSSL_PARAMS) and it is enabled by default.
Closing.


Non-Immediate "Hey btw" kinda bug, already fixed just throwing it out there.

Issue description:
Display? Bug, made it seem like items in drives were gone
What happens:
It appeared as though all the items in my disk drive were gone, I couldn't view any items or take any items out, drive still read as 23k filled
What you expected to happen:
Items to still be there
Steps to reproduce:
Unsure if this will reproduce since I'm not willing to test it cuz my game takes ~15mins to relaunch. but this is what happened leading up to the issue

I dumped ~4k Inferium Essence into the system
I used the crafting grid + JEI Shift+ key repeatedly to turn them all into blocks, then dumped em back in the system
Repeated step 2 all the way up the tiers
Searched "essence" (still in the crafting grid) and the system showed that I still had 4k inferium essence, but none of the higher tier essences or blocks were showing under that search terms
Delete the search term expecting to see all my items again
Display is empty
Check wireless grid, grid, crafting grid, everything is showing empty
Panic
Save & quit then relaunch the game
Items now displaying as normal
...

Version (make sure you are on the latest version before reporting):

Minecraft: 1.12
Forge:
Refined Storage:
Latest version of the Stoneblock pack
Does this issue occur on a server? [yes/no]
no

If a (crash)log is relevant for this issue, link it here:
I can link it if you want it, but this isn't really an immediate issue.
[pastebin/gist/etc link here]

Basically just a display bug(or so I hope, I have to actually check and see if ALL my items are still there) Just throwing it out here in case other users experience it and it's something fixable :)

Sorry, I can't do anything with those reproduction steps!

I have 2 different users on my server that reported this issue to me today.  In both cases a client restart fixed it. There is nothing in the server log. Unsure of client logs as they have not sent them. We also attempted pulling out the drives to reinitialize, remove/replace all the system components but it did not help. Would be happy to give more info if it happens again. In both cases for me the users had been playing for hours when this occurred. We are using Forge .2760 and Refined Storage 1.6.5, Refinedstorageaddons0.4.2 and in case it matters... rebornstorage 1.12.2-<IP_ADDRESS>. Happy to help diagnose if you need something specific.

Oh I forgot about this thread until that notification popped up, I did have the issue happen to me again on the stoneblock pack(latest version as of yesterday so 1.0.9) and I tried removing & replacing drives, removing the controller, I tore the entire network down and put it back and still nothing, interacted with different grids & wireless grids and still nothing, changed dimensions, re-built it in the nether, and still nothing displayed, then a quick relog fixed it.

In order to further compile data on this issue and hopefully help @raoulvdberge find the bug, my modlist is here https://pastebin.com/jPJhn0KP. I would be more then willing to run a version that can give verbose logging if that exists.


Out of date

This content applies to the App Service Environment v2 which is out of date. A Zone redundant ASEv3 has improved this deployment pattern. This design should warn it is for the ASEv2 until it is updated to cater for a zone redundant ASEv3

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

ID: c59b0445-0fba-d12e-0c4f-600b9c97aad5
Version Independent ID: 2d9f8030-b696-651b-b37e-a96b841a4928
Content: Enterprise deployment using Azure ASE - Azure Reference Architectures
Content Source: docs/reference-architectures/enterprise-integration/ase-standard-deployment.yml
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @martinekuan
Microsoft Alias: martinek

@iaasazure
Duplicate of #https://github.com/MicrosoftDocs/architecture-center/issues/4090
We are going to close this thread as Duplicate https://github.com/MicrosoftDocs/architecture-center/issues/4090


Latest Step Functions choice operators are not available in 1.1.2 release

Version
>>> import stepfunctions
>>> stepfunctions.__version__
'1.1.2'

installed from pypi.
Expected
In this commit from 22 Sep 2020, new comparators were added to stepfunctions, including IsPresent. On 24 Sep 2020, the 1.1.2 release was published to PyPI. So I expected to see the new comparators available there. But,
What actually happens
is this:
>>> from stepfunctions.steps import ChoiceRule
>>> ChoiceRule.IsPresent()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: type object 'ChoiceRule' has no attribute 'IsPresent'

perhaps it would be possible to publish a new release with these features included? Thank you!

Hi @anatoly-scherbakov, as you noted, https://github.com/aws/aws-step-functions-data-science-sdk-python/pull/88 adds support for the new choice operators but is not yet released. We're working on a v2 release that will include this! Stay tuned.
#108

@anatoly-scherbakov - v2 has been released and includes support for the new choice operators.
Take a look at the release notes for details on upgrading and breaking changes in v2.0.0.
Resolving this issue, feel free to reopen if you have any outstanding questions!


Fixes LL-655

flush the (un)install when interrupted

https://github.com/LedgerHQ/ledger-live-common/pull/144

@Arnaud97234 finally it should be fixed 🤞

wtf

each time i push my branch, the PR closes \o/
i'll open a new PR


Feature Proposal: Specified Selector Subscription Model and Reference Model

Thanks for your submission!
Here are some guidance for submitting your issue.
Tell us why you are submitting?

[ ] I found a bug - here are some steps to recreate it.
[x] I have an idea for a new feature - please document as "As a user, I would
like to..."
[ ] I am having trouble getting setup, understanding documentation, or using
Loggregator in some way - please highlight any resources you are using.
[ ] This is an architecture change that will result in cleaner more efficient
code - Tell us why you think this is a good idea.

We review issues and PR's on a weekly basis and try to schedule and prioritize
items. If you are wondering about status of an item feel free to contact us on
our slack channel.
Problem Summary
Nozzle developers are forced to scale their nozzle for the full throughput of the Firehose even when only a small subset of metrics are of interest. This makes nozzle development inherently challenging and limits innovation of tooling from Cloud Foundry metrics. Additionally, the V2 Loggregator API has no reference nozzle or external consumption outside of Scalable Syslog
Solution Summary
Provide an ability to request Firehose subscriptions that filter out all unspecified content using the Loggregator v2 API endpoint from the Reverse Log Proxy. Develop a reference nozzle that uses the Loggregator V2 API and consumes only specified whitelisted metrics.
See feature proposal

This has recently shipped. Closing issue.


Unexpected character encountered

an exception of type 'Newtonsoft.Json.JsonReaderException' occurred in Newsoft.Json.dll but was not handled in user code.
Additional information: Unexpected character encountered while parsing value: <.Path ",line 0, position 0.

its the script that did it SchemaResult schemaResult = JsonConvert.DeserializeObject (result);

i think the problom is becuse this script chemaResult schemaResult = JsonConvert.DeserializeObject (result);
return schemaResult.result ?? null;

@vasd20 if you found a solution I would be happy if you could post it here. Otherwise please offer additional details so I could possibly reconstruct your issue or close this issue.
Thank you for any response


make modular kernel tree-shaker agnostic transformers

The modular kernel tree-shaker in package:front_end is breaking encapsulation: it contains hard-coded knowledge about methods that may be used by some transformations (like some helper methods for async/await).
Possible solutions to avoid this:

declare used members in transformers: this might be exposed as methods in kernel.Transformer and kernel.Target that, given a program/CoreTypes, they return a set of members that are expected to exist.
transformers inject an external declaration for members used: this might not be that easy to for modular transformers though.

/cc @kmillikin

We are not planning on using the tree-shaker for some time, marking this as low-priority for now.


mapping_code_{sp} and streams_{sp} symbology for resident species when HYDRO (dams) are involved

For areas like the KOTL watershed group, all streams are above dams.  We deal with "resident" fish populations so still need to have map symbology that helps us understand connectivity in the watershed group.
In the current symbology specs for the bcfishpass qlr DAM is involved.  Guessing this is meant to be HYDRO....  @smnorris - is the DAM in the symbology of the streams layer meant to be HYDRO ? Is this issue already dealt with somehow for places like the ELKR watershed group - https://github.com/smnorris/bcfishpass/issues/110 ?
Editing the qgs project file or a layer specific qlm to swap out DAM for HYDRO in the mapping_code_{sp} columns of the bcfishpass.streams layer for resident species of interest such as bt and wct allows us to see symbology but shows everything upstream of the dams as blocked so does not symbolize connectivity above the dams (see screenshots below).  Potential path forward?:

Modify the streams_{sp} layers for resident species of interest so when a DAM is involved for bt, wct(rainbow too soon hopefully) the stream still shows as orange (like MODELLED). Save the qlm as a streams_above_dams or something like that and then apply to specific streams_{sp} layers in Q?

will load example project to Q and share for collaboration in case that is helpful

Before editing qgs file

After editing qgs file to swap DAM for HYDRO

After editing symbology to swap orange for red when HYDRO involved

Yes - focus has been on salmon/steelhead, mapping of resident spp behind dams need to be resolved.

open issue in bcfishpass is here https://github.com/smnorris/bcfishpass/issues/304

Yes, agree everything upstream of dams for resident species should be coloured as per above modelled/potential barriers. I also think that we don't really need HYDRO in the mapping code, a dam is a dam in terms of symbolization for resident species. The HYDRO code is more for mapping of historic anadromous habitat and I'm not sure it is really needed at this point either.

Hmmm. Maybe we’re not quite there yet with that symbolization with that adjustment. Really we want to be able to fix culverts on tribs to main rivers (Kootenay River in that example) and be able to visualize that its restored connectivity within the system… As it is there, if I have my head wrapped around it correctly,
If we don’t fix the dams we won’t be able to visualize any connectivity restoration work getting done upstream… maybe the HYDRO label could be useful still but perhaps it could be ignored for our use case of exploring road/stream crossing restoration opportunities…

For barriers that get fixed we are already symbolizing as green.
But for resident spp, some other colour indicating upstream of dam but not upstream of a modelled crossing would be useful.

The concept of a HYDRO label for historic anadromous access is actual pretty awesome. There is TONS going on these days in the KOTL and LARL etc reagarding reintroductions (happening already with huge fry releases planned very soon) and modelling for salmon suitability. For those watershed groups dams in states should prob be considered too. All that is likely too much to deal with right now but perhaps the HYDRO label need not be changed - just pulled into the symbology. Just a thought…

I have added a column to streams table that indicates if the next barrier downstream is a dam. Those streams can be given a different colour, and streams upstream of modelled crossings / PSCIS barriers retain current colour. It isn't perfect but seems better than current style and can be adjusted as we figure this out.

I'll add a column indicating if a hydro dam is the next barrier downstream as well. But I'll hold off on any changes to anadromous symbology for now.


Create a Terminal GUI

using https://github.com/ronisbr/TextUserInterfaces.jl. Especially look at the examples.

this could be an alternative https://github.com/Gnimuc/CImGui.jl looks also very promising


Fixed issue where shortcut items would not be cached properly

This pr fixes an issue where Shortcut items would not be cached properly.
The issue was caused by the Json converter serializing and de-serializing the shortcut as a ListedItem, not as a ShortcutItem. When the cache was then read, Files would treat the shortcut like a normal file, instead of as a shortcut.
This would cause the details page instead of the shortcut page to be shown in the properties window when a shortcut was selected, and also caused a minor issue with #3349.

Attempting to navigate to the details page would then cause a crash, since StorageFile doesn't work with shortcuts.
This PR fixes that issue by removing the ShortcutItem child class, and moving all of it's properties into the ListedItem parent class. ListedItem.IsShortcutItem is now set to true when a shortcut is initialized. This way, all of the shortcut-specific properties can be serialized and de-serialized, therefore allowing the shortcut's information to be cached.
I have tested these changes with creating, deleting, opening, and changing the settings of shortcuts, with and without file caching enabled, and have not noticed any issues thus far.

I'm pretty sure you can set the json serializer to keep the type when serializing and thus deserialize to the correct type with the TypeNameHandling option

@gave92 That seems to work, and is much simpler. Thanks. I'll make a new branch and PR. #3434


NA_Addr_cmp returns wrong result with ofi+tcp

NA_Addr_cmp returns NA_TRUE for addresses that are actually different, when using ofi+tcp (I haven't tried with other OFI plugins). It correctly returns NA_FALSE with na+sm.
I'm using Mercury 2.0.0rc1 with libfabric 1.10.1.

I'm closing the issue; I think it was caused by my test framework, which was forking child processes between tests. The creation of addresses was being done by the parent before the fork and the child process was inheriting addresses including a self address that wasn't actually valid.


Added Youtube tutorial on Docker

Fixes Issue

Changes proposed

Screenshots

Note to reviewers

@TRohit20 sure I will keep that in mind : )


Improve compiling containers on non-Linux systems

This issue documents a usability issue but does not currently offer a solution.
As it stands, executing copy2DockerDaemon will build the container locally and then push it to whatever Docker registry is configured on the local system. In non-Linux systems, this presents a problem because the Docker daemon is running inside a Linux VM. The result is that the container is typically built for macOS/Windows and then uploaded to a Docker daemon running under Linux (this is true for any runtime, including podman, containerd, etc.).
I'm not sure if this problem can be solved entirely within nix2container or if some documentation can be generated with a workaround for users in this context. The most obvious solution is to just run everything in a Linux VM and forward the Docker socket to the local machine (this is what I'm currently doing using lima).
Another potential solution that I think is worth exploring is using remote builders to build the OCI image. The primary problem I see here is that the image isn't actually stored in the nix store (which I understand is a good thing), so figuring out how to actually get the image built remotely is the primary challenge.
There may be other solutions that I'm not aware of. I figured this issue is a good starting place to discuss potential solutions and their pros/cons.

Another potential solution that I think is worth exploring is using remote builders to build the OCI image.

I think this is what @nktpro is doing. Currently, there are however still some issues because of the "nix case hack" required on aufs (see #48 and https://github.com/nlewo/nix2container/issues/37), but i started to work on these issues.

I'd be curious to learn how this is being implemented. I don't think a typical nix remote builder can work since the image isn't put in the store. There may be some workarounds I'm not aware of.

@jmgilman Currently the workaround is to output the image in skopeo dir format as another derivation, for example:
image = nix2container.buildImage {
 ...
};
image-as-dir = runCommand "image-as-dir" { } "${image.copyTo}/bin/copy-to dir:$out";

We can then build image-as-dir remotely on any aarch64-linux or x86_64-linux builders from macOS/Windows, then simply copy the result to any registry, e.g:
skopeo copy --insecure-policy dir:./result ...

The obvious drawback of this approach is that it defeats the strength of nix2container altogether, as it shares all the inefficiencies of dockerTools in nixpkgs.

@jmgilman The remote builder builds the image.copyTo script (with all of its dependencies, ie the image itself) and your local deamon asks the remote store for the script image.copyTo which depends on all store paths required to push the image. Your local deamon just has to copy all store paths used by the image and builds the Skopeo binary which is then used to push the image: the image has been built by the remote builder and Skopeo is built and executed locally.
However, this is not fully working yet (see above mentioned issues).


Add serverless version to repo

Serverless 1.4 adds support for C# https://github.com/serverless/serverless/pull/2863
Let's do the the same with this template 😃 I'll make a start, feel free to jump in

@slang25 I'll look at converting this project to use serverless (I'll keep it in a sub folder for now so there are options)

Cool, let me put up the WIP PR for your reference too, will just be a few minutes.

[ ] Setup Hello Word in CSharp template
[ ] Convert to use the F# project.json and files
[ ] Add a Readme on setup instructions pointing here

https://github.com/serverless/serverless/pull/3045

Implemented in PR: https://github.com/lukemerrett/FSharp-Template-for-Aws-Lambda/pull/3


TypeError

Excited to explore the library as always!
class MiniData(NamedTuple):
    X: ArrayImpl
    Y: ArrayImpl

def loss_fn_per_obs(y, p):
    return jnp.where(y==1.0, -jnp.log(p ), -jnp.log(1-p ))

def fn(params, args):
    P =  jax.nn.sigmoid(args.X @ params)
    losses = jax.vmap(loss_fn_per_obs, in_axes=(0,0))(args.Y, P)
    return jnp.mean(losses)

init_params = jax.random.normal(jax.random.PRNGKey(0), shape=(19,1))
data = MiniData(X=jax.random.normal(jax.random.PRNGKey(1), shape=(100, 19)),
                Y= jax.random.normal(jax.random.PRNGKey(2), shape=(100, 1)))
solver = optimistix.NonlinearCG(rtol=0.01, atol=0.01)
optimistix.minimise(fn=fn, solver=solver, y0 = init_params, args=data, has_aux=False)

I am running into the following type error:
TypeError: linearize() got an unexpected keyword argument 'has_aux'

Which version of JAX are you using? This was added in one of the more recent JAX releases. (It's possible we need to bump the minimum version required by Optimistix.)

@patrick-kidger Everything works once I updated the necessary libraries. My bad!


21-httprequest.js: toLowercase --> toLowerCase

this line uses toLowercase, should be toLowerCase but the code is probably no longer used?

That function does appear to be now unused.
Please feel free to submit a pr to remove it

Done! PR #4522


Error when creating a database

OrientdDB 2.1.6
This is the error I get on console  when I try to create a document database from studio as a root user
2015-12-02 13:25:20:514 WARNI -><IP_ADDRESS>: Command not found: GET.sqlProfiler/SupplierPartCatalogueDB [ONetworkProtocolHttpDb]
2015-12-02 13:25:20:991 SEVER Internal server error:
com.orientechnologies.orient.core.exception.OQueryParsingException: Error on parsing query at position #8: Error on parsing command at position #0: Error on parsing query
Query:  _studio WHERE user.name = 'admin' AND type = 'GraphConfig'
-------------^
--> com.orientechnologies.orient.core.exception.OCommandExecutionException: Class '_STUDIO' was not found in current database [ONetworkProtocolHttpDb]
Nevertheless the database has been created, OK I believe....

hi @healiseu
which version of OrientDB?

First line in the OP says "OrientdDB 2.1.6"
Scott

I believe it has been fixed in OrientDB 2.1.9

Fixed long time ago.


user select form not work

Hi,
I have just installed your bundle but on version 1.10 of OroCRM.
It seems that their is problem with the select oro user select widget on Timesheet with the xhr request.
Maybe a compatibility version problem.
 Notice: Undefined offset: 4 in /home/sinabs/sites/dev.orocrm.sinabs.fr/vendor/oro/platform/src/Oro/Bundle/UserBundle/Autocomplete/UserAclHandler.php on line 92
Have you try it on latest version of Oro ?
Could you update your bundle ?
Your work seems great i really would like to use it.

I found the problem I think.
Just replace autocomplete alias by user in configuration form
private function buildUserSelector()     {         return         $this->get('form.factory')             ->createNamed(                 'timesheet_user',                 'oro_user_select',                 null,                 [                     'autocomplete_alias' => 'users',                     'configs' => [                         'entity_id'               => $this->getCurrentUser()->getId(),                         'entity_name'             => 'OroUserBundle:User',                         'excludeCurrent'          => false,                         'extra_config'            => 'acl_user_autocomplete',                         'permission'              => 'VIEW',                         'placeholder'             => 'Select a user',                         'result_template_twig'    => 'OroUserBundle:User:Autocomplete/result.html.twig',                         'selection_template_twig' => 'OroUserBundle:User:Autocomplete/selection.html.twig'                     ],                     'grid_name' => 'users-select-grid-exclude-owner',                     'random_id' => false,                     'required'  => true                 ]             )             ->createView();     }


Direct Buffer Used Despite Parameters Indicating Not To

Expected behavior
If -Dio.netty.allocator.numDirectArenas=0 and -Dio.netty.noPreferDirect=true, that Direct Buffers are not used when a Heap Buffer is possible.
Actual behavior
Instead, Direct Buffers are always used as shown in this Stacktrace:
16:37:49.059 [nioEventLoopGroup-3-4] WARN  DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 480 byte(s) of direct memory (used:<PHONE_NUMBER>, max:<PHONE_NUMBER>)
	at io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:535)
	at io.netty.util.internal.PlatformDependent.allocateDirectNoCleaner(PlatformDependent.java:489)
	at io.netty.buffer.UnpooledUnsafeNoCleanerDirectByteBuf.allocateDirect(UnpooledUnsafeNoCleanerDirectByteBuf.java:30)
	at io.netty.buffer.UnpooledUnsafeDirectByteBuf.<init>(UnpooledUnsafeDirectByteBuf.java:67)
	at io.netty.buffer.UnpooledUnsafeNoCleanerDirectByteBuf.<init>(UnpooledUnsafeNoCleanerDirectByteBuf.java:25)
	at io.netty.buffer.UnsafeByteBufUtil.newUnsafeDirectByteBuf(UnsafeByteBufUtil.java:410)
	at io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:336)
	at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:183)
	at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:174)
	at io.netty.buffer.AbstractByteBufAllocator.ioBuffer(AbstractByteBufAllocator.java:135)
	at io.netty.channel.AdaptiveRecvByteBufAllocator$HandleImpl.allocate(AdaptiveRecvByteBufAllocator.java:104)
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:117)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:646)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:581)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:498)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:460)
	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:131)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Thread.java:748)

Why? See io.netty.buffer.AbstractByteBufAllocator.ioBuffer(AbstractByteBufAllocator.java:135) aka https://github.com/netty/netty/blob/2dc686ded17d8123118921ac6d36aea30cdce267/buffer/src/main/java/io/netty/buffer/AbstractByteBufAllocator.java#L128-L150
 @Override
    public ByteBuf ioBuffer() {
        if (PlatformDependent.hasUnsafe() || isDirectBufferPooled()) {
            return directBuffer(DEFAULT_INITIAL_CAPACITY);
        }
        return heapBuffer(DEFAULT_INITIAL_CAPACITY);
    }

From the above, if hasUnsafe evaluates to true, directBuffer() is invoked vs. heapBuffer().
The only workaround is to provide -Dio.netty.noUnsafe=true in addition to the aforementioned parameters.
Steps to reproduce
N/A
Minimal yet complete reproducer code (or URL to code)
N/A
Netty version
Latest
JVM version (e.g. java -version)
openjdk version "1.8.0_202"
OS version (e.g. uname -a)
Ubuntu 16.04

@trustin @ejona86 @carl-mastrangelo WDYT ? I am a bit on the fence for this one... I guess it would be fine to adjust to work more like buffer as NIO implementation will use a local ThreadLocal cache anyway.

From the code:
    /**
     * Create new instance
     *
     * @param preferDirect {@code true} if {@link #buffer(int)} should try to allocate a direct buffer rather than
     *                     a heap buffer
     */
    protected AbstractByteBufAllocator(boolean preferDirect) {  }

I think the "prefer" is when the caller doesn't care about the type, specifically in the case of buffer().  ioBuffer() does care that the buffer is direct, because a direct buffer is required to do Io. (the JDK will do this automatically for you, but it does eventually have to be direct).

The only workaround is to provide -Dio.netty.noUnsafe=true in addition to the aforementioned parameters.

Can you explain your usage pattern more?   I.e why can you not pass in PreferHeapByteBufAllocator into the Channel config?

I don't think those configuration options imply "no direct buffers." They mean "no pooling for direct buffers" and "given a choice between direct and heap, whether direct should be used."
I think "don't use any direct buffers" is more of a feature request. Right now any code that calls alloc.directBuffer() should get a direct buffer. And it seems fair that ioBuffer also is a direct buffer, given how memory works in Java. So I don't know if even that makes sense.
@amcrn, can you explain why direct memory is off-limits for you?

I think I agree with @ejona86

Thanks for the quick replies @ejona86 @carl-mastrangelo @normanmaurer , I really appreciate it.

Can you explain your usage pattern more? I.e. why can you not pass in PreferHeapByteBufAllocator into the Channel config?

(Note: I'm going to be very explicit with flags and such so that other people with the same issue can find it in a Google search)
My attempt to avoid direct buffers arose out of trying to triage OutOfDirectMemoryErrors being thrown repeatedly in a high throughput application.  Turning on -Dio.netty.leakDetection.level=paranoid returned nothing, and limiting -XX:MaxDirectMemorySize didn't prove fruitful either. Inspecting direct memory is fairly difficult in our deployment environment, so I was looking to have all allocations heap-based when possible, that way an OutOfMemoryError would trigger a Heap Dump via -XX:+HeapDumpOnOutOfMemoryError, and then I could begin to investigate what was "leaking" or dominating.
The following three parameters were enough to cause a Heap Dump vs. OutOfDirectMemoryError: -Dio.netty.allocator.numDirectArenas=0, -Dio.netty.noPreferDirect=true, and  -Dio.netty.noUnsafe=true. After analyzing the Heap Dump, I was able to determine that reducing -Dio.netty.allocator.maxOrder to 3 for our Heap size (~2GB) was the appropriate solution, as that in turn reduced the chunkSize (and other artifacts) to a more reasonable limit.
Long story short: Having the option to use heap memory vs. direct memory proved very useful in identifying a "leak" (in this case, it wasn't really a leak, just too aggressive of an allocation strategy) in a deployment environment that doesn't permit direct access to the Box/VM/container.

I think "don't use any direct buffers" is more of a feature request

Fair enough. Maybe a small enhancement could be made to the documentation or Javadoc indicating that even if -Dio.netty.allocator.numDirectArenas=0 and -Dio.netty.noPreferDirect=true, direct memory will still be used (and why).

Can you explain your usage pattern more? I.e. why can you not pass in PreferHeapByteBufAllocator into the Channel config?

Good question. Netty in this case is being used by a third party library that we have no control over. Is there a -Dio.netty flag that can be set to indicate the Class desired?

I'm having a similar problem. A lot of direct memory seems to be used, more than it is available in the machine and then swap memory starts to be used. I currently think that Netty is allocating this memory in a situation similar to what @amcrn described. I tried to find some documentation and where -Dio.netty.noPreferDirect is used in Netty code in order to understand it is purpose, but I had no success. Could please someone help me understand that? I would suggest creating some documentation explaining the purpose of not only this parameter, but all of them as I couldn't find it anywhere.


Remove Emperor's Birthday of 2019.

The emperor's birthday in 2019 is not a holiday.
http://www8.cao.go.jp/chosei/shukujitsu/gaiyou.html#link2

@babatakao Thank you fixing.


'fail to parse token for foo/bar. signature is invalid' with gitlab

Using gitlab.com, and a freshly installed drone, after authorizing drone to access gitlab, and the 'Drone CI' service on gitlab being empty, when i trigged the 'Activate Now' button on Drone, it fullfill the 'Drone CI' service form on gitlab, but when i hit 'Test Settings' on gitlab, It leads to the error 'fail to parse token for foo/bar. signature is invalid' (on the Drone side).
Unfortunatly, i have no access to any kind of logs on gitlab.com, as it is an hosted service.
Any Ideas?

@kri5 when drone add a hook to GitHub / GitLab / Bitbucket / etc it adds an access_token query parameter, which is used to authorize hook requests. This token is verified when the hook is received by Drone and based on the above message seems to be failing:
https://github.com/drone/drone/blob/master/controller/hook.go#L61
The token verification is used by all providers, including GitHub, Bitbucket and Gogs and there are no known issues with those systems. I'm not sure what changed with GitLab, but unfortunately Drone no longer has a GitLab maintainer. If you are interested in helping troubleshoot and get to the bottom of why it is failing it would be greatly appreciated.

I think that new version 8.2 RC was deployed on gitlab.com and there was one change in drone service in 8.2:
https://gitlab.com/gitlab-org/gitlab-ce/commit/5aa142212fc4fb7765aad801c1a25696fb752fba
Maybe this is the reason why it is not working anymore.
I didn't try it yet. I have my own instance of Gitlab currently on 8.1 version and It's working correctly with Drone 0.4.
I'm planning to look at it in the following days and help with Gitlab integration.

@kri5 Are you getting error 500 on gitlab.com when you hit 'Test settings' ?

@martinsefcik On a newly configured project, i get 500 when i hit the test settings button on gitlab.com

Fix is available here: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/1856
Posted as an 8.2 regression. Will hopefully be able to get it in before the release.

I think this can be closed.
Gitlab 8.2 was released and it's working.

@bradrydzewski @martinsefcik Works for me. Gitlab.com runs on 8.2 now, and i have no more issues.


Display Temp HP and Max+ HP modifiers in an Actor's HP Bar on a Group sheet

Updating the HP bar on the Group sheet to visually match the Token HP Bar would be a welcome addition to grok this info at a glance

I didn't even think about tempmax, but I too would like to elevate a desire to want this feature added.


Improve notification popup

I don't know how hard (or is it possible at all) is to alter the popup i get in Chrome. But i would like to see:

No Pade - Unified Communications at Work as a header as it takes too much space (maybe just leave Pade);
Replace Pade icon with user's avatar if available (can still show this icon if no avatar is set, or maybe a generic avatar with first letter of a user);
Show user's name before the message (maybe in bold). I really like to see who is saying what without opening a chat window just by looking at the popups.

I haven't yet looked into that, maybe i can even do something of these myself. Probably not :)

This what a notification looks like with Windows 10. We have limited control of what we can change or format. All Window applications use the same notification format.

We can't change the header.  It is the extension name and short description and is taken automatically from the browser extension manifest file.
Icon is replaced with avatar for one2one chat. Groupchats don't have any avatars
We can't change the formatting of the username.

Improve notifications for group chat mentions.
Show the nickname of the participant that mentions user's name and show avatar of that user if available

Done. Now available in version 1.2.3

extending on this, could you add notification numbering/dots on the group chats so that it's easy to see which group has an update?
This would be useful for contacts that are grouped as currently, I need to expand each group to find who has messaged me directly. if it was at a group level I can easily expand on the group.
Regards
Mark


Wrong Data for IFSC code BKID0008463

Data from API:
{
"IMPS": true,
"CITY": "SIRSI",
"ADDRESS": "BANK OF INDIA,SIRSI BRANCH, 3, KAMAT PLAZA, T.S.T. ROAD, SIRSI-581402",
"BRANCH": "SIRSI BRANCH",
"UPI": true,
"STATE": "KARNATAKA",
"DISTRICT": "UTTAR KANNAD",
"MICR": "",
"RTGS": true,
"NEFT": true,
"CONTACT": "",
"CENTRE": "SIRSI",
"BANK": "Bank of India",
"BANKCODE": "BKID",
"IFSC": "BKID0008463"
}
Expected Data:
Address: BANK OF INDIA CHIKKABALLAPUR 2ND CROSS OPO ROAD 28TH WARD CHIKKABALLAPUR CHIKKABALLAPUR DIST BANGALORE KARNATAKA STATE 562101
State: KARNATAKA
District: BANGALORE URBAN
Branch: CHIKBALLAPUR

Closing the issue as publically the data is different but the RBI website is having same record as the API.

Sorry closed by mistake.
The data is not matching what is on RBI website
Reference: https://www.rbi.org.in/Scripts/IFSCDetails.aspx?pkid=179151

Any updates?

The details come from the RBI website itself: https://rbidocs.rbi.org.in/rdocs/RTGS/DOCs/RTGEB0815.xlsx (Linked at https://www.rbi.org.in/scripts/FAQView.aspx?Id=65)
Can't do anything here, perhaps reach out to RBI or the banks to get this corrected.


Update Chihuahua to v7.0.1

Chihuahua will upgraded to v7.0.1 at https://www.mintscan.io/chihuahua/block/13250000
Jun 17th 2024, 14:11:31+00:00.
Proposal: https://www.mintscan.io/chihuahua/proposals/77

@tombeynon can we have the temp docker image for this?
Thanks

@CharlesJUDITH definitely, thanks for opening this. I'll get the pre release image built in the next hour

Pre-release image: ghcr.io/akash-network/cosmos-omnibus:v0.4.19-rc4-chihuahua-v7.0.1


Quick fix BoundsChecker entry point

Fixed the BoundsChecker to match the other verification entry points

Motivation

Consistency

Test Plan

cargo test

@bors-libra r=dariorussi

:pushpin: Commit 56c821b has been approved by dariorussi

:hourglass: Testing commit 56c821b3c3b278a12ddce1c03c1bda60535bea91 with merge a59dea52646cf4d033035358dbae780359608c74...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: dariorussi
Pushing a59dea52646cf4d033035358dbae780359608c74 to master...


Quickstart example fails at python hello_config.py print_config

I was just trying out Sacred, and one of the configuration examples mentioned in "Quickstart" fails when calling python hello_config.py print_config with the following error message:
INFO - hello_config - Running command 'print_config'
INFO - hello_config - Started
ERROR - hello_config - Failed after 0:00:00!
Exception originated from within Sacred.
Traceback (most recent calls):
  File "/home/paethon/.local/lib/python3.8/site-packages/sacred/commands.py", line 61, in _non_unicode_repr
    repr_string, isreadable, isrecursive = pprint._safe_repr(
TypeError: _safe_repr() missing 1 required positional argument: 'sort_dicts'

same here

Interesting. Yes this seems to be a 3.8 issue, thanks for reporting. I'll mark it as a bug.

@Qwlouse would you be willing to merge the PR?
I have tested this on machines using Python 3.8 and Python 3.7.
I'm unsure but hope this patch meets the contributing guidelines.
tox only gave unrelated warnings.

did you open the pull request?

@CarloLucibello No, GitHub did that automatically because I forked the repo, created a new branch and used Fix #712 as a commit message.

@flxai I do not see your PR, you might need to submit it manually. Your fix looks good to me, so I'd be happy to merge.

@Qwlhouse @CarloLucibello Sorry, I mistook the notice referenced above for an automatically opened pull request. #719 contains the PR now. I'm not sure if that is the right way or whether I could have created the PR within this issue.

Hi all,
In which sacred version is this fixed? I'm using 0.8.1 and Python 3.8 and I'm getting this error.


stdenv: remove assumption of exactly two cross stages

If you want to see an example of the problem this PR solves, cherry pick just the "stdenv: cross: insert no-op stages" commit and nix-instantiate . -A pkgsCross.<anything>.
Motivation
This removes one of the last obstacles to unifying our native and cross bootstraps, which will allow to eliminate all the libcCrossChooser and simply reuse the relevant stages from pkgs/stdenv/linux/default.nix instead.
Description of changes
The native stdenv bootstrap (e.g. pkgs/stdenv/linux/default.nix)    is very elegantly structured as a sequence of arbitrarily-many    stages.  This makes it easy to refactor and modularize and reuse,    because if a stage gets too complicated we can just split it up into    two separate sequential stages.  We can also insert optional stages.
Unfortunately we can't do the same thing with cross-compiled    stdenvs, because adjacentPackages includes the hardwired    assumption that there are exactly two stages after the end of the    native bootstrap stage sequence:

The (build==host)!=target stage
The build!=(host==target) stage

This PR eliminates that assumption.
Instead of resolving things    like pkgsBuildHost to prevStage, we instead search backwards    for the most recent stage which creates packages on our    buildPlatform and for our hostPlatform.
This PR should not affect eval.
Note that pkgsTargetTarget, which becomes targetPackages still    has hardwired assumptions.  I think setting pkgsTargetTarget to    nextStage is just flat-out wrong for every stage except the "main"    stage (the build!=(host==target) stage), but I fear that there may    be code that relies on the particular way that it is wrong.  It    looks like pkgsTargetTarget and targetPackages exist exclusively    in order to provide access to the postStage hack; I intend to    submit a separate PR that throws if it is used in any other way,    to see what breaks.

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

nix-diff $(nix eval --raw ".?rev=$(git merge-base master HEAD)#pkgsCross.aarch64-multiplatform.sway.drvPath") $(nix eval --raw ".#pkgsCross.aarch64-multiplatform.sway.drvPath")
nix-diff $(nix eval --raw ".?rev=$(git merge-base master HEAD)#pkgsCross.aarch64-multiplatform.python3Packages.cryptography.drvPath") $(nix eval --raw ".#pkgsCross.aarch64-multiplatform.python3Packages.cryptography.drvPath")
no eval changes

Checking if these stats are correct

I don't think ofborg does a lot of cross eval, so 1% extra work seems rather significant.
Maybe the new items in the stage list are significant (multiple // on a whole pkgs attrset - or maybe I'm mistaken), or maybe some binding is accidentally not shared anymore.
1% extra work is based on the total allocation stat, which is a decent proxy for the amount of work done.
Could you try locally with NIX_SHOW_STATS=1 nix-build -A?

removed 2 of the no-op stages, left 1 in.

It was the extra stages

Squashed, rebased.
There is now only one no-op stage, but with an expanded comment explaining why it thwarts unjustified assumptions, and a mention of the other two (removed) no-op stages in case re-introducing them helps with troubleshooting.

Doesn't this break "identity cross compilation"? I.e. introducing a new stage which is not differentiated in the hostPlatform.
This is funny to me because I sort of wanted to go in the opposite direction: the native bootstraps do not need all these stages, instead there should be just one "with bootstrapping tools" stage and then one "without bootstrapping tools" stage.
But I am willing to do this because I don't yet have time to do rework things as I have wanted to for years, and @amjoseph-nixpkgs is motivated and does have time for putting in the work.

which will allow to eliminate all the libcCrossChooser and simply reuse pkgs/stdenv/linux/default.nix instead.

This is not describing this PR, but this actually sounds quite bad to me. The linux bootstrap is totally overfit to GCC, and the current cross bootstrapping works with LLVM or GCC.

I've revised this to:

eliminate all the libcCrossChooser and simply reuse the relevant stages from pkgs/stdenv/linux/default.nix instead.

You have to admit that there is a huge amount of duplication between the cross bootstrap and stdenv/linux -- except that the cross stuff that got smashed together in all-packages.nix is much uglier (no stages, spaghetti-builds, etc).
Both of them go through the same dance:

Compile the compiler
Use the compiler to compile the libc
Compile the compiler again

The goal is to deduplicate this dance with no loss of functionality.

The linux bootstrap is totally overfit to GCC, and the current cross bootstrapping works with LLVM or GCC.

Don't worry; I have absolutely no intention of reducing our cross bootstrap's capability.  If I can't make it work for every case in tests.cross.sanity, I will not undraftify it.  Obviously that includes LLVM!
It's qute likely that the end result will have certain stages skipped as totally unnecessary if isLLVM.  Then you'll have a nice concise example to point at in order to show people how much better LLVM's build process is than GCC's!

Doesn't this break "identity cross compilation"? I.e. forcing a round of cross bootstrapping even though buildPlatform == hostPlatform.

I don't quite understand what you mean here.
Could you give an example (like pkgsCross.something.something.something or nixpkgsFun { ... }) of where you see this happening?


Error following deployment guide

I have followed the deployment guide and arrived to the end installing the app in Teams. When executing the app I obtain the following:

I have consulted the application insights in Azure and obtained the following:

The concrete exception is:
AADSTS65001: The user or administrator has not consented to use the application with ID 'myAADappIdGUID' named 'Contact Group Lookup'. Send an interactive authorization request for this user and resource.

when I am uploading the app in Team then getting the error of Manifest parsing has failed.
For more information, please visit aka.ms/teamsdocs


chore(ci): add renovate, release-please

[x] @3arthqu4ke you will need to set "Allow GitHub Actions to create and approve pull requests" under repository Settings > Actions > General.

Ok, done, do I need to setup something? Add a RENOVATE_TOKEN secret?

Ok, done, do I need to setup something? Add a RENOVATE_TOKEN secret?

No no, I've listed a few things in Discord, I'll let you know the last items on the list once I've finished up.

[ ] Add Renovate to this repo https://github.com/apps/renovate
[ ] Enable "Automatically delete head branches"
[ ] Disable "Allow merge commits"
[ ] Set squash commits to "Pull request title"
[ ] Squash merge this PR

@3arthqu4ke


Return 404 when instance does not exist

Description
Changes proposed in this pull request:

Return 404 if an instance does not exist
Return 404 if an operation does not exist
Add last operation tests
Fix return 400 when operation exists, but an instance is invalid

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Hanna Gosciniak seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add Agent App Widget example

It should:

show contents of customer_profile
print a button in General tab of customer details

I think we've got it


Fix ConfigureAwait(false) not being used to resume without current co…

…ntext on awaits

Creating a sample MVC app that syncronously blocks on the Async method will produce a deadlock with the current implementation.
public ActionResult Load()
{
    UpsertAsync().GetAwaiter().GetResult();

    return Content("Loaded!");
}

private static async Task<IDocumentResult<string>>  UpsertAsync()
{
    return await Bucket.Value.UpsertAsync(new Document<string> { Id = "1", Content = "Content" }).ConfigureAwait(false);
}

@millerhederi -
Thanks for the submission! If you haven't already done so, would you mind creating a Gerrit (our code review system: review.couchbase.com) account and signing the CLA? Here are the steps: http://www.couchbase.com/wiki/display/couchbase/Contributing+Changes
Once you do that, I'll push this PR to Gerrit for review and it will be included in 2.2.0 next month assuming it is +2!
Thanks,
Jeff

@jeffrymorris -
Hey Jeff, I went ahead and created an account on Gerrit and signed the CLA, hopefully should be good to go.

@jeffrymorris - Is there any update on this? I have not received any notification that the PR has been pushed into Gerrit.

@millerhederi  -
I pushed it the PR to gerrit; there is a backlog of things to be reviewed and merged in gerrit, so it will take a bit of time before it's reviewed. The planned release date for 2.2.0 (the next release) is early October 2015.
-Jeff


First 5 minutes experience UX

What's the motivation behind the feature? what problem does the feature intend to solve ?
Currently the user's first 5 minutes experience doesn't create enough incentive to carry over to the rest of the course.
The data also validates this:
Only 40% of the people reach chapter 1.
Out of those 40% only 25% reach chapter 5.
~ which translates to that out of 100 people, only 10 people reach chapter 5 which is sad since most of the meat of the learning is after chapter 5.
Describe the solution you'd like.
I don't have tactical solutions in my mind at the moment. Just principles:

that first time user loses steam very quickly and we need to think of what dopamine hit can we give to keep them hooked till they become more invested in the course.
studying is cognitively loaded and hence 1 becomes 10x critical problem to solve.

First 5 min onboarding was a bit repetitive, ie the home page, the mission briefing, and to lesser extent the animated storyline with "Save the Planet" grass gem presentation, and then again chapter 1 prologue — all these repeat the lines about gem and build/assemble bot. I suspect you will retain more uses by reducing this and getting them into action faster and can then add more narrative later. Possibly an a/b test would help in optimizing this intro flow.
The prologue uses some terms which are "fun" but could be confusing: 1. why "#build-ers" rather than just "builders" 2. why ask what user will "#buidl" 3. Later use of "#builder-s" These inconsistent use of hash tags, spelling, and the term buidl are not too inviting to someone new to the space as it leaves one wondering if there is already some special terminology they are missing.
Prologue also might be overstating the prerequisite: "You are generally familiar with software development, writing code, and running your code" in particular seems might scare some people off, better "an interest" rather than general familiarity. And "running your code" need not be highlighted as thats handled by the tooling for them. Instead of "have working knowledge..." maybe just "an interest in learning some python — a popular beginner friendly language used in many areas beyond crypto"
More minor but I also found these two lines and use of unclear symbols/icons to be a source of introductory confusion which is where its most important to avoid:
begin typing your code here. ⌨
click on "Show Answer" button to activate 🧞♂ mode!


How to get a transaction fees?

As we can see in the example with the package
final PartiallySignedTransaction psbt = await txBuilder.addRecipient(script, 700).feeRate(1.1).finish(wallet);
it was used as a predefined transaction fee.
Also, on the BDK website, there is an article https://bitcoindevkit.org/blog/2021/01/fee-estimation-for-light-clients-part-1/ about this issue.
So the question is - what is the recommended way to get fees for building a UX like in the attached image?

Hi @awaik enhanced fee estimation will be added to bdk-flutter in the next release. It will have flutter api for this functionality https://github.com/orgs/bitcoindevkit/projects/8?pane=issue&itemId=16803487
In the meantime electrs provides fee estimation:
link to fee estimate reference from electrs: https://github.com/blockstream/esplora/blob/master/API.md#get-fee-estimates
This is an example call to the blockstream public server for current fee rates:
https://blockstream.info/api/fee-estimates

@awaik this is available in v0.27.1

@awaik this is available in v0.27.1

Thank you! There are two issues:

I've tried to use it and always have a result 1.0 sat/vB. Code
final FeeRate rate = await blockchain!.estimateFee(13);

Even if I have correct sat/vB value, for example 15 sat/vB, I can't get a network fee in BTC. I'm trying to implement something like on the screenshot.


Using Custom Dataset with Different Input Lengths for Model

My input dimensions are [1500, 50, 6] and my label dimensions are [1500, 1]. Can I use this model? If so, could you please explain how to configure it correctly?

It looks like a classification task as you mentioned the "label"

If it means that the task only cares about the predicted value of one of the variables (with the other inputs as covariates), you can try to calculate the prediction error of only the target variable and backpropagate it when the loss function is optimized.


Flag HIPAA-compliant services

Flag services that are HIPAA-compliant - one idea would be to add a column in the "AWS Product Maturity and Releases" section.
https://aws.amazon.com/compliance/hipaa-eligible-services-reference/
https://aws.amazon.com/about-aws/whats-new/2017/06/cloudfront-s3-transfer-acceleration-waf-shield-are-now-hipaa-eligible/

👍 good idea

Could this possibly be expanded to include PCI-compliant services as well?

Closing. It's in the guide now; piecemeal updates are welcome!


SQL server datetime is not recongnized

Bug description / Feature request:
Hi Matt,
I'm storing the events in SQL Server and in particular startsAt and endsAt are stored in a datetime data type field.
The calendar does not recognize the datatime format and it throws the following error:
Event startsAt should be a javascript date object. Do new Date(event.startsAt) to fix it.
This means that I need to loop through all events in order to convert the datetime to a javascript date object.
My question is, why the datetime stored in SQL server is not recognized as a javascript date object?
Am I using the wrong SQL data type for a datetime data?
Thanks!
Versions
Angular:  1.5.0
Calendar library: 0.24.0
Browser name and version: Chrome 55.0.2883.87 (64-bit)
SQL Server: 12 (2014)

The reason for this is that your format is a string not a JavaScript Date object. There are many browser inconsistencies with how dates are constructed hence why I made it explicit that you as a user have to construct them yourself. A lot of people were relying on the calendar to construct invalid strings as dates and then wondering why they weren't displaying as the dates were invalid, hence why I went for this approach.

I appreciate if you can point me on how to get the datetime as a javascript date object rather than a string.
Actually I "google'd" this issue but all what I found are a sort of "hack" and say that datetime need to be converted in a query but I need a clean and standard approach that allows to retrieve datetime directly from the table as the field type is datetime not string!
Your support is highly appreciated!

You can pass a second argument to JSON.parse to control the deserialisation of the json to parse dates as Date objects instead of strings: https://blog.mariusschulz.com/2016/04/28/deserializing-json-strings-as-javascript-date-objects
However as angular controls the deserialisation of events from the API it might be tricky to implement this, I'd recommend just looping over the events in your controller, it's only 4 lines of code:
vm.events = vm.events.map(function(event) {
  event.startsAt = new Date(event.startsAt);
  return event;
});

Thanks a lot Matt!
I'm already using the mentioned loop to fix that issue with my datetime data but I'm trying to find a better solution.
Thanks for your helpful info.


Feature/traceback

This creates basic access for debugging

a history view of the automation (as actually run, i.e. loops unfolded, splits in parallel)
traceback view in case an automation task stops with errors

To do:

Update documentation

Feedback welcome!

Codecov Report

Merging #22 (2ea9e9c) into master (c1b8894) will increase coverage by 0.48%.
The diff coverage is 97.08%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage   94.39%   94.87%   +0.48%
==========================================
  Files          18       19       +1
  Lines        1230     1326      +96
==========================================
+ Hits         1161     1258      +97
+ Misses         69       68       -1

Impacted Files
Coverage Δ

src/automations/models.py
91.74% <50.00%> (-2.44%)
:arrow_down:

src/automations/flow.py
94.12% <100.00%> (+0.89%)
:arrow_up:

src/automations/tests/test_automations.py
98.96% <100.00%> (+0.08%)
:arrow_up:

src/automations/views.py
94.20% <100.00%> (+2.15%)
:arrow_up:

src/automations/templatetags/atm_tags.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Write concern revisited

This is #19 from @zecke but:
rebased and squashed (maybe I should had rebase only) + some tests and comments more + updated to use ordered dictionary + some minor refactorings
hope it's ok

Hiope is not a strategy!


README updates: Wording updates as per suggested in PR #7 review

Description
Made some updates in README related to wording as suggested in #7.
Refs #7

@rufuspollock whenever you get time please review this and merge if it looks good. Just made some small changes in README as per your comments in #7 PR.


How to I access the API on Postman along with Auth Creds

So, here is something I would like to understand.
I made the whole setup. Works like a charm after using it as is. Now the thing is I need to use the API service and provide it to my other app development team. They are using Node to build the app. I was keen to expose the API to them along with a specific username and password but unfortunately not of the guides/references point me in the right direction.
Is it possible for you to share the API endpoint URL which contains username and password that I could use as a reference and build on it?
Last resort is to use python inside node.js and call this library. No doubt it will work but it just makes things complicated. I want to use this library on a parallel web application that connects to the same endpoint whereas the mobile app that has a backend on node needs to access the same but I do not know the endpoint for that.

webui uses http basic authentication. You won't have problem using it from node directly. BTW If you are transmitting through internet without encryption it's not safe.

webui uses http basic authentication. You won't have problem using it from node directly. BTW If you are transmitting through internet without encryption it's not safe.

For some reason didn't get an alert. Anyhow, any way in which we can secure the API access though? The automatic1111 interface is already up and running on a cloud server and we're building an application that may require APIs to generate results through it.
Any viable suggestions?


Cannot ssh into container

Followed your readme, but when I try to connect via ssh I get a timeout error after a minute of waiting.
I got the insecure key, got the IP address, but I cannot login via the ssh command. I'm using Mac OS.
Thanks,

+1

Are you using docker-machine? If so you need to ssh into that and then ssh into the container.
docker-machine ssh <machine name>

Then follow the instructions: https://github.com/mtmacdonald/docker-laravel#connecting-to-a-container-with-ssh


Error with DDP and automatic_optimization=False

🐛 Bug

When running with distributed_backend="ddp" and automatic_optimization=False, there is an error when returning a detached tensor. More details below. I'm using lightning version 1.0.4; I also saw the same thing in 1.0.3. First, here's the code:
# ddp_bug.py
import os
import torch
from torch.utils.data import Dataset
from pytorch_lightning import Trainer, LightningModule

class RandomDataset(Dataset):
    def __init__(self, size, length):
        self.len = length
        self.data = torch.randn(length, size)
    def __getitem__(self, index):
        return self.data[index]
    def __len__(self):
        return self.len

class BoringModel(LightningModule):
    def __init__(self, detach=False):
        super().__init__()
        self.layer = torch.nn.Linear(32, 2)
        self.detach = detach

    def forward(self, x):
        return self.layer(x)

    def loss(self, batch, prediction):
        # An arbitrary loss to have a loss that updates the model weights during `Trainer.fit` calls
        return torch.nn.functional.mse_loss(prediction, torch.ones_like(prediction))

    def training_step(self, batch, batch_idx):
        opt = self.optimizers()
        output = self.layer(batch)
        loss1 = self.loss(batch, output)
        self.manual_backward(loss1, opt)
        opt.step()
        opt.zero_grad()

        if self.detach:
            loss1 = loss1.detach()

        return loss1

    def validation_step(self, batch, batch_idx):
        output = self.layer(batch)
        loss = self.loss(batch, output)
        return {"x": loss}

    def configure_optimizers(self):
        optimizer = torch.optim.SGD(self.layer.parameters(), lr=0.1)
        lr_scheduler = torch.optim.lr_scheduler.StepLR(optimizer, step_size=1)
        return [optimizer], [lr_scheduler]

def run_test(args):
    class TestModel(BoringModel): pass

    # fake data
    train_data = torch.utils.data.DataLoader(RandomDataset(32, 64))
    val_data = torch.utils.data.DataLoader(RandomDataset(32, 64))
    test_data = torch.utils.data.DataLoader(RandomDataset(32, 64))

    # model
    model = TestModel(args.detach)
    trainer = Trainer.from_argparse_args(
        args,
        default_root_dir=os.getcwd(),
        limit_train_batches=5,
        limit_val_batches=5,
        max_epochs=1,
        weights_summary=None,
        automatic_optimization=False,
    )
    trainer.fit(model, train_data, val_data)
    trainer.test(test_dataloaders=test_data)

if __name__ == '__main__':
    import argparse
    parser = argparse.ArgumentParser()
    parser.add_argument('--detach', action='store_true')
    parser = Trainer.add_argparse_args(parser)
    args = parser.parse_args()
    run_test(args)

To Reproduce
If you save the script above as ddp_bug.py and run the following command:
python ddp_bug.py --gpus=2 --distributed_backend=ddp --detach

the resulting error is thrown:
    self.trainer.accelerator_backend.backward(result, optimizer, opt_idx, *args, **kwargs)
  File "/home/catalys1/pylt/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 97, in backward
    model.backward(closure_loss, optimizer, opt_idx, *args, **kwargs)
  File "/home/catalys1/pylt/lib/python3.8/site-packages/pytorch_lightning/core/lightning.py", line 1103, in backward
    loss.backward(*args, **kwargs)
  File "/home/catalys1/pylt/lib/python3.8/site-packages/torch/tensor.py", line 185, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph)
  File "/home/catalys1/pylt/lib/python3.8/site-packages/torch/autograd/__init__.py", line 125, in backward
    Variable._execution_engine.run_backward(
RuntimeError: Expected to mark a variable ready only once. This error is caused by one of the following reasons:
1) Use of a module parameter outside the `forward` function. Please make sure model parameters are not shared across
multiple concurrent forward-backward passes
2) Reused parameters in multiple reentrant backward passes. For example, if you use multiple `checkpoint` functions to
wrap the same part of your model, it would result in the same set of parameters been used by different reentrant backward
passes multiple times, and hence marking a variable ready multiple times. DDP does not support such use cases yet.

The following commands don't throw an error
python ddp_bug.py --gpus=2 --distributed_backend=ddp

python ddp_bug.py --gpus=2 --distributed_backend=dp --detach

python ddp_bug.py --gpus=1 --detach

Expected behavior
My understanding is that setting automatic_optimization=False prevents any optimization steps from happening outside of the training_step function. It looks like maybe this isn't being honored? If it were, there should be no difference between returning a detached or not-detached tensor I would think.
Environment

PyTorch Version (e.g., 1.0): 1.6
OS (e.g., Linux): Linux
How you installed PyTorch (conda, pip, source): pip
Python version: 3.8
CUDA/cuDNN version: 10.2
GPU models and configuration: 1080 Ti

Additional context
I encountered this bug because I'm working on a model that requires multiple backwards passes per batch.

@awaelchli is this supported?


dev dependencies question

Hello guys,
I just clonned the repository via hilla cli and look at package.json.
My first question was:
"Why these packages with generator name are not under dev dependencies?"
https://github.com/vaadin/skeleton-starter-hilla-react/blob/v2/package.json#L8-L16
    "@hilla/generator-typescript-cli": "2.5.7",
    "@hilla/generator-typescript-core": "2.5.7",
    "@hilla/generator-typescript-plugin-backbone": "2.5.7",
    "@hilla/generator-typescript-plugin-barrel": "2.5.7",
    "@hilla/generator-typescript-plugin-client": "2.5.7",
    "@hilla/generator-typescript-plugin-model": "2.5.7",
    "@hilla/generator-typescript-plugin-push": "2.5.7",
    "@hilla/generator-typescript-plugin-subtypes": "2.5.7",
    "@hilla/generator-typescript-utils": "2.5.7",

Can you reply please?

No comment about the v2.5, but the good news is that with the new 24.4 they are now in the devDependencies:
https://github.com/vaadin/skeleton-starter-hilla-react/blob/v24.4/package.json#L39

wow from version 2 to 24? how does this happen over one year?

@landsman Btw, you can ask this types of questions on Vaadin Forum to get faster answers:
https://vaadin.com/forum/c/hilla/18

cool, do you have some expected release date of this version?

https://twitter.com/leifastrand/status/1783719215679373378


ICU macros

Is your feature request related to a problem? Please describe.
In our project, we are using the ICU format and we wanted to use the ICU macros but am not sure how do I use them with next-i18next.

You can find an example here: https://gitlab.com/kachkaev/website-frontend/-/blob/master/src/i18n.ts. Note that next-i18next has not been upgraded for some time in that project. I plan to do this once #869 is resolved.
Also note that the issues in the repo should follow a template.

@kachkaev Can anything be done within next-i18next to make this easier for users?

Hi @isaachinman! I don't think I have an answer at this point. I can look into this once there is a version for Next.js 10. Overall, adding ICU to next-i18next should not differ to much to just using i18next-icu: https://github.com/i18next/i18next-icu
The only tricky optimisation I can think of is dynamically importing 'i18next-icu/locale-data/LANG' so that the client bundle had to download just one lang based on the current route.

The only tricky optimisation I can think of is dynamically importing 'i18next-icu/locale-data/LANG' so that the client bundle had to include just one file based on the current route.

Can be done via a dynamic import, I imagine.
Should we leave this issue open?

Can be done via a dynamic import, I imagine

Yeah true. For that though, there's a need for async initiI18next(currentPageLocale) function of some sort, in which configuration process happens. This is where the lib can load all the necessary plugins and asynchronously import the ICU data for a specific lang. And maybe fetch namespace data too?

Should we leave this issue open?

Up to you really 🙂 I personally don't think that ICU integration is the job of next-i18next since ICU is just a yet another i18next plugin.

@hazem3500 Do you feel like your issue is solved, with the links and help that @kachkaev has shared, or do you want to keep this open?

@kachkaev I can't really open the link you've sent, probably an issue with GitLab, could you paste the code here?
I've managed to add ICU support like so
// i18n.ts
import NextI18Next, { InitConfig } from 'next-i18next'
import path from 'path'
import ICU from 'i18next-icu'

const icu = new ICU()

const I18nInstance = new NextI18Next({
    localePath: path.resolve('./public/static/locales'),
    use: [icu],
} as InitConfig)

export const {
    appWithTranslation,
    Link,
    Router,
    Trans,
    config,
    i18n,
    initPromise,
    useTranslation,
    withTranslation,
} = I18nInstance

export default I18nInstance

Is there anything that I am missing?


Fix Component Lifecycle documentation

What could be improved

The documentation part about the Component Lifecycle, especially about the onLoad method states:

The onLoad method can be overridden to run asynchronous initialization code for the component, like loading an image for example. This method is executed after onGameResize, but before onMount.

The phrasing can be improved to emphasize that onLoad is executed before onGameResize, and not after.
That being said, maybe it is in fact better to call onLoad after onGameResize, to allow sizing computations be run before onLoad (just like it is done in the FlameGame class).
Why should this be improved

By looking at the provided diagram in the documentation section and some quick testing, it turns out the onLoad method is executed before onGameResize and before onMount.
Also the docs should be as correct as possible to not irritate people new to flame.
Any risks?

Just some doc change...
More Information
The order of calls was changed in #2317 , where the documentation for onGameResize was changed, but not for onLoad.

That being said, maybe it is in fact better to call onLoad after onGameResize, to allow sizing computations be run before onLoad (just like it is done in the FlameGame class).

If I remember correctly it was a bit problematic to have onGameResize running before onLoad in normal components, and you can still get the size from the game with HasGameReference or just findGame().size in onLoad.

The phrasing can be improved to emphasize that onLoad is executed before onGameResize, and not after.

Sounds good, do you want to submit a PR that updates the phrasing? You'll get the great honor of being our 200th contributor if you do. :wink:


deis client breaks when enforceHTTPS is enabled

The deis binary does not play well with the backend API if the backend cluster enforces the use of HTTPS. Requests made directly to the API via CURL still work when HTTPS is forced. The issue appears to be localized to the deis client.
To reproduce:
$ deis apps
=== Apps
...
$ deisctl config router set enforceHTTPS=true
$ deis apps
$ deis login ...
username: ...
password: ...
!    WARNING: Client and server API versions do not match. Please consider upgrading.
!    Client version: 1.7
!    Server version:
Error: invalid character '<' looking for beginning of value
$ deisctl config router set enforceHTTPS=false
$ deis apps
=== Apps
...

deis --version: 11.1.1

perhaps this has something to do with #4400 and #4504?

ping @kenaniah. Were you able to further debug how or what causes this issue?

Unfortunately I don't have the time to look into this further at the moment. But more than happy to elaborate on the environment or repro steps if necessary.

That would be very helpful. That way we can test and verify this is an issue on master.

Might the issue be simply that the client doesn't follow redirects?

+1
deis apps
Error: Get https://example.com/v1/apps/?page_size=100: stopped after 10 redirects

@kenaniah @arkkanoid in either of your cases, is their a proxy of any sort between the deis client and the load balancer?  If so, this could very well be related to #4504, #4997, and the pending fix in #4998.

is there a proxy of any sort between the deis client and the load balancer?

If so, you might want to try again using a router built from the head of master-- #4998 was just merged.

closing as we have a strong belief this has been fixed in the LTS release as well as in v2. please re-open if this is not the case. thanks!


Charm trying fail to set report_host on scale up

Sunbean related bug

Full debug log.
https://bugs.launchpad.net/snap-openstack/+bug/2059774/+attachment/5783568/+files/sunbeam-inspection-report-20240528_134403.tar.gz

Thanks @nobuto-m


[ruff] Unformatted special comments (RUF037)

Summary
Resolves #10160.
Test Plan
cargo nextest run and cargo insta test.

@AlexWaygood do you have any recommendations on the rule's scope?

I agree that we're getting into very hairy territory if we start formatting other tools' pragma comments by default. However, it does seem useful to have a rule that does generalised formatting of pragma comments.
I like @MichaReiser's second suggestion in https://github.com/astral-sh/ruff/pull/14111#pullrequestreview-2427244566 -- I would suggest a rule

That is not in the RUF1XX category (which as @MichaReiser says is a category specifically for Ruff pragma comments)
That by default, only formats Ruff pragma comments. (And maybe also type: ignore comments, since they are standardised across tools according to a specification?)
That can be configured so that it also includes other tool-specific pragma comments such as pyright: ignore, isort: skip_file and pragma: nocover

Currently the rule is handling (aside from # type) # noqa, # ruff: noqa, # flake8: noqa, # isort, # ruff: isort and # fmt. Aren't these all comments that Ruff reads?

They are! I wasn't necessarily criticising anything you were doing -- was just giving my response to Micha's request in https://github.com/astral-sh/ruff/pull/14111#issuecomment-2470227442 on what the scope of the rule should be :-)

I'm in favor of limiting this rule to just Ruff comments, as I have already rewritten this PR a couple of times and I don't feel like redoing it all over again. I'll give custom comments their own rule in another PR.

Feel free to keep this PR small and not implement any configurability now. Small, incremental PRs are definitely encouraged! However, if you want to open a followup PR, please make this rule configurable in the followup PR rather than creating a separate rule just for custom comments. I think Micha and I are aligned that a single, configurable rule would be preferable to two rules that do very similar things.

I do think that we can drastically simplify the implementation because we no longer need to special case different comments. All we need is to match for # (fmt|noqa|...) and then see if it has an optional : following it.

The problem I see with special casing is that it isn't a good fit for a general-purpose, extensible rule; it should instead be a specific rule for noqa.
The question is if we can come up with some general rules that work for all suppression comments without being specific to any pragma comment and that allows easy configuration:

Require a space between # and name in # `
Require no space left of a : but require a space right of it: # name: ignore ok, # name:ignore not-ok
Require no a space left of a , but require a space right of it: # type: ignore[a, b] is ok, type: ignore[a,b] isn't
Require no space around [ but require a space right of ] if it isn't the end of the comment.

The rule doesn't require that any suppression comment is valid. E.g. it accepts #type: ignore, a, b, cd t
Note: What's interesting is that e.g. pyright's documentation uses a space before [: # pyright: ignore [reportPrivateUsage, reportGeneralTypeIssues] whereas mypy recommends using no-space # type: ignore[<code>] (which I prefer)

A general purpose rule that handles all kinds of pragma comments. It only enforces a single space between # and the keyword and, optionally, that the colon is followed by a space. We can add a configuration option to support custom pragma codes.

Making this rule extensible is also what I've suggesting in https://github.com/astral-sh/ruff/issues/10160#issuecomment-1971452721 . Even if it comes as a follow-up PR, I'd like if it could handle comments that Ruff doesn't need to be aware of (like pyright)


[Feature request] bosh deploy --recreate --resume

We are trying to work through a large --recreate deploy in BOSH, and it's very painful to see it fail due to some transient error on AWS, and have to restart the whole thing again.
It would be nice if BOSH could resume a previous task under some circumstances, if it failed for some reason like timeouts and other transient failures. This would prevent us from spending hours recreating VMs that had already been recreated in the previous run.

@Kaixiang bosh doesnt recreate recreated VMs, so something must be going on wrong with the env. can take a look.

Talked in person. Consider using ignore instance command. Will wait for your usage feedback.


feat(graphql-toolkit-http): add graphql-toolkit-http crate

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.52%. Comparing base (ab13ad9) to head (78fac00).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #70   +/-   ##
=======================================
  Coverage   66.52%   66.52%
=======================================
  Files          21       21
  Lines        3361     3361
=======================================
  Hits         2236     2236
  Misses       1125     1125

Flag
Coverage Δ

integration
50.67% <ø> (ø)

unit
34.95% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix ObjectIterator for PHP8

Hi, with PHP8.1 the iterator methods of ObjectIterator must be covariant with the PHP core interfaces.
I didn't know if theres a specific return type for ::current, so I went with the suppress annotation here. Happy to change this to a return type, if there is one?
Deprecated:  Return type of JsonSchema\Iterator\ObjectIterator::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in [...]/vendor/justinrainbow/json-schema/src/JsonSchema/Iterator/ObjectIterator.php on line 42

Deprecated:  Return type of JsonSchema\Iterator\ObjectIterator::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in [...]/vendor/justinrainbow/json-schema/src/JsonSchema/Iterator/ObjectIterator.php on line 52

Deprecated:  Return type of JsonSchema\Iterator\ObjectIterator::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in [...]/vendor/justinrainbow/json-schema/src/JsonSchema/Iterator/ObjectIterator.php on line 61

Deprecated:  Return type of JsonSchema\Iterator\ObjectIterator::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in [...]/vendor/justinrainbow/json-schema/src/JsonSchema/Iterator/ObjectIterator.php on line 71

Deprecated:  Return type of JsonSchema\Iterator\ObjectIterator::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in [...]/vendor/justinrainbow/json-schema/src/JsonSchema/Iterator/ObjectIterator.php on line 81

Deprecated: Return type of JsonSchema\Iterator\ObjectIterator::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in [...]/vendor/justinrainbow/json-schema/src/JsonSchema/Iterator/ObjectIterator.php on line 90

Thanks but given the min php version is still 5.3.3 on this repo, it'd probably be more appropriate to mark all methods with #[ReturnTypeWillChange]

@R4c00n #689

See #726 for the topic of raising the minimum PHP level and supporting newer versions PHP.

Any chance of this making it into the next 5.x release? Adding #[ReturnTypeWillChange] should be enough for now and it would still be compatible with PHP 5.3.

Any chance of this making it into the next 5.x release? Adding #[ReturnTypeWillChange] should be enough for now and it would still be compatible with PHP 5.3.

We are working on bringing the project back alive, you can see more in the discussions. We are however not planning to do anything with the 5.x branch but only focus on the upcoming 6.x and forward. Secondly in it's current state this PR would break the support of older PHP versions which is still part of the 5.x branch.

This PR was ported in #746 which address the raising on the minimum version PHP as a whole including pipelines.
Closing this PR for now


PowerShell command for disabling automatic writeback of Microsoft 365 groups

The PowerShell command under step 2 of the "Disable automatic writeback of all Microsoft 365 groups" section doesn't work in a existing environment.
The PowerShell should probably have a Set-AzureADDirectorySetting instead, as seen in this comment: https://github.com/MicrosoftDocs/azure-docs/issues/82180#issuecomment-940873465

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

ID: 35863b41-f4b7-a772-b9d7-119b8eb08830
Version Independent ID: 2db4eafa-79cb-9401-baf6-6902a1593972
Content: Modify group writeback in Azure AD Connect - Microsoft Entra
Content Source: articles/active-directory/hybrid/how-to-connect-modify-group-writeback.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@fsutil
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Thank you for submitting this issue.  Unfortunately, due to high volumes I was unable to respond to this in a timely manner.  At this point, I am going to close this due to it's age and the possibility that it may have been addressed.  If this is still a problem, please consider submitting a new issue.  Thank you.
#please-close


1.0.0 release does not work on Mac OS X 10.6

Compilation worked fine using PIP, but importing the module fails.
Python 3.2.2 (default, Nov 11 2011, 15:50:38)
[GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.9)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import misaka
Traceback (most recent call last):
File "", line 1, in
ImportError: dlopen(/usr/local/Cellar/python3/3.2.2/lib/python3.2/site-packages/misaka.so, 2): Symbol not found: _PyInt_FromLong
Referenced from: /usr/local/Cellar/python3/3.2.2/lib/python3.2/site-packages/misaka.so
Expected in: dynamic lookup

0.4.2 is still fine. Might be related to the change to use Cython.

Currently installed packages:
20566swerner:~ swerner$ pip freeze
Brownie==0.5.1
Cython==0.15.1
Markdown==2.1.1
PyYAML==3.10
Pygments==1.4
argh==0.14.2
distribute==0.6.24
jasy==0.5-beta1
misaka==0.4.2
msgpack-python==0.1.12
pathtools==0.1.2
polib==0.7.0
wsgiref==0.1.2

Confirmed. Looks like I forgot to check Python 3 before releasing. I will look into this.

I made a quick fix: https://github.com/FSX/misaka/commit/bd2ba1f5283b7f061417077688060a0bcc55e915

Awesome. Thanks!
BTW: I use Misaka in Jasy now (our web tooling solution at Zynga): https://github.com/wpbasti/jasy


Building locally

When I grab the repo and try to build, I get this error;
./clubhouse_options.go:17: undefined: clubhouse.Member
When I look at the Go Clubhouse library I think you use, I don't see Member defined.
Not sure what is going on. Thanks for any help!
Note: I am relatively new to Go

Hey @zdrummond,
You are quite right - I just looked and realized - that I never merged the branch I created to support the V2 upgrade for Clubhouse on that repo. But I had that branch checked out locally so my binary was built from that branch I had checked out.
If you update the clubhouse-go that you've already pulled - you should now be able to build the binary locally.
Sorry for the confusion and thanks for the heads up about that issue.


CQL errors are not shown

If you enter an invalid CQL query and the server responds with an error, the error is not shown. Instead you just get a blank result set.

Now rescues any cassandra errors and returns a formatted json with the error class, and message. Formatted this json on the front-end with an error banner across the top of the screen displaying the error class and message.


Support new chatdown features in Emulator

Conversation update, multi-user handling are now supported in chatdown v1.0.6.
We should add support for those constructs in the V4 Emulator so the transcript will render correctly

Needs design on what do display in the case of multi-user which is currently unsupported in webchat.

This depends on 2 PRs that are outstanding to enable the role property on activities in DirectLineJS & Webchat.
https://github.com/Microsoft/BotFramework-DirectLineJS/pull/79
https://github.com/Microsoft/BotFramework-WebChat/pull/1053

Both PR are merged, but we are hitting another problem, mentioned in Web Chat bug #1110.

This is going to be fixed in Chatdown #377.

I am unable to view anything in transcript file using BotEmulator v4 generated using chatdown 1.0.5


Fix misc deprecations

Coverage decreased (-1.03%) to 58.097% when pulling 9bdb13a877b72dfaadf5f8236503c1f222950e83 on malmaud:fix_dep into 558be653b2c66843d61a5a8e84001e742b84399f on stevengj:master.

Coverage decreased (-1.03%) to 58.097% when pulling 9bdb13a877b72dfaadf5f8236503c1f222950e83 on malmaud:fix_dep into 558be653b2c66843d61a5a8e84001e742b84399f on stevengj:master.

Coverage decreased (-59.1%) to 0.0% when pulling a72aad56e744e1bc916715b15f23f34b8dd1bffd on malmaud:fix_dep into 558be653b2c66843d61a5a8e84001e742b84399f on stevengj:master.

Thanks!


sigsegv in mattermost.SendWebhook

Describe the bug
I run matterbridge to connect an IRC channel and a mattermost channel. mattermost -> IRC works, but each message on IRC crashes matterbridge, so the message doesn't arrive and the bridge rejoins.
The output is (using the docker container 1.10.0):
time="2018-05-19T05:31:15Z" level=info msg="Running version 1.10.0 86865c6" prefix=main
time="2018-05-19T05:31:15Z" level=info msg="Parsing gateway default" prefix=gateway
time="2018-05-19T05:31:15Z" level=info msg="Starting bridge: irc.freenode " prefix=gateway
time="2018-05-19T05:31:15Z" level=info msg="Connecting irc.freenode.net:6667" prefix=irc
time="2018-05-19T05:31:16Z" level=info msg="Connection succeeded" prefix=irc
time="2018-05-19T05:31:16Z" level=info msg="irc.freenode: joining #coreboot (ID: #corebootirc.freenode)" prefix=bridge
time="2018-05-19T05:31:16Z" level=info msg="Starting bridge: mattermost.site " prefix=gateway
time="2018-05-19T05:31:16Z" level=info msg="Connecting using webhookurl (sending) and webhookbindaddress (receiving)" prefix=mattermost
time="2018-05-19T05:31:16Z" level=info msg="mattermost.site: joining irc (ID: ircmattermost.site)" prefix=bridge
2018/05/19 05:31:16 Listening on http://<IP_ADDRESS>:9999...
time="2018-05-19T05:31:16Z" level=info msg="Gateway(s) started succesfully. Now relaying messages" prefix=main
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x48 pc=0x55eda293c0c2]

goroutine 163 [running]:
github.com/42wim/matterbridge/bridge/mattermost.(*Bmattermost).sendWebhook(0xc42041a8a0, 0xc420196100, 0x3f, 0xc420400d9c, 0x3, 0xc420586f00, 0xb, 0xc420457dc0, 0x1c, 0xc420196a80, ...)
        /go/src/github.com/42wim/matterbridge/bridge/mattermost/mattermost.go:388 +0x662
github.com/42wim/matterbridge/bridge/mattermost.(*Bmattermost).Send(0xc42041a8a0, 0xc420196100, 0x3f, 0xc420400d9c, 0x3, 0xc420586f00, 0xb, 0xc420457dc0, 0x1c, 0xc420196a80, ...)
        /go/src/github.com/42wim/matterbridge/bridge/mattermost/mattermost.go:132 +0x70d
github.com/42wim/matterbridge/gateway.(*Gateway).handleMessage(0xc4203f1810, 0xc420196100, 0x3f, 0xc420400d9c, 0x3, 0xc420586f00, 0xb, 0xc420457dc0, 0x1c, 0xc420196a80, ...)
        /go/src/github.com/42wim/matterbridge/gateway/gateway.go:275 +0x475
github.com/42wim/matterbridge/gateway.(*Router).handleReceive(0xc4204152e0)
        /go/src/github.com/42wim/matterbridge/gateway/router.go:101 +0x2ce
created by github.com/42wim/matterbridge/gateway.(*Router).Start
        /go/src/github.com/42wim/matterbridge/gateway/router.go:57 +0x579

Expected behavior
messages passing back and forth, no segfaults.
Environment (please complete the following information):

OS: Linux
Matterbridge version: docker images 42wim/matterbridge:1.10.0 (but also latest)

Additional context
The mattermost-side config is:
[mattermost]
    [mattermost.site]
    Server="chat.coreboot.org"

    # use webhooks. URL is incoming, Bind is outgoing (from mattermost's POV)
    # the URLs look weird but are a-ok from within the containers' POV
    WebhookURL="http://XXX/hooks/XXX"
    WebhookBindAddress="<IP_ADDRESS>:9999"
    IconURL="https://www.coreboot.org/images/1/17/Coreboot64px.png"

    SkipTLSVerify=true
    NoTLS=false

    Team="coreboot"
    #Login="XXX"
    #Password="XXX"
    Token="XXX"
    #PrefixMessagesWithNick=true
    RemoteNickFormat="<{NICK}> "

It crashes at the same place with both login/password and token authentication

As a workaround, you can remove the WebhookURL and WebhookBindAddress if you have Token or Login/Password specified. (unless you need specific webhook features)

Thanks for reporting, it's fixed in master now, a 0.10.1 will be released soon


Two commands for Python Create Environment show up in command palette when using Codespaces

ADD ISSUE DESCRIPTION HERE
Version: 1.79.0-insider
Commit: 2575777b9d3cdb865d61f9f1dfaac1fea9e1bde6
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/113.0.1774.42
Embedder: codespaces

I'm using Python extension version v2023.9.11321009
To reproduce:

Open a Codespace
Install the Python extension
Open the command palette and look for "Create Environment"

@luabud shouldnt this be filed to the extension?