Remove Python <3.7 support

Python 3.5 has been considered EOL since September 2020 and requests (a primary dependency) has dropped support as of 2.26.0. This removes a workaround for handling black in the CI.
Dropping support for 3.5 will allow use of some newer features, probably most visible being f-strings.

Personally, I think this needs a bit of discussion as to the timing for making this change. While I understand the 'keeping up to date' argument, I don't see any current, compelling reason that would drive SoCo to drop 3.5 support.
Note that Debian 9/Stretch has LTS support for 3.5 through to June 2022.
@KennethNielsen: any thoughts?

Agree, I wanted to get this on the radar. With requests dropping 3.5 support it seemed like a good time to start discussing.

I'm working on adding Python venv caching to the CI runs and 3.5 support is a blocker. To ensure the CI is always testing with the latest release, it's necessary to pin each library's version in requirements-dev.txt as the hash of that file is used as a cache key. However if we pin to the latest release, several of the libraries no longer support <3.6 and will fail to install. This includes requests and black, possibly others.

Note that once #857 is merged, we can rebase this PR and clean up the changes to requirements-dev.txt which the other PR introduces.

@pwt @jjlawren I think we should probably develop make a decision on what we want to with support of older version in general, so that we have that to lean on the next time this problem pops up. From my point of view, the answer is somewhere in between the things you have already discussed.
As @pwt, I would prefer the measuring stick for which version we do support to be the oldest python versions that LST distributions support in as far as that can be achieved with reasonable effort. So, personally I would be willing to compromise on it, the the burden is too high, but I too have heard of clever version pinning tools that apply to the dependencies dependencies, so if we could set one of those up and note in internal documentation, which distributions old python is limiting which dependency etc. etc. so that we would know when to update the pin, then that would be awesome. I will try and have a look at the other PRs soon.

@pwt @jjlawren I think we should probably develop make a decision on what we want to with support of older version in general, so that we have that to lean on the next time this problem pops up. From my point of view, the answer is somewhere in between the things you have already discussed.
As @pwt, I would prefer the measuring stick for which version we do support to be the oldest python versions that LST distributions support in as far as that can be achieved with reasonable effort. So, personally I would be willing to compromise on it, the the burden is too high, but I too have heard of clever version pinning tools that apply to the dependencies dependencies, so if we could set one of those up and note in internal documentation, which distributions old python is limiting which dependency etc. etc. so that we would know when to update the pin, then that would be awesome. I will try and have a look at the other PRs soon.

My (personal) position on this is that we might as well support older releases unless there's a compelling reason not to do so -- e.g., libraries on which we depend dropping support in some significant way, or language features that it's highly inconvenient to live without. It has not been onerous to maintain 3.5 support, and I'm sure it's been a service to plenty of legacy systems out there.
Having said that, once 3.5 stops receiving any security patches (June 2022), we should probably drop support to 'nudge' people into updating their systems.
I'm not really in favour of complex support matrices or elaborate version pinning. Not the best use of our energies.

Python 3.5 reached EOL over a year ago. In fact, 3.6 reached EOL a few weeks ago in Dec 2021.
The difficulty with supporting old versions is going to be more around the dependencies than the distributions. Dependencies will drop support for python versions as they reach EOL, and we'll have little control over problems caused by outdated dependencies when those arise.
As noted above, both requests and black dropped support for 3.5 a while back (and requests plans on dropping 3.6 support in 2022). Having divergent dependency versions based on distribution may become a problem over time. For example, requests may change fix a bug or change behavior, or old versions of black may format PRs differently than what our CI uses.
We already have a similar issue today as versions are not pinned and unexpected dependency upgrades lead to CI failures for things unrelated to the PR.

Python 3.5 reached EOL over a year ago. In fact, 3.6 reached EOL a few weeks ago in Dec 2021.

I'm aware of this, but note that the Debian LTS project is supporting Stretch (and Python 3.5) through to the end of June 2022.

The difficulty with supporting old versions is going to be more around the dependencies than the distributions. Dependencies will drop support for python versions as they reach EOL, and we'll have little control over problems caused by outdated dependencies when those arise.

Agree with the risk; currently hypothetical. Assess and deal with it when we encounter it?

As noted above, both requests and black dropped support for 3.5 a while back (and requests plans on dropping 3.6 support in 2022). Having divergent dependency versions based on distribution may become a problem over time. For example, requests may change fix a bug or change behavior, or old versions of black may format PRs differently than what our CI uses.

Agreed; also currently hypothetical. (Black has never supported 3.5, FWIW.)

We already have a similar issue today as versions are not pinned and unexpected dependency upgrades lead to CI failures for things unrelated to the PR.

Agreed, but this is not a version deprecation issue.
As I've alluded, I have in mind to deprecate 3.5 in June unless there's a significant cost we're incurring in the meantime.

Agreed it's not causing any critical issues now and June is a reasonable goal. The biggest benefits I see from dropping 3.5 would be:

Allowing us to have a clean set of pinned dependencies. Right now we'll have this mess while 3.5 is around: https://github.com/SoCo/SoCo/pull/857/files
Ability to use new Python features, like f-strings in 3.6.

I just reviewed #857 to see what the current state of dependencies looks like. As of right now, flake8, pylint, pytest, and requests no longer support 3.5 and we're using outdated versions of those on the CI for the 3.5 tests.

If we're aligning with Debian LTS support timelines, then we should be able to remove both 3.5 and 3.6 support in when Debian 9 ("Stretch") LTS support ends on June 30, 2022. The next LTS release will be based on Debian 10 ("Buster") which comes packaged with 3.7.

I'm in agreement with dropping 3.5 support for the upcoming v0.28 release, but also dropping 3.6 requires further discussion, at least from my point of view.

The latest release of requests has officially dropped support for py36: https://github.com/psf/requests/releases/tag/v2.28.0

The latest release of requests has officially dropped support for py36: https://github.com/psf/requests/releases/tag/v2.28.0

Meaning that folks using 3.6 will not get requests updates. Everyone else will. SoCo will keep working, at least for the time being.
I will shortly release v0.28. This PR will be included if it is restricted to removing Python 3.5 support. Otherwise, it won't be included.

I'll revert the 3.6 removal for now.

CI failures are from a new unpinned pylint version and are addressed here: https://github.com/SoCo/SoCo/pull/916.

I'll revert the 3.6 removal for now.

Thanks for doing that. Let's discuss 3.6 removal for the a future release.
My general philosophy, FWIW, is that we shouldn't unnecessarily inconvenience SoCo users unless we have solid engineering reasons to do so.


kubectl certificate deny should have clear output

What happened:
I am trying to create a csr. Using the command kubectl certificate deny <csr name> it had an output certificatesigningrequest.certificates.k8s.io/my-svc.my-namespace approved. This becomes confusing at times.
What you expected to happen:
I would expect it to have a clear output, something like "certificatesigningrequest.certificates.k8s.io/my-svc.my-namespace denied."
How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:
Environment:

Kubernetes client and server versions (use kubectl version): v1.18.0
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release): Ubuntu

duplicated https://github.com/kubernetes/kubernetes/issues/91876#issuecomment-641533097

@knight42 Thanks for pointing out


Cookie consent Plugin is missing

Hi
I searched few minutes, but could not find a cookie consent plugin or any function in this direction.
I think that this is a necessary feature, no mater if solved with a plugin or build-in solution.
Thanks in advance
Best regards

Hi @TechArea,
I don't really see the need for a cookie consent plugin as WonderCMS doesn't use any cookies for "normal" visits. Only when you, as admin, log in a cookie is created.
But, since I do think this is something that can come in handy if you use cookies, I created a quick plugin for displaying a simple cookie message.
You can find the github repo here: https://github.com/StephanStanisic/addon-cookie-message/
(It is for WonderCMS 3.0.0)
Example can be found here: https://demo1.wonder.stanisic.nl

@StephanStanisic, awesome of you for explaining and providing a solution. Much appreciated and welcome! )
Thank you!


Empty "page" breaks search

If you don't specify a "page" when creating a new redirect, the search filter in django admin will throw an error.
Here's the traceback:
Traceback (most recent call last):
File "/some/path//lib/python2.6/site-packages/django/core/handlers/base.py", line 100, in get_response
response = callback(request, _callback_args, *_callback_kwargs)
File "/some/path//lib/python2.6/site-packages/django/contrib/admin/options.py", line 288, in wrapper
return self.admin_site.admin_view(view)(_args, *_kwargs)
File "/some/path//lib/python2.6/site-packages/django/utils/decorators.py", line 76, in _wrapped_view
response = view_func(request, _args, *_kwargs)
File "/some/path//lib/python2.6/site-packages/django/views/decorators/cache.py", line 78, in _wrapped_view_func
response = view_func(request, _args, *_kwargs)
File "/some/path//lib/python2.6/site-packages/django/contrib/admin/sites.py", line 190, in inner
return view(request, _args, *_kwargs)
File "/some/path//lib/python2.6/site-packages/django/utils/decorators.py", line 21, in _wrapper
return decorator(bound_func)(_args, *_kwargs)
File "/some/path//lib/python2.6/site-packages/django/utils/decorators.py", line 76, in _wrapped_view
response = view_func(request, _args, *_kwargs)
File "/some/path//lib/python2.6/site-packages/django/utils/decorators.py", line 17, in bound_func
return func(self, _args2, *_kwargs2)
File "/some/path//lib/python2.6/site-packages/django/contrib/admin/options.py", line 1026, in changelist_view
self.date_hierarchy, self.search_fields, self.list_select_related, self.list_per_page, self.list_editable, self)
File "/some/path//lib/python2.6/site-packages/django/contrib/admin/views/main.py", line 64, in init
self.query_set = self.get_query_set()
File "/some/path//lib/python2.6/site-packages/django/contrib/admin/views/main.py", line 244, in get_query_set
qs = qs.filter(reduce(operator.or_, or_queries))
File "/some/path//lib/python2.6/site-packages/django/db/models/query.py", line 561, in filter
return self._filter_or_exclude(False, _args, *_kwargs)
File "/some/path//lib/python2.6/site-packages/django/db/models/query.py", line 579, in _filter_or_exclude
clone.query.add_q(Q(_args, *_kwargs))
File "/some/path//lib/python2.6/site-packages/django/db/models/sql/query.py", line 1167, in add_q
self.add_q(child, used_aliases, force_having=force_having)
File "/some/path//lib/python2.6/site-packages/django/db/models/sql/query.py", line 1170, in add_q
can_reuse=used_aliases, force_having=force_having)
File "/some/path//lib/python2.6/site-packages/django/db/models/sql/query.py", line 1105, in add_filter
connector)
File "/some/path//lib/python2.6/site-packages/django/db/models/sql/where.py", line 67, in add
value = obj.prepare(lookup_type, value)
File "/some/path//lib/python2.6/site-packages/django/db/models/sql/where.py", line 316, in prepare
return self.field.get_prep_lookup(lookup_type, value)
File "/some/path//lib/python2.6/site-packages/django/db/models/fields/related.py", line 139, in get_prep_lookup
raise TypeError("Related Field has invalid lookup: %s" % lookup_type)
TypeError: Related Field has invalid lookup: icontains

One solution would be to use 'page__title_set__title' in the search fields.

I fixed it in my fork and will create a pull request for it.
https://github.com/ableton-web/django-cms-redirects/commit/5abbcd80721567d0402966a04c8343088715b70d

Closing this issue due to its age.


wip: magic endpoint for executing stuff on all namespaces

SUPER HEAVY DRAFT/EXPERIMENT
Don't even bother reviewing, just posting my loose experiments for transparency and bus factor prevention

Rebased successfully on top of LRU code for namespaces:
$ curl -sH 'Content-Type: application/json' \
  -d '{"sql": "select libsql_server_namespace_name()"}' localhost:9090/v1/execute_on_all \
  | jq '.[].results.rows.[].[]'
"another_1"
"another_10"
"another_11"
"another_5"
"another_6"
"another_8"
"another_9"
"another_3"
"another_7"
"another_2"
"another_4"
"another_12"

Freshly rebased and made the inner code work with SQL batches; also, I fixed the error paths which used to produce incorrect jsons.

Added a test case

The pull request has conflicts and has not been updated for a while. Please feel free to open a new one if you wish to submit this for merging.


broken due to removed dependency

Since https://github.com/jfhbrook/node-ecstatic/issues/255 the version ~0.4.5 of ecstatic has been removed from the repositories, breaking testling:
$ npm install testling
npm WARN deprecated<EMAIL_ADDRESS>use [cross-spawn](https://github.com/IndigoUnited/node-cross-spawn) or [cross-spawn-async](https://github.com/IndigoUnited/node-cross-spawn-async) instead.
npm ERR! Linux 4.15.0-48-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "testling"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2

npm ERR! No compatible version found<EMAIL_ADDRESS>npm ERR! Valid install targets:
npm ERR! 4.1.2, 3.3.2, 2.2.2
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /home/da/nodemerda/npm-debug.log

npm restored all the removed versions, so everything should be ok again: https://github.com/jfhbrook/node-ecstatic/issues/255#issuecomment-489259794


WIP: SwxSOC cdf investigation

Change Summary
This is a first draft pass of using the SWXSOC CDF style of attribute generation. This actually doesn't depend on their code, and more rewrites part of it to pull out the common pieces. Ideally, I would want to put this in its own repo, perhaps in the LASP repository, so both us and the Hermes team could make improvements to it. But this is just a proof of concept for now.
Overview

This mostly works with the MAG L1A RAW CDF files, with some minor fixes to the way the variable bases work still needed.
There is also a mismatch between the global schema provided by HERMES and the added global attrs we have, but I think that will be easy to fix.
New Dependencies

Added the HERMES-SOC as a dependency, but it's not really needed
This still requires some coordination with the HERMES team - I think ideally I would pull the shared pieces out into a different repo, give them credit, and then if they wanted, they could replace the duplicate pieces in their repo with the library. Still an open question where that repo should live, who should maintain, etc - LMK thoughts!

Does this give us metadata validation as well as the schema?
I'm wondering if there is an easy way to go from spreadsheet -> this yaml format -> code. I'm guessing there is and we'd just need to update the PR I opened.
One thing that worries me here is the complexity this adds versus a straight dictionary lookup. Could we have the classes inherit from MutableMapping to make them dict-like? Or am I missing another reason for why we want to use the extra functions to access the metadata.

Does this give us metadata validation as well as the schema?

It validates against the schema but the current version of the code does not do validation beyond that.

I'm wondering if there is an easy way to go from spreadsheet -> this yaml format -> code. I'm guessing there is and we'd just need to update the PR I opened.

Yes, I think so, if we decided to go that way. I have further thoughts that I'll bring up in the meeting

One thing that worries me here is the complexity this adds versus a straight dictionary lookup. Could we have the classes inherit from MutableMapping to make them dict-like? Or am I missing another reason for why we want to use the extra functions to access the metadata.

This was just personal style from me, I think having a dictionary lookup would make a lot of sense too now that I have actually finished. It was just a level of abstraction in case I wanted to add something in between class creation and retrieval.

Re: Excel sheet, my strong preference would be for us to use the YAML files as the source of truth and use them to generate both the code and the spreadsheets for discussion. So we would edit the YAML files, but we could still use spreadsheets for discussions. I feel like if we invite edits from external people, there's a good chance they would (inadvertently) make a breaking change to the format and we would need to edit/verify everything carefully anyway. But, this is a discussion for our meeting about this.

One other thing that I'm not completely following is the organization/nesting of global/variable attributes. What does "global" mean, I think it is actually "dataset" in this context, or is there different levels of "global".

Here, "global" refers to global file attributes. In xarray, this would be Dataset attributes. "variable" refers to everything else - in xarray, DataArray level attributes. There are multiple "global" values because there is a distinction between project specific and instrument or level specific attributes - but all global values are eventually put in the same level at the dataset.

Would it make sense to do more nesting within the yaml files themselves rather than within the Python code with the load_global and load_variable?

Unfortunately you can't alias/anchor across different files. We either need to have multiple files and do some legwork in the code to combine them, duplicate mission level attributes, or have one massive file for everything. I'd prefer to have the code combine the files. Tim brought up moving some of the instrument attributes into the level attributes using aliases though, which is possible because it's in the same file.

pre-commit.ci autofix


Add getting users playlist like getting users tracks aka .getMyPlaylists()

Spotify now has an endpoint available to get a users playlists directly at "/v1/me/playlists". See more information here.
This would keep us from having to query .getMe() just to retrieve the Id and then having to use getPlaylistsForUser(user.userId())

Will be part of version 2 on which I'm currently working.

Added in bd1599b.

Version 2.0.0-RC1 was just released.


Update specs2-core to 5.4.2

About this PR
📦 Updates org.specs2:specs2-core from 5.0.7 to 5.4.2
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2", artifactId = "specs2-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.specs2", artifactId = "specs2-core" }
}]

labels: test-library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #234.


Clean up : update webgl cropAndResize code for readability

While reading the code, I've noticed x and y was switched in src/kernels/webgl/crop_and_resize_gpu.ts.
For readability, i suggest to use x for width/right/left and y for height/top/bottom parameters.

This change is

RC = RowColumn and CR = ColumnRow

Ok, now i understand why this x <-> y switch was not a problem !
I have updated it anyway, to make it easier for other newbies like me :-)


Add docs about creating a patch release branch

The goal of adding this doc is so that this repo can have a documented process for this.
In theory with that process laid out for everyone to follow we can continue merging PRs to HEAD branches during r/r freeze with more confidence. And this could potentially allow us more time/flexibility to address the renovate PRs.
Warning
Before we execute on this practice across all our maintained branches we will first need to:

Edit GHA workflows to allow tests/ci to run based on any release/* (or similar) branch regex,
Sync all workflows to older branches via backport.

Eventually we can still adjust how we manage workflows in this repo if that's desired. Since we've been discussing some methods of keeping the workflows in sync across all branches more easily. (Automatic backports, orphan branch of canonical workflows, dedicated workflow repo etc)

Just a quick overview to make sure I understand the process proposed here:

In a code freeze we of course do not want to merge new code into the release branch. E.g. release/v5.0.
But sometimes urgent patches are needed.
For that, we create a new branch from release/v5.0 as described in this new doc and merge the desired change into it.
A patch release is made from this new branch.
When code freeze is over, the change is also merged into the main (release/v5.0) release branch.

Is that correct? If not, maybe we can add some extra context into these docs for them to be useful to newcomers to the project who do not yet understand the process very well.

Just a quick overview to make sure I understand the process proposed here:

In a code freeze we of course do not want to merge new code into the release branch. E.g. release/v5.0.
But sometimes urgent patches are needed.
For that, we create a new branch from release/v5.0 as described in this new doc and merge the desired change into it.
A patch release is made from this new branch.
When code freeze is over, the change is also merged into the main (release/v5.0) release branch.

Is that correct? If not, maybe we can add some extra context into these docs for them to be useful to newcomers to the project who do not yet understand the process very well.

It's actually kind of the opposite of this 😓 mostly.
The idea here being that we should keep working on release/5.0 even if r/r is in a freeze. So we will do that. My impression from recent discussion is that r/r is technically the only thing in freeze.
Repos like ours can follow that freeze, but don't need to strictly. It is however a lot easier to follow the freeze, since working during it needs a process like this in place. And this would roughly be that process to enable us to "branch back in time" and create a clean working slate equivalent to the version we need to patch.

LGTM


413 Request Entity Too Large nginx/1.25.1 (File stash)

File size: 700MB
File Typ: Mkv
I tried to upload the same file using a telegram bot where I received error as:  ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
Files upto 100MB is uploaded successfully

Hi, thanks for using it. I have tried uploading a file of around 800MB with both CLI and WebDAV, and it worked without issue. Can you please share the WebDAV client you were using? Also, you can test with the following command and let me know if it works
tgfs cmd cp [local file path] /


68 code clean up

Changes

Splits code into modules
Separate error handling from functions
Removed unused functions
General code-clean-up

Only small clarifying questions, could be added as comments in the code for others.


:new:usr Added a folder for Vis with Realtime D3 Vis

:new:usr Added a folder for Vis with Realtime D3 Vis

Aproving, but please, use the correct gitchangelog labels: "new: usr: ..." instread of ":new:usr..."
For more information on the format: https://github.com/vaab/gitchangelog/blob/master/.gitchangelog.rc


Adds pagination

Hi @OwenRay, is this PR related to this issue? https://github.com/Bardavon-Health/actions-aws-ssm-params-to-env/issues/56
If so, I'd like to merge it to a fork of this repo I made, to increase the speed of updates.
I decided to fork (again) the repo and release an updated version of the GitHub action here<EMAIL_ADDRESS>I'd like to merge your changes as well in the next release, what do you think?
Meanwhile I'm trying to contact one of the maintainers (@chough-bardavon) to ask him if it's possible for me to maintain this repo, so we can use the official one and not a fork.

Hi @dennybiasiolli
it's related to that indeed.
Feel free to merge it to your branche.
would be nice to have an up-to-date official version indeed, hopefully @chough-bardavon  will respond on that.

Hi @OwenRay, they included me as a collaborator in this repository, so I can help them check pull requests and merge things 😉
Can you please rebase your pull request here on top of the last commit on branch master?
After that I will be happy to merge this pull request and release an updated version 🎉

@OwenRay :pray:


[GHSA-f626-677r-j5vq] Nette Database SQL injection

Updates

Affected products

Comments
mentioned code in https://github.com/CSIRTTrizna/CVE-2024-55586 does not check user input, I think it is not responsibility of framework to check user input
CVE should be revoked!

a970a46b06869b991ffe0c1f6d166e4f2f3e9c39

Hey @calvera, the cve was assigned by mitre so if you want it to be revoked you'll need to contact them at https://cveform.mitre.org/
https://nvd.nist.gov/vuln/detail/CVE-2024-55586
It looks like the link you shared is dead which might support the cause for a revocation with mitre. It seems that the project itself is also discussing the issue
https://github.com/nette/database/issues/314
Please attempt to reach out to mitre and let me know how that goes on this thread. 👍

@calvera sorry for the delay, but we've gone ahead and withdrawn this advisory. See: https://github.com/github/advisory-database/pull/5079 for more of the context on the delay 🙇


config: Remove obsolete items from the config template file.

What problem does this PR solve?
Problem Summary: Some configs are deleted in the past months, but these items are not deleted from config-template.toml, which is a mistake and confuses readers.
What is changed and how it works?
What's Changed: This PR deleted these config items from config-template that are actually already deleted.
Related changes

Need to cherry-pick to the release branch

I think this PR should be cherry-picked to 5.0 since people may try to confirm the configs by reading the config template from code.

Check List
Tests

Unit test

Release note

No release note

/merge


Add conflict between AdjustableModPanel and JanitorsCloset

A functional conflict has been discovered between these two mods, see:
https://forum.kerbalspaceprogram.com/index.php?/topic/207263-112x-adjustable-mod-panel-kamp-v15990-adoption-edition-09-apr-2022/&do=findComment&comment=4128958

Janitor's Closet can be installed alongside Adjustable Mod Panel (AMP) - only use ONE or the other to manage buttons.

Meanwhile @linuxgurugamer has taken a different approach:
https://forum.kerbalspaceprogram.com/index.php?/topic/147463-112x-end-your-parts-list-nightmare-introducing-the-janitors-closet/

Can you guys discuss and hopefully agree on how this should be presented? If LGG wants a conflict marked and zer0Kerbal wants no conflict, we can't satisfy both parties.

@linuxgurugamer seems to be sticking with incompatibility. Merging conflict...


test: Minimal test suite to run against node RPC to check for breaks over the wire

We need something ASAP that's minimal and covers the most important endpoints at first, and then spreads to 100% coverage of the API. We do not need the canonical API workstream to get this done, we can already do it now.
Spin up a node instance in docker and some separate sidecar-like program that uses node's API over RPC and ensures they're all working normally.
Run a mock tendermint node as well so the cel-node has something to point at for data, we need to test writes as well.

Or let's maybe look at using knuu for this as a first step.

Yeah I think this should be paired with knuu work i.e. and should ideally use raw JSON RPC queries

Well, this is what Swamp tests were for that were supposed to be run over RPC client instead of direct API calls, but iirc Ryan never had a chance to finish those.
On the raw RPC @cmwaters. There is no need for that and it will only complicate things.
We have interface and both server and client are autogenerated for it via reflection. If we make tests over the interface and ensure that those tests run over RPC client for every method, then all such breakages are gonna be detected without hussles of raw json

And this is a duplicate of https://github.com/celestiaorg/celestia-node/issues/2337 fwiw

Sure, I just want to make sure that we can guarantee that clients in other languages can use the API as expected. Raw can mean using generated interfaces if that sufficiently covers it


Angular 12

Would it be possible to bump angular to version 12?

@drozhzhin-n-e is this repository still active and will be updated to Angular 12?

interesting to have this update as well please

I'm interested in this update too.

It works fine here on ng12 and 13. What exactly is the problem?

i managed to install it with --force on angular 12 and works fine

When using with ng13, npm gives the following warnings:-
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

When using with Angular 13, npm gives the following warnings:-
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

https://github.com/across-the-stars/ngx-pinch-zoom/commit/b888a61ff1be0c0855b644c8283bebf51940ec6f
Someone updated to Angular 12.
https://github.com/across-the-stars/ngx-pinch-zoom

Seems now with latest Angular I cannot get rid of "Uncaught Error: Type PinchZoomModule does not have 'ɵmod' property." TSCC does not run/compile it properly.

Seems now with latest Angular I cannot get rid of "Uncaught Error: Type PinchZoomModule does not have 'ɵmod' property." TSCC does not run/compile it properly.

same.

Seems now with latest Angular I cannot get rid of "Uncaught Error: Type PinchZoomModule does not have 'ɵmod' property." TSCC does not run/compile it properly.

Same

Seems now with latest Angular I cannot get rid of "Uncaught Error: Type PinchZoomModule does not have 'ɵmod' property." TSCC does not run/compile it properly.

how did you solve this?

Deinstall and use instructions to STRG+/- 😅 ... we are using a JS Vanilla lib instead


[BUG]prvProcessICMPMessage_IPv6() sends replies to the wrong Endpoint

Describe the bug
As as already discussed in #1064, I found the same type of issue when handling ICMPv6 ND packets.
Target

ALL

To Reproduce
In my test setup I have two network interfaces. One has an IPv6 Endpoint and is connected to my PC.  At this stage, My PC has no problem pinging the first interface by it's link-local IPv6 address.
The issue arises when I configure an IPv6 link-local Endpoint on the second interface. As soon as I do that, I'm no longer able to ping the first interface from my PC.
What happens is, the PC sends a Neighbor Solicitation packet to the first interface, FreeRTOS+TCP receives it and sends the response out the second interface.
The problematic piece of code is: HERE
As was the case in #1064, we are searching for an endpoint when we already have a known good one.
Changing
NetworkEndPoint_t * pxEndPointFound = FreeRTOS_FindEndPointOnIP_IPv6( &( pxICMPHeader_IPv6->xIPv6Address ) );

to
NetworkEndPoint_t * pxEndPointFound = pxNetworkBuffer->pxEndPoint;

fixes the issue but I haven't fully examined the problem and the fix. This was just a quick 30min. debugging session and sadly I have to move on.
rant-mode-on....
I keep finding these small little issues and it is starting to feel like FreeRTOS+TCP might need some kind of a review of the general approach to how Endpoints are handled. When do we search for endpoints vs when do we trust the endpoint that is already selected. When we search for endpoint, do we just search based on address/netmask/prefix or do we need to also consider the network interface? The deeper I dig, the more these questions pop up. I don't want to water down this specific issue, but I have another similar endpoint-related issue in the pipeline and it again involves one of these "FindEndpointXXXXX" functions. Something just doesn't feel right. The deeper I dig into +TCP, the more weird issues keep popping up and to be honest, I don't feel completely comfortable with the solutions that I'm proposing. This code has been written by people that have a lot more experience than me and I don't believe I'm competent enough to correct their decisions, but at the same time, I have a job to do and a device that needs to work properly, so I have to fix these issue. And if I don't push my changes upstream, I end up with too many changes that I need to rebase every time "main" pushes forward.
Please excuse the rant above but I needed to share my frustration.
FreeRTOS+TCP is amazing and I love working with it and on it. The IPv6 functionality is a literal life saver for me and I really really really want it to work properly.
Thanks for your time.

Thanks for the bug report. Our team will take a look.

Thanks @evpopov for bringing this out. We are looking into the same and will get back on this soon.
Thanks,
Shub

Hi @evpopov , as you suggested we can use the endpoint of the NetworkBuffer to to map to the correct Link Local endpoint. Will you be creating a change or we can also create one. Please suggest.

@shubnil This on seems pretty straight-forward. I'll create a PR. I will appreciate any help from the team if it fails the CI tests


Excalidraw theme issue

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
6.1.11
Describe the bug
From my experience, the issues raised in #427 and #491 are not fully resolved. Would it be possible to add an option to the theme to not affect Excalidraw at all?
I love the minimal theme... but the way it handles Excalidraw styling interferes with the dark/light mode switch in Excalidraw. See this screenshot as an example.

I use Obsidian in dark mode, but I frequently draw on a light canvas in Excalidraw. This is not supported by the minimal theme.
I am planning to add the Alternative Dark mode demonstrated in this video to the core Excalidraw plugin package, but the script is overridden by the Minimal Theme settings. Since Minimal Theme is so popular, I'm concerned that the alternative dark mode will not work for many of my users.
If I clean excalidraw from the theme, dark/light mode switch works as expected, and so does the alternative dark mode script.
https://user-images.githubusercontent.com/14358394/205512474-ed2b0f17-bfe4-4a6b-8947-99c5f04fa51e.mp4
Debug info
SYSTEM INFO:
Obsidian version: v1.1.0
Installer version: v1.0.3
Operating system: Windows 10 Home 10.0.22621
Login status: logged in
Catalyst license: supporter
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: Minimal v6.1.11
Snippets enabled: 1
Restricted mode: off
Plugins installed: 56
Plugins enabled: 17
1: Dataview v0.5.47
2: Map View v2.2.0
3: Obsidian42 - BRAT v0.6.36
4: Obsidian42 - Jump-to-Date v1.0.14
5: Obsidian42 - WordNet Dictionary v2.0.1
6: Recent Files v1.3.3
7: Hot Reload v0.1.9
8: Custom Frames v2.4.4
9: ExcaliBrain v0.1.16
10: Customizable Page Header and Title Bar v4.7.1
11: Kanban v1.5.1
12: Advanced Tables v0.17.3
13: Banners v1.3.3
14: Templater v1.16.0
15: Pane Relief v0.4.1
16: Excalidraw v1.8.2
17: Minimal Theme Settings v6.1.0
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

The problem I see is that there are too many levels of override happening. There is a cleaner way to solve this within Excalidraw plugin itself:

Use Obsidian's default theme variables instead of custom colors. This way Excalidraw will automatically respond to themes instead of forcing theme developers to create custom rules for Excalidraw
Use the .theme-light and .theme-dark variables on the Excalidraw container itself, so that the variable definitions get passed in

Doing these two things would enable me to completely remove any Excalidraw styling in Minimal

Unfortunately, changing the Excalidraw component's css because of Obsidian is unlikely to succeed. Even smaller Obsidian specific changes are resisted by the Excalidraw product team... Obsidian is just one of many use-cases. I have to cook with what's out of the box in Excalidraw.
I also don't think the Excalidraw theme should necessarily follow the dark/light theme setting of Obsidian, but rather of the drawing being edited. I for one, always use Obsidian in dark mode, but most of my drawings have a lighter background. In the plugin settings the user can fine tune the canvas color settings (i.e. to match or not the Obsidian theme)


메시지 큐 정리

https://12bme.tistory.com/176
https://shortstories.gitbooks.io/studybook/content/message_queue_c815_b9ac.html
https://docs.aws.amazon.com/ko_kr/AWSSimpleQueueService/latest/SQSDeveloperGuide/welcome.html


[R-289] better support for ollama models

ref

Handle large context windows using Ollama's LLMs for evaluation purpose · Issue #1120 · explodinggradients/ragas

feats

check how good ollama models are performing
context window issue, need to throw and error if that is the case
make a documentation and see if you can figure out a PR?

From SyncLinear.com | R-289

user report from discord

My use case is for evaluation currently, but I am encountering issues. Using llama3.1 (also tried with instruct) I only get the following as output:
Failed to parse output. Returning None.
Also tried the 70b model, but then something breaks in Ollama then. I get time=2024-08-06T20:17:22.069+02:00 level=DEBUG source=server.go:572 msg="server unhealthy" error="server not responding" in Ollama logs.

@jjmachan , I have tried to solve this issue, I have changed the wait time to some higher value like some 300 keeping the workers same. I have was able to generate the score now. There are NaN values for some metrics but we were able to get the score for certain metrics. So its the issue with models i guess, The model is having some good inference time and the model couldn't generate the score within the time frame.
embed = OllamaEmbeddings(model="llama3") llm_model = Ollama(model="llama3") evaluator_llm = LangchainLLMWrapper(llm_model) evaluator_embeddings = LangchainEmbeddingsWrapper(embed) result = evaluate(hf_dataset,metrics=[context_precision,faithfulness,answer_relevancy,context_recall,],embeddings=embed,llm=llm_model,run_config=RunConfig(max_workers=3,timeout=240,))
I hope this would help


Would it be helpful to provide a PR that ports KaTeX to TypeScript?

Before requesting a feature, please search for existing issues.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like:
A clear and concise description of what you want to happen.
Link to or name of a (La)TeX package that provides the same feature:
KaTeX's general goal is to render as LaTeX does.
Describe alternatives you've considered:
A clear and concise description of any alternative solutions or features you've considered.
Additional context:
Add any other context or screenshots about the feature request here.

Hi.  I am interested in contributing to KaTeX but would find it easier to work with the project if it were in TypeScript.  If the team is already planning to use TypeScript, I can volunteer to do the port.

@steveluc We currently use Flow for type checking. I'm not an expert on TypeScript but at a high level they look pretty similar. I'm not aware of any plans to move to TypeScript.
P.S. Including a template but not actually filling it out isn't very helpful...

@steveluc there's quite a bit of overlap between flow and typescript.  I'm curious what parts of using typescript would make KaTeX easier to work on.


Cannot read property 'format' of null

Hello,
I have the following error when execute ICS: Import events.
Maybe because spanish format date?
Uncaught (in promise) TypeError: Cannot read property 'format' of null
at Object.callback (eval at  (app.js:1), :18:6409)
at SR (app.js:1)
at e.onChooseItem (app.js:1)
at e.onChooseSuggestion (app.js:1)
at e.selectSuggestion (app.js:1)
at t.useSelectedItem (app.js:1)
at t.onSuggestionClick (app.js:1)
at HTMLDivElement.s (app.js:1)
callback @ VM236:18
SR @ app.js:1
e.onChooseItem @ app.js:1
e.onChooseSuggestion @ app.js:1
e.selectSuggestion @ app.js:1
t.useSelectedItem @ app.js:1
t.onSuggestionClick @ app.js:1
s @ app.js:1

This happens when the filename is not in format YYYY-MM-DD


Add terradoc

Recreated README with terradoc, checked documentation for errors or inconsistencies.

Are the badges correct?

@kassianh feel free to merge your PR :)


Fixed docs link to Rust's demand-driven compilation guide

This PR fixes the link to Rust's guide on demand-driven compilation, which has changed location.

@swift-ci smoke test

@swift-ci smoke test Linux


New property ShowMarkers on Line Series

Resolution for issue https://github.com/radzenhq/radzen-blazor/issues/1229

Hi @paulo-rico,
Markers are controlled by their own tag. This functionality should be implemented as a Visible property of <RadzenMarkers />


Support for MSVS 2022

Trying to use this action with the just added "windows-2022" environment (see https://github.com/actions/virtual-environments/issues/3949) doesn't work, msbuild is not found. It would be nice if it could be updated to support the latest version. TIA!

Do you have a repo you can share with the settings you are using? Or just the default? I think this may be due to needing -prerelease available...which is #45 which I need to merge...

Yes, as long as the user didn't specify their own conflicting vs-version input.

I think this may be due to needing -prerelease available...which is #45 which I need to merge...

Just noticed that you've merged it and using it does allow the action to find MSBuild in this environment, thanks! There are other problems in my builds, but they're unrelated to this action, so I think this issue can be closed now.
Thanks again!

Awesome, thank you for confirming


No Roles from keycloak

Did you every experienced issues that the roles of a user weren't handed over the Nexus?

Not yet until now. You can give more details, maybe I can find some clues to fix it.

we have to explizit set the client roles for each user.
Composition on realm role level isn't working.
So we have overall admins, which should have also admin access to nexus. Let's call this group platform-admin In nexus we have a mapping role nexus-admin which is read from a client role app-admin in the nexus client
If I say in the roles definition for platform-admin it's including app-admin of the nexus client it's not working for all users. But if I assign all users to app-admin role of the nexus client it's working

I think this isn't an error or bug, it's working as the expected.
As you know, until now, Nexus can only see the client roles which are defined for the nexus client in Keycloak, and the role platform-admin will be unkown to Nexus.
So the user who is assigned platform-admin role but isn't assigned app-admin will not have the nexus-admin role.
For now, the better way is to assign the nexus's client role to every user. And I am thinking about how to support the realm roles, but it's not very clear, and I have to find some free time to do that :-(


Notifications not available in headless mode

Puppeteer version: 1.8.0
Platform / OS version: Windows 8.1
Node.js version: v10.11.0

What steps will reproduce the problem?
Assuming there is a registered serviceworker and a notification:
const puppeteer = require('puppeteer');

(async() => {
    const browser = await puppeteer.launch({
        headless: true
    });

    const context = browser.defaultBrowserContext();
    const page = await context.newPage();

    await page.goto('https://notificationDomain.com', {
        waitUntil: "networkidle2"
    });

    const notifications = await page.evaluate(() => {
        return navigator.serviceWorker.ready.then(function(registration) {
            return registration.getNotifications().then(function(notifications) {
                return notifications;
            })
        })
    });

    console.log(notifications.length + ' Notifications');
    await browser.close();
})();

What is the expected result?
The notifications array should contain the notification like it does when using the non-headless mode.
What happens instead?
The notifications array is empty although there is a notification.

Is this expected behavior? Any help is appreciated.

@paul-kl can you please try enabling "notifications" using browserContext.overridePermissions?

@aslushnikov I'm sorry, forgot that in my example but used it in my code. I hope this helps:
const puppeteer = require('puppeteer');

(async() => {
    const browser = await puppeteer.launch({
        headless: false
    });

    const domain = 'https://puush.pw'
    const context = browser.defaultBrowserContext();
    const page = await context.newPage();

    await context.overridePermissions(domain, ['notifications']);

    try {
       await context.overridePermissions(domain, ['push']);
    } catch (e) {
       // workaround because 'push' throws unknown permisson type but works anyways
    }

    await page.goto('https://puush.pw', {
        waitUntil: "networkidle2"
    });

    // Wait for the SW
    await page.waitFor(1*5000);

    const sw = await page.evaluate(() => {
      return navigator.serviceWorker.getRegistrations().then(registrations => {
        return registrations && registrations.length > 0 ? true : false;
      })
    })

    // Give me time to send the push notification
    await page.waitFor(1*15000);
    console.log('Push check...');

    if(sw){
      const notifications = await page.evaluate(() => {
          return navigator.serviceWorker.ready.then(function(registration) {
              return registration.getNotifications().then(function(notifications) {
                  return notifications;
              })
          })
      });

      console.log(notifications.length + ' Notifications');
    } else {
      console.log('SW not registered!');
    }

    await browser.close();
})();

Output non-headless:
Push check...
0 Notifications

or when I did send one (onesignal.com service running on the domain)
Push check...
1 Notifications

Output headless:
Push check...
SW not registered!

The serviceworker won't register.  There is something strange about the 'push' permission but once I added it, I was able to recive push notifications, not just normal ones.

Hi, you can click on the notification or get data from the onclick method?

I think my previous results aren't accurate because I wasn't able to receive notifications again with the 'push' permission. I did some more testing:
Normal notifications and overridePermissions 'notifications' work fine.
If push notifications are requested and overridePermissions 'push' is set, the 'Allow'/'Deny' dialog pops up, so it isn't working. If I press 'Allow' by hand, close the browsers and run the profile again, I'm able to receive push notifications.
Headless won't take the headful profile where push was accepted (or any profile at all, nothing happens) so I couldn't test the profile in headless.
If I use a headless instace without a profile I can't get any service worker output while I'm able to get servicer worker output in headful (without hitting 'Allow', like in my example above).
@reznikGit in headful mode you can dump the notification data. Not sure about handling the onclick method.

@aslushnikov do you think you could add push and (better?) SW coverage in the near future? If not, is it possible to handle the push notifications with the dev protocol?

"is it possible to handle the push notifications with the dev protocol?" 🤔

Is there any plan to go on working on this?

I am facing the exact same issue as posted by @paul-kl today. It will be great if this can be fixed

I am still facing the same problem.

The issue got resolved in the latest versions using the new default headless mode:


[QA] Color changing lights are not working on Seed scene

Explorer Alpha build versions:

v0.13.0
v0.15.0
v0.16.0

Issue Description:

On Seed scene /goto -104,-95 the selection of color changing lights is not working. You cannot see the lights as in current Unity Render.
STR:

Go to the top floor of the scene
Open the button menu
Turn on the Color changing lights option

Expected behaviour:
The lights change color
Current behaviour:
There are no lights on scene
Evidence:
ALPHA
https://github.com/user-attachments/assets/af1faad8-095b-4b67-bdf8-33449e68a007
RENDER
https://github.com/user-attachments/assets/84f174f5-b946-42b0-97e7-1137de6b4352
Additional Notes:

The lights and stars are working fine in editor but not in the build :S In build they directly don't exist :S
Unity Editor
https://github.com/user-attachments/assets/e72cab72-cd53-4508-917f-7253a513fc00
Windows Build
https://github.com/user-attachments/assets/fc1a9e65-e98b-420f-bab7-01cb8882bf4a

Fixed in the PR https://github.com/decentraland/unity-explorer/pull/1658


Support "-" for X-Forwarded-Proto log for Gorouter

Whenever X-Forwarded-Proto header is "-" the log cannot be parsed.
Example:
   Code(
        "-\" x_forwarded_proto:\"-\" vcap_request_id:\"eb922abf-0f2d-4042-4a84-9161e6ee17a1\" response_time:0.000108962 app_id:\"-\" app_index:\"-\" x_b3_traceid:\"81aa595b268bbe68\" x_b3_spanid:\"81aa595b268bbe68\" x_b3_parentspanid:\"-\" b3:\"81aa595b268bbe68-81aa595b268bbe68\"",
        Tag,
    ),

for
<IP_ADDRESS>:80 - [2019-10-31T00:11:09.329+0000] "GET / HTTP/1.1" 404 0 69 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36" "<IP_ADDRESS>:36539" "-" x_forwarded_for:"-" x_forwarded_proto:"-" vcap_request_id:"eb922abf-0f2d-4042-4a84-9161e6ee17a1" response_time:0.000108962 app_id:"-" app_index:"-" x_b3_traceid:"81aa595b268bbe68" x_b3_spanid:"81aa595b268bbe68" x_b3_parentspanid:"-" b3:"81aa595b268bbe68-81aa595b268bbe68"

OK, thanks for the heads up. I think I can fix this one pretty easy. Will keep you posted.

When I get a chance to fix #2 I'll push out a new release.


dataset is missing?

In evaluation.py you wrote
from dataset.camvid import CamVid, CamVidWithFlow
from dataset.cityscapes import CityScapes, CityScapesWithFlow

but there's no dataset folder in the repo.

Thanks for pointing this out. It has been updated.

I'm going to close this issue. Welcome to star this repo if you find it helpful.


Exception of type 'System.OutOfMemoryException' was thrown.

I am getting out of memory exception when calling function ExportToMemoryStream(ms) for large database?
Here is my code,
GC.Collect();
using (MySqlConnection con = new MySqlConnection(conBuilder.ToString()))
{
 using (MySqlCommand cmd = new MySqlCommand())
  {
   using (MySqlBackup mb = new MySqlBackup(cmd))
    {
     mb.ExportInfo.AddCreateDatabase = False;
     mb.ExportInfo.ExportTableStructure = True;
     mb.ExportInfo.ExportProcedures = True;
     mb.ExportInfo.ExportFunctions = True;
     mb.ExportInfo.ExportTriggers = True;
     mb.ExportInfo.ExportViews = True;

     cmd.Connection = con;
     con.Open();
     MemoryStream ms = new MemoryStream();
     mb.ExportToMemoryStream(ms); // ERROR: at this Out of Memory //
     ms.Position = 0;
     MemoryStream mszip = new MemoryStream();
     using (GZipStream zip = new GZipStream(mszip, CompressionMode.Compress, true))
      {
       byte[] buffer = ms.ToArray();
       zip.Write(buffer, 0, buffer.Length);
       zip.Flush();
       }
       mszip.Position = 0;
       // Client.PutObject('myflename.dump.Gzip',mszip);
       con.Close();
      }
     }
     con.Close();
    }

Yupe, that's the limitation of exporting to memory stream.
Try export it to a physical file.

Exporting it to a physical file when the database is very large is also throwing below exceptions, Is there any way to tell mb.Export.. to include all tables but exclude this list of tables?

Fatal error encountered during data read.
Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

If the timeout is caused by MySQL connection, then you can increase the duration of the connection timeout by adding the following connection string option:
ConnectionTimeout=15

The length of time (in seconds) to wait for a connection to the server before terminating the attempt and generating an error. Source: https://dev.mysql.com/doc/connector-net/en/connector-net-connection-options.html
Example:
server=localhost;user=root;pwd=1234;database=test;ConnectionTimeout=300;

If the timeout is caused by ASP.NET connection timeout, increase the connection timeout of ASP.NET.
If you are developing in WinForm or WPF desktop app, try execute MySqlBackup.NET on another separate thread, such as by using BackgroundWorker.

Include or excluding tables, you can refer this wiki page:
https://github.com/MySqlBackupNET/MySqlBackup.Net/wiki/Conditional-Rows-Export-for-Each-Table

Thank You for the quick response,
There is no errors on import of .sql file, but in my case i have a large database so using GZipStream compressed.
I downloaded MySQL backupup file(.gz) and trying to import into new database, but I am getting below error when importing into new MySQL database( i am using SQLyog). I posted my code in the question.
Error Code: 1064 - You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '?' at line 1

MySqlBackup.NET is not used for MariaDB.

It seems like MySqlBackup.Net is working fine for MariaDB as well. For import .sql is working very well but .gz import is not working, getting Error Code: 1064 ( I tried import using SQLyog)

.gz is a compressed file. Just like a .zip file. I believe you need to decompressed the file for MySqlBackup.NET to understand the content.

Same throw here but the issue comes when importing from File Blob seems to have an issue not freing memory. Anybody can help?
private void BTN_Restore_Click(object sender, EventArgs e)
{
MiConexion.Open();
if (MiConexion.State == ConnectionState.Open)
{
using (MiConexion)
{
using (MySqlCommand MiComando = new MySqlCommand())
{
using (MySqlBackup MiBackup = new MySqlBackup(MiComando))
{
MiComando.Connection = MiConexion;
MiBackup.ImportFromFile(@"C:\Templ\Bakckup.sql");
MiConexion.Close();
}
}
}
}

Are you using the latest the version of MySqlBackup.net?
In the latest version, the memory is clear immediately after executing every single SQL query.
If the problem still exists, this might be caused by the blob size. The blob data's length is too long to be handle by .NET Language.

V2.0.12 for NetFwk 4.6.1 seem to worked properly.
Thank you!

Hi, can you try the following setup:
1st, make your program to be compiled in x64 bit binary.
2nd, at the app.config, add the following:
<configuration>
  <runtime>
    <gcAllowVeryLargeObjects enabled="true" />
  </runtime>
</configuration>


Update Golang Dependencies

Accounting, Checkout, and Product Catalog Services need update from 1.10-1.11 to 1.16 per #916

Hi, @austinlparker I want to work on this one.

All yours!


fix: apply SQL in redshift timeout

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary
(describe what this merge request does)
Delegate creating schema for applications to stepFunctions
Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[x] add new test cases
[ ] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

add end-to-end tests results, including creating a new stack and updating existing stack


Enable upgrade of Kubernetes clusters with master VMs using managed disks

Introduction of Kubernetes master VMs to start using managed disks both for OS and etcddisk broke upgrade operation:
Upgrade operation was supported on unmanaged disks only and making manageddisk the default StorageProfile broke upgrade operation OOB.
Switch to using managed disk also started using a default disk name to be assigned by Disk RP (vs. one assigned by ACS Engine like for other resources). This could be problematic in many ways:

With main one being relying on and understanding DiskRP’s naming convention to discover the right etcd disk for each master VM. This might not be a big issue in the RP because disk names/ids can be saved in the database but from ACS Engine standpoint for operations to be idempotent disk names need to be deterministic.

This also adds unnecessary complexity of loading and editing the template during upgrade with the disk name generated by Disk RP.

This issue tracks:

Enabling upgrade operation on Kubernetes clusters with master VMs using managed disks
Fix etcddisk to use deterministic unique names instead of auto generated names assigned by DiskRP

PR #1008


Use client setting for max_frame size

It appears that currently the major browsers do not set the max frame size in the settings, but it seems that we should take them up on larger frame sizes if they are willing to handle them.

[approve ci clang-analyzer]

[approve ci clang-format]

Nice catch. This is what we're missing. Does this improve performance when client set the setting?
Also, I'm wondering if we should use the value from the client naively. When the client says 2^24-1 (the maximum value), do we really allow to create 16MB data frame?

SETTINGS_MAX_FRAME_SIZE (0x5):  Indicates the size of the largest
frame payload that the sender is willing to receive, in octets.
 The initial value is 2^14 (16,384) octets.  The value advertised
 by an endpoint MUST be between this initial value and the maximum
 allowed frame size (2^24-1 or 16,777,215 octets), inclusive.
 Values outside this range MUST be treated as a connection error
 (Section 5.4.1) of type PROTOCOL_ERROR.

[approve ci auformat]

[approve ci autest]

[approve ci clang-format]

Moving out to 9.1.x

Agreed if we take their value, we should have another max possible setting to limit how much we are willing to open things up.

Closing this for now.  Sounds like we need to take a more nuanced approach

Since #6337 removed the concerning buffer, maybe we can do this now?


Synthesis failed for Genomics

Hello! Autosynth couldn't regenerate Genomics. :broken_heart:
Here's the output from running synth.py:
2020-06-06 06:00:51,946 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-06 06:00:52,767 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-06 06:00:52,770 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-06 06:00:52,773 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-06 06:00:52,775 autosynth [DEBUG] > Running: git config push.default simple
2020-06-06 06:00:52,778 autosynth [DEBUG] > Running: git branch -f autosynth-genomics
2020-06-06 06:00:52,781 autosynth [DEBUG] > Running: git checkout autosynth-genomics
Switched to branch 'autosynth-genomics'
2020-06-06 06:00:53,164 autosynth [INFO] > Running synthtool
2020-06-06 06:00:53,164 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/genomics/synth.metadata', 'synth.py', '--']
2020-06-06 06:00:53,166 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/genomics/synth.metadata synth.py -- Genomics
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-06 06:00:53,387 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-genomics
nothing to commit, working tree clean
2020-06-06 06:00:55,307 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmp3wfuqyp9/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Genomics
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmp3wfuqyp9/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Genomics
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

13:01:28.961 [info]  FETCHING: https://genomics.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

13:01:29.274 [info]  FETCHING: https://genomics.googleapis.com/$discovery/rest?version=v1

13:01:29.320 [info]  FOUND: https://genomics.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200507, new=20200519, generating=true
Creating leading directories
Writing CancelOperationRequest to clients/genomics/lib/google_api/genomics/v1/model/cancel_operation_request.ex.
Writing ComputeEngine to clients/genomics/lib/google_api/genomics/v1/model/compute_engine.ex.
Writing ContainerKilledEvent to clients/genomics/lib/google_api/genomics/v1/model/container_killed_event.ex.
Writing ContainerStartedEvent to clients/genomics/lib/google_api/genomics/v1/model/container_started_event.ex.
Writing ContainerStoppedEvent to clients/genomics/lib/google_api/genomics/v1/model/container_stopped_event.ex.
Writing DelayedEvent to clients/genomics/lib/google_api/genomics/v1/model/delayed_event.ex.
Writing Empty to clients/genomics/lib/google_api/genomics/v1/model/empty.ex.
Writing Event to clients/genomics/lib/google_api/genomics/v1/model/event.ex.
Writing FailedEvent to clients/genomics/lib/google_api/genomics/v1/model/failed_event.ex.
Writing ListOperationsResponse to clients/genomics/lib/google_api/genomics/v1/model/list_operations_response.ex.
Writing Operation to clients/genomics/lib/google_api/genomics/v1/model/operation.ex.
Writing OperationEvent to clients/genomics/lib/google_api/genomics/v1/model/operation_event.ex.
Writing OperationMetadata to clients/genomics/lib/google_api/genomics/v1/model/operation_metadata.ex.
Writing PullStartedEvent to clients/genomics/lib/google_api/genomics/v1/model/pull_started_event.ex.
Writing PullStoppedEvent to clients/genomics/lib/google_api/genomics/v1/model/pull_stopped_event.ex.
Writing RunPipelineResponse to clients/genomics/lib/google_api/genomics/v1/model/run_pipeline_response.ex.
Writing RuntimeMetadata to clients/genomics/lib/google_api/genomics/v1/model/runtime_metadata.ex.
Writing Status to clients/genomics/lib/google_api/genomics/v1/model/status.ex.
Writing UnexpectedExitStatusEvent to clients/genomics/lib/google_api/genomics/v1/model/unexpected_exit_status_event.ex.
Writing WorkerAssignedEvent to clients/genomics/lib/google_api/genomics/v1/model/worker_assigned_event.ex.
Writing WorkerReleasedEvent to clients/genomics/lib/google_api/genomics/v1/model/worker_released_event.ex.
Writing Operations to clients/genomics/lib/google_api/genomics/v1/api/operations.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

13:01:29.695 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-06 06:01:32,725 synthtool [DEBUG] > Wrote metadata to clients/genomics/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/genomics/synth.metadata.
2020-06-06 06:01:32,754 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth is still having trouble generating Genomics. :sob:
Here's the output from running synth.py:
2020-06-07 05:54:42,007 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-07 05:54:42,787 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-07 05:54:42,790 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-07 05:54:42,793 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-07 05:54:42,795 autosynth [DEBUG] > Running: git config push.default simple
2020-06-07 05:54:42,798 autosynth [DEBUG] > Running: git branch -f autosynth-genomics
2020-06-07 05:54:42,801 autosynth [DEBUG] > Running: git checkout autosynth-genomics
Switched to branch 'autosynth-genomics'
2020-06-07 05:54:43,067 autosynth [INFO] > Running synthtool
2020-06-07 05:54:43,068 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/genomics/synth.metadata', 'synth.py', '--']
2020-06-07 05:54:43,070 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/genomics/synth.metadata synth.py -- Genomics
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-07 05:54:43,282 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-genomics
nothing to commit, working tree clean
2020-06-07 05:54:45,149 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpk1kktwll/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Genomics
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpk1kktwll/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Genomics
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:55:14.722 [info]  FETCHING: https://genomics.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:55:15.034 [info]  FETCHING: https://genomics.googleapis.com/$discovery/rest?version=v1

12:55:15.079 [info]  FOUND: https://genomics.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200507, new=20200519, generating=true
Creating leading directories
Writing CancelOperationRequest to clients/genomics/lib/google_api/genomics/v1/model/cancel_operation_request.ex.
Writing ComputeEngine to clients/genomics/lib/google_api/genomics/v1/model/compute_engine.ex.
Writing ContainerKilledEvent to clients/genomics/lib/google_api/genomics/v1/model/container_killed_event.ex.
Writing ContainerStartedEvent to clients/genomics/lib/google_api/genomics/v1/model/container_started_event.ex.
Writing ContainerStoppedEvent to clients/genomics/lib/google_api/genomics/v1/model/container_stopped_event.ex.
Writing DelayedEvent to clients/genomics/lib/google_api/genomics/v1/model/delayed_event.ex.
Writing Empty to clients/genomics/lib/google_api/genomics/v1/model/empty.ex.
Writing Event to clients/genomics/lib/google_api/genomics/v1/model/event.ex.
Writing FailedEvent to clients/genomics/lib/google_api/genomics/v1/model/failed_event.ex.
Writing ListOperationsResponse to clients/genomics/lib/google_api/genomics/v1/model/list_operations_response.ex.
Writing Operation to clients/genomics/lib/google_api/genomics/v1/model/operation.ex.
Writing OperationEvent to clients/genomics/lib/google_api/genomics/v1/model/operation_event.ex.
Writing OperationMetadata to clients/genomics/lib/google_api/genomics/v1/model/operation_metadata.ex.
Writing PullStartedEvent to clients/genomics/lib/google_api/genomics/v1/model/pull_started_event.ex.
Writing PullStoppedEvent to clients/genomics/lib/google_api/genomics/v1/model/pull_stopped_event.ex.
Writing RunPipelineResponse to clients/genomics/lib/google_api/genomics/v1/model/run_pipeline_response.ex.
Writing RuntimeMetadata to clients/genomics/lib/google_api/genomics/v1/model/runtime_metadata.ex.
Writing Status to clients/genomics/lib/google_api/genomics/v1/model/status.ex.
Writing UnexpectedExitStatusEvent to clients/genomics/lib/google_api/genomics/v1/model/unexpected_exit_status_event.ex.
Writing WorkerAssignedEvent to clients/genomics/lib/google_api/genomics/v1/model/worker_assigned_event.ex.
Writing WorkerReleasedEvent to clients/genomics/lib/google_api/genomics/v1/model/worker_released_event.ex.
Writing Operations to clients/genomics/lib/google_api/genomics/v1/api/operations.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:55:15.440 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-07 05:55:18,503 synthtool [DEBUG] > Wrote metadata to clients/genomics/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/genomics/synth.metadata.
2020-06-07 05:55:18,526 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth is still having trouble generating Genomics. :sob:
Here's the output from running synth.py:
2020-06-08 05:55:10,151 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-08 05:55:10,982 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-08 05:55:10,985 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-08 05:55:10,988 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-08 05:55:10,991 autosynth [DEBUG] > Running: git config push.default simple
2020-06-08 05:55:10,994 autosynth [DEBUG] > Running: git branch -f autosynth-genomics
2020-06-08 05:55:10,997 autosynth [DEBUG] > Running: git checkout autosynth-genomics
Switched to branch 'autosynth-genomics'
2020-06-08 05:55:11,238 autosynth [INFO] > Running synthtool
2020-06-08 05:55:11,238 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/genomics/synth.metadata', 'synth.py', '--']
2020-06-08 05:55:11,240 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/genomics/synth.metadata synth.py -- Genomics
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-08 05:55:11,442 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-genomics
nothing to commit, working tree clean
2020-06-08 05:55:12,907 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpbieafr1m/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Genomics
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpbieafr1m/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Genomics
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:55:44.623 [info]  FETCHING: https://genomics.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:55:44.934 [info]  FETCHING: https://genomics.googleapis.com/$discovery/rest?version=v1

12:55:44.983 [info]  FOUND: https://genomics.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200507, new=20200519, generating=true
Creating leading directories
Writing CancelOperationRequest to clients/genomics/lib/google_api/genomics/v1/model/cancel_operation_request.ex.
Writing ComputeEngine to clients/genomics/lib/google_api/genomics/v1/model/compute_engine.ex.
Writing ContainerKilledEvent to clients/genomics/lib/google_api/genomics/v1/model/container_killed_event.ex.
Writing ContainerStartedEvent to clients/genomics/lib/google_api/genomics/v1/model/container_started_event.ex.
Writing ContainerStoppedEvent to clients/genomics/lib/google_api/genomics/v1/model/container_stopped_event.ex.
Writing DelayedEvent to clients/genomics/lib/google_api/genomics/v1/model/delayed_event.ex.
Writing Empty to clients/genomics/lib/google_api/genomics/v1/model/empty.ex.
Writing Event to clients/genomics/lib/google_api/genomics/v1/model/event.ex.
Writing FailedEvent to clients/genomics/lib/google_api/genomics/v1/model/failed_event.ex.
Writing ListOperationsResponse to clients/genomics/lib/google_api/genomics/v1/model/list_operations_response.ex.
Writing Operation to clients/genomics/lib/google_api/genomics/v1/model/operation.ex.
Writing OperationEvent to clients/genomics/lib/google_api/genomics/v1/model/operation_event.ex.
Writing OperationMetadata to clients/genomics/lib/google_api/genomics/v1/model/operation_metadata.ex.
Writing PullStartedEvent to clients/genomics/lib/google_api/genomics/v1/model/pull_started_event.ex.
Writing PullStoppedEvent to clients/genomics/lib/google_api/genomics/v1/model/pull_stopped_event.ex.
Writing RunPipelineResponse to clients/genomics/lib/google_api/genomics/v1/model/run_pipeline_response.ex.
Writing RuntimeMetadata to clients/genomics/lib/google_api/genomics/v1/model/runtime_metadata.ex.
Writing Status to clients/genomics/lib/google_api/genomics/v1/model/status.ex.
Writing UnexpectedExitStatusEvent to clients/genomics/lib/google_api/genomics/v1/model/unexpected_exit_status_event.ex.
Writing WorkerAssignedEvent to clients/genomics/lib/google_api/genomics/v1/model/worker_assigned_event.ex.
Writing WorkerReleasedEvent to clients/genomics/lib/google_api/genomics/v1/model/worker_released_event.ex.
Writing Operations to clients/genomics/lib/google_api/genomics/v1/api/operations.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:55:45.358 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-08 05:55:47,928 synthtool [DEBUG] > Wrote metadata to clients/genomics/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/genomics/synth.metadata.
2020-06-08 05:55:47,956 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


refactor(kafka-utils): Use generic topic name instead of creating new for each tenant

Purpose
Use generic topic name instead of creating new for each tenant
Approach
Reuse KafkaUtils and respective method for topic name creation from folio-service-tools module
Changes Checklist

[ ] API Changes: Document any API paths, methods, request or response bodies changed, added, or removed.
[ ] Database Schema Changes: Indicate any database schema changes and their impact. Confirm that migration scripts were created.
[ ] Interface Version Changes: Indicate any changes to interface versions.
[ ] Interface Dependencies: Document added or removed dependencies.
[ ] Permissions: Document any changes to permissions.
[ ] Logging: Confirm that logging is appropriately handled.
[ ] Unit Testing: Confirm that changed classes were covered by unit tests.
[ ] Integration Testing: Confirm that changed logic was covered by integration tests.
[ ] Manual Testing: Confirm that changes were tested on local or dev environment.
[ ] NEWS: Confirm that the NEWS file is updated with relevant information about the changes made in this pull request.

Related Issues
MODELINKS-213

News


Add CallFunctionArgsN

AFAIK, it wasn't possible to call a func from go code, which has exactly 3, or more than 4 args. This change adds a function "CallFunctionArgsN", which allows calling a function with any number of args.

Varargs/slices/maps only heap-allocate if they really need to. A lot of the time, the compiler can figure out that they can just be stack-allocated.
Here is an example that shows that fixed args, varargs and slices don't allocate any memory in simple cases (CallFunctionArgsN should also be such a simple case):
https://go.dev/play/p/Nb9uZK40aqc


DRILL-5033: Query on JSON That Has Null as Value For Each Key

DRILL-5033: Query on JSON That Has Null as Value For Each Key
Description
Drill returns same result with or without store.json.all_text_mode=true
Note that each key in the JSON has null as its value.
[root@cent01 null_eq_joins]# cat right_all_nulls.json
{
"intKey" : null,
"bgintKey": null,
"strKey": null,
"boolKey": null,
"fltKey": null,
"dblKey": null,
"timKey": null,
"dtKey": null,
"tmstmpKey": null,
"intrvldyKey": null,
"intrvlyrKey": null
}

Querying the above JSON file results in null as query result.
We should see each of the keys in the JSON as a column in query result.
And in each column the value should be a null value.
Current behavior does not look right.
0: jdbc:drill:schema=dfs.tmp> select * from `right_all_nulls.json`;
+-------+
|   *   |
+-------+
| null  |
+-------+
1 row selected (0.313 seconds)

Documentation
(Please describe user-visible changes similar to what should appear in the Drill documentation.)
Testing
(Please describe how this PR has been tested.)

I copied the JIRA into the PR description.

@vvysotskyi My attempt to deal with this bug is just a quick workaround since the solution as stated by @cgivre might just be the setting of the schema, of the dataset to query, from the start (which requires non trivial updates to the code).

@unical1988
You actually don't have to modify the code to get this data to read properly.  As I mentioned on the user group, the easiest way would probably be to provide a schema.  The good news is that you can do this at query time.  Take a look here: https://drill.apache.org/docs/plugin-configuration-basics/#specifying-the-schema-as-table-function-parameter
An example query might be:
select * from table(dfs.tmp.`file.json`(
schema => 'inline=(col0 varchar, col1 date properties {`drill.format` = `yyyy-MM-dd`})
properties {`drill.strict` = `false`}'))

Thanks @cgivre for the clarification, but suppose the assumption that considering nulls as strings would solve the issue, were the changes i made (over the class JSONReader.java) adequate (should the methods be changed as i did)? i see that some tests didn't pass.

Thanks @cgivre for the clarification, but suppose the assumption that considering nulls as strings would solve the issue, were the changes i made (over the class JSONReader.java) adequate (should the methods be changed as i did)? i see that some tests didn't pass.

For us to merge a pull request, all the unit tests have to pass.  (Or be modified with an explanation of why they are being modified)  Drill is a very complex beast with a lot of dependencies so even small changes can break things you didn't intend to.  Believe me... I know from experience ;-)
One other thing to note is that there is another option drill.exec.functions.cast_empty_string_to_null.  Setting this to true forces empty strings to be treated as null.  This can have some unintended side effects,  but might also help you out.

I'm going to close this PR.  If there is any objection, we can revisit.


convert should read the config, and respect its output option

#770 defaults --output to . It would be nicer to default to docs/ (or the root if specified in the config), so users can start preview/build faster without having to figure out this option.

Retitled and redesigned: I think it should take the --config option (which defaults to observablehq.config.{ts,js} in the current working directory) and then respect the output option in the config, which defaults to docs. So if you have a different output set, --output will default to that. And maybe we don’t bother reading the config if you specify --output explicitly.


swift-inspect: clean up some of the code in WindowsRemoteProcess

Add some vertical whitespace to the code ejection process.  Alter the logic to clean up the memory allocation first, ignoring the error as the subsequent run will perform a new allocation and this will leak a fixed amount of memory without interrupting the process or use of the tool. No longer check the exit code of the thread as that is always guaranteed to be 0 as the module unloading path does not report any error code in the injected code (DLL).
Use the opportunity to do some simple renaming to improve the readability and create an overload for avoiding unnecessary ceremony around use of a shared constant.

@swift-ci please test

@swift-ci please test

@swift-ci please build toolchain Windows platform

@swift-ci please test

@swift-ci please test Windows platform


Use in Objective C project

Hi there! I have problems with using the delegate.
I added "use_frameworks!" in my pod file and imported library "@import KDEAudioPlayer;"
When I added property "@property (strong, nonatomic) AudioPlayer *internalPlayer;"
And it was OK.
I can use AudioPlayer methods such as "playItem" or "removeItemAtIndex" and so on, but with delegate a have an error "Cannot find protocol declaration for 'AudioPlayerDelegate'".
Maybe I did something wrong?

Hi,
I haven't really tested the integration of this lib in an Objective-C project.
This error seems to be related to the AudioPlayerDelegate that is not obj-c compatible. I'll see what I can do.
Keep you posted.

Thank you! I am looking forward to news

Hi! Are there any changes?

Hi!
This is on the TODO list but I still haven't work on that yet. Thing is some types currently used are not objc compatible so some one them require full re-work.


video_to_pose: command not found

Followed the instructions on the Readme, installed the library and then tried running the video_to_pose command, only for it to be "not found".
conda create -n pose-format pip
conda activate pose-format
python -m pip install pose-format
$ video_to_pose
video_to_pose: command not found

Perhaps it might be a legacy item from the deprecated https://github.com/sign-language-processing/transcription? Which does have a folder/module of that name.

creating an env for https://github.com/sign-language-processing/transcription seems to confirm that when you install that it does indeed contain such a video_to_pose command

Aha! that works! Now I get "no module named 'cv2'" but of course you can solve that with python -m pip install opencv-python

... and python -m pip install mediapipe

Thanks for confirming.
Yes, they are in dev dependencies because they are not needed for just using pose files, and opencv is a very large library (ideally, just loading and saving files should be very lightweight)
Perhaps we can improve the error messages in the future

It gives me an AttributeError when I try the following:
videos_to_poses --format mediapipe --directory path/to/my/directory

@SalsabilRefaei that feature was introduced in Python 3.9, perhaps that's the issue? Also we could probably discuss that in a different thread, this error doesn't seem related to the "command not found" one in this thread
Article about removesuffix: https://www.geeksforgeeks.org/python-string-removesuffix/

I see in the image that your Python version is 3.7, so that's probably it.

Tried testing/replicating, but Python 3.7 is so old that I can't figure out how to install it in Google Colab at all, sorry

Nevermind, got it running. See https://colab.research.google.com/drive/18vwjnjM29EAb3KaH5Y7wq3sxBDys-HCE?usp=sharing. That was indeed the issue.
I recommend looking into something like virtualenv aor miniconda so you can switch Python versions easily. https://docs.conda.io/projects/miniconda/en/latest/index.html

@SalsabilRefaei I am curious how you installed pose-format? Because I would have expected pip to check the Python version and make an error

@SalsabilRefaei I am curious how you installed pose-format? Because I would have expected pip to check the Python version and make an error

I used pip .I did not have any problem, it works fine.

Ah, then perhaps we should add a check to prevent it from installing without Python 3.9 or later.


Remove wallet types from coin selection test suite.

Issue Numbers
Epic: ADP-1448 (Coin Selection Type Generalization: Part 1)
Tasks: ADP-1527, ADP-1528, ADP-1529, ADP-1530, ADP-1531.
Summary
This PR adjusts the following modules:

CoinSelection.InternalSpec
CoinSelection.Internal.BalanceSpec
CoinSelection.Internal.CollateralSpec
Primitive.Types.UTxOIndexSpec
Primitive.Types.UTxOSelectionSpec

Within these modules, we remove all usages of the following types:

Primitive.Types.Address
Primitive.Types.TxIn
Primitive.Types.TxOut

To achieve this, we replace our dependency on WalletSelectionContext with a new TestSelectionContext:
- instance SelectionContext WalletSelectionContext where
-     type Address WalletSelectionContext = W.Address
-     type UTxO    WalletSelectionContext = W.WalletUTxO
+ instance SelectionContext TestSelectionContext where
+     type Address TestSelectionContext = TestAddress
+     type UTxO    TestSelectionContext = TestUTxO

From the point of view of the coin selection algorithm, the actual concrete types used for Address ctx and UTxO ctx are not important: it's only important that these types have Ord, Show, and Buildable instances. For the test suite, it's also important that these types have Arbitrary and CoArbitrary instances.
With that in mind, we define types TestAddress and TestUTxO in terms of the Quid (quasi-unique identifier) type, which provides support for deriving all these instances automatically:
newtype TestAddress = TestAddress (Hexadecimal Quid)
    deriving (Arbitrary, CoArbitrary) via Quid
    deriving Buildable via Pretty TestAddress
    deriving stock (Eq, Ord, Read, Show)

newtype TestUTxO = TestUTxO (Hexadecimal Quid)
    deriving (Arbitrary, CoArbitrary) via Quid
    deriving Buildable via Pretty TestUTxO
    deriving stock (Eq, Ord, Read, Show)

The Arbitrary instance for Quid generates values of a length that is governed by the QuickCheck size parameter. By adjusting the size parameter, we can control the level of "uniqueness" of generated Quid values, and the frequency of collisions:

Choosing a lower value for the size parameter results in less uniqueness, and a higher rate of collisions.
Choosing a higher value for the size parameter results in more uniqueness, and a lower rate of collisions.

For some properties, a certain level of collisions is desirable. In many cases we can satisfy our coverage checks just by adjusting the QC size parameter.

The Hydra build should be fixed by this PR: https://github.com/input-output-hk/cardano-wallet/pull/3203

bors r+


[1.20.1] Parts of all create items disappear when using iris mod

Describe the Bug
My package only used iris and sodium, fabric api, and the latest build1143 create of 1.20.1. After entering the world, when entering another dimension or leaving these items, you will find that some of them are invisible when you come back .If you break them and place them again, they will return to their original state, but they will still become invisible when you come back after leaving
Reproduction Steps
1.Download the latest build 1143, sodium, iris
2.Create a new world, place a create item, such as a baler
3.Exit the world or go to another dimension and back
...
Expected Result
i thought it could be normal .
Screenshots and Videos

Crash Report or Log
No response
Operating System
Window11
Mod Version
0.5.1d
Minecraft Version
1.20.1
Other Mods
No response
Additional Context
No response

#1039