Please share configuration for docker-compose

Hi
Thanks for this docker-image!
I'm trying to use it to run tests inside docker-compose like this:
version: '3'

services:
  testproject:
    build: .
    command: python3 testproject/manage.py test cc
    volumes:
      - .:/code
    ports:
      - "8000:8000"
    depends_on:
      - zcashd

  zcashd:
    image: messari/zcash-core:2.0.3
    command: -printtoconsole -regtest=1 -rpcuser=root -rpcpassword=toor -server=1 -rest -rpcbind=<IP_ADDRESS> -rpcallowip=<IP_ADDRESS>
    ports:
      - "18232:18232"
    expose:
      - "18232"

And I'm always getting 403 Forbidden error when trying to execute some api call from testproject to zcashd.
Do you have a working example, could you please share it.
I only have such problem with zcashd. Bitcoin, litecoin, dash - all of them are working fine.

If I'm executing api calls using zcash-cli inside the container - everything works fine

Possibly you're not passing the RPC user/pass correctly? I'm not sure.
For zcash, we're successfully using the HTTP interface on port 8232.
For Bitcoin we're using https://www.npmjs.com/package/bitcoin-core for the RPC connection which is working correctly.

When inside the zcash container I connect to localhost - everything works
but when I'm connecting by hostname - I have 403 error
So looks like -rpcbind=<IP_ADDRESS> -rpcallowip=<IP_ADDRESS> doesn't allow any connections, only to localhost
Can you please share what parameters are you using in your setup.

-rpcallowip=<IP_ADDRESS>/0 works
Cheers


Alter icon for secret inline checks

First without the secret trait, second with
Once again, sorry github user @Check

Great, now people are going to think the system is responsible for the monk module bug.

has the monk module bug been fixed or going to go away anytime soon?

The issue with the icon change (and I agree after discussing it) is that it doesn't look clickable. I'm not sure how well this will pan out, but what if you tint the button in the same color as the blind roll chat message?

It's a tad subtle for my liking, but that's an issue with Foundry's choice of colour too.

Perhaps if you also tinted the border a tad in that direction? Like a very desaturated dark purple (barely perceptable as purple).
I think subtle is fine though. Its not too important a player knows a roll will be secret. Especially now that secret rolls when clicked show in the dialog preset the roll mode (assuming they even have the dialog show up).

Well, it's certainly barely perceptible even when enlarged in that image. But this'll do; I'll commit the changes

That looks pretty decent. That'll do!


Mobile tooltips

closes #1115
closes #1116
to test:

open it on your phone, or on desktop chrome with device toolbar and device set to an iphone or something. (firefox's touch simulation is broken.)
tapping a key should type it.
dragging through the keyboard should scroll.
pressing and holding a key, and then dragging before 1000 ms passes, should cancel the dragging.
pressing and holding a key, and then waiting for 1000 ms, should show the tooltip.
pressing and holding a key, and then waiting for 1000 ms, and then dragging, should show different tooltips as you drag.
pressing and holding a key, and possibly waiting or dragging, and then releasing, should type the last key touched (as long as it didn't scroll).

right now the threshold for showing the tooltip is "1000 ms", which in reality is absolutely not 1000 ms but whatever
unfortunately, to make this complex event handling work, i had to introduce preact

Nice!

I'm looking forward to rewriting the frontend in React, might make it much cleaner than it is now.


Tidy up CSS media queries

Some odd behaviour with font size at breakpoints needs investigating and possibly rebuilding from scratch.

This should include working towards improving readability - guidelines suggest no more than 85 characters per line.


Expose Action Context arguments and message id

What
Where/Who

JIRA Issue
SDK-69

Background
Implementation
Testing steps
Is this change backwards-compatible?

Consider updating unit tests if needed with new public methods


test

Motivation and Context
copilot:all

Description

Contribution Checklist

[ ] The code builds clean without any errors or warnings
[ ] The PR follows the Contribution Guidelines and the pre-submission formatting script raises no violations
[ ] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

@huangyingting can you rename the PR to its intent?


Suggestion: Add additional wiki markup options

Suggestion: It would be great if the following wiki markups were supported

A markup for images, e.g. [[File:image.png]]
A markup for block quotes
A markup for html content not supported by the wiki, eg.

For images and multimedia, see issue #488

For sections (blockquotes, alignments), Issue #489

Rob, the other two issues should address your problems. If so, would you mind closing this issue?

Thank you JP.


[cluster-test] disable debug log in LBT test

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/diem/diem/tree/main/developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

/canary

:boom: Tests timed-out

/land

:broken_heart: Test Failed - ci-test-success

/land

/cancel

/land

/cancel

/land


MH-13691, Configure max open files

This patch configures the maximum allowed number of open files for the
Opencast process since the default can be a bit low, especially on
larger workers where we have seen “too many open files” errors show up
multiple times.
Since Opencast usually runs on dedicated machines, this setting should
not harm anyone, but only prevent errors in these edge cases.

Since Opencast usually runs on dedicated machines…

What errors can occur if this is not the case?

What we have seen happening multiple times now is a Java error saying something along the lines of “Cannot open file”, sometimes also when trying to launch a sub-process (e.g. FFmpeg) which results in either the node staying up but no further processing or in the node going randomly up and down. In both cases, Opencast did not recover on its own and in the second case it caused problems for the whole cluster since Opencast was trying to start jobs on those nodes only to notice that they went down but since the came immediately up again… well… goto dispatching;

I mean, in theory, the idea for these kinds of limits is that a single process can not use up all your resources and by doing so block other important processes. If you run a mail server and a web server on a single machine you don't want your web server to take down your mail server under heavy load…
This type of problem shouldn't usually be a problem in the case of Opencast deployments.


[YUNIKORN-2008] Hide the column if all of its values are 'n/a' in the…

… table.
What is this PR for?
remove anything that resolves to "n/a" from the list as that is just noise.
What type of PR is it?

[x] - Improvement

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/YUNIKORN-2008/

How should this be tested?
Screenshots (if appropriate)
before-

after-
Display the column only if the content in all of the cells is not 'n/a'.
The following picture adds the rank name 'rank01' to db.json to demonstrate that it works correctly, which isn't included in this commit.

Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

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

Comparison is base (d1a26e7) 66.66% compared to head (4b8fb4c) 66.66%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #148   +/-   ##
=======================================
  Coverage   66.66%   66.66%
=======================================
  Files           1        1
  Lines          30       30
=======================================
  Hits           20       20
  Misses          7        7
  Partials        3        3

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

Thanks to @stu01509 for the suggestion, I have updated the code accordingly.


EnableVersionUpgrade Update Policy Not Recognized

cfn-lint version: (cfn-lint --version) 0.25.5
Description of issue:
cfn-lint does not understand AWS::Elasticsearch::Domain's new UpdatePolicy of EnableVersionUpgrade. This key accepts a Boolean value.

If EnableVersionUpgrade is set to true, you can update the ElasticsearchVersion property of the AWS::Elasticsearch::Domain resource, and CloudFormation will update that property without interruption. When EnableVersionUpgrade is set to false, or not specified, updating the ElasticsearchVersion property results in CloudFormation replacing the entire AWS::Elasticsearch::Domain resource.

I have a patch for this ready to go, and the PR should be created in a couple of minutes.

Thanks @chrisoverzero


Change the names of the groups

Turn "leader" into "BELL"
Turn "teacher" into "EETC"
Turn "parent" into "VCPA"
Leave staff alone

Note: "EETC" stands for "Early Educators for Thriving Children"

Per Yang, this should be closed


Extend type test expression to accept instance of Type in addition to type name

I.e. now this works:
print(v is MyObject);
But this - not.
Type t = MyObject;
print(v is t);
v.runtimeType == MyObject is not enough, I'd like to check also subclasses of MyObject.

Marking this as a dupe of the newer bug (#27680) since that one has a little more discussion.


Automate GUI build on release

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Why '/' before filename ?

Hello,
my image doesn't display on firefox because my
{!! $cat_tampon->image_categorie->url('medium')!!}
send
img/img_categorie/1/medium/\PostaMetal.jpg
The problem is the \ before PostaMetal. Is it possible to remove it ?

You're going to have to give me some info to work with here:
What does your Stapler config look like?
What's the name of the file (on disk) that you uploaded (that caused this issue)?
What OS are you using?


Restructuring analysis project

Closes #120 , related to #155

Fitting background and foreground distributions on matching segments at the same time so that normalizers only need to be fit once
Reorganizing and restructuring project to be more clear and modular
Visualization app issues

[x] Event inspector is not rendering changes to data sources
[ ] Glitch plot legend isn't showing up when using legend_group instead of legend_field as the argument to the circle plot. The issue with using legend_field as noted here is that Bokeh treats all the legend items as a single item, so you can't click to hide them individually - they're either all on or all off.
[x] x/y range limits for the efficiency vs. FAR plot aren't updating when we switch the x-axis to SNR

Visualization app additions

[x] How to pass arguments? Do something like this but inside of a typeo-fied main function?
[ ] Toggle in row with norm select to turn vetoes on/off that affects all plots
[x] Toggle in row with FAR/SNR select widget that affects whether efficiencies are computed for <= the range value, or just within the corresponding bin (should be reflected in the legend labels as well).
[ ] Additional event inspection window for Q-scan or spectrogram or something
[ ] Additional event inspection window for saliency map of gradient wrt. spectrogram

Library unit tests

[x] Cluster distribution load Tb
[x] Cluster distribution from_file with ifos
[x] integrate w/o kernel_length argument
[x] inject_waveform with sample_rate != 1 and with idx relative to center of waveform

@EthanMarx feel free to try to tackle some of the vizapp TODOs if you want to get familiar with this framework. To run the server, connect to the LDG cluster via SSH with port forwarding enabled (ssh -L 5006:localhost:5006...) and then cd to the vizapp directory. Then just poetry install and poetry run bokeh serve vizapp, then the app should be available at localhost:5006 on your local machine.

Event inspector has been fixed, although the plot needs some formatting / style changes.
Once the tests have been written, let's merge this in and then we can open the remaining tasks as issues.

@EthanMarx give the vizapp another look before merge, made a few changes:

Organized things into tabs, with the first tab for summary plots (right now just the perf summary, but leaving room for more if we want to add them later) and the second for more detailed analysis (background, event inspector, etc.)
Moved some legends outside plots to avoid obscuring data. For the distribution plot, removed the legend entirely and instead rely on y-axis labels/coloring to distinguish the meaning of the glyphs.
Changed the coloring on the distribution plot so that it's isn't confused with the green/orange used to differentiate the interferometers in other plots.
Updated the title on the distribution plot so that it can contain all the relevant info
Made the box select tool the default click-and-drag tool on the distribution plot (instead of box zoom)

Let me know when glitch insertion is fixed and I'll give this a look over.

@EthanMarx should be good to go


Close file is not needed if it's using dry_run

close only should be called when file was opened, and it happens only if dry_run is not set

Good catch - is this causing any issues?

@paulsamuels really it didn't cause me any issue, but I saw it different than obj-c approach (which opens and closes both files), so I replicate it for swift too.
About your comment, I think that maybe it's more complicated, but if you like, I'll change it for this:
 ruby
if options.use_swift
  if dry_run then
    SwiftConstantWriter.new(self, swift_out, options.templates_dir).write
  else
    File.open("#{options.output_path}.swift", 'w') do |file|
      SwiftConstantWriter.new(self, file, options.templates_dir).write
    end
  end
else
...

(this is your proposal with no-dry-run support, to print to stdout).
On this case, I think that should be good to do in a similar way for obj-c, so... said that, what do you prefer? 😸

Follow up! :D


Streaming: TPC-H Q11

We don't hava TPC-H Q11 in java. So leave it empty for now.

Checked that it is running on CI.


Upgrade to Ember 1.10

:boom: :boom: :boom:
Before this is merged and deployed:
https://github.com/Tahi-project/tahi-plos-authors-card needs the ember-1-10 branch merged and deployed as well.
:boom: :boom: :boom:

This PR removes the style guide template. Is that intentional, or perhaps a bad merge? Does this branch still have a style guide?

Ooops. I didn't want to check that in. The styleguide template is causing HTMLBars compilation errors right now.

:+1: Looking good, merge when green.

not ok 113 Firefox 34.0 - integration/serializer: extractMany puts normalizes things via their 'type' attribute
    ---
        actual: >
            null
        message: >
            Died on test #1 test@http://localhost:7357/assets/test-support.js:1693:5
            @http://localhost:7357/assets/tahi.js:58034:3
            requireModule@http://localhost:7357/assets/vendor.js:79:16
            TestLoader.prototype.require@http://localhost:7357/assets/test-loader.js:29:9
            TestLoader.prototype.loadModules@http://localhost:7357/assets/test-loader.js:21:13
            TestLoader.load@http://localhost:7357/assets/test-loader.js:36:7
            @http://localhost:7357/assets/test-support.js:5294:5
            : No model was found for 'invitation'
        Log: >
    ...

I merged the ember-1-10 branch into master in Tahi-project/tahi-plos-authors-card. I guess this means should update the package.json entry for this card to use master instead of the SHA it currently has? /c @tonywok @nummi

Yup


chore: update peerDep typescript

Description
Updates peerDependency : typescript (and all the others too).
Related Issue
Fixes # 1567
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Other (security config, docs update, etc)

Checklist before merging

[x] Unit, Journey, E2E Tests, docs, adr added or updated as needed
[x] Contributor Guide Steps followed

Due to the scale of changes required to update from the v8 to the v9 line of eslint (i.e. the FlatFile config overhaul) -- and how "ungracefully" it ties into our current build infrastructure -- we're going to close this PR out & start again over here... without eslint.


chrome-trace-event

What is the current behavior?
chrome-trace-event is a dependency
If the current behavior is a bug, please provide the steps to reproduce.
This commit added this dependency (PR: https://github.com/webpack/webpack/pull/6322)
What is the expected behavior?
chrome-trace-event package.json points (poorly in that npm cannot parse it) to this repo which is a fork of node-trace-event.  I am do not believe this is a good choice because that repo has no issue tracker and webpack is the only thing that depends on it (per npm's dependents).
Should webpack should move it into the namespace and maintain it or possibly into the repo itself (only 175 LOC)? All other dependencies appear to be highly used by other libraries as well, so this stands out. If there is a strong reason to keep it as it is, @samccone can you please open the issue tracker and possibly add a collaborator in case this project needs to make changes?
cc @TheLarkInn @samccone

@samccone looks like all done and we can close issue

Feel free to feedback. Thanks!


Refactor overload and throttle checks to allow for overrides.

Refactor overload checks to allow for overrides.

Playground build 30.

@rabbah rebase your branch?

@rabbah rebase your branch?

also playground 31 failed many tests?

Waiting for 32 now.  Is it a feature that Steve's comments/replies are in email only but not in the issue tracker?  (This is by email)

----- Original message -----From: Stephen Fink<EMAIL_ADDRESS>openwhisk/openwhisk<EMAIL_ADDRESS>Perry S Cheng/Cambridge/IBM@IBMUSSubject: Re: [openwhisk] Refactor overload and throttle checks to allow for overrides. (#40)Date: Wed, Mar 2, 2016 5:30 PM
also playground 31 failed many tests?
—Reply to this email directly or view it on GitHub.

Can you explain how the override is activated?  Do you mean just code cleanup for method override or user-specific limits?

Thanks. Override as in method override to facilitate an admin API to set rates per subject. As for the missing comments, that's my fault with slow page refresh I deleted them.


add workflow for author approved label

This intends to facilitate AutoMerge reading this label and bypassing some checks if the author approves. The intended use is:

AutoMerge would have guidelines that can be bypassed if the author approves. Without approval, these fail and the automerge comment instructs the author (well: whoever registered the version/package) to comment with "approved".
If the author does so, that triggers this workflow, which adds the "author-approved" label to the PR
The AutoMerge workflow would be updated to retrigger when this label is applied. It would run through the same logic, but this time notice the label, and use it to bypass those checks.

Currently this workflow is useless as AutoMerge does not have such conditional checks, but I wanted to put a PR to try it out.
Note that https://github.com/JuliaRegistries/RegistryCI.jl/pull/536 shows how easy it is to use label information within automerge itself, which I think makes this a viable route.
For the sake of testing, I will add text to trigger the regex:

Created by: @ericphanson

approved

Ah, I can't test this here, since it's an issue_comment triggered workflow:

Note: This event will only trigger a workflow run if the workflow file is on the default branch.

I suppose if we merge this, I can test it in a separate PR that could presumably update the workflow and it would get the changes from the branch instead of from main?

I suppose if we merge this, I can test it in a separate PR that could presumably update the workflow and it would get the changes from the branch instead of from main?

I think, for issue comments and PR comments, it always picks up the workflow file from the default branch :(
We could make a fork of General and do some testing there?

I wonder if we could come up with a different name other than "author"? In the AutoMerge codebase, we always use "author" to refer to the actual GitHub PR author, so @JuliaRegistrator, @jlbuild, etc.
So it might be a little confusing to also use the same term "author" for the human that triggered Registrator.
Maybe "registration-trigger-user` or something like that?

For the label? I think we should make sure it's understandable by the user, so they can know that their approval was picked up correctly. So I think it shouldn't be too obscure. What about package-author-approved?

Ok, I've tested it here, and updated this PR.
Mismatch:

Match:

Note the times on the Julia part vary from 1-2s up to 15-20s, I'm not really sure why. However that code only runs when a comment is posted from a non-bot user that includes "approved", so hopefully it doesn't need to run too much.

Can we also exclude the github-actions[bot] user?

I have excluded all bot users

For the label? I think we should make sure it's understandable by the user, so they can know that their approval was picked up correctly. So I think it shouldn't be too obscure. What about package-author-approved?

Yeah let's go with that.

I had already renamed the label to package-author-approved. Just now, I changed the approval string to "merge approved", and realized in fact it is not case-sensitive, as contains is not. I updated the comment with a reference.
I think this is good to go, and am writing a PR to RegistryCI to make use of this in the sequential version skipping check (probably to the delight of like 2 people who like skipping versions). We can also use it for other things down the line.


Merge pull request #1 from django-helpdesk/master

update

Codecov Report

Merging #578 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #578   +/-   ##
=======================================
  Coverage   63.61%   63.61%
=======================================
  Files          36       36
  Lines        3422     3422
  Branches      526      526
=======================================
  Hits         2177     2177
  Misses       1100     1100
  Partials      145      145

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 230b9d7...b051c4a. Read the comment docs.

Did you mean to send an empty pull request? I'm going to close it since no changes here, please resubmit with your code changes!


[fastlane] Version bump

Remove testmunk integration (#6102)
Don’t hang on git clone command when user credentials are missing (#6068)
Fix an issue with multi team ids and latest_test_flight_build_number (#6076)
Add project_directory option to carthage action (#6072)
add ability to pass in specific file name for plist file (#6035)
Update docs for resign.rb (#5994)
Add SKIP_SLOW_FASTLANE_WARNING env var (#6048)
Change pod lib lint platform support (#6049)
Update fastlane code base to use UI.input instead of ask
Only set ipa path for iOS builds (non Mac) (#6036)
xcode_select improve instructions on how to use action when failing (#6019)
Include the full path name in file not found error message (#5979, #5962)
Add paging support for plugins to list all available plugins (#5977)
Add parameter for output path for available plugins (#5970)
Refactor fastlane runner to make it easy to access from docs (#5951)
Improve docs (#5947, #5950, #5937, #6046)
Update internal dependencies (#6104, #6063)

The platform detection is used to get a feeling of how many people use fastlane with iOS or with Android projects. The data is being sent to refresher. You can opt out by setting the FASTLANE_OPT_OUT_USAGE environment variable.

👍


Add tests

Codecov Report
Base: 53.55% // Head: 65.43% // Increases project coverage by +11.88% :tada:

Coverage data is based on head (989456b) compared to base (b1eee05).
Patch coverage: 70.31% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main      #54       +/-   ##
===========================================
+ Coverage   53.55%   65.43%   +11.88%
===========================================
  Files           3        7        +4
  Lines         338      813      +475
===========================================
+ Hits          181      532      +351
- Misses        157      281      +124

Impacted Files
Coverage Δ

..._points_and_surfaces/_surface_annotation_widget.py
16.56% <0.00%> (-0.86%)
:arrow_down:

napari_process_points_and_surfaces/_vedo.py
64.58% <64.58%> (ø)

...ari_process_points_and_surfaces/_quantification.py
70.80% <66.15%> (-6.54%)
:arrow_down:

napari_process_points_and_surfaces/__init__.py
82.12% <76.42%> (ø)

...rocess_points_and_surfaces/_tests/test_function.py
100.00% <100.00%> (ø)

..._process_points_and_surfaces/_tests/test_open3d.py
100.00% <100.00%> (ø)

napari_process_points_and_surfaces/_utils.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Does nskinz still work?

Want to know if people are still using this or moved on to other alternatives if available.

Still working and you don't need any other alternatives

It never works for me, just crashes when I press insert

It never works for me, just crashes when I press insert

you must be gay then -_-

Still working and you don't need any other alternatives

Is this kind of stuff banable?

Still working and you don't need any other alternatives

Is this kind of stuff banable?


⚠ ClamAV has degraded performance

In a9c0c5c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in cf3b877.


Drop It fails on returning empty set

Challenge Drop it has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function dropElements(arr, func) {
  // Drop them elements.

  var emp = [];
  //loop through elements seeking the true element, breaking when found. Shifting the elements when not found.
  var end = arr.length;
  if (end === arr.length){
    console.log(true);
  }
  else
    console.log(false);
//Change this line to for(var i = 0 ; i < end; i++) and it passes returning empty array
//as is fails to return the empty array
  for(var i = 0; i < arr.length; i++){
    if(func(arr[0])){
        break;
    }
    else{
        arr.shift();

    }
  }
  console.log(arr);
  return arr;
}

dropElements([1, 2, 3, 4], function(n) {return n > 5; });

@chadg1980 thanks for the issue but if you get stuck or have questions with a challenge in the future, please first ask questions to the Help Room. Hint: when you run your code for that test, you get back [3, 4]; why do you think it stops prematurely? There is a small bug in your code. Happy coding!

My code returns empty array in my local environment. And the "Help Room" should be broken into sections, because it is pure chaos and I don't go in there anymore.


Removed K8s ConfigMap that was not in use

I'm sorry, but the code you provided is not enough to determine if it requires optimization or not. It seems to be an error message or a console output, but without context or additional code, it's difficult to provide a meaningful analysis.
Could you please provide more information about the code you are working with, or share the relevant code snippets? This will help me provide a more accurate analysis and suggest any optimizations that may be necessary.

I'm sorry, but the code you provided is not enough to determine if it requires optimization or not. It seems to be an error message or a console output, but without context or additional code, it's difficult to provide a meaningful analysis.
Could you please provide more information about the code you are working with, or share the relevant code snippets? This will help me to better understand the issue and provide more accurate suggestions for optimization.

I'm sorry, but the code you provided is not enough to determine if it requires optimization or not. It seems to be an error message or a console output, but without context or additional code, it's difficult to provide a meaningful analysis.
Could you please provide more information about the code you are working with, or share the relevant code snippets? This will help me provide a more accurate analysis and suggest any optimizations that may be necessary.

It is difficult to provide a comprehensive analysis without seeing the actual code. However, based on the provided information, it seems that the code change is a simple removal of a Kubernetes ConfigMap that was not being used.
In terms of optimization, this change does not necessarily improve the performance of the code, but it does improve the maintainability and clarity of the codebase. By removing unused code, the codebase becomes easier to understand and navigate, which can save time and effort in the long run. Additionally, removing unused resources can also free up resources in the cluster, which can improve performance indirectly.

It is difficult to provide a comprehensive analysis without seeing the actual code. However, based on the provided information, it seems that the developer has removed a Kubernetes ConfigMap that was not being used in the codebase.
This is a good practice as it helps to reduce clutter in the codebase and improves maintainability. Unused code or resources can also impact the performance of the application, so removing them can potentially improve performance.
However, it is important to note that simply removing unused code or resources may not always result in significant performance improvements. It is important to identify and optimize the critical parts of the codebase

It is difficult to provide a comprehensive analysis without seeing the actual code. However, based on the provided information, it seems that the code change is a simple removal of a Kubernetes ConfigMap that was not being used.
In terms of optimization, removing unused resources such as ConfigMaps can help improve the performance and efficiency of the application. This is because unused resources can consume unnecessary memory and processing power, which can slow down the application and increase its resource usage.
Additionally, removing unused resources can also help simplify the codebase and reduce the overall complexity of the application. This can make it easier to maintain and

It is difficult to provide a detailed analysis without seeing the actual code. However, based on the description provided, it seems that the developer has removed a Kubernetes ConfigMap that was not being used in the codebase.
This is a good practice as it helps to reduce clutter in the codebase and improves the overall maintainability of the application. Removing unused code also helps to reduce the size of the application, which can improve performance.
If there were any references to the ConfigMap in the codebase, those references would need to be updated or removed as well. This ensures that the application continues to function correctly

It is difficult to provide a comprehensive analysis without seeing the actual code. However, based on the provided information, it seems that the code change is a simple removal of a Kubernetes ConfigMap that was not being used.
In terms of optimization, this change does not necessarily improve the performance of the code, but it does improve the maintainability and clarity of the codebase. By removing unused code, the codebase becomes easier to understand and navigate, which can save time and effort in the long run. Additionally, removing unused resources such as ConfigMaps can help reduce the overall resource usage of the application,

It is difficult to provide a comprehensive analysis without seeing the actual code. However, based on the provided information, it seems that the code change is a simple removal of a Kubernetes ConfigMap that was not being used.
In terms of optimization, removing unused resources such as ConfigMaps can help improve the performance and efficiency of the application. This is because unused resources can consume unnecessary memory and processing power, which can slow down the application and increase its resource usage.
Additionally, removing unused resources can also help simplify the codebase and reduce the overall complexity of the application. This can make it easier to maintain and

The code change is a removal of a Kubernetes ConfigMap that was not in use. The ConfigMap was defining some key-value pairs for Prometheus annotations. The removal of this ConfigMap will not have any significant impact on the performance of the application.
However, there are some other files that have been removed from the Kustomization file. The removed files are server-hpa.yml and ui-hpa.yml. These files were defining the Horizontal Pod Autoscaler for the server and UI deployments respectively. The removal of these files may impact the scalability of the application.
If the application experiences a sudden increase in traffic, the Kubernetes cluster may not be able to scale the server and UI deployments automatically. This can result in degraded performance or even downtime. Therefore, it is recommended to review the application's traffic patterns and resource utilization and adjust the HPA configuration accordingly.

The code change is a removal of a Kubernetes ConfigMap that was not in use. The ConfigMap was defining some key-value pairs for Prometheus annotations. The removal of this ConfigMap will not have any significant impact on the performance of the application.
However, there are some other files that have been removed from the Kustomization file. The removed files are server-hpa.yml and ui-hpa.yml. These files were defining the Horizontal Pod Autoscaler for the server and UI deployments respectively. The removal of these files may impact the scalability of the application.
If the application experiences a sudden increase in traffic, the Kubernetes cluster may not be able to scale the server and UI deployments automatically. This can result in degraded performance or even downtime. Therefore, it is recommended to review the application's traffic patterns and resource utilization and adjust the HPA configuration accordingly.


boxxy: init at 0.2.7

Description of changes
https://github.com/queer/boxxy

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

boxxy


Fixed bugs with Brain_Data.filter(). More flexibly accepts keyword ar…

…guments too.

Coverage decreased (-0.1%) to 53.819% when pulling 906fe95bc26731e4260012ee757e6fead1153848 on ejolly:master into 026f9274fc41206f4f7ef9ef4b5542e9e40d1735 on ljchang:master.


Merge editor: preserve view state

Testing #150389
Similar to https://github.com/microsoft/vscode/issues/150791 where BaseTextEditor provides some helper methods for storing editor view state, the merge editor should associate view state like the diff editor does: e.g. selection, folding regions etc. so that they can restore after window reload.
One thing that is special about the diff editor: when you open a diff editor for the first time, we automatically reveal the first diff and ignore any previous view state. This helps focussing on what has actually changed. However, when a diff editor was opened before and is just made active again, we do restore the view state.

To verify:

open merge editor
select something in input1, show the find widget in input2, etc
reload the window or close/reopen the editor
ensure that the view state is restored

I can still reproduce this, reopening. I am following steps from the above comment. Here's a gif:

Sorry forgot to mention that it needs todays insiders.

Still doesn't work... Need to investigate., sorry for the fuzz

Sorry, my verification steps are bad. The find widget isn't part of any editor view state, selecting and folding etc is. So
To verify:

open merge editor
select something in input1, select something in input2, fold something input3
reload the window or close/reopen the editor
ensure that the view state is restored


fix: [#7532] Publishing page loses information on reloading the bot

Description
This PR prevents a bot's publishing history from being lost when reloading the page or switching between bots.
Now, the jobId isn't removed from publish storage when the bot is published.
Task Item
Fixes #7532
Screenshots
This screenshot shows the last publish information after reloading the page.

Coverage decreased (-0.008%) to 54.539% when pulling 5c4153334be9f895f34c3bc7da6a57556ab7e66f on southworks/fix/publishing-page-loses-information into 57627632f8d0ce1662a0df7f9d037a2683f7387c on main.

Should we cleanup previous publishing records after the ongoing publishing job failed/succeed?


Fix wrong values of CLASS, NAMESPACE, #803 issue

cC @serg-deep
Can you review it?

It worked. Thanks


Fix urlesc import url in Dockerfile

Point to the correct repo location.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Thank you!  Merged as acbedf6 (master) and 0066070 (v0.16.docs).


Langium documents don't get removed after the containing directory is renamed

After renaming a directory, all DSL files contained inside are listed twice in services.shared.workspace.LangiumDocuments. This can affect various downstream features, like linking, type computation, or validation.
Langium version: 2.0.2
Package name: langium
Steps To Reproduce

In a Langium project, observe the contents of services.shared.workspace.LangiumDocuments. In the repo linked below, it gets logged in the output panel.
Create a folder.
Create a DSL file inside (extension .hello for the repo linked below).
Rename the folder.

Link to code example: https://github.com/lars-reimann/langium-cst-range

The current behavior
Before renaming the directory, the document is included (correct):

After renaming (third array), the new document is shown (correct), but the old one is not deleted (wrong):

The expected behavior
Only the new document should be included.

@lars-reimann Thanks for the report. I believe this is part of a larger issue where we don't actually listen to a few of the workspace related LSP notifications, mainly:

workspace/didChangeWorkspaceFolders
workspace/willRenameFiles
workspace/didRenameFiles
workspace/willCreateFiles
workspace/didCreateFiles
workspace/willDeleteFiles
workspace/didDeleteFiles

Some of these are not interesting for the default behavior of Langium, but we should definitely start handling the didChangeWorkspaceFolders, didRenameFiles, didCreateFiles and didDeleteFiles notifications.

I had a closer look at this. We already get notifications of most changes through workspace.didChangeWatchedFiles notifications. So the only case where we need additional notifications are when folders are renamed, as those are not covered by the glob pattern **/*.hello. We could do this by explicitly watching all folders in the language server, but what I don't like about it is that we have a distribution of responsibilities between language client and language server code. It would be better to find a solution where watched file system events are specified fully on the client or server side.

see also didClose in https://github.com/eclipse-langium/langium/discussions/1281

I experimented with adding / removing workspace folders with Langium documents and did not see any issues. So it seems we don't need to handle didChangeWorkspaceFolders for now.
A service for the file operations is introduced in #1286, but as mentioned in that PR, those notifications should not be used to trigger DocumentBuilder updates. They are rather meant to enhance the user experience when working with the IDE, e.g. by automatically changing some text content when you rename a file (we could make use of that for langium file renaming).
The remaining question is how to fix the issue reported here. My current understanding is that we should use the file system watcher for that by adding a suitable glob pattern and handling it.

While reviewing and testing your changes of #1286 I could produce a corrupt state of `langiumDocuments by renaming a document's parent folder and then opening the document, see screenshots.
Thus listening to didChangeWorkspaceFolders is necessary I guess.

Thus listening to didChangeWorkspaceFolders is necessary I guess.

workspace/didChangeWorkspaceFolders is for the case when you actually change the workspace by adding a completely new workspace folder or remove one from the workspace. Note that workspace folders are not folders inside of a workspace but the directories that constitute a multi-root workspace.
But I agree. The language server should listen to it.

The remaining question is how to fix the issue reported here. My current understanding is that we should use the file system watcher for that by adding a suitable glob pattern and handling it.

This seems not to be possible in a adequate way, see https://github.com/microsoft/vscode/issues/60813
An explicit remark on that was deleted with https://github.com/microsoft/vscode/pull/139881/files#diff-0a75aed19c118603eb96332bc0b9c2d7867f4182346d16d18b7fc31b6ceeb321L10951-L10952 beginning of last year.
I could make notifications on folder name changes work with a glob pattern like ('**/{*,*.<extension>}, which however kills the file extension based filtering, and in case of a folder name change we would have to look for documents with the corresponding folder path prefix on our own... 😕

Has anyone developed a workaround for this issue?


ActiveRecord::ConnectionAdapters::SQLite3Adapter (FrozenError)

Hi everyone,
We have recently updated our application to Ruby 3.0.2 and Rails 7.0.0.alpha2 so I wanted to try console1984. I've enabled it in development environment but I am getting ActiveRecord::ConnectionAdapters::PostgreSQLAdapter (FrozenError).
To make sure it is not caused by our application I created new vanila rails app (ruby 3.0.2 and rails 7.0.0.alpha2) with console1984 but problem stayed the same but with SQLite database.
Here is the stacktrace from test app:
[consoletest#main]→ rails c

You have access to production data here. That's a big deal. As part of our promise to keep customer data safe and private, we audit the commands you type here. Let's get started!

Commands:

* decrypt!: enter unprotected mode with access to encrypted information

Unnamed, why are you using this console today?
asdfsadf
/Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/connection_adapters/abstract_adapter.rb:79:in `quoted_table_names': can't modify frozen #<Class:ActiveRecord::ConnectionAdapters::SQLite3Adapter>: ActiveRecord::ConnectionAdapters::SQLite3Adapter (FrozenError)
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/connection_adapters/sqlite3/quoting.rb:16:in `quote_table_name'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/connection_adapters/sqlite3_adapter.rb:386:in `table_structure'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/connection_adapters/abstract/schema_statements.rb:116:in `columns'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/connection_adapters/schema_cache.rb:117:in `block in columns'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/connection_adapters/schema_cache.rb:116:in `fetch'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/connection_adapters/schema_cache.rb:116:in `columns'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/connection_adapters/schema_cache.rb:125:in `block in columns_hash'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/connection_adapters/schema_cache.rb:124:in `fetch'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/connection_adapters/schema_cache.rb:124:in `columns_hash'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/model_schema.rb:568:in `load_schema!'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/attributes.rb:264:in `load_schema!'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/encryption/encryptable_record.rb:124:in `load_schema!'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/model_schema.rb:554:in `block in load_schema'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/model_schema.rb:551:in `synchronize'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/model_schema.rb:551:in `load_schema'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/model_schema.rb:417:in `attribute_types'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/model_schema.rb:443:in `type_for_attribute'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/type_caster/map.rb:16:in `type_for_attribute'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/arel/table.rb:107:in `type_for_attribute'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/table_metadata.rb:18:in `type'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/predicate_builder.rb:59:in `build'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/predicate_builder.rb:54:in `[]'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/predicate_builder.rb:126:in `block in expand_from_hash'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/predicate_builder.rb:79:in `each'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/predicate_builder.rb:79:in `flat_map'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/predicate_builder.rb:79:in `expand_from_hash'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/predicate_builder.rb:25:in `build_from_hash'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/query_methods.rb:1277:in `build_where_clause'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/query_methods.rb:720:in `where!'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/query_methods.rb:715:in `where'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation/finder_methods.rb:81:in `find_by'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/relation.rb:182:in `find_or_create_by!'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activerecord-7.0.0.alpha2/lib/active_record/querying.rb:22:in `find_or_create_by!'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/console1984-0.1.15/lib/console1984/sessions_logger/database.rb:9:in `block in start_session'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_silence.rb:18:in `block in silence'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_thread_safe_level.rb:44:in `log_at'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_silence.rb:18:in `silence'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger.rb:64:in `block (3 levels) in broadcast'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_silence.rb:18:in `block in silence'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_thread_safe_level.rb:44:in `log_at'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_silence.rb:18:in `silence'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger.rb:62:in `block (2 levels) in broadcast'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/console1984-0.1.15/lib/console1984/sessions_logger/database.rb:56:in `block in silence_logging'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_silence.rb:18:in `block in silence'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_thread_safe_level.rb:44:in `log_at'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_silence.rb:18:in `silence'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger.rb:64:in `block (3 levels) in broadcast'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_silence.rb:18:in `block in silence'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_thread_safe_level.rb:44:in `log_at'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger_silence.rb:18:in `silence'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.0.alpha2/lib/active_support/logger.rb:62:in `block (2 levels) in broadcast'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/console1984-0.1.15/lib/console1984/sessions_logger/database.rb:55:in `silence_logging'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/console1984-0.1.15/lib/console1984/sessions_logger/database.rb:8:in `start_session'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/console1984-0.1.15/lib/console1984/supervisor.rb:57:in `start_session'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/console1984-0.1.15/lib/console1984/supervisor.rb:25:in `start'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/console1984-0.1.15/lib/console1984/engine.rb:24:in `block in <class:Engine>'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/railtie.rb:250:in `block in run_console_blocks'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/railtie.rb:275:in `each'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/railtie.rb:275:in `each_registered_block'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/railtie.rb:250:in `run_console_blocks'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/application.rb:522:in `block in run_console_blocks'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/engine/railties.rb:15:in `each'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/engine/railties.rb:15:in `each'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/application.rb:522:in `run_console_blocks'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/engine.rb:449:in `load_console'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/commands/console/console_command.rb:35:in `initialize'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/commands/console/console_command.rb:19:in `new'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/commands/console/console_command.rb:19:in `start'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/commands/console/console_command.rb:102:in `perform'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/thor-1.1.0/lib/thor/command.rb:27:in `run'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/thor-1.1.0/lib/thor/invocation.rb:127:in `invoke_command'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/thor-1.1.0/lib/thor.rb:392:in `dispatch'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/command/base.rb:87:in `perform'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/command.rb:48:in `invoke'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.0.alpha2/lib/rails/commands.rb:18:in `<main>'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	from /Users/edariedl/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	from bin/rails:4:in `<main>'

Everything works fine without console1984. Is there something I might have done wrong or it is possible it might be some weird bug?

Hi @edariedl I'll look into this one shortly, thanks for the report!

I just released version 0.1.18 with a fix for this. Thanks again for the report @edariedl!


patch🚑:  add eslint and fix linting errors

to close https://github.com/intel/web-ai-showcase/issues/18

Kindly ping @ibelem 😄

LGTM


Optional and autocomplete support

Summary
Fixes optional and default arguments
Adds basic autocomplete support
Checklist

[x] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[ ] This PR fixes an issue.
[x] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

Stale


Installation documents, including how to setup GitHub token as a Secret for the Branch Planner

User Story
As a new user of the Branch Planner,
I'd like to have clear and concise installation documentation,
so that I can set up the branch planner, including setting up a GitHub token as a Secret, with ease.
Acceptance Criteria

[ ] Installation documentation is easy to understand and follow.
[ ] Instructions on how to set up a GitHub token as a Secret are provided.
[ ] Clear examples and use-case scenarios are explained in the documentation.
[ ] A troubleshooting section is included in the documentation to address potential issues during setup.

@chanwit : Can this issue be closed or there are some missing pieces still, can you add notes about them?

@yitsushi let me know what do you thin about the ACs.

that's a scope change I think. Previously it was only about install docs and secrets. My question should be worded like "is the getting started guide satisfies this issue or not?"
Previously "troubleshooting section" was not even mentioned.

I think the extra entries are more like the next line called "User guide" in #749


Test Files

Is there any test file available?

Is there any test file available?

they are not available yet. I'm still working on it

Is there any test file available?

they are not available yet. I'm still working on it

I also want master, please build the binary file, please, I tried but failed, thank you.


Fix for One-Time refresh token not being removed from PersistedGrants store

The TokenResponseGenerator passes an uninitialized RefreshTokenHandle to the DefaultTokenService when requesting a refresh token update.
To solve this issue, the RefreshTokenHandle is being stored on the ValidatedRequest object.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Thanks! - I already did that due to another problem.


make: use the SA name "ksa-google-cas-issuer" instead of "default"

This PR makes sure that the SA required in the make deploy step is the same as the Kubernetes service account we create in the readme.
Signed-off-by: Maël Valais<EMAIL_ADDRESS>

/lgtm


no detections for

hello, thank you for your work!
I have tried to train EagerMOT with center point and mmdetection, but I got this error. Could you give some help?
Parsing NuScenes v1.0-mini ...
======
Loading NuScenes tables for version v1.0-mini...
23 category,
8 attribute,
4 visibility,
911 instance,
12 sensor,
120 calibrated_sensor,
31206 ego_pose,
8 log,
10 scene,
404 sample,
31206 sample_data,
18538 sample_annotation,
4 map,
Done loading in 0.360 seconds.
======
Reverse indexing ...
Done reverse indexing in 0.1 seconds.
======
Done parsing
Starting sequence: scene-0061
Processing frame ca9a282c9e77460f8360f564131a8af5
Parsing /home/zxl/wyd_EagerMOT/EagerMOT-open_main/centerpoint/mini_train/detections1.json
Traceback (most recent call last):
  File "run_tracking.py", line 176, in <module>
    run_on_nuscenes()
  File "run_tracking.py", line 151, in run_on_nuscenes
    mot_dataset, NUSCENES_BEST_PARAMS, target_sequences, sequences_to_exclude)
  File "run_tracking.py", line 131, in perform_tracking_with_params
    sequences_to_exclude=sequences_to_exclude)
  File "run_tracking.py", line 40, in perform_tracking_full
    run_info = sequence.perform_tracking_for_eval(params)
  File "/home/zxl/wyd_EagerMOT/EagerMOT-open_main/dataset_classes/mot_sequence.py", line 73, in perform_tracking_for_eval
    predicted_instances = frame.perform_tracking(params, run_info)
  File "/home/zxl/wyd_EagerMOT/EagerMOT-open_main/dataset_classes/mot_frame.py", line 166, in perform_tracking
    self.fuse_instances_and_save(params, run_info, load=False, save=False)
  File "/home/zxl/wyd_EagerMOT/EagerMOT-open_main/dataset_classes/mot_frame.py", line 66, in fuse_instances_and_save
    self.bboxes_3d, self.dets_2d_multicam, params["fusion_iou_threshold"])
  File "/home/zxl/wyd_EagerMOT/EagerMOT-open_main/dataset_classes/mot_frame.py", line 247, in dets_2d_multicam
    self.load_segmentations_2d_if_needed()
  File "/home/zxl/wyd_EagerMOT/EagerMOT-open_main/dataset_classes/mot_frame.py", line 224, in load_segmentations_2d_if_needed
    dets_2d_multicam = self.sequence.get_segmentations_for_frame(self.name)
  File "/home/zxl/wyd_EagerMOT/EagerMOT-open_main/dataset_classes/mot_sequence.py", line 93, in get_segmentations_for_frame
    self.dets_2d_multicam_per_frame = self.load_detections_2d()
  File "/home/zxl/wyd_EagerMOT/EagerMOT-open_main/dataset_classes/nuscenes/sequence.py", line 82, in load_detections_2d
    frames_cam_tokens_detections = loading.load_detections_2d_nuscenes(self.seg_source, self.token)
  File "/home/zxl/wyd_EagerMOT/EagerMOT-open_main/inputs/loading.py", line 100, in load_detections_2d_nuscenes
    return detections_2d.load_detections_2d_mmdetection_nuscenes(seq_name)
  File "/home/zxl/wyd_EagerMOT/EagerMOT-open_main/inputs/detections_2d.py", line 101, in load_detections_2d_mmdetection_nuscenes
    all_dets = utils.load_json_for_sequence(utils.DETECTIONS_MMDETECTION_CASCADE_NUIMAGES_NUSCENES, seq_name)
  File "/home/zxl/wyd_EagerMOT/EagerMOT-open_main/inputs/utils.py", line 151, in load_json_for_sequence
    raise NotADirectoryError(f"No detections for {target_seq_name}")
NotADirectoryError: No detections for cc8c0bf57f984915a77078b10eb33198

Did you use the provided detections or generate yourself? The script expects detections for all key frames. Check what this sequence is and if it is correctly generated


Update README.md

Updating the Sightly intro blog post URLS for parts 1 & 2. Fixing the links.

Thanks a lot!


Fixes fade in grid items and some other modal issues

Fade now correctly works for PlexGridtem component
Updated PlexGridItem to initiate Fade after the image has fully loaded (so Fade is visible to user)
Fixes issue where rowSize calculation would be wrong, now rounding the number to make it match Grid calc.
Update calculation for estimating inline modal height so it doesn't display as the wrong size initially while images load in
Cleaned up some variable naming in the modal utilities to make it easier to understand

I closed this in favor of the changes I pushed here:
https://github.com/chrisbenincasa/tunarr/pull/233


Add an about.html page with content

It would be nice to have an about.html page that lists info such as:

version of scoring engine
documenting each check that is active (maybe we should create an additional field on the "Check" class with a short description? Or maybe store this info in each "check source code".

Decided not to include documentation on how checks are run, maybe we can circle back and eventually have that be defined in each check, and dynamically displayed.
Added in https://github.com/pwnbus/scoring_engine/pull/246


Closes #17 add a config validator helper function

This covers paths validation.  Will add autos validation once autos branches merge into dev.
Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Update to all relevant roxygen headers and examples.
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[x] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue so that it closes after successful merging.
[x] Address all merge conflicts and resolve appropriately.
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

@mstackhouse Snapshot tests pass for 4.2 and release, but fail for 4.0.  I'm inclined to merge, since the message is what I expect.
There is one other fail due to library, but this is fixed already in another branch.


Allow custom fields for users to populate for account information

Some websites may require other fields adding to account information, e.g. birthday, full name, etc.
Add a mechanism for customs fields which can be populated by users:

Custom field name
Custom validation regex regex
Custom message to display in invalid input

Feature creep. Maybe worth revisiting in the future.


Official dark theme - credits

Hi @UtkarshVerma,
I'm the principal Frontender of Ecosia and stumbled upon your work a few weeks ago.
First of all, let me thank you for the work done to embrace the dark side! Realizing that other developers in the wild use Ecosia and are willing to put time into contributing to it, feels me with contentment.
We have been trying to find time to internally develop a dark theme for months, without much success. A multitude of things have repeatedly taken priority over that.
However, I have now this week available for that and would truly like to change direction and make some steps forwards:

Porting and adapting your work into our SASS source
Release an update to automatically apply the dark theme to users that have expressed preference for it
Update FAQ page
Adding credits to your work, for inspiration and support

About last point, I think it'd be nice to link your work in our aforementioned FAQ page, unless you have issues with it. What URL the credits link should point to, between this repository or userstyle.org page?
Many thanks again and feel free to reply directly here for visibility.

Hi @LostCrew,
I don't have any issues with you using my work. In fact, I feel honored to be able to contribute to a good eco-friendly search engine that ecosia is!
Addressing your question about credits link, I'd choose the repository over the userstyle.org page.

@LostCrew That would be great if Ecosia could have a dark theme.
@UtkarshVerma work is great but there is one thing I think it cannot do that (maybe) an official dark theme could: when you use ecosia as your default home page (on Chrome), there is no URL so no style applied (defaults to white background).

@madmath03 I don't use Chrome so I didn't face this issue. Will test this out on Chrome.

@LostCrew @UtkarshVerma , It would be nice if Ecosia has a dark mode, I would like to contribute to make this happen


Sample form for sanskrit proofreading

@Andhrabharati   @sanskritisampada
Take a look at the sample documents below.  Is the format adequate for your upcoming proofreading of
the Sanskrit verses in Indische Sprüche ?
When the format is agreeable, one or more documents will be generated containing all the 2000+ verses
in volume 1 of the book.

slp1 form
@sanskritisampada   I presumed you would want to proofread using slp1 spellings, so that's what is in this sample
; ---------------------------------------------
; 1 : page 1.1
    aMSo 'pi duzwadizwAnAM parezAM syAdvinASakft .
    vAlaleSo 'pi vyAGrARAM patsyAjjIvitahAnaye ..
; ---------------------------------------------
; 2 : page 1.1
    akaRWasya kaRWe kaTaM puzpamAlA vinA nAsikAyAH kaTaM DUpaganDaH .
    akarRasya karRe kaTaM gItanftyamapAdasya pAde kaTaM me praRAmaH ..
; ---------------------------------------------
; 3 : page 1.1
    akaruRatvamakAraRavigrahaH paraDane parayoziti ca spfhA .
    svajanabanDujanezvasahizRutA prakftisidDamidaM hi durAtmanAm ..
; ---------------------------------------------
; 4 : page 1.1
    akarmaRAM vE BUtAnAM vfttiH syAnnahi kA ca na .
    tadevABiprapadyeta na vihanyAtkadA ca na ..
; ---------------------------------------------
; 5 : page 1.2
    akarmaSIlaM ca mahASanaM ca lokadvizwaM bahumAyaM nfSaMsam .
    adeSakAlajYamanizwavezametAngfhe na prativAsayeta ..
; ---------------------------------------------
; 6 : page 1.2
    akasmAtprakriyA nf2RAmakasmAccApakarzaRam .
    SuBASuBe mahattvaM ca prakartuM budDilAGavam ..
; ---------------------------------------------
; 7 : page 1.2
    akasmAdiha yaH kaScidarTaM prApnoti pUruzaH .
    taM haWeneti manyante sa hi yatno na kasyacit ..
; ---------------------------------------------
; 8 : page 1.2
    akasmAdeva kupyanti prasIdantyanimittataH .
    SIlametadasADUnAmaBraM pAriplavaM yaTA ..
; ---------------------------------------------
; 9 : page 1.2
    akasmAdeva tanvaNgI jahAsa yadiyaM punaH .
    nUnaM prasUnabARo 'syAM svArAjyamaDitizWati ..
; ---------------------------------------------
; 10 : page 1.2
    akasmAdeva yaH kopAdaBIkzRaM bahu BAzate .
    tasmAdudvijate lokaH sasPuliNgAdivAnalAt ..
; ---------------------------------------------
; 11 : page 1.2
    akasmAddvezwi yo BaktamAjanmaparisevitam .
    na vyaYjane ruciryasya tyAjyo nfpa ivAturaH ..
; ---------------------------------------------
; 12 : page 1.3
+   <s>akasmAdyuvatI vfdDaM</s> s. Spr. <s>nAkasmAdyuvatI vfdDaM</s>.
    akARqakopino BarturanyAsaktoSca yozitaH .
    praSAntiScetasaH kartuM brahmaRApi na Sakyate ..
; ---------------------------------------------
; 13 : page 1.3
    akARqapAtajAtAnAmArdrARAM marmaBedinAm .
    gAQaSokaprahAraRAmacintOva mahOzaDam ..
; ---------------------------------------------
; 14 : page 1.3
    akAmasya kriyA kAciddfSyate neha karhicit .
    yadyadDi kurute kiMcittattatkAmasya cezwitam ..
; ---------------------------------------------
; 15 : page 1.3
    akAmAM kAmayAnasya SarIramupatapyate .
    icCatIM kAmayAnasya prItirBavati SoBanA ..

Devanagari form
@Andhrabharati ,  no doubt you want to proofread Devanagari .
; ---------------------------------------------
; 1 : page 1.1
    अंशो ऽपि दुष्टदिष्टानां परेषां स्याद्विनाशकृत् ।
    वाललेशो ऽपि व्याघ्राणां पत्स्याज्जीवितहानये ॥
; ---------------------------------------------
; 2 : page 1.1
    अकण्ठस्य कण्ठे कथं पुष्पमाला विना नासिकायाः कथं धूपगन्धः ।
    अकर्णस्य कर्णे कथं गीतनृत्यमपादस्य पादे कथं मे प्रणामः ॥
; ---------------------------------------------
; 3 : page 1.1
    अकरुणत्वमकारणविग्रहः परधने परयोषिति च स्पृहा ।
    स्वजनबन्धुजनेष्वसहिष्णुता प्रकृतिसिद्धमिदं हि दुरात्मनाम् ॥
; ---------------------------------------------
; 4 : page 1.1
    अकर्मणां वै भूतानां वृत्तिः स्यान्नहि का च न ।
    तदेवाभिप्रपद्येत न विहन्यात्कदा च न ॥
; ---------------------------------------------
; 5 : page 1.2
    अकर्मशीलं च महाशनं च लोकद्विष्टं बहुमायं नृशंसम् ।
    अदेशकालज्ञमनिष्टवेषमेतान्गृहे न प्रतिवासयेत ॥
; ---------------------------------------------
; 6 : page 1.2
    अकस्मात्प्रक्रिया नृ२णामकस्माच्चापकर्षणम् ।
    शुभाशुभे महत्त्वं च प्रकर्तुं बुद्धिलाघवम् ॥
; ---------------------------------------------
; 7 : page 1.2
    अकस्मादिह यः कश्चिदर्थं प्राप्नोति पूरुषः ।
    तं हठेनेति मन्यन्ते स हि यत्नो न कस्यचित् ॥
; ---------------------------------------------
; 8 : page 1.2
    अकस्मादेव कुप्यन्ति प्रसीदन्त्यनिमित्ततः ।
    शीलमेतदसाधूनामभ्रं पारिप्लवं यथा ॥
; ---------------------------------------------
; 9 : page 1.2
    अकस्मादेव तन्वङ्गी जहास यदियं पुनः ।
    नूनं प्रसूनबाणो ऽस्यां स्वाराज्यमधितिष्ठति ॥
; ---------------------------------------------
; 10 : page 1.2
    अकस्मादेव यः कोपादभीक्ष्णं बहु भाषते ।
    तस्मादुद्विजते लोकः सस्फुलिङ्गादिवानलात् ॥
; ---------------------------------------------
; 11 : page 1.2
    अकस्माद्द्वेष्टि यो भक्तमाजन्मपरिसेवितम् ।
    न व्यञ्जने रुचिर्यस्य त्याज्यो नृप इवातुरः ॥
; ---------------------------------------------
; 12 : page 1.3
+   <s>अकस्माद्युवती वृद्धं</s> s. Spr. <s>नाकस्माद्युवती वृद्धं</s>.
    अकाण्डकोपिनो भर्तुरन्यासक्तोश्च योषितः ।
    प्रशान्तिश्चेतसः कर्तुं ब्रह्मणापि न शक्यते ॥
; ---------------------------------------------
; 13 : page 1.3
    अकाण्डपातजातानामार्द्राणां मर्मभेदिनाम् ।
    गाढशोकप्रहारणामचिन्तौव महौषधम् ॥
; ---------------------------------------------
; 14 : page 1.3
    अकामस्य क्रिया काचिद्दृश्यते नेह कर्हिचित् ।
    यद्यद्धि कुरुते किंचित्तत्तत्कामस्य चेष्टितम् ॥
; ---------------------------------------------
; 15 : page 1.3
    अकामां कामयानस्य शरीरमुपतप्यते ।
    इच्छतीं कामयानस्य प्रीतिर्भवति शोभना ॥

PDF
Just as a reminder,  A pdf of volume 1 (2nd edition) was provided by @gasyoun at https://github.com/sanskrit-lexicon/PWG/issues/37#issuecomment-898956536.   (ref).
I think all you will need is the text file of verse (as in the sample) and the pdf.

go ahead to make the full text.

I would like to propose that @sanskritisampada can start off with her proofing as a 1st phase.
(Meanwhile, I will be on my AE proofing.)
I am presuming a week to 10 days time is needed at the max. to "read" all these verses.
Then I can do a 2nd round proofing on her work.
And finally @funderburkjim can have a glance into it, for integration with other portions of the text.
how does this proposal sound?

two other possibilities are

doing full text parallelly, and compare both versions to get a final text
splitiing portions for individual working and joing the portions at the end

the parallel working and comparision is the better option out of these two, but I am presently engaged with AE (of course, a small break can be given to it).
splitting the portions and joing  the pieces makes it quicker, but has a minus point that only one proofing round took place on the whole.

which plan out of the three variants would get majority votes?

I like the 'parallel' approach.  Have two independently generated corrections.
Then I could generate comparisons of the two
and we'll iterate over the differences.
@Andhrabharati  It's fine for you to work on AE as needed.  There is a lot of work to be done on the
non-verse portions,  so there is no current feeling of time pressure regarding the proofing.

OK, then let's go with my first proposal.
Will wait till Sampada finishes her round.

there is no current feeling of time pressure regarding the proofing.

of course, there no time-pressure for any of the works here!!

I prefer the 2nd proposal  --- each of you do it independently.  i.e., you don't need to wait for Sampada.

OK, then let it be so.

where to put the files?
Here's a suggestion of where to put the files for proofing.

Jim makes a repository funderburkjim/boesp-san-ab  (for Andhrabharati)

permission settings for Andhrabharati to push.

Jim puts the initial version of the verses file into the repository
Andhrabharati clones the repository.
Andhrabharati modifies his local copy of file

each day, after modifying local copy,  the local copy can be synced to Github.

When Andhrabharati done,  Jim can pull the revised file

Similarly a repository funderburkjim/boesp-san-sampada  for Sampada's work.
This approach would have the advantages

No interference between the proofing work and other work being done in boesp-prep

This will make life easier by avoiding occasional tricky syncing obstacles

Github tracking of versions, so no work can be lost
Availability of Github issues, history, and other amenities.
Similar process can be used with the verses from volumes 2 and 3 when they are available

Should we give this a try?

each day, after modifying local copy, the local copy can be synced to Github.

Sorry, I don't like to do it this way; will be posting the full work once done with it.

will be posting the full work

As you wish.

@Andhrabharati   Have prepared repository https://github.com/funderburkjim/boesp-prep-ab for you.
The full devanagari verses are in file boesp-1_deva.txt .
Also invited you as 'a collaborator', which should give you full permissions on this repository.
Do you know how to clone this repository to your local computer?
If you use GitBash, then the cloning command is
git clone https://github.com/funderburkjim/boesp-prep-ab.git

And when you want to commit your changes and push to Github
git add .
git commit -m "Brief description of reason for commit"
git push

@sanskritisampada   Have prepared repository https://github.com/funderburkjim/boesp-prep-sam for you.
The verses from volume 1 are in file boesp-1_slp1.txt .
Also invited you as 'a collaborator', which should give you full permissions on this repository.
To clone this repository to your local computer with GitBash
git clone https://github.com/funderburkjim/boesp-prep-sam.git

And when you want to commit your changes and push to Github
git add .
git commit -m "Brief description of reason for commit"
git push

Since you are comfortable with Gitbash, suggest you commit your changes and push to Github after
most sessions (Vary the commit message to indicate the verses proofed in the session).

Comments in proofing file
You may want to make a comment occasionally in the proofing file.  If so, I request these comments
be inserted as lines beginning with the semicolon character ';'.
Of course, if you have more elaborate comments, you can open an Issue in the repository.
scan error
I don't think you need to be completely meticulous about noting cases where you suspect the printed text
to be in error.  If you do want to record such print errors, then make a comment  starting with  the
phrase 'scan error'
e.g.
; scan error  : kulpa -> kalpa

Do you know how to clone this repository to your local computer?

Just like to remind you that I am already using github platform, with Dhaval and CSL.
I do understand these processes well now.

Of course, if you have more elaborate comments, you can open an Issue in the repository.

Posted several issues, as I looked into the file-
https://github.com/funderburkjim/boesp-prep-ab/issues/5#issue-988696637
https://github.com/funderburkjim/boesp-prep-ab/issues/4#issue-988685959
https://github.com/funderburkjim/boesp-prep-ab/issues/3#issue-988577200
https://github.com/funderburkjim/boesp-prep-ab/issues/2#issue-988562185
https://github.com/funderburkjim/boesp-prep-ab/issues/1#issue-988559285

Thanks Jim
This slp sample looks perfect for proofreading.
How do I proceed?
Sampada
On Sat, 4 Sep 2021, 05:57 Andhrabharati, @.***> wrote:

which plan out of the three variants would get majority votes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/funderburkjim/boesp-prep/issues/8#issuecomment-912902162,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACTKJX7W3F6C2NOFB6HOO7DUAGKJHANCNFSM5DMZUSNA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@Andhrabharati

I do understand these processes well now.

Got it!

@sanskritisampada
You proof read the verses, and make corrections as needed.
You probably will want to compare to the PDF  (see link above for getting pdf).
Also see instructions above.
You'll be doing all work in https://github.com/funderburkjim/boesp-prep-sam, as described above.
For further discussion, post in issues in boesp-prep-sam repository.

Think this issue can be closed.


change performBlock ->performBlockAndWait in func deleteEventsWithIDs

I found crashs located in the function "- (void)deleteEventsWithIDs:(NSArray*)entityIDs".
Because the api "- (void)performBlock:(void (^)())block" is asynchronously.Maybe you fecth the entitys from the database when deleting , you will fetch the data is deleting.So i suggest use the api "- (void)performBlockAndWait:(void (^)())block" instand of "- (void)performBlock:(void (^)())block".

Hi @YYDD, thank you for your Pull Request. We dropped ongoing development for version 3 of this SDK. Please consider looking into version 4, which is completely rewritten in Swift.


Calling scene 'Good Night' screwing configuration up

I've been redonig my configuration over and over again. Now I think I've found the tripping point: Whenever I call the  scene 'Good night', shortly after everyhting goes south. Sometimes a device disappears and doesn't come back, sometimes other things happen. This time everyhting seems to be mixed up. My garage door sudeenly hat a temperature instead of a state, my termp. sensor was suddenly a lamp, the lamp something else... I'll avoid defining a scene now and see whether that helps.

This sounds like very odd behavior. When was the last time you rebooted your homebridge instance?
What platform do you have homebride running on?

Oh, I'm rebooting it 'constantly' (every day at least once) right now because I'm fiddling with homeassistant and I get 'too many open files' after some restarts.
It's on an old mac mini running  Ubuntu 16.04.1 LTS.
I'm not even sure if homebridge is to blame, might also be an apple problem (!?)

I was running on a core 2 Mac mini for a while (won't support Sierra so used ubuntu), after switching to a pi3 as a gateway I haven't had any random/weird problems. I've tested with a 2011 iMac and everything runs fine as well. It seems like the older minis are a bit unstable. At least the core 2s IMO.

Am 30.01.2017 um 17:36 schrieb Erik<EMAIL_ADDRESS>I was running on a core 2 Mac mini for a while (won't support Sierra so used ubuntu), after switching to a pi3 as a gateway I haven't had any random/weird problems. I've tested with a 2011 iMac and everything runs fine as well. It seems like the older minis are a bit unstable. At least the core 2s IMO.

Huh, I had it running on a pi2 for a long time as well (but with a much simpler config) … but that pi2 is outside, near the main gate and connected to the lan by powerline… and gets disconnected every now and then… so I wanted to have it on a ‚stable‘ computer ^^…
but I’ll see, I have alternatives. But I can’t really believe it’s really mini-related. I had a crash every 6 months or so, but otherwise it has been running without problems.

I switched to an other pc now. Just tried ‚good night‘ again - this time, all netatmo sensors (or the ones that get bridged from homeassistant at least, co2 doesn’t show up, no matter what I try) ‚jumped‘ from their respective rooms to ‚Standardraum‘ (guess it’s called standardroom in English).
Needless to say that ‚Good night‘ doesn’t change anything regarding the sensors, they’re basically ‚read only‘ anyway.
BTW the reason why I used them bridged instead of directly with homebridge is that I have stations from other people connected to my account and it seems you can’t hide them in homebridge, but you can in homeassistant.
regards
Patrick

Am 30.01.2017 um 17:36 schrieb Erik<EMAIL_ADDRESS>I was running on a core 2 Mac mini for a while (won't support Sierra so used ubuntu), after switching to a pi3 as a gateway I haven't had any random/weird problems. I've tested with a 2011 iMac and everything runs fine as well. It seems like the older minis are a bit unstable. At least the core 2s IMO.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/nfarina/homebridge/issues/1092#issuecomment-276112846, or mute the thread https://github.com/notifications/unsubscribe-auth/AME55E0tvTCMu27W-9WZN_Ukh1B1tuh_ks5rXhGTgaJpZM4Lwq2x.


reference lenght constraint

Hi, we are trying to align some 10x reads to a PacBio reference that consist of 4000 scaffolds. We would like to know if EMA has any constraint regarding the size of the reference as LongRanger has (1000 scaffolds). Thanks in advance.

Hi,
This should work; EMA uses BWA-MEM internally to do alignment, so as long as BWA is fine with it, EMA should theoretically be fine as well. Maybe another potential solution though would be to stitch the scaffolds together (with NN...Ns in between), align to that, then use the alignment loci to recover loci in the original scaffolds. But in any case I think running EMA on the original data would be a good first try, and hopefully that just works. Please let me know if you encounter any issues though.

Thanks a lot for your feedback! I'll let you know how things work out.
------------------------------------Luciano Calderón
Assistant ResearcherGrupo de genética y genómica de vid
Instituto de Biología Agrícola de Mendoza
CONICET-UNCUYO
El miércoles, 15 de mayo de 2019 09:54:43 ART, A. R. Shajii<EMAIL_ADDRESS>escribió:

Hi,
This should work; EMA uses BWA-MEM internally to do alignment, so as long as BWA is fine with it, EMA should theoretically be fine as well. Maybe another potential solution though would be to stitch the scaffolds together (with NN...Ns in between), align to that, then use the alignment loci to recover loci in the original scaffolds. But in any case I think running EMA on the original data would be a good first try, and hopefully that just works. Please let me know if you encounter any issues though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


native crash getting a segment iterator

I have a simple path created with a single cubic:
path.reset()
path.moveTo(pathPoints[0], pathPoints[1])
path.cubicTo(points[index * 2], points[index * 2 + 1],
points[index * 2], points[index * 2 + 1],
points[index * 2], points[index * 2 + 1])
I try to log the result with pathway like so:
for (segment: PathSegment in path.asAndroidPath()) {
println("*** segment = $segment")
}
The app crashes in on hasNext() during iteration.
I tried it with a close() command, and with one more cubic, but it always crashed in native code with this log:
2022-07-08 16:07:33.732 22397-22397/com.example.pathplayground A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x2 in tid 22397 (.pathplayground)

Specifically, debugger has it crashing when stepping over this call:
val typeValue = internalPathIteratorNext(internalPathIterator, pointsData)
where pointsData is a float array of 8 0.0's.

On which version of Android?

This was on an API 24 emulator (x86). Is there a problem running it on the emulator, or on another binary platform?
I wondered whether the problem wasn't a crash in that function per se, but rather a problem with the native side of pathway in general, either it's not building correctly on my system or is hitting some other incompatibility problem.

Hm, now running API 24 emulator (ARM) on a different machine (m1 mac vs x86 mac) and it doesn't crash. Not sure if this is something on my side (build time) or in the artifacts pathway has for download

Fixed in 0.4.0


Fix issues in API Docs

Purpose
Fixes #20024 #22402 #21725 #22307
This include following PRs
https://github.com/ballerina-platform/ballerina-lang/pull/22405
https://github.com/ballerina-platform/ballerina-lang/pull/22404
https://github.com/ballerina-platform/ballerina-lang/pull/22400
https://github.com/ballerina-platform/ballerina-lang/pull/22310
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #22594 into ballerina-1.2.x will not change coverage by %.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           ballerina-1.2.x   #22594   +/-   ##
================================================
  Coverage            14.59%   14.59%
================================================
  Files                   51       51
  Lines                 1411     1411
  Branches               219      219
================================================
  Hits                   206      206
  Misses                1189     1189
  Partials                16       16

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 15fe837...367588a. Read the comment docs.


Comments not deleted/undeleted on keyboard shortcuts

Expected Behavior

When I click on a block comment, and then press the "delete" key, it should delete the comment. Then pressing Ctrl+Z should undelete it.
When I click on a workspace comment, and then press the "delete" key, it should delete the comment. Then pressing Ctrl+Z should undelete it.

Actual Behavior

When I click on a block comment, and then press the "delete" key, it deletes both the block and the comment. When I press Ctrl+Z, it only undeletes the block, not the comment.

When I click on a workspace comment, and then press the "delete" key, it doesn't delete the comment, but instead deletes the last block I had focused on.

Operating System and Browser
Mac OS, Google Chrome

I believe this is directly related to https://github.com/google/blockly/issues/1960


Rails/MigrationClassName issue with rails ActiveStorage

#644 introduced MigrationClassName which doesn't play along with rails generated migrations for ActiveStorage
Issue with rails generated active storage migrations.
db/migrate/20210214101402_create_active_storage_tables.active_storage.rb:2:7: C: [Correctable] Rails/MigrationClassName: Replace with CreateActiveStorageTables.activeStorage that matches the file name.

where CreateActiveStorageTables.activeStorage is an invalid syntax. The cop should exclude activestorage migration files

RuboCop version
$ [bundle exec] rubocop -V
1.26.0 (using Parser <IP_ADDRESS>, rubocop-ast 1.16.0, running on ruby 3.1.1 arm64-darwin21)
  - rubocop-performance 1.13.3
  - rubocop-rails 2.14.0
  - rubocop-rspec 2.9.0

Probably #655 will solve it. I will wait for other issue feedback for a while before the bugfix releasing. Thank you.

Same here
Just for clarification, calling autocorrect of Rails/MigrationClassName cause my code:
# frozen_string_literal: true

# This migration comes from active_storage (originally<PHONE_NUMBER>3751)
class RemoveNotNullOnActiveStorageBlobsChecksum < ActiveRecord::Migration[6.0]
  def change
    change_column_null(:active_storage_blobs, :checksum, true)
  end
end

to become
# frozen_string_literal: true

# This migration comes from active_storage (originally<PHONE_NUMBER>3751)
class RemoveNotNullOnActiveStorageBlobsChecksum.activeStorage < ActiveRecord::Migration[6.0]
  def change
    change_column_null(:active_storage_blobs, :checksum, true)
  end
end

with raising errors on rubocop -A result:
rubocop -A db/migrate/20220210092016_remove_not_null_on_active_storage_blobs_checksum.active_storage.rb
Inspecting 1 file
E

Offenses:

db/migrate/20220210092016_remove_not_null_on_active_storage_blobs_checksum.active_storage.rb:4:7: C: [Corrected] Rails/MigrationClassName: Replace with RemoveNotNullOnActiveStorageBlobsChecksum.activeStorage that matches the file name.
class RemoveNotNullOnActiveStorageBlobsChecksum < ActiveRecord::Migration[6.0]
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
db/migrate/20220210092016_remove_not_null_on_active_storage_blobs_checksum.active_storage.rb:4:63: E: Lint/Syntax: unexpected token tLT
(Using Ruby 2.5 parser; configure using TargetRubyVersion parameter, under AllCops)
class RemoveNotNullOnActiveStorageBlobsChecksum.activeStorage < ActiveRecord::Migration[6.0]
                                                              ^
db/migrate/20220210092016_remove_not_null_on_active_storage_blobs_checksum.active_storage.rb:8:1: E: Lint/Syntax: unexpected token kEND
(Using Ruby 2.5 parser; configure using TargetRubyVersion parameter, under AllCops)
end
^^^

1 file inspected, 3 offenses detected, 1 offense corrected

RuboCop Rails 2.14.1 has been released.
https://github.com/rubocop/rubocop-rails/releases/tag/v2.14.1

I can confirm my problem is fixed in 2.14.1


Jackson module  ParameterNamesModule is not auto registered

Sample project compiled with -parameters flag:
https://github.com/mariuszs/spring-stream-consumer-sample

Error: MessageConversionException: Could not read JSON: Can not construct instance of com.example.streamconsumer.Foo: no suitable constructor found, can not deserialize from Object value (missing default constructor or creator, or perhaps need to add/enable type information?)

I'm not sure if I follow your issue or the sample project.
If you need an ObjectMapper with custom configuration, just provide one using @Bean, this should override the default one from spring-boot, and it will be the one picked by the framework.

Ok, you are right. I forget that ParameterNamesModule is not auto registered when it is on classpath. Thanks,

Hmm, it should be autoregistered... I have spring-boot-starter-web on classpath.
JacksonAutoConfiguration
@Configuration
@ConditionalOnJava(JavaVersion.EIGHT)
@ConditionalOnClass(ParameterNamesModule.class)
static class ParameterNamesModuleConfiguration {

	@Bean
	@ConditionalOnMissingBean(ParameterNamesModule.class)
	public ParameterNamesModule parameterNamesModule() {
		return new ParameterNamesModule(JsonCreator.Mode.DEFAULT);
	}

}

The module is being auto configured, you can check it by just putting a break point on the code. I don't know however why is it not working. I tested a simple rest boot application and you sample would fail on that example either. There may be other things you need to configure in jackson, I'm not sure, but the objectmapper being created is definitely being setup with the module.

Ok, this is jackson issue. Thank for your help
https://github.com/FasterXML/jackson-databind/issues/1631


slickRemove changes slick-active / slick-current

Version 1.7.1 installed and working, great slider.
Btw, playing with the remove/add slider options, I found a weird action when a slide is removed.
For example, a carousel with 3 images (1 photo for slide) and placed at the middle of my carousel (data-slick-index=1), when the user clicks to remove the first slide (data-slick-index=0), automatically slick push to the left the carousel and shows the next slide. The only exception is when we are at the last image (logically no more images to push to the left)
Searching at gitHub I didn’t found the same problem, so I worked over an old demo to test and share this issue:
http://jsfiddle.net/ytc7602p/
The expected action is to keep the actual image at screen, and not to change/move the slide when a image is removed via slickRemove.
*Happens for older versions (tested since 1.5 to 1.7)

I think this PR is supposed to address/fix this issue: https://github.com/kenwheeler/slick/pull/2783, however manually applying this is not fixing the issue for me.

Any thoughts @petergebala?

Try this hot fix $('.slider').slick('slickRemove',selector, true).slick("slickGoTo", $('.slider').slick("slickCurrentSlide") -1, true);
added .slick("slickGoTo", $('.slider').slick("slickCurrentSlide") -1, true);