Issue 72/user list management, Issue 73/refactoring, Issue 76/application routing

Draft PR for Issue #72 (user list manager) and includes Issue #73 (refactoring sesssion-core/session-helper/reducer, etc.) as part of the commits.
Improvements here includes the addition of a user list manager and login tracker (both of which could be subject to change as is) in preparation for a home screen. Functionality and components build here could be used for that.
The user list can only be accessed by the user themselves within Pod container Users and shows the data for a user's name and their Pod URL.
The login tracker only shows the time and date of their latest login and is placed within public, which only provides read access to other users.
Combined these two functionalities provides a list of users that could be seen from their main page the other user's name, the other user's  Pod URL, and their Last Active Date.

Updating PR to include Issue #76. Likely be the final changes before merging to Development, then we'll move onto #75 with Material UI as discussed.

went over and tested changes in discord voice chat. 🚀


All the project listing pages show throw 403 if permission fails

Describe the task
All the project listing pages show throw 403 page if permission fails if user has projects.view permission. Right now it says the message in the table but I can still see the tabs, and count of projects which is not right.
Expected behavior
All project pages should show 403 page if projects.view permission isn't there

Closing as issue is fixed


feat(name_section): select all text on focus

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
34

Relevant Lines:
34

💛  - Coveralls


clearly state you can only search a 1 week period at a time

[Enter feedback here]
clearly state you can only search a 1 week period at a time when searching 6 months back

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 9450b1a9-f22b-c5d7-6789-676c9f4afc1f
Version Independent ID: 8ada75ef-7a51-07dc-f69d-a71451b69cf1
Content: Activity filters and queries - Microsoft Defender for Cloud Apps
Content Source: CloudAppSecurityDocs/activity-filters-queries.md
Service: defender-for-cloud-apps
GitHub Login: @batamig
Microsoft Alias: bagol

Thank you for your comment. We'll investigate and get back to you.

Hi @MikeBakerSAV, thanks again for your feedback. The page has been updated at https://learn.microsoft.com/defender-cloud-apps/activity-filters-queries#query-activities-six-months-back.
Can you please look to see if you have any additional feedback, or if we can close this issue? We appreciate your contribution!

Hi @MikeBakerSAV, it's been a few weeks since we fixed this page and we haven't heard from you.
I'm going to close this page for now but feel free to tag me again in any further feedback you might have.
Thanks again for writing into docs!
#please-close


[1.12.2] Conflict: Bows or any item that fires Projectiles breaks Tinker's Tools to the point where everything on that tool is wiped clean.

Minecraft: 1.12.2
Forge: <IP_ADDRESS>08
Mods:
Cyclic-1.12.2-1.15.11
Mantle-1.12-<IP_ADDRESS>
TConstruct-1.12.2-<IP_ADDRESS>

Video of Bug:
https://www.youtube.com/watch?v=dNPfxjr-FmI
While the bug which prevented projectiles from being fired was fixed, another bug surfaced... this time it breaks Tinker's Construct Tools quite badly and it's possible it may affect other things.
What happens is that if you have a Tinker's Tool that fires a projectile from it.. the Tool becomes broken to the point where all Tool Parts and modifiers on that Tool are gone with the Durability being strange.
If you have... say a Tinker's Broadsword in your Main-Hand and you use a Vanilla Bow or a Tinker's Tool that uses projectiles from your Off-Hand, the Broadsword instantly breaks with everything wiped from it.
This type of bug didn't occur in Cyclic-1.12.2-1.15.10.

Can confirm.
It totally wiped my electrum knightslime longbow.
https://imgur.com/a/MWuR5Im

Hm i thought i fixed this in last version, but you are already on 15.11 so ill have to check again https://github.com/PrinceOfAmber/Cyclic/issues/843

SO kind of duplicate, but not really since the fix didnt actually work and caused new issues

This fixes it for me. if it comes back or theres something else let me know !!! https://minecraft.curseforge.com/projects/cyclic/files/2573825

Can confirm it's fixed in...
Cyclic-1.12.2-1.15.12
...will let you know if something else happens.


a package which imports itself causes infinite loop

What version of CUE are you using (cue version)?
0.4.2
What did you do?
exec cue eval

-- cue.mod/module.cue --
module: "hof.io/repro"
-- data/index.cue --
package data

import "hof.io/repro/data"

Foo: "Bar"
-- index.cue --
package main

import "hof.io/repro/data"

foo: data.Foo

What did you expect to see?
A cycle or other error
What did you see instead?
nothing and cue eval running indefinitely

Is this the same as #849 ?

I would point out that there is a difference in the formulation, not sure about the relation to underlying issue.

#849 has mutually importing packages
This issue has a self importing package


ERD Modeling for Ticketing System

Version needs review, please add any fields we may be missing from these entities or drop any ideas in the comments :) <3

Need to coordinate with Celine on wireframes for any missing entities.


feat: added NewAssignmentNotification - to all groupmembers

Fixes #3294
Describe the changes you have made in this PR -

added notifications to group members on new Assignment creation

Screenshots of the changes (If any) -

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Coverage increased (+0.08%) to 82.114% when pulling 70a3112aeaa36e11cb37148cce17b8512f4bc732 on VaibhavUpreti:NewAssignmentNotification into 6803ef1476fe957743da26f08444f22f057a0fec on CircuitVerse:master.

@vedant-jain03 kindly review.

Hey @vedant-jain03 , thank you for the review.
I found some things were broken .

All pages were giving name error... due to new_assignment_notification.rb file ....

Error seems to be in calling the method
''' assignment = params[:assignment] '''
I changed this to as shown in the image

After this ... all the name errors were gone ... and notifications were showing
this produces the following output

For the routing part

It was giving the following error
I think a possible fix for this could be to find group by params id. But alas it was still not working .. rather giving 404

@VaibhavUpreti could you please add spec testcases for this notifications!
Also test if the assignment got deleted, the associated notification are destroying or not!
That is the edge case, we need to see!
I think has_noticed_notifications do this thing but just in case kindly test this in your end!

@VaibhavUpreti could you please add spec testcases for this notifications!
Also test if the assignment got deleted, the associated notification are destroying or not! That is the edge case, we need to see!
I think has_noticed_notifications do this thing but just in case kindly test this in your end!

Yeah Sure! I will write the required specs for these... And nothing seems to be broken after deleting the assignments ... The notifications are also getting cleaned up.

@vedant-jain03 I have written the tests ... can u please check .. also I had sent u dm on slack regarding testing controller

@VaibhavUpreti
you need to write the test for this in #create in assignment_controller_spec.rb.
Here
Try adding under the context when primary mentor is logged in, try this:
      it "sends notifications to group members" do
        sign_in @primary_mentor
        post group_assignments_path(@group), params: { assignment:
          { description: "group assignment", name: "Test Name" } }
        expect(@member.noticed_notifications.count).to eq(1)
      end

@vedant-jain03 I think this one if good to merge now.

@tachyons @vedant-jain03 I haven't used the function "notification_type" as I think routing is part of ActionController and not present in custom classes. So the current code handles routing in the controller itself and "notify" function works for now.
Is there any way we can use "redirect_to" method in our service class ... is so then we can keep this function else remove this.

@tachyons made the controller "skinny" ... moved all the logic to the service class. Kindly review.


Update obsolete a11y-dialog URLs

Cheers. :)

Thanks @KittyGiraudel .
This entire repo is actually all generated, so no need manually patching it. I'll refresh the metadata next time I run the full build :)

Thank you!


Adding a public typealias for Database

Fixes #22

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

@mbarnach Anyway the PR gets merged?

Thanks for the PR.  Let me fix up the CI issue, then I'll merge it.


Circular.io not working for me, unable to sign in properly to dashboard. Please help....

My twitter handle is @ThenNowWow
Before signing in to Circular, there are no apps approved to use my account.
Screenshot:

Then I opened circular.io in a new tab.
Screenshot:

Clicking on "Sign in with Twitter" twitter's app authorization page loads.
Screenshot:

Clicking on "Authorize app" loads Circular's home page, but it doesn't redirect to Circular's dashboard. The ring keeps on moving round and round indefinitely. Reloading the page doesn't help, again that ring keeps on moving round!
Screenshot:

I also checked apps approval page of twitter which shows that Circular has been approved successfully.
Screenshot:

Please help out.
Thanks

Hey I am having the same problem as @jacobparra and @khanak. Any help?

If I download and install the source code in my own server I should have this problem?

Taking a stab at this later today. Please stay put, and any help in testing is more than welcome.

I'm still having this problem as well. Get a status code 500 on the oauth.php request:
"{\"errors\":[{\"code\":89,\"message\":\"Invalid or expired token.\"}]}"{"id":"<redacted>","users":{"<redacted>":{"user_id":<redacted>,"user_screen_name":"<redacted>","profile_image_url":"http:\/\/abs.twimg.com\/sticky\/default_profile_images\/default_profile_3_normal.png","name":"Christopher Su","id":"<redacted>"},"<redacted>":[]}}

Hello. I'm having this issue as of February's 18th, 2016. Happened after I tried to connect multiple accounts and logged in onto another browser in a different computer.

Same here! I have made a new twitter account and I can log into circular.io with no problem.
But the other 6 accounts connected to it are not working anymore and cannot login into ciruclar.io from them! All of them are going in an infinite loop! I think something needs to be stopped on their end on circular.io


fix: pass application context to adapter setup

Fix the receive adapter to start without panic
@pierDipi as far as I can tell, the mt_receive_adapter should be fine since it uses adapter.WithController(). Do you think we also need the adapter.WithInjectorEnabled() call for that one as well?

/cc @pierDipi @Leo6Leo

/cherry-pick release-1.14

/cherry-pick release-1.13

/override codecov/patch

/override codecov/patch


GPSQuickFix data not updating

Using the latest master code and watch firmware 1.8.35
It looks like the update is working OK
Downloading GPSQuickFix data file...
Writing file to watch...
GPSQuickFix data updated
But the watch shows the download icon and it does take several minutes to get  a fix so the data has not been applied.
Reading the file (0x00010100) from the watch and comparing it with the file from gpsquickfix.services.tomtom.com/fitness/sifgps.f2p3enc.ee shows it is being written to the watch correctly.
Time on the watch is correct.
Any thing else I can try?
Thanks for a great piece of code
Ad

I noticed that when I went for a run this afternoon too. Maybe something changed in the last firmware update. I'll look into it in the next few days when I get some time.
Cheers,
Ryan

Easy fix. Somehow in the last big update, the code to reset the GPS processor following the GPSQuickFix data being updated was lost. I have added it again, and it's working again.

Yes all good. Thanks for the quick response


Rating and metering plan returns business response.

Summary:

Metering & rating config's get plan function returns business response.
Adjusted Meter, Accumulator, and Aggregator to attach error and reasons to doc when error happen.
Report will throw error when business error happens.

Coverage increased (+0.01%) to 87.046% when pulling 5de3c10ac0e1f741dfbfe2bbef38653dbdc9fe43 on KRuelY:meterFailManagement into a4cd00b4cdd2a498cf847f55f7afed3590cdb34e on cloudfoundry-incubator:master.

Coverage increased (+0.01%) to 87.046% when pulling 08ab0b35be8f8e52bedec3f63c3dc927fb76657b on KRuelY:meterFailManagement into a4cd00b4cdd2a498cf847f55f7afed3590cdb34e on cloudfoundry-incubator:master.

Combined and commited in f412896


API documentation is empty

the link https://itsyou.online/apidocumentation is showing an empty doc.
TypeError: Cannot read property 'buffer' of undefined
    at api-console.js:1124
    at processQueue (api-console-vendor.js:423447)
    at api-console-vendor.js:423463
    at Scope.$eval (api-console-vendor.js:424699)
    at Scope.$digest (api-console-vendor.js:424515)
    at api-console-vendor.js:424738
    at completeOutstandingRequest (api-console-vendor.js:415069)
    at api-console-vendor.js:415457

This is due to an error in the raml file


dev crash can only concatenate str (not "NoneType") to str

def download_exception(type, e, i, max_retries, sleep_time, status_message):
    """
    Handle exceptions during the download process.
    """
    type = e.__class__.__name__.upper()
    status_message = f"{status_message}\n" + \
        f"{type} -> ({i+1}/{max_retries}), reconnect in {sleep_time} seconds...\n" + \  #<-- The ends `+ \` cause the crash because it actually not connected to another str
    vb.write(status_message)
    time.sleep(sleep_time)

thank you :)


W3C validation error: Attribute sprig not allowed on element form at this point.

Question
How do you deal with the errors Sprig causes in Nu Html Checker?

You can use the alternative data-sprig if you prefer.


Benchmarks to back up "fastest template engine" claim?

Do you have benchmarks that back up the claim that yarte is the "fastest template engine?"

You can see in:

https://github.com/botika/yarte#is-it-really-the-fastest
https://github.com/botika/template-bench-rs
https://travis-ci.org/github/botika/template-bench-rs/jobs/676386705#L1024
cargo asm

I completely missed the link to the benchmarks in the readme, my apologies!
Thanks for the quick response. :-)


Replace nn_to_cudnn by cudnn.convert #106

What does this PR do?
Replace nn_to_cudnn and cudnn_to_nn by cudnn.convert delivered by cudnn-torch repo
How should this PR be tested?
Now, I do not know why, after single epoch the GPU RAM consumption rise  2x times. I can not find why. I will try to find the reason. Test can include running the code with 2 epochs (with minimal epochSize)
Any background context you want to provide?
What are the relevant issues?
#106

I resolved that problem. It occur that I have to clone the model (you have cloned the model too in convertion). Now everything works. Additionally, it works faster:) Only because the function "nn_to_cudnn" was replacing "SpatialConvolutionMM" by cudnn version. As none of our model not have "SpatialConvolutionMM", so it does not replaced it by cudnn version. From my test, nn4.def is 2x faster now

Thanks @melgor - I'm excited to merge this in. It's also halved the execution time on my machine too!


Test conversion ts

List of fixed issues (if they exist):

Converts test from JavaScript to TypeScript (via @cdrake)
closes #735 (via @hanayik)
closes #882 (via @hanayik)
adds piped stdout and stderr to playwright console output from browser window
closes #824 until more vitest unit tests added later

@cdrake , I have added a couple of commits to this PR. They should fix #882. I updated the builds to use a separate tsup config that targets a build for our tests, and another tsup config that is aimed at building a leaner niivue javascript bundle.
@jens-ox, and @jennydaman, it might be nice for the two of you to take a look at these specific changes too.

Sounds good to me.  Let me know if you would like me to make any other changes.

Looks like testing is broken. I will try to get testing working again.

@cdrake, please review my latest commit (fix pretest). I removed all the *.js output files that are created by tsc. I also updated a screenshot that was wrong. I created a nodejs script to copy files (so it can make the output folder if needed). I also updated gitignore.


Module not found: Error: Can't resolve -> adding background-image without '/'

Bug Report or Feature Request (mark with an x)
- [ X] bug report -> please search issues before submitting
- [ ] feature request

Versions.
@angular/cli: 1.0.3
node: 6.10.3
os: darwin x64
@angular/animations: 4.1.2
@angular/common: 4.1.2
@angular/compiler: 4.1.2
@angular/compiler-cli: 4.1.2
@angular/core: 4.1.2
@angular/forms: 4.1.2
@angular/http: 4.1.2
@angular/material: 2.0.0-beta.3
@angular/platform-browser: 4.1.2
@angular/platform-browser-dynamic: 4.1.2
@angular/platform-server: 4.1.2
@angular/router: 4.1.2
@angular/cli: 1.0.3
Repro steps.
Using background-image : url()  path without slash gives error . Ex:
Not works:
   background-image: url('manage/assets/images/play-button.svg')
Works:
   background-image: url('/manage/assets/images/play-button.svg')
The log given by the failure.
ERROR in ./src/app/manage/contents/home/home.component.css
Module not found: Error: Can't resolve './manage/assets/images/play-button.svg' in '/Users/Alisgandarov/Desktop/Projects/Jabd
a_Manage/src/app/manage/contents/home
Desired functionality.
It is needed to work without slash, because my application is in subfolder in the serve ('/manage' in this case) , but we are working in the index , so you need to change '/' to '/subfolder' everytime on build.
Mention any other details that might be useful.

Assets with relative URLs are managed by the CLI and processed at build time.  This is the cause of the build error.  It is recommended to use this approach as the asset will benefit from hashing and automatic copying to the output (and in the future, image optimization passes).
When using the root relative URL, in processing occurs on the asset.  However, the URL will be adjusted based on the deploy URL and/or base HREF options, if provided.


ActiveRecord::StatementInvalid in Devise::SessionsController#create

Hi!
I'm fairly new to rails/devise and I can't detect the source of the problem.
I installed devise via the Installation Guide and if I try to "Sign up" , there is the following error:
ActiveRecord::StatementInvalid in Devise::RegistrationsController#create
ActiveRecord::JDBCError: Bei der Konvertierung eines varchar-Datentyps in einen datetime-Datentyp liegt der Wert außerhalb des gültigen Bereichs.: INSERT INTO [users] ([created_at], [current_sign_in_at], [current_sign_in_ip], [email], [encrypted_password], [last_sign_in_at], [last_sign_in_ip], [remember_created_at], [reset_password_sent_at], [reset_password_token], [sign_in_count], [updated_at]) VALUES ('2012-01-16 10:19:18', NULL, NULL<EMAIL_ADDRESS>N'$2a$10$7Iit/nLVHd3Rqppqmp7pheybjuSyhwjJwxUC7rMAPB8O7ifwpoEb.', NULL, NULL, NULL, NULL, NULL, 0, '2012-01-16 10:19:18'
Theres a problem with the conversion from a varchar-type to a datetime-type . I don't really know the exact english error, but this will give you an idea.
Thanks in advance,
David

I'm not sure if this is a Devise error. Did you use the Devise generated migration? Can you provide the table schema of your Database? Seems that you're trying to insert a Varchar to a Datetime field (though, I'm not a JDBC specialist).

I just followed the instructions on https://github.com/plataformatec/devise and I haven't customized it yet.
create_table "users", :force => true do |t|
t.string   "email",                                 :default => "", :null => false
t.string   "encrypted_password",     :limit => 128, :default => "", :null => false
t.string   "reset_password_token"
t.datetime "reset_password_sent_at", :limit => 16
t.datetime "remember_created_at",    :limit => 16
t.integer  "sign_in_count",          :limit => 10,  :default => 0
t.datetime "current_sign_in_at",     :limit => 16
t.datetime "last_sign_in_at",        :limit => 16
t.string   "current_sign_in_ip"
t.string   "last_sign_in_ip"
t.datetime "created_at",             :limit => 16
t.datetime "updated_at",             :limit => 16
end

Unsure. Maybe this is an issue with the database locale? Maybe Rails is feeding data in a format invalid to the current database locale?


fix member expression extraction if this is present in member expression

The problem:
t`${ this.user.name } hello`

was extracted to "${ undefined.user.name } hello" instead of "${ this.user.name } hello"
@alxpy

nice :+1:


MAISTRA-1374: support multiple multus CNI interfaces

This needs to be updated once https://github.com/Maistra/istio/pull/117 is merged

/retest

/cherry-pick maistra-1.2


Always use datetime and timedelta in camera.proxy instead of int/float

Description:
The camera proxy module compares a float with a datetime object, and also attempts to add a float to a datetime. This is not valid, and produces the following error:
Dec 11 07:11:09 raspberrypi hass[3669]: 2018-12-11 07:11:09 ERROR (MainThread) [homeassistant.components.websocket_api.decorators] Unexpected exception
Dec 11 07:11:09 raspberrypi hass[3669]: Traceback (most recent call last):
Dec 11 07:11:09 raspberrypi hass[3669]:   File "/home/pi/.local/lib/python3.5/site-packages/homeassistant/components/websocket_api/decorators.py", line 16, in _handle_async_response
Dec 11 07:11:09 raspberrypi hass[3669]:     await func(hass, connection, msg)
Dec 11 07:11:09 raspberrypi hass[3669]:   File "/home/pi/.local/lib/python3.5/site-packages/homeassistant/components/camera/__init__.py", line 463, in websocket_camera_thumbnail
Dec 11 07:11:09 raspberrypi hass[3669]:     image = await async_get_image(hass, msg['entity_id'])
Dec 11 07:11:09 raspberrypi hass[3669]:   File "/home/pi/.local/lib/python3.5/site-packages/homeassistant/components/camera/__init__.py", line 93, in async_get_image
Dec 11 07:11:09 raspberrypi hass[3669]:     image = await camera.async_camera_image()
Dec 11 07:11:09 raspberrypi hass[3669]:   File "/home/pi/.local/lib/python3.5/site-packages/homeassistant/components/camera/proxy.py", line 155, in async_camera_image
Dec 11 07:11:09 raspberrypi hass[3669]:     now < self._last_image_time + self._image_refresh_rate):
Dec 11 07:11:09 raspberrypi hass[3669]: TypeError: unorderable types: datetime.datetime() < float()

I'm actually not sure how it ever worked, unless image_refresh_rate is not set... :-/
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

@PhracturedBlue , as the original author, any thoughts? Did I miss something?

FYI, github will properly work after a force-push without closing the ticket.  You should not need to close your own tieckets with homeassistant (unless you don't actually want your fix to be merged of course)

I know; I closed it because I had pushed something that I then realized was wrong, and I didn't want to clutter the comment thread. My intention was to re-open once the branch looked the way I wanted it to, and only then let people like you and the CI see it.


Drop container registry tarball

The tarball for the container registry chart is generated by helm package, from the assets/container-registry hierarchy.
There is no need to have the tarball be a part of the repository. The assets are enough.
Remove the tarball, and modify the Makefile to generate it as part of the embed_files target.
IOW make the update_registry target a dependency of embed_files.

Of course, if there is good reason to keep the tarball, add this reason to the developer documentation, to preemptively answer the question.

Done here: https://github.com/epinio/epinio/pull/413


Composite cookers don't get "OnDataAvailable" called when second trace in a session is opened

My composite cooker pipeline works fine on first trace that is opened. But when I open the second trace within the same WPA session and I do "tableData.QueryOutput(dataOutputPath)" within BuildTable, OnDataAvailable never gets called in my composite cooker and the query returns stale data from the first trace. Interestingly, the stale data doesn't even show up in the table.
The source cookers appear to be properly updated for the second trace.
It looks like OnDataAvailable is not called a second time because InstanceInitialized is never set back to false in GetOrCreateInstance

Thanks @KyleStorck. I'm taking a look at this.


[SPARK-17389] [SPARK-3261] [MLLIB] Significant KMeans speedup with better choice of init steps, optimizing to remove 'runs'

What changes were proposed in this pull request?

Deprecate KMeans 'runs' param which was a no-op since 2.0
optimize/simplify code now that runs = 1 always
most significantly, choose initializationSteps = 2 as default for default k-means|| init because the paper implies that's as optimal and is much faster.

How was this patch tested?
Jenkins

Test build #64894 has started for PR 14948 at commit dbed7d7.

Test build #64894 has finished for PR 14948 at commit dbed7d7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Test build #64896 has started for PR 14948 at commit 0a51e1e.

Test build #64896 has finished for PR 14948 at commit 0a51e1e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

Test build #64899 has started for PR 14948 at commit e7f12fa.

Note this also now resolves SPARK-3261. This change already means that with k-means|| init, fewer than k cluster centers may be returned, which is probably correct (and faster). Now random init will also return no duplicate centers, and thus < k clusters when the input has size < k.

Test build #64899 has finished for PR 14948 at commit e7f12fa.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

I think https://github.com/apache/spark/pull/14937 also removes runs. cc @yanboliang can we coordinate these PRs?

Ah yeah, it also removes runs from k-means||. The good news is I think these changes are actually not overlapping for the most part, and where they do, they're essentially the same change.
@yanboliang what do you think of this? This takes out runs entirely and I think simplifies the code even a bit further. But the real win was reducing the default init steps. I'm also here trying to fix the fact that duplicate centroids can be returned.

Yep, these changes are not overlapping with #14937 for the most part, and they are actually same changes for the overlapping part. Let's make this PR focus on the optimization of initialization step and to fix it's likely to return duplicate centroids.
For reducing initialization steps to 2 for default k-means||, I wonder the impact to the total training iteration number. It will definitely reduce the initialization time, but whether it will introduce more training iterations due to not good enough initial centers? If it does not introduce extra iterations for most cases, I think it's OK. Or we should trade off the initialization and training iterations. Thanks!

@yanboliang I'm going to close this PR and instead 'port' a few changes I made in this version for your consideration. Yours should be the primary PR for removing runs I think. I'll break out the two other changes in separate PRs.
You're right that this is the question regarding init steps -- more steps could make for a better clustering, which could indirectly mean a faster convergence too. Maybe you can check my work. I think the default of 5 was taken from Table 6 in http://theory.stanford.edu/~sergei/papers/vldb12-kmpar.pdf but it's not saying 5 is necessarily an optimal value. In fact Figure 5.2/5.3 imply that (for l/k=2 as we've chosen here) there's virtually no improvement for more than 2 init steps.
Coupled with the fact that an init step now takes about 5x longer than a single iteration, it seems like 5 is pretty expensive as a default too.


Add padding to QR code

The QR code feels really tight in the screenshot below, especially relative to the text underneath.

Are you having problems with it being recognized? We have a comfortably larger size than is required by the standard and I haven't seen issues. If you are truly having problems please reopen and let me know in what circumstances it doesn't resolve.

This report is about aesthetics. Generally images and text have "breathing space" between them. Check out the lack of padding in the screenshot below. Please reopen.

I renamed the issue because it was confusing. Spacing below the QR code is what you were asking for.

Cheers. In CSS there's a property called padding which is may do the job here.


Nuxt guide?

Is this compatible with SSR?
If so, how would we use it? And I don't mean disabling SSR by using ssr: false or client-only.

Actually just downloading the component & placing it in my components worked.
However I'm experience severe popin when doing hardrefreshes / loading in directly from a link.
It starts off expanded & reverts to closed.. Any idea?


fetch issue in AWS lambda

Hello Team,
I am currently attempting to integrate Cohere embed within an AWS Lambda function and have come across a frustrating issue. It appears that the library interferes with the global "fetch" function that is provided by Node.js version 18, resulting in a malfunction that causes other libraries that utilize "fetch" to fail. The specific error message I'm receiving is "TypeError: fetch is not a function." Could anyone suggest a potential solution or workaround for this problem?
Thank you for your assistance.

Hey @alex-cortenix thanks for reporting, we're seeing similar issues with #110. Will sync with @dsinghvi and have a fix for you asap.

you may have luck depending on 7.6.0 if that unblocks you for now. This was the version that used axios, not fetch. Thanks

Closing in favour of https://github.com/fern-api/fern/issues/2555

Hey @alex-cortenix this should be working as of 7.7.5. Let me know if you have any further issues! Thanks

Hello I'm using @langchain/cohere with CohereRerank which uses cohere-ai client version 7.7.7 running on lambda and getting the error
CohereError: fetchFn is not a function

Could this still be related? Anyone managed to make it work with lambda?

Found the cause of the error, in my case if I  update the  compiled js code to be  const response = yield fetchFn.default insteadof const response = yield fetchFn under makeRequest in Fetcher file, it works. I suspect it has something to do with how require("node-fetch") is used.  I'm using node 18


Psw as nodes

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 4

Clones added
============
- src/tests/possumwood/subnetwork_rename.cpp  1
- src/apps/possumwood/node_menu.cpp  1
- src/tests/possumwood/subnetwork_from_file.cpp  3

Clones removed
==============
+ src/apps/possumwood/main_window.cpp  -1
+ src/tests/possumwood/json.cpp  -13

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 3

Clones added
============
- src/tests/possumwood/subnetwork_from_file.cpp  3
- src/apps/possumwood/node_menu.cpp  1
- src/tests/possumwood/subnetwork_rename.cpp  1

Clones removed
==============
+ src/apps/possumwood/main_window.cpp  -1
+ src/tests/possumwood/json.cpp  -13

See the complete overview on Codacy


Use shell for execution of .cmd (tsp-server.cmd)

fixes #4343. shell needs to be used for executing .cmd file in newer nodejs version (a breaking change from nodejs security release). more detail can be found in the issue.

All changed packages have been documented.

:white_check_mark: typespec-vscode

Show changes
typespec-vscode - fix ✏

Use "shell" when spawning execution of .cmd file(i.e. tsp-server.cmd) in windows

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


AMD, Ubuntu, GLFW and mouse, that does not work

I'm looking for some help with visualization using GLFW library.
My models are simulated and rendered correctly, but the viewer window does not respond to mouse and keyboard inputs.  I have attempted the default mujoco viewer, mujoco python viewer, and a custom GLFW-based viewer, but the issue persists. I suspect the issue lies with my AMD graphics card.
I am running Ubuntu 22.04.4 on an AMD Radeon RX 6600M graphics card and AMD Ryzen 7 5800H processor. When running Ubuntu normally, the mouse and keyboard do not function, and for some reason, the title box becomes black with the title written in bold.
mouse_does_not_work.webm
When I run Ubuntu in recovery mode, however, everything returns to normal, and I am able to interact with the model using a mouse and keyboard. Additionally, the title bar becomes white with a default font.
mouse_does_work.webm
After recovery mode “some graphic drivers require a full graphical boot and so will fail when resuming from recovery”. It appears that something has been disabled after recovery mode, allowing the use of the viewer with mouse interaction.
This issue did not occur a few weeks ago.
Could you please assist me in resolving this issue? I would appreciate any suggestions or guidance you may have. Thank you for your attention!

There's a long-standing issue with the GUI when running in Windows with AMD hardware, but I believe this is the first time we have a complaint from a Linux user...
Before we dig too deep, could you please check if the issue first appears at commit eb844a4b7725822c609ef6a3403c0f1c5635e693 for you?

Duplicate of #639


Add .map  method to feed-base.

This function is designed for response realtime processing when .all method is in progress.
This is useful when you are collecting real large amount of data, and you have not so much RAM.
The return of this function will be saved in RAM  instead of original response.
For example, if you need only ids, you can redefine this method in your feed instance like this
const feed = new AccountFollowingFeed();
feed.map = follower => follower.id;
feed.all()
  .then( followers => console.log(followers) ) // here will be only ids.

👍


Features

refactor and fix bug

looks like bug all fixed.

rename with preview

ready to merge

Awesome @glepnir hopefully after this patch I will be encourage to switch and start experimenting and reporting. Thanks a lot


Update meta.yaml

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

I'm not sure how to fix the current error I'm getting on CI with qhull (not an expert, just had a bug and thought upgrading qhull would fix it, instead I downgraded and things are working now)


Remove redundancy in TV

Is your feature request related to a problem? Please describe.
Now we have total_variation metric and TVLoss, which are exactly the same things.
Describe the solution you'd like
One of entities needs to removed. Another, probably, renamed.

Together with @denproc decided not to do that because:

Metric and loss are different entities meaning that it might be not intuitive to use something called loss for computation of metric and vice versa
Metric and loss might have slightly different interfaces
Loss can reuse metric function anyway

As a bottom line: metrics should be implemented as functions with minimal and independent API, losses need to be implemented as classes to store state and sattisfy PyTorch convention and heavily reuse code of metrics when possible.


refactor: upgrade repo

The repo is currently broken, this MR fixes it:

Upgrade all dependencies
Upgrade project structure to comply with Poetry expectations
Manage all dependencies through Poetry and get rid of requirements.txt
Manage gpt-migrate execution through Poetry as well using poetry run gpt-migrate
Use relative path for internal file reading
Add a maxtokens options to allow models using only 4096 tokens
Prevent gpt-migrate from crashing when model response content contains Python None
Prevent gpt-migrate from crashing when the project to convert contains nested directories
Use openai models by default

Fixing:

#50
#48
#46
#45
#43 (use openai as default)
#42
#41

Your PR seems to work, thanks a lot!
Although I'm not quite familiar with poetry, I had to mv  ./src/gpt_migrate/ ./gpt_migrate, because it wouldn't recognize gpt-migrate as an internal package.

Yeah, I encountered the same issue when I tried to run main.py:
% python main.py --model gpt-4-32k --targetlang nodejs
Traceback (most recent call last):
  File "/Users/nateaune/Documents/code/gpt-migrate-fixed/src/gpt_migrate/main.py", line 7, in <module>
    from gpt_migrate.ai import AI
ModuleNotFoundError: No module named 'gpt_migrate'

This occurred after poetry complained about gpt_migrate not being a package:
% poetry install
Installing dependencies from lock file

Package operations: 13 installs, 31 updates, 0 removals

  - Downgrading typing-extensions (4.12.2 -> 4.10.0)
  - Installing annotated-types (0.6.0)
  - Downgrading certifi (2024.8.30 -> 2024.2.2)
  - Downgrading charset-normalizer (3.4.0 -> 3.3.2)
  - Downgrading exceptiongroup (1.2.2 -> 1.2.0)
  - Downgrading idna (3.10 -> 3.6)
  - Downgrading pydantic-core (2.27.0 -> 2.16.3)
  - Downgrading urllib3 (2.2.3 -> 2.2.1)
  - Downgrading filelock (3.16.1 -> 3.13.1)
  - Downgrading anyio (4.6.2.post1 -> 4.3.0)
  - Downgrading frozenlist (1.5.0 -> 1.4.1)
  - Downgrading fsspec (2024.10.0 -> 2024.2.0)
  - Downgrading httpcore (1.0.7 -> 1.0.4)
  - Installing jsonpointer (2.4)
  - Downgrading multidict (6.1.0 -> 6.0.5)
  - Installing orjson (3.9.15)
  - Downgrading packaging (24.2 -> 23.2)
  - Updating pydantic (1.10.8 -> 2.6.3)
  - Downgrading pyyaml (6.0.2 -> 6.0.1)
  - Downgrading requests (2.32.3 -> 2.31.0)
  - Downgrading tqdm (4.67.0 -> 4.66.2)
  - Downgrading attrs (24.2.0 -> 23.2.0)
  - Downgrading httpx (0.27.2 -> 0.27.0)
  - Downgrading huggingface-hub (0.26.2 -> 0.21.3)
  - Installing jsonpatch (1.33)
  - Updating langsmith (0.0.92 -> 0.1.10)
  - Installing markupsafe (2.1.5)
  - Installing regex (2023.12.25)
  - Downgrading tenacity (8.5.0 -> 8.2.3)
  - Downgrading yarl (1.17.1 -> 1.9.4)
  - Installing zipp (3.17.0)
  - Downgrading aiohttp (3.11.2 -> 3.9.3)
  - Installing importlib-metadata (7.0.1)
  - Installing jinja2 (3.1.3)
  - Installing langchain-core (0.1.27)
  - Updating openai (0.27.10 -> 1.13.3)
  - Downgrading termcolor (2.5.0 -> 2.4.0)
  - Installing tiktoken (0.6.0)
  - Downgrading tokenizers (0.20.3 -> 0.15.2)
  - Installing langchain-openai (0.0.8)
  - Updating litellm (0.1.213 -> 1.28.0)
  - Installing ruff (0.2.2)
  - Downgrading typer (0.9.4 -> 0.9.0)
  - Updating yaspin (2.5.0 -> 3.0.1)

Installing the current project: gpt-migrate (0.1.0)
gpt_migrate is not a package.


Read and Write The Driver's Dependency Graph For Cross-Module Builds

The refactoring of the incremental compilation state class is in three pieces:

Formalize the type of the InitialState computed by the initializer
Internalize computeModuleDependencyGraph and instead make a unified computeInitialState entrypoint (we'll need this for testing later)
Divide the status quo and cross-module initial state computations. There is no change to the status quo outside of the breakup of Driver.getBuildInfo

The cross-module path is slightly different than the status quo. For one, the incremental build need not fail entirely when either the build record or dependency graph cannot be read. In fact, it is a requirement that the incremental build proceed but schedule every single input file to rebuild, otherwise we won't have a module dependency graph to serialize!
As an aside, we ought to consider unifying the build record with the module dependency graph state we're writing here. They're read and written in lock-step when cross-module builds are turned on.

@swift-ci test

@swift-ci test


Feature Request: Silverlight Support

Yes, I know, no body uses Silverlight anymore. But for those who do it would be really great to have support for it in VS Code especially as VS 2017 does not support Silverlight anymore.

Hi, I appreciate the request. Unfortunately, we can't prioritize having support for legacy technologies like Silverlight in C# for VS Code. I haven't tried one, but I would expect Silverlight projects to at least provide IntelliSense in VS Code. However, beyond that there isn't much we can do for VS Code.

I'd definitely be willing to take a bug report for that to see if something can be done. :smile: Could you provide a bit of information to help us investigate?

What operating system are you running on?
VS Code version:
C# for VS Code version:
Could you provide your OmniSharp Log after opening a Silverlight project? You can grab this by selecting View->Output from the menu and selecting OmniSharp Log from the dropdown at the top-right corner of the Output pane.

I get this error on Windows 10, VS Code  1.11.1:
    Loading project from 'e:\Code\D\FOOO.csproj'.

    The Silverlight 4 SDK is not installed.

    Failed to process project file 'e:\Code\D\FOO.csproj

However, I do have SL4 SDK installed. Do I have to set a path somewhere?

Is that the whole log?

Also, what version of C# for VS Code do you have installed?


Remove version: 8x8.VirtualOfficeDesktop version <IP_ADDRESS>

Consolidating into 8x8.Work. Related to: #135119
Microsoft Reviewers: Open in CodeFlow

URL: https://vod-updates.8x8.com/ga/work-64-msi-v8.6.2-9.msi
Status Code: 200
(Automated message - build 656)

URL: https://vod-updates.8x8.com/ga/work-64-msi-v8.6.2-9.msi
Status Code: 200
(Automated message - build 656)


OpenAPI research

https://apihandyman.io/writing-openapi-swagger-specification-tutorial-part-1-introduction/


[stdlib] Used map and guard for nil handling

Changed nil handling by using map statements.
I think these changes should have guard let or map as it is more expressive.
Please let me know if anything else needed.
Thanks to swift team

@NachoSoto Thinking about that also find these changes in #193. I am making these changes. Thanks for advice

done changes to handle nil by map.

@gribozavr  Thanks for reviewing this. I have done the changes. I also done some performance Test and I get result same. All if/nil , map and guard are tanking same amount of time. You can find gist here
Please let me know if any other changes required.
One thing more. I have run the test on swift master branch(Apple master this does not include my changes) and found some of test are failing on my machine. Here is [output] (https://gist.github.com/codestergit/a466da4b6d197b25b3c1). Do you know what stupid thing I have done
Thanks

@codestergit I ran the tests and couldn't reproduce the failure.

@gribozavr  Thank for merging. Sorry but just for my knowledge want to know the index++ side effect. I am not that much good with higher order functions.How map will affect or behave different way. Optional.map has following implementation
public func map(@noescape f: (Wrapped) throws -> U) rethrows -> U? {
switch self {
case .Some(let y):
return .Some(try f(y))
case .None:
return .None //I think it will return as it is and f will not execute and index++ should not happen
}
}
so it is also returning early if our base.next() return nil value or .None. It will not execute clousre and count value should remain same. I have tested this and both are giving same result. Is I missing something. Thanks for being so kind :)

@codestergit It should behave correctly just as you expect, it is just poor style to use side-effecting operations with APIs influenced by the functional paradigm, like map().

Thanks @gribozavr .


Application middleware not called if route is not matched

The documentation states:

Application middleware is invoked for every incoming HTTP request.

In my tests, this is not true; application middleware is only invoked if there is a matching route somewhere in the application. After creating a test project with php composer.phar create-project slim/slim-skeleton slimtest, I added the following block of code below $app = AppFactory::create();:
$app->add(function ($request, $handler) {
        $response = new Slim\Psr7\Response();
        $response->getBody()->write('testing');
        return $response;
});

If I request / from the application, I see the output testing. If I request /foo, I see the output:
{
    "statusCode": 404,
    "error": {
        "type": "RESOURCE_NOT_FOUND",
        "description": "Not found."
    }
}

This seems to indicate that the middleware was not executed. Indeed, putting die() in the middleware will cause the request to terminate when requesting / but the output for /foo remains unchanged.
I'm not sure if this is a doc bug or a behavioral bug, but the current behavior does not match the documentation.
This was tested against 4.3.0.

That’s because routing is done before your middleware gets reached and then throws an exception which is caught by the error middleware which will short circuit and return a response.
Add your middleware after ErrorMiddleware and it will get reached first.
Remember middleware is executed in Last In First Out order.


[improve][broker] Add fine-grain authorization to retention admin API

Motivation
Add fine-grain authorization to retention admin API so that it can be controlled at a more fine-grain level.
Modifications

Update getRetention, add PolicyName.RETENTION with READ check
Update setRetention & removeRetention, add PolicyName.RETENTION with WRITE check

Verifying this change

[x] Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:

[x] The REST endpoints

Documentation

[x] doc-not-needed

@mattisonchao We have a conflict in branch-3.0. can you help to cherry-pick this to branch-3.0?


Upgrade python version

The latest release of python is now 3.12, which means our 3.8 is now 4 versions back, and we should consider upgrading.
I would not go all the way to 3.12 which was just released, but I'd rather push to 3.10.
according to https://devguide.python.org/versions/ 3.10 is now not recieving any updates rather than security, while 3.11 and 3.12 are still recieving bugfixes.
I tested 3.10 and at least for the hextof tutorial notebook and the tests, it worked just fine.
Also, I'm a big fan of 3.10, as it greatly improves readability of type hihts and their flexibility.
No need for Union or capitalized List Dict etc...
def foo(x: int | list[int]) -> None:
   if not isinstance(x, int | float):
       raise ValueError()

There are also other performance improvements and a case funtion which is nice
https://docs.python.org/3/whatsnew/3.10.html
On the other hand:

Python 3.11 is between 10-60% faster than Python 3.10. On average, we measured a 1.25x speedup on the standard benchmark suite. See Faster CPython for details.

I am absolute up for making sure our code is compatible with recent python version, so we should extend our multiversion tests accordingly. However, I would keep compatibility to python 3.8, because it is the default python shipped with many long-term support os-es, e.g. ubuntu 20.04, which has support until 2025.

I wonder if using the new features of python 3.10 would break compatibility with 3.8.
I have the feeling I did this and it worked, but i need to test to be sure

Using the 3.10+ specific features definitely for example cause linting errors with other versions.
If we don't change the code, there shouldn't be any problem with moving to 3.10, as all our tests already show it works fine. That means that the dependencies we have are all compatible with 3.10.

Just my comments. I am totally okay with moving to 3.10. We can change our linting workflow to adapt to it as well.

I tested functions using 3.10 functionalities in 3.8, and it obviously does not work... 😭
We probably need to stick to developing in the oldest version we want to keep compatibility with, which is a pitty.
I would therefore propose we find really good reasons why to stick with 3.8 and not upgrade... the "its the default in an os" does not feel like a good enough reason to me.

There only point regarding default on os is: The standard user on maxwell or any linux system (most users) will be having python 3.8 preinstalled. Then they just need to do pip install (or in their venv) to install sed. To have multiple python versions isn't that difficult but just additional steps for user.
Though, just to counter that argument, users on systems other than linux are not exposed to the same python version e.g. on mac the default is 3.9
I don't think it's a necessarily strong argument

My favourite feature is the simpler type hints probably, but sure not worth big changes.
I'd be curious about performance improvements, but those we should get by just using a more recent version, no need for extra features.

So I think we are sticking with 3.8.
I'd suggest we update the toml file to at least allow for 3.11 (maybe 3.12 as well). We could of course add that to our tests.

We could consider this:
https://stackoverflow.com/questions/63939138/is-there-a-way-to-use-python-3-9-type-hinting-in-its-previous-versions


require request 2.85.1

request 2.85.1 requires hawk 6.0.2, which requires boom 4.x.x, which requires hoek 4.x.x. (hoek 2.16.3 has a security vulnerability).

If you don't want to use current request, how do you propose getting a current hoek? How will you address #2355?

Please respect our time by search for issues before opening a new one. Your questions have all been answered many times.

I see from #2288 that this has been known for at least six weeks. Sigh.

It's know and unpatched on purpose because request broke semver by dropping
node < 4 support.
On Sat., 28 Apr. 2018, 9:33 am Paul Schreiber<EMAIL_ADDRESS>wrote:

I see from #2288 https://github.com/sass/node-sass/issues/2288 that
this has been known for at least six weeks. Sigh.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/pull/2356#issuecomment-385118888, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAjZWNjhcLYwwsMQ23bKHzRIyQZFHEktks5ts6rOgaJpZM4TrBkL
.

For anyone that is looking at this issue, the dependency upgrade is in the works with the release of node-sass 5.  See https://github.com/sass/node-sass/pull/2312


internal: Generate ast nodes for each ast trait

Generate a DynTrait node per ast trait that implements the trait itself as well as conversions via the AstNode trait. This is a trick already employed in hir_def::attr with AttrsOwner where it was manually implemented for.
This basically gives us stack trait objects for these(only useful for hir_def::attr currently) as well as simple conversions of SyntaxNode to a trait, in cases where only a result of a function call of such a trait is of interest.
It doesn't have many uses yet but as its autogenerated it doesn't add any maintenance costs.
bors r+

bors retry

Yeah, I've been debating whether we should have this for years. I wonder if we should call those AnyAttrOwner rather that DynAttrOwner?
In a similar genre, I'd love to rename XxxOwner to HasXxx one day....

Ye, AnyAttrOwner seems like a better name, I like that one. Same for Has over Owner


[WFLY-4777] Allow expressions on wsdl-uri-scheme attribute

The same as https://github.com/wildfly/wildfly/pull/7608 but for 9.x

Windows Build 122 is now running using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65

Linux Build 120 is now running using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65

Linux with security manager Build 115 is now running using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65

Linux with security manager Build 115 outcome was SUCCESS using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65
Summary: Tests passed: 828, ignored: 319 Build time: 0:06:17

Windows Build 122 outcome was SUCCESS using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65
Summary: Tests passed: 2870, ignored: 374 Build time: 0:47:04

Linux Build 120 outcome was FAILURE using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65
Summary: Tests failed: 2 (1 new), passed: 2867, ignored: 374, muted: 1 Build time: 0:50:17
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest: <no details avaliable>

org.jboss.as.test.clustering.cluster.web.authentication.FormAuthenticationWebFailoverTestCase(SYNC-tcp).test: <no details avaliable>

retest this please

Linux Build 121 is now running using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65

Linux with security manager Build 116 is now running using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65

Windows Build 123 is now running using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65

Linux with security manager Build 116 outcome was SUCCESS using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65
Summary: Tests passed: 828, ignored: 319 Build time: 0:05:57

Windows Build 123 outcome was SUCCESS using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65
Summary: Tests passed: 2870, ignored: 374 Build time: 0:47:48

Linux Build 121 outcome was FAILURE using a merge of 6bce15eccac8a5d381937a34bc0377757b17ef65
Summary: Tests failed: 2, passed: 2867, ignored: 374, muted: 1 Build time: 0:50:06
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest: <no details avaliable>

org.jboss.as.test.clustering.cluster.web.authentication.FormAuthenticationWebFailoverTestCase(SYNC-tcp).test: <no details avaliable>


Questions about writing service-traffic

Please answer these questions before submitting your issue.

Why do you submit this issue?
[x] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

At present, I found that the writing of service_traffic (ServiceTrafficDispatcher) is only triggered when analyzing the segment reported by the client. However, although some applications do not report segment, the instance information has been reported, such as jvm data. On the oap page, you must first check the service_traffic information before you can check the specific instance information (even if the client has uploaded the instance information, it cannot be queried on the oap page, but it can be obtained in the jvm related table of the ES). Is this reasonable? Would it be better if the writing of service_traffic is triggered in the register of the client?

Which agent are you talking about? Are you really facing a case or just guessing when read source codes?

Really facing a case about this. Our agent only uses the dubbo plugin, and we have a service A which has no dubbo-related logic, but we want to monitor its machine and jvm information. However, because service_traffic does not have the service information, we cannot search on the oap background service page, but the jvm information of the service is actually stored in es.

It is most likely you changed the source codes, rather than the official agent. Where is your codebase from?

I will check it carefully, we did change the source code, but did not change this place. In addition, we use the kafka-reporter-plugin

Do you cut the grpc channel when you use kafka reporter? You should know, once you change source codes, you are on your own.
There is nothing the community could do, or should do.

Thanks a lot for information, was searching for it


Update build.gradle.kts

Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 98.238% (-0.4%) from 98.678% when pulling 890f4a245dae696ea56966be5c3d6d662c1fe3d7 on update-to-3.2.0-SNAPSHOT into 7fb9e35577c3a3eea5b81e0f7addbe648eee48eb on main.


Add support fo RN 0.57 (+ fix deprecated configuration)

I would also consider upgrading the default versions of sdk to this (from RN build.gradle)
buildToolsVersion = "27.0.3"
minSdkVersion = 16
compileSdkVersion = 27
targetSdkVersion = 26

Wouldn't that make it less downwards compatible with devices?

Wouldn't that make it less downwards compatible with devices?

Oh yes, that's a good point. Let's keep the current, if it doesn't cause any issues.


Add bsnes

Add bsnes emulator to this bucket.
https://github.com/bsnes-emu/bsnes

Pull request: https://github.com/Calinou/scoop-games/pull/549


gbc emulator options

"gameboy_model",
  "System - Emulated Model (Requires Restart)",
  "Emulated Model (Requires Restart)",
  "Chooses which system model the content should be started on. Certain games may activate special in-game features when ran on specific models. This option requires a content restart in order to take effect.",
  NULL,
  "system",
  {
     { "Auto",                 "Auto Detect DMG/CGB"                       },
     { "Auto (SGB)",           "Auto Detect DMG/SGB/CGB"                   },
     { "Game Boy",             "Game Boy (DMG-CPU B)"                      },
     { "Game Boy Color C",     "Game Boy Color (CPU-CGB C) (Experimental)" },
     { "Game Boy Color",       "Game Boy Color (CPU-CGB E)"                },
     { "Game Boy Advance",     NULL },
     { "Super Game Boy",       "Super Game Boy NTSC"                       },
     { "Super Game Boy PAL",   NULL },
     { "Super Game Boy 2",     NULL },
     { NULL, NULL },
  },
  "Auto"

},
  "gameboy_auto_sgb_model",
  "System - Auto Detected SGB Model (Requires Restart)",
  "Auto Detected SGB Model (Requires Restart)",
  "Specifies which model of Super Game Boy hardware to emulate when SGB content is automatically detected. This option requires a content restart in order to take effect.",
  NULL,
  "system",
  {
     { "Super Game Boy",       "Super Game Boy NTSC" },
     { "Super Game Boy PAL",   NULL },
     { "Super Game Boy 2",     NULL },
     { NULL, NULL },
  },
  "Super Game Boy"

},
  "gameboy_rtc",
  "System - Real Time Clock Emulation",
  "Real Time Clock Emulation",
  "Specifies how the emulation of the real-time clock feature used in certain Game Boy and Game Boy Color games should function.",
  NULL,
  "system",
  {
     { "sync to system clock", "Sync to System Clock" },
     { "accurate",             "Accurate"             },
     { NULL, NULL },
  },
  "sync to system clock"

},
  "gameboy_mono_palette",
  "Video - GB Mono Palette",
  "GB Mono Palette",
  "Selects the color palette that should be used when playing Game Boy games.",
  NULL,
  "video",
  {
     { "greyscale", "Greyscale"               },
     { "lime",      "Lime (Game Boy)"         },
     { "olive",     "Olive (Game Boy Pocket)" },
     { "teal",      "Teal (Game Boy Light)"   },
     { NULL, NULL },
  },
  "greyscale"

},
  "gameboy_color_correction_mode",
  "Video - GBC Color Correction",
  "GBC Color Correction",
  "Defines which type of color correction should be applied when playing Game Boy Color games.",
  NULL,
  "video",
  {
     { "emulate hardware",    "Modern – Balanced"            },
     { "accurate",            "Modern – Accurate"            },
     { "preserve brightness", "Modern – Boost Contrast"      },
     { "reduce contrast",     "Reduce Contrast"              },
     { "correct curves",      "Correct Color Curves"         },
     { "harsh reality",       "Harsh Reality (Low Contrast)" },
     { "off",                 "Disabled"                     },
     { NULL, NULL },
  },
  "emulate hardware"

},
  "gameboy_light_temperature",
  "Video - Ambient Light Temperature",
  "Ambient Light Temperature",
  "Simulates an ambient light's effect on non-backlit Game Boy screens, by setting a user-controlled color temperature. This option has no effect if the content is run on an original Game Boy (DMG) emulated model.",
  NULL,
  "video",
  {
     { "1.0",   "1000K (Warmest)"       },
     { "0.9",   "1550K" },
     { "0.8",   "2100K" },
     { "0.7",   "2650K" },
     { "0.6",   "3200K" },
     { "0.5",   "3750K" },
     { "0.4",   "4300K" },
     { "0.3",   "4850K" },
     { "0.2",   "5400K" },
     { "0.1",   "5950K" },
     { "0",     "6500K (Neutral White)" },
     { "-0.1",  "7050K" },
     { "-0.2",  "7600K" },
     { "-0.3",  "8150K" },
     { "-0.4",  "8700K" },
     { "-0.5",  "9250K" },
     { "-0.6",  "9800K" },
     { "-0.7", "10350K" },
     { "-0.8", "10900K" },
     { "-0.9", "11450K" },
     { "-1.0", "12000K (Coolest)"       },
     { NULL, NULL },
  },
  "0"

},
  "gameboy_border",
  "Video - Display Border",
  "Display Border",
  "Defines when to display an on-screen border around the content.",
  NULL,
  "video",
  {
     { "always",              "Always"                  },
     { "Super Game Boy only", "Only for Super Game Boy" },
     { "never",               "Disabled"                },
     { NULL, NULL },
  },
  "Super Game Boy only"

},
  "gameboy_high_pass_filter_mode",
  "Audio - Highpass Filter",
  "Highpass Filter",
  "Applies a filter to the audio output, removing certain pop sounds caused by the DC Offset. If disabled, the sound will be rendered as output by the Game Boy APU, but popping effects will be heard when the emulator is paused or resumed. 'Accurate' will apply a global filter, masking popping sounds while also reducing lower frequencies. 'Preserve Waveform' applies the filter only to the DC Offset.",
  NULL,
  "audio",
  {
     { "accurate",         "Accurate"              },
     { "remove dc offset", "Preserve Waveform"     },
     { "off",              "Disabled"              },
     { NULL, NULL },
  },
  "accurate"

},
  "gameboy_audio_interference",
  "Audio - Interference Volume",
  "Interference Volume",
  "Controls the volume of the buzzing effect caused by the electrical interference between the Game Boy SoC and the system speakers.",
  NULL,
  "audio",
  {
     { "0",   "0%"   },
     { "5",   "5%"   },
     { "10",  "10%"  },
     { "15",  "15%"  },
     { "20",  "20%"  },
     { "25",  "25%"  },
     { "30",  "30%"  },
     { "35",  "35%"  },
     { "40",  "40%"  },
     { "45",  "45%"  },
     { "50",  "50%"  },
     { "55",  "55%"  },
     { "60",  "60%"  },
     { "65",  "65%"  },
     { "70",  "70%"  },
     { "75",  "75%"  },
     { "80",  "80%"  },
     { "85",  "85%"  },
     { "90",  "90%"  },
     { "95",  "95%"  },
     { "100", "100%" },
     { NULL, NULL },
  },
  "0"

},
  "gameboy_rumble",
  "Input - Rumble Mode",
  "Rumble Mode",
  "Defines which type of content should trigger rumble effects.",
  NULL,
  "input",
  {
     { "all games",            "Always"                        },
     { "rumble-enabled games", "Only for rumble-enabled games" },
     { "never",                "Never"                      },
     { NULL, NULL },
  },
  "rumble-enabled games"

},
/* Core options used in dual cart mode */
{
"gameboy_link",
"System - Link Cable Emulation",
"Link Cable Emulation",
"Enables the emulation of the link cable, allowing communication and exchange of data between two Game Boy systems.",
NULL,
"system",
{
{ "enabled",  "Enabled" },
{ "disabled", "Disabled" },
{ NULL, NULL },
},
"enabled"
},
  "gameboy_screen_layout",
  "System - Screen Layout",
  "Screen Layout",
  "When emulating two systems at once, this option defines the respective position of the two screens.",
  NULL,
  "system",
  {
     { "top-down",   "Top-Down"   },
     { "left-right", "Left-Right" },
     { NULL, NULL },
  },
  "top-down"

},
  "gameboy_audio_output",
  "System - Audio Output",
  "Audio Output",
  "Selects which of the two emulated Game Boy systems should output audio.",
  NULL,
  "system",
  {
     { "Game Boy #1", NULL },
     { "Game Boy #2", NULL },
     { NULL, NULL },
  },
  "Game Boy #1"

},
  "gameboy_model_1",
  "System - Emulated Model for Game Boy #1 (Requires Restart)",
  "Emulated Model for Game Boy #1 (Requires Restart)",
  "Chooses which system model the content should be started on for Game Boy #1. Certain games may activate special in-game features when ran on specific models. This option requires a content restart in order to take effect.",
  NULL,
  "system",
  {
     { "Auto",                 "Auto Detect DMG/CGB"                       },
     { "Auto (SGB)",           "Auto Detect DMG/SGB/CGB"                   },
     { "Game Boy",             "Game Boy (DMG-CPU B)"                      },
     { "Game Boy Color C",     "Game Boy Color (CPU-CGB C) (Experimental)" },
     { "Game Boy Color",       "Game Boy Color (CPU-CGB E)"                },
     { "Game Boy Advance",     NULL },
     { "Super Game Boy",       "Super Game Boy NTSC"                       },
     { "Super Game Boy PAL",   NULL },
     { "Super Game Boy 2",     NULL },
     { NULL, NULL },
  },
  "Auto"

},
  "gameboy_auto_sgb_model_1",
  "System - Auto Detected SGB Model for Game Boy #1 (Requires Restart)",
  "Auto Detected SGB Model for Game Boy #1 (Requires Restart)",
  "Specifies which model of Super Game Boy hardware to emulate when SGB content is automatically detected for Game Boy #1. This option requires a content restart in order to take effect.",
  NULL,
  "system",
  {
     { "Super Game Boy",       "Super Game Boy NTSC" },
     { "Super Game Boy PAL",   NULL },
     { "Super Game Boy 2",     NULL },
     { NULL, NULL },
  },
  "Super Game Boy"

},
  "gameboy_model_2",
  "System - Emulated Model for Game Boy #2 (Requires Restart)",
  "Emulated Model for Game Boy #2 (Requires Restart)",
  "Chooses which system model the content should be started on for Game Boy #2. Certain games may activate special in-game features when ran on specific models. This option requires a content restart in order to take effect.",
  NULL,
  "system",
  {
     { "Auto",                 "Auto Detect DMG/CGB"                       },
     { "Auto (SGB)",           "Auto Detect DMG/SGB/CGB"                   },
     { "Game Boy",             "Game Boy (DMG-CPU B)"                      },
     { "Game Boy Color C",     "Game Boy Color (CPU-CGB C) (Experimental)" },
     { "Game Boy Color",       "Game Boy Color (CPU-CGB E)"                },
     { "Game Boy Advance",     NULL },
     { "Super Game Boy",       "Super Game Boy NTSC"                       },
     { "Super Game Boy PAL",   NULL },
     { "Super Game Boy 2",     NULL },
     { NULL, NULL },
  },
  "Auto"

},
  "gameboy_auto_sgb_model_2",
  "System - Auto Detected SGB Model for Game Boy #2 (Requires Restart)",
  "Auto Detected SGB Model for Game Boy #2 (Requires Restart)",
  "Specifies which model of Super Game Boy hardware to emulate when SGB content is automatically detected for Game Boy #2. This option requires a content restart in order to take effect.",
  NULL,
  "system",
  {
     { "Super Game Boy",       "Super Game Boy NTSC" },
     { "Super Game Boy PAL",   NULL },
     { "Super Game Boy 2",     NULL },
     { NULL, NULL },
  },
  "Super Game Boy"

},
  "gameboy_mono_palette_1",
  "Video - GB Mono Palette for Game Boy #1",
  "GB Mono Palette for Game Boy #1",
  "Selects the color palette that should be used when playing Game Boy games on Game Boy #1.",
  NULL,
  "video",
  {
     { "greyscale", "Greyscale"               },
     { "lime",      "Lime (Game Boy)"         },
     { "olive",     "Olive (Game Boy Pocket)" },
     { "teal",      "Teal (Game Boy Light)"   },
     { NULL, NULL },
  },
  "greyscale"

},
  "gameboy_mono_palette_2",
  "Video - GB Mono Palette for Game Boy #2",
  "GB Mono Palette for Game Boy #2",
  "Selects the color palette that should be used when playing Game Boy games on Game Boy #2.",
  NULL,
  "video",
  {
     { "greyscale", "Greyscale"               },
     { "lime",      "Lime (Game Boy)"         },
     { "olive",     "Olive (Game Boy Pocket)" },
     { "teal",      "Teal (Game Boy Light)"   },
     { NULL, NULL },
  },
  "greyscale"

},
  "gameboy_color_correction_mode_1",
  "Video - GBC Color Correction for Game Boy #1",
  "GBC Color Correction for Game Boy #1",
  "Defines which type of color correction should be applied when playing Game Boy Color games on Game Boy #1.",
  NULL,
  "video",
  {
     { "emulate hardware",    "Modern – Balanced"            },
     { "accurate",            "Modern – Accurate"            },
     { "preserve brightness", "Modern – Boost Contrast"      },
     { "reduce contrast",     "Reduce Contrast"              },
     { "correct curves",      "Correct Color Curves"         },
     { "harsh reality",       "Harsh Reality (Low Contrast)" },
     { "off",                 "Disabled"                     },
     { NULL, NULL },
  },
  "emulate hardware"

},
  "gameboy_color_correction_mode_2",
  "Video - GBC Color Correction for Game Boy #2",
  "GBC Color Correction for Game Boy #2",
  "Defines which type of color correction should be applied when playing Game Boy Color games on Game Boy #2.",
  NULL,
  "video",
  {
     { "emulate hardware",    "Modern – Balanced"            },
     { "accurate",            "Modern – Accurate"            },
     { "preserve brightness", "Modern – Boost Contrast"      },
     { "reduce contrast",     "Reduce Contrast"              },
     { "correct curves",      "Correct Color Curves"         },
     { "harsh reality",       "Harsh Reality (Low Contrast)" },
     { "off",                 "Disabled"                     },
     { NULL, NULL },
  },
  "emulate hardware"

},
  "gameboy_light_temperature_1",
  "Video - Ambient Light Temperature for Game Boy #1",
  "Ambient Light Temperature for Game Boy #1",
  "Simulates an ambient light's effect on non-backlit Game Boy screens, by setting a user-controlled color temperature applied to the screen of Game Boy #1. This option has no effect if the content is run on an original Game Boy (DMG) emulated model.",
  NULL,
  "video",
  {
     { "1.0",   "1000K (Warmest)"       },
     { "0.9",   "1550K" },
     { "0.8",   "2100K" },
     { "0.7",   "2650K" },
     { "0.6",   "3200K" },
     { "0.5",   "3750K" },
     { "0.4",   "4300K" },
     { "0.3",   "4850K" },
     { "0.2",   "5400K" },
     { "0.1",   "5950K" },
     { "0",     "6500K (Neutral White)" },
     { "-0.1",  "7050K" },
     { "-0.2",  "7600K" },
     { "-0.3",  "8150K" },
     { "-0.4",  "8700K" },
     { "-0.5",  "9250K" },
     { "-0.6",  "9800K" },
     { "-0.7", "10350K" },
     { "-0.8", "10900K" },
     { "-0.9", "11450K" },
     { "-1.0", "12000K (Coolest)"       },
     { NULL, NULL },
  },
  "0"

},
  "gameboy_light_temperature_2",
  "Video - Ambient Light Temperature for Game Boy #2",
  "Ambient Light Temperature for Game Boy #2",
  "Simulates an ambient light's effect on non-backlit Game Boy screens, by setting a user-controlled color temperature applied to the screen of Game Boy #2. This option has no effect if the content is run on an original Game Boy (DMG) emulated model.",
  NULL,
  "video",
  {
     { "1.0",   "1000K (Warmest)"       },
     { "0.9",   "1550K" },
     { "0.8",   "2100K" },
     { "0.7",   "2650K" },
     { "0.6",   "3200K" },
     { "0.5",   "3750K" },
     { "0.4",   "4300K" },
     { "0.3",   "4850K" },
     { "0.2",   "5400K" },
     { "0.1",   "5950K" },
     { "0",     "6500K (Neutral White)" },
     { "-0.1",  "7050K" },
     { "-0.2",  "7600K" },
     { "-0.3",  "8150K" },
     { "-0.4",  "8700K" },
     { "-0.5",  "9250K" },
     { "-0.6",  "9800K" },
     { "-0.7", "10350K" },
     { "-0.8", "10900K" },
     { "-0.9", "11450K" },
     { "-1.0", "12000K (Coolest)"       },
     { NULL, NULL },
  },
  "0"

},
  "gameboy_high_pass_filter_mode_1",
  "Audio - Highpass Filter for Game Boy #1",
  "Highpass Filter for Game Boy #1",
  "Applies a filter to the audio output for Game Boy #1, removing certain pop sounds caused by the DC Offset. If disabled, the sound will be rendered as output by the Game Boy APU, but popping effects will be heard when the emulator is paused or resumed. 'Accurate' will apply a global filter, masking popping sounds while also reducing lower frequencies. 'Preserve Waveform' applies the filter only to the DC Offset.",
  NULL,
  "audio",
  {
     { "accurate",         "Accurate"              },
     { "remove dc offset", "Preserve Waveform"     },
     { "off",              "disabled"              },
     { NULL, NULL },
  },
  "accurate"

},
  "gameboy_high_pass_filter_mode_2",
  "Audio - Highpass Filter for Game Boy #2",
  "Highpass Filter for Game Boy #2",
  "Applies a filter to the audio output for Game Boy #2, removing certain pop sounds caused by the DC Offset. If disabled, the sound will be rendered as output by the Game Boy APU, but popping effects will be heard when the emulator is paused or resumed. 'Accurate' will apply a global filter, masking popping sounds while also reducing lower frequencies. 'Preserve Waveform' applies the filter only to the DC Offset.",
  NULL,
  "audio",
  {
     { "accurate",         "Accurate"              },
     { "remove dc offset", "Preserve Waveform"     },
     { "off",              "disabled"              },
     { NULL, NULL },
  },
  "accurate"

},
  "gameboy_audio_interference_1",
  "Audio - Interference Volume for Game Boy #1",
  "Interference Volume for Game Boy #1",
  "Controls the volume of the buzzing effect caused by the electrical interference between the Game Boy SoC and the system speakers on Game Boy #1.",
  NULL,
  "audio",
  {
     { "0",   "0%"   },
     { "5",   "5%"   },
     { "10",  "10%"  },
     { "15",  "15%"  },
     { "20",  "20%"  },
     { "25",  "25%"  },
     { "30",  "30%"  },
     { "35",  "35%"  },
     { "40",  "40%"  },
     { "45",  "45%"  },
     { "50",  "50%"  },
     { "55",  "55%"  },
     { "60",  "60%"  },
     { "65",  "65%"  },
     { "70",  "70%"  },
     { "75",  "75%"  },
     { "80",  "80%"  },
     { "85",  "85%"  },
     { "90",  "90%"  },
     { "95",  "95%"  },
     { "100", "100%" },
     { NULL, NULL },
  },
  "0"

},
  "gameboy_audio_interference_2",
  "Audio - Interference Volume for Game Boy #2",
  "Interference Volume for Game Boy #2",
  "Controls the volume of the buzzing effect caused by the electrical interference between the Game Boy SoC and the system speakers on Game Boy #2.",
  NULL,
  "audio",
  {
     { "0",   "0%"   },
     { "5",   "5%"   },
     { "10",  "10%"  },
     { "15",  "15%"  },
     { "20",  "20%"  },
     { "25",  "25%"  },
     { "30",  "30%"  },
     { "35",  "35%"  },
     { "40",  "40%"  },
     { "45",  "45%"  },
     { "50",  "50%"  },
     { "55",  "55%"  },
     { "60",  "60%"  },
     { "65",  "65%"  },
     { "70",  "70%"  },
     { "75",  "75%"  },
     { "80",  "80%"  },
     { "85",  "85%"  },
     { "90",  "90%"  },
     { "95",  "95%"  },
     { "100", "100%" },
     { NULL, NULL },
  },
  "0"

},
  "gameboy_rumble_1",
  "Input - Rumble Mode for Game Boy #1",
  "Rumble Mode for Game Boy #1",
  "Defines which type of content should trigger rumble effects when played on Game Boy #1.",
  NULL,
  "input",
  {
     { "all games",            "Always"                        },
     { "rumble-enabled games", "Only for rumble-enabled games" },
     { "never",                "Never"                         },
     { NULL, NULL },
  },
  "rumble-enabled games"

},
  "gameboy_rumble_2",
  "Input - Rumble Mode for Game Boy #2",
  "Rumble Mode for Game Boy #2",
  "Defines which type of content should trigger rumble effects when played on Game Boy #2.",
  NULL,
  "input",
  {
     { "all games",            "Always"                        },
     { "rumble-enabled games", "Only for rumble-enabled games" },
     { "never",                "Never"                         },
     { NULL, NULL },
  },
  "rumble-enabled games"

},

@philj56

Thanks, but a big list of features from another emulator isn't particularly useful. Some of these features are already in GBCC, some are planned, and some aren't relevant.


How to create step by step onWheel gesture

Hi 👋
I'm trying to create some sort of sliding carousel based on the onWheel event.
I'd like to be able to trigger the onwheel from the left or the right and move the elements accordingly but step by step, not going all the way to the end or the beginning.
I have a csb here that shows my issue: https://codesandbox.io/s/onwheel-fire-once-f5p7s
If you onWheel over the blue elements, it goes from 0 to 2 and vice versa. I'd like to be able to make it do 0->1, 1->2, 2->1, 1->0 and so on. (kind of how netflix does it).
I feel my approach might not be right since the onWheel listener is fired multiple times and ideally I'd need it only once per actions.
If you have any idea how to accomplish this, I'd appreciate it.
Thanks!

@Magellol I'm using a combination of https://github.com/d4nyll/lethargy and a setTimeout() to do exactly this.
Here's an example:
const [scrollFired, setScrollFired] = useState<boolean>( false );
  useEffect( () => {
    const resetScrollFired = setTimeout( () => setScrollFired( false ), 300 );
    return () => {
      clearTimeout( resetScrollFired );
    }
  }, [scrollFired] );

const bindEvents = useGesture({
    onWheel: ( { event, first, delta: [, y] } ) => {
      const handleSwitch = () => {
        if ( y > 0 ) switchItem( 'next', 'scroll' );
        if ( y < 0 ) switchItem( 'prev', 'scroll' );
      }
      const scrolling = event && lethargy.check( event ) !== false;
      if ( !dragging && !first && scrolling && !scrollFired ) {
        setScrollFired( true );
        handleSwitch();
      }
    }
});

The problem I'm having is that Lethargy needs a new event after we trigger a 'switch'.
Do you know if there's a way to remove the OnWheel listener and then rebind it?

@dbismut I appreciate the help.
Unfortunately your first example doesn't work well with Trackpads with inertia.
You can't scroll quickly, you must wait until last is called, which on a trackpad with inertia can take up to 2-3 seconds.
This is the entire reason why I'm using Lethargy. I appreciate you trying to make an example with Lethargy, however you're not quite using the LethargyJS library properly.
It's just a way to tell if the wheel scroll the user makes is 'enough' to trigger a real scroll, including trackpad. So it must be used in conjunction with a timeout.
Here's an updated version of your example:
https://codesandbox.io/s/onwheel-fire-once-with-lethargy-vd7w2
It works really well on non-Windows computers.
For some reason on windows, the event is always the same scroll event, so lethargy thinks it detecting a massive scroll and so it doesn't work after the first scrolls.

@jwmann

You can't scroll quickly, you must wait until last is called, which on a trackpad with inertia can take up to 2-3 seconds.

Hm no, I'm not using last in that example, that I specifically built with inertia in mind and it works on my trackpad. It's very likely that Lethargy does a better job at this though.

It's just a way to tell if the wheel scroll the user makes is 'enough' to trigger a real scroll, including trackpad. So it must be used in conjunction with a timeout.

Lethargy is just a way to distinguish real scroll events from inertia-triggered scroll events. You might use Lethargy so that you can only scroll one frame at a time (which seems to be your intent), but there's no improper use of Lethargy in the example above as far as I'm aware. There's nothing on Lethargy readme that implies using a timeout.
Here's my last sandbox modified to use Lethargy. It doesn't involve using a timeout, it works just fine with my Macbook trackpad.
https://codesandbox.io/s/onwheel-fire-once-2coe8

@dbismut
I think we're both on the same page about Lethargy.
Although I'm using a timeout, your new example still uses a reference to achieve the same result.
I'm just using a timeout because of an animation that I want to wait until it completes.
That being said, I no longer have the original issue I described with the event. I think the only thing I changed was checking lethargy after making sure it was scrolling (aka !first && !last) instead of checking it right away and then checking for scrolling.
So, thank you for helping me fix that! 😆


Remove ignoreLooseRPF param from docs

Description
This Felix config param was removed in v3.12

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit e42d5a58b191d6b1cb88329688e5a750371790f7
https://deploy-preview-3669--calico.netlify.app


Error with CdTe BS

Hi!
This is a really useful and well put-together package! 🙌 Excited to see how it develops!
I was trying to run this with CdTe, in the same way as the GaAs example notebook, and I'm running into this issue (see attachments). Basically it seems that the MP bandstructure has a down-sampled 12x12x12 mesh (I think), so manually hard-coding the mesh to 6x6x6 works, but the default doesn't.
I've pulled my hair out for a few hours now trying to figure out what was going on here & where it was failing 😅, so I think I've found mostly where the issue is coming from but not how best to fix. Hopefully those who are more familiar with the code will be able to spot/fix the issue quicker!
CdTe_TAS_Error_MWE.ipynb.zip

Which mp_id did you use? The issue is that some of the MP calculations didn't use a uniform k-point mesh. They used a custom code to generate the symmetry adapted mesh which was broken and omitted random k-points. PyTASER requires a uniform k-point mesh (symmetry reduced is fine) to calculate the k-point weights. If you don't have a uniform mesh you can't reliably calculate the weights so unfortunately this isn't something we can fix.
You have two options:

Sometimes there are multiple uniform BS tasks on MP for the same structure, you can try using one of the others.
You can run PyTaser from your own DFT data. @youngwonwoo can help you with this.

Thanks, @kavanase. It's exciting to know you run the Pytaser with CdTe. We checked several materials, but this k-point mesh uniform issue from the MP band structure is new. Thanks for sharing.
With DOS and band structure calculation DFT data, you can easily run the Pytaser 🙂!

Thanks both for the quick replies!
I just used the mp-406 material ID for Zinc Blende CdTe from the Materials Project. It's not critical so I can just use my own data, which I'll try now, was just noting in case it was an easy-ish fix for ppl using the Materials Project based PyTASer workflow!
I wonder in cases like this if it would be relatively easy to determine the subset of kpoints which form a uniform mesh. E.g. here it seems the reduced 12x12x12 mesh contains a uniform 6x6x6 mesh, which if you make PyTASer use this it seems to run ok (and I'd think the weights should be fine – might just need to be renormalised?), so could it be used?

I checked again that this issue is still present for CdTe.
I had a look around and it seems there are no other task_ids for zinc blende CdTe bandstructures.
For now, I've added a warning to the Materials Project tutorial about this (dbe30a0). As mentioned in that last message ☝ , I think downsampling the kpoint mesh would work as a solution here. I think something like this (in expand_kpoints) could work:
addresses = np.rint((kpoints + shift / (mesh * 2)) * mesh)
for factor in [1,2,3,4,6,8]:
    try:
        mesh = np.rint(mesh)/factor
        ...
        if n_mapped != n_expected:
            raise ValueError(f"Expected {n_expected} points but found {n_mapped}")
        break
    except ValueError as exc:
        if factor == 8:
            raise exc

to loop over possible uniform subsets of the broken full mesh (e.g. for CdTe would identify the 6x6x6 uniform mesh from the non-uniform 12x12x12 mesh). The kpoint weights would then just need to be renormalised based on the (relative) weights of this reduced uniform mesh, and the self.bs object might need to be adjusted somehow so its kpoint indices match that of the output kweights (with this reduced mesh), so e.g. the jdos() function works correctly.
I don't have the space for this, but just noting that / how I think it can be done.


Remove usage of Accumulator from window functions

Is your feature request related to a problem or challenge?
Currently the window expressions use Accumulator to generate the output values.
This should be relatively inefficient as each individual value will generate a ScalarValue, leading to many allocations, high memory usage and limited vectorization.
Describe the solution you'd like
Write more efficient code moving away from Accumulator and producing the values more directly.
Describe alternatives you've considered
No response
Additional context
If we don't use Accumulator in window functions anymore, we can remove count from SumAccumulator, making conventional sums slightly more efficient.

cc @metesynnada / @mustafasrepo


add a configuration option listen address

Add a configuration option for viewer listen address:
The
CodeChecker server
sub option should be:
-l listen address
the default should be localhost.
Then the not so practical
--not-host-only
option can be removed.

The --not-host-only should be documented as it is very useful when wanting to integrate CodeChecker to a companies CI toolchain for example.
Though I agree that the "-l listen address" is a better interface.

It will be part of the upcoming command line argument cleanup #415

What would providing an address other than localhost mean?

The new argument is implemented in #655. Removing the old argument will be in v6.0 because that is a backward incompatible change.


Wildcard for 404 page

Hello. i dont understand how its work or its bug?
I have 'proxy host' rules with forward subdomain to ip
a.mydomain.com -> <IP_ADDRESS>
b.mydomain.com -> <IP_ADDRESS>
c.mydomain.com -> <IP_ADDRESS>
I want to create a 404 page for all those subdomains that are not explicitly listed above.
On page '404 Hosts' i create wildcard for all non exists domains :

Try enter:
non.mydomain.com
and receive Nginx Proxy Manager home page.

+1
Current behaviour is not secure

up

I would create a cusotm 404 page and redirect to this page

Actually, I found a solution. In Settings change Default Site setting from Congratulations Page to 404 Page. For me it solved an issue.


gstreamer: backport device discovery fix

Motivation for this change
This is a manual backport of recent changes1 in gstdevicemonitor.c
that fix the device discovery failing entirely if one provider fails
(eg. if pulseaudio support is enabled but no daemon is running).
The commit couldn't have been simply cherry-picked because it doesn't
directly apply to gstreamer 1.18.4.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

(currently building a bunch of Qt stuff for testing)

I succesfully built and tested QtWebEngine and VoIP in Nheko.

ping

What about applying the previous patch first?
    # https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/679
    (fetchpatch {
      url = "https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/41677a526b83bb2493087af1d93b50c297cf97cd.patch";
      sha256 = "e5SCjRREIQ2Y1/SK8ywW/Q+ejxuWkJ7eMR4M0/wQCFs=";
    })
    # https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/1189
    (fetchpatch {
      url = "https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/1912bcbcc42e8ee2c4948511619219f5722631d2.patch";
      stripLen = 3;
      extraPrefix = "";
      sha256 = "a1EcW0phtXjjoC4PaHGrNB9+SVHSTq8bdQbpyspp/zM=";
    })

Thanks, it seems to be producing an identical gstdevicemonitor.c.
I'm rebuilding and testing again just to be sure.

Done, I tested again that nheko can discover mic and audio outputs.

Sounds good to me, then. Though we will probably want to target staging.

Actually GStreamer 1.20 has just been released: https://gstreamer.freedesktop.org/releases/1.20/

Ok, I suppose I could change this to target 21.11 instead.

Yes.  I see 1.20 in staging-next already.


Empty logs

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

open lazydocker
Click on container
Log is empty

Screenshots
Screen

Desktop (please complete the following information):

OS: Ubuntu 24.04 LTS
Lazydocker Version 0.23.3

Additional context
Docker version 27.1.1, build 6312585
Containers are started using the command "docker compose -f 'path' up -d"

Also experiencing this issue. Using the run command line as an alias under debian:
alias lzd='docker run --rm -it --name lazydocker -v /var/run/docker.sock:/var/run/docker.sock -v ~/docker-apps/lazydocker:/.config/jesseduffield/lazydocker lazyteam/lazydocker'

Common thread here seems to be using docker-compose -f.
Lazydocker was working fine for me when I previously ran docker-compose up -d in my directory with a single docker-compose.yml file. Logs stopped showing up in lazydocker as I started using additional separate docker-compose files all started with -f {path} arguments.
e.g., docker-compose $(for file in /path/*.yml; do echo -n "-f $file "; done) up -d

Same here, containers started with docker compose -f have empty logs. Logs are visible with docker logs $id --follow. Debian 12, lazydocker installed with curl. Version 12.3. It was working in the previous version I had but I lost the specific version number.

Tested with 12.1, same issue.

See https://github.com/jesseduffield/lazydocker/issues/391#issuecomment-1324799180

See #391 (comment)

I don't think this is the same issue. I just started the service with docker compose up -d and saw no logs.

I don't see logs with bash alias approach, but it works for manually installed binary


[Enhancement] add all steps to Figma

Motivation / Problem
Currently, only the first step is added in Figma. But the next step(s) should be added as well as they might differ in their layout, texts need to be added and it is not clear how the faucet will be displayed yet.

Solution

Design all steps in Figma.
Also add final texts to all steps (https://github.com/deltaDAO/mvg-portal/issues/110)

The idea for the faucet would be to only have one button to ask for the tokens, so the design of all the steps is indeed quite similar, the only difference would be that some steps have 2 sub-cards instead of 1 (add tokens to MetaMask and request tokens from the faucet)


[AxisBasedChart] Label drawing and NullOrEmpty label

Changes :

Fix Null/Empty label drawing => Crash if Label is Null
Fix Series generation without label => Bad series/simple item generation when label is not fully filled and unique
Add sample for BarChart without Label => For issue testing

Fix issue :

#137

@eman1986 any chance that will be merge soon ?
I'm working an align Value label positioning (TopOfChart, TopOfElement -bar, point, ...-, OverElement) and the merge part on main block me to made a good PR.

Sorry about that, I thought I merged this already. Looks good.


Loading unprocessed corpus documents with CTM and Optimizer

OCTIS version: 1.10.0
Python version: 3.7.6
Operating System: Ubuntu 20.04 LTS

Description
I've asked this at #29, but decided to open a new issue because this is a more specific scenario. So, here it is:

Hi @silviatti. So, if I understand correctly, currently there's no way to load the unprocessed corpus documents on OCTIS' CTM while using its optimizer, in a manner similar to the one done on standalone CTM's README?

Originally posted by @lffloyd in https://github.com/MIND-Lab/OCTIS/issues/29#issuecomment-974875277
What I Did
I gave a look at the docs.

Thanks for open the specific issue, because I had lost the question. Yes, I confirm that there's currently no way to load the unpreprocessed corpus.
As mentioned before, this would require to rethink how we pre-process the corpus and the format of the pre-processed corpus. This is currently a .tsv file with no header. The first two columns are mandatory, and they contain the pre-processed text and the partition of the dataset to which the document belong. Then we may have an additional column representing the label associated with the doc.
A possibility could be to add an additional column representing the unpreprocessed text. This could be mandatory (although it's not necessary if one doesn't use CTM) or this could be optional. In case it's optional, this can create some confusion (how can we recognize that a specific column represents the unpreprocessed text, the labels, etc?), unless we provide a header to the .tsv file.
Happy to discuss if you want. Unfortunately my time to dedicate to this project has been reduced lately. So I am be slow to respond. However I think OCTIS can be useful for the community and I'm trying to keep it alive :)

Thanks Roberta! :)
yes, that is correct.
My suggestion is to first try hyperparameter configurations that "usually" work well. You can find some reference values in these papers:

https://aclanthology.org/2021.acl-short.96/
https://aclanthology.org/2021.ranlp-1.157/
https://arxiv.org/pdf/2202.07631.pdf

Moreover, make sure you select an appropriate pre-trained model for generating the contextualized representations of the documents. In this paper we noticed that this has an impact on the results. And also the pre-processing is quite important. It seems CTM works better with smaller vocabularies.
Hope it helps :)
Silvia

thanks for the super quick reply and the pointers! :)


[FAB-17953] Add integration tests for snapshot feature (leveldb, no pvtdata)

Signed-off-by: Wenjian Qiao<EMAIL_ADDRESS>Type of change

New feature

Description
Add basic end to end tests for the snapshot feature:

generate snapshots and compare snapshots generated on different peers
bootstrap peer from a snapshot for peers in an existing org and new org
generate snapshot again on a peer bootstrapped from a snapshot
verify bootstrapped peer: chaincode invocation and upgrade, channel config update,
join new channel, qscc, history query, new chaincode deployment

It covers leveldb without private data. Tests for couchdb and private data will be covered in separate PRs.
Additional details
Related issues
https://jira.hyperledger.org/browse/FAB-17953

/ci-run

This test is failing on master in CI and locally. Opened FAB-18288.

Fix merged! No further action needed for the above.


dev-cmd/bottle: save local_filename to json

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

As discussed in https://github.com/Homebrew/homebrew-test-bot/issues/172#issuecomment-414932561 and https://github.com/Homebrew/brew/pull/4612, the local bottle filenames differ from the filename on bintray. So this adds the local filename as an extra field called local_filename to the json file generated by brew bottle --json.

Thanks @scpeters!