Why "old" digest functions are deprecated?

Hi, I am preparing a slow switch from openssl 1.1 to 3.0 and I know that the "old" digest functions are not recommended and deprecated in 3.0.
I am talking about this for example: https://www.openssl.org/docs/manmaster/man3/MD5_Init.html
I will switch to the new EVP functions, of course, but I was wondering why are the old ones deprecated? Because I understood that internally they can still be used...
Because for most of us, the old ones were easier to use ::MD5(...) instead of calling 5 functions: EVP functions + MD_CTX_new/free
Other than flexibility, maybe a security reason or smth?
Thank you

For a number of reasons. For example:

In some cases you get sub-optimal implementations with the low-level APIs vs the EVP APIs. An example from the "cipher" world (but the same concept applies to digests) is the low-level function AES_encrypt. If you call that you will never get the AESNI optimized version which may be available on your platform.

We want to encourage applications to use a consistent API for all types of digests/ciphers etc. This makes it much easier for everyone to update code as security advice changes. For example you mention the MD5 digest APIs. MD5 is no longer recommended. It's a lot harder to update your code to use some other digest if you've used the low-level APIs vs the high level ones. Looking into the future imagine some algorithm has some major flaw discovered in it that requires a rapid migration away from it to some other algorithm. We want the OpenSSL ecosystem to be as agile as possible to be able to deal with that.

The old APIs no longer fits architecturally with how OpenSSL 3.0 works. All algorithm implementations are now made available by "providers" in OpenSSL 3.0 - for example we have the "default" provider, the "fips" provider and a "legacy" provider.  The low level APIs circumvent all of that which means we have to maintain 2 ways of doing everything (3 actually when you bring ENGINEs into the picture as well). This leads to unnecessary code bloat and complexity....which is definitely something you want to avoid in a crypto library. Ideally we would have removed the old ways completely - but that would have been too big a breaking change.

Thank you for the explanations @mattcaswell.

@mattcaswell what a nice reply! I think it deserves a place in the wiki.

Yes, it's a great reply.  Also put it in the FAQ?

I believe it is also a good idea to point at a few resources showing how insecure MD5 and others have been long deprecated although still in widespread use, in part because of a lack of agility in existing applications due to scarce agility in popular legacy crypto APIs (including OpenSSL low level ones).

https://shattered.io/ makes a good job at making easy to understand how broken SHA-1 (and even more MD5) is (SHAttered is from 2017, but SHA-1 attacks have been a reality since 2005, and NIST officially deprecated it already in 2011)
https://en.wikipedia.org/wiki/MD5 has also a very good summary. Basically broken since 1996, and repeatedly abused by white-hat and black-hat attackers violating both collision and preimage reistance.

@romen I know, MD5 was just an example that came to my mind. :-)

@romen I know, MD5 was just the first example that came to my mind. :-), I am using SHA256.

Yes, my comment was directed more towards enriching the very good answer by @mattcaswell in the optic of making it a part of a Wiki or FAQ entry (and for those that reach this answer searching on github issues).
I think we have a responsibility to sensitize our users regarding the level of security risks of using the legacy API and the legacy implementations: as a security researcher I would go even as far as saying that, looking at current —after decades of deprecation!— adoption rates in the wild of MD5 and SHA-1 (or DES to venture into other domains), I feel —personally and not as a voice for the OpenSSL project— this is an area where I would prefer to ditch legacy to force existing applications to migrate to newer and more secure choices.
The OpenSSL project can't yet remove these APIs due to the promises it made, so I believe all members of the project share the burden of raising awareness of the security risks we are exposing the users to when they pick legacy APIs.
Even more given the fact that, as long as the compiler or the linker does not throw a warning —given how conservative we as a project are even with applying deprecations!—, maintainers of existing applications could be even unaware that their applications is insecure, and users of such applications can be even less aware of it.

* https://en.wikipedia.org/wiki/MD5 has also a very good summary. Basically broken since 1996, and repeatedly abused by white-hat and black-hat attackers violating both collision and preimage reistance.

Violating preimage resistance? Really? Can you point to any practical preimage attack on MD5?
Wikipedia talks only about: "In April 2009, an attack against MD5 was published that breaks MD5's preimage resistance. This attack is only theoretical, with a computational complexity of 2^123.4 for full preimage." That does not really look practical.
You probably mean chosen prefix collision attacks which are much more useful than the generic collision attacks. And yes both SHA-1 and MD5 are susceptible to this attack and moreover their Merkle-Damgard construction also provides ability to choose the suffix.

* https://en.wikipedia.org/wiki/MD5 has also a very good summary. Basically broken since 1996, and repeatedly abused by white-hat and black-hat attackers violating both collision and preimage reistance.

Violating preimage resistance? Really? Can you point to any practical preimage attack on MD5?
Wikipedia talks only about: "In April 2009, an attack against MD5 was published that breaks MD5's preimage resistance. This attack is only theoretical, with a computational complexity of 2^123.4 for full preimage." That does not really look practical.
You probably mean chosen prefix collision attacks which are much more useful than the generic collision attacks. And yes both SHA-1 and MD5 are susceptible to this attack and moreover their Merkle-Damgard construction also provides ability to choose the suffix.

@t8m I did not intend to claim anything more than it is written on that Wikipedia entry, and I did not distinguish between more or less practical attacks.
Anyway, the same authors of that paper, published further improvements in 2013, but I am not aware of further published research on breaking its preimage resistance.
I am not saying the attack is now practical, but then again the fact that no further published results seem to be available does not mean that there aren't more viable practical attacks.
One has also to consider that there might be little incentive for public research to venture further into the topic, as it could be seen as a waste of resources: the prospective impact of research results attacking something that the research community considers a relic of an age past and already completely broken (even if industry is unable to move on quickly enough) is arguably low, but still the efforts to further improve the theoretical results are probably considerable and it is unclear how much scientific value might be yielded by the engineering efforts to achieve what industry deems a "practical" attack.
This is the classic set of conditions in which white hat teams have very little incentive while black hat teams have all the incentive to keep advancements secret.

Anyway, I believe for most users the details of how practical a preimage attack is when collision attacks are practical is of little relevance.

I reacted just because from that sentence I thought you know about some practical exploit for the preimage weakness.

And of course that does not mean there is not a practical attack that is secret.


No dpm_solver Error during inference/sampling

Question
After running training on custom dataset, the ./results/ folder produced models of these three types:

/kaggle/input/medsegdiff-trials/results/emasavedmodel_0.9999_040000.pt
/kaggle/input/medsegdiff-trials/results/optsavedmodel040000.pt
/kaggle/input/medsegdiff-trials/results/savedmodel040000.pt

For inference, in the model_path argument, which checkpoint should I provide? I am not clear about what each of them signifies.
References
Training Logs:
Last check-point:
--------------------------
| grad_norm   | 2.13     |
| loss              | 0.0117   |
| loss_cal        | 0.00869  |
| loss_cal_q0  | 0.00925  |
| loss_cal_q1  | 0.00853  |
| loss_cal_q2  | 0.00879  |
| loss_cal_q3  | 0.00816  |
| loss_q0        | 0.0419   |
| loss_q1        | 0.00343  |
| loss_q2        | 0.00113  |
| loss_q3        | 0.000812 |
| mse_diff      | 0.0117   |
| mse_diff_q0 | 0.0419   |
| mse_diff_q1 | 0.00343  |
| mse_diff_q2 | 0.00113  |
| mse_diff_q3 | 0.000812 |
| param_norm  | 263      |
| samples       | 7.16e+04 |
| step             | 1.79e+04 |
--------------------------

Error during inference:
Note: For all the three modeltypes I am getting this error " No dpm-solver".
Logging to ./results/
creating model and diffusion...
sampling...
no dpm-solver

---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
/tmp/ipykernel_23/238904562.py in <module>
    206
    207 if __name__ == "__main__":
--> 208     main()

/tmp/ipykernel_23/238904562.py in main()
    162                 step = args.diffusion_steps,
    163                 clip_denoised=args.clip_denoised,
--> 164                 model_kwargs=model_kwargs,
    165             )
    166

/kaggle/input/codebase-medsegdiff/MedSegDiff-master/guided_diffusion/gaussian_diffusion.py in p_sample_loop_known(self, model, shape, img, step, org, noise, clip_denoised, denoised_fn, cond_fn, model_kwargs, device, progress, conditioner, classifier)
    569                 model_kwargs=model_kwargs,
    570                 device=device,
--> 571                 progress=progress,
    572             ):
    573                 final = sample

/kaggle/input/codebase-medsegdiff/MedSegDiff-master/guided_diffusion/gaussian_diffusion.py in p_sample_loop_progressive(self, model, shape, time, noise, clip_denoised, denoised_fn, cond_fn, org, model_kwargs, device, progress)
    638                         clip_denoised=clip_denoised,
    639                         denoised_fn=denoised_fn,
--> 640                         model_kwargs=model_kwargs,
    641                     )
    642                     yield out

/kaggle/input/codebase-medsegdiff/MedSegDiff-master/guided_diffusion/gaussian_diffusion.py in p_sample(self, model, x, t, clip_denoised, denoised_fn, model_kwargs)
    444             clip_denoised=clip_denoised,
    445             denoised_fn=denoised_fn,
--> 446             model_kwargs=model_kwargs,
    447         )
    448         noise = th.randn_like(x[:, -1:,...])

/kaggle/input/codebase-medsegdiff/MedSegDiff-master/guided_diffusion/respace.py in p_mean_variance(self, model, *args, **kwargs)
     88         self, model, *args, **kwargs
     89     ):  # pylint: disable=signature-differs
---> 90         return super().p_mean_variance(self._wrap_model(model), *args, **kwargs)
     91
     92     def training_losses(

/kaggle/input/codebase-medsegdiff/MedSegDiff-master/guided_diffusion/gaussian_diffusion.py in p_mean_variance(self, model, x, t, clip_denoised, denoised_fn, model_kwargs)
    320             else:
    321                 pred_xstart = process_xstart(
--> 322                     self._predict_xstart_from_eps(x_t=x, t=t, eps=model_output)
    323                 )
    324             model_mean, _, _ = self.q_posterior_mean_variance(

/kaggle/input/codebase-medsegdiff/MedSegDiff-master/guided_diffusion/gaussian_diffusion.py in _predict_xstart_from_eps(self, x_t, t, eps)
    342
    343     def _predict_xstart_from_eps(self, x_t, t, eps):
--> 344         assert x_t.shape == eps.shape
    345         return (
    346             _extract_into_tensor(self.sqrt_recip_alphas_cumprod, t, x_t.shape) * x_t

AssertionError:

Inference configuration
def create_argparser():
    defaults = dict(
        data_name = 'NUCLEI',
        data_dir="./kmms_test/kmms_test",
        clip_denoised=True,
        num_samples=1,
        batch_size=1,
        use_ddim=False,
        model_path="", # Here I gave the model paths
        num_ensemble=5,      #number of samples in the ensemble
        gpu_dev = "0",
        out_dir='./results/',
        multi_gpu = None, #"0,1,2",
        dpm_solver = True,
        debug = True,
    )
    defaults.update(model_and_diffusion_defaults())

    return defaults

I have the same question. Who can answer the question? Thank you very much.

Hey @cyz21,
I was able to overcome this error. One needs to set the dpm_solver=True after defaults.update(model_and_diffusion_defaults()).
So you can do something like:
args.dpm_solver = True
Hope this helps!
However, I am not stuck due to CUDA out of memory error, only able to sample and infer one image.

Hey @cyz21, I was able to overcome this error. One needs to set the dpm_solver=True after defaults.update(model_and_diffusion_defaults()).
So you can do something like: args.dpm_solver = True
Hope this helps!
However, I am not stuck due to CUDA out of memory error, only able to sample and infer one image.

Thank you for your reply! In addition to this, I also have doubts about your initial question. What's the difference between savedmodel_XXXX.pt, optsavedmodel_XXXX.pt, emasavedmodel_XXXX.pt？Which one should I choose to use?Thank you again!

Hey @cyz21, I was able to overcome this error. One needs to set the dpm_solver=True after defaults.update(model_and_diffusion_defaults()).
So you can do something like: args.dpm_solver = True
Hope this helps!
However, I am not stuck due to CUDA out of memory error, only able to sample and infer one image.

Thank you for your reply! In addition to this, I also have doubts about your initial question. What's the difference between savedmodel_XXXX.pt, optsavedmodel_XXXX.pt, emasavedmodel_XXXX.pt？Which one should I choose to use?Thank you again!

You can give the ema or savedmodel in the inference checkpoint path. optmodel gave me error.
Hope this helps!

Hey @cyz21, I was able to overcome this error. One needs to set the after .dpm_solver=True``defaults.update(model_and_diffusion_defaults())
So you can do something like: args.dpm_solver = True
Hope this helps!
However, I am not stuck due to CUDA out of memory error, only able to sample and infer one image.

Hey, I have the same question that when I run segmentation.py, it only sample and infer 2 images. I wonder how you solving this problem? Thanks a lot!


frontend: Remove l10 support from shared components

Overview
We do not support l10n in the applications consuming @vdk/shared. The l10 functionality should be removed.
DoD

Remove l10 component files from @vdk/shared.
Remove the SimpleTranslateService
Refactor existing components to not pass the translate service and work without it.

Triaged. Closed as stale.


Fixed Light-Dark Mode, Added Prettier Config

:bug:  Added ThemeContext for easier access and toggling of theme. Uses React Context so that theme works on all pages #250
:art:  Added Prettier config, and updated Eslint to work with Prettier

Hii @NiketanG, can you please share some screenshot shots of changes you have done.

Hii @NiketanG, can you please share some screenshot shots of changes you have done.

Sure !

It looks nice @NiketanG, but it will be more attractive if you will do the same for background:

It looks nice @NiketanG, but it will be more attractive if you will do the same for background:

Sure, will do !

@Ritwik880 Do you have a Dark Variant of the background Image ?

@Ritwik880 Do you have a Dark Variant of the background Image ?

No

@NiketanG Background is not suiting with text. Please fix this.

@Isha2103 @Ritwik880 I've updated the PR with new Fixes. Take a look:

@NiketanG  Looks great

Thank you for hard work @Ritwik880

thanks you @NiketanG


New bank account tests failing

(failure)[https://github.com/trustbloc/sandbox/runs/3449375720#step:5:236)
this could be due to these missing changes in k8s configurations in adapter-rp

The flow is failing with below error:

{"errMessage":"malformed credentials: malformed credential: parseWalletResponse: invalid presentation submission: input descriptor id [driver_license:local] requires schemas [0xc0005e77a0] which do not match vc with @context [[https://www.w3.org/2018/credentials/v1 https://trustbloc.github.io/context/vc/examples/mdl-v1.jsonld]] and types [[VerifiableCredential mDL]] selected by path [$.verifiableCredential[0]]"}

This is due to mismatch between PEx logic between adapter (afg) and wallet.

This has been fixed - https://github.com/trustbloc/sandbox/pull/1194


Clarify validator responsibilities

Validators are expected to periodically (once per epoch? once per N epochs?) submit a SignedValidatorRegistration to builder software but I do not think this is document anywhere outside of the comment in the https://github.com/ethereum/beacon-APIs
We should craft a spec/validator.md that contains some light prose on the expected validator flow to be able to participate in the external builder network.

Agreed. We should also outline how validators should propose blocks -- i.e. they should still request against local EL in case the external builder fails, there should be some mechanism to force local EL block if the previous N beacon blocks had empty/invalid execution payloads, etc. I started something a while back but it didn't make it into v0.0.0:

The Builder API offers a protocol for proposing blocks built by external entities, but it is not a complete replacement for locally sourced blocks. Builders may timeout, go offline, or otherwise behave dishonestly. It’s crucial that validators be prepared for this.

A potential expansion of this process, which takes into account results from the Builder API, could be as follows:

First, the CL client will need to decide on a deadline for releasing the block to the network. For illustrative purposes, suppose that deadline is 4 seconds into the slot. This is the maximum amount of time the CL is willing to expend on block production. If no result has be retrieved from the Builder API at this point, the CL should sign and release a block using a local payload. Now, working backwards, the CL can decide the maximum amount of time it will wait for an ExecutionPayloadHeader from the builder. The API specifies that the builder must respond immediately to header requests with the best header on hand, so it is fair game for the CL to expect this request should be quite fast.

Once the CL has received both a local payload and an external payload header, it should compare the expected value of proposing each. This isn’t trivial today, because GetPayload doesn’t return the expected value of local payloads. This is a bit of an open question as to how to handle this in the short term. In the medium term, we should expand the method’s response to also return the expected value of the local payload. After deciding which payload is more profitable, the CL should seal and release it. If the CL uses an external payload header, it will need to submit the SignedBlindedBeaconBlock to the builder to get the unblinded values. This shouldn’t cut much into the deadline though, as the builder will have all the necessary data (and incentive) to gossip the signed block as soon as it receives the request.


ENYO-5434: VideoPlayer bottom control renders

Issue Resolved / Feature Added
Some apps control the visibility of bottom controls via imperative APIs (showControls and hideControls) because there are cases where app wants to prevent showing controls upon newly loaded/played event. For example, the app does not want to display controls at everytime video changes when in store demo mode.
Because apps control the visibility of bottom controls in a similar way as frameworks do, it could render unwanted results.
Resolution
Apps shouldn't need to control the visibilities via calling imperative APIs if we allow them to prevent the default action via event.
Additional Considerations
The general idea behind this is that apps want to display bottom controls when initially playing a video in most cases. So instead of letting apps to take care of, we fixed the framework to support that in #1661.
Proposed change can still break the app as long as apps try to handle the same requirement on their end. We can remove supporting "auto showing controls" and let app control everything entirely, too.
Enact-DCO-1.0-Signed-off-by: Stephen Choi<EMAIL_ADDRESS>

My initial implementation of allowing to prevent "play" event wouldn't work as play button pressed on a remote should only display the mini feedback. So I've decided to handle all visibility control in loadstart event. However, preventing loadstart doesn't seem intuitive as it needs to reset internal states no matter what. I've created an alternative approach to add additional prop in #1829.

Closing in favor of #1829


"Accept-Ranges: bytes"  is missing from static file endpoints

Accept-Range header is missing while calling HEAD/GET method to a static file path.

But http-server supports Range header to access partial content.  And Accept-Range is only present in  such response.

Some clients checks this header to resume interrupted request.
Tell us about your environment

exact http-server version: 0.12.3
Node version: 10.18.1
Platform: Linux

#536  addresses this by including Accept-Ranges: bytes with every response.
Merged to be released in v0.13.0.

Should be fixed by #536, please reopen if this is not the case


Options not reactive

Component does not update if you change colors or chart options

Interesting. I'll need to explore why this isn't working as expected. This would be a good place to start.

@jnordberg while it's true that updating the colors prop (or other non-data props) does not update the chart, I believe that this is a limitation of the update method in the frappe-charts library itself. I'd recommend filing an issue over there, or seeing if there is a similar one which has been filed over there (looks like it may already have been worked on: https://github.com/frappe/charts/pull/179).
Once that change lands, we will be able to make an update here to allow props such as colors to update the underlying chart.


kalendar: add missing dependency kirigami-addons

Description of changes
At the moment, certain parts of kalendar don't work due to a missing dependency. For example:

Launch kalendar from a terminal
Go to settings > configure kalendar
Click the "Accounts" tab.
Nothing shows in the GUI, the following is output in the terminal:

kf.kirigami: (qrc:/ViewSettingsPage.qml:9:1: module "org.kde.kirigamiaddons.labs.mobileform" is not installed
    import org.kde.kirigamiaddons.labs.mobileform 0.1 as MobileForm
    ^)
file:///nix/store/q7f6z1qw1579flszg5dm5045vj89xwx4-kirigami2-5.102.0/lib/qt-5.15.8/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:37:5: Unable to assign SettingsPage_QMLTYPE_396 to Page_QMLTYPE_37
kf.kirigami: (qrc:/ViewSettingsPage.qml:9:1: module "org.kde.kirigamiaddons.labs.mobileform" is not installed
    import org.kde.kirigamiaddons.labs.mobileform 0.1 as MobileForm
    ^)
kf.kirigami: (qrc:/SourceSettingsPage.qml:16:9: Type AgentConfigurationForm unavailable
            AgentConfigurationForm {
            ^, file:///nix/store/kd6rl651b8yf1000g0rix7zz1rf2wrhj-kalendar-22.12.2/lib/qt-5.15.8/qml/org/kde/akonadi/AgentConfigurationForm.qml:9:1: module "org.kde.kirigamiaddons.labs.mobileform" is not installed
    import org.kde.kirigamiaddons.labs.mobileform 0.1 as MobileForm
    ^)

This PR adds the missing dependency, kirigami-addons. With this PR, the account settings page appears and functions correctly, allowing users to add calendars to kalendar.
Things done

Built on platform(s)

[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I'm not using kalendar recently, please remove me from the maintainers

@ofborg build kalendar


fix(ioncube extension): remove installation for PHP 8

Description

Reference. According to this thread, PHP 8.0 is not supported yet.
Motivation and Context

PHP 8.0 currently is not supported, so it should be removed from the building for this version.
Types of Changes

[x] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).

Definition of Done Checklist:

[x] I've read the Contribution Guide.
[ ] I've updated the documentation. (refer to this for how to do so).


Test for minimum supported plugin versions

Split from #1793

Other than typescript-eslint, that is.


fix(tabs): adding 'active' ng-class for tab  tags for bootstrap 4

adds 'active'/'disabled' classes for anchor links to affect proper active tab styling in bootstrap 4.

We are not giving BS 4 support at this moment.

@foxandxss, @wesleycho allowed a PR in last week or so.  IMO, if the change doesn't break anything and doesn't add bloat, I don't have an issue with it.  Thoughts, guys?

I don't have an issue as well, I just don't want to give the false impression that we are supporting BS4

I'll work to address any regressions that get reported.  To my knowledge the active toggle class on anchor tags, along with the 'nav-link' class on the anchor tag are all that are needed for bs4, and I didn't notice any real negatives to including these tags in existant bootstrap versions.

I do know bs4 makes more sense going forward for ng2, but my feeling (with tabs at least) was that this was low hanging fruit to get to a minimal level of functionality.

This adds a $watch from ng-class - I do not think this is wise while support Bootstrap 3. The nav-link class is fine because it is a harmless change, but this has perf ramifications.
I'm inclined to reject this.

I suppose that makes sense. I could look at possibly using a different template for BS4 that would remove the duplicated watch, if that'd be preferred. but that may mean enlarging the scope of the pr beyond what the team would desire. Any suggestions?

At this time, I think you should just override the default template with your own template in $templateCache.
When we investigate BS4 support, we can then make the modifications, but that won't be for a little while.


Markdown numbered lists not rendered correctly

Bug Description
If I have a code like this:
{#each something as thing}
1. {thing.name}

{/each}

I expect ordered list. However I get 1. always.
Also, {/each} must be set in this case after empty line, or evidence errors.
On Slack, it is said that issue is due to md compiler, MDSveX.
Severity

[x] Low - I'm able to keep using Evidence as normal, but flagging this for the team to fix

Expected Behavior
Normal ordered list.
Error Messages and Screenshots
Here is the error when I remove the empty line before /each:
Error

Note: I can't copy paste this err without OCR, you should fix that too.
Workarounds
One workaround is to use custom iterator:

{#each categories as category}

{++i}. {category.category}

{/each}

or
{#each categories as category, i}

{++i}. {category.category}

{/each}

The other method is to use html:

{#each forms as form, i}

{form.name}

{/each}

Do you want to contribute a fix for this bug?
If so, let us know and we can help you get started.
Environment Information
Operating System (e.g., MacOS, Windows 10): Windows 10
Node version (node -v): 19.0
npm version (npm -v): 8.19.3
Package versions (npm list --depth=0<EMAIL_ADDRESS>

Adding context:
This is due to the way MDSveX parses each blocks.
We don't have a good fix right now, the workarounds above are probably the best solution at this stage.
Possible avenues to fix:

Change our markdown compiler to something else
Create our own Each component that wraps the functionality of Svelte's {#each} block

For unordered lists (ie bullet points) I have found a CSS hack to be relatively visually effective for removing additional spacing


execute multiple calls in a single transaction

How is it possible to sign and send multiple calls using the snap?
It seems starkNet_sendTransaction function only accept one call data base on open-rpc doc.
I'm looking for something like this:
https://www.starknetjs.com/docs/API/classes/Account#execute
https://github.com/starknet-io/starknet.js/blob/1843e3c95724e801f437d9efd8d57e1ef154e743/src/account/default.ts#L275

Hello @RanGojo we have starkNet_executeTxn it's on the main branch but not deployed to prod yet

@wantedsystem Cool. I'm looking forward for this feature.

@wantedsystem Hello, Do we have any update on this?

Thanks

@RanGojo the package has released and you can use it above endpoint


Add Refund of charges to Colosseum

Adds a refund of charges to the colosseum if you die before finishing

[x] I have tested all my changes thoroughly.

:rocket:
This description was created by Ellipsis for commit 549e5760c62d8186cfa002b3bb6f04ebcf38e879

Summary:
Added functionality to refund charges for specific items if a user dies before completing the Colosseum.
Key points:

Added: Refund of charges for scythe_of_vitur, venator_bow, and blood_fury if a user dies before completing the Colosseum in src/lib/colosseum.ts.
Updated: startColosseumRun function in src/lib/colosseum.ts to include charge calculations.
Added: refundChargeBank function in src/lib/degradeableItems.ts to handle the refund logic.
Updated: colosseumCommand in src/lib/colosseum.ts to pass charge information.
Updated: ColoTaskOptions interface in src/lib/types/minions.ts to include charge fields.
Updated: colosseumTask in src/tasks/minions/colosseumActivity.ts to process charge refunds on death.
Updated: simulateColosseumRuns in src/mahoji/commands/simulate.ts to include charge parameters.

Generated with :heart: by ellipsis.dev

@ellipsis-dev can you review this pr

@ellipsis-dev can you review this pr


Yii debug enhancement

hi
I worked with cakephp ,but recently I have switched to Yii.
Yii is Great , but its debug is unbearable!
in cakephp app does not stop running while notice or warning occuring.
you can see cakephp notice debug bellow:

By clicking on error title (warning or notice) , you can see more details:

is there any chance that add this kind of debug mode in future releases?
Thank you for your attention.

No. Notice in Yii is considered a really serious thing that should stop the app. It won't be changed.

you can set php error_reporting to skip notices but that is not recommended.

Is there any way to enhance Yii Debugger and insert Notice in my own projects?
For example changing current plugin or writing new plugin.

you can extend the ErrorHandler class and configure the application component.


Github Wrapped Contribution Count does not get updated.

Tried opening my Github Wrapped in a Private Window. Contribution count isn't getting updated.

Sorry I'm not sure I fully understand. Could you describe further/provide a screenshot?

I checked out my github wrapped a few days ago on the github trends website. It was 1812 contributions in total on that day. I checked out the thing today again using the same URL, but the new contribution count doesn't seem to reflect. I have 1865 contributions now, but on the website it still shows 1812.

The count only includes up to the end of November. I might change this in the future, I will update here if I do.

Oh alright. Thanks buddy! Thats some awesome work, out there. :)


Failed to activate the existdb package

[Enter steps to reproduce:]

install existdb package from package manager
restart Atom

Atom: 1.21.1 x64
Electron: 1.6.15
OS: Mac OS X 10.12.6
Thrown From: existdb package 0.6.0
Stack Trace
Failed to activate the existdb package
At Attempt to change mapping for "tei" extension from "application/tei xml" to "application/xml". Pass `force=true` to allow this, otherwise remove "tei" from the list of extensions for "application/xml".

Error: Attempt to change mapping for "tei" extension from "application/tei xml" to "application/xml". Pass `force=true` to allow this, otherwise remove "tei" from the list of extensions for "application/xml".
    at Mime.define (/packages/existdb/node_modules/mime/Mime.js:32:17)
    at /packages/existdb/lib/existdb-tree-view.coffee:22:18)
    at Object.activate (/packages/existdb/lib/existdb.coffee:38:25)
    at Package.module.exports.Package.activateNow (/Users/username/Applications/Atom.app/Contents/Resources/app/src/package.js:253:25)
    at /Users/username/Applications/Atom.app/Contents/Resources/app/src/package.js:225:38
    at Package.module.exports.Package.measure (/Users/username/Applications/Atom.app/Contents/Resources/app/src/package.js:99:21)
    at /Users/username/Applications/Atom.app/Contents/Resources/app/src/package.js:218:32
    at Package.module.exports.Package.activate (/Users/username/Applications/Atom.app/Contents/Resources/app/src/package.js:215:40)
    at PackageManager.activatePackage (/Users/username/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:690:42)
    at config.transactAsync (/Users/username/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:665:36)
    at Config.module.exports.Config.transactAsync (/Users/username/Applications/Atom.app/Contents/Resources/app/src/config.js:367:24)
    at PackageManager.activatePackages (/Users/username/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:663:23)
    at PackageManager.activate (/Users/username/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:646:50)
    at /Users/username/Applications/Atom.app/Contents/Resources/app/src/atom-environment.js:854:36

Commands

Non-Core Packages
atom-ide-ui 0.5.1
existdb 0.6.0
minimap 4.29.7

@mark-donoghue The public-repo's version of atom-editor-support, v0.2, is out of date. The current version, which ships with the atom-existdb package and which atom should prompt you to detect it connects to an eXist-db instance that doesn't have it installed, is v0.2.7. I'd suggest uninstalling v0.2 via the Dashboard, and then in Atom selecting Packages > existdb > Reconnect. This should cause Atom to detect that the atom-editor-support app isn't installed and offer to install the bundled v0.2.7 version.

hey @joewiz, I was so happy to see your instructions, but I'm afraid they didn't do the the trick for me. Installing the exist-db package alongside an exist instance without the atom-editor-support package doesn't actually install the atom-editor-support at all.
I installed the v.0.2.7 manually, but even with it there, I'm still getting the same error...

Wolfgang, do you have any idea how to fix this?

This particular error was fixed with 5242a7c, which unfortunately is not included in the latest release. For now you can follow the instructions on building from source

I have just uploaded the last version of existdb Atom support package from build (0.2.7) but it throws still the same. In Atom I have the version 0.6.0 of the atom-existdb package. I need to connect to an external server via https. Could it be the problem? (I have set the URL in atom-existdb config.)

I can confirm that the original issue as reported remains valid with the current version of atom, 1.24.0. When trying to install the existdb package via Atom > Preferences > Install > existdb > Install (the current release listed is 0.6.0), installation fails with:

Failed to activate the existdb package. Attempt to change mapping for "tei" extension from "application/tei+xml" to "application/xml". Pass force=true to allow this, otherwise remove "tei" from the list of extensions for "application/xml". The error was thrown from the existdb package. This issue has already been reported.

It appears that several of Wolfgang's commits since the 0.6.0 release address compatibility problems with Atom 1.21.0.
In the short term, installing the package built from source and restarting Atom does prevent this error (i.e., the one that @welblaud reported above). The version of the companion application for eXist (atom-editor-support) that is included in the version of the atom-existdb atom package built from source is 0.2.7 and was committed on June 15 (much newer than the version in the exist-db.org public-repo, 0.2.2). There have been some important fixes made in commits to the atom-editor-support since June 15.
So to sum up, I think a new release of both the atom-exist atom package and the atom-editor-support eXist app are in order.
Wolfgang, I'd be happy to assist in the preparation of these updates if it would help. The best way to give me the necessary permissions for committing and publishing may be for you to migrate the repositories to the eXist-db organization as discussed in recent Community Calls.

For me it does not work. I use Atom 1.25 (beta), the package atom-existdb is 0.6.0, in eXist (3.6.0) I have the builded packate 0.2.7. Should I restart the server? Or could it be associated with the beta version of Atom? (I have to use it because I need the portable version.)

You need to also build a new version of atom-existdb, since 0.6.0 will not work. Just follow the instructions. The problem is that one of the dependencies, the mime package, had API-breaking changes, that were fixed with 5242a7ce36b12b23542404709ffd72bb9d267bf7.

Thank you! It somehow helped and Atom started to solve dependencies. The last thing (strange!) was it asked whether I wish to install server side support app. The strange part was after the question it tried to show the app version but instead of the version numbers it logged HTML of the main page of my app (Home).
When I agreed to install the support despite the strange log, it threw:
Stack Trace
Uncaught TypeError: Cannot read property 'onSelect' of undefined
At D:\C_temp\Atom\exist-db-package\atom-existdb\lib\existdb-tree-view.coffee:173

TypeError: Cannot read property 'onSelect' of undefined
    at Request._callback (D:/C_temp/Atom/exist-db-package/atom-existdb/lib/existdb-tree-view.coffee:173:39)
    at Request.self.callback (/packages/existdb/node_modules/request/request.js:186:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:194:7)
    at /packages/existdb/node_modules/request/request.js:1163:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:191:7)
    at /packages/existdb/node_modules/request/request.js:1085:12)
    at Object.onceWrapper (events.js:293:19)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:188:7)
    at endReadableNT (_stream_readable.js:975:12)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

Commands
     -1:21.9.0 core:delete (input.hidden-input)
  3x -1:21.5.0 core:move-right (input.hidden-input)
     -1:20.8.0 editor:select-to-end-of-line (input.hidden-input)
  2x -1:20.6.0 core:select-left (input.hidden-input)
     -1:19.8.0 intentions:highlight (input.hidden-input)
     -1:19.6.0 core:paste (input.hidden-input)
 29x -1:17.9.0 core:move-left (input.hidden-input)
     -1:16 core:move-right (input.hidden-input)
  7x -1:15.7.0 core:backspace (input.hidden-input)
     -1:14.2.0 intentions:highlight (input.hidden-input)
     -1:13.8.0 core:save (input.hidden-input)
     -1:11.7.0 editor:select-to-end-of-line (input.hidden-input)
  2x -1:11.4.0 core:select-left (input.hidden-input)
  7x -1:09.0 core:backspace (input.hidden-input)
     -0:59.3.0 intentions:highlight (input.hidden-input)
     -0:58.8.0 core:save (input.hidden-input)

Non-Core Packages
atom-ide-ui 0.9.2
atom-material-syntax 1.0.8
atom-material-syntax-dark 1.0.0
atom-material-ui 2.1.3
atom-runner 2.7.1
atom-ternjs 0.18.3
busy-signal 1.4.3
caprice-dark-syntax 2.0.0
deep-purple-syntax 0.2.18
duotone-dark-sky-syntax 2.1.0
existdb 0.7.0
hyperclick 0.0.0
ide-java 0.8.1
ide-typescript 0.7.5
idle-theme 0.1.0
intentions 1.1.5
joehannes-steampunk-ui 0.2.11
linter 2.2.0
linter-ui-default 1.6.10
monokai 0.24.0
steam-pirate-ui 0.6.1

I moved this repo and atom-editor-support to the eXist-db github and published a new release. For some reason apm assigned it version 0.8.0 instead of 0.7.0 (no idea why), but I hope this fixes the issue.

Closing for now, as the original issue is no longer evident with version 0.8.0 of the atom-existdb package (install via Atom's preferences > Packages). Please open a new issue for any problems with the new version.


Clearfixing

Another one from the History Books of CSS:
I'm wondering if we should include some advice on clearfixing?
For those unfamiliar, if you have a parent element with floated children inside, the parent won't contain them.
In other words, this:

Left Content

Right Content

Results in this:

For the longest time, it was common practice to fix this by just inserting a utility element with clear: both applied to it.

Left Content

Right Content

I actually stuck with this method for a long time until I discovered that applying overflow: auto or overflow: hidden to the parent element works just as well.
For more complex cases, there are clearfixes like the micro clearfix hack.
Sitepoint did a pretty great rundown of the various methods and I threw together a demo demonstrating the various techniques as well.
Since this is a fairly common use case (at least in my experience), I'm wondering if we should include some guidance within the web guide.
Any thoughts? Opinions?

I don't typically see

used alot anymore with the advent of CSS frameworks to build upon. Moreso, with the examples of Flexbox given recently in the WSG meetings.
I would be of the opinion -- the sooner it dies (and how can I help it die) then all the better. That being said I say we don't mention it. More to the point I might argue we should have a "top 5" used CSS frameworks on campus this year. While we're here to advocate to standards I don't necessarily agree everything should be created from scratch -- which is a broad sense is being advocated here.
Eg, http://stackoverflow.com/questions/14973317/understanding-bootstraps-clearfix-function
The approach you've outlined is a trivial implementation of boostrap's .clearfix. Yet to be more far-reaching and backwards compatibles FB's is about 1000's more cryptic; yet remains consistent in old browsers. Which is why I mention offering a rundown of modern CSS frameworks (or even just links to useful CSS frameworks).
Kinda annoying builtwith.com doesn't show CSS framework usage ... http://builtwith.com/webguide.ucsb.edu
If builtwith.com had a CSS usage metric it would have been an interesting task to run some analytics on the campus CSS (framework) usage.

I agree with you @tenken on both fronts: (1) let's not provide guidance on this and (2) let's discuss possibly providing guidance on front-end frameworks.


switch: Fix #17602 When toggling the value causes it to be destroyed

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

Toggling the switch destroys the component generating the error:
Error in nextTick: TypeError: _this.$refs.input is undefined switch

fixes #17602

@cs1707 Have you reviewed this?


FATAL:  sorry, too many clients already

What I'm trying to achieve
Don't see this error.
Steps to reproduce the problem

Start saleor with python manage.py runserver 0:8000
Use dashboard for awhile (about 15 minutes or so) e.g. creating new products, update existing data

Occasionally dashboard stopped working and checking browser's network log reveals GraphQL query errors as "FATAL:  sorry, too many clients already". I did googles and it likely a known issue with many Django apps, unfortunately there is no reliable fix/workaround.
I looked at pg_stat_activity and saw several dead connections (from Saleor) 3-4 days ago while I have only used this saleor instance less than an hour a day.
Whenever I saw this error saleor stopped working (500 error) and I needed to restart it.
What I expected to happen
No error.
Screenshots and logs

[ ] dev (current main)
[x] 3.5.0
[ ] 2.11
[ ] 2.10

Operating system:

[ ] Windows
[x] Linux
[ ] MacOS
[ ] Other

@tiendq Please keep in mind that runserver is not a production solution, it's meant for local debugging and is quite limited. You can try restarting it to see if fixes your problem.

@tiendq Please keep in mind that runserver is not a production solution, it's meant for local debugging and is quite limited. You can try restarting it to see if fixes your problem.

I had to restart saleor every time I saw this error, I guess it will happen after I use saleor for awhile (and open many connections). But why too many connections? And I think even in development mode it shouldn't happen.

I have never seen this happen. Did you modify any part of the stack? Custom PostgreSQL configuration?

We noticed when using https://github.com/saleor/saleor-platform setup on a dev server

@saleor/devtools folks, could you try to reproduce?

Do you use anything like this db_from_env = dj_database_url.config(conn_max_age=500)? Some guys (not all) could fixed the issue by dropping conn_max_age, more detail here.

@manojLondhe can you provide on what commits are your saleor-platform submodules?

I believe this problem should be fixed in the current main branch. We got rid of connection reuse as it's no longer supported by Django 4 in ASGI mode.


Error in `phantomjs': double free or corruption (!prev)

I have no idea why it started to do this, what I did :-/
I'm using master, commit eddb0db1d253fd0c546060a4555554c8ee08c13c from Fri Oct 10 06:40:42 2014
Dump is attached.
4f1d6457-46fc-9bae-5d548296-12425060.dmp | uploaded via ZenHub

@ariya I have a same problem!


diag_need_check_nil inacurate warnings on or and truthy

or

truthy

get_best_follower_capsule returns table|nil

Those 2 are fixed. Thank you,

Type is not narrowed to remove nil after nil check


Fix TaskResult Example in Documentation

Fix enum case with Associated Value having no 'let' to get local value.
hope it helps!

- case .factResponse(.success(fact)):
+ case let .factResponse(.success(fact)):

is it okay to suggest this one either?
Type FeatureAction is not the conformance of Reducer, rather Action.
- enum FeatureAction: Equatable {
+ enum Action: Equatable {
   case factButtonTapped
   case factResponse(TaskResult<String>)
}

Hi @ValseLee, yep, can you start a new PR?

absolutely :)


False positive for Style/TrailingComma cop

In RuboCop version 0.32.0, given the following configuration:
Style/TrailingComma:
  EnforcedStyleForMultiline: 'comma'

And the following code:
Foo.new({})

RuboCop generates the following offense:
Put a comma after the last parameter of a multiline method call.
Foo.new({})
        ^^

With autocorrect enabled, the code is changed to:
Foo.new({},)

Something is clearly wrong. This was not a problem in earlier versions of RuboCop.

I made a pull request with a possible fix. Basically the cop interpreted the expression, correctly, as a method call. As can be seen in the code, because the last argument, the {} has no comma, and comma is the setting, an offense was reported.
I simply added a check to not report an offense if the first argument of the function is an empty hash, as can be seen here.
My only concern, as mentioned on the pull request is that my solution would create false negatives. For example, it would not report an offense for Foo.new({}, ... \n /// 5), when perhaps it should.
Thoughts?

The error message says:

Put a comma after the last parameter of a multiline method call.

IMHO, it should only apply to multiline method calls. For example:
Foo.new(
  "first arg",
  "second arg",
)

Hmm so maybe the problem is that Foo.new({}) should never have been called multiline in the first place. I'm guessing that has something to do with the new definition of multiline (seen here), although I may be totally wrong about that.

I thought we argued this style through and decided against this default.
IMO, rubocop should not default to disputed standards. If the community standard is unsettled no rubocop default setting should enforce a standard even if it is override able in settings. Out of the box behavior should be non controversial.
Or a close to possible as a community standard can be. This style had real opposition.

@philoserf This is not the default. I am overwriting the default, as I say in the first line of the description with the configuration:
Style/TrailingComma:
  EnforcedStyleForMultiline: 'comma'

My miss. Comment retracted.

I updated my pull request off of @sferik's observation that this method should not have been labelled multiline? in the first place. Let me know if I can make any changes to improve it!

My setup is exactly like @sferik and I'm also getting this problem.

I’m running into the same exact issue.
Here’s another case where the cop gives incorrect output:
Foo.new(
  'blah blah',
  { owner: 'me', author: 'myself' },
  'more blah',
)

RuboCop reports:
stuff.rb:6:14: C: Avoid comma after the last parameter of a method call, unless each item is on its own line.
  'more blah',
             ^


Add beautiful logo for readme on repo

This repo needs to be more beautiful <3 .
Explanation:
The sparrow which is the symbol of swift and the green color is the wink of Android
Generated by AI

Thanks for generating the image! However I think we're fine without a logo for now, if we add one I want to put some thought into what it should look like first before adopting anything.


Add download site to RGP Lua

In keeping with Jari's original idea of integrating a script repository with JW Lua, it occurred to me that a simple link button in RGP Lua that launches to our documentation site would be a simple step in that direction. Which is the most "official" top-level URL?

For users, it would probably be: https://jwluascripts.com/help
For developers, it's: https://jwluascripts.com/docs/getting-started
Also, is there any reason why someone may wish to use JW Lua instead of RGP Lua? I should probably also update the docs to link to RGP Lua instead of JW Lua since Jari has given it his blessing.

As to why someone would wish to use JW Lua, anyone still running on a 32-bit version of Finale would have to use JW Lua. Also, the 64-bit version still works quite well in Windows. There are no issues with the edit dialog scrolling, so it's still a handy dev platform for quick prototyping at least.
Also, the Windows version is not facing imminent incompatibility with CPU chip changes. Although there is an ARM version of Windows, it is not necessarily the future of Windows, and I am not aware of any plans at Makemusic to support native operation with ARM Windows.

I should add that for Windows users it is perfectly feasible to continue running much older versions of Finale than it is on Mac. I'm fairly certain I could open Finale 2000 under the latest version of Win10. (I'll try after I finish migrating my Win dev env.) And for sure I can run Finale 2010 with JW Lua under the current version of Win 10.

I'm closing this, because we've addressed what I needed to know.

Ok, so if I understand you correctly, the reasons why someone would choose JW Lua over RGP Lua are:

If they're on a 32-bit version of Finale
If they wish to develop scripts on Windows for the developer experience

For all other cases, there's no real need to use JW Lua instead, though especially on Windows JW Lua works perfectly fine.

Is that roughly what you're saying?
For context, I'm trying to figure out if I should rewrite the docs to only point to RGP Lua as that's the most recent canonical version, or if I should also link to JW Lua.

That's all I can think of. Maybe also if they have scripts that make
extensive use of UserValueInput, but that's fairly easy to replace with
FCCustomWindow. (I've replaced it in all of ours.)
32-bit Finale is probably more prevalent on Windows than Mac. I was able to
run my copy of WinFin 2000 on the latest Win 10, so there is a lot less
incentive to upgrade Finale on Windows. That said, I believe the earliest
version JW Lua 0.54 supports is F2010. At any rate, I asked this on the
list and that was the earliest version anyone mentioned.
Perhaps the main focus in the docs should be on RGP Lua, but a brief
mention of JW Lua aimed at 32-bit Finale users might be helpful.
(Developers can take care of themselves or use 3rd party tools as we do.)
On Sat, Jan 15, 2022 at 9:34 PM Nick Mazuk @.***> wrote:

Ok, so if I understand you correctly, the reasons why someone would choose
JW Lua over RGP Lua are:

If they're on a 32-bit version of Finale
If they wish to develop scripts on Windows for the developer
experience

For all other cases, there's no real need to use JW Lua instead, though
especially on Windows JW Lua works perfectly fine.
Is that roughly what you're saying?
For context, I'm trying to figure out if I should rewrite the docs to only
point to RGP Lua as that's the most recent canonical version, or if I
should also link to JW Lua.
—
Reply to this email directly, view it on GitHub
https://github.com/finale-lua/jw-lua-scripts/issues/123#issuecomment-1013803709,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYB6X64YZZIFK4VI4JYMFLUWI4BLANCNFSM5LKWW3SQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>

BTW, speaking of converting UserValueInput to FCCustomWindow, if we can ever get the mixin library sorted, that seems like a perfect class for simplifying the DX. I hope we hear from @ThistleSifter about this soon.

Sounds good


Error creating Terraform demo

I attempted to create the demo for Terraform and received the following:
Error while creating release definition: Tasks with versions 'Replace tokens in terraform file:5.*' are not valid for deploy job 'Agent job' in stage Dev.
AB#3908

Kindly Install the required extensions manually from the marketplace and try to provision the project.
Refer to https://github.com/microsoft/AzureDevOpsDemoGenerator/issues/626 for more info


Project structure

After some discussions, I think having different project/module is a better structure. Our APIs are versioned independently and having Gradle will allow more flexibility (e.g.: single Git repo with multiple API model/SDK with different version)

👍


Bluring out status bar

Is it possible to also blur out status bar once the menu appears on top?

The status bar isn't inside an accessible view / window, meaning drawViewHierarchyInRect:afterScreenUpdates: can't be sent to a view / window containing the status bar.


Implement the designs for listing attachments & Enhance file upload end-points

Overview
Links to jira tickets

https://quartech.atlassian.net/browse/BHBC-967
https://quartech.atlassian.net/browse/BHBC-968

This PR contains the following changes

End to end upload flow with list view, ability to delete individual files, view them in list, and also view their data using a signed url

This PR contains the following types of changes

[x] New feature (change which adds functionality)
[x] Enhancement (improvements to existing functionality)

How Has This Been Tested?

Local, S3, database

Screenshots

No tests in this PR - all tests coming in separate pull request 👼🏼


Passing application_name parameter has no effect

I'm trying to pass connection_parameters into the pgo config like so...
 let db_config =
    pgo.Config(
      ..config_from_url,
      connection_parameters: [#("application_name", "hello")],
    )

But my postgres logs don't reflect the change:
connection authorized: user=postgres database=main application_name=nonode@nohost

I'll keep looking at the Erlang code, not my strong suite! Hoping that someone more familiar could take a look and make sure we're passing the connection parameters.

Understood. As I was trying to explain, I don't have much experience with Erlang so my personal progress on this will be very slow. I was hoping, if the bug was in Erlang and shallow, that it might be obvious to someone with more experience.


Discuss Android 4.4.4 Support

Currently android 4.4.4 is not working. Should we fix this?

We will drop android 4.4 since it is outdated and would need extra implementation work for small range of devices.


docs : fix document format

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[x] Docs related to the changes have been added/updated (if applicable)

The code block is not in the right position here.
https://datahubproject.io/docs/metadata-ingestion


Add Generic HTTP-based SD

Proposal
Use case. Why is this important?
This SD should look exactly the same as the file-based SD, except that it is fetched from an HTTP endpoint rather than the local fs.
I work on a large project for storage monitoring and I think many face the same issue that we do. We don't want to open a SD request for our own Project, but a generic HTTP-based would satisfy everyone.
I am also coding in Go, so if the community thinks this is a good idea, I could prepare a pull request.

I am also coding in Go, so if the community thinks this is a good idea, I could prepare a pull request!

This is discussed here: https://docs.google.com/document/d/1tVeuzjpU4-TiYPNWJXKmcyIuZF6A2tUq270RbBT5zho/edit

awesome, thanks for sharing the link

is someone already working on this? should I go ahead and try to implement it myself?

There are still disagreements over the design doc.

This is being implemented in #8839

Can this issue be closed now?

Yes 🥳


Not compatible with Python 3.8

I am trying to use another library that depends on this one on Python 3.8, and it gives this error during import:
    def shuffle(self, seed: Optional[Union[int | float | str | bytes | bytearray]] = None) -> "slist[_K]":
TypeError: unsupported operand type(s) for |: 'type' and 'type'

From the internet:

| was added in python 3.10, so not available in python 3.8.

So you either want to remove 'python 3.8/3.9' label from your latest releases, or make it actually compatible with older versions.

@kiranzo totally agree.
Fixed in this commit: https://github.com/asuiu/streamerate/commit/6aad71938385285be9a59de3782085a16b1712bf
Deployed new version on PyPi: https://pypi.org/project/streamerate/1.1.1/
Issue fixed.


Thank

How to use ios

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

ID: b400e326-face-ddc7-d9ac-ab08488bb75a
Version Independent ID: 1da91dfc-2a76-5be4-1376-959e6c3635a9
Content: Windows Server
Content Source: WindowsServerDocs/Windows-Server.md
Product: windows-server-threshold
GitHub Login: @jaimeo
Microsoft Alias: jaimeo

Hi, is there specific information that you're looking for? Thanks!

This is not much information for windows server
http://www.educationbangla.com/


Currency column type

Today users have to create by themselves a currency column (and implement the necessary filters and functions).
It'll be awesome if pluto had this by default

[x] factory PlutoColumnType.currency
[x] PlutoColumnTypeCurrency
[x] sort column
[x] PlutoCurrencyCell
[x] edit column value
[x] Filter column
[x] New 5.1.0 aggregation functions
[ ] Tests

@bosskmk still in dev, but already showing some results on the table:

@bosskmk it's ready for your review.
If everything is ok, and you want me to add the tests instead of you, please warn me.

@Macacoazul01
Thanks for the code contribution.
I'll check this out and make sure it's released in the next version.

@Macacoazul01
Deployed on PlutoGrid 5.1.2.
https://weblaze.dev/pluto_grid/build/web/#feature/currency-type-column
thank you


Added set_bin_list method to HAWCLike to allow use of non-contiguous …

…sets of bins and bins with arbitrary string names now that these features are supported by LiFF.  Also added plotting of pulls as alternative to residuals in HAWCLike.display, turned on using pulls=True.

@sammarinelli thanks for this!
The tests are failing, but I suspect it is because the docker container we are using for the test contains a version of LiFF which is not updated enough.
Which version of LiFF should I install to support this feature?

I talked with @giacomov offline, but I'll post our conclusion here for anyone else following along.  The new functionality requires a more recent version of AERIE than the latest release, which is from last April.  @giacomov is going to try building against the AERIE trunk instead.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5156437). Click here to learn what that means.
The diff coverage is 38.46%.

@@            Coverage Diff            @@
##             master     #165   +/-   ##
=========================================
  Coverage          ?   75.11%
=========================================
  Files             ?      110
  Lines             ?    11317
  Branches          ?        0
=========================================
  Hits              ?     8501
  Misses            ?     2816
  Partials          ?        0

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 5156437...1fc9206. Read the comment docs.

@sammarinelli I updated the test environment with the most recent version of aerie, and now all tests are passing successfully.
Thanks for this contribution, I am going to merge it now.


Create documentation on how to get multiple different clients to register

Motivation
We currently are trying to build a website that has content split across two different projects in Kentico Kontent.
Our requirements are to be able to register separate IDeliveryClient registrations.
We have attempted to solve this using the attached code in the Clients folder.
There are two files. One called ICachingAppsOrgDeliveryClient.cs and the other is ICachingArrtOrgDeliveryClient.cs
In our startup.cs we register those two clients but we can not figure out how to have the DeliveryClientBuilder to return anything other then an IDeliveryClient. Which causes our cast to fail.
You can see this if you search for the comment "//ISSUE HERE" in startup.cs.
Once we can figure out how to register these two different delivery clients we can then use the two different clients in a single controller:
public class DualKenticoController : Controller
{
    public DualKenticoController(ICachingArrtOrgDeliveryClient kenticoDeliveryClient1, ICachingAppsOrgDeliveryClient kenticoDeliveryClient2, ILogger<ContentPageController> logger)
    {
        //Code here
    }
}

Sadly I can't figure out how to register this properly.
Kentico Multiple Different Client Issue.zip
Proposed solution
Documentation on registering multiple different delivery clients in a single .NET Core project.

Hey @xantari , great question.
You have several options:

Create a factory class that would create instances of the DeliveryClient based on a name and inject the factory into the controllers.

public interface IDeliveryClientFactory    { IDeliveryClient Get(string name); }

// + an appropriate implementation of IDeliveryClientFactory

public class DualKenticoController : Controller
{
    public DualKenticoController(IDeliveryClientFactory factory)
    {
      // factory.Get("xyz")....
      // factory.Get("abc")....
    }
}

Use the beta version of the SDK that saves you from writing the factory as it already contains it. (Things may change in the beta though...be prepared for that).
Use a DI container that supports named/keyed services (e.g. autofac). Autofac docs, autofac example

3 is a generally accepted practice. Once we have 2 finished, it'll be the best practice for the scenario.
Let me know if you have more questions.

Cool, okay the beta version and/or the factory pattern will probably be our way forward. Thanks.

@petrsvihlik Can you show me example code on how to get two "AddWebhookInvalidatedCachingClient" services registered with this method?
Can't seem to figure it out...

@petrsvihlik  Does this look correct? If so would be helpful to get this added to the boiler plate example and perhaps dancing goat sample.
services.AddSingleton<IContentLinkUrlResolver, CustomContentLinkUrlResolver>();
services.AddSingleton<ITypeProvider, CustomTypeProvider>();
services.TryAddSingleton<ICacheManager, CacheManager>();

var deliveryOptions = new DeliveryOptions();
Configuration.GetSection(nameof(DeliveryOptions)).Bind(deliveryOptions);

var deliveryOptionsArrt = new DeliveryOptions();
Configuration.GetSection("DeliveryOptionsArrt").Bind(deliveryOptionsArrt);

services.AddWebhookInvalidatedCachingClientToFactory("Client1", builder =>
{
	return DeliveryClientBuilder
	   .WithOptions(_ => deliveryOptions)
	   .WithTypeProvider(builder.GetService<ITypeProvider>())
	   .WithContentLinkUrlResolver(builder.GetService<IContentLinkUrlResolver>())
	   .Build();
}, (options) =>
{
	//if (Environment.IsDevelopment())
	//{
	//    options.StaleContentTimeout = TimeSpan.FromSeconds(1);
	//    options.DefaultTimeout = TimeSpan.FromHours(1);
	//}
	//else
	//{
	options.StaleContentTimeout = TimeSpan.FromSeconds(2);
	options.DefaultTimeout = TimeSpan.FromHours(24);
	//}
});
services.AddWebhookInvalidatedCachingClientToFactory("Client2", builder =>
{
	return DeliveryClientBuilder
	   .WithOptions(_ => deliveryOptionsArrt)
	   .WithTypeProvider(builder.GetService<ITypeProvider>())
	   .WithContentLinkUrlResolver(builder.GetService<IContentLinkUrlResolver>())
	   .Build();
}, (options) =>
{
	//if (Environment.IsDevelopment())
	//{
	//    options.StaleContentTimeout = TimeSpan.FromSeconds(1);
	//    options.DefaultTimeout = TimeSpan.FromHours(1);
	//}
	//else
	//{
	options.StaleContentTimeout = TimeSpan.FromSeconds(2);
	options.DefaultTimeout = TimeSpan.FromHours(24);
	//}
});

ServiceCollectionExtensions.cs
public static IServiceCollection AddWebhookInvalidatedCachingClientToFactory(this IServiceCollection services, string name,
	Func<IServiceProvider, IDeliveryClient> baseClientFactory,
	Action<CacheOptions> configureCacheOptions = null)
{
	if (configureCacheOptions != null)
	{
		services.Configure(configureCacheOptions);
	}

	services.TryAddSingleton<ICacheManager, CacheManager>();

	services.AddTransient<IConfigureOptions<DeliveryClientFactoryOptions>>(sp =>
	{
		return new ConfigureNamedOptions<DeliveryClientFactoryOptions>(name, options =>
		{
			options.DeliveryClientsActions.Add(() =>
			{
				return new CachingDeliveryClient(
					 sp.GetRequiredService<ICacheManager>(),
					 baseClientFactory(sp));
			});
		});

	});

	return services;
}

Hmm... That didn't work.  Couldn't get the new one in the Beta 6 package setup to use multiple WebhookInvalidatedCachingClient classes...

@tomasjurasek may I ask you to help out @xantari ? (we've made some improvements in the beta SDK which may make the registration easier, but I'll let Tomas answer)

@xantari I'm preparing demo application wit features like DeliveryFactory, Cache, and Registration of multiple clients.

@tomasjurasek OK thanks, I am trying to register multiple "WebhookInvalidatedCacheClients" that are in your boilerplate sample...

@xantari  We support these scenarios like DeliveryClientFactory, Multiple configurations of client, Memory cache in beta SDK. Look at demo app - https://github.com/tomasjurasek/kontent-delivery-demo

@tomasjurasek How do you register your custom ITypeProvider and IContentLinkUrlResolver using this new method?
Also, how do you attach your own HttpClient to each client?
How do you associate a DynamicRouteValueTransformer class to each registered client?

I'm using Beta6 and get this:

@xantari  now, we have  Beta9. Please look at the demo application, there is referenced.
Of course, you can register specific implementation for each client, for this scenario you can register named client with DeliveryClientBuilder and pass the implementation there.
Or if you want to register custom implementation for all clients, you can use ServiceCollection registration like services.AddSingleton<ITypeProvider, CustomTypeProvider>()

Internal reference: https://kentico.atlassian.net/browse/CTC-871

we'll update the wiki https://github.com/Kentico/kontent-delivery-sdk-net/wiki
and especially this page: https://github.com/Kentico/kontent-delivery-sdk-net/wiki/Instantiating-DeliveryClient-with-Configuration-API-and-DI-in-ASP.NET-Core-MVC-apps
with all the new configuration options

updated docs: https://github.com/Kentico/kontent-delivery-sdk-net/wiki/Registering-the-DeliveryClient-to-the-IServiceCollection-in-ASP.NET-Core#registering-multiple-clients
RTM to be released on Thursday


doc/md/guides: Add docs for functional and descending indexes in PostgreSQL and SQLite

Merged with https://github.com/ariga/atlas/pull/1486. I deleted your change to package-lock.json.


Fix pause/unpause on update does not update status correctly

Fixes #10

It seems we had some disconnect on the exact nature of what was causing issue here, I will attempt to explain here.
We began our investivation into the sync/async nature of the way the broker attempts to pause and unpause a cluster since that was reported as "returning too early". But in fact, the issue was that upon sending the pause command the broker was just not reporting back the proper "In progress..." status to the osb-runtime. https://github.com/mongodb/atlas-osb/commit/5a7824ce6effdd60db6df94f865a515aa6352547 fixes this issue.


Style layer button

Completed https://github.com/Project-OSRM/osrm-frontend-v2/commit/bd1b210d3359430f0bb10e97f6d879ffccaceab2


Make the snake appear directly at x=0 when he touches the right side …

…of canvas[closes #91]

👍


Retry json decoding errors from the Kubernetes API to prevent flaky tests.

What type of PR is this?
/kind bug
What this PR does / why we need it:
This retries json decoding errors returned by the CreateOrUpdate method to prevent flaky tests.
Which issue(s) this PR fixes:

Fixes #415
Does this PR introduce a user-facing change?:

NONE

Had to re-run the build because it turns out Circle CI gets confused if you have it enabled on your fork and you open a PR :man_facepalming:


Update project to be compatible with React 0.14

These are the changes I've been looking for for 3 days. Thanks @bL0p.


Python ENV based logger

Nodejs has a very nice ENV based logger called debug. This is especially helpful in our containers for writing logs to disk instead of having to chase them in stdout/err. We should find and use a similar library for our python based containers

This might be what we are looking for: https://docs.python.org/3/library/logging.html

Basic logging style using the logging library
gps2tsdb_1  | INFO:root:Initing Postgres obj

A nice feature would be to set the logging level from the Docker compose file either using strings or numbers.
Do we want to change the timestamp format in the logs? Do we want to compare the logging timestamp to the database timestamp?

@jarett-lee I think we should set the logging level via env variables like this. That is the natural way to pass arguments into containers.

Example output as of most recent changes:
gps2tsdb_1  | 2020-10-05 02:02:33.517 UTC INFO     Ensuring tables are setup properly
gps2tsdb_1  | 2020-10-05 02:02:33.518 UTC WARNING  Ensuring GPS point table is a timescaledb hypertable
gps2tsdb_1  | 2020-10-05 02:02:33.520 UTC ERROR    Finished settting up tables

It looks like basicConfig can handle strings on its own, but I had to put in some logic to handle integers.

I think those changes satisfies what @abalmos was asking for? If so, I think we are close to being able to open the PR and start reviewing the code itself?

Unfortunately I don't have the time to review at the moment, but anything along those lines is an improvement and seems worthy of opening a PR. It will also let us test how the actions deal with external PRs.
Out of curiosity, does this work like debug does? For example:
$ DEBUG="err:*,trace:sub-system-I-care-about:*" python my-broken-service.py

would output all error messages and only traces from "sub-system-I-care-about".
In short, debug just has a "tag" for each message and the typically pattern is to write the tags like "type:system:sub-system:sub-sub-system:..." and then the DEBUG evn is a pattern match on those tags.
BTW -- I'm not saying we should or should not make that work, I am just wondering what we have now.

As far as I know that is not currently implemented. Is that a feature in the nodejs debug lib? It seems quite helpful but we are likely limited to the features included in the python logging lib. An external lib may support this but I am unaware of it and would add another dependency

@aaron97neu Correct, that is essentially all that the node debug library does. I'm not familiar enough with the logging module or any other python logging library to know if that is a reasonable comparison or not.

This looks to be the closest but def does not work out the box https://docs.python.org/3/library/logging.html#filter-objects.


check SAPHanaSR >= 0.153, os-release >= 15.1

additional checs for CFSA-83.
Ref: https://jira.suse.com/browse/CFSA-83?jql=key in (CFSA-83)

@aleksei-burlakov don't bother referencing jira from here, just do the opposite. :)
This is a follow-up of #31 right?

@aleksei-burlakov don't bother referencing jira from here, just do the opposite. :)
This is a follow-up of #31 right?

Yes, it's the follows up for both #30 and #31.

@aleksei-burlakov let me summarize what needs to be done here:

change the check logic so that it doesn't rely on the PRETTY_NAME, which won't give any indication of the system actually being SLES4SAP instead of SLES. Also, the check logic must allow for any future SLES4SAP 15 SP version.

@stefanotorresi , as @lee-martin proposed, I used the VERSION_ID instead

use You need at least SUSE Linux Enterprise Server for SAP Applications 15 SP1 or newer as abstract.

Fixed.

use Please install or upgrade to a supported OS version as remediation.

Fixed.

put a link to https://documentation.suse.com/sbp/all/single-html/SLES4SAP-hana-sr-guide-PerfOpt-15 in the references

Fixed.


NonListenerPipeConnectionsAreLoggedAndIgnored fails randomly

Substring issue in HttpClientSlim.GetStatus
[xUnit.net 00:00:29.9233847]     Microsoft.AspNetCore.Server.KestrelTests.ListenerPrimaryTests.NonListenerPipeConnectionsAreLoggedAndIgnored [FAIL]
[xUnit.net 00:00:29.9249778]       System.ArgumentOutOfRangeException : Length cannot be less than zero.
[xUnit.net 00:00:29.9250620]       Parameter name: length
[xUnit.net 00:00:29.9272464]       Stack Trace:
[xUnit.net 00:00:29.9362760]            at System.String.Substring(Int32 startIndex, Int32 length)
[xUnit.net 00:00:29.9365414]         /Users/travis/build/aspnet/KestrelHttpServer/test/shared/HttpClientSlim.cs(80,0): at Microsoft.AspNetCore.Testing.HttpClientSlim.GetStatus(String response)
[xUnit.net 00:00:29.9366463]         /Users/travis/build/aspnet/KestrelHttpServer/test/shared/HttpClientSlim.cs(64,0): at Microsoft.AspNetCore.Testing.HttpClientSlim.<ReadResponse>d__4.MoveNext()
[xUnit.net 00:00:29.9369606]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:29.9371221]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:29.9372878]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:29.9374454]         /Users/travis/build/aspnet/KestrelHttpServer/test/shared/HttpClientSlim.cs(33,0): at Microsoft.AspNetCore.Testing.HttpClientSlim.<GetStringAsync>d__1.MoveNext()
[xUnit.net 00:00:29.9377769]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:29.9379250]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:29.9384108]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:29.9385747]         /Users/travis/build/aspnet/KestrelHttpServer/test/Microsoft.AspNetCore.Server.KestrelTests/ListenerPrimaryTests.cs(310,0): at Microsoft.AspNetCore.Server.KestrelTests.ListenerPrimaryTests.<AssertResponseEventually>d__3.MoveNext()
[xUnit.net 00:00:29.9390012]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:29.9391564]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:29.9393128]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:29.9394813]         /Users/travis/build/aspnet/KestrelHttpServer/test/Microsoft.AspNetCore.Server.KestrelTests/ListenerPrimaryTests.cs(155,0): at Microsoft.AspNetCore.Server.KestrelTests.ListenerPrimaryTests.<NonListenerPipeConnectionsAreLoggedAndIgnored>d__1.MoveNext()
[xUnit.net 00:00:29.9398884]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:29.9400457]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:29.9402044]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:29.9403507]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:29.9405043]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:29.9406604]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:29.9408078]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:29.9409626]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:29.9411180]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
Failed   Microsoft.AspNetCore.Server.KestrelTests.ListenerPrimaryTests.NonListenerPipeConnectionsAreLoggedAndIgnored
Error Message:
 System.ArgumentOutOfRangeException : Length cannot be less than zero.
Parameter name: length
Stack Trace:
   at System.String.Substring(Int32 startIndex, Int32 length)
   at Microsoft.AspNetCore.Testing.HttpClientSlim.GetStatus(String response) in /Users/travis/build/aspnet/KestrelHttpServer/test/shared/HttpClientSlim.cs:line 80
   at Microsoft.AspNetCore.Testing.HttpClientSlim.<ReadResponse>d__4.MoveNext() in /Users/travis/build/aspnet/KestrelHttpServer/test/shared/HttpClientSlim.cs:line 64
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Testing.HttpClientSlim.<GetStringAsync>d__1.MoveNext() in /Users/travis/build/aspnet/KestrelHttpServer/test/shared/HttpClientSlim.cs:line 33
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Server.KestrelTests.ListenerPrimaryTests.<AssertResponseEventually>d__3.MoveNext() in /Users/travis/build/aspnet/KestrelHttpServer/test/Microsoft.AspNetCore.Server.KestrelTests/ListenerPrimaryTests.cs:line 310
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Server.KestrelTests.ListenerPrimaryTests.<NonListenerPipeConnectionsAreLoggedAndIgnored>d__1.MoveNext() in /Users/travis/build/aspnet/KestrelHttpServer/test/Microsoft.AspNetCore.Server.KestrelTests/ListenerPrimaryTests.cs:line 155
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:33.8585785]   Finished:    Microsoft.AspNetCore.Server.KestrelTests

Assigning to @cesarbs for investigation.

@benaadams Are you still seeing this test randomly fail? I ran it in a loop for several minutes and didn't catch any failures.

Nope; will reopen if it occurs again


Tuple type options parses every character as an individual value

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the Typer documentation, with the integrated search.
[X] I already searched in Google "How to X in Typer" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[ ] I already checked if it is not related to Typer but to Click.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
import typer
from typing import Tuple
from pathlib import Path
app = typer.Typer()

@app.command()
def useless(): # at least two commands are needed for typer to run properly
    pass

@app.command()
def test(tupl: Tuple[Path] = typer.Option(None, '--tuple', '-t'), help='Tuple values'):

    for x in tupl:
        print(x)

app()

# RUN
# python3 app.py test -t AAA BBBBB

# PROBLEM
# should be interpreted as tuple("AAA", "BBBBB") but is interpreted as tuple("A", "A", "A")

# ERROR with :  python3 app.py test -t AAA BBBBB
# Error: Invalid value for '--tuple' / '-t': 1 values are required, but 3 were given.

# ERROR with : python3 app.py test -t A B
# Error: Got unexpected extra argument (B)

Description
I am trying to use a Tuple type option which is supposed to work as mentioned below :
python3 app.py --tuple  value1 value2
This should be interpreted as tuple('value1', 'value2')
BUT
The app seems to interpret the tuple as being the individual characters of value1:   tuple('v', 'a', 'l', 'u', 'e', ''1') and throws an error
Error: Invalid value for '--tuple' / '-t': 1 values are required, but 6 were given.
Operating System
Linux
Operating System Details
Ubuntu 20.04 LTS
Typer Version
0.4.0
Python Version
3.8.10
Additional Context
No response

Your test should be:
def test(tupl: Tuple[Path, Path] = typer.Option(None, '--tuple', '-t'), help='Tuple values'):
https://typer.tiangolo.com/tutorial/multiple-values/options-with-multiple-values/


update scheduling-hugepages page

update scheduling-hugepages page

Please rebase this pull request against master to bring in a work-around for issue #22222.

@fancc please rebase this one onto master branch? it has been here for 2 months.

@fancc please rebase this one onto master branch? it has been here for 2 months.

done

/uncc

/lgtm
/approve


Moving music streaming to a thread for desktop

This PR is an attempt to move music streaming to a thread for desktop backends.
It still a work in progress, it almost work as expected but there are some corner cases to fix, maybe i'll need to change the synchronization strategy.
I only changed Lwjgl3 backend for now, i'll copy/paste to lwjgl2 backend once it's all clear.
I need to find time to finish it but i thought it was preferable to PR this WIP for discussion as a replacement of #6452.

I need so hard this PR merged, having the same issues that origin this. What is the status of this? Need a hand?


Maintain keyword syntactic sugar for non-keywords

[:foo, bar: :baz]

should be formatted without changes but it gets formatted to
[:foo, {:bar, :baz}]

The AST is [:foo, {:bar, :baz}] so there is no way to know if the user has used keyword synactic sugar or not.
If we were to go about implementing this, should we enforce keyword syntactic sugar for all tuples of size 2 in non-keyword list? Personally, I prefer desugaring since there is a clearer delineation between elements with the tuple curly brackets.

Yeah I know there is no way to know, I meant to always go with the sugar syntax. I always use that anyways. Thoughts @josevalim @lexmag?

We should go with the keywords list one. Question: is each atom in the
keywords list wrapped in a block?
José Valimwww.plataformatec.com.br
http://www.plataformatec.com.br/Founder and Director of R&D

Okay, we can go with the sugar syntax.
@josevalim only the value atom is wrapped in a block:
iex(28)> Code.string_to_quoted "[:foo, bar: :baz]", wrap_literals_in_blocks: true
{:ok,
 {:__block__, [line: 1],
  [[{:__block__, [line: 1], [:foo]}, {:bar, {:__block__, [line: 1], [:baz]}}]]}}


Error E5113 on Ubuntu

Error detected while processing /home/mgrosser/.config/nvim/init.lua:
E5113: Error while calling lua chunk: /home/mgrosser/.config/nvim/init.lua:59: attempt to index field 'keymap' (a nil value)
stack traceback:
~/.config/nvim/init.lua:59: in main chunk

The nvim-Version 0.6.x was to old. An update to 0.9.x fixed the issue.

The nvim-Version 0.6.x was to old. An update to 0.9.x fixed the issue.


Fix axes mapping when using Axes custom param, fixes #409, #411

I tested on Fah-Kwang, the new axes are like that:
    <axes>
        <axis default="400" maximum="700" minimum="200" name="Weight" tag="wght" />
        <axis default="0" maximum="10" minimum="0" name="Italic" tag="ital" />
    </axes>

The code wrongly assumed that the "Axes" custom parameter was always used in conjunction with the "Axis Location" parameters for masters.

That's funny. I thought I specified the axis location in the master dialog...

Can you test the branch with Cantarell? I didn't

The version in question is https://gitlab.gnome.org/GNOME/cantarell-fonts/raw/801f581de296a1d2d0ddca3db6565d4bca5044d3/src/Cantarell.glyphs. This PR makes it work.

I don't understand why it didn't work before. Axis locations were all specified?

In your Cantarell file, none of the masters have the Axis Location custom parameter

But "Axis coordinates" are all specified?!

oh gosh.. what's "Axis Coordinates" now?!

I suppose a new way to specify coordinates :O

"Axis Location" is something else than this number box, it's a way to map master design locations (the number box in the screenshot) to user locations. It was explained by Georg here: https://github.com/googlei18n/glyphsLib/issues/280#issuecomment-342786012
Your Cantarell files doesn't have the Axis Location custom param as seen here:

The axes coordinates above are nothing new, they actually end up in the glyphs file in the same fields as weightValue, widthValue, customValue etc, as confirmed by Georg there: https://github.com/googlei18n/glyphsLib/issues/280#issuecomment-374912389

So, how to proceed? Does your fix check all the boxes?

I think it does, it fixes your two problems and there are no regressions. By the way we could also probably close #280 now? Are you and @m4rc1e are building variable fonts with success?

Building a VF works, as do static instances.

The UI calls it it "Axis Locations" but the underlying data structure in the file has not changes. There are still the weightValue, widthValue, customValue, customValue1 ... for the first axis, use the weightValue, for the second axis use the widthValue and so on. The UI will show the proper axis names but under the hood, nothing has changed. I couldn’t change the file structure for v2.5.


Release app

Before i18n feature will be done create first release of the app. v1.0.0 and branch release/v1.0 accordingly

Resolved


Added github workflows on release branches and fix migration workflow issues

Feature or Bugfix

Feature
Bugfix

Detail

Add all applicable GitHub workflows to PRs pointing at v2m* branches
fix semgrep finding issue from GitHub workflows from migration script for notifications type --> added nosemgrep as no user input is passed to the SQL query and only code administrators will have access to the query.
fix migration validation: this one is tricky as it succeeds when running it locally and on a real pipeline. It turns out that the issue was not on the migration script itself but on the way we dropped and updated tables in the validation migration stage. For dropping tables, we were using a different schema that the one used in upgrade database. This PR removes the schema_name variable and uses the envname as schema for all cases. One final note, this issue might be related to #788.

Here some screenshots of the resulting local schema for the notification table after running make drop-tables and make upgrade-db

Relates

V2.1 release

Security
Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

Does this PR introduce or modify any input fields or queries - this includes
fetching data from storage outside the application (e.g. a database, an S3 bucket)?

Is the input sanitized?
What precautions are you taking before deserializing the data you consume?
Is injection prevented by parametrizing queries?
Have you ensured no eval or similar functions are used?

Does this PR introduce any functionality or component that requires authorization?

How have you ensured it respects the existing AuthN/AuthZ mechanisms?
Are you logging failed auth attempts?

Are you using or adding any cryptographic features?

Do you use a standard proven implementations?
Are the used keys controlled by the customer? Where are they stored?

Are you introducing any new policies/roles/users?

Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Tested in AWS to verify migrations and validate migrations succeed


[ldd-msn_surface] Add Observational_Intent

Add as a child of the top-level class (Surface_Mission_Information):
<Observational_Intent> Describes the intent and context of the observation
Children:
 Identifies the long-term observational campaign of which this observation is a part
 Identifies the goal of this observation
 Identifies the specific task for this observation
<activity_notes> Provides additional notes regarding the activity
We may end up needing more but that's a good start.  All are cardinality 0:1.

@rgdeen you may have already reviewed but just in case (one last chance although I will close for now):
https://github.com/pds-data-dictionaries/ldd-msn_surface/blob/d620727e58bf612b0cf778d5bee539e85c465cd8/src/PDS4_MSN_SURFACE_IngestLDD.xml#L888

Looks good at a glance, thanks!


Implementing cairo-compile

Hi guys!
Super cool work you're doing! I saw cleopatra was supporting only the equivalent of cairo-run at the moment. Do you envision supporting as well compilation of cairo programs in the future? Or do you intend to stay pegged to the toolchain (with the potential limitations it brings)?
Thanks!

Hi @Nashtare, thanks for the comment. Some news about this will be presented at StarkNet.CC in this front! I will update the issue after StarkNet.CC

Great! Looking forward, thanks! :)

@unbalancedparentheses Do you have any update on this? :)


How to apply csrf token to certain forms only?

When i apply csrf plugin in app.js and it will applying to all forms. If i remove them it is showing error.
I want to send csrf token either through ajax or completely remove for that particular form. How can i achieve that

You will need to make the appropriate customization on the server-side for your ajax handler.  Not sure if you have already done so or not, but I highly recommend reading about CSRF, implementation and token handling: https://owasp.org/www-community/attacks/csrf


Box Component

Feature request 🚀

[ ] I will create Pull Request
[x] It's just a suggestion

Expected

Hey! So, what about a Box component? Just a basic div with no style, basic style properties like padding, width and a  as prop to transform the tag from div to another HTML tag (e.g. form) and support its properties.

Examples
import { Box } from '@geist-ui/core'

function Page() {
  return (
    <Box as="form" py={4} onSubmit={...} action={...}>
      ...
    </Box>
  )
}

Programme (Optional)
Others (Optional)

is anything moving forward?

AFAIK, a completely generic component for any HTML element is pretty hard in TypeScript, I tried to do that but could not complete implementation of the solutions that I found for the types. Maybe it's just me though.
E.g. could not get this accepted answer to work:
https://stackoverflow.com/questions/55969769/typing-a-dynamic-tag-in-react-with-typescript
And approaches like this one do not type-check attributes:
https://www.aleksandrhovhannisyan.com/blog/dynamic-tag-name-props-in-react/
I'd love a slightly more opinionated Box component though, maybe restricted to a subset of HTML tags?
My own version for a current learning project uses CSS modules and just assumes Flexbox.
Currently I only need two types of tags, but for these type-checking should work.
Problem is that this component does not use Geist's design system at all so it definitely is not a suggestion or solution for resolving this issue.
https://gist.github.com/strlns/9a9127637791804cb03922caafc19e59
Also it assumes usage of typescript-plugin-css-modules to ensure that no invalid class names are constructed.
As mentioned here, I'm aware that the usage of CSS modules is not really compatible with geist-ui or idiomatic in its design system.
I just couldn't see an alternative except for styled-components or inline styles, may be lack of experience on my side.


Task 9

Issue: #218
portScan using nmap

Hey @shrut2606
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Hey @shrut2606
Your PR has been merged 🥳🥳 and you have earned 10 points.
Thanks for contributing in OpenCode'24 ✨✨


moment.js is missing

moment.js is missing in 0.5.3 - publish.js references require("moment")

See #116

fixed


Advent of code 2024, day 02

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

Project coverage is 94.50%. Comparing base (bae8c53) to head (3295a7f).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #161      +/-   ##
==========================================
+ Coverage   94.48%   94.50%   +0.02%
==========================================
  Files         372      375       +3
  Lines       12460    12512      +52
  Branches     1297     1304       +7
==========================================
+ Hits        11773    11825      +52
  Misses        556      556
  Partials      131      131

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


Missing Solo MMR?

So I noticed that my solo MMR shows N/A. I tried refreshing the match history (hoping it would also refresh that data). I also checked my MMR section and it shows my MMR all the way up until October 16th 2015. From there is completely disappears.

You need to show your MMR in your ingame profile, then play a ranked game.

So I have to display it on my profile. Alright well thanks. I figured the Yasp bot being in my friends list and my profile being public was enough.

Valve disabled the old player profiles around the time Reborn was released, so the bots are no longer needed.


[bugfix] critic can not update.

What does this PR do?
Fixes
Critic weight cannot be updated due to parameter name modification
Before submitting

[x] Did you read the contributor guideline,
Pull Request section?
[x] Was this discussed/approved via a GitHub issue? Please add a link
to it if that's the case.
[x] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines.
[x] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

@NINGBENZHE  do you know where in the code the issue is occurring?

@NINGBENZHE do you know where in the code the issue is occurring?

I haven't found the issue yet, but after making the modifications, the critic's loss is functioning normally, and the optimizer's functionality has been restored.

ok let me try to pin-point the issue...  and perhaps try to add a failing test?

ok let me try to pin-point the issue... and perhaps try to add a failing test?
You can repeat the same data and observe the critic's loss; it remains unchanged.

I found that the issue was introduced by this PR.
https://github.com/huggingface/trl/commit/16fa13ce728e537a91742571b0c4824fb3a98a30

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@NINGBENZHE can you kindly run make precommit in the root dir to fix the formatting?

@NINGBENZHE can you kindly run make precommit in the root dir to fix the formatting?

I made the submission directly on the web, without using local Git, and only modified the parameter names, so it should not have introduced any new formatting issues. Can you force the merge?

closing as these changes have been merged into the PR #2463