fix: disable analyzers for Samples

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

Part of #8944

You can test this PR using the following package version. 11.0.999-cibuild0026836-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-nightly/nuget/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0026878-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-nightly/nuget/v3/index.json) [PRBUILDID]


Version 3.0.1: ImportError: No module named fcntl

Hi I got trouble with installing new version (3.0.1) on Windows:
In my case progressbar2 installed as a dependency of django-stdimage.
Console output:
Collecting progressbar2>=2.7 (from django-stdimage==1.2.2->-r requirements\base.txt (line 22))
  Using cached progressbar2-3.0.1.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "c:\users\jenssd~1\appdata\local\temp\pip-build-rnf6vf\progressbar2\setup.py", line 6, in <module>
        from progressbar import metadata
      File "progressbar\__init__.py", line 64, in <module>
        from .bar import ProgressBar
      File "progressbar\bar.py", line 5, in <module>
        import fcntl
    ImportError: No module named fcntl

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in c:\users\jenssd~1\appdata\local\temp\pip-build-rnf6vf\progressbar2

Hmm, that's a serious issue. Apparently fcntl is not supported by Windows (hard to test for me unfortunately), I'll get out a fix today :)

This should be fixed by the new release (3.1.0), please give it a try and let me know if you have any issues :)

Yes this version works fine. Thank you!


[State Sync] Separate unit and integration tests.

Motivation
Note: no logic changes in this PR. 😄
This PR simply separates the unit from integration tests in the state sync folder. Providing better test separation will help to identify missing tests and offer a cleaner layout and structure.
The PR offers the following commits:

Clean up the cargo.toml file.
Move the request manager unit tests to the request manager file and out of "src/tests".
Move the executor proxy unit tests to the executor proxy file and out of "src/tests".
Move the fuzzer out of the src/tests directory and into the coordinator file. Moreover, move "src/tests" into "tests" to make them follow the rust style integration tests.

We'll follow this PR with a renaming PR that makes naming consistent and avoids having to make imports like "use state_synchronization::state_synchronization::StateSyncClient".
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
All tests pass locally.
Related PRs
None, but this relates to: https://github.com/diem/diem/issues/6795

Thanks @gregnazario! 😄
/land

Thanks @gregnazario! 😄
/land


Add support for host port and no advertise

Adds support for host port to be able to bind a nats server to an external ip, plus support for disabling advertising the internal ips to clients that connect externally.
apiVersion: "nats.io/v1alpha2"
kind: "NatsCluster"
metadata:
  name: "example-nats-1"
spec:
  size: 3
  version: "1.4.0"
  noAdvertise: true
  pod:
    enableClientsHostPort: true

LGTM.


databasez 0.8 compatibility

Changes:

fix compatibility with databasez >=0.8
some small test utility related fixes
fix pre-commit for python != 3.10

@devkral CI is breaking


Honor .sortedKeys (redux)

This PR supersedes #11, which had some unwanted commits added to it. It addresses the formatting issues mentioned by @MaxDesiatov.

Hi @MaxDesiatov: codecov/patch failed because the PR doesn't have tests for all the files that have been reformatted by SwiftFormat. 😄 But I believe it's ready to merge.
Once you do that, I'll suggest another PR that adds character data support for encoding and decoding.
Thanks!

LGTM, thanks!


[Android, question] Exceptions on commands

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[] iOS
[*] Android
[] tvOS
[] macOS
[] .NET Standard
UWP IS NOT SUPPORTED DURING THE BETA PERIOD - ONLY PRs ARE WELCOME FOR NOW

Version of OS(s) listed above with issue
Version of Library
Expected Behaviour
Actual Behavior
If applicable, please include entire exception - type, message, stacktrace
I am just wondering why some commands like this return NullReferenceException. I am caching exceptions, so its just fine.
Also, i saw that there is Retry extension, which does, just throw exception without doing much in next retries if first retry failed sometimes. I found out that resetting connection is the only thing that can help with that, this could be the reason why.
Normally i would be happy about timeout exception or connection not valid exception or could not get such service exception...
var ch = await device.DeviceObject.GetKnownCharacteristics(SERVICE, CHARACTERISTIC).Timeout(OperationTimeout);

12-03 10:12:58.271 W/art     (10769): JNI RegisterNativeMethods: attempt to register 0 native methods for md51558244f76c53b6aeda52c8a337f2c37.ActivityIndicatorRenderer
12-03 10:12:58.796 W/art     (10769): JNI RegisterNativeMethods: attempt to register 0 native methods for md58432a647068b097f9637064b8985a5e0.ViewRenderer_2
12-03 10:12:58.865 W/art     (10769): JNI RegisterNativeMethods: attempt to register 0 native methods for md58432a647068b097f9637064b8985a5e0.FrameRenderer
12-03 10:12:58.935 W/View    (10769): requestLayout() improperly called by md58432a647068b097f9637064b8985a5e0.NavigationPageRenderer{c9f1b7c V.E...... ......ID 0,0-2560,1528 #1} during second layout pass: posting in next frame
Thread started:  #7
12-03 10:12:59.178 W/art     (10769): JNI RegisterNativeMethods: attempt to register 0 native methods for md5e4c2749da5edf4a9690b7fedcbdb53f0.SKCanvasViewRendererBase_2
12-03 10:12:59.178 W/art     (10769): JNI RegisterNativeMethods: attempt to register 0 native methods for md5e4c2749da5edf4a9690b7fedcbdb53f0.SKCanvasViewRenderer
12-03 10:12:59.277 I/art     (10769): Starting a blocking GC Explicit
12-03 10:12:59.296 I/art     (10769): Explicit concurrent mark sweep GC freed 1733(307KB) AllocSpace objects, 0(0B) LOS objects, 39% free, 14MB/23MB, paused 208us total 18.213ms
12-03 10:12:59.365 W/art     (10769): JNI RegisterNativeMethods: attempt to register 0 native methods for md51558244f76c53b6aeda52c8a337f2c37.CellRenderer_RendererHolder
12-03 10:12:59.809 I/Choreographer(10769): Skipped 50 frames!  The application may be doing too much work on its main thread.
12-03 10:12:59.875 W/BluetoothGatt(10769): onCharacteristicRead() - Device=C3:32:D1:9C:CC:E8 handle=37 Status=0
12-03 10:13:00.175 W/BluetoothGatt(10769): onCharacteristicRead() - Device=C3:32:D1:9C:CC:E8 handle=52 Status=0
Thread started:  #8
12-03 10:13:00.260 I/art     (10769): Starting a blocking GC Explicit
12-03 10:13:00.295 I/art     (10769): Explicit concurrent mark sweep GC freed 11771(682KB) AllocSpace objects, 0(0B) LOS objects, 40% free, 15MB/26MB, paused 372us total 35.006ms
12-03 10:13:00.425 W/BluetoothGatt(10769): onCharacteristicRead() - Device=C3:32:D1:9C:CC:E8 handle=46 Status=0
[0:] Scheduler -> Update device:
12-03 10:13:00.926 W/BluetoothGatt(10769): onCharacteristicRead() - Device=CE:30:44:24:35:0F handle=37 Status=5
12-03 10:13:02.079 W/BluetoothGatt(10769): onCharacteristicRead() - Device=CE:30:44:24:35:0F handle=37 Status=0
Thread started:  #9
12-03 10:13:02.476 W/BluetoothGatt(10769): onCharacteristicRead() - Device=CE:30:44:24:35:0F handle=52 Status=0
[0:] System.NullReferenceException: Object reference not set to an instance of an object.
  at Plugin.BluetoothLE.Device.<DiscoverServices>b__16_0 (System.IObserver`1[T] ob) [0x00051] in C:\dev\acr\bluetoothle\Plugin.BluetoothLE\Platforms\Android\Device.cs:120
  at System.Reactive.AnonymousObservable`1[T].SubscribeCore (System.IObserver`1[T] observer) [0x00000] in <370f6a6bb34048878534065376a195cb>:0
  at System.Reactive.ObservableBase`1[T].Subscribe (System.IObserver`1[T] observer) [0x00037] in <370f6a6bb34048878534065376a195cb>:0
--- End of stack trace from previous location where exception was thrown ---
  at System.Reactive.PlatformServices.ExceptionServicesImpl.Rethrow (System.Exception exception) [0x00006] in <370f6a6bb34048878534065376a195cb>:0
  at System.Reactive.ExceptionHelpers.ThrowIfNotNull (System.Exception exception) [0x0000d] in <370f6a6bb34048878534065376a195cb>:0
  at System.Reactive.Subjects.AsyncSubject`1[T].GetResult () [0x00039] in <370f6a6bb34048878534065376a195cb>:0
  at NNNNNNNNNNNNNNNNNNNNNNN+<YYYYYYYYYYYYYYYYYYY>d__41.MoveNext () [0x00124] in XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\Services\Bluetooth\Bluetooth.cs:265
12-03 10:13:04.613 I/hwaps   (10769): JNI_OnLoad

Code of Conduct

No Library Update Requests
No Timeline Requests
Please read through the documentation and FAQs
If you have a complaint about the docs, FIX IT - DO NOT FILE IT HERE!  I won't guarantee everything is always 100% up-to-date since I am just 1 person.
Please be respectful of my time. I put a lot of effort into my libraries.  I try to support the issue requests within a day.  I'm not psychic, so please take the time to fill out the above form as complete as possible

The GATT object is null which would only happen if the device was disconnected.  The actual line number is there so you can review for yourself in the future.


Changes to build analyzer for PS7 and PS6 and ship in separate directories and bump version to 1.19.0

PR Summary
With changes in PS7 parser, rules will likely be created which will not even compile on PS6 (Ast changes). This changes our build to release assemblies for both PS6 and PS7. PS6 assemblie stays as netstandard assemblies, but the new assemblies target netcoreapp3.1.
Other changes include needed changes to sign and release via our build system (which had some breaking changes recently). Also add defines for PS7 and PS6 so new rules targeting PS7 may be more easily created.
Update to release version 1.19.0
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

but I would merge this PR only once we have a rule that needs it.

That's something of a chicken and egg problem. PSUseCompatibleSyntax could use this today, but doesn't have an ifdef to target currently. If it did, we could add visitor methods for new syntaxes that issue warnings for other versions

Ok, let me re-phrase it then: Do we want to get 1.19.0 out of the door in 1-2 weeks or 1-2 months? Because taking advantage of those new APIs will take some time. I'm up for either, just want to be sure we are all on the same page

Ok, let me re-phrase it then: Do we want to get 1.19.0 out of the door in 1-2 weeks or 1-2 months? Because taking advantage of those new APIs will take some time or do you guys plan to spend much more time on PSSA for those PRs since PS and the extension have shipped now? I'm up for either approach (fast releases or wait longer for just 1 release), just want to be sure we are all on the same page.

Could you expand on this some more? Which PRs are you referring to? Which changes do you mean will take advantage of the new APIs?
As far as I can think, the only rule that would easily take advantage of the new AST elements is the compatible syntax rule. Currently most of the rules just pick up the ASTs they're normally looking for, and they'll continue to do that when targeting PS7 APIs. Are there other rules you have in mind for changes?

OK, that sounds good if it is just your compatibility syntax rule, I thought the scope could've been bigger. Totally OK if you want to have this change as part of 1.19.0
In a few days, Azure Pipelines images are likely going to update PowerShell to 7.0 so testing is going to be interesting for 6.2 in the next months until it goes out of support in 6 months...
Will have a re-review around some of the build related changes. So far the only problem that I could spot is the issue that we also need conditions for the version of Microsoft.Management.Infrastructure.

@JamesWTruher @bergmeister this should be ready to go now, if you're able to sign off or let me know what else should be changed

Just a question for my own understanding/education: Jim said that one should use the Microsoft.PowerShell.SDK NuGet package and not the SMA one, why?

Ok I've now had a discussion with members of the PowerShell team on this one, and I think for our purposes, SMA is the right target for now. I'm hoping to write documentation of some kind to address this in the next week or so

Ok I've now had a discussion with members of the PowerShell team on this one, and I think for our purposes, SMA is the right target for now. I'm hoping to write documentation of some kind to address this in the next week or so

Interesting, thanks.
My simplistic understanding as a user is that SMA is to be used for when .net code is executed from within PowerShell itself as a reference assembly of SMA APIs since PowerShell itself already has all required assemblies. I'd use the SDK if the code was running as part of a 'normal' .net app that doesn't have the PowerShell dependencies like the SMA Dll and its other dependent assemblies so that a dotnet publish contains those DLLs and therefore ships a self-contained version of the PowerShell 'runtime' (also meaning that the author would be in charge of patching)

Basically the outcome of our discussion was:

Use SMA for just parsing, minimal hosting using SessionState.CreateDefault2() and only commands in the Microsoft.PowerShell.Core module, or when you need a reference assembly with version-specific APIs
Use the SDK for hosted scenarios where arbitrary commands or modules may be used or where code references are required to other Microsoft.PowerShell.* module types
Use PSStd for all reference (rather than hosted) scenarios where version-specific APIs are not required


Adding a pre-commit task that runs git-secrets.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Adds a pre-commit task that runs git-secrets.
I don't think this is a good idea, but I want to put it up here for feedback. I think I'd prefer that the developer guide instructs developers to install git-secrets manually, and configure it globally, as good hygiene. I can PR that instead under separate cover.
As this PR stands,
Pros:

Helps avoid accidentally committing secrets into the repo because developers run ./gradlew precommit.

Cons:

Requires installing of git-secrets from  https://github.com/awslabs/git-secrets. Would require updating CI bot.

Requires adding this task into every single plugin if we want this to be adopted generally.

Redundant with a global installation of git-secrets which can be done as follows (on a mac), just once:
brew install git-secrets
git secrets --register-aws --global
git secrets --install ~/.git-templates/git-secrets
git config --global init.templateDir ~/.git-templates/git-secrets

Why not check in PRs?
Because GitHub secret scanning is automatically enabled on public repositories, so by the time a PR is created the compromized account owner has been notified and the account disabled.
Why not a server-side pre-commit hook?
It's available in GitHub Enterprise Server, but isn't available on github.com.
Issues Resolved
N/A
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[x] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

start dco check
start wrapper validation
start gradle precommit

start gradle precommit

I propose we close this without moving forward/merging, @CEHENKLE?

Hey @dblock!  Here's where I am on this:
I hate relying on good intentions for something like this.  If we're talking personal preference in set up, then yeah, absolutely put a note in the guide and TMTOWTDI!  But keeping secrets out of the repo seems like something we should make a best effort to help people from making mistakes.
But that being said, I hear what you're saying -- we haven't found a good way to do it.  How do other repos handle this situation?   If the answer comes back "they call it out in their developer guide, but that's it", well, then c'est la guerre.
Thanks,
/C

I don't think other repos do much different. If you push a secret to Github it gets flagged immediately and account is rotated by the providers, such as AWS. Having done it once or twice I now setup git-secrets globally :) i'm going to close this.


More TAB, similar to the browser tabs, each TAB when a separate form

http://www.builive.com/apps/default/main.html#menu/main-menu

Hi @smile2014! Thanks for proposal, but we don't have time for realisation this functionality.


fix MultipartUpload test

For UFile: The size of all parts except the last part cannot be less than 4MB, otherwise calling the FinishMultipartUpload API will fail.
ref #3272

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.04 :tada:

Comparison is base (caefb53) 55.61% compared to head (6cb31e5) 55.66%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3298      +/-   ##
==========================================
+ Coverage   55.61%   55.66%   +0.04%
==========================================
  Files         142      142
  Lines       33825    33825
==========================================
+ Hits        18812    18828      +16
+ Misses      13019    13006      -13
+ Partials     1994     1991       -3

Impacted Files
Coverage Δ

cmd/sync.go
50.34% <100.00%> (ø)

pkg/meta/redis.go
66.75% <0.00%> (+0.03%)
:arrow_up:

pkg/chunk/cached_store.go
73.10% <0.00%> (+0.14%)
:arrow_up:

pkg/chunk/disk_cache.go
73.54% <0.00%> (+0.29%)
:arrow_up:

pkg/vfs/reader.go
79.90% <0.00%> (+0.63%)
:arrow_up:

pkg/vfs/handle.go
84.32% <0.00%> (+0.74%)
:arrow_up:

pkg/vfs/writer.go
78.65% <0.00%> (+1.16%)
:arrow_up:

pkg/fuse/context.go
73.17% <0.00%> (+7.31%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Can we make sure that sync use correct part size for UFile?


Fullcalendar3.9.0 upgrade

@kpakur this is the same as #90 with conflicts solved and deprecated types removed
@Jamaks what do you think?

@antoinepairet thanks! I will test your mr

Build failed. See below for errors.

TypeError: args.indexOf is not a function

@antoinepairet  Merge from master latest version and pull request again please

Looking forward to 3.9.0 being merged to the master. Also please consider supporting themeStyle

check it out https://github.com/Jamaks/ng-fullcalendar/pull/144


Change docs url to subdomain

Codecov Report

Merging #67 (7d76bbd) into main (62b6e3f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #67   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          736       736
=========================================
  Hits           736       736

Continue to review full report at Codecov.

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


Import reverse from django.urls, not django.core

https://stackoverflow.com/a/43139407

Already included in https://github.com/brutasse/django-rq-dashboard/pull/20


pypyjs / PyPyJS / PyPy-JS / PyPy.js ...

I know, a kind of a nonsense question...
What's the "official" spelling ???
Every time I write pypy, i have to think about the right spelling ;)

This actually seems like an important question. And there's a related question, in my mind, about the naming conflict between the project overall and the "pypy.js" library it contains... which seems incidental the file that's the point of the project overall, which is "pypy-vm.js"?
As this project continues to evolve (see what I did there?) someone ought to choose these names deliberately!

The github org name is pypyjs -> https://github.com/pypyjs/
The main repro called pypyjs -> https://github.com/pypyjs/pypyjs/
So what's about to rename all variants to pypyjs ?
On the other side: this low-case variant will be not good noticed in normal continuous text...

All the repository descriptions (and the organization description) use PyPy.js.

I played around with a few variants when naming things originally and I think I prefer "PyPy.js" as the canonical name for the project.  But I'm open to arguments that it should be something else :-)
Perhaps we can standardize on "PyPy.js" when appearing in text, and "pypyjs" as the name of things in code contexts where dots are not welcome?

And there's a related question about the naming conflict between the project overall and
the "pypy.js" library it contains

@crantila I'd like to hear more about this.  I agree that the vm.js file is the real heart of the project, but the pypy.js file is the entry-point that you actually load in order to use things.

Perhaps we can standardize on "PyPy.js" when appearing in text, and "pypyjs" as the name of things in code contexts where dots are not welcome?

+1

Regarding the naming conflict I mentioned above, it first occurred to me while explaining PyPy.js to collaborators on my project. (We've yet to contribute to PyPy.js directly, but it will happen!) The confusion arises because there seem to be three things called PyPy.js: the project, the JavaScript library, and the interpreter.
The problem is most noticeable when someone's first trying to wrap their head around the nature of running Python in JavaScript. People want to understand who does what, where, and why. Saying "this happens in PyPy.js" is ambiuguous in many cases. Depending on what's being explained at the moment it can either mean "this happens in PyPy.js the JavaScript library instead of the interpreter," or "this happens in PyPy.js the interpreter instead of the JavaScript interpreter," or even other things.
To some extent, newcomers may simply be confused about what's going on because it's different and new. Yet we (PyPy.js contributors) can alleviate this confusion by communicating as clearly as possible. The most obvious solution is to provide additional clarification in documentation whenever "PyPy.js" might be ambiguous, but I feel this may prove to be unnecessarily difficult over time. A simpler, one-time solution would rename something to avoid troublesome ambiguity altogether.
My suggestion is therefore to rename pypy.js, the JavaScript file that is the entry-point to the PyPy.js interpreter, to pypy-bridge.js. I've already started calling this file "the JavaScript bridge" because the metaphor of bridging between Python-land and JavaScript-land is quite helpful. The remaining ambiguity between PyPy.js as a project and PyPy.js the interpreter seems unlikely to cause troublesome ambiguity.
What does everyone think? There may be even better solutions out there!

My 2ct:
PyPy.js as project name:

pro:

looks nice
described the project IMHO very good

con:

looks like a filename
can't be used in sources, because of the dot and case sensitive

pypyjs as the name for everything:

pro:

can be used consistently, everywhere
github group and git repro use it already
all low case

con:

Looks not so nice than "PyPy.js"

About renaming pypy.js:
What's about to rename it to pypyjs-init.js ?
I think bridge doesn't match it completely.
btw. we have three important files...
From the https://github.com/pypyjs/pypyjs-release/blob/master/lib/README.txt :

pypy.js:         public-facing API to the PyPy VM
pypy.vm.js:      the PyPy VM itself, as built by rpython+emscripten
pypy.vm.js.mem:  memory initializer data for the PyPy VM

So what's renaming all three (If pypy.js will be renamed) ?
e.g.:

pypyjs-init.js
pypyjs-vm.js
pypyjs-mem.dat

The file extension .dat is a other question, see: https://github.com/pypyjs/pypyjs.github.io/issues/4

@crantila thanks for expanding on that, I see you points.  There's also some additional weirdness around the naming of the release bundles, their directory structure, etc.  @jedie, your list of pros and cons closely matches my own :-)
Would it be too much repetition of "js" if we were to name files like this?
  pypyjs.js
  pypyjs.vm.js
  pypyjs.vm.js.mem

I think that would be a big improvement, but perhaps still not as clear as marking the JavaScript file with "init" or "bridge" or similar.

...marking the JavaScript file with "init" or "bridge" or similar.

:+1:

marking the JavaScript file with "init" or "bridge" or similar.

I gotta be honest, I vaguely dislike this but I can't articulate the reasons why.  Perhaps I just need to sleep on it :-)
Would calling the helper file something other than "vm" help to clear things up?

any news here?

Sorry, I'm travelling for work at the moment so trying to stay on top of these issues in-between meetings etc.  I think I still like the scheme from https://github.com/pypyjs/pypyjs/issues/147#issuecomment-114548127 the best of all the options considered, will try it out for the next release.
Do you think the top-level name exposed by the javascript should change from PyPyJS to pypyjs for consistency?


[lsp-server] Feature Request: Support for offline schema transforms

The API I've been working on has created some custom directives to make development easier, and usage of these relies on the mapSchema from @graphql-tools/utils to transform the schema.
I do realize that the extension can be configured to connect to the remote (localhost) api service to introspect the schema - however, that doesn't allow for proper Go-To Definition to work either - since the schema is split among a number of different files and introspection treats it as a single temporary large schema file.
I know this extension can be configured for glob pattern schema files schema: '**/*.gql' - and that works good for the Go-To definition, but errors due to the directives injecting extra fields onto the types.
Offline schema is also preferred since the developer doesn't actually have to spin up the api for it to start working.
A very small sample of what we are doing:
interface UserBase {
  user_id: ID!
  username: String!
  first_name: String
  middle_name: String
  last_name: String
}

type User implements UserBase @inherits(field: "UserBase") {
  created_at: DateTime
}

Our custom @inherits directive looks up the UserBase type, get the fields and merges them onto the type User that it is decorating - with the resulting type (once the API is running) looking like this:
"""@inherits from UserBase """
type User implements UserBase {
  created_at: DateTime
  """@inherits from UserBase .user_id"""
  user_id: ID!
  """@inherits from UserBase .username"""
  username: String!
  """@inherits from UserBase .first_name"""
  first_name: String
  """@inherits from UserBase .middle_name"""
  middle_name: String
  """@inherits from UserBase .last_name"""
  last_name: String
}

It would be awesome if there was some way to configure the extension (and therefore the language-server) by providing an extra script or function to introduce our own schema mapping so we can help the language server understand our custom directives.
If something like this were possible, an extra enhancement would be to allow the extensions customization to indicate the original file/line that the Go-To definition would take when encountering these injected fields.

@Borvik there is a new interface for customizing jump to definition that I just added that would facilitate this! I can't remember what I named it, will check when Im home, but it can be configured from your graphql config file. it was designed to match a similar capability in relay LSP (which I might add, does not require relay and is a nice alternative to our LSP!)

I'd be very interested to know what that would be - though the request isn't purely about the jump to definition, it's mostly about the ability to handle schema transforms that aren't available to be parsed from the source *.gql files

I wonder if we can't solve this issue with graphql-config itself, as it allows very dynamic appraches for loading schema. I will circle back to this soon as I clear up some other things

If we could tap into and register an extension on the config, that might be possible


The training crashes

Dear authors, thank you for sharing your codes for the community, I have a question about the model training, is it nomarl that the model crashes during the training, as I tried to reproduct the model on derain and desnow datasets, but during certain iters, as 800000, the visual results shows like pure noise or pure black. Should I wait more iters or is there any error in my reproduction? Thank you very much

I've verified that the black patch shows when the loss is NAN

hey there can you help me to setup this code locally as i am not able to find datasets and .txt files?

hey there can you help me to setup this code locally as i am not able to find datasets and .txt files?

you can find the .txt files from #10


Update JupyterLite packages

Update to the latest packages and depend on jupyterlite-core to avoid bringing the Pyodide kernel by default.

Superseded by https://github.com/jupyter-widgets-contrib/ipycanvas/pull/338


[BUG] Workspaces require the management ACR name to deploy child bundles

Describe the bug
When deploying a workspace such as workspaces/azureml_devtestlabs that requires acr_name deployment fails.
Two issues:

The API should validate the parameter and say it cannot be found as is marked as required
The API should inject this parameter as it is system provided

Steps to reproduce

Publish  workspaces/azureml_devtestlabs bundle
Deploy the bundle via the create workspace API with a payload without acr_name:

{
  "displayName": "My workspace",
  "description": "workspace for team X",
  "workspaceType": "tre-workspace-azureml-devtestlabs",
  "parameters": {
"address_space": "<IP_ADDRESS>/24"},
  "authConfig": {
    "provider": "AAD",
    "data": {
      "app_id": "xxxx"
    }
  }
}

#420 should come first.

@sachinkundu assigning to you as part of #420

The API should inject this parameter as it is system provided
I'll convert this to another issue. Closing this one.


Check boxes don't work on the backlog view

Screencast from 04-06-2017 08:42:26 AM.webm.zip

@cctrieloff  - check-boxes and the "move" menu have been removed for now.
The work flow was for moving a work item up or down.

Select a check box. For summit, we had restricted work item selection to a single item.
Select an option from the Move drop down menu (move up, move down, move top, move bottom)
The work item would be moved to the specified position

Ordering of work items can be achieved using the drag and drop feature. For this also, a single work item can be selected at a time.


Some fixes to the guide

There was an error while validating job ba48fce7-9869-4348-84e1-3f4f1ad8f4c1 Message:
Result status: Failed
There was a problem accessing Github repository 'https://github.com/Microsoft/cordova-docs.git'.
Details:Microsoft.LightweightJobEngine.Core.Language.ContextCommandBase+ContextCommandException:
Result status: Failed
There was a problem accessing Github repository 'https://github.com/Microsoft/cordova-docs.git'.
---> System.AggregateException: One or more errors occurred. ---> System.ArgumentException: Error clonning repository ---> LibGit2Sharp.NotFoundException: Branch 263 not found. Available branches: origin/master
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetBranch(Repository repo, String name)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass30.<>c__DisplayClass34.b__29(KeyValuePair2 branch)    at System.Collections.Generic.List1.ForEach(Action1 action)    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass30.<CloneRepository>b__28()    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.<>c__DisplayClass1.<ExecuteAction>b__0()    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction[TResult](Func1 func)
at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction(Action action)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)    --- End of inner exception stack trace ---    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository()
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetVersionAsync(String path)
at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.CheckExternalServicesCommand.Do(IDictionary2 context)    --- End of inner exception stack trace ---    --- End of inner exception stack trace ---    at Microsoft.LightweightJobEngine.Core.Language.ContextCommandBase.ThrowIfErrorsLogged()    at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.CheckExternalServicesCommand.Do(IDictionary2 context)
at Microsoft.LightweightJobEngine.Core.Language.JobWorkflow1.RunCommands(Guid jobId, IDictionary2 context, CancellationTokenSource cancelSignal)


show number of statistical errors in refine tab

• Purpose is to encourage more responsible tilegrams by letting users know which states have statistical errors

Updated:


The URL to my online portfolio

Here is the url to my deployed portfolio:
https://taiwoenoch.github.io/TaiwoEnoch-Portfolio/

I pasted the link to my online portfolio


Allow user to create their own placeholders in the cargo-generate.toml file.

It would be nice if users can create their own placeholders so cargo generate can be used for more than just rust projects.
Example
[template]
rust_project = false

[placeholders]
SOME_PLACEHOLDER = "Prompt to user"
SERVER_NAME = "Enter the domain name for your server: "

services:
  jenkins:
    ...
  nginx:
    environment:
      SERVER_NAME: {{SERVER_NAME}}
    ...

Running cargo generate --git <DOCKER_STACK_REPO>
would trigger the typical prompts and...
Enter the domain name for your server:

duplicate of #17

Closing it as duplicate of #17.
Please to contribute to the original issue @seanybaggins :)
Thanks in advance

Closing it as duplicate of #17.
Please to contribute to the original issue @seanybaggins :)
Thanks in advance


simulate_for_sbi breaks iid simulator by automatically reshaping

Please see #767

@michaeldeistler this is fixed with #780, or was never an issue (see my comment in #767 )?

makes sense!


not running under DR

When I run my harness with drrun debug it works fine, but when I run fuzz with winafl it shows the following：
process 37460 is not running under DR
0 processes nudged
nudge operation failed, verify permissions and parameters.
drrun debug log:
Module loaded, dynamorio.dll
Module loaded, xxx.dll
Module loaded, winafl.dll
Module loaded, drx.dll
Module loaded, drreg.dll
Module loaded, drmgr.dll
Module loaded, drwrap.dll
Module loaded, harness.exe
Module loaded, VERIFIER.dll
Module loaded, VCOMP140.DLL
Module loaded, VCRUNTIME140.dll
Module loaded, ucrtbase.dll
Module loaded, KERNELBASE.dll
Module loaded, WS2_32.dll
Module loaded, RPCRT4.dll
Module loaded, KERNEL32.dll
Module loaded, ntdll.dll
In pre_fuzz_handler
In OpenFileW, reading xxx
In OpenFileW, reading xxx
In post_fuzz_handler
In pre_fuzz_handler
In OpenFileW, reading xxx
In OpenFileW, reading xxx
In post_fuzz_handler
In post_fuzz_handler
Everything appears to be running normally.
Coverage map follows:

I'll add to my command line arguments
afl-fuzz.exe -i in -o out -m none -t 20000+ -D C:\Use
rs\xxx\Desktop\fuzz\dymRIO\bin64\ -- -coverage_module xxx.dll -target_module
harness.exe -target_offset 0x1130 -fuzz_iterations 2 -nargs 2 -- C:\Users\xxx\Deskt
op\fuzz\harness.exe @@

Furthermore, my program is running normally, and WinAFL is indeed fuzzing, as evidenced by the running interface. Upon inspection, I've confirmed that winafl.dll has successfully been instrumented into the target program.

It seems that after downgrading to a lower version of DR, the errors have ceased. Could it be that the latest version of DynamoRIO is not fully compatible with it?

Oh, I think I've just discovered an issue in my harness. There's a conditional judgment in the code that's causing the program's DLL to prematurely exit before reaching the end of the harness.


Delete unnecessary dirs/files before building sdist

so we don't ship things like autom4te.cache

I don't see these anymore...

I don't see these anymore...


This page needs updating to reflect latest changes in SharePoint change the look

Will these instructions (and schema) be updated to include some of the newer change the look elements, such as the new header and footer options? Several new change the look options have been introduced since the last update to this page and it would be great to be able to start utilizing them in site scripts.

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

ID: 68267476-ee8d-7b95-446b-711ddb683da2
Version Independent ID: aa099b9d-48db-5513-11c7-32c49a27e5be
Content: Site design JSON schema
Content Source: docs/declarative-customization/site-design-json-schema.md
Product: sharepoint
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Double checked with Microsoft engineering & they say these options you mention aren't in site scripts so there's nothing to update in the docs. When they do update it, they'll update the docs


[google_maps_flutter] Add documentation

Description
Add documentation to google maps plugin.
Related Issues
https://github.com/flutter/flutter/issues/44390
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Thanks for this! Could you also add an analysis_options.yaml file to the plugin linting for this to prevent it from regressing going forward? There's an example you can copy in android_intent. You can test with it locally by running pub global run tuneup.

Actually now that flutter/plugins#2300 has been merged, the better thing to do would be to pull in master and then remove the google_maps_flutter/analysis_options.yaml from there. That PR applied the public_members_api lint globally to all plugins and added exclusions for already failing cases like this one so that it could land. So now that it's merged it would be better to remove the exclusion.


Function wait has a Cognitive Complexity of 9 (exceeds 5 allowed). Consider refactoring.

says CodeClimate.

This has been solved.


Add integration test use case to Examples section in README

Since running integration tests in parallel is one of the great benefits of the project it'd be good to have a small example showing how it can be done. The examples available right now enlighten the uses in automation and scraping, but not so much on tests.

anyone knows how run many instances in  parallel?

While we don't yet have a "recommended" way, here are two options. Both assume you're running the tests over the Proxy.:

Write tests with a test runner that supports concurrent execution (e.g. ava --concurrency <num>, jest--maxWorkers=<num>). Then write any number of tests, for example:

import test from 'ava'
import Chromeless from 'chromeless'

test('google title', async t => {
  const chromeless = new Chromeless({ remote: true })
  const title = await chromeless
    .goto('https://www.google.com')
    .evaluate(() => document.title)

  await chromeless.end()

  t.is(title, 'Google')
})

Then:
export CHROMELESS_ENDPOINT_URL=https://XXXXX.execute-api.eu-west-1.amazonaws.com/dev
export CHROMELESS_ENDPOINT_API_KEY=mulolKOvmeowIaqEC6Azs9Csausages2lCychahal
ava

This first method is used by Graphcool for integration tests on in-production code. You can see a work-in-progress example of this in their Console repository. You'll start seeing these types of tests more within this repository as we improve our test coverage.

Initialise a Chromeless instance n-times that you need it. For example, here's a hacky way I test the Proxy's parallelisation:

const Chromeless = require('chromeless').default

async function run() {
  const chromeless = new Chromeless({
    remote: {
      endpointUrl: 'https://XXXXX.execute-api.eu-west-1.amazonaws.com/dev',
      apiKey: 'mulolKOvmeowIaqEC6Azs9Csausages2lCychahal',
    },
    debug: true,
  })

  const screenshot = await chromeless
    .goto('https://www.google.com')
    .type('chromeless', 'input[name="q"]')
    .press(13)
    .wait('#resultStats')
    .screenshot()

  console.log(screenshot) // prints local file path or S3 url

  await chromeless.end()
}

const concurrency = 1 // increase this to run multiple at once. May cause unexpected AWS usage billing if you're not careful.

for (var i = 0; i < concurrency; i++) {
  run().catch(console.error.bind(console))
}


Content : Updated content for twitter

Updated links, followers count & username.
Will be automated in the future with an appropriate API function.

Approved. Merging


Add version number

Currently I have no clue how to determine the version I am currently using.
No windows version info in the file properties and "about" shows noe version info dialog, only opens the github page.

https://github.com/mapron/d2modgen/releases/tag/0.6.3
done

Now window title contains version.


Add staking support for Waves

Add staking support for Waves. Need to research for Waves protobuf messages to support staking and add them to wallet-core.

Pull request #652


Added FlavioHelloWorld.java

@diaojinggang Please review my code

@FlavioBayer for training purposes, please submit a BAD hello world example for @diaojinggang to review and add comments.

Check the report of travis continuous-integration. It shows the error:
[ERROR] /home/travis/build/TextDB/textdb/textdb/textdb-sandbox/src/main/java/edu/uci/ics/textdb/sandbox/FlavioHelloWorld.java:[12,45] ';' expected
In general, you should first wait until travis continuous-integration passes (just 1-2 minutes) before you submit your pull request.

Hi Flavio,
According to google sheets, it seems like I should review the code.
review:
in line 12, the last character should be ";" instead of ":"
Thanks

@zuozhi Please provide your comments inline (at the place of the code).

@FlavioBayer The check fails because of java gramma mistakes and it won't compile. If you replace : with ; , you can pass all the check. Which means no matter the code is good or not, at least it will compile. Please follow Zuozhi's suggestion to correct the code and then merge to the master branch.

@FlavioBayer can you take care of the comments and finish this pull request soon?

Please review the code again. It should be working now.

Please finish this pull request ASAP.

@zuozhi Please review the code again. It should be working now.

@FlavioBayer It should be ok now, and I just merged the branch to master.


Create PoC Kubernates Cluster in AWS

used kops to create a PoC Kubernates cluster
resources:
https://aws.amazon.com/blogs/compute/kubernetes-clusters-aws-kops/
https://github.com/kubernetes/kops/blob/master/docs/aws.md


Verification fails, but succeeds with --verify-function

In the attached two .zip files generated by running with --record, the first run finds a verification failure in abort_after_failed_item_table_tentatively_write_item, namely a failure to satisfy a precondition of a lemma. But in the second run, using --verify-function abort_after_failed_item_table_tentatively_write_item, it reports "1 verified, 0 errors".
2024-09-18-11-56-53.zip
2024-09-18-11-58-15.zip

I've been informed that the --record didn't capture this important file:
libdeps_hack.zip

And here's the entirety of deps_hack/target/release:
deps_hack_target_release.zip

Here are the SMT files generated:
verify_function_kv__durable__durableimpl_v.smt2.zip
verify_module_kv__durable__durableimpl_v.smt2.zip

If you want to build deps_hack yourself, you can use the kv_dev branch of https://github.com/microsoft/verified-storage

I am somewhat confused about the smt2 log output.  For the module version of the query,
line 58398--59621 seems to contain the query for abort_after_failed_item_table_tentatively_write_item.
;; Function-Def lib::kv::durable::durableimpl_v::DurableKvStore::abort_after_failed_item_table_tentatively_write_item
;; c:/Apps/verified-storage-windows/storage_node/src\kv\durable\durableimpl_v.rs:2500:9: 2504:10 (#0)

However, the corresponding check-sat at 59619 is not followed by get-model or more check-sat for debugging.
In other words, that check-sat at 59619 seemed to have worked according to the smt2 log.
I ran Mariposa on both queries and they both turn out to be stable.
Maybe I am misunderstanding something here?

Oh, I was apparently confused about where the errors were. Sorry about that!


make lint fail

Issue: #42

Hello @gopinath-langote! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file onebuild/config_parser.py:

Line 43:80: E501 line too long (177 > 79 characters)


Update timelines

Added "landed" dates and PRs for two RFCs + some minor formatting fixes in other RFCs. Also added a "released" entry for RFC9 (currently our only RFC implemented in a released version of Cedar).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

did you check that all of the GitHub labels on merged RFC PRs are up to date too?

Yep 👍


Fix the v0.5.0 docs

I fixed examples of Mesh resource and an example of the command to generate traffic on the v0.5.0 docs.
Refs:

https://kuma.io/docs/0.5.0/policies/mutual-tls/
https://kuma.io/docs/0.5.0/policies/traffic-metrics/

Awesome, thank you for the fixes! 🎉
It was there in #181 but must have been lost during merging.


Share optimization ideas with you

Sorry this is not a real issue. There is no forum for this project, I don't know better way to talk to you ;)
FYI, I wrote 2048 ai last year, too. https://github.com/kcwu/2048-c
I used many similar ideas and borrowed some from you, so I'd like to share back to you.
Before @xificurk's improvement, if patched my program with your original eval function, my program can get better score than your original program. So I think you may be interested in how do I handle search details and optimizations (ignore my eval. xificurk's is better). I have noted the difference in the README file. The major ones you could reuse are:

helper minimax search (only consider tile-2) to avoid dead. It can search 20+ steps ahead.
Faster bit operations.
Cache: use more than one hash table. Fixed size hash table to avoid allocation. Also take 'depth' into consideration.
Use 64 bits for score calculation. (32 bits are not enough and may loss some precision)

This sounds great! It seems like we can get a lot from merging some of these ideas.

Minimax sounds like a good idea. I don't know why you'd consider only tile 2 though - seems like the odds of dying to bad 4 placement are also problematic (and usually the cause of game-over situations).
Faster bit operations sound like a good idea. What are some examples here?
#34 takes depth into account when caching positions. What do you mean by using more than one hash table? What would other hash tables store?
Due to the probability limit (CPROB_THRESH_LIMIT), I don't know if we gain much from using double. I wonder what the speed penalty is there.

Is it possible for you to submit a pull request for any of these items?

If compiled for 64-bit it shouldn't make a difference in a modern processor, although the cache would obviously grow larger, so there would be more memory overhead.
But thinking about it, converting to double would make sense. An ieee754 float has a 23 bit mantissa. And heuristic scores are usually over a million. 2^20 = 1048576, therefore you need more than 20 bits just to represent the integral part of the heuristic, which doesn't leave much for the fractional part at all.

Only tile-2 in additional search: this is because the possibility of tile-2 is far larger than tile-4. For example, 0.920=0.1215 > 0.1. That means even the possibility of consecutive 20 tile-2 is still higher than one tile-4. Only consider tile-2 makes the helper search faster.
bit operations: you can try https://github.com/kcwu/2048-c/blob/master/micro_optimize.cc transpose5() used only 12 operations. And count_blank3() is faster than your count_blank1().
Yes, depth should be taken into account as #34.
Regarding to multiple hash tables, they are

cache1[]: a normal one in normal search . used where like yours.
local_cache1[]: like cache1, but only cached the search path. It cannot cover more than cache1, but it is very lightweight and high hit-rate.
cache2[]: a hash table for my extra minimax search.
cache3[]: I have another search extension in eval_reliable(), which is slow and need cache to optimization.

Board score is almost used up all bits. There is not much rooms for calculating the average score of random drops accurately. (You need several bits to *0.9, to += tens scores, to / num_open.) If taken all these into consideration, even 32 bits may not enough. Needless to say 23 bits.

Yes 20 2-tiles have a better chance of being spawned than 1 4-tile.
However consider this: very late in the game when quite often there is only 1 empty tile on the board, on the first level of searching the probabilities will be as follows
(0.9 * maximize(2-tile) + 0.1 * maximize(4-tile)) / (1 empty tile)
which would mean that in the 1st ply of searching you eliminated an entire tree branch that could have a significant effect on the score... and all this in the endgame, where it's needed the most.

My extra 2-tiles search just provided as short-cut: if dead in few moves, don't try this move. Otherwise,still keep original search. So it won't
You can see my root_search_move() for the detail. Yes, this short-cut is only for root move and is not related to score calculation.
https://github.com/kcwu/2048-c/blob/master/bot.cc#L537

But doesn't expectimax already do that? If a tree branch results in a dead position, there aren't any others beneath it, and it negatively affects the score.
You said that if you patched your program with @nneonneo's original eval function yours scored better. I'm curious, have you tried your program with the @xificurk's heuristic? If so what were the results?

FYI, when tuning up the heuristic, I also tried versions that used double, but it did not bring any improvement and run a bit slower.

just a thought, gitter is a great way to communicate within a repository.

If this isn't already implimented, how about an option to calculate deeper or more moves into the future? it should default to the current setting but someone on a powerful computer can raise it to raise their chances of a larger end title/score

The program is single threaded. And since single threaded performance isn't really improving much (newer developments focus on more cores and better power efficiency) it wouldn't do much good. Furthermore, the program looks fewer moves ahead when there are few distinct tiles on the board. This was done to get it to run at an acceptable speed, since the expectimax algorithm cannot be optimized like minimax. and combinatorial explosion happens really fast.
Also, the program doesn't evaluate the entire branch if its probability is low enough (eg. getting 4 consecutive 4 tiles) so increasing the number of moves to look ahead by too much wouldn't do much as most of the tree will be pruned due to the low probabilities before reaching that depth. Again... combinatorial explosion happens really fast.

I have a version in which I have implemented pthreads and uses up to 4 cores. I can make a pull request if anyone's interested.


User Limit

Hello!
I'am running in to a problem that users can't connect to the VPN although they get an OK respond.
I think it has to do with the 2 user limit of OpenVPN. The community edition has this by my knowledge not, any change I could change the 2 user limit to (idk) 100 user limit? (I am expecting a maximum of 20 users the most at all time so 25 would be enough).
Greetings

J0113

Any possibility??

@adworacz I'm creating for every user a new .ovpn file with option 1) from the menu

@J0113 I don't uderstand your issue.
Have you put: user limit to 2, ad now do you want to change it to 50?

@Kcchouette Every user get's a profile (custom generated). The problem is that only two users can connect to the server. I want to let all my all my users (20) be able to connect to the VPN server at the same time!

Can you try adding "max-clients 20" on server.conf?
Did adding that change something?

OpenVPN Access Server has a user limit. OpenVPN Community does not have any.
Plus I can't reproduce this on my side.


Clarification of HTTP_HEADERS format requirements

This is taken from Go implementation, but I believe I've seen similar inconsistencies in other implementations. In Go the definition of HTTP_HEADERs format says
        // Unlike TextMap, the HTTPHeaders format requires that the keys and values
	// be valid as HTTP headers as-is (i.e., character casing may be unstable
	// and special characters are disallowed in keys, values should be
	// URL-escaped, etc).

The way I interpret it is the Tracer is responsible for encoding / url-encoding keys/values before inserting them into the carrier. However, the HTTPHeadersCarrier helper class [has this](https://github.com/opentracing/opentracing-go/blob/master/propagation.go#L148):
// Set conforms to the TextMapWriter interface.
func (c HTTPHeadersCarrier) Set(key, val string) {
	h := http.Header(c)
	h.Add(key, url.QueryEscape(val))
}

which would do an additional url-encoding of the value.
IMO the spec is right, but the helper code is wrong in this case. The helper code should be simply c.Add(key, value).
@bensigelman

@yurishkuro I agree about both the spec (being right) and the code (being wrong / not being updated when it should have been).

One thing I am uncertain about is whether we can count on all http frameworks to respect the client's values. For example, Go's HTTPHeader certainly doesn't respect the case of the keys. Could it be that some frameworks have similar "helpful" abstractions over HTTP headers where they e.g. automatically url-encode values, whether you want it or not?  In those scenarios the tracer is going to have a hard time.

IMO the HTTP case is a mess, and the Tracer impls would do well to "play it safe", whatever that means.

Shouldn't the implementing tracer handle the actual copying of baggage into the headers? Only it could know if it e.g wants to append a prefix (e.g. x-trace-*) or filter the entries, etc.
If I understand correctly, the API should only allow a user to tell the tracer which format should be used, but implementation is up to it, right?

@cwe1ss Tracer does decide if it wants to append the prefix or not. The issue here is that the tracer may not be given access to the actual headers. It's given access to the "carrier", which could be directly passing data onto headers, or storing them and the instrumentation later transfers them from carrier to headers. So in the latter case, the instrumentation might apply additional url-encoding of the values (which is what was happening in HTTPHeadersCarrier), but it would be the wrong thing to do if we clarify that the Tracer is responsible for doing that.

... continued at https://github.com/opentracing/specification/issues/15


Swift 4.0 branch swift merge

Merge swift support from master into swift-4.0-branch.

@swift-ci please test

Please test with following pull request:
https://github.com/apple/swift/pull/7049
@swift-ci please test

@swift-ci please test

@swift-ci please test

Merging tis even without successful PR test because it is better than what we have at the moment, and I can't keep fighting with the PR testing system. The last attempt at PR testing was failing to build Swift.

@llvm-beanz This is the wrong approach. Where was it failing to build Swift? You should talk with the swift buildczar in such situations. If your change breaks swift PR testing, many people will be very unhappy...

@llvm-beanz I just talked with Chris, he told me that this does not affect mainline swift testing. Sorry for the noise!


[WFLY-4357] Update the JDR Subsystem to Include a Type 4 UUID in its Report

Generates a type-4 UUID, stores the value in a JDR server properties file and returns the value to the user once a JDR is generated.

Can one of the admins verify this patch?


Authorizing endpoints or domains against a Shibboleth IDP (two different set of keys for encrypt/signing)

Disclaimer: I have posted this also here. I will make sure I link both once I get things working.
I have successfully added SAML authentication to an Apache server. The IdP I use implements SAML via Shibboleth. Now I want to migrate to Caddy. That’s how I discovered this plugin.
The plugin uses the crewjam/saml package. I have used that before successfully on a standalone golang server against the same IdP I want to use for my Caddy server.
There is one caveat though. The current Apache configuration uses two different set of keys for signing and encrypting.
My questions are:

Can I use this plugin to authorize my domains/endpoints against my SAML IdP?
Can I use the two separate set of keys to setup the SAML flow or I have to use the same keys for signing and encrypting?
When I started working with SAML and  crewjam/saml I found this example very useful to get things going. What would be the Caddyfile to implement that with Caddy and the auth plugin? Maybe I can add it to the examples/docs.

Thank you,
-drd

@drio , please take a look at the following links. I am not sure what you mean by separate keys. Upon authentication via SAML IdP, the portal issues its own token and uses its own keys to authenticate access to some path.
https://authp.github.io/docs/authenticate/saml/jumpcloud
https://github.com/authp/authp.github.io/blob/main/assets/conf/saml/jumpcloud/Caddyfile

Thank you for the reply @greenpau.

I am not sure what you mean by separate keys.

When I look at the metadata (xml file) that I use to configure my apache webserver, I see the following:
...
        <!-- Simple file-based resolvers for separate signing/encryption keys. -->
        <CredentialResolver type="File" use="signing" key="sp-signing-key.pem" certificate="sp-signing-cert.pem"/>
        <CredentialResolver type="File" use="encryption" key="sp-encrypt-key.pem" certificate="sp-encrypt-cert.pem"/>
...

My IDP handles the authentication, I just need my webserver to handle the authorization only (via interaction with the IDP). I guessing I only need the  saml identity provider and the authorization policy mypolicy from the Caddyfile you posted.

@drio, I'm curious about the outcome, were you able to get Shibboleth working with Caddy in the end?

@billksun I ended up bulding my own thing.


Add Grid and Matrix utility classes

Grid is a generic 2 dimensional array representing a grid of Type
Matrix expands on Grid<number> and represents the mathematical construct, hence the class will have functions such as add(a: Matrix, b: Matrix) etc

i think im going to actually make the Matrix arithmetic and stuff happen in a separate PR, im toast for the rest of today :)


Extractor XML descriptors can't be loaded from .jar files

This issue was noted in comments of #5. I am making it a top-level issue for clarity. The 'extractorsDir' config property is bound to FolderResourceFactory but extractor xml files can't be resolved if they are packaged inside a jar.
Now that https://github.com/nhl/link-move/issues/101 is available, we can make it work. Will require LM 2.4 upgrade when it is available.

I have a working implementation on a local branch. Once linkmove is upgraded to Cayenne 4.0.B2 and released, it can be pushed.


[OK] Expose port

What did you implement:
ContainerOptionsBuilder::expose();

It adds the ability to expose ports from Containers.

Closes: #73
Replaces: #74
How did you verify your change:
By testing and with units tests.
What (if anything) would need to be called out in the CHANGELOG for the next release:
Nothing.

Arrrgh, I can't use cargo fmt :c

thanks @Nurrl!


(PUP-2169) flush selinux at transaction teardown

Waiting for CLA signature by @ciprianbadescu
@ciprianbadescu - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppet.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppet.com/community/trivial_patch_exemption.html

jenkins please test this on debian8-64a,debian9-32a,fedora28-64a,fedora29-64a,redhat5-64a,centos6-64a,centos6-32a,redhat7-64a,redhat8-64a,redhatfips7-64a,sles11-64a,sles11-32a,sles12-64a,sles15-64a,ubuntu1404-64a,

CLA signed by all contributors.

jenkins please test this on debian8-64a,debian9-32a,fedora28-64a,fedora29-64a,redhat5-64a,centos6-64a,centos6-32a,redhat7-64a,redhat8-64a,redhatfips7-64a,sles11-64a,sles11-32a,sles12-64a,sles15-64a,ubuntu1404-64a


[Suggestion] Add option to disable command deletion

I'd like to disable the command delete so we know who called it.

Added with the next push:

deleteUsersCommandOnError=true
true(default):
This will delete the user's message if:
Syntax is wrong,
Database connection error
deleteUsersCommandOnSuccess=true
true(default):
This will delete the user's message if:
User is EXIST and SUCCESFULLY SHOWN,
Clans TOP list is EXIST and SUCCESFULLY SHOWN
deleteUsersCommandOnNotFound=true
true(default):
This will delete the user's message if:
User not Found On DB
deleteUsersCommandOnTooFast=true
true(default):
This will delete the user's message if:
User writes a command too fast / that is in cooldown
deleteUsersCommandOnWrongChannel=true
true(default):
This will delete the user's message if:
User writes a command on wrong channel


Returning "None" when calling a variable

Hi!
I'm a newbie in python. I'm working on a console application that generates a basic xml file, so I decided to use PyJade because of my preview experience with Jade.
The code is as follows:
from pyjade.utils import process
import os
...
f = open('templates/genoutdaily.proj.jade', 'r')
prj = open('../out/genoutdaily.proj', 'w')
obj = {'name': 'test'}
prj.write(process(f.read(), **obj))
f.close()
prj.close()
...

The template:
person
  name #{name}

and the output
<person>
  <name>None</name>
</person>

I don't know why I'm getting None instead of test
Could somebody help me?
Thanks in advance,
Edwin

Hi Edwin!
This isn't your fault, the problem is that PyJade was initially intended to just translate Jade templates into other template languages (like Django templates) and let them do the variable interpolation and so on. The builtin PyJade HTML/XML compiler came later, and right now pyjade.utils.process() doesn't pass along any variable context to the compiler.
You have a few options. One is to also install a template library like jinja2 that PyJade can convert into -- here is an example of that, it's a pretty smooth process.
Another way is to patch the built-in process() function to accept variables.
I'm working on improvements, but in the meantime you can use the following function instead of pyjade.utils.process():
from pyjade.parser import Parser
from pyjade.ext.html import HTMLCompiler, local_context_manager

def process(jade_string, context=None, **compiler_kwargs):
    ctx = context or {}
    block = Parser(jade_string).parse()
    compiler = HTMLCompiler(block, **compiler_kwargs)
    with local_context_manager(compiler, ctx):
        return compiler.compile()

# So your code becomes
with open('templates/genoutdaily.proj.jade') as f:
    with open('../out/genoutdaily.proj', 'w') as prj:
        obj = {'name': 'test'}
        prj.write(process(f.read(), obj))
# and no file-closing needed, because `with` takes care of that when you leave the block

Hi Ben!
Thanks a lot for your response!
The code you sent me worked perfectly!
Best,
Edwin


compass cache size detection not working on AMD EPYC hosts

travis CI is using AMD EPYC 7401P 24-Core Processor recently, compass cannot detect the cache hierarchy correctly there
https://travis-ci.org/psteinb/compass/jobs/417308560

resolved with #17


Requires unicorn version: 1.0.2. Relax this requirement?

At the moment Speakeasy requires a very specific version of Unicorn: 1.0.2. However, the latest Unicorn version presently available via PyPI is 1.0.3. As a result, run_speakeasy.py produces an error:
AssertionError: Requires unicorn version: 1.0.2

Would it be possible to relax the Unicorn requirement so that 1.0.2 is the lowest supported version, so that higher Unicorn versions would also be accepted?

The assertion is removed with: https://github.com/fireeye/speakeasy/commit/9c6145e82a6b3c728ff902c88b2740b7f4fc1747


feat(videoplayer): add closed captions

Related Ticket(s)
#4012
Description
Add closed caption button to VideoPlayer.
Changelog
New

closed captioning button to Kaltura video player

I'm assuming actual close captions would replace "Test Video - 1:1 (0:18)" under the video, correct?

I'm assuming actual close captions would replace "Test Video - 1:1 (0:18)" under the video, correct?

It will add the CC button if the video has captions.

Currently only working locally, as the Kaltura environment variables for deploy previews needs to be changed to view the videos (examples in any of the CTA video variations).


new mqtt client invokes old callbacks

Steps:

create a mqtt client 1 with callbacks
connect
disconnect
create new client 2
connect -> success called on old callback handler of first client

Sorry, Was another issue...


ci: add node 12

Codecov Report

Merging #44 (9f575c0) into main (8b20c83) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #44      +/-   ##
==========================================
- Coverage   30.19%   30.13%   -0.06%
==========================================
  Files          13       13
  Lines         573      574       +1
  Branches      118      118
==========================================
  Hits          173      173
- Misses        400      401       +1

Impacted Files
Coverage Δ

packages/vite-plugin-checker/src/logger.ts
20.35% <0.00%> (-0.19%)
:arrow_down:

Continue to review full report at Codecov.

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

relating to https://github.com/fi3ework/vite-plugin-checker/issues/42


Update 24.1.0

☆ Hatch Fancy PyPI Readme 24.1.0 Update ☆
Jira Ticket
Upstream
Changes

Updated version number and sha256
removed noarch
Skip to python versions less than 3.7
Updated build script with --no-deps, --no-build-isolation, and --ignore-installed flags
New and improved about section
Replace denigrated build testing dependency with python-build

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_9eij18t78w/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:25: python_build_tool_in_run: The python build tool hatchling is in run depends
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_bege7w3xgi/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:25: python_build_tool_in_run: The python build tool hatchling is in run depends
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_1dpcpu6fbt/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:25: python_build_tool_in_run: The python build tool hatchling is in run depends
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_14tchr9jnu/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:25: python_build_tool_in_run: The python build tool hatchling is in run depends
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_63eubquhl2/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:25: python_build_tool_in_run: The python build tool hatchling is in run depends
===== Final Report: =====
0 Errors and 1 Warning were found


missing/truncated docs text for torchdata.nodes

📚 The doc issue
https://pytorch.org/data/main/what_is_torchdata_nodes.html#how-does-torchdata-nodes-perform

With GIL python, torchdata.nodes with multi-threading performs better than multi-processing in some scenarios, but makes features like GPU pre-proc easier to perform which can boost

Suggest a potential alternative/fix
not sure!

Nice catch @rbavery !

This is fixed on main now https://pytorch.org/data/main/what_is_torchdata_nodes.html#how-does-torchdata-nodes-perform Thanks @rbavery for flagging!


Added item groups, logger, and more

Dont ask how the register on ItemGroups.java works

Closing this as it's pretty incompatible with the project structure now


Using Nuts for the remoteReleases URL in electron-installers

I am using Nuts as my endpoint for autoUpdater, and grunt-electron-installer to generate my installer, with .nupkg, setup,exe, and RELEASES files. I was wondering if it could also be used as the URL for remoteReleases in grunt-electron-installer as it would be convenient instead of having to host separate servers for nuts and my .nupkg, RELEASES, and Setup.exe files.

Got it. remoteReleases requires a URL to where the RELEASES, *-full.nupkg, *-delta.nupkg are found. Since Nuts requires the version to be passed in, I pass it as a command line option in grunt. Thus, I set
remoteReleases: 'http://my-url.net/download/' + grunt.option('ver'),.
And from the command line, I would do
grunt create-windows-installer --ver=x.x.x, assuming I have that endpoint in Nuts.


onInit does not execute from static creation method

I want to create some factories around my models. This is how I typically do it, but onInit doesn't fire when instantiated this way. What am I missing?
Excerpt from Code Sandbox
import { prop, objectMap, Model, idProp, model } from "mobx-keystone";

@model(`MyModel`)
export class MyModel extends Model({
  id: idProp,
  name: prop<string>(),
}) {
  onInit() {
    console.log(`init ${this.name}`);
  }

  static create(modelData: any) {
    return new MyModel(modelData);
  }
}

const foo = new MyModel({ name: "foo" }); // logs "init foo"
const bar = MyModel.create({ name: "bar" }); // no log

are you using babel transpiration by any chance? if so try to move the create function outside the class, there's a bug in a babel decorator plugin that makes references to the same class within static classes actually reference the undecorated class

related issue https://github.com/xaviergonz/mobx-keystone/issues/122

@xaviergonz Sorry for the duplicate issue. Thanks for helping. As an alternative, do you see anything wrong with calling onInit() manually?
static create(modelData: any) {
    const result = new MyModel(modelData);
    result.onInit();
    return result;
  }


support/http/httptest: add headers to response

Mocked responses should have the ability to have custom headers. Currently, only the response body can be mocked.

closed in #1434


Admin panel refactoring

We're bumping Bootstrap to the next major version (v4 -> v5), and that will require us to do some deeper changes to the admin panel front-end.
I'll take this opportunity to do a deeper facelift on the UI itself. We should see dark mode finally being properly implemented and some stuff that wasn't exactly playing nicely on mobile should be back... playing nicely with mobile devices.

19 commits in - I figured out I'd give a little teaser on the new control panel look and feel?
It's not going to be anything huge where everything gets done upside down; In fact, you should be able to use the new panel just like you used the old one. But this one is more beautiful and actually kinda works on your phone, too. :wink:
Feedback is welcome! I'll keep you posted.

Context
Old
New

Login

Status Checks

TLS Certificates

Backups

PGP Keyring

WKD Management

6 pages to go!

So far, so good - some pages will need some deeper refactoring, but we've reached the point where everything works reasonably well.
Next commits will be targeted towards implementing proper dark mode.

Dark mode, your eyes will finally be able to rest :relieved:
Ok, this was a bit easier than expected. The admin panel will include a toggle so that you can switch between light and dark mode to your heart's content!

I might be done for now!
There'll be a second refactoring phase on the entire codebase (covering admin panel AND the API) which won't be part of this PR.

Nice one!
The new admin panel looks gorgeous with that dark theme.

Thanks! ^-^

Looks really great, thanks for your efforts 👍🏻


Update dependencies

This PR provides some dependency updates.

update Apache Arrow to v15
update Cloudquery plugin SDK to the latest version (v4.29.1)
update indirect dependencies

ping @dihedron :)


SPI DMA & Async memcpy (IDFGH-9182)

Answers checklist.

[x] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Slave SPI DMA and async memcpy doesn't work together.
Device: ESP32-C3 (any devboard or chip)
How to reproduce:

compile "spi_slave/receiver" example
check it works fine
add "esp_async_memcpy_install" code anywhere (before or after spi initialize) (see below)
compile and see SPI doesn't work (send garbage to master)

Initialize async memcpy code:
async_memcpy_config_t config = ASYNC_MEMCPY_DEFAULT_CONFIG();
async_memcpy_t driver = NULL;
ESP_ERROR_CHECK(esp_async_memcpy_install(&config, &driver));

@enhany  Thanks for reporting the issue. This seems like a hardware limitation that we can't workaround very well at the moment. The issue is that, the memory copy engine will occupy one of the DMA trigger ID that used by the peripheral. And by default, we set the trigger ID to zero for memory copy, however this ID is also used by SPI2.
For now, you can just change them to 2, your SPI2 should work again.
In the future, we should make that user ID selectable from the menuconfig. But we can't change the situation that the memcpy takes another perpheral's DMA.


Compact signing that uses stdin instead of a file

With this PR, the signing flow is as follows:
Generate keys with pact -g > key.yaml
Create an unsigned SigData representation with pact -u tx.yaml > tx-0.yaml.
Now you can add a signature with cat tx-0.yaml | pact add-sig key.yaml > tx-1.yaml.
You can chain these invocations with cat tx-0.yaml | pact add-sig key.yaml | pact -add-sig key2.yaml > tx-2.yaml.
You can add many signatures in one shot with cat tx-0.yaml | pact add-sig key*.yaml.
In all of these cases, pact add-sig takes SigData YAML on standard input and puts the output with the additional signature(s) on standard output.  If the added signatures result in a fully signed transaction that validates, then add-sig will instead output the final transaction JSON ready to be sent to the blockchain.
The above workflow gives a serialized process of adding signatures.  This PR also supports a parallel process as follows:
pact -u tx.yaml > tx-0.yaml
cat tx-0.yaml | pact add-sig alice.yaml > tx-alice.yaml
cat tx-0.yaml | pact add-sig bob.yaml > tx-bob.yaml
pact combine-sigs tx-alice.yaml tx-bob.yaml > tx-final.json

The combine-sigs operation has the same output behavior as add-sig where if the transaction validates, the output is the final JSON, otherwise it is the SigData YAML.
To export data to a cold wallet using QR codes, you can drop the command data with grep -v "^cmd:" tx-0.yaml (the output of the pact -u command).  The above parallel process would then become:
pact -u tx.yaml > tx-0.yaml
cat tx-0.yaml | grep -v "^cmd:" > tx-0.small.yaml
cat tx-0.small.yaml | pact add-sig alice.yaml > tx-signed-alice.yaml
cat tx-0.small.yaml | pact add-sig bob.yaml > tx-signed-bob.yaml
pact combine-sigs tx-0.yaml tx-signed-*.yaml > tx-final.json

Just realized this isn't quite ready yet.  The new commands can sometimes reorder the signatures.  Need to fix it to not change the order.

@mightybyte the ordering is actually fine. The pact add-sig output might switch the order of the signers, but at the very end it adds the signers and signatures in the ordering that you specified in the yaml file of your transaction.

Great, thanks @LindaOrtega.  @slpopejoy I think this should be ready to merge then.


Grouping errors by *errors.errorString

This kinda sucks:

The error class to be sent to Bugsnag. This defaults to the type name of the Error, for
example *error.String

https://github.com/bugsnag/bugsnag-go/blob/master/event.go#L55
It's pretty common in Go to use errors.New and fmt.Errorf very liberally, rarely creating your own types for errors. If you do that, bugsnag will group by the ErrorClass, resulting in a bunch of very different errors being grouped together. Can we add a way to configure this?

It'll only group them together if they happen from the same line of code, so it's not too too bad.
Happy to think about ways of making this better. From past experience just using the message is terrible, as messages are too unique so you end up with the opposite problem.

Going to close this, as I think the best way is just to use a custom error type.

In case someone else gets to here because grouping is too broad, the key ingredient for correct grouping is to set ProjectPackages in your configuration to a suitable value (e.g. []string{"github.com/yourco/yourproj/**"}) as the grouping goes by the top most line that's in-project, but if it finds nothing in-project it will just use the top line which is likely something like
runtime/panic.go:489 gopanic
(or maybe it just skips the top file:line and uses the error class exclusively?)
making everything sharing an error class group together.


Release v0.1.0-alpha3

Testing

[x] Test node peers/syncs with testnet parachain: ./target/release/pop-node --chain node/chain-specs/pop-paseo.raw.json -- --chain node/chain-specs/paseo.raw.json

synced #794929 blocks
shown to be peered with collators
[x] Test runtime upgrade locally (no existing state):

Pop Network current

Switch to commit of last release and build pop node.
Start network with pop u p -f paseo.toml -r v1.7.0 -v and:

verify pop node version -- rpc calls -> system -> version()
verify runtime version -- rpc calls -> state -> getRuntimeVersion()

Leave the network running.
Pop new release

Switch to your branch where you have bumped the versions and rebuild.
In Activity Monitor on Mac, find the pop-node process and force quit. The network will still be running, but without the collator so no pop blocks. Or killall pop-node.
Return to the terminal where you launched pop up and copy the command shown in the output which was used to launch the pop-node collator.
In another terminal, run this copied command. This will launch the newly built node (new release) and have it use previously generated chainspecs, effectively allowing it to take over running the network with latest release. Ensure that blocks continue to be produced and verify node version (see above).
Upgrade the chain to the new runtime release -- can be found in target/release/wbuild/testnet_runtime/testnet_runtime.compact.compressed.wasm
Verify successful runtime upgrade:

verify pop node version -- (see above)
verify runtime version -- (see above)
verify migrations have been executed successfully
verify chain is running

[ ] Test runtime upgrade locally based on existing state from testnet: follow

[ ] Test runtime upgrade using try-runtime:

cargo b -r --features=try-runtime
try-runtime --runtime ./target/release/wbuild/pop-runtime-testnet/pop_runtime_testnet.wasm on-runtime-upgrade live --uri wss://rpc3.paseo.popnetwork.xyz:433

Release

[ ] create release for node: e.g. https://github.com/r0gue-io/pop-node/releases/tag/v0.1.0-alpha2

[ ] provide a description and then click generate release notes

[ ] create release for runtime: e.g. https://github.com/r0gue-io/pop-node/releases/tag/v0.1.0-alpha2

[ ] provide a description and then click generate release notes

[ ] do a final runtime upgrade with chopsticks using the deterministic runtime wasm blob from the release.
[ ] approve and enact on chain

Stuck on try-runtime and chopsticks tests

See #155 and #157


Wrong coloring syntax

Steps to reproduce

Use the following functional code
Expected behaviour
The color syntax is wrong starting with the subshell at line 13. The content of the two echo at line 22 and 23 should be yellow for instance
Version of Vim
VIM - Vi IMproved 6.4 (2005 Oct 15, compiled May  3 2006 12:40:19)
Environment

OS : AIX 7.3
Terminal : Windows Terminal
TERM : xterm-256color
SHELL : Bash 5.1.4(1)-release

Logs and stack traces
No response

VIM - Vi IMproved 6.4 (2005 Oct 15, compiled May 3 2006 12:40:19)
I don't mean to come across as overly snarky, big iron being big iron, but chances are that if there was something to fix, it has been fixed sometimes during the last 17 years. I'm getting slightly different results using vim9 right now.
You could try tossing the current syntax file onto that box, but your best bet is to try and catch up if at all possible.

wow, that is an old version.
Looks like the latest version available for AIX is 7.4.460 (which is also quite old): http://www.perzl.org/aix/index.php?n=main.vim
BTW: if @flyingdutchman could share the bash snippet it's easier to reproduce and show syntax output.

similar one:
output="$(
	foo
	sed 's/"//g'
	bar
)"

// though perhaps was not a recommend coding style.

I've fixed the problem Shane pointed out, although I have yet to run it through my test suite and see what happens (and fix 'em). The OP's problem I won't touch until I get some code I can work with; I'm pretty busy and don't have the time to type all that in.

Thanks for the quick responses !
Here is the code, I also updated the original post to have it
#! /bin/bash

arr=()

scanHost()
{
  arr+=("$(hostname)")
  tmpResult=$(hostname)
}

scanHost

eval "$(ssh operator@sasqa_vm_09 "bash -s --" <<EOF
$(typeset -f scanHost)
$(declare -p arr)
scanHost
declare -p arr
declare -p tmpResult
EOF
)"

echo "Local array -> ${arr[@]}"
echo "Local echo  -> $tmpResult"

Hi,
I checked on my local installed version 9.0.975 and it seems to be okay I would say.

@flyingdutchman you may try to update the sh.vim syntax file from @cecamp website http://www.drchip.org/astronaut/vim/index.html#SYNTAX_SH However I am not sure this will work on your old vim version.

Great thanks for the help ! I'll try that :)
Since the issue is only present on old versions, I'll just close this issue.


New distribution: ParticleDistribution

This PR simply adds the new distribution ParticleDistribution and corresponding tests. All methods and properties of SMCUpdater which were (in my opinion) relevant to a bare particle distribution were copied over (but left intact). This is the first step of #105. The next step, in my view, is to implement the hierarchy ParticleDistribution>AbstractUpdater>SMCUpdater.
It would be worthwhile for someone to compare the properties and methods of ParticleDistribution and SMCUpdater to check if my choices are appropriate and comprehensive.
[Sorry for all the whitespace changes my text editor did automatically]

Coverage increased (+2.2%) to 67.713% when pulling 1bef90ed4eee2c2ccf772ab396df39294bd8464c on ihincks:feature-particle-distribution into a93f9d2a971258f6f7a0e9e645b28f7601711067 on QInfer:master.

Coverage increased (+2.2%) to 67.713% when pulling 66ace2db847fcd9de47ec9a6cd88a9f694071e1e on ihincks:feature-particle-distribution into a93f9d2a971258f6f7a0e9e645b28f7601711067 on QInfer:master.

Coverage increased (+2.2%) to 67.713% when pulling 66ace2db847fcd9de47ec9a6cd88a9f694071e1e on ihincks:feature-particle-distribution into a93f9d2a971258f6f7a0e9e645b28f7601711067 on QInfer:master.

Coverage increased (+2.2%) to 67.713% when pulling 66ace2db847fcd9de47ec9a6cd88a9f694071e1e on ihincks:feature-particle-distribution into a93f9d2a971258f6f7a0e9e645b28f7601711067 on QInfer:master.

Coverage increased (+2.2%) to 67.713% when pulling 66ace2db847fcd9de47ec9a6cd88a9f694071e1e on ihincks:feature-particle-distribution into a93f9d2a971258f6f7a0e9e645b28f7601711067 on QInfer:master.

Thanks, this looks like a very good start on #105! I'll look over and see if I have any concrete suggestions, but after a cursory look, I think it's great.
Before merging, I'd like to fix the Travis build error, though. It looks like it's unrelated to this PR, but is happening due to changes in QuTiP upstream; now that 4.0 is out, we should be able to make the doctest build more stable, so I'll go on and take care of that in a separate PR soon. Thanks!

Coverage increased (+2.2%) to 67.713% when pulling 5ff3f5a43773bc5ae4c7788a41fae401b2e7b31b on ihincks:feature-particle-distribution into a93f9d2a971258f6f7a0e9e645b28f7601711067 on QInfer:master.

Coverage increased (+2.2%) to 67.713% when pulling 5ff3f5a43773bc5ae4c7788a41fae401b2e7b31b on ihincks:feature-particle-distribution into a93f9d2a971258f6f7a0e9e645b28f7601711067 on QInfer:master.


[Feature] Support adding additional attr[0-4] for service level metrics

Search before asking

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

Description
Add attr[0-4] to all service level metrics through OAL and MAL metrics, and support customers to set these attrs through OAL filter(code extension) or MAL SampleFamily processes.
To keep the costs limited, this feature would be totally optional, and we will only wave layer as attr0 for the default implementations.
FYI @Fine0830 We will need UI side enhancement to add a new kind of widget to query layer-based TopN on the root dashboard to get the service list. And those services could jump into the service dashboard like the service table widget.
Use case
Currently, all service topN needs to be globally query. But, within v9 and v10, we introduced the layer concept, and many more monitoring are added.
Then, people are wondering, whether SkyWalking would provide group or layer-based topN query? Sadly, we can't as service metrics(all metrics actually) don't have extra extension fields.
So, with this extension and MQE extension, we could have new expression such as service_cpm{attr0="general"} to get a layer-based topN.
Related issues
No response
Are you willing to submit a pull request to implement this on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

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

@wu-sheng @wankai123 Lets ensure this Label based metrics supports Services and Endpoints.


add udp interface

Not used in solo-python, but allows separate testing tool to interface with a software authenticator for testing purposes.
See https://github.com/solokeys/solo/pull/115

I changed the patch method name to snake case (solo.fido2.force_udp_backend) for consistency, and added some ways to call it from solo tool.
Can we get rid of the patched python-fido2 now?

Yes no reason to keep our version of python-fido2


apps: Fix the mismatch of SM2 keys keymgmt

The SM2 key has a separate keymgmt, which is independent of the
EC. The key generated by the subcommand ecparam is wrong. Using
'openssl ec -in sm2.key -noout -text' will also encounter some
errors.
When using the ecparam subcommand to generate the SM2 key, use
the correct keymgmt to solve this problem.
Signed-off-by: Tianjia Zhang<EMAIL_ADDRESS>
Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

This pull request is ready to merge

Merged to master. Thank you for your contribution.


Provide pagination information such as total number of pages

Hello @fabienpiette
Currently fetcheable_on_api pagination support does not return any information whatsoever about pagination state to the caller.
Information such as the total number of pages or items should be returned to the caller or added to the response in some way, otherwise a client cannot know when to stop requesting next page.
I see two options in order to provide this:

Return the information to the caller in some way, so they can use it however they see fit.
Add the information to the response headers directly.

Release of 0.1.4 address the issue, but it is undocumented.


Yatin: Watch premier-aesthetics.com

Yatin requests the watch of the watch_keyword premier-aesthetics\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

premier-aesthetics\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


fastjson2 不支持

JSON converter cannot be found. Please check your classpath if there is the JSON framework, eg. Jackson (>= 2.9.10), Gson or Fastjson (>= 1.2.48), in the dependencies of your project.
maven dependency

com.dtflys.forest
forest-core
1.5.26

com.alibaba.fastjson2
fastjson2
2.0.15

org.projectlombok
lombok
1.18.24
provided

com.google.protobuf
protobuf-java
3.21.7

Currently, Forest does not support fastjson2.
But it will be integrated in future version.


Microsoft.Maps.Directions.d.ts implicit any types

In Microsoft.Maps.Directions.d.ts definition file, in the Waypoint class, these three declarations break the disable implicit 'any' types rule :
	/**
	*	Occurs when the any properties of the waypoint change or are updated.
	**/
	changed(waypointEventArgs: WaypointEventArgs);

	/**
	*	Occurs when a geocoding request for the waypoint’s address is made.
	**/
	geocoded(waypointEventArgs: WaypointEventArgs);

	/**
	*	Occurs when a reverse geocoding request for the waypoint’s location is made. This happens when no address is provided for the waypoint, or if the waypoint is dragged (in which case its location is changed).
	**/
	reverseGeocoded(waypointEventArgs: WaypointEventArgs);

I guess we can just add ": any" at the end of the declaration to make them explicit and then comply to the rule.

@bmiller1 ?

From the current version of Microsoft.Maps.Directions.d.ts:
    changed: (args: WaypointEventArgs) => void;
    geocoded: (args: WaypointEventArgs) => void;
    reverseGeocoded: (args: WaypointEventArgs) => void;

Those functions already have return types and they do pass the implicit any rule.  Adding the comments would be good though.

Completely sorry, i didn't realize i was using definition files not coming from DefinitelyTyped.
I deleted the other files and switched to the DefinitelyTyped nuget package.
The previous problem is fixed but i have other ones :

the LocationRect class definition is wrong, it defines the getSoutEast methos instead of getSoutheast (the 2nd 'e' should not be a capital letter).

        getSoutheast(): Location;

The EntityCollection constructor should declare the option argument optional.

        constructor(options?: EntityCollectionOptions);

Properties in the EntityCollectionOptions should be optional.

    export interface EntityCollectionOptions {
        bubble?: boolean;
        visible?: boolean;
        zIndex?: number;
    }

In Map class, tryLocationToPixel and tryPixelToLocation only support array arguments, they should support array or single argument types.

        tryLocationToPixel(locations: Array<Location>|Location, reference?: PixelReference): any;
        tryPixelToLocation(points: Array<Point>|Point, reference?: PixelReference): any;

I agree with doubret's suggested changes

thanks! please send a pull request.

bmiller1 or I ?

You.
On Fri, Aug 14, 2015 at 12:41 PM, doubret<EMAIL_ADDRESS>wrote:

bmiller1 or I ?
—
Reply to this email directly or view it on GitHub
https://github.com/borisyankov/DefinitelyTyped/issues/5243#issuecomment-131191843
.

Ok, no problems.
I'll do that in the weekend.

All has already been fixed by @ericrtodd.
The issue can be closed.


PubSub SubscriptionAdminClient.create() returns subscription with invalid name

Environment details
Docker container openjdk:14-alpine
google-cloud-pubsub version 1.82.0
Steps to reproduce

Create a new subscription using the SubscriptionAdminClient
print the results of getName() on the returned instance
Create a subscription using the Subscription.newBuilder() method
print the results of calling getName() on the instance

The results of step 3 is the "full" path of the subscription while step 4 is just the expected subscription name.
Code example
String projectId = "1234";
String topic = "foo";
String name = "bar";

SubscriptionAdminClient client = SubscriptionAdminClient.create();
ProjectTopicName topicName = ProjectTopicName.of(projectId, topic);
SubscriptionName subName = SubscriptionName.of(projectId, name);

// Generated subscription creates incorrect name
Subscription subscription = client.createSubscription(subName, topicName, PushConfig.getDefaultInstance, 0);

System.out.println(subscription.getName) // output: projects/1234/subscriptions/bar

// Manual subscription has correct name
Subscription subscription2 = Subscription.newBuilder()
          .setName(subName.getSubscription)
          .setTopic(topicName.getTopic).
          .setPushConfig(PushConfig.getDefaultInstance)
          .setAckDeadlineSeconds(0)
          .build();

System.out.println(subscription2.getName) // output: bar

Thanks for reporting this finding.
When creating a subscription manually, the name passed into .setName should be in the form of "projects/{project}/subscriptions/{subscription}".  In the case above, 'subName.getSubscription' will not return the full name, just the 'bar' portion of the name.
When creating a subscription manually, subName.toString() should be used instead to set the name. For example, the following manual subscription should report the same name as the generated subscription:
Subscription subscription2 = Subscription.newBuilder()
.setName(subName.toString())
.setTopic(topicName.toString()).
.setPushConfig(PushConfig.getDefaultInstance)
.setAckDeadlineSeconds(0)
.build();


Increase (and/or make configurable) the maximum size of a direct response

Title: Increase (and/or make configurable) the maximum size of a direct response
Description:
I'd like to have a direct response which is more then 4KiB in size, I completely understand the desire to be conservative with the size of direct responses (and the niceness of 4KiB aligning with common block/buffer sizes) but I have a use case where a slightly larger maximum size would be useful for me.
I propose either/both:

Increasing maximum direct response size to say 16KiB (an arbitrary number, way more than I need)
Making the maximum direct response size configurable (perhaps keeping the default as 4KiB)

[optional Relevant Links:]
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/http/http_routing#:~:text=If a response body is,footprint from growing too large.

This is a dupe of https://github.com/envoyproxy/envoy/issues/13422.

This is a dupe of https://github.com/envoyproxy/envoy/issues/13422.


Add 3 dotnet tools

Add Fusion++, RepoZ and dnSpy to the Tools list.

Thanks for the changes, @rpetrusha. I changed applied them, of course.

Thanks for making the additional changes, @awaescher. I'll merge your PR now.


Wire add UI - rubber banding click to activate

In "click to activate" mode -- when an "open" plug is left clicked on, it will enter wire add mode.
A rubber band will follow the cursor until:

A left click on another "open" plug (which will initiate rendering a wire)
A left click on an empty space or non "open" plug -- exit wire add mode

This is now working.