Allow VM assignment to tunnels

This allows the assignment of VMs to tunnels for both A and B side.
This fixes #15
Looks like this:

I have tested it manually, and it works.
However, I am having issues writing a testcase to test this.
I have my current try in this PR, but it does not pass with the following error:
django.core.exceptions.ValidationError: {'side_a_assigned_object_type': ['content type instance with id 38 does not exist.'], 'side_b_assigned_object_type': ['content type instance with id 121 does not exist.']}

I think it cant find the interface(s), but I am unsure why that would be the case.
Any idea what is going on?

I do not know why, but the django model validation continues to fail. It complains that the dcim.interface and virtualization.vminterface content types do not exist.
I am not sure if it looks for them in the plugin model or if its another issue.
But I dont think evaluating this specifically is that important, as the core models can generally be considered to exist.
So I have excluded that model field specifically from being validated.
The test case passes now. If this is not acceptable to you @robertlynch3  then I'll have to look more into why the validation fails, but right now, I do not know.

This looks great. Working on v3.5.9.


Child changing width resizes panels

Hi. Thanks for the library.
I'm trying to work out if this is intended behaviour or not (given everything works with percentages).
I have a horizontal group where one of the panels (right) has content with varying widths. When the content width changes it causes the panels to resize. This results in:

The whole panel group grows in size, sometimes extending outside of the page
The left and right panels both change size causing the resize divider to move

This is a test component I've been using which triggers the behaviour.
export function RandomWidthPanel() {
  const [state, setState] = useState(1000);

  return (

      <Button onClick={() => setState(Math.round(Math.random() * 2000 + 500))}>
        Click me
      </Button>

  );
}

Is it a bug? Or is there a way for me to restrict the width of the children dynamically when the panels are resized?

Your panel's content should not be larger than the panel itself. If it is, that would break the layout in the way you're describing.

Or is there a way for me to restrict the width of the children dynamically when the panels are resized?

I would suggest you use CSS (max-width: 100% or something similar– without knowing more about your use case, it's hard to say).

Closing this because it's been answered but if you have a follow up, you can ask.

Setting a max-width on the children still didn't fix it, the children were controlling the width of the parent, so max-width just grew to the size of the content.
I spent the last hour banging my head against the wall until I found this article. After setting width: 0 on the pane, it works perfectly.


✨  OG and Twitter data per post feature

no issue

adds facebook and twitter card data to PSM

Changes Unknown when pulling 4a6a9f8e59d952dbf50668b42df0b9333e074e46 on AileenCGN:feature/post-meta-data into ** on TryGhost:master**.

Changes Unknown when pulling fee923e47b6f390289b048acd215921437d944e0 on AileenCGN:feature/post-meta-data into ** on TryGhost:master**.

Changes Unknown when pulling 268e3edcc8ba730987647a64f6db4cbc8c02d4ee on AileenCGN:feature/post-meta-data into ** on TryGhost:master**.

Changes Unknown when pulling 90da8652a9f45ae1da2471293b12ff093005ef51 on AileenCGN:feature/post-meta-data into ** on TryGhost:master**.

Changes Unknown when pulling 94e2198fbc297969c64d05c627b681cec7e81ed5 on AileenCGN:feature/post-meta-data into ** on TryGhost:master**.

Changes Unknown when pulling eadd064099dd1eb2a1adcf5e72fb187e2067d353 on AileenCGN:feature/post-meta-data into ** on TryGhost:master**.

Changes Unknown when pulling 534307ed0bb04831ab33f26a89152567882b1f23 on AileenCGN:feature/post-meta-data into ** on TryGhost:master**.

Coverage increased (+0.1%) to 73.391% when pulling b04a3f00a7662016269c6de9ed1bc613220816e9 on AileenCGN:feature/post-meta-data into 15324eac55ec04c8ffd56a3c387ad3660c4c3bb3 on TryGhost:master.


Add "Free Play" button to Main Menu

In this task, the "play different map" buttons should be removed and replaced with the "Free Play" button. When pressing the free play button, the player will be taken to the map selection screen widget.

I spent about 30 minutes setting up the "Free Play" button so the user can navigate to the level selection screen. I created a new level that houses the level selection widget. I also linked the "Main Menu" button back to the main menu level.


Build fails after upgrading gradle to 7.3.3

Since gradle 7.3.3 does not support using insecure repositories, I have moved one of the maven repositories from insecure one to secure one in my android gradle project.
Basically from
insecure - maven ("http://developer.huawei.com/repo/") to
secure - maven ("https://developer.huawei.com/repo/")
The build works fine on local mac machine. But on remote jenkins machine hosted on AWS EC2, we are facing an issue while building the app. The error is
2022-07-14T12:35:46.416+0000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]                > Certificate for <developer.huawei.com> doesn't match any of the subject alternative names: [a248.e.akamai.net, *.akamaihd-staging.net, *.akamaihd.net, *.akamaized-staging.net, *.akamaized.net]

Before, I was using gradle 6.5 and insecure repository which worked fine without any issues.

I'm afraid that we can't do much here as this is an issue with certificates within your organization.
FYI you can use insecure repositories by calling allowInsecureProtocol.


how to output multi results

as title, I want to choose the best result from multi results, but docplex only output a result, how to output multi results.

If you want to collect all the solutions, you should look at callbacks.
Here is an example which shows how those callbacks work in docplex: https://github.com/PhilippeCouronne/docplex_contribs/blob/master/docplex_contribs/src/cut_callback.py
and the doc: http://ibmdecisionoptimization.github.io/docplex-doc/mp/docplex.mp.callbacks.cb_mixin.html#docplex.mp.callbacks.cb_mixin.ModelCallbackMixin


Find a way to integrate with request/current thread locale

Assuming this api will be used in back-end web services, integrate with request locale in http headers.
In other occasions(if any), such as Windows Desktop apps, integrate with locale of current thread..

Integrating with the system language is very nice opinion.
I will add this issue to roadmap.
Thanks a lot.


[BUG] fix bug in verbose mode in CNN TSC models

minor typo in cnn model (fix verbose mode)

Thanks for your contribution!
this PR is failing linting/code formatting tests, can you kindly check?

Sorry, I added further commits to the PR branch.
Now I removed them so no errors should occur.


An option to auto-paste in the buffer the plugin was invoked from

Rather than having to type "" then picking the register, then typing "*p or "*P to paste after or before the current buffer position, allow one or more mappings which instead perform the paste action once the register has been picked.
I'd ideally like to be able to map something like this:
nnoremap <Leader>P <Plug>PeekupPasteBefore
nnoremap <Leader>p <Plug>PeekupPasteAfter
nnoremap "" <Plug>PeekupPaste

... and have the plug-in auto-paste before/after if a register was picked (and for nothing to happen if no registers were picked/if the window was closed/if an invalid key was pressed)
... but I could settle for a way to have a (given as parameter) command executed on the buffer the plugin was called from once a register has been successfully picked and the contents of the * register replaced with the contents of the picked register
nnoremap <Leader>P <Plug>PeekupPaste('"*P')
nnoremap <Leader>p <Plug>PeekupPaste('"*p')

I've tried to develop this myself but my knowledge of lua is a bit rusty and my knowledge of the neovim API almost nonexistent.
If you've pointers as to how I could find out:

how to find out which buffer/window/"thing" the plugin's window has been opened from
how to "hook" on when the plugin's window has been closed, with a successfully picked register

... then I might attempt this, and in that case I'll open a pull-request.

This is definitely worth looking into. Without having had much thought on it, one way the following could be done

how to find out which buffer/window/"thing" the plugin's window has been opened from

can be:

either to save the current buffer_id before opening the peekup window (with bufnr("%")) and then put the content back into vim.api.nvim_buf_set_lines(<original buffer>, 0, -1, true, content)
after the peekup window closes the "current buffer" defaults back to what the "previous buffer" was (need to check on this) so one could probably just put into the cursor position

how to "hook" on when the plugin's window has been closed, with a successfully picked register

could you please specify what the desired behaviour should be, here? Would you like the register window to still be available (some sort of buffer hidden or the like)?

could you please specify what the desired behaviour should be, here?

Overall, I would like to have a mapping which automatically pastes the register name I pick. I'd "obviously" need to choose whether I want to paste before or after, but that's about it.

I'm in a buffer
I press a key combination to "pick and paste" above, or "pick and paste" after
the plugin's buffer opens and I have the option of selecting a buffer
if I pick a valid register, the register's contents get pasted before or after the position of the cursor on the buffer I invoked the plugin from
if I don't / if I close the plugin buffer, nothing gets pasted in the buffer I opened the plugin from

To do the above I'd need to get a reference to the buffer the plugin was invoked from, to know on which buffer I should then choose to paste inside of. bufnr("%") gets me that. Great, I'll keep that in mind.
Next, I would need to know whether the plugin window selected a buffer. This is currently "kind of" done via on_keystroke, but that also does something else. Currently, a byproduct of having selected a buffer is that the contents of the * registers have chanced since the plugin was invoked.
Next, I would need to know when the plug-in window was closed. The floating_window adds a <buffer>-local BufWipeout autocommand to wipeout the buffer. I'd likely want to hook there, or "around that point" so I can then perform the logic for something like: "if the user has selected a buffer, paste (before/after) the selected register's contents into that buffer".

after the peekup window closes the "current buffer" defaults back to what the "previous buffer" was

Yes, that happens, but I cannot seem to find how to perform an action then, rather than - say - on the plugin's buffer's "close" action. All I can seem to be able to hook on is "around" the plugin buffer.
With the above changes, the plugin effectively becomes a "pickable register contents paster", which I've so sorely missed :^)

I see now, it definitely makes sense. I need to give it some thoughts as it seems to be a little more complicated.

Next, I would need to know whether the plugin window selected a buffer. This is currently "kind of" done via on_keystroke, but that also does something else. Currently, a byproduct of having selected a buffer is that the contents of the * registers have chanced since the plugin was invoked.

do you mean "register" here instead of "buffer"? The plugin window selects a register, not a buffer.

Yes, that happens, but I cannot seem to find how to perform an action then

wouldn't this be just putting into the now-current buffer (usually referred to as 0) after this line (perhaps I am wrong here, I have not checked if it actually works)?

do you mean "register" here instead of "buffer"?
Yes, sorry!

My lua might be icky, and I've most definitely screwed up the indenting in the source files, but I think https://github.com/mfontani/nvim-peekup/tree/autopaste has it all?
"just" one commit - https://github.com/mfontani/nvim-peekup/commit/2f06faaa768a12bf8971af62c8897fdf9220f56f
With that, all one needs is to:
    nnoremap <Plug>PeekupOpenThenPasteAfter  :lua require('nvim-peekup').peekup_open("p")<CR>
    nnoremap <Plug>PeekupOpenThenPasteBefore :lua require('nvim-peekup').peekup_open("P")<CR>

.. and then in their own config:
    nmap <Leader>P <Plug>PeekupOpenThenPasteBefore
    nmap <Leader>p <Plug>PeekupOpenThenPasteAfter

... after which one can:

use "" to trigger the usual behaviour the plugin does
hit <Leader>P or <Leader>p to paste the contents of the selected register before/after the cursor in the buffer from which they invoked the plugin from.

What's missing is ensuring the picked register is proper...

I have had a look at your branch: I have a few suggestions

there is no need to carry over the buffer nr variable. I could obtain the desired behaviour (namely pasting before/after cursor position) simply doing vim.cmd('execute "normal! \\"'..key..paste_where..'"') here. Unless you feel the need for some other special cases I would say we can get rid of it altogether. This should answer your question of

What's missing is ensuring the picked register is proper...

I am not sure one must remove the vim.cmd('let<EMAIL_ADDRESS>if not paste_where: at the end of the day it does not hurt, and if the user wants to use another register we have already dealt with it here.
I have noticed that with this change the standard "" is incredibly slow in opening up. I really do not know what is causing it: <leader>pand <leader>P open the window at the speed of light (as before): is this happening to you too (or perhaps it is some hidden recursive remapping I have set up somewhere on my machine)?

I have noticed that with this change the standard "" is incredibly slow in opening up.

I've not experienced that. Could you try the branch in the just-opened issue? It's simpler, works (at least for me) and doesn't pass around a buffer number anymore.

This issue was implemented and merged in https://github.com/gennaro-tedesco/nvim-peekup/pull/14


Default values not working for integer types?

I have generateDefaultValues = true which is working fine for complex types/enums etc. but for plain integers like:
someparam:
  type: integer
  default: 4

No default value is generated?

The same problem for long data type:
C#:
[Required]
public long Id { get; set; } = 0;

TS (no default value):
id!: number;
How can I solve this problem?


Error message when parsing files and mandatory fields are missing.

Using the tools.spdx.dev and feeding in file:

SPDXVersion: SPDX-2.2
DataLicense: CC0-1.0
SPDXID: SPDXRef-DOCUMENT-SAGPM
DocumentName: Software Assurance Guardian Point Man (SAG-PM)
DocumentNamespace: http://softwareassuranceguardian.com/
Creator: Person: Dick Brooks<EMAIL_ADDRESS>Creator: Tool: PyInstaller 3.6
Created: 2020-09-08T19:44:17Z
Package: SAG-PM
PackageName:aiodns
SPDXID: SPDXRef-aiodns-2.0.0
PackageSupplier: Person:Saúl Ibarra Corretgé
PackageVersion: 2.0.0
PackageChecksum: SHA-256: aaa5ac584f40fe778013df0aa6544bf157799bd3f608364b451840ed2c8688de
PackageDownloadLocation<EMAIL_ADDRESS>FilesAnalyzed: false
PackageName:altgraph
SPDXID: SPDXRef-altgraph-0.17
PackageSupplier: Person:Ronald Oussoren
PackageVersion: 0.17
PackageChecksum: SHA-256: c623e5f3408ca61d4016f23a681b9adb100802ca3e3da5e718915a9e4052cebe
PackageLicenseConcluded: MIT
PackageDownloadLocation<EMAIL_ADDRESS>FilesAnalyzed: false

The error message, “Only one PackageName allowed, extra at line: 21”  is confusing and misleading.
as I think the problem is missing mandatory fields.   But please confirm if this is indeed the case.

I'm not able to reproduce the same error.
When I run validate using the above file text, I get an invalid document error due to the SPDX Document Ref.
The SPDXID: SPDXRef-DOCUMENT-SAGPM needs to be replaced with SPDXID: SPDXRef-DOCUMENT per the spec.
When I fix that, I get a different error:

Looking at the document, line 10 contains Package: SAG-PM which is not a valid keyword.
When I remove the invalid package, I get the following error:
Analysis exception processing SPDX file: Invalid checksum algorithm: SHA-256: aaa5ac584f40fe778013df0aa6544bf157799bd3f608364b451840ed2c8688de at line number 14
SHA-256 needs to be replaced with SHA256.
Fixing this, I get the error Analysis exception processing SPDX file: Invalid download location pattern<EMAIL_ADDRESS> Must match the pattern ^(NONE|NOASSERTION|(((git|hg|svn|bzr)\+)?(http:\/\/www\.|https:\/\/www\.|http:\/\/|https:\/\/|ssh:\/\/|git:\/\/|svn:\/\/|sftp:\/\/|ftp:\/\/)?[a-z0-9]+([\-\.]{1}[a-z0-9]+)*\.[a-z]{2,5}(:[0-9]{1,5})?(\/.*))|(git\+git@[a-zA-Z0-9\.]+:[a-zA-Z0-9]+)|(bzr\+lp:[a-zA-Z0-9\.]+))$
Removing the download location, I got the following message:
This SPDX Document is not valid due to:
	Package at line 17 invalid: Missing required copyright text for altgraph in altgraph
	Package at line 17 invalid: Missing required download location for package altgraph
	Package at line 17 invalid: Missing required declared license for package altgraph
	Package at line 10 invalid: Missing required concluded license for aiodns in aiodns
	Package at line 10 invalid: Missing required copyright text for aiodns in aiodns
	Package at line 10 invalid: Missing required download location for package aiodns
	Package at line 10 invalid: Missing required declared license for package aiodns

BTW - I did find a separate issue parsing external Ref's while investigating this, issue #3

Thanks, Gary. I'll tackle these issues. Is there an online, web spdx verifier I can use to check for errors?

@rjb4standards Yes - https://tools.spdx.org/app/validate/
I thought that was the origin of these errors.
Are you using the command line tool at https://github.com/spdx/tools?
If so, you can try a more up to date command line tool at https://github.com/spdx/tools-java

@rjb4standards Were these error found using the Python parser?  If so, you can ignore all my comments above on the error handling and I'll transfer this over to the Python tools repo.

Gary, yhe Python parser is reporting these errors, but the online validator, my new best friend, reports no errors.
PackageName:spdx-tools
SPDXID: SPDXRef-spdx-tools-0.6.1
PackageSupplier: Person:Ahmed H. Ismail
PackageVersion: 0.6.1
PackageChecksum: SHA256: 45fa09d43534772ca63bff2dccf1fbde88e1fc9b9515fc7a34ae50540d7ad29c

Moving this issue to the Python tools repo


hquantlib <IP_ADDRESS> / HerbiePlugin

base-<IP_ADDRESS> is out of bounds for:

[ ] HerbiePlugin-<IP_ADDRESS> (==4.8.*). No maintainer. @mikeizbicki

Ping @paulrzcz.
The latest hquantlib pulls in HerbiePlugin as a dependency, which does not allow GHC 8. Neither does subhask, one of HerbiePlugin's dependencies. subhask also has frozen dependencies (https://hackage.haskell.org/package/subhask) which doesn't play well with stackage, better to use version ranges and have stackage take care of freezing dependencies.
To solve this you can update the dependencies or stop using them.

The bounds for HerbiePlugin are correct and cannot be changed.  HerbiePlugin cannot use GHC 8.0 because the interface for GHC plugins changed between 7.10 and 8.0.  Updating HerbiePlugin to use GHC 8.0 would be a relatively straightforward task, but it's not something I have time for at the moment.  I'd gladly accept a pull request though :)

Ok. I will exclude HerbiePlugin for now from hquantlib's dependencies and try to find time to fix the plugin for GHC 8.0.


Detect use of unsafe language features

Via static analysis where possible.
e.g.

JNDI
Unsafe code in memory safe languages

Depends on #519


Dynamic Cluster: even with correctly formatted and filled out certificates, TLS/SSL blade prevents cluster formation

Using Dynamic Cluster offer version 1.0.32 2021-03-05 13:52 EST
https://ms.portal.azure.com/#create/oracle.20210202-test-01-previewarm-oraclelinux-wls-dynamic-cluster
With the following options filled out
Basics

Nothing special

TLS/SSL
keytool -genkey -keyalg RSA -alias servercert -keystore keyStoreIdentity.jks -storepass Gumby12340987 -validity 360 -keysize 2048 -keypass Gumby12340987 -storetype jks

keytool -genkey -keyalg RSA -alias servercert -keystore keyStoreTrust.jks -storepass Gumby12340987 -validity 360 -keysize 2048 -keypass Gumby12340987 -storetype jks

OHS

Upload existing key stores

keytool -genkey -keyalg RSA -alias servercert -keystore keyStoreOhs.jks -storepass Gumby12340987 -validity 360 -keysize 2048 -keypass Gumby12340987 -storetype jks

DNS -> Create+Review

No

Deploying the cluster in this way causes the managed servers to not run.

Hi Ed @edburns,
I tested using the keystore commands provided in the issue. Though the deployment went through, the SSL setup is not working as expected due to wrong trust.jks file being used.
Below are the correct keystore commands that needs to be used to create the identity.jks and trust.jks files.
Create identity.jks File:
keytool -genkey -alias servercert -keyalg RSA -keysize 2048 -sigalg SHA256withRSA -validity 365 -keystore identity.jks -keypass Gumby12340987 -storepass Gumby12340987
Export identity.jks File and generate root cert file:
keytool -export -alias servercert -noprompt -file root.cert -keystore identity.jks -storepass Gumby12340987
Import root.cert and create trust.jks file
keytool -import -alias servercert -noprompt -file root.cert -keystore trust.jks -storepass Gumby12340987

The identity and trust keystore files are related to each other and we cannot use independently created keystores and use it as identity and trust keystores.
I am working on including few validations in the script to check if the provided files is a valid keystore file.
I will also try to find out if there is a way to validate, if the identity and trust keystores provided are related.

The following commands can be used to validate the identity & trust.jks keystore files:
Validate Identity Keystore
keytool -list -v -keystore identity.jks -storepass Gumby12340987 -storetype JKS |grep "Entry type:"|grep 'PrivateKeyEntry'
Returns 0 on successful validation and 1 on validation failure
Validate Trust Keystore
keytool -list -v -keystore trust.jks -storepass Gumby12340987 -storetype JKS |grep "Entry type:"|grep 'trustedCertEntry'
Returns 0 on successful validation and 1 on validation failure
These validations will be added to the SSL Configuration logic in Domain Setup scripts for all the three offers.

Implemented validation for SSL Keystores during deployment and add node features.
Created pull requests for all the three offers.
https://github.com/wls-eng/arm-oraclelinux-wls-admin/pull/96
https://github.com/wls-eng/arm-oraclelinux-wls-cluster/pull/136
https://github.com/wls-eng/arm-oraclelinux-wls-dynamic-cluster/pull/123


DELETE requests to deletef and forwardf routing to a controller fail with 404 not found

Possibly related to issue #54
Using the latest from Saturn master branch as of 12/20/2018 at 10:00 MDT.
Using Controller.Sample I added a deletef route to topRouter and added a new deleteRoute router.  The route pattern is /delete/%i.
This is the URL I put in PostMan to make the DELETE request: http://localhost:8085/delete/1111
You can see the source code for this in my forked repo here: https://github.com/MarneeDear/Saturn/blob/delete-routes-404/sample/Controller.Sample/Controller.Sample.fs#L105
Delete requests to this route fail with 404 when the route sends directly to a controller
   deletef "/delete/%i" (fun (_ : int) -> userController)

Requests directly to a function are OK.
let apiDeleteExample2 id = sprintf "Echo: %i" id |> text

//inside topRouter
    deletef "/delete/%s" apiDeleteExample2

I'm using dotnet on Windows 10.
When I run Controller.Sample I do dotnet watch run.
UPDATE
I think this happens when the id passed to the controller is not a string.
This doesnt work (id is type int)

//In userController
    delete (fun ctx id -> (sprintf "Delete handler no version failed - %i" id) |> Controller.text ctx)

//In topRouter
    deletef "/delete/%i" (fun (_:int) -> userController)

This works (id is type string)
//In userController
    delete (fun ctx id -> (sprintf "Delete handler no version failed - %s" id) |> Controller.text ctx)

//In topRouter
   deletef "/delete/%s" (fun (_:string) -> userController)

forwardf instead of getf seems to work, but I am having problems with pointing it to another router. I'm going to write a new issue.

Made the comment on the wrong issue.

I suspect I will need to use forwardf. I am trying that out.

DELETE to a forwardf to a controller are 404.
These both 404.
    deletef "/delete/%i" (fun (_:int) -> userController)
    forwardf "/delete/%i" (fun (_ : int) -> userController)

See full source code here.
https://github.com/MarneeDear/Saturn/blob/delete-routes-404/sample/Controller.Sample/Controller.Sample.fs#L112

I just looked at what the code is doing, and its not wrong. However it's not obvious how it all works either. To understand you need to know a few important points to grasp why all your examples do what they do.

Saturn uses Giraffe subrouting under the hood, only for forward and forwardf calls as mention with jargon in their method details.
Forwards calls to different scope. Modifies the HttpRequest.Path to allow subrouting.
When you use forward/forwardf, they consume their matched route segment so to say, allowing the next handler to start matching at the subsequent segment. This is how subController works as well.

If you use any consuming 'formatting' (so forwardf and subController) route handler, always use the passed-in argument. This is the only time you'll get that route argument. So every example that does something like:
deletef "/delete/%i" (fun (_:int) -> userController)
will discard the %i and put the route pointer past that segment. So by the time the userController matches its action routes they all start their matches AFTER /delete/%i.
So that means in this case when you would call it with delete/11/1 you would get 1 as the id in your controller actions. For delete/11 it correctly 404s if you don't have an index/post/deleteall action.

Now you also see, when you don't use a consuming route handler as delete/deletef and related friends are, every subsequent handler will start their match at the same point in path again.
In your samples you write out id as %s in your sprintf handler. Through F#s type inference that will set the controller's 'Key type as string. The result is that the string route basically matches anything of path, returning to you delete/11 as the id.
This last part feels like a bug though, and is something I need to think about, it seems incorrect that a 'Key = string controller would just always match the full remaining path, intuitively I would expect it would return delete as the id instead, stopping at the first unencoded '/'. What do you think @Krzysztof-Cieslak?
Hope this helps!

Fix for weird matching behavior of %s controllers is pushed, see https://github.com/SaturnFramework/Saturn/pull/168

Hey, @NinoFloris thanks for the detailed response!
@MarneeDear, I'll close this issue - as Nino mentioned above, most of the behaviour is expected, and the %s bug was fixed by #168 and will be available in next Saturn release. Please let us know if we can help more with the problems - we probably need to clarify some documentation around (sub)routing.


Using only C-u and C-v does not reduce memory consumption

Dear Feihu,
I can imagine how busy you might be. Still if you give some insights I will be very thankful.
In another issue I asked about memory consumption and you mentioned that the 4D cost volume of RAFT is also looked up over the (refinement) iterations, therefore this released implementation of SeparableFlow uses more memory compared to RAFT.
I changed the code in such a way that the 4D cost volume is not looked up during the refinement iterations and based on the paper, it is only used as a base to compute C-u and C-v. That changed the memory consumption only negligibly.
You mentioned in the paper that the 4D cost volume does not have to be stored. But we need it for back propagation. Could you elaborate on how not to store it and how you achieved much reduction in the memory consumption in the original SeparableFlow?
Thanks for your support.
Azin

I am also confused about the mentioned " Note that Cu can be computed without storing the intermediate 4D cost volume C" in Sec.3.2.1. How to perform back propagation if you release the GPU memory of 4D cost volume C?


Create select.js

Branch 56 created, code developed, committed and pushed upstream. Awaiting release 0.5.

Merged into master, closing

Updated to fix
PCyl: select junk
NO SELECTIONS ARE AVAILABLE FOR PRESSURE

Should be
PCyl: select junk
NO SELECTIONS ARE AVAILABLE FOR JUNK

R-merged into master.


Not generating routes for Blueprints

It is not generating routes for blueprints at all.

Check #2, and make sure your sails config blueprint rest is true. As swagger.json on editor.swagger.io would show you all default blueprints.
Or if not answered, you can further explain, Thanks.

I tried changing rest: false but still blueprint routes are coming.How can I disable all blueprint api's ?
Even If I add my swagger object in config/routes.js it is not overriding blueprint request params.

https://github.com/theo4u/sails-hook-swagger-generator/blob/12ffb0f83bf24173b337d7a32edd64deb4fce0d3/test/generators.test.js#L253


 allow multiline label or word wrap it

PYPE-750 created by jakub.trllo

Solved with https://github.com/pypeclub/pyblish-lite/pull/52


Dev

Related to the last discussion regarding ant. Ant variables implemented by chef.

Thanks Liora. We need to figure out if a generalized solution would be more apropos.


fix exception on reload

with the content of kcptun-traffic-statistics.json as "null", null value of this._trafficStatistics can cause exceptions.

Merged. Thanks!


Swagger-Ui not showing any controller even though api-docs are there

I'm trying to make a single REST controller integrated with Springfox using only Java Based configuration.
The json is being generated correctly so Swagger UI should display the doc as well, but this is not happening, the UI is shown as well but with no documentation in it.
I'm using Springfox 2.5.0
Here are the main parts of the configuration:
Swagger Configuration
@EnableSwagger2
 public class ConfigSwagger {

    @Bean
    public Docket api() {
        return new Docket(DocumentationType.SWAGGER_2)
                .apiInfo(apiInfo())
                .select()
                .apis(RequestHandlerSelectors.any())
                .paths(PathSelectors.any())
                .build();
    }

    private ApiInfo apiInfo() {
        return new ApiInfoBuilder()
                .title("Información")
                .build();
    }

}

MVC configuration
@EnableWebMvc
@Configuration
@Import(ConfigSwagger.class)
@ComponentScan(basePackages = {"confbase"})
public class MvcConfig extends WebMvcConfigurerAdapter{

    @Override
    public void addResourceHandlers(ResourceHandlerRegistry registry) {
        registry.addResourceHandler("/resources/**").addResourceLocations("/resources/");
        registry.addResourceHandler("swagger-ui.html")
                .addResourceLocations("classpath:/META-INF/resources/");
        registry.addResourceHandler("/webjars/**")
                .addResourceLocations("classpath:/META-INF/resources/webjars/");
    }
    @Override
    public void configureDefaultServletHandling(DefaultServletHandlerConfigurer configurer) {
        configurer.enable();
    }
}

WebAppInitializer
@Configuration
public class WebAppInitializer extends AbstractAnnotationConfigDispatcherServletInitializer {

    @Override
    protected Class<?>[] getRootConfigClasses() {
        return new Class[] { MvcConfig.class, ConfigSwagger.class };
    }

    @Override
    protected Class<?>[] getServletConfigClasses() {
        return null;
    }

    @Override
    protected String[] getServletMappings() {
        return new String[] { "/api/*" };
    }

}

The Controller
@Controller
@RestController
public class AController {
    @RequestMapping(method = RequestMethod.GET, value = "/string")
    public String getString() {
        return "String";
    }
}

They're all in the same package.
I don't know what the problem could be.
Thanks in advanced for any help you could give!

Would you mind trying with 2.6.1?
Also since your servlet is looking for apis at /api/* you might have to play around with your configuration a bit. Try changing that to / and work yourself up to /api

Thanks DIlip.
Tried changing the mapping to /, that way the api-docs  don't get generated, I tried that solution with both versions 2.6.1 and 2.5.0 but doesn't seem to be any difference

Hi, @jvirriel
Are you perhaps using spring boot?

Hi @codeMmaster
No,  i'm using JBoss as server

@jvirriel What do you see when you navigate to

/api/v2/api-docs and
/v2/api-docs

I also faced similar issue with swagger version 2.7.0. This got resolved by using 2.6.1 swagger version

it worth to check pom.xml for presence of

io.springfox
springfox-swagger-ui
2.....

any updates here?
Im getting:
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.
Sun Apr 07 14:02:25 EDT 2019
There was an unexpected error (type=Not Found, status=404).
No message available

I'm facing the same issue. Even though I have added the swagger-ui but I can't still figure out why the ui is getting 404.

Sent from my iRotary phone
On Mar 28, 2020, at 4:48 PM, syeddanishzakir8080<EMAIL_ADDRESS>wrote:

I'm facing the same issue. Even though I have added the swagger-ui but I can't still figure out why the ui is getting 404.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/springfox/springfox/issues/1688#issuecomment-605517649, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACO7FDMCIR2DLOSNNTS7ODLRJZO75ANCNFSM4DBEJ2YQ.


Template Updates 27 Jun 2023

Updated event Templates for Origin alpha Trials

I added myself based on offline sync with Kate. Please let me know if you need more time working on it before a review

The PR doesn't build. Can you please have a look at the "Build and test / Build and test (pull_request) " check and fix the errors.

Hi @mariolamassaavedra , thanks for the PR.
For the Alpha pilots, I'd suggest to align event template protos with media types that we currently have in the UK Measurement Policy draft.
Namely I'd suggest the following structure:
common_template
- No fields

display_event_template
- Viewability

video_event_template
- Viewability
- DigitalVideoCompletionStatus

other_media_event_template
- No fields

This would allow to define explicitly in the event group schema what media types following event group would report.
Let me know what do you think.

One last update from my side. We need to slightly amend the VIEWABLE_0_PERCENT_PLUS option.
  // More than 0% of the ad was displayed in the browser for more
  // than 0 seconds.
  0_PERCENT_PLUS = 1;

Hi @mariolamassaavedra , thanks for the PR.
For the Alpha pilots, I'd suggest to align event template protos with media types that we currently have in the UK Measurement Policy draft.
Namely I'd suggest the following structure:
common_template
- No fields

display_event_template
- Viewability

video_event_template
- Viewability
- DigitalVideoCompletionStatus

other_media_event_template
- No fields

This would allow to define explicitly in the event group schema what media types following event group would report.
Let me know what do you think.

@zasadnyy - This may be worth revisiting when we upgrade to the V2 Reporting Server. But, the reason for having a common template was to enable us to set a common filter on a ReportingSet which contains multiple EventGroups with different media types (i.e. common_template.viewability == "VIEWABLE_100_PER_CENT"). In the V1 Reporting Server, without this common template we would be forced to set individual filters per EventGroup (i.e. video_template.viewability == "VIEWABLE_100_PER_CENT" for video EventGroups, and display_template.viewability == "VIEWABLE_100_PER_CENT" for display EventGroups) which would then need to be set in the EventGroupUniverse to handle this case.

@khisba thanks for the context on the intentions for this design. I agree that suggested approach would make sense if we have only Display and Video media types but we have more.
Please consider that events falling into "other media" category do not have definition of the viewability. Therefore, viewability in the common template won't make sense for this media type.
Another benefit that I see from moving viewability into Display and Video templates - we'll be able to have separate enums for each type. This would allow us to clearly name viewability enums for Display and Video, eg VIEWABLE_50_PER_CENT_PLUS_1_SECOND and VIEWABLE_50_PER_CENT_PLUS_2_SECONDS

Reproducing this comment from the email thread:

If we're planning on changing the UK pilot event templates now, I recommend the following fixes as well:

Drop the redundant Template suffix from the message name and the _template suffix from the template name.

This also means renaming the fields in the Event message, since these must match the template names.

Drop the deprecated event_field annotation and use the new template_field annotation instead.

This implies reducing the layers of nesting. There should only be top-level fields in event templates using the new annotation.

Use appropriate types rather than uint32 for everything (e.g. bool or an enum type).

As a reminder, the uk-pilot-event-templates repo should be archived after the pilot.

I'd also recommend changing the protobuf package to something that would be globally unique. Maybe halo.uk.pilot with a corresponding Java package of org.halo_cmm.uk.pilot?

Looks good. Only thing is as @khisba mentioned, lets keep the file names consistent. Either with the _event suffix or without.
I vote to keep out the _event suffix

Sorry, I think there is a misunderstanding here. I hadn't realized you got rid of the wrapper Event message. We have to have that to disambiguate for fields in different templates. For example we have viewability in both DisplayEvent and VideoEvent. The edps wouldn't know which one to filter against. Here is the documentation : Name of the field in an event message that uses this template. Required. Immutable.
Here is I think the best way to define that wrapper message :
message Event {
  Display display = 1;
  Video video = 2;
  Other other = 3;
}

Note that I got rid of _event suffixes since they are not events but templates.


Enhancement: document environment variables

What version of Wrangler are you using?
2.1.4
What operating system are you using?
Mac
Describe the Bug
We apparently have six environment variables - let's document them

I will sync up with @lauragift21 on Monday and find out the best place to put all the Process Environment Variables, now they are co-located in the same file it will be easier to track.


RSpec/SubjectStub. Add top level group callback

It's a followup of https://github.com/rubocop-hq/rubocop-rspec/pull/925 and it addresses the following issue https://github.com/rubocop-hq/rubocop-rspec/pull/925#issuecomment-641151939
Changes:

added module TopLevelGroup (similar to TopLevelDescribe)
refactored SubjectStub to avoid manual caching and rely on TopLevelGroup

The goal of TopLevelGroup is to handle all the possible example and shared groups in a spec file. It calls on_top_level_group callback for every top-level describe, context, feature, shared context... group.

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[ ] Updated documentation.
[ ] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

@pirj Fixed all the issues

Merging without consensus, since this change has been discussed in the past, and only affects one cop.
Thank you again, @andrykonchin !


Aggressive retransmits / duping from different source port (dpi randomly drops / lags / hangs ssl client helo)

Describe your feature / Опишите ваше предложение
Hello,
In my country, we have a DPI that doesn't outright block stuff but instead makes the internet "unreliable". The DPI inspects SSL Client HELO, and randomly chooses such packets to then blackhole the connection. Alternatively, it may delay the response by many seconds (possible overload). When I change the sni I am using in my vpn program, it works ok for a few minutes then the shittification gets switched on.
The auto-ttl and fragmentation options help, but is there a way to have goodbyedpi aggressively send multiple copies of the same packet or find a way to beat such internet shittification ?
UDP bypasses this, but the DPI at random times of the day will throttle any unidentifiable udp traffic to 2 Mbps.
Protocols like QUIC are totally blocked (some versions of it).
If there's any suggestion of combination of settings to beat this or if there's any captures I can send privately to assist, let me know.

This is a reasonable proposal, I have an idea to implement packet stuffing, will do retransmissions as well.

@ValdikSS, thanks for keeping GoodbyeDPI developed.
Happy new 2024 year from Russia. Stay healthy, sane and safe.


Can't build due to undefined ciphers

I believe that the TLS ciphers being used are dependent on version of openSSL being used on the operating system. In my case, it appears that I don't have support for a number of the ciphers, so it won't build or run properly without them. I'm running OSX v10.12.4 (latest of Sierra). Others may have issue depending on their particular operating system and version of openSSL (if that's indeed the library that is being used by crypto/tls).

Here are the set of ciphers that finally allowed me to successfully build (from the tlscheck.go file):

Hi Aaron,
What is the Go version do you use? I'm using 1.8 on travis and my Debian Stretch.

go version go1.7.1 darwin/amd64 on OSX v10.12.4 (Sierra).
That might be why. I had heard of a number of issues with Go on this exact version of Sierra recently, that's why I didn't want to upgrade quite yet. Though they may be resolved now, I'll have to check.

Just checked, looked like 1.8.1 fixes these issues (https://github.com/golang/go/issues/19734#issuecomment-293221337). I'll upgrade and try again, then let you know on here. Going to have to head out for a bit right now though, so it may be a little bit later.

Just upgraded to go 1.8.1. Confirmed that this fixes it. This isn't on the main README yet, it might be a good idea to mention on the Build section that the build has been confirmed to work on the latest version of Go (1.8.1). This might also be something that you can have automated with Travis CI, but I don't know for sure.

https://github.com/yanc0/beeping#build
I've added the requirement on README.md
Thanks Aaron !

No problem! By the way, "#14" doesn't have a link attached to it. I understand that it means issue 14, but some may not. Maybe include a link to this issue directly?


Update CivSpy to 1.18 and use Gradle

I have no idea why I keep opening PRs against civclassic by accident...


June updates

Docs Build status updates of commit d5163c3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-nav/Converting-a-Database.md
:warning:Warning

Details

dynamics-nav/d365-sales-modifications-for-upgrade.md
:warning:Warning

Details

dynamics-nav/Demo-Option.md
:bulb:Suggestion

Details

dynamics-nav/Deployment.md
:bulb:Suggestion

Details

dynamics-nav/Designing-RDLC-Report-Layouts.md
:bulb:Suggestion

Details

dynamics-nav/Developer-Option.md
:bulb:Suggestion

Details

dynamics-nav/Report-Metadata-Virtual-Table.md
:bulb:Suggestion

Details

dynamics-nav/System-Requirements-for-Microsoft-Dynamics-NAV-2017.md
:bulb:Suggestion

Details

dynamics-nav/System-Requirements-for-Microsoft-Dynamics-NAV.md
:bulb:Suggestion

Details

dynamics-nav/Converting-a-Database.md

Line 2, Column 8: [Warning-duplicate-titles] Title 'Converting a Database - Technical Upgrade - Dynamics NAV' is duplicated in: 'Converting-a-Database.md(2,8), Converting-a-Database-2017.md(2,8), d365-sales-modifications-for-upgrade.md(2,8)'. Titles must be unique within a docset.
Line 13, Column 1: [Warning-duplicate-h1s] H1 'Converting a Database - Technical Upgrade' is duplicated with other articles: 'Converting-a-Database.md(13,1), Converting-a-Database-2017.md(14,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 55, Column 128: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/uninstall-navapp' will be broken in isolated environments. Replace with a relative link.
Line 194, Column 13: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/repair-navappSynchronize' will be broken in isolated environments. Replace with a relative link.

dynamics-nav/d365-sales-modifications-for-upgrade.md

Line 2, Column 8: [Warning-duplicate-titles] Title 'Converting a Database - Technical Upgrade - Dynamics NAV' is duplicated in: 'Converting-a-Database.md(2,8), Converting-a-Database-2017.md(2,8), d365-sales-modifications-for-upgrade.md(2,8)'. Titles must be unique within a docset.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

dynamics-nav/Demo-Option.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

dynamics-nav/Deployment.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

dynamics-nav/Designing-RDLC-Report-Layouts.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

dynamics-nav/Developer-Option.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

dynamics-nav/Report-Metadata-Virtual-Table.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

dynamics-nav/System-Requirements-for-Microsoft-Dynamics-NAV-2017.md

Line 29, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 46, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 60, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 73, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 81, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 91, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 104, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 115, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 126, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 137, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 145, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 156, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 165, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 173, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

dynamics-nav/System-Requirements-for-Microsoft-Dynamics-NAV.md

Line 29, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 46, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 59, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 72, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 80, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 91, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 103, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 113, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 124, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 136, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 144, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 155, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 164, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 172, Column 2: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Did you crop raw samples on the z axis?

Thank you for your work and sharing the code. But I have a question about data preprocessing.
The papersays that "we cropped the 3D samples according to the ground truth, with enlarged margins i.e. [10 ∼ 20, 10 ∼ 20, 5 ∼ 10] or [25, 25, 25] voxels on LA or PancreasCT, respectively", but your preprocessing code just cropped the samples on the x axis and y axis.
Why they are different? Which method is used to produce the performance reported in the paper, like 91.07 on LA and 79.37 on PancreasCT?

Hi Wang,
Thanks for your interest. You are right. I cropped the slices on Pancreas-CT only at the X and Y axes. The relevant description of the details should be a typo in the paper. I will modify that in the future version. This setting is similar to the DTC model for fair comparisons, see https://ojs.aaai.org/index.php/AAAI/article/view/17066.
Meanwhile, on the LA dataset, the pre-processing part https://github.com/ycwu1997/MC-Net/blob/main/MC-Net/code/dataloaders/la_heart_processing.py  is similar to the compared UA-MT, DTC models.
Note that, all experiments in this paper followed the same settings and used the same data inputs. If any issues, feel free to contact me. Thanks.
Yicheng


The "editor.selectionHighlightBackground" color should have different contrast with "editor.selectionBackground" color

By default, the editor.selectionHighlightBackground have the same color with editor.selectionBackground , it could be confused sometime:

In the screenshot I only selected the fourth a, but the background highlight is confusing.
The editor.selectionHighlightBackground color usually have lower contrast than the editor.selectionBackground
For example:
Default Dark+

Monokai

Monokai Dimmed

Thanks for your contribution :+1:
I'll analyze and reproduce this behavior and see if it should be changed.

I agree, it should have a different color to know what is being highlighted and what is being mirrored.

Hi @ooJerryLeeoo  :wave:, sorry for the long delay. I've been really busy with my job, real life and Nord's, finally launched, official website and documentation.
The problem you're describing is a really tricky one for theme designers since VS Code limits us to only use the theme keys they provide so it is hard to use different colors that match the overall theme style while supporting all the different states:

selected ➜ will highlight other occurrences in the same editor
selected, but no focus ➜ will highlight other occurrences in the same editor, but reduces opacity due to focus loss
highlighted as find result by the search widget

➜ allows also to be highlighted as selection and as other occurrence

You see there are a lot of states that you need to think of when choosing the colors and there are many themes out there that have the same problem like e.g. the large thread of sdras/night-owl-vscode-theme#90.
In my opinion the case you're describing here is a edge case since it is unusual to have the same words in the exact same indentation on multiple lines exactly with each other. I've tested several opacity settings and different colors and there's not really a case where it might end up in a nice way for all states.
The following screenshots show the current highlighting color with a opacity of 60%. It doesn't really make a large difference when multiple same words are highlighted like on your examples, but it significantly decreases the visual recognizability when words are distributed among a paragraph or within the current active cursor line.
Current highlighting
Significantly decreases visual recognizability with total opacity of 60%
Minimal improvement for edge case and in highly zoomed view
Proposed Solution
As you can see, it is unfortunately hard to find a good and well balanced solution for this problem, therefore I don't want to change the theme, but every user who does not like this highlighting can simply fix it using a theme-scoped workbench color customization:
"workbench.colorCustomizations": {
  "[Nord]": {
    // Colorize automatic occurrences highlights different than selections
    "editor.selectionHighlightBackground": "#434c5e99"
  }
}

Adding this snippet to your user settings and replace the #434c5e99 with any color you'd like. This will only apply to the Nord theme and will not affect any other themes.
Also if you want to disable the automatic highlighting of other word occurrences or code variables you can also add this to your settings:
// Disable automatic occurrences highlighting
"editor.occurrencesHighlight": false

I hope you can understand this solution and feel free to ask if there are any questions :smile:

What I did was add a green-ish color to the main highlight, which might break the theme a little but I prefer having a better idea of the selections:

I made this and other changes into a new theme which you can find here: https://marketplace.visualstudio.com/items?itemName=madprops.nordico


How to speed up the scrolling?

Thanks a lot for this package, it makes Emacs feel so much better and modern.
One question I had was if there is a way to configure something, so it scrolls a little faster?
When I scroll in other apps, the same amount of movement results in twice as much scrolling, whereas in Emacs with good-scroll it is scrolling only about half the rate, so I need to physically scroll more (or it seems scroll the same amount but faster) to get the same effect.
Thanks

Glad you like the package! You can set the good-scroll-step variable to change how much one scroll event scrolls, and you can change good-scroll-duration to edit the animation speed.

Thanks, I toyed with those, but nothing gave me exactly what I was looking. Then I thought, maybe it's because Emacs itself takes longer to register a scroll event. And if I try C-h k, I see that it takes me moving my fingers for longer distances on the trackpad before Emacs shows mouse-4. Where-as in Chrome for example, moving a smaller distance starts scrolling immediately.
Not sure there'd be a fix to this, seems Emacs just takes longer to register a scroll up/down from my trackpad.

Hmm, it probably depends on your OS and trackpad drivers.

Hello there! I am on macOS and feeling experience the same as @didibus. It takes longer swipes to "start scrolling".

@didibus Are you also using macOS?


Brazilian Portuguese translation added to l10n folder

Brazilian Portuguese translation
New files

l10n/pt_BR.js
l10n/pt_BR.json

This is running in our production server already.
I have revised the translation many times, but sorry if I still have missed something.
Note: Not sure how the plural stuff at the end of each file works. I didn't touch that.
Cheers!
Gus

It's great!
Can you create a pull request to develop branch?

Ok, it is there: https://github.com/ONLYOFFICE/onlyoffice-owncloud/pull/144
Had to git reset --hard upstream/develop because I the merging created some mess on commits.
It should be fine like this though (just adding the 2 files to your last commit on develop and without extra/repeated commits).
Cheers!
Gus

oh shit.. pushed the wrong branch..

Close as duplicate of https://github.com/ONLYOFFICE/onlyoffice-owncloud/pull/144


Gmail + Google Calendar Unable to login

Describe the bug
Whenever I try and login to a Gmail or Gcal, it redirects me to this page
To Reproduce
Steps to reproduce the behavior:

Add Gmail/Gcal as a service
Try logging into an account with a @gmail or business domain
See error

Screenshots

Desktop (please complete the following information):

macOS 10.15.3 Catalina
Franz Version 5.4.0-beta.3

I have the same problem with Gmail and Hangout...

You can override this issue by editing the index.js file in the recipe.
Change
module.exports = Franz => Franz;

To
module.exports = Franz => class useragent extends Franz { overrideUserAgent() { return "Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136"; } };

The recipe should be located at:
Mac: ~/Library/Application Support/Franz/recipes/
Windows: %appdata%/Franz/recipes/
Linux: ~/.config/Franz/recipes/

This is not working anymore for Linux (I'm on Ubuntu 18.04).

You can override this issue by editing the index.js file in the recipe.
Change
module.exports = Franz => Franz;

To
module.exports = Franz => class useragent extends Franz { overrideUserAgent() { return "Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136"; } };

The recipe should be located at:
Mac: ~/Library/Application Support/Franz/recipes/
Windows: %appdata%/Franz/recipes/
Linux: ~/.config/Franz/recipes/

Duplicate: https://github.com/meetfranz/franz/issues/1573

This is not working anymore for Linux (I'm on Ubuntu 18.04).

You can override this issue by editing the index.js file in the recipe.
Change
module.exports = Franz => Franz;

To
module.exports = Franz => class useragent extends Franz { overrideUserAgent() { return "Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136"; } };

The recipe should be located at:
Mac: ~/Library/Application Support/Franz/recipes/
Windows: %appdata%/Franz/recipes/
Linux: ~/.config/Franz/recipes/

@shimatai it worked for me. I changed it in the folder corresponding to the proper service (so ~/.config/Franz/recipes/hangouts/index.js for me), changed the line and it did the tricks !
I'm on Manjaro 19.0.2 :ok_hand:

This is not working anymore for Linux (I'm on Ubuntu 18.04).

You can override this issue by editing the index.js file in the recipe.
Change
module.exports = Franz => Franz;

To
module.exports = Franz => class useragent extends Franz { overrideUserAgent() { return "Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136"; } };

The recipe should be located at:
Mac: ~/Library/Application Support/Franz/recipes/
Windows: %appdata%/Franz/recipes/
Linux: ~/.config/Franz/recipes/

@shimatai it worked for me. I changed it in the folder corresponding to the proper service (so ~/.config/Franz/recipes/hangouts/index.js for me), changed the line and it did the tricks !
I'm on Manjaro 19.0.2

Do you have 2 factor authentication enabled?

Yes

module.exports = Franz => class useragent extends Franz { overrideUserAgent() { return "Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10136"; } };

The recipe should be located at:
Mac: `~/Library/Application Support/Franz/recipes/`
Windows: `%appdata%/Franz/recipes/`
Linux: `~/.config/Franz/recipes/`

Solution works. Why it isn't the default?

Didn't work for me. Gmail behaviour changed though. Now I first get the first marketing page of gmail and when clicking Sign in --> Link opens in a new tab and I end up at the Account Chooser page.
Also Slack has a similar problem.
Could i be the device which is apparently Electron?


layer: clarify attributes for implied directories

The image specification currently does not describe how conformant implementations should handle the case of a layer that contains "implied directories" -- entries that imply parent directories exist through their path, without those parent directories having their own entires in the archive.
As such, this behavior is currently implementation-defined and may not be consistent, even in the same implementation (e.g. moby/moby#44106).
To resolve this, we explicitly define what behavior is expected in this situation, selecting 'neutral' attributes (e.g. using the container USER's UID/GID, and using 0755 for mode, as derived from the default umask(2) of 0022).
It has been observed that it may be desirable to allow (MAY) conformant implementations to instead elect to not handle this case, and to fail with a useful error message instead. I lack the insight into the wider ecosystem to consider if this is a useful behavior, but it provides another aspect to consider when discussing this change.

cc @vasiliy-ul @thaJeztah

Does this mean / would be chowned to the user, with 755 permissions? Are there implementations that do this already?

/ cannot be present as all paths in a tar archive are relative. Implementations should handle that already, though I would not be opposed to an explicit Note: that calls that out.

Hmm, I suppose I misspoke, as . will serve the same purpose even if it's not a literal /. Moby has always ignored the root directory when creating parent directories, and the new implementation that is driving this PR makes it a bit more explicit:
https://github.com/moby/moby/blob/b9921a5560e22a2744bd7f51cca0475bbe20162e/pkg/archive/archive.go#L1154-L1173

When I first saw this, I was thinking of the COPY --link feature in buildkit, where you don't necessarily know the parent folder state, but inferring it is probably a worse option (e.g. creating a user folder in /home shouldn't change the permission of /home itself).
Since we are saying layer creators SHOULD include the parent folders, and this is just an exception case, then this LGTM. I've added it to tomorrow's meeting agenda to get some more eyes on it.

Capturing from the call -

Create an issue on runtime spec to get inputs from runtime authors
Consider how layers shared across behaves with this proposal of implicit directories.
@cpuguy83  -

Possibly need to look at the parent dir to get perms
Maybe with consideration for SOURCE_DATE_EPOCH or other such configurability.

I'm still mulling over what changes to this PR should look like, but as I experiment and consider, others might benefit from links to existing implementations:

podman/cri-o:
https://github.com/containers/storage/blob/4a4d8f88a707a3118c1fa61672772a428ac7e460/pkg/archive/diff.go#L79-L93
containerd:
https://github.com/containerd/containerd/blob/bb0c3804c637d640a029a8979916d97f8dcc5a8e/archive/tar.go#L425-L483
https://github.com/containerd/containerd/blob/bb0c3804c637d640a029a8979916d97f8dcc5a8e/archive/tar_unix.go#L143-L175
moby:
https://github.com/moby/moby/blob/b9921a5560e22a2744bd7f51cca0475bbe20162e/pkg/archive/archive.go#L1154-L1173

To rephrase the shared layer concern: layers aren't attached to a single image, they can be included in multiple images. So when runtimes share layers, the filesystem permissions and ownership can vary based on the order the images are pulled.
The fix is to pick settings not based on the image, either static values (root), or imply values based on the first entry in the tar file that creates the implied directories.

umoci uses 0755 and the root UIDs, btw. We also set the ctime and mtime to the Unix epoch (to have at least some hope of producing a reproducible container) but I think no-one else does that. I don't think we should say that implementations shouldn't modify / -- a lot of container images don't have a / (or . if you prefer) entry and so you can end up with irreproducible container images if you don't allow container image tools to set / (or any other implied directory) to some fixed value.

I've spent a bit of time experimenting over the last few days, and come to some conclusions:

As nice as supporting SOURCE_DATE_EPOCH sounds, there's not really a way to interpret it that makes sense given the process model of existing implementations; it also has the potential to not be deterministic across runtime instance restarts.
Containerd currently recurses looking to copy metadata back down the tree when it is missing; this is rather complex, and hard to specify, and doesn't seem to offer many advantages when we are trying to define an edge case image authors should avoid.
Picking the most neutral metadata possible (e.g. root:root, with the Unix epoch time) seems to be the most reasonable across the board.

I've pushed up a new version that adjusts things to root:root and the Unix epoch; however I still have not considered atime and ctime as they are not mentioned elsewhere in the existing spec. Does anything think we should consider those as well?

I'd like to hear more about the motivation behind these specific recommendations/requirements. A user might naively expect parent directories to be created with the same ownership and permissions as the file being created, and I can't immediately think of an obvious reason to not do that. A different expectation might be that the ownership percolates down from the parent of the first implied directory.
i.e. If you're creating A/B/C/D and A/B already exists then the ownership and permissions of D will be specified but C is the focus of this PR. This proposal dictates specific attributes for C. I might also suggest that C's attributes could be copied from B or from D.

however I still have not considered atime and ctime as they are not mentioned elsewhere in the existing spec. Does anyone think we should consider those as well?

atime is not practical to set on Linux (there's no interface to change it directly, you can only change the system time -- possible in a time namespace -- and hope when you touch the file it matches the time you wanted) so we should ignore it. I think ctime should be set to the same as mtime.
(I wrote this draft message last year and it got lost in my tabs. I only just got around to posting it. Sorry...)

@sparr At the moment the behaviour is completely unspecified so different image-spec implementations can produce different results. If you feel that your suggested algorithm makes more sense, then you should still want some text in the spec to describe the required behaviour.
As for your suggestion, there are a few issues that would need to be considered:

What about xattrs and other file metadata? Should only the owner and mode be copied? What about file attributes? ACLs?
What if A/B/C/D is a file, with the parent being an implied directory? Using the file mode doesn't make sense, so we have to pick a default for this case anyway. The trickle-down suggestion doesn't have this problem, but it could cause security issues if the top directory had the sticky bit set and you ended up setting the sticky bit for every implied directory.
Looking at precedent, GNU tar creates implied directories as the current user and sets the mode of directories to 0755 (though I suspect this is affected by umask). In other words, for root users the behaviour matches this proposal (and the way umoci does it, btw).

My personal view is that there needs to just be a simple fallback behaviour for this edge-case -- the suggestions of copying attributes up or down just adds more complexity for something that basically no image is going to run into. No image generation tool that I'm aware of generates tar archives with implied directories (arguably it would be perfectly correct for an image-spec tool today to error out if you had an archive with implied directories).
In addition, a new MUST change like this should take into account what existing tools do -- AFAIK most tools either handle this in the "naive" way (without noticing this might be an issue, they just make implied directories) or they use similar defaults to the ones described in this PR.

Friendly ping @neersighted -- I think changing that one MUST to SHOULD is the only feedback preventing this from moving :eyes: :heart: