Add Kakaowork CLI

#7

Codecov Report

Merging #13 (b389802) into master (d86741e) will decrease coverage by 7.20%.
The diff coverage is 0.00%.

:exclamation: Current head b389802 differs from pull request most recent head 9a30919. Consider uploading reports for the commit 9a30919 to get more accurate results

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
- Coverage   83.56%   76.35%   -7.21%
==========================================
  Files           7        8       +1
  Lines         657      719      +62
==========================================
  Hits          549      549
- Misses        108      170      +62

Impacted Files
Coverage Δ

kakaowork/__main__.py
0.00% <0.00%> (ø)

kakaowork/command.py
0.00% <0.00%> (ø)

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 0e5ec8b...9a30919. Read the comment docs.


Finetune automation of local k8s deployment

Changes

Fixes bug in check-commit-format, so this action is no longer skipped on regular, non-merge commits.
Adds ingress access to the grafana dashboard so that it can be accessed without having to do port-forwarding. It is accessible through <ingress_ip>/dashboard. Username/password is still the default combination.
Finetunes the deploy.sh script. To deploy the remla-app application locally in minikube you only have to run ./deploy.sh. To run the script you need to first install helm and minikube. You can find the ip of the ingress through minikube service list and you can access the following three endpoints: <ingress_ip>/predict, <ingress_ip>/metrics, <ingress_ip>/dashboard. Keep in mind that /predict only accepts post requests so you can't test it directly in the browser, but you can use something like Postman.

After some issues relating to my VirtualBox, it ran perfectly. Tip for others: Make sure your VirtualBox is up to date :)


Columns containing question marks are rendered strangely

In my user model I have:
field :admin?, :boolean

This results in:

@hut8 can you try my pull request version and see if it fixes your issue?
Thanks


Add delete decoration functionality

I might have to figure out how to remove the ratings from users who have rated the decoration that is being deleted.
This is a job for future Ed


Rancheros ISO startup error  （level=error  msg=symlink /usr/bin/ros/  .... ）

RancherOS Version: (ros os version)
v1.0.3
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
baremetal, VMware esxi  platform and VMware Fusion or virtualbox
I install rancherOS system on the VMware esxi  platform and VMware Fusion or virtualbox,  The terminal is always jammed When the rancheros ISO  startup  ，       The error is as follows：

mmm, those errors are known, and have (now) been determined to be harmless (I've removed them in v1.0.4).

thanks!


Separate CXXFLAGS from LDFLAGS/LIBS for modules

Currently it uses MODFLAGS for both, and therefore clang on freebsd shows for every module:
Building module stickychan...
c++: warning: argument unused during compilation: '-L/usr/local/lib'
Linking  module stickychan...

Found by fred

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1387543-separate-cxxflags-from-ldflags-libs-for-modules?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

Fixed in CMake build


Add producer to Routing and Faulting engine

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Initializes the Producer for the routing and faulting custom device to send messages to all switch consumer custom devices.

The producer is initialized with all of the consumer names.
Input channels are set up so when value changes occur, disconnect messages will be sent followed by connect messages.
Initial state will be sent to all consumers once the logic for creating the connect messages exists.
During shutdown, disconnect all and shutdown messages are sent to all consumers.

Why should this Pull Request be merged?
This is the basis for all communication between the routing and faulting custom device and any SLSC Switch custom devices in the system.
What testing has been done?

Ensured all SLSC Switch consumers are correctly enumerated.
Ensured shutdown of the producer is handled correctly. The SLSC Switch engine may need to remove the check for shutdown in the consumer loop to ensure it handles shutdown correctly.
Tested the writing outputs works correctly by manually creating the channels and hard coding indices. Once the status channels are added to initialization of the custom device and compiled correctly, channel writing will just work.

[ ] Should Shutdown Producer.vi run unconditionally, instead of checking incoming error? We stop the data loop in the case of an error (e.g. if Engine Main.vi errors), but the producer will not shut down.

Should Shutdown Producer.vi run unconditionally, instead of checking incoming error? We stop the data loop in the case of an error (e.g. if Engine Main.vi errors), but the producer will not shut down.

Yes, it should run unconditionally. Also, Send Shutdown All.vi should be pulled outside the loop and run just before Shutdown Producer.vi. It should also run unconditionally.

[ ] RT Driver VI.vi: Clean up wiring. Boolean wire overlaps status unbundle. Engine data should enter/exit on left/right, not top.

[ ] Send Shutdown All.vi: Do not eat the errors. Merge the errors in to error out.

[ ] Update Initial States.vi, Update States.vi: Why do we cache the disconnect and connect messages in engine data? Create and send the message without caching the message. The only thing we should cache is the previous routing channel value. The messages are only used within the same loop iteration and do need to be stored for the next iteration.

https://github.com/ni/niveristand-slsc-switch-message-library/pull/6

Create an issue to remove connect and disconnect messages from engine cluster.


Error in converting googleapiclient.errors.HttpError to string

try:
    results = ga.core.query.get()
except googleapiclient.errors.HttpError as err:
    print(err)  # TypeError: the JSON object must be str, not 'bytes'

    print(json.loads(err.content.decode('utf-8'))['error']['message'])  # works

Environment:

Python 3.4.3
google-api-python-client==1.4.0
httplib2==0.9.1
oauth2client==1.4.7
six==1.9.0
uritemplate==0.6

Looks like 0915761b fixed this issue. When is the next release coming out?

It looks like 1.4.1 contains the fix.


Line wrap issues

at d1083fb
Line wrap works while composing, but is broken after posting, then fixes itself after a while.

Then a bit later:

Alright, I've pushed a fix for this in latest, let me know if that fixes it for you?


⚠ Avatar API Endpoint has degraded performance

In bc55c3e, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 2520 ms

Resolved: Avatar API Endpoint performance has improved in de88ac6 after 9 minutes.


Docker: Containerized deployment on Virtual machines

Docker: Containerized deployment on Virtual machines

Please ignore this issue. It was supposed to be created on my repo.
Thank you for understanding.


Component Added: Interactive Button

Pull Request: Interactive Button
Changes Made

Added support for .jsx files in the project and customized color options in tailwind.config.js.

Modified tailwind.config.js to support .jsx files.
Customized color options to enable more flexibility in styling.

Added a new component, Button.jsx, to the components folder. This component provides customizable buttons with interactive features.

The Button.jsx component can be used to create buttons with various styles and optional icons.

Renamed Homepage.js to Homepage.jsx and added examples of how to use the Button.jsx component.

Created a new Homepage.jsx file.
Demonstrated the usage of the Button.jsx component with different configurations.
Added an icon asset, arrow-right.svg, to showcase the button's icon functionality.

Related Issues
New Component Suggestion - Interactive Button
Proposed Changes

Enhance the project's flexibility by supporting .jsx files and providing customizable color options in tailwind.config.js.
Introduce a versatile button component, Button.jsx, that can be easily customized for different use cases.
Update the Homepage.jsx file to demonstrate the usage of the Button.jsx component and showcase its icon functionality.

Screenshots

Additional Notes
@vaishnavi-3969
Please review this PR and provide your feedback. Your input is highly valuable for ensuring the quality of the project.
Hacktoberfest
To make this PR eligible for Hacktoberfest, please consider labeling it as hacktoberfest-accepted once reviewed and approved.

Your PR has been reviewed and approved, @suryanshsingh2001! 😄 Thank you so much for your valuable contribution ❤ to the repository. Your efforts are greatly appreciated.


Possible Fix for #4541

Possible Fix for #4541
Reset-AADPassword playbook not working with default OOB template
Required items, please complete

Update PS script
Updated the logic app / playbook definition.

@anki-narravula & @v-spadarthi  - Please let me know for further changes to this.

@lior-tamir & @BenjiSec - Could you please help merging this !

template error

@samikroy - I'll have to change few things and will make new PR. Need to add control if user doesn't have a manager and will change connection for checking manager to HTTP. Also this is template so need to change template versioning as well as add release notes.

@BenjiSec - Thank you for sharing this.


[log] polish disable_existing_loggers

Polish disable_existing_loggers(). Make its API clearer.
Rename colossalai.logging.logging to colossalai.logging.logger. In colossalai/logging/__init__.py, logging is imported. We actually want to import standard library here, but there is colossalai/logging/logging.py, which makes me confused.

@ver217 , I think @feifeibear  has written a singleton meta class, can you refactored the current singleton logger with his implementation?

@ver217 , I think @feifeibear has written a singleton meta class, can you refactored the current singleton logger with his implementation?

This is a little different from the standard singleton. For loggers, every "name" corresponds to a "singleton". Maybe we can optimize  it in next MR.

LGTM.


Adding "football" terms to soccer pitch

Hi,
We like to call it football instead of soccer, so I have added an extra search term to make this possible.
Thanks :+1:

Looks good, thanks!  ⚽


Not sorting properly by 'line'

When sorting by 'line', todo-show appears to be sorting alphabetically instead of numerically. E.g.:
12
156
2345
4
87
9
Instead of:
4
9
12
87
156
2345

Thank you. Will be included in next release.

Thanks for addressing this so quickly, and for creating this package.


Interested in Mangacraft anyway to get Access?

Hi guys!
I'm interested in mangacraft, I've been searching online for it but it looks like it's been abandoned. Does anybody know how I can get access to it, any information would be greatly appreciated. Thank you!

I thought it got discontinued. Anyway, you can colour entire pages of manga if you are good with this AI.

您好(*?0?7▽｀)ノノ青弦已经收到您的邮件啦！请耐心等待，10个工作日内会给您回复w

hey! it's been close to 10 days, was wondering if there was any response to this, thank you so much for your reply! :)

hey, a reply would be greatly appreciated, I know you're busy with the SEPA launch so I 100% understand. Just wondering if you got my last reply, thank you :)

This qinxian233 user always says he will reply in 3 days, but he never does.

Hi all. (1) I do not know who is qinxian233. She/he is not a team member of S2P. (2) We have given up the support for Mangacraft several years ago, but hi ecchirealm, I did get your messages!

Hi @lllyasviel can we get the exact date of SEPA v5. April is coming to an end, I hope you guys release it soon but I'm not forcing it. The delay of release date is your right.
With respect :))

hi @lllyasviel a response would be appreciated :)

hello bumping in case illyasviel forgot about this

您好(*?0?7▽｀)ノノ青弦已经收到您的邮件啦！请耐心等待，10个工作日内会给您回复w

hey

just use s2p, it works fine.

hey

Or try using the way back machine


add feature allow date by regex

I want allow to choose some day by dynamic,for example choose the last day of quarter every year,so I  add this feature.

any docs/examples available for this feature?

@xdan How to allowDateRe and allowDate add docs
{format:'Y-m-d',allowDateRe:'\d{4}-(03-31|06-30|09-30|12-31)' }
@1allen

Hey. Added doc.tpl file in the repository . From this information goes directly to the documentation on the website .

@1allen  #391


use stack allocated arrays in CommandBuffer in vulkan backend

Fixes #3309

PR checklist:

[X] make succeeds (on *nix)
[ ] make reftests succeeds
[X] tested examples with the following backends (gl, vulkan compilation only)
[ ] rustfmt run on changed code

there is this SmallVec left:
https://github.com/gfx-rs/gfx/blob/210b54f225a460628d700b4562a86331c6d22409/src/backend/vulkan/src/command.rs#L49
but I couldnt figure out the return type without it
it should be something like Map<T, SomeClosure>, but idk how the closure is typed
rustc says something like:

found struct std::iter::Map<_, [closure@src/backend/vulkan/src/command.rs:59:14: 70:10]>

which doesnt help :shrug:

@khodzha oh, this one is simple, actually. We don't need to return a stack-allocated vector from this function, we want to return an iterator:
fn map_buffer_image_regions<T>(_image: &n::Image, regions: T) -> impl Iterator<item = vk::BufferImageCopy>

And then after invocation we'd do stack allocation for the results (based on the length of the original iterator), to pass down a slice to Ash

there are smallvecs in BarrierSet and other places still

also there is this bind_vertex_buffers which does
https://github.com/gfx-rs/gfx/blob/210b54f225a460628d700b4562a86331c6d22409/src/backend/vulkan/src/command.rs#L539-L543
and unzip() automatically collects here :shrug:

ok, it sounds like we can follow-up with more changes then :)

bors r+

is there something to be done about smallvecs embedded into structs? or we just leave them be?

uh, it's not clear to me how we can resolve fn destructure_barriers gracefully

there is also this struct https://github.com/gfx-rs/gfx/blob/210b54f225a460628d700b4562a86331c6d22409/src/backend/vulkan/src/device.rs#L462-L466


how to use pjf fuzz a json parse binary ?

i  am learning fuzz. when i try use pjf to fuzz pjf.
[~/fuzz]$ pjf --P "./jq" -p "-r ."

I am trying to fuzz a binary https://github.com/amzn/ion-c. Is there a way to fuzz into a file and then run the ./jsonparser on the file?

pjf --auto --no-logo > f
while [ $? -eq 0 ]; do
      echo "fuzzing"
      pjf --auto --no-logo > f
     ./ion process f
done
echo "found crash"


'spotify_to_ytmusic' is not recognized as an internal or external command, operable program or batch file.

Make sure you can execute Python scripts on the CLI.
https://realpython.com/add-python-to-path/

@sigma67 What path I add to PATH ?


NO sonoff.update_consumption service available

Hi,
I'm not able to call the service as per your documentation as i don't see it available in the developer tab.
I'm running HA in Hassio environment and your module is working well to get the current power, voltage from Sonoff POW R2 device.
versions:

this is data from my dashboard

this is the sensor configuration:
sensor:

platform: template
sensors:
sonoff_pow_today_consumption:
friendly_name: Today consumption
unit_of_measurement: kWh
value_template: "{{ state_attr('switch.sonoffpowercamera', 'consumption').0 }}"
sonoff_pow_ten_days_consumption:
friendly_name: 10 days consumption
unit_of_measurement: kWh
value_template: "{% set p=state_attr('switch.sonoffpowercamera', 'consumption') %}{{ p[:10]|sum if p }}"
sonoff_pow_consumption:
friendly_name: Consumption
unit_of_measurement: Wh
value_template: "{{ state_attr('switch.sonoffpowercamera', 'power') }}"
sonoff_pow_volts:
friendly_name: Volts
unit_of_measurement: V
value_template: "{{ state_attr('switch.sonoffpowercamera', 'voltage') }}"
sonoff_pow_instant_v:
value_template: "{{ state_attr('switch.sonoffpowercamera', 'voltage') }}"
sonoff_pow_instant_a:
value_template: "{{ state_attr('switch.sonoffpowercamera', 'current') }}"
sonoff_pow_instant_w:
value_template: "{{ state_attr('switch.sonoffpowercamera', 'power') }}"

can you please help?

I found that the data are available only via cloud.
i changed the cofiguration to cloud and i see the consumption service.
i would reccomend to improve the documentation for that.


Migrate to nimib 0.3 - BlockMaker

The hardest parts are migrated and are less hacky now. fragmentCore, fragmentStart and fragmentEnd are still a bit hacky but I think this is necessary for it to work.
~There are still a lot of nbText: *html code* everywhere but they aren't important right now as they work fine. Also has some problems with nim-mustache not liking HTML and turning < into < for example. Will have to look into if we can escape the tags somehow. nbText goes through the markdown processor which must somehow escape it, because it works.~ Found it! I have seen you prefixing fields with & in the templates but didn't know what they did. Seems like it's escaping the text :D
Overall it was a quite smooth transition and implementing animateCode was a breeze by reusing the functionality of nbCode :D
@pietroppeter Would appreciate your eyes on this when you have the time. Especially if I made something more convoluted than it had to be done :D
TODO:

[x] One slide to rule them all (remove slideRight, slideLeft)
[x] Update examples
[x] Update README
[x] Skip the initReveal call entirely and just dump everything in global?

Found it! I have seen you prefixing fields with & in the templates but didn't know what they did. Seems like it's escaping the text :D

yep indeed that is the case. In mustache you can use & or a triple mustache to escape the content. I started at some point using exclusively the & since I think it make it more easy to spot and it is a very important detail (might need to highlight it somewhere in nimib docs)

~Skip the initReveal call entirely and just dump everything in global?~ Must keep this adding {.experimental: "flexibleOptionalParams".} to the user file

just saw this and I have a review comment that was suggesting to dump everything in global (since with last PR I did that for nimib). Does this mean that current devel  for nimib will not work for either 1.4 or 1.6 or that it has some kind of issues?

the {.inject.} for the variable shouldn't be needed

I was trying to understand this comment to learn something more about templates but I was not able to find the correct commit that makes it clear. Also rather weirdly, comments in this conversation start duplicating themselves at some point...

I was trying to understand this comment to learn something more about templates but I was not able to find the correct commit that makes it clear. Also rather weirdly, comments in this conversation start duplicating themselves at some point...

Haha yes, it is really messy 😅 I had to change it multiple times because I hadn't taken edge cases into consideration so there isn't a single commit 🙃 I don't understand it either tbh, all I know is that it doesn't work without it 🤷

@pietroppeter I've found the problem I'm getting with -d:nimibPreviewCodeAsInSource now. It turns out to be related to rawBlock here: https://github.com/HugoGranstrom/nimib-reveal/blob/1b2b7d99a20042f869760df8a41e0091d26217a7/nimiSlides.nim#L132
When nimib is creating the block, it now always parses the code of the block if I understand it correctly? In this case as the call to rawBlock is made inside nimiSlide itself, it will try to look at line 132 as expected. Problem is that getCodeAsInSource doesn't know that and tries to find line 132 in the user's file instead. Hence my errors previously.
Either we become smarter about which files to look in, or we become selective about which blocks have to actually read the code. What do you think?

@pietroppeter I've found the problem I'm getting with -d:nimibPreviewCodeAsInSource now. It turns out to be related to rawBlock here:
https://github.com/HugoGranstrom/nimib-reveal/blob/1b2b7d99a20042f869760df8a41e0091d26217a7/nimiSlides.nim#L132
When nimib is creating the block, it now always parses the code of the block if I understand it correctly? In this case as the call to rawBlock is made inside nimiSlide itself, it will try to look at line 132 as expected. Problem is that getCodeAsInSource doesn't know that and tries to find line 132 in the user's file instead. Hence my errors previously.
Either we become smarter about which files to look in, or we become selective about which blocks have to actually read the code. What do you think?

this is a tricky one. From this use case, it seems that we might need to build blocks that do not automatically read the code (either from source or from AST) so we should provide a new newNbBlock mechanism which does not do any code processing (name to be found).
For the future instead I realized that the use you make it inside slide is due to the fact that we do not have (yet) a container block and when that is materialized those begin and end of section should be likely done as template for the container block.

Saw your commits on local reveal and wanted you to point out something that might be interesting for this and possibly other aspects of configuration. Nimib handles its (very basic currently contains only srcDir and homeDir) configuration file nimib.toml with the library from status toml_serialization (see nimib/config.nim). The setup in a way that other themes can take advantage of this configuration file.
for example you could have a configuration file with a [nimislides] section like so:
[nimislides]
localReveal = "assets"

inside your theme function you would add something like:
let nimislidesCfg = Toml.decode(nb.rawCfg, NimislidesCfg, "[nimislides]")

if nimislidesCfg.localReveal != "":
  nb.useLocalReveal(nimislidesCfg.localReveal)

where you would have defined a type:
type
  NimislidesCfg* = object
    localReveal*: string

details of the code above might not be correct but hopefully the idea is conveyed.
I am working for nimibook to start using this config feature.

@pietroppeter Do nbText need readCode = true? I left it so because you had old tests that expected it. I suspect my failed attempt at fragmentList is because of that exactly, that I use nbText inside the template and it in turn tries to read that code instead

that is a good question. the reason why I was expecting nbText to readCode is that in general that was the default before readCodeAsInSource. With readCodeAsInSource, reading code might cause issues when used in a template so, yeah, either we find a way to make readCodeAsInSource to work also inside templates (no idea how at the moment and what would be the issue) or we might want to limit reading code to the essentials. Or... mmh, I am getting an idea where we might be able to decide to disable readCode automatically when we are not in the mainfile (I think it could be doable by checking file where is instantiated against what nb object thinks about that)...
Anyway, I can see how that could have caused you the issue in the past, is it something that you have solved now in this codebase or you are asking because you would want to maybe see a change?

OK yes that makes sense. Your idea of checking if the files match sounds like it could work quite well 👍

Anyway, I can see how that could have caused you the issue in the past, is it something that you have solved now in this codebase or you are asking because you would want to maybe see a change?

I have templates that I would like to use nbText in (e.g pass in seq[string] and run nbText on each of them wrapped in a fragment, see recent fragmentList commit). I could of course solve this for the moment by making my of nbTextNoReadCode, but in the future and for future theme-makers it has to be addressed. And changing nbText to not read the code is a simple fix until we try out your more ambitious idea of checking if the files are the same.

ok you have conviced me it is something we need to address. Idea could be to make indeed readCode false by default in nbText (another option would be to provide with a nbText(readCode=false): "bla bla bla" api). I added this as a todo item for nimib0.3: https://github.com/pietroppeter/nimib/pull/81 I will update also here when I will have this completed

Thanks :) What are a use-cases for wanting the code of a nbText block? Say we have this:
var lines: seq[string]
nbText:
  lines.join("\n")

I can't come up with any at least. If someone wants it, they probably want to roll their own block entirely and make other changes as well. At least that's how I see it. So just making it the default and not offering a separate overload would be my choice if it was up to me

One use case would be to be to have a web interface like a Jupiter notebook where you can change a cell from rendered output to source and viceversa. Note that there is nothing like that currently. The other use case I need to check is the markdown cheat sheet which does show the source (but uses anyway a custom block). I tend to agree that currently making nbText by default not reading the source might need the best option, but I am not yet completely sold

That is actually a pretty dope use case 😎 It sounds like it would need some pretty big changes regardless to make something like that work and this is a very minor change compared to those. Do as you see fit, it doesn't hurt adding that overload now, but it could otherwise always be added in the future when needed.

With this implementation the typewriter will compile more or less the same Karax code for every fragment?
Wouldn't be better to have some JavaScript (added with a nb.useTypewriter) that will do that for every paragraphs with (for example) a typewriter class?

With this implementation the typewriter will compile more or less the same Karax code for every fragment?

Indeed.

Wouldn't be better to have some JavaScript (added with a nb.useTypewriter) that will do that for every paragraphs with (for example) a typewriter class?

I see what you mean, but I don't see how that would simplify things really. I prefer atomic widgets over using shared code that must interact between widgets. Also then we would need to use the nbCodeToJsInit + addCodeToJs API which also would require us to insert a addToDocAsJs at the end requiring us to add a nimiSlidesEnd template or something like that that the user must remember to run before running nbSave. Or am I complicating things again?

Ok, I re-read your message and you propose something like this?

Type this text

And then the javascript looks for all
 tags with the typewriter class and associates each one with an object holding its id and fragmentIndex. Maybe could work but I wouldn't hide it behind a nb.useTypewriter, there's no point in doing that.

Well the nb.useTypeWriter would be to add a block that contains the code to convert to javascript, not to be used for the single class instance.

OK I understand what you mean then, it would require a few {.exportjs.} and {.importjs} to make it work. But I'm against the general use of the useSomething API. The user shouldn't have to remember to call a template to setup a widget just to use the widget if it is possible to avoid. Otherwise, we might end up with code like this:
useWidget1()
useWidget2()
useWidget3()
useWidget4()
useWidget5()

just to use a couple of widgets. For the user, it only brings more complexity. Do you understand my reasoning?

Yes, I see, although html files being very big because they have a lot of JavaScript inside is also a issue. Anyway better to start having the widgets and after that improving on these details. :)

Yes, I see, although html files being very big because they have a lot of JavaScript inside is also a issue.

That's a good point that the file size may grow a bit if we have to repeat the "boilerplate" code compiler creates each time. But for karax components that is a necessary evil as they have to be compiled in separate files. In this case karax is overkill of course and it could in theory be merged with other codes.

Adding a call to closure-compiler if it is available should be trivial to implement in nimib for example.

I tried it and totally raw the code size is 200kb for one typewriter. Gzipped it was 33KB (and this is what we should look at as pages often are gzipped nowadays). Compressed and gzipped is was 24KB so not a huge difference, but it means we could fit 40 karax components in 1MB roughly. So unless you are going haywire with karax components we should be pretty safe.


Fix for required modules (v2)

This implements the changes in the repo:
https://github.com/vitreo12/OmniModulesProofOfConcept

Finally merging!


[Search Results] Inconsistency between the names of the buttons with those that should be according to file "Localization"

Environment: OnePlus 7
Reproducible: always.
Build found: 1.0.177.
Preconditions
User logged in.
Car app is opened.
Existing ride is found.
Steps to reproduce
Option panel:

Click on 'Request' button.
Pay attention to the "With the Previous Filters" and "With New Filters" options.

Confirmation pop-up window:

Click on 'Request' button.
Click on 'With New Filters' option.
Pay attention to the "Yes, Create" and "No, Go back" buttons.

Actual result
Options and buttons are named incorrectly.
Expected result
Options should be named as "With the previous filters", "With new filters" and buttons as "Yes, create" and "No, go back".
User story and test case links
E.g.: "User story #214
Labels to be added
"Bug" ("bug"), Priority ("pri: ")

Bug fixed.


Now building feedChanges.js via python script on build

Hey guys,
This seems to work for me, sorry for the delay in getting it done!
The python script is now going through all features in the features directory, (ignoring 'shared') scanning each .js file with a RegEx to look for the line that roughly looks like:
ynabToolKit.budgetProgressBars = new function ()  {

I tried to make the RegEx pretty forgiving but still ensure it only finds the correct line.
It then grabs the function name out of it and generates this into the feedChanges.js file with the observe call afterwards, wrapped in a try catch block. It uses a python set instead of a list (array) because that way each .observe is only called once per feature, even though in the case of budgetProgressBars there are 3 files that match.
@Niictar, could you test and ensure this is doing what you expect before I merge into master? I tested and it looks like for me it's putting everything in feedChanges that's already there, just in a different order.

@blargity
Sure. I'll take a look. I won't be in front of my computer till the tail end of the weekend, but I'll sit down and experiment with it before to long.

Well, a change of plans got me to look at this much sooner than expected. Anyway, this looks good to me. I followed up with this by making PR #147 that refactors the reconciled text color feature to use the MutationObserver and the build worked as expected.
Someone else may want to review this, but nothing stands out to me as a problem. 👍

Cool, thank you!
I'll merge it in and if there's a new issue I'll address that separately.


blaze: init at 0.8.2 - work in progress

Requires #8765, #8763 and #8737.
Maybe next time when I have a case with dependencies like here I should put the commits in a single PR?
Cherry-picked the other commits and tested with nox-review.

There are some optional dependencies as well that I did not include here yet. However, I think it is best if by default those are installed as well. It's not really clear how each optional dependency is used.
Add a flag optional=true in this case?

Well, you choose. If you need those optional dependencies, just include them.

Alright, I'll add them then. Thanks.

@lethalman  @pSub can this be merged?


how to change the section header name

just messing around with some stuff and idk but I've looked through this entire src and there's no way to change the section without it crashing

having the same problem I'm getting:
[!] Could Not Find ."SECTION_NAME" Section ! (main:56)
where "SECTION_NAME" is the section name I choose


Publish MSI packages to WinGet

Subj

Initial PR: https://github.com/microsoft/winget-pkgs/pull/94206


os-hardening is not working in Ansible 2.9

I am newly using Ansible 2.9 on my new computer.
I used to use the OS-hardening script for my servers but its not working any more on Ansible 2.9
fatal: [ham-01]: FAILED! => {
"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'os_family'\n\nThe error appears to be in '/Users/keyvan/ansible/environment/roles/ansible-os-hardening/tasks/hardening.yml': line 2, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n---\n- name: Set OS family dependent variables\n  ^ here\n"
}

The problem happened when you are not using data gathering and the gather_facts: False
to solve the problem you can enable gather_facts: True or using the minimal one:
gather_subset:
- min


docs(fontawesome) : Add documentation for using Angular -fontawesome

Fixes #13018
Adds the documentation for recommended official library and also updates the npm dependency for the current version of font-awesome.

Hi, thanks for this however the wiki pages are currently being deprecated.
See https://github.com/angular/angular-cli/pull/13366


[backport] Fix typo in v2 Upgrade Guide

Backport of #5771

Jenkins failures are unrelated to the PR.


trailing slashes needed after resource name

We need trailing slashes after resource names, or close sends us redirects to the version of the api call with the trailing slash -
utter insanity

@seddy Confirmed


Add readthedocs config file

This is required nowadays: https://blog.readthedocs.com/migrate-configuration-v2/

Build passed:

https://readthedocs.org/projects/baseplate/builds/23353575/
https://baseplate--825.org.readthedocs.build/en/825/


BUG: DB connection encoding / collation fix.

Fix for https://github.com/silverstripe/silverstripe-framework/issues/9160

Didn't check yet, I only tested it with my test case (Fluent + History tab).

@dnsl48 Added the unit test and one suit is passing, the others are failing.

Looks like the passing test just does not run the framework (failing) tests, that's why it's passing.

I think I may have tried this fix too initially. My guess it's not working because it may require some extra server-side configuration changes (as per the comment)

Ok, will investigate this further.

@dnsl48 Pushed up updated unit tests which are now all green. I changed the unit tests to check for the case which was causing the issue as opposed to checking DB connection settings. This is more end-to-end test approach.

I changed the unit tests to check for the case which was causing the issue as opposed to checking DB connection settings

Haha, that's good, but I'm not sure that's fair :D
If the bug is not with the actual collation, but rather with the settings, we should at least add the test that verifies it.
For example, we could add a test for ordering that behaves differently between utf8mb4_general_ci and utfmb4_unicode_ci and validate that regardless of what collation is returned by connection settings, the ordering is still correct.

@dnsl48  That's what this test already covers. The query contains = condition which will throw if values on both sides have different collations (the default collation being utf8_general_ci). Try running my unit test without the fix and you will see that it will throw.
Isn't this the recommended way how to fix bugs? Write a unit test which reproduces the observed issue which fails and then provide a fix for it? My unit test is a simplified version of an actual query which is used to populate history tab. This was the place where we observed the issue.

Fair enough. I'll play with the fix some time this week.

Sorry for the delay. Yes, I've had a dig into it and I can confirm that it's true that mysqli->get_charset()->collation has a bug there.
The patch for MySQLiConnector in this PR is unnecessary, everything already works fine. I'm going to amend the tests so that we account for the bug with mysqli->get_charset()->collation, document it and then I think we can unblock the original issue.
Thank you for looking into it! I'll be working with the original PR and rewrite the tests to cover the actual collation behaviour rather than what's returned by mysqli->get_charset()->collation.


Network policy with multiple selectors does not work with IPv6 cluster

I am trying to test out the network policy with multiple selector on a calico IPv6 cluster but it seems not working.  At this point, all pod should access the db svc
kubectl exec -n default <APP POD NAME> -- nc -v -w 2 db-tnioue.default 6379

# Now apply the following network policy to the cluster
kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
  name: redis-allow-services
spec:
  podSelector:
    matchLabels:
      app: bookstore
      role: db
  ingress:
  - from:
    - podSelector:
        matchLabels:
          app: bookstore
          role: search
    - podSelector:
            matchLabels:
              app: bookstore
              role: api
    - podSelector:
            matchLabels:
              app: inventory
              role: web

# Test out the nc connection again, the pod with prefix "other" should not work and other app should work
kubectl exec -n default <APP POD NAME> -- nc -v -w 2 db-tnioue.default 6379

Note: This test works perfectly in Calico IPv4 cluster.
Expected Behavior
pod add with app:other label will not work but the rest of app will work
Current Behavior
app which is allowed in the network policy cannot talk to the db svc
Possible Solution
Steps to Reproduce (for bugs)
See description
Context

Your Environment

Calico version: 3.6.1
Orchestrator version (e.g. kubernetes, mesos, rkt): k8s 1.12.6
Operating System and version: ubuntu 18.04
Link to your project (optional):

app which is allowed in the network policy cannot talk to the db svc

None of the other applications can talk to the db svc? Or do some work and other not?
Have you checked to make sure that applications can talk to each other even with no policies defined?

@caseydavenport yes, I have checked. If I deleted the policies and it all works fine.

@kahou82 just had a thought - did you modify the manifest to set this to true?
            # Disable IPv6 on Kubernetes.
            - name: FELIX_IPV6SUPPORT
              value: "false"

Have you verified that the pods, nodes, and services are all using IPv6? Doing a kubectl get <resource> -o wide should show those.

It has been 25 days with no response so I'm going to close this issue for now. If you can respond with the answers to Casey and I's questions we will reopen the issue.


[LFT Term 3]: The checksum check of the three-party dependencies

Enhancement
The checksum verification of the dependencies in kpm has not been completed, and this part needs to be redesigned and completed.
PreTest
A paper work

A technical proposal for common package management tools checksum checking such as cargo, npm, go. mainly includes:

The main purpose of checking checksum

Related to the checksum check function

To implement the checksum check, which parts need to finished

Combined with kpm, which functions of kpm need to add checksum

For the existing kpm dependencies, we need a solution that does not break compatibility for starting this feature

hey i would wish to work on this issue under lfx mentorship, are there any prerequisites or any tasks that i need to complete for the issue

Hey @zong-zhe @AkashKumar7902 . Any communication channels to connect with you. I started on pretest mentioned. It will be great to connect with community too.

Hey @varshith257 👋
You can connect with us on the slack channel. https://github.com/kcl-lang/community

Looking forward to making contributions for the Fall term and possibly completing pre -test with some guidance (if needed ) :)
Thanks1

hewyy @Peefy  is the issue still open to be worked over?

Hi @zong-zhe,
Should I create a pull request for the proposal using a README.md file or a docx/pdf file?
Thank you.

Hello everyone! I'm excited to join this community and am looking forward to making contributions for the Fall term. I'm currently working on a pre-test. I'd appreciate any guidance or suggestions you can offer to help me navigate and contribute effectively. Thanks!

Hi @NishantBansal2003 @varshith257 @Gmin2 😄
I need these information from you until Aug 13 5:00 PM PDT

Full name (as listed on https://mentorship.lfx.linuxfoundation.org/)
The email address
The GitHub handle

I need these information from you until Aug 13 5:00 PM PDT

Full name (as listed on https://mentorship.lfx.linuxfoundation.org/)
The email address
The GitHub handle

Full name: Nishant Bansal
Email address<EMAIL_ADDRESS>GitHub: https://github.com/NishantBansal2003

Full name: Mintu Gogoi
Email Address<EMAIL_ADDRESS>Github: https://github.com/Gmin2

@zong-zhe
Full Name: Vamshi Maskuri
Email<EMAIL_ADDRESS>GitHub : https://github.com/varshith257


Greenkeeper/nsp 3.2.1

Pull Request Test Coverage Report for Build 24

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

Totals

Change from base Build 17:
0.0%

Covered Lines:
12

Relevant Lines:
12

💛  - Coveralls


This is a question for beta.
This seems to be an issue in the current passport service (as per this tweet), and it could be more of an issue for older people more like to have white hair.

@sanjaypoyzer Is this a question for LAs or IDPs?

@anthonylord More for LAs, but would be great if IDPs are thinking about this too!


ce no translate products

Can you reproduce this issue on default Wordpress theme (eg Storefront)?
Can you reproduce this issue when all other plugins are disabled except WooCommerce, Polylang and Hyyan WooCommerce Polylang Integration?
What product versions and settings are you using when this issue occurs?

PHP:
WordPress:
WooCommerce:
Polylang: [state if using Polylang PRO]
Hyyan WooCommerce Polylang Integration:
Browser:

Steps to Reproduce

What I Expected
What Happened Instead
WordPress Environment

```
Copy and paste the system status report from **WooCommerce > System Status** in WordPress admin here.
```

Please follow the getting started guide at:
https://github.com/hyyan/woo-poly-integration/wiki/Getting-Started
and if you still have a problem, report with more details.


Memory Issues

First up, thank you for your work and the results from BERTopic topic modelling works as I expected with this vectorizer. However I am running into out of memory issues in both Google Colab and Kaggle on my custom dataset, about 7500 documents. I do not have any paid subscription to Google Cloud Platform or Colab Pro so it is not an option to run my codes using those. Is there any tricks or tips to optimise this vectorizer on large datasets? Thank you

I encountered the same issue with BERTopic using a large dataset. The way BERTopic uses the vectorizer somehow results in huge memory consumption. I suspect the reason for this is that BERTopic passes the concatenated documents of a topic as a huge string to the vectorizer and spaCy can't handle such a large string. Unfortunately, I do not have a satisfactory solution for this problem currently. As soon as I have some time to spare, I will take a closer look at the problem.

I encountered the same issue with BERTopic using a large dataset. The way BERTopic uses the vectorizer somehow results in huge memory consumption. I suspect the reason for this is that BERTopic passes the concatenated documents of a topic as a huge string to the vectorizer and spaCy can't handle such a large string. Unfortunately, I do not have a satisfactory solution for this problem currently. As soon as I have some time to spare, I will take a closer look at the problem.

I am also facing the same memory problem with large dataset. Secondly, it becomes quite slow on large dataset. I have combined keyphrasevectorizer with keybert. Any help is very much appreciated!

Solved with the v0.0.12 release.


Revert "Switch quicksort pivot selection strategy to random

Temporary "fix" for https://github.com/TheAlgorithms/TypeScript/issues/169 until someone debugs the underlying issue.

Unrelated failing tests: merging.


Tensor_flow text Similarty _issue

Hello Every One ,
Can you please help out to resolve below issue.
2018-09-17 15:10:51.106133: I T:\src\github\tensorflow\tensorflow\core\platform\cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2018-09-17 15:10:52.536772: I T:\src\github\tensorflow\tensorflow\core\common_runtime\gpu\gpu_device.cc:1405] Found device 0 with properties:
name: GeForce 940MX major: 5 minor: 0 memoryClockRate(GHz): 1.189
pciBusID: 0000:01:00.0
totalMemory: 4.00GiB freeMemory: 3.36GiB
2018-09-17 15:10:52.541692: I T:\src\github\tensorflow\tensorflow\core\common_runtime\gpu\gpu_device.cc:1484] Adding visible gpu devices: 0
2018-09-17 15:10:59.482063: I T:\src\github\tensorflow\tensorflow\core\common_runtime\gpu\gpu_device.cc:965] Device interconnect StreamExecutor with strength 1 edge matrix:
2018-09-17 15:10:59.506852: I T:\src\github\tensorflow\tensorflow\core\common_runtime\gpu\gpu_device.cc:971]      0
2018-09-17 15:10:59.521022: I T:\src\github\tensorflow\tensorflow\core\common_runtime\gpu\gpu_device.cc:984] 0:   N
2018-09-17 15:10:59.527459: I T:\src\github\tensorflow\tensorflow\core\common_runtime\gpu\gpu_device.cc:1097] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 3081 MB memory) -> physical GPU (device: 0, name: GeForce 940MX, pci bus id: 0000:01:00.0, compute capability: 5.0)
[None, None]
2018-09-17 15:11:26.985779: E T:\src\github\tensorflow\tensorflow\core\common_runtime\executor.cc:697] Executor failed to create kernel. Not found: No registered 'Size' OpKernel for GPU devices compatible with node module_apply_default/compound_bigrams/boolean_mask/Prod = Size[T=DT_STRING, out_type=DT_INT32, _device="/job:localhost/replica:0/task:0/device:GPU:0"](module_apply_default/compound_bigrams/concat_2/_91, ^module_apply_default/compound_bigrams/boolean_mask/Shape_1/_95)
(OpKernel was found, but attributes didn't match)
.  Registered:  device='CPU'; out_type in [DT_INT32]
device='CPU'; out_type in [DT_INT64]
device='GPU'; T in [DT_HALF]; out_type in [DT_INT32]
device='GPU'; T in [DT_HALF]; out_type in [DT_INT64]
device='GPU'; T in [DT_BFLOAT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_BFLOAT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_FLOAT]; out_type in [DT_INT32]
device='GPU'; T in [DT_FLOAT]; out_type in [DT_INT64]
device='GPU'; T in [DT_DOUBLE]; out_type in [DT_INT32]
device='GPU'; T in [DT_DOUBLE]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT64]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT64]; out_type in [DT_INT64]
device='GPU'; T in [DT_UINT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_UINT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_UINT8]; out_type in [DT_INT32]
device='GPU'; T in [DT_UINT8]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT8]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT8]; out_type in [DT_INT64]
device='GPU'; T in [DT_COMPLEX64]; out_type in [DT_INT32]
device='GPU'; T in [DT_COMPLEX64]; out_type in [DT_INT64]
device='GPU'; T in [DT_COMPLEX128]; out_type in [DT_INT32]
device='GPU'; T in [DT_COMPLEX128]; out_type in [DT_INT64]
device='GPU'; T in [DT_BOOL]; out_type in [DT_INT32]
device='GPU'; T in [DT_BOOL]; out_type in [DT_INT64]
device='GPU'; T in [DT_VARIANT]; out_type in [DT_INT32]
device='GPU'; T in [DT_VARIANT]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT32]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT32]; out_type in [DT_INT64]
     [[Node: module_apply_default/compound_bigrams/boolean_mask/Prod = Size[T=DT_STRING, out_type=DT_INT32, _device="/job:localhost/replica:0/task:0/device:GPU:0"](module_apply_default/compound_bigrams/concat_2/_91, ^module_apply_default/compound_bigrams/boolean_mask/Shape_1/_95)]]

Traceback (most recent call last):
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\client\session.py", line 1278, in _do_call
return fn(*args)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\client\session.py", line 1263, in _run_fn
options, feed_dict, fetch_list, target_list, run_metadata)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\client\session.py", line 1350, in _call_tf_sessionrun
run_metadata)
tensorflow.python.framework.errors_impl.NotFoundError: No registered 'Size' OpKernel for GPU devices compatible with node module_apply_default/compound_bigrams/boolean_mask/Prod = Size[T=DT_STRING, out_type=DT_INT32, _device="/job:localhost/replica:0/task:0/device:GPU:0"](module_apply_default/compound_bigrams/concat_2/_91, ^module_apply_default/compound_bigrams/boolean_mask/Shape_1/_95)
(OpKernel was found, but attributes didn't match)
.  Registered:  device='CPU'; out_type in [DT_INT32]
device='CPU'; out_type in [DT_INT64]
device='GPU'; T in [DT_HALF]; out_type in [DT_INT32]
device='GPU'; T in [DT_HALF]; out_type in [DT_INT64]
device='GPU'; T in [DT_BFLOAT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_BFLOAT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_FLOAT]; out_type in [DT_INT32]
device='GPU'; T in [DT_FLOAT]; out_type in [DT_INT64]
device='GPU'; T in [DT_DOUBLE]; out_type in [DT_INT32]
device='GPU'; T in [DT_DOUBLE]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT64]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT64]; out_type in [DT_INT64]
device='GPU'; T in [DT_UINT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_UINT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_UINT8]; out_type in [DT_INT32]
device='GPU'; T in [DT_UINT8]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT8]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT8]; out_type in [DT_INT64]
device='GPU'; T in [DT_COMPLEX64]; out_type in [DT_INT32]
device='GPU'; T in [DT_COMPLEX64]; out_type in [DT_INT64]
device='GPU'; T in [DT_COMPLEX128]; out_type in [DT_INT32]
device='GPU'; T in [DT_COMPLEX128]; out_type in [DT_INT64]
device='GPU'; T in [DT_BOOL]; out_type in [DT_INT32]
device='GPU'; T in [DT_BOOL]; out_type in [DT_INT64]
device='GPU'; T in [DT_VARIANT]; out_type in [DT_INT32]
device='GPU'; T in [DT_VARIANT]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT32]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT32]; out_type in [DT_INT64]
     [[Node: module_apply_default/compound_bigrams/boolean_mask/Prod = Size[T=DT_STRING, out_type=DT_INT32, _device="/job:localhost/replica:0/task:0/device:GPU:0"](module_apply_default/compound_bigrams/concat_2/_91, ^module_apply_default/compound_bigrams/boolean_mask/Shape_1/_95)]]

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 3, in
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\client\session.py", line 877, in run
run_metadata_ptr)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\client\session.py", line 1100, in _run
feed_dict_tensor, options, run_metadata)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\client\session.py", line 1272, in _do_run
run_metadata)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\client\session.py", line 1291, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.NotFoundError: No registered 'Size' OpKernel for GPU devices compatible with node module_apply_default/compound_bigrams/boolean_mask/Prod = Size[T=DT_STRING, out_type=DT_INT32, _device="/job:localhost/replica:0/task:0/device:GPU:0"](module_apply_default/compound_bigrams/concat_2/_91, ^module_apply_default/compound_bigrams/boolean_mask/Shape_1/_95)
(OpKernel was found, but attributes didn't match)
.  Registered:  device='CPU'; out_type in [DT_INT32]
device='CPU'; out_type in [DT_INT64]
device='GPU'; T in [DT_HALF]; out_type in [DT_INT32]
device='GPU'; T in [DT_HALF]; out_type in [DT_INT64]
device='GPU'; T in [DT_BFLOAT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_BFLOAT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_FLOAT]; out_type in [DT_INT32]
device='GPU'; T in [DT_FLOAT]; out_type in [DT_INT64]
device='GPU'; T in [DT_DOUBLE]; out_type in [DT_INT32]
device='GPU'; T in [DT_DOUBLE]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT64]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT64]; out_type in [DT_INT64]
device='GPU'; T in [DT_UINT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_UINT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_UINT8]; out_type in [DT_INT32]
device='GPU'; T in [DT_UINT8]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT8]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT8]; out_type in [DT_INT64]
device='GPU'; T in [DT_COMPLEX64]; out_type in [DT_INT32]
device='GPU'; T in [DT_COMPLEX64]; out_type in [DT_INT64]
device='GPU'; T in [DT_COMPLEX128]; out_type in [DT_INT32]
device='GPU'; T in [DT_COMPLEX128]; out_type in [DT_INT64]
device='GPU'; T in [DT_BOOL]; out_type in [DT_INT32]
device='GPU'; T in [DT_BOOL]; out_type in [DT_INT64]
device='GPU'; T in [DT_VARIANT]; out_type in [DT_INT32]
device='GPU'; T in [DT_VARIANT]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT32]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT32]; out_type in [DT_INT64]
     [[Node: module_apply_default/compound_bigrams/boolean_mask/Prod = Size[T=DT_STRING, out_type=DT_INT32, _device="/job:localhost/replica:0/task:0/device:GPU:0"](module_apply_default/compound_bigrams/concat_2/_91, ^module_apply_default/compound_bigrams/boolean_mask/Shape_1/_95)]]

Caused by op 'module_apply_default/compound_bigrams/boolean_mask/Prod', defined at:
File "", line 3, in
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow_hub\module.py", line 203, in call
name=name)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow_hub\native_module.py", line 447, in create_apply_graph
restore_collections_predicate=(lambda key: key in import_collections))
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\training\saver.py", line 1939, in import_meta_graph
**kwargs)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\meta_graph.py", line 744, in import_scoped_meta_graph
producer_op_list=producer_op_list)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\util\deprecation.py", line 454, in new_func
return func(*args, **kwargs)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\importer.py", line 442, in import_graph_def
_ProcessNewOps(graph)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\importer.py", line 234, in _ProcessNewOps
for new_op in graph._add_new_tf_operations(compute_devices=False):  # pylint: disable=protected-access
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\ops.py", line 3289, in _add_new_tf_operations
for c_op in c_api_util.new_tf_operations(self)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\ops.py", line 3289, in
for c_op in c_api_util.new_tf_operations(self)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\ops.py", line 3180, in _create_op_from_tf_operation
ret = Operation(c_op, self)
File "C:\Users\Rahul\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\framework\ops.py", line 1717, in init
self._traceback = tf_stack.extract_stack()
NotFoundError (see above for traceback): No registered 'Size' OpKernel for GPU devices compatible with node module_apply_default/compound_bigrams/boolean_mask/Prod = Size[T=DT_STRING, out_type=DT_INT32, _device="/job:localhost/replica:0/task:0/device:GPU:0"](module_apply_default/compound_bigrams/concat_2/_91, ^module_apply_default/compound_bigrams/boolean_mask/Shape_1/_95)
(OpKernel was found, but attributes didn't match)
.  Registered:  device='CPU'; out_type in [DT_INT32]
device='CPU'; out_type in [DT_INT64]
device='GPU'; T in [DT_HALF]; out_type in [DT_INT32]
device='GPU'; T in [DT_HALF]; out_type in [DT_INT64]
device='GPU'; T in [DT_BFLOAT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_BFLOAT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_FLOAT]; out_type in [DT_INT32]
device='GPU'; T in [DT_FLOAT]; out_type in [DT_INT64]
device='GPU'; T in [DT_DOUBLE]; out_type in [DT_INT32]
device='GPU'; T in [DT_DOUBLE]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT64]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT64]; out_type in [DT_INT64]
device='GPU'; T in [DT_UINT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_UINT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT16]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT16]; out_type in [DT_INT64]
device='GPU'; T in [DT_UINT8]; out_type in [DT_INT32]
device='GPU'; T in [DT_UINT8]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT8]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT8]; out_type in [DT_INT64]
device='GPU'; T in [DT_COMPLEX64]; out_type in [DT_INT32]
device='GPU'; T in [DT_COMPLEX64]; out_type in [DT_INT64]
device='GPU'; T in [DT_COMPLEX128]; out_type in [DT_INT32]
device='GPU'; T in [DT_COMPLEX128]; out_type in [DT_INT64]
device='GPU'; T in [DT_BOOL]; out_type in [DT_INT32]
device='GPU'; T in [DT_BOOL]; out_type in [DT_INT64]
device='GPU'; T in [DT_VARIANT]; out_type in [DT_INT32]
device='GPU'; T in [DT_VARIANT]; out_type in [DT_INT64]
device='GPU'; T in [DT_INT32]; out_type in [DT_INT32]
device='GPU'; T in [DT_INT32]; out_type in [DT_INT64]
     [[Node: module_apply_default/compound_bigrams/boolean_mask/Prod = Size[T=DT_STRING, out_type=DT_INT32, _device="/job:localhost/replica:0/task:0/device:GPU:0"](module_apply_default/compound_bigrams/concat_2/_91, ^module_apply_default/compound_bigrams/boolean_mask/Shape_1/_95)]]

Hi Every One ,
     Please help me resolve of this error ..

Hi @rahulgarg1,
can you please paste a minimal code snippet that reproduces this?
Also which version of tensorflow-gpu do you have installed?

have the same issue with google colab @vbardiovskyg -> https://colab.research.google.com/github/tensorflow/hub/blob/master/examples/colab/semantic_similarity_with_tf_hub_universal_encoder.ipynb

Tried to reproduce by clicking on the link, then "Runtime -> Run All", seems to work with "https://tfhub.dev/google/universal-sentence-encoder/2".
Did you make any changes to the colab before it failed?

it works on CPU runtime, but GPU runtime has the same issues as from the original author cc @vbardiovskyg

same issue here

minimal code that generates the issue:
import tensorflow as tf
import tensorflow_hub as hub

with tf.Graph().as_default():
    module_url = "https://tfhub.dev/google/universal-sentence-encoder/2"
    embed = hub.Module(module_url)
    embeddings = embed(["A long sentence.", "single-word",
                      "http://example.com"])

    with tf.Session() as sess:
        sess.run(tf.global_variables_initializer())
        sess.run(tf.tables_initializer())
        print(sess.run(embeddings))

aka the code example provided in the website!

Thanks @rmanak and @lc0 for explaining the problem.
I've contacted the publisher and got an explanation:
"Yes, this is a known issue, the USE2 worked on GPU on tf 1.7 (and maybe 1.8). There are some ops removed or unregistered from GPU since tf 1.9, which caused the problem you pasted. A simple fix to make USE2 work on GPU is switching to a early version of tensorflow, e.g. 1.7."
So the way around this for now is to either use https://tfhub.dev/google/universal-sentence-encoder-large/3 or run this on tensorflow-gpu==1.7.

@vbardiovskyg should we update the docs in this case?
I am just not sure how make it nice, since when colab has CPU env the version works fine.
Otherwise, I would at least limit to pip install at https://github.com/tensorflow/hub/blob/master/examples/colab/semantic_similarity_with_tf_hub_universal_encoder.ipynb
What do you think?

I think this should be documented on the module description.
Not sure if we should downgrade TF version on the Colab just because some modules do not work (there will always be modules that use older versions of TF).
We could add a comment next to the module selection that some modules might not be compatible with GPU, or pick two that are both compatible.

None of the following helped me:

Changing to https://tfhub.dev/google/universal-sentence-encoder-large/3
running on tensorflow-gpu==1.7.

Hi I tried on tensorflow-gpu==1.7 but somehow get this error
AttributeError: module 'tensorflow.python.estimator.estimator_lib' has no attribute 'Exporter'

None of the following helped me:

Changing to https://tfhub.dev/google/universal-sentence-encoder-large/3
running on tensorflow-gpu==1.7.

I solved this problem by changing the module to https://tfhub.dev/google/universal-sentence-encoder-large/3.
Or you can try to set the device to tf.device('/cpu:0').

@vbardiovskyg  Has this been updated in the module documentation ? If not, please let me know the module owner name and I will follow up on this. Thanks !

I tried using the https://tfhub.dev/google/universal-sentence-encoder-large/3 version on a fresh install of

tensorflow==1.7
tensorflow_hub==0.2.0
with tf.device('/cpu:0')

Unfortunately the whole process is still running on the CPU

Hi @koolkao, it seems like you are not installing tensorflow-gpu and placing it explicitly on CPU, so I am not sure why you expect to not run on CPU. (maybe a typo somewhere, but not clear where)

Aside from koolkao's immediate problem, there has been some progress on the root issue:
Commit https://github.com/tensorflow/tensorflow/commit/5c4d1c87a2794ed80d8c1da8bb6fe8b6eb86242a fixes an issue with Grappler (graph optimizer) that may have caused the failures ever since TF 1.8.
Community input is welcome whether the problem can be avoided in the field by any of the following:

Use a tf-nightly-gpu past that commit (1.14.1.dev20190503 should do, or a day after).
Turn off the incriminated optimization by setting
config.graph_options.rewrite_options.shape_optimization = 2
in the tf.ConfigProto passed to the tf.Session.

If yes, the module documentation could be updated for that (and maybe again once the fix hits a release; might be as late as 1.15/2.0).

tensorflow: 1.13.1
tensorflow-gpu: 1.13.1
I have got the same error. However, setting
config = tf.ConfigProto()
config.graph_options.rewrite_options.shape_optimization = 2
session = tf.Session(config=config)

fixed it for me. Thanks!

Thanks @arnoegw for figuring out the state of and the solution for the problem. I will update the documentation to reflect this.

try doing failed ml operation within tf.device block
with tf.device('/cpu:0'):


Made it possible to parse yaml with null values

Data source "yaml_map_of_strings" with "flatten" enabled used to crash if YAML with empty keys (key: null or just key:) was passed to it.
This PR makes yaml_map_of_strings ignore these empty keys.

Great catch!
I wonder if we should be silently omitting such fields or rather coercing them to empty strings? Given the resource name of yaml_map_of_strings, an absent value is effectively an empty string. 🙂

@anton-dessiatov are you interested in discussing/adjusting PR or should I just merge it and take care of the rest?

Hi. Sorry for late reply.
There is number of tests for existing functionality - would you mind adding a test you mentioned? I'm not sure I fully understand how Terraform would handle nil so I hope test will help with that.
I may change my opinion once I see the behavior but I still think that we should force coerce any "void" value to an empty string. I believe that "explicit is better than implicit" and because data source is named "yaml_map_of_strings" it's better to make sure we have just strings in output. Also, as of now, Terraform's type system is pretty primitive and you cannot mix types in map values. Introducing nil adds ambiguity that I'd rather avoid.
Things likely change dramatically with Terraform v0.12 and HCL2.0 but it's not out yet. This entire plugin might need to be reconsidered once that's out.
In term of another aspect of ambiguity you mentioned, we may add an option to control behavior in the face of empty values - whether to skip them or coerce to empty strings. However, if we were to do so I'd err on the side of supplying it a default value to not break backward compatibility.

I have added a test and this pull request now interprets YAML nulls (actually reflect.Invalids internally) as empty strings.

Just back from vacation and I'm 😍. @anton-dessiatov thank you for the contribution!

Also, added you to CONTRIBUTORS.md - hope you don't mind. 😊

Released as a new version https://github.com/ashald/terraform-provider-yaml/releases/tag/v2.0.1


Fix/audiodatadisplay

#381

Fixed the issue with displaying audio editor data
Fixed the issues with importing USFM and auto-deleting the selected scope
Fixed the issue with non-selected books and chapters

Metinoed issues were fixed and working as expected

Displaying audio editor data
Importing USFM and auto-deleting the selected scope
APP breaks when the non-selected books and chapters
This PR can be merged.


Incorrect version for dynamic data masking initial support

Dynamic data masking was introduced in SQL Server 2016 (13.x), not in 2017 (14.x)

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

ID: 48cb4a50-bcd6-38bc-187b-27cc36576219
Version Independent ID: 38c1d92e-25d6-6237-9a04-6ca13bbb1a09
Content: What's new in SQL Server 2019 - SQL Server
Content Source: docs/sql-server/what-s-new-in-sql-server-ver15.md
Product: sql
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

Thanks @ghotz! @MikeRayMSFT - Please take a look at this.

@ghotz Thanks Gianluca

@ghotz - thank you. We are updating the content.


Implement state tracking.

Currently maintains a list of Guilds (Members/Channels) and PrivateChannels.
This allows a lot of nice things inside bot code such as:
if i, err := d.Session.Invite(join); err == nil {
  if _, err := d.Session.State.GetGuildByID(i.Guild.ID); err == nil {
    fmt.Println("I have already joined that server.")
    return
  }
}
if _, err := d.Session.InviteAccept(join); err == nil {
  fmt.Println("I have joined the server.")
}

or something like:
func (s *Session) IsMessagePrivate(m *Message) bool {
	_, err := s.State.GetPrivateChannelByID(m.ID)
	return err == nil
}

I can see maybe you would want to make this a toggle, let me know, it would just be adding a bunch more if's in wsapi :ok_hand:

Oh, nice! Great addictions.  I wanted to at some point start adding some of these sort of helper functions into the library :)
I do think anything that caches data should be optional though.  Since in some cases it would be unused by someone using the library.  So we don't want to be wasting memory storing data that will never be used.  However it's absolutely handy for a lot of people as well :)
Lets make it optional and if a client user calls the discord.go New() func that sort of just sets everything up for them, default to having this these types of features enabled by default.  Of course they can still toggle it off.
If someone sets up their connection using the old manual methods it would default to having this type of features disabled.  Of course they can still toggle it on.
Also, some funcs have names like GetFuncName but throughout the rest of the library I'm not using names like that.  I think we should be consistent in naming across the board.   So something like GetGuildChannelByID should match the style in restapi GuildChannels  so maybe just State.GuildChannel(string)
Then, my final idea :) A lot of these functions would be handy regardless of caching and I've in the past liked the idea of adding helper functions to each of the main structs like Message, Guild, Channel, etc.
Would it be better to have a Guild.Channel(string) function that would pull from the cache if existed/enabled, otherwise do the leg work to get the information from Discord?  Similar functions for many of the other ones you've added?  I'm asking your thoughts on this one because I'm not sure what makes the best sense.  But I think these would be handy and creating two sets of similar functions maybe wouldn't be best?
Sorry, I know that's a lot of comments.

I have changed the method names and made state tracking optional, additionally I have made it null safe just in-case someone does something silly like:
s := &discordgo.Session{}
s.StateEnabled = true

I think it would be super cool to make the Guild/Channel/User methods go to cache first, but I think that should be implemented as a layer on top of State, instead of intermingling those concerns.


Software Serial Transmission Does not work

I am attempting to create a software serial connection using wave_add_serial to send the data and bb_serial_read_open to read data being received. I am able to receive the data perfectly but when I send "Hello World" the reception on the other side is completely different asci characters. I put the code below and the response in HEX. It seems like the bit order is changing some how but I am not sure how it is. Can't seem to find a pattern.
import pigpio
import time
import sys
import numpy
import struct

txPin=20
rxPin=21

serialpi=pigpio.pi()
serialpi.set_mode(rxPin,pigpio.INPUT)
serialpi.set_mode(txPin,pigpio.OUTPUT)

pigpio.exceptions = False
serialpi.bb_serial_read_close(rxPin)
pigpio.exceptions = True

baudrate =9600

serialpi.bb_serial_read_open(rxPin,baudrate,8)

def Sendline(serialpi):
    serialpi.wave_clear()
    serialpi.wave_add_serial(txPin,baudrate,b'Hello world',0,8,2)
    wid=serialpi.wave_create()
    serialpi.wave_send_once(wid)
    while serialpi.wave_tx_busy():
        pass
    serialpi.wave_delete(wid)

#while True:
Sendline(serialpi)
print 'sent'
time.sleep(.5)

The response on the other end is
BA 02 00 AB DB D2 52 A4 8B 14 DA 74 BA 02 00 AB D3 D2 52 A4 8B 14 DA 3A BA 02 00

I suggest there is a problem at the "other end" whatever that might be.
The script works fine when I connect a wire between GPIO 20 (pin 38) and GPIO 15 (pin 10 UART RXD) and cat /dev/serial0.
$ cat /dev/serial0
Hello world
Hello world
Hello world
Hello world

Note, I changed the script to add a \r\n to the string for testing and I have enabled serial on my Pi3.

Thanks for the quick response. So if I plug the Tx directly into the serial RX on the pi, everything works fine just like you. Any other computer I use does not however. I've tried multiple computers with different usb to db9 connectors. I've tried different cables and different lengths. I've tried lowering the baud rate to 600. Any ideas?

The Pi's GPIO are 3V3 TTL.
What wiring are you using between the Pi and the other end?
What is it connected to at the other end?

Ok I think I know where you going at here. Im sending 3v3 TLL on the pi and receiving 5V TLL on the computer. Didn't even think about that. I'll try to convert it and see if it works. Thanks

I am going to close this issue.  Please re-open if there does prove to be a software problem.


[ARM] az deployment: Fix the bug of 'bytes' object has no attribute 'get' for error handling in retry cases

Issue: #19743
Description

This error bytes' object has no attribute 'get' is due to the bug of JsonCTemplatePolicy in the retry operation.
In the case of retry, because the first request has been processed and converted the type of request.http_request.data from string to bytes code link  , so there is no need to process request.http_request.data again during retry,
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

ARM

The logic of JsonCTemplatePolicy is hard to understand. We need better comments!

It seems JSONSerializer wraps the jsonc in a JsonCTemplate and then JsonCTemplatePolicy extracts the jsonc. Why isn't the jsonc serialization logic done in JSONSerializer?

In fact, it's technically feasible. I've tried it and it works fine. I guess this may be a decision in code design. Maybe this splicing is not appropriate to put it in the serialization logic in code design.
Because this is legacy code, I can't answer this question perfectly. 😂

Also, The name template_as_bytes is misleading (#10389 (comment)).

I agree! It will be converted to bytes in the subsequent step of JsonCTemplatePolicy, but not in the step of JSONSerializer. So I submitted a PR #21991 to correct the variable name and add some comments to explain the function of JsonCTemplatePolicy


Atom Editor Support

This module can be adapted to work with onelint, by editing lib/init.js and lib/utils/select-style.js.
https://github.com/ricardofbarros/linter-js-standard
But it's suboptimal, as you'd want it to use the linter installed in the project that you're linting, and not a version shipped with the plugin.

Working prototype of cleverer way of doing it: https://github.com/gustavnikolaj/linter-js-standard-engine

I believe that this plugin is now solid enough that this issue can be completed.


🐛 Fixed default email recipients always being "everyone" rather than matching post visibility

refs https://github.com/TryGhost/Ghost/issues/16125
The previous fix for incorrect recipient details being shown when re-sending a failed email introduced another bug that prevented the "Match post visibility" default recipients setting from working.

the server always sets post.emailSegment to 'all' for new posts so the publish flow recipient filter logic that checked for post.emailSegment being present always defaulted to 'all' rather than falling back to the selected default recipients setting
when a post has been published but the email failed it will have its newsletter value set so we can use that as a check for using the post.emailSegment value in place of the default recipients setting

Aren't there any unit tests in Ghost that could prevent such regressions from happening?


fix data-type mismatch for mlperf_inference accuracy test

fix data-type mismatch for mlperf_inference accuracy test

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Mac OS: LoadError: Could not open library 'vips'

So I did brew upgrade vips that poured the vips-8.5.8_2.el_capitan and now require vips (the gem is the latest one) cause:
LoadError: Could not open library 'vips': dlopen(vips, 5): image not found.
Could not open library '/usr/local/lib/libvips.dylib': dlopen(/usr/local/lib/libvips.dylib, 5): Library not loaded: @rpath/libpoppler.71.dylib
  Referenced from: /usr/local/opt/poppler/lib/libpoppler-glib.8.dylib
  Reason: image not found
	from /Users/nakilon/.gem/gems/ffi-1.9.18/lib/ffi/library.rb:147:in `block in ffi_lib'
	from /Users/nakilon/.gem/gems/ffi-1.9.18/lib/ffi/library.rb:100:in `map'
	from /Users/nakilon/.gem/gems/ffi-1.9.18/lib/ffi/library.rb:100:in `ffi_lib'
	from /Users/nakilon/.gem/gems/ruby-vips-2.0.7/lib/vips.rb:466:in `<module:Vips>'
	from /Users/nakilon/.gem/gems/ruby-vips-2.0.7/lib/vips.rb:457:in `<top (required)>'

$ ls -l /usr/local/lib/libvips.dylib
lrwxr-xr-x  1 nakilon  admin  40 11 окт 19:17 /usr/local/lib/libvips.dylib -> ../Cellar/vips/8.5.8_2/lib/libvips.dylib
$ ls -l /usr/local/lib/libpoppler.dylib
lrwxr-xr-x  1 nakilon  admin  45 11 окт 19:17 /usr/local/lib/libpoppler.dylib -> ../Cellar/poppler/0.60.1/lib/libpoppler.dylib

Ruby is native to this OS: 2.0.0p648
The thing I've noticed about brew is that now it drags some portable Ruby 2.3 -- not sure if that's relevant.

Have a look at #130 and try the suggestions... I think it's a bad install configuration issue and you need to track down where it went wrong.

I tried again here and it seems to be working on sierra at least:
==> Downloading https://homebrew.bintray.com/bottles/vips-8.5.8_2.sierra.bottle.
==> Downloading from https://akamai.bintray.com/89/89fdabb07d18ac3cf22448e1bbb6f
######################################################################## 100.0%
==> Pouring vips-8.5.8_2.sierra.bottle.tar.gz
🍺  /usr/local/Cellar/vips/8.5.8_2: 188 files, 12.7MB
john@katamata ~ $ gem uninstall ruby-vips
Successfully uninstalled ruby-vips-2.0.6
john@katamata ~ $ gem install ruby-vips
Fetching: ruby-vips-2.0.7.gem (100%)
Successfully installed ruby-vips-2.0.7
Parsing documentation for ruby-vips-2.0.7
Installing ri documentation for ruby-vips-2.0.7
Done installing documentation for ruby-vips after 1 seconds
1 gem installed
john@katamata ~ $ irb
irb(main):001:0> require 'vips'
=> true
irb(main):002:0> x = Vips::Image.black 10, 10
=> #<Image 10x10 uchar, 1 bands, b-w>
irb(main):003:0>

$ which vips
/usr/local/bin/vips
$ vips --version
vips-8.5.8-Fri Oct  6 06:09:10 BST 2017
$ brew --prefix vips
/usr/local/opt/vips
$ gem uninstall ruby-vips
Select gem to uninstall:

ruby-vips-1.0.3
ruby-vips-2.0.7
All versions

3
Successfully uninstalled ruby-vips-1.0.3
Successfully uninstalled ruby-vips-2.0.7
$ gem install ruby-vips
Fetching: ruby-vips-2.0.7.gem (100%)
Successfully installed ruby-vips-2.0.7
Parsing documentation for ruby-vips-2.0.7
Installing ri documentation for ruby-vips-2.0.7
1 gem installed

$ irb
irb(main):001:0> require "vips"
LoadError: Could not open library 'vips': dlopen(vips, 5): image not found.
Could not open library '/usr/local/lib/libvips.dylib': dlopen(/usr/local/lib/libvips.dylib, 5): Library not loaded: @rpath/libpoppler.71.dylib
Referenced from: /usr/local/opt/poppler/lib/libpoppler-glib.8.dylib
Reason: image not found
from /Users/nakilon/.gem/gems/ffi-1.9.18/lib/ffi/library.rb:147:in block in ffi_lib' 	from /Users/nakilon/.gem/gems/ffi-1.9.18/lib/ffi/library.rb:100:in map'
from /Users/nakilon/.gem/gems/ffi-1.9.18/lib/ffi/library.rb:100:in ffi_lib' 	from /Users/nakilon/.gem/gems/ruby-vips-2.0.7/lib/vips.rb:466:in module:Vips'
from /Users/nakilon/.gem/gems/ruby-vips-2.0.7/lib/vips.rb:457:in <top (required)>' 	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in require'
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in rescue in require' 	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:144:in require'
from (irb):1
from /usr/bin/irb:12:in `'

Putting debug prints into ffi I see it loads libglib and libgobject as dylibs from /usr/local/lib/ but fails to load libvips.
$ file /usr/local/lib/libvips.dylib
/usr/local/lib/libvips.dylib: Mach-O 64-bit dynamically linked shared library x86_64

What is poppler? Maybe it's smth with it?
$ file /usr/local/lib/libpoppler
libpoppler-cpp.0.3.0.dylib   libpoppler-cpp.dylib         libpoppler-glib.8.dylib      libpoppler.71.0.0.dylib      libpoppler.dylib
libpoppler-cpp.0.dylib       libpoppler-glib.8.9.0.dylib  libpoppler-glib.dylib        libpoppler.71.dylib

Switching back via $ brew switch vips 8.5.8  does not help:
$ vips --version
dyld: Library not loaded: /usr/local/opt/poppler/lib/libpoppler-glib.8.dylib
  Referenced from: /usr/local/bin/vips
  Reason: Incompatible library version: vips requires version 18.0.0 or later, but libpoppler-glib.8.dylib provides version 8.0.0
Trace/BPT trap: 5

Applying patch from pull/144 (usr instead of lib) had no effect.

Weird stuff. Looking for a way to debug I found such tools as dtrace and similar. To make it work on modern Mac OS you have to avoid the SIP (that security thing that protects /usr/bin). One of the ways to do this is to copy the binary from /usr/bin to any another folder. So I've copied ruby and irb to another folder, edited the shebang in irb, ran it and guess what -- it does require "vips" and loads images with no problem.

Probably related: https://github.com/ros2/ros2/issues/391#issuecomment-333984976

So as workaround I've decided to copy a ruby executable to another directory -- for example, a working directory of where I need to run things. Like this:
$ sudo cp /usr/bin/ruby ./
$ chmod 500 ./ruby

Here is how I made things work:
IRB
If you do which irb you'll see that it's a ruby script /usr/bin/irb that has hardcoded shebang #!/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby so instead of irb you have to do:
$ ./ruby irb

RSPEC
which rspec gives me /Users/nakilon/.gem/bin/rspec and there we see the #!/usr/bin/env ruby that means you don't have to patch it, just:
$ PATH=`pwd`:$PATH rspec

RAKE
This one is tricky -- rake runs rspec in another way and seems to use the system ruby. How to check it? The only working way to know the exact path to executable by PID on Mac OS I've found is https://stackoverflow.com/a/14805946/322020 so you compile it and put the tool nearby. You can see it's working by:
$ ruby -e 'puts `./pathfind #{Process.pid}`'
proc 19893: /usr/bin/ruby
$ PATH=`pwd`:$PATH ruby -e 'puts `pathfind #{Process.pid}`'
proc 19897: /Users/nakilon/.../ruby
$ PATH=`pwd`:$PATH /usr/bin/env ruby -e 'puts `pathfind #{Process.pid}`'
proc 19900: /Users/nakilon/.../ruby

Now at the bottom of vips issue backtrace we see from /Users/nakilon/.gem/gems/rspec-core-3.5.3/exe/rspec:4. Here its content:
#!/usr/bin/env ruby

require 'rspec/core'
RSpec::Core::Runner.invoke

Right after shebang you add the following line for debug:
puts __FILE__, `/Users/nakilon/.../pathfind #{Process.pid}`

Now when you run the rake again you see:
/Users/nakilon/.gem/gems/rspec-core-3.5.3/exe/rspec
proc 19849: /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby

that means shebang is ignored. Open the /usr/bin/rake and add the
require "byebug"
byebug

right before the Rake.application.run -- moving down with step and next commands you'll eventually get to:
[74, 83] in /Users/nakilon/.gem/gems/rspec-core-3.5.3/lib/rspec/core/rake_task.rb
   74:       # @private
   75:       def run_task(verbose)
   76:         command = spec_command
   77:         puts command if verbose
   78:
=> 79:         return if system(command)
   80:         puts failure_message if failure_message
   81:
   82:         return unless fail_on_error
   83:         $stderr.puts "#{command} failed" if verbose
(byebug) command
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby -I/Users/nakilon/.gem/gems/rspec-support-3.5.0/lib:/Users/nakilon/.gem/gems/rspec-core-3.5.3/lib /Users/nakilon/.gem/gems/rspec-core-3.5.3/exe/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb

where the spec_command was:
   141:       def spec_command
   142:         cmd_parts = []
   143:         cmd_parts << RUBY
   144:         cmd_parts << ruby_opts
   145:         cmd_parts << rspec_load_path

The RUBY constant isn't declared at the moment the byebug starts but it appears immediately after you step into Rake.application.run. If you do the
$ grep -rI "RUBY =" /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/

you'll find the RUBY = ENV['RUBY'] || File.join( in file_utils.rb that is required by /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rake.rb. So the solution is just:
$ RUBY=`pwd`/ruby rake

Thank you for writing this @Nakilon, it's very helpful.
I guess another solution would be to recommend the homebrew Ruby, is that right?

Since the issue didn't exist earlier, I think smth is broken and can be fixed. Maybe some updated dependency does not meet modern Mac OS practices. That's not nice to force people to use another Ruby or disable SIP.

Update to previous comment.
This
bundle exec ./ruby `which irb`

seems to stop working if you install rbenv. In this case you should do:
bundle exec ../ruby/ruby /usr/bin/irb

since the which irb now points to bash script that obviously can't be interpreted by ruby.

Upgraded macOS from El Captain to High Sierra -- it comes with Ruby 2.3.3. And issue seems to be gone.

This worked for me:
Macos M1
Rbenv
Ruby 3.0.1
Rails 7.0.1
Just ran arch -x86_64 brew install vips and the action_text successfully printed my jpg in trix editor content.


Action Final Page

I would like you to consider the action of the burden of the last page in your source code for example:
paginator.toFinalPage = function () {
         if (paginator.page! = null) {
           paginator.numPages paginator.page = -1;
         }
  };
Thank you for your contribution was very helpful to me.

@DoteroMauricio feel free to send a PR with your suggested changes for review. Thanks!


Compilation errors with g++ 5.3.0

Hi, everyone! I've tried to compile simple program from "Sneak Peek" section and I got errors,
I've tried with -std=c++14 and -std=c++1z output is same:
https://pastebin.com/X5Ns8LU3
g++.exe (GCC) 5.3.0
In MSVC 2015 Community compilation has been successfully finished.

Not sure why this is happening. We include the necessary <cctype> header. Compilatino also succeeds on MinGW 6 and 7 and 5, so many this is a 5.3=specific bug...

Turns out MinGW doesn't like strerror_s since it's considered "optional" as part of the C11 standard. So they don't implement it sometimes.
It also doesn't have strerror_r. Which is really, really bad. Either way, I'm re-implementing it...

Should be fine now. Tagged up and ready to go: https://github.com/ThePhD/sol2/releases/tag/v2.18.0

Now error message is:
In file included from test_sol_binding.cpp:1:0:
sol.hpp: In function 'int strerror_r(int, char*, size_t)':
sol.hpp:2006:33: error: 'sys_nerr' was not declared in this scope
  if ((errnum < 0) || (errnum >= sys_nerr)) {
                                 ^

It seems strange, but I downloaded lua library version 5.2.4 and example was compiled successfully, previous version was 5.1.5

5.1.5 is where this error manifests because we have to write a compatibility shim for it. If you use 5.2.4 or 5.3.4 or even LuaJIT, this wouldn't be a problem per say.
sys_nerr is SUPPOSED to be defined by MinGW...

Give it another whirl: https://github.com/ThePhD/sol2/releases/tag/v2.18.0


[geographiclib] Update to 1.50.1

Update geographiclib to the latest version 1.50.1.
Other changes:

Update the patches
Update the usage file

Also fix the usage error like this:
CMake Error at F:/test/vcpkg/scripts/buildsystems/vcpkg.cmake:329 (_find_package):
1> [CMake]   Could not find a configuration file for package "geographiclib" that is
1> [CMake]   compatible with requested version "".
1> [CMake]
1> [CMake]   The following configuration files were considered but not accepted:
1> [CMake]
1> [CMake]     F:/test/vcpkg/installed/x64-windows/share/geographiclib/geographiclib-config.cmake, version: 1.47 (package = GeographicLib, NOT geographiclib)
1> [CMake]
1> [CMake] Call Stack (most recent call first):
1> [CMake]   CMakeProject8/CMakeLists.txt:5 (find_package)
1> [CMake] -- Configuring incomplete, errors occurred!

Resolve #10293
Note: No feature need to test.

/azp run

I tried applying this patch to vcpkg:master at commit 7192d3affa4b1d8f88e3e730eb561612c24f7d78, but it failed to apply. See below:
$ git apply 11687.patch
11687.patch:46: trailing whitespace.
diff --git a/CMakeLists.txt b/CMakeLists.txt
11687.patch:47: trailing whitespace.
index 4a9ec4e..57bf448 100644
11687.patch:48: trailing whitespace.
--- a/CMakeLists.txt
11687.patch:49: trailing whitespace.
+++ b/CMakeLists.txt
11687.patch:50: trailing whitespace.
@@ -46,6 +46,7 @@ set (LIBVERSION_API 19)
error: patch failed: ports/geographiclib/CONTROL:1
error: ports/geographiclib/CONTROL: patch does not apply
error: patch failed: ports/geographiclib/portfile.cmake:45
error: ports/geographiclib/portfile.cmake: patch does not apply

Is the patch invalid or am I doing something wrong?

@Mistrical
The error is like here:
11687.patch:46: trailing whitespace.
You might need to handle trailing whitespace issue.

@NancyLi1013 Is this PR likely to be finished/merged soon?
I'm happy to help with testing it, but I still can't seem to apply the patch to master at commit 70ab27f

@Mistrical Try git pull upstream pull/11687/head on the local branch you want to patch. It should work if you have your upstream remote set on your fork. There are conflicts that you can accept incoming on in: ports/geographiclib/CONTROL and ports/geographiclib/portfile.cmake

Please resolve the file conflicts.

@NancyLi1013 Hi, I'm the author of geographiclib.  I would be interested in hearing from you how I can simplify the deployment of a vcpkg for geographiclib.  Perhaps a single flag in CMakeLists.txt?  I also have some questions/comments about the patches:

I see that the tools are not being built.  Perhaps they should be, but not installed?  That way the tests could be enabled.

I've tried to make the version checking in project-config-cmake.cmake.in as robust as possible.  Do you have any suggestions here?

Hi @cffk
Thanks a lot for coming here. It will be so great with your support and help.
It would be better to add the OPTIONS for these parts:
add_subdirectory (tools)
add_subdirectory (man)
add_subdirectory (doc)
add_subdirectory (js)
add_subdirectory (matlab)
add_subdirectory (python/geographiclib)
add_subdirectory (examples)

If so, we can disable the codes that we don't need to build via setting the value of options as off instead of making patches.  Or we can add them as features for geographiclib.
I need to investigate why tools are disabled in  current version since it was introduced by some older changes.
As for the usage, I just added this line:
set(PROJECT_NAME_LOWER ${PROJECT_NAME}).
Since the package name seems to be updated GeographicLib as geographiclib.
We should use find_package(GeographicLib CONFIG REQUIRED)  instead of find_package(geographiclib CONFIG REQUIRED).
I will try to rebuild geographiclib  and confirm if it can work well after removing patches.
Thanks again for your support.

When I try to use geographiclib in release type, it references to a debug file. Since I only copy tools from bin/  directory to tools/geographiclib directory.
CMake Error at F:/11687/vcpkg/installed/x64-windows/share/geographiclib/geographiclib-targets.cmake:118 (message):
1> [CMake]   The imported target "CartConvert" references the file
1> [CMake]
1> [CMake]      "F:/11687/vcpkg/installed/x64-windows/tools/geographiclib/CartConvert_d.exe"
1> [CMake]
1> [CMake]   but this file does not exist.  Possible reasons include:
1> [CMake]
1> [CMake]   * The file was deleted, renamed, or moved to another location.
1> [CMake]
1> [CMake]   * An install or uninstall procedure did not complete successfully.
1> [CMake]
1> [CMake]   * The installation package was faulty and contained
1> [CMake]
1> [CMake]      "F:/11687/vcpkg/installed/x64-windows/share/geographiclib/geographiclib-targets.cmake"
1> [CMake]
1> [CMake]   but not all the files it references.

Let me try to get my arms around vcpkg and the changes that are being made to the build of GeographicLib.  Then I will be able to offer some intelligent feedback.  (A colleague at work was telling me about vcpkg since a year ago, but I haven't looked at it until now.)  I hope to get back to you within a couple of weeks.

@cffk if you have any questions about how this stuff works, we're available on discord, slack, and github issues 😄😄😄

OK, I've submitted an independent PR #12379.  I've configured this from scratch and expect that the next release of GeographicLib will need a minimal patch to work with vcpkg.  By the way, what's the recommended CMake variable, e.g., _VCPKG_ROOT to test for to see if a vcpkg port is being built.

Closed this PR since @cffk has submitted another PR #12379 to update geographiclib .


ERROR:  syntax error at or near "NULL"

Hello!
When following the Quick Start w/ Docker guide, I get the following error on start-up with Docker Compose:
ERROR:  syntax error at or near "NULL"

I suspect this is due to a syntax error in the regression testing code:
https://github.com/postgresml/postgresml/blob/8bbc08ffdfa8ae287d62c0b2007f4c11f10e5f8d/pgml-extension/src/orm/task.rs#L84
This line in task.rs is written:
"ORDER BY models.metrics->>'{}' {} NULL LAST",

If this is for PostgreSQL, I think this is the wrong syntax.  I think in PostgreSQL an ORDER BY clause should have the keywords NULLS LAST not NULL LAST.  The PostgreSQL docs seem to support this:
https://www.postgresql.org/docs/current/sql-select.html
I could be wrong, though.  Thanks!
Best,
David

You are correct, this is a regression. I'll work on a patch for later today, unless you want the honors. I think we need to figure out why this wasn't caught by our test suite.


[BEAM-12421] Migrates ElasticsearchIOTest to use testContainers

Tackles the migration of ElasticsearchIOTest from in mem Elasticsearch emulator to using test containers instead. This PR also drops testing support for Elasticsearch 2.x which was previously agreed to by the mailing list[1]. This change set aims to address some of the flakiness with ES testing.
I'd especially like to give credit to @ludovic-boutros whose work this PR is heavily based on.
[1] https://lists.apache.org/thread.html/ra8c4541327c0419e672c55a385abe1af1f5831c9e2943713b525f969%40<user.beam.apache.org>

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @aromanenko-dev @timrobertson100 @ludovic-boutros

Looks like I need to modify the waitStrategy a bit more so these tests don't flake

tests all passing, ready for review

Thanks!
@echauchot Since you contributed a lot to ElasticsearchIO, could you take a look, please?

Sorry guys, I don't have time to review this PR. @timrobertson100 can you take a look ?
Also @ludovic-boutros can you take a look as it is based on your work ?
Thanks

Run Java PreCommit

Run Java PreCommit

It seems Task :runners:flink:1.11:test keeps failing in builds. ES tests on one occasion as well, but so far substantially less frequently with TestContainers

Anything outstanding here? What are the next steps?

Will this help deflake the presubmit? If so, can we have this merged soon please?
I am seeing several ElasticsearchIOTest failures in my precommit.
Thread:
https://lists.apache.org/thread.html/r3979180772ff2166a95ff65735ff353a71dd42b2be16b643529b89c3%40<dev.beam.apache.org>

Anything outstanding here? What are the next steps?

If so, can we have this merged soon please?

I don't think this has been reviewed yet, @timrobertson100 just had one high-level comment. It doesn't sound like anyone with elasticsearch expertise has time to review.
Do you have time to review it @ajamato? I could take a quick look and merge after that.

Thanks, @TheNeuralBit, @egalpin
I looked over the code and was happy with it with only the one high-level comment which is resolved (we'll remove duplication in a different issue). I am afraid I am not familiar enough with decisions in the Beam project around use of containers to know if this is a welcome addition to merge, or the consequences.

Got it, thank you @timrobertson100. We're already using test containers in a few other places, so this is a welcome change.

Thanks for merging @TheNeuralBit and especially to @egalpin for the work on this.

Yes thanks to @egalpin and thanks to all of you for review/merge while I was unavailable !


Make virtio-scsi as the default if not specified

Make sure to use virtio-scsi as the disk interface type if not specified.
The prime reason for that is support for large number of disks and iothread support. Overall this is ovirt's recommendation as well.

commit f0fca55de7cc431ae3855ac0e330428b09fc6b41 fixes this


Program sometimes freezees up on sudo

When saving a file with Sudo, it asks y or n, and I enter my password. It takes two hits of enter to complete, and sometimes it freezes there and doesnt save and I have to press ctrl+ c and go back in to redo my changes.

I have not been able to reproduce this but I believe it is fixed with the new and improved save with sudo code.


Remove Windows tests.

Since we're planning on utilizing signals to do online reconfiguration, this probably isn't going to work for Windows.  Windows just seems to have less-good tooling around sending signals to processes, etc.  Linux is our target environment, so... might as well lean into it.

Note: we added a call to our integration tests here, which is broken when it tries to run on Travis -- presumably it can't create the Synchrotron configuration on disk or the hard-coded path to redis-server is wrong -- but it doesn't actually fail the build so I'm going to leave it and make it work in another PR since we have integration test improvements in #7 that are likely important.