Not finding CUDA when it's installed both in conda env and for Windows globally (different versions)

Hi
Not sure what is happening here, but when I try to run python server.py, it says No CUDA runtime is found.
Is a specific version needed? Which one?
ie, I have 12.0 installed with PATH set in Win11 environment variables. I use 12.0 for 3D rendering and design.
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.0
It says not found here though, should I assume 12.0 is not the version we need then?
So, I also installed 12.3 inside the conda environment "exui".
It's not seeing this either. I though the point of an environment was that it looks in there first, and then outside if the components it needs are not present in the env. If I have to set the windows PATH for every environment I run, I'll be forever switching the PATH all day.
Or is 12.3 too new? Do I need 12.2 instead?
This GUI/app looks really good, but I think the install instructions could be a bit more detailed and take into account an environment manager or two.

look at the torch documentation it says 12.1 :)

Thanks I didn't see it in the documentation, just looked at the main github page and there is no link to docs. Maybe a line under "Running locally" on the main repo page, "You will need CUDA 12.1 and etc etc, then git clone etc.". :)
Will 12.3 work as well? Doing a system update and it seems like I should get on the latest, other LLM apps need 12.2 and I hope 12.3 will at least get me through the next few months!

no i don’t think so. maybe you can customise torch trough some configs but out of the box (as far as i know) thats not possible

Alright so I uninstalled CUDA and installed 12.1. Check win environment variable, all seems OK.
Delete conda env to start fresh. Set up new one. Pip install requirements. Run server.py.
Error:
(exui) C:\AI\Text\exui>python server.py
No CUDA runtime is found, using CUDA_HOME='C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1'
Traceback (most recent call last):
  File "C:\AI\Text\exui\server.py", line 11, in <module>
    from backend.models import update_model, load_models, get_model_info, list_models, remove_model, load_model, unload_model, get_loaded_model
  File "C:\AI\Text\exui\backend\models.py", line 5, in <module>
    from exllamav2 import(
  File "C:\Users\ComputeyName\AppData\Local\Programs\Python\Python310\lib\site-packages\exllamav2\__init__.py", line 3, in <module>
    from exllamav2.model import ExLlamaV2
  File "C:\Users\ComputeyName\AppData\Local\Programs\Python\Python310\lib\site-packages\exllamav2\model.py", line 17, in <module>
    from exllamav2.cache import ExLlamaV2CacheBase
  File "C:\Users\ComputeyName\AppData\Local\Programs\Python\Python310\lib\site-packages\exllamav2\cache.py", line 2, in <module>
    from exllamav2.ext import exllamav2_ext as ext_c
  File "C:\Users\ComputeyName\AppData\Local\Programs\Python\Python310\lib\site-packages\exllamav2\ext.py", line 131, in <module>
    exllamav2_ext = load \
  File "C:\Users\ComputeyName\AppData\Local\Programs\Python\Python310\lib\site-packages\torch\utils\cpp_extension.py", line 1308, in load
    return _jit_compile(
  File "C:\Users\ComputeyName\AppData\Local\Programs\Python\Python310\lib\site-packages\torch\utils\cpp_extension.py", line 1710, in _jit_compile
    _write_ninja_file_and_build_library(
  File "C:\Users\ComputeyName\AppData\Local\Programs\Python\Python310\lib\site-packages\torch\utils\cpp_extension.py", line 1810, in _write_ninja_file_and_build_library
    _write_ninja_file_to_build_library(
  File "C:\Users\ComputeyName\AppData\Local\Programs\Python\Python310\lib\site-packages\torch\utils\cpp_extension.py", line 2199, in _write_ninja_file_to_build_library
    cuda_flags = common_cflags + COMMON_NVCC_FLAGS + _get_cuda_arch_flags()
  File "C:\Users\ComputeyName\AppData\Local\Programs\Python\Python310\lib\site-packages\torch\utils\cpp_extension.py", line 1980, in _get_cuda_arch_flags
    arch_list[-1] += '+PTX'
IndexError: list index out of range

Why would it not find it when it's exactly where it says it's looking?

The failure seems to happen in PyTorch, at this point:
        arch_list = []
        # the assumption is that the extension should run on any of the currently visible cards,
        # which could be of different types - therefore all archs for visible cards should be included
        for i in range(torch.cuda.device_count()):
            capability = torch.cuda.get_device_capability(i)
            supported_sm = [int(arch.split('_')[1])
                            for arch in torch.cuda.get_arch_list() if 'sm_' in arch]
            max_supported_sm = max((sm // 10, sm % 10) for sm in supported_sm)
            # Capability of the device may be higher than what's supported by the user's
            # NVCC, causing compilation error. User's NVCC is expected to match the one
            # used to build pytorch, so we use the maximum supported capability of pytorch
            # to clamp the capability.
            capability = min(max_supported_sm, capability)
            arch = f'{capability[0]}.{capability[1]}'
            if arch not in arch_list:
                arch_list.append(arch)
        arch_list = sorted(arch_list)
        arch_list[-1] += '+PTX'

It fails on the last line indexing the last element of arch_list, which means that list is empty. The only way I can see that happening is if torch.cuda.device_count() is zero, i.e. Torch has not recognized any CUDA devices.
Are you sure you have the CUDA-enabled version of Torch installed? pip freeze should show torch==...+cu121 I believe. The "No CUDA runtime is found" error is also emitted by Torch, so it does look like you have the CUDA version, but it really can't find the CUDA runtime, which would be provided by the NVIDIA driver. I don't know if maybe that's not installed, or not available somehow? Do you get anything from running nvidia-smi?

for "pip show torch":
Name: torch
Version: 2.1.2
Summary: Tensors and Dynamic neural networks in Python with strong GPU acceleration
Home-page: https://pytorch.org/
Author: PyTorch Team
Author-email<EMAIL_ADDRESS>License: BSD-3
Location: c:\users\hesperos\appdata\local\programs\python\python310\lib\site-packages
Requires: filelock, fsspec, jinja2, networkx, sympy, typing-extensions
Required-by: exllamav2

pip freeze shows
torch==2.1.2
or in anaconda it shows
torch==2.1.0+cu121
but then once the environment is active anaconda also shows
torch==2.1.2
nvidia-smi shows
NVIDIA-SMI 546.12                 Driver Version: 546.12       CUDA Version: 12.3
And the 2x 4090s.
of course, the 12.3 there just means that the driver is compatible up to that version of CUDA as you know.
So that's the weird thing, torch is there, CUDA is there, etc.
Or is it?
I need a torch install inside the env. But it wasn't in the requirements... it's a requirement though?
Hm
Now after installing torch I get "No module named 'flask'" which I suppose means I am supposed to have an environment variable for it.
But if I do >flask --version
I get
Python 3.10.8
Flask 3.0.0
Werkzeug 3.0.1

So I don't know. I have it or not.

You definitely have the non-CUDA version of Torch. Why 2.1.0+cu121 shows up in Anaconda I don't know. In any case, I would do:
pip uninstall torch
pip install torch --index-url https://download.pytorch.org/whl/cu121

There's definitely something up with your conda envs though. flask is a requirement and shouldn't need any environment variables. You should be able to install it with:
pip install torch waitress

(waitress being the next requirement it would likely not find if it isn't finding flask.)

Had same issue today, installed from anaconda :
conda create -n exui python==3.10
conda activate exui
pip install -r requirements.txt

And received same error.
To fix that:
pip uninstall torch # and generated right version of pytorch on their site
pip install torch --index-url https://download.pytorch.org/whl/cu121

Now everything is working. I guess it would be nice to add some note in installation guide for conda users.

I had this issue today, because I'm using 12.1 instead of 12.2. The readme doc currently refers to 12.1. We could be more generic about it to help other users troubleshoot, maybe:
"Run torch freeze, make sure you have the version listed installed in , otherwise pip uninstall torch (...) pip install torch (...), or install the correct version of Torch from (...)."

true something like a "currently supported versions" list would be helpful


[SPARK-34793][SQL] Prohibit saving of day-time and year-month intervals

What changes were proposed in this pull request?
For all built-in datasources, prohibit saving of year-month and day-time intervals that were introduced by SPARK-27793. We plan to support saving of such types at the milestone 2, see SPARK-27790.
Why are the changes needed?
To improve user experience with Spark SQL, and print nicer error message. Current error message might confuse users:
scala> Seq(java.time.Period.ofMonths(1)).toDF.write.mode("overwrite").json("/Users/maximgekk/tmp/123")
21/03/18 22:44:35 ERROR FileFormatWriter: Aborting job 8de402d7-ab69-4dc0-aa8e-14ef06bd2d6b.
org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 1.0 failed 1 times, most recent failure: Lost task 0.0 in stage 1.0 (TID 1) (<IP_ADDRESS> executor driver): org.apache.spark.SparkException: Task failed while writing rows.
	at org.apache.spark.sql.errors.QueryExecutionErrors$.taskFailedWhileWritingRowsError(QueryExecutionErrors.scala:418)
	at org.apache.spark.sql.execution.datasources.FileFormatWriter$.executeTask(FileFormatWriter.scala:298)
	at org.apache.spark.sql.execution.datasources.FileFormatWriter$.$anonfun$write$15(FileFormatWriter.scala:211)
	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:90)
	at org.apache.spark.scheduler.Task.run(Task.scala:131)
	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:498)
	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1437)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:501)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: Failed to convert value 1 (class of class java.lang.Integer}) with the type of YearMonthIntervalType to JSON.
	at scala.sys.package$.error(package.scala:30)
	at org.apache.spark.sql.catalyst.json.JacksonGenerator.$anonfun$makeWriter$23(JacksonGenerator.scala:179)
	at org.apache.spark.sql.catalyst.json.JacksonGenerator.$anonfun$makeWriter$23$adapted(JacksonGenerator.scala:176)

Does this PR introduce any user-facing change?
Yes. After the changes, the example above:
scala> Seq(java.time.Period.ofMonths(1)).toDF.write.mode("overwrite").json("/Users/maximgekk/tmp/123")
org.apache.spark.sql.AnalysisException: Cannot save interval data type into external storage.

How was this patch tested?

Checked nested intervals:

scala> spark.range(1).selectExpr("""struct(timestamp'2021-01-02 00:01:02' - timestamp'2021-01-01 00:00:00')""").write.mode("overwrite").parquet("/Users/maximgekk/tmp/123")
org.apache.spark.sql.AnalysisException: Cannot save interval data type into external storage.
scala> Seq(Seq(java.time.Period.ofMonths(1))).toDF.write.mode("overwrite").json("/Users/maximgekk/tmp/123")
org.apache.spark.sql.AnalysisException: Cannot save interval data type into external storage.

By running existing test suites:

$ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly *DataSourceV2DataFrameSuite"
$ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly *DataSourceV2SQLSuite"

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40807/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136225/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136241/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40823/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40828/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136246/

@yaooqinn @cloud-fan Thank you for review. I am merging this to master.


Separate package for cli and package sevm to prevent unintended subdependencies

Currently when you install sevm in your package, itll add the ansi-colors, yargs and env-paths  dependencies to your lock file. This is not intentional if you are only trying to use the package and not the cli. To reduce bundle size and keep the dependency tree clean, this should be separated.

If Anyone sees this as well and wants to have a quick workaround:
If you use pnpm as a package manager, You can force pnpm to not install certain subdependencies by adding the following overrides  to your root package.json:
{
"pnpm": {
   "overrides": {
      "...[other_overrides]",
      "sevm>ansi-colors": "-",
      "sevm>yargs": "-",
      "sevm>env-paths": "-"
   }
}}

Hi @MbBrainz, thanks for sending this.

To reduce bundle size [..]

Please keep in mind that it won't affect the bundle size. Those dependencies (and js-sha3 as well) are only used by the CLI, so when you bundle the package, your bundler shouldn't include those dependencies. Moreover, the package should not depend on any Node specific API, meaning it should work in a browser without problem.

[..] and keep the dependency tree clean, this should be separated.

I understand this can be odd when wanting only the package. In fact, in the past I tried to keep the CLI dependencies to a minimum. However, I'm reluctant to split the package and the CLI (at least for now) if the only issue is the dependency tree.

Hey @MbBrainz, going to close this for now. If it still represents a problem for you, feel free to reopen.

@acuarica Thanks for the detailed explanation. I see indeed that in our build, those packages dont show up.


Test Case Config does not behave as I expected

The documentation states that I can add a timeout to a test. It states that it is "Useful for code that is non-deterministic and might not finish". This leads me to believe that this setting will stop the test execution after the given duration has passed. However, when I accidentally executed a test that called a method with an infinite loop, it didn't stop the execution after the timeout had passed. Is this a documentation issue, a fault on my side or a bug?
After some testing, I found out that this fails, but only after the full test has finished:
class FiniteLoopString: StringSpec() {
    "has a long finite loop test".config(timeout = 100.milliseconds) {
        val startTime = currentTimeMillis()
        while (currentTimeMillis() < startTime + 1000) {
            "this" shouldNotBe "that"
        }
    }
}

while the following test just keeps running forever:
class InfiniteLoopString: StringSpec() {
    "has an infinite loop test".config(timeout = 100.milliseconds) {
        while (true) {
            "this" shouldNotBe "that"
        }
    }
}

During my testing, I also found that this test succeeds, even though it takes longer than the timeout:
class SuccessfulTest: WordSpec() {
    init {
        "String.length" should {
            "return the length of the string".config(timeout = 2.seconds) {
                val startTime = currentTimeMillis()
                while (currentTimeMillis() < startTime + 10000) {
                    "this" shouldNotBe "that"
                }
            }
        }
    }
}

Definitely a bug. The timeout should kick in for any test that takes longer than the timeout.

Which version of kotlintest ?

I tested this with version 3.1.10.

I'll grab this if you're not working on it, @sksamuel .

I'll fix this as part of #518 as it will need to work differently.

Added. Review as part of #518


minitest in .bundle not generating correct Rakefile

This is a bug in 1.9.9 and confirmed to be fixed in 1.10.0.rc1.
With a .bundle/config in my home directory:
---
BUNDLE_GEM__COC: true
BUNDLE_GEM__MIT: true
BUNDLE_GEM__TEST: minitest

The Rakefile generated for bundle gem foo is missing the minitest test task configuration:
require "bundler/gem_tasks"

When it should be something like:
require "bundler/gem_tasks"
require "rake/testtask"

Rake::TestTask.new(:test) do |t|
  t.libs << "test"
  t.libs << "lib"
  t.test_files = FileList['test/**/*_test.rb']
end

task :default => :test

I'm not sure if this is worth patching in 1.9.9 if the 1.10.0 release is immenent.

CC: @zenspider

Closing at the advice of @indirect and @zenspider.


[Rule] No embedded keyword arguments

Robot keywords allow you to set arguments in 2 ways: Through the [Arguments] tag and through embedded arguments. For details on embedded arguments see https://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#embedding-arguments-into-keyword-name.
I would like a rule that disallows this pattern. It can result in hard to understand code. This rule could be called something like no-embedded-keyword-arguments.
I'm willing to write this rule. Let me know if you're interested in adding it.

It is valid rule, though obviously only for some people. Feel free to implement it but it would go as community rule (not enabled by default)

Yeah not everybody would like this one. I'll add this one to the community rules soon™


Standardize docstrings

This PR's aim is to standardize the docstrings across the whole repo and enforce this standardization to avoid needing more PRs like these.

Can I take it?

Can I take it?

I am inclined to say go for it! I have seen that @ItsDrike is more interested in the CI/CD of this repo as of late and I have always been more focused on reviewing small pull requests rather than contributing. I don't know the status of work in this branch, so you would have to take a gander or @ItsDrike would have to remark on that. I just pushed a rebased version of this branch into docstring-revolution for whoever picks this up. For some reason, I have fun rebasing lots of tiny conflicts.

Can I take it?

I am inclined to say go for it! I have seen that @ItsDrike is more interested in the CI/CD of this repo as of late and I have always been more focused on reviewing small pull requests rather than contributing. I don't know the status of work in this branch, so you would have to take a gander or @ItsDrike would have to remark on that. I just pushed a rebased version of this branch into docstring-revolution for whoever picks this up. For some reason, I have fun rebasing lots of tiny conflicts.

Yeah sure, feel free to take it over, I don't plan on working on this any time soon so it's quite alright.


Setting NODE_TLS_REJECT_UNAUTHORIZED=0 doesn't work in jest@22+

💥 Regression Report
A clear and concise description of what the regression is.
Last working version
Worked up to version<EMAIL_ADDRESS>Stopped working in version<EMAIL_ADDRESS>To Reproduce
Steps to reproduce the behavior:

Clone repo https://github.com/trivikr/jest-self-signed-certificate
cd jest-self-signed-certificate
Change to jest-21 branch by running git checkout jest-21
npm test is successful
Change to master branch by running git checkout master
npm test fails

Expected behavior
I expected test to succeed, it fails with:
 FAIL  src/__tests__/server.test.js
  server
    ✕ server sends response (38ms)

  ● server › server sends response

    self signed certificate

Link to repl or repo (highly encouraged)
https://github.com/trivikr/jest-self-signed-certificate
Run npx envinfo --preset jest
Paste the results here:
npx: installed 1 in 1.231s

  System:
    OS: macOS High Sierra 10.13.6
    CPU: (4) x64 Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz
  Binaries:
    Node: 12.1.0 - /usr/local/bin/node
    Yarn: 1.15.2 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
  npmPackages:
    jest: ^24.8.0 => 24.8.0

Ref: https://github.com/aws/aws-sdk-js-v3/issues/244

Hi, is there any update on this regression?
Or any proposed solution to test https server by setting NODE_TLS_REJECT_UNAUTHORIZED=0
This might block users from updating past Jest v21

This is a blocker for us. We're trying not to have a flag in our services to turn off SSL. For testing, we have to use self-signed certs. Pretty much a dealbreaker :-(

I tried to require server after setting environment variable in commit https://github.com/trivikr/jest-self-signed-certificate/commit/864ef96d15d8e49c863038c3103970687f7a4be6 (under the assumption that update in process.env variables apply only for subsequent require statement)
The issue still exists

Any update on this regression?

Having the same issue.

Hi team, any suggestion on how to work around the regression to write the unit test?
Requiring modules after setting environment variable doesn't work as explained in https://github.com/facebook/jest/issues/8449#issuecomment-495385977

After some experimenting/debugging, I tbh still have no idea why Node doesn't pick up the setting or which change in v22 could have introduced this. As a workaround it seems that it works if you launch Jest with the env var set to 0 straight away. If it's just a few tests that need this, could also consider doing a separate Jest run for those if you don't want to set it for all tests.

It looks like it doesn't pick up any change to process.env not only to NODE_TLS_REJECT_UNAUTHORIZED.

Any update on this request?

for me
export NODE_TLS_REJECT_UNAUTHORIZED=0   worked
set  NODE_TLS_REJECT_UNAUTHORIZED=0  did not

any update on this issue ?

After researching this problem, it appears that jest wraps the env object with a proxy. Hence, any change on process.env would not be propagated to the real one.
https://github.com/facebook/jest/blob/c83051789cc60789f2c575374270236e3a428879/packages/jest-util/src/createProcessObject.ts#L82-L128

Any updates?

Hi ,
I am also facing same issue. When running test using JEST. I am getting FetchError: request to URL/login failed, reason: self signed certificate in certificate chain
Note I am able tto run same test using Jasmine with setting
process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";
I have opened this issue please check. If any suggestions to resolve it.
https://github.com/jest-community/vscode-jest/issues/592

for me
export NODE_TLS_REJECT_UNAUTHORIZED=0 worked
set NODE_TLS_REJECT_UNAUTHORIZED=0 did not
Hi, can you please tell me where can I do that?

Doing the same in a setup file also seems to have no effect:
jest.config.js:
module.exports = {
  setupFiles: "./setup.js",
};

setup.js:
process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

Hi Dear.
I've ran process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0"; in setup.js but it's surely not working.
Network Error
  at createError (node_modules/axios/lib/core/createError.js:16:15)
  at XMLHttpRequest.handleError (node_modules/axios/lib/adapters/xhr.js:84:14)
  at XMLHttpRequest.<anonymous> (node_modules/jsdom/lib/jsdom/living/helpers/create-event-accessor.js:32:32)
  at innerInvokeEventListeners (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:318:25)
  at invokeEventListeners (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:274:3)
  at XMLHttpRequestImpl._dispatch (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:221:9)
  at fireAnEvent (node_modules/jsdom/lib/jsdom/living/helpers/events.js:18:36)
  at requestErrorSteps (node_modules/jsdom/lib/jsdom/living/xhr/xhr-utils.js:128:3)
  at Object.dispatchError (node_modules/jsdom/lib/jsdom/living/xhr/xhr-utils.js:59:3)
  at Request.<anonymous> (node_modules/jsdom/lib/jsdom/living/xhr/XMLHttpRequest-impl.js:654:18)
  at Request.onRequestResponse (node_modules/request/request.js:948:10)

Running coverage on untested files...  console.log
0 process.env.NODE_TLS_REJECT_UNAUTHORIZED
  at Object.<anonymous> (test/jest/__tests__/QBtn.spec.js:37:13)

console.error
Error: Error: SSL Error: DEPTH_ZERO_SELF_SIGNED_CERT
Could you please tell me what's the issue?

Hey I found a workaround for this in jest 26 (if you are using jsdom).  With the upgrade to jsdom 16, jest is not aware of the "resources" option on the JSDOM constructor, this and a combination of a regression somewhere with process.env which some of this thread has picked up on doesnt allow NODE_TLS_REJECT_UNAUTHORIZED=0 to work anymore.
Steps to patch:

create a custom jsdom environment (save this as custom-jsdom-env.js next to package.json). This is similiar to the jest-environment-jsdom which ships with jest HOWEVER, it includes the "resources" component of JSDOM with the strictSSL set to false, there are two other options in the resources which you can find on jsdom but I have just set this one.

// custom-jsdom-environment
const JSDOMEnvironment = require('jest-environment-jsdom')
const { ResourceLoader, JSDOM, VirtualConsole } = require('jsdom')
const { installCommonGlobals } = require('jest-util')
const { ModuleMocker } = require('jest-mock')
const { LegacyFakeTimers, ModernFakeTimers } = require('@jest/fake-timers')

class CustomEnvironment extends JSDOMEnvironment {
  constructor(config, context) {
    super(config, context)

    this.dom = new JSDOM('<!DOCTYPE html>', {
      pretendToBeVisual: true,
      runScripts: 'dangerously',
      url: config.testURL,
      virtualConsole: new VirtualConsole().sendTo(context.console || console),
      ...config.testEnvironmentOptions,
      resources: new ResourceLoader({ strictSSL: false }),
    })
    const global = (this.global = this.dom.window.document.defaultView)

    if (!global) {
      throw new Error('JSDOM did not return a Window object')
    }

    // for "universal" code (code should use `globalThis`)
    global.global = global

    // Node's error-message stack size is limited at 10, but it's pretty useful
    // to see more than that when a test fails.
    this.global.Error.stackTraceLimit = 100
    installCommonGlobals(global, config.globals)

    // Report uncaught errors.
    this.errorEventListener = (event) => {
      if (userErrorListenerCount === 0 && event.error) {
        process.emit('uncaughtException', event.error)
      }
    }
    global.addEventListener('error', this.errorEventListener)

    // However, don't report them as uncaught if the user listens to 'error' event.
    // In that case, we assume the might have custom error handling logic.
    const originalAddListener = global.addEventListener
    const originalRemoveListener = global.removeEventListener
    let userErrorListenerCount = 0
    global.addEventListener = function(...args) {
      if (args[0] === 'error') {
        userErrorListenerCount++
      }
      return originalAddListener.apply(this, args)
    }
    global.removeEventListener = function(...args) {
      if (args[0] === 'error') {
        userErrorListenerCount--
      }
      return originalRemoveListener.apply(this, args)
    }

    this.moduleMocker = new ModuleMocker(global)

    const timerConfig = {
      idToRef: (id) => id,
      refToId: (ref) => ref,
    }

    this.fakeTimers = new LegacyFakeTimers({
      config,
      global,
      moduleMocker: this.moduleMocker,
      timerConfig,
    })

    this.fakeTimersModern = new ModernFakeTimers({ config, global })
  }

  async setup() {
    await super.setup()
  }

  async teardown() {
    await super.teardown()
  }

  runScript(script) {
    return super.runScript(script)
  }
}

module.exports = CustomEnvironment

Add the testEnvironment to jest settings:
You need to set the testEnvironment option to {PATH_TO}/cutom-jsdom-env.js or the --env={PATH_TO}/custom-jsdom-env.js

My workaround for this was:
  testEnvironment: 'jsdom',
  testEnvironmentOptions: {
    resources: new ResourceLoader({ strictSSL: false }),
  },

Duplicate of #5118

Same as https://github.com/facebook/jest/issues/9264#issuecomment-1053646395.
If you really need to test this flag, I suggest doing what was suggested in https://github.com/facebook/jest/issues/8449#issuecomment-500123589 (a separate run). You should be able to set this in a globalSetup as that's the real process.env and will be reflected in node core modules.

Note that if https://github.com/nodejs/node/issues/31852 is every implemented, it might be possible we do something about this


[BUG]: Parameter of size (torch.Size([4096])) has already been reduced, duplicate reduction will lead to arithmetic incorrectness

🐛 Describe the bug
when I use add two loss ，some error ，pleaese help

error：

Environment
No response

zero2 not support this format?

only backward loss_reward also lead to this error!


Making the text in highlighted candidate in the "ink" theme more visable

I'm always frustrated when I can't see the pinyin in the highlighted candidate when I'm using the ink theme. It used to be white in the previous versions of rime but in this version, you can barely see it. Its a very dark gray.

this is not a issue of librime. maybe you should issue in the  issues of corresponding front end. maybe you should also check if this is the issue of the color scheme 'ink'.


Typescript not picking up extended NuxtConfig interface when installing with pnpm

Environment

Operating System: Linux
Node Version:     v18.18.0
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    -
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, modules, ui, colorMode
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-yurofm?file=package.json,nuxt.config.ts
Describe the bug
When using a module, for example @nuxt/ui, and installing dependencies with pnpm, the extended type for NuxtConfig is not being picked up by Typescript (both tsc and vue-tsc). This leads to a type error in nuxt.config.ts:
nuxt.config.ts:5:3 - error TS2353: Object literal may only specify known properties, and 'ui' does not exist in type 'InputConfig<NuxtConfig, ConfigLayerMeta>'.

5   ui: {
    ~~

Found 1 error in nuxt.config.ts:5

Additionally, I found that:

the extended interface is present in .nuxt/schema.d.ts
removing node_modules and reinstalling with npm will fix the error
type casting the input parameter of defineNuxtConfig as InputConfig<NuxtConfig> will circumvent the issue, but requires me to add c12 as a dependency

Additional context
This is my first project using pnpm, but I decided to give it a go after I saw nuxt itself uses it. Because of that I was also surprised I did not find any other issues mentioning this. So perhaps this is a misconfiguration on my end, and people here know the answer straight away. But I decided to open a bug since I could easily reproduce the issue with Stackblitz.
Logs
No response

hi :wave: can you try with a --shamefully-hoist install ?

Hi @huang-julien! When I install with --shamefully-hoist it types correctly, so I reckon the error is in the node_modules struture of pnpm.
Any clue on why this happens? If I have to use that flag I probably just switch back to npm. Not really a problem, but I wonder if there's something to be fixed here.

This is resolved in the latest version of Nuxt.

https://stackblitz.com/edit/github-yurofm-5kpdoa?file=nuxt.config.ts


Redshift JDBC driver in DBeaver needs updating to version <IP_ADDRESS>3.

As a result of resolving 1897 the Redshift JDBC driver that ships with DBeaver needs to be upgraded to version <IP_ADDRESS>3 or higher so that current versions of DBeaver have access to Redshift external table metadata and schemata that are access as part of the Redshift Spectrum feature.
The new Redshift JDBC driver version can be obtained here: http://docs.aws.amazon.com/redshift/latest/mgmt/configure-jdbc-connection.html.
Licensing for driver redistribution can be obtained by following the instruction on the same linked page.

It was resolved in  #1897


Update config to enable docfx v3

AB#275107
This Pull Request is for docfxv3 migration, after the Pull Request merged, the repository will be built with docfxv3 instead of docfxv2.

Docs Build status updates of commit 36ae944:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-DocsetsWithDuplicatedBasePath] There are multiple docsets of same base path in this repo (Docsets of name xbldevtools,XboxLive-API are of same base path '/dotnet'.). This is not supported in DocFX v3. Please let repo admin open a ticket on //SiteHelp to either merge those docsets into one, or split them into multiple repos.

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


[QUESTION] Unable to stream video to AWS KINESIS DATA STREAMS

I am trying to stream video to AWS Kinesis Data streams from Raspberry pi Zero 2W board, I tried to run sample application using below command after building
 ./kvs_gstreamer_sample rpi-stream

Below is the log details after running above command
** Logging **
log4cplus:ERROR Unable to open file: ./log/kvs.log
[INFO ] [26-09-2023 14:28:10:327.536 GMT] Using region: ap-south-1
[INFO ] [26-09-2023 14:28:10:327.888 GMT] Using aws credentials for Kinesis Video Streams
[INFO ] [26-09-2023 14:28:10:328.120 GMT] No session token was detected.
[INFO ] [26-09-2023 14:28:10:335.552 GMT] createKinesisVideoClient(): Creating Kinesis Video Client
[WARN ] [26-09-2023 14:28:10:336.064 GMT] fixupClientInfo(): Connection timeout is invalid...setting to default
[WARN ] [26-09-2023 14:28:10:336.312 GMT] fixupClientInfo(): Completion timeout is invalid...setting to default
[INFO ] [26-09-2023 14:28:10:336.694 GMT] heapInitialize(): Initializing native heap with limit size 134217728, spill ratio 0% and flags 0x00000001
[INFO ] [26-09-2023 14:28:10:336.939 GMT] heapInitialize(): Creating AIV heap.
[INFO ] [26-09-2023 14:28:10:337.263 GMT] heapInitialize(): Heap is initialized OK
[DEBUG] [26-09-2023 14:28:10:337.857 GMT] getSecurityTokenHandler invoked
[DEBUG] [26-09-2023 14:28:10:338.280 GMT] Refreshing credentials. Force refreshing: 0 Now time is:<PHONE_NUMBER>338161409 Expiration: 0
[INFO ] [26-09-2023 14:28:10:338.556 GMT] New credentials expiration is<PHONE_NUMBER>
[INFO ] [26-09-2023 14:28:10:338.871 GMT] createDeviceResultEvent(): Create device result event.
[DEBUG] [26-09-2023 14:28:10:339.078 GMT] clientReadyHandler invoked
[DEBUG] [26-09-2023 14:28:10:339.354 GMT] Client is ready
[INFO ] [26-09-2023 14:28:10:339.812 GMT] Creating Kinesis Video Stream rpi-stream
[INFO ] [26-09-2023 14:28:10:340.087 GMT] createKinesisVideoStream(): Creating Kinesis Video Stream.

[DEBUG] [26-09-2023 14:28:25:362.541 GMT] defaultStreamStateTransitionHook(): Stream state machine retry count: 0
[DEBUG] [26-09-2023 14:28:25:362.610 GMT] defaultStreamStateTransitionHook():
 KinesisVideoStream base result is [599]. Executing KVS retry handler of retry strategy type [1]
[ERROR] [26-09-2023 14:28:40:348.707 GMT] createKinesisVideoStreamSync(): Failed to create Kinesis Video Stream - timed out.
[INFO ] [26-09-2023 14:28:40:349.344 GMT] freeKinesisVideoStream(): Freeing Kinesis Video stream.
[DEBUG] [26-09-2023 14:28:40:349.733 GMT] freeStream(): [rpi-stream] Freeing stream
[DEBUG] [26-09-2023 14:28:40:850.647 GMT] freeStream(): [rpi-stream] Completed freeing stream
[ERROR] [26-09-2023 14:28:40:851.185 GMT] createKinesisVideoStreamSync(): operation returned status code: 0x0000000f
[ERROR] [26-09-2023 14:28:40:851.855 GMT]  Unable to create Kinesis Video stream. rpi-stream Error status: 0xf
[INFO ] [26-09-2023 14:28:40:852.619 GMT] Freeing Kinesis Video Stream for rpi-stream
[INFO ] [26-09-2023 14:28:40:853.076 GMT] freeKinesisVideoStream(): Freeing Kinesis Video stream.
[ERROR] [26-09-2023 14:28:40:853.652 GMT] Failed to initialize kinesis video with an exception:  Unable to create Kinesis Video stream. rpi-stream Error status: 0xf
[INFO ] [26-09-2023 14:28:40:854.140 GMT] freeKinesisVideoClient(): Freeing Kinesis Video Client
[DEBUG] [26-09-2023 14:28:40:854.471 GMT] curlApiCallbacksShutdownActiveRequests(): pActiveRequests hashtable is empty
[DEBUG] [26-09-2023 14:28:41:258.713 GMT] freeKinesisVideoClientInternal(): Total allocated memory 0
[INFO ] [26-09-2023 14:28:41:259.226 GMT] Completed freeing client
[WARN ] [26-09-2023 14:28:41:259.686 GMT] curlApiCallbacksShutdown(): curlApiCallbacksShutdown called when already in progress of shutting down
log4cplus:ERROR Failed to open file ./log/kvs.log

I will share if additional info is needed, kindly help.

It seems the describeStream call is timing out which indicates that curl is having issues executing the call. Verify that there isnt a firewall that is obstructing curl. This might necessarily not be an SDK issue.
Also, make sure you are in the right region.


Not able to get data from editor which we used options

Team I need sample for get data from Editor as what ever used formats like Bold or Italic, etc... Not able to restrict length. Help me on this. How to get editor data and limit the maximum character

Hi,
You can use richTextState.currentSpanStyle to get the current span style and then use val isBold = currentSpanStyle.fontWeight = FontWeight.Bold  to know if it is bold or not, for example.
https://mohamedrejeb.github.io/Compose-Rich-Editor/span_style/#styling-spans
For now there's no way to set a character limit. That's important I'll try to implement it ASAP

But I need to get data from Editor with bold and whatever I used in outline text field. I need to POST that data to server. I cant  find any samples for this... Just give me an Idea for this

I'm not sure if I understand correctly, for saving data to server we support HTML. So you can transfer your RichTextState into HTML string that could be saved to the server, and you transfer it back to RichTextState later.
Check this link

Hey, Mohamed Thanks for your reply. I can access now. Thanks for your prompt response

.


Explore other persistence backends besides SQL databases

Currently, the graph is tied to being able to persist in a SQL database, using SQL Alchemy as the ORM.
This works, but it's a bit painful to reason about the ORM layer and keep it in sync with our internal data model. Also, any data generated locally is likely small enough probably to fit in memory. One option then would be to implement a simpler storage mechanism that is more flexible than SQL for our current use cases and push off developing a higher performance persistence and querying layer till later. For that, it might even make sense to use a graph DB, (neo4j is pretty mature, open source, and has a Python ORM library), so that we can push some of the slicing directly into the DB as well (as well as other queries, like "what columns are used from this table", which would could be expressed more directly with a graph query language).
One way to move toward this would be:

Create an abstract "Backend" interface that would provide all the APIs for fetching and storing data. This would probably deal with the types currently in the types.py file. (this would be a slight modification of our current db.py file to make sure it doesn't expose asn ORM values).
Add a simpler serialization/deserialization mechanism based on JSON that implements this backend interface.
(Optional/later on) Add a SQL or Graph Query language backend

closing til we have plans for this.


gpio_shell: Not functional anymore following DT label cleanup and deprecation

Describe the bug
GPIO_SHELL provides a utility to perform few specific GPIO related actions:
"Configure GPIO"
"Get GPIO value"
"Set GPIO"
"Blink GPIO"

It could be used as follows:
uart:~$ gpio conf GPIOD 15 "out"
Configuring GPIOD pin 15
uart:~$ gpio set GPIOD 15 1
Writing to GPIOD pin 15
uart:~$ gpio get GPIOD 15
Reading GPIOD pin 15
Value 1

Since recent device tree label deprecation and cleanup, this is not functional anymore:
uart:~$ gpio conf GPIOD 15 "out"
uart:~$ gpio set GPIOD 15 1
uart:~$ gpio get GPIOD 15
uart:~$

To Reproduce
CONFIG_SHELL=y
CONFIG_GPIO_SHELL=y

Expected behavior
gpio shell should be functional
Impact
gpio shell is useless

You need to use the devicetree node name instead of GPIOD (e.g. gpio@deadbeef).

Ok, let me close and I'll open a new issue as description doesn't match a enhancement.


Plugin does not honor the header directive

In our caddy file we remove the server header with -Server. However when plugin returns a 429 error, it also adds back the Server header not respecting the config. How can we prevent this?
{
    order rate_limit before basicauth
}
:8443 {
    tls /etc/ssl/my.crt /etc/ssl/my.key
    header {
        -Server
        Strict-Transport-Security max-age=31536000;
        X-Content-Type-Options nosniff
        X-Frame-Options DENY
        Referrer-Policy no-referrer-when-downgrade
        X-XSS-Protection "1; mode=block"
    }
    encode gzip
    log {
        output discard
    }
    reverse_proxy http://my-api:8080
    rate_limit {
            distributed
            zone static_example {
                key    static
                events 5
                window 1m
            }
    }
}

I think after rate_limit, it goes through the error handler chain if the request was rejected. So I think you'll need to configure handle_errors as well and remove the header in there.

Here is a solution with handle_errors:
    handle_errors {
        @429
        header {
            -Server
        }
        respond @429 "The service cannot be reached. Please wait a while!"
    }


Rectangle missing flip use case from deprecated shape Quad

What problem does this solve or what need does it fill?
The deprecated shape Quad's flip field does not have a clear migration path to the new Rectangle shape.
Current migration guide: https://bevyengine.org/learn/migration-guides/0-12-to-0-13/#deprecate-shapes-in-bevy-render-mesh-shape
What solution would you like?
#10569 specifies that there should be a flipped method to cover this use case, however that seems to be missing.
let flipped_rectangle = Rectangle::new(100.0, 100.0).mesh().flipped();

This was sort of left out on purpose: https://github.com/bevyengine/bevy/pull/11431#issuecomment-1904776945
It seems a bit strange to me to support flipping a texture in a mesh representation. I feel like it's something that should instead be configurable at a material-level. I would assume that this is possible already? If not, I think it'd be valuable to have.
Only supporting texture flipping for Rectangle/Quad also seems slightly arbitrary to me; why not also support planes? Or circles? Or basically any shape?
Looking at other applications, I'm also not seeing a similar flip property elsewhere. For example, Godot doesn't have it (I also checked editor GUI), Unity doesn't have it, and Blender doesn't have it. To me, it doesn't feel like a quad-specific property, but a general material property.

I'm not saying that the flipped method needs to be added to Mesh, as a user of Quad::flip I think that a line in the migration guide on how to achieve this in the new bevy release would be enough

I feel like it's something that should instead be configurable at a material-level

Do you mean just add to StandardMaterial additional parameter, or mention in migration guide that making custom flipping material is the correct way for replacement of Quad::flip?

For any UV transformations you can use StandardMaterial::uv_transform, which is pretty fresh, because it had been added for KHR_texture_transform support to current main and it will be available from next 0.14 release.
For example for flip you can try set uv_transform to
Affine2{matrix2: -Mat2::IDENTITY, translation: Vec2::ONE,} for both axes flip
or
Affine2 {
    matrix2: Mat2::from_cols(-Vec2::X, Vec2::Y),
    translation: -Vec2::X + Vec2::Y,
} // for horizontal flip

instead of default or premultiply it with uv_transform that you wanted to use earlier, if so.
@alice-i-cecile How do you think, should we add flipped method to StandardMaterial, or maybe add FLIPPING / HORIZONTAL_FLIPPING const value to Affine2 consts?

I think that StandardMaterial is the most predictable place to find this. I think we should do that, but also add some nice constants to Affine2 (and possibly Affine3): those are great simple constants that will come up repeatedly and improve readability.


Add example notebook on sale attribution

Example notebook is based on synthetic data to first quantify sales attribution to different drivers, and then conduct interventions to calculate incremental return on investment

@all-contributors please add @vivianqin214 for code please


Lost ability to specify custom path for JS & CSS flies

I've just attempted to update from ancient version <IP_ADDRESS> and found out that I'm no longer able to specify custom locations for JS and CSS files. It'd seem that any customizations in configuration get overwritten by call to get_theme_files() that's done after the custom config is loaded. Maybe the line in apps.update_config() should read DEFAULT_CONFIG[key] = get_theme_files(self.theme, key) instead of CONFIG[key] = get_theme_files(self.theme, key) ?

I am new to Django and just started looking at django-summernote. I am looking for the option to specify local copies of Bootstrap and jQuery and this question seems relevant. I tried implementing the above change, but got a bunch of errors. The only way I managed to hack it for now is by updating utils.py with my own values:
'bs4': {
    'base_css': (
        #'//stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css',
        '/static/core/css/bootstrap.min.css',
    ),
    'base_js': (
        #'//code.jquery.com/jquery-3.3.1.min.js',
        #'//stackpath.bootstrapcdn.com/bootstrap/4.3.1/js/bootstrap.bundle.min.js',
        '/static/core/js/jquery-3.4.1.min.js',
        '/static/core/js/bootstrap.bundle.min.js',
    ),


Optionally Generate TestNG Classes

It would be good if Randoop could generate TestNG tests as well as JUnit.

That sounds great.  It isn't too much work because it's just a matter of formatting.  Please feel free to implement this and submit a pull request.  I'll close the issue for now, but we would be glad to incorporate such an improvement in Randoop.


Unable to set or override deployment strategy via keptn onboard cli command

The --deployment-strategy flag does not set/override a deployment strategy for a given stage.
To Reproduce
Given a project using the following trivial shipyard.yaml
stages:
  - name: "dev"
  - name: "production"

when onboarding a service using the following command (note the --deployment-stragety flag) :
keptn onboard service <svc-name> --project=<project-name> --chart=./<chart-name> --deployment-strategy=direct
keptn send event new-artifact --project=<project-name> --service=<svc-name> --image=<img-name> --tag=<tag>

then the continuous delivery process stops at the dev stage, i.e., the service is not deployed in the production stage.
The bridge looks as follows:

The logs of the gatekeeper-service reveal that there is no deployment strategy is defined for, hence the --deployment-strategy flag was not taken into consideration.

Keptn Version (keptn version): 0.7.1

Expected behavior
The onboarded service passe both stages, dev as well as production
Current behavior
The onboarded service is only deployed in dev stage, as to keptn there is no deployment strategy is defined

In order to execute the continuous-deployment use case with Keptn, we always assume that there is a deployment_strategy defined in the shipyard. Hence, the gatekeeper-service tries to parse the deployment_strategy field defined in the shipyard. However, your shipyard does not define anydeployment_strategy.
I agree that this assumption is not reasonable especially when defining a deployment strategy using the --deployment-strategy flag of the CLI.
However, in 0.8.0 we will remove this --deployment-strategy flag. Hence, I would propose to not fix this issue.

However, in 0.8.0 we will remove this --deployment-strategy flag. Hence, I would propose to not fix this issue.

Agreed. I'll leave this issue open and assign it to 0.8.0 though.


🫨

Is your feature request related to a problem? Please describe.
I'm always frustrated when🫨 shows up as the unicode box
Describe the solution you'd like
A clear and concise description of what you want to happen: please implement this as well as the new emojis 🙏
Describe alternatives you've considered
coping
Additional context
pleeeeees

This repository is no longer maintained, please check out https://github.com/jdecked/twemoji!

Was this decision made pre-elon or after-elon?


Fix Issue 414: outputType being Ignored

Bug fix for issue #414
Previously, outputType was not passed to doExportPresentation() when the function gets called in callbackImgToDataURLDone(). This mean that if the output pptx had any data that required base64 conversion, the output type would be disregarded.
This PR sets outputType to be part of gObjPptx when the user calls pptx.save(). Then when doExportPresentation() gets called, outputType will be fetched from gObjPptx

Hi @hktony0129
This is fixed in version 3.0


Treat "date-span" string formats as System.TimeSpan

Motivation
Swashbuckle commonly outputs TimeSpan types as date-span string formats in the output Swagger specifications.
Modifications
Treat date-span the same as partial-time.
Fixes #214

/merge


Fix typo in README.md

Hello!
I noticed a small typo in README regarding encryption cert loading. Here is the fix.

The changes are already merged in PR #17


HADOOP-17851. Support user specified content encoding for S3A

#3312 by @holdenk rebased & with some final wrap-up tweaks.

"fs.s3a.object.content-encoding" declares the content encoding
it's not set for directories.
it's documented this is a verification code text messages for some online account

I changed the key name to line up for adding the rest of the standard headers as/when we choose; fs.object.* would cover the set.
Tested, s3 london, no s3guard. One test failure, the usual intermittent ITestPartialRenamesDeletes.testRenameDirFailsInDelete

[X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ X] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 54s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 3 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
34m  5s

trunk passed

+1 :green_heart:
compile
0m 44s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
0m 36s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
0m 27s

trunk passed

+1 :green_heart:
mvnsite
0m 42s

trunk passed

+1 :green_heart:
javadoc
0m 21s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 31s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
1m  9s

trunk passed

+1 :green_heart:
shadedclient
22m 12s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 19s

the patch passed

+1 :green_heart:
mvnsite
0m 35s

the patch passed

+1 :green_heart:
javadoc
0m 14s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 23s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
1m 10s

the patch passed

+1 :green_heart:
shadedclient
21m 57s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 47s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

92m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3498/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3498

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell markdownlint

uname
Linux c4c99f55b520 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f45736768f604cb43efd31c422b5568e72664e82

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3498/1/testReport/

Max. process+thread count
518 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3498/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

merged into trunk. To get into 3.3 we will need the CSE backport, which is blocked on #3466, and probably also needing #3260 just for completeness & to maintain a consistent ordering

Yay, thanks @steveloughran and everyone for their review time and help I appreciate it :)


Added Command as a replacement for Actions

Command - replacement of Actions (closures)
This new type was added to replace our old implementation of closures usage.
CommandWith is a generic struct with type T, where T is a closure that you send.
To present your variable as a Command, you should specify its type. By default, Command has an empty closure that doesn't receives and doesn't returns anything:(Void) -> (Void). To use any other type as a received one, you should specify it as CommandWith<Type>.

Discussion summary: rename xxxCommand to xxxAction in variable names.

@RomanTysiachnik If you haven't started this yet - we discussed this with @AlexeyDemedetskiy - we can follow onXxx pattern here. This will hide the implementation details (Action or Command) - and still will be clear named.

@AndriiMoskvin @AlexeyDemedetskiy onXxx? Maybe better xxxOn?

@AndriiMoskvin! I've discussed with @AlexeyDemedetskiy about these names and I'm agreed with him, that it should be left as it was (with Actions). It looks and sounds perfect and if we change these names, it won't change anything eventually. If there would be an urgent need to change it, I will do it in another PR.


Uncaught TypeError: Cannot convert undefined or null to object

Upon opening the "References" page, it shows the "Uncaught TypeError: Cannot convert undefined or null to object" message in the console (see the image below). The "Add to Zotero" button does not respond. What would be a possible cause?

Thank you for uploading the console error! I think I've located it (missing check on the API key's group permissions), working on a fix now.

Thanks for the quick update! For the time being, changed the group permission and everything is working as expected.


feat(batcher): add decision reached response struct

This change is

#2722
#2721  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


cmd/compile: internal compiler error: "schedule does not include all values in block" on linux-s390x-ibm

See also #37246.
https://build.golang.org/log/37189dee0a49af1e6e538c7e05d0e6a402f5a210
# golang.org/x/perf/internal/stats
internal/stats/utest.go:127:13: internal compiler error: 'MannWhitneyUTest': schedule does not include all values in block b80

goroutine 21 [running]:
runtime/debug.Stack(0x9c51a0, 0xc00000e018, 0x0)
	/data/golang/workdir/go/src/runtime/debug/stack.go:24 +0x98
cmd/compile/internal/gc.Fatalf(0xc000b96080, 0x36, 0xc000a7dba0, 0x2, 0x2)
	/data/golang/workdir/go/src/cmd/compile/internal/gc/subr.go:193 +0x170
cmd/compile/internal/gc.(*ssafn).Fatalf(0xc000a667e0, 0xd0007f0d1, 0x870026, 0x30, 0xc000a5b3e0, 0x1, 0x1)
	/data/golang/workdir/go/src/cmd/compile/internal/gc/ssa.go:6857 +0x184
cmd/compile/internal/ssa.(*Func).Fatalf(...)
	/data/golang/workdir/go/src/cmd/compile/internal/ssa/func.go:625
cmd/compile/internal/ssa.schedule(0xc0004d8420)
	/data/golang/workdir/go/src/cmd/compile/internal/ssa/schedule.go:293 +0x1194
cmd/compile/internal/ssa.Compile(0xc0004d8420)
	/data/golang/workdir/go/src/cmd/compile/internal/ssa/compile.go:93 +0x946
cmd/compile/internal/gc.buildssa(0xc0000d8420, 0x3, 0x0)
	/data/golang/workdir/go/src/cmd/compile/internal/gc/ssa.go:460 +0x93c
cmd/compile/internal/gc.compileSSA(0xc0000d8420, 0x3)
	/data/golang/workdir/go/src/cmd/compile/internal/gc/pgen.go:296 +0x40
cmd/compile/internal/gc.compileFunctions.func2(0xc000a83140, 0xc000498240, 0x3)
	/data/golang/workdir/go/src/cmd/compile/internal/gc/pgen.go:361 +0x40
created by cmd/compile/internal/gc.compileFunctions
	/data/golang/workdir/go/src/cmd/compile/internal/gc/pgen.go:359 +0x116

CC @mundaym @randall77

Steps to reproduce (I used the compiler at revision 83bfe3b1bf and perf at revision 9c9101da83):
git clone https://go.googlesource.com/perf
cd perf/internal/stats
GOOS=linux GOARCH=s390x go test -c

Output:
# golang.org/x/perf/internal/stats [golang.org/x/perf/internal/stats.test]
./utest.go:127:13: internal compiler error: 'MannWhitneyUTest': schedule does not include all values in block b80

goroutine 29 [running]:
runtime/debug.Stack(0xd6ff40, 0xc00000e018, 0x0)
	/home/michael/Development/go/master/src/runtime/debug/stack.go:24 +0x9d
cmd/compile/internal/gc.Fatalf(0xc0003f9d40, 0x36, 0xc000a98380, 0x2, 0x2)
	/home/michael/Development/go/master/src/cmd/compile/internal/gc/subr.go:193 +0x1aa
cmd/compile/internal/gc.(*ssafn).Fatalf(0xc0009cf680, 0x7f0d10000000d, 0xc1c4a1, 0x30, 0xc0003f6d60, 0x1, 0x1)
	/home/michael/Development/go/master/src/cmd/compile/internal/gc/ssa.go:6843 +0x19b
cmd/compile/internal/ssa.(*Func).Fatalf(...)
	/home/michael/Development/go/master/src/cmd/compile/internal/ssa/func.go:625
cmd/compile/internal/ssa.schedule(0xc000b634a0)
	/home/michael/Development/go/master/src/cmd/compile/internal/ssa/schedule.go:293 +0x1abd
cmd/compile/internal/ssa.Compile(0xc000b634a0)
	/home/michael/Development/go/master/src/cmd/compile/internal/ssa/compile.go:93 +0x9bb
cmd/compile/internal/gc.buildssa(0xc0000e89a0, 0x3, 0x0)
	/home/michael/Development/go/master/src/cmd/compile/internal/gc/ssa.go:460 +0xcca
cmd/compile/internal/gc.compileSSA(0xc0000e89a0, 0x3)
	/home/michael/Development/go/master/src/cmd/compile/internal/gc/pgen.go:296 +0x5d
cmd/compile/internal/gc.compileFunctions.func2(0xc000b97260, 0xc000017da0, 0x3)
	/home/michael/Development/go/master/src/cmd/compile/internal/gc/pgen.go:361 +0x49
created by cmd/compile/internal/gc.compileFunctions
	/home/michael/Development/go/master/src/cmd/compile/internal/gc/pgen.go:359 +0x128

I printed a bit more information. The scheduler seems to assume the Select0 and Select1 ops are always in the same block as their argument, which is probably necessary for register allocation, however that invariant appears to be broken in this case:
schedule does not include all values in block b80
  value not found: v724 = Select1 <flags> v616 (block b80)
    argument 0: v616 = FSUB <float64,flags> v282 v403 (block b70)

Floating point ops generating flags was added in CL 209160. I think the oversight in that CL is that the new rules do not force the Select1 to be in the same block as the original value:
(LTDBR (Select0 x:(F(ADD|SUB) _ _)))   -> (Select1 x)
(LTEBR (Select0 x:(F(ADDS|SUBS) _ _))) -> (Select1 x)

The solution is probably to replace these rules with:
(LTDBR (Select0 x:(F(ADD|SUB) _ _)))   && b == x.Block -> (Select1 x)
(LTEBR (Select0 x:(F(ADDS|SUBS) _ _))) && b == x.Block -> (Select1 x)

Alternatively we could use @x.Block, but we probably don't want to move the block that the flags are generated in for this optimization.
cc @ruixin-bao

Thank you for looking into this issue.

Steps to reproduce (I used the compiler at revision 83bfe3b and perf at revision 9c9101da83):

I am able to reproduce it as well.

The solution is probably to replace these rules with:
(LTDBR (Select0 x:(F(ADD|SUB) _ _)))   && b == x.Block -> (Select1 x)
(LTEBR (Select0 x:(F(ADDS|SUBS) _ _))) && b == x.Block -> (Select1 x)

It looks like so. FWIW, I have tested the CL you sent and can confirm it fixes the problem.


Use native reponav dropdown if available

Fixes #1269
Not tested on GHE. @Naramsim can you try this branch?
Style matches the native one as well:

And it should look like this on GHE (mockup):

Fine on my side 😄  You are so quick!

Since you're here, do you have a Dependencies page on your GHE? Likehttps://github.com/sindresorhus/refined-github/network/dependencies


Allow passing memoryview/buffers to send

As nanomsg doesn't provide multipart messages it's convenient to create a BytesIO and dump a sequence of pickles into it. That way the "parts" of the message can be recovered at the other side by means of an equivalent sequence of pickle loads.
But the current implementation of Socket.send in nnpy requires the memoryview associated with the BytesIO to be transformed to bytes first:
TypeError: initializer for ctype 'char[19]' must be a bytes or list or tuple, not memoryview

This is not efficient, as it implies an extra copy of the message. But it seems the cffi guys implemented a conversion from buffer to char array:
https://bitbucket.org/cffi/cffi/issues/65/support-memoryview-to-char-conversion
https://bitbucket.org/cffi/cffi/issues/47/creating-a-cdata-from-a-buffer
I think it's important to support this in nnpy, as nanomsg is intended to be fast and require as little copy as possible.

I don't have the time to create a PR just right now but this seems to work fine in python 3:
    def send(self, data, flags=0):
        if isinstance(data, memoryview):
            buf = ffi.from_buffer(data)
        else:
            data = data.encode() if isinstance(data, str) else data
            buf = ffi.new('char[]', data)
        rc = nanomsg.nn_send(self.sock, buf, len(buf), flags)
        assert rc > 0, rc

Thanks for reporting and the fix!


Update links on product roadmap page

Direct links to Notion.so documents were in the old format without a subdomain.
This behaviour was changed in July 2021.
Source: https://www.notion.so/blog/personalize-public-pages

@warnaa congrats for your first PR


401 unauthorized

I'm getting the following when starting the bot:
Gateway     Discord.Net.HttpException: The server responded with error 401: 401: Unauthorized

The bot is in my server, it has all the right permissions and I enabled all Privileged Gateway Intents.

You have specified the wrong discord_bot_token in config file

Thanks that was a mistake on my part, however I'm getting this now:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Starting character setup...
(ID: 6HhWfeDjetnxESEcThlBQtEUo0O8YHcXyHqCgN7b2hY)

Fetching character info... Error!
 Request failed! (https://beta.character.ai/chat/character/info/)

Setup has been aborted
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

That's a public bot (elon musk) and i tried different bots too, it just doesn't work.

Did you try use both find command and browser methods of character setup?

Nvm, I see that's a bug. cAi was updated recently, and now you can't start a chat with a character you have never speak to with this bot. I'll make an update soon.
For now, you have only one option to go with:

Open your browser with the same cAI account you use in bot
Write any message to a character you want to set in bot
Now you can set it up
(or you don't as they could change something again while I wasn't waching D:)

It still doesn't work

It does on my side. I guess you'll have to check your char_ai_user_token for a third time.
My bad that there's such a poor failure log with no details at all... Although, it is already changed in the incomng update too.

It should almost exactly like one in readme

Yah that's the one I copied from the console. I also see that it's making a request to https://beta.character.ai/chat/character/info-cached/ in the browser instead of https://beta.character.ai/chat/character/info/ maybe that's the problem? Maybe you changed that in your current version and that's why it's working for you?

I've checked it with an old one

https://beta.character.ai/chat/character/info-cached/
It's only a browser's thing. There's no caching in this bot.

Ok, it must be a Windows thing. I just tested it on linux and it's working fine there.

🤷

@JcynR
Many underhood things were changed in #21
If you still need it on Windows, try it out


pop medial wall before multivariate zscoring?

hyperintensity on medial wall giving zscore of ~19

the reports are done by @rcruces


[usecase-embedding] Add 4 use case for validating performLongClick an…

…d requestFocus
Impacted TCs num(approved): New 4, Update 0, Delete 0
Unit test Platform: Android
Android test result summary: Pass 2, Fail 2, Block 0
Bug for LongClick listener is reported
https://crosswalk-project.org/jira/browse/XWALK-5018

LGTM


Remove hard coded username

GitHub Issue: n/a
What does this Pull Request do?
Within Catalyst we're using a custom base box for our development environments.
The provisoning scripts in this repository assume that CLAW is to be installed
as the ubuntu user, which does not exist on our box.
This PR introduces the variable CLAW_USER through configs/variables,
which is automatically set to the owner of the supplied home directory.
This allows to run the CLAW Vagrant environment with a different base box,
by just changing the home_dir in the Vagrantfile instead of hunting down
all occurrences of the ubuntu user in scripts and config.
What's new?

Added CLAW_USER variable to configs/variables that is set to the owner of the supplied home directory
Changed installation scripts to use the CLAW_USER variable instead of ubuntu
Changed installation scripts to also replace the home directory in configs where required

How should this be tested?

Bring up a fresh vagrant environment with vagrant up
Ensure the provisioning completes without errors

I've tested these changes against:

The newest public ubuntu/xenial64 base box for VirtualBox (v20171116.0.0)
Our internal xenial base box for LXC (which is using the vagrant user instead of ubuntu)

Interested parties
@Islandora-CLAW/committers

@fkleon this all seems fine, however I will note that we are hoping to deprecate this in favour of https://github.com/Islandora-DevOps/claw-playbook. So I am wondering if you want to continue with this PR or have a look at the ansible playbook and see if similar changes (there might already by a similar PR there) would be better?

Hi @whikloj - you're right, I'm actually looking at the Ansible playbook as well.
There were some similar issues to sort out, and a few unrelated kinks. I hope to prepare some pull requests for that on Monday. All in all the Ansible provisioner offers a much smoother experience!
However since this Shell provisioner is still supported and the work was already done, I decided to go ahead with this PR.


[MM]: When clicking on empty space, megamenu does not close causing stacking

Detailed description

Describe in detail the issue you're having.

When clicking on any empty area not associated with a link on the megamenu, the megamenu opens and closes and then remains stuck open. When user then clicks on another L0 nav item, the menu stacks on top.

Is this a feature request (new component, new icon), a bug, or a general
issue?

Bug

Is this issue related to a specific component?

MegaMenu

What did you expect to happen? What happened instead? What would you like to
see changed?

The menu should not close when user clicks on the empty space and when user opens another menu, the previous one should close.

What browser are you working in?

Chrome

What version of the IBM.com Library are you using?

v1.10.0
Steps to reproduce the issue

Click on any L0 nav item (ie, Products & Solutions)
Click on any empty space within the megamenu
Click on another L0 nav item (ie. Services & Consulting)
See how the menus stack

Additional information

hmm, when I was discussing functional specs with James I didn't want it to close if the user accidentally clicked on an empty space within the background of the mega menu container.
But the overlapping action is a problem because clicking on an empty space seems to lose the focus and then the menus don't realize one is open.

Agreed—even when clicking in the large empty space on either side when the browser is large, it should not close as long as the click happens inside the megamenu container.

Praveen and Chetan tested this bug fix.  Looks good.  Can be closed.


[Bug] An activated modal from first entry in ng-repeat elements does not use updated $scope variables

Note: for support questions, please use one of these channels: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#question. This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
Report a bug
What is the current behavior?
When the first ng-repeat element is clicked and 1) a $scope variable is change and 2) a modal appears, the modal that appears will not display the updated value for the $scope variable.
(all elements after the first ng-repeated element call a modal with the correctly updated variable).
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (template: http://plnkr.co/edit/tpl:yBpEi4).
When I run the template http://plnkr.co/edit/tpl:yBpEi4 I get Hello {{name}}! so the template is broken...
What is the expected behavior?
The modal called by the first ng-repeated element should have the updated $scope variable (just like a modal called from all subsequent elements after the first one).
What is the motivation / use case for changing the behavior?
N/A
Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
This never worked. All Browsers (I think). angular 1.4.9
Other information (e.g. stacktraces, related issues, suggestions how to fix)
I use a hack to get around this by making a blank zeroth object in the array I am using in ng-repeat. That object has a boolean property that is checked by ng-if and ng-if prevents the first entry from being made. That way the first visible element is really the second entry in the ng-repeated array (which is not bugged)

We can't investigate this without a reproduction. The template (http://plnkr.co/edit/tpl:yBpEi4) is not broken btw. It works fine for me.

O.o

got plnkr to work on  chrome (ff wasn't working) i'll make an example now.

I tried making plunker launch a modal and it doesn't...
http://plnkr.co/edit/kHi4kyqIo1JjtJlEEUDr
(I just copy pasted the example HTML code from http://getbootstrap.com/javascript/#modals "Live Demo" section)

@zinroc Well you have some errors in the console you should fix. Angular is not defined and you need to include jquery.

Just forget it -_- I'm not going to debug why the plunker angular template doesn't have angular defined...


Use Node.js 6.10 runtime

This PR updates the Node.js version used to build function.zip to 6.10 and makes it compatible with the new Node.js version offered by Amazon. The NPM packages are also updated to their latest versions.

Dope! I'll review this asap. Very excited to get this merged and thanks so
much for contributing!
On Sat, Apr 1, 2017 at 3:25 PM Jorrit Schippers<EMAIL_ADDRESS>wrote:

This PR updates the Node.js version used to build function.zip to 6.10 and
makes it compatible with the new Node.js version offered by Amazon. The NPM
packages are also updated to their latest versions.
You can view, comment on, or merge this pull request online at:
https://github.com/awslabs/serverless-image-resizing/pull/19
Commit Summary

Use Node.js 6.10 runtime

File Changes

M Dockerfile
https://github.com/awslabs/serverless-image-resizing/pull/19/files#diff-0
(2)
M README.md
https://github.com/awslabs/serverless-image-resizing/pull/19/files#diff-1
(2)
M dist/function.zip
https://github.com/awslabs/serverless-image-resizing/pull/19/files#diff-2
(0)
M image-resize.yaml
https://github.com/awslabs/serverless-image-resizing/pull/19/files#diff-3
(2)
M lambda/package.json
https://github.com/awslabs/serverless-image-resizing/pull/19/files#diff-4
(4)

Patch Links:

https://github.com/awslabs/serverless-image-resizing/pull/19.patch
https://github.com/awslabs/serverless-image-resizing/pull/19.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/serverless-image-resizing/pull/19, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABNP91MdYpdaXIEEn0USUWsAMqSDkxLks5rrqSSgaJpZM4Mwlmq
.

No problem! Please test it, my tests were only in combination with several other modifications I use for my app.

I fixed it. Is it really necessary to have the zip in the git repository? It seems to me that it is better to have an official release every now and then and publish the built zip file as a binary attachment to the release.

It's not strictly necessary, no, but that's where I linked to in the blog post. It probably would have been better to post the distribution file to an S3 bucket but I did this for expediency.

Hmm, I still changes when I make clean && make dist in the zip file.

Which ones? Maybe you can make the dist file then?

Sure, I'll merge and rebuild.

Thanks!


Move to libpldm APIs

libpldm provides APIs for allocating instance IDs directly, which eliminates the need for remote dbus calls to the pldm daemon. Refactor the code to use these APIs and eliminate all the dbus operations.

Replace pldm transport APIs with libpldm pldm_transport APIs to remove the dependency on pldm.

This change removes the dependency on pldm by utilizing the standardized libpldm APIs for transport operations, improving maintainability and compatibility.
We don't currently have the infrastructure in place to get the correct TIDs, so to keep everything working as before use the EID as the TID in the EID-to-TID mapping.
Change-Id: I348d54d9b5db47ef706cf7935e01ab8e7a55a594

I created one commit for both instance ID API and transport API changes.
Changes are similar to phosphor-debug-collector, waiting for review,
https://gerrit.openbmc.org/c/openbmc/phosphor-debug-collector/+/72594
https://gerrit.openbmc.org/c/openbmc/phosphor-debug-collector/+/72595


Screen Shake Append to Character

What feature do you want to get added on the base engine?
This is a humble request to allow for appending Screen Shake values to individual characters. Ideally this would also allow for player characters to shake the screen, but this is only an added layer of flavor.
How this would work is the intensity increments by 0.01 as opposed to 0.05, while duration still increments in 0.05 so as to not break the schema.
OPTIONAL BONUS: Add the ability to increment shake duration and health drain in lower values than 0.05, such as 0.005 or 0.001. That would certainly make my day much better.
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor and 6K+ support.

I’ll see if I can make that happen

What feature do you want to get added on the base engine?
This is a humble request to allow for appending Screen Shake values to individual characters. Ideally this would also allow for player characters to shake the screen, but this is only an added layer of flavor.
How this would work is the intensity increments by 0.01 as opposed to 0.05, while duration still increments in 0.05 so as to not break the schema.
OPTIONAL BONUS: Add the ability to increment shake duration and health drain in lower values than 0.05, such as 0.005 or 0.001. That would certainly make my day much better.
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor and 6K+ support.

This is a cool suggestion, I will add this in!

however, why would shake duration be needed is a question i have?

for a funny should i make the shake duration stack

yeah, sustains should count as note hits to the shake

Ok


Vhds readme

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description: Adds documentation for on-demand VHDS/RDS
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

Drive by: Can this instead be in the public docs vs. a markdown file? We should be talking about this probably in these locations:
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/operations/dynamic_configuration
https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol (maybe if anything is different here)
https://www.envoyproxy.io/docs/envoy/latest/configuration/http_conn_man/rds
Thank you!

BTW: IIRC we are moving docs to docs/root/ with .rst instead of .md. I could be wrong.

High level comment. Can we please add references to VHDS from the other places that I mentioned? There should be docs in the HTTP arch overview, etc. Basically I think anywhere we mention scoped RDS we should also mention this. Thank you.
/wait

/reopen

Closing, we can merge this into https://github.com/envoyproxy/envoy/pull/8617

rebased
finished responding the previous round of feedback

Reopening as it seems like we are going to finish this out. This should include arch docs, detailed config docs, etc. please look at all the places RDS, SRDS, routing, etc. are mentioned and make sure include VHDS also. Thanks!

Thanks @mattklein123

@brian-avery please don't force push, it makes it very hard to keep track of what's going on during review.

@htuch Apologies. It's been a while since I rebased and the branch had diverged. This force push didn't  include any code changes, only a rebase onto the latest master so that I could pick up the .gitattributes file.

/wait

@htuch Apologies for the force push. Was a git commit ammend --author to fix the DCO failure.

@brian-avery @dmitri-d I would like to land this? Can we merge master and actually get the doc build passing? You can build docs locally using docs/build.sh. Thank you!
Also please do not force push again on this PR. It makes reviews extremely difficult. Thank you!
/wait

@htuch Please take a look.

/wait

#9317 was merged earlier; this is a pretty reasonable way to handle missing resources. Can we update the implementation to match? This shouldn't be a huge change.

This looks great to me!  Thanks for making all of those changes.

Epic! Thank you every one for seeing this through!


Style bug when workbench.editor.tabCloseButton is set to "left"

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.70.2
OS Version: macOS 12.5

Steps to Reproduce:

Set workbench.editor.tabCloseButton to left
Look at the tab's close button - it's too far to the left, butting up against the start of the tab (especially noticeable when hovered over) compared to when set to right

Comparison:

Agree. I think @misolori the change in https://github.com/microsoft/vscode/commit/10375e8c124fbfe7ab35dafa16b1f18d5d78f581 pushes the close button more to the left, can you elaborate why that was done?

I'm trying to remember why that was changed and can't remember, happy to remove if it doesn't appear to break anything.


remove "you can star our repo" text from chat room challenge

There are grammar mistakes in this one. I will submit a PR fixing them. I can't with the translations though.


Update README.md

elm-get => elm-package.
0.13 => 0.14
cabal install invocation based on src/BuildFromSource.hs

Awesome, thank you!


Info on some Canadian zones

Just wanted to make sure you saw this:
https://mm.icann.org/pipermail/tz/2020-January/028779.html
I haven't checked to see if it's already reflected here or not.
Thanks.

Thanks for bringing it to my attention. I'll include this in the next release.


Matches in Language should get priority

If you're interested in a general explanation of regexes, it gets shown way below in the list, with a lot of fuzzy matches first.
I think generally any match on a filename in "language" should be shown as the first option.

We have a zillion of search bar issues, both regarding the outlook and the content. So far, nobody had the time to take on that, apparently. I liked the idea of Richard but so far it also hasn't drawn much attention.

FYI Not got a lot of time at present. Just solved missing 'syntax/' file
problem. IMHO It's a result of an awful hack and bad documentation
standards. But I have a solution that I'm soon posting.
Search is next priority.
On Wed, 22 Mar 2023, 11:06 Márton Polgár, @.***> wrote:

We have a zillion of search bar issues, both regarding the outlook and the
content. So far, nobody had the time to take on that, apparently. I liked the
idea of Richard https://github.com/Raku/doc-website/discussions/127 but
so far it also hasn't drawn much attention.
—
Reply to this email directly, view it on GitHub
https://github.com/Raku/doc-website/issues/222#issuecomment-1479362461,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACYZHBSINFGKXRMHVXCXA3W5LMMZANCNFSM6AAAAAAWCRLKCU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

#127 was/is great, but it various points  should be addressed by more specific Issues like this #222.
The glossary should be considered for first place.

The ordering of the search candidates puts 'Language' files first in new search. I think this issue has been completed.
@coke, please review for closing


Audio Recording is not working

On iOS 16.1, iPhone 14 pro max:

Audio inputs(app and mic) are not recording.
On console doesn't throw any error.

Is it something to do with output settings?

Hi Mehmet!
Thank you for submitting the issue!
I have not 14 pro max to debug the issue.
But if you have, you may check on your own
I may suggest, the issue about compressionProperties
at BroadcastWriter.swift:22 AVVideoExpectedSourceFrameRateKey: 60.nsNumber

I can replicate the issue on iPhone 12, iPhone 13, iPhone 13 pro, iPhone 13 mini, iPhone SE(2nd Generation) and iPhone 12 Pro. I believe it is about the iOS 16 change not device issue.

i have an iPhone 12 Pro w, so I can try to reproduce. So in your case you do not have a video in result, only audio, right?

Sorry for the typo. Only the audio is not working(no mic nor app audio), video is working fine :)

Okay, I'll try to check and fix in next few days

I have a similar codebase as BroadcastWriter and in my case, the audio of the mic(strangely the audio of the app works fine) stops after 7:40 minutes.  Only happens in iOS 16 or higher. I don't see any issues on previous versions(15,14 and 13)
Do you have any suggestions on what might cause the issue?

So do I understand you right?
The issue is not about this repo?
Can you reproduce it on the Example project from this repo?

The same issue is happening in this repo as well. The problem is simply the audio of the mic is not working with iOS 16 on the devices I mentioned above.

Hi @romiroma ,
I have fixed the issue by adding and setting active the audio session configuration before starting to process AVAssetriter.

Hi @mehmetbaykar,
Can you please share sample code?  I have the same problem and still not solved.


Optional mapping of integers in the DB to class names for polymorphic relations

I'm working on a project that is likely to have its DB accessed outside of Laravel and PHP contexts.
For the sake of keeping the schema "clean", it might be nice if I could keep a mapping of integers to class names in Laravel instead of putting whole class names in the DB when doing polymorphic relations.
This also would have the added benefit of cutting down the amount of space needed to store rows that contain the references.
(FTR: In pure Laravel projects, this never bothers me much, but it would be nice to have the option.)

Ping @taylorotwell.

This is already achievable by overriding the morph class.

:+1:


🐛 Bug Report: RepoUrlPicker is not checking the owner existence

📜 Description
The RepoUrlPicker is not checking the owner existence or availability and while executing his value is the one associated with the token
👍 Expected behavior
While choosing the repository owner, if it is not existing, the FE should raise an error
👎 Actual Behavior with Screenshots
No check is done and instead of using the owner written by the user a "default" one is used
👟 Reproduction steps
Create a template like this:
apiVersion: scaffolder.backstage.io/v1beta3
kind: Template
metadata:
name: example
title: Example with RepoUrlPicker
description: This is a multicloud example done with Crossplane and Argo pipeline
spec:
owner: user:guest
type: service
parameters:
- title: Choose a location
required:
- repoUrl
properties:
repoUrl:
title: Repository Location
type: string
ui:field: RepoUrlPicker
ui:options:
allowedHosts:
- github.com
steps:
- id: publish
name: Publish
action: publish:github
input:
allowedHosts: ['github.com']
description: This is ${{ parameters.repoUrl }}
repoUrl: ${{ parameters.repoUrl }}
output:
links:
- title: Repository
url: ${{ steps['publish'].output.remoteUrl }}
Then while filling the parameter, use an unexisting owner, having the integration config for github configured into backend, and at the end the repository initialization will be done on the wrong owner (instead of the "non existing" owner, the token owner will be used)
📃 Provide the context for the Bug.
No response
🖥 Your Environment
I'm using backstage version 1.14.2 but the same happens with last version
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

Yeah, I think that theres some room for improvement here. It would be great if the RepoUrlPIcker could use your token for the SCM and be able to list the places that you have access to create so that it's an autocomplete box rather than free text. This ensures that the owner already exists, and that you also have read/write access to the org or owner repo already.

Ok so instead of checking while the flow is executing are you thinking to add the check while making field validation? Because I was thinking to add the check on the backend side during the flow execution, where it is supposed to have the usable token but maybe it's not the correct place for this kind of check

Yes I agree but this means that we need to include the logic on FE to understand if we have to use the integration token or the user token (this logic seems already present in the backend). The worst thing here is that I need to understand how to check the owner existence, I'm not an expert of the single library used to integrate Github/Gitlab/Bitbucket etc.. (and I don't know if the owner concept is spammed on all the platform). In the mean time I'm checking if it's possible for me (I need a company authorization before proceeding) to make the fix and publish it

Just coming back to this to give a little more direction on ideas for implementation. Thinking that we should add some more routes to the scaffolder-backend that can help surface the available options for each integration.
/v1/integrations/:provider/orgs or something like this, could produce a list of available ID's where the scaffolder has write permissions to, either using a provided github_token which could come from the user, or using the GITHUB_TOKEN in the integrations config.
Each provider has different API's, so I'd suggest that we start simple with like the github API to find out all the orgs that are available to these tokens, and return then in the JSON response and those can be consumed by the RepoUrlPicker.


Add PS3.0 support to Install-DbaInstance

Type of Change

[x] Bug fix (non-breaking change, fixes #5526 )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[x] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Enable PS3 users to use the command since it copies the config file to the remote computer using -ToSesssion syntax that is not available in PS3
Approach
New internal function Send-File to deliver the file through the session.
Screenshots

Any concerns about this one?

thank you both, and thanks for the backwards compat! <3


[QA] Minigames - Player's Face Blocks Game View in Word Search, Liquid Labyrinth, and Salad Slash

Explorer Alpha build versions:

v0.30.0

Issue Description:
In the Word Search game at (-75,-46), when entering the game while another player is active, the first person sees the face of the other player instead of focusing on the game.
STR:

Launch the explorer.
Go to Word Search at (-75,-46).
Enter the game while another player is already playing.
Observe if the other player's face is visible in first person.
Goto Liquid Labyrinth (-139,-28)
Repeat step 3 and 4.
Goto Salad slash (17,-114)
Repeat step 3 and 4

❌ Actual Result
The first person sees the other player's face instead of focusing on the game.
✅ Expected Result
The game should display only the Word Search interface, not the other player's face.
Additional Notes:
Windows 11. 12th Gen Intel(R) Core(TM) i7-12650H 2.30 GHz. nvidia geforce RTX
Macbook M1 Pro Sonoma 14.5

This issue is related to the multiplayer queue issue that allows multiple players to jump into the play zone, however we are working on avoiding players obstructing the vision of the game regardless the situation, this change is already present in multiple of the games already.


Tag 1.2.0-beta.1 version as beta and 1.1.0 as stable

Hello,
Could someone tag the current 1.2.0-beta.1 version as beta on npm and the 1.1.0 version as stable ?
Many tools used to check dependencies like npm-check-updates rely on these tags for their processing.
Thank you =)

any news on this?

Done; we should make this part of a to-be-developed automated build process /cc @Turbo87

@marcoow you could use something like https://github.com/ember-cli/core-object/blob/v2.x/package.json#L40-L42 on the beta branch

We don't have a beta branch. There's only master that we publish releases from every now and then.

yeah, noticed that after I wrote the comment...
right now this repo doesn't seem to use automatic publishing via TravisCI so I'm assuming you run npm publish manually. in that case you have two options:

use e.g. npm publish --tag beta whenever you do a beta release

write the beta tag in the package.json as linked above and remove it again once you do a stable releases

if you want to use TravisCI for publishing you will have to use the second option as the npm publish command that's run there isn't configurable other than through the package.json file.
it might make sense to have a stable branch, and merge the master branch with the new stuff in, once you want to promote the beta to stable. at the point of the merge we'd then need to make sure that the publishConfig in package.json is not merged in too, but once that is established it should work fine for future merges.

Yeah, I'd like to keep branching structure simple as long as possible. Right now it seems that automatic tagging support would be the only reason to split master/stable branches and I don't really think that's worth it. I also wasn't aware that these tags were even supported be npm. Are other Ember projects using them as well?

yes, we use them in Ember CLI itself, and now that ember-source is a thing they are used there as well. we've also used them for e.g. ember-cli-eslint last year when we had to support ESLint 2 and 3 at the same time.

OK, sounds like ESA should do so as well then. I'll make a mental note for now and we'll see whether that works or we need to set some process up for releases in the future.


Rooms can't be loaded unless you're logged in

This was caused by the commit that added gif support. File types were being loaded in the room when the user was logged in, but the code to load in file types wasn't duplicated to the other part of the if block for the case when the user wasn't logged in.


analyzer: "return_of_invalid_type" on ?? return

analyzer:
  strong-mode: true

$ dart --version
Dart VM version: 2.0.0-dev.3.0 (Wed Oct  4 03:03:29 2017) on "macos_x64"

The following triggers an error in the strong-mode analyzer:
import 'dart:async';

void main() {
  _currentLogger.log('test');
}

class Logger {
  void log(String message) {}
}

final _defaultLogger = new Logger();
// ignore: return_of_invalid_type
Logger get _currentLogger => Zone.current[#currentLogger] ?? _defaultLogger;

It doesn't in earlier versions of the analyzer (like on DartPad):
https://dartpad.dartlang.org/091cf8ac03704f58afd405119e551003
I would have sort of expected this maybe with implicit-casts: false, but even turning this option off doesn't make this work. I didn't actually try it in the VM, Dart2JS, or DDC, though.

  I can't repro this on fairly recent bleeding edge: I get the error with implicit-casts off, no error with implicit-casts on.

@matanlurey Is this still an issue, or can we close it?

I haven't seen this again, lets close it.


Does openfpga support the following crossbar？

When I was looking for a local routing architecture with 50% connectivity, I found that there are many places in VTR that have descriptions as shown in the figure below. In my opinion，wouldn't this create a physical conflict(two tags have a same output).
For this way of writing, can OpenFPGA automatically derive a mux, or does it not support this way of writing?

the  tag and  has a same output.

@narutozxp It may cause errors in OpenFPGA. If you want to build a sparse crossbar, I suggest you to look into examples：
https://github.com/lnis-uofu/OpenFPGA/blob/1f0f13ce0d1be583aee2733c61eb4d308e45e6b0/openfpga_flow/vpr_arch/k4_N5_tileable_pattern_local_routing_40nm.xml#L284-L297
https://github.com/lnis-uofu/OpenFPGA/blob/1f0f13ce0d1be583aee2733c61eb4d308e45e6b0/openfpga_flow/vpr_arch/k6_frac_N10_tileable_adder_register_scan_chain_depop50_40nm.xml#L626-L646

Close the issue as the crossbar is considered as illegal in physical representation.


idk

Hello @AdityaSeth777
Just fix a few things here.
Use the White HLV logo everywhere and do increase/decrease size whereever required
I could see the footer and the navbar and the titlepage with black logos, do change them.

also while u rename the files, keep the file names in camelCase like cseFarewellWhite.svg and cseFarewellBlack.svg