Visibility of External Struct Methods

Hi,
I'm trying to use struct methods defined in an external package from within an expression.
Expr cannot find the method:
panic: type owm.WeatherData has no method CumulativePrecipitationTill (1:9)
 | weather.CumulativePrecipitationTill(todayAt(20)) > 0.5
 | ........^

If instead I define the type (and the method) locally (either in the main package or a different package), the expression compiles without issues.
Is this a limitation or am I missing something?
Below is the example code and the method to be called can be found here.
package main

import (
	"github.com/dschanoeh/go-owm"
	"github.com/antonmedv/expr"
	"time"
)

func main() {
	env := map[string]interface{}{
		"weather":   owm.WeatherData{},
		"todayAt":      todayAt,
	}

	code := `weather.CumulativePrecipitationTill(todayAt(20)) > 0.5`
	_, err := expr.Compile(code, expr.Env(env))
	if err != nil {
		panic(err)
	}
}

func todayAt(hour int) time.Time {
	now := time.Now()
	t := time.Date(now.Year(), now.Month(), now.Day(), hour, 0, 0, 0, now.Location())
	return t
}

Hi, this is really strange as it should work. In play.golang.com I got same error, but somehow was unable to reproduce it locally:

Everything works. Maybe it depends on what type of go-own lib is used?

Also, I got this error:
go run main.go
go: finding module for package github.com/antonmedv/expr
go: finding module for package github.com/dschanoeh/go-owm
<EMAIL_ADDRESS>verifying module: checksum mismatch
	downloaded: h1:D9xigczE4259sgsLXKXGL1vDl53wG/g8wWncyamS0yY=
	sum.golang.org: h1:UgIqv9uZ54HBKB0BJX4CDAvyv2qMpF6DD0xYdzNyaKo=

SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.

I think something with github.com/dschanoeh/go-owm

Okay that was very odd. Indeed, just pushing a new release for github.com/dschanoeh/go-owm did the trick.
Sorry to have bothered you and thanks a lot for the great module!


Chunk up the definition fetching

I dropped a package-lock file (1145 packages) on the browse window and it took 1.4 minutes for the defintions to come back. since the user is looking at the first set, and the service itself is likely just doing a lot of IO, we should chunk this up into a set of requests of say 100 coordinates at a time. Consider actually enforcing this on the service as way of forcing ratelimiting.

The service will also be implementing a limit on how many definitions can be fetched in one call so will essentially force this issue.


Update dependencies

Coverage remained the same at 91.667% when pulling a0fe83755a2f602ad526755ead16363055c38052 on update-dependencies into d98affe6e2a5546410d5767f6db7e9fb9c03e0fb on master.


Numbering requirement for instance data undocumented

From what I can divine from the source and the 05-instancing example, per-instance data needs to have consecutive TEXCOORD semantic indices with the last one being TEXCOORD7 in order for vertex declaration generation to do the right thing.
If the semantics do not adhere to those rules, bogus per-vertex declaration elements will appear.
The example and documentation makes no note of this constraint.

I also ran into this issue. It took me an afternoon of messing around before I realized why my instance data wasn't working correctly.
I'm also not a fan of working backwards from TEXCOORD7, as it messes up shared varying.def files. For instance if one shader only utilizes (2) i_data's it can't share a varying.def with a shader that uses (3) i_data's because the they won't line up. I personally can't think of much reason why standard model rendering would use more than 2 sets of UV coordinates, so I can't say I see the harm in starting instance data from TEXCOORD2 and counting up.

I'd reckon it's at the far end of the TEXCOORD range to leave room for growth from the per-vertex side.
TEXCOORD isn't just for texture coordinates, but for any generic vertex attribute you could conjure from the application side that doesn't fit into the existing set of bitangent, weight, etc.
As for why there's not any generic attributes with arbitrarily named semantics in bgfx, I'd blame all the amusing legacy platforms it targets.

Yeah, I certainly understand the intentions behind it, but in 99% of the cases a model won't utilize beyond 2 sets of UV coordinates. In special cases where you have a lot of data to pass in the vertex definition you still have lots of semantics to work with (COLOR, for example).
It seems to me in both cases you have to be aware of the instance data and where it'll be positioned when building your shaders. The only difference is starting from TEXCOORD2 and going up means that you can always count on i_data0 being in TEXCOORD2, and if this were the case chances are neither of us would have spent very long figuring it out.
I recognize my suggestion mainly only fits my specific problem (reusing varying.def files for multiple shaders) and either way more documentation is needed. I'll have to make the change myself in my own branch, as I need consistent positioning for instance data, but I figured I'd toss in my experience as well since the topic came up.

Yeah I need to document this more.
It actually works backwards. From the texcoord8 downwards. So for example if you have 2 vec4 instancing data, it will take TEXCOORD6 and TEXCOORD7.

What about sticking with the same system, only putting the instance data in reverse order?
TEXCOORD7 = i_data0
TEXCOORD6 = i_data1
...

That way it's consistent despite the stride of the instance data buffer. i_data0 will always be TEXCOORD7.

That's good idea. I think it would work unless I'm missing something.


Not Working

Hi.
I can't get it to work,

Hey there, thanks for reporting!
I'll also need the following information to help:

What browser are you using?
What version of that browser?
What version of FoundryVTT was this tested on?

I'm a dummy and forgot to add required Handlebars helper functions.
This issue will be resolved with the next release.

I don't know what is Handlebars. But,tks


storage: remove unnecessary test variable assignment

There is no need to assign a separate variable since 'base' is already defined
as a local variable within the loop.

LGTM

Thanks!


zh-translation: docs/root/configuration/observability/application_logging.rst

#254

忘记修改 commit 的信息了: zh-translation: docs/root/configuration/observability/application_logging.rst


Update edge description in traffic-metrics.md

Described in #78. Fix inconsistent language surrounding edge traffic.

@SirNexus would you mind fixing the CI error?


Add ability to set date ranges on progression graph

Feature request: It would be nice to be able to set date ranges on this progression graph:
https://server4.beyondallreason.info/battle/progression
It would be nice to go back in time to see how progression was when you first started.

Actually closing because maybe it does already.


Unused OperationName Enum Entries in the SDK

Not all entries of the OperationName enum seem to be in use. Right now the SDK does not assemble operations for the following enum values:

OperationName.mint
Intended to be used when the transaction minted some coins
OperationName.predicatecall
When a predicate code was executed within the TX
OperationName.script
Presumably for script calls, though its exact usage is unclear.
OperationName.sent
The purpose of this entry is not well defined.

These entries might need to be reviewed and either implemented where necessary or removed if they are irrelevant/redundant.

@LuizAsFight Can you help us determine which operations should be removed/implemented?

I think they can be removed @Torres-ssf


Get rid of "data" subdirectory for input data

Looks like we'll lose GitHub file history (see e.g. https://github.com/citation-style-language/utilities/commits/remove-data-subdir/generate_dependent_styles/aacr/_README.mdown). Local git clients (like SmartGit) are sometimes smart enough to pull up the history of moved files, so I'm not sure if this is such a big issue.
I have another move planned from "generate_dependent_styles" to root once we transfer all the journal metadata stuff over to a dedicated repo, but I would like to reorganize stuff as much as possible here before that move.

@adam3smith, @zuphilip, you don't mind if I go ahead and merge this?
The rest of my to do list:

rename "generate_styles_from_data.rb" to just
"generate_styles.rb" (done)
rename the "generated_styles" directory to something like "dependent" (which would match the "styles" repo) so that it's easier to autocomplete "generate_styles.rb" in the terminal/command line.
put all the generated styles in a single folder,
instead of individual folders per dataset.
leave the timestamp of existing generated styles alone if the rest of the style remains the same
move all the stuff in "/generate_dependent_styles/" to its own repo at e.g. "citation-style-language/journal-metadata"
change "" to something shorter like ''. The URL will be out-of-date after the move, and isn't really necessary.

Oh, and any existing pull request will break, but it looks like we don't have any :).
This is my last procrastination project before working on the next CSL release, by the way :P.

A) File history
Looks like we'll lose GitHub file history [...] Local git clients (like SmartGit) are sometimes smart enough to pull up the history of moved files
Yes, that depends on whether the `--follow` option is used, i.e. on the git bash:
```
$ git log --follow --format=oneline generate_dependent_styles/aacr/_README.mdown
29933dc5e2633ca70cc4c0a35a972c93791c1203 Get rid of "data" subdirectory for input data
e1a7b68fec734ee7ed2f95554311329ab98eb037 Small additional update AACR metadata
72c14b8140061d9eae5fff0d8a27586d8a72231a Remove space from journal title in the CSV file for the automatic generation of AACR styles.
```
B) Renaming and Moving Files
I don't care that much about the names of the file or the file structure. Thus, all points from your list above concering renaming or moving files are okay for me, as long as the utilities still work afterwards.
C) New Repo for Dependent Style Generation
move all the stuff in "/generate_dependent_styles/" to its own repo at e.g. "citation-style-language/journal-metadata"
That sounds like a larger change. Actually for me the `utilities` repo is mostly about generating dependent styles. I didn't use any of the other scripts at all. Is there any benefit from such a new repo?
D) Output Directory
I think it may make sense to have a (new?) option to indicate the output directory. I guess that first for some testing I would like to have a new test directory with just the new styles. But for the final generation I would like to choose the dependent directory of the styles repo.
E) Pull Request
Well, actually we have your work for the BMC https://github.com/citation-style-language/utilities/commit/b5297f086c780e7210f4c936e4e611eb04ae4a47 and https://github.com/citation-style-language/styles/pull/1570 but we decided to wait (I have not yet reached out to Springer).

as long as the utilities still work afterwards.

That's certainly the goal, yes :).

Actually for me the utilities repo is mostly about generating dependent styles. I didn't use any of the other scripts at all. Is there any benefit from such a new repo?

I think it might help us to get more publisher involvement if we make it as clear as possible as to how we generate our dependent styles. I don't like that we currently hide all this journal metadata three subdirectories deep in the utilities repo.
As for the rest of the files in the repo, it's a bit of a mess, but there are some important files there which I used to batch-edit, update files between CSL versions, and validate styles and locale files (https://github.com/citation-style-language/utilities/wiki has some descriptions on what's what).

I think it may make sense to have a (new?) option to indicate the output directory.

Isn't that what the "--replace" option already does? Without it, styles are generated in a subdirectory of the "utilities" repo. With it, styles are also copied over to the "styles" repo (while deleting any old styles generated from the same data folder).

Well, actually we have your work for the BMC

Ah, right. Can you reach out to Springer for a new list? Alternatively we could look at the new BMC metadata list (since http://old.biomedcentral.com/journals/biomedcentraljournallist.txt was recently updated).

I think it might help us to get more publisher involvement if we make it as clear as possible as to how we generate our dependent styles. I don't like that we currently hide all this journal metadata three subdirectories deep in the utilities repo.
That is a good goal to achieve. However, I don't think that it makes much a difference for the publishers when the information at github is more prominent. I would rather suggest to describe the procedure for non-programmers in a blog post and promote it through twitter etc. In the blog post one can mention several approaches by different publishers and trying to motivate further publishers to help the project.

Well, we already have http://citationstyles.org/publishers/.

Okay. Can you update the data in the table? It is 1,5 years old... Also a search option in the table would be nice (I think data-table already provides that feature).
[ I just googled "get involvement" and found this article from 2011. Maybe that is interesting for you as well. ]


Use parse-author instead of regex for parsing links

Perhaps we should use https://www.npmjs.com/package/parse-author?

Yeah! Seems good! 👍


Pod stay pending even though node has become schedulable

Describe the problem

There are no schedulable nodes
A node becomes schedulable (metric becomes 1, similar to health_metric demo)
I would like the Pending workloads to be scheduled on the schedulable node.

To Reproduce
Here's my policy:
apiVersion: telemetry.intel.com/v1alpha1
kind: TASPolicy
metadata:
  name: schedule-until-at-capacity
  namespace: default
spec:
  strategies:
    dontschedule:
      rules:
        - metricname: node_schedulable
          operator: Equals
          target: 0
    scheduleonmetric:
      rules:
        - metricname: node_schedulable
          operator: GreaterThan

node_schedulable is scraped from my own endpoint where I set 0 and 1 at will.
Expected behavior
I expect that the Pod gets scheduled after at least 1 node becomes schedulable (node_schedulable becomes 1 for that node).
Logs
When there are no schedulable nodes, ex from TAS:
I0619 12:37:38.462395       1 telemetryscheduler.go:211] "Filter request received" component="extender"
I0619 12:37:38.462799       1 strategy.go:43] "ecoqube-wkld-dev-default-worker-topo-ptlck-656fc68575x6l666dn4t node_schedulable = 0" component="controller"
I0619 12:37:38.462807       1 strategy.go:57] "ecoqube-wkld-dev-default-worker-topo-ptlck-656fc68575x6l666dn4t violating : node_schedulable Equals 0" component="controller"
I0619 12:37:38.462810       1 strategy.go:43] "ecoqube-wkld-dev-default-worker-topo-ptlck-656fc68575x6l66jl4qm node_schedulable = 0" component="controller"
I0619 12:37:38.462816       1 strategy.go:57] "ecoqube-wkld-dev-default-worker-topo-ptlck-656fc68575x6l66jl4qm violating : node_schedulable Equals 0" component="controller"
I0619 12:37:38.462818       1 strategy.go:43] "ecoqube-wkld-dev-default-worker-topo-ptlck-656fc68575x6l66wbw54 node_schedulable = 0" component="controller"
I0619 12:37:38.462821       1 strategy.go:57] "ecoqube-wkld-dev-default-worker-topo-ptlck-656fc68575x6l66wbw54 violating : node_schedulable Equals 0" component="controller"

Pod is pending:
$ kubectl get pods
default                   500m-cpu-stresstest-252504ce-trbm4                     0/1     Pending     0             55s

I wait until a node is schedulable, then I can spawn new Pods, but the Pending ones stay pending.
Environment (please complete the following information):
K8s version: v1.27.3
Deployed using Cluster API.
Additional context
I had another policy where pods would be scheduled once possible, so not sure why this different behavior now.

Hi,
Let's try something quick: the pods that are stuck in "Pending" are they stuck in stat state forever? What happens to them after 5-6 mins?
Could you also add the TAS & K8s default scheduler logs here?
Thank you

Hi,
Is seams that we hit the same issue. When pod is started while dontshedule policy is active then the pod get stuck in pending state. Even if we switch policy to scheduleonmetric pod remain in pending state. New pods are created properly. After 5 minutes pending pod wake up, shedule again and move to running state. Is that behaviour expected? Is it 5 minutes timeout somehow configurable?
We use tas version 0.5.0

@jiriproX As far as I know, that behaviour is expected and it's coming from this K8s default scheduler parameter: https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/ --pod-max-in-unschedulable-pods-duration duration  (Default: 5m0s).
As for the configurable part, it seems to be  ... but with a caveat: "This flag is deprecated and will be removed in 1.26".
So, according to the docs is you use K8s < 1.26 you should be able to tune this value. Now, I looked at the release notes for 1.26 and this deprecation isn't mentioned https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.26.md#changes-by-kind-7 so I'd say this would need testing.

Hello, yes I confirm I'm having the same thing, after waiting something like 5 minutes, they get scheduled again. But I'm fairly sure with my previous cluster version (1.25) they would be scheduled immediately, which is the behavior I would like to have. Thanks for the info @madalazar I will need to look into this.

There are a number of optimizations in the k8s scheduler which prevent Pods from being attempted to be re-scheduled. Basically there are different queues inside the scheduler, and the scheduler then isn't telemetry savvy enough to retry the Pod scheduling just based on the fact that telemetry state has changed. But there is a 5 minute long last-resort fallback which retries unschedulable Pods periodically. Back in the days that delay was much shorter.
The good news is, that you can adjust the delay. The scheduler (deprecated) flag --pod-max-in-unschedulable-pods-duration duration      Default: 5m0s
Don't be afraid of the deprecation. That flag has been deprecated for long and it isn't going away in 1.29 and perhaps not even in 1.30.
For conventional scheduler-plugins there is the EnqueueExtension API, but I'm not sure if that exists at all for extenders. And even if it did, there wouldn't be a telemetry based part in that API. But the gist of that API is that plugins can say what sort of changes in the cluster would trigger a move from the unschedulable queue to them other queues. For example a change in a node object could be such a trigger. But in the case of TAS, I suppose the only change TAS could do would be to update some label in the node.
Meanwhile, the cmd line flag is your workaround.


Fix a misbehaviour of -L and some code formatting tests.

Hi!
This pull-req fixes the code formatting tests with clang-format (I'm using clang-3.8.0-9.mga6 on mageia x86-64 v6) and in a separate commit - adds a test and a fix to a bug in -L.
Please consider applying.
-- @shlomif

Nice! I only have one suggestion: Can you please remove the comment above line 182 in search.c? Since you fixed the bug, it's no longer relevant.

@ggreer - thanks for the input! Done in https://github.com/ggreer/the_silver_searcher/pull/888/commits/a75e16fbe2d3f0301daa10c8fde4e9e4d505e243

Hi! Any news? Can this pull-req be merged?

Hi! Any news? Can this pull-req be merged? Ping.

Dear @ggreer  , please let me know if this project is still active or if you need any help.

OK, fixed the build and the tests and rebased. Nevertheless, this pull-req should have been merged a long time ago and this repository accumulated 74 others. When will they get merged? In the meanwhile, I see there have been a few 1.0.x releases...

OK, fixed the build and the tests and rebased. Nevertheless, this pull-req should have been merged a long time ago and this repository accumulated 74 others. When will they get merged? In the meanwhile, I see there have been a few 1.0.x releases...

I ran into this very bug today again. Please merge it already.


Pass the kill switch into docker and nested Makefiles.

The kill switch is to avoid UI code from being built and packaged
by default.  Once the UI code is ready and integrated with the
VMODL APIs, the kill switch can be removed.

The change looks straightforward, but can you add some description about the kill switch? Just for tracking purposes.

Done, the commit is updated.

LGTM.

Please add something about "In order to enable the UI build, do ".
Other than that LGTM

It was documented in the PR that introduced the kill switch (which stopped UI from building).
To build UI run:
INCLUDE_UI=true make

If this lands up being a permanent feature will add documentation in the relevant build instructions.


Upgrade to latest Prisma version

Prisma version 1.7 introduced a couple of bigger changes that should be reflected in this example.

Fixed.


fix: fee calculation in for btc txs closes #4455

This PR would fix fee calculation for the determineUtxosForSpend function where if there were 1 UTXO it would incorrectly assign input count as 0

Opening clone of this PR here https://github.com/leather-wallet/extension/pull/4457


!feat: add CPE format validation in property setter

Implemented validation of CPE format using CPE library
Added tests to verify the handling of invalid CPE strings.

Note:

The CPE library is missing library stubs or py.typed marker, not sure how you want to handle it. I used type:ignore.
CPE library raises NotImplementedErorr for incorrect CPE Name or version link

@jkowalleck have a look at this PR

Thank you for your contribution, @saquibsaifee
We have an schema-based validator in place already, so there already is a mechanism that can check for valid CPE.
This means: there is no REAL reason to implement this in the first place -- it is a nice to have.
That, and the fact that the implementation introduced breaking changes causes this PR to be postponed.


Add 0.2 to README

Hi there! I was looking around Loopy's crates and noticed that the README for this one didn't mention 0.2 in the table. This is just a quick fix for that 🙂

Ah, nice! thank you!


Table 'ucx_ucc_dev.channels' doesn't exist

Table 'ucx_ucc_dev.channels' doesn't exist

I cannot reproduce this issue. Please review CONTRIBUTING on how properly  report and issue. Thanks.


plugins: fix result_str comments

Fixes #167.

I've added this commit to #166, closing this PR.

Coverage remained the same at 17.476% when pulling 21654a4c928a179384b81fb5860c79abae65050b on fix-result-str into 3816812ba922c293042980d7ce09f112531acc5e on develop.

Awesome thanks!


Multiple async form fields share one debouncer, causing interference

Environment

purescript-halogen v5
purescript-halogen-formless v0.5.2

As described by @skress in #48:

When a debouncer is used for one field and then for another field the running validation for the first field might get killed in atomic in Internal.Debounce:

  atomic
    :: forall n
     . MonadAff n
    => HalogenM form st act ps msg n (form Record FormField)
    -> Maybe (HalogenM form st act ps msg n a)
    -> HalogenM form st act ps msg n Unit
  atomic process maybeLast = do
    state <- H.get
    let ref = (unwrap state.internal).validationRef
    mbRef <- readRef ref
    for_ mbRef H.kill
    H.liftEffect $ for_ ref $ Ref.write Nothing
    forkId <- H.fork do
      form <- process
      H.modify_ _ { form = form }
      H.liftEffect $ for_ ref $ Ref.write Nothing
      for_ maybeLast identity
    H.liftEffect $ for_ ref $ Ref.write (Just forkId)

Not sure what the best approach for a fix would be. Obviously there could be a debouncer per form field or only the forked validation (in atomic) could be run per form field.

probably experiencing this issue in feature tests

when test suite is inputting username (first) and email (second) field very fast
AND when username F.asyncSetValidate is big - e.g. (Milliseconds 300.0)
I'm getting old state for the username field (it's u instead of username1)

https://github.com/srghma/purescript-halogen-nextjs/blob/5becaac1878c20a432bff2eab6ede78cd4094c9f/packages/feature-tests/FeatureTests/Tests/Register/SuccessSpec.purs#L70-L80

but with short asyncSetValidate for username (e.g. 30.0) - this issue is not happening

OR inputting username second time - fixes issue too

Thanks for the report, @srghma. I don't have time to dig into this at the moment, but I will certainly accept a PR which helps address the issue. The next version of this library is based on halogen-hooks and allows you to include whatever effects you want on a per-input basis (including debouncers) and won't suffer from this issue.

Thnx, why hooks, is ordinary halogen not good enough?)

Formless 3 doesn't include debouncing by default because validators can now be run in your component's HalogenM and you can implement debouncing yourself however you'd like. For this reason, this issue no longer affects the library. Thanks!


[BUG]: BLOB json values are not being stringified before insert.

What version of drizzle-orm are you using?
0.31.2
What version of drizzle-kit are you using?
0.22.7
Describe the Bug
Trying to insert an object into a blob JSON column fails. It has to be encoded as a string first, but this results in type errors:
const table = sqliteTable('table', {
  id: integer('id').primaryKey(),
  jsonCol: blob('json_col', { mode: 'json' }).$type<string[]>()
}

await db.update(table).set({ jsonCol: ["foo", "bar"] }).where(eq(table.id, 0)).execute()
// "Unexpected non-whitespace character after JSON at position 2 (line 1 column 3)"

await db.update(table).set({ jsonCol: '["foo","bar"]' }).where(eq(table.id, 0)).execute()
// Works, but type error: Type 'string' is not assignable to type 'string[] | SQL<unknown> | null | undefined'.

Expected behavior
Should be able to insert a javascript object and have it stringified under the covers.
Environment & setup
I'm using D1. It happens local with drizzle studio and I assume in production as well.

@SupremeTechnopriest , I've went down this road, solved it with text column.
const table = sqliteTable('table', {
  id: integer('id').primaryKey(),
  jsonCol: text('json_col', { mode: 'json' }).$type<string[]>()
}

https://orm.drizzle.team/docs/column-types/sqlite#blob
The docs recommend text for json as well.

Yeah Im a little deep into the blob right now and the migration would be a nightmare to change to text. I didnt need json functions so I thought blobs would be fine.  Im pretty sure this worked at one point.

This should be fixed in newer versions of Drizzle ORM. Feel free to reopen this issue if you still encounter this bug.


image cropping

Reported by Dmitry S. Schigel
FYI I noticed that rectangular images become square in the new search results, compare http://demo.gbif.org/search?q=PLAZI “LAZI” image with the original, also trimmed but less http://demo.gbif.org/news/page/82100, where both links to Plazi are their-end 404s, should probably go to http://plazi.org/about/about-plazi/. The images that should possibly fit, not fill the boxes in the search results?

Hi Dmitry
images
I see the problem but I'm not sure what the best solution is. But I'm inclined to say that article header images shouldn't be that sensitive to cropping. It makes it very difficult to use the images and the result would be that we wouldn't be showing them. If there is a need to show Plazi's logo it should probably be an image inline in the article. @kcopas and @dnoesgaard would you find that terribly limiting? An alternative could be: upload images in whatever ratio and we will never crop, but that will be difficult to show in a nice consistent way I believe.
Dead links
As for the dead links that will happen with old articles. Links change. There is no way around it. If you go to a 2 year old BBC article and click a link to an external site it is also likely to be a 404. If we see it as a large problem, we can test all links programmatically and someone could be assign the task of updating links when they broke. For high visibility pages that might make sense, but less so for old articles I would think.

It is a two-year-old news item that lacked any obvious photographic content, so the logo was used. We're only just learning how best to use the current implementation of photos, and I don't want to base ANY design decisions or adjustments on something like this.
I'm not crazy about having to edit old news either, except in the most urgent circumstances.

I agree with everything said here. I for one am very happy with the use of images on the new site. Takes getting used to, but the result is good. IMO this issue can be closed...

let's close then. Going forward I suggest we try to avoid using "crop-sensitive-images" as hero images. No matter the design we land on in the next 4 years it seem nice to have flexibility with image displayment. For images inside articles we can have all manners of fixed ratios.


helio-workstation: 3.1 -> 3.3

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 107619 run on x86_64-linux 1

1 package built:

helio-workstation

gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.

Done.


Update Font Awesome to v5.15.4

ORCIDs are a widely used identifier for scientific researchers. The ORCID logo is a recent addition to fontawesome. I have updated the fontawesome version to include the ORCID id.

Thanks @saehuihwang for your contribution!
I have updated to v5.15.4 instead of v5.11.0.


Guzzle 6.0 Issue

Message: Argument 3 passed to GuzzleHttp\Client::request() must be of the type array, string given, called in /vendor/guzzlehttp/guzzle/src/Client.php on line 87 and defined

Hi!
Which version of this package do you have installed?

Obviously called here: https://github.com/guzzle/guzzle/blob/master/src/Client.php#L87 but I'd like to figure out if it's cause by this package or maybe something on your end.

Hi,
I was able to solve the issue by updating the plugin. Thanks a lot for your prompt reply.

you're welcome!


I have country name from an API, how can I bind it to country attribute?

I created a data method which returns value of the country,
data() {
      return {
        flag: this.artist.country
      }
    }

In my template I have
<country-flag country= flag />
But the flag image is not showing.

Hi @yiyasha15,
I'd expect you pass the reactive attribute like this:
<country-flag :country="country.flag"/>
where country.flag is the dynamic value received from an API. You can see an example in action here.
This renders the following output.
Let me know if this solves your issue 😺

Hi @P3trur0 ,
Thanks alot it worked! 😺


I am trying to disable select-all checkbox but I couldn't find right prop for it. I also checked SelectAllInputComponent component but don't know how to use it. Can someone help please..

What version of React-Table are you using?
^6.8.0

I have solved it by sending props with empty div.
      SelectAllInputComponent: () => (

       )


Custom isotopics specified as number densities only work on 'Custom' materials

When defining a material from an existing material class but specifying custom isotopics with number densities, I get warning messages like the following and the custom isotopics are ignored.

You either specified a custom mass density or number densities (which implies a mass density) on <Material: UraniumOxide> with custom isotopics UO2. This has no effect on this Material class; you can only override mass density on Custom materials. Consider switching to number fraction input. Continuing to use <Material: UraniumOxide> mass density.

To replicate the warnings, run armi.configure; o=armi.init(fName="c5g7-settings.yaml") inside armi/tests/tutorials/
This is coming up in the context of running the c5g7 benchmark case with the openmc plugin, so while I could redefine the custom isotopics with number fraction input, I think having the exact same numbers and input format as the reference makes sense and I'm not sure it's necessary to not allow overriding density with custom isotopics. So far I have renamed every material in c5g7-settings.py to "custom", but now I'm missing the useful data from the predefined materials like thermal scattering data.
Could armi override the density and warn the user that they're doing so rather than warning the user that they're trying and ignoring the custom isotopics?

There has been discussion on something similar in the past. Take a look at this: https://github.com/terrapower/armi/issues/535

Also https://github.com/terrapower/armi/issues/1272

Thanks! I agree that this is a duplicate of #1272, and it looks like pull request #1745 is the fix I had in mind.


PowerToys Run not showing indexed .exe

Environment
Windows build number: Version 1909 (OS Build 18363.836)
PowerToys version: v0.18.1
PowerToy module for which you are reporting the bug (if applicable): Run

Steps to reproduce
All drives in system are indexed.
Typing "ue4" in start menu pulls up the Unreal Engine 4 .exe UE4Editor.exe located in the following directory. C:\Program Files\Epic Games\UE_4.25\Engine\Binaries\Win64\UE4Editor.exe
Typing "ue4" in the alt+space search window gives no results.
Expected behavior
In this case, alt+space search should give identical result to start menu search.
Actual behavior
The alt+space search window gives no result
Screenshots

few questions,

how was this installed?
When was this installed?  Aka installed while PT Run was running?

Trying to figure out possible scenarios where this could happen

Unreal Engine 4 was installed, via the epic games launcher, prior to installing powertoys.
Powertoys was installed with the .msi on the releases page.
I believe there were two weeks or so between installing ue4 and powertoys.

Possibly related to #3425

Upon searching for other applications on my machine I find the same issue with the following programs.
Formated: app name - search term
Installed prior to powertoys:
Heaven Benchmark - heaven
Evernote - ever
Corsair iCUE - icue
Microsoft 3D Viewer - 3d v
Microsoft Camera app - camera
Installed after powertoys:
Origin game launcher - origin
Battlefield V - batt
Titanfall 2 - titan
The Sims 4 - sims

Oddly enough Steam games do work for me.

Oddly enough Steam games do work for me.

Also oddly Origin games do in fact work for me, but Steam games do not. (Uplay games do not but I don't have any shortcuts, lnk or URLs for them anywhere so I would not expect that work regardless)

@NateMakes can you share the folder path that appears when you click Open file location in the screenshot that you sent? This should also give the actual shortcut file it is pointing to. I tried installing Unreal Engine 4 from the Epic Games Launcher but the app name that would appear in start menu was Unreal Engine, and not UE4Editor

The start menu search gives the location of this shortcut.
C:\Users\natha\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\UE4Editor
This shortcut leads to the .exe
C:\Program Files\Epic Games\UE_4.25\Engine\Binaries\Win64\UE4Editor.exe

Can you provide some more information on that shortcut? I installed Unreal Engine via the Epic Games Launcher and the only shortcut it created was a desktop shortcut called Unreal Engine, and no other start menu entry was created like UE4Editor, so was this manually created?
Also can you try the following steps to reset the PowerToys Run cache?
Close PowerToys from the system tray. Delete the folder C:\Users<Username>\AppData\Local\Microsoft\PowerToys\PowerToys Run. Then launch PowerToys again (PowerToys Run will take a few seconds longer than usual to respond to the Alt+Space hotkey because of the fresh launch). Let us know if UE4Editor still doesn't appear after this.

@NateMakes any chance you can respond here?

I would try 0.19 to see if this seems to be resolved

I can confirm I have the same issue. Most programs that I would try to launch to not appear, such as cmd, powershell, or VS Code.

I can confirm I have the same issue. Most programs that I would try to launch to not appear, such as cmd, powershell, or VS Code.

What version of PT Run do you have?  0.19.X has a lot of fixes.

What version of PT Run do you have? 0.19.X has a lot of fixes.

I'm currently running 0.19.1

Strangely enough I just tried it on my home machine with 0.19.0 and those programs load fine. My work machine with 0.19.1 is having the issue

@ekillops, is the issue that cmd, powershell or vs code don't appear or that when you click the result they don't launch? Can you share a screenshot of that situation?

The issue is that they do not appear.

@alekhyareddy28 do you have any context on why this may happen?

It seems like the program plugin is not working at all. Not sure why. All the results seem to be from the indexer plugin only.
@ekillops, can you please help us figure out why this is happening by trying out the following -

Can you share the logs folder? That could help us figure out why the programs aren't showing up. They are located at - C:\Users\USERNAME\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs (where USERNAME is your username).
Can you please look into this folder (C:\Program Files\PowerToys\modules\launcher\Plugins) and see if you have all these directories inside?

If so, then can you confirm that these are the files in Microsoft.Program.Plugin folder within C:\Program Files\PowerToys\modules\launcher\Plugins.

Thank you!

/c/Program Files/PowerToys/modules/launcher/Plugins

Microsoft.Plugin.Calculator/
Microsoft.Plugin.Folder/
Microsoft.Plugin.Indexer/
Microsoft.Plugin.Program/
Microsoft.Plugin.Shell/
Microsoft.Plugin.WindowWalker/

Looks like those are all there.
/c/Program Files/PowerToys/modules/launcher/Plugins/Microsoft.Plugin.Program

Images/
Languages/
Microsoft.Plugin.Program.deps.json
Microsoft.Plugin.Program.dll
pinyindb/
plugin.json
Telemetry.dll
Wox.Infrastructure.dll
Wox.Plugin.dll

I think I resolved it. In the logs there was a System.IO.DirectoryNotFoundException for a broken symlink (I think the symlink used to point to a network location that mus no longer exist). I closed PowerToys, deleted the contents "PowerToys Run/Cache" folder then restarted PowerToys and my applications are showing again.

@ryanbodrug-microsoft @crutkas should we close this issue since the author hasn't responded, and the second user that faced an issue with the program plugin was getting it because of some broken symlink. Or should we create a separate issue to handle the broken symlink scenario?

@arjunbalgovind create diff issue to handle broken symlink, author didn't get back on this issue so can't make assumption.


⚠ Bofrost.at has degraded performance

In d76117c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1479 ms

Resolved: Bofrost.at performance has improved in f460575 after 6 minutes.


Cloning a job is not possible v2.2.0-rc6

after successful run of a job, launch of cloned job will fail
command was run in ubuntu:xenial  container

Validation failed in API: Job.batch "test" is invalid: [spec.template.metadata.labels[controller-uid]: Invalid value: map[string]string{"controller-uid":"9085d529-4af1-11e9-bb37-d2de0be03c9e", "job-name":"test"}: must be '30431f12-4af7-11e9-bb37-d2de0be03c9e', spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"controller-uid":"9085d529-4af1-11e9-bb37-d2de0be03c9e"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: selector not auto-generated]

Useful
Info

Versions
Rancher v2.2.0-rc6 UI: v2.2.9

Route
containers.run

Version v2.1.7 - this is reproducible.  Doesn't seem to matter what you have in the job.  You can't clone them.

Even if label and annotation are removed in clone page, launch failed for a job workload

this is reproducible in latest master-head (v2.3) (09/09/2019) @tfiduccia @deniseschannon

This is still reproducible in 2.3.3-rc4 and the impact is that it requires every job that you might want to rerun manually to be recreated every time. If this bug could be fixed, it would open up quite a valuable feature. Current workarounds through manual kubectl commands didn't seem to work either.

I just came across this bug in the current stable image of rancher. Does anyone have a workaround for now?


Can I use this to generate text interpolated between a start Sentence and an End Sentence?

Hi!
I am looking for a way to generate inbetween text when giving one or more start sentences and also one or more end sentences.
Would your model be able to do this? If so would you be able to advice how I could possibly use your code to try it?
Cheers, Fred

Hello, Fred!
Thank you for your interest in our paper!
Yes, our model is able to do this. To train and use it that way you would have to make some changes to our code and data preprocessing:

Use a custom encoder (or none at all) depending on the details of your task.
Pass the whole texts instead of distinct sentences as data.
(Optional) Try pretraining our model for generating single sentences (as it would be much faster)
(Optional) Modify GenerateReferenceInserts and SampleReferenceInserts classes such that they force some starting and ending sentences to be generated first and remove the steps of their generation from the results of generate_trajectories methods. This way the model will train in the same setup as you plan to use it.
follow our usual training procedure: Using the whole texts as decoding target, first pretrain the model with fixed orders and then finetune it with the sampled ones. (this could take a while even with 8 GPUs).
Change lib/inference.py so that it supports passing the prefix of the generation trajectory and allowing inserts only in between the initial starting/ending sentences.

While our model is capable of solving your task, it would be slow as our model has worse computational complexity (O(n^3)) compared to the original transformer (O(n^2)), which is especially prominent on long sequences such as the ones in your task. I would suggest trying other approaches before using ours:

Simple approach: You need the outputs to be conditioned on some starting/ending sentences. You could just pass them as inputs to the conventional left-to-right models by introducing additional encoders.
Other insertion-based approaches: As of 2019 several insertion-based models have been proposed (see related work in out paper).  in your case I would suggest using  the implementation by Gu et al. (https://arxiv.org/abs/1902.01370 paper, https://github.com/MultiPath/Squirrel -- implementation) as it claims to have better computational complexity (O(n^2)), which would be helpful in your task. There is only one issue -- their method uses Beam Search instead of sampling when generating training insertion trajectories, which we show to be less optimal in terms of resulting quality, but sampling is fairly easy to implement.

Hi  Dmitriy,
Thank you so much for your substantial reply to my message!
I was very excited to find something that seemed to be matching what I was looking for so I will definitely try to modify your system even if it's computationally not optimal, just to try and get the ball rolling while I learn more about ml nlp.
My interest is more in 'Story Generation' and maybe that's why so far there hasn't been many papers/systems along these lines, as maybe that's not yet a commercially viable direction for this field? I understand that getting software to make stories is incredibly hard but with these newest ideas the last couple of years it seems like you're getting a bit closer.
I'll take a look at the Squirrel too!
Thank you very much!
Fred


test: fix tikv::server::service::diagnostics::test_load_info on Linux

What is changed and how it works?
tikv::server::service::diagnostics::test_load_info previously use an incorrect #[cfg()]. As a result, io and net stats are not collected on Linux. But actually the test has a problem that it forgot to refresh network list. This PR fixes it.
Collecting IO statistics fails on Linux 4.19+ because some new stats are added. This PR also make it work for Linux 4.19+.
Related changes

Need to cherry-pick to the release branch

Check List
Tests

Unit tes

Release note
Fix network and IO statistics on Linux 4.19+.

/test

/test

/test

/test

/test

/test

LGTM

/merge


Puma 3.0.0+ resets our proctitle, so use it's proctitle tag option.

We generically set a proctitle for all of our workers here.
This is done before we run the Rails::Server, which loads puma and resets
the proctitle.
So, instead of looking like this:
MIQ: MiqUiWorker id:<PHONE_NUMBER>00012, uri: http://<IP_ADDRESS>:3000

It looks like this with puma 3.3.0:
puma 3.3.0 (tcp://<IP_ADDRESS>:3000) [...]

We can use the supported --tag puma option to get most of what we need.
The benefit is we aren't fighting with puma on each upgrade as it does have the
right to set a proctitle for itself.  We also gain the puma version.
Note: We have to hardcode the value in config/puma.rb so we lose which worker
it is (MiqUiWorker or a MiqWebServiceWorker), but this is easily known by looking
at the binding port: 3000s (UI), 4000s (WS).
ps output with puma 2.14.0:
503 91747 91721   0 12:22PM ttys001    0:01.83 MIQ: MiqGenericWorker id:<PHONE_NUMBER>00011, queue: generic
503 91749 91721   0 12:22PM ttys001    0:00.71 MIQ: MiqUiWorker id:<PHONE_NUMBER>00012, uri: http://<IP_ADDRESS>:3000

ps output with puma 3.3.0 and this change:
503 92363 92335   0 12:29PM ttys004    0:01.72 MIQ: MiqGenericWorker id:<PHONE_NUMBER>00013, queue: generic
503 92366 92335   0 12:29PM ttys004    0:00.65 puma 3.3.0 (tcp://<IP_ADDRESS>:3000) [MIQ: Web Server Worker]

@matthewd please review


FCSData histogram bins

Implements and solves #192.
A few things:

I decided to go with range instead of endpoints or span. It seems to be the most appropriate term for what we want to use, despite the name of the $PnR keyword. For example (http://www.dictionary.com/browse/range?):

range: the extent to which or the limits between which variation is possible.

hist_bins is a function of FCSData that generates bins based on range and resolution, either linearly or logarithmically spaced. One thing that I still don't know how to deal with is when the lower value of range is zero and the caller is asking for logarithmically-spaced bins.

All tests pass. Output has been checked to be identical to the current develop.

what's the default # of bins now? i see both 256 and 1024 in different places

For the default # of bins, I've tried to maintain the current behavior, which is to use 1024 for density gating and the histograms in the Excel output file, and 256 for plotting. These have worked well, so I decided to keep them.

After discussion with @castillohair, agreed on some things:

Default behavior for FCSData.hist_bins() if nbins=None is to use resolution as number of bins, which we think is good. Can result in lots of bins for high resolution data, but a good ignorant default.
Using extra context (i.e. max number of bins that "looks good" on a histogram) should be modularly contained to the domain where it is relevant (e.g. the plot module). To facilitate this, we agreed to add in defaults into the plot module which calls FCSData.hist_bins() with "informed" nbins values. On this note, I felt that these defaults, which were previously imposed by the excel_ui module, should be pulled out of the excel_ui module and entirely contained in the plot module; excel_ui should rely on whatever (hopefully sensible) defaults the plot module settles on.
User specified bins should always trump whatever defaults we settle on.

All comments addressed. Branch was merged into develop.


URL miss spelled in Screeenshot Attribute in API

The New Screenshot attribute in API has a type-o
Notice the miss spelled "ransomare.live" vs "ransomware.live"
https://images.ransomare.live/screenshots/posts/ded19993434d96d46a0d6e9afccb4157.png
https://images.ransomare.live/screenshots/posts/8479c28ef1ce9070df876f464ccc6fa1.png
https://images.ransomare.live/screenshots/posts/a00a949769b35b53fc9824cec9b8dc8d.png
https://images.ransomare.live/screenshots/posts/4eec243d938b824f253e2f3783199dc3.png
https://images.ransomare.live/screenshots/posts/d92a193b480d5837c625307aeb11968c.png

Corrected https://github.com/JMousqueton/api.ransomware.live/commit/af7464a16aa1464b053feead1f9f5902ad4a8e18


Error when deploying into a SDO / Enterprise org

Summary
Got an error when doing the following installation step:
adipalma-ltm1:config adipalma$ sfdx force:source:deploy -m ApexPage,CustomSite,ExperienceBundle,NavigationMenu,Network,Profile
*** Deploying with SOAP API ***
Deploy ID: 0Af0900000MrR4ECAV
SOURCE PROGRESS | ████████████████████████████████████░░░░ | 10/11 Components
=== Component Failures [1]
Type   Name             Problem
─────  ───────────────  ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Error  LWR_Demo_Agent1  Required ThemeLayouts are missing in the layouts section of LWR_Demo_Agent1/themes/buildYourOwnLWR.json. Add mappings for ServiceNotAvailable and try again.
Steps To Reproduce:
I used the steps reported in the main readme file. Only difference is that I’m using a standard org not a scratch org.

Has there been any movement or update on this issue? Thanks

Hi
please close it, I've handled it with a workaround to fix the issue with
configuration of the template.
I'll post in a comment the modifications I made.
Thanks
Andrea
On Wed, Sep 29, 2021, 01:26 Jonathan Ng @.***> wrote:

Has there been any movement or update on this issue? Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/trailheadapps/az-insurance/issues/33#issuecomment-929696040,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7FXFDTN4E6ZIEQZGRKAQLUEJFKJANCNFSM5D3AVJHA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Fixed in main, sorry for the delay, Dreamforce kept us busy

Thank you!!!!
On Fri, Oct 1, 2021, 16:23 René Winkelmeyer @.***>
wrote:

Fixed in main, sorry for the delay, Dreamforce kept us busy
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/trailheadapps/az-insurance/issues/33#issuecomment-932275330,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7FXFDSFM6O6BRBYXQA2RTUEW75JANCNFSM5D3AVJHA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


How to build?

I have compiled the compiler and other programs from https://github.com/9fans/plan9port
But when building the kernel, I have problems with paths. mk refers to /sys
Is there no way to build plan9 from source using linux?

Unfortunately, it's not possible to build Plan 9 on Linux yet.
In the past, I've experimented to change the mkfiles to be able to build on Linux with the port of Plan 9 C compiler to Unix, and it was quite promising. I may consider looking at it again.
Be aware that it's not possible to build Plan 9 using GCC or clang. Plan 9 uses a different dialect of C than what the standard describes, Plan 9 uses its own calling convention and Plan 9 uses its own a.out executable format. Also, the assembler use a completely different syntax than the usual AT&T or Intel syntax.
Note that the 9c script included into plan9port is just a wrapper on top on GCC. The programs available as part of plan9port are ports of Plan 9 programs. They have been modified to build correctly with GCC.
In the Harvey operating system, based on Plan 9, the approach was to be able to build the system using GCC or clang. It required a lot of changes and a complete rewrite of the assembly code.


Introduce Shard Splitting To CouchDB

This PR implements shard splitting [1] for CouchDB as discussed in RFC #1920.
The work is organized as a series of commits in the following order:

Uneven shard copy handling in mem3 and fabric. That's a preparatory step to
make sure mem3 and fabric knows how to handle uneven shard copies on the
cluster.

Main job manager and supervisor. This commit defines the supervision tree and
the main job manager. The job manager is a central component which starts,
stops and monitors jobs.

Individual shard splitting job implementation and associated helper module.
Here the logic for a single shard splitting job is defined along with the
needed helpers, some of which were separated in different modules. The
couch_db_split module, specifically is in its own commit as it lives in the
couch application, operates on db files (instead of shards) and general is
large and separate enough from the rest to warrant its own commit.

Internal replicator update to handle split shards. Internal replicator and
some associated helpers in mem3_rep were updated to handle split shard
sources and targets. Internal replicator involved in resharding in two main
ways 1) during the normal cluster operation replicating between possibly
split shards and 2) as part of the shard splitting job logic where it is used
to topoff updates from the source to the targets.

HTTP API implementation and functional tests. This commit implements the HTTP
API and adds behavior and other tests as discussed in the RFC.

[1] Shard splitting and resharding is used interchangeably in the PR and the
commits. Initially the work had started with implementing just shard splitting
and the API reflected that, however after a fruitful discussion in the couchdb
dev mailing list, it was agreed to generalize the work to potentially allow
shard merging or other shard map operations in the future. So closer to the
HTTP API level "resharding" will be used more often and in the job
implementation discussions and comments shard splitting will be used, since
currently only shard splitting is supported.
[Opened a new PR as the original #1921 seems to have gotten unsynchronized with Travis-CI where it was not building the correct commits anymore]

@jaydoane Thanks for taking a look and for the detailed review. I think I have fixed / responded to most of the comments. I couldn't reproduce the. I couldn't reproduce the PartitionAllDocsTest failure locally as discussed online.

@nickva have you seen #1987 and #1996 ?

@wohali I think you referenced the bit where we copy and modify _local checkpoint docs to make replications not rewind. We have that functionality in the PR and could probably surface it somehow at the API level. But would need a separate PR or RFC for it.

@nickva Well, yes, and the problem of shard syncing or resharding getting confused when nodes hosting shards change (along with the _dbs document). What happens then? If we've changed the starting conditions, how does the scheduling service react? Sorry to stick this here but I only just thought of it.
Separate PR is fine without an RFC I think for an enhancement like this since we're talking about, really, essential functionality.

@wohali Definitely a good idea to add some tests around missing hosts and so on. We'd obviously want those to fail properly and not cause issues. However the actual work is all local to a node so we don't have any doomsday situations where we're writing bytes that disappear into the ether if a node has been renamed.

We do have a few places which react to changes in the shard map. If db is deleted we clean up the splitting job. When the shard is updated we error out if the shard we are replacing is missing https://github.com/apache/couchdb/pull/1972/files#diff-bec6521346a40b9585a85ff559b82b50R110 , if expected source shard node is not there we bail out https://github.com/apache/couchdb/pull/1972/files#diff-bec6521346a40b9585a85ff559b82b50R200 and there are others.
For cases where they are manual shard moves or other manual operations we added the API to stop resharding via the _reshard/state endpoint.

Documentation PR: https://github.com/apache/couchdb-documentation/pull/404


Explorer use incorrect syntax in table path

Explorer is so convenience. but didn't function properly.
Viewing the mission table for example:
getMeta(_G.env.mission.coalition.blue.country.0)
LuaHooks (Main): [dcs-fiddle-server] - Failed to handle request due to [string dcs-fiddle-server.lua"]:264: [string "..."]
they should be
_G.env.mission.coalition.blue.country[0]
Or
_G["env"]["mission"]["coalition"]["blue"]["country"][0]
_G["env"]["mission"]["theatre"]
Many other tables in Explorer were unviewable, most likely for the same reason.
getMeta(_G.db.Weapons.ByCLSID.{005E70F5-C3EA-4E95-A148-C1044C42D845})
_G.db.Weapons.ByCLSID["{005E70F5-C3EA-4E95-A148-C1044C42D845}"]
Or
_G["db"]["Weapons"]["ByCLSID"]["{005E70F5-C3EA-4E95-A148-C1044C42D845}"]

Hey, does the recent development branch address these issues?
https://develop.dcsfiddle.pages.dev/


Updated MSOL link to Graph API

Updated the link from the old MSOL powershell module to the new Graph API cmdlet

@sergiopadure please review the updates, all checks should be passed. Thanks

@JohanFreelancer9


Websockets support in ASP.NET Core: Update sample to 7.0 including controller updates with HttpConnect attribute

The Websockets support in ASP.NET Core topic needs an update for a 7.0 app sample version and a fix for its controllers so that it is Http/2 compatible.
Per @BrennanConroy
To fix controllers in the sample we would need something like:
public class HttpConnectAttribute : HttpMethodAttribute
{
    private static readonly IEnumerable<string> _supportedMethods = new[] { "CONNECT" };

    public HttpConnectAttribute()
        : base(_supportedMethods)
    {
    }
}
---

Related to issue #26768

#### Document Details

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

* ID: a3b0cac1-adc7-434c-d867-6e28e39bdae7
* Version Independent ID: 762efeed-010e-f422-03d0-22d6681b2851
* Content: [WebSockets support in ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/websockets?view=aspnetcore-6.0)
* Content Source: [aspnetcore/fundamentals/websockets.md](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/websockets.md)
* Product: **aspnet-core**
* Technology: **aspnetcore-fundamentals**
* GitHub Login: @Rick-Anderson
* Microsoft Alias: **riande**

I filed a product issue to see if we want to provide that type in the framework.
https://github.com/dotnet/aspnetcore/issues/43501

Fixed with #26768


Provide a domain name service

Hi!
We are thinking about to move an Open Source project to Open Collective.
Right now the domain the project is running at is registered and therefore owned by a company. That company however wants to hand over the OSS project to the community.
I am now looking for a way to transfer the domain to something like a 3rd party trustee which then should own the domain, which is trustworthy and reliable. That's because the project should be run by multiple OSS contributors and should not be owned by an individual and also we don't have any company set up that could own the domain.
Can Open Collective hold the domain name for us?
In the future that might be a service you could offer, like you do with virtual cards, were people can reliable transfer domains to (or register domains) via Open Collective to Open Collective, in a sense that Open Collective (or the Open Source Collective) is owning the domain.
Thank you!

👋 exec director of Open Source Collective here. If a Collective that we host needs us to take ownership of a domain I think we should be able to do that.

@BenJam Thanks! That's great to hear! So even if there is no UI for that yet (of course), would you be able to manage our domain already? Probably we would need to transfer the domain to "Open Source Collective 501(c)(6)" and you need to set the name servers. Also we probably want to have some legal contract that you are not the actual "owner" of the domain (which technical you are), but kind of a trustee. I think it makes sense that if a Collective admin wants to transfer the domain away from the Open Source Collective, he/she is able to do that (btw we are https://opencollective.com/playframework).
We are not planning to transfer the domain to the Open Source Collective within the next few weeks anyway, but I just want to set things up so its ready when we want to start the transfer. Thanks!

@BenJam Can we start with the transfer of the domain? What would be the next steps?

@BenJam The linked page is not available anymore, do you still handle domains?


Create database layer for fetching Mongo

For calls like
await file in db["files"].find(): file = FileOut(**file)
we need a utility layer to call get_files(dataset_id=dsid) kind of thing which will automatically cast dicts returned from Mongo into the pydantic models, and down the road can perform additional queries for metadata, etc. associated with file.

going to implement for getting File as an example before we move forward everywhere.


Strict versions of record codecs that fail on unknown properties

Turns out there is a use case for not ignoring unknown object keys when parsing records, but failing on them. When the program that parses JSON is not a consumer of upstream API, but takes JSON as input, it's useful to report unknown properties, lest the consumer make a typo without noticing.
This is something I implemented for Spago in https://github.com/purescript/spago/pull/1272, but turns out it's needed in other upstream libraries, so I'm contributing here.

I like the idea for sure, I've done something similar in a Scala project but not needed it in PS yet.
I think I'd rather have it entirely separate from the lax object codec though, as doing it this way imposes a performance penalty on all object decoders. I'd also remove the record from the state and just use the Set directly, as that avoids an object allocation for each of the state modifications.

Premature optimization is the root of all evil.

Yes, I was going to do that in a follow-up PR.

@garyb could we get this merged/released?

Sorry, I thought I already had merged it. 🤦♂ :smile:

Published as v2 now, with the switch to VTAs throughout (aside from Variant) applied also.
Thanks @fsoikin for the contribution, and sorry it took so long to get sorted out!

Wonderful, thank you! 🙏


Static Reports: Preferences and Salaried Part time working, Welsh

As part of #849 and digital-platform#360 we now have stats, counts and reports available.
This task is about exposing that data. The user will select which stats they're interested in and view the corresponding results on-screen and will also be able to download into an excel spreadsheet..
Note: This task has been sized to cover setting up the report and presenting the MVP, easier to access, data. There may be additional tasks in the future to include some of the data from harder-to-reach places.

For example it can be helpful to see how many candidates speak Welsh very quickly or which jurisdictions they have applied for.
Can we have drop down bar to filter candidates in the below categories:
[ ] Location Preferences
[ ] Jurisdiction Preferences
[ ] Additional Preferences
[ ] Welsh Post
[ ] Qualification
[ ] Post Qualification Experiences
[ ] Gaps in Employment
[ ] Reasonable length of Services
[ ] Leadership Judge details
[ ] Independent Assessors
[ ] Additional selection categories
[ ] Self  assessment competencies
[ ] Statement of suitability
There is not an exact science to what the team may need to see and therefore it might be most sensible that using the filter they can choose to see any of the fields within the application form except for personal information outside of the name of the candidate and reference number (that includes reasonable adjustments which are captured in a separate report) and the equality and diversity information which is captured in that report and in the contacts download.
This is an on screen report and they just need to clear see the numbers of candidates for the criteria they have decided to see in the report and Admin should be able to download data  in an excel spreadsheet.

@warrensearle How would I get this into like a 5 and a 3?

If we are unable to create a filter so that admins can choose to see any of the fields within the application form, we will need to go to the Design Group to workshop what reports are essential/required.

Assigned to Drie in March WO.

hello @warrensearle is there an update on this ticket?

Can we make this report downloadable - following convo with Joy and Kate.

[ ] Add video recording

https://www.loom.com/share/57c3e099214540e4a13ef303de1905ab

https://www.loom.com/share/8cdfbd0cfc864e20ad5ee2fffaff1317


Dockerized app with parameterised redis host & port

While running sidekiq workers in containerised environments, it would be helpful to have the exporter run within a container native to the rest of the application ecosystem.

copy-paste from the issue
Closes #23

May I ask how this will be used? In the projects, I'm involved, we also run exporter inside the docker and separated from the rest. And this is a ruby gem ...
More important is that this library allows you to write any kind of bootstrap and it's not limiting your choices of how to export your metrics. For instance, suggested config.ru covers just a few configuration options of the Redis connection.
Can you please clarify issue #23 (better in this PR)?

want to be able to run this in Kubernetes. I have been working on a helm chart for this as well. tested out and ready for PR(will create a separate issue for that). needed the docker image as a pre-requisite. people will always have the ability to override the docker image with something more custom that satisfies their needs but this is just a default to begin with.
P.S. looking to eventually leverage KEDA to start scaling of workers based on queue lengths

@mikhailadvani Ok, I see, give me a bit of time to make a review. Also since you want to have a docker image we can put it into hub.docker.com after we build this one

sure @Strech you can test the image I built at mikhailadvani/sidekiq-prometheus-exporter

Hey @mikhailadvani thanks for your amazing proposal 👏
I start digging into what exactly we are going to build and I find out some other images already in the hub.docker.com also, it turns out that if I will review this PR it may convert into programming via PR.
So what I would like to suggest – can you review this PR instead https://github.com/Strech/sidekiq-prometheus-exporter/pull/25 I will very appreciate your input


Expense Manager

This is an 'Expense Manager' built using the basic features of file handling in python, It is a GUI enabled python script. GUI is made using 'Tkinter' module in python. #1 @Logan1x

Please put the .py file in the root folder i.e. this and give description about how to run and what your file is in readme.md

Cool 🤘🏻 @akshitgrover  thanks for your contribution's.


python311Packages.google-cloud-bigquery-logging: 1.4.2 -> 1.4.3

Changelog: https://github.com/googleapis/google-cloud-python/blob/google-cloud-bigquery-logging-v1.4.3/packages/google-cloud-bigquery-logging/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 293799 run on x86_64-linux 1

2 packages marked as broken and skipped:

python312Packages.google-cloud-bigquery-logging
python312Packages.google-cloud-bigquery-logging.dist

2 packages built:

python311Packages.google-cloud-bigquery-logging
python311Packages.google-cloud-bigquery-logging.dist


chore: remove unused runcitadel sdk

Describe the changes you have made in this PR
Removes the citadel npm package
Link this PR to an issue [optional]
Step 2: #1314
Type of change
(Remove other not matching type)

chore

Checklist

[x] My code follows the style guidelines of this project and performed a self-review of my own code
[x] New and existing tests pass locally with my changes
[x] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

Socket Security Pull Request Report

Not sure why these packages are named. They haven't been changed in the this PR. At least they do not shpw up as changed in the lock-file diff or am I missing something?


Wrong link to the profile after finishing unfollowing

When i hover on the username (after the unfollowing process) the link to the profile is wrong

As you can see below on the picture "https://www.instagram/www.instagram/USERNAME"
Suggestion
This feature isnt that bad if you can add it even before i start unfollow them. This way i can check more faster their profile before
selecting them. (copy and paste is tooo muchh )

When i hover on the username (after the unfollowing process) the link to the profile is wrong

Yeah, this will be fixed as part of #30.

This feature isnt that bad if you can add it even before i start unfollow them

Sound good! will probably add this too.

@onnipotenza

When i hover on the username (after the unfollowing process) the link to the profile is wrong

This was fixed.

This feature isnt that bad if you can add it even before i start unfollow them

This was added.
Now both places that show the username (the results and the unfollow log), are a link to the relevant profile.
Note that it doesn't appear as a link at first, mostly because it didn't look very good, but if you hover over the username it'll become underlined.
Also, the main Readme file wasn't yet updated with the new script, so you can just copy it from the relevant file.
Just for now, until it gets updated.
Link to minified file:
https://github.com/davidarroyo1234/InstagramUnfollowers/blob/master/dist/dist.min.js

I just tried it and the new interface look amazing. Thanks @tomleb3


m6i not ilisted in eni-max-pods.txt

What would you like to be added:
m6i support.
m6i is not listed in https://github.com/awslabs/amazon-eks-ami/blob/master/files/eni-max-pods.txt
Why is this needed:
see AWS m6i blogposts about how amazing it is if it was available in EKS.

related: https://github.com/weaveworks/eksctl/issues/4106

looks like this is possibly resolved via #735


Translate Docs to Greek - work-in-progress

I would like to start translating vuejs.org DOCS to the Greek language.
Anyone is welcome to contribute to this translation.
Thank you,
Merianos Nikos

Closing in favor of #2015. Feel free to add a link there.


Data does not sync across devices

I have 2 computers that I use for different things and it's really frustrating that the poms I do on one computer do not show up in my pom history on the other. This sort of defeats the purpose of aggregating all the data and renders it completely inaccurate.

I miss this feature too.

I miss this feature too.

I do a manual sync of the excel report for now.


Adding other Redux maintainers as NPM publishers?

Hi, @ellbee . Not sure how else to contact you, so hoping you'll see this.
I know you haven't been very active with Reselect for a while.  Given that, could you look at adding myself and @timdorr as publishers on NPM? We already have commit rights to the repo itself as part of the reduxjs org.  That way we at least have the ability to put out new Reselect builds if necessary.

Resolved - Tim and I now have publish rights on NPM.


What tool are you adding and to what category?
We need to add MasterClass to Course Platforms.
Add Tool Link
https://www.masterclass.com/?irclickid=XBs0Kj2UZxyPUd8XKpRHgWgzUkFzAb18Z2jiQs0&utm_source=impact&utm_medium=affiliate&utm_campaign=&utm_content=1317543&utm_term=1359419&irgwc=1

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] The tool is free for use

@JasonDsouza212 Please assign this issue to me under GSSOC'23.

@blindaks is it free


Extra process guards

Following on from earlier PR (https://github.com/apple/swift-package-manager/pull/921) and bug SR-3275 - adding in the mechanisms to support the extra guard logic for validating that an executable file (i.e. git, etc) exists, and making the results when it doesn't exist more consistent across all the various underlying toolchains.
Here for visibility and feedback...
Next steps:

[x] rebase after https://github.com/apple/swift-package-manager/pull/1002 & https://github.com/apple/swift-package-manager/pull/1003 merged
[x] add in string output handling for new errors enums in Commands/Errors.swift
[x] add in relevant tests to validate

@aciidb0mb3r PR updated after the various merges - still need to write tests, but wanted to get your eyes on this first. Was tough choosing where to put in a relevant check to validate git that wasn't in 1000 places, but also wasn't checked when not needed. I aimed for a putting it in getActiveWorkspace (which looked like it was always in the right flow for the places where this check would be valuable) with the idea that any of the tool's running runImpl would leverage that method and get the check, and I could throw an error from there, and update the Error handling output in Commands/Error.swift to print appropriately. This sound like an acceptable plan of attack, and stubbed/initial implementation?

@aciidb0mb3r I think it's ready for a review - I can rebase to a single commit before merging, but wanted to get feedback from here.
I leveraged the other PR's adding in the various guards, and this wraps around Process to check for errors using that simple cache mechanism. I've also added some messaging and handling into Commands/Error.swift to cover the execution failure within Process

@aciidb0mb3r simplified and updated, including the lookupExecutable method in misc and corresponding tests. Also rebased the whole kit to a single commit. I haven't make this explicitly thread-safe, so no improvements on that front from earlier commits, but I think it's in good order as it stands.

thanks @xwu appreciate the call-outs - updated.

I suspected that might be the path you suggested. I'll update

@aciidb0mb3r give it another look-see? Changes made, methods collapsed, and rebased onto latest master into a single commit.

@swift-ci please smoke test

@swift-ci please smoke test

@heckj Thanks for working on this!

Thank you for the guidance and pointers on threadsafety!


Where can I find your paper

Hi，
Where can i find your paper?

you can find the paper in here.
https://openaccess.thecvf.com/content/ACCV2020/papers/Stoiber_A_Sparse_Gaussian_Approach_to_Region-Based_6DoF_Object_Tracking_ACCV_2020_paper.pdf

In addition to the ACCV paper, the paper for SRT3D and ICG are both available on arXiv:

https://arxiv.org/abs/2110.12715
https://arxiv.org/abs/2203.05334


TEST-#0000: pin ipython<8.13.0 for python 3.8

What do these changes do?

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[ ] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] signed commit with git commit -s
[ ] Resolves #?
[ ] tests added and passing
[ ] module layout described at docs/development/architecture.rst is up-to-date

It seems that ipython is being implicitly installed for documentation build, let's try adding the ipython<8.13.0 restriction in our requirements-doc.txt file

Maybe it makes sense to wait for a fix for https://github.com/ipython/ipython/issues/14053

I think we can wait until Monday and if it won't be fixed until then I'll merge this PR

so the problem was fixed on ipython's side (https://github.com/ipython/ipython/issues/14053), so closing our issue


Tigerbeetle probably needs to run latest version of Zig (0.10.0)

Hello, I am using MacOS Ventura 13 and Zig version lower than 0.10.0 'panics' as discussed in thread https://github.com/ziglang/zig/issues/10478.
Looks like tigerbeetle-node should run this newer version of Zig in order to have working packages on Ventura 13.
The issue is happening when I try to run pnpm i.
The stack trace:
Scope: all 7 workspace projects
Lockfile is up to date, resolution step is skipped
Packages: +1646
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 1646, reused 1630, downloaded 0, added 0, done
<EMAIL_ADDRESS>Running postinstall script, failed in 9s
.../node_modules/tigerbeetle-node postinstall$ npm run install_zig && npm run download_node_headers && npm run build_lib
│ ><EMAIL_ADDRESS>install_zig
│ > ./src/tigerbeetle/scripts/install_zig.sh
│ Installing Zig 0.9.1 release build...
│ Downloading https://ziglang.org/download/0.9.1/zig-macos-aarch64-0.9.1.tar.xz...
│ Extracting zig-macos-aarch64-0.9.1.tar.xz...
│ Installing zig-macos-aarch64-0.9.1 to 'zig' in current working directory...
│ Congratulations, you have successfully installed Zig 0.9.1 to<EMAIL_ADDRESS>│ ><EMAIL_ADDRESS>download_node_headers
│ > ./scripts/download_node_headers.sh
│ Downloading https://nodejs.org/download/release/v16.18.0/node-v16.18.0-headers.tar.gz...
│ Extracting ./build/node-v16.18.0-headers.tar.gz...
│ ><EMAIL_ADDRESS>build_lib
│ > mkdir -p dist && zig/zig build-lib -mcpu=baseline -OReleaseSafe -dynamic -lc -isystem build/node-$(node --version)/include/node src/node.zig -fallow-shlib-undef
│ thread 403088 panic: Darwin is handled separately via std.zig.system.darwin module
│ Unable to dump stack trace: debug info stripped
│ sh: line 1: 55468 Abort trap: 6           zig/zig build-lib -mcpu=baseline -OReleaseSafe -dynamic -lc -isystem build/node-$(node --version)/include/node src/node.
└─ Failed in 9s

Thanks for the reply @sentientwaffle - anything that can be done in the meantime?

I'm not too familiar with Mac OS or the zig compiler internals, so I won't be much help there.
You could try running the current version within Docker, though.

Thanks @sentientwaffle, do you have an approx. idea on when the upgrade will be available? :)

@Tymmmy probably soon after Zig 0.10.1 lands (whenever that is :wink:) — we are blocked from upgrading by https://github.com/ziglang/zig/pull/13017.


User Story: GA4GH Workflow Execution Showcase

As a user, I would like to showcase a full end-to-end MMG-CWL and/or MMETSP workflow at the GA4GH 6th Plenary by Oct 2018, so that I can further my research publication objectives and engage with the global standards initiative.

We presented successfully at the plenary with a multi-step workflow, that was created by MMG team.


Use a proper Url data type for the OktaAuth0 / OktaConfig structs

The OktaAuth0 struct and OktkaConfig struct currently accept a String for the tenant_base_url:
pub struct OktaAuth0 {
    pub tenant_base_url: String,
    pub client_id: String,
    pub certificate: String,
}

We should use a Url instead.

I would like to take this one! @etorreborre

Please do @aleksandarskrbic!

Fixed with #5368


Update Header and Footer to Common Component

Definition of Ready

[ ] Does this meet the INVEST criteria?
[ ] Does this have a clearly defined user?
[ ] Does this have an estimate?
[ ] Does this have acceptance criteria?
[ ] Does this have sufficient context (wireframes, business rules, etc.)?
[ ] Is this traceable to a feature, epic, or PI?

User Story
As a user
I want the header and footer to be consistent across EASEY apps
So that I can have consistent experience
Acceptance Criteria
Given
When
Then
Does this Story require 508 Testing?

[ ] Implementing a new authoring tool that will produce code / content for the application
[ ] Implementing a 3rd party widget that will be part of the application
[ ] Adding new / updating custom functionality
[ ] Adding new / updating a page template
[ ] Adding new / replacing existing functionality (unless the replacement has already passed 508 testing)
[ ] Full Site Review prior to a scheduled EPA 508 review
[ ] Planning a video that will appear on the application
[ ] Producing a video that will appear on the application
[ ] Producing Training materials
[ ] Producing documents

Context
(User journeys, design mockups, architectural diagrams, business rules, data element definitions)
Testing
Test Case:
Tester:
Definition of Done

[ ] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[ ] Has the code been unit tested and peer reviewed?
[ ] Have the functional tests been executed?
[ ] Have all defects been reviewed and dispositioned, resolved, or deferred?
[ ] Has the user story been accepted by the Product Owner?
[ ] Is the user story ready to be deployed to the test/staging environments?

Ticket no longer needed. Will be handled by the tech team in ticket Refactor CAMPD UI to use easey-design-system components#1572

Need to discuss this ticket further. Is there additional work after the tech team builds the header and footer


Update to syn 2

Closes #92
Closes #94
Commits taken from #93 and squashed

I'm going to release this as 0.1.3 as this doesn't change any features at all that the crate provides.


The short distance to get the pointcloud

What is the shortest distance of the point cloud captured by the camera? Is there a manual to get this data? On the other hand, does the color of the object surface affect the point cloud quality? Because I found that the black surface gets better point cloud quality than the white surface. Why?

At the moment we have 3 product lines - structured light SR300, stereo D400 and lidar L500.
Which camera are you using?

D435 resolution is 680*360

At the moment we have 3 product lines - structured light SR300, stereo D400 and lidar L500.
Which camera are you using?

D435 resolution is 680*360

Hi wuhaoqi-hub
Under 640x360 on D435, the minimum depth distance is around 16cm (around 6"). Stereo 3D camera likes to see the objects with random texture patterns regardless of the color. If there is nothing on object surface, i.e. white wall, the laser projector can add IR dots on the object surface to assist camera to get 3D vision.

Any further question? otherwise the ticket will be close next week. thanks


innerJoinRelation without specifying .select() would overwrite values

eg:
model.query().innerJoinRelation('model2')
would overwrite model's id column with model2's id column as not specifying .select() defaults to '*', no ambiguous column warning is given (using mysql 5.7 with mysql2 as adapter)

There is currently no way of knowing the columns the table has, so we need to use a generic *. jsonSchema is optional and even if one uses it there are cases when the properties in that are different from the table columns. You need to specify select().

That's reasonable, But I think it'll be good to maybe do one of the following

note that in the documentation
default to selecting only model.* unless .select() is specified if innerJoinRelation is used.
you can figure out which columns belong to which table using this trick:

SELECT table1.*, '' AS 'table1_END', table2.*, '' AS 'table2_END' FROM table1 INNER JOIN table2 ON (table1.table2id = table2.id)
This would give you each table columns separated by the table name suffixed with _END, not sure if you'd consider this too "hackish" or not but it should work fine in both mysql variants and postgresql (dunno about sqlite)
Overall I think doing both the first and second option would be best, there are very few scenarios I can think of where defaulting to * with a join is good.
up to you

I think we should default to select model.* as you mentioned. I'll fix this for 0.6.0 release.

Sorry, didn't fix this for 0.6.0 😬 There was so much new stuff in 0.6 and it has been a while since a stable release that I just decided to release it.


Allow controlling major version in the upgrader

This makes it possible to set the target major Vespa version
in the upgrader explicitly for applications that do not.
This allows us to do a more controlled rollout of new major versions.
@mpolden please review
@arnej27959 fyi

Fyi @kkraune and @aressem

great - thanks!


[AD] Indirect passing differentiation support.

This patch adds initial support for differentiation of functions with indirect parameters/results.
There are no regressions for non-indirect-passing differentiation.
TODOs/FIXMEs related to indirect passing are tracked at: TF-199, TF-201, TF-202, TF-204.

Support indirect passing in PrimalGen.

Reabstract pullbacks during PrimalGen using thunks.

This is necessary when actual pullback types are "less direct" than the lowered
primal value struct pullback member types, which are "as direct as possible".
Reabstraction thunk helpers are copied from SILGen and exist as top-level static
functions.

Check callee VJP same-type generic requirements during PrimalGen.

This requires additional logic in
PrimalGenCloner::getOrDiagnoseAssociatedFunctionSubstitutionMap.

Support indirect passing in AdjointGen.

In AdjointEmitter::run():

Modularly register adjoint buffers for original indirect parameters and indirect seeds.

In AdjointEmitter::visitApplyInst():

Select original apply result based on source index.
Previously, the source index and original apply indirect results were not handled.
Modularly create stack allocations for pullback indirect results.
Previously, this was unhandled as pullbacks could not have indirect results.
Handle adjoint buffer accumulation for original apply indirect parameters.
Previously, only adjoint value accumulation was handled.

Implement AdjointEmitter::visitCopyAddr.
Fix cleanup/deallocation for adjoint buffers.

Use (retain|release)_value_addr only for buffers with loadable types.
Otherwise, cleanup using destroy_addr.

Random fixes/gardening.

Fix generic signature handling in SILFunctionType::getAutoDiffAssociatedFunctionType.

Result types should be canonicalized using generic signature,
if specified. This is important for consistency to avoid deserialization
verification crashes.

Check callee VJP same-type generic requirements during PrimalGen.

This requires additional logic in
PrimalGenCloner::getOrDiagnoseAssociatedFunctionSubstitutionMap.

Add tests.

@rxwei: Ready for review. Triggering tests to make sure everything passes as expected.

@swift-ci Please test tensorflow

Before -O is fixed, I think we should make indirect passing support available under a flag.

I'd suggest playing with DeepLearning to see whether things work for libraries.

Lastly, congrats on figuring everything out! This is a huge huge step forward.

Before -O is fixed, I think we should make indirect passing support available under a flag.

I tried to gate indirect passing support via a flag: WIP branch at dan-zheng/swift:ad-indirect-passing-flag.
The blocker is test/TensorFlowRuntime/tensor_autodiff_indirect.swift, for which the following RUN line doesn't work:
// FIXME: Passing arbitrary arguments after `%target-run-eager-swift` doesn't work.
// RUN: %target-run-eager-swift -Xllvm -indirect-passing-differentiation

We discussed in person and decided that not adding a flag is okay.

Indirect passing is known to crash with -O only for niche cases ("ResultSelection" test in test/TensorFlowRuntime/tensor_autodiff_indirect.swift).
Unsupported indirect passing cases don't crash - diagnostics are emitted, which is acceptable. (TF-201, TF-203).

LGTM!

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

Merged to unblock progress. Known indirect passing issues are tracked at primary bug TF-104.


Make grammar fixes in README.md.

This commit just makes some grammar changes to the README.md.

Great work! Thank you :)


Template make example missunderstanding

Problem
make example command is running test_example.
There is a naming collision. template/ directory contains two directories:
test_example/
example/

Where test_example/ is just an example of how to use the template when example/ is an example of how to run terrafom module which lies in the root.
Currently, the command make dev runs terraform module which locates in example/
How to fix
Option 1:
Rename make example to make run-template-example or smth similar
Option 2:
....

I say we rename it to make template_example :) Note: In #267 test_example is renamed to template_example

@zhenik : Can we close this?

The command make example is still controversial to me to understand which example it runs https://github.com/fredrikhgrelland/vagrant-hashistack/blob/template-doc-refactor/template/Makefile#L31

Yeah, it's still just make example. I haven't changed it bexause there is no "consesus" here yet. But I mean, we two agree, let's just change it?

@pdmthorsrud I see that directory waas renamed :+1 , but command is not changed in #267
@Neha-Sinha2305
The command in template/ folder make example is still controversial to me to understand which example it runs https://github.com/fredrikhgrelland/vagrant-hashistack/blob/template-doc-refactor/template/Makefile#L31

Hmm..i get it and surely we should solve this.
I was just wondering if it will be better to add new issues tagged for milestone 0.3.3 instead of 0.3.2, more so for issues that need consensus or discussion. 0.3.2 aims to improve the basic documentation and i guess we have achieved that through the PRs that are already merged so we could focus on releasing these changes so as to keep the momentum going :)

Yeah, I will mark it for 0.3.3


Error while using async conversation

I tried this
import asyncio
import llm

model = llm.get_async_model("llama3.2")

conversation = model.conversation()

async def run():
    response = await conversation.prompt("joke")
    text = await response.text()
    response2 = await conversation.prompt("again")
    text2 = await response2.text()
    print(text, text2)

asyncio.run(run())

This fails with this error
File "/private/tmp/temptest.py", line 17, in <module>
    asyncio.run(run())
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
    return future.result()
  File "/private/tmp/temptest.py", line 12, in run
    response2 = await conversation.prompt("again")
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/site-packages/llm/models.py", line 471, in _force
    async for _ in self:
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/site-packages/llm/models.py", line 458, in __anext__
    chunk = await self._generator.__anext__()
  File "/Users/sukhbindersingh/PROJECTS/llm-ollama/llm_ollama.py", line 260, in execute
    raise RuntimeError(f"Async execution failed: {e}") from e
RuntimeError: Async execution failed: 1 validation error for Message
content
  Input should be a valid string [type=string_type, input_value=<coroutine object AsyncRe....text at 0x7fa261a8ac40>, input_type=coroutine]
    For further information visit https://errors.pydantic.dev/2.10/v/string_type
sys:1: RuntimeWarning: coroutine 'AsyncResponse.text' was never awaited

@simonw Am I doing something wrong?  This works if I replace conversation.prompt with model.prompt but no conversation history as expected.

using the model gemini-2.0-flash-exp
I get this error

  File "/private/tmp/temptest.py", line 17, in <module>
    asyncio.run(run())
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
    return future.result()
  File "/private/tmp/temptest.py", line 12, in run
    response2 = await conversation.prompt("again")
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/site-packages/llm/models.py", line 471, in _force
    async for _ in self:
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/site-packages/llm/models.py", line 458, in __anext__
    chunk = await self._generator.__anext__()
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/site-packages/llm_gemini.py", line 271, in execute
    async with client.stream(
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/contextlib.py", line 181, in __aenter__
    return await self.gen.__anext__()
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/site-packages/httpx/_client.py", line 1604, in stream
    request = self.build_request(
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/site-packages/httpx/_client.py", line 357, in build_request
    return Request(
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/site-packages/httpx/_models.py", line 340, in __init__
    headers, stream = encode_request(
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/site-packages/httpx/_content.py", line 212, in encode_request
    return encode_json(json)
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/site-packages/httpx/_content.py", line 175, in encode_json
    body = json_dumps(json).encode("utf-8")
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/Users/sukhbindersingh/opt/anaconda3/lib/python3.9/json/encoder.py", line 179, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type coroutine is not JSON serializable
sys:1: RuntimeWarning: coroutine 'AsyncResponse.text' was never awaited

Not async version of the code works

import llm

model = llm.get_async_model("llama3.2")
conversation = model.conversation()

def run():
    response = conversation.prompt("joke")
    text = response.text()
    response2 = conversation.prompt("again")
    text2 = response2.text()
    print(text, text2)

run()

(.llm) sukhbindersingh@sukhMacPro llm % python tests/test_real.py
Why don't scientists trust atoms?

Because they make up everything!
Why don't scientists trust atoms?

Because they make up everything! What do you call a fake noodle?

An impasta.
Here's one:

What do you call a fake noodle?

An impasta.

I have the same issue. I believe the issue is that subsequent calls in the conversation, try to include previous responses, however the handling of the previous responses does not account for an instance of AsyncResponse.
With llm-gemini, the request body is built here, which in turn tries to get the text from previous responses in the conversation here. But because the response is an instance of AsyncResponse, we get the error coroutine 'AsyncResponse.text' was never awaited.
As a workaround, I override the text method of the response to make it synchronous, but this is pretty jank...
response = await conversation.prompt(prompt)
result = await response.text()
response.text = lambda: result
response2 = await conversation.prompt(prompt)
result2 = response2.text()

I have pushed fix for this in the llm-gemini plugin repo. The PR is here


expose callbacks

as I started my neovim, I got surprised that my <tab> key was doing non-sense.
As I had just installed llm.nvim the culprit was evident (plus :verb map <tab>). Tab is an important key so I dont think the plugin should hijack it like this. I would prefer for the plugins to expose its callbacks and let me map them. The mapping could be kept in the README out of the setup function.
The setup function meme can be quite annoying when you compose your setup
https://mrcjkb.dev/posts/2023-08-22-setup.html

Do you have any examples of plugins that do it "the right way"?
Also, is this linked to #61?

Historically, plugins expose their mappings via <Plug>Name.
In lua that would give:
vim.keymap.set("n", "<Plug>HelloWorld", function() print("Hello World!") end)
vim.keymap.set("n", "gs", "<Plug>HelloWorld")

in the readme, you could remove the mappings from the setup() but still document them in the snippet:
require("lazy").setup({
  {
    'huggingface/llm.nvim',
    config = function() require'llm'.setup {
      -- cf Setup
      opts
    }
    vim.keymap.set("n", "gs", "<Plug>LlmAcceptSuggestion")
    end
  },
})

but with lua I am not sure you need to go through the Plug route anyway, you could straightaway document:
vim.keymap.set("n", "gs",  function () require'llm'.accept_suggestion() end)

+1
My specific use case is to provide more context to the prompt in order to get more accurate results.