Badge for forkability.io

I would like to enable forkability to offer a badge.
What do I need to add to the code so that we can make it work?
Initially I would go with yes/no, but in the future I would like to be able to offer a score of x passed/case tested

Thanks for that suggestion!
It might be as simple as fetching a /badge/ from shields.io. The question is, what should it show?

It depends on the projects owner: cc @basicallydan
The project gives an indication of how 'forkable' a repo is.

There is a Github Pages site, but as far as I know, there is no web api that can be called to receive the information needed.
Basically I am looking for some guidance on how to set up such an api that can be used in  conjunction with shields.io

@M-Zuber This is a great idea! Looks like we'll have to set up some kinda web service for forkability for this.
So, @espadrine the way that Forkability works is like this:

It's a commonjs JavaScript module which fetches GitHub repo information and runs it through a number of linters to measure the "Forkability" that @M-Zuber mentioned.
It works in NodeJS, so it'd be fairly easy to run wrap it in a JSON API.
It also works in the browser which is how it is currently used by most people.

I saw mention of the "Shields standard", and in the README saw mention of opening an issue to get a service supported which I guess @M-Zuber also saw.
Do we need to set up a web API for it, or is there any chance that Shields would be capable of scraping data from a JavaScript page? If it's the former, then @M-Zuber and I have some thinking to do! Maybe Heroku or NodeJitsu for now?

@basicallydan You can simply generate this image when the result is overall positive, and provide copy-pasteable links in markdown, html, what have you, with a link to the forkability result:  (http://img.shields.io/badge/forkable-yes-brightgreen.svg / http://img.shields.io/badge/forkable-no-red.svg)

Ah great! @espadrine we can just give them that specific link, you're OK with that?
If so, @M-Zuber we don't really need an web API necessarily. Though in the ideal situation, I guess the badge would be an automated generation based on the most recent forkability result.
For now though, we should definitely add this to the results page and hopefully improve the "virality" of the service and get some more contributors. Thanks!

Sure!

Back from vacation :smile:
Thank you @espadrine
So, seeing that we are going with the static route (at least for now) this seems like a very nice solution.
One item is we will just have to hope that people don't use the badge without running the service, so maybe it shouldn't be added to the list on shields.io?

I suppose a simple warning on your website suffices?

that call has to be made by @basicallydan

@espadrine Yep, sounds good enough to me. I'll do it later though... getting late here in Seoul, and I'm getting tired! However, badges now are displayed after running Forkability, as long as your repo passes ;)
https://basicallydan.github.io/forkability/?u=badges&r=shields

Another thing is that the badge won't be shown to web app users unless they pass, so that should reduce the amount of people using it when they shouldn't.
Anyway I bucked up and added a little note: https://github.com/basicallydan/forkability/blob/master/README.md#badges
I'll leave it up to you, @espadrine, to decide whether to add it or not :)

I am willing to make a PR to have it added, but I could not find clear instructions on how (mainly to which files changes need to be made)

CC @espadrine

@M-Zuber I'm not sure exactly what you mean by "have it added". How should things work?

I was referring to have it listed on shields.io

@M-Zuber Hmm, that would be in try.html (with installation instructions in INSTALL.md for testing purposes), but the badge wouldn't be accurate when edited…

In what way would the badge not be accurate? That people would use it without qualifying?

The badges under Miscellaneous on shields.io have all been generated according to the parameters given in the URL. In that sense, they are all accurate (their data correspond to their parameters). If I recall correctly, the forkability badge is not able to retrieve the information that would presumably relate to the repository specified in the img.shields.io URL parameters.

This is the badge markdown generated after running forkability on itself:
[![This is a forkable respository](https://img.shields.io/badge/forkable-yes-brightgreen.svg)](https://basicallydan.github.io/forkability/?u=basicallydan&r=forkability&l=nodejs)</li>

Unless the repo information used in the example (which would be forkability itself) is changed that link is still valid, as it is simply a link to the service with parameters already set.
Does this then solve your worry?

I am not worried. I am simply unsure what you would like to see happen when one clicks on the badge and the popup opens. A patch would be unambiguous, though.

cc @basicallydan what do you say?
Should we have the badge listed for exposure - but it's not clear how to build the link behind it. Or should we evangelize and hope people check us out after seeing the badge on another repo?

@M-Zuber I say we go with the latter.
If we try and get people to use it on shields.io at the moment then it'd be really confusing, since the URL isn't based on the name of your repo.
It'd be rad if it was based on the URL though. Maybe we should try turning this into an HTTP service.
@espadrine So if we did go with a service, the URL would serve up the shields.io badge right? And then you could set up a route on shields.io to point to our URL with the given params?
Until then, @M-Zuber I say we just evangelise. I'm gonna try and fix up my biggest repo (https://github.com/basicallydan/interfake) and hopefully that'll help a little. As soon as I get a few free moments. Still on the road...

Great! I'll close this then.
Enjoy the rest of your trip :smile:

@M-Zuber Thanks dude!


Question about your  pre-trained model for testing

@cardwing Hello,i download your pre-trained model for testing,and i found this pre-trained model not be trained by the code of this repository. Can you share what operations need to supplement to  reproduce the results as your pre-trained model?

The code has been revised to support multi-gpu training. You can either re-train the model or use the old code which is before Dec 19, 2018.

Thank you!


add faq for how to do advanced customized logging using fluentd

customized logging exists now, but you might not notice/realize it, so we should add a faq about it.
step 4 when enabling logging
https://rancher.com/docs/rancher/v2.x/en/cluster-admin/tools/logging/
https://rancher.com/docs/rancher/v2.x/en/project-admin/tools/logging/

This is now covered on https://rancher.com/docs/rancher/v2.x/en/logging/v2.5/ with examples.


Add background in dialog explorer

Fixes #1508
Changelog Entry

Add background image in the dialog explorer
Fix dialog-bg color in dark theme

Specific Changes
Added data scheme to the default allowedSchemes
Testing

The specific changes are wrong (they are from another PR)

Replaced by #1625


SkipTrailingSlash

In project, that I'm writing for some handlers I need to remove trailing slash (REST server, where I cannot influence form of requests). I spent a few hours yesterday, but I have not find any good looking solution.
Problem, that when I handle something inside r.Group or r.Mount, inside this handler next handle to root does not work.
Example: In your example account code I don't want be able to handle only
    curl <IP_ADDRESS>:3333/accounts/123
but also
    curl <IP_ADDRESS>:3333/accounts/123/
with the same handler.
Inside accountsRouter there is no good looking solution how to use the same handler for both cases.
r.Get("/", getAccount)
handles only the first form. When I tried to change it into r.Get("//", ...) it does not handle anything.
Possible solution (if I understand well are):
a) Use two handlers for  r.Route("/:accountID", ...) and r.Route("/:accountID/", ...) with same "next" function. That looks confusing, and also I can't use anonymous function. Also when some trailing slashes can appears in many handlers, I have to repeat such bad code for each handler.
b) Write middleware SkipTrailingSlash, that checks, whether path ends with /, and if it, just remove it. I made it, it works fine, but I have to modify chi.Context, because routeCtxKey is not visible neither from my application nor chi.middleware. I had to change it, but it is not nice, because main idea was publish internal routing mechanism and make it visible for everyone.
c) Add flag SkipTrailingSlash, into Mux. I thing that this is the best idea yet, but I welcome any better proposals. I could write it, that is not problem, but do you think it is a good idea?

hey @lofcek, it's a good point and the trailing slash has been a bit of a pain. I added a test case https://github.com/pressly/chi/commit/53adbc4e11d956b350ba39aed51801f2dd42a17d that can show you how to do it now. The reason this works is because routes are layered on top of each other, that build the routing tree.
I do agree I should build something standard into the mux. However, there are usually two options, many people will want to redirect /accounts/123/ to /accounts/123 and others will want the trailing slash to be treated to the same handler.
one idea is instead of changing the Mux{} object, because, its more of an underlying struct and its best to use the Router interface, and we don't really support configuration options (not that we couldn't), but it limits extensibility..
I think instead... I could update the code to support something like..
func TestMuxTrailingSlash(t *testing.T) {
	r := NewRouter()
	r.NotFound(func(ctx context.Context, w http.ResponseWriter, r *http.Request) {
		w.WriteHeader(404)
		w.Write([]byte("nothing here"))
	})

	subRoutes := NewRouter()
	indexHandler := func(ctx context.Context, w http.ResponseWriter, r *http.Request) {
		accountID := URLParam(ctx, "accountID")
		w.Write([]byte(accountID))
	}
	subRoutes.Get("/", indexHandler)

	r.Mount("/accounts/:accountID", middleware.ServeSlashes, subRoutes)

	ts := httptest.NewServer(r)
	defer ts.Close()

	if resp := testRequest(t, ts, "GET", "/accounts/admin", nil); resp != "admin" {
		t.Fatalf(resp)
	}
	if resp := testRequest(t, ts, "GET", "/accounts/admin/", nil); resp != "admin" {
		t.Fatalf(resp)
	}
	if resp := testRequest(t, ts, "GET", "/nothing-here", nil); resp != "nothing here" {
		t.Fatalf(resp)
	}
}

so, the introduction is to add middleware.ServeSlashes, which, I will write in a few minutes. The other middleware would be, middleware.RedirectSlashes
..and now as I think about it.. this could very easily be an option on the chi.Context, the middleware could be the thing that sets it on the routing context

btw.. this works..
func StripSlashes(next Handler) Handler {
	fn := func(ctx context.Context, w http.ResponseWriter, r *http.Request) {
		path := r.URL.Path
		if path[len(path)-1] == '/' {
			rctx := RouteContext(ctx)
			rctx.RoutePath = path[:len(path)-1]
		}
		next.ServeHTTPC(ctx, w, r)
	}
	return HandlerFunc(fn)
}

I'll be packaging this into middleware pkg soon enuf once I write the RedirectSlashes middleware, but I gotta head out for now

And I also didn't realize it immediately- I think change data inside Context during execution is a bit confusing. I think it should be better to create a new chi.Context, don't change previous one.

Thanks for the thoughts but I don't fully agree. You're right about the root path, I'll make a check but if you have other opinions, please submit a PR or a breaking test case. Ie. rctx is a pointer and doesn't need to set to ctx again, since it already on the context chain, and we don't need a new chi.Context

On Jun 20, 2016, at 7:30 AM, lofcek<EMAIL_ADDRESS>wrote:
And I also didn't realize it immediately- I think change data inside Context during execution is a bit confusing. I think it should be better to create a new chi.Context, don't change previous one.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

thanks for the feedback. I've added support with https://github.com/pressly/chi/commit/b74aedb047b9ee86e7f0c0154101b65fe255fd9a


Development Guide hyperlink 404's

The "Development Guide" hyperlink in the initial README docs 404. It is not clear where to go instead to learn how to participate.

/assign lance
/kind bug

@bbtong we recently rearranged the docs and it seems some links were missed. Here is the developer's guide. https://github.com/knative-sandbox/kn-plugin-func/blob/main/docs/function-developers/developers_guide.md

@lance Thanks!


implement yubihsm auth

This is used to calculate session keys for Yubico HSM.
TODO:

[x] Test against an HSM the generated keys match
[x] Add helpers for:

[x] adding
[x] deleting
[x] listing credentials

@tony-iqlusion any chance to get this merged?

Will do a pass on this repo soon


Tags for nodes

Nodes should be able to have tags.
A Tag model should contain:

id: int
name: str: the name of the tag
description: str: description for the tag
tag_type: str: the type of tag (this can be arbitrarily set by the user and should represent the category of the tag, i.e., something like business_area or report or group)
tag_metadata: json: arbitrary metadata for the tag

I wonder if tags need owners... to be revisited.


Selectable.get breaks without any exception - customSelect(rawSelectQuery)

Selectable? data = appDb.customSelect(queryString);
List list =await data.get();
when I try to get the list of QueryRow from selectable it breaks the code not throwing any exception.
It does not occur all the time though.
Note : I'm using MoorIsolate to estabish DB connection

What do you mean by "breaks the code". Do you have a simple example that I could take a look at?

I have a select function which takes a query and queries from DB using customSelect
Future<List> select(DBInputEntity dbInputEntity) async {
String queryString = "SELECT * FROM ${dbInputEntity.entityName}";
String whereClause = "";
if (dbInputEntity.whereClause.length > 0) {
whereClause = " WHERE ${dbInputEntity.whereClause}";
}
Selectable? data;
Database appDb = await DatabaseManager().getAppDB();
try {
  data = appDb.customSelectQuery(queryString + whereClause);
} catch (e) {
  Logger.logError("DatabaseManager", "replace", e.toString());
}
List<Map<String, dynamic>> result = [];

 if (data != null ) {
   try{
     List<QueryRow> list =await data.get();
     result = list.map((e) => e.data).toList();
   }catch(e){
     log(e.toString());
   }

}
return result;

}
When this line (List list =await data.get();) is reached it does not return anything, also not throwing exception

The issue was due to transaction added for customSelect within isolate....Thanks


Remove raven from setup.py

Usage of raven is removed in https://github.com/postmanlabs/httpbin/commit/e5433806757a09d58e48935c081db80170296ab5

Seems this project has been dead. I will no longer keep an eye on this. Anyone can use up my patch in any place if they wish.

Seems this project has been dead. I will no longer keep an eye on this. Anyone can use up my patch in any place if they wish.


Back image always coming as Nil when trying to scan a US DL.

When i scan both front and back of the US DL, after the back scan my delegate method didScanEntireDocument gets called. I find the front image in recognitionResult.frontSideDocumentImage but recognitionResult.backSideDocumentImage is always coming as Nil.
Below are my settings :
MBBlinkSettings.sharedInstance.frameGrabberMode = .successFrames
MBBlinkSettings.sharedInstance.frameGrabberDelegate = self
MBBlinkSettings.sharedInstance.initialCountry = MBCountry(supportedCountry: .unitedStatesOfAmerica)
MBBlinkSettings.sharedInstance.initialDocument = .driverLicense
    MBBlinkSettings.sharedInstance.shouldShowCancelButton = false
    MBBlinkSettings.sharedInstance.shouldValidateDocuments = true

Hi,
you can get back side document image only if the document recognizer supports document image retrieval, which is not the case for USDLs.
Best regards,
Dominik


Work out options for integrating with a pattern portfolio - talk to Brad Frost, etc. How much like a theme does it need to be?

Going to break this down into actual tasks. Some are already added and show up in ceviche-starter issue list.


why general1.2xlarge instances for CodeBuild?

Is there any specific reason why you use the quite expensive instance type "general1.2xlarge"?
Wouldn't be a smaller instance type sufficient?

I just spotted this too. 145 GB memory, 72 vCPUs seems a bit overkill for a simple script!
I'm not sure what the 120 second delay is for either....
https://github.com/aws-samples/aws-nuke-account-cleanser-example/blob/8e63b4911bc40a0da751b13108081313fb5f6ab0/nuke-cfn-stack.yaml#L365

https://github.com/aws-samples/aws-nuke-account-cleanser-example/issues/10

Hey agree ! the compute is overkill, I sent a request for an updated PR to modify this,
I also added the --max-wait-retries - to avoid Nuke continuously re-trying for resources waiting/Pending state


On GHC 9.2.7, Cabal cannot resolve package dependencies.

test/Spec.hs:1:1: error:
    hspec-discover: builderMainLoop: exec: invalid argument (Bad file descriptor)
  |
1 | {-# OPTIONS_GHC -F -pgmF hspec-discover #-}
  | ^

At least I can stay busy.


bug: plugins lazy loaded with autocmd events don't always execute their events when loaded

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9.0
Operating system/version
MacOS 13.4
Describe the bug
When a plugin is lazy loaded using an autocmd  event and also has the same type but broader event on plugin startup, the event does not run. Some plugins will not work properly when this happens since their startup code is not properly set up. An example is a plugin that is loaded by event = "BufReadPost *.md" but also has autocmd BufReadPost * on their startup code
I think this happens because in this line pattern = pattern is used to filter for any new autocmds that have been created from loading the plugin, but filtering by the specific pattern will ignore the more broader patterns
Steps To Reproduce

have a plugin lazyload via event, ie: event = "BufReadPost *.md"
add on autocmd on plugin config for same event but broader, ie:

vim.api.nvim.create_autocmd("BufReadPost", {
  pattern = "*", -- this pattern should match the pattern by which this plugin is loaded with
})

observe that the autocmd does not run when the plugin loads

Expected Behavior
The plugin is expected run matching autocmds when it loads, but does not
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
  {
    "tomasiser/vim-code-dark", -- plugin doesn't matter, only used for the example
    event = "BufReadPost *.md",
    config = function()
      print("plugin 3 config")
      vim.api.nvim_create_autocmd("BufReadPost", {
        pattern = "*.md",
        callback = function()
          print("plugin *.md autocmd!") -- expect this to print (does print)
        end,
        group = vim.api.nvim_create_augroup("mygroup3.1", {}),
      })
      vim.api.nvim_create_autocmd("BufReadPost", {
        pattern = "*",
        callback = function()
          print("plugin * autocmd!") -- expect this to print (does NOT print)
          print(debug.traceback())
        end,
        group = vim.api.nvim_create_augroup("mygroup3.2", {}),
      })
      vim.api.nvim_create_autocmd("BufReadPost", {
        pattern = "*.ts",
        callback = function()
          print("plugin *.ts autocmd!") -- expect this to not print
        end,
        group = vim.api.nvim_create_augroup("mygroup3.3", {}),
      })
    end
  },
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Hi, this was closed by mistake by the above release, but the commit was reverted


:tada: Capturing of WebGL art

:zap: use WebGL API if needed
:bug: :label: should return blob
:zap: use webgl for next drop
:wrench: next drop is split

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Needs QA check

@kodadot/qa-guild please review

Context
WebGL is possible to screenshot
Did your issue had any of the "$" label on it?

[ ] My DOT address: Payout

Screenshot 📸

[ ] My fix has changed UI

@vikiival what exactly i should be able to screenshot now?

The same things
Except the cloudflare cannot make screenshot webgl.
I will make one more art to test it on AHK

@prury /ahk/drops/coretime


We're doing the same thing

@rockandska
Air traffic control / collision avoidance activated 😄
i've made a pytest-tmux repo and reserved it on PyPI. In anticipation of having this moved into the package: https://libtmux.git-pull.com/pytest-plugin/index.html. I was going to publish it today. I've hit the breaks.
I want to show you something - this is from July 17th, me preparing to do a pytest plugin: https://github.com/tmux-python/libtmux/issues/381
but you've also told me you want to do make a pytest-plugin for tmux. I don't recall if it's before or after.
What do you propose? What do you think?
If this really seems like something you've been building up to do and can follow through with it, I'm open to transitioning ownership of the pypi package to you (and I'll have to pick another). I note: That's easy to do now - since I've delayed publishing after finding we're on the same path - but harder to do later 😆

@rockandska I found the develop branch
Now I'm more convinced you have a creative vision for this.
If you want to talk off tracker, ping or email me.  tony at git-pull dot com.  no biggie for me

I was going to publish it today. I've hit the breaks.

Thanks for the consideration

I want to show you something - this is from July 17th, me preparing to do a pytest plugin: https://github.com/tmux-python/libtmux/issues/381

yeah, I remember discuss it and have seen it

but you've also told me you want to do make a pytest-plugin for tmux. I don't recall if it's before or after.

Does it really matter ? ^^

What do you propose? What do you think?

If this really seems like something you've been building up to do and can follow through with it, I'm open to transitioning ownership of the pypi package to you (and I'll have to pick another). I note: That's easy to do now - since I've delayed publishing after finding we're on the same path - but harder to do later laughing

Not sure if I would have the time and skill to maintain it, but I'm inclined to co-author it.
I could even let you have this repository and clean it up if you think that it will fit better the users requirements.

Now I'm more convinced you have a creative vision for this.

Yeah we clearly not have the same vision / goal :)
I need to push my last modifications, but I need to refactor some of the logic.
If you are not in rush, maybe I could try to push some examples to show you a better vision of what I try to achieve
Actually, I use jhawthorn/ttytest and was my first motivation to have a similar thing in pytest.

If you want to talk off tracker, ping or email me. tony at git-pull dot com. no biggie for me

Sure thing, we could even chat on gitter if it is not a problem for you

Does it really matter ? ^^

yes of course we don't want to step on anyone's toes in open source

Not sure if I would have the time and skill to maintain it, but I'm inclined to co-author it.
I could even let you have this repository and clean it up if you think that it will fit better the users requirements.

We have various options
As it stands, neither of us have a 1.0 package, so APIs are free to be shifted around, things can be changed.  Nobodies using the package - so ample time to try things out
In regards on what you plan to push - I look forward to seeing your changes
Thanks for telling me about jhawthorn/ttytest
In regards to gitter, how is slack for you? (not that you'd need to be on it regularly). if you did, I'd at least need you to send me your email to invite you


Add shadow shader

Add option to enable inner shadow
(see https://github.com/StaffEngineer/velo/blob/main/assets/shaders/shadows.wgsl for inspiration)

Should inputs be the same as CSS?
Like this tool on inset mode.
I'm speculating now, I think the way the redraw function works at the moment either the shadow will be rendered above the text or alpha blending would break down where shadow and text meet (for big shadows). To remedy this the redraw function would need to sample the material's final color at each pixel. I'd have to play around with a shader implementation to be sure tho.

Let me give you some intro. This plugin is temporary solution until bevy doesn't have native text input. Bevy should integrate cosmic-text rendering in 0.12/0.13 release. So, native cosmic-text input is expected in 0.13/0.14 bevy release I guess. Big chunk of this plugin can be upstreamed to bevy, chunk of keyboard/mouse interactions, etc. The plugin does CPU rendering, bevy will have GPU rendering. Now back to the shadows. Since we already doing CPU rendering maybe we can play with cosmic-text draw function and make inner shadow. In velo shadows was done by using wgsl, utilising bevy custom material feature (GPU rendering). Another option is for bevy_ui make element invisible and use it only for layouting, for sprite everything is alright and then use custom material bevy feature to draw inner shadow and then render cosmic-text image into sprite and put shadow above it so to speak.

Ah okay. I was thinking of porting all the draw functions to shaders but my wgsl is rubbish right now haha, if that's being worked on upstream I'll leave it alone. Will give this another look later, gonna take a crack at #45 for now

Yeah, I don't see straight solution to tackle this problem yet, more experimentation is needed :)

bevyengine/bevy/pull/9506 will close this, now in final review :)

@bytemunch we already can fix half of the issue, when sprite is used as the base for text drawing, right? :)
Then it's going to be just re-using shader code once bevy merges support for ui materials.

things are happening 👀
https://github.com/StaffEngineer/bevy_cosmic_edit/assets/43527203/b9ac75ad-ae3e-4509-8394-24ab30d84e46

Niceee...so using SDF you can add rounded corners of border and inner/outer shadows 🥇


fix: foxy canClaimWithdraw satisfy getTimeUntilClaimable logic

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #4481   👈

This comment was auto-generated by Graphite.


Good work, but why can't we achieve good results after 100000 iterations of training？

Me too, I have trained with this code and data download directly, but the result is bad.

@barbararoessle Hi, I have trained several scenes using this code and your data without making any changes, but some val images have floaters (almost every scene has some images with floaters, and even like a mask before the scene). Have you met the same problems?

Number of optimization iterations: We found that for the room-like scenes longer optimization, 500.000 iterations, improves the results. Since entire rooms with inside-out viewing direction have more surface area, than f.ex. single objects with outside-in viewing direction, I don't find it surprising that they benefit from more optimization iterations.
Regarding the quality of results and floaters: The stetting with very few views and no sensor depth of the scene is under-constraint and difficult, so it is certainly possible that there are floaters in the rendered test views.
The difference to NeRF without depth priors, however, should be large, like in the comparison videos.

hi

Me too, I have trained with this code and data download directly, but the result is bad.

hi,me too ,I tried directly using the downloaded data and pretrained model. but the psnr even only 17 average. I test ten images ,all results are bad


Add bucket policy to dandiset_bucket module

Currently, the dandiset_bucket module is only used for embargo buckets.
The production embargo bucket isn't working because the Heroku IAM user
is in a different account than the embargo bucket.
Add a new bucket policy to the staging and production buckets that
explicitly allow the IAM user to do anything to the bucket. Cross
account access requires that both the IAM user and the bucket have a
policy allowing access.
To resolve the issue and verify that this is the correct solution, I manually put this policy onto the production embargo bucket:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Statement1",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::278212569472:user/dandi-api-heroku"
            },
            "Action": "s3:*",
            "Resource": [
                "arn:aws:s3:::dandiarchive-embargo/*",
                "arn:aws:s3:::dandiarchive-embargo"
            ]
        }
    ]
}

This PR adds that configuration to terraform.
Fixes https://github.com/dandi/dandi-archive/issues/1035

Currently, the dandiset_bucket module is only used for embargo buckets.

Do these changes interfere with the plan to refactor the non-embargo buckets to use the dandiset_bucket module (outlined in #107)?
Would these changes interfere with


[FEATURE] Desktop: show most recently accessed entries at top of list not bottom

They are in order of creation time, with newest created at the top.
Is this not what happens for you?  We do not show most recently accessed at the bottom.

You now have the option to sort by accessed time I think this can be closed.  #849 added the feature.


safe-setting v1 release

Overview
I have made a lot of changes to the v1 release of safe-settings. Initially, safe-settings was based on probot/settings app. However, in this release, I have made changes that moves it away from the original probot settings app in several important ways:

safe-settings now supports 3 levels at which the settings could be managed:

Org-level settings are defined in .github/settings.yml
SubOrg-level settings. The org-level settings could be overridden at a  suborg level. These would be a collection of repos belonging to a project or a business unit, or a team. The suborgsettings reside in the .github/suborgsfolder.
Repo-level settings. Lastly, we could override settings for individual repos by creating a repo specific yaml in .github/reposfolder

New validator plugin to support Validation of repo names
Glob support for specifying suborg repo names.
Several bug fixes

TODO

Add support for noop mode for pull requests validations for settings showing the impact of the change.
Add support for specifying templates in the settings for repo creation
Add support for cron expression support for setting up timers for periodic full syncs
Add support for querying audit logs for identifying config drifts and converging the repo settings to the known state
Code cleanup and restructuring for better maintainability
Write tests

@decyjphr Looking forward to see the result of all your work. Do you have an idea as to when you will release it as v1?

@decyjphr Looking forward to see the result of all your work. Do you have an idea as to when you will release it as v1?

I am hoping to get the testing wrapped and release it in a few days.

@mortenbirkelund I have merged the v1-release to main. Let me know if you have any questions and looking forward to your feedback.

@decyjphr awesome. Looking forward to give it a spin


typescript 5.0.0-beta conflicts with configuration of this plugin:package. json->peerDependencies ->typescript: >=4.4.4, resulting in installation failure

Reproduction
typescript 5.0.0-beta conflicts with configuration of this plugin:package. json->peerDependencies ->typescript: >=4.4.4, resulting in installation failure
Steps to reproduce the bug

package.json set "typescript": "5.0.0-beta"
delete and node_modulespackage-lock.json
run npm install

Expected behavior
installed successfully
Actual behavior
installation failed
Additional information
No response

temporary solution : npm install --force


fix: Gitpod and Codespaces can use HTTPS

The Issue

#5684

The refactored code had an incorrect condition for Gitpod and Codespaces.
How This PR Solves The Issue
Fixes it.
Manual Testing Instructions
Automated Testing Overview

Related Issue Link(s)
Release/Deployment Notes

False alarm, this logic should remain unchanged:

https://github.com/ddev/ddev/pull/5684#discussion_r1516300948

Reopening with updated PR description.

@stasadev it's your call whether to pull this and it's an incremental improvement or whether we should defer it and figure out the rest of what's going on with codespaces. We can either hold it back and move forward with release or we can pull it (does no harm as far as I can see, although I didn't test on gitpod). Either way, we're good to do a release.


[Documentation Request] Wait for Port

I did not see this addressed in the documentation. What port does the Wait methods use?

I think this can be closed I dug through the src and saw the following
 protected Integer getLivenessCheckPort() {
        if (exposedPorts.size() > 0) {
            return getMappedPort(exposedPorts.get(0));
        } else if (portBindings.size() > 0) {
            return Integer.valueOf(PortBinding.parse(portBindings.get(0)).getBinding().getHostPortSpec());
        } else {
            return null;
        }
    }

It seems that the answer is : The first port among exposed ports.

Hi @bearrito,
It's mentioned in the docs ( https://www.testcontainers.org/usage/options.html#customizing-the-container ):

Ordinarily Testcontainers will wait for up to 60 seconds for the container's first mapped network port to start listening.

Do you think we need to be more explicit or it is fine?


Pre-commit linting

I commented out lots of stuff to make adoption of the tool smoother. This config is based on the Scientific Python project template. As we go, let's try and keep adding / uncommenting rules we like :)

pre-commit.ci autofix


Add S3 ingress

Closes #23

Dunno if we should about Nginx CORS attributes:

hardcode it in the template (current solution)
move them to values, as default
remove them from the code and add notes on README
add s3.ingress.type value and implement these attributes for several controllers

@jhonatanmorais, @tico24, @agoldis, what are your thoughts here?

Dunno if we should about Nginx CORS attributes:

hardcode it in the template (current solution)
move them to values, as default
remove them from the code and add notes on README
add s3.ingress.type value and implement these attributes for several controllers

@jhonatanmorais, @tico24, @agoldis, what are your thoughts here?

Dunno if we should about Nginx CORS attributes:

hardcode it in the template (current solution)
move them to values, as default
remove them from the code and add notes on README
add s3.ingress.type value and implement these attributes for several controllers

@jhonatanmorais, @tico24, @agoldis, what are your thoughts here?

IMHO, number 2 or 4 are the best options. I don't have a preference between them.

Dunno if we should about Nginx CORS attributes:

hardcode it in the template (current solution)
move them to values, as default
remove them from the code and add notes on README
add s3.ingress.type value and implement these attributes for several controllers

@jhonatanmorais, @tico24, @agoldis, what are your thoughts here?

IMHO, number 2 or 4 are the best options. I don't have a preference between them.

@fsmaia I don't have a string opinion, the mindset is that helm users are quire powerful and should be able to figure out the CORS settings. Having the topic documented is important though, regardless ;)

@fsmaia I don't have a string opinion, the mindset is that helm users are quire powerful and should be able to figure out the CORS settings. Having the topic documented is important though, regardless ;)

Dunno if we should about Nginx CORS attributes:

hardcode it in the template (current solution)
move them to values, as default
remove them from the code and add notes on README
add s3.ingress.type value and implement these attributes for several controllers

@jhonatanmorais, @tico24, @agoldis, what are your thoughts here?

IMHO, number 2 or 4 are the best options. I don't have a preference between them.

Hmm, I'll go with the number 2 then. :)
It would be too complex to implement annotations of several different controllers.

Dunno if we should about Nginx CORS attributes:

hardcode it in the template (current solution)
move them to values, as default
remove them from the code and add notes on README
add s3.ingress.type value and implement these attributes for several controllers

@jhonatanmorais, @tico24, @agoldis, what are your thoughts here?

IMHO, number 2 or 4 are the best options. I don't have a preference between them.

Hmm, I'll go with the number 2 then. :)
It would be too complex to implement annotations of several different controllers.


Conflict between iziToast and iziModal

I used  both iziToast and iziModal in a project but I think there are some conflict between them.
For example:
If I put iziToast.css below the iziModal.css it cause negative side effects on the animation of the background overlay of the opened modal [when i want close the modal].
and
If i put iziModal.css below the iziToast.css it cause negative side effects on opend notification (the title of notification is hide)!
You can see side effect of iziModal on title of iziToast in the bellow image (100% key-frame has zero opacity then it hide the title of toast notification):

Is there a patch for these conflicts?
Or should I use these tools with some special order and configs in this cases?
In addition: Hey @dolce , I think your plugins are awesome! Bravo!

Thanks @Ramin-Bateni!  I'll analyze! 👊

@Ramin-Bateni
Could you test, please?
iziModal + iziToast.zip

Of course, I tested it. 😉
It seems the problems are solved and the toast notifications and modals appears and hides properly (I wrote iziModal.css after iziToast.css in my test).
Thank you..
Apart from this issue:
A) I see 2 error in the Chrome console when I mouse over and mouse leave a toast notification:

B) Also I recommend Tahoma  font for RTL languages. It is most popular font in the RTL websites.
For example 'Lato' and arial are exactly same view in Persian and Arabic language and Tahoma has very better view than them to show Persian and Arabic words (RTL languages).
.iziToast-rtl {
    /*other styles here*/
   font-family: tahoma,'Lato',arial;
}
.iziToast-rtl .iziToast-body strong {
    /*other styles here*/
    font-size: 11px;
}
.iziToast-rtl .iziToast-body p {
    /*other styles here*/
    font-size: 11px;
}

Also I recommend `Tahoma `as default font every where in your plugins (iziToast & iziModal &...) for RTL mode.

Is it possible to you fix them?

In your attached codes I see another problem too. When I use: theme: 'dark'
An inline style override dark background CSS then result is texts with white font color over a white background color:

Yes, but I'm not seeing these errors in the console.
What are your settings?
And try this version:
iziToast_v1.2.0.zip

I tested both normal and minified versions of the js file. Both work the same way.
I found the error condition.
Please test it with timeout : 0 or timeout : false option.
iziToast.info({
	title:"My Title"
	,description:"My Description"
	,timeout : 0
});

Now I've been able to replicate the issue.
Fixed. thank you

Now I've been able to replicate the issue.
See if it's working..
iziToast v1.1.2.zip

Now I've been able to replicate the issue.
See if it's working..
iziToast v1.2.0.zip

Now it's OK
Thank you...


State of the project?

Is this project still alive?
If not, what project do you suggest?
One of these?
https://github.com/topolvm/topolvm
https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner

This project is still alive and heavily used in production.

If there are any more question feel free to re-open.


Adding CVEs for bluez-doc

Adding Advisory CVE-2020-24490 for bluez-doc

added in https://github.com/wolfi-dev/advisories/pull/750


Can't extract mesh with exract_mesh.ipynb

I tried to extract the mesh with the ipynb code, and have the same error messages while searching tight bound of the object as #114 mentioned.
But after I changed two lines of the second block into :
embedding_xyz = Embedding(10)
embedding_dir = Embedding(4)

It showed up the following error messages instead:
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
/tmp/ipykernel_19394/55603309.py in <module>
     34 vertices, triangles = mcubes.marching_cubes(sigma, sigma_threshold)
     35 mesh = trimesh.Trimesh(vertices/N, triangles)
---> 36 mesh.show()

~/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/trimesh/base.py in show(self, **kwargs)
   2480         """
   2481         scene = self.scene()
-> 2482         return scene.show(**kwargs)
   2483
   2484     def submesh(self, faces_sequence, **kwargs):

~/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/trimesh/scene/scene.py in show(self, viewer, **kwargs)
   1050         elif viewer == 'notebook':
   1051             from ..viewer import scene_to_notebook
-> 1052             return scene_to_notebook(self, **kwargs)
   1053         else:
   1054             raise ValueError('viewer must be "gl", "notebook", or None')

~/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/trimesh/viewer/notebook.py in scene_to_notebook(scene, height, **kwargs)
     65
     66     # convert scene to a full HTML page
---> 67     as_html = scene_to_html(scene=scene)
     68
     69     # escape the quotes in the HTML

~/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/trimesh/viewer/notebook.py in scene_to_html(scene)
     34         resources.get('viewer.template.zip', decode=False),
     35         file_type='zip')['viewer.html.template'].read().decode('utf-8')
---> 36     scene.camera
     37     # get export as bytes
     38     data = scene.export(file_type='glb')

~/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/trimesh/scene/scene.py in camera(self)
    642         if not self.has_camera:
    643             # will create a camera with everything in view
--> 644             return self.set_camera()
    645         assert self._camera is not None
    646

~/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/trimesh/scene/scene.py in set_camera(self, angles, distance, center, resolution, fov)
    559             rotation=rotation,
    560             distance=distance,
--> 561             center=center)
    562
    563         if hasattr(self, '_camera') and self._camera is not None:

~/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/trimesh/scene/cameras.py in look_at(points, fov, rotation, distance, center, pad)
    327     # Transform points to camera frame (just use the rotation part)
    328     rinv = rotation[:3, :3].T
--> 329     points_c = rinv.dot(points.T).T
    330
    331     if center is None:

ValueError: shapes (3,3) and (0,) not aligned: 3 (dim 1) != 0 (dim 0)

May I ask how do I fix this problem ?

Hmm... The error messages are gone by now, It works again.

This time error occurs at the final block(extract colored mesh), while the others seem fine.
The error messages are:
/home/mea303/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/torch/functional.py:445: UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument. (Triggered internally at  ../aten/src/ATen/native/TensorShape.cpp:2157.)   return _VF.meshgrid(tensors, **kwargs)  # type: ignore[attr-defined] Predicting occupancy ...   0%|                                                  | 0/4096 [00:00<?, ?it/s] Traceback (most recent call last):   File "extract_color_mesh.py", line 136, in <module>     out_chunks += [nerf_fine(xyzdir_embedded)]   File "/home/mea303/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl     return forward_call(*input, **kwargs)   File "/home/mea303/Documents/Python/NeRF_project/nerf_pl-dev/models/nerf.py", line 100, in forward     torch.split(x, [self.in_channels_xyz, self.in_channels_dir], dim=-1)   File "/home/mea303/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/torch/functional.py", line 156, in split     return tensor.split(split_size_or_sections, dim)   File "/home/mea303/anaconda3/envs/nerf_pl/lib/python3.7/site-packages/torch/_tensor.py", line 518, in split     return super(Tensor, self).split_with_sizes(split_size, dim) RuntimeError: start (0) + length (63) exceeds dimension size (42).

Hi, I corrected the issue #114 and also the corresponding code in extract_color_mesh.py. Can you pull the latest code and try again? I verified that it worked for lego scene.

Yes, It works now with the latest code.
Thanks for your reply and hard work !!!


Status change causes confusion

We have noticed that Mollie updates statuses through requests to our PrestaShop system. While this provides valuable information, it makes it challenging for our warehouse staff to keep up with the changes. Please see the screenshot below:

It updates the status even after the package has been marked as "Sent" ("Wysłane") (twice!), which disrupts the warehouse workflow. Is there any way to disable this update?
Environment

PrestaShop version: 8.1.7
Mollie module version:  6.2.3
PHP version: 8.1

Hi there @mariuszsienkiewicz,
We have checked this issue and tried to recreate it locally on our environments, however, everything seems to be working fine, but we were not able to prompt this issue.
That being said, we will need access to your shop to debug the issue. Can you provide the Back Office and FTP credentials?
If you have a development environment, that would be even better. That way, we can work on the issue without disturbing the live store.
You can add the credentials here - https://privatebin.net/ and share the link via email at<EMAIL_ADDRESS>Also, please attach logs from the Mollie dashboard.
Thanks!
Best Regards,
Invertus Support team.

@mariuszsienkiewicz,
As this was not updated for a couple of weeks, I am closing the issue.
If you decide to get back to it, please post a reply here and we will continue from where we left of.
If you have any questions, please let me know!
Best Regards,
Invertus Support team.


Vanilla Webpack HMR

This replaces react-hot-loader with vanilla webpack HMR as per Dan
Abramov’s latest suggestions (i.e. sunsetting react-hot-loader and
react-transform). I am not 100% sure that redbox-react is working
properly. However, the project does hot reload in development.

@rowellx68 any thoughts? Not sure redbox-react is functioning properly.

HMR works well, but you're right about redbox-react not working.

@rowellx68 should we just drop redbox react then?

It may be best to do so until a solution can be found

@rowellx68 Do you have time today to send a new PR for this? Currently tied up with client work.

@jaredpalmer is this branch ready to merge to master?

LGTM


UI for alidns provider in globaldns

Able to use alidns(Alibaba Cloud DNS) as a provider option in the UI.
Similar to route53, supported configurations include rootDomain,accessKey,secretKey
Related backend issue: https://github.com/rancher/rancher/issues/17838

Version: Master 2.2 (2/13/19)
Tested the UI. Confirmed I can create, edit, delete an Ali DNS GDNS provider.
Inspected HTTP/API to ensure this looks correct.
Further testing will be done in the linked backend issue.
Initial creation (POST)
alidnsProviderConfig: {accessKey: "acessKey", secretKey: "SecretKey", rootDomain: "myroot.alidns.com"}
  accessKey: "accessKey"
  rootDomain: "myroot.alidns.com"
  secretKey: "SecretKey"
description: "description."


Offices activity feed logic fix

Fixes activity feed logic to only display when tags are present.
Changes

Updated 'src/sub-pages/_single.html' to display activity feed only when tags present.
Updated 'src/offices/_single.html' to display activity feed only when tags present.
Updated 'src/sub-pages/_single-grandchild-pages.html' to display activity feed only when tags present.

Test

Visit 'http://localhost:7000/offices/privacy/' and observe the activity feed.
Visit 'http://localhost:7000/sub-pages/civil-penalty-fund/' and observe the activity feed.

Review
@jimmynotjim
@anselmbradford
@KimberlyMunoz

LGTM :+1:

:+1:


Add namespaces to Druid segments within a data source

Motivation
Currently, Druid versions segments by their data source, covered interval, and an arbitrary version string (usually the time at which they were written). However, for cases where users want to be able to ingest and query data from multiple sources or selectively update subsets of their data, this requires intermediate processing or over-processing. To support these use cases, we can introduce the concept of a namespace to shard specs and VersionedIntervalTimelines, versioning namespaced shard specs by their data source, covered interval, namespace, and version string. This would allow data sources to be transparently populated from multiple input sources, with overshadowing and atomic updates continuing to function within the context of a name space without affecting data in other name spaces and without affecting the behavior of non-namespaced segments.
Proposed changes
The proposed changes primarily fall into two buckets:
First, modify the PartitionChunk and ShardSpec classes to add the methods default Object getChunkIdentifier and default Object getIdentifier, which simply return the chunk number and partition number, respectively. Further, modify the SegmentId and SegmentDescriptor classes to add an identifier. From here, all calls to ShardSpec's getPartitionNum should be replaced with calls to getIdentifier and all SegmentDescriptor/SegmentId creations updated. Namespaced shard specs can be created that approximate existing shard specs (e.g. a NamedNumberedShardSpec can be created that duplicates the logic of a NumberedShardSpec with the abuts and compareTo methods updated to check for matching name spaces as well). Additionally, real time ingestion specs (which don't allow specifying a shard spec directly) can be updated to optionally take a name space. These changes are transparent to existing code, except for a small performance hit of comparing Objects instead of ints.
The other piece of the puzzle is to introduce a NamespacedVersionedIntervalTimeline that similarly apes the logic of VersionedIntervalTimeline with a few key changes. Primarily, NamespacedVersionedIntervalTimelines can contain a map of string (namespaces) to VersionedIntervalTimelines (timelines for each namespace). Adding, removing, and overshadowing segments and partitions can then be done in the context of the appropriate namespace while look ups can be done across all namespaces. VersionedIntervalTimelines in CachingClusteredClient, BrokerServerView, etc. can then be replaced with NamespacedVersionedIntervalTimelines without affecting any non-namespaced segments (since they'll all be added to the default namespace and thus the same underlying VersionedIntervalTimeline, as they currently are).
These changes should be entirely transparent to users who aren't interested in using them, since all existing behavior will be unchanged. For users who do want to use namespaced shard specs, they can simply specify the appropriate shard spec in their ingestion config (or for real-time ingestion specs, a name space) and namespaced shard specs will be created. These shard specs will only extend or overshadow data with same data source and name space, but all segments with a given data source will be queried together, regardless of name space. Here, this proposal takes advantage of the fact that Druid already handles cases where some dimensions or metrics are available in certain segments for a datasource but not all of them. Metrics are inferred to be 0 and dimensions are inferred to be null. If there are shared dimensions between namespaces, post aggregators can be used to return combined results for any given combination, even if not all metrics or dimensions are present in all name spaces.
Rationale
The primary motivation for this proposal is to support scenarios where users produce data from multiple sources but wish to query this data as if it were a single table. Although there are ongoing efforts in the Druid community to address this via joins  #(8728) and union data sources, both approaches have certain drawbacks. The initial phases for join support envision supporting joining enhanced lookup-style dimension tables onto data sources, not joining data sources, and union data sources require all unioned data sources to have identical schemata. Namespacing allows multiple logical data sources to be merged, even if they have differing schemata. The obvious downside to namespacing is that this merging must be performed at ingestion time and doesn't support arbitrary joining at query time.
Operational impact
These proposed changes modify many internal APIs, but do not deprecate or remove any external features or behavior.
These changes are transparent to non-namespaced segments and data sources, meaning that clusters can be upgraded and downgraded without issue. Once namespaced segments are created, data sources cannot be downgraded (whichever namespace was lexicographically last would overshadow all other namespaces).
We have been running these changes in production for ~12 months without a noticeable affect on latency and performance. Of course, our implementation and a community implementation will likely differ to some degree to account for the broader use cases throughout the community. It is possible that this change would introduce small latency regressions for some use cases due to the move to comparing objects instead of ints for partition numbers/identifiers.
Test plan
There are two main pieces of this proposal that need testing: first, that namespacing works as intended, and also that there are no observable changes for users who do not adopt namespacing.
For testing namespacing, we would want to test the following scenarios that new namespaced segments with a higher version should overshadow only existing segments with the same namespace and that namespaced segments with the same datasource are queried across namespaces when the data source is queried. We would also want to test that all current realtime and batch ingestion mechanisms can correctly create namespaced segments.
For testing that there are changes required for non-namespaced segments, the existing Druid tests should be sufficient (e.g. if all our existing tests work without changes, we can be confident that existing use cases will be unaffected).

I  read your  email on dev list and  consequently https://medium.com/pinterest-engineering/powering-pinterest-ads-analytics-with-apache-druid-51aa6ffb97c1 . Thanks, that was a good  read.
From that reading, my understanding of your use case is that you could have multiple dataSources which have same set of dimension columns but different  metrics columns. I wonder how difficult
was it to improve "union query" handling so that it could accommodate this use case.
I see that you noticed that current union query handling couldn't  work with dataSources of  different schema. Did you try to improve union query handling to make that work and encountered a technical difficulty and led to conclude that namespace feature was simpler to do?

We have both differing dimension and differing metrics between the namespaces. I investigated modifying union datasources as well, but there were a number of problems:

At the time (and perhaps still), union data sources were queried in serial, not parallel. This is obviously fixable.
Implementing this feature with unioned data sources required implementing query logic to handle disjoin schemata, which namespacing did not.
We've scaled this from a handful of namespaces per data source (where union data sources probably could work) to hundreds for a few (I'm not sure how easy managing 100+ data sources in a cluster would be, but this may not be a major concern)

Since more changes were required for making this work with union datasources, we went with namespacing (and it was fairly simple to implement the changes described above). I see merit in both approaches.

@JulianJaffePinterest thanks for the proposal and a nice blog post. The problems of the union query you mentioned above are correct and still exist. But, I believe we should address those problems someday to provide all functionalities supported by the SQL union query. Even if those problems were addressed, would this namespace feature still handle some use cases where the union query cannot? I'm wondering whether their use cases overlap too much or not.

I'm also curious exactly what namespaces are for. AFAIK, Druid currently allows users to ingest data into the same datasource from multiple sources. Those sources can have different schema and Druid will handle it at query time by filling missing columns with nulls.

It seems like an interesting application of namespaces is that it allows you to do reingestion and retention policies on a subset of a data source.  For example, you could have a data source that contains customer data from customers in several pricing tiers. Querying should work the same for all customers, but you may want to load more history from customers who pay more (either in the "setting historical load rules" sense or the "actually killing old segments" sense), or you may want to run native batch reingestion on cheaper customers to reduce queryGranularity of their older data without needing to also rewrite the data from the higher tier customers.
(Moving a customer between tiers in this model could still be a challenge, though, unless you can create a batch ingestion job that writes to a couple namespaces.)

I have read the proposal and my understanding is that you are trying to index data form the same source with the same interval of time but you want to break it into more sub tasks to make it parallel is that the main pain point that pushed you to implement this name spacing  ? OR  is it because you have some data reprocessing and you want to re-process only sub part of the data and the only way know / filter this data is what you are calling namespace ? In my opinion for both cases i would agree with the general sentiment that this is better done in the Query layer as standard union and would be a wonderful contribution that can be used by many other use cases.

@JulianJaffePinterest thanks for explaining the difficulties. However considering the use case at hand and the alternatives available, order wise, I would first explore fixing union queries which has more benefits. However if a technical limitation is hit that didn't allow problems to be resolved then namespace as a secondary option would be the necessary choice.
@glasser if you tried one dataSource  for all customers and found it to be too problematic due to scale etc and really needed per customer-tier QoS, then per customer-tier dataSource would probably be the right fix in that situation.

@himanshug Yeah, I don't know much about union queries and that might be a better way to go.

Let me explain our use case, which will hopefully clarify some of the questions here:
We have multiple independent pipelines that produce data we serve as a single data source (to give an oversimplified example, you can imagine that one pipeline calculate clicks and impressions while another pipeline calculates conversions). The outputs of these pipelines are queried together, and they share some dimensions and have some unique dimensions, as well as unique metrics. We also produce intra-day computations of these data sets that are updated with daily true-ups. The output of an intra-day run needs to overshadow any existing output for the time it's running for, which can be handled by overshadowing, but the intra-day output of a conversion pipeline shouldn't affect the output of any other pipeline, so simply synchronizing on version and using a linear shard spec won't work. Union data sources, if they were performant, could likely handle this without too much trouble since we're only discussing a few distinct input sources. In our case, most queries actually cover over a hundred namespaces. At that scale, I'm not sure how performant unioning would be (possibly fine). The main benefit namespacing provides is that clients don't need to know or care about these details, nor do they need to know which data sources to union. I agree with the overall point that this all could be done in the query layer (and perhaps even should be done there).

Yeah, I agree with your concerns about 100+ dataSource scale in union. My guess is that it could still be handled by pushing the union dataSource to Historicals . Similar to single dataSource case, Broker would find segments to  be  scanned for multiple dataSources  in union, and push the union along with segments for each dataSource to right Historicals  (current approach is to split queries by dataSource when they  are sent to historical,  done serially .. even if done in parallel, that would result  in too many queries to downstream Historicals). It would likely require introducing a new QuerySegmentSpec similar to MultipleSpecificSegmentSpec  but that lists segments for multiple dataSources. If done that way, then union query handling would be very close in terms of processing to that  of a single  dataSource and scale  wouldn't have too much of an overhead due to query being a union query.
It is, of course, possible that there would be technical glitches in implementing above, but we don't  know that yet.

The main benefit namespacing provides is that clients don't need to know or care about these details

That problem is a lot more cosmetic . It  could either be handled by  introducing  concept   of "Virtual DataSource"  at the api layer on top  of Druid that typically customers have or could be implemented as a feature in Druid itself.

@JulianJaffePinterest thanks for more details.

The output of an intra-day run needs to overshadow any existing output for the time it's running for, which can be handled by overshadowing, but the intra-day output of a conversion pipeline shouldn't affect the output of any other pipeline, so simply synchronizing on version and using a linear shard spec won't work.

Just FYI, you can actually do this with the segment locking and the task audit logging. Since you can track what task created what segments from task audit logs, you can overwrite only the segments what you want with segment locking. (The task audit logging is deprecated because we haven't found a good use case for it. If this is a popular use case, then we may need to consider supporting it back. See https://github.com/apache/druid/issues/5859 for details.). But it requires you to track all segments outside of Druid and I guess this would be more complex than the proposal.
As long as there is no unique use case where only this proposal can address, I'm more inclined to fixing the union query properly because we have to do it anyway. As @himanshug mentioned, that could address most of the problems mentioned here even though there is at least one more potential issue with query performance. The segment balancer uses a heuristic that the segments will be more likely queried together as their intervals are closer. Based on this heuristic, the segment balancer assigns the segments of close intervals into different historicals so that they can be processed in parallel. This assumption doesn't apply to the union query. However, I don't know what the impact of this would be.

That problem is a lot more cosmetic . It could either be handled by introducing concept of "Virtual DataSource" at the api layer on top of Druid that typically customers have or could be implemented as a feature in Druid itself.

@himanshug this is true. I guess this could be the view in SQL.

is it because you have some data reprocessing and you want to re-process only subpart of the data and the only way know / filter this data is what you are calling namespace
@b-slim Right now we are facing this issue Where we have multiple customers data in single datasource and want to reingest specific customer data. How can we do it?

is it because you have some data reprocessing and you want to re-process only subpart of the data and the only way know / filter this data is what you are calling namespace

@b-slim Right now we are facing this issue Where we have multiple customers data in single datasource and want to reingest specific customer data. How can we do it in query layer?

@skyrocknroll You can not do ingestion via the query layer, that is not what i said. What you can do and trying to explain is that it is better to have a datasource per costumer, that will lead to better overall management and query performance. If you need to have a view on the top of those multiple customers then we can add something in the query path like a global view to allow that, but in any case you need to do a separate ingestion for each customer.

@b-slim Thank you for the response :+1:


docs: split readme into subsection and document missing helpers

feat: add request and response helpers
feat: add url utilities
docs: document all builtins in readme

🔗 Linked issue
#420
#423

❓ Type of change

[x] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
/!\ Careful this PR is against #427 , not main .
This update the readme to improve the readability and document the missing helpers.
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

Thanks! (I have rebased your changes to make it mergeable against main and iterate quickly)


Remove lxd.tar.xz from history

Would it be possible to remove lxd.tar.xz from this repo?
It is pretty easy to do with something like https://rtyley.github.io/bfg-repo-cleaner/,
the only problem is that you need to rewrite history.
But I would argue it's worth it, since this should never been part of the repo
and will speed up every clone in the future which is created from this repo.
git clone --mirror git@github.com:lxc/pylxd.git
java -jar ~/Downloads/bfg-1.14.0.jar --strip-blobs-bigger-than 50M pylxd.git

Rewriting git history isn't really something we'd consider at this point. A possible workaround is to do a shallow clone:
git clone --depth=1 https://github.com/canonical/pylxd.git


beforeunload event not working on Safari Mobile

On the remote side, the beforeunload event is subscribed so that conn.disconnect() could be called, to ensure the connexion to master closes when you close the window :
https://github.com/topheman/webrtc-remote-control/blob/master/packages/core/remote/src/core.remote.js#L69-L75
It seems the beforeunload event is not triggered on Safari Mobile. Is there a way to fix this ?

One way of fixing this could be to send a heartbeat on the datachannel from remote to master with a trace like this :
{
  "__HEARTBEAT": "2022-04-24T16:30:23.006Z"
}

This shouldn't be re-emitted on the data event to the end user
A heartbeat could be sent e every 5s or 10s
On master, a connexion could be removed after 2 periods of heartbeat have passed without any heart beat message

Questions :

Only do that on devices that don't support beforeunload ?
What about networking problems and if we disconnect a client that shouldn't be disconnected ? Find use cases


iOS, preloadSimple: "Asset Not Found" on http assetPath

Steps to reproduce
Try this:
window.plugins.NativeAudio.preloadSimple('music','http://incompetech.com/music/royalty-free/mp3-royaltyfree/Furious%20Freak.mp3',function(a){console.log("ok",a);},function(b){console.warn("no",b);});

(Or, upload your own MP3 to your own server and point to that path.)
Expected result
The file has been preloaded so that I may play it back
Actual result
The console logs the warning no – "(NATIVE AUDIO) Asset not found. (http://incompetech.com/music/royalty-free/mp3-royaltyfree/Furious%20Freak.mp3)" .
Notes
This was just tested in iOS Simulators for 8.x, 9.x, and 10.x. None of them work.
My only guess is that [[NSFileManager defaultManager] fileExistsAtPath : path] does not check actual external URLs, so the preloadSimple. I've tried with a 3-minute song as well as a 5-second 'sound effect', and I receive the same error each time.

Same here. Any feedback on this issue?

I'm having the same issue, any news or workarounds?

Is this issue solved?

Same issue here on Android

java.io.FileNotFoundException: www/http://<IP_ADDRESS>:8080/calls/...

www/http://<IP_ADDRESS>:8080/calls/... is not a valid local file path.
This plugin does not support remote audio resource, yet. So, you need put the assets together with your js code.

@floatinghotpot I agree.  But the documentation does state that it supports this.  Wasn't until I looked at the source that I confirmed it wasn't supported  Certainly is misleading

@floatinghotpot is it planned to be supported ? I'm looking to build an online radio app

Yes would be nice to know, and also good to remove it form documentation.

spend the last two hours "troubleshooting" this thinking i had an issue on the server, because I believed the documentation when it said "relative path or absolute URL (inluding http://)" ...

@rickybrown same here, which was frustrating given the docs. I ended up using the Media library and so far it's working as expected.

Just bumped into this today while working with Ionic, the docs still says "assetPath | string | the relative path or absolute URL (inluding http://) to the audio asset." (inluding is another typo in the docs :))
I'm unable to play audio from external source (e.g. Firebase) and was wondering if there are any news on this? Am I doing something wrong or if not, is there a plan to support external source any time soon? Thanks!

@lina94 I had this issue a long time ago, I think this library is not supported anymore. I solved this problem using cordova-plugin-media

Anyone got any solution to play audio file using URL ?

Anyone got solution to play audio file using URL ?

It looks like music from remote servers was never supported. I'm closing this issue as won't fix.


Davos

Project
Davos.xyz
Description
Davos Protocol presents a refreshed approach to collateralized debt positions (CDPs) by directly addressing the inherent constraints of conventional DeFi CDPs. Central to this is our commitment to a balanced monetary strategy and equitable borrowing rates, ensuring users' interests are at the forefront, thus enhancing DeFi's appeal to a wider audience. Crucially, users can capitalize on their collateral's growth potential, safeguarding their prospective gains.
At the core of our solution is the integration of Liquid Staking Tokens (LSTs) and the upcoming inclusion of a wider array of reward-bearing tokens, notably Liquid Restaking Tokens (LRTs). These tokens are key to creating DUSD, our omnichain stablecoin. Through our CDP system, users can unlock the extensive potential of their staked assets, leading to enhanced returns. By facilitating the staking and farming of DUSD, the Davos Protocol creates pathways for compounded yields, thus enabling users to amplify their financial growth in the DeFi ecosystem. Our commitment to DeFi composability ensures seamless navigation and maximization of returns for our users.
Forked from the established MakerDAO foundation, Davos Protocol offers seamless functionality across multiple Proof-of-Stake Network terrains, enabling fluid DUSD transitions between them. Such interoperability unveils a plethora of opportunities across diverse networks, elevating users' prospects. Furthermore, with Davos Governance Token (DGT) steering our direction, we emphasize community-driven governance, reinforcing our commitment to a truly decentralized environment.
In essence, Davos Protocol positions itself at the forefront of DeFi innovation, merging the reliability of traditional finance with the dynamic features of decentralized finance. Our platform empowers users to compound their earnings by using LSTs, LRTs and other reward-bearing tokens as collateral to borrow DUSD. This enables participation in a range of yield-generating activities within the Davos DeFi ecosystem, fostering an environment where users can enhance their yield potential and financial trajectory. Davos Protocol thus stands as a catalyst in advancing DeFi, focusing on user empowerment and financial growth.
Please provide the project scope.
Safe Apps
Select a primary category of your project.
DeFi
Select secondary categories of your project.
Dashboard
Project logo

Value proposition
No response
Contact
No response
Project URL
https://davos.xyz/
Github / Dev Docs
https://github.com/davos-money/davos-contracts
Twitter
No response
Primary integration
No response
Packages
No response
Modules / Guards
No response
Smart Accounts
No response
Networks
No response
Can you create a Safe via the interface?
None
Can you import an existing Safe via the interface?
None

@Sk1mer12 - have you followed our process (https://docs.safe.global/safe-apps-sdk/release) to be listed as a Safe App on our Safe Wallet interface? This is a prerequisite to be added to the Eco page.


Don't cast empty string to Boolean if prop types include String and Boolean (fix #4538)

Additional info in issue  #4538

Thanks!


Fixed issue 9

Resolver now accepts data for POST, PUT and DELETE requests

Coverage remained the same at 88.298% when pulling 948b8d2d3fe2ae374986f126dcfc3c0338754f01 on fix-issue-9 into e1d9930b33677297c221975451479b7ab505d17b on master.

This PR allows developers to use POST, PUT and DELETE in some MKM endpoints. Anyway, developers must not write XML on their own (or through a third-party library) because it's better to provide a clear way to use these endpoints.
I suggest to implement some internal utilities (such as a kind of Serializer) so that developers can provide just a plain python dict (or whatever) to upload or query their stuff to MKM.
By the way you can merge the PR but point in your roadmap that a Serializer (or something similar) is required (create a new issue for that).


Collaborative Memos

Describe the solution you'd like
A lot of people are comming to Memos from Google Keep. Memos can be a great alternative but lacks in term of collaborative feature.
As of now, there is no way to make to people edit the same memos. ( Even Admins can't modify other memos)
I hope that together we can discuss what is the best way to add collaborative editing to Memos.
Type of feature
User Experience (UX)
Additional context
Current code
In the current code, the ability to edit is defined by :

const readonly = memo.creator !== user?.name;
const allowEdit = !props.readonly && memo && currentUser?.name === memo.creator;

Which makes the creator the only one capable of editing the memo.
Ways of adding collaborative features
Workspace Editing
As i previously mention in a PR ( #3673), one of the easiest way is to let everyone in the same workspace edit all "workspace memos".
Such a "feature" as i implemented will not resolve the "admin" problem on public and private memos. But is easy to add and don't touch the database models.
Collaborators Field
An other way would be to add a "Collaborator" field to each memos.
Then a UserA could add UserB to the memo.
UserB would have almost the same permissions as UserA. Editing the content of the memos but not the visibility nor add collaborators.
This is a quite robust way of dealing with collaborative work but changes to the database will be needed.
CollaboratorsPermissions
This part is a upgrade for the Collaborators Field feature. What we could do is add a permission system. (Read/Write/Admin)
It would work like that :

READ : Can see the memos (even if its visibility is Private) and can comment.
WRITE : READ + can edit the content of the memo (e.g: check boxes, add task to list)
ADMIN : WRITE + can change the visibility, add collaborators, delete the memos... (anything that the creator can do)

Instead of using a field in the memo (which could eventually become too large) we could use an other table in the database. :

memoId
userId
permission

integer
integer
integer

Permission is a number representing the permission :

READ : 0
WRITE : 1
ADMIN : 2

Using 0 for READ let us use the "permission" number as a "allow edit" bool value
(the following code is not a implementation, just a example)
const allowEditing = Collaborators(memo).getPermission(userId); // => 0/1/2 or undefined
// 0 and undefined act as Falsy values
if (allowEditing) {
  // here we are sur to edit because 1 and 2 are "true" values
}else{
  // Here we know for a fact that we won't be able to edit.
}

Obviously, the server host (and users set as Admins) will have the ADMIN permission on each memos.
UI
In terms of UI, this will add :

a "collaborator" button that opens a small modal. With the list of collaborators and each permission (with selectors to change their permissions)
a button to hide collaborative memos from the Home/Explore page. (optionnal)

Issues related :  #3754  #3708

I started to work on it.
Here is the repo : iziram/memos#collaborators
Worked on a bit of UI :
https://github.com/user-attachments/assets/8e2afeb5-171d-4d0a-9bee-889a9ee18a7a

super excited for this!
As a fellow "moving away from Keep", this will solve most of the gaps I have with my wife and I sharing to-do lists and notes, etc.


How to change routes from the main process

I want to change the current app route from the user menu. I guess it's quite common but couldn't find it in the docs.
Currently I've use loadURL, as I don't have access to React Router from the main process:
{
      label: '&Users',
      submenu: [{
        label: 'List',
        accelerator: 'Ctrl+R',
        click: () => {
          this.mainWindow.loadURL(`file://${__dirname}/app.html#users`);
        }
      }]
    },

It doesn't seem to be the proper way. I didn't see any info or code in the example. What is the proper way? Using IPC?

IPC is definitely the simplest route. Using react-router, the basic idea is

send a message from main to renderer with the URL you'd like to show
renderer receives the message and sets window.location
react-router responds to the change

Note that, in #2, you could use router navigation like push() and replace() rather than setting window.location if you want to control how the URL history is handled.


Device connected successful,but device disconnect after disconnected USB

Device connection is successful, the connected devices list there are two devices, but after disconnected USB, the two devices are gone.
This phone and my computer can transfer data via the same WIFI.
Maybe WIFI ADB is not compatible with my phone?
phone:moto x style
pc:win8.1

@treycc I have bad news for you, the problems related with the device connection once the device has been connected over WiFi is something we can't fix from our plugin. Review if you are using the last adb version of if there is any problem with your device or your WiFi configuration. From my side it's impossible to fix this issue :(

@pedrovgs thanks

I'm so sorry. I'd like to improve this, but I can't improve the Android Debug Bridge from my side.

@pedrovgs i try to check whether there is problem with Android Debug Bridge,or try an other phone


Booleans converted to Numbers

Hey there. Thanks a lot for making this repo, very helpful. Wish Amazon provided an easy way to do this!
Noticed an issue though: seems like Booleans are converted to Numbers.
Here's an entry in my source table:

...and now the destination table:

Note that the public and the tiles[0].trigger.sync parameters have changed from true to 1. Fortunately, false becomes 0 in other cases, so we can probably guess what's happening.
Should be easy enough fix manually on my end with a DynamoDB query, but thought you should be aware!

Relevant discussion here: http://stackoverflow.com/questions/32109154/boolean-converted-to-decimal-decimal-object-in-boto-dynamodb-requests


Build error for Lumina Desktop in Ubuntu

I'm trying to build Lumina Desktop in Ubuntu 16.04 as mentioned in Lumina website. While running make command, I got following error.

pages/page_defaultapps.cpp:68:3: warning: identifier ‘nullptr’ is a keyword in C++11 [-Wc++0x-compat]
QTreeWidgetItem *group = nullptr;
^
pages/page_defaultapps.cpp: In member function ‘virtual void page_defaultapps::LoadSettings(int)’:
pages/page_defaultapps.cpp:68:28: error: ‘nullptr’ was not declared in this scope
QTreeWidgetItem *group = nullptr;
^

How can I overcome this issue? Is there any flag that I need to enable when running make command.?

Fixed this problem by replacing nullptr with NULL.


Update project file to reflect minimum swift 5.2 requirement

I think the README should be updated: show the minimal version and update the snippet?


Remove use_cleargrads from tutorial

Remove use_cleargrads from tutorial

Ref: https://github.com/pfnet/chainer/pull/2549

LGTM


How to catch URL / Text from share intent

I am building an app which can catch all the URLs from share intent and save it to a DB. but I can only share text not URLs.
Also, each share opens a new instance of the app.

hi @niteshkumarniranjan
are you still experiencing the issue with the latest Flutter stable release?
if so, please provide the output of "flutter doctor -v"

I haven't checked yet.
using https://github.com/d-silveira/flutter-share as of now.

Hi @niteshkumarniranjan !
As you found the solution for now, closing this issue.
However, feel free to open a new issue if you still encounter the same problem.


adding FakerDataProvider

Connected to #30

hey @drager
I made a few changes. just adding the feature of accepting a FakerDataProvider to the Faker class.
right now FakerDataProvider only accepts a LoremDataProvider.
also added a FakerDataProviderFa which does provide farsi lorem text.
review the code if it looks ok let me know to do the same job with the other parts like address, person, etc.

did you get a chance to look at it

Did you get a chance to look at it?

Just looked at it. Thanks! Will make sure the build passes before merging.

have you published it? because I don't get the last version when I include it in pubspec.yaml dependencies

@easazade I have not published it just yet

@easazade Published in 2.0.0-rc-1


[usecase-linux] Update test status for SystemIMEs

Feature https://crosswalk-project.org/jira/browse/
XWALK-3823 has been resolved, change test status from
"designed" to "approved"
Impacted tests(approved): new 0, update 1, delete 0
Unit test platform: Crosswalk Project for Linux <IP_ADDRESS>0
Unit test result summary: pass 1, fail 0, block 0

Unit test platform: Crosswalk Project for Linux <IP_ADDRESS>0

Where do you get this package?

@zqzhang
I got it from http://pan.baidu.com yesterday morning, but the package was removed form the website shortly after I got it. And I will retest it with the new package.

@zqzhang
I have retested it with new packge in http://pan.baidu.com , test also got pass


Itemset doesn't update if calculation that is part of itemset expression updates

See #678 and this attempted workaround (which is also not working, and that's more surprising)
https://docs.google.com/spreadsheets/d/1QtVC6TQ1Z2YWRARnUY66UBy-HKUf-zYTS60Y3K3aKfw/edit#gid=0

Correction: the workaround is working. I made a mistake in the calculate expression.


Flow plugin broken

The plugin is broken for 2 reason:

The API is out dated, we have to update the plugin to comply to the current architecture (use onData).
The plugin doesn't receive a full and valid JSON file. The content is cut before the end.
When looking into the console, we can see a promise which fails without any error. i tried to reproduce in a bash terminal, and when started with yarn flow, the problem also occurs. I suspect the problem not coming from Molecule itself.


Ubuntu SAMBA: Cannot delete files with Atom editor

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
I store almost all of my files on an in-home VPS that I run so that I can have them up 24/7. To access these I have a samba server on my VPS setup so that I can easily access the files via Windows. Whenever I'm using the Atom editor on the samba file system it seems to not work because it cannot detect a Recycle Bin. I have to manually delete the file in File Explorer for it to work. I tried changing the File System Watcher settings under Core Settings to see if it would have an effect but it didn't solve the issue.
Steps to Reproduce
Just try to delete a file on a Ubuntu samba server
Expected behavior: The file to delete like normal
Actual behavior: Popup message:
The following file couldn't be moved to the trash.
\\NETWORK\share\node\web\extensions\test.js
Is there a Recycle Bin on the drive where the files are stored?

Reproduces how often: 100% of the time, I have to delete in the Windows File Tree
Versions
Windows 10 Pro

Atom    : 1.26.0-beta0
Electron: 1.7.11
Chrome  : 58.0.3029.110
Node    : 7.9.0

apm  1.19.0
npm  3.10.10
node 6.9.5 x64
atom 1.26.0-beta0
python 3.6.4
git 2.16.0.windows.2
visual studio

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/3306. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Admin via PowerShell?

Where's the information regarding adding admins to groups via powershell? If I have a large number of groups in a large organisation I want to be able to add a user as admin to many groups in bulk.

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

ID: dfa3130f-f429-4305-5114-915d1ebb9762
Version Independent ID: 5902f898-f078-6025-8dbc-35d121d80ec9
Content: Add, block, or remove Yammer users
Content Source: yammer/manage-yammer-users/add-block-or-remove-users.md
Product: office-online-server
GitHub Login: @IrenePasternack
Microsoft Alias: v-irpast

@officedocsbot assign @mypil

@angoo-atea - Thank you for submitting feedback.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:  https://docs.microsoft.com/office365/admin/contact-support-for-business-products
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.

Hi @mypil, many thanks. I've now opened a support request: [Ticket #:15065739] "add specific users as admin to specific Yammer groups in bulk via the Yammer REST API and PowerShell"
I've asked the engineer to determine whether this functionality is available, and if not when it will be added.

@angoo-atea - Thank you for this additional information. Let me also tag the doc owner on this issue to get some insights to your query.
@IrenePasternack - Can you please share your insights on this issue?
Thank you.

The REST API documentation can be found at developer.yammer.com/docs.  There are some sample PowerShell scripts for working with Yammer at TechNet at https://gallery.technet.microsoft.com/office/Create-a-Yammer-Group-56b0a4a0.

We don't support setting admins for Yammer groups using PowerShell.
Our  long-term direction is to make all groups connected in Yammer, and then the standard Office 365 Groups APIs will work. Until then there are some holes in the capabilities and these need to be raised via Design Change Requests (DCRs) through support cases, so you’re on the right track by opening a support request.
Irene
From: Joyce Y<EMAIL_ADDRESS>Sent: Thursday, June 27, 2019 4:07 AM
To: MicrosoftDocs/OfficeDocs-O365ITPro<EMAIL_ADDRESS>Cc: Irene Pasternack (Steyer Associates Inc<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-O365ITPro] Admin via PowerShell? (#583)
@angoo-ateahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fangoo-atea&data=02|01|v-irpast%40microsoft.com|40b393ce0b5b45ca40b508d6faef9164|72f988bf86f141af91ab2d7cd011db47|1|0|636972304176044825&sdata=teRqGo3jMRYdZnvieG2s88JdHEGAdD5kgpJBwKzPvCA%3D&reserved=0 - Thank you for this additional information. Let me also tag the doc owner on this issue to get some insights to your query.
@IrenePasternackhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIrenePasternack&data=02|01|v-irpast%40microsoft.com|40b393ce0b5b45ca40b508d6faef9164|72f988bf86f141af91ab2d7cd011db47|1|0|636972304176044825&sdata=wtM1KYPnEggjpqUhK%2BoASGSuMErFaPAtvhVUau%2F6e2c%3D&reserved=0 - Can you please share your insights on this issue?
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-O365ITPro%2Fissues%2F583%3Femail_source%3Dnotifications%26email_token%3DAJFIDIZVVZHS633IY7REQGDP4SNNBA5CNFSM4H3IQFLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYWY3GI%23issuecomment-506301849&data=02|01|v-irpast%40microsoft.com|40b393ce0b5b45ca40b508d6faef9164|72f988bf86f141af91ab2d7cd011db47|1|0|636972304176054792&sdata=kahh51NvrI5tQGD7joipkncYM%2FLHeJVTJkP%2FhQVIW98%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJFIDI7ULJ4RT667P7OORLLP4SNNBANCNFSM4H3IQFLA&data=02|01|v-irpast%40microsoft.com|40b393ce0b5b45ca40b508d6faef9164|72f988bf86f141af91ab2d7cd011db47|1|0|636972304176054792&sdata=6TVgWJxFx7hhrLIDIMWQPAKDthZI67WYQXsbtWkf3uA%3D&reserved=0.

@angoo-atea - From our understanding, the issue you raised has been answered by IrenePasternack. If you feel it hasn't been answered, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


Countdown and stopwatch have millisecond precision

The countdown or count up (stopwatch) you display should at least have millisecond precision (microsecond precision if possible).
so you have DDD:HH:MM:SS.mmm.mic
At least millisecond precision.
DDD:HH:MM:SS.mmm
Microseconds may not be needed, but if you can put it there, might as well.
https://twitter.com/Dziemborowicz/status/674106790481518592

Why is this needed?  You're never going to be able to start or stop the timer with that much accuracy.


fix format of freq/cpu time, handle zero total cpu time

This PR fixes format issue when CPU time = 0.

Cause: due to typo fmt.Sprint instead of fmt.Sprintf, exported value of v.CurrCPUTime and v.AvgCPUFreq contains %f.
Change: use the same standard strconv.FormatFloat instead
Cause: totalCPUTime = 0, avgFreq is NaN
Change: compute avgFreq equally for all core when totalCPUTime = 0

thank you @sunya-ch for catching up these! Would you please resolve the conflicts?


added more crypto functions

Lets get this started https://github.com/nearprotocol/near-wallet/issues/32.
I dont like how the base58 is used atm, but not sure what the protocol would be. Return uint8array, return b58 or return b64?
Up for first review, this is not final.

Hey wanted to clear this up to clear out older issues. This has been addressed in different pushes.


fix: updated typo in english cramers-rule

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝

@nhcarrigan Thanks a lot, you made my day🎉
Yes, definitely looking forward to contributing more. :+1:


tutorial needs to explain how to deploy wasm app using another webserver

Where in the docs did you come across this?
https://rustwasm.github.io/docs/book/reference/deploying-to-production.html
Describe what about it does not make sense
The tutorial needs to explain how to deploy your wasm app using another web-server.  The tutorial setups webpack dev server using a template so after following the tutorial new users who have no idea about web-pack will not no where to start to serve this client side app using another web-server like actix web.
Why does it not make sense?
Because a template is used that is already integrated with webpack-dev-server and a web-pack is used to bundle the files users new to web-development will easily get confused about these technologies. There needs to be more guidance on some of the frameworks used.
How could we improve it?
link you webpack getting started and explain what it does at a high level.
Extent the tutorial - section on deploying to production using eg Actix-web Or any other production capable web server
I would start by setting webpack.config to static
  output: {
    path: path.resolve(__dirname, "dist", "static"),
    filename: "bootstrap.js",
  },

That way you can see the bundle webpack is serving. I tried copying this static folder and configuring actix web to serve this directory - however this did not work.  I have no idea how to serve the app i built in the tutorial using another web server.
Currently
The index.html loads and i can see the button but there are console errors
bootstrap.js:1 Uncaught SyntaxError: Unexpected token '<'
DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/contentscript.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/inpage.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

not sure how to fix the error thats preventing bootstrap.js loading because it loads when i run it from webpack dev server

this is my attempt so far to serve the tutorial client side app using actix web
https://github.com/ta32/wasm-game-of-life-tutorial

https://github.com/realSuffix/wasm_game_of_life_actix
a person helped me to create a working example.


Add support for radial search on k-NN and Neural query types

Description
Add support for radial search on k-NN and Neural query types
Issues Resolved
Fixes #1226
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I see the parameters present in the API spec. How far are we from getting this via the code generator?

I see the parameters present in the API spec. How far are we from getting this via the code generator?

The query types (plus a couple others) have special deserialization logic for handling the fact they're "single key dictionaries", keyed on field, and in Java (and .NET) the field value gets flattened into the same class as the other query properties. So requires tweaking the spec to be consistent in how they're represented to be able to add special handling to the generator. It is one of the next things I'm going to look into, and will need to make sure the spec changes work for the people working on protobuf representation of the search api.


Mountable engine routes

Im trying to create a a mountable engine with devise on it, I've followed this tutorial: https://github.com/plataformatec/devise/wiki/How-To:-Use-devise-inside-a-mountable-engine
And everything works fine, except the routes. My engine is mounted in the route admin like this:
 mount C4::Engine => "/admin"

but when devise redirects the user (like when it hasn't signed in) it redirects to a path without the '/admin' prefix and gives me the usual No route matches [GET] /users/sign_in because the correct route is admin/users/sign_in.
I'm kind of new to rails mountable engines so It could be just me, is this a devise issue?

Ok, It seems I wasn't using the correct devise version, devise 3.5.1 works fine.

I think this should be reopened (?)
I am having the same problem using 3.5.6, downgrading to 3.5.1 fixes the problem however opens my app up to security issues

Reverting this commit solves the issue.