text:
Prepended text appears over a positioned element (add-on with z-index)

As you can see on thsi picture : http://imgur.com/sPyiz the prepended text is showing over the panel instead of being under.
This is because, the add-on class has a z-index set to 2.
Why this default value ? Can't we leave it to auto ?

Removed in 2.0-wip.

authors: Steren markdotto


text:
[portability] compile error on non-x86

Describe the bug
src/storage/seg/hashtable.c unconditionally includes x86intrin.h and thus fails to compile on non-x86
To Reproduce
compile as per build instructions, make -j fails
Expected behavior
builds successfully
Environment
macOS 12.1 (arm64, i.e. M1) with Homebrew clang version 13.0.0
Additional context
feel free to close (but please update the requirements in README.md) if pelikan is only intended for x86_64
Thanks!

we will remove the include because it is not needed, thank you for pointing out

Please reopen if other things are in the way.

source: gharchive/issue

authors: 1a1a11a thinkingfish varkappadev

repo: twitter/pelikan

license_type: permissive

license_source: github-api


text:
Added the case when there are untracked files to working-directory-is-clean condition in GitHelpers.

It should be cool to have personal files that you do not want to 'git add', right?

Allowing untracked files opens us up to human error, where you commit/publish/whatever, and you forgot to git add that one file.
I recommend for your use case that you add the "personal files" to your gitignore.
-1

authors: fizx pankajgupta

repo: twitter/standard-project

license_source: bigquery


text:
Remove totem dependency (torch now has its own tester)

Also fix contiguous grad

Closes #123

source: gharchive/pull-request

repo: twitter/torch-autograd


text:
Russian date formats do not parse out "real character" escaping single quotes, redux

c.f. https://github.com/twitter/twitter-cldr-js/issues/57
@KL-7 - it looks like the single-quotes around the г for "года" have returned.

Hey, thanks for flagging this. What version of the library are you using?

Hi there!
It looks like we are currently running 1.3.1, but will be running 1.3.6 after some infrastructure upgrades.
I can't imagine that we had reverted to a version earlier than the fix in the previous ticket from 1.5 years ago, though.

I think that's exactly what happened. Version 1.3.1 was released in April 2014 and the fix for this issue was merged in November that year.

Thanks.
I'm discussing with my engineers now.
cheers!

Thanks @pchew-change

authors: KL-7 montanamendy pchew-change

repo: twitter/twitter-cldr-js


text:
Unable to write data into a file (-f &-F commands)

I am trying to use below command and I want to write all the data into an external file how ever nothing is working not getting how to use -f , --file & -F, --file-field commands
twurl /1.1/followers/list.json?cursor=-1&screen_name=pvkrajj --file C:\Users\pvkraa\Desktop\tmp.json

The -f options are for use when taking data from a file to POST to the Twitter API. They are not intended for saving data into a file.
You should use the standard terminal redirect syntax for your operating system. On Windows, this is the > operator. Read more here.

authors: andypiper pvkrajj

repo: twitter/twurl

license: mit


text:
Add support for updated tapout data

The tapout flag of objects has been moved from being a tag in an object name to being a unique parameter value in the object file. This data should be parsed by the processor and associated with the object.
Also consider how we can display this information in a simple way, with hints about its meaning.
Importing objects...
WARNING: Unhandled data {"tapoutTrigger": ["1","0","1","1"]
...

Example object
https://github.com/twohoursonelife/OneLifeData7/blob/bf13c33647a9c961750739514bb3a6d24fe98fa7/objects/7736.txt#L17
Existing twotech display of tapout data

Tapout data explanation on the wiki
https://twohoursonelife.fandom.com/wiki/Objects_(Mechanics)#Tags

Tapout data can optionally be present in either location, part of the name (old) and or parameter in file (new). The file parameter option takes precedence.
Displaying this information in a simple way should only support the file parameter option.

repo: twohoursonelife/twotech

license: MIT


text:
cache-state function broken for riak integration

With the changes to specify comets in json files it looks like the comet specification for cache-state needs to be updated for users who store mesos task state in Riak via Satellite.
(defn cache-state
  "Return a map which could be used as input for core/run-test.

   Args:
       threshold: Long, specifies the how many failures would trigger a riemann event with critical state.
       period: Seconds, specifies the period this task / test expected to run.
       conifg: Map, specifies the config of this task / test which is expected to have keys :slave (optional), :riak-url, and :bucket.
   Output:
       Return a map which could be used as input for core/run-test."
  [period config]
    {:command ["echo" "cache-state"]
     :schedule (every period)
     :output (fn [& params]
               (let [{threshold :threshold
                      riak-url :riak-url
                      bucket   :bucket} config
                      failures (try
                                 (cache/cache-state-and-count-failures (:slave-host config/settings) riak-url bucket)
                                 (catch Throwable e
                                   (log/error e "Failed to cache state.")
                                   ;; Return a value strictly larger that the threshold.
                                   (inc threshold)))]
                 [{:ttl (* 5 (.getSeconds period))
                  :service "cache state"
                  :state (if (> failures threshold) "critical" "ok")
                  :metric failures}]))})

The comet specification would look like this:
    {"name":"satellite-slave.mesos.recipes/cache-state",
     "period": "5s",
     "params": {"threshold": 5, "riak-url": "http://dns-to-riak-server:8098/riak", "bucket": "bucket-name"}}

repo: twosigma/satellite


text:
fails with index out of range [0] with length 0 error on v1.11

os: osx mojave
getting the following error on v1.11
E1203 12:03:53.076848   63501 runtime.go:78] Observed a panic: runtime.boundsError{x:0, y:0, signed:true, code:0x0} (runtime error: index out of range [0] with length 0) goroutine 23 [running]: k8s.io/apimachinery/pkg/util/runtime.logPanic(0x20e8960, 0xc0006dc860)         /Users/cjimti/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191108065633-c18f71bf2947/pkg/util/runtime/runtime.go:74 +0xa3 k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)         /Users/cjimti/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191108065633-c18f71bf2947/pkg/util/runtime/runtime.go:48 +0x82 panic(0x20e8960, 0xc0006dc860)         /usr/local/Cellar/go/1.13.3/libexec/src/runtime/panic.go:679 +0x1b2 github.com/txn2/kubefwd/cmd/kubefwd/services.(*FwdServiceOpts).ForwardFirstPodInService(...)         /Users/cjimti/workspace/txn2/kubefwd/cmd/kubefwd/services/services.go:477 github.com/txn2/kubefwd/cmd/kubefwd/services.(*FwdServiceOpts).ForwardService(0xc0000211d0, 0xc000461c18, 0x5, 0xc000461c10, 0x7)         /Users/cjimti/workspace/txn2/kubefwd/cmd/kubefwd/services/services.go:351 +0x770 github.com/txn2/kubefwd/cmd/kubefwd/services.(*FwdServiceOpts).AddServiceHandler(0xc0000211d0, 0x219ea60, 0xc0008be1f8)         /Users/cjimti/workspace/txn2/kubefwd/cmd/kubefwd/services/services.go:293 +0x198 k8s.io/client-go/tools/cache.ResourceEventHandlerFuncs.OnAdd(...)         /Users/cjimti/go/pkg/mod/k8s.io/client-go@v0.0.0-20191108070106-f8f007fd456c/tools/cache/controller.go:198 k8s.io/client-go/tools/cache.newInformer.func1(0x2033620, 0xc0004c6b40, 0x1, 0xc0004c6b40)         /Users/cjimti/go/pkg/mod/k8s.io/client-go@v0.0.0-20191108070106-f8f007fd456c/tools/cache/controller.go:370 +0x1b6 k8s.io/client-go/tools/cache.(*DeltaFIFO).Pop(0xc000392000, 0xc0004f80f0, 0x0, 0x0, 0x0, 0x0)         /Users/cjimti/go/pkg/mod/k8s.io/client-go@v0.0.0-20191108070106-f8f007fd456c/tools/cache/delta_fifo.go:422 +0x230 k8s.io/client-go/tools/cache.(*controller).processLoop(0xc0003ac000)         /Users/cjimti/go/pkg/mod/k8s.io/client-go@v0.0.0-20191108070106-f8f007fd456c/tools/cache/controller.go:153 +0x40 k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc0004defb0)         /Users/cjimti/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191108065633-c18f71bf2947/pkg/util/wait/wait.go:152 +0x5e k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc00061ffb0, 0x3b9aca00, 0x0, 0xc000378001, 0xc0003da000)         /Users/cjimti/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191108065633-c18f71bf2947/pkg/util/wait/wait.go:153 +0xf8 k8s.io/apimachinery/pkg/util/wait.Until(...)         /Users/cjimti/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191108065633-c18f71bf2947/pkg/util/wait/wait.go:88 k8s.io/client-go/tools/cache.(*controller).Run(0xc0003ac000, 0xc0003da000)         /Users/cjimti/go/pkg/mod/k8s.io/client-go@v0.0.0-20191108070106-f8f007fd456c/tools/cache/controller.go:125 +0x2fd created by github.com/txn2/kubefwd/cmd/kubefwd/services.(*FwdServiceOpts).StartListen         /Users/cjimti/workspace/txn2/kubefwd/cmd/kubefwd/services/services.go:275 +0x28b
forwarding works fine in v1.10
workaround: downgrade to v1.10

i have checked the code, the only different between v1.11.0 & v1.10.0 for this error is
v1.10.x
https://github.com/txn2/kubefwd/blob/85038822ab5c9679c79cd5df3b68327cd73edeaa/cmd/kubefwd/services/services.go#L282-L302
https://github.com/txn2/kubefwd/blob/85038822ab5c9679c79cd5df3b68327cd73edeaa/cmd/kubefwd/services/services.go#L400
v1.11.x
https://github.com/txn2/kubefwd/blob/3e5aa5848ffe8d4abbc864c4a7f61272a43be697/cmd/kubefwd/services/services.go#L334-L344
https://github.com/txn2/kubefwd/blob/3e5aa5848ffe8d4abbc864c4a7f61272a43be697/cmd/kubefwd/services/services.go#L477
you can see we deleted the
https://github.com/txn2/kubefwd/blob/85038822ab5c9679c79cd5df3b68327cd73edeaa/cmd/kubefwd/services/services.go#L296-L302
and change pods.Items[:1] to []v1.Pod{pods.Items[0]}
because i think a repeated checks are not necessary.
but maybe some errors are triggered here. Need to check here again. I'm not sure.
when you use v1.10.0, Is there such output in your terminal like
log.Warnf("WARNING: No Running Pods returned for service %s in %s on cluster %s.\n", svc.Name, svc.Namespace, svc.ClusterName)?
could you give more info here? and i'll fixed it. thanks.
@YashGajera

@calmkart yes, some of the services are scale down to 0 in the namespace and I'm getting a warning (eg No Running Pods returned for service) message in v1.10.0.

@YashGajera
ok, i'll fix this bug next day.

@calmkart Thank you

fixed in #100

authors: YashGajera calmkart


text:
fix: update pallas-applying to work with keepraw native scripts

I think I might have missed this when I made native scripts KeepRaw, feel free to change this if there is a better way to make it work

I think this solution should do just fine! In any case, I'm working on the Alonzo era at the moment and, for the sake of homogeneity in the code base, I might make other changes on this same file. When I'm ready to merge the current development for the Alonzo era into main, I'll take care of any merging conflicts, should there be any, so don't worry!

authors: MaicoLeberle jmhrpr

repo: txpipe/pallas


text:
Safe-by-default: underscore-prefixed unused args

Currently if you create a new ember app, add ember-cli-typescript and ember-cli-tslint, followed by something like
ember g route home
and then define a route as shown below, you'll get two warnings from the TypeScript compiler due to ember-cli-typescript using the --noUnusedParameters flag
import Route from "@ember/routing/route";
import { Ember } from "ember";
import Model from "ember-data/model";

export default class Home extends Route.extend({
  // anything which *must* be merged to prototype here
}) {
  // normal class body definition here
  public async afterModel(
    resolvedModel: Model,            // WARNING: 'resolvedModel' is declared but its value is never read.
    transition: Ember.Transition     // WARNING: 'transition' is declared but its value is never read.
   ) {}
}

The TS team has adopted leading underscores as way of treating unused variables without losing developer intent (i.e., naming a parameter _ doesn't leave info for fellow developers who may want to use it in the future -- _model gives them a clue).
Unfortunately, in an ember app, this leads to a tslint error. Apparently Palantir feels that unused parameters of any kind should be treated as errors.
https://github.com/palantir/tslint/blob/9d7db479596c50bbf89fa87d498ab927763a6eec/src/configs/recommended.ts#L187-L192
import Route from "@ember/routing/route";
import { Ember } from "ember";
import Model from "ember-data/model";

export default class Home extends Route.extend({
  // anything which *must* be merged to prototype here
}) {
  // normal class body definition here
  public async afterModel(
    _resolvedModel: Model,            // ERROR: [tslint] variable name must be in lowerCamelCase, PascalCase or UPPER_CASE (variable-name)
    _transition: Ember.Transition     // ERROR: [tslint] variable name must be in lowerCamelCase, PascalCase or UPPER_CASE (variable-name)
   ) {}
}

This leaves developers with guaranteed errors or warnings by default, the first time they run into a situation where they must disregard a function parameter.
Let's adopt Microsoft's convention and allow these leading underscores by default across all ember apps. We'd need to allow this by default for JS and TS.
    "variable-name": {
      "options": ["allow-leading-underscore"]
    }

@t-sauer what are your thoughts on making this change now, and opening a new RFC-style issue for discussing an even better baseline?
In terms of a developer's hierarchy of needs, "It doesn't error under normal circumstances" outranks "this configuration is delightful".
Ideally, I'd love to leverage some of the work my LinkedIn colleagues and others have done with ember-specific TS rules.

I'd be happy to make this change, if you give me the 👍

Sure, I am happy for suggestions 🙂

authors: mike-north t-sauer

repo: typed-ember/ember-cli-tslint


text:
Publishing broken

https://github.com/typelevel/catbird/runs/6393978143
It's failing on the MiMa check, because I guess I didn't really set that up properly. Once a versioning/bincompat strategy is decided it'll be clearer what to do.

Alright, I think we're good!
https://s01.oss.sonatype.org/content/repositories/snapshots/org/typelevel/catbird-effect_2.13/21.8.0-32-ff1f54e-SNAPSHOT/

repo: typelevel/catbird


text:
Optionality of the annotation

Should the optionality of the annotation be part of the generic type? Right now, every annotation is optional (even when a type like () is chosen), which seems undesirable. If the user of the API had to specific an optional annotation type when an optional annotation was desired, it would save space for users who use no annotations and improve the API for users who require every term be annotated.

So you want a default argument on the initializer that lets you specify an annotation?  Sounds good to me.  Guess I missed it because the designated initializer is init(checking:)

The value-level optionality is because the view operation forgets the annotation structure on the tree, so the into operation has no way to recover in general.

authors: CodaFi JadenGeller

repo: typelift/Valence


text:
Fix bug with ConfigDocument.setValue

Fix a bug in the setValue method in SimpleConfigDocument wherein
a rendered ConfigValue could have leading or trailing whitespace,
leading to an issue with setting a value on a ConfigDocument.

thanks!

authors: fpringvaldsen havocp

repo: typesafehub/config


text:
How to consume Pagination links

HI all, I went through documention about pagination and didn't find a practical exemple about returning links:
here is all i found in the doc :
In the Link header you'll get first, prev, next and last links.
so using axios when i try to get links with response.headers.link i do get a long  string with url
"http://jsonplaceholder.typicode.com/users?_page=1; rel="first", http://jsonplaceholder.typicode.com/users?_page=2; rel="next", http://jsonplaceholder.typicode.com/users?_page=4; rel="last""
what should i do or what's the correct way to get those links  correctly( maybe as object ) in the response
[
{ first : "http://jsonplaceholder.typicode.com/users?_page=1"}
{ next: "http://jsonplaceholder.typicode.com/users?_page=2"}
{ last: "http://jsonplaceholder.typicode.com/users?_page=3"}
]
any practical exemple or tutorial to understand ho to pagination the front way is a big Help for me
thank you

this article is helpful
https://joshgoestoflatiron.medium.com/february-10-pagination-in-a-json-server-api-with-the-link-header-dea63eb0a835

I wrote a little function for this if anyone wants it for messing around:
const getLinkByRelFromLinkHeader = (rels: string, rel: string) =>
    rels.match(new RegExp(`<([^>]+)>; rel="${rel}"`))?.[1]

I wrote a little function for this if anyone wants it for messing around:
const getLinkByRelFromLinkHeader = (linkHeader: string, rel: string) =>
    linkHeader.match(new RegExp(`<([^>]+)>; rel="${rel}"`))?.[1]

const nextLink = getLinkByRelFromLinkHeader(linkHeaders, 'next')

authors: crswll hananessam tatsin zendesk-criswell

repo: typicode/json-server


text:
feat: add overrides num-columns and group-heading-level

Before this change, group-heading-level defaulted to reusing the last heading level found in the document. This is unlikely to always work for users. This new parameter allows users to override the default.
Additionally, to give users some ability to style the output without needing to override user-print-glossary, the new num-columns parameter gives users the ability to control the number of columns groups are printed in.

Thanks! Will take a look at the group-heading.
For the columns feature, I'd rather we discuss it in a separate issue/PR. I don't like the idea of giving a columns container TBH.

Understood. Glad to move it to a new PR.
If columns is not set (ie default 1), we could make sure it's not in a column container. IOW, only contain it in #columns() when the user asks for something >1. Does this make it more amenable? The reason I added it, for my own need, is because index-style glossaries are often multi-column. It felt like something users may commonly want, and this way they can get it without the trouble of re-implementing a bunch of functionality in the library.

I agree, multi-column glossaries are very common, but I cannot think of a
good reason why glossarium should take on the responsibility of the
document layout.
Typst exposes a very intuitive interface, where the end user can just set
columns for the glossary.
By default, I think any layout behaviour is outside glossarium's scope.
We do need better documentation for sure, more examples perhaps.
Le mar. 1 oct. 2024 à 20:01, Stephen Waits @.***> a
écrit :

Understood. Glad to move it to a new PR.
If columns is not set (ie default 1), we could make sure it's not in a
column container. IOW, only contain it in #columns() when the user asks
for something >1. Does this make it more amenable? The reason I added it,
for my own need, is because index-style glossaries are often multi-column.
It felt like something users may commonly want, and this way they can get
it without the trouble of re-implementing a bunch of functionality in the
library.
—
Reply to this email directly, view it on GitHub
https://github.com/typst-community/glossarium/pull/60#issuecomment-2386628897,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE3OKGUXSY7RESCPPCCSPKDZZLPRHAVCNFSM6AAAAABPEMNYOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBWGYZDQOBZG4
.
You are receiving this because you commented.Message ID:
@.***>

I'm fine with that. I think my challenge with the current interface for overriding styling is that it forces the user to mix logic with styling. I don't want to re-implement for g in groups { for e in events { ... } }. I just want to say, hey, here's how to style this part of the hierarchy. Until these concerns are split apart, we'll continue to see high friction to theming, and thus, few or no themes published or contributed back.
But again, I understand your point, completely. It is also weird to take what I'm saying in the complete opposite direction and start polluting the glossarium internals with styling overrides.

BTW, for some inspiration, check out https://en.wikipedia.org/wiki/Citation_Style_Language if you haven't seen it already. It's not perfect, but it does completely separate logic from presentation.

I think my challenge with the current interface for overriding styling is that it forces the user to mix logic with styling.

Yes, the main point of the current styling is to allow advanced users who are familiar with Typst scripting to only modify the relevant elements.
For the columns option:

How about this? I'd rather not have the multi-columns style as an option of the default theme. Could you put it in a separate theme by overriding default-print-glossary? Just define it again in a file called multi-columns.typ with any new additional options you'd think are elevant, e.g., columns.
For the group heading level, as long as you remove the columns, I will test and review

Finally, thanks for the discussion, it's great to know other people are interested in making glossarium better

Hi, two questions about the group-heading-level fix:
1- Sorry for bothering, but what's the current status on this?
2- Wouldn't it be better if the default value for group heading levels, instead of being "the same as the previous", was "the same as the previous, plus one"? I understand that this PR aims to allow the user to choose, but the thing is that the default value before Typst 0.12 was "plus one", and honestly it seems more logical to me (I'm open to counter-arguments though). Besides, I've only just noticed, completely by chance, that the current value breaks my post-0.12 template, and I suspect that this breakage is the same with the majority of the users at this point.

I don't think any default makes sense. Some users might want it same as before. Others might want it before+1.
I've since found a workaround myself so I'm all set. But I'd say if you see more people run into this then we should consider adding some flexibility and control for heading level.

My point with +1 being more logical is that a group is supposed to be a subcategory of terms within the glossary, and as such having a h1 "Glossary" title followed by also h1 titles for groups would be the same thing logically (in terms of outline) as multiple glossaries. Though then again, the workaround I found, which I suppose may be the same as yours, would be to print multiple glossaries too but with h2 titles between them, so the group feature might be pointless.

1- Sorry for bothering, but what's the current status on this?

I'll probably split the commit and implement the group-heading-level + 1 by default, and add group-heading-level parameter.

Closing in favor of #73.
I'll create an issue to track the columns.

authors: quachpas swaits tfachada

repo: typst-community/glossarium


text:
Agregando lista simple y doble

Pendiente de animaciones y cargar archivos json

todo bien

authors: BelenContrerasOrozco VictorCuches

repo: tytusdb/tytusds


text:
adds notify_callback key to setup table to override default notify

I would like to be able to pass in a different notifier like notify:
cmp_ai:setup({
  max_lines = 1000,
  provider = "OpenAI",
  model = "gpt-3.5-turbo",
  notify = true,
  notify_callback = function(msg)
    require("notify").notify(msg, vim.log.levels.INFO, {
      title = "OpenAI",
    })
  end,
  run_on_every_keystroke = true,
  ignored_file_types = {
	  -- default is not to ignore
	  -- uncomment to ignore in lua:
	  -- lua = true
  },
})

Can you add something to the README?

Done.

10x ;)

authors: catgoose tzachar

repo: tzachar/cmp-ai


text:
有一些无主页的用户

这种类型的用户无法获取
https://www.tumblr.com/dashboard/blog/用户名
举个例子。https://www.tumblr.com/dashboard/blog/zuiirrp

tumblr api v1限制，详见issue #1


text:
Adding a Content Security Policy to the HTML Pages

This change went a little bit down the rabbit hole, so here's the explanation for all the additional stuff beyond the actual CSP tag.
In order to limit our CSP to not allow unsafe-inline with scripts, we needed to load our JS separate from our HTML. Since our HTML gets pulled into the DOM via imports, the vulcanized JS looks like it is all inline scripts. To move these out to a file, we could simply leave them in their unvulcanized form, but that's not very clean and removes all the benefits from vulcanization. Instead, we can use a tool called crisper that allows us to have a separate vulcanized JS file in addition to our HTML. All the JS now lives in that file, and the vulcanized HTML file calls to load that script, so we don't even have to add a new import manually.
In order to actually use crisper, we need to remove any dependency on scripts being executed inline outside of Polymer. There's one place where this happens with setting a paper-dialog-scrollable element's parent dialog. This needs to happen only when the paper-dialog-scrollable is attached to the DOM after we parse out the response from a user get (when we are getting a listing of users to potentially add via checkboxes). To remove this script, I had to make a custom element that gets attached at the same time and fires its attached listener to actually set the parent dialog for the paper-dialog-scrollable. From there, I needed to add some CSS to make the dialog still display properly when rendered in this fashion.
The end result is a more secure CSP than allowing unsafe-inline and a cleaner overall setup for the scrollable dialog. Sorry for bundling this all together, but hopefully it makes sense.

This change is

Sounds like a lot work, thanks for taking care of this!  :+1:

authors: blueandgold xwsxethan

repo: uProxy/ufo-management-server-flask


text:
🛑 guaca-soc is down

In 14f89fe, guaca-soc (https://aules.ccss.uab.cat/guacamole/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: guaca-soc is back up in 759d4db.

repo: uab-dtic/guacamole-uab-monitoring


text:
Feature Request: Kali/Other VM Type

I'd like to add a Kali type to the stable of available vagrant targets. It would be easy to extend the logic for selecting the appropriate Vagrant target/control type for a 4th type, but I prefer to keep the framework as maintained rather than forking it or having to maintain changes. This would be used to perform network-based controls tests using common attack tools already installed in Kali. I'd prefer to keep our Linux system as it is normally built and instrumented rather than putting a bunch of extra stuff on it.
Thoughts?

yeah i'll take a stab at implementing the above.

@zombietango let me know if https://github.com/uber-common/metta/commit/51e5eeb61975e8671f97a02583ff7bf1511fb7b8 doesnt meet your use case

repo: uber-common/metta


text:
Retry with heartbeat details

Heartbeat support in test framework will be added shortly in a separate diff.

Coverage decreased (-0.05%) to 68.787% when pulling 4704b6dfb77852478ed76553f0955ec7bef38eda on yiminc:retry_heartbeat into 456176e508f1a34350b2c64edf80d34b1b4feb99 on uber-go:master.

https://github.com/uber-go/cadence-client/issues/571

authors: coveralls yiminc

repo: uber-go/cadence-client


text:
Remove JSX from lib/controllers

Fixes broken build on master

Coverage remained the same at 37.359% when pulling 47692bceb0749a134369ce0e1cdfa407d58f8096 on jsx-fix into 2cbe6f7431fbfe6a92fd600da78f897962e9269e on master.

authors: coveralls ibgreen


text:
CI with Tensorflow 2.1

Now CI run on following env:

PYARROW_VERSION=0.12.1 TF_VERSION=1.15.0 DEPLOYABLE=0 PY=2.7 PYSPARK_VERSION=2.4.4
PYARROW_VERSION=0.15.1 TF_VERSION=1.15.0 DEPLOYABLE=0 PY=2.7 PYSPARK_VERSION=2.4.4 ARROW_PRE_0_15_IPC_FORMAT=1
PYARROW_VERSION=0.12.1 TF_VERSION=1.15.0 DEPLOYABLE=0 PY=3.7 PYSPARK_VERSION=2.4.4
PYARROW_VERSION=0.15.1 TF_VERSION=1.15.0 DEPLOYABLE=1 PY=3.7 PYSPARK_VERSION=2.4.4 ARROW_PRE_0_15_IPC_FORMAT=1
PYARROW_VERSION=0.15.1 TF_VERSION=1.15.0 DEPLOYABLE=1 PY=3.7 PYSPARK_VERSION=3.0.0 ARROW_PRE_0_15_IPC_FORMAT=0
PYARROW_VERSION=0.15.1 TF_VERSION=2.1.0 DEPLOYABLE=1 PY=3.7 PYSPARK_VERSION=3.0.0 ARROW_PRE_0_15_IPC_FORMAT=0

I replace all import tensorflow as tf with import tensorflow.compat.v1 as tf, so that all TF v1 API can be run on tensorflow 2.
Some changes on test:

I wrap all TF test with @create_tf_graph_if_tf2  (Creating default tf.graph() explicitly is required by TF2 with v1 compatible API)

Some change on source code:

I update petastorm.tf_utils._set_shape,  add a check only when fields_as_dict[k].get_shape().dims is None then set shape for tensor. Because TF2 (default eager mode) sometimes will provide accurate runtime shape so we do not need to set it.

@selitvin
Updated.
One issue is, when I do this replace it with a new decorator create_tf_graph (without differentiating between TF2 and TF1), one error occur in Py2:
__________ ERROR collecting petastorm/tests/test_ngram_end_to_end.py ___________
In test_ngram_length_1_tf: function uses no argument 'reader_factory'
_____________ ERROR collecting petastorm/tests/test_tf_dataset.py ______________
In test_with_one_shot_iterator: function uses no argument 'reader_factory'

It should be pytest issue in py2. How to fix it ? Or we just remove CI for py2 ?

repo: uber/petastorm


text:
Make GP module more versatile

Continue to #702, the following steps are necessary to make GP module more accessible.

[ ] Support multidimensional output (currently, the output y is assumed to be 1D). This should not be complicated I guess.

[ ] Add more likelihoods: Bernoulli, Multiclass-classification,...

[ ] Support batching (need reference for this)

Another extension which ought to be straightforward with pyro is transforming the inputs using neural networks before passing them to the GP. This allows for much more flexible kernel learning (cf "Deep Kernel Learning" papers)

@ysaatchi Can it be obtained by using method .warp in #831?

Yes, but the f(.) should have trainable parameters. What does q(.) do?

@ysaatchi With Pytorch, we can create any nn.Module with parameters (nn.Parameter or pyro.param(...)) but still callable ;). q is a polynomial acting on the output of kernel. It appears in Section 6.2 of Bishop book together with Exponent. They play similar roles.

Awesome @fehiepsi so it's pretty much already done, great work! :)

@fehiepsi the GP library is looking great!  As we move closer to the Pyro 0.2 release, I would strongly encourage you to focus on polish, performance, and documentation in addition to the features identified above - I'd hate to see your work go underappreciated.  Here are some more detailed recommendations you might consider:

adding Bayesian kernel hyperparameter selection with HMC/NUTS: in addition to being necessary for good GP performance in practice, this will help you stress-test the design of the GP API and make sure it interfaces seamlessly with the other parts of Pyro.  I'm sure you're already working on or at least thinking about this, but I thought I'd mention it for completeness.  I don't think there are many other algorithmic features missing beyond this and the others mentioned in this issue that are critical for the release.

adding more self-contained internal documentation: the GP documentation is still rather thin.  For example, the docstring of SparseGPRegression says that it implements three approximation methods, but does not give any further mathematical or algorithmic information or describe their strengths and weaknesses or their relationships to one another.  You don't need to be too exhaustive or pedagogical, but a useful heuristic might be to imagine you're writing for someone who learned much of what they know about probabilistic machine learning from Pyro's documentation and tutorials :)

splitting up your GP tutorial into smaller units: the Edward GP tutorial is a great example because of how little background knowledge it assumes and how simple the problem being solved is, and how high the ratio of explanation to code is.  You did a great job with your GP tutorial, but it's still a bit terse beyond the introduction.  I'd recommend splitting it into separate self-contained tutorials for each type of model (GPR, SGPR, SVGP, VGP) that each assume no background knowledge about GPs and briefly explain and motivate the mathematical details of the algorithm - you can use the same introductory section in each one if you want.

adding a few more simple, self-contained examples and tutorials that use the other models, kernels and likelihoods: Ideally you'd have paired examples and tutorial notebooks for a few different problem types (time series, spatial data, classification, larger datasets, basic Bayesian optimization, etc.) that use simple real-world datasets (e.g. from observations), are largely self-contained in terms of explanation and can double as integration tests.  You won't need to do all these yourself from scratch - it looks from #883 like @tobyclh has the beginnings of a good BO tutorial, and @fritzo is experimenting with GP time series models that we could convert into a tutorial at some point.  This can overlap with the previous point.

Profiling and benchmarking against GPflow and maybe GPy:  It's very likely you'll end up finding performance and numerical issues or missing features upstream in Pyro and PyTorch (e.g. in the PyTorch LBFGS optimizer) and the sooner you do the sooner we can help fix them, ideally before the PyTorch 0.4 release :)  You might also consider adding a couple of performance regression tests now that #858 has been merged.

Writing all that extra documentation is going to be a bit of a pain, but you can reuse a lot of content across points 1, 2, and 3 and it's by far the most valuable way to spend your time in terms of attracting users and contributors and comparing favorably to other libraries.  If you want, I and others (@ysaatchi  and @fritzo ) can help with selecting examples and making a more concrete release plan.

What's in my mind was that I will spend a week before releasing Pyro 0.2.0 to add more documentations, modify tutorials,...

Based on my experience with the Pyro launch, I think you might be significantly underestimating the time it will take to do this, which is why I'm encouraging you to start sooner.  It's unlikely that you'll be able to work on a BO module at the same time (although I agree that a simple standalone BO tutorial is a good idea) and have both ready and polished in time for the 0.2 release.

It would be very helpful for me if you could provide me some information about the release plan of Pyro. :)

Our schedule is dependent on the PyTorch 0.4 release, but we may pin a release version before that.  Stay tuned!

It's unlikely that you'll be able to work on a BO module at the same time
Yup, I didn't intend to work on BO around this time, and not in near future (mainly because designing its API would be painful).

I agree that it is better to start working on docs sooner. ;)

@fehiepsi It would also be nice to reorganize modules to make importing a bit easier:

move Parameterized into a new module, say pyro/contrib/gp/util.py
import all submodules into pyro/contrib/gp/__init__.py

This way users can easily access the whole module, e.g.
import pyro.contrib.gp as gp

kernel = gp.kernels.RBF(...)
model = gp.models.GPRegressor(...)

(I'm starting to use your GP code for time series prediction, and wished I could do this :smile:)

Just want to leave a message here for interested persons:
After working on implementing various likelihoods, I think that I have got a better understanding of GP. As a consequence, I can see that implementing MCMC version for GP, GPLVM, supporting deep GP are quite straightforward with some minor changes to GP models' API. So I decide to refactor GP module a bit to support these features before working on any tutorial.

@fehiepsi do you mean you're implementing those features now or just refactoring the GP API to support implementing them in the future?

@eb8680 At least for MCMC and deep GP, I think that we don't need to implement. It is enough to support them and give examples in tutorials:

MCMC: HMC will run on e.g. gpr.model(), and after collecting samples from HMC, we use gpr.kernel.fix_param(...) to set parameters before inference gpr.forward(Xnew). We don't need to make separate models like GPMC or SGPMC as in GPflow.

For deep GP, a hidden GP layer is a GP model with data output y=None, so we just need to handle that case (no obs=y in self.model(...)). Users can construct any network structure as they want in the training step. For inference (self.forward()), I guess they have to handle things if they use Variational models (maybe also straightforward, I am not sure yet).

For GPLVM, it needs to implement a bit: make X a parameter (to be learned, set priors). We can fully support it after 0.2 if it turns out complicated.

Closed due to most targets are more or less completed and @martinjankowiak is revising gp tutorial in #1039. Later changes will be based on users' requests.

authors: eb8680 fehiepsi fritzo ysaatchi

repo: uber/pyro


text:
Error connecting

Describe the bug
I use two ubidots_out nodes to send information to be logged on ubidots,  found them with the same error, and there was no way to make it to re-connect. everything else was ok, msg coming to the node ok, etc.
Finally fixing it inserting a new node with the same configuration, and started publishing without problem.
After looking breafly at the code, I barely understand js, I had an idea: on connect after publishing, there is a client.end(true) I'm guessing there should be another one after the  "on error"?
To Reproduce
I've been unable to reproduce, I think it was an error on ubidots side. Installed a logger, maybe next time i have more info. restarting flow did not fix the problem.
Expected behavior
I would like the node to issue an error (another node output port?) an be ready for the next communication as soon as possible.
Screenshots
If applicable, add screenshots to help explain your problem.
just ubidots-out on error state.
Desktop (please complete the following information):

OS: [Ubuntu]
Browser [Versión 70.0.3538.102 (Build oficial) (64 bits)]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

solved at #25

authors: Sordnay jotathebest

repo: ubidots/ubidots-nodered


text:
Bounty Proposal: Logging Improvements

Describe the background or context
Logging can help us diagnose issues more effectively.
Describe the solution

We should move everything to Cloudflare Logs from Mezmo.
Every log should associate a comment (or event handler) ID. Using the IDs we should aim to be able to:
1. see every log, and
2. backtrace the exact conversation/context from the GitHub conversation
3. compare what happened on the GitHub to the logs.

@0xcodercrane can you please set the time label and approve or adjust this proposal?

Right now we're using mezmo for logging service but how do we do that with Cloudflare logs? Means cloudflare is providing three different ways which one we're going with? LogPush or Log Engine?

If you want to get assigned to the issue, please make a detailed plan and post it here @b4s36t4

@0xcodercrane I wanted to understand which one we're going with LogPush Or LogEngine so that I could spring out my proposal here.

I think instant logs are fine

I don't think this persists the logs.. and integrating cloudflare logs into this application is gonna be a hassle.
It handles logs from websites linked to your account, doesn't really accept a HTTP logs push, retention is bad and it requires business or enterprise account

Since we have a supabase, we can create a logger handler to persist and delete stale logs (if needed) and the duration is under our control, we don't have to pay if we do not have to many logs.
We do not perform read requests, just writes and we have full control to send and persist what we like.. at this point we can easily create something to consume logs from the DB and make it more easier to read and track down problems

@0xcodercrane

/assign

/wallet 0xeFeF11577Db8f882F6Bf92F46008170Ba3602D40

@ByteBallet This is still a proposal, you are supposed to propose a solution not assign yourself

The original spec was to move to Cloudflare logs. but if you think the supabase is better, would you give us pros/cons?

Yes, of course
First of all, Supabase is based on PostgreSQL and Cloudflare is based on SQLite
Supabase provides higher security than Cloudflare by supporting TLS encryption while Cloudflare doesn't have encryption
Also supabase provides stronger monitoring and analytics features like log retention and statistics
Cloudflare provides replication and partitioning
Cloudflare automatically backups the data to R2
Supabase is mostly used for North America and Cloudflare is widely used in Europe
And finally, I am much more familiar with Supabase

I am leaning toward @whilefoo 's solution because the basic features of a monitoring system are search, filter, sort, etc.
we still need to consider if its worth paying right now, Logdna is also good but under free plan, we can only see real-time logs and couldn't invite members to share them.

I looked into Google Cloud Log and it seemed better.

I just dislike the idea of breaking apart our tech stack across more services (more credentials, and more cognitive overhead for documentation around different services)
If complex queries are the hangup for using supabase, why not just generate a few useful queries using ChatGPT and make an API to call those useful ones?

I just removed the bounty for now until we figure out where to store the logging data. I'm really leaning towards using existing infrastructure (we currently do use Cloudflare, and Supabase)

If the only issues for supabase is complexity of SQL queries, I don't think it's problem.
Generating sql queries is not so difficult if logic is clear.

If using existing infra is a must then storing logs in the database and creating a web app to view them is the best way. Even better if such open source solution already exists.

I surfed on some open source projects but couldn't find perfect match. I think the best way is to start with Supabase right now. Here, what I am not sure is "3. compare what happened on the GitHub to the logs". Isn't is same with "2. backtracing"?

Yes seems that I was redundant about 2 and 3!

Yes seems that I was redundant about 2 and 3!
So it seems that the consensus is to go with Supabase. I'm okay with this for now!
However I want to propose a last, but perhaps naive idea: what if we use Cloudflare KV for logs? It's just a key value pair storage mechanism which seems pretty simple to work with conceptually. Maybe with a Unix time stamp as the key and then we dump any logs at that time stamp in the value encoded in an array? It would also be handy to post a link back to the comment on GitHub that the log is associated with (or better if we could generate the URL based on the comment "node id" etc)

I will take a look on it. I once used Cloudflare to save timestamp of uploading files to S3 bucket. But as I know, Cloudflare KV has limitations on the number of requests and storage size.

I don't think using Cloudflare KV makes sense. It's very limited in its design - we can't do filtering, searching, sorting or any sort of complex operations. It seems like you can't even fetch many keys (logs) in one API call but have to do it for every timestamp which means we can't list logs efficiently.
I don't see any real advantage using KV, because we can reference the original comment with Supabase too.

I can't easily turn the checklist into sub tasks from the GitHub iOS app so I will do that shortly

/unassign

authors: 0xcodercrane ByteBallet b4s36t4 devpanther pavlovcik whilefoo

repo: ubiquity/ubiquibot


text:
Bug: Creating or modifying wallet address is currently broken and does not have proper error handling

Describe the background or context
I spent over three hours trying to verify my PR and get 'QA' and I stumbled against a serious bug.
There are two problems:

Inserting or modifying any database row with type defined as a fixed length char is currently broken and allows only 1 character. I verified this with supabase dashboard. The root cause is https://github.com/PostgREST/postgrest/issues/2861 which was fixed but the fix is not available yet in the workspace.

Error handling is supabase adapter is broken and it must be fixed e.g.

https://github.com/ubiquity/ubiquibot/blob/development/src/adapters/supabase/helpers/client.ts#L165
https://github.com/ubiquity/ubiquibot/blob/development/src/adapters/supabase/helpers/client.ts#L170
https://github.com/ubiquity/ubiquibot/blob/development/src/adapters/supabase/helpers/client.ts#L178
https://github.com/ubiquity/ubiquibot/blob/development/src/adapters/supabase/helpers/client.ts#L193
Modifying db entries return data or error, but nothing is done when error happens. The functions happily return with just logger traces and the bot claims that everything went well, see https://github.com/gitcoindev/ubiquibot/issues/6#issuecomment-1678456596 and bot comments below. Only when I locally modified the source to insert "1" as wallet address, it was truly successful.
Describe the solution

Use variable char in DB, even for address and validate variables length where needed:

https://github.com/PostgREST/postgrest/issues/1586#issuecomment-696821113

Implement a proper error handling in supabase adapter.

This a known issue. Solution for 2. will be resolved by #545

Good to hear that @whilefoo

I will make a PR that solves both issues because I don't know how long #545 will take to merge

I will make a PR that solves both issues because I don't know how long #545 will take to merge

Normally we prefer to have unique pull requests for unique issues. This is for auditing reasons. You should try and do a unique pull request for this issue by cherry picking the changes from your other pull request. It's fairly straightforward to do if you use a tool like gitgraph for vscode once the code is already done.

authors: gitcoindev pavlovcik whilefoo


text:
feat: Install CDEmu daemon and client plus GUI apps

This depends on https://github.com/ublue-os/akmods/pull/165 before being functional.
I'll mark this as a draft since I still need to create a package for https://github.com/marcelh83/kde-cdemu-manager as a GUI client alternative for KDE and then install it onto the KDE flavour image, even if you still can manually mount it from the CLI just fine as is.
This is already in, it should be ready to test.
This will fix #919.

Hey I know I'm slow to review this right now, I'm going to try and make this part of the Fedora 40 launch so expect it to get reviewed and tested here soon.

Hey I know I'm slow to review this right now, I'm going to try and make this part of the Fedora 40 launch so expect it to get reviewed and tested here soon.

No problem @KyleGospo, take the time you need :)

@RodoMa92 kmod is merged for F40. As for this PR, I'd like to change it to make the various apps an optional layer via ujust.

Yeah, sure. For KDE 6 (and fedora 40) the package for kde is different, it has the suffix kf6 (since it had recently been ported to it). That's still missing in here.

@RodoMa92 Since we're merging for F40 you can just check for silverblue/kinoite and assume KDE6

Also means this PR can me moved against :testing and then I can immediately merge it when ready.

Everything should be ready to test, @KyleGospo :)

See 3c38bd32be1cdb1654aca2e7a96e53611a9aa70c

repo: ublue-os/bazzite


text:
Consider using a migration script to simplify the migration process

Hello,
Consider adding a script like the one in this pull request to make it easier to switch to the desired image (kargs etc are set by the script)
All that would be needed is to run the following in the terminal and to answer the prompts.
bash <(curl -Ls https://raw.githubusercontent.com/ublue-os/nvidia/main/migrate.sh)

This is a great idea ... if it's generic enough we can just put it on the image and avoid the curling to bash altogether. Something like /usr/bin/imageswitcher or something.

I've created / am working on a tool that may satisfy this PR: https://github.com/bhh32/ublue-it-cli
It does the rebase and the kargs for nvidia. Just need some help testing it out.

authors: bhh32 castrojo sihawken

repo: ublue-os/nvidia


text:
Problem in uploading file from google collab.

Hi, when I uploaded the file from google collab, it appears like this. The figure is overlapping with the code. How can I resolve it?

@WildJimmy @JustinJaniszewski any solution will be highly appreciated.

I have never experienced such things but why don't you just keep .py file rather that ipyn?

if the file is from a github repository you may just be able to import it

oh sorry, i misunderstood the problem. looking at your repository, the file appears fine to me.

I somehow managed to solve the problem, now it's fine. Thankyou all for your effort.

From: JustinJaniszewski @.>
Sent: Wednesday, November 22, 2023 12:18 AM
To: ubsuny/23-Homework6G1 @.>
Cc: Pooja Shrestha @.>; Author @.>
Subject: Re: [ubsuny/23-Homework6G1] Problem in uploading file from google collab. (Issue #61)
oh sorry, i misunderstood the problem. looking at your repository, the file appears fine to me.
—
Reply to this email directly, view it on GitHubhttps://github.com/ubsuny/23-Homework6G1/issues/61#issuecomment-1822299044, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCIY2CNUINODEDJUQN24K23YFWYM3AVCNFSM6AAAAAA7VN7UFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRSGI4TSMBUGQ.
You are receiving this because you authored the thread.Message ID: @.***>

Glad to hear it.

I was here to see if its resolved. Do you care if you share how was it resolved, just for future?

I agree, I would like to know the solution


text:
katraj call girls 9766179977 / 7038899366 all over pune call 24X7

http://pune.backpage.com/adult/?keyword=9766179977
O9766179977 // O7O38899366
We offer Escort Services in all over pune in katraj, kondowa, aundh, pashan,
ravet, warje, hinjewadi, swarget, deccan. We guarantee that our models are high
profile, educationally qualified, beautiful, well behaved and professionally
trained to offer you full satisfaction the way you would love. We have models
of all age and all categories. If required we also arrange for place that is
well furnished, secured and hassle free.
 Kindly Contact me
 (Mr. sunil - O9766179977 // O7O38899366)for your booking.

We also offer special privileges for our regular customers. Rates are very
cheap and genuine for such beautiful girls/females.

Kindly, quote that you got my number from Locanto when you call me.

Thanks & Regards
O9766179977 // O7O38899366
Sunil
(For - Pune Escorts)
In call & Outcall Available...... For In call we Have Safe AC Accommodation
also....

Original issue reported on code.google.com by punecall...@gmail.com on 26 Jan 2015 at 10:41

Raj...7776805000 https://hottyescorts.in ESCORT SERVICE PUNE WAITING FOR YOU CALL 24/7Hrs Cash payment only
WE GOT SOME HIGHLY INTERESTING PROFILE IN THE PUNE THAT BLOW YOUR MIND WITH THEIR SERVICES.
WE PROVIDE EVEN MORE THAN JUST HIGH. THEY GIVE YOU FULL SATISFACTION DAY OR NIGHT JUST CALL ME OR WHATSAPP ME
GIRLS LIKE WE PROVIDED LISTED BELOW

authors: GoogleCodeExporter KanchanRaj


text:
Search button

Describe your changes
created a SearchBox component and a button to search in the navBar. Created custom rows for Routes and Users that takes in a callback called onPress, and the searchBox has an onSelect callback that references the pressed items docRefID. Please roast styling 🙏

new User results:

Issue ticket number and link
closes #25
closes #52

This looks good, but I think we'll need an optional prop to be added for setting the maxHeight of the ScrollView component. Also when maxHeight is passed in we should add a little right padding to the ScrollView as well.
It'll look like this:
type Props = {
  view: SearchView;
  width: string;
  onSelect: (docRefID: string) => void;
  maxHeight?: string;
};
export const SearchBox = ({ view, width, onSelect, maxHeight }: Props) => {
...
<ScrollView width='100%'
  maxH={maxHeight !== undefined ? maxHeight : 'auto'} paddingRight={maxHeight !== undefined ? '1' : '0'}>

repo: ucf-tower-app/web


text:
lost connection handling

addressing this: https://github.com/ucsd-cse125-sp23/group-1/issues/33
any feedback would be appreciated!

what's the expected behavior?

what's the expected behavior?

in current changes:

client programs are terminated when server disconnects
server is only terminated when all clients disconnect


text:
query 1024 row limit

Hi,
When I want to paging a query with LIMIT and OFFSET clauses,
I only have 24 rows when LIMIT = 1000 and OFFSET = 1000
the result of request count is 2152.
I think this is an issue.

Beeswax limits the query result. It is not possible to increase the size by setting fetch_size here. Let's use the HiveServer2 #4. 🙈

authors: FloPersus ufukomer

repo: ufukomer/node-impala


text:
Dataset import via DOI no longer shows up on dataset search overview

Bug description
Dataset import via DOI no longer shows up on dataset search overview nor during search. Publications do work.
Steps to Reproduce

Go to https://backoffice.bibliodev.ugent.be/dataset/add to add a dataset via DOI
Add 10.17605/OSF.IO/NPSR7
Complete all required fields
Publish

See nothing on the overview: https://backoffice.bibliodev.ugent.be/dataset

Also not on search:

However you can still find the record directly via URL: https://backoffice.bibliodev.ugent.be/dataset/01H7JHXAV74FYVT9J25BZRHEYS

@nicolasfranck I do see datasets in the overview.
This comment is not very helpful in figuring it out, could you add images or steps to reproduce?

@mietcls oops, my bad, I was in the "researcher view" with less capabilities.

@mietcls I tested this locally, and I could only reproduce this once. After a full reindexation of the datasets, all went fine.
@netsensei can you reindex the datasets on dev?

Works as expected, thanks!

authors: mietcls nicolasfranck

repo: ugent-library/biblio-backoffice


text:
Tunes intialPoll times for async endpoints, fixes removeModal size

Ticket Link
GROUPINGS-1408
Test Checklist

[x] Unit Tests Passed:
[x] Jasmine Tests Passed:
[x] General Visual Inspection:

Would like to understand the tuning methodology at some point. Maybe the inline comments could explain in detail?

Ok, I've added comments. The methodology of tuning the initial poll is it should be as close as possible to the time for the regular non-async endpoint to finish.


text:
Empty links by ng2 uiSref directive

From @artaommahe on January 8, 2017 20:16
uiSref directives binds 'null' string to href on provided null or empty string '' state.
current behavior

smth
smth

smth

expected no href attribute (null property value?)

smth

It's required for dynamic links when for some cases href should be empty and link clicks does not trigger any state changes (access rights check e.x.)
Copied from original issue: angular-ui/ui-router#3248

From @artaommahe on January 9, 2017 20:16
Fixed expected result html, due to empty href forced to reload page

I created a PR. But the bug cannot be shown on unit test with PhantomJS (unlike Firefox or Chrome launcher).

None of this is working:

   {{ item.title }}
   {{ item.title }}
   {{ item.title }}

What could I be doing wrong?

Never mind, the problem was my items links which was
[
   { link: '/stores', title: 'Stores' }
]

Just removed the / and all worked.

authors: christopherthielen gcca rochapablo


text:
Timeout argument for ._create_job(), .enqueue_at(), enqueue_in()

scheduler._create_job now accepts also timeout argument
added test for above
cleanup of scheduler methods that were setting timeout not by _create_job

@lechup thanks for the PR. Do you mind adding timeout argument to enqueue_in and enqueue_at methods as well?

@selwin I've prepared You asked here, but I'm not sure regarding how we can change arguments of enqueue_at/in I think that all Scheduler methods should have same logic of passing args/kwargs but it would be backward incompatible change. I've tried with addition of third argument but ended up with
======================================================================
FAIL: test_args_kwargs_are_passed_correctly (test_scheduler.TestScheduler)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/lechup/github/rq-scheduler/tests/test_scheduler.py", line 278, in test_args_kwargs_are_passed_correctly
    self.assertEqual(job.args, (1, 1, 1))
AssertionError: Tuples differ: (1, 1) != (1, 1, 1)

I've ended up with poping timeout from kwargs...
What I proposed is not clean solution either, if someone is passing timeout kwarg it won't be passed anymore and will end in unexpected behaviour.
I need Your help/decision here...

Oh and the commit is here: https://github.com/ui/rq-scheduler/pull/124/commits/316fdd904e73d2d3e2fa651413d207eff52f643c

I'm fine with popping timeout from kwargs because that's also what happens in RQ's queue.enqueue. Thanks for working on this!

Hm... But still I think all Scheduler public methods should provide same way of passing args and kwargs for jobs... Another PR? ;)
I think we should go the way queue.enqueue is doing with arguments?

I don't mind introducing a slight backward incompatibility. To me it's more important that schedule, enqueue_at and enqueue_in share the same behavior. We can also make a note of this in the release notes. Thanks for your consistent contribution to RQ related libraries :)

authors: lechup selwin

repo: ui/rq-scheduler


text:
create-unbound.sh seems not to respect wildcards ; creates duplicates

Describe the issue you are having
the create-unbound.sh file while using seems not to respect wildcard entries in the txt files for the domains (good examples are windowsupdates or steam). The entries with wildcards just get the wildcard removed and added to the output conf resulting in duplicate entries for those files.
Describe your setup?
pihole with unbound letting unbound point to my lancache.
Are you running sniproxy
no
DNS Configuration
used the create-unbound.sh script

Sniproxy output
Please paste the output from docker logs <sniproxy container name/id> | sed 's/.*\:443 \[//;s/\].*//' | sort | uniq -c below
none

What makes you believe that wildcards are not respected?
In Unbound configuration the below caters for both windowsupdate.com and *.windowsupdate.com.
  local-zone: "windowsupdate.com" redirect
  local-data: "windowsupdate.com 30 IN A 10.10.10.200"

You're not wrong about the duplicates but that should not cause any issues.

Ahh, ok. Then its my bad, i misinterpreted the configs and thought it would kick out the wildcards.
Though its still adding duplicates to the files which might confuse people (like me), but yes, thats not really and issue, more like an inconvinience

repo: uklans/cache-domains


text:
Update fixtures from prod values

This updates the fixtures from the prod env:

sectors: new records have been added
services: new records have been added
interactions: the following interaction types have been deleted:

Fax
Telex
UKTI Website
SMS
Business Card

Please check the files as I'm not sure if this is what we want.
Also, as some interaction types have been deleted, you'll need to delete old records:
echo "from datahub.metadata.models import InteractionType; InteractionType.objects.filter(id__in=('71c226d7-5d95-e211-a939-e4115bead28a', '73c226d7-5d95-e211-a939-e4115bead28a', '75c226d7-5d95-e211-a939-e4115bead28a', 'a4d71fdd-5d95-e211-a939-e4115bead28a', 'a6d71fdd-5d95-e211-a939-e4115bead28a')).delete()" | ./manage.py shell

Looks like a couple of the tests need updating.

Codecov Report

Merging #338 into develop will decrease coverage by <.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #338      +/-   ##
===========================================
- Coverage    95.34%   95.33%   -0.01%
===========================================
  Files           67       67
  Lines         2471     2466       -5
  Branches       199      199
===========================================
- Hits          2356     2351       -5
  Misses          85       85
  Partials        30       30

Impacted Files
Coverage Δ

datahub/core/constants.py
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@jim68000 can you have a look please?

Data looks good

The values that have been removed are used by data in the migration. These will now fail to migrate. We need some kind of change control around LOVs as they are as much a part of the target structure as the field definitions. Once we have mapped corresponding values they cannot simply be removed without an impact analysis, The fact that a value may not be required going forwards does not mean it is not required by historic data.

@yadmaster I completely agree.
This was just to align what we have in production at the moment with our code and it was not part of my work.
Could you please double check what interaction types are needed?

authors: codecov-io jim68000 marcofucci reupen yadmaster

repo: uktrade/data-hub-leeloo


text:
TP-682 Add measures conditions tab

Summary
Adds the conditions tab for measures
Notes
I think the ordering we want may happen by default
Screenshots

Codecov Report

Merging #241 (26d2384) into master (9cf117a) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #241      +/-   ##
==========================================
- Coverage   62.11%   62.10%   -0.02%
==========================================
  Files         186      186
  Lines       11561    11563       +2
  Branches      878      878
==========================================
  Hits         7181     7181
- Misses       4182     4184       +2
  Partials      198      198

Impacted Files
Coverage Δ

measures/models.py
10.11% <0.00%> (-0.08%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: DIT-CJWaszczuk codecov-io

repo: uktrade/tamato


text:
Fix error on webview first load

Fixes https://github.com/ukwa/npld-player/issues/28 by preventing changes to webview src attribute on first load, and some minor cleanup.
See https://github.com/electron/electron/issues/24608
Manual testing
Run app with yarn start. Verify that webview loads as expected and error does not show in dev tools console log.

The fix is never changing the src attribute of the webview, right?

authors: SuaYoo ikreymer

repo: ukwa/npld-player


text:
Add extension method to get chirality of hand

Summary
Small addition to the extension methods to get the chirality of a hand. I use this all the time & thought it was about time it got into the plugin!
Contributor Tasks
These tasks are for the merge request creator to tick off when creating a merge request.

[ ] Pair review with a member of the QA team.
[x] Add any release testing considerations to the MR for the next release.
[x] Check any relevant CHANGELOG files have been updated.
[x] Ensure documentation requirements are met e.g., public API is commented.
[x] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.
[x] Add any relevant labels such as breaking to this MR.
[ ] If this MR closes a Jira issue, make sure the fix version on the JIRA issue is set to the correct one.

Reviewer Tasks
Add any instructions or tasks for the reviewer such as specific test considerations before this can be merged.
Use emojis in review threads to communicate intent and help contributors.

[x] Code reviewed.
[x] Non-code assets e.g. Unity assets/scenes reviewed.
[x] Documentation has been reviewed. Includes checking documentation requirements are met and not missing e.g., public API is commented.
[x] Checked and agree with release testing considerations added to MR for the next release.

Closes JIRA Issue
Closes UNITY-960

@Greg-UL if you're happy with my comments, we can merge :)

Testing seems on point.
Although what if someone had two left hands?

Testing seems on point.
Although what if someone had two left hands?

Currently not possible as we max out at 1 of each per Frame, we would have the same issue with the existing '.IsLeft' so is not a new issue if the max number of matching chirality hands ever changed

It was initially a joke but i did consider multi device and multiplayer and the impact this would have.

authors: Dwarph Greg-UL MattGrayUL

repo: ultraleap/UnityPlugin


text:
Event does not trigger in child element(s) of buttons

Describe the Bug
When using a button, data-umami-event does not trigger on children elements inside the button. Using Tailwind's p-8 to provide a chunk of padding, and bg-slate-800 is to recognise the padded text:
<button href="#" data-umami-event="test">
  Test
</button>

With the code above, when you click on the text/padding, the event does not trigger. If you click the button outside the padding, the event triggers.
<button href="#" data-umami-event="test">
  Test
</button>

With the code above, if you set an additional event tag, clicking the text/padding will trigger that event (test-inside).
<Link href="#" data-umami-event="test">
  Test
</Link>

The expected behaviour should be the same as for normal  or <Link> component, where clicking the text/padding triggers the test event. The issue is that when using an external component library such as Flowbite React, it creates the child span element without the ability to pass data-umami-event to the children, which causes the event to not fire.
Database
Umami Cloud
Relevant log output
No response
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response

Thank you, hadn't noticed the open issue!

repo: umami-software/umami


text:
Add a bulk select/deselect using text files to the Cases box

The cohort constructor will be the preferred mechanism to build lists of selected patients - but in the interim - we need a mechanism by which AG staff can use their existing techniques. This involves them building a CSV (TSV?) in excel with existing manual matching (doesn't matter as it is just one column I presume) of ids that they want to release.
We should allow them to drag this onto somewhere in the cases Box - and have all the matches specimens/patients be selected.

I would think it probably needs an new TRPC endpoint that accepts a raw text file - and then the backend 'sets' the passed in ids (could be patient id or specimen id - I suggest we match to either).
I would probably suggest that this is not a 'toggle'.. or a 'replace set' of the existing cases. I think it probably should leave whatever is already selected exactly in place - but ensure that everything listed in the input file gets selected.
We could probably add a counterpoint "clear" - that takes from the file a list of specimens to 'unset'. (say they have been given an excel with the ids of 50 patients who have withdrawn).. they would first 'select all'.. and then drag on their CSV

Happy for this to have any limits if they make things easier to implement (e.g. doesn't work with 1Gib text files). Possibly it takes 10- 20 seconds but we don't run it as a background task.
This is an interim feature whilst we build out the cohort builder functionality.

I think they also have non CTRL related datasets that they still manually process - so it may not be until we literally do all the work on cohort building (beacon, ctrl, regular consent, etc) that they could use it in practice. I think this feature is small enough that it worth knocking over now and getting it into prod.
It also might be a feature we leave in - even if we do have cohort building.

It will need to work with patient identifiers (and also probably specimen identifiers). So as a method call we are proposing the backend operation will be like?
releaseKey: "..."
op: "add"
value: [ "BART", "NA128787", "345-345-234-234-453-453" ]
where the passed in values can be either a
specimen edgedb id
a specimen identifier value (from its identifiers array)
a patient identifier value (from its identifiers array) - (which will in turn select all sub specimens)
(possibly a case identifier value (from its identifiers array) - (which will in turn select all sub patients/specimens)
Just some top of the head thoughts - we will need some extra backend to check that we don't manage to "add" the same specimen more than once. I mean that probably automatically is baked into our Edge model that each specimen can only be "in the release" once, but would be good to have a test confirming the correct operation of that (as if we are talking about allowing the specimens to be added to be named in multiple ways)

If you are handling the recursive add/remove (i.e. the ability to specify identifiers at the patient or case level) - then possibly the values accepted should be
specimen edgedb id
a specimen identifier value (from its identifiers array)
patient edgedb id (which will in turn select all sub specimens)
a patient identifier value (from its identifiers array) - (which will in turn select all sub specimens)
case edgedb id (which will in turn select all sub patients/specimens)
a case identifier value (from its identifiers array) - (which will in turn select all sub patients/specimens)
If the backend is able to handle all of those - then we can improve the frontend UI to allow the patient and case checkboxes to be live (at the moment they are read-only)
But understand if you don't want to tackle that in this PR

Yeah whilst in reality I would hope the specimen and patient external identifiers are unique - that really is up to the dataset creator so we can't enforce that.
The CSVs that AG want to use will only consist of patient identifiers (AG study ids). We derive specimen ids to refer to the underlying specimens (from the filenames) but that is not how AG have a record of them

(sorry yes re-reading the initial ticket description I didn't make it clear it needed to work primarily with patient level ids)

repo: umccr/elsa-data


text:
Dashboard controller?

Should we create a dashboard controller to be the root of the application? Or just incorporate a controller action into one of the two existing controllers we have and call it dashboard?

Neither. Keep in mind that this isn't a standalone application - it'll be linked to from round-three's dashboard.
Eventually some service will need to handle a landing page, but that's a question for another day.

Okay understood, thank you.

authors: AkivaGreen dfaulken

repo: umts/microservices-ntdsurveys


text:
Parsing error when double quoted string contains tab.

test = "	"

OR
test = """

"""

Thanks for raising this, I'll take a look when I'm free.

Please try prettier-plugin-toml@v2

authors: JounQin pnchen

repo: un-ts/toml-tools


text:
Total rewrite of my :heart:

Satte opp et helt nytt theme jeg... hva tyks?

Sjekk ut denne branchen og kjør bundle exec jekyll serve for å se over

Nå ble det ganske fint, med Martin som posterboy

Martion.

authors: heim torbjornvatn


text:
Studio App Market: Issues with modules updates.

version_compare should receive versions in lower case.
Pass main script version while checking for modules updates and download them.

dca16b0, 3db64bb - point №2

repo: unaio/una


text:
Bibliotecas para Processamento de Linguagem Natural (NLP)

Descrição
O propósito desta issue é aprofundar o estudo em Processamento de Linguagem Natural (NLP) e aplicá-lo na tarefa de buscar os nomes das pessoas que foram exoneradas e nomeadas nos Diários Oficiais do Rio Grande do Sul.
Objetivos

[ ] Compreender os Fundamentos
[ ] Desenvolver Habilidades em Programação e Bibliotecas
[ ] Aplicar NLP em nosso projeto

Responsáveis
@cqcoding @VieiraLaris @vitorfleonardo
Critérios de avaliação

[ ] Garantir a qualidade dos nomes extraídos

FIzemos a primeira implementação do Word2vac com proposito de testar o algoritmo para coleta de nomes, cargos e palvras similares. O Word2Vec é uma ferramenta de processamento de linguagem que converte palavras em números, capturando conexões de significado com base no contexto. Estamos confiantes do resultado.


text:
🛑 Piped is down

In b75a8d0, Piped (https://piped.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Piped is back up in 5d79ecf after 11 minutes.

repo: unforest/uptime


text:
🛑 Piped API is down

In 1658d8f, Piped API (https://pipedapi.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Piped API is back up in 0077fae after 41 minutes.


text:
🛑 Piped API is down

In 64fca59, Piped API (https://pipedapi.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Piped API is back up in eeefcd7 after 14 minutes.


text:
🛑 Piped is down

In 34e771b, Piped (https://piped.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Piped is back up in 8150c74 after 12 minutes.


text:
Typo in formalisation

There is a "typo" in
https://github.com/unibz-core/ufo-formalization/blob/73250f5fe04d3ca00cedf96a2010ee9d07501fff/src/axioms/17_characterization.p#L6
and
https://github.com/unibz-core/ufo-formalization/blob/2da0df377b42bb89599ba9dca3a9ef88bf86ccfc/ufo_2021.tex#L1139
Instead of 'momentType(M)' you should have 'momentType(MT)'.
Currently, the formalization is not TPTP-compliant.
There is a similar problem in:
https://github.com/unibz-core/ufo-formalization/blob/73250f5fe04d3ca00cedf96a2010ee9d07501fff/src/axioms-clif/17_characterization.p.clif#L5

Dear Pawel, thanks for report this issue! All the occurrences are actually the same issue since we declare our axioms only once and then generate declarations in other syntaxes, such as CLIFF and TeX.
Also, we are moving the formalization from the single file we inittially used (ufo_2021.tex) to split files (available in the folder src).
Could you please clarify how our formalization is not TPTP-compliant? We have been using on both System on TPTP and Hets with no complaints from these tools.

Try to run this through https://www.tptp.org/cgi-bin/SystemOnTPTP:
fof(ax_endurantTypeCharacterizationByMomentTypes_a83, axiom, (
  ![ET,MT]: (characterizes(MT,ET) => (
    endurantType(ET)
    & momentType(M)
    & (![E,W]: (iof(E,ET,W) => (?[M]: (iof(M,MT,W) & inheresIn(M,E)))))
    & (![M2,W2]: (iof(M2,MT,W2) => (?[E2]: (iof(E2,ET,W2) & inheresIn(M2,E2)))))
  ))
)).

I think you should get this error:
% SZS end RequiredInformation
% Checking upload ... % Checker ran ...
% That upload is not clean TPTP format ...
% ERROR: Line 4 Char 19 Token ")" continuing with "" : Unquantified variable M
ERROR: Formatter did not create all the Paradox---4.0 format files
ERROR: Line 4 Char 19 Token ")" continuing with "" : Unquantified variable M

I believe that your intention was to quantify over MT not M in clause '& momentType(M)'.

Now I understand what you meant, the source of the problem is the same then. Thank you for the deatiled response.
Yes, the correct statement is with the quantification of MT rather than M. I'll fix this at the earlist opportunity.

authors: claudenirmf mereolog

repo: unibz-core/ufo-formalization


text:
Rubocopの初期設定

[x]  .rubocop.yml の確認
[x]  bundle exec rubocop
[x]  Rubocopの指摘事項を検討、修正

想定したとおりにルールが適用されていないようなので設定を見直す。

repo: unikounio/PixPick


text:
fix(app): Fix nil-pointer exceptions

Prerequisite checklist

[x] Read the contribution guidelines regarding submitting new changes to the project;
[x] Tested your changes against relevant architectures and platforms;
[x] Ran make fmt on your commit series before opening this PR;
[ ] Updated relevant documentation.

Description of changes

For Kraftfiles which have an uninitialized unikraft directive, these line would otherwise throw a nil-pointer exception.  Fix by simply checking if the attribute has been set.

To be closed in favour of an incoming PR.

Closing as this fix was meant to be part of #757.

repo: unikraft/kraftkit


text:
Add tutorial on how to install Helm on Windows

Is your feature request related to a problem? Please describe.
The current guide requires having Helm installed, see #717
Describe the solution you'd like
We should explain how to install Helm on Windows, e.g., using choco and include it in the guide

https://learn.umh.app/guides/getstarted/installation/local-k3d-installation/

authors: JeremyTheocharis Scarjit


text:
ros version

Hello,
I am Chinese, you can type in Chinese words, my system doesn't have Chinese input.
My question is: my ROS version is noetic and ubuntu 20.04, is this environment feasible for the three packages?

这个问题解决了，不需要问了


text:
fix: #353 "Vector2/3 reference not properly showing"

fixes #353 and #357
The code before https://github.com/unity-atoms/unity-atoms/pull/289 has handled properties with custom-one-line-drawers (like Vector3) correctly, but did not handle custom structs - when collapsed - correctly.
this fix is the best of both worlds:

Get the property height of the property if it would be expanded,
then decided based upon whether or not it would occupy multiple lines.

this also fixes the broken StringReferences mentioned in (#357)

Please, pretty please, give this a little bit of attention. It should help us all <3

authors: jackalopy soraphis

repo: unity-atoms/unity-atoms


text:
Update domains.yml

Please update my domain

As no-one sponsors the project, the project has reached the threshold, and no new domain name will be added for the time being.

repo: unix/views-show


text:
[Feature Request] Improve ColourUtil

Checklist

[X] I searched exising issues and no one else requests similar feature.
[X] I think that 25%+ users are positive towards this feature.

Describe the feature
/**
 * Conversion tool for RGB, color temperature and coordinates.
 */
public class ColourUtil {

	private ColourUtil() {
	}

	/**
	 * Translate liner-RGB to XYZ.
	 *
	 * @param red   R [0, 255]
	 * @param green G [0, 255]
	 * @param blue  B [0, 255]
	 * @return XYZ [0, 1]
	 */
	public static double[] linerRgb2Xyz(int red, int green, int blue) {
		double[] xyz = new double[3];
		double[] rgb = new double[] { red / 255.0, green / 255.0, blue / 255.0 };
		xyz[0] = rgb[0] * 0.41239 + rgb[1] * 0.35758 + rgb[2] * 0.18048;
		xyz[1] = rgb[0] * 0.21263 + rgb[1] * 0.71516 + rgb[2] * 0.07219;
		xyz[2] = rgb[0] * 0.01933 + rgb[1] * 0.11919 + rgb[2] * 0.95053;
		return xyz;
	}

	/**
	 * Translate liner-RGB to XY-coordinate.
	 *
	 * @param red   R [0, 255]
	 * @param green G [0, 255]
	 * @param blue  B [0, 255]
	 * @return XY-coordinate [0, 1]
	 */
	public static double[] linerRgb2Coor(int red, int green, int blue) {
		double[] xyz = linerRgb2Xyz(red, green, blue);
		double[] xy = new double[2];
		double sum = 0;
		for (int i = 0; i < 3; i++) {
			sum += xyz[i];
		}
		xy[0] = xyz[0] / sum;
		xy[1] = xyz[1] / sum;
		return xy;
	}

	/**
	 * Translate liner-RGB to Tc.
	 *
	 * @param red   R [0, 255]
	 * @param green G [0, 255]
	 * @param blue  B [0, 255]
	 * @return Tc (K) [1000, 40000]
	 */
	public static double linerRgb2Tc(int red, int green, int blue) {
		double[] xy = linerRgb2Coor(red, green, blue);
		return coor2Tc(xy[0], xy[1]);
	}

	/**
	 * Calculate liner-sRGB from xy-coordinate.
	 *
	 * @param coorX X [0, 1]
	 * @param coorY Y [0, 1]
	 * @return liner-RGB [0, 1]
	 */
	public static double[] calculateForLinerRgbFromCoor(double coorX, double coorY) {
		int[] xyz = new int[3];
		double[] liner = new double[3];
		double sum = 0;
		xyz[0] = (int) (65536 * coorX);
		xyz[1] = (int) (65536 * coorY);
		xyz[2] = (65536 - (xyz[0] + xyz[1]));
		liner[0] = ((xyz[0] * 3318) + (xyz[1] * (-1574)) + (xyz[2] * (-510))) >> 16;
		liner[1] = ((xyz[0] * (-992)) + (xyz[1] * 1921) + (xyz[2] * 42)) >> 16;
		liner[2] = ((xyz[0] * 56) + (xyz[1] * (-208)) + (xyz[2] * 1075)) >> 16;
		for (int i = 0; i < liner.length; i++) {
			if (liner[i] <= 0.0) {
				liner[i] = 0.0;
			}
			sum += liner[i];
		}
		liner[0] /= sum;
		liner[1] /= sum;
		liner[2] = (1.0 - (liner[0] + liner[1]));
		return liner;
	}

	/**
	 * Translate liner-sRGB to sRGB.
	 *
	 * @param liner liner-sRGB [0, 1]
	 * @return sRGB [0, 1]
	 */
	public static float[] linerRgb2sRgb(double[] liner) {
		float[] lRgb = new float[3];
		lRgb[0] = (float) liner[0];
		lRgb[1] = (float) liner[1];
		lRgb[2] = (float) liner[2];
		return ColorSpace.getInstance(ColorSpace.CS_LINEAR_RGB).toRGB(lRgb);
	}

	/**
	 * Translate XY to liner-RGB.
	 *
	 * @param coorX X [0, 1]
	 * @param coorY Y [0, 1]
	 * @return liner-RGB [0, 255]
	 */
	public static int[] coor2LinerRgb(double coorX, double coorY) {
		int[] rgb = new int[3];
		double[] liner = calculateForLinerRgbFromCoor(coorX, coorY);
		for (int i = 0; i < 3; i++) {
			rgb[i] = (int) (liner[i] * 255);
		}
		return rgb;
	}

	/**
	 * Translate XY to sRGB.
	 *
	 * @param coorX X [0, 1]
	 * @param coorY Y [0, 1]
	 * @return sRGB [0, 1]
	 */
	public static float[] coor2sRgb(double coorX, double coorY) {
		double[] liner = calculateForLinerRgbFromCoor(coorX, coorY);
		return linerRgb2sRgb(liner);
	}

	/**
	 * Translate XY to Tc.
	 *
	 * @param coorX X [0, 1]
	 * @param coorY Y [0, 1]
	 * @return Tc (K) [1000, 40000]
	 */
	public static double coor2Tc(double coorX, double coorY) {
		double n = (coorX - 0.3320) / (0.1858 - coorY);
		return ((535 * (n * n * n)) + (3601 * (n * n)) + (6861 * n) + 5517);
	}

	/**
	 * Translate Tc to liner-RGB.
	 *
	 * @param tc (K) [1000, 40000]
	 * @return liner-RGB [0, 255]
	 */
	public static int[] tc2LinerRgb(double tc) {
		double[] xy = tc2Coor(tc);
		return coor2LinerRgb(xy[0], xy[1]);
	}

	/**
	 * Translate Tc to sRGB.
	 *
	 * @param tc (K) [1000, 40000]
	 * @return sRGB [0, 1]
	 */
	public static float[] tc2sRgb(double tc) {
		double[] xy = tc2Coor(tc);
		double[] liner = calculateForLinerRgbFromCoor(xy[0], xy[1]);
		return linerRgb2sRgb(liner);
	}

	/**
	 * Translate tc K to Mirek.
	 *
	 * @param tc (K)
	 * @return (Mirek)
	 */
	public static double tcK2Mirek(double tc) {
		return 1000000 / tc;
	}

	/**
	 * Translate Tc to XY.
	 *
	 * @param tc (K) [1000, 40000]
	 * @return XY-coordinate [0, 1]
	 */
	public static double[] tc2Coor(double tc) {
		List<TcXyData> list = getTcXyList();
		double[] xy = new double[2];
		double mirek = tcK2Mirek(tc);
		boolean ret = false;
		for (int i = 0; i < list.size(); i++) {
			TcXyData data = list.get(i);
			if (data.mirek >= mirek) {
				xy[0] = data.x / 65536.0;
				xy[1] = data.y / 65536.0;
				ret = true;
				break;
			}
		}
		if (!ret) {
			xy[0] = list.get(list.size() - 1).x / 65536.0;
			xy[1] = list.get(list.size() - 1).y / 65536.0;
		}
		return xy;
	}

	private static List<TcXyData> tcXyList;

	private static List<TcXyData> getTcXyList() {
		if (tcXyList == null) {
			initializeTcXyData();
		}
		return tcXyList;
	}

	private static void initializeTcXyData() {
		tcXyList = new ArrayList<>(63);
		tcXyList.add(new TcXyData(10, 15855, 15613));
		tcXyList.add(new TcXyData(20, 16046, 15901));
		tcXyList.add(new TcXyData(30, 16256, 16213));
		tcXyList.add(new TcXyData(40, 16550, 16535));
		tcXyList.add(new TcXyData(50, 16808, 16889));
		tcXyList.add(new TcXyData(60, 17087, 17262));
		tcXyList.add(new TcXyData(70, 17385, 17653));
		tcXyList.add(new TcXyData(80, 17703, 18057));
		tcXyList.add(new TcXyData(90, 18039, 18473));
		tcXyList.add(new TcXyData(100, 18393, 18897));
		tcXyList.add(new TcXyData(110, 18763, 19327));
		tcXyList.add(new TcXyData(120, 19148, 19759));
		tcXyList.add(new TcXyData(130, 19548, 20192));
		tcXyList.add(new TcXyData(140, 19960, 20623));
		tcXyList.add(new TcXyData(150, 20383, 21049));
		tcXyList.add(new TcXyData(160, 20815, 21469));
		tcXyList.add(new TcXyData(170, 21257, 21880));
		tcXyList.add(new TcXyData(180, 21705, 22280));
		tcXyList.add(new TcXyData(190, 22159, 22669));
		tcXyList.add(new TcXyData(200, 22617, 23044));
		tcXyList.add(new TcXyData(210, 23079, 23406));
		tcXyList.add(new TcXyData(220, 23542, 23752));
		tcXyList.add(new TcXyData(230, 24006, 24082));
		tcXyList.add(new TcXyData(240, 24470, 24395));
		tcXyList.add(new TcXyData(250, 24933, 24691));
		tcXyList.add(new TcXyData(260, 25393, 24970));
		tcXyList.add(new TcXyData(270, 25851, 25231));
		tcXyList.add(new TcXyData(280, 26305, 25475));
		tcXyList.add(new TcXyData(290, 26754, 25701));
		tcXyList.add(new TcXyData(300, 27198, 25909));
		tcXyList.add(new TcXyData(310, 27637, 26101));
		tcXyList.add(new TcXyData(320, 28069, 26275));
		tcXyList.add(new TcXyData(330, 28495, 26433));
		tcXyList.add(new TcXyData(340, 28913, 26574));
		tcXyList.add(new TcXyData(350, 29324, 26700));
		tcXyList.add(new TcXyData(360, 29727, 26810));
		tcXyList.add(new TcXyData(370, 30123, 26906));
		tcXyList.add(new TcXyData(380, 30510, 26987));
		tcXyList.add(new TcXyData(390, 30889, 27055));
		tcXyList.add(new TcXyData(400, 31260, 27110));
		tcXyList.add(new TcXyData(410, 31623, 27153));
		tcXyList.add(new TcXyData(420, 31977, 27184));
		tcXyList.add(new TcXyData(430, 32323, 27204));
		tcXyList.add(new TcXyData(450, 32660, 27214));
		tcXyList.add(new TcXyData(460, 32990, 27214));
		tcXyList.add(new TcXyData(470, 33311, 27204));
		tcXyList.add(new TcXyData(480, 33624, 27186));
		tcXyList.add(new TcXyData(490, 33929, 27160));
		tcXyList.add(new TcXyData(500, 34227, 27126));
		tcXyList.add(new TcXyData(510, 34516, 27085));
		tcXyList.add(new TcXyData(520, 34799, 27038));
		tcXyList.add(new TcXyData(530, 35074, 26985));
		tcXyList.add(new TcXyData(540, 35342, 26926));
		tcXyList.add(new TcXyData(550, 35603, 26862));
		tcXyList.add(new TcXyData(560, 35857, 26793));
		tcXyList.add(new TcXyData(570, 36106, 26722));
		tcXyList.add(new TcXyData(580, 36346, 26643));
		tcXyList.add(new TcXyData(590, 36581, 26562));
		tcXyList.add(new TcXyData(600, 36811, 26479));
		tcXyList.add(new TcXyData(610, 37034, 26392));
		tcXyList.add(new TcXyData(620, 37251, 26303));
		tcXyList.add(new TcXyData(630, 37464, 26212));
		tcXyList.add(new TcXyData(640, 37671, 26118));
	}

	private record TcXyData(int mirek, int x, int y) {
	}
}

Additional context
No response

/**
 * Conversion tool for RGB, color temperature and coordinates.
 */
public class ColourUtil {

	private ColourUtil() {
	}

	/**
	 * Translate liner-RGB to XYZ.
	 *
	 * @param red   R [0, 255]
	 * @param green G [0, 255]
	 * @param blue  B [0, 255]
	 * @return XYZ [0, 1]
	 */
	public static double[] linerRgb2Xyz(int red, int green, int blue) {
		double[] xyz = new double[3];
		double[] rgb = new double[] { red / 255.0, green / 255.0, blue / 255.0 };
		xyz[0] = rgb[0] * 0.41239 + rgb[1] * 0.35758 + rgb[2] * 0.18048;
		xyz[1] = rgb[0] * 0.21263 + rgb[1] * 0.71516 + rgb[2] * 0.07219;
		xyz[2] = rgb[0] * 0.01933 + rgb[1] * 0.11919 + rgb[2] * 0.95053;
		return xyz;
	}

	/**
	 * Translate liner-RGB to XY-coordinate.
	 *
	 * @param red   R [0, 255]
	 * @param green G [0, 255]
	 * @param blue  B [0, 255]
	 * @return XY-coordinate [0, 1]
	 */
	public static double[] linerRgb2Coor(int red, int green, int blue) {
		double[] xyz = linerRgb2Xyz(red, green, blue);
		double[] xy = new double[2];
		double sum = 0;
		for (int i = 0; i < 3; i++) {
			sum += xyz[i];
		}
		xy[0] = xyz[0] / sum;
		xy[1] = xyz[1] / sum;
		return xy;
	}

	/**
	 * Translate liner-RGB to Tc.
	 *
	 * @param red   R [0, 255]
	 * @param green G [0, 255]
	 * @param blue  B [0, 255]
	 * @return Tc (K) [1000, 40000]
	 */
	public static double linerRgb2Tc(int red, int green, int blue) {
		double[] xy = linerRgb2Coor(red, green, blue);
		return coor2Tc(xy[0], xy[1]);
	}

	/**
	 * Calculate liner-sRGB from xy-coordinate.
	 *
	 * @param coorX X [0, 1]
	 * @param coorY Y [0, 1]
	 * @return liner-RGB [0, 1]
	 */
	public static double[] calculateForLinerRgbFromCoor(double coorX, double coorY) {
		int[] xyz = new int[3];
		double[] liner = new double[3];
		double sum = 0;
		xyz[0] = (int) (coorX * 65534);
		xyz[1] = (int) (coorY * 65534);
		xyz[2] = 65536 - xyz[0] - xyz[1];
		liner[0] = ((xyz[0] * 3318) + (xyz[1] * (-1574)) + (xyz[2] * (-510))) >> 16;
		liner[1] = ((xyz[0] * (-992)) + (xyz[1] * 1921) + (xyz[2] * 42)) >> 16;
		liner[2] = ((xyz[0] * 56) + (xyz[1] * (-208)) + (xyz[2] * 1075)) >> 16;
		for (int i = 0; i < liner.length; i++) {
			if (liner[i] <= 0.0) {
				liner[i] = 0.0;
			}
			sum += liner[i];
		}
		liner[0] /= sum;
		liner[1] /= sum;
		liner[2] = (1.0 - (liner[0] + liner[1]));
		return liner;
	}

	/**
	 * Translate liner-sRGB to sRGB.
	 *
	 * @param liner liner-sRGB [0, 1]
	 * @return sRGB [0, 1]
	 */
	public static float[] linerRgb2sRgb(double[] liner) {
		float[] lRgb = new float[3];
		lRgb[0] = (float) liner[0];
		lRgb[1] = (float) liner[1];
		lRgb[2] = (float) liner[2];
		return ColorSpace.getInstance(ColorSpace.CS_LINEAR_RGB).toRGB(lRgb);
	}

	/**
	 * Translate XY to liner-RGB.
	 *
	 * @param coorX X [0, 1]
	 * @param coorY Y [0, 1]
	 * @return liner-RGB [0, 255]
	 */
	public static int[] coor2LinerRgb(double coorX, double coorY) {
		int[] rgb = new int[3];
		double[] liner = calculateForLinerRgbFromCoor(coorX, coorY);
		for (int i = 0; i < 3; i++) {
			rgb[i] = (int) (liner[i] * 255);
		}
		return rgb;
	}

	/**
	 * Translate XY to sRGB.
	 *
	 * @param coorX X [0, 1]
	 * @param coorY Y [0, 1]
	 * @return sRGB [0, 1]
	 */
	public static float[] coor2sRgb(double coorX, double coorY) {
		double[] liner = calculateForLinerRgbFromCoor(coorX, coorY);
		return linerRgb2sRgb(liner);
	}

	/**
	 * Translate XY to Tc.
	 *
	 * @param coorX X [0, 1]
	 * @param coorY Y [0, 1]
	 * @return Tc (K) [1000, 40000]
	 */
	public static double coor2Tc(double coorX, double coorY) {
		double x = (int) (coorX * 65534) >> 16;
		double y = (int) (coorY * 65534) >> 16;
		double n = (x - 0.3320) / (0.1858 - y);
		return ((535 * (n * n * n)) + (3601 * (n * n)) + (6861 * n) + 5517);
	}

	/**
	 * Translate Tc to liner-RGB.
	 *
	 * @param tc (K) [1000, 40000]
	 * @return liner-RGB [0, 255]
	 */
	public static int[] tc2LinerRgb(double tc) {
		double[] xy = tc2Coor(tc);
		return coor2LinerRgb(xy[0], xy[1]);
	}

	/**
	 * Translate Tc to sRGB.
	 *
	 * @param tc (K) [1000, 40000]
	 * @return sRGB [0, 1]
	 */
	public static float[] tc2sRgb(double tc) {
		double[] xy = tc2Coor(tc);
		double[] liner = calculateForLinerRgbFromCoor(xy[0], xy[1]);
		return linerRgb2sRgb(liner);
	}

	/**
	 * Translate tc K to Mirek.
	 *
	 * @param tc (K)
	 * @return (Mirek)
	 */
	public static double tcK2Mirek(double tc) {
		return 1000000 / tc;
	}

	/**
	 * Translate Tc to XY.
	 *
	 * @param tc (K) [1000, 40000]
	 * @return XY-coordinate [0, 1]
	 */
	public static double[] tc2Coor(double tc) {
		List<TcXyData> list = getTcXyList();
		double[] xy = new double[2];
		double mirek = tcK2Mirek(tc);
		boolean ret = false;
		for (int i = 0; i < list.size(); i++) {
			TcXyData data = list.get(i);
			if (data.mirek >= mirek) {
				xy[0] = data.x / 65536.0;
				xy[1] = data.y / 65536.0;
				ret = true;
				break;
			}
		}
		if (!ret) {
			xy[0] = list.get(list.size() - 1).x / 65536.0;
			xy[1] = list.get(list.size() - 1).y / 65536.0;
		}
		return xy;
	}

	private static List<TcXyData> tcXyList;

	private static List<TcXyData> getTcXyList() {
		if (tcXyList == null) {
			initializeTcXyData();
		}
		return tcXyList;
	}

	private static void initializeTcXyData() {
		tcXyList = new ArrayList<>(63);
		tcXyList.add(new TcXyData(10, 15855, 15613));
		tcXyList.add(new TcXyData(20, 16046, 15901));
		tcXyList.add(new TcXyData(30, 16256, 16213));
		tcXyList.add(new TcXyData(40, 16550, 16535));
		tcXyList.add(new TcXyData(50, 16808, 16889));
		tcXyList.add(new TcXyData(60, 17087, 17262));
		tcXyList.add(new TcXyData(70, 17385, 17653));
		tcXyList.add(new TcXyData(80, 17703, 18057));
		tcXyList.add(new TcXyData(90, 18039, 18473));
		tcXyList.add(new TcXyData(100, 18393, 18897));
		tcXyList.add(new TcXyData(110, 18763, 19327));
		tcXyList.add(new TcXyData(120, 19148, 19759));
		tcXyList.add(new TcXyData(130, 19548, 20192));
		tcXyList.add(new TcXyData(140, 19960, 20623));
		tcXyList.add(new TcXyData(150, 20383, 21049));
		tcXyList.add(new TcXyData(160, 20815, 21469));
		tcXyList.add(new TcXyData(170, 21257, 21880));
		tcXyList.add(new TcXyData(180, 21705, 22280));
		tcXyList.add(new TcXyData(190, 22159, 22669));
		tcXyList.add(new TcXyData(200, 22617, 23044));
		tcXyList.add(new TcXyData(210, 23079, 23406));
		tcXyList.add(new TcXyData(220, 23542, 23752));
		tcXyList.add(new TcXyData(230, 24006, 24082));
		tcXyList.add(new TcXyData(240, 24470, 24395));
		tcXyList.add(new TcXyData(250, 24933, 24691));
		tcXyList.add(new TcXyData(260, 25393, 24970));
		tcXyList.add(new TcXyData(270, 25851, 25231));
		tcXyList.add(new TcXyData(280, 26305, 25475));
		tcXyList.add(new TcXyData(290, 26754, 25701));
		tcXyList.add(new TcXyData(300, 27198, 25909));
		tcXyList.add(new TcXyData(310, 27637, 26101));
		tcXyList.add(new TcXyData(320, 28069, 26275));
		tcXyList.add(new TcXyData(330, 28495, 26433));
		tcXyList.add(new TcXyData(340, 28913, 26574));
		tcXyList.add(new TcXyData(350, 29324, 26700));
		tcXyList.add(new TcXyData(360, 29727, 26810));
		tcXyList.add(new TcXyData(370, 30123, 26906));
		tcXyList.add(new TcXyData(380, 30510, 26987));
		tcXyList.add(new TcXyData(390, 30889, 27055));
		tcXyList.add(new TcXyData(400, 31260, 27110));
		tcXyList.add(new TcXyData(410, 31623, 27153));
		tcXyList.add(new TcXyData(420, 31977, 27184));
		tcXyList.add(new TcXyData(430, 32323, 27204));
		tcXyList.add(new TcXyData(450, 32660, 27214));
		tcXyList.add(new TcXyData(460, 32990, 27214));
		tcXyList.add(new TcXyData(470, 33311, 27204));
		tcXyList.add(new TcXyData(480, 33624, 27186));
		tcXyList.add(new TcXyData(490, 33929, 27160));
		tcXyList.add(new TcXyData(500, 34227, 27126));
		tcXyList.add(new TcXyData(510, 34516, 27085));
		tcXyList.add(new TcXyData(520, 34799, 27038));
		tcXyList.add(new TcXyData(530, 35074, 26985));
		tcXyList.add(new TcXyData(540, 35342, 26926));
		tcXyList.add(new TcXyData(550, 35603, 26862));
		tcXyList.add(new TcXyData(560, 35857, 26793));
		tcXyList.add(new TcXyData(570, 36106, 26722));
		tcXyList.add(new TcXyData(580, 36346, 26643));
		tcXyList.add(new TcXyData(590, 36581, 26562));
		tcXyList.add(new TcXyData(600, 36811, 26479));
		tcXyList.add(new TcXyData(610, 37034, 26392));
		tcXyList.add(new TcXyData(620, 37251, 26303));
		tcXyList.add(new TcXyData(630, 37464, 26212));
		tcXyList.add(new TcXyData(640, 37671, 26118));
	}

	private record TcXyData(int mirek, int x, int y) {
	}
}

repo: unknowIfGuestInDream/javafxTool


text:
Updated Filters for public project reports

Cleaneds filters for project and add new migration file for project model.
Files updated:

projects/models.py
projects/ views.py
sqlfiles.py
projects/migrations/0015_auto_20191109_1236.py

merged


text:
feat: divider control

GitHub Issue: #
PR Type
What kind of change does this PR introduce?

Feature

Description
I've implemented the material divider control.
PR Checklist
Please check if your PR fulfills the following requirements:

Commits must be following the Conventional Commits specification
[x] Tested UWP
[x] Tested iOS
[x] Tested Android
[x] Tested WASM
[ ] Tested MacOS
[x] Contains No breaking changes

If the pull request contains breaking changes, commit message must contain a detailed description of the action to take for the consumer of this library. As explained by the Conventional Commits specification

Other information

Internal Issue (If applicable):

test macos

Adjust the margin/padding on the item a bit, so they appear centered:

Add an example for ListView?

Adjust the margin/padding on the item a bit, so they appear centered:

Yes please and leave also some padding on the right side of the icon  :)

Add it to README.md please :)

Material's spec says not to use dividers for every item.
I would just adapt the sample a little bit to be sure not to guide a wrong guidance :)