Introducing internal methods

This PR introduces static dispatch in which the implementation of a polymorphic operation is selected at compile-time. A new visibility modifer called internal is introduced. Methods marked as internal are only visible to the extension, this allows the compiler to generate direct C-calls to these methods instead of using the dynamic dispatch method in the PHP userland that sometimes is slow.
Internal methods are not visible by PHP, this means that a PHP script cannot call these methods. They aren't visible by the PHP reflection system and backtraces do not show these methods as part of the stack, also, some functions like func_get_args() and func_num_args() do not work in these kind of methods.
In the other hand, internal methods are really fast, for instance doing a recursive fibonacci vs plain php:
class McallInternal
{
    internal function fibonacci(long n) -> long
    {
        if n == 1 || n == 2 {
            return 1;
        }
        return this->fibonacci(n - 1) + this->fibonacci(n - 2);
    }

    public function callFibonacci(long n) -> long
    {
        return this->fibonacci(n);
    }
}

<?php

class Math
{
    function fibonacci($n)
    {
        if ($n == 1 || $n == 2) {
                return 1;
        }
        return $this->fibonacci($n - 1) + $this->fibonacci($n - 2);
    }
}

$t = microtime(true);
(new Test\Mcallinternal)->callFibonacci(31);
echo 'Zephir: ', microtime(true) - $t, PHP_EOL;

$t = microtime(true);
(new Math)->fibonacci(31);
echo 'PHP 5.6: ', microtime(true) - $t, PHP_EOL;

Results:
Zephir: 0.12126803398132
PHP 5.6: 0.613104820251464

Zephir: 0.12285614013672
PHP 5.6: 0.55841708183289

4.5/5x 450%/500% improvement

I think this can also be implemented later in properties

:+1:

:+1:

:+1:

:+1:

Could it be possible to introduce internal classes? @andresgutierrez


Backstories, translation?

The main problem is, that all vanilla backstories in the assests, so they can't be translated into other languages. Can it be done in CCL?

No less than they could before.

I have a question about translation : can we translate the Def folder ?

It would be better to use the language folder with the proper def injection.  We'd really love it if people volunteered to translate CCL into their own native language (or second language if you have a high proficiency).  Feel free to go ahead and do so, submitting a pull request (dev branch) and we'll be sure to include it and give full credit for the translations!

@ForsakenShell i'll try to explain better in french if you don't mind.
@MossieuLeblanc  Je me permet d'intervenir brièvement. ce qu'il veux dire c'est que tu clones tous le repo CCL. Ensuite sur ton pc tu te règles/positionnes bien sur la branche Développement, tu va dans le dossier CCL et tu prends le chemin suivant : CommunityCoreLibrary/_Mod/User Release/Community Core Library/Languages/English/ a partir de là tu fais ton "copier/coller + renommage du dossier en French" comme je t'avais déjà expliqué. Et voila de là tu traduis en français et derrière tu peux faire un Pull Request comme j'ai vu que tu avais fait sur le Ludeon/fr

@kaptain-kavern Bonne, merci!

@kaptain-kavern Merci pour les explications :+1:
@ForsakenShell I will "pull request" my first translation version then,
I also tried to translate the Defs Folder, "Renamed "French/DefInjected" just for a test, but my translation don't appear in the game. I don't understand why, it should work :(

iirc, there was some changes in A14 def injection for translations.  We'll have to look deeper to see what's going on.

Ok, I'm waiting you to find the solution, then :)
@kaptain-kavern j'ai traduit le "mod marijuana" ^^,
malheureusement c'est comme CCL, rien ne s'affiche en jeu :'(  Curieux de savoir comment on fait.

Plaît, c'est le traqueur de problème pour le CCL. Problèmes avec les autres mods devraient être situés dans leur propre traqueur ou sur les forums dans leur fil.
Pardonnez mon français, je ne parle pas régulièrement.

I didn't understand ^^
Actually, I understand that it's a tracker problem, but I don't know what it mean.
Is this fixable, at least?
I can try to find a solution by myself but I also have other translation projects currently (and i'm a real noob in code)
I'd love to learn how to integrate the Def folder , it could let me translate every mod I want to :dancer:

I would look in the translations sub-forum on the ludeon site as to how to do it.  The steps for translating the core game will be exactly same for mods.

Finally... I understand !
In fact, the problem is  we can't translate some folders.
Here are the folders I can't translate (It doesn't show the translation in the game)

HelpCategoryDef
HelpDef
MiniMapDef
MiniMapOverlayDef
That's pretty sad ....:-1:

But every other folders are fine. (ThingDef, Research, etc) :+1:
I'll try to make a decent pull request, this time... lol

We'll see what we can do to make some of those more translateable before the next release.

RowCode post some ideas with backstories translation:
https://ludeon.com/forums/index.php?topic=3000.msg208718#msg208718

Very helpful given nobody on the CCL team speak or read russian.
¬¸¬


FFmpeg fails [Errno 9] Bad file descriptor

Home Assistant release with the issue:

Hassio 0.87.0
Last working Home Assistant release (if known):
Hassio 0.86.4
Operating environment (Hass.io/Docker/Windows/etc.):

Hassio
Component/platform:

https://www.home-assistant.io/components/ffmpeg/
Description of problem:
Seeing the following error during Hassio startup
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
ffmpeg:

Traceback (if applicable):
FFmpeg fails [Errno 9] Bad file descriptor
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/haffmpeg/core.py", line 114, in open
    stderr=stderr
  File "/usr/local/lib/python3.6/asyncio/subprocess.py", line 225, in create_subprocess_exec
    stderr=stderr, **kwds)
  File "uvloop/loop.pyx", line 2601, in subprocess_exec
  File "uvloop/loop.pyx", line 2561, in __subprocess_run
  File "uvloop/handles/process.pyx", line 588, in uvloop.loop.UVProcessTransport.new
  File "uvloop/handles/process.pyx", line 123, in uvloop.loop.UVProcess._init
OSError: [Errno 9] Bad file descriptor

Additional information:
Using with 2 cameras via RTSP connections

Can you turn on debug log for haffmpeg?
# configuration.yaml
logger:
  default: info
  logs:
    homeassistant.components.ffmpeg: debug
    haffmpeg: debug

I will try and get some logging in this weekend.

@MwC-Trexx Have you had the time to check it out? Please make sure to update to the latest Home Assistant version (0.90).

Issue doesn't seem to be appearing in 0.90.  Also switched camera feeds to new Stream component so don't need FFMPEG feed for them anymore.


[4.x] Support for Ruby 3

@adzap  Support for Ruby 3 in 4.x versions 🎉 🤝
c/c: @willradi @leonardocomar 🍻

@adzap Your eyes/review on it will be awesome 🤝

Hi, what about merge and release this fix?

Anybody here?

v4 is for Rails 4.x Does Rails v4.x support Ruby 3?

We use this gem in 4.x version with Rails 6 👍

But now with 5.x official version released, the suggestion is to migrate to 5.x, right @adzap ?
is there any breaking change betwenn 4.x and 5.x version of gem? Changelog provides this informations for us?
Anyway, thanks a lot for your feedback here ❤ 🤝

Yes v5 is official Rails 5 release and removes some old hacks.
On 3 Apr 2021, 10:16 AM +1100, Pedro Furtado @.***>, wrote:

But now with 5.x official version released, the suggestion is to migrate to 5.x, right @adzap ?
is there any breaking change betwenn 4.x and 5.x version of gem? Changelog provides this informations for us?
Anyway, thanks a lot for your feedback here ❤ 🤝
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@adzap  Anyway, is it possible to provide this feature to 4.x? Currently, we are using a fork to provide this🤝

@pedrofurtado the changes are backward incompatible and specific to changes in Rails mostly ActiveModel and ActiveRecord.


"Lift" operation in code

Hi,
Thank you for your research.
Could you give me some tips about "Lift" operation in Code,
may be here:
https://github.com/aharley/simple_bev/blob/be46f0ef71960c233341852f3d9bc3677558ab6d/utils/vox.py#L291-L341

The idea here is: for each 3D coordinate in the mem grid (aka the BEV meshgrid but with a vertical axis), take a bilinear sample at the pixel location where this coordinate projects.

@aharley that means, several 3d cells which are projected to the same pixel will be assigned the same 2D feature?

Yes. But I think it's rare for the features to be exactly the same, because really the 3D coordinates land in floating point (subpixel) locations, and we take bilinear samples.


X915 enforcing linting

Added lefthook to handle pre-commit checks
Added eslint and prettier config
Prettier'd entire repo
Updated readme
Updated github actions to include prettier and lint check

Going to remake branch off of devel as the merge conflicts would take longer than redoing the work.


feat: change release stategy

Issue #, if available:
Description of changes:
Checklist:

[ ] Have you successfully deployed to an AWS account with your changes?
[ ] Have you written new tests for your core changes, as applicable?

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

Also, we should add a workflow to perform readme update and commit on push to release branch


Bundle-cleanup to use BUNDLE_RUN_NAMESPACE for namespace

bundle-run allows for custom defined Namespace via BUNDLE_RUN_NAMESPACE, so also bundle-cleanup target should use
the same variable when removing the bundle.

Follow up to #103
/lgtm


Current master fails Travis CI on type comparison

Travis CI fails on Linux build on comparison between signed and unsigned:
. . . . .
make[2]: Entering directory '/home/travis/build/mouse07410/asn1c/libasn1parser'
  CC       asn1parser.lo
  CC       asn1p_y.lo
  LEX      asn1p_l.c
%option yylineno entails a performance penalty ONLY on rules that can match newline characters
REJECT entails a large performance penalty
  CC       asn1p_l.lo
asn1p_l.c: In function ‘yy_get_next_buffer’:
asn1p_l.c:3800:44: error: comparison between signed and unsigned integer expressions [-Werror=sign-compare]
  if ((int) ((yy_n_chars) + number_to_move) > YY_CURRENT_BUFFER_LVALUE->yy_buf_s
                                            ^
cc1: all warnings being treated as errors
. . . . .

This file is generated.

Guys...? Can we do anything with asn1p_l.l other than disable -Wsign-compare?


Add Datadog tags support

@keithduncan, this starts to add tags support so that statsd-client can also send to dogstatsd. I only implemented key/value tags, but I believe that just a tag name is supported too. Please forgive the beginner Haskell!
Here's what's left on my TODO list:

[x] Get some feedback on changing all the function signatures (breaking change). What do you think here? Is there a better way to support an optional argument and not break existing consumers of statsd-client? Some ideas:

It's fine, just bump the version and require consumers to pass [] if they don't want to send tags.
Create a new set of functions like increment' or dogIncrement.
Create DogStatsd.hs and a DogStatsdClient

[x] Implement support for tags that aren't key value pairs.
[x] Bump the version

References

Datadog datagram format

Here's what refactoring into a dedicated module for Dogstatsd might look like. I think this might be a cleaner approach. Usage would look like:
client <- dogStatsdClient "statsd://<IP_ADDRESS>:8125/prefix"
increment client "requests" [("country", "usa"), ("role", "machine")]

I removed the travis config because I couldn’t get things building in #2 without supporting really out of date tooling, we can ignore the CI status and it won’t show up on later commits.

I’m really happy with this, I think we just need to tweak the definition of Tags to use Name and Value then this is ready :+1: once this is merged we can tag and publish v<IP_ADDRESS> on Hackage. Do you want to set up an account there and I can add you as a maintainer too?

This should be good to go now @keithduncan, got the Tag Name/Value change in and should be good to merge at your leisure. Thanks for the very helpful review!

Do you want to set up an account there and I can add you as a maintainer so you can publish too?

Done. I'm just tclem over there too.

I’ve added you on hackage but it hasn’t shown up yet, I’m guessing there’s an invite you need to accept ✨ let me know if you want to do the <IP_ADDRESS> release or if you want to 🍐 on it, I need to refresh my memory on the process too 😄

Published 🎉  !


Move Documentation into Markdown

As a user of this library, I want to be able to read the documentation based on the version
ACS:

[ ] there is a documentation in the code based on Markdown
[ ] it is possible to open it as a website

how about docs site like go-mir docs site, it use hugo+Book theme to generate static site base on markdown documents.
The generated static site is just simple for project's document but not well as a project offical site.
docs for go-mir as a example to show Book theme for hugo and it support mutil-language translate.


remove duplicated code

remove duplicated code
doc: clarify unsafe_blit_fixed function description for FixedArray usage

Pull Request Test Coverage Report for Build 4012
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 80.401%

Totals

Change from base Build 4010:
0.04%

Covered Lines:
4373

Relevant Lines:
5439

💛  - Coveralls


Collect errors and display nicely

Turbolift currently runs multiple commands in series over the list of repositories, displaying stdout/stderr to the user but ignoring exit codes.
This can make it difficult for the user - they have to scour logs for failures.
We should collect errors (i.e. exit code != 0) and display a suitably formatted list at the end of execution.

+1 even just having a list of names of repos that failed at the end, alongside the count, would be helpful


docs: typed policy engine DR

What this PR changes/adds
Adds DR for typed policy engine refactor
Why it does that
Briefly state why the change was necessary.
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Part of #3511
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

@jimmarino @paullatzelsperger I revisited the DR scope, now is more narrow and it will permit to keep scopes hierarchy.

@jimmarino DR is ready to review


Run build fails using adapter-static - help understanding why.

Describe the bug
I am getting some errors when trying to build a static build using the adapter.
Here is my config svelte.config
import adapter from '@sveltejs/adapter-static';
import preprocess from 'svelte-preprocess';

/** @type {import('@sveltejs/kit').Config} */
const config = {
	// Consult https://github.com/sveltejs/svelte-preprocess
	// for more information about preprocessors
	preprocess: preprocess(),

	kit: {
		target: '#svelte',
		adapter: adapter({
			// default options are shown
			pages: 'build',
			assets: 'build',
			fallback: null
		})
	}
};

export default config;

Error log output
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'C:\\Program Files (x86)\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;E:\Traning BOX\socialize-3rd\node_modules\.bin;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler;C:\Python38\Scripts\;C:\Python38\;C:\Python27\;C:\Python27\Scripts;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Program Files (x86)\nodejs\;C:\Users\imris\AppData\Local\Programs\Python\Python37-32\Scripts\;C:\Users\imris\AppData\Local\Programs\Python\Python37-32\;C:\Users\imris\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Microsoft VS Code\bin;C:\Users\imris\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\imris\flutter\bin;C:\Users\imris\AppData\Local\GitHubDesktop\bin;C:\Users\imris\AppData\Local\Microsoft\WindowsApps;C:\Users\imris\AppData\Roaming\npm
9 verbose lifecycle<EMAIL_ADDRESS>CWD: E:\Traning BOX\socialize-3rd
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '/d /s /c', 'svelte-kit build' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec build script
13 verbose stack Error<EMAIL_ADDRESS>build: `svelte-kit build`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:376:20)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:376:20)
13 verbose stack     at maybeClose (internal/child_process.js:1055:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd E:\Traning BOX\socialize-3rd
16 verbose Windows_NT 10.0.19042
17 verbose argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
18 verbose node v14.17.0
19 verbose npm  v6.14.13
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>build: `svelte-kit build`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

I don't even understand the error,
any help would be appreciated 👍👍

There's not enough info here to reproduce your issue

My apologies .. what else can i add?
(and probably how)
its the sveltest latest - 2 weeks old

Can you provide a repository where this occurs?

Here it is:
https://github.com/sagive/sveltemp
I don't know how to check what's not working so i cant
even to try and debug it. May i ask what your checking?
Coming from PHP etc i am used to follow the error message (well.. mostly)..
Thank you very much 🙏

You error logs look very strange. If I run npm run dev or npm run build I get the following error message, which pretty clearly explains the issue:
Error: Failed to resolve import "../firebase_config" from "src/services/firebase.ts". Does the file exist?
    at formatError (node_modules/vite/dist/node/chunks/dep-bc228bbb.js:44564:46)
    at TransformContext.error (node_modules/vite/dist/node/chunks/dep-bc228bbb.js:44560:19)
    at normalizeUrl (node_modules/vite/dist/node/chunks/dep-bc228bbb.js:69451:26)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async TransformContext.transform (node_modules/vite/dist/node/chunks/dep-bc228bbb.js:69584:57)
    at async Object.transform (node_modules/vite/dist/node/chunks/dep-bc228bbb.js:44765:30)
    at async transformRequest (node_modules/vite/dist/node/chunks/dep-bc228bbb.js:59029:29)
    at async instantiateModule (node_modules/vite/dist/node/chunks/dep-bc228bbb.js:68641:10)

omg, sorry - thats a matter of the git.ignore for that file that holds the DB keys...
its ok, its a temp DB anyhow. i pushed again with this file.
Bassicly i am stuck between 2 errors...
if I remove the @ from firebase imports dev works but compiling doesn't.
if i add @ to the imports dev works but i get firebase.auth is not a function
I don't understand whats the problem... debuggin is weird
(no page / line numb etc - how you got such a nice error with the file in question?)

But.. I am asking about errors in the build process.
everything works in dev.
nm, thanks for trying to help.


[REQ] Ability to disable this

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
Its kinda annoying cuz I'm testing stuff and i need to click a button eraaaaaaaaaaaaaahhhhhhhh

Can be replaced with a non-obtrusive toast notification in the menu


Fixup deepspeed/cli tests

Adds check for print statement that deepspeed decided to add in the latest version causing a failure in our checking of the CLI outputs 🙃 Linked FR to hopefully make it a logger and not a print statement: https://github.com/microsoft/DeepSpeed/issues/3680
For now thought this can be merged w/o issue

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Adding a one-off price to a new subscription fails

Bug report

Extension name: firestore-stripe-payments

Describe the bug
Beginning a subscription with a one-off price included fails with an Invalid value type error
To Reproduce
Take a look at the following screenshot from Firestore

Simple checkout_session doc with 2 prices attached (1x recurring, 1x one-off) as an array of maps. Error returned:
Invalid value type: {:"0"=>"price_1JeZSJG3jpBeqZbddfKBWEJV", :"1"=>"price_1JwdSwG3jpBeqZbdvPnsCswO"} must be a string
Expected behavior
According to the documentation, adding a one-off price to a new subscription is meant to work (e.g. "one time setup fee"):
https://github.com/stripe/stripe-firebase-extensions/blob/2ad018aeb45564fce06540a952253715aba1ef79/firestore-stripe-payments/POSTINSTALL.md?plain=1#L418-L447

@Bandit The issue here is your metadata parameter. Checkout Session can only be created with key: String pairings.


Better rendering of list-table

https://github.com/Qiskit/qiskit-terra/pull/9549/ uses list-table extensively and the rendering is not optimal.
The table width scales with the content; does not stretched to the full width which I personally find aesthetically not pleasing.

This can probably be improved by css.

Can we also render - or have a option to render, cells so they are vertically top aligned. The X,Y,Z,I alternative is Pauli and the center alignment - with the extra content in the right hand cell, makes the center alignment not so suitable here I think. IMO it would look better as per this manually edited image

list-table looks much better in the new Furo theme (https://github.com/Qiskit/qiskit_sphinx_theme/pull/425). It takes up the full screen real estate, and the design is aligned with Carbon and qiskit.org.

We released 1.13.0rc1 today and are looking for feedback on the new theme. Feel free to reopen this issue if you have suggestions for further improvements.


hcpms-create-hybrid-app - "Mobile Services" renamed?

hi, in
http://go.sap.com/developer/tutorials/hcp-template-mobile-web-app.html step 2
I cannot find a "Mobile Services" service, however there is a "Development & Operations" service with the same icon and content, so it looks like the "Mobile Services" service has been renamed?

SAP HANA Cloud Platform mobile services was renamed to SAP HANA Cloud Platform mobile services for development and operations. Other services are being added under the "mobile services" group. Tutorial updated with new screenshots/instructions. See commit: https://github.com/SAPDocuments/Tutorials/commit/2f4cab4c7318ac521dde890b1db7ff415d27601c


reference coefficients in Eq.4

In Eq.4, ‘s’ denotes the coefficient for each reference point, but in Section 3.1, a number of ‘s’ appear, but they do not seem to represent reference coefficients and they seem to indicate the positional encoding.
So can you explain what the ‘s’ actually stands for?

Hi, I am sorry that the "s" is a typo. We have fixed it in the latest version of our paper.

In addition, I think there is an inconsistency between Equation 4 and Figure 2.  In Eq. 4, all encodings (d, sin, cos, z) for each reference point are weighted using reference coefficients. But in Figure 2, only the depth encoding (d) is weighted.
I don't know if I understand correctly, I hope this helps.

@Yzichen In reading the paper, I also found this problem.

The yellow box seems to represent the distance PE, but I don't understand that after Fourier coding it becomes D×C dimensional, and I don't know why the reference coefficients (red box) are added to the distance PE, aren't the reference coefficients in the MLP?

@ChenhongyiYang Hi, where is the latest version of the paper?

Sorry for the incontinence. We largely rephrased the method section before we Arxiving the paper, so there were a lot of typos and inconsistencies between the figures and formulations. We are continuing to fix them and update the paper.
@Yzichen  For your concerns, for Figure 2 (a), you are correct that the heights are also weighted here, and we will fix this later. For rotation PE, we do not need to explicitly weight it because all lifted 3D pixels from the same 2D pixels share the same rotation. For Figure 2 (b), we also do not need to compute the rotation PE for all lifted 3D pixels from an image column because they are all the same.
@WYL-Projects For your concerns, in Figure 2 (a) we are actually showing how we compute the PE for a 2D image pixel (shown in the small red box). Therefore, given a pixel, after we lift it, we will get D 3D pixels. Then after the Fourier encoding, the shape of PE becomes D x C. Also, the MLP we showed here is used to fuse the PE for different parts (distance, rotation, height), and the reference coefficients are actually predicted by another conv layer (not explicitly shown here).

@ChenhongyiYang Okay, thanks for the reply. Since the rotational PE is not explicitly weighted, what PE does the green box represent and what PE does the yellow box represent?

@ChenhongyiYang Okay, thanks for the reply. Since the rotational PE is not explicitly weighted, what PE does the green box represent and what PE does the yellow box represent?

Sorry to bother you, I have another small question, I see that RefPE is converting multiple views to LIDAR coordinate system uniformly, why is it PE with the self vehicle as the origin again, this process is converting the point coordinates under LIDAR coordinate system to the self vehicle coordinate system centered on the rear axle of the vehicle again?


Figure out a way to not need to call mockWindow in each test

Discussed this some in slack with @simonihmig but we didn't come up with any definitive solution. The main problem with calling mockWindow in each test, for me, is if I use it in an addon, then someone consumes my addon, they may not know about this requirement, and it could break their tests and be hard for them to figure out how to fix.

Just C&P from Slack, so the latest discussion does not get lost 😉


[FEATURE REQUEST] - Separate Sampler and Scheuler from SD Parameter Extractor

Summary

I dont know if this feature is possible to do right now, or if it could be done. I would like to import all data from image including scheduler and sampler. And I see in the extractor scheduler and sampler are together. Would be possible to separate this information?
Thank you!
Basic Example

Reference Issues.
No response

That's a really good question. Firstly, I didn't separate the Sampler and Scheduler as individual outputs because different tools support different Samplers and Schedulers. Connecting the output Sampler directly to other nodes is likely to cause issues (and different tools even have different names for the same Sampler sometimes). If separating the Sampler and Scheduler would significantly benefit your workflow, I can try to add a similar feature to the Extractor.
One possible approach is to match against a known list of Schedulers, but the downside is that I might not be able to update that list immediately when new Schedulers show up in the community. Additionally, since I've been quite busy recently, I don't think I'll be able to update the repo within the next few weeks.


adding kafka troubleshooting info

Merging kafka troubleshooting info from zendesk to this repo
https://help.datadoghq.com/hc/en-us/articles/115002655346-Troubleshooting-and-Deep-Dive-for-Kafka

@hush-hush PR updated


Set new subscription manager address for Opensea

This updates the address for the opensea subscription manager which will be reflected upon the next deploy of the contract.
Reference for the new address (which is now managed by a DAO): https://github.com/ProjectOpenSea/operator-filter-registry

Verified address at https://etherscan.io/address/0x3cc6CddA760b79bAfa08dF41ECFA224f810dCeB6


ignore None when user data is empty (gunzip: invalid magic)

When user data is empty, output for describe-instance-attribute --attribute userData --query UserData.Value is "None".
If not excluding None from output, you get inconsistent data, ending in code trying to gunzip something because is not base64 encoded as ASCII:
gunzip: invalid magic

@gabrielsoltz I had to revert it, I realized it changes more than just fixing gunzip: invalid magic. As in other PR you made, output doesn't work as expected, it is probably OSX related (if works fine in Linux). Please, feel free to PR a fix for the gunzip:invalid magic issue only. Also, in your changes you are leaving trace of what is found, I don't like that approach since it is not secure. Thanks!


Fix regex to catch rules without specific types

Currently flask-swagger does not support paths with no types
bad
@route('/<param>/<another>')

good
@route('/<string:param>/<string:another>')

The problem explained here: https://regex101.com/r/iL3jK2/3
Solution explained here: https://regex101.com/r/gZ2rV3/4
This PR fixes the problem!

Thanks Bruno!


NuScenes Boston Split

Hi,
thanks for the great work!
Do you provide the Boston split that you used in Table.8? Can it be enabled by setting nusc_new_split to True in nuscenes_dataset.py and generated with nusc_split.py?

Thank you for your interest in our project. The "new split" is a split newly proposed in the article "StreamMapNet: Streaming Mapping Network for Vectorized Online HD Map Construction." The new split is a good choice if you want to test the model's performance on datasets without geographical overlap. Yes, it can be enabled by setting nusc_new_split to True within nuscenes_dataset.py and using nusc_split.py for generation. I have tested the effect of the neural map prior on this split, and there has been a notable improvement. I have uploaded the code for generating the Boston split here. The generation of the Boston split involves a series of calculations, making the use of the new split a better option.

Thank you for the clarification, that was helpful!


Pressing "Tab" brings you to a strange place

To repro:

To go "Become a store"
Press the Tab key twice
Notice you're in a funny place (see screenshot)

Can you see if this has been fixed with the latest code commits?


Fix links to schema files in x-ms-examples docs

Changelog
Fix broken links

2 in docs about x-ms-examples

None of these issues is related to this PR.


asn1ber: OID values starting larger than .2.39 are interpreted incorrectly

OID values are encoded a bit strangely in asn1, in that the first two octets are encoded using a single byte:

BER encoding. Primitive. Contents octets are as follows, where value1, …, valuen denote the integer values of the components in the complete object identifier:

The first octet has value 40 × value1 + value2. (This is unambiguous, since value1
is limited to values 0, 1, and 2; value2 is limited to the range 0 to 39 when value1 is 0 or 1; and, according to X.208, n is always at least 2.)
The following octets, if any, encode value3, …, valuen. Each value is encoded base 128, most significant digit first, with as few digits as possible, and the most significant bit of each octet except the last in the value's encoding set to "1."

The result of this is that the first two octets of an OID can only be within the ranges:

0.0.x to 0.39.x
1.0.x to 1.39.x
2.0.x to 2.79.x

The OID value .2.46 encodes to the byte 0x7E. The problem is this is incorrectly decoded as .3.6.
I came across this with a device with a hrDeviceId value. Interestingly, this is actually a fairly common problem across a few different libraries and applications, and took a while to isolate because many other libraries/tools have the same bug

I wonder if ITU are real happy with the tradeoff in terms of man hours fixing stuff like this versus the one byte saved in the encoding...

See, I even managed to confuse myself in the commit message.

Yeah this can be summed up as: Don't be "clever". Especially when designing protocols.
Thanks for the fix!


Drop blank orders on session destroy

Currently, Shoppe creates a blank order with a "building" status whenever a new session is created (e.g. when a user visits the site), but if the user leaves the page, the blank orders reamins on the database. This clutters the db a lot, so i guess shoppe should not save them or destroy them when the session is no longer valid.

A script can be easily written to remove any blank orders. It wouldn't clutter the database up much as it's just creating 1 record


[Enhancement] (nereids)implement DropUserCommand in nereids

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
DropUserCommand is implemented in the legacy planner but missing in Nereids. You need to implement it in Nereids. The syntax for this command is provided in DorisParser.g4, and you can refer to DropUserStmt.java in the legacy planner for its functionality.
unsupportedDropStatement : DROP USER (IF EXISTS)? userIdentify
Solution
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

i will pick it


hasOne field should have prop index: true

It's important, it's missing, it's easy to fix.

I'm using this patch for now:
https://github.com/kapouer/node-orm2/commit/6877c47a079f9b770f605f7a3694baf131eb563b
@dxg what do you think ?


Update builder to the offical builder

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/cherry-pick release-v1.1


Memory leak in parse_string? (or misleading documentation?)

I received a report of memory leaks from an XMLDict user https://github.com/samoconnor/XMLDict.jl/issues/1.
I'm somewhat surprised. The LightXML.jl doc says, under the heading "Create an XML Document", that "When you create XML documents and elements directly you need to take care not to leak memory". However, under the heading "Read an XML file" there is no mention of memory management. XMLDict.jl only calls LightXML.parse_string, so it does not "create XML documents and elements directly".
The documentation seems to say that if you are just "read[ing] an xml file", as opposed to "create[ing] XML documents and elements directly", then you do not need to worry about memory management.
Is parse_string broken? or is the documentation broken?
This seems related: https://github.com/JuliaLang/LightXML.jl/pull/19

https://github.com/JuliaLang/LightXML.jl/blob/d31f1f43dc04fd1546ec5e4ad039c6f1981892fd/src/document.jl#L103
XMLDocument(p) is creating an XML document. So the word "directly" should probably be adjusted. If you know you're never adding children or other references to the same underlying pointer you can manually add a finalizer to any XMLDocuments you create. I don't think it's safe to do that in general without bookkeeping reference counts in all of the Julia types.

I suggest at a minimum:

Add a finalizer in the parse_* methods
Describe in the documentation: under what circumstances users of parse_* could still get into trouble with memory management.
Provide an example of "this is ok", and an example of "this is not ok", and "here is how to handle it".

My concern is if you do parse_string to create an initial XMLDocument, then add some children to it, if it has a finalizer and the Julia XMLDocument object goes out of scope and gets garbage collected but the children are still alive, you could cause a segfault since the Julia GC doesn't know about the C-level reference between the two objects.

So, per my suggestion above, please describe that in the documentation.
i.e. say that everything is fine if...

you don't manually add children.
when you do add children, you make sure to hold a reference to the parent doc until after you're done with the children.

And, please provide examples of correct usage in the documentation.
(FWIW, a segfault is far preferable to a memory leak. A segfault gets found in testing. A memory leak causes stuff to break months later in production and costs way more to fix.)

A segfault caused by a GC will not necessarily be found in tests.

I'm not familiar with libxml2 API but is the memory own'ed by a root object and is it always possible to find know what the owner object is when the library returns a pointer (either from the argument or from some libxml2 api)?

I don't know exactly how to answer your question @yuyichao. libxml2 is a C library and until someone implements a full reference count system here (which is what I believe the R wrapper and maybe also the Python wrapper do), you're responsible for C-like manual memory management when using it through this wrapper.

What I mean is that we don't necessarily need to keep track of reference counting and we can instead track the reference directly. This may not be simpler in general (although also won't be much more complicated since for RC you also need to lookup the julia object corresponding to a libxml2 pointer) but in the case where each object has a clear owner this would be much simpler.
My question was basically if this is true for libxml2. For example, can a xml node belong to multiple xml document simultaneously? And if this is reasonable to keep track of given the API. (i.e. if it is clear from the API when and how the ownership is transfered.)

can a xml node belong to multiple xml document simultaneously

Looks like.
julia> xdoc = XMLDocument()
<?xml version="1.0" encoding="utf-8"?>
julia> xroot = create_root(xdoc, "States")
<States/>
julia> xs1 = new_child(xroot, "State")
<State/>
julia> xdoc2 = XMLDocument()
<?xml version="1.0" encoding="utf-8"?>
julia> xdoc
<?xml version="1.0" encoding="utf-8"?>
<States>
  <State/>
</States>
julia> xroot2 = create_root(xdoc2, "States2")
<States2/>
julia> add_child(xroot2, xs1)
true
julia> xroot2
<States2>
  <State/>
</States2>
julia> xs2 = new_child(xs1, "StateChild2")
<StateChild2/>
julia> xdoc
<?xml version="1.0" encoding="utf-8"?>
<States>
  <State>
    <StateChild2/>
  </State>
</States>
julia> xdoc2
<?xml version="1.0" encoding="utf-8"?>
<States2>
  <State>
    <StateChild2/>
  </State>
</States2>

Actually it looks like this is not allowed since freeing both xdoc and xdoc2 here causes a segfault.
julia> using LightXML

julia> xdoc = XMLDocument()
<?xml version="1.0" encoding="utf-8"?>

julia> xroot = create_root(xdoc, "States")
<States/>

julia> xs1 = new_child(xroot, "State")
<State/>

julia> xdoc2 = XMLDocument()
<?xml version="1.0" encoding="utf-8"?>

julia> xroot2 = create_root(xdoc2, "States2")
<States2/>

julia> add_child(xroot2, xs1)
true

julia> xroot2
<States2>
  <State/>
</States2>

julia> xroot
<States>
  <State/>
</States>

julia> fre
free  frexp
julia> free
free (generic function with 4 methods)

julia> free(xdoc)
Ptr{Void} @0x0000000000000000

julia> free(xdoc2)

signal (11): 段错误
while loading no file, in expression starting on line 0
xmlFreeNodeList at /usr/bin/../lib/libxml2.so (unknown line)
xmlFreeNodeList at /usr/bin/../lib/libxml2.so (unknown line)
xmlFreeDoc at /usr/bin/../lib/libxml2.so (unknown line)
free at /home/yuyichao/projects/contrib/LightXML.jl/src/document.jl:71
unknown function (ip: 0x7fa6af99c045)
[inline] at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/julia_internal.h:69
jl_call_method_internal at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/gf.c:1879
do_call at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/interpreter.c:66
eval at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/interpreter.c:185
jl_toplevel_eval_flex at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/toplevel.c:561
[inline] at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/julia.h:1379
jl_eh_restore_state at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/builtins.c:548
eval at ./boot.jl:267
[inline] at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/julia_internal.h:69
jl_call_method_internal at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/gf.c:1879
[inline] at ./REPL.jl:3
eval_user_input at ./REPL.jl:62
unknown function (ip: 0x7fa6afbca5b7)
[inline] at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/julia_internal.h:69
jl_call_method_internal at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/gf.c:1879
[inline] at ./REPL.jl:92
#1 at ./task.jl:59
unknown function (ip: 0x7fa8b80c1560)
[inline] at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/julia_internal.h:69
jl_call_method_internal at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/gf.c:1903
start_task at /home/yuyichao/projects/arch-pkg/pkg/all/julia-git/src/julia/src/task.c:245
unknown function (ip: (nil))
Allocations: 4859550 (Pool: 4857857; Big: 1693); GC: 10

That's expected, xmlFreeDoc frees all children http://xmlsoft.org/html/libxml-tree.html#xmlFreeDoc

Then is there a way to free all the memory allocated without segfault after creating this?

xmlNode for example also have a parent field so I think it is not supposed to be added to two trees simultaneously.

It might be one of those things that the library lets you do but you're not supposed to do it? If we want to do something clever and automatic here, I think we'd really have to carefully study how some other proven, well-tested wrapper of libgit2 for some garbage collected language handles these things.

IIUC lxml.etree uses libxml2 and when you try to add a node to another tree, it is deleted from the original one.
In [1]: from lxml import etree

In [2]: root = etree.Element("root")

In [3]: root2 = etree.Element("root2")

In [4]: c1 = etree.Element("child1")

In [5]: root.append(c1)

In [6]: print(etree.tostring(root).decode())
<root><child1/></root>

In [7]: print(etree.tostring(root2).decode())
<root2/>

In [8]: root2.append(c1)

In [9]: print(etree.tostring(root).decode())
<root/>

In [10]: print(etree.tostring(root2).decode())
<root2><child1/></root2>

FWIW, here's a detailed description of how this works in the R wrapper for libxml2:
https://github.com/omegahat/XML/blob/master/Docs/MemoryManagement.pdf

In XMLDict, I've added finalizer(doc, LightXML.free) after parse_string, and finalize(doc) after doc has been converted to a Dict. https://github.com/samoconnor/XMLDict.jl/commit/146af78e7c28e1cbbbd79c1a8794a6c0d4b7fd18
The user who reported https://github.com/samoconnor/XMLDict.jl/issues/1 says that they can now process large (6 gb) files with constant memory usage.
I'd like to reiterate my request to the maintainers of LightXML.jl: Please add, ASAP, a description and and example to the documentation for the simple read-only case that says "if you do x, y and z you'll be fine". I understand that it might take time to figure out a robust way to handle all the corner cases, but in the meantime, the documentation should at least tell the user how to use the library safely in its current form.

Pull requests encouraged.

FYI I made a further tweak to the XMLDict.jl work-around: https://github.com/samoconnor/XMLDict.jl/commit/d7b63d09f7681919119e20d7032878a96cc83836
-- "keep back refernce to top level XMLDocument object to avoid premature finalisation".


[Section] Bridges

Specs:
https://hackmd.io/@UqIQhrvmTZavwMkJPpVXHw/SJVei03jc#Bridges
Labelled with:

#bridges

Closed with https://github.com/gnosischain/documentation/pull/31
Will create subsequent follow-up issues (AMB Bridge, xDai Bridge, Omnibridge, etc)


Bump @electron/asar dep

Include the fix in https://github.com/electron/asar/pull/268

This fix is within range of our current dependency string making this PR a no-op


Vector Highlight Crash

"When you have a vector highlighted and no vector is defined and you hit apply changes, it crashes the GUI"
server log snippet for the crash:
"i Mar 18 10:31:56 2022
mvaDescriptor(""omega"",180.0)
CA.Client.Exception...............................................
   Warning: ""Virtual circuit disconnect""
   Context: ""xf17id1-srv1-1713.nsls2.bnl.local:5064""
   Source File: ../cac.cpp line 1237
   Current Time: Fri Mar 18 2022 10:32:04.929387362
..................................................................
Fri Mar 18 10:32:11 2022
center_on_click(322.0,262.0,650.0,520.0,""screen"",0)
Traceback (most recent call last):
 File ""/GPFS/CENTRAL/xf17id1/skinnerProjectsBackup/lsdc_amx/lsdcGui.py"", line 4334, in editSelectedRequestsCB
   self.editSampleRequestCB(singleRequest)
 File ""/GPFS/CENTRAL/xf17id1/skinnerProjectsBackup/lsdc_amx/lsdcGui.py"", line 4368, in editSampleRequestCB
   reqObj[""vectorParams""][""fpp""] = int(self.vectorFPP_ledit.text())
KeyError: 'vectorParams'"

log directory is /GPFS/CENTRAL/xf17id1/RA-310090_18Mar2022


unable to set log levels

How does the logging configuration work?
$ sudo ./fancon --help
fancon argument=value ...
…
-l  log-lvl      Sets the logging level: info, debug, trace, warning, error (default: info)

Based on the help text I assumed one of the following invocations should work. As you can see fancon always reports <debug> No config found
$ sudo ./fancon start -v -l=debug
20/07/07 08:49 [20757] <debug> No config found

$ sudo ./fancon start -v -l debug
20/07/07 08:50 [20844] <warning> Unknown argument 'debug' from statement 'debug'
20/07/07 08:50 [20844] <debug> No config found
Starting controller

Ah, sorry: -ENOTENOUGHCOFFEE.
-l=debug works as <debug> No config found is a debug logging message.


helper_name doesn't work in package-tap.i18n

My package-tap.i18n looks like this:
{
    "i18n_files_route": "i18n/",
    "languages_files_dir": "i18n/",
    "translation_function_name": "localizeString",
    "helper_name": "localizeString"
}

However, the template helper is still registered as "_" unless I also add the helper name to project-tap.i18n. The javascript helper is still registered properly.

@mglidden did you find a workaround for this? Encountering the same issue

Since I was using it in an internal package, I just put the config at the project level


Black / White List

Hi everyone,
It could be very useful to have a black / white list to enable or disable pixel-saver for certain applications, where it does not work as expected.
Thanks,
Felipe

There are heuristic right now on what to decorate or not. Window that have extra feature in the title bar (like many gnome apps) or windows that do not have a title bar (like chromium) are not subject to pixel saver features.
Do you have an app in mind that do not behaves properly ?


Allow non-Jupyter kernels to populate the variable explorer

.ipynb notebooks using a .NET Interactive kernel don't populate the Jupyter Variable View:

There should be a mechanism for other kernels/notebook controllers to provide their variables, and in the case of .NET Interactive an additional column for target kernel (e.g., C#, F#, PowerShell, etc.) would be ideal since separate kernels won't necessarily share the same variables.

Covered via #5913.

Lets use this issue to track the variable explorer, (instead of having a single github issue to track 2 separate issues).

I'm wondering if we can implement this without requiring the Jupyter extension to know anything about language-specific code. Perhaps we could standardize on a KernelVariableDataProvider interface? Language extensions could call a registerKernelVariableDataProvider(dataProvider: KernelVariableDataProvider) method that the Jupyter extension provides in its extension API. The KernelVariableDataProvider would then expose methods that the Jupyter extension can call to populate its variable explorer.

andardize on a KernelVariableDataProvider interface? Language extensions could call a registerKernelVariableDataProvider(dataProvider: KernelVariableDataProvider)

I'd prefer for us to start using the Jupyter Kernel API instaed of using our own API, this way others don't need to pull in our dependencies (types or the like). i.e. 3rd party extensions expose API thats a standard today (Jupyter npm services)


Linux update failures

Report from discord:

@caesay
hm yes that looks familiar
Well not exactly. so cross-device I've seen before, that happens if we try and rename .AppImage when it was extracted to a different /dev to the target location. But it looks like that was handled ("trying again with a copy"). The copy failed due to "text file busy" which I've not seen before.
This seems to suggest that it happens when trying to modify a running executable https://stackoverflow.com/questions/16764946/what-generates-the-text-file-busy-message-in-unix but that doesn't sound right
It's strange because
the AppImage is not an executable, and
we should be waiting for it to exit before performing the update anyway
does it reproduce or was it a one-off?
@AArnott
Yes, it happened again on the next app update.

@caesay
I've not seen this error before and don't see anything obvious in the code, unless you're able to provide some more details I'll likely need to install xubuntu and try myself at some point.
Without any specific ideas of what is going wrong, here are some shoot-in-dark questions:
Has an update ever worked on this machine, if so, do you have logs for that?
Can you describe your current disk layout eg. using lsblk or df -h?
Is another instance of the application running while you try to update or is it only the instance being updated?
After the update fails can you try manually copying the update into place by extracting the nupkg (path in the logs, it's a zip) and then doing a cp to replace the existing AppImage on the desktop?
@AArnott
I can repro the exact problem myself with WSL that my user experienced in xubuntu. Here are the answers to your questions from my environment:
No, update has never worked.
lsblk output:
NAME  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0   7:0    0 446.7M  1 loop /mnt/wsl/docker-desktop/cli-tools
loop1   7:1    0 147.5M  1 loop
loop2   7:2    0 717.6M  1 loop
sda     8:0    0   256G  0 disk
sdb     8:16   0 342.4M  1 disk
sdc     8:32   0   256G  0 disk /
sdd     8:48   0   256G  0 disk /mnt/wsl/docker-desktop/docker-desktop-user-distro
sde     8:64   0   256G  0 disk /mnt/wsl/docker-desktop-data/isocache
It's the only instance ever invoked. However, when my app launches, it looks for other processes by the same path and attempts to communicate with them over a unix domain socket and then exits (so I have only one process left running at a time).
Manually copying over works fine.
Interestingly, the failure I saw happened while I ran the AppImage from the /mnt/c/Users/andre/Downloads folder. When I copied the AppImage to /home/andre and ran it from there, update worked. So at least for my case the error seems to be related to the file being under /mnt/c which indeed is a different 'device' than /var/tmp/velopack.

Fixed in 0.0.523-g5727de1

Just to circle back, yes this fixed the issue for my beta tester too.


Add and test JSON object matcher

JSON matching for #817

Rebased onto main as this is independent of the diff in #817. Feel free to merge into main once @jackzampolin and maybe @alpe had a look.


currency_settings locales refactoring

:ru locale added, :en and :sv locales fixed and template fixed.

@futhr sv.yml review and fixes required.

Thanks @foxweb, this has been applied to 3-0-stable and master branches. I fixed failing spec + changed i18n :notice key to :notice_messages (see) https://github.com/spree/spree/blob/master/core/config/locales/en.yml#L8


Customizations don't persist when app is quit

One of the nice things about Nova is that when you quit the app, the customised Dock icon remains shown in both the Finder, and the Dock.
I've just tried doing the same using this project, and the customisations are all reset when the app is quit.
It would be great if the customizations persisted.

Hey mate,
To make the changes persist you'll need to create a NSDockTilePlugin for the dock. The plugin runs independently of the app and means that a app pinned in the dock can have its icon updated dynamically.
If you look in the Demos/ folder you'll find a demo in the folder called 'DSFDockTile Plugin Demo'.  It's a SwiftUI app with a docktileplugin that changes the icon depending on the dark mode state.  Check out the description here. I used the instructions here to set up the project (see the attributions in the DSFDockTile README file) - it can be a little finicky to get right.
It's not quite as straight forward as you'll need to communicate between the plugin and the app to tell it to update (maybe shared preferences or if you like your AppKit more hardcore XPC services), but it works.  You can use DSFDockTile in the plugin to do all the dock imaging etc (in the demo I've got a SwiftUI app) and tell it from the primary app what it needs to display.
Cheers and thanks for the feedback!  Hope you're keeping safe.

It's not quite as straight forward as you'll need to communicate between the plugin and the app to tell it to update (maybe shared defaults or the like), but it works. You can use DSFDockTile in the plugin to do all the dock imaging etc (in the demo I've got a SwiftUI app) and tell it from the primary app what it needs to display.

I'd hoped to use a user defaults suite within an app group for this, but whatever the Dock is doing with these plugins, that doesn't seem to work.
If you don't use sandboxing in your main app process, you can use a shared user defaults suite, and post a distributed notification to ask the dock tile to read the updated defaults, but this seems to be a bit flaky (particularly around the updated user defaults not being saved to disk at the point the notification is sent… it's promising, and could probably work).
In any case, it seems like dock tiles are banned from the App Store, so it's all a bit moot, sadly.
Thanks for the well wishes, and I hope you're staying safe, too 😀

Yeah if you're targeting the App Store then you're out of luck either way.
If not, then as long as your NSDockTilePlugin is self-contained (the demo just changes the icon depending on the dark mode status) then you're fine - but its definitely a limited palette for sure.  I suppose you could use a distributed notification to transfer visual states in a docktileplugin (eg. send a notification for 'processing', another notification for 'idle', another notification for 'waiting' etc.) and the plugin can just respond appropriately - as long as the plugin itself is completely self contained.  But if the app is running then you may as well just not use an NSDockTilePlugin and sacrifice the non-running state.
I use a couple of apps which use the docktile to good use while the app is running (Handbrake for example) so just having a nice easy way of providing the functionality is useful.  Plus I wanted to have a little animated Stitch in my dock hehe.
Thanks for the feedback mate -- it's much appreciated.

Closing due to inactivity


FEATURE: SidekiqProcess metrics

Hi again! 👋🏻
We have this in our codebase and thought it might be interesting for everyone else. We have setup alerts for our Sidekiq deployments based on the latency metric coming from the SidekiqQueue instrumentation, but it was hard to see if we were overprovisioned or what, and we wanted to be able to have metrics on utilization (busy vs total).
The new metrics are based on Sidekiq's ProcessSet class, and expose what it returns.
I'd still need to add something to the README before the PR can be merged (and any other feedback, of course), but thought I'd open the PR early to see if this was interesting or not 😄

It sounds good to me, once you add the documentation! I can certainly see it as useful.

Added a bit to the README. Not sure if more is necessary, advice is welcome 😄

In case this is relevant at all, just tried this branch in our staging environment and everything seems to be in order.
Is anything else missing? Is an entry in the Changelog necessary? Feel free to add it if necessary, I think we're in opposite sides of the world 😆
Thanks a lot Sam!

Looking good to me, we are due for a release, I can take the changelog!
Thanks @mrsimo !


parameter meaning

Hi Nick, what's the meaning of parameter stride in the dataLoader function?

Hi @LeZhengThu
The stride is an additional parameter for decomposing the total time-series of a training example into a smaller chunks for learning. Specifically, the stride is the index we sample these smaller time-series at. This contrasts to target_steps which specifies the length of these smaller time-series.
For example consider a time series of 30 time-steps and I set up a data-loader with stride = 5, target_steps = 10, the examples would look like:

[0,1,2,3,4,5,6,7,8,9]
[5,6,7,8,9,10,11,12,13,14]
[10,11,12,13,14.15,16,17,18,19]
etc.

The reason I did this augmentation to the data is I found this deep Koopman to be very unstable during training, requiring smaller time-series lengths to get more consistent convergence.


Fix :  Interim fix for the codeblock

@AlanWalk,  Thank you for providing a useful extension.
I'm having a problem.
Command fails with code block.

I've created an Interim fix for the codeblock.
Regards,
Kazuyuki

Appreciate the PR, It's a valid fix, but I didn't need isInCodeCount, why did you doing that?

@AlanWalk, Thank you fix it!
I seems to have the wrong something.
I did not notice it in the correct behavior in the fix of a single line.
Lack my study, but Also one I was able to study.
Thanks!


Ability to configure the NearExpiry?

Commenting on this text: (The default is 30 days before the expiration date.)
Since it says "default", I presume there is a way to configure this event?  We would like to actually change this to be two events:  WarnNearExpiry and AlertNearExpiry.  We would Warn at 30 days which would generate tickets and work for us to update the value.  For secrets that can be auto-rotated, we'd create a job for that.  The AlertNearExpiry would be for 10 days out, which would trigger an on-call event.
Is either of that possible?  Thanks!

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

ID: 08fcaa60-2206-ed3d-9851-09a201f749e2
Version Independent ID: bfcac51f-f712-74ed-f0ff-15b56ae4216f
Content: Azure Event Grid event schema for Azure Key Vault
Content Source: articles/event-grid/event-schema-key-vault.md
Service: event-grid
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@SirAlvarex Thank you for your feedback! We will review and update as appropriate.

@msmbaldwin / @banisadr  any thoughts here?

@spelluru can you share your thoughts here?

@SirAlvarex, thank you for raising that concern. I am also looking for the ability to modify the NearExpiry default value if possible.

@mike-urnun-msft Is there an update on this issue?

@banisadr - please review as soon as you can. Thanks.

@mike-urnun-msft @banisadr I am also very interested in this :D
This should make SecretNearExpiry and KeyNearExpiry more useful.

any updates here? anyone?

This update would help me too! 30 days seems way to long. I would like to be able to set it to something like a day or week before. thanks again!

It is hardcoded to 30 days today as it is still in Preview. Ability to modify it across all types is coming. It will be available by end of the year.
Jack Lichwa
Key Vault PM

Default removed from documentation to avoid confusion. #please-close


Update composer to latest version

Latest is 1.4.2 https://github.com/composer/composer/releases

Wrong image.


WFLY-19056 Upgrade Narayana to 7.0.1.Final

https://issues.redhat.com/browse/WFLY-19056

Hello, marcosgopen. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

/ok-to-test


Setup a docker container for Django and web server

Builds container with a fresh copy of a specified version of Django
Loads other production dependencies and libraries
Uses a “secret” configuration including:

Database user id and password
Specified IP and port to access database (possibly non-standard)
Specified IP and port to receive web traffic (possibly non-standard)

Includes uWSGI installation and configuration
Includes any hardening needed for production

made the name of this issue agnostic to the web server being used because I am honestly not sure if I was to use uWSGI


Refactor cb

Here's a refactoring pass of the connection box generator. All tests still pass on Travis and kiwi (ncsim tests).
Mainly decomposing into helper functions and using operators where possible.
We have to do a lot of parameter passing to the helper functions which is a bit verbose. We should consider some sort of class structure for generators where can have access to parameters in our method definitions. Alternatively we could define these functions within the define_cb closure, but at that point I think we should consider using a class.

Pull Request Test Coverage Report for Build 82

59 of 151 (39.07%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-30.9%) to 63.121%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

connect_box/cb_orig.py
0
92
0.0%

Totals

Change from base Build 80:
-30.9%

Covered Lines:
178

Relevant Lines:
282

💛  - Coveralls


acquireTokenInteractive Ignores Scopes when Requesting Access Token

Core Library
MSAL Node (@azure/msal-node)
Core Library Version
1.14.3
Wrapper Library
Not Applicable
Wrapper Library Version
None
Public or Confidential Client?
Public
Description
When using PublicClientApplication.getTokenInteractive, only the default OIDC scopes are granted for the access token.
This is despite all the requested scopes being granted.
This can be seen here where request.scopes is not accessed at all.
https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/42e1baf2c53b980b509678bf011d9cdaa469f9fc/lib/msal-node/src/client/PublicClientApplication.ts#L121-L127
As stated in https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-access-token-with-a-client_secret, the scope parameter should hold the desired scopes.
When testing using @microsoft/microsoft-graph-client, a simple request to /me fails since the User.Read scope is not granted.
Error Message
There's no error message specifically, but the log in the First Code Sample below gives
Granted Scopes: [ 'openid', 'profile' ]

Error with @microsoft/microsoft-graph-client Test (Second Code Sample Below):
https://graph.microsoft.com/v1.0/me
(node:10584) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
C:\Users\Redfire\silicon\node_modules\@microsoft\microsoft-graph-client\src\GraphError.ts:61
                super(message || (baseError && baseError.message));
  ^
GraphError: Exception of type 'Microsoft.Fast.Profile.Core.Exception.ProfileAccessDeniedException' was thrown.
    at new GraphError (C:\Users\Redfire\silicon\node_modules\@microsoft\microsoft-graph-client\src\GraphError.ts:61:3)
    at Function.GraphErrorHandler.constructErrorFromResponse (C:\Users\Redfire\silicon\node_modules\@microsoft\microsoft-graph-client\src\GraphErrorHandler.ts:76:18)
    at Function.<anonymous> (C:\Users\Redfire\silicon\node_modules\@microsoft\microsoft-graph-client\src\GraphErrorHandler.ts:102:31)
    at step (C:\Users\Redfire\silicon\node_modules\@microsoft\microsoft-graph-client\node_modules\tslib\tslib.js:144:27)
    at Object.next (C:\Users\Redfire\silicon\node_modules\@microsoft\microsoft-graph-client\node_modules\tslib\tslib.js:125:57)
    at C:\Users\Redfire\silicon\node_modules\@microsoft\microsoft-graph-client\node_modules\tslib\tslib.js:118:75
    at new Promise (<anonymous>)
    at Object.__awaiter (C:\Users\Redfire\silicon\node_modules\@microsoft\microsoft-graph-client\node_modules\tslib\tslib.js:114:16)
    at Function.GraphErrorHandler.getError (C:\Users\Redfire\silicon\node_modules\@microsoft\microsoft-graph-client\lib\src\GraphErrorHandler.js:85:24)
    at GraphRequest.<anonymous> (C:\Users\Redfire\silicon\node_modules\@microsoft\microsoft-graph-client\src\GraphRequest.ts:391:55) {
  statusCode: 403,
  code: 'ErrorInsufficientPermissionsInAccessToken',
  requestId: 'cea8f798-7cfc-4456-9b2c-6aff7bd5367f',
  date: 2022-11-12T02:38:45.000Z,
  body: `{"code":"ErrorInsufficientPermissionsInAccessToken","message":"Exception of type 'Microsoft.Fast.Profile.Core.Exception.ProfileAccessDeniedException' was thrown.","innerError":{"date":"2022-11-12T10:38:45","request-id":"cea8f798-7cfc-4456-9b2c-6aff7bd5367f","client-request-id":"0d1f7a1a-befd-aad2-708f-df3c0f98e948"}}`
}

Msal Logs
[Sat, 12 Nov 2022 10:33:02 GMT]<EMAIL_ADDRESS>: Info - getTokenCache called
[Sat, 12 Nov 2022 10:33:02 GMT]<EMAIL_ADDRESS>: Info - getAuthCodeUrl called
[Sat, 12 Nov 2022 10:33:02 GMT]<EMAIL_ADDRESS>: Verbose - initializeRequestScopes called
[Sat, 12 Nov 2022 10:33:02 GMT] : [a2edfb47-ce31-4f91-9ba9-fc2920bde922]<EMAIL_ADDRESS>: Verbose - buildOauthClientConfiguration called
[Sat, 12 Nov 2022 10:33:02 GMT] : [a2edfb47-ce31-4f91-9ba9-fc2920bde922]<EMAIL_ADDRESS>: Verbose - building oauth client configuration with the authority: https://login.microsoftonline.com/consumers
[Sat, 12 Nov 2022 10:33:02 GMT] : [a2edfb47-ce31-4f91-9ba9-fc2920bde922]<EMAIL_ADDRESS>: Verbose - createAuthority called
[Sat, 12 Nov 2022 10:33:03 GMT] : [a2edfb47-ce31-4f91-9ba9-fc2920bde922]<EMAIL_ADDRESS>: Verbose - Auth code client created
[Sat, 12 Nov 2022 10:33:30 GMT]<EMAIL_ADDRESS>: Info - acquireTokenByCode called
[Sat, 12 Nov 2022 10:33:30 GMT]<EMAIL_ADDRESS>: Verbose - initializeRequestScopes called
[Sat, 12 Nov 2022 10:33:30 GMT] : [13813f63-fac3-414d-853f-435f84a754d5]<EMAIL_ADDRESS>: Verbose - buildOauthClientConfiguration called
[Sat, 12 Nov 2022 10:33:30 GMT] : [13813f63-fac3-414d-853f-435f84a754d5]<EMAIL_ADDRESS>: Verbose - building oauth client configuration with the authority: https://login.microsoftonline.com/consumers
[Sat, 12 Nov 2022 10:33:30 GMT] : [13813f63-fac3-414d-853f-435f84a754d5]<EMAIL_ADDRESS>: Verbose - createAuthority called
[Sat, 12 Nov 2022 10:33:30 GMT] : [13813f63-fac3-414d-853f-435f84a754d5]<EMAIL_ADDRESS>: Verbose - Auth code client created
[Sat, 12 Nov 2022 10:33:30 GMT] : [13813f63-fac3-414d-853f-435f84a754d5]<EMAIL_ADDRESS>: Info - in acquireToken call

MSAL Configuration
const pcaOptions: Configuration = {
	auth: {
		clientId: process.env.MICROSOFT_CLIENT_ID,
		authority: "https://login.microsoftonline.com/consumers",
	},
	system: {
		loggerOptions: {
			loggerCallback: (_1, message, _2) => console.info(message),
			piiLoggingEnabled: true,
				logLevel: msal.LogLevel.Trace,
		}
	}
};

Relevant Code Snippets
const scopes = ["User.Read", "Files.Read", "offline_access"];
const pca = new msal.PublicClientApplication(pcaOptions);

const interactive: InteractiveRequest = {
    openBrowser: async function (url) {
        await open(url);
    },
    scopes,
};

const credentials = await pca.acquireTokenInteractive(interactive);
console.log("Granted Scopes:", credentials.scopes);

import { Client } from "@microsoft/microsoft-graph-client";

const options: ClientOptions = {
	debugLogging: true,
	authProvider: new CustomAuthenticationProvider(callback => callback(null, accessToken)),
};

const client = Client.initWithMiddleware(options);
await client.api("/me").get();

Reproduction Steps

Initialise a Public Client Application
Acquire a Token Interactively
Log Granted Scopes of the Token

Expected Behavior
It is expected for the scopes of the granted token to contain all the scopes requested.
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
None (Server)
Regression
No response
Source
External (Customer)

@Redfire75369 This is indeed a bug, thanks for catching this!


pythonPackages.piexif: init at 1.0.12

Motivation for this change
piexif is a dependency for another package that I'm going to pull request soon.
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Is this ok or does it need some fixes?


Media views

is that anyway to gain media views ?

it is by not really implemented yet, maybe in future version or PR welcomed...

could you please elaborate on how to implant it. may be the endpoint?


Missing license

Thanks for releasing your code and model! I'm interested in trying it out, but couldn't find a LICENSE file, could you add one? Ideally MIT License, which is perhaps the most common choice for similar repositories nowadays.

Thanks for your reminder and the MIT license is now added.


What happened when...

What happen when a group  belongs a two projects and the issue is assigned to a group?
If the user of group does not have checked the project, dont send notification?
thanks

Ha..!
Good one, We have not really used the user group association.
Let me check this.
My feeling is that it would still send a mail based on users preference.


Update Reward Distribution Logic

Current Impl:
feed reward is distributed to all the data providers in the feed's data provider list when a new feed data is submitted
Improvement Proposal:
Need to verify the signatures to verify if data provider has signed, in order to receive reward.
Need to verify that feed parameters are met before reward distribution.

heartbeat time has passed
minimum deviation threshold is met
submission count is met
etc.

might not need to have these as they are done on the chainlink's end via quorum
need to further deliberate on implementation.


2.x Implementation of interest channel state propagation (enhancement #384)

NetflixOSS » eureka » eureka-pull-requests #78 SUCCESS
This pull request looks good

NetflixOSS » eureka » eureka-pull-requests #90 SUCCESS
This pull request looks good

NetflixOSS » eureka » eureka-pull-requests #92 SUCCESS
This pull request looks good

NetflixOSS » eureka » eureka-pull-requests #98 SUCCESS
This pull request looks good

NetflixOSS » eureka » eureka-pull-requests #100 SUCCESS
This pull request looks good


Ubuntu 14.04 make release (error)

I downloaded the most recent code from github, and I executed "make release".  The build failed.
It failed on "docker save ${docker_image_tag} > ${1}/${binary_name}.tar" (build/common.sh:621)
docker info
Containers: 2
Images: 42
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Dirs: 46
Execution Driver: native-0.2
Kernel Version: 3.16.0-30-generic
WARNING: No swap limit support
make release
....
+++ [0416 10:39:26] Starting Docker build for image: kube-apiserver
+++ [0416 10:39:26] Starting Docker build for image: kube-controller-manager
+++ [0416 10:39:27] Starting Docker build for image: kube-scheduler
Sending build context to Docker daemon 15.05 MB
Sending build context to Docker daemon
Sending build context to Docker daemon 19.86 MB
Sending build context to Docker daemon
Sending build context to Docker daemon 25.11 MB
Sending build context to Docker daemon
2015/04/16 10:39:39 Error: mkdir /tmp/docker-export-462515189/gcr.io/google_containers/kube-scheduler:ab6feb8cac6a763395c744ff866e4521: no such file or directory
!!! Error in build/../build/common.sh:621
'docker save ${docker_image_tag} > ${1}/${binary_name}.tar' exited with status 1
Call stack:
1: build/../build/common.sh:621 kube::release::create_docker_images_for_server(...)
2: build/../build/common.sh:572 kube::release::package_server_tarballs(...)
3: build/../build/common.sh:509 kube::release::package_tarballs(...)
4: build/release.sh:40 main(...)
Exiting with status 1
2015/04/16 10:39:40 Error: mkdir /tmp/docker-export-350534352/gcr.io/google_containers/kube-controller-manager:47b1def5551b4ca0ce7ecd447cdc07da: no such file or directory
!!! Error in build/../build/common.sh:621
'docker save ${docker_image_tag} > ${1}/${binary_name}.tar' exited with status 1
Call stack:
1: build/../build/common.sh:621 kube::release::create_docker_images_for_server(...)
2: build/../build/common.sh:572 kube::release::package_server_tarballs(...)
3: build/../build/common.sh:509 kube::release::package_tarballs(...)
4: build/release.sh:40 main(...)
Exiting with status 1
2015/04/16 10:39:40 Error: mkdir /tmp/docker-export-273039343/gcr.io/google_containers/kube-apiserver:9d99764c4d1cf782de2dc0c620bba48b: no such file or directory
!!! Error in build/../build/common.sh:621
'docker save ${docker_image_tag} > ${1}/${binary_name}.tar' exited with status 1
Call stack:
1: build/../build/common.sh:621 kube::release::create_docker_images_for_server(...)
2: build/../build/common.sh:572 kube::release::package_server_tarballs(...)
3: build/../build/common.sh:509 kube::release::package_tarballs(...)
4: build/release.sh:40 main(...)
Exiting with status 1
!!! [0416 10:39:40] previous Docker build failed
!!! Error in build/../build/common.sh:599
'( local binary_name; for binary_name in "${KUBE_DOCKER_WRAPPED_BINARIES[@]}";
do
kube::log::status "Starting Docker build for image: ${binary_name}"; ( local md5_sum; md5_sum=$(kube::release::md5 "$1/${binary_name}"); local docker_build_path="$1/${binary_name}.dockerbuild"; local docker_file_path="${docker_build_path}/Dockerfile"; local binary_file_path="$1/${binary_name}"; rm -rf ${docker_build_path}; mkdir -p ${docker_build_path}; ln $1/${binary_name} ${docker_build_path}/${binary_name}; printf " FROM scratch \n ADD ${binary_name} /${binary_name} \n ENTRYPOINT [ "/${binary_name}" ]\n" > ${docker_file_path}; local docker_image_tag=gcr.io/google_containers/$binary_name:$md5_sum; docker build -q -t "${docker_image_tag}" ${docker_build_path} > /dev/null; docker save ${docker_image_tag} > ${1}/${binary_name}.tar; echo $md5_sum > ${1}/${binary_name}.docker_tag; rm -rf ${docker_build_path} ) &
done; kube::util::wait-for-jobs || { kube::log::error "previous Docker build failed"; return 1; }; kube::log::status "Docker builds done" )' exited with status 1
Call stack:
1: build/../build/common.sh:599 kube::release::create_docker_images_for_server(...)
2: build/../build/common.sh:572 kube::release::package_server_tarballs(...)
3: build/../build/common.sh:509 kube::release::package_tarballs(...)
4: build/release.sh:40 main(...)
Exiting with status 1
!!! [0416 10:39:40] previous tarball phase failed
!!! Error in build/release.sh:511
'return 1' exited with status 1
Call stack:
1: build/release.sh:511 main(...)
Exiting with status 1
make: *** [release] Error 1
docker ps -a
CONTAINER ID        IMAGE                    COMMAND             CREATED             STATUS                         PORTS               NAMES
498169e06c2b        kube-build:build-8c287   true                About an hour ago   Exited (0) About an hour ago                       kube-build-data-8c287
c3045a0142fd        ubuntu:latest            /bin/bash           About an hour ago   Up About an hour                                   silly_ritchie

This is a little disturbing, because you're building in the same docker containers I am, in theory, and getting different results. Looking, since I added the code.

I'm having trouble telling from first principals what's going on with your build. We do actually mkdir -p ${docker_build_path}, which encompasses ${1} in the process. It actually seems to be the docker save itself that's failing. What version of docker are you trying this with? That could be the divergence.

apt-cache show docker.io displays two versions of docker.io
1.0.1~dfsg1-0ubuntu1~ubuntu<IP_ADDRESS>
0.9.1~dfsg1-2
Initially, I did an "apt-get install docker.io"
David

I'm sorry, but I think the problem is that you're running quite an old version of docker. We don't support anything below docker 1.4 right now, and even that's been a rough ride occasionally for people - 1.5 is where all the continuous testing is at right now.

No problem.  I upgraded to:
ii  lxc-docker                          1.6.0                                amd64        Linux container runtime
ii  lxc-docker-1.6.0                    1.6.0                                amd64        Linux container runtime
I downloaded kubernets into a new folder, and now make release works.
Thanks.

I spun up a new VM on AWS using ubuntu-trusty-14.04-amd64-server-20150325 (ami-d05e75b8)
I installed the latest version of docker (1.6).
Now, with "build release" I am getting the following:
ok      github.com/GoogleCloudPlatform/kubernetes/plugin/pkg/auth/authenticator/token/tokenfile 0.010s
ok      github.com/GoogleCloudPlatform/kubernetes/plugin/pkg/scheduler  0.010s
ok      github.com/GoogleCloudPlatform/kubernetes/plugin/pkg/scheduler/algorithmprovider        0.008s
ok      github.com/GoogleCloudPlatform/kubernetes/plugin/pkg/scheduler/api/validation   0.006s
ok      github.com/GoogleCloudPlatform/kubernetes/plugin/pkg/scheduler/factory  0.022s
+++ [0418 15:40:44] Running build command....
FATA[0000] Error response from daemon: Cannot start container e74bd5db59fe376d1f74f4fca8c9b15040409f7c42e319e28d94df04b23093ee: Error getting container e74bd5db59fe376d1f74f4fca8c9b15040409f7c42e319e28d94df04b23093ee from driver devicemapper: Error mounting '/dev/mapper/docker-202:1-398132-e74bd5db59fe376d1f74f4fca8c9b15040409f7c42e319e28d94df04b23093ee' on '/var/lib/docker/devicemapper/mnt/e74bd5db59fe376d1f74f4fca8c9b15040409f7c42e319e28d94df04b23093ee': no such file or directory
!!! Error in build/../build/common.sh:432
'"${docker_cmd[@]}" "$@"' exited with status 1
Call stack:
1: build/../build/common.sh:432 kube::build::run_build_command(...)
2: build/release.sh:36 main(...)
Exiting with status 1
make: *** [release] Error 1

On my second try, it worked.


CNRM CRD Generated types looks strange

Hey,
I'm trying to write a KPT function that works on Config Connector CRDs but I can't make sense of the generated types - the "CRD list types" seem to be complete while the actual CRD types are just aliases for object and don't implement KubernetesObject.
Or maybe CRDs are simply not expected to work yet? I'm not completely sure how interpret GoogleContainerTools/kpt-functions-sdk#46.
Anyway to exemplify what I mean, this is the contents one of the files generated by npm init kpt-functions (against a cluster with Config Connector CRDs installed):
export type KMSKeyRing = object;

// KMSKeyRingList is a list of KMSKeyRing
export class KMSKeyRingList {
  // APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
  public apiVersion: string;

  // List of kmskeyrings. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md
  public items: KMSKeyRing[];

  // Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
  public kind: string;

  // ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.
  public metadata?: KMSKeyRingList.Metadata;

  constructor(desc: KMSKeyRingList) {
    this.apiVersion = KMSKeyRingList.apiVersion;
    this.items = desc.items;
    this.kind = KMSKeyRingList.kind;
    this.metadata = desc.metadata;
  }
}

export function isKMSKeyRingList(o: any): o is KMSKeyRingList {
  return o && o.apiVersion === KMSKeyRingList.apiVersion && o.kind === KMSKeyRingList.kind;
}

export namespace KMSKeyRingList {
  export const apiVersion = "kms.cnrm.cloud.google.com/v1alpha1";
  export const group = "kms.cnrm.cloud.google.com";
  export const version = "v1alpha1";
  export const kind = "KMSKeyRingList";

  // KMSKeyRingList is a list of KMSKeyRing
  export interface Interface {
    // List of kmskeyrings. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md
    items: KMSKeyRing[];

    // ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.
    metadata?: KMSKeyRingList.Metadata;
  }
  // ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.
  export class Metadata {
    // continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a consistent list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response, unless you have received this token from an error message.
    public continue?: string;

    // remainingItemCount is the number of subsequent items in the list which are not included in this list response. If the list request contained label or field selectors, then the number of remaining items is unknown and the field will be left unset and omitted during serialization. If the list is complete (either because it is not chunking or because this is the last chunk), then there are no more remaining items and this field will be left unset and omitted during serialization. Servers older than v1.15 do not set this field. The intended use of the remainingItemCount is *estimating* the size of a collection. Clients should not rely on the remainingItemCount to be set or to be exact.
    public remainingItemCount?: number;

    // String that identifies the server's internal version of this object that can be used by clients to determine when objects have changed. Value must be treated as opaque by clients and passed unmodified back to the server. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency
    public resourceVersion?: string;

    // selfLink is a URL representing this object. Populated by the system. Read-only.
    //
    // DEPRECATED Kubernetes will stop propagating this field in 1.20 release and the field is planned to be removed in 1.21 release.
    public selfLink?: string;
  }
}

Per offline discussion with Morgante, setting preserveUnknownFields: false in CRD worked for him.

I run into this issue aswell and this seemed to solve it - do we think it's best to document the CRD generation in more detail somewhere?
I'm happy to try and put something together.

@artbegolli we can document how not setting this field manifests as an issue during type generation. Is that what you're suggesting?

Suggestion from @monopole, we should have a avoid list or except list in case there are non-structural CRDs on the API server which the user doesn't care about.

@artbegolli we can document how not setting this field manifests as an issue during type generation. Is that what you're suggesting?

Yep that works - just some visibility into why CRDs may not be picked up successfully


fix typos in ReadMe

To be honest I did not think much about this. I did notice the first typo myself ("goals") but the other one was spotted by copilot (I saw an icon on the bottom right of my screen that I had never noticed before, so I gave it a try, just asking "check spelling").


Adding Bootstrapping CI 95% to InstanceMetric and GlobalMetric

It seems the test fails.   Is it deterministic?
AssertionError: global score must be equal, got {"exact_match": 0.33, "f1": 0.56, "f1_ci_high": 1.0, "f1_ci_low": 0.0, "score": 0.56, "score_ci_high": 1.0, "score_ci_low": 0.0, "score_name": "f1"} =/= {"exact_match": 0.33, "f1": 0.56, "f1_ci_high": 0.89, "f1_ci_low": 0.09, "score": 0.56, "score_ci_high": 0.89, "score_ci_low": 0.09, "score_name": "f1"}

It seems the test fails. Is it deterministic?
AssertionError: global score must be equal, got {"exact_match": 0.33, "f1": 0.56, "f1_ci_high": 1.0, "f1_ci_low": 0.0, "score": 0.56, "score_ci_high": 1.0, "score_ci_low": 0.0, "score_name": "f1"} =/= {"exact_match": 0.33, "f1": 0.56, "f1_ci_high": 0.89, "f1_ci_low": 0.09, "score": 0.56, "score_ci_high": 0.89, "score_ci_low": 0.09, "score_name": "f1"}

I updated the expected values. I thought i eliminated all causes for random behavior, but perhaps there is still some issue left.
I think once the PR is merged, if this issue happens again, we will know what broke it. This can help in identifying the root cause.

It seems the test fails. Is it deterministic?
AssertionError: global score must be equal, got {"exact_match": 0.33, "f1": 0.56, "f1_ci_high": 1.0, "f1_ci_low": 0.0, "score": 0.56, "score_ci_high": 1.0, "score_ci_low": 0.0, "score_name": "f1"} =/= {"exact_match": 0.33, "f1": 0.56, "f1_ci_high": 0.89, "f1_ci_low": 0.09, "score": 0.56, "score_ci_high": 0.89, "score_ci_low": 0.09, "score_name": "f1"}

I updated the expected values. I thought i eliminated all causes for random behavior, but perhaps there is still some issue left. I think once the PR is merged, if this issue happens again, we will know what broke it. This can help in identifying the root cause.

OK i think i found the issue here. The problem was that a single random generator was shared between all instacnces derived from MetricWithConfidenceInterval. Changed it such that the generators are separate here.


Add images to tensorboard

Adds support to plot images of the first batch of the validation set to tensorboard

@jerpint : still have to check this PR (and some of the others), but I was wondering if we are getting too specific on the current toy task (like, here we assume we will work with images).
In the end, the toy task will be erased in the first week or work (or something like that), to make space for the real task.
But again, not sure if this PR is also doing more stuff.. I will be back later on this PR.

This PR uses a callback to show how to log an image to tensorboard, so it can easily be removed by simply removing the callback, and consulted to find out how to do it, but good point, we don't want to overdo it either. Not sure what the best tradeoff would be

This PR uses a callback to show how to log an image to tensorboard, so it can easily be removed by simply removing the callback, and consulted to find out how to do it, but good point, we don't want to overdo it either. Not sure what the best tradeoff would be

this is a perfect example for code logic that should be in the new repository that we will create.
So it does not weight on the cookiecutter, but it's still available.
Do you see any disadvantages with that?

Once we have cookiecutter in a stable state, i will probably maintain a separate repo with a bunch of killer features

stale, closing


KAFKA-18100: Fix testDeserializationErrorFailsTheLoading

JIRA: KAFKA-18100
This test fails due to the error flow change in #16898. To fix it, we should update the assertion message.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@frankvicky Could you please focus on fixing CoordinatorLoaderImplTest instead of creating a duplicate PR to #17954?

close as #17954 will include it


useHover: Function components cannot have refs. Did you mean to use React.forwardRef()?

You can see the issue here.
This code works fine (to validate the styled component functionality):
const App = () => (

    <Help visible={false}>HELP HERE</Help>

Hello

)

You have the incorrect deconstructed order :)
const [vis1, refVis1] = useHover(200, 200);
should be
const [refVis1, vis1] = useHover(200, 200);
Happy to help!

Ah, you are right. Sorry, I was evaluating a few hover-hook libs. that totally works


Drop old and add new Java docs submodule

Supersedes #978
This is a temporary measure until we settle #989

Preview: https://deploy-preview-995--opentelemetry.netlify.app/docs/instrumentation/java/

/cc @cartermp

Thanks for the review and approval @cartermp. Merging ...


Add decoding Strategies to PushSecret

Problem
When I use a PushSecret, the existing K8 secret is always base64 decoded and written to the vault in plain text.
I have some binary secrets that I need to store in base64-encoded in vault.
Possible solution
add decodingStrategy like in ExternalSecret to a PushSecret
---
apiVersion: external-secrets.io/v1alpha1
kind: PushSecret
metadata:
  name: pushsecret-example-binary
  namespace: example
spec:
  refreshInterval: 10s
  secretStoreRefs:
    - name: vault
      kind: SecretStore
  selector:
    secret:
      name: example-binary-cert
  data:
    - match:
        secretKey: ca.password
        decodingStrategy: Base64        # decode the k8 secret and store the result as plain text in vault
        remoteRef:
          remoteKey: example/cert
          property: ca.password
    - match:
        secretKey: ca.p12
        decodingStrategy: None          # don't decode the k8 secret and store the result base64 encoded in vault
        remoteRef:
          remoteKey: example/cert
          property: ca.p12
    - match:
        secretKey:  ca.crt
        decodingStrategy: Base64        # decode the k8 secret and store the result as plain text in vault
        remoteRef:
          remoteKey: example/cert
          property: ca.crt

Once https://github.com/external-secrets/external-secrets/pull/2926 lands, you'll have the ability to do templating for push secret. As I understand it, templating provides b64dec. So you should be able to use that I think 🤔


split cm-matched-string into two css classes

with the latest update, matches to the current string + matches to the current selection both get cm-matched-string class. this makes it impossible to style them separately, even though it would be useful to use more subtle styling for current-string-matches and more emphasized styling for current-selection-matches.

Added back cm-matched-word and cm-current-word in 0.1.1

thanks :)