Add "validation" subworkflow

Description of feature
Add validation subworkflow which runs RTGtools and/or hap.py to generate a validation report and can be enabled with a flag or something

nah, that's exactly what I had in mind.
Also add an option for a bed file to limit the regions to investigate

Might also be worth adding to nf-core, since there's work being done for a "validation" workflow

Perfect! And yes was planning on directly adding it to nf-core :)

Added in #63


Running Jtop causes the system to brick next time it is rebooted

Currently running jtop at any point makes it so that the system ends up crashing when the machine is rebooted
Here are some screenshots that might be useful for you guys
My plan right now is that I'm just going to reinstall everything from scratch and make sure that I don't run jtop, but I would like to use jtop in the future since it is a really nice utility

Overall, I ❤ the work you guys have put into this!

Dear @v2thegreat,
I've tried to reproduce your issue. Downloaded the image and flashed it on a new SD. No problem with JTop.
Did a sudo apt-get update and sudo apt-get upgrade. Still no problem. I can use JTop as any other program and reboot without any hitch.
My intuition tells me that your operating system is somewhere, corrupted in some way. I would recommend backing up all your work to USB and getting a new and fresh OS.

The thing is, I've tried this 3-4 times. I had installed some additional packages and stuff when I got things working. I'm currently using a jetson nano 4GB. This time I'll do a more detailed overview of what I end up doing. Oh, I should mention: I disable the desktop since that enables me to free up more memory. Did you try that out as well?
I can't think of anything at this time that I might be doing, so I'll get back to you on it if things happen again, this time with detailed instructions for what is going wrong if I can

I will wait. I can imagine that turning off the desktop image doesn't make JTop happy. By the way, I'll help you as best I can, but the whole problem is more of a JTop issue than an SD image problem. I think, if you had an original JetPack image, without the extra software we put on it, you'd still be in trouble.


Add details on Debian and Alpine sources to README.md

Is the OSS Fuzz removal intentional? Wasn't mentioned in the description.

Is the OSS Fuzz removal intentional? Wasn't mentioned in the description.

OSS-Fuzz wasn't removed, and still exists in the list above.

OSS-Fuzz wasn't removed, and still exists in the list above.

Weird. I swear the diff rendered differently on my phone while I was out at lunch...


the screen resolution does not change and the rendering quality does not change either. I can choose any of the proposed screen resolutions, but nothing changes

Describe the bug
the screen resolution does not change and the rendering quality does not change either. I can choose any of the proposed screen resolutions, but nothing changes
Screenshots
If applicable, add screenshots to help explain your problem.
System Information (please complete the following information):

macOS: [e.g. 13.1 monterey]
Device: [e.g. MacbookPro 14 2021 ]
CPU: [e.g. Apple M1 pro]
Dedicated GPU (if any): [e.g.  m1 pro]
RAM: [e.g. 16G ]

Additional context
Add any other context about the problem here.
Logs (if any)

If it's related to the launcher, upload neutralinojs.log in Yaagl Data Directory

If it's related to the game, upload `logs/game_{timestamp}.log in Yaagl Data Directory

Do you still have this issue?


Use source version of libs/orchestrator instead of external module that has been archived

updates pkg/github/models/models.go to use the local version of lib/orchestrator
If became evident that though the repo https://github.com/diggerhq/lib-orchestrator had been archived because the library had been merged into diggerhq/digggr the code was still referencing the external module. I have updated to use the internal and most up to date version of libs/orchestrator vs github.com/digghq/lib-orchestrator
also removes github.com/diggerhq/digger/lib-orchestrator from go.mod and go.sum

Thanks! It seems I missed that in my recent PR which merges the libs


release notes creation task failed with errors.

Hi,
tried first time the release notes task and it failed with below errors: is there something i am miising ? or i a m doing wrong ? I am running on windows 2005server.
2016-06-20T06:10:26.4964533Z ##[debug]Loading template file [D:\BuildAgent_work\1\s\Main\Build\release-template.md]
2016-06-20T06:10:26.5454582Z ##[debug]Processing template
2016-06-20T06:10:27.1405177Z ##[error]Cannot convert null to type "System.DateTime".
2016-06-20T06:10:27.1745211Z ##[error]Cannot convert null to type "System.DateTime".
2016-06-20T06:10:27.2835320Z ##[debug]Writing output file [ D:\BuildAgent_work\1\a\releaseNotes.md].
2016-06-20T06:10:27.3115348Z ##[error]Cannot find drive. A drive with the name ' D' does not exist.

My first guess on the Drive D missing error would be the obvious, the build box does not have a drive D:, but I assume it can't be that obvious.
As you use the path 'D:\BuildAgent_work' I am assuming it is your own build agent, not an MS hosted one. So you choose to pick D:
Now you could have set your agent's work folder to 'BuildAgent_work', but this does look like a potential typo, as I would usually expect the path to be 'BuildAgent_work' as this is the default form.
So is there a chance it is a typo in your path, a missing \
Can you remote onto the build agent and check the folder structure?

Thanks for the quick response.  this is my configuration.

in the enviroenment variable :  BUILD_ARTIFACTSTAGINGDIRECTORY: is set to   D:\BuildAgent_work\1\a
error is : 2016-06-20T11:17:01.8675756Z ##[debug]Writing output file [ D:\BuildAgent_work\1\a\releaseNotes.md].
2016-06-20T11:17:01.8785767Z ##[error]Cannot find drive. A drive with the name ' D' does not exist.

So, just too check, is this...

a VSTS hosted build agent
your own self hosted VSTS agent
an on prem TFS 2015.x setup

As it picks up the path from the environment variable I must assume it is correct, if not none of the build would work.
I would suggest trying the output  file as $(System.DefaultWorkingDirectory)\releasenotes.md, then using the copy task to move the results to drops. Maybe the artifacts folder does not exist at the time the task is running, but I have never seen this before.
If you can I would remote onto the agent VM and have a look around

I am new to tfs build. we have TFS setup on  windows 2008 server. the same is using for builds. I configured the build agent on server.  is it called on Prem setup ? i am not sure.
publish & copy build artifacts task exist before the release task.  anyway, i tried output file as $(System.DefaultWorkingDirectory)\releasenotes.md
2016-06-20T18:20:29.3282800Z ##[debug]Loading template file [D:\BuildAgent_work\1\s]
2016-06-20T18:20:29.3442736Z ##[error]Access to the path 'D:\BuildAgent_work\1\s' is denied.
2016-06-20T18:20:29.3692636Z ##[error]Cannot load template file [D:\BuildAgent_work\1\s] or it is empty
2016-06-20T18:20:29.3712628Z ##[debug]Writing output file [D:\BuildAgent_work\1\s\releasenotes.md].
one more i tried output file as D:\temp\releasenotes.md
2016-06-20T16:52:09.8911468Z ##[debug]Loading template file [D:\BuildAgent_work\1\s]
2016-06-20T16:52:09.9041481Z ##[error]Access to the path 'D:\BuildAgent_work\1\s' is denied.
2016-06-20T16:52:09.9291506Z ##[error]Cannot load template file [D:\BuildAgent_work\1\s] or it is empty
2016-06-20T16:52:09.9301507Z ##[debug]Writing output file [D:\temp\releaseNotes.md].

No problem, we are all new to products at some point, what you have what is call an 'on premises' installation, so you own the TFS server and build agent i.e. you set it up, as this the only option for 'on prem'
I assume your build works OK for all the other tasks?
The error looks like one of few things

The path is wrong - but that seem unlikely as it is autogenerated
The account the build agent is running as has not rights to the drive/folder - again seems strange if the rest of the build is OK - BUT THE ERRORS REALLY LOOK LIKE RIGHTS SO IT IS MY BEST GUESS

So

You have place the template file in the declared location in source control?
Do you get the same results if you place it inline (see the WIKI on this site for details)
Is the build agent running as a service or interactive on the desk top?

I would suggest logging onto the agent VM as the account the build process is running and see what you can see.

yes, its in source control. 2. i will try that next 3. build agent is running as service. i am with my credential in agent VM already.

The error really looks like some rights issue. 2 days back, we updated the TFS 2015 RC2.1 version.
Atleast the build agent setup is changed in updated version, its not powershell script for configuring. its windows cmd script and extra there is Runagent.cmd script , that should run always to enable the build agent.  If don't run as admin, i got error in first step, access denied for getting the sources.  and build stopped.
2016-06-20T19:58:47.7097376Z ##[error]Access to the path 'D:\BuildAgent_work\SourceRootMapping\c0634b7d-4844-4c34-b28c-0969262ce351\9\SourceFolder.json' is denied.
I tried running again the Runagent.cmd script with admin rights. other build steps went fine, except your release task.
2016-06-20T20:04:43.3275348Z ##[debug]Loading template file [D:\BuildAgent_work\1\s]
2016-06-20T20:04:43.3395360Z ##[error]Access to the path 'D:\BuildAgent_work\1\s' is denied.
2016-06-20T20:04:43.3645385Z ##[error]Cannot load template file [D:\BuildAgent_work\1\s] or it is empty
2016-06-20T20:04:43.3665387Z ##[debug]Writing output file [$(BUILD_ARTIFACTSTAGINGDIRECTORY)\releasenotes.md].
2016-06-20T20:04:43.3765397Z ##[error]Could not find a part of the path 'D:\BuildAgent\tasks\GenerateReleaseNotes\1.3.22$(BUILD_ARTIFACTSTAGINGDIRECTORY)\releasenotes.md'.

I have seen issues where a folder is created with 'run as admin' and then when you try to access it as a 'non run as admin' you get similar errors. This might be the case between running the build agent via the desktop script or the as a service
One option is to delete the folder in question and start again.
However, that last line of error you show above seems to show that the variable expansion has failed.  You should never see $(BUILD_ARTIFACTSTAGINGDIRECTORY) in the logged path, this could be changed to c:\xxxx or similar
So did the task work prior to upgrading to 2015.2.1?

i added  this task only   after 2015.2.1 update.  Tried deleting all the folders in build agent , started again, still have the same access issue for release notes only.
tried for inline template : $(BUILD_SOURCESDIRECTORY)\Main\Build\release-template.md
is it the right way ?   got the below error.
2016-06-21T05:32:54.9892182Z ##[debug]Processing template
2016-06-21T05:32:55.0252254Z ##[error]Method invocation failed because [System.Char] does not contain a method named 'Trim'.
2016-06-21T05:32:55.0272258Z ##[error]Method invocation failed because [System.Char] does not contain a method named 'Trim'.
2016-06-21T05:32:55.0292262Z ##[error]Method invocation failed because [System.Char] does not contain a method named 'Trim'.

If you are using the inline method you expect to see a log
2016-05-20T06:40:50.0425987Z Executing the powershell script: C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\1.99.0\tasks\GenerateReleaseNotes\1.3.22\GenerateReleaseNotes.ps1 2016-05-20T06:40:50.3515793Z ##[debug]collectionUrl = [https://richardfennell.visualstudio.com/] 2016-05-20T06:40:50.3525786Z ##[debug]teamproject = [GitHub] 2016-05-20T06:40:50.3535786Z ##[debug]releaseid = [] 2016-05-20T06:40:50.3535786Z ##[debug]buildid = [459] 2016-05-20T06:40:50.3545792Z ##[debug]defname = [Validate-ReleaseNotesTask.Master] 2016-05-20T06:40:50.3555787Z ##[debug]buildnumber = [20160520.1] 2016-05-20T06:40:50.3555787Z ##[debug]In Build mode 2016-05-20T06:40:50.3565784Z ##[debug]Getting build details for BuildID [459] 2016-05-20T06:40:50.6075607Z ##[debug]Getting associated work items for build [459] 2016-05-20T06:40:50.6085609Z ##[debug]Getting associated changesets/commits for build [459] 2016-05-20T06:40:50.6965552Z ##[debug]Using template mode [InLine] 2016-05-20T06:40:50.6975546Z ##[debug]Using in-line template 2016-05-20T06:40:50.7055540Z ##[debug]Processing template 2016-05-20T06:40:50.7285529Z ##[debug]   Starting block WI 2016-05-20T06:40:50.7345521Z ##[debug]      0 items 2016-05-20T06:40:50.8405449Z ##[debug]   Ending block WI 2016-05-20T06:40:50.8435441Z ##[debug]   Starting block CS 2016-05-20T06:40:50.8455430Z ##[debug]      0 items 2016-05-20T06:40:50.8465441Z ##[debug]   Ending block CS 2016-05-20T06:40:50.8475442Z ##[debug]Writing output file [C:\a\1\a\releasenotesinline.md].
If running in inline mode

Output file $(Build.ArtifactStagingDirectory)\releasenotesinline.md
Mode - Inline
Template is as below

`
#Release notes for build $defname
Using line line template
Build Number  : $($build.buildnumber)
Build started : $("{0:dd/MM/yy HH:mm:ss}" -f [datetime]$build.startTime)
Source Branch : $($build.sourceBranch)
###Associated work items
@@WILOOP@@

$($widetail.fields.'System.WorkItemType') $($widetail.id) [Assigned by: $($widetail.fields.'System.AssignedTo')]     $($widetail.fields.'System.Title')
@@WILOOP@@
###Associated change sets/commits
@@CSLOOP@@
ID $($csdetail.changesetid)$($csdetail.commitid) $($csdetail.comment)
@@CSLOOP@@
`

The errors you have now seem to be that the template is missing or you have no text to process.
I will update the wiki to try to explain using the inline method more clearly

Thanks for the instructions. YES, inline - mode is working for me. Its good to see working finally. is it so that output file won't have any formatting when generated with inline ? is it possible to specify the output file in some other format than .md ?

Sorry I only support markdown (MD) as a format, feel tree to fork the code and add a different one of you wish :)
There is no difference in what you get between inline or file based operations assuming the template is the same. It is just down to whether you wish to source control your template or just have it as a build parameter.
So I suspect the problem all along has been the source template (file) not ending up in the location you expect.
Glad you have something working now

Hi @rfennell ,
I have kind of the same problem as @pagadalacs had. It seems to me that the template file is by default taken from the artifacts directory (in my case  ##[error]System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\BATest_work\2\a\releasenotes.md) . I have included the template in my Git repo to be used and can select it fine. (see below). However I think the tool assumes that this file will end up in de artifact dir (as it would maybe eventually) but this is only the case after the build finishes (e.g. when the release is made. Is this maybe the assumption? We , for now, work with the inline mode which does work.
Maybe its an idea to rework the source directory for the template?
Regards, martin


Issue regarding blocks being colored/in place but not

I don't see any blocks or any ghost blocks with textures on them, can someone help me?

I'll need at least the mod list, Minecraft/Forge/Schematica version to start giving advice.

Basically all I have is the 1.8.8 versions for Minecraft, Forge and Schematica.

I need exact versions, not just the Minecraft version.

Okay, 1.8 for Forge, 1.8.8 for Schematica, and for Forge, 1.8.8

I'm having the exact same issue with 1.11 minecraft forge using only LunatriusCore and Schematica.

I still don't have a mod list with their versions...
Just upload the logs/fml-client-latest.log file and paste the link here. Otherwise I can't do anything about it.
The only advice that I can give you is to remove optifine if you have it installed and try turning VBOs on/off.

fml-client-latest.txt

Optifine was deleted and VBO's have been resetted but that didn't work

Nothing out of the ordinary in the log file. Have you tried toggling the VBO setting on/off?

Yes I have.

Could you test if this issue is still present in the 1.12 version?

I'll try once I get home. In France enjoying my holidays atm hehe
Op 1 aug. 2017 23:41 schreef "Jadran Kotnik"<EMAIL_ADDRESS>
Could you test if this issue is still present in the 1.12 version?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Lunatrius/Schematica/issues/189#issuecomment-319505300,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXfi5YeEz3uaGAjGuWRV08Tnsr4bFvyjks5sT5trgaJpZM4LLtcW
.


MM-15528: Updates to channel info for group-constrained channels.

Summary
For group-constrained channels:

Adds a line of text to the channel info view.
Hides the "Add Member" link.
Never shows "Manage Members", always "View Members".

Ticket Link
https://mattermost.atlassian.net/browse/MM-15528
and
https://mattermost.atlassian.net/browse/MM-15529
Checklist

[ ] Added or updated unit tests (required for all new features)
[ ] All new/modified APIs include changes to mattermost-redux (please link)
[x] Has UI changes
[x] Includes text changes and localization file updates

Device Information
iPhone X, iOS 12.2 emulator.
Screenshots

@hmhealey In the webapp you can manage the members by changing their role between [team|channel]_user and [team|channel]_admin. Furthermore, depending on QA capacity, with the release of this feature users may be able to be individually added to teams and channels if they're in the subset of system users who are members of associated groups. However that adding of users may be pushed to the next iteration.
Put simply, canManageChannelMembers will need to be a separate boolean from isGroupConstrained.

Cool, I was just missing something then. That makes sense


401 on report page for admins

Describe the bug
Getting a 401 error from the /api/history/report/xxxxx endpoint when trying to load a report detail page when mocking a receiver as an admin.
Impact
Only affecting PrimeAdmins.
To Reproduce
Steps to reproduce the behavior:

Log in with an admin account
Switch to a receiver org & select receiver from the mock dropdown (al-phd for example)
Click the "Daily Data" in the nav menu, click through to an individual report
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

^ Note the mismatch between organization header and what org is selected in the admin org switcher.

Blocked by: https://www.slack.com/archives/C026DV8R21W/p1658438513173289

Blocked by PR #6032 -- Awaiting merge so we can migrate this page over to the new deliveries API and remove this bug.


improve: add github themes

Closes #75
Themes from https://github.com/projekt0n/github-nvim-theme

:tada: This PR is included in version 4.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Resistance Calculator using Ohm's Law

Calculator Functions
Description
Ohm’s law states that the voltage across a conductor is directly proportional to the current flowing through it, provided all physical conditions and temperature remain constant.
Mathematically, this current-voltage relationship is written as, V=IR. With this the calculator will determine resistance within a given circuit.
Contribution Event
GSSOC22
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

If this issue isn't closed yet, can I work on this??

If this issue isn't closed yet, can I work on this??

I will make don't worry, make your own


Open Glorious Champion Capsules

So far only regular champion capsules are supported – the lootId for Glorious Champion Capsules needs to be added to support them.

lootId is CHEST_129


question: Does import database operation delete existed records?

OrientDB Version: 2.2.25
Expected behavior
Import database doesn't delete existed records.
Actual behavior
just found imported 30000 records were deleted!
Steps to reproduce
Because inserting record is really time consuming, I use some other server do the inserting paralleled, and import one of them to the main server. Found the existed 30000 record deleted!
script:
import database xxxx10-15.export.gz -preserveClusterIDs=true
Questions:
How can i restore the deleted records? And how to import without deleting existed records?

hi @HuangKBAaron,
Yes by default an "database import" delete all the existing data and reimport the new one, if you want to move just some data you should do and "export database -excludeAll -includeClass=ClassName file.tar.gz"  and after "import database -merge file.tar.gz" for more details have a look to : http://orientdb.com/docs/last/Console-Command-Export.html and http://orientdb.com/docs/last/Console-Command-Import.html

@tglman many thx! I will try and report status later.

@tglman，about the script you suggested:
export database -excludeAll -includeClass=ClassName file.tar.gz
There are lots of class name out there, is it better to use includeSchema than listing all the classname?

@tglman @luigidellaquila
The script given did work PARTIALLY. In my demo db, there are 720 records of v_volume.
Here is the steps:

Export by:
export database C:\projects\personal\Volkswagen-volume-predict\data\vw-schema-record-index.gz -excludeAll "v_city_cluster v_fuel_type v_pr_vol_output e_has_type v_ev_type v_segment v_pr_vol_input v_body_type e_content_item v_product_type" -includeRecords=true

Added one record of v_volume to the db will be restored to.

Import by:
import database C:\projects\personal\Volkswagen-volume-predict\data\vw-schema-record-index.gz -merge=true

observed result:
Importing database database C:\projects\personal\Volkswagen-volume-predict\data\vw-schema-record-index.gz -merge=true...
Started import of database 'plocal:C:/projects/orientdb-c/databases/Volkswagen-volume-predict' from C:\Users\HUANGK~1\AppData\Local\Temp\Volkswagen-volume-predictimport5202552626653811236vw-schema-record-index.gz...

Importing records...

Started migration of links (-migrateLinks=true). Links are going to be updated according to new RIDs:
- Cluster v_content_3... Completed migration of 6 records in current cluster
- Cluster v_content_2... Completed migration of 6 records in current cluster
- Cluster v_content_1... Completed migration of 8 records in current cluster
- Cluster v_brand_indicator_3... Completed migration of 2 records in current cluster
- Cluster v_brand_indicator_2... Completed migration of 2 records in current cluster
- Cluster v_brand_indicator_1... Completed migration of 2 records in current cluster
- Cluster v_product_type_1... Completed migration of 2 records in current cluster
- Cluster v_product_type_3... Completed migration of 0 records in current cluster
- Cluster v_product_type_2... Completed migration of 0 records in current cluster
- Cluster oschedule... Completed migration of 0 records in current cluster
- Cluster e_in_pr_3... Completed migration of 360 records in current cluster
- Cluster e_in_pr_1... Completed migration of 360 records in current cluster
- Cluster e_in_pr_2... Completed migration of 360 records in current cluster
- Cluster e_content_item... Completed migration of 22 records in current cluster
- Cluster osequence... Completed migration of 0 records in current cluster
- Cluster orole... Completed migration of 6 records in current cluster
- Cluster v_segment_2... Completed migration of 4 records in current cluster
- Cluster v_segment_1... Completed migration of 4 records in current cluster
- Cluster v_city_level_1... Completed migration of 2 records in current cluster
- Cluster v_volume_1... Completed migration of 360 records in current cluster
- Cluster v_volume_2... Completed migration of 360 records in current cluster
- Cluster v_segment_3... Completed migration of 2 records in current cluster
- Cluster v_volume_3... Completed migration of 360 records in current cluster
- Cluster v_city_level_2... Completed migration of 2 records in current cluster
- Cluster v_city_level_3... Completed migration of 2 records in current cluster
- Cluster v_city_level... Completed migration of 4 records in current cluster
- Cluster v_model... Completed migration of 0 records in current cluster
- Cluster _studio_2... Completed migration of 10 records in current cluster
- Cluster _studio_3... Completed migration of 10 records in current cluster
- Cluster default... Completed migration of 0 records in current cluster
- Cluster v_calculation_type_3... Completed migration of 0 records in current cluster
- Cluster v_calculation_type_2... Completed migration of 2 records in current cluster
- Cluster v_calculation_type_1... Completed migration of 2 records in current cluster
- Cluster _studio_1... Completed migration of 10 records in current cluster
- Cluster v_content... Completed migration of 8 records in current cluster
- Cluster e... Completed migration of 0 records in current cluster
- Cluster v_body_type... Completed migration of 4 records in current cluster
- Cluster v... Completed migration of 0 records in current cluster
- Cluster v_ssss_type... Completed migration of 4 records in current cluster
- Cluster v_body_type_3... Completed migration of 2 records in current cluster
- Cluster v_body_type_2... Completed migration of 4 records in current cluster
- Cluster v_calculation_type... Completed migration of 2 records in current cluster
- Cluster v_body_type_1... Completed migration of 4 records in current cluster
- Cluster v_ev_type... Completed migration of 2 records in current cluster
- Cluster v_pr_vol_output... Completed migration of 0 records in current cluster
- Cluster v_ev_type_1... Completed migration of 2 records in current cluster
- Cluster v_ev_type_3... Completed migration of 0 records in current cluster
- Cluster v_ev_type_2... Completed migration of 0 records in current cluster
- Cluster v_pr_vol_input_3... Completed migration of 0 records in current cluster
- Cluster v_pr_vol_input_2... Completed migration of 0 records in current cluster
- Cluster v_pr_vol_input_1... Completed migration of 0 records in current cluster
- Cluster v_pr_vol_input... Completed migration of 0 records in current cluster
- Cluster e_has_type... Completed migration of 2,194 records in current cluster
- Cluster v_2... Completed migration of 0 records in current cluster
- Cluster v_1... Completed migration of 0 records in current cluster
- Cluster v_3... Completed migration of 0 records in current cluster
- Cluster v_ssss_type_1... Completed migration of 4 records in current cluster
- Cluster _studio... Completed migration of 12 records in current cluster
- Cluster v_ssss_type_2... Completed migration of 4 records in current cluster
- Cluster v_ssss_type_3... Completed migration of 2 records in current cluster
- Cluster v_plan_round_3... Completed migration of 0 records in current cluster
- Cluster e_content_item_1... Completed migration of 20 records in current cluster
- Cluster v_plan_round_2... Completed migration of 0 records in current cluster
- Cluster e_content_item_2... Completed migration of 20 records in current cluster
- Cluster e_content_item_3... Completed migration of 20 records in current cluster
- Cluster ofunction... Completed migration of 0 records in current cluster
- Cluster v_plan_round_1... Completed migration of 2 records in current cluster
- Cluster v_city_cluster_2... Completed migration of 2 records in current cluster
- Cluster v_city_cluster_3... Completed migration of 0 records in current cluster
- Cluster v_city_cluster_1... Completed migration of 2 records in current cluster
- Cluster v_city_cluster... Completed migration of 2 records in current cluster
- Cluster e_has_type_3... Completed migration of 2,192 records in current cluster
- Cluster e_has_type_2... Completed migration of 2,192 records in current cluster
- Cluster e_has_type_1... Completed migration of 2,194 records in current cluster
- Cluster v_segment... Completed migration of 4 records in current cluster
- Cluster e_1... Completed migration of 0 records in current cluster
- Cluster e_3... Completed migration of 0 records in current cluster
- Cluster e_2... Completed migration of 0 records in current cluster
- Cluster v_pr_vol_output_1... Completed migration of 0 records in current cluster
- Cluster v_pr_vol_output_2... Completed migration of 0 records in current cluster
- Cluster v_brand_indicator... Completed migration of 2 records in current cluster
- Cluster v_pr_vol_output_3... Completed migration of 0 records in current cluster
- Cluster v_product_type... Completed migration of 2 records in current cluster
- Cluster v_volume... Completed migration of 361 records in current cluster
- Cluster v_model_3... Completed migration of 0 records in current cluster
- Cluster ouser... Completed migration of 6 records in current cluster
- Cluster v_model_1... Completed migration of 0 records in current cluster
- Cluster e_in_pr... Completed migration of 360 records in current cluster
- Cluster v_model_2... Completed migration of 0 records in current cluster
- Cluster v_fuel_type... Completed migration of 2 records in current cluster
- Cluster v_fuel_type_3... Completed migration of 0 records in current cluster
- Cluster v_fuel_type_2... Completed migration of 0 records in current cluster
- Cluster v_fuel_type_1... Completed migration of 2 records in current cluster
- Cluster v_plan_round... Completed migration of 2 records in current cluster
Total links updated: 11,905

Done. Imported 5,954 records in 2.43 secs

Rebuild of stale indexes...
Start rebuild index ouser.nameError on database import happened just before line 0, column 948304
com.orientechnologies.orient.core.storage.ORecordDuplicatedException: Cannot index record #5:3: found duplicated key 'admin' in index 'OUser.name' previously assigned to the record #5:0
        DB name="Volkswagen-volume-predict" INDEX=OUser.name RID=#5:0
        at com.orientechnologies.orient.core.index.OIndexUnique$1.validate(OIndexUnique.java:47)
        at com.orientechnologies.orient.core.index.OIndexUnique$1.validate(OIndexUnique.java:37)
        at com.orientechnologies.orient.core.index.sbtree.local.OSBTree.put(OSBTree.java:873)
        at com.orientechnologies.orient.core.index.sbtree.local.OSBTree.validatedPut(OSBTree.java:267)
        at com.orientechnologies.orient.core.index.engine.OSBTreeIndexEngine.validatedPut(OSBTreeIndexEngine.java:169)
        at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.doValidatedPutIndexValue(OAbstractPaginatedStorage.java:1953)
        at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.validatedPutIndexValue(OAbstractPaginatedStorage.java:1939)
        at com.orientechnologies.orient.core.index.OIndexUnique.put(OIndexUnique.java:82)
        at com.orientechnologies.orient.core.index.OIndexUnique.put(OIndexUnique.java:35)
        at com.orientechnologies.orient.core.index.OIndexAbstract.populateIndex(OIndexAbstract.java:944)
        at com.orientechnologies.orient.core.index.OIndexAbstract.indexCluster(OIndexAbstract.java:1044)
        at com.orientechnologies.orient.core.index.OIndexAbstract.fillIndex(OIndexAbstract.java:543)
        at com.orientechnologies.orient.core.index.OIndexAbstract.rebuild(OIndexAbstract.java:504)
        at com.orientechnologies.orient.core.index.OIndexAbstract.rebuild(OIndexAbstract.java:407)
        at com.orientechnologies.orient.core.index.OIndexAbstractDelegate.rebuild(OIndexAbstractDelegate.java:167)
        at com.orientechnologies.orient.core.sql.OCommandExecutorSQLRebuildIndex.execute(OCommandExecutorSQLRebuildIndex.java:105)
        at com.orientechnologies.orient.core.sql.OCommandExecutorSQLDelegate.execute(OCommandExecutorSQLDelegate.java:74)
        at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.executeCommand(OAbstractPaginatedStorage.java:2578)
        at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.command(OAbstractPaginatedStorage.java:2524)
        at com.orientechnologies.orient.core.command.OCommandRequestTextAbstract.execute(OCommandRequestTextAbstract.java:69)
        at com.orientechnologies.orient.core.db.tool.ODatabaseImport.rebuildIndexes(ODatabaseImport.java:482)
        at com.orientechnologies.orient.core.db.tool.ODatabaseImport.importDatabase(ODatabaseImport.java:428)
        at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.importDatabase(ONetworkProtocolBinary.java:2915)
        at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.executeRequest(ONetworkProtocolBinary.java:654)
        at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.sessionRequest(ONetworkProtocolBinary.java:337)
        at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.execute(ONetworkProtocolBinary.java:201)
        at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:77)

Error: com.orientechnologies.common.io.OIOException

Error: java.io.EOFException

The total record of v_volume became 1441. And the extra record has been deleted.

@tglman, @luigidellaquila, tried with the real records. it works and produce some ghost records. For example, there a class, v_body_type, has two same records after imported, with different rid, #21:0, #21:2. Tried the following script:
select count(*) from v_volume LET $body_t=in('e_has_type')[@class='v_body_type'] where $body_t.@rid=21:0
returned 0 (ZERO)
select count(*) from v_volume LET $body_t=in('e_has_type')[@class='v_body_type'] where $body_t.@rid=21:2
returned all v_volumes' record count.
Read from web studio tool, 21:0 does have edge connected

Clicked one of them:

The 21:0 was gone:

Tried another edge:

Hi @HuangKBAaron,
Is normal that if you export and import only one class if this reference records of different class this will end up to stale references, the import procedure do not clean stale references, yes is ok to delete this data.
In any case i see that you where able to run the import correctly, closing this.
Regards


Hide Invalid Non-Strict Singleton Versions on Production Console

Feature request

What is the expected behavior?
index.js:2 Unsatisfied version x.y.z from ------- of shared singleton module ----- (required ^x.y.z) warnings should not appear on production console.
What is motivation or use case for adding/changing the behavior?
End users on browsers see these errors and think there's something wrong with the page.
How should this be implemented in your opinion?
Provide a setting to hide these warnings and/or only show them during build:
https://github.com/webpack/webpack/blob/0bc3a2ea02ba85e23e4d1e01b4b1f15fb27b5c1d/lib/sharing/ConsumeSharedPlugin.js#L308-L310
https://github.com/webpack/webpack/blob/0bc3a2ea02ba85e23e4d1e01b4b1f15fb27b5c1d/lib/sharing/ConsumeSharedRuntimeModule.js#L118-L124
Are you willing to work on this yourself?
yes

PR welcome, but I think it can be the problem for debugging

Do I not have permission to create a new branch? I have something to PR, but can't push up a new branch.

Ah nm, forked it. Will figure out the CLA with my org here.
https://github.com/webpack/webpack/pull/16388

Can I get a resolution on this MR? We were discussing programmatically removing every warn code snippet in two runtime modules, but I have concerns about maintainability with this approach.


Fix BasicAuth when using PowerTrack 2.0

This looks like it should work, but I get a 401 "Authorization Required" response when I use it with PowerTrack 2.0:
val auth = new BasicAuth(username, password)
val client = new ClientBuilder()
  .name("GnipClient")
  .hosts("https://gnip-stream.twitter.com")
  .endpoint(endpoint)
  .authentication(auth)
  .processor(new LineStringProcessor(queue))
  .gzipEnabled(true)
  .build()

Debugging shows no auth header is sent with the request:

DEBUG [org.apache.http.impl.conn.DefaultClientConnectionOperator] Connecting to gnip-stream.twitter.com:443
DEBUG [org.apache.http.client.protocol.RequestAddCookies] CookieSpec selected: best-match
DEBUG [org.apache.http.client.protocol.RequestAuthCache] Auth cache not set in the context
DEBUG [org.apache.http.client.protocol.RequestTargetAuthentication] Target auth state: UNCHALLENGED
DEBUG [org.apache.http.client.protocol.RequestProxyAuthentication] Proxy auth state: UNCHALLENGED
DEBUG [org.apache.http.impl.client.DefaultHttpClient] Attempt 1 to execute request
DEBUG [org.apache.http.impl.conn.DefaultClientConnection] Sending request: GET /stream/powertrack/accounts/MY_ACC/publishers/twitter/prod.json HTTP/1.1
DEBUG [org.apache.http.wire] >> "GET /stream/powertrack/accounts/MY_ACC/publishers/twitter/prod.json HTTP/1.1[\r][\n]"
DEBUG [org.apache.http.wire] >> "Accept-Encoding: gzip,deflate[\r][\n]"
DEBUG [org.apache.http.wire] >> "Host: gnip-stream.twitter.com[\r][\n]"
DEBUG [org.apache.http.wire] >> "Connection: Keep-Alive[\r][\n]"
DEBUG [org.apache.http.wire] >> "User-Agent: Hosebird-Client 2.2.0[\r][\n]"
DEBUG [org.apache.http.wire] >> "[\r][\n]"
DEBUG [org.apache.http.headers] >> GET /stream/powertrack/accounts/MY_ACC/publishers/twitter/prod.json HTTP/1.1
DEBUG [org.apache.http.headers] >> Accept-Encoding: gzip,deflate
DEBUG [org.apache.http.headers] >> Host: gnip-stream.twitter.com
DEBUG [org.apache.http.headers] >> Connection: Keep-Alive
DEBUG [org.apache.http.headers] >> User-Agent: Hosebird-Client 2.2.0
DEBUG [org.apache.http.wire] << "HTTP/1.1 401 Authorization Required[\r][\n]"
DEBUG [org.apache.http.wire] << "connection: close[\r][\n]"
DEBUG [org.apache.http.wire] << "content-length: 138[\r][\n]"
DEBUG [org.apache.http.wire] << "content-type: application/json; charset=utf-8[\r][\n]"
DEBUG [org.apache.http.wire] << "date: Tue, 19 Jul 2016 14:18:21 GMT[\r][\n]"
DEBUG [org.apache.http.wire] << "server: tsa[\r][\n]"
DEBUG [org.apache.http.wire] << "x-connection-hash: 2473a62afd5d8bf2163f1e3259091fb1[\r][\n]"
DEBUG [org.apache.http.wire] << "[\r][\n]"

I don't have time to open a PR, but I'm using this replacement for BasicAuth instead which works:
package com.twitter.hbc.httpclient.auth;

import com.google.common.base.Preconditions;
import org.apache.http.HttpHeaders;
import org.apache.http.auth.AuthScope;
import org.apache.http.auth.UsernamePasswordCredentials;
import org.apache.http.client.methods.HttpUriRequest;
import org.apache.http.impl.client.AbstractHttpClient;
import sun.misc.BASE64Encoder;

/**
 * Reimplementation of BasicAuth that actually works.
 */
public class WorkingBasicAuth implements Authentication {
    private final String username, password;

    public WorkingBasicAuth(String username, String password) {
        this.username = Preconditions.checkNotNull(username);
        this.password = Preconditions.checkNotNull(password);
    }

    public void setupConnection(AbstractHttpClient client) {
        client.getCredentialsProvider().setCredentials(
                AuthScope.ANY,
                new UsernamePasswordCredentials(username, password)
        );
    }

    @Override
    public void signRequest(HttpUriRequest request, String postParams) {
        request.setHeader(HttpHeaders.AUTHORIZATION,
                createAuthHeader(this.username, this.password));
    }

    private String createAuthHeader(String username, String password) {
        BASE64Encoder encoder = new BASE64Encoder();
        String authToken = username + ":" + password;
        return "Basic " + encoder.encode(authToken.getBytes());
    }
}

@boosh  Did you get "IOException caught when establishing connection to https://gnip-stream.twitter.com/stream/PRODUCT/accounts/ACCOUNT_NAME/publishers/twitter/STREAM.json " warning while connecting to PowerTrack-2.0
The IOException says "org.apache.http.conn.HttpHostConnectException: Connection to http://gnip-stream.twitter.com refused" in my case.

@saikamineni I don't think so. I ended up copying EnterpriseStreamingEndpoint and updating the URLs in it to reflect the powertrack 2.0 URLs.
I got it working in the end...

I am trying to get https://github.com/gnip/sample-kinesis-connector working for PowerTrack 2.0 . But the connection isn't establishing. But the connection is established when I tried using EnterpriseStreamExample.

EnterpriseStreamingEndpoint uses the wrong URL. Copy it and create your own version replacing BASE_PATH with:
private static final String BASE_PATH = "/stream/powertrack/accounts/%s/publishers/%s/%s.json";

Worked for me.

Yes, I made all the changes to point to the new URL and tested with EnterpriseStreamExample, I was able to pull the data. Once I start integrating it with Sample Kinesis Connector the connection is not being established.

This is the stacktrace of the exception.

Not sure. Those http:// protocols should be https:// though I guess.

I had the same issue. I created a pull request here: https://github.com/twitter/hbc/pull/169

@saikamineni Did you ever figure out your issue? I'm having the same issue! <3

If you are try to get this working for PowerTrack 2.0, check the dependencies. One of the dependencies related to AWS caused the issue in my case.

If you are using HBC to connect to PowerTrack 2.0 using the same method in pull request #169 by @rj93 then a recent change to the twitter API will cause your connection to fail authorisation.
The reason is that auth.signRequest is called multiple times in com.twitter.hbc.httpclient.ClientBase and multiple headers are added to the request. A simple workaround is to check in the signRequest method and only add a header if it doesn't exist...
if(request.getFirstHeader("Authorization") == null) {
    request.addHeader("Authorization", authValue);
}


No items or small amount of items: Map does not resize

The map does not resize to the set map dimension on collapsing.
No code was editing from checking out the repository apart from below in which the problem can be recreated:
for (int i = 0; i < 2; i++) {
            testData.add("Item " + i);
 }

Closed without a solution @ashleypeacock  did you find a way?

I found a solution to the caused effect without resizing. I added a fake footer view at the bottom to cover the map when there's less than 3 items.
This package is now being beautifully used in the android app Bubbal with some tweaks.
Thanks for the reminder : do you want me to add  what we did?

yes please if you can. that would be really helpful.
-------- Original Message --------
From:ashleypeacock<EMAIL_ADDRESS>Sent:Fri, 21 Aug 2015 15:54:53 +0530
To:dlukashev/AndroidSlidingUpPanel-foursquare-map-demo<EMAIL_ADDRESS>Cc:rishabhsri20<EMAIL_ADDRESS>Subject:Re: [AndroidSlidingUpPanel-foursquare-map-demo] No items or small amount of items: Map does not resize (#5)

I found a solution to the caused effect without resizing. I added a fake footer view at the bottom to cover the map when there's less than 3 items.
This package is now being beautifully used in the android app Bubbal with some tweaks.
Thanks for the reminder : do you want me to add what we did?
—
Reply to this email directly or view it on GitHub.￼

see https://github.com/dlukashev/AndroidSlidingUpPanel-foursquare-map-demo/issues/11


feat(api): deprecate get account endpoint

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #50483

Always a good idea, @huyenltnguyen. He's my go-to for "can I break this?".


Crash with qwik v1.6.0 : document is not defined

Project fails to build with the latest qwik release v1.6.0
[vite] Error when evaluating SSR module /src/routes/demo.css.ts.vanilla.js: |- ReferenceError: document is not defined
For what i know, it happens in injectStyles function in @vanilla-extract/css/injectStyles .
var injectStyles = _ref => {
  var {
    fileScope,
    css
  } = _ref;
  var fileScopeId = fileScope.packageName ? [fileScope.packageName, fileScope.filePath].join('/') : fileScope.filePath;
  var stylesheet = stylesheets[fileScopeId];
  if (!stylesheet) {
    var styleEl = document.createElement('style');
    if (fileScope.packageName) {
      styleEl.setAttribute('data-package', fileScope.packageName);
    }
    styleEl.setAttribute('data-file', fileScope.filePath);
    styleEl.setAttribute('type', 'text/css');
    stylesheet = stylesheets[fileScopeId] = styleEl;
    document.head.appendChild(styleEl);
  }
  stylesheet.innerHTML = css;
};

I tried skipping the call when document is not defined. It does not crash but the styles are completely ignored. This is no solution.
if(typeof document !== "undefined"){
  inject(${JSON.stringify(css)});
}

You can repro with this repo : https://github.com/franck-co/styled-vanilla-extract-hot-reload
On branch master (qwik 1.5.7) this is working as expected
On branch 1.6.0 (qwik 1.6.0) it crashes

This is actually a problem with Qwik 1.6.0 and should be reported there. During dev mode, right?

That's right

Is there an issue on Qwik's repo? Couldn't find one?

Should be fixed by https://github.com/wmertens/styled-vanilla-extract/commit/bfdccadfbdbf5310a505ada5fd89bd9da89f4e0a

I can confirm things work fine with Qwik 1.7.1 and SVE 1.0.
Thanks, @wmertens. 🙇🏻


raft: cache progress ids to avoid frequent copy

Now for every bcast, we have to clone all progress IDs, this is wasteful. We can cache the progress IDs and use them directly, no need to another clone.
I write a simple test to bench:
#![feature(test)]

extern crate test;
extern crate flat_map;

#[cfg(test)]
mod tests {
    use test::{self, Bencher};
    use flat_map::FlatMap;

    #[bench]
    fn bench_flatmap_keys(b: &mut Bencher) {
        let mut m = FlatMap::with_capacity(3);
        m.insert(1, 1);
        m.insert(2, 2);
        m.insert(3, 3);

        b.iter(||{
            let ids: Vec<_> = m.keys().cloned().collect();
            test::black_box(ids);
        });
    }

    #[bench]
    fn bench_keys(b: &mut Bencher) {
        let m = vec![1, 2, 3];

        b.iter(||{
            let ids: Vec<_> = m.clone();
            test::black_box(ids);
        });
    }

    #[bench]
    fn bench_option_keys(b: &mut Bencher) {
        let mut m = Some(vec![1, 2, 3]);

        b.iter(||{
            let ids = m.take().unwrap();
            test::black_box(&ids);
            m = Some(ids);
        });
    }
}

The result:
test tests::bench_flatmap_keys ... bench:          36 ns/iter (+/- 0)
test tests::bench_keys         ... bench:          33 ns/iter (+/- 1)
test tests::bench_option_keys  ... bench:          12 ns/iter (+/- 1)

The performance of caching IDs is better. Because bcast is a very frequent operation, I think this optimization is worthful.
PTAL @BusyJay @javaforfun @overvenus

How about make send, send_heartbeat and send_append not methods any more? So clone and cache are not necessary.

How about make send, send_heartbeat and send_append not methods any more?

Using Macro? I doubt this may not fix the origin reference problem and will change the codes a lot, not a good idea now.

One way is define them as function, the other way is seperate prs and messages from Raft. So they won't affect each other.

I guess these may also change raft codes a lot, maybe you can try it later.


handle interpreted text blocks

This PR renders interpreted_text blocks using a <span> tag and adding a class for the role if specified.

Thanks!


almalinux/9.aarch64 vagrant box not working with m1 mac

Hello!
I tried to run the AlmaLinux 9 aarch64 vagrant box with my M2 Macbook Air today but it failed at the Mounting shared folder step because Parallels Tools are not installed.
Here is the full output:
paulmaunders@pauls-air-m2 test-parallels-alma9 % vagrant up
Bringing machine 'default' up with 'parallels' provider...
==> default: Box 'almalinux/9.aarch64' could not be found. Attempting to find and install...
    default: Box Provider: parallels
    default: Box Version: >= 0
==> default: Loading metadata for box 'almalinux/9.aarch64'
    default: URL: https://vagrantcloud.com/almalinux/9.aarch64
==> default: Adding box 'almalinux/9.aarch64' (v9.0.20220905) for provider: parallels
    default: Downloading: https://vagrantcloud.com/almalinux/boxes/9.aarch64/versions/9.0.20220905/providers/parallels.box
    default: Calculating and comparing box checksum...
==> default: Successfully added box 'almalinux/9.aarch64' (v9.0.20220905) for 'parallels'!
==> default: Registering VM image from the base box 'almalinux/9.aarch64'...
==> default: Creating new virtual machine as a linked clone of the box image...
==> default: Unregistering the box VM image...
==> default: Setting the default configuration for VM...
==> default: Checking if box 'almalinux/9.aarch64' version '9.0.20220905' is up to date...
==> default: Setting the name of the VM: test-parallels-alma9_default_1666801345265_43507
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Preparing network interfaces based on configuration...
    default: Adapter 0: shared
==> default: Clearing any previously set network interfaces...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: :22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection refused. Retrying...
    default: Warning: Connection refused. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for Parallels Tools installed on the VM...
==> default: Parallels Tools were not detected on this VM! They are required
==> default: for shared folders, time sync and more. If shared folders are not
==> default: working on this machine, please install Parallels Tools within the
==> default: virtual machine and reload your VM.
==> default: Mounting shared folders...
    default: /vagrant => /Users/paulmaunders/Documents/Code/test-parallels-alma9
Vagrant was unable to mount Parallels Desktop shared folders. This is usually
because the filesystem "prl_fs" is not available. This filesystem is
made available via the Parallels Tools and kernel module.
Please verify that these guest tools are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t prl_fs -o uid=1000,gid=1000,_netdev vagrant /vagrant

The error output from the command was:

mount: /vagrant: unknown filesystem type 'prl_fs'.

It looks like this is a known problem with Parallels Tools not currently supporting RHEL 9: https://forum.parallels.com/threads/parallels-tools-do-not-install-on-rhel9.357546

I was able to successfully install Parallels Tools as of yesterday (2023-02-23).  Another comment in that post also notes they were successful.
I'm running:
Parallels v18.2.0 (53488)
AlmaLinux 9.1 via Vagrant Box almalinux/9.aarch64 (v9.1.20230122)
@paulmaunders - Based on the work you did in #115, do we maybe just need a new box version released at this point?

Also confirmed that enabling guest tool updates in the Vagrant file completes successfully.  I can use this as a workaround in the meantime, but having Parallels Tools baked into the Vagrant box would save some significant boot time.  My use-case is testing Ansible changes, so I'm spinning boxes up & down constantly as I make changes.
node.vm.provider "parallels" do |prl|
    prl.update_guest_tools = true
end

==> alma9: Machine booted and ready!
==> alma9: Checking for Parallels Tools installed on the VM...
==> alma9: Parallels Tools were not detected on this VM! They are required
==> alma9: for shared folders, time sync and more. If shared folders are not
==> alma9: working on this machine, please install Parallels Tools within the
==> alma9: virtual machine and reload your VM.
==> alma9: Installing the proper version of Parallels Tools. This may take a few minutes...
==> alma9: Parallels Tools have been installed. Rebooting the VM...
==> alma9: Attempting graceful shutdown of VM...
==> alma9: Booting VM...
==> alma9: Waiting for machine to boot. This may take a few minutes...
==> alma9: Machine booted and ready!
==> alma9: Mounting shared folders...
    alma9: /vagrant => /Users/klesher/code/ansible/tests

Same issue: https://github.com/AlmaLinux/wiki/issues/293


Add blank line when template does not end in newline

Minor feature request: When adding a template, if the upstream .gitignore template does not end in newline, add one when generating the .gitignore file.

@bamapookie Thanks for that - seems reasonable.
Do you have any example of the template that has no new line at the end?

Not off hand.  I usually insert the blank line myself when I notice it.  Will update when I find one.  Another option would be to request some QC upstream.

macOS template is one.

-1 here.
You do not know what the line end should look like: LF? CRLF? You can look in the file, but what if the file contains a mixture? What if the file is empty, or a single line without a line end?
The more you try to deal with edge cases, the more you have opportunities for the code to do things that the user did not expect.
(Aside note: Even without the CRLF conundrums, I'd recommend against doing this. If something unexpected happens, mechanisms like the one proposed here add yet another place that you have to check whether it might be responsible. This is a general caveat against behaviour that is out of scope - and modifying files just when they are read is definitely out of scope. Having standard line endings after the ignore file has been rewritten is a different issue, here people expect changes to the ignore file.)

You are correct that fixing the template upstream would be better, but inserting a blank line at the end upon insertion would not be any worse than adding the comment line with the template name at the top.

Invisible changes are much harder to diagnose as the cause of a problem, so I assume it is somewhat worse.
Note that problems can occur if the .gitignore file is processed by software other than git. E.g. if it's being inlined into a HTML file, or style checked, or something I don't think about right now.


Remove version: Tableau.Public version 24.1.1062

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://downloads.tableau.com/public/TableauPublicDesktop-64bit-2024-1-2.exe
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 896)


[Q] How to remove cell comments

I've added a comment to a cell as follows:
ws.getCell('A1').note = {
    texts: [
        {
            text: 'some comment',
        },
    ],
};

I'm then trying to completely remove the comment afterwards, but i couldn't see any obvious way to do this.

check this: https://github.com/exceljs/exceljs#cell-comments

ws.getCell('A1').note = {};
should works;

Seems that ws.getCell('A1').note = {} doesn't remove the note. It is still there but just empty, which results in having an empty note in the xlsx file.
The only workaround I found so far is
ws.getCell('A1')._comment = undefined


problem starting server on glusterFS

Which chart:
stable/postgres
What happened:
nami    ERROR Unable to start com.bitnami.postgresql: Cannot find pid file '/opt/bitnami/postgresql/tmp/postgresql.pid'
What you expected to happen:
no error, server starts up
How to reproduce it (as minimally and precisely as possible):
set your default storage class to be glusterFS (or specify glusterFS on the helm command-line)
Anything else we need to know:

Do you mind running helm repo update and try to install the chart again?
I have seen some issues fixed recently related with persistence so maybe is already fixed in the latest version.


Stricter Writer

Hi,
I made the packages writer-cps-mtl and writer-transformers-mtl which implement a stricter writer monad transformer in continuation passing style as was discussed before on the Haskell mailing list etc

http://hackage.haskell.org/package/writer-cps-mtl
http://hackage.haskell.org/package/writer-cps-transformers

See also the current reddit discussion:
https://www.reddit.com/r/haskell/comments/50hf2s/stricter_writert_and_rwst_replacements/
Would you be interested in including this into mtl? If not it can also exist as a separate package, but I guess it would be nice to have a well-behaving writer around in the standard toolbox.
Daniel

@minad Thank you for writer-cps-* packages, I'll incorporate them into the next release of ether as the default implementation for Writer.

It seems transformers pulled writer-cps-transformers, see https://hub.darcs.net/ross/transformers/patch/b6743fad9f5ce8a9e13f15320f7d2752330084e2

Assuming that these provide the same interface as the other State/Writer data types (which appears to be the case from a cursory glance, although I have not looked deeply), I'd happily accept a patch which adds MonadState/MonadWriter instances for these.

As soon as the new transformers is released, you can pull the code from http://hackage.haskell.org/package/writer-cps-mtl. I can also prepare a patch. The same applies to the other writer-cps-* packages, providing orphan instances for exceptions, lens and mmorph.

I believe #67 implements this on mtl's side, so closing. Please re-open if you disagree.


fix: update spark-branch with latest develop

Codecov Report

Merging #926 (7aa264a) into spark-branch (2dd0390) will increase coverage by 0.28%.
The diff coverage is 98.87%.

@@               Coverage Diff                @@
##           spark-branch     #926      +/-   ##
================================================
+ Coverage         90.51%   90.80%   +0.28%
================================================
  Files               166      169       +3
  Lines              4513     4653     +140
================================================
+ Hits               4085     4225     +140
  Misses              428      428

Flag
Coverage Δ

py3.8-ubuntu-latest-pandas
90.80% <98.87%> (+0.28%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

setup.py
0.00% <ø> (ø)

tests/unit/test_summarizer.py
100.00% <ø> (ø)

src/pandas_profiling/visualisation/utils.py
79.54% <83.33%> (+0.47%)
:arrow_up:

src/pandas_profiling/model/pandas/utils_pandas.py
93.75% <87.50%> (-6.25%)
:arrow_down:

src/pandas_profiling/config.py
100.00% <100.00%> (ø)

src/pandas_profiling/model/alerts.py
94.24% <100.00%> (ø)

...filing/model/pandas/describe_categorical_pandas.py
99.08% <100.00%> (+0.02%)
:arrow_up:

src/pandas_profiling/model/summary_algorithms.py
75.00% <100.00%> (ø)

...das_profiling/report/presentation/core/variable.py
66.66% <100.00%> (ø)

src/pandas_profiling/report/structure/report.py
94.04% <100.00%> (+0.07%)
:arrow_up:

... and 9 more

Continue to review full report at Codecov.

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


Avoid a dedicated thread in ConsoleLoggerProcessor

https://github.com/aspnet/Logging/blob/db73396309d4989925486061e0a88997b966ae0a/src/Microsoft.Extensions.Logging.Console/Internal/ConsoleLoggerProcessor.cs#L22

The issue is we're using an additional thread which stays idle for the most of the time. Backlogging for now to see if this causes any real issues.

@SteveSandersonMS right on.  I tried it out a few days ago (Blazor 0.1.0) and was met with threading issues, but that could just be the newness of it all.

So it looks like https://github.com/aspnet/Logging/pull/739 broke WebAssembly compatibility by using Threads.
https://github.com/aspnet/Logging/blob/d09254b564c9f108a136287f558fd272100b84b1/src/Microsoft.Extensions.Logging.Console/Internal/ConsoleLoggerProcessor.cs#L22-L27

Closing this. We can write a separate logger implementation for blazor if requirement comes up.
I think using Console.WriteLine in the browser is very limiting anyway considering how rich browser console is.


pydantic migration v3 -- w/ individual commits

Uploading branch for reference. We'll be cherry picking some commits from here onto master (commits that are compatible with pydantic v1). And the rest of the PRs will be cherry-picked onto another branch in September.

auto config update
Update to import from pydantic instead of langchain_core.pydantic_v1
Use model_rebuild instead of update_forward_references
x
MANUAL: Update BaseLanaguageModel with model_config = ConfigDict(arbitrary_types_allowed=True)
MANUAL: Replace config in tools. Determine why it inherits from Serializable?
MANUAL: Update create subset model
MANUAL: Add Optional for model_rebuild for StrOutputParser
MANUAL: Update serializable to handle excluded fields correctly
MANUAL: Force model_rebuild, bring Optional into scope
MANUAL: Update create_model to use new RootModel (INCOMPLETE)
qxqxqx
MANUAL Handle AnyID in unit tests
MANUAL: Fix REPR for Document in a test
MANUAL: Update @pre_init decorator to work with pydantic 2
MANUAL: Add missing AnyID import
STASHED CHANGE
MANUAL: Fix RunnableAssign parameterization
STASHED CHANGES
MANUAL: Update Serializable to handle default factory for is field useful
MANUAL: Fix REPR for ToolMessage

reference:
@classmethod
def model_parametrized_name(cls, params: Tuple[Type[Any], ...]) -> str:
    return f'{params[0].__name__.title()}Response'


Add support for registering PDU allocators for TCP and UDP

Inner PDU protocols can be registered for well-known port numbers and associated with the source or destination port fields.

I would like to upstream this enhancement.

Please approve if you don't have any other comments, @jamesm-cerebras .


Form Validators Don't Work In PreferenceAssessmentScreen

Steps to reproduce:

Leave the questions under 'ART Refill' and 'Notifications' unanswered.
Tick at least 4 support options that open up a follow up question, e.g. 'Saturday Clinic Club', 'Community Youth Club', 'Home-visit by PE', and 'School visit by PE'. Do not answer the follow up questions.
Click save at the bottom of the form.

Now the form validators of the 'ART Refill' and 'Notifications' questions do not work. They should react to the unanswered questions there and display a red indicator text.
This is an issue because the logic of the form relies on the validators, i.e. if the validators don't work the integrity of the data stored in the database is not guaranteed.
If you answer the follow up questions from step 3 (i.e., fulfill the validators in the 'Support' section) there will be an error on the console Failed assertion: boolean expression must not be null, which occurs because the boolean phoneAvailable is still null when the data is attempted to be stored in the database.

Possible Solution
Possibly, this bug occurs because there are too many form validators in the preference assessment screen. It might help if the form is split up into several screens (ART Refill, Notifications, Support, Psychosocial Support, Unsuppressed Viral Load), e.g., using a (horizontal) stepper. This would also improve the usability because it reduces the amount of information the user has to perceive on one page:

Fixed with flutter v1.7.8+hotfix.4 (could not reproduce)?

Problem does not seem to occur anymore on the latest version (1.0.2). Closing this issue.


Athletics Page needs entirely redone

Between the horrible CSS and hard coded information, it has to go.

Make sure that all your work is reactive with window size and looks nice


[FEAT] Display End event

Closes #55

@csouchet do we update the bpmn support doc each time we support a new bpmn type or we do it prior releasing? if the answer is the 1st proposal, this PR should update the doc
@aibcmars what do you think about it?

Done :)


Reduce Shard Number to 1

Hi,
after I run the mongodb-connector each mongodb database is stored in elastic search on 10 shards.
How can I reduce the amount to only a single shard?
I know that having more shards improves writing performance. But I think having only one shard imporoves the reading perforance
So how to set shard numbers to 1?
thanks

The elastic doc manager creates indexes only by indexing documents into them; the indexes are created with whatever the default settings are. You can change the settings like this: https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-update-settings.html#indices-update-settings.


Question about POD-Attention

I got some questions while reading the implementing codes of 'POD-attention'

what does the fused_params  mean? It looks like it has four values, 9, 11, 15, and 64, do each of these represent different levels of fusion?
I'm little confused about codes here.  Does num_splits_p indicate that the prefill is divided into num_splits_p chunks (like chunked-prefill)? So num_splits_d means to slice the decoding across KV?  Moreover, The note says 'Used for 2 TBs per SM', is this because prefill and decode each use a thread blocks?

 // Generate at least 1 full wave of decode for better overlap; Used for 2 TBs per SM
    if (fused_params == 9 ||
        (fused_params == 15 && (batch_size_p * num_heads_p * num_m_blocks_p >= dprops->multiProcessorCount * 2 ||
                                batch_size_p * num_heads_p * num_m_blocks_p * 2 < 0.8f * dprops->multiProcessorCount * 2)))
    {
        if (batch_size_d * num_heads_d * num_m_blocks_d >= 0.8f * dprops->multiProcessorCount * 2 &&
            batch_size_d * num_heads_d * num_m_blocks_d < dprops->multiProcessorCount * 2)
            num_splits_d = dprops->multiProcessorCount * 2 / (batch_size_d * num_heads_d * num_m_blocks_d) + 1;
    }

seems both num_splits_p and num_splits_d split among KV？

fused_params is used as a configuration parameter, should default to 15. fused_params = 9 has POD use 2 threadblocks per SM, 11 uses 4 threadblocks per SM, 15 attempts to pick the best between 2 and 4 based on input parameters. 64 uses HFuse instead of POD.
num_splits_p and num_splits_d controls FlashDecoding (https://pytorch.org/blog/flash-decoding/), which yes, splits along KV. This is used when the decode batch size or prefill sequence length is too small to saturate the GPU's parallelism. Keep these as 0 in default, everything else will be automatically handled internally.

Thx for your response！ So how do you control the number of thread blocks on each SM?  Isn't this limited by registers and shared memory?

That's correct.
In this line: https://github.com/microsoft/vattention/blob/3459e5a09bcc38bbdcb1acce8243f240d17db1c5/pod_attn/pod_attn/fused_fwd_launch_template.h#L540
We use fused_params = 9, which launches the kernel with tile sizes of 128 * 128 (for query) and 64 * 128 (for K/V), and 128 threads per threadblock (4 warps). This allows 2 threadblocks / SM on A100 and H100.
This line:
https://github.com/microsoft/vattention/blob/3459e5a09bcc38bbdcb1acce8243f240d17db1c5/pod_attn/pod_attn/fused_fwd_launch_template.h#L534
is for fused_params = 11, which uses tile sizes of 64 * 128 (for query) and 32 * 128 (for K/V) and 64 threads per threadblock (2 warps). This halves the shared memory and register usage of each threadblock, fitting 4 threadblocks / SM on A100 and H100.

got it 💯


add coverage flags to nosetest command

Coverage remained the same at 55.79% when pulling 2f18cc3c094bacab710140f2e5965ba5f59232a4 on more-coverage into 838eec4130ec14fa8141c91e9556c32f07be7979 on master.


add note for ServiceBus package inclusion

When working in Visual Studio, if you create an event hubs trigger project, you get the package references that you need (Microsoft.Azure.WebJobs.ServiceBus, etc).
However, if you want a function triggered some other way (for example queue storage) and want to output to event hub, the package reference isn't there. This PR adds a note to the section on usage of event hubs for output, reminding the user to add these references.

@ : Thanks for your contribution! The author, @tdykstra, has been notified to review your proposed change.

@ : Thanks for your contribution! The author, @tdykstra, has been notified to review your proposed change.

#sign-off

I removed the note formatting, as you suggested.

Thank you!


RFC: Remove lock step versioning between core modules

Affected Version
4.x
Description
Currently we have a lock step between core modules, in that they are only ever tagged as new versions during a recipe release process, e.g. cms/framework/reports/siteconfig are all 4.3.1, admin/versioned/campaign-admin/asset-admin are all 1.3.1 etc.
Problems with removing lock step

It makes it a little harder to know which versions people are probably using with admin 1.3.1 (for example) if they report a bug in it
It makes core recipe planning slightly harder, because version bumps are no longer the same for all

Benefits of removing lock step

Patch fixes take less time (can sometimes be 3 months or more with lock step) to get to users
(Assumption) users will not resort to using unstable dev branches to pull fixes in
We can quickly release a fix for a small issue without doing a full recipe release
Less active core contributors will be happier to do module tags for new fixes

Proposed solution

We remove the necessity for fringe-core modules to be in lock step with each other for patch versions. Recipes continue to be compiled with the latest minor/patch releases available at the time, and/or release new minor/patch versions during the process of creating them.
We continue to keep silverstripe/installer, silverstripe/recipe-core, silverstripe/recipe-cms, silverstripe/framework, and silverstripe/cms in lock step with each other, since these are the most commonly used modules and recipes
Add notes to the documentation that clarify this process for the core team

Side notes

CWP recipes are not using lock step except for the core CWP modules (which constitute a small amount of the CWP recipe). Supported modules are tagged whenever they have fixes (or features) available.

cc @silverstripe/core-team

It makes it a little harder to know which versions people are probably using with admin 1.3.1 (for example) if they report a bug in it

composer show is all bug reporters need to run though, right? And if they downloaded ye-olde-zip, we should be able to tell what package versions were released with that the recipe version (or ask them to upload the composer.lock that’s bundled in the ZIP)?

We can quickly release a fix for a small issue without doing a full recipe release
Less active core contributors will be happier to do module tags for new fixes

I’d be happy with this approach - I’m perfectly happy creating tags, but the full release process is daunting and probably too time consuming for me to want to volunteer for! Are there any practical concerns with adopting this approach (e.g. around security releases)? None spring to mind, but I’m not heavily involved with releases...

We continue to keep silverstripe/installer, silverstripe/recipe-core, silverstripe/recipe-cms, silverstripe/framework, and silverstripe/cms in lock step with each other, since these are the most commonly used modules and recipes

Recipes/installer I can understand, but why keep silverstripe/framework + silverstripe/cms in lock step? Their minor versions would still always be in lock step, so I don’t see why it would matter if the patch versions diverged (as long as we correctly bump cross-package dependencies if we need to).

Yeah it was for an “ease into it” approach but I’m happy to make a blanket rule that recipes are locked and modules (incl framework) are not

I'm all for this, it should make things easier which is always a good thing. It should also speed up the "speed to market" of peoples PR's making it out to their instances which has always been a slow, painful process for the person who has contributed. I'm all for it being across everything that the core team maintains.

blanket rule that recipes are locked and modules (incl framework) are not

I'm still in favour of this. composer show is a common request anyway for raised issues. Anybody core contributor should feel comfortable releasing a patch version if they think there's reason.

continue to keep silverstripe/installer, silverstripe/recipe-core, silverstripe/recipe-cms, silverstripe/framework, and silverstripe/cms in lock step with each other, since these are the most commonly used modules and recipes

What are the main reasons for that? Having "exceptions" of the rule usually makes the rule more complicated. People will have to remember what module is in-sync and what isn't. Why can't we apply the rule ultimately to everything and make things simpler?

Great discussion, I think the benfits outweigh the risks here. Faster release cycles on individual modules is a big one. That relies on either more non-staff core committers willing to tag, or staff core committers making it a better part of their team processes. Sounds reasonable.
It'll make it harder to tell if a certain module release line is still supported: You need to look up which release is packaged in a recipe, since that's what determines support. So if we package silverstripe/versioned:1.4.1 with silverstripe/recipe-cms:4.4.0, but then silverstripe/versioned:1.6.0 with silverstripe/recipe-cms:4.5.0, it effectively means silverstripe/versioned:1.4 and silverstripe/versioned:1.6 minor release lines are supported for the duration of the recipe, but silverstripe/versioned:1.5 isn't (was never part of a recipe). We'll need to document that well, and make it easy for people to make that connection.

We remove the necessity for fringe-core modules to be in lock step with each other for patch versions. Recipes continue to be compiled with the latest minor/patch releases available at the time, and/or release new minor/patch versions during the process of creating them.

As discussed in in https://github.com/silverstripe/silverstripe-versioned/issues/230, this does not imply that we're aiming to support modules across minor release lines. We should bump dependencies as required, I'm not willing to jump through a lot of hoops to have silverstripe/framework:4.6 support silverstripe/versioned:1.2 unless it comes "for free". And we won't actively test combinations other than the ones declared in recipes.
Does anyone have a view on how this affects the cow release tool? I guess we'll need to do more "recipe planning" than currently, but the mechanics for that should already exist because it's how the CWP release works, right?
As a sidenote, this doesn't change any discussions around requiring new major versions of modules alongside new minor versions of core. silverstripe/graphql is the (only?) offender there, we've bumped from 1.x to 3.x in silverstripe/admin:4.x releases. That's an exception rather than the rule. In my opinion, we should've never tagged silverstripe/graphql:1.x, and hence never declared any of those APIs as stable. That has some nasty downstream effects on modules like silverstripe/versioned-admin and dnadesign/silverstripe-elemental who need to pull in those new releases. As far as I'm concerned, none of this will change with this ticket: It's still an awkward exception, we should a) stick to semver incl. dependencies and b) be very careful what we declare as public/stable APIs.

continue to keep silverstripe/installer, silverstripe/recipe-core, silverstripe/recipe-cms, silverstripe/framework, and silverstripe/cms in lock step with each other, since these are the most commonly used modules and recipes

I think we could do a "soft lockstep" where it's more common to bump dependencies. If you're introducing a new utility class or interface in framework because you need it in versioned, we'd bump the versioned dependency on framework. They'll both need minor or patch releases.
That brings up a good point: We have to be super careful with these cross module dependencies on new behaviour/classes/interfaces. It'll be very easy to just tag versioned in the example above, and forget that you'll also need to tag framework. This is an argument for only implementing these features in a backwards compatible way, but it won't always be as straightfoward as a class_exists() check.

I really still think that the recipes should continue to be in lock step with each other.
While I'm proposing we remove lock step for patch tags, I can also see that modules like reports or siteconfig that never have any new features added may get to a point where it doesn't make any sense to release a new minor version of them any more if they aren't in lock step. Then you get siteconfig + reports 4.4.0 being used in silverstripe-installer 4.9.0 or something, which goes back to making it tricky to achieve what you said @chillu about not supporting cross module versions.
Summary: I think we need to keep lock step on minor versions, but remove it for patch versions. And keep it for recipes.

Summary: I think we need to keep lock step on minor versions, but remove it for patch versions. And keep it for recipes.

So in terms of the benefits we're gaining from this: Bugfixes (mostly patch level) can be pushed out quicker, but new features (mostly minor level) need to wait until the next minor recipe release. I think that's a good compromise. It also allows us to test cross-interactions of features before a) releasing them and b) committing to their stable APIs. Otherwise you might release a new versioned API, and then figure out it's a bad idea because it doesn't work with fluent two months later in the CWP recipe pre-release testing. Some of this can be captured through automation tests and peer review, but there's a lot of combos to consider. If people are are eager to use new features prior to recipe releases, we could always work with per-module alpha releases?

we could always work with per-module alpha releases?

I think using dev branches is good enough for that as long as we keep tests green.

continue to keep silverstripe/installer, silverstripe/recipe-core, silverstripe/recipe-cms, silverstripe/framework, and silverstripe/cms in lock step with each other, since these are the most commonly used modules and recipes

It feels I may be misunderstanding this bit.
Do you suggest recipe versions reflect module versions, or do you mean silverstripe/framework patch version should be kept in sync with silverstripe/cms?

I think the consensus is that all modules should not be in lock step any more, but I think recipes still should be with other recipes (installer is also a recipe)

Looks like everyone so far is in agreement, we could always trial this approach and if we do run into any unforeseen issues it wouldn’t be hard to go back to the status-quo for the next minor version. We could even go back in a minor release by just tagging everything with the highest patch version number and performing a release. Tldr; I don’t see any risks of trialing this.
One thing worth considering is what constitutes a release-worthy change? My instinct says that will probably just amount to “use your best judgement” so we avoid tagging every merged PR (or actually, maybe we could if we wanted? it’s just another number, right?)

One thing worth considering is what constitutes a release-worthy change?

I'd consider anything higher than impact/low

I'd consider anything worth being installable.
So a docs change doesn't matter that much as a code change, even a small patch, which could be released. The most annoying thing for us are modules with code changes that are not "released". When people do PRs, they expect to be able to use them back in their projects when they are merged and referencing them via commit hash or worse via dev-branch wouldn't be preferable I'd say.

One thing worth considering is what constitutes a release-worthy change? My instinct says that will probably just amount to “use your best judgement” so we avoid tagging every merged PR (or actually, maybe we could if we wanted? it’s just another number, right?)

I'm a big fan of "use your best judgement". "It's just another number" also hits the nail on the head. It's pretty easy to release with GitHub UI - I don't really conceive any downsides of tagging

I'd consider anything higher than impact/low

This is a good indicator - but probably doesn't have to be the rule.

So a docs change doesn't matter that much as a code change, even a small patch, which could be released.

When we release CWP - we don't tag docs changes or updates to tests/test configuration. We will release anything else though.

The most annoying thing for us are modules with code changes that are not "released". When people do PRs, they expect to be able to use them back in their projects when they are merged and referencing them via commit hash or worse via dev-branch wouldn't be preferable I'd say.

Currently, any module that's not part of the "core" definition (not included in silverstripe/installer) is not part of this "lock-step" versioning. You're welcome to open an issue on a repo (or pop a message in community Slack - perhaps the #get-involved channel) and ask for a tag - we're happy to do that. Given this RFC is accepted that will be possible for any other (non-recipe) module too!

@tractorcow would you like to weigh in?

I'm generally supportive of this approach and also keen that it is most enthusiastically supported by the people who do release work most frequently, which seems to be the case. :+1: from me

This all sounds good. @unclecheese As the main person performing core recipe releases at the moment, can you please weigh in here? Is anyone keen to draft the required release process docs and guidance for core committers?

I’m happy to draft a write up for this

Not really involved in the actual release, so I don't have the most informed opinion about this. But it seems like a relatively easy way to gain more flexibility without downside.
Put me in the thumbs up column.

Cool - accepted with a quorum of 7/12 core committers in favour (with @unclecheese confirming verbally)

Versioned 1.3.4 now breaks the core module version lock step. This RFC has been accepted, so going to close it now. Thanks everyone 🎉

@robbieaverill Can you please document this somewhere for core maintainers? In particular, which modules continue in lockstep and which aren't?

Docs PR at https://github.com/silverstripe/silverstripe-framework/pull/9000

Late thought: what do we do about changelogs? IIRC cow currently generates these, and they encompass the changes across all core modules for that given release. Lets say we find a high-impact bug in the CMS module tomorrow, and decide to release 4.4.2 of just CMS, do we create a 4.4.2.md, even though framework doesn’t have a 4.4.2? I think that would be a problem point for us, and confusing for devs reading the docs.

The changelogs at the moment are really a list of what's included in a recipe release, rather than individual modules (just info, not saying it should remain this way)

Late thought: what do we do about changelogs?

Yeah, I guess one of the "amenities" we provide through a recipe release is a more curated changelog. For patch releases, I would say that Github commit messages are sufficient. This is an effort to simplify our release process, and we're not achieving that by introducing a repo/module-specific changelog generation and release process.
Github provides release drafts with Markdown notes. While that's a convenient shortcut, it also risks that the info contained in there is not duplicated in the highlevel recipe changelog. I'd rather keep it simple: If you want to stay up to date with bugfix releases, you need to read raw changelogs. Otherwise wait for recipe releases.
Here's a curly one: Do we allow module security releases without recipe releases? https://docs.silverstripe.org/en/4/contributing/making_a_silverstripe_core_release/#security-release-process says "make a core release", which implies a recipe release. If we don't follow the core release process, important steps will likely be skipped (e.g. comms). I'd suggest keeping security releases to recipe releases, unless they need to be actioned quickly (e.g. already publicly disclosed). And then aim to do at least one or two recipe releases per quarter. Put another way: Security releases are currently our main driver for perfoming those recipe releases
Also, I've gone through https://www.silverstripe.org/download/security-releases/ and made it clear which modules those versions relate to, that was a bit haphazard - they should be resolveable composer constraints now.

Do we allow module security releases without recipe releases?

I think we can probably make a light ruling around this. If a patch is prepped for a minor security issue I don't see a problem with just releasing it for the masses when it's ready? Saves juggling more things during a recipe release.


Lack attribute when import saved svg file

when i created a svg file, i put attribute 'label' in it. And i changed the saved function to make the label attribute code in file. for example, like 'label="xxxxxx"'.
However, when i import this svg file, the attribute missed.
The attachment is the example.

path数据得到

@lanqiuzf Method Draw cleans up certain attributes upon importation.


ext: load C extension files from non-native gems via "require"

What problem is this PR intended to solve?
As reported in #2300, we should be loading the C extension relying on require and $LOAD_PATH and not using require_relative.
Have you included adequate test coverage?
No. This is a bit challenging to test, as we'd have to modify the gem installation (and delete the nokogiri.so files present under "lib/nokogiri"), and the regression value is pretty low (especially given the verbose comment in this PR).
That said, this change has adequate test coverage already in the gem-install CI pipeline, to ensure we don't break unmodified installations.
Does this change affect the behavior of either the C or the Java implementations?
No.

Released in Release 1.12.2 / 2021-08-04 · sparklemotion/nokogiri


TF2 Efficientdet added

Function to delete the saved models that are accumulated over time.
Saving metric changed from loss to mAP. Exact number of images will be dispalyed.

This PR has become stale; merge conflicts would be prohibitive at this point.


the account '' is missing token

I did everything as I should have but get the following error directly at the start:
2024-01-18T03:27:39.682127461Z time="18-01-2024 03:27:39" level=fatal msg="the account '' is missing token"
My config:
# Config generated by using /etc/crowdsec/bouncers/crowdsec-cloudflare-bouncer.yaml as base
crowdsec_lapi_url: http://crowdsec:8080/
crowdsec_lapi_key: XYZ
crowdsec_update_frequency: 10s
include_scenarios_containing: [] # ignore IPs banned for triggering scenarios not containing either of provided word
exclude_scenarios_containing: [] # ignore IPs banned for triggering scenarios containing either of provided word
only_include_decisions_from: [] # only include IPs banned due to decisions orginating from provided sources. eg value ["cscli", "crowdsec"]
cloudflare_config:
    accounts:
        - id: 123<EMAIL_ADDRESS>Account
          zones:
            - zone_id: 123 #xyz.de
              actions:
                - managed_challenge
            - zone_id: 123 #xyz.top
              actions:
                - managed_challenge
          token: xyz
          ip_list_prefix: crowdsec
          default_action: managed_challenge
          total_ip_list_capacity: 9990 # only this many latest IP decisions would be kept
    update_frequency: 10s
daemon: false
log_mode: stdout
log_dir: /var/log/
log_level: info
log_max_size: 0
log_max_age: 0
log_max_backups: 0
compress_logs: null
prometheus:
    enabled: true
    listen_addr: <IP_ADDRESS>
    listen_port: "2112"
key_path: ""
cert_path: ""
ca_cert_path: ""

What is wrong?

Just a docker path fail...


[Event Request] Codeunit 80 "Sales-Post": Need to affect "Sales Line Disc. Account"

Hello.
In Codeunit 80, function FillInvoicePostingBuffer, we need to overwrite the GenPostingSetup."Sales Line Disc. Account" field with our own selected value, for posting.
…
IF SalesSetup."Discount Posting" IN
[SalesSetup."Discount Posting"::"Line Discounts",SalesSetup."Discount Posting"::"All Discounts"]
THEN BEGIN
CalcLineDiscountPosting(SalesHeader,SalesLine,SalesLineACY,InvoicePostBuffer);
IF (InvoicePostBuffer.Amount <> 0) OR (InvoicePostBuffer."Amount (ACY)" <> 0) THEN BEGIN
OnFillInvoicePostingBufferOnSetAccount_u(SalesLine,GenPostingSetup); // New event
InvoicePostBuffer.SetAccount(
GenPostingSetup.GetSalesLineDiscAccount,TotalVAT,TotalVATACY,TotalAmount,TotalAmountACY);
InvoicePostBuffer.UpdateVATBase(TotalVATBase,TotalVATBaseACY);
UpdateInvoicePostBuffer(TempInvoicePostBuffer,InvoicePostBuffer,TRUE);
END;
END;
…
LOCAL [IntegrationEvent] OnFillInvoicePostingBufferOnSetAccount_u(SalesLine : Record "Sales Line";VAR GenPostingSetup : Record "General Posting Setup")

Why you need to do this? Can you simple update general posting setup data for you accounting regulation?

We have an additional table with discount types, and based on the entry we find in this table we grab the Account No. we want to use for the discount type being posted. So, we are not just putting in one specific Account No,, but a variable one based on the discount type.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Change Protector class member detector to private

Hello, I found not logic rule.
https://github.com/magento/marketplace-eqp/blob/develop/MEQP2/Sniffs/PHP/ProtectedClassMemberSniff.php
Comment in line 13 says "Detects possible usage of 'private' scope modifiers.", and whole class detecting 'protected'.
To fast fix: change return [T_PROTECTED]; to return [T_PRIVATE]; in line 32. And protected $warningCode = 'FoundProtected'; to protected $warningCode = 'FoundPrivate';
Same on Russian:
Похоже что произошла ошибка, PHPCS с стилем MEQP2 говорит мне что protected переменные не желательны. А судя по комменту в коде детектора, должно искать private, а не protected.
Fixed file:
ProtectedClassMemberSniff.php.txt

@Leonede , thank you for reporting. We will fix it in the next commit.

Fixed typo in comment 810c1491232b9e19dfe388da3279700c4e81edc4.

I expecting it will be another fix..
So, now  in Magento 2, protected methods and variables are not consumable? Which one I need to use then?
Is private OK so?

@Leonede, yes, all nop-public methods and properties should be private. For Magento 2 extension development we recommend using object composition over class inheritance. It makes your extension easier to maintain when class changes occur and update when new features need to be implemented. Follow here for the detailed explanation.

@Leonede , it means if a protected  method is which is existing  at extended class,does not  override by  my own class  same rename method?


Check deadlineDate is in the league trade settings object

Should fix KeyError with deadlineDate field #10

Codecov Report

Merging #11 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage   94.39%   94.42%   +0.03%
==========================================
  Files           8        8
  Lines         321      323       +2
==========================================
+ Hits          303      305       +2
  Misses         18       18

Impacted Files
Coverage Δ

ff_espn_api/settings.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


zos update didn't asked for init function neither it can be called later with send-tx

To my understanding update command should provide a way to call init method. Also I was unable to call init method later with send-tx. Is it by design?

It's not possible to call the initializer more than once, that includes when you update. The initializer has already been called and can't be called again. You can only add new functions you want to call if you want to set some sort of new deployment state. However I think, the modifier (I might be wrong) can still be used just once.

Yeah. You are right. I am closing the issue.

You are right @crazyrabbitLTC. The best thing to do here would be to check if an initializer function has been called before, and don't show the initializer functions it that's the case.


Update documentation for v3

Coverage increased (+0.008%) to 96.448% when pulling 622d3f0e78c91fdda864afa3d4b7f128c503d323 on v3docs into c04e9666bf34ab2a4d565be43729bf4e65a5e3e0 on dev.


Adding new repository for indexing: atracsys_fusion_tracker

Please Add This Package to be indexed in the rosdistro.
Kinetic
The source is here:
https://github.com/cerberos79/atracsys_fusionTrack.git
Checks

[ ] All packages have a declared license in the package.xml
[ ] This repository has a LICENSE file
[ ] This package is expected to build on the submitted rosdistro

@cerberos79, it looks like there are merge conflicts. Would you mind resolving them?

We are preparing for the final kinetic sync. All releases should be prepared by April 20th and we will have a long soak time until April 26th. Please make sure to test from the testing repository to make sure that there's no regressions after this is released. You can get more info from this thread on ROS Discourse
Because of the pending EOL status of Kinetic I might suggest that you target a newer platform. The kinetic rosdistro will be frozen after the above sync.

Hi @cerberos79. There are still merge conflicts that will prevent testing and merging this change, but I spotted another issue.
The release: portion of this change is referring to the content repository, when it should refer to a "release" repository. You'll notice that other entries in this file use a separate repository for this purpose.
Please take a look at this page, which describes how to release your package: http://wiki.ros.org/bloom/Tutorials/FirstTimeRelease
For now, I recommend dropping the release: part and merge only the source: part, until you've properly prepared the package as described on the wiki.

Given where we are with the final Kinetic sync, and the fact that this still has conflicts, I'm going to close this out.  If you'd like this package to be indexed, I'll suggest opening a PR against Melodic or Noetic, which still have a few years of support left.


Loading big report fails because protobuf's reader by default forbids big messages

Describe the bug
Trying to load a big report file fails (shown on the CI) and the UI is just stuck empty.
To Reproduce
Steps to reproduce the behavior:

Download this large report we ran with the CI
extract the ZIP
Open the Convenient Manager
Attempt to load the report from the UI
See error on the CLI:

[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: InvalidProtocolBufferException: While parsing a protocol message, the input ended unexpectedly
in the middle of a field. This could either mean that the input
has been truncated or that an embedded message misreported its
own length.

Note that the buffer containing the message has 328221025 bytes, but
CodedBufferReader was allowed to parse only 67108864 bytes.

#0      CodedBufferReader._throwTruncatedMessageError (package:protobuf/src/protobuf/coded_buffer_reader.dart:34:7)
#1      CodedBufferReader.readMessage (package:protobuf/src/protobuf/coded_buffer_reader.dart:110:7)
#2      _mergeFromCodedBufferReader (package:protobuf/src/protobuf/coded_buffer.dart:186:15)
#3      GeneratedMessage.mergeFromBuffer (package:protobuf/src/protobuf/generated_message.dart:192:5)
#4      new ReportCollection.fromBuffer (package:convenient_test_common_dart/src/protobuf/convenient_test.pb.dart:38:17)
#5      MiscDartService.readReportFromFile (package:convenient_test_manager_dart/services/misc_dart_service.dart:53:47)
<asynchronous suspension>
#6      MiscFlutterService.pickFileAndReadReport (package:convenient_test_manager/services/misc_flutter_service.dart:35:5)
<asynchronous suspension>

Expected behavior
It works, I suppose. Maybe by reading the file in a stream or in chunks rather than it failing ...
Screenshots

If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Linux Manjaro (Arch)

Note that the buffer containing the message has 328221025 bytes, but
CodedBufferReader was allowed to parse only 67108864 bytes.

Hmm... Looks like protobuf's reader does not like that big size.
https://pub.dev/documentation/protobuf/latest/protobuf/CodedBufferReader-class.html Maybe we just need to do a simple change: e.g. CodedBufferReader(sizeLimit:<PHONE_NUMBER>).

Got a PR to fix it.
Though loading large files like that is pretty slow: like multi-minutes on modern hardware,  where the screen just sits there and CPU usage is pretty high (I had to decrease the log-level as well or the debug print would simply be too much ...)

Though loading large files like that is pretty slow: like multi-minutes on modern hardware, where the screen just sits there and CPU usage is pretty high (I had to decrease the log-level as well or the debug print would simply be too much ...)

Hmm... Maybe we can use another isolate to load it, for example.