Ramping option of ITC503

Include a software layer for the ramp of the Oxford ITC503:
The ramp rate set for ITC503 is not always what the instrument does, since there is a maximum time for the ramp. If a very small ramp rate is set for a single large temperature step, this will fail.

[x] look at the maximum step time
[x] look at the absolute maximum ramp time
[x] In case one step is not enough to keep the ramp rate, break it into two steps

Done - maximum sweep time is now 15 * 24 * 60 min = 21 600 min
Slowest rate of 0.01 K/min can be used for a 216 K step at maximum


[10.x] Add Lang::whenMissingTranslation() callback support

As a follow-up to #46999, this PR implements an alternative, less intrusive, system for detecting missing translations. It is similar to the DB::whenQueryingForLongerThan() or the kernel whenCommandLifecycleIsLongerThan() handlers.
Lang::whenMissingTranslation(function (string $key): void {
    report("Missing translation for key [{$key}]");
});

(I have not added the facade docblock, since I assume it is now generated automatically.)
Thanks!

Not sure why some tests are failing on some DBs - cannot see the reason apart from "This job failed".


Wrong description of the Settings / Security / Code security feature

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
Multiple articles.
What part(s) of the article would you like to see updated?
Regarding the issue #35324 I noticed that in the GitHub docs the Settings / Security / Code security feature is refered as "Code security and analysis". This term occurs 32 times over 19 files in the docs. This should be updated to the correct name "Code security".
Additional information
I could provide a PR to fix this issues.

@akordowski Thank you for opening this issue and linking your PR! ✨ Once we've received a response from the team regarding the related issue - https://github.com/github/docs/issues/35324, we'll review this issue and PR as well 💛

@akordowski 👋 Many apologies, but the comment I made here applies here too https://github.com/github/docs/issues/35324#issuecomment-2486234675
I'll discuss this internally as soon as I can, but because of the complications around versioning involved, I'm not sure if we'll be able to accept your PR.
However, I'd be happy to add you as a co-committer on any PRs we do raise. I'll leave this open for now, and we'll get back to you as soon as we can.

@subatoi @nguyenalex836 As the PR is closed I close this issue as well.


Fix scanner_iter() db session out of sync when used by multiple simultaneous queries.

Fixes #1711, by enabling eager loading.
The KE scanner needs a different fix because it uses 2 explicit nested queries.  So, breaking them up into separate sequential queries.

The travis failures are for lints.  Opened issue #1719 to fix separately.


Getting started update

Based on the feedback from yesterdays HOL. Feel free to add more.

The elephant in the room is still: should we include both Bash and PowerShell snippets?

The elephant in the room is still: should we include both Bash and PowerShell snippets?

I'd vote for no. The guide should be as lightweight and straightforward as possible.
We'd some trouble with the Service Principals as well. It might make sense to highlight that as well.

The elephant in the room is still: should we include both Bash and PowerShell snippets?

you mean both? I'm almost for dropping CLI command completely from the guide

The elephant in the room is still: should we include both Bash and PowerShell snippets?

you mean both? I'm almost for dropping CLI command completely from the guide

I used it when going through the guide and it's much more efficient and less error-prone than clicking in the portal. So I'd definitely keep the commands there.

https://github.com/Azure/AlwaysOn-Foundational-Connected/pull/101


Named

Named cells:

Adds cell names with an observablehq--cellname class before inspected values
That's it

There’s a slight discrepancy between how function and class names are shown.

Option 1. If we never want to show function/class names, then it should be g = class and class for the last two cells.
Option 2. If we always want to show function/class names, then it should be f = ƒ F() and ƒ F() for the first two cells.
Option 3. If we only want to show function/class names if the top-level value is a function/class and the name is different than the cell, then it should be f = ƒ F() and ƒ F() for the first two cells, but f = ƒ() and g = class in the more common case where the function/class name matches the cell name.
Option 3 is my preference, followed by Option 1 if we think function names are never useful. I don’t like Option 2 because it’s too noisy in the common case (foo = ƒ foo()).

Yep, so I initially implemented Option 1, looked at g = class and just thought it looked weird - no more real sophistication than that. g = f() just helps me understand 'this is a function' because of the trademark parens.
I think that showing function names that differ from cell names doesn't have value outside of the rare case someone's relying on function.name in their code: most of the time, this information is used to reference the cell, and the internal name doesn't help with that.


mod_auth_openidc Session

Hi,
is mod_auth_openidc send a request to the server each page reloading, to get the token ?
otherwise is mod_auth_openidc a stateless or stateful ?
Thank you

stateful, see: https://github.com/pingidentity/mod_auth_openidc/wiki/Caching


Invalid URL at new NodeError

When having
cache:
  redis:
    url: '{env.REDIS_DSN}'

it simply doesn't work because its interoplated after it's parsed, but cannot be parsed in first place because {env.REDIS_DSN} is not an valid url.
🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] 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)
[ ] This change requires a documentation update

Screenshots/Sandbox (if appropriate/relevant):
Adding links to sandbox or providing screenshots can help us understand more about this PR and take action on it as appropriate
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Test Environment:

OS:
@graphql-mesh/...:
NodeJS:

Checklist:

[ ] I have followed the CONTRIBUTING doc and the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests and linter rules pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

I added the changeset and merging :)


on zoom adapt canvas resolution

Hi,
I'm trying to introduce panzoom and a modal lightbox on spritespin wordpress plugin.
Here a working sample page:
https://easyw.github.io/spritespin-zoom-lightbox/
what I have noticed is that if I use a small spritespin canvas, even when using high res images (1920x1080), the canvas is rendering at the canvas size.
If I apply a panzoom zoom, I would like to apply a new data instance to adapt the resolution to the new zoom (the same issue using the lightbox modal option).
Using full screeen instead, the image get rendered at higher resolution and the zoom result is much nicer.
Would you please suggest a way, if possible, to improve this behavior?
Thanks in advance
Maurice

On zoom the canvas display area is increased via CSS transform. But the Backbuffer of the canvas keeps unchanged. You have to re-render the canvas with a high resolution backbuffer. The way to go is to change the canvasRatio option of spritespin. I did it like this
$("canvas").on("panzoomzoom", function(e, p) {
  $(".spritespin1").spritespin({ canvasRatio: p.scale * window.devicePixelRatio });
})

This seems to work (tested on screens with devicePixelRation of 1 and 2). However this forces spritespin to reboot which means that it puts itself into preloading mode and introduces a short flicker.
I'd have to fix that or allow a caller to tell spritespin to update an option without a reboot but instead with a re-layout only.

This is actually already possible but requires a few more lines of code. The following works without flicker.
$("canvas").on("panzoomzoom", function(e, p) {
  var data = $(".spritespin1").spritespin("data");
  data.canvasRatio = p.scale * window.devicePixelRatio;
  SpriteSpin.applyLayout(data);
  SpriteSpin.updateFrame(data, data.frame);
  data.stage.show();
});

@giniedp
thanks a lot!
This is exactly what I needed.
Great and very powerful jQuery plugin!
:smile_cat:


Correct links to 1.15 release team in blog post

The 1.15 blog post linked to the 1.14 release team. There is no bit.ly link for the 1.15 release, so I updated both references to use the git.k8s.io redirect.

/lgtm

Woops. Didn't catch there was an outstanding PR already XD
Closing this in favor of earlier PR (ref: https://github.com/kubernetes/website/pull/15022)
/close


Fix mel filter bank

Fixes to address issue https://github.com/pytorch/audio/issues/292

One test is failing due to a timeout. I'll go ahead and merge.


Magento: set MAGE_IS_DEVELOPER_MODE env variable

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
Please set MAGE_IS_DEVELOPER_MODE env variable by default, to not have to re-add it everytime.
Describe your solution
Add MAGE_IS_DEVELOPER_MODE  to default config.yml and set it to 1.
Describe alternatives
No response
Additional context
No response

I assume you're talking about openmage/magento 1?
I'm sure you know you can add an environment variable like this to .ddev/.env, or ddev config --web-environment-add=MAGE_IS_DEVELOPER_MODE=1 if it's an environment variable...
For magento 2, we suggest in the quickstart ddev magento deploy:mode:set developer

You know you can set MAGE_IS_DEVELOPER_MODE globally too right?

Yes, its about M1/OM.
I know about these options, but i thought it would be easier to have it added to default config.yml.

@stasadev has added it to the quickstart in

https://github.com/ddev/ddev/pull/6449

But I think you were asking for it to be part of the .ddev/config.yaml when doing a ddev config --project-type=magento, adding
web_environment:
 - MAGE_IS_DEVELOPER_MODE=1

by default. Is that the request?
We've never added a default variable for a project type before, but I imagine it could be done pretty easily.

I think it should be optional, because people may like the CMS settings added by DDEV, but adding env may be too intrusive.


Release v0.0.2-beta.1

What's Changed
New Features 🎉

feat(client): add module anaysis components
feat(platform): report platform add bundle size page
feat(client): add timeline chart & loader analysis page
feat(client): Overall Page‘s compile overall card add details timeline
feat(client): add resolve & loader & plugin pages
feat: migrate rsdoctor packages

Bug Fixes 🐞

fix: lack @rsdoctor/types dependency
fix(graph): duplicate pkg version
fix(components): some components types.

Other Changes

Optimize(client): optimize ui client
Rsdoctor report platform add overall page (close: #25)
refactor(client): migrate build tool to Rsbuild

release v0.0.2-beta.1


Fix for "Types are not assignable to defined types" BUG

Hi,
I wanted to save some time for people who wanted to use this library v 15.2.0 . Issue #23 is genuine and can be faced by anyone.
Documentation mistake:
Everywhere in the examples popperTrigger is mentioned to use like this:
   <popper-content #popper1Content>

Popper on bottom

   </popper-content>

Hey!

Choose where to put your popper!

And we will get following issue with this:

How I solved it:
In TS file:
import {NgxPopperjsTriggers,NgxPopperjsPlacements} from "ngx-popperjs";
trigger= NgxPopperjsTriggers.hover
placement= NgxPopperjsPlacements.AUTO
In Html File:
   <popper-content #popper1Content>

Popper on bottom

   </popper-content>

Hey!

Choose where to put your popper!

Thank you & Cheers!

@jigneshk5 nope man you're totally off.

It's a problem of how you configure Angular...go read the docs.
I created the "popperLoose" directive to deal with all of you guys who really can't deal with writing code the way it should be.

@jigneshk5 also read my reply in #23...maybe you can get the hint and fix your code.


Misconfig?

I am seeing this error from lightning
raise MisconfigurationException(
pytorch_lightning.utilities.exceptions.MisconfigurationException: The provided lr scheduler ExponentialLR doesn't follow PyTorch's LRScheduler API. You should override the LightningModule.lr_scheduler_step hook with your own logic if you are using a custom LR scheduler.

updated to the 2.0.~ of lightning
File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/tensor/code/piper/src/python/piper_train/main.py", line 147, in
main()
File "/home/tensor/code/piper/src/python/piper_train/main.py", line 37, in main
Trainer.add_argparse_args(parser)
AttributeError: type object 'Trainer' has no attribute 'add_argparse_args'
they apparently removed this

tried lower version of pytorch lightning
DEBUG:piper_train:Checkpoints will be saved every 1000 epoch(s)
DEBUG:vits.dataset:Loading dataset: /home/tensor/code/piper/src/python/TrainingData/dataset.jsonl
LOCAL_RANK: 0 - CUDA_VISIBLE_DEVICES: [0]
DEBUG:fsspec.local:open file: /home/tensor/code/piper/src/python/TrainingData/lightning_logs/version_3/hparams.yaml
/home/tensor/code/piper/src/.venv/lib/python3.8/site-packages/pytorch_lightning/utilities/data.py:111: UserWarning: Total length of DataLoader across ranks is zero. Please make sure this was your intention.
rank_zero_warn(
/home/tensor/code/piper/src/.venv/lib/python3.8/site-packages/pytorch_lightning/trainer/connectors/data_connector.py:224: PossibleUserWarning: The dataloader, train_dataloader, does not have many workers which may be a bottleneck. Consider increasing the value of the num_workers argument(try 24 which is the number of cpus on this machine) in theDataLoader` init to improve performance.
rank_zero_warn(
<--- gets stuck here with version 1.8.5

actually it looks like, I jump to tensor board from here and figure out how training is doing

1.7.7 is supported version

some things to point out.
the point you're highlighting where its getting stuck, its not stuck, its doing the training at that point.
because, below is a snippet from my testbed.
notice after the warning about increasing num_workers for the trainer_dataloader, i have an additional warning compared to you about batch_size and log - but after that, its beginning training (i have my checkpoint_epochs=5 to see updates more frequently)
  rank_zero_warn(
/home/turner/PiperTTS/.venv/lib/python3.10/site-packages/pytorch_lightning/trainer/connectors/data_connector.py:224: PossibleUserWarning: The dataloader, train_dataloader, does not have many workers which may be a bottleneck. Consider increasing the value of the `num_workers` argument` (try 16 which is the number of cpus on this machine) in the `DataLoader` init to improve performance.
  rank_zero_warn(
/home/turner/PiperTTS/.venv/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py:1609: PossibleUserWarning: The number of training batches (4) is smaller than the logging interval Trainer(log_every_n_steps=50). Set a lower value for log_every_n_steps if you want to see logs for the training epoch.
  rank_zero_warn(
DEBUG:fsspec.local:open file: /home/turner/train-me/lightning_logs/version_4/checkpoints/epoch=734-step=994302.ckpt
DEBUG:fsspec.local:open file: /home/turner/train-me/lightning_logs/version_4/checkpoints/epoch=739-step=994342.ckpt

for me - my dataset, settings, and hardware, complete 1 x epoch in ~28seconds,
so i see an update in the console every ~2mins30secs after 5 x epochs complete.
your checkpoints occur every 1000 epochs - if its taking 1 min per epoch (depending on your dataset, batch size, precision level, test samples taken, your hardware capability, etc.) you wont see any updates in the console/terminal window for 1000 x minutes (16.6 hours!), and even if you're completing 1 x epoch every second, that's still going to take 16.6 minutes before you see any updates. Theres no point potentially waiting up to 16 hours for an update before determining if you have an issue.
i'd suggest, creating a very small test dataset, like literally 2 or 3 lines in your dataset.jsonl, maybe record some fresh really short wavs maybe 5 words each file so it wont take long to process it.
then change your command to below
(obviously, dont forget to change the path and name of the datasrt_dir, and resume_from_checkpoint arguments to point to your dataset and checkpoint, also amend the --max_epochs to to maybe 5 higher than your current checkpoint, just for this test)
python3 -m piper_train \
--dataset-dir ~/train-me \
--accelerator 'gpu' \
--gpus 1 \
--batch-size 32 \
--validation-split 0.0 \
--num-test-examples 0 \
--max_epochs 105 \
--resume_from_checkpoint "~/train-me/lightning_logs/**VersionFolderWithYourCheckpoint**/checkpoints/epoch=100-step=1000.ckpt" \
--checkpoint-epochs 1 \
--precision 32 \
--max-phoneme-ids 400 \
--quality medium
~~~~~~~~~~~~

then assume its going to take (on the extreme) 2 mins per epoch.
you should then expect to see SOMETHING within 2-6 mins.
either an error, or it progressing.
if you continue to see NOTHING then that would confirm you have some problem elsewhere.

but i just think you had too much data, with settings as such, that you wouldn't see an update in a VERY long time leading you to believe something was up or it had crashed.

if the test works, you know its nothing more than the combination of your dataset, settings, and hardware capability.
you can slowly regress from the test command and setup, back to your original command and setup.
for instance, add your original dataset back in, but keep the --checkpoint_epochs to a lower figure, 1 - 5 maybe?, then youd see an update far sooner and be reassured its ticking along.

after that, you can go back to setting --checkpoint_epochs to 1000 again if you wish.


Removed obsolete sn-webpages links

Removed obsolete sn-webpages links from the "starting out with MVC" doc

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@B3zo0 and @herflis please review this pull request.

Hi @codetronaut thanks for your help. Did you have a chance to try it out? We want to make sure that you can complete the tutorial without the sn-webpages package.

@B3zo0 No I haven't tried it yet.

Hey @codetronaut , as it is stated in the referenced issue, the tutorial has to be reviewed as well, to check that is is working without the sn-webpages installation.


:bug:Fuzzing: remove tmp directories with the OSS-Fuzz repository

Closes https://github.com/ossf/scorecard/issues/1264

https://github.com/ossf/scorecard/pull/1265#issuecomment-968539477


Proxy Support

Hello,
Would it be possible to allow http_proxy as input so that this action can run on self-hosted runners running inside a secure environment

Hello @gauravngandhi ,
Thank you for your feedback. We have noted this as a feature request.

Hi @rstevens011,
Thank you for the reply. Do you have any timeline on when we can expect this feature? Currently, the proxy setting is provided as part of the configure-AWS-credentials GitHub action. It would be great if we could have this feature with this action as well.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.15.6 to before v5.15.6",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=09eb40f6776c8b50c2e46a504bf5483440ca607d",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1c939a53b26b6b39378a77f76a49be8dd6df7af0"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "09eb40f6776c8b50c2e46a504bf5483440ca607d",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "1c939a53b26b6b39378a77f76a49be8dd6df7af0",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "io_uring: fix link traversal locking\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.6 by commit 1c939a53b26b6b39378a77f76a49be8dd6df7af0, it was introduced in version v5.15.6 by commit 09eb40f6776c8b50c2e46a504bf5483440ca607d. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002526


IPAM Prefix Sort Not Available

Environment

Nautobot version (Docker tag too if applicable): 2.0
Python version: 3.11
Database platform, version: psql
Middleware(s): N/A

Steps to Reproduce

Go to https://demo.nautobot.com/ipam/prefixes/
Click on headers

Expected Behavior
To sort based on the column header you created

Observed Behavior
No sorting

Seems like we just need to remove this https://github.com/nautobot/nautobot/blob/70012f7f8db4513e673c2061e07075a36b8f6580/nautobot/ipam/tables.py#L376, but not sure why it was there to begin with?

Given that prefixes are hierarchical, I'm not sure sorting makes a lot of sense (similar to #1854). Can you give an example of the type of sorting you'd expect to be able to do here?

IIRC in #1854 we chose at the time to disable sorting on tree models primarily due to the odd visual representation of nested data and because we did not have the cycles in 2.0 to properly solve that.
Let's use this issue to build a good story around the presentation and interaction with the Prefix hierarchy alone. I'm sure some of it will meaningfully carry over to other tree models like location, but there will be different use cases.
To start, I can see two primary views into the prefix data.

A collapsable, navigable tree. Filtering and sorting here, would only effect top level nodes in the tree.
A flat view that ignores the tree relationships in which all traditional filtering and sorting works.

As a user I would want a simple toggle between these two options in the list view.
I'm certain we can get more advanced from there.
In the first case, I care primary about drilling down into the data. In the second case, I care more about filtering and sorting, such as filtering by a location and then sorting by the role.

For now, we will allow the sorting and when a user actually does sort, we will dynamically remove the hierarchy indentation.

We had a request today regarding sorting in Locations, and I'm assuming it's missing due to the same reason. @lampwins do you want me to create a parallel issue?

I don't think so. We would support sorting any column that it should be, in this model.

Reopening this issue, needs to be implemented on the Prefix list view, and needs to be implemented when filtering a tree list view as well as sorting

#5452 added sortability to the Prefix table. Remaining work now is to remove the indentation of entries whenever a filter is applied to any tree table.


old_configuration_format rule not working for PRs

# elvis.config [FAIL]
Error: '{badmatch,{error,enoent}}' while applying rule 'old_configuration_format'.

The problem is the rule is always using file:consult/1 instead of first verifying if the Target already has its content. In that case use ktn_code:consult/1.


Fix misspelled helm init parameter "--history-max"

What this PR does / why we need it:
In the quickstart guide, --max-history is recommended as parameter for helm init. The actual name of the parameter is --history-max.
Special notes for your reviewer:
If applicable:

[X] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

I failed to do the signoff, I'll retry.


[BUG] Can't load namespace creation page content and create namespace on Harvester from Rancher v2.8.5

Describe the bug

When we try to create a namespace from the Rancher virtualization management.

Can't load the namespace creation page content well

When given the name and click create, it would prompt failure message
Failed to parse body: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal string into Go value of type map[string]interface {}

https://github.com/user-attachments/assets/8d4540bd-dd63-4c73-82f1-59bb47eff6b7

To Reproduce

Import Harvester to Rancher

Access Harvester from Rancher virtualization management

Go to Projects/Namespaces and create a new project test-project

In the Resource Quotas tab, add Storage Reservation and use 20000 MiB as project limit and 12000 MiB as namespace default limit

Create a new namespace named quota-test in the previously created project.

Expected behavior

Can load namespace creation page well on Harvester from Rancher virtualization management.
Support bundle

supportbundle_c2f1e2b2-34c5-4cbb-87e2-560ff5dd2a88_2024-11-05T11-19-29Z.zip
Environment

Harvester ISO version: v1.4-eaf3009a-head (24/11/05)
Underlying Infrastructure: Three nodes kvm machines

Additional context
This issue did not happen on Rancher v2.9.2

This issue also exists on Rancher v2.8.9 with Harvester v1.4-eaf3009a-head

Due to https://github.com/harvester/dashboard/pull/1208 merged in rc5 caused below error. Test with v1.4.0-rc4  + Rancher-2.8.5 is good. cc @torchiaf
Error: Cannot find resourceFields for Schema namespace (schemaDefinitions have not been fetched)

Rancher v2.8 -> Rancher v2.9 has lots of change (even broken change), like steve-schema.ts is introduced in v2.9. So it's somehow may break something on v2.8.x.
See @torchiaf has any solution.

yes, QA validates the release with Rancher 2.8.9.

Verified fixed on v1.4-eaf3009a-head (24/11/08). Close this issue.
Test result of Rancher v2.8.9
$\color{green}{\textsf{PASS}}$ Can load namespace creation page content and create namespace well $~~$

Test result of Rancher v2.9.3
$\color{green}{\textsf{PASS}}$ Can load namespace creation page content and create namespace well $~~$

Test Information

Test Environment: Single node kvm machine
Harvester version: v1.4-eaf3009a-head (24/11/08)
Rancher: v2.8.9, v2.9.3

Verify Steps
 Create namespace in Rancher

Import Harvester to Rancher
Access Harvester from Rancher virtualization management
Go to Projects/Namespaces and create a new project test-project
In the Resource Quotas tab, add Storage Reservation and use 20000 MiB as project limit and 12000 MiB as namespace default limit
Create a new namespace named quota-test in the previously created project.


@threlte/rapier and @threlte/studio refactoring

This PR is a refactoring of the packages @threlte/rapier and @threlte/studio.
@threlte/rapier

Removed transform props from Collider, AutoColliders and RigidBody because they are and won't be in-line with the syntax used on <T>.
<Collider> components are now not reactive to parent transforms by default. Add type="dynamic" to make them reactive.
A binding refresh was added on <Collider> and <AutoColliders> to refresh the transform and – in regards to <AutoColliders> recreate the colliders from the underlying geometry.
Updated dependencies

@threlte/theatre

<Editable>

Added events on:create and on:change to listen to prop values
Added prop detach to detach a SheetObject onDestroy
Added keyboard shortcut  "g" to change transform space from world to local

<Studio> now has an inner slot that only mounts when the Studio is mounted:

<Studio>
  <!-- Threatre.js Studio is loaded -→
</Studio>

Adde hook useStudio
Updated dependencies

Documentation is missing for some of these things … Part of another PR.


[Question] off-chain order book details?

Hi Seaport devs,
My understand that the "order book" will be maintained by OpenSea in some form and will be "off-chain" - are there any plans to work on a open decentralised off-chain order book of sorts?  I understand that there is also an on-chain engine as well but I suspect the vast majority will use the off-chain matching engine for UX/GAS savings
Please correct me if I am wrong on this front and it works differently?
Thanks

Hey @jamesmorgan, yes we are working on exactly this - a decentralized p2p orderbook for Seaport orders that anyone can spin up a node and listen to orders for interested contracts, or all activity. Hope to have something to show soon, keep an eye out and I will try to remember to ping you when we have a public pre/beta release.

Hey @jamesmorgan, yes we are working on exactly this - a decentralized p2p orderbook for Seaport orders that anyone can spin up a node and listen to orders for interested contracts, or all activity. Hope to have something to show soon, keep an eye out and I will try to remember to ping you when we have a public pre/beta release.

Thats really great to hear! - looking forward to seeing this in action and building on it


WeakOuter annotation for fields

Is there any particular reason why the WeakOuter annotation cannot be placed on fields?
AFAICT, code like this creates a reference cycle that would be fixed by that annotation:
class OkCache {
  final OkInternalCache internalCache = new OkInternalCache() {
    @Override public OkResponse get(OkRequest request) throws IOException {
      return OkCache.this.get(request);
    }
  }
  .
  .
  .
}

The ideal syntax would be:
final OkInternalCache internalCache = new @WeakOuter OkInternalCache() {...}
But it is not currently supported by J2ObjC. Quote from this post:
https://j2objc.blogspot.com/2017/01/breaking-retain-cycles-with-weak-and.html

Promote anonymous classes to inner classes. Since Java 8, it is possible to create anonymous instances with type annotations. For example: Runnable r = new @Foo Runnable() { … }; For the time being, though, J2ObjC’s @WeakOuter still needs to be backward compatible with Java 7. This means you have to promote your anonymous classes to inner classes, so you can add @WeakOuter to them.

After a bit a research and testing, I found out that there are libraries that are using WeakOuter and that need to be Java 7 compatible. Adding TYPE_USE to WeakOuter will break these libraries. Please follow the recommendation in the previous comment.

I see. Thanks for the explanation!


Example run changes directory to repository root

The example depends on being run in the root directory of the repo.
This minimal change simply does a cd into the root directory of the repo. A longer-term conversation: how do paths work relative to scripts, config files, etc., etc.? Best not to change anything significant until the reproducibility model stabilizes.
Also modified path computations to use os.path.join().

I'll take a look at this on Monday.

I think it probably makes sense to punt this kind of thing until after the packages get reorg'd and relative paths get re-thought.
At that point we can identify the best non-hacky solution—I suspect there's a "correct" way to do this that doesn't involve messing with the python search path at runtime.


added chpk domain

Official website URL: "http://chpk.rchuv.ru/"

@VeraJVV I am sorry, rchuv.ru domain that you submit does not belong to a particular school. It seems to belong to an umbrella institution (such as a government body). Please apply for free educational license with an official document that proves your student status. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students. Thank you for your understanding!
I have to close this request without merging.


1.2.2 patch release to fix Conda environment

nf-core/chipseq pull request
Many thanks for contributing to nf-core/chipseq!
Please fill in the appropriate checklist below (delete whatever is not relevant).
These are the most common things requested on pull requests (PRs).
PR checklist

[ ] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/chipseq branch on the nf-core/test-datasets repo
[ ] Ensure the test suite passes (nextflow run . -profile test,docker).
[ ] Make sure your code lints (nf-core lint .).
[ ] Documentation in docs is updated
[ ] CHANGELOG.md is updated
[ ] README.md is updated

Learn more about contributing: CONTRIBUTING.md

Done https://github.com/nf-core/chipseq/pull/209/commits/801bc537dbe006d881df60b4b50a4e1c91352c90

Manual docker builds pushed and available: https://hub.docker.com/repository/docker/nfcore/chipseq/tags?page=1&ordering=last_updated


Build failure: gss

Steps To Reproduce
Steps to reproduce the behavior:
Trying to nixos-rebuild with ~current nixpkgs master.
I've tried this twice now thinking maybe it was just a failed malloc but no such luck.
Build log
make[3]: Entering directory '/build/gss-1.0.4/tests'
  CC       basic.o
  CCLD     basic
  CC       saslname.o
  CCLD     saslname
  CC       krb5context.o
  CCLD     krb5context
make[3]: Nothing to be done for 'threadsafety.sh'.
make[3]: Leaving directory '/build/gss-1.0.4/tests'
make  check-TESTS
make[3]: Entering directory '/build/gss-1.0.4/tests'
make[4]: Entering directory '/build/gss-1.0.4/tests'
PASS: threadsafety.sh
PASS: basic
PASS: saslname
../build-aux/test-driver: line 112:  5536 Aborted                 (core dumped) "$@" >> "$log_file" 2>&1
FAIL: krb5context
==============================================================
   GNU Generic Security Service 1.0.4: tests/test-suite.log
==============================================================

# TOTAL: 4
# PASS:  3
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: krb5context
=================

loop 0 init failure
gss_accept_sec_context failure
loop 0 accept flag failure (18592)
gss_accept_sec_context failure
gss_init_sec_context failure (2)
client gss_wrap failure
server gss_unwrap failure
wrap+unwrap failed (4, 4334080, <85><C0>u<DC>B<80><3=u<D5>J<8D>\3^AH<89><D8>[]A\A]A^1<D2>1<F6>1<FF><C3>ff.^O^_<84>)
free(): invalid size
FAIL krb5context (exit status: 134)

============================================================================
Testsuite summary for GNU Generic Security Service 1.0.4
============================================================================
# TOTAL: 4
# PASS:  3
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0
============================================================================
See tests/test-suite.log
Please report to<EMAIL_ADDRESS>============================================================================
make[4]: *** [Makefile:1838: test-suite.log] Error 1
make[4]: Leaving directory '/build/gss-1.0.4/tests'
make[3]: *** [Makefile:1946: check-TESTS] Error 2
make[3]: Leaving directory '/build/gss-1.0.4/tests'
make[2]: *** [Makefile:2033: check-am] Error 2
make[2]: Leaving directory '/build/gss-1.0.4/tests'
make[1]: *** [Makefile:1556: check-recursive] Error 1
make[1]: Leaving directory '/build/gss-1.0.4'
make: *** [Makefile:1856: check] Error 2

Additional context
using content-addressed derivations and
  28   │   nixpkgs.hostPlatform = {
  29   │     gcc.arch = "znver3";
  30   │     gcc.tune = "znver3";
  31   │     system = "x86_64-linux";
  32   │   };

Notify maintainers
@stuebinm @wegank @toonn

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 wrath@JustinMohnsIPod  /e/nixos   master ⁝ ✚ 
 ❯ nix-shell -p nix-info --run "nix-info -m"                                                                                [17:50:50]
this path will be fetched (0.00 MiB download, 0.00 MiB unpacked):
  /nix/store/kjhgwsnn7wkacncxhrcgc4mx0v82kbdf-nix-info
copying path '/nix/store/kjhgwsnn7wkacncxhrcgc4mx0v82kbdf-nix-info' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 6.9.4-xanmod1, NixOS, 24.11 (Vicuna), 24.11.20240621.e739fee`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.20.3`
 - channels(root): `""`
 - nixpkgs: `/nix/store/k2rkryiqwhqc38rq5yxgnabv9b2m09dj-source`

Add a :+1: reaction to issues you find important.

Some change in stdenv must be causing this since it built fine a month ago and hardly anything else changed. I guess the build-host kernel is different too, if this is some libc jank..

https://github.com/NixOS/nixpkgs/pull/317260 this looks a bit suspicious but it's just a guess. The testing infrastructure doesn't check if things like this don't subtly break compilation for anyone using non-standard gcc.{arch,tune} @alyssais

wait could this just be expired test data or something
https://git.savannah.gnu.org/cgit/gss.git/tree/tests/krb5context.c
I've tried rebuilding this with clang and this build doesn't exhibit the memory corruption but it does immediately fail the same test
make[3]: Entering directory '/build/gss-1.0.4/tests'
make[4]: Entering directory '/build/gss-1.0.4/tests'
PASS: threadsafety.sh
PASS: basic
PASS: saslname
../build-aux/test-driver: line 112:  6711 Segmentation fault      (core dumped) "$@" >> "$log_file" 2>&1
FAIL: krb5context
==============================================================
   GNU Generic Security Service 1.0.4: tests/test-suite.log
==============================================================

# TOTAL: 4
# PASS:  3
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: krb5context
=================

loop 0 init failure
gss_accept_sec_context failure
loop 0 accept flag failure<PHONE_NUMBER>)
gss_accept_sec_context failure
gss_init_sec_context failure (2)
client gss_wrap failure
server gss_unwrap failure
FAIL krb5context (exit status: 139)

I have now let down my hair, put on my freest pair of sneakers and started galloping in The Savannah https://git.savannah.gnu.org/cgit/gss.git/tree/tests/krb5context.c and it sure looks like any memory corruption was due to it immediately imploding when it tries to create a context and then doing some inappropriate cleanup

name:authtime  type:GENERALIZED_TIME  value:20040711155558Z
name:endtime  type:GENERALIZED_TIME  value:20240711155558Z
JFC
this is the test data in https://git.savannah.gnu.org/cgit/gss.git/tree/tests/krb5context.tkt#n48
guess July 2024 wasn't "forever" enough

oh wow @alyssais already reported this, thank you https://lists.gnu.org/archive/html/help-gss/2024-07/msg00000.html

looks like https://github.com/NixOS/nixpkgs/pull/327128 fixes this


scion.sh run fails when run within Docker container

Hi,
I have followed the instructions for the Docker build, and the last step $ ./scion.sh run fails.
Setup & Steps:

Ubuntu 16.04 fresh install in a Virtual Box VM.
Followed the step-by-step instructions from Docker build.
The last 2 steps:
 $ ./docker.sh run WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
scion@scion:~/go/src/github.com/scionproto/scion$ ./scion.sh run Compiling... make[1]: *** No rule to make target 'install'.  Stop. Makefile:30: recipe for target 'liblwip' failed make: *** [liblwip] Error 2

@ognjenvukovic : i believe the problem is that you have not checked out the git submodules. Try running these commands on your host machine, and then rebuilding the docker image:
git submodule init
git submodule update

@kormat : thank you Stephen, that solved the issue.


'await' outside of an async method yields crappy error message

This
import 'dart:async';

void main() {
  await new Future.value(1);
}

yields this error message
error: line 4 pos 8: semicolon expected
  await new Future.value(1);
       ^

That's misleading.  It should say something more like
error: line 4 pos 8: await can only be used inside an async function
  await new Future.value(1);
       ^

dup of #24533

Thanks for the report.


Port already in use error when running a container

I started seeing this behavior after upgrading from 0.6.6 to 0.7.1
Steps to reproduce:

Run a container with -p
Stop container
Remove container
Repeat step 1

Step 4 will fail with "Port already in use" error corresponding to whatever was used with -p
Here's some screen-scrape love:
relevs09:~/build >>> sudo docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
relevs09:~/build >>> sudo netstat -lntp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      1905/sshd
tcp6       0      0 :::22                   :::*                    LISTEN      1905/sshd
relevs09:~/build >>> sudo docker run -d -name dns_master -h foosrv0 -dns <IP_ADDRESS> -p 53:53/udp stackmachine.com/windowsrefund/foo:dns_master
580fb786794f21c32160ae2b66dd087fbaf8db0ad9e4f8888ec957fd99c9be39
relevs09:~/build >>> sudo docker stop dns_master
dns_master
relevs09:~/build >>> sudo docker rm dns_master
dns_master
relevs09:~/build >>> sudo docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
relevs09:~/build >>> sudo docker run -d -name dns_master -h foosrv0 -dns <IP_ADDRESS> -p 53:53/udp stackmachine.com/windowsrefund/foo:dns_master
ba9864d582689637dd87aeace7478b8c7200d209102b8cb6d54702059eeddc5a
2013/12/16 00:41:13 Error: start: Cannot start container ba9864d582689637dd87aeace7478b8c7200d209102b8cb6d54702059eeddc5a: Port already in use: 53
relevs09:~/build >>> sudo netstat -lntp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      1905/sshd
tcp6       0      0 :::22                   :::*                    LISTEN      1905/sshd
relevs09:~/build >>>

Having this issue 2 years later.  Any luck figuring it out?

@acebailey did you check if no stopped containers are present (docker ps -a) or another (non-containerized) service on the host? Just to name some easy to overlook causes.

I just go this same error using 1.12 her is my output
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
wrk1-tpr@wrk1-tpr:~$ docker ps -a
CONTAINER ID        IMAGE                                    COMMAND             CREATED             STATUS                        PORTS               NAMES
2ce6ec595541        btreepress/voting-app-demo:latest        "python app.py"     33 minutes ago      Exited (137) 24 minutes ago                       vote.7.bzm4oaa5zpp9nlstr7o3il2ad
92a085ae5702        btreepress/voting-app-demo:latest        "python app.py"     43 minutes ago      Exited (137) 40 minutes ago                       thepetrepublic.7.adg4t05y8mlsdchb99wlvz369
ec3437740e95        btreepress/node-web-express-app:latest   "npm start"         About an hour ago   Exited (137) 45 minutes ago                       thepetrepublic.2.evdxh5vyj5oba3wh6jwu0e68g
wrk1-tpr@wrk1-tpr:~$ docker run -d -p 80:80 btreepress/boting-app-demo
Unable to find image 'btreepress/boting-app-demo:latest' locally
Pulling repository docker.io/btreepress/boting-app-demo
docker: Error: image btreepress/boting-app-demo:latest not found.
See 'docker run --help'.
wrk1-tpr@wrk1-tpr:~$ ^C
wrk1-tpr@wrk1-tpr:~$ clear
wrk1-tpr@wrk1-tpr:~$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
wrk1-tpr@wrk1-tpr:~$ docker ps -a
CONTAINER ID        IMAGE                                    COMMAND             CREATED             STATUS                        PORTS               NAMES
2ce6ec595541        btreepress/voting-app-demo:latest        "python app.py"     34 minutes ago      Exited (137) 25 minutes ago                       vote.7.bzm4oaa5zpp9nlstr7o3il2ad
92a085ae5702        btreepress/voting-app-demo:latest        "python app.py"     44 minutes ago      Exited (137) 41 minutes ago                       thepetrepublic.7.adg4t05y8mlsdchb99wlvz369
ec3437740e95        btreepress/node-web-express-app:latest   "npm start"         About an hour ago   Exited (137) 46 minutes ago                       thepetrepublic.2.evdxh5vyj5oba3wh6jwu0e68g
wrk1-tpr@wrk1-tpr:~$ docker run -d -p 80:80 --name vote  btreepress/voting-app-demo:latest
8ee0929660def578a34fdc62015f860d6a68ff4e275a352dc82024335b401c75
docker: Error response from daemon: driver failed programming external connectivity on endpoint vote (3ec836d6faa2f7827eb4695b5e3f7b257307cbed21d3153a8c85d34a6d168b44): Error starting userland proxy: listen tcp <IP_ADDRESS>:80: bind: address already in use.
wrk1-tpr@wrk1-tpr:~$ docker rm $(docker ps -a -q)
8ee0929660de
2ce6ec595541
92a085ae5702
ec3437740e95
wrk1-tpr@wrk1-tpr:~$ docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
wrk1-tpr@wrk1-tpr:~$ docker run -d -p 80:80 --name vote  btreepress/voting-app-demo:latest
6bc7f750e7ef0f43f5bd884094d04937e728701baf56d1399fe68652ac7b7e01
docker: Error response from daemon: driver failed programming external connectivity on endpoint vote (a892114570d257ee2b555c5fb789cde892eb182127353ac7817ddf03820ea709): Error starting userland proxy: listen tcp <IP_ADDRESS>:80: bind: address already in use.
wrk1-tpr@wrk1-tpr:~$ docker info
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 3
Server Version: 1.12.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 33
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: overlay bridge null host
Swarm: active
NodeID: 97pslexccnzpff4u83mi6ijid
Is Manager: false
Node Address: <IP_ADDRESS>
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-28-generic
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.636 GiB
Name: wrk1-tpr
ID: 2EXQ:RDZR:TSVG:U2C6:NL7R:5KFY:7MX2:QAHQ:WB26:6FME:WUGP:NEVE
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
<IP_ADDRESS>/8
wrk1-tpr@wrk1-tpr:~$

wrk1-tpr@wrk1-tpr:~$ netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0    432 <IP_ADDRESS>:ssh            cpe-23-242-198-55:14251 ESTABLISHED
tcp        0      0 <IP_ADDRESS>:58088          blob.by4prdstr02a:https TIME_WAIT
tcp        0      0 <IP_ADDRESS>:58090          blob.by4prdstr02a:https TIME_WAIT
tcp        0      0 <IP_ADDRESS>:48010          <IP_ADDRESS>:http      TIME_WAIT
tcp        0      0 <IP_ADDRESS>:57514          <IP_ADDRESS>:7946           TIME_WAIT
tcp        0      0 <IP_ADDRESS>:58098          blob.by4prdstr02a:https TIME_WAIT
tcp        0      0 <IP_ADDRESS>:43958          <IP_ADDRESS>:7946           TIME_WAIT
tcp        0      0 <IP_ADDRESS>:54954          <IP_ADDRESS>:2377           ESTABLISHED
tcp        0      0 <IP_ADDRESS>:58100          blob.by4prdstr02a:https TIME_WAIT
tcp        0      0 <IP_ADDRESS>:43948          <IP_ADDRESS>:7946           TIME_WAIT
tcp        0      0 <IP_ADDRESS>:48020          <IP_ADDRESS>:http      TIME_WAIT
tcp6       0      0 <IP_ADDRESS>:7946           <IP_ADDRESS>:51684          TIME_WAIT
tcp6       0      0 <IP_ADDRESS>:7946           <IP_ADDRESS>:57472          TIME_WAIT
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags       Type       State         I-Node   Path
unix  2      [ ]         DGRAM                    400191   /run/user/1000/systemd/notify
unix  3      [ ]         DGRAM                    10581    /run/systemd/notify
unix  12     [ ]         DGRAM                    10588    /run/systemd/journal/dev-log
unix  2      [ ]         DGRAM                    10600    /run/systemd/journal/syslog
unix  8      [ ]         DGRAM                    10602    /run/systemd/journal/socket
unix  3      [ ]         DGRAM                    96156
unix  2      [ ]         DGRAM                    400176
unix  3      [ ]         STREAM     CONNECTED     13865
unix  3      [ ]         DGRAM                    96159
unix  2      [ ]         DGRAM                    14430
unix  3      [ ]         STREAM     CONNECTED     13972
unix  2      [ ]         DGRAM                    11072
unix  2      [ ]         DGRAM                    96149
unix  2      [ ]         DGRAM                    17868
unix  3      [ ]         STREAM     CONNECTED     15820    /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     400315
unix  3      [ ]         STREAM     CONNECTED     244856   /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     13144
unix  3      [ ]         STREAM     CONNECTED     12969    /run/systemd/journal/stdout
unix  3      [ ]         DGRAM                    96157
unix  2      [ ]         DGRAM                    14267
unix  2      [ ]         DGRAM                    245106
unix  2      [ ]         DGRAM                    244183
unix  2      [ ]         DGRAM                    400055
unix  3      [ ]         STREAM     CONNECTED     14344    /var/run/dbus/system_bus_socket
unix  3      [ ]         STREAM     CONNECTED     13035
unix  3      [ ]         STREAM     CONNECTED     12968
unix  3      [ ]         STREAM     CONNECTED     244855
unix  2      [ ]         DGRAM                    15518
unix  3      [ ]         STREAM     CONNECTED     14274
unix  3      [ ]         STREAM     CONNECTED     13036    /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     245421
unix  2      [ ]         DGRAM                    13897
unix  3      [ ]         DGRAM                    96158
unix  3      [ ]         STREAM     CONNECTED     96039
unix  2      [ ]         DGRAM                    16866
unix  3      [ ]         STREAM     CONNECTED     244172
unix  2      [ ]         DGRAM                    28522
unix  3      [ ]         STREAM     CONNECTED     11307
unix  2      [ ]         DGRAM                    13135
unix  3      [ ]         STREAM     CONNECTED     400140   /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     400138
unix  2      [ ]         DGRAM                    245439
unix  3      [ ]         STREAM     CONNECTED     28538
unix  3      [ ]         STREAM     CONNECTED     14432
unix  2      [ ]         DGRAM                    245313
unix  3      [ ]         STREAM     CONNECTED     13145
unix  3      [ ]         STREAM     CONNECTED     13709
unix  3      [ ]         STREAM     CONNECTED     14343
unix  3      [ ]         STREAM     CONNECTED     28539    /var/run/docker/libcontainerd/docker-containerd.sock
unix  3      [ ]         STREAM     CONNECTED     14275    /var/run/dbus/system_bus_socket
unix  3      [ ]         STREAM     CONNECTED     13417    /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     245305
unix  2      [ ]         STREAM     CONNECTED     423811   /var/run/nscd/socket
unix  3      [ ]         DGRAM                    244231
unix  3      [ ]         STREAM     CONNECTED     245424   /run/systemd/journal/stdout
unix  2      [ ]         DGRAM                    400165
unix  3      [ ]         STREAM     CONNECTED     13103    /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     13102
unix  3      [ ]         STREAM     CONNECTED     13866    /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     14433    /var/run/dbus/system_bus_socket
unix  3      [ ]         STREAM     CONNECTED     13973    /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     244173   /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     96040    /var/run/dbus/system_bus_socket
unix  3      [ ]         STREAM     CONNECTED     28502
unix  3      [ ]         STREAM     CONNECTED     400314
unix  3      [ ]         STREAM     CONNECTED     28515    /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     13710    /run/systemd/journal/stdout
unix  3      [ ]         DGRAM                    244232
unix  3      [ ]         STREAM     CONNECTED     11308    /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     96136
unix  3      [ ]         STREAM     CONNECTED     96137    /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     13416
unix  3      [ ]         STREAM     CONNECTED     245306   /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     15811

@drlukeangel your issue cannot be the same as the issue reported here originally; this issue is almost three years old, and the networking stack in docker has been completely replaced. It's possible you get a similar error, but the cause cannot be the same.
The original issue reported here was resolved in docker 0.7.2 if anyone still sees this issue, please open a new issue, or search for an existing issue that's still opened and reported with the version you're using.
I'm locking this issue to prevent it from collecting unrelated reports.


useJsonForm with InlineBlocks not working as expected.

Description
When using useJsonForm in conjunction with InlineForm and InlineBlocks in a Gatsby project there seems to be something wrong. According to the Tina docs InlineBlocks takes a name prop with the object key of where the blocks are. This results for me in an empty page, perfectly editable, but nothing happens when pressing Save (it succeeds but nothing happened).
However it works when passing rawJson.blocks to the name prop.
I was wondering if this was intended or the docs are correct 😄
Steps to reproduce
function BlogPostTemplate({ data }) {
  const [, form] = useJsonForm(data.dataJson)
  usePlugin(form)

  return (
    <div className={`home theme-light primary-teal`}>
      <InlineForm form={form}>
        <InlineBlocks name="blocks" blocks={BLOCKS} />
      </InlineForm>
    </div>
  )
}

Here's a demo: https://github.com/RobertBroersma/statikly
Check out the templates/blog-post.js!
Expected result
<InlineBlocks name="blocks" blocks={BLOCKS} /> works.
Actual result
<InlineBlocks name="rawJson.blocks" blocks={BLOCKS} /> works.
Environment
Windows 10 with WSL.
Tinacms Package Versions
─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>Tools

Tool
Version

Chrome
83.0

Windows + WSL
10

node
14

yarn
1.22.4

EDIT: Looking at the examples it seems to be correct. You can close this!

Hi @RobertBroersma, thanks for posting! This is expected behavior. The name should be the path to the blocks data. So blocks is just an example if it was in the root of the data, since Gatsby paths work a bit differently, that rawJson.blocks is what you need. Let us know if you have any other questions!


On row click

Is there is any way to subscribe on row click event?
If it's not I can try to contribute it.

Options to achieve this:

Place onClick handlers on your rendered elements in each cell (cumbersome, but works right now)
Override the trComponent to use a custom one that implements onClick functionality
Submit a PR that does the following:

Add an onTrClick event after (this)[https://github.com/tannerlinsley/react-table/blob/master/src/index.js#L25] with a good default noop.  Probably something like:

onTrClick: () => null

Add an onClick handler here that will fire the onTrClick prop with all of the appropriate information about the row.  eg:

onClick={(event) => this.props.onTrClick(rowInfo, event)}

I would also be okay with the prop being called onRowClick if that feels or sounds better.
Thoughts? :)

Sounds good!) I'll send PR.

https://github.com/tannerlinsley/react-table/pull/23


Potential memory leak? (Potentially related to Generator type)

Reporting a bug

[x] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
[x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

Dear numba Team.
I am not sure whether I found an actual error or whether the error is on my side.
Therefore, I am sorry to disturb your work and take your time.
If I execute the code below, then the python process will slowly consume more and more memory until it eventually crashes.
Notice the program has an endless loop, but it does not explicitly allocate any new object.
Expectation: Program runs forever but does not consume excessive memory.
Observation: The memory consumption is ever-increasing (found with the top program).
Note: If I remove the @numba.njit, the memory consumption remains normal.

from typing import Final

import numba  # type: ignore
import numpy as np
from numpy.random import Generator

@numba.njit
def swap_2_or_flip(random: Generator, dest: np.ndarray,
                   x: np.ndarray) -> None:
    """
    Copy `x` into `dest` and swap two different values or flip a sign.

    :param random: the random number generator
    :param dest: the array to receive the modified copy of `x`
    :param x: the existing point in the search space
    """
    dest[:] = x[:]  # First, we copy `x` to `dest`.
    length: Final[int] = len(dest)  # Get the length of `dest`.

    i1: Final[int] = random.integers(0, length)  # first random index.
    v1: Final = dest[i1]  # Get the value at the first index.

    if random.integers(0, 2) == 0:  # With p=0.5, we flip the sign of v1.
        dest[i1] = -v1  # Flip the sign of v1 and store it back at i1.
        return  # Quit.

# Swap two values. Now, normally we would repeat the loop until we find a
# different value. However, if we have signed permutations, it may be
# possible that all values currently are the same. To avoid an endless loop,
# we therefore use a sufficiently large range.
    for _ in range(10 + length):
        i2: int = random.integers(0, length)  # Get the second random index.
        v2 = dest[i2]  # Get the value at the second index.
        if v1 != v2:  # If both values different...
            dest[i2] = v1  # store v1 where v2 was
            dest[i1] = v2  # store v2 where v1 was
            return  # Exit function: we are finished.
    # If we get here, probably all elements are the same, so we just...
    dest[i1] = -v1  # ...flip the sign of v1 and store it back at i1.

rand = np.random.default_rng(10)
xx = np.array(range(10), int)
out = np.empty(len(xx), int)

while True:
    swap_2_or_flip(rand, out, xx)

Interestingly, the same issue (increased memory consumption) still happens if I just do
import numba  # type: ignore
import numpy as np
from numpy.random import Generator

@numba.njit
def swap_2_or_flip(random: Generator, dest: np.ndarray,
                   x: np.ndarray) -> None:
    i = len(dest)

rand = np.random.default_rng(10)
xx = np.array(range(10), int)
out = np.empty(len(xx), int)

while True:
    swap_2_or_flip(rand, out, xx)

It stops happening if I do:
import numba  # type: ignore
import numpy as np
from numpy.random import Generator

@numba.njit
def swap_2_or_flip(dest: np.ndarray,
                   x: np.ndarray) -> None:
    i = len(dest)

rand = np.random.default_rng(10)
xx = np.array(range(10), int)
out = np.empty(len(xx), int)

while True:
    swap_2_or_flip(out, xx)

Therefore, I think, the problem might be related to the Generator type?
Here you can find the versions of libraries potentially related to the issue:
numpy 1.24.4
numba 0.57.1
intel-cmplr-lib-rt 2023.2.0
matplotlib 3.7.2
psutil 5.9.5
scikit-learn 1.3.0
scipy 1.11.1

My Ubuntu Linux system information is as follows:
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.2 LTS
Release:	22.04
Codename:	jammy

os.name: Linux
os.release: 5.19.0-50-generic
os.version: 50-Ubuntu SMP PREEMPT_DYNAMIC Mon Jul 10 18:24:29 UTC 2023

My python version is as follows:
Python 3.10.6
python.version: 3.10.6 (main, May 29 2023, 11:10:38) [GCC 11.3.0]
python.implementation: CPython

Other software versions are:
gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Again, I am not sure whether any of this is relevant or whether the mistake is on my side.
All the best,
Thomas.
bug.zip

Hi @thomasWeise, thanks for the report. I can confirm the bug.
Reproducer:
import numba  # type: ignore
import numpy as np
from numpy.random import Generator

@numba.njit
def swap_2_or_flip(random: Generator):
    return

rand = np.random.default_rng(10)

while True:
    swap_2_or_flip(rand)

Upon inspecting NRT stats, all allocations using the Numba runtime are freed:
import numba  # type: ignore
import numpy as np
from numpy.random import Generator
from numba.core.runtime import rtsys, _nrt_python

_nrt_python.memsys_enable_stats()

@numba.njit(no_cfunc_wrapper=True)
def foo(random: Generator):
    return

rand = np.random.default_rng(10)

for i in range(1000):
    foo(rand)
new_stats = rtsys.get_allocation_stats()
print(new_stats)
# nrt_mstats(alloc=1000, free=1000, mi_alloc=1000, mi_free=1000)

Wonder if the memory leak happens at the CPython wrapper.

Thank you, @guilhermeleobas.

@kc611, you worked on the NumPy generator. Do you have any idea where the leak is happening?

Hi.
With numba 58.1, I can still reproduce this problem.
Is there any way to work around it?

Sorry Thomas, I am not aware of any work around.
cc @kc611 for visibility

Thank you @guilhermeleobas.
I admit I just wanted to ping this issue in the hope that it will not fall out of focus.
On my side, I think the possibility to use Generators directly in numba code is incredibly cool.
It would make my code much faster.
It is exactly what I want.
The fact that this very cool feature is basically not usable because it will crash my Python, take down the executing shell, and sometimes even the computer running it ... is saddening.
It means that this beautiful feature is sitting right there but it cannot be used in any application.
The only reason why compiling code using Generators would make any sense is if that code is run often.
But if it runs often, it will cause the programs to crash.
Could you point me to wherever this compilation happens?
I do not understand the numby project structure, but if you could tell in which repo/file stuff happens, maybe I can weasel myself into it? (estimated <10% chance of success)
I assume that it will do some C magic somewhere.
Now my C is very rusty (over 20 years old), but maybe it won't hurt if another set of eyes look over the code.
While I think I can most likely not be of any help, I''d be glad to at least take a look and try...

confirm this on v59.0

I'm also affected by this bug. A partial workaround, if the code structure permits it, is to put the repeated calls to the function into another jit'ed function.

I found another workaround. It is possible to unpack the BitGenerator manually and define a custom random generator function by passing the ctypes state, like is done here (example ♯2 for a substitute of the OP's rng.integer support). By copying from https://github.com/numba/numba/blob/main/numba/np/random/new_distributions.py , it is possible to adapt all the other methods too. In my case, I needed the standard_exponential which worked like a charm.

From my perspective, I'd say the jitting of numpy.random.Generator parameters should no longer be permitted.
There might be dozens of libraries and programs out there that now have memory leaks and maybe don't even know it.
It would be better if trying to jit a function with a numpy.random.Generator directly raises an exception.
Then people can immediately see: OK, I cannot jit this function.
Then it will run a bit slower.
That's OK.
At least it seems to me that there always is the memory leak when you jit such a function.
This means that anybody doing this will have a memory leak in their code.
Compared to simply not being able to jit the function, that's a much bigger problem.
Maybe it does not show up in unit tests but crashes the real application after half an hour when you are no longer looking (as it was the case for me), maybe after hours, maybe after days.
Finding this problem is then very hard.
My suggestion would be that if fixing the problem is not feasible right now (which is totally OK and fine), then maybe for now the feature could be disabled altogether.

Thanks for the report. I debugged this a bit, seems like there's a few reference leaks in the unboxing code for the BitGenerator:
https://github.com/numba/numba/blob/301ba23116864ef66a2caccfab7c7123e7bcbcfc/numba/core/old_boxing.py#L1147-L1148
here:
https://github.com/numba/numba/blob/301ba23116864ef66a2caccfab7c7123e7bcbcfc/numba/core/old_boxing.py#L1241
and here:
https://github.com/numba/numba/blob/301ba23116864ef66a2caccfab7c7123e7bcbcfc/numba/core/old_boxing.py#L1246
Patching these locally seems to prevent most of the issue, but I then noticed a smaller continuous consumption of memory (filed as #9733). I have patches locally and plan on fixing both for 0.61.

Dude, you are a hero.
I really, really like this feature, because it is basically what I need to make my code much much faster.
I was so sad when it turned out to kill my code instead (after passing all unit tests just fine).
If that works with the next release, it would just be awesome.
Many thanks.

No problem, the leaks should be fixed via the PRs referenced above. They are in the 0.61.0-rc1 milestone (upcoming release) which means as long as there's nothing unexpected, 0.60.0 will contain fixes for this issue. Thanks for using Numba!


Fix combined feed missing messages.

discussion: https://chat.zulip.org/#narrow/channel/9-issues/topic/.F0.9F.8E.AF.20.E2.9D.93combined.20feed.20missing.20messages
Reproduced by sending a new message while latest message for combined feed was not fetched.

Still in the process of auditing rest of the add_messages calls.

This looks pretty plausible; posted a couple comments.

Merged, thanks @amanagr!


Compatibility with MAUI

Hello,
I want to know if mapster is compatible with MAUI ?
Thanks

Can you explain further what you mean by compatible? Mapster runs on .NET 6 and .NET 7.


Allow prebuilt js in run.html links

Add option to use prebuilt js on share page in arcade to speed up loading; this is mainly just an intermediary step towards prebuilding sim js in general (hopefully!)

asphodel diff:
time from page load -> first asphodel paint on my work computer:

with this (worth noting this is local serve / loading time may vary):

~Since there are changes in runner.ts we'll need to do a backend release to speed things up (I believe there are a few other changes in there that are waiting to actually get used too, like https://github.com/microsoft/pxt/pull/7463 and https://github.com/microsoft/pxt/pull/7555. Maybe we need a gh action that checks for any changes in runner.ts and adds a comment reminding us to deploy changes)~ I think I was mistaken on this after looking over things a bit more, should be fine without release
other notes:

I'm appending version suffixes so any bump would need to rebuild the source -- this isn't usually necessary except for major releases, but
plays a bit weirdly with local host, as we replace @versionsuff@ with "" there; for testing locally I just renamed the file without the suffix
I only made the cli command to build one share link's js at a time (instead of all approved sharelinks), but it'll be easy enough to add one that builds all approved links + a github action to handle checking out the right release / build all / make a pr; just a few other improvements I wanted to look at before the release / it's not a big deal to manually update when there's only one approved link at the moment anyways
~worth noting explicitly that ---run / run.html will get the option to run prebuilt js from an arbitrary source, but I don't think that's any different than just using the simulator directly / seems like we could clean up the generated code for github integration a bit with this~ changed

and example built off current arcade (not stable branch): https://github.com/microsoft/pxt-arcade/pull/2622

This is slightly better but it still creates nested iframes instead running the simulator in the main window.

[ ] our "buildtarget" command should regenerate all these files.

I can take a look at cutting the second iframe, it shouldn't be that hard as it would just be taking portions of run.html and inserting them into arcades docfiles/script.html; that's all over in arcade though.
For buildtarget do you mean dropping them in the built arcade repo instead of docs or just as part of the build? Currently these are a bit closer to the electron app than other docs, as you would want the ones in docs to always match either the current index-ref or the next one you are planning on releasing. I was planning on doing a github action for these post release that would handle cleaning and building these (take a tag you're planning on releasing as a param, delete any old builtjs that don't match target or index-ref, builds all approved share links, makes a PR updating everything) but I can do that tonight if preferred.

Look at the GitHub script page for skipping the idéale.

From: Joey Wunderlich<EMAIL_ADDRESS>Sent: Thursday, December 3, 2020 8:16:41 PM
To: microsoft/pxt<EMAIL_ADDRESS>Cc: Peli de Halleux<EMAIL_ADDRESS>Review requested<EMAIL_ADDRESS>Subject: Re: [microsoft/pxt] Allow prebuilt js in run.html links (#7681)
I can take a look at cutting the second iframe, it shouldn't be that hard as it would just be taking portions of run.html and inserting them into arcades docfiles/script.html; that's all over in arcade though.
For buildtarget do you mean dropping them in the built arcade repo instead of docs or just as part of the build? Currently these are a bit closer to the electron app than other docs, as you would want the ones in docs to always match either the current index-ref or the next one you are planning on releasing. I was planning on doing a github action for these post release that would handle cleaning and building these (take a tag you're planning on releasing as a param, delete any old builtjs that don't match target or index-ref, builds all approved share links, makes a PR updating everything) but I can do that tonight if preferred.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpxt%2Fpull%2F7681%23issuecomment-738236777&data=04|01|jhalleux%40microsoft.com|7cab44c1db9643bd6fe208d897bff74f|72f988bf86f141af91ab2d7cd011db47|1|1|637426198025360040|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=IYuTDOEO5W8ogCGbp4q5quzd0%2F8bJc7dFU31XnoU9Ak%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA73QKPJTCWRKL32P42LAYDSS7PZTANCNFSM4ULQUBSA&data=04|01|jhalleux%40microsoft.com|7cab44c1db9643bd6fe208d897bff74f|72f988bf86f141af91ab2d7cd011db47|1|1|637426198025370034|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=UrM8RYMH0usgoAU0l224tVxp%2BYoO0Yh9ZcYcV6cPz0o%3D&reserved=0.

I can take a look at cutting the second iframe, it shouldn't be that hard as it would just be taking portions of run.html and inserting them into arcades docfiles/script.html; that's all over in arcade though.**

Lets do it in a different PR.

For the build, yes i think it should be part of "pxt buildtarget". It also acts as a integration test too.

If they're built during buildtarget we'd have to create a new release any time we want to add a new prebuilt sample game, which is doable but maybe a bit tedious. Also, ideally we wanted to get the share page faster for this patch release so it's better for hour of code week, would it be alright to keep it as is for this pr and do a follow up pr changing where it's stored?
If we are baking them into releases though, my understanding is that during the build I'd be adding each game to /built/prebuiltsim/<EMAIL_ADDRESS>and then they'd be available at /blb/prebuiltsim/<EMAIL_ADDRESS>in the html (hopefully? I'll look at the order things get resolved, this would have to assume that @id@ gets replaced before the @blobCdnUrl@ is portion is handled); I haven't added anything new there yet so need to look that over.

Don't we want this for hour of code?

If they're built during buildtarget we'd have to create a new release any time we want to add a new prebuilt sample game, which is doable but maybe a bit tedious.

I don't understand that reasoning. Probably a mis understanding there. I think we should be them on every build as a test suite; probably not to commit them.

Yes we wanted to get it out in the skillmap patch, @pelikhan @mmoskal do you have time to review? Trying to keep changes here minimal for porting

I don't understand that reasoning. Probably a mis understanding there. I think we should be them on every build as a test suite; probably not to commit them.

Ah, yes, I thought you meant to save them in buildtarget, happy to add as part of ci tests but would prefer to do that in another PR for porting


docs(fix): add required v2 to theme module url

Closes #791
Since it is required by go to use /v2 for post 2.0 versions in the path this is required to get module method of using the theme to work.

Should /v2 also be added to exampleSite/config.toml as well? Since the documentation's next step after installing the module is to copy that example config file into the project's root directory, it would revert the module definition and result in the error again.


Ensure exception as last formatting parameter is picked up as exception

It would be really nice if the string-formatting overload of Logger's methods pick up an exception as last parameter and allow it to be used as a 'real exception' that will be logged according the the formatting for an exception.
This will allow a usage such as:
    public void TestExceptionLog()
    {
        string name = "my name";
        try
        {

            throw new Exception("Broken");
        }
        catch (Exception e)
        {
            Logger.Error("Unable to work for {0}", name, e);
        }
    }

Where e will be picked up as an actual exception and not ignored. The only way to do this currently is as below, but I would prefer to use a formatting overload:
    Logger.Error("Unable to work for " + name, e);

I added unit test statements to validate which exception was captured (I did not see such test statements in the tests so far, but maybe I overlooked them). Furthermore I was unfortunately not able to build the solution directly in visual studio (and did not spend enough time figuring out how to do a correct build and full unit test run) so my changes might not be completely correct, but I believe the basic working should be ok.

Logger.Error("Unable to work for {0}", name, e)

This overload would make resharper complain that e argument is not used in format string, so it's generally not a good idea to give special meaning to some of string.Format arguments.

There were already some discussions, related to exception-taking overloads with format string arguments: see #63, https://github.com/NLog/NLog/issues/431#issuecomment-66605694.

You can also use the fluent interface!

How would one do this with the fluent interface?

I added some thoughts to #431 comments.

I'm not sure if this would work, but could you use  with type inference?
just typing some things here
public void Info(string message, args, T exception) where T : Exception
and call it with
log.Info("this was not for working for {0}", name, ex)

Thanks for the PR but I don't think this PR is a good solution. I'm now typing on a mobile so I can't easily explain this with many lines but I think the solution proposed in #431 (exception as first parameter) Is much more clear and less "magic" . Also is easier to retain backwards compatible

I agree, this may be too magic

Closing this PR but the discussion is still open on #431

The good things about this 'magic' approach:

very minor change in the codebase (only 1 line updated in LogEventInfo, other changes are just unit tests)
very unlikely that this breaks anyones code (even if last argument was intended as an exception to be included in the formatted message that still occurs, only change is that the exception will also be caught as a proper exception), and it might even fix some bugs (where people were expecting the exception to be properly caught)
no 'new' API, just added feature of existing methods (actually I believe you could get rid of a few overloads of info(), etc since now one method definition captures all variations: void info(string message, params object[] arguments)
consistent API (Exception always sent as last parameter). To achieve this with the Exception as first parameter (as suggested) requires new overloads on all methods taking an Exception so it may be passed as first parameter and marking all current ones as obsolete. That's quite a big change for all existing users...

IMO code/API's should be transparent. Magic is the opposite of  transparent.
The issues I see:

It's nontransparent (as said before)
It's is non-backwards compatible change (same API, different behavior)
I can affect the performance (10K log calls =  10K checks for datatype)

IMO the non-backwards compatible change is a big change for existing users.


update rand to 0.7 and quickcheck to 0.9

I have also bumped version to 0.2.1.

@srijs Ping! Any objections?


Error in date parse from log file, it is not possible to see the container logs

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description

I can't see the logs from the jellyfin container, when I run
podman logs --tail=100 jellyfin

Steps to reproduce the issue:

Create a jellyfin container (that example is exactly what I execute to create my container)

podman create \
  --name=jellyfin \
  --privileged \
  --restart=always \
  -e TZ=America/Sao_Paulo \
  -p 8096:8096 \
  -v /opt/data/Vídeos/jellyfin/jellyfin:/config \
  -v /opt//data/Vídeos/jellyfin/tvShows:/data/tvshows \
  -v /opt//data/Vídeos/jellyfin/Filmes:/data/movies \
  linuxserver/jellyfin

Run it

podman start jellyfin

Try to get the logs

podman logs --tail=100 jellyfin

Describe the results you received:
I received that output when I try do see the log, seems to be a error with a parse from the timestamp ?
Error: unable to read log file 91fdd32c59e9d4376e49c389e92093f74bafdf04b624271e89dc229fef6cb328 for /var/home/emerson/.local/share/containers/storage/overlay-containers/91fdd32c59e9d4376e49c389e92093f74bafdf04b624271e89dc229fef6cb328/userdata/ctr.log : unable to convert time  from container log: parsing time "" as "2006-01-02T15:04:05.000000000Z07:00": cannot parse "" as "2006"

Describe the results you expected:
If I tail the file descripted on the command I can see the log, I guess this is what I need to see when running the podman logs command
tail -f /var/home/emerson/.local/share/containers/storage/overlay-containers

output
/91fdd32c59e9d4376e49c389e92093f74bafdf04b624271e89dc229fef6cb328/userdata/ctr.log
2020-04-04T21:00:30.447079981-03:00 stdout F [21:00:30] [INF] [1] App: Executed all post-startup entry points in 0:00:00.2608729
2020-04-04T21:00:30.447106641-03:00 stdout F [21:00:30] [INF] [1] Main: Startup complete 0:00:04.5772437
2020-04-04T21:00:30.645704778-03:00 stdout F [21:00:30] [INF] [10] LibraryMonitor: Watching directory /data/movies
2020-04-04T21:00:30.809927046-03:00 stdout F [21:00:30] [INF] [12] LibraryMonitor: Watching directory /data/tvshows/Séries
2020-04-04T21:00:31.012889394-03:00 stdout F [21:00:31] [INF] [6] LibraryMonitor: Watching directory /data/tvshows/Animes
2020-04-04T21:00:32.904564251-03:00 stdout F [21:00:32] [INF] [14] TaskManager: StartupTrigger fired for task: Update Plugins
2020-04-04T21:00:32.905100373-03:00 stdout F [21:00:32] [INF] [14] TaskManager: Queueing task PluginUpdateTask
2020-04-04T21:00:32.907051132-03:00 stdout F [21:00:32] [INF] [12] TaskManager: Executing Update Plugins
2020-04-04T21:00:34.030666731-03:00 stdout F [21:00:34] [INF] [21] TaskManager: Update Plugins Completed after 0 minute(s) and 1 seconds
2020-04-04T21:00:34.060047647-03:00 stdout F [21:00:34] [INF] [21] TaskManager: ExecuteQueuedTasks

Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version:            1.8.2
RemoteAPI Version:  1
Go Version:         go1.14
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.14
  podman version: 1.8.2
host:
  BuildahVersion: 1.14.3
  CgroupVersion: v2
  Conmon:
    package: conmon-2.0.14-1.fc32.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.14, commit: a08df20e61ed6795fd25cc9e27ef452cf3259c06'
  Distribution:
    distribution: fedora
    version: "32"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  MemFree:<PHONE_NUMBER>6
  MemTotal:<PHONE_NUMBER>2
  OCIRuntime:
    name: crun
    package: crun-0.13-1.fc32.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.13
      commit: e79e4de4ac16da0ce48777afb72c6241de870525
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 12
  eventlogger: journald
  hostname: bakemono
  kernel: 5.6.0-300.fc32.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.3-6.0.dev.gita8414d1.fc32.x86_64
    Version: |-
      slirp4netns version 0.4.3+dev
      commit: a8414d1d1629f6f7a93b60b55e183a93d10d9a1c
  uptime: 4h 55m 34.26s (Approximately 0.17 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
store:
  ConfigFile: /var/home/emerson/.config/containers/storage.conf
  ContainerStore:
    number: 1
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7.8-1.fc32.x86_64
      Version: |-
        fusermount3 version: 3.9.1
        fuse-overlayfs: version 0.7.8
        FUSE library version 3.9.1
        using FUSE kernel interface version 7.31
  GraphRoot: /var/home/emerson/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 1
  RunRoot: /run/user/1000/containers
  VolumePath: /var/home/emerson/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.8.2-2.fc32.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
Os: Fedora 32 Silverblue

@baude Any ideas?

Hey, I don't know what happen, but It's working now, maybe some package update ?
podman version
Version:            1.8.2
RemoteAPI Version:  1
Go Version:         go1.14
OS/Arch:            linux/amd64

podman info --debug
debug:
  compiler: gc
  git commit: ""
  go version: go1.14
  podman version: 1.8.2
host:
  BuildahVersion: 1.14.3
  CgroupVersion: v2
  Conmon:
    package: conmon-2.0.14-1.fc32.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.14, commit: a08df20e61ed6795fd25cc9e27ef452cf3259c06'
  Distribution:
    distribution: fedora
    version: "32"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  MemFree:<PHONE_NUMBER>
  MemTotal:<PHONE_NUMBER>4
  OCIRuntime:
    name: crun
    package: crun-0.13-1.fc32.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.13
      commit: e79e4de4ac16da0ce48777afb72c6241de870525
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 12
  eventlogger: journald
  hostname: bakemono
  kernel: 5.6.2-301.fc32.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.3-6.0.dev.gita8414d1.fc32.x86_64
    Version: |-
      slirp4netns version 0.4.3+dev
      commit: a8414d1d1629f6f7a93b60b55e183a93d10d9a1c
  uptime: 28h 15m 39.54s (Approximately 1.17 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
store:
  ConfigFile: /var/home/emerson/.config/containers/storage.conf
  ContainerStore:
    number: 3
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7.8-1.fc32.x86_64
      Version: |-
        fusermount3 version: 3.9.1
        fuse-overlayfs: version 0.7.8
        FUSE library version 3.9.1
        using FUSE kernel interface version 7.31
  GraphRoot: /var/home/emerson/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 3
  RunRoot: /run/user/1000/containers
  VolumePath: /var/home/emerson/.local/share/containers/storage/volumes

podman logs --tail 5000 -f jellyfin
[emerson@bakemono ~]$ podman logs --tail 1000 -f jellyfin
[12:17:18] [INF] [76] LibraryMonitor: Ajuste de Contas (/data/tvshows/Séries/The Mandalorian/The.Mandalorian.S01E07.1080p.WEB-DL.DDP5.1.H264.DUAL-LAPUMiA.mkv) will be refreshed.
[12:17:18] [INF] [76] LibraryMonitor: O Mandaloriano (/data/tvshows/Séries/The Mandalorian/The.Mandalorian.S01E01.1080p.WEB-DL.DD5.1.H264.DUAL-LAPUMiA.mkv) will be refreshed.
[12:17:18] [INF] [76] LibraryMonitor: O Pistoleiro (/data/tvshows/Séries/The Mandalorian/The.Mandalorian.S01E05.1080p.WEB-DL.x264.DUAL-WWW.BLUDV.TV.mkv) will be refreshed.
[12:17:18] [INF] [76] LibraryMonitor: Redenção (/data/tvshows/Séries/The Mandalorian/The.Mandalorian.S01E08.1080p.WEB-DL.DDP5.1.H264.DUAL-LAPUMiA.mkv) will be refreshed.
[12:17:32] [INF] [109] LibraryMonitor: movies (/data/movies) will be refreshed.
[12:17:32] [INF] [109] LibraryMonitor: Sonic.the.Hedgehog.2020.1080p.HC.HDRip.Dublado (/data/movies/Sonic the Hedgehog/Sonic.the.Hedgehog.2020.1080p.HC.HDRip.Dublado.mkv) will be refreshed.
[12:17:18] [INF] [76] LibraryMonitor: O Pistoleiro (/data/tvshows/Séries/The Mandalorian/The.Mandalorian.S01E05.1080p.WEB-DL.x264.DUAL-WWW.BLUDV.TV.mkv) will be refreshed.
[12:17:18] [INF] [76] LibraryMonitor: Redenção (/data/tvshows/Séries/The Mandalorian/The.Mandalorian.S01E08.1080p.WEB-DL.DDP5.1.H264.DUAL-LAPUMiA.mkv) will be refreshed.
[12:17:32] [INF] [109] LibraryMonitor: movies (/data/movies) will be refreshed.
[12:17:32] [INF] [109] LibraryMonitor: Sonic.the.Hedgehog.2020.1080p.HC.HDRip.Dublado (/data/movies/Sonic the Hedgehog/Sonic.the.Hedgehog.2020.1080p.HC.HDRip.Dublado.mkv) will be refreshed.
^C
[emerson@bakemono ~]$ podman logs --tail 1000 -f jellyfin
[12:17:18] [INF] [76] LibraryMonitor: Ajuste de Contas (/data/tvshows/Séries/The Mandalorian/The.Mandalorian.S01E07.1080p.WEB-DL.DDP5.1.H264.DUAL-LAPUMiA.mkv) will be refreshed.
[12:17:18] [INF] [76] LibraryMonitor: O Mandaloriano (/data/tvshows/Séries/The Mandalorian/The.Mandalorian.S01E01.1080p.WEB-DL.DD5.1.H264.DUAL-LAPUMiA.mkv) will be refreshed.
[12:17:18] [INF] [76] LibraryMonitor: O Pistoleiro (/data/tvshows/Séries/The Mandalorian/The.Mandalorian.S01E05.1080p.WEB-DL.x264.DUAL-WWW.BLUDV.TV.mkv) will be refreshed.
[12:17:18] [INF] [76] LibraryMonitor: Redenção (/data/tvshows/Séries/The Mandalorian/The.Mandalorian.S01E08.1080p.WEB-DL.DDP5.1.H264.DUAL-LAPUMiA.mkv) will be refreshed.
[12:17:32] [INF] [109] LibraryMonitor: movies (/data/movies) will be refreshed.
[12:17:32] [INF] [109] LibraryMonitor: Sonic.the.Hedgehog.2020.1080p.HC.HDRip.Dublado (/data/movies/Sonic the Hedgehog/Sonic.the.Hedgehog.2020.1080p.HC.HDRip.Dublado.mkv) will be refreshed.

What to do? close that issue ?


Added IAP Desktop version 2.14.565. (as a v1.0 manifest).

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Have you tested your manifest locally with winget install -m ?

Microsoft Reviewers: Open in CodeFlow

/azp run


Metadata extraction fails on 4-space-or-more indented content

I'm working with the latest version on master, and found that you can blow up the first pass parse time (to a degree where I haven't seen it stop!) with any content indented by four spaces or more:
---
anything:
    indented4Spaces: true
---

Configuration:
let mut options = Options::all();

(I imagine this is possible to trigger by just enabling the ENABLE_YAML_STYLE_METADATA_BLOCKS option, but haven't checked yet.)
This goes for any time something is indented that far in the metadata block, including nested keys like this:
---
something:
  nested:
    twice: true
---

Or lists:
---
lists:
    - indented 4 spaces
---

Thanks, it was an important bug. It has been fixed in #690.


Adonis Client using pcall on nil function

what even?!?!?!

Wtf that shouldn't be happening lol

oh uh I haven;t seen this and it's been over a year soooooo ;)


Feature/issue 86

Closes #86

Pull Request Test Coverage Report for Build 1116

191 of 218 (87.61%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 87.626%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

safe_relay_service/relay/services/stats_service.py
35
38
92.11%

safe_relay_service/relay/models.py
38
43
88.37%

safe_relay_service/relay/models_raw.py
54
63
85.71%

safe_relay_service/relay/views.py
11
21
52.38%

Totals

Change from base Build 1103:
0.2%

Covered Lines:
4362

Relevant Lines:
4978

💛  - Coveralls

Pull Request Test Coverage Report for Build 1114

191 of 218 (87.61%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 87.626%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

safe_relay_service/relay/services/stats_service.py
35
38
92.11%

safe_relay_service/relay/models.py
38
43
88.37%

safe_relay_service/relay/models_raw.py
54
63
85.71%

safe_relay_service/relay/views.py
11
21
52.38%

Totals

Change from base Build 1103:
0.2%

Covered Lines:
4362

Relevant Lines:
4978

💛  - Coveralls


Reorganize examples

I think we should:

[ ] remove all nb examples except for quickstart, test_gc, and for now imagewidget. Once we have imgui integration we can remove imagewidget as well and just have the quickstart notebook
[ ] move examples/desktop to just examples/ and have these as the main examples for everything, docs, tests, users, etc. Move any examples that are currently only in the notebook to here.

@clewis7 thoughts? I think this will make everything easier to maintain, and easier for users too since there would only be one set of examples.

I think so too, much easier to have many many examples
The version control with the notebooks is tedious anyway I think

I think in the future it would also be nice to add sections of the gallery for domain-specific examples (neuro, astronomy, etc.)


cmake: find_dependency(spdlog)

Type of change:
Please delete options that are not relevant.

[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)
[ ] This change requires a documentation update

Checklist:

[ ] Pull request title reflects its content
[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Description:
Fix cmake dependency of spdlog.
This is cherry-picked from branch release/3.2.

As @JakaMohorkoDS said in #597 there shouldn't be any external dependency on spdlog.
If there is, that should be fixed instead.


[BUG] OOM during indexing

OOM memory when indexing and similar for some search request
I am trying to understand is this due to GPU , do we do hnsw indexing and search using GPU ?

Do you mind adding more details? For example, the number of documents you are trying to index, there number of search requests, and the machine's available disk, RAM and GPU/CPU?
As far as I know, HNSW traversal uses the CPU

oh ok  if hnsw indexing and search is all on cpu we can close this because then it is probably some issue with my model inference on gpu


Adds a mention for this-based type guards in the handbook v2

This was only mentioned in the 1.8 release notes, now it gets a re-direct in the narrowing section and lives in the classes one.

Perhaps it'd be worth adding a specific example for using this to remove an undefined value?  This does seem to be a common usage of this pattern, and it may not be obvious from the this is Subtype examples.
class Box<T> {
    value?: T;
    hasValue(): this is { value: T } {
      return this.value !== undefined;
    }
}


BIGTOP-3537. Fix puppetize.sh to work with the latest CentOS 8 Docker image.

https://issues.apache.org/jira/browse/BIGTOP-3537

Because this issue is blocking us from running CI using CentOS 8, I'm going to merge it in accordance with the CTR manner.

All images are successfully built with this PR.
https://ci.bigtop.apache.org/view/Docker/job/Docker-Puppet-Trunk/29/

@sekikn Sorry for late reply. I'm +1 based on the comment on JIRA .