change the default width and height of Size to Val::Auto

Objective
In CSS Flexbox width and height are auto by default, whereas in Bevy their default is Size::Undefined.
This means that, unlike in CSS, if you elide a height or width value for a node it will be given zero length (unless it has an explicitly sized child node). This has misled users into falsely assuming that they have to explicitly set a value for both height and width all the time.
relevant issue: #7120
Solution
Change the Size width and height default values to Val::Auto
Changelog

Changed the Size width and height default values to Val::Auto

Migration Guide
The default values for Size width and height have been changed from Val::Undefined to Val::Auto.
It's unlikely to cause any issues with existing code.

Undefined and Auto definitely aren't the same.
Ultra minimal example, red window:
use bevy::prelude::*;
fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_startup_system(|mut commands: Commands| {
            commands.spawn(Camera2dBundle::default());
            commands.spawn(NodeBundle {
                style: Style {
                    size: Size::new(Val::Percent(100.), Val::Auto),
                    ..Default::default()
                },
                background_color: BackgroundColor(Color::RED),
                ..Default::default()
            });
        })
        .run();
}

grey  window:
use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_startup_system(|mut commands: Commands| {
            commands.spawn(Camera2dBundle::default());
            commands.spawn(NodeBundle {
                style: Style {
                    size: Size::new(Val::Percent(100.), Val::Undefined),
                    ..Default::default()
                },
                background_color: BackgroundColor(Color::RED),
                ..Default::default()
            });
        })
        .run();

The Taffy 2.x source is full of child_style.cross_size(constants.dir) == Dimension::Auto predicates.

bors r+


Reduce CI complexity using OCIS_URL

PR #1148 implemented an environment variable OCIS_URL
From that environment variable a lot of other values are deduced that are suitable for an install where "everything" runs on a single host. That should be relevant for CI.
Investigate the environment variables being used in CI to define the OCIS configuration. Try to use OCIS_URL instead, and get rid of as many "random" environment variables as possible.
Do the same in owncloud/web and get the configuration of the web-on-OCIS UI test pipelines "the same" as the way they are configured when running web UI test pipelines in OCIS CI.

@phil-davis the env var is already applied in ocis CI,web was done in owncloud/web#4600, can we close this now?

@phil-davis the env var is already applied in ocis CI,web was done in owncloud/web#4600, can we close this now?


contract __call__ function

What was wrong?
closes #559
How was it fixed?
To-Do

[ ] OPTIONAL: Update Spec if applicable

[ ] Add entry to the release notes (may forgo for trivial changes)

[ ] Clean up commit history

Codecov Report

Merging #622 (1ee5f20) into master (f151b53) will decrease coverage by 0.11%.
The diff coverage is 64.28%.

@@            Coverage Diff             @@
##           master     #622      +/-   ##
==========================================
- Coverage   86.51%   86.40%   -0.12%
==========================================
  Files          96       96
  Lines        8424     8464      +40
==========================================
+ Hits         7288     7313      +25
- Misses       1136     1151      +15

Impacted Files
Coverage Δ

crates/analyzer/src/db.rs
100.00% <ø> (ø)

crates/analyzer/src/db/queries/contracts.rs
86.48% <44.44%> (-7.19%)
:arrow_down:

crates/analyzer/src/namespace/items.rs
81.62% <100.00%> (+0.05%)
:arrow_up:

crates/yulgen/src/db/queries/contracts.rs
100.00% <100.00%> (ø)

crates/yulgen/src/runtime/abi_dispatcher.rs
100.00% <100.00%> (ø)

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 f151b53...1ee5f20. Read the comment docs.

I like this approach. It is a natural way to accommodate the ABI compatibility concerns and is foundational enough that we can always build higher level language features that use this internally.
LGTM


Dev Portal API Listing keeps loading when there are no published APIs

When no APIs are published, accessing https://localhost:9443/devportal/apis page keeps loading. Instead it should show "Sorry, no records found" message.
This issue occurs with the fix done in https://github.com/wso2/carbon-apimgt/pull/7207

Fixed with https://github.com/wso2/carbon-apimgt/pull/7228


Please change the warning: "Be careful when using this code, it's not being tested!"

I think I understand the intention behind this warning, but its current wording can be pretty misleading. The warning shows up if a code block is set to ignore in the documentation.
I have such code in the documentation for my crate here:

Using random() often requires you to specify a type that you want to generate. For example,
if you run the following, the compiler will tell you that it needs you to give it more
information about the type that you want to generate:
let mut turtle = Turtle::new();
turtle.set_speed(random());

This will produce an error that looks something like the following:
error[E0283]: type annotations required: cannot resolve `_: std::convert::Into<turtle::Speed>`
 --> src/rand.rs:5:8
  |
5 | turtle.set_speed(random());
  |        ^^^^^^^^^

This code intentionally doesn't compile so that I can show the reader an error case. I marked it with ignore so that it would still pass the tests. Rust doesn't provide a mechanism yet for doctests that aren't meant to compile.
This has the effect of producing the following for anyone reading the documentation on docs.rs:

Seeing this warning immediately makes this code seem untrustworthy when it is in fact correct.
Possible Solution
It would be great if we could completely disable enhancements like this to the documentation on a per-crate basis. These don't show up with just regular cargo doc, so they're hard to find unless you go look on docs.rs. (This is optional but would be really great to have.)
As for this warning, I think we should change its wording and its icon. Instead of warning, let's use the information symbol since it's quite possible that there may be nothing to warn about in the first place. Then, it would be great to change the wording of the message to something more mild and informative instead of the cautious and negative tone used now.
Instead of "⚠ Be careful when using this code, it's not being tested!"
We could have: "🛈 This code is not automatically tested by the documentation tests of this crate."
The second note is both very accurate and doesn't imply that the code may not be correct. I'd be happy to open a PR for this if you're okay with this message.
I'm open to other messages too. It's just important that people aren't misled into thinking that the documentation they are reading may not be correct. For well written docs (which we're all aiming for), that will most often be the exception to the rule, not the most common case to account for.

Thanks for reporting, this warning is generated by rustdoc and I believe it is removed in recent versions. Updating rustc on docs.rs should fix this issue and remove the warning. I had some setback for building rustc on OSX but it is about to get fixed as well.

Closing as this has been fixed in rustdoc for a while now.


Slight tweak to the Docker Desktop UI Container List View Action Buttons would improve usability

Tell us about your request
I have a UI/UX suggestion that would probably be trivial to implement but would make the user experience better.
Which service(s) is this request for?
Hi, I’m working in a microservices environment where we have about 18 microservices running in Docker. Most of us use Docker Desktop to interact with these services. On a regular basis, we will stop, start, and exec into running containers.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
PROBLEM: On the right side of the Containers list, there are Action buttons. When my cursor is in this area, I know that I want to click an Action button. I do not want to click on the Container row itself, which would open into the Logs section of that Container. However, the Action Buttons are small circles. When you click just outside these circles, you end up the Container Logs view—a place you certainly did not want to be, because if you did want to be there, you’d just click on the Container row itself, which is right in your face and stretches across the window.
I suspect that 99% of users who click in the Actions area are trying to perform an Action, not navigate into the Container Logs view. Yet when a user is working fast, there tend to be many misclicks just outside the boundary of the Action buttons. These clicks take you to the Container logs view, and you have to navigate back to Container List view again, go back and click the button more accurately.
SOLUTION: I suggest that the area outside the Action Button Circles should have no cursor action when clicked. That, or the entire Cell in which the Action button is contained should perform the same command as the Action button itself. Users are often working very fast and shouldn’t need to slow down to bullseye the target of an Action Button.

Although I have never noticed it, now I see it could indeed be improved. The same happens by the way when I run a compose project and I want to list the services in that project so I would click on the arrow icon between the checkbox and the compose project name. And that arrow is even smaller than the action buttons.


Support password protected videos

Sometimes it happens that the video is password protected by the instructor. As an example, this is the case of the first video of the "Misure" course.
Link to video: Misure - Lecture 1
Password of the video: misure
After the webpoliself login flow, the user is redirected on a page where it is mandatory to insert the password for the video, otherwise no access is granted (and thus the PoliWebex tool won't work).
Input element xpath: //*[@id="main_content"]/div/div/div[2]/div/div[1]/input
Submit button xpath: //*[@id="main_content"]/div/div/div[2]/button
Thank you for your always useful and fast work ;)
EDIT: Attach image

Support added in https://github.com/sup3rgiu/PoliWebex/commit/74296e47007a2d922e48cc2990ba02c84210f57d


#96 - Fix ctrl+m, ctrl+a shortcuts

Fixed wrong reference to ReactJS component refs

Hi @pietromartino,
Thanks for fixing this issue !
could you add this in the release note (CHANGES.md file) and following the convention.

Fix "Show all data" shortcut from popup issue 96 (fix by Pietro Martino)


Suggest - get rid of explicitly defined ModelInput class

Imaging what it will be on that 7000 column's dataset.

A proper way is to use DataFrame class, which supports loading from fixed width text file directly.

If ModelInput were not used and only LoadCSV is used, can model skip additional columns?
For apps having  ModelInput may have the benefit of being a list of what fields are needed for the model, and being able to read it during debugging.

Thanks all for the discussion. There are no plans for this at the moment, so closing for now.


GET URL opens directly in browser, download button missing

I'm encountering an issue with the Openfire HTTP File Upload plugin(1.3.0). When accessing a file through the GET URL generated by the plugin, the browser opens the file directly instead of displaying a download button.
Here are the details of the issue:
Steps to reproduce:

Upload a file using the plugin.
Access the generated GET URL for the uploaded file.
Expected behavior: The browser should display a download button, allowing the user to save the file.
Actual behavior: The browser opens the file directly, often displaying the content inline.

I checked but not able to find any configuration where I can define the content type or content-disposition header to make it downloadable.
I would appreciate it if you could investigate this issue and suggest potential solutions or workarounds. If there are configuration options to control download behavior, please provide guidance on how to access them.

HTTP File Upload plugin's URLs are not really intended to be used directly in a browser. The plugin certainly does not intent to present any kind of UI interface for end-users. This plugin provides infrastructure, not a end-user facing feature.
Instead, it is expected that a client that gets sent the download URL provides appropriate UI elements to present a reference to the data that is being exchanged.
The plugin does currently not allow the uploader to explicitly define the content type of the data (an issue for this feature requests exists here). Instead, the plugin will attempt to determine the content type based on the file data and metadata.

thanks @guusdk for the prompt reply.
we are direclty sharing the GET URL to access the media file mp3 but that third party module is rejecting file because the file content-type is generic applicate/octet-stream. and because of it we are not able to exchange mp3 files do you have any workaround or we need to create some wrapper to provide end to end features?

Try using a filename value that ends with 'mp3'. Otherwise, the most prudent way to achieve this is by fixing the feature request that I linked to above.

when i checked the fileRepo path. files are saved as alphaNumeric number without file extension. and to access the file we are using GET URL for eg. https:///httpfileupload/oRXUINag5U4FXgKIB1-V-lypNcE/test.mp3
but still the content-type is not resolved.

Then I'm not sure if there's another way to get this to work other than implementing https://github.com/guusdk/httpfileuploadcomponent/issues/25


x/tools/gopls: suggests completion 'nilfunc' instead of 'nil' when module requires golang.org/x/tools

example.com$ go version
go version devel +55b2d479d Tue Oct 20 08:08:15 2020 +0000 linux/amd64

example.com$ ls -d ~/.emacs.d/elpa/eglot*
/usr/local/google/home/bcmills/.emacs.d/elpa/eglot-20200830.1254

example.com$ go version -m $(which gopls)
/usr/local/google/home/bcmills/bin/gopls: devel +186f0220d0 Mon Oct 5 11:12:24 2020 -0400
        path    golang.org/x/tools/gopls
        mod     golang.org/x/tools/gopls        v0.5.1  h1:AF3Uh7HF08SZpKFfgJO6zfF3bbxyDXWqdkK4kMXiQ1o=
        dep     github.com/BurntSushi/toml      v0.3.1  h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
        dep     github.com/google/go-cmp        v0.5.1  h1:JFrFEBb2xKufg6XkJsJr+WbKb4FQlURi5RUcBveYu9k=
        dep     github.com/sergi/go-diff        v1.1.0  h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
        dep     golang.org/x/mod        v0.3.0  h1:RM4zey1++hCTbCVQfnWeKs9/IEsaBLA8vTkd0WVtmH4=
        dep     golang.org/x/sync       v0.0.0-20200625203802-6e8e738ad208      h1:qwRHBd0NqMbJxfbotnDhm2ByMI1Shq4Y6oRJo21SGJA=
        dep     golang.org/x/tools      v0.0.0-20200930165741-f1523d29dbb9      h1:1R38tQp22dcHpTKJPjgVa16FhlDy/kHEaCM/ndi/FIc=
        dep     golang.org/x/xerrors    v0.0.0-20200804184101-5ec99f83aff1      h1:go1bK/D/BFZV2I8cIQd1NKEZ+0owSTG1fDTci4IqFcE=
        dep     honnef.co/go/tools      v0.0.1-2020.1.5 h1:nI5egYTGJakVyOryqLs1cQO5dO0ksin5XXs2pspk75k=
        dep     mvdan.cc/gofumpt        v0.0.0-20200802201014-ab5a8192947d      h1:t8TAw9WgTLghti7RYkpPmqk4JtQ3+wcP5GgZqgWeWLQ=
        dep     mvdan.cc/xurls/v2       v2.2.0  h1:NSZPykBXJFCetGZykLAxaL6SIpvbVy/UFEniIfHAa8A=

example.com$

Steps to reproduce
$ go mod init example.com
go: creating new go.mod: module example.com

$ go get -d golang.org/x/tools
go: downloading golang.org/x/tools v0.0.0-20201020141929-90550980fc82
go: golang.org/x/tools upgrade => v0.0.0-20201020141929-90550980fc82

example.com$ cat > example.go
package example

func F() interface{} {
}

$ emacs example.go

Now move the cursor to the function body, type return nil, leave the cursor at the end of that line, and wait for completions.
Expected
nil is the obvious thing to return from a func interface{}, and is also a valid and complete statement, so no completion should be suggested (or the first completion should be nil itself).
Observed
The first completion returned by gopls is the package name nilfunc for package golang.org/x/tools/go/analysis/passes/nilfunc, so any stray press of the Tab key will result in a broken source file. 😞

[Trace - 11:45:39.152 AM] Sending request 'initialize - (1)'.
Params: {"processId":9779,"rootPath":"/tmp/tmp.UF2AKOuMKI/example.com/","rootUri":"file:///tmp/tmp.UF2AKOuMKI/example.com/","initializationOptions":null,"capabilities":{"workspace":{"applyEdit":true,"executeCommand":{"dynamicRegistration":false},"workspaceEdit":{"documentChanges":false},"didChangeWatchedFiles":{"dynamicRegistration":true},"symbol":{"dynamicRegistration":false},"configuration":true},"textDocument":{"synchronization":{"dynamicRegistration":false,"willSave":true,"willSaveWaitUntil":true,"didSave":true},"completion":{"dynamicRegistration":false,"completionItem":{"snippetSupport":true},"contextSupport":true},"hover":{"dynamicRegistration":false,"contentFormat":["markdown","plaintext"]},"signatureHelp":{"dynamicRegistration":false,"signatureInformation":{"parameterInformation":{"labelOffsetSupport":true}}},"references":{"dynamicRegistration":false},"definition":{"dynamicRegistration":false},"declaration":{"dynamicRegistration":false},"implementation":{"dynamicRegistration":false},"typeDefinition":{"dynamicRegistration":false},"documentSymbol":{"dynamicRegistration":false,"hierarchicalDocumentSymbolSupport":true,"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]}},"documentHighlight":{"dynamicRegistration":false},"codeAction":{"dynamicRegistration":false,"codeActionLiteralSupport":{"codeActionKind":{"valueSet":["quickfix","refactor","refactor.extract","refactor.inline","refactor.rewrite","source","source.organizeImports"]}}},"formatting":{"dynamicRegistration":false},"rangeFormatting":{"dynamicRegistration":false},"rename":{"dynamicRegistration":false},"publishDiagnostics":{"relatedInformation":false}},"experimental":null}}

[Trace - 11:45:39.153 AM] Received response 'initialize - (1)' in 1ms.
Result: {"capabilities":{"textDocumentSync":{"openClose":true,"change":2,"save":{}},"completionProvider":{"triggerCharacters":["."]},"hoverProvider":true,"signatureHelpProvider":{"triggerCharacters":["(",","]},"definitionProvider":true,"typeDefinitionProvider":true,"implementationProvider":true,"referencesProvider":true,"documentHighlightProvider":true,"documentSymbolProvider":true,"codeActionProvider":{"codeActionKinds":["quickfix","refactor.extract","refactor.rewrite","source.fixAll","source.organizeImports"]},"codeLensProvider":{},"documentLinkProvider":{},"workspaceSymbolProvider":true,"documentFormattingProvider":true,"documentOnTypeFormattingProvider":{"firstTriggerCharacter":""},"renameProvider":true,"foldingRangeProvider":true,"executeCommandProvider":{"commands":["generate","fill_struct","regenerate_cgo","test","tidy","undeclared_name","upgrade_dependency","vendor","extract_variable","extract_function","gc_details","generate_gopls_mod"]},"callHierarchyProvider":true,"workspace":{"workspaceFolders":{"supported":true,"changeNotifications":"workspace/didChangeWorkspaceFolders"}}},"serverInfo":{"name":"gopls","version":"Build info\n----------\ngolang.org/x/tools/gopls v0.5.1\n<EMAIL_ADDRESS>h1:AF3Uh7HF08SZpKFfgJO6zfF3bbxyDXWqdkK4kMXiQ1o=\n<EMAIL_ADDRESS>h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=\n<EMAIL_ADDRESS>h1:JFrFEBb2xKufg6XkJsJr+WbKb4FQlURi5RUcBveYu9k=\n<EMAIL_ADDRESS>h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=\n<EMAIL_ADDRESS>h1:RM4zey1++hCTbCVQfnWeKs9/IEsaBLA8vTkd0WVtmH4=\n<EMAIL_ADDRESS>h1:qwRHBd0NqMbJxfbotnDhm2ByMI1Shq4Y6oRJo21SGJA=\n<EMAIL_ADDRESS>h1:1R38tQp22dcHpTKJPjgVa16FhlDy/kHEaCM/ndi/FIc=\n<EMAIL_ADDRESS>h1:go1bK/D/BFZV2I8cIQd1NKEZ+0owSTG1fDTci4IqFcE=\n<EMAIL_ADDRESS>h1:nI5egYTGJakVyOryqLs1cQO5dO0ksin5XXs2pspk75k=\n<EMAIL_ADDRESS>h1:t8TAw9WgTLghti7RYkpPmqk4JtQ3+wcP5GgZqgWeWLQ=\n<EMAIL_ADDRESS>h1:NSZPykBXJFCetGZykLAxaL6SIpvbVy/UFEniIfHAa8A=\n"}}

[Trace - 11:45:39.154 AM] Sending notification 'initialized'.
Params: {}

[Trace - 11:45:39.155 AM] Received notification 'window/showMessage'.
Params: {"type":4,"message":"Loading packages..."}

[Trace - 11:45:39.155 AM] Received request 'workspace/configuration - (1)'.
Params: {"items":[{"scopeUri":"file:///tmp/tmp.UF2AKOuMKI/example.com/","section":"gopls"},{"scopeUri":"file:///tmp/tmp.UF2AKOuMKI/example.com/","section":"gopls-example.com"}]}

[Trace - 11:45:39.155 AM] Sending notification 'textDocument/didOpen'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go","version":0,"languageId":"go","text":"package example\n\nfunc F() interface{} {\n}\n"}}

[Trace - 11:45:39.156 AM] Sending notification 'workspace/didChangeConfiguration'.
Params: {"settings":{"gopls":{"staticcheck":true,"matcher":"CaseSensitive"}}}

[Trace - 11:45:39.156 AM] Sending request 'textDocument/documentSymbol - (2)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"}}

[Trace - 11:45:39.161 AM] Sending response 'workspace/configuration - (1)' in 6ms.
Result: [{"staticcheck":true,"matcher":"CaseSensitive"},null]

[Trace - 11:45:39.197 AM] Received request 'client/registerCapability - (2)'.
Params: {"registrations":[{"id":"workspace/didChangeWatchedFiles-0","method":"workspace/didChangeWatchedFiles","registerOptions":{"watchers":[{"globPattern":"**/*.{go,mod,sum}","kind":7},{"globPattern":"/tmp/tmp.UF2AKOuMKI/example.com/**/*.{go,mod,sum}","kind":7}]}}]}

[Trace - 11:45:39.198 AM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/10/20 11:45:39 go env for /tmp/tmp.UF2AKOuMKI/example.com/\n(root /tmp/tmp.UF2AKOuMKI/example.com)\n(go version go version devel +55b2d479d Tue Oct 20 08:08:15 2020 +0000 linux/amd64\n)\n(valid build configuration = true)\n(build flags: [])\nGO111MODULE=auto\nGOFLAGS=\nGOMOD=/tmp/tmp.UF2AKOuMKI/example.com/go.mod\nGONOPROXY=\nGOPATH=/tmp/tmp.UF2AKOuMKI/_gopath\nGOINSECURE=\nGOSUMDB=sum.golang.org\nGONOSUMDB=\nGOPRIVATE=\nGOCACHE=/usr/local/google/home/bcmills/.cache/go-build\nGOMODCACHE=/tmp/tmp.UF2AKOuMKI/_gopath/pkg/mod\nGOPROXY=https://proxy.golang.org,direct\nGOROOT=/usr/local/google/home/bcmills/sdk/gotip\n\n"}

[Trace - 11:45:39.199 AM] Sending response 'client/registerCapability - (2)' in 1ms.
Result:

[Trace - 11:45:39.295 AM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/10/20 11:45:39 go/packages.Load\n\tsnapshot=0\n\tdirectory=/tmp/tmp.UF2AKOuMKI/example.com\n\tquery=[./... builtin]\n\tpackages=2\n"}

[Trace - 11:45:39.295 AM] Received notification 'window/showMessage'.
Params: {"type":3,"message":"Finished loading packages."}

[Trace - 11:45:39.296 AM] Received request 'workspace/configuration - (3)'.
Params: {"items":[{"scopeUri":"file:///tmp/tmp.UF2AKOuMKI/example.com/","section":"gopls"},{"scopeUri":"file:///tmp/tmp.UF2AKOuMKI/example.com/","section":"gopls-example.com"}]}

[Trace - 11:45:39.304 AM] Received notification 'textDocument/publishDiagnostics'.
Params: {"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/go.mod","diagnostics":[{"range":{"start":{"line":4,"character":0},"end":{"line":4,"character":61}},"severity":2,"source":"go mod tidy","message":"golang.org/x/tools is not used in this module"}]}

[Trace - 11:45:39.305 AM] Received notification 'textDocument/publishDiagnostics'.
Params: {"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go","diagnostics":[{"range":{"start":{"line":3,"character":0},"end":{"line":3,"character":1}},"severity":1,"source":"compiler","message":"missing return"}]}

[Trace - 11:45:39.319 AM] Sending response 'workspace/configuration - (3)' in 23ms.
Result: [{"staticcheck":true,"matcher":"CaseSensitive"},null]

[Trace - 11:45:39.319 AM] Received response 'textDocument/documentSymbol - (2)' in 162ms.
Result: [{"name":"F","detail":"()","kind":12,"range":{"start":{"line":2,"character":0},"end":{"line":3,"character":1}},"selectionRange":{"start":{"line":2,"character":5},"end":{"line":2,"character":6}}}]

[Trace - 11:45:57.507 AM] Sending request 'textDocument/signatureHelp - (3)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"},"position":{"line":2,"character":22}}

[Trace - 11:45:57.508 AM] Received response 'textDocument/signatureHelp - (3)' in 0ms.
Result: null

[Trace - 11:45:57.508 AM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/10/20 11:45:57 no signature help: cannot find an enclosing function\n\tposition={2 22}\n"}

[Trace - 11:45:57.508 AM] Sending request 'textDocument/hover - (4)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"},"position":{"line":2,"character":22}}

[Trace - 11:45:57.509 AM] Received response 'textDocument/hover - (4)' in 0ms.
Result: null

[Trace - 11:45:57.509 AM] Sending request 'textDocument/documentHighlight - (5)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"},"position":{"line":2,"character":22}}

[Trace - 11:45:57.510 AM] Received response 'textDocument/documentHighlight - (5)' in 0ms.
Result: []

[Trace - 11:45:58.058 AM] Sending notification 'textDocument/didChange'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go","version":2},"contentChanges":[{"range":{"start":{"line":2,"character":22},"end":{"line":2,"character":22}},"rangeLength":0,"text":"\n"},{"range":{"start":{"line":3,"character":0},"end":{"line":3,"character":0}},"rangeLength":0,"text":"\t"}]}

[Trace - 11:45:58.059 AM] Sending request 'textDocument/signatureHelp - (6)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"},"position":{"line":3,"character":1}}

[Trace - 11:45:58.059 AM] Sending request 'textDocument/hover - (7)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"},"position":{"line":3,"character":1}}

[Trace - 11:45:58.059 AM] Received response 'textDocument/signatureHelp - (6)' in 0ms.
Result: null

[Trace - 11:45:58.060 AM] Received response 'textDocument/hover - (7)' in 0ms.
Result: null

[Trace - 11:45:58.060 AM] Sending request 'textDocument/documentHighlight - (8)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"},"position":{"line":3,"character":1}}

[Trace - 11:45:58.060 AM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/10/20 11:45:58 no signature help: cannot find an enclosing function\n\tposition={3 1}\n"}

[Trace - 11:45:58.060 AM] Received response 'textDocument/documentHighlight - (8)' in 0ms.
Result: []

[Trace - 11:45:58.060 AM] Received notification 'textDocument/publishDiagnostics'.
Params: {"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go","version":2,"diagnostics":[{"range":{"start":{"line":4,"character":0},"end":{"line":4,"character":1}},"severity":1,"source":"compiler","message":"missing return"}]}

[Trace - 11:46:00.130 AM] Sending notification 'textDocument/didChange'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go","version":12},"contentChanges":[{"range":{"start":{"line":3,"character":1},"end":{"line":3,"character":1}},"rangeLength":0,"text":"r"},{"range":{"start":{"line":3,"character":2},"end":{"line":3,"character":2}},"rangeLength":0,"text":"e"},{"range":{"start":{"line":3,"character":3},"end":{"line":3,"character":3}},"rangeLength":0,"text":"t"},{"range":{"start":{"line":3,"character":4},"end":{"line":3,"character":4}},"rangeLength":0,"text":"u"},{"range":{"start":{"line":3,"character":5},"end":{"line":3,"character":5}},"rangeLength":0,"text":"r"},{"range":{"start":{"line":3,"character":6},"end":{"line":3,"character":6}},"rangeLength":0,"text":"n"},{"range":{"start":{"line":3,"character":7},"end":{"line":3,"character":7}},"rangeLength":0,"text":" "},{"range":{"start":{"line":3,"character":8},"end":{"line":3,"character":8}},"rangeLength":0,"text":"n"},{"range":{"start":{"line":3,"character":9},"end":{"line":3,"character":9}},"rangeLength":0,"text":"i"},{"range":{"start":{"line":3,"character":10},"end":{"line":3,"character":10}},"rangeLength":0,"text":"l"}]}

[Trace - 11:46:00.132 AM] Sending request 'textDocument/completion - (9)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"},"position":{"line":3,"character":11},"context":{"triggerKind":1}}

[Trace - 11:46:00.133 AM] Sending request 'textDocument/signatureHelp - (10)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"},"position":{"line":3,"character":11}}

[Trace - 11:46:00.134 AM] Sending request 'textDocument/hover - (11)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"},"position":{"line":3,"character":11}}

[Trace - 11:46:00.135 AM] Sending request 'textDocument/documentHighlight - (12)'.
Params: {"textDocument":{"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go"},"position":{"line":3,"character":11}}

[Trace - 11:46:00.137 AM] Received notification 'textDocument/publishDiagnostics'.
Params: {"uri":"file:///tmp/tmp.UF2AKOuMKI/example.com/example.go","version":12,"diagnostics":[{"range":{"start":{"line":0,"character":0},"end":{"line":0,"character":15}},"severity":2,"source":"ST1000","message":"at least one file in a package should have a package comment"}]}

[Trace - 11:46:00.168 AM] Received response 'textDocument/completion - (9)' in 36ms.
Result: {"isIncomplete":true,"items":[{"label":"nilfunc","kind":9,"detail":"\"golang.org/x/tools/go/analysis/passes/nilfunc\"","preselect":true,"sortText":"00000","filterText":"nilfunc","insertTextFormat":2,"textEdit":{"range":{"start":{"line":3,"character":8},"end":{"line":3,"character":11}},"newText":"nilfunc"},"additionalTextEdits":[{"range":{"start":{"line":1,"character":0},"end":{"line":1,"character":0}},"newText":"\nimport \"golang.org/x/tools/go/analysis/passes/nilfunc\"\n"}]},{"label":"nilness","kind":9,"detail":"\"golang.org/x/tools/go/analysis/passes/nilness\"","sortText":"00001","filterText":"nilness","insertTextFormat":2,"textEdit":{"range":{"start":{"line":3,"character":8},"end":{"line":3,"character":11}},"newText":"nilness"},"additionalTextEdits":[{"range":{"start":{"line":1,"character":0},"end":{"line":1,"character":0}},"newText":"\nimport \"golang.org/x/tools/go/analysis/passes/nilness\"\n"}]},{"label":"nil","kind":6,"sortText":"00002","filterText":"nil","insertTextFormat":2,"textEdit":{"range":{"start":{"line":3,"character":8},"end":{"line":3,"character":11}},"newText":"nil"}}]}

[Trace - 11:46:00.169 AM] Received response 'textDocument/signatureHelp - (10)' in 35ms.
Result: null

[Trace - 11:46:00.169 AM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/10/20 11:46:00 no signature help: cannot find an enclosing function\n\tposition={3 11}\n"}

[Trace - 11:46:00.169 AM] Received response 'textDocument/hover - (11)' in 35ms.
Result: {"contents":{"kind":"markdown","value":"```go\nnil\n```"},"range":{"start":{"line":3,"character":8},"end":{"line":3,"character":11}}}

[Trace - 11:46:00.170 AM] Received response 'textDocument/documentHighlight - (12)' in 34ms.
Result: [{"range":{"start":{"line":2,"character":9},"end":{"line":2,"character":20}},"kind":1},{"range":{"start":{"line":3,"character":8},"end":{"line":3,"character":11}},"kind":1}]

[Trace - 11:46:30.169 AM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/10/20 11:46:30 background imports cache refresh starting\n"}

[Trace - 11:46:30.172 AM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/10/20 11:46:30 background refresh finished after 3.385517ms\n"}

CC @stamblerre @heschik

Thanks for the report! This seems like a case of unimported completions getting ranked higher than other completions, which I've actually noticed happening more recently.
@heschik: Maybe we need to reevaluate the relative scoring.

https://github.com/golang/go/issues/40599 tracks reevaluating scoring--going to close this issue in favor of that one, with a comment to make sure we fix this problem.


add dashboard to dependencies of ray-default

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Toward fixing #82: make the dashboard a dependency of ray-default (like in the wheels).

Still need to create an alias for ray -> ray-default

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


Add separate documentation for R.__

Addressing #835.
One question I had - would it be worthwhile to remove the mostly identical sections within the docs for R.curry and R.curryN?
Also slightly unsure about the @constant tag.

:herb:

:deciduous_tree: Very nice. Thank you, @mcamac!

This is still not found in the documentation page on the homepage.

Yes, another thing on which I dropped the ball.  This was working until a recent docs build/deploy.
I'll try again to get to this tonight.  See https://github.com/ramda/ramda.github.io/issues/214


Expose the robot logger

My module logs an error message if an environment variable isn't set. However, there's no way to test for that because I can't get access to the robot logger (or it isn't documented). It would be nice if hubot-test-helper would intercept calls to robot.logger.* and allow me to call assertions on logs.

I had this issue, but found it was a problem with how I was accessing or triggering the robot and listener (which creates the response object, which includes the robot, which includes the logger).
Here's a basic working example (coffeescript). Obviously the npm modules used need to be installed. Hope it helps.
logger-test.zip

You can access the robot via room.robot, so you can set spies on the logger methods: sinon.spy(room.robot.logger.error); and then assert the calls.

@alFReD-NSH that's a great idea. However, it seems it's not working (although it could be a bug in my test code) because the logging happens immediately on module initialization. See strugee/hubot-bridge#6.

@strugee I've created hubot-pretend, which was initially a fork of hubot-test-helper but I've added lots of features now, such as easy access to an internal array keeping all the logs produced by robot logger for test assertions. Here's an example test interrogating the logs...
https://github.com/PropertyUX/hubot-pretend/tree/master/test/usage


Update scalafmt-core to 2.7.0

Updates org.scalameta:scalafmt-core from 2.0.1 to 2.7.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-minor

Codecov Report

Merging #112 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #112   +/-   ##
=======================================
  Coverage   60.22%   60.22%
=======================================
  Files          98       98
  Lines        3892     3892
  Branches      141      141
=======================================
  Hits         2344     2344
  Misses       1548     1548

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 c6d9f4e...2445b4e. Read the comment docs.


Hive external table: get partitions from hive metastore failed: java.net.SocketTimeoutException: Read timed out

Steps to reproduce the behavior (Required)
1200partitions, 58columns in hive table.
kerberos authentication.
use cbo planner.
Expected behavior (Required)
Real behavior (Required)
2021-11-02 09:57:02,679 WARN (starrocks-mysql-nio-pool-3|534) [StatisticsCalculator.estimateHiveScanColumns():241] hive table hive_product_test get column failed. error : com.starrocks.common.DdlException: get table level column stats failed: com.starrocks.common.DdlException: get partitions from hive metastore failed: java.net.SocketTimeoutException: Read timed out

StarRocks version (Required)

1.19.0

@gengjun-git please assign to me if no one working on this issue

cc @Ielihs


wrong dotnet template

Regarding "Create an ASP.NET Core web app":
I think this sample is done using a blank web app (ASP.NET Core empty; dotnet new web).

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

ID: edb1fa6c-8433-882f-8b97-4d381f885b1d
Version Independent ID: aad3ec71-363f-3500-8bcd-dc040f71821e
Content: Quickstart to learn how to use Azure SignalR Service
Content Source: articles/azure-signalr/signalr-quickstart-dotnet-core.md
Service: signalr
GitHub Login: @wesmc7777
Microsoft Alias: wesmc

@AlexanderPilhar
Thanks for the feedback! We are currently investigating and will update you shortly.

@wesmc7777 should a blank web app be used instead of mvc?

I believe this tutorial could be done with a blank web app but, there would be some minor differences in the steps when/if you proceed further to the authentication tutorial which is built on top of this tutorial.

I did follow this sample step by step but failed when I came to "Add the web app client interface" - copying index.html file to wwwroot just doesn't have much effect, since /Views/Home/Index.cshtml will be served in a MVC project. So, I switched over to a blank web app and succeeded.

Please reassign to @sffamily. He will determine any necessary follow-up action.

#in-progress

This is an old question, that has been answered a while ago in this thread. The current tutorial can go through.
#please-close


Use the til::enumset type for the SgrSaveRestoreStackOptions enum

Summary of the Pull Request
This replaces the std::bitset for the SgrSaveRestoreStackOptions enum with a til::enumset type, thus avoiding the need to cast the enum to a size_t every time a value is set or tested.
This also fixes an issue with the handling of omitted and zero parameters in the XTPUSHSGR sequence, which are meant to be ignored, and not interpreted as "all".
PR Checklist

[x] Closes #11879
[x] Closes #11883
[x] CLA signed.
[ ] Tests added/passed
[ ] Documentation updated.
[ ] Schema updated.
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments
In addition to dropping all the static_cast operations, the use of the til::enumset also allowed us to get rid of the try/catch handling that was previously required in a couple of places, since the til::enumset operations don't throw.
And to fix the zero parameter handling, we just needed to add an additional lower bound when validating that options are in range - if an option is 0 (All), it will now just be ignored.
Validation Steps Performed
The updated code still passes the existing unit tests, and I've manually confirmed that it fixes the test case for omitted and zero parameters from issue #11883.

Btw, I included the #11883 fix in this PR because it's such a trivial change (https://github.com/microsoft/terminal/pull/11888/commits/15514c98a9483a1e42729704b45dbd20c5957345), but if you prefer to keep the issues separate, I can pull that out into another PR.

I love this. Thanks @j4james!


Footer: Code of Conduct

Code of Conduct (formerly Terms and Conditions) link should point to marmalade.ai content: Navigate to a separate Code of Conduct page on the company website. Content for this page is specified here:
Marmalade > website > Code of Conduct
https://docs.google.com/document/d/1P4m36xHiZEWLmv5l4QDWioBSOq_LclWrMC0DXKVt1Ss/edit?usp=sharing
Notes:

This Code of Content applies to users of the networking application, but we want to make it available on the company website.
There is no need for an Accept or Decline choice on this page. Other pages, e.g. the networking application's Register page will include a link to this company website page along with buttons or checkboxes, where the potential member can accept or reject the policy.

Fixed by pull request #19


Show Waypoints Without Navigation

I have a waypoint list. I want to show it on the map without starting the navigation. I haven't seen this business code in the sample code or documentation. If possible, how can I do this?

I work on Android right now

If it is not possible can we contribute to repo ?

Yes. Please send PR

The embedded Nav view shows the route preview on Build Route but does not return the waypoints. Will be ideal for the Build Route function to return the waypoints if that route that was built

I also need waypoint when I don't define any route (other packages and official doc say it's an annotation). In this way, the user can select a specific place by long pressing, also the user can see certain places that I have defined beforehand and define a rotational navigation to these markers. As far as I understand, in order to do this job, I need to create a new branch from this repo and write the code to provide this job, is it true?

You will fork the repo and create a branch on the fork for the change. Then do a PR when done. The current design has long press to select location.

The embedded Nav view shows the route preview on Build Route but does not return the waypoints. Will be ideal for the Build Route function to return the waypoints if that route that was built

Thanks for your feedback, sorry for one last question. I want insert all waypoints dynamically (these are called from API) when page initialized and these waypoints seem on map without any defined route. Is this feature suitable for current design ?

Stale issue message


test: fix an Xcode 16 issue

Summary
Ticket: none
#517 introduced an Xcode 16 test issue, but that's lower-priority than getting those changes out the door.
Testing
Verified that the test now passes in Xcode 16.

Honestly, I wouldn't recommend it - some of the accessibility label tests that got added while I was stuck on https://github.com/mbta/mobile_app/pull/457 have been failing the whole time, and when I tried to add the right set of .implicitAnyView() calls I was getting the wrong text back, so I'm kinda just hoping ViewInspector eventually figures out a way to not require .implicitAnyView() all over the place.


Use fixed NFS dns name

/ok-to-test
/lgtm
/assign @idvoretskyi

@IronPan apologies to mention you randomly. Does k8s handle the NFS server DNS lookup nicely now? Up until now, you have had to specify the IP of the nfs service, rather than reference the DNS name. For example: https://github.com/kubernetes/minikube/issues/3417.

Still does not work. See
https://github.com/kubernetes/minikube/issues/3417

Still doesn't work with DNS, use Service's Cluster-IP instead.


Volume controls dead on sheldonp

I'm on lineage-18.1-20220925-UNOFFICIAL-sheldon.zip right now with open_gapps-arm-11.0-tvmini-20220215.zip flashed, and I noticed some bugs, viz.

Volume Buttons Dead
Remote needs to be re-paired every boot by holding home button for 10 seconds
Google Assistant/Voice Controls don't work (Sometimes, it works, and sometimes, it just displays the said words on TV, but then freezes, and doesn't actually show the search results. 15 seconds after freezing, it responds with something like "Sorry! something went wrong, try again in a few seconds". Once this happens, all the audio input completely stops and consecutive attemps are greeted by "There was a glitch, try again" )

I've taken logs using wireless debugging and attached them below, and pasted them here aswell
log.txt
EDIT: I cleanflashed lineage-18.1-20220505-UNOFFICIAL-sheldon.zip (vanilla this time) and volume controls still doesn't work.(It worked for someone else I guess on XDA)

I am also having the same issues.

I just saw this, sorry. I'm currently very busy but as soon as I get some free time I'll take a look.


Fix reduction failure in Bazel test

Description
Contains changes from https://github.com/oneapi-src/oneDAL/pull/2769 proposed to fix issue with GPU reduction primitives.

/intelci: run


Report concept set presences that are 0

When using addPresence, we currently lose line items for concept sets that have no presence during the time window.
For table reporting, it's useful to keep these in with N = 0 and Percent = 0.

I will try to fix this but this maybe an artifact of summarizing in SQL. If there is no count for a concept set and I do a GROUP BY, it won't use an item that is not present.
Can add a post-processing step to add a placeholder for concept set with no presence or are below a minimum reportable value (say <5). Agree something should be done for sake of completeness

Agreed, doesn't need to be during processing. But I think it'd be great if in the addPresence functions, we keep a parameter like 'reportZero' and then in the finished categorical result, we get those items.

adding to v1 milestone


Dynamic Mixing fix

as noted by JusperLee in mpariente/asteroid#168.
Added also checks to prevent clipping.

Also thanks to @JusperLee !

Thank you very much for your dynamic mixing @popcornell and speech separation library @mpariente .

Yeah it is very weird. It has been merged to master no ?

yes, it has been merged to master.

Yeah it is very weird. It has been merged to master no ?

I guess you made a new branch from your last state, which was not master, so it contained the three commits you made in the previous branch. As we squash commits to merge into master, the git trees looked different so it rendered the diff.
It's just a matter of branch starting point, no problem.


form-control-sm select box cuts off the bottom side of the text

The letters having bottom side (e.g. g) are cut off on the bottom side in form-control-sm.
https://jsfiddle.net/78c569bf/1/
<select class="form-control form-control-sm custom-select">
  <option value="">The g is cut off</option>
</select>

Related: #24070, #23769, but both are closed

.form-control{-xxxx} and .custom-select can not be used at the same elements.
Form control size options:
<select class="form-control form-control-lg">
  <option>Large select</option>
</select>

Custom select size options:
<select class="custom-select custom-select-lg">
  <option>Large select</option>
</select>

@ysds Indeed, good point! But custom-select-sm doesn't seem to resize the whole box. Perhaps I need to do both?
  <select class="form-control form-control-sm custom-select-sm custom-select">
    <option value="">This g seems to be okay, and select box is smaller, like expected</option>
  </select>

Updated jsfiddle: https://jsfiddle.net/78c569bf/2/

custom-select-sm changes the font size which makes no sense to me. It should align padding as form-control-sm does for inputs. Something is wrong/inconsistent here indeed.
Note that I see no issue in Firefox as it renders the font differently. So, use Chrome for testing.

Your HTML is incorrect. Review our docs again—you don't add .custom-select to inputs with .form-control classes. Custom selects are simply class="custom-select".

@alecpl The behaviors are functioning as they should. Both .form-control-sm and .custom-select-sm will change font-size, padding, and more.

@mdo, <select class="form-control form-control-sm"> and <select class="custom-select custom-select-sm"> end up with different font size. Is it a bug?

@mdo Umm, well of course I wouldn't add .custom-select to inputs. That was just to check different cases.
But, like @alecpl mentioned, I'm confused about the custom-select-sm behavior. I would expect that custom-select-sm would make the select box smaller (along with the font-size), like form-control-sm does it.

@IonicaBizau The point is to not mix form-control and custom-select on a select element.
Anyway, the two examples in @ysds comment produce different font-size. Which is a bug, imo. I'll create a separate ticket.


Deny cookies, creates cookies.

When i press deny cookies, why do it then create a cookie with the status deny, is that not controversial of the button's purpose?
I cant find a way to disable that.

We could use WebStorage instead, but I'm not sure how good support for that is at the moment 🤒


[doc] SSR compatibility of components

HxInputDateRange and HxMultiSelect currently do not support server-side rendering (SSR) form binding
we have components that are non-interactive and compatible with SSR, as well as those that require interactivity

...we should consider highlighting these characteristics in our documentation.

When using HxCheckboxList with no rendermode, I get some odd form element names. Is static ssr not supported for this component?


✨ Add Microsoft Clarity script to RootLayout止

@CodiumAI-Agent /improve

PR Code Suggestions ✨

CategorySuggestion                                                                                ScoreSecurity

Improve security by avoiding the use of dangerouslySetInnerHTML for script injection

Consider using a safer method to inject the Microsoft Clarity script to avoid potential security risks associated with dangerouslySetInnerHTML. You can create a separate script file and import it, or use a library designed to handle external scripts safely.
app/layout.tsx [71-83]
 <Script
   id="clarity-script"
   strategy="afterInteractive"
-  dangerouslySetInnerHTML={{
-    __html: `
-      (function(c,l,a,r,i,t,y){
-          c[a]=c[a]||function(){(c[a].q=c[a].q||[]).push(arguments)};
-          t=l.createElement(r);t.async=1;t.src="https://www.clarity.ms/tag/"+i;
-          y=l.getElementsByTagName(r)[0];y.parentNode.insertBefore(t,y);
-      })(window, document, "clarity", "script", "ofux61lvfu");
-    `,
-  }}
+  src="path/to/safe-clarity-script.js"
 />

Suggestion importance[1-10]: 9
Why: The suggestion addresses a significant security concern by recommending an alternative to dangerouslySetInnerHTML, which can expose the application to cross-site scripting (XSS) attacks. Implementing a safer method for script injection is crucial for maintaining the security integrity of the application.
9


wso2mi 4.1 - Entitlement mediator makes XACML request with an LDAP query in subject-id when using an X509 certificate

Description:

When I used the X509 certificate with the Entitlement mediator, the produced  XACML request did not have the correct subject-id.
<Attributes Category="urn:oasis:names:tc:xacml:1.0:subject-category:access-subject"> <Attribute AttributeId="urn:oasis:names:tc:xacml:1.0:subject:subject-id" IncludeInResult="false"> <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string"> CN=localhost, OU=WSO2, O=WSO2, L=Mountain View, ST=CA, C=US </AttributeValue></Attribute></Attributes>
Apparently in getUserName Method in EntitlementCallbackHandler class, CommonName not return by getSubjectDN().getName() functions correctly.
Steps to reproduce:
I followed applying security to a proxy service article.
My entitlement mediator:
<entitlementService   callbackClass="org.wso2.micro.integrator.identity.entitlement.mediator.callback.X509EntitlementCallbackHandler"  remoteServiceUrl=" https://testdomain.org:9444/services/"   client="basicAuth"   remoteServicePassword="admin"   remoteServiceUserName="admin">
Affected product version:
wso2mi 4.1
Environment details (with versions):

OS: Ubuntu 20.04.4 LTS

It is a mistake. Sorry.


RemoveModal fixes

[x] buttons not spanning entire modal
[x] docs broken
[x] remove close icon

just as a reminder that a template with state management will always be necessary in stories for use for the mdx docs otherwise there's no way to trigger the modal


Fix Release Versioning and SQLite Package

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


add test for spellcheck

The spellCheck attribute is handled differently if it goes through ppx vs set manually. The PR adds a test to show it.

After looking more at the code, I am realizing there is something going on in the current code that conflates both types of props. ReactDOM.createDOMElementVariadic takes in a list of React.JSX.prop:
https://github.com/ml-in-barcelona/server-reason-react/blob/44bb2218ca041c319e982dbd3cf44560c7e90a68/packages/reactDom/src/reactDOM.mli#L37
This is also the type that is returned by domProps function:
https://github.com/ml-in-barcelona/server-reason-react/blob/44bb2218ca041c319e982dbd3cf44560c7e90a68/packages/reactDom/src/reactDOM.mli#L532
The above allows to define createDOMElementVariadic in terms of React.createElement:
https://github.com/ml-in-barcelona/server-reason-react/blob/44bb2218ca041c319e982dbd3cf44560c7e90a68/packages/reactDom/src/reactDOM.ml#L234-L236
I think that the mentioned ReactDOM functions should work with DomProps.props or a different type, and not with the more generic React.JSX.prop. Does that make sense?

React.JSX.props are the values set at runtime
while DomProps.props are the types used by the ppx to add annotations

I'm unsure how to unify both types (It's probably doable)


Implement missing Mongo referential actions emulation

Some emulations are missing. Implement:

[ ] onUpdate: Cascade
[ ] onUpdate: Restrict
[ ] onUpdate: SetNull
[ ] onUpdate: Restrict
[ ] onUpdate: NoAction

The onDelete emulations are also missing hooks into the onUpdate emulation (required for example for SetNull propagation).

Note: This blocks migrate from releasing "no foreign key" mode


@liveblocks/client: Remove private methods and fields

#87

@nvie @ofoucherot I'll push a fix tomorrow to fix the integrations tests


[$500] [Feature Request] Pressing back while writing notes makes text disappear

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to a contacts DM
Click on Private Note
Click on  My Note
Type something (don't save)
press the back button
click on My Note again.
Verify that the draft note you wrote has disappeared

Expected Result:
The note should not disappear
Actual Result:
The note disappears and we see a blank input page
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screencast from 19-09-23 01_16_24 AM IST.webm
Expensify/Expensify Issue URL:
Issue reported by: @Someshwar-Tripathi
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695047398155859
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~012d86d9fa187b7292
Upwork Job ID:<PHONE_NUMBER>588886528
Last Price Increase: 2023-10-02
Automatic offers:

DylanDylann | Contributor | 27097407

Proposal
Please re-state the problem that we are trying to solve in this issue.

[Inconsistency] Pressing back while writing notes makes text disappear

What is the root cause of that problem?

Currently, we do not have the logic "save as draft" for private notes like the message compose, so pressing back while writing notes makes the text disappear

What changes do you think we should make in order to solve the problem?

We can create the logic to save the private notes as draft for each reports as we do with the message composer:

Create the collection PRIVATE_NOTES_DRAFT: 'privateNotesDraft_' to store the draft private note for each report.
Create savePrivateNotesDraft(reportID, note) function to save the draft private note to local storage:

function privateNotesDraft(reportID, note) {
    Onyx.merge(`${ONYXKEYS.COLLECTION.PRIVATE_NOTES_DRAFT}${reportID}`, note);
}

The onChangeText here https://github.com/Expensify/App/blob/76c1559fb3fbee1d07c8f210b522b63edd03920e/src/pages/PrivateNotes/PrivateNotesEditPage.js#L118-L131 will become:

 onChangeText={(text) => {
                                    privateNotesDraft(reportID, text)
                                    setPrivateNote(text)
                                }}

Also, we can consider applying debounce to savePrivateNotesDraft
What alternative solutions did you explore? (Optional)

NA

Taking over this an engineer as I worked on the implementing the private notes feature so I will able to add some value here.

Quick question: What will be the behaviour if we edit multiple private notes? Would a single draft value handle all the edits or for each private notes we create unique draft to store it's value?

Taking over this as an engineer(CME) as I worked on implementing the private notes feature so I will able to add some value here

As I mentioned in my proposal, for each private notes we create a unique draft to store it`s value like what we did with compose

@techievivek what do you think about the above?

@DylanDylann OK, great, that sounds like a plan. Thanks

@robertKozik can you please review the above proposals, thanks.

Proposal
Please re-state the problem that we are trying to solve in this issue.

Feature Save Draft Private Note.

What is the root cause of that problem?

New Feature

What changes do you think we should make in order to solve the problem?

Create an action in Report.js.

function saveReportPrivateNoteDraft(reportID, note, accountID) {
    // Save the draft private note to Onyx
    // Added accountID to the key to make it unique for each user.
    // As there can be multiple users in a report (Group / Admin / Rooms)
    Onyx.merge(`${ONYXKEYS.COLLECTION.REPORT_PRIVATE_NOTE_DRAFT}${reportID}${accountID}`, note);
}

We will use similar implementaion as getDraftComment.ts to get the draft private note.

We will update onChangeText of PrivateNotesEditPage to save the draft private note.

<TextInput
    {...rest}
    onChangeText={(text) => {
        saveReportPrivateNoteDraft(reportID, text, session.accountID);
        setNoteText(text);
    }}
/>

Then we will update the savePrivateNote function to clear the draft private note.

Finally we will update the useState of PrivateNotesEditPage to get the draft private note.

const parser = new ExpensiMark();
+ const draftPrivateNot = useRef(getDraftPrivateNote(report.reportID, route.params.accountID));
const [privateNote, setPrivateNote] = useState(
-    parser.htmlToMarkdown(lodashGet(report, ['privateNotes', route.params.accountID, 'note'], '')).trim()
+    draftPrivateNot.current || parser.htmlToMarkdown(lodashGet(report, ['privateNotes', route.params.accountID, 'note'], '')).trim()
);

What alternative solutions did you explore? (Optional)

N/A

Hi @techievivek! I've checked the existing proposals, and the one from @DylanDylann looks good and it was the first one which described whole process of implementing this new feature, so I think we can go for it. As for the debounce suggestion, I'm all for it - we don't need excessive onyx calls.
🎀 👀 🎀 C+ reviewed

Not overdue, just assigned the job to @DylanDylann

@neonbhai Can you please follow the instructions from the comments here https://github.com/Expensify/App/issues/28599#issuecomment-1752652121, so we automate the process next time for you.

@robertKozik this PR ready for review

@DylanDylann @techievivek @robertKozik 👋🏼 mind taking a look at this: https://github.com/Expensify/App/issues/27596#issuecomment-1768924985
We think the PR here caused an issue with trailing newlines not being trimmed on the My Note page

Thanks for heads up @MariaHCD I've briefy checked our PR and I think as well that our PR reintroduced this problem.
@DylanDylann It looks like this line is flawed https://github.com/Expensify/App/pull/29149/files#r1369162805

Hey! I think the regression pointed before was fixed almost a month ago in this PR https://github.com/Expensify/App/pull/30357.
Automation seems to didn't catch this

@johncschuster Could you help to process this issue?

Sorry, I missed this! I'll process this later today!

Ok, I'm back.
@robertKozik I'm a bit confused – are you saying in this comment that the regression was already fixed?

@johncschuster The regression fixed long time ago

Not overdue, @johncschuster can you please take a look at the above comment.

I've issued payment to @Someshwar-Tripathi. I think we can close this up! Please let me know if I've missed anything!


RPGItems breaking lore in CrazyAuctions!

Hello So I tried to sell a RPGItem in CrazyAuctions and it broke lore... It should add to lore who's selling it, price and more... but it doesn't it probably sets its lore how it should be and it won't allow crazy auctions to add their lore to item in auction. Please fix this it's really important because players won't know the price.

can't reproduce

If you're still having the problem, regenerate the config file. Sometimes new updates changes the file to allow me methods and bug fixes.


Kestrel configuration updates

Fixes #14566
Thanks @khteh! :rocket:

@halter73 @Tratcher ok ... that should be at least closer. Where's it failing?

We'll probably need some wording touches. Plz shoot me your suggestions.

... and do you want to use something besides AddServerHeader? If MS tracks on that in any way, we shouldn't be showing it disabled. We could set a different one ... how about one of these instead ...

MaxRequestBufferSize
ShutdownTimeout
ThreadCount

@halter73 Ready ...
It goes with DisableStringReuse for >=3.0 and kills the entry for <3.0 because those still have the Limits, and the reader will get the point from that when they're looking at the <3.0 examples.

Anything else on this one @Rick-Anderson?


Update FontAwesome to 5.1.0

Hello! Here's my contribution of FontAwesome 5.1.0.
Since FontAwesome 5.x breaks compatibility with 4.x and splits itself into more fonts -- per "style", as they call it -- I kept the "fa" prefix for 4.7 and added 3 new prefixes for 5.x as:

fa5 (regular)
fa5s (solid)
fa5b (brands)

I decided to put in "5", the major version, in the prefix so that in the future when FontAwesome 6.x comes out and potentially breaks backwards glyph compatibility again, we can just add another prefix and call it a day.
I tried to edit as little as possible so I hope all the regular tests are still passing. If not, I will try to fix what I can if I know how.

By the way I noticed the Scrutinizer CI does not seem to report "Completed".
It's stuck "Pending" but when clicking through to the job it says it's done and didn't find new issues.
Not sure what I can do about that, if anything.

I don't know what's wrong with the Appveyor build. It quit abruptly without any errors?

I've noticed icons that should be solid render as regular. I suspect there is a small bug with how the fonts are being loaded and the solid is not getting taken, yet its icon codes and prefix is registered properly.
Any idea where the issue may be?
I have this simple example file:
# -*- coding: utf-8 -*-

# Standard library imports
import sys

# Third party imports
from qtpy import QtCore, QtWidgets
from six import unichr

# Local imports
import qtawesome as qta

class AwesomeExample(QtWidgets.QDialog):

    def __init__(self):
        super(AwesomeExample, self).__init__()

        # Get icons by name.
        fa_icon = qta.icon('fa5s.flag')
        fa_button = QtWidgets.QPushButton(fa_icon, 'Font Awesome!')

        # Render a label with this font
        label1 = QtWidgets.QLabel(unichr(0xf118) + ' ' + 'Regular')
        label1.setFont(qta.font('fa5', 16))
        label2 = QtWidgets.QLabel(unichr(0xf118) + ' ' + 'Solid')
        label2.setFont(qta.font('fa5s', 16))

        # Layout
        vbox = QtWidgets.QVBoxLayout()
        widgets = [fa_button, label1, label2]

        for w in widgets:
            vbox.addWidget(w)

        self.setLayout(vbox)
        self.setWindowTitle('Awesome')
        self.show()

def main():
    app = QtWidgets.QApplication(sys.argv)
    QtCore.QTimer.singleShot(10000, app.exit)
    _ = AwesomeExample()
    sys.exit(app.exec_())

if __name__ == '__main__':
    main()

which renders as:

About the failing AppVeyor builds, it seems to fail specifically with Python 3.5 and not with 3.4 or earlier.
I noticed your master branch's setup.py says:
        # Supported Python versions
        'Programming Language :: Python :: 2',
        'Programming Language :: Python :: 2.6',
        'Programming Language :: Python :: 2.7',
        'Programming Language :: Python :: 3',
        'Programming Language :: Python :: 3.2',
        'Programming Language :: Python :: 3.3',
        'Programming Language :: Python :: 3.4',]

No Python 3.5 there... so why does appveyor.yml try to test 3.5 in line 19 and line 26?
Want me to make a PR to remove 3.5 from the testing matrix?

Looks like fa5 overwrite fa5s, I'll give a look

I have proposed a small fix

@ccordoba12 Shall I rebase over master to get the fixed testing infra? Is that okay or do you prefer I merge the branch into this one?

I think a rebase is easier in this case.

Just rebased and in doing so, squashed some commits for clarity of history.
Looks like the circleci tests succeeded and this time, so did AppVeyor's! :tada:
I'll look into upgrading this from 5.1.0 to 5.2.0 then. Just have to update the ttfs, md5 hashes and dump the icon metadata again.

@darkvertex, this is looking really great, thanks!
However, you need to a shim between the icon names in FontAwesome 4 with the ones in FontAwesome 5. Else Spyder will stop to work.
You can find that work in PR #82.

Okay, I'll look at sorting out those shims while updating to 5.2.0

I rebased to fix the little conflicts from the other PRs that got merged before this one.
I also made the changes to update FA from 5.1.0 to 5.3.1, the very latest and greatest. :man_dancing:
As for the shims, I was wondering if they are truly necessary when you consider that I am not affecting the "fa" namespace at all? As per the PR in its current form, "fa" remains as FontAwesome 4.7 forever. My understanding is that the shims information is for keeping the namespace, using the same font and aliasing the changes from old to the new, but since I'm introducing fa5, fa5s and fa5b yet leaving fa as-is, is it still relevant? (Correct me if I'm wrong.)
I've never used Spyder IDE at all so forgive my poor understanding of its inner workings.

If you would rather I use the shims so as to update the old namespace in-place while introducing the new "solid" and "brands" variants, I could change things like so:
fa5 -> fa
fa5s -> fas
fa5b -> fab
Would you prefer that?

Also, I checked the other PR with the shims.py https://github.com/spyder-ide/qtawesome/blob/614ccbab9b89cba61ed6ab69b2a2bb442cc2baa8/update/shims.py
but I don't understand what I'm supposed to feed update_fa_dict().
Docstring reads:
:param namedict: dictionary with aliases for icons, like Spyder's icon_manager.py

but where do I get that dict from?

As for the shims, I was wondering if they are truly necessary when you consider that I am not affecting the "fa" namespace at all? As per the PR in its current form, "fa" remains as FontAwesome 4.7 forever. My understanding is that the shims information is for keeping the namespace, using the same font and aliasing the changes from old to the new, but since I'm introducing fa5, fa5s and fa5b yet leaving fa as-is, is it still relevant?

If FontAwesome 5 has its own namespace, then I think that's much better. That way Spyder won't loose its current look and feel, and other projects use icons from any version they want.

 Does it look good to you now?

I updated /docs to match README.md improvements.
I think it's all good to go.

Thank you! I'm really happy to see this get merged at last.
When do you plan to release a new version to PyPi?

Amazing!! 😃


path issue for retraining

there seems to be path error when running runner.py in retrain mode:
hajh@hydra:~/Workspace/raisim_ws/ME491_2022_project/raisimGymME491/env/envs/aliengo_jump$ python runner.py --mode retrain --weight data/ME491_final_project/2022-11-23-19-03-43/full_2620.pt
[RAISIM_GYM] Tensorboard session created: http://localhost:6007/
Retraining from the checkpoint: data/ME491_final_project/2022-11-23-19-03-43/full_2620.pt
Traceback (most recent call last):
File "/home/hajh/Workspace/raisim_ws/ME491_2022_project/raisimGymME491/env/envs/aliengo_jump/runner.py", line 81, in
load_param(weight_path, env, actor, critic, ppo.optimizer, saver.data_dir)
File "/home/hajh/Workspace/raisim_ws/ME491_2022_project/raisimGymME491/helper/raisim_gym_helper.py", line 50, in load_param
copyfile(item_to_save, pretrained_data_dir+'/'+item_to_save.rsplit('/', 1)[1])
File "/home/hajh/anaconda3/lib/python3.9/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory: 'data/ME491_final_project/2022-11-23-19-03-43/full_2620.pt'

You have to pass the full path to the pt file, not from data


Kill entire process group spawned by build command for spaClient

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix

What is the current behavior?
Currently, when there is a long-running listener created, such as a WebsocketServer, the port of this listener will be occupied even after build has completed. This leads to EADDRINUSE errors on dev or start after build.
Afaict, this behavior is unique to spaClient because a shell child_process is being spawned that itself spawns the vite process. The proc.kill() command terminates the shell, but the vite subprocess does not receive the signal, which prevents graceful shutdown.
What is the new behavior?
The child_process is spawned as a detached process, which makes it the leader of a process group. For a shutdown, the whole process group is being killed, which will forward SIGTERM to the vite process.
Other information
I've tested this change locally and it fixes the issue. There could be side-effects for Windows users (I am running in WSL2) considering the nature of the detached option.
Without the change:

With the change:

Yeah, tests for windows are failing. 8[

I've updated the code so the Windows build doesn't error anymore. But the way I did it is to just apply this fix conditionally for non-windows environments.
After seeing the Windows tests failing I have installed everything on my Windows host machine and tried to test the change there. The issue is exactly the same as in Linux, i.e. if merged as is, the problem will remain in Windows.
I'm not sure how to move forward from here.

Wild suggestion I am not sure works properly... what if we don't spawn a vite server to generate the index.html and build/use server entry instead? Basically what is done on the astro branch.

No spawn
No waitOn

Quick example of what I mean:
https://github.com/edivados/solid-start/tree/spa-build-mod
Note: The generated index.html required a bit of cleanup. Not so cool...

Removing nodes in head


R!! Cleaned up project structure

This has a better maven structure to it.  The tests are in a test dir.

thanks


chore: remove undefined attributes

Description
remove undefined attributes
Scope

[ ] Patch: Bug Fix
[ ] Minor: New Feature
[ ] Major: Breaking Change

can you share a bit about why this change is required?

@chasestarr Updated the description. Let me know if that makes sense!


UserComment to text

Can explain: how convert "UserComment" from "65,83,67..." to text?

Sorry, I can't. You can read the description for UserComment.


How to rotate page(s) ?

What is (are) command(s) can be used to rotate page(s) of PDF ?

This is not an operation supported by qpdf.

Is there plan to add it ? It is related to structure not to contents as it appear to me (may be I'm wrong).

This is a frequently requested feature, and it's not hard to add. I'll strongly consider adding it for 7.0.0.

Thank you very much !

In qpdf 7.0.0, it will work like this:
qpdf in.pdf out.pdf --rotate=[+|-]angle:page-range
The --rotate option may be repeated. angle may be 90, 180, or 270. If preceded by + or -, the angle is added to or subtracted from the original rotation. Otherwise, the rotation is set.
For example, qpdf in.pdf out.pdf --rotate=+90:2,4,6 --rotate=180:7-9 would rotate pages 2, 4, and 6 clockwise by 90 degrees from whatever rotation they originally had and would force the rotation of pages 7 through 9 to 180.

@jberkenbilt, how can I rotate only the odd or even pages?

@saber7165 From version 9.1.0 on, you can use qpdf in.pdf out.pdf --rotate=90:1-z:even or qpdf in.pdf out.pdf --rotate=90:1-z:odd to specify even or odd pages.

@jberkenbilt
Why do you exclude 0 (without + or -) as angle? That would be useful to force re-set each page's rotation.

And if it's possible to rotate depending on the current rotation, it should be possible to find out the current rotation from each page.
I mean it would be nice if there was a command to list the current rotation of each page, something like:
page 1: <page 1's current angle>
page 2: <page 2's current angle>
page 3: <page 3's current angle>
...

@su-ex Thanks for your comments/questions. It would be possible to implement your suggestions based on the value of /Rotate in the page dictionary, and that might be a useful thing to do, and certainly adding 0 as an allowable value is a good idea. Note that it will only affect the rotation that is done by changing the page metadata. There is no guarantee that the actual page content itself isn't drawn in a rotated fashion, in which case resetting the rotation to 0 won't necessarily make the page look upright. You could extract rotation information for each page using json mode right now with a little code. I'm not sure I would be inclined to add something to the CLI specifically for this purpose, but I could certainly add rotation to the json for pages, which would make it easier to extract. Right now, you'd have to use the pages information to get the page objects and the objects information to get the rotation. If rotation were in the pages object, you could do it with a simple jq command.
Please open a new issue for this suggestion. Comments on a closed issue will not be tracked, and I don't want to reopen the issue because I like to not track multiple things with one issue. I can open the issue myself, but I thought you might prefer to open it yourself. If I don't hear anything, I will open the issue. I'll leave the github email flagged in my inbox as a reminder to do this.

Can we rotate PDF by specific angle such as 30 degree or 45 degreee?

@ilovefreesw Comments posted to closed tickets are likely to be overlooked. At this time, qpdf can't do rotation by other than multiples of 90 degrees because the rotation uses the page metadata, and that's all it supports. I have plans in the relatively near future to add a different way to do transformations on a page that would make this possible, but it is not possible yet, and I'm not 100% certain that I will add that. I already have that specific item (performing arbitrarily matrix transformations) on my to-do list, so you don't need to create a separate issue, but if you want to follow the gory details as I work toward fully designing the feature, you can create a separate issue requesting this feature, and I will tag it.


Update configure deployment credentials include

Updating the deployment credentials include to match https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/app-service-web/app-service-web-get-started-nodejs.md
The current include does not mention the 409 error and password requirements.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

The other option would be to update the app-service-api include to match the app-service one instead of taking the include wholesale. Not sure what the protocol is here.

#sign-off

Hi @bradygaster, Please make the corresponding update in azure-docs-pr. Merging this PR. Thanks.


Create envelope with documents for certain formats failing.

I tried to create envelope using docusign_rest gem, it is failing only for certain MIME types files such as (CSV,png...), but working fine for few things like (JPEG,PDF...)
Version used :  docusign_rest (0.4.4)
File params:
{"file1"=>#<UploadIO:0x00007feac1ec3930
 @content_type="text/csv",
 @original_filename="local.path",
 @local_path="local.path",
 @io=#<StringIO:0x00007feac1ed1cd8
 @base_uri=#<URI::HTTPS https://s3.amazonaws.com/xxx_Sample_CSV%20%282%29%20%281%29.csv?AWSAccessKeyId=xxxxx&Expires=xxx&Signature=xxxxxx>,
 @meta={"x-amz-id-2"=>"xx/xxx+xxx=",
   "x-amz-request-id"=>"xx",
   "date"=>"Thu, 03 Oct 2019 13:13:19 GMT",
   "last-modified"=>"Thu, 03 Oct 2019 13:12:27 GMT",
   "etag"=>"\"xx\"",
   "x-amz-storage-class"=>"REDUCED_REDUNDANCY",
   "x-amz-server-side-encryption"=>"AES256",
   "accept-ranges"=>"bytes",
   "content-type"=>"text/csv",
   "content-length"=>"63",
   "server"=>"AmazonS3"},
 @metas={"x-amz-id-2"=>["xxx/xxx+xx="],
   "x-amz-request-id"=>["xxxx"],
   "date"=>["Thu, 03 Oct 2019 13:13:19 GMT"],
   "last-modified"=>["Thu, 03 Oct 2019 13:12:27 GMT"],
   "etag"=>["\"xx\""],
   "x-amz-storage-class"=>["REDUCED_REDUNDANCY"],
   "x-amz-server-side-encryption"=>["AES256"],
   "accept-ranges"=>["bytes"],
   "content-type"=>["text/csv"],
   "content-length"=>["63"],
   "server"=>["AmazonS3"]},
 @status=["200", "OK"]>,
 @opts={"Content-Disposition"=>"file; documentid=1"}>}

Getting the below Error
{"errorCode"=>"UNABLE_TO_CONVERT_DOCUMENT", "message"=>"System was unable to convert this document to a PDF. Unable to convert Document(local.path) to a PDF. Error: UserId:xxxxxxxxxxxx IPAddress:xxx.xxx.xxxx Source:ApiRESTv2:FileType path is ineligible for conversion."}

Check that you have set the fileExtension attribute of the document object within your Envelopes::create call.
Also:

This type of question is best asked on stackoverflow, using the docusignapi tag
I recommend upgrading to the new version of the SDK gem. See https://rubygems.org/gems/docusign_esign/versions/3.0.0.rc1

Thanks. Figured out the issue, it was because of file processor causing random issues in the old version based on size.
Closing this issue.


Compliance with Spec, as documented in new meltano.com Singer Spec docs

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/91
Originally created by @aaronsteers on 2021-04-06 21:43:13

With https://gitlab.com/meltano/meltano/-/merge_requests/2083 now documenting the Singer Spec in an easier-to-digest fashion, let's apply that page as a test and checklist for SDK completeness.

[x] Metadata

We haven't invested much in discoverable metadata. We should declare these properties automatically when we can.
If and when the SDK cannot automatically implement the full set of discoverable metadata attributes, we should provide easy-to-use controls for the developer to do so.
be sensitive in nature.

[x] Stream selection (TODO, as documented in #7 and resolving in !121)

Additionally, as related to the metadata topic above:

[x] inclusion - Should default to automatic for replication keys and primary keys, available for all others.
[x] selected-by-default - Should default to true

[ ] Should be overridable so the developer can use false when the stream is known to be sensitive in nature

[x] Add logging for metrics types:

[x] http_request_duration (type: timer) - If personally find these messages overly verbose and I often wish I could mute them. Nevertheless, we should at least support emitting them.
[x] record_count (type: counter) - Per the cadence of STATE messages, we can simultaneously emit counter metrics.

Documentation updates:
Once completed, the following documentation pages should also be updated:

[ ] docs/implementation/catalog_metatadata.md: https://sdk.meltano.com/en/latest/implementation/catalog_metadata.html
[x] docs/implementation/metrics.md
[x] docs/implementation/catalog.md: https://sdk.meltano.com/en/latest/implementation/cli.html#input-catalog-catalog

View 25 previous comments from the original issue on GitLab


K8SPXC-758 fix: operator-sdk generate k8s

https://jira.percona.com/browse/K8SPXC-758

Test name
Status

scheduled-backup
passed

big-data
passed

scaling
passed

storage
passed

haproxy
passed

recreate
passed

upgrade-haproxy
passed

self-healing
passed

scaling-proxysql
passed

self-healing-chaos
failed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

demand-backup
passed

monitoring-2-0
passed

operator-self-healing
passed

operator-self-healing-chaos
failed

affinity
passed

smart-update
passed

one-pod
passed

pitr
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1092/commits/3c755e36af7ca470ce5e5b3df18cfc3e807a15eb
image: perconalab/percona-xtradb-cluster-operator:PR-1092-3c755e36

Test name
Status

scheduled-backup
passed

scaling
passed

scaling-proxysql
passed

big-data
passed

haproxy
passed

security-context
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

upgrade-haproxy
passed

recreate
passed

storage
passed

one-pod
passed

restore-to-encrypted-cluster
passed

self-healing
passed

auto-tuning
passed

demand-backup
passed

self-healing-chaos
failed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1092/commits/3c755e36af7ca470ce5e5b3df18cfc3e807a15eb
image: perconalab/percona-xtradb-cluster-operator:PR-1092-3c755e36

Test name
Status

upgrade-haproxy
passed

haproxy
passed

scheduled-backup
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

storage
passed

auto-tuning
passed

self-healing
passed

proxysql-sidecar-res-limits
passed

self-healing-chaos
failed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scaling
passed

recreate
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

demand-backup
passed

pitr
passed

demand-backup-encrypted-with-tls
passed

big-data
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1092/commits/3c755e36af7ca470ce5e5b3df18cfc3e807a15eb
image: perconalab/percona-xtradb-cluster-operator:PR-1092-3c755e36

Test name
Status

scaling
passed

scaling-proxysql
passed

security-context
passed

scheduled-backup
passed

upgrade-haproxy
passed

storage
passed

recreate
passed

self-healing
passed

restore-to-encrypted-cluster
passed

self-healing-chaos
failed

demand-backup
passed

pitr
passed

demand-backup-encrypted-with-tls
passed

haproxy
passed

big-data
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1092/commits/3c755e36af7ca470ce5e5b3df18cfc3e807a15eb
image: perconalab/percona-xtradb-cluster-operator:PR-1092-3c755e36

Test name
Status

scaling
passed

scheduled-backup
passed

haproxy
passed

scaling-proxysql
passed

init-deploy
passed

security-context
passed

limits
passed

monitoring-2-0
passed

big-data
passed

recreate
passed

upgrade-haproxy
passed

storage
passed

affinity
passed

restore-to-encrypted-cluster
passed

self-healing
passed

one-pod
passed

demand-backup
passed

self-healing-chaos
failed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1092/commits/3c755e36af7ca470ce5e5b3df18cfc3e807a15eb
image: perconalab/percona-xtradb-cluster-operator:PR-1092-3c755e36

Test name
Status

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1092/commits/b4f63280c2e085496c65c60669b158efe8b5a997
image: perconalab/percona-xtradb-cluster-operator:PR-1092-b4f63280

Test name
Status

storage
passed

upgrade-haproxy
passed

big-data
failed

self-healing
passed

self-healing-chaos
failed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1092/commits/b4f63280c2e085496c65c60669b158efe8b5a997
image: perconalab/percona-xtradb-cluster-operator:PR-1092-b4f63280

Test name
Status

scheduled-backup
passed

upgrade-haproxy
passed

recreate
passed

big-data
failed

storage
passed

scaling
passed

haproxy
passed

self-healing
passed

self-healing-chaos
passed

upgrade-proxysql
passed

init-deploy
passed

restore-to-encrypted-cluster
failed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

smart-update
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

scaling-proxysql
passed

security-context
passed

upgrade-consistency
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
failed

demand-backup
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1092/commits/b4f63280c2e085496c65c60669b158efe8b5a997
image: perconalab/percona-xtradb-cluster-operator:PR-1092-b4f63280

Test name
Status

scheduled-backup
passed

storage
passed

self-healing
passed

self-healing-chaos
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

operator-self-healing
passed

haproxy
passed

recreate
passed

big-data
passed

operator-self-healing-chaos
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

upgrade-haproxy
passed

limits
passed

monitoring-2-0
passed

scaling
passed

affinity
passed

scaling-proxysql
passed

one-pod
passed

security-context
passed

auto-tuning
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

proxysql-sidecar-res-limits
passed

demand-backup
passed

users
passed

pitr
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1092/commits/b4f63280c2e085496c65c60669b158efe8b5a997
image: perconalab/percona-xtradb-cluster-operator:PR-1092-b4f63280


Update akka-actor to 2.5.16

Updates

com.typesafe.akka:akka-actor
com.typesafe.akka:akka-testkit

from 2.4.20 to 2.5.16.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a nice day!

This project target Akka 2.4 and 2.5. Therefore this PR can not be accepted.


adapt to git sync changes

Thanks, merged and added to the upstream PR with partial clone (you are able to use fetch ~depth:1 :tada:).


api.sendMessage with mentions no longer working

Some time within the last 2 days this function broke, and the API gets HTTP error 500, followed by error 404 when trying to send this message. Attached below is the GitHub sample code in the documentation.
const login = require("facebook-chat-api");

login({email: "EMAIL", password: "PASSWORD"}, (err, api) => {
    if(err) return console.error(err);

    api.listen((err, message) => {
        if (message && message.body) {
            // Getting the actual sender name from ID involves calling
            // `api.getThreadInfo` and `api.getUserInfo`
            api.sendMessage({
                body: 'Hello @Sender! @Sender!',
                mentions: [{
                     tag: '@Sender',
                     id: message.senderID,
                     fromIndex: 9, // Highlight the second occurrence of @Sender
                }],
            }, message.threadID);
        }
    });
});

Seems like we might be missing a new field "profile_xmd[i][type]".  In my tests so far it's always been equal to 'p'.  Do you want to try adding this line and seeing in it helps?
https://github.com/Schmavery/facebook-chat-api/blob/master/src/sendMessage.js#L262-L264

Can confirm that this solves the issue for me.

Awesome!  Any chance you want to submit a PR with that change? :)

Thanks again @7222-SIMON :smile:

Hi, this has stopped working again, although there's no error. 😢

switch (message.body) {
    case 'mention': {
        api.sendMessage({
            body: 'This is @you, and this is @me',
            mentions:
                [{
                    tag: '@you',
                    id: message.senderID,
                },
	        {
	            tag: '@me',
                    id: api.getCurrentUserID()
	        }],
        }, message.threadID);
    }
}

This works with the lastest Schmavery/facebook-chat-api

@kentnek there seems to be a bug when tag is at offset 0
check issue #857 , I created a new PR for it #858.

@kentnek there seems to be a bug when tag is at offset 0
check issue #857 , I created a new PR for it #858.

@shellcxd3 thanks! but I actually stopped using this library altogether as it seemed to cause my accounts to be flagged and banned by Facebook...

@shellcxd3 thanks! but I actually stopped using this library altogether as it seemed to cause my accounts to be flagged and banned by Facebook...


please add gitlab support

🚀 Feature Request
please support gitlab CI/CD
🔈 Motivation
My company uses gitlab
🛰 Alternatives
I cannot move to github
📎 Additional context
I think it is just changing the github actions to gitlab pipelines

Also to add to what a1d4r have said, I have also forked Romain's template and added support to GitLab development. Please check it what I have done so far in #857 if you're interested and feel free to contribute! :slightly_smiling_face:


4.1.0 Beta text wrapping or not aligned.

Hi all Kevin asked me to open a new issue. We have been using the Select2 module for some time now inside Oracle Apex as a plugin. We picked up an issue with IE where you could not add new text with tagging support.
https://github.com/select2/select2/issues/5378
Kevin made a fix for it that I took and added to the code we have inside the plugin for Apex. This seemed to work well. Now we want to upgrade our Oracle Apex platform from 18.1 to 20.1 and we found that version 4.0.7 that I fixed with Kevin's code no longer works.
So I decided to try out 4.1.0 Beta. Now that works fine on all browsers except we get funny text placements and alignments.
Here is 4.0.7 alignment correct

4.1.0 Beta wrong

If you enter a lot of text in 4.0.7 it fits correctly with a scrollbar at the bottom.

and the text inside the box once you press enter.

4.1.0 Beta is a bit of a mess.

Is there a way the layout can be fixed or the old one be made to work on all browsers?
Thanks for a great module.

I cannot reproduce the spacing/margin issue that you are seeing when I am on https://select2.org/tagging in IE11. Make sure you're using the 4.1.0-beta.1 CSS with the 4.1.0-beta.1 JS.
I can reproduce the text within options not wrapping properly though. This is an issue that appears to be consistent within both IE11 and Chrome.
I also also reproduce the scrollbar issue where the text field appears to be extending outside of the container instead of stopping at the end.

I can reproduce the text within options not wrapping properly though. This is an issue that appears to be consistent within both IE11 and Chrome.

Changing the rendered selection to display: inline-block, fixing the new margins that appear, and setting max-width: 100% appears to fix the issue in IE11 and Chrome. The individual choices also need word-wrap: break-word to be applied to them in order to properly break them across lines when they are too long.

I can also reproduce the scrollbar issue where the text field appears to be extending outside of the container instead of stopping at the end.

It looks like the inline search wrapper needs to be set to display: inline-block as well to allow it to be collapsed next to the smaller selections instead of always displaying under them. Setting it to max-width: 100% also allows for the search box to not overflow the container, assuming max-width: 100% is also set on the search box as well.

I marked this as "needs information" because of not being able to reproduce the spacing issue on the documentation website.

OK I uploaded the beta plugin into the Oracle testing cloud.
I am not sure if it is some other javascript code of the old plugin that is creating the space in front.
But here you can see what it is doing no matter what browser you are using.
https://apex.oracle.com/pls/apex/f?p=96087:2:110675964291781:::::

For single selects we currently use an ellipsis to collapse long options down (relying on the title to accurately show the remainder). To remain consistent, that is what is being done for multiple selects as well.
Since I know people like multiple selects to wrap instead of being cut off, here is the CSS that can be used to enable that.
.select2-selection__choice {
    word-wrap: break-word;
    overflow: visible;
    white-space: normal;
    word-break: break-all;
}

I added the CSS but done see any change.

Hi. Any idea when they may be fixed ?

Hi all. We need to have this fixed ASAP. How much would a bounty be to fix this?

@kevin-brown sorry to bug you. Any news on when this will be fixed?

It's been a rough couple of months so I haven't had much time to work on Select2. I am planning on finishing off 4.1.0 and releasing another beta sometime in December, which should hopefully address this issue.

It's been a rough couple of months so I haven't had much time to work on Select2. I am planning on finishing off 4.1.0 and releasing another beta sometime in December, which should hopefully address this issue.

Hi. I understand. Been a hectic year. Not sure have you released the new version with the fix yet?

Hi Kevin.
I have uploaded the latest version. The text not fitting at the back seems to be working but I still have a gap at the front of the box, that gap will let the text then still stick out the back on Chrome.

If I het enter then it fits almost in the box.

Is there somthing in the Apex plugin of framework that is causing this ?
Ypu can have a look here
https://apex.oracle.com/pls/apex/f?p=96087:2

Hi Kevin.
I have uploaded the latest version. The text not fitting at the back seems to be working but I still have a gap at the front of the box, that gap will let the text then still stick out the back on Chrome.

If I het enter then it fits almost in the box.

Is there somthing in the Apex plugin of framework that is causing this ?
Ypu can have a look here
https://apex.oracle.com/pls/apex/f?p=96087:2

OK it is fixed now. You need to add this CSS.
.select2-container ul, .select2-container ol { margin: 0;}

OK it is fixed now. You need to add this CSS.
.select2-container ul, .select2-container ol { margin: 0;}

OK it is fixed now. You need to add this CSS.

Yup, noticed that was the issue when I looked at it. I'll make a PR today to get that CSS added.

OK it is fixed now. You need to add this CSS.

Yup, noticed that was the issue when I looked at it. I'll make a PR today to get that CSS added.


Electron-170 (Monitor position in notification settings)

Added an event to update the monitor selection drop-down whenever a display is added/removed.
@VikasShashidhar , @VishwasShashidhar & @lneir Please review. Thanks

@KiranNiranjan Can you add a code comment explaining what the code does?


Show message when ready

I'm using fable for react native and can't really see when fable is done. Can you please add a ready meesage at end?

Can you please give more detail about how are you using fable (e.g. are you using the --watch option?) and what exactly you would like to see. Right now, you get a message every time a file is compiled and if you're not using the --watch option the process just stops when finished (or calls the postbuild script):
MacbookPro:Fable alfonsogarciacaronunez$ fable samples/browser/pacman/
npm install
Start compilation...
Compiled pacman.fsx at 4:04:52 PM
MacbookPro:Fable alfonsogarciacaronunez$

thx for telling me about --watch.
this is great. :kiss:


When there are no transactions in a ledger show tx count

Show transaction count of 0 when there are no transactions.  Currently it looks like something went wrong with the ledger.
This is typically seen on https://testnet.xrpl.org/.

https://github.com/ripple/explorer/pull/289