Bitmap.prototype.getAlphaPixel return the wrong type

Hello,
I noticed meanwhile working on the typescript conversion I noticed that
Bitmap.prototype.getAlphaPixel is supposed to return a String although my linter show it's return an Uint8ClampedArray
wich is making the documentation wrong.
I suggest for fix this to either change the return type from the comment from String to  Uint8ClampedArray or to do this :
    Bitmap.prototype.getAlphaPixel = function(x,  y) {
        var data = this._context.getImageData(x, y, 1, 1).data;
        return data[3].toString();
    };

thanks for your time!

Nevermind my version was outdated without I noticed
Closing this.

I am reopening again due that I noticed that yes this was indeed having a error
/**
 * Returns pixel color at the specified point.
 *
 * @method getPixel
 * @param {Number} x The x coordinate of the pixel in the bitmap
 * @param {Number} y The y coordinate of the pixel in the bitmap
 * @return {String} The pixel color (hex format)
 */
Bitmap.prototype.getPixel = function(x, y) {
    var data = this._context.getImageData(x, y, 1, 1).data;
    var result = '#';
    for (var i = 0; i < 3; i++) {
        result += data[i].toString(16).padZero(2);
    }
    return result;
};

/**
 * Returns alpha pixel value at the specified point.
 *
 * @method getAlphaPixel
 * @param {Number} x The x coordinate of the pixel in the bitmap
 * @param {Number} y The y coordinate of the pixel in the bitmap
 * @return {String} The alpha value
 */
Bitmap.prototype.getAlphaPixel = function(x, y) {
    var data = this._context.getImageData(x, y, 1, 1).data;
    return data[3];
};

getPixel is indeed converted but not AlphaPixel

Should we add color class?

getAlphaPixel returns alpha value of specified pixel, so It's correct.
We agree method name doesn't have clear intention,
But for compatibility, We cannot change it.


Version conflict for rubocop-rspec 1.44.0 with rubocop-ast 0.8

I just updated all the rubocop gems we use in our project and found that rubocop cannot load rubocop-rspec afterwards.
Unable to activate rubocop-rspec-1.44.0, because rubocop-ast-0.8.0 conflicts with rubocop-ast (~> 0.7.1)
I am pretty sure this is due to the newly added rubocop-ast runtime dependency in the gemspec
spec.add_runtime_dependency 'rubocop-ast', '~> 0.7.1'

Is there a particular reason to limit the minor version?

Here's a PR, I have no idea if this locking is for any particular reason but at least get a build running on it.

My bad guys, I don't know what I was thinking.
Thanks for the PR, @PhilCoggins !

Fixed in v1.44.1. Thanks for reporting.


HA 0.108 error?

I get this 👍
Failed config
General Errors:
- Component error: sonoff - No module named 'Crypto'
when I use : Check Home Assistant configuration add-on
?  what is it ?

I am seeing this as well.  Latest of everything installed, 0.107.7.

Thanks for your great component! I love it.
Since 0.108.0 my Sonoff Remote control usb devices are not working anymore. Hopefully you can solve this. No errors noticed, they are just not available anymore since the update from 0.107.7 to 0.108.0. Tried several restarts, no luck. Greetings!!

I get the same error message with Check configuration add-on.
But this is not a real issue as I can use the devices (sonoff S26) after update to HA 108.1

The problem
Check Home Assistant configuration v3.2.0 returns an error for custom SONOFF integration  (see https://github.com/AlexxIT/SonoffLAN) :
Component error: sonoff - No module named 'Crypto
Environment
Home Assistant Core release with the issue: 0.108.1
Last working Home Assistant Core release (if known):
Operating environment (Home Assistant/Supervised/Docker/venv): HassOS 3.12
Integration causing this issue: Check Home Assistant configuration 3.2.0
Link to integration documentation on our website:
Problem-relevant configuration.yaml
Traceback/Error logs
[[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing...
starting version 3.2.9
[16:23:13] INFO: Update udev information
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[16:23:13] INFO: Setup udev devices
[16:23:13] INFO: Don't worry, this temporary installation is not overwriting your current one.
[16:23:13] INFO: Installing Home Assistant: latest...
[16:23:13] INFO: Please be patient, this might take a few minutes...
[16:23:35] INFO: Installed Home Assistant 0.108.5
[16:23:35] INFO: Making a copy of your configuration for checking...
[16:23:35] INFO: Checking your configuration against this version...
[16:25:05] ERROR: The configuration check did not pass!
[16:25:05] ERROR: See the output below for more details.
INFO:homeassistant.util.package:Attempting install of colorlog==4.1.0
Testing configuration at /tmp/config
INFO:homeassistant.util.package:Attempting install of xknx==0.11.2
INFO:homeassistant.util.package:Attempting install of hbmqtt==0.9.5
INFO:homeassistant.util.package:Attempting install of paho-mqtt==1.5.0
INFO:homeassistant.util.package:Attempting install of aiohttp_cors==0.7.0
INFO:homeassistant.util.package:Attempting install of flux_led==0.22
INFO:homeassistant.util.package:Attempting install of ha-philipsjs==0.0.8
INFO:homeassistant.util.package:Attempting install of pysonos==0.0.25
INFO:homeassistant.util.package:Attempting install of defusedxml==0.6.0
INFO:homeassistant.util.package:Attempting install of netdisco==2.6.0
INFO:homeassistant.util.package:Attempting install of python-forecastio==1.4.0
INFO:homeassistant.util.package:Attempting install of google-api-python-client==1.6.4
INFO:homeassistant.util.package:Attempting install of httplib2==0.10.3
INFO:homeassistant.util.package:Attempting install of oauth2client==4.0.0
INFO:homeassistant.util.package:Attempting install of speedtest-cli==2.1.2
INFO:homeassistant.util.package:Attempting install of wakeonlan==1.1.6
INFO:homeassistant.util.package:Attempting install of mutagen==1.43.0
INFO:homeassistant.util.package:Attempting install of gTTS-token==1.1.3
INFO:homeassistant.util.package:Attempting install of google-cloud-texttospeech==0.4.0
INFO:homeassistant.util.package:Attempting install of hass-nabucasa==0.32.2
INFO:homeassistant.util.package:Attempting install of home-assistant-frontend==20200407.2
INFO:homeassistant.util.package:Attempting install of PyNaCl==1.3.0
INFO:homeassistant.util.package:Attempting install of distro==1.4.0
INFO:homeassistant.util.package:Attempting install of sqlalchemy==1.3.15
INFO:homeassistant.util.package:Attempting install of HAP-python==2.8.2
INFO:homeassistant.util.package:Attempting install of aiofiles==0.4.0
INFO:homeassistant.util.package:Attempting install of aiogithubapi==0.5.0
INFO:homeassistant.util.package:Attempting install of hacs_frontend==20200309184730
INFO:homeassistant.util.package:Attempting install of integrationhelper==0.2.2
INFO:homeassistant.util.package:Attempting install of semantic_version==2.8.4
INFO:homeassistant.util.package:Attempting install of influxdb==5.2.3
INFO:homeassistant.util.package:Attempting install of WazeRouteCalculator==0.12
INFO:homeassistant.util.package:Attempting install of psutil==5.7.0
Failed config
General Errors:
- Component error: sonoff - No module named 'Crypto'
Successful config (partial)
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Additional information

hopefully someone could fix it i had troubles with 108.5 to had to downgrade back

i get this too:
2020-04-20 20:28:59 ERROR (MainThread) [homeassistant.setup] Setup failed for sonoff: Unable to import component: No module named 'Crypto'

I forgot to post... I went ahead with the 0.108.1 and subsequent updates and it seems to be working for me.

i don't know why but i had to manual click all the switches in the ewelink app before they where all found in home assistant.
it all worked before it was just after the updates

I have the same problem but the module named alternates between Crypto and Zerconf.
I went ahead and tried running HA and both my new eWelink switches were found and appear to operate correctly.
They are not Sonoff but these from Amazon UK: https://www.amazon.co.uk/gp/product/B07WYV4GHH/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

ROR (MainThread) [homeassistant.setup] Setup failed for sonoff: Unable to import component: No module named 'Crypto'

Had the same issue. Had to pip install pycryptodome in HA virtual env.

i had the problem as soon as i restarted my Home assistant
all my sonoff things where unavailable
i tryed alot not working things
but i have found my solution as this:
i was using an Netgear R7000 Router
running standard netgear firmware
someone told me maybe it was mDNS but wasn't sure
so i tought maybe i flash that crappy netgear ;)
i'm using Advanced Tomato now (because i didn't get my USB working on Fresh Tomato)
and now it works i can restart as many as i want directly sonoff is available and working
Maybe it could help someone grz alex

#93 Fixed https://github.com/AlexxIT/SonoffLAN/releases/tag/v1.10.4

Thank you.
I've just checked and so far there is no warning anymore with the check
congig tool.
Thanks.
Le mer. 6 mai 2020 à 09:57, Alex X<EMAIL_ADDRESS>a écrit :

#93 https://github.com/AlexxIT/SonoffLAN/issues/93 Fixed
https://github.com/AlexxIT/SonoffLAN/releases/tag/v1.10.4
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/AlexxIT/SonoffLAN/issues/74#issuecomment-624498912,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2HDACA2CJAY52RQFJ5OULRQEJ4ZANCNFSM4MEDUIAA
.

many thanks for the fix i updated my version looks ok ;) keep up the good work !


429 {"type":"error","error":{"type":"rate_limit_error","message":"This request would exceed your organization’s rate limit of 80,000 input tokens per minute.

Which API Provider are you using?
Anthropic
Which Model are you using?
Claude Sonnet 3.5
What happened?
Cline was testing a website locally. There should not have been any traffic back and forth to the LLM API. it went to close the task and failed because it did not have enough tokens. I have not used cline for a couple of days.
Steps to reproduce

resume testing local webpages for website
success on all testing
try to close the task

Relevant API REQUEST output
Step 3 of 3

Previous

Next

429 {"type":"error","error":{"type":"rate_limit_error","message":"This request would exceed your organization’s rate limit of 80,000 input tokens per minute. For details, refer to: https://docs.anthropic.com/en/api/rate-limits; see the response headers for current usage. Please reduce the prompt length or the maximum tokens requested, or try again later. You may also contact sales at https://www.anthropic.com/contact-sales to discuss your options for a rate limit increase."}}

Additional context

This is the rate limit on your own API from Anthropic. See here for details, it's not a bug with CLINE...
See tier:
https://docs.anthropic.com/en/api/rate-limits

I totally understand that. and I am at a tier 2 Anthropic API customer. It does not seem right that I can't even close a Cline task even with not doing any other work for days within Cline using Claude Sonnet. Is there any way I can see the tokens that are being asked for that are exceeding the 80,000 tokens per minute that I am allowed?

The best solution is change to openrouter. This error disappear completely

Sorry you ran into this @Garry-TI but like @rlgordaliza recommended, I suggest using OpenRouter for no rate limit issues


refactor: CodeIgniter has context

Description
Supersede: #5649

add CodeIgniter::$context: web, php-cli, spark
make the constant SPARKED deprecated
remove is_cli() in CodeIgniter

Checklist:

[x] Securely signed commits
[x] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

@samsonasik Is this a bug of rector?
1 file with changes
===================

1) system/CodeIgniter.php:369

    ---------- begin diff ----------
@@ @@
     }

     /**
-     * Invoked via php-cli command?
-     */
-    private function isPhpCli(): bool
-    {
-        return $this->context === 'php-cli';
-    }
-
-    /**
      * Web access?
      */
     private function isWeb(): bool
    ----------- end diff -----------

Applied rules:
 * RemoveUnusedPrivateMethodRector

@samsonasik

could you create failing test case?

No, I tried on getrector.org/demo, but RemoveUnusedPrivateMethodRector was not applied.

Also, I think we should set a default context on MockCodeIgniter (probably "web"?) so people's tests don't start failing unexpectedly.

Added.

@MGatner

Unless there is a compelling reason for these methods I prefer the simple property check inline.

The simple property check inline is too complex to me, as @samsonasik pointed out.
Can I use private methods?

The simple property check inline is too complex to me, as @samsonasik pointed out.
Can I use private methods?

I'm fine with the private methods. It still isn't my preference but I don't think either is "wrong" and I trust you as the author, unless there are other stronger opinions.

@MGatner Can you review?

Should spark and public/index.php be included in the "All Changes" section?

Strictly speaking no, I think. Because:

All changes noted here are optional until the next major version,
and any mandatory changes will be covered in the sections above.

@samsonasik
Can't reproduce.
$ php spark serve

CodeIgniter v4.1.8 Command Line Tool - Server Time: 2022-02-18 17:51:33 UTC-06:00

CodeIgniter development server started on http://localhost:8080
Press Control-C to stop.
[Sat Feb 19 08:51:33 2022] PHP 8.0.15 Development Server (http://localhost:8080) started


Cannot save a secret of type PSCredential

Issue # 2
When trying to store a credential from Get-Credential, I get an error back from op.exe
Set-Secret -Name 'PS Test 2' -Secret (Get-Credential)

PowerShell credential request
Enter your credentials.
 {Get-Secret, Get-SecretInfo, Get-SecretVault, Register-SecretVault…}
Manifest   <IP_ADDRESS>               SecretManagement.1Password

$PSVersionTable

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

op -v

1.8.0

I'm running PowerShell 7.1.0 on a Mac, and got the same error.
Debugging the flow, it looks like the PSCredential block within the switch (Set-Secret function) is not being executed.
# Suggest changing the first match item in switch from
{ 'string' -or 'Int32' -or 'Int64' -or 'Double' }
# to
{ $PSItem -in 'string','Int32','Int64','Double' }

@DonPwrShellHunt Yup, that was all sorts of wrong. Fixed it with a more concise check.

Working great now!


Spatial audio doesn't work in iOS12.01 safari

Hi.
I tried resonance Audio SDK for web in (iOS12.0.1/safari & OSX10.13.6/safari) . But it did't work at all.
Official Web sample didn't play any sound in this environments.
In iOS11.2.5, it seems to work well. Would anyone tell me this reason?

Just to clarify:
Safari on iOS 11.2.5 = Working
Safari on iOS 12.0.1 = Not working
Safari on OSX 10.13.6 = Not working
Do you see any error messages in the developer console?

@hoch Thank you for reply.
In iOS 12.0.1 and OSX10.13.6, Hello world Demo show these message when push play button. There was nothing error message.

[Log] [Omnitone] Version 1.0.6 (running Safari 12.0.1 on Mac OS X) (@144.00ms) (resonance-audio.min.js, line 166)
[Log] [Omnitone] Safari detected. Appliying polyfill... (@144.00ms) (resonance-audio.min.js, line 166)
[Log] [Omnitone] FOARenderer: Initializing... (mode: ambisonic) (@280023.00ms) (resonance-audio.min.js, line 166)
[Log] [Omnitone] BufferList: 2 AudioBuffers from Base64-encoded HRIRs loaded successfully. (@280231.00ms) (resonance-audio.min.js, line 166)
[Log] [Omnitone] FOARenderer: HRIRs loaded successfully. Ready. (@280232.00ms) (resonance-audio.min.js, line 166)

I think this is related to CORS issue. I am seeing the same problem when I run Omnitone example:
https://rawgit.com/GoogleChrome/omnitone/master/examples/foa-renderer.html

MediaElementAudioSource outputs zeroes due to CORS access restrictions for https://rawgit.com/GoogleChrome/omnitone/master/examples/resources/4ch_B_FuMaNorm_FuMaOrd_speech.wav

At least Chrome Canary (72.0.3599.0) produces this error, so I can track it from there.

I can confirm:

https://cdn.rawgit.com/resonance-audio/resonance-audio-web-sdk/master/examples/room-models.html does not play any sound with Chrome 85.0.4183.109 on iOS 14.0.1.
When I download this repo, and host it all locally, the audio does play and the demo works. Though there is some audible noise. It seems somewhat rhythmic, so perhaps it's a buffer issue.

To summarize - this issue is definitely caused by CORS. But there might be more problems too.


arc_select fails on large dataset

Describe the bug
arc_select() crashes when downloading a large dataset. Not sure if this is truly connected to it being large or some other aspect of the data, but I can confirm that I am able to download other, smaller datasets.
To Reproduce
Use arc_open to open a feature service and arc_select to download the feature service and return it as an sf.
library(magrittr)
library(arcgis)

options(RUST_BACKTRACE=1)

PRCP_pred <- "https://services.arcgis.com/GL0fWlNkwysZaKeV/arcgis/rest/services/TXLA_ZCTA_PRCPpred/FeatureServer/0" %>%
    arc_open() %>%
    arc_select()
#> thread '<unnamed>' panicked at arcpbf\src\parse.rs:11:22:
#> internal error: entered unreachable code
#> thread '<unnamed>' panicked at arcpbf\src\lib.rs:156:1:
#> explicit panic
#> Error in multi_resp_process_(resps) :
#>   User function panicked: multi_resp_process_

I made the feature service public so you should be able to try to download it for yourself
Expected behavior
I expected the feature to be downloaded and stored as an sf. Annoyingly, the error only happens after it seems to have downloaded the entire feature.
Additional context
R version 4.4.0 (2024-04-24 ucrt)
Platform: x86_64-w64-mingw32/x64
Running under: Windows 10 x64

Well here is the good news. I can reproduce the bug with only one feature! Bad news, there's a bug 😲. I'm sorry about that. I'll work on it.


Use leases lock for istio operator's resourcelock

Signed-off-by: Tianpeng Wang<EMAIL_ADDRESS>Please provide a description of this PR:
Since 1.9 (https://github.com/istio/istio/commit/8ed67b3c4f2ef6691d65925b7c999652e0d95df8), the default resource lock is configmapsleases, now we can use "leases" only, which performs better than configmaps (for legacy reasons)
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

Hi @timonwong. 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.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
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.

@timonwong: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
2af3e2ca068d55bec4401b02d9c3806f65ef8248
link
true
/test release-notes_istio

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.

@timonwong: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
2af3e2ca068d55bec4401b02d9c3806f65ef8248
link
true
/test release-notes_istio

gencheck_istio
2af3e2ca068d55bec4401b02d9c3806f65ef8248
link
true
/test gencheck_istio

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.

@timonwong: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
2af3e2ca068d55bec4401b02d9c3806f65ef8248
link
true
/test gencheck_istio

release-notes_istio
d0541151fd2cce8e6ba4a2e4ebe2ab8967f82c56
link
true
/test release-notes_istio

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.

Is release note required?
And besides, why the @istio-policy-bot didn't run for some PRs?

@timonwong Is there logged issue for this fix? If yes, you'd better add release note.

I would add a release note as it could be a breaking change if someone has
a bespoke config (since it uses new RBAC permission). Shouldn't be an issue
for users using the normal install method but good to call out just in case
On Fri, Jan 28, 2022, 3:46 AM Morven Cao @.***> wrote:

@timonwong https://github.com/timonwong Is there logged issue for this
fix? If yes, you'd better add release note.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/36931#issuecomment-1024138964, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXKHMCNZZDKWVDXSNOTUYJ62VANCNFSM5MPNS7YA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because your review was requested.Message ID:
@.***>


Proposal: Improve normalizeGlyphName.

Currently the normalizer for glyph names only tests for type and lower limit character length.
From §6 in the AGL spec.:

All glyph names are subject to a length-limit of 63 characters, and require that they be entirely composed of characters from the following set: A–Z, a–z, 0–9, ‘.’ (period; U+002E FULL STOP), and ‘_’ (underscore; U+005F LOW LINE).

Apart from keeping glyph names standardised, these added restrictions would benefit groups, insofar as they are intended to only hold lists of glyph names.

Suggested implementation:
def normalizeGlyphName(value: str) -> str:
    """Normalize a glyph's name.

    :param value: The glyph name to normalize as a non-empty :class:`str`.
    :return: A :class:`str` representing the normalized glyph name.
    :raises TypeError: If `value` is not a :class:`str`.
    :raises ValueError: If `value` is an empty string.

    """
    if not isinstance(value, str):
        raise TypeError(f"Glyph names must be strings, not {type(value).__name__}.")
    if not 1 <= len(value) <= 63:
        raise ValueError("Glyph names must be between 1 and 63 character long.")
    allowed = set(string.ascii_letters + string.digits + "._")
    if not all(character in allowed for character in value):
        raise ValueError(
            "Glyph names must only contain the following characters: "
            f"{''.join(sorted(allowed))}"
        )
    return value

Additionally, The AGL states that glyph names cannot start with a number or a period (except .notdef). Here's a suggested implementation taking all of these restrictions into account:
def normalizeGlyphName(value: str) -> str:
    """Normalize a glyph's name.

    :param value: The glyph name to normalize as a :class:`str`. The value:
        - must be 1-63 characters in length.
        - must consist of only letters (a-z, A-Z), numbers (0-9), periods (.) or
          underscores (_).
        - must not start with a number.
        - must not start with a period, unless when named ``'.notdef'``.

    :return: A :class:`str` representing the normalized glyph name.
    :raises TypeError: If `value` is not a :class:`str`.
    :raises ValueError:
        - If `value` is not within the accepted length range.
        - If `value` contains characters outside the accepted character set.
        - If `value` starts with a number.
        - If `value` starts with a period when not named ``'.notdef'``.

    """
    if not isinstance(value, str):
        raise TypeError(f"Glyph names must be strings, not {type(value).__name__}.")
    if not 1 <= len(value) <= 63:
        raise ValueError("Glyph names must be between 1 and 63 character long.")
    allowed = set(string.ascii_letters + string.digits + "._")
    if not all(character in allowed for character in value):
        raise ValueError(
            "Glyph names must only contain the following characters: "
            f"{''.join(sorted(allowed))}"
        )
    if any(value.startswith(d) for d in string.digits):
        raise ValueError("Glyph names cannot start with a number.")
    if value != '.notdef' and value.startswith('.'):
        raise ValueError("Glyph names not named '.notdef' cannot start with a period.")
    return value
``


Add support of new command: ssubscribe and sunsubscribe

#1958
implemented command:
ssubscribe
sunsubscribe
pubsub shardchannels
pubsub shardnumsub

@raffertyyu Thanks for your contributions.

2.8version support all redis 7.0  pubsub???
MakeCmdAttr<CommandPublish>("publish", 3, "read-only pub-sub", 0, 0, 0),
MakeCmdAttr<CommandMPublish>("mpublish", -3, "read-only pub-sub", 0, 0, 0),
MakeCmdAttr<CommandSubscribe>("subscribe", -2, "read-only pub-sub no-multi no-script", 0, 0, 0),
MakeCmdAttr<CommandUnSubscribe>("unsubscribe", -1, "read-only pub-sub no-multi no-script", 0, 0, 0),
MakeCmdAttr<CommandPSubscribe>("psubscribe", -2, "read-only pub-sub no-multi no-script", 0, 0, 0),
MakeCmdAttr<CommandPUnSubscribe>("punsubscribe", -1, "read-only pub-sub no-multi no-script", 0, 0, 0),
MakeCmdAttr<CommandSSubscribe>("ssubscribe", -2, "read-only pub-sub no-multi no-script", 0, 0, 0),
MakeCmdAttr<CommandSUnSubscribe>("sunsubscribe", -1, "read-only pub-sub no-multi no-script", 0, 0, 0),
MakeCmdAttr<CommandPubSub>("pubsub", -2, "read-only pub-sub no-script", 0, 0, 0), )

/* pubsub */
{"psubscribe","Listen for messages published to channels matching the given patterns","O(N) where N is the number of patterns the client is already subscribed to.","2.0.0",CMD_DOC_NONE,NULL,NULL,COMMAND_GROUP_PUBSUB,PSUBSCRIBE_History,PSUBSCRIBE_tips,psubscribeCommand,-2,CMD_PUBSUB|CMD_NOSCRIPT|CMD_LOADING|CMD_STALE|CMD_SENTINEL,0,.args=PSUBSCRIBE_Args},
{"publish","Post a message to a channel","O(N+M) where N is the number of clients subscribed to the receiving channel and M is the total number of subscribed patterns (by any client).","2.0.0",CMD_DOC_NONE,NULL,NULL,COMMAND_GROUP_PUBSUB,PUBLISH_History,PUBLISH_tips,publishCommand,3,CMD_PUBSUB|CMD_LOADING|CMD_STALE|CMD_FAST|CMD_MAY_REPLICATE|CMD_SENTINEL,0,.args=PUBLISH_Args},
{"pubsub","A container for Pub/Sub commands","Depends on subcommand.","2.8.0",CMD_DOC_NONE,NULL,NULL,COMMAND_GROUP_PUBSUB,PUBSUB_History,PUBSUB_tips,NULL,-2,0,0,.subcommands=PUBSUB_Subcommands},
{"punsubscribe","Stop listening for messages posted to channels matching the given patterns","O(N+M) where N is the number of patterns the client is already subscribed and M is the number of total patterns subscribed in the system (by any client).","2.0.0",CMD_DOC_NONE,NULL,NULL,COMMAND_GROUP_PUBSUB,PUNSUBSCRIBE_History,PUNSUBSCRIBE_tips,punsubscribeCommand,-1,CMD_PUBSUB|CMD_NOSCRIPT|CMD_LOADING|CMD_STALE|CMD_SENTINEL,0,.args=PUNSUBSCRIBE_Args},
{"spublish","Post a message to a shard channel","O(N) where N is the number of clients subscribed to the receiving shard channel.","7.0.0",CMD_DOC_NONE,NULL,NULL,COMMAND_GROUP_PUBSUB,SPUBLISH_History,SPUBLISH_tips,spublishCommand,3,CMD_PUBSUB|CMD_LOADING|CMD_STALE|CMD_FAST|CMD_MAY_REPLICATE,0,{{NULL,CMD_KEY_NOT_KEY,KSPEC_BS_INDEX,.bs.index={1},KSPEC_FK_RANGE,.fk.range={0,1,0}}},.args=SPUBLISH_Args},
{"ssubscribe","Listen for messages published to the given shard channels","O(N) where N is the number of shard channels to subscribe to.","7.0.0",CMD_DOC_NONE,NULL,NULL,COMMAND_GROUP_PUBSUB,SSUBSCRIBE_History,SSUBSCRIBE_tips,ssubscribeCommand,-2,CMD_PUBSUB|CMD_NOSCRIPT|CMD_LOADING|CMD_STALE,0,{{NULL,CMD_KEY_NOT_KEY,KSPEC_BS_INDEX,.bs.index={1},KSPEC_FK_RANGE,.fk.range={-1,1,0}}},.args=SSUBSCRIBE_Args},
{"subscribe","Listen for messages published to the given channels","O(N) where N is the number of channels to subscribe to.","2.0.0",CMD_DOC_NONE,NULL,NULL,COMMAND_GROUP_PUBSUB,SUBSCRIBE_History,SUBSCRIBE_tips,subscribeCommand,-2,CMD_PUBSUB|CMD_NOSCRIPT|CMD_LOADING|CMD_STALE|CMD_SENTINEL,0,.args=SUBSCRIBE_Args},
{"sunsubscribe","Stop listening for messages posted to the given shard channels","O(N) where N is the number of clients already subscribed to a shard channel.","7.0.0",CMD_DOC_NONE,NULL,NULL,COMMAND_GROUP_PUBSUB,SUNSUBSCRIBE_History,SUNSUBSCRIBE_tips,sunsubscribeCommand,-1,CMD_PUBSUB|CMD_NOSCRIPT|CMD_LOADING|CMD_STALE,0,{{NULL,CMD_KEY_NOT_KEY,KSPEC_BS_INDEX,.bs.index={1},KSPEC_FK_RANGE,.fk.range={-1,1,0}}},.args=SUNSUBSCRIBE_Args},
{"unsubscribe","Stop listening for messages posted to the given channels","O(N) where N is the number of clients already subscribed to a channel.","2.0.0",CMD_DOC_NONE,NULL,NULL,COMMAND_GROUP_PUBSUB,UNSUBSCRIBE_History,UNSUBSCRIBE_tips,unsubscribeCommand,-1,CMD_PUBSUB|CMD_NOSCRIPT|CMD_LOADING|CMD_STALE|CMD_SENTINEL,0,.args=UNSUBSCRIBE_Args},


Add appveyor.yml.

Add an initial appveryor.yml to test on AppVeyor's Windows CI.
See here for a sample run: https://ci.appveyor.com/project/MJDSys/bolt/build/2
They provide free accounts for open source software.  I signed up with no issue to test this.

@MJDSys Thanks, I signed up for an account. I'll give it a try. I'm working on some build support that'll run across all the Go platforms but until then it'll be nice to have a Windows build running.


Skip Bind Values performance tuning.

As part of #13498
Instead of setting ? and then replacing, this technique of appending is 6x faster (on the string manipulation piece).
For 1.2 Million records import of 3 columns, it takes 4 mins with this technique (I verified the import with different data in each line this time around) vs. setting it to ? and then performing replace takes 25 mins.

@serge-rider
Reposting from the issue as it's closed now.
In this case, the slowness is because of how the replace method internally works vs. just append. I measured timing and it was just doing replace for 50-70 seconds for every run (100k multirow insert size-with 3 columns)
I had tested all the below options as I didn't want to break anything.
These are the options that I tested.

Single record (multirow insert+no skip bind value, disable batches+no skip bind value, multirow insert+skip bind value, disable batches+skip bind value)
2k+ records (multirow insert+no skip bind value, disable batches+no skip bind value, multirow insert+skip bind value, disable batches+skip bind value)
1M+ records (multirow insert+skip bind value)
The modified version functionally does the same thing as what and you had for skip bind values and @LonwoLonwo for multirow respectively. It just binds the variable in a loop vs. doing replace later.

This does the same work as replace but in a quicker way.
Pls consider this change as it will help in faster data imports.

Was thinking to avoid same modulus calculated over and over again.
The complexity is the same if you have 10 records and 3 attributes, I do
103 and you are suggesting 130?
SD

Calculating modulus is not a really expensive operation on modern CPUs. At least you can make proof of concept to see whether it will perform good or bad.

@ShadelessFox I didn't see any difference in performance using modulus. So, I modified the code just to change the skipBindValues portion. I see a difference in performance close to 6.5x-7x improvement. 30 mins for 1 Million 3 rows vs. 4 mins!

@ShadelessFox-Also noticed the replace is exponentially slow with number of columns increasing to 25+. The append is extremely fast!

I don't really the query.indexOf("\n\tVALUES ") part. Maybe you can move skipBindValues check above, so it will not generate VALUES clause in the first place.
Actually, I was talking about rewriting and embedding this logic in the main loop above to eliminate this additional loop entirely.

I don’t like that part too, but ended up doing it to not touch other part
of the code. I will do that. --
SD

@ShadelessFox Instead of rewriting the main loop, I just have an if-else and do the necessary work in the else. Think this should work.

@ShadelessFox - Take a look when you can, I have updated the code.

Fixed

I like this iteration. Have you tested it?

Yup with different settings and combinations. --
SD

Hi @deepaksenthilkumar. The PR generally looks nice 👍

I did some testing and fixed the assert logic!
Also note the current code in 21.1.2 fails if there are ? in the file

Also note the current code in 21.1.2 fails if there are ? in the file that we are trying to import. So this is not just a performance fix, but also a bug fix!

Do you mean question mark inside values? Now I noticed this too. Blindly replacing ? with actual values is a bit suspicious thing because it can lead to unforeseen consequences when value contains ? too. Nice catch, by the way!

@serge-rider @ShadelessFox - Is this targeted for 21.2.1?

We haven't discussed it yet, unfortunately.

Mainly because of imports with ? Failing this might need to be a priority
fix!--
SD

We'll review it tomorrow.

Let's try it.
@deepaksenthilkumar, @ShadelessFox  Thanks for reviewing and patching 👍

Verified


TWDa filtering when Crocodile's Tongue is chosen library card fails

scenario:

I filtered Library for croc
opened Crocodile's Tongue
clicked TWD icon
clicked + to search for decks with more instances of the card

https://github.com/smeea/vdb/assets/14051461/bca3fddf-b360-4ceb-b5a5-888a56195c9f
URL: https://vdb.im/twd?q={"library"%3A{"100450"%3A{"q"%3A3%2C"m"%3A"gt"}}}
console printscreen:

Fixed in 7a9bc463a3facc164d1063794c71b6c360e8fc27 (was an issue with banned indicators and filtering just brought banned decks to the screen). Will be deployed in the next update.
P.S. Thanks for great detailed report!
Btw, my needs are much simpler, and to save your time in the future be sure that if something is easy reproducible (like following your scenario / url) I would not mind looking at it even without such detailed report, so short one-line reports are welcome too!


[move-only] Two small batched changes

First change converts __shared -> borrowed in the tests. I did this since semantically there isn't a difference beyond mangling and it makes sense to match what our users will use.
I turned off emitting move only errors on functions if we already emitted an escaping capture bug for that function. The reason why is because SILGen today assumes that we will error in such cases and thus does not emit markers in said function for the inout. This then causes us to emit spurious "found a copy of a noncopyable value" errors that
may cause the user to think there is a bug in the compiler.

@swift-ci test

In a forthcoming commit, the 2nd commit will come into play, I am just peeling the onion

@swift-ci smoke test

@swift-ci test

@swift-ci test source compatibility

@swift-ci test

@swift-ci test source compatibility

I discovered a small issue where I introduced an optnone by mistake. I am going to remove it in a follow on smoke test change.

Actually I was wrong about the optnone. It was in my local branch that I am working with on top of this.

I took a look at the compatibility failure. One was a UPASS that showed up on the actual bot.

The other failure is distributed actors which is also failing on other PRs due to misconfiguration. I talked with Konrad and he agreed I can ignore it.


How to Add a Catergoricals Column?

for LineUp V3
I want to add a categoricals column, but i have a hard time to configure it correctly?
I created a ColumnDesc and added it with the builder but I just get an empty column.
const catsColDesc: ICategoricalsColumnDesc & IArrayColumnDesc<string | null> = {
      type: 'categoricals',
      dataLength: 5, // not sure about this property is this the number of categories?
      label: 'catsCol',
      categories, // 5 categories
      missingCategory: 'm.V.'
    };

data = [
{catsCol: ['cat1', 'cat2']},
{catsCol: ['cat2', 'cat3']},
{catsCol: ['cat3', 'cat4']},
{catsCol: ['cat4', 'cat5']}
];
const builder = LineUpJS.builder(data);
const catColumn = new CategoricalsColumn('catsCol', catsColDesc);
builder.column(catColumn.desc);
builder.build(document.body);

I'm also not sure about the data format for the column, is it a string array, object array or string?
Currently I have an array of strings for the categories of the entity.
What is the correct way to configure the column description, add how to add the column to the builder? Furthermore, which format is used for the data values?

what is the use case for an array of categoricals? I haven't found a useful case yet. Do you need a SetColumn. ?

Basically, an entitiy can be part of different set. I thought I would use the categories as my set names. But maybe a SetColumn would be better for the usecase.
The same questions apply, how do i define the column and which format is used for the data values?

desc = { type: 'set', label: 'Set', column: 's', categories: ['c1', 'c2', 'c3']}

rows = [
{  s: ['c1', 'c2'] },
{  s: ['c1'] },
{  s: ['c2', 'c3'] },
];

closing due to inactivity.


Chat-In compose box, emojis displayed are cut off in top.

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

Version Number: 1.4.62
Reproducible in staging?: Y
Reproducible in production?: N
**If this was caught during regression testing, add the test name, ID and link from TestRail:*(https://expensify.testrail.io/index.php?/tests/view/4489664)
Issue reported by: Applause - Internal Team
Action Performed:

Launch app
Tap on a report
Tap emoji picker and select an emoji(any simileys round shaped select it so issue will be visible easily)

Expected Result:
In compose box, emojis displayed must not cut off in top
Actual Result:
In compose box, emojis displayed are cut off in top
Workaround:
Unknown
Platforms:

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

[x] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/81eac5a8-4819-4b6c-85bb-d69beef5e59b
View all open jobs on GitHub

@marcaaron  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Likely live markdown related, and relatively minor. I'm going to demote from a deploy blocker while we fix this.

This is known - we have an existing issue here https://github.com/Expensify/App/issues/39274


Fix for #2312

Implemented constant cleanup method for ExampleGroups and implemented in RSpec::Core::World.reset and RSpec.reset.

I just realized the implementation here isn't quite what we want.  To explain why, let's consider a spec file like this:
RSpec.describe MyClass do
  context "in a particular state" do
    # ...
  end

  context "in some other state" do
    # ...
  end
end

RSpec.describe AnotherClass do
  # ...
end

For this spec file, RSpec will create the following constants:

RSpec::ExampleGroups::MyClass
RSpec::ExampleGroups::MyClass::InAParticularState
RSpec::ExampleGroups::MyClass::InSomeOtherState
RSpec::ExampleGroups::AnotherClass

RSpec.world.example_groups would return just the top-level example groups: [RSpec::ExampleGroups::MyClass, RSpec::ExampleGroups::AnotherClass.
So, when you run @world.example_groups.reduce(&:remove_all_constants), it causes RSpec::ExampleGroups::MyClass to remove its nested constants (RSpec::ExampleGroups::MyClass::InAParticularState and RSpec::ExampleGroups::MyClass::InSomeOtherState) and RSpec::ExampleGroups::AnotherClass to remove its nested constants (but there are none), which means that after resetting, we are left with two constants:

RSpec::ExampleGroups::MyClass
RSpec::ExampleGroups::AnotherClass

But that's not what we want.  In practice, it's only the constants nested under RSpec::ExampleGroups that have to be removed.  Once we've removed those, the ones nested further (e.g. RSpec::ExampleGroups::MyClass::InAParticularState) will be inaccessible -- if a parent constant can't be accessed a child one under it can't be accessed, either.
So I think the implementation we want is ExampleGroups.remove_all_constants.  Much simpler, actually :).
Does that make sense?

Migrated tests to the API's behavior. Updated call to be on parent level groups instead of sub groups.

Cleaned up and send updated to send.

Thanks!

Cherry picked to 3-5-maintenance


(OraklNode) Update Mexc subscription

Description
Mexc only allows maximum 30 subscription, which could lead to potential failure of subscription in the future. instead of subscribing for price pairs one by one, this pr will subscribe to batch ticker and only store the ones we're interested in
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] 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

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Deployment

[ ] Should publish npm package
[ ] Should publish Docker image

@coderabbitai review


Add option to create a service when setting a Port in workloads

Issue:  In rancher 2.4 and before, when we created a deployment and added a port it automatically created a service and opened the port.  I could easily click on the port link in list page and see my app functioning.  We lost that ability in the new UI.
Resolution:  Add an option on in the port section for workloads to create service and open the port.  Then display available external port.

Verified on 2.5-head, commit be72f96

Created a "Damemonset" workload
During add port selected "create service" check
Provided container internal port, public port
The daemonset workload created successfully on each worker node but the endpoint is not routable
The endpoint it creates not using the public port but it uses the container internal port 80

Verified on 2.5-head, commit be72f96

Created a "Damemonset" workload
During add port selected "create service" check
Provided container internal port, public port
The daemonset workload created successfully on each worker node but the endpoint is not routable
The endpoint it creates not using the public port but it uses the container internal port 80

I think in order to validate this issue, both the endpoints listed in the workload table need to be correct, and the service(s) themselves need to be correct. To be in keeping with the Ember UI, clusterIP services are given the same name as the workload and nodeport ip services are given the name with '-nodeport' appended.

I think in order to validate this issue, both the endpoints listed in the workload table need to be correct, and the service(s) themselves need to be correct. To be in keeping with the Ember UI, clusterIP services are given the same name as the workload and nodeport ip services are given the name with '-nodeport' appended.

Verified the fix on 2.5-head, v2.5-24c32a358
I am seeing the "check" box is not there anymore but we add a new option in the dropdown "Do not create service".

Created some daemonset services
Verified the created service in amber UI and Explorer View
Service creation was successful
Created a clone of the service created in Explorer view
The service endpoints display issue is fixed
There is still an issue with the service link endpoint created in Explorer View.
The explorer view shows the created service endpoint with the container internal ports, these ports are not routable.

The explorer view endpoints link, not routable. Port 80 is the internal port of the pod.

In Amber UI, the endpoints link are created with external ports, the links are routable

Expected if we want to display the endpoint link,  we do it with the external ports.

Verified the fix on 2.5-head, v2.5-24c32a358
I am seeing the "check" box is not there anymore but we add a new option in the dropdown "Do not create service".

Created some daemonset services
Verified the created service in amber UI and Explorer View
Service creation was successful
Created a clone of the service created in Explorer view
The service endpoints display issue is fixed
There is still an issue with the service link endpoint created in Explorer View.
The explorer view shows the created service endpoint with the container internal ports, these ports are not routable.

The explorer view endpoints link, not routable. Port 80 is the internal port of the pod.

In Amber UI, the endpoints link are created with external ports, the links are routable

Expected if we want to display the endpoint link,  we do it with the external ports.

Verified the fix on 2.5-head,  761c805
Test1: During the "node port" service create public port was given by the user

Created  a daemonset service of type "node port", during creating the service public port was given as 9999
Service creation was successful
The service endpoint link got created successfully. The endpoint is routable.
But it creates two endpoints for the service,  one with the user given port "9999" other with a random port "

It's expected that daemonset service should create one service endpoint per node.
In case the public port is specified by the user then the service should be exposed only to that port.
Test2: During node port service creation, no port was specified
This time service creation was successful and only created one service endpoint by picking a random port, which is expected

Hi @mantis-toboggan-md
please fix the issue in the test1.

Tested with Rancher server rancher\rancher:v2.5-head version 87006de
When setting a port in workloads, user is given an option to create a service:

Steps:
Create a daemonset. Specify listening port and create a node port service:

The endpoint is seen with the specified port:

On ember UI, the endpoint is also seen:

Ran a few validations tests:
Validated that services created through workload creation have -nodeport appended:

Validated that 1 endpoint is created if 1 port/service is added. And the correct number of endpoints are shown if multiple ports/services are added.

Service view:

If the workload is deleted, the services created are also deleted.
Able to create the following services through workload creation:

ClusterIP
Node Port
Load Balancer

Validated that no service was created if the user selects Do not create a service

Validated endpoints are available in every service type (ClusterIP, Node Port, Load Balancer).


MODEL_FILTER_LIST not working as expected

Bug Report
Installation Method
Through docker compose:
  open-webui:
    container_name: open-webui
    image: ghcr.io/open-webui/open-webui:latest
    environment:
      - OLLAMA_BASE_URLS=http://ollama:11434
      - DEFAULT_USER_ROLE=user
      - ENABLE_MODEL_FILTER=True
      - MODEL_FILTER_LIST="model-0:latest;model-1:latest;model-2:latest"
    ports:
      - "8081:8080"

Environment
macOS Sonoma 14.6.1
Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[ ] I have included the browser console logs.
[ ] I have included the Docker container logs.
[x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:
I expected all 3 models to be in the users available models list.
Actual Behavior:
I only see model-1 in the list.
Description
Bug Summary:
The list seems to ignore any models that do not begin with and end with a semicolon ;. If I add semicolons to the front and back then I see all three models in the list; MODEL_FILTER_LIST=";model-0:latest;model-1:latest;model-2:latest;"
Reproduction Details
Steps to Reproduce:
Create different models and add them MODEL_FILTER_LIST along with ENABLE_MODEL_FILTER=True. Log in as a basic user and notice that any models that are not surrounded with a semicolon ; are not in the user's available models list at the top left.

I have tried with
docker run -d -p 3000:8080 \
--add-host=host.docker.internal:host-gateway
-v open-webui:/app/backend/data
-e MODEL_FILTER_ENABLED=true
-e MODEL_FILTER_LIST="llama3.2:latest;gemma2:latest;llava:latest;mistral:latest;mixtral:latest;"
--name open-webui
--restart always
ghcr.io/open-webui/open-webui:latest
and worked for me.

@parniantaghipour I do not expect to have to put a semicolon at the end of the list llama3.2:latest;gemma2:latest;llava:latest;mistral:latest;mixtral:latest;. Can you remove the semicolon and try again? Also, make sure you are looking at the list as a User and not as an Admin.
Here is what I see:
As a user

As an Admin

MODEL_FILTER_LIST will most like be deprecated in favour of https://github.com/open-webui/open-webui/issues/2924.

I have used this:
docker run -d -p 3000:8080 \                                                   --add-host=host.docker.internal:host-gateway \   -v open-webui:/app/backend/data \   --name open-webui \   --restart always \   -e ENABLE_MODEL_FILTER=True \   -e MODEL_FILTER_LIST="llama3.2:latest;gemma2:latest;llava:latest" \   ghcr.io/open-webui/open-webui:latest
and This is my admin:

and this is my user:

Deprecated in 0.4 #2924


main/vulns: add fixable group

TL;DR:

add a new group of "Fixable" vulns
exit with error on any fixable vulns
add fixable-threshold parameter

The thinking behind the feature:

replicate quay.io behaviour of exposing the number of fixable issues
give the ability to fail CI builds when a fixable issue is detected

The main assumption is fixable issues are actionable, in contrast to CVEs you cannot address because there is no patch released.
The implementation may be not as elegant/idiomatic as it could - any feedback appreciated.

Dope!


Clean up personal stream settings UI

At present, personal stream settings are surrounded by a rectangle, creating visual clutter. This rectangle should be removed.

The "Personal settings" header (see above) should contain the stream name to make that context easier to find: "Personal settings for X"
We should add a section heading for notification settings. We can use the following organization for the settings:

(no section)
- Mute stream
- Pin stream to top of left sidebar
- Stream color
Notifications
-  Visual desktop notifications
-  Audible desktop notifications
-  Mobile notifications
-  Email notifications
-  Notifications for @all/@everyone mentions

@zulipbot claim


How do you get the file type?

I've searched everywhere in the documentation but could not find where to get the file type or extension before the upload starts. My custom uploader receives two parameters (file, updateProgress)  where file is a Blob. How do I know whether the file being upload is say either .png or .jpg?

Figured it out, thanks


More concise concierge message

This makes concierge slightly more concise by moving the reviewer checklist to a collapsed dropdown and removing the signature. I think the signature was nice to have but since concierge's bio now has a link to its repo, its settings information are just 2 clicks away for those that are curious. It's otherwise just noise on every post.
The only issue is you can't have checkboxes inside of these dropdowns on GitHub. I think it's worth compromising because then all the info concierge posts will be pertaining to the user who opened the PR, and those reminders are I think where most of its value is.
@ggetz

Thanks for the pull request @OmarShehata!

: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.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks for the pull request @OmarShehata !

: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.

Reviewer reminders.

- Does Cesium Viewer work?
- Does it work in 2D/CV?
- Does it work (or fail gracefully) in IE11?


Add FEP-bench and EdgeRep

add project description pages for FEP-bench and EdgeRep

@royyhuang can you move the bullet points starting with Topics to just under the project description heading ... see https://ucsc-ospo.github.io/project/osre24/lbl/aiio/ as an example of what I mean.

I think I was able to fix everything with PR #386 -- Please open a new pull request if I missed anything. This is now closed.


Upgrade CI runner from macos-12 to macos-14

MacOS CI runners are deprecated and will be removed soon: https://github.com/actions/runner-images/issues/10721.
In fact, macOS already entered the burnout period.

Grr, libcrypto.3.dylib does not exist in macos-14 (nor 13, nor 15...). In fact, the GH runner documentation says that those newer macOS images only ship with OpenSSL 1.1.1. OpenSSL 3 was probably included in macos-12 by mistake.
The problem is that there doesn't seem to be a libcrypto1.1.dylib file neither...
Maybe because just today macOS is migrating to OpenSSL 3 (https://github.com/actions/runner-images/blob/main/images/macos/macos-14-Readme.md) and things a bit messy. Will wait till tomorrow.

According to https://github.com/actions/runner-images/issues/10817 macOS 13 will get OpenSSL 3, so I suppose we should end up pointing at that (rather than 14) to get oldest possible coverage?

Can we not brew install openssl@3?

According to actions/runner-images#10817 macOS 13 will get OpenSSL 3, so I suppose we should end up pointing at that (rather than 14) to get oldest possible coverage?

actually yeah we may as well wait. Apparently "Image deployment will start on November 4 and will take 2-3 days."

Finally found the right path to libcrypto.3.dylib 😅.

@dagood PTAL


Issue opening PATH for VSCode in Windows

I am using Cygwin64 with Terminus, and when I type code or code . I usually open VSCode from shell, any other shells works, I tested from Cygwin64, Powershell, Git Bash, Mitty and even from cmd and clink.
I think this is a bug related to terminus. By the way so far other Environment PATHs are being read ok.

This issue is regarding my setup in Terminus. To be allowed to use ZSH with Cygwin in Windows I had to put some configuration in SHELL section:

If someone has the workaround let me know. BY THE WAY it only happens with code variable, all other Environment Variables are properly working.
And yes, from Cygwin code command to open VSCODE works smoothly


MSID: 91038 Version: 1 DOI: 2<IP_ADDRESS>2730

"msas": "Neuroscience"
"msid": "91038"
"preprintDoi": "10.1101/2<IP_ADDRESS>2730"
"Reviewed Preprint posted": "2023-11-01"
"Sent for peer review": "2023-08-09"
"Posted to bioRxiv": "2023-10-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>2730v1/")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=91038)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/91038/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>2730)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/91038/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/91038)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/91038

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/91038

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/91038/v1/91038-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/91038)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

elocations missing from references


Flash Ultility 2 Selected file is not a proper BIOS / not a UEFI BIOS

System

Motherboard: Asus Sabertooth Z97 MARK S
BIOS Version: 2702
GPU: AMD Gigabyte Aorus 5700XT
CPU: i7 4770k
[y] CSM is turned off
[y] 4G decoding is enabled
[y] UEFIPatch is applied (see README for more information)

Description
Did UEFITool Method. It created a .ROM file After that i used the UEFIPatch with Powershell which corrected one path: 114Ah 75080FBAE80F89442430 - EB080FBAE80F89442430. Then i got Pad file created at PcIHostBridge which i corrected with MMtool.
The i renamed the .rom to .cap but Flash Utility says file is not proper Bios.
The Modded file is in .rom format but i need .cap.
Have seen a youtube video where someone extraced the modded.rom file from UEFITool and then used HxD to switch the Capsual HEX binaries from the original to the modded and then just renamed the rewritten file to the original one.
https://youtu.be/aISCfhK05Rk?t=1375
I did the same but in Flash Utilitily then says it's not a UEFI Bios and doesn't even start to flash.
This Motherboard isn't in the list yet as i see but other z97 types worked.
Im pretty new to this so please don't harass me to much :D
USB-Stick is In FAT32 Format

Mentioning @Tokobotenkai @cursemex @Divin1ty666 since they all own ASUS Z97 boards and probably know how to solve this.

I used this as one way to flash.
https://rog.asus.com/forum/showthread.php?99490-Flash-any-most-Asus-motherboard-Bios-in-DOS-with-USB-tutorial-Intel-AMD-roll-back
Using EZFlash won't work afaik because of CAP & Rom modifications.
Best of luck.

System
* Motherboard: Asus Sabertooth Z97 MARK S

* BIOS Version: 2702

* GPU: AMD Gigabyte Aorus 5700XT

* CPU: i7 4770k

* [y] CSM is turned off

* [y] 4G decoding is enabled

* [y] UEFIPatch is applied (see README for more information)

Description
Did UEFITool Method. It created a .ROM file After that i used the UEFIPatch with Powershell which corrected one path: 114Ah 75080FBAE80F89442430 - EB080FBAE80F89442430. Then i got Pad file created at PcIHostBridge which i corrected with MMtool.
The i renamed the .rom to .cap but Flash Utility says file is not proper Bios.
The Modded file is in .rom format but i need .cap.
Have seen a youtube video where someone extraced the modded.rom file from UEFITool and then used HxD to switch the Capsual HEX binaries from the original to the modded and then just renamed the rewritten file to the original one.
https://youtu.be/aISCfhK05Rk?t=1375
I did the same but in Flash Utilitily then says it's not a UEFI Bios and doesn't even start to flash.
This Motherboard isn't in the list yet as i see but other z97 types worked.
Im pretty new to this so please don't harass me to much :D
USB-Stick is In FAT32 Format

@Schlappenschleuder
I had issues flashing so this worked for me:
I used a hex editor using instructions here (https://winraid.level1techs.com/t/howto-get-full-nvme-support-for-all-systems-with-an-ami-uefi-bios/30901/5900?page=296).
    First, use UEFITool on the stock.CAP BIOS to extract the body >> Right click AMI Aptio Capsule and choose extract body, Then do NVME mod to that bin/rom
    This is how you should do that >> open stock.CAP in Hex editor and go to offset 800. Open mod bios rom/bin in second tab of hex editor, select all and copy, then paste at offset 800 in stock.cap, then save this file as M5F.CAP

    Extension name does not matter so much when saving, I mean you can easily rename, but how the BIOS is created and it’s contents are what matters.
    Your mod BIOS is in a capsule, but named rom/bin, renaming should have been OK but it’s probably not accepted due to how you did the mod with capsule included while editing.

How I used the hex editor would be the same here: https://winraid.level1techs.com/t/howto-get-full-nvme-support-for-all-systems-with-an-ami-uefi-bios/30901/5903?page=296
Hope it helps.

Thanks for the quick replies,  will try those out later.
Will let you know if those methods worked to share for others.

Hello again, @cursemex @Tokobotenkai @xCuri0
Got the Bios flashed with the USB method @cursemex mentioned. Didn't need to change the HEX Binaries. Booted up fine and went into BIOS do disable CSM and enable 4G Decoding. GPU-Z shows that only Resizable BAR isn't enabled.
Launched ReBarState and set value to 14 for 16gb and got GetLastError 5.
I've got 16 GB Ramm installed on Motherboard.
Does it have domething to do with overclock ?
Is there a way to solve this?
Can't find anything related to that in @cursemex or Githubs Thread.

@Schlappenschleuder you aren't using the correct patches.txt that's provided in this repo. i downloaded your bios file and none of the patches are applied.

ofc you have to do the MMTool thing to not get any pad files when patching

@xCuri0 It works! Thank you very much!
I just overlooked the txt file in that thread thank you for mentioning.
Only little issue is on boot my keaboard doesn't get detected but in Windows it does but doesn't bother me so no big deal :)
I am goin to look into games soon to see what performance increase i get.
Set bar size in ReBarState.exe directly to value 14 for 16 GB. Should i try more ? This is the Size for now.
I have 8192mb Memory size on my card and 16 GB of Ram if this influences working ReBarSize please let me know.
Also thanks to @cursemex for giving me Thread and step by step instructions & @Tokobotenkai for letting me know how to use HXE editor even if i didn't needed it :)

@xCuri0 I do have a question, when i set barsizevalue in ReBarState to 15 for 16gb and reboot, i still got 8gb shown in GPU-Z.
Does this mean i am at maximum?

@Schlappenschleuder yes because 8gb VRAM GPU


Github URL broken on Chrome webstore when extension installed

I was trying to send the Github link to this awesome extension to a friend but couldn't remember the URL so I went to the Chromestore to get it. Lo and behold, the extension actually breaks the URL:

Replaces the text 'the cloud' with 'my butt', as well as 'cloud' with 'butt' in certain contexts.
Slight improvements to Butt-to-butt, found here:
https://github.com/panicsteve/butt-to-butt
My repo: https://github.com/hank/butt-to-butt
Changes occurences of "butt" or "my butt" to "butt" or "my butt" respectively and only in proper context (not weather sites, if possible).

Not a huge deal but it was confusing at first.
Should URLs be ignored?

Seems like that entire description is messed up by the plugin itself.


GPMDP changing audio quality on bluetooth speaker

OS: macOS High Sierra Version 10.13.3
GPMDP Version: Version 4.5.0
Issue Descriptions: When I turning on bluetooth speaker and wanna listen the music. Quality of sound is very bad
Steps to Reproduce: Open GPMDP, play music, connect bluetooth device, done - you have a bad sound quality.

Duplicate #2589


Fix logical error in Sample transform javadoc

If the limit passed into the Sample transform is greater than or equal to the size of the input, then all the input's elements will be selected.

R: @davorbonaci

LGTM (will merge today).


keep getting  Alloy is not installed error after install

Windows 10 Enterprise
vs code

Error

I had the same issue and I believe you need to install alloy locally as well Install alloy.

looks like that error message is a red herring. it still works in vscode, even with alloy-installer-windows-amd64.exe.zip not installed.


update searchengine for realease

@MrCreosote can you release

@tiramisu24 Should probably make this release 0.2.2-dev until we merge to master, as we may make changes after we put it on CI
@arfathpasha are you ok with making a dev release with what's currently on develop?


Load "real" data to wildlife-datareturn website

As part of finalizing, did some additional updates to open-humans (94ef2f313) to add this to the activities page.

Done


Replace calls to v8::Object::Set/GetHiddenValue with Set/GetPrivate

The Set/GetHiddenValue API was removed in V8 5.2, which is shipped in Electron 1.3.0. Presumably at some point NAN will get updated to handle this breaking API change, but for the time being I've sourced an alternative implementation of the removed functionality using the v8::Object::Set/GetPrivate API. Compatibility with older V8 versions has been preserved.

@3y3 Is it possible to merge this PR?

If anyone needs it, you can grab from here: https://github.com/RisingStack/v8-profiler or https://www.npmjs.com/package/@risingstack/v8-profiler
cc @enlight @tomruttle @bonesoul

Just checking in to see if this package is going to be updated for node v7+ or taken over by somebody else?

@3y3 What needs to be done here?

Is there anyone who can use v8-profiler for Electron apps these days?
I've tried the solutions by @gergelyke and @jrieken and I got this error:
Error: The specified procedure could not be found.
\\?\C:\_CODE\electron-markdownify\node_modules\v8-profiler\build\Release\profiler.node
    at Error (native)
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:173:20)
    at Object.Module._extensions..node (module.js:583:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:173:20)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\_CODE\electron-markdownify\node_modules\v8-profiler\v8-profiler.js:2:15)

Tried with Node v6.1.0, v6.3.1, and v7.4.0 on Windows 10 64 bit.

@gergelyke risingstack version fails to compile on Linux x64, node 7.5
><EMAIL_ADDRESS>install /usr/lib/node_modules/@sematext/logagent-nodejs-monitor/node_modules/@risingstack/v8-profiler
> node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(404): https://node-inspector.s3.amazonaws.com/profiler/v5.7.0/node-v51-linux-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v51 ABI) (falling back to source compile with node-gyp)
gyp WARN EACCES user "root" does not have permission to access the dev dir "/home/ubuntu/.node-gyp/7.5.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_modules/<EMAIL_ADDRESS>make: Entering directory `/usr/lib/node_modules/@sematext/logagent-nodejs-monitor/node_modules/@risingstack/v8-profiler/build'
make: *** No rule to make target `../.node-gyp/7.5.0/include/node/common.gypi', needed by `Makefile'.   System Linux 3.13.0-108-generic
gyp ERR! command "/usr/bin/nodejs" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/usr/lib/node_modules/<EMAIL_ADDRESS>"--module_name=profiler" "--module_path=/usr/lib/node_modules/<EMAIL_ADDRESS>gyp ERR! cwd /usr/lib/node_modules/@sematext/logagent-nodejs-monitor/node_modules/@risingstack/v8-profiler
gyp ERR! node -v v7.5.0
gyp ERR! node-gyp -v v3.5.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/nodejs /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/usr/lib/node_modules/<EMAIL_ADDRESS>--module_name=profiler --module_path=/usr/lib/node_modules/<EMAIL_ADDRESS>(1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/@sematext/logagent-nodejs-monitor/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:106:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:192:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:890:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
node-pre-gyp ERR! System Linux 3.13.0-108-generic
node-pre-gyp ERR! command "/usr/bin/nodejs"<EMAIL_ADDRESS>"install" "--fallback-to-build"
node-pre-gyp ERR! cwd /usr/lib/node_modules/@sematext/logagent-nodejs-monitor/node_modules/@risingstack/v8-profiler
node-pre-gyp ERR! node -v v7.5.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.33
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/nodejs /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/usr/lib/node_modules/<EMAIL_ADDRESS>--module_name=profiler --module_path=/usr/lib/node_modules/<EMAIL_ADDRESS>(1)
/usr/lib
└── (empty)

npm ERR! Linux 3.13.0-108-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "i" "-g" "@sematext/logagent-nodejs-monitor"
npm ERR! node v7.5.0
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the @risingstack/v8-profiler package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs @risingstack/v8-profiler
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls @risingstack/v8-profiler
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/npm-debug.log

Hi, the issue has been resolved in https://github.com/node-inspector/v8-profiler/pull/106 , is it ok to close this pr?


failure to run main.py

Successfully install the env and build.spec... is there something i miss out in the readME.md?
Im using ubuntu 20.04
python Main.py
Traceback (most recent call last):
File "Main.py", line 27, in
from speech_translate.Globals import app_icon, app_icon_missing, app_name, fJson, gClass
File "/home/mraway/Desktop/src/Speech-Translate/speech_translate/Globals.py", line 16, in
from .utils.Json import SettingJsonHandler
File "/home/mraway/Desktop/src/Speech-Translate/speech_translate/utils/Json.py", line 7, in
from speech_translate.components.MBox import Mbox
File "/home/mraway/Desktop/src/Speech-Translate/speech_translate/components/MBox.py", line 10, in
def Mbox(title: str, text: str, style: Literal[0, 1, 2, 3], parent: Tk | None = None):
TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'

hmm  You are using python 3.8.5 and it seems that | operator is added in python 3.10.
I will add add that to the requirements.

Let me know if it's still not working, thanks for the issue that you submitted :D

Hi Thanks! the updates work for linux now. Do you happen to know if i can batch upload multiple files and process it together?

Hi Thanks! the updates work for linux now. Do you happen to know if i can batch upload multiple files and process it together?

That's one of the feature that is gonna be implemented for this app, but I'm a little busy now so it might take a while. You can post it on issue as a feature request if you want @MRAWAY77


data never accepts objects array

<SelectDropdown
                  data={[{item: 'asd', value: 'asd'}, {item: 'asd', value: 'asd'}]}
                  onSelect={(selectedItem, index) => {
                    console.log(selectedItem, index)
                  }}
                  buttonTextAfterSelection={(selectedItem, index) => {
                    // text represented after item is selected
                    // if data array is an array of objects then return
                    // selectedItem.property to render after item is selected
                    console.log('selectedItem', selectedItem)
                    return selectedItem.value
                  }}
                  rowTextForSelection={(item, index) => {
                    // text represented for each item in dropdown
                    // if data array is an array of objects then return item.property to represent item in dropdown
                    console.log('item', item.value)

                    return item
                  }}
                />

Show error
Document said I can use objects array to data but there is no mention which the form of object (What kind of key I should use?)

It accepts an array of objects, try to use examples in the example folder, and which version do you use?

It accepts an array of objects, try to use examples in the example folder, and which version do you use?

Let's say I have an array of object where one of the property is id, would it be possible to have the property id as the main thing to consider while choosing the value. At the moment it has to consider all the properties of the item in the list


Fix descendant selector

Given a node like:

a selector like .find(".test div") or .find("div div") unexpectedly matches the outer div, as well as the inner div.
The patch uses child nodes of current matches, which excludes the 'parent' match.

@ljharb Ah, I see. I'm glad for the workaround, thanks!
...But, this doesn't match CSS behaviour. Is this a 'breaking change' meaning:

do-not-accept; docs need updating to clarify descendant selectors do not work as expected, or
accept-later; but it will need to be rolled into a version bump?

the docs currently just say:

enzyme also gives support for the following contextual [css] selectors .foo .bar .foo input

Thanks.

It already doesn't match CSS behavior because there's both host nodes and Component instances in the tree :-)
It's a breaking change meaning, I don't think it's worth accepting it at this time - and I don't think it'd be an improvement.
As for .find(".test div"), can you share your actual component and test code?

Ah, I see. I'll close this PR and open one to update the docs then.
The component was mapping pseudo-markdown so it could be styled easier:
export default class Section extends React.Component {
    renderLine(line, index) {
        switch (line.slice(0, 2)) {
            case "# ":
                return <div key={`${index}`} className={"heading"}>{line.slice(2)}

            default:
                return <div key={`${index}`} className={"paragraph"}>{line}

        }
    }

    render() {
        return (

                {this.props.lines.map(this.renderLine)}

        )
    }
}

The test was:
it("should display the expected number of results", () => {
    const LINES = [ "# Hello world", "Hello world" ]
    const component = shallow(
)
    expect(component.find(".section div").length).toEqual(LINES.length)
})

which I expected to return the inner divs generated by the .map(, but also returned the outer div.
(I could have used .children().length, but I had been successfully using .find("foo bar") elsewhere in the tests so I used it again for consistency. Now I know it is broken, I'll stop using them elsewhere as well, and use chaining in stead)

As discussed in #1700 , there is a bug here, but it needs updating to handle both host-nodes and components first. Next step is a test case to define that behaviour.

@ReactiveRaven any update on updating the test cases?

@ljharb hey sorry, just realised I posted it in #1700 but didn’t make it clear here:

If you can describe/provide a test case for the intended behaviour when working with non-host-nodes, I'll happily get that PR fixed up.

So, I need from you an example situation that you are concerned about this change breaking.

(and now from the correct account)
@ljharb Hey sorry, just realised I posted it in #1700 but didn't make it clear here:

If you can describe/provide a test case for the intended behaviour when working with non-host-nodes, I'll happily get that PR fixed up.

So, I need from you an example situation that you are concerned about this change breaking. Then I can turn that into the test case and make sure nothing breaks.

ahhh thanks for clarifying. In this case, I suspect if you rebase your branch, existing tests will fail if it's indeed breaking.

@ljharb Rebase completed! Test & lint passes locally; the two failures on travis were:

a timeout with no explanation 🙁
complaining of a missing TS definition in lodash (flatten, which was already used in that file before my changes)

So I triggered a rerun, and got:

a timeout with no explanation, but on a different one this time (mysterious!)
the same lodash complaint.

So I rm -rf node_modules; npm installed and tried again, and it looks like some dev-dependencies were removed from the package.json; I found react and react-dom weren't installed, which caused npm run lint to complain. Once I ran npm install --save-dev react react-dom, it works again locally. It seems like something odd is going on with dependencies, maybe that is why it is flagging flatten?
Can you shed any light?

Good news: Now the only failure is a timeout! 🎉 Using the right remote really helps.
Bad news: I'm worried the test command might not be running all the tests? The last successful push shows only three tests, and <25% branch coverage - locally, I tried editing a test to deliberately make it fail (lengthOf(3) -> lengthOf(3000)) and the tests still passed.
I took a look, and it looks like a describe.only has snuck in!

Looks like this has already been reported in #1741. When I manually apply the fix from that PR, all tests pass, so I guess this PR is blocked on #1741 for now.

That's now merged, and I've rebased this one.

@ljharb Thanks! Looks like you have better luck with timeouts, we have a green tick :)
Did you still want to add an extra test to be super sure it works right?

OK sure. Can you describe what that test should look like?

@ReactiveRaven i think just something that's not selecting on just html - ie like div Foo span

Thanks; I've tweaked the test a bit; will merge once it passes.

Hello! 👋
We had some tests that were broken by this change. I can see why this was packaged as a patch release, but it is functionally a breaking change.
I think ideally the way this should have been handled is:

written passing tests for this unintended behaviour
documented as an unintended behaviour
delayed the API change to 4.0

However it's not a big deal.

@tvararu if the standard for “breaking” is “made any previously passing tests fail” then a huge class of bugs wouldn’t be able to be fixed. In this case, the tests that failed never should have passed in the first place, and it was a bug that they did.

@ljharb I want to avoid a debate about the meaning of SEMVER and bugs vs features in software.
The fact is that the API changed in a way that is not backwards compatible. It doesn't matter if this was to address an existing bug / an incorrectly documented API; it just is.
For what it's worth, jQuery did the same thing by doing a patch release for a backwards incompatible bug fix in one of its functions. That function was being used in that specific incorrect way in the jquery-tabs library, and it ended up breaking the GOV.UK bank holiday page. There's a relevant GitHub issue thread about this on the jQuery project but I can't find it.
Those are my full thoughts on this issue; I believe that in perspective the impact of this change is quite a lot smaller, and I'm not looking for someone else to blame for why our builds were broken for 2 hours. I was simply suggesting how I think this would have been handled if SEMVER was indeed followed to the letter.
All the best. :)

It definitely matters; because you’re invoking the meaning of semver if you’re claiming it’s a breaking change.
Semver is very fuzzy, it does not have a “letter” here - and if it did, the documented api of our selectors was broken, and this fixes it, making it objectively a patch. That it broke your build is actually irrelevant to semver.

@tvararu Hi!  SemVer refers only to the 'public API', which for Enzyme is defined in the documentation (semver 2.0.0 item 1). The implementation is distinct from the public API, which allows for 'bug fixes' to update incorrect behavior in the implementation (item 6) as long as it does not change the public API. It is not a major change, because the public API has not changed (item 8). In this case, if your project broke as a result of this change, it was depending on an internal implementation detail (in this case, a 🐛, like ljharb says), not the public API as defined by Enzyme's documentation.
The easiest way to avoid this in future would be to note when a feature of a project diverges from the stated public API, immediately raise an issue/ticket (or subscribe to/vote on existing ones), then not use that feature in your project so you avoid writing code that depends on a bug.
Anyway. Thank you for the excuse to go refresh myself on SemVer, and congrats on the new, more correct, test suite. All the best :)

That it broke your build is actually irrelevant to semver.

@ljharb this is true, but nobody likes having their stuff broken, regardless of the issue.
@ReactiveRaven your explanation makes perfect sense. Thank you!

The easiest way to avoid this in future would be to note when a feature of a project diverges from the stated public API, immediately raise an issue/ticket (or subscribe to/vote on existing ones), then not use that feature in your project so you avoid writing code that depends on a bug.

I agree. The reason this didn't happen in this particular situation was that the original code actually contained a typo:
// What was written
component.find('.class .another-class');

// What was intended
component.find('.class.another-class');

So we didn't realise we were relying on a bug. Went unnoticed for months before this.
I take back and my comment about "SEMVER being followed to the letter."
Genuinely all the best and carry on the good open sourcing. 👌

To be quite honest, we had one or two tests inside @airbnb that suffered from that exact same bug, that this update helped us catch 😌


Add equivalences from CX to CPhase+U and CRZ+U

Summary
Adds CX equivalences to fix issue #6906
Details and comments
None

Do you mind having a look @kdk ?

It also seems that you have to readjust test.python.transpiler.test_basis_translator.TestBasisExamples.test_cx_bell_to_ecr.

This is likely uncovering an issue that needs to be fixed within the BasisTranslator. The new rules are allowing it to find a faster-to-find but ultimately worse decomposition of cx in terms of ecr (the pass as written currently always prefers the fastest translation it can find). I'll take a look at updating the weightings used in the search.

Thanks for the comment @kdk.
Then, should I just worry about creating a new test for the added feature and the release note?

Then, should I just worry about creating a new test for the added feature and the release note?

That'd be great! I'll take care of looking into the needed changes in the BasisTranslator.

While doing the test for the features I added, I encountered something strange in https://github.com/Qiskit/qiskit-terra/blob/685622de76b1b9074f41f6a674e1bc15af8c3c3c/test/python/transpiler/test_basis_translator.py#L768-L769
As you can see, a QuantumRegister is created but not added to the circuit. This wouldn't be a problem if when adding gates the register is not referenced, but it is: https://github.com/Qiskit/qiskit-terra/blob/685622de76b1b9074f41f6a674e1bc15af8c3c3c/test/python/transpiler/test_basis_translator.py#L770-L773
Changing line 769 to expected = QuantumCircuit(qr) does not fix the test issue, but I thought it was worth noting.

Good catch, that is a latent bug in the test, but agree this isn't likely to be the cause of the BasisTranslator failure. (Currently, QuantumCircuit(2) implicitly creates a QuantumRegister(2) behind the scenes and adds it to the circuit, so these are functionally equivalent, but this behavior is slated to be deprecated in the future.)

I think the only thing missing is the issue @kdk mentioned about BasisTranslator.

We recently merged a pretty big change in the search algorithm used by the BasisTranslator in #7211. It's probably worth rebasing this and testing to see if we're still having issues now.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 83.721%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
53024

Relevant Lines:
63334

💛  - Coveralls

Thanks @mtreinish!
Seems like it is somewhat working now. Linux, Windows, and MacOS tests passed in 1f26cee while Docs and Lint failed, but Linux and Lint are now failing in de0f5fc while the other pass although I only added some comments. From the pipeline, I see that there was problem while installing Qiskit dependencies: ERROR: Could not build wheels for qiskit-terra, which is required to install pyproject.toml-based projects. How can I fix this?
Also, I've added the comments illustrating the equivalent circuits for the cx equivalences I added, but I'm missing to add the global phase difference between the normal gate and the equivalence, is there some Qiskit function that can help me compute this phase?

It looks it was a temporary networking blip that caused the CI jobs to fail. It failed to download some rust dependency packages during the build. Let me retrigger CI on the failed jobs to retry them

Awesome! @epelaaez Thanks for your quick response for making the changes and made the PR into Terra 0.20!


PLAT-143809 Added UI tests for Alert.

Checklist

[X] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[X] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Alert had no UI tests.
Resolution
Created UI tests for Alert.
Additional Considerations
Links
PLAT-143809
Comments

LGTM


New Python Wrapper

Apache StreamPipes
Apache StreamPipes (incubating) is a self-service (Industrial) IoT toolbox to enable non-technical users to connect, analyze and explore IoT data streams. StreamPipes offers several modules including StreamPipes Connect to easily connect data from industrial IoT sources, the Pipeline Editor to quickly create processing pipelines and several visualization modules for live and historic data exploration. Under the hood, StreamPipes utilizes an event-driven microservice paradigm of standalone, so-called analytics microservices making the system easy to extend for individual needs.

Background
Current wrappers such as standalone (JVM, Siddhi) or distributed (Flink) already allow to develop new processors in the given runtime environment. The idea is to extend the list of standalone runtime wrappers to also support pure Python processors. We already got a minimal working version that however is pretty inflexible and still relies on Java as a proxy to the pipeline management in the backend service for the model declaration in the setup phase ( capabilities, requirements, static properties of a processor) as well as the actual invocation in the execution phase ( receiving specific configuration from pipeline management when pipeline is started). This issue is to track the status of the development.

Tasks

Add API endpoints as an interface for registration/invocation ( partly done)
Port relevant model classes over to Python (declaration **** invocation descriptions)
Implement support for various transport protocols and transport formats
Implement dev friendly alternative to Java builder pattern for model declaration
Implement overall runtime logic for Python wrapper

Relevant Skills

Don't be afraid! We'll guide you through your first steps with StreamPipes.

Excellent Python skills
Excellent understanding of stream processing paradigm incl.  message broker such as Kafka, MQTT, etc
Good Understanding of RESTful web services (HTTP, etc.)
Basic Java skills to understand existing wrapper logic

Info

SIP-02 to collect design decisions https://cwiki.apache.org/confluence/display/STREAMPIPES/SIP-02Pythonwrapper
Current python runtime wrapper implementation: https://github.com/apache/incubator-streampipes/tree/dev/streampipes-wrapper-python
POC example: https://github.com/apache/incubator-streampipes-examples/tree/dev/streampipes-pipeline-elements-examples-processors-jvm/src/main/java/org/apache/streampipes/pe/examples/jvm/python

Mentor
Patrick Wiener, PPMC Apache StreamPipes<EMAIL_ADDRESS>Imported from Jira STREAMPIPES-174. Original Jira may contain additional context.
Reported by: wiener.

The following subtask(s) are associated with this issue: #366, #367, #368, #369, #370, #371, #372, #373


Floodlight is unable to recognize the switch and connect to Mininet

Describe the bug
Upon running the Floodlight controller, and attempting to connect it to a Mininet-wifi instance, there are failures as the FL controller is unable to recognize the switch provided in the Mininet instance despite explicit definition.
The CLI command for Mininet succeeds in integrating almost all of the time.
The CLI command for Mininet-wifi succeeds in integrating both 50% of the time.
The script defined to connect both fails 100% of the time.
CLI Command,
sudo mn --wifi --switch=ovsk,protocols=OpenFlow13 \
	--controller=remote,ip=<IP_ADDRESS>,port=6653

Script,
#!/usr/bin/python

from mininet.net import Mininet
from mininet.node import Controller, OVSKernelSwitch, RemoteController
from mininet.link import TCLink
from mininet.cli import CLI
from mininet.log import setLogLevel, info

import subprocess

def emptyNet(controller_ip, controller_port):
	net = Mininet(controller=RemoteController, build=False)
	c1 = net.addController('c1', controller=RemoteController, link=TCLink, switch=OVSKernelSwitch, ip=controller_ip, port=controller_port)
	h1 = net.addHost('h1', ip='<IP_ADDRESS>')
	h2 = net.addHost('h1', ip='<IP_ADDRESS>')
	s1 = net.addSwitch('s1', protocols=["OpenFlow15"])

	net.addLink(s1, c1)
	net.addLink(s1, h1)
	net.addLink(s1, h2)

	net.build()
	c1.start()
	s1.start([c1])

	net.start()
	net.staticArp()
	CLI(net)
	net.stop()

def getControllerIP():
	guest_ip = subprocess.check_output("/sbin/ifconfig enp0s3 | grep 'inet' | cut -d: -f2 | awk '{print $2}'", shell=True)
	split_ip = guest_ip.decode('utf8').strip().split('.')
	return '.'.join(split_ip)

if __name__ == "__main__":
	setLogLevel('info')
	controller_ip = getControllerIP()
	emptyNet(controller_ip, 6653)

To Reproduce
Steps to reproduce the behavior:

Copy the script into the local environment.
Run the floodlight controller, and run the script using,

sudo python script.py

Test the pingall command to see it fail, and check the logs of the FL controller.
Notice that the switch is not recognized and a connection is not established.

Expected behavior
The mininet switch and the controller should be able to establish a connection with one another, and the pingall command should work successfully.
Screenshots
CLI-run mininet instance,

Script-run mininet instance,

There has been no recognition of the switch, and it goes back to LLDP packet detection afterward.
Desktop:
Floodlight Version [master]
OS: [Lubuntu]
Mininet-Wifi VM

Additional context
I am currently attempting this in a Mininetwifi-VM, whose VM image can be found here.
Another issue that I faced which causes the 50% failure rate in Mininet-wifi is the following, I wonder if I should raise another issue for this or whether it relates to this issue.

This may not be an issue of the Mininet instance being at fault, but more of the station being unable to detect the AP that it's supposed to associate itself too. Closing this issue.