Posts are being served as text/plain

My setup worked on v3 but I can't figure out how to make it work on v4. My directory structure looks like this:
source/posts/2015-06-22-some-title.md
source/posts/2015-06-24-some-other-title.md

My URLs look like this:
http://myblog.com/some-title
http://myblog.com/some-other-title

On v3 my config looked like this:
activate :blog do |blog|
  blog.sources   = "posts/{year}-{month}-{day}-{permalink}.html"
  blog.permalink = "{permalink}"
  blog.layout    = "post"
end

Having to append .html to the end of sources was always kind of weird, but it worked. In v4 I have:
activate :blog do |blog|
  blog.sources   = "posts/{year}-{month}-{day}-{title}"
  blog.permalink = "{title}"
  blog.layout    = "post"
end

Now they're displayed correctly on the main page, but if I go to a permalink page it's served as text/plain instead of text/html. How do I get the correct behavior?

Your posts must use .html.md extension instead of .md.

Oh. Why? They didn't before?
I understand the “tilt” pattern, but it doesn't seem to make any sense here. It makes sense for templates (foobar.html.erb), because it's HTML that you want to be parsed as ERB first. But these posts are not HTML with markdown in—they're just markdown, which happens to be converted to HTML. They're data, not templates.
That pattern was also created to handle the case where the final type is unknown. It could be foobar.html.erb or foobar.js.erb. Other middleman pages need that flexibility because they're templates—you might want to generate an XML feed or something. But the blog posts are always going to be HTML.
Right?

See https://github.com/middleman/middleman-asciidoc/issues/7#issuecomment-170076370.
You are right, but I quite like the explicitness.
I imagine it makes the underlying code simpler and easier to reason about, you just pop off each extension but the last and run it through Tilt.
Layouts aren't rendered on their own so it follows that they have no .html extension.
If someone does want to serve a raw markdown file with the .md extension they can do that - the user defines the file extension/mine-type explicitly.
As you say, you still had to be explicit in the past for stuff like foobar.erb -> foobar.js.erb or feed.slim -> feed.xml.slim. May as well do this everywhere.
That said, this is apparently missing from the docs - I couldn't find mention of it in the 'upgrading to v4' section. :/

Ah, it didn't occur to me to add/override the mime type for markdown! Although, I can't seem to figure out how to do that... this didn't work:
mime_type :md, "text/html"

Any idea what I'm missing?

I meant that a .md file would be converted to .html automatically before. Which might be a nuisance if you actually (for some reason) wanted to serve a raw version without converting it, while still having .md path.
To actually rewrite the destination path to use .html you can do this: https://github.com/middleman/middleman-asciidoc/commit/e2fb71e1e6d4dc8d25cca7fcee5f5f4305a7e3d4
Which involves making an extension and defining a method like this:
def manipulate_resource_list(resources)
  resources.each do |resource|
    File.extname(resource.source_file) == '.md'
    resource.destination_path << ".html" unless resource.destination_path.include? ".html"
  end
end

Oh, I see what you meant. Thanks so much for your help!
(I think you meant to wrap the path appending in an if statement with the line above it?)

Whoops, yep - fixed. If you get it working you might want to throw it in a gist so other people can use it, might help others who are upgrading. =]


AMQP-643: Doc Polishing

JIRA: https://jira.spring.io/browse/AMQP-643

Merged as https://github.com/spring-projects/spring-amqp/commit/29e89d1562b5692e175b7b39a155b1153150709c


docs(license): update to match LICENSE file

Seems that license in package manifest and the LICENSE file differ.
I suspect the correct is the LICENSE file so I updated the manifest to match

Coverage remained the same at 99.515% when pulling 5c09d7fe2775a6c5f7a1deb8a185212823473dad on lirantal-patch-2 into e6fc4188c3f8d311d8bf84d8e7f40d89fc9456a2 on master.


Move to JRE instead of JDK for container

Coverage remained the same at 88.688% when pulling 47ae3f1c65b8861b520b5f87a19d4961809050b9 on tgianos:master into 8eceddddf29bf96f24d36cf2058f87bd6f3df036 on Netflix:master.


allow unknown options

Description
As mentioned in #1164 and #1188 , some time run build by shell or gradle or build in jenkins, the vars need passed by command, and can not by env.
We really need this feature.
Eg:
for dev and local test pass
pnpm build -- "--sourceMap=true" "--outputDir=build/dist"
for test delpoy into docker pass
pnpm build -- "--sourceMap=true" "--outputDir=docker/dist"
for product delpoy into docker pass
pnpm build -- "--sourceMap=false" "--outputDir=docker/dist"

Suggested solution
Support unknown options, just passthrough the args.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I still don't think we should do this, and there hasn't been enough request to justify it.
Maybe you can wrap the vite CLI and remove these args before calling Vite?


[PoC] Snack bar component

Create a new snack bar web component.
This component is for displaying "notifications" inside the web application. Some examples:

Asynchronous feedback from a previous task
Feedback from an external process

Other implementations:

https://dna.iddinkgroup.com/?path=/story/core_overlays-snack-bar-examples--api
https://material.angular.io/components/snack-bar/overview
https://nordhealth.design/components/toast-group/
https://web.dev/building-a-toast-component/

Requirements:

It should provide an API for displaying notifications
Displaying notifications should be handled by a "controller" component (<sl-snack-bar-controller>)
API & controller should be loosely coupled (events)
Controller should handle multiple notifications at the same time (stack them)
It should be accessible (aria-live?)
For this initial version, only allow message: string and autoClose: boolean, type: 'info' | 'success' | 'error'

https://loihdefactor.com/fi/2022/04/29/building-testing-tools-for-aria-live-regions

Thanks for these links @furstenberg Really interesting!
https://adamsilver.io/blog/the-problem-with-snackbars-and-toast-messages/

I have many more related to the other components that are going to be made, so let me know if they are of interest.
Itslearning have spent quite some time on accessible components.

@furstenberg Of course we're interested in your expertise! Feel free to keep commenting on issues and certainly join in the discussions: https://github.com/sanomalearning/design-system/discussions
We will keep doing our research before each component we make so if we have specific questions regarding an interaction we'll get in touch!

📝 put back on backlog until we've figured out how (if) we should make this in an accessible way

https://github.com/sl-design-system/components/discussions/149


MCS-674 Removing evaluation-related code

AWS credentials, S3 buckets, evaluation mode, team name are all removed from the python api. This draft PR opens the door for debate on the merits of moving file uploads (history, logs, video recordings) to the pipeline. The python api will be focused on running scenes at various metadata levels and providing the json or imagery recordings for researchers to use.

@kdrumm File renaming can happen, as you suggested, in the pipeline itself. Since the pipeline is the authority on team and evaluations names, it seems apt to be handled there.

So this code looks good to me, but we probably can't merge this until we have coverage in the pipeline for everything we are taking out correct?  Or at the least a way to track all of it?

@brianpippin I don't think so. It's all in git somewhere if we need to copy code to the pipeline.

I would think this would be another case of parallel PRs in both repos (mcs and mcs-pipeline) that are both reviewed before either are merged.  Just like when we have changes in MCS and AI2Thor that are dependent on each other.

I am also in favor of this change. The code looks good -- you did a nice job cleaning up some things too.

I am also in favor of this change. The code looks good -- you did a nice job cleaning up some things too.

I snuck some stuff in there.


Link to Best Practices Analyzer is outdated?

The link to the Best Practices Analyzer links to a page, which is applicable to Windows Server 2008 R2. Is this really the latest?

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

ID: 3e8b8354-682b-74f8-324b-205b1ed3629b
Version Independent ID: c3473722-b5a4-7e20-7c5f-a401b42b2344
Content: Best Practices Analyzer for Hyper-V
Content Source: WindowsServerDocs/virtualization/hyper-v/best-practices-analyzer/Best-Practices-Analyzer-for-Hyper-V.md
Service: na
GitHub Login: @KBDAzure
Microsoft Alias: kathydav

I know this is a very late reply, but there is a 2012 R2 version of the page.
I will make an effort to find the related links and create a pull request to have the links updated.
The best case scenario will be that I can manage to get more than 1 link changed to use the newer version, maybe even get a link to the 2016 PowerShell cmdlet page into the mix.

I have been searching through the pages underneath https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-on-windows-server , but could not find any TOC links to pages related to "Best Practices Analyzer for Hyper-V" for modern server versions:
Hyper-V on Windows Server (Get started, Plan, Deploy, Manage) :

https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/get-started/get-started-with-hyper-v-on-windows
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-hyper-v-on-windows-server
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/deploy-hyper-v-on-windows-server
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/manage-hyper-v-on-windows-server

I suspect that what we are looking for is mainly documented in the PowerShell repository for modern servers.
For now, I can only locate the specific page for "Applies To: Windows Server 2012 R2, Windows Server 2012" as an improvement to the 2008 R2 version:

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn283329(v=ws.11)

PowerShell BestPractices Module:

https://docs.microsoft.com/en-us/powershell/module/bestpractices/?view=win10-ps

There you go. PR #4896 is ready for review. I have postponed other link changes as a solution to other potential ticket reports for outdated links.


Added WindowClosingEventArgs.

What does the pull request do?
Adds WindowClosingEventArgs and uses it for Window.Closing. This API allows the event listener to detect:

Why the window is closing
Whether the close was done programmatically or via user interaction

Note that WindowCloseReason.OSShutdown is included but not currently supported by any platform backends. Not sure how we should handle this:

Implement it as part of this PR?
Remove the enum value for now?
Add a note that not all platform backends may support this enum value and may send ApplicationShutdown instead?

Fixed issues
Fixes #9524.

You can test this PR using the following package version. 11.0.999-cibuild0027611-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0027712-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


Provide readme to configure the debugger for Camel

based on https://microsoft.github.io/debug-adapter-protocol/implementors/tools/ , there are 2 extensions possible:

https://github.com/puremourning/vimspector
https://github.com/mfussenegger/nvim-dap

Vim inspector sounds more advanced; i think we should go with this one.

Provided readme to configure the debugger for Camel #2


TypeEngine.with_variant should accept TypeEngine for type argument instances as well as Type[TypeEngine]

Describe the bug
Documented usage for TypeEngine.with_variant() as here https://docs.sqlalchemy.org/en/14/core/type_basics.html#using-uppercase-and-backend-specific-types-for-multiple-backends
Uses an instance of a TypeEngine for the type argument like is usually done with Column for example. This gives a type error with current type stubs
Expected behavior
Documented usage with both an instance and a TypeEngine class directly should both work.
To Reproduce
from sqlalchemy import Integer

# TypeEngine.with_variant should accept both a TypeEngine instance and the Concrete Type
Integer().with_variant(Integer, "mysql")
Integer().with_variant(Integer(), "mysql") # Fails type_checking before this change
# Also test Variant.with_variant
Integer().with_variant(Integer, "mysql").with_variant(Integer, "mysql")
Integer().with_variant(Integer, "mysql").with_variant(Integer(), "mysql")  # Fails type_checking before this change

Versions.

OS: Ubuntu 22.04
Python: cPython 3.10.6
SQLAlchemy: SQLAlchemy==1.4.41
mypy: Whatever runs with tox setup in this project
SQLAlchemy2-stubs: 0.0.2a27

thanks for reporting


HttpServer is slow for web application

I am using sd card.
I found out it is very slow.
I guess HttpServer class is single thread. Can we improve it to make multi threader.
It could be due to sd card read is slow. I will try to copy all my web files on spiffs and try it.

My web application is big size with images. cannot fit into spiffs.


@azure/keyvault package doesn't generate package.json

Will be fixed in https://github.com/Azure/azure-rest-api-specs/pull/4429


Load a base theme that provide defaults for all required keys

Currently, each theme must provide all required values or else the converter will crash. It would be better if a theme only had to specify values for keys it wants to override / customize. This can be accomplished by introducing a base theme. The base theme should be loaded before the specified theme and provide defaults for all required values.
You can think of the base theme as a “CSS reset”.

The base theme also allows us to introduce new theme settings without the risk of breaking existing themes.

Once we have a base theme in place, we should remove all the unnecessary fallbacks when we check for keys...or, these fallbacks should be preconfigured.
Case in point:
@theme.prose_margin_bottom || @theme.vertical_rhythm

We have to assume we're going to have a value for the prose_margin_bottom key or the code is just ugly.

Now that I have Asciidoctor PDF 1.5.0.alpha.8, do I assume that theme base + overriding is working yet, or do I still need to copy the base theme?

It's best to start with the default theme and modify it at this point. I'm
still working on the base theme feature. It will make the next release
(alpha.9 or beta.1).

Hi guys, i'm using alpha8 and can't load my custom theme. I've just put my theme file in same directory as my adoc document  and ran asciidoctor-pdf myfile.adoc. The theme file is name myfile-theme.yml

managed to load my theme using pdf-style and styledir options:
´´´
asciidoctor-pdf myfile.adoc -a pdf-style=myfile -a pdf-stylesdir=/home/pestano/projects
´´´
It would be nice if it used adoc file path as default pdf-stylesdir and adoc filename(plus -theme sulfix) as default pdf-style. If no pdf-style is found then use basic-theme.yml.
Does it makes sense? I think it should work like docinfo.html

Please file a separate issue for this enhancement and we'll discuss /
design / consider it there. Thanks!


Release 'Publish Build Artifacts' fails with 'Unable to find container for build'

Hi, I am trying to publish some test results from the release agent working folder using the task 'Publish Build Artifacts' that I put into my release definition, but it fails with:
##[error]Unable to find container for build: 88
I think 88 is the id of the build that triggered the release.
Interestingly, I have another 'Publish Build Artifacts' in my build definition and that works just fine.
Here is the task setup from my release definition

And this is all the log output of the task:
Set workingFolder to default: C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\1.99.0\tasks\PublishBuildArtifacts\1.0.30
##[debug]loading inputs and endpoints
##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
##[debug]loading INPUT_ARTIFACTNAME
##[debug]loading INPUT_ARTIFACTTYPE
##[debug]loading INPUT_PATHTOPUBLISH
##[debug]loading INPUT_TARGETPATH
##[debug]loaded 5
##[debug]check path : C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\1.99.0\tasks\PublishBuildArtifacts\1.0.30\task.json
##[debug]set resource file to: C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\1.99.0\tasks\PublishBuildArtifacts\1.0.30\task.json
##[debug]system.culture=en-US
##[debug]PathtoPublish=C:\a\1196b1921\requirementsCoverage.html
##[debug]check path : C:\a\1196b1921\requirementsCoverage.html
##[debug]ArtifactName=ReqirementCoverage
##[debug]ArtifactType=Container
##[debug]TargetPath=\my\share\waverage.feature\waverage_plan_in_traderwebapp_2016_05_18.5
##[error]Unable to find container for build: 88
Could you help me find out what the problem is?
Or in case this task is not supported in a release definition, is there a way around this? Something like using cUrl or powershell to attach the files to the release using the VSO Rest API?

The output from above is not from this agent that is in this repo.  Please log your issue in the tasks repo
https://github.com/Microsoft/vsts-tasks


CDRIVER-2955 CSharp Bindings

CSharp Bindings

Thanks so much Mark! 😸 Per an offline discussion, the .NET team will be using your branch as a basis for a future PR and closing this PR.


router top file：Confused about ns_con

Sir, I'm confused by this "con", I guess it's an abbreviation for connection, but what about the ns in front of it? Why only ns, sn, not nw, ne? Can you answer my doubts when you have time? Thank you very much!
router_if ns_con [(NoCCfgSzRows+1)NoCCfgSzCols] ();
router_if sn_con [(NoCCfgSzRows+1)NoCCfgSzCols] ();
router_if we_con [NoCCfgSzRows(NoCCfgSzCols+1)] ();
router_if ew_con [NoCCfgSzRows(NoCCfgSzCols+1)] ();

Hi @Elena32061
please add a link to the particular line in the file you're talking about. The abbreviation of con means connection and the reason why I have only ns/sn/we/ew it's because you have only wires in XY direction between routers, take a look at this image down below.

I'm sorry, sir. I didn't think hard about this question。  Thank you for your patience


testing/quick: variadic function causes panic

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go1.9
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
Linux amd64
What did you do?
Try to call quick.Check(f, nil) where f has a variadic argument
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
https://play.golang.org/p/7jvo72sHT5
What did you expect to see?
"Check looks for an input to f, any function that returns bool, such that f returns false."
No panic.
What did you see instead?
panic: reflect: cannot use []int as type int in Call
goroutine 1 [running]:
reflect.Value.call(0x1304a0, 0x164d14, 0x13, 0x1451c5, 0x4, 0x1050a0c0, 0x1, 0x1, 0x0, 0x0, ...)
/usr/local/go/src/reflect/value.go:382 +0x1280
reflect.Value.Call(0x1304a0, 0x164d14, 0x13, 0x1050a0c0, 0x1, 0x1, 0x105442a0, 0x14ba01, 0x0, 0x0)
/usr/local/go/src/reflect/value.go:302 +0xc0
testing/quick.Check(0x1304a0, 0x164d14, 0x0, 0x0, 0x113ca0, 0x7f47)
/usr/local/go/src/testing/quick/quick.go:289 +0x2c0
main.main()
/tmp/sandbox034499881/main.go:9 +0x40
Program exited.

I'm unsure what the exact status of testing/quick is. It was on a short-list not long ago of packages to freeze. See #15557.

Ah, yes. It is indeed documented as being frozen: https://github.com/golang/go/blob/e25fdb968c4ff93c6d41574f2220a11ee02b0914/src/testing/quick/quick.go#L7
Given that this panic occurs because of a function signature entirely within the control of the user is passed to the package, I would consider this a feature request to add support for variadic functions. However, we're not extending the API of this package, so I'm going to close this.
Thanks for reporting. Feel free to fork and develop quick further if you use the package heavily.

However, we're not extending the API of this package, so I'm going to close this.

A fix will not extend the API of the package, and will not break existing programs because the only ones that the fix will affect will panic right now. I don't mind if this stays closed but fixing this would not require changing the API of testing/quick.

I should have said "not extending the feature set" rather than "not exstending the API". My mistake.


Tests ensuring the server integrity when running third-party code

A small suite of tests for ensuring that the deployed docker container works, and does not leak any more information that it is needed.
I've included three simple tests:

The endpoint works
The endpoint recovers from someone calling System.exit
The endpoint does not expose anything of interest through sys.env

If you can think of other tests, please let me know.
I've kept these tests separate from other endpoint tests in the code as this is really to make sure that the endpoint works, rather than the functionality of the endpoint itself.
--
These tests sit in their own SBT package, and are currently not run as part of any automated build.  Due to Docker on Heroku being in beta and still very new, it is not possible to use Heroku's deployment pipelines with Docker yet. I think we have a few options here as to what to do with them.

Run the tests when Travis is triggered to deploy a Docker container, and notify of any issues. Manual intervention to fix/rollback.
Set up our own pipeline, deploying to a different staging URL, running the smoketests there and deploying to the production URL on success. Will have to be hand-rolled, but I don't think this would be much effort.

Once Heroku can deploy pipelines of Docker containers, we should definitely move over to using that.
@raulraja Thoughts? I think setting our own pipeline wouldn't take very long and I'm all for no manual intervention, but as I'd be hand-rolling this, I just wanted to see what you think before I go down this route.
Resolves #39.

Thanks, merging. FYI, I've added a line in the .travis.yml file to run these tests after a Docker deployment.


[FLINK-35742] Don't create RocksDB Column Family if task cancellation is in progress

We observe a lot of TMs stuck for > 30s in RocksDBHandle.registerStateColumnFamilyHandleWithImport which boil down to native calls to create Column Family. This change registers prevents CF creation if task cancellation is in progress.

What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
Brief change log
(for example:)

The TaskInfo is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change
Please make sure both new and modified tests in this PR follow the conventions for tests defined in our code quality guide.
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluster with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

@flinkbot run azure
please


Default outputStyle to compressed in release mode

Good idea. Could you add a CHANGELOG entry for another dot release?

Of course! Would you like me to bump the pubspec and everything else necessary for release? Or just the CHANGELOG entry?

AFAIK No other changes planned in the near future. I'll merge and publish.

Thanks!


Scoped clients

Adds a new .scoped operator on URLRoutingClient that can be used to create scoped clients.
This supports a use case where your main client may support a large number of routes and you only want to be able to pass around a client that handles a sub-set of those routes as a dependency.
For instance, imagine a feature domain within a TCA app - your AppEnvironment may hold onto a URLRoutingClient<AppRoute> client but your account feature may only need to make requests to account-related routes, so you'd like to pass a URLRoutingClient<AccountRoute> client to that domain's environment, limiting its scope and making it easier for you to find the right route at the call-site.
I debated over whether or not to call this scoped or pullback - I think the shape of this function is a pullback but the term "scope" or "scoped" felt more ergonomic to me in this context.
Also added some basic tests for the client.
Suggestion - consider adding some integration tests of the live implementation using a mock server. There's a few available (I've found https://github.com/surpher/PactSwift really easy to use although its use cases extend beyond simply creating a mock server).

This is great. I followed your thought process in your other thread and I think you're onto something very important here.
As a side note, I think it might be good to drop the "d" and call it scope so it matches TCA's nomenclature. What do you think?

@davdroman for consistency you might be right, but to me scope reads like its mutating the receiver, where as scoped implies that it's returning a new client (which it does).

Hey @lukeredpath! Thanks for the PR.
We can theoretically see this being useful but would love to take it for a spin, ideally both in our episode demo and a larger project like isowords, to see how it can help. We briefly explored a variant of scoping while developing the library, but found that our solution wasn't useful on pointfree.co because our features rely so much on cross-linking to other parts of the site.
If you've used this method in a real world code base, we'd also love to see more examples and/or hear more about how it's worked and improved things, as well as any caveats you encountered!

I did try using this in a project, and wanted to share one small wrinkle I found, in case this were ever picked up again.
I wanted to do something like this:
import Dependencies
import URLRouting

extension URLRoutingClient<ApiRoute>: TestDependencyKey {
  public static let testValue = Self.failing
}

extension DependencyValues {
  public var apiClient: URLRoutingClient<ApiRoute> {
    get { self[URLRoutingClient<ApiRoute>.self] }
    set { self[URLRoutingClient<ApiRoute>.self] = newValue }
  }
}

extension URLRoutingClient<ApiRoute> {
  public var books: URLRoutingClient<BooksRoute> {
    .init { booksRoute in
      try await self.data(for: .books(booksRoute))
    }
  }
}

so that I could then use it like this, as a means of minimizing what routes a feature is requesting access to:
@Dependency(\.apiClient.books) var booksClient

However, I quickly realized my computed client, and I think the scope implementation in this PR, is not passing along the URLRoutingClient's configured JSONDecoder. Which I think you'd really want to do, and not hard-code a custom decoder in every extension, so that it remains configurable from the top level.
However, URLRoutingClient holds on to that decoder internally, so I think this kind of scoping is currently not possible in an extension.
So, either a shipped .scoped operator would want to pass along the decoder, or perhaps the decoder could be made public, so this kind of scoping would be possible ad-hoc via extension.

@kamcma what do you mean by configured decoder? I don’t see any decoder in the client, except for the one you pass in when calling the particular request overload that takes one.

Ah, forgive me for framing it as an omission. That possibility had not occurred to me.


Bug fix: SpawnPointId should be SpawnpointId

Better just add the upper P here :
https://github.com/Armax/Pokemon-GO-node-api/blob/master/poke.io.js#L358
No ?

==> #117

@TomVivant Whatever works I guess


refractor: deleted local img, update it with hosted img, reorder & up…

Related Issue
#95

Info about the related issue

This will lessen the image file size.
Describe the changes you've made
Give a clear description what modifications you have made

Deleted some local images
Hosted the images on GitHub & updated the URL source
Reorder and change team member title.

Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Describe how have you verified the changes made
Checklist:

[x] My code follows the guidelines of this project.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly whereever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots

Original
Updated

N/A
N/A

sorry I missed it XD


nep-Y: add verify NEP

@roman-khimov  please update.

Please merge #179 first, there are gonna be conflicts in README.


Can't find the issue in the save nor can parse it to look at it.

Error
An exception was thrown (press Ctrl+C to copy):
System.ArgumentException: count exceeds buffer bounds
at ICSharpCode.SharpZipLib.Zip.Compression.Inflater.Inflate(Byte[] buffer, Int32 offset, Int32 count)
at ICSharpCode.SharpZipLib.Zip.Compression.Streams.InflaterInputStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at Gibbed.BorderlandsOz.FileFormats.SaveFile.Deserialize(Stream input, Platform platform, DeserializeSettings settings)
at Gibbed.BorderlandsOz.SaveEdit.ShellViewModel.<>c__DisplayClass58_0.b__2()
at Caliburn.Micro.Contrib.Results.DelegateResult.Execute(ActionExecutionContext context)
OK
Getting a cStringIO error when I try to parse the save, but other saves are parsing just fine.

Can you attach a copy of the save?

https://www.mediafire.com/file/sdf3eku6jtle7jv/Nisha.zip/file


//cy.checkForBrokenImages(

:tada: This PR is included in version 5.12.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Graftorio addition

Add graftorio for Grafana integration of some sweet production graphs etc.
Sourced from TheVirtualCrew/graftorio (modified for scenario usage and not a mod) with big thanks to Tim Vroom.

Closing because the mod has some bugs and I put it in my backlog.


Reconsider if Vespa CLI should require test package for prod deployment

Vespa CLI currently requires tests to be present when submitting an application package to production (vespa prod submit). Do we still want to enforce this requirement?

No; the sever side will enforce it if and only if tests are specified in deployment.xml.


Please test if we can depend on MPCF as a full mux replacement

Note: MPCF == Multipeer Connectivity Framework
The goal of this bug is to determine if we can directly bridge TCP/IP connections from the node layer to the iOS native layer by mapping each TCP/IP connection's individual input/output stream to pairs of 'virtual sockets' in the MPCF layer.
A 'virtual socket' is a pair of output streams going in each direction (e.g. an output stream from A to B and from B to A) that we will map to an individual TCP/IP connection's two streams.
To test if this goal is possible we need to write a test application that does the following:

Use two phones, each phone MUST run identical test software doing identical things with the exception that it's fine to just anoint one phone as the phone that will invite the other phone to a MCSession
Each phone MUST open N output streams at the MPCF layer to the other phone (where N should default to 20). Over each of these output streams the phone MUST output Y bytes of randomly generated data (Y can start at say 10 MB). Each group of bytes MUST be sent in randomly sized buffers from 1 to 4KB in size. The randomly sized buffers simulate TCP's behavior of sending different buffer sizes. Each phone MUST then wait for the other phone to echo back the data it sent and then the phone MUST confirm that it was echoed back the same data it was sent. When all N connections successfully send and get echoed back Y bytes then the test is a success on that phone.
Each phone MUST listen for incoming streams from the other phone and MUST generate a matching outgoing stream that echoes the bytes received. The echoed bytes MUST be sent in the same buffer sizes they were received. The phone will know it no longer needs to echo data when it has created N echo streams each of which has successfully sent Y bytes of data.
Each phone MUST NOT be connected to a wifi access point while this test is run. Otherwise the test will be bogus because when iOS devices are connected to WiFi they will just use local TCP/IP across the access point to move the data. Therefore both WiFi and Bluetooth MUST be turned on but the WiFi MUST NOT be connected to any access point.

So the above means we will send N streams * Y bytes * 2 times (once out and once echoed back) * 2 devices worth of bytes.
I will discuss a possible architecture for this test code below but how you implement the code is up to you. The key thing is to go to create a GitHub repo some place and start it with no content and configure it to support reviewable.io. Then submit a PR with the XCode project to it. The code review I will then perform will have the goal of both letting me review how you attacked the problem but also how you deal with multi-threading, code style issues, etc. It's a good dry run to understand how we want code to be written. I'll also want to run the test locally.
Optional Architecture
You do not have to implement the code this way. It's just a suggestion and hopefully will clarify goals even if you take a different approach.
Now a fairly simple architecture to implement the previous would be that each phone would have a main thread that would fire off N output workers.
Each output worker would generate a GUID and that GUID would then be entered into a global dictionary indexed by GUID. Each entry would have associated with it a LIFO queue of bytes. The output worker would then open an output stream with that GUID as its name.  The output worker would then start generating Y bytes of data using a random number generator stream outputter and would output those bytes in buffers of size 1 to 4K bytes where the actual buffer size will be randomly picked for each output event (in other words the first buffer might be 10 bytes, the next 1234 bytes, the next 23 bytes, the next 10 bytes, etc.). The various buffer sizes are meant to simulate TCP/IP's random buffer sizes. While the worker is outputting the bytes to the output stream it would simultaneously put those bytes into the LIFO queue in the global dictionary associated with the output worker's GUID. Each worker would exit when it finished transmitting its Y bytes. [Note: You actually don't need a GUID. You could also just pass in a counter created by the main thread to each worker, so long as each worker gets a different counter value then it can use that value as its index and stream name and everything will be fine]
Simultaneously there would be a listener for input streams. Whenever an input stream is received an input worker would be assigned to it. The first thing the input worker would do is see if the stream's name is in the global dictionary of GUIDS mentioned above.
If it is not then the input worker would immediately open an output stream to the other device with the same name as the input stream. The input worker would then take any buffers of bytes received from the input stream and immediately copy them using the same buffer size to the identically named output stream. The input worker would count how many bytes it has sent and when it reaches Y bytes it will know it is done and can exit.
If the name of the input stream is in the global dictionary of GUIDs then this means that the stream is an echo back to the local device of bytes it has sent to the remote device. In that case the input worker needs to look up the LIFO in the global dictionary for that GUID and start matching the incoming bytes it is receiving against the bytes in the LIFO. If there are any mis-matches (e.g. bytes received on the input stream don't match the bytes in the LIFO) then an exception MUST be thrown and the test MUST fail. If all Y bytes are received and matched then the input worker will exit.
The main thread knows the test is over when the N output workers successfully exit and when 2N input workers (N of which are just echo'ing the other devices bytes and N of which are confirming echos sent over from the other device) successfully exit.

We should have this finished by tomorrow.

The current issue is that we aren't getting any data back or at least it hangs for a long time before showing up. Also it turns out that the current test isn't symmetric, the initiator is the only one who starts sending data and the other device just responds. We need the test to be symmetric. So Alex will fix the test and also test with N = 1 to see if data flows when there is just one connection as Toby found of if the problem is something in his code. Alex will also look at Toby's old code to see how he handled things and we'll start a thread with Toby to see if he has any advice.

It works!!!!!!

@yaronyg, I've implemented a test app with architecture you've mentioned above.
You can look on it here:
https://github.com/baydet/MPCF_Mutltistream_Test
to specify who is the master and who is the slave you should pass -server 0 or -server 1 to command line. Also in Constants.h file you can change parameters (size of transferring data, size max size of single bunch of data)
In the first version of this app I have some issues with multithreading (deadlocking) which causes NSStream freezing. So I assume that we have similar nature bugs with Thali.

@baydet Unfortunately the current code does not appear to implement the spec as above. If I read the code correctly (you can see my notes in #779) then the biggest problem is that there doesn't appear to be any validation that the data that is reflected back is the data that was sent. This is critical because otherwise we have no idea if useful data is actually flowing. If I'm reading the code correctly then I believe that OutputDataGenerator needs to record the data it outputs. Then didReceiveStream in MultipeerSession, when it receives an incoming stream with retr_ in it, has to compare it against what OutputDataGenerator has outputted. Just remember that the size of buffer we output isn't going to necessarily equal the size of buffer we get back so we need to store the output bytes as a flat byte array and then compare the input bytes against it. If you can use a LIFO queue then you can push bytes in as they are generated and pull them out as they are validated on the return channel. But you will still have to keep track of total byte count so we exit when we have got all the bytes.
Also we MUST validate as bytes are received. We MUST NOT wait until they are all received on reflection before validating. If we do that we are not coming even close to the way data flows in a real app. So every time data comes in on a retr_ stream we need to validate it as we get it.
There should also be some explicit event that fires and displays something when we have validated all the data against all the retr streams.
I also suspect there is a bug in DataStream.m/InputDataStream/readData. It will read up to kStreamReadMaxLength but depending on how the data gets buffered there can easily be more information than that. I suspect that if all the available data isn't read (say in a while loop that goes until there is no more data available) then we aren't going to get any more hasBytesAvailable notifications telling us to read data that has already arrived. So I'm guessing we need that while loop.
Also is dataForStream in DataBuffer in DataGenerators implementing a busy wait in this line? Sorry if I'm confused. I'm not an expert in Objective-C. But it looks like it's going to sit in that while loop when the buffer is empty until the readingDidEndForStream gets called or data gets added. If it is a busy wait then it needs to be changed to an asynchronous pattern.

Yes, you're right - it's busy waiting. In this implementation I'm sure that this code will not produce deadlocks. Also I did not care a lot about resources management. The key point for this project is checking possibility of multistream connection with MPCF. So because of that I haven't put key focus on app's threading architecture.

Please re-implement the project in Swift 2.2
Please put in a random (very short, no more than 1 second, usually closer to 200 or 300 ms) delay in outputting day to replicate the kind of bursty behavior we see with TCP
Please change the validator that checks that what is reflected is what we sent so it can handle very large streams

Then please re-run the tests with much larger data, say 1 Gig total across all streams

@yaronyg, I've implemented swift version of these changes. You may check it here
https://github.com/baydet/MPCF_Multistream_Test/tree/swift. All the code stored in MPCF_Multistream_test-swift folder
Also I've change architecture a bit to make it more clear.
But I have no time today to run it on 1 gig of data.

@baydet Please run the code on three phones, one as leader and the other two as followers.


Add style prop to create cards/containers

What does this PR do?

Gives users the ability to add styling to the entire accordion container. We needed to create cards for each header item in the accordion that were seamlessly connected to header. Please see the image below.

Anything Else We Should Know?

Your PR process requests that we push to the next branch, but I only see master.

Images

Man that is a beautiful app 💯, seems like a duplicate of #246 . However if you can finish the changes before, then i'll merge yours.
Still need to add typescript definitions and fix the ci

@iRoachie Sorry I added the wrong picture, but the new one is up with the Accordion in full force. I'll take a look into #246 and Mr. Travis.

@iRoachie how do you run the ci locally? I don't have this '.' it speaks of.

You can run npm run test --fix and see if that works

@iRoachie helps if you npm i 😞. I think this last push should do the trick.

Lastly can you add it to defaultProps https://github.com/oblador/react-native-collapsible/blob/b21aa79e565f0478c243d0ec347df39bc48a55d9/Accordion.js#L31

Oops forgot the docs! Add it to the readme

Ok this time for real! Sorry for the back and forth.

Thanks mate! Release will be out soon


faker 17.6.0

Recipe directory diff between current master and this update:
diff --git a/recipe/meta.yaml b/recipe/meta.yaml
index 29fe4e4..03d0f9c 100644
--- a/recipe/meta.yaml
+++ b/recipe/meta.yaml
@@ -1,4 +1,4 @@
-{% set version = "8.8.1" %}
+{% set version = "17.6.0" %}

 package:
   name: faker
@@ -6,7 +6,7 @@ package:

 source:
   url: https://pypi.org/packages/source/F/Faker/Faker-{{ version }}.tar.gz
-  sha256: ccd76cd86a49f1042811faaa3a7d1b094fcf8e60a1ec286190417bbb5a3f2f76
+  sha256: 51f37ff9df710159d6d736d0ba1c75e063430a8c806b91334d7794305b5a6114

 build:
   number: 1

Jira ticket:  (-)
The upstream data:
Github releases:  https://github.com/joke2k/faker/releases
Diff between the latest and previous upstream releases
License: https://github.com/joke2k/faker/blob/master/LICENSE.txt
Changelog: https://github.com/joke2k/faker/blob/master/CHANGELOG.md
Requirements:

setup.cfg:  https://github.com/joke2k/faker/blob/v17.6.0/setup.cfg
setup.py:  https://github.com/joke2k/faker/blob/v17.6.0/setup.py

Actions:

Notes:
*
Additional info:

Package's statistics

Priority D | effort: easy | Category: other | subcategory:  | pkg_type: python
Outdated platforms: 'linux-64', 'linux-aarch64', 'linux-ppc64le', 'osx-64', 'osx-arm64', 'win-64'
Latest version: 17.6.0
Release on PyPi:

version: 17.6.0
date: 2023-03-03T16:59:17

PyPi history
Popularity:

3 months downloads: 37459.0
All time:  726076 downloads -  faker  17.6.0  Faker is a Python package that generates fake data for you

Other checks:

[ ] Check the pinnings

[ ] Verify that the 'build_number' is correct

[x] has 'setuptools'

[x] has 'wheel'

[x] 'pip' in test

[ ] Verify the test section

[ ] Verify if the package is 'architecture specific'

[ ] Verify that private modules are not mentioned in the recipe For example: (_private_module)

[x] license_file: LICENSE.txt is present

[x] license_family MIT is present

[x] License: MIT
[x] License is 'spdx' compliant

Check if the license identifier has correct name from the SPDX License List

Identifier

HPND-sell-variant-MIT-disclaimer

MIT

MIT-0

MIT-advertising

MIT-CMU

MIT-enna

MIT-feh

MIT-Modern-Variant

MIT-open-group

MIT-Wu

MITNFA

Check dependency issues:

../aggregate/faker-feedstock/recipe/meta.yaml
Dependencies: ['python >=3.6', 'setuptools', 'pip', 'wheel', 'python-dateutil >=2.4', 'text-unidecode ==1.3']
noarch:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

linux-64:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

linux-ppc64le:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

linux-s390x:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

osx-64:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

osx-arm64:

py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

win-64:

py3.7:  No issues found
py3.8:  No issues found
py3.9:  No issues found
py3.10:  No issues found

**Other:**

Checking 'faker' recipe...
~/OneDrive - SoftServe, Inc/src/aggregate/faker-feedstock/recipe ~/OneDrive - SoftServe, Inc/src/finder
>>> Easy: noarch python recipe <<<
--- Build Requirements ---
>> Empty Host Section <<
--- Host Requirements ---
pip: main
setuptools: main
wheel: main
--- Run Requirements ---
python-dateutil >=2.4: main
text-unidecode ==1.3: main
~/OneDrive - SoftServe, Inc/src/finder

https://repo.anaconda.com/pkgs/main/noarch
faker-8.8.1-pyhd3eb1b0_1.tar.bz2
https://repo.anaconda.com/pkgs/main/linux-64
https://repo.anaconda.com/pkgs/main/linux-ppc64le
https://repo.anaconda.com/pkgs/main/linux-aarch64/
https://repo.anaconda.com/pkgs/main/linux-s390x/
https://repo.anaconda.com/pkgs/main/osx-64
https://repo.anaconda.com/pkgs/main/osx-arm64/
https://repo.anaconda.com/pkgs/main/win-64

      name version           spec

0  factory_boy   3.2.0  faker >=0.7.0
1  factory_boy   3.1.0  faker >=0.7.0
2  factory_boy   3.0.1  faker >=0.7.0
3  factory_boy  2.12.0  faker >=0.7.0
4  factory_boy  2.11.1  faker >=0.7.0
5  factory_boy  2.10.0  faker >=0.7.0
6  factory_boy   2.9.2  faker >=0.7.0

Package Build Score: 19

Links:

Anaconda Recipes feedstock
Update branch
conda-forge recipe
PyPI
Diff between upstream and feature branch
Diff between origin and feature branch
The last merged PRs

Updating the recipe:
If the recipe needs additional modification the update branch can be modified. Note that the PR diffs are not updated with these changes.
git clone -b 17.6.0 git@github.com:AnacondaRecipes/faker-feedstock.git

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_aa5w5_q8wa/clone/recipe/meta.yaml:14: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_aa5w5_q8wa/clone/recipe/meta.yaml:37: has_imports_and_run_test_py: Imports and python test file cannot coexist.
WARNING: /tmp/abs_aa5w5_q8wa/clone/recipe/meta.yaml:52: missing_description: The recipe is missing a description
Errors were found


Unlock OpenPGP Secret Keys

Using the pass utility in the passwd-cmd settings where the OpenPGP key is password-protected causes himalaya to throw the error
Error: cannot login to IMAP server

Caused by:
    No Response: [UNAVAILABLE] Temporary authentication failure. [2022-09-08 06:10:31]

This error can be mitigated by first running a command such as pass show<EMAIL_ADDRESS>and entering the passphrase in the prompt shown.
┌───────────────────────────────────────────────────────────────┐
│ Please enter the passphrase to unlock the OpenPGP secret key: │
│ "John Doe<EMAIL_ADDRESS>                               │
│ 4096-bit RSA key, ID ################,                        │
│ created 2022-09-07 (main key ID ################).            │
│                                                               │
│                                                               │
│ Passphrase: _________________________________________________ │
│                                                               │
│         <OK>                                   <Cancel>       │
└───────────────────────────────────────────────────────────────┘

After this passphrase has been entered, the gpg utility will not ask again for the passphrase for a brief time. Is there a way to allow himalaya to display this prompt when the user has not yet been challenged?
Note, this behavior also happens in vim, where without first entering the pass show command, himalaya will result in failure.

Let me know if one of those issues helps you:

https://github.com/soywod/himalaya/issues/377
https://github.com/soywod/himalaya/issues/350

Let me know if one of those issues helps you:

Pinentry #377

Yes, this issue helped solve my problem. I skipped past this one because the title seemed irrelevant to the problem I was encountering. Thanks for your help.


Adds new custom dimension to track relevant result shown in finders

The new custom dimension is Relevant result shown (83). This should be set to 'Yes' if a  search in the finder search box results in a 'relevant result'. (The null label is 'No'.)
https://trello.com/c/lwQK2Pi7/336-set-up-a-b-test-for-answer-boxes

This is no longer needed.

Does this file: https://github.com/alphagov/govuk-static-private/blob/1422fb460596d5821dee7963ec227cdad5c033ab/app/views/govuk_component/analytics_meta_tags.raw.html.erb need to be updated as well?
A bit like in this commit: alphagov/govuk-static-private@1422fb4#diff-6d770471136872e42f49ea40fb39d63c ?

Hey @leenagupte - not needed as we want this for only a specific view and not all of them.


Added technical reference to docusaurus based on existing wiki pages

This PR is intended to update the navigation and structure and add the initial content for the technical reference.
The content has been migrated from the existing wiki pages pretty much "as is" and the intent of this PR is not to re-write content (which may need doing in addition) but to get the initial migration in place.
Comments on the structure and how this fits with the user reference manual are very welcome.
Comments on the detail of the content are less useful in relation to this PR as it's intention is to simply migrate content from the wiki into the new documentation site

Seems fine to me.

@ostephens I just realized that this added an image eclipse-debug-config.png at the root of the repository - I think this should be in a subdirectory of docs instead, no?

Looks like I dropped a duplicate file in the wrong place by accident - I'll do a PR to fix. Apologies


Hover Project images for Description

@f-camp @billie-cat
Adding this would allow viewers to read what the project is about before clicking on it.

Center hidden text 9809703dce863c11e2fbcca5a95c8c524b9acef3


1.5.0, custom videos and what's next

So I'll try to sum up what I've been up to here and what's next for Aerial.
My goal is to get 1.5.0 out by the end of next week, before WWDC if possible. Will probably be a busy week then, and for some reason I have a feeling we might get sherlocked 😅
In any case, 1.5.0 will add 2 new large features:

The new spanned mode. This seems to work already correctly for most people. There's a tiny bug in how I calculate margins in case of "grid" screen configurations (say 2x3 screens) but that's about it. This is already in since a few betas, and the preview works in sync with what you'll get:

The second one has often been requested although I was reluctant to get into it : custom videos. The idea is simple, let Aerial play other videos from your computen than just the Aerials. There's now a new option at the bottom of the menu:

Clicking it the first time will open a pretty empty window. You simply click "Add folder" on top and point it to a folder containing videos and let it will fill up. For long time users, a good way to try this is your oldvideos folder in your Aerial cache folder.

This is what you'll see if you click on a folder you've added in the side column. By default it will be named with your folder name, but you can rename it however you like. This will later be used as the "city/country" category in Aerial.
Click a file and you'll get the asset editor:

This should be mostly self explanatory, you can change the name of the video, whether it's day or night (by default everything gets imported as day) and also add/remove/edit points of interests :

As you click through your pois, the preview on the bottom seeks there so you can preview what you do. The video thing is pretty bare and I'll try to add some more controls and info in the next betas but you should get the idea.
When done, just close that window and all that info will be saved in customvideos.json in your Aerial cache folder. The format is the same as the tvOS12 format, roughly and you can also edit it manually if that's your thing.
Now, a few notes about that feature in beta6:

Right now, closing the window correctly saves the json, but the list in Aerial's main panel doesn't get properly refreshed (if you open/close the "Manage Custom Videos" again it will update though, or restart System Preferences).
You can pick a name that already exists in tvOS's Aerials. In my screenshots above I picked the versions of LA Downtown with the better colors, since I named that folder "Los Angeles", it gets merged with other Aerials in the main list :

This will solve the long lasting issue of people preferring an older version of a video, if you used my previous "Move old videos" feature in advanced, you'll still have those videos, just resurrect those you want from there and merge them back !

Video formats/containers : You can add a folder with whatever kind of video you want, as long as they are .mov or .mp4 files. I manually limit to those extensions in beta6, this can change if needed. As to what it can play in terms of codec/containers, in theory anything that QuickTime Player X can play (so no mkv as of Mojave, again this may change as they deprecate QuickTime 7 in 10.15).
If you want to add a new video to a folder on disk, just re add the folder using the button on top of the window, the new videos will get merged with the ones imported previously
Imported videos don't get a 4K badge whether they are 4K or not

So that's about it for this feature, let me know how it goes for you and any bug you find, this is a pretty big amount of code so there are probably a few.
As to what's next, with 1.5.0 I'll try splitting the readme in multiple files as it's really way too long, and we need a better way to preserve the information for new users.
After 1.5.0, my next goal will be to probably clean up the UI a bit, and make the UI translatable. This should be easy enough but a bit of cleanup to simplify it would probably make it easier on everyone 😄

Just dropped beta7 which fixes pretty much everything mentioned above and more:

Videos will now play muted (!)
Video manager now shows informations about resolution and duration of a video
Fix stepper not working when adding a poi, fixed seeking when adding a poi, and disallow times above duration
4K custom videos now have the correct 4K badge in main UI
customvideos.json is now pretty printed for easier manual editing
Closing the custom video manager now properly reloads the video list in main UI

Barring any bad bug, I will release 1.5.0 by the end of the week!

Closed as implemented with the release of 1.5.0


Add syntax to allow arbitarary operators to be applied infix

Haskell provides a method of applying prefix functions as infix. Given a function f : a -> b -> c you can apply as infix by enclosing it in backticks, like
x `f` y

Providing some sugar like this would allow us the benefits of flexible infix operator application without the ambiguity resulting from the pervasive infix operator application removed in #122

I think we have decided not to go this way some time ago, x.f(y) is a good enough substitution for infix operators. Closing this issue.


Standardize store.stream() to emit only new items

This PR proposes migrating the subject within RealInternalStore which acts as a bridge for subscribers to store.stream() from a BehaviorSubject to a PublishSubject.
This is a go at standardizing the behavior of store.stream() so that subscribers will passively stream only new items -- that is, items that are fetched after they subscribe.
If I'm understanding right, in the current implementation, subscribers to store.stream() on a new RealStore instance will passively stream new items. However, subscribers to an existing store instance where the fetcher has already returned at least one item, in addition to passively streaming new items, will also receive the last fetched item as cached by the BehaviorSubject. As of now, this cached item also persists through a clear() event.

Thanks for the fix, good work! :D


Fix Action Response Serialization

Currently, all action responses are being generated as 204. However, per the OASIS Mapping documentation 4.5.3 :
HTTP response code [of an action should be ] 204 if the response has no body
...200 for other success codes...
For a specific example, the following xml:

Should generate a 200 response.
Modified UnitTest to pass expected responseCode as InlineData

Merged. Thanks.


[docs] fix a term 模板

What type of PR is this?
/kind cleanup
/kind documentation
What this PR does / why we need it:
Replace a term from 模版 with 模板 globally. See how ChatGPT responds to this term:

/lgtm


Add DesignateSpecCore struct

This version of the struct (called "core") is meant to be used via the OpenStackControlplane. It is the same as DesignateSpec only it is missing the containerImages.
The Default() function for webhooks has been split accordingly.
Jira: OSPRH-4835

/test designate-operator-build-deploy-kuttl

/lgtm


chore(refactor): refactor Wasm engine and Sat construction

This PR introduces the engine2 package, which is a significant simplification of the previous engine package. A future PR will delete the engine package, and it was not deleted here for diff simplicity.
The construction of a Sat instance was also simplified.

(Not that you added it, but no sense in bringing it over in the refactor.)


manifest feature doesn't support "supports" field

Describe the bug
In https://github.com/microsoft/vcpkg/blob/master/docs/users/manifests.md#features-and-default-features it is stated, that the feature field have a supports field. However if adding this field, vcpkg x-add-version <port> and vcpkg format-manifest <port> will fail.
Example with the port comms:
vcpkg.json:
{
  "name": "comms",
  "version-semver": "3.4.0",
  "features": {
    "tools": {
      "description": "Builds CommsChampion tools",
      "supports": "!static",
      "dependencies": [
        "qt5-base"
      ]
    }
  }
}

Error message from format-manifest
.\vcpkg.exe format-manifest .\ports\comms\vcpkg.json
Failed to parse manifest file: D:\dev\vcpkg_mapnik\.\ports\comms\vcpkg.json
Errors occurred while parsing D:\dev\vcpkg_mapnik\.\ports\comms\vcpkg.json
    $.features.tools (a feature): unexpected field 'supports', did you mean 'description'?

Error message from x-add-version
 .\vcpkg.exe x-add-version comms --overwrite-version
Error: Couldn't load port `comms`.

Environment

OS: Windows
.\vcpkg.exe --version
Vcpkg package management program version 2021-08-12-85ab112d5ee102bc6eac8cdbbfdd173a71374e04

Expected behavior
I would expect to support the supports field.
Related PR https://github.com/microsoft/vcpkg/pull/19581

Basically a duplicate of #17651.
Note that supports has only limited practical effects IIRC:

vcpkg.io website
CI testing

In one case, I added a $supports field instead IIRC.

wouldn't (e.g. taken above example) vcpkg install comms[tools]:x64-windows-static fail if someone wants to install the port?

will close this in favor of #17651

wouldn't (e.g. taken above example) vcpkg install comms[tools]:x64-windows-static fail if someone wants to install the port?

If it is implemented it should then fail, yes

wouldn't (e.g. taken above example) vcpkg install comms[tools]:x64-windows-static fail if someone wants to install the port?

I don't see such behaviour. If you want a reliable error message, it has to be added to the portfile (vcpkg_fail_port_install).
But please verify yourself.

wouldn't (e.g. taken above example) vcpkg install comms[tools]:x64-windows-static fail if someone wants to install the port?

I don't see such behaviour. If you want a reliable error message, it has to be added to the portfile (vcpkg_fail_port_install).
But please verify yourself.

Currently it wouldn't fail (root manifest supports). But from a user perspective this would be desirable. At least a warning should be printed when trying to install (classic or manifest mode) a port which is not supported.

Maybe I have time to implement that next week, but the install code is currently 2500 lines long with literally no comment. But imho it should be an error. Then vcpkg_fail_port_install is also not necessary anymore.


AddScreen/ScreenInit failed for driver 1

(xenial)kamnida@localhost:~$ sudo startxfce4
[sudo] password for kamnida:
Do not launch startxfce4 as root inside the chroot.
(xenial)kamnida@localhost:~$ sudo startx
X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-59-generic armv7l Ubuntu
Current Operating System: Linux localhost 3.8.11 #1 SMP Tue Jun 20 22:56:11 PDT 2017 armv7l
Kernel command line: cros_secure console= console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=PARTUUID=70decbf0-1469-4f4f-9dd8-534a720e41ed/PARTNROFF=1 rootwait rw dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=0 dm="1 vroot none ro 1,0 2539520 verity payload=ROOT_DEV hashtree=HASH_DEV hashstart=2539520 alg=sha1 root_hexdigest=fa73b006d69c3bc52ce0d0e87660fae3d933bcc6 salt=3a0f75bb764b091fcd4f01017f9dca289e8c603d31a937cea31c15925a38145a" noinitrd vt.global_cursor_default=0 kern_guid=70decbf0-1469-4f4f-9dd8-534a720e41ed
Build Date: 26 January 2017  12:27:19AM
xorg-server 2:1.18.4-1ubuntu6.1~16.04.1 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Wed Jun 28 01:22:25 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
gbm: failed to open any driver (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
gbm: Last dlopen error: /usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory
failed to load driver: exynos
EGL_MESA_drm_image required.
(EE)
Fatal server error:
(EE) AddScreen/ScreenInit failed for driver 1
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
My Chromebook is SAMSUNG Xe303c12 Chromebook..
name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
crouton: version 1-20170619181610~master:980f090f
release: xenial
architecture: armhf
xmethod: xorg
targets: xfce
host: version 9592.29.0 (Official Build) beta-channel daisy
kernel: Linux localhost 3.8.11 #1 SMP Tue Jun 20 22:56:11 PDT 2017 armv7l armv7l armv7l GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
chronos@localhost / $
What i gonna do ?

Here you go #3291
Second Post


cycle # instead of date in output filename + make conversation subfolder with population name

cycle # instead of date in output filename + make conversation subfolder in outputs with population name


Using Hextra on GitHub Page never works

Hi there,
Thank you for sharing such as nice theme.
However, I have been trying to build and deploy Hextra to a GitHub page all night, but I haven't been able to make it work
I've tried using the Hextra template and also tried building from scratch based on Hextra's instruction, but neither approach worked.
On the local server (http://localhost:1313/) I can view the new site using hugo server --buildDrafts --disableFastRender. I can also successfully use GitHub Actions to build and deploy it. However, every time I click on the site's link, it only displays the repository's name and the contents of the README.md, not the content the site should have.
I'm not sure if I need to convert the site to static with Hugo. But after trying hugo or hugo -D in the terminal and then uploading the files onto the GitHub repo, it still just displays the repository's name and the README.md content after clicking the link of the site.
I'm also not sure if the failure is because Hextra requires special flags like --buildDrafts and --disableFastRender when running hugo server  since other themes don't need these flags.
Could you please help me solve this? Or provide guidance on how to correctly deploy a blog with the Hextra theme on GitHub pages? I've been able to deploy other themes based on Hugo to GitHub pages successfully.

@wlin16 please start with the hextra-starter-template repo. In the README, there's a Deployment section that tells you how to deploy to GitHub Pages:

A GitHub Actions workflow is provided in .github/workflows/pages.yaml to publish to GitHub Pages for free.
We need to run the workflow manually.

To clarify:

I'm not sure if I need to convert the site to static with Hugo. But after trying hugo or hugo -D in the terminal and then uploading the files onto the GitHub repo, it still just displays the repository's name and the README.md content after clicking the link of the site.

I recommend using the GitHub action I provided in the template repo. You don't need to convert the site to static locally using Hugo.

I'm also not sure if the failure is because Hextra requires special flags like --buildDrafts and --disableFastRender when running hugo server  since other themes don't need these flags.

No, these flags are not required to build the site.

Could you please help me solve this? Or provide guidance on how to correctly deploy a blog with the Hextra theme on GitHub pages? I've been able to deploy other themes based on Hugo to GitHub pages successfully.

Use the hextra-starter-template to create your own repo by clicking the "Use this template"
Run the GitHub action on your created repo if it's not triggered automatically

After that, you should at least see a site that looks exactly like the template site. And you can start modifying files from there.


chore: release 2.0.0

:robot: I have created a release *beep* *boop*
2.0.0 (2019-05-14)
Bug Fixes

run the generator (#616) (92b0add)
deps: update dependency google-gax to v1 (#615) (687a353)
Fix client pooling for long-lived listens (#614) (479bc9c), closes firebase/firebase-admin-node#499 #256
deps: update dependency google-gax to ^0.26.0 (#606) (a637a68)

Build System

upgrade engines field to >=8.10.0 (#608) (32485f4)

BREAKING CHANGES

upgrade engines field to >=8.10.0 (#608)

we will regenerate this once @schmidt-sebastian has landed a couple other breaking changes we'd like to get into 2.x.


Python3-compatible version

Let's see what Travis says. Tests pass with Python3 and Python2 in my environment.
Anyway it can certainly still be improved. I see at least:

With Python2 there are warnings that I don't know how to handle from sqlalchemy: .../python2.7/site-packages/sqlalchemy/sql/sqltypes.py:185: SAWarning: Unicode type received non-unicode bind param value 'fff'. (this warning may be suppressed after 10 occurrences) (util.ellipses_string(value),))
Instead of an if in from_bytes(), use the same kind of function redefinition as in b().
Change more things in cyvcf2's output to type string instead of bytes (e.g. impact headers['CSQ'/'EFF'/'ANN']) for more consistency (keys are now strings) and to avoid some conversions.
There may be some unnecessary conversions (in particular, I don't understand everything with the "escape_unicode" things).

awesome! can you test against the newest commit in cyvcf2 where I return string from INFO rather than bytes (this was done recently -- 7/17 morning).

I did already, it is fine. Only some values are still bytes (e.g. impact headers), but no more key.


ssh login issues

The first (perhaps couple) times I tried ssh git.charm.sh, it worked fine.

Then I started getting this:

$ ssh git.charm.sh
Permission denied (publickey,keyboard-interactive)

Followed by:

$ ssh git.charm.sh
ssh: Could not resolve hostname git.charm.ssh: nodename nor servname provided, or not known

Is 1. because of rate limiting, what is 2. about? Thanks!

I'm actully getting this too...
$ ssh git.charm.sh
<EMAIL_ADDRESS>Permission denied (publickey,keyboard-interactive).

+1

Just tried to ssh git.charm.sh and it worked perfectly. Don't know what exactly the issue was or what fixed it.


When the browser window is resized the height of the graph is reduced.

Hi there,
Thanks for your work on this awesome library.
I've been having this issue lately where when my browser window is very wide, the graph doesnt seem to respect the height of its parent, the height set in HTML(inline CSS) or the size parameter set in javascript by the size:{height:400}.
The effect is shown below.

Displays properly here at a width of 1300px

Above, the width is around 1920px and the graph's height is reduced
Any ideas? Thanks. (tried on 0.4.8 & 0.4.4)

I had the same issue. I fixed it by adding a min-height style to the div element. For example,
Before:
After:

I had the same issue. I fixed it by adding a min-height style to the div element. For example,
Before:

After:

Hi there,
I tried that but the graph still doesn't seem to get the full height.
JS Fiddle showing the issue
http://jsfiddle.net/dazhbog/1rb8qexp/

Hi, sorry I can't see this issue. It's still happening in the fiddle?

This is very interesting. I just went to the fiddle and it seems that its working now without any change. I then went to my local environment and I could still see the problem, I just made sure I re-update the library to the same version as the masayuki0812/c3/master/c3.js (latest at the moment 4.8) and it seems to be fine now.
I shall close it for now then, thanks for your time! :+1:

Ok this is weird, Is there a difference between this file here https://rawgit.com/masayuki0812/c3/master/c3.js
and the file in the .js file in the zip file here?
https://github.com/masayuki0812/c3/archive/0.4.8.zip
Both have this line     var c3 = { version: "0.4.8" };
I had the one from the zip file, where the bug is present but when I use the one from this link https://rawgit.com/masayuki0812/c3/master/c3.js everything works.
I think some new changes made the fiddle to start working after it was created.

Yes, there is. https://rawgit.com/masayuki0812/c3/master/c3.js is different from the latest release (v0.4.8 in this case) and includes the fixes that are not released yet. It might be better to create develop branch for the next version and work on it.. Anyway, sorry for the confusion.

Ok I have updated the fiddle to use the 0.4.8 release so that you can quickly check the issue out.
same link: http://jsfiddle.net/dazhbog/1rb8qexp/
I will go ahead and open the issue again, If you think its fixed in the 0.4.9 release the you can go ahead and close it again.
I also tried the 0.4.9, that seems to fix the issue, but had another issue that the graphs wouldnt appear until I resized the window. But i guess I have to wait until it is a proper release to test it.
Thanks.

Please let me close this issue. For another issue you found, can you open a new issue? Thanks.


CFN errors ocasionally

Seems like we might need to implement implicit success report, using cfn-signal.

xref https://github.com/microservices-demo/microservices-demo/issues/413#issuecomment-260921298

For me it's systematic unless I use large instances (m4.xlarge)
On Nov 21, 2016 11:24 AM, "Ilya Dmitrichenko"<EMAIL_ADDRESS>wrote:

xref microservices-demo/microservices-demo#413 (comment)
https://github.com/microservices-demo/microservices-demo/issues/413#issuecomment-260921298
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/integrations/issues/87#issuecomment-261899121,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQOJME_F-4-C8PTRCzSl1p7fnv8t73Sks5rAXFcgaJpZM4IHRbK
.

xref https://github.com/weaveworks/integrations/issues/116


About the input sequence and PID controller

Hi @ap229997 , I really like your amazing works. It inspires me a lot. However, there are 2 things that I want to know.

In your paper, it is said that the transfuser takes a sequence of inputs. However, it is not described exactly how many inputs the model takes (neither in the supplementary file). In the config.py on each model, I see that you set the parameter
seq_len = 1 # input timesteps
Does it mean that each model just takes 1 input and not a sequence of inputs (that contains several inputs)? Could you please explain to me how you feed the inputs to your model?

In your paper, it is said that each model (except CILRS) is predicting 4 waypoints (in BEV x,y coordinate). Then, I check the PID controller on the supplementary file and the codes (model.py, https://github.com/autonomousvision/transfuser/blob/164e01993dc1c67b81ec2680c49c73c2cbba153c/transfuser/model.py#L470), it seems that only 2 waypoints (the first and second one) are considered to control the steer and throttle. So, what is the purpose of predicting 2 extra waypoints? Is it used to give the GRU more learning experience during the training process?

Thanks in advance.

seq_len = 1 means we only consider input from a single timestep. Since the transformer takes a sequence of tokens as input, we convert the feature map that we get from the convolutional encoder into a 1D sequence of tokens. For example, 8x8 feature map is converted into 64 tokens, so these 64 tokens form a sequence.
Predicting future entities, in general, helps the model to implicitly learn anticipation/forecasting capabilities which is desirable. We experimented with predicting multiple timesteps into the future and 4 timesteps worked the best. Another use of the 4 waypoints could be to design a better controller, e.g. fitting a curve over the 4 waypoints rather than using just a few waypoints.

Ok, got it. Thanks!


Changeable lore

I'd like to be able to change this

Into something like this

Without breaking the wand / plugin

Not currently possible, I’ll leave this open until custom lore support is implemented.

Custom lore support is implemented, though you can't have it auto-generate a list of spells like that. You'd have to put the spells in lore yourself.
I just noticed you'd also like the spell to not show up in the item name - it actually should not if there is only one spell on the wand.
Now you mention it though, it would be nice to have the option of not having the spell on the wand name, I can probably just use the action bar to show spell cycling.

Oops, I forgot that the spell name is in the wand name because otherwise the hotbar mechanism doesn't work well, it'd flash spell names as you switch in a very ugly way.
So probably what's there now in terms of custom lore is as good as it's going to get, if you make a wand with a single spell the spell doesn't show up in the name and that's probably the best I can do.


Change output type of Adapter.adapt()

Adapter.adapt() should return only a List[RequestState] rather than a ScenarioState.

The most pertinent reasons are to make progress towards:

A Python notebook API that allows researchers to prototype new scenarios and models in Python notebook.
Cleaner separation between the test and SUT.
More explicit typing (i.e. using different types for before and after running the model - before this PR, both types were ScenarioState)


Feature Request: Who is on-call card for component page

It would be nice to show who is on-call on the component page. There should be a annotation for team name and based on team name it should show all on-calls for all schedules

This would be wonderful for us. We aren't using the Opsgenie Page for some reasons, but would really find who-is-on-call for the component page super helpful.


No module named 'dask.distributed'; 'dask' is not a package

Hi,
I'm new to Dask but when I tried to import dask.distributed it said :
No module named 'dask.distributed'; 'dask' is not a package

Knowing that I'm running conda venv where I can see that dask is installed :

Can someone help to undersatnd what going wrong ?
thanks

Thanks for raising an issue @arcontechnologies. It looks like your local dask.py file is interfering with importing from dask (the package). One fix would be to change the dask.py file to have another name

Oh my mistake ! I renamed it and it's working
thanks


Yarn version misaligned with NPM

Hey there!
Yarn still is in 0.0.7
https://yarnpkg.com/package/@vectopus/atlas-icons-react

Hi @mosamy19 could I get your eyes on this? not sure why Yarn is not automatically upgrading to 0.0.10 should be a short fix?

workaround is to remove the package and install it again, as there is no older versioning it is fetched as 0.0.10 from NPM


chore(deps): update commitlint monorepo to v9.1.2

This PR contains the following updates:

Package
Type
Update
Change

@commitlint/cli
devDependencies
patch
9.1.1 -> 9.1.2

@commitlint/config-conventional
devDependencies
patch
9.1.1 -> 9.1.2

Release Notes

conventional-changelog/commitlint
v9.1.2
Compare Source
Bug Fixes

update dependency (#1993) (32667e8)

update dependency cosmiconfig to v7 (#2044) (f4db933)

update dependency execa to v4 (#1936) (8efb441)

update dependency find-up to v5 (#2060) (25d42f4)

update dependency fs-extra to v9 (#1018) (2df49fa)

update dependency get-stdin to v8 (#1938) (f94a5c8)

refactor!: drop support for node 8 (#1999) (751f39f), closes #1999

BREAKING CHANGES

remove node 8 from circle-ci checks

also remove node 13 because we do not support experimental versions

docs: update node v10 to latest LTS 10 version

Co-authored-by: Cedric van Putten<EMAIL_ADDRESS>Co-authored-by: Cedric van Putten<EMAIL_ADDRESS>9.1.2 (2020-07-13)
Note: Version bump only for package @commitlint/root
9.1.1 (2020-06-30)
Bug Fixes

load: resolve plugins from extended configs (#1976) (d0f0eb9)
mark internal packages as private #972 (#1970) (2351124)

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

:tada: This PR is included in version 5.1.15 :tada:
The release is available on:

v5.1.15
GitHub release

Your semantic-release bot :package::rocket:


Started shell refactoring.

Issue: #147

The idea of these changes is to adapt the shell so it can be used both locally and on SageMaker.
Example usage:
python -m gluonts.shell train R --data-path ~/tmp/exp/optml

Job PR-156/13 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-156/13/index.html

Codecov Report

Merging #156 into master will increase coverage by 0.42%.
The diff coverage is 47.72%.

@@            Coverage Diff             @@
##           master     #156      +/-   ##
==========================================
+ Coverage   78.13%   78.55%   +0.42%
==========================================
  Files         120      124       +4
  Lines        6778     6781       +3
==========================================
+ Hits         5296     5327      +31
+ Misses       1482     1454      -28

Impacted Files
Coverage Δ

src/gluonts/model/forecast.py
67.91% <100%> (+0.34%)
:arrow_up:

src/gluonts/shell/train.py
31.37% <25%> (+1.54%)
:arrow_up:

src/gluonts/shell/serve/app.py
39.13% <39.13%> (ø)

src/gluonts/shell/env/path.py
40% <40%> (ø)

src/gluonts/shell/env/__init__.py
40.9% <40.9%> (ø)

src/gluonts/shell/__main__.py
41.66% <41.66%> (ø)

src/gluonts/shell/serve/__init__.py
63.63% <63.63%> (ø)

src/gluonts/shell/serve/util.py
66.66% <66.66%> (ø)

src/gluonts/shell/env/params.py
83.33% <83.33%> (ø)

... and 6 more


Use kleidukos/get-tested and include GHC supported versions in cabal file

Let's follow the same approach that Rollbar Haskell is doing: https://github.com/stackbuilders/rollbar-haskell/pull/64

We're using Nix in our CI settings and it seems get-tested is not generating a Matrix valid for Nix yet: https://github.com/Kleidukos/get-tested/issues/14

I'm closing this since we're using only version of Nix for this. No need to use this GitHub action or do something in Nix for it.


Adds Easier Shader Debug

The usueal pink shader is still activated, but real but failed shader is
inside a  _DEBUG so that you can debug it in  "shader editor"

I dont understand how it could work well.
If your _DEBUG program declare some uniforms, let's say materialDiffuse. At compile time because the _DEBUG will not use those uniforms, the function cacheUniformList will not list them. So when you enable the _DEBUG, materialDiffuse will not apply because not listed in the program to apply.
It's the same thing with cacheAttributeList.
It's possible it could work, but I prefer we improve first the way we report shader error

pr title not clear sorry:
shader debug => shader syntax error debug.
When a shader compilation fails, it's always syntax problem, not a render problem.
Here, the goal is not to debug visually the render, so no interest at all in attributes and uniform.
The goal here with this minimal change is to get the shader in shader editor chrome extension so we can fix syntax errors fast and easy on the spot
you can spot and fix  the syntax painlessly.
(shader editor does compile shader just for syntax check and points errors with colors in its own context...)

In this case why not just fixing that in the report log of the shader, there is some code to handle this

much much easier in shader editor:

you have the whole shader
shader syntax code coloring
you can fix edit directly on the whole shader
much mire readable
no need to tweak log level.
etc

adding the same level of feature means code bloat in shader.js code
On Sun, Feb 26, 2017, 09:46 Cedric Pinson<EMAIL_ADDRESS>wrote:

In this case why not just fixing that in the report log of the shader,
there is some code to handle this
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cedricpinson/osgjs/pull/732#issuecomment-282541874,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH2O_ssJ3fMDHlhaLSIanqSSOTAVR9Dks5rgTwCgaJpZM4MJjWe
.

I dont feel that it's the general use case, Why not instead disabling failsafe instead, would that be simpler and do the same thing ?

When shader compilation fails, the program is not linked and thus not
showing in the shader editor.
imho the change is really very benign here, hard to do a simpler change, no
side effect, so the cost/benefits, even if considereing "it's not the
general case" is quite positive.
( Myself I would even remove all the shader error logging code in favor of
that, as I won't ever use it again if this PR is merged.)
On Sun, Feb 26, 2017 at 10:18 AM Cedric Pinson<EMAIL_ADDRESS>wrote:

I dont feel that it's the general use case, Why not instead disabling
failsafe instead, would that be simpler and do the same thing ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cedricpinson/osgjs/pull/732#issuecomment-282543271,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH2O8FwMgIqznCz0U1eOZcTse1Ht9HYks5rgUNKgaJpZM4MJjWe
.

shader editor does not work on all platform, the log must stay and be improved. The point I dont like is that there are more effort to hack on top of thing, instead of just improving what needs to be improved. It's probably as easy to copy/paste the shader from the log into shader editor. Not need to create multiple failsafe shader with original shader inside.

Ok, currently we don't log no more the whole shader when it fails.
( shader error log is messy since changes in logs level and fold )
OT:  I would recommand using that shader editor I do use
https://github.com/Kuranes/ShaderEditorExtension/tree/feature/upgrade that
works even on mobile, including ios ( using vorlonjs.)( Still some case
where attributes/uniform not properly rebinded on edit, but shader editor
syntax debug always works for me.
On Sun, Feb 26, 2017 at 10:46 AM Cedric Pinson<EMAIL_ADDRESS>wrote:

shader editor does not work on all platform, the log must stay and be
improved. The point I dont like is that there are more effort to hack on
top of thing, instead of just improving what needs to be improved. It's
probably as easy to copy/paste the shader from the log into shader editor.
Not need to create multiple failsafe shader with original shader inside.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cedricpinson/osgjs/pull/732#issuecomment-282544572,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH2O45kEFzazcvt10XuijOXJW6Lyl0oks5rgUnhgaJpZM4MJjWe
.

It does not work here, I click on one program everything disappear

yes, quite possible shader render debugging may not work on your os but
shader syntax error debugging  works :)
On Sun, Feb 26, 2017, 13:54 Cedric Pinson<EMAIL_ADDRESS>wrote:

It does not work here, I click on one program everything disappear
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cedricpinson/osgjs/pull/732#issuecomment-282553852,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH2OwCh6w0fXWpU_dNls1LR0lZ0L7kWks5rgXXrgaJpZM4MJjWe
.

Ho yes I am sure it helps for that, my point is that log must be clean and fixed, you will probably able to copy/paste a shader from the log.
I will be open to add extra code to improve that. We should also talk with other devs to know their workflow and what's their pain.

I agree with @Kuranes on this point.
When writting shader the log system in console log is a pain.
Copy-paste the error in a glsl linter (http://shdr.bkcore.com/, chrome shader extension)  works but it's always a pain to copy long string from the chrome console output.
For me, the worst case is when I don't know which shader failed, when you have easily 10-20 shaders it's not funny (I usually check the shader_name define or the code itself).
Ideally I'd like to have the failed shader in the shader editor extension (with its original name, and ideally append with "Failed" or something like that).

ok then if you have both the same issue, @Kuranes use @stephomi inputs to update your PR

Just to add my 2 cents
ShaderEditor is not working for me from long time ago, so I didn't rely in it at all. I have had hard times to get shaders form the chrome debug tools, as with long text strings it's pretty awful as @stephomi said.
It keeps creating shaders objects, attached a screenshot.

I ended up using webGL Insight chrome extension to copy paste shaders.
I get the point of @cedricpinson and also I think it would be nice to have something in case you are not using chrome and chrome extensions. Said that I think adding this PR won't hurt, and sure it will help to improve the workflow for people using these extensions.
I didn't test the @Kuranes mod of shaderEditor, but I will.


Powerline Frequency cannot be left blank

If the Powerline Frequency is left to the default value of 'n/a', a TypeError is raised and not handled. I think instead of handling this error at runtime, it should be a requirement before allowing conversion.

n/a is a valid value:

Fixed.