add scatter method to light curves, for more flexible plotting

lc.plot() is an awesome quick tool. I thought it'd be nice if there were a lc.scatter() parallel to it, which would allow folks to use arrays to color individual markers with the c=[some-array] keyword. The particular case I was thinking of for this was to be able to match up actual time (in JD) to phase-folded time across multiple plots (see the test). Is this useful?
I wrote this as an entirely new scatter function because I was nervous to mess with plot. Would you prefer me to compress this into fewer lines of code by adding a usescatter=True/False keyword to plot, which could then trigger in the (very few) lines where the two functions would differ?

I like this sort of functionality, you could imagine adding colors for e.g. the centroids to see if there is a significant change in the image center during the transit!
Plus it'll use the plt.scatter() API which is slightly different to plt.plot()
Let's take a look at your pull request!
Thanks @zkbt!! 😄

Oh fudge, I worry I might have just done that starting from an old version. Let me know if that ruins things, and I'll start over.

Thanks @christinahedges! I love that painting-by-centroid idea! With a good color scale, I feel like that would in some ways be even more intuitive than difference images!

Codecov Report

Merging #228 into master will decrease coverage by 0.12%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##           master     #228      +/-   ##
==========================================
- Coverage   88.79%   88.67%   -0.13%
==========================================
  Files          24       24
  Lines        3114     3160      +46
==========================================
+ Hits         2765     2802      +37
- Misses        349      358       +9

Impacted Files
Coverage Δ

lightkurve/tests/test_lightcurve.py
98.26% <100%> (+0.07%)
:arrow_up:

lightkurve/lightcurve.py
90.89% <76.92%> (-1.29%)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks @zkbt!!  We have a lot going on this week so it may take a few days, but we're all excited to take a closer look at this PR.  I love the color-by-centroid idea, too!

No rush! I’d like to help out, and thought I’d start small!
--------------------------------------
Zach Berta-Thompson
Assistant Professor, Exoplaneteer
(pronouns = he/him/his)
Department of Astrophysical & Planetary Sciences
University of Colorado at Boulder
casa.colorado.edu/~bertathompsonhttp://casa.colorado.edu/~bertathompson
+1(303)735-6821
I stand with undocumented students, staff, and their families.
--------------------------------------
On Aug 22, 2018, at 12:29 PM, Geert Barentsen <notifications<EMAIL_ADDRESS>wrote:
Thanks @zkbthttps://github.com/zkbt!! We have a lot going on this week so it may take a few days, but we're all excited to take a closer look at this PR. I love the color-by-centroid idea, too!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/KeplerGO/lightkurve/pull/228#issuecomment-415133048, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEeUibLIqMKINLUK2apXUwbP0WuzeI83ks5uTaMjgaJpZM4WGtXF.

Hey @zkbt! We loved the idea of adding in a scatter plotting function! I've taken the PR you made and created a few changes to hopefully improve all our plotting and add some more sensible defaults. Sorry to change things up!
I've added a new ✨ style sheet ✨ to lightkurve which will produce easier to read plots that are a little easier on the eye!
There are some demos below. Does this capture the functionality you were going for?
lc.plot()

lc.scatter()

lc.scatter(c=ITERABLE)

tpf.plot()

Amazing! Yes! This is exactly what I was hoping for!
I have one other hope, but I'll open another issue on it!

I've been refactoring the code a bit.  Most notably, I've introduced a hidden helper method called _create_plot which is called by both lc.plot() and lc.scatter() to avoid code duplication.

Hey @barentsen this is great, we should add an lc.errorbar() function though as this is no longer showing error bars in our plots! Alternately we can have errorbars show by default, perhaps with a lc.plot(show_errorbars=True) keyword.
I can open another PR?

@christinahedges Yes please!  I forgot that we did support error bars in the past :fearful:

@barentsen also I see why you want a _create_plot() function, but that has removed the functionality I added to have a colorbar with a scatter plot...which I think was the original point of the PR. We need to add that back in.

@christinahedges D'oh, apologies, I'm surprised I overlooked that.  Let's add it back in for sure.


Updates from react-media-recorder-2

This PR is simply taking the current state of react-media-recorder-2 and merging it into react-media-recorder. I don't plan on modifying this PR, so if you have a different strategy for doing this feel free to delete mine.
Also, huge shoutout to @marefati110 for maintaining react-media-recorder-2 in the meantime!

Closing in favor of https://github.com/DeltaCircuit/react-media-recorder/pull/142


[#50] Add Resources section to Java installation guide

Part of #50
Added links to the official SDKMAN documentation and a video installation guide, might be useful for students who want to delve deeper into the software or need a more visual approach to guide them through the process of installing the tool.

@itstrueitstrueitsrealitsreal The first link is mentioned in the intro. I added the video at the relevant place in the main body in https://github.com/se-edu/guides/commit/fdc8a23cb00c767b177511cb749e0e8a31b47566


Long names spill out of compose box

Long names spill out of the compose box on the right:

Initial investigation:

Karl Stolley: Poked at this a bit today, but there's no obvious fix. Once we're using more grid instead of a series of flexboxes in the compose box, this should be easier to manage. But I'll return next week to develop an interim fix. An easy but heavy-handed one would be to just decide on a maximum width, in pixels, for user pills.

Karl Stolley: Some more notes to self here: we're using a ton of inline flexes in this area, but the outer .pill-container itself should just be a regular old display: flex; the inline behavior really should be handled just by the flex-wrap property there. Then it's a matter of getting the Matryoshka dolls of flexes-within-flexes to behave as expected within the bounds of the pill container.

CZO thread

@zulipbot claim


Updating the sonar versions

@jagdeep-sonar Please separate support for major version from patch version. Patch version can be merged to dev immediately while merging major version is a more complex process and you have to wait for all the DSF teams to add
their support.

Also, 3 of the 5 actions failed on this branch. All actions should be green before we approve.

Ok Linda.. i will separate support for major version from patch version.
and how will I get to know if all the DSF teams have added their support for major version?

Thank Jagdeep. My team is responsible for releasing an eDSF Kit version when a new DSF version is released, so once you created the PR and saw that the actions passed, your job is done, unless we find issues with the integrations between Sonar, DAM and DRA later. Please take a look at the procedure that my team does here: https://docs.google.com/document/d/1vNp3P6JH9QAsHtnNqpkFtTLMZD7sZT6eeNsu8lK2CVo

Ok Linda. Got it. I will close this PR and raise separate PRs for major and patch version. Thank you.


Fix search episode endpoint with series name

This PR fix a problem in search endpoint. The search endpoint cannot handle sname (series name) properly in develop branch.
Test plan:

Create a series with title foo
Add an event bar and add the event to the foo series
Search episode in search endpoint ( https://opencast.domain/docs.html?path=/search) , GET /episode.{format:xml|json} with following parameters

format: json
sname: foo

Expected behavior
bar should be included in the search result.
Actual behavior
bar is not included in the search result. The search result is empty.
Explain
The following code is used to set the series name condition
.withQuery("dc_title___:" + SolrUtils.clean(seriesName));

I'm not familiar with Solr. But after I changed the code to
.withQuery("dc_title_:" + SolrUtils.clean(seriesName));

The problem is solved.
Your pull request should…

[ ] have a concise title
[ ] close an accompanying issue if one exists
[ ] be against the correct branch
[ ] include migration scripts and documentation, if appropriate
[ ] pass automated tests
[ ] have a clean commit history
[ ] have proper commit messages (title and body) for all commits

As always, thanks for the patch @Gao-Jun!
This revealed another issue in r/10.x.
Once #2923 is in, this is probably unnecessary. I'll come back to this once we proceed there.

The problem is solved in 10.2
I think this PR could be closed.

You are right. Forgot about closing this. Doing so now…


Add candy crush game

I want to add candy crush game onto the FunFusion website. I am attaching a screenshot for reference.

@Priyanshi662 Please assign me this issue under JWOC.


Add source.sortImports support for .vue files in Volar

Preamble
I think this issue needs to be in language-tools, but that repo has limited issue reporting to existing contributors, so I can't post this there. If it does need to be moved, I would appreciate a contributor adding it over there. Thank you in advance!
Request
I use VS Code for Vue development with the Volar plugins. In my VS Code config I used to use source.organizeImports in editor.codeActionsOnSave but it deletes unused imports which can break an application. I read that VS Code v1.57 added the source.sortImports action for javascript and typescript files. However, this action has no effect on .vue files.
Please add source.sortImports support for .vue files so I can automatically organize my inputs in a non-destructive manner.
Thank you!

Coincidentally this is not a vuejs/language-tools issue, I'll be tracking it here.

pls! this is a large pain point. thanks for all your hard work Johnson.

Don't know which version it is, but this has been fixed.


fix(deploy): typo in mayastor daemonset url

Corrects a typo in the url for the Mayastor I/O daemonset
Signed-off-by: GlennBullingham<EMAIL_ADDRESS>

resolves: https://github.com/openebs/mayastor/issues/1232


Prevent create files on PEX ROOT as root when pex file is run with sudo

Run a pex with sudo the first time:
sudo my-pex.pex

It creates files under in my HOME ~/.pex/install/ with root as owner,
$ ls -la ~/.pex/install/
total 0
drwxr-xr-x 1 root   root   3818 Nov 28 17:03 .
drwxrwxr-x 1 user user   14 Nov 28 17:03 ..
drwxr-xr-x 1 root   root     76 Nov 28 17:03 attrs-19.3.0-py2.py3-none-any.whl.e91da08a7091c46772d87f0c961a63ac85d4a810
drwxr-xr-x 1 root   root     82 Nov 28 17:03 requests-2.22.0-py2.py3-none-any.whl.9523c112783d316b50f5bfd5d4bcad40736336aa
.........

Later when the same pex is run without sudo it produces PermissionError
Traceback (most recent call last):
  File "/usr/bin/my-pex.pex/.bootstrap/pex/pex.py", line 395, in execute
  File "/usr/bin/my-pex.pex/.bootstrap/pex/pex.py", line 93, in _activate
  File "/usr/bin/my-pex.pex/.bootstrap/pex/environment.py", line 249, in activate
  File "/usr/bin/my-pex.pex/.bootstrap/pex/environment.py", line 357, in _activate
  File "/usr/bin/my-pex.pex/.bootstrap/pex/environment.py", line 238, in _update_candidate_distributions
  File "/usr/bin/my-pex.pex/.bootstrap/pex/environment.py", line 203, in _load_internal_cache
  File "/usr/bin/my-pex.pex/.bootstrap/pex/environment.py", line 190, in _write_zipped_internal_cache
  File "/usr/bin/my-pex.pex/.bootstrap/pex/util.py", line 166, in cache_distribution
  File "/usr/lib/python3.7/zipfile.py", line 1599, in extract
    return self._extract_member(member, path, pwd)
  File "/usr/bin/my-pex.pex/.bootstrap/pex/common.py", line 121, in _extract_member
  File "/usr/lib/python3.7/zipfile.py", line 1662, in _extract_member
    os.makedirs(upperdirs)
  File "/usr/lib/python3.7/os.py", line 211, in makedirs
    makedirs(head, exist_ok=exist_ok)
  File "/usr/lib/python3.7/os.py", line 211, in makedirs
    makedirs(head, exist_ok=exist_ok)
  File "/usr/lib/python3.7/os.py", line 221, in makedirs
    mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/home/user/.pex/install/pyrsistent-0.15.6-cp37-cp37m-linux_x86_64.whl.5e52dba7dab3ea7ab9594ad73326d31baf150835.a8407da79a3145ad8d2ed53f8f654852'

Maybe this files can be created with the real user ownership

@carlosduelo I don't think Pex ever wants to learn sudo, ie check for:
$ sudo /usr/bin/env | grep SUDO_
SUDO_COMMAND=/usr/bin/env
SUDO_USER=jsirois
SUDO_UID=1000
SUDO_GID=1000

There is a can of worms here. If the user did intend to run with sudo then ..., etc.
#929 provides the best relief I can think of, which is to warn when pex can't write to PEX_ROOT (~/.pex by default) and instead write to a temporary directory. WIth this feature, pex will now work in the scenario you describe, but like so:
$ ./dist/pex --pex-root=/root/.pex -o empty.pex
/home/jsirois/.pex/installed_wheels/0038e7d1e7d68a69b212b2cbe3915b17a83355b7/pex-2.1.6-py2.py3-none-any.whl/pex/variables.py:281: PEXWarning: PEX_ROOT is configured as /root/.pex but that path is un-writeable, falling back to a temporary PEX_ROOT of /tmp/tmpk4mwqwvn which will hurt performance.
  pex_warnings.warn('PEX_ROOT is configured as {pex_root} but that path is un-writeable, '

So, your PEX will run with a bit worse performance and you'll get a warning about the problem. You still have to clean up your ~/.pex dir, but hopefully this helps.


chore: move Multiset.lift_coe

This lemma doesn't mention any functors, so can go much earlier.

Thanks!
maintainer merge

Thanks!
bors merge


Blog Post API not supporting all the filters

I'm trying to use the GetPage API in the BlogPostsAPI, but it only supports the date-related criteria, while in the HubSpot documentation here, The document mentions we can filter all of the fields. Like language__eq=en, that results in blogs with only language=en.

The API clients in this package are generated directly from the Hubspot openapi spec. If there's not a filter in the code, that's because there's not a filter defined in the spec.
It looks like Hubspot lets you filter on any field as you noted, and has opted not to represent this in the spec. Two approaches we could take on this one:
Customize HTTP request with function options
One approach is to allow you to modify the HTTP request prior to sending it to the HTTP client. That would require a pretty big set of changes to function signatures from
func (a *BlogPostsApiService) GetPageExecute(r ApiGetPageRequest)

to something like this
func (a *BlogPostsApiService) GetPageExecute(r ApiGetPageRequest, options ...func(*http.Request))

and then you could apply the filters against a reference to the HTTP request. I'm not sure what kind of time I'd have to implement this in the short term, but would be happy to discuss this option and other alternatives in more depth with anyone else who would be interested in helping me implement it.
Use alternative openapi generators that support this behavior
I think that oapi-codegen might support this, but would need to investigate more to be sure. The downside to this approach is it would entirely change the current API of the generated clients.
Very bad, temporary workaround
type TransportFunc func(r *http.Request) (*http.Response, error)

func (f TransportFunc) RoundTrip(r *http.Request) (*http.Response, error) {
    return f(r)
}

c := blog_posts.NewAPIClient(&blog_posts.Configuration{
	HTTPClient: &http.Client{
		Transport: TransportFunc(func(r *http.Request) (*http.Response, error) {
			if strings.Contains(r.URL.Path, "/cms/v3/blogs/posts") {
				// Modify the query string with the language filter
			}
			return http.DefaultTransport.RoundTrip(r)
		}),
	},
})

c.BlogPostsApi.GetPage(context.Background()).Execute()


Opening a dataset with a projected CRS does not convert the dataset's coordinates

This seems to lead to errors later on when attempting to write results back to a geotiff using rioxarray.
Full notebook to reproduce: https://colab.research.google.com/drive/149vNtVZ0lGJn5PXxfn7oaTS1VoJX0Qec?usp=sharing
Opening a dataset without specifying a crs:
unprojected_ds = xr.open_dataset(
    col,
    engine="ee",
    scale=0.0025,  # degrees
    geometry=geometry,
)

And then writing to a geotiff using:
def to_raster(ds, fname, crs="epsg:32610", x_dim="X", y_dim="Y"):
    ds = ds.transpose(y_dim, x_dim)
    ds = ds.rio.set_spatial_dims(x_dim=x_dim, y_dim=y_dim)
    ds = ds.rio.write_crs(crs)
    ds = ds.rio.reproject(crs)
    ds.rio.to_raster(fname)

to_raster(
    unprojected_ds.mean(dim="time"),
    "unprojected_dataset.tif",
    crs="epsg:4326",
    x_dim="lon",
    y_dim="lat",
)

And then uploading that geotiff to earth engine produces an image that has the right dimensions and is located properly:

Opening a dataset with a specific crs:
ds = xr.open_dataset(
    col,
    engine="ee",
    scale=10,
    crs="epsg:32610",
    geometry=geometry,
)
to_raster(ds.mean(dim="time"), "dataset.tif")

Writing to geotiff and then uploading to earth engine produces an image that is located in the wrong location (over the equator in the pacific ocean, should be over san francisco), has the wrong dimensions (225x181 vs 203x206), and the wrong scale (0.000103m vs 10m):

Transforming the coordinates of a dataset opened with a crs:
def transform_coords(dataset):
    x = dataset.coords["X"].values
    y = dataset.coords["Y"].values

    _x = np.linspace(np.min(x), np.max(x), y.shape[0])
    _y = np.linspace(np.min(y), np.max(y), x.shape[0])

    transformer = pyproj.Transformer.from_crs("epsg:4326", crs, always_xy=True)
    x_prime = transformer.transform(x, _y)[0]
    y_prime = transformer.transform(_x, y)[1]

    return dataset.assign_coords({"X": x_prime, "Y": y_prime})

transformed_ds = transform_coords(ds)
to_raster(transformed_ds.mean(dim="time"), "transformed_dataset.tif")

And then uploading to earth engine, produces an image that is properly located and has the right dimensions (the scale is slightly off, but I think that has to do with the hacky method I'm using to transform the coordinates here):

Writing to geotiff and then uploading to earth engine produces an image that is located in the wrong location

Hello @boothmanrylan you haven't passed EPSG:4326 into the to_raster.
ds = xr.open_dataset(
    col,
    engine="ee",
    scale=10,
    crs="epsg:32610",
    geometry=geometry,
)
to_raster(ds.mean(dim="time"), "dataset.tif")

Due to this, the raster created is in projection EPSG:32610.  Furthermore raster created for unprojected_ds is in EPSG:4326.  In reality images are plotted in the correct location as per its projection (plotting depends on image projection).
So If you pass EPSG:4326 into the to_raster for the above code then it will match with unprojected_ds raster file.


Wrong path?

Hi,
I followed the Installation guide, but tried to install openvpn-status on a standalone machine. The OpenVPN server is running on another system in the same LAN.
OS: Ubuntu 16.04.4 LTS
Node version: v10.5.0
When I navigate to http://:3013, I get this error (which is also shown in the logs):
Error: ENOENT: no such file or directory, stat '/home//openvpn-status/dist/index.html'
Indeed, there is no "dist" folder in openvpn-status.
Any idea?
Thanks!

It seems like you didn't ru npm run build ?

Well, it seems that you're right :)


Integrate nusa-crowd with nusa-catalogue

Provide a way to download data with nusa-crowd/datasets from nusa-catalogue

#self-assign

Closing this one on https://github.com/IndoNLP/nusa-catalogue/pull/13


fix: Finding main view controller on iOS

In a situation when rootViewController is not set by the application, the main view controller is not found, resulting in error:
Attempt to present <STP_Internal_BottomSheetViewController> on  (from ) whose view is not in the window hierarchy.
which then prevents the Stripe bottom sheet from showing. Blocking the payment flow.
To prevent this, a fallback is added to traverse the windows hierarchy and find the first one that has isKeyWindow set to true.
Testing

[x] I tested this manually
[ ] I added automated tests

Documentation
Select one:

[ ] I have added relevant documentation for my changes.
[x] This PR does not result in any developer-facing changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Very good catch @dluksza, hopefully we can go back to a release version of stripe before we launch the marketplace for OneFootball and 11TeamSports end of next month.

hey @charliecruzan-stripe, what are we missing to get this in? Sorry to bother, but we're happy to make any changes requested and go back to use Stripe from trunk :D


Race condition when using 1+ shards

This affects the pr/14 branch.
When the handle() function is called, it uses the passed in client object to get the shard (if existent), and then calls fetchClientValues(). If all shards aren't ready, this throws an error and fails to post the information.
This happens because shards are started at a delay. If shard 0 doesn't call handle() when every shard is ready, this will error every time. The solution is to wait until all shards are ready before running the fetchClientValues code.
Normally, you might think 'Just use the event that runs when all the shards are ready.' That event doesn't exist, though. The only way to dynamically wait before calling the function is to write your own implementation of an allShardsReady event or some other way of waiting for every shard to get ready.
Another, a simpler solution would be to just wait 45 or so seconds before calling the function and hope your shards are ready then.

should be fixed

Is not fixed, same error.


Remove generics from Stark Prover and Verifier

Description
Resolves #291.
Removes generics from the hasher methods. This includes everything that uses those methods.
NOTE: We should merge #297 first and resolve conflicts.
Type of change

Bug fix

Checklist

[x] Linked to Github Issue
[x] Unit tests added
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

[ ] This change is an Optimization

[ ] Benchmarks added/run

Codecov Report

Merging #293 (78258bc) into main (df9e07f) will decrease coverage by 0.29%.
The diff coverage is 97.37%.

@@            Coverage Diff             @@
##             main     #293      +/-   ##
==========================================
- Coverage   96.43%   96.15%   -0.29%
==========================================
  Files          92       91       -1
  Lines       11525    11459      -66
==========================================
- Hits        11114    11018      -96
- Misses        411      441      +30

Impacted Files
Coverage Δ

proving_system/stark/src/proof.rs
0.00% <ø> (ø)

crypto/src/merkle_tree/merkle.rs
88.23% <70.00%> (-11.77%)
:arrow_down:

crypto/src/merkle_tree/proof.rs
85.26% <82.60%> (-13.77%)
:arrow_down:

proving_system/stark/src/air/trace.rs
90.17% <93.75%> (+0.45%)
:arrow_up:

crypto/src/hash/sha3/mod.rs
88.00% <100.00%> (+0.50%)
:arrow_up:

fft/src/polynomial.rs
94.02% <100.00%> (ø)

fft/src/roots_of_unity.rs
97.56% <100.00%> (ø)

...src/field/fields/montgomery_backed_prime_fields.rs
92.66% <100.00%> (+0.01%)
:arrow_up:

...ving_system/stark/src/air/constraints/evaluator.rs
100.00% <100.00%> (ø)

proving_system/stark/src/air/example/cairo.rs
99.51% <100.00%> (+<0.01%)
:arrow_up:

... and 11 more

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Converting to draft until we merge #267.

We will remove generics as needed when changing the protocol to match the Starkware verifier


New version: UnsafeAssume v1.0.1

Registering package: UnsafeAssume
Repository: https://gitlab.com/nsajko/UnsafeAssume.jl
Created by: https://gitlab.com/nsajko
Version: v1.0.1
Commit: ed16634ef2a6f632b663b7740250ab13571a3952
Git reference: HEAD
Release notes:

assume effects

block

Seems this'll have to wait until I drop support for Julia 1.9.


Adding Dockerfile for dotnet

I've just created a new image for dotnet coreclr, basically it was created from https://github.com/aspnet/aspnet-docker/blob/master/1.0.0-rc1-update1-coreclr/Dockerfile (size 357.7 MB compare with this one 69.58 MB, a significant number smaller than standard image of Microsoft) and we can run a very basic HelloWorld app.
But there're many packages I've ignored since they are not available on Alpine:

libcurl3-gnutls
sqlite3
libsqlite3-dev
libunwind8
libicu-dev
zlib1g

Thanks,
Phi

Thanks!  I assume this is different than the mono image we have?

@treeder Yes, it's only Alpine with the dotnet coreclr since dotnet can run on Linux without based on Mono. As a result, we can shrink down the size really much.

Can you make a README for this like the rest of images.

@trumhemcut , this is awesome!

Still need a README for this. Also, should there be a :dev version?

DNX is an outdate version of coreclr


Add back tutorials using stellar/quickstart

It looks like at some point we've lost tutorials and instructions for how to use quickstart in the main soroban docs. We used to at an early point in the getting started guide help folks run their contracts on their own private network using the stellar/quickstart image.
What I see today is no mention of it, instead only using testnet:

Ref: https://soroban.stellar.org/docs/getting-started/deploy-to-testnet
I think really early on in the developer journey we need to expose them to quickstart. It ideally should be step 3 in this flow. Quickstart is faster to develop against, albeit with some additional setup cost.
We should definitely promote testnet at the same points to and let folks hitup testnet directly. But still include quickstart as the recommended place to test and run contracts.

I think really early on in the developer journey we need to expose them to quickstart. ... Quickstart is faster to develop against, albeit with some additional setup cost.

Can you expand on this? How is it faster to develop against? What are the benefits of having an early exposure to the quickstart workflow?
I know quickstart is a really quick (pun intended lol) thing to spin up, but in my experience it's been faster/easier just to use the Futurenet/Testnet environments that are already created/setup/maintained. The rpc and friendbot urls are pretty straight-forward and easy to remember, I don't have to wait (admittedly, a very short time) for the container to spin up. I'm not very well-versed with docker, so there's a whole skillset I don't need to feel incompetent about hehe. Plus, from playing with "classic" Stellar early on in my dev journey, Testnet was the only method I knew about (although I'm sure quickstart was a thing then) to develop on.
My own experience is probably far from a "good baseline" to make decisions off of, just want to better understand what I'm missing.

I nearly forgot. Some of the quickstart-releated instructions do still exist here: https://soroban.stellar.org/docs/reference/rpc#run-your-own-instance-for-development
Of course, that doesn't address your point about exposing developers to quickstart early on. But, at least the content is still around

We want quickstart to be known, visible early on so folks reach for it when it is right for them. This could be through the getting started section having a "Run on a Local Network" page, similar to the "Run on Testnet" page we have now. We used to have something like that run on a local network before.
Once developers start going, quickstart serves a variety of purposes better than testnet does:

You get 1 second ledger closes, so it is faster to dev against, faster for CI.
It'll soon support a variety of "limit" configurations, so you can develop with unlimited limits, then tune your contract to fit it into pubnet/testnet limits.
No impact from testnet resets.
Can run reproducible test runs with a blank slate.
No impact from testnet congestion.

We see reports from folks who are impacted by testnet resets, etc because they built their dev flow around testnet.
Folks can still use testnet, but exposure to quickstart early means devs that it "speaks to" will know about it upfront, and be able to adopt it when needed later.

Sounds like something to experiment with. If we make the tutorial a dual tutorial for parallel things there's some risk it'll be difficult for the reader to follow. If we stack one tutorial on-top of the other there's some risk that the buried content will be not be discoverable. Maybe there's another way we could present it with inline tabbed code snippets. I defer to what you folks (cc @briwylde08) think is best.

Ooh, I like the idea of making it tabbed... That might be just right. Experimenting a bit sounds like a good step, though.

Hi, I was following the tutorials which said to test contracts with soroban contract invoke --wasm ... (e.g. here and here) but my soroban CLI didn't accept that option. After some digging around it seems like it got removed recently (stellar/soroban-tools#997) in the latest release. Is this quickstart docker image supposed to be the replacement for that, and is this issue tracking updating those parts of the docs as well?

Is this quickstart docker image supposed to be the replacement for that

Yup. The quickstart image provides the same capabilities and more that the original invoke command you're referencing did. So no capability should be lost, but the docs have fallen behind the released tool.

I discussed this with @tyvdh in the weeks leading up to Meridian, and I think we both preferred moving this to Reference. I moved it in https://github.com/stellar/soroban-docs/pull/504.
The goal is to use Divio's documentation system, with the "Getting Started" section as a quick end-to-end Tutorial tour of Soroban's highlights. I think stopping to have people install and run Docker seems like an unnecessary step in that process.
I personally avoid Docker when at all possible, and I don't think I'm alone. From my experience at NEAR, it seems like the vast majority of people prefer to build against Testnet, rather than figure out how to run their own node. But NEAR also pushes people in that direction, and doesn't have a nice quickstart like Soroban's.
Could this be improved with better tooling? Probably. Are we there yet? I don't think so. Maybe once we have a soroban network start command (in progress!), but if it just runs Docker behind-the-scenes then you'd still need to install & start Docker. If it ran quick built-for-your-hardware binaries instead of Docker containers? Definitely; I'd love that so much. I'd way rather build locally against something like that than against Testnet. But I'd way rather build against Testnet than Docker.
Another benefit of building against Testnet: other people can interact with your app! It's just a web page. They don't need to be a developer and run everything locally. So even if we had super quick Docker-free local dev environments, a lot of people still might prefer building against Testnet. I would, for many kinds of projects.
For now, I think it makes sense to add a section at the top of 2. Deploy to Testnet that explains that you can run your own network locally, that it's easy if you're already comfortable with Docker, and explains the benefits mentioned above (I actually hadn't known these until I read this Issue; thanks @leighmcculloch!). Then links to the Run your own RPC Node page.

@ElliotFriend  would love some thoughts here as I know you're restructuring all our docs right now

I'm actually working on this right now!! great timing!
Turns out it's quite trivial to add some synchronized tabs throughout the getting started pages, so that anyone could still copy/paste their way through without much trouble or thinking at all. Essentially, doing exactly this, as suggested by @chadoh:

... add a section at the top of 2. Deploy to Testnet that explains ...

I think since the instructions can be unintrusively presented both ways, it makes sense to provide as much useful info as possible. I should have a PR preview ready in just a bit that would be awesome to have some feedback on.
I'm unfamiliar with Divio's doc system, but at first glance it looks like a really awesome framework to think through this.

Here's the preview from #659, would love everyone's thoughts on this: https://soroban-docs-pr659.previews.kube001.services.stellar-ops.com/docs/getting-started/deploy-incrementor The deploy-incrementor page demonstrates what it ends up looking like.

I like it! Thanks @ElliotFriend!
Still seems useful to have an explainer at the top of 2. Deploy to Test Network. Could be an info box or just a paragraph/bullet points.

Thanks @chadoh! There's a bit of explanation I added to the Setup page, since that's (likely?) where people would first be faced with the decision.
The page that actually talks about deploying to a test network does seem like a place where the explanation might fit (or be expected by someone), though... I'll add it there!

Ah, I see! No, I like where you have it! I would maybe just give a little extra info to help people think through which to use. I liked Leigh's bullet points above. For Testnet, you might want to mention the benefit of being able to deploy apps that other people can try out, rather than needing to run it locally.

+1 as long as we keep it brief a brief enumeration of when to use one or the other would be helpful. Noting that one requires docker.

I'm not sure if I kept it brief enough: https://soroban-docs-pr659.previews.kube001.services.stellar-ops.com/docs/getting-started/setup#configuring-the-cli
Thoughts? @chadoh @leighmcculloch


Can't compute prior (local_log_prob) of a StochasticTensor inside tf.scan (in LSTM cell)

Hi,
I tried to implement the bayesian_rnn from the docs.
However, while trying to compute log_joint, I can't compute the log of prior log_pz because w is declared within a LSTM cell, so I get the following error:
Traceback (most recent call last):
  File "blstm.py", line 111, in <module>
    joint_ll = log_joint({'x': x, 'y_i': y_i, 'y_v': y_v})
  File "blstm.py", line 106, in log_joint
    log_pz, log_px_z = model.local_log_prob(['w', 'y_v'])  # Error
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/zhusuan/model/base.py", line 346, in local_log_prob
    ret.append(s_tensor.log_prob(s_tensor.tensor))
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/zhusuan/model/base.py", line 140, in log_prob
    return self._distribution.log_prob(given)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/zhusuan/utils.py", line 215, in _func
    return f(*args, **kwargs)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/zhusuan/distributions/base.py", line 303, in log_prob
    log_p = self._log_prob(given)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/zhusuan/distributions/univariate.py", line 180, in _log_prob
    return c - logstd - 0.5 * precision * tf.square(given - mean)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/ops/math_ops.py", line 979, in binary_op_wrapper
    return func(x, y, name=name)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/ops/gen_math_ops.py", line 8009, in sub
    "Sub", x=x, y=y, name=name)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
    op_def=op_def)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3392, in create_op
    op_def=op_def)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1760, in __init__
    self._control_flow_post_processing()
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1769, in _control_flow_post_processing
    control_flow_util.CheckInputFromValidContext(self, input_tensor.op)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/ops/control_flow_util.py", line 263, in CheckInputFromValidContext
    raise ValueError(error_msg + " See info log for more details.")
ValueError: Cannot use 'model/scan/while/MatMul/Normal.sample/Squeeze' as input to 'Normal.log_prob/sub_1' because 'model/scan/while/MatMul/Normal.sample/Squeeze' is in a while loop. See info log for more details.

Up-to-run code:
https://github.com/jilljenn/vae/blob/master/blstm.py#L106
How to make it?

Hi, which version of TF do you work on? I think I had that example run on a earlier version.

TensorFlow 1.8.0. I will try earlier, thanks!

In TensorFlow 1.4, the error becomes:
Traceback (most recent call last):
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1323, in _do_call
    return fn(*args)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1302, in _run_fn
    status, run_metadata)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/framework/errors_impl.py", line 473, in __exit__
    c_api.TF_GetCode(self.status.status))
tensorflow.python.framework.errors_impl.InvalidArgumentError: The node 'Normal.log_prob/sub_1' has inputs from different frames. The input 'model/scan/while/MatMul/Normal.sample/Squeeze' is in frame 'model/scan/while/while_context'. The input 'model/zeros' is in frame ''.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "blstm.py", line 144, in <module>
    feed_dict={x: x_batch, y_i: y_i_batch, y_v: y_v_batch})
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 889, in run
    run_metadata_ptr)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1120, in _run
    feed_dict_tensor, options, run_metadata)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1317, in _do_run
    options, run_metadata)
  File "/Users/jilljenn/code/vae/venv/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1336, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: The node 'Normal.log_prob/sub_1' has inputs from different frames. The input 'model/scan/while/MatMul/Normal.sample/Squeeze' is in frame 'model/scan/while/while_context'. The input 'model/zeros' is in frame ''.

Hi, I need to walk through your code to figure out what happened, but unfortunately I haven't got that much time yet (before the nips ddl). Could you take a look at this script, which corresponds to the example in the white paper.

Short answer: If you change the line joint_ll = log_joint({'x': x, 'y_i': y_i, 'y_v': y_v}) to joint_ll = log_joint({'w': tf.zeros([2 * 128 + 1, 4 * 128]), 'y_v': y_v}), the error will not occur.
Long answer:
In your code,
@zs.reuse('model')
def p_net(observed, seq_len):
    '''
    Encoder: p(x|z) = p(y_v|w)
    '''
    with zs.BayesianNet(observed=observed) as model:
        cell = BayesianLSTMCell(128, forget_bias=0.)
        # shape was [max_seq_len, nb_batches, nb_classes]
        h_list = bayesian_rnn(cell, x, y_i)
        item_features = tf.get_variable("item_features", shape=[nb_items, embedding_size, nb_classes],
                                        initializer=tf.truncated_normal_initializer(stddev=0.02))
        relevant_items = tf.nn.embedding_lookup(item_features, y_i, name="feat_items")
        logits = tf.tensordot(h_list, relevant_items, axes=[[2], [2]])  # That's not even the good shape but anyway
        _ = zs.Categorical('y_v', logits)  # shape of its local_log_prob = [max_seq_len, nb_batches]
                                           # because we already observe the true variable (y_v is in observed)
    return model

def log_joint(observed):
    model = p_net(observed, seq_len)
    # print('all', model._stochastic_tensors)  # w and y_v
    log_pz, log_px_z = model.local_log_prob(['w', 'y_v'])  # Error
    # log_px_z = model.local_log_prob('y_v')
    return log_pz + log_px_z  # Error
    # return log_px_z

joint_ll = log_joint({'x': x, 'y_i': y_i, 'y_v': y_v})

So in the zs.BayesianNet context, the StochasticTensors defined is w (when calling BayesianLSTMCell.__init__) and y_v. The parameter observed for zs.BayesianNet is to give some of these StochasticTensors observed values.
Therefore, the line of joint_ll should be something like joint_ll = log_joint({'w': blabla, 'y_v': y_v}); you need not supply the value of x and y_i since there are no StochasticTensors named x or y_i in the BayesianNet.
Moreover, since you want to compute log_joint of the BayesianNet, both the value of w and y_v should be given (or the value of w would be its samples according to self._w=zs.Normal(...)), to make the following codes reasonable:
def log_joint(observed):
    model = p_net(observed, seq_len)
    log_pz, log_px_z = model.local_log_prob(['w', 'y_v'])  # Error
    return log_pz + log_px_z  # Error

I think the reason why the error happens is: When calculating model.local_log_prob('w'), since when calculating p(w) we need a value of w, if value of w is not given in observed(as in your code), then the value of w will be set as its sample (In your code the value is sampled from zs.Normal('w', w_mean, std=1., group_ndims=2)). However, in your code self._w appears in the __call__ function of the BayesianLSTMCell, so w will be sampled in the loop body of while_loop in tf.scan. It seems that this will lead to the error when calculating model.local_log_prob('w'), but I am not clear about the reason.
I guess in the objective function what you want to optimize, the StochasticTensor should be integrated (taken integration). Then you could try variational inference using evidence lower bound by zs.variational.elbo; Please refer to JiaXin's code (need to change zs.sgvb to zs.variational.elbo and add the dataset loader in his code), or ZhuSuan's tutorial on Bayesian NN.

Thanks a ton!

I haven't got that much time yet (before the nips ddl)

We're all in this!

@csy530216 Can I still ask you questions?
Your approximate of the posterior (the variational function) in both bayesian_rnn.py and Bayesian NN tutorial does not seem to depend on the observed variables. Why is that? Is it normal behavior?

Yes. In VAE, the latent variable z is local (the number of latent variables is proportional to size of dataset). To accelerate the inference we use amortized inference, that is to make the variational distribution of z depend on the value of observed x. Then by learning a inference network, the experience between different data points can be shared.
In principle in VAE we can also make the variational distribution independent of the observed variables like in Bayesian NN, which make the variational family more flexible, but the inference would be much less efficient (maybe there are other advantages and drawbacks).
In Bayesian NN the latent variable W is global (shared between different data points), so the variational distribution need not depend on the observed variables.

Thanks! I guess it means q(W) reflects the posterior over the whole dataset D.
For my purposes, I need to make it depend on the datapoints. I will do my best :) Thanks for such a great library, great docs, and great customer service! 😄

Yes you are right. Thanks for your kind words :)


chore: ignore yarn.lock

Description

added yarn.lock to .gitignore.
the project uses npm (package-lock.json). So better we ignore yarn.lock to avoid someone committing it accidentally.

Notes to reviewers:
Checklist

[x] DCO signed.
[x] Title of the PR starts with area name, e.g. meshery:, mesheryctl:, ui:.

Yarn command wont work with npm engine. No point of adding it to git-ignore henceforth

Thank you, @snitin315 👍


Vscode on Mobile

Is vscode coming on mobile and tablet devices if yes then when? Will it contain terminal too?

Tell pls

https://vscode.dev/

Yes, but is there any plan on Android devices?
And vscode.dev's terminal is not working.
On Tue, 1 Mar, 2022, 9:20 am hello-smile6, @.***> wrote:

https://vscode.dev/
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/144139#issuecomment-1054976741,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXPCVEFZJ73MBX7ZUUUDJ5TU5Q673ANCNFSM5PS3ZCZA
.
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.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Yes, but is there any plan on Android devices? And vscode.dev's terminal is not working.
…
On Tue, 1 Mar, 2022, 9:20 am hello-smile6, @.> wrote: https://vscode.dev/ — Reply to this email directly, view it on GitHub <#144139 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXPCVEFZJ73MBX7ZUUUDJ5TU5Q673ANCNFSM5PS3ZCZA . 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. You are receiving this because you modified the open/close state.Message ID: @.>

Use v86, then.

Duplicate of #126147

vscode.dev can be used on mobiles currently, but terminals aren't yet available there.
/duplicate #135565


Add support for Redis user

Proposed Changes
PR is related to issue https://github.com/vernemq/vernemq/issues/2110
Adding support for Redis "user" allows the use of Redis with ACL to
leverage some security feature such as:

Different user than "default"
Different password
Level of permissions
Key patterns

Types of Changes
What types of changes does your code introduce to this project?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes issue #2110)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (correction or otherwise)
[ ] Cosmetics (whitespace, styles...)
[ ] DevOps (Build scripts, pipelines...)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

[x] I have read the CODE_OF_CONDUCT.md document
[x] All tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if needed)
[x] Any dependent changes have been merged and published in related repositories
[x] I have updated changelog (At the bottom of the release version)
[x] I have squashed all my commits into one before merging

@goldyfruit nice, thanks! could you add a line to the changelog.md?
Also (if you strive for perfection ;)... opening a quick PR against the vmq-docs master branch with a short description of the feature. Probably best in the Redis section of the "Auth with databases" chapter.
Have you made sure that the actual auth queries to Redis work? (i.e that new user would not be underprivileged for that, or anything similar).

@goldyfruit nice, thanks! could you add a line to the changelog.md?

Done

Also (if you strive for perfection ;)... opening a quick PR against the vmq-docs master branch with a short description of the feature. Probably best in the Redis section of the "Auth with databases" chapter.

I will.

Have you made sure that the actual auth queries to Redis work? (i.e that new user would not be underprivileged for that, or anything similar).

All my tests were successful, I set the default Redis user to default (according Redis documentation).

@goldyfruit Merging. Thanks again!

@goldyfruit Merging. Thanks again!

Awesome, thanks!

@mths1 oh, interesting. So Redis 5 does not have that username option?
cc @goldyfruit what is your take on this?

@goldyfruit Thanks for your info. We can fix this inline, I guess, with no need for a legacy option. When a user is not given (let's say 'undefined'), we return different opts in vmq_diversity_redis.


02.25-coroutineParsingDataStreamCustomAllocator1 compile error with Ubuntu-GCC 12.1

The error message is hard to understand.
It seems like type-cast related.
main.cpp:284:1: error: ‘static void promise_type_base<T, G, InitialSuspend>::operator delete(void*, size_t) [with T = std::__cxx11::basic_string<char>; G = generator<std::__cxx11::basic_string<char>, false>; bool InitialSuspend = false]’ called on pointer returned from a mismatched allocation function [-Werror=mismatched-new-delete]   284 | }       | ^ 02.25-coroutineParsingDataStreamCustomAllocator1/main.cpp:284:1: note: returned from ‘static void* promise_type_base<T, G, InitialSuspend>::operator new(size_t, arena&, TheRest&& ...) [with TheRest = {DataStreamReader&}; T = std::__cxx11::basic_string<char>; G = generator<std::__cxx11::basic_string<char>, false>; bool InitialSuspend = false]’ /home/wps/cpp20/coro-study/02.25-coroutineParsingDataStreamCustomAllocator1/main.cpp: In function ‘generator<std::byte> sender(arena&, std::vector<std::byte>)’: 02.25-coroutineParsingDataStreamCustomAllocator1/main.cpp:292:1: error: ‘static void promise_type_base<T, G, InitialSuspend>::operator delete(void*, size_t) [with T = std::byte; G = generator<std::byte>; bool InitialSuspend = true]’ called on pointer returned from a mismatched allocation function [-Werror=mismatched-new-delete]   292 | }       | ^ 02.25-coroutineParsingDataStreamCustomAllocator1/main.cpp:292:1: note: returned from ‘static void* promise_type_base<T, G, InitialSuspend>::operator new(size_t, arena&, TheRest&& ...) [with TheRest = {std::vector<std::byte, std::allocator<std::byte> >&}; T = std::byte; G = generator<std::byte>; bool InitialSuspend = true]’ cc1plus: all warnings being treated as errors

Hello @19317362,
as far as I can see, this is the result of a new warning in GCC mismatched-new-delete. I wasn't able to quickly understand what this warning is complaining about and whether this isn't a false positive.
However, you can disable this warning -Wnomismatched-new-delete to get the code working. I hope this helps.
Andreas


python311Packages.mlflow: 2.11.3 -> 2.12.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.mlflow is: Open source platform for the machine learning lifecycle
meta.homepage for python311Packages.mlflow is: https://github.com/mlflow/mlflow
meta.changelog for python311Packages.mlflow is: https://github.com/mlflow/mlflow/blob/v2.12.1/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.12.1 with grep in /nix/store/7fpv40xh5pqwlbgjhiv3ba267bg2dwjw-python3.11-mlflow-2.12.1
found 2.12.1 in filename of file in /nix/store/7fpv40xh5pqwlbgjhiv3ba267bg2dwjw-python3.11-mlflow-2.12.1

Rebuild report (if merged into master) (click to expand)

20 total rebuild path(s)

20 package rebuild(s)

First fifty rebuilds by attrpath
dbx
mlflow-server
python311Packages.dalle-mini
python311Packages.fastai
python311Packages.k-diffusion
python311Packages.mlflow
python311Packages.mmcv
python311Packages.mmengine
python311Packages.skrl
python311Packages.spacy
python311Packages.spacy-loggers
python311Packages.spacy-lookups-data
python311Packages.spacy-transformers
python311Packages.textacy
python311Packages.textnets
python311Packages.wandb
python312Packages.mlflow
python312Packages.mmcv
python312Packages.mmengine
tts

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7fpv40xh5pqwlbgjhiv3ba267bg2dwjw-python3.11-mlflow-2.12.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.mlflow https://github.com/r-ryantm/nixpkgs/archive/b09e4d3815a6a8ce680dbf641beaeba889f7fa6b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b09e4d3815a6a8ce680dbf641beaeba889f7fa6b#python311Packages.mlflow

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7fpv40xh5pqwlbgjhiv3ba267bg2dwjw-python3.11-mlflow-2.12.1
ls -la /nix/store/7fpv40xh5pqwlbgjhiv3ba267bg2dwjw-python3.11-mlflow-2.12.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages marked as broken and skipped:

tts
tts.dist

6 packages failed to build:

python312Packages.mlflow
python312Packages.mlflow.dist
python312Packages.mmcv
python312Packages.mmcv.dist
python312Packages.mmengine
python312Packages.mmengine.dist

32 packages built:

dbx
dbx.dist
mlflow-server
mlflow-server.dist
python311Packages.dalle-mini
python311Packages.dalle-mini.dist
python311Packages.fastai
python311Packages.fastai.dist
python311Packages.k-diffusion
python311Packages.k-diffusion.dist
python311Packages.mlflow
python311Packages.mlflow.dist
python311Packages.mmcv
python311Packages.mmcv.dist
python311Packages.mmengine
python311Packages.mmengine.dist
python311Packages.skrl
python311Packages.skrl.dist
python311Packages.spacy
python311Packages.spacy-loggers
python311Packages.spacy-loggers.dist
python311Packages.spacy-lookups-data
python311Packages.spacy-lookups-data.dist
python311Packages.spacy-transformers
python311Packages.spacy-transformers.dist
python311Packages.spacy.dist
python311Packages.textacy
python311Packages.textacy.dist
python311Packages.textnets
python311Packages.textnets.dist
python311Packages.wandb
python311Packages.wandb.dist

Maintainer pings
cc @tbenst for testing.

From the release notes:

Addressed a critical Local File Read/Path Traversal vulnerability within the Model Registry, ensuring robust protection against unauthorized access and securing user data integrity.

nixpkgs-review shows no failures on Linux aarch64.
Result of nixpkgs-review pr 304824 run on aarch64-linux 1

14 packages failed to build:

dbx
dbx.dist
python311Packages.mmcv
python311Packages.mmcv.dist
python311Packages.mmengine
python311Packages.mmengine.dist
python311Packages.skrl
python311Packages.skrl.dist
python312Packages.mlflow
python312Packages.mlflow.dist
python312Packages.mmcv
python312Packages.mmcv.dist
python312Packages.mmengine
python312Packages.mmengine.dist

22 packages built:

mlflow-server
mlflow-server.dist
python311Packages.fastai
python311Packages.fastai.dist
python311Packages.k-diffusion
python311Packages.k-diffusion.dist
python311Packages.mlflow
python311Packages.mlflow.dist
python311Packages.spacy
python311Packages.spacy-loggers
python311Packages.spacy-loggers.dist
python311Packages.spacy-lookups-data
python311Packages.spacy-lookups-data.dist
python311Packages.spacy-transformers
python311Packages.spacy-transformers.dist
python311Packages.spacy.dist
python311Packages.textacy
python311Packages.textacy.dist
python311Packages.textnets
python311Packages.textnets.dist
python311Packages.wandb
python311Packages.wandb.dist


Mode keys will run a proc placed in "hold" no matter what the hold time is set to

I wanted to make a key that presses backspace if tapped, and keypad enter if held for a while. This is what I ended up writing:
kbd.define_mode_key :ENTER_DEL, [ :KC_BSPACE, Proc.new { kbd.send_key(:KC_KP_ENTER); puts "Enter" }, 10000, nil]
(the long time and the puts is just for testing)
However, if I keep it pressed, "Enter" appears in the console several times.
Now that I think about it, this might be intended behavior. If it is, I would like to request some way of doing what I want here; a key which does one key if tapped, and another if pressed for a while.

Let me think for a while...


Draft: Feat/workspaces

sorry if this is obvious - but are workspaces analogous to vim sessions? I'd love to be able to manage multiple sessions for a given "project" (where project == a repo). Sometimes I want a session that deals with just groups of files related to the build system, or a particular subcomponent and being able to save/reload sessions (aptly-named) for each of these project sub-topics is really useful. This is something that ctrlspace does really well (https://github.com/vim-ctrlspace/vim-ctrlspace/blob/master/doc/ctrlspace.txt#L630) but I'd love to replace that with a telescope enabled option. FWIW, ctrl-space by default just saves session files into the .git subdir...or other repo metadata dirs for other scms.

@claidler How is it going? Are you still working on this or the Project.
@matu3ba, who opened https://github.com/nvim-telescope/telescope-project.nvim/issues/63 would be interested in picking it up because he needs it for his project (which is based on this project).

Hi @Conni2461  personal circumstances have caused me to take a break from this. I'm intending to come back to it, but would appreciate any help, so very happy for someone to take over whilst I'm unavailable. Thanks

Thats fine. Everybody needs a break from time to time :)
Then if @matu3ba is still interested. I suggest you open a new PR (based on this one) that finishes the implementation. I then can review and merge it :) After that we can talk about having a second maintainer/Collaborator here as a little helper :) because the core telescope team doesnt have the time right now to also maintain extension repos.

Hey @claidler, author of telescope-project-scripts here. I can finish this feature, but I need some answers regarding usability.
From what I understand of the code is that you made any projects being possible to be bundled inside a workspace and I think that is the easiest approach, which goes the least into the way of people and doesnt try to deal with any dependency or path stuff.
(which is good)

How do you intend to filter results by workspace?
Do you want to keep track of the current workspace (if project is part of one)? If yes, where?
Should the project listing shown via require'telescope'.extensions.project.project{} show what projects are part of a workspace? If yes, how?
As I understand it, the file representation is fixed, but user interaction is missing. Am I missing relevant context or questions necessary to understand how the feature should work?

Some other nits are in the issues, but not too relevant to get this finished.

Hi @matu3ba thanks for looking into this. I'll try and answer these best I can, although I'd be very happy for you to come up with your own way of doing this, if you'd prefer, as I didn't get too far into it. I do think this implementation would work quite well though.

How do you intend to filter results by workspace?

You can see every line in the project txt file has a title, path, workspace and activated property, all separated by '='. So an example line (project) in the file would be: myProjectTitle=/home/claidler/projectFiles=w2=1
So that project belongs to workspace 2, as it has w2 in it. So to filter all projects to only show workspace 2 projects, for instance, I'd split the string by the '=' sign, and then get the part specific to the workspace, and then say if it's 'w2', show it.

Do you want to keep track of the current workspace (if project is part of one)? If yes, where?

If you mean keep track of the workspaces the user is currently in, then yes. I was thinking wed have to have a separate file, to keep track of that. Currently there is just the projects txt file, but we'd need one for workspaces also

Should the project listing shown via require'telescope'.extensions.project.project{} show what projects are part of a workspace? If yes, how?

That would be nice. As I said in my answer to the first question, the project would have the workspace number assigned to it via the w2 (workspace 2) part, or w3/4/5, etc, in the project file, so you could just use that.

As I understand it, the file representation is fixed, but user interaction is missing. Am I missing relevant context or questions necessary to understand how the feature should work?

When telescope project is open, it will default to workspace 0 (unless a different default is set via some global nvim config), this will show 'all projects' projects from workspaces 1-9 and any projects that are yet to be assigned to a workspace. When a user adds a project for the first time, the project will be added to w0 (workspace 0), which is the equivalent of unassigned. When the user opens the telescope project window, they can then assign that project to a different workspace via some key command (e.g. ctrl+w) and then input a number to specify the workspace the project should be assigned to. This change the 'w0' part in the text file to be 'w1' or 'w2' or whatever workspace has been set. Now when the user opens the telescope project window they can then switch between workspaces to see a list of projects in the various workspaces.

Some other nits are in the issues, but not too relevant to get this finished.

@claidler Hey, I fixed the test cases and have the basic design idea done.
I am not satisfied with only providing numbers. From my point of view the interface is faster with single letters for setting any specific filter and making everything else working with the fzf algorithm.
My not fully polished vision of the "ultimate project handler":
Column: 1. user name for repo, 2. path to repo, 3. workgroup, 4. active, 5. path_to_worktree

zig=/home/misterspoon/dev/git/zig/zig=0=1=0
zigbare=/home/misterspoon/dev/git/zig/zig=compiler=1=1
zigmaster=/home/misterspoon/dev/git/zig/zig/master=compiler=1=master
Rows:
is a normal repo (default)
is a bare repo
is a worktree with name master

Assumptions for a filter search(1-2), selection of projects(3-4) and general(5-6):
0. Keybindings and popups with interaction are annoying distractions for something frequently used

Any continuous string containing / is an intended path by user
String starting with z zig are intended to be switched to with zoxide and co (but we can show the project preview).
We always do :lcd and want the status line to show clwd. The cwd should be at the top window line and it should be possible to set it to the clwd.
n for name, p for path, w for workspace are good and memorable abbreviations and sufficient.
Additional logic depending on telescope-project imitates the folder structure of the associate git project.
Users want de-duplication of repository names and paths, where the first one is only to be provided from a specified root directory to a specified depth.

Personally I think 4. is missing a vision for git worktrees/bare repositories, which are not yet good supported in neovim but in the work.
Unfortunately they are called worktree, which overlaps with workspace and both are "in git".
From my point of view there must be a notation for "This user repo with name n on path p is git worktree of bare repo with name n on path p", where path may be abbreviated or not (simplicity).
What are your thoughts on the points 0-6 and in special the unfortunate naming coincedence of "worktree" and "workspace"? How could workspace be renamed?


What is $$ >> (context)

Hi, I just saw your interesting projects, and found $$ >> (context) and > syntax, can you please explain what are thet?

I'm using a custom RX implementation with flutter_hooks to remove a lot of boilerplate code. $, $$, $$$ are helpers related to flutter_hooks.
but in a nutshell:
/// Creates a new HookWidget (same as using a HookBuilder)
$$ >> (context) {
...
}

/// Subscribes and automatically disposes a wave (you can think of a wave as an Observable or a Stream)
$(() => ...);

/// Subscribes and automatically disposes a bloc.
$$$(() => ...);

The second part is a little hard to explain.
Imagine you had to do math like this:
+(
  value:2
  child: +(
    child: + ()...

you can think of the & as a plus sign that combines widgets that accept a single child (I call them Applicators)
Because Applicators themselves are not widgets and will always need a child to become a Widget (remember, every widget tree has a last widget e.g. Text or a Container without a child) they need a last stage where they receive a real widget. that's what > is for.
I'm also using this concept for lists and other types because dart is a little limiting in that regard
bgColor(...) & height(..) > onListView() >> []
The operators have been chosen in a way that you usually don't need any parentheses like in (3+2*2 = 7 and not 10)
This opens up a whole new world of possibilities.
you can apply applicators to each element of a list
padding(all: 4.0) * []
you can hide applicators
padding(all: 4.0).when(false)
...
dartfmt doesn't play well with that way of writing widgets so I recommend you to use the IntelliJ formatting.
There's really a lot more to explain but I hope this gives you a starting point.

thanks, I like your solution, it's amazing 👍

@modulovalue is there any tools to easily create dart package like bird_flutter?

@modulovalue is there any tools to easily create dart package like bird_flutter?

What tools do you need? I might not be understanding your question correctly, could you elaborate?

I found it, source_gen

I wrote the code by hand but I guess source_gen could be used too for some parts

Good thanks, it's someting new for me


license?

I can't seem to find a license file for this repo.
I'd love to incorporate some of these sklearn estimators into https://github.com/AllenInstitute/neuroglia, so if you have room to select a license, adding BSD3 compatible license (or a direct contribution) would be very helpful.

Great! I just added the license file.


Visual Studio Build Tools no installation

Hello. I was installing all the tools required for node-gyp in Windows with the command: npm install --global windows-build-tools. 1 minute later, it log me that I can't install Visual Studio Build Tools and that I should restart. Can someone help me, please?

https://github.com/felixrieseberg/windows-build-tools is the repo you want to post this to.

Thanks


Drop duplicate docs requirements

What does this PR do?
The same shall be already in requirements/docs.txt
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

turned to be important fix as the duplicate file brings doc dependencies to main repo

What was the issue that @williamFalcon faced?

What was the issue that @williamFalcon faced?

Some missing dependencies... but don't know the details: #14638


gnome3.webkitgtk: 2.20.5 -> 2.22.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/webkitgtk/versions.
meta.description for gnome3.webkitgtk is: '"Web content rendering engine, GTK+ port"'.

Checks done (click to expand)

built on NixOS
/nix/store/jcl8a9ivnim05h25ggfxy9ham9wl9nja-webkitgtk-2.22.2/bin/WebKitWebDriver passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.22.2 with grep in /nix/store/jcl8a9ivnim05h25ggfxy9ham9wl9nja-webkitgtk-2.22.2
directory tree listing: https://gist.github.com/dc1fc23e8d737f509cc32d37113f44ca
du listing: https://gist.github.com/b5b6068364f006a4dfb550c8c3fcb9c5

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:

Install cachix from https://cachix.org/
Use r-ryantm's cache:cachix use r-ryantm

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/9df237fdb0f97148af2b05390bbb2231ac35daeb.tar.gz -p gnome3.webkitgtk
ls -la /nix/store/jcl8a9ivnim05h25ggfxy9ham9wl9nja-webkitgtk-2.22.2

This is part of #45950


v3: Sync Client to OpenAPI Spec, Bump Ruby Version

A few big changes in this PR:

Update the client to be in line with the API's open_api spec.
Use v7 of the OpenAPI Client Generator
Bump the gem's ruby version to 3.3.1, since 2.7 has been end-of-life since last March.

This brings about a few updates to the client, like returning a flag name and the ability to update payees and categories. See the changelog for more information.
With this in mind, I decided to go ahead and bump the library to a major breaking change of 3.0.0, since getting the client in sync with the open_api spec required it to remove some previously deprecated schemas.

:shipit:

Tests running with these changes on main branch: https://github.com/ynab/ynab-sdk-ruby/actions/runs/9212146210


[SPARKR-241] Update R to fail early if SparkR package is missing

R should stop if SparkR is missing.
There is this one case in Spark/R with shell.R.
Please see https://github.com/amplab-extras/SparkR-pkg/pull/233

Thanks @felixcheung for opening the PR here as well. Merging this.


[BUG] Register schema doesn't seem to work

From here
https://docs.microsoft.com/en-us/java/api/overview/azure/data-schemaregistry-readme?view=azure-java-stable#register-a-schema
I copy the box with the "copy" button:

And I get this:

Exception in thread "main" com.azure.data.schemaregistry.implementation.models.ErrorException: Status code 400, "{"Code":400,"Detail":"Schema validation failed: Invalid character after parsing property name. Expected ':' but got: ". Path '', line 1, position 6. TrackingId:be527e06-f644-48b3-8451-652db65cdc33_G19, SystemTracker:lmazuel-bugbash-sr.servicebus.windows.net:$schemaGroups/lmazuel/schemas/lmazuelschema, Timestamp:2021-12-07T19:28:15"}"

I didn't made any attempt to set any env variables for auth at this point (mentionning just in case this is a side effect of some auth issue). It's by the way interesting it doesn't yell at me for auth trouble.

Follow-up: I did a replace on VSCode of \n by no character, and it now all works.

Registered schema: dab2b21cf1f24109a39463380b906c44

So I guess I have some auth I didn't remember :p


Add quiet mode (-q) and command descriptions

I think a quiet option could make sense. However, I was thinking of moving away from print statements to logging. To make logging quiet, it would only require reconfiguring the loggers.
import logging
import sys

root = logging.getLogger()
root.setLevel(logging.DEBUG)

handler = logging.StreamHandler(sys.stdout)
handler.setLevel(logging.DEBUG)
formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s')
handler.setFormatter(formatter)
root.addHandler(handler)

branch has conflicts now


Animation tools fix

Fixes to make_html and make_rst to properly load html text.
Added animation_tools_demo.ipynb for testing everything.

This is great; I very much like the manual option for slower interacts and we should incorporate that into some of the widgets in the book.
I guess that a lot of the text in the notebook can also be incorporated as docstrings for the functions.  I sent you a PR with this.
Now if only we could figure out how to avoid rasterizing complicated plots when making jsanimations.
By the way, the notebook says "JSAnimation package from ?".  I'm not sure what is supposed to go in place of the "?".


no_std feature is backwards: a use_std feature should be used, which is part of the default features

Cargo features are supposed to be additive, which means the current no_std feature is backwards. This is an issue if you're writing a library, because there is currently no way to pass a negative switch (e.g. if I have a use_std flag, there is no way to say 'enable the no_std flag if it's not enabled.
The current system should be switched, so that there is a use_std feature, which is enabled in the default features.

Yeah. I learned this a few weeks ago.
When I added the feature I saw other crates do it that way, but thought no_std was easier to use.
I wish cargo had a more descriptive way of disabling features than default-features=false / --no-default-features.

Fixed by https://github.com/tomprogrammer/rust-ascii/commit/0cf9d8b19bfb58c84ae9a336adfd056e2512a69d.

I'll leave the issue open until I release the new version containing this commit today.

@tomprogrammer you still haven't released a new version. please make it 0.8 or something.

I've released version 0.8.0 with all pending changes listed in RELEASES.md.


unique_together check design on Cert model is flawed

In some cases it may happen that by using the app normally the unique_together check will fail.
We should avoid this, will try to collect more information on how to reproduce the issue.

Any updates on this? Is this still an issue?

@dimrozakis I couldn't reproduce this issue anymore but I remember clearly one time it happened so I left the issue open just in case somebody else incurs in it.
Did you experience the same problem? If yes can you reproduce it?

Hey @nemesisdesign

Did you experience the same problem? If yes can you reproduce it?

No, I haven't experienced the issue. I'm considering using this django app, and looked at the issue tracker to check for any known issues, and this seemed troubling, so I thought to ask.

@dimrozakis it hasn't happened anymore since that time and it only happened in my development environment. I might have caused some mess while developing. I will close this since I cannot reproduce it.


Prompt before the initial clone of fips in the fips template.

My first encounter with fips was having it clone a repo and drop a bunch of folders in a directory I cared about when I was trying to follow the build steps of an unfamiliar project.
This was a bit surprising, and I would have appreciated a confirmation prompt at the start of all of it, even if it wasn't that bad to rectify.
Maybe this will help some future users will avoid such issues. Or even myself from accidentally doing the same thing again.
Sorry in advance, I'm not good at python. I made an attempt to stick to your style (well, I put spaces before the : anyway), but might have messed up.

Hi, I agree that this is a problem, and generally like the idea of a prompt, and you also thought about hinting automated build systems with the environment variable, but:

all changes to the fips template file are problematic, because this is 'decentralized' and copied into each project, for this reason it should remain as small and simple as possible
...which would mean: the prompt should move into the fips project itself before dependencies are pulled (so the fips project would be pulled first and this would "pollute" the directory, but I think that's ok, it's the (potentially) dozens of dependencies which are the problem)
I wonder if there's a better way to detect whether a confirmation should happen or not than via an environment variable...

But anyway... I'm hesitant merging this PR also because of another thing that's been rolling around in my head for a long time, but never got around to actually do it:
I'm thinking about changing fips' default behaviour so that everything is written into a subdirectory of the project (for instance ".fips-build"), so that it doesn't pollute the directory level above that project. The current behaviour would become a special "shared depdencies mode" which would need to be enabled per project (for instance through a new ".fips-settings" flag). That way a warning/confirmation wouldn't be needed, because by default only this local subdirectory would be written to.

I wonder if there's a better way to detect whether a confirmation should happen or not than via an environment variable...

I considered:

listing the parent directory and seeing what it had in it (although I wasn't exactly sure what the check would be -- certainly if this is the only item it's probably fine, or if the parent dir is something like fips-workspace, but these kind of heuristics are finnickey)
checking istty on stdout (although IDK if this works on windows)

But even then, I think for use cases like CI or other automation, you'd still want to be able to disable that kind of thing absolutely.

all changes to the fips template file are problematic, because this is 'decentralized' and copied into each project, for this reason it should remain as small and simple as possible

I could imagine eventually fips evolving support for updating the fips template, e.g. as part of a fips update fips or something. You could even be intelligent and only overwrite it if it hasn't changed (easy enough to check with git, even though they're in different repos, or fips could keep a list of all past template/fip's file shas and compute the current).
That said this isn't exactly critical functionality that people can't live without -- it's nice if new projects can get it, but it's not like not updating it breaks backwards compat or anything.

I'm thinking about changing fips' default behaviour so that everything is written into a subdirectory of the project (for instance ".fips-build"), so that it doesn't pollute the directory level above that project

This would be wonderful. The pollution of the parent dir is really annoying and surprising for new users (it and the use of submodules are my two least favorite things about fips).

I could imagine eventually fips evolving support for updating the fips template, e.g. as part of a fips update fips or something.

That's a good idea!


Update MD file on new branch 2017-19-14_07-11-04

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fixed path separator in built BiblioSpec libraries

I was surprised this didn't trigger needing to record new reference checks for everything, but I see we always trim the path to the BiblioSpec root. Otherwise tests would fail between Linux/Windows or just a different source tree location. That actually brings up the point that in rare cases, a BiblioSpec library may have been created on Linux, so its path will use forward slashes with / as the root. I suppose that's not a common enough case to worry about though, eh @brendanx67 ?

I don’t have a problem with that case, nor where the user used full network
paths on Windows and has paths like:
\server\share\path\to\file.mgf
I was only objecting to the mixed path separators obviously created by
BlibBuild and not something a user would otherwise ever expect to see.
On Tue, Aug 23, 2022 at 7:22 AM Matt Chambers @.***>
wrote:

I was surprised this didn't trigger needing to record new reference checks
for everything, but I see we always trim the path to the BiblioSpec root.
Otherwise tests would fail between Linux/Windows or just a different source
tree location. That actually brings up the point that in rare cases, a
BiblioSpec library may have been created on Linux, so its path will use
forward slashes with / as the root. I suppose that's not a common enough
case to worry about though, eh @brendanx67 https://github.com/brendanx67
?
—
Reply to this email directly, view it on GitHub
https://github.com/ProteoWizard/pwiz/pull/2236#issuecomment-1224147985,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYBWUCVLA5CCUO2HV65O6DV2TNBFANCNFSM57IZMNNQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Dynamic forms - add ability to set autocomplete attribute to form element

Feature Request

Support adding autocomplete attribute to dynamic form elements

this component is deprecated and no longer maintained please use regular angular forms


Blockchain blocks endpoint

we should have an API endpoint for related block information (e.g., payload/signatures).

with a reference between Sidetree transactions.
with a relationship to /blockchain/time.
with a mechanism to validate based on the blockchain config at that time (#220).

Note: this blocks API is for providing transparency of the underlying fabric blockchain channel. (hence why the Sidetree spec would be silent on it.)
It could make sense to make it clear what part of the response is from “fabric”, or perhaps incorporate “fabric” as part of the endpoint path...
Endpoint could be similar to: /blockchain/fabric/blocks and/or /blockchain/blocks.

Should supply both a friendly view (JSON) and also a raw view where signatures can be validated.


[Suggestion] Only Show Items that are Nearby

Thank you for fixing the Sinytra Compat!
I'm just here with a suggestion. Can you make it so that the items that show up on the list are only items that are in nearby inventories? It gets a bit overwhelming to see all items at once and needed to search through it all the time.
IDK if that's a feature you already added but in forge it shows all the items in the game, not just whats nearby.
Thank you!

Well it's funny that you say that, because that feature is high on my list of plans and I am currently looking into the best approach to do it! It may need some work but i hope to implement it very soon!


What happens to Routine when it has finished?

Just wondering what happens to a routine that is invoked within an ants pool after it finishes ?
Let say i set up an ants pool of size 10, and I've invoked 10 routines, so there should be 10 routines running within the pool.
If 1 routine has finished, is it now 9 routines running? Or are we still left with 10 routine but with 1 inactive ?
I've setup my application to handle PubSub messages concurrently with each message handled by a function invoked in a worker pool (so 10 messages = 10 Message handler in ants pool). However I want to make sure that the ant pool frees up resources when 1 of the handler finishes.

My understanding from the docs is that, I need to set ants.WithExpiryDuration() to make sure that those finished routines are cleared out?

My understanding from the docs is that, I need to set ants.WithExpiryDuration() to make sure that those finished routines are cleared out?

Yes, let's say you call WithExpiryDuration(500ms), then ants will check and find all those idle workers that haven't processed tasks in 500ms periodically (every 500ms).

@panjf2000  thank you!


Fixed colours in windows 10 cmd terminal

Before

After

Does it have any impact on other terminals(unix)?

Does it have any impact on other terminals(unix)?

I'll try it out on Ubuntu.

Did it have any effects?

Did it have any effects?

Sorry for the long wait. It still works correctly on Ubuntu but as you might see on the first line you get sh: 1: color: not found, so I guess I'll just need to add an os check for windows before running os.system('color FF') to get rid of that.

Thanks a lot, this will be merged and the os check will be implemented in the next commit


Compiler unable to determine Lifetime of local static mut in 0.6.0-alpha.5

I'm upgrading from 0.6.0-alpha.2 to 0.6.0-alpha.5.  The last bit i'm struggling with is one of my former static mut resources, which is now a local resource.
Whenever I try to use the technique suggested in the migration docs (see: no static mut transform), I get a compiler error that says `lifetime 'static required'
taken from: https://github.com/LongLiveCHIEF/led-backlighting-controller/blob/b718a3af2c510bfc8706e211e1cc812a95a50a1a/src/main.rs#L123-L148
    #[task(shared = [modeDetectPin], local = [
        hold: Option<hold::SpawnHandle> = None,
        pressed_at: Option<Instant<RtcMonotonic>> = None
    ])]
    fn debounce(mut cx: debounce::Context){
        let HOLD: &'static mut Option<hold::SpawnHandle> = cx.local.hold;
        let PRESSED_AT: &'static mut Option<Instant<RtcMonotonic>> = cx.local.pressed_at;
        if let Some(handle) = HOLD.take() {
            handle.cancel().ok();
        }

Compiling results in the following error:
error[E0621]: explicit lifetime required in the type of `cx`
   --> src/main.rs:128:60
    |
128 |         let HOLD: &'static mut Option<hold::SpawnHandle> = cx.local.hold;
    |                                                            ^^^^^^^^^^^^^ lifetime `'static` required

error: aborting due to previous error

If I try to specify the lifetime of cx: debounce::Context, i get a compiler error: unexpected lifetime 'static in pattern.
Rust version:  rustc 1.54.0 (a178d0322 2021-07-26)

Getting rid of type and lifetime annotations for the HOLD and PRESSED_AT vars allows the project to compile, and it works as expected. Just as an FYI.  It's not a solution I'm happy with, but one that'll work in the short term.

I missed the weekly meetup this week, but saw you guys asked if I was around.  For my part, my only real concern about this is that the docs aren't discontiguous around the need to explicitly specify lifetime for these, so that we're friendlier to beginners to Rust.
I was just certain I was doing something wrong and just removed the annotations for lifetimes as a last ditch effort to see if the compiler could figure out what it was I wanted to do.

Hi, as we discussed this is expected behavior - there is no need to specify lifetimes when using locals.
If you have any other issue, feel free to ping!


Build: npm install fails with peer invalid error for typescript

Hello,
I'm trying to build the repository, but npm install fails with the following :
npm ERR! node v4.2.6
npm ERR! npm  v2.14.12
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants typescript@*
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
Thanks in advance for any help :)

thanks, I reverted to ts beta


Incorrect axes labels for ellipses in ArcGIS Pro 2.4

Current Behavior
This bug was discovered while doing Certification Testing for the Distance and Direction add in for ArcGIS Pro 2.4.
Repro steps:

Install ArcGIS Pro 2.4 + Distance and Direction Addin <IP_ADDRESS>
Using the Distance and Direction Tool to create an ellipse (either by using the map point tool or manually entering the values)
Select Semi for the Ellipse Type drop-down box

a) Optional: Enter 3000 for the Major Axis box and 1500 for the Minor Axis box and 30 for Angle (though any angle will do because the angle label works correctly).

Ellipsoid is created. The core measure tool is set to Geodesic and used to confirm the issue.

b) Selecting Full:

Note: The labels being displayed for this feature show semi major and minor axis values instead of full major and minor axis values
Expected Behavior
The labels displayed when an ellipsoid is created should reflect major and minor axis values. The core measure tool set to Geodesic is used to confirm results.

Additional Notes:
•   Observed in ArcGIS Pro 2.3 with released version of MT/DD
•   Did not observe on ArcMap 10.7.1

Addressed in PR #664 - should behave the same in Pro and ArcMap now (i.e. the label shown is the "full" axes values)
Pro and ArcMap for same values used for both "full"(left) and "semi"(right) inputs:
Pro:

ArcMap:

@ljuru @csmoore Was this just on Pro 2.4 and introduced new at MT 3.5? or was this an issue in previous versions of Pro/MT?

@lfunkhouser I noticed the issue was in Pro 2.3 as well.

I should have mentioned in my comments - it looked like this issue may have been present since we switched the graphics to features (June, 2018)

Doc work:

[ ] Update What's new page

[ ] MT section
[ ] Distance and Direction section

Update DD homepage
Update DD Resources
Update MT Resources
Publish DD Resources tab
Publish MT Resources tab
Publish DD pdf
Publish MT Release notes (pdf)

https://solutionsdev.arcgis.com/defense/help/military-tools/resources/june-2019-military-tools-for-arcgis.htm

removed G-qc verify because i forgot to do it when i made this comment

Doc PR is still open

PR has been approved and merged.

Verified doc updates on solutionsdev for MT and DD and PDFs for MT (dev build <IP_ADDRESS>8) and DD (dev build (88).


Error code: 401 - {'error': {'code': 'PermissionDenied', 'message': 'Principal does not have access to API/Operation.'}}

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [x ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Update a previous version of the webapp with new code deployed via VS Code.
Local deployment works perfectly.
Any log messages given by the failure

2024-07-29T16:41:07.903585431Z ERROR:root:Error code: 401 - {'error': {'code': 'PermissionDenied', 'message': 'Principal does not have access to API/Operation.'}}
2024-07-29T16:41:07.903619832Z Traceback (most recent call last):
2024-07-29T16:41:07.903625032Z   File "/tmp/8dcacc2ffe1ab39/app.py", line 358, in conversation_internal
2024-07-29T16:41:07.903628532Z     result = await stream_chat_request(request_body, request_headers)
2024-07-29T16:41:07.903631632Z              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-29T16:41:07.903634832Z   File "/tmp/8dcacc2ffe1ab39/app.py", line 345, in stream_chat_request
2024-07-29T16:41:07.903638632Z     response, apim_request_id = await send_chat_request(request_body, request_headers)
2024-07-29T16:41:07.903641932Z                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-29T16:41:07.903644932Z   File "/tmp/8dcacc2ffe1ab39/app.py", line 323, in send_chat_request
2024-07-29T16:41:07.903648232Z     raise e
2024-07-29T16:41:07.903651632Z   File "/tmp/8dcacc2ffe1ab39/app.py", line 318, in send_chat_request
2024-07-29T16:41:07.903663132Z     raw_response = await azure_openai_client.chat.completions.with_raw_response.create(**model_args)
2024-07-29T16:41:07.903666632Z                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-29T16:41:07.903669832Z   File "/tmp/8dcacc2ffe1ab39/antenv/lib/python3.11/site-packages/openai/_response.py", line 262, in wrapped
2024-07-29T16:41:07.903673132Z     return cast(APIResponse[R], await func(*args, **kwargs))
2024-07-29T16:41:07.903676432Z                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-29T16:41:07.903679632Z   File "/tmp/8dcacc2ffe1ab39/antenv/lib/python3.11/site-packages/openai/resources/chat/completions.py", line 1295, in create
2024-07-29T16:41:07.903683332Z     return await self._post(
2024-07-29T16:41:07.903686432Z            ^^^^^^^^^^^^^^^^^
2024-07-29T16:41:07.903689632Z   File "/tmp/8dcacc2ffe1ab39/antenv/lib/python3.11/site-packages/openai/_base_client.py", line 1536, in post
2024-07-29T16:41:07.903692832Z     return await self.request(cast_to, opts, stream=stream, stream_cls=stream_cls)
2024-07-29T16:41:07.903706933Z            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-29T16:41:07.903710433Z   File "/tmp/8dcacc2ffe1ab39/antenv/lib/python3.11/site-packages/openai/_base_client.py", line 1315, in request
2024-07-29T16:41:07.903713533Z     return await self._request(
2024-07-29T16:41:07.903716533Z            ^^^^^^^^^^^^^^^^^^^^
2024-07-29T16:41:07.903719533Z   File "/tmp/8dcacc2ffe1ab39/antenv/lib/python3.11/site-packages/openai/_base_client.py", line 1392, in _request
2024-07-29T16:41:07.903722633Z     raise self._make_status_error_from_response(err.response) from None
2024-07-29T16:41:07.903727133Z openai.AuthenticationError: Error code: 401 - {'error': {'code': 'PermissionDenied', 'message': 'Principal does not have access to API/Operation.'}}
Expected/desired behavior

It should display reply to my query.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Linux

azd version?

run azd version and copy paste here.

Versions

azd version 1.2.0 (commit 99ea7577f0df0df2ba34b677da189fafba18c0f7)

Mention any other details that might be useful
I deployed the WebApp in October last year. It was working perfectly. I updated the code from the latest git repo and deployed the app from the commands given in the git repo. Now it is showing the error. However, when I do a local deployment, it works as expected.

Thanks! We'll be in touch soon.

@pamelafox AZURE_OPENAI_API_KEY was blank. I copied the KEY and now its working! Was it supposed to be blank?

@pamelafox AZURE_OPENAI_API_KEY was empty. I copied the actual key and now its working!
Was it supposed to be empty?

I had the same issue, where AZURE_OPENAI_API_KEY was empty. Filling it in the Environment Variables for the App Service resource in the Azure Portal fixed it

BUT every time that I re-deploy the app or deploy a new app, the AZURE_OPENAI_API_KEY gets wiped out blank and the issue returns, requiring this manual step.
@pamelafox is there a fix for that?

I experience the same, but in my case AZURE_OPENAI_API_KEY isn't even set, and I need to create it after every deployment.

From my talk with Azure support, the env variables from .env file do not get updated, the existing variables in the Azure portal gets priority. So, it makes sense to set the environment variables each time after redeploying. Hope they make the update.

To resolve this problem, I create in App Service -> Environment Variables: AZURE_OPENAI_API_KEY and put the KEY 1 from OpenAI Resource. This worked for me.


Holder of drop page iteration

One item was used for a claim Chroma Lattice, and the second was not; they can not claim drop where it is required holderOf .motherboard as the current code uses the first one, which is claimed already for user.

was not a good design from me, lets fix it a bit. Better version hopefully coming with v2 drop page UI

its clear when you hold more than 1 nft

Design

updated in figma https://www.figma.com/file/JXNtryaNYhY0XJNArzvPQx/Handoff?type=design&node-id=394-6126&mode=design&t=FmXDMzEHIN8lTS0n-11

list of requirements, check or cross next to them

other possible states

with the one failed, it shows the same as with 2 fails - requirements not met

available for mint

this shows how much nfts from the collection you can still use to mint the drop

there is also a tooltip:

Mobile
just stacking things on top

thanks! lmk if anything 🚀

we can test on chroma drop

anyone 👀

👋


python 3.13 and django 5

You probably want to contribute this to original repo: https://github.com/georgemarshall/django-cryptography which hopefully will encourage the author to merge and finally do a release :(


Update .rubocop.yml

Disable Style/Documentation cops

Im a little confused. Shouldn't that have been covered by the Shopify cops we added?

You're right, all cops are disabled by default in Shopify's Ruby style guide and this particular cop is never explicitly enabled... not sure what's going on there.

Yeah, forget this. Looks like we just need to rebase our branches to pull in the Rubocop config.


Use protobuf encoding for core K8s APIs in Prometheus Engine

For core K8s API objects like Pods, Nodes, etc., we can use protobuf encoding which, compared to the default JSON encoding, reduces CPU consumption related to (de)serialization, reduces overall latency of the API calls, reduces memory footprint and the work performed by the GC and results in quicker propagation of objects to event handlers of shared informers.
Core system components of K8s default their serialization method to protobuf for 8 years already: https://github.com/kubernetes/kubernetes/pull/25738.
Some benchmarks comparing JSON vs. protobuf showcasing how the latter data format (de)serializes faster and uses less memory:

https://medium.com/@akresling/go-benchmark-json-v-protobuf-4ec3c62ec8d4
https://www.codingexplorations.com/blog/performance-comparison-protobuf-marshaling-vs-json-marshaling-in-go
https://medium.com/@david_turner/protocol-buffers-just-how-fast-are-they-9ec19ea580db

Is there a case where potential non-GKE k8s would ONLY support JSON and this will fail or client is able to fallback?

Only in K8s older than 1.3 in which protobuf support was added. It's embedded in the server and can't be turned off.

Thanks!