display-name triggered on default export using React.memo

This issue was originally reported by @jwalton in #2133. Confirmed that issue exists in 7.13.0 and 7.14.1 (we are not using typescript in our project).

simple solution there, use a default export :-D

In latest build, this appears to be broken for a default export (although... I'm in a typescript project, so this might be a problem specific to linting .tsx files):
export default React.memo(function LabelControl(props: ControlProps) {
    const control = props.control as OnDemandLabelControl;

    return (
        <ControlWrapper>
            <Translate tagName="h2" message={control.title} />
        </ControlWrapper>
    );
});

triggers react/display-name, but:
function LabelControl(props: ControlProps) {
    const control = props.control as OnDemandLabelControl;

    return (
        <ControlWrapper>
            <Translate tagName="h2" message={control.title} />
        </ControlWrapper>
    );
}

export default React.memo(LabelControl);

does not.
Originally posted by @jwalton in https://github.com/yannickcr/eslint-plugin-react/issues/2133#issuecomment-502449263

Thanks for confirming this was in vanilla js.  :)

Yep, I am getting the same error with something as simple as:
export const Foo = React.memo(
    function Foo() {
        return <div>:(</div>;
    }
);

However, in the React dev tools, the component has the display name Foo just fine. If I use an arrow function instead, then there is no display name (just shows as Component) and the error would be correct.

I'm also getting this error with the forwardRef function (e.g. as in #2269, but without the same issues with propTypes).  I'm getting this when using named exports (e.g. export const Foo = forwardRef(...)) and with default exports (e.g. export default forwardRef(...)).
In all of these cases, as best I can see, the forwardRef and memo functions use the name of the wrapped component (or component-like).  Certainly, when I look in React DevTools, I can see the correct component name in all of these cases.

Still get the same issue as @TrevorSayre

Please update to v7.17, released yesterday, and file a new issue if you’re still having trouble.


Add support for stopping multiple projects with stop command

Update tm stop <project> to be able to stop multiple projects.
For example: tm stop project1 project2 project3

Implemented in latest release


Menu not able to build simple item that is { ID, string, string }

This line doesn't seem to build:
            wxUI::Item { wxID_FIND, "&Find\tCTRL-F", "No-op Find" },

It looks like it's because Item has this deduction:
    template <typename F>
    Item(wxStandardID identity, std::string const& name, F function)
        : Item(identity, name, "", function)
    {
    }

That template F gets Hungry, and will "swallow" anything, including strings.
Why not just call it the function type that we expect?

Fixed with #133


Custom request body validation

Is there a way to make use of the zod Schema.strict in the automatic validation of a request body? Or override/disable the automatic validation?
At the moment if I create a schema
const TestSchema = z.object({
    foo: z.string()
})

class TestPost extends OpenAPIRoute {
    static schema = {
        requestBody: TestSchema,
    }
    ...
}

And then send this payload to the route
{
    "foo": "example",
    "bar": "example"
}

this will be accepted as valid even though "bar" is not a valid property on TestSchema
TestSchema.strict(...) is how I would handle this manually but unsure how/if the default validation behaviour would be modified. Or is the only way to handle this to parse the data again in the handler?

Hey @henrytoone to enable the strict mode, you just need to enable the raiseUnknownParameters flag in the router.
Check the router options here.

Hi @G4brym , I gave this a go and it doesn't seem to be working. I'm not sure if it's something else I've missed but the option seems to have no effect
const router = OpenAPIRouter({
	raiseUnknownParameters: true,
});

const TestSchema = z.object({
	foo: z.string(),
});

class TestPost extends OpenAPIRoute {
	static schema = {
		requestBody: TestSchema,
	};
	async handle(request: Request, env: any, context: any, data: Record<string, any>) {
		// Create typed object
		const body = TestSchema.parse(data.body);

		return { ok: true };
	}
}

router
	.post('/test', TestPost)

	// 404 for all misses
	.all('*', () => error(404, 'not found'));

Then sending the payload below still returns the ok response
{
    "foo": "example",
    "bar": "example"
}


chore: udpate configuration for renovate

↪ Pull Request

[ ] Make sure you are opening from a feature/feat/docs/fix/bug/hotfix/stable/chore (right side) and not your master branch!
[ ] Ensure that the pull request title represents the desired changelog entry

📒 Description

🕶 Types of changes

[ ] Core
[ ] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[ ] Documentation
[ ] Dependencies

🤯 List of changes

👫 Relationships

🔎 Review hints

🚨 Test instructions

Checklist

[ ] My code follows the code style of this project.
[ ] I have read the CONTRIBUTING document.
[ ] Added/updated unit tests for this change
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).
[ ] Filled out test instructions (In case there aren't any unit tests)
[ ] I followed the existing code standards and didn't mess up the formatting.
[ ] My change requires a change to the documentation.
[ ] I did my best to add documentation to any public classes or methods I added.
[ ] Included links to related issues/PRs


Fixes inconsistent encoding behavior.

Python encodes ASCII by default and escapes the unicode characters.
This fix enforces utf-8.
Python 3.5.2 (default, Nov 23 2017, 16:37:01)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ipfsapi
>>> api = ipfsapi.connect('<IP_ADDRESS>', 5001)
>>> val = {"key": "Value, não é?"}
>>> api.add_json(val)
'QmNRzhk1e4cHYpqej7LjguBd5fP4uLyVYTQFfJFGm9ESLQ'
>>> api.get_json('QmNRzhk1e4cHYpqej7LjguBd5fP4uLyVYTQFfJFGm9ESLQ')
{'key': 'Value, não é?'}
>>>

This is ok, expected behavior.
https://ipfs.io/ipfs/QmNRzhk1e4cHYpqej7LjguBd5fP4uLyVYTQFfJFGm9ESLQ <-- Ok here as well.

Thanks for finding this! This really shouldn't be happening. :slightly_smiling_face:

Was merged as part of #168 for py-ipfs-http-client.


Snakefile: update to newer pypsa-eur with '_ec' in filename

If you seek to at some point use a newer version of PyPSA-Eur beyond https://github.com/PyPSA/pypsa-eur/commit/81d9d2ab4d5dccec14db1b02283bd0b04d1acbed, this change is necessary.

implemented in f9952b9aadffc4fde0b8d659b404fd7864221fc6


Handling missing references

This issue is more related to citeproc, but I decided to open it here. As I only played with citation-js this weekend,  there might be a solution that I couldn't find in the documentation.
Issue:
When we try to output a citation that does not exist in our input references, a SyntaxError: Unexpected token u in JSON at position 0 is fired.
I guess citeproc tries to retrieve a reference like so:
Item = JSON.parse(JSON.stringify(this.sys.retrieveItem("" + id)));
However, in case of an undefined JSON.parse( .. ) fires Uncaught SyntaxError.
Wanted behavior:
If a reference is missing, it would be nice to output question marks, i.e., ??.
Example:

This works

let Cite = require("citation-js");

let cite = new Cite( [ { id: 1, title: 'ref1' }, { id: 2, title: 'ref2'  } ] );

const opt = { format: "html", template: "apa", lang: "en-US"};

let citation = cite.format("citation", {
  entry: [ 1, 2 ],
  opt,
});

console.log( citation );

// Output
// (“ref1,” n.d.-a; “ref2,” n.d.-b)

This doesn't work

let citation = cite.format("citation", {
  entry: [ 1, 2, 3 ],
  opt,
})

// Output
// SyntaxError: Unexpected token u in JSON at position 0

Wanted output

(“ref1,” n.d.-a; “ref2,” n.d.-b; ??)

MWE: Codesandbox

Since citation-js does not control the citeproc-js output it would be a bit difficult to prescribe ?? as the output for unknown references, but it could avoid the error internally by passing an empty object if no reference is found (probably rendering n.d.). The CSL plugin is the next one on the list to get a rework if all goes well, so I can improve the process a bit there.

Thank you @larsgw for your replay.
Yeah, using a dummy (empty) object outputs n.d..

To avoid unexpected output I am going to clarify the error message ("Cannot find entry with id '...'") instead of outputting a placeholder.


fix(deps): update terraform terraform-ibm-modules/cos/ibm to v8.2.1

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
patch
8.2.0 -> 8.2.1

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.2.1
Compare Source
Bug Fixes

validation to allow null values (#599) (f45883e)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

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

GitHub release
v0.5.5

Your semantic-release bot :package::rocket:


Add conditional compilation for Less while DEBUG = True

Since Less gives the option of compilation at runtime via a JavaScript library, it'd be nice if django-pipeline could include an option for using runtime compilation while DEBUG = True.
Currently, you can do this with the following template code, but it'd be nicer if this could be integrated with django-pipeline:
{% if debug %}
    <link href="{% get_static_prefix %}styles/application.less" rel="stylesheet" type="text/css" />
    <script src="{% get_static_prefix %}scripts/less.js" type="text/javascript"></script>
{% else %}
    {% compressed_css 'all' %}
{% endif %}

That would duplicate pipeline auto-compilation of less/coffee/sass on DEBUG.


Module parse failed: Unexpected token

Hello. I get error on project start
Module parse failed: Unexpected token (209:148)
File was processed with these loaders:

./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|
|   const focus = tree.focusedNode;

if (!focus) return ((_tree$root$children = tree.root.children) === null || _tree$root$children === void 0 ? void 0 : _tree$root$children.length) ?? 0;
|   if (focus.isOpen) return 0;
|   if (focus.parent) return focus.childIndex + 1;

Project created with CRA
Environment
Node: 12.22.7
React: 17.0.2
react-scripts: 4.0.3

Fixed by migrating app to CRA version 5


Add monitor task decorator to create tasks that to poll some state

This PR introduces an monitor task decorator, which can be particularly useful for tasks that need to poll some state (e.g.,  the presence of a file, the state of another WorkGraph) at given intervals until a success criterion is met.
Possible use cases:

Time trigger: start a task until a given time.
File trigger: start a task until a file exits.
Task monitor: monitor the state of a task and determine what's to do for a special event.
Cross-WorkGraph Dependencies: allows adding a task that checks the state of another task inside a different workgraph.

Note: while polling the state, the task will sleep for a given interval (default 1.0 second, can be changed by user), and relinquish control to the WorkGraph engine, so that it can run other tasks.
Example Usage:
Time monitor
A task wati until a given time.
@task.monitor()
def time_monitor(time):
    """Return True if the current time is greater than the given time."""
    return datetime.datetime.now() > time

# The task will wait until 2024-08-16, 10:54
monitor1 = wg.add_task(time_monitor, time=datetime.datetime(2024, 8, 16, 10, 54, 0))
add1 = wg.add_task(add, "add1",x = 1, y = 2)
add1.waiting_on.add(monitor1)

File monitor
Start a task until a file exits.
@task.monitor()
def file_monitor(filename):
    """Check if the file exists."""
    import os
    return os.path.exists(filename)

# The task will wait until the file exists, checking every 60 seconds.
monitor1 = wg.add_task(file_monitor, filepath="/tmp/test.txt", interval=60.0)
add1 = wg.add_task(add, "add1",x = 1, y = 2)
add1.waiting_on.add(monitor1)

Builtin tasks
I created two builtin Tasks: TimeMonitor and FileMonitor
monitor1 = wg.add_task("workgraph.time_monitor", datetime=datetime.datetime.now() + datetime.timedelta(seconds=10))

monitor2 = wg.add_task("workgraph.file_monitor", filepath="/tmp/test.txt")

General awaitable task
I also created an awaitable decorator to allow the user to take full control of the asyncio function.
import asyncio
from aiida_workgraph import WorkGraph, task
from aiida import load_profile

# Load the AiiDA profile
load_profile()

# Define an awaitable task using the new decorator
@task.awaitable()
async def awaitable_func(x, y):
    await asyncio.sleep(0.5)  # Simulate a delay for polling
    return x + y

# Create a WorkGraph and add the awaitable task to it
wg = WorkGraph(name="test_awaitable")
awaitable1 = wg.add_task(awaitable_func, "awaitable_func1", x=1, y=2)

# Run the WorkGraph
wg.run()

About the the asyncio
The awaitable task will let the WorkGraph go to the Waiting state. the task will relinquish control to the asyncio event loop, thus the WorkGraph can run other tasks.
However, if there is a long-running calcfunction, the available task will wait for the calcfunction to finish before it can get the control to run the next next step.

Codecov Report
Attention: Patch coverage is 79.34783% with 19 lines in your changes missing coverage. Please review.

Project coverage is 79.36%. Comparing base (5937b88) to head (2a8c9f5).
Report is 34 commits behind head on main.

Files
Patch %
Lines

aiida_workgraph/engine/workgraph.py
70.31%
19 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #235      +/-   ##
==========================================
+ Coverage   75.75%   79.36%   +3.60%
==========================================
  Files          70       63       -7
  Lines        4615     4627      +12
==========================================
+ Hits         3496     3672     +176
+ Misses       1119      955     -164

Flag
Coverage Δ

python-3.11
79.36% <79.34%> (+3.69%)
:arrow_up:

python-3.9
?

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

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

Extensive! Great to have the monitor. I take it this supports monitoring in the AiiDA sense? So currently in AiiDA, a monitor function can be assigned to a CalcJob (see docs). Though initially intended to terminate the job if some condition is met, the monitor function can in principle do more.
Is this PR's feature meant to replicate this via aiida-workgraph methodology? Could you please comment a bit on what it can('t) do? For example, can it kill the job or attach (tracked) outputs to the job? These are currently supported. One interesting future (current?) task for a monitor would be to trigger other jobs if some condition is met. This is a feature request from the W&C community. The trick is how we should keep track of these actions in the provenance.
As for awaitable decorator (maybe should be in a separate PR?), no comments there. I don't play with async all that much. However, good to support it, as concurrency is a powerful tool in general!

@edan-bainglass , thanks for for the comment!
The Calcjob monitor and the WorkGraph monitor are different in terms of the scope of monitoring.
The Monitor in AiiDA currently works on the Calcjob. It is called within the CalcJob's process, so it can modify its output. This is intra-process monitoring.
The Monitor in WorkGraph is a task. The monitor task can monitor any events (e.g. time, file changes, etc.) as long as there is a API. Of course, it can also monitor the AiiDA processes using AiiDA API. It can fetch the state of other AiiDA processes, and it can kill/pause/play the process, but it can not modify the data (outputs) of the process. This is inter-process monitoring.

One interesting future (current?) task for a monitor would be to trigger other jobs if some condition is met.

This is exactly what the monitor task does.

The trick is how we should keep track of these actions in the provenance.

The provenance is not tracked as the monitor task is not a aiida process, and it can not be a process, otherwise it will store too much unuseful data. I believe we need to create a special data type for the monitor task to store the provenance, because AiiDA provenance requires AiiDA data,
The monitor task is actually implemented using the awatiable feature similar to the awaitable decorator, but we hide the asyncio from the user. The user only needs to write the monitor task as a normal function, and the WorkGraph will take care of the rest.

@superstar54 thanks for clarifying the various parts. Let's discuss next week the submission of other jobs via a monitor. This is quite interesting.
As for the PR, good to merge when you're ready.


Verilator

Add unit-tests for Verilator backend support.
NB! This test currently fails!
See: https://groups.google.com/forum/#!topic/chisel-users/2cfBgvQpDcc

Thanks!


price and currency still appear when cart visibility set to false

hey @omahili, you work is amazing. Thank you for creating this packages.
i have some question,

how to disable price and currency in legends?
it's possible to set price based on row and col  index?

Hi, thank you!

Currently it's not possible to hide prices from the legend. You need to create your own custom legend and omit it.

Yes, you can set seats as you wish across the map. Add a type to options.map.seatTypes and populate seats. For example:

seatTypes: {
   default: {
     // ...
   },
   reduced: {
      price: 10,
      label: 'Reduced',
      cssClass: 'reduced',
       seats: [
          { row: 1, col: 1 },
          // ...
       ],
   },
},

See the docs, for more details.

Solved, thank youu @omahili


Segmentation fault running tests on Ubuntu 14.04

This isn't just from running tests. Parsing anything seems to do it, its just the easiest way I've found to reproduce it. Following your build from source steps here. Doesn't seem to matter if using system install or using your bootstrap script. Also, needed to install the following packages to get it to compile properly...
sudo apt-get install libbz2-dev zlib1g-dev libssl-dev
Output:
(.env)root@pos:~/spaCy# py.test tests/
==================== test session starts ====================
platform linux2 -- Python 2.7.5 -- py-1.4.30 -- pytest-2.7.2
rootdir: /root/spaCy, inifile:
collected 142 items

tests/test_docs.py Segmentation fault (core dumped)
(.env)root@pos:~/spaCy#

Let me know if any other info would be helpful or anything else I can try. I'd love to test this further but so far I've only been able to reliably get it running locally on OSX. I've run into the same issues on Docker installs as well.
Further Info:
(.env)root@pos:~/spaCy# pip2.7 list
cymem (1.11)
Cython (0.22.1)
ecdsa (0.13)
Fabric (1.10.2)
fabtools (0.19.0)
murmurhash (0.24)
numpy (1.9.2)
paramiko (1.15.2)
pathlib (1.0.1)
pip (1.5.6)
plac (0.9.1)
preshed (0.37)
py (1.4.30)
pycrypto (2.6.1)
pytest (2.7.2)
setuptools (3.6)
six (1.9.0)
thinc (3.0)
ujson (1.33)
Unidecode (0.04.18)
wget (2.2)
wsgiref (0.1.2)

Also, build-essential and python-dev are installed.

Hey,
I shouldn't have pushed this version to master --- I'm about to do another release, and the data you're downloading is incompatible with the code in the current master branch. I also don't have a tag for the last version. #walkofshame
Specifically, I've switched the data format in the parsing model, to reduce memory usage. But the version you're using is trying to load a model with the old format, which doesn't work.
Options:

Checkout b266a63f2cc, reinstall requirements (which should be pinned to the correct version of 'thinc', the model loading code that's causing the problem)
Install from pip, which has the code compatible with the current model
Hold off a little bit, and I'll have the new model uploaded (probably 2 or 3 hours).

I've tried the pip method as well. Python still crashes while parsing. If running in debug mode it appears to also be a segmentation fault. Possible its two different issues, but the pip version crashing is what caused me to try building from source. I'll try starting with a fresh environment and attempt to recreate in a few hours.

Hmm, okay.
Let me get the release up --- I'm doing it now. Then we can at least debug the latest version.
Thanks for the report.

Okay, v0.87 is on pip.
Everything's working on my server, and on Travis. See how you go.

Still having issues from pip with python dying. I'll try building from source a little later. Any suggestions on how I can get you more info to debug?

Hmm.
How much memory is available?

2GB. It never uses it all though it gets close before crashing. Do you recommend more?

I can try more as well, only reason I thought the 2 was safe was I didn't see swap getting pegged.

So I have an update... I got it to work. Though I've changed a few variables here, so I'm not 100% on which was the main issue just yet.
Main Variables Changed:
Ubuntu 14.04  -> Ubuntu 15.04
Python 2.7.x   ->  Python 3.4.3
Memory 2GB  -> 8GB
I'm guessing it was the memory seems to be using around 4.2GB of the 8. I'll try a few more scenarios. Hoping it'll play nice w/ 4GB as the 8GB instances are a good deal more $.

I had a similar memory issue on a smaller machine. If you're using Amazon -
m4.large might be your friend for better performance.
On Tue, Jun 30, 2015 at 2:26 PM, Nicholas Hilem<EMAIL_ADDRESS>wrote:

So I have an update... I got it to work. Though I've changed a few
variables here, so I'm not 100% on which was the main issue just yet.
Main Variables Changed:
Ubuntu 14.04 -> Ubuntu 15.04
Python 2.7.x -> Python 3.4.3
Memory 2GB -> 8GB
I'm guessing it was the memory seems to be using around 4.2GB of the 8.
I'll try a few more scenarios. Hoping it'll play nice w/ 4GB as the 8GB
instances are a good deal more $.
—
Reply to this email directly or view it on GitHub
https://github.com/honnibal/spaCy/issues/71#issuecomment-117350064.

Depending on what you're doing, you could save some memory by passing load_vectors=False when you create an instance of the English class.
v0.87 has some improvements in memory efficiency — it should use 30-40% less than v0.86.

Interesting... I'll give that a try as well. Thanks!


feat!: Add support for Nuxt 3

This PR enables this module to work for  Nuxt 3.
Notable changes

Uses @nuxt/module-builder to build module.
Refactor structure (lib -> src, templates -> runtime)
Rewrite in TypeScript
Move from templating options to runtime config

TODO

Re-enable test suite (https://github.com/nuxt/framework/pull/2952)

any updates?

@DenchiUA  You can use nuxt-gtag in the meanwhile. It's a native Gtag integration for Nuxt 3.


[swift-4.0-branch] Fix access level for extern_proc.p_starttime

Explanation: The original fix did not mark the new property as public which made it unavailable outside the standard library. This change fixes the access level.
Scope of Issue: Makes an existing API public (which was the intention in the first place)
Risk: none
Reviewed By: Ted Kremenek
Testing: Automated test suite
Directions for QA: N/A
Radar: rdar://problem/32819749

@swift-ci Please test

Similar to https://github.com/apple/swift/pull/10323

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - fd54a1dada997c9f2a17d5df5cc1ec5f15b49782
Test requested by - @moiseev


Some formatting cleanup.

Making formatting (periods at end) consistent among lines
Making language around "discount of X% off" consistent
Fixing empty links so they won't lead to a Github 404

Looks good 👍
Hope you are enjoying your journey with OpenGenus


"-" character doesn't work for triggering snippets

VSCode Version: 1.1.1
OS Version: win 10

Steps to Reproduce:

Add this snippet
{
"Method Comment Header": {
"prefix": "--",
"body": [
"// -------------------------------------------------------------------------",
"\t$1"
],
"description": "Method Comment Header"
}
}
Try to trigger it via "--"
It does not work
Try triggering via normal letter characters, say "hh"
Works fine.

The proposal is actually in the list, but even when entering --, it is at the very last:

@joaomoreno @jrieken Joh or Joao?

@aeschli Is the issue that the snippet isn't revealed when typing --?

It's not selected. You have to scroll down and look for it and select it yourself.
Thats how it looks after Ctrl+Space:

assigning to @joaomoreno who knows how to select

Current word madness.

oh, - is for sure nowhere a word

Yeah, the selection algorithm is selecting the empty string as the current word for sure.

We made filtering already independent of the currentWord but use text selected by overrideBefore (which default to the current word). In effect filtering is now custom to each suggestion. I wonder if we can do the same for selecting the best match.

The problem here is that trigger 24x7 IntelliSense only when a word is being typed. Characters like - or # usually aren't part of a word, at least not with the word definition of that language. Unsure what to do about this...

Closing this as designed. The 24x7 IntelliSense feature works by detecting when a word is being typed. What a word is depends on the language being used and can be set by that language. I don't think we should temper with that word-behaviour in favour of some snippets.
This is what you can do:

use tab completion after typing --
use insert snippet from F1
invoke intellisense manually and type --

Thanks for understanding and Happy Coding


When is Android support expected to be implemented?

Hello, I was wondering when Android support for this plugin is expected to be implemented? Thanks.

Thank you for your request.
I plan to add the implementation for Android this year.
Unfortunately, other projects have a higher priority at the moment and I can't provide a more specific deadline.
The progress will be tracked in this issue: #13


Add validity check to SaveStatsPeriodically_Threaded

Simply adds an IsValid check into the foreach player loop in SaveStatsPeriodically_Threaded.
In short, this is causing crashes for the same reason as #767, but far more rarely, as this loop only executes every five seconds, and a player must disconnect at the exact same time it runs. Still, I've had it happen.
[19:55:53] [NORTHSTAR] [info] Player player disconnected: "You were disconnected due to being AFK"
[19:55:53] [NORTHSTAR] [info] Player player disconnected: "You were disconnected due to being AFK"
[19:55:53] [NORTHSTAR] [warn] attempted to write pdata of size 0!
[19:55:53] [SCRIPT SV] [info] SCRIPT ERROR: [SERVER] Persistent data not available.
[19:55:53] [SCRIPT SV] [info]  -> player.SetPersistentVar( key, expect float( player.GetPersistentVar( key ) ) + val )
[19:55:53] [SCRIPT SV] [info]
CALLSTACK
*FUNCTION [Stats_SaveAllStats()] mp/_stats.nut line [93]
*FUNCTION [SaveStatsPeriodically_Threaded()] mp/_stats.nut line [1041]

[19:55:53] [SCRIPT SV] [info] LOCALS
[@ITERATOR@] 5
[val] 8.3329941844568e-005
[key] "timeStats.dead"
[player] ENTITY (player player [9] (player "player" at <-4847.97 -975.969 328.046>))
[this] TABLE
[@ITERATOR@] 9
[player] ENTITY (player player [9] (player "player" at <-4847.97 -975.969 328.046>))
[@INDEX@] 8
[this] TABLE

DIAGPRINTS

abnormal program termination

It may be prudent to look into modifying GetPlayerArray rather than adding these fixes... Though for now I've modded these two in on my servers, and it has drastically reduced crashes.

@ASpoonPlaysGames

This really isn't testable other than hosting a server for a prolonged period of time and checking for script errors. This is basically what @CTalvio did so I'm forgoing testing on my end ^^


Tabs do not render correctly

It seems - or so I am experiencing - the Tabs component does not render correctly when used with vaadin-app-layout.
Following the example called 'Tabs with pages' here, under the regular MainLayout (from the Vaadin Starter that has the menu on top), the tabs correctly look like this:

In an application that uses AppLayoutRouterLayout<LeftLayouts.LeftResponsiveHybrid>, the rendered Tabs component looks like this:

The tab names are too close to each other and there are no links.
Tested with Brave, Safari latest on macOS 10.15.1 with Vaadin 14.0.13 and app-layout-addon 4.0.0.rc4.
Thanks...!

Tested against master and Vaadin 14.1.4. I was not able to reproduce this issue.

Hi appreciated,
I have the very same issue here.
Vaadin: 14.1.19.
Used layout: LeftResponsiveSmallNoAppBar
Running on: Spring Boot 2.1


Spring Cloud Sleuth GCP: every time spans are sent, they are sent to localhost as well

There should be a way to turn off the default ZipkinRestTemplateSenderConfiguration when using Spring Cloud GCP. I would prefer if it was turned off by default.
Currently, every time spans are being sent, a completely unnecessary call to http://localhost:9411/api/v2/spans, and it fails 100% of the time because there is nothing there to answer.
The only reason I saw it was because I used logging.level.org.springframework.cloud=TRACE.
I tried to fix it by setting spring.zipkin.enabled=false but it crashes on startup because of ZipkinBackwardsCompatibilityAutoConfiguration.
If there already is a way to turn this off I would be very happy. Anyway my opinion is it should be off by default because I have already chosen spring.cloud.gcp.trace.enabled=true.
Thanks.

Shouldn't it get fixed in Spring Cloud GCP?

Sorry, it probably should... I will post it there instead


crf tagger fails with SIGSEGV signal if faced with unknown word or word with typo

I assume the problem rely in the fact that in those case tagged word not inside a corpus. But failing in those case looks like something wrong for me.
Based on the latest provided crf model this code cause problem for me:
std::vector<std::string> tokens{"Boby", "go", "to", "school", "every", "week"}; //Boby contains a typo. But could be any other word.

std::string pathToModel = "/path/to/model";
crf crf1{pathToModel};
auto tg = crf1.make_tagger();
meta::sequence::sequence seq;

auto analyzer = meta::sequence::default_pos_analyzer();
analyzer.load(pathToModel);

std::for_each(sentence.begin(), sentence.end(), [&seq](std::string token) {
       seq.add_observation({meta::sequence::symbol_t{token}, meta::sequence::tag_t{"[UNK]"}});
});

analyzer.analyze(seq);
tg.tag(seq);

//... trying to print tagged results

Admittedly this API could be better, but the problem is in the usage. As described in the POS tagging tutorial, you're missing the critical step
const auto& ana = analyzer; // access the analyzer via const ref
                            // so that no new feature ids are generated
ana.analyze(seq);

Calling analyze on a non-const analyzer will allow it to generate new feature ids as is done during training. During testing, you want the const version of the function so that it ignores previously unseen features.
Let me know if that fixes the issue for you (I suspect it will).

Indeed, accessing via const reference solving the problem. Looks like a magic for me (sorry, quite new in C++ after decade of coding other langs). Could you explain to me - how it's possible that the way we acessing object affect how logic executed?


Style logs

Style logs:

Print headers in a private function to avoid repeating code.
Print a separator among requests / responses to view easily when each starts / ends.

Example of output:
---------------------
GET 'https://github.com/konkab/AlamofireNetworkActivityLogger':
Headers: [
  Content-Type : application/x-www-form-urlencoded; charset=utf-8
  Authorization : XXXX
]
---------------------
200 'https://github.com/konkab/AlamofireNetworkActivityLogger' [1.2180 s]:
Headers: [
  Cache-Control : max-age=0, private, must-revalidate
  ...
  Server : Cowboy
]
[
  {
  ...
  }
]

@pablog nice!


Limitless LED Not responding

Home Assistant release (hass --version):
14.2
Python release (python3 --version):
3.4.4
Component/platform:
Limitlessled
Description of problem:
Platform no longer responds to changes/commands in HA to certain groups Bulbs still respond with their own APP
Expected:
All groups to be controlled as expected log shows no limitless LED pipeline events after commands sent in HA ( see log snippet below)
16-03-01 22:00:00 limitlessled.pipeline: Starting a new pipeline on group 2 (Bedroom) @ <IP_ADDRESS>
16-03-01 22:00:00 homeassistant.core: Bus:Handling <Event service_executed[L]: service_call_id=55456040-125>
16-03-01 22:00:00 limitlessled.pipeline:  -> Running stage 'on()' on group 2 (Bedroom) @ <IP_ADDRESS>
16-03-01 22:00:00 homeassistant.core: Bus:Handling <Event service_executed[L]: service_call_id=55456040-124>
16-03-01 22:00:01 limitlessled.pipeline:  -> Running stage 'white()' on group 2 (Bedroom) @
16-03-01 22:00:01 limitlessled.pipeline:  -> Running stage 'transition(0, brightness=1.0, color=Color(R=255, G=255, B=255))' on group 2 (Bedroom) @ <IP_ADDRESS>
16-03-01 22:00:02 limitlessled.pipeline: Finished pipeline on group 2 (Bedroom) @ <IP_ADDRESS>
Problem-relevant configuration.yaml entries and steps to reproduce:
light:
  platform: limitlessled
  bridges:
    - host: <IP_ADDRESS>
      version: 5
      port: 8899
      groups:
      - number: 1
        type: rgbw
        name: Living Room
      - number: 1
        type: white
        name: Dinning Room
      - number: 2
        type: rgbw
        name: Bedroom
      - number: 3
        type: rgbw
        name: Man Cave
      - number: 2
        type: white
        name: Porch
      - number: 3
        type: white
        name: Rear Porch
script:
 bedroomwakeup:
    alias: bedroom light on wakeup
    sequence:
      - alias: bedroom light on low
        service: light.turn_on
        data:
          entity_id: light.bedroom
          brightness: 1
          rgb_color: [255,255,255]
      - alias: bedroom light on bright
        service: light.turn_on
        data:
          entity_id: light.bedroom
          brightness: 255
          rgb_color: [255,255,255]
          transition: 360
      - delay:
          # supports seconds, milliseconds, minutes, hours, etc.
          minutes: 15
      - alias: Bedroom transition Off
        service: light.turn_on
        data:
          entity_id: light.bedroom
          brightness: 120
          rgb_color: [255,255,255]
          transition: 120
scene:
  - name: Bedroom Normal
    entities:
        light.bedroom:
            state: on
            transition: 2
            brightness: 120
            rgb_color: [255,255,255]
  - name: Bedroom Playing media
    entities:
        light.bedroom:
            state: on
            transition: 2
            brightness: 20
            rgb_color: [255,255,255]

Seems to be random sometimes it works fine othertimes it does not
1.
2.
3.
Traceback (if applicable):

Additional info:
log entry with no limitless pipeline events.
16-03-02 07:30:00 homeassistant.components.automation: Executing bedroom light on at 7:30
16-03-02 07:30:00 homeassistant.components.device_tracker.fritz: Scanning
16-03-02 07:30:00 requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): <IP_ADDRESS>
16-03-02 07:30:00 requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): <IP_ADDRESS>
16-03-02 07:30:00 requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): <IP_ADDRESS>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event logbook_entry[L]: name=bedroom light on at 7:30, domain=automation, message=has been triggered>
16-03-02 07:30:00 requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): <IP_ADDRESS>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event call_service[L]: domain=homeassistant, service_data=entity_id=['script.bedroomwakeup'], service_call_id=55456040-140, service=turn_on>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event call_service[L]: domain=script, service_data=entity_id=['script.bedroomwakeup'], service_call_id=55456040-141, service=turn_on>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event call_service[L]: domain=script, service_data=None, service_call_id=55456040-142, service=bedroomwakeup>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event service_executed[L]: service_call_id=55456040-141>
16-03-02 07:30:00 homeassistant.components.script: Executing script bedroom light on wakeup
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event service_executed[L]: service_call_id=55456040-140>
16-03-02 07:30:00 homeassistant.components.script: Executing script bedroom light on wakeup step bedroom light on low
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event call_service[L]: domain=light, service_data=entity_id=light.bedroom, brightness=1, rgb_color=[255, 255, 255], service_call_id=55456040-143, service=turn_on>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=light.bedroom, old_state=<state light.bedroom=off; friendly_name=Bedroom @ 23:05:00 01-03-2016>, new_state=<state light.bedroom=on; brightness=1, friendly_name=Bedroom, rgb_color=[255, 255, 255] @ 07:30:00 02-03-2016>>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event service_executed[L]: service_call_id=55456040-143>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=group.all_lights, old_state=<state group.all_lights=off; entity_id=('light.living_room', 'light.rear_porch', 'light.man_cave', 'light.bedroom', 'light.dinning_room', 'light.porch'), auto=True, order=1, hidden=True, friendly_name=all lights @ 23:05:00 01-03-2016>, new_state=<state group.all_lights=on; entity_id=('light.living_room', 'light.rear_porch', 'light.man_cave', 'light.bedroom', 'light.dinning_room', 'light.porch'), auto=True, order=1, hidden=True, friendly_name=all lights @ 07:30:00 02-03-2016>>
16-03-02 07:30:00 homeassistant.components.script: Executing script bedroom light on wakeup step bedroom light on low
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event call_service[L]: domain=light, service_data=entity_id=light.bedroom, brightness=255, transition=360, rgb_color=[255, 255, 255], service_call_id=55456040-144, service=turn_on>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=light.bedroom, old_state=<state light.bedroom=on; brightness=1, friendly_name=Bedroom, rgb_color=[255, 255, 255] @ 07:30:00 02-03-2016>, new_state=<state light.bedroom=on; brightness=255, friendly_name=Bedroom, rgb_color=[255, 255, 255] @ 07:30:00 02-03-2016>>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event service_executed[L]: service_call_id=55456040-144>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=script.bedroomwakeup, old_state=<state script.bedroomwakeup=off; friendly_name=bedroom light on wakeup, can_cancel=False, hidden=True @ 17:56:47 01-03-2016>, new_state=<state script.bedroomwakeup=on; friendly_name=bedroom light on wakeup, can_cancel=False, last_action=bedroom light on low, hidden=True @ 07:30:00 02-03-2016>>
16-03-02 07:30:00 homeassistant.core: Bus:Handling <Event service_executed[L]: service_call_id=55456040-142>
16-03-02 07:30:00 requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): <IP_ADDRESS>

Related to https://github.com/balloob/home-assistant/issues/1409

Anyone have an idea what the problem is here? The issue persists until I restart HA.

Try disabling your transitions as a quick fix.

It seems to behave better now without transitions but i would like to get this fixed. The odd thing is HA doesn't throw up any errors related to the pipeline they simply don't appear in the log after the event/new state? At some point i'm sure I have seen a 'division by zero error' related to limitless module but I can't find it now..

This issue still persists. I'll try disabling transitions but this should be addressed. I'd like to help out finding the cause for this. If there's anything you need for information let me know.

Indeed unfortunately I dont have the knowledge to fix this myself.  But I can provide whatever logs/resource needed to get it fixed.

I too experienced this behavior - but only when triggering from MQTT events via automation. I would merely be setting brightness levels via automation commands - and maybe 1 out of 10 times, the bulb group would go unresponsive in HA.
Using the Milight/EasyBulb app could still control the lights. Restarting HA would clear the fault.
I have since moved to HAASKA and have set the brightness at least 60 times without a single such issue.

No sure if my issue is related or if it's normal but my milights react very slow especially if you dimm them it can take 4-5 seconds until do start dimming turning off and on seems to work faster?
Anyone experienced that as well?

...and it persists. Many months and many major versions later, while native and third party apps just work. Not that I am complaining, but... perhaps there are workarounds that would mimic those apps? Like command line switch sending out UDP requests?
Is there a chance that someone "adopts" the issue?
Thanks

Same issue here.  Strangely, it was working perfectly until I upgraded to .35
I have a ton of these bulbs in my apt and would be willing to put in a donation if someone is able to sort it out for good...

I'd pinch in

If anyone is still following, I found the workaround. Example below is for white group 1.
100% reliable so far.
platform: command_line     switches:       living_room:         friendly_name: Living Room         command_on: 'echo -n -e "\x38\00\x55" > /dev/udp/<IP_ADDRESS>/8899'         command_off: 'echo -n -e "\x3b\00\x55" > /dev/udp/<IP_ADDRESS>/8899'
If you use HA in the docker, you'll need to set SSH without password between docker and host system, and modify commands.
platform: command_line     switches:       living_room:         friendly_name: Living Room         command_on: ssh user@host 'echo -n -e "\x38\00\x55" > /dev/udp/<IP_ADDRESS>/8899'         command_off: ssh user@host 'echo -n -e "\x3b\00\x55" > /dev/udp/<IP_ADDRESS>/8899'
Command reference:
https://github.com/stoman/MilightAPI/blob/master/doc/limitlessled-documentation.txt

FYI: These might be related to https://github.com/home-assistant/home-assistant/issues/6295. Pipeline never finishes with certain transition.

Closing this because it appears to be fixed by #6334.


Tests fail on Windows

lxd test failure is expected, because server part can't be run on Windows. shared tests would be nice to have and client test should probably work too.
# github.com/lxc/lxd/shared
.\util_test.go:38: undefined: syscall.Setxattr
.\util_test.go:47: undefined: syscall.Setxattr
.\util_test.go:59: undefined: GetAllXattr
.\util_test.go:79: undefined: GetAllXattr
.\util_test.go:158: undefined: ReadLastNLines
.\util_test.go:177: undefined: ReadLastNLines
FAIL    github.com/lxc/lxd/shared [build failed]

# github.com/lxc/lxd/lxd
.\nsexec.go:26:23: fatal error: sys/mount.h: No such file or directory
compilation terminated.
FAIL    github.com/lxc/lxd/lxd [build failed]

github.com\lxc\lxd>go test
--- FAIL: TestLocalLXDError (0.00s)
        client_test.go:34: GetLocalLXDErr returned the wrong error, EXPECTED: connection refused, ACTUAL: %!s(<nil>)
FAIL
exit status 1
FAIL    github.com/lxc/lxd      0.077s

Yeah, there's definitely no way you'll get a clean test run for the lxd directory until someone spends some serious time contributing a windows container backend, but having shared and lxc pass tests on Windows and MacOS would be nice.
Will be easy enough to add a test run to Travis and AppVisor once any issue with those is sorted out.

GetLocalLXDErr is connectViaUnix fail, which should probably use https://github.com/natefinch/npipe on Windows.

connectViaUnix simply can't work on Windows, no matter how much porting you do since it's only relevant if lxd can be running on the same system as the client, which it can't on Windows.

connectViaUnix should probably be somehow restricted to Linux with all other platforms returning an error if attempted

I mean that Windows' named pipes provides the same mechanism for local communication channel. So maybe it is possible to factor out this interface into some FileSocketConnection?

Well, creating util_linux_test.go seems to be the easiest solution.

My point is that making a generic Socket/Pipe connector in LXD doesn't make sense. It'd bring in more dependencies for something which will just never work anyway as this feature is only relevant if the client and daemon run on the same machine.
Much easier to just make this fail on other OS and skip any tests.


Proving mem_approx for functions involving ofNat

How should one prove mem_approx_f below?
I don't know how to prove the sorry and also don't know how one might generalize mem_approx_ofNat to work for numbers besides 2.
import Interval

def Interval.f (x : Interval) : Interval := x / 2

noncomputable def Real.f (x : ℝ) : ℝ := x / 2

@[mono] lemma mem_approx_ofNat :
  (n : ℝ) ∈ approx (OfNat.ofNat 2 : Interval) := by
  sorry

@[mono] lemma mem_approx_f (ix : Interval) (x : ℝ) (is_approx_x : x ∈ approx ix) :
    x.f ∈ approx ix.f := by
  simp [Interval.f, Real.f]
  mono

With naive approach of adding
@[mono] lemma mem_approx_ofNat' {n : ℕ} [OfNat Interval n]:
  (n : ℝ) ∈ approx (OfNat.ofNat n : Interval) := by
  sorry

@[mono] lemma mem_approx_f (ix : Interval) (x : ℝ) (is_approx_x : x ∈ approx ix) :
    x.f ∈ approx ix.f := by
  simp [Interval.f, Real.f]
  mono
  exact mem_approx_ofNat'

mono does not pick up on it.

Sorry for delay! I've updated to recent Mathlib now, and also ported my mono machinery over to a much cleaner custom approx tactic built on Aesop. The new version of your code is:
import Interval

def Interval.f (x : Interval) : Interval := x / 2

noncomputable def Real.f (x : ℝ) : ℝ := x / 2

@[mono] lemma mem_approx_f (ix : Interval) (x : ℝ) (m : x ∈ approx ix) :
    x.f ∈ approx ix.f := by
  simp only [Real.f, Interval.f]
  approx

Unfortunately all the OfNat related lemmas have to be carefully marked with no_index due to https://github.com/leanprover/lean4/issues/2867, but this should be all done now.

That works great, thanks!


Datepicker input value not updated in html

This issue pertains to ui.bootstrap.datepicker. The issue is that when using .val() to set the value of the datepicker input field, the value is set in the DOM but not in the html whereas by using .attr() to set the 'value' attribute sets both.
I have what may be a unique situation where I need to extract the html and render elsewhere, causing the value in the DOM to be lost and a blank input to be displayed.

plunkr please

Here is a plunkr demonstrating the behavior: http://plnkr.co/edit/JLAQ1rAtGJac5qybTuIP?p=preview
I realize my initial comment is a bit cryptic.  The solution I propose is simply:
Use the jqLite .attr() method to set the value of the input instead of .val()

This works perfectly fine, as demonstrated by this Plunker fork.
There is not much that should be done on UI Bootstrap's side - the data is available in the DOM and the model value, it is up to the developer to make use of their JavaScript to extract the necessary values, since it is something that the developer can control.


Support for sequences

I tried mariadb4j and it worked nicely until it stumbled over sequences.
MariaDB supports sequences starting from Version 10.3.
So the current version of mariaDB which MariaDB4j is using must be below 10.3? Can I see that version somewhere?

MariaDB4j supports using existing native MariaDB binaries on the host system rather than unpacking MariaDB from the classpath. This is useful if you need a newer version than is currently distributed [...]

So if I would supply a newer version of mariaDB also sequences would be supported?
Thanks!

So the current version of mariaDB which MariaDB4j is using must be below 10.3? Can I see that version somewhere?

see https://github.com/vorburger/MariaDB4j/blob/main/mariaDB4j/pom.xml

So if I would supply a newer version of mariaDB also sequences would be supported?

@Lonzak Yeah, that's correct. If you would be interested in raising a PR to contribute to this project for this, you could pick up #710, which made a great start with upgrading the native binaries.

@Lonzak in #771 @TheKnowles has contributed (and it got merged as part of #772)  a newer version MariaDB binaries.
I suspect that that will fix this issue. Would you like to (for now, either use https://jitpack.io/#vorburger/MariaDB4j/main-SNAPSHOT or locally build and) try it out?

Sounds promising! Unfortunately I currently I do not have the time to try it out...Maybe someone else in the community can?

@Lonzak I suspect those newer version MariaDB will support SQL for sequences.
Let's close this issue; any future readers, please open a new issue, or (better) a PR with a fix if any is required!


WFP Traffic Inspection Sample: the last ACK at release not send

Hi all,
Description
While running the latest inspection sample of WFP, I set BlockTraffic to 0 and RemoteAddressToInspect to <IP_ADDRESS>.
I used curl to send data to the host I inspected, the TCP connection establishment / data transition worked fine, but the final ACK of connection release was not sent. (And the remote host resent 5 FIN and 1 RST to release the connection)

My Investigation
I tried both FWPM_LAYER_OUTBOUND_IPPACKET_V4 filter and Wireshark to sniff the final ACK outbound packet, but captured nothing.
And I got netBufferList->Status of STATUS_NOT_FOUND 0xC0000225L in the completeFn of FwpsInjectTransportSendAsync. So I wondered if the endpointHandle was invalid at final ACK, which is documented in MSDN:

Callout drivers should use the provided handle to inject cloned packets back into the data path as soon as possible, before the socket associated with the stack endpoint is closed and the handle becomes no longer valid.

Thanks 😄

I met the same proble, when try to use proxy scenarios. In the proxy scenario, WFPSampler hooks FWPS_LAYER_OUTBOUND_TRANSPORT_V4 and FWPS_LAYER_INBOUND_IPPACKET_V4.
when deals with TCP, connection establishment SYN, SYNACK, SYN are proxied,
when the connection is closing, the first FIN, ACK, FINACK are proxied, however the last ACK packet can not be sent using FwpsInjectTransportSendAsync event the status is 0.

I saw somewhere in the documentation that "injecting arbitrary FINs into the transport layer" is not permitted. My guess is what Microsoft is enforcing this rule somehow in a sloppy way.
The transport layer is a mess when it comes to TCP. There are so many rules prohibiting so many things, I'm not quite sure what use the layer is beyond passive inspection and binary permit/deny.

What is the current status of this issue? It reveals a serious flaw in WFP architecture. It makes F in WFP impossible.

i also faced a similar problem for reinjecting back the dns request  packet captured in the datagram layer. for reinjection it back i was using FwpsInjectTransportSendAsync() and the packet was not sent out , same can be verified through wireshark. In the completion handle of the packet i dumped the NET_BUFFER_LIST_STATUS(pNetBufferList)) and it showed  0xC0000225. Later on i figured out  i was not filling the endpointHandle, once that is taken care of the problem gets resolved.


Upgrade to helm v.3.0.0-beta

All the migrated charts doesn't appear in helm ls -n ${ns} in Helm v.3.0.0-beta.1
Could you please upgrade the plugin?

PR GH-9 did a trick for me and now I see migrated release. However, I am not a Go developer so mostly what I did is 'change things until they start to work' :)
BR,
Bohdan

@slenky Thanks for raising this PR. The plugin has an issue because there were changes in the release metadata from Helm 3 alpha to beta. lets get the updated delivered in PR #9 that you have pushed.


Verifiy if the CL interpolated after stall is 0 or CL_max

After stall, the get_CL function should return 0.
The CD should also return a big number if stalled.
Those are in aerodynamic_surfaces.py

We should think about how to transport this to ADR 2.0.

The content of this issue is being registered in a list of things to be aware of during the development of ADR2 and the issue is being closed.


Trouble passing -co arguments

Great library, thank you.
When I pass co arguments on linux and mac, Pyvips fails. Mac and linux.
Any tips greatly appreciated.
kubi -r lbb -f nx px py ny nz pz test.jpg test_out.jpg -co overlap=0
Traceback (most recent call last):
  File "/usr/local/bin/kubi", line 33, in <module>
    sys.exit(load_entry_point('kubi', 'console_scripts', 'kubi')())
  File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 343, in run
    main(sys.argv[1:])
  File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 339, in main
    kubi(args)
  File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 225, in kubi
    mapim.write_to_file(f'{dst}_{fn}{dst_ext}', **args.co)
  File "/usr/local/lib/python3.9/site-packages/pyvips/vimage.py", line 804, in write_to_file
    return pyvips.Operation.call(name, self, filename,
  File "/usr/local/lib/python3.9/site-packages/pyvips/voperation.py", line 288, in call
    raise Error('{0} does not support optional argument {1}'
pyvips.error.Error: VipsForeignSaveJpegFile does not support optional argument overlap

kubi -r lbb -f nx px py ny nz pz test.jpg test_out.jpg -co jpg
Traceback (most recent call last):
  File "/usr/local/bin/kubi", line 33, in <module>
    sys.exit(load_entry_point('kubi', 'console_scripts', 'kubi')())
  File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 343, in run
    main(sys.argv[1:])
  File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 339, in main
    kubi(args)
  File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 225, in kubi
    mapim.write_to_file(f'{dst}_{fn}{dst_ext}', **args.co)
  File "/usr/local/lib/python3.9/site-packages/pyvips/vimage.py", line 804, in write_to_file
    return pyvips.Operation.call(name, self, filename,
  File "/usr/local/lib/python3.9/site-packages/pyvips/voperation.py", line 288, in call
    raise Error('{0} does not support optional argument {1}'
pyvips.error.Error: VipsForeignSaveJpegFile does not support optional argument compression

Havn't looked into this but maybe it helps to move the -co before the input and output?!Am 11.09.2023 20:05 schrieb Clayton Rothschild @.***>:
Great library, thank you.
When I pass co arguments on linux and mac, Pyvips fails. Mac and linux.
Any tips greatly appreciated.
kubi -r lbb -f nx px py ny nz pz test.jpg test_out.jpg -co overlap=0
Traceback (most recent call last):
File "/usr/local/bin/kubi", line 33, in
sys.exit(load_entry_point('kubi', 'console_scripts', 'kubi')())
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 343, in run
main(sys.argv[1:])
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 339, in main
kubi(args)
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 225, in kubi
mapim.write_to_file(f'{dst}_{fn}{dst_ext}', **args.co)
File "/usr/local/lib/python3.9/site-packages/pyvips/vimage.py", line 804, in write_to_file
return pyvips.Operation.call(name, self, filename,
File "/usr/local/lib/python3.9/site-packages/pyvips/voperation.py", line 288, in call
raise Error('{0} does not support optional argument {1}'
pyvips.error.Error: VipsForeignSaveJpegFile does not support optional argument overlap
kubi -r lbb -f nx px py ny nz pz test.jpg test_out.jpg -co jpg
Traceback (most recent call last):
File "/usr/local/bin/kubi", line 33, in
sys.exit(load_entry_point('kubi', 'console_scripts', 'kubi')())
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 343, in run
main(sys.argv[1:])
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 339, in main
kubi(args)
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 225, in kubi
mapim.write_to_file(f'{dst}_{fn}{dst_ext}', **args.co)
File "/usr/local/lib/python3.9/site-packages/pyvips/vimage.py", line 804, in write_to_file
return pyvips.Operation.call(name, self, filename,
File "/usr/local/lib/python3.9/site-packages/pyvips/voperation.py", line 288, in call
raise Error('{0} does not support optional argument {1}'
pyvips.error.Error: VipsForeignSaveJpegFile does not support optional argument compression
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Oh wait I think it clearly says what the problem is those options are not supported fo jpeg. Compresdion is available for tiffs for example (you can use jpeg compresdion in a tiff or lzw or something else). The overlap option is only available for deepzoom (.dz) image pyramids.So I would say the errors are correct.Am 11.09.2023 20:05 schrieb Clayton Rothschild @.***>:
Great library, thank you.
When I pass co arguments on linux and mac, Pyvips fails. Mac and linux.
Any tips greatly appreciated.
kubi -r lbb -f nx px py ny nz pz test.jpg test_out.jpg -co overlap=0
Traceback (most recent call last):
File "/usr/local/bin/kubi", line 33, in
sys.exit(load_entry_point('kubi', 'console_scripts', 'kubi')())
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 343, in run
main(sys.argv[1:])
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 339, in main
kubi(args)
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 225, in kubi
mapim.write_to_file(f'{dst}_{fn}{dst_ext}', **args.co)
File "/usr/local/lib/python3.9/site-packages/pyvips/vimage.py", line 804, in write_to_file
return pyvips.Operation.call(name, self, filename,
File "/usr/local/lib/python3.9/site-packages/pyvips/voperation.py", line 288, in call
raise Error('{0} does not support optional argument {1}'
pyvips.error.Error: VipsForeignSaveJpegFile does not support optional argument overlap
kubi -r lbb -f nx px py ny nz pz test.jpg test_out.jpg -co jpg
Traceback (most recent call last):
File "/usr/local/bin/kubi", line 33, in
sys.exit(load_entry_point('kubi', 'console_scripts', 'kubi')())
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 343, in run
main(sys.argv[1:])
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 339, in main
kubi(args)
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 225, in kubi
mapim.write_to_file(f'{dst}_{fn}{dst_ext}', **args.co)
File "/usr/local/lib/python3.9/site-packages/pyvips/vimage.py", line 804, in write_to_file
return pyvips.Operation.call(name, self, filename,
File "/usr/local/lib/python3.9/site-packages/pyvips/voperation.py", line 288, in call
raise Error('{0} does not support optional argument {1}'
pyvips.error.Error: VipsForeignSaveJpegFile does not support optional argument compression
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Here is a list of the options for jpegsave: https://libvips.github.io/pyvips/vimage.html#pyvips.Image.jpegsaveMaybe you wanted "Q" for quality?Am 11.09.2023 20:05 schrieb Clayton Rothschild @.***>:
Great library, thank you.
When I pass co arguments on linux and mac, Pyvips fails. Mac and linux.
Any tips greatly appreciated.
kubi -r lbb -f nx px py ny nz pz test.jpg test_out.jpg -co overlap=0
Traceback (most recent call last):
File "/usr/local/bin/kubi", line 33, in
sys.exit(load_entry_point('kubi', 'console_scripts', 'kubi')())
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 343, in run
main(sys.argv[1:])
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 339, in main
kubi(args)
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 225, in kubi
mapim.write_to_file(f'{dst}_{fn}{dst_ext}', **args.co)
File "/usr/local/lib/python3.9/site-packages/pyvips/vimage.py", line 804, in write_to_file
return pyvips.Operation.call(name, self, filename,
File "/usr/local/lib/python3.9/site-packages/pyvips/voperation.py", line 288, in call
raise Error('{0} does not support optional argument {1}'
pyvips.error.Error: VipsForeignSaveJpegFile does not support optional argument overlap
kubi -r lbb -f nx px py ny nz pz test.jpg test_out.jpg -co jpg
Traceback (most recent call last):
File "/usr/local/bin/kubi", line 33, in
sys.exit(load_entry_point('kubi', 'console_scripts', 'kubi')())
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 343, in run
main(sys.argv[1:])
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 339, in main
kubi(args)
File "/usr/local/lib/python3.9/site-packages/kubi/kubi.py", line 225, in kubi
mapim.write_to_file(f'{dst}_{fn}{dst_ext}', **args.co)
File "/usr/local/lib/python3.9/site-packages/pyvips/vimage.py", line 804, in write_to_file
return pyvips.Operation.call(name, self, filename,
File "/usr/local/lib/python3.9/site-packages/pyvips/voperation.py", line 288, in call
raise Error('{0} does not support optional argument {1}'
pyvips.error.Error: VipsForeignSaveJpegFile does not support optional argument compression
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

@claytonrothschild Were you able to solve the problems and generate the desired output with kubi? Should I close this?

The solution is that indeed the -co arguments fail if one is not generating an image pyramid (dzsave) - as those arguments are specific to image pyramid.
Details here
So for example, this will fail:
kubi -r lbb -f nx px py ny nz pz test.jpg test_out.jpg -co overlap=0

but this will succeed no problem:
kubi -r lbb -f nx px py ny nz pz test.jpg test_out.dz -co overlap=0

We can close this!


False negative for E1012 Ref not found

cfn-lint version: (cfn-lint --version) 0.48.0
Description of issue.
Example template:
AWSTemplateFormatVersion: 2010-09-09

Resources:

  A:
    Type: AWS::Route53::HostedZone
    Properties:
      Name: example.com.

  Record:
    Type: AWS::Route53::RecordSet
    Properties:
      Name: example.com.
      Type: CNAME
      HostedZoneId: !Ref AB
      ResourceRecords:
      - example.org

Linting this passes even though the !Ref AB fails on cloudformation
Commeting out resource "A" makse it fail - it looks to me like any !Ref that matches a prefix will pass. This may be due to use of re.match in RegexDict without a terminating $.

Good catch. I'm on it.

it looks to me like any !Ref that matches a prefix will pass

@kddejong is this from modules support? Should continue matching prefixes for modules while only allowing exact matches for resources

yea, I just got a PR in to do exactly that.

Looks like the RegexDict fixes we did for modules opened up this issue.  Switching that Regex dict to handle only doing that comparison when the type is a Module.


Bloomberg Service URI

I notice that currently the service uri's that are supported are //blp/refdata and //blp/mkdata.
I keep going over the blpapi docs and everywhere, the service URI is //blp/mktdata.  Is this a misunderstanding on my part?
Great work and thanks!

@pliew looks like a typo...are you able to test this? We no longer have access to a connection?

Hi @andrewstevenson
I recompiled the connector correcting the typo, but it looks like it's not operating correctly.
Two issues come up:

For refdata, it seems to only insert a static amount of data (not sure if this is just performing a snapshot of somesort)
The connector doesn't seem to store the entire element.

I haven't been able to dive deeper into this but at first glance that is what I could spot out.

@pliew We can have a look but since we don't have any connection to bloomberg anymore it's difficult to check, we can start looking at the issues but any help from your side is much appreciated. Do you have any logs of what your are seeing?

Hi @pliew
Could you please join the Slack channel - so that we can have a direct chat and try to resolve your issues ?
There's a button at https://datamountaineer.com/contact/

fixed in master.


Introducing BlobStoreCompactor

BlobStoreCompactor is data moving component of compaction that copies valid data from
the segments under compaction to the swap spaces and executes an atomic swap once compaction
is complete. It executes compaction based on the details provided by CompactionDetails and
records progress in the CompactionLog
Built and formatted.
All known code paths including recovery and various blob configurations are covered by tests.
Will add logging and metrics in this PR or as a follow up - so they are not blockers.
Primary reviewers: @pnarayanan, @nsivabalan
Unit testing

Class
Class, %
Method, %
Line, %
Test class

BlobStoreCompactor
100% (3/ 3)
100% (33/ 33)
97.3% (319/ 328)
BlobStoreCompactorTest

@nsivabalan @pnarayanan Gentle reminder to review.

@pnarayanan @nsivabalan Comments addressed.
72507d5 and 49ab400 are the commits with the changes. The rest are the result of a rebase.

@nsivabalan Addressed comments.

@pnarayanan @nsivabalan I have attached a diff of the changes that show how the APIs in the compactor will be used and how the compaction thread will be run. I can add it to this PR or create a new one once this is merged.
CompactionThread.txt

#576 provides some context on how these APIs are going to be used.

@nsivabalan @pnarayanan Comments addressed

@pnarayanan Comments addressed

Looks good to me.

@pnarayanan Comments addressed

@pnarayanan 201174e is the commit with the most recent changes.

@pnarayanan Addressed comments


External tracing.zipkin.address results in requests with host=zipkin

Bug Description
We've been migrating from a cluster.local zipkin collector to one behind an ELB so that in a multi-cluster scenario, our traces are unified. However, when we made that change, we found that we got no traces from istio into it. After some debugging, we found the ELB logs that the host of the request is being set to just "zipkin" instead of the FQDN of the address we configured, and so the request was being rejected. ELB log exerpt:
"POST https://zipkin:443/api/v2/spans HTTP/1.1"

https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/trace/v3/zipkin.proto#config-trace-v3-zipkinconfig
shows a collector_hostname field with the following description:

(string) Optional hostname to use when sending spans to the collector_cluster. Useful for collectors that require a specific hostname. Defaults to collector_cluster above.

Here is the tracing config from one of our proxies:
"tracing": {
  "http": {
    "name": "envoy.tracers.zipkin",
    "typed_config": {
      "@type": "type.googleapis.com/envoy.config.trace.v3.ZipkinConfig",
      "collector_cluster": "zipkin",
      "collector_endpoint": "/api/v2/spans",
      "trace_id_128bit": true,
      "shared_span_context": false,
      "collector_endpoint_version": "HTTP_JSON"
    }
  }
}

As you can see, collector_hostname is not set, so I assume that from the description in the envoy docs that it will just use the collector_cluster as the hostname, which is "zipkin".
I would expect that the tracer.zipkin.address would be the hostname, or that there is a configuration option that I can use to force it to be so.
To temporarily workaround this issue, we had to configure the system ingress behind the ELB to accept a "zipkin" hostname, which feels quite odd.
Version
$ istioctl version
client version: 1.11.2
control plane version: 1.11.3
data plane version: 1.11.3 (132 proxies)

$ kubectl version --short
Client Version: v1.20.4-dirty
Server Version: v1.20.7-eks-d88609

Additional Information
No response

@jwineinger did you change the tracing address in MeshConfig

Refer to  envoy_bootstrap.json, maybe we need a PR to fix this.
you can try something as following:

use a custom bootstrap to override, see more detail here
use EnvoyFilter to applies the patch to bootstrap configuration.
use otel-collector  as a transit

@jwineinger seems this was fixed in https://github.com/istio/istio/pull/36277

Excellent. I see a PR to cherry pick it into a 1.11 release as well.  I do think we may try otel-collector anyway, because we're evaluating different trace backends and that seems to be a easy way to switch between them.

Excellent. I see a PR to cherry pick it into a 1.11 release as well. I do think we may try otel-collector anyway, because we're evaluating different trace backends and that seems to be a easy way to switch between them.

agree!
BTW, can we close the issue?


Devbox release floc 2519

This is a design for https://clusterhq.atlassian.net/browse/FLOC-2519.
The only real way to test this is to do a dev release. However I think that it can be looked at first.
This includes attempts to:

Provide instructions for installing the prerequisites which were installed in the dev box onto the host
Do all the work on the host
Remove permanent changes (e.g. use a temporary environment, don't change the git config, stop using an environment variable throughout because it might get overwritten and we don't want to write to .bashrc). These didn't matter in a temporary Vagrant box.

Once the Vagrant box is out of the way, I'd prefer the simplicity of setting the VERSION environment variable, and setting other things (the branch name) off that.  Can you explain further why this would be a problem?
The subtraction of the prefix from the branch name seems somewhat fragile (if it fails due to some change to the branch name, accidental or policy-led, the very important tagging of the release could go very wrong).

Thanks. I'd like to see the replies to these comments before pushing this forward to coding.

Once the Vagrant box is out of the way, I'd prefer the simplicity of setting the VERSION environment variable, and setting other things (the branch name) off that. Can you explain further why this would be a problem?

With the Vagrant system, we stored the environment variable to ~/.bashrc. I don't think that it is appropriate to do that here, on an engineer's host system. The reason that the environment variable was stored was that it became a pain to not store it - the release process took time, and has gaps (review, long builds etc.). Environment variables are prone to being lost across this long period of time, e.g. if the engineer closes their terminal window. Maybe we should store the version in a better way, but I don't like the environment variable only system. Maybe a file?

OK to proceed with coding

The next step is:

Do a dev release following the instructions in this branch
Change anything which comes up as an issue when doing that
Submit for review

Only one minor change suggested. Please merge once you've made it and tests pass. If fixing the tests require non-trivial changes, please bounce back for further review.

Thanks, I think that the failing builds were unrelated and hope that they will pass next time round.


Segmentation fault when using "go"

Hello, i was trying to use your chess engine to have some inspiration for mine, when i have encounter that error. I am not able to run it, since it just segfaults, i don't know much, so maybe i'm just doing something dump, but for know i'm just not able to run it due to that error. For my little knowledge i think it is failing on the reset_nnue function inside the iterative_deepening. It only works when i'm in debug mode as you can see.

Hi, if you want to search infinitely with Patricia, don't use "go", use "go infinite". Patricia doesn't know how to handle "go" by itself and honestly I didn't think that was valid UCI before today. Thanks for bringing it up to my attention.

Sorry to bother again, seems that go infinite also don't work as expected, it just works with the command "d" witch i assume to be debug mode. If the platform matters i am running it on macos

I have added some comments to debug, and that's what i have found out.

I have added some print statements to find out what is going on. I think its understandable what is happening from them. In the "add_to_all" function in the file "nnue.h" line 63 for some reason the for loop that is being performed go out of bounds, since the "offset" parameter is 755712 and the size of the "delta" array is 589824.

I apologize for my dumb mistake, I forgot to use the  "position startpos" command.


Don't use pmsocks in pcp config

Why do we need this change? :thought_balloon:
The pmlogger is using pmsocks which is needed when monitoring the systems protected by firewall. As this is local configuration this is not required, so removing this unnecessary option.
Please include the context of this change here.
Documentation update? :memo:

[ ] Yes
[ ] No

Security Checklist :lock:
Upon raising this PR please go through RedHatInsights/secure-coding-checklist
:guardsman: Checklist :dart:

[x] Bugfix
[ ] New Feature
[ ] Refactor
[ ] Unittests Added
[ ] DRY code
[ ] Dependency Added
[ ] DB Migration Added

Additional :mega:
Feel free to add any other relevant details such as links, notes, screenshots, here.

Looks good to me, regression worked fine.

Thank you @anurag03 for verifying this change. With this, merging this pull-request.


Autodetect service provider

Remove forced service provider when using Ubuntu. This caused problems when I wanted to use it on Ubuntu 16.04, which supports upstart. Don't know why this was added because the documentation says:

provider
The specific backend to use for this service resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.

Source: https://docs.puppet.com/puppet/latest/reference/type.html#service-attribute-provider

tnx ... Yeah back in the days you had to do that "manually". tnx.


yaml config is difficult

particularly private keys, which are big multiline strings.

The specific issue with private keys is covered by #225. Are there other things, or can we mark this as a duplicate?

No that's the main one, will close as dup.


A very odd crash

So im using mekanism V8.0.201
My players have suddenly started crashing after they built the Solar Evaporation Plant
they crash right when they join, or freeze and crash.
here is the crash report, it mentions cofh but im not sure where to report bugs to them, if its their problem, where should i report it?
http://pastebin.com/ezCmSckL

Report to CoFHLib - not a Mekanism issue

ok will do

i reported it to CoFH but they beleive it may be your problem too?
They said the error report is vary vague..but that is all it produces so im not really sure what todo
https://github.com/CoFH/Feedback/issues/365


I2C_BUS set to 0 instead of 1

Commit d5ad6a7
 replaces all calls to i2c functions with the hardcoded value 1 with the I2C_BUS variable. However, the variable is set to 0 by default. This currently breaks any existing installs trying to update from older versions of the software.

Thanks for the report. The commit e833c8d fixes it.

Thanks!


Make relationship discovery more flexible

Am not sure if this PR is the right way, here's what I'm trying to accomplish.
PostgreSQL supports arrays as a database type. In other words, a single column can be a an array of ints, etc. This is a much more lightweight one-to-many solution than another table with a relationship, and there are built-in operators and functions which deal with the array.
Npgsql fully supports arrays on the ADO.NET level, and I'd like to add support to the EFCore level as well. The main issue is that EFCore identifies CLR array types as relationship/navigation properties. My approach is to add an attribute [MapAsArray], which would let EFCore know to leave the property alone and let it be mapped as a "scalar" (as far as EFCore is concerned). However, RelationshipDiscoveryConvention, doesn't seem to be very extensible (most of the logic is private) - this PR makes the main DiscoverRelationships method overridable.
Does the approach seem valid? Do you foresee other issues?

@roji Does explicitly telling EF that the property is a scalar property cause it to be mapped correctly? For example, modelBuilder.Entity<Foo>().Property(e => e.MyArray); Theoretically, this should prevent the convention from treating it as a navigation.

@ajcvickers it seems like I had an issue with my type mapper implementation which caused the error. I've managed to get arrays to work although I admit I'm not sure exactly why. Basically my NpgsqlTypeMapper overrides FindMapping(Type clrType), and if no simple mapping is found, checks whether clrType is an array or generic list. If so it returns a proper mapping. Somehow this doesn't conflict with relationships, so I'm going to close this for now.
It would be good to understand though - does the relationship discovery automatically ignore properties for which a database mapping has been found?

@roji - Yes, it does.
https://github.com/aspnet/EntityFramework/blob/dev/src/Microsoft.EntityFrameworkCore.Relational/Metadata/Conventions/Internal/RelationalRelationshipDiscoveryConvention.cs has function which finds the target type for navigation. It returns null value for primitive properties and type mapper is used to determine whether a property is primitive property. Therefore as long as a CLR type can be mapped to database type by type mapper, it won't be discovered as navigation property.

Great, must have missed that. This probably means that array support isn't going to require anything special from the core.
I'm off to add scaffolding support as well. Thanks for the help!

@roji Awesome that you got it working. It would be good to know if it works with other parts of the stack--like change detection, queries, and updates. It's not something we have ever bee nable to try before, so I expect that there may be some issues.

@ajcvickers will try to do thorough testing and will let you know if I run into anything. It's really cool to see EFCore create tables with int[] etc.

@ajcvickers Thanks to @roji 's contribution, EF core works fine with arrays and npgsql. However, the InMemoryProvider seems to throw this exception:
System.InvalidOperationException: The property 'MyEntity.MyProp' could not be mapped, because it is of type 'Int32[]' which is not a supported primitive type or a valid entity type. Either explicitly map this property, or ignore it using the '[NotMapped]' attribute or by using 'EntityTypeBuilder.Ignore' in 'OnModelCreating'.
Is there anything that can be done to enable that support for InMemoryDatabase?

@alexzaytsev-newsroomly Filed #11926


Uploader metadata for xvideos-pornhub

xvideos and pornhub have uploader/channel/model-name
It would be great if youtube-dl can support it, so filename will be (uploader/channel/model-name) - (title)
thank

This is already supported.

@dstftw  but uploader - uploader_id is not working

It works for pornhub but not xvideos, it gives me NA when I use uploader, creator, uploader_id, channel. Using --write-info-json shows that it's not being pulled at all for xvideos.


fix: vscode debugger is not hitting breakpoints

Description

Testing

Additional context

Codecov Report

Merging #64 (52da2b6) into main (3751927) will decrease coverage by 1.50%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #64      +/-   ##
==========================================
- Coverage   86.78%   85.28%   -1.50%
==========================================
  Files          13       13
  Lines         401      401
  Branches       61       61
==========================================
- Hits          348      342       -6
- Misses         37       44       +7
+ Partials       16       15       -1

Flag
Coverage Δ

integration
?

unittests
85.28% <ø> (ø)

unittests-3.10
85.28% <ø> (ø)

unittests-3.11
85.28% <ø> (ø)

unittests-3.8
85.28% <ø> (ø)

unittests-3.9
85.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes


Merged main into dev 1.22 to keep in sync 22/06/2021

/cc @ashnehete @carlisia @chrisnegus @ritpanjw
Weekly branch sync done early because i didn't have time to do it last week, this also fixes the integration branch, since it has a trivial conflict.

all the toplopolgy manager related fails were fixed in the last commit in https://github.com/kubernetes/website/pull/28075 .
https://github.com/kubernetes/website/pull/28569/commits/5a5c96b2ccfc2f8114e676ecf24148465cbac800 was fixed in  https://github.com/kubernetes/website/pull/28434

/lgtm

Thanks @PI-Victor .
/approve


Add Batch Write into Milvus

Swap out the normal upload in Milvus (https://github.com/dgarnitz/vectorflow/blob/74b1f50e8784362323ea553360bc55a6bd2292b2/src/worker/vdb_upload_worker.py#L192-L216) for the batch update for faster upload.
This sample code should provide guidance - https://github.com/milvus-io/pymilvus/blob/master/examples/example_bulkinsert_json.py

Not doing this, as we have removed milvus support

@dgarnitz @david-vectorflow Hi. Updating the docs and website regarding removal of milvus support would be good. I tried setting the project up for last 3 hours without any success and finally noticed that there was no method to write embeddings to milvus

Requesting to update the docs and website accordingly.

@tvvignesh Super sorry to hear that you needed it! We were having dependency issues with Milvus and it was not being used in production by anyone so we removed it. Is there something I can do to help you get vectorflow spun up?

Hi. Thanks for the reply. After seeing lack of support for milvus in vectorflow, I removed it and am sticking to handling all the ETL in python scripts itself as of now and it works. As of now, I am good, but if you plan to support Milvus in the future, would be happy to try it out.


Documentation Fixes

There were a couple problems building our docs since the switch to sphinx-multiversion:

Images weren't showing up in rendered documents
API docstrings for the torch dataloader/column similarity op were incorrectly formated
potential issues with old versions getting picked up through sys.path includes in conf.py

rerun tests

rerun tests

rerun tests


Error New Events Report (String could not be serialized with encoding: Uniode (UTF-8))

Hi,
i tried the new events report in Traccar Manager+ and get the error "String could not be serialized with encoding: Uniode (UTF-8)!
the existing summary report works fine?
I am using latest traccar server installed on a raspberry pi connected to a mySQL database on my Synology NAS.
Barni

Hi Barni,
Screenshot please

"Summary" report works?

Yes. Summary report is fine... Checked it again right now...

try in the browser
http://localhost/api/reports/events?deviceId=ID&from=2017-11-01T00:00:00.000Z&to=2017-11-09T23:59:59.000Z
where localhost - your traccar server, ID - device id

Seems to work...

report.xlsx

Here is the API result of the summary report.
It is a json array instead of an xlsx file!
[{"deviceId":3,"deviceName":"Skoda Yeti","distance":663284.39,"averageSpeed":18.151805197845995,"maxSpeed":94.83,"spentFuel":0.0,"engineHours":0}]

Please json array events from 2017-11-01 to 2017-11-08

If i ran the .../api/reports/events... i get an excel file to download as shown above.
How do i get the JSON-Array?

You can use the program  https://www.getpostman.com

events.json.txt

Hi Uwe,
Test in new version 1.5
What's new

Animation devices move
Switch my location
Add report events attributes
Show events on map
Fix request json

I will test it and give you feedback.
Thank you so much.

Hi Sergey,
-Switch my location works fine now
-Event report also works now (No UTF8 Error)
-I can show the events also on the map. Great

The animation devices moves (i am not sure what it does) i will check while driving home and expect a trace on the map?.

Good Job. Thank you...
Barni

Thank you


Quadratic time and memory explosion for storing JSON module in filesystem cache

Bug report
What is the current behavior?
In a project with a JSON module containing a moderately sized object, using cache.type = "filesystem" causes webpack to take an enormous amount of time and memory. For example, with an object of 10000 keys, webpack takes 10 seconds and 2.5 GiB. When changing the size of the object, both time and memory appear to scale quadratically.
If the current behavior is a bug, please provide the steps to reproduce.
You can reproduce from this Gist with npm run build.
package.json
{
  "dependencies": {
    "webpack": "^5.39.1",
    "webpack-cli": "^4.7.2"
  },
  "scripts": {
    "build": "npm i && node gen.js && \\time webpack"
  }
}

gen.js
const fs = require("fs");
fs.writeFileSync("src.json", JSON.stringify({ ...[...Array(10000).keys()] }));

webpack.config.js
module.exports = {
  mode: "development",
  cache: {
    type: "filesystem",
  }
};

$ npm run build
[…]
asset main.js 137 KiB [emitted] (name: main)
./src.json 115 KiB [built] [code generated]
webpack 5.39.1 compiled successfully in 101 ms
10.86user 0.64system 0:10.66elapsed 107%CPU (0avgtext+0avgdata 2622824maxresident)k
0inputs+2896outputs (0major+652413minor)pagefaults 0swaps

What is the expected behavior?
webpack should take negligible time and memory on this project.
Other relevant information:
webpack version: 5.39.1
Node.js version: 14.17.0
Operating System: Linux

hmm yeah. I'll fix it...


[New Blueprint]: OpenJS Architect

Blueprint Name
Architect: local dev hello world SSR with Web Components
Maintainer
brianleroux
Maintainer URL
https://github.com/brianleroux
Repository Link
https://github.com/brianleroux/arc-example-hono-enhance-ssr
Description
Server-side render Web Components using HonoJS on top of API Gateway and Lambda
Infrastructure as Code (IaC) Tool
OpenJS Architect (generates AWS SAM)
CI/CD Tool
Github Actions
Programming Language
JavaScript

merged in #11


Wrong hex file generated for MCUboot

Describe the bug
When building with CONFIG_BOOTLOADER_MCUBOOT=y a empty header of image header size is generated in zephyr.hex. This empty header is not required and results in a failure of
imgtool.py to generate a correct hex file (another header will be prepended to the image).
To Reproduce
Steps to reproduce the behavior:

west build -s zephyr/samples/hello_world/ -b nrf52_pca10040
zephyr.hex (image starts at C200):

:10C000000000000000000000000000000000000030
:10C010000000000000000000000000000000000020
:10C020000000000000000000000000000000000010
:10C030000000000000000000000000000000000000
:10C0400000000000000000000000000000000000F0
:10C0500000000000000000000000000000000000E0
:10C0600000000000000000000000000000000000D0
:10C0700000000000000000000000000000000000C0
:10C0800000000000000000000000000000000000B0
:10C0900000000000000000000000000000000000A0
:10C0A0000000000000000000000000000000000090
:10C0B0000000000000000000000000000000000080
:10C0C0000000000000000000000000000000000070
:10C0D0000000000000000000000000000000000060
:10C0E0000000000000000000000000000000000050
:10C0F0000000000000000000000000000000000040
:10C10000000000000000000000000000000000002F
:10C11000000000000000000000000000000000001F
:10C12000000000000000000000000000000000000F
:10C1300000000000000000000000000000000000FF
:10C1400000000000000000000000000000000000EF
:10C1500000000000000000000000000000000000DF
:10C1600000000000000000000000000000000000CF
:10C1700000000000000000000000000000000000BF
:10C1800000000000000000000000000000000000AF
:10C19000000000000000000000000000000000009F
:10C1A000000000000000000000000000000000008F
:10C1B000000000000000000000000000000000007F
:10C1C000000000000000000000000000000000006F
:10C1D000000000000000000000000000000000005F
:10C1E000000000000000000000000000000000004F
:10C1F000000000000000000000000000000000003F
:10C20000500500207DD4000075E800000DD300002B
:10C210000DD300000DD300000DD300000DD300009E
:10C220000DD300000DD300000DD3000069CF000036
:10C230000DD300000DD3000011CF000065E8000011
:10C240003DD400003DD400003DD400003DD40000AA
:10C250003DD400003DD400003DD400003DD400009A
:10C260003DD400003DD400003DD400003DD400008A
:10C270003DD400003DD400003DD400003DD400007A
:10C280003DD400003DD400003DD400003DD400006A
:10C290003DD400003DD400003DD400003DD400005A
:10C2A0003DD400003DD400003DD400003DD400004A
:10C2B0003DD400003DD400003DD400003DD400003A
:10C2C0003DD400003DD400003DD400003DD400002A
...

Expected behavior
The header that is added should not be there zephyr.hex:
:10C20000500500207DD4000075E800000DD300002B
:10C210000DD300000DD300000DD300000DD300009E
:10C220000DD300000DD300000DD3000069CF000036
:10C230000DD300000DD3000011CF000065E8000011
:10C240003DD400003DD400003DD400003DD40000AA
:10C250003DD400003DD400003DD400003DD400009A
:10C260003DD400003DD400003DD400003DD400008A
:10C270003DD400003DD400003DD400003DD400007A
:10C280003DD400003DD400003DD400003DD400006A
:10C290003DD400003DD400003DD400003DD400005A
:10C2A0003DD400003DD400003DD400003DD400004A
:10C2B0003DD400003DD400003DD400003DD400003A
:10C2C0003DD400003DD400003DD400003DD400002A
...

Impact
imgtool.py cannot generate images using the zephyr hex file, so at the moment only bin input is allowed. Other bootloaders might have the same problem with the generated hex file.

Can you bisect to determine the commit to blame, in case this was not always wrong?

@ioannisg I can't because I don't understand what is causing the zeros to be prepended.

@nvlsianpu could you investigate this please?

Zeros at hex begin are fine - Build behaves like that since mcuboot was ported for zephyr.
0x200 bytes are reserved for image header which is added by the imgtool.py.
Be aware of this change: https://github.com/JuulLabs-OSS/mcuboot/commit/44588eff41a3f90145394cd739ffd3e993087396#diff-3b31e4a6417a485b1075e37618453979 was done in imgtool.py some time ago.
In the mean time will check whether this work as expected.

Thanks @nvlsianpu

TEXT_SECTION_OFFSET sets the offset - it is not available via menuconfig (I was not aware that it was hidden) but can be modified via adding to west build a configuration file option -- -DCONF_FILE=*.conf

Hi @nvlsianpu, I don't understand why the 0's are added, when a hex file is read by imgtool it will add an extra header (only for hex files). Would it not be simpler/easier for MCUboot config to set:
CONFIG_FLASH_LOAD_OFFSET=DT_FLASH_IMAGE0_OFFSET + 0x200
CONFIG_FLASH_LOAD_SIZE=DT_FLASH_IMAGE0_SIZE - 0x200

(Not exactly this code of course, using $(dt_hex_val, ...))
In that case it will not add anything to the generated hex file, and imgtool can do the required padding. And it is easy to extend to ram load images in future: zephyr is compiled with the correct ram location and imgtool can add the required header. Zephyr just generates the required hex file without any padding at all, and the same for the binary files.

Originally imgtool.py had been able to operate only on *.bin files., and then was extended to support *.hex file as well. TEXT_SECTION_OFFSET might be different than 0x200 for other SoC.
Probably unused part of this area need to be zeroed in order to meet image SHA.

CONFIG_FLASH_LOAD_OFFSET=DT_FLASH_IMAGE0_OFFSET + 0x200
CONFIG_FLASH_LOAD_SIZE=DT_FLASH_IMAGE0_SIZE - 0x200

That`s possible
I would not change this until it is required for feature you are developing (ques ram load images...).
Just need to be carefully while changing that.

@nvlsianpu, I know this offset might be different for other SOC, at the moment it is quite fixed in zephyr.
I will not use anything from MCUboot to support any feature I am developing. I will create a proper separate Kconfig. When I see things that are strange, or could be improved for mcuboot I am just reporting them. The way I look at mcuboot/zephyr the zephyr images generated should be as standard as possible, what is really needed is to set the load/exe offset OK (taking into account the header size and slot slot size), and that is all. It is then up to imgtool to generate a good image from this.
After this there might still be a required to offset the hex to load it into the correct slot (slot1) using nrfjprog but this I do not consider a task of imgtool.
But to get back on topic, is the generated hex file OK to be processed by imgtool ?

yes it is ok.

If the generated hex file is OK, I will close the issue.


fix: reverts private widgets feature

Description
This PR reverts the private widgets feature introduced in this PR
Fixes #10691
Fixes #10668
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Manual
Checklist:

[x] My code follows the style guidelines of this project
[x] 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 pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: fix/revert-private-widget-feature

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
54.96 (-0.04)
36.38 (-0.18)
34.86 (-0.07)
55.36 (-0.04)

:green_circle:
app/client/src/sagas/PostEvaluationSagas.ts
16.55 (0.11)
0 (0)
0 (0)
20.17 (0.17)

:red_circle:
app/client/src/sagas/WidgetOperationSagas.tsx
51.32 (-0.22)
38.54 (-0.48)
52.08 (0)
52.79 (0)

:green_circle:
app/client/src/selectors/commentsSelectors.ts
85.25 (1.64)
64.71 (2.95)
73.33 (0)
90.59 (2.35)

:red_circle:
app/client/src/utils/DSLMigrations.ts
73.33 (0.03)
63.5 (-6.06)
71.13 (0)
73.1 (0)

:red_circle:
app/client/src/utils/DynamicBindingUtils.ts
83.52 (-0.55)
69.64 (-1.79)
75.86 (0)
82.82 (-0.62)

:red_circle:
app/client/src/utils/WorkerUtil.ts
88.98 (-0.78)
70.59 (-1.96)
100 (0)
92.38 (-0.95)

:red_circle:
app/client/src/widgets/BaseWidget.tsx
73.98 (-4.88)
35.56 (-8.88)
68.75 (-6.25)
72.88 (-5.09)

:red_circle:
app/client/src/widgets/ListWidget/widget/index.tsx
61.95 (-1.39)
25.89 (-1.47)
56.86 (-1.63)
60.79 (-1.75)

:red_circle:
app/client/src/workers/DataTreeEvaluator.ts
76.26 (-0.09)
57.77 (-0.18)
72.53 (-0.59)
76.17 (-0.11)

:red_circle:
app/client/src/workers/evaluationUtils.ts
57.1 (-2.23)
53.29 (-1.62)
61.11 (-2.68)
54.81 (-2.33)

/ok-to-test sha=88077bd

/ok-to-test sha=6bbbb6e

Tested both issues on DP and both issues have been resolved
#10691
#10668


feat: package page

The title is probably too big

Filter is not working. Feel free to comment it and extract into separate ticket (or ask @KnoWabLe)

There should be `Hide` button after clicking on `Show all` button.

What do you think if we create a version popularity graph (top 5-10) on this page to make it more vibrant and beautiful?
@ctizen @KnoWabLe @zardak

Favicons should be rounded. Can you please also add some extra vertical space between websites?

What do you think if we create a version popularity graph (top 5-10) on this page to make it more vibrant and beautiful? @ctizen @KnoWabLe @zardak

https://github.com/fingerprintjs/gradejs-backend/issues/258

Can you please make fixed columns?


Reduces the verbosity of campfire command failures

Right, fixed.
Snuck in another change which removes the .env as having it auto-populate environment variables is unexpected and may lead to some inconsistent results (the classic statement of "explicit rather than implicit). I was the only one that used the file as well, as I don't think vscode auto loads .env files


colourmap change not working

Describe the bug
The colourmap feature has several issues.

[ ] the description in rose-meta needs clarifying what file format is expected. At the moment the user has no idea how a colourmap should look like #591
[ ] the description in rose meta needs clarifying if a single path to a file is expected or several entries along the lines of directory, filename
[ ] when pointing to the json file under cset-workflow/extra-meta the run crashes with the following error message:
IsADirectoryError: [Errno 21] Is a directory: '~/CSET/cset-workflow/extra-meta'
[ ] -when I point to the folder in Christine's home directory the run works.

Unfortunately we can't add it easily, as we don't know where people have CSET downloaded to. Issue #590 tracks adding a default on into the CSET package itself, which would fix this.

I did expand the help infromatiomn in rose-meta listing the relative local path to the json file. So I hope that helps.

After experiencing the same error message as Sylvia with the json file I checked that I was up-to-date on my branch and I was - there were no changes. I ran the workflow again but this time with the full directory name instead of $HOME and it worked. I have just switched back to $HOME to see if that could re-create the error, but that worked. So I have been unable to re-create the error.
To see if the error exists (or if it was slow updating for our branches) I think it would be useful to get someone else (who hasn't updated or run it since they last updated their version) to try and see if they get the same error.

Fixes with https://github.com/MetOffice/CSET/issues/590


Modeling with a defined template

Hello,
I am modeling a multimer composed of a monomer that binds to a homodimer. The monomer in solution adopts a conformation but when bound to the dimer, it suffers a big conformational change. My goal is to model the monomer in that conformation bound to the dimer.
There are structures of the monomer in solution and a homolog that is in the conformation that I am interested in. Is it possible to define a particular template with a conformation of interest to model a particular chain of a multimer? Or, is it possible to exclude templates for the prediction?
Thanks in advance for the help

This functionality should be baked into colabfold. Don't think that it is currently supported in Alphafold

Thanks for the reply!