[BugFix] Support non slotref exprs for partition_by_exprs

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
https://github.com/StarRocks/StarRocksBenchmark/issues/230
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/planner/RuntimeFilterDescription.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/planner/ExchangeNode.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/planner/RuntimeFilterDescription.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/planner/ExchangeNode.java
1
1
100.00%
[]

Add some test case?

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_be_unittest

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_be_unittest

run starrocks_be_unittest

run starrocks_be_unittest

run starrocks_be_unittest

run starrocks_be_unittest

rerun starrocks_be_unittest

starrocks_be_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/planner/RuntimeFilterDescription.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/planner/ExchangeNode.java
1
1
100.00%
[]


Upgrade to 1.32

f577f0f is the commit to pin guava to 31.1-jre, otherwise, other commits are from apache/calcite.


pip not giving any feedback on wsl and not working

Version
[Version 10.0.19044.1586]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.4.72
Distro Version
Ubuntu 20.04
Other Software
visual studio code 1.65.2
Repro Steps
pip install dnspython
or
sudo pip install dnspython
or try to install any other modules with pip (even if the module do not exist)
pip install [anything]
Expected Behavior
shows some errors or show the progress of the modules being installed
Actual Behavior
it doesn't show anything, after 5 minutes i just stopped the execution with CTRL+C and that's the output(every time is the same output, no matter how many minutes )

^CTraceback (most recent call last):
  File "/usr/bin/pip", line 11, in <module>
    load_entry_point('pip==20.0.2', 'console_scripts', 'pip')()
  File "/usr/lib/python3/dist-packages/pip/_internal/cli/main.py", line 73, in main
    command = create_command(cmd_name, isolated=("--isolated" in cmd_args))
  File "/usr/lib/python3/dist-packages/pip/_internal/commands/__init__.py", line 96, in create_command
    module = importlib.import_module(module_path)
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 848, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/pip/_internal/commands/install.py", line 24, in <module>
    from pip._internal.cli.req_command import RequirementCommand
  File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", line 19, in <module>
    from pip._internal.network.session import PipSession
  File "/usr/lib/python3/dist-packages/pip/_internal/network/session.py", line 26, in <module>
    from pip._internal.network.auth import MultiDomainBasicAuth
  File "/usr/lib/python3/dist-packages/pip/_internal/network/auth.py", line 36, in <module>
    import keyring  # noqa
  File "/usr/lib/python3/dist-packages/keyring/__init__.py", line 3, in <module>
    from .core import (
  File "/usr/lib/python3/dist-packages/keyring/core.py", line 189, in <module>
    init_backend()
  File "/usr/lib/python3/dist-packages/keyring/core.py", line 93, in init_backend
    keyrings = filter(limit, backend.get_all_keyring())
  File "/usr/lib/python3/dist-packages/keyring/util/__init__.py", line 21, in wrapper
    func.always_returns = func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/keyring/backend.py", line 210, in get_all_keyring
    return list(rings)
  File "/usr/lib/python3/dist-packages/keyring/util/__init__.py", line 31, in suppress_exceptions
    for callable in callables:
  File "/usr/lib/python3/dist-packages/keyring/util/properties.py", line 26, in __get__
    return self.fget.__get__(None, owner)()
  File "/usr/lib/python3/dist-packages/keyring/backend.py", line 67, in viable
    cls.priority
  File "/usr/lib/python3/dist-packages/keyring/util/properties.py", line 26, in __get__
    return self.fget.__get__(None, owner)()
  File "/usr/lib/python3/dist-packages/keyring/backends/kwallet.py", line 37, in priority
    bus = dbus.SessionBus(mainloop=DBusGMainLoop())
  File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 212, in __new__
    return Bus.__new__(cls, Bus.TYPE_SESSION, private=private,
  File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 102, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 124, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
  File "/usr/lib/python3/dist-packages/dbus/exceptions.py", line 47, in __init__
    def __init__(self, *args, **kwargs):
KeyboardInterrupt

@mariobros2 don't cancel it, just let it run. On my WSL2 Ubuntu it took longer than 5 min for the command to start executing. Can't say why. On the same WSL2 setup when using Arch pip runs immediately.

@mariobros2 don't cancel it, just let it run. On my WSL2 Ubuntu it took longer than 5 min for the command to start executing. Can't say why. On the same WSL2 setup when using Arch pip runs immediately.

omg, thank you very much, i waited almost 10 minutes, but then it worked!!!

I am still having the same issue, same distro, latest Win 10. Yes, waiting "worked", but the delay is present after each following call, including feedback for errors. It's not just some weird "warm up" for the first call.

I found the solution somebody has found: it's the usage of an X-server.
https://github.com/pypa/pip/issues/9061
I have used XLaunch, too.
Run this in the WSL console:
export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0
Then pip returns quickly.


Fix db deadlock

PR Description
We have onTransactionClosed callback which is synchronized (and should) and called on every transaction close, so it was clashing with general close method. Making single snapshot of transactions and iterators and operating with it out of synchronized looks safe as DB is marked as closed in the beginning and new transactions shouldn't be added. Actually I think it's safe to remove synchronized from db.close() too.
Fixed Issue(s)

Fixes #4867
Documentation

[x] I thought about documentation and added the documentation label to this PR if updates are required.

Changelog

[x] I thought about adding a changelog entry, and added one if I deemed necessary.

@ajsutton you haven't answered whether we remove sync on db.close(), I've removed and did several test runs, looks ok, and from the code I think there shouldn't be any clashing. I'd keep test because store locks are not rare.
Could you confirm code without sync block on db.close()?

Yep removing the synchronized around db.close is safe. Sorry, forgot that question.


Add "clear" image

Once uploaded, no way to remove image

[ ] add "clear" button to remove image selection

Implemented


Don't include empty valence handlers

Description
The System.from_smirnoff method will in cases create empty handlers if a molecule has no slots of a given type that need to be filled but the force field contains parameters for that slot type. An example of this is formaldehyde which does not contain any proper dihedrals, but the resulting System object contains an empty SMIRNOFFProperTorsionHandler.
This is mainly just a minor nuisance factor and I don't feel too strongly either way about keeping the empty handlers or not.

I think this has been resolved; please re-open if that is not the case.


Per-process cpu usage

I'm able to get a list of the pids/parent pids/etc for each process, but I was wondering if there was also a way to get the CPU % that each pid is using.

No, not at the moment, so I had created the #106 issue to track missing parts.
Is there anything else you need except for cpu percentage? There is a lot to implement, so at least we could prioritize some tasks.

CPU usage the main one, though it'd be nice to then later add other usage stats like memory usage.

Closed in 060a131e7311b5421695f326f188907b9cb2cdb1


project doesn't build on Xcode7 / ios9

I wasn't able to get the examples to work on ios 9 with xcode7..
I created a fork and got it to work here: https://github.com/edwardvalentini/meteor-ios/tree/xcode7
I was going to submit a PR but don't want to do it on your master branch...  let me know if you want to create an xcode7 branch and merge it in there.

Thanks! I haven't been able to spend much time on this project lately, but I plan to give it some love again around the time Xcode 7 is released (which should be soon I think).
I need to look into some other issues as well, such as the project organization (to make sure things work with both CocoaPods and Carthage) and OS X support. I've also made some changes to the utility code included with the examples as part of an app, so I think for my own understanding I prefer to do the conversion to Xcode 7/Swift 2 myself.
But in the meantime, it's great people running Xcode 7 beta can use your fork!


Rechunk Pressure level data in lat lon dataset

I have been using the latlon dataset here gs://gcp-public-data-arco-era5/ar/full_37-1h-0p25deg-chunk-1.zarr-v3. It has been extremely helpful for setting up different projects. I am wondering if it would be possible to rechunk the pressure level data. Currently all pressure levels are in a single chunk. If we want to sub sample we will end up getting the entire chunk which can significantly slow down the bandwidth. Ideally given this is in object storage we could use much smaller chunk sizes and just have the chunks be the lat long grid. What do you thinks?

This is a lot of data, so I don't think we're going to store another duplicate version of this dataset. But there are a number of tools for rechunking the data yourself, e.g., see rechunker or xarray-beam

I have a similar issue. If I am only interested into a region of the world and a subset of the data, I would have to download 1PB for only a few hundred megabyte. I do not thinks that is the idea.
So there is not possibility to download only a subset of the remote chunk? We have always to download the full chunk and than rechunk local?


Add keccak in stdlib

Related issue(s)
Resolves #1189
Description
Summary of changes
Adds Keccak in stdlib and handle Keccak intrinsic function.
Dependency additions / changes
Needs a bunch of PR to be merge and versions to be updated before this can be tested:
https://github.com/noir-lang/acvm/pull/247
https://github.com/noir-lang/aztec_backend/pull/150
https://github.com/AztecProtocol/barretenberg/pull/393
Test additions / changes
I will add an integration test once the above PR are published.
Checklist

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt with default settings.
[X] I have linked this PR to the issue(s) that it resolves.
[X] I have reviewed the changes on GitHub, line by line.
[X] I have ensured all changes are covered in the description.

Documentation needs

[X] This PR requires documentation updates when merged.

New Keccak function in the stdlib.

This can be tested by updating the Cargo.toml file on https://github.com/noir-lang/aztec_backend/pull/150 to point to the head commit of https://github.com/noir-lang/acvm/pull/247 and then updating this PR to use the updated backend commit.
As an example of this see https://github.com/noir-lang/noir/pull/1226/files/d79b7f3a737940a9528753a05e1ed4d530397064

Waiting for https://github.com/noir-lang/aztec_backend/pull/164 to merge so we can avoid the memory leak


Add Cypress testing tool (and write tests)

Describe the new a11y feature or project enhancement
This would be a project enhancement: adding a testing tool. Right now, all the checks to verify that the new change didn't affect anything already in place have to be done manually. This is error-prone (it's easy to miss something) and unsustainable in the long run, when many tests are reached.
Describe the solution you'd like
My suggestion would be adding Cypress as the testing tool. Cypress is simple and easy, and as a test, I was able to get something up and running in 10 minutes:

It will help run all the tests in an automated way, without missing anything. For each new feature, the developer would be in charge of writing the test for their feature and verify that the rest are still Ok (e.g. just run the tests and make sure all of them pass.)
Link(s)

Cypress website
Cypress documentation

Ohhh...this would be really cool! I'd be more than happy to contribute as well!

This sounds really good! I have zero experience with Cypress 😅

@tricinel If you want, I could push what I have –I added some tests and a couple of functions to be able to read ::before and ::after styles– and you can continue or we can divide the work. I don't know if the structure I have is the best; it works, but it would need some review.

Yeah, that'd be cool! I don't have that much experience with Cypress either - I'm looking forward to learning though. @alvaromontoro let's continue on your work if that's alright. 👍


Custom Call-ID on Outgoing Invite

It'd be great if we can specify a custom call-id instead of SIP.js generating a random string.
I put this request in over 5 years ago and since have had to hack in this feature into every release and Id really like to stop hacking in this feature.
Sometimes we want to track custom call-ids based on a distributed back-end generating the ids and a client-side library generating the ids is not gonna cut it.
Any thoughts?

// Create a user agent client to establish a session
        const inviter = new Inviter(userAgent, target, {
          sessionDescriptionHandlerOptions: {
            constraints: { audio: true, video: false },
            remote: { audio: this.getAudioElement(this.audioId) },
          }
          ,
          params : {
            callId: customCallId,
          },
        });

Solved with this code.


ESI::Base extended options and include_completed for industry

Hi,
This pull request is based on #125 with the ESI::Base extented for supporting include_completed option.
If ok for you, I merge this PR with #125 .
The interested parts are https://github.com/biow0lf/eve_online/commit/725c8200d1eab2a4bdd053eb896c68ad090519c8 and https://github.com/biow0lf/eve_online/commit/a451b181bf4bdc3cbb9552f4aa2d6d85c9bed14e.
@+
Meka

Few notes:

Rename lib/eve_online/esi/models/industry_jobs.rb to lib/eve_online/esi/models/industry_job.rb. For consistency.

Rename EveOnline::ESI::CorporationIndustryJob to EveOnline:: ESI::CorporationIndustryJobs (with file)

Rename EveOnline::ESI::CharacterIndustryJob to EveOnline::ESI:: CharacterIndustryJobs (with file)

Rationale: Character has many jobs.

Remove:

options.each do |k,v|
  instance_variable_set("@#{k}", v) unless v.nil?
end

As I see, this is unneeded this case.

@include_completed = "false" if options[:include_completed].nil? I think, this is not good, but ok for now. I will think about this later.

Extend examples:

job.activity_id # => 5
job.blueprint_id # =><PHONE_NUMBER>103

And so for all other fields in json.

Update CHANGELOG
Add yourself to Contributors section in README.md.

Ping

Pong ;-)
I was off this last days (business travel). I'll be working on it this week-end.
@+
Meka

Humm, if I delete this part of code 👍
options.each do |k,v|
  instance_variable_set("@#{k}", v) unless v.nil?
end

The variable don't seem to be initialized ;-(
options = { corporation_id: 98146630, token: "1234", include_completed: "true" }
# => {:corporation_id=>98146630, :token=>"1234", :include_completed=>"true"}
corporation_jobs = EveOnline::ESI::CorporationIndustryJobs.new(options)
# => #<EveOnline::ESI::CorporationIndustryJobs:0x007fffece51de0 @corporation_id=98146630, @parser=JSON, @token="1234">
[4] pry(main)> corporation_jobs.url
# => "https://esi.tech.ccp.is/v1/corporations/98146630/industry/jobs/?datasource=tranquility&include_completed="

So, ok. I merged. I have few comments for this code, but I will write it in issues.
Also, welcome on a board. I add you as collaborator to this repo. Welcome! :)


Readme format

I formatted the line properly so it has consistency with the [mp3 ur]l one :3

Fantastic contribution! Thank you for your work.


Feature/protoproc

Codecov Report

Merging #31 (2d148af) into main (454a977) will increase coverage by 1.70%.
The diff coverage is 83.53%.

@@            Coverage Diff             @@
##             main      #31      +/-   ##
==========================================
+ Coverage   89.97%   91.68%   +1.70%
==========================================
  Files          33       33
  Lines        1826     1875      +49
==========================================
+ Hits         1643     1719      +76
+ Misses        151      117      -34
- Partials       32       39       +7

Impacted Files
Coverage Δ

mizugos/entitys/module.go
100.00% <ø> (ø)

mizugos/errors/error.go
100.00% <ø> (ø)

mizugos/procs/stack.go
77.16% <77.16%> (ø)

mizugos/procs/proto.go
80.76% <80.76%> (ø)

mizugos/procs/json.go
87.14% <87.14%> (ø)

mizugos/entitys/entity.go
87.21% <92.85%> (+2.36%)
:arrow_up:

mizugos/events/eventmgr.go
97.33% <100.00%> (+0.55%)
:arrow_up:

mizugos/logs/empty.go
100.00% <100.00%> (ø)

mizugos/logs/zap.go
96.90% <100.00%> (-0.02%)
:arrow_down:

mizugos/metrics/metricsmgr.go
100.00% <100.00%> (ø)

... and 2 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Problems with Disconnected/Restricted Network Mirroring Steps

The disconnected/restricted mirroring steps appear to be a mix of OCP and OKD documentation:
https://docs.okd.io/latest/installing/installing-mirroring-installation-images.html#installation-mirror-repository_installing-mirroring-installation-images
For example, it tells the reader to view both:
https://access.redhat.com/downloads/content/290/
and
https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags
to determine an OCP_RELEASE tag (i.e., 4.5.4).
From experience, I know that OCP_RELEASE is looking for the full tag (i.e.,: 4.7.0-0.okd-2021-09-19-013247).
I use an online VM to [1] mirror the images for a release to a directory, I transfer it to a VM in a restricted network with both docker and a registry:2 running and [2] upload the images to the local docker registry running:
[1]
oc adm release mirror -a ${LOCAL_SECRET_JSON} --to-dir=${REMOVABLE_MEDIA_PATH}/mirror quay.io/${PRODUCT_REPO}/${RELEASE_NAME}:${OCP_RELEASE}
[2]
oc image mirror -a ${LOCAL_SECRET_JSON} --from-dir=${REMOVABLE_MEDIA_PATH}/mirror "file://openshift/release:${OCP_RELEASE}*" ${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}
After this, I see the docker registry contents in the persistent volume mount to the registry:2 docker registry container.
My install-config.yaml also has the imageContentSources block so it can use my mirror instead of quay.io.
Bootstrap node is complaining about manifests being unknown:
ERRO[1831] response completed with error auth.user.name=admin err.code="manifest unknown" err.detail="unknown manifest name=okd4 revision=sha256:dbf65<snip>34209" err.message="manifest unknown" ... response.status=404
I've done this process with the past 3 Release Tags - I'm also aware that the first release of 4.8.0 will not work because of v2/s2 Digest errors: https://github.com/openshift/okd/discussions/904#discussioncomment-1420766
I'm not sure the proper procedure to mirror without running into manifest issues. Is there something I'm doing wrong in the mirroring process?
Thank you

also hitting this


Add overflow-free mulDiv method for all types

Triplet of a * b / c integer operations may overflow. So will be great have u128.mulDiv operation which avoid overflow in multiplication part.

Need some real tests for #49
cc @willemneal

Need some real tests for #49
cc @willemneal


Docker 24.0.7 is being flagged for CVE-2023-44487

docker:24.0.7 is being flagged for CVE-2023-44487 (https://security.snyk.io/vuln?search=CVE-2023-44487)
INFO[0000] Scanning Image: docker:24.0.7  Scan SessionID: 93cd28e6-8965-4bb2-a67f-50abac57581c

Vulnerabilities
===============
  CVE               Severity    CVSS    Package Name              Package Version    Fixed In Version    Description
  ---               --------    ----    ------------              ---------------    ----------------    -----------
  CVE-2023-44487    high        7.5     google.golang.org/grpc    v1.50.1            1.56.3              https://security.snyk.io/vuln?search=CVE-2023-44487
  CVE-2023-44487    high        7.5     golang.org/x/net/http2    v0.14.0            0.17.0              https://security.snyk.io/vuln?search=CVE-2023-44487
  CVE-2023-44487    high        7.5     golang.org/x/net/http2    v0.8.0             0.17.0              https://security.snyk.io/vuln?search=CVE-2023-44487
  CVE-2023-44487    high        7.5     google.golang.org/grpc    v1.53.0            1.56.3              https://security.snyk.io/vuln?search=CVE-2023-44487

Image Scan Results
==================
  Image Name:    docker:24.0.7
  ImageID:       sha256:5b912308540a3c49177b012c400f71cbb53ff56c4ee79f36323fdff7527f9f44
  Digest:        docker@sha256:1dfc375736e448806602211e09a9b1390eb110548dcb839eef374da357ca5f5d

  Certification:   silver
  Image Published: false

  Vulnerability
    Critical: 0
    High:     4
    Medium:   0
    Low:      0
    Total:    4

I'm hoping a patched version can be pushed soon to remediate these vulnerabilities :-)

Upvote for this one.  Also getting flagged with this in our build pipelines.

This comes from the docker-buildx cli plugin binary.
https://github.com/docker-library/docker/blob/bfe953e38b9610b085d1e0f139dbe2c39556216b/24/cli/Dockerfile#L58-L102
Since this image just packages the releases of docker/buildx, there is not much we can do unless they make a new release (or maybe they know that they are not vulnerable).
There is a related open discussion: https://github.com/docker/buildx/discussions/2081, but there was also a dismissed dependabot bump with the library fix https://github.com/docker/buildx/pull/2097 so maybe they've already evaluated whether or not the CVE applies to their usage of google.golang.org/grpc.

Seeing these additional vulnerabilities. Are these from buildx?
CVE-2023-47108 -
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
g.org/grpc/otelgrpc
CVE-2023-45142 -
go.opentelemetry.io/contrib/instrumentation/github.com/emicklei/go-restful/otelrestful
go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin
go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux
go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho
go.opentelemetry.io/contrib/instrumentation/gopkg.in/macaron.v1/otelmacaron
go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace
go.opentelemetry.io/contrib/instrumentation/net/http/otel
CVE-2023-48795 -
golang.org/x/crypto
GHSA-7ww5-4wqc-m92c -
github.com/containerd/containerd

@yosifkit  Could you answer above question so that I can check with buildx?

That seems like a better question for whichever tool gave you that list, right? :sweat_smile:

That seems like a better question for whichever tool gave you that list, right? 😅

Its showing on your site for your image
https://hub.docker.com/layers/library/docker/24.0.7-dind/images/sha256-c7ddea2dbae3870b02cb025bd05cef854903e2eb0b38ce798311bdc818af4200?context=explore

Ah, Scout has the data, but doesn't show it there (yet? not sure if that's something that team is working on - we're not part of that team)
If you check https://dso.docker.com/images/docker/digests/sha256:c7ddea2dbae3870b02cb025bd05cef854903e2eb0b38ce798311bdc818af4200, it's got more, especially which file each match comes from.

The opentelemewtry are not just in buildx. They are in compose and dockerd

The opentelemetry are not just in buildx. They are in compose and dockerd

Is dockerd from moby project https://github.com/moby/moby?

Yes, dockerd is the "Moby Engine" (built from https://github.com/moby/moby/tree/master/cmd/dockerd)

https://github.com/moby/moby/issues/47246

Closing since there isn't anything we can do in the image if/until there are published updates.
Follow along in https://github.com/moby/moby/issues/47246, https://github.com/docker/buildx/pull/2221 or similar issues; though they all seem unexploitable anyway (or require privileged access): https://github.com/moby/moby/issues/47246#issuecomment-1916844668, https://github.com/docker/buildx/pull/2221#issuecomment-1923741651.


Allow fetching all packages from the SBOM

As we don't seem to have an "describing packages", refactor the function to allow retrieving all packages.

The idea is to have "all packages in the context of the SBOM". Unrelated to any relationships. The idea is browse through the SBOM content.
I am also working on the next function, which does: give me related packages (in the context of an sbom). Then again, those two functions seem related. So my next try is to make them one, at least on the service level. Using:
pub enum Which {
    /// All packages of the SBOM
    All,
    /// Top level packages of the SBOM (with no relationshhip
    TopLevel,
    /// Search relationships, given the left side and an optional relationship type
    Left(Purl, Option<Relationship>),
    /// Search relationships, given the right side and an optional relationship type
    Right(Purl, Option<Relationship>),
}

That could also get a DescribesSbom variant. then again, that would go into a completely different table. Let's see.

All packages within an SBOM should only be there because the SBOM either describes them or they are related to a described package, I think yeah?
Assuming we ingest all of that (we may be missing tables/etc) then grabbing left/right of relationships, and everything described, and unique-ing it shoud but... good?

All packages within an SBOM should only be there because the SBOM either describes them or they are related to a described package, I think yeah?

I don't think so. To my understanding "document describes" was an extension, that also wasn't well documented. It is not a requirement.
Searching for all packages in the quarkus SBOM, which don't have any relationship, I now get:

{
    "items": [
        {
            "purl": "pkg://maven/com.redhat.quarkus.platform/quarkus-bom@3.2.11.Final-redhat-00001?repository_url=https://maven.repository.redhat.com/ga/&type=pom"
        }
    ],
    "total": 1
}

Which feels correct. Taking a look at the "document describes" part, there is nothing. Still, that SBOM has a valid package, named pkg://maven/com.redhat.quarkus.platform/quarkus-bom@3.2.11.Final-redhat-00001?repository_url=https://maven.repository.redhat.com/ga/&type=pom, which has a relationship to all the others. That sounds good.

I updated the PR to allow searching for: root level packages (as described above), all packages (belonging to the sbom) … as well as searching for relationships inside the sbom.
Unifying the search packages and search relationships calls doesn't seem possible. Mainly because they actually return different data. In the context of relationships, it returns the relationship type too. And making the return format depending on the input search arguments feels wrong.

Also see: https://github.com/spdx/spdx-spec/issues/395 … It's still not really clear to me: https://spdx.github.io/spdx-spec/v2.3/relationships-between-SPDX-elements/


Mashery

Since the H1 report it's no longer possible to take over the domain.

Mashery no longer lets trial users add custom domains. I believe a paid user can though.

Starting at $1995/month

Addressed in #15 and #16 (one for title and one for long description).

Resolved via #54

These do appear to be vulnerable now with a paid account. Although Mashery seeks account approval manually, once the account is paid this does not include any sort of company verification (such as a company e-mail, or A record).

Any update on this?

Is there any update on this issue?


Spotify API Inconsistency: Integer Values Returned as Floats Without Documentation Update

We've observed a recent and undocumented change in Spotify's API behavior, specifically regarding the data type of certain values that were traditionally returned as integers. This alteration is gradually being implemented across various endpoints, with a notable example being the tracks endpoint. Previously, values such as "duration_ms" would be returned as integers (e.g., "duration_ms": 2345). However, we are now receiving these values as floats (e.g., "duration_ms": 2345.0), despite the official web API reference still indicating that integers are to be expected.
This discrepancy has been confirmed to affect multiple endpoints and is causing issues for applications with strict type requirements, where floats are not expected in places where integers were previously provided. As a result, typed applications that rely on these integer values are experiencing breaks in functionality.
A discussion thread exists on the Spotify Developer Forums highlighting this issue, but responses and clarifications from Spotify have been minimal: Spotify Developer Forums Thread.
As a temporary workaround, I have modified all applicable properties in my application from type int to float and performed a cast back to int where necessary (I'm still on a very old version of SpotifyAPI-NET but I guess this affects the latest version too). Checking the latest code it seems like the models for the API response are still typed and thus this issue will also arise in the current release. Models. While this approach has resolved the issue for my application and benefitted my users, it is not an ideal or sustainable solution.
The staggered rollout of these API changes has further complicated diagnosis and troubleshooting, especially since the effects were not immediately evident across all user bases.
I am raising this issue here so others know what's up, if they encounter Newtonsoft.Json.JsonReaderException.
Discussed in https://github.com/JohnnyCrazy/SpotifyAPI-NET/discussions/925

Originally posted by rogamaral January  5, 2024
Since yesterday and suddenly, without any changes to the code, I started to have the following exception:
Newtonsoft.Json.JsonReaderException:
'Input string '359120.0' is not a valid integer.
Path 'followers.total',
line 1, position 127.'
var artist = await _spotify.Artists.Get(artistId);
Does anyone else also have this problem?
Thanks.

This issue seems to be happening to multiple developers, including myself, and has been discussed previously in #925, #926 and #928. For me, it randomly stopped happening after few days.

This issue seems to be happening to multiple developers, including myself, and has been discussed previously in #925, #926 and #928. For me, it randomly stopped happening after few days.

I'm aware that this was discussed. I raised the issue out of #925 to further spread awareness for it.
The Newtonsoft.JSON Deserializer should convert int to double if int is returned from the API and double is expected. Thats why the approach of changing the types might work long term.

Well I should read all the discussions beforehand. It seems the Serializer has been modified to convert.
My bad!

Hi @Inzaniity,
I'm also experiencing the JsonReaderException on some properties, for instance album.total_tracks. Updating to the latest SpotifyAPI.Web (7.1.1) did not fix them all.
If I add the DoubleToIntConverter attribute to the properties that still cause the exceptions it's ok again.
So it seems to me we should add the DoubleToIntConverter attribute to all int properties so it doesn't break when Spotify decides to return doubles/floats somewhere. What do you think?

Hi @Inzaniity, I'm also experiencing the JsonReaderException on some properties, for instance album.total_tracks. Updating to the latest SpotifyAPI.Web (7.1.1) did not fix them all.
If I add the DoubleToIntConverter attribute to the properties that still cause the exceptions it's ok again.
So it seems to me we should add the DoubleToIntConverter attribute to all int properties so it doesn't break when Spotify decides to return doubles/floats somewhere. What do you think?

I mean that is what I did but on an older code base. So yeah, converting all expected ints seems to be the solution here.

A Spotify developer confirmed a fix for this in the discussion on the Spotify developer forum

An optimization in the deserialization of JSON in upstream was causing the serializer to default to double types for integer values. The optimization was not applied to all queries, and several tools were sanitizing the response which was the reason we did not uncover this from the start.


Implement --diff for Jupyter Notebooks

Summary
Implement --diff for Jupyter Notebooks
Test Plan

Use crates/ruff/resources/test/fixtures/jupyter/isort.ipynb as a test case
and add a markdown cell in between the code cells to check that the diff
outputs the correct cell index.
Run the command:
cargo run --bin ruff --package ruff_cli -- check --no-cache --isolated --select=ALL crates/ruff/resources/test/fixtures/jupyter/isort.ipynb --fix --diff

Example output:

--- /Users/dhruv/playground/ruff/notebooks/test.ipynb:cell 0
+++ /Users/dhruv/playground/ruff/notebooks/test.ipynb:cell 0
@@ -1,3 +0,0 @@
-from pathlib import Path
-import random
-import math

--- /Users/dhruv/playground/ruff/notebooks/test.ipynb:cell 2
+++ /Users/dhruv/playground/ruff/notebooks/test.ipynb:cell 2
@@ -1,5 +1,3 @@
-from typing import Any
-import collections
 # Newline should be added here
 def foo():
     pass

Would fix 5 errors.

resolves: #4727

Current dependencies on/for this PR:

main

PR #6149   👈

This comment was auto-generated by Graphite.

Oh, I need to avoid adding newlines if the cells are not changed otherwise there'll be blank lines for each unchanged cells.


[webpack-isomorphic-tools] [error] asset not found

It's strange. I remove webpack-asset.json, then do a fresh build with webpack, I can get  webpack-asset.json correctly.
{
  "javascript": {
    "app": "/static/js/app.js",
    "vendor": "/static/js/vendor.js"
  },
  "styles": {
    "app": "/static/css/app.css",
    "vendor": "/static/css/vendor.css"
  },
  "assets": {
    "../~/font-awesome/fonts/fontawesome-webfont.eot": "/static/fonts/fontawesome-webfont.eot",
    "../~/react-toolbox/lib/app_bar/theme.scss": {
      "appBar": "theme-appBar___3WmWk",
      "flat": "theme-flat___1W35s",
      "fixed": "theme-fixed___20COC",
      "title": "theme-title___yKUyv",
      "leftIcon": "theme-leftIcon___2TQQz",
      "rightIcon": "theme-rightIcon___30ltD",
     ...
   }
}

But when I change source code, then webpack-dev-server trigger recompiling, webpack-assets.json will be incorrect.
{
  "javascript": {
    "app": "/static/js/app.js",
    "vendor": "/static/js/vendor.js"
  },
  "styles": {
    "app": "/static/css/app.css",
    "vendor": "/static/css/vendor.css"
  },
  "assets": {}
}

How can I solve this problem?

Enable debug: true in your settings and post full console output.

The fresh build. webpack-assets.json is correct
[webpack-isomorphic-tools/plugin] [debug] running write assets webpack plugin v2.5.8 with options {
  "development": true,
  "debug": true,
  "assets": {
    "images": {
      "extensions": [
        "jpeg",
        "jpg",
        "png",
        "gif"
      ]
    },
    "fonts": {
      "extensions": [
        "woff",
        "woff2",
        "ttf",
        "eot"
      ]
    },
    "svg": {
      "extensions": [
        "svg"
      ]
    },
    "bootstrap": {
      "include": [
        "./src/theme/bootstrap.config.js"
      ],
      "extensions": [
        "js"
      ]
    },
    "style_modules": {
      "extensions": [
        "css",
        "less",
        "scss",
        "sass"
      ]
    }
  },
  "project_path": "/work/koapp/src",
  "assets_base_url": "/static/",
  "webpack_assets_path": "/work/koapp/storage/tmp/webpack-assets.json",
  "webpack_stats_path": "/work/koapp/storage/tmp/webpack-stats.json",
  "output": {
    "javascript": {},
    "styles": {},
    "assets": {}
  },
  "output_to_a_file": true,
  "regular_expressions": {
    "images": {},
    "fonts": {},
    "svg": {},
    "bootstrap": {},
    "style_modules": {}
  }
}
[webpack-isomorphic-tools/plugin] [debug]  (development mode is on)
[webpack-isomorphic-tools/plugin] [debug] writing webpack stats to /work/koapp/storage/tmp/webpack-st
ats.json
[webpack-isomorphic-tools/plugin] [debug] getting javascript and styles for chunk "app"
[webpack-isomorphic-tools/plugin] [debug]  (got javascript)
[webpack-isomorphic-tools/plugin] [debug]  (got style)
[webpack-isomorphic-tools/plugin] [debug] getting javascript and styles for chunk "vendor"
[webpack-isomorphic-tools/plugin] [debug]  (got javascript)
[webpack-isomorphic-tools/plugin] [debug]  (got style)
[webpack-isomorphic-tools/plugin] [debug] No filter specified for "images" assets. Using a default on
e.
[webpack-isomorphic-tools/plugin] [debug] No path parser specified for "images" assets. Using a defau
lt one.
[webpack-isomorphic-tools/plugin] [debug] parsing assets of type "images"
[webpack-isomorphic-tools/plugin] [debug]  time taken: 1 ms
[webpack-isomorphic-tools/plugin] [debug] No filter specified for "fonts" assets. Using a default one
.
[webpack-isomorphic-tools/plugin] [debug] No path parser specified for "fonts" assets. Using a defaul
t one.
[webpack-isomorphic-tools/plugin] [debug] parsing assets of type "fonts"
[webpack-isomorphic-tools/plugin] [trace] Adding asset "../~/font-awesome/fonts/fontawesome-webfont.e
ot", module id 742 (in webpack-stats.json)
[webpack-isomorphic-tools/plugin] [debug]  time taken: 1 ms
[webpack-isomorphic-tools/plugin] [debug] No filter specified for "svg" assets. Using a default one.
[webpack-isomorphic-tools/plugin] [debug] No path parser specified for "svg" assets. Using a default
one.
[webpack-isomorphic-tools/plugin] [debug] parsing assets of type "svg"
[webpack-isomorphic-tools/plugin] [debug]  time taken: 0 ms
[webpack-isomorphic-tools/plugin] [debug] parsing assets of type "bootstrap"
[webpack-isomorphic-tools/plugin] [debug]  time taken: 1 ms
[webpack-isomorphic-tools/plugin] [debug] parsing assets of type "style_modules"
[webpack-isomorphic-tools/plugin] [trace] Adding asset "../~/react-toolbox/lib/app_bar/theme.scss", m
odule id 497 (in webpack-stats.json)
[webpack-isomorphic-tools/plugin] [trace] Adding asset "../~/font-awesome/css/font-awesome.min.css",
module id 740 (in webpack-stats.json)
[webpack-isomorphic-tools/plugin] [debug]  time taken: 2 ms
[webpack-isomorphic-tools/plugin] [debug] compiling assets
[webpack-isomorphic-tools/plugin] [debug] compiling asset "../~/font-awesome/fonts/fontawesome-webfon
t.eot"
[webpack-isomorphic-tools/plugin] [debug] require()ing "/work/koapp/~/font-awesome/fonts/fontawesome-
webfont.eot"
[webpack-isomorphic-tools/plugin] [debug]  found in parsed assets
[webpack-isomorphic-tools/plugin] [debug] compiling asset "../~/react-toolbox/lib/app_bar/theme.scss"
[webpack-isomorphic-tools/plugin] [debug] require()ing "/work/koapp/~/react-toolbox/lib/app_bar/theme
.scss"
[webpack-isomorphic-tools/plugin] [debug]  found in parsed assets
[webpack-isomorphic-tools/plugin] [debug] require()ing "./../../../css-loader/lib/css-base.js"
[webpack-isomorphic-tools/plugin] [debug]  not found in parsed assets, searching in webpack stats
[webpack-isomorphic-tools/plugin] [debug]  found in webpack stats, module id 498
[webpack-isomorphic-tools/plugin] [debug] compiling asset "../~/font-awesome/css/font-awesome.min.css
"
[webpack-isomorphic-tools/plugin] [debug] require()ing "/work/koapp/~/font-awesome/css/font-awesome.m
in.css"
[webpack-isomorphic-tools/plugin] [debug]  found in parsed assets
[webpack-isomorphic-tools/plugin] [debug] require()ing "./../../css-loader/lib/css-base.js"
[webpack-isomorphic-tools/plugin] [debug]  not found in parsed assets, searching in webpack stats
[webpack-isomorphic-tools/plugin] [debug]  found in webpack stats, module id 498
[webpack-isomorphic-tools/plugin] [debug] require()ing "../fonts/fontawesome-webfont.eot?v=4.6.3"
[webpack-isomorphic-tools/plugin] [debug]  not found in parsed assets, searching in webpack stats
[webpack-isomorphic-tools/plugin] [debug]  found in webpack stats, module id 741
[webpack-isomorphic-tools/plugin] [debug] require()ing "../fonts/fontawesome-webfont.eot"
[webpack-isomorphic-tools/plugin] [debug]  not found in parsed assets, searching in webpack stats
[webpack-isomorphic-tools/plugin] [debug]  found in webpack stats, module id 742
[webpack-isomorphic-tools/plugin] [debug] require()ing "../fonts/fontawesome-webfont.woff2?v=4.6.3"
[webpack-isomorphic-tools/plugin] [debug]  not found in parsed assets, searching in webpack stats
[webpack-isomorphic-tools/plugin] [debug]  found in webpack stats, module id 743
[webpack-isomorphic-tools/plugin] [debug] require()ing "../fonts/fontawesome-webfont.woff?v=4.6.3"
[webpack-isomorphic-tools/plugin] [debug]  not found in parsed assets, searching in webpack stats
[webpack-isomorphic-tools/plugin] [debug]  found in webpack stats, module id 744
[webpack-isomorphic-tools/plugin] [debug] require()ing "../fonts/fontawesome-webfont.ttf?v=4.6.3"
[webpack-isomorphic-tools/plugin] [debug]  not found in parsed assets, searching in webpack stats
[webpack-isomorphic-tools/plugin] [debug]  found in webpack stats, module id 745
[webpack-isomorphic-tools/plugin] [debug] require()ing "../fonts/fontawesome-webfont.svg?v=4.6.3"
[webpack-isomorphic-tools/plugin] [debug]  not found in parsed assets, searching in webpack stats
[webpack-isomorphic-tools/plugin] [debug]  found in webpack stats, module id 746
[webpack-isomorphic-tools/plugin] [debug]  time taken: 53 ms
[webpack-isomorphic-tools/plugin] [debug] writing webpack assets info to /work/koapp/storage/tmp/webp
ack-assets.json
[webpack-isomorphic-tools/plugin] [debug] ------------------- Finished -------------------

Recompile, webpack-assets.json is incorrect
webpack: bundle is now INVALID.                                                             [70/1936]
 95% emit[webpack-isomorphic-tools/plugin] [debug] ------------------- Started -------------------
[webpack-isomorphic-tools/plugin] [debug] running write assets webpack plugin v2.5.8 with options {
  "development": true,
  "debug": true,
  "assets": {
    "images": {
      "extensions": [
        "jpeg",
        "jpg",
        "png",
        "gif"
      ]
    },
    "fonts": {
      "extensions": [
        "woff",
        "woff2",
        "ttf",
        "eot"
      ]
    },
    "svg": {
      "extensions": [
        "svg"
      ]
    },
    "bootstrap": {
      "include": [
        "./src/theme/bootstrap.config.js"
      ],
      "extensions": [
        "js"
      ]
    },
    "style_modules": {
      "extensions": [
        "css",
        "less",
        "scss",
        "sass"
      ]
    }
  },
  "project_path": "/work/koapp/src",
  "assets_base_url": "/static/",
  "webpack_assets_path": "/work/koapp/storage/tmp/webpack-assets.json",
  "webpack_stats_path": "/work/koapp/storage/tmp/webpack-stats.json",
  "output": {
    "javascript": {},
    "styles": {},
    "assets": {}
  },
  "output_to_a_file": true,
  "regular_expressions": {
    "images": {},
    "fonts": {},
    "svg": {},
    "bootstrap": {},
    "style_modules": {}
  }
}
[webpack-isomorphic-tools/plugin] [debug]  (development mode is on)
[webpack-isomorphic-tools/plugin] [debug] writing webpack stats to /work/koapp/storage/tmp/webpack-st
ats.json
[webpack-isomorphic-tools/plugin] [debug] getting javascript and styles for chunk "app"
[webpack-isomorphic-tools/plugin] [debug]  (got javascript)
[webpack-isomorphic-tools/plugin] [debug]  (got style)
[webpack-isomorphic-tools/plugin] [debug] getting javascript and styles for chunk "vendor"
[webpack-isomorphic-tools/plugin] [debug]  (got javascript)
[webpack-isomorphic-tools/plugin] [debug]  (got style)
[webpack-isomorphic-tools/plugin] [debug] No filter specified for "images" assets. Using a default on
e.
[webpack-isomorphic-tools/plugin] [debug] No path parser specified for "images" assets. Using a defau
lt one.
[webpack-isomorphic-tools/plugin] [debug] parsing assets of type "images"
[webpack-isomorphic-tools/plugin] [debug]  time taken: 0 ms
[webpack-isomorphic-tools/plugin] [debug] No filter specified for "fonts" assets. Using a default one
.
[webpack-isomorphic-tools/plugin] [debug] No path parser specified for "fonts" assets. Using a defaul
t one.
[webpack-isomorphic-tools/plugin] [debug] parsing assets of type "fonts"
[webpack-isomorphic-tools/plugin] [debug]  time taken: 1 ms
[webpack-isomorphic-tools/plugin] [debug] No filter specified for "svg" assets. Using a default one.
[webpack-isomorphic-tools/plugin] [debug] No path parser specified for "svg" assets. Using a default
one.
[webpack-isomorphic-tools/plugin] [debug] parsing assets of type "svg"
[webpack-isomorphic-tools/plugin] [debug]  time taken: 0 ms
[webpack-isomorphic-tools/plugin] [debug] parsing assets of type "bootstrap"
[webpack-isomorphic-tools/plugin] [debug]  time taken: 0 ms
[webpack-isomorphic-tools/plugin] [debug] parsing assets of type "style_modules"
[webpack-isomorphic-tools/plugin] [debug]  time taken: 0 ms
[webpack-isomorphic-tools/plugin] [debug] compiling assets
[webpack-isomorphic-tools/plugin] [debug]  time taken: 0 ms
[webpack-isomorphic-tools/plugin] [debug] writing webpack assets info to /work/koapp/storage/tmp/webpack-assets.json
[webpack-isomorphic-tools/plugin] [debug] ------------------- Finished -------------------

Thank you for your quickly reply!

Well, I don't know.
In a subsequent build it doesn't find any style_modules inside webpack-stats.json and so it outputs no styles.
Why is that so - that's a webpack question.
webpack-stats.json are written from a Webpack plugin.

the module ../~/react-toolbox/lib/app_bar/theme.scss missing in webpack-assets.json, it can always be found inwebpack-stats.json
    {
      "id": 496,
      "identifier": "/work/koapp/node_modules/extract-text-webpack-plugin/loader.js?{\"omit\":1,\"extract\":true,\"remove\":true}!/work/koapp/node_modules/style-loader/index.js!/work/koapp/node_modules/css-loader/index.js?sourceMap&modules&importLoaders=1&localIdentName=[name]-[local]___[hash:base64:5]!/work/koapp/node_modules/postcss-loader/index.js!/work/koapp/node_modules/sass-loader/index.js!/work/koapp/node_modules/react-toolbox/lib/app_bar/theme.scss",
      "name": "../~/react-toolbox/lib/app_bar/theme.scss",
      "index": 496,
      "index2": 490,
      "size": 255,
      "cacheable": true,
      "built": false,
      "optional": false,
      "prefetched": false,
      "chunks": [
        0
      ],
      "assets": [],
      "issuer": "/work/koapp/node_modules/react-toolbox/lib/app_bar/index.js",
      "failed": false,
      "errors": 0,
      "warnings": 0,
      "reasons": [
        {
          "moduleId": 487,
          "moduleIdentifier": "/work/koapp/node_modules/react-toolbox/lib/app_bar/index.js",
          "module": "../~/react-toolbox/lib/app_bar/index.js",
          "moduleName": "../~/react-toolbox/lib/app_bar/index.js",
          "type": "cjs require",
          "userRequest": "./theme.scss",
          "loc": "18:13-36"
        }
      ],
      "source": "// removed by extract-text-webpack-plugin\nmodule.exports = {\"appBar\":\"theme-appBar___3WmWk\",\"flat\":\"theme-flat___1W35s\",\"fixed\":\"theme-fixed___20COC\",\"title\":\"theme-title___yKUyv\",\"leftIcon\":\"theme-leftIcon___2TQQz\",\"rightIcon\":\"theme-rightIcon___30ltD\"};"
    }

Post your configuration for webpack-isomorphic-tools

Yes, here is my configuration.
var WebpackIsomorphicToolsPlugin = require('webpack-isomorphic-tools/plugin');

// see this link for more info on what all of this means
// https://github.com/halt-hammerzeit/webpack-isomorphic-tools
module.exports = {

  // when adding "js" extension to asset types
  // and then enabling debug mode, it may cause a weird error:
  //
  // [0] npm run start-prod exited with code 1
  // Sending SIGTERM to other processes..
  //
  debug: true,
  webpack_assets_file_path: '../storage/tmp/webpack-assets.json',
  webpack_stats_file_path: '../storage/tmp/webpack-stats.json',
  assets: {
    images: {
      extensions: [
        'jpeg',
        'jpg',
        'png',
        'gif'
      ],
      parser: WebpackIsomorphicToolsPlugin.url_loader_parser
    },
    fonts: {
      extensions: [
        'woff',
        'woff2',
        'ttf',
        'eot'
      ],
      parser: WebpackIsomorphicToolsPlugin.url_loader_parser
    },
    svg: {
      extension: 'svg',
      parser: WebpackIsomorphicToolsPlugin.url_loader_parser
    },
    // this whole "bootstrap" asset type is only used once in development mode.
    // the only place it's used is the Html.js file
    // where a <style/> tag is created with the contents of the
    // './src/theme/bootstrap.config.js' file.
    // (the aforementioned <style/> tag can reduce the white flash
    //  when refreshing page in development mode)
    //
    // hooking into 'js' extension require()s isn't the best solution
    // and I'm leaving this comment here in case anyone finds a better idea.
    bootstrap: {
      extension: 'js',
      include: ['./src/theme/bootstrap.config.js'],
      filter: function(module, regex, options, log) {
        function is_bootstrap_style(name) {
          return name.indexOf('./src/theme/bootstrap.config.js') >= 0;
        }
        if (options.development) {
          return is_bootstrap_style(module.name) && WebpackIsomorphicToolsPlugin.style_loader_filter(module, regex, options, log);
        }
        // no need for it in production mode
      },
      // in development mode there's webpack "style-loader",
      // so the module.name is not equal to module.name
      path: WebpackIsomorphicToolsPlugin.style_loader_path_extractor,
      parser: WebpackIsomorphicToolsPlugin.css_loader_parser
    },
    style_modules: {
      extensions: ['css', 'less', 'scss', 'sass'],
      filter: function(module, regex, options, log) {
        if (options.development) {
          // in development mode there's webpack "style-loader",
          // so the module.name is not equal to module.name
          return WebpackIsomorphicToolsPlugin.style_loader_filter(module, regex, options, log);
        } else {
          // in production mode there's no webpack "style-loader",
          // so the module.name will be equal to the asset path
          return regex.test(module.name);
        }
      },
      path: function(module, options, log) {
        if (options.development) {
          // in development mode there's webpack "style-loader",
          // so the module.name is not equal to module.name
          return WebpackIsomorphicToolsPlugin.style_loader_path_extractor(module, options, log);
        } else {
          // in production mode there's no webpack "style-loader",
          // so the module.name will be equal to the asset path
          return module.name;
        }
      },
      parser: function(module, options, log) {
        if (options.development) {
          return WebpackIsomorphicToolsPlugin.css_modules_loader_parser(module, options, log);
        } else {
          // in production mode there's Extract Text Loader which extracts CSS text away
          return module.source;
        }
      }
    }
  }
}

"name": "../~/react-toolbox/lib/app_bar/theme.scss",

This is not the module it's looking for.
filter looks for another module:
https://github.com/halt-hammerzeit/webpack-isomorphic-tools/blob/master/source/plugin/plugin.js#L224
This is the filter for css-loader
I don't know why in your webpack-stats.json you have the CSS in a module with another name.


Including tests in the main cargo [workspace] and as a result, the main Cargo.lock file.

cc @adlerjohn we briefly discussed this in https://github.com/FuelLabs/sway/pull/1497 but I think we need to make a choice about this for the repo more generally.
Current Situation
Currently, we have three separate sets of tests:

The main E2E tests - https://github.com/FuelLabs/sway/tree/master/test/src/e2e_vm_tests
The separate lib-std tests - https://github.com/FuelLabs/sway/tree/master/test/src/sdk-harness
The examples/ test harnesses (coming soon #1321)

The main E2E tests are included in the main workspace and as a result are locked alongside the rest of the workspace. The lib-std tests however have a totally independent workspace and do not include a Cargo.lock file. The examples/ test harnesses will likely land soon, and we need to make a decision on what the right approach is.
We should decide on one consistent approach across all of our testing and update either the E2E harness or the lib-std tests to follow suit.
Why we currently omit Cargo.lock in lib-std tests
The reason we don't currently lock the lib-std tests or the examples/ test harnesses and why we do not include them in the main workspace is that we do not want to miss patch releases from the fuels, fuel-* and all other dependency crates (see #1497 discussion).
The idea behind this is that it makes our testing process closer to the actual user experience of using the test harness crates in newly generated projects. E.g. If fuels publishes a patch release that unintentionally breaks sway projects, then by not locking our tests there is a chance that we would catch this by CI mysteriously breaking in an unrelated PR or on master before it makes it to users. On the other hand if our tests are locked, it's possible that we would miss bugs/breakage that make it through upstream testing in patch releases.
At the core of this reasoning is the fact that Rust provides no way to enforce the correct use of its "semver" feature in crates. E.g. while a patch release should never break publicly exposed APIs or publicly observable side-effects, it is entirely up to the maintainer of each crate to uphold this guarantee. It's unrealistic to rely on this fuzzy notion of "patch" release when we have 500+ dependencies across the sway repo.
The problems with omitting Cargo.lock
Non-deterministic testing
By not including a Cargo.lock for tests, it means that every time we open a PR or merge a PR into master we invite the possibility of hitting unrelated/mysterious bugs caused by breakage in the patch releases of our dependencies. Without a Cargo.lock, CI will always retrieve the latest patch release for every one of the ~500 deps. Devs will need to either 1. run cargo update -p <test-packages> and run the tests before pushing to CI, or just hope that CI will pass with latest deps and that deps won't get updates between opening the PR and when it lands in master.
The same problem arises when a reviewer pulls down the changes and runs the tests locally. Depending on the last time they updated their Cargo.lock, they may or may not see a whole different set of errors that may be caused by older or newer dependencies.
Longer build times and artifact bloat
Having separate workspaces greatly bloats the number of build artifacts across the repo. It means that despite sharing something like 80% of dependencies with the main workspace, all of the dependencies in the lib-std tests need to be built a second time - once for the main workspace, and again for the lib-std test workspace.
In #1321 we aim include a test harness for each of the examples. If the examples/ each have their own test harness and we still wish to omit them from the main workspace, we will then either need to build all of these dependencies yet again per example, or once for all examples if we create a nested workspace under the examples/ directory. This means that we end up with a third copy of most of the build artifacts in the one repo and all the time it takes to build the extra aftifacts.
The CI rust cache helps to mitigate long build times for many cases during CI, but if anything is touched within those workspaces (which it often is during development) then we will need to endure the full, tripled build times. Today, our lib-std CI job already jumps between 8min and ~27 mins depending on the last commit on the PR. The larger bloat and longer build times are also something devs will need to endure locally regardless.
It doesn't guarantee catching breakage anyway
Not having a Cargo.lock file does not mean we will definitely catch breakage in patch releases. If we anticipate having 1000s+ active forc projects in the wild, then a broken patch release from fuels, fuel-* or some other dependency will almost certainly hit a user before one of our devs happens to open or merge a PR that hits the unrelated bug.
Removing determinism from our testing and potentially tripling our build-times/bloat is a messy solution and beats-around-the-bush of the real issue, which is that we do not trust patch releases in our users' test harness crate dependencies.
Possible Solutions
1. Pin to patch release
We could possibly pin the [dependencies] within the generated test harness manifest to a particular patch release. E.g. rather than specifying fuels = "0.11", we would specify fuels = "=0.11.0". While this would pin the top-level dependencies, this would not fix the issue for all dependencies of dependencies.
2. Include the Cargo.lock for the generated test harnesses
This would mean all of the test harness dependencies would be pinned to a known, working state. However, it's not clear to me how to extract the parts of the workspace lock file that are specific to the test harness without re-generating one, and if we have to regenerate one each time then we're back to square one. We would need to investigate if there is some tool out there for moving a locked crate out of a workspace while keeping the same locked state for its own dependencies.
3. Trust patch releases. Fix occasional breakage.
Add everything under the main [workspace], share the main Cargo.lock file and trust that upstream maintainers generally follow the conventions for patch releases, fixing the occasional patch-release breakage when it does occur.
Accept that Rust doesn't give us tools to enforce correct semver usage and that if we're going to generate test harnesses with unpinned, minor versions specified, there will always be a chance that users' newly generated test harnesses will break due to a rogue patch release, whether or not we unlock our own tests.
4. In-language Sway Testing
#1375 would solve this in a much more complete and general way by removing the need for Rust test harnesses altogether, but needs a lot more discussion/design.

Personally I'm leaning toward the 3rd option until we one day land the 4th, and perhaps bump the priority of discussing in-lang testing. I don't think the questionable benefits of omitting the Cargo.lock file or separating tests and examples into separate workspaces justify the problems mentioned above.
I'm keen to get others thoughts on this, or to hear if anyone has a better/alternative solution.

A bit late to the party, but I'm hesitant to include SDK harness Cargo deps in the workspace. The reason being that currently sway depends on fuels-rs for SDK tests, and fuels-rs depends on forc for its own tests. This circular dependency isn't hasn't been too bad yet, but may become an issue in the future. until it's unwinded, we should avoid tightening it. (3) is the most reasonable option IMO.


working on  for login/register. Will need your support for writing unit tests

look up the subject

I will prepare an "essay" on this topic
Sunday morning

we need new SQL table
UUID | UserID
and CRUD methods

it is done now


i18n(es): Update customization

Description

What does this PR change? Give us a brief description.
Updated customization

Thank you so much @delucis & @Waxer59 for the review 😁


Fix/17164 code snipet issue on reload

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Noel Kovács seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Not moving past Welcome screen despite being synced 100% and funded

Hi Guys,
I have installed the Zap desktop software, created a wallet, waited for it to sync and funded(transaction confirmed (35+ times) the Address in the screenshot.
But it doesnt move past the welcome screen. I cant do anything.
Am I doing something wrong?

Am I doing something wrong?

Zap version: 0.7.2
Operating System and version: Windows 10

Thanks for helping!

Apparently the address changed when I deleted and restored the wallet, but I am a 100% certain I send some btc to the correct wallet, as I scanned QR code to send BTC to it. I'm not sure how to move to the next screen now.

Apparently the address changed when I deleted and restored the wallet, but I am a 100% certain I send some btc to the correct wallet, as I scanned QR code to send BTC to it. I'm not sure how to move to the next screen now.

I have also recovered on macOS Mojave using the seed, and there all seems to be okay.
The other system I tried was a fresh install of windows 10, and there it didn’t move past the welcome screen.

I have also recovered on macOS Mojave using the seed, and there all seems to be okay.
The other system I tried was a fresh install of windows 10, and there it didn’t move past the welcome screen.

It happened to me as well a few times. Not sure why exactly this happens. Normally restarting Zap helps. Sometimes it requires a few tries.

It happened to me as well a few times. Not sure why exactly this happens. Normally restarting Zap helps. Sometimes it requires a few tries.

Same thing happened to me. I just let it sit, and about an hour later, a message appeared that the blockchain had synched and then my wallet finally came up with my correct balance.


Image retrieval / similarity

Thanks for this great resource.

I am wondering whether this approach could be used for image retrieval / image similarity?
Have you looked into it?

@johnyquest7 hey Johnson! yea absolutely! It works like any other neural net. You can take the embedding (usually the output at the very last attention layer) https://github.com/lucidrains/vit-pytorch/blob/main/vit_pytorch/vit_pytorch.py#L113 and use your favorite nearest neighbor library (for example, Faiss https://github.com/facebookresearch/faiss) and you've got yourself retrieval

I found this question, but I do not want to open a new issue. @lucidrains  For the retrieval, shouldn't we take the output of the last attention layer, but more specifically, the class-token output?
    x = self.transformer(x, mask)
    x = x[:, 0]        <- these are the embeddings we are interesed in


[Sema] Do not attempt openning same generic argument twice while checking default parameter

Use the already opened type variable for same generic argument instead of attempting to open it twice.

Resolves https://github.com/apple/swift/issues/61061

@swift-ci please test

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test macOS platform


Changed the order view to something more nice

Changed the order view to something a little bit more "intuitive". The buttons are now styled more nicely, the interface now has two columns on desktop view and the alerts are more specific.

I think the 'back to overview' button should be fully centered

What about a back to shift overview button in the footer? And then a "order items" button in the footer of the shift overview.

What about a back to shift overview button in the footer? And then a "order items" button in the footer of the shift overview.

Then I would say add some breadcrumbs on top and include the button there. The footer should only be for admins in my opinion (but breadcrumbs might be nice, that always works when page structure is unclear)

Hmm, could you make a mock-up, I'm not sure what you mean.

I'm just going to center the button, we can look at breadcrumbs later.


Maybe this can be of help

I noticed you're getting Nim to run on a STM32.  Here's how I did it.  Notice that I used a different svd-to-nim tool, so my syntax to r/w registers will be a little different.

Thanks Ill probably be looking at this for reference, still working my way up to compiling a binary for my target.


[material-ui][Popover] How to create a hover card using a popover?

The problem in depth
The documentation includes an example  of implementing a hover card using a popover, but it is flawed in that the card disappears when hovered over. How can it be implemented so that it remains visible?
export const HoverCard = ({ children }: HoverCardProps) => {
    const [anchorEl, setAnchorEl] = useState<null | HTMLDivElement>(null);

    const handleMouseEnter = (event: MouseEvent<HTMLDivElement>) => setAnchorEl(event.currentTarget);

    const handleMouseLeave = () => setAnchorEl(null);

    return (
        <>
            <Box onMouseEnter={handleMouseEnter} onMouseLeave={handleMouseLeave}>
                {children}
            </Box>

            <Popover
                open={Boolean(anchorEl)}
                anchorEl={anchorEl}
                sx={{
                    pointerEvents: 'none'
                }}
            >
                Content
            </Popover>
        </>
    );
};

Your environment

`npx @mui/envinfo`
  System:
    OS: Windows 11 10.0.22631
  Binaries:
    Node: 18.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.5.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.6.0 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Chromium (127.0.2651.74)
  npmPackages:
    @emotion/react: ^11.11.4 => 11.11.4
    @emotion/styled: ^11.11.5 => 11.11.5
    @mui/base:  5.0.0-beta.40
    @mui/core-downloads-tracker:  5.15.17
    @mui/icons-material: ^5.15.17 => 5.15.17
    @mui/lab: ^5.0.0-alpha.170 => 5.0.0-alpha.170
    @mui/material: ^5.15.17 => 5.15.17
    @mui/private-theming:  5.15.14
    @mui/styled-engine:  5.15.14
    @mui/system:  5.15.15
    @mui/types:  7.2.14
    @mui/utils:  5.15.14
    @mui/x-charts: ^7.3.2 => 7.3.2
    @mui/x-data-grid:  7.3.2
    @mui/x-data-grid-generator: ^6.20.0 => 6.20.0
    @mui/x-data-grid-premium:  6.20.0
    @mui/x-data-grid-pro: ^7.3.2 => 7.3.2
    @mui/x-date-pickers: ^7.4.0 => 7.4.0
    @mui/x-date-pickers-pro: ^7.4.0 => 7.4.0
    @mui/x-license:  7.2.0
    @mui/x-license-pro:  6.10.2
    @types/react: ^18.2.66 => 18.2.79
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^5.2.2 => 5.4.5

Search keywords: popover
Order ID: 89766
Search keywords:

For this advanced case, you'll need to use material-ui-popup-state, as recommended in the docs. Here's a working example: https://stackblitz.com/edit/react-pifkmh?file=Demo.tsx.
Also, the hover example text incorrectly says "using mouseover event," but it actually uses mouseenter. I'll create a PR to correct that.

I don't think it is flawed. For this advanced case, you'll need to use material-ui-popup-state, as recommended in the docs. Here's a working example: https://stackblitz.com/edit/react-pifkmh?file=Demo.tsx.
Also, the hover example text incorrectly says "using mouseover event," but it actually uses mouseenter. I'll create a PR to correct that.

What do you mean by using MouseEnter instead of MouseOver? Where did you see this? Thanks.

I don't think it is flawed. For this advanced case, you'll need to use material-ui-popup-state, as recommended in the docs. Here's a working example: https://stackblitz.com/edit/react-pifkmh?file=Demo.tsx.
Also, the hover example text incorrectly says "using mouseover event," but it actually uses mouseenter. I'll create a PR to correct that.

What do you mean by using MouseEnter instead of MouseOver? Where did you see this? Thanks.

In the demo, the hover behavior is triggered by the onMouseEnter event, not onMouseOver. The example incorrectly mentions mouseover. I’ve created PR #43290 to correct this.


added more usefull functions

added onPullStart global method
added onPullEnd global method
added a maxPullThreshold to break pull on full screen
removed unnessesery overflow-y css this isn't important and fails on some projects

check also if scroll position is not on top


Speech not working in web chat for GOV cloud due to wrong endpoint

Screenshots
Below is the screenshot of Firefox web console

Version
What version of Web Chat are you using? 4.9.2 This one
Are you using the CDN? Yes
Describe the bug
We are developing a bot hosted on Azure gov cloud and the sample web chat is working fine except the speech. When we click on the mic icon in web chat, it throws an error "Firefox can’t establish a connection to the server at wss://usgovvirginia.stt.speech.microsoft.com" which I believe is wrong/incorrect endpoint for azure gov speech resource as per this article.
Steps to reproduce

Configure the sample js Web Chat with appropriate secret and speech key.
Run the Web Chat on Firefox.
Open Firefox' web console (dev tools).
Click on mic icon to see the error in web console.

Expected behavior
Web Chat must take speech input and bot should respond accordingly.
[Bug]

Looks like you are using region instead of speechRecognitionHostname or speechSynthesisHostname for sovereign cloud.
Please follow the documentation here for specifying endpoint for sovereign cloud, https://github.com/microsoft/BotFramework-WebChat/blob/master/docs/SPEECH.md#using-sovereign-cloud.

Thanks! that helped


[bug] <Cannot read properties of undefined (reading 'toLowerCase')> Navigator undefined in getBrowser

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
2.1.2
wagmi Version
2.9.10
Current Behavior
The problem is that after migrating and following the migration guides to the 2.x rainbow wallet, and the same for wagmi and viem, I'm getting a weird problem where the navigator in the<EMAIL_ADDRESS>is not being recognized, such that the function, getBrowser() has a problem when navigator.userAgent.toLowercase() is called because navigator is an empty Object (I console.log'ed it and it showed that).
If I just return normally with an if statement checking if its empty, my code runs as functioned. But I assume you shouldn't be changing the node modules for rainbow kits. So any idea why this is happening?
So, please see the full error below:

function getBrowser() {
  if (typeof navigator === "undefined")
    return "Browser" /* Browser */;
  const ua2 = navigator.userAgent.toLowerCase();
  ...

I've attached my app.js below
import React from "react";
import { GlobalPriceProvider } from "../context/GlobalPriceContext";
import "../styles/globals.css";
import Router from 'next/router';
import { NextUIProvider } from "@nextui-org/react";
import dotenv from "dotenv";
import NProgress from 'nprogress';
import 'nprogress/nprogress.css';
import<EMAIL_ADDRESS>import { ToastContainer, toast } from 'react-toastify';
import 'react-toastify/dist/ReactToastify.css';
import { SpeedInsights } from '@vercel/speed-insights/next';
import { Analytics } from "@vercel/analytics/react";
import {
  getDefaultConfig,
  RainbowKitProvider,
  darkTheme
} from "@rainbow-me/rainbowkit";
import { WagmiProvider, http } from 'wagmi';
import { CompModalProvider } from "context/CompModalContext";
import {
  RainbowKitSiweNextAuthProvider,
} from "@rainbow-me/rainbowkit-siwe-next-auth";
import { SessionProvider } from "next-auth/react";
import { mainnet, polygon, optimism, arbitrum, base } from "wagmi/chains";
import { QueryClient, QueryClientProvider } from "@tanstack/react-query";
import Sidebar from "@/components/UI/layouts/Sidebar";
import { AccountInfoProvider } from "context/AccountInfoContext";

const config = getDefaultConfig({
  appName: 'DegenzFinance',
  projectId: "hidden",
  chains: [mainnet],
  ssr: true, // If your dApp uses server side rendering (SSR)
});

const queryClient = new QueryClient()

const Disclaimer = ({ Text, Link }) => (
  <Text>
    By connecting your wallet, you agree to the Degenz.Finance{' '}
    <Link href="/tos">Terms of Service</Link> and
    acknowledge you have read and understand the {' '}
    <Link href="/privacy">Privacy Policy</Link>. An account shall be created when you sign in.
  </Text>
);

const getSiweMessageOptions = () => ({
  statement:
    "Verify wallet ownership on Degenz.Finance. By signing, an account is created, and you agree to the Terms of Service and Privacy Policy",
});
NProgress.configure({ showSpinner: false });

Router.events.on('routeChangeStart', () => NProgress.start());
Router.events.on('routeChangeComplete', () => NProgress.done());
Router.events.on('routeChangeError', () => NProgress.done());

dotenv.config()
function App({ Component, pageProps }) {
  return (
    <>
    <SpeedInsights />
    <Analytics />
    <NextUIProvider>
    <main className="dark text-foreground bg-background">
     <WagmiProvider config={config}>
      <QueryClientProvider client={queryClient}>
        <SessionProvider refetchInterval={0} session={pageProps.session}>
          <RainbowKitSiweNextAuthProvider
            getSiweMessageOptions={getSiweMessageOptions}
          >
            <RainbowKitProvider

              modalSize="wide"
              initialChain={1}
              appInfo={{ appName: "Degenz.Finance", disclaimer: Disclaimer }}
              theme={darkTheme({
                accentColor: '#5A40FF',
                accentColorForeground: 'white',
                borderRadius: 'large',
                fontStack: 'system',
                fontWeight:"400",
                overlayBlur: 'small',
                })}
              >
              <AccountInfoProvider>
              <GlobalPriceProvider>
                <CompModalProvider>
                    <main className="flex grow bg-background">
                        <Component {...pageProps} />
                    </main>
                    <ToastContainer
                      autoClose={2000}
                      theme="dark"
                      position="top-left"
                      pauseOnHover={false}
                    />

                </CompModalProvider>
              </GlobalPriceProvider>
              </AccountInfoProvider>
            </RainbowKitProvider>
          </RainbowKitSiweNextAuthProvider>
        </SessionProvider>
      </QueryClientProvider>
    </WagmiProvider>
    </main>
    </NextUIProvider>
    </>
  );
}

export default App;

@0xAskar What browser are you using ? Can you share a small reproducible example ?

@magiziz I used both Firefox and Chrome. I can perhaps release a reproducible example a bit later in the day. But, I don't seem to problem disrupt functionality in production, just in developing.
Would it make sense to add just error handling that ensures Navigator isn't an empty object as well. Would it be possible to update the library to have that in the getBrowser function?

@0xAskar Yeah i'll get that fixed, but it's hard for me to debug if i can't reproduce this on my end. Whenever you have time can you just link a small reproducible example here ? I can't seem to get that error in the console for some reason.

@magiziz hey mate, i just added a reproducible example by stripping down every file or component in my project and just keeping the bare mimium. the package json is mostly the same. Also, if you're going to fix it by just adding another clause in the if, could I do that lol? I have never publicly fixed a bug on an open sourced project and would love to learn how.
I don't know if there is a better way but i made a public repo, let me know if you get the problem, because i still do with this stripped down repo
https://github.com/0xAskar/RainbowKitNavBug

@0xAskar I can't seem to reproduce this locally on chrome. I only see the next-auth errors and not the navigator.userAgent error.

If you want to fix this you're welcome to open a PR, but this should be an easy fix i just can't seem to reproduce this on my end.

@magiziz Hey, so just to check my sanity, I deleted the reprod. example and recloned it, installed the libraries, and re-ran. I still get the same error. I assume this is just some local error but still pops up due to lack of error handling if the object is empty.
anyways, i created the pull request, lmk if anything needs to change and we can update it. That would make developing much easier to do, because rn i have to amend the index file within the rainbowkit modules myself

@0xAskar Thanks! I'll take a look 👍


harmonize scoring based on extension (fixes #109)

This change implements the following ranking:

No extension: LICENSE, COPYING, etc.
Filetype extension (syntactic annotation): UNLICENSE.txt, COPYRIGHT.md, etc.
Content-related extension (semantic annotation): COPYING.image, LICENCE.go, etc.

@waldyrious This is great. One comment on the priorities, and then we'll just need to update the corresponding tests.

Shouldn't the tests be relative (score of form X > score of form Y) rather than binded to absolute values?

Shouldn't the tests be relative (score of form X > score of form Y) rather than binded to absolute values?

If there's a concise way to write that, that would better match our intent here, yes, I believe the actual values can be treated as arbitrary.

fixed the tests and rebased the branch.

Thanks @waldyrious! I'll get those rubocop errors clean up on master as I believe I may have introduced at least one of them. 😄

Thanks :)


dashboard mostly blank when streamers channel changes names?

Using TwitchAutomator 5.0.5/0.2.1, I wasn't able to view most of my dashboard this morning.  I saw this stack in my log:
2021-05-13 10:29:53.307 | helper | <ERROR> Failed to fetch channel id for ExLibrisDJ: {"data":[]}
NOTICE: PHP message: PHP Fatal error:  Uncaught TypeError: Typed property App\TwitchChannel::$userid must be string or null, bool used in /var/www/twitchautomator/src/TwitchChannel.php:43

Stack trace:
#0 /var/www/twitchautomator/src/Controller/ApiController.php(67): App\TwitchChannel->load()
#1 /var/www/twitchautomator/src/Traits/ApiChannels.php(49): App\Controller\ApiController->generateStreamerList()
#2 /var/www/twitchautomator/vendor/slim/slim/Slim/Handlers/Strategies/RequestResponse.php(43): App\Controller\ApiController->channels_list()
#3 /var/www/twitchautomator/vendor/slim/slim/Slim/Routing/Route.php(384): Slim\Handlers\Strategies\RequestResponse->__invoke()
#4 /var/www/twitchautomator/vendor/slim/slim/Slim/MiddlewareDispatcher.php(81): Slim\Routing\Route->handle()
#5 /var/www/twitchautomator/vendor/slim/slim/Slim/MiddlewareDispatcher.php(81): Slim\MiddlewareDispatcher->handle()
#6 /var/www/twitchautomator/vendor/slim/slim/Slim/Routing/Route.php(341): Slim\MiddlewareDispatcher->handle()
#7 /var/www...

I went to check on ExLibrisDJ and twitch showed the "Sorry. Unless you’ve got a time machine, that content is unavailable."  I think they changed their name to ExLibrisOfficial, but not 100% sure.
I manually removed ExLibrisDJ from my config.json and things seem to be working again.
Just thought I'd pass this scenario along and not sure how helpful this is.

yeah i'm gonna have to rewrite this whole thing to use usernames instead of display names one day, unless this was an actual username change


⚠ BroadcasTheNet has degraded performance

In 64cea20, BroadcasTheNet ($BTN) experienced degraded performance:

HTTP code: 502
Response time: 13864 ms

Resolved: BroadcasTheNet performance has improved in 446417f after 5 minutes.


Only initialize time if CO_GET_CNT(TIME)==1

If NO time service is defined in the OD and the TIME service feature is not enabled.
A rx buffer is allocated.

We have to discuss about this commit too. You can't do that, because CO_TIME_init() function uses idxRx so rx buffer could get overlapped with other CANopen object.
Configuration may seems complex. There are two sources of configuration:

primary: CO_CONFIG... macros, which enables/disables parts of code
secondary: object dictionary, which may or may not have specific objects.

I tried to make stack independent from object dictionary, so there is not much automation.
Optimization of the stack must be done with CO_CONFIG... macros (in CO_driver_target.h or CO_driver_custom.h file).
Object dictionary must then match the configuration somehow. If there are missing required OD entries, then stack may compile but will not run from the first time.

Sorry, I missed:
#if (CO_CONFIG_TIME) & CO_CONFIG_TIME_ENABLE
    if (CO_GET_CNT(TIME) == 1) {
        err = CO_TIME_init(co->TIME,
...

I will check again, if we can optimize rx buffer usage.

Actually this commit is not necessary, because
RX_CNT_TIME gets value of 1 only if (CO_GET_CNT(TIME) == 1), otherwise it has value 0 and additional rx buffer is not allocated.
(But I must say, I'm not 100% sure if it works correctly, I didn't use MULTI_OD much.)

It didn't work for me, with MULTI_OD defined, hence the PR.
Time service was not  initialized, buf the buffer for it was allocated.
I may have been the cause of this myself.
I will look into it, but as you, I get occupied elsewhere.

Fra: Janez @.>
Sendt: 22. juni 2021 10:29
Til: CANopenNode/CANopenNode @.>
Cc: Carsten Frank @.>; Author @.>
Emne: Re: [CANopenNode/CANopenNode] Only initialize time if CO_GET_CNT(TIME)==1 (#306)
CAUTION - EXTERNAL EMAIL: Do not open attachments or links unless you recognize the sender and the content is safe.
Sorry, I missed:
#if (CO_CONFIG_TIME) & CO_CONFIG_TIME_ENABLE
if (CO_GET_CNT(TIME) == 1) {
err = CO_TIME_init(co->TIME,
...
I will check again, if we can optimize rx buffer usage.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https://github.com/CANopenNode/CANopenNode/pull/306*issuecomment-865719495__;Iw!!GenOTVeOfQ!GtAax5h9KSxmKyjYR_TVqvp2DAVO5m5d9WxEXcVljPqzFzknIV_6aZFATyrrlF8$, or unsubscribe [github.com]https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AKQDKZCODATHK7IDZOEEON3TUBCW5ANCNFSM45W7I4SA__;!!GenOTVeOfQ!GtAax5h9KSxmKyjYR_TVqvp2DAVO5m5d9WxEXcVljPqzFzknIV_6aZFAsS6Wouc$.

Actually this PR is not necessary, rx buffer is not allocated, if CO_GET_CNT(TIME) == 0. I was working with CO_MULTIPLE_OD in the last days and have included all your ideas and some mine, see next PR.


DOC: fixed typos in GroupBy document

[ ] closes #xxxx
[ ] tests added / passed
[x] passes git diff upstream/master | flake8 --diff
[ ] whatsnew entry

@mortada thank you!


Can't find variable: exports with ember

This may be a question for beginners but I can't find the solution. I'm trying to run my tests with Karma in an Ember app.
I have this karma.conf.js file :
// Karma configuration
// Generated on Wed Jan 27 2016 13:35:28 GMT+0000 (UTC)

module.exports = function(config) {
  config.set({

    // base path that will be used to resolve all patterns (eg. files, exclude)
    basePath: '',

    // frameworks to use
    // available frameworks: https://npmjs.org/browse/keyword/karma-adapter
    frameworks: ['mocha'],

    // list of files / patterns to load in the browser
    files: [
      'bower_components/jquery/dist/jquery.js',
      'bower_components/ember/ember.debug.js',
      'bower_components/ember-data/ember-data.js',
      'bower_components/ember-mocha-adapter/adapter.js',
      "app/**/*.hbs",
      "app/**/*.js",
      "tests/**/*.js"
    ],

    // list of files to exclude
    exclude: [
    ],

    plugins: [
     'karma-mocha',
     'karma-ember-preprocessor',
     'karma-phantomjs-launcher',
     'karma-babel-preprocessor'
    ],

    // preprocess matching files before serving them to the browser
    // available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
    preprocessors: {
      'app/**/*.js': ['babel'],
      'tests/**/*.js': ['babel']
    },

    babelPreprocessor: {
      options: {
        presets: ['es2015'],
        sourceMap: 'inline'
      },
    },

    // test results reporter to use
    // possible values: 'dots', 'progress'
    // available reporters: https://npmjs.org/browse/keyword/karma-reporter
    reporters: ['progress'],

    // web server port
    port: 9876,

    // enable / disable colors in the output (reporters and logs)
    colors: true,

    // level of logging
    // possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
    logLevel: config.LOG_INFO,

    // enable / disable watching file and executing tests whenever any file changes
    autoWatch: false,

    // start these browsers
    // available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
    browsers: ['PhantomJS', 'Chrome'],

    // Continuous Integration mode
    // if true, Karma captures browsers, runs the tests and exits
    singleRun: false,

    // Concurrency level
    // how many browser should be started simultaneous
    concurrency: Infinity
  })
}

When I do karma start and karma run, I have this error message :
PhantomJS 2.1.1 (Linux 0.0.0) ERROR
  ReferenceError: Can't find variable: exports
  at /frontend/app/adapters/application.js:3

PhantomJS 2.1.1 (Linux 0.0.0) ERROR
  ReferenceError: Can't find variable: exports
  at /frontend/app/adapters/application.js:3

Here is the line in question :
export default ActiveModelAdapter.extend(DataAdapterMixin, {

If I understand, babel should convert, from es6 to e5, this file but it didn't.
What can I do ?

Babel converts from es6 to es5 which results in commonjs exports (that's why the error says exports and not export) commonjs only works in node so you need to add a module bundler e.g webpack or browserify to the mix to get a bundle usable in the browser.

@dignifiedquire you're right. I have a lot of problems with ember and karma but it's not related to karma. If you know a tutorial to use karma with ember can you share it ?
Thanks !

@GCorbel Did you solve this? I can't find a complete tutorial either


Update choose-web-site-cloud-service-vm.md

The doc says "Automatic OS updates are planned for a future Service Fabric release.".
OS patching of SF nodes/VMs is available through the POA service although not fully automated by Azure, which will come in next releases.
https://blogs.msdn.microsoft.com/azureservicefabric/2017/05/22/os-patching-of-service-fabric-cluster-nodes/

@CESARDELATORRE,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@CESARDELATORRE : Thanks for your contribution to the Azure documentation! The author, @ggailey777, has been notified to review your proposed change.

This doc has been moved. Fixed in the private repo. Thanks! #please-close


Fix Working Group link in README.md

The Working group link in the Community section was broken.

hey thanks! can you make it link to the #readme anchor instead, so they can see the folders?

@acao, sorry I don't completely follow you here.
The README inside working-group doesn't have a readme anchor 😕. Did you mean pointing to the folder instead so they see the README and all the folders, like this:

ah, yeah its confusing, and hard to find the anchor
the only change we need is from this:
[Learn more.]('working-group#readme')

to this:
[Learn more.](working-group#readme)


ARS-4463: add a custom authenticator for ARS to authenticate against the dashboard (WIP)

Ticket
https://techweb.axway.com/jira/browse/ARS-4463
Description
This is to add a custom authenticator for ARS to authenticate against the dashboard.

replaced by https://github.com/appcelerator/harbor/pull/2


add Indonesian words

This module is for English words. You could fork and publish your own superb-indonesian module maybe.


Add RTL support

as arabic, persian, hebrew,... localisations are available it might be good idea to add RTL support

I'm completely inept when it comes to RTL.
Pull requests are welcome

how about using rtlcss-stylus, maybe a note to how make RTL version with gulp in wiki or README file is enough.

Your works is awesome ! Thanx !
But, as Sijad, I am very interested by an RTL implementation! I bet we r far being alone :)

Thank you so much !!
How we do activate the RTL ?
Is this relative to the localization ?

Hello,
See https://github.com/chmln/flatpickr/tree/master/dist/rtl

Also note that this is the initial version.
Please report here if there are any issues

Wow ! Awesome !
OK ! I will let you know of course :)

Closing due to inactivity.
The RTL versions are not perfect, and while lacking competency in subject I'll happily accept future PRs that fix any issues. :+1:

Hello,
I just found a few issues and I am trying to resolve them on the provided themes. Will submit PR once done.

@chmln Hey, did you remove the RTL support?
@ahmadalfy Were you able to get an RTL theme?

@kfirba I am revamping the build system. RTL will be included in the next release

If anyone needs RTL in the meantime, here's my overrides to support it (for default theme):

.flatpickr-calendar {
    .dayContainer, .flatpickr-weekdaycontainer {
        flex-direction: row-reverse;
    }
    .flatpickr-months {
        .flatpickr-month {
            height: 32px;
        }
        .flatpickr-prev-month {
            left: unset;
            right: 0;
            transform: scaleX(-1);
        }
        .flatpickr-next-month {
            right: unset;
            left: 0;
            transform: scaleX(-1);
        }
    }
}
.flatpickr-day {
    &.selected.startRange, &.startRange.startRange, &.endRange.startRange {
        border-radius: 0 50px 50px 0;
    }
    &.selected.endRange, &.startRange.endRange, &.endRange.endRange {
        border-radius: 50px 0 0 50px;
    }
    &.selected.startRange + .endRange:not(:nth-child(7n+1)), &.startRange.startRange + .endRange:not(:nth-child(7n+1)), &.endRange.startRange + .endRange:not(:nth-child(7n+1)) {
        box-shadow: 10px 0 0 #569ff7;
    }
}


YARA UI & Service Updates

It would be nice if the Signature Search also searched on Source.  So if I search bartblaze or reversinglabs, I'd get some Yara hits for Signatures.  I couldn't find the Yara (perhaps due to a 10,000 limit on Signatures) so I was searching on the Source and kept getting 0 hits.  I didn't realize I needed to search Yara.  I did end up finding them by clicking on the source fingerprint.

Some of my yara source updates don't appear to be processing the yara rules.  Here are couple public repositories that I've added that say they've downloaded, but show no signatures.

(.*.yara$) https://github.com/chronicle/GCTI.git
(.*.yara$) https://github.com/reversinglabs/reversinglabs-yara-rules.git

for number 1 you can do: source:reversinglabs  (case sensitive)
@cccs-sgaron Will investigate indexing all the text of the rule body in the futur.
@cccs-rs for #2 :)

Regex seems wrong, should be .*\.yara$

Refer to my recent messages re: 1. https://discord.com/channels/908084610158714900/908084610624274494/1086247172724510843

Source Configurations (typo on the second but still matched the file path):

Which yielded signatures being import for both sources:

Is there anything in the yara-updates container to suggest what the issue could be?

No errors in the logs.  For all purposes that I can tell, it completes successfully. There are just no signatures when I click on the fingerprint.  Status: Skipped.

Issue partially resolved by clearing the cached entries in Redis. Adding a cache-less update mechanism has been created as a ticket.

Documenting what @cccs-rs and I have discussed in chat (and also a reminder).  The Redis cache resolved 2 of my 3 issues with the yara files.  The last was reported an error of 'utf-8' codec can't decode byte 0xbb in position 908: invalid start byte.
The line causing the exception is here:  https://github.com/CybercentreCanada/assemblyline-service-yara/blob/3061ac084004db4cb514d192ab88fd142ad9d09e/yara_/update_server.py#L96
The readlines() causes an exception as it finds a character it can't decode.  I did verify the files are utf-8 files that just have unknown characters in them.  Here is an example.
What I guess I'd suggest is maybe a couple things...

Might make sense to Include the reading of the file in the try / except statement, so even if there is an error on a file, it continues to read the other rules.

Probably would be good to define errors in the open(errors=) so that it can hopefully use the rule as intended.  I'm not sure if they should be set to ignore or maybe surrogateescape? https://docs.python.org/3/library/functions.html#open

Based on these comments, I recommend ignoring any encoding errors.
https://github.com/VirusTotal/yara/pull/1770#issuecomment-1357622486
https://github.com/VirusTotal/yara-python/pull/136#issuecomment-612820721

$str_08 = "<(:<\Documents and Settings\all users\Application Data\�"

Do you have a link to the source, or can you upload that portion of the rule here? Strings pasted inline won't retain the source encoding.

It's not public, but here is a modified file based on that rule.

It's not public, but here is a modified file based on that rule.
testgen.txt

Yeah, it was a BB hex for that one, which comes across in my hex editor as ».

Looks like I was behind on the status of the rule encodings. But there appears to be a consistent desire from the development team to only support UTF-8 in the future.
https://github.com/VirusTotal/yara/commit/68eb237dd66dd5805cb44ce17a3b22c999f43bbe
iso-8859-1 will accept any byte, but the values in [\x80-\xFF] may be incorrect if a different encoding was used at the source.
                try:
                    with open(file, 'r') as f:
                        f_lines = f.readlines()
                except UnicodeDecodeError as exc:
                    with open(file, 'r', encoding='iso-8859-1') as f:
                        f_lines = f.readlines()
                    self.log.error(f"File could not be loaded as UTF-8: {file}")

v4.4.0.stable5 of the YARA service will include performing a surrogateescape when reading the contents of YARA files with non-UTF8 charactors
Services w/ updaters built from v4.4.0.stable5 of Assemblyline will now be able to instruct the Scaler about when to scale a service.
If a service depends on the bundle sent by the updater, indicated by wait_for_update flag, (ie. YARA) then the service is only considered 'active' and ready for scaling only if the updater deems it so (ie. it has at least 1 downloaded source).
If you notice this issue still persists, feel free to re-open the issue with more information! 😁


openexrcore/encoding.c: warning: format specifies type 'unsigned long' but the argument has type 'size_t'

When cross-compiling openexr-3.2.0-rc4 from Debian Bookworm x86_64 to Windows aarch64 and armv7 using llvm-mingw, I get a single warning for each:
aarch64:
/home/claude/opt/windows/posix/aarch64/src/openexr-3.2.0-rc4/src/lib/OpenEXRCore/encoding.c:35:13: warning: format specifies type 'unsigned long' but the argument has type 'size_t' (aka 'unsigned long long') [-Wformat]
            exr_compress_max_buffer_size (encode->packed_bytes));
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

armv7:
/home/claude/opt/windows/posix/armv7/src/openexr-3.2.0-rc4/src/lib/OpenEXRCore/encoding.c:35:13: warning: format specifies type 'unsigned long' but the argument has type 'size_t' (aka 'unsigned int') [-Wformat]
            exr_compress_max_buffer_size (encode->packed_bytes));
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

(I don't have any ARM Windows machines to test with so I don't know how significant this is...)

@claudeha, this should be addressed by #1534, can you confirm?

Closing for now since #1534 should resolve it, but feel free to reopen or submit a new issue if something is still amiss.


Added Angelic_Search in planning.py

Added multiple refinements
Added angelic search algorithm
-- Doesn't work correctly for all instances
(e.g. when initial plan achieves the goal, the implementation might not achieve the goal)
-- Making progress is not implemented
-- Added tests for angelic search and its relevant functions
-- Added notebook planning_angelic_search with examples for angelic_search

@MariannaSpyrakou You need to update your fork of the repository before you commit your changes, to prevent merge conflicts.


Fail to clean up report #100

https://github.com/andgineer/bitwarden-import-msecure/actions/runs/8858130612/job/24326410693
Report successfully generated to gh-pages-dir/builds/tests/113
Traceback (most recent call last):
File "/.venv/lib/python3.11/site-packages/github_custom_actions/action_base.py", line 68, in run
self.main()
File "/generate-allure-report/app/allure_generate.py", line 98, in main
self.cleanup_reports()
File "/generate-allure-report/app/allure_generate.py", line 129, in cleanup_reports
report.unlink()
File "/usr/lib/python3.11/pathlib.py", line 1147, in unlink
os.unlink(self)
IsADirectoryError: [Errno 21] Is a directory: 'gh-pages-dir/builds/tests/100'
Generate Allure Report action v.3
Generating report from allure-results to gh-pages-dir/builds/tests ...
Found 21 report(s) in history, keeping 20
Removing 100 ...

Hello @andgineer, how to fix this error? Getting the same in my config.

Are you using the latest version?
As I see I fixed it so it should not use unlink at all
https://github.com/andgineer/allure-report/commit/41b6e648587e52d3a725e08a460f883d1c8511e2

Updated to 3.4 version and now it works fine. Thanks!


Transfer Region in UserAgent-header

Fixes #3098
Stores the region in the UserAgent-header in the following format:
User-Agent: Boto3/1.14.12 Python/2.7.15+ Linux/4.15.0-106-generic Botocore/1.17.12 region/us-west-2
Marked as draft, as I haven't accounted for the fact that the user might have provided their own extra user-agent information - just verifying the POC for now

Coverage decreased (-0.1%) to 94.137% when pulling 6ab2f58b21b1e14296d926d3943a61a4c158688f on bblommers:region-stored-in-user-agent into 73813460b66119dd2491f286a01bf07e0b18d193 on spulec:master.


Use existing params

When updating a stack, if a parameter is not given but is set on the existing stack, use the existing stack's parameter.  Also, this pull allows us to catch missing parameters earlier.
Fixes GH-11
Fixes GH-15

Hrm - this is a diff from the taxonomy_cleanup branch, which is on deck.  I'm going to do some more testing of that branch, then I'll reopen this once I merge taxonomy_cleanup.