Right click on a URL from the Preview tab opens both Context Menu and system browser.

Describe the bug
Right click on a URL from the Preview tab opens both Context Menu and system browser.
To Reproduce
Steps to reproduce the behavior:

Receive any JSON which contains one or more valid HTTP(s) links.
Right click on a highlighted link, assuming to open a context menu.
Observe the context menu opens and then immediately a default system browser opens as well, navigating you to the link's URL.

Expected behavior
I expect only the Context Menu to pop up, and never the browser.
Desktop (please complete the following information):
Version: Insomnia Core 2020.4.2
Release date: 10/21/2020
OS: Windows_NT x64 10.0.19042
Electron: 9.1.1
Node: 12.14.1
V8: <IP_ADDRESS>-electron.0
Architecture: x64
node-libcurl: libcurl/7.69.1-DEV OpenSSL/1.1.1d zlib/1.2.11 WinIDN libssh2/1.9.0_DEV nghttp2/1.40.0

I was not able to reproduce this issue on:
Version: Insomnia Core 2020.4.2
Release date: 24/11/2020
OS: Darwin x64 20.1.0
Electron: 9.1.1
Node: 12.14.1
V8: <IP_ADDRESS>-electron.0
Architecture: x64
node-libcurl: libcurl/7.69.1 OpenSSL/1.1.1g zlib/1.2.11 brotli/1.0.7 libidn2/2.1.1 libssh2/1.9.0 nghttp2/1.41.0
I'll check on Windows too.

Do you need me to record a video?

Do you need me to record a video?

No, I trust you. I'm leaving here some details if someone wants to pick this up.
Sadly, I have no clue what's causing it.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Bump, then.

Hello,
I noticed this issue also and it will be very useful if we can have it resolved.


Change window title when navigating in browser

I updated the title and added navigation to the setup wizard. It will just show the wizard in the step it was left.


Update composer version in the documentation

Update composer version in the documentation because some options in the doc need to be with the development version (exemple: customize the default button look).

I'd rather keep the instructions like that to not encourage people to use an unstable version by default.

@craue Ok I understand, but some options are not available in the current stable version. So we need to precise them. What do you think?

How about just removing the version number and letting Composer choose which version to install depending on the minimum-stability setting. I even more like this approach because I won't have to remember updating this value on each major release. :smile:

@craue Sure It's better to remove the version number and letting Composer choose alone. But we need to precise the minimum version for all options not available in the stable version (with something like this: option available in master branch and not in the development branch). Ok for you?

Considering this explanation I now think it's better to keep the version number to explicitly install the version someone is reading the docs for. So I'm basically :+1: for your initial suggestion, although I'd prefer ~3.0@dev.
This would also solve the issue of feature confusion as someone is reading the docs for a specific version, right?

@Remiii: Are you still working on this?

/ping @Remiii

@craue: I will look that ASAP. Sorry for the delay.

@craue: You got it :sunglasses:

Coverage decreased (-0.78%) to 98.6% when pulling d56129d2a2ee3bb9e301b7774254beb510683917 on Remiii:update-composer-version into 61f0cc7f8c5ec2dacba618fd9ef985e2fba39f48 on craue:master.

Coverage decreased (-0.78%) to 98.6% when pulling d56129d2a2ee3bb9e301b7774254beb510683917 on Remiii:update-composer-version into 61f0cc7f8c5ec2dacba618fd9ef985e2fba39f48 on craue:master.

Really? Now the change for the version number is gone. :scream:
Having ~3.0@dev there would be fine.
Do you still think mentioning in the docs for the master branch that a feature from the master branch is not available in the latest stable version? If someone is using a specific version, he/she should also read the docs for that version, not for the master branch. So I don't see the need to add such notices.

@craue: Ok but a warning like feature not available in all version is better than nothing? What do you think?

I don't see that it's needed at all. When reading the docs for a specific version, you can only read about all the features actually available, not stumble upon the ones added in later versions. But notices like these would have to be removed again when releasing a new version, which might be forgotten.

@craue: If you think is not a good thing you can close the PR.

I thought the main purpose of this PR is to update the version number for the Composer command.

Coverage remained the same at 99.38% when pulling 6a9e6e5da5dfbf90695777cb81ccfff2699ac463 on Remiii:update-composer-version into 61f0cc7f8c5ec2dacba618fd9ef985e2fba39f48 on craue:master.

Coverage remained the same at 99.38% when pulling 6a9e6e5da5dfbf90695777cb81ccfff2699ac463 on Remiii:update-composer-version into 61f0cc7f8c5ec2dacba618fd9ef985e2fba39f48 on craue:master.


Failed to setup when HA reboot if camera is off (zigbee plug)

Hi,
I've a little problem with my camera.
My cam is on a on/off plug, i turn the plug "on" when i'm leaving home.
Problem is, if i've made an HA reboot and the camera was "off", the integration display "failed to setup" and i can't reload it. I have to reboot HA to make it available.
If i reboot HA and the camera is "on", no problem of course.
I imagine this is a normal behavior but is there a way to reload the integration or a service to call or whatever to avoid a reboot to get things work ?
Thanks !
To Reproduce

Plug of the camera on "off" when HA start after a reboot -> The integration display "Failed to setup"
Plug of the camera on "on" -> The integration still on "Failed to setup" and can't be reloaded.

Expected behavior

Plug of the camera on "off" when HA start after a reboot -> The integration display "Failed to setup"
Plug of the camera on "on" -> Service or option to reload the integration to avoid a HA reboot to get things work

Environment:

2021.8.7, RPI4 HAOS, on ssd.
E1 ZOOM
v<IP_ADDRESS>_21040708

The failed to setup is because on startup the integration tries to talk to the camera, the connection times out, and the error is reported. The setup does not really fail, it just failed to setup that camera because it is not present. It should retry after some time though, I think 10 minutes or so. There is no real way to avoid that error in the logs given your situation, you should be able to safely ignore it though.


Improve finding lucene field from field name

Now it's possible to specify <druid-column> instead of <druid-column.lucene-field>.

lucene_query('L_COMMENT.comment', ...) --> lucene_query(L_COMMENT, ...)
sql> select L_COMMENT from lineitem where __time < TIMESTAMP '1992-10-01 00:00:00' AND lucene_query(L_COMMENT, 'breach bo ~3') limit 10;
  [L_COMMENT]
  -----------
  [ even ideas breach slyly above the d]
  [nts wake bl]
  [ blithely even foxes bo]
  [ronic excuses breach final re]
  [brave dependencies bo]
  [according to the bl]
  [kages do affix blithely even, i]
  [ly unusual deposits. bl]
  [ly special deposits breach blith]
  [uickly final accounts sleep blithely abo]
> Retrieved 10 rows in 373 msec
sql>


Feature/java 9 experiment

cobertura seems to have a known conflict with Java 9
added Maven plugin to prevent further dependencies on deprecated APIs in Java 9
fixed issue causing failed builds locally

[x] Check that you pass the basic style checks and unit tests by running mvn clean install

Coverage remained the same at 72.519% when pulling e9d72b2e40771b6ea96d8adf2ef54f650c8c5878 on feature/java_9_experiment into 6fc8f4387a874ddf8fa3f6f374cd5e5a9296f582 on develop.


Absence of the consent-state cookie is not handled correctly

Node/npm version(s):
Node v18.13.0
NPM 8.19.3
Package(s) version(s):
<EMAIL_ADDRESS>
Browser(s) version(s):
Chrome 111.0.5563.64
Description of the issue/feature:
Consent banner does not open when cookie is absent, only when cookie is present, but set to the empty string. The cause of this is the following code (source):
const cookieValueString =
    `; ${document.cookie}`.split(`; ${this.cookieName}=`).pop() ??
    "".split(";").shift();

const cookieValues = cookieValueString ? cookieValueString.split(",") : [];

This code does not work properly if this.cookieName does not occur in document.cookie.
The first template string (`; ${document.cookie}`) can never be the empty string. Even if there are no cookies set at all and document.cookie is the empty string, `; ${document.cookie}` will be '; '. Calling split on a non-empty string will never produce an empty array, as such the following pop call will always return a value. As such anything past the ?? is never executed.
Now, if document.cookie doesn't contain this.cookieName, then the result of pop will just be the entire document.cookie with ;  prepended to it. This is then assumed to be the contents of the cookie and the code assumes a consent decision has already been made.

Thanks for detailed analysis, @diesieben07!
Will publish a new version in the next hours

Thank you for the quick fix, however your solution only solves half of the problem. The code now checks whether document.cookie is completely empty, but this issue also arises (and does still arise in the new version) if there are other cookies set, but the consent state cookie is not present.


Option to pass rootpath to cp.RawModule over using tmp

Description
For profiling it's very common to analyze the PTC or SASS along with the source code, to check which lines translate to which instructions and the time each one takes. So keeping the source file that generated the NVTX can be of interest.
Currently the file is generated automatically and saved in a tmpdir, with default commands in the source
https://github.com/cupy/cupy/blob/49135f8310441be6ad8d7a717f539a63dee79e9d/cupy/cuda/compiler.py#L315C1-L322C66
Request:
Add an argument to the functions compile_using_nvcc and compile_using_nvrtc to pass a root directory, otherwise a temporary one is used, and also update the other functions and modules that interact with it, such as cupy.RawModule
Additional Information
Example of debugging with NCU where source info is not available:

Changing the path to "./" in the functions compile_using_nvrtc and compile_using_nvcc allows to check the source code in Nsight Compute

    if not cache_in_memory:
        with tempfile.TemporaryDirectory() as root_dir:
            cu_path = os.path.join("./", filename)

            with open(cu_path, 'w') as cu_file:
                cu_file.write(source)

            return _compile(source, options, cu_path,
                            name_expressions, log_stream, jitify)

It's already doable without any code change on the CuPy side. I should have sent a PR to document the trick:
Prerequisite for the trick:

CuPy can dump the source to disk if the env var CUPY_CACHE_SAVE_CUDA_SOURCE is set (to 1)
ncu --import-source 1 ... would raise a warning, but as long as -lineinfo is passed at the compile time, the counter data is there, and we just need to load the source code dumped by CuPy.

My steps:

Write a plain script with RawKernel/RawModule (below & in the attachment I called it test_reg_count.py as I was using it to investigate the register usage)
Run ncu with CUPY_CACHE_SAVE_CUDA_SOURCE set:

CUPY_CACHE_SAVE_CUDA_SOURCE=1 /usr/local/cuda-12.1.0/bin/ncu -f -o 123 --set full --import-source 1 -k regex:my python test_reg_count.py

See that the file is cached in the CuPy cache dir

$ ls -l $CUPY_CACHE_DIR/*.cu
-rw-rw-r-- 1 leof leof 155 Jun  6 08:53 /home/leof/.cupy/kernel_cache_cuda_118/3bc1ed3ee19b1e44c4a0b9630489e036f3bd5ae5.cubin.cu

(I happen to have CUPY_CACHE_DIR set; if not, I think the default is ~/.cupy/kernel_cache.)
4. If profiling remotely, make sure the ncu output and the dumped source code are transferred back to local.
5. Load the ncu output in the GUI. When switching to the Source page, it’d show that the source code is not found. Click “Resolve” and load the CuPy source code. Done.
test_reg_count.py.txt (GitHub does not allow me to upload .py files...)

Thanks for the help and clarification! It would be great to see this in the official docs on profiling with cupy


When switching from landscape mode to portrait, the screen remains half blank

Application only work in portscape mode, we need to disable landscape mode.

@sibilrahman want to work on this issue? I think its just have to add two or three words in android/app/src/main/AndroidManifest.xml as per the docs.
Related stackoverflow answer:- https://stackoverflow.com/a/57413087/14781260

resolved on #78


[Catalog View] Add a 'Grid View' as an alternative to the table on the catalog page. (RFC #9947)

Hey, I just made a Pull Request!

Added a toggle between Grid/Table views (default to the existing Table view)

Added Grid view

Added the ability to search on title/name in the grid view

Added the ability to filter on tags from grid view cards

Added the ability to define icons for cards

Added some new tests to cover some of the new features (TODO: more to do here)

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[~] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

I'm just an adopter of Backstage in early stages.
In my opinion this is not very helpful for a majority of adopters. May be helpful if the adopter only have a handful of services and a few libraries because the cards are pretty big and will get you to need search to find anything almost right away.

I've reformulated this into a standalone plugin here so that it becomes an opt-in feature rather than always occupying space. https://github.com/backstage/backstage/pull/11464


Invoke-Webrequest -Method Head fails to follow redirect and returns error 404 instead of 301

Hello,
Invoke-Webrequest -Method Head seems to fail to follow redirect and returns error 404 instead of 301.
Strangely enough, it succeeds after same URL has been opened in browser or without option -Method Head.
Steps to reproduce
(I don't like to put a real life URL here, but I find it important to be able to reproduce exactly as seen)
Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -Method Head -MaximumRedirection 10

Invoke-WebRequest : Le serveur distant a retourné une erreur : (404) Introuvable.
Au caractère Ligne:1 : 1
+ Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/fl ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation : (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

=> Sniffer indicates 301 Permanently moved to https://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg
Same issue when trying to open directly HTTPS uri that HTTP uri is redirected to:
Invoke-WebRequest -Uri https://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -Method Head -MaximumRedirection 10

Invoke-WebRequest : Le serveur distant a retourné une erreur : (404) Introuvable.
Au caractère Ligne:1 : 1
+ Invoke-WebRequest -Uri https://www.fondationlouisvuitton.fr/content/f ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation : (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Now opening succeeds if -Method Head is not specified:
Invoke-WebRequest -Uri https://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg

StatusCode        : 200
StatusDescription : OK
Content           : {255, 216, 255, 224...}
RawContent        : HTTP/1.1 200 OK
                    X-Content-Type-Options: nosniff
                    X-Frame-Options: SAMEORIGIN
                    Connection: keep-alive
                    Strict-Transport-Security: max-age=86400
                    Content-Length: 223987
                    Cache-Control: max-age=7185
                    Co...
Headers           : {[X-Content-Type-Options, nosniff], [X-Frame-Options, SAMEORIGIN], [Connection, keep-alive], [Strict-Transport-Security, max-age=86400]...}
RawContentLength  : 223987

And if I try again specifying -Method Head, it now works !
Invoke-WebRequest -Uri https://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -Method Head -MaximumRedirection 10

StatusCode        : 200
StatusDescription : OK
Content           : {}
RawContent        : HTTP/1.1 200 OK
                    X-Content-Type-Options: nosniff
                    X-Frame-Options: SAMEORIGIN
                    Connection: keep-alive
                    Strict-Transport-Security: max-age=86400
                    Content-Length: 223987
                    Cache-Control: max-age=7175
                    Co...
Headers           : {[X-Content-Type-Options, nosniff], [X-Frame-Options, SAMEORIGIN], [Connection, keep-alive], [Strict-Transport-Security, max-age=86400]...}
RawContentLength  : 0

Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -Method Head -MaximumRedirection 10

StatusCode        : 200
StatusDescription : OK
Content           : {}
RawContent        : HTTP/1.1 200 OK
                    X-Content-Type-Options: nosniff
                    X-Frame-Options: SAMEORIGIN
                    Connection: keep-alive
                    Strict-Transport-Security: max-age=86400
                    Content-Length: 223987
                    Cache-Control: max-age=5896
                    Co...
Headers           : {[X-Content-Type-Options, nosniff], [X-Frame-Options, SAMEORIGIN], [Connection, keep-alive], [Strict-Transport-Security, max-age=86400]...}
RawContentLength  : 0

Please note that opening the URL is a browser succeeds, and also seem to make the invoke-webrequest -Method Head behave properly...
Expected behavior
Either succeed and return statuscode 301, or follow redirection and return statuscode 200, depending on value of -MaximumRedirection:
Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -Method Head -MaximumRedirection 10

StatusCode        : 200
StatusDescription : OK
Content           : {}
RawContent        : HTTP/1.1 200 OK
                    X-Content-Type-Options: nosniff
                    X-Frame-Options: SAMEORIGIN
                    Connection: keep-alive
                    Strict-Transport-Security: max-age=86400
                    Content-Length: 223987
                    Cache-Control: max-age=5896
                    Co...
Headers           : {[X-Content-Type-Options, nosniff], [X-Frame-Options, SAMEORIGIN], [Connection, keep-alive], [Strict-Transport-Security, max-age=86400]...}
RawContentLength  : 0

Actual behavior
Fails with error 404 whatever the value of -MaximumRedirection.
Succeeds if the URI is opened once with browser or with Invoke-Webrequest without specifying -Method Head.
Environment data
Name                           Value
----                           -----
PSVersion                      5.1.16299.248
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.16299.248
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

BTW, before anyone points me to upgrading to v6.0 core, please note that I have the same issue with v6.0 core:
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.2
PSEdition                      Core
GitCommitId                    v6.0.2
OS                             Microsoft Windows 10.0.16299
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Error 404 while trying to open the URI while specifying -Method Head:
Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -Method Head -MaximumRedirection 10

Invoke-WebRequest : Response status code does not indicate success: 404 (Not Found).
At line:1 char:1
+ Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/fl ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (Method: HEAD, R...rShell/6.0.2
}:HttpRequestMessage) [Invoke-WebRequest], HttpResponseException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Success while trying to open the URI without specifying -Method Head:
Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -MaximumRedirection 10

StatusCode        : 200
StatusDescription : OK
Content           : {255, 216, 255, 224...}
RawContent        : HTTP/1.1 200 OK
                    Cache-Control: max-age=7192
                    Connection: close
                    Date: Mon, 22 Oct 2018 09:58:50 GMT
                    Server: Apache
                    X-Content-Type-Options: nosniff
                    X-Frame-Options: SAMEORIGIN
                    Strict-Transport-Sec...
Headers           : {[Cache-Control, System.String[]], [Connection, System.String[]], [Date, System.String[]], [Server, System.String[]]...}
RawContentLength  : 223987
RelationLink      : {}

Then success again while trying to open the URI while specifying -Method Head:
Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-pa
rreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -Method Head -MaximumRedirection 10

StatusCode        : 200
StatusDescription : OK
Content           : {}
RawContent        : HTTP/1.1 200 OK
                    Cache-Control: max-age=7189
                    Connection: close
                    Date: Mon, 22 Oct 2018 09:58:53 GMT
                    Server: Apache
                    X-Content-Type-Options: nosniff
                    X-Frame-Options: SAMEORIGIN
                    Strict-Transport-Sec...
Headers           : {[Cache-Control, System.String[]], [Connection, System.String[]], [Date, System.String[]], [Server, System.String[]]...}
RawContentLength  : 0
RelationLink      : {}

Please also take a moment to verify that it does not work with the latest version of PowerShell Core. I believe the updates to the web cmdlet happened after 6.0.2, if I'm not mistaken. 😄

Thanks for your suggestion.
Upgraded PSH core to v6.1, and got exactly the same behaviour:
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.1.0
PSEdition                      Core
GitCommitId                    6.1.0
OS                             Microsoft Windows 10.0.16299
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -Method Head -MaximumRedirection 10
Invoke-WebRequest : Response status code does not indicate success: 404 (Not Found).
At line:1 char:1
+ Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/fl ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (Method: HEAD, R...rShell/6.1.0
}:HttpRequestMessage) [Invoke-WebRequest], HttpResponseException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -MaximumRedirection 10

StatusCode        : 200
StatusDescription : OK
Content           : {255, 216, 255, 224...}
RawContent        : HTTP/1.1 200 OK
                    Server: Apache
                    X-Content-Type-Options: nosniff
                    X-Frame-Options: SAMEORIGIN
                    Cache-Control: max-age=1061
                    Date: Mon, 22 Oct 2018 11:40:27 GMT
                    Connection: keep-alive
                    Strict-Transpor...
Headers           : {[Server, System.String[]], [X-Content-Type-Options, System.String[]], [X-Frame-Options,
                    System.String[]], [Cache-Control, System.String[]]...}
RawContentLength  : 223987
RelationLink      : {}

Invoke-WebRequest -Uri http://www.fondationlouisvuitton.fr/content/flvinternet/en/expositions/hors-les-murs/philippe-parreno-marilyn/_jcr_content/image.flvcrop.2048.5000.jpeg -Method Head -MaximumRedirection 10

StatusCode        : 200
StatusDescription : OK
Content           : {}
RawContent        : HTTP/1.1 200 OK
                    Server: Apache
                    X-Content-Type-Options: nosniff
                    X-Frame-Options: SAMEORIGIN
                    Cache-Control: max-age=1057
                    Date: Mon, 22 Oct 2018 11:40:31 GMT
                    Connection: keep-alive
                    Strict-Transpor...
Headers           : {[Server, System.String[]], [X-Content-Type-Options, System.String[]], [X-Frame-Options,
                    System.String[]], [Cache-Control, System.String[]]...}
RawContentLength  : 0
RelationLink      : {}

This problem appears to be with the web server you are trying to reach, not with Invoke-WebRequest. I cannot reproduce this with other sites. You will need to contact the owners of that web server for support on accessing their site. They may have ant-scraping or robot protections in place that are being triggered by the request. HEAD is not universally supported by all web servers and implementations may vary. The web server may also be filtering based on your IP, User-Agent, and session tokens. These things require additional changes to your calls in order to properly obtain data from some sites.
$uri = 'https://httpbin.org/redirect-to?status_code=301&url=https://httpbin.org/get'
Invoke-WebRequest -method HEAD -Uri  $uri -MaximumRedirection 10

Thanks for your comment. The good news is that this website is ours. The bad news is that we are not aware of any exotic configuration that would prevent this.
We will however look into this more deeply. It could also be a side effect of the CDN.
However, I still find it strange that it would work without the -Method Head, and that it would work with the -Method Head once it has worked once without. Maybe this could point to a cache effect (and to the CDN).
I will keep you posted on my finding so that we can hopefully conclude it is not a PSH bug.

@FLVSD CDN could definitely cause this behavior along with application firewalls. If you are able to run the query directly against your servers instead of the CDN you can at least rule out yor server config.
CDN's are complex beasts and they are primarily written to work with web browsers. They often have speciqal configurations for curl and wget, but Invoke-WebRequest is not as well known. You may be able to get around CDN issue by using the -UserAgent and supplying a User-Gent header for curl or wget.

Thanks again for your suggestion.
We have good support from our CDN, and I have opened a support ticket with them to plan a diagnostics session. They will also be in a position to give us some highlights on how our servers react, so I guess they should be able to point us in the right direction.


"Agreement" button for negotiation coalitions

The "Three-Way Coalition" game being used here is interesting, as only 2 out of 3 players need to form a "coalition" in order for an agreement to hold, and the third person doesn't need to agree at all. However, it might be nice to give the third person a 30-second grace period after 2 of the 3 agree, in order to have a last-ditch persuasive effort before the negotiation officially ends.
Therefore, in an ideal world:

There should be some button that allows participants to formally register their agreement
Only 2 out of 3 participants need to be able to click on it to move on
Once clicked, a 30-second timer counts down, and the third person can try to persuade the others to "un-click" their buttons
If at least one of the 2 individuals "un-clicks" the button, then all three participants go back to the negotiation table
Otherwise, if the last-ditch persuasive effort is unsuccessful, the negotiation ends and everyone moves to the post-questions.

This is probably a lot of engineering, so I'll have to brainstorm some workarounds, using the existing infrastructure, for simulating a discussion in which only 2 out of 3 need to agree.

A good way to implement this would be to make the submit button visibility conditional on a threshold of participants having selected something else.  For example, we can already use something like this to only show a submit button once everyone has said they are ready:
          - type: submitButton
            desc: shown when all are ready
            conditions:
              - promptName: individualReady
                comparator: equal
                position: all
                value: yes

Currently, position can take integer values corresponding to a particular other position (eg, 1) or all to indicate that all players have individually agreed, or shared if the condition depends on a shared input.
We could change the conditional rendering such that when some number of positions (rather than all positions) have said 'yes' we render the submit button. We could use a few keywords in place of "all", such as "majority", "two-thirds", "one-third", "all-but-one" without having to add any extra parameters, but it could get confusing.
I'll have to think about how this could be implemented.


swift 4 !!!!!!!

FYI, a quick fix to support Swift 4 would be to add @objcMembers before the GDPerformanceMonitor class definition:
@objcMembers public class GDPerformanceMonitor: NSObject { ... }

Please, check the lates version. It should be fixed.


Implement Web fallback when cordova is not available

Now if cordova is not available the plugin throws the plugin_not_installed error.
Since this plugin has a small API, it would be easy to add a proper web fallback for browsers:
  getPromisifiedLocalStorage() {
    return {
        setItem: (key, value) => {
          return new Promise( (resolve, reject) => {
            try {
              window.localStorage.setItem(key, this.encodePayload(value));
              resolve();
            } catch (error) {
              reject(error);
            }
          });
        },
        getItem: (key) => {
          return new Promise( (resolve, reject) => {
            try {
              const result = window.localStorage.getItem(key);
              resolve(this.decodePayload(result));
            } catch (error) {
              reject(error);
            }
          });
        },
        remove: (key) => {
          return new Promise( (resolve, reject) => {
            try {
              window.localStorage.removeItem(key);
              resolve();
            } catch (error) {
              reject(error);
            }
          });
        },
        clear: () => {
          return new Promise( (resolve, reject) => {
            try {
              window.localStorage.clear();
              resolve();
            } catch (error) {
              reject(error);
            }
          });
        },
      }

Note: This implementation is Promise based as I use Ionic-Native, but its pretty straight forward to make  rewrite it into callbacks.

I'm not familiar with promises in native JS. Is this native JS?
If so, please make u pull request and I'l be happy to merge it.
Thanks

Here is an implementation with callbacks:
  getCallbackifiedLocalStorage() {
    return {
        setItem: function setItem(key, value, success, error) {
          try {
            window.localStorage.setItem(key, this.encodePayload(value));
            succes();
          } catch (error) {
            error(error);
          }
        },
        getItem: function getItem(key, success, error) {
          try {
            var result = window.localStorage.getItem(key);
            success(this.decodePayload(result));
          } catch (error) {
            error(error);
          }
        },
        remove: function remove(key, success, error) {
          try {
            window.localStorage.removeItem(key);
            success();
          } catch (error) {
            error(error);
          }
        },
        clear: function clear(success, error) {
          try {
            window.localStorage.clear();
            success();
          } catch (error) {
            error(error);
          }
        },
       encodePayload: function encodePayload(payload) {
         try {
           payload = JSON.stringify(payload);
         } catch(error) { }
           return payload.toString();
       },
       decodePayload: function decodePayload(payload) {
         try {
           payload = JSON.parse(payload);
         } catch(error) { }
           return payload;
       }
     }

If so, please make a pull request and I'l be happy to merge it.

Okay, I will test it and make one

Hmm, just did a quick look on the source code and it seems it already has local storage as a fallback. So maybe the Ionic Native wrapper messes up something, I will give it a proper look later (probably on the weekend)

@NoNameProvided @GillesC  Sorry, for the late reply.
What I had done was there is a delegate that falls back to localstorage based on the storageSupportAnalyse function's response to StorageHandle at line 27.
If even localstorage isn't available we fail gracefully with a console.log (my comment :) at the code). No detailed error message with trace that's all.

Let us reopen, if there is something we can work on here though. I'm closing for now. Thanks!


Source Control: Select all/none repositories

When opening vscode in a directory - all of the repos in that directory are not always added to the source control window - this tends to happen with directories that have many (10,20,30) repos.
So initially I think it would be a good idea to do this by default (if it doesn't already - needs checking for large number of repos).
More importantly - I currently have to navigate to Source Control > ... > View and Sort > Repositories > and then select a repo I want to add. Frustratingly the nested windows don't stay open or allow multiple selections! So for 30/40 repos these steps have to be repeated for each repo.
Even worse this'll reset in a couple days time so have to repeat all over again!!
If there has been user selections/deselections or suspected non vscode detection outlined above - then would be extremely useful to provide the user with an option to Source Control > ... > View and Sort > Repositories > 'select all' or 'select none' to quickly add or clear repos.!

Do you know about the SOURCE CONTROL REPOSITORIES view? You can enable this by right-clicking on the titlebar of the SOURCE CONTROL view container, then select/deselect repos in the list it displays.

Aha, I did not! Well.. I did, but since forgotten about.
So I can now see if you click on a repo in SOURCE CONTROL REPOSITORIES then the SOURCE CONTROL window displays your selection - single, multi-click or ctrl/cmd + a for all. That last bit being the behaviour I needed.
So that's not a bad workaround - but I remember why I'd forgotten about it now - I couldn't understand the use of having both window views - for example when using SOURCE VIEW - it's essentially the same as SOURCE CONTROL REPOSITORIES but you have the additional functionality of stage control, commit authoring etc.
So.. that said - and now I understand it a bit more - would it make more sense to drop the SOURCE CONTROL REPOSITORIES view and make the SOURCE VIEW show all repos by default, with streamlined selection? That would seem a cleaner and more intuitive UX to me but would be interested to see what other people use/think?


hidden arguments?

Is there a way to add an argument, but not make it show up in the help message? (Useful in implementing backdoor developer-only testing features.)

Is https://hackage.haskell.org/package/cmdargs-0.10.20/docs/System-Console-CmdArgs-Implicit.html#v:ignore what you are after?

Thanks Neil!
Unfortunately that's not quite what I want. I still want this to be a valid parameter to the program, just not displayed in the "help" output.
I've found this stack-overflow question that describes the issue https://stackoverflow.com/questions/33199324/hidden-arguments-with-cmdargs
But the accepted solution seems quite hackish and it dates back to 2015. So, I'm wondering if there's a better way to do the same.

Unfortunately nothing better available I'm afraid. I can't think of a better way than that.

Thanks! I'll close this ticket; but feel free to re-open it if you want to implement something! It's definitely a nice-to-have. Much appreciated.

Let's leave open to add - it's pretty hacky as it stands now...

In case this helps anyone else, I found a workaround that sort of works. You first do:
allNames :: [String]
allNames = concatMap flagNames $ modeFlags defaultOptions

where defaultOptions is the record you construct for arguments. This grabs all the flag names.  Then, do a preprocessing step and check all "flag-like" arguments to be in this list before calling cmdArgs itself. If you find anything outside, you can do a more detailed analysis as needed.
Rather hackish, but it does do the trick for my use case. I'd like to hear if anyone has a better idea that doesn't require mocking with cmdArgs itself.


Hanging download_feature because of 401 response

Describe the bug
After some time downloading, the download hangs inside download_feature. I am not sure if the hang is deterministic, but it happens several times per week.
With #83 on top of main, here is a partial log with correct timestamps:
time=2024-02-25T04:59:48 level=INFO msg="Download started"
<614 successful downloads>
time=2024-02-25T13:02:48 level=INFO msg="Download started"
time=2024-02-25T13:02:49 level=WARNING msg="Status code 401, retrying.." file=download.py:109
time=2024-02-25T13:03:58 level=WARNING msg="Status code 401, retrying.." file=download.py:109
<loop continues with 401 status>

So it's hanging in the loop at https://github.com/SDFIdk/CDSETool/blob/8385e3a82d0915f472458955608ec40aadb0e082/src/cdsetool/download.py#L103
This is a different issue from #60 since that gives an exception.
Steps to reproduce
Pseudo code for what produces the log:
options = {... Credentials(user, password) ...}
for product in list_of_many_products:
    download_feature(product, options)

Expected behavior
Some kind of recovery, or returning a failure, or throwing an exception.
Environment

OS: Ubuntu 22.04
Package version: 0.2.3, but also CDSETool main branch with #83 on top.
Python version: 3.10

This happened again last night using main branch just before the proxy PR.
time=2024-03-07T22:27:51 level=INFO msg="Download started"
time=2024-03-07T22:27:52 level=WARNING msg="Status code 401, retrying.." file=download.py:104
time=2024-03-07T22:29:07 level=WARNING msg="Status code 401, retrying.." file=download.py:104
time=2024-03-07T22:30:08 level=WARNING msg="Status code 401, retrying.." file=download.py:104

@pedep a hanging job is a bit of an issue since that doesn't self-heal, any ideas?

I thought the monitor had something to do with things, but they always seem to be cleaned up properly for me.

I think i have an idea as to why the session will not refresh despite retrying for multiple seconds
# [..snip..]
    with _get_monitor(options).status() as status:
        status.set_filename(filename)

        session = _get_credentials(options).get_session() # a session is acquired, which may be seconds from expiring
# [..snip..]
        response = _retry_backoff(url, session, options)
# [..snip..]

def _retry_backoff(url, session, options):
    response = session.get(url, stream=True) # by this point the session may already have gone bad
    # the while-loop contains no way of refreshing the session
    # so the stale access token is used indefinitely
    while response.status_code != 200:
        options["logger"].warning(f"Status code {response.status_code}, retrying..")
        time.sleep(60 * (1 + (random.random() / 4)))
        response = session.get(url, stream=True)

    return response

Yes, hasn't that been obvious from the log in the issue?

Yes, thats what clued me in. I didnt have time to look at it until now.
If you knew that already, why spend time on a sidetrack like #100 ?

There are no comments in the code, but I assume there must have been a good reason to ignore every response code except 200 in the first place.
A hanging download requires a bunch of logic to monitor output and figure out if the python process should be killed, and killing the python process requires even further logic to restore other things to how they were before the download started, and then the python process needs to be started again. A download that returns a failure can be checked inside the python process and immediately retried, and the second download seems to work.

This morning I stopped getting 401 and started getting intermittent 404. It's possible that is just a disguised 401 that reveals less information, so I will check the logs next week and report back.

I have 404 and 500 in my logs now, so I guess they changed the response from 401 to 404.

This has been fixed for a long time.


Change data_format default to None

Set data_format default of Conv2DTranspose to None so that it is consistent with K.image_data_format().
Issue #5974

Duplicated with #5976


Loosen requirements.txt version pins

Installing this package currently takes an extremely long amount of time (20+ minutes) if you want a specific
version of a package. For example, say torch==2.1.
The error that happens at the commandline is:
INFO: pip is looking at multiple versions of peft to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of openai to determine which version is compatible with other requirements. This could take a while.

It looks like all of the dependencies in the requirements.txt file have an upper bound, which
seems unnecessary and is likely slowing down the resolution times.
We should remove the upper bounds for all the packages except for those that introduce breaking changes.
For those introducing breaking changes, we should instead create an issue to handle them and then have a seprate PR
which upgrades the dependency.

This is sort of related to https://github.com/instructlab/dev-docs/issues/77. It would be good to have a general policy for the version ranges of python dependencies.
When we add dependabot support for python dependencies, we may be then able to use == versions and let dependabot manage them for us.

We are currently using it to manage GitHub actions versions.

When we add dependabot support for python dependencies, we may be then able to use == versions and let dependabot manage them for us.

Pinning specific packages with == is considered to be a bad practice as it can lead to Python uninstalling incompatible packages, as @dhellmann pointed out in his message here:
https://github.com/instructlab/training/issues/34#issuecomment-2176071856


How to setup the SAP Vora developer edition virtual machine

sudo rm -rf /var/local/vora/scheduler
when executing above lines I get several device or resource busy message.
I used this in the context to access the URL IPADD:19000. This is not loading in chrome or edge either.

I just noticed the vora services are shown as exited not starting or started when I execute systemctl command for vora*. Kindly suggest and see snip attached for your recommendation in regards to the issue.

Why did you delete everything in the scheduler directory?
As to your second comment, is this what you see after deleting the files from the scheduler directory?
If so, you would be better off to start with a fresh VM and not remove those files.
--Jason


Added alternative to binding icons manually.

Added a simple example block of code you can add to your app.component.html to trick the script into importing icons that it might otherwise miss.

This is an interesting guide. Thanks, I will merge it!


Current version of webpack-dev-server fails on build.

i after run yarn webpack received error in console.
Error is:
Error: Cannot find module 'webpack-cli/bin/config-yargs'
Require stack:
- D:\PersianDnn\Dnn.Platform\Dnn.AdminExperience\Extensions\Content\Dnn.PersonaBar.Extensions\WebApps\Roles.Web\node_modules\webpack-dev-server\bin\webpack-dev-server.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:713:15)
    at Function.Module._load (internal/modules/cjs/loader.js:618:27)
    at Module.require (internal/modules/cjs/loader.js:771:19)
    at require (internal/modules/cjs/helpers.js:68:18)
    at Object.<anonymous> (D:\PersianDnn\Dnn.Platform\Dnn.AdminExperience\Extensions\Content\Dnn.PersonaBar.Extensions\WebApps\Roles.Web\node_modules\webpack-dev-server\bin\webpack-dev-server.js:84:1)
    at Module._compile (internal/modules/cjs/loader.js:868:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:879:10)
    at Module.load (internal/modules/cjs/loader.js:731:32)
    at Function.Module._load (internal/modules/cjs/loader.js:644:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:931:10) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'D:\\PersianDnn\\Dnn.Platform\\Dnn.AdminExperience\\Extensions\\Content\\Dnn.PersonaBar.Extensions\\WebApps\\Roles.Web\\node_modules\\webpack-dev-server\\bin\\webpack-dev-server.js'
  ]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Steps:

Did you run yarn install first ?

Oh, sorry, just saw the screenshot after the comment...

Ok, can you got back to the root workspace /Dnn.AdminExperience/ and run yarn install then go into the subfolder and try yarn webpack again...

Ok, I will try and announce the result

Ok, can you got back to the root workspace /Dnn.AdminExperience/ and run yarn install then go into the subfolder and try yarn webpack again...

this doesn't work, but i copy webpack-cli from AdminLogs.Web\node_modules\webpack-cli into WebApps\Roles.Web\node_modules worked

I was able to reproduce the issue, looks like this is an issue with webpack and we need to update it's version. After upgrading webpack to 4.31.0 I was able to build without this error, however I did not do extensive testing with this upgrade... I am changing the title of the issue for that reason.

There was a huge build reorganization done since this issue was last visited. I don't think this is a problem anymore with the new build instructions. I am closing this issue for that reason.


[Bug]: Climbers Trail Extract Still Requires RR/Paracord/NoArmour

Discord Username
harry53
What happened?
I have 'ignoreCliffRequirements' set to true, but the Climbers Trail on Shoreline still requires the normal Cliff Extract requirements.
With debug turned on I can see that Lighthouse and Reserve both state "Alpinist on MAP has had its paracord, red rebel, and armored rig requirements removed." in the logs. There does not appear to be one for Shoreline though. I've put this in the server log part below.
If you need anything else just @ me on the SPT discord, or send me a PM.
I will also note that I haven't yet had a chance to test the Reserve or Lighthouse cliff extracts.
SPT Version
3.8.0
Server Log
OpenExtracts: Crossroads on Customs has been updated to allow all entry points: Boiler Tanks,Customs.
OpenExtracts: Smuggler's Boat on Customs has been updated to allow all entry points: Boiler Tanks,Customs.
OpenExtracts: RUAF Roadblock on Customs has been updated to allow all entry points: Boiler Tanks,Customs.
OpenExtracts: ZB-1012 on Customs has been updated to allow all entry points: Boiler Tanks,Customs.
OpenExtracts: ZB-1011 on Customs has been updated to allow all entry points: Boiler Tanks,Customs.
OpenExtracts: Trailer Park on Customs has been updated to allow all entry points: Boiler Tanks,Customs.
OpenExtracts: Old Gas Station on Customs has been updated to allow all entry points: Boiler Tanks,Customs.
OpenExtracts: Dorms V-Ex on Customs has been updated to allow all entry points: Boiler Tanks,Customs.
OpenExtracts: Dorms V-Ex on Customs has had its extraction time updated from 60 seconds to 30 seconds.
OpenExtracts: EXFIL_ZB013 on Customs has been updated to allow all entry points: Boiler Tanks,Customs.
OpenExtracts: NW Exfil on Interchange has been updated to allow all entry points: MallSE,MallNW.
OpenExtracts: SE Exfil on Interchange has been updated to allow all entry points: MallSE,MallNW.
OpenExtracts: PP Exfil on Interchange has had its extraction time updated from 60 seconds to 30 seconds.
OpenExtracts: Hole Exfill on Interchange has had its backpack requirement removed.
OpenExtracts: Interchange Cooperation on Interchange has been converted to a payment extract.
OpenExtracts: lab_Vent on Laboratory has had its backpack requirement removed.
OpenExtracts: Alpinist_light on Lighthouse has had its paracord, red rebel, and armored rig requirements removed.
OpenExtracts: tunnel_shared on Lighthouse has been converted to a payment extract.
OpenExtracts: Nothern_Checkpoint on Lighthouse has been updated to allow all entry points: Tunnel,North.
OpenExtracts: V-Ex_light on Lighthouse has had its extraction time updated from 60 seconds to 30 seconds.
OpenExtracts: Alpinist on Reserve has had its paracord, red rebel, and armored rig requirements removed.
OpenExtracts: EXFIL_ScavCooperation on Reserve has been converted to a payment extract.
OpenExtracts: EXFIL_vent on Reserve has had its backpack requirement removed.
OpenExtracts: Unity_free_exit on Ground Zero has been updated to allow all entry points: east,west.
OpenExtracts: Sandbox_VExit on Ground Zero has been updated to allow all entry points: east,west.
OpenExtracts: Sandbox_VExit on Ground Zero has had its extraction time updated from 60 seconds to 30 seconds.
OpenExtracts: Sniper_exit on Ground Zero has been updated to allow all entry points: east,west.
OpenExtracts: Scav_coop_exit on Ground Zero has been updated to allow all entry points: east,west.
OpenExtracts: Scav_coop_exit on Ground Zero has been converted to a payment extract.
OpenExtracts: Nakatani_stairs_free_exit on Ground Zero has been updated to allow all entry points: east,west.
OpenExtracts: Tunnel on Shoreline has been updated to allow all entry points: Riverside,Village.
OpenExtracts: Rock Passage on Shoreline has had its chance to be enabled changed from 0% to 50%.
OpenExtracts: CCP Temporary on Shoreline has been updated to allow all entry points: Riverside,Village.
OpenExtracts: Road to Customs on Shoreline has been updated to allow all entry points: Riverside,Village.
OpenExtracts: Road_at_railbridge on Shoreline has been updated to allow all entry points: Riverside,Village.
OpenExtracts: Shorl_V-Ex on Shoreline has had its extraction time updated from 60 seconds to 30 seconds.
OpenExtracts: Smugglers_Trail_coop on Shoreline has been converted to a payment extract.
OpenExtracts: E1 on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: E2 on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: E3 on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: E4 on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: E5 on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: E6 on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: E7_car on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: E7_car on Streets of Tarkov has had its extraction time updated from 60 seconds to 30 seconds.
OpenExtracts: E8_yard on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: E9_sniper on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: Exit_E10_coop on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: Exit_E10_coop on Streets of Tarkov has been converted to a payment extract.
OpenExtracts: E7 on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: E8 on Streets of Tarkov has been updated to allow all entry points: E6_1,E1_2,E2_3,E3_4,E4_5,E5_6.
OpenExtracts: ZB-016 on Woods has been updated to allow all entry points: House,Old Station.
OpenExtracts: Outskirts on Woods has been updated to allow all entry points: House,Old Station.
OpenExtracts: UN Roadblock on Woods has been updated to allow all entry points: House,Old Station.
OpenExtracts: RUAF Gate on Woods has been updated to allow all entry points: House,Old Station.
OpenExtracts: ZB-014 on Woods has been updated to allow all entry points: House,Old Station.
OpenExtracts: South V-Ex on Woods has had its extraction time updated from 60 seconds to 30 seconds.
OpenExtracts: Factory Gate on Woods has been converted to a payment extract.
OpenExtracts: un-sec on Woods has been updated to allow all entry points: House,Old Station.
OpenExtracts: Extracts have successfully adjusted according to the configuration.

Just would like to add that I managed to test the Reserve cliff extract and it worked fine :)

This should be resolved in release v1.4.1. Thank you!


How to refresh certificates - for server and client?

Hello,
On the /certificates page we have a preview of the certificates. There is an Expiration date after which the client/server will probably not have access to the VPN. I'm referring to these dates:

How do you refresh these certificates? Is it possible to do it somehow without breaking the current server<->client connection e.g. by swapping .ovpn config on client and server?

for the clients you can do with renew feature.
Server itself (CA) is not possible to renew, the only way is to create CA with infinite expiration time (lets say 99 years) or generate new CA.


There is no options for "Foxit reader"

Hi,
"Always on top" feature is greyed out for "Foxit reader" (a lightweight alternative to adobe acrobat reader, I believe many engineers are using that). I use 64 bit version, https://www.foxitsoftware.com/pdf-reader/.

That "Minimize to system tray" option comes from foxit itself, menu entries from MenuTools are greyed out

A little bit of spam: I jumped to https://github.com/AlexanderPro/SmartSystemMenu while your project was "on hold" (cannot remember exact reason, maybe x64 applications was not handled in "MenuTools"..?). Maybe you will will be interested in features it has to offer. The show stopper for that project is that it does not support google chrome, so I am switching back to menu tools to tryout.
Thank you for making a must have addon for windows OS, great work :)

@WhiteChairFromIkea
Have you tried vitaminj's workaround here?

Thnak you for quick responce. It is a different situations here: issue you mention is about MenuTools  injected menu items not showing at all for specific apps. I can see these menus in my case, but they are greyed out.
Also, shift + RMB combination does not throw menu at all for foxit in the taskbar (but it does show it for metro apps, as per workaround). I guess foxit is yet another type of application, not covered in earlier issue.

I'll try to check it out today.
Ps: I'm using Sumatra PDF, way lighter for reading.
On Tue, Dec 22, 2020, 09:08 WhiteChairFromIkea<EMAIL_ADDRESS>wrote:

Thnak you for quick responce. It is a different situations here: issue you
mention is about MenuTools injected menu items not showing at all for
specific apps. I can see these menus in my case, but they are greyed out
.
Also, shift + RMB combination does not throw menu at all for foxit in the
taskbar (but it does show it for metro apps, as per workaround). I guess
foxit is yet another type of application, not covered in earlier issue
https://github.com/navossoc/MenuTools/issues/2#issuecomment-428595266.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/navossoc/MenuTools/issues/7#issuecomment-749508859,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASX56SWMD44GOZDCWTWRVDSWCD2PANCNFSM4VFNWD3Q
.

Yep, installed sumatra right after issue post 👍
On Tue, Dec 22, 2020, 14:49 Rafael Cossovan<EMAIL_ADDRESS>wrote:

I'll try to check it out today.
Ps: I'm using Sumatra PDF, way lighter for reading.
On Tue, Dec 22, 2020, 09:08 WhiteChairFromIkea<EMAIL_ADDRESS>wrote:

Thnak you for quick responce. It is a different situations here: issue
you
mention is about MenuTools injected menu items not showing at all for
specific apps. I can see these menus in my case, but they are greyed
out
.
Also, shift + RMB combination does not throw menu at all for foxit in the
taskbar (but it does show it for metro apps, as per workaround). I guess
foxit is yet another type of application, not covered in earlier issue
https://github.com/navossoc/MenuTools/issues/2#issuecomment-428595266.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/navossoc/MenuTools/issues/7#issuecomment-749508859,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AASX56SWMD44GOZDCWTWRVDSWCD2PANCNFSM4VFNWD3Q
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/navossoc/MenuTools/issues/7#issuecomment-749524194,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALDCHBNCPOTR2QLKPVFGH7TSWCIWHANCNFSM4VFNWD3Q
.


bst artifact pull: 'artifact not found' is success

See original issue on GitLab
In GitLab by [Gitlab user @aevri] on Mar 21, 2019, 17:50
Summary
If you try to bst artifact pull an artifact that the server does not have, the command exits with code 0 and prints 'SUCCESS'.
It seems that it should exit with non-zero and print less positive text about the operation.
Steps to reproduce
git clone https://gitlab.com/buildstream/buildstream.git
cd buildstream/doc/examples/running-commands

REPO=$(mktemp -d)
bst-artifact-server "$REPO" -p 8888 &

cat >>project.conf <<EOF

artifacts:
    url: http://localhost:8888
    push: false
EOF

bst artifact pull hello.bst

What is the current bug behavior?
(bst) running-commands$ bst artifact pull hello.bst
[--:--:--][5a1a024a][ pull:hello.bst                     ] START   running-commands/hello/5a1a024a-pull.84519.log
[--:--:--][5a1a024a][ pull:hello.bst                     ] STATUS  Pulling artifact 5a1a024a <- http://localhost:8888
[--:--:--][5a1a024a][ pull:hello.bst                     ] INFO    Remote (http://localhost:8888) does not have 5a1a024a cached
[00:00:00][5a1a024a][ pull:hello.bst                     ] SKIPPED Pull
[00:00:00][        ][ main:core activity                 ] SUCCESS Pull

Pipeline Summary
  Total:      3
  Session:    1
  Pull Queue: processed 0, skipped 1, failed 0

(bst) running-commands$ echo $?
0

What is the expected correct behavior?
Something more like:
(bst) running-commands$ bst artifact pull hello.bst
[--:--:--][5a1a024a][ pull:hello.bst                     ] START   running-commands/hello/5a1a024a-pull.84519.log
[--:--:--][5a1a024a][ pull:hello.bst                     ] STATUS  Pulling artifact 5a1a024a <- http://localhost:8888
[--:--:--][5a1a024a][ pull:hello.bst                     ] INFO    Remote (http://localhost:8888) does not have 5a1a024a cached
[00:00:00][5a1a024a][ pull:hello.bst                     ] SKIPPED Pull
[00:00:00][        ][ main:core activity                 ] FAILURE Pull

Pipeline Summary
  Total:      3
  Session:    1
  Pull Queue: processed 0, skipped 0, failed 1

Remote (http://localhost:8888) does not have 5a1a024a (hello.bst) cached

(bst) running-commands$ echo $?
1

In GitLab by [Gitlab user @aevri] on Mar 21, 2019, 17:50
[Gitlab user @cs]-shadow has expressed interest in this.

In GitLab by [Gitlab user @tristanvb] on Nov 5, 2020, 07:19
I'm not sure I agree with this, it is not necessarily a failure if the remote has no artifact to pull, and there is no error message and error log to observe for an artifact which was successfully observed to not be present.
That said, it might make sense to have other messaging after the scheduler session completes informing the user a bit more clearly than the fact that the task was skipped. It would certainly be wildly inconsistent to say pulling a non-existing artifact is a failed status rather than a skipped status.
Note your suggestion itself contains an inconsistency:
[--:--:--][5a1a024a][ pull:hello.bst                     ] START   running-commands/hello/5a1a024a-pull.84519.log
[--:--:--][5a1a024a][ pull:hello.bst                     ] STATUS  Pulling artifact 5a1a024a <- http://localhost:8888
[--:--:--][5a1a024a][ pull:hello.bst                     ] INFO    Remote (http://localhost:8888) does not have 5a1a024a cached
[00:00:00][5a1a024a][ pull:hello.bst                     ] SKIPPED Pull
[00:00:00][        ][ main:core activity                 ] FAILURE Pull

Pipeline Summary
  Total:      3
  Session:    1
  Pull Queue: processed 0, skipped 0, failed 1

Here you are suggesting that the overall session status be considered a failure if the pull task was skipped, which is a bit more plausible.
However, you are also suggesting that we pretend that the pull task was failed rather than skipped, here we can clearly see the pull task SKIPPED in the logs, but instead shows up as failed in the pipeline summary at the end.


configure

please add comands for configurations and execution

please add comands for configurations and execution

what do you mean?

Reopen when active


Hide / Toggle on Scroll

Hi, is it possible if the side panel is open, and one scrolls the main content (not scrolling within the menu), it toggles and hides the menu ?..
thanks

@WPThemer this would definitely be possible, but is not a current built in feature. I'm going to add a "feature request" label to this question. Thanks!

Thanks @ascott1


Add metabase chart

The helm chart for Metabase

@unguiculus I've just made a few changes as your request, sorry for my mistake 😄

/ok-to-test

Good work, thanks. Don' be sorry. :wink:


Sorting: explained

Is your feature request related to a problem?
I wanted to open a new issue that we are missing Sorting by Popular, but then I found that it was already opened by @exezbcz. This issue:

#5335

I think the options we have in sorting can be confusing.

Unpopular = with the least activity (I think)
Recently interacted = is the opposite of unpopular (?) - with recent activity (BUT not MY activity, recently interacted in general?)

Describe the solution you would like
Can we have that pop-up hovering window (idk what you call it) that we have for example for minting?

With a very short text that explains the options?

Old/new - these maybe don't need explanations
Unpopular = with the least activity, least interacted ones
Recently interacted = NFTs with the most interactions
Least/most supply = also shortly explained

Describe alternatives you have considered
Better naming - I already wrote my idea in #5335 but let me copy-paste it here:
I would use the same naming for unpopular/recently interactive options. Ideas:  Unpopular/Popular. Least activity/Most activity. Recent activity/Least activity
Screenshots
No response
Are there opened related issues?
No response

I also noticed that we have different names for Old First/New first for collection and Oldest/Recently created for NFTs (items). Basically, it's the same thing... but in one case we are searching in collections and in another case in Items. It would be good to have the same naming.

Can we have that pop-up hovering window (idk what you call it) that we have for example for minting?
With a very short text that explains the options?
* Old/new - these maybe don't need explanations

* Unpopular = with the least activity, least interacted ones

* Recently interacted = NFTs with the most interactions

* Least/most supply = also shortly explained

I don't think it's a good idea to add tooltip as it would add some noise on the screen.

Describe alternatives you have considered
Better naming - I already wrote my idea in #5335 but let me copy-paste it here:
I would use the same naming for unpopular/recently interactive options. Ideas: Unpopular/Popular. Least activity/Most activity. Recent activity/Least activity

Feel free to list what you want to see instead. maybe @exezbcz can help with better naming.
Here's some example from popular marketplace:

Hmm, I would not put the tooltip there, agree with roileo that it would be than redundant noise.
How is unpopular defined? least interacted right?
what about this?

i would also switch the recently created to newest? If we would like to add recently listed, we can then divide it again

Recently interacted = most interacted in short time horizon no? At Least for us.
I would also switch the order of price
not sure about the serial number? Is it useful?


Update platemaps for screen

Update platemaps for screen
In this PR, updated plate maps are added to the metadata module, and new example figures are generated:

One for the layout of a full plate
One for the layout of the last plate (plate 11) which is a partial plate (uses less wells)

@axiomcura Thanks for the review! I will merge now!


[BUG] Compilation Error with Device Defender Windows Simulator Project

Describe the bug
A concise description of what the bug is.
Compilation error "xOutput': is not a member of 'MetricsType_t". The actual definition of this type in tcp_netstat.h is "XOutput". Uppercase "X" instead of the current "x"
Target

Development board:  Windows Simulator
IDE and version: Visual Studio 2019

Host

Host OS: Windows 10

To Reproduce
Unable to build the demo project

Hi @vanithar75,
This build error has been resolved, I will close this ticket as it is resolved. Please re-open it should you have any further issues.
Thanks,
Carl


Fixed wrong value in exception message when Xmx exceeds allowed limit

Thanks for making this fix.

LGTM

LGTM


Add empty theme, example theme, or custom theme options to slate theme

Timber was great way to learn how to build Shopify themes by example. It was not a great way to get started building a new theme because it was very opinionated and required heavy modification if you wanted to use an alternative approach, such as a different style library.
The default theme included with Slate now is an okay resource to learn by example and an okay starting point. It contains limited examples of things you need to know when developing a theme, but nothing extra or optional like Timber. It contains some JS and SCSS that might help you get started, or it might get in the way and you will rip it out.
In combination with https://github.com/Shopify/slate/issues/252, Slate has the potential to allow for all the educational and knowledge sharing benefits of Timber while also allowing the developers to start a project with nothing in the way.
I propose that the following options be available when creating a new theme:

Empty Theme (default) - A theme with the absolute minimum to be compatible with Slate-tools and uploaded to Shopify. A developer should not need to remove anything to this theme, only add.
Example Theme - An updated, Slate compatible version of Timber which purpose is to educate developers by example. Developers are welcome to use these examples in their own themes, but are encouraged to expand upon them to reduce duplicated experiences across themes.
Custom Theme - As mentioned https://github.com/Shopify/slate/issues/252, a developer can specify their own custom, Slate-compatible theme to start with. For example, a developer could start with an 'Empty Theme', copy what they like from the Example Theme, add any additional boilerplate they want, and use this as a custom starting point for all their themes.

This has been implemented in Slate v1.x branch with the introduction of create-slate-theme


Issue with cipher suites/signature algorithm on my zephyr based TLS client

Hi,
I'm working on a TLS client based on echo-client sample.
I have been debugging my zephyr based TLS client for 1 week because I have an issue with it. During the handshake between my client (zephyr based) and my server ("$ sudo openssl s_server -accept 443 -cert serv_cert.crt -key serv_key.key -tls1_2")  a handshake failure happens.
". 404796A5FF770000:error:0A000076:SSL routines:tls_choose_sigalg:no suitable signature algorithm:../ssl/t1_lib.c:3293:
shutting down SSL
CONNECTION CLOSED"
On WIreshark my client hello looks like this :

I printed the ciphers suite available on my server : "$ openssl ciphers -s -tls1_2"
ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES256-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA
There are no common ciphersuites between the previous one and the client hello. How could I add more ciphersuite to my board, particularly the one that "openssl ciphers" command prints ? Does the ciphersuite list depends on the board we use ?
I tried to modify my overlay-tls.conf by adding "CONFIG_MBEDTLS_KEY_EXCHANGE_ALL_ENABLED" but nothing happened.
Thank you in advance for your help !

Does the ciphersuite list depends on the board we use ?

The list of available cipersuites on the Zephyr side depends on the mbedTLS configuration, see:
https://github.com/zephyrproject-rtos/zephyr/blob/main/modules/mbedtls/Kconfig.tls-generic
You can enable more or less everything with the following configs:
CONFIG_MBEDTLS_KEY_EXCHANGE_ALL_ENABLED=y
CONFIG_MBEDTLS_CIPHER_ALL_ENABLED=y
CONFIG_MBEDTLS_ECP_ALL_ENABLED=y
CONFIG_MBEDTLS_HASH_ALL_ENABLED=y
CONFIG_MBEDTLS_CMAC=y
CONFIG_MBEDTLS_GENPRIME_ENABLED=y
CONFIG_MBEDTLS_HMAC_DRBG_ENABLED=y
CONFIG_MBEDTLS_ECDH_C=y
CONFIG_MBEDTLS_ECDSA_C=y
CONFIG_MBEDTLS_ECJPAKE_C=y
CONFIG_MBEDTLS_ECP_C=y

But it's usually better to select those algorithms from the link above that your project really needs.
Converting this into discussion, since it's not really a bug.


Update ethadapter for pre-relase candidate 3.0.0-rc28

Update ethadapter for pre-release candidate 3.0.0-rc28


Add jon, JSON parser for the fishshell.

jon is a JSON parser. It will transform a JSON stream into a flat /slash/slash <TAB> "value"-like array; easier to parse in the shell. jon speaks fish and is made for fishshell.

Cool, thanks -- out of curiosity, does jon support validation? Or how exactly does it relate to JSON Schema?

Currently it stops and highlights whatever syntax error there was if invalid JSON is detected.

Invalid JSON or invalid JSON Schema or an instance that's invalid under a
schema? Your project seems to be a JSON parser, not JSON Schema related. Or
am I missing it, I only took a quick look, so apologies if I did.
Sent from my mobile device. Any typos are intentional.
On Feb 4, 2015 8:11 AM, "Jorge Bucaran"<EMAIL_ADDRESS>wrote:

Currently it stops and highlights whatever syntax error there was if
invalid JSON is detected.
—
Reply to this email directly or view it on GitHub
https://github.com/json-schema/JSON-Schema-Test-Suite/pull/82#issuecomment-72851644
.

It is a JSON parser. I am using the tests files in this repository to test it. What am I confusing JSON and JSON schema? There are no types in fish or rather, everything is either a symbol (string) or a list of symbols.

Ah. Yes. JSON and JSON Schema are quite different things. This test suite
tests JSON Schema. If you're using it to test a JSON parser I suspect your
parser only works in a very simple sense, in that the tests are in fact a
particular form of JSON.
Sent from my mobile device. Any typos are intentional.
On Feb 4, 2015 8:32 AM, "Jorge Bucaran"<EMAIL_ADDRESS>wrote:

It is a JSON parser. I am using the tests files in this repository to test
it. What am I confusing JSON and JSON schema? There are no types in fish
or rather, everything is either a symbol (string) or a list of symbols.
—
Reply to this email directly or view it on GitHub
https://github.com/json-schema/JSON-Schema-Test-Suite/pull/82#issuecomment-72854328
.

I will think about how to validate a schema from fishshell, but in the meantime I would simply like to use your tests to proof jon runs.

OK, I mean if you find them useful, go for it :). I'm gonna revert the commit though if that's OK, the list here is meant to demonstrate people using the test suite for making sure they have conforming / working validation libraries.

By all means, I should've been more careful! :smile:


automatic_authentication is not working

Describe the bug
Construct a client which also set automatic_authentication to true (default). It will not automatically auth.
To Reproduce
Repo: https://github.com/reyamir/rust-nostr-debug.git
let keys: Keys = Keys::generate();
let signer = NostrSigner::Keys(keys);

// Config
let opts = Options::new().automatic_authentication(true);

// Setup nostr client
let client = ClientBuilder::default().signer(signer).opts(opts).build();

client.add_relay("wss://relay.damus.io").await?;
client.connect().await;

// Add nip-17 relay
client.add_relay("wss://auth.nostr1.com").await?;
client.connect_relay("wss://auth.nostr1.com").await?;

// Send private message
let receiver =
    PublicKey::from_bech32("npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445")
        .unwrap();
let message = "Hello world";

match client
    .send_private_msg_to(["wss://auth.nostr1.com"], receiver, message, None)
    .await
{
    Ok(output) => println!("Ok: {:?}", output),
    Err(e) => println!("Err: {}", e),
}

Ok(())

The result is Err: event not published: auth-required: you must auth
Expected behavior
Automatically auth when add new relay.
Build environment

Library: nostr-sdk
Language: Rust
Language version: 1.78
Tag/commit: 79b84f618d2e339f13c763f697c6fd56d8062aec
OS+version: macOS 14

As temporary workaround: subscribe with autoclosing option using a filter that get nothing, like Filter::new().kind(Kind::TextNote).limit(0) (or use get_events_of with thay filter).
The issue shouldn't be the authentication but the fact that AUTH message is sent after you send the first event (or REQ). So, after the authentication, the event should be re-sent (same issue of few days ago with REQ).
I'll try to search a way to automatically re-send the event if the error is related to authentication.

Yo thank you, your workaround help me resolve the weird bug in my chat app 😅

Fixed in PR #667


[oozie] Create and call function to await HDFS Data Nodes

Some users are experiencing errors when init actions begin running before dfs has come online.  This patch pauses before the first call to dfs in order to avoid this race condition.
This patch is intended as the fix for #1077

/gcbrun

The pause needs to happen before the initialization actions are launched.  We can stagger the cluster node startup with a script such as the following.
cjac@cjac11:~/src/team/cloud-support-tses/products/dataproc/dataproc-repro$ cat init/delay-masters-startup.sh                    #!/bin/bash

set -x

readonly ROLE="$(/usr/share/google/get_metadata_value attributes/dataproc-role)"
if [[ "${ROLE}" != 'Master' ]]; then set +x; exit 0; fi

node_number=$(echo ${HOSTNAME} | perl -ne '/-m-(\d+)/; print $1')
delay_seconds=$((${node_number} * 150))
sleep ${delay_seconds}s

NOW=$(date +"%F-%T")
echo "instance #${node_number} (${HOSTNAME}) proceeds at ${NOW}" | tee /var/log/delay-masters.log

set +x

Once the agent has launched and kicks off the init actions, the patched script should be capable of running even if the HDFS store does not come online ever.

/gcbrun

/gcbrun

I'm going to close this CL and open a new one.  Somehow we got one of nvliyuan's ephemeral email addresses as a contributor.  This was likely due to me rebasing my changes on a different branch.

continued in #1089


Printing Problems

Having a variety of issues with printing and created a test case to help explain it, with some PDF samples.  Using the v4 beta as can be seen in my print-demo.txt (rename to .html and you can view this in any browser).  Designed to be a test case which spans a number of pages for ease of debugging.
print-demo.txt
-SOME- of these can be fixed with uncommenting the media print stylesheet in the heading, but this causes other display problems of course with various browsers.
Firefox v55:
Mostly Blank page 2
Three full flex boxes
Three cut off and missing headers
print-demo firefox.pdf
Chrome v61 (printing from full width):
Correctly displays the six flex boxes
Stops after the first of the 3 cards
Does not display two of the boxes
Does not display the footer at all
print-demo chrome.pdf
Chrome v61 printing from a narrow width (by resizing the browser very narrow and then printing the page):
Seems to do everything correctly
print-demo chrome (narrow).pdf

Isn't this the same as #23864?

Not "the same".  May share similarities.
#23864 refers to printing inconsistencies between two browsers which would suggest a minor tweak to one browser to get the page to print right.  Moreover, it uses the Bootstrap homepage as the test which is not a "simplified" test case.
This bug refers to NONE of the browsers printing "properly" and provides a test case HTML file with basic elements configured in a common way.  No browser (other than, for some reason a very narrow Chrome when you hit the print button) prints properly.
This bugs refers to an overall problem with printing styles of Bootstrap pages across all browsers.

Still seems like the same issue to me, but whatever.

Hi michael krieger,
Were you able to find a fix for the print issue above?
Thanks


On state change: Uncaught TypeError: Cannot read property 'props' of null

Whenever I search my table (or update its state in any way), I get this error, and the table breaks.
Uncaught TypeError: Cannot read property 'props' of null on line 48 on on TableColumn's children.

Chrome dev console breakpoint set on line 48, showing the value of `children` immediately before the error.

Fo some reason the if statement on line 47 seems to think typeof "251" === "object", and it immediately errors on the next line when it tries to call "251".props, which of course doesn't exist since "251" is a string.  I've tried checking the type in console as well typeof children >> "string", I'm stumped.  Any ideas?

Code to reproduce:

export class CustomSortTable extends React.Component {
    render() {
        var {items, fields} = this.props;
        return <BootstrapTable data={items} search={true}>
            {fields.map((field, idx) =>
                <TableHeaderColumn
                    dataField={field.id}
                    dataSort={true}
                    key={field.id}
                    isKey={field.isKey || false}>
                    {field.name}
                </TableHeaderColumn>)}
        </BootstrapTable>
    }
};

var fields = [
    {id: 'id', name: 'ID', 'isKey': true},
    {id: 'my_value', name: 'My Value'},
]

var items = [{
     'id': '251',
     'my_value': true,
}, ...]

<CustomSortTable items={items} fields={fields}/>

Thanks for bug report, I'll check this out after my vacation, need some time :)

新年快乐！Enjoy your vacation  :), no rush.

happy new year :)

@pirate, which version of react-bootstrap-table did you used? and are you sure the code will produce the error? because I can't reproduce this followed by your example code

react-bootstrap-table 1.5.0, react 0.14.6.  I'll try a few things, and if they don't work I'll see if I can write some more reproducible code than this snippet.

@pirate, I've published v1.5.1 and you can try it again :)

Appears to be fixed, thanks!

@pirate, Thank you. I am very grateful. I've no idea about accepting any donations:) Actually, I need more contributor to help this project become better :)
Thanks :+1:


flow-router-ssr : call server method in route action from server : cannot find data in collection if not subscribed

There are some collections that I do not wish to publish (like Meteor.users, or internal stats) and some datas I want to get in straight json and not as cursors (for pagination purpose mostly). So I want to get them from a Meteor.call. No subscription and no reactivity.
It works client side, but not server side.
To reproduce, clone the repo of the hello react meteor application : https://github.com/arunoda/hello-react-meteor. Then in the router.jsx, change that code :
action: function() {
  ReactLayout.render(BlogLayout, {
    content: <PostList />
  });
}

To that one :
action: function() {
  Meteor.call('getPost', function (err, res) {
    console.log('err : ', err);
    console.log('res : ', res);
    ReactLayout.render(BlogLayout, {
      content: <PostList />
    });
  });
}

And add the method to retrieve a post :
 if( Meteor.server )
    Meteor.methods({
      getPost(){
        return Posts.findOne();
      }
    });

You can now find the retrieved post in the client and server console. It works.
But now, comment the subscription :
//this.register('posts', Meteor.subscribe('posts', selector));

Client side, it keeps working, but server side, the result is now undefined (the view is broken now of course, but we don't care for this example).
Is it a bug ? Is it supposed to work that way ? Is there a workaround ?
Here are the stack traces :
Call from server :
Trace: undefined
at [object Object].Meteor.methods.getPost (both/router.jsx:14:19)
at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1617:1)
at packages/ddp/livedata_server.js:1530:1
at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
at [object Object]._.extend.apply (packages/ddp/livedata_server.js:1529:1)
at [object Object]._.extend.call (packages/ddp/livedata_server.js:1472:1)
at FlowRouter.route.action (both/router.jsx:25:12)
at packages/meteorhacks:flow-router-ssr/server/route.js:19:1
at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
at packages/meteorhacks:flow-router-ssr/server/route.js:13:1
at doCall (packages/meteorhacks:picker/lib/implementation.js:98:1)

Call from client
Trace: one
at [object Object].Meteor.methods.getPost (both/router.jsx:13:19)
at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1617:1)
at packages/ddp/livedata_server.js:648:1
at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
at packages/ddp/livedata_server.js:647:1
at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
at [object Object]._.extend.protocol_handlers.method (packages/ddp/livedata_server.js:646:1)
at packages/ddp/livedata_server.js:546:1

From what I understand, this is a context matter. But I have no idea how to solve that.

I tried to subscribe globally to 'posts' like that :
FlowRouter.subscriptions = function() {
  this.register('posts', Meteor.subscribe('posts'));
};

And it does not work, I have to have a specific subscription for the route.

I'll have some guides on SSR soon with limitations. So, in the current state, things changes a lot.
I suggest you to wait a few days.

I haven't tried meteor methods in the code yet. May be we won't support it.

Will this help to solve the problem : https://github.com/meteor/meteor/pull/4939 ?

Will this help to solve the problem : https://github.com/meteor/meteor/pull/4939 ?

I think it's not related. Currently we don't support or haven't done any
experiments with method calls.
You should use a subscription to get data. Otherwise, it data won't show
up.
So basically, even it runs on the server it has client side like context.
On 2015 අගෝ 15, සෙන at ප.ව. 2.53 fabien huet<EMAIL_ADDRESS>wrote:

Will this help to solve the problem : meteor/meteor#4939
https://github.com/meteor/meteor/pull/4939 ?
—
Reply to this email directly or view it on GitHub
https://github.com/kadirahq/flow-router/issues/205#issuecomment-131321595
.

Sorry, I explained myself poorly : You DO support method calls. They work with flow router SSR.
If you fork your repo : https://github.com/arunoda/hello-react-meteor and change the first route to that :
FlowRouter.route("/", {
  action: function() {
    Meteor.call( 'getNumber', ( error, number ) => {
      ReactLayout.render(BlogLayout, {
        content: <PostList number={ number } />
      });
    } );
  }
});

Then create the corresponding method :
getNumber() {
	return 42;
},

And then add this in the render function :
My number : { this.props.number }

It works, the server send this code : My Blog

My number : 42

When you console.log( this.props.number ) in the render function of the PostList component, the terminal and the console return 42. So, no question. You can call a method and it works well to send static data. But, when you try another method like :
getPost() {
	return Posts.findOne();
},

It stops working server side and returns undefined (but still works client side). It would be a killer feature to be able to send a collection count in the props for instance. Or to modify a cursor server side to inject needed translations for i18n.
So the question is not 'why metor call don't work server side in the router', but 'why meteor call cannot get data from a collection'.
I'm not sure why this happens, but I suspect a synchronicity problem. Try this for instance :
FlowRouter.route("/", {
  action: function() {
    Meteor.setTimeout( () => {
      ReactLayout.render(BlogLayout, {
        content: <PostList />
      });
    }, 2000 );
  }
});

Ok, you would never do that in real life. It still works client side : when you land on the page, nothing happen for 2 sec and the page renders. But server side, nothing is rendered.

is returned.
So, it behave like async is not possible.

Okay. Now I got it and I know the issue.
That's because, since you call if from the SSR context, Method call also has the SSR context.
I know how to fix this.
I will do a fix.

I've did some changes to the latest version and this should work with that. Could you try with the SSR branch.

Well, now it's broken with a big and scarry error message :
xception in delivering result of invoking 'getNumber': Error: Can't call yield in a noYieldsAllowed block!
I20150817-11:58:52.452(2)?     at Function.Fiber.yield (packages/meteor/fiber_helpers.js:8:1)
I20150817-11:58:52.453(2)?     at Function.wait (/Users/fabienhuet/.meteor/packages/meteor-tool/.<IP_ADDRESS>wysac9++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:183:14)
I20150817-11:58:52.453(2)?     at Object.Future.wait (/Users/fabienhuet/.meteor/packages/meteor-tool/.<IP_ADDRESS>wysac9++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:397:10)
I20150817-11:58:52.453(2)?     at [object Object]._.extend._nextObject (packages/mongo/mongo_driver.js:929:1)
I20150817-11:58:52.453(2)?     at [object Object]._.extend.forEach (packages/mongo/mongo_driver.js:963:1)
I20150817-11:58:52.453(2)?     at [object Object]._.extend.map (packages/mongo/mongo_driver.js:973:1)
I20150817-11:58:52.453(2)?     at [object Object]._.extend.fetch (packages/mongo/mongo_driver.js:997:1)
I20150817-11:58:52.453(2)?     at [object Object].Cursor.(anonymous function) [as fetch] (packages/mongo/mongo_driver.js:812:1)
I20150817-11:58:52.453(2)?     at [object Object].React.createClass.getMeteorData (both/components/post_list.jsx:8:53)
I20150817-11:58:52.454(2)?     at packages/react-meteor-data/meteor-data-mixin.jsx:73:28
W20150817-11:58:52.496(2)? (STDERR) error on fast-rendering path: / ; error: Error: Can't set headers after they are sent.
W20150817-11:58:52.496(2)? (STDERR)     at ServerResponse.OutgoingMessage.setHeader (http.js:690:11)
W20150817-11:58:52.496(2)? (STDERR)     at ServerResponse.res.setHeader (/Users/fabienhuet/.meteor/packages/webapp/.<IP_ADDRESS>p5axz++os+web.browser+web.cordova/npm/node_modules/connect/lib/patch.js:59:22)
W20150817-11:58:52.496(2)? (STDERR)     at next (/Users/fabienhuet/.meteor/packages/webapp/.<IP_ADDRESS>p5axz++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:153:13)
W20150817-11:58:52.497(2)? (STDERR)     at next (/Users/fabienhuet/.meteor/packages/webapp/.<IP_ADDRESS>p5axz++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:127:23)
W20150817-11:58:52.497(2)? (STDERR)     at processNextSubRouter (packages/meteorhacks:picker/lib/implementation.js:74:1)
W20150817-11:58:52.497(2)? (STDERR)     at processNextSubRouter (packages/meteorhacks:picker/lib/implementation.js:74:1)
W20150817-11:58:52.497(2)? (STDERR)     at processNextRoute (packages/meteorhacks:picker/lib/implementation.js:65:1)
W20150817-11:58:52.497(2)? (STDERR)     at processNextMiddleware (packages/meteorhacks:picker/lib/implementation.js:48:1)
W20150817-11:58:52.497(2)? (STDERR)     at packages/meteorhacks:fast-render/lib/server/routes.js:39:1
W20150817-11:58:52.497(2)? (STDERR)     at packages/meteorhacks:fast-render/lib/server/routes.js:93:1
W20150817-11:58:52.497(2)? (STDERR) error on fast-rendering path: / ; error: Error: Can't set headers after they are sent.
W20150817-11:58:52.498(2)? (STDERR)     at ServerResponse.OutgoingMessage.setHeader (http.js:690:11)
W20150817-11:58:52.498(2)? (STDERR)     at ServerResponse.res.setHeader (/Users/fabienhuet/.meteor/packages/webapp/.<IP_ADDRESS>p5axz++os+web.browser+web.cordova/npm/node_modules/connect/lib/patch.js:59:22)
W20150817-11:58:52.498(2)? (STDERR)     at next (/Users/fabienhuet/.meteor/packages/webapp/.<IP_ADDRESS>p5axz++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:153:13)
W20150817-11:58:52.498(2)? (STDERR)     at next (/Users/fabienhuet/.meteor/packages/webapp/.<IP_ADDRESS>p5axz++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:127:23)
W20150817-11:58:52.498(2)? (STDERR)     at processNextSubRouter (packages/meteorhacks:picker/lib/implementation.js:74:1)
W20150817-11:58:52.498(2)? (STDERR)     at processNextSubRouter (packages/meteorhacks:picker/lib/implementation.js:74:1)
W20150817-11:58:52.499(2)? (STDERR)     at processNextRoute (packages/meteorhacks:picker/lib/implementation.js:65:1)
W20150817-11:58:52.499(2)? (STDERR)     at processNextMiddleware (packages/meteorhacks:picker/lib/implementation.js:48:1)
W20150817-11:58:52.499(2)? (STDERR)     at packages/meteorhacks:fast-render/lib/server/routes.js:20:1
W20150817-11:58:52.499(2)? (STDERR)     at handleError (packages/meteorhacks:fast-render/lib/server/routes.js:106:1)
W20150817-11:58:52.499(2)? (STDERR)
W20150817-11:58:52.499(2)? (STDERR) /Users/fabienhuet/.meteor/packages/meteor-tool/.<IP_ADDRESS>wysac9++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:245
W20150817-11:58:52.504(2)? (STDERR) 						throw(ex);
W20150817-11:58:52.504(2)? (STDERR) 						      ^
W20150817-11:58:52.504(2)? (STDERR) Error: Can't set headers after they are sent.
W20150817-11:58:52.505(2)? (STDERR)     at ServerResponse.OutgoingMessage.setHeader (http.js:690:11)
W20150817-11:58:52.505(2)? (STDERR)     at ServerResponse.res.setHeader (/Users/fabienhuet/.meteor/packages/webapp/.<IP_ADDRESS>p5axz++os+web.browser+web.cordova/npm/node_modules/connect/lib/patch.js:59:22)
W20150817-11:58:52.505(2)? (STDERR)     at next (/Users/fabienhuet/.meteor/packages/webapp/.<IP_ADDRESS>p5axz++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:153:13)
W20150817-11:58:52.505(2)? (STDERR)     at next (/Users/fabienhuet/.meteor/packages/webapp/.<IP_ADDRESS>p5axz++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:127:23)
W20150817-11:58:52.505(2)? (STDERR)     at processNextSubRouter (packages/meteorhacks:picker/lib/implementation.js:74:1)
W20150817-11:58:52.506(2)? (STDERR)     at processNextRoute (packages/meteorhacks:picker/lib/implementation.js:65:1)
W20150817-11:58:52.506(2)? (STDERR)     at processNextMiddleware (packages/meteorhacks:picker/lib/implementation.js:48:1)
W20150817-11:58:52.506(2)? (STDERR)     at packages/meteorhacks:fast-render/lib/server/routes.js:20:1
W20150817-11:58:52.506(2)? (STDERR)     at handleError (packages/meteorhacks:fast-render/lib/server/routes.js:106:1)
W20150817-11:58:52.506(2)? (STDERR)     at packages/meteorhacks:fast-render/lib/server/routes.js:95:1
=> Exited with code: 8

Maybe it could be put in triggersEnter. But triggersEnter is not supported server side.

Can I have a sample code for this. I need to experiment with this.
May be this leads to anti-pattern or something. Let's see.
On 2015 අගෝ 17, සඳුදා at ප.ව. 3.38 fabien huet<EMAIL_ADDRESS>wrote:

Maybe it could be put in triggersEnter. But triggersEnter is not
supported server side.
—
Reply to this email directly or view it on GitHub
https://github.com/kadirahq/flow-router/issues/205#issuecomment-131765521
.

Of course :
https://www.dropbox.com/s/vxq5ipqub2psqm9/examples-ssr.zip
The "call-value" example works client and server side. (look at the generated source code)
The "call-collection" example works client side but not server side (the call returns undefined).
When you use the last version of the ssr branch (not the one on atmosphere, juste download and use as a local package), both examples crash the whole thing.

I can understand the issue. Will work it.
On 2015 අගෝ 17, සඳුදා at ප.ව. 4.03 fabien huet<EMAIL_ADDRESS>wrote:

Of course :
https://www.dropbox.com/s/vxq5ipqub2psqm9/examples-ssr.zip
The "call-value" example works client and server side. (look at the
generated source code)
The "call-collection" example works client side but not server side (the
call returns undefined).
When you use the last version of the ssr branch (not the one on
atmosphere, juste download and use as a local package), both examples crash
the whole thing.
—
Reply to this email directly or view it on GitHub
https://github.com/kadirahq/flow-router/issues/205#issuecomment-131772434
.

Any news on that one ?

I looked at it a bit and here's the problem :
ReactLayout._renderServer = function(layoutClass, regions) {         // 29
  var el = React.createElement(layoutClass, regions);                // 30
  var html = React.renderToString(el);                               // 31
                                                                     // 32
  if(Package['kadira:flow-router-ssr']) {                            // 33
    var FlowRouter = Package['kadira:flow-router-ssr'].FlowRouter;   // 34
    var ssrContext = FlowRouter.ssrContext.get();                    // 35
    ssrContext.setHtml(html);                                        // 36
  }                                                                  // 37
};                                                                   // 38

When ReactLayout.render is called asynchronousely, FlowRouter.ssrContext.get() is null. The solution is probably to provide it when you call ReactLayout.render. For example :
action( params, queryParams ) {
	let context;
	if ( Meteor.isServer ) {
		context = FlowRouter.ssrContext.get();
	}
	Meteor.call( 'getPostData', params.slug, ( error, result ) => {
		if ( Meteor.isServer ) {
			let el = React.createElement( ReactLayouts.MainLayout, {
				content: <ReactViews.Post data={ result } />,
			} );
			let html = React.renderToString( el );
			context.setHtml( html );
		} else
			ReactLayout.render( ReactLayouts.MainLayout, {
				content: <ReactViews.Post data={ result } />,
			} );

	} );
}

This way, it works. But it's ugly. The action hook should send by default the ssr context, so it's never lost.
I try to make a PR.
(and for dochead, it's the same problem)

Hi,
Just adding my support to this. Being able to have the result of a Meteor method available would be very helpful.
I currently use a meteor method to get an array of _ids and then subscribe to the those _ids. It lets me keep the initial ordering of the documents whilst retaining reactivity (this article describes it in more detail: http://tomkelsey.co.uk/reining-in-the-reactivity-with-meteor/)
I haven't worked out how to do this with SSR as I can't wait on the method call on the client - so react reports a mismatch between the client and server code.
If @fabien-h's PR solves the issue I'm all for it :+1:

I'm having the same problem too! But with react-mounter. Has this been resolved? Or FR SSR won't support this?

You can use Inject-Initial as a workaround to make data instantly available on the client: https://github.com/meteorhacks/meteor-inject-initial

Hi,
Any update on how to fetch content with methods and SSR?


Increase batch size fail threshold for cassandra service

1、Let cassandra, scylladb, mysql and hbase stored in tmpfs
2、Increase batch size fail threshold for cassandra service