Bug Report: Security vulnerabilities

Note: We also welcome PRs to fix bugs! This helps us take action faster where a bug has been identified!
For our official CircleCI Docker Convenience Image support policy, please see CircleCI docs.
This policy outlines the release, update, and deprecation policy for CircleCI Docker Convenience Images.

Describe the bug
The image has multiple vulnerabilities, many of which are fixed in the upstream packages and so just a rebuild should fix them. From my count: "critical_fixable":1,"high_fixable":14,"medium_fixable":45
To Reproduce
Scan the image
Expected behavior
The packages to be up to date.
Workarounds
It's costly, but we could run the updates and host our own images.
Screenshots and Build Links
If possible, add screenshots and links to jobs to help explain your problem.
Additional context
We use this image in our ci workflows and ci is a major point of exploitation.

We've cut a new image tag 2024.08 built against the latest ubuntu 22.04 cimg/base, and with some updated tooling. Please run your scan on that image and see if it closes the vulnerabilities you have reported.


Works a couple of times then dies

Hi there,
This is a very cool library, thanks for putting it together.
Two things when I ran the next command:
python - m speech_recognition

it didn't work until I changed in line 21 on speech recognition main str for value
once I did that it works once and sometimes a couple of times but always get the the next
You said DS
Say something!
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/speech_recognition/__main__.py", line 28, in <module>
    print("Uh oh! Couldn't request results from Google Speech Recognition service")
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/speech_recognition/__init__.py", line 81, in __exit__
    self.stream.stop_stream()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pyaudio.py", line 524, in stop_stream
    pa.stop_stream(self._stream)
IOError: Stream not open

I'm not very sure what the problem is
Just in case here is  main
import speech_recognition as sr

r = sr.Recognizer()
m = sr.Microphone()

try:
    print("A moment of silence, please...")
    with m as source:
        r.adjust_for_ambient_noise(source)
        print("Set minimum energy threshold to {}".format(r.energy_threshold))
        while True:
            print("Say something!")
            audio = r.listen(source)
            print("Got it! Now to recognize it...")
            try:
                # recognize speech using Google Speech Recognition
                value = r.recognize_google(audio,key="AIzaSyB55R1xXklGJOGbYh_UpQ31MRWv_5LlG5c")

                # we need some special handling here to correctly print unicode characters to standard output
                if value is bytes: # this version of Python uses bytes for strings (Python 2)
                    print(u"You said {}".format(value).encode("utf-8"))
                else: # this version of Python uses unicode for strings (Python 3+)
                    print("You said {}".format(value))
            except sr.UnknownValueError:
                print("Oops! Didn't catch that")
            except sr.RequestError:
                print("Uh oh! Couldn't request results from Google Speech Recognition service")
except KeyboardInterrupt:
    pass

Give v3.1.2 a try - it should now gracefully handle the audio input ending.
Also, try upgrading PyAudio to 0.2.9! The new version fixes a tricky overflow issue.

I updated pyaudio and SpeechRecognition but same error. I'm going to try uninstalling and installing everything again later today. I will keep you posted.

Same here.
Actually, the problem started on recent versions.
I'm starting to wonder if it has something to do with newer pyaudio versions.

Reverting to pyaudio 0.2.8 stopped this specific problem.

Very strange, perhaps PyAudio 0.2.8 wasn't uninstalled correctly when 0.2.9 was installed? Can @julian-ramos confirm if downgrading to 0.2.8 helps with the issue?

I downgraded to 0.2.8 and got the next:
Traceback (most recent call last):
  File "/Users/ingenia/git/playground/speech_recognition_sample.py", line 13, in <module>
    audio = r.listen(source)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/speech_recognition/__init__.py", line 295, in listen
    buffer = source.stream.read(source.CHUNK)
  File "build/bdist.macosx-10.6-intel/egg/pyaudio.py", line 605, in read
IOError: [Errno Input overflowed] -9981

@julian-ramos Did you ever get this working?

sh-3.2# python -m speech_recognition
A moment of silence, please...
Set minimum energy threshold to 80.365360297
Say something!
Got it! Now to recognize it...
You said hi
Say something!
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 162, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/Library/Python/2.7/site-packages/speech_recognition/main.py", line 27, in
print("Uh oh! Couldn't request results from Google Speech Recognition service; {0}".format(e))
File "/Library/Python/2.7/site-packages/speech_recognition/init.py", line 80, in exit
if not self.stream.is_stopped():
File "/Library/Python/2.7/site-packages/pyaudio.py", line 543, in is_stopped
return pa.is_stream_stopped(self._stream)
IOError: [Errno -9988] Stream closed

@fairythink, that seems to be an instance of #71, so I'd recommend trying the latest suggestion in that issue and reporting the results there.
I think the original issue is fixed as of 3.2.0, so I'll close this for now. Feel free to re-open if it starts happening in the latest version.


Use parameters for VPC and subnets CIDR blocks

Fixes #183

@rbankston ptal

LGTM thanks for the turnaround


Bump version

Depends-on: #614

Codecov Report

Merging #615 (74b6959) into main (e296c4f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #615   +/-   ##
=======================================
  Coverage   84.82%   84.82%
=======================================
  Files         302      302
  Lines       26943    26943
=======================================
  Hits        22855    22855
  Misses       4088     4088

Continue to review full report at Codecov.

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


Clean up truffle compilation warnings

Whenever I try compiling contracts that import from the repo, I get some warnings:
`Compilation warnings encountered:
zeppelin-solidity/contracts/token/StandardToken.sol:73:3: Warning: No visibility specified. Defaulting to "public".
function increaseApproval (address _spender, uint _addedValue)
^
Spanning multiple lines.
,zeppelin-solidity/contracts/token/StandardToken.sol:80:3: Warning: No visibility specified. Defaulting to "public".
function decreaseApproval (address _spender, uint _subtractedValue)
^
Spanning multiple lines.
,zeppelin-solidity/contracts/ownership/Ownable.sol:20:3: Warning: No visibility specified. Defaulting to "public".
function Ownable() {
^
Spanning multiple lines.
,zeppelin-solidity/contracts/math/SafeMath.sol:9:3: Warning: Function state mutability can be restricted to pure
function mul(uint256 a, uint256 b) internal constant returns (uint256) {
^
Spanning multiple lines.
,zeppelin-solidity/contracts/math/SafeMath.sol:15:3: Warning: Function state mutability can be restricted to pure
function div(uint256 a, uint256 b) internal constant returns (uint256) {
^
Spanning multiple lines.
,zeppelin-solidity/contracts/math/SafeMath.sol:22:3: Warning: Function state mutability can be restricted to pure
function sub(uint256 a, uint256 b) internal constant returns (uint256) {
^
Spanning multiple lines.
,zeppelin-solidity/contracts/math/SafeMath.sol:27:3: Warning: Function state mutability can be restricted to pure
function add(uint256 a, uint256 b) internal constant returns (uint256) {
^
Spanning multiple lines.`
It might be nice to clean those up to prevent such printouts.

Confirm you're using the compiler than the OZ contracts are compiled with normally (currently 0.4.18). If it's time to upgrade we can upgrade to 0.4.19 and update our pragmas and fix these compilation errors.

Somebody help me, I have been compiling OZ ..getting this compilation warning
zeppelin-solidity/contracts/crowdsale/Crowdsale.sol:102:3: Warning: Function state mutability can be restricted to pure
function _preValidatePurchase(address _beneficiary, uint256 _weiAmount) internal {
^
Spanning multiple lines.
,zeppelin-solidity/contracts/crowdsale/Crowdsale.sol:112:3: Warning: Function state mutability can be restricted to pure
function _postValidatePurchase(address _beneficiary, uint256 _weiAmount) internal {
^
Spanning multiple lines.
,zeppelin-solidity/contracts/crowdsale/Crowdsale.sol:141:3: Warning: Function state mutability can be restricted to pure
function _updatePurchasingState(address _beneficiary, uint256 _weiAmount) internal {
^
Spanning multiple lines.
,zeppelin-solidity/contracts/crowdsale/distribution/FinalizableCrowdsale.sol:38:3: Warning: Function state mutability can be restricted to pure
function finalization() internal {
^

@Khokavim that is ok and expected — those are solidity compilation warnings and are required because even though it's correct (that visibility can be restricted, etc) we have to leave it open because the contracts that override these functions need to have those visibilities/state-access modifiers set correctly.

Also, the OpenZeppelin slack channel or stack overflow is the correct forum for these questions 😄


Get 404 when click on Create an issue link

Description:

Go to community page

https://v1-0.ballerina.io/community/

Click on here

Results 404. Link should be corrected to https://github.com/ballerina-platform/ballerina-lang/issues

Fixed with #1607


API authentication parameters in URL parameters

Behaviour
After adding API that requires authorization, API status shows:
"API backend is down for some reason. Please contact support."
Example:
"Yle API uses app_id and app_key URL parameters for authentication, Apinf should be flexible for different kind of API authorizations. It's not good to show "API backend is down for some reason. Please contact support.", if we are getting 401 not authorized."
Above comment from issue: https://github.com/apinf/api-umbrella-dashboard/issues/917
Expected
When getting 401, show info "API requires authentication" or allow 401 to be successful status.

@frenchbread will you take this task? It may be that we need to pass the HTTP response code to the user, and allow other status codes than 200.


Suggestion: filter by other parts of URL

It seems a shortcoming that Exceptionless only lets one filter exceptions by Path, and no other part of the URL.
Specifically, It'd be useful to be able to filter on the domain that requests are made to.

Hmm, yeah, it would be nice to have the host and possibly port as well indexed. Not sure how much sense it would make to index any of the others..
Is there any chance you'd be willing to submit a pr for this? You'd just need to edit the EventIndexType here: https://github.com/exceptionless/Exceptionless/blob/master/src/Exceptionless.Core/Repositories/Configuration/Indexes/EventIndex/EventIndexType.cs#L210

Great, thanks!

This should be fixed in elastic 7. We are now allowing users to search by partial paths and we are splitting the host field on ..


Couldnot locate openfast3.0_x64s.exe in matlab-toolbox-main folder

Hello
I am trying to execute the mfile scripts but getting the errors 'could not locate openfast3.0_x64s.exe in _ExampleData folder'.
I tried locating the file but there is no such file.
It will be great to get a response.
Thanks

Hi,
We do not provide binaries of OpenFAST as part of this repository as it would make the repository too big.
You'll need to adapt the script to point to an openfast executable  that you have on your machine.
You can download them from the openfast repository: https://github.com/OpenFAST/openfast/releases
Please note that the OpenFAST input files change from one OpenFAST version to the next, so you might run into issues with your OpenFAST executable not matching with the example inputs of this repository. We try to keep the input files in this repository up to date with the latest version of OpenFAST, but we sometimes miss some.
I hope that helps
Emmanuel


Fix cleanup process in  _delete_node of document_summary

Description
Cannot remove doc from DocumentSummaryIndex by delete_ref_doc(...)
As designed, the user can remove the nodes from the document summary index according to "doc_id" by delete_ref_doc(...) which will call delete_nodes(...) from BaseIndex to do the work.

However, it passes the related node_ids instead of doc_id itself.

Fixes # (issue)
Type of Change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] I ran make format; make lint to appease the lint gods

Going to close this due to innactivity. Please do port the change to v0.10.x and address the comments if you still feel you need this.


Fix lint errors

It fixes most of the lint errors.
Just a few left:

@ngokevin the 'ga' is not defined in multiple files, should I just add /* global ga */ for each file or we should ignore it in any file from the config?
dangerouslySetInnerHTML will be changed in a future PR to fix some of the scenegraph's code.

I'd ignore the ga errors for now, I will most likely introduce the cross-origin analytics where I have to add a central helper. So I won't be using hthe global.

r+wc/rebase


Build with GHC 9.2.1

I am getting this build error:

https://github.com/haskell/haskell-language-server/runs/4625279018?check_suite_focus=true#step:15:838

I am trying #47 with hls and it seems to work

I am trying #47 with hls and it seems to work

Maybe unix-compat-0.5.1 needs an upper bound on Win32 just like https://hackage.haskell.org/package/unix-compat-0.5.2/revisions/ ?

On a Windows machine,
cabal install -w ghc-9.2.2 unix-compat-0.5.1

fails nowadays already in the configuration step.
I think this issue can be closed.


npm run dev  Error

i follow the Guide  , but when i run npm run dev i get error:

 engine-seed git:(master) npm run dev

><EMAIL_ADDRESS>dev /Users/xieyiming/code/famous/engine-seed
> node ./bin/dev.js

serving /Users/xieyiming/code/famous/engine-seed/public on port 1618

module.js:340
    throw err;
          ^
Error: Cannot find module 'glsl-tokenizer/string'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/xieyiming/code/famous/engine-seed/node_modules/famous/node_modules/glslify/node_modules/glslify-deps/index.js:1:78)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

npm ERR<EMAIL_ADDRESS>dev: `node ./bin/dev.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev script.
npm ERR! This is most likely a problem with the engine-seed package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./bin/dev.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls engine-seed
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 14.1.1
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev"
npm ERR! cwd /Users/xieyiming/code/famous/engine-seed
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.21
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/xieyiming/code/famous/engine-seed/npm-debug.log
npm ERR! not ok code 0

i have to install by my self
   "glsl-tokenizer": "~2.0.2",
   "graceful-fs": "~4.1.2",
   "map-limit": "0.0.1",
   "inherits": "~2.0.1"

and then :
engine-seed git:(master) ✗ npm run dev

><EMAIL_ADDRESS>dev /Users/xieyiming/code/famous/engine-seed
> node ./bin/dev.js

serving /Users/xieyiming/code/famous/engine-seed/public on port 1618

module.js:340
    throw err;
          ^
Error: Cannot find module 'events/'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/xieyiming/code/famous/engine-seed/node_modules/famous/node_modules/glslify/node_modules/glslify-deps/index.js:5:16)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

what's going on ?

I just installed the engine-seed without any problems. It looks like you're running into permission issues from the errors shown, e.g. npm ERR! Exit status 8 (http://stackoverflow.com/questions/21960111/node-js-express-npm-start-error-exit-status-8#21960610) and all the npm ERR!'s.
You could either install/run with sudo or fix your npm issues so you won't have those problems anymore:
https://docs.npmjs.com/getting-started/fixing-npm-permissions


pipenv uses wrong exit code when delegated process is killed

Issue description
In memory constrained environment, like a docker container, invoked subprocess can be OOM killed by the kernel but pipenv still exit with status code 0.
Expected result
Exit code should be different from 0.
Actual result
Exit code is 0.
Steps to replicate
I'm afraid I couldn't come up with a simple way to reproduce the memory pressure we got in production and have the OOM trigger at will on the right process. However, you will find below a clear description of why this can happen and how to fix it.
Origin of the problem
The issue comes from the pexpect delegator that treats positive and negative exit code differently. When the process is OOM killed, the exit code is negative (-15) and so exitstatus is set to None while signalstatus is set to 15 (see https://github.com/pypa/pipenv/blob/72835f142c8010f686ca26af21f3f9079d5bf997/pipenv/vendor/pexpect/popen_spawn.py#L166). As a consequence, when the delegator return_code property is checked, it return None because it ignore signalstatus. This is then passed to sys.exit(...) leading to a successful run of pipenv instead of failure.
Proposed fix
diff --git a/pipenv/vendor/delegator.py b/pipenv/vendor/delegator.py
index 19f27070..e2fb2a2a 100644
--- a/pipenv/vendor/delegator.py
+++ b/pipenv/vendor/delegator.py
@@ -168,6 +168,8 @@ class Command(object):
     def return_code(self):
         # Support for pexpect's functionality.
         if self._uses_pexpect:
+            if self.subprocess.signalstatus is not None:
+                return -self.subprocess.signalstatus
             return self.subprocess.exitstatus
         # Standard subprocess method.
         return self.subprocess.returncode

$ pipenv --support
Pipenv version: '2020.11.15'
Pipenv location: '/usr/local/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pipenv'
Python location: '/usr/local/.pyenv/versions/3.6.13/bin/python3.6'
Python installations found:

3.9.4: /usr/local/.pyenv/versions/3.9.4/bin/python3
3.8.8: /usr/local/.pyenv/versions/3.8.8/bin/python3.8
3.7.10: /usr/local/.pyenv/versions/3.7.10/bin/python3.7m
3.6.13: /usr/local/.pyenv/versions/3.6.13/bin/python3.6m
3.6.9: /usr/bin/python3.6m
3.6.9: /usr/bin/python3
3.6.9: /usr/bin/python3.6
2.7.18: /usr/local/.pyenv/versions/2.7.18/bin/python2.7

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.6.13',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '5.4.0-74-generic',
 'platform_system': 'Linux',
 'platform_version': '#83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021',
 'python_full_version': '3.6.13',
 'python_version': '3.6',
 'sys_platform': 'linux'}

System environment variables:

LC_ALL
LS_COLORS
LANG
HOSTNAME
PYENV_ROOT
PWD
HOME
BUNDLE_PATH
DEBIAN_FRONTEND
TERM
BUNDLE_SILENCE_ROOT_WARNING
BUNDLE_BIN
SHLVL
DEPENDABOT_NATIVE_HELPERS_PATH
PATH
_
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: .bundle/binstubs:/usr/local/.pyenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/dependabot/.bundle/bin:/opt/python/bin
LANG: en_US.UTF-8
PWD: /home/dependabot

Hello @frostming, would you have time to review this PR ? Or could you suggest somebody as reviewer ? Thanks!

@marco-m or @odormond is there an open PR or is the patch in the issue report the proposal for starting a PR?

delegator is dropped from the vendors, this issue can be closed


Fixed Typo in Registration Page

Fixes #331
Description
Fixed the typo in the registration page ( spelling of "Mobile Number" )

Screenshots

@sreeharianilkumar1 make sure there are no warnings in the console. Else the checks won't pass

@sreeharianilkumar1 make sure there are no warnings in the console. Else the checks won't pass

Why are the checks NOT Successful?
I created a new pull request #337 because the current one was not Upstream.
The new pull request is also failing the checks, please check #337

@sreeharianilkumar1 why there are two PRs for the same issue?


build: fix shell script

Fixes #49
Checklist

[ ] run npm run test and npm run benchmark
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

Nice I will test


Explore the Generated App and OData Service

In step 2 of this tutorial "Examine the generated application", I get this error message on the simulated device when I tap on either of the collections:
loading data failed!
dataserviceerror error 500 (internal server error)
{"code":"",message":"service excetion: [414] user is forced to change password"}

Tutorial URL: https://developers.sap.com/tutorials/fiori-ios-scpms-teched18-03.html

By getting this tutorial to work (https://developers.sap.com/tutorials/fiori-ios-scpms-create-sample-app.html) I think that the misstake is happening in the Destination setup.

Hi @TThorsager ,
I am sorry you experienced issues with the tutorial. Could you please off board the app and try on boarding again. Also you can delete the app and re-install. If that doesn't help could you please provide me some logs? While doing that I will verify the tutorial.
Thanks

Thank you for your feedback. We haven't heard from you in the past 30 days, so we are closing the issue.
If you still have questions, feel free to reopen the issue.


[FLINK-1840] Fix BLOB manager on Windows

closes open FileOutputStream before the field is moved
replaces java.io.File.renameTo() by com.google.common.io.Files.move() to avoid platform-dependent behavior

+1 LGTM


Fix remaining explicit URLs (incl. filter tabs)

Addresses DOC-10953
Summary of changes:

Convert ALL remaining www.cockroachlabs.com/docs/... links to use Liquid template syntax across all currently supported versions of CockroachDB (v23.1, v23.2, v24.1, v24.2).

NB. Only links were edited, no content changes were made whatsoever

cc @mdlinville FYI, this should be the last PR needing a port to cloud-2.0 branch.  The changes needed were too extensive to be done via script, so they'll have to be merged.  The good news is this PR only touches links, there are no content changes, so it "should merge properly" (tm) (famous last words lol).

Thanks for the review @taroface - just pushed commits that hopefully address all of your feedback!
Once build is green PTAL!
Thanks for reviewing this!


Respect "Preserve Log" setting in Network tab of Chrome Dev Tools

There are times when the list of network calls gets replaced by a new set of calls (not 100% sure what causes that, so maybe that's the bug), but checking the "Preserve Logs" checkbox doesn't prevent those items from being removed, as it should.

You can click "Clear" explicitly to remove entries, but I'm otherwise not aware of any way to have the entires removed automatically.  Note that due to #13 there may be other weird upstream bugs we don't know about that cause rendering glitches.
As far as preserve logs, I don't think that would help in either case.  That's designed to not clear the network traffic when navigating to another page which is a concept we don't even support currently :)


[Feature Request] Add support for testing dark mode

This is a feature request to test the dark mode support of an email.
Inspiration: https://proofjump.com/dark-mode-simulator/

Never mind!
It already works but it adopts the system theme not the theme you are switching in Mailpit UI.

The dark mode setting is actually for the Mailpit UI, and not how emails are rendered (they are always rendered in "light mode", ie: the standard). Dark mode in emails this is not as simple as it may sound, in fact it is very complicated, and each (of the very few) email clients that do have a native "dark mode" all apparently render this in their own unique / different way. In reality there appears to be no actual standard for dark mode emails, and thus almost no adoption (as far as I am aware). Email programs are a mess, really.
The website you linked to actually hardcodes the font, link and background colours for every html element in an email - very different to how a web browser applies dark mode for supporting websites, and likely very different to each of the few clients that support dark mode.
I believe that trying to support this feature in Mailpit (ie: a "fake" way of emulating dark mode) would only result in tonnes of bug requests with users expecting different results because their XYZ client does it differently. Please have a look at https://www.litmus.com/blog/the-ultimate-guide-to-dark-mode-for-email-marketers to see what I mean.

Agreed.
And because it can still adopt the system dark/light mode, we are still able to test. In case anyone trying to test the dark mode, just switch to dark mode at system level and mailpit or the browser itself should respect the preference.
closing this, as its not an issue anymore.
thanks for great work, Ralph ❤


How to read and write  istio crd

I have a yaml file like:
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: echo-vs
spec:
  hosts:
    - echo
  gateways:
    - main-gateway
  http:
    - match:
        - uri:
            prefix: /echo
      route:
        - destination:
            host: echo
            port:
              number: 8000

I want to modify some things like prefix and save to yaml file

Looking forward to any suggestions

kubectl get virtualservice This is a kubernetes question, please take a look at https://kubernetes.io/docs/reference/kubectl/cheatsheet/ or ask in Kubernetes slack overflow, etc. Thanks!


[SPARK-45930][SQL] Support non-deterministic UDFs in MapInPandas/MapInArrow

What changes were proposed in this pull request?

This PR supports non-deterministic UDFs in MapInPandas and MapInArrow.
Why are the changes needed?

Currently, MapInPandas and MapInArrow do not support non-deterministic UDFs. The analyzer will fail with this error:
org.apache.spark.sql.AnalysisException: [INVALID_NON_DETERMINISTIC_EXPRESSIONS] The operator expects a deterministic expression, but the actual expression is "pyUDF()".
This is needed for https://github.com/apache/spark/pull/43791.
Does this PR introduce any user-facing change?

No. Users cannot directly create a non-deterministic UDF in PySpark to be used in MapInPandas/MapInArrow.
How was this patch tested?

New unit tests.
Was this patch authored or co-authored using generative AI tooling?

No

cc @cloud-fan

Merged to master.


Minor issue building dtc

Perhaps it's a missing dependency upstream, but the make of dtc fails as version_gen.h is not provided in the dtc repo.  A 'make version_gen.h' is required before the make of dtc itself.  Thanx!

Is this using the dtc-compiler from NTC?  I haven't built DTC in a while, the ones with CHIP_IO also have the binary files that are installed via setup.py.

It's using the dtc from "atenarc" as per
https://github.com/xtacocorex/CHIP_IO So whether the issues is in the
atenarc dithub Makefile or your instructions is your call. I could see it
going either way.  Thanx.
On Thu, Dec 1, 2016 at 8:26 AM, Robert Wolterman<EMAIL_ADDRESS>wrote:

Is this using the dtc-compiler from NTC? I haven't built DTC in a while,
the ones with CHIP_IO also have the binary files that are installed via
setup.py.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xtacocorex/CHIP_IO/issues/29#issuecomment-264185952,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALdQDxXzWu7NNc4kEEkCBV9ymRloGOeeks5rDtkVgaJpZM4K9ZYy
.

In setting up a CHIP specifically for CHIP_IO dev, I forgot to setup the DTC compiler.  I didn't have to run the make version_gen.h when I got it all setup.  Will investigate this more once I get the PWM stuff figured out.

I'm removing the DTB compilation requirement from CHIP_IO. OverlayManager will handle the PWM and SPI sample dtb from chip-dt-overlays.  Going to close this.


merge new version

Hi @zmyer. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

please check your diff before making a PR, thank you


Rjf/traversal abstractions clone issue

This PR refactors the energy model build process so that all objects in the energy TraversalModelService are wrapped in Arc references if they are large heap objects, so cloning is not expensive. it cleans up the build removing one layer of indirection along the way.
TraversalModelService (and builder) traits were defined in routee-compass but have been moved to routee-compass-core so that they are available from the routee-compass-powertrain crate. build methods now return a TraversalModelError on failure, since CompassConfigurationError is no longer in scope.
It's probably a good low-hanging fruit task to move the rest of the builder traits to the core crate too.
i attempted to update the doc reference from the routee-compass crate that references TraversalModelBuilder, but i'm worried it won't take, that we can't make cross-crate references like that. we may need to replace those builder links with a direct hyperlink to the routee-compass-core docs at docs.rs.
Closes #34.

Perhaps I can merge this into the ndr/phev branch if/when we feel like it's in a good place since there a going to be a couple of merge conflicts related to the changes on the speed grade energy model?

sounds kinda like the same thing as merging this into main now though, right? either way the changes have to get merged into your branch.


refactor: remove and adjust header writing in fast writer

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.18%. Comparing base (a05bac2) to head (dfa3ef7).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
- Coverage   98.22%   94.18%   -4.04%
==========================================
  Files           7        1       -6
  Lines         507       86     -421
==========================================
- Hits          498       81     -417
+ Misses          7        3       -4
  Partials        2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


JSON output questions (int/string and locations array)

Please document the different output schemas (e.g. JSON, XML, text)

As I am using JSON currently, I wanted to point out that numbers such as locations[i].column and locations[i].line are being output as strings instead.

@ryaneberly --- do you know of anything downstream (like IDE tools, build server plugins etc) that would break if we fixed JSON datatypes?

@KamasamaK
In the dev branch (and from the next official release on), the Findbugs XML output style is actually compliant with the findbugs xml schema definition.
I guess you could probably quite easily come up with an xml schema for CFLint's "default"/internal XML - keen to tackle that @KamasamaK ?
I personally haven't used the JSON/text output, but should should be reasonably straight forward to document. You could start by documenting the current output (please use the dev branch) formats in the Wiki.

@TheRealAgentK,  I'm not aware of any issues with 'fixing' the number output in JSON with downstream tooling.  But I'm not familiar with many of the downstream usages.

@ryaneberly @KamasamaK I guess the question is then - do we want/need to have numeric values like the counts, line, column etc. as numeric data in JSON or are we ok with just leaving them as strings.
I'm not leaning very strongly either way here - what do other people think?

I think the goal should be to use the proper data types. Breaking compatibility is a potential concern, but it should be easy enough to work around if it's an issue. The only ones I've really looked into are Atom's linter-cflint plugin, which uses the XML output, and SublimeLinter's which uses the text output. The other projects I've seen just appear to be using the Java directly.
Actually, the reason this came up is that I was seeing if I could change Atom's linter-cflint to use JSON instead of XML output. I was successful, but I had to use parseInt() on the values which shouldn't be necessary. Note that if JavaScript/ECMAScript's parseInt() is being used in any code currently it won't cause issues as it works fine even if it's already numeric.

I don't feel strongly either.  I'm good with @KamasamaK
https://github.com/kamasamak 's recommendation.
On Fri, Jun 30, 2017 at 3:05 AM, KamasamaK<EMAIL_ADDRESS>wrote:

I think the goal should be to use the proper data types. Breaking
compatibility is a potential concern, but it should be easy enough to work
around if it's an issue. The only ones I've really looked into are Atom's
linter-cflint plugin, which uses the XML output, and SublimeLinter's which
uses the text output. The other projects I've seen just appear to be using
the Java directly.
Actually, the reason this came up is that I was seeing if I could change
Atom's linter-cflint to use JSON instead of XML output. I was successful,
but I had to use parseInt() on the values which shouldn't be necessary.
Note that if JavaScript/ECMAScript's parseInt() is being used in any code
currently it won't cause issues as it works fine even if it's already
numeric.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cflint/CFLint/issues/318#issuecomment-312192165, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFtZux_2Vrt_wwFwigcs_u0mEn7EsvaJks5sJJ4ngaJpZM4OJqqQ
.

@KamasamaK @ryaneberly I'll implement the String->Int changes in dev later, re @KamasamaK's second question (locations array). I honestly don't know at this stage - I looked into the whole JSON output mechanism for the first time yesterday :)

Schema documentation moved into #322, @KamasamaK .

Done, schemas and use of locations element is being dealt with in #322

We just need to change
jg.writeStringField()  to jg.writeNumberField() in order to make the
numbers come out.
Changing the locations not be an array may break downstream tooling.
There is an opportunity to more concisely represent issues that repeat
within in a file by just repeating the line and column numbers in the
locations array -- is that useful or confusing?
On Fri, Jun 30, 2017 at 9:08 PM, Kai Koenig<EMAIL_ADDRESS>wrote:

@KamasamaK https://github.com/kamasamak @ryaneberly
https://github.com/ryaneberly I'll implement the String->Int changes in
dev later, re @KamasamaK https://github.com/kamasamak's second question
(locations array). I honestly don't know at this stage - I looked into the
whole JSON output mechanism for the first time yesterday :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cflint/CFLint/issues/318#issuecomment-312401418, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFtZu4qdcpdrMeXTdoYOmtoc1d6lIDglks5sJZvxgaJpZM4OJqqQ
.

For any tool using the JSON output, I can't think of a way it wouldn't break removing the array.
I understand what you're proposing, which would be for both JSON and XML, but I have a feeling that could also break tooling due to assumptions people made about the output, which is precisely why I felt documenting output schemas was necessary. For example, Atom's linter-cflint package assumes a single location for each issue.

Good point.  Something to visit at 2.0?

"jg.writeStringField()  to jg.writeNumberField() in order to make the
numbers come out." --- that's already been done in fe73779a35fc0b7c9490bd2f1defb9635f30b766

"There is an opportunity to more concisely represent issues that repeat
within in a file by just repeating the line and column numbers in the
locations array -- is that useful or confusing?....    In fact after looking at it a bit more, it should already be doing that."
I don't think it is dong that at this stage. I can't see it in my daily usage at least.
But you're making a very good point @ryaneberly --- we could have a grouping by file mechanism that lists issues differently and with multiple location elements per issue.
Nothing to look deeper at now, I'd agree - I'd leave locations unchanged for 1.x and we'll have a rethink for 2.0.


python3Packages.tokenizers: 0.12.1 -> 0.13.3

Description of changes
Update to the latest version: https://github.com/huggingface/tokenizers/releases/tag/python-v0.13.3
The Cargo.lock file is no longer contained in the release tarball: https://github.com/huggingface/tokenizers/pull/1131#issuecomment-1510007065, so I manually generated it for this update.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 227126 run on x86_64-linux 1

6 packages failed to build:

python310Packages.dalle-mini
python310Packages.dalle-mini.dist
python310Packages.shap
python310Packages.shap.dist
python310Packages.vqgan-jax
python310Packages.vqgan-jax.dist

18 packages built:

khoj
khoj.dist
openai-whisper (python310Packages.openai-whisper)
openai-whisper.dist (python310Packages.openai-whisper.dist)
python310Packages.sentence-transformers
python310Packages.sentence-transformers.dist
python310Packages.spacy-transformers
python310Packages.spacy-transformers.dist
python310Packages.stanza
python310Packages.stanza.dist
python310Packages.tokenizers
python310Packages.tokenizers.dist
python310Packages.transformers
python310Packages.transformers.dist
python311Packages.tokenizers
python311Packages.tokenizers.dist
python311Packages.transformers
python311Packages.transformers.dist

Result of nixpkgs-review pr 227126 run on x86_64-linux 1

6 packages failed to build:

python310Packages.dalle-mini
python310Packages.dalle-mini.dist
python310Packages.shap
python310Packages.shap.dist
python310Packages.vqgan-jax
python310Packages.vqgan-jax.dist

18 packages built:

khoj
khoj.dist
openai-whisper (python310Packages.openai-whisper)
openai-whisper.dist (python310Packages.openai-whisper.dist)
python310Packages.sentence-transformers
python310Packages.sentence-transformers.dist
python310Packages.spacy-transformers
python310Packages.spacy-transformers.dist
python310Packages.stanza
python310Packages.stanza.dist
python310Packages.tokenizers
python310Packages.tokenizers.dist
python310Packages.transformers
python310Packages.transformers.dist
python311Packages.tokenizers
python311Packages.tokenizers.dist
python311Packages.transformers
python311Packages.transformers.dist

It looks like dalle-mini and shap were already failing before this update - I'm not sure about vqgan-jax though, because it has an unfree license.

https://hydra.nixos.org/job/nixpkgs/trunk/python310Packages.dalle-mini.x86_64-linux
https://hydra.nixos.org/job/nixpkgs/trunk/python310Packages.shap.x86_64-linux


[Feature request] Filter feeds with keywords or tags

A set of persistent filtering rules per feed.
Some feeds have tags in the title like "[Mac] title" or "[iOS] title". It would be great to filter out items, and mark the rest as read.

Duplicate of #1864


Allow investigation to schedule modules regardless PUBLISH_

Due to conditions in main_common PUBLISH_* variable cant be empty. Set to None to allow the scheduling.
https://progress.opensuse.org/issues/156394

According to https://progress.opensuse.org/issues/156394#note-14 Jobs would still fail in the same way in before. And how does os-autoinst and openQA handle the jobs trying to publish a non-existant asset "none"?

I am looking at the second part now. Which maybe it would be good idea to do first

According to https://progress.opensuse.org/issues/156394#note-14 Jobs would still fail in the same way in before.

That's actually a good thing. With that I meant that it ran the whole schedule, so the investigation job could reproduce the original failure.
But I guess we should set this to not-ready until changes are done on the openQA side.

@b10n1k can you reply to https://github.com/os-autoinst/scripts/pull/299#issuecomment-1987993165 please?

According to https://progress.opensuse.org/issues/156394#note-14 Jobs would still fail in the same way in before.

That's actually a good thing. With that I meant that it ran the whole schedule, so the investigation job could reproduce the original failure.
But I guess we should set this to not-ready until changes are done on the openQA side.

Sorry missing to reply earlier. However we were looking on this with @kalikiana . I remember running a job (with an older commit of os-autoinst https://github.com/os-autoinst/os-autoinst/pull/2470) and observe to observe the behavior. the job finishes without uploading hdd and without any further problem. If there is something else to be done in openQA i havent seen it. openQA seems to handle the rest properly without any change.


[Bug]: Show Less / 2 More Issues on ODHDocCards in the Resource Section

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
There is only one label -- it's got a hardcoded 3 items in it.

Expected Behavior
For it to perform normally based on the number of items.
Steps To Reproduce

Install the ODH Dashboard & the accompanying resources from ODH Manifests & ODH Dashboard manifests folder
Navigate to the Resources section and view card mode
Find the Jupyter docs one (should be generated from the OdhApp and not be an actual OdhDocument object)

Workaround (if any)
No response
What browsers are you seeing the problem on?
No response
Open Data Hub Version
Dashboard: v2.6.0

Anything else
No response

This is an issue I noticed and submitted a fix in PF https://github.com/patternfly/patternfly-react/pull/8505. It's already merged and bumping the PF version could simply fix this issue I think.

This is an issue I noticed and submitted a fix in PF patternfly/patternfly-react#8505. It's already merged and bumping the PF version could simply fix this issue I think.

@DaoDaoNoCode can you verify this is fixed in your PF bump PR?


Revise ncclimo  default invocation

zppy chooses to invoke ncclimo in MPI mode with requesting 4 nodes for climo jobs. Based on email exchanges with @czender: For all low resolution simulations, use the default background mode instead, will potentially reduce queue time and save resources. MPI mode can be useful for HR simulations, and those can either be assigned multiple nodes in MPI mode or accomplished in background mode by ratcheting down the number of concurrent processes (to relieve RAM pressure) with the --job_nbr option.

Do you encounter problems with the current zppy climo default?

I experience long time for the queued jobs to run on Cori. At today's LR+RRM finalization meeting, @xuezhengllnl also mentioned long queue time for post processing jobs. I thought revising the ncclimo default invocation for climo will alleviate this problem.

Did you use the debug queue? climos normally don't take long to compute and can fit in the cori debug queue.
You can try, but I don't see an easy, optimal way as it depends on the machine queue configs and more importantly the realtime machine usage by others.

@chengzhuzhang nd @czender : I'll gladly defer to you two regarding the best default settings for post-processing with ncclimo.
Here is an example of a configuration file for some v1-HR output on chrysalis. Note that MPAS-Analysis will fail because some mpas-o output files are corrupted, so you may want to turn the task off.
[default]
input = /lcrc/group/e3sm/ac.ndkeen/scratch/chrys/E3SM_simulations/production-unc06
input_subdir = run
output = /lcrc/group/e3sm/ac.golaz/E3SM_analysis/20210112.A_WCYCL1950S_CMIP6_HR.ne120_oRRS18v3_ICG.unc06
case = 20210112.A_WCYCL1950S_CMIP6_HR.ne120_oRRS18v3_ICG.unc06
www = /lcrc/group/e3sm/public_html/diagnostic_output/ac.golaz/E3SM/v1-HR
partition = compute
e3sm_unified = latest

[climo]
active = True
years = "137-155",

  [[ atm_monthly_720x1440_nco ]]
  input_files = "cam.h0"
  mapping_file = /home/ac.zender/data/maps/map_ne120np4_to_cmip6_720x1440_nco.20190601.nc

[ts]
active = True
years = "137:155:1",

  [[ atm_monthly_720x1440_nco ]]
  input_files = "cam.h0"
  mapping_file = /home/ac.zender/data/maps/map_ne120np4_to_cmip6_720x1440_nco.20190601.nc
  vars = "FSNTOA,FLUT,FSNT,FLNT,FSNS,FLNS,SHFLX,QFLX,TAUX,TAUY,PRECC,PRECL,PRECSC,PRECSL,TS,TREFHT,CLDTOT,CLDHGH,CLDMED,CLDLOW"

  [[ atm_monthly_glb ]]
  input_files = "cam.h0"
  mapping_file = "glb"
  vars = "FSNTOA,FLUT,FSNT,FLNT,FSNS,FLNS,SHFLX,QFLX,TAUX,TAUY,PRECC,PRECL,PRECSC,PRECSL,TS,TREFHT,CLDTOT,CLDHGH,CLDMED,CLDLOW"

[glb]
active = False

[e3sm_diags]
active = True
years = "137-155",

  [[ atm_monthly_720x1440_nco ]]
  short_name = 'unc06'
  grid = '720x1440_nco'
  reference_data_path = '/lcrc/soft/climate/e3sm_diags_data/obs_for_e3sm_diags/climatology'
  output_format_subplot = "pdf",

[e3sm_diags_vs_model]
active = False

[amwg]
active = False

[mpas_analysis]
active = True
walltime = "24:00:00"
parallelTaskCount = 6
subdir_ocean = run
subdir_ice = run
ts_years = "137-155",
enso_years = "137-155",
climo_years ="137-155",
mesh = "oRRS18to6v3"


Is it possible to add custom rules?

I want to add some custom rules like
{item=12345}(foo bar)

which should translate to something like
foo bar

+1

Looking at the code it doesn't seem like it the tokenizer and parser are hard coded if statements.
I did it by first parsing what I needed first using regexs then passing the rest to marked.
It seems like being able to  add custom rules would slow it down and marked seems written for speed.
It would also be a nice feature.

Came here looking for the same. In a similar fashion I'm hoping to convert this in markdown:
I> Here is an info box

To:
Here is an info box

+1

Closing to consolidate issues.


Explore how other centers manager their open source projects

➤ Basil Mohamed Gohar commented:
We should look and see how TACC, Trilabs, NCSA, SDSC manager their open source projects and their associated websites/pages.


Fixed function/audio/anim tracks in blend tree animation filter

The change makes function, audio and animation tracks usable when filtering animations in some AnimationNodeBlendTreeEditor nodes.
Helps with #32920 but there might be more issues to solve there.
Example animation:

Animation Filter:

Before
After

Thanks!


Replays will attempt to send infinitely if sending replay fails

See https://sentry.io/organizations/sentry/issues/3516366698/?project=11276

Closed by https://github.com/getsentry/sentry-replay/pull/201


entirely mappable migration region must not allow struct vfio_device_migration_info to be mmaped

The user requests migration support for the device and in reponse we initialize the migration region. The migration region we create is sizeof(struct vfio_device_migration_info) bytes larger than the user requested in order to fit at the beginning of it the migration registers struct vfio_device_migration_info. If the user specifies the entire migration region to be mappable (by providing a file descriptor but setting mmap_areas to NULL), we need to internally make the migration region sparsely memory mappable, excluding the migration registers at the beginning.

Check init_migration.

Check init_migration.

The user requests migration support for the device and in reponse we initialize the migration region. The migration region we create is sizeof(struct vfio_device_migration_info) bytes larger than the user requested in order to fit at the beginning of it the migration registers struct vfio_device_migration_info. If the user specifies the entire migration region to be mappable (by providing a file descriptor but setting mmap_areas to NULL), we need to internally make the migration region sparsely memory mappable, excluding the migration registers at the beginning.

The user requests migration support for the device and in reponse we initialize the migration region. The migration region we create is sizeof(struct vfio_device_migration_info) bytes larger than the user requested in order to fit at the beginning of it the migration registers struct vfio_device_migration_info. If the user specifies the entire migration region to be mappable (by providing a file descriptor but setting mmap_areas to NULL), we need to internally make the migration region sparsely memory mappable, excluding the migration registers at the beginning.

The original problem in this issue is easily fixed. However, I discovered the following problem when the migration region is memory mappable (either wholly or in part via sparse mmaps): the user supplies a file descriptor with the sparse mmap addresses based on the beginning of the file. However, libvfio-user will create a PCI region which must be sizeof(struct vfio_device_migration_info) larger than the migration region the user specifies in order to contain the migration registers. The migration registers must be placed at the beginning of the migration region and cannot be memory mapped. The problem is that we cannot simply adjust the base addresses of the sparse mmaps by adding sizeof struct vfio_device_migration_info because that would require changing the size of the file and shifting the first few bytes. If we leave the sparse mmaps to their original values then they'll be wrong. This whole problem stems from our decision to hide the fact that migration is implemented as a PCI region. One way to solve this problem is to have libvfio-user create the file and return the file descriptor to the user, or have the user supply the file descriptor but leave to the library to truncate it accordingly and return the usable area. Another way to solve this is to tell the user to reserve a few extra bytes at the beginning of the file (we can implement a function to return sizeof struct vfio_device_migration_info. Or we can simply expose the fact that migration is implemented as a region. @jlevon @swapnili thoughts?

The original problem in this issue is easily fixed. However, I discovered the following problem when the migration region is memory mappable (either wholly or in part via sparse mmaps): the user supplies a file descriptor with the sparse mmap addresses based on the beginning of the file. However, libvfio-user will create a PCI region which must be sizeof(struct vfio_device_migration_info) larger than the migration region the user specifies in order to contain the migration registers. The migration registers must be placed at the beginning of the migration region and cannot be memory mapped. The problem is that we cannot simply adjust the base addresses of the sparse mmaps by adding sizeof struct vfio_device_migration_info because that would require changing the size of the file and shifting the first few bytes. If we leave the sparse mmaps to their original values then they'll be wrong. This whole problem stems from our decision to hide the fact that migration is implemented as a PCI region. One way to solve this problem is to have libvfio-user create the file and return the file descriptor to the user, or have the user supply the file descriptor but leave to the library to truncate it accordingly and return the usable area. Another way to solve this is to tell the user to reserve a few extra bytes at the beginning of the file (we can implement a function to return sizeof struct vfio_device_migration_info. Or we can simply expose the fact that migration is implemented as a region. @jlevon @swapnili thoughts?

I think a reasonable comprosie to the above problem is to request that the file should contain some initial empty space of at least sizeof struct vfio_device_migration_info bytes and this area must not be accessed.

Another possibly better approach would be to have libvfio-user create the file and mmap it, and provide a pointer to the part of the file excluding struct vfio_device_migration_info at the beginning. The user doesn't have to know that this memory is backed by a file or that there's stuff before that address.

I think better approach is libvfio-user creates and setups the file, user do not have to know about this fact and can just use the memory returned back by libvfio-user.

After discussing the issue with @jlevon and @swapnili we decide to expose the fact that live migration is done via a region. We'll document that the user needs to reserve at least sizeof(struct vfio_device_migration_info) bytes at the beginning of the migration region. We'll keep the callbacks but make them optional: if the user doesn't procide callbacks then the standard region read/write callbacks will be called and the user must handle accesses to the migration region registers. The only remaining question is whether we should fix the migration region index right after the PCI ones or make it freely selectable, as VFIO allows it. We should reach out to the VFIO maintainers for clarification.


getSharesForAccounts returns nothing

I've reset the database with a clean install and have run into a problem with payouts not completing. Curious if anyone is familiar with how $share->getSharesForAccounts works as this seems to be where the problem is.
https://github.com/MPOS/php-mpos/blob/b7b45eb580dfd7f683540b519a66e14d3fe8321d/include/classes/share.class.php#L96

2017-08-16 20:30:49 - DEBUG --> Starting PPLNS payout process
2017-08-16 20:30:49 - INFO --> |         PPLNS Target |        Actual Shares |   Height |     Amount |          Finder |
2017-08-16 20:30:49 - INFO --> |              1007616 |              1007616 |  1056333 |      10.25 |        ZenMiner |
2017-08-16 20:30:49 - DEBUG -->   Matching or exceeding PPLNS target of 1007616 with 1007616
2017-08-16 20:30:49 - DEBUG --> 1
2017-08-16 20:30:49 - DEBUG -->
2017-08-16 20:30:49 - CRIT -->   No shares found for this block, aborted! Block Height : 1056333, Block ID: 1

Seems that its an issue with MySQL V5.7+
https://dev.mysql.com/doc/refman/5.7/en/group-by-handling.html
When I run the query manually I'm getting:
Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'mpos.a.id' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by

See FAQ and searching tickets for my detailed explanation.


Setting test#strategy has no effect

I've tried
:let g:test#strategy = "neovim_vscode"
:let g:test#strategy = "foo"
:let test#strategy = "neovim_vscode"
:let test#strategy = "foo"

and nothing ever changes. I've read out the value using let [g:]test#strategy after test running to make sure it's not overwritten.

What command are you using to execute your commands? I have found that some, especially TestLatest, reuse the last settings.
Looking at source: https://github.com/vim-test/vim-test/blob/8872ec0f788af934386b2aef0cd28a5c2b923146/autoload/test.vim#L70-L77 there are some flows where the setting is not read. You can try print-debugging that file by adding some echom strategy and sourcing it or restarting vim to update plugin source code.

I don't remember exactly, but the problem had a sane explanation in the end (plugin manager or similar)


travis: Use toolchain name directly.

A small change to the naming in eos-s3/README.rst names means we can
simplify the .travis.yml to use the TOOLCHAIN value directly rather than
needing multiple if statements.
Also add comments to explain what is happening in each section.
Signed-off-by: Tim 'mithro' Ansell<EMAIL_ADDRESS>

@kamilrakoczy - PTAL. This pull request simplifies the .travis.yml a bit and makes reduces the need for if statements.


DO NOT DISTURB Mode is not restarted after alarm code.

2b tested. Alarm fragment has now implementation for this.

Now it is restarted. Working implementation.


why use aria-describedby in slides?

I'm wondering about the appropriateness or need to use aria-describedby in each slide to refer to the navigation dots. The dots don't provide any sort of descriptive information about the slide.
I'm not which which aria attribute would be appropriate to indicate the relationship between the dots and the slide (if this is the goal). Possibly aria-controls? But aria-describedby doesn't seem right.
Moreover, this attribute is still generated even when the dots are not present , which is the default for Slick. So, unless I'm missing something, it shouldn't even appear by default.

@plweil i agree; i had to fake this to pass validation by visually hiding the dots even though i really wanted them gone together. if the dots don't exist, then the describedby ID doesn't exist, which is invalid.
additionally, i noticed this 'hack' didn't work on a "center" slick slider.
i'm guessing the cloned slides iterate their referred by ID - which it shouldn't, since they are clones.

I am also dealing with the validation errors caused by this.

I came up against this issue as well. In my slideshow each slide has a div corresponding to the title of the slide. I set that div to the "aria-describedby" attribute generated by slick to get around the ADA compliance.
$('.slide-title').each(function () {
    var $slide = $(this).parent();
    if ($slide.attr('aria-describedby') != undefined) { // ignore extra/cloned slides
        $(this).attr('id', $slide.attr('aria-describedby'));
    }
});

@wemaycode that's a good alternative / fallback!

I'm also having this issue, would be nice to have a setting for this or remove aria-describedby when dots are set to false.

Also noticed this going through the markup generated. aria-describedby really shouldn't be set if the element it points to doesn't exist.

And even if the dots exist, why use aria-describedby? The dots don't provide a description. If there is something we want to communicate to the user regarding the relationship between the slide and the dot, let's use the aria attribute that accomplishes what we want.

Good question! I'm not an expert, and I don't have strong feelings, but my guess is that the describedby is less in reference to the dot representation, and more in reference to the markup, in which there's a number corresponding to the slide it navs to. The number is hidden with the theme styles and replaced with that dot. Moreover for implementations that use custom paging, there's often even richer relationship information conveyed.

Just wondering why this issue was closed?
I agree with @surfbird0713 and @benvoynick, if dots are set to false then aria-describedby should either be pointing to a different, perhaps hidden, descriptive element, or just not included at all.
It would be nice to have this issue resolved at some point so we won't have to continue resorting to workarounds.

Also wondering why this was closed?  Accessibility is important, especially since we have a legal obligation to make these sites work for all.  Slick slider does not pass validation if no dots are used.

I'm no a11y expert, so I'm certainly open to suggestion, and more importantly PRs. hit me.

I think @ibarsi had a great suggestion of creating an element only visible to screen-readers to describe the slides.  Or just remove the broken aria-reference?

I don't mind forking and putting together a PR with a potential solution (likely hidden fields) once I'm back from vacation next week, unless someone beats me to it!

I can't help thinking that in this case, the aria-describedby attribute isn't the way forward. I've been tasked with making a site that uses lots of carousels (slick is the best in every other way) fully accessible and this is really holding me up. Some of the carousels have dots, some don't as there are specific settings for specific uses and sizes of carousel.
From what I can see, the only thing this attribute refers to are id's on dots and even when you do have dots enabled, there'll be plenty of these attributes with no id attached to them as they'll be intermittently referring to every third/fourth/fifth etc slide within the range.
@wemaycode's solution is a great idea and helps though can cause multiple id's unfortunately. I'll keep investigating this issue and hope to find a robust solution.

@webegguk If you check the pull request I've created, I've modified the aria-describedby generation logic for the case in which there are more slides than dots. I've ensured that each slide is referencing the dot that makes it visible. However, I'm sure there are many slick configurations that I haven't tested, as I am pretty new to this repo.
Honestly, I really do believe that these dots are not providing any real added description to the slides... To avoid the need for workarounds like what @wemaycode has done, maybe we should remove the generation of aria-describedby tags all together and leave it up to the user to add meaningful tags themselves? That will likely bring more value to those that are trying to make slick accessible.

I tend to agree. Removal of the aria-describedby attributes entirely, or optionally including them seems like a good solution as the only thing they refer to as you say, is the dots, which don't seem to provide any descriptive content hence negating the need to add accessibility.

+1 This ever going to be addressed?

@plweil posted a comment above that appears to be in support of making the change that would fix this issue, and also was the creator of the issue, but he closed the issue himself on the same day, for some reason. I do not understand why.

Actually I don't remember closing it, and have no idea why I might have closed it.

+1 to removing aria-describedby

+1 to removing aria-describedby

+1 to removing aria-describedby

+1 to removing aria-describedby

+1  removing aria-describedby

+1 removing aria-describedby

+1 removing aria-describedby

I had to comment out aria-describedby to pass a lighthouse audit :/


Fix empty traversal for mixed empty and non-empty tiles

Fixes #9356
This PR fixes a bug in empty tile traversal code where sometimes a parent tile wouldn't refine if one of its children is a long chain of empty tiles followed by a tile with content. The old logic would assume the parent shouldn't refine because there was a renderable descendant, and refining would create a hole. However, some cases (like in #9356 and #11564) actually require the hole to render properly.
I went through and redid the logic of that function, and was able to simplify and document it so it's easier to follow.
The biggest difference is that now only tiles that would be rendered for the current camera view are examined, before it would traverse deeper in the tree if there are a lot of empty tiles.
@jjhembd could you review?
CC @lilleyse

Thanks for the pull request @ptrgags!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

I'm going through the Sandcastles in the gallery for further testing. I'm noticing some issues:

for Google Photorealistic 3D Tiles, when I move the camera, the view gets blurry when waiting for tiles... so something's not quite right
For 3D Tiles Next Photogrammetry Classification, it takes quite a bit longer to load and hits the memory limit, that doesn't happen on main

I know the approach in the PR as it stands now is not the correct approach, I get tiles popping in and out with Google Photorealistic 3D Tiles.
It might be worth re-trying @lilleyse's original idea of just returning true. I think there might be some subtleties there indicated by unit tests when I tried it the first time.
For now, I'm closing this PR.


[Hono] Generated handler cannot be implemeted (Argument of type 'string' is not assignable to parameter of type 'never')

With latest Orval (6.26.0) the generated Hono handers give an error:
Whem implementing https://github.com/anymaniax/orval/blob/master/samples/hono/src/handlers/showPetById.ts
like:
import { createFactory } from 'hono/factory';
import { zValidator } from '@hono/zod-validator';
import { ShowPetByIdContext } from '../petstore.context';
import { showPetByIdParams } from '../petstore.zod';

const factory = createFactory();

export const showPetByIdHandlers = factory.createHandlers(
  zValidator('param', showPetByIdParams),
  (c: ShowPetByIdContext) => {

    const petId = c.req.param('petId');

    const pet = {
      // TODO
    }

    return Response.json(pet);

  },
);

the code const petId = c.req.param('petId'); gives the error:
Argument of type 'string' is not assignable to parameter of type 'never'.ts(2345)

From the Hono docs this that should be the way to retrive the path params:

I also tried the alternative to get all path paramers at once:

However, the showPetByIdParams contains the petId.

On a related note, is there a way to type-safe the response as well?

I am on it and for the response. A zod schema is already generated but not automatically checked. I am not sure how to do it properly if you have an idea or example I am open to add it

something like this would do the job I will add it as an option and we can iterate on it
const responseValidator = factory.createMiddleware(async (c, next) => {
  await next();

  const data = c.res.json();

  const result = await createPetsResponse.safeParseAsync(data);

  if (!result.success) {
    c.res = new Response(JSON.stringify(result), {
      status: 400,
      headers: {
        'Content-Type': 'application/json',
      },
    });
  }

  c.res = new Response(c.res.body, c.res);
});

I ended with something like this
// based on https://github.com/honojs/middleware/blob/main/packages/zod-validator/src/index.ts
import type { z, ZodSchema, ZodError } from 'zod';
import {
  Context,
  Env,
  Input,
  MiddlewareHandler,
  TypedResponse,
  ValidationTargets,
} from 'hono';
type HasUndefined<T> = undefined extends T ? true : false;

type Hook<T, E extends Env, P extends string, O = {}> = (
  result:
    | { success: true; data: T }
    | { success: false; error: ZodError; data: T },
  c: Context<E, P>,
) =>
  | Response
  | Promise<Response>
  | void
  | Promise<Response | void>
  | TypedResponse<O>;

export const zResponseValidtor =
  <
    T extends ZodSchema,
    Target extends keyof ValidationTargets,
    E extends Env,
    P extends string,
    In = z.input<T>,
    Out = z.output<T>,
    I extends Input = {
      in: HasUndefined<In> extends true
        ? {
            [K in Target]?: K extends 'json'
              ? In
              : HasUndefined<keyof ValidationTargets[K]> extends true
              ? { [K2 in keyof In]?: ValidationTargets[K][K2] }
              : { [K2 in keyof In]: ValidationTargets[K][K2] };
          }
        : {
            [K in Target]: K extends 'json'
              ? In
              : HasUndefined<keyof ValidationTargets[K]> extends true
              ? { [K2 in keyof In]?: ValidationTargets[K][K2] }
              : { [K2 in keyof In]: ValidationTargets[K][K2] };
          };
      out: { [K in Target]: Out };
    },
    V extends I = I,
  >(
    schema: T,
    hook?: Hook<z.infer<T>, E, P>,
  ): MiddlewareHandler<E, P, V> =>
  async (c, next) => {
    await next();

    const clonedResponse = c.res.clone();

    let value: unknown;
    try {
      value = await clonedResponse.json();
    } catch {
      const message = 'Malformed JSON in response';
      c.res = new Response(message, { status: 400 });
    }

    const result = await schema.safeParseAsync(value);

    if (hook) {
      const hookResult = hook({ data: value, ...result }, c);
      if (hookResult) {
        if (hookResult instanceof Response || hookResult instanceof Promise) {
          const hookResponse = await hookResult;

          if (hookResponse instanceof Response) {
            c.res = new Response(hookResponse.body, hookResponse);
          }
        }
        if (
          'response' in hookResult &&
          hookResult.response instanceof Response
        ) {
          c.res = new Response(hookResult.response.body, hookResult.response);
        }
      }
    }

    if (!result.success) {
      c.res = new Response(JSON.stringify(result), {
        status: 400,
        headers: {
          'Content-Type': 'application/json',
        },
      });
    }
  };

Thx @anymaniax , looking forward to it.
For the response typing, to be honest, I had no idea how to do it; so anything would be good ;-)
My main problem with responses in general is that to much is send to the client; e.g. fields with data that is not meant to be exposed.

Both will be in the next release

Sure use Discord?


Uncaught TypeError: undefined is not a function

[Enter steps to reproduce below:]

...
...

Atom Version: 0.166.0
System: Mac OS X 10.10.2
Thrown From: minimap-git-diff package, v3.1.0
Stack Trace
Uncaught TypeError: undefined is not a function
At /Users/jux/.atom/packages/minimap-git-diff/lib/minimap-git-diff-binding.coffee:10

TypeError: undefined is not a function
  at new MinimapGitDiffBinding (/Users/jux/.atom/packages/minimap-git-diff/lib/minimap-git-diff-binding.coffee:10:24)
  at /Users/jux/.atom/packages/minimap-git-diff/lib/minimap-git-diff.coffee:64:7
  at createdCallback (/Users/jux/.atom/packages/minimap/lib/mixins/view-management.coffee:53:40)
  at Emitter.module.exports.Emitter.emit (/Users/jux/.atom/packages/minimap/node_modules/event-kit/lib/emitter.js:71:11)
  at Minimap.module.exports.ViewManagement.onEditorAdded (/Users/jux/.atom/packages/minimap/lib/mixins/view-management.coffee:112:12)
  at /Users/jux/.atom/packages/minimap/lib/mixins/view-management.coffee:87:19

Commands
     -0:01.3 project-manager:toggle (ul.list-inline.tab-bar.inset-panel)
     -0:00.0 core:confirm (atom-text-editor.editor.mini)

Config
{
  "core": {
    "excludeVcsIgnoredPaths": false,
    "themes": [
      "NealRame-ui",
      "monokai-flat"
    ],
    "projectHome": "/Users/jux/Documents/Development"
  }
}

Installed Packages
# User
NealRame-ui, v0.5.0
color-picker, v1.2.6
dash, v1.0.0
file-icons, v1.4.4
git-diff, v0.47.0
language-cmake, v0.1.1
language-jade, v0.3.0
language-powershell, v0.6.6
minimap, v3.5.0
minimap-git-diff, v3.1.0
minimap-selection, v3.1.0
monokai-flat, v1.0.1
project-manager, v1.14.1
react, v0.7.8

# Dev
No dev packages

/cc @atom/core

Thanks for the report, I'll take a look asap.


Log failed output decoding

See #1841, if we print the raw data this gives us a shot at reproducing the error.

@lutter I've added logging to the input decoding since we've also seen that fail, and also added the function ABI to the log. This should be a good start.


Error using sample smart quote function

Powershell 5.1 on Win10 1709, using PSReadline 1.2.
I copied the sample PSReadline profile from here verbatim into an empty profile (Documents/WindowsPowerShell/profile.ps1). Everything seems to work except the smart quote. When I type a quote (single or double) when no text is selected, e.g. either on an empty line or at the end of some text, I get this:
An exception occurred in custom key handler, see $error for more information: Unable to find type [StringToken].
$error contains:
Unable to find type [StringToken].
At C:\Users\vrice\Documents\WindowsPowerShell\profile.ps1:177 char:20

if ($token -is [StringToken] -and $token.Kind -ne [TokenKind]::Ge ...

               ~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (StringToken:TypeName) [], RuntimeException
FullyQualifiedErrorId : TypeNotFound

I searched around the web trying to see if I could find something obvious, but I'm not sufficiently advanced in PowerShell to interpret what I found.
I don't get this when typing a brace {, I get the expected {} with the cursor between. But, that function doesn't refer to [StringToken].
I deleted the profile and cut-and-pasted it from here again, same result. (The site says the sample file is included with 1.2, but I couldn't find it anywhere, i.e. in or out of the PSReadline module subdirectory).
What am I missing?

Can you paste the code from your profile? Or copy again from https://github.com/lzybkr/PSReadLine/blob/9d592b875ebea83d6385b9cc6b6899584b08277a/PSReadLine/SamplePSReadlineProfile.ps1#L122 (though this version has some quirks too - but it's just a sample :)
There was a bug like this in that example long ago, but it was fixed.

I pasted the entire function here and was about to post it, but thought I'd try one more time. I cut-and-pasted the function from the sample again, but got the same result.
I was pretty convinced it was my error, so I kept looking, and doh! I somehow missed or deleted the two namespace lines at the very top! After putting those back, everything works fine.
My apologies for the noise! I suspected it was something obvious, I just couldn't figure out what it was.

I see. Maybe I should change the sample then so it doesn't require the usings.
At any rate, sounds like this is resolved.

Definitely resolved, but it was my fault, not yours. I wouldn't worry about the usings, they're fine. I just missed them.

On Nov 1, 2017, at 6:43 PM, Jason Shirk<EMAIL_ADDRESS>wrote:
I see. Maybe I should change the sample then so it doesn't require the usings.
At any rate, sounds like this is resolved.


Faster HMR  checks

Is your feature request related to a problem? Please describe.
To detect if a file is accepting HMR with import.meta.hot.accept() we are using babel's parser, this will slow down the server, it will even more noticeable for projects that use the vite-react-plugin because it injects import.meta.hot.accept on every file
https://github.com/vitejs/vite/blob/125d43eb64869a4f31240d99a58401a5ebbf7add/src/node/server/serverPluginHmr.ts#L395
Describe the solution you'd like
We could remove the need for parsing and instead use a regex, but this could potentially fail in some rare cases
Describe alternatives you've considered
If parsing the import.meta.hot is really necessary we could start parsing only from the line that contains if (import.meta.accept) to the end of the file
Additional context

That's already the case. rewriteFileWithHMR is only called when source.includes('import.meta.hot').
See https://github.com/vitejs/vite/blob/master/src/node/server/serverPluginModuleRewrite.ts#L211

Yes i know, the problem is that vite-plugin-react adds the import.meta.hot to all the files with a react component
https://github.com/vitejs/vite-plugin-react/blob/9031b924498a3121b2356c645a0084b899218c5b/src/transform.ts#L54


Tick count callback is broken

Issue is with jQuery.minicolors. Changing issue title to reflect.

It's a C3 issue. If tick count is specified for a categorical axis, "undefined" is returned. It kind of worked in 0.3.0, though?

Logged at masayuki0812/c3#935.

Kicking into the tall grasses because it's a C3 issue resolved in its next release.

The tall grasses are where the wild pokemon are though

![http://i1.kym-cdn.com/photos/images/newsfeed/000/065/215/129012076232534752.jpg]


chocolatey-visualstudio.extension.1.10.2: Issue parsing some parameters.

The visual studio installer have a special arguments with space within their neme:
--path cache="C:\VS\cache" --path shared="C:\VS\shared"
When passing theses arguments to chocolatey the Parse-Parameters in Parse-Parameters.ps1 in the extension crash as key and values are splitted by their space between them:
Exception lors de l'appel de « Add » avec « 2 » argument(s) : « L'élément a déjà été ajouté. Clé du dictionnaire : 'path'  Clé ajoutée : 'path' »
I fixed it on my end this way, but it would be nice to get it fixed officially:
    If ($kvp.StartsWith("path ", "CurrentCultureIgnoreCase")) {
        $key = $kvp
        $value = ''
    }
    else {
        if ($delimiterIndex -lt $kvp.Length)
        {
            $value = $kvp.Substring($delimiterIndex + 1).Trim()
        }
        else
        {
            $value = ''
        }
    }

https://learn.microsoft.com/en-us/visualstudio/install/command-line-parameter-examples?view=vs-2022

Yes, those path arguments are troublesome; the package parameters parser was implemented long before Microsoft added them. The fix seems reasonable, I'll incorporate it (but no promises as to when).

Or maybe it will be simpler to just add "path" to the list of allowed multivalue parameters.

Another wrinkle: --path install=<path> is an alias for –-installPath, so it would need to be recognized as such.

Another wrinkle: --path install=<path> is an alias for –-installPath <path>, so it would need to be recognized as such.

Yeah, i hoped for an alias like --cachePath and --sharedPath, but they don't exist nor don't works at all.

Implemented in extension 1.11.0, currently in preview. Example:
cup -y chocolatey-visualstudio.extension --version 1.11.0-preview7
cup -y visualstudio2022buildtools --params "--locale en-US --path install=C:\VS 2022 BT --path shared=C:\VS 2022 Shared --path cache=C:\VS 2022 Cache --includeRecommended --includeOptional"

--path install=... is synonymous with --installPath ... (in fact, the extension internally converts the former to the latter).


az interactive error !!!! help

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az interactive
Errors:
cannot import name 'DEFAULTS_SECTION'
Traceback (most recent call last):
Temp\pip-install-mjd5h3hf\knack\knack\cli.py, ln 206, in invoke
azure\cli\core\commands\__init__.py, ln 603, in execute
azure\cli\core\commands\__init__.py, ln 661, in _run_jobs_serially
azure\cli\core\commands\__init__.py, ln 654, in _run_job
Local\Temp\pip-install-mjd5h3hf\six\six.py, ln 696, in reraise
azure\cli\core\commands\__init__.py, ln 631, in _run_job
azure\cli\core\commands\__init__.py, ln 306, in __call__
azure-cli-core\azure\cli\core\__init__.py, ln 487, in default_command_handler
azure\cli\command_modules\interactive\custom.py, ln 41, in start_shell
.azure\cliextensions\interactive\azext_interactive\__init__.py, ln 10, in start_shell
    from .azclishell.app import AzInteractiveShell
cliextensions\interactive\azext_interactive\azclishell\app.py, ln 35, in <module>
    from azure.cli.core._config import DEFAULTS_SECTION
ImportError: cannot import name 'DEFAULTS_SECTION'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az interactive

Expected Behavior
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6
Shell: cmd.exe

azure-cli 2.0.77

Extensions:
interactive 0.4.1

Additional Context

@jiasli Please help here

Same as https://github.com/Azure/azure-cli/issues/11042
interactive has been updated to 0.4.3. Please try
az extension update -n interactive

it is working fine now GOD bless :)


Questions about CUDA version

First of all, thank you for sharing your work.
I have several questions about reproducing your code and code from PLOP, which you have referred.
Q1. Have you also worked on CUDA 10.2?
Official code of MiB and PLOP works on CUDA 10.2. And I might have missed it, but there is no CUDA description on your github repo. Since the code also relies on 'apex' package, I guess it's also working on CUDA10.2. Have you worked on CUDA 10.2?
Q2. Have you tried to reproduce it on CUDA > 11.0
It may not be true but I figured out 'apex' package can be installed on CUDA version under 11.0.
As far as I know, for CUDA version higher than 11.0, torch.cuda.amp is used instead
So I have tried to update the code from PLOP without apex package using amp module from torch.cuda. But, currently, I am also facing some error with 'inplace-abn' package. So I was just wondering if you have tried on reproducing the code on higher version of CUDA.

Hi, thanks for reaching out.
For Q1, if you mean cudatoolkit, we tried that and it should work. But I think it's not a problem. Try it first and ask me again if you have any problems.
For Q2, since inplace-abn restrict the cuda version, we didn't try on cuda > 11.0. Nevertheless, it should be noticed that inplace-abn is a little bit different from the normal bn layer(In dealing with minimal terms). Based on this, our transformation has also changed a bit. If you replace inplace-abn with syncbn, remember to fix this part.
gamma = bn2d.weight.abs() + eps     beta = bn2d.bias

Hi, @jihwankwak Thanks for your interest.
We have updated the conda environment requirements in the repository. We run all experiments on Python3.6 + Torch1.3.1 + CUDA 10.1 and installed Apex from source code.

First of all, thank @schuy1er @zhangchbin for fast reply.
For @schuy1er,
Yes, the code works perfectly on your descriptions.
As you might have noticed in Q2, I have been wondering how to update this PLOP code framework in higher CUDA version.
Since I am having trouble doing this, this led me to ask the CUDA toolkit of your implementation.
I will try to replace inplace-abn with syncbn, as you suggested. This may help me out. Thank you again.
Thanks @zhangchbin for your fast update.

hi, @jihwankwak
We found that high version pytorch can not reach the supposed performance due to the bug caused by InplaceABNSync, which has been fixed in our latest commitment. You can refer to our latest news. Sorry for the inconvenience caused.

Thanks for letting me know.
I haven't check the code yet, but I will let you know if I bump into another questions.
By the way, have you tried to implement basic baselines such as MiB, PLOP in the higher version as well?
For me, those results are quite different than codes based on CUDA10.2.
-----Original Message-----
From: "Chang-Bin @.>
To: @.>;
Cc: @.>; @.>;
Sent: 2023-10-25 (수) 14:49:24 (GMT+09:00)
Subject: Re: [zhangchbin/RCIL] Questions about CUDA version (Issue #10)
hi, @jihwankwak
We found that high version pytorch can not reach the supposed performance due to the bug caused by InplaceABNSync, which has been fixed in our latest commitment. You can refer to our latest news. Sorry for the inconvenience caused.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


[Security] Potential Secret Leak

It has been noticed that while using fossa-contrib/fossa-action@v1 your fossa-api-key 5ee8bf422db1471e0bcf2bcb289185de is present in plaintext. Please ensure that secrets are encrypted or not passed as plain text in github workflows.

We can’t do that, fossa needs to scan PRs made by outside contributors.


fix: skeleton border

close https://github.com/dream-num/univer/issues/2509
close https://github.com/dream-num/univer/issues/3490

Pull Request Checklist

[ ] Related tickets or issues have been linked in the PR description (or missing issue).
[ ] Naming convention is followed (do please check it especially when you created new plugins, commands and resources).
[ ] Unit tests have been added for the changes (if applicable).
[ ] Breaking changes have been documented (or no breaking changes introduced in this PR).

2024_12_11 11_19_03 video.webm

prev issue
The border data does not match the drawing results.


Issue1 Fix

Fixed an issue that install font feature is not working for SEA server players.
Fix includes:

Detect if the user is selecting SEA server languages as source language.
If the user is from SEA server, try to fetch online fonts and install.
If no online font is available, make sure the user is choosing OTF font file, and install it as th_pearl.otf

Merge by owner.
CR is skipped.


Adding exact match for Numbers

It's now possible to do exact match queries on numbers. Scoring on it is still missing though.

I messed up trying to merge this. Rebase?

@Damienkatz My fault, you had no chance doing a rebase easily, it was a mess.


Revert "Create 6-InterfaceListItem.yaml and reference interfaces in 2-ComponentListItem.yaml"

Reverting ODU-CGA-CubeSat/dof-cubesat#2 as Type should have been a dictionary as opposed to a list in line 61 https://github.com/ODU-CGA-CubeSat/dof-cubesat/blob/4cbcc2047b672037edb01d55d017f9938b041063/architecture/3-DataStructures/2-ComponentListItem.yaml#L61

closing, as separate PR should be opened to address mistype


⚠ Bofrost.be has degraded performance

In a433957, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 958 ms

Resolved: Bofrost.be performance has improved in 93b7468 after 6 minutes.


Add concepts page on temporary credentials lifetime

Part of: https://github.com/stackabletech/issues/issues/586
Alternative take on https://github.com/stackabletech/documentation/pull/688, incorporating the changes from there
Co-authored-by: Razvan-Daniel Mihai<EMAIL_ADDRESS>

Is this going to be in 25.3 or 24.11.1?

25.3


Question: Which version control should I use?

If I use mobx-sync with forage, both have their version control, which one should I use?

Any one as you want.
mobx-sync use version to control node or field's version, forage use version to control key version. mobx-sync does not support multiple keys currently, so, if your global store root structure is changed, you can use forage's version to ignore outdated item, or you can use mobx-sync's version to ignore one node or field if its structure is changed.


Add Korean localization and mark more text for localization

I think it should be fine to merge, what do you think?

@ansh

Great thanks for confirming these translations are correct @lens0021
@quiple Can you fix the linting errors so I can merge this PR?

I've fixed a linting error in shareUrl and formatCount, reverting the first letter back to lowercase. We've also made other changes as requested, but I'd like to discuss another requests further.
I've also created another branch for Korean localization and will PR it again later.

Thanks! #2395 has been merged separately.

Whew this is intense! I'm somewhat inclined to get all of the in-flight translations merged, then pull this in

There are also some standing issues that ansh has already remarked upon that do need to be addressed before it can merge

But thank you for all this work @quiple !

@ansh Thanks for review! I'll request a new PR later.


Add Innovation Collective: Boise

Looking into planned support for Eventbrite at gemstate.io, and adding the Eventbrite organizer ID that's being used for the first if not all events going forward. I don't consider this closed until the organizer ID gets finalized.

Unfortunately Eventbite organizer ID<PHONE_NUMBER>2, which Zach told me was would be the ID they'd use going forward for this org, has been unused since March 14th. Events were listed on the private Facebook group after that, with some events cross-listed on Eventbrite organizer ID<PHONE_NUMBER> (Innovation Collective C'dA.)

Given innovationcollective.co no longer lists Boise as a community, I'm guessing this one was unsuccessful (and I haven't heard anything more of it since the first meeting I attended.) Mark group abandoned and close this.

This was cleaned up in #170; I went with a 1/1/2020 abandoned date instead, to match Lewiston and Sandpoint.


acc: Update basic test to pass after latest commit

Description

Updates the basic test which got broken after the latest two PRs got
merged. This patch addresses fixes it.
How Has This Been Tested?

$ make testacc
-> Formatting Go files...
-> Formatting Terraform documentation blocks...
-> Done.
-> Running terraform acceptance tests...
=== RUN   TestAccDatasourceDeployment_basic
=== PAUSE TestAccDatasourceDeployment_basic
=== RUN   TestAccDeployment_basic
=== PAUSE TestAccDeployment_basic
=== RUN   TestAccDeploymentTrafficFilter_basic
=== PAUSE TestAccDeploymentTrafficFilter_basic
=== CONT  TestAccDatasourceDeployment_basic
=== CONT  TestAccDeploymentTrafficFilter_basic
=== CONT  TestAccDeployment_basic
--- PASS: TestAccDeploymentTrafficFilter_basic (15.67s)
--- PASS: TestAccDatasourceDeployment_basic (871.85s)
--- PASS: TestAccDeployment_basic (1308.99s)
PASS
ok  	github.com/terraform-providers/terraform-provider-ec/ec/acc	1309.820s

Types of Changes

[x] Refactoring (improves code quality but has no user-facing effect)

Merging this myself also to get this change in my local


Docs should specify exact dependencies or use shrinkwrap.

Feature Request
Motivation Behind Feature
If a dependency in the docs changes, npm will install it automatically on your machine. To avoid this, we should pin docs dependencies to specific versions.
Feature Description
Pin docs dependencies to specific versions.
Alternatives or Workarounds

Specify exact version numbers in package.json.
Specify a npm-shrinkwrap.json file.
Specify a package-lock.json file.

We have package-lock.json committed now which should address the original concern.


Payments: Copy update request

User story
As a product owner I want to prevent unnecessary emails to mdn-support@, and therefore want the following copy change request implemented:

Please change:
"Please contact mdn-support@ to cancel. " to
something that links to
https://developer.mozilla.org/en-US/payments/recurring/management
in order to prevent unnecessary emails to: mdn-support@

Original Bugzilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1547771
Acceptance criteria

[x] Copy updated to point a user to the recurring payment management page as opposed to the support email address

Tasks

[x] Update copy as per request

[x] Open PR

[ ] Deploy to production

This appears to be live in production, so closing.


Update liaisons on hdash

Please update the liaisons column with the following names:
HTAN BU HTA3   Jen<EMAIL_ADDRESS>HTAN DFCI HTA5  Jen
HTAN Vanderbilt HTA11 Clarisse
HTAN WUSTL HTA12 Clarisse
HTAN SRRS HTA15 Clarisse

I think it might be easier to just delete the liaison column from the dashboard, since we already document this elsewhere.  thoughts?

Yes, I think that would be better
On Thu, Feb 29, 2024 at 6:20 PM ecerami @.***> wrote:

I think it might be easier to just delete the liaison column from the
dashboard, since we already document this elsewhere. thoughts?
—
Reply to this email directly, view it on GitHub
https://github.com/ncihtan/hdash_air/issues/17#issuecomment-1972136429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASQWVX2ZOIIUNYYAVHSCSZDYV63TLAVCNFSM6AAAAABDTZIP3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGEZTMNBSHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Done and deployed at:  https://hdash.website-us-east-1.linodeobjects.com/


Embedded scrollview always fires both vertical & horizontal scrollstart

I implemented the Embedded scrollview scrolling restrictions that you decribed at
https://github.com/IjzerenHein/famous-flex/blob/master/tutorials/FlexScrollView.md#embedded-scrollview-scrolling-restrictions
Unexpectedly, it always fires both vertical & horizontal scrollstart events. I had to make a small change to work around that during vertical-only scrolling by setting a flag in the vertical scrollstart to prevent the horizontal scrollstart from coming in behind it and disabling the vertical.  Logically it seems that setOptions({ enabled: false }) would disable the horizontal scrollstart firing, but there must be a race condition with the callbacks.
While the list is scrolling one way, it can't be scrolled the other way since it's waiting for the scrollend event to re-enable.  This is problematic as the list decelerates and looks like it has stopped but not quite. Is there an option to increase the dampening effect?
Also is there an option to limit how far the list can be pulled away from the edge at the ends of the list?  That inertia draws out how long the list continues moving and prevents swiping in the perpendicular direction. It would be great if that could be disabled because in my case, the horizontal scrollview shouldn't pull away from the edge.

Thanks for reporting this Peace.
I will have to have a closer look at the scrollstart events both firing, this doesn't seem right.
The scrolling damping effect is controlled by a physics particle, a spring and two drag-forces. You can fine-tune these like this. You will have to look in the famo.us source-code on what other options you can pass to these physics objects:
var scrollView = new FlexScrollView({
        scrollParticle: {
            // use defaults
        },
        scrollDrag: {
            forceFunction: Drag.FORCE_FUNCTIONS.QUADRATIC,
            strength: 0.001,
            disabled: true
        },
        scrollFriction: {
            forceFunction: Drag.FORCE_FUNCTIONS.LINEAR,
            strength: 0.0025,
            disabled: false
        },
        scrollSpring: {
            dampingRatio: 1.0,
            period: 350
        },
});

It's currently not possible to configure how far the the list can be pulled from the edge. If you think this would be useful for other developers as well, please make a explanatory feature request for it so others can vote for it as well.

Hi, I am unable to reproduce this problem. Can you share the code or a live example so I can have a look?
Are you sure that you have set touchMoveDirectionThresshold: 0.5 for both scrollviews?

ping @peacechen

ping @peacechen


Thumbnail navigation example doesn't seem to work with vertical thumbnail navigation layout

Bug is related to

[ ] The Vanilla JavaScript version
[X] The React version
[ ] The Embla Carousel core (all versions)
[ ] Documentation website
[ ] Other

Embla Carousel version

v4.5.03

Describe the bug

Thumbnail navigation via two embla carousels does not work when thumbnail carousel is set to vertical. The thumbnail carousel seems to want to recognize as a horizontal one

CodeSandbox

https://codesandbox.io/s/embla-carousel-thumbnails-react-forked-b34hv?file=/src/css/embla.css

Steps to reproduce

Fork thumbnail example
Add flex direction column to thumbnail carousel container (.embla__container--thumb)
Add fixed height to thumbnail carousel container (.embla__container--thumb)
Clicking thumbnails does not navigate the thumbnail carousel and swiping the main carousel does not navigate the thumbnail carousel

Expected behavior

Clicking a thumbnail and swiping the main carousel should center the current thumbnail

Additional context

N/A

Hi @bundit,
Have you set the thumbnail carousel options to vertical with the axis option?
David

@davidcetinkaya Seems like I didn't read the docs well enough :) thanks for your help