License violations don't include Severity. Also lots of licenses get reported as Unknown.

Describe the bug
When reporting license violations, severity is not reported, both in the PR scan as well as Repo scan. Xray on-demand scans do include severity information for licenses. Also, a lot of licenses are reported as Unknown when using a watch with policy to report Unknown licenses. Please see the screenshots uploaded in 'Current behaviour'.
Current behavior
In PR scan:

In Repo scan:

Reproduction steps
Run Frogbot scans with a watch configured to report license violations along with unknown licenses.
Expected behavior
Severity is reported, so higher ones could be spotted over lower ones. There should not be too many unknown licenses, only legitimate cases should be reported.
JFrog Frogbot version
2.19.10
Package manager info
npm. package.json.
Git provider
GitHub
JFrog Frogbot configuration yaml file
No response
Operating system type and version
Github Actions. Ubuntu 22.04.4.
JFrog Xray version
3.87.9

Hi @imranzunzani,
Thank you for using Frogbot!
It seems like this issue is related to how you've configured your watch and policy. You can find more information about configuring trigger violations using Xray policy rules in the following link: Xray Policy Rules Documentation
The entries you're seeing are for packages with unknown licenses, which we treat as violations. You can remove these types of violations by editing the rule.
To do so, you can remove the option "Disallow Unknown Licenses", that is shown as enabled in the screenshot below:

Please feel free to reach out if you have any further questions or encounter any issues.

Hi @attiasas ,
Thank you for the response.
We actually want the 'Disallow Unknown License' to report the unknown licenses, but the problem seems to be that it is reporting too many licenses as 'Unknown' which actually have licenses associated. Eg. in the screenshot, you could see hasown which is MIT, but reported as Unknown. You can check this at https://github.com/inspect-js/hasOwn/tree/v2.0.0?tab=readme-ov-file.
Also, could you please check and confirm, if there are plans to include 'Severity' information?

Hi @imranzunzani,
Regarding the absence of 'Severity' information regarding the license, currently, it's not displayed. However, we have added it to our backlog, and it will be available in future versions after prioritization.

"Unknown" licenses may arise from various situations:

The component license exists but isn't identified by Xray, meaning it's not in Xray's license database. In such cases, an Admin can add a Custom License via the UI (Administration > Xray > settings > Compliance Licenses). Once added to the Xray DB, if the artifact contains the licenses Xray can detect it.
The component isn't in our Software catalog (XUC), or it's in our catalog but lacks license info, and the artifact doesn't include any license info in the component. In such cases, the user may assign a license to the component from the Descendants screen.

Hi @attiasas ,
Thank you for adding the 'Severity' info, for the future releases.
Regarding the 'Unknown' licenses, it seems like an anomalous behaviour, as the license info is there in Xray (Artifactory), but it is getting reported as 'Unknown'.
Eg. For the neo-async package, the following information is present:

but that still gets flagged as 'Unknown'.
Could you please check, if this could be happening due to any reason with the logic at Frogbot, or should this be raised to JFrog support, so that it gets looked into by Xray?

Hi @attiasas,
Thank you for the clarification. Regarding your 'Unknown' license related various situations (point 2), please find these explanations with attached datasets as mentioned below:

The component isn't in our Software catalog (XUC), or it's in our catalog but lacks license info, and the artifact doesn't include any license info in the component. In such cases, the user may assign a license to the component from the Descendants screen.

Explanation: As mentioned below "xmlchars 2.2.0" package is present in the artifactory and x-ray is able to identify its license information. This showcase that the package metadata is present within the Jfrog Software catalog (XUC) along with the license info.
On the other hand, frogbot is not able to identify same package's license information.
My assumption is that the frogbot and x-ray are pointing to the same knowledge base. If so, then frogbot should be able to showcase the same result set as its shown in the xray. Let me know if its otherwise.

Hey @Avi706 @imranzunzani
Xray on demand scanning and Frogbot scanning have different scan methodologies.
Xray on-demand scans a binary file while Frogbot scans a source code, the context of these 2 methodologies is different, and therefore the results may vary. In this case,  for npm package xmlchars 2.2.0 we do miss license information in our Software catalog (XUC). We will work on adding it.

Hi @orz25,
Thank you for the response. Please do note that there are many packages getting reported as with 'Unknown' licenses, not just xmlchars 2.2.0, so this behaviour would need fixing some logic systemically in XUC, we think.

@imranzunzani We will take a look at this. Thank you for the feedback!

Hi @attiasas and @orz25,
I have submitted https://github.com/jfrog/frogbot/pull/672, which adds the 'Severity' column to the PR's Licenses violations info. Please consider that change, as it is required for us. As we also need that information in the Repository Scan results as well, i.e. in GHAS's SARIFs submission, we would appreciate if you could look into that portion of the functionality. Currently the classification on the list (code-scanning) is getting reported as 'Error' and 'Note', which is not helpful for filtering:

As mentioned before (screenshot), the information is not present in the description either, when clicked on an element in the list.

Hi @imranzunzani,
Thank you for your submission. I will review it as soon as possible. Additionally, I will address the issue you have raised.
Could you please provide more details about the information you expect for your filtering? What specific information is missing? Are you referring to the severity? Kindly elaborate on your requirements.
Thank you.

Hi @attiasas ,
Thank you for looking into this.
The PR that I have submitted adds the Severity Field for the PR Scans. Hope you would review that soon.
Other than that, there are two requirements:

'Severity' is required for filtering the violations in the list of alerts in 'code scanning' for the Repository Scan. It works for the CVEs, but is not there for the license violations, as the screenshots show.
There is the problem of licenses being flagged as 'Unknown', while they are fine in Xray. Could this be related to the untrimmed spaces, as mentioned in this PR: https://github.com/jfrog/frogbot/pull/670? Could you please take a look, if that could to be the problem, for the licenses getting flagged as 'Unknown'?

Hi @imranzunzani,
The pull request you opened has been merged, and the fix will be available in the next release of Frogbot.
About the requirements:

Changes to the Scan-Repository command (which generates the SARIF file) should be implemented here: Link to code. We always add the security-severity property equal to 0 when we need to calculate it based on severity.

As mentioned by @orz25, the two scans are different. Frogbot scans source-code, while Xray-On-Demand scans binary. When scanning source code, we only send the dependencies ID. If it exists in our database, we return the license information. When scanning binary, we actually walk and search in the files for the license and not just information in our database. To change this behavior, we need to investigate and prioritize a solution. If you want, you can pass us a list of the dependencies with their license information, and we will check if we can add it to our general catalog database. If not, you can always add it yourself as mentioned above.

Hi @attiasas ,
Thank you for merging the PR.
Regarding the requirements, @Avi706 will take it up from here on those, probably with the ESL.

Hello @imranzunzani and @Avi706
does this issue has been resolved? do you need any further assistance with it?
If not- can I close the ticket?

Hello @eranturgeman, thanks for reaching out to us. We managed to fix the unknown license issue in x-ray and we are going to test the same in Frogbot soon to check the behavior and update here.

Hello @eranturgeman, thanks for reaching out to us. We have managed to solve the unknown license issue in x-ray and we will be testing the same in Frogbot soon. Once we are done with it, will update the issue accordingly.

Great @Avi706
Let me know if all worked out and I can resolve this issue :)

Hi @imranzunzani,
The pull request you opened has been merged, and the fix will be available in the next release of Frogbot.
About the requirements:

Changes to the Scan-Repository command (which generates the SARIF file) should be implemented here: Link to code. We always add the security-severity property equal to 0 when we need to calculate it based on severity.
As mentioned by @orz25, the two scans are different. Frogbot scans source-code, while Xray-On-Demand scans binary. When scanning source code, we only send the dependencies ID. If it exists in our database, we return the license information. When scanning binary, we are using a different method. To change this behavior, we need to investigate and prioritize a solution. If you want, you can pass us a list of the dependencies with their license information, and we will check if we can add it to our general catalog database. If not, you can always add it yourself as mentioned above.

Hi @attiasas
Was #2 addressed? We have also observed this issue concerning Frogbot's detection of Licenses linked to some dependencies. Several components are being indicated with an 'Unknown' license in Frogbot Scan. However, upon cross-checking within Artifactory and Xray, we have found that these reported components indeed have an license associated with them.
Eg: For a python fast-api project, several (indirect) dependencies are being flagged with an unknown license

The impacted dependency “Pygments==2.17.2” is listed as Unknown License but in Artifactory it is associated with BSD-2-Clause License

And also, frogbot is unable to detect license for core packages for the project (python, root)

Hi @pru-qmir,
Regarding point #2, we do not support detecting licenses in first-party source code. We only support license detection when the code is in binary form. If you need this feature, please let us know, and we will add it to our backlog for implementation.
As for the other issues you have raised:
The row related to root is a bug and should not appear. I believe I know the cause and will work on resolving it.
Regarding Pygments 2.17.2, we are currently investigating, is it also the case for typing-extensions \ python?
I will provide updates on the open issues as soon as I can.

Regarding Pygments 2.17.2, we are currently investigating, is it also the case for typing-extensions \ python?
Yes, that's correct for typing-extensions. I am not sure for python, I don't see this binary in Artifactory. Should python not appear similar to root?


Create thread when starting fetcher

When creating a Fetcher instance in consumer, a thread is created to handle the commands and fetch the data in the background. That threads starts the loop right after the Fetcher is created. When the fetcher instance stops, that thread is still running in forever-loop. This creates serious thread leaking in some use cases where many instances of consumers are used. Therefore, I moved the thread initialization to Fetcher#start and kill the thread naturally when calling Fetcher#stop.  This change seems to be safe and more efficient. In the consumer, before starting the consumer loop, the fetcher is started. Right after the consumer loop breaks (interrupting, error, etc.), the fetcher is cleaned up and stopped totally.
This script demonstrates the thread leaking in previous versions, and fixed in current version.
require 'kafka'
topic = 'hello'

begin
  kafka = Kafka.new(
    seed_brokers: ['localhost:9092'],
    client_id: "simple-consumer",
    socket_timeout: 20
  )

  consumer = kafka.consumer(group_id: "firehose")
  consumer.subscribe(topic)

  consumer.each_message do |message|
    #consumer.stop
    raise if rand(0..10) == 5
    puts message.value
  end
rescue => e
  puts e
  consumer.stop
  p Thread.list.count
  retry
end

cc @mensfeld @dasch
P/s: this PR contains some changes to fix flaky tests. They are now stable.

Here's the code you can use to check if that solves the problem:
begin
 kafka = Kafka.new(
   seed_brokers: brokers,
   client_id: "simple-consumer",
   socket_timeout: 20,
   logger: logger,
 )

   consumer = kafka.consumer(group_id: "firehose")
   consumer.subscribe(topic)

 consumer.each_message(topic: topic) do |message|
   #puts message.value
   #consumer.stop
   raise
 end
rescue => e
 consumer.stop
 p Thread.list.count
 retry
end

The number of threads shouldn't raise.

Thank you. This indeed should solve the problem, making the usage of consumers way more flexible.
Is there a chance to actually backport this fix as well?

@mensfeld This fix is simple and looks safe to me. So, I think there won't be any conflict to the 0.6.x stable versions. @dasch is the only one who can release the version though 😄

This needs to be run with production load for a while though – there are some edge cases when restarting a crashed consumer loop that I remember. @mensfeld can you validate this with real workloads?

If someone needs a bigger project to work on with regards to ruby-kafka, a much better integration test suite would be great :D

@dasch I can, however this problem persists for corner-cases that aren't actually related to any of my productions :( The way I've discovered that was by a report of one of the Karafka users, that uses confluence cloud that was dropping the connections upon reaching the tier limits. Anyhow, I can give it a spin just running to make sure it actually works :)

If someone needs a bigger project to work on with regards to ruby-kafka, a much better integration test suite would be great :D
I have a bigger integration setup in plans for Karafka. It would pretty much cover many corner cases from ruby-kafka as well, but like any open-source, you paradoxically need some payed resources to do that and Karafka team is already investing their time. Oh... life I guess ;)

We are currently soak testing this on our beta environment and will report back.

Same here. So far so good. @lewispb could you actually reach the limits of confluence to trigger the issue that caused us to discover this in the first place?

We have been seeing this issue occur even without hitting any limits, so going for 3 days without problems would indicate success in my view.

@lewispb awesome. It's also running on my stagings. So far so good.

We are now seeing the timeout problem again. This time though, a new error:
RuntimeError: already started
  from kafka/fetcher.rb:46:in `start'
  from kafka/consumer.rb:389:in `consumer_loop'
  from karafka/patches/ruby_kafka.rb:15:in `consumer_loop'
  from kafka/consumer.rb:290:in `each_batch'
  from karafka/connection/client.rb:29:in `fetch_loop'
  from karafka/connection/listener.rb:39:in `fetch_loop'
  from karafka/connection/listener.rb:23:in `call'
  from karafka/fetcher.rb:19:in `block (2 levels) in call'

@lewispb That error comes from a check that raises exception when the fetcher already started.
def start
  raise "already started" if @running
  # ...
end

This is not actually an exception. The outsider can call Fetcher#start anytime before going into consumer loop to ensure it is running, to be safe. So, the Fetcher should not be panic. Pushed a small change to silently return in this case.

Thanks, will try that out Monday. A new error overnight:
TypeError: no implicit conversion of nil into Integer
  from kafka/protocol/encoder.rb:57:in `pack'
  from kafka/protocol/encoder.rb:57:in `write_int32'
  from kafka/protocol/offset_commit_request.rb:31:in `encode'
  from kafka/protocol/request_message.rb:22:in `encode'
  from kafka/protocol/encoder.rb:178:in `encode_with'
  from kafka/connection.rb:162:in `write_request'
  from kafka/connection.rb:103:in `block in send_request'
  from active_support/notifications.rb:170:in `instrument'
  from kafka/instrumenter.rb:21:in `instrument'
  from kafka/connection.rb:96:in `send_request'
  from kafka/broker.rb:188:in `send_request'
  from kafka/broker.rb:86:in `commit_offsets'
  from kafka/consumer_group.rb:82:in `commit_offsets'
  from kafka/offset_manager.rb:125:in `commit_offsets'
  from kafka/consumer.rb:426:in `make_final_offsets_commit!'
  from kafka/consumer.rb:420:in `ensure in consumer_loop'
  from kafka/consumer.rb:422:in `consumer_loop'
  from karafka/patches/ruby_kafka.rb:15:in `consumer_loop'
  from kafka/consumer.rb:290:in `each_batch'
  from karafka/connection/client.rb:29:in `fetch_loop'
  from karafka/connection/listener.rb:39:in `fetch_loop'
  from karafka/connection/listener.rb:23:in `call'
  from karafka/fetcher.rb:19:in `block (2 levels) in call'

Hmm. Weird. That error happens because the consumer leaves the consumer loop, tries to make final commit after leaving group or before joining any group. Both cases are weird, I could not found any logics lead to this situation. In Karafka, there is a patch on consumer loop (lib/karafka/patches/ruby_kafka.rb) and there is some threaded activities involved. I think we can start investigating from that. cc @mensfeld. This error doesn't change anything, the final commits are discarded anyway in both cases.
Btw, that error does not relate to this PR, that's a different error. So, we can fix that latter.

Since everything seems stable, everyone seems not to have problems with it and this is not a big change, I think I'll merge it now.


Support PIKs

support PIKs in place of CIKs

PIKs will probably not become official, so I'm closing this as won't fix.


console issuses

how to setup console element auto scroll to bottom
console output auto wrap.  which causes resize console panel and copy console text with wrap

I've added autoscrolling to the console (using the solution from https://github.com/mfussenegger/nvim-dap/pull/654) so as long as the cursor is on the last line of the buffer, it will autoscroll, similar to a terminal.
Terminal wrapping is not controlled by nvim-dap-ui. There are some issues with it in Neovim https://github.com/neovim/neovim/issues/2514

cool, thx


[analyzer] Soundness issue with typing of equality expressions

Consider the following example, based on this comment:
class NeverEqual {
  Never operator ==(Object? o) => throw 0;
}

void main() {
  NeverEqual? neverEqual = NeverEqual() as dynamic, other;
  Object? o = true;

  if (o is! int) neverEqual == other; // Incorrect to assume that this throws.
  print(o.toRadixString(16)); // Unsound.
}

This shows that it is unsound to assume that the type of an <equalityExpression> is Never, even in the case where the corresponding declaration of operator == has return type Never. Equality expressions should always have the type bool.
However, the analyzer (DartPad based on Dart SDK 3.3.0-16.0.dev) does not report any errors on the line marked 'Unsound', which implies that it considers neverEqual == other to be an expression that cannot complete normally.

It's worth mentioning that this cannot affect constant evaluation, since constant == is only allowed with primitive equality, not anything that calls a user written implementation. So it will only be incorrect typing of code that will never be executed at that type. (So technically it's not "unsound", there is no expression which is evaluated to a type which isn't a subtype of its static type. It's just not correct, it doesn't match the compiler behavior.)

Well, it's an analyzer issue. If the CFE had had the same static analysis then it would certainly have been a soundness issue: It will attempt to call toRadixString on true.

@srawlins, I just tried the example, and it looks like it has been resolved already?


Add host functions support to the verifier

Modify the verifier so that it's generic over signature verification and hashing
pub trait HostFunctions {
 fn sha_256(bytes: &[u8]) -> Hash32;
 fn fast_aggregate_verify(pub_keys: Vec<BlsPublicKey>, signing_root: Hash32, signature: BlsSignature) -> bool;
}
pub struct EthLightClient<H: HostFunctions> { ... }

Unneeded

unneeded


Cannot activate error warning when installing extension dependending on grammar extension

Verifying https://github.com/microsoft/vscode/issues/128375
Version: 1.59.0-insider
Commit: f6df685c62da50886f7540cbf768ed4333d58bea
Date: 2021-07-13T05:14:01.722Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.11.0-22-generic

open a dev container window
install the scala-lang.scala extension (scala grammar, no code, extensionKind: ui, explicitly defined)
install the scalameta.metals exension (with code, depends on 'scala-lang.scala')

Error after installing the second extension:
Cannot activate the 'Scala (Metals)' extension because it depends on the 'Scala Syntax (official)' extension, which is not loaded. Would you like to reload the window to load the extension?
That reload should not be necessary here.
Feel free to close the issue as it's a special setup and all works fine after reloading.

The ExtensionsActivator works with a set of "resolved extensions". This set is only initialized on workbench start-up and is not updated when extensions are enabled/installed or disabled/uninstalled.


Added translations for confirm password error state

Fixes # BLUI-3944

Changes proposed in this Pull Request:

Added translations for confirm password error state
Updated package version
Updated changelog

Screenshots / Screen Recording (if applicable)

To Test:

Any specific feedback you are looking for?

Please open https://github.com/etn-ccis/blui-react-workflows/pull/237 once this gets merged

I see that we already have this:
https://github.com/etn-ccis/blui-react-auth-shared/blob/e8d29ca51f882c2b41306086c2ffcfd91f58c3f1/src/data/translations/english.ts#L112
and you added this
https://github.com/etn-ccis/blui-react-auth-shared/blob/e8d29ca51f882c2b41306086c2ffcfd91f58c3f1/src/data/translations/english.ts#L163
Are you able to either
(1) reuse what's already there, or if that is not possible
(2) make the verbiage match?

I see that we already have this:
https://github.com/etn-ccis/blui-react-auth-shared/blob/e8d29ca51f882c2b41306086c2ffcfd91f58c3f1/src/data/translations/english.ts#L112
and you added this
https://github.com/etn-ccis/blui-react-auth-shared/blob/e8d29ca51f882c2b41306086c2ffcfd91f58c3f1/src/data/translations/english.ts#L163
Are you able to either
(1) reuse what's already there, or if that is not possible (2) make the verbiage match?

I will reuse the PASS_MATCH_ERROR for this. Closing this PR, as there are no changes needed in shared auth.


Wrong index calculation in constructing sparse random matrix

Description
In cupyx/scipy/sparse/construct.py the constructor random first generates the indices as a contiguous array, than transforms them to row and column indices. However to do that uses a formula that does not work for certain values:
line: 367
ind = random_state.choice(mn, size=k, replace=False)
j = cupy.floor(ind * (1. / m)).astype('i')
i = ind - j * m

For example if ind = 3150 and m = 3150, j should be 1, but this algorithm returns 0, probably for rounding errors. In this case i = 3150, and this causes a
ValueError('row index exceeds matrix dimensions') later in the coo constructor
The simple fix is to calculate directly the integer division, with the notation //, so the code becomes:
ind = random_state.choice(mn, size=k, replace=False)
j = ind//m
i = ind - j * m

To Reproduce
No response
Installation
Source (pip install cupy)
Environment
OS                           : Linux-5.13.0-22-generic-x86_64-with-glibc2.34
Python Version               : 3.9.7
CuPy Version                 : 10.0.0
CuPy Platform                : NVIDIA CUDA
NumPy Version                : 1.20.3
SciPy Version                : 1.7.1
Cython Build Version         : 0.29.24
Cython Runtime Version       : None
CUDA Root                    : /usr/local/cuda
nvcc PATH                    : /usr/local/cuda/bin/nvcc
CUDA Build Version           : 11040
CUDA Driver Version          : 11040
CUDA Runtime Version         : 11040
cuBLAS Version               : (available)
cuFFT Version                : 10501
cuRAND Version               : 10205
cuSOLVER Version             : (11, 2, 0)
cuSPARSE Version             : (available)
NVRTC Version                : (11, 4)
Thrust Version               : 101201
CUB Build Version            : 101201
Jitify Build Version         : 60e9e72
cuDNN Build Version          : (not loaded; try `import cupy.cuda.cudnn` first)
cuDNN Version                : (not loaded; try `import cupy.cuda.cudnn` first)
NCCL Build Version           : None
NCCL Runtime Version         : None
cuTENSOR Version             : None
cuSPARSELt Build Version     : None
Device 0 Name                : NVIDIA GeForce GTX 1050 Ti with Max-Q Design
Device 0 Compute Capability  : 61
Device 0 PCI Bus ID          : 0000:01:00.0

Additional Information
No response

Thank you! Can you send a PR?

Hey! I would like to fix this bug if nobody has yet started working on it.
Thanks.

Go ahead

i am not able to set it up on my local system.

[Requirements
NVIDIA CUDA GPU with the Compute Capability 3.0 or larger.]

Can it be installed without  NVIDIA CUDA GPU?
Log:

-------- Configuring Module: cuda --------
Command "x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -D_FORCE_INLINES=1 -I/home/error0180/git_projects/cupy/cupy/_core/include/cupy/cub -I/home/error0180/git_projects/cupy/cupy/_core/include -c /tmp/tmpbimo8oej/a.cpp -o /tmp/tmpbimo8oej/tmp/tmpbimo8oej/a.o" failed with exit status 1
**************************************************
*** WARNING: Cannot check compute capability
Command "x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -I/home/error0180/git_projects/cupy/cupy/_core/include/cupy/cub -I/home/error0180/git_projects/cupy/cupy/_core/include -c /tmp/tmpgsfyt7in/a.cpp -o /tmp/tmpgsfyt7in/tmp/tmpgsfyt7in/a.o" failed with exit status 1
**************************************************

************************************************************
* CuPy Configuration Summary                               *
************************************************************

Build Environment:
  Include directories: ['/home/error0180/git_projects/cupy/cupy/_core/include/cupy/cub', '/home/error0180/git_projects/cupy/cupy/_core/include']
  Library directories: []
  nvcc command       : (not found)
  hipcc command      : (not found)

Environment Variables:
  CFLAGS          : (none)
  LDFLAGS         : (none)
  LIBRARY_PATH    : (none)
  CUDA_PATH       : (none)
  NVTOOLSEXT_PATH : (none)
  NVCC            : (none)
  HIPCC           : (none)
  ROCM_HOME       : (none)

Modules:
  cuda      : No
    -> Include files not found: ['cublas_v2.h', 'cuda.h', 'cuda_profiler_api.h', 'cuda_runtime.h', 'cufft.h', 'curand.h', 'cusparse.h', 'nvrtc.h']
    -> Check your CFLAGS environment variable.

ERROR: CUDA could not be found on your system.

HINT: You are trying to build CuPy from source, which is NOT recommended for general use.
      Please consider using binary packages instead.

Please refer to the Installation Guide for details:
https://docs.cupy.dev/en/stable/install.html

************************************************************

Traceback (most recent call last):
  File "setup.py", line 85, in <module>
    ext_modules = cupy_setup_build.get_ext_modules(False, ctx)
  File "/home/error0180/git_projects/cupy/install/cupy_builder/cupy_setup_build.py", line 515, in get_ext_modules
    extensions = make_extensions(ctx, compiler, use_cython)
  File "/home/error0180/git_projects/cupy/install/cupy_builder/cupy_setup_build.py", line 319, in make_extensions
    raise Exception('Your CUDA environment is invalid. '
Exception: Your CUDA environment is invalid. Please check above error log.

I installed cupy-cuda101, and cupy-cuda113, but still the same problem persist.
I searched on web and came through some of these links but still same problem persist:
https://github.com/explosion/spaCy/issues/5368
https://stackoverflow.com/questions/50009625/cupy-error-installation
https://askubuntu.com/questions/210884/setting-ld-library-path-for-cuda
Thanks.

#6257

PR
#6257

Thanks.

Fixed via #6257. Thanks!


Update dependency constraints, fix deprecation warnings

Overview: What does this pull request change?

Mainly:

Loosen library dependencies (WIP)
Switch from the deprecated dev-dependencies section to Poetry groups
Remove the use of requests in the command handling. A bit of cleaning is also made there
Drop unused dependencies
Excplicity state we are using a vendored version of click-default-group
Fix some deprecation warnings
Update almost all dev dependencies

Motivation and Explanation: Why and how do your changes improve the library?

Even if most people will install Manim in an isolated environment (e.g. a single virtualenv for Manim), we still have to consider Manim as an installable package, meaning it can live with other unrelated libraries in the same environment (one example would be when using plugins).
Currently, Manim is using caret requirements (^), implicitly setting upper bounds for dependencies. Most people consider this as a bad practice, for two main reasons:

each time a new "major" version is out, we would have to update our dependencies (and looking at the current state of the pyproject.toml, a couple ones aren't).
If this isn't handled, users of manim are bound to versions they don't control. Say I want to use a feature in watchdog>=3.0.0 inside my virtualenv where Manim is installed, I'd have to open a PR on the Manim repo to loosen the dependency on watchdog (which currently is >=2.1.6,<3.0.0), and there're probably no breaking changes for this version bump.

My goal here is to go over the dependencies one by one, and set a reliable minimum version (to be sure it isn't incompatible with how it is used in the codebase).
Links to added or changed documentation pages

Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

This is a good idea in general, and the tests seem like they almost pass. I mainly wanted to get rid of all the individual (automated) PRs by collecting them together here.
I haven't had enough time to carefully check the modified dependencies on your PR yet -- but there are some core dependencies where I'd likely want to stick with caret restrictions (e.g., numpy, pycairo, moderngl, manimpango ...) because the risk of breaking changes is too high. I'll leave a comment on #3376 later today.

Originally posted by @behackl in https://github.com/ManimCommunity/manim/issues/3399#issuecomment-1755174236
I've added constraints to these specific libraries: pycairo, moderngl, manimpango. Regarding numpy and scipy, I don't think adding an upper constraint is necessary: their API is more than stable, and they both emit deprecation warnings in advance. I'm going to check for deprecation warnings when running tests, and check if they pass with numpy 2.0.0 (from master) as well.

@behackl This is finally ready for review and tests passes. The diff may seem overloaded but most of the edited files are imports cleanup (from click to cloup).


contractimport fails when imported contract defines a contracterror

What version are you using?
0.2.0
What did you do?
Importing contracts with the macro contractimport fails for contracts with an Error enum defined as shown in the examples.
See example branch (and pardon the bad naming... with_event -> with_error): https://github.com/mootz12/soroban-examples/tree/bug/import_contract_with_event/example_error_consumer

What did you expect to see?
The contract to be successfully imported.
What did you see instead?
error[E0507]: cannot move out of `*val` which is behind a shared reference
 --> example_error_consumer/src/lib.rs:6:5
  |
6 | /     soroban_sdk::contractimport!(
7 | |         file = "../target/wasm32-unknown-unknown/release/soroban_errors_contract.wasm"
8 | |     );
  | |_____^ move occurs because `*val` has type `error_contract::Error`, which does not implement the `Copy` trait
  |
  = note: this error originates in the attribute macro `soroban_sdk::contracterror` (in Nightly builds, run with -Z macro-backtrace for more info)

Where the Error in question does implement Copy:
https://github.com/mootz12/soroban-examples/blob/bug/import_contract_with_event/errors/src/lib.rs#L4-L9

Thanks for identifying this issue @mootz12. I've published a fix in v0.2.1.


Proposal: Dockerfile add BIND_CONTEXT

Currently I have mostly-useless commands in my Dockerfile like
ADD stuff /docker_setup
RUN /docker_setup/install.sh && rm -rf /docker_setup
This is ugly.  Can we have:
BIND_CONTEXT /docker_context
RUN /docker_context/stuff/install.sh
I'm not picky about the syntax.  I want to have docker build do what docker run -v does, but during the build process.

This proposal as stated here has two problems.

It creates unnecessary extra work. If I already have the stuff I need for my build in, say, /var/apt/cache - and I want it to be available during my (OFFLINE!) build, at /var/apt/cache inside the container, then this requires a bunch of extra and generally unnecessary steps, involving symlinking or bind-mounting inside my host and inside my container.

The word "CONTEXT" is not unambiguous as to the use case. What would people needing this search for, and which one of the many contexts does the word context refer to? Does docker need yet another unintuitive verb? ... They would search  for "BIND" or "MOUNT" or "LOCAL" or "TEMP" or "OFFLINE" or... just maybe... "BUILDCONTEXTBINDMOUNT"  :-p

Let's recap the use case: You're offline, or in a secure environment, or you want secrets in your build that need not remain in your image. You want a command that will only be run on a certain "home" host, and will not cause an error on another, but you don't want people to hack together various solutions to something that can easily be solved.
I've read all the text in all the linked tickets and the only potential criticism comes from @tianon who is concerned with the cache (https://github.com/docker/docker/pull/5369) - I've not looked into how and what docker caches, but the logical counter to that is that nothing that is bind-mounted into the build-context, will end up in the final image, or necessarily changing the final image, and as such should not affect the cache, unless something in there results in different files being generated- or copied to/in the build - which it should not in most instances.
If I have a local copy of all the .deb files I'll need, I can just BINDMOUNT /var/cache/apt/distfiles:/var/cache/apt/distfiles and my stupid docker won't have to download 500MB of data from the other side of the planet everytime I try to generate an image locally.
If I have a directory with a generic key, and a config file for a database to pull into my image, but I also have a secure/development key and a local database thats much faster, then I'd like to be able for local build to use my local stuff, by just overloading the directory with the configs. If it's not there, the image will still build, but it will use the generic/globally available resources.
Yes there's a security issue: A docker pull and run can read your local filesystem, which we don't want. Especially since a lot of people run docker as root. Simple: ignore all these commands, unless a special command line switch is given. And display a warning.
But thats the point, you want these commands ignored, unless you're in a home environment. The main purpose of these commands is to work on rapidly creating and fine tuning images, in an offline environment if you want.

I challenge any of the docker developers/maintainers to try and work with docker in an offline or poor-connectity environment, and see what irks you and what solutions you come up to deal with it...

I've not looked into how and what docker caches, but the logical counter to that is that nothing that is bind-mounted into the build-context, will end up in the final image, or necessarily changing the final image, and as such should not affect the cache

I think you may be confused about intent of BINDCONTEXT (caching data was no the goal)
The main purpose is to bind files so that they can be processed in the subsequent RUN commands and the result ends up in the image.
Typically you mount your sources with BINDCONTEXT and issue a RUN to build the binaries. The binaries depend on the content of sources so you want them to be properly fingerprinted. Plus everything happens exclusively on server-side, so you are guaranteed to have no user-induced side effects.
The criticism from @tianon was not aimed at this proposal but at a comment from someone who suggested to bind the context implicitly at every build.
Caching data for subsequent builds is a very valuable objective, but I would largely favour methods that are free of any uncontrolled side effect (eg. #4962 #9553)
Regarding the word 'context' I think the meaning is pretty clear in docker's builder:
	$ curl -s http://docs.docker.com/reference/builder/| grep -oi context |wc -l
	27

(anyway I would not mind having a better name)

Hello!
We are no longer accepting patches to the Dockerfile syntax as you can read about here: https://github.com/docker/docker/blob/master/ROADMAP.md#22-dockerfile-syntax
Mainly:

Allowing the Builder to be implemented as a separate utility consuming the Engine's API will open the door for many possibilities, such as offering alternate syntaxes or DSL for existing languages without cluttering the Engine's codebase

Then from there, patches/features like this can be re-thought. Hope you can understand.

To implement something like this does not require any extension to Dockerfile syntax. The build content could be made available over HTTP at some predefined address where it could be picked up by a curl or similar during RUN command.

Goes without saying that there are numerous "hacky" workarounds, but all of
them require you to either modify the guest, poison DNS, or run a special
Web server.
Which is why I don't get why the docker maintainers don't get it - doing
things like this is already possible, so why not just streamline /
standardize it and save everyone a lot of pain?
What if you can't or don't want to modify the guest for aesthetic reasons.
Ie. You want to use the unmodified distribution of an OS, but you want it
to be able to use your local offline data cache or ssh keys if they are
available, to speed up your build?
I've since gotten gigabit Internet, so this hasn't been a need, else I
would've fixed it myself... but I still pity anyone who tries to use docker
offline or in the 3rd world where data costs $200/Gb. Very egalitarian.
To implement something like this does not require any extension to
Dockerfile syntax. The build content could be made available over HTTP at
some predefined address where it could be picked up by a curl or similar
during RUN command.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/3056#issuecomment-213832893

To make this 100% clear: this feature request was never about any sort of caching.  It was to improve the situation when I have contents (code, scripts, configuration, big tarballs, whatever) in the Dockerfile context directory and I want scripts in the Dockerfile to be able to access it without manually ADDing every file.

I think it would be easier to just make the build context available via some well-known mount point in the build containers - like /_bc   or /_docker_bc  then you could run/copy/whatever files directly from there w/o them being in the image.  I even had some prototype code for this as part of a different piece of work.  What I like about this is that it doesn't require a change to the Dockerfile and you can just any normal shell commands to access it - no need for http stuff.

Certainly... or you could kill two birds with one stone and achieve so much
more with the same amount of effort.
Once again, for me first prize is to be able to use unmodified guests. Say
you want the startup of some service in your guest to run differently for
whatever reason - simple just overload the relevant file or path.
If you make it a fixed path, you're enforcing something on a lot of people.
If it's configurable, docker is friendlier as it can adapt to things that
are already in place.

My use case is to run a compiler or preprocessor during Docker build. When one use COPY or ADD before the RUN the source ends up in the image bringing unnecessary bloat. That cannot be removed as COPY and RUN belong to different image layers so doing rm during the build does not remove the files from the image.
One possible workaround for that is to expose the source over HTTP so one can use curl or similar to get it during RUN before executing the compiler. Another one is to use a staged build when one first build image with the compiler, then run it to compile the sources and then build the final image from the results. These are non-standard and require tools beyond the docker.

To give some feedback about this issue (as the author of #5369), i have used this feature since v0.11 and i still rely a lot on it to reduce the size of my images. But i stopped maintaining #5369 after v1.7 and developed a simpler patch (named tmp-volume).
This new patch mounts /tmp from a temporary directory during the whole build. Everything that lands in /tmp is dropped when the build is complete and it is actually never committed into any layer. Compared to BINDCONTEXT, it is much less intrusive in the code, and it can be used to include only a part of the context. For those interested, it is up do date with v1.10.3.

@duglin: note that setting up a permanent mount point like /_bc or /_docker_bc would do more harm than good in practice because it prevents caching the intermediate stages of the build (changing a single bit anywhere in the context would invalidate the whole cache). The whole point about BINDCONTEXT is that it works like COPY (including fingerprinting of the content) except that the content is stored outside the image.
For builds including a compilation (@ibukanov case), though i used  BINDCONTEXT a lot in the beginning, I now prefer building a separate image for the compiler for two reasons : (1.) I don't want the compiler in the final image (2.) some tools (e.g maven) implement their own cache to speed up successive builds but their cache is useless when run inside a dockerfile. To facilitate these multi-stage builds I developed a separate command docker-rundev.

This feature is now available in the experimental Dockerfile syntax; see the Dockerfile frontend experimental syntaxes
Create a "build context" to work with; this would normally be your source files :smile:
mkdir my-context && cd my-context
echo this is a file in my context > file1.txt
mkdir subdir
echo this is a file in subdir > subdir/file2.txt

Make sure buildkit is enabled:
export DOCKER_BUILDKIT=1

You can use files from the bind-mounted context with the --mount option. These files are accessible during build, but are not copied to the image, so it's a great way to (e.g.) build source-code without the source code itself ending up in the image.
This example bind-mounts the whole build-context. Note that src=/ is relative to the root of your build-context, not an absolute path on your host. In this example, we're copying a file from the bind-mounted context to a file named foo.txt at the root of the container. This is obviously not a very useful thing to do (COPY file1.txt /foo.txt would've done the same), but it's just an example; this step could've been a make && make install.
docker build -t example -f- . <<EOF
# syntax=docker/dockerfile:1.0-experimental
FROM busybox
RUN --mount=src=/,target=/foo cp /foo/file1.txt /foo.txt
EOF

Running the image you can see that the "build artefacts" (foo.txt) is in the image:
docker run --rm example cat /foo.txt
this is a file in my context

But the source files are not;
docker run --rm example cat /foo/file1.txt
cat: can't open '/foo/file1.txt': No such file or directory

Note that the build-context is still sent to the daemon, so when you're bind-context, files are mounted from a copy of your local files that resides on the daemon's host.
Instead of bind-mounting your whole build-context, you can also mount just a subdirectory. BuildKit is smart enough to only send what's needed, so bind-mounting just what you need can improve build speed;
docker build -t example2 -f- . <<EOF
# syntax=docker/dockerfile:1.0-experimental
FROM busybox
RUN --mount=src=/subdir,target=/foo cp /foo/file2.txt /foo2.txt
EOF

And you can verify it worked;
docker run --rm example2 cat /foo2.txt
this is a file in subdir

By default, binds are read-only, but you can mount writable. However, changes are not persisted (this is by design), so the second RUN in this Dockerfile will fail
docker build -t example3 -f- . <<EOF
# syntax=docker/dockerfile:1.0-experimental
FROM busybox

RUN --mount=src=/,target=/writable,rw echo new file > /writable/new-file.txt
RUN --mount=src=/,target=/writable,rw cat /writable/new-file.txt
EOF

...
=> [2/3] RUN --mount=src=/,target=/writable,rw echo new file > /writable/new-file.txt                                                     2.6s
 => ERROR [3/3] RUN --mount=src=/,target=/writable,rw cat /writable/new-file.txt                                                           2.7s
------
 > [3/3] RUN --mount=src=/,target=/writable,rw cat /writable/new-file.txt:
#11 2.088 cat: can't open '/writable/new-file.txt': No such file or directory
------
rpc error: code = Unknown desc = executor failed running [/bin/sh -c cat /writable/new-file.txt]: exit code: 1


python3Packages.ipfshttpclient: 0.4.2.post1 -> 0.6.1, rename from ipfsapi

Motivation for this change
This adds ipfshttpclient from https://github.com/ipfs-shipyard/py-ipfs-http-client, which has been renamed from ipfsapi.
The patch changing VERSION_MAXIMUM is needed because this library hardcodes a maximum version of IPFS, which is older then the version currently in nixpkgs. It seems to work just fine though.
I think completely removing the old ipfsapi package is fine since that version is from 2017. And while a compatibility layer has been written to make migrations easier, it stopped getting updates at the end of 2019 according to https://github.com/ipfs-shipyard/py-ipfs-http-client/blob/910d11f87f1e22a1d07a684a2ca3852841e07bd7/ipfsapi/init.py#L8 and also only works with versions 0.4.x of this library, not 0.5.x or even 0.6.x. To package the compatibility layer, we would need to either patch it to work with the latest version or package an outdated version of this package as well.
The tests start an IPFS daemon, which listens on some ports. The build is usually sandboxed and without internet connection, so this should be perfectly fine, right?
I kept the original maintainer @mguentner, even though he hasn't updated the package since 2017.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 115984 at 20b4d704 run on x86_64-linux 1

1 package built successfully:

python38Packages.ipfshttpclient

1 suggestion:

warning: unused-argument
Unused argument: python3.
Near pkgs/development/python-modules/ipfshttpclient/default.nix:5:3:
  |
5 | , python3
  |   ^

I removed the unused argument.

I replaced pytest-ordering with  pytest-order, which is a maintained fork.
I also updated ipfshttpclient to 0.7.0, which is the latest version.
Please review.

Thank you for updating the title of this PR to reflect the change in the commit. I forgot to change it.


⚠ API - Lens has degraded performance

In 9427d4e, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 363 ms

Resolved: API - Lens performance has improved in d806b95 after 8 minutes.


Error reading sample_to_species_mapping.txt

When I try to run the primate example with the latest release (2.0.0-alpha.1), I get an unexpected behavior when using the accompanying sample_to_species_mapping.txt file. The output window goes blank (white) after half a second, and nothing else happens.
I can run the same release on the same files without the sample_to_species_mapping.txt file without problem.
I can replicate the behavior on my laptop and LUMC computer.

This already fixed in the current GitHub version. As a workaround, you an also select a difference comparison order (e.g. random).
The cause is that with this dataset, the first comparison happens between two files of the Gorilla_gorilla species. When a sample-to-species file is used, the "comparems-to-distancematrices" executable outputs the distance between species, not between samples. In this case, there is only one specie, causing the output distance matrix to be empty. In the 2.0.0-alpha1  version, the phylotree javascript crashed when there is only once node and no distance. This is now fixed.


fix for smarty security issue during ajax calls

changed order of addTemplateDir call
function will be now called before ajax request check
solves issue with smarty security during ajax calls

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/PT-9940
Please use this issue to track the state of your pull request.


Consumer Cancel Notification

Does Wascally support Consumer Cancel Notification?
https://www.rabbitmq.com/consumer-cancel.html

@vilmysj - check out rabbot, it handles them implicitly. As an example, you can go into the dashboard, delete a queue that has bindings and an active subscription and rabbot will log that a consumer cancel took place, re-create the queue, the binding and re-start the subscription.


Adding zoom effect (on hover) on the coin cards of "top 10 cryptocurrencies of the world"

@arnab2001 plz assign me this issue under jwoc 2k23

https://user-images.githubusercontent.com/79015311/221130429-8d7f6197-f367-4a79-9c4e-f056d8ad56d8.mp4
@arnab2001 shall i create pr?? but before that plz assign me and give the appropriate labels.....

Sure , great job

Assigned you the issue with proper lable

pr sent

new pr sent


Add mitchell kernel

Pull request for #1432. Adds newly available (as of libvips 8.7.0) Mitchell-Netravali spline as a resize kernel option.

Coverage remained the same at 98.972% when pulling 6f5e40bd1bbdd7a53aab16dc1ffcffc6456c8a33 on Daiz:add-mitchell-kernel into 95ef6b3f71ca637bc4894332e92cda1bd728aea5 on lovell:master.

Thank you!


Merchant Add: Software Development

Hey @erciccione,
Please, add IdeaSoft (website https://i-deasoft.com) as
"IdeaSoft - Full-cycle Software Development"
Thanks!

Don't know why but didn't get the notification for this.
Added in #530 . Thank you
+merchant
+in progress

Thanks!


feat: create employer standards navigation area

New top-level menu navigation for Employer Standards

:tada: This PR is included in version 3.3.0-next.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix docker hooks directory

See https://github.com/Senzing/stream-loader/issues/284

Pull requests:

https://github.com/Senzing/docker-aptdownloader/pull/20


Use kuttl collectors to improve logs gathering

Kuttl introduced collectors  https://kuttl.dev/docs/testing/reference.html#collectors, these definitions should help gather logs from the cluster in case the test fails. The scope of this ticket is to select one test in our integration test suite and enrich it with a collector.
DoD

[ ] add the collector to a test
[ ] verify that the integration tests pipeline still passes
[ ] comment on this ticket how the logs look like and how we could integrate them to the current pipeline results

Ref
https://kudo.dev/blog/blog-2020-06-29-kuttl-v0.5.0.html#pod-log-collector

@prakrit55 will you take this one?

Yes, I will work on it.

thank you! 😸

Hello @RealAnna ,
On passing one of a integration test I got the test pass with the log-
=== RUN   kuttl
harness.go:462: starting setup
harness.go:252: running tests using configured kubeconfig.
harness.go:275: Successful connection to cluster at: https://<IP_ADDRESS>:8443
harness.go:360: running tests
harness.go:73: going to run test suite with timeout of 10 seconds for each step
harness.go:372: testsuite: . has 1 tests
=== RUN   kuttl/harness
=== RUN   kuttl/harness/e2e
=== PAUSE kuttl/harness/e2e
=== CONT  kuttl/harness/e2e
logger.go:42: 19:55:05 | e2e | Ignoring example-test as it does not match file name regexp: ^(\d+)-(?:[^.]+)(?:.yaml)?$
logger.go:42: 19:55:05 | e2e | Creating namespace: kuttl-test-accurate-sawfish
logger.go:42: 19:55:05 | e2e | e2e events from ns kuttl-test-accurate-sawfish:
logger.go:42: 19:55:05 | e2e | Deleting namespace: kuttl-test-accurate-sawfish
=== CONT  kuttl
harness.go:405: run tests finished
harness.go:513: cleaning up
harness.go:570: removing temp folder: ""
--- PASS: kuttl (5.84s)
--- PASS: kuttl/harness (0.00s)
--- PASS: kuttl/harness/e2e (5.22s)
PASS
I enriched an assert file with testassert with collectors in it
Went to the parent directory and cmd kubectl kuttl test . The tests being in the lowermost dir.

ubuntu@keptn-tst:~/tests$ cat kuttl-report.xml

 With the following reports

ubuntu@keptn-tst:~/tests$ cat kuttl-report.xml
testsuites name="" tests="1" failures="0" time="5.839">
testsuite tests="1" failures="0" timestamp="2023-07-19T19:55:05.58954915Z" time="0.012" name=".">
testcase classname="." name="e2e" timestamp="2023-07-19T19:55:05.589709009Z" time="0.012" assertions="0">
/testcase>
/testsuite>
/testsuites>
 With the following reports

Hi @prakrit55 sounds great 🚀 can you link a branch with your test to this issue so that we have it documented and can see it running in the pipeline too?

Hey, @RealAnna, I fed the annotated-namespace-not-enabled's assert with a collector and renaming the container in the deployment with non-existent container name, it produced the following logs:
=== CONT  kuttl/harness/annotated-namespace-not-enabled
logger.go:42: 14:12:16 | annotated-namespace-not-enabled/0-install | test step failed 0-install
logger.go:42: 14:12:16 | annotated-namespace-not-enabled/0-install | collecting log output for [type==pod,label: app=test,container: busybox]
logger.go:42: 14:12:16 | annotated-namespace-not-enabled/0-install | running command: [kubectl logs --prefix -l app=test -n kuttl-test-true-woodcock -c busybox --tail=10]
logger.go:42: 14:12:16 | annotated-namespace-not-enabled/0-install | Error from server (BadRequest): container "busybox" in pod "test-69c65d4f67-524n5" is waiting to start: trying and failing to pull image
case.go:364: failed in step 0-install
logger.go:42: 14:12:16 | annotated-namespace-not-enabled | annotated-namespace-not-enabled events from ns kuttl-test-true-woodcock:
logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:35 +0000 UTC    Normal  Pod test-69c65d4f67-524n5               Scheduled  Successfully assigned kuttl-test-true-woodcock/test-69c65d4f67-524n5 to minikube
logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:35 +0000 UTC    Normal  ReplicaSet.apps test-69c65d4f67         SuccessfulCreate    Created pod: test-69c65d4f67-524n5
logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:35 +0000 UTC    Normal  Deployment.apps test            ScalingReplicaSet  Scaled up replica set test-69c65d4f67 to 1
logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:38 +0000 UTC    Normal  Pod test-69c65d4f67-524n5.spec.containers{busybox} Pulling  Pulling image "usybox"
logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:42 +0000 UTC    Warning Pod test-69c65d4f67-524n5.spec.containers{busybox} Failed   Failed to pull image "usybox": rpc error: code = Unknown desc = Error response from daemon: pull access denied for usybox, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:43 +0000 UTC    Warning Pod test-69c65d4f67-524n5.spec.containers{busybox} Failed   Error: ErrImagePull
logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:44 +0000 UTC    Normal  Pod test-69c65d4f67-524n5.spec.containers{busybox} BackOff  Back-off pulling image "usybox"
It thereby states that the container name is mistaken as "usybox".

Hey, @RealAnna, I fed the annotated-namespace-not-enabled's assert with a collector and renaming the container in the deployment with non-existent container name, it produced the following logs:
=== CONT kuttl/harness/annotated-namespace-not-enabled logger.go:42: 14:12:16 | annotated-namespace-not-enabled/0-install | test step failed 0-install logger.go:42: 14:12:16 | annotated-namespace-not-enabled/0-install | collecting log output for [type==pod,label: app=test,container: busybox] logger.go:42: 14:12:16 | annotated-namespace-not-enabled/0-install | running command: [kubectl logs --prefix -l app=test -n kuttl-test-true-woodcock -c busybox --tail=10] logger.go:42: 14:12:16 | annotated-namespace-not-enabled/0-install | Error from server (BadRequest): container "busybox" in pod "test-69c65d4f67-524n5" is waiting to start: trying and failing to pull image case.go:364: failed in step 0-install
logger.go:42: 14:12:16 | annotated-namespace-not-enabled | annotated-namespace-not-enabled events from ns kuttl-test-true-woodcock: logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:35 +0000 UTC Normal Pod test-69c65d4f67-524n5 Scheduled Successfully assigned kuttl-test-true-woodcock/test-69c65d4f67-524n5 to minikube logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:35 +0000 UTC Normal ReplicaSet.apps test-69c65d4f67 SuccessfulCreate Created pod: test-69c65d4f67-524n5 logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:35 +0000 UTC Normal Deployment.apps test ScalingReplicaSet Scaled up replica set test-69c65d4f67 to 1 logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:38 +0000 UTC Normal Pod test-69c65d4f67-524n5.spec.containers{busybox} Pulling Pulling image "usybox" logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:42 +0000 UTC Warning Pod test-69c65d4f67-524n5.spec.containers{busybox} Failed Failed to pull image "usybox": rpc error: code = Unknown desc = Error response from daemon: pull access denied for usybox, repository does not exist or may require 'docker login': denied: requested access to the resource is denied logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:43 +0000 UTC Warning Pod test-69c65d4f67-524n5.spec.containers{busybox} Failed Error: ErrImagePull logger.go:42: 14:12:16 | annotated-namespace-not-enabled | 2023-07-28 14:05:44 +0000 UTC Normal Pod test-69c65d4f67-524n5.spec.containers{busybox} BackOff Back-off pulling image "usybox"
It thereby states that the container name is mistaken as "usybox".

Hi @prakrit55 it looks like some funny cli escape, maybe you could try to pass -c 'busybox' using quotes

No, I was expecting the error from the collectors by troubling the name of the container. Do you think this is what we want to achieve from this ticket ? Since the collectors are limited only to the pods and commands, do u think its viable?

@prakrit55 let's have a look at the pr and we can discuss about this!

reopen required


Zend/Mvc/Router/Http/Literal and Part

Need validate tests, maybe wrong use case

Problem with Segment route with $pathOffset != Null.
pattern in preg_match finds only first letter in path request.
https://github.com/AndrejAndb/zf2/blob/work/Mvc_Route/library/Zend/Mvc/Router/Http/Segment.php#L250

Reviewed, merged, and pushed to master. I updated the tests to use a dataProvider -- makes the test simpler. I see the failing test, and will work with DASPRiD to try and fix it.


Some Small Recommendations

Summary
Nothing groundbreaking here, but a few small recommendations, mostly around project organization preferences and niceties that I've built up after my few years programming.
Changes

Adds gitignore
Adds shell to code blocks in README.md so that they render with syntax highlighting on GitHub
Moves source code into src directory to make the repo a little prettier :)
Outputs built artifact to build/ directory
Adds a Makefile, a habit I tend to like
A couple other notes I'll add inline

Notes
Since I moved the make_mod.sh script, it shows up as a new file in the diff. Go here to see my comments on the actual diff: https://github.com/audiophyl/qnxdemotools/pull/1/files/0e0900b0d7c08fe9f75c4ff8a687033768a12607#diff-cdefa21107232705f04f9ed5ff7cc8ec328cd26802848a271a1caf3dbdb5e21a

Here's a good primer on Makefiles: https://rosszurowski.com/log/2022/makefiles
Specifically the section on "a consistent interface for scripts": https://rosszurowski.com/log/2022/makefiles#a-consistent-interface-to-project-scripts

hey hey, doing a little cleanup, so I'm going to close this PR. Feel free to re-open if you'd like.


Error playing TIKTOK videos

Hello, I have detected a problem when playing videos from the TIKTOK platform from the browser on Android, and is that since version 97.0.1072.78 are no longer played, ie, before if everything worked but in the new versions you have touched something in the code that no longer play.
Attached is a video showing that in the previous version it plays and in the new one it does not.
https://github.com/MicrosoftEdge/DevTools/assets/86065304/6424cf0d-afaf-4b79-bea1-e6c6f66cfbea

Thanks for reaching out and sorry about the issue you're facing. However, this repository is specific to DevTools. DevTools is a developer feature in Edge which has nothing to do the Edge app for Android, or with playing videos.
Can you please send your feedback again by using the browser's feedback mechanism? Here's how:
On Desktop:

Click Settings and more (the ... button in the top-right corner of the browser).
Click Help and feedback.
Click Send feedback.

On Mobile:

Tap the hamburger menu icon at the bottom-right corner.
Swipe right to display the second page of options.
Tap Help and feedback.

Thank you for your understanding.


WIP: test on tubi defined version

This is the diff from manifests for coredns
--- old.yaml    2023-03-08 18:08:28
+++ new.yaml    2023-03-08 18:05:25
@@ -1,6 +1,4 @@

-# Based on coredns/deployment/kubernetes/coredns.yaml.sed v1.8.3
----
 apiVersion: v1
 kind: ServiceAccount
 metadata:
@@ -73,6 +71,19 @@
         reload
         loadbalance
     } # STUBDOMAINS - Rancher specific change
+
+    tubi {
+      errors
+      template ANY AAAA {
+        rcode NXDOMAIN
+      }
+      prometheus :9153
+      forward . <IP_ADDRESS>
+      cache
+      health localhost:8092 {
+        lameduck 30s
+      }
+    }
 ---
 apiVersion: apps/v1
 kind: Deployment
@@ -83,9 +94,6 @@
     k8s-app: kube-dns
     kubernetes.io/name: "CoreDNS"
 spec:
-  # replicas is not specified in upstream template, default is 1.


Integrate with Quasar Framework

They have a really nice components that works with web and mobile
http://quasar-framework.org/components/
It would make people more interested to use weex if it's ported here.

This PR/issue doesn't received response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


i3 module: can only see the current workspace

Hello,
I am currently trying to show my i3 workspaces on my bar, but unfortunately without any success. I am only seeing the current workspace (icon).
My polybar version:
polybar 3.3.0-89-gcb75857f

Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) -render -damage -sync +composite +xkb +xrm +xcursor

Build type: Release
Compiler: /usr/bin/c++
Compiler flags: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -Wall -Wextra -Wpedantic -O3 -DNDEBUG
Linker flags: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now

My i3 module config:
[module/i3]
type = internal/i3

format = <label-state>
format-offset = -20

label-focused = %icon%
label-occupied = %icon%
label-visible = %icon%
label-focused-padding = 2
label-occupied-padding = 2
label-visible-padding = 2
label-focused-font = 3
label-occupied-font = 3
label-visible-font = 3

label-focused-underline = #ea3520
label-focused-background = #db6060

pin-workspaces = false
enable-scroll = false
reverse-scroll = false

ws-icon-0 = code;
ws-icon-1 = terminal;
ws-icon-2 = firefox;
ws-icon-3 = music;
ws-icon-4 = dl;

I tried to debug my config with polybar -l info and polybar -l trace but I didn't see any errors.
Thank you very much in advance for any help.

Can you post a screenshot of your bar as well as a screenshot of the i3bar (comes with i3) so we can see how the module should look like

Here is what my bar looks like:

Here is what my i3bar looks like:

My i3bar only has this config:
bar {
}

I can't see the problem here, your two bars show the same workspaces.
Don't forget that i3wm destroys workspaces if they are empty

Don't forget that i3wm destroys workspaces if they are empty.

Okay, now I understand, thank you


[#6303] Apply spring profile to flink

Codecov Report

Merging #6318 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #6318      +/-   ##
=========================================
+ Coverage    39.6%   39.6%   +<.01%
=========================================
  Files        3065    3065
  Lines       91413   91413
  Branches    11839   11839
=========================================
+ Hits        36203   36208       +5
+ Misses      52227   52224       -3
+ Partials     2983    2981       -2

Impacted Files
Coverage Δ

...navercorp/pinpoint/rpc/common/SocketStateCode.java
82.92% <0%> (-2.44%)
:arrow_down:

...om/navercorp/pinpoint/rpc/codec/PacketDecoder.java
57.44% <0%> (-2.13%)
:arrow_down:

...cluster/zookeeper/ZookeeperClusterDataManager.java
56.12% <0%> (-1.94%)
:arrow_down:

...java/com/navercorp/pinpoint/rpc/DefaultFuture.java
72.5% <0%> (-1.67%)
:arrow_down:

...ollector/cluster/zookeeper/ZookeeperJobWorker.java
79.53% <0%> (-1.4%)
:arrow_down:

...pinpoint/profiler/monitor/DeadlockMonitorTask.java
18.6% <0%> (-1.17%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
72.07% <0%> (-0.33%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
79.92% <0%> (+0.7%)
:arrow_up:

...vercorp/pinpoint/web/vo/ApplicationAgentsList.java
69.23% <0%> (+2.56%)
:arrow_up:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
73.33% <0%> (+3.33%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


Adding appropriate inbound triples based on LDP containment properties

adding IT to cover typical PCDM use case of proxies

Fixes https://jira.duraspace.org/browse/FCREPO-1497

Resolved with: https://github.com/fcrepo4/fcrepo4/commit/8845a22fdeffbec07bb0d0abd35ec9fd3854e788


Consider not using BlockingQueue but just Lock/Conditions in SourceTask

The SourceTask#poll API specifies that we should block to wait for data, but it should be interruptible when stop is called. At the moment it's not, we simply block for 5 seconds until there is data, and if no data is available return control to the caller (which, unless stopping, will just call poll again).
So it could be a little nicer to allow poll to be interrupted by using a combination of ReetrantLock and Condition instead of the BlockingQueue, as suggested by @Zelldon.

Not relevant anymore


Introduce the ROCMINFO_PATH variable to override hard-coded rocm_agent_enumerator location

In the spack package manager we do not provide a bin/ or lib/ folder in the prefix. The problem is that hipcc expects the bin/ folder to exist. This PR introduces a variable ROCMINFO_PATH which can be set to the rocminfo package root folder, such that rocm_agent_enumerator can still be located.

Why not have hipcc find rocm_agent_enumerator in the PATH? Spack will add that package to the PATH if its set as a runtime dependency. This seems better than creating another custom env variable.

@pfultz2 can we get a change like this in? In spack there's been a patch since 3.5.0 to fix this issue, would be nice to drop it at some point.

Closing all existing pull requests that do not target the develop branch. In case this pull request is still valid, please rebase your changes against develop branch and resubmit.


UI - issues with userconfig

[x] no username displayed in horizontal main nav bar (admin user);  after clicking  "settings - users - sync to ldap" the issue goes away

[ ] logout/login sometimes fails on first try: the re-login (same user or other user) sometimes fails with error Maybe backend (API or database) is unreachable. Please contact administrator

might be related to new roles changes in request module (because user admin with admin role) has a problem here
might best be reproduced by creating a new user (e.g. auditor) and logging in with this user afterwards
a reload fixes it (leads to login)

[ ] @Y4nnikH :  When logging out as some user and logging in as admin next, the before logged in username will be displayed in the nav bar.

[ ] JWT refresh leads to "Username must not be empty" error

2022-10-12T08:00:01.879068+02:00 fwo-ubu22-desktop fworch-ui:  2022-10-12T08:00:01+02:00 Error - API Connection (GraphQlApiConnection.cs in line 103), Error while sending query to GraphQL API. Caught by GraphQL client library.
2022-10-12T08:00:01.879159+02:00 fwo-ubu22-desktop fworch-ui:  Message: Your requested role is not in allowed roles
2022-10-12T08:00:01.879709+02:00 fwo-ubu22-desktop fworch-ui:  2022-10-12T08:00:01+02:00 Error - API Connection (GraphQlApiConnection.cs in line 138), Error while sending query to GraphQL API. Query: query getUserByDn($dn: String!) {
2022-10-12T08:00:01.879753+02:00 fwo-ubu22-desktop fworch-ui:    uiuser(where: {uuid: {_eq:  $dn } }) {
2022-10-12T08:00:01.879775+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_id
2022-10-12T08:00:01.879793+02:00 fwo-ubu22-desktop fworch-ui:      uuid
2022-10-12T08:00:01.879811+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_username
2022-10-12T08:00:01.879930+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_language
2022-10-12T08:00:01.879968+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_password_must_be_changed
2022-10-12T08:00:01.879987+02:00 fwo-ubu22-desktop fworch-ui:    }
2022-10-12T08:00:01.880005+02:00 fwo-ubu22-desktop fworch-ui:  }
2022-10-12T08:00:01.880023+02:00 fwo-ubu22-desktop fworch-ui:  , variables: {"dn":"uid=admin,ou=tenant0,ou=operator,ou=user,dc=fworch,dc=internal"}
2022-10-12T08:00:01.880041+02:00 fwo-ubu22-desktop fworch-ui:   ---
2022-10-12T08:00:01.880058+02:00 fwo-ubu22-desktop fworch-ui:  Exception thrown:
2022-10-12T08:00:01.880076+02:00 fwo-ubu22-desktop fworch-ui:   Exception
2022-10-12T08:00:01.880097+02:00 fwo-ubu22-desktop fworch-ui:  Message:
2022-10-12T08:00:01.880115+02:00 fwo-ubu22-desktop fworch-ui:   Your requested role is not in allowed roles
2022-10-12T08:00:01.880137+02:00 fwo-ubu22-desktop fworch-ui:
2022-10-12T08:00:01.880155+02:00 fwo-ubu22-desktop fworch-ui:  Stack Trace:
2022-10-12T08:00:01.880300+02:00 fwo-ubu22-desktop fworch-ui:   at FWO.Api.Client.GraphQlApiConnection.SendQueryAsync[QueryResponseType](String query, Object variables, String operationName) in /usr/local/fworch/lib/files/FWO.Api.Client/GraphQlApiConnection.cs:line 107

second sample log for requester1 which has roles requester and approver:
2022-10-12T14:49:59.591889+02:00 fwo-ubu22-desktop fworch-ui:  2022-10-12T14:49:59+02:00 Audit - AuthenticateUser (AuthStateProvider.cs in line 69), user requester1 successfully authenticated
2022-10-12T14:49:59.695951+02:00 fwo-ubu22-desktop fworch-ui:  2022-10-12T14:49:59+02:00 Error - API Connection (GraphQlApiConnection.cs in line 103), Error while sending query to GraphQL API. Caught by GraphQL client library.
2022-10-12T14:49:59.696070+02:00 fwo-ubu22-desktop fworch-ui:  Message: Your requested role is not in allowed roles
2022-10-12T14:49:59.714098+02:00 fwo-ubu22-desktop fworch-ui:  2022-10-12T14:49:59+02:00 Error - API Connection (GraphQlApiConnection.cs in line 138), Error while sending query to GraphQL API. Query: query getUserByDn($dn: String!) {
2022-10-12T14:49:59.714236+02:00 fwo-ubu22-desktop fworch-ui:    uiuser(where: {uuid: {_eq:  $dn } }) {
2022-10-12T14:49:59.714307+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_id
2022-10-12T14:49:59.714371+02:00 fwo-ubu22-desktop fworch-ui:      uuid
2022-10-12T14:49:59.714457+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_username
2022-10-12T14:49:59.714540+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_language
2022-10-12T14:49:59.714589+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_password_must_be_changed
2022-10-12T14:49:59.714627+02:00 fwo-ubu22-desktop fworch-ui:    }
2022-10-12T14:49:59.714662+02:00 fwo-ubu22-desktop fworch-ui:  }
2022-10-12T14:49:59.714696+02:00 fwo-ubu22-desktop fworch-ui:  , variables: {"dn":"uid=requester1,ou=tenant0,ou=operator,ou=user,dc=fworch,dc=internal"}
2022-10-12T14:49:59.714731+02:00 fwo-ubu22-desktop fworch-ui:   ---
2022-10-12T14:49:59.714785+02:00 fwo-ubu22-desktop fworch-ui:  Exception thrown:
2022-10-12T14:49:59.714826+02:00 fwo-ubu22-desktop fworch-ui:   Exception
2022-10-12T14:49:59.714855+02:00 fwo-ubu22-desktop fworch-ui:  Message:
2022-10-12T14:49:59.714884+02:00 fwo-ubu22-desktop fworch-ui:   Your requested role is not in allowed roles
2022-10-12T14:49:59.714923+02:00 fwo-ubu22-desktop fworch-ui:
2022-10-12T14:49:59.714986+02:00 fwo-ubu22-desktop fworch-ui:  Stack Trace:
2022-10-12T14:49:59.715039+02:00 fwo-ubu22-desktop fworch-ui:   at FWO.Api.Client.GraphQlApiConnection.SendQueryAsync[QueryResponseType](String query, Object variables, String operationName) in /usr/local/fworch/lib/files/FWO.Api.Client/GraphQlApiConnection.cs:line 107

2022-10-14 - could still reproduce issue in current develop branch:
user us2 has roles reviewer, fw-admin, planner
2022-10-14T17:38:15.054570+02:00 fwo-ubu22-desktop fworch-ui:  2022-10-14T17:38:15+02:00 Audit - AuthenticateUser (AuthStateProvider.cs in line 69), user us2 successfully authenticated
2022-10-14T17:38:15.122710+02:00 fwo-ubu22-desktop fworch-ui:  2022-10-14T17:38:15+02:00 Error - API Connection (GraphQlApiConnection.cs in line 103), Error while sending query to GraphQL API. Caught by GraphQL client library.
2022-10-14T17:38:15.122845+02:00 fwo-ubu22-desktop fworch-ui:  Message: Your requested role is not in allowed roles
2022-10-14T17:38:15.135372+02:00 fwo-ubu22-desktop fworch-ui:  2022-10-14T17:38:15+02:00 Error - API Connection (GraphQlApiConnection.cs in line 138), Error while sending query to GraphQL API. Query: query getUserByDn($dn: String!) {
2022-10-14T17:38:15.135703+02:00 fwo-ubu22-desktop fworch-ui:    uiuser(where: {uuid: {_eq:  $dn } }) {
2022-10-14T17:38:15.135825+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_id
2022-10-14T17:38:15.135887+02:00 fwo-ubu22-desktop fworch-ui:      uuid
2022-10-14T17:38:15.135941+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_username
2022-10-14T17:38:15.135989+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_language
2022-10-14T17:38:15.136029+02:00 fwo-ubu22-desktop fworch-ui:      uiuser_password_must_be_changed
2022-10-14T17:38:15.136088+02:00 fwo-ubu22-desktop fworch-ui:    }
2022-10-14T17:38:15.136137+02:00 fwo-ubu22-desktop fworch-ui:  }
2022-10-14T17:38:15.136176+02:00 fwo-ubu22-desktop fworch-ui:  , variables: {"dn":"uid=us2,ou=tenant0,ou=operator,ou=user,dc=fworch,dc=internal"}
2022-10-14T17:38:15.136204+02:00 fwo-ubu22-desktop fworch-ui:   ---
2022-10-14T17:38:15.136252+02:00 fwo-ubu22-desktop fworch-ui:  Exception thrown:
2022-10-14T17:38:15.136283+02:00 fwo-ubu22-desktop fworch-ui:   Exception
2022-10-14T17:38:15.136310+02:00 fwo-ubu22-desktop fworch-ui:  Message:
2022-10-14T17:38:15.136336+02:00 fwo-ubu22-desktop fworch-ui:   Your requested role is not in allowed roles
2022-10-14T17:38:15.136361+02:00 fwo-ubu22-desktop fworch-ui:
2022-10-14T17:38:15.136395+02:00 fwo-ubu22-desktop fworch-ui:  Stack Trace:
2022-10-14T17:38:15.136419+02:00 fwo-ubu22-desktop fworch-ui:   at FWO.Api.Client.GraphQlApiConnection.SendQueryAsync[QueryResponseType](String query, Object variables, String operationName) in /usr/local/fworch/lib/files/FWO.Api.Client/GraphQlApiConnection.cs:line 107

One issued closed, the rest was not repeoducible

just experienced "logout/login sometimes fails on first try" with version 6.0

not reproducible lately


Filter out private JS dependencies during parsing

Currently, we attempt to update private JS dependencies, but this causes errors in the UpdateChecker when we look for them in the registry and fail to find them.
This PR removes any dependencies that don't come from the main yarn registry at parse time. It's a little brutal, but perhaps the best we can do?
For an example of how private dependencies work with npm/yarn, see https://gemfury.com/l/private-npm.

@hmarr - can you take a look? There's a sentry, too, if you want to dig deeper into this.

@hmarr - if you get a chance to review this it would still be appreciated, but we're getting an error for this everyday at the moment, so I'm merging this fix.


Add new upscaler options for txt2img

I noticed that the txt2img function was missing the new options around upscaling. I added them and validated locally that it is working against the latest version of automatic1111.
Also updated the readme with commented out options for the txt2img piece.
Hope this makes sense :p

Thank you for the PR. Merged and published to pypi.

Cool thanks for merging! Glad I could help even a tiny bit. Super thanks for the library, having great fun with it right now :)