Channel Islands pieces - Chapman Code integrity

We have 4 Chapman Codes for the Channel Islands but they are all recorded in the PARMS under CHI. We have designated this in the Chapman Code structure as a country along with ENG, WLS etc.
I have had a look at the vld collection for the Channel Islands and the impact of the historical structures used by the TNA in their census collection, which is the basis of our PARMS structure.
In 1861 and 1891 (the only two years that FreeCEN has transcribed) they appear to have used a structure where the Channel Islands were the primary chapman code and not the chapman code of the individual islands. (The ability to search the whole channel islands has recently been introduced).
So we have a situation in the existing searches where if I search for John Smith in Jersey in 1861 I may not find him. However if I search for John Smith in the Channel Islands in 1861 I will be able to find him.
This TNA structure caused headaches when the PARMS was established. The ongoing implications were not realised.
I am proposing that the Chapman code for CHI in the PARMS should be changed to that of the individual islands. This will affect 29 online pieces in 1861 and 8 pieces in 1891.
I can coordinate these changes with Rhoda. The data manager still has the ability to download and reload vld files. Once the piece is downloaded Rhoda can do the changes and then the piece can be reloaded.
There are also 5 x 1861 csv files that will need changing. There are no unincorporated 1861 csv files. There are 6 x 1891 csv files that will need changing. There are no unincorporated 1891 files.
In addition I propose that although the Piece name of RG9_4374 is Guernsey, the contents are Alderney. I therefore propose that we change  give it a Chapman Code of ALD.
In the interests of Chapman Code integrity I propose that we break up RG12_4707 into 4707 GSY, 4707A ALD and 4707B SRK. This will be the only online piece that is affected by the changes. It is currently a vld file so will need re-validation as a csv file.
There are no files online for 1841, 1851, 1871, 1881, or 1901 .
From 1841 to 1901 the PARMS structure includes Alderney and Sark as Guernsey, which is the government structure.
In 1911 the PARMS structure uses the islands of  ALD, GSY, JSY and SRK. From 1841-1901 the structure is only CHI with the Islands as piece names. Therefore the structure does not conform to our country / county / regn district / piece / civil parish structure.
I also propose that we adjust the PARMS for the other census years in a similar manner to give us a similar structure to the rest of the PARMS entries.
Referred for consideration, please.
This story has been triggered when considering story #341.
Geoff

Agreed in Scrum

Gazetteer updated, Changes completed.
Geoff


What does do dnscrypt-proxy exactly?

Dear jedisct1 and Github users,
Hope you are fine. I have some questions about this tool.

First question is title.
Second question is this encrypts DNS traffic? If yes, my ISP can be monitored content even if encrypted? I mean is this encrypts my dns queries (web)?
Third question when i installed this, internet connection of other devices in my LAN made laggy and slow (freezes internet connection, for ex. videos are waiting for fetch. When i turn off software, everything is normal). And sometimes 30-40 seconds there is no internet on my LAN. What is the reason?
Fourth question you had wrote "you can configure plenty of options" in Installation section. Could you please explain some of them?
Fifth question when i run from folder via command line it is faster than installed service. There are too much difference between two of them. Installed service is too much slow. I tested this scenario on five (5) different computers. Please make fix for this.
Sixth question i saw there are many public DnsCrypt resolvers but i couldn't understand how can i use sdns://78438....... address as like in this picture.
http://prntscr.com/ld9udu
Seventh question how can i configure this tool "only use encrypted Dnscrypt protocols"?

Have a happy day.
Thanks in advance.
Best Regards.

Hi,
The answer to most of your questions are in the documentation: https://github.com/jedisct1/dnscrypt-proxy/wiki
It doesn't encrypt your web traffic. Which is mostly already encrypted these days. But it encrypts and authenticates DNS, which is used before you load any web page, and is the easiest, cheapest, most common way to do monitoring and censorship.
It doesn't do anything to web content, even less to videos. But some services use DNS information to route you to a server close to your ISP. If you use your ISP DNS, they will serve the content from a location close to your ISP, or from caches hosted by the ISP itself.
If you use a DNS resolver which is far away, they may send the files from a far away location.
But this is less and less the case with modern CDNs.
Options are described in the documentation, as well as how to choose the resolvers. You don't need to copy the sdns://.... addresses.
If you use this tool, you will always use encrypted DNS services. It will never connect to an unencrypted one (it can't, this is not even implemented).

Thank you for your interest and polite answers. So, is this supports DNS Over TLS, right?

It supports the more recent DNS-over-HTTPS, as well as DNSCrypt.

I got it. Do you think add Dns-over-TLS feature?

Probably not.
DNS-over-TLS doesn't have any security advantage over other protocols. It's badly designed, can hardly evolve, it's slow and can reduce privacy. Its funky port number also makes it impossible to use on many public WiFi where it could actually be useful.
"It's a standard" is the only argument it had. Now what DNS-over-HTTPS is an official IETF protocol and that DNSCrypt is about to be submitted, there is no point in supporting it.

I got it. Thank you for your interest.

Last one thing. How often Dns resolvers is been updating?

Every 3 days by default.


Remove const for intercept-stdout, Fix --help with no prefix in LUIS

Proposed Changes

Remove unused const for intercept-stdout in LUIS and Ludown files.
Move validation for --prefix argument before the validation for --help, otherwise it will not intercept output for the --help text.

Testing
Calling luis --help --prefix will append the prefix to the output of the command.
The removal of the unused const will not modify the behavior of the code.

Pull Request Test Coverage Report for Build 600

17 of 17 (100.0%)  changed or added relevant lines in 15 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 64.433%

Totals

Change from base Build 596:
0.0%

Covered Lines:
3810

Relevant Lines:
5628

💛  - Coveralls


Edge Support

It does support Edge?

CJS export targets latest Node. See the babelrc .
Also see #191.
If people want to request different targets for the CJS export, I will consider that.

I'm using the next-i18next, it do work's fine in chrome and firefox, but now on edge things are just not work. For example i have a title that uses the translation function, and now it just don't appears (if i inspect the dom tree the text is there). I go back to a point where the next-i18next wasn't being using yet and it do work's. You can check in here https://cwi.com.br/.

Do you understand my point about transpilation targets?

Not really. I have been looking in the code and find out that em the link component of next-i18next, there is a const with name 'as' and this is a reserved word and edge don't seen to work like chrome that accept it.
      as,
      children,
      href: hrefProp,
      lng,
      nextI18NextConfig,
      ...props
    } = this.props;```

I already try to use babel costume config from next.js to use @babel/plugin-transform-reserved-words but i don't think this work in file's in node modules.
Don't really know what to do to get this to work.

Hi @RizziWilliam. As far as I know, as is not a reserved word in JavaScript.
The file I linked is our babelrc, which tells Babel what targets we would like to transpile to. Our target for CJS is the latest Node, as I've said.

Depending on if this is a transpilation/JS-feature issue or some other sort of "reserved keyword" issue, we can decide how to proceed. Let me know.

Ok, i do found a away to get this to work, when using next we create a next.congif.js, in this file we have :
 webpack(config, options) {
config.module.rules.push({
      test: /\.(txt|jpg|png|svg|ico)$/,
      use: [
        {
          loader: 'url-loader',
          options: {
            limit: 10000,
            name: '[path][name].[hash].[ext]',
            publicPath: '/_next',
          },
        },
      ],
    })
}

what i did was also put this inside webpack :
config.module.rules.push({
      test: /\.js$/,
      include: /node_modules/,
      use: [options.defaultLoaders.babel],
    })

Yes that's correct - you're transpiling the dep to your specific target. That said, can you copy/paste your Babel settings? I'm fine to change our target to make this easier for you and others.

I actually don't have a custom babel config, it only uses the babel config from the next.js.

That's a really good point - we should transpile to the same target as Next.

Hey @RizziWilliam - with v0.36.0 we are transpiling the CJS output to the exact same target that NextJs does. This means if you don't want to transpile your deps you can consume next-i18next/dist/commonjs for the same browser support that NextJs delivers out of the box.

@isaachinman Thanks for your work here. My next app is being compiled to a static site using yarn run build and yarn run export. Unfortunately, Edge and IE failed with this error when I upgraded from 0.8.0 to 0.32.1:
SCRIPT 1028: Expected identifier, string or number
I just upgraded to 0.36.0 and updated my config file to use i18next/dist/commonjs:
const NextI18Next = require('next-i18next/dist/commonjs').default

const options = {
  defaultLanguage: 'en',
  otherLanguages: ['fr'],
}
module.exports = new NextI18Next(options)

Edge now loads correctly. IE has some other errors but they may not be related to this project. I think it'd be useful to document the commonjs target in the README for others who experience this same issue. Thanks!

Hi @2WheelCoder - a couple things:
This project does not support export explicitly as it breaks universal rendering. See the README.
Second, what exactly would you like to have added to the README? The example targets the CJS export.

Hey, going to update to the new version. Thank you for the attention on this issue 👍

@RizziWilliam Please let me know if it fixes your issue!

@isaachinman it's working as expected in edge (and the others browser's, didn't look IE). Doesn't need do put any code on next.config for this to work anymore. Thank you for the quickly fix.

@isaachinman Apologies, I missed that example.
I haven't added the site's second language yet. Looks like I'll have to think through my usage of this package when I do. I only need to toggle translations on the clientside so perhaps all I need is react-i18next, not this package...

@2WheelCoder One of the main reasons you might want SSR (especially in the context of localisation) is for indexing. Just something to keep in mind. Good luck in your exploration!

@RizziWilliam I am very glad to hear it.

Yeah, that's true. The main reason I went with Next was that I could switch over to SSR when we need it and that may be the trigger. But for the next month or so we are supporting only one language so the static site setup is simple to manage.

@2WheelCoder The new serverless stuff in v8 may be of interest to you.


[Bug] Works only on CPU, not using GPU

I give up... I tried to install it in all ways that i can found here for 4 days, but it always ends with GPU not used for generation. I have 1060 6gb and other variants of Stable Difusion works well for me, but not Infinity... Any help, please?

Yeah same with mine. I have an RTX2060 and it uses none GPU and only my CPU

for me too, same behavior, and it's a pity (tesla P40)
Does anyone have an idea what's going wrong?


library not working with new acl system of consul 1.4

Die acl part of the library is not working with the latest consul version 1.4 and the updated acl system. They use new webservice entpoints and new features. The old acl system is also supported by consul1.4 but without the new features like policies and the key_prefix option. Is it planed to adapt python-consul to the new consul version 1.4 and the updates acl system?
Thanks and Regards
Andreas

I started working on it but it's quite a major re-work since the new API is not backwards compatible. Not sure how the creators want to continue since it would break compatibility with Consul versions earlier than 1.4.0

I have some time the next few weeks that I could take a crack at this. @pcantea how far did you end up getting if you don't mind sharing your work?

Hi,
I create a pr to manage new acl system for consul 1.4 and 1.5: https://github.com/cablehead/python-consul/pull/254


Incorrect Unicode Constants - Wikimedia Issue T105315

I've been working with a group investigating this minor outdated accessibility issue on Wikimedia:
https://phabricator.wikimedia.org/T105315
After following the API from Wikimedia to Mathoid I finally arrived here.  I suspect the issue may reside in a few of the unicode constants used in one of this systems APIs. I briefly related it to Peter Krautzberger and he pointed to the 'texvc' library as the most likely spot.
With that said, this issue is beyond the scope and time period my group had anticipated so we agreed to discontinue on our end. Still, if time and convenience allow, please investigate this issue and try to tie it up on Wikimedia. Otherwise, if this issue not related, you can reject this issue. Thanks.

Thanks for your advice on this.  We will take it under advisement as we move forward with the MathJax v3 rewrite.


tests, network: Fix guest PCI address check

What this PR does / why we need it:
The test that examined if the PCI Address specification on input reached the guest has been passing even though no interface appeared (in the guest).
The test is fixed by using a proper PCI Address and simplifying the assertion.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

Can you please explain why the original test passed?

Can you please explain why the original test passed?

If we run the command on a non existing PCI/path, the error includes eth0:
$ grep INTERFACE /sys/bus/pci/devices/foo/*/net/eth0/uevent|awk -F= '{ print $2 }'
grep: /sys/bus/pci/devices/foo/*/net/eth0/uevent: No such file or directory

/approve

/retest


bug:  plugin config "concurrent map writes"

Current Behavior
controller processor occasionally crash during running,
cause by "fatal error: concurrent map writes"
Expected Behavior
no panic
Error Logs

Steps to Reproduce
function call stack like this:

so function   Plugins.DeepCopyInto(pkg/types/apisix/v1/types.go:187)  could be called by multiple goroutine at same time,
type  Plugins  is alias name  to map，
it is not concurrent safe，this will cause  ”concurrent map writes“  error
Environment

APISIX Ingress controller version  1.7.1

The struct on which unmarshal is being performed is created with new() everytime when DeepCopy is called. Which means the data which is being written is not shared between function calls, so how can there be concurrent writes? I am trying to understand that right now.

"I also encountered the same bug; the ingress can restart about three times a week."


[Docs Bug 🐞 report]: change of navigation button from 2.3.0 to 2.4.0

Describe the bug you found in AsyncAPI Docs.

While navigating the streetlights - interactive (alpha) doc to specifications tour, the next button navigates the to 2.3.0 v  whereas with the release of 2.4.0 v it should ideally be navigated to 2.4.0 vpage.

@alequetzalli Please do let me know if you wish to add here something as well :)
Attach any resources that can help us understand the issue.

Code of Conduct

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

I will like to add up to this issue. With the creation of 2 new spec files, the Navigation buttons are not added in the 2.4.0 and 2.3.0 files. (as the spec file generator doesn't have a feature to add the buttons). Kindly look at the other pages' navigation buttons and accordingly add them to these pages as well to maintain the connectivity among the pages.

I would like to work on this issue once confirmed:)

wanna pair on it, @nelsonmic and @starlightknown? How about Nelson does the PR and @starlightknown helps review/test it?

Sure we can pair..

Yep let's do that 💪

great work @nelsonmic ⭐


[dao] do not reuse ID generators

The dao factory used the same ID generator instance for multiple calls to the get_dao method resulting in StopAsyncIteration errors. When no custom generator is provided, the get_dao method will now initiate a new default one.
Thanks to @Cito for pointing that out.

Danke @MoritzHahn1337


Skip leading space on leading pipe in scan_table_head

Fixes #656

Thanks for your contribution! Test cases are great and your fix guided me to find the actual issue.
However, the actual fix is returning the actual offset from calc_indent (1 minus was returned), and your fix didn't take into account tabs, which must be taken into account.


[AppDev] Project Map - OpenFeature

Review and finalize "OpenFeature" section of Project Map Document: https://github.com/cncf/tag-app-delivery/blob/wg-app-dev-map-review/app-development-map/v1alpha1/index.md#openfeature

@salaboy any inputs for improvements/updates on this section?

Closing this for now as we wrapped up iteration 1. We are starting a second iteration on the deliverable, and we'll have a second look at each section for further improvements.


Use chain issue

Tiles don't wait on open animation.
https://codesandbox.io/s/108y319q27

@drcmda

@jass99 this is working as intended, since you're passing the same arguments to useChain on every render, this would cause it to just start both animations immediately.
do you want it to be sequential without changing the order?

Yes.., even somthing like   useChain([springRef, transRef],[4,5]) won't work...
Can you lay it out for me, and can you update the codebox show how sequential without changing order.
Thx

that is not supported internally.. but a workaround is here https://codesandbox.io/s/4lvjk9vxj9 . this would force the object ref to change everytime thereby forcing it to play the animations sequentially.

Bunch of thanks!!!

What was the reason to immediately start all animations on subsequent renders?

What worked for me was to change:
useChain([firstRef, secondRef])
into
useChain([{ current: firstRef.current }, { current: secondRef.current }])

v9 fixes this issue, I think.

@robbertvancaem The workaround  with v8.0.27 causes the following console error web.js:584 Uncaught (in promise) TypeError: Cannot read property 'start' of undefined     at web.js:584 is that safe to ignore?

My Apollo "useQuery" function was somehow breaking the time changes of my "useChain" function, but this fix got it up and running for me again. Thank you!


[Question]: Why is API So Different from OSProcess?

I'm just wondering if there was a calculated reason to depart from the existing API. It would seem to make things much easier to unify as much as possible…

+1

Because part of the reasons of developing this new tool is because I don't like OSProcess API.

Makes sense.  How do you feel about including a shim to mock the old API onto the new?
I could look into writing what I think I need for a start.
Kind of like MockGemStone but for OSProcess things.  Would be good to translate to GemStone's performOnServer: too I guess.

On Jun 20, 2017, at 12:27 PM, marianopeck<EMAIL_ADDRESS>wrote:
Because part of the reasons of developing this new tool is because I don't like OSProcess API.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi @pdebruic
If you want to go ahead with that kind of mock or compatibility package then do it. I am not against. but please make it a separate package. Also, as for GemStone performOnServer: , for my case for example, I have that split into my own (my product) compatibility packages. So I have a polymorphic API that on Pharo it uses OSSubprocess and in GemStone it uses performOnServer:.
Cheers,

I also agree that OSSubprocess API is ugly.
Now, regarding this issue, it was open in february and no action was taking since. I vouch to close it for now.

 Typo?
On Nov 17, 2017 7:25 AM, "Guillermo"<EMAIL_ADDRESS>wrote:

I also agree that OSSubprocess API is ugly.
Now, regarding this issue, it was open in february and no action was
taking since. I vouch to close it for now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/marianopeck/OSSubprocess/issues/24#issuecomment-345204676,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_CgqdrAAB4Wi5PviAiSHCwzfrTDn05ks5s3V77gaJpZM4LzbB3
.

Typo :) I fixed it.


Del does not work as expected on IE11

Expected behavior
delete char to right of cursor
Actual behavior
nothing
Steps to reproduce

on IE11 go to http://codepen.io/jcubic/pen/MbVMwO
enter 1
use left arrow to move the cursor to 1
press DEL

In IE11 the key property for delete key is Del not Delete like in other browsers, fixed in master branch.

thank you for the fast fix.

it seems that this issue is back again in latest version 1.1.0

it was a typo fixed now.

It's in master branch that already have version 1.1.1 but it's not yet released.


Resolve class loader maze

In actual implementation there was supposed that in call of Class.forName(name, initialize, null) will be used caller's class loader but that is not (always) true. This has to be fixed using solution from Find a way out of the ClassLoader maze

Resolved.


MetadataToken collisions causing unpredictable Linq query execution when using custom method call parsers

Problem
The current implementation of LinqParsing class utilises the MetadataToken of the extension method being resolved to a method call parser to speed up future lookups of the same extension method.  I think this was approach was originally introduced in v7.0.  https://github.com/JasperFx/marten/blob/master/src/Marten/LinqParsing.cs#L140
As per the .Net docs for MetadataToken it is only guaranteed to be unique within the scope of the a module (so the same Token can be repeated in different assemblies).
As you increase the number of method call parsers (and extension methods) being registered in your own project, you begin to increase the chance of potential collisions with the inbuilt method call parsers registered in the Marten assembly.  Changes in either assembly over time (e.g. adding more types) means that over time collisions may occur just by updating your own project or Marten by adding classes with methods completely unrelated to Linq parsing.
Further confounding things is that the order in which you execute queries during runtime impacts behaviour - for my particular application the collision was occurring with one of my method call parsers and the inbuilt MaybeArchived method.  If I ran a test in my test suite just exercising my extension method, it would work, if I ran the whole suite of tests (which include other tests that execute queries using MaybeArchived first) then my later tests would fail sometimes, depending on xunits random order of test execution.
This has ended up being a bit of a nightmare for me because MaybeArchived actually just translates to 1 = 1 in the executed query - so it's like our custom Linq expression was never applied to the query 😬 depending on your application this can have security-impacting implications (thankfully for us it only impacted correctness not security because of multi-tenancy) but it has been a confounding bug to track down.
Proposed fix
I think the method call parser needs to take the module of the method's declaring type into account when caching the lookup of method call parsers.  There may be more efficient ways to do it, but I think something like this would work:
private ImHashMap<Module, ImHashMap<int, IMethodCallParser>> _methodParsersByModule =
        ImHashMap<Module, ImHashMap<int, IMethodCallParser>>.Empty;

    internal IMethodCallParser FindMethodParser(MethodCallExpression expression)
    {
        var module = expression.Method.Module;

        if (!_methodParsersByModule.TryFind(module, out var methodParsers))
        {
            methodParsers = ImHashMap<int, IMethodCallParser>.Empty;
            _methodParsersByModule = _methodParsersByModule.AddOrUpdate(module, methodParsers);
        }

        if (methodParsers.TryFind(expression.Method.MetadataToken, out var parser))
        {
            return parser;
        }

        parser = determineMethodParser(expression);

        _methodParsersByModule = _methodParsersByModule.AddOrUpdate(module, methodParsers.AddOrUpdate(expression.Method.MetadataToken, parser));

        return parser;
    }

I've created a fix PR for review here: https://github.com/JasperFx/marten/pull/3372
Detection / work-around
For anyone finding this issue who is maybe stuck on an older version of Marten v7.x (pre this getting fixed) I would suggest adding a rudimentary test to detect instances of collision, something along the lines of the below - the impact of the collision on the correctness of your queries can be highly impactful, particularly if your unlucky and end up colliding with the MaybeArchived (most other collisions will probably just result in a runtime error if the arguments don't line up).
    public class MethodCollision(MethodInfo method, MethodInfo collidedMethod)
    {
        public string MethodName => method.Name;
        public string MethodDeclaringType => method.DeclaringType!.Name;
        public string ColidedMethodName => collidedMethod.Name;
        public string ColidedMethodDeclaringType => collidedMethod.DeclaringType!.Name;
    }

    [Fact]
    public void MetadataTokenUniqueness()
    {
        var extensionMethodsByToken = typeof(SomeTypeInYourProject).Assembly.GetTypes()
            .Where(x => x.Name.Contains("extension", StringComparison.OrdinalIgnoreCase))
            .Where(x => x.IsStatic())
            .SelectMany(x => x.GetMethods(BindingFlags.Public | BindingFlags.Static))
            .ToDictionary(x => x.MetadataToken);

        var martenExtensionMethodsByToken = typeof(Marten.LinqExtensions).Assembly.GetTypes()
            .Where(x => x.Name.Contains("extension", StringComparison.OrdinalIgnoreCase))
            .Where(x => x.IsStatic())
            .SelectMany(x => x.GetMethods(BindingFlags.Public | BindingFlags.Static))
            .ToDictionary(x => x.MetadataToken);

        var collisions = new List<MethodCollision>();

        foreach (var extensionMethod in extensionMethodsByToken)
        {
            if (martenExtensionMethodsByToken.TryGetValue(extensionMethod.Key, out var martenMethod))
            {
                collisions.Add(new MethodCollision(extensionMethod.Value, martenMethod));
            }
        }

        if (collisions.Count > 0)
        {
            Assert.Fail("Collisions detected: " + JsonSerializer.Serialize(collisions));
        }
    }

Once you determine there are collisions the you can make changes to your code to prevent them - generally just adding a dummy class in the same file before the extension methods are declared with 1 or more methods can cause the metadata token numbering to change enough to stop the collisions 😢 though there's no guarantee they wont come back when adding other classes/methods to your project later on (the metadata tokens are assigned roughly based on the order of C# files being compiled in your project).
public class DummyClassToImpactMetadataToken
{
    public string Method1() {}
    public string Method2() {} // keep going until you don't have collisions / tests pass again.. good luck!
}

We did have a proposed fix for this a few months ago that got missed by the pile of other PRs: https://github.com/JasperFx/marten/pull/3060. I'm not super fussed by either implementation; whichever one is better for performance is the preference.

We did have a proposed fix for this a few months ago that got missed by the pile of other PRs: #3060. I don't have a strong opinion of either implementation; whichever one is better for performance is the preference.

Ahh I missed that earlier issue, sorry to open up a duplicate @Hawxy 😬
I would need to profile both implementations as I suspect they will be quite close in terms of performance but I would guess the version that relies on bit-shifting (https://github.com/JasperFx/marten/pull/3060/files#diff-5aa1724a43832824d3e1c1ec9a95e5844dbf1f8cc7b5f53decc6eb4c16976195R143) is probably going to be faster as it won't rely on a second level of indirection.  There is (however tiny) a small chance of potential hash collisions between modules, but it's going to be very statistically unlikely, but my proposed PR would avoid that ever happening.  I'm not fussed either way as long as it gets fixed 😁

Looks to be closed by https://github.com/JasperFx/marten/pull/3372

Thanks for merging this @jeremydmiller @Hawxy much appreciated!


React quick start still has shims for setTimeout(), etc.

https://github.com/AdobeXD/plugin-samples/blob/master/quick-start-react/src/react-shim.js is out of date.
If we update the sample's minVersion to 16, we can remove the setTimeout() & clearTimeout() shims.
If we update min to 18, we can remove the requestAnimationFrame() & cancelAnimationFrame() shims.

addressed


"The configuration file contains legacy configuration keys." on fresh LXD install from ubuntu-lxc/lxd-stable

Required information

Distribution: Ubuntu Server
Distribution version: 17.04
The output of "lxc info": https://pastebin.com/raw/E5b0qKt7

Issue description
I am getting error: The device doesn't exist - The configuration file contains legacy configuration keys on fresh installations of Ubuntu Server 17.04 with LXD updated to 2.18. After installing 17.04, I run the following commands:
add-apt-repository -y ppa:ubuntu-lxc/lxd-stable
apt update
apt upgrade -y
lxd init --auto --storage-backend dir

After this I get the configuration error when I create profiles, networks, containers, etc.
Just to test, I purged lxcfs and lxd, removed /root/.config/lxc and the config in my home directory as well, and removed /usr/share/lxc and /usr/share/lxcfs. Then I ran apt install lxd and configured it again. The errors still occurred.

Release notes supposedly contain info on how to handle this, but they neither inform where the config files are stored by default. Basic thing, but missing.
(Separately, I was surprised that this kind of major change was done - as far as I could tell - rather silently; those who have lxc in production and upgrade packages won't be happy when this hits them. I just spent 30 minutes trying to figure what hit me and where the heck the config files are stored - so far no luck.)

LXC 2.1 comes with a lot of configuration key changes but is entirely backwards compatible. If you started a container at a point where you had liblxc < 2.1 installed the container uses the old library and hence lxd will use the legacy configuration keys when creating a config for the container. When you now update, and call e.g. lxc exec then the exec will load the new liblxc >= 2.1 version at which point you'll get these errors reported. This however is non-crucial and - if you can - you can simply restart the container and the warning should vanish.
LXD generates the config on the fly so there's also nothing that you need to-do on-disk itself.

Oh, I see - you're right, the container does start. The warning looks too scary.
I hope it's within the scope of this issue to ask - where are the config files stored? The message suggests to fix it, but it's not easy to figure out where the config files are stored.

@scaleoutsean, there's no need for you to touch any configuration files manually with LXD. This will only be in-memory. :)

I have 2.1.0-0ubuntu1~ubuntu17.04.1~ppa1 installed; my reason for creating this issue is because this error shows up when LXD is first initialized and containers are created after the update to 2.18.

@ajthemacboy Can you do:

systemctl restart lxd
lxc launch ubuntu:16.04 test
lxc exec test bash

And see if that shows you the warning (it shouldn't)? If it does, then please show "lxc config show --expanded test" so we can check if there's anything in the container config that may be causing problems.

I did all of that. Here is the result:
root@userv1704:~# systemctl restart lxd
root@userv1704:~# lxc launch ubuntu:16.04 test
Creating test

The container you are starting doesn't have any network attached to it.
  To create a new network, use: lxc network create
  To attach a network to a container, use: lxc network attach

Starting test
root@userv1704:~# lxc exec test bash
The configuration file contains legacy configuration keys.
Please update your configuration file!
root@test:~#

root@userv1704:~# lxc config show test
architecture: x86_64
config:
  image.architecture: amd64
  image.description: ubuntu 16.04 LTS amd64 (release) (20170919)
  image.label: release
  image.os: ubuntu
  image.release: xenial
  image.serial: "20170919"
  image.version: "16.04"
  volatile.base_image: 03c2fa6716b5f41684457ca5e1b7316df520715b7fea0378f9306d16fdc646ee
  volatile.idmap.base: "0"
  volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprang
e":65536}]'
  volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"M
aprange":65536}]'
  volatile.last_state.power: RUNNING
devices: {}
ephemeral: false
profiles:
- default
stateful: false
description: ""

However, after restarting the container the error goes away.
root@userv1704:~# lxc restart test
root@userv1704:~# lxc exec test bash
root@test:~#

@ajthemacboy, can you show me the output of lxc info, please?

stgraber@castiana:~$ rssh<EMAIL_ADDRESS>Warning: Permanently added 'vm01.maas.mtl' (ECDSA) to the list of known hosts.
root@vm01:~# clear
root@vm01:~# apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu zesty InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu zesty-updates InRelease [89.2 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu zesty-backports InRelease [89.2 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu zesty-security InRelease [89.2 kB]
Fetched 268 kB in 0s (510 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
root@vm01:~# apt-add-repository ppa:ubuntu-lxc/lxd-stable
 This PPA contains the latest stable release of LXD as well as the latest stable version of any of its dependencies.
 More info: https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxd-stable
Press [ENTER] to continue or ctrl-c to cancel adding it

gpg: keybox '/tmp/tmpa1ieh5s7/pubring.gpg' created
apt updategpg: /tmp/tmpa1ieh5s7/trustdb.gpg: trustdb created
gpg: key D5495F657635B973: public key "Launchpad PPA for Ubuntu LXC team" imported
gpg: Total number processed: 1
gpg:               imported: 1
OK
root@vm01:~# apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu zesty InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu zesty-updates InRelease [89.2 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu zesty-backports InRelease [89.2 kB]
Get:4 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu zesty InRelease [20.7 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu zesty-security InRelease [89.2 kB]
Get:6 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu zesty/main amd64 Packages [4,092 B]
Get:7 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu zesty/main Translation-en [2,488 B]
Fetched 295 kB in 1s (283 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
6 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@vm01:~# apt upgrade -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  xdelta3
The following packages will be upgraded:
  liblxc1 libseccomp2 lxc-common lxcfs lxd lxd-client
6 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 5,642 kB of archives.
After this operation, 15.9 MB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu zesty/universe amd64 xdelta3 amd64 3.0.11-dfsg-1ubuntu1 [68.9 kB]
Get:2 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu zesty/main amd64 liblxc1 amd64 2.1.0-0ubuntu1~ubuntu17.04.1~ppa1 [292 kB]
Get:3 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu zesty/main amd64 lxc-common amd64 2.1.0-0ubuntu1~ubuntu17.04.1~ppa1 [93.3 kB]
Get:4 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu zesty/main amd64 libseccomp2 amd64 2.3.1-2.1ubuntu2~ubuntu17.04.1~ppa1 [37.3 kB]
Get:5 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu zesty/main amd64 lxcfs amd64 2.0.7-0ubuntu5~ubuntu17.04.1~ppa1 [42.5 kB]
Get:6 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu zesty/main amd64 lxd amd64 2.18-0ubuntu2~ubuntu17.04.1~ppa1 [3,105 kB]
Get:7 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu zesty/main amd64 lxd-client amd64 2.18-0ubuntu2~ubuntu17.04.1~ppa1 [2,003 kB]
Fetched 5,642 kB in 24s (231 kB/s)
(Reading database ... 62785 files and directories currently installed.)
Preparing to unpack .../0-liblxc1_2.1.0-0ubuntu1~ubuntu17.04.1~ppa1_amd64.deb ...
Unpacking liblxc1 (2.1.0-0ubuntu1~ubuntu17.04.1~ppa1) over (2.0.8-0ubuntu1~17.04.2) ...
Preparing to unpack .../1-lxc-common_2.1.0-0ubuntu1~ubuntu17.04.1~ppa1_amd64.deb ...
Unpacking lxc-common (2.1.0-0ubuntu1~ubuntu17.04.1~ppa1) over (2.0.8-0ubuntu1~17.04.2) ...
Preparing to unpack .../2-libseccomp2_2.3.1-2.1ubuntu2~ubuntu17.04.1~ppa1_amd64.deb ...
Unpacking libseccomp2:amd64 (2.3.1-2.1ubuntu2~ubuntu17.04.1~ppa1) over (2.3.1-2.1ubuntu1) ...
Preparing to unpack .../3-lxcfs_2.0.7-0ubuntu5~ubuntu17.04.1~ppa1_amd64.deb ...
Unpacking lxcfs (2.0.7-0ubuntu5~ubuntu17.04.1~ppa1) over (2.0.7-0ubuntu1~17.04.2) ...
Preparing to unpack .../4-lxd_2.18-0ubuntu2~ubuntu17.04.1~ppa1_amd64.deb ...
Warning: Stopping lxd.service, but it can still be activated by:
  lxd.socket
Unpacking lxd (2.18-0ubuntu2~ubuntu17.04.1~ppa1) over (2.12-0ubuntu3) ...
Preparing to unpack .../5-lxd-client_2.18-0ubuntu2~ubuntu17.04.1~ppa1_amd64.deb ...
Unpacking lxd-client (2.18-0ubuntu2~ubuntu17.04.1~ppa1) over (2.12-0ubuntu3) ...
Selecting previously unselected package xdelta3.
Preparing to unpack .../6-xdelta3_3.0.11-dfsg-1ubuntu1_amd64.deb ...
Unpacking xdelta3 (3.0.11-dfsg-1ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up lxd-client (2.18-0ubuntu2~ubuntu17.04.1~ppa1) ...
Processing triggers for libc-bin (2.24-9ubuntu2.2) ...
Setting up libseccomp2:amd64 (2.3.1-2.1ubuntu2~ubuntu17.04.1~ppa1) ...
Processing triggers for systemd (232-21ubuntu5) ...
Setting up lxcfs (2.0.7-0ubuntu5~ubuntu17.04.1~ppa1) ...
Processing triggers for man-db (<IP_ADDRESS>-2) ...
Setting up xdelta3 (3.0.11-dfsg-1ubuntu1) ...
Setting up liblxc1 (2.1.0-0ubuntu1~ubuntu17.04.1~ppa1) ...
Setting up lxd (2.18-0ubuntu2~ubuntu17.04.1~ppa1) ...
Setting up lxc-common (2.1.0-0ubuntu1~ubuntu17.04.1~ppa1) ...
Installing new version of config file /etc/apparmor.d/abstractions/lxc/start-container ...
Processing triggers for libc-bin (2.24-9ubuntu2.2) ...
root@vm01:~# lxd init --auto --storage-backend dir
LXD has been successfully configured.
root@vm01:~# systemctl restart lxd
root@vm01:~# lxc launch ubuntu:16.04 test
If this is your first time using LXD, you should also run: lxd init
To start your first container, try: lxc launch ubuntu:16.04

Creating test

The container you are starting doesn't have any network attached to it.
  To create a new network, use: lxc network create
  To attach a network to a container, use: lxc network attach

Starting test
root@vm01:~# lxc exec test bash
root@test:~# exit
root@vm01:~#

@ajthemacboy what did I miss?

I'm not sure, your setup looks identical to mine. I am reinstalling for the 3rd time (have been testing various things in virtual environments); maybe init auto is missing something on my setup? I am using Ubuntu Server 17.04 direct from the website in a Hyper-V VM. Either way if you cannot reproduce this then I'm probably doing something wrong.
I will close this issue for now and reopen if I figure anything out. Thanks!

In my case, it was Ubuntu 17.04 server deployed through MAAS and then using the same commands you mentioned, including the --auto, so should have been identical to your setup...


fix download percentage not always getting to 1 due to rounding errors

Sometimes download percentage does not go to '1' staying at 0.99999999999. The issue is due to rounding errors when creating: let slice = Double(1.0)/Double(expectedLength) in HTTPProgress constructor.

Thank you for fix!

Thank you for fix!

np. thx for the library :)


Bot Registration Failure

Sometime when registering a nick, the bot fails to register successfully and hangs with no mention of failure.
Need to fix.

Issue was fixed in git commit.
https://github.com/mac-reid/lazydcc/commit/c9fc2beffa4dbaaebbf99a1b9da18bc1d58be217


Q: why different file sizes for HEX binary?

Hi,
first, thank you very much for this great project 👍
I've build a bwhoop.hex file with gcc (using Travis-CI), but to my surprise, the final .HEX file is 43kByte, instead of 33kByte you provide in bin folder.
Any idea, why there is such a huge difference? (and yes, my compiled version flies ;-) )
Background information:
I've forked it and using now Travis-CI as build agent (see my changes in travis.yml to automatically export .hex file).
Output
arm-none-eabi-size bwhoop.elf
   text	   data	    bss	    dec	    hex	filename
  15236	    128	   2832	  18196	   4714	bwhoop.elf
arm-none-eabi-objcopy -O binary bwhoop.elf bwhoop
arm-none-eabi-objcopy -O ihex bwhoop.elf bwhoop.hex

Regards
Martin

yes, gcc will compile a file size about 40% larger compared to keil, it will also be slower
the gcc fork for cortex is maintained by arm employees I think, and keil is arm's commercial software, I suppose they made it this way

Hi,
thank you for this explanation.
I thought i has to do with e.g. debug symbols are not stripped (did not checked this yet).
What a pity, I found this gcc approach really charming, because of the sleek automation. I even thought about extending the Makefile, to build multiple firmwares in one run and upload them to GitHub - you know, similar like Betaflight is doing. This would ease development very much and give also users a great reliable source for download.
(I mean, using GitHub releases is more convenient and transparent to users and additionally leaves developers freedom to develop on master branch. Release also can contain a release note.)


Combining sort and limit not working

I'm not sure if this is a bug but I don't see any support forum or wiki so reporting it here.
I have this query that works in against vanilla MongoDB:
db.getCollection('widgets').find({num_skus: 0}).sort({price: -1}).limit(5)

i.e. get the 5 highest priced widgets that have num_skus == 0. I get 5 results back.
In Monk I am trying:
db.get('widgets').find({num_skus: 0}, {sort: {price: -1}, limit: 5}, function(e, docs) {
  // callback happens with docs undefined.
});

and I get no results back.
Am I doing something wrong or is this a bug?

Might be a dup of #107. If I look at the error it is the same (QueryFailure flag set on getmore command).

I had a similar issue:
{ [MongoError: QueryFailure flag set on getmore command] name: 'MongoError' }
when using this query
db_collection.find({}, {"limit" : per_page, "skip": skip, "sort":{"created": -1}},
    function (db_err, db_docs) {
              .
              .

I was able to fix it by creating an index on the collection. I assume for me it was related to this:
https://docs.mongodb.org/v3.0/reference/limits/#Sort-Operations

Sort Operations
If MongoDB cannot use an index to get documents in the requested sort order, the combined size of all documents in the sort operation, plus a small overhead, must be less than 32 megabytes.

A lot has changed in<EMAIL_ADDRESS>I'm closing this issue, feel free to open a new one if it is still an issue.


Update running-testnet-node.md to avoid confusion for beginners

Both Release and Debug stacks-node  is being installed which maybe not needed.
stacks-node debug execution may not be needed to avoid confusion like https://github.com/blockstack/docs/issues/833

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

@wileyj could you help review this? Why do we have release & debug instructions? Any reason not to remove the debug steps?

@wileyj could you help review this? Why do we have release & debug instructions? Any reason not to remove the debug steps?

I would say keeping the debug binary compile command in the docs is important.
However, from the current docs it's not clear what this command is adding to the binary.
I would think there should be a Note or something that the command cargo build --workspace --bin stacks-node will add additional debugging symbols (useful for devs mainly).

@wileyj could you help review this? Why do we have release & debug instructions? Any reason not to remove the debug steps?

@agraebe @agnelvishal
something like this perhaps? (formatting is a little weird):
Install the Stacks node by running:
# release build
cargo build --workspace --release --bin stacks-node
# binary will be in target/release/stacks-node
./target/release/stacks-node krypton

For a Binary with extra debugging symbols:
cargo build --workspace --bin stacks-node
# binary will be in target/debug/stacks-node
./target/debug/stacks-node krypton

I like it! @agnelvishal could you update the  PR please? 🙏

@wileyj  It would be better and accurate if ./target/release/stacks-node krypton and ./target/debug/stacks-node krypton are placed in 'Running the node' section. Agree?

@wileyj It would be better and accurate if ./target/release/stacks-node krypton and ./target/debug/stacks-node krypton are placed in 'Running the node' section. Agree?

Logically that makes sense - and the edits you've made look good!
I'll defer to @agraebe

@wileyj It would be better and accurate if ./target/release/stacks-node krypton and ./target/debug/stacks-node krypton are placed in 'Running the node' section. Agree?

Logically that would make sense to me, and the edits look good - thanks!
I'll defer to @agraebe for approval though, just added them as a reviewer

looks great, thanks @agnelvishal!


When testing, Event mock object lacks of listen() method.

Laravel Version: 5.3.19
PHP Version: 7.0.0
Database Driver & Version: N/A

Description:
Since the 5.3.19 update, some of my tests which implies events and artisan calls have errors. This appends because the App\Console\Kernel::commands() method execute the base_path('routes/console.php') file, in which there is an Artisan::command() call by default, which leads us to Illuminate\Foundation\Console\Kernel::command() in which there is (finally) a $this->app['events']->listen() instruction. But when using, in tests, $this->withoutEvents() (from the MockApplicationServices trait), the mock created here lacks of this listen() method.
Adding a $mock->shouldReceive('listen'); instruction in this method solve the issue. But since I am not sure how deep it can go, so I choose to write an issue instead of creating a PR.
Steps To Reproduce:
Write a test with $this->withoutEvents() and an artisan call, leaving the default routes/console.php file content.

Opened a PR to fix that: https://github.com/laravel/framework/pull/16012


Implement migration and database creation startup flags

Implement a command line flag --with-migration <url> that will instruct the main program to download data from a URL and insert in the database before bringing the server up.
If the database already has data, throw an error. We could create another flag --recreate-database that will drop and create a database from scratch. So, if the user executes:
$ stop-analyzing-api --recreate-database --with-migration https://endpoint-with-migration-data

The service will perform a clean start loading this data. This will be very useful for development porpuses.
How about that?
@jairsjunior or @flaviostutz, any thoughts?

Hello guys!
Quick question here... Do we have any thoughts about content, protocol or anything that the Url (endpoint-with-migration-data) is going to provide?
Are we going to expose this URL with the migration information inside the "stop-analyzing-api" service itself, so we would use it to migrate from an existing scenario to another OR are we going to have a third party service with the content to be migrated?
Thanks!

Hi @zamariola ! Good point!
We will have a mix of the second and third option. We are going to have the data coming from third parties and those third parties will follow the spec that will be defined in #7 . This way we will be able to decouple "data gathering" from "data presenting" in a smooth manner.
So, I think we can discuss in #7 this content spec and protocol. Agreed?

Hi @zamariola !
I think you would be interested in taking a look or maybe giving some thoughts at #8 .


[Quick Launch] Update 0.02

Moved configuration from launcher to Settings->Apps.

Thanks! Just wondering about "type": "launch", - you're still expecting there to be another launcher on the system as well? Eg this isn't expected to erase the default launcher?
There's an issue open at https://github.com/espruino/BangleApps/issues/1682 and when that gets fixed, it might mean that installing this tries to replace the default launcher with it.
Please could you use '"type": "bootloader"'`?

// if this is 'bootloader' then it's code that is run at boot time, but is not in a menu

Ah, I see. Updated metadata. I wanted to hide it from the default launcher but I wasn't sure what app type I was supposed to specify. Is there a list of app types I can look at?

Thanks! Yes, there's a list at: https://github.com/espruino/BangleApps#metadatajson-format
If you think I can add some better docs (or links to that somewhere) please let me know though - or even better do a PR ;)


PWA plugin uses Google CDN by default with no (obvious) way to turn it off

Version
4.5.4
Reproduction link
This is just the default created by vue-cli with PWAs enabled:
https://github.com/KB1RD/google-cdn-default
Environment info
  System:
    OS: Linux 4.4 Ubuntu 16.04.6 LTS (Xenial Xerus)
    CPU: (16) x64 AMD Ryzen 7 1700 Eight-Core Processor
  Binaries:
    Node: 12.16.1 - /usr/local/bin/node
    Yarn: 1.21.1 - /usr/local/bin/yarn
    npm: 6.13.4 - /usr/local/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: 77.0.1
  npmPackages:
    @ant-design-vue/babel-helper-vue-transform-on:  1.0.1
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0
    @vue/babel-plugin-transform-vue-jsx:  1.1.2
    @vue/babel-preset-app:  4.5.4
    @vue/babel-preset-jsx:  1.1.2
    @vue/babel-sugar-functional-vue:  1.1.2
    @vue/babel-sugar-inject-h:  1.1.2
    @vue/babel-sugar-v-model:  1.1.2
    @vue/babel-sugar-v-on:  1.1.2
    @vue/cli-overlay:  4.5.4
    @vue/cli-plugin-babel: ~4.5.0 => 4.5.4
    @vue/cli-plugin-eslint: ~4.5.0 => 4.5.4
    @vue/cli-plugin-pwa: ~4.5.0 => 4.5.4
    @vue/cli-plugin-router:  4.5.4
    @vue/cli-plugin-vuex:  4.5.4
    @vue/cli-service: ~4.5.0 => 4.5.4
    @vue/cli-shared-utils:  4.5.4
    @vue/component-compiler-utils:  3.2.0
    @vue/preload-webpack-plugin:  1.1.2
    @vue/web-component-wrapper:  1.2.0
    eslint-plugin-vue: ^6.2.2 => 6.2.2
    vue: ^2.6.11 => 2.6.12
    vue-eslint-parser:  7.1.0
    vue-hot-reload-api:  2.3.4
    vue-loader:  15.9.3 (16.0.0-beta.5)
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.6.11 => 2.6.12
    vue-template-es2015-compiler:  1.9.1
  npmGlobalPackages:
    @vue/cli: 4.4.6

Steps to reproduce

Run yarn build
Look in @/dist/service-worker.js. Notice the importScripts("https://storage.googleapis.com/workbox-cdn/releases/4.3.1/workbox-sw.js"); line.
Note that this still happens when building a custom worker with InjectManifest

What is expected?

The documentation for @vue/cli-plugin-pwa should inform users that the Google CDN will be used and provide a method for changing CDNs or switching to all-local serving
This method should not be too complicated

What is actually happening?

There seems to be no warning or note anywhere that the CDN will be used, except if the user is familiar with workbox
The method to change CDNs is too complicated. As far as I can tell, this would involve having a separate webpack build that builds the worker and uses InjectManifest to make it work, but I still cannot figure out how to remove the CDN (except by editing it out post-build)

The worst thing is, that it not only uses CDN but also an outdated version v4.3.1. The current version as of this writing would be v.5.1.3. There is also no easy way to update this, because @vue/cli-plugin-pwa has workbox-webpack-plugin with version ^4.3.1 as dependency (current version again would be 5.1.3) and workbox-webpack-plugin has then workbox-build with version ^4.3.1 as dependency (current version again would be 5.1.3). --- workbox-build is the package responsible for loading from CDN.

if you are using yarn you can use the resolutions field in the package.json file to update this, it works quite well. it was mentioned here.
#5119

For using a local import (no CDN), see https://github.com/vuejs/vue-cli/issues/3361#issuecomment-457134243

For using a local import (no CDN), see #3361 (comment)

This no longer works... Google removed support for it. You can see this configuration option present in 2019, when that comment was posted, but isn't there now. Just did a quick search through their repo to confirm that it isn't a hidden config option, and their unit tests ensure that it does not exist. Thank you for pointing that out, though.

For using a local import (no CDN), see #3361 (comment)

This no longer works... Google removed support for it. You can see this configuration option present in 2019, when that comment was posted, but isn't there now. Just did a quick search through their repo to confirm that it isn't a hidden config option, and their unit tests ensure that it does not exist. Thank you for pointing that out, though.

I just generated the service worker with a local import using that option and can confirm that it still works (an extra folder with a dependeny is generated into the /dist). Maybe vue-cli is using an old version for that purpose.

@ssc-hrep3 you're right, my bad... I forgot Vue was using an older version. As mentioned in that issue you linked, though, it would be good to make this a default or at least document it.
The one thing is the plan for Vue CLI v5 has a plan to support Workbox 6, which removes this option.

I don't mean to spam this issue, but this issue in Workbox seems relevant:

For the time being, we will still publish bundles of the Workbox runtime to the CDN, but my expectation is that it will be only be useful for injectManifest users. Longer-term, we may phase out the CDN entirely, and encourage all developers to go through a flow that produces a Workbox runtime bundle that's customized for their specific usage.

Later today I might play around with the Vue CLI dev builds to see if Workbox 6 defaults to building locally instead of using the CDN. It's a bit hard to track progress on this issue.


Corrected location for report phishing manifest file

Location was changed and so needed to make changes to communicate the same to customer.

@chrisda could you please approve these changes

Learn Build status updates of commit fffd93b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/submissions-users-report-message-add-in-configure.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 8577aa0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/submissions-users-report-message-add-in-configure.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit cdf51ac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/submissions-users-report-message-add-in-configure.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Update main.py

No write_ply function in mesh.py.  It's called write_mesh.

I think you would need to edit line number 108, to make the function that was using write_ply to write_mesh, if this is to have an effect, or am i missing something :question:


Add  a generic Entity type

I would like to enter metadata in OpenMetadata for which currently no entity is defined, e.g.:

Product information and/or product models
Information models
Thesauruses
...

A practical approach would be to define a generic Product entity, a bit similar to the existing (ML)Model, but instead of an algorithm attribute I would add a definition attribute which stores a JSON definition.
A tag can be used to specify the type of instances, eg product or thesaurus
@harshach Is this a good idea?

@tomtor Can you elaborate on what the product entity will have and what it will represent.
I think adding a new entity became simpler now with new code rebase.
cc @sureshms

I think adding a new entity became simpler now with new code rebase.

That's interesting, I started on adding a Thesaurus entity:
https://github.com/tomtor/OpenMetadata/commit/77198d3a2342dd842df47fe9b443ad401da9c3b1
which has a SKOS property which would contain JSON-LD data. I get a 500 error when feeding test data to the server, so I probably have to add some Java code to handle REST calls to the Theasurus API.
After this I figured out that having a generic Entity to store metadata encoded in a JSON representation would be more flexible and require less code. The best name I could think of is product, but perhaps a better name could be choosen.
So replace SKOS with definition and thesaurus with product in https://github.com/tomtor/OpenMetadata/blob/77198d3a2342dd842df47fe9b443ad401da9c3b1/catalog-rest-service/src/main/resources/json/schema/api/data/createThesaurus.json to get the idea.

@harshach  Some more general remarks/questions about metadata in Open-Meta.
Say we have a database table with cars and one of the columns is named EngineType. This can be 'petrol,diesel,electric,hybrid,unknown' (a code list).
How/where would we store this and how do we link this to the column?

How/where would we store this and how do we link this to the column?

To partially answer my own question, we can in the current release add textual descriptions which contain text and URLs.
I think the GUI and generic metadata model should also allow the user to add links (Entityrefs) from any Entity to any other Entity.

@tomtor, can you add details on what is a thesaurus entity  in the context of OpenMetadata (thesaurus.json from current patch does not describe what that entity is. See table.json for how to add details). It might be a good to write a simple one page on what it is, how it will be used, and how it is surfaced in the UI.

@tomtor, can you add details on what is a thesaurus entity in the context of OpenMetadata (thesaurus.json from current patch does not describe what that entity is. See table.json for how to add details). It might be a good to write a simple one page on what it is, how it will be used, and how it is surfaced in the UI.
Given not a lot of people have understanding of SKOS (including me), json-ld etc. this might be a great talk to cover in our biweekly meetings to get everyone up to speed. WDYT?

@sureshms Sure, the point is that currently OpenMetadata only allows tagging and some text with URLs embedded to add additional information to datasets. In an organization people are often working with data related to specific real world objects or concepts.
So a column in a dataset is named eg MTBF or Mean-Time-Between-Failure. A user could add a textual description to clarify how MTBF is defined or calculated (this is an example of metadata) and how it relates to other quality aspects. This is important for users of the data, because without this info (metadata) they could use the data in an incorrect way. But what if many different datasets from a department have MTBF data. He/she would have to copy this text anywhere in OpenMetadata?
We need a central place to store this metadata. The idea is that we can define entities which contain a SKOS definition. A department/team would create a SKOS Thesaurus entity to store descriptions of concepts, how they relate, a collection of allowed values (a bit like a JSON-Schema enum) etc. These could also be created with a connector which reads this data from another system.
The Thesaurus create API takes a parameter with the thesaurus definition data as a (large) string in JSON or another format. We could design our own JSON-Schema for this, but it is better to support the use of an existing standard (SKOS). A thesaurus entity which is displayed in the GUI would show a list of the concepts defined in it. In its simplest form each concept can have a HTML-anchor and the user could copy the URL which points to this entry in the thesaurus. This URL can be pasted eg in the description of a dataset column.
https://www.w3.org/TR/skos-primer/#secintro is good introduction for SKOS.
A quote from that introduction:
SKOS can also be seen as a bridging technology, providing the missing link between the rigorous logical formalism of ontology languages such as OWL and the chaotic, informal and weakly-structured world of Web-based collaboration tools, as exemplified by social tagging applications.
The aim of SKOS is not to replace original conceptual vocabularies in their initial context of use, but to allow them to be ported to a shared space, based on a simplified model, enabling wider re-use and better interoperability.
There exists OpenSource SKOS publishing software (SKOSMOS), see eg https://skosmos.v7f.eu/unesco/nl/page/C01717?clang=en for an example of a huge thesaurus (I would expect that Thesauruses in OpenMetadata would be small and tied to a company or team) but it would be nice to integrate this higher level metadata in OpenMetaData.

@tomtor, thank you for the explanation.
I am very happy that you have thought through and added a lot of code. I hope my comments don't discourage you. We have two types of tags - Descriptive and Classification. Example of Descriptive tag is User and Classification is - Tiers, PersonalData and PII. Descriptive tags can be added to describe things such as MTBF and be attached to fields of an entity. And then there are business glossaries that the data world is used to. Some systems uses tags also as business glossary.
We did try to use RDFs, Owl, and Json-ld etc. at Uber in the past. Most developers lacked knowledge about them and pushed back on them for the simplicity of JSON schema + descriptions. I understand the benefits of what you are trying to do, but it comes at a huge complexity to our users and I fear they would not be able to use it. More than formally defining concepts and tying it with other standard concepts to organize knowledge, simply describing it in a place and making it reusable will keep it simple for our users.
Perhaps when we are more mature and have solved basic problems, evolution toward knowledge graph, semantic web etc. might be more appropriate. But when I read OWL, RDF, JSON-LD, and the complex syntax, I feel simply overwhelmed. This will be true for most of our users.
What do you think?

Perhaps when we are more mature and have solved basic problems, evolution toward knowledge graph, semantic web etc. might be more appropriate. But when I read OWL, RDF, JSON-LD, and the complex syntax, I feel simply overwhelmed. This will be true for most of our users.

@sureshms I agree, I am not a linked-data person myself and I am all in for a conceptual simple approach.
The only reason I am proposing doing something with SKOS is that it is an existing standard in which concepts are defined in some organizations.
We do not need to support the full Linked-Data machinery. Translating SKOS to our own JSON-Schema based tagging approach is sufficient. End-users will never see RDF.
We should think of a thesaurus as simply a collection of tags.
A business glossary is just a thesaurus.
An elegant solution would be to extend the current OpenMetadata tagging implementation with tags of the form thesaurus:concept. When users click the tag they see the definition of this tag and the entities tagged with it.
We could also use the name glossary instead of thesaurus to make it a bit less formal?

Perhaps when we are more mature and have solved basic problems

I am missing some more basic entities in OpenMetaData.
A simple one is REST-services which are implemented by teams in the organization.
These entities should at least  registrate the endpoints and an optional swagger URL.
I can create an issue for this?
A more complex problem is documenting the relation between datasets (or entities in general). I think it's fantastic that OpenMetadata uses graphs of JSON-schemas. That's why it is conceptual superior to other solutions and it allows us to extend the system in an elegant way.
Regarding model, I think it would be better if the current Model would be named ML-Model because there are a lot of models and this is confusing. Adding a generic JSON-Model entity would allow users of OpenMetaData to extend the system with new types of entities (simple by tagging the JSON-Model entity) without writing lots of code. I underestimated the amount of code needed to add my concept Thesaurus entity. If we add a JSON-schema visualization (#1011) OpenMetadata would be an even better environment to work with Metadata.

A JSON-Model entity would have two attributes (and the standard OpenMetadata attributes):

A JSON-Schema
A JSON-Object which is an instance of the schema

One of the two may be empty. (We could also model 2 entities, A JSON-Object entity with an optional reference to a JSON-Schema entity). The GUI would show the JSON-Object and the JSON-Schema in a graphical way. If the JSON-Object has Entity references then the user can select them and the browser will show this referenced Entity.

@sureshms I agree, I am not a linked-data person myself and I am all in for a conceptual simple approach.
The only reason I am proposing doing something with SKOS is that it is an existing standard in which concepts are defined in some organizations.
We do not need to support the full Linked-Data machinery. Translating SKOS to our own JSON-Schema based tagging approach is sufficient. End-users will never see RDF.
We should think of a thesaurus as simply a collection of tags.
A business glossary is just a thesaurus.

This sounds great.

An elegant solution would be to extend the current OpenMetadata tagging implementation with tags of the form thesaurus:concept. When users click the tag they see the definition of this tag and the entities tagged with it.
We could also use the name glossary instead of thesaurus to make it a bit less formal?

Naming it as glossary would make it less formal and more accessible to our users. 👍

A simple one is REST-services which are implemented by teams in the organization. These entities should at least have info about the endpoints and an optional swagger URL. I can create an issue for this?

You are suggesting API endpoints available as entities that are discoverable. Correct? How about modeling this as a service with service has an API endpoint? We already have many services (database, messaging, dashboard etc.). This could be a type of service (not sure what a good name is - microservice, API service...). What do you think?

A more complex problem is documenting the relation between datasets (or entities in general). I think it's fantastic that OpenMetadata uses graphs of JSON-schemas. That's why it is conceptual superior to other solutions and it allows us to extend the system in an elegant way.

Relationships can definitely have tags as you are proposing in this for conceptual binding. What do you think? They can be class level properties (JSON schema for entity X to Json schema for entity Y) and not instance level properties.

Regarding models, I think it would be better if the current Model would be named ML-Model because there are a lot of models and this is confusing. Adding a generic JSON-Model entity would allow users of OpenMetaData to extend the system with new types of entities (simple by tagging the JSON-Model entity) without writing lots of code. I underestimated the amount of code needed to add my concept Thesaurus entity. If we add a JSON-schema visualization (#1011) OpenMetadata would be an even better environment to work with Metadata.

Model is already named as MLModel. It would be great to discuss the details of JSON-Model entities and how it will work. One thing I worry about is, opening up adding new types and entities can result in poorly designed/documented types created leading to duplicate and inconsistent types. This will run against the spirit of standardization and make tool interoperability harder. My initial thought was, let's work in the community and design all the entities. Then let's add extension points to existing entities. And as we learn more about how users are using the system, let's explore allowing adding entities/types programmatically. Thoughts?

Then let's add extension points to existing entities

@sureshms @harshach Yes, the option to extend existing entities without touching the Java codebase (or with just minimal additions) would be great.
Suppose we would like to extend eg the current table Entity with some additional GUI elements (eg buttons which links to URIs or even a visual presentation of the sample data records). I wonder if the React GUI could be passed the Entity JSON and the sample-data (or just the API-URLs to retrieve these) and if we could define extension Javascript code based on assigned tags. Each tag could have an optional Javascript extension script. For security reasons only a certain class of users would be allowed to add these extensions.
I have no React experience, but I assume it should be possible to add Javascript hooks which execute when a GUI element is shown.

It would be great to discuss the details of JSON-Model entities and how it will work

@sureshms @harshach I noticed https://github.com/open-metadata/OpenMetadata/issues/1159
This Model could be used as a JSON-Model?
What is missing? The GUI which shows the JSON? The option to tag the Model as a JSON-Schema Entity or as a instance of a model with an EntityRef to the schema?

You are suggesting API endpoints available as entities that are discoverable. Correct? How about modeling this as a service with service has an API endpoint? We already have many services (database, messaging, dashboard etc.). This could be a type of service (not sure what a good name is - microservice, API service...). What do you think?

@sureshms Sounds good, API (service) would be a good name?

@tomtor sorry for delay in response. #1159 is adding DBT model as model. Let me know if we should rename it.

#1159 is adding DBT model as model. Let me know if we should rename it.

@harshach Name Model is fine is we could use it to extend to various models.
The model is currently stored in a string, that is a nice generic type. How will it be visualized in the GUI?
If we can have a default visualization then we could extend the visualization based on TAGS and/or an added model-type attribute? I could then also use it to implement Glossary/Thesaurus instead of the current draft PR https://github.com/open-metadata/OpenMetadata/pull/1087

Name Model is fine is we could use it to extend to various models.

@harshach I now see that Model is already quite specific with database field handling, so it is not really suited as a generic Model. So perhaps a better name is SchemaModel or just Schema?

Closing this issue


sync upstream main branch to downstream

Sync the upstream changes from csi-addons/kubernetes-csi-addons:main into the
main branch. The most important recent changes that we want included are:

functional sidecar container-image
vendored tools for building components
ability to build a bundle container-image

Hmm, not sure why there are conflicts... Will need to resolve them manually :disappointed:

Closing in favour of #4


Error reducing memory overcommitment from Sunstone

Description
When reducing the memory overcommitment from Sunstone, the RESERVED_MEM attribute is not sending a correct value. Also, if memory overcommitment is not modified and click on update, Suntone is sending RESERVED_MEM empty causing the overcommitment is reset to the actual host memory.
To Reproduce
Reduce the memory overcommitent in Sunstone, note that the memory overcommitment value is not correct. Then click on update again without modifying the memory overcommitment value, note that the memory overcommitment is reset to the actual host memory.
Expected behavior
When reducing the memory overcommitment in Sunstone the RESERVED_MEM must be set with the actual target value. When clicking on update without modifying the memory value, the current configured value should be set in RESERVED_MEM.
Details

Affected Component: Sunstone
Version: 5.12

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Code: https://github.com/OpenNebula/one-ee/pull/460


TransparentClientHandler doesn't use CertificateManager.RootCertificate for AuthenticateAsServerAsync

A genuine certificate can be set to ProxyServer.CertificateManager.RootCertificate and this should be used rather than creating a certificate on the fly.
-                            var certificate = await CertificateManager.CreateCertificateAsync(certName);
+                           var certificate = CertificateManager.RootCertificate ?? await CertificateManager.CreateCertificateAsync(certName);

For security reasons, root certificate should never be used as a certificate for any hostname.
If you want to use a single certificate for all requests,  use any generic certificate as shown below in latest beta release.
explicitEndPoint = new ExplicitProxyEndPoint(IPAddress.Any, 8000)
{
 GenericCertificate = new X509Certificate2(Path.Combine(System.IO.Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().Location), "genericcert.pfx"), "password")
};

good point thanks


[Speeding up] Improvements of checkpoints and beyond

We've implemented hardcoded checkpoints to save some processing time on old blocks.
However, there is still some space for further improvements. Currently, we are aware of these:

POS StakeModifier (v1) is not used anymore for V3 blocks (which is place for quite a long time already, so latest checkpoints are V3). However, we still spend a lot of CPU and I/O time on calculating this v1 StakeModifier. We think we can remove this completely, which will speed up validation time on blocks after last checkpoint.

AcceptBlock method in ConsensusLoop contains this line:

                context.Flags = this.NodeDeployments.GetFlags(context.BlockResult.ChainedBlock);

It seems that it takes quite a lot of time to execute this line and the question is if that time could be saved for historic blocks - i.e. before last checkpoint. If so, this could save significant amount of time during IBD with checkpoints enabled.

Transactions and blocks are still validated even for historic blocks. This consumes a lot of CPU especially on mainnets. If we could skip validations, we could gain extremely fast syncing times.

@dangershony wants to remove V2 modifier from checkpoint and compute it always as it is negligible once we remove V1 completely

 [Speeding up] Improvements of checkpoints and beyond

will be done as a part of #494

 [Speeding up] 3 Improvements of checkpoints and beyond


Ensuring positive definite covariance matrix in tensorflow

Hi all,
I have the problem how to ensure psd property of covariance matrix in tensorflow. so I map the rnn outputs to the $\mu$ and $\Sigma$ of a MVN. So here I have to make the covariance psd, I tried to use matrix exponential, but it is not implemented in tensorflow, and I tried SVD, but then my loss function is not differentiable. So I tried to use $LL^{T} + \alpha |$, but still the program has bugs that the Sigma matrix is not invertible. Any suggestions for this problem? Thanks in advance!
def get_lossfunc(mu, Sigma,input_data):
    loss = 0
    for i in range(len(mu)):
        muC = tf.squeeze(mu[i])
        SigmaC = Sigma[i]
        inputC = input_data[i]
        SigmaC = tf.matmul(SigmaC, tf.transpose(SigmaC)) + tf.eye(10)
#         s,u,v = tf.svd(Sigma[0])
#         SigmaC = tf.matmul(tf.matmul(u,tf.diag(tf.exp(s))),v)
        dist = tf.contrib.distributions.MultivariateNormalFull(muC, SigmaC)
        loss += -tf.log(dist.pdf(inputC))
#         print loss
    return loss

This might be better suitable for stackoverflow, there are tricks to make sure your matrices are invertible (adding C*I to matrix)

@yaroslavvb , I already used "tf.matmul(SigmaC, tf.transpose(SigmaC)) + tf.eye(10)", but there is still bug that the matrix is inconvertible.

Try adding a multiple of TF.eye, if it's big enough, the inverse exists
On Mar 29, 2017 3:45 PM, "KKKL"<EMAIL_ADDRESS>wrote:

@yaroslavvb https://github.com/yaroslavvb , I already used
"tf.matmul(SigmaC, tf.transpose(SigmaC)) + tf.eye(10)", but there is still
bug that the matrix is inconvertible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/8799#issuecomment-290248881,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABaHAcusTNKDo33hbO3P_OxSNKAktOrks5rqt7xgaJpZM4Msykq
.


Twitch Name Change: Need Change on Plugin

Hello! I recently changed my name from Rs_Slushiiii to slushiiiibtw on Twitch. Can you please change it so that my RSN's: Slushiiii,  Prewerkout, Ratification, and Hcim To Zuk are no longer under twitch.tv/rs_slushiiii, but rather twitch.tv/slushiiiibtw? If you need any video proof it's on my channel. Thanks!

Hey there, I just became a maintainer of this plugin. I'm going through the backlog of requests and should get yours processed today. I'll close this ticket when I've submitted to plugin-hub. Thanks for being so patient!


Added an example for 'ShowCreationThenFadeOut'

Overview: What does this pull request change?

Motivation and Explanation: Why and how do your changes improve the library?

Links to added or changed documentation pages

https://manimce--2457.org.readthedocs.build/en/2457/reference/manim.animation.indication.ShowCreationThenFadeOut.html
Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

Thank you for your efforts with the PR!
Although, since this animation is fairly simple (just Creating and FadingOut), I think it might be better to simply deprecate it as the comments just above it suggest. See the following link in the docs for how to properly deprecate a class: deprecate

Do you mean like this?
@deprecated(message="use create and fade-out separately")
class ShowCreationThenFadeOut(Succession):

https://deprecation.readthedocs.io/en/latest/
according to this, we should include import deprecation as well


Implement Forge Data Decoder

Follow up to #555, this PR implements a forge data decoder.

Hey @CoolCat467, can I mark it as "up for grabs"?

Yea, sure thing. To be honest I sort of forgot about this, but I feel like it was in a pretty good state.

If there were a review with most recent changes I could look into trying to get this taken care of

I will review this soon. Can you also look at open conversations?

Also, would be great if someone checked those byte manipulations, I am getting really confused when anything touches bytes.

There's a pending request from me to use the connection classes for these, since a lot of it is just the same code but written as if none if those abstractions were available, we have them in mcstatus though, so we should use them.

Also, would be great if someone checked those byte manipulations, I am getting really confused when anything touches bytes.

There's a pending request from me to use the connection classes for these, since a lot of it is just the same code but written as if none if those abstractions were available, we have them in mcstatus though, so we should use them.
There was some work in the form of adding StringBuffer class, but it doesn't seem to actually be used anywhere, instead the old code, reading the bytes manually is still present. I therefore assume this is still WIP, but in case it was forgotten/lost in the sea of all of the conversations here, I'm bringing it up again. Until that gets addressed, I won't review again, as it will likely change a fair few things about the code that reads the raw data.

I definitely at least started trying to work on StringBuffer, but I think I hit a wall. I'll look into that again later, but I think it might have to come to just adding more read methods to it. I don't think the encoded format is very similar to any of the existing formats Connections can read, but again I'll look into it.

@ItsDrake as of 740503f, finished StringBuffer reading

Can I mark it as "up for grabs"?

I thought this was done a long time ago, kind of forgot it was still open.

Oh, have we changed the test system? Everything was working earlier. If I could get help converting to whatever the new system is that would be great.

So could you answer open conversations? As far as I can remember, it's almost ready for merge, except for those two things.

I think it would be easier if I will just commit those changes, that I proposed in review. Of course if you don't mind

I think it would be easier if I will just commit those changes, that I proposed in review. Of course if you don't mind

Sure thing, I would like to see these changes merged in one way or another so I don't need to maintain my own module to do it because of lack of support.


Possible to make URL's case-insensitive?

A report from a viewer on youtube:
'FYI: Some of the links in the description are truncated - and have been for past videos as well.
Learn more on the TTT site: https://developers.google.com/web/shows/ttt/
Subscribe by email: https://feedburner.google.com/fb/a/mailverify?uri=TotallyToolingTips&loc=en_US
RSS feed: https://developers.google.com/web/shows/ttt/feed.xml
The paths are also unfortunately case-sensitive, so 'TTT' 404s.'

No - unfortunately DevSite is case sensitive. We'll need figure out how to fix this.


A mangled name appears in bindings when vertex type is imported

Minimal repro:
clear.wgsl:
#import vertices::VertexIn

struct VertexOutput {
    @builtin(position) position: vec4<f32>,
}

@vertex
fn vertex_main(input: VertexIn) -> VertexOutput {
    var output: VertexOutput;
    output.position = input.position;
    return output;
}

@fragment
fn fragment_main(input: VertexOutput) -> @location(0) vec4<f32> {
    return vec4(1.0, 1.0, 1.0, 1.0);
}

vertices.wgsl:
struct VertexIn {
    @location(0) position: vec4<f32>,
}

build.rs
WgslBindgenOptionBuilder::default()
        .workspace_root("shaders")
        .add_entry_point("shaders/clear.wgsl")
        .skip_hash_check(true)
        .serialization_strategy(WgslTypeSerializeStrategy::Bytemuck)
        .type_map(GlamWgslTypeMap)
        .short_constructor(2)
        .shader_source_type(WgslShaderSourceType::UseComposerEmbed)
        .derive_serde(false)
        .output("src/new_render/pipelines/bindgen.rs")
        .build()?
        .generate()
        .into_diagnostic()?;

The generated code for vertex buffer layout references a type NewPosColVertexX_naga_oil_mod_XOZSXE5DJMNSXGX, which does not exist in rust. My guess is that naga_oil starts mangling types when they are imported and so the assumption that the name in rust will be the same as it is in the composed shader module is violated.

There was a mistake in the example, sorry. vec3 in VertexIn should actually be vec4

I'll try to have a look at this weekend, at both updating wgpu and this issue.

Fixed in https://crates.io/crates/wgsl_bindgen/0.14.1
Thanks for reporting.


The debugger cannot be run

1.71  debugger cannot be run；

/needsMoreInfo

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

similar here https://github.com/microsoft/vscode/issues/159881

@onemanshea what debugger?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[SEC] update argocd dependencies

Codecov Report

Merging #321 (f9f3fc2) into main (bc4daf6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #321   +/-   ##
=======================================
  Coverage   60.44%   60.44%
=======================================
  Files          17       17
  Lines        3036     3036
=======================================
  Hits         1835     1835
  Misses       1101     1101
  Partials      100      100

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Joining request

Hey!
I want to join this organization to improve my logic and programming skills in Python. And since this project is open source, my contributions and knowledge will also be visible on my profile.

Hey there @Daksh777 , welcome to PatternHouse! I have sent the invite to join, do make your membership public so that the organization badge is visible on your profile.

Thank you so much!


Relationship Extraction node - does it work ?

Can't seem to get the Relationship Extraction node to work - can someone supply some simple test to confirm it is working ?

I'll look into this for you.

Okay, so the Relationship Extraction service used to return XML and now returns JSON by default. This has broken the node. It's a simple fix, so I'll push out a change shortly.

Can it be told what to return ? So it can be fixed in case they change it again?


@fepre This still an issue with Pandas Profiling version 2.10.0.

@fepre This still an issue with Pandas Profiling version 2.10.0.
import numpy as np import pandas_profiling df = pd.DataFrame(     np.random.rand(100, 5),     columns=["a", "b", "c", "d", "e"] ) pandas_profiling.ProfileReport(df)
Originally posted by @JamesMDorame in https://github.com/pandas-profiling/pandas-profiling/issues/496#issuecomment-769953226

Duplicate of #685


docs: improve CONTRIBUTING docs

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
Improve CONTRIBUTING docs

Define format of the embedded script
Add embedded script for 'git config'
Improve case for 'github'

Ⅱ. Does this pull request fix one issue?
NO, just improve docs.
Ⅲ. Why don't you add test cases (unit test/integration test)?
Unnecessary for docs.
Ⅳ. Describe how to verify it
See the change via any markdown reader
Ⅴ. Special notes for reviews

Codecov Report

Merging #4163 (934131f) into develop (2639ec8) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #4163      +/-   ##
=============================================
- Coverage      49.76%   49.67%   -0.09%
+ Complexity      3768     3767       -1
=============================================
  Files            700      700
  Lines          23624    23596      -28
  Branches        2917     2866      -51
=============================================
- Hits           11756    11721      -35
+ Misses         10669    10657      -12
- Partials        1199     1218      +19

Impacted Files
Coverage Δ

...obuf/convertor/BranchRegisterRequestConvertor.java
90.47% <0.00%> (-9.53%)
:arrow_down:

...otobuf/convertor/BranchReportRequestConvertor.java
90.90% <0.00%> (-9.10%)
:arrow_down:

...obuf/convertor/BranchRollbackRequestConvertor.java
92.00% <0.00%> (-8.00%)
:arrow_down:

...otobuf/convertor/GlobalBeginResponseConvertor.java
92.59% <0.00%> (-7.41%)
:arrow_down:

...otobuf/convertor/GlobalCommitRequestConvertor.java
93.75% <0.00%> (-6.25%)
:arrow_down:

...otobuf/convertor/GlobalStatusRequestConvertor.java
93.75% <0.00%> (-6.25%)
:arrow_down:

...obuf/convertor/GlobalRollbackRequestConvertor.java
93.75% <0.00%> (-6.25%)
:arrow_down:

...protobuf/convertor/RegisterTMRequestConvertor.java
94.73% <0.00%> (-5.27%)
:arrow_down:

...protobuf/convertor/RegisterRMRequestConvertor.java
90.47% <0.00%> (-4.77%)
:arrow_down:

...tobuf/convertor/BranchReportResponseConvertor.java
95.45% <0.00%> (-4.55%)
:arrow_down:

... and 28 more


Issue with Genome Editing Metadata

@yuliujpl There seems to be an issue with some of the Genome Editing Metadata. I just noticed and haven't checked any other collections or datasets.
When i drilled down to this virtual dataset
https://labcas.jpl.nasa.gov/nist/cd/index.html
it is showing the Flow Cytometry old metadata (see screenshot):

Other virtual datasets look like they contain the correct collection, but all of the metadata is the older version and needs to be updated to the new Version 1. Do you want me to create a new issue just for that? Any of the collection and file metadata updates should carry throughout the system. I can map that out if it would be helpful :) I completely forgot about this level.

I'm looking into it, I suspect that the virtual hierarchy view needs to be updated!

@yuliujpl let me know if you want me to provide you with screenshots of the metadata updates. :)

Changed! Here is the mapping I used! virtual_hierarchy_dataset_displayfields_keys is the actual keys in solr, and virtual_hierarchy_dataset_displayfields_labels is the change in display labels I map to!
"virtual_hierarchy_dataset_displayfields_keys":"DatasetDescription,WorkingGroupDesignation,LeadPoC,LeadPoCEmail,OwnerPrincipal,ProtocolHandle,SourceID,ParentCellLine,MammalianCellCode,InstrumentHandle,ExpansionType,StudyType,DataCustodian,DataCustodianName,DataCustodianEmail,BlindedDataset,AssayType,CoreCapabilities,PrimaryFocusAreas",
"virtual_hierarchy_dataset_displayfields_labels":"Dataset Description,Working Group Designation,Principal Contact Name,Principal Contact Email,Owner Principal,Protocol Handle,Source ID,Parent Cell Line,Mammalian Cell Code,Instrument Handle,Expansion Type,Data Category,Data Custodian Name,Data Custodian Name,Data Custodian Email,Blinded Dataset,Assay Type,Core Capabilities,Primary Focus Areas",

@yuliujpl I'm closing this issue, but have created another issue to ensure all CollectionLevel metadata is displayed and updated for all Collections showing the same set of metadata now that we have a standard :) #145


Find kokkos module

@masterleinad Would you review this please?

Sure.

@aprokop I removed our patching Kokkos from the Dockerfile but I did not bother rebuilding.  I don't think it is necessary.

I didn't test this, though.

Merge?

@dalg24 With this merged PR, what's our minimum CMake version?

@dalg24 With this merged PR, what's our minimum CMake version?

I suspect 3.10 works


New package: Yubico.YubiKeySmartCardMinidriver version <IP_ADDRESS>

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

This package merely installs a driver, therefore the Validation-No-Executables label is expected behavior.

[Policy] Needs Attention

@wingetbot waivers Add Validation-Domain

@wingetbot waivers Add Validation-No-Executables

/AzurePipelines run

/AzurePipelines run

/AzurePipelines run


[ISSUE #4381] Fix missing HOST header delete operation

FIX #4381 missing HOST header delete operation

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #4425 (22c09e4) into master (1278156) will decrease coverage by 0.15%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #4425      +/-   ##
============================================
- Coverage     68.09%   67.94%   -0.15%
- Complexity     7483     7492       +9
============================================
  Files          1021     1023       +2
  Lines         28913    29006      +93
  Branches       2584     2589       +5
============================================
+ Hits          19688    19709      +21
- Misses         7681     7744      +63
- Partials       1544     1553       +9

Impacted Files
Coverage Δ

...yu/plugin/httpclient/AbstractHttpClientPlugin.java
40.84% <100.00%> (+0.84%)
:arrow_up:

...pache/shenyu/plugin/cryptor/utils/CryptorUtil.java
13.04% <0.00%> (-22.45%)
:arrow_down:

...he/shenyu/loadbalancer/spi/RandomLoadBalancer.java
81.81% <0.00%> (-9.10%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
21.27% <0.00%> (-6.39%)
:arrow_down:

...java/org/apache/shenyu/common/utils/UUIDUtils.java
75.00% <0.00%> (-6.25%)
:arrow_down:

...rg/apache/shenyu/plugin/rewrite/RewritePlugin.java
66.66% <0.00%> (-5.56%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
52.12% <0.00%> (-4.26%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
85.71% <0.00%> (-4.09%)
:arrow_down:

...in/response/strategy/NettyClientMessageWriter.java
71.42% <0.00%> (-3.58%)
:arrow_down:

.../org/apache/shenyu/common/config/ShenyuConfig.java
68.89% <0.00%> (-1.97%)
:arrow_down:

... and 13 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Corrected link for SymPy project

Updated the link for SymPy from the old Google Code page

Thanks @cjmgit, merged.


Creating base workspace is not working on a new TRE environment

When creating a new TRE environment from scratch by make all, and trying to deploy a base workspace to it, it fails.

First, it fails with an API error:

However, if you manage to skip this validation step, this will occur once you deploy the workspace base template:

This is the issue with the unit test that got through, let me find the line in PR that fixes it.

@anatbal this is the fix:
https://github.com/microsoft/AzureTRE/blob/e3578a02e19a74310f28e99491681855510f13ac/api_app/db/repositories/workspaces.py#L70-L73

@marrobi
Also, I noticed that if I manage to have a ws already in the cosmosdb, creating a second, different workspace is also failing.  I am just not sure if it is related to this or perhaps a different thing

I think it's likely the same issue, the v0.7.0 will fail.

@LizaShak might be trying to do a quick fix just on this issue.


Start never ends on node.js 15.x || ^14.6

Never resolves await application.init();
Even no message:
09:10:50  W1   system   Application started in worker 1

Partially fixed in metavm v0.2.0 but just for preventEscape: false (default)


Fix /some/ new clippy warnings

Okay, enough CI ping-pong for today. This is as far as I want to go for now. Good night.

This PR now adds something more than just "mechanically apply clippy suggestions": https://github.com/psychon/x11rb/pull/757/commits/71fd6c747dd6478c64a81266f0837794dc443389 makes x11rb::image::Image derive Clone. This then causes
error[E0119]: conflicting implementations of trait `std::borrow::ToOwned` for type `image::Image<'_>`
   --> x11rb/src/image.rs:513:1
    |
513 | impl<'a> ToOwned for Image<'a> {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: conflicting implementation in crate `alloc`:
            - impl<T> std::borrow::ToOwned for T
              where T: std::clone::Clone;

Oh, hey, a blanket implementation! Let's just use that.
(Note: This is actually a behaviour change because previously to_owned() would copy the underlying data. However, it was not possible to express this in the type system and thus the borrow checker still kept the original borrow. The new code now actually does exactly that, which I think should be fine.)

....aaaand this now also bumps the MSRV to 1.56 to fix #756

Thanks!
I'll now take a look at the VecDeque binary search thing...


Friendly URLS

Are friendly urls working? I can't seem to make them work. I can only access pages like index.php?r=post%2Fview&id=3
//fixed

`'urlManager' => [
'class' => 'yii\web\UrlManager',
// Disable index.php
'showScriptName' => false,
// Disable r= routes
'enablePrettyUrl' => true,
],
Put this in frontend/config/main.php   inside component
Add .htaccess file in your web folder
`RewriteEngine on
If a directory or a file exists, use it directly
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
Otherwise forward it to index.php
RewriteRule . index.php
That should work.