The docs need to be made for 20.04

On this page https://docs.microsoft.com/en-us/dotnet/core/install/linux-package-manager-ubuntu-1910
It's only mention the 19.10, There has to be a page for 20.04.
If you replace the 19.10 with 20.04 the path will still not work.
[Edit by gewarren to add doc details.]

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

ID: b5cbe58d-ad05-60fd-47d7-0d9ccfeecde4
Version Independent ID: c9773e9b-dbc1-cb7b-b303-287cf8bd354c
Content: Install .NET Core on Ubuntu 19.10 package manager - .NET Core
Content Source: docs/core/install/linux-package-manager-ubuntu-1910.md
Product: dotnet-core
GitHub Login: @Thraka
Microsoft Alias: adegeo

Ping @rbhanda what is the story with 20.04?

Ping @rbhanda what is the story with 20.04?

As per the last update, this should get updated by 23rd April 2020.

Thanks! I'll add it to our milestone

https://github.com/dotnet/core/issues/4360
phillip-haydon commented 19 minutes ago
I used the 18.04 source on 20.04 with the help from this tweet:
https://twitter.com/sinclairinat0r/status/1237201767198273536
wget http://mirrors.edge.kernel.org/ubuntu/pool/main/i/icu/libicu63_63.2-2_amd64.deb
sudo dpkg -i libicu63_63.2-2_amd64.deb
Then installed .NET Core normally.

Well, it's 29th april and still not update. Is there that much of a difference between 19.04 and 20.04?

Just as an FYI, if you download the tar ball yourself and follow the instructions on how to install it manually (which is really easy anyways and most Linux/UNIX geeks like me prefer it this way sometimes for more control), you don't have to worry about the mirrors, etc.
What I do is extract the tar ball into a folder in my home folder, naming it to the version of the SDK (in case I want to flip back and forth between 2 and 3 possibly). I then create a link in my home folder to point to the current version I want to use (such as ln -s ../dotnet3.1 ./dotnet).
I then update .bashrc to fix my path as such:
export $DOTNET_ROOT=$HOME/dotnet
export PATH=$PATH:$DOTNET_ROOT
Then, if I want to switch between versions, I just update the soft link so that the ./dotnet link points to whatever version of the SDK I want to use.
Same goes for VIssual Studio Coee. I just download the tar ball, install it into $HOME/code, update my path to so that $HOME/code is in it and I can launch code from any folder at the command line.
Of course, I can't add the Code launcher to my dock without doing the machinations of create the desktop files, etc. But it works.

@iBolski I can see that I have posted 20.04 link was initially 404. Now it's pointing to a file. I hope everything will work as expected.

dotnet/core#4360
phillip-haydon commented 19 minutes ago
I used the 18.04 source on 20.04 with the help from this tweet:
https://twitter.com/sinclairinat0r/status/1237201767198273536
wget http://mirrors.edge.kernel.org/ubuntu/pool/main/i/icu/libicu63_63.2-2_amd64.deb
sudo dpkg -i libicu63_63.2-2_amd64.deb
Then installed .NET Core normally.

I did this, but the dotnet packages still weren't there.

Seems the repo is here but not the package
$ docker run --rm -it ubuntu:20.04
[docker]$  apt update -y
[docker]$  apt install -y wget
[docker]$  wget https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
[docker]$  dpkg -i packages-microsoft-prod.deb
[docker]$  apt update -y
[docker]$  apt search dotnet-sdk
Sorting... Done
Full Text Search... Done

Still can not install on Ubuntu 20.04 😰

The Ubuntu update will be available on 5/12

with a ref it's better: https://github.com/dotnet/core/issues/4360#issuecomment-623521485

@rbhanda any reference where this date came from?

Waiting ...

Waiting on 20.04 too! So excited! 😃

i have tried 19.10 on ubuntu 20.04 and no luck. its 5/12 and still no update =..(

@dmedina0217 please take a look at dotnet/core#4360 once this blocking task is done then the doc should follow IMHO...

@Mizux thank you for the reply and i hope that fix is what gets the release pushed out

Finally, I can install dotnet-sdk from ubuntu 20.04 the repo!

yeah it worked

oh yeah it works!
since the above isnt updated, and anyone is interested, all you would have to do is copy below and you'll be good.
wget https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
sudo apt-get update
sudo apt-get install apt-transport-https
sudo apt-get update
sudo apt-get install dotnet-sdk-3.1
sudo apt-get update
sudo apt-get install apt-transport-https
sudo apt-get update
sudo apt-get install aspnetcore-runtime-3.1
sudo apt-get update
sudo apt-get install apt-transport-https
sudo apt-get update
sudo apt-get install dotnet-runtime-3.1


Parcel is wrongly defined

When creating a shipment, go-shippo defines parcel as a string, yet within the documentation, a parcel is defined as parcels of type []string. Because of this, when I create a shipment object, I receive:

Error returned from API: [400] {"parcels": ["This field is required."]}

Seems that the wrapper has not been updated to account for these changes.


Add beat and utc to time_date sensor

This PR adds UTC as option to display and for the geeks 'beat' (Swatch Internet Time). Also I renamed a couple of variables to differ for the 'systemmonitor' sensor which was the source in the first place.

Coverage remained the same at 75.51% when pulling 584d3ea272c083e4462053adf5836bb72b7e82eb on fabaff:beat into 52f5c45ca841ea9b40d0da540bd3e8fae5c8a8ed on balloob:dev.


Roblox Not Opening

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
Roblox Doesn't Open After Deleting Bloxstrap and Installing Normal Roblox Roblox Doesn't Open Because of Bloxstrap Please How Can I Solve It?

You've just said yo uninstalled Bloxstrap. If you have it uninstalled, how would Roblox be unable to open because of it?

Roblox Doesn't Open Even If I Delete Bloxstrap And Even If I Install Bloxstrap, Roblox Doesn't Open

then i won't be able to play roblox anymore

Thank you very much for telling me that there is a problem with Roblox. As a result of my efforts, I can play Roblox and now I will download Bloxstrap.


Update raycast-ollama extension

Description

Command 'Manage Models': Support for multiple configured Ollama Server, manage and use models from different server.
Command 'Custom Command': changed prompt format to the Raycast Prompt Explorer one. More details on supported tag on the README.md. WARNING: This change combined with allowing multiple Ollama server feature break all configured custom command so all custom commands need to be reconfigured.
Command 'Summarize Website': New command that summarize the content of the current web browser tab. For this feature Raycast Browser Extentision is required.
Command 'Chat with Ollama': Improved UI, combine models from different Ollama Server and use browser content on prompt with Raycast Browser Extentision.
Added support for keep_alive, you can now chose how many minutes the model must stay on memory.

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

It looks like there is a lot of errors inocmming since this version was released, do you mind checking the issue page for the extension
Feel free to find me on our Slack community if you have any questions 🙂


Skipping parts of search space?

Hi,
There are some parts of search space where my model will fail to return a usable result, and this triggers a BoundError at the prediction step. The parts of search space where this will occur is not clearly defined (and is probabilistic), so clean! is not applicable. I am wondering how I may wrap the tuning with a try-catch so that certain errors are simply returned as an infinite loss, rather than breaking the entire tuning and exiting?
Thanks!
Miles

I guess it might be cleaner to just have the model not throw an error, but just return an uninitialized array in case of error?

Hi,
There are some parts of search space where my model will fail to return a usable result, and this triggers a BoundError at the prediction step. The parts of search space where this will occur is not clearly defined (and is probabilistic), so clean! is not applicable. I am wondering how I may wrap the tuning with a try-catch so that certain errors are simply returned as an infinite loss, rather than breaking the entire tuning and exiting?
Thanks! Miles

Can you give an example code snippet.

I guess it might be cleaner to just have the model not throw an error, but just return an uninitialized array in case of error?

Yeah. You should be able to handle all that during the call to fit.

Thanks for the quick response!
After thinking about it more, I may just have the predict step return an uninitialized array in case of incorrect fits, as it seems something unique to SRRegressor (in case the search can't find a valid expression, for example).


Kargo CLI should allow setting promotionpolicies when creating a Project

Checklist

[x] I've searched the issue queue to verify this is not a duplicate feature request.
[x] I've pasted the output of kargo version, if applicable.
[x] I've pasted logs, if applicable.

Proposed Feature
I am able to create a project with kargo create project kargo-demo ...however  I still need to provide further configuration to get other settings.
Example being promotionPolices
apiVersion: kargo.akuity.io/v1alpha1
kind: Project
metadata:
  name: kargo-demo
spec:
  promotionPolicies:
  - stage: dev
    autoPromotionEnabled: true
  - stage: uat
    autoPromotionEnabled: true

Although declarative configuration is the preferred method, it would still be nice to be able to be able to do it imperatively.
Motivation
Usually someone needs to create a Project before creating the credentials (chicken/egg), even if they will store the configurations declaratively
Suggested Implementation
Since promotionPolices can be tricky to write an intuitive CLI against...I would recommend looking at kubectl create role and kubectl create clusterrole as users would probably be used to that type of syntax
example (off the top of my head)
kargo create promotionPolicy dev --auto-promote=true --project  kargo-demo
Or, if we want to leave it in the project subcommand
kargo create project  kargo-demo --promotion-policy=dev --promotion-autopromote=dev:true --promotion-policy=uat  --promotion-autopromote=uat:true
Just ideas, I'm completely open to any implementation that makes sense.

I am somewhat opposed to this for a few reasons:

Policies are almost guaranteed to grow in complexity over time. There are a number of open issues that are likely to be addressed through new policy fields -- for instance specifying, "freeze" or "blackout" windows where promotions do not occur. Projects are likely to eventually have more properties than just PromotionPolicies as well. It will be a burden to keep the CLI up to date with all those options, which segues into the next reason...

Beyond a certain degree of complexity, doing things imperatively just does not make sense anymore. Your kubectl create role example may feel reasonable on some level, but only because Role resources are relatively simple. Look at kubectl create deployment and you will notice two things: The number of flags is absolutely dizzying and even with all of those options available, there are still things you can only do declaratively. One wonders why they bothered with all those flags.

Usually someone needs to create a Project before creating the credentials (chicken/egg), even if they will store the configurations declaratively

This isn't so much of a problem as you might think.
Taking Kargo out of the equation and speaking about out-of-the-box Kubernetes resources, something similar goes on with namespaces. If you're declaring a namespace and a bunch of resources that belong in that namespace, you have the following options, both of which are fairly well-established conventions that Kubernetes respects:

Put all the resources in a single file, with the namespace(s) preceding everything else.
When dealing with multiple files, use naming conventions (like prefixing certain files with _) to create an implied ordering, with namespaces first.

In either case, Kubernetes will create resources in the desired order. These same strategies work with Projects, and in fact, we were quite careful to ensure that. I've observed 100% success rate with the following:

my-project.yaml:
apiVersion: kargo.akuity.io/v1alpha1
kind: Project
metadata:
  name: kargo-demo
spec:
  promotionPolicies:
  # ...
---
apiVersion: v1
kind: Secret
metadata:
  namespace: kargo-demo
  # ...
# ...
---
apiVersion: kargo.akuity.io/v1alpha1
kind: Warehouse
metadata:
  namespace: kargo-demo
  # ...
# ...
---
apiVersion: kargo.akuity.io/v1alpha1
kind: Stage
metadata:
  namespace: kargo-demo
  # ...
# ...
---
# ...

$ kargo create -f myproject.yaml

I'll leave the final decision up to @jessesuen, however.

I'm inclined to agree with @krancour here. Just look at what happened with argocd app create and the dozens of flags that were added to that command (which, btw, is still incomplete from full available options).
That said, I agree there should be some flags for very common settings that will enable people to get started. But aside from that, I would keep things in the spec, and make the UI easy to enable a lot of these features.

I agree there should be some flags for very common settings that will enable people to get started.

We should open a separate issue for that if/when useful flags for Project creation become apparent.


Fixes Telescope Issue #1936, added Cache-Control microservice

This is a middleware service that addresses the needs for Cache-Control Levels.
Arguments:

res : The object that will be assigned our Cache-Control levels

Cache Durations:
never(res) - The never() function doesn't not allow caching at all, max-age is set as 0, along with no-store.
duration(time, res) - Allows a user to set a custom time for max-age.
forever(res) - allows caching for up to 1 year, and sets the item as immutable.
Freshness, and Staleness
It's possible to set your Response to a certain freshness, or how long the response can be stale for.
freshFor(time, res) - Sets the amount of time a response could be fresh for.
staleFor(time, res) - Sets the amount of time a response could be stale for.
When calling our Cache Control functions, this is how you call the functions/
For example,
cache().forever(res); // Sets max-age to 1 year forever
cache().duration('1m', res); // Sets max-age to 1 month

Let me know when you want this reviewed again, it looks like you're still working?

Let me know when you want this reviewed again, it looks like you're still working?

@humphd  Yup! I am. Quite a lot of progress though, I got nginx to set our Cache Control headers, along with Read/Write to the config file by class. If by any chance, we would need to add anything in our nginx config dynamically, we could do so now, along with setting our Caches to their respective levels as defined above.
Eg: finding all the values for add_header within the http portion of the config

value is a variable passed, and it's the block within a config (in the pic, value is set to http)
it also supports adding in new blocks if we ever need it:

prop is the name of the new block that we would like to create.


Update dogestry to 2.1.6

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as bc32a23ec8c58411505eb7051739f07b9f842543. Your contribution is still credited to you.


Increasing the flexibility of plotAssemblyTypes

Description
This is in response to #623 . Essentially, just making a plotting function a little more flexible.
(Also I removed a couple of unused files from the repo.)

Checklist

[X] The code is understandable and maintainable to people beyond the author.
[X] Tests have been added/updated to verify that the new or changed code works.
[X] There is no commented out code in this PR.
[X] The commit message follows good practices.
[X] All docstrings are still up-to-date with these changes.

Hey John, thanks for doing this. I was planning on doing it myself, but just hadn't gotten around to it. Appreciate it!


Haiku App Package Config and Build utility

I think the biggest hurdle after developing and compiling a Haiku application is doing the package work.  It would be great to have the ability to configure and build the package (*.hpkg) from Paladin IDE.

Funnily enough I was just thinking of this yesterday. :) My workflow for Paladin is:-

Dev a feature (Tests first TDD)
Run tests to check it works and to find any regressions
Merge feature branch to develop
Export latest translation work (but don't wait for it to all be finished...)
When develop ready, merge to master, tag as version and release
Update hpkg recipe on haikuports for latest release
Build hpkg successfully (64 and 32 bit)
PR for new working recipe

The more of that I can automate the better. Ideally point Paladin to the main project PLD, the tests PLD, and the recipe in haikuports and saying "Have at it".
Is this the kind of thing you were thinking?

it could make sense to run the "package" tool directly and build an hpkg file without the help of haikuports, for distribution outside the haikuports repository.

@pulkomandy Sounds like it will work... How do things wind up listed in HaikeDepot outside of HaikuPorts?

You can create alternative repositories (using the package_repo) tool and let users add these using pkgman or Repositories preferences. Or you can just put the hpkg file online or give them to people on whatever convenient media, and they can install it with a double click.
For the official haikuports repo, going through a recipe is required because haikuporter does some sanity checks and ensure a minimal level of QA.


More Analytics: Count Dat archives and test global net reachability

Extend analytics to track these additional usage metrics:
netReachablePort
Asks a remote server to test whether the client’s Dat port is reachable or not. Using Transmission’s test server as a proof of concept until this can be moved to Beaker’s own analytics server. Data will help determine how many people are capable of acting as nodes and participating in the network.
datWatchlist
Number of items on the watchlist. Data will help prove how useful this feature is and also how many people regularly have problems downloading Dat archives.
datArchivesOwned
Number of archives the client has created. Data will help establish whether people are creating with Beaker.
datArchivesSeed
Number of archives the client is seeding. Data will help determine whether people actively choose to volunteer bandwidth and help keep the distributed network healthy.
datArchivesCache
Number of cached archives. Data will help determine whether people are engaging with content on the distributed web.
I’ll work on the server side next if there is interest in adding support for the above. I don’t believe the above constitutes personal data nor do I believe any user would object more to participating in analytics data collection with or without the above data points.

Sorry this never got discussed, we were focused on the 1.0 release. We'll do a pass on analytics in the near future


Redirect 'swift --version' stderr to /dev/null

With the new swift driver running 'swift --version' will always print "swift-driver version: X.Y.Z" to stderr before printing the normal version info to stdout.
This causes all of the version checks as swiftenv runs to print the driver over and over.
The other option is to instead pass the flag '-disallow-use-new-driver' but at some point the new driver will most likely become the only driver so this future proofs against that.

Thanks for catching and fixing this @bscothern


The project website dotspatial.codeplex.com cannot be accessed

Including http://dotspatial.codeplex.com/discussions is also not accessible

Is there some problem with the server? or the IP address is not configured correctly？

The former codeplex.com web site has been replaced with Github. Microsoft
used to run codeplex but they have shut it down. You can find all
discussions and documentation about DotSpatial here:
https://github.com/DotSpatial/DotSpatial/

Daniel P. Ames, Ph.D., P.E.
Professor, Civil & Environmental Engineering,Brigham Young University,
Provo, Utah, USA
Past-President, International Environmental Modelling & Software Society
Editor-in-Chief, Environmental Modelling & Software
http://ceen.et.byu.edu/content/dan-ames
https://ceen.byu.edu/directory/dan-p-ames
http://www.researchgate.net/profile/Daniel_Ames
http://scholar.google.com/citations?user=S0GUCeUAAAAJ

On Tue, May 10, 2022 at 3:52 AM BINGHUAice @.***> wrote:

Including http://dotspatial.codeplex.com/discussions is also not
accessible
[image: image]
https://user-images.githubusercontent.com/63250003/167601077-0c5d16ac-7c2f-4df1-a485-1d2fff949c23.png
Is there some problem with the server? or the IP address is not configured
correctly？
—
Reply to this email directly, view it on GitHub
https://github.com/DotSpatial/DotSpatial/issues/1444, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2PZ5AGBAOKF7EZ6TWARSLVJIWUHANCNFSM5VRAHGXQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

you should probably updated your readme then since it directs you to codeplex for documentation

I have tried to translate some of the documentation here: https://github.com/sindizzy/DSW/wiki


Versioning

Can I make a request that once you are moderately happy (perhaps after worker changes) you do a pre-release version? It can be v0.1.0alpha1 for all that matters.
I would be happy to test it for you and report any issues. That makes it easier to easily identify releases to merge, QA and deploy.

Absolutely. It will be after this worker thing is resolved.
I appreciate your help dude.
It'll also help me with the bundle.


Use Enum names for Ocarina Actions and Sequence IDs

forgot to include that in the previous PR, both games match on my side, both gists are updated (oot, mm)

OOT and MM both OK. MM needs this patch
https://gist.github.com/louist103/d2f7c4839d384457cf08872b1965b35e


Issue with many parallel subscribe tasks with same pool

First a reminder of this TODO in the docs section about aioredis.pubsub.Receiver:

To do: few words regarding exclusive channel usage.

Moreover, I found out the hard way that my pubsubs receiver randomly either work or not work, depending on random start up order.  The reason was that I was using a redis pool, which picks a random connection.
In my strong opinion, this is a big trap you have laid out for developers using aioredis.  Using the method subscribe() of a Redis pool object is not safe, since it may pick one connection for the subscribe and later when you start listening with a Receiver another connection may be picked.  Therefore you don't receive anything!
I'm not sure what is the best way to fix this, but IMHO aioredis should at the very least detect this problem.  Perhaps don't allow shared connection Redis object to have stateful methods like subscribe and unsubscribe.
Right now what seems to work is something like:
with await self.redis as redis:
    await redis.subscribe(receiver.channel("channelname"))
    async for sender, msg in receiver.iter():

When using shared redis (backed by a pool), things randomly do not work.  Like I said, a big way to let developers shoot themselves in the foot.

I stumbled across the same issue and I want to share a workaround - as it isn't so obvious what to do (until the refactoring took place or the documentation puts more emphasis on that).
Example of one publisher and two subscribers (channel name "event") that does not work as intended (here only one of the subscribers gets the messages):
import asyncio
import logging

from aioredis import Redis, create_redis_pool

log = logging.getLogger(__name__)

async def subscriber(redis: Redis, name: str):
    ch, = await redis.subscribe('event')
    try:
        async for event in ch.iter():
            log.info(f'{name} received "{event}"')
    finally:
        ch.close()

async def publisher(redis: Redis):
    for i in range(10):
        message = f'Published "{i}"'
        await redis.publish('event', message)
        log.info(message)
        await asyncio.sleep(1)

async def run():
    redis = await create_redis_pool("redis://localhost")
    sub_task1 = asyncio.create_task(subscriber(redis, 'sub1'))
    sub_task2 = asyncio.create_task(subscriber(redis, 'sub2'))
    pub_task = asyncio.create_task(publisher(redis))
    await pub_task
    sub_task1.cancel()
    sub_task2.cancel()
    redis.close()
    await redis.wait_closed()

logging.basicConfig(level=logging.INFO, format='%(asctime)-15s %(message)s')
asyncio.run(run(), debug=True)

Workaround: Use a dedicated connection to subscribe to messages:
async def subscriber(redis: Redis, name: str):
    with await redis as r:
        ch, = await r.subscribe('event')
        try:
            async for event in ch.iter():
                log.info(f'{name} received "{event}"')
        finally:
            ch.close()


CancellationToken throws even if throwing is not requested

https://msdn.microsoft.com/en-us/library/system.threading.cancellationtoken.throwifcancellationrequested(v=vs.110).aspx
http://stackoverflow.com/questions/7343211/cancelling-a-task-is-throwing-an-exception
First link above documents ThrowIfCancellationRequested - presumably the token does not throw if the method is not called first, correct?
    [Test]
    public async Task CancelTokenTest()
    {
        SemaphoreSlim sem = new SemaphoreSlim(0, 1);
        CancellationTokenSource src = new CancellationTokenSource();
        CancellationToken token = src.Token;
        Action a = async () => await sem.WaitAsync(token);
        a();
        src.Cancel(); // throws
    }

I'm thinking this belongs at https://github.com/dotnet/corefx.

In your code, WaitAsync() throws, because token became cancelled. Since a is async void, the exception is rethrown on the current synchronization context (if there is one).
Which part of that is not the behavior you would expect?

Thanks svick, I do not expect the token to throw as I have not called ThrowIfCancellationRequested.
Sorry if I posted in the wrong place.

It looks like I was confused on the purpose of ThrowIfCancellationRequested............
I read the documentation for CancellationTokenSource which says:

Call the CancellationTokenSource.Cancel method to provide notification of cancellation. This sets the CancellationToken.IsCancellationRequested property on every copy of the cancellation token to true.

and for some reason I thought that calling the CancellationTokenSource.Cancel method would provide notification of cancellation by seting the CancellationToken.IsCancellationRequested property on every copy of the cancellation token to true.
But it looks like this is only half the story as the CancellationTokenSource appears to have to throw to cause the semaphore to continue.

But it looks like this is only half the story as the CancellationTokenSource appears to have to throw to cause the semaphore to continue.

It's not really the CancellationTokenSource itself that throws, it's the WaitAsync. And the whole point of passing the CancellationToken to that method is so that it can be cancelled, which you can observe as it throwing an exception.
Effectively, WaitAsync calls ThrowIfCancellationRequested, or does something similar, so that it can be cancelled.

which you can observe as it throwing an exception.
Regardless of who throws I would much rather observe the IsCancellationRequested property without the exception.  Having read the code (line 727) I am still not clear why WaitAsync - or anyone else - needs to throw.
It seems to me that line 727 takes control from the developer (which she/he has by way of ThrowIfCancellationRequested) and just imposes the exception.  This is, in many cases (certainly in my case), a violation of the good design principals found here.

@sam-wheat That's how CancellationToken works: if you pass it to a method, the token gets cancelled and the method observes it, it will throw an exception.
It does not take control from you, you gave up the control by passing the CancellationToken to the method.
If I understand you correctly, you propose that if the method observes that the CancellationToken is cancelled, it should just silently return? I think that would be a terrible idea, because you would have no indication that the method did not finish successfully.

@svick No, I don't think CancellationToken works that way.  As cited in my post above I believe the functionality is like this:

Call the CancellationTokenSource.Cancel method to provide notification of cancellation. This sets the CancellationToken.IsCancellationRequested property on every copy of the cancellation token to true.

If the developer observes the IsCancellationRequested property and chooses throw that is his decision (ThrowIfCancellationRequested makes this a bit easier).
In many cases (such as mine), cancellation is part of normal program flow and I do not want to use or rely on exceptions.  In the case of the semaphore, I should at least have an opportunity to observe IsCancellationRequested and throw if i desire to to so.  However as you describe the WaitAsync method denies me this opportunity by throwing in advance.
I've worked around this by implementing a TryWaitAsync Extension method.  I still have to live with the exception at the framework level however.  My suggestion is that semaphore slim implement something like TryWaitAsync and not throw in this new method.

I don't think CancellationToken works that way.

What I meant is that, as far as I know, every single method that supports cancellation by accepting a CancellationToken does work that way.

My suggestion is that semaphore slim implement something like TryWaitAsync and not throw in this new method.

Then you should file an issue on the corefx repo, following the API review process.

Closing ... satisfactory guidance has been given. Thanks @svick.


Fix exit error TypeError("'NoneType' object is not callable",) using catch try block in close method

Fixes https://github.com/piskvorky/sqlitedict/issues/44
@piskvorky
Added try catch block to close function to prevent error log message in __del__ method when sqlitedict is not closed correctly. Error was raised by conn.close() and conn.commit()

@tmylk @piskvorky I rebased commits to return to original close method and added only try catch to __del__ method.

@janrygl @tmylk this PR seems to contain unrelated changes (read-only sqlite?), what's going on there?

The read-only commits have already been merged. I was planning to cherry-pick just @janrygl's changes once we converge here.

Merge in https://github.com/piskvorky/sqlitedict/commit/9cc6dd3be9fb00fb5569347b44412067d5e2ae19


session-bind

fix to session.bind api reference to remove template handler and make it pure angular

wrong files added.


Legacy Makeup Converter - Feminine Veena Issues

Legacy Makeup Salvager forces a purple forehead gem for Viera Veena Feminine faces 1, 2 and 4. It is omitted from face 3, and the Legacy Makeup Salvager appears to be working correctly for this face option.

Example conversions for Face 2, Face 3 and Face 4 attached. These are all from the same original .tex file.


Unknown host.json file in documentation

In order to enable dependency management, you say to edit the host.json file.  Where is this file?  I see a function.json file but no host.json.

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

ID: efae763f-03a9-b3b0-e7ad-52f9b1559438
Version Independent ID: 2afd9c78-e5b0-5d34-b809-47d9576399d0
Content: PowerShell developer reference for Azure Functions
Content Source: articles/azure-functions/functions-reference-powershell.md
Service: azure-functions
GitHub Login: @eamonoreilly
Microsoft Alias: glenga

@philhines Thanks for the question! We are investigating and will update you shortly.

@SumanthMarigowda : I had a chat with the original author yesterday and he helped me with this. In retrospect I think the article does cover this sufficiently.  I just missed it.


Errors have no real stacktrace

I often have these kind of errors
gekko_1       |   xxx POST /api/backtest 500 774ms -
gekko_1       |
gekko_1       |   Error: non-error thrown: Child process has died.
gekko_1       |       at Object.module.exports.onerror (/usr/src/app/node_modules/koa/lib/context.js:105:40)
gekko_1       |       at process._tickCallback (internal/process/next_tick.js:103:7)

But they are very hard to debug without actual proper stacktrace that indicates me where the code failed :/
Any idea regarding the possibilities of improving that ? I've been using gekko only for some days so I'm not yet familiar with its inner structure.

I will update the docs, but this is what I am thinking:
If you are working on your own plugins or strats, it's a lot easier to use the commandline interface for Gekko. This way everything runs in a single process and debugging behaves the same as any other nodejs project. Refer how to set that up here: https://gekko.wizb.it/docs/commandline/about_the_commandline.html

Hi ! Yes I've been using the commande line interface for my plugins and strats, it made things easier indeed :)
As for my problem specifically, I got these errors with Gekkoga which uses the Gekko API to run its backtests. Depending on the date range and/or dataset I use to run my tests, I get these errors, even though the same test setup works from the backtest CLI or the UI which is odd.
I'll try later today if I can find a way to print more info in the stacktrace and debug that.
Thanks for your help though!

Thanks ! It helped. Looks like there was an issue in the data I pulled from Poloniex, I was getting Simulation based on incomplete market data errors.
I pulled the data several times and it ended up working (pure luck). If this is of any help, here is a sample of imported data log
2017-12-11 19:58:22 (DEBUG):	No end date specified for importing, setting to 2017-12-11 19:58:22
2017-12-11 19:58:23 (INFO):	BTC LTC Requesting data from 2017-12-10 00:00:00, to 2017-12-10 02:00:00
2017-12-11 19:58:25 (DEBUG):	Processing 3782 new trades. From 2017-12-10 00:00:01 UTC to 2017-12-10 02:00:00 UTC. (2 hours)
2017-12-11 19:58:26 (INFO):	BTC LTC Requesting data from 2017-12-10 01:50:00, to 2017-12-10 03:50:00
2017-12-11 19:58:28 (DEBUG):	Processing 3828 new trades. From 2017-12-10 02:00:01 UTC to 2017-12-10 03:49:59 UTC. (2 hours)
2017-12-11 19:58:29 (INFO):	BTC LTC Requesting data from 2017-12-10 03:40:00, to 2017-12-10 05:40:00
2017-12-11 19:58:32 (DEBUG):	Processing 4203 new trades. From 2017-12-10 03:50:01 UTC to 2017-12-10 05:39:47 UTC. (2 hours)
2017-12-11 19:58:33 (INFO):	BTC LTC Requesting data from 2017-12-10 05:30:00, to 2017-12-10 07:30:00
2017-12-11 19:58:35 (DEBUG):	Processing 2387 new trades. From 2017-12-10 05:40:05 UTC to 2017-12-10 07:29:58 UTC. (2 hours)
2017-12-11 19:58:36 (INFO):	BTC LTC Requesting data from 2017-12-10 07:20:00, to 2017-12-10 09:20:00
2017-12-11 19:58:37 (DEBUG):	Processing 1978 new trades. From 2017-12-10 07:30:09 UTC to 2017-12-10 09:19:59 UTC. (2 hours)
2017-12-11 19:58:38 (INFO):	BTC LTC Requesting data from 2017-12-10 09:10:00, to 2017-12-10 11:10:00
2017-12-11 19:58:40 (DEBUG):	Processing 2295 new trades. From 2017-12-10 09:20:38 UTC to 2017-12-10 11:09:55 UTC. (2 hours)
2017-12-11 19:58:41 (INFO):	BTC LTC Requesting data from 2017-12-10 11:00:00, to 2017-12-10 13:00:00
2017-12-11 19:58:43 (DEBUG):	Processing 2129 new trades. From 2017-12-10 11:10:02 UTC to 2017-12-10 12:59:59 UTC. (2 hours)
2017-12-11 19:58:44 (INFO):	BTC LTC Requesting data from 2017-12-10 12:50:00, to 2017-12-10 14:50:00
2017-12-11 19:58:47 (DEBUG):	Processing 6901 new trades. From 2017-12-10 13:00:02 UTC to 2017-12-10 14:49:58 UTC. (2 hours)
2017-12-11 19:58:48 (INFO):	BTC LTC Requesting data from 2017-12-10 14:40:00, to 2017-12-10 16:40:00
2017-12-11 19:58:52 (DEBUG):	Processing 3934 new trades. From 2017-12-10 14:50:05 UTC to 2017-12-10 16:39:55 UTC. (2 hours)
2017-12-11 19:58:53 (INFO):	BTC LTC Requesting data from 2017-12-10 16:30:00, to 2017-12-10 18:30:00
2017-12-11 19:58:56 (DEBUG):	Processing 6936 new trades. From 2017-12-10 16:40:02 UTC to 2017-12-10 18:29:57 UTC. (2 hours)
2017-12-11 19:58:57 (INFO):	BTC LTC Requesting data from 2017-12-10 18:20:00, to 2017-12-10 20:20:00
2017-12-11 19:59:00 (DEBUG):	Processing 3600 new trades. From 2017-12-10 18:30:02 UTC to 2017-12-10 20:19:53 UTC. (2 hours)
2017-12-11 19:59:01 (INFO):	BTC LTC Requesting data from 2017-12-10 20:10:00, to 2017-12-10 22:10:00
2017-12-11 19:59:03 (DEBUG):	Processing 1906 new trades. From 2017-12-10 20:20:04 UTC to 2017-12-10 22:09:40 UTC. (2 hours)
2017-12-11 19:59:04 (INFO):	BTC LTC Requesting data from 2017-12-10 22:00:00, to 2017-12-11 00:00:00
2017-12-11 19:59:06 (DEBUG):	Processing 3700 new trades. From 2017-12-10 22:10:12 UTC to 2017-12-11 00:00:00 UTC. (2 hours)
2017-12-11 19:59:07 (INFO):	BTC LTC Requesting data from 2017-12-10 23:50:00, to 2017-12-11 01:50:00
2017-12-11 19:59:09 (DEBUG):	Processing 3345 new trades. From 2017-12-11 00:00:12 UTC to 2017-12-11 01:49:59 UTC. (2 hours)
2017-12-11 19:59:10 (INFO):	BTC LTC Requesting data from 2017-12-11 01:40:00, to 2017-12-11 03:40:00
2017-12-11 19:59:12 (DEBUG):	Processing 3605 new trades. From 2017-12-11 01:50:01 UTC to 2017-12-11 03:40:00 UTC. (2 hours)
2017-12-11 19:59:13 (INFO):	BTC LTC Requesting data from 2017-12-11 03:30:00, to 2017-12-11 05:30:00
2017-12-11 19:59:15 (DEBUG):	Processing 3043 new trades. From 2017-12-11 03:40:02 UTC to 2017-12-11 05:30:00 UTC. (2 hours)
2017-12-11 19:59:16 (INFO):	BTC LTC Requesting data from 2017-12-11 05:20:00, to 2017-12-11 07:20:00
2017-12-11 19:59:18 (DEBUG):	Processing 6110 new trades. From 2017-12-11 05:30:01 UTC to 2017-12-11 07:19:52 UTC. (2 hours)
2017-12-11 19:59:19 (INFO):	BTC LTC Requesting data from 2017-12-11 07:10:00, to 2017-12-11 09:10:00
2017-12-11 19:59:24 (DEBUG):	Processing 2517 new trades. From 2017-12-11 07:20:02 UTC to 2017-12-11 09:09:55 UTC. (2 hours)
2017-12-11 19:59:25 (INFO):	BTC LTC Requesting data from 2017-12-11 09:00:00, to 2017-12-11 11:00:00
2017-12-11 19:59:27 (DEBUG):	Processing 1826 new trades. From 2017-12-11 09:10:03 UTC to 2017-12-11 10:59:55 UTC. (2 hours)
2017-12-11 19:59:28 (INFO):	BTC LTC Requesting data from 2017-12-11 10:50:00, to 2017-12-11 12:50:00
2017-12-11 19:59:30 (DEBUG):	Processing 2637 new trades. From 2017-12-11 11:00:02 UTC to 2017-12-11 12:49:56 UTC. (2 hours)
2017-12-11 19:59:31 (INFO):	BTC LTC Requesting data from 2017-12-11 12:40:00, to 2017-12-11 14:40:00
2017-12-11 19:59:35 (DEBUG):	Processing 14683 new trades. From 2017-12-11 12:50:15 UTC to 2017-12-11 14:40:00 UTC. (2 hours)
2017-12-11 19:59:36 (INFO):	BTC LTC Requesting data from 2017-12-11 14:30:00, to 2017-12-11 16:30:00
2017-12-11 19:59:39 (DEBUG):	Processing 8279 new trades. From 2017-12-11 14:40:01 UTC to 2017-12-11 16:30:00 UTC. (2 hours)
2017-12-11 19:59:40 (INFO):	BTC LTC Requesting data from 2017-12-11 16:20:00, to 2017-12-11 18:20:00
2017-12-11 19:59:43 (DEBUG):	Processing 8979 new trades. From 2017-12-11 16:30:01 UTC to 2017-12-11 18:19:59 UTC. (2 hours)
2017-12-11 19:59:44 (INFO):	BTC LTC Requesting data from 2017-12-11 18:10:00, to 2017-12-11 20:10:00
2017-12-11 19:59:48 (DEBUG):	Processing 7153 new trades. From 2017-12-11 18:20:03 UTC to 2017-12-11 19:58:22 UTC. (2 hours)
2017-12-11 19:59:48 (INFO):	Done importing!

I saw in the code that there is an overlapSize between batches, and if you look and the Requesting data and Processing X new trades logs, the timestamp is quite different, as if the overlap size was not respected.


Qingkai added the mining emails using python

Hi all,
This is my script for this afternoon, please merge it. Thanks!

Thanks Stuart! See you this afternoon! I will be there 10 min earlier to
setup!
On Wed, Mar 30, 2016 at 10:35 AM, Stuart Geiger<EMAIL_ADDRESS>wrote:

Merged #55 https://github.com/thehackerwithin/berkeley/pull/55.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/thehackerwithin/berkeley/pull/55#event-608626168

--
Qingkai KONG
Ph.D Candidate
Seismological Lab
289 McCone Hall
University of California, Berkeley


bot will not boot up

so I'm sourcing and this never happened until I updated the bot because I had not updated in a while.

Some app is using NadekoBot.Core.dll. Restart the computer or find that app (another instance of the server?)

already did that. was told to post here from the discord

Yea. That's the issue. Maybe your antivirus then? Or you're running it as a service maybe. In either case, something is using your bot's files.

I just did a tasklist on the directory of what its saying is being used and showed nothing

reopen plz

even disabled antivirus and still didn't work

Try this: duplicate the root folder with a different name, then start the new one.

root folder as in the folder i put everything in or?

didnt work

You mean the same thing happened with the new one? It's being used by another process?

Yes i even installed a fresh ftom github and moved the database and credentials over and still happes

@kwoth

You can try re-installing windows tottaly. But instead of putting the db back. Just add the token only (get a new one) and just start the bot. Should just work.
You can always put the db back later, but for now i'm curious how it would work with your hardware and all.


add fail2ban support

Added with https://github.com/dd-dreams/aft/commit/5fbb2b89e1200c4986662e2de565890a046daea5


Spawning new MaterialMeshBundles takes ~3-5x longer in Bevy 0.12 with WASM + WebGL2

Bevy version

Original: 0.11.3
Current: 0.12.0

Relevant system information
Chrome 119
Rust 1.73.0 (Stable)
AMD Ryzen 9 5900X
NVIDIA GeForce RTX 4070
What's performing poorly?
Spawning a new mesh (and/or a new material? Not sure exactly what the trigger is) that hasn't been rendered previously triggers a significant hiccup in WASM builds with the WebGL2 backend. This was also the case previously, but 0.12 has significantly increased the duration of these "hiccups".
Repro
The problem should be pretty apparent with any sufficiently complex glTF scene, but I'm also seeing the issue with programmatic geometry (e.g. Mesh::from(shape::*)) and simple flat-color materials (e.g. StandardMaterial { base_color: Color::RED, unlit: true, ..default() }).
Before and After Traces

Before: https://drive.google.com/file/d/1LChOxM5_1ezh56WPtAVTRXy3pZlkJWex/view?usp=sharing
After: https://drive.google.com/file/d/1OrA03YPNWpJEKiQlbSLvhmaLHA6mVcDE/view?usp=sharing

Additional information
The traces above were captured in an app that loads a fairly complex glTF scene. After loading, I click a few buttons which trigger some new (programmatic) meshes to spawn. The same steps were followed in the same order to produce each trace, and the only substantive difference between the two builds was upgrading Bevy from 0.11.3 to 0.12.0.
The specific function call that seems to be triggering the slowdown is WebGl2RenderingContext::get_program_parameter, which is called by glow::web::Context::get_program_link_status, which is called by wgpu::Device::create_render_pipeline. I suspect this is because the shaders have gotten much larger with the introduction of the deferred pipeline, but I'm very much not an expert on this type of thing.
This is a private project for my employer, so I can't share a link to the repo or anything, but I could likely get permission to share a link to the staging site in a DM if that would be helpful.

The stuttering is due to the driver compiling shaders for your GPU. You'll have the same problem on native, it's just that newer graphics APIs have much better compilers that aren't as slow (but still slow enough to cause visible stutter). You ideally want to spawn an instance of each of your materials ahead of time in a loading screen in order to get the pipelines (shaders) cached. You can despawn the material afterwards.
As for why it got worse in Bevy 0.12, try adding the component ShadowFilteringMethod::Hardware2x2 to your camera.

That's super helpful, thanks for the info!

You'll have the same problem on native, it's just that newer graphics APIs have much better compilers that aren't as slow (but still slow enough to cause visible stutter).

I assume that means that switching to WebGPU would also improve things?

You ideally want to spawn an instance of each of your materials ahead of time in a loading screen in order to get the pipelines (shaders) cached.

Any insight on which of the StandardMaterial properties require a unique shader permutation? Also (this one's a long shot), once a shader is compiled, is there any way we could retrieve and store it on the user's machine so it doesn't need to be recompiled on subsequent application launches?

As for why it got worse in Bevy 0.12, try adding the component ShadowFilteringMethod::Hardware2x2 to your camera.

That did help quite a bit, thank you!

Any insight on which of the StandardMaterial properties require a unique shader permutation?

For StandardMaterial specifically, take a look at StandardMaterialKey. Each possible value of the key type will be a different pipeline. However, that's just one layer of the pipeline (specialization) system. There are other keys that influence the final pipeline. The specific mesh you're using as well as view-specific things like SSAO change the pipeline. Look at MeshPipelineKey. Various effects or other systems also have multiple shader permutations, such as SSAO or TAA themselves.

I assume that means that switching to WebGPU would also improve things?

Probably? I don't have any hard data

is there any way we could retrieve and store it on the user's machine so it doesn't need to be recompiled on subsequent application launches?

Not at the moment, no.


Add config random_page_count for production

Issue #301
How to test if it really works?
Check if Jarbas performance improved
Who can help reviewing it?
@cuducos

Many thanks, @caduvieira — it seams to work nicely ; )


[5.0] Fix PythonString::GetString for >=python-3.7

Cherry-pick of https://reviews.llvm.org/rLLDB337908 to swift-5.0-branch.
SR-9180

@swift-ci Please test

Uh, hm. We took Linux off the requirements for the Swift repo for swift-5.0-branch because the corelibs repos haven't branched. Should the same have been done for LLDB? Or should I just wait two weeks?

@shahmishal See Jordan's comment. I have a bunch of stuff to integrate, I really need PR testing to work on the 5.0 branch

Note that this is dangerous. LLDB works on the 5.0 branch which is then auto merged into stable. If we don't test on Linux on the 5.0 branch we might break Linux PR testing on stable as a side effect.

@milseman was working on creating bug report on bugs.swift.org.
We are seeing this issue because we auto merge master into swift-5.0-branch for swift-corelibs-* projects. The change corresponding to foundation needs to be cherrypicked into swift-5.0-branch or reverted.

https://bugs.swift.org/browse/SR-9189 was what I filed

@swift-ci Please test Linux

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test macOS

@fredriss Do I need special approval to merge this? It's mostly just a favor for those using Python 3.

Nope, that's fine. I just merged it


Data types - reader/writer/deletion roles

Allow developers to define reader/writer/deletion roles for each collection instead of them being defined automatically for the user.
If no roles are defined by the user, then the defaults (as is) should be defined. The user must be able to define more than 1 role for each.

New requirement, ability to define that no role is required and that only a valid token is required.

Added in commit beb4420e2a73bae06dd1da15e543145b0a13e8fc, allows for the configuration of:

0 or more roles for read, write and delete operations on a data type
Ability to remove the default roles from being applied on a data type
Ability to remove the need for any role to be defined for read/write/delete operations


Ensure at least version 1.8 of tmux

This is required for tmuxinator, according to the README.

Resolved in f4c3d6785bbd073ceeb2230da8574c7e7efc346f. I went ahead and ensured version 2.2, because various parts of my .tmux.conf probably depend on the version being even more recent than 1.8.


Update installation instructions

PR #40 creates docs/install.rst which includes installation instructions for xrtpy which were copied over from PlasmaPy's repository. I put an admonition near the top that states that the instructions are written in preparation for the 0.1.0 release, and thus are not valid yet.  These will need to be updated before the 0.1.0 release.

@namurphy, after reviewing the installation instructions, they appear to be functionally correct. If everything looks good, let's go ahead and close this issue?


mailpit: 1.20.4 -> 1.21.0

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for mailpit is: Email and SMTP testing tool with API for developers
meta.homepage for mailpit is: https://github.com/axllent/mailpit
meta.changelog for mailpit is: https://github.com/axllent/mailpit/releases/tag/v1.21.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.21.0 with grep in /nix/store/9cq7ikqr606pnnh1sai7kgwqqibvsq78-mailpit-1.21.0
found 1.21.0 in filename of file in /nix/store/9cq7ikqr606pnnh1sai7kgwqqibvsq78-mailpit-1.21.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
mailpit

Instructions to test this update (click to expand)

Build yourself:
nix-build -A mailpit https://github.com/RafaelKr/nixpkgs/archive/cadbd79f3cd276ed97831cb246efe9df6dcf5f4d.tar.gz

Or:
nix build github:RafaelKr/nixpkgs/cadbd79f3cd276ed97831cb246efe9df6dcf5f4d#mailpit

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9cq7ikqr606pnnh1sai7kgwqqibvsq78-mailpit-1.21.0
ls -la /nix/store/9cq7ikqr606pnnh1sai7kgwqqibvsq78-mailpit-1.21.0/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @stephank for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

obsoletes https://github.com/NixOS/nixpkgs/pull/345528

@RossComputerGuy could we get this into 24.11?
That release adds support for socket based communication which is very useful for running multiple instances without Port conflicts required to manage multiple hostings on the same server. See https://github.com/axllent/mailpit/issues/373

Result of nixpkgs-review pr 351837 run on aarch64-linux 1

1 package built:

mailpit


Write schema for empty parquet files

Is your feature request related to a problem? Please describe.
I am trying out daft as an alternative to spark, in our current use of spark we make use of the feature that even if dataframe is empty, spark will still create an empty parquet file with the schema of the dataframe, I would like daft to do the same
Describe the solution you'd like
I found the following issue in pyarrow which seems to indicate it is "bug" in arrow, either we wait for the upstream fix or we work around it by using pyarrow.parquet.write_table when writing parquet
Let me know what you think, I am might also be able to help drive this change

Hi @Hanspagh !
Are you referring specifically to the df.write_parquet(...) API, and that you'd want an empty df to write an empty Parquet file?
We could likely corner-case this to work, but it might get a little messy because we do distributed writes. Each partition writes its own Parquet file(s), and so in the event that you have N partitions and all of them are empty, then we'd end up with N empty Parquet files.

Yes I am referring to df.write_parquet(..), maybe I can explain a bit more about our use-case and why we 'need' empty parquet files.
In our data transformation repo we automatically smoke test all our transformation jobs with random sample data based on the input schemas for the job, and then we can validate that the output of the job matches a output schema. This work very well in spark because no matter the filters etc. spark will always produce a parquet file with a schema based on the query plan.
We are experimenting with using daft as a replacement for spark and would be very sad to lose this possibility for automated smoke-tests.
I see the problem in ending up with several empty parquet files because of partitions, for our use-case it would not really matter, since this is only used for testing anyways, but maybe we need make this behavior optional?

That makes sense. Couple of follow-up questions for you here:

Does Spark have the behavior of writing many empty Parquet files, or does it somehow just write one empty file?
We've tested Spark behavior before and when writing Parquet files it always writes multiple files (at least one file per executor). Is this consistent with what you're observing as well?

There is a separate but perhaps related thread on getting Daft to write to a single Parquet file (instead of outputting multiple files): #2359
Perhaps in "single-file" mode it could be expected to output an empty Parquet file, but in the "many-file" mode it would output an empty directory.

I just did bit of experimenting. As you said spark will always write a parquet directory (a folder with 1 or more parts in it) and dont think there is a way to get spark to a write a single file.
I tried to play a bit round with spark locally and it seems no matter the amount of executor I only get a single part, when the output file is empty. I think the official docs says that spark will write at least one file per partition.
Even if I force my qurry to use multiple partitions with repartition, the final number of partitions for my empty df will be 0, hence I get get a single part in my parquet file. If I instead change the partitions for a df with data I get one part for each partition.
That being said for our usecase it does not really matter, since this is purely for testing purposes, but if you want to align with spark you might want to adhere to ther above :).
I hope this helps, please reach out if need more information :).

By the way we didn’t manage to work on this just yet, but a couple of updates that might help here:

We merged a Schema.to_pyarrow() which should help with testing quite a bit!

We’re working on a new version of our execution engine, which will help us produce just 1 file instead of many files for our local runner. This will make it much easier to support this empty file usecase!

--
Jay Chia
Founder, Eventual ( https://www.eventualcomputing.com/ )
On Fri, Jun 21 2024 at 1:30 AM, Hans < @.*** > wrote:

I just did bit of experimenting. As you said spark will always write a
parquet directory (a folder with 1 or more parts in it) and dont think
there is a way to get spark to a write a single file.
I tried to play a bit round with spark locally and it seems no matter the
amount of executor I only get a single part, when the output file is
empty. I think the official docs says that spark will write at least one file
per partition.
Even if I force my qurry to use multiple partitions with repartition , the
final number of partitions for my empty df will be 0, hence I get get a
single part in my parquet file. If I instead change the partitions for a
df with data I get one part for each partition.
That being said for our usecase it does not really matter, since this is
purely for testing purposes, but if you want to align with spark you might
want to adhere to ther above :).
I hope this helps, please reach out if need more information :).
—
Reply to this email directly, view it on GitHub (
https://github.com/Eventual-Inc/Daft/issues/2373#issuecomment-2182269510 )
, or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AEG7ELVBZ3T2DFOVS3GTFBTZIPQCDAVCNFSM6AAAAABJIHAAG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBSGI3DSNJRGA
).
You are receiving this because you commented. Message ID: <Eventual-Inc/Daft/issues/2373/2182269510
@ github. com>

Thank you for the update, we are looking forward to see what you come up with :)

@Hanspagh we just merged in #2540 which should do this by default. This will be out in the new release, let us know if you get to try it!


Overridden locale domains don't switch locale

Environment

Operating System: Darwin
Node Version:     v20.9.0
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, modules, i18n
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-dx8kkg?file=nuxt.config.ts
The reproduction will not work on stackblitz due to using the custom domains. Please clone it & test locally.
Describe the bug
The documentation says:

Alternatively, to avoid the need for multiple builds, the locale domains can be overridden via runtime environment variables. The variable name should follow the format NUXT_PUBLIC_I18N_LOCALES_{locale code}_DOMAIN

However, based on my testing, this doesn't seem to work. The domains provided through .env do appear in the lang switcher (result of switchLocalePath() call), however, they don't switch the locale.
I'm not sure if I'm just doing something wrong or if this is a bug, but regardless, this issue either needs fixing or the documentation needs to be updated. I'd be happy to update the docs if necessary.
Additional context
No response
Logs
No response

Sounds similar to #2602
@CernyMatej did you find any workarounds?

Sadly, still waiting for a fix

@kazupon any update?

We've encountered the same problem.

Same for us.
Any update on this?

Still the same problem here

Same problem here.


[Feature Request] RPM package and make available through the Fedora repositories

Hi, thanks for the request! I think having fend be available in a Fedora repository would be great but I’m not keen on maintaining or building an RPM package myself. I’m also not too familiar with the process for adding a package to the Fedora repos.
From what I've gathered from these docs, it seems like someone will have to create the package and go through the approval process with a Fedora maintainer. So if you or someone else wants to do that that'd be awesome! But since it’s not something I’ll be handling myself, I’ll go ahead and close this issue for now.


Non-working android 7.1.2 MIUI 9.5

Thank you excellent app, but didn't work in my new cell phone from xiaomi.
Good work.

Have you had a phone with MIUI before that worked with Ad-Free? I don't know how much of MIUI is custom but the currently implemented ad-detector relies on specific notification attributes set by the Android runtime.
some trouble shooting hints:

try to reinstall Ad-Free
try to run it with a Spotify version which is listen in the README file.
does the Ad-Free notification appear when ads are active?
does the Ad-Free notification appear if you press the ♫ - icon on the second screen in Ad-Free to test a selected plugin?

Here on Redmi 2 with Android 8.1 the songs are halting 'randomly'

please file a new issue if problems persist.


Split settings into "Basic" and "Advanced" sections

Pull request checklist:

[ ] CHANGELOG.md was updated, if applicable

Description
Progress towards https://github.com/Chatterino/chatterino2/issues/1956, refer to the linked issue for more information.
TODO:

[x] Devise a way to hide "Advanced" section (see ExpandableLayout class)
[x] Decide which settings should go into the "Basic" and "Advanced" section
[ ] Consistent search behavior
[ ] Decide on a strategy for "Advanced Settings" button UX
[ ] Explore other strategies: Advanced Settting on different page, Advanced Settings in different tab
[ ] Document which settings have been moved

Points mentioned by @gempir in chat:

Opening the "Advanced Settings" dropdown results in unintuitive UX as the new content is barely visible. Should at the least scroll down to the new settings.
Increase spacing to "Miscellaneous"  section. (Looks too related.)
Button should be more noticeable in general.
Why not use an existing style for advanced settings? (Either an own settings page or an own tab on the "General" page.)

I tried to emulate Chromium's style of hiding advanced setting. I like the idea of these settings being "out of the way" for most users so I opted for this approach. Curios about further input though.

Haven't looked at the PR yet, but another "advanced settings" software user is OBS, might be worth looking at that for some inspiration

Closing until I come up with a better idea to organize this


Extract polkadot-metrics grafana dashboard to a separate repo and publish it on grafana site

Similar to https://github.com/zhangyelong/cosmos-dashboard currently the dashboard is defined here https://github.com/w3f/polkadot-deployer/blob/master/config/charts/grafana.yaml#L36

Done here https://github.com/w3f/polkadot-dashboard and uploaded here https://grafana.com/grafana/dashboards/11171


iss_off_update

Probably a new branch is needed.
Several optimization:

I removed some parameters not used in the input json
I changed the field stop masks and the hot pixel masks
New bad pixel removal: it takes the median of the pixels around in order to avoid big gradients close to the hot pixels
prefilter maps is flipped now
polarimetric registration before demodulation if iss_off == True (3 iterations for a better alignment). Specific subregion used if limb observation
Automatic VtoQU correction. It uses points in which abs(V) > 3e-3. Parameters are not normalized and they are computed using all the wavelengths.
wavelength registration after VtoQU to align each wavelength using continuum maps if iss_off == True (3 iterations for a better alignment).
other small changes.

I think that's all!

Accepted the changes, made new branch: jonas_development, to save my copies of cmilos, input_jsons, download files etc. In future maybe add your cmilos libraries to your .gitignore, so these different files won't be added to the PR


Homework Submission

Post the link to your homework post here with your full name.


App not running

Hello,
I write this simple code:

(breakpoint not called)
And app not running. If i remove this code, everything works.
I add service into manifest :(
Whats I`am doing wrong?
Device with - Android L

It doesn't make sense, the library not throw an exception?  OK, there it is. You need give the job an condition at least. As we know, A job only can be triggered while its condition(s) are all satisfied, so a job without any conditions is illegal.
You can just make your own condition or just use the three internal condition, they are all broardcast in fact. Please see the README again, you can't miss it.


How to mock Futurefunction({Rect? bounds}) ?

Describe the bug
I am trying to verify that a method on a viewModel gets called on button tap but I am getting an error.
The original method looks like this :
Future<void> exportNotes({Rect? bounds}) {}
I have tried to mock it like this :
when(() => _vmMock.exportNotes()).thenAnswer((_) => Future.value());
and then run the following test :
testWidgets('calls exportNotes if button is pressed', (tester) async {
          await _pumpAssessmentDetailsCard(tester);
          await tester.pumpAndSettle();

          final exportButtonTextFinder = find.text('Export Notes');
          final exportButtonFinder = find.ancestor(
              of: exportButtonTextFinder,
              matching:
                  find.byWidgetPredicate((widget) => widget is OutlinedButton));

          expect(exportButtonFinder, findsOneWidget);

          await tester.tap(exportButtonFinder);
          verify(() => _vmMock.exportNotes()).called(1);

          tester.idle();
        });

So the button exists but when the tester runs .tap()  I am getting an error
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following _TypeError was thrown running a test:
type 'Null' is not a subtype of type 'Future<void>'

Expected behavior
I was expecting to get a verification of the executed method
**Logs **
No issues found! (ran in 3.2s)
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.4 20F71 darwin-x64, locale de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.2)
[✓] Connected device (1 available)
• No issues found!

Should be exportNotes(any(named: 'bounds'))

Thanks 😊


API: make edugain export tag name configurable

In the PATCH API, when edugain_enabled is True, the API tags the entity with
hard-coded tag 'aaf-edugain-export'.
This name is specific to AAF.
Make the tag name configurable, with default being the current value.
Add template matching the current value to config/saml_service.yml.dist
Tested locally.  All rspec tests pass.

Rebased on develop  And added safe navigation to handle when the value is not defined in config.

Rebased on develop - Ruby 2.7.0 / #214

Rebased on develop - Ruby 2.7.0 / #216

Rebased on develop / #219 .  @bradleybeddoes , would you be able to review this?

@vladimir-mencl-eresearch we're not going to bring this into our tree currently, trying to maintain status quo as much as possible whilst we work through core tooling considerations internally.


Remove legacy tags_list field

Problem

The media models use an unnecessary legacy tags_list field.
Description

When the machine-generated tags were added, the data model for them changed from simple array of strings a list of ForeignKeys to a separate ImageTags table to an array of objects with properties such as provider and accuracy (only for machine-generated tags). The tags_list property was deprecated, but not removed from the database: https://github.com/cc-archive/cccatalog-api/pull/182
We should remove it.
Alternatives

We could also convert all tags to use simple string array since we are not really using machine-generated tags. But I think we will want to use them in the future, and removing them now to re-add later is an unnecessary complication.
Additional context

Implementation

[ ] 🙋 I would be interested in implementing this feature.

If we drop this from the Django models, will this need any change in the catalog or the ingestion server?

The catalog will not need to change anything because the tags column in the catalog is not changing. But the ingestion server will probably need to be updated.

Since the ingestion server makes no explicit reference to the columns and picks the overlapping ones, removing it from the API DB would be more than enough for the ingestion server to not copy it. I think this can be marked as ready for work then.


Broken link

link to "Migrate Azure AD Graph apps to Microsoft Graph" gives a 404

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

ID: 44d6245e-2ebc-c815-2d35-c29450062f3b
Version Independent ID: 98ead160-0377-d530-345f-1909e0039955
Content: Azure Active Directory Graph API
Content Source: articles/active-directory/develop/active-directory-graph-api.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@Chielus Thank you for pointing it out . We will investigate and update the thread.

@Chielus We have updated the link to the correct article and the changes will be updated in the next release cycle in 24-48 hours. We will now close this issue.


storybook component registration when using constant metadata export

Hi, we've recently kicked off a project to implement the code-connect for our design system. We have already been using the Storybook and thought it would be straight forward to implement the code-connect, but we ran into an issue with the component registration when using different export styles on our *.stories.tsx files
The anonymous default object literal export works seamlessly:
export default {
  argTypes: {},
  parameters: {
    design: {}
  }
}

but, when the default export is assigned to a constant, Storybook correctly includes the Figma embed, but the component fails to register in dev-mode:
// This configuration does not appear in dev mode
// There are no CLI errors or warnings, but Storybook displays the Figma embed.

const metadata: Meta<typeof Button> = {
  title: 'Button',
  component: Button,
  argTypes: {
    variant: {
      control: 'radio',
      options: ['primary', 'secondary', 'tertiary', 'danger'],
    }
  },
  parameters: {
    design: {
      type: 'figma',
      url: 'https://www.figma.com',
      examples: [Default],
      props: {
        variant: figma.enum('variant', {
          primary: 'primary',
          secondary: 'secondary',
          tertiary: 'tertiary',
          danger: 'danger',
        }),
      },
    },
  },
}

export default metadata

It seems like code-connect fails to recognize the component when the Storybook files deviate from a certain pattern, which seems like a restrictive limitation. Documenting this behavior could save time for others facing similar issues. Additionally, any insights into why this happens or potential fixes would be greatly appreciated, if there is anything we can do on our side?
our storybook dependencies:
"@storybook/addon-designs": "^8.0.0",
"storybook": "^8.0.8",

Yes, this would be super good, I also stumbled upon this. Anonymous default exports are not a good practice and also not what Storybook recommends. See: https://storybook.js.org/docs/writing-stories/typescript
We always write stories with TypeScript 4.9 syntax like mentioned in the Storybook docs.

Hey, thanks for the input on this! We're definitely aware that we don't support every Storybook syntax and so your feedback is really helpful. I think in this case, our parser isn't following the metadata reference – hopefully this is quite an easy fix. We'll take a look and get back to you once we have a solution.

This should be fixed in the latest release (0.1.2). Please reopen this issue if the problem persist.


Add release notes for July 9 release.

Codecov Report

Merging #380 into next will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             next     #380   +/-   ##
=======================================
  Coverage   39.77%   39.77%
=======================================
  Files          19       19
  Lines         636      636
  Branches       85       85
=======================================
  Hits          253      253
  Misses        381      381
  Partials        2        2


Rename on symbol in from foo import foo incorrectly updates module name

Environment data

Language Server version: 2023.3.31

Code Snippet
declare.py
def declare():
    return "success"

consume.py
from declare import declare

declare()

Repro Steps

Create files as above
Right-click on declare() call in consume.py and select Rename Symbol
Enter func as new name, press Enter.

Expected behavior
Within consume.py only the imported symbol name and the function call are modified.
from declare import func

func()

Actual behavior
Module name in import is also changed. Error on module name: "Import "func" could not be resolvedPylance (reportMissingImports)"
from func import func

func()

This issue has been fixed in prerelease version 2023.4.11, which we've just released. You can find the changelog here: CHANGELOG.md


Material Folders demo broken; easing function being rejected

In the Material folders demo,
keyframe-effect-constructor.js:128 Uncaught TypeError: Failed to execute 'animate' on 'Element': 'function (a){return a}' is not a valid value for easing
    at Object.b.newUnderlyingAnimationForKeyframeEffect (keyframe-effect-constructor.js:128)
    at b.Animation._rebuildUnderlyingAnimation (web-animations-next-animation.js:86)
    at b.Animation (web-animations-next-animation.js:35)
    at b.AnimationTimeline._play (timeline.js:48)
    at Object.b.newUnderlyingAnimationForGroup (group-constructors.js:189)
    at b.Animation._rebuildUnderlyingAnimation (web-animations-next-animation.js:90)
    at b.Animation (web-animations-next-animation.js:35)
    at b.AnimationTimeline._play (timeline.js:48)
    at b.AnimationTimeline.play (timeline.js:65)

Thanks for reporting this. Looks like the version of web-animations-js used needs to be updated to 2.1.5 or later.


Integration with a label indexing service

We're developing a service that would index all known target labels, and would lookup matching labels by a given a (partial) class name or a package name.
We want to integrate it with the plugin, providing code completion and adding matching targets to existing BUILD files.
To increase the chance of this being considered for wider adoption (we're eventually going to opensource this service/API), we need to make it all configurable (i.e. service URL, possible authentication).
We were thinking of adding a separate tab to the Bazel configuration UI in IntelliJ, and specify those features there, so they would be explicitly enabled by the user.
Do you think this is an acceptable proposal?

That sounds great! I like the idea of auto-complete suggestions based on partial package names.
I think it's something we'd like to support internally as well. My preference would be to pull out a very general extension point in the bazel plugin, without any implementation details (e.g. an interface with methods similar to:
List matchingTargets(String fragment);
For adding matching targets to existing BUILD files, there are also the (not yet combined) extension points SourceToTargetProvider and SourceToTargetFinder.

Where would an implementation (any implementation for that matter) sit?
On Thu, 7 Jun 2018 at 21:44 brendandouglas<EMAIL_ADDRESS>wrote:

That sounds great! I like the idea of auto-complete suggestions based on
partial package names.
I think it's something we'd like to support internally as well. My
preference would be to pull out a very general extension point in the bazel
plugin, without any implementation details (e.g. an interface with methods
similar to:
List matchingTargets(String fragment);
For adding matching targets to existing BUILD files, there are also the
(not yet combined) extension points SourceToTargetProvider and
SourceToTargetFinder.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/intellij/issues/335#issuecomment-395524615,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF0WRDV0mLsnK8_nnrcITEg_HsOPWks5t6XSagaJpZM4Uaw8E
.

Up to you -- it's easiest to put it in the bazel plugin, so that there are no versioning concerns. But a separate plugin depending on the bazel plugin would be fine to (assuming you wanted to put the extension point in the bazel plugin).

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.


Recording clips where front and back camera are shown simultaneously

Similar to BiCamera, BeReal, Instagram Dual Camera or Dual Camera.
Maybe these source codes can be used as inspiration:

https://github.com/zhoujinyan/Camera2Application
https://github.com/Arslanmajeed270/presuno
https://github.com/Mohit29061999/CameraApp

awesome idea


cla email invalid

I've got that

I can't see where I should verify my email.

This message says that there are some commits in your PullRequest which were done with another e-mail address than the one you have assigned to your profile. If you add the e-mail address (the invalid one) to your Profile then GitHub and CLA assistant will recognise you.

oh... moment, it looks like "invalid-email-adress" is a github user, isn't it? Could you provide a link to the PR?

https://github.com/wekan/wekan/pull/1003
I think you right... I forget to set a user.email in my git config -_-'

think, I rework my branch here https://help.github.com/articles/changing-author-info/ and certificate is validate

Maybe a better explicit message, or clicable something :/

normally there is a better message, assuming user has used a valid (but not assigned to his/her github profile) email address for the commit. We haven't had such constellation like yours so far.


Support flutter run on Android module project

Landing on red dashboard. The failing Cirrus job has been successfully re-run.

FYI @matthew-carroll @jamesderlin Support for flutter run on a Flutter module, Android part. Host app is auto-generated, depends on Flutter AAR module in the same way as in add2app scenarios, and remains hidden (sometimes described as an "ephemeral" host app).


without sudo or su?

Hi,
is there a way that we ask bundler to use another ssh account with sudo rights,
but run bundle install with another user?
example:
user1 owns the project,
but useradmin is the sudo user,
highly appreciate your tinker with this :)

Sure, SSH as useradmin, and then run sudo su user1 -c bundle install. You don’t need bundler to do this. :)

On May 7, 2015, at 7:21 PM, James<EMAIL_ADDRESS>wrote:
Hi,
is there a way that we ask bundler to use another ssh account with sudo rights,
but run bundle install with another user?
example:
user1 owns the project,
but useradmin is the sudo user,
highly appreciate your tinker with this :)
—
Reply to this email directly or view it on GitHub https://github.com/bundler/bundler/issues/3628.

it someone return
bash: bundle: command not found

but if i change 'bundle install' to 'ls', it works

That means you need to fix your environment, but this is a tracker just for bugs in Bundler. If you find a bug in Bundler, please let us know! But we can’t help you with server setup problems.

On May 7, 2015, at 7:42 PM, James<EMAIL_ADDRESS>wrote:
it someone return
bash: bundle: command not found
but if i change 'bundle install' to 'ls', it works
—
Reply to this email directly or view it on GitHub https://github.com/bundler/bundler/issues/3628#issuecomment-99973423.


cube: portability_subset demo (for review only)

DO NOT MERGE, FOR REVIEW ONLY!
Demonstrate using the portability_subset extension using the vkcube example.
This example code does little exception checking, in order to provide
opportunities for the portability validation layer to detect issues.
Also included is a verbatim local copy of vk_extx_portability_subset.h from the v0.2 release.
Change-Id: Ibe631782e92427cb8dc025d98d4bef6ff41092c7

This app is for exercising the portability validation layer, see https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/941

To be replaced


fix: use onPostBuild instead of onSuccess

Since we're running the Lighthouse audit after the site was built, it makes sense to have it run on onPostBuild.
Related to https://github.com/netlify/plugins/issues/134

:tada: This PR is included in version 1.4.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ARROW-4959:[C++][Gandiva][Crossbow] Gandiva crossbow packaging changes.

Supports building Gandiva in the manylinux docker image.
Fixes some issues discovered.
Move crossbow to build using manylinux docker image.
Use system dependencies to package Gandiva in OsX.

@kszucs could you please review this..i am not sure about the CI failure (i re-based from master and it still fails).

@kszucs @pravindra Could you please review. The CI failure is unrelated.

Could you rebase on the master?
We've rebased the master for 0.13.0 release.

Could you rebase on the master?
We've rebased the master for 0.13.0 release.

Sure rebased and pushed.

@praveenbingo could You paste a link for the crossbow tasks?

@kszucs sorry missed that. Here are the links
https://travis-ci.org/praveenbingo/arrow-build/builds/513370768
https://travis-ci.org/praveenbingo/arrow-build/builds/513370764

@kszucs @pravindra can you please review.

Latest crossbow builds
https://travis-ci.org/praveenbingo/arrow-build/builds/515556320
https://travis-ci.org/praveenbingo/arrow-build/builds/515556318

Codecov Report

Merging #4082 into master will increase coverage by 0.79%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #4082      +/-   ##
==========================================
+ Coverage   87.83%   88.62%   +0.79%
==========================================
  Files         739      604     -135
  Lines       90965    81301    -9664
  Branches     1252        0    -1252
==========================================
- Hits        79896    72057    -7839
+ Misses      10948     9244    -1704
+ Partials      121        0     -121

Impacted Files
Coverage Δ

.../src/gandiva/precompiled/extended_math_ops_test.cc
98% <100%> (+0.12%)
:arrow_up:

cpp/src/arrow/csv/column-builder.cc
95.32% <0%> (-1.76%)
:arrow_down:

cpp/src/arrow/util/thread-pool-test.cc
97.66% <0%> (-0.94%)
:arrow_down:

cpp/src/arrow/util/bpacking.h
99.81% <0%> (-0.01%)
:arrow_down:

go/arrow/math/uint64_amd64.go

go/arrow/memory/memory_avx2_amd64.go

js/src/enum.ts

go/arrow/array/builder.go

js/src/Arrow.node.ts

js/src/schema.ts

... and 129 more

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 1574b77...e5913de. Read the comment docs.


Angular 14 ng production build gives "the tensor should have 409600 values but has 5803"

When I try to run the angular 14 in debug build, I am able to scan the image and getting the proper image properties.
But, When I run in production build, We are getting the above error while parsing image.
Is there any different between prod/debug build ???
Kindly let us know.
We are using mobilnet_v2 for scanning the images.
Here is the full error message.
Based on the provided shape, [1,1,320,1280], the tensor should have 409600 values but has 5803

Any help here please

That's an interesting error.  I'm not familiar with any bug that should cause that :/

Thank you @GantMan for responding.
There are no errors at all, when the build is in Debug mode, but it's the error only we are facing in the release mode.
It would be great someone to shed some light into this. Or let me know if any pointers to debug this case.
Thank you.

You might want to check into the TensorFlow flags
https://www.tensorflow.org/js/guide/platform_environment#flags
&
https://github.com/infinitered/nsfwjs/tree/5ce2a0863db5e20c19cbe901b3454c8a7c16918a?tab=readme-ov-file#production
I don't know what could be changing because these are manual flags, though.

Thank you @GantMan for the directions.
Let me look into this and see why the release mode behaving a little different.


Chef Development Kit cannot execute without accepting the license

In the provided kitchen config... neither options seem to work.
provisioner:
  client_rb:
    chef_license: accept
  attributes:
    chef_license: accept

>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 3 actions failed.
>>>>>>     Failed to complete #converge action: [Expected process to exit with [0], but received '172'
---- Begin output of chef install /chef/effortless/effortless-infra-migration/Policyfile.rb ----
STDOUT: Chef Development Kit cannot execute without accepting the license
STDERR:
---- End output of chef install /chef/effortless/effortless-infra-migration/Policyfile.rb ----
Ran chef install /chef/effortless/effortless-infra-migration/Policyfile.rb returned 172] on managed-ubuntu-16-04-x64
>>>>>>     Failed to complete #converge action: [Expected process to exit with [0], but received '172'
---- Begin output of chef install /chef/effortless/effortless-infra-migration/Policyfile.rb ----
STDOUT: Chef Development Kit cannot execute without accepting the license
STDERR:
---- End output of chef install /chef/effortless/effortless-infra-migration/Policyfile.rb ----
Ran chef install /chef/effortless/effortless-infra-migration/Policyfile.rb returned 172] on managed-ubuntu-14-04-x64-do
>>>>>>     Failed to complete #converge action: [Expected process to exit with [0], but received '172'
---- Begin output of chef install /chef/effortless/effortless-infra-migration/Policyfile.rb ----
STDOUT: Chef Development Kit cannot execute without accepting the license
STDERR:
---- End output of chef install /chef/effortless/effortless-infra-migration/Policyfile.rb ----
Ran chef install /chef/effortless/effortless-infra-migration/Policyfile.rb returned 172] on managed-ubuntu-18-04-x64
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration```

This worked on the versions of Workstation prior to the license change.  I will have to follow up with the workstation team, and I will get back to you with possible resolutions.
In the meantime, please ensure that you're running the latest versions of Chef Workstation (0.5.1 at the time of this writing).

@esoterick would you execute chef env --chef-license accept on your workstation, and see if that resolves the issue?

@ncerny given the immaturity of code and documentation in this repo, we've chosen to go in another direction with our migration solution.  I'll close this and my other issues.

@esoterick looks like you found some of our ideation around our upgrade/migration strategy for customers but will have more official open repos with a more fully fleshed out approach from product and engineering shortly.


Email verification doesn't send. I can't login or change my password. Please help me

my email<EMAIL_ADDRESS>

hi @dmitrymailk, can you try again? our email provider had blocked your email because it caused a hard bounce in the past (meaning an email couldn't be delivered properly), I manually approved it.

Thank you. It's working. Love you so much ❤


MINIFI-294 Required vs. optional fields in config YAML

Long description of the changes in this commit can be found in the
JIRA for MINFI-294. Basically, better checks are now in place and
in the case of missing required fields, better error messaging.
This builds upon improvements made in MINIFI-275, and also
updates the config.yml exampe in the README.md file to match the
code.
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with MINIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE file?
[x] If applicable, have you updated the NOTICE file?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

reviewing

@kevdoran,
Changes look good.  Ran against some sample configs and things work as anticipated.  Thanks for correcting this!  Will get merged.

Cool, thanks @apiri. feel free to squash on merge


move tests directory into hkl so it does not install out of package

This change fixes #22, a ClobberError on installation.  Similar to https://github.com/pcdshub/typhos/pull/398/commits.

Thanks for the review.  This repo does need a minor overhaul.  Please add the new PR to the 0.3.15 milestone.

The PR is #34. I'll add it, thanks!


07/12/2018 01:49 : Create Pull Request for branch master -> prTesting1_2018071201

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.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.


feat: change output html option to more logical/consistent ID and re-order options

Summary
Enabling HTML output has nothing to do with "session"; so, changed the ID to results.html.enabled which makes more sense, follows pattern with results.html.style, and easier to extend to other results formats in the future. Also, I think it makes more sense for the connection profiles (and related certificates) to appear first, since that is usually the first thing you do when getting going with the extension.
Testing

Ensured the extension settings are now in the desired order. (Note: When you open the extension settings from the extension in the Extensions pane, it looks like the settings are in alphabetical order rather than the specified order. To see the specified order, type "sas" in the search field or select Extensions->SAS in the settings tab.)
Ensure the "HTML: Enabled" and "HTML: Style" settings still work as desired.

I'm not against this PR. It just brings a question about do we plan to set explicit order for all settings in future? Or do we only want to make the connectionProfiles and certificates first and leaving others in natural order unless a specific reason?

I'm not against this PR. It just brings a question about do we plan to set explicit order for all settings in future? Or do we only want to make the connectionProfiles and certificates first and leaving others in natural order unless a specific reason?

I think order should be considered. If options are related somehow, I'd certainly expect them to be adjacent, rather than appear in the order in which they were added.

The items order at Settings are shown as expected.


Please add to UK store

It's only available in US store

Noticed the same issue, Cabin is not available in UK itunes store.

Vanished from the NZ store, please return

Same for the Belgian itunes store

It's only available in US store

I can't find it in US app Store right now. Can you help me? thanks

Is there a plan to add it to UK store in near future?

Seems silly given that it’s literally a checkbox. Just... check the checkbox, no?


[#115404231] Remove collector

What
Remove collector
In our current deployment, collector is not configured to send metrics anywhere (even though it might seem so from logs, but historian has no targets configured). Also remove etcd_metrics_server, as that was sending etcd metrics to NATS for them to be picked up by collector.
How to review
Deploy to new/existing env. In existing env observe collector being deleted and etcd upgated. Check that there is no metrics job on etcd servers.
Who can review
not @mtekel

Deploy to new/existing env. In existing env observe collector being deleted and etcd upgated. Check that there is no metrics job on etcd servers.

Can you describe how the reviewer can verify that these components weren't configured/used?
I think it'd also be useful to reference this post on cf-dev which describes the intention to remove collector from cf-release and the linked spreadsheet which gives specifics about why it's no longer required:

<EMAIL_ADDRESS>

To check collector configuration:

check the manifest, properties for collector: should be empty
on collector server, check /var/vcap/jobs/collector/config/config.yml . Compare against https://github.com/cloudfoundry/cf-release/blob/v237/jobs/collector/templates/config.yml.erb
you can check historian code in the deployed collector: var/vcap/packages/collector/lib/collector/historian.rb (you can also note that it supports cfMetrics backend, but which can't be configured as it's missing in spec and config.erb template)

I'll update the commit messages.

I confirm that what @mtekel says is right, stats are not configured.
The code removes that vm and the job from etcd.

LGTM, letting tests to run and I will merge.

rebased with master

👍 👍


Georgy/fix rule unification

Closes #406

Make result indeterminate when trying to bind an already bound variable with a different expression. This was returning a failing result before, causing a soundness bug, because in some cases rules with duplicate variables in LHS would not be applied.
Make result indeterminate when unifying an injection with a variable. This allows us to get a clear remainder instead of a weird swapped substitution item
Only report violating substitution items

This may cause a lot of cases that were failing to become indeterminate now? Maybe we should post timing information here just in case.

Yes , running the performance measurement now with PYTEST_PARALLEL=3 with the hope for it to finish before the standup.

We seem to be getting a 2x slowdown on some of the Kontrol proofs (with PYTEST_PARALLEL=3):
| Test                                                     | georgy-fix-rule-unification time | master-e6752d1 time | (georgy-fix-rule-unification/master-e6752d1) time
|----------------------------------------------------------|----------------------------------|---------------------|---------------------------------------------------
| ArithmeticTest.test_max1(uint256,uint256)                | 71.29                            | 102.16              | 0.697826938136257
| StoreTest.testGasLoadColdVM()                            | 39.04                            | 54.32               | 0.7187039764359352
| SetUpDeployTest.test_extcodesize()                       | 97.02                            | 132.99              | 0.7295285359801488
| StoreTest.testGasLoadWarmUp()                            | 62.57                            | 84.06               | 0.744349274327861
| AllowChangesTest.testFailAllowChangesToStorage()         | 129.43                           | 149.32              | 0.8667961425127244
| AddrTest.test_addr_true()                                | 34.86                            | 36.98               | 0.942671714440238
| AssumeTest.test_assume_true(uint256,uint256)             | 37.81                            | 39.7                | 0.9523929471032746
| ArithmeticTest.test_max2(uint256,uint256)                | 75.58                            | 79.16               | 0.9547751389590703
| BlockParamsTest.testRoll(uint256)                        | 36.45                            | 38.14               | 0.9556895647614054
| AssertTest.testFail_assert_true()                        | 39.83                            | 41.63               | 0.9567619505164544
| AccountParamsTest.test_Nonce_NonExistentAddress()        | 52.86                            | 54.84               | 0.9638949671772428
| ExpectRevertTest.testFail_expectRevert_empty()           | 43.38                            | 41.66               | 1.0412866058569372
| AssertTest.test_assert_true_branch(uint256)              | 108.43                           | 79.63               | 1.3616727364058774
| AssertTest.test_assert_true()                            | 76.61                            | 54.41               | 1.4080132328616064
| ExpectRevertTest.testFail_expectRevert_multipleReverts() | 185.24                           | 125.23              | 1.4791982751736805
| ExpectRevertTest.test_expectRevert_true()                | 157.43                           | 98.7                | 1.5950354609929078
| PlainPrankTest.test_prank_zeroAddress_true()             | 305.59                           | 150.96              | 2.0243110757816636
| ExpectRevertTest.testFail_ExpectRevert_failAndSuccess()  | 204.75                           | 100.84              | 2.0304442681475603
| ExpectRevertTest.testFail_expectRevert_false()           | 205.9                            | 100.16              | 2.0557108626198084
| PlainPrankTest.test_startPrank_true()                    | 290.19                           | 133.78              | 2.169158319629242
| PlainPrankTest.test_startPrankWithOrigin_true()          | 307.25                           | 134.29              | 2.2879588949288854
| PlainPrankTest.test_startPrank_zeroAddress_true()        | 353.61                           | 140.75              | 2.5123268206039078
| ExpectRevertTest.test_ExpectRevert_increasedDepth()      | 423.25                           | 166.35              | 2.5443342350465885
| AssertTest.testFail_expect_revert()                      | 196.44                           | 70.31               | 2.793912672450576
| ExpectRevertTest.test_expectRevert_returnValue()         | 592.58                           | 142.26              | 4.165471671587235
| ExpectRevertTest.test_expectRevert_message()             | 553.48                           | 103.39              | 5.35332237160267
| TOTAL                                                    | 4680.870000000001                | 2456.02             | 1.9058761736467948

No significant difference in KEVM (ran with PYTEST_PARALLEL=1):
| Test                                     | georgy-fix-rule-unification time | master-e6752d1 time | (georgy-fix-rule-unification/master-e6752d1) time
|------------------------------------------|----------------------------------|---------------------|---------------------------------------------------
| mcd/dstoken-approve-fail-rough-spec.k    | 101.53                           | 108.03              | 0.9398315282791817
| benchmarks/ecrecover00-siginvalid-spec.k | 98.99                            | 105.12              | 0.9416856925418569
| erc20/ds/transferFrom-failure-1-a-spec.k | 99.22                            | 103.39              | 0.9596672792339684
| TOTAL                                    | 299.74                           | 316.54              | 0.9469261388766033