Able to remove the default bridge network; also inconsistent error messages

I was able to remove the default bridge network, now i can't run continers
Trying to remove null says it can't be found but it clearly is found by docker network ls

buntu@ip-172-31-36-118:~$ docker network ls
NETWORK ID          NAME                DRIVER
a792d9893ebd        none                null
37c1b62f7b40        host                host
97ee5a4064f7        bridge              bridge
ubuntu@ip-172-31-36-118:~$ docker network rm bridge
ubuntu@ip-172-31-36-118:~$ docker network ls
NETWORK ID          NAME                DRIVER
a792d9893ebd        none                null
37c1b62f7b40        host                host
ubuntu@ip-172-31-36-118:~$ docker network rm host
Error response from daemon: network of type "host" cannot be deleted
ubuntu@ip-172-31-36-118:~$ docker network rm null
Error response from daemon: network null not found
ubuntu@ip-172-31-36-118:~$ docker network ls
NETWORK ID          NAME                DRIVER
a792d9893ebd        none                null
37c1b62f7b40        host                host
ubuntu@ip-172-31-36-118:~$ docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
b901d36b6f2f: Pull complete
0a6ba66e537a: Pull complete
Digest: sha256:517f03be3f8169d84711c9ffb2b3235a4d27c1eb4ad147f6248c8040adb93113
Status: Downloaded newer image for hello-world:latest
Error response from daemon: Cannot start container da483ad019745e76834d1b2bd4be6b742367b5b53d985f306d5c596fa08a180b: network bridge not found
ubuntu@ip-172-31-36-118:~$

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

@moxiegirl we shouldnt allow the user to remove the default bridge network. will fix it.
regarding the other issue, you are trying to remove the driver null. the network name is none.
can you try that ?

@mavenugo Yep, that time I got the right error.  Got a question how come the default bridge network is not name bridge0 ?  I was expecting to see that. It would fit with your explanation to me and maybe provide a hint to users coming from the old 1.8 world

@moxiegirl thats because docker0 is a bridge name and is an implementation detail. folks are familiar with --net=bridge, which is the network that people are used to.

@mavenugo your implementation detail is surfaced through ifconfig which shows docker0  on the host. Your dismissal doesn't jive with how you explained networks to me. There, you started by talking about the old docker0 bridge as a means of conveying knowledge. By not using docker0 as this default network name, you are denying existing customers the same clarity you delivered in your verbal explanation to me.

@moxiegirl i see your point. but, that is a documentation thing to communicate to the user. as you know, the --net has been enhanced to support user-defined networks. If you look at the current --net option you can see they are bridge, host, none. They are mapped directly to the network names. docker0 is something that the user never configures or sees in this context. ifconfig is the implementation detail I was refering to. So, IMO, I think in order to provide proper compatibility with the existing UX and extending for the 1.9 features, the --net should be the reference point and not the bridge name that is created by the driver.
But I do agree that it was easy to explain on the whiteboard with docker0 because bridge is such a common word. Lets make sure we communicate the same in documentation.

@mavenugo It is a grave mistake to rely on documentation to convey what a UX can do more easily.  You yourself don't rely on documentation as you told me.  Rare is the person that reads something once and recalls it perfectly forever -- yet our implementation can do this forever by being consistent and thought in choosing things even as simple as the name of a single element.
Considering we are at RC1 and there is time, unless this is a major break or a major piece of work (over an hour), we should do it.

@moxiegirl how about my explanation above ?
as you know, the --net has been enhanced to support user-defined networks. If you look at the current --net option you can see they are bridge, host, none. They are mapped directly to the network names. docker0 is something that the user never configures or sees in this context. ifconfig is the implementation detail I was refering to. So, IMO, I think in order to provide proper compatibility with the existing UX and extending for the 1.9 features, the --net should be the reference point and not the bridge name that is created by the driver.

@moxiegirl and how about users who are used to --net=bridge , do you want to change that to --net=docker0 ?

You don't give the default null network a name of null you call it none.  I'm just asking you to call the default bridge network docker0 so that it matches what it was known as in the past.
NETWORK ID          NAME                DRIVER
0bad5fe884f2        none                null
b06fb2876a91        host                host
275ceccf4a8b        docker0              bridge

The network driver name should remain bridge of course.

@moxiegirl the network name is none as in --net=none. same as --net=bridge.
the driver names are entirely different from network names.

Bridge is the right name, especially as you can replace the actual bridge interface by something else and it's still --net=bridge.

@icecrime good point. today the bridge network does take other bridges that are not docker0 using the -b option.

@mavenugo @icecrime Madhu sorted me in a convo yesterday.  I think I'm down to the original purpose of this issue, I was able to remove the default bridge. --- is that still valid?

Thanks @moxiegirl. Yes the default bridge deletion will be addressed.

I have the same issue with docker-1.9.0rc3:
$ docker version
Client:
 Version:      1.9.0-rc3
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   2100b94
 Built:        Wed Oct 28 01:29:10 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.0-rc3
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   2100b94
 Built:        Wed Oct 28 01:29:10 UTC 2015
 OS/Arch:      linux/amd64

ubuntu@node-2:~$ docker network ls
NETWORK ID          NAME                DRIVER
fbe71653f1cc        swarm               overlay
5af18d78297b        host                host
c5e0bc826099        bridge              bridge
1991225575e0        none                null

# rm via ID
ubuntu@node-2:~$ docker network rm c5e0bc826099
ubuntu@node-2:~$ docker network ls
NETWORK ID          NAME                DRIVER
fbe71653f1cc        swarm               overlay
5af18d78297b        host                host
1991225575e0        none                null

ubuntu@node-2:~$ docker network create bridge
880c67cc889570fc39156eecdefee00a47877506f7e36ebb3b2a9be8e1839dc1
ubuntu@node-2:~$ docker network ls
NETWORK ID          NAME                DRIVER
fbe71653f1cc        swarm               overlay
880c67cc8895        bridge              bridge
1991225575e0        none                null
5af18d78297b        host                host

#rm via name
ubuntu@node-2:~$ docker network rm bridge
ubuntu@node-2:~$ docker network ls
NETWORK ID          NAME                DRIVER
fbe71653f1cc        swarm               overlay
5af18d78297b        host                host
1991225575e0        none                null

@vieux can you pls confirm if you see this in master ?
@tiborvass i couldnt find https://github.com/docker/docker/issues/17351 as 1 of the patches in https://github.com/docker/docker/issues/17000
Can you pls confirm ?

I confirm, I cannot reproduce on master

thanks @vieux at this point, we have to make sure #17351 is pulled in for the release.We can keep this issue open just to make sure

Now that #17351 is pulled in for RC4, we can close this.


Run-AlPipeline in new avalaibles countries where Cronus is not available

Describe the issue
Context: International app for AppSource. (for all countries available for BC)
In that context, MS ask to test the app in all localizations against the Cronus evaluation company.
In some contries (EE, HK, JP, KR, PL...) the Cronus company do not exist directly in the sandbox, and the existing company is empty. We can create the company with the new company function in sandbox. May be using the New-CompanyInBcContainer function. But how to make a condition by container ?
Do you have any idea to face this issue? Today I use the Run-AlPipeline with succes except on those countries.

In Next version of Run-AlPipeline, you can specify a function to load test data in a parameter called:
  -ImportTestDataInBcContainer

The value of this is a scriptblock.
In the next preview, there will also be a new function called: UploadImportAndApply-ConfigPackageInBcContainer
You can kind of guess what it does:-)
This can be used with the new parameter override in Run-AlPipeline:
Run-AlPipeline `
    -parameter `
    -parameter `
    -ImportTestDataInBcContainer { Param([Hashtable]$parameters)
        $country = Get-BcContainerCountry $parameters.containerName
        if ($country -eq "hk") {
            UploadImportAndApply-ConfigPackageInBcContainer @parameters -configPackage 'W1.ENU.STANDARD'
            UploadImportAndApply-ConfigPackageInBcContainer @parameters -configPackage 'W1.ENU.EVALUATION'
        }
    }

Shipped in 1.0.15-preview269

Perfect !
As we prepare containers images before the CI/CD. Can we imagine to get that option also in New-bcImage ?

I am planning to add a -bakfile parameter to new-bcimage - to use a bakfile.
Then you would have to prepare your database in a container and use that for the container.
The more specific you make the images, the less useful they are.


write_page() throws an Encoding::CompatibilityError for chinese characters

Hey,
I am trying to fix an issue, where the page name is something chinese: 你是我的中关星. Saving the page via:

class B

  def self.test(wiki, name)

    canonicalized_filename = Gollum::Page.canonicalize_filename(name)
    format = :markdown
    content = "abc"
    commit = {
      name: "nirnanaaa",
      email<EMAIL_ADDRESS>      message: "created abc"
    }
    path_name = "/"

    wiki.write_page(canonicalized_filename, format, content, commit, path_name)
  end
end

wiki = User.wiki
 => #<Gollum::Wiki:70304539248780 /Volumes/Documents/GollumRails4Test/demoapp.git>

2.1.2 :003 > name = "你是我的中关星"

2.1.2 :003 > B.test(wiki)
Encoding::CompatibilityError: incompatible character encodings: UTF-8 and ASCII-8BIT

	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gitlab-grit-2.6.12/lib/grit/index.rb:176:in `%'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gitlab-grit-2.6.12/lib/grit/index.rb:176:in `block in write_tree'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gitlab-grit-2.6.12/lib/grit/index.rb:171:in `each'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gitlab-grit-2.6.12/lib/grit/index.rb:171:in `write_tree'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gitlab-grit-2.6.12/lib/grit/index.rb:123:in `commit'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gollum-lib-3.0.0/lib/gollum-lib/committer.rb:170:in `commit'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gollum-lib-3.0.0/lib/gollum-lib/wiki.rb:340:in `write_page'
	from /Volumes/Documents/chin.rb:24:in `test'
	from (irb):3
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/railties-4.1.4/lib/rails/commands/console.rb:90:in `start'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/railties-4.1.4/lib/rails/commands/console.rb:9:in `start'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/railties-4.1.4/lib/rails/commands/commands_tasks.rb:69:in `console'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/railties-4.1.4/lib/rails/commands/commands_tasks.rb:40:in `run_command!'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/railties-4.1.4/lib/rails/commands.rb:17:in `<top (required)>'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:247:in `require'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:247:in `block in require'
... 3 levels...
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:241:in `load'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:241:in `block in load'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:232:in `load_dependency'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:241:in `load'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/commands/rails.rb:6:in `call'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/command_wrapper.rb:38:in `call'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:180:in `block in serve'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:153:in `fork'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:153:in `serve'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:128:in `block in run'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:122:in `loop'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:122:in `run'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application/boot.rb:18:in `<top (required)>'
	from /Users/nirnanaaa/.rvm/rubies/ruby-2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/nirnanaaa/.rvm/rubies/ruby-2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from -e:1:in `<main>'2.1.2 :004 >

I have then edited the file gitlab-grit/lib/grit/index.rb at line 176 and changing the [tmode, obj.name, sha] to [tmode, obj.name, sha.force_encoding("UTF-8")] works, but is not a good practice.
Some tests:

Create a page with the filename in english and the content in englisch - WORKS
Create a page with the filename in english and the content in chinese - WORKS
Create a page with the filename in chinese and the content in english - DOES NOT WORK

After trying to create the page with write_page once, each single of those tests in the current session will fail:
2.1.2 :007 >   name = "testpage"
 => "testpage"
2.1.2 :008 > B.test(wiki, name)
Encoding::CompatibilityError: incompatible character encodings: UTF-8 and ASCII-8BIT

	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gitlab-grit-2.6.12/lib/grit/index.rb:176:in `%'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gitlab-grit-2.6.12/lib/grit/index.rb:176:in `block in write_tree'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gitlab-grit-2.6.12/lib/grit/index.rb:171:in `each'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gitlab-grit-2.6.12/lib/grit/index.rb:171:in `write_tree'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gitlab-grit-2.6.12/lib/grit/index.rb:123:in `commit'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gollum-lib-3.0.0/lib/gollum-lib/committer.rb:170:in `commit'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/gollum-lib-3.0.0/lib/gollum-lib/wiki.rb:340:in `write_page'
	from /Volumes/Documents/chin.rb:24:in `test'
	from (irb):3
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/railties-4.1.4/lib/rails/commands/console.rb:90:in `start'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/railties-4.1.4/lib/rails/commands/console.rb:9:in `start'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/railties-4.1.4/lib/rails/commands/commands_tasks.rb:69:in `console'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/railties-4.1.4/lib/rails/commands/commands_tasks.rb:40:in `run_command!'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/railties-4.1.4/lib/rails/commands.rb:17:in `<top (required)>'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:247:in `require'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:247:in `block in require'
... 3 levels...
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:241:in `load'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:241:in `block in load'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:232:in `load_dependency'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/activesupport-4.1.4/lib/active_support/dependencies.rb:241:in `load'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/commands/rails.rb:6:in `call'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/command_wrapper.rb:38:in `call'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:180:in `block in serve'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:153:in `fork'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:153:in `serve'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:128:in `block in run'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:122:in `loop'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application.rb:122:in `run'
	from /Users/nirnanaaa/.rvm/gems/ruby-2.1.2/gems/spring-1.1.3/lib/spring/application/boot.rb:18:in `<top (required)>'
	from /Users/nirnanaaa/.rvm/rubies/ruby-2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/nirnanaaa/.rvm/rubies/ruby-2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from -e:1:in `<main>'2.1.2 :004 >

Debugging things a little further I found the following:
    now_tree.contents.each do |obj|
        sha = [obj.id].pack("H*")
        k = obj.name
        k += '/' if (obj.class == Grit::Tree)
        tmode = obj.mode.to_i.to_s  ## remove zero-padding
        debugger
        tree_contents[k] = "%s %s\0%s" % [tmode, obj.name, sha]
      end if

(rdb:1) tmode.encoding
#<Encoding:US-ASCII>
(rdb:1) tmode
"100644"
(rdb:1) obj.name.encoding
#<Encoding:UTF-8>
(rdb:1) obj.name
"你是我的中关星.md"
(rdb:1) sha.encoding
#<Encoding:ASCII-8BIT>

the emergence of Chinese, and then throws the  Exception.
Hope someone can help.
Thanks a lot

Took a look at this and encountered some surprising results. @nirnanaaa's test case works both with the rugged adapter and the grit adapter. However, in both cases, when trying to create a page with a name containing utf-8 cases via the gollum webapp, the pagename is transliterated (e.g. '你是我的中关星' => 'Ni Shi Wo De Zhong Guan Xing'). Conclusion: both grit and rugged now support utf-8 filenames, but gollum is messing up the page title. The problem is thus not in gollum-lib but in gollum, so I'm closing this and re-opening https://github.com/gollum/gollum/issues/830. See there for further diagnostics.

let me try with gollum_rails. I will report back


Cleanup of mini_allocator.c . Add unit-tests to exercise this module.

This is a draft PR built on top of PR #531. Code cleanup and unit-tests added to allocator.c and mini_allocator.c

Some smaller changes added to allocator.h and allocator.c, which should be peeled off to its own PR.

Other cleanup / code consolidation done to mini_allocator.c, along with unit-tests to exercise these interfaces.

Start a draft PR to see how the rest of the tests fare under CI.

Draft PR to shake-out some coding ideas / directions. Nothing more to be pursued.


feat: adds support for preset_mode: sleep

Note that this is my first PR to an HA integration and I'm not really sure how to test this but the changes seem to make sense.

thanks @grantland !


Web build as a separate branch or repo

What feature do you want to get added on the base engine?
Could you make a separate branch or repo for a web build such that it does not interfere with the desktop build. It's doesn't even have to be a part of the releases, I would just like to have a version to compile for a web server.
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor, 6K+ support, and winning icons.

No intention on adding Browser support again as it tends to hinder the Desktop build.

Not only does it hinder the Desktop builds, I have no interest in going back to work on browser builds.


ci: Check various FreeBSD versions

Since we suport multiple versions and this is tier 2, we should make sure that we can build with a couple versions. This does not run tests.
This introduces an environment variable for an easy way to override the version for testing.

:umbrella: The latest upstream changes (presumably #4157) made this pull request unmergeable. Please resolve the merge conflicts.

@asomers could you take a look at this? I don't think we should check all versions with all architectures on CI but we can at least check them all with the T1 i686 and x86_64.


Change codec and its options

Is it possible to set codec and rendering options for that codec in template or in prerender script?

if you are referring to output template modules for after effects, yes, it can be set
most of the things related to settings/output templates and other things described there:
https://github.com/inlife/nexrender#details

note: there is also link to adobe's documentation describing more

I see, thanks!
Vladyslav Hrytsenko<EMAIL_ADDRESS>schrieb am Fr. 1. März 2019
um 19:22:

if you are referring to output template modules for after effects, yes, it
can be set
most of the things related to settings/output templates and other things
described there:
https://github.com/inlife/nexrender#details
note: there is also link to adobe's documentation describing more
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/inlife/nexrender/issues/118#issuecomment-468761237,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAhnH4SagrFdemfdkkgM4Jg0ejIjUnucks5vSW_igaJpZM4bY7KV
.

Would it be possible to load and use output modules from a file?

not sure, what do you mean?

Right now, I can create an output module and use it in a AE instance running on my PC, but when I want to use the same output module on another machine I have to manually go there and import it.
Would it be possible to import output modules somewhere, eg. in a prerender script?

That is a good idea, however
I'm just worried about a potential possible collision of output module settings
particularly in case of let's say 2 running nexrender workers on the same machine attempt to replace a file that contains output module settings.
Also probably it is a good idea to revert to original file after rendering has finished, but again, what if the process was killed and auto-revert didn't happen.
The best case, probably, would be to add a custom entry to an output module settings, so it would replicate the one used in after effects.
Or even better, add an ability to directly set those settings from json job.settings. However, I'm not sure that the format of those settings is reversed since if I remember correctly it was a binary buffer.

Ok, I see that those issues might be too complicated to resolve properly.
I am still interested how that might be done for my own purpose. Are output modules just some file in AE that I can just replace? Where can I find it?

On windows:
%appdata%/Adobe/After Effects/$VERSION/Adobe After Effects $VERSION Prefs-indep-output.txt

Thanks! I will look into what can be done there. If I come up with a
solution that would solve issues raised by you I will post here. For now I
think you can safely close this issue.
Vladyslav Hrytsenko<EMAIL_ADDRESS>schrieb am Di. 19. März 2019
um 14:52:

On windows:
%appdata%/Adobe/After Effects/$VERSION/Adobe After Effects $VERSION Prefs-indep-output.txt
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/inlife/nexrender/issues/118#issuecomment-474379592,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAhnHzZj9uWDsbzmk2LSY1iRf-N7ZN44ks5vYOufgaJpZM4bY7KV
.

thank you!


Need an option to include extra files in deploy

We include other files in our deploy, config files, etc. It seems like roku_deploy has options to add these in, but I at first glance I'm not seeing the option for the launch.json in the extension.

@TwitchBronBron Best scenario would be defining files and what the would map to in the end output vs simply the files to include (since some mappings might be different). Currently we have custom build scripts that create "flavors" of the app.
For example, we may have
flavors/shared/resources/fonts
flavors/spanish/prod/resources/config/config.json
flavors/spanish/dev/resources/config/config.json
We'd want to map each resources folder to the root resources/.....
We'd merge shared and prod or shared and dev. By allowing mapping of the files/folders we could pull this off with the extension by simply having different configurations. ex: spanish-dev, spanish-prod, english-prod, etc

It appears that adding a rokudeploy.json doesn't work, but the files property although "not supported" does work as a pass thru. The only issue is that the file paths don't all resolve correctly and we can't map them. Thus it seems like the change may be less on this project and more on roku deploy. Looking into this some.

@TwitchBronBron I was able to make a simple change to the roku deploy script where rather than create absolute paths for ever file within a folder, etc that it just copied complete directories (which is probably way more efficient). In addition, I allowed the definition of src and dest for the files entry. All of this works like a charm and makes me very happy. Hopefully you can add this in and make it official.
Below is a sample of what a launch.json might look like with various stubs so you can see what I'm doing
{     // Use IntelliSense to learn about possible attributes.     // Hover to view descriptions of existing attributes.     // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387     "version": "0.2.0",     "configurations": [         {             "type": "brightscript",             "request": "launch",             "name": "flavor1-staging",             "stopOnEntry": true,             "host": "XXXXXX",             "password": "XXXXXX",             "rootDir": "${workspaceFolder}",             "files" : [                 {                     "src":"flavors/flavor1/manifest",                      "dest" : "manifest"                 },                 {                     "src":"flavors/flavor1/resources",                      "dest" : "resources"                 },                 {                     "src":"components",                      "dest" : "components"                 },                 {                     "src":"source",                      "dest" : "source"                 },                 {                     "src":"flavors/flavor1/staging/ADBMobileConfig.json",                      "dest" : "ADBMobileConfig.json"                 },                 {                     "src":"flavors/flavor1/staging/config.json",                      "dest" : "resources/config.json"                 },             ],             "consoleOutput": "normal"         }     ] }

I like it! Would you be willing to submit a pull request to the roku-deploy project with your changes? Then I will update the task information for this extension to make it more obvious which roku-deploy settings can be specified in the launch configuration.

@kbunch I finally got some time to put this together. I updated the roku-deploy project with your proposed {src;dest;} concept. Could you npm install the latest version of roku-deploy (v0.2.0-beta1) directly in your project and run a few tests to make sure it solves your issues? I don't want to release a new version of vscode-brightscript until I know that roku-deploy solves your issue.

Hi @TwitchBronBron , i wanted to use the same feature, but it gives me an error when trying to add a config file with the "file" property: Property files is not allowed.
Any suggestions?

@avoltis, this functionality only exists in the roku-deploy package right now, and is not yet in the vscode-brightscript-language extension. I was hoping that @kbunch would verify that it solves his needs using just roku-deploy, then I'll release a new version of vscode-brightscript-language with the upgraded roku-deploy package.

Hi @TwitchBronBron , just tested with rokudeploy.json included extra files and it is working fine :)  let us know when you release the new version 👍
Attached config:

@avoltis, I just released version 1.2.1 of the extension which includes this change. Can you test and make sure it's working?

@TwitchBronBron hi, yeah i did test it this morning. It is working 👍
Thank you !

My apologies, I ran an Ironman this past weekend and have been in CT this week with a client. I'll check when I get home to see if its working how we tweaked it. Many thanks ahead of time!

@TwitchBronBron its working 👍. Have a new request now ;). We write test files to run various tests while we are writing out all the logic. We stuff all of those files under components/test. These get pushed out to the end zip unless we exclude them in some way. Wondering if it makes sense to add an exclude value as a property to src, dest object OR if we add a way to run a post process node script. Thoughts?

I think you can accomplish this specific use case using a glob pattern (which roku-deploy already supports).
Change your glob pattern for the components folder to this (include all subfolders EXCEPT the test folder):
{
   "src": "components/!(test)/**/*'",
   "dest": ""
}

Does that solve your issue?

@TwitchBronBron That doesn't seem to work, trying different patterns, but I can't get it to move all the subfolders over to the components directory. We have folders like... yourdomain/app/content/utils/Foo.brs.


feat: add feedServiceWindow to JSON report

Summary:
Closes #1849
added feedServiceWindow to JSON report
Expected behavior:

Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[ ] Add or update any needed documentation to the repo
[x] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
[x] Linked all relevant issues
[x] Include screenshot(s) showing how this pull request works and fixes the issue(s)

Instead of adding a single field, feedServiceNow add two fields feedServiceNowStartDate and feedServiceNowEndDate. Having two fields instead of one will make the service date easier to parse.

@davidgamez


cancel chromedp.Run context will also cancel parent context

What versions are you running?

github.com/chromedp/chromedp v0.6.4
Chromium 88.0.4298.0
go version go1.15.5 linux/amd64

What did you do? Include clear steps.
	var options []chromedp.ExecAllocatorOption
	options = append(options, chromedp.DefaultExecAllocatorOptions[:]...)

	// create context
	aCtx, aCancel := chromedp.NewExecAllocator(context.Background(), options...)
	defer aCancel()

	ctx, cancel := chromedp.NewContext(aCtx)
	defer cancel()

	urls := []string{"https://www.google.com", "https://www.bing.com"}
	for _, url := range urls {
		func() {
			xCtx, xCancel := context.WithTimeout(ctx, time.Second*90)
			defer xCancel()
			err := chromedp.Run(xCtx, chromedp.Tasks{
				chromedp.Navigate(url),
			})
			if err != nil {
				log.Printf("%s failed: %s ", url, err)
				return
			}
			log.Println("success: ", url)
		}()
	}

What did you expect to see?
Run all task successful
What did you see instead?
2021/02/01 19:31:07 success:  https://www.google.com
2021/02/01 19:31:07 https://www.bing.com failed: context canceled

Currently cancel one task in the loop will cancel all other tasks

https://github.com/chromedp/chromedp/issues/746#issuecomment-771388870


fix: remove the metric keda_build_info from ms prometheus tests

Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

/run-e2e sequential


[DNM] bootstrap: set py3 as default

This is a duplicate for #1362 with only difference that here is python3 set as default

@susebot run deploy

retest this please

@susebot run deploy

@susebot run deploy

@susebot run deploy

retest this please

retest this please

@susebot run deploy


Treeview expand animation

It will conflict with combobox PR. You just need to keep only one version of MathMultiConverter

re. conflict, OK...let's work thru the combo box and I'll do this after.

done

@l1pton17 did u see the other one (missing ease function)

@ButchersBoy yep


Fix typo in gitea-postgres README

In the gitea-postgres README.md a nextcloud container was referenced instead of gitea, most likely it was copied from the nextcloud description.

Indeed!
Can you just do a git commit --amend -s --no-edit and push force to pass the DCO please?

Sorry I missed the failed test yesterday (and thanks for the notice), push the amended commit again.

thanks @winter0mute for the contribution 👍


PathParams double encoding fix

Fixes https://github.com/rest-assured/rest-assured/issues/1733

Will this PR ever be merged or looked at?

I am having a similar issue. Can someone look at this PR?  Thanks.

Hello @johanhaleby, would you happen to have a moment to review this?


Update get_ignores.js

#123
Instead of exiting on failed failed channel, process all --avoid channel and log the error before exiting.

If you want to just avoid a pair and not a channel, you can use the --avoid pubkey/pubkey syntax instead of --avoid chanId

#123
Instead of exiting on failed failed channel, process all --avoid channel and log the error before exiting.

Please help


Dynamically loading pdf blur, the same file official demo is very clear. I can't locate the problem

Dynamically loading pdf blur, the same file official demo is very clear. I can't locate the problem?
Use the chrome browser. Version 73.0.3683.86 (official version) (64-bit)
Here is my code：
async loadingPdf(getUint8Array, index) {
//渲染canvas
let pdf = await pdfjsLib.getDocument({ data: getUint8Array, cMapUrl: cMapUrl, cMapPacked: cMapPacked  });
let page = await pdf.getPage(1).then(page => {
return page;
});
let canvas = document.getElementById("the-canvas" + index);
       var viewport = page.getViewport(1.7);
  if (canvas.dataset.runed) return;
  //var CSS_UNITS = 150.0/ 72.0;
  var CSS_UNITS =120.0/ 72.0;
  canvas.width = viewport.width*CSS_UNITS;
  canvas.height = viewport.height*CSS_UNITS;

//  canvas.width = viewport.width;

//   canvas.height = viewport.height;
this.canvasW =
this.canvasW > (1000 / viewport.height) * viewport.width
? this.canvasW
: (1000 / viewport.height) * viewport.width;
canvas.style.width = (1000 / viewport.height) * viewport.width;
canvas.dataset.runed = true;
var context = canvas.getContext('2d');
// 【重要】关闭抗锯齿
context.mozImageSmoothingEnabled = false;
context.webkitImageSmoothingEnabled = false;
context.msImageSmoothingEnabled = false;
context.imageSmoothingEnabled = false;
await page.render({
//enableWebGL: true,
// canvasContext: context,
transform: [CSS_UNITS, 0, 0, CSS_UNITS, 0, 0],
//  transform: [1, 0, 0, 1, 0, 0],
canvasContext: canvas.getContext("2d"),
viewport: viewport
});
this.loadedPages.push(index)
},

I can't pinpoint the problem accurately, and reading all the source code obviously doesn't show up. So you need to help me take a look.

When opening as issue, you need to provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md and in this case please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md as well (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us on the IRC channel -- keep in mind that just code snippets won't help us troubleshoot the problem.

Thank you, reply me in your busy schedule. I am looking at the content inside your connection. What is the detailed record? For example, what about code snippets, data json, network requests, etc?


Revert "test: Add test socket interface that allows overriding IoHandle behavior (#12528)"

Revert "test: Add test socket interface that allows overriding IoHandle behavior (#12528)"
This reverts commit 5ddb5f45f4405dcc43175e5995821da4ac892ccb.
Signed-off-by: Yan Avlasov<EMAIL_ADDRESS>For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]

Are you reverting because of #12722 or some other issue? If the latter, I'll drop the fix.

It is likely the reason.


Favorite registration micro-interaction for Android

Overview
Implement a micro-interaction animation when tapping the favorite button on the timetable list. The animation should show a heart entering the "Favorites" tab (heart icon) in the bottom navigation from the timetable list's favorite button.
Links

Design: https://www.figma.com/design/XUk8WMbKCeIdWD5cz9P9JC/DroidKaigi-2024-App-UI

🙋　Can I take charge of this? It might take some time, though.

Thanks! Assigned 👍


Copy github.dev Link is giving a github.com link in VS Code insiders

Extension version: v0.62.0
VSCode Version: 1.78.0-insider
OS: MacOS

Steps to Reproduce:

Create a codespace using VS Code Insiders
Connect to it and open any file
Right click -> Share -> "Copy github.dev Link"

I was expecting a github.dev link but got a github.com link

@alexr00 what version of GHPRI do you have in Codespaces? I think Codespaces always bundles the stable version of GHPRI by default, and there is no way to switch to pre-release in product. May require installing from VSIX?

I don't see github.dev as an option at all

Yes, that's the intended behavior

Oops :) thought he fix was fixing it to actually go to github.dev instead of github.com. In that case, verified!

The version that shows is different in different places, but given that @TylerLeonhardt verified the issue it seems likely that the actual version is stable. I am following up about the inconsistent version:


Branches have diverged

@threezool could you please merge your changes from master to develop?

Sure, synced the dev branch and changed to it so not to affect the master branch.

Not fixed yet... https://github.com/StarcounterSamples/People/commit/e09579cde1cf157ec5253d6df9e8837c5931148a was reverted but master branch still needs to be merged to develop, because develop is two commits behind:

This is fixed now, thanks!


Hide plugins (in structure mode) - feature [re]quest(ion)

Other CMS provide the user with the possibility to 'hide' plugins, i.e. to not show them to the ordinary site visitor without having to delete them.
Is a similiar functionality in the making for djangoCMS by chance?
This might have been asked here before, in which case I apologize for my insufficient research.

What's the use case for this feature? (BTW you can easily create a HiddenPluginsPlugin which hides the contained plugins according to some specific rules -like: hide plugins for non staff users)

Use case: Some banner or image on a page that you periodically want to manually hide and show. Or some content that you need later but now happen to have the time to insert it in the CMS. You could then leave it hidden for the time being.
Can't think of anything more illustrating right now, but I have been asked this by multiple clients who were switching to djangoCMS and appreciated such functionality in their old CMS.
Of course I could create a HiddenPluginsPlugin, but a 'hide/show' option along with 'copy', 'edit', 'delete', ... in the structure view would appear much more convenient to me.

Looks legit. Thanks for the suggestion @creimers

@yakky Yes I'll be able to contribute this with some help. Is there documentation on how the structure mode works/is built?

You may have a look at the segmentation plugin.
https://github.com/aldryn/aldryn-segmentation
djangocms-casade also offers segmentation.

@creimers no need for structure mode: https://github.com/divio/django-cms/blob/develop/cms/plugin_base.py#L333-L340 use these to add items to the placeholder / plugin menu, a view in PlaceholderAdminMixin, then I guess we could handle this with a field that saves whether to hide the plugin or not.
In edit mode the plugin must be rendered (eventually adding a specific class to make visible they are "hidden"), so you'll need to adjust the get_plugins function https://github.com/divio/django-cms/blob/develop/cms/utils/plugins.py#L26

This has been discussed before, in fact I discussed it recently with someone but I can't remember where or with whom.
In short, it's a feature I've wished for since 2.3, and it would have enormous practical and time-saving use.
Each plugin that is publish-enabled (this might not be appropriate for every kind of plugin) should have a checkbox, Publish, that is on by default.
Whether this control should be visible in content as well as structure mode is not clear; why not both, if it's easy enough?
Actual use cases:

there was an emergency situation, and the home page of the site needed a prominent message, but we had to wait for the go-ahead before publishing it. Over the next few days we needed sometimes no message, and sometimes a modified version of it.

every so often, we want not to display a certain section of a page temporarily

on one page, we regularly published the same announcement at different times of the year, for a week or so; the rest of the time it wasn't needed

publish control over plugins would make managing this much easier, and without repeating our efforts
So, very strongly in favour.

My client has also requested this feature for the purpose of showing and hiding seasonal content, so I'm strongly in favor as well.
How should this feature interact with the new Alias plugin? Should an Alias that points to a hidden plugin always be hidden, or should its visibility always be independent of the source plugin? (I assume that if the source plugin is visible, you should be able to hide the Alias if you want to.)

implementing this on your own is not that hard, and indeed very usefull...I'm using this since quite some time. using arbitrary 3rd party plugins is more difficult, though.
Proof of concept:
https://github.com/bnzk/djangocms-baseplugins/blob/develop/djangocms_baseplugins/baseplugin/models.py#L80
https://github.com/bnzk/djangocms-baseplugins/blob/develop/djangocms_baseplugins/baseplugin/cms_plugins.py#L20
Making it opaque also works: https://github.com/bnzk/djangocms-baseplugins/blob/develop/djangocms_baseplugins/baseplugin/templates/djangocms_baseplugins/baseplugin_styles.html
Adding context menu items (show/hide) is a thought...but not a priority.

djangocms-cascade has such a feature implemented. There you can hide a plugin and all of its children.


Why some basic phrases doesn't exist?

Thanks to your effort to gather all these phrases, I'm using the corpus for spell checking but there are lot's of basic vocabs that are missing, like:
care
good
wear
call
morning
my
but
etc.

there is
CARE
Good
Wear
Call
Morning
MY
BUT

it was probably deduplicated and that the lowercase versions of these words were lost.
The words_alpha list has lowercase versions of these words.


Image Resizer 👍

📝 Provide a description of the new feature
What is the expected behavior of the proposed feature?  What is the scenario this woudl be used?
Control Click to change Add Size into Remove Size 👍
If you'd like to see this feature implemented, add a 👍 reaction to this post.

@jantoonen Could you be a bit more specific? Would you like to see a way to add a size when resizing images (and outside of settings)?

Op za 1 aug. 2020 om 15:03 schreef Niels Laute<EMAIL_ADDRESS>
@jantoonen https://github.com/jantoonen Could you be a bit more
specific? Would you like to see a way to add a size when resizing images
(and outside of settings)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/5426#issuecomment-667528812,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHSTD3A5RZT3HO5FLTQ7ZG3R6QHA3ANCNFSM4PRSZLSA
.

Just hit one too many times ADD. Can’t undo hence... the question to delete
an entry.
Regards
Jan Toonen

@jantoonen You can remove sizes by clicking the trash icon?

@jantoonen, do you not see the trash can icon?

I do, thanks. My default window was too small. After being attended on the
trashcan I dragged the windows larger and found and used the can.
Thanks
Jan Toonen
Op do 27 aug. 2020 om 18:19 schreef Clint Rutkas<EMAIL_ADDRESS>
@jantoonen https://github.com/jantoonen, do you not see the trash can
icon?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/5426#issuecomment-682050234,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHSTD3BW5L2RUM4SZPHTCRLSC2BPXANCNFSM4PRSZLSA
.

For me, the Powertoys window size was a bit too narrow after installation, did not show the trash can in full view and looked a bit weird, something like this:

The contents in the left pane are breaking too late when resizing, the right help / sidebar can overlap it quite a bit:

This is with Powertoys 0.25.0, Windows 10 1909, German locale

@chk1 this is a known issue we need to solve.   Tracked in https://github.com/microsoft/PowerToys/issues/2813


Dockerfile?

Hi there,
I was trying to set the matterbot up with a Dockerfile.
I have the following
FROM·python:3-slim
RUN·pip·install·mattermost_bot
ADD·mattermost_bot_settings.py·/srv/mattermost_bot_settings.py
WORKDIR·/srv
ENTRYPOINT·["matterbot"]

I run the docker container like so:
docker run -e MATTERMOST_BOT_SETTINGS=mattermost_bot_settings mbot

It seems that the matterbot is not seeing my settings as it is trying to connect to www.example.com/api/v3
What am I doing wrong here?

This way it works wonderfully
FROM python:3-slim

RUN pip install mattermost_bot

ADD mattermost_bot_settings.py /srv/mattermost_bot_settings.py
WORKDIR /srv

ENV MATTERMOST_BOT_SETTINGS_MODULE=mattermost_bot_settings

ENTRYPOINT ["matterbot"]


Have consolidated documentation for v4

We currently do have some docs for v4 -
https://github.com/EasyEngine/easyengine/tree/develop-v4/docs
But we also need it to be accessible to people via github pages or wiki or from our easyengine website.

@kirtangajjar -- I'm happy to help out with this. I would suggest using one of the following and am happy to get started once you let me know what the rest of the EasyEngine team decides on.

Using MkDocs with the MkDocs Material theme and hosting on GitHub Pages.

Using SphinxDoc with ReadTheDocs for building & hosting the docs.

Sphinx is a bit more complicated as reStructuredText isn't as widely understood as Markdown so contributing has a bit larger barrier to entry. However, it would also provide EasyEngine with the option to download a PDF and/or ePUB file for offline access and archiving.
cc: @rahul286 & @rahulsprajapati @rtCamp

@brianjking any reason to recommend MkDocs?
Among static site generators, I prefer Hugo, Gitbook and also Jekyll-Github-Pages.
Ideally, I would like to setup sync between a WordPress site and Github repo. May be using something like https://github.com/mAAdhaTTah/wordpress-github-sync

@rahul286 --

MkDocs is nice as editing content/creating new content requires just basic Markdown knowledge. It can be hosted for free on GitHub Pages, MkDocs Material theme is clean, responsive, has built in translation support, syntax highlighting, is version controlled, no hosting expenses or maintenance necessary as there would be with WordPress, it's made for writing documentation and IMO it does this very well.

As EasyEngine (and most other open source projects) suffer from lack of donations/income/sponsorship/volunteer time adding something such as WordPress seems to just add unnecessary maintenance and expenses.

Hugo & Jekyll are nice, however, I have less experience with either of these. I believe there is a port of the MkDocs Material theme for Hugo, however, it might be slightly out of date from my quick glance a few minutes ago here.

Gitbook is nice and definitely would be far more appealing to me than Hugo or Jekyll. It's easy to browse on computer, responsive for mobile, and has PDF and ePUB generation similar to what is generated with SphinxDoc when using ReadTheDocs.

Gitbook is limited to 2 users on the free plan. However, it looks like they have a free to use for non-profit & open source projects.
Let me know your thoughts...
cc: @kirtangajjar @rtCamp @rahulsprajapati

Any updates on this? Still available and would like to help contribute on these docs.
For a project that seems to suffer primarily from lack of volunteers who are actually looking to contribute code, support, or documentation this certainly hasn't been easy.
CC: @rahul286 @mbtamuli @kirtangajjar @rtCamp @rahulsprajapati

@brianjking I read https://docs.gitbook.com/v2-changes/important-differences and its seriously limiting. They are basically saying they discontinued whole thing!
Gitbook no longer uses git! No markdown etc. Better than calling it V2, they should have launched a new product IMHO.
At the moment, we are planning to use Github Pages and Jekyll only. The documentation work is yet to start https://github.com/EasyEngine/easyengine.github.io
We are really low on resources (or put it other way have a lot to work on than our team of 4-5 people can do!) :/

@rahul286 -- This is why I'm saying I can help out with docs as your core team is overloaded with work...

@brianjking You are more than welcome to help. How would you prefer to start? I mean do you need an outline of docs/content, or something else.

@rahul286 -- I'd need whatever you have in terms of docs/content for the v4 release. I'd really prefer to move forward with MkDocs over Jekyll, seems just much more straightforward.

I've setup this repo. Using GitBook.
https://github.com/EasyEngine/easyengine.github.io -> https://easyengine.github.io/
Will be adding documentation in a day or two.

We can generate PDF for offline access - https://toolchain.gitbook.com/ebook.html,
and we can have multi language support - https://toolchain.gitbook.com/languages.html
Will have to look into it. Will create issues once this is set up, and will ping you @brianjking for help if you still want to help. :slightly_smiling_face:

@mbtamuli
I thought based on @rahul286's comments here from 8 days ago and my comments from 28 days ago that GitBook isn't a good option since it's no longer using git, no longer generates PDF (in v2), no longer using Markdown and instead is using AsciiDoc....

V2 changes

cc: @rahul286 @kirtangajjar @rtCamp @rahulsprajapati

@brianjking  If you see here - https://github.com/GitbookIO/gitbook#publish-your-book it mentions legacy.gitbook.com as Heroku for books. As such, the changes mentioned here - https://docs.gitbook.com/v2-changes/important-differences, pertaining to docs.gitbook.com which is an upgrade from legacy.gitbook.com, is the hosted platform itself.
We're using GitBook CLI - https://github.com/GitbookIO/gitbook, and our purpose will be served in bringing documentation to the users. GitBook CLI documentation is at - https://toolchain.gitbook.com/ and it contains all the features that I mentioned https://github.com/EasyEngine/easyengine/issues/1084#issuecomment-415067699.
You can think of GitBook vs GitBook CLI as the same difference as Git vs GitHub
Also, if your concern is that someone wishing to contribute to the docs will have to use the git command line, they can simply use GitHub and edit markdown files directly, or we can configure the edit links to point to https://prose.io/ so that we have a proper Markdown editor.

@mbtamuli Yeah, I understand the differences between GitBook v2 and GitBook Legacy.
How can I help contribute to these docs in the repository you've setup here?
@rahul286 Perhaps you can help out as well as per your comment 6 days ago?
Thanks...

@brianjking sorry for a delayed reply.
We have started documentation here https://github.com/EasyEngine/docs#v4-docs
The README has all details to get you started including the link to topics we like to document - https://github.com/EasyEngine/docs/issues?q=is%3Aissue+is%3Aopen+label%3Adocumentation
I am closing this issue. If you need any input, we can start a disucssion in docs repo. :-)

@rahul286 https://twitter.com/brianjking/status/1067864888041566208

@brianjking since you prefer Twitter, posted reply on Twitter.


Fixed nullable areas

Resolves #18 , resolves #20 , resolves #21
fixed nullable areas.

Other merges need resolved then this one can be merged.

Done


Implement fitness caching

Sometimes fitness is expensive to calculate, allow for fitness caching (off by default)

The pros are not worth it


aminvakil merge

As discussed in https://github.com/inCaller/prometheus_bot/pull/117#issuecomment-2538756167
I'm merging all my commits from there to here.
This also adds ghcr.io deployment.

@hryamzik I cannot approve and merge my own request, and I cannot push to master.
Would you please merge this and later #119 ?

That's on purpose, at least one other person should review PRs

That's on purpose, at least one other person should review PRs

Fine, should I mention you every time I open a PR? I'm fine with that, just let me know.

you can add me as a reviewer


Delete _directory/cupboard.md

Unfortunately, Cupboard has now closed down. ☹ - thanks for letting us being a part of /packaging tho @kepano! 🙏

😢
Thanks for contributing!


Update contract to include Audience and OIDC Serviceaccount field

The contract between control- and data-plane needs to be configured to include the following fields for the Egress:

Audience of the Destination
Audience of the Reply
Audience of the Dead-Letter-Sink
OIDCServiceAccountName

The Ingress needs to be configured to include the Audience of the ingress (e.g. from the Broker object).
Additional Information:

contract file: https://github.com/knative-extensions/eventing-kafka-broker/blob/main/proto/contract.proto
To update the generated files, run ./hack/generate-proto.sh or /hack/update-codegen.sh

/assign


firefox-bin: 94.0 -> 94.0.1

Motivation for this change
Version bump.
Related: #144950
Things done

Built on platform(s)

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

[ ] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

dropbox
dropbox-cli
firefox-bin
firefox-bin-unwrapped
mate.caja-dropbox

I made a PR for 94.0.2 (#146616).  Closing this.


add kubernetes operator dashboard generator

The kubernetes operator runs node-exporter on a kubernetes node,
not Scylla node. Therefore, datacenter and cluster information does not
exist nor makes sense. Moreover, data is extracted from a
'kubernetes_node' instead of 'node'.
This patch makes those adaptations given a -k flag for load-grafana.sh
and -ko for make_dashboards.py.

Also would be nice to cherry-pick to scylla-monitoring-2.3 stable branch

we split the dashboards so that node_ related metrics will be in their own dashboard this way you can have different ips for the node_exporter and for scylla.
If you are using kubernetes as your node source (instead of reading the ip from a file).
you can use relabel to modify the instance label.
About changing the dc, it's better to change the dashboard to allow empty dc than to do that in a script.

we split the dashboards so that node_ related metrics will be in their own dashboard this way you can have different ips for the node_exporter and for scylla.
If you are using kubernetes as your node source (instead of reading the ip from a file).
you can use relabel to modify the instance label.
About changing the dc, it's better to change the dashboard to allow empty dc than to do that in a script.

I am in agreement with the above.

@jwnx I think we can replace this PR with a change to the dashboards that would allow empty DC.
Ping me if you need help with the configuration and relabeling.
If it will not work we'll see what we can do.
If it does work, it's best to add that to the documentation or knowledge base.

Closing


^4.0.0  No animation

No animation in Google Chrome
There is no animation in Google Chrome, there is no animation in the 4.0.4 version installed. But I can install 2.3.0.
var opts = {
lines: 13, // The number of lines to draw
length: 38, // The length of each line
width: 17, // The line thickness
radius: 45, // The radius of the inner circle
scale: 0.05, // Scales overall size of the spinner
corners: 1, // Corner roundness (0..1)
color: '#ffffff', // CSS color or array of colors
speed: 1, // Rounds per second
rotate: 0, // The rotation offset
direction: 1, // 1: clockwise, -1: counterclockwise
};
this._spinner = new Spinner(opts).spin(this.refs.dot);

Did you load the spin.css stylesheet file?

Yes I did. I have same error:

Possibly related: https://github.com/fgnass/spin.js/issues/373

Is the spinner on a white background? If you use white lines on a white background you won't be able to see them.


New version: Microsoft.Teams.Classic version <IP_ADDRESS>51

Created by 🥟 Dumplings in workflow run #6450.

Log
Updated: <IP_ADDRESS>69 → <IP_ADDRESS>51
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

https://github.com/microsoft/winget-pkgs/issues/142854


Fix yaml parser

This fixes Yaml file parsing (e.g. version.yaml files) like so:
1.1.1: this is a "new" release
1.1.2: !!! warning this is a "new" release
1.1.3:
  - my "new" item
  - my "other" item

gets replaced with:
1.1.1: "this is a 'new' release"
1.1.2: "!!! warning this is a 'new' release"
1.1.3:
  - "my 'new' item"
  - "my 'other' item"

@bennothommo @LukeTowers I guess I can close this one, right?

Implemented with https://github.com/wintercms/winter/commit/defb57f59cf69502cdc41f97866ef494fe46ecc6 - thanks @mjauvin!


Update pre-commit config

Changes proposed in this Pull Request

Addresses the following error:
build attempt 1...
    => error
    An error has occurred: InvalidManifestError:
    ==> File /pc/clone/jNZWZVRSTLq-4hbwuef7PA/.pre-commit-hooks.yaml
    ==> At Hook(id='docformatter-venv')
    ==> At key: language
    =====> Expected one of conda, coursier, dart, docker, docker_image, dotnet, fail, golang, haskell, lua, node, perl, pygrep, python, r, ruby, rust, script, swift, system but got: 'python_venv'
    Check the log at /pc/pre-commit.log

Checklist

[ ] I tested my contribution locally and it seems to work fine.
[ ] Code and workflow changes are sufficiently documented.
[ ] Changed dependencies are added to envs/environment.yaml.
[ ] Changes in configuration options are added in all of config.default.yaml.
[ ] Changes in configuration options are also documented in doc/configtables/*.csv.

oh shoot i actually fixed this in my PR, forgot to mention i found this issue too

If I pull the pre-commit from master, so many files change? Maybe this is the issue?

These changes overlap with changes in master


PENV-293 send test run results to testrail

- What I did
- How I did it
- How to verify it
- Description for the changelog

Codecov Report

Merging #49 into master will decrease coverage by 0.47%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #49      +/-   ##
==========================================
- Coverage   66.01%   65.54%   -0.48%
==========================================
  Files          35       35
  Lines        1701     1701
==========================================
- Hits         1123     1115       -8
- Misses        488      496       +8
  Partials       90       90

Impacted Files
Coverage Δ

etl/extractor/platform_impl.go
70.53% <0.00%> (-7.15%)
:arrow_down:

Continue to review full report at Codecov.

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


look and feel

Describe the bug

set intro paragraph width to be the same width as other paragraphs below it (same as the 3 buttons view team instance, set up dev tools, manage ....)
Install button and learn more for mobile foundation not centered (this was fixed in the other so apply the same fix)
For learn more expanded boxes, Install button and Close buttons should both be in the lower left corner and the Install button should be first, followed by Close after it

this is no longer needed as a redesign is coming for the index page


deploy on tags

Closes #55. Purely only Alessandro suggestions
Checklist before merge:

[ ] Reviewers confirm new code works as expected.
[ ] Tests are passing.
[ ] Documentation is updated.

Codecov Report
Patch and project coverage have no change.

Comparison is base (af13fbb) 72.42% compared to head (8489bf1) 72.42%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   72.42%   72.42%
=======================================
  Files          11       11
  Lines         544      544
=======================================
  Hits          394      394
  Misses        150      150

Flag
Coverage Δ

unittests
72.42% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Frankly, I don't understand why you prefer tags instead of releases, when you release you make a tag and this generates a clear release page in github with all diffs and PRs. I would prefer to keep it simple with a releases-only approach, in symmetry with the other repos.

My only doubt on these "fast" releases/tags is that I will end up doing a new one almost every PR. But I trust your choice and experience on the matter.
Also in the debate between releases and tags, for me it is almost the same...
Maybe it is nicer to group several PRs in a single new releases, while still publishing on tags more frequently. But again I don't have strong opinions


uJIT hits assertion at lj_record.c:1453

uJIT (current master) crashes with assertion  on Centos 7 if built with CMAKE_BUILD_TYPE=DEBUG.
ujit: /home/master/rpm/luavela-master/src/jit/lj_record.c:1453: rec_varg_setup: Assertion `nvararg >= 0' failed.

I guess this assertion goes largely unnoticed in release builds introducing opportunity for more subtle bugs and/or state corruption somewhere down the line.
The code that causes this is rather complex, and we couldn't strip it down to a simple test case. Nevertheless, it works well on vanilla Lua 5.1 and LuaJIT 2.x, and a move to uJIT has been just an experiment for us for some time. The code employs heavy use of coroutines, varargs/results and various tricks using setfenv().

@igelhaus FYI. Please let me know if there's anything we can do to help hunt this bug if anyone interested of course...

#0  0x00007f249cb3f387 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55
55	  return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0  0x00007f249cb3f387 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55
#1  0x00007f249cb40a78 in __GI_abort () at abort.c:90
#2  0x00007f249cb381a6 in __assert_fail_base (fmt=0x7f249cc93ce0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x494cc8 "nvararg >= 0",
    file=file@entry=0x493758 "/home/master/rpm/luavela-master/src/jit/lj_record.c", line=line@entry=1453, function=function@entry=0x495230 <__PRETTY_FUNCTION__.8523> "rec_varg_setup") at assert.c:92
#3  0x00007f249cb38252 in __GI___assert_fail (assertion=assertion@entry=0x494cc8 "nvararg >= 0", file=file@entry=0x493758 "/home/master/rpm/luavela-master/src/jit/lj_record.c",
    line=line@entry=1453, function=function@entry=0x495230 <__PRETTY_FUNCTION__.8523> "rec_varg_setup") at assert.c:101
#4  0x000000000043a6f1 in rec_varg_setup (J=0x7f249dc09888, J=0x7f249dc09888, trftsz=318799887, nresults=-1, dst=13) at /usr/src/debug/luavela-master/src/jit/lj_record.c:1453
#5  rec_varg (J=J@entry=0x7f249dc09888, dst=dst@entry=13, nresults=nresults@entry=-1) at /usr/src/debug/luavela-master/src/jit/lj_record.c:1678
#6  0x000000000043d282 in lj_record_ins (J=J@entry=0x7f249dc09888) at /usr/src/debug/luavela-master/src/jit/lj_record.c:2135
#7  0x000000000043522e in trace_state (L=<optimized out>, dummy=<optimized out>, ud=<optimized out>) at /usr/src/debug/luavela-master/src/jit/lj_trace.c:569
#8  0x0000000000471984 in lj_vm_cpcall ()
#9  0x0000000000435b80 in lj_trace_ins (J=<optimized out>, pc=<optimized out>) at /usr/src/debug/luavela-master/src/jit/lj_trace.c:629
#10 0x0000000000475eac in hook_record_ins (pc=0x7f249bb29dc8, L=0x7f249b630db8) at /usr/src/debug/luavela-master/src/uj_hook.c:118
#11 uj_hook_ins (L=0x7f249b630db8, pc=0x7f249bb29dc8) at /usr/src/debug/luavela-master/src/uj_hook.c:177
#12 0x0000000000473cbe in lj_vm_inshook ()
#13 0x0000000000472597 in lj_ff_coroutine_resume ()
#14 0x000000000040a80a in lua_pcall (L=<optimized out>, nargs=<optimized out>, nresults=<optimized out>, errfunc=<optimized out>) at /usr/src/debug/luavela-master/src/uj_capi.c:966
#15 0x0000000000405e4c in docall (L=0x7f249dc09378, narg=1, clear=0) at /usr/src/debug/luavela-master/src/ujit.c:123
#16 0x0000000000406c0a in preprocess_and_call (clear=0, narg=1, L=0x7f249dc09378) at /usr/src/debug/luavela-master/src/ujit.c:222
#17 handle_script (n=<optimized out>, argv=<optimized out>, L=<optimized out>) at /usr/src/debug/luavela-master/src/ujit.c:344
#18 pmain (L=0x7f249dc09378) at /usr/src/debug/luavela-master/src/ujit.c:750
#19 0x0000000000471489 in lj_BC_FUNCC ()
#20 0x000000000040a8d3 in lua_cpcall (L=<optimized out>, func=<optimized out>, ud=<optimized out>) at /usr/src/debug/luavela-master/src/uj_capi.c:989
#21 0x000000000040585d in main (argc=3, argv=0x7ffce98fac48) at /usr/src/debug/luavela-master/src/ujit.c:790
(gdb) fr 4
#4  0x000000000043a6f1 in rec_varg_setup (J=0x7f249dc09888, J=0x7f249dc09888, trftsz=318799887, nresults=-1, dst=13) at /usr/src/debug/luavela-master/src/jit/lj_record.c:1453
1453	  lua_assert(nvararg >= 0);
(gdb) print nvararg
$1 = -1
(gdb)

Please let me know if there's anything we can do to help hunt down this bug. If anyone interested of course...

@neoxic, does the issue still present? Are there any related updates?

The following fixes to LuaJIT might be related to this issue:
https://github.com/LuaJIT/LuaJIT/issues/611
https://github.com/LuaJIT/LuaJIT/issues/624

Right, I'll see whether these issues are related to this one, thanks!


The logo images aren't consistent, and they're not centred properly

Hello is this issue still valid, I would like to contribute and which logo images are you referring to.
As I looked into the code I saw only 2 logo images which are

This isn't relevant anymore. Closing


New Block Version

Block Version 805306368 recently released. Once the parser hits blk00443.dat it will fail around half way through and the entire process will end. DLL needs to be updated to handle the new block version.

Thank you TheAxZim. The issue is now fixed with v 1.5


Enhances command spo orgassetslibrary add, Closes #4842

Closes #4842

Thank you @nicodecleyre! We'll try to review it ASAP!

Hi @nicodecleyre, marked the PR as a draft again because the Documentation seems to be broken. Could you have a look at it, please?

Hi @nicodecleyre, marked the PR as a draft again because the Documentation seems to be broken. Could you have a look at it, please?

it's fixed now... But strange fix if you ask me 😄

Hi @nicodecleyre
The pipeline succeeded because removed the backticks for the options list. This way the page will be rendered totally different and the link doesn't break because it's not interpreted as a link. You should do the following things to fix it:

Readd the option backticks.
Remove remark indents
Fix the link path, you can always look at other examples. The .mdx at the end shouldn't be required.

Could you have a look at it again?

Hi @nicodecleyre
The pipeline succeeded because removed the backticks for the options list. This way the page will be rendered totally different and the link doesn't break because it's not interpreted as a link. You should do the following things to fix it:

Readd the option backticks.
Remove remark indents
Fix the link path, you can always look at other examples. The .mdx at the end shouldn't be required.

Could you have a look at it again?

Thx man, that really helped!

Hey @nicodecleyre, I'm getting some merge conflicts when pulling down the PR. Could you please have a look so that we don't lose any of your changes? Thank you! ❤

Merged manually. Thank you! 👏


Docs on Read the Docs are incomplete

The docs hosted at https://render-engine.readthedocs.io/en/latest/ are missing all of the autodoc documentation, but if I render the docs locally (after modifying my local Makefile as described in #44) all docs are present. After a bit of searching through the documentation build logs, it seems like the project may not be installed by RTD before building? I set up a different sphinx environment without installing render_engine, and resulting documentation build seemed to be the same as what I see on RTD. One possible explanation: if the RTD "Install Project" setting (under the "Advanced Settings" Admin section) is not enabled, that step might be getting skipped and ignoring the missing components to build mostly blank docs.

@all-contributors please add @jonafato for code


Add Closure to CSV Download

Overview
Add the facility closure status to the CSV downloads in the case that
the report_a_facility switch is on.
Connects #1248
Demo

Testing Instructions

Run ./scripts/server
Turn off the Reports switch and download the facilities CSV

[ ] It should not have an 'is_closed' column

Turn on the Reports switch and download the facilities CSV

[ ] It should have an 'is_closed' column with appropriate data

Checklist

[ ] fixup! commits have been squashed
[ ] CI passes after rebase
[ ] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines

I agree that 'CLOSED' is going to be clearer for non-technical users. I've updated the code to use 'CLOSED' when True and otherwise display nothing, and updated the test to check for handling both True and False.


Unable to install SQL Server 2019 and  2022 in my Brand new Asus tuf A17

@DEVRAJSINH1625 -- thank you for your feedback.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow


Function1 in tooltip

object Demo {
  def f(a: Int)(f: Int => Double) : Int = ???
  def g(a: Int) = Demo.f(a) _
}

The tooltip for Demo.f shows f(a: scala.Int)(f: Function1[scala.Int, scala.Double]) : scala.Int
It would be awesome if Function1 types could be converted into X => Y syntax, and the scala. prefix of standard types could be ommited (as in Eclipse IDE)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27062088-function1-in-tooltip?utm_campaign=plugin&utm_content=tracker%2F14719420&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F14719420&utm_medium=issues&utm_source=github).

Function: Acknowledged! I was thinking the same, but never got around to it.
scala-package: Sure, I'll fix that.

Should be fixed in 0.25


Unable to effectively prevent occlusion

Hello, I am using your project in Inside_ Out_ In the tracker file, my occlusion has a significant impact on him. As long as it is occluded, it cannot be detected. I request your help

Can you upload a screen recording of the effect? You can drag and drop a video file into your reply on this issue, or upload to imgur.com.

When I look at your video, it's apparent that the tracker never initializes properly. That's why there are a cluster of tags right in the middle of the screen.

When working properly, each tag in this cluster moves towards its correct location. Additionally you can tell by the huge tracking error that the program has not successfully figured out where the camera is.

Have you checked that the map that was built (try python pytagmapper_tools/show_map.py [the map directory]) matches what you see in real life? Please paste a screenshot.
Also it looks like your setup is 2D, so you should use --mode 2d  when you run build_map.py.

@zh-csc Any updates?

I'm not sure where my problem lies, but I now suspect it's an initialization issue (referencing your other issue, which was shot with an iPhone, and I suspect the iPhone's lens zooming may result in inaccurate camera parameters). My issue is similar, and I suspect it's a distortion or camera parameter problem. However, even after changing the camera, there hasn't been much improvement.Finally, thank you for your patient replies and assistance. Best wishes!

No problem! In the other issue, the user mentioned some alternative software that ended up working well for him. I encourage you to try that as well.


Bug with Midi QoL Module

Hi, the module have a bug with midi-QoL
Bug:

Normal:

I've had the same issue. It causes similar issues in some other modules as well, for instance TheRipper's new D&D5e System customization module.

Same issue here. It's definitely a CSS conflict. I think I isolated it to the following:

.window-app . window-content
{display: flex;}
If you turn off the flex, all other windows work properly but the emoji popout doesn't render. You get a message, "Failed to load emojis. Try again."

Fixed with the 2.3.0 release


significant differences in MPD between t10 and t1, t11-t17

t10-t17 are supposed to be the same as t1 except for a content option. The MPD for t10 however has a number of small differences.
(Edited)

$ diff t1/stream.mpd t10/stream.mpd
1,2c1,6
< <?xml version="1.0" ?><!-- MPD file Generated with GPAC version 1.1.0-DEV-rev779-g7cda102d5-master at 2021-04-30T09:12:39.113Z --><MPD xmlns="urn:mpeg:dash:schema:mpd:2011" minBufferTime="PT2.000S" type="static" mediaPresentationDuration="PT0H1M0.000S" maxSegmentDuration="PT0H0M2.021S" profiles="urn:mpeg:dash:profile:isoff-live:2011,urn:mpeg:dash:profile:cmaf:2019,urn:cta:wave:test-content-media-profile">
<
---
> <?xml version="1.0"?>
> <!-- MPD file Generated with GPAC version 1.1.0-DEV-rev779-g7cda102d5-master at 2021-04-30T09:16:04.456Z -->
> <MPD xmlns="urn:mpeg:dash:schema:mpd:2011" minBufferTime="PT2.000S" type="static" mediaPresentationDuration="PT0H1M0.000S" maxSegmentDuration="PT0H0M2.021S" profiles="urn:mpeg:dash:profile:isoff-live:2011,urn:mpeg:dash:profile:cmaf:2019">
>  <ProgramInformation moreInformationURL="http://gpac.io">
>   <Title>stream.mpd generated by GPAC</Title>
>  </ProgramInformation>
4,5c8,9
<  <ProgramInformation><Source>CTA WAVE</Source><Copyright>CTA WAVE</Copyright></ProgramInformation><Period duration="PT0H1M0.000S">
<   <AssetIdentifier schemeIdUri="urn:cta:org:wave-test-mezzanine:unique-id" value="0"/><AdaptationSet segmentAlignment="true" lang="und" startWithSAP="1" contentType="audio" segmentProfiles="cmfs, cmff">
---
>  <Period duration="PT0H1M0.000S">
>   <AdaptationSet segmentAlignment="true" lang="und" startWithSAP="1">
21c25
<   <AdaptationSet segmentAlignment="true" maxWidth="1920" maxHeight="1080" maxFrameRate="30" par="16:9" lang="und" startWithSAP="1" contentType="video" segmentProfiles="cmfs, cmff">
---
>   <AdaptationSet segmentAlignment="true" maxWidth="1920" maxHeight="1080" maxFrameRate="30" par="16:9" lang="und" startWithSAP="1">
27c31
<    <Representation id="2" mimeType="video/mp4" codecs="avc1.64002A" width="1920" height="1080" frameRate="30" sar="1:1" bandwidth="5100000">
---
>    <Representation id="2" mimeType="video/mp4" codecs="avc1.64002A" width="1920" height="1080" frameRate="30" sar="1:1" bandwidth="4800000">

This is the diff between the MPD for t10 and for t11. Something similar applies for t10 and t12 onwards.
diff t10/stream.mpd t11/stream.mpd
1,6c1,2
< <?xml version="1.0"?>
< <!-- MPD file Generated with GPAC version 1.1.0-DEV-rev779-g7cda102d5-master at 2021-04-30T09:16:04.456Z -->
< <MPD xmlns="urn:mpeg:dash:schema:mpd:2011" minBufferTime="PT2.000S" type="static" mediaPresentationDuration="PT0H1M0.000S" maxSegmentDuration="PT0H0M2.021S" profiles="urn:mpeg:dash:profile:isoff-live:2011,urn:mpeg:dash:profile:cmaf:2019">
<  <ProgramInformation moreInformationURL="http://gpac.io">
<   <Title>stream.mpd generated by GPAC</Title>
<  </ProgramInformation>
---
> <?xml version="1.0" ?><!-- MPD file Generated with GPAC version 1.1.0-DEV-rev779-g7cda102d5-master at 2021-04-30T09:15:11.280Z --><MPD xmlns="urn:mpeg:dash:schema:mpd:2011" minBufferTime="PT2.000S" type="static" mediaPresentationDuration="PT0H1M0.000S" maxSegmentDuration="PT0H0M2.021S" profiles="urn:mpeg:dash:profile:isoff-live:2011,urn:mpeg:dash:profile:cmaf:2019,urn:cta:wave:test-content-media-profile">
>
8,9c4,5
<  <Period duration="PT0H1M0.000S">
<   <AdaptationSet segmentAlignment="true" lang="und" startWithSAP="1">
---
>  <ProgramInformation><Source>CTA WAVE</Source><Copyright>CTA WAVE</Copyright></ProgramInformation><Period duration="PT0H1M0.000S">
>   <AssetIdentifier schemeIdUri="urn:cta:org:wave-test-mezzanine:unique-id" value="0"/><AdaptationSet segmentAlignment="true" lang="und" startWithSAP="1" contentType="audio" segmentProfiles="cmfs, cmff">
25c21
<   <AdaptationSet segmentAlignment="true" maxWidth="1920" maxHeight="1080" maxFrameRate="30" par="16:9" lang="und" startWithSAP="1">
---
>   <AdaptationSet segmentAlignment="true" maxWidth="1920" maxHeight="1080" maxFrameRate="30" par="16:9" lang="und" startWithSAP="1" contentType="video" segmentProfiles="cmfs, cmff">
31c27
<    <Representation id="2" mimeType="video/mp4" codecs="avc1.64002A" width="1920" height="1080" frameRate="30" sar="1:1" bandwidth="4800000">
---
>    <Representation id="2" mimeType="video/mp4" codecs="avc1.64002A" width="1920" height="1080" frameRate="30" sar="1:1" bandwidth="4700000">

From the legacy script we make some manual manipulation on the manifest. I put comments in the code to try to get rid of this. Apparently this post-processing went wrong for t10 but the error was not catched. Let me check.

Another issue with t10 is that t10.zip is missing. It seems to be the only one so perhaps it's another casualty of the same issue?

Ok this is fixed.
I understand what happened. The specific version of gpac used couldn't chains the bsrw (bitstream rewrite filter) that removed the SEIs, change the SAR, and set the VUI. The error was actually reported but I missed it.

Could you check it is ok now?

Looks OK.


GH-40827: [Java] Adding Spotless to Gandiva module

Rationale for this change
Applying Java code style and formatting options to Gandiva module.
What changes are included in this PR?
Java code formatting via spotless plugin has been enabled.
Are these changes tested?
Yes, but doesn't involve test cases, the plugin itself corrects.
Are there any user-facing changes?
No

GitHub Issue: #40827

@github-actions crossbow submit -g java

CI test failure seems to be unrelated.

CI test failure seems to be unrelated.

Yes, it looks like a transient issue with quay.io container images service
ERROR: failed to solve: quay.io/pypa/manylinux2014_x86_64:2024-02-04-ea37246: pulling from host quay.io failed with status code [manifests 2024-02-04-ea37246]: 502 Bad Gateway


Custom node_modules location, working directory, environment variables

In our environment we have multiple kernels under app directory e.g. symfony-project/app/[kernel]/config/ and the location of node_modules is shared among these. The cache and Resources directories location also specific, e.g. symfony-project/user/app/[kernel]/cache/, and it is the %kernel.root_dir%  so node_modules is not even in ascendant directory relatively to config.yml and webpack.config.js. Probably this bundle was meant to be used in simple environments, hence several issues arose.

The 'app' => '%kernel.root_dir%/Resources/assets', is hardcoded and leads to an error. Must be overridden.

When webpack process is started in %kernel.root_dir%/.. it won't find node_modules directory and webpack-dashboard is obviously fails to run.

tty can be disabled by providing an empty array or alternatively a direct path in the actual node_modules can be specified
Usually it is possible to use export NODE_PATH=... before calling a node script but looks like such possibility, to add custom environment variables, is not provided in bundle's WebpackCompiler class (btw, ProcessBuilder has an addEnvironmentVariables method that can be used instead of command line concatenation in addEnvironment).
Another webpack integration bundle, the hostnet/webpack-bundle provides the node_modules_path key in config, though we would really like to stick with maba's implementation.
The maba_webpack.root_directory parameter in services.xml have a hardcoded %kernel.root_dir%/.. value and is used in WebpackCompiler to set the working directory and as noted in that xml it is Not configurable from config.yml. However it maybe solve the problem. Please reconsider making it configurable. Thanks

@mariusbalcytis I may try to implement these features in a PR

About first problem - I think overriding alias is the way ahead. Or do you think behavior should be changed somehow?
node_modules could be fixed by changing configuration for executables and TTY prefix, but it's really more clearer to add configuration for root directory as you've suggested.
Could you overwrite maba_webpack.root_directory parameter in your config.yml or parameters.yml and check if this would resolve your issue? In that case I'd extend configuration for it.
As I understand, you also need to change node_modules location and/or environment? Would this still be needed? If environment variables would be changed, reconfiguration of executables would still be needed as they include path from working directory (if it's not by current convention in your case).
Pull requests are also welcome - just try to maintain the code style and don't break the tests ;)
By the way, export was added as setEnv was not working as expected, but as I see now, ProcessBuilder can inherit current environment which should resolve the initial issue. Thanks for noticing, I'll check that out.

imho the @app alias is excessive and it brings troubles to those who don't have Resources directly in the app dir. It's easy for a dev to add this if required, based on another hardcoded alias, the @root.
Yep, my current webpack.yml that is imported to config.yml looks like this (I had to put it to a separate file because it became unexpectedly large):
maba_webpack:

    # webpack.config.js must be under a sibling directory of node_modules
    # https://github.com/mariusbalcytis/webpack-bundle/issues/38
    config:
        path: '%dir.symfony%/webpack/symfony/symfony-webpack.config.js'
        parameters:
            logLevel: '%webpack_log_level%'

    bin:
        webpack:
            executable:
                - node
                - '--max-old-space-size=4096' # 4GB
                - '%node_modules%/.bin/webpack'

        dev_server:
            executable:
                - node
                - '--max-old-space-size=4096' # 4GB
                - '%node_modules%/.bin/webpack-dev-server'

            # currently webpack-dashboard cannot be optional (toggled with a boolean through parameters.ini)
            # https://github.com/mariusbalcytis/webpack-bundle/issues/39
            tty_prefix:
                - node
                - '%node_modules%/webpack-dashboard/bin/webpack-dashboard.js'
                - '--'

            arguments:
                - --inline
                - --host
                - '%webpack_host_ip%'

    asset_providers:
        -
            type: twig_bundles
            resource:
                # Backend
                - OpenbizboxBackendBundle
                - OpenbizboxDesignWizardBundle
                - OpenbizboxSetupBundle
                # Frontend
                - OpenbizboxCheckoutBundle
                - OpenbizboxFrontendBundle

    aliases:

        additional:
            app: '%dir.user%/app'
            # Backend vendor
            be_node_modules: '%node_modules.backend%'
            be_bower: '%node_modules.backend%/@company/backend-vendor/bower_components'
            be_vendor: '%node_modules.backend%/@company/backend-vendor/vendor'
            # Frontend vendor
            node_modules: '%node_modules.frontend%'
            bower: '%node_modules.frontend%/@company/frontend-vendor/bower_components'
            vendor: '%node_modules.frontend%/@company/frontend-vendor/vendor'

        register_bundles:
                # Backend
                - OpenbizboxBackendBundle
                - OpenbizboxDesignWizardBundle
                - OpenbizboxSetupBundle
                # Frontend
                - OpenbizboxCheckoutBundle
                - OpenbizboxFrontendBundle

Not too complicated, simply two kernels - for the frontend and the admin area.
As you can see, in order to be able to use your bundle currently paths to all scripts had to be overridden.

Could you overwrite maba_webpack.root_directory parameter in your config.yml or parameters.yml and check if this would resolve your issue? In that case I'd extend configuration for it.

root_directory cannot be overwritten
 Unrecognized option "root_directory" under "maba_webpack"

that's because $ignoreExtraKeys by default is false for ArrayNodeDefinition of a Symfony\Component\Config\Definition\Builder. In order to not throw an error, when extra keys should just be ignored without an exception, the ignoreExtraKeys(false) should be called on $rootNode (maba_webpack)  in Configuration::getConfigTreeBuilder. First argument is to not remove extra keys.
But that is not enough, because the final parameters that are merged to Symfony's DependencyInjection\ParameterBag are added in MabaWebpackExtension the loader of bundle's config and here the params of main app's config.yml (that are provided to load function in $configs array) are selectively applied with $container->setParameter.

Pull requests are also welcome - just try to maintain the code style and don't break the tests ;)

Regarding code style, I prefer chained (fluent) API, e.g. instead of:
        $prototype = $assetProviders->prototype('array');
        $prototypeChildren = $prototype->children();
        $prototypeChildren->scalarNode('type');
        $prototypeChildren->variableNode('resource');

I would write:
        $assetProviders->prototype('array')
                $prototype->children()
                        ->scalarNode('type');
                        ->variableNode('resource')
                ->end()
        ;

it's also a preferred style in Symfony docs.
Also I prefer yml over xml for configs and would split services.xml to parameters.yml and services.yml.
If you don't mind I would make such small changes, in a separate pull request if you wish.

As I understand, you also need to change node_modules location and/or environment?

Looks like you already had plans to make a configurable prefix. Currently an empty array is provided as $prefix to buildProcess() in compile  and exec in compileAndWatch on Linux systems.

By the way, export was added as setEnv was not working as expected

It still works unexpected when node_modules directory is in a different place :) and also limits possibilities of command-line customization, the prefix part to be precise.
The $processBuilder->setPrefix($ttyPrefix); is
The NODE_PATH is required for require-d scripts but not for the called scripts, i.e. calling 'node' 'node_modules/webpack/bin/webpack.js' will not work without proper working directory. So really is a cd %node_modules% required before the default maba_webpack.bin.webpack.executable. And here we have a problem. E.g. with following configuration
maba_webpack:
    bin:
        webpack:
            tty_prefix:
                - cd
                - '%node_modules%;'

we get an error
[Symfony\Component\Process\Exception\ProcessFailedException]
  The command "TTY_MODE=on 'cd' '/project/user/app/backend/../../../core/symfony/node_modules;' 'node' '
  node_modules/webpack/bin/webpack.js' '--config' '/obb/openbizbox/user/app/backend/cache/dev/webpack.config.js
  '" failed.
  Exit Code: 1(General error)
  Working directory: /project/user/app/backend/..

Today I had problems with the hardcoded manifest_file_path too, again, because of our multi-kernel approach. To avoid running multiple webpack dev-servers for every bundle (increases complexity) we need to have a single location for cache files. Every kernel have it's own console command, but the list of commands is same, thus e.g. when running app/kernel1/console the %kernel.cache_dir% is user/app/kernel1/cache and you can imagine where the cache_dir points for another kernel.
Having ability to override the %kernel.cache_dir% will give ability to use webpack in multi-kernel environments like ours.


using my own data, I can use test.py to generate 360 scene images, but I cannot extract mesh file

Describe the bug
using my own data, I can use "test.py" to generate 360 scene images, but I cannot extract the mesh file. I got something like

I think that the problem is the setting of x,y,z range. However, I modified them and it does not work.
Which branch you use
dev

I know where the problem is. When training the NeRF on your own data, use downscaled images, rather than the original size. More importantly, downsampling your own images by 8 times (about 400*400) works. Otherwise, the model cannot successfully extract the 3D mesh.


#4 API GET Routes in Insomnia

WHEN I open API GET routes in Insomnia Core for categories, products, or tags
THEN the data for each of these routes is displayed in a formatted JSON


Merge u1, u2 and p gate together if they contain parameters.

Summary
Before the fix, the 'Optimize1qGates' transpiler optimization join together the gate only when the parameter was bounded (or when there was no parameter at all). After the fix, the u1, u2, and p gates will be combined even when the parameter is unbounded.
from qiskit import QuantumCircuit
from qiskit.circuit import Parameter
from qiskit.transpiler import PassManager
from qiskit.transpiler.passes import Optimize1qGates, Unroller
phi = Parameter('φ')
alpha = Parameter('α')
qc = QuantumCircuit(1)
qc.u1(2*phi, 0)
qc.u1(alpha, 0)
qc.u1(0.1, 0)
qc.u1(0.2, 0)
qc.draw(output='mpl')

pm = PassManager([Unroller(['u1', 'cx']), Optimize1qGates()])
nqc = pm.run(qc)
nqc.draw(output='mpl')
This change is a part of the advocate project done under @nbronn.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

18 of 21 (85.71%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.007%) to 82.76%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/transpiler/passes/optimization/optimize_1q_gates.py
18
21
85.71%

Totals

Change from base Build<PHONE_NUMBER>:
0.007%

Covered Lines:
50180

Relevant Lines:
60633

💛  - Coveralls

Thanks @kdk for your feedback, I've made changes.

Closing this as the fork this PR was created from has been deleted so this PR is now effectively read only and we can't make modifications to the PR code anymore. This has been reopened from a new fork by the author at #7579 and we'll continue the review in that PR.


Appstudio update test-component-pac-hxmo

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-hxmo-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
11 seconds
init

✅ Succeeded
28 seconds
clone-repository

✅ Succeeded
2 minutes
build-container

✅ Succeeded
43 seconds
sanity-inspect-image

✅ Succeeded
42 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
34 seconds
sbom-json-check

✅ Succeeded
23 seconds
sanity-optional-label-check

✅ Succeeded
23 seconds
sanity-label-check

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-hxmo-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
11 seconds
init

✅ Succeeded
28 seconds
clone-repository

✅ Succeeded
2 minutes
build-container

✅ Succeeded
43 seconds
sanity-inspect-image

✅ Succeeded
42 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
34 seconds
sbom-json-check

✅ Succeeded
23 seconds
sanity-label-check

✅ Succeeded
23 seconds
sanity-optional-label-check

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-hxmo-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
11 seconds
init

✅ Succeeded
28 seconds
clone-repository

✅ Succeeded
2 minutes
build-container

✅ Succeeded
42 seconds
deprecated-base-image-check

✅ Succeeded
43 seconds
sanity-inspect-image

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
34 seconds
sbom-json-check

✅ Succeeded
23 seconds
sanity-optional-label-check

✅ Succeeded
23 seconds
sanity-label-check

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-hxmo-on-pull-request has failed.

StatusDurationName

✅ Succeeded
20 seconds
init

🏃 Running
---
clone-repository

---
---
build-container

Pipelines as Code CI/test-component-pac-hxmo-on-pull-request has failed.

StatusDurationName

✅ Succeeded
20 seconds
init

🏃 Running
---
clone-repository

---
---
build-container

Pipelines as Code CI/test-component-pac-hxmo-on-pull-request has failed.

StatusDurationName

✅ Succeeded
20 seconds
init

✅ Succeeded
19 seconds
clone-repository

🏃 Running
---
build-container

Pipelines as Code CI/test-component-pac-hxmo-on-pull-request has failed.

StatusDurationName

✅ Succeeded
20 seconds
init

✅ Succeeded
19 seconds
clone-repository

🏃 Running
---
build-container


DrupalVM does not download a base Ubuntu box.

I suspect that this is because I have Parallels installed on the machine. But I can't find a way around it. It's parallels 12 which doesn't support Parallels provider.

Normally the provider is specified at the top of config.yml.
It'd be helpful to know if yours matches up with what's below.
# `vagrant_box` can also be set to geerlingguy/centos6, geerlingguy/centos7,
# geerlingguy/ubuntu1404, geerlingguy/ubuntu1204, parallels/ubuntu-14.04, etc.
vagrant_box: geerlingguy/ubuntu1604
vagrant_user: vagrant
vagrant_synced_folder_default_type: nfs

Beyond this, I cannot be of help - not being familiar with Parallels.

@cdesautels - I don't have Parallels so can't offer any support there—older versions seemed to work fine with Vagrant, but if Vagrant doesn't integrate with Parallels 12 yet, then there's nothing I can do to help.

Parallels 12 should work but now only Pro and Business editions of Parallels Desktop for Mac are compatible with the Vagrant Parallels Provider. - https://github.com/Parallels/vagrant-parallels#requirements