Is this extension still actively maintained?

Hello @vector-of-bool, @lygstate, @Randshot and possibly other contributors,
First of all, I would like to thank you for this nice extension!
Sorry for asking this annoying question, but there is a lot of issues reported here that I have also encountered and it seems like the last commit was 3 months ago and last release 5 months ago.
Is there still anyone actively maintaining this repository or is the help wanted from #315 still going on?

Wondering the same thing. I did contribute a few things last year and the author was quite active, but since January there doesn't seem to anything going on here :/

On @vector-of-bool patreon page there is a not that he is taking a break from OSS. I guess we will have to wait

Hey, as far as I know, @vector-of-bool is still looking for help for this extension.
I don't know about his current circumstances though. I wouldn't mind helping with maintaining this extension, but I don't have enough time to do that myself, and this also not being my project.
The problem is that some pretty big changes were started in separate branches from the maintainer and various contributors, but never finished, so I don't know which direction @vector-of-bool is envisioning.

Hi, thanks for the answers !
I perfectly understand that sometime people no longer have time/motivation for OSS and that's fine ! If there is any way to contact the author, maybe he could take a few minutes to explain how he envision the future of the addon, explain a bit what the big changes are/should be, and then give access to one or more trusted contributors ?
There's currently more than 680k installations of this addon, and it's the current "goto" addon for anyone working on C/C++ projects, so it would be nice if this addon could still be actively maintained :)

@Randshot you seem to have some rights on this repository; do you also have the rights to release a new version of the addon on the Visual Studio Code marketplace ?

Nope, that is completely separate.

Thought so, but wanted to be sure. Thanks

Hello, all.
I still get emails for everything that goes on in this repo, but I've been terrible about being active in the repo beyond that. I saw the email for this issue and feel like I should respond directly.
I feel pretty terrible about how much I've let this repo sit unattended for so long. Why has it sat? I'm not sure. After I changed positions at my job, I've been doing much less development work than I had before, and using CMake within VSCode has become rare for me simply by virtue of rarely doing C++ development. There is also a lot of time pressure as I'm active on several other projects at the moment. Add on some real-life time issues, and I'm fairly preoccupied.
I still have so many ideas of what I would like to do with this ext, but spouting them all immediately right now isn't prudent. With the release of CMake 3.14 and its new File API, as well as VSCode's upcoming custom task execution engine, I think it may be prudent for a refreshing of this extension (or possibly a new one :thinking:).
And @Randshot is correct: I am still looking for help with maintenance, up to and including handing off repository ownership (and possibly the VSCode Marketplace publication rights), but not to the extent that I want to become completely un-involved. (This will be tricky, though. You may recall a recent event in which handing off the publication rights of a popular project didn't go very well...)
I haven't yet sorted through the many, many, many backlog items that have gone unaddressed for months. I feel bad about being so inactive in here, and I can't promise that I'm yet ready to return, but I felt that I should at least follow-up on this ticket so that there isn't abject radio silence.
Thank you all for your patience.

I've created #691. Rationale and reasoning will be posted elsewhere soon.

I'm pleased to announce that this repository and extension has now been transferred to Microsoft, and I'm looking forward to see this code receive the attention that it deserves and that I have been unable to provide the past few months.
Thank you all for your tremendous patience!

A big thank you to @vector-of-bool for all of your hard work on this extension. 👏
In the coming days/weeks we will be spending time reviewing the existing issues and PR's and coming up with schedules for the work we plan to do with this extension. As always, community contributions are accepted and encouraged!


⚠ AsianCinema has degraded performance

In 7401930, AsianCinema ($ACM) experienced degraded performance:

HTTP code: 200
Response time: 10263 ms

Resolved: AsianCinema performance has improved in 6b7561f after 18 minutes.


Add additional illumos and Solaris constants

This adds some additional constants for fcntl(2) and setsockopt(3SOCKET).

r? @JohnTitor
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 0f8e3d054cffb198874242b21c194783df8a5ba2 has been approved by JohnTitor

:hourglass: Testing commit 0f8e3d054cffb198874242b21c194783df8a5ba2 with merge d8fc4b2d5c282595d814ccf2ff69d44accae6e19...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: JohnTitor
Pushing d8fc4b2d5c282595d814ccf2ff69d44accae6e19 to master...


Secrets in appSettings?

I thought KeyVault could be used to fill secrets into the appSettings of an App Service, but I don't see that mentioned here. Instead the secrets are being read from the code.
What is a best practice?

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

ID: 2cc0b77a-df21-7007-5cec-4399d98c6dc6
Version Independent ID: efe5ae5e-ff64-f1c7-6920-4512fc8f36d1
Content: Azure Key Vault Configuration Provider in ASP.NET Core
Content Source: aspnetcore/security/key-vault-configuration.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @guardrex
Microsoft Alias: riande

I meant https://docs.microsoft.com/en-us/aspnet/core/security/key-vault-configuration?view=aspnetcore-2.2

@hansmbakker Thank you for your query. The best practice is to read the secrets on the fly using REST API calls whenever needed .

@hansmbakker Are you working in ASP.NET Core or .NET Framework? The topic referenced only applies to ASP.NET Core (or an ASP.NET Core app that targets the .NET Framework). That topic doesn't apply to a traditional .NET Framework app.

As we have not received any further response from your side , we will be closing this thread. Should you have any further query on this, feel free to tag any of us and we will be happy to help .

@hansmbakker The Key Vault Configuration Provider and the Environment Variable Configuration provider run in parallel as two separate config providers in ASP.NET Core apps.
The Key Vault Configuration provider described in the linked topic reads the secrets from Key Vault directly into the app's configuration, not into the app's app settings. For more info on how configuration providers work in ASP.NET Core, see https://docs.microsoft.com/aspnet/core/fundamentals/configuration/.
Azure App Service's app settings are environment variables. IIRC when you store them as KEY-VALUE pairs in the portal, they are stored internally as APPSETTING_{KEY} and the VALUE. CreateDefaultBuilder (reference source) on the WebHost (see Program.cs of a new ASP.NET Core app created from the Web Application template) sets up the Environment Variable Configuration Provider. Such an app reads the App Services app settings into the app's configuration (the APPSETTING_ prefix used internally by Azure Apps is removed on the service side before the app receives them reference source).

@guardrex thank you for your additional explanation! I am using ASP.net core. I’ll look into it further and come back in case I have more questions.


zipline UnboundLocalError: local variable 'data' referenced before assignment

Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System: (Windows Version
Python Version:  3.4 (separately download with conda
Python Bitness: $ python -c 'import math, sys;print(int(math.log(sys.maxsize + 1, 2) + 1))'
How did you install Zipline: conda install
Python packages:  conda list`

Now that you know a little about me, let me tell you about the issue I am
having:
first my problem is that my Jupyter QTConsole (version python 3.4) doesn't work.
i create py34 wiht
conda create -n py34 python=3.4 anaconda
however whenever clicking Jupyter QTConsole, nothing happen. aslo IPython too.
anyway, I perform my coding in anaconda prompt (py34)
install zipline with
conda install zipline
but, whenever import zipline, I get error like this
[
C:\Users\Administrator\AppData\Local\conda\conda\envs\py34\lib\site-packages\pandas\tseries\index.py:755: PerformanceWarning: Non-vectorized DateOffset being applied to Series or DatetimeIndex
PerformanceWarning)
C:\Users\Administrator\AppData\Local\conda\conda\envs\py34\lib\site-packages\pandas\tseries\index.py:755: PerformanceWarning: Non-vectorized DateOffset being applied to Series or DatetimeIndex
PerformanceWarning)
C:\Users\Administrator\AppData\Local\conda\conda\envs\py34\lib\site-packages\pandas\tseries\index.py:755: PerformanceWarning: Non-vectorized DateOffset being applied to Series or DatetimeIndex
PerformanceWarning)
]
although error, coding can run. so I scrap tutorial code. but I take error
[
Traceback (most recent call last):
File "E:/workspace/zip.py", line 23, in
algo = TradingAlgorithm(Iinitialize=initialize, handle_data=handle_data)
File "C:\Users\Administrator\AppData\Local\conda\conda\envs\py34\lib\site-packages\zipline\algorithm.py", line 269, in init
self.trading_environment = TradingEnvironment()
File "C:\Users\Administrator\AppData\Local\conda\conda\envs\py34\lib\site-packages\zipline\finance\trading.py", line 96, in init
self.bm_symbol,
File "C:\Users\Administrator\AppData\Local\conda\conda\envs\py34\lib\site-packages\zipline\data\loader.py", line 165, in load_market_data
trading_day,
File "C:\Users\Administrator\AppData\Local\conda\conda\envs\py34\lib\site-packages\zipline\data\loader.py", line 253, in ensure_benchmark_data
if not has_data_for_dates(data, first_date, last_date):
UnboundLocalError: local variable 'data' referenced before assignment
]
my coding is here
[
import pandas_datareader.data as web
from zipline.api import order, record, symbol
from zipline.algorithm import TradingAlgorithm
data = web.DataReader("AAPL", "google")
data = data[['Close']]
data.columns = ["AAPL"]
data = data.tz_localize('UTC')
def initialize(context):
context.sym = "AAPL"
context.i = 0
def handle_data(context):
order(context.sym, 10)
context.i += 1
algo = TradingAlgorithm(Iinitialize=initialize, handle_data=handle_data)
result = algo.run(data)
print(result)
]
what should I do??
please help me. errors hurting me
Sincerely,
$ whoami

Hi @mongeoroo , That error is https://github.com/quantopian/zipline/issues/1506 and is masking failure to download the benchmark.
The fix for the exact error you're seeing was released some months ago, if you want to start by updating to the latest version of zipline. Then you/we might have more information about why the benchmark isn't downloading.

I'm hitting the same error, but on macOS. Is there any way to install a newer version of zipline (above 1.0.2) using something other than pip, which is giving me trouble? Thanks.

@ShadoFlameX , You could clone the repo locally and build the c extensions in place manually.

Going to close this due to inactivity/no response from OP. Feel free to re-open if you have further issues 🙂


New year, new argument parser!

I talked about this a bit on Discord, but I think it's time to actually start talking about a new library I've been working on. So here goes: introducing the very creatively named uutils-args, a derive-based argument parsing library.
Why a custom argument parser
For a while now, we've been using clap as our argument parser, but over time I've been become increasingly frustrated with it. Not because it's a bad library, but because it doesn't fit the very specific needs of the coreutils and we constantly have to work around clap with a lot of verbose code. I looked into basically every Rust argument parser out there and none really fit our needs. So about a month ago, I started working on a parser based on lexopt specifically for uutils.
The whole design is too complex to explain here, so I wrote some documents in the repo. It has three subpages:

an overview of all argument types in coreutils
a page listing problems we ran into with clap
and how uutils-args works.

The library also integrates very nicely with some of the plans I had earlier for the --help pages (https://github.com/uutils/coreutils/issues/3181, https://github.com/uutils/coreutils/issues/2816), because the help text is read as markdown from a file in this library.
Current Status
The library supports many utils already, but a few important features are still missing. Some low-hanging fruit:

The deprecated arguments for head, tail and uniq,
~Hidden arguments,~
~Setting exit codes.~

And more complicated:

better and more complete markdown rendering,
argument completion.

There are also rough edges that can be smoothed out like improving the error messages and the output of --help.
It is also very much a product of me working on it alone, which means that most of the naming conventions make sense to me but maybe not to others. I would very much welcome feedback on any part of the API.
If you want to see the library in action, I suggest to take a look at some of the coreutils for which I have created tests (more to come in the future):

basename
cat
mktemp
ls

A full list is here: https://github.com/tertsdiepraam/uutils-args/tree/main/tests/coreutils. I found that most are relatively easy to port.
Downsides
Porting to this new library will have a few downsides.

New contributors won't be familiar with this library.
We won't have argument completion (until we implement ourselves in this library)
We'll have to update uudoc.
We don't get all the features and years of iterative improvement that clap has.

Proposed roadmap
Of course, I'm aware that this is gonna be a huge effort to port and we should carefully how (and even if) we want to do that. For now, I've come up with the following steps:

[ ] Figure out whether the migration is going to be worth it.
[ ] Collect feedback and accept PRs to get the library ready for use in uutils. This includes

Reevaluating the names for crates, traits and functions.
Implementing missing features.
Adding more documentation.
Stabilize the API.
Add more coreutils APIs as tests to prove the feasibility of the library.

[ ] Fix up administration

[ ] Move the repo to the uutils organisation
[ ] Publish the crates in the repo

[ ] Port utils one by one[^1]
[ ] Change uudoc to use the info from the new library.

How to help out
For now, I need lots of feedback on this library, so I can get it ready, feel free to open an issue with whatever feedback you have or comment below. You can also help by picking up any of the open issues.
I'd be happy to answer any questions about this library :)
cc @sylvestre, @rivy, @jfinkels
[^1]: I think this is possible by having clap and this new library coexist in the repo for a while, though it will break completion and the online docs.

Interesting :)
but I am a bit worried that we end up reinventing the wheel.
Did you try to:

ask clap developer if they would be willing to take some patches?
if we could write a clap extension for this?

@tertsdiepraam , I'd love to have improvements in command line arguments support.
Your contributions have always been great and I'm happy to support your further experiments.
I would suggest that, if you decide to embark on this project, it should be built and developed in another repo and as it's own crate. We can set it up as a repo under the uutils banner.
I can understand @sylvestre's concern about duplication of effort and reinvention, but I empathize strongly with your position. I've contributed to clap a few times, and it's become a bit of a beast. I quite understand the "replace it" feeling that you are experiencing. 😄

yeah, we should probably do it :)
I just want to make sure that we have really discussed about it

This sounds like a reasonable change to me, I've run into quite a few issues with argument parsing. So if we can make it easier to deal with silliness like
chmod u=rrrr+-+-+-www f

or
df --o

without too much effort, that would be great.

What's the silliness you're referring to? Is it about parsing the permissions and  non-ambiguous prefixes of long arguments? I have the second one implemented, but the first one will probably not be part of this library. You can define a type that implements a parser that will work though.

Yes, I was referring to parsing the permissions and non-ambiguous prefixes of long arguments. They were just two things that came to mind when I tried to recall trouble I had had with arguments in the past.

I've resumed my work on this. I think the next step is determining when we deem it feature-complete and battle-tested enough to be included here.
Here's what I have right now:

Short args (with no, optional and required arguments)
Long args (with no, optional and required arguments)
Positional arguments
--help and --version
Help text based on an external file
Help text based on docstrings
dd-style args
A special parsing mode for echo
An escape hatch for arguments like -10/+10 like fold
Error messages on invalid arguments
Parsing of values with a derive macro
Control over the exit code on errors

What's missing is:

Making the errors more informative and pretty (e.g. add hints for typos)
Generate docs, completions, and manpages (https://github.com/tertsdiepraam/uutils-args/issues/5, https://github.com/tertsdiepraam/uutils-args/issues/4)
A good design for composing multiple definitions of arguments (https://github.com/tertsdiepraam/uutils-args/issues/21).
Everything that I've missed in my research (even though the research was pretty extensive)

The problem is that there's only so much I can do in a separate repo. We have to start properly integrating this if we want to find the rest of the actual problems.
There's also the issue that while we are migrating, the docs and manpages will probably be broken anyway, because we will temporarily have both clap and this parser in the repo. Unless we only work on a separate branch, but that seems suboptimal too. Happy to hear any suggestions for how we should deal with this. My solution is that we generate the manpages and docs, store them and then remove the code that generates it. That will give people a snapshot that will be pretty accurate for a while.

Looks like I accidentally stumbled into another clap-impossibility: unattached multi-valued short-args, which clap would prefer not to fix, and I honestly agree that it's a silly feature that should have never been invented in the first place.
However, with clap it is impossible to implement shuf -ez hello world correctly.

That might be where I definitively draw the line of compatibility 😄 Holy cow, that's cursed.

I think it's pretty doable with uutil-args. If I get it to work, would you be interested, or is that too cursed?
More cursed stuff …
$ echo foo > a; echo bar > b
$ shuf a b
shuf: extra operand 'b'
Try 'shuf --help' for more information.
[$? = 1]
$ shuf a b -e # A *later* argv string changes the interpretation of an *earlier* argv!
b
a
$

Actually, I think this is because --echo does not take any arguments. So, it should be possible in both clap and the new parser.
Sort of related, I think we should also put some guidance in CONTRIBUTING.md about filing issues on our behalf.  Especially with clap, we've had people file issues a few times without communicating with the uutils maintainers and I don't want Ed Page to get annoyed with us [^1] 😅
[^1]: Of course, he's been awesome about this and always provided clear and detailed responses.

According to the GNU documentation, --echo does take arguments, and shuf a b proves that, kinda. But yes, I would implement it as a boolean flag, and then later error out if more than one "file" was supplied. Sorry, I'm getting off-topic.
I tried to keep the clap issue reasonably general, and in retrospect I agree that perhaps it would have been better to coordinate with you. Thankfully, nothing bad happened this time. :)

Where do you see that --echotakes arguments? In the manpage it says

treat each ARG as an input line

with ARG referring to this line:

shuf -e [OPTION]... [ARG]...

and in the docs it says

Treat each command-line operand as an input line.

So I think it's just a boolean.

Here's another behavior that is impossible to replicate using clap:
$ date -Ilolwut -R -R  # parses "lolwut" before either "-R", and raises that error
date: invalid argument 'lolwut' for '--iso-8601'
Valid arguments are:
  - 'hours'
  - 'minutes'
  - 'date'
  - 'seconds'
  - 'ns'
Try 'date --help' for more information.
[$? = 1]
$ date -R -R -Ilolwut  # parses the second "-R" before "-Ilolwut", and raises that error
date: multiple output formats specified
[$? = 1]
$ date -R -Ilolwut -R  # In fact, it first tries to parse the value of "-i" before noticing duplicity
date: invalid argument 'lolwut' for '--iso-8601'
Valid arguments are:
  - 'hours'
  - 'minutes'
  - 'date'
  - 'seconds'
  - 'ns'
Try 'date --help' for more information.
[$? = 1]
$ date -R -Idate -R  # … so if the value to "-I" is valid, it notices the duplicity only afterwards.
date: multiple output formats specified
[$? = 1]

I'll implement a proof-of-concept in uutils-args soon, I think is easy to replicate there.

From your examples, it seems like the parsing is just handled sequentially in order, terminating at the first error. Is that right?

@jfinkels: Yes, hence my proposal to implement it like this: https://github.com/uutils/uutils-args/pull/113


Always use Using Blocks

These are poor programming practices that can break a production system.  You should be using "Using" blocks, so you can close your connections.
Wrong:
"var blogs = context.Blogs
.FromSqlRaw("SELECT * FROM dbo.Blogs")
.ToList();"
Correct:
var blogs;
Using (var db = new context() )  {
blogs = db.Blogs.FromSqlRaw("SELECT * FROM dbo.Blogs").ToList();
}

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

ID: 7e1289d5-8364-18a4-3445-6bba05c6854b
Version Independent ID: 2680e647-f64a-7991-f821-3b5e2a845960
Content: Raw SQL Queries - EF Core
Content Source: entity-framework/core/querying/raw-sql.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @smitpatel
Microsoft Alias: avickers

The sample code contains many "using" statements: https://github.com/dotnet/EntityFramework.Docs/tree/main/samples/core/Querying/RawSQL

Ok. I reviewed the sample code.  The sample code always has "using" statements and is top-notch.  Great stuff.
The page does not list these; the page is technically correct, but I see programmers googling this stuff and using these commands as is, and breaking their programs.
https://docs.microsoft.com/en-us/ef/core/querying/raw-sql?fbclid=IwAR03RuV8sCbVhGXcoZpLj_hZPPBbqgw9qNI2MzrAeabgY22B8EpII7xFJCE


Several bug fix to call SHAP from EconML

Hi, I created a PR solving issues I found when implemented SHAP functionalities into EconML #1620 , please take a look and we reply on those changes to make it work calling from EconML.
Also I have another issue didn't solve through this PR, when I have a Explanation object and I reset the feature_names as a list, it can't be correctly passed through when call slicing, the way to make it work correctly is to reset as an alias of list Alias(list of new feature_names, dimension), could you please handle that internally?
est=LinearRegression()
est.fit(x,y)
explainer=shap.Explainer(est,x[:10],feature_names=["a","b","c","d"])
shap_values=explainer(x[:10])
# change feature names
shap_values.feature_names=["a","b","c"]
# new feature name won't pass through when slicing
print(shap_values.feature_names)
print(shap_values[1].feature_names)

Thanks @heimengqi ! I also ran into the same slicing issue and thought Harsha and Sam fixed it on the InterpretML/slicer side, but I'll check into it and see if it is a different issue or something that is not yet pushed.

Thanks @slundberg ! I currently have a solution by reset .feature_names as of Alias instead of a list, so it's not a blocker from our side. But please keep me posted if you could finally handle that internally, then I will update my code.

Harsha just pushed support for this to slicer: https://github.com/interpretml/slicer/commit/08cc7d23eeb55fb1b0e3faa1c30c46e26d9ee157
So once it is tested with SHAP we can start getting it into tagged releases


Refactor webhook/websocket worker.

Currently the webhook/websocket worker is spread out over several django models.  This makes maintaining it un-necessarily difficult.  It also makes tracking the connection status more difficult.  Refactor the worker to be its own django app with a connection model.  By adding an event subscription model, the user can toggle on/off events that they do or do not want to subscribe to.

[x] Create new TwitchConnection app
[x] Add EventSubscription model with a unique event_type field.  Thus there can be 1 instance of an EventSubscription model for each EventType.
[x] Use the TwitchConnectionConfig AppConfig class to ensure that there is an EventSubscription created for each EventType.  This will let us easily add new event types in the future.  Newly created EventSubscription instances should have their disabled field set to True
[x] Create a UI to allow the user to turn off/on subscriptions to event types.
[x] Add websocket connection to inform clients which events are subscribed to.

Fully implemented in PR #81


DNM: example: asdf for local tooling

Do not merge

This PR serves as an example of how we could make use of asdf as a way of keeping our local tooling in sync and up-to-date.
asdf

Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more

About
Why?
We keep seeing troubles among engineers which are caused by outdated or different versions of our tooling. We could keep them in sync by using different solutions, asdf is one of them.
My evaluation
Pros:

installation and usage is fairly easy

as well as maintenance (hopefully :crossed_fingers: )

it only applies to the wbaas-deploy tree: outside of that dir structure system fallbacks are used (e.g. the versions of the tools that you installed in some other way)
it's entirely optional: even if you don't opt-in to use this, we could use the .tool-versions file as a way of documenting which versions we expect people are using

Cons:

Yet another tool and complexity

my added bash scripts aren't ideal IMO

Reliance/dependance on community driven binary sources
Even if the system fallbacks are used (e.g. you are outside the wbaas-deploy tree), asdf shims are getting called - potential error source?

How to

Download and install asdf

For example by

running git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch v0.12.0
and (for example) adding this to ~/.profile:

export ASDF_DIR="$HOME/.asdf"
. "$HOME/.asdf/asdf.sh"

Run make asdf-install to add plugins ("package sources") and installing the tools

This does three things:

adding tool "plugins" (basically the package sources)
installs the tools with the current versions defined in .tool-versions
sets a system fallback for the tools outside of wbaas-deploy (this touches ~/.tool-versions)

Run the tools (helmfile version, minikube version, etc.)

tip: asdf which <toolname> show you which binary the shim is calling at the moment:

deer@C352 ~/wbaas/wbaas-deploy $ asdf which helmfile
/home/deer/.asdf/installs/helmfile/0.153.1/bin/helmfile
deer@C352 ~/wbaas/wbaas-deploy $ cd
deer@C352 ~ $ asdf which helmfile
/home/deer/.local/bin/helmfile

Looks great! Did you try but struggle with gcloud / the google GKE auth plugin?

Looks great! Did you try but struggle with gcloud / the google GKE auth plugin?

Hm everything seems to work fine for me actually. Did you see troubles like that?

I didn't even try! I just noticed no entries for either of them in https://github.com/wmde/wbaas-deploy/pull/1030/files#diff-751af1a340658c7b8176fe32d7db9fadbe15d1d075daba1919a91df04155bc70

Now I get it! totally forgot about that tool as I don't use it very often, will look into it


Error - HoloLensWorldManager failed to return a world coordinate system!

Overview
I get the error down below when I play my scene.
Expected Behavior
Preferably this should not occur.
Actual Behavior
Full error
HoloLensWorldManager failed to return a world coordinate system!
UnityEngine.XR.WSA.SurfaceObserver:SetVolumeAsAxisAlignedBox(Vector3, Vector3)
Microsoft.MixedReality.Toolkit.WindowsMixedReality.SpatialAwareness.WindowsMixedRealitySpatialMeshObserver:ConfigureObserverVolume() (at Assets/MixedRealityToolkit.Providers/WindowsMixedReality/WindowsMixedRealitySpatialMeshObserver.cs:523)
Microsoft.MixedReality.Toolkit.WindowsMixedReality.SpatialAwareness.WindowsMixedRealitySpatialMeshObserver:CreateObserver() (at Assets/MixedRealityToolkit.Providers/WindowsMixedReality/WindowsMixedRealitySpatialMeshObserver.cs:300)
Microsoft.MixedReality.Toolkit.WindowsMixedReality.SpatialAwareness.WindowsMixedRealitySpatialMeshObserver:Initialize() (at Assets/MixedRealityToolkit.Providers/WindowsMixedReality/WindowsMixedRealitySpatialMeshObserver.cs:82)
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:RegisterServiceInternal(Type, IMixedRealityService) (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:842)
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:RegisterServiceInternal(IMixedRealitySpatialAwarenessObserver) (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:858)
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:RegisterService(Type, SupportedPlatforms, Object[]) (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:199)
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:RegisterDataProvider(Type, SupportedPlatforms, Object[]) (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:280)
Microsoft.MixedReality.Toolkit.SpatialAwareness.MixedRealitySpatialAwarenessSystem:Enable() (at Assets/MixedRealityToolkit.Services/SpatialAwarenessSystem/MixedRealitySpatialAwarenessSystem.cs:85)
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:EnableAllServices() (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:973)
Microsoft.MixedReality.Toolkit.MixedRealityToolkit:OnEnable() (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:772)
The error ticks while the scene is being played

Steps to reproduce
This is the scene hierarchy

There is also an ARCamera for my script (which is on the main camera) to handle.
How the game scene looks like

Unity Editor Version
2019.1.0f2
Mixed Reality Toolkit Release
MRTK v2 RC1

The warnings full text

https://stackoverflow.com/questions/55830143/hololensworldmanager-failed-error-when-using-the-mrtk-v2-rc1

The link above result in Page not Found.
RC1 does not support Unity 2019.1. If you need 2019.1 you may have to wait for RC1 refresh this week.
Closing this issue. please reopen if you see this after we release RC1 Refresh!

Hi there,
I am running the examples through 2019.1 using the RC1 refresh and I have encountered this same issue when previewing.
After a bit of debugging, I have pinned it down to changing platform to UWP. After doing this I get the error. If I switch back to PC Mac & Linux standalone I no longer get the error when previewing.
Let me know if you would prefer a new issue - just found this one when searching - cheers!
HoloLensWorldManager failed to return a world coordinate system! UnityEngine.XR.WSA.SurfaceObserver:SetVolumeAsAxisAlignedBox(Vector3, Vector3) Microsoft.MixedReality.Toolkit.WindowsMixedReality.SpatialAwareness.WindowsMixedRealitySpatialMeshObserver:ConfigureObserverVolume() (at Assets/MixedRealityToolkit.Providers/WindowsMixedReality/WindowsMixedRealitySpatialMeshObserver.cs:523) Microsoft.MixedReality.Toolkit.WindowsMixedReality.SpatialAwareness.WindowsMixedRealitySpatialMeshObserver:UpdateObserver() (at Assets/MixedRealityToolkit.Providers/WindowsMixedReality/WindowsMixedRealitySpatialMeshObserver.cs:408) Microsoft.MixedReality.Toolkit.WindowsMixedReality.SpatialAwareness.WindowsMixedRealitySpatialMeshObserver:Update() (at Assets/MixedRealityToolkit.Providers/WindowsMixedReality/WindowsMixedRealitySpatialMeshObserver.cs:104) Microsoft.MixedReality.Toolkit.<>c:<UpdateAllServices>b__65_0(IMixedRealityService) (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:959) Microsoft.MixedReality.Toolkit.MixedRealityToolkit:ExecuteOnAllServices(Action`1) (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:1009) Microsoft.MixedReality.Toolkit.MixedRealityToolkit:UpdateAllServices() (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:959) Microsoft.MixedReality.Toolkit.MixedRealityToolkit:Update() (at Assets/MixedRealityToolkit/Services/MixedRealityToolkit.cs:792)

Pretty sure this is a Unity bug with the Observer.
I'd double check to make sure you have the latest 1.0.9 Windows Mixed Reality Package installed in the Unity Package Manager.

@wassx probably relates to your bug report on the fork as well.

Pretty sure this is a Unity bug with the Observer.
I'd double check to make sure you have the latest 1.0.9 Windows Mixed Reality Package installed in the Unity Package Manager.

@StephenHodgson definitely have 1.0.9 installed. Should I be logging an issue with Unity? Not that I can currently find the place to do so.

Yeah I think this is a bug with 2019+ (Is that the version you're using as well?)

Yeah I think this is a bug with 2019+ (Is that the version you're using as well?)

Yep 2019.1 - thanks for the help - will report :D

@StephenHodgson ah thx for the hint!
@handyjellyfish do you have a link to the filed unity issue please?

@StephenHodgson ah thx for the hint!
@handyjellyfish do you have a link to the filed unity issue please?

Have just submitted it - will let you know as soon as I have more info :)

https://fogbugz.unity3d.com/default.asp?1153049_2d4gcjera1n04qou

@handyjellyfish might be best to send them a repro that doesn't include the MRTK.
They'll be able to rule it out easier.
a min repro is good.

` private void ConfigureObserverVolume()
{
// Update the observer
switch(ObserverVolumeType)
{
#if !UNITY_EDITOR
case VolumeType.AxisAlignedCube:
observer.SetVolumeAsAxisAlignedBox(ObserverOrigin, ObservationExtents);
break;
            case VolumeType.Sphere:
                // We use the x value of the extents as the sphere radius
                observer.SetVolumeAsSphere(ObserverOrigin, ObservationExtents.x);
                break;

            case VolumeType.UserAlignedCube:
                observer.SetVolumeAsOrientedBox(ObserverOrigin, ObservationExtents, ObserverRotation);
                break;

            default:
                Debug.LogError($"Unsupported ObserverVolumeType value {ObserverVolumeType}");
                break;
        #endif
        }
    }

`
I ran into this issue and I lust put a platform parameter (#if !UNITY_EDITOR) around the part that throws the error like seen in the code snippet above.
(Just a quick and dirty hotfix)

I am getting this error now when implementing the XRTK v 01.15

HoloLensWorldManager failed to return a world coordinate system!
UnityEngine.XR.WSA.SurfaceObserver:SetVolumeAsAxisAlignedBox(Vector3, Vector3)
XRTK.WindowsMixedReality.SpatialObservers.WindowsMixedRealitySpatialMeshObserver:ConfigureObserverVolume(Vector3, Vector3) (at Library/PackageCache/com.xrtk.wmr@40f707ba94f5b34d8969246ee980dbe9c3b8ff31/SpatialObservers/WindowsMixedRealitySpatialMeshObserver.cs:131)
XRTK.WindowsMixedReality.SpatialObservers.WindowsMixedRealitySpatialMeshObserver:Update() (at Library/PackageCache/com.xrtk.wmr@40f707ba94f5b34d8969246ee980dbe9c3b8ff31/SpatialObservers/WindowsMixedRealitySpatialMeshObserver.cs:68)
XRTK.Services.MixedRealityToolkit:UpdateAllServices() (at Library/PackageCache/com.xrtk.core@838e59081c1adc5ea07281f243561186c034f127/Services/MixedRealityToolkit.cs:1284)
XRTK.Services.MixedRealityToolkit:Update() (at Library/PackageCache/com.xrtk.core@838e59081c1adc5ea07281f243561186c034f127/Services/MixedRealityToolkit.cs:705)>

Would this cause Unity to not open application in MixedReality window?


[Bug] No such file or directory: '00000001.png'

Prerequisite

[X] I have searched Issues and Discussions but cannot get the expected help.
[X] I have read the FAQ documentation but cannot get the expected help.
[X] The bug has not been fixed in the latest version (master) or latest version (1.x).

Task
I'm using the official example scripts/configs for the officially supported tasks/models/datasets.
Branch
1.x branch https://github.com/open-mmlab/mmediting/tree/1.x
Environment
mmcv 2.0.0rc4
mmedit 1.0.0rc6
Reproduces the problem - code sample
python demo/restoration_video_demo.py \
    configs/real_basicvsr/realbasicvsr_wogan-c64b20-2x30x8_8xb2-lr1e-4-300k_reds.py \
    https://download.openmmlab.com/mmediting/restorers/real_basicvsr/realbasicvsr_wogan_c64b20_2x30x8_lr1e-4_300k_reds_20211027-0e2ff207.pth \
    data/video/ \
    data/output \
    --start-idx=1

Reproduces the problem - command or script
python demo/restoration_video_demo.py \
    configs/real_basicvsr/realbasicvsr_wogan-c64b20-2x30x8_8xb2-lr1e-4-300k_reds.py \
    https://download.openmmlab.com/mmediting/restorers/real_basicvsr/realbasicvsr_wogan_c64b20_2x30x8_lr1e-4_300k_reds_20211027-0e2ff207.pth \
    data/video/ \
    data/output \
    --start-idx=1

Reproduces the problem - error message
03/24 02:18:56 - mmengine - INFO - Loads checkpoint by http backend from path: https://download.openmmlab.com/mmediting/restorers/basicvsr/spynet_20210409-c6c1bd09.pth
Loads checkpoint by http backend from path: https://download.openmmlab.com/mmediting/restorers/real_basicvsr/realbasicvsr_wogan_c64b20_2x30x8_lr1e-4_300k_reds_20211027-0e2ff207.pth
The model and loaded state dict do not match exactly

unexpected key in source state_dict: step_counter

Traceback (most recent call last):
  File "demo/restoration_video_demo.py", line 89, in <module>
    main()
  File "demo/restoration_video_demo.py", line 65, in main
    output = restoration_video_inference(model, args.input_dir,
  File "/home/win/mmediting/mmedit/apis/inferencers/inference_functions.py", line 618, in restoration_video_inference
    data = test_pipeline(data)
  File "/home/win/anaconda3/envs/mmedit/lib/python3.8/site-packages/mmengine/dataset/base_dataset.py", line 59, in __call__
    data = t(data)
  File "/home/win/anaconda3/envs/mmedit/lib/python3.8/site-packages/mmcv/transforms/base.py", line 12, in __call__
    return self.transform(results)
  File "/home/win/mmediting/mmedit/datasets/transforms/loading.py", line 107, in transform
    img = self._load_image(filename)
  File "/home/win/mmediting/mmedit/datasets/transforms/loading.py", line 148, in _load_image
    img_bytes = self.file_backend.get(filename)
  File "/home/win/anaconda3/envs/mmedit/lib/python3.8/site-packages/mmengine/fileio/backends/local_backend.py", line 33, in get
    with open(filepath, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: '00000001.png'

Additional information
Hello, everyone!
I'm trying to use super resolution for video, with pre-trained models, using the commands from the documentation
I'm entering the command exactly as it's described in the documentation, but I get a message saying that I can't find the file 00000001.png, even though I know for a fact that it is at the path $MMEDITING/data/video/00000001.png I specified
When I run restoration_video_demo.py, I specify this path as data/video/ in the arguments, but I expect this is correct because it is shown in the example.
I don't understand what I'm doing wrong.

Hi, this Pull Request will fix this bug. @windoozatnick


[1pt] Feature add user Admin to handle add & remove vehicles, review csrf auth tokens

Feature add user Admin to handle add & remove vehicles.


Could data augmentation improve the clustering?

SpCL is amazing project. You use Unified Contrastive Learning as loss function, which is different from SimCLR. But I find that the transformer don't use any data augmentation as SimCLR when I read the code of SpCl. I wonder whether the data augmentation (just like SimCLR or MoCo V2) could improve the clustering. For example, the centroids of  data augmentation's feature outputs  became a  Cluster Centroids instead of Outlier Instance Features.

Sorry. I found transforms has done the work and got  the meaning of Outlier Instance Features.


Update triton version to 3.1.0 for release  2.5.0

closing will reopen with checkout from proper branch


rclone aws fuse wont upload data

When filing an issue, please include the following information if
possible as well as a description of the problem.  Make sure you are
using the latest version of rclone.

What is your rclone version (eg output from rclone -V)
rclone v1.33

Which OS you are using and how many bits (eg Windows 7, 64 bit)
centos 7

Which cloud storage system are you using? (eg Google Drive)
Amazon Cloud Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)
./rclone mount amazon:/ ~/rclone-v1.33-linux-amd64/mnt/ --debug-fuse -v

A log from the command with the -v flag (eg output from rclone -v copy /tmp remote:tmp)
2016/09/01 01:39:00 &{0xc420192730 TestData/README.html}: Error detected after finished upload - waiting to see if object was uploaded correctly: Post https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication: http: ContentLength=436 with Body length 187028
2016/09/01 01:39:00 &{0xc420192730 TestData/README.html}: Object not found - waiting (1/24)
2016/09/01 01:39:00 fuse: <- Interrupt [ID=0xe Node=0x0 Uid=0 Gid=0 Pid=0] ID 0xd
2016/09/01 01:39:00 fuse: -> [ID=0xe] Interrupt
2016/09/01 01:39:05 &{0xc420192730 TestData/README.html}: Object not found - waiting (2/24)
2016/09/01 01:39:10 &{0xc420192730 TestData/README.html}: Object not found - waiting (3/24)
2016/09/01 01:39:15 &{0xc420192730 TestData/README.html}: Object not found - waiting (4/24)
2016/09/01 01:39:20 &{0xc420192730 TestData/README.html}: Object not found - waiting (5/24)
2016/09/01 01:39:25 &{0xc420192730 TestData/README.html}: Object not found - waiting (6/24)
2016/09/01 01:39:30 &{0xc420192730 TestData/README.html}: Object not found - waiting (7/24)
2016/09/01 01:39:35 &{0xc420192730 TestData/README.html}: Object not found - waiting (8/24)
2016/09/01 01:39:40 &{0xc420192730 TestData/README.html}: Object not found - waiting (9/24)
2016/09/01 01:39:46 &{0xc420192730 TestData/README.html}: Object not found - waiting (10/24)
2016/09/01 01:39:51 &{0xc420192730 TestData/README.html}: Object not found - waiting (11/24)
2016/09/01 01:39:56 &{0xc420192730 TestData/README.html}: Object not found - waiting (12/24)
2016/09/01 01:40:01 &{0xc420192730 TestData/README.html}: Object not found - waiting (13/24)
2016/09/01 01:40:06 &{0xc420192730 TestData/README.html}: Object not found - waiting (14/24)
2016/09/01 01:40:11 &{0xc420192730 TestData/README.html}: Object not found - waiting (15/24)
2016/09/01 01:40:16 &{0xc420192730 TestData/README.html}: Object not found - waiting (16/24)
2016/09/01 01:40:21 &{0xc420192730 TestData/README.html}: Object not found - waiting (17/24)
2016/09/01 01:40:26 &{0xc420192730 TestData/README.html}: Object not found - waiting (18/24)
2016/09/01 01:40:31 &{0xc420192730 TestData/README.html}: Object not found - waiting (19/24)
2016/09/01 01:40:36 &{0xc420192730 TestData/README.html}: Object not found - waiting (20/24)
2016/09/01 01:40:42 &{0xc420192730 TestData/README.html}: Object not found - waiting (21/24)
2016/09/01 01:40:47 &{0xc420192730 TestData/README.html}: Object not found - waiting (22/24)
2016/09/01 01:40:52 &{0xc420192730 TestData/README.html}: Object not found - waiting (23/24)
2016/09/01 01:40:57 &{0xc420192730 TestData/README.html}: Object not found - waiting (24/24)
2016/09/01 01:41:02 &{0xc420192730 TestData/README.html}: Finished waiting for object - returning original error: Post https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication: http: ContentLength=436 with Body length 187028
2016/09/01 01:41:02 TestData/README.html: WriteFileHandle.Flush error: Post https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication: http: ContentLength=436 with Body length 187028
2016/09/01 01:41:02 fuse: -> [ID=0xd] Flush error=EIO: Post https://content-na.drive.amazonaws.com/cdproxy/nodes?suppress=deduplication: http: ContentLength=436 with Body length 187028

I'm away at the moment - will investigate further next week.
However I have a nasty feeling that uploads don't work with ACD via fuse because they need to know the file size in advance.

Yes I've confirmed this - you can't upload files to ACD with rclone mount. :-(  This is rather complicated to fix unfortunately - it might just be easier it I add a flag so rclone mount uses a temporary file for the upload.

I am experiencing a quite similar issue with fuse mount, but the behaviour seems to depend on the operating system. In Ubuntu 14.04, fuse mount works fine (I can create or copy files without apparent restrictions), while fuse mount in Raspbian Jessie behaves as if it were a read-only filesystem. In both systems rclone copy/sync are working properly.

Same issue here.
$ rclone -V
rclone v1.33-105-gd1080d5β

$ cp twrp_z00a_v24_repack.img ~/acd/
cp: impossibile creare il file regolare '/home/niccolo/acd/twrp_z00a_v24_repack.img': Errore di input/output

Hope you will fix it soon, meanwhile i'm going to use acd_cli to upload.

Hm, I guess I must be missing something here. AmazonDrive does not require the size to be known in advance, apart from the "files over 12 GB might not work" check. Using this rather simple patch, I can do the following:
stefan@aard ~/code/gocode/src/github.com/ncw/rclone $ cp /opt/rclone ~/acd/
stefan@aard ~/code/gocode/src/github.com/ncw/rclone $ md5sum /opt/rclone
505cfe704e2f7faf5b84104e86f68323  /opt/rclone
stefan@aard ~/code/gocode/src/github.com/ncw/rclone $ md5sum ~/acd/rclone
505cfe704e2f7faf5b84104e86f68323  /home/stefan/acd/rclone
stefan@aard ~/code/gocode/src/github.com/ncw/rclone $ rm ~/acd/rclone
stefan@aard ~/code/gocode/src/github.com/ncw/rclone $ cat /opt/rclone > ~/acd/rclone
stefan@aard ~/code/gocode/src/github.com/ncw/rclone $ md5sum ~/acd/rclone
505cfe704e2f7faf5b84104e86f68323  /home/stefan/acd/rclone

Overwriting doesn't work yet, but I haven't checked where this issue stems from. I first wanted to know what other problems you had in mind that would make write support complicated before fixing any of the probably simple bugs?
The patch is simply explained: instead of relying on src to give us a size, it simply checks if at least one byte can be read. The PutSized is only needed to create 0-byte files anyway.
diff --git a/amazonclouddrive/amazonclouddrive.go b/amazonclouddrive/amazonclouddrive.go
index 2a4d1a9..61ffde7 100644
--- a/amazonclouddrive/amazonclouddrive.go
+++ b/amazonclouddrive/amazonclouddrive.go
@@ -13,6 +13,7 @@ we ignore assets completely!
 */

 import (
+ "bytes"
        "encoding/json"
        "fmt"
        "io"
@@ -590,10 +591,14 @@ func (f *Fs) Put(in io.Reader, src fs.ObjectInfo) (fs.Object, error) {
        err = f.pacer.CallNoRetry(func() (bool, error) {
                start := time.Now()
                f.startUpload()
-           if src.Size() != 0 {
-                   info, resp, err = folder.Put(in, leaf)
-           } else {
+
+         buf := make([]byte, 1)
+         n, readErr := in.Read(buf)
+         if n == 0 && readErr == io.EOF {
                        info, resp, err = folder.PutSized(in, size, leaf)
+         } else {
+                 in = io.MultiReader(bytes.NewReader(buf), in)
+                 info, resp, err = folder.Put(in, leaf)
                }
                f.stopUpload()
                var ok bool

This should be fixed in http://beta.rclone.org/v1.34-22-g0b562bc/ (will be uploaded in 15-30 mins)
Please re-open if it doesn't work for you.

Upload works, the fuse mounts don't have any data in them. You can see them uploaded to amazon though.

Still an issue for me. I can mount my drive no issue, but when I try to copy a file to it I get the message "The item “Family photo” can’t be copied because there isn’t enough free space." The file is shown locally on my mount, but 0kb...
What is your rclone version (eg output from rclone -V)
rclone v1.34 (installed latest 1.34 beta, didn't change anything)
Which OS you are using and how many bits (eg Windows 7, 64 bit)
MacOS Sierra up-to-date
Which cloud storage system are you using? (eg Google Drive)
Amazon Cloud Drive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone mount -v Amazon:/Videos/ ~/Users/myname/Desktop/
Log: 2016/12/31 14:33:07 rclone: Version "v1.34" starting with parameters ["rclone" "mount" "-v" "Amazon:/Videos/" "/Users/karldagenais/Users/karldagenais/Desktop/"]
2016/12/31 14:33:08 amazon drive root 'Videos': Modify window not supported
2016/12/31 14:33:08 amazon drive root 'Videos': Mounting on "/Users/karldagenais/Users/karldagenais/Desktop/"
2016/12/31 14:33:08 amazon drive root 'Videos': Root()
2016/12/31 14:33:08 : Dir.Attr
2016/12/31 14:33:14 .hidden: Dir.Lookup
2016/12/31 14:33:14 : Reading directory
2016/12/31 14:33:14 amazon drive root 'Videos': Reading ""
2016/12/31 14:33:15 amazon drive root 'Videos': Finished reading ""
2016/12/31 14:33:15 : Dir.ReadDirAll
2016/12/31 14:33:15 : Dir.ReadDirAll OK with 3 entries
2016/12/31 14:33:15 Plex Series: Dir.Lookup
2016/12/31 14:33:15 Plex Series: Dir.Lookup OK
2016/12/31 14:33:15 Plex Series: Dir.Attr
2016/12/31 14:33:15 Plex Movies: Dir.Lookup
2016/12/31 14:33:15 Plex Movies: Dir.Lookup OK
2016/12/31 14:33:15 Plex Movies: Dir.Attr
2016/12/31 14:33:15 Plex Family Movies: Dir.Lookup
2016/12/31 14:33:15 Plex Family Movies: Dir.Lookup OK
2016/12/31 14:33:15 Plex Family Movies: Dir.Attr
2016/12/31 14:33:15 : Dir.Attr
2016/12/31 14:33:15 : Dir.Attr
2016/12/31 14:33:15 : Dir.ReadDirAll
2016/12/31 14:33:15 : Dir.ReadDirAll OK with 3 entries
2016/12/31 14:33:20 : Dir.Attr
2016/12/31 14:33:20 Family photo.jpg: Dir.Lookup
2016/12/31 14:33:20 Family photo.jpg: Dir.Lookup
2016/12/31 14:33:20 Family photo.jpg: Dir.Lookup
2016/12/31 14:33:20 Family photo.jpg: Dir.Lookup
2016/12/31 14:33:20 Family photo.jpg: Dir.Lookup
2016/12/31 14:33:20 Family photo.jpg: Dir.Create
2016/12/31 14:33:20 Family photo.jpg: Dir.Create OK
2016/12/31 14:33:20 File.Attr
2016/12/31 14:33:20 Family photo.jpg: WriteFileHandle.Flush
2016/12/31 14:33:20 Family photo.jpg: WriteFileHandle.Flush ignoring flush on unwritten handle
2016/12/31 14:33:20 Family photo.jpg: WriteFileHandle.Release closing
2016/12/31 14:33:21 : Dir.Attr
2016/12/31 14:33:21 Family photo.jpg: WriteFileHandle.Release OK
2016/12/31 14:33:21 Family photo.jpg: File.Attr
2016/12/31 14:33:21 Family photo.jpg: File.Open
2016/12/31 14:33:21 Family photo.jpg: ReadFileHandle.Flush
2016/12/31 14:33:21 Family photo.jpg: ReadFileHandle.Flush OK
2016/12/31 14:33:21 Family photo.jpg: ReadFileHandle.Release closing
2016/12/31 14:33:21 Family photo.jpg: ReadFileHandle.Release OK
2016/12/31 14:33:21 Family photo.jpg: File.Attr
2016/12/31 14:33:21 Family photo.jpg: File.Open
2016/12/31 14:33:22 Family photo.jpg: ReadFileHandle.Flush
2016/12/31 14:33:22 Family photo.jpg: ReadFileHandle.Flush OK
2016/12/31 14:33:22 Family photo.jpg: ReadFileHandle.Release closing
2016/12/31 14:33:22 Family photo.jpg: ReadFileHandle.Release OK
2016/12/31 14:33:22 Family photo.jpg: File.Open
2016/12/31 14:33:22 : Dir.ReadDirAll
2016/12/31 14:33:22 : Dir.ReadDirAll OK with 4 entries
2016/12/31 14:33:22 Family photo.jpg: ReadFileHandle.Flush
2016/12/31 14:33:22 Family photo.jpg: ReadFileHandle.Flush OK
2016/12/31 14:33:22 Family photo.jpg: ReadFileHandle.Flush
2016/12/31 14:33:22 Family photo.jpg: ReadFileHandle.Flush OK
2016/12/31 14:33:22 Family photo.jpg: ReadFileHandle.Release closing
2016/12/31 14:33:22 Family photo.jpg: ReadFileHandle.Release OK
2016/12/31 14:33:22 Family photo.jpg: File.Attr
2016/12/31 14:33:22 .ql_disablethumbnails: Dir.Lookup
2016/12/31 14:33:22 .ql_disablecache: Dir.Lookup
2016/12/31 14:33:27 Family photo.jpg: File.Open
2016/12/31 14:33:27 Family photo.jpg: ReadFileHandle.Flush
2016/12/31 14:33:27 Family photo.jpg: ReadFileHandle.Flush OK
2016/12/31 14:33:27 Family photo.jpg: ReadFileHandle.Release closing
2016/12/31 14:33:27 Family photo.jpg: ReadFileHandle.Release OK
2016/12/31 14:33:39 : Dir.Attr
2016/12/31 14:33:54 Family photo.jpg: File.Attr
2016/12/31 14:33:54 : Dir.ReadDirAll
2016/12/31 14:33:54 : Dir.ReadDirAll OK with 4 entries
2016/12/31 14:33:54 Family photo.jpg: File.Open
2016/12/31 14:33:54 Family photo.jpg: ReadFileHandle.Flush
2016/12/31 14:33:54 Family photo.jpg: ReadFileHandle.Flush OK
2016/12/31 14:33:54 Family photo.jpg: ReadFileHandle.Release closing
2016/12/31 14:33:54 Family photo.jpg: ReadFileHandle.Release OK
2016/12/31 14:33:54 Family photo.jpg: File.Open
2016/12/31 14:33:54 Family photo.jpg: ReadFileHandle.Flush
2016/12/31 14:33:54 Family photo.jpg: ReadFileHandle.Flush OK
2016/12/31 14:33:54 Family photo.jpg: ReadFileHandle.Release closing
2016/12/31 14:33:54 Family photo.jpg: ReadFileHandle.Release OK
2016/12/31 14:33:54 Family photo.jpg: File.Attr
2016/12/31 14:33:54 Family photo.jpg: File.Open
2016/12/31 14:33:54 : Dir.Attr
2016/12/31 14:33:54 : Dir.ReadDirAll
2016/12/31 14:33:54 : Dir.ReadDirAll OK with 4 entries
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Flush
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Flush OK
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Release closing
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Release OK
2016/12/31 14:33:55 Family photo.jpg: File.Attr
2016/12/31 14:33:55 Family photo.jpg: File.Open
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Flush
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Flush OK
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Release closing
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Release OK
2016/12/31 14:33:55 Family photo.jpg: File.Attr
2016/12/31 14:33:55 Family photo.jpg: File.Open
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Flush
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Flush OK
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Release closing
2016/12/31 14:33:55 Family photo.jpg: ReadFileHandle.Release OK


Add SELinux policy for clearkey HIDL service.

Convert clearkey plugin to HIDL to support drm HAL v1.1.
Add SELinux policy for<EMAIL_ADDRESS>Test: CTS test
ANDROID_BUILD_TOP= ./android-ccts-tradefed run cts-dev
--module CtsMediaTestCases
-t android.media.cts.ClearKeySystemTest#testClearKeyPlaybackCenc
bug: 69635855
Change-Id: I61e9c272c2a2788fd07d5c12921d28c785661b77

needed by
https://github.com/sonyxperiadev/device-sony-common/pull/505/commits/f98f536980a1b5266724a33e5cf6d18e4bfa2889
https://github.com/sonyxperiadev/device-sony-common/pull/505/commits/4bf7d2ac80d22d7c7d554621b5e2eb08bf715d12
https://github.com/sonyxperiadev/device-sony-common/pull/505/commits/f8bcca566ec15eadda9dc54ba07cb35da038bf55

please split the commit
https://github.com/sonyxperiadev/device-sony-sepolicy/pull/398/commits/ab11ae86fff717cb5714fff8a51d317399f635cf

please set PRODUCT_SHIPPING_API_LEVEL := 26 in your local tree

why 26 ? not all supported devices were released with nougat

@alviteri 26 is 8.0, 27 is 8.1.
What matters is that setting PRODUCT_SHIPPING_API_LEVEL to whatever causes PRODUCT_FULL_TREBLE to be set, in turn applying even more neverallow constraints to the sepolicy, with which we want to stay compatible.

ok whatever but we should declare the shipping api level (real one)

libsepol.report_failure: neverallow on line 866 of system/sepolicy/public/domain.te (or line 11008 of policy.conf) violated by allow hal_camera_default camera_data_file:dir { search };
libsepol.check_assertions: 1 neverallow failures occurred

please rebase

new start with PRODUCT_SHIPPING_API_LEVEL := 26 in local tree

Thank you alin ... For some unknown reasons I don't have the flag set anymore ... I will be careful next time .....

please rebase


Cryptography Changes

Having already made changes to master, I didn't want to have to deal with any conflicts, so I cherry-picked most of your changes from this PR, and they've been released in 1.4.10. Thanks for your contribution!


codecov fails on seemingly random test packages

Some examples:
Reports are stored in /go/out/codecov
The following tests failed
FAIL: istio.io/istio/mixer/adapter/cloudwatch
FAIL: istio.io/istio/mixer/adapter/cloudwatch/config
FAIL: istio.io/istio/mixer/tools/mixgen/cmd
Exited with code 1

2x:
The following tests failed
FAIL: istio.io/istio/galley/pkg/runtime
FAIL: istio.io/istio/mixer/pkg/il/text
FAIL: istio.io/istio/mixer/pkg/lang/checker
Exited with code 1

The following tests failed
FAIL: istio.io/istio/galley/tools/mcpc
FAIL: istio.io/istio/istioctl/cmd/istioctl/gendeployment
FAIL: istio.io/istio/istioctl/pkg/convert
FAIL: istio.io/istio/istioctl/pkg/util/clusters
FAIL: istio.io/istio/istioctl/pkg/util/configdump
FAIL: istio.io/istio/mixer/adapter/kubernetesenv/config
FAIL: istio.io/istio/mixer/adapter/kubernetesenv/template
FAIL: istio.io/istio/mixer/adapter/list/config
Exited with code 1

The last 5 jobs are all failures:
https://circleci.com/gh/istio/istio/213186
https://circleci.com/gh/istio/istio/213171
https://circleci.com/gh/istio/istio/213201
https://circleci.com/gh/istio/istio/213186
https://circleci.com/gh/istio/istio/213201
Seems to work fine locally on my dev env.

/cc @stewart-yu

/assign
will have a look

@stewart-yu: GitHub didn't allow me to assign the following users: stewart-yu.
Note that only istio members and repo collaborators can be assigned.
For more information please see the contributor guide

In response to this:

/assign
will have a look

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

This should have been fixed by https://github.com/istio/istio/pull/9341
Though, the codecov jobs are now failing due to integration test failures at the moment.


[Feature]: Add missing query parameters on GET v3/service_credential_bindings

Background
Currently the supported query parameters when listing service bindings are: AppGUIDs, ServiceInstanceGUIDs. There are a lot of possible parameters missing. Here we can see all supported ones: https://v3-apidocs.cloudfoundry.org/version/3.180.0/index.html#list-service-credential-bindings
Acceptance Criteria

Enable filtering with all the missing parameters when listing service bindings

I will look into this if I can get this done

after having a first look I have an idea why no one implemented that so far :D


Update README with staging deploy steps

This PR is updating the readme with the staging deploy steps as outlined here.
The reason for this is mainly so that whoever is reading the "Testing on staging" part in the readme don't have to search for an additional doc on how to deploy staging.

I believe we eventually need something like https://github.com/dimagi/staging-branches/ for CCA or can we use that same repo itself for cca?

Yes, I think so.
I've added this ticket yesterday, so maybe it can form part of that.


Add "DOH!" sound

This adds a target to the Makefile called with-sound that builds sound support for doh that can be activated with the -s flag.
Example usage:
./doh -s example.com

The textual output should be identical to ./doh example.com. Other than that, just make sure your volume isn't too high :smirk:
If you prefer that to be the default behavior, you can always set an alias for it
(e.g. alias doh="doh -s")
By default, doh sound support will not be included (meaning this won't affect people who don't know about it or want it).
As a side note, I tried finding a cross-platform lib to play audio and SDL2 was the best I could come up with. It seems kinda overkill given the use case, but it's what I found. I'm open to other (better) ideas if they're out there.

@bagder Any word on this?

I've been struggling on what to think about this PR and how to proceed.
I don't want to be a party pooper and this is only conditional and I realize it is made with good intentions and the right spirit. At the same time, I fear that accepting this PR signals that this is a joke tool and that we'll get further jokes and will get to argue about why the next joke won't be merged when this was fine.
Right now, I'm leaning towards saying this was a fun idea and to reject it, but I'm also open to hearing if there are other voices out there that can convince me to accept it. So I rather just leave this open for now without making a firm decision. I'll tweet about it and see if I can drum up some opinions...

That's fair. I made it purely for fun, and it's not really "useful" other than for humor, so I don't have a problem if you decide to close/reject it :+1:
(But it is pretty fun)

We need this, I can't use curl if I have no doh!

It's unnecessary. I don't get the struggle. It may actually be useful to someone and not a joke but that's besides the point. Every feature that's added has a maintenance cost and a maintenance cost is a time cost. Is this really worth your time? Is it really worth it to hear Homer Simpson say doh? (I somewhat suspect this argument may backfire, but ok). It's a cool idea and I liked reading about it but not for upstream.

@kimbo Please fork the repo and let it be packaged under the name audioh

Thanks everyone for your feedback, thoughts and comments and thanks to @kimbo for the PR. In the end I want to focus on code stability and include code that is easy to maintain - thus I say thanks but no thanks to this doh sound PR.


LE Audio: TBS add support for optional characteristics and features

Is your enhancement proposal related to a problem? Please describe.
The current TBS implementation includes all features and characteristics, and some of these are either conditional or optional, and can be optimized.
Describe the solution you'd like
The optional features and characteristics should be optionally enabled with Kconfig. If we want to support different set of characteristics per TBS instance, then these needs to be added/removed at runtime registration once https://github.com/zephyrproject-rtos/zephyr/issues/41738 is done.
Describe alternatives you've considered
N/A
Additional context
N/A

This is still valid


Improve coverage in common.

This gets line coverage in common to 100% and improves branch coverage.

LGTM, just a few linting issues.

In a meeting; will knock them when I get out.
I will also install a linter plugin in Atom so I catch those sooner.

Coverage increased (+0.01%) to 99.987% when pulling 3ab1b283ab8bcb154ee2d33e20cd4918089d22ee on lukesneeringer:common-coverage into f569e1dcfdc63af40787e9a79debe494ae7c49a0 on GoogleCloudPlatform:master.


Update Globals “nav”

Automatically generated by Netlify CMS

👷 Deploy Preview for shiny-babka-998c7e processing.

Name
Link

🔨 Latest commit
4171fec8bc28ee216d5609a58b253302dbfc6df6

🔍 Latest deploy log
https://app.netlify.com/sites/shiny-babka-998c7e/deploys/6283608ced73f0000963aeb0


Patch to custom env docs

It's not very clear where to find the example environment configuration files when reading the custom environment docs.
Just added an additional pointer that explicitly says the config files are in the repo containing the source code of the docs.
There is probably a better way but this is just a quick improvement.

Any reason to not just link to the github location?

FYI I have merged getting-started into develop. Can we re-point this PR to develop?

Sure will move this.
@wildintellect which branchn would I point to ? what if users are looking at the version of another branch?

@emileten can you provide some urls, so we can examine if we should always point to master or perhaps the files are in the rendered site and a relative url works?

@wildintellect the files aren't in the rendered site. That could be a todo for later, would be more user friendly.
The file sources is here https://github.com/MAAP-Project/maap-documentation/tree/develop/docs/source/system_reference_guide/example_conda_configuration_files.
I don't think these will be change often, so it should be ok to just always point to that link?

@emileten this raises a question, should those file be buried deep in the website source, or should they be brought up much higher in the directory structure for easier access when cloning the repo? Example https://github.com/aws/studio-lab-examples/tree/main/custom-environments puts a folder at the repo top level.  This way even if we re-organize the pages later these files won't move.
Also wondering if we should give them more descriptive env names? and if we should make some real useful examples rather than just examples for examples sake?

@emileten this raises a question [...]

Suggestion @wildintellect : I add a notebook that looks like this and I link that in the custom-env explanation notebook. That way the yaml files referenced are always the right ones.

Also wondering if we should give them more descriptive env names?

Agreed, I will address this in this PR

And if we should make some real useful examples rather than just examples for examples sake?

Agreed but that takes more time so we should do this in a later issue/PR

Sure we can do better examples later. A few comments:

At a minimum these should always include ipykernel
For later, we need a R example with an Rkernel
does the base.yml conflict with the base env already in a workspace?

At a minimum these should always include ipykernel
For later, we need a R example with an Rkernel

Adding these to an 'update examples' ticket along with 'real useful examples rather than just examples for examples sake'

does the base.yml conflict with the base env already in a workspace?

I don't think it does since I remember testing all of these configs. To be clear, it's a config used to show how to update an environment. Should rename it to update_base.yml.

Now I am pointing to a notebook showing the example config files. The notebook lives in the same section (system reference guide). Also renamed the files so that the names align with the example purpose.
Here is part of the notebook in a screenshot. It's admittedly not perfect, e.g. one has to copy paste what's printed and put it in a yaml file. But I think it's better than before ?

I think listing the contents like this is fine. It seems most likely that it'll be used as a template, anyway, and someone would copy/paste from a file or from the notebook and then edit it.
Potentially we could suggest that the workspaces have these environment examples built-in, in a standardized location. That way everyone would start to put their env files in the same location and have some examples to start with.

@rtapella I quickly tried after your suggestion https://github.com/mamba-org/gator#Navigator and it both works relatively smoothly and is nice. It also looks acceptably active.
So if we follow your suggestion

Potentially we could suggest that the workspaces have these environment examples built-in, in a standardized location. That way everyone would start to put their env files in the same location and have some examples to start with.

We could replace the pointer to this printer notebook with a pointer to the environments UI.
My question is : if we want to do that, should we hold on merging this ? Or should we merge this, and then figure out the UI addition ?
This is ready by the way. Below a screen of what the index looks like.

@rtapella yes having the whole docs installed by default has been mentioned several times (future scope)
@emileten the visual tool does not solve this issue, we need users to make yaml files because they will need to supply those for DPS algorithms. It's just an extra, I consider out of scope for this version.


Add v0 branch

I'm working on a fork to maintain the v0.x.x versions and I need a branch called v0 to send PR to it. I'm doing this because I work with a project that use this lib, but my project use Angular 9 and some feature of this lib were add in v1.x.x and forward.

Hi @pedromdev!
I would suggest that you simply push commits to your fork. I think it's easier for both parts. I can include a link to your fork in the README.md if anyone is interested in an Angular 9 version of the support.
Creating a separate branch would require me to review the PR and merge them, and unfortunately, I am too busy to dedicate time to this work. Additionally, publishing 0.x.x versions is out of the scope.
If you have any questions just tell me!  In summary, I believe this is the best option!


Missing versioning and release documentation

Currently we try following semver versioning while creating GitHub releases, but that's not documented anywhere.
ToDo:

[ ] Finalize versioning and releases standard.
[ ] Add documentation for release procedure.
[ ] Update README with links to documentation created in above steps.
[ ] Update maintainer docs.

Finalize versioning and releases standard

Since this is something that needs a decision that has a major effect, I think this shouldn't be a good first issue.
For example, https://www.kubernetes.dev/docs/guide/help-wanted/#good-first-issue, the Kubernetes Contributors docs mention that good first issues should have a defined solution.


move request builder files to index in typescript

now that all the files for a given request builder are grouped in a single file after #3798, we should have all that content in index.ts to save 2 files x2 per path segment in the Microsoft Graph SDK. This will reduce the bundle size and speed up install/tooling/bundling

back of the napkin math would indicate we'd save ~7000 files (x2 js and .d.ts) over the current 36k => 22k ~30% reduction in file number.
each of those 7k entry represent about 215 bytes on disk  ~1.5MB disk size reduction.


DOM for Pager

Hi,
I think the pagination generated by Pager should have a better DOM. Actually DOM looks like.
nav > a

What we should have when I looking in Bootstrap and Bulma documentation pagination, should be a list.
nav > ul > li > a

And not forget class for active / current page as props.
Thanks :)

Hi there, bootstrap can also do this:

This is from their official docs.

But I agree we need to add an option to change the active class :)
https://gridsome.org/docs/pagination


x/tools/gopls: TestRenamePackage_InternalPackage failing on linux-amd64-wsl builder

It looks like the linux-amd64-wsl builder is generally unhappy. It seems to have encountered "hanging go commands" very frequently, but that is a separate issue (#54461).
Recent failures appear deterministic, failing with "permission denied", starting with https://go.dev/cl/459416. This may be because the go command is still holding onto a file, but the failure mode does seem related to that change.
https://build.golang.org/log/5053369eca96766a09d70f36ed4ac8926fc182a1
rename_test.go:940: renaming sandbox file: rename /tmp/workdir-host-linux-amd64-wsl/tmp/gopls-regtest-4043663239/TestRenamePackage_InternalPackage/default/work/lib /tmp/workdir-host-linux-amd64-wsl/tmp/gopls-regtest-4043663239/TestRenamePackage_InternalPackage/default/work/lib1: permission denied

CC @dle8

The WSL builder has been sick, see https://go.dev/issue/57517.

Closing as dupe of #57517


Correct name and path

cc @cowanrc trust the process

Codecov Report
Base: 95.67% // Head: 95.82% // Increases project coverage by +0.15% :tada:

Coverage data is based on head (5dc41b9) compared to base (2efa3e5).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #55      +/-   ##
==========================================
+ Coverage   95.67%   95.82%   +0.15%
==========================================
  Files          32       32
  Lines         416      407       -9
  Branches       98       96       -2
==========================================
- Hits          398      390       -8
+ Misses         15       14       -1
  Partials        3        3

Impacted Files
Coverage Δ

src/hooks/useUser.ts
93.33% <0.00%> (+1.66%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Do not remove ial on blockquote inside triple quoted

Closes #94.

Since I was playing with the line scanner code not long ago, I thought I would give the fix a try!

Pull Request Test Coverage Report for Build 0a2c9c2dcde30d2671a767f10b8f846e3190ffbd-PR-96

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.9%) to 95.892%

Totals

Change from base Build 199e8dd5d9f9a2fc0415a027ec3d6d8f1aeb7f08:
1.9%

Covered Lines:
747

Relevant Lines:
779

💛  - Coveralls

Hmm I had rejected this fix because I assumed (never assume of course) it would break the case where Milmazz was needing it.
Obviously I was wrong
Ty so much, I'll release 1.4.20 today (although 2022-02-22 would be funnier)


Haskell-ghc-mod: ghc-mod failed to launch.It is probably missing or misconfigured.

[Enter steps to reproduce below:]

...
...

Atom Version: 1.3.2
System: Mac OS X 10.11.2
Thrown From: haskell-ghc-mod package, v1.3.0
Stack Trace
Haskell-ghc-mod: ghc-mod failed to launch.
It is probably missing or misconfigured.
Restart Atom after configuring.
At Error: spawnSync ghc-mod ENOENT

Error: spawnSync ghc-mod ENOENT
    at exports._errnoException (util.js:837:11)
    at Object.spawnSync (child_process.js:432:20)
    at new GhcModiProcess (/Users/andrew/.atom/packages/haskell-ghc-mod/lib/ghc-modi-process.coffee:24:14)
    at Object.module.exports.HaskellGhcMod.activate (/Users/andrew/.atom/packages/haskell-ghc-mod/lib/haskell-ghc-mod.coffee:84:18)
    at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:170:19)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:150:32
    at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:92:15)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:143:26
    at Package.module.exports.Package.activate (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:140:34)
    at PackageManager.module.exports.PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:517:21)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:499:29
    at Config.module.exports.Config.transactAsync (/Applications/Atom.app/Contents/Resources/app.asar/src/config.js:337:18)
    at PackageManager.module.exports.PackageManager.activatePackages (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:494:19)
    at PackageManager.module.exports.PackageManager.activate (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:478:46)
    at AtomEnvironment.module.exports.AtomEnvironment.startEditorWindow (/Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:686:21)
    at module.exports (/Applications/Atom.app/Contents/Resources/app.asar/src/initialize-application-window.js:28:10)
    at setupWindow (file:///Applications/Atom.app/Contents/Resources/app.asar/static/index.js:86:5)
    at window.onload (file:///Applications/Atom.app/Contents/Resources/app.asar/static/index.js:41:9)

Commands

Config
{}

Installed Packages
# User
autocomplete-plus, v2.25.0
haskell-ghc-mod, v1.3.0
ide-haskell-cabal, v1.0.0
language-haskell, v1.5.1

# Dev
No dev packages

Do you have Haskell Platform or similar?
Do you have ghc-mod installed?
Is it on your PATH?

If answer to all of the above questions is 'yes', you likely need to set 'Additional Path Directories' in haskell-ghc-mod settings to reflect your PATH. OSX has some weirdness w.r.t. PATH inheritance.
If answer to last question is 'no', you need to specify full path to ghc-mod executable in 'ghc-mod Path' in addition to above.

Closing due to inactivity


We need to do a text copy audit and review for the new Docs and Guides updated

Link to the Page
https://dev.skeleton.dev/docs/why
https://dev.skeleton.dev/guides/install
Describe the Issue
These were recently updated as part of:

https://github.com/Brain-Bones/skeleton/pull/513

However, the copy is still a bit rough. We have several spelling and grammar mistakes. Let's do a follow up and improve this before the upcoming release.
Are you able to create a Pull Request with the fix?
Yes

I've implemented all my desired changes. Though always welcome more QA and feedback!


Does LangChain-Benchmarks only support models from the model registry?

I'd like to run some benchmarks against models from Hugging Face. The tutorials seem tailored for models from the registry or OpenAI.
Before I go down the rabbit hole and try to use it myself, I thought I'd see if it was possible or if anyone has done this before and has examples I can look at.
Thanks

Nope! The registry is a convenience wrapper, but you can run it on anything. Here's an example that's more manual: https://langchain-ai.github.io/langchain-benchmarks/notebooks/tool_usage/intro.html#custom-agent-factory
Or you can pass in a langchain LLM to the other agent "factories"


model: sktime: Add forecasting models

https://github.com/alan-turing-institute/sktime

@pdxjohnny  I'd like to work on this.

@mHash1m Awsome!


update racon repo

The following instructions are for pull requests related to tool entries.
If your pull request is about something else they can be ignored.
Please describe your pull request below and fill out the check list:
Add your description here:
Please check whether you could check following boxes. Else it will break the build of the database!

[ ] Only (manually) edited long_read_tools_master.csv
[ ] Tool/pipeline names were added using only "[a-z],{a-}, [0-9], _, -" characters (e.g. no spaces, slashes or tabs
[ ] Add relevant multiple publications separated by ;
[ ] Add "NOT-MAINTAINED:: " or "DEPRECIATED:: " to the beginning of the description column of long_read_tools_master.csv
[ ] Completed all columns that needs logical values(i.e. TRUE, FALSE)
[ ] Have at least one functional category marked as TRUE per tool
[ ] Add multiple Programming_Language separated by commas
[ ] Check the link of the Source you are noting points to the root of the repository only
[ ] Either have peer-reviewed journal DOI or preprint DOI. Leave reference as blank for unpublished tools
[ ] Run build_lrs_db.R (optional)

I have updated this manually... hopefully, it will show up. thanks for submitting directly.


RandomResize during inference?

Quick question. Why do you do RandomResize during inference?
https://github.com/IDEA-Research/GroundingDINO/blob/2b62f419c292ca9c518daae55512fabc3fead4a4/demo/inference_on_a_image.py#L64

Quick question. Why do you do RandomResize during inference?
https://github.com/IDEA-Research/GroundingDINO/blob/2b62f419c292ca9c518daae55512fabc3fead4a4/demo/inference_on_a_image.py#L64

We can only set one scale in its args to make it into a single size transform here

Tracking down RandomResize implementation, the images are resized to a fixed square size of 800x800; no randomness is employed.
Note that it is [800] not 800, the former is a list of random sizes to choose from whereas the later is a minimum limit on size to use. Since we choose a random number from a list of one value only, the size is always fixed to 800.

The image will be resized while keeping the original ratio. The short side of the image will be resized to 800 if doing so the long side of the resized image will be less than or equal to 1333. Otherwise, the long side will be resized to 1333.

Hi quick question, the resizing obviously changes the coordinates of the detected bounding boxes so if the downstream aplication needs the coordinates of the bounding boxes relative to the original size, how to do the conversion back? i'm guessing that since the obtained coordinates are relative instead of absolute we just need to multiply by the original size(or something similar, haven't put too much thought into it, just the first idea that came to mind)


⚠ Bofrost.be has degraded performance

In 33cb445, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1057 ms

Resolved: Bofrost.be performance has improved in cb781f9 after 6 minutes.


fira: remove Fira Mono

(This is my first pull request here and I'm mildly overwhelmed with the things I should do below. If someone wants to help, I'd appreciate it. I'm not even sure how I go about testing the change on my own system. )
Description of changes
Change the build commands to only copy FiraSans*.otf. Fira Mono is covered by a different derivation "fira-mono"
I ran into an error when I tried to install "fira" and "fira-mono", so I investigated it and the reason is that the mozilla/Fira repository contains a sneaky 3 extra FiraMono*.otf files. They are being packaged by both fira-mono and fira

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

cc @rycee

Makes sense, I think. And yeah, the apostrophe package will need to be updated as well. Could you include the apostrophe change as well?

Running into this as well.
building '/nix/store/g4yip9z58721xxcb196yzvjl1h6l019p-system-fonts.drv'...
warning: different permissions in `/nix/store/z6f505d9gb9228npm1mnykdr3a10j2an-fira-4.202/share/fonts/opentype/FiraMono-Bold.otf' and `/nix/store/l2y2djl6jail954c9rfjl4n6zahmkg5d-fira-mono-4.202/share/fonts/opentype/FiraMono-Bold.otf': 0555 <-> 0444 at /nix/store/by3lmvq7ldg20ivmad96p6kzb9pwb8bs-builder.pl line 103.
error: collision between `/nix/store/l2y2djl6jail954c9rfjl4n6zahmkg5d-fira-mono-4.202/share/fonts/opentype/FiraMono-Bold.otf' and `/nix/store/z6f505d9gb9228npm1mnykdr3a10j2an-fira-4.202/share/fonts/opentype/FiraMono-Bold.otf'
error: builder for '/nix/store/g4yip9z58721xxcb196yzvjl1h6l019p-system-fonts.drv' failed with exit code 2

I've disabled fira fonts in my configuration.nix file for now.

My problem with this change is that it'll break downstream user's systems silently: Fira Mono will just disappear. Consequently this needs at least a changelog entry.
An alternative, non-breaking way of solving the inconsistency would be to drop fira-mono and alias it to fira (it's not called fira-sans anyways).

Or we can deprecate fira in favour of fira-sans.

Do the benefits outweigh the costs of downstream users needing to potentially debug their systems and adjust their configuration?

Aliasing fira-mono to fira will result in fira-mono bringing FiraSans*.ttf, which is unexpected.
The proper fix is to drop one of the two, and human intervention is required in both case. And dropping fira is just better.

In the context of configurability, I would prefer if I could choose either firaSans or firaMono fonts separately and then an Alias called firaFull that includes both.

I'm really sorry I lost track of doing this PR. I can see that a bunch of people got involved. Is there anything you need me to do at the moment? If yes, I will make time over the weekend.

@wegank Did you have any specific changes in mind when you set this to draft in April?
Not trying to force a merge decision... I just read hellerbarde's comment and couldn't figure out myself whether this has hit an impasse, or the ball is in his court, or if there's some other blocker.


feature: Users can create conversations.

I'm going to take care of #21 soon, but I know that how we want to handle messaging is going to require a lot of discussion. I had some ideas about the data model, so I wanted to get some of my ideas down in code so that we can start discussing things now instead of later.
I had a lot of trouble naming some of the relationships, and I'm still trying to completely determine how the UI would look. Any input here would be appreciated. Right now I'm particularly struggling with how we differentiate between Client users and Developer users.

Just a note for myself after doing some more thinking.
I'm considering changing client_conversations to be leads and developer_conversations to be prospects. I'm not 100% on these names, but I feel like they fit the domain and that they'll be helpful with the UI design.

Thanks for kicking this off! This is probably the next "big" feature for railsdevs, but I want to make sure #86 is live before I dive into this too deeply.
That said, for the modeling, I think you have some solid ideas. Here's how I've sketched it out before.

A Conversation has many Messages

Messages belong to a conversation, developers have many messages through conversations

A Conversation belongs to a Developer and a Company

I want a better name for Company, but they are essentially the "hirer"

Developers can't message other developers (for now)
Only companies can initiate a conversation with a developer
That leads to a ConversationsController and a MessagesController

Former is where the viewing of messages occurs
Latter is where the POSTing of messages occurs

"Multi-column inbox" from Tailwind UI is the (more complicated) direction I'm thinking design-wise
This will flesh out when you create an account saying you are a developer or a company

This could be started with a boolean flag (radio) on the sign up form

On top of that, there's moderation. We don't need this for this PR, but I won't launch messaging until this is in place.

ModerationController is nested under MessagesController to allow POSTing to flag a message
This creates a Moderation record, belonging to a Message
Moderations are only visible to admins via Admin::ModerationsController

There's a lot to do here, but just being able to see the flagged content is a great start

Hey! I'm just poking around GitHub while finishing eating breakfast, and I need to get back to my work. That said, I just wanted to drop a super quick reply.
I feel that what you've sketched out roughly matches the conceptual model I have in my head as well. I ran into a few stumbling blocks around handling some of the domain logic. If you're available to chat today I'd be more than happy to offer some insight on what I've found so far.

Awesome! If possible, I'd love to keep as much conversation on GitHub. Then everything is kept public and anyone can chime in who is reading.

@joemasilotti I think that I'm going to go ahead and close this PR for now, but I wanted to quickly write a summary post while eating breakfast.
So, the data model essentially played out the way you described.

Conversation belongs to developer and client
Clients have many hiring_leads
Developers have many work_leads
Conversations have index and show views
The index and show views are combined into a single UI

I didn't ultimately need separate controllers for hiring leads vs. work leads though. Instead I used Pundit scopes to select the appropriate conversations for each type of user.
From there the plan was the following:

Conversation has many messages
Clients could only message developers and vice versa
Conversations could be created in the show action using find_or_create_by

Ultimately I want to put a pin in this for 3 major reasons.

In this implementation I attached conversations to users rather than the developer model. I'm not sure if this is the best approach, and I want to take some time to thoughtfully discuss with you what we consider Developer to be. As of now, it kind of seems to represent more of a developer profile to me, but I can also see the argument that it represents a role of User that's composed into the User class using the has_one relationship.
We need to figure out how we want to model companies before getting the behavior for conversations down solid. This goes hand in hand with point 1. For instance, if we want to go with the composable approach mentioned in 1, we might need a new registration flow. Additionally, I think we might have to consider moving avatar into the User class since that would need to be a shared behavior. Either way, in order to get Conversation solid, we'll need the Company API to be solid so that  we can establish the Conversant ducktype or role solid.
Even this one PR which was meant to be just a portion of the behavior, is like three or four actual feature PRs in one. We need to make a decision regarding whether we want to pull this out into a branch outside of master while working on it, or if we want to do feature flags.

I hope this was insightful. If you have any questions I'll try and answer when I'm available. Things will be pretty spotting this week with Thanksgiving coming up though.

Thanks so much for this spike @jacobdaddario! I agree with your third point – this is way more work than a single PR. It will most likely be built up slowly and perhaps a lot behind feature flags to start.
I'm hoping to break this down into PR-sized chunks over the next few days. And I'll be referencing your PR for guidance.


chore: add eslint

Closing this PR as linting was fixed in https://github.com/warp-ds/elements/pull/153.


Opt-out of array merging

Is there a way to opt-out of the array merging?

What do you mean? If you merge A with B and both contain the array named C then the result will contain the array from B. Do you want the result to ignore the array from B and keep the array from A?

I'd like to do something like this:
let o = Immutable({arr: [{id: 2}]});
o.merge({arr: [{id: 3}]}, {mergeArray: false});
// o is {arr: [{id: 3}]}

So the array from B should override the array from A.
With the current implementation the result is {arr: [{id: 2}, {id: 3}]}

This is my output when I test with 3.0.0 and 4.0.2:
var o = immutable({arr: [{id: 2}]});
o = o.merge({arr: [{id: 3}]});
// o is {arr: [{id: 3}]}

Oh, you're of course totally right! Sorry for the annoyance – I mixed this up with another library. Everything works as expected.


Doesn't seem to be working?

I tried both copying the in/out teleport methods shown in the animate gif and creating an @stairs NPC and placing them in the drawing with level 1 and 2. I also tried with and without map note teleport, nothing I seem to do is able to move the tokens from floor 1 to floor 2 and back within the same scene. The clone effect DOES work, however. but that's all that's working.

Are you on Foundry VTT 11? It seems to have stopped working with V11 for me.


Implement logging

Context
It would be useful if the site had robust logging in order to quickly diagnose issues.
Things to consider
Need to learn best practices with Django logging.

Implemented in https://github.com/jsolly/blogthedata/pull/114
Logs are in django_project/logs/blogthedata.log


Fixed overlap ( border does a lot better now)

Didn't mean to put the branch on your page.

Yeah, I think it may be easier for you if you work directly over the same repository. But what we were doing until now also worked!


proof https://github.com/kcp-dev/kubernetes/pull/96

Summary
Related issue(s)
Fixes #

/hold

/hold cancel

/lgtm
/approve


Fully replace jest unit tests with cypress E2E tests

The problem
Jest unit tests are great! Just not for this component. JSDOM pretty much completely disables the video element, which is what this entire library is built on. As a result. I had to throw together an absolutely monstrous amount of mocking in order to make anything testable. I did my best to stick as closely to the W3C specs as I could for the mock implementation, but it still has gaps and in retrospect, that was just a really terrible idea. Why did I do that?
The solution
The time has come to fully go all-in on E2E tests. Since everything is running in a real browser, these tests don't require any mocking at all in order to test the the video element is loading/playing correctly! Additionally, this opens up the ability to go even deeper with some tests to make sure things really work the way they're supposed to.
TODO

[x] Get test coverage for cypress tests up to 100%
[x] Rip out old jest tests and ensure each test is replaced by a cypress test

:tada: This issue has been resolved in version 9.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


update list deps

Feature description

support build deps graph and list upstream/downstream dependencies.  These apis do not reply on analyzing the Kusion stack/project structure, but only parse dependency by parsing import statements.
add apis:

ListUpStreamFiles(workDir string, opt *DepOption) (deps []string, err error): ListUpStreamFiles return a list of upstream depend files from the given path list.
ListDownStreamFiles(workDir string, opt *DepOption) ([]string, error): ListDownStreamFiles return a list of downstream depend files from the given changed path list.

Examples of usage:

the demo KCL
the API call to list the upstream files that the focused files depend on:
depParser, err := NewImportDepParser("testdata/complicate/", DepOption{Files: []string{appops/projectA/base/base.k", "appops/projectA/dev/main.k", "base/render/server/server_render.k"}) upstreamDeps := depParser.ListUpstreamFiles()

LGTM


Support for fixed-size / inline arrays

Please consider implementing support for fixed-size, "inline" arrays in struct definitions, as in C/C++, or in C#'s Fixed Size Buffers. In the wire formats, the encoding could be exactly the same so there'd be no difference in size; for applications with structs containing an array-typed field known to have a fixed length (e.g., ISBN could be represented by byte[13]), this may improve performance by eliminating lots of small array/string heap allocations.

You can achieve this with type aliases, e.g.: https://github.com/Microsoft/bond/tree/master/examples/cpp/core/static_array

@sapek Seems like that'll only work for C++? What about C# support?

You can use array as type alias of a vector/list/blob in C#. I've never tried with fixed size array though. Give it a try. If it works, it would be a great example to contribute. If you find a problem we should see if it can be fixed.

Type aliases won't work for C# fixed arrays for two reasons:

there's no way to "name" the generated type for the fixed array, so none of the converter method match; and
the converter method isn't given access to the source/destination object, just the value to convert, so there no where to put the data.

[Schema]
unsafe struct Foo
{
    [Id(0)]
    [Type(typeof(Bond.Tag.blob))]
    public fixed byte inlineFixedArray[10];
}

    public unsafe static class BondTypeAliasConverter
    {
        // BROKEN!!!
        public static byte* Convert(ArraySegment<byte> value, byte* unused)
        {
            fixed (byte* inputPtr = value.Array)
            {
                // This will fail, as unsued isn't actually a pointer into the object. It will be 0.
                Buffer.MemoryCopy(inputPtr + value.Offset, unused, 10, 10);
            }

            return default(byte*);
        }

        // BROKEN!!!
        public static ArraySegment<byte> Convert(byte* value, ArraySegment<byte> unused)
        {
            var copy = new byte[10];
            fixed (byte* copyPtr = copy)
            {
                // Who knows if this will work. Will value point to the right thing?
                Buffer.MemoryCopy(value, copyPtr, copy.Length, copy.Length);
            }

            return new ArraySegment<byte>(copy);
        }
    }

If you want to use fixed arrays, a custom transform is going to be needed.


Hangs related to QSTask

I’ve been seeing QS “Not Responding” with the latest Universal builds from Xcode 13.
I’ve sampled the process and gotten some spindumps, but in every case, it appears to be related to the @synchronized calls in QSTask.
This happened the first 3 times I tried to install plug-in updates, but not the 4th. I’ve also seen it happen when rescanning the QSProcessObjectSource, but that thing gets rescanned every time you switch applications in macOS, so it’s probably a potential issue with all catalog entries and that one is just the most likely to hit it.
I’ve attached a sample. I plan to look into this when I can, but if anyone else is bored, feel free.
Sample of Quicksilver.txt

Do you have your TaskViewer pop up automatically by any chance, or is the task viewer visible somewhere (perhaps off-screen)?
Again, this looks like a QSTask issue as opposed to an actual catalog scanning issue, so that's probably where I'd look first.
I'm thinking that the task is trying to start (on the main thread) which then means a UI refresh is needed, but that can't be done because the task is blocking the main thread. Or something like that at last.

This seems to always be caused by -[QSLibrarian reloadSource:] and -[QSLibrarian scanCatalogIgnoringIndexes:] getting called on different threads.
I think the answer might be to wrap reloadSource: with
dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_LOW, 0), ^{})

So they’ll both be run in the same queue and can’t lock each other. Sound right?

Yes, that was my immediate thought as well, although I suggest you use the built-in QSGCDAsync, OR we create a specific queue for rescan tasks and use that queue (I have a vague recollection that that's been done/I did that before - but not sure)
[goes and looks] - yep, here's my PR: https://github.com/quicksilver/Quicksilver/pull/1497
Doesn't look like there was any real reason why that wasn't merged. And you said you tried it out and it seemed OK. Perhaps it's worth re-implementing those comments and seeing. But yeah, I would recommend creating a single named thread for catalog scanning, using dispatch_queue_create and storing it as an instance variable of QSLibrarian. (see here and  here )

Note: the fix for this (to move scanning to background threads and make it async) is good - doesn't lock the UI. However it now causes the issue at #2718
Currently debugging