Alpine Linux based images

It'd be nice if there are images based on Alpine Linux.

Thank you for your review. I modified Dockerfile and add the health check introduced in #8 as well.
One problem is that Alpine Linux doesn't have bash by default. I, hence, modified shebang to use OS's default shell. Is it an acceptable change? If not, I'll copy shell scripts in alpine directory so that the main image can use /usr/bin/env bash and the alpine one can use /bin/sh.

Email addresses and the COPY step are fixed.
As for the shell scripts, if you build with this command at the root of this repository, it should work:
$ docker build -t sia:1.4.7-alpine -f alpine/Dockerfile .

(and docker build -t sia:1.4.7-dev -f dev/Dockerfile ., too)


proxy disparity generation

Hey, I tried to use the method "Unsupervised-Confidence-Measure" to generate proxy disparities. However, I found it can only get left disparity. How did you generate the right one?
Another question is that sampling probability, also the argument "input_points" in main.py. I see it is different between train and test in your paper. Specially,  1/1000 in train stage, 1/20 in test. But you didn't set it in the  readme. I want to confirm it.
hope for your reply.

Hi, in order to generate the right disparity map using "Unsupervised-Confidence-Measure" given an input stereo pair, you can flip horizontally the left and right images and then switch them before passing to the method. To put it simply, the horizontally flipped left image become the new right image and the horizontally flipped right image become the left one. As final step, you just have to flip again the disparity outcome from the method. By doing so, you will have a disparity map aligned with the right view of the initial stereo pair.
For what concern the "input points", we confirm that we use 1/1000 during training and 1/20 during testing in our experiments. You can find such implementation detail in Section 4.2 of the main paper.

@xjturobocon
Hello,
Have you reproduced this repo?


[Feature]: plugin integrations

Similar Issues

[X] Before filing, I have searched for similar issues.

Description
Just toying with an idea, what if we could integrate with various other plugins that add default keymaps? For example diffview.nvim adds a bunch of keymaps when diffview is open, we could built an integration that would automatically show them in the legendary finder.

I tried to integrate it with packer.nvim and failed. My goal is to have keymaps of lazy-loaded plugins displayed in the legendary API before the plugin is actually loaded.
I tried to use the helpers module, but it clashes with packer's bindings for lazy loading.

For now you should be able to manually add the keymaps to legendary. There isn’t a great way to do it automatically at the moment.
I need to put a lot more thought into this.

Is there a way to add a keymap without actually mapping it? My goal is to prevent collision with packer's lazy-loaded-by-keys plugins.

Yes, just don’t provide an implementation (2nd list element), just keys and description. See: https://github.com/mrjones2014/legendary.nvim/blob/master/doc/table_structures/KEYMAPS.md

Oh, your'e right. I must have missed that.
Thank you very much!

We’ll be starting with nvim-tree. My comment from #289:

Hey there, this is awesome, thanks for filing the issue!
This may be better suited actually for #184, nvim-tree is probably a good candidate for a first one for a proof of concept.
I'm not sure exactly what they will look like, but I have a few ideas. The best idea I have currently is along the lines of:
Legendary.nvim must be loaded before other plugins. We have a set of plugins, or plugins can be provided by the other plugin itself, at legendary.plugins.[plugin name]. This way, plugins can be looked up dynamically; that is, if they wanted to, nvim-tree could provide its own legendary.nvim integration by adding lua/legendary/plugins/nvim_tree.lua in their repo, just for an example.
The plugin is just a plugin-specific script that must handle registering its keymaps, commands, autocmds, and functions. It may set up autocmds to do so on BufEnter for example, or it may call some custom logic to determine the correct buffer to attach to.
So for this example, and nvim-tree / legendary.nvim plugin would look like:
User's config:
require('legendary').setup({
  plugins = {
    nvim_tree = true,
  }
})

File: lua/legendary/plugins/nvim_tree.lua
vim.api.nvim_create_autocmd('FileType', {
  pattern = 'NvimTree',
  once = true,
  callback = function()
        local   nvimtreemappings = require("nvim-tree.keymap").keymaps
        local   keystodisable    = vim.tbl_map(function(e) return e.key end, nvimtreemappings)
        -- Set up Legendary plugin keybindigns
        local keymaps = vim.tbl_map(function(e)
            -- just set up a description-only keymap
            local entry = {}
            entry.mode  = "n"
            entry[1]    = e.key        -- Key
            if type(e.key) == "table" then entry[1] = e.key[1] end
            entry.description = "Nvim-tree: " .. e.desc
            entry.opts = { buffer = bufnr, noremap = true }
            return entry
        end, nvimtreemappings)
        require('legendary').keymaps(keymaps)
  end
})

See also:

https://github.com/nvim-tree/nvim-tree.lua/issues/1858
https://github.com/nvim-tree/nvim-tree.lua/issues/1869

@mrjones2014 You may also want to take a look how persisted.nvim deals with Telescope integration over here.

@mrjones2014 Minor feedback here. I think  Legendary dont' needs a sophisticated module-resolving system akin to Telescope one. The best way to handle plugins IMO by registering a plugin table (object) with a meta information and init function that is provided by api instance e.g.:
   local legendary = require("legendary")
   legendary.plugins:add({
      name = "FooPlugin",
      init = function(api)
         api.register({ keymaps = { ... } })
      end
)

I have seen this approach many times in Web development tools.

I disagree.
This doesn't allow the user to easily load only the plugins they want, unless you mean the user will be writing the snippet you gave above themselves, in which case I think that's just really un-ergonomic. This also doesn't easily allow other plugin authors to provide their own legendary.nvim plugin integrations.

I have seen this approach many times in Web development tools.

That's an extremely different use case.

@mrjones2014 Flexibility may be achieved both by consumers and plugin-writers:
    -- init.lua
    local PluginA = require("cool/legendary/extensionA")
    local PluginB = require("cool/legendary/extensionB")
    local PluginC = require("myExtensions/legendary/keymaps")

    legendary.plugins:add(PluginA)
    legendary.plugins:add(PluginB)
    legendary.plugins:add(PluginC)
    legendary.plugins:add({
        name = "foo-keymaps"
        init = function(legendaryApi) ... end
    })

That's a lot less ergonomic than just being able to do:
require('legendary').setup({
  plugins = {
    plugin_a = true,
    plugin_b = true,
  },
})

It also potentially breaks lazy-loading setups.
Is there any actual downside to a module resolution system like I described above? I see only benefits, and I see many downsides with your suggested approach, with no benefit over the module resolution system.

@mrjones2014 Well this way it's too simplified. It's going to be a nightmare if two different modules use the same name.
Btw, is there a way to detect whether legendary module is present or not?

@mrjones2014 Well this way it's too simplified. It's going to be a nightmare if two different modules use the same name. It also deprives user from a control over module system.

Any progress on this?
I have a question about package manager status intergration. Like, how would a third-party plugin check that Legendary.nvim is installed? In packer we can do:
local L = packer_plugins["legendary.nvim"]
if L and L.loaded) then
 ...
end

But what about the rest? It's not easy to detect...

Haven’t made any progress yet, I have been abroad in the Netherlands, so I haven’t had time to work on open source lately.

Looking into this again, we also need: https://github.com/nvim-tree/nvim-tree.lua/issues/1895

We could technically do it by re-binding the keymaps in nvim-tree's on_attach but then we'd be creating duplicate keymaps every time you open nvim-tree.

This should be possible now, by setting the keymaps generated to have filters = { fileytpe = 'NvimTree' }

@mrjones2014 Please add docs & examples on how to implement extensions. Thanks.

Filters are one of a few tools you can use. I consider the API unstable currently, as is noted in the docs. I’m still iterating in it, I will add thorough docs once I feel like it’s in a good place.

@mrjones2014 Flexibility may be achieved both by consumers and plugin-writers:
    -- init.lua
    local PluginA = require("cool/legendary/extensionA")
    local PluginB = require("cool/legendary/extensionB")
    local PluginC = require("myExtensions/legendary/keymaps")

    legendary.plugins:add(PluginA)
    legendary.plugins:add(PluginB)
    legendary.plugins:add(PluginC)
    legendary.plugins:add({
        name = "foo-keymaps"
        init = function(legendaryApi) ... end
    })

That's a lot less ergonomic than just being able to do:
require('legendary').setup({
  plugins = {
    plugin_a = true,
    plugin_b = true,
  },
})

It also potentially breaks lazy-loading setups.
Is there any actual downside to a module resolution system like I described above? I see only benefits, and I see many downsides with your suggested approach, with no benefit over the module resolution system.

This is the composition vs configuration as convetion approach.
ruby on rails went down the latter. you'll end spending the rest of your life tweaking offical default configs due to n+inifity requests in tickets.
I mean, you should step back and rexamine what it really is you're trying to achieve:

cool plugin system?
a super god like config convention that's tricky: "lol i anticipated every possible edge case, so just put yourpluginname = true"
registering other plugins keymaps so the user has superior UX?

I dare say the actual goal here is :

registering other plugins keymaps so the user has superior UX?

In which case, have you discussed monkey patching the nvim keymap functions so you catch all and any keymaps?

a super god like config convention that's tricky: "lol i anticipated every possible edge case, so just put yourpluginname = true"

Tells me you have not bothered reading the documentation or look at the actual implementation that was merged, so that's super cool. Only a moron could think they've anticipated every possible edge case.

registering other plugins keymaps so the user has superior UX?

Yes that's the goal.

have you discussed monkey patching the nvim keymap functions so you catch all and any keymaps

This decreases control, it doesn't tell us the source of a keymap, and it doesn't allow users to have some but not all keymaps in their legendary.nvim config. Sometimes you don't want everything in the finder, just the stuff you don't use all the time or don't always remember the keymap or command.
 I just came from Telescope.nvim and can already tell you how bad it is. It would be a major design flaw.
Thanks.


[Network] az network application-gateway rewrite-rule create: support url configuration

History Notes:
(Fill in the following template if multiple notes are needed, otherwise PR title will be used for history note.)
[Component Name 1] (BREAKING CHANGE:) (az command:) make some customer-facing change.
[Component Name 2] (BREAKING CHANGE:) (az command:) make some customer-facing change.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

Context?

Fix #12088


Typo on IRP Page

There is a typo on the I/O Request Packets page.
At the bottom of the page, there is a section that says I/0 (zero).

The IRP structure is self-contained in the sense that it holds all of the information that a driver needs to handle an I/0 request.

Proposed fix in #76.

Fixed in #76.


fix(12365): Add formatter option "insertSpaceAfterTypeAnnotation"

Adds an option to insert/remove space after the type annotation colon:
// true or undefined
let obj: { a: string, b: number } = { a: "a", b: 1 };

// false
let obj:{ a:string, b:number } = { a: "a", b: 1 };

First contribution, so I'm definitely not familiar with the codebase.
There can be places I missed that I have to change as well to add the new formatter option.
Fixes #12365

The introduction of a new optional property readonly insertSpaceAfterTypeAnnotation?: boolean to

ts.FormatCodeSettings in src/services/types.ts
ts.server.protocol.FormatCodeSettings in src/server/protocol.ts

causes these two errors:

     unittests:: Public APIs
       for the language service and compiler
         should be acknowledged when they change:
 Error: The baseline file api/typescript.d.ts has changed.

     unittests:: Public APIs
       for the language server
         should be acknowledged when they change:
 Error: The baseline file api/tsserverlibrary.d.ts has changed.

What should I be doing?

@wise0704

npm test
npm run gulp -- baseline-accept
commit and push

I'll check with the team, but unless we decide to add this in the next couple of weeks, I'm going to close this PR. We can re-open it if we accept the originating bug.

I'm closing this since we decided not to accept the bug.

I'm closing this since we decided not to accept the bug.

May I know the reason for rejection? Because it seems like a very useful feature people have been asking for that can be implemented with no breaking changes.

Oops, I thought that we already posted the results of our discussion. I'll do so back on the original bug.


[No JIRA] force_destroy was not configured for gke buckets

GCP buckets did not have the option to toggle force_destroy
Also an update to the S3 bucket tagging to reflect the state of force_destroy

good callout @lloydChris

good callout @lloydChris


Tests using toString on a run-time type cannot work with minification

The following tests in sdk/tests/language_2 use e.toString() to get a string representation of a given run-time type (e has type Type), and compares the result to string literals:
cyclic_type2_test
cyclic_type_test/0*
f_bounded_quantification5_test
generic_closure_test
mixin_mixin2_test
mixin_mixin3_test
mixin_mixin4_test
mixin_mixin5_test
mixin_mixin6_test
mixin_mixin_bound2_test
mixin_mixin_bound_test

As mentioned in issue #12605, no guarantees are given for the return value of toString, including the one on Type, and in particular the output looks very different for user-defined classes and for the class Map in $minified mode.
Only generic_closure_test avoids user-defined classes and Map, so it may work, but the others will inherently fail with $minified.
This issue exists to make sure this situation is known, and it may be used to track an update to the tests (if that's given priority). I haven't given the issue area-dart2js because this is a problem with the tests, not with dart2js.

Note that #31053 was created in response to the same problem that this issue addresses, and it was closed because this issue subsumes #31053.


UT for route pkg

Added unit tests for 2 functions in route.go
This is an update to Janki's original patch here:
https://github.com/rancher/submariner/pull/44
Signed-off-by: Janki Chhatbar<EMAIL_ADDRESS>

@Jaanki can you have an eye ^ ?

LGTM :)


Update plugin versions because of @threadSafe

The newer plugin versions support a @threadSafe build, e.g.:
mvn -T 1C package
The only non-threadsafe plugins left are:
[WARNING] The following goals are not marked @threadSafe in Google Guice - Core Library:
[WARNING] org.sonatype.plugins:jarjar-maven-plugin:1.9:jarjar
[WARNING] org.sonatype.plugins:munge-maven-plugin:1.0:munge-fork
But those seem to work correctly, maybe they are already threadsafe but
not explicilty marked as so...

Hi Sam,
any update on this?

I guess this is another dead open source project then?

dead

12 commits were pushed to master three days ago

Hi,
I rebased my branch on top of current master. See 9fd2d78 in above time line. sadly the rebase doesn't trigger a CI build.
So, would be cool if somebody could have a look at this PR and may pull it.


Double? -> int? example in readme doesn't work

org.clojars.akiel/spec-coerce {:mvn/version "0.4.0"}
org.clojure/spec.alpha {:mvn/version "0.2.176"}
Clojure 1.10.0 ; JVM
(require '[spec-coerce.alpha :refer [coerce]])
(require '[clojure.spec.alpha :as s])

(s/def ::x double?)

(spec-coerce.alpha/coerce (s/keys :req [::x]) {::x 1})
=> :clojure.spec.alpha/invalid

(spec-coerce.alpha/coerce (s/keys :req [::x]) {::x "1"})
=> #:user{:x 1.0}

Thanks for reporting. Do you need a release?


Discuss where tests will be run

The design doc describes running tests on LUCI, however this involves a few bits of custom work that aren't applicable to running the tests elsewhere, including using CIPD for distributing browsers and webdrivers, and setting up recipes. If forkability is a key focus, we may want to re-evaluate where tests will be run.
Right now all tests are being run on a VM @jeffcarp set up as a stepping stone.
cc @bobholt @foolip

Quoting myself from an old email:

Technology choices are not something I feel strongly about, as long as the end result is reliable.
However, it should be fairly easy to set up a new instance of the running infrastructure and dashboard including historical data. This adds credibility to the project, as neither Google nor Bocoup will be a gatekeeper.

In other words, we'd like forkability, and I think this implies that even if it's possible to run tests on LUCI, it should at the very least be possible to do the same on public infrastructure, in the simplest case physical, dedicates machines running the requisite OSes.


Create a new thread for each client connection

Currently, the server is not creating a new thread for each client connection. This means that the server can only handle one client at a time. To improve the server's functionality, we need to create a new thread for each client connection. This will allow the server to handle multiple clients simultaneously.
By creating a new thread for each client connection, we will improve the server's performance and responsiveness. Clients will be able to connect to the server without experiencing any delays, and the server will be able to handle all incoming requests efficiently.

This has been implemented in f3f444f, merged in #27


chore(stable): Bump stable to 2.5.5

:tada: This PR is included in version 2.5.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bug fix/update ui node dependencies

This PR fixes some issues during the ui grunt build process.

updated node modules
changed some eslint issues
slightly changed the libs.min.js generation process

Do not merge right now. This issue appeared in devel & 3.4 branch.
There are issues with the concat or uglyfying of libs.js. We need to inspect differences between libs between versions 3.3 and 3.4. So maybe we could fix this issue cleaner than mentioned above.

Ready to merge now. Please test if build process is working as expected.


cannot import name 'LabelStudioMLBase' from 'label_studio.ml'

https://labelstud.io/tutorials/sklearn-text-classifier.html
I tried to follow the steps linked above, type label-studio-ml init my_backend in CMD, and get this error.
cannot import name 'LabelStudioMLBase' from 'label_studio.ml'

To build my own machine learning backend, I need to write two scripts, right? Corresponds to _wsgi.py and simple_text_classifier.py in the example

@abu2wu

Label Studio ML backend was moved to a new repository: https://github.com/heartexlabs/label-studio-ml-backend , you need to install it separately.
You have to write simple_text_classifier.py only and then run label-studio-ml init --script simple_text_classifier.py

Hi, @abu2wu ! Please feel free to reopen the issue if you still have not succeeded to run the ML backend


Unable to load PayForm storyboard from framework

When I try to run the sample code in the README, I get this error:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Could not find a storyboard named 'PayForm' in bundle NSBundle </Users/{USERNAME}/Library/Developer/CoreSimulator/Devices/B86BCF6C-913C-4509-9946-5CACC35CB812/data/Containers/Bundle/Application/6240778F-24EB-439C-938F-6ACC84FA9827/payformtest.app/Frameworks/PayForm.framework> (loaded)'
I tried this in a new/empty swift project. The PayForm framework was added through cocoapods as directed in the README.

If you want I'd be happy to look at your project to see if I can find the issue. Conversely, I have a test project that pulls in PayForm via CocoaPods that I could tar up and send you to use to compare with.
BTW... I just updated to Xcode 8 and am considering if updating the code base to Swift 2.3 or 3.0 is best. Do you have any thoughts on the matter?

I uploaded the sample that crashes here: https://github.com/CBDev1/PayFormSimpleTest
My opinion is objective-c for best compatibility. Don't have to rely on a specific xcode version, don't have to keep updating syntax, etc ;o) As for which Swift version, I have no opinion since I am personally waiting for ABI stability before updating any of my code

Current workaround

In XCode, click on Pods > Pods > PayForm > Resources > PayForm.storyboard
Under Target Membership, check PayForm
Clean and build

0.3.2 should resolve this issue.

Closing as user appears to be unblocked with the latest fix

Unfortunately this did not solve my issue, and the workaround does not work anymore.
New error, it appears it is now looking for the storyboard in the main bundle instead of the PayForm cocoa pod:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Could not find a storyboard named 'PayForm' in bundle NSBundle </Users/{USERNAME}/Library/Developer/CoreSimulator/Devices/B86BCF6C-913C-4509-9946-5CACC35CB812/data/Containers/Bundle/Application/3074A088-3C8B-4C11-A556-CD603DBDE2B6/{APPNAME}.app> (loaded)'

Never mind, my bug. I forgot to change the bundle back after updating to the newest version of PayForm like it shows in the Readme:
let bundle = NSBundle.init(forClass: PayFormViewController.classForCoder())

Hmmm, not fixed after all. In order to get it to work in my project, I also need to change this line in the PayForm library.
PayFormViewController.swift line 131
From:
let storyboard = UIStoryboard(name: "PayForm", bundle: nil)
To:
let storyboard = UIStoryboard(name: "PayForm", bundle: NSBundle(forClass: self.classForCoder))


Add TextField triple tap gestures

This PR adds the following triple tap gestures to select text in a TextField.

Triple tap to select a paragraph in multi-line text fields.
Triple tap to select all text in single-line text fields.
Triple click + drag to select text in paragraph blocks.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

@tgucio sorry this wasn't ready for review. This depends on another PR so some files are not related to this one. Appreciate the feedback nonetheless :)

@Renzo-Olivares this is a very welcome PR so I thought I'd share review comments early but it looks like I missed the "Draft" status :).

This is ready to review with a caveat: I'm still addressing an edge case where the CupertinoTextSelectionControls selection handles blocks the TextSelectionGestureDetector below it. This will happen when the tap begins at a word edge, on double tap the selection handles will pop up and block the gesture detector below it, so the triple tap is never registered.

Tests currently failing due to #120629

Friendly bump, still looking for a review. The failing tests should clear up when https://github.com/flutter/engine/pull/39693 is merged

Can you explain again (or link me) why hiding the handles until kDoubleTapTimeout after the double tap wasn't viable? I think this solution is pretty clean, but I want to make sure if we're going to be adding new public API to support it.
Otherwise my comments are pretty small stuff.

I thought the delay was a bit too noticeable, especially since the highlight pops up on double tap as well.

Delay
No Delay

https://user-images.githubusercontent.com/948037/225496077-ae13f2fd-c01d-4862-8634-8650070a03cf.mov
https://user-images.githubusercontent.com/948037/225496087-4b0a3071-7609-4c00-b60a-4f8b4b4179d9.mov


Update the dependencies on package.json

This module require another module called load-json. You should update the package.json

Thanks!


WIP Closed Job Poster Apply Button

I fixed the conflicts, but Josh should take one last look at styling.

The button is now grey and I altered the cursor to be an arrow instead of pointer.


[EMB-124] TypeScript linting

Purpose
Better linting, better life.
Summary of Changes

Adds the following devDependencies:

tslint-consistent-codestyle for best practices
tslint-eslint-rules for tslint rules that are similar to the eslint rules
typescript-eslint-parser Gvies eslint the ability to parse TypeScript

Updates eslint and tslint configurations to adjust for TypeScript

Side Effects / Testing Notes
Minor code style changes, no functional or user-facing changes.
Ticket
https://openscience.atlassian.net/browse/EMB-124
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Coverage remained the same at 0.0% when pulling 3ff85b248e6f94624f7eb80c6819100a626c7cbf on feature/typescript into f220b95c9a4bc6a8f26837f5ef9d58a6a27c1395 on develop.


Coop leaderboards are broken: sim modded games counts

Just check out the  # 1  replay of 5th mission (Mind Games, 23m 40s by pobus)
You'll see this:

This guy obvsiously have sim mod (resourses x1000000 or something like that)
So leadebord has no meaning because of this bug, need to fix & clear leaderboard from modded replays somehow

Can you please post the replay id

Can you please post the replay id

I cant for now (yesterday was banned for smurfing, for a week)
Can give you replay file
temp.coop.zip
Is has "uid": 15440072 . But may be this is user id, not the replay id?
at least it has "launched_at":<PHONE_NUMBER>.0, "game_end":<PHONE_NUMBER>.0, its possible to find replay id by setting the date interval in the search
Replay from pobus, approximately from the september 2021, if i not mistaken

Thanks, yea that’s the replay id

It is server issue


Expose API for calling functions with already serialized arguments

Since .NET can't really pass a bson array from managed to native, we serialize it to string, then deserialize it in the C layer, only for OS to then serialize it again. It would be nice if OS exposed an API to call a function with pre-serialized string as opposed to a bson array. Similarly, it would be nice if the callback of this API used a string instead of the bson type.

Moved to https://github.com/realm/realm-core/issues/4182


Customer information within screenshot

Hi,
within the screenshot directly beneath the URL https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/threat-explorer?view=o365-worldwide#threats-in-urls we can see a customer name. Should be removed, I think. Visible in the URL samples and the MessageID

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

ID: c67966fc-41a2-d368-3ec9-e74768984af4
Version Independent ID: e2b8c076-e23b-4141-dbe1-62d984e6a87a
Content: Threat Explorer and Real-time detections - Office 365
Content Source: microsoft-365/security/office-365-security/threat-explorer.md
Product: m365-security
Technology: mdo
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

@myfope Thank you for your feedback. We have removed customer information from the screenshot. This can be tracked via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/5405
Thanks
Sri

@MSFTTracyP Please merge the PR #5405

@KCCross PR merge request pending. Thanks

Fixed.
https://github.com/MicrosoftDocs/microsoft-365-docs-pr/pull/12149
Closing


Update de_CH.json

What happens here :D

The wrong branch?
Von meinem iPhone gesendet

Am 25.09.2017 um 20:36 schrieb Diego Najar<EMAIL_ADDRESS>What happens here :D
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Merge packaging tool  into master.

Now that the 2019.4 beta is out, merge this into master.

Hi, @pvanderknyff! Thanks for opening this PR!

In the file connector-packager/connector_packager/helper.py:

Line 19:22: E127 continuation line over-indented for visual indent
Line 15:37: E226 missing whitespace around arithmetic operator
Line 9:1: E302 expected 2 blank lines, found 1

In the file connector-packager/connector_packager/jar_jdk_packager.py:

Line 113:61: E226 missing whitespace around arithmetic operator
Line 113:32: E226 missing whitespace around arithmetic operator
Line 8:1: F401 '.connector_file.ConnectorFile' imported but unused

In the file connector-packager/connector_packager/jar_jdk_signer.py:

Line 30:36: E226 missing whitespace around arithmetic operator

In the file connector-packager/connector_packager/xml_parser.py:

Line 164:121: E501 line too long (129 > 120 characters)
Line 164:52: E222 multiple spaces after operator
Line 163:121: E501 line too long (143 > 120 characters)
Line 153:121: E501 line too long (149 > 120 characters)
Line 126:9: F841 local variable 'schema' is assigned to but never used
Line 29:31: E262 inline comment should start with '# '
Line 29:30: E261 at least two spaces before inline comment
Line 28:28: E261 at least two spaces before inline comment
Line 27:31: E261 at least two spaces before inline comment
Line 14:1: E302 expected 2 blank lines, found 1
Line 12:121: E501 line too long (129 > 120 characters)
Line 4:41: E231 missing whitespace after ','
Line 4:1: F401 'defusedxml.ElementTree.ParseError' imported but unused

In the file connector-packager/connector_packager/xsd_validator.py:

Line 110:121: E501 line too long (139 > 120 characters)
Line 107:5: E722 do not use bare 'except'
Line 75:1: E302 expected 2 blank lines, found 1
Line 7:1: F401 '.connector_file.ConnectorFile' imported but unused
Line 5:1: F401 'xmlschema.validators.exceptions.XMLSchemaException' imported but unused

In the file connector-packager/tests/__init__.py:

Line 8:38: E231 missing whitespace after ','

In the file connector-packager/tests/jar_packager.py:

Line 60:29: W605 invalid escape sequence '\j'
Line 52:49: W605 invalid escape sequence '\p'
Line 52:41: W605 invalid escape sequence '\p'
Line 52:33: W605 invalid escape sequence '\s'
Line 52:30: W605 invalid escape sequence '.'


adding 2 Similar Sites in 2 different region

Hello friends,
I have two sites located in two different regions that have similar names. When I tried to add the second site, I received an error message stating that the site name already exists.
Is this impossible or have I missed something here?

Hello, I think that is an NetBox issue not something about the Plugin NBRisk.


Azure Pipelines token-less integration not working

I am trying to use CodeCov with Azure Devops Pipelines and I am not able to get the tokenless authentication working.
When I run the bash uploader I get the following error:
https://dev.azure.com/vowpalwabbit/Vowpal Wabbit/_build/results?buildId=7919&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=9c939e41-62c2-5605-5e05-fc3554afc9f5&l=27177
==> Uploading reports
    url: https://codecov.io
    query: branch=merge&commit=4c0ba2d79c63569605e85e5e12bf2ff7c9cadc47&build=20200404.18&build_url=https%3A%2F%2Fdev.azure.com%2Fvowpalwabbit%2FVowpal%20Wabbit%2F_build%2Fresults%3FbuildId%3D7919&name=&tag=&slug=VowpalWabbit%2Fvowpal_wabbit&service=azure_pipelines&flags=&pr=2385&job=7919&project=VowpalWabbit&server_uri=https://dev.azure.com/vowpalwabbit/
    -> Pinging Codecov
https://codecov.io/upload/v4?package=bash-tbd&token=secret&branch=merge&commit=4c0ba2d79c63569605e85e5e12bf2ff7c9cadc47&build=20200404.18&build_url=https%3A%2F%2Fdev.azure.com%2Fvowpalwabbit%2FVowpal%20Wabbit%2F_build%2Fresults%3FbuildId%3D7919&name=&tag=&slug=VowpalWabbit%2Fvowpal_wabbit&service=azure_pipelines&flags=&pr=2385&job=7919&project=VowpalWabbit&server_uri=https://dev.azure.com/vowpalwabbit/
HTTP 400
Unable to locate build via Azure API. Please upload with the Codecov repository upload token to resolve issue.

I have tried this in a PR build from a fork as well as a push triggered build on a branch on the main upstream repo.
I also tried setting CODECOV_TOKEN (which I would really like to avoid), and I get a different error:
https://dev.azure.com/vowpalwabbit/Vowpal Wabbit/_build/results?buildId=7952&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=9c939e41-62c2-5605-5e05-fc3554afc9f5&l=27178
==> Uploading reports
    url: https://codecov.io
    query: branch=merge&commit=89b8cb1f099e85a09d2fd298a5c2234d12f0829d&build=20200405.2&build_url=https%3A%2F%2Fdev.azure.com%2Fvowpalwabbit%2FVowpal%20Wabbit%2F_build%2Fresults%3FbuildId%3D7952&name=&tag=&slug=VowpalWabbit%2Fvowpal_wabbit&service=azure_pipelines&flags=&pr=2385&job=7952&project=VowpalWabbit&server_uri=https://dev.azure.com/vowpalwabbit/
    -> Pinging Codecov
https://codecov.io/upload/v4?package=bash-tbd&token=secret&branch=merge&commit=89b8cb1f099e85a09d2fd298a5c2234d12f0829d&build=20200405.2&build_url=https%3A%2F%2Fdev.azure.com%2Fvowpalwabbit%2FVowpal%20Wabbit%2F_build%2Fresults%3FbuildId%3D7952&name=&tag=&slug=VowpalWabbit%2Fvowpal_wabbit&service=azure_pipelines&flags=&pr=2385&job=7952&project=VowpalWabbit&server_uri=https://dev.azure.com/vowpalwabbit/
HTTP 400
Provided token is not a UUID.

Also currently a bit stuck on this. Recently migrated to Azure Pipelines from Travis, used to work seamlessly there. 😕
Example build for the first error here.
I get the second error on PRs from forks only — not on PRs I open myself. Seems like the solution would be making secrets available to forks, but I'd really like to not have to do that either.

Just managed to make it work by specifying -C $(Build.SourceVersion):
bash <(curl -s https://codecov.io/bash) -C $(Build.SourceVersion)

Seems like Azure creates a temporary merge commit (visible in the "Checkout" step) which confuses with Codecov.

I tried using that and I still get the same error:

Unable to locate build via Azure API. Please upload with the Codecov repository upload token to resolve issue.

I have no visibility it seems as to what is causing it not to be found.

I'm hitting the same error and, like jackgerrits, "-C $(Build.SourceVersion)" did not help.

Hi all, apologies for the delay in getting to this issue. However because of the age of the issue, I'm going to close out, but if it's still an issue, please open a ticket in our community boards.

Heads up everyone, bash <(curl -s https://codecov.io/bash) -C $(Build.SourceVersion) only works when your Azure Devope Project is Public and pipeline belongs it. If is already Private, just delete/disable it and make a Public one. Hope it helps.


Broken link of image, on edit page of attribute in case of Swatch Type "Image" when editing first time.

Framework Version: 0.1.4

Framework Version: 0.1.4
Not fixed

Fixed


iOS version

Is the iOS version planned? Technically, this should be possible, since the project is written in React Native.

Yes sometimes next year. Will need to look after some help to get it done.

Great!
I tried to build from the source by myself and I faild. The whole Xcode thing is a total mess :-/

Agree. Some of the libs I use require tweaks to xcode project, needs to be done one by one. No showstoppers, I chose the deps so that they do not have blocking issues on iOS.
Matter of strong will and enough time to kick it until it works.
Had a smart young student helping me spring and summer but he got admitted to fairly serious math uni from this sept and is out of any free time as of now...
Will likely need to look for another one, not sure anybody will just volunteer for a task like this. Not a fan of iOS from dev POV.

Have you thought about introducing Expo to the project or you want to keep it lean?
It is an extra dependency, but simplifies cross-platform development a lot.

Did one previous project using Expo and decided to drop it from this one. Staying lean was one motivation, step out of the pace of mandatory upgrades was the second and did not want to invest time to learn their new build tooling. As well, somehow could not get rid of bundled facebook trackers before, but they may be fixed that one, as they decomposed many libs to separate packages over time.


A better way to copy dependency of modules

Currently when a module reference to packages. By default, these packages are not being copied to the build output and cause the module cannot load these dependencies.
The temporary workaround is set true. However this CopyLocalLockFileAssemblies set to true, too many system assemblies are copied to the build output also.
We want to copy only packages that we explicitly referenced, not assemblies are bundled with AspnetCore

This will be tracked in #570

In development, we can set CopyLocalLockFileAssemblies to true OR set isBundledWithHost to true and add project reference in the WebHost. To publishing a module as self contained, use dotnet publish

I got ten of these emails saying the same thing today and i unsubscribed. Next step is this
[cid:A373595C-0AA3-480C-8250-95A4E02CBA4D]
On Oct 1, 2018 at 6:16 PM, <Thien Nguyen Le<EMAIL_ADDRESS>wrote:
In development, we can set CopyLocalLockFileAssemblies to true OR set isBundledWithHost to true and add project reference in the WebHost. To publishing a module as self contained, use dotnet publish
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/simplcommerce/SimplCommerce/issues/227#issuecomment-426082529, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Apk8sFEm_DhGC2RuUL7k0KOPwVP3RCYhks5ugpQ_gaJpZM4Ob1ET.

@kenc82 Please unwatch this project and stop posting similar comments. You should learn how to use GitHub first


Feat:  "Username" as well as "Confirm Password" in the sign up page

Describe the feature
Want to add "Username" as well as "Confirm Password" in the sign up page
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@sailaja-adapa here,close this issue since you merged it


route53-ACME DNS01 challenge:  certificate provisioned correctly, but cert-manager spins forever looking for DNS propagation

I am able to create a certificate using the DNS01 challenge in AWS with route53.
I can see the TXT record created:
dig _acme-challenge.console-openshift-console.apps.cluster-2d3c.sandbox37.opentlc.com TXT

; <<>> DiG 9.11.8-RedHat-9.11.8-1.fc30 <<>> _acme-challenge.console-openshift-console.apps.cluster-2d3c.sandbox37.opentlc.com TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61329
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;_acme-challenge.console-openshift-console.apps.cluster-2d3c.sandbox37.opentlc.com. IN TXT

;; ANSWER SECTION:
_acme-challenge.console-openshift-console.apps.cluster-2d3c.sandbox37.opentlc.com. 10 IN TXT "qcmZDQz-uTddq7VcqeYwMz05q5QtnoERwasfXODu8qc"

;; Query time: 64 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Fri Jul 26 13:19:31 EDT 2019
;; MSG SIZE  rcvd: 166

and I get tls material in a secret. yet cert-manager spins forever saying that it cannot check the dns propagation. see log
I0726 17:41:17.595288       1 controller.go:198] cert-manager/controller/orders "level"=0 "msg"="syncing resource" "key"="openshift-console/console-1399319360"
I0726 17:41:17.595472       1 sync.go:274] Need to create 0 challenges
I0726 17:41:17.595485       1 sync.go:319] Waiting for all challenges for order "console-1399319360" to enter 'valid' state
I0726 17:41:17.595512       1 controller.go:204] cert-manager/controller/orders "level"=0 "msg"="finished processing work item" "key"="openshift-console/console-1399319360"
I0726 17:41:17.595542       1 controller.go:213] cert-manager/controller/challenges "level"=0 "msg"="syncing resource" "key"="openshift-console/console-1399319360-0"
I0726 17:41:17.595647       1 dns.go:112] Checking DNS propagation for "console-openshift-console.apps.cluster-2d3c.sandbox37.opentlc.com" using name servers: [<IP_ADDRESS>:53]
E0726 17:41:17.671868       1 sync.go:180] cert-manager/controller/challenges "msg"="propagation check failed" "error"="NS ns-1536.awsdns-00.co.uk.:53 returned REFUSED for _acme-challenge.console-openshift-console.apps.cluster-2d3c.sandbox37.opentlc.com." "dnsName"="console-openshift-console.apps.cluster-2d3c.sandbox37.opentlc.com" "resource_kind"="Challenge" "resource_name"="console-1399319360-0" "resource_namespace"="openshift-console" "type"="dns-01"
I0726 17:41:17.678220       1 controller.go:219] cert-manager/controller/challenges "level"=0 "msg"="finished processing work item" "key"="openshift-console/console-1399319360-0"

I am using: quay.io/jetstack/cert-manager-controller:v0.8.1
/kind bug

"msg"="propagation check failed" "error"="NS ns-1536.awsdns-00.co.uk.:53 returned REFUSED

Try to change DNS server.
You can use --dns01-recursive-nameservers flag .

I changed DNS and it worked. I assume in AWS one would use the internal DNS, but it seems like the name propagation  never reached it. Is there a reason to that? Would it make sense to document this behavior.

I'm running into this with an on-prem Rancher v2.2.7 cluster, the resolver is using some DNS server in the 10.x.x.x address space and spinning forever. If I manually set the DNS server with --dns01-recursive-nameservers=<IP_ADDRESS>:53 it does work.
The problem for me is that this requires a manual tweak of the running service since I installed with the command kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/${CERT_MANAGER_VERSION}/cert-manager.yaml. Perhaps the could be some environment variables that are used by default?

@msnelling I believe I have the same or a similar issue (using Rancher 2.3.0 and cert-manager 0.11.0, installed from the cert-manager.yaml file). I create a certificate, but the propagation never finishes. The cert-manager controller log just says "msg"="propagation check failed" "error"="DNS record for \"mydomain.io\" not yet propagated" I'm using an acme-dns server for the challenge.
What is the full command in which you used the flag --dns01-recursive-nameservers? The doc mentions that the controller exposes that flag, but I'm a bit of a K8s noob and don't fully understand how to use said flag.
(I can create a separate issue if needed. It's possible that this is a bug in cert-manager's integration with acme-dns.)

I could resolve this issue just by recreating the cert-manager pod. It is running v0.11.0. So it seems to be an issue inside the cert-manager application and not a nameserver problem.

On OpenShift 4.3 using AWS there are likely two hosted records - one public and one private. cert-manager doesn't necessarily infer which one is appropriate, but the ACME DNS record must be in the public hosted record.

this issue is still open for me. It affects deployments via OLM, in which the arguments cannot be changed. It would be interesting to understand how the resolver is picked when running in AWS. For example I'm running in the us-west region and cert-manager is trying to use this resolver: ns-0.awsdns-00.com  but sometimes if I restart the cert-manager pod it uses: ns-512.awsdns-00.net.
An improvement would be to be able to pass the resolver as environment variables. A further improvement would be to let the user specify the resolver in the resolvers.dns01 section.


Publish to packagelist when done

Not done, but https://packagist.org/packages/jsonrpcbitcoin/jsonrpcbitcoin


issue/7325-release-tool-version-tag (#7489)

Pull request opened by the merge tool on behalf of #7489

Merged into branches iso7 in 6d20843891d06609ff7c1eca560827f0ed9cd4b9


Add OnTransition::Any that runs on any change to the state S

Objective
I want to be able to run a system in between OnExit and OnEnter that runs on any change to the state. This can be useful if, for example, you want to cover all the possibilities of the transition with a match statement.
Solution

Replace the OnTransition { from, to } schedule with an enum:

enum OnTransition {
    Any,
    Exact { from, to },
}

Add the StateTransition resource that is made available by the apply_state_transition system during the transition. This can be used to access the exiting and entering states.

Open Questions

Currently the StateTransition resource is made available to all of OnExit/OnTransition/OnEnter. Maybe it should only be made available for OnTransition?

Changelog
TODO: ...
Migration Guide
// old
OnTransition { from: MyState::A, to: MyState::B }

// new
OnTransition::Exact { from: MyState::A, to: MyState::B }

@lee-orr, following your work in https://github.com/bevyengine/bevy/pull/10088 I'm really curious about what you think of this design.
I'm fond of the simple incremental change. Still forming an opinion on the temporary resource 🤔 I think maybe it could be replaced by just looking at the current and next state resource that already exists?

Yeah, I am also not 100% sure about the temporary resource. But I think it is not really possible with the NextState<S> resource, as this contains an Option<S>, so users would always have to unwrap.
If I am not missing anything, at least it's quite clean, because nobody can create, clone or modify the StateTransition resource from outside. So misuse is difficult/not really possible.

Yeah, very nice encapsulation :) I think I'm on board with it now.

I think the design makes sense. There is actually a similar-ish temporary resource in #10088 - the ActiveTransition resource, which uses a tuple rather than being based on two fields. The only comment I'd have here is that it might be worth agreeing on an API for this so that we don't run into the need to change things later?
An option for that is to have the state transition resource expose a "from" and "to" function rather than methods, since that will make it relatively easy to replace ActiveTransition with it in a way that preserves ActiveTransition's additional functionality (the ability to swap ordering for some transition evaluation things).

Sorry! I meant methods rather than fields... I.e. abstract away how things are stored internally.

As for your second point - I think it might be better to have it present for the entire transition, but make the values Options.
This could allow a janky version of matching on enter/exit as well, where you check the resource for the outgoing/incoming value respectively

Okay, so for the methods vs fields: The fields are already private, so the methods are the only way to access them.
Regarding the ActiveTransition resource, can you explain what fields would then be set to Some/None for which schedule.
The one thing I really dislike about Options is that you would have to unwrap them in the OnTransition schedules. This is the point at which the resource would be most likely be used, and you would always need to unwrap guaranteed Somes.
And as I have already said, I think if you need the other state in your system, you should probably be in the OnTransition schedules and not in OnEnter/OnExit anyways.
Please feel free to disagree, it's just the way I currently see it:)

I disagree there, primarily on grounds of making the option explicit - I don't want people to find things crashing if they try to use a system for both OnTransition and OnEnter, for example - and OnEnter also runs the first time.
Another option is to default to having it be a transition where both states are identical if it's the first entrance/exit?

Can you give me an example where that would make sense? For me, the two are actually so different that I can't imagine what I would reuse.
The way I see it, OnEnter/OnExit are the standard choice to handle changing between different states of your app.
OnTransition only makes sense if you want to "prepare" something between Exit-Enter depending on the transition.
I think the root problem for providing the ActiveTransition resource to all schedules is the OnEnter run on the first time. There is simply no sensible previous state. I would also find it very unintuitive to simply use the same one. But then forcing an Option everywhere else doesn't feel right either.

OK - sorry, it took me a bit to respond...
I don't know why I was under the impression the resource exists during OnEnter/OnExit as well... It may have just been mis-remembering since that's what happens in #10088.
I think my concern really comes from how ActiveTransition from this PR would interact with the version in #10088. In that case it felt like the appropriate way to handle things was having an ActiveTransition object that exists across the entire transition rather than just during the "OnTransition" portion(I'll put fuller details of the reasoning in that PR below if you're interested, but it doesn't directly affect this one).
Given the currently available API's and what you are proposing, I think you are probably right. And since I don't know if/when #10088 will get merged, maybe we don't need to actually plan for a compatible API.

If you're interested - the reasons #10088 exposes ActiveTransition across all 3 transition schedules are:

When you are matching more than a single, discreet state, you might only want to match if the other state in the transition isn't part of the you are matching.

the classic example is App::InGame::Running and App::InGame::Paused - there are actions I want to take whenever I enter App:::InGame::*, like spawning the world, regardless of which it is - but only if we're not already in one of the matching states. Other things, like clearing the UI, I might want to do whenever I exit one of these states regardless of whether I'm moving to another matching state - since the HUD doesn't need to be visible while paused and vice versa.

The other reason is a bit weirder, but due to some ergonomic constraints that PR has untyped variations of OnEnter/OnExit (Entering and Exiting) and actually swaps the order of states in ActiveTransition between the two. This is primarily to allow one of the following: avoiding the need to declare the types in multiple places, allowing one state type to react to a transition in another state type, and allowing you to re-use types that match a transition in both directions. A "Transitioning" schedule used to exist as well, but it felt redundant since "Entering" and "Exiting" basically had the same impact - only with inverted matching.

One possible API compromise is doing something like this:
// This code is not actually valid or fully formed, it's just expressing the idea

ActiveTransition<S> {
 main: S,
 secondary: Option<S>,
 direction: TransitionDirection
}

enum TransitionDirection {
  Entering,
  Exiting
}

impl<S> ActiveTransition<S> {
  fn entering(&self) -> S {
     match self.direction {
      Entering => self.main,
      Exiting => self.secondary.unwrap_or(self.main)
     }
  }

  fn exiting(&self) -> S {
    match self.direction {
    Entering => self.secondary.unwrap_or(self.main),
    Exiting => self.main
    }
  }
}

Ok, thanks for the feedback.
I updated the PR description. From my point of view this is good to go. @alice-i-cecile @lee-orr

I also took a quick look at #10088: To be honest, it does offer some new/powerful possibilities, but it seems very complex to me and also has a lot of subtle cleverness hidden in it.

@jannik4 @alice-i-cecile - Should be able to close this at this point I think?


docs: add import instructions to component doc pages

just gonna merge and call it a day, comment later if there's anything


The following assertion was thrown during performLayout():

type '_InternalLinkedHashMap<String, dynamic>' is not a subtype of type 'BrandModel'

Unfortunately this is not enough information for us to diagnose the problem.
Please explain the steps how to reproduce.
Please also add the output of flutter doctor -v.
Is this related to JSON serialization?

this is my code:please help me.
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: Text('Top Animate Movies'),
),
body: formList == null
? Center(child: CircularProgressIndicator())
: Padding(
padding: EdgeInsets.symmetric(horizontal: 6.0, vertical: 10.0),
child: ListView.builder(
itemCount: formList.length,
itemBuilder: (BuildContext context, int index) {
return MyBrand(formList[index]);
},
),
),
);
}
It crash at  return MyBrand(formList[index]);

Please use StackOverflow or other channels like https://gitter.im/flutter/flutter for support questions.


Cookie support for automap

To-do:

[x] Handle TODO comments.
[x] Separate cookie parsing and formatting into a separate module that could eventually serve as a starting point for https://github.com/scrapy/scrapy/issues/5431
[x] Agree on the best way to handle max cookies.
[ ] Should we provide a workaround for https://github.com/scrapy/scrapy/issues/5841? Push for an upstream fix? Let things be for now?

Thanks @Gallaecio! I've checked all the changes, and can't spot any issue 👍  This is a complex feature, so we both might be missing something, but it'd be found in a real-world usage. So, let's proceed. Great work!


Set GameState in code sample to GameState{}

First of all, thank you for submitting a PR!
I don't think this change is necessary, however - in the example, GameState is a unit struct, which means that you do not need to use braces to instantiate it. I actually was not aware you could instantiate a unit struct with braces - I'd just assumed it'd be a compile error!
Personally, I would rather keep the symmetry between the struct's declaration and the creation of the instance, rather than having braces in one place and not the other. That said, I am considering changing the example in the future to be a bit more representative of real Tetra code, and that'll probably mean adding some fields to the struct.

No worries @17cupsofcoffee. Thanks for closing the PR!
Great project by the way!

🙂 Thank you for being understanding, never feels good to turn down a pull request!


[BUG] During volume live engine upgrage, if a newly migrating replica hit an error and stops, the volume stuck in upgrading forever

Describe the bug (🐛 if you encounter this issue)
During volume live engine upgrage, if a newly migrating replica hit an error and stops, the volume stuck in upgrading forever even if the reason that causes the replica error already resolved
To Reproduce
Steps to reproduce the behavior:

Install Longhorn v1.3.1 into a 3-nodes cluster
Create a volume and attach it to a node
Upgrade Longhorn to v1.3.2
Cordor a node
Kill the new instance-manager-r pod on the cordoned node (This manually triggers a instance-manager-r unavailable condition. A similar unavailable condition can happen when the new instance-manager-r has not been deployed yet and the user has enabled Concurrent Automatic Engine Upgrade Per Node Limit)
Upgrade the engine for the volume -> upgrade stuck because one of the newly migrating replica (the one on the cordoned node) hits error and stopped
Uncordoned the node, the instance-manager-r pod becomes running
However, the volume is stuck in the upgrading process forever

Expected behavior
the volume should retry and finish upgrading or simply rollback. It shouldn't be stuck in the between
Affected Longhorn version: v1.3.2

Workaround:

Rollback the engine upgrade to clean up the migrating replicas
Retry the engine upgrade

Workaround:

Rollback the engine upgrade to clean up the migrating replicas
Retry the engine upgrade

For a problematic volume, can do some retry and after that, if it's still unable to finish the engine upgrade successfully due to some env runtime issue somehow, can just cancel the upgrade for the volume, and then continue others like the best efforts. For users, there will be no interruption since they can still upgrade the current engine image when reattaching the volume. @PhanLe1010 WDYT?

Looks like we touch this issue at https://github.com/longhorn/longhorn-manager/pull/1533 So the fix should already exist in Longhorn v1.3.3-rc
cc @innobead

Perfect. Have u validated this again?

Perfect. Have u validated this again? @PhanLe1010
Cc @longhorn/qa

Yeah, I revalidated it. It doesn't stuck

Closing this in favor of https://github.com/longhorn/longhorn/issues/4726

@khushboo-rancher can you help retest this again? Would like to ensure this has been fixed by #4726 Thanks.
cc @longhorn/qa

This issue has been fixed as expected, closing. For another issue, we will just focus on testing #5684 .

While checking this I encountered a strange behavior, I logged a bug - https://github.com/longhorn/longhorn/issues/5729


No option to convert Saitama Inu old -> Saitama Inu v2

Currently, the Metamask, trust wallets have the option to change the smart contract address resulting the
migration of Saitama V2,
There is no option currently in the Ledger Live to do the same :(

Referring this
https://watcher.guru/news/how-to-migrate-tokens-to-saitama-v2
and this official tweet from Saitama Community
https://twitter.com/WeAreSaitama/status/1531463639445778432

Hey @dnsoumik,
Please pick an issue template and stick to it in the issue description. (also this sounds like a feature request)
Thanks.


Manifest 2.0 prototype

rough rebase of https://github.com/tomerd/swift-package-manager/tree/feature/manifest2-poc, doesn't work yet

Will first need to figure out the JSON parsing since this was all done using the old parsing code, then fix the test cases that were added for the new format. Once that's done we can make actual progress :)

JSON parsing is functional now, but not 100% complete and I restored the tests from the original PR.
I introduced a new module PackageManifestModel that contains symlinks to the files from PackageManifest so we can re-use the codable model objects for deserialization.
Since versioning is already a thing in the manifest for a bit now and we're up to version 2 already, I called the new version 3 now.

The use of variadics doesn't seem to work like it did anymore, not sure if that means we should change the APIs here:
error: fatalError
/Package.swift:24:22: error: cannot pass array of type '[String]' as variadic arguments of type 'String'
            .sources(["sources-1"])
                     ^
/Package.swift:24:22: note: remove brackets to pass array elements directly
            .sources(["sources-1"])
                     ^           ~"

@swift-ci please smoke test

@swift-ci please smoke test

Locally I am still seeing issues specifically with the new tests in bootstrap, the compiled manifest is not producing any output, but also not failing. Not sure yet what's different between the two environments.

The issue mentioned above reproduces on CI as well
Test Suite 'Selected tests' started at 2023-06-01 20:37:48.768Test Suite 'PackageDescriptionNextLoadingTests' started at 2023-06-01 20:37:48.770Test Case 'PackageDescriptionNextLoadingTests.testSample1' started at 2023-06-01 20:37:48.770[debug]: evaluating manifest for '' v. unknown
<EXPR>:0: error: PackageDescriptionNextLoadingTests.testSample1 : threw error "Invalid manifest (compiled with: ["/home/build-user/build/buildbot_incremental/toolchain-linux-x86_64/usr/bin/swiftc", "-vfsoverlay", "/tmp/TemporaryDirectory.kt50lY/vfs.yaml", "-L", "/home/build-user/build/buildbot_incremental/swiftpm-linux-x86_64/x86_64-unknown-linux-gnu/lib/swift/pm/ManifestAPI", "-lPackageDescription", "-Xlinker", "-rpath", "-Xlinker", "/home/build-user/build/buildbot_incremental/swiftpm-linux-x86_64/x86_64-unknown-linux-gnu/lib/swift/pm/ManifestAPI", "-swift-version", "5", "-I", "/home/build-user/build/buildbot_incremental/swiftpm-linux-x86_64/x86_64-unknown-linux-gnu/lib/swift/pm/ManifestAPI", "-package-description-version", "999.0.0", "/Package.swift", "-o", "/tmp/TemporaryDirectory.LG7W0V/-manifest"])
Missing or empty JSON output from manifest compilation for

I see the issue now, SERIALIZATION needs to be defined when building the PackageManifest module, but isn't in the CMake build.

Taking this out of draft since this should be working end-to-end now. I propose that we can land it like this in main to avoid another large rebase in the future, as long as its use is behind a 999.0 tools-version. That way we can iterate until we are happy enough with it to take it to Swift evolution.

@swift-ci please smoke test

@swift-ci please smoke test windows

We got past the test issue, but there seems to be an issue during install (which I didn't test locally):
--- bootstrap: note: Installing /home/build-user/build/buildbot_incremental/swiftpm-linux-x86_64/x86_64-unknown-linux-gnu/release/libPackageManifest.so to /home/build-user/build/buildbot_incremental/toolchain-linux-x86_64/usr/lib/swift/pm/ManifestAPI/libPackageManifest.so
Traceback (most recent call last):
  File "/home/build-user/swiftpm/Utilities/bootstrap", line 827, in <module>
    main()
  File "/home/build-user/swiftpm/Utilities/bootstrap", line 65, in main
    args.func(args)
  File "/home/build-user/swiftpm/Utilities/bootstrap", line 412, in install
    install_swiftpm(prefix, args)
  File "/home/build-user/swiftpm/Utilities/bootstrap", line 456, in install_swiftpm
    install_dylib(args, "PackageManifest", dest, ["PackageManifest"])
  File "/home/build-user/swiftpm/Utilities/bootstrap", line 465, in install_dylib
    install_binary(args, g_shared_lib_prefix + library_name + g_shared_lib_suffix, install_dir)
  File "/home/build-user/swiftpm/Utilities/bootstrap", line 495, in install_binary
    shutil.copy2(src, dest)
  File "/usr/lib/python3.8/shutil.py", line 435, in copy2
    copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
    with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: '/home/build-user/build/buildbot_incremental/swiftpm-linux-x86_64/x86_64-unknown-linux-gnu/release/libPackageManifest.so'

There's also a build issue on Windows:
C:\Users\swift-ci\jenkins\workspace\swiftpm-PR-windows\swiftpm\Sources\PackageManifest\Serialization\ManifestEncoding.swift:38:38: error: cannot find 'fileDescriptor' in scope
        guard let filePipe = _fdopen(fileDescriptor, "w") else {
                                     ^~~~~~~~~~~~~~
C:\Users\swift-ci\jenkins\workspace\swiftpm-PR-windows\swiftpm\Sources\PackageManifest\Serialization\ManifestEncoding.swift:39:20: error: cannot find 'fileDescriptor' in scope
            _close(fileDescriptor)
                   ^~~~~~~~~~~~~~

This should really be a draft

Seems like it is time to close this.


Discussion: Debugging

It's not an issue since I've been able to fix my problem, but... React Native JS debugging overall experience is very poor.
Consider this code:

That's some bad code and, of course, it throws an error. So far, so good. But that's the error:

And I solved it by using the following snippet:

Point is: .sort actually mutates the array instead of return a new copy. Ok, my mistake, I shouldn't be doing that way. But what useful message does the debugger returns for me? It says there's the specified error in Requests (assuming it is the component in question).
But what else? In which line? Which statement is causing the error? That stacktrace is not very specific. That was very hard to find out, turned out to be something very simple to fix but it cost me at least an hour.
That's just a "contrived" example, but that actually happens everywhere. Debugging in the JS core is a nightmare, in both iOS and Android. I literally have to comment code, do the trial-and-error method to find out what is going wrong and then fix it. What can be done to address this?

👋 there - we are aware of the problem and, in fact, there is already a discussion open in the dedicated repo: https://github.com/react-native-community/discussions-and-proposals/issues/69


llvmPackages_{12,13,14,15,16,17,18,git}.lldb: add patch to remove origin variable

Description of changes
Fixes #315214

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

the lines with ORIGIN should just get remove

No, I based the patch on the one we have for LLVM (pkgs/development/compilers/llvm/17/llvm/gnu-install-dirs.patch).

kgs/development/compilers/llvm/17/llvm/gnu-install-dirs.patch

yeah, that patch is wrong too -- in the llvm18 init it was fixed up a bit to remove $ORIGIN.

yeah, that patch is wrong too -- in the llvm18 init it was fixed up a bit to remove $ORIGIN.

Oh huh, I forgot I made that change when I made the LLVM 18 PR.

in general, it seems that anything using $ORIGIN that is exiting the derivation path should be removed. $ORIGIN/../lib is ok for binaries in /nix/store/.../bin/.  and maybe if there is some subdirectory, things might what $ORIGIN/lib-subdir for things in lib to reference lib/lib-subdir. but even many of those uses we add absolute RPATHS anyway so are mostly redundant.

Alright, I removed $ORIGIN.

this should get the backport release-24.05 label too

rpaths for LLVM12-18. looks like LLVM13 is still using $ORIGIN/../../../../lib for some reason.
patchelf --print-rpath $x|xargs -d : -n 1
$ORIGIN/..//nix/store/cxdbc9gkk08flmgvy070qdmnq0zppkij-lldb-12.0.1-lib/lib
///nix/store/wn3s8rxc7zv00ibj9gsj8f353yj4849s-llvm-12.0.1-lib/lib
/nix/store/7hnr99nxrd2aw6lghybqdmkckq60j6l9-python3-3.11.9/lib
/nix/store/x5mpg1pjazhvja8aq0yxig2zgz51i9c1-lua-5.3.6/lib
/nix/store/j4m3lwhh4x0bzilvi77d512ahry775nq-ncurses-6.4/lib
/nix/store/bmjckrv5ryxahvkldr47jyx7zmlrcan3-libedit-20230828-3.1/lib
/nix/store/kf7fzax0av9him9m4zcmbqmihh5108wq-libxml2-2.12.7/lib
/nix/store/k7zgvzp2r31zkg9xqgjim7mbknryv6bs-glibc-2.39-52/lib
/nix/store/xvzz97yk73hw03v5dhhz3j47ggwf1yq1-gcc-13.2.0-lib/lib
/nix/store/qhfk7hvngljfi8bck3b7rskl69h5xk8g-clang-12.0.1-lib/lib

$ORIGIN/..//nix/store/aici40kvdhlb4pmz2hrv2w60aclnc73k-lldb-13.0.1-lib/lib
///nix/store/lz8sjwcrfrk1jqmsrdm6ikrra5824y8z-llvm-13.0.1-lib/lib
$ORIGIN/../../../../lib
/nix/store/7hnr99nxrd2aw6lghybqdmkckq60j6l9-python3-3.11.9/lib
/nix/store/x5mpg1pjazhvja8aq0yxig2zgz51i9c1-lua-5.3.6/lib
/nix/store/j4m3lwhh4x0bzilvi77d512ahry775nq-ncurses-6.4/lib
/nix/store/bmjckrv5ryxahvkldr47jyx7zmlrcan3-libedit-20230828-3.1/lib
/nix/store/kf7fzax0av9him9m4zcmbqmihh5108wq-libxml2-2.12.7/lib
/nix/store/k7zgvzp2r31zkg9xqgjim7mbknryv6bs-glibc-2.39-52/lib
/nix/store/d4dzkmwkyrkc1l8z9x7vcdj193fx4g45-gcc-12.3.0-lib/lib
/nix/store/fvgyp8fqjkxif8gbab23h6dvgqi55sd8-clang-13.0.1-lib/lib

$ORIGIN/..//nix/store/wfr0lw9g3dragcyg8rnv1i064ncvwj93-lldb-14.0.6-lib/lib
/nix/store/lh3dq18c0a6d8nybvm9z68fr04vlq8w1-llvm-14.0.6-lib/lib
/nix/store/7hnr99nxrd2aw6lghybqdmkckq60j6l9-python3-3.11.9/lib
/nix/store/x5mpg1pjazhvja8aq0yxig2zgz51i9c1-lua-5.3.6/lib
/nix/store/j4m3lwhh4x0bzilvi77d512ahry775nq-ncurses-6.4/lib
/nix/store/lv6nackqis28gg7l2ic43f6nk52hb39g-zlib-1.3.1/lib
/nix/store/bmjckrv5ryxahvkldr47jyx7zmlrcan3-libedit-20230828-3.1/lib
/nix/store/kf7fzax0av9him9m4zcmbqmihh5108wq-libxml2-2.12.7/lib
/nix/store/k7zgvzp2r31zkg9xqgjim7mbknryv6bs-glibc-2.39-52/lib
/nix/store/xvzz97yk73hw03v5dhhz3j47ggwf1yq1-gcc-13.2.0-lib/lib
/nix/store/js44niygpsvdni002pjk7jx1yx4gr822-clang-14.0.6-lib/lib

$ORIGIN/..//nix/store/q8ypj9ymv55nv551nvhf7pirs9nw4yga-lldb-15.0.7-lib/lib
/nix/store/33drjrjajqv0xd7jg5hiq47pdwd641gh-llvm-15.0.7-lib/lib
/nix/store/7hnr99nxrd2aw6lghybqdmkckq60j6l9-python3-3.11.9/lib
/nix/store/x5mpg1pjazhvja8aq0yxig2zgz51i9c1-lua-5.3.6/lib
/nix/store/j4m3lwhh4x0bzilvi77d512ahry775nq-ncurses-6.4/lib
/nix/store/lv6nackqis28gg7l2ic43f6nk52hb39g-zlib-1.3.1/lib
/nix/store/bmjckrv5ryxahvkldr47jyx7zmlrcan3-libedit-20230828-3.1/lib
/nix/store/kf7fzax0av9him9m4zcmbqmihh5108wq-libxml2-2.12.7/lib
/nix/store/k7zgvzp2r31zkg9xqgjim7mbknryv6bs-glibc-2.39-52/lib
/nix/store/xvzz97yk73hw03v5dhhz3j47ggwf1yq1-gcc-13.2.0-lib/lib
/nix/store/k8m2f5rwb4ryx20cm1mjy1gmrfjbksc1-clang-15.0.7-lib/lib

$ORIGIN/..//nix/store/0jcgihrrjxhdy9lw2mgpyq3lazy3ja2s-lldb-16.0.6-lib/lib
/nix/store/gshzcbn5677fyp2g46wx49r7jdzsa05h-llvm-16.0.6-lib/lib
/nix/store/7hnr99nxrd2aw6lghybqdmkckq60j6l9-python3-3.11.9/lib
/nix/store/x5mpg1pjazhvja8aq0yxig2zgz51i9c1-lua-5.3.6/lib
/nix/store/j4m3lwhh4x0bzilvi77d512ahry775nq-ncurses-6.4/lib
/nix/store/lv6nackqis28gg7l2ic43f6nk52hb39g-zlib-1.3.1/lib
/nix/store/bmjckrv5ryxahvkldr47jyx7zmlrcan3-libedit-20230828-3.1/lib
/nix/store/kf7fzax0av9him9m4zcmbqmihh5108wq-libxml2-2.12.7/lib
/nix/store/px860gmf08bwx7cwdnilzscgp3540j8p-clang-16.0.6-lib/lib
/nix/store/k7zgvzp2r31zkg9xqgjim7mbknryv6bs-glibc-2.39-52/lib
/nix/store/xvzz97yk73hw03v5dhhz3j47ggwf1yq1-gcc-13.2.0-lib/lib

$ORIGIN/..//nix/store/cxzf6ryar2ldvdvm9ly33fifcmf05hmg-lldb-17.0.6-lib/lib
/nix/store/ax9wbqknwawnl21kvkp8l6jn2r6q0l90-llvm-17.0.6-lib/lib
/nix/store/7hnr99nxrd2aw6lghybqdmkckq60j6l9-python3-3.11.9/lib
/nix/store/x5mpg1pjazhvja8aq0yxig2zgz51i9c1-lua-5.3.6/lib
/nix/store/j4m3lwhh4x0bzilvi77d512ahry775nq-ncurses-6.4/lib
/nix/store/lv6nackqis28gg7l2ic43f6nk52hb39g-zlib-1.3.1/lib
/nix/store/bmjckrv5ryxahvkldr47jyx7zmlrcan3-libedit-20230828-3.1/lib
/nix/store/kf7fzax0av9him9m4zcmbqmihh5108wq-libxml2-2.12.7/lib
/nix/store/wxxgsgjxbnkkyczgf8lkbfrsqiywm8bi-clang-17.0.6-lib/lib
/nix/store/k7zgvzp2r31zkg9xqgjim7mbknryv6bs-glibc-2.39-52/lib
/nix/store/xvzz97yk73hw03v5dhhz3j47ggwf1yq1-gcc-13.2.0-lib/lib

/nix/store/yvk6901c28z1vpshzvp0z4qyxi274jlh-llvm-18.1.6-lib/lib
/nix/store/7hnr99nxrd2aw6lghybqdmkckq60j6l9-python3-3.11.9/lib
/nix/store/x5mpg1pjazhvja8aq0yxig2zgz51i9c1-lua-5.3.6/lib
/nix/store/j4m3lwhh4x0bzilvi77d512ahry775nq-ncurses-6.4/lib
/nix/store/lv6nackqis28gg7l2ic43f6nk52hb39g-zlib-1.3.1/lib
/nix/store/bmjckrv5ryxahvkldr47jyx7zmlrcan3-libedit-20230828-3.1/lib
/nix/store/kf7fzax0av9him9m4zcmbqmihh5108wq-libxml2-2.12.7/lib
/nix/store/5d52f93rlhp8xbjc94kycxfs70dbwna6-clang-18.1.6-lib/lib
/nix/store/k7zgvzp2r31zkg9xqgjim7mbknryv6bs-glibc-2.39-52/lib
/nix/store/xvzz97yk73hw03v5dhhz3j47ggwf1yq1-gcc-13.2.0-lib/lib

@paparodeo Fixed, LLVM 13 uses it's own separate patch for lldb like how LLVM 12 does.

Gentle ping - would love to get this in so bpftrace can fix its pipelines


MVP access to internal developers

Need
User story:

As a developer for matrix service, data browser, analysis
I want to query for HCA metadata in the query service
to answer questions I have about the metadata as it is stored in the DSS.

Approach
Open up access to internal developers.
TODO: add any gap requirements that arise as we approach the release.

Many internal developers are getting access as a part of the first round UX study.
#122 is a user guide for access to query service MVP via datagrip or api swagger ui, and will be provided to UX study participants


relref with a dot error out

I have the following (partial) structure:
content/
  blog/
    20160323-GNOME-3.20-release-party.md
    20170921-GNOME-3.26-release-party.md

20170921-GNOME-3.26-release-party.md has a relref to 20160323-GNOME-3.20-release-party. When I run hugo in versions after 0.64.1, I get the following error:
REF_NOT_FOUND: Ref "20160323-GNOME-3.20-release-party": "/home/afranke/www/content/blog/20170921-GNOME-3.26-release-party.md:11:151": page not found

I have many relref in my blog, and four of them bring up this error. The common trait amongst them is they all have a . character in the slug, so I’d say this is the culprit.
0.64.1 is the latest version that works correctly in such cases. This issue was introduced in 0.65. I have confirmed it can be reproduced with all of 0.65.x, 0.66 and 0.99 (latest at the time of filing this).
This is a variant of #6952 but the fix for that one doesn’t work here.

If your target filename contains more than one period, include the extension.
{{< relref "20160323-GNOME-3.20-release-party.md" >}}

Ok, that indeed works around the issue. Is the behaviour I reported expected though? I failed to find any documentation that would have warned me that I would run into the problem.

Duplicate of https://github.com/gohugoio/hugo/issues/10864.


Fix MultifactorAuthenticationProviderTypes from discovery.

Arguments should be in reverse order, when creating form options for
mfaProviders from CasServer profile.

This is excellent. Could you post the patch for the cas-6 branch as well?

Of course. #39

Outstanding. Thank you very much!


Enhance replay functions

Use case
In FS server, when doing some research or exploration, user would like to replay the histroical data/stream and using the replayed result to validate or run backtest.
my case is

import nyse data of quote and trade into two streams ( two big csv files) refer to https://ftp.nyse.com/Historical Data Samples/DAILY TAQ/
replay both streams, so the quote and trade will replay in the same time interval
run some query that corelate these two streams to monitor or analysis the trade/quote

the existing query cannot be used in such case as the current replay is based on append time, and in my case, all historical data are appended in the same time.
Describe the solution you'd like

support using _tp_time as the time col when replay

select * from s settings replay_speed = 1, time_col = '_tp_time'

support using customer time col when replay

select * from s settings replay_speed = 1, time_col = 'time'

3 support replay historical query in streaming way
select * from table(s) order by _tp_time limit 10 settings replay_speed = 1, time_col = '_tp_time'

3 might be hard for now, it is OK if we only support 1/2

Replay only supports data in streaming store. Otherwise we will need sort the whole data set according to timestamp specified and then replay.


fix(formio): Change the returned result object for updateUser method

Information

Type
Breaking change

Feature/Fix/Doc/Chore
Yes/No

Description
A few sentences describing the overall goals of the pull request's commits.
Usage example
Example to use your feature and to improve the documentation after merging your PR:
import {} from "@tsed/common";

Todos

[ ] Tests
[ ] Coverage
[ ] Example
[ ] Documentation

:tada: This PR is included in version 6.47.4 :tada:
The release is available on:

v6.47.4
GitHub release

Your semantic-release bot :package::rocket:


Git Admins shouldn't need to mark their own accounts as repo administrators when editing permissions

Right now, when a server-wide admin opens the Edit dialog for a repository, they have to tag their account as an administrator within the administrator list for that repo in order to be able to save changes. Not doing so throws the error "You can't remove yourself as an administrator".
This seems a bit counter-intuitive, as it shouldn't matter whether or not a server admin is an admin over a specific repository - they're going to have access regardless.

Yes, this is overzealous checking on the part of the form - the permission layer lets a system-admin do everything anyway, as you say there's no need for it to be burnt into the repo record too.

@RedX2501 I think there are two checks here which are not strictly necessary:

There's a requirement in RepositoryDetailModel that a repo has to have an admin, which seems to me unnecessary, given that you can just be a sys-admin and administer everything anyway, and the one bad situation, (which is a repo-only-admin removing themselves from the repo) is caught by the 'don't remove yourself' below.

As @hmmwhatsthisdo notes, the 'don't remove yourself' rule (in the action method) does not need to apply to a sys admin.

Any objections to me removing rule 1 and modifying rule 2?

Nope go for it.
I always found that rule strange anyway.


Output FITS image of source

It would be nice to automatically see the source model.

With #185 we are now able to get the position and radius of sources, if the types are correctly specified in the parameter array. Using this information, we could figure out the bounding box of the sources, and trim the field of view of the FITS file to this region.


Prepare v1.18.1

Description
Prepare fix release v1.18.1
TODOs

[x] Create branch release/{version-number} from tag v1.18.0
[x] Bump version number in package.json
[x] Update CHANGELOG.md
[x] Create DRAFT release page at GH linked to release/{version-number} branch
[x] ADD release notes to DRAFT release page
[x] Sign binaries as described here and add signed message to DRAFT release page
[x] Check binaries by running on macOS, Windows and Linux
[x] Publish release

Done by #2396


3D models synced with open layers?

I saw #163 . What I'm trying to do:

Make a feature, like a point, in Openlayers.
Set a key value pair with ol.Feature.set('model', '/models/airplane.gltf'). Maybe with some basic options like minimumPixelSize and scale.
When switching from Openlayers to Cesium, it replaces the point with that model.

Is something like having a 3D model synced (i.e. position) with a point in Openlayers possible? If so, can I please get an example? Thank you.

It is possible to implement it:

either in ol3-cesium, by adding this case in the
olcs.FeatureConverter.prototype.olPointGeometryToCesium() method;
or in your application, by subclassing the olcs.FeatureConverter and
overriding the above method.

I think it is acceptable to add an experimental implementation in Ol3-Cesium
(solution 1). It would simply use the Cesium Model option hash described
in https://cesiumjs.org/Cesium/Build/Documentation/Model.html instead of
the gltf url, like you propose.
There is no example of it yet, but Pull Requests are welcomed.
Please let me know if you want to work on this.

I ended up kind of hacking this...
I added a toggle button to switch between OL and Cesium. Using olcs.OLCesium.getEnabled(), I would apply a style that would hide/show the features with a model.
The cool thing about OL is that you can store a reference to the model from Cesium directly in the feature by using the ol.Feature.set(key, value) function. So, when I delete any feature, I call the Cesium function destroy() on the model, I can move it etc.
The above combined with forEachFeature solved the problem for me.

Thank you @thinkpadder1 for the tip.
The issue is still valid in my opinion, so we can keep it opened.

@thinkpadder1 you mean, we must add models and hide features in globe and remove models and shoe features in 2D view?


Version 1.0 Purchase Requests

Is there somewhere we can note our interest in purchasing v1.0 ?

Not yet, I'll set something up tonight using Google forms though.
As a point of curiosity would you be wanting a fully built unit or a kit? Also, would you want the aluminium chassis or a plastic one?

Hey, I finally got the survey done, I needed too set up a company for a few bits first.
Link below: https://forms.gle/bdBZMKoUopvWX2VN7
If this works for you I'll post it more visibly soon.

I have used the form - really great. Put me down for 4 !

I've just seen it on KBD News - https://kbd.news/Rolio-0.9-2158.html

Ha, that's cool.
There's even a picture of the prototype travel case! I maybe should have re-printed the case with the fixed up logo.
I can see you've answered the survey, thank you. If you do genuinely want one of these boards (though you do say 4) I can probably get you at least one soonish, I have 6 aluminium chassis coming from JLCPCB soon. I could sell you one as an early test, if you really like it I can do more after, with some potential for limited customisation if you'd like (LED and chassis colour for example).
Let me know here if you're keen and I'll email you directly with more information.

That would be FANTASTIC!
I say 4, but I don't want to appear greedy ;-) . I have a Corne-ish Zen, which I love, but I only managed to get one, and it's awkward for work & home. If it's a limited run, I completely understand that from your point of view, more users is better...
But .... your extra keys and scrollers just looks cracking.


Speed up cache warmup

Motivation
Cache warmup is taking a lot of time
Description
This PR speeds up cache warmup by using a single SQL query instead of multiple separate SQL queries for VRF nonces and malicious node IDs. Speedup on a Mac M3 Max:

warmup without the patch: ~5m 50s
warmup with the patch: ~1m 20s

Test Plan
Verified on a mainnet node.

bors try

What is the difference between IterateAtxsData and IterateAtxsOps? The first one I didn't see being used anywhere except for one test?

the second is used in api and allows a bit of programmability, the first one is used in warmup.go (which is a subjet of this change)

There is also IterateForGrading which looks similar to the other two. Would it make sense to only have IterateAtxsOps and pass the builder.Operations needed for the specific query?
I know IterateAtxsOps decodes the ATXs from their binary representation, but that's gonna change with ATX v2, where we don't need to do that any more.
cc @poszu

unlike the other two IterateForGrading selects unique piece of information that is not used in those other two. it would be wasteful to always do a join and select that piece of information in other queries. also in this change there is another part that selects nonce which wouldn't make sense to use in IterateForGrading, and it certainly would be problematic to add it to IterateOps.
it doesn't sound like a good idea to break down atx into multiple fields and store all of them separately. maybe you can try to keep blobs as they are. and save subset of fields that are relevant for consensus, in a way similar to current schema.

@dshulyak the goal is to keep only the minimum necessary information in individual columns in the table.
The main problem with relying on decoding ATXs when fetching them from the DB is, that we then need to put logic into the SQL package to be able to decode different blobs of ATXs based on their publish epoch. In my opinion this should be the sole responsibility of the activation.Handler and other parts of the codebase should ideally not even be aware about different encoding schemas of ATXs.
For gossip / fetch the handling functions don't need to be aware how the blob data encodes an ATX but just serve / gossip it if needed. As fallback one can use the ATX ID to fetch the binary blob and decode the ATX itself if needed somewhere, with the caveat that they then need to be aware of possible different encoding schemas of ATXs.
Right now we have multiple ways of representing the same data structure:

types.ActivationTx
types.VerifiedActivationTx
types.ActivationTxHeader
atxsdata.ATX

With some of them performing double duties and - at least for the first 3 - tight coupling between them. For me ideally we only had 2 types:

types.ATX
activation.ATXDto

Where the first contains all the information relevant for consensus and in the best case maps fields 1:1 to the columns in the atx table in the DB and the second is the representation of the ATX as it is sent over the wire and should ONLY be used for that. The first can be used anywhere and be freely extended or changed without having to fear to break backwards compatibility. Queries would always return an types.ATX (with some fields possibly being nil or zero if that speeds up specific queries) and only the activation package is aware of the actual binary representation of an ATX so it can decode them in the Handler. (possibly checkpoint needs to be aware as well - because it cares about PrevATXID and PositioningATX that are not available as columns in the atx table).
I'm only advocating for a leaner surface to the sql/atxs package. Ideally there would only be one Iterate method that is flexible enough to handle the 3 use cases we already have and not need 3 individual functions for it. builder.Options could be extended with joins and with selects.
I've seen #5670 but I don't fully understand how this improves performance? Why does it matter if the blob data is in the same or a different table? I'm not advocating against it. It could even help keeping the separation as suggested clear in the code. Would moving it to a different table not cause functions like IterateAtxsOps, Get and GetByEpochAndNodeID to break (also indirectly anything that uses types.ActivationTxHeader)?

Probably simplifying somewhat, but #5670 should improve SQLite performance b/c with blobs taken out of atxs table, the whole table should basically fit in the cache (RAM) and thus all the operations involving a subset of ATXs but not actual blobs should be faster

It makes no sense to include the VRFNonce in every published ATX. For any given identity it usually never changes. If we wouldn't support PoST resizing we would only ever need to include it in the initial ATX (similar to CommitmentATX). But since an existing nonce can become invalid if the user chooses to increase their PoST size we must have an option to update the VRFNonce of an identity.
If you want to simplify the lookup of the nonce instead we could make the nonce column NOT NULL and set it to the same value as in the previous ATX of the same NodeID if it is not set in the broadcast ATX.

@fasmat ok I'll adjust the patch not to broadcast the nonce, yet we need to include it in the atxs rows.
Even if it's 80Mb increase it's close to nothing compared to the database size (up to ~26 GiB currently) and it speeds up a lot of queries substantially, e.g. warming up the cache is down to ~15s from ~1m 26s on my laptop compared to what can be achieved using a subquery

@fasmat ok I'll adjust the patch not to broadcast the nonce, yet we need to include it in the atxs rows. Even if it's 80Mb increase it's close to nothing compared to the database size (up to ~26 GiB currently) and it speeds up a lot of queries substantially, e.g. warming up the cache is down to ~15s from ~1m 26s on my laptop compared to what can be achieved using a subquery

I see no issue in adding the value to the DB 🙂, I just want to avoid having to broadcast the nonce with every ATX.

reverted the change which was including nonces in each published ATX
added prev_id field to the atxs table
instead VRFNonce function (which queries nonce by epoch + node id) used NonceByID (which queries atxs.nonce field which is now always populated) where possible
made the migration somewhat faster by means of re-creating the atxs table, and also by creating the indices after populating the atxs and atx_blobs tables. This comes at the price of not having PRIMARY KEY column in both tables as SQLite can't add PK to a table after the table has already been created, but the unique indices serve the same purpose and have no differences in performance

bors merge


Lint Cleanup

Describe your PR
This PR cleans up some lingering lint warnings that have been showing up in open PRs
Related to #n/a
Fixes # CI
Pages/Interfaces that will change
n/a - this shouldn't affect anything functionally.  There should be 0 lint warnings after CI runs.
Screenshots / video of changes
n/a
Steps to test

let CI run lint!

Additional notes

Pushed one more commit just now - this updates all of the eslint dependencies to latest

I would say this has gone well 🤦🏻♂

@mbifulco Fixed the package-lock! that's all it was


[submodule-sync] bot-submodule-sync-branch-24.02-test to branch-24.02-test [skip ci] [bot]

submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
 If failed, it will remain open until test pass or manually fix.


source code is not complete

I am not able to able to access complete source code, can any body explain what's major issue there. is this project is incrypted.

No, the project is not encrypted. All the source code necessary to build the packaged versions is in this repo (once you install Maven).

thanks jeremybrerrill


ESET NOD32 Antivirus V<IP_ADDRESS> + License Key 2025 [Latest]

ESET NOD32 Antivirus Crack is the most powerful protection against today’s massive Internet and email threats. It is a popular choice for users who want to protect their PCs from viruses, Trojans, ransomware, adware, spyware, worms, rootkits, dialers, and other malware types. It provides comprehensive anti-virus and anti-spyware protection without affecting the performance of the computer. The application allows you to explore online quickly, easily, and confidently.
📥👉Download ESET NOD32 Antivirus Crack Full Version
ESET NOD32 Antivirus Free Download Full Version with Crack has advanced functions running in the background while protecting your computer from the latest Internet threats, browser and application attacks, and malware. It has a user-friendly and intuitive interface. The setup process is fast and requires attention. It requires users to enable or disable detection programs or potentially harmful programs according to their preferences.
It provides advanced detection technology and multi-layer security functions as well as network security training. ESET NOD32 Antivirus Keygen, based on ESET’s unique algorithm technology, can identify viruses. It enables them to actively protect your computer in real time against new viruses and network threats that traditional signature-based antivirus products cannot capture.


Added adjustable knobs for Managed Scaling

Issue #, if available:
Customers reported that their clusters are underutilized because EMR Managed Scaling constantly scales to maximum capacity
Description of changes:
This script introduces adjustable knobs for Managed Scaling in EMR providing customers with the control to define the Initial_max for Managed Scaling, gradually scale up to Upper_max, and efficiently revert back to Initial_max if the container_pending is zero for a specified Cool_down_period.

Based on discussion with Ian, would add a bootstrap operation, and streamline the 8 input arguments to only include <Initial_max>, <Scale_increment_max>, and <Cool_down_period_to_initial_max>. The remaining parameters can be obtained from the API.

Based on discussion with Ian, would add a bootstrap operation, and streamline the 8 input arguments to only include <Initial_max>, <Scale_increment_max>, and <Cool_down_period_to_initial_max>. The remaining parameters can be obtained from the API.

This is implemented in the current version

Next revision:

Add a percent calculation for scale_increment_max .
Make the values for MSDampener arguments in the run_continuously_s3.sh script as arguments which can be passed in EMR step, allowing users to just pass them in the EMR step for implementation without script modification for each cluster, making it more user-friendly.


Passing multiple items to an Option

Hi
I've been going through your examples and I'm having an issue with Creating a Root Command Parser. It works with multiple -w. Example:
dotnet run -- -w "aaa" -w "bbb" -w "ccc" -s "#"

How can I get it to work passing multiple values to a single -w? Example:
dotnet run -- -w "aaa" "bbb" "ccc" -s "#"

I did some searching and found Option.AllowMultipleArguments, but could not get it to work.

I think I've found the solution by reading further through your examples. It was in Defining Inputs Manually
By using System.CommandLine.Option I was able to add opt.AllowMultipleArgumentsPerToken <- true and this worked.

Glad you found a solution. 👍


"Difference" should be "different"

This sentence should use the word "different" instead of "difference":
This is quite important to work out ahead of time as difference connectors bear a "Premium" or "Enterprise" (in the case of Logic Apps) which affect the overall cost of running the workflow in your decision-making process.

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

ID: d3341b93-944b-b3b4-bdd2-3ef9df2a19d5
Version Independent ID: 3ecd9b65-0dd5-6f08-b8cf-4766fbb6fa2d
Content: Power Automate vs Logic Apps
Content Source: Community/power-automate-vs-logic-apps.md
Service: power-platform
GitHub Login: @pkbullock
Microsoft Alias: daisyfeller

Sorry for the lag in getting to this, and thanks for the suggestion, @tylerfarmer1. I'll make that change and give you credit for it in the changelog!


Labels should not define a top margin

Same as https://github.com/vaadin/vaadin-form-layout/issues/85

Labels of form items set a margin-top: var(--lumo-space-m) on themselves. Items should not care about that, since they don't know what might be around them. I understand this is intended to create a gap between items, but then the first item in the form will have a useless top margin.
In my opinion, the layout element should care about spacing its own items, not the items themselves.

In this case, it defines margin-top: calc(var(--lumo-font-size-s) * 1.5).

I would oppose. The space above the label is not useless, it is meaningful.
One of the key visual design principles is that distance between things defines relationships. Things that are highly related should be close, things that are not related should be placed far apart from each other.
The label is related to the labelled item more than to anything else. So it should always be distanced from the rest elements to maintain this visual relationship. The margin above the label does exactly that.
Using multiple <vaadin-text-field> stacked inside a plain div, not a layout, is a valid use case. It should not result in confusing output about what the labels belong to. Thus we cannot delegate all the spacing work to layout components.

Thank you @platosha for the feedback! The motivation is clear. The problems I see here are that:

the element assumes there is something preceding itself, so you get space you don't need when the element is e.g. the first child;
if you use the element in a layout which takes care of the spacing, you also get space you don't need.

Of course the use case of fields stacked in a plain div is valid, but in such a "vanilla" use case I'd prefer to have a "vanilla" style too, i.e. no spacing, to let the developer decide how to space (e.g. with display: grid or third part framework).
To have beautiful spacing by default, Vaadin's already provide its own vertical and horizontal layouts with ad-hoc styles (i.e. theme="spacing").

Here is how you can reset padding for the text-fields, if you need:
<dom-module id="no-label-padding" theme-for="vaadin-*-field">
  <template>
    <style>
      :host([theme~="no-label-padding"][has-label]) {
        padding-top: 0;
      }
    </style>
  </template>
</dom-module>

The theme attribute propagation allows to propagate it inside the components using text-field internally (combo-box, date-picker, select, time-picker) so the appearance would be consistent.
Given the above, let me close as won'tfix per https://github.com/vaadin/vaadin-text-field/issues/239#issuecomment-404856452