MDA Shape Controls for Custom Pages with Test Engine Support Validation

Pull Request Template
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Checklist

[x] The code change is covered by unit tests. I have added tests that prove my fix is effective or that my feature works
[x] I have performed end-to-end test locally.
[x] New and existing unit tests pass locally with my changes
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I used clear names for everything
[x] I have performed a self-review of my own code

Since shape controls primarily have design properties and limited runtime properties, I validated only the OnSelect event with positive and negative test cases.

Added the Navigation for Arrows.


Universal different files converter using python script | Multiple Contributors | Add your own conversation function. | Follow the guideline

Objective
Developing a versatile Python script that serves as a universal file converter, capable of converting various file formats to different formats. This tool will provide users a seamless way to convert files such as documents, images, audio, and more, enabling compatibility across different applications and platforms.
Features

Support for Multiple Formats: Implement the ability to convert files between different formats, including but not limited to documents (e.g., PDF to DOCX), images (e.g., PNG to JPEG), audio (e.g., MP3 to WAV), etc.

User-Friendly Interface: Provide a clear and intuitive interface for users to select input and output formats, and specify file paths.

Batch Conversion: Allow users to convert multiple files at once for increased efficiency.

Example Usage
import file_converter

# for standalone function, but for the main script we will be using the argument from the shell.
# Convert a PDF document to a Word document
file_converter.convert('input.pdf', 'output.docx', input_format='pdf', output_format='docx')

# Convert a PNG image to a JPEG image
file_converter.convert('input.png', 'output.jpg', input_format='png', output_format='jpeg')

# Convert an MP3 audio file to a WAV audio file
file_converter.convert('input.mp3', 'output.wav', input_format='mp3', output_format='wav')

Difficulty: Beginner/Intermediate/Advanced
Tags: Python, File Conversion, Universal Converter, Compatibility
Additional Information

Consider using libraries like Pillow for image conversion, pdf2docx for PDF to DOCX conversion, and appropriate libraries for other formats.
Ensure that the script provides informative error messages in case of invalid input or other issues during the conversion process.

Contribution Guidelines
The updated guidelines can be found here.
Important Note:

It's not a single person's job to write this script, I am adding this as an issue so that you can comment first, on what you can add, and work on that so that another person doesn't work on the same function.
Note that whoever comments about what they will add, other people should avoid working on that, until that person says otherwise.
you can use third-party libraries if it can not be done with Python from scratch easily.
just need to add your own code and update the config.json file,
I have added one first function and conversation, so use that as your reference.

Happy Coding!!
Please follow the below guidelines.

folder name must be convert_{ext1}_to_{ext2} (ex: convert_srt_to_lrc) #btw both are lyrics files extensions
add a script with the same name as the folder name.
add __init__.py inside the same folder.
write your code using OOP for beginners if they don't know that, you can simply write a function also no worries as long as that works :). if it's OOP based then main method will be according to first point. and for funtion the name will be according to first point.
after writing modify the config.yml file, to add your function in the main script, that's it, I have already configured the convert_me.py script, so no need to modify anything.
currently all the functions will take only two arguments, input_file_path and output_file_path, but if you want to add more, you might need to modify the code in the convert_me.py file
that's it, Check the README.md file in the folder convert_srt_to_lrc, you can add your GitHub username there. under Features section.

Tracker

Done
Conversion
can be worked on?
Bugs
Contributor
Improvement Required

🟢
srt to lrc
Y

@bhargavnova
Y

🟢
pdf to docx
Y
Y
@harshjais369
Y

[ ]
pdf to txt

[ ]
pdf to html

[ ]
pdf to image (jpg, png, etc.)
Y

[ ]
docx to pdf

[ ]
docx to txt

[ ]
docx to html

[ ]
docx to pdf

[ ]
txt to pdf

🟢
txt to csv
Y

@kom-senapati

🟢
csv to json
Y

@scove

🟢
csv to xml
Y

@scove

[ ]
csv to excel (xlsx)

🟢
json to csv
Y

@scove

[ ]
json to xml

[ ]
xml to json

[ ]
xml to csv

[ ]
image (jpg, png, etc.) to pdf
Y

[ ]
image (jpg, png, etc.) to text

[ ]
image (jpg, png, etc.) to grayscale
Y

[ ]
audio (mp3, wav, etc.) to text

[ ]
audio (mp3, wav, etc.) to spectrogram image

[ ]
video (mp4, etc.) to audio (mp3, wav, etc.)
Y

[ ]
video (mp4, etc.) to images (frames)
Y

[ ]
video (mp4, etc.) to gif
Y

[ ]
audio (mp3, wav, etc.) to spectrogram image

[ ]
html to pdf
Y

[ ]
html to text
Y

[ ]
html to image
Y

[ ]
html to docx
Y

[ ]
html to markdown
Y

🟢
markdown to html
Y

@kom-senapati

[ ]
markdown to pdf
Y

[ ]
markdown to docx
Y

[ ]
epub to pdf
Y

[ ]
epub to mobi

[ ]
mobi to pdf

[ ]
pdf to epub

[ ]
pdf to mobi

[ ]
excel (xlsx, csv) to pdf
Y

[ ]
excel (xlsx, csv) to html
Y

[ ]
excel (xlsx, csv) to json

[ ]
excel (xlsx, csv) to xml

[ ]
excel (xlsx, csv) to text

[ ]
xml to excel (xlsx, csv)

[ ]
pdf to excel (xlsx, csv)

[ ]
pdf to json

[ ]
pdf to xml

Added universal_file_converter
clone this repo, add ur conversation function inside _my_utils/_utils/
there is one function added already convert_srt_to_lrc use that as a reference.
:)
Just have to add your own function.
modify the config.yml file.
modify the func_list.txt file.
Happy Coding!
Comment what are you going to work on, and start working, just make sure someone is not working on the same function as you are.
you can check previous comments for that, or check the code itself.

Hey @bhargavnova , seems very interesting and fun to work on this issue. I'm thinking to start it by first building a pdf to docx converter. Could you please assign me this issue under hacktoberfest label?

Sure @harshjais369, go ahead.

I have added one template folder which contains class-based .py file and function-based .py file,
you can choose any of those to get started, and add your function inside _my_utils/_utils/
Note: This Issue can have multiple contributors so anyone can submit their own conversation function, just mention here what you are going to work on.
if you have any doubts feel free to ask.

@bhargavnova Thank you! I have built my function, and will raise a PR after a few hours later..

Can I try CSV to JSON?

I will take JSON to CSV as well :smile:

I can do the txt to csv part.

I am also doing the markdown to html.

I will add CSV to XML :grinning:

Hey @bhargavnova , I would like to work on this. Can I take up pdf to txt and txt to pdf?

I can do html to markdown.

I want to add docx to pdf.

I also want to add image to grayscale.


sample_text_to_3d can't finish downloading "0/64 [00:00<?, ?it/s]"

I just copy sample codes and run, then a download task can't be done.
PS D:\shap-e> python test.py
  0%|                                                                                | 0/64 [00:00<?, ?it/s]

Me too

same here

Here is the fix: https://github.com/openai/shap-e/issues/64


(Prototype) Fix semantics node id overflow issue

The semantics id may overflow if the app generate too many semantics node.
This PR makes it so we only assign semantics id if the it is attached to the owner and set it to null when it is detached. The id generator will generate the id as usual until the id overflows. Once it overflows, it will check the used ids that are currently attaches to a semantics owner and make sure it doesn't generate a duplicated id.
There will be a lot of test failures (due to the id may be null), I will fix them once we are ok with this approach.
Fixes https://github.com/flutter/flutter/issues/77036
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Hi @goderbauer , can you take a look at this POC?

Hi @goderbauer thanks for reviewing, this is ready for another look!


Creation of Mesos workshop

Creating a one day hands on workshop similar to the existing Docker one, but focused on Mesos. It should include:

Overview/History of Mesos
Difference from Docker and Kuberneties

Demos of:

Deploying Docker Container on Mesos
Deploying an Application Bare Metal on Mesos

Great idea! Renamed to "Creation of Mesos workshop".

@jonasrosland found this lingering issue, can we close this out? Based on this PR https://github.com/emccode/training/pull/46


Document the API

It's actually pretty flexible and configurable. The people should know that.

Bam.


cleanup

There are too many different approaches in the directory but I haven't had the time yet to sort everything accordingly.
Files from other approaches could also be moved in other branches, however we may be able to reuse parts.

Close this for now as the main part is done by 26f0b734619e47544d34a8c5f80c2574683fd7d8.


lint cyoa branches

for @lldelisle, xref https://github.com/galaxyproject/training-material/pull/5529  featuring a number of new warnings:
$ ruby bin/lint.rb --limit GTN:041
./topics/climate/tutorials/ocean-variables/tutorial.md:1:1:1:1:GTN041 You have non-unique options in your Choose Your Own Adventure. Please ensure that each option is unique in its text. Unfortunately we do not currently support re-using the same option text across differently disambiguated CYOA branches, so, please inform us if this is a requirement for you.We identified the following duplicate options in your CYOA: Options xview, xview became the key: xview; Options png, png became the key: png
$ ruby bin/lint.rb --limit GTN:042
./topics/contributing/tutorials/create-new-tutorial-content/tutorial.md:1:1:1:1:GTN042 We recommend specifying a default for every branch
./topics/ecology/tutorials/marine_omics_bgc/tutorial.md:1:1:1:1:GTN042 We recommend specifying a default for every branch
$ ruby bin/lint.rb --limit GTN:043
./topics/genome-annotation/tutorials/apollo-euk/tutorial.md:1:1:1:1:GTN043 We did not see a corresponding option# for the default: _Create your own organism"_, but this could have been written before we automatically slugified the options. If you like, please consider making your default option match the option text exactly.
$ ruby bin/lint.rb --limit GTN:044
./topics/climate/tutorials/ocean-variables/tutorial.md:1:1:1:1:GTN044 We did not see a corresponding option# for the default: «tools», please ensure the text matches one of the branches.
$ ruby bin/lint.rb --limit GTN:045
./topics/assembly/tutorials/mrsa-nanopore/tutorial.md:1:1:1:1:GTN045 We did not see a branch for Without Illumina MiSeq data (Without-Illumina-MiSeq-data) in the file. Please consider ensuring that all options are used.

I think there are valid use cases for GTN:045, but, maybe people should be adding an explicit 'no' branch anyway, even if it is just an empty div?
the linting is not as nice as it could be, it reports the error as being on the first line of the file. But due to needing to use multi-line matches, we don't have a good way to know where the real start is...

This is amazing! Thank you so much.

For GTN045 I would be in favor of an empty div like when you wrap a conditional in a tool.


enable pagination in the project view

I don't think you've updated the loadData method of the route here (used for server side rendering):
https://github.com/BlueBrain/nexus-explorer/pull/78/files#diff-531be4588f505195388f950d7ccd50a4R51
Also, what's the effort of reflecting the pagination state in the URL: i.e. https://bbp-nexus.epfl.ch/staging/web/kenny/search?page=2
you get the state of your paginated list from here and you can use it both server and client side.
If that's a big job I guess it could be done in a separate task.


Standalone Library

Hey!
How can i use this project as a standalone library in my project? I tried importing the js files from /lib but it didn't work.
Thanks!

Currently I only support build tools like webpack or browserify as specified in README.md


additional components in dev env

Hi, I wanted to know if there's any way to setup a sharepath and the analytics component in the dev environment? The ways provided here and here should work with the regular installation only.
Thanks.

Hi,
CVAT uses cvat_root/share folder as a fileshare, just mount to this point any resource you want
Regarding Analytics I would to suggest run analytics containers (ELK) as usually but you need to forward port for logstash service definition here https://github.com/openvinotoolkit/cvat/blob/develop/components/analytics/docker-compose.analytics.yml#L57

Thanks for the answer. I didn't understand what I should do with the logstash service. Can you explain it again please?

@AmitN1212 , for analytics, nuclio you need docker containers. We don't develop these components. I will close the discussion. Don't hesitate to ask our community on gitter if you have more questions.


rails g ember:init hangs

Which operating system and version is the project developed on?
macOS Sierra
Which version of [ruby][ruby] is the project developed on?
⋊> ~/w/w/dossier on master ⨯ ruby -v                                                                          01:33:55
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]

Which version of [npm][npm] is the project developed on?
⋊> ~/w/w/dossier on master ⨯ npm -v                                                                           01:24:46
3.10.7

Which version of [ember-cli][ember-cli] is the project developed on?
⋊> ~/w/w/dossier on master ⨯ ember -v                                                                         01:34:20
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
ember-cli: 2.8.0
node: 6.6.0
os: darwin x64

What is the [rails][rails] version?
⋊> ~/w/w/dossier on master ⨯ rails -v                                                                         01:34:41
Rails <IP_ADDRESS>

What is the [ember-cli-rails][gem] version (from Gemfile)?
⋊> ~/w/w/dossier on master ⨯ cat Gemfile.lock | grep ember-cli                                                01:34:58
    ember-cli-rails (0.8.1)

What is the [ember-cli-rails-addon][addon] version (from package.json)?
N/A
Is your application server [multi-threaded][] (such as puma and unicorn) or is
it multi-process (such as thin and webrick)?
N/A
What are the contents of config/initializers/ember.rb?
N/A
What are the contents of the Rails' view that renders the Ember application?
N/A
How are the EmberCLI-related routes defined?
N/A
How is the application deployed?
N/A
When I run rails g ember:init... the command line just hangs. I have to CTRL-C to exit. When I do, I get this stacktrace:
⋊> ~/w/w/dossier on master ⨯ rails g ember:init                                                                01:32:06
^C/Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/client/run.rb:117:in `gets': Interrupt
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/client/run.rb:117:in `verify_server_version'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/client/run.rb:62:in `run'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/client/run.rb:42:in `warm_run'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/client/run.rb:35:in `call'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/client/command.rb:7:in `call'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/client/rails.rb:24:in `call'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/client/command.rb:7:in `call'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/client.rb:30:in `run'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/bin/spring:49:in `<top (required)>'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/binstub.rb:11:in `load'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-1.7.2/lib/spring/binstub.rb:11:in `<top (required)>'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /Users/thampton/.rbenv/versions/2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /Users/thampton/workspace/work/dossier/bin/spring:13:in `<top (required)>'
        from /Users/thampton/workspace/work/dossier/bin/rails:3:in `load'
        from /Users/thampton/workspace/work/dossier/bin/rails:3:in `<main>'

I'd like to mention that frontend does exist in my root directory.
⋊> ~/w/w/dossier on master ⨯ ls -ltrA | grep frontend                                                          01:38:16
drwxr-xr-x  21 thampton<PHONE_NUMBER>   714 Sep 27 01:28 frontend

I created my own initializer/config.rb file manually and then ran rake ember:install and that hung as well.
I then downgraded Spring to 1.2.0 since that was what was in the Gemfile.lock of the demo project and everything worked.

@howdoicomputer thanks for opening this issue.

I then downgraded Spring to 1.2.0

What was your Spring version before you downgraded?

It was at 1.7.0.

For reference, here is a similar issue: https://github.com/rails/spring/issues/486

And a stack Overflow post: http://stackoverflow.com/questions/25027284/ruby-on-rails-console-hanging-when-loading

I went through and did a sudo pkill spring to clean up stubborn processes. I don't know if this is really an ember-cli-rails bug but rather a spring bug since it is long standing and affects the generation process itself. Maybe this can be closed?

Thanks for debugging this issue, @howdoicomputer.

Maybe this can be closed?

I'll close it for now. If this continues to happen, and you or others feel like it's due to ember-cli-rails, please comment here and we'll reopen.
Thanks!


Applying action to text

Microsoft PowerToys version
0.70.1
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
I was trying to use "Apply action to text" to capitalize the text and none of it works, regarding in which program i try...
Picture of specs:

Picture of action:

✔ Expected Behavior
It should capitalize the text
❌ Actual Behavior
Nothing
Other Software
No response

This is not powertoys. Sorry. Looks like VS code or an extension there.


"Not in scope" warnings are shown even though the function/etc is defined in a parent component

"Not in scope" warnings are underlined in code and percolated to file explorer even thought the definition is in scope in a parent component ( ie. current component defined as extending a parent, and so on up the derivation chain.)

Can you provide a sample project or zip reproducing the issue? Typically are valid issues, due to some OTHER scope not having the required imports.

Will do...

We see this one scattered enormously through our code base, but in creating an example, I realize it is due to us creating "Abstract Components" (or abstract derivations thereof).  That is, the Abstract Component is invoking methods it expects to be in defined in components that are extensions of the "Abstract Component".  We do not create dummy (empty) definitions in the "Abstract Component" because, like all good compilers ;) , we want to have an error thrown at compile time.
Regardless, I have attached an example as promised.
simple-videoplayer-channel.zip
grep -rin --include=*.brs "issues/556"


"Undefined is not an object" on page transitions

Good morning,
First of all: Loving your slider!
I keep running into this one issue in my Angular app when moving to or from a page that holds a slider:
Error: undefined is not an object (evaluating 'e.settings.value.split')
create@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:49:383
init@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:45:1144
e@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:45:630
p@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:31:353
m@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:18:49
file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:29:46
file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/angularjs/angular.min.js:158:251
e@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/angularjs/angular.min.js:45:355
file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/angularjs/angular.min.js:48:276

I'm making some effort in debugging it and trying to figure out a workaround, but was wondering if you have seen this before? Perhaps I am just doing something wrong?
Thanks!

PS. In your latest code base, the error hits on line 622:
Error: undefined is not an object (evaluating 'self.settings.value.split')
create@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:622:39
init@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:583:18
Slider@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:559:29
slidering@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:188:30
init@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:78:53
file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/ng-slider/angular-awesome-slider.min.js:160:19
file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/angularjs/angular.min.js:158:251
e@file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/angularjs/angular.min.js:45:355
file:///Users/christian.schuit/Documents/Development/GitLab/sdc/sdc/sdc-app/src/main/html/ext/angularjs/angular.min.js:48:276

Further testing shows the same on line 647.
By added a test to both lines to see whether the object exists, the error goes away but I havent yet discovered whether this impacts the functionality of the slider. Further testing commences.
622: values = (self && self.settings && self.settings.value) ? self.settings.value.split(';') : [];
647: this.settings.single = (self && self.settings && self.settings.value) ? !self.settings.value.split(";")[1] : '';

To complete my test case, this is my directive code, where formatLabel is passed as a method (I replaced the other variables with literals for this test):
<input data-ng-model="amount" type="text"
    name="amount" id="amount" slider options="{
    from: 500,
    to: 8000,
    step: 500,
    dimension: '',
    scale: [
        formatLabel('R','')(500),
        formatLabel('R','')(2000),
        formatLabel('R','')(4000),
        formatLabel('R','')(6000),
        formatLabel('R','')(8000)
    ],
    heterogeneity: ['25/' + 2000,'50/' + 4000,'75/' + 6000],
    vertical: false,
    round: true,
    smooth: true,
    realtime: true,
    modelLabels: formatLabel('R',''),
    threshold: 2,
    css: {
        background: {'background-color': 'silver'},
            before: {'background-color': '#92AAC7'},
            default: {'background-color': 'white'},
            after: {'background-color': 'green'},
            pointer: {'background-color': 'red'},
            range: {'background-color': 'red'}
        }
    }" />

My formatting function:
$scope.formatLabel = function(prefix,postfix) {

	return function(value) {

		return '<nobr>' + prefix + $filter('number')(value, 0) + postfix + '</nobr>';
	}
}

Hope you can help me out...
Thanks!

Woo, first of all thanks a lot for sharing and all details given above. I am not sure I can take a look at the moment because I have not managed it for a while, but as soon as I got time, I will give a try.


push to npm?

@habbes maybe push this package to npm and also a PR on the at-node.js README on how to use this?

Okay, I will try to do so by the end of the week. I will add tests and a more comprehensive guide.

@ianjuam I've written unit tests, next is to work on a proper documentation

@habbes awesome! I'm already using this; playing around with the next USSD app/ demo. Haven't made much progress

@ianjuma oh great. Though may have made some changes to make sure all tests pass. I'll keep you posted. Hopefully the doc will be done soon.

And @ianjuma, are you hiring devs at Africastalking, I'd like to join you guys.

@habbes of course! We are always looking for good talent. I'll do a couple of introductions; always happy to :smile:

@ianjuma Oh cool. Let me know how it goes, I have already published the module on NPM, now just updating the documentation.

@ianjuma I've updated the docs with a more comprehensive guide. Hopefully now it makes sense.

@ianjuma my contacts<EMAIL_ADDRESS>or student<EMAIL_ADDRESS>

already did the intro :smile:


"Add missing types" functionality

Someone on the #vim channel on Slack mentioned that elm-mode for Emacs has a function to add types to functions missing type declarations.  I implemented a basic version of this for Vim here: https://gist.github.com/hoelzro/9228e18fb2cc6c672767193250e57497
Would you be interested in me cleaning this up and adding it to elm-vim via a PR? If so, any guidance on how you would like me to clean it up would be most weclome!

Any thoughts on this?

This feature is super useful! 👍

I would use it 👍


Add basic example for Tempo

Solves #8

@pavolloffay could you take a look? I applied all the changes we talked about. Thanks!

And probably add a follow-up ticket about using ODF instead of minio?

I added a warning in the README.md file about that. The problem is that ODF can be a little bit difficult to install... So, it depends on what we want to provide:

Examples where the customers can start "playing" with the product
Deployments production ready
@pavolloffay could you answer to this?

And probably add a follow-up ticket about using ODF instead of minio?

I added a warning in the README.md file about that. The problem is that ODF can be a little bit difficult to install... So, it depends on what we want to provide:

Examples where the customers can start "playing" with the product
Deployments production ready
@pavolloffay could you answer this?

Maybe, something I can do it's to just document that a secret with a given name (e.g. tempo-storage-secret) needs to be created, using ODF, AWS S3, Google Cloud Storage or Azure Storage.
What do you think?

Maybe, something I can do it's to just document that a secret with a given name (e.g. tempo-storage-secret) needs to be created, using ODF, AWS S3, Google Cloud Storage or Azure Storage. What do you think?

Yes, I like the idea of separating the tempo deployment and the storage. Because all examples in this repo will be compatible with any storage, or in other words, if we add the storage to all examples the storage part is basically duplicated.
Maybe something like "Step 1: Select your storage... Options: ODF, Minio, S3, ..." and "Step 2: Select tempo deployment; options: basic installation (this PR), multitenancy, ..." for the docs?

Maybe, something I can do it's to just document that a secret with a given name (e.g. tempo-storage-secret) needs to be created, using ODF, AWS S3, Google Cloud Storage or Azure Storage. What do you think?

Yes, I like the idea of separating the tempo deployment and the storage. Because all examples in this repo will be compatible with any storage, or in other words, if we add the storage to all examples the storage part is basically duplicated.
Maybe something like "Step 1: Select your storage... Options: ODF, Minio, S3, ..." and "Step 2: Select tempo deployment; options: basic installation (this PR), multitenancy, ..." for the docs?

I kind of this that in the last commit.

Maybe, something I can do it's to just document that a secret with a given name (e.g. tempo-storage-secret) needs to be created, using ODF, AWS S3, Google Cloud Storage or Azure Storage. What do you think?

Yes, I like the idea of separating the tempo deployment and the storage. Because all examples in this repo will be compatible with any storage, or in other words, if we add the storage to all examples the storage part is basically duplicated.
Maybe something like "Step 1: Select your storage... Options: ODF, Minio, S3, ..." and "Step 2: Select tempo deployment; options: basic installation (this PR), multitenancy, ..." for the docs?

I kind of this that in the last commit.

Kind of, yep; my point was, the storage will be different for each use case.
For on-prem customers, I'd suggest using ODF. For customers in the cloud, e.g. on AWS I'd suggest S3. But this can be done in a separate PR.


#22 Basic Pie Chart

Added new diagram, a basic Pie Chart, more advanced feature to follow.

Pull Request Test Coverage Report for Build 937

20 of 71 (28.17%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.05%) to 53.348%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/utils.js
1
2
50.0%

src/diagrams/pie/pieDb.js
16
19
84.21%

src/mermaidAPI.js
0
8
0.0%

src/diagrams/pie/pieRenderer.js
3
42
7.14%

Totals

Change from base Build 933:
0.05%

Covered Lines:
2622

Relevant Lines:
4862

💛  - Coveralls

A new diagram! Thats very nice! Looking forward to see it.


Add CLI subcommands for all admin dashboard actions

This PR adds CLI subcommands for all operations available in the web admin panel.
The gogs admin command now looks like this:
NAME:
   Gogs admin - Allow using internal logic of Gogs without hacking into the source code
to make automatic initialization process more smoothly

USAGE:
   Gogs admin command [command options] [arguments...]

COMMANDS:
     create-user                  Create a new user in database
     delete-inactive-users        Delete all inactive accounts
     delete-repository-archives   Delete all repositories archives
     delete-missing-repositories  Delete all repository records that lost Git files
     collect-garbage              Do garbage collection on repositories
     rewrite-public-keys          Rewrite '.ssh/authorized_keys' file (caution: non-Gogs keys will be lost)
     resync-hooks                 Resync pre-receive, update and post-receive hooks
     reinit-missing-repositories  Reinitialize all repository records that lost Git files

OPTIONS:
   --help, -h  show help

Thank you!

@Unknwon I just realized that these new subcommands only work when a gogs web instance is running. Is there a quick way to fix this?

@knedlsepp I think it depends on which subcommands you're looking for executing without web instance.


Wrong port on maven repo

I swear I'd updated the server settings so it'd still be available over 8081, but oh well. Shouldn't be too hard to fix across the mods that depend on Cotton stuff


dependencies: Upgrade Source Sans Pro font to Source Sans 3

https://blog.adobe.com/en/2020/11/30/whats-new-in-source-sans-3.html
Testing plan: Basic dev server testing, with extra attention to the numbers we draw in the favicon, which needed a quoting fix for a font-family containing a digit.

Can you do before/after screenshots?  It looks like it's mostly an additive change but I figure we should at least look at whether there's a noticeable change in the appearance of text.

There are minuscule metric differences, but an English speaker isn’t going to notice them (unless the picture in their Word document that was carefully positioned with thousands of space characters got rewrapped to the next page).

Merged, thanks @andersk!


Finish crio base tests

Add crio container template and associated ping container
creation/exec. Add functionality for created container to ping
to host. Remove hacky start and extra init file.
Signed-off-by: Yu Qi Zhang<EMAIL_ADDRESS>

Just realized that the generated image should have been named localhost/ping:latest as per https://github.com/ashcrow/mantle/pull/1/files#diff-97d819ab0f34263a7b5a5aa1082aad0cR53 ,
but is actually named docker.io/library/ping . The tests should pass as I added: https://github.com/ashcrow/mantle/pull/1/files#diff-97d819ab0f34263a7b5a5aa1082aad0cR93 but should look into.


Using @sentry/electron with @sentry/webpack-plugin doesn't provide proper stack traces anymore (1.X worked fine)

Environment
"@sentry/webpack-plugin": "^2.1.0"
"@sentry/electron": "^4.5.0" (which uses "@sentry/browser": "7.50.0", which should be compatible and have debug_id support)
Steps to Reproduce
I'm using electron and a dual build with separate configs for building main and the renderer.
In production code I use the following SDK in main:
import * as Sentry from '@sentry/electron/main'
Sentry.init({
  dsn: process.env.SENTRY_DSN,
  release: APP_VERSION || 'unknown',
  environment: process.env.STAGE,
  integrations: [new Sentry.Integrations.ElectronMinidump()]
})

And the following in the renderer:
import * as Sentry from '@sentry/electron/renderer'
Sentry.init({
  dsn: process.env.SENTRY_DSN,
  release: process.env.APP_VERSION || 'unknown',
  environment: process.env.STAGE,
  integrations: (defaultIntegrations) => {
    return [new CaptureConsoleIntegration(), ...defaultIntegrations]
  }
})

I'm using the following for the main webpack config:
import { sentryWebpackPlugin } from '@sentry/webpack-plugin'
sentryWebpackPlugin({
  authToken: process.env.SENTRY_AUTH_TOKEN,
  org: 'XXXXX',
  project: 'XXXXX-desktop',
  sourcemaps: {
    assets: [
      path.join(__dirname, '..', '..', '..', 'desktop-release', 'app', 'dist', 'main.js.map'),
      path.join(__dirname, '..', '..', '..', 'desktop-release', 'app', 'dist', 'main.js'),
      path.join(__dirname, '..', '..', '..', 'desktop-release', 'app', 'dist', 'pdfWorker.js.map'),
      path.join(__dirname, '..', '..', '..', 'desktop-release', 'app', 'dist', 'pdfWorker.js')
    ]
  }
})

and the following for the renderer webpack config:
import { sentryWebpackPlugin } from '@sentry/webpack-plugin'
sentryWebpackPlugin({
  authToken: process.env.SENTRY_AUTH_TOKEN,
  org: 'XXXXXX',
  project: 'XXXXX-desktop',
  sourcemaps: {
    assets: [path.join(__dirname, '..', '..', '..', 'desktop-release', 'app', 'dist', '**')],
    // those are handled by the main build
    ignore: ['main.js', 'main.js.map', 'pdfWorker.js', 'pdfWorker.js.map']
  }
})

The logs of the main build process:
Source Map Upload Report
  Minified Scripts
    ~/600a95d7-1ae2-4529-98c1-f9862b6de145-0.js (sourcemap at main.js.map, debug id 600a95d7-1ae2-4529-98c1-f9862b6de145)
    ~/e90f76c6-acb5-46ca-9791-6722a6566319-1.js (sourcemap at pdfWorker.js.map, debug id e90f76c6-acb5-46ca-9791-6722a6566319)
  Source Maps
    ~/600a95d7-1ae2-4529-98c1-f9862b6de145-0.js.map (debug id 600a95d7-1ae2-4529-98c1-f9862b6de145)
    ~/e90f76c6-acb5-46ca-9791-6722a6566319-1.js.map (debug id e90f76c6-acb5-46ca-9791-6722a6566319)

The logs of the renderer build process:
Source Map Upload Report
  Minified Scripts
    ~/1e674106-c4ca-473f-8846-4ba4c32fd4c2-1.js (sourcemap at windowAuth.js.map, debug id 1e674106-c4ca-473f-8846-4ba4c32fd4c2)
    ~/4e803fcc-3af8-4e1a-a133-7d0d2437cda1-2.js (sourcemap at runtime.js.map, debug id 4e803fcc-3af8-4e1a-a133-7d0d2437cda1)
    ~/600a95d7-1ae2-4529-98c1-f9862b6de145-6.js (sourcemap at main.js.map, debug id 600a95d7-1ae2-4529-98c1-f9862b6de145)
    ~/693adea4-6c20-43ae-87d6-1e65ceb6ce16-9.js (no sourcemap ref, debug id 693adea4-6c20-43ae-87d6-1e65ceb6ce16)
      - warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/693adea4-6c20-43ae-87d6-1e65ceb6ce16-9.js)
    ~/8ba42dbb-5a24-4dc0-a266-455ba38368ae-0.js (sourcemap at windowMain.js.map, debug id 8ba42dbb-5a24-4dc0-a266-455ba38368ae)
    ~/91348eeb-3570-44cb-a750-ceb848961393-8.js (no sourcemap ref, debug id 91348eeb-3570-44cb-a750-ceb848961393)
      - warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/91348eeb-3570-44cb-a750-ceb848961393-8.js)
    ~/c488e720-7582-4c36-9795-65d3164cf26a-10.js (no sourcemap ref, debug id c488e720-7582-4c36-9795-65d3164cf26a)
      - warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/c488e720-7582-4c36-9795-65d3164cf26a-10.js)
    ~/e28603d3-7806-4eb9-b165-6e4f47976d07-7.js (sourcemap at loader.js.map, debug id e28603d3-7806-4eb9-b165-6e4f47976d07)
    ~/e90f76c6-acb5-46ca-9791-6722a6566319-4.js (sourcemap at pdfWorker.js.map, debug id e90f76c6-acb5-46ca-9791-6722a6566319)
  Source Maps
    ~/1e674106-c4ca-473f-8846-4ba4c32fd4c2-1.js.map (debug id 1e674106-c4ca-473f-8846-4ba4c32fd4c2)
    ~/4e803fcc-3af8-4e1a-a133-7d0d2437cda1-2.js.map (debug id 4e803fcc-3af8-4e1a-a133-7d0d2437cda1)
    ~/600a95d7-1ae2-4529-98c1-f9862b6de145-6.js.map (debug id 600a95d7-1ae2-4529-98c1-f9862b6de145)
    ~/8ba42dbb-5a24-4dc0-a266-455ba38368ae-0.js.map (debug id 8ba42dbb-5a24-4dc0-a266-455ba38368ae)
    ~/e28603d3-7806-4eb9-b165-6e4f47976d07-7.js.map (debug id e28603d3-7806-4eb9-b165-6e4f47976d07)
    ~/e90f76c6-acb5-46ca-9791-6722a6566319-4.js.map (debug id e90f76c6-acb5-46ca-9791-6722a6566319)

Then in main.ts I capture an Exception:
import * as Sentry from '@sentry/electron/main'
Sentry.captureException(new Error('main test error'))

And in the renderer I throw:
throw new Error('renderer test error')

Main Result (eventId: 1803622f265e4d8e82afc5c621c8d736):

Renderer Result (eventId: 452429489c4849db8a73c8c8745a90e6):

What I expect
I expect the stacktraces to point me exactly where in the code the Error was thrown. As it was before when using 1.x.
Things I tried out
I tried adding
release: {
  name: APP_VERSION || 'unknown'
}

to the config and also tried without it. It doesn't really have an effect other than me knowing which artifacts belong to which release, if I understood correctly.
I am sure that artifacts are uploaded correctly, as I can see them under Project > Source Maps > Artifact Bundles.
If I download a file from an artifact bundle I can see both sourceMappingURL=XXX and debugId=YYY being present.
Neither am I using a dist value in SDK, nor in sentryWebpackPlugin.
As a reference: This used to be my previous 1.x renderer config that worked flawlessly:
new SentryWebpackPlugin({
  authToken: process.env.SENTRY_AUTH_TOKEN,
  org: 'XXX',
  project: 'XXX',
  include: {
    urlPrefix: 'app:///dist/',
    stripCommonPrefix: true,
    paths: [path.join(__dirname, '..', '..', '..', 'desktop-release', 'app', 'dist')]
  },
  // those are handled by the main build
  ignore: ['main.js', 'main.js.map', 'pdfWorker.js', 'pdfWorker.js.map'],
  release: APP_VERSION || 'unknown'
}),

Note that I had to use the urlPrefix app:///dist. With the new artifact system this should not be necessary anymore, right?
Due to running out of ideas I tried adding rewriteSources: (source) => `app:///dist/${source}` , but that had no effect as far as I could tell.
If I look at the json of the two events, I CANNOT see a bundle_id anywhere, so I'm assuming this is the culprit?

PS: this page is out of date: https://docs.sentry.io/platforms/javascript/sourcemaps/best-practices/

Hey, can you share a link to the sentry event that is not uminified properly? You can use the share button if you don't want your org name public. Thanks!  You basically provided all the info I would have asked for :)

Hey, can you share a link to the sentry event that is not uminified properly? You can use the share button if you don't want your org name public. Thanks! :)

@lforst org name public shouldn't be an issue, is that what you wanted?
https://fugoya.sentry.io/issues/4207322458/events/1803622f265e4d8e82afc5c621c8d736/
https://fugoya.sentry.io/issues/4207365171/events/452429489c4849db8a73c8c8745a90e6/

By the way: I wanna give you props for doing a bunch of research before you opened this issue. You basically provided all the info I would have asked for :)

I hate opening issues on github because it means I take away attention from someone else that could be doing something more productive, but in this case I'm just kinda lost on what to try next :-)
Btw liebe Grüße ausm 7. in den 2. ✌🏻

Also: If you set debug: true in the plugin. Can you share logs with the [sentry-webpack-plugin] prefix? thanks!

That's what I get in addition:
[sentry-webpack-plugin] Info: Sending error and performance telemetry data to Sentry. To disable telemetry, set `options.telemetry` to `false`.
[sentry-webpack-plugin] Debug: Could not determine debug ID from bundle. This can happen if you did not clean your output folder before installing the Sentry plugin. File will not be source mapped: /XXX/desktop-release/app/dist/preload.js
[sentry-webpack-plugin] Debug: Could not determine source map path for bundle: /XXX/desktop-release/app/dist/362.js
[sentry-webpack-plugin] Debug: Could not determine source map path for bundle: /XXX/desktop-release/app/dist/374.js
[sentry-webpack-plugin] Debug: Could not determine source map path for bundle: /XXX/desktop-release/app/dist/126.js
[sentry-webpack-plugin] Debug: Could not determine debug ID from bundle. This can happen if you did not clean your output folder before installing the Sentry plugin. File will not be source mapped: /XXX/desktop-release/app/dist/pdf.worker.js

Interesting.
So the 362.js 374.js and 126.js are actually just i18n files, so don't worry about them.
The preload.js and pdf.worker.js are something to fix differently I guess, but both of them are not that important.
The main.js and windowMain.js are the two really important ones, both are not logged in a special way since flagging debug.

I just saw: while the uploaded artifacts have a debugId=YYY, the main.js in my dist (that gets packaged into the final binary) does not have a debugId at the bottom, only //# sourceMappingURL=main.js.map. Is that correct?

Running sentry-cli sourcemaps explain yields:
✔ Fetched data for event: 452429489c4849db8a73c8c8745a90e6
✔ Event has release name: 0.1.11
✔ Event has a valid exception present
✔ Event has a valid stacktrace present
⚠ Exception is already source mapped and first resolved frame points to:

> [missing context line]

I just saw: while the uploaded artifacts have a debugId=YYY, the main.js in my dist (that gets packaged into the final binary) does not have a debugId at the bottom, only //# sourceMappingURL=main.js.map. Is that as intended?

Yeah that is intended!
We actually found the culprit and a fix is on its way: https://github.com/getsentry/sentry-electron/pull/676

SDK development any% (test skip glitch allowed) PB

@lforst I saw one runner timed out preventing the release of 4.6.0, can you check?
https://github.com/getsentry/sentry-electron/actions/runs/5091595222

@tom2strobl thanks for the heads up. Electron SDK CI is a bit flakey. The release is out now if you wanna try it out.
LG ausm 2. :)

4.6.0 build went through, updated @sentry/electron, tested it and can user-confirm, both renderer and main stacktrace now like a charm. Thanks!

@tom2strobl great! Thanks for verifying :)


Implement a get_model function for the pymc3 backend

You may consider creating an object for with environments, i.e., an object that implements __enter__ and __exit__

Fixed in #97


Couldn't bring up network: couldn't find any CNI network configurations

**Rancher versions:v2.0.0-alpha10
**
I had this issue, Please help !

Results:

Closing as duplicate of https://github.com/rancher/rancher/issues/10033


parse uefi-label to allow the user to define a custom label

Hey,
in some UEFIs the default Label may not be valid and therefor not displayed.
The user should have the option to specify a custom label.
This commit will allow uefi-mkconfig to parse file called uefi-label (searched for in the same paths as uefi-mkconfig) and use that label instead.

I thought about allowing the user to write a little script that will be sourced, but i think it would be easier to create an installkernel hook that runs before uefi-mkconfig that writes to that file.
Not sure what about the default label wont work on my System, I'll do some testing...

The problem with that is that uefi-mkconfig regenerates the entries for all kernels, not just the one that is being installed via installkernel. This is by design because we use uefi-mkconfig only for the "traditional" implementation of installkernel that does not support kernel removal. For systemd's kernel-install we use fedora's virt-firmware instead which approaches the problem differently, meaning that it creates and removes an entry only for the kernel version that is being installed or removed.

Ohh yeah thats a problem...
Do you think we can safely parse the respective names from the initial_uefi_state?

Btw I figured out why the default Label is invalid: For some reason my uefi has a maximum length of exactly 60 characters for the label

Hello, @fabolous005 !
Regarding the label customization, but for this we would need to do a lot more verification if the custom label is valid + there is the problem with including something that will be unique for each entry. In short, it is possible but would introduce a lot more complexity.
However your finding that your firmware has a limit of 60 characters is a great finding! I'll make a fix so the default generated entries do not exceed this limit.
If you want we can have a longer discussion regarding the label customization and we can develop it further to see if it is feasible without overengineering it. But I will not merge it now.

However your finding that your firmware has a limit of 60 characters is a great finding! I'll make a fix so the default generated entries do not exceed this limit.

Note that this limit is not part of the UEFI spec AFAIK, it may well be that other boards have limits of 50 or 40 characters. That being said, it is of course a good idea to be as short as possible.

Note that this limit is not part of the UEFI spec AFAIK, it may well be that other boards have limits of 50 or 40 characters. That being said, it is of course a good idea to be as short as possible.

Yes yes, I'm aware. I'll try to make those labels as short as possible while remaining usable now that I know length constraint exists.

I'll release fix ASAP

@Biosias, @AndrewAmmerlaan  thank you, i would gladly try to help developing this further, btw i'm also the guy from reddit, asking about multiple kernel entries with different kernel cmdline per kernel.
Feel free to close this for now (as it's clearly nowhere near a good solution).
I'll open a PR regarding said problem soon, as i think it should be easier to implement.
Quick question do you prefer configuring that from one file and iterating over lines, or use glob matching on any of previous used directories?

Regarding support for multiple different cmdlines, my suggestion would be to simply use the config file we already have but to allow this file to have multiple lines. For each line in the file we would then register an entry in the UEFI.

Yeah i meant that, Thanks!

I'll close  this PR for now. Could you please open an issue with a list of features you would like to add so we can discuss them?


Add information about library dependencies in a release

Users adds Boost to their toolset using different approaches when using and installing boost libraries (package managers, adding source to their in-house repos, using their own build system...).
One useful information for users that want to evaluate or limit the size of their boost dependency in their applications is to know the dependency chain of their chosen libraries. This way, users can know and minimize the headers and library compilation requirements that need to be distributed with their applications, SDKs....
Currently [a dependency report] (https://pdimov.github.io/boostdep-report/) is generated for each release in pdimov's website, but it would nice if this information is at least linked in the new website for each release. A nicer dependency report plot or graph generated with the boostdep tool (which produces html, csv, and other formats) would be a nice to have goodie, but the basic information listed in the html report is a good starting point.

@PeterTurcan I think we discussed that in some PR in website-v2-docs?

@igaztanaga Agree with your assertions. We can certainly add a link from the User Guide to pdimov's website. I am not sure how a user extracts the full list of primary and secondary dependencies from this report easily - adding an explanation of how to do this to the User Guide would add value.
@alandefreitas @pdimov

I am not sure how a user extracts the full list of primary and secondary dependencies from this report easily

There's a list for each library.

OK. Added a short explanation and links in this PR:
https://github.com/boostorg/website-v2-docs/pull/173

Boost should be capitalized.

I can change it, but boost is not capitalized here: https://pdimov.github.io/boostdep-report/
Ideally link text and the target should match - though happy to change it if there is a reason for the lower case on your reports?

I'm emulating the Boost logo there. It's capitalized in the page title.


Named Imports can be used.

https://github.com/pimlicolabs/erc20-paymaster-contracts/blob/60c3ea1c2d75069f9aa7f8d35bc08545a2edb34b/src/PimlicoERC20Paymaster.sol#L8
Suggested Change:
import {IERC20Metadata} from<EMAIL_ADDRESS>
Which can improve readability and also destruct only the necessary code.

If this is necessary, I would like to raise a PR.


Fix apt_repository for latest os version 16.10

Description
Great description and solution of the problem made by @jeremiahsnapp in
the below issue!
Closes https://github.com/chef/chef/issues/5831
I have validated this works fine for the following os:

Ubuntu 14.04
Ubuntu 16.04
Ubuntu 16.10 (latest)
Debian-6.0.10
Debian-8.7 (latest)

Signed-off-by: Salim Afiune<EMAIL_ADDRESS>Issues Resolved

COOL-685
https://github.com/chef/chef/issues/5831

Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

@afiune Any idea how this works on Debian?

Nice fix, Salim. It needs chefstyle fixes, and it would be good to confirm on Debian 6 and Debian 8, at least.

Thanks @tas50 @thommay ... Chefstyle has been fix, I'll push it again as soon as I confirm functionality in Debian.

@tas50 @thommay Done! Test should pass this time... Take it away!


Various Styling and Perf Improvements

Fix #101
Test URLs:

https://bug-styles--famous-smoke-cigaradvisor--hlxsites.hlx.page/cigaradvisor/
https://bug-styles--famous-smoke-cigaradvisor--hlxsites.hlx.page/cigaradvisor/fragments/404
https://bug-styles--famous-smoke-cigaradvisor--hlxsites.hlx.page/cigaradvisor/author/john-pullo
https://bug-styles--famous-smoke-cigaradvisor--hlxsites.hlx.page/cigaradvisor/posts/2023/12/top-10-best-new-cigars-of-2023

The blog post template seems to break the footer on the posts.

Yep. Got a little too over zealous . Will fix

Fixed(?)


Update to use newer node path code

The version of path this uses is very old - many things won't work, eg my code uses path.posix because it needs to process posix paths even when running on windows, but it's missing in this version so you get undefined error in browser. Also path.parse and etc
I'd be happy to do a PR but only if it's welcome and likely to actually get merged - hasn't been any activity here in four years
Alternately is there a way to override core things like path in browserify? I read the manual etc but couldn't find anything. May have missed it.

#12 updated to Node 8. i'll release soon after porting some more tests.

Alternately is there a way to override core things like path in browserify? I read the manual etc but couldn't find anything. May have missed it.

you can use the --require flag with an alias to do this sort of thing:
browserify --require ./my-path-polyfill:path


Does the segmentation codes load pretrained weight?

Hi,
There is difference between detection codes and segementation codes.
https://github.com/whai362/PVT/blob/cceb465b7dfb2b7a48b39074a14a04dedab427e8/detection/pvt.py#L241
https://github.com/whai362/PVT/blob/cceb465b7dfb2b7a48b39074a14a04dedab427e8/segmentation/pvt.py#L241
It seems that segmentation codes do not load pretrained weights. Is this a bug?

Maybe it is a bug in detection? The backbone(PVT) initialize in Detector.weight_init()


Update helm chart documentations

Current helm chart Readme https://github.com/ceph/ceph-csi/blob/master/charts/ceph-csi-cephfs/README.md and https://github.com/ceph/ceph-csi/tree/master/charts/ceph-csi-rbd  will talk about only on how to install and uninstall cephfs and rbd csi driver. we need to document all the available options when deploying these helm charts, This will help users to understand available options which they need to pass when there are installing helm charts

@yati1998 is it something you are interested to work on ?

@humblec sure I will take a look into this.

@humblec or @Madhu-1 can you please give me some more details on the other options available when deploying the helm charts? Or if there are any reference for this that can help me in the documentation.

the configuration we need to documents are https://github.com/ceph/ceph-csi/blob/master/charts/ceph-csi-cephfs/values.yaml and https://github.com/ceph/ceph-csi/blob/master/charts/ceph-csi-rbd/values.yaml https://github.com/rook/rook/blob/master/Documentation/helm-operator.md is an example you can follow

@Madhu-1 thanks for the insights.

We also need to add helm upgrade also which is missing currently.


WIP: introduce project file documentation

Oops, didn't see that WIP there, but this looked good so far.


Bookstore: connect to API

👇 👇 The following feature was added to the branch 👇 👇
✍  App id was generated
✍ Data from API was fetched into the react component
✍ Two features Add-new-book item and Remove-book from the list were applied

🙏🙏 Thank you so much!!!


TrailingStopRiskManagementModel Only Handles Long Positions

Expected Behavior
TrailingStopRiskManagementModel handles risk for both long and short positions.
Actual Behavior
TrailingStopRiskManagementModel only handles risk for long positions.
Potential Solution
Implement logic to handle risk for short positions.
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

Please could I be assigned to this issue?


Refactor validate_template_version_patch method to use parent_service_template_name instead of parent_resource_id

Fixes #3824
This pull request refactors the validate_template_version_patch method in order to use the parent_service_template_name instead of the parent_resource_id.  This was preventing user resource upgrades from working.

/test-extended

@marrobi Can you confirm the right issue is linked? I don't see the relationship between Key Vault secrets restore and this PR.

It is now, sorry.

/test-force-approve
Passed: https://github.com/microsoft/AzureTRE/actions/runs/7499784309


[Feature] export image file-list

(This is probably already supported, but I've been unable to locate this feature if it's already present)
It would be handy to be able to export the full list (or tree) of files contained in the image, in-order to compare with content of other images.
Especially for larger images, where the current UI doesn't easily support overview.
My initial thought was an export that contained the full paths ala. output from find, but I'm open to suggestions :)
Ie. output like so:
$ find /var | sort
/var
/var/backups
/var/cache
/var/cache/apt
/var/cache/apt/archives
/var/cache/apt/archives/apport_2.20.9-0ubuntu7.12_all.deb
...

This would also provide a workaround for #63; by combining the exported list with grep or similar.

I needed the same thing in #270 and got half baked notes how to implement that in https://dev.to/abitrolly/non-interactive-ls-for-dive-2pgl-temp-slug-7094088?preview=befe9a1b5ceadee0d4c5ac1cafb9ff89e4cc4e6751550bced33edd1578f7351ed216faa0a92fe180bc536a493b37141864ca3e45701ca7fb9c9bca3c
And today I discovered this tool - https://github.com/GoogleContainerTools/container-diff - that can potentially get the list from the image. Haven't tried it. Please tell me if it works.

Hi @abitrolly,
Nice find.
The suggested container-diff is indeed able to output find-ish output as outlined by the excerpt below:
$ container-diff analyze --type=file daemon://i386/ubuntu:18.04

-----File-----

Analysis for i386/ubuntu:18.04:
FILE                                                                                SIZE
/bin                                                                                5M
/bin/bash                                                                                1.2M
/bin/bunzip2                                                                                33.4K
/bin/bzcat                                                                                33.4K
/bin/bzcmp                                                                                6B
/bin/bzdiff                                                                                2.1K
/bin/bzegrep                                                                                6B
/bin/bzexe                                                                                4.8K
/bin/bzfgrep                                                                                6B
/bin/bzgrep                                                                                3.6K
/bin/bzip2                                                                                33.4K
...

.. export the full list (or tree) of files contained in the image, in-order to compare with content of other images.

This is nicely covered by the diff argument, as demonstrated below:
$ container-diff diff --type=file daemon://i386/ubuntu:18.04 daemon://myFlacImage:latest

-----File-----

These entries have been added to i386/ubuntu:18.04:
FILE                                                        SIZE
/usr/bin/flac                                               243K
/usr/bin/flac2aac.sh                                        9.5K
/usr/bin/metaflac                                           150.3K
/usr/lib/i386-linux-gnu/libFLAC.so.8                        16B
/usr/lib/i386-linux-gnu/libFLAC.so.8.3.0                    373.3K
/usr/lib/i386-linux-gnu/libogg.so.0                         15B
/usr/lib/i386-linux-gnu/libogg.so.0.8.2                     29.2K
/usr/share/doc/flac                                         8.7K
/usr/share/doc/flac/changelog.Debian.gz                     31B
/usr/share/doc/flac/copyright                               8.7K
/usr/share/doc/libflac8                                     11K
/usr/share/doc/libflac8/changelog.Debian.gz                 2.4K
/usr/share/doc/libflac8/copyright                           8.7K
/usr/share/doc/libogg0                                      5.2K
/usr/share/doc/libogg0/changelog.Debian.gz                  1.6K
/usr/share/doc/libogg0/copyright                            3.6K
/usr/share/doc/multiarch-support                            24.9K
/usr/share/doc/multiarch-support/changelog.Debian.gz        28B
/usr/share/doc/multiarch-support/copyright                  24.9K
/var/lib/dpkg/info/flac.list                                294B
/var/lib/dpkg/info/flac.md5sums                             354B
/var/lib/dpkg/info/libflac8:i386.list                       247B
/var/lib/dpkg/info/libflac8:i386.md5sums                    218B
/var/lib/dpkg/info/libflac8:i386.shlibs                     19B
/var/lib/dpkg/info/libflac8:i386.symbols                    15K
/var/lib/dpkg/info/libflac8:i386.triggers                   60B
/var/lib/dpkg/info/libogg0:i386.list                        242B
/var/lib/dpkg/info/libogg0:i386.md5sums                     215B
/var/lib/dpkg/info/libogg0:i386.postinst                    135B
/var/lib/dpkg/info/libogg0:i386.postrm                      132B
/var/lib/dpkg/info/libogg0:i386.shlibs                      17B
/var/lib/dpkg/info/libogg0:i386.symbols                     2.1K
/var/lib/dpkg/info/multiarch-support.list                   163B
/var/lib/dpkg/info/multiarch-support.md5sums                76B
/var/lib/dpkg/status-old                                    88.5K

These entries have been deleted from i386/ubuntu:18.04: None

These entries have been changed between i386/ubuntu:18.04 and myFlacImage:latest:
FILE                                 SIZE1         SIZE2
/var/log/dpkg.log                    188.3K        190.7K
/var/lib/dpkg/status                 85.2K         88.5K
/var/log/apt/history.log             7.4K          7.6K
/etc/ld.so.cache                     6.9K          7.1K
/var/log/apt/eipp.log.xz             5K            5.2K
/var/cache/ldconfig/aux-cache        4.9K          5.1K
/var/log/apt/term.log                67B           2.1K
/var/lib/apt/extended_states         0             176B

Closing, as the desired feature is covered by another tool.

I've found another Google tool called crane that is able to export tar of image into tar of final image filesystem. I had to patch the tool, so that it can read image (which is also tar compressed) from stdin. The patch is merged, but not released. Yet it is possible to use it from source.
An example of reading /etc/passwd from node:16-alpine image (tar -Oxf explained).
✗ podman image save node:16-alpine - | ./crane export - - | tar -Oxf - etc/passwd
root:x:0:0:root:/root:/bin/ash
bin:x:1:1:bin:/bin:/sbin/nologin
daemon:x:2:2:daemon:/sbin:/sbin/nologin
adm:x:3:4:adm:/var/adm:/sbin/nologin
lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin
sync:x:5:0:sync:/sbin:/bin/sync
shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown
halt:x:7:0:halt:/sbin:/sbin/halt
mail:x:8:12:mail:/var/mail:/sbin/nologin
news:x:9:13:news:/usr/lib/news:/sbin/nologin
uucp:x:10:14:uucp:/var/spool/uucppublic:/sbin/nologin
operator:x:11:0:operator:/root:/sbin/nologin
man:x:13:15:man:/usr/man:/sbin/nologin
postmaster:x:14:12:postmaster:/var/mail:/sbin/nologin
cron:x:16:16:cron:/var/spool/cron:/sbin/nologin
ftp:x:21:21::/var/lib/ftp:/sbin/nologin
sshd:x:22:22:sshd:/dev/null:/sbin/nologin
at:x:25:25:at:/var/spool/cron/atjobs:/sbin/nologin
squid:x:31:31:Squid:/var/cache/squid:/sbin/nologin
xfs:x:33:33:X Font Server:/etc/X11/fs:/sbin/nologin
games:x:35:35:games:/usr/games:/sbin/nologin
cyrus:x:85:12::/usr/cyrus:/sbin/nologin
vpopmail:x:89:89::/var/vpopmail:/sbin/nologin
ntp:x:123:123:NTP:/var/empty:/sbin/nologin
smmsp:x:209:209:smmsp:/var/spool/mqueue:/sbin/nologin
guest:x:405:100:guest:/dev/null:/sbin/nologin
nobody:x:65534:65534:nobody:/:/sbin/nologin
node:x:1000:1000:Linux User,,,:/home/node:/bin/sh


How do you train your data

i want to train my data,but i don't know what should do,Where should I put my image?

hello，i meet this problem too. Do you solve it? I need your help. Thank you


getImage() does not seem to work and always times out

Tested API and sample works well.
When I added commaner.getImage() i always get
akka.pattern.AskTimeoutException: Ask timed out on [Actor[akka://DroneAPI/user/$a#-817831732]] after [2000 ms]
			Future<byte[]> p = commander.getImage();
			p.onFailure(new OnFailure() {

				@Override
				public void onFailure(Throwable arg0) throws Throwable {
					arg0.printStackTrace();

				}
			}, system.dispatcher());

Hello,
Can you try the following sequence and report me the results?

Initialize video on the DroneCommander class (initVideo())
Subscribe (using an Akka aktor) to the DroneCommander using the ImageMessage class e.g. ImageMessage subscription
Register the receive message on the next line (part of the abstract actor) to listen to an ImageMessage. Right now this is a simple byte array of a JPEG encoded frame (due to decoder restrictions in Java) which can be sent to e.g. OpenCV.

There have also been some reports that video frames got increased in the new 3.0+ firmware. Is this the newest version you're on?
The code needs a patch on https://github.com/ugent-cros/cros-core/blob/01ad96a1008b38ed6b0a8decb781028a314bd236/drivers/parrot/src/parrot/ardrone3/protocol/ArDrone3.java#L40 to
private static final int MAX_FRAME_SIZE = 65000;
but since we no longer have a Bebop at our disposal, I haven't been able to verify this and push to the repository.
I am not sure about the getImage call directly, @brecht-d-m can you elaborate on this?

Is this ticket still relevant?


[ZEPPELIN-5427] mongodb interpreter: config by env vars

What is this PR for?
Add the possibility to configure the interpreter through env vars
What type of PR is it?
Improvement
Todos
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-5427
How should this be tested?
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? Maybe

LGTM
@cnoelle Have you tested this function manually?

LGTM
@cnoelle Have you tested this function manually?

Yes, exactly

LGTM
@cnoelle Have you tested this function manually?

Yes, exactly

Okay, I think that should be a nice feature for 0.10.0.


Revert "Add Meta.engine_version"

Reverts enso-org/enso#11320
@JaroslavTulach suggested that such a text-based API is an anti-pattern and so we should back out the PR.
When running locally, we probably should be able to rely on digging through logs to find the engine version that was picked up.

Do we not want a way to get the version of the engine and the libs at runtime?

Do we not want a way to get the version of the engine and the libs at runtime?

If it is supposed to be used by code, then indeed it needs more design. This was just a little debug tool. I think it could have been useful as a debug tool, but I don't want to argue about it.
I guess ideally, we'd want the IDE to display the currently running engine version next to the GUI version. This could probably be achieved by adding some Language Server endpoint. But that requires additional coordination between GUI and LS teams.

i guess @4e6 @MrFlashAccount for discussion
personally i don't think there's any real preference for the exact API, as long as it's callable and returns info dashboard will be able to use it.
so if anything the discussion would be on what info we want - (just the engine version? git branch/hash so that we can debug engine binaries taken from PRs?)

Do we not want a way to get the version of the engine and the libs at runtime?

If it is supposed to be used by code, then indeed it needs more design. This was just a little debug tool. I think it could have been useful as a debug tool, but I don't want to argue about it.

We should be able to get a version within the libs code but yes should be built properly.
GUI should ideally show version details for running project somewhere so we can get it when helping someone.

Do we not want a way to get the version of the engine and the libs at runtime?

I believe we should expose the version to the code. And we should expose not only a single version, but multiple ones! To quote Practical API Design Chapter 2: "The Motivation to Create an API",  page 21:

Each piece of a modular application has a version number, usually a set of natural numbers separated by dots, such as 1.34.8. When a new version is released, it should have a new and larger version number .... You can express dependencies on other components of the modular system by specifying the identification name of such a component and the minimal needed version.

Some versions of components can contain bugs that need workarounds. For this reason, a
secondary version—an implementation version—is usually associated with a component. In
contrast to the specification version, this is usually a string, such as Build20050611, and can
only be tested for equality.

E.g. it is OK to have Runtime.version type=..Engine and return "2024.4.2" or Runtime.version type=..Commit and return "1a0ae7c84d8d79c9b6d825c34557a5cd2ac97954".
However I am against exposing concatenated text messages that require parsing to be processed by a machine. It is a well known antipattern which has bitten many. See for example Practical API Design, Chapter 3: "Determining what makes a good API", page 31:

Beware of situations where there is no alternative to parsing text messages! If the information isn’t available in other ways, people will parse any textual output generated by your code. For example, this happened to the JDK’s Exception.printStackTrace(OutputStream).

Last, but not least I agreed to disagree with @radeusgd that exposing an API annotated with ## PRIVATE creates no obligations. It does! I can't force that policy to the whole libraries team, but I am ready to apply such policy when it comes to the Enso engine API (e.g. builtins).
Next time anyway gets an idea to modify a builtin, please involve @JaroslavTulach in the review.


thank you for this project!

I'm really glad for this project, sorry to spam issues I just wanted to buy you guys a beer.
@GitCash send 0.008 BCH to @fabxc and @Bplotka

@fabxc,@Bplotka

@fabxc,@Bplotka

This is so awesome to hear! (: Thanks!

Thanks :) Much appreciated.


Update ajax-chosen.js

There was a problem when " append options " to target select,
Especially when use class name to run script. e.g :
$(".chzn-select").ajaxChosen();
i've changed " select " with  " $this " to make it run correctly ..
and changed :
.trigger("liszt:updated");
To latest update of chosen ..
.trigger("chosen:updated");

Lets get some movement on this please.


Deploy eUPF with eBPF CNI (Cilium or Calico)

Acceptance criteria:

[ ] Enable Calico ebpf CNI
[ ] Verify UPF 0-scenario (both generic and native attach modes)
[ ] Make perf tests

well , ... i want to try it too 👍 and i will do it

Calico BPF dataplane doesn't support SCTP https://docs.tigera.io/calico/latest/operations/ebpf/enabling-ebpf#not-supported
Clilcim support SCTP in beta https://docs.cilium.io/en/latest/configuration/sctp/

after testing with Cilium, we have:

open5gs core start and works
gnb connects to AMF successfully
ue connects to upf and get IP address
traffic from UE doesn't pass to internet

# cilium monitor -t drop
Listening for events on 4 CPUs with 64x4096 of shared memory
Press Ctrl-C to quit
level=info msg="Initializing dissection cache..." subsys=monitor
xx drop (Invalid source ip) flow 0x0 to endpoint 0, ifindex 16, file bpf_lxc.c:1328, , identity 28789->unknown: <IP_ADDRESS> -> <IP_ADDRESS> EchoRequest
xx drop (Invalid source ip) flow 0x0 to endpoint 0, ifindex 16, file bpf_lxc.c:1328, , identity 28789->unknown: <IP_ADDRESS> -> <IP_ADDRESS> EchoRequest
xx drop (Invalid source ip) flow 0x0 to endpoint 0, ifindex 16, file bpf_lxc.c:1328, , identity 28789->unknown: <IP_ADDRESS> -> <IP_ADDRESS> EchoRequest

Calico BPF dataplane doesn't support SCTP https://docs.tigera.io/calico/latest/operations/ebpf/enabling-ebpf#not-supported
Clilcim support SCTP in beta https://docs.cilium.io/en/latest/configuration/sctp/

It is beta version.
Sorry but I have tried to simulate gnodeB pod with AMF pod and tried to communicate them. Unfortunately  nothing was done

Calico BPF dataplane doesn't support SCTP https://docs.tigera.io/calico/latest/operations/ebpf/enabling-ebpf#not-supported Clilcim support SCTP in beta https://docs.cilium.io/en/latest/configuration/sctp/
SCTP need for connection between gnb and AMF

the issue with cilium is about the multi-homing. I don't think that is supporting it


Adds Netstandard2.1 support.

Adds Netstandard2.1 support.
Allows a wider range of usage such as Unity 2018 and Xamarin projects.
If possible it would be neat to update the Nuget like previously.

I am not sure this is worth the hassle. NS2.1 is already getting dated, and there are some useful future features (e.g. SNI support) that this would make impossible. I'm also not fond of the amount of extra code this adds to maintain.


Add explicit timeout for subscriber creation

Codecov Report
Attention: Patch coverage is 66.66667% with 3 lines in your changes missing coverage. Please review.

Project coverage is 92.83%. Comparing base (9ead159) to head (f4fd297).

Files
Patch %
Lines

google_nest_sdm/google_nest_subscriber.py
66.66%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1029      +/-   ##
==========================================
- Coverage   92.97%   92.83%   -0.14%
==========================================
  Files          19       19
  Lines        1821     1829       +8
==========================================
+ Hits         1693     1698       +5
- Misses        128      131       +3

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


Adding auto start

The app needs to start automatically every time the Systems is started.

[x] look up, what possibilities are there for auto start
[x] evaluate the best way
[ ] implement autostart in its own project
[ ] migrate autostart to MADCAP

Further Pursued in #36


Add Docs about what IAM Permissions are Needed

Add Docs about what IAM Permissions are Needed in order to start the cluster. For example when permissions should I grant the user that I specify in the config?

As the CloudFormation stack creates an EC2 IAM Role for the cluster, you typically need a user with the Power User policy.
Also I suggest that these questions might be best directed to the AWS HPC forum, as they are not actual software issues in the CfnCluster code.
https://forums.aws.amazon.com/forum.jspa?forumID=192


Optimize  Facet and Table API's - Too Much Data is coming down.

For example we are getting all files in a sample.

Dave to elaborate requirements


Ready to make pull request

This pull request brings two new functionality, resize_open and resize_close.
Problem
The problems I would like to solve is the following.
Normally, if you close window D in the below configuration, the height of window D goes to A and C.
Actual behavior
---------------          ---------------
|      |      |          |      |      |
|      |  B   |          |      |  B   |
|  A   |------|          |  A   |------|
|      |  C   |    ->    |      |  C   |
|      |      |          |      |      |
---------------          |      |      |
|      D      |          |      |      |
---------------          ---------------

This, at least to me, is strange as I would expect the the height and to be evenly distributed as between B and C
Expected Behavior
---------------          ---------------
|      |      |          |      |      |
|      |  B   |          |      |  B   |
|  A   |------|          |  A   |      |
|      |  C   |    ->    |      |------|
|      |      |          |      |      |
---------------          |      |  C   |
|      D      |          |      |      |
---------------          ---------------

The same goes for opening a new window. For example, if you open toggleterm in vertical direction (windows D in the below figure), the initial windows will go out of proportion.

 However, I found out that it shares a lot of codebase with bufresize.nvim, thus I am adding this functionality in this plugin.
The two new functions are resize_open and resize_close. Below is the configuration to solve the problem above.
opts = { noremap = true, silent = true }
map = vim.api.nvim_set_keymap
ToggleTerm = function(direction)
    local command = "ToggleTerm"
    if direction == "horizontal" then
        command = command .. " direction=horizontal"
    elseif direction == "vertical" then
        command = command .. " direction=vertical"
    end
    if vim.bo.filetype == "toggleterm" then
        require("bufresize").block_register()
        vim.api.nvim_command(command)
        require("bufresize").resize_close()
    else
        require("bufresize").block_register()
        vim.api.nvim_command(command)
        require("bufresize").resize_open()
        cmd([[execute "normal! i"]])
    end
end
map("n", "<C-s>", ":lua ToggleTerm()<cr>", opts)
map("n", "<leader>ot", [[:lua ToggleTerm("horizontal")<cr>]], opts)
map("n", "<leader>ol", [[:lua ToggleTerm("vertical")<cr>]], opts)
map("i", "<C-s>", "<esc>:lua ToggleTerm()<cr>", opts)
map("t", "<C-s>", "<C-\\><C-n>:lua ToggleTerm()<cr>", opts)

resize_open: find the newly opened window that is in the current state but not in the registered state, adjust the proportion of registered windows accordingly, then apply resize to the registered windows. Should be use with block_register to prevent race condition
resize_close: find the newly closed window that is not in the registered state but not in the current state, adjust the proportion of registered windows accordingly, then apply resize to the registered windows. Should be use with block_register to prevent race condition

A complete list of functions are listed in the README.
With this setup, below is the new behavior.
https://user-images.githubusercontent.com/38927155/146653790-512c8ca5-8428-4874-bf2d-76fdf1957f5e.mov

Hi! I got this working with neo-tree's event_handlers config option. I just wanted to confirm if the following code snippet is a good implementation? I mean it works, but I think I don't fully understand when block_register should be called and why? I just assumed it should be on neo_tree_window_before_open event but I'm not 100% sure.
Considering these neo-tree events:

"neo_tree_window_before_open" Fired before opening a new Neo-tree window.

"neo_tree_window_after_open" Fired after opening a new Neo-tree window.

"neo_tree_window_before_close" Fired before closing a Neo-tree window.

"neo_tree_window_after_close" Fired after closing a Neo-tree window.

I implemented this working solution:
...
event_handlers = {
	-- See https://github.com/kwkarlwang/bufresize.nvim/pull/8
	{
		event = "neo_tree_window_before_open",
		handler = function()
			require("bufresize").block_register()
		end,
	},
	{
		event = "neo_tree_window_after_open",
		handler = function()
			require("bufresize").resize_open()
		end,
	},
	{
		event = "neo_tree_window_after_close",
		handler = function()
			require("bufresize").resize_close()
		end,
	},
},
...

Here's the before and after in that order:

Hi! I got this working with neo-tree's event_handlers config option. I just wanted to confirm if the following code snippet is a good implementation? I mean it works, but I think I don't fully understand when block_register should be called and why? I just assumed it should be on neo_tree_window_before_open event but I'm not 100% sure.
Considering these neo-tree events:

"neo_tree_window_before_open" Fired before opening a new Neo-tree window.
"neo_tree_window_after_open" Fired after opening a new Neo-tree window.
"neo_tree_window_before_close" Fired before closing a Neo-tree window.
"neo_tree_window_after_close" Fired after closing a Neo-tree window.

I implemented this working solution:
...
event_handlers = {
	-- See https://github.com/kwkarlwang/bufresize.nvim/pull/8
	{
		event = "neo_tree_window_before_open",
		handler = function()
			require("bufresize").block_register()
		end,
	},
	{
		event = "neo_tree_window_after_open",
		handler = function()
			require("bufresize").resize_open()
		end,
	},
        {
	        event = "neo_tree_window_before_close",
	        handler = function()
		        require("bufresize").block_register()
	        end,
        },
	{
		event = "neo_tree_window_after_close",
		handler = function()
			require("bufresize").resize_close()
		end,
	},
},
...

Here's the before and after in that order:

Hi @serranomorante, glad to see you got it working! Let me explain why block_register is necessary. First of all, we have state, state contains all the visible opened windows info (widths and heights). Using the default configuration, a state is registered on the events of WinEnter and BufWinEnter, essentially when you enter or open a new window.
So what block_register does is to prevent the state from being registered, even when WinEnter or BufWinEnter happens.
Below is a high level diagram demonstrating the what happens with or without block register. With block register, opening neotree will prevent
not trigger a state register. So when applying resize, the plugin knows that both A and B should occupy half of the space. After resize_open,
unblock_register is called and a new state will be registered (hence the state = neotree: 20%, A: 40%, B:40%).
Without block_regisiter
---------------         ---------------
|      |      |         |n |   |      |
|      |      |         |e |   |      |
|  A   |  B   |         |o | A |  B   |
|      |      |   ->    |t |   |      |
|      |      |         |r |   |      |
|      |      |         |e |   |      |
|      |      |         |e |   |      |
---------------         ---------------

before opening neotree:
state = A: 50%, B: 50%

after opening neotree (a new state is registered):
state = neotree: 20%, A: 30%, B:50%

after resize_open:
state = neotree: 20%, A: 30%, B:50%

With block_regisiter
---------------         ---------------
|      |      |         |n |     |    |
|      |      |         |e |     |    |
|  A   |  B   |         |o |  A  |  B |
|      |      |   ->    |t |     |    |
|      |      |         |r |     |    |
|      |      |         |e |     |    |
|      |      |         |e |     |    |
---------------         ---------------

before opening neotree:
state = A: 50%, B: 50%

after block_register:
state = A: 50%, B: 50%

after opening neotree (state stays the same as before as block register is on):
state = A: 50%, B:50%

after resize_open:
state = neotree: 20%, A: 40%, B:40%

Hope this help!

Thank you so much :sob:!! That make things more clear.


Potter/improve v2 connector docs

Hey @potter-potter it's quite old PR but I see you recently made commit here. It would be great to have stable and official docs to consult about connectors, since few people from deepsense are starting on migrating them right now. Do you have an ETA on when it could be merged? Of course we can look into it right now and it will help, but I'm not sure which parts are up to date, and which in the meantime became obsolete.

Hey @potter-potter it's quite old PR but I see you recently made commit here. It would be great to have stable and official docs to consult about connectors, since few people from deepsense are starting on migrating them right now. Do you have an ETA on when it could be merged? Of course we can look into it right now and it will help, but I'm not sure which parts are up to date, and which in the meantime became obsolete.

@hubert-rutkowski85 yes. Its here:
https://github.com/Unstructured-IO/unstructured-ingest/tree/main/docs


Rendering of alternate lines are blurry and not displayed clearly.

Attach (recommended) or Link to PDF file here:
Alternate lines in a PDF document shows blurry when viewed at a zoom level of 70%
The sample document will be uploaded by the client within a couple of hours. Request you to wait.
Configuration:

Web browser and its version: Any browser. Tested in Chrome
Operating system and its version: Any OS. Tested in Windows
PDF.js version: 2.5.207
Is a browser extension:

Steps to reproduce the problem:

Open the attached document
Alternate lines appear blurry when viewed on a monitor at zoom level 70%

What is the expected behavior? (add screenshot) No blurry lines.
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

The sample document will be uploaded by the client within a couple of hours. Request you to wait.

Please respect peoples time, since this is an open-source projects (where many of us are unpaid volunteers), by waiting until you've gathered all of the required information before opening an issue!

PDF.js version: 2.5.207

That version is no longer supported, please find the latest releases at https://mozilla.github.io/pdf.js/getting_started/#download

blur image.pdf
please find the attached document

I could see some blurriness in the text when reducing the zoom level even in the latest version. The document is uploaded. Can you please reopen the ticket?

WFM, when testing with the built-in PDF Viewer in Firefox 94.

I could see some blurriness in the text when reducing the zoom level

That's not actually text, but rather an image. Furthermore, the ISSUE_TEMPLATE is specifically asking for screen-shots since it's not at all clear what "blurriness" you're referring to here.

even in the latest version.

Such a statement is not helpful, since "latest" can mean any number of things. Hence why an actual version number is required.

The above is why I didn't re-open this issue, since I cannot reproduce the issue and given that it's still missing enough information to be actionable/valid.

I noticed that at 70% the entire page becomes a bit blurry, which is what I assume was meant here (but indeed, screenshots would have been good to confirm). I'm attaching my screenshots below:
80% is fine:

70% looks less sharp:

:

I guess this is simply due to everything being an image. I'm attaching my screenshots below:

Thank you!
In that case it seems that the issue is simply about the fact that downsizing of images may result in slightly different rendering at different zoom levels (depending on e.g. the particular downsizing algorithm used), since images will never look perfect when downsized (compared to e.g. rendering of vector-data).
All-in-all, closing as WONTFIX (or even INVALID) since this is more-or-less expected when downsizing images a lot.

@Snuffleupagus and @timvandermeij Thank you for your analysis and help. Appreciate that.


Add supported engines

Add node as engine and set supported version to be at least 0.10.26 and at most 0.10.x (excluding 0.10.34).

:+1:


Update docs (Table 18) - move transform to end

Fix the order of the transform algorithm within table 18, so that it appears at the end of the table, in alphabetical order.  The remainder of the algorithm names are sorted and it is extremely confusing when looking for this algorithm, since it is in an unexpected location.

Minor change, I know, but it was driving me crazy every time I tried to
look through the docs to find this...
On Tue, May 23, 2017 at 7:26 AM, Hartmut Kaiser<EMAIL_ADDRESS>wrote:

@hkaiser approved this pull request.
LGTM, thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/STEllAR-GROUP/hpx/pull/2649#pullrequestreview-39712954,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFuWFXOI741zcB3no0KmW7aE6r5_BxCEks5r8sJPgaJpZM4NjcwZ
.


http1: allow duplicated chunked header

Signed-off-by: Yuchen Dai<EMAIL_ADDRESS>Commit Message:
Allow transfer-encoding: chunked appears repeatedly in the header.
Additional Description:
Initially reported in https://github.com/istio/istio/issues/24753
I don't find RFC declare duplicated chunked as a failure.
I also confirmed by feeding curl with the duplicated transfer-encoding: chunked. No error is reported.
Risk Level: LOW
Testing: unit test
Docs Changes:
Release Notes:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]

I agree "chunked, chunked" is an error. So envoy is doing nothing wrong.
So the question is do we allow "chunked" body and sanitize "chunked, chunked" to "chunked"?
Happy to close if we don't need such a sanitize.

So the question is do we allow "chunked" body and sanitize "chunked, chunked" to "chunked"?

That would be the one option... but we don't know if that's really the case and if backend simply emitted duplicate headers and response is chunked once, or if response is incorrectly chunked twice (e.g. by multiple layers of HTTP proxies).
As such, I believe that the current behavior of rejecting responses with multiple transfer-encoding values is much safer.

but we don't know if that's really the case and if backend simply emitted duplicate headers and response is chunked once, or if response is incorrectly chunked twice (e.g. by multiple layers of HTTP proxies).

Make sense. Thanks @alyssawilk @PiotrSikora !