Unable to compile FakeSign

sircmpwn@makase ~/s/roslyn master> xbuild Src/Tools/Source/FakeSign/FakeSign.csproj
XBuild Engine Version 12.0
Mono, Version <IP_ADDRESS>
Copyright (C) 2005-2013 Various Mono authors

Build started 2/4/2015 3:13:55 PM.
__________________________________________________
Project "/home/sircmpwn/sources/roslyn/Src/Tools/Source/FakeSign/FakeSign.csproj" (default target(s)):
/home/sircmpwn/sources/roslyn/Src/Tools/Source/FakeSign/FakeSign.csproj:  warning : Project has unknown ToolsVersion '14.0'. Using the default tools version '2.0' instead.
    Target PrepareForBuild:
        Configuration: Debug Platform: AnyCPU
    Target GetFrameworkPaths:
/usr/lib/mono/2.0/Microsoft.Common.targets:  warning : TargetFrameworkVersion 'v4.5' not supported by this toolset (ToolsVersion: 2.0).
    Target GenerateSatelliteAssemblies:
    No input files were specified for target GenerateSatelliteAssemblies, skipping.
    Target GenerateSyntaxModel:
    No output files were specified for target GenerateSyntaxModel, skipping.
    Target GenerateSyntaxModelTests:
    No output files were specified for target GenerateSyntaxModelTests, skipping.
    Target GenerateBoundTree:
    No output files were specified for target GenerateBoundTree, skipping.
    Target GenerateErrorFacts:
    No output files were specified for target GenerateErrorFacts, skipping.
    Target GenerateAssemblyInfoFile:
: error : Error initializing task WriteCodeFragment: Not registered task WriteCodeFragment.
        Build FAILED.
        Warnings:
        /home/sircmpwn/sources/roslyn/Src/Tools/Source/FakeSign/FakeSign.csproj (default targets) ->
            /home/sircmpwn/sources/roslyn/Src/Tools/Source/FakeSign/FakeSign.csproj:  warning : Project has unknown ToolsVersion '14.0'. Using the default tools version '2.0' instead.
        /home/sircmpwn/sources/roslyn/Src/Tools/Source/FakeSign/FakeSign.csproj (default targets) ->
        /usr/lib/mono/2.0/Microsoft.Common.targets (GetFrameworkPaths target) ->
            /usr/lib/mono/2.0/Microsoft.Common.targets:  warning : TargetFrameworkVersion 'v4.5' not supported by this toolset (ToolsVersion: 2.0).
        Errors:
        /home/sircmpwn/sources/roslyn/Src/Tools/Source/FakeSign/FakeSign.csproj (default targets) ->
        /home/sircmpwn/sources/roslyn/Src/Tools/Microsoft.CodeAnalysis.Toolset.Open/Targets/GenerateAssemblyInfo.targets (GenerateAssemblyInfoFile target) ->
            : error : Error initializing task WriteCodeFragment: Not registered task WriteCodeFragment.
             2 Warning(s)
             1 Error(s)
        Time Elapsed 00:00:00.1682610

I installed the MS PCL here:
sircmpwn@makase ~/s/roslyn master> ls /usr/lib/mono/xbuild-frameworks/.NETPortable/v4.5/Profile/Profile7
GlobalDTARSettings.proj*                    System.dll*                         System.Reflection.dll*                              System.ServiceModel.NetTcp.dll*
Microsoft.CSharp.dll*                       System.Dynamic.Runtime.dll*         System.Reflection.Extensions.dll*                   System.ServiceModel.Primitives.dll*
Microsoft.VisualBasic.dll*                  System.Globalization.dll*           System.Reflection.Primitives.dll*                   System.ServiceModel.Security.dll*
mscorlib.dll*                               System.IO.Compression.dll*          System.Resources.ResourceManager.dll*               System.ServiceModel.Web.dll*
RedistList/                                 System.IO.dll*                      System.Runtime.dll*                                 System.Text.Encoding.dll*
SupportedFrameworks/                        System.Linq.dll*                    System.Runtime.Extensions.dll*                      System.Text.Encoding.Extensions.dll*
System.Collections.Concurrent.dll*          System.Linq.Expressions.dll*        System.Runtime.InteropServices.dll*                 System.Text.RegularExpressions.dll*
System.Collections.dll*                     System.Linq.Parallel.dll*           System.Runtime.InteropServices.WindowsRuntime.dll*  System.Threading.dll*
System.ComponentModel.Annotations.dll*      System.Linq.Queryable.dll*          System.Runtime.Numerics.dll*                        System.Threading.Tasks.dll*
System.ComponentModel.DataAnnotations.dll*  System.Net.dll*                     System.Runtime.Serialization.dll*                   System.Threading.Tasks.Parallel.dll*
System.ComponentModel.dll*                  System.Net.Http.dll*                System.Runtime.Serialization.Json.dll*              System.Windows.dll*
System.ComponentModel.EventBasedAsync.dll*  System.Net.NetworkInformation.dll*  System.Runtime.Serialization.Primitives.dll*        System.Xml.dll*
System.Core.dll*                            System.Net.Primitives.dll*          System.Runtime.Serialization.Xml.dll*               System.Xml.Linq.dll*
System.Diagnostics.Contracts.dll*           System.Net.Requests.dll*            System.Security.Principal.dll*                      System.Xml.ReaderWriter.dll*
System.Diagnostics.Debug.dll*               System.Numerics.dll*                System.ServiceModel.dll*                            System.Xml.Serialization.dll*
System.Diagnostics.Tools.dll*               System.ObjectModel.dll*             System.ServiceModel.Duplex.dll*                     System.Xml.XDocument.dll*
System.Diagnostics.Tracing.dll*             System.Reflection.Context.dll*      System.ServiceModel.Http.dll*                       System.Xml.XmlSerializer.dll*

You need to use master mono as described in README

I am using master mono, that's not the problem here.

You are using Mono, Version <IP_ADDRESS> not master

Yeah, you're right. I compiled it incorrectly.


Does not use native trash functionality (unlike Atom)

I just lost an hour's work because I used the quick delete to delete the wrong file. I trusted this package to use the native trash functionality (the trashcan on OS X), which Atom does. However, looking at the code, your package actually permanently deletes the file, and there's no undo operation.
This, in my mind, makes its delete functionality completely unusable.
If this is intended behavior, I hope you will at least put a large bold warning in the readme to warn off other users.

I love all the other quick file actions - really really useful.
Agreed this point though. I recommend for anyone else coming across this to add the following to your keymap.cson to trash the current file:
# avoid permanent deletion used by Quick File Actions package = prefer Atom's Tree View: Remove
'atom-workspace':
  'ctrl-alt-f d': 'tree-view:remove'

You lose some of the path resolving abilities of quick-file-actions for deletion, but for me at least I'm generally only using keyboard shortcuts in atom to delete the current open file. Bonus functionality: if the file has no changes/was saved - Atom will close the tab for you after trashing it :balloon:

Hilariously enough github didn't notify me of new issues in this repo.
Sorry for the massive delay, but the feature has been implemented. It's now the default behaviour to send files to the trash bin, but I've also added an option for that.


Huge production files

First, I truly want to thank you for carrying the torch for erikas. This is one of the best repos I have seen in years.
But unless I am doing something wrong, the main.js file is huge as is the stylesheet file. I tried to use common-chunks-plugin (webpack 3.3) and while it does break up the files, and the css files do work in smaller bundles, the scripts don't work, and I get a console error: "webpackJsonp is not defined".
Are you aware if I am doing something wrong, or, do you have any intentions soon to break up the script files into smaller packages as well as separating out the vendor batch from the app?
Thanks for your attention to this question.

+1 Thank you for carrying the torch for erikas!!!
Same issue here. my main js is 1.5M, and main.css is 856K (which is not minified as well.)
The first load seems to be slow and see a couple seconds of white screen before rending. See my site here: https://shopecific.com/
I was using erikas's version and it seems to be faster. It's demo site loads very faster: https://react-redux.herokuapp.com/

Comparing these two demo sites:
https://react-hot-example.herokuapp.com/ (@bertho) - use Chrome hard refresh, see 1 sec blank page
https://react-redux.herokuapp.com/ (@erikas) - use Chrome hard refresh, I don't see the blank issue.
Bertho's one is using "Service Worker". Could be that causing slowness? #48

I have this on '/' on production:

The second blank is actually due to the service worker, because it does not wait for the server response.
On the other hand the service-worker helps me to load my page in 480ms and that of Erikras load in 1.70-1.80s.


Trailing space in translation output from API

A trailing space was introduced. Before:
{
    "context": [
        {
            "id": "ibm",
            "score": 0.048597444
        },
        {
            "id": "europarl",
            "score": 0.007114725
        }
    ],
    "took": 13,
    "translation": "mondo"
}

Current develop branch:
[david@hopper MMT]$ curl "http://localhost:8045/translate?q=world&context=computer" | python -mjson.tool
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   116  100   116    0     0    292      0 --:--:-- --:--:-- --:--:--   292
{
    "context": [
        {
            "id": "ibm",
            "score": 0.048597444
        },
        {
            "id": "europarl",
            "score": 0.007114725
        }
    ],
    "took": 2,
    "translation": "mondo "
}

Bug solved in branch features/xmessage I'm going to close this issue as soon as I merge the work done.

fixed in develop branch


Openmodelica's compiler doesn't have access to Standard library when run in CLI

Describe the bug
When running the Openmodelica compiler omc, it doesn't have access to the modelica standard library. Probably just some entry similar to this one for OMEdit is missing:
https://github.com/NixOS/nixpkgs/blob/634141959076a8ab69ca2cca0f266852256d79ee/pkgs/applications/science/misc/openmodelica/combined/default.nix#L16-L21
Steps To Reproduce
No time right now but I wanted to report in parallel to #173138 so that both could be fixed at the same time. I will add a detailed description later if required.
Expected behavior
The omc binary should have access to the Open Modelica library as well (e.g. through the associated environment variable)
Notify maintainers
@balodja
@smironov

Somebody is finally interested in OM on the NixOS! Thanks, I'll take a look.


Remove copyrighted image

Image in README is copyrighted because no license was provided by the author of the animation. This pull request fixes that.

@aodhneine looks good to me! Thank you so much! :+1:


Make emissary-ingress-apiext optional

Please describe your use case / problem.
I want to install Emissary-ingress without being forced to use emissary-ingress-apiext.
Describe the solution you'd like
There is a way to install Emissary-ingress with getambassador.io/v3alpha1 CRDs only.
Additional context
I am installing Emissary-ingress on a cluster that do not have any getambassador.io/v2 custom resources, so I don't need support for migrating between versions.

Hi @Sh1ftry, could you let us know what kind of issues this creates for you when it is included by default?

It's an additional component in the cluster, which needs to be monitored, regularly updated and in case of any problems it can cause disruptions in the cluster as mentioned in your documentation:
If the emissary-ingress-apiext Deployment's Pods all stop running, you will not be able to use getambassador.io/v3alpha1 CRDs until restarting the emissary-ingress-apiext Deployment.

The above makes it less appealing to companies with strict regulations on what can and cannot be deployed to their clusters. This could easily be solved just by allowing users to simply disable emissary-ingress-apiext in case it's not needed.

Agreed I would prefer to have this opt-out if possible, it's an external dependency we don't need as we can manage the CRD install ourselves.
We've also seen weird errors where the CRDs fail with
dry-run failed, error: conversion webhook for getambassador.io/v3alpha1, Kind=Host failed: Post "https://emissary-apiext.emissary-system.svc:443/webhooks/crd-convert?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)...

Yeah +1 to this request. I experienced a similar issue to what Alan01252 is describing above. This did help (https://stackoverflow.com/a/70608787/18679153) but I shouldn't have to manually change my Firewall rules to permit apiext to run. I'd rather not have the main source for all production traffic to be reliant on a service that might not actually be needed in my particular use case.
I do think it's a fantastic addition, especially with assisting those moving from Version X to Version Y, but I think it'd be a better place to have it as an optional deployment that can be enabled / disabled in the values file (as opposed to installing it via the https://app.getambassador.io/yaml/emissary/2.2.2/emissary-crds.yaml file).

The webhook is configured in the CRD definition. I think if you remove the block shown below from each of the CRDs, then the emissary-ingress-apiext resources should no longer be required. I haven't tested this yet since I ran into this issue when I was vendoring the CRD definitions to our internal environment and saw it included more resources than I expected.
spec:
  conversion:
    strategy: Webhook
    webhook:
      clientConfig:
        service:
          name: emissary-apiext
          namespace: emissary-system
      conversionReviewVersions:
      - v1beta1

What is the status here? I also came across this and it feels a bit like a trojan horse to have this included in a crds file. The helm chart didn't have any reference to it.
Also it does not have any resource requests, security context and readiness probe defined

We've also come across this. We fully migrated from 1.x to 2.x and also believe the api-ext deploy should be optional. Not sure if anyone else noticed this but our kube-api pods get spammed  by api-ext for failing to list/watch mapping/module/tlscontext.
E0701 16:39:38.022190       1 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=Mapping: conversion webhook for getambassador.io/v2, Kind=Mapping failed: no kind "Mapping" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...
E0701 16:39:38.117232       1 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=Module: conversion webhook for getambassador.io/v2, Kind=Module failed: no kind "Module" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...
E0701 16:39:38.721206       1 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=TLSContext: conversion webhook for getambassador.io/v2, Kind=TLSContext failed: no kind "TLSContext" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...
E0701 16:39:39.025949       1 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=Mapping: conversion webhook for getambassador.io/v2, Kind=Mapping failed: no kind "Mapping" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...
E0701 16:39:39.121784       1 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=Module: conversion webhook for getambassador.io/v2, Kind=Module failed: no kind "Module" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...
E0701 16:39:39.726207       1 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=TLSContext: conversion webhook for getambassador.io/v2, Kind=TLSContext failed: no kind "TLSContext" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...

Hello, I am doing a fresh installation of emissary-ingress on EKS via helm and am running into issues with the pods being able to POST to the apiext service. I don't have any necessity for v2 CRDs either and I can't figure out what is causing the problems I'm facing. It would be great to make this service optional as sometimes this issue occurs and sometimes not and I cant seem to figure out what the pattern is, but it is becoming a hindrance to my getting started.

@Sh1ftry I get
* status.storedVersions[0]: Invalid value: "v1": must appear in spec.versions when trying to remove that section
any idea how you were able to edit the CRD ?

reiterating what others have said - installing a new cluster, this was by far the most problematic part of the install.
even now with everything ~working - my argocd installation continually reloads emissary due to crd mismatches - which may/not be related

I was investigating why my log ingest bill had a huge, inexplicable jump. Turns out it's due to gigabytes of these logs after an emissary "upgrade" last week:

E0701 16:39:38.022190       1 cacher.go:419] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list getambassador.io/v1, Kind=Mapping: conversion webhook for getambassador.io/v2, Kind=Mapping failed: no kind "Mapping" is registered for version "getambassador.io/v1" in scheme "/go/cmd/apiext/main.go:50"; reinitializing...

The entire CRD migration path has been an absolute nightmare, time suck, and now money pit. Jeez.

This did help (https://stackoverflow.com/a/70608787/18679153) but I shouldn't have to manually change my Firewall rules to permit apiext to run. I'd rather not have the main source for all production traffic to be reliant on a service that might not actually be needed in my particular use case.

I can confirm that adding the port to my cluster's master firewall resolved my issue, but I also agree that I shouldn't be forced to use the migration path if I have no v2 resources.

So to me, it seems this api-ext setup is to allow backwards compatibility to not have to carry multiple versions of the CRD for people who use older versions of ambassador/emissary. It also seems like it may convert stuff in the other direction. We are on v2 CRDs atm, so I have patched them myself to remove all v3 and v1 things as well as the webhook. Perhaps these are useful to others: https://gist.github.com/sharkymcdongles/19d4d729ceeda694c3bc2e5737c99ea3
I only tested them with my setup, but it seems to work as far as I have tested so far albeit I just made these change 5 min ago. :D

+1 for making apiext optional

+1

+1


Configuration#5 : Step#6: concatenate and shuffle MATTER and LBT dataset

Using sbatch jetscape-ml-tensorflow-nn-dataset-concatenate-shuffler.sh
Making final dataset, and shuffled dataset files as output

no script output


Change FAB placement

I want to merge this change because...
Resolves #1383
Pull Request Checklist

[x] Privileged views and APIs are guarded by proper permission checks.
[x] All visible strings are translated with proper context.
[x] All data-formatting is locale-aware (dates, numbers, and so on).
[x] Database queries are optimized and the number of queries is constant.
[x] The changes are tested.
[x] The code is documented (docstrings, project documentation).
[x] Python code quality checks pass: pycodestyle, pydocstyle, pylint.
[x] JavaScript code quality checks pass: eslint.

Codecov Report

Merging #1394 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1394   +/-   ##
======================================
  Coverage    82.9%   82.9%
======================================
  Files         128     128
  Lines        5775    5775
  Branches      663     663
======================================
  Hits         4788    4788
  Misses        830     830
  Partials      157     157

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 017da02...c58aeaa. Read the comment docs.

On the product list page:

While on the Sales list:

@dominik-zeglen Please make sure that all list views are consistent.


Burnout Paradise → the sky is not well rendered

with d9vk:

without d9vk:

System information

GPU: Nvidia GT 730M
Driver: 435-17 (beta)
Wine version: Proton 4.11
DXVK version: #807

Apitrace file(s)
https://mega.nz/#!jzQ2XQJa!5XP-i6QaTUjWaLVRpSOE7pAZwyFawg7FnFcW9ikGh1s
Log files
steam-24740-d3d9.log
steam-24740-d9vk.log

This might be a regression related to the fixed function fog. I remember I tried the game at some point and it was fine.

The issue about the sky was introduced with #705, so yes, it's a regression.

I can reproduce it using the build 704.

The sky issue is on master and #375 fixes the background on the main menu.

Tested with #845 and everything is perfect :+1:


[4.1] Fixing FetchOperation behaviour when clauses are already applied.

Like described in #2882
If you use fetch with pre-defined conditions that will mess with the way we add searchable conditions to the query.
The description provided in the issue is pretty explanatory to understand what is going wrong. I hope my comment inline also helps.
Best,
Pedro

A new inspection was created.

The inspection completed: 1 new issues

Great job.


Color disappears from TransformControls after first interaction

three version: 0.128.0
@react-three/fiber version: 6.0.19
@react-three/drei version: 4.3.3
node version: v12.21.0
npm (or yarn) version: 7.11.2

Problem description:
Currently, TransformControls start with a color-coded set of axes that can be clicked and dragged. However, after the first mouse interaction (either hover or click/drag), the color disappears on the interacted axis, and the other axes disappear.
Relevant code:
This behavior is currently visible in the storybook for TransformControls.
Suggested solution:
This may actually be an issue with three-stdlib.

duplicate of #60 which i'm closing in favour of because it has a clearer description


Release Production API Support (v1 to v2)

See this article for what to do:
https://api.random.org/migration
Basically:
You will need to upgrade your clients to use Release 2 of the API. If you are still using Release 1, you can switch to Release 2 by changing the URL endpoint in your client from the following:
https://api.random.org/json-rpc/1/invoke
To the following:
https://api.random.org/json-rpc/2/invoke

See commit 606f176725b99dfe9392d0252615ff4586761bd6


No HANA Cloud Database as part of this tutorial.

This workshop is completely unusable.  Nowhere in the workshop does it contain instructions for setup of SAP HANA Cloud.  How can anyone attach their project to an HDI container and deploy when you haven't guided them to setup HANA Cloud at all.
You just get this error of course at this point

Added as a part of prerequisite


Android 10: System Gesture Exclusion Rects

Description
Exposes setSystemGestureExclusionRects and getSystemGestureExclusionRects to the Flutter framework.
Sample code
When _setRects is true, the top left side of the application ignores system level gesture navigation. Otherwise, it takes precedence over the app's gestures.
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  bool _setRects = true;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(),
      body: Column(
        mainAxisAlignment: MainAxisAlignment.center,
        children: <Widget>[
          Center(
            child: RaisedButton(
              onPressed: () async {
                List<Rect> rect;
                if (_setRects)
                  rect = null;
                else
                  rect = [Rect.fromLTRB(0, 0, 100, 100)];

                setState(() {
                  _setRects = !_setRects;
                });
                await SystemGestures.setSystemGestureExclusionRects(
                  rects: rect,
                  devicePixelRatio: MediaQuery.of(context).devicePixelRatio,
                );
              },
              child: Text('Toggle Exclusion Rects'),
            ),
          ),
          Text(_setRects ? 'On' : 'Off'),
        ],
      ),
    );
  }
}

Related Issues
Fixes https://github.com/flutter/flutter/issues/39858
Tests
I added the following tests:

Control test for setSystemGestureExclusionRects
Control test for getSystemGestureExclusionRects

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

After some discussion on the discord channel and an offline chat with @HansMuller, we've decided that it doesn't make sense to expose this via the framework and would be better for this to be a plugin because it is very specific to just one platform, and only Android 10+ versions of that one platform. I'll close this PR and make a note on the original issue.


Gracefully handle when apt-get update fails

People love to put broken PPAs in their apt sources.  Not really sure why, but to each his or her own, I guess.
Anyway, when that happens, crouton should do something other than fall flat on its face.  Some options (in order of increasing difficulty:

Simply print out some helpful tips about how to correct
Blindly ask if the user wants to disable all of their PPAs, then flood the sources.list/sources.list.d with #'s
Monitor apt-get update output, grep for the failing PPA, then (ask?) comment out the PPA in sources and try again.

The third is clearly the best, and I don't think it would be particularly hard to do, but there may not be enough people hitting these kinds of issues to make it really worthwhile.

Package up Crouton with a minimal stateful distro. Update it every year or so. If the user needs a specific update of something, they can apt-get install it and be responsible for new PPAs that they've added from the base complete crouton distribution. I never understood why the Crouton versions of xfce target (for ARM) are missing dozens of utilities that are on the minimal x86 cd or usb mini live distros, other than oversight for the arm (this is with precise)

I don't really understand what you're suggesting.    Not everyone wants to burn through their limited storage that way, though...

Since creating a new chroot with https:// and wget script commands takes a good hour or so, and I see the benefits of this - small crouton and latest everything when their chroot finishes, but it depends on increasingly unreliable connections, people being in the right places at the right time, proxies not blocking, PPA servers synced and running, etc.
If Crouton included the base image files in a big one time download, then creating chroots could be done without a connection, [or optional download upgrades, if online with fast connection] and faster (disk to disk) transfers.
About the missing utilities, they are minor, but I'm willing to document them if you like, I'll load a barebones 3 or 4 year old 12.04 ubuntu 32-bit x86 release on a pc, then, an xfce chroot on the chromebook, and things like nano, vim, gcc, and basically the core of bash and linux are just not there, they have to be installed with apt-get install .

'crouton' gives you the option '-d -f' to download a bootstrap file for your release which saves installation time and it doesn't need to be updated.

Yeah, exchanging one period of download for another, higher maintenance one doesn't really seem like a win to me.  Dennis' trick is probably what you want.  You can maintain a repo of generated bootstraps and download them on demand.
This is all OT though.

OK, thanks @DennisLfromGA I am creating a chroot now with -t xfce,xfce-desktop when done, I will use the -d -f to save a local bootstrap file, and see how much time that saves for new chroot installs.
@dnschneid yeah, sorry for going OT, but I think a Crouton distro could be useful in instances where connectivity is less than optimal. Am going to d/l the bootstrap files shortly though.

IMO I would go for number 1, just let people correct their own mistakes to learn from them. Also, I didn't look at it deeply, but wouldn't number 3 give "problems" if their are other distros added to crouton which will use different package managers?

Simply print out some helpful tips about how to correct

This is how I handle this kind of issues on Arch: some (rare) Arch updates require manual intervention. I think most people who manually add PPA are also able to remove it without much help.

@divx118 > IMO I would go for number 1, just let people correct their own mistakes to learn from them.
@drinkcat > I think most people who manually add PPA are also able to remove it without much help.
I also think #1 is the best way to go for both of those reasons.

wins.

Here's part of a routine I picked up off the internet.
I think the idea is worthy, maybe some of it could be used.
If we want to be more aggressive, just remove the comment.
( I don't know if it's "easy-as-pie" though... ;)
sudo rm /tmp/update.txt
sudo apt-get update | tee /tmp/update.txt 2>&1
awk '( /W:/ && /launchpad/ && /404/ ) { print substr($5,26) }' /tmp/update.txt > /tmp/awk.txt
awk -F '/' '{ print $1"/"$2 }' /tmp/awk.txt > /tmp/awk1.txt
sort -u /tmp/awk1.txt > /tmp/awk2.txt; tput sgr0
if [ -s /tmp/awk2.txt ]; then
  printf "PPA's that need to be removed\n%s\n" "$(cat /tmp/awk2.txt)"
  while read -r line
  do
    echo "sudo add-apt-repository -r ppa:$line"
  done < /tmp/awk2.txt > /tmp/out
# sudo bash /tmp/out
fi

@DennisLfromGA What about keeping a known good backup copy of /etc/apt/sources.list and if something is broken, prompt the user to revert to the default, but that they will have to add their package back again after they restore to a known good install?
http://askubuntu.com/questions/496495/can-a-ppa-repository-be-added-to-etc-apt-source-list

I'm really not too well versed on ppa's and such, someone else might be a
better source.
On Sun, Apr 26, 2015 at 6:56 PM, tedm<EMAIL_ADDRESS>wrote:

@DennisLfromGA https://github.com/DennisLfromGA What about keeping a
known good backup copy of /etc/apt/sources.list and if something is broken,
prompt the user to revert to the default, but that they will have to add
their package back again after they restore to a known good install?
http://askubuntu.com/questions/496495/can-a-ppa-repository-be-added-to-etc-apt-source-list
—
Reply to this email directly or view it on GitHub
https://github.com/dnschneid/crouton/issues/1365#issuecomment-96443972.

--
DennyL@GMail

Soooo, I ended up just ignoring apt-get update failures.  We could print out a helpful message, but I don't think anybody would see it.


Bug: Type that uses Ash.Type.NewType defines multiple GraphQL types with the same name.

Having the following type
defmodule MyApp.Types.DayOfWeek do
  @moduledoc false

  use Ash.Type.NewType,
    subtype_of: :atom,
    constraints: [one_of: [:monday, :tuesday, :wednesday, :thursday, :friday, :saturday, :sunday]]

  def graphql_input_type(_), do: :day_of_week
  def graphql_type, do: :day_of_week
  def graphql_type(_), do: :day_of_week
end

That is used in two resources:
defmodule ResourceA do
  ...
  attributes do
    ...
    attribute :days_of_week, {:array, MyApp.Types.DayOfWeek}
  end
end

defmodule ResourceB do
  ...
  attributes do
    ...
    attribute :day_of_week, MyApp.Types.DayOfWeek}
  end

  relationships do
    belongs_to :a_resource, ResourceA, allow_nil?: false
  end
end

Causes the GraphQL type to be defined multiple times resulting in the following error:
== Compilation error in file lib/my_app/schema.ex ==
** (Absinthe.Schema.Error) Compilation failed:
---------------------------------------
## Locations
my_app/deps/ash_graphql/lib/resource/resource.ex:2358
my_app/deps/ash_graphql/lib/resource/resource.ex:2358
my_app/deps/ash_graphql/lib/resource/resource.ex:2358
my_app/deps/ash_graphql/lib/resource/resource.ex:2358
my_app/lib/my_app/graphql/types/common_types.ex:63

Type name "DayOfWeek" is not unique.

References to types must be unique.

> All types within a GraphQL schema must have unique names. No two provided
> types may have the same name. No provided type may have a name which
> conflicts with any built in types (including Scalar and Introspection
> types).

Reference: https://github.com/facebook/graphql/blob/master/spec/Section%203%20--%20Type%20System.md#type-system
---------------------------------------

Clues after debugging
After some debugging I think it's because the NewType is being defined per resource as we can see in resource.ex:2297.
I've inserted IO.inspect into get_auto_enums and after resource.ex:2342 and when my type was based on Ash.Type.NewType it was in these inspects, but when I've switched back to Ash.Type.Enum it wasn't.
I'm guessing that it's being treated as "inline enum", so when you defined enum like this:
attribute :some_enum, :atom do
  constraints one_of: [:a, :b, :c]
end

because in these inspects I see "types" that are defined like this, the main difference is that for those it has unique name per resource.
It would work without defining def graphql_input, but for some reason to types defined like that the _input postfix isn't added like to those "inline enums", so there are same atoms returned for type_name and additional_type_name in resource.ex:2304.
When def graphql_input is defined, it uses this name everywhere, so there are more Locations with conflicts for Absinthe, as seen before.

This https://github.com/ash-project/ash_graphql/issues/73 should solve this issue once complete.


x/tools/containers/intsets: use the Sparse root block

Sparse has a root block but that block doesn't store any element information. So even very small sets (e.g. single element) will need to allocate another block on the heap. So (on a 64-bit arch) we have 56 bytes in the structure and another 56 bytes on the heap, just to represent a single value.
There is no reason to not use the root block itself to store bits. It could be always the block with the smallest offset.

@alandonovan

I can try to find some time to take a stab at this if folks agree it's a good idea.

Please do; it would certainly be a worthwhile optimization.  I tried this at some point in the past but the logic got rather messy so I abandoned it.

what about bitsets, a high performance pkg.

@dongweigogo - the usecase is different: Sparse supports arbitrary integers, bitsets looks like it allocates X bits if it contains value X.


fix: updated condition for adding kubectl apply synced timeline

Description
Updated condition for getting/adding kubectl apply synced timeline.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Local Environment
[x] Microk8s cluster

Checklist:

[x] The title of the PR states what changed and the related issues number (used for the release note).
[ ] Does this PR requires documentation updates?
[ ] I've updated documentation as required by this PR.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[x] I have tested it for all user roles.
[ ] I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

RCA: we were updating health status pipeline on basis of reconciliation time and kubectl apply synced timeline. In an edge case, if the sync status changes from succeeded to something else, kubectl apply synced timeline was not getting fetched and this was causing health timeline to not update whereas deployment status was getting updated since we had extra call for kubectl applly synced timeline there.


Allow long runs

if we want to allow > 2h long runs, we should not kill bootstrax before that time. Instead - only kill bootstrax if it is still running for a long time despite the run having ended

Coverage increased (+0.03%) to 93.212% when pulling 50c859c941f32a2c9fe596b119b750670a462b66 on increased_run_duration into 0c42a29ebc4be958815f6da97adca539564bd85d on master.


Default theme.toml throws error.

Describe the bug
Default UI looks horrible, wasn't able to navigate through menu so I decided to plug theme.toml to play around with
To Reproduce
I catch this behavior by creating default theme.toml
Expected behavior
Spotify player will run
Log and backtrace
spotify_player

Error: missing field `selection_background` for key `themes.palette` at line 148 column 1

Screenshots
Default settings give me this look

Environment

OS: macOS BigSur 11.6
Application version:  spotify-player 0.10.0
Application features: if applicable, provide cargo features used to build with spotify-player
cargo install spotify_player --features image --locked
Additional context

I guess you're referring to theme.toml in the examples folder. Recently, I made some changes to the theme structure, so you can look into this instead.

Default settings give me this look

The default theme shouldn't give such a look. Can you try running the app using different terminal? My initial guess is that it is because colors are not well supported by your terminal.

Problem  solved by switching off ANSI colors but everything turned black/white now

Related: https://github.com/aome510/spotify-player/issues/97. I think it will get better with the new upcoming release, in which I switched to use terminal default colors instead of defining custom themes.
You can try the latest build of master branch. In the meantime, I'll close this issue for now. Feel free to reopen if encountering related issues.


Add MetadataStatus per core schema in Metadata pydantic model

Is your feature request related to a problem? Please describe.
It would be nice to get a top level check of the status of each of the core schemas attached to a data asset (subject, procedures, rig, etc.) Some of the flags could be:
Describe the solution you'd like
It would be nice to get a top level check of the status of each of the core schemas attached to a data asset (subject, procedures, rig, etc.). For example, we could subject_status, rig_status, etc. to the Metadata model. Some of the flags could be:
Valid: There is a valid model
Invalid: There is an invalid model
Corrupt: There is a json file found with the data asset, but it's not possible to add the json file to DocDB for some reason
Missing: There is no json file found for this data asset (this may be redundant if we just the field to None)

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

After discussion w/ Saskia we've agreed to validate and store the state outside of the metadata itself. We're working on the validator code here: https://github.com/AllenNeuralDynamics/aind-metadata-validator/ and it will push to a redshift db (or somewhere else) and then we can use aind-data-access-api to expose the database.

Sounds good, I'll close this issue out then.


NullPointerException StreamingSheetReader caused by drawing "row"

I have found that if an xlsx file contains a drawing with element "row" this throws a null pointer (StreamingSheetReader.java:96) ( as drawing rows do not have a rowNumAttr
a correct row has the namespace http://schemas.openxmlformats.org/spreadsheetml/2006/main
a drawing row has the namespace http://schemas.openxmlformats.org/drawingml/2006/spreadsheetDrawing

this would be fixed by https://github.com/monitorjbl/excel-streaming-reader/pull/58


Added the ability to parse SNMP packets directly from a binary buffer

Thank you for sending a pull request.
Could you tell me more about this change?
(Are you trying to support the trap server of version 3?)

My goal was to parse SNMP from binary packets as opposed to having a client who actively passes the buffers. I didnt really have version 3 in mind, so im not really sure it will work in that case.

Sorry, I cannot merge this pull request for the following reasons:

The concept of this library is to provide a simple API to handle the SNMP messages. (It hides the parsing and validation of packet from library users)
It cannot be correctly parsing the second and any later packets of v3 because Parser is stateful. (concretely, usm.DiscoveryStatus)


Refreshing temporary credentials failed during advisory refresh period.

I'm not an experienced Python developer, so go easy on me ;-)  Noticing lots of credential refreshing errors in our logs
Aug 26 13:29:46 staging-serv-upload-v2-5cf6486f58-7lnzc serv-upload-v2 Traceback (most recent call last):
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 382, in _make_request
    self._validate_conn(conn)
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 1010, in _validate_conn
    conn.connect()
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connection.py", line 411, in connect
    self.sock = ssl_wrap_socket(
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/util/ssl_.py", line 449, in ssl_wrap_socket
    ssl_sock = _ssl_wrap_socket_impl(
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/local/lib/python3.8/ssl.py", line 500, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/local/lib/python3.8/ssl.py", line 1040, in _create
    self.do_handshake()
  File "/usr/local/lib/python3.8/ssl.py", line 1309, in do_handshake
    self._sslobj.do_handshake()
Aug 26 13:29:46 staging-serv-upload-v2-5cf6486f58-7lnzc serv-upload-v2 socket.timeout: _ssl.c:1091: The handshake operation timed out
Aug 26 13:29:46 staging-serv-upload-v2-5cf6486f58-7lnzc serv-upload-v2 During handling of the above exception, another exception occurred:
Aug 26 13:29:46 staging-serv-upload-v2-5cf6486f58-7lnzc serv-upload-v2 Traceback (most recent call last):
  File "/home/fd4b/.local/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
    resp = conn.urlopen(
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 755, in urlopen
    retries = retries.increment(
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/util/retry.py", line 532, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/packages/six.py", line 770, in reraise
    raise value
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 699, in urlopen
    httplib_response = self._make_request(
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 385, in _make_request
    self._raise_timeout(err=e, url=url, timeout_value=conn.timeout)
  File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 336, in _raise_timeout
    raise ReadTimeoutError(
Aug 26 13:29:46 staging-serv-upload-v2-5cf6486f58-7lnzc serv-upload-v2 urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='iam.cloud.ibm.com', port=443): Read timed out. (read timeout=5)
Aug 26 13:29:46 staging-serv-upload-v2-5cf6486f58-7lnzc serv-upload-v2 During handling of the above exception, another exception occurred:
Aug 26 13:29:46 staging-serv-upload-v2-5cf6486f58-7lnzc serv-upload-v2 Traceback (most recent call last):
  File "/home/fd4b/.local/lib/python3.8/site-packages/ibm_botocore/credentials.py", line 2627, in _protected_refresh
    metadata = self.auth_function()
  File "/home/fd4b/.local/lib/python3.8/site-packages/ibm_botocore/credentials.py", line 2529, in _default_auth_function
    response = requests.post(
  File "/home/fd4b/.local/lib/python3.8/site-packages/requests/api.py", line 119, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/home/fd4b/.local/lib/python3.8/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/home/fd4b/.local/lib/python3.8/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/fd4b/.local/lib/python3.8/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/home/fd4b/.local/lib/python3.8/site-packages/requests/adapters.py", line 529, in send
    raise ReadTimeout(e, request=request)
Aug 26 13:29:46 staging-serv-upload-v2-5cf6486f58-7lnzc serv-upload-v2 requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='iam.cloud.ibm.com', port=443): Read timed out. (read timeout=5)

WARNING:ibm_botocore.credentials:Refreshing temporary credentials failed during advisory refresh period.
Traceback (most recent call last):
File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 445, in _make_request
six.raise_from(e, None)
File "", line 3, in raise_from
File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 440, in _make_request
httplib_response = conn.getresponse()
File "/usr/local/lib/python3.8/http/client.py", line 1332, in getresponse
response.begin()
File "/usr/local/lib/python3.8/http/client.py", line 303, in begin
version, status, reason = self._read_status()
File "/usr/local/lib/python3.8/http/client.py", line 264, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/usr/local/lib/python3.8/socket.py", line 669, in readinto
return self._sock.recv_into(b)
File "/usr/local/lib/python3.8/ssl.py", line 1241, in recv_into
return self.read(nbytes, buffer)
File "/usr/local/lib/python3.8/ssl.py", line 1099, in read
return self._sslobj.read(len, buffer)
socket.timeout: The read operation timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/fd4b/.local/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 755, in urlopen
retries = retries.increment(
File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/util/retry.py", line 532, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/packages/six.py", line 770, in reraise
raise value
File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 447, in _make_request
self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
File "/home/fd4b/.local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 336, in _raise_timeout
raise ReadTimeoutError(
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='iam.cloud.ibm.com', port=443): Read timed out. (read timeout=5)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/fd4b/.local/lib/python3.8/site-packages/ibm_botocore/credentials.py", line 2627, in _protected_refresh
metadata = self.auth_function()
File "/home/fd4b/.local/lib/python3.8/site-packages/ibm_botocore/credentials.py", line 2529, in _default_auth_function
response = requests.post(
File "/home/fd4b/.local/lib/python3.8/site-packages/requests/api.py", line 119, in post
return request('post', url, data=data, json=json, **kwargs)
File "/home/fd4b/.local/lib/python3.8/site-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/home/fd4b/.local/lib/python3.8/site-packages/requests/sessions.py", line 542, in request
resp = self.send(prep, **send_kwargs)
File "/home/fd4b/.local/lib/python3.8/site-packages/requests/sessions.py", line 655, in send
r = adapter.send(request, **kwargs)
File "/home/fd4b/.local/lib/python3.8/site-packages/requests/adapters.py", line 529, in send
raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='iam.cloud.ibm.com', port=443): Read timed out. (read timeout=5)

Having local issues creating a PR - may I suggest something like the below as a solution to enable us to override the default of 5 seconds.
credentials.py
...
...
...

class DefaultTokenManager(TokenManager):
    """A default implementation of token manager.
    Retreives token on first use and holds it in memory
    for further use. Background thread tries to refresh token
    prior to its expiration, so that main thread is always
    non-blocking and performant.
    :ivar API_TOKEN_URL: Default URL for IAM authentication.
    :ivar _advisory_refresh_timeout: The time at which we'll attempt to refresh, but not
        block if someone else is refreshing.
    :ivar _mandatory_refresh_timeout: The time at which all threads will block waiting for
        refreshed credentials.
    """
    API_TOKEN_URL = 'https://iam.cloud.ibm.com/identity/token'
    _advisory_refresh_timeout = 0
    _mandatory_refresh_timeout = 0
    REFRESH_OVERRIDE_IN_SECS = 0 # force refresh in this number of secs
    DEFAULT_AUTH_FUNCTION_TIMEOUT = 5

    ...
    ...
    ...

    def get_default_auth_function_timeout():
        """
        Return the class variable DEFAULT_AUTH_FUNCTION_TIMEOUT
        This variable represents the timeout value
        when requesting a new auth token
        """
        return DefaultTokenManager.DEFAULT_AUTH_FUNCTION_TIMEOUT

    def set_default_auth_function_timeout(timeout=5):
        """
        Assign the class variable DEFAULT_AUTH_FUNCTION_TIMEOUT
        Overrides the default timeout (5 seconds) when requesting
        a new auth token
        :param timeout: The timeout value in seconds when requesting a new auth token
        :return: Old timeout value.
        """
        old_timeout = DefaultTokenManager.DEFAULT_AUTH_FUNCTION_TIMEOUT
        DefaultTokenManager.DEFAULT_AUTH_FUNCTION_TIMEOUT = timeout
        return old_timeout

    ...
    ...
    ...

    def _default_auth_function(self):
        response = requests.post(
                                 url=self._get_token_url(),
                                 data=self._get_data(),
                                 headers=self._get_headers(),
                                 timeout=DefaultTokenManager.DEFAULT_AUTH_FUNCTION_TIMEOUT,
                                 proxies=self.proxies,
                                 verify=self.get_verify())

        if response.status_code != httplib.OK:
            _msg = 'HttpCode({code}) - Retrieval of tokens from server failed.'.format(code=response.status_code)
            raise CredentialRetrievalError(provider=self._get_token_url(), error_msg=_msg)

        return json.loads(response.content.decode('utf-8'))

We are looking at your proposed solution now for possible inclusion. In most cases like this, we recommend users extend DefaultTokenManager to make the custom changes they want and then pass that into the token_manager parameter at client creation. In your case, the class would just inherit from DefaultTokenManager and override _default_auth_function to set whatever timeout you want. Note that while the create_client call does accept an auth_function parameter, which might seem perfect for this case, it does not work as you might expect. Extending DefaultTokenManager is the better approach.

Thanks Eric - I was hoping to avoid extending the class as some future breaking changes would expose me to being forced to address them, when all I want/ed is to provide a timeout value

We have implemented an override in 2.11.0, though the changelog mistakenly has omitted listing this. Can you verify and close this ticket?

Thank you Eric - I try to get it in and tested next sprint

Closing this ticket as resolved.


Invalid augroup

Description
Via 865375407e794b7efcab7d28efc51955560d0aaa startup notes:
packer.nvim: Error running config for gitsigns.nvim: ...p
↪.pack/packer/opt/plenary.nvim/lua/plenary/async/async.lu
↪ua:14: The coroutine failed with this message: .../packe
↪er/opt/gitsigns.nvim/lua/gitsigns/nvim/autocmds.lua:8: i
invalid augroup: gitsigns

does not happen with 06aefb1867687ee2b1d206fd5d19a2b254c62f2c, as makes sense.
Neovim version
NVIM v0.7.0-dev+1175-g5d6006f9b
Operating system and version
Linux
Expected behavior
No error on startup
Actual behavior
Error on startup
Minimal config
vim.o.packpath = '/tmp/nvim/site'

local plugins = {
  gitsigns = 'https://github.com/lewis6991/gitsigns.nvim',
  plenary  = 'https://github.com/nvim-lua/plenary.nvim',
  -- ADD OTHER PLUGINS _NECESSARY_ TO REPRODUCE THE ISSUE
}

for name, url in pairs(plugins) do
  local install_path = '/tmp/nvim/site/pack/test/start/'..name
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
end

require('gitsigns').setup{
  debug_mode = true, -- You must add this to enable debug messages
  -- ADD GITSIGNS CONFIG THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
}

-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE

Steps to reproduce

nvim -nu minimal.lua
...

Gitsigns debug messages
No response

Beat me to it.

Very sorry about that, CI should have caught this but didn't because it doesn't run this particular autocmd as setup is run after VimEnter.
Should be fixed in 6d66300

After updating, the error from gitsigns is fixed but I get the following error from impatient now

Error detected while processing VimEnter Autocommands for "*":
E5108: Error executing lua ...ck/packer/start/impatient.nvim/lua/impatient/profile.lua:212: attempt to index a nil value
stack traceback:
        ...ck/packer/start/impatient.nvim/lua/impatient/profile.lua:212: in function <...ck/packer/start/impatient.nvim/lua/impatient/profile.lua:210>
        [C]: in function 'require_'
        ...te/pack/packer/start/gitsigns.nvim/lua/gitsigns/nvim.lua:22: in function '__index'
        ...ck/packer/start/gitsigns.nvim/lua/gitsigns/highlight.lua:63: in function 'setup_highlights'
        ...pack/packer/start/gitsigns.nvim/lua/gitsigns/manager.lua:368: in function 'fn'
        ...im/site/pack/packer/start/gitsigns.nvim/lua/gitsigns.lua:466: in function 'fn'
        ...tart/gitsigns.nvim/lua/gitsigns/nvim/autocmds_compat.lua:13: in function <...tart/gitsigns.nvim/lua/gitsigns/nvim/autocmds_compat.lua:13>
        ...tart/gitsigns.nvim/lua/gitsigns/nvim/autocmds_compat.lua:8: in function '_exec'
        [string ":lua"]:1: in main chunk

No, without profiling enabled, I don't get the error.

Good to know, but means it is an Impatient issue.

Shall I file an issue there?

Actually, I think I've realized the issue and is caused by Gitsigns storing a copy of require. The profiling in impatient is a  bit sensitive to that kind of thing.
It does indicate that you may be setting up impatient incorrectly. It needs to be the first thing you require in your Neovim setup, and I think that error is only possible if you load gitsigns first.


[release-4.10] fix-resolv-conf-search.service: run after NM

Ensure that resolv.conf search domain patching runs after NM has built a new resolv.conf. This should prevent coredns from picking up stub resolver.
Cherry-pick of #323 on release-4.10 branch
Fixes https://github.com/openshift/okd/issues/978

/test e2e-vsphere
/test e2e-ovirt

/test e2e-vsphere
Bootstrap failed

/test e2e-ovirt
Failed to launch masters on bootstrap

vsphere install passed, but one worker could not rollout. No luck with oVirt installs - still no masters could be created.
/skip

/override ci/prow/e2e-aws-upgrade
Disruption


add dive for scanning container size

would that work to scan for suboptimally build images?

This looks really neat

Ahh, thank you for the fix - that's where I wasn't sure- I merge and test next week

dive scan works :)


Gestures swallow UITableView's delete functionality

By swiping between child view controllers, UITableView's can't respond to swipe gestures.
How do I prevent a ButtonBarPagerTabStripViewController from scrolling?

contentView.scrollEnabled = false


Remove InstantiatorBackedObjectFactory

And introduce more limited ExecObjectFactory.
So we can use file properties in ExecSpec, for https://github.com/gradle/gradle/pull/31154

@bot-gradle test this

I've triggered the following builds:

Pull Request Feedback (Trigger) (Check)

Build Scan

@bot-gradle cancel

This PR is not in the merge queue.

@bot-gradle test this

I've triggered the following builds:

Pull Request Feedback (Trigger) (Check)

Build Scan

The following builds have been cancelled:

Pull Request Feedback (Trigger) (Check)

Build Scan

@bot-gradle test this

I've triggered the following builds:

Pull Request Feedback (Trigger) (Check)

Build Scan

The following builds have been cancelled:

Pull Request Feedback (Trigger) (Check)

Build Scan

@bot-gradle test this

I've triggered the following builds:

Pull Request Feedback (Trigger) (Check)

Build Scan

@bot-gradle test this

I've triggered the following builds:

Pull Request Feedback (Trigger) (Check)

Build Scan

The following builds have failed:

Pull Request Feedback (Trigger) (Check)

Build Scan

The following builds have failed:

Pull Request Feedback (Trigger) (Check)

Build Scan

@bot-gradle test this

I've triggered the following builds:

Pull Request Feedback (Trigger) (Check)

Build Scan

The following builds have passed:

Pull Request Feedback (Trigger) (Check)

Build Scan

@bot-gradle test rfn

I've triggered the following builds:

Ready for Nightly (Trigger) (Check)

Build Scan

The following builds have passed:

Ready for Nightly (Trigger) (Check)

Build Scan


dnsmasq - problem with service status on Apple Silicon M1

brew gist-logs <formula> link OR brew config AND brew doctor output
$ brew config
HOMEBREW_VERSION: 3.0.9
ORIGIN: https://github.com/Homebrew/brew
HEAD: ed87211daa83982a6136e14d181a1550b46a0f17
Last commit: 5 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 02df6b76b81fa4e5ca13d3c7f4336d9a93c776e1
Core tap last commit: 2 hours ago
Core tap branch: master
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: octa-core 64-bit arm_firestorm_icestorm
Clang: 12.0 build 1200
Git: 2.24.3 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 11.2.3-arm64
CLT: <IP_ADDRESS>.1.1610135815
Xcode: N/A
Rosetta 2: false

% brew doctor
Your system is ready to brew.

[X] The brew doctor above contains no "Warning" lines.

What were you trying to do (and why)?
I try correct start dnsmasq service.
What happened (include all command output)?
It's start. It's working.
To the status of running the service was correct.
Step-by-step reproduction instructions (by running brew commands)
brew install dnsmasq
echo 'address=/.local/<IP_ADDRESS>' > /opt/homebrew/etc/dnsmasq.conf
sudo brew services start dnsmasq
brew services list

It doesn't seem to be an install issue so I transfered it to the services repo

@sb84 What's the output of launchctl list | grep dnsmasq and ps aux | grep dnsmasq and brew services list | grep dnsmasq?

sbaczyk@M1 ~ % sudo brew services start dnsmasq Warning: Taking root:admin ownership of some dnsmasq paths:   /opt/homebrew/Cellar/dnsmasq/2.84/sbin   /opt/homebrew/Cellar/dnsmasq/2.84/sbin/dnsmasq   /opt/homebrew/opt/dnsmasq   /opt/homebrew/opt/dnsmasq/sbin   /opt/homebrew/var/homebrew/linked/dnsmasq This will require manual removal of these paths using sudo rmon brew upgrade/reinstall/uninstall. ==> Successfully starteddnsmasq (label: homebrew.mxcl.dnsmasq) sbaczyk@M1 ~ % launchctl list | grep dnsmasq sbaczyk@M1 ~ % ps aux | grep dnsmasq nobody           22799   0,0  0,0 408114032   1776 s003  T     9:30     0:00.03 /opt/homebrew/opt/dnsmasq/sbin/dnsmasq --keep-in-foreground -C /opt/homebrew/etc/dnsmasq.conf -7 /opt/homebrew/etc/dnsmasq.d,*.conf root             22798   0,0  0,1 408394832  10512 s003  T     9:30     0:00.05 sudo /opt/homebrew/opt/dnsmasq/sbin/dnsmasq --keep-in-foreground -C /opt/homebrew/etc/dnsmasq.conf -7 /opt/homebrew/etc/dnsmasq.d,*.conf sbaczyk          23480   0,0  0,0 408103296   1264 s003  S+   12:38     0:00.00 grep dnsmasq sbaczyk@M1 ~ % brew services list | grep dnsmasq dnsmasq unknown root /Library/LaunchDaemons/homebrew.mxcl.dnsmasq.plist sbaczyk@M1 ~ %

sbaczyk@M1 ~ % sudo brew services start dnsmasq
Warning: Taking root:admin ownership of some dnsmasq paths:
  /opt/homebrew/Cellar/dnsmasq/2.84/sbin
  /opt/homebrew/Cellar/dnsmasq/2.84/sbin/dnsmasq
  /opt/homebrew/opt/dnsmasq
  /opt/homebrew/opt/dnsmasq/sbin
  /opt/homebrew/var/homebrew/linked/dnsmasq
This will require manual removal of these paths using `sudo rm` on
brew upgrade/reinstall/uninstall.
==> Successfully started `dnsmasq` (label: homebrew.mxcl.dnsmasq)
sbaczyk@M1 ~ % launchctl list | grep dnsmasq
sbaczyk@M1 ~ % ps aux | grep dnsmasq
nobody           22799   0,0  0,0 408114032   1776 s003  T     9:30     0:00.03 /opt/homebrew/opt/dnsmasq/sbin/dnsmasq --keep-in-foreground -C /opt/homebrew/etc/dnsmasq.conf -7 /opt/homebrew/etc/dnsmasq.d,*.conf
root             22798   0,0  0,1 408394832  10512 s003  T     9:30     0:00.05 sudo /opt/homebrew/opt/dnsmasq/sbin/dnsmasq --keep-in-foreground -C /opt/homebrew/etc/dnsmasq.conf -7 /opt/homebrew/etc/dnsmasq.d,*.conf
sbaczyk          23480   0,0  0,0 408103296   1264 s003  S+   12:38     0:00.00 grep dnsmasq
sbaczyk@M1 ~ % brew services list | grep dnsmasq
dnsmasq unknown root /Library/LaunchDaemons/homebrew.mxcl.dnsmasq.plist
sbaczyk@M1 ~ %

Looks like it's:

running twice
launchctl can't find the pid

This may be an issue with your local machine or may be an issue with the dnsmasq plist. It's not a Homebrew/services issue.

This may be an issue with your local machine or may be an issue with the dnsmasq plist. It's not a Homebrew/services issue.

So where should I direct my inquiry?
Can you refer the ticket to the appropriate section?

@sb84 You'll need to figure this out yourself for now. We'll review a pull request if you can come up with a fix.

@sb84 You'll need to figure this out yourself for now. We'll review a pull request if you can come up with a fix.

Are you able to give me any advice what should I check?
Or what keywords should I dig on Google for?

Sorry, no.

Others may be able to!

I don't know what the reason is
but in the end, for my own needs, I solved it like this
that I run the dnsmasq service as a normal user, but on port other than 53 (for me it is 8053), and additionally I set up a local redirection of calls from port 53 to 8053
echo "rdr pass inet proto udp from any to <IP_ADDRESS> port 53 -> <IP_ADDRESS> port 8053" | sudo pfctl -ef -
the service is green and all calls from X.local are directed to <IP_ADDRESS>
I don't know who is responsible for the dnsmasq package exactly,
I am also not privy enough to prepare some solutions, if you think it is right, then direct it to the right people


fix deprecated process.EventEmitter

process.EventEmitter has been removed in node 7 and replaced by the events module.
This PR applies this change.
This seems to fix it for me.

Oops, forgot to update the test helper.

Ok, seems a lot better now.

Hey, I merged in https://github.com/flowdock/node-flowdock/pull/24 which also replaces process with events, so I'm going to close this one. Thanks for your time though!


How long is it allowed to block a grpc thread

I have implemented a server-streaming server based on grpc. The grpc::ServerWriteReactor class is used as stream writers. When a remote procedure is called by a client, a reactor is created. The data for is retrieved from a thread-safe queue: in the OnWriteDone method, the next Response is retrieved and passed to the StartWrite method.
The queue is blocking. When there is no data in it, the reading thread (in my case it is the grpc library thread) blocks until data arrives in the queue.
Are there any restrictions on how long a grpc thread can be blocked? Is there some kind of liveness probe inside grpc that, seeing that the thread is blocked, will take some action?

Please do not use this repository for asking questions. This repository is for reporting issues with gRPC implementation. Use StackOverflow or grpc-io mailing list for for asking questions.

I asked the question because the form on the Issue tab allows it. In that case, remove this item to avoid misleading anyone.

Also, I asked this question on SO. However, the answer provided there contradicts the information here.


Menu item alignment issues

Several menus have issues such as this - This is the invite link page on channel settings

You must have an older version of Slate. Please update.

I just downloaded it a couple days ago, there's no new version
On Tue, Dec 15, 2020, 07:11 Ian<EMAIL_ADDRESS>wrote:

You must have an older version of Slate. Please update.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DiscordStyles/Slate/issues/25#issuecomment-745076663,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATEGYAPI5TX23HSTP7NMUDSU34XNANCNFSM4UVKIDNQ
.

Oh I see why. That's in the channel settings and not server settings.

Fixed.

Fixed.


Add more dungeons, rooms or floors - Part 3

It'd be awesome to have a lot of the dungeons, rooms, or floors, so the game could be more fun 😜
🐞 Problem
Currently, we have only a bunch of dungeons, rooms, or floors in the project
🎯 Goal
Have a lot of dungeons, rooms, or floors from the diverse games.
💡 Possible solutions
Add new a new dungeon, rooms, or floors.
How to make it?
Check out Contribution Guidelines
📋 Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request and add this in comments - Addresses #
Ask for a review in the comments section of the pull request
Celebrate your contribution to this project 🎉

This issue will close every 10 contributions for adding new room(s) or floor(s)

Hello @ming-tsai . I have forked the pen and is working on creating a new floor and rooms for the existing English dungeon.

Work in Progress: Add a new dungeon "covid-19"
May take a little long

I have an idea for a castle the player might be able to explore. Gives alot of room to work in and room for other people to build off of.
Might also take a while.

I have an idea for a castle the player might be able to explore. Gives alot of room to work in and room for other people to build off of.
Might also take a while.

You are planning to implement this as a new dungeon or to an existing dungeon?
Nice idea, by the way.

I have an idea for a castle the player might be able to explore. Gives alot of room to work in and room for other people to build off of.
Might also take a while.

You are planning to implement this as a new dungeon or to an existing dungeon?
Nice idea, by the way.

Thanks; I'd like for it to be a new dungeon, but I have to find a place it would work in.

@FukurouMakoto, you could Marge the branch using git command

Hi @ming-tsai, please check #110. I can't complete it. I don't know to write a good story, so I have unassigned myself to this issue.
Sorry.

Can some explain the dungeon structure?

It is available in the README file.


automated benchmark over big list of prompts

our latest decoder run are currently a bit hard to evaluate, the during training metrics and generation all seem pretty good
the generation also seem pretty good overall when using with the prior and an upsampler

however is it as good as the original dalle2 ? not quite, missing a bit in generality
a nice way to solve this is to evaluate on a list of difficult prompts automatically and then display that nicely in wandb
it has been done by dalle mini, imagen, dalle2 and parti with pretty good success
see https://gist.github.com/rom1504/b5db3c98c5485c0ec5a1d22d79ca083a and https://gist.github.com/rom1504/a16b2259510632637e0978aad8933d8b and https://wandb.ai/dalle-mini/dalle-mini/reports/DALL-E-Mega--VmlldzoxODMxMDI2
let's build such an evaluated benchmarking, to know whether our models are getting better
@nousr has started work on this

good idea! yea we should definitely compile a set of prompts sorted by difficulty
then it would be trivial to preencode them for eval across a range of models and roll our human eyes over it

proposed evaluation procedure after discussion.
we want to know

does the prior work

does the decoder work
on

real image/caption

ood generated image/prompt (eg https://twitter.com/jd_pressman/status/1543778382894141441)

take good image + prompt

compute clip emb from image, compute clip emb from text

give those to decoder -> get image_without_prior

give prior(clip_text) + clip_text to decoder -> get image_with_prior

display real image, image_without_prior, image_with_prior

Then as metrics:

compare images from 5
compare embeddings from 2 and 4

This should tell us whether the prior and the decoder are working, and whether we can handle ood


Include topic children in links

So that we can render the topic pages entirely from the content-store.

Tests will fail until https://github.com/alphagov/govuk-content-schemas/pull/88 is merged.


API docs for SpectralCube don't show BaseSpectralCube functionality

I'm looking here to try and find out all the wonderful methods that SpectralCube has:
http://spectral-cube.readthedocs.io/en/latest/api/spectral_cube.SpectralCube.html
But currently there's only 3 methods listed: convolve_to, spectral_interpolate, spectral_smooth.
Is is possible to either add BaseSpectralCube to the API docs or have the BaseSpectralCube methods shown for the SpectralCube class?

Huh... yes, we need to do that.  I didn't realize that changing the inheritance structure had broken the docs.

See fix in #342


pytoml.core.TomlError when executing ays blueprint

load dirs
Traceback (most recent call last):
File "/usr/local/bin/ays", line 546, in
cli()
File "/usr/lib/python3/dist-packages/click/core.py", line 716, in call
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 696, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1060, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 889, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 534, in invoke
return callback(*args, **kwargs)
File "/usr/lib/python3.5/contextlib.py", line 77, in exit
self.gen.throw(type, value, traceback)
File "/usr/lib/python3/dist-packages/click/core.py", line 86, in augment_usage_errors
yield
File "/usr/lib/python3/dist-packages/click/core.py", line 534, in invoke
return callback(*args, **kwargs)
File "/usr/local/bin/ays", line 171, in blueprint
repo = j.atyourservice.get()
File "/opt/jumpscale8//lib/JumpScale/baselib/atyourservice81/AtYourServiceFactory.py", line 343, in get
return self.repoGet(path=path)
File "/opt/jumpscale8//lib/JumpScale/baselib/atyourservice81/AtYourServiceFactory.py", line 351, in repoGet
self._doinit()
File "/opt/jumpscale8//lib/JumpScale/baselib/atyourservice81/AtYourServiceFactory.py", line 99, in _doinit
global_templates_repos = j.atyourservice.config['metadata']
File "/opt/jumpscale8//lib/JumpScale/baselib/atyourservice81/AtYourServiceFactory.py", line 59, in config
cfg = j.data.serializer.toml.load(config_path)
File "/opt/jumpscale8/lib/JumpScale/data/serializers/SerializerBase.py", line 12, in load
return self.loads(b)
File "/opt/jumpscale8//lib/JumpScale/data/serializers/SerializerTOML.py", line 18, in loads
return pytoml.loads(s)
File "/usr/local/lib/python3.5/dist-packages/pytoml/parser.py", line 23, in loads
ast = _p_toml(src)
File "/usr/local/lib/python3.5/dist-packages/pytoml/parser.py", line 344, in _p_toml
s.expect_eof()
File "/usr/local/lib/python3.5/dist-packages/pytoml/parser.py", line 124, in expect_eof
return self._expect(self.consume_eof())
File "/usr/local/lib/python3.5/dist-packages/pytoml/parser.py", line 164, in _expect
raise TomlError('msg', self._pos[0], self._pos[1], self._filename)
pytoml.core.TomlError: (13, 9): msg

Fixed.


Stricter npm field validation

Changes:

Makes npm field required and uses stricter regex (package-name-regex)
Fixed properties for 5 entries in components.json
Moved 1 entry from components.json to templates.json
Removed 1 entry from components.json that does not have a published npm package

Hi @MacFJA , just checking if you wanted any further changes? Thanks!


TorchatReady.txt not being found

Users can't tell when it's running.
Change directories

Now they can.


Local settings wanted

why #37519 was locked

We need some changes here or clarification
https://github.com/microsoft/vscode/issues/83132

It was locked because it was closed with a workaround (which is available at the end of the issue).


Update MATCH emit output tests

I decided to separate this from Cypher and Gremlin emit output tests because this isn't a direct find-and-replace job-- some tests seem to be giving output that doesn't make sense, so I'm correcting them here too.

Implement the change requested here for MATCH

Make these emit output tests use the test schema

Correct any incorrect tests from before

Seems fine so far. Happy to merge as-is if you think it's ready.

One more test for here (that is already in Gremlin but not here). Also will take a look at the failing CI, but I'll mark it when it's ready so you don't have to keep checking :)


Request for a job

Hi, I'm Ayodeji Fakayode a graphic designer and Brand identifier, I would be glad to handle the project graphic design aspect.. Kindly Message me on discord : Ayomifay#7269

Thanks! Think we're all set for now, but we'll keep you in mind if we have any specific graphic design needs.


fix: golangci-lint error

Which issue(s) this PR fixes:
https://github.com/longhorn/longhorn/issues/7448
What this PR does / why we need it:
Special notes for your reviewer:
Additional documentation or context

@FrankYang0529 Need to resolve the conflict. Thank you.


Lock Mouse To Screen/Window in Stronghold Crusader

Hello,
first of all great Project you do here, it improved Stronghold Crusader Graphic Interface quit well :)
But i have a Problem after enabling Dd7to9 to 1, the Mouse Cursor was Locked on the Game Screen before but after upgrading to the Dd9 it is no more locked what have the issue there is no more Map Scrolling and the mouse go to my Second Monitor.
Here my Settings i use(i know Crusader use DDraw.dll because i saw the import in ida):
dxwrapper.zip
Do you have any idea how i can lock the Mouse to the Stronghold Window, so it wont go to a other Screen, so if anyone have 2/3 Screen Setup no Problems.
Thanks and i hope you have a great day :)

Hello @PodeCaradox,  I have not added features into the project yet to lock the mouse cursor or features to handle multiple monitors.  However, you could try disabling the Fullscreen option.  This might help solve some of the mouse issues.  That option won't work if you have more than one monitor unless you duplicate them instead of extending them.

I doubt I will get to this anytime soon, if ever.  So I am going to just close it for now.  Closing as not planned.


Adapt NetworkPolicys for components in Istio-related namespaces

How to categorize this PR?

/area dev-productivity ops-productivity networking security
/kind enhancement
What this PR does / why we need it:
This PR adapts and replaces all possible network policies that are used for Istio-{System, Ingress} with the help of the NetworkPolicy controller.
Co-authored-by: Rafael Franzke<EMAIL_ADDRESS>Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/7352
Special notes for your reviewer:
f10d67bf8ddd0277a03524ceb2674af2ec0d788c adds required labels for exposureclass handler namespaces along the way(cc @ScheererJ @axel7born). This was probably missed before.
Release note:

Network policies for `Istio-System` and `Istio-Ingress` have been adapted and now make use of GRM's [NetworkPolicy Controller](https://github.com/gardener/gardener/blob/master/docs/concepts/resource-manager.md#networkpolicy-controller).

/assign

Most of the requested changes were pushed in separate commits. The PR still missed the deny-all handling (https://github.com/gardener/gardener/pull/7570#pullrequestreview-1315000986) which will follow in a bit.

/hold
Together with @rfranzke we discussed that https://github.com/gardener/gardener/commit/e747c53164eba9966fd71c4ce692c5f3665165b9 can be reverted and GRM can be activated for zonal exposure class by using the label value handler.exposureclass.gardener.cloud/name (cc @ScheererJ)

Thanks for your feedback @rfranzke and @ScheererJ. I addressed all comments, please see commits cb429b5bf8714563cba39659bb012b3ff946adc6 and following.

/unhold

/test pull-gardener-e2e-kind

/test pull-gardener-e2e-kind-ha-multi-zone

New changes are detected. LGTM label has been removed.

Force pushed after rebase due to merge conflicts with https://github.com/gardener/gardener/commit/c35f375c4f6f17eaac32afd00edb9f0705ab4b8f.

Thanks again for your input and support @ScheererJ and @rfranzke 👍


Dapr doesn't gracefully recover from cluster upgrade/shutdown

Reported by @avo-sepp:
After updating from 1.26.x to 1.27.7, ALL replica sets (and deployments) were failing with error similar to:

Error creating: admission webhook "sidecar-injector.dapr.io" denied the request: error from sentry SignCertificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:443: connect: connection refused"

To get deployments to come online I had to remove the sidecar-injector.Dapr.io mutation webhook from the cluster entirely. Then allow all deployments to come back online, before re-adding the mutation webhook.

Closed via https://github.com/dapr/dapr/pull/7507


Akamai 2.0 is now online

Please update the toolbox

I no longer work on antibot solutions, this project won't be updated for Akamai v2

the v2 seems to be much harder to deobfuscate


[BEAM-8747] Guava dependency cleanup

Fixes BEAM-8747.
As per email thread "Completeness of Beam Java Dependency Check Report" (archive link),  @kennknowles found there are "declared but unused" and "used but undeclared" Guava dependencies in some of modules. This PR addresses the findings.
I used gradle-lint-plugin to confirm Ken's findings. See detail in the ticket https://issues.apache.org/jira/projects/BEAM/issues/BEAM-8747 .

GCP connector turned out using guava in fully-qualified class name (link; no action taken.
sdks/java/extensions/sql/jdbc had "declared but unused" Guava dependency.
runners/google-cloud-dataflow-java/worker depends on 2 classes without declaring. These classes should not depend on Guava class. So I updated them to use vendored Guava.
sdks/java/io/kinesis has "used but undeclared" Guava dependency.
sdks/java/extensions/sql/zetasql has "used but undeclared" Guava dependency.
sdks/java/io/elasticsearch-tests/elasticsearch-tests-2 has "declared but unused" Guava dependency.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @kennknowles

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit


Fix Playwright setup on Gitpod

Fixes Issue
Closes #2257
Changes proposed
Install playwright dependencies on init.
Set Playwright to not run parallel tests on Gitpod

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

The scripts need to be executed in a custom-dockerfile.
The init task only persists the data inside the workspace directory.
Depending if the tests should be able to run headed, the base image of the dockerfile needs to be gitpod/workspace-full-vnc

The scripts need to be executed in a custom-dockerfile. The init task only persists the data inside the workspace directory. Depending if the tests should be able to run headed, the base image of the dockerfile needs to be gitpod/workspace-full-vnc

Would the playwright install be the only command needed in the dockerfile or would the npm ci be needed in there too?
Does it make sense to support headed tests or Gitpod, or would it make more sense to to have people run that elsewhere if needed?

How do we do it for the finder project? Could we do it similar
https://github.com/EddieHubCommunity/good-first-issue-finder/blob/main/.gitpod.yml

Thank you both for continuing to work through this 💪

It works 🎉
gitpod /workspace/LinkFree (gitpod) $ npm run test

><EMAIL_ADDRESS>test
> npx playwright test

Running 19 tests using 1 worker
[WebServer] (node:1331) [DEP0128] DeprecationWarning: Invalid 'main' field in '/workspace/LinkFree/node_modules/react-icons/package.json' of 'lib'. Please either fix that or report it to the module author
(Use `node --trace-deprecation ...` to show where the warning was created)
[WebServer] Warning: data for page "/search" (path "/search?username=_test-profile-does-not-exist") is 492 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
See more info here: https://nextjs.org/docs/messages/large-page-data
[WebServer] Warning: data for page "/search" is 492 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
See more info here: https://nextjs.org/docs/messages/large-page-data
[19/19] [chromium] › search.spec.js:44:6 › find the profile after providing concise name

  10 skipped
  9 passed (43s)

To open last HTML report run:

  npx playwright show-report


Suggestion: Separate Reference Consolidation Service

It would be good to separate the reference consolidation from the extraction itself (I believe there is no such service yet?).
Some of the advantages I could see with that:
Consolidation Results Used As Suggestions
The consolidation is not perfect (nothing is of course, #616). By using it as a separate service it would make it easier to see it as suggestion. For example a user could accept those manually. Or they could be accepted automatically depending on how confident we are in the results.
An alternative to that could be to include original and consolidated XML in the response.
Consolidation as a Background Process
The extracted results could initially be used directly which will be quicker. Consolidation could happen in the background and later enhance the results.
Backdated Consolidation
The consolidation could be used on XML that had already been extracted before (or may not even come from GROBID).
Better API Progress Feedback
Even if say a website wants to extract and consolidate in one go, it could give better user-feedback by splitting the process. e.g. a user could see that it has been extract and is now currently being consolidated. If consolidation fails, it could be retried etc.

Thanks Daniel !
I think this is already the case, one can select crossref or biblio-glutton for consolidation in the config. file. Consolidation is a background process as it relies on external services and run with a distinct pool of threads (in the case of crossref, the number of parallel queries follows the dynamic max query per second returned by the service).
It's also possible to simply use biblio-glutton separately for consolidation, and even call grobid from biblio-glutton if we start from a raw reference string. Some Grobid users like scite.ai are using it like that, to optimize the balance between all the services, because consolidation takes actually more runtime than Grobid itself, so it's good to have more biblio-glutton nodes for instance than grobid nodes if one wants to scale (crossref becomes quicly impossible to use if we want to process several PDF in parallel, because the limit of queries per second - even in the best hours/days - is a blocker).
I also used it like that for ISTEX, running Grobid without consolidation, then call the consolidation based on the XML and updating the XML. In general it's really up to the user to build its pipeline according to its needs, as you suggest.

Okay, thank you.
I see, I think I was wrongly assuming that biblio-glutton was always meant to be used through GROBID.
I see the value of biblio-glutton, but it seems quite a bit of setup (but I may be wrong). Having the option to start with using Crossref would be good.
I haven't studied biblio-glutton yet. Can it be used directly with Crossref or does it need to build the index? Does it need to use ElasticSearch?

Yes biblio-glutton requires an heavy set-up, that's the price to pay ;)
The idea is not to use and not to depend on CrossRef REST service, no compromise on this !
You can test/play with biblio-gluton at the public demo end point:
http://cloud.science-miner.com/glutton/service/data
for example:
http://cloud.science-miner.com/glutton/service/lookup?biblio=koff 27 1994 cell&firstAuthor=koff&jtitle=cell&firstPage=27&postValidate=true

Okay, thank you again.
Nothing is free these days ;-)
I probably should not use the demo service to do the evaluation on my documents.
I better close this issue.

I added a faq label, so I re-open until we put this in the faq :)

Not super-relevant, there is another label called "documentation", if it's the same, we could merge with "Faq"? (the black colour is threatening btw 😂)

ah yes sorry! black was the last "color" not already taken. I remove it.

I close this issue, this is already documented in details here


Picovoice Console Issue: New wake word "livi" or "lifi" is not recognized

Make sure you have read the documentation, and have put forth a reasonable effort to find an existing answer.
Expected behaviour
The Train Wake Word on console processes the wake word
Actual behaviour
Missing pronunciations for words: [“lifi”]. If these words are present in a respected English dictionary, please provide a link to the word and its pronunciation via a GitHub issue . Custom pronunciations and branded words can be created for commercial customers; contact Picovoice for more information.
Steps to reproduce the behaviour
Put "hi livi" or "hi lifi" (expected to be pronounced as hi lee fee) on the wake word training console

This is not a bug. It's a question at this time. Please use the correct label moving forward. These don't see English words and hence we won't be adding them. If I'm wrong provide the link to a dictionary item and I will re-open. If these are company/product names and you are working on a commercial application you can contact the sales team to help out.


Publish a "vulnerability reporting" process

We should have done this a long time ago. Some relevant items to figure out:

[ ] draft process and get feedback from nokogiri-core
[ ] publish process in both English and Japanese READMEs
[ ] publish process on nokogiri.org
[ ] set up a PGP key so reporters can protect their email content

Process document should include:

[ ] what email list report should go to
[ ] clearly identify who the core contributors are that will receive the information
[ ] clearly identify a point person and backup person for security

Also see how Pivotal is doing this: http://www.pivotal.io/security

I agree we should have had this earlier. Also, I think it's nice to have how should we, nokogiri team, treat such vulnerability reports. I heard Rails team must notify some sort of security group (authority?) if vulnerability is found. Rails may be a special product and needs to have a strict rule which may not be applied to Nokogiri. If Nokogiri team just fixes the bug and writes back to the reporter, that's all nokogiri team does?

Hey all, I set up a project profile at https://hackerone.com/ for Nokogiri, and have requested they review the project and put it into production mode.
Using a tool like this would greatly simplify reporting and our reporting policy and process. Rails uses it, though they offer a bounty which we likely will not (without external funding).
Anybody have thoughts here? Otherwise, I'm going to move forward with this plan over the next few days.

I agree with using hackerone.  It's been nice for the Rails team, and I think it would work well for us.

Bump @flavorjones.  What's the next step for hackerone?

Hey @flavorjones, anything I can do to help get this moving? :)

I've submitted Nokogiri to Hackerone as a project for review.

@flavorjones approved! Just shot you an e-mail with some details. Let me know if you have any questions.

@reedloden Thank you!

@tenderlove @jvshahid @knu @larskanis I've invited you all to the Hackerone project as team members. Currently it's in "controlled launch" until we handle a few vulnerability reports.
I've also invited everyone I could find in my email and the project's github issues that reported a vulnerability, as "hackers" who can submit vulnerability reports.
Next up:

create a SECURITY.md file that explain how to report security issues (omitting Hackerone until it's a public project)
add a security page to nokogiri.org

Once the project is public:

update SECURITY.md
update page on nokogiri.org
tweet, etc.

Anything I've missed?

Oh, and if anyone else wants to be invited to be a "hacker" on the project to submit vulnerability reports, let me know, happy to send an invite.

@flavorjones I'm happy to move you directly to public if you wish, but the invite-only stage is great for testing out a few (valid) reports. However, I understand that may be hard to do based on the nature of Nokogiri (and it being an open source library), so if you want to go public sooner, just let me know.

Hi @reedloden, I just emailed you about this. I think it would be really useful to go public sooner, if that's possible.

@flavorjones Totally understand and agree! Replied to your e-mail, but tl;dr is that https://hackerone.com/nokogiri is now public. 💃 🎉

Here's my checklist of what remains to be done:

[ ] copy "policy" from hackerone and put it into a SECURITY.md file
[ ] link to SECURITY.md from README
[ ] add a security page to nokogiri.org
[ ] announce on a github issue
[ ] announce via twitter
[ ] announce via email

Security page available at http://www.nokogiri.org/tutorials/security.html

Done. Thanks, all!


Netty Http2 client in example not connecting to all h2 servers which browsers can connect to(SSL problem)

Expected behavior
Creating a client with InsecureTrustManagerFactory should allow connection to any h2(Http2 over TLS) web server like webtide.com or deckofcardsapi.com.
Actual behavior
Encountering an exception "Received fatal alert: handshake_failure".
Steps to reproduce
The Netty example project for http2 client can be re-used for reproducing the by just changing the host to deckofcardsapi.com and port to 443 and url to "/api/deck/new/shuffle/?deck_count=1"
Minimal yet complete reproducer code (or URL to code)
https://github.com/netty/netty/blob/4.1/example/src/main/java/io/netty/example/http2/helloworld/client/Http2Client.java
Netty version
Netty-All 4.1.41.Final
JVM version (e.g. java -version)
Java-8
OS version (e.g. uname -a)
MacOS

TLS Handshake is failing because to SNI is not specified in TLS Client Hello request. Just change this code: https://github.com/netty/netty/blob/41c47b41bf0caa2f0faffec901a374516fbd19f7/example/src/main/java/io/netty/example/http2/helloworld/client/Http2ClientInitializer.java#L101
pipeline.addLast(sslCtx.newHandler(ch.alloc())); -> pipeline.addLast(sslCtx.newHandler(ch.alloc(), Http2Client.HOST, Http2Client.PORT));

TLS Handshake is failing because to SNI Extension is not specified in TLS Client Hello request. Just change this code: https://github.com/netty/netty/blob/41c47b41bf0caa2f0faffec901a374516fbd19f7/example/src/main/java/io/netty/example/http2/helloworld/client/Http2ClientInitializer.java#L101
pipeline.addLast(sslCtx.newHandler(ch.alloc())); --> pipeline.addLast(sslCtx.newHandler(ch.alloc(), Http2Client.HOST, Http2Client.PORT));
This will add SNI Extension in TLS Client Hello request.

@hyperxpro can you do a PR ?

@hyperxpro can you do a PR ?

Sure


bug: completion plugins fore codium/copilot don't work

Did you check docs and existing issues?

[x] I have read all the LazyVim docs
[x] I have updated the plugin to the latest version before submitting this issue
[x] I have searched the existing issues of LazyVim
[x] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.2
Operating system/version
MacOS
Describe the bug
Seeing the following since upgrading to 14. If I switch to nvim-cmp, this goes away, but, having other issues with that, so trying to make it work with blink.

Steps To Reproduce
Upgrade to 14.
Expected Behavior
It should still work
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "LazyVim/LazyVim", import = "lazyvim.plugins" },
    -- add any other plugins here
  },
})

You still have a nvim-cmp spec in your config.
If you want to keep using nvim-cmp, you need to enable the extra.
If not, renove that spec from your config.

The error is gone, thank you, removed my nvim-cmp config, but the ai plugins simply don't work.

same, removed nvim-cmp, error is gone but ai plugins still don't work. Do we have to revert back to nvim-cmp to use ai plugins?

I also just pushed an update to make sure nvim-cmp specs won't cause no longer issues,
so other users won't have this.

All ai plugins work for me.

thanks @folke going to test it out and report back

I've updated to the latest, the copilot lang server is running, but the completions are definitely not being presented:

Could very well be due to this, which seems to have been reported:
unhandled error: ...al/share/nvim/lazy/nvim-lspconfig/lua/lspconfig/util.lua:256: bad argument #1 to 'lines' (/Users/jacquesg/dev/projects/asterias/deianira/package.json/package.json: Not a directory)```

Yes, like I mentioned too many times already in this or other issues: https://github.com/neovim/nvim-lspconfig/issues/3503

I've reverted to the known good commit, error is gone, but still no completions for the ai plugins :)

You are using the codeium extra right?
Did you do :Codeium Auth?

It was authed already, redid it, same result. I've got both codeium and copilot enabled, neither work

the completions might be lower in the menu and not shown at the top. Did you check that?

Yep, they're not in the popup menu at all.

Having same issue here. Had nvim-cmp error at first. Reinstalled LazyVim from scratch, didn't add any custom config yet. Just added copilot from LazyExtras, authenticated. No errors now, but AI autocompletion doesn't work at all.

Can you check again? Should be fixed now.

Yep, all working now for me! Thank you.

great

I know this is closed but it is working for me as well, thanks @folke and everyone