Wider text area in the blog posts/pages

Great theme!! Is there an easy way to make the text area in the blog posts a litt wider and reduce the "white borders". I'm not a CSS expert and my attempts failed so far ;). Any hint appreciated.

Sorry to zombie an old post, but I wanted to clarify something. (I'm also a Jekyll and css noob, sorry :(.)
Is changing variable $def_grid: 12 to something like $def_grid: 16 in the file grid.scss the only thing that is required to make the text wider?
Or do we also need to update all the grid(12,10) values in page.scss to match?
If I just change $def_grid, nothing seems to happen. But if I try to change the values in pages.scss to match $def_grid---say, grid(16,14) prefix(16,1) and suffix(16,1) to match $def_grid: 16---I get a "page failed" error from GitHub.
I sort of just gave up and reverted everything back. Would be great to fully understand how to shift the width.
Thanks!

Changing $def_grid probably won't help. All it's going to do is change the math slightly.
You need to play with the grid mixins found in grid.scss. They're all documented if you look at the comments for some guidance. Basically what's going on is with the grid(x, x) mixin it's saying make the element you apply it to x amount of columns wide.
grid(12,10) means 10 columns of 12 (12 being the same amount of columns as $def_grid) which is a width of about 83.33333%. 12,12 would be 100%. The mixin isn't doing much other than to do some quick math to output the widths in percentages.
There's also some media queries mixed in there to change the amount of columns #main .post and #main .page span depending on the screen sizes. I'm guessing you want to make it wider on desktop screens. So you'll need to play with the grid mixin values at the large and x-large breakpoints.
You'll see below it goes from 10 columns on mobile to 6 columns, to 5 columns at the largest screen size. I did this to make the typographic measure shorter since long lines of text are harder for the eye to track and read.
#main {
	counter-reset: captions;
	@include container;
	@include clearfix;
	clear: both;
	margin-top: 2em;
	h1 {
		margin-top: 0;
	}
	.post,
	.page {
		@include container;
		@include grid(12,10);
		@include prefix(12,1);
		@include suffix(12,1);
		margin-bottom: 2em;
		@media #{$small} {
			@include grid(12,8);
			@include prefix(12,0);
			@include suffix(12,0);
		}
		@media #{$large} {
		@include grid(12,6); // increase 6 if you want to make it wider
		}
		@media #{$x-large} {
			@include grid(12,5); // increase 5 if you want to make it wider
		}
	}
}

The prefix and suffix mixins apply margin before and after to simulate a gutter. They work similar to the other mixin. The first value is the base grid (eg. 12 columns), the second is how many columns.
prefix(12,0) would remove any margin to the left, prefix(12,1) would add a column of margin before, 12,2 would add 2 columns, etc. etc. etc.

Pretty sure I understand.
I decided to try running my site locally (following your amazing instructions) since I had not done so upgrading to OS X 10.11.
I find that, while running the server locally and making the following changes to #main.page...
        ...
        @media #{$large} {
        @include grid(12,10); // increased to 10
        }
        @media #{$x-large} {
            @include grid(12,9); // increase to 9
        }

...I find no noticeable changes to a post even though I can see the changes being regenerated in terminal.
But the more odd thing I noticed is that the text DOES get wider as I make my browser screen thinner. It only shrinks when I get to a certain browser window width. You can see a video of here.
So I'm at a loss. I've fiddled with the variables but have seen no significant changes. I also noticed, as seen in the video, that the issue the width of a post is wider at thinner browser widths but then breaks as I take the browser with to full screen. My guess is that it has something to do with the @media variables in variables.scss
$micro            : "only screen and (min-width: 30em)";
$small            : "only screen and (min-width: 37.5em)";
$medium           : "only screen and (min-width: 48em)";
$large            : "only screen and (min-width: 62em)";
$x-large          : "only screen and (min-width: 86.375em)";

But, when I fiddled with this, I just got errors. So I left them alone.
Anyway, sorry to take your time. I just got that itch where I'm obsessed with why the hell something doesn't seem to be working and can figure it out (I need to stop and move on---my site looks more than great thanks to your work!).

I just did a quick test with the grid changes you made and it sort of works, but is 1 column too wide so things stack weird.
If you decrease by one like so:
...
        @media #{$large} {
        @include grid(12,9);
        }
        @media #{$x-large} {
            @include grid(12,8);
        }

You'll get this. I would probably knock it down another value and add @include suffix(12,1); to apply some white space on the right so the text isn't hitting the scrollbar.

The fact that your CSS isn't changing tells me you probably have url:  in your _config.yml set to your production site. When working locally you'll need to leave that blank or change to url: http:localhost:4000 to use the local CSS. All asset links in the theme are absolute and it's likely pulling the one from your prod site instead... which is why you're not seeing any changes.
Be sure to restart the Jekyll server after making any _config.yml changes since those aren't watched automatically.
Another thing I'd suggest is firing up your browser's web developer tools. Once enabled you'll be able to right click any element and inspect it's CSS properties. You can also tinker with the declarations in real time to figure out what changes you might want to make.
The line numbers won't match up exactly but should give you a good idea on what classes or elements you need to target to get things laid out how you'd like.
PS: I'm working on a complete rewrite of the theme which should make customizing things a bit easier. I was never happy with the column placement on the current version. You're not the first person to run into problems trying to widen the main content container or shift things around. Probably won't launch for a bit but I'm getting closer as I build out the documentation.

Sweet. Got it to work. And you were correct, I didn't change the url. While I was looking at the correct html file, my guess is that, since I wasn't using the local port, things just weren't update correctly.
Thanks so much. That one failure (not changing the url) was really the biggest issue. Now that I can play around and see things in real time, I should be in much better shape!

Thank you!


Support additional charsets in isByteLength()

like
isByteLength('abc中文', {
 min: 1,
 max: 20,
 charset: 'utf16le',
})

thanks

This is outside the scope of the library.


do not generate rss feed for draft posts

Hi,
would it be possible to add a setting for not generating RSS feeds for markdown files that have
draft: true

in their frontmatter?

Hello,
Thanks for your interest.
Good idea and simple to implement. Done in #149.
Can you have a look please?

yes, looks good, thank you.
which version should this change be merged in so that I can pinpoint to it in my requirements?
PS> sorry for piggybacking on this, but I failed to find if there is an option to exclude "updates" feed from being generated?

which version should this change be merged in so that I can pinpoint to it in my requirements?

Released in https://github.com/Guts/mkdocs-rss-plugin/releases/tag/1.5.0

PS> sorry for piggybacking on this, but I failed to find if there is an option to exclude "updates" feed from being generated?

Please create other issue with more details (use case, reasons, examples...).


add fasttext module

Checklist

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

This is a fix to be merged in lieu of seemingly dead PR #10.

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

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Non noarch packages should have python requirement without any version constraints.
Non noarch packages should have python requirement without any version constraints.

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

OK, @kylebgorman I think this is good now.


Docker Setup - can't log into db - FATAL: role “postgres” does not exist

Using Ubuntu 18.04.
Everything works well until I try to get into the database in the postgres container using the cli.
FATAL: role “postgres” does not exist

Managed to 'solve' this by connecting to the db in the normal way - outside of the container.


addr_to_string() doesn't include na plugin prefix

This is a problem when you compile in support for two NA plugins that can handle the same program, e.g. cci+verbs and ofi+verbs.  If you start a server with an ofi+verbs address, it will resolve it's own address to a string that looks like this:
verbs://fi_sockaddr_in://<IP_ADDRESS>:46326

If you give that address to a client, however, it will try to give that address to the cci plugin (because cci takes precedent over ofi if both support verbs) and a segfault occurs.
I think this would work Ok if the addr_to_string prepended the ofi+ prefix so that other processes could tell which na plugin is expected for communication.

Ah I see yes OK I will fix that.

Oh but wait, do you mean you give that address to the HG_Init() call? How can it use the cci plugin if you do HG_Init() with ofi+verbs for example?

Ah, right, so to be more specific: when I give the client an address like verbs://fi_sockaddr_in://<IP_ADDRESS>:46326, my client program is stripping off everything after the // and using that as the argument to HG_Init(), then using the whole address in the addr_lookup call.
Basically I'm trying to get the client to select it's HG_Init() argument automatically based on the server address that it is instructed to connect to.
This problem might not exist if it were (for example) an MPI program where every process uses an identical, pre-selected HG_Init() argument.  I can't test that right now though do to some apparent bad interaction between MPI and fi_verbs...

OK yes that makes sense then I can fix NA to automatically include the plugin name then.

Should be fine now, plugins will just need to be careful to always add the protocol first when generating the string.

Confirmed the fix works- thanks @soumagne !


Integration Tests for plugins

We need to add integration tests for all official plugins in order to ensure jss or plugins releases don't break each other.

Or maybe we should complete #163 and then run all plugins tests after we run the main test suite

Ok the plan for now is:

Every package we want to test from jss test runner creates a build into tests dir. That built contains all tests as well the sources compiled to cjs/es3 (yes es3 is needed to support IE9 stuff like "default").  Also those files are already "pre-wired".
JSS repository has all devDependencies needed to run the tests of those packages. Yes, it will potentially break if some of the packages expects a newer version than the one used in the main repo, however we will see it as we run the tests.
JSS main test entry will import tests from tests folder of those packages.

done


Key Account Manager dropdown in client details page

Describe the task
When creating/updating a client, in the list of Key Account Managers, there are a few problems:

The names are not sorted, so it's difficult to identify the person we want to select
The names of inactive users are also coming, as a result the list is unnecessarily long!

Expected behavior

The names should be sorted
Inactive users should not be included

@GauravGusain98 Sir, where do we check the status of user as active or inactive in this, I can only find the status of clients and projects. Please give me a reference to check the user status

@GauravGusain98 Sir, where do we check the status of the user as active or inactive in this, I can only find the status of clients and projects. Please give me a reference to check the user status

If a user has a deleted_on column filled in the users table in the database then he/she is inactive, else if the field is null then he/she is a active user.


typo fix

Codecov Report

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

@@           Coverage Diff           @@
##           master      #53   +/-   ##
=======================================
  Coverage   41.16%   41.16%
=======================================
  Files          12       12
  Lines         498      498
=======================================
  Hits          205      205
  Misses        255      255
  Partials       38       38

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 e633db3...2ad4dff. Read the comment docs.


timestamp/naive_datetime fields always appear in changeset "changes" even if not changed

Current behavior
As here in the docs says:
"By default, if there are no changes in the changeset, update/2 is a no-op."
https://hexdocs.pm/ecto/Ecto.Repo.html#c:update/2
But I've noticed that updated_at column was being updated even with the same update attributes already in database. This case happened when the changeset includes timestamp columns:
Notice that in the example below the first image is the first update:

In the second one I've submitted the same changeset, but this time the changes does not include the varchar column status with the value canceled" (because it didn't changed). The other timestamp columns were marked as changed but actually they are not.
Is this an expected behaviour? If not, maybe is a NaiveDatetime to timestamp conversion...

Thanks
Expected behavior
The expected behaviour should be that no changes are applied to the changeset and the updated_at column is not updated.

Maybe this can help. The first image prints fields from Repo.get(...). The second one prints fields from a Repo.insert/update(...).

@lucasmazza looking at your last comments when data returned by Repo.get has microsecond precision but data returned by Repo.insert doesn't (because your changeset had timestamps without microseconf precision too), the issue seems related to https://github.com/elixir-ecto/ecto/issues/2018 and will be fixed in ecto 3.0 by introducing separate types.
In the future when submitting bugs please fill in issue template especially ecto version & which db you use!

@wojtekmach you pinged the wrong Lucas. :)
@luccasmaso as @wojtekmach explained, this is being addressed in the next ecto release!

sorry @lucasmazza 😂

@wojtekmach all good, haha 👋


Define working directory for each process.

Can I define separate working_dir for specific process? or specific environment for each process?
Eye.application 'services' do
  check :cpu, every: 10.seconds, below: 100, times: 3 # global check for all processes

    working_dir "/root/"
    stdall "/var/log/dnsvault/eye/trash.log" # stdout,err logs for processes by default
    env 'APP_ENV' => 'development' # global env for each processes
    trigger :flapping, times: 10, within: 1.minute, retry_in: 5.minutes
    chain grace: 10.seconds # chained start-restart with 10s interval, one by one.

    process :nginx do
       pid_file "/var/run/nginx.pid"
       start_command "service nginx start"
       stop_command "service nginx stop"
       restart_command "service nginx restart"
       stdall "/var/log/dnsvault/eye/nginx.log"
       start_timeout 60.seconds
       depend_on [:tincd, :avahi_autoipd, :avahi_daemon]
    end
    process :redis do
       pid_file "/var/run/redis/redis.pid"
       start_command "service redis start"
       stop_command "service redis stop"
       restart_command "service redis restart"
       stdall "/var/log/dnsvault/eye/redis.log"
       start_timeout 60.seconds
    end
    process :syncthing do
       working_dir "/usr/home/system/"
       uid "system"
       gid "system"
       pid_file "/var/run/syncthing.pid"
       start_command "/usr/home/syncthing/syncthing"
       stdall "/var/log/dnsvault/eye/syncthing.log"
       start_timeout 60.seconds
       daemonize true
    end
end

yes, just copy option working_dir or any other into process definition. it would be rewrited for that process.


Prevent Firefox from dying with a DOM exception when calling getBBox() on an invisible node.

Firefox throws a NS_ERROR_FAILURE when calling  getBBox() on an invisible node.
See http://jsfiddle.net/sym3tri/kWWDK/

I changed the method name to getBBoxProperty() as you suggested.
Chartist is a great lib btw.
Regards
Thilo

Hi Thilo
Great! Thanks for your contribution! And thanks for the kind words :-) There are millions of things we still need to fix and change but we do our best in the available time that we have in an open source project.
Cheers
Gion

It looks like this was merged into develop, but I'm still seeing this in the current dist (0.11.0).
Did this ever get tested?


integrate keepalived between pihole instances

https://github.com/acassen/keepalived
https://www.youtube.com/watch?v=hPfk0qd4xEY


Can you use machine generated identities?

Are you able to use machine generated identities to access Key Vault when configuring certificates on Application Gateways?

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

ID: 4c416d5e-5bfd-c641-e9bb-324dcb921acc
Version Independent ID: 8739a044-d471-c432-3ed1-503539408ae8
Content: TLS termination with Azure Key Vault certificates
Content Source: articles/application-gateway/key-vault-certs.md
Service: application-gateway
GitHub Login: @vhorne
Microsoft Alias: victorh

@atrauzzi Thanks for reaching out. We are working on your query and will get back to you shortly.

@atrauzzi , Assigned this to the content author for providing better insights.

Hello @atrauzzi,
Thanks for reaching out! System assigned managed identities are not supported for Application Gateway, you must leverage User Managed Identities for the integration with key vault today.
Hope this helps!
Jack
#please-close


chore: release 1.2.324

:robot: I have created a release *beep* *boop*
1.2.324 (2024-07-31)
Bug Fixes

build, buildah, dockerfile, staged: 'ADD / /app' not working (8bf5d52)
dev: disable signing for service commits (4d9ba02)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v1.2.324 :sunflower:


What aspects of the tutorial are different if creating an iOS app?

I am trying to build an iOS app in Swift, using a Haskell backend for logic. There have been no comprehensive tutorials online about how to do this, so I assumed that it wouldn't be too different from creating a Mac app. I did find one repo called ghc-ios, which had a guide on how to set up a iOS project, but ghc-ios was written in 2014 when Swift was still in its early days (in addition, Cabal linking is a mess in that tutorial and did not work).
I was able to get through half of the tutorial*, up until I am supposed to "Build the SwiftHaskellLibrary framework in Xcode, then stack build, and then finally build and run the SwiftHaskell app target to launch the app and see the default window from MainMenu.xib".
*At one point, we assumed MainMenu.xib could be considered the same as Main.storyboard?
Then, during stack build we get the following error:
ld: warning: URGENT: building for OSX, but linking against dylib (build/SwiftAppLibrary.framework/SwiftAppLibrary) built for iOS. Note: This will be an error in the future.
Undefined symbols for architecture x86_64:
  "_runNSApplication", referenced from:
      _r2YD_info in Main.o
      _c30S_info in Main.o
     (maybe you meant: _Main_runNSApplication_info, _Main_runNSApplication_closure )
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Does anyone know what modifications I could follow to properly run Haskell code in Swift (3.0.2) for iOS? Is it even possible to make modifications to this Mac tutorial?
Any insight would be helpful. Thank you.

You'll still need ghc-ios or an equivalent cross-compiling GHC, as a standard x86_64 GHC can't produce programs for iOS ARM (and maybe not even the simulator). ghc-ios might have been started in 2014, but it looks like it's been updated to keep pace with iOS updates. Changes to Swift can't really break ghc-ios, as ghc-ios doesn't depend on Swift.
Main.storyboard is indeed the equivalent of MainMenu.xib.
Regarding your error message, if the linker is not finding the symbol because of the platform mismatch, then you'll need to configure stack to use ghc-ios. (This would be needed anyways to get an ARM binary.) It might also be that the symbol is just not in the library; you can check with nm -a.
I don't know whether the full linking setup in the tutorial will actually work on an iOS device with all its signing and execution restrictions, but I think the platforms are similar enough that it's plausible that it could work.

Yeah, need to use the contents of main.m from an iOS app instead. Something like (not tested):
void runNSApplication(void) {
    int argc = 1;
    char *argv[] = {strdup("app")};
    @autoreleasepool {
        return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));
    }
}

I don't remember why I wasn't using NSApplicationMain in the tutorial project's code, so there might be some subtlety that would require loading the storyboard and starting UIApplication yourself.

Hi, I wonder could you help with this:
When you write:

This is possible to write in Swift, however as of Swift 3.0.2, the annotation to export unmangled C symbols (@_cdecl) is not documented as stable. Additionally, whole module optimization will assume that @_cdecl symbols are unused and remove them.

Has this changed in later versions of Swift? And would it be possible to rewrite this to work with Storyboards, or even better SwiftUI?
Thanks!
#import "SwiftAppLibrary.h"

@interface AClassInThisFramework : NSObject @end
@implementation AClassInThisFramework @end

void runNSApplication(void) {
    NSApplication *app = [NSApplication sharedApplication];
    NSBundle *bundle = [NSBundle bundleForClass:[AClassInThisFramework class]];
    NSArray *topObjects;
    [[[NSNib alloc] initWithNibNamed:@"MainMenu" bundle:bundle]
     instantiateWithOwner:app topLevelObjects:&topObjects];
    [app run];
}

@_cdecl does still work and has tests in the Swift compiler repo. I'm not sure about its stability status or if the bug with whole module optimization has been fixed.
Storyboards and Swift UI may work the same if launching with UIApplicationMain. Here's an example in Swift 4:
@_cdecl("runUIApplication")
func runUIApplication() {
    let argc: Int32 = 1
    let argv = UnsafeMutablePointer<UnsafeMutablePointer<Int8>?>.allocate(capacity: 1)
    // Should probably pass the real arguments from Haskell's getArgs
    // or Foundation's ProcessInfo instead of this placeholder.
    argv[0] = strdup("app")
    return autoreleasepool {
        UIApplicationMain(argc, argv, nil, NSStringFromClass(AppDelegate.self))
    }
}

You'll also need to remove @UIApplicationMain from your AppDelegate, just like removing @NSApplicationMain for macOS in the tutorial.


QueryDSL SQL 4.1.0

Hello,
You have here a very interesting project that I would like to use. My question is, does it work with last version of QueryDSL SQL 4.1.0?
Thank you.

Not yet tested. Currently my unit tests only included jpa and mongodb, but will add support for querydsl sql as well. Will include your request in M2 release.

@natros After reviewing the API of Querydsl SQL, I notice that it has a different way of building select clause compare with JPA model. And for sure, doing a deeper comparison will reveal other differences in API. Providing another abstraction to support both JPA and SQL with the same module will be more complex. Its very possibly that I will need to create another module implementation for QueryDSL SQL.
This would be lot easier compare to 2.0.0.RELEASE goal of supporting JOOQ, since this is of the same framework library which is QueryDSL. I would defer this support on 1.1.0.RELEASE then.

Hi @natros, just want to inform you a good news. I'm planning to create a 2.0.0 release concurrently with 1.0.0 release. As I've seen, the latest querydsl groupId is caused by the change of the company owner of the product. So this means, 4.x.x structure will be followed from now on, and 3.x.x will be sort of legacy code. So as much possible, my library must keep on updated with the latest querydsl library. This is why, I am going to simultaneously create another branch for 3.x.x separately, and 4.x.x will be the main code which stays on develop branch. The final releases(1.0.0 and 2.0.0) are approximately will be delivered on later part of May 2016.
Please feel free to offer any assistance, any help is greatly appreciated.

That's good news. I believe querydsl is fallowing the same release model. I can offer my assistance with migration but I'm a newcomer to querydsl.
Sent from my iPhone

On 24/04/2016, at 13:51, John Michael Vincent Rusta<EMAIL_ADDRESS>wrote:
Hi @natros, just want to inform you a good news. I'm planning to create a 2.0.0 release concurrently with 1.0.0 release. As I've seen, the latest querydsl groupId is caused by the change of the company owner of the product. So this means, 4.x.x structure will be followed from now on, and 3.x.x will be sort of legacy code. So as much possible, my library must keep on updated with the latest querydsl library. This is why, I am going to simultaneously create another branch for 3.x.x separately, and 4.x.x will be the main code which stays on develop branch. The final releases(1.0.0 and 2.0.0) are approximately will be delivered on later part of May 2016.
Please feel free to offer any assistance, any help is greatly appreciated.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@natros Hi good news again, 1.0.0.RELEASE is completed and deployed to maven central.
If you have time and want to help, you can fork this repo and checkout git branch 'feature/querydsl4'.
From this branch you can start to migrate the code from using querydsl 3.x.x to querydsl 4.x.x. If you are familiar with maven or gradle, then it will be easier. Let me know if you agree and if you still need more information. Migration only takes time but not that hard, and since I have a full time job and also a husband and a father, time is I don't really that have much. That's why any assistance is greatly appreciated. Lets

@natros Hi natros, any updates on this one? Please don't hesitate to send me a message if you have any questions. Here is my personal email<EMAIL_ADDRESS>

See : https://github.com/vineey/archelix-rsql/pull/16

Hi @vineey sorry to disappoint you. I have two jobs and lately I have no free time to spare. I had started the migration before opening the issue, only the testes where not converted.

@natros no problem, I understand, we have the same situation. Still, thank you for starting the idea and the time. Don't worry, another interested developer has already submitted a pull request for querydsl v4.x.x migration.

Duplicate issue #16

Will deploy on osshr for maven release at the end of this day.
Thanks @natros for pointing me on this direction!
Thanks @wwadge for the great contribution.
I will make sure your efforts are listed in the release notes. Please always feel free to give suggestions and contributions on tasks for this project milestones. Thanks guys!


It's hard to install it

I encountered the same issue during the installation. I chose to download the .whl file locally and then installed it using pip.

Use docker instead?
docker run -itd --shm-size 32g --gpus all -v /root/.cache:/root/.cache --name sglang_dev lmsysorg/sglang:dev /bin/zsh

@ToSev7en @mantle2048


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 115 ms

Resolved: ClamAV performance has improved in b360abe after 540 days, 18 hours, 57 minutes.


BitSight Solution initial submission for certification.

Required items, please complete
Change(s):

Added BitSight Solution for certification.

Reason for Change(s):

New product

Version Updated:

Initial version

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

@jayeshprajapaticrest, can you please remove the keys in analytic rules which are empty, thanks.

@jayeshprajapaticrest, can you please remove the keys in analytic rules which are empty, thanks.

@v-sabiraj I have removed the empty keys from JSON and updated solution accordingly.
Let me know if anything is required.
One request can you please take this PR on priority to as we need this solution publicly as possible we can?

@jayeshprajapaticrest, can you please fix the validation errors, thanks.

@jayeshprajapaticrest, can you please fix the validation errors, thanks.

@v-sabiraj I have fixed the validation errors. Can you further proceed with the PR merge?
Let me know if any other changes required.

@devikamehra, can you please check on the Analytic Rules and approve. Thanks.

Hi @devikamehra could you please check analytic rules, thanks!

There are multiple issues which are common to all the queries

Improve the Name and Description of rules.
queryPeriod and lookback time do not match
Tactic and techniques are missing
All queries are HIGH in severity. Please divide them amongst different severity levels.
There are no Entity or custom details which are getting matched. Try matching atleast one entity wherever possible.

@devikamehra
We have fixed all the above common changes to all the Analytics rule.
So please confirm and let me know if any other changes required from our end.
Thanks

@jayeshprajapaticrest, will check on other things, thanks.

Hi @jayeshprajapaticrest, please check comments above and act accordingly. Thanks

Hi @jayeshprajapaticrest, please check comments above and act accordingly. Thanks

@v-atulyadav @devikamehra
Will check above and fixing it. Thanks

@devikamehra
Regarding the WorFromHome Analytics rule relate question.
We have understood your concern, but the actual use case of this analytic rule is as below,

We are using this analytic rule as a sample rule for the users.
We have mapped "Src" field of the ASIM network session parser with customDetails field of analytic rule with the name "ip_address".
The user will add one automation rule after deployment of this analytic rule to run a workflow and that workflow will use our mapped field "ip_address" to fetch the data of BitSight.
Also workflow will store that fetched BitSight data into log analytic workspace and will displaying the data in workbook.

Also by default this rule will be disabled and if user want the data of network session from every configured sources which only has High EventSeverity then user can modify the query of this analytic rule and can access our connected workflow as explained above.
Let me know if you have any questions related this.
Thanks.

Hi @devikamehra, suggested changes fixed by @jayeshprajapaticrest please have a look. Thanks,

@devikamehra @v-atulyadav
A gentle request to please provide a final list of changes covering everything related to analytic rule in one go only so I can resolve them at once and we can hasten up the merging process.

@v-atulyadav Please get the other components reviewed. I have reviewed the analytical query.

@jayeshprajapaticrest, can you fix the "Command And Control" to "CommandAndControl", also please check on the other comments.

@jayeshprajapaticrest, can you fix the "Command And Control" to "CommandAndControl", also please check on the other comments.

@v-sabiraj We have fixed the changes suggested above. Thanks

Hello @v-sabiraj please look into this

@v-prasadboke @v-sabiraj
Is there any update on this PR approval? As we need this solution available to the azure marketplace as early as possible.

Hi @jayeshprajapaticrest, please check below comments.

Metadata should not be in this path, you should update metadata from "Tools/Create-Azure-Sentinel-Solution/V2/WorkbookMetadata/WorkbooksMetadata.json". Remove the metadata folder from this solution
The images should be in the Preview folder, which can be found at Workbooks/Images/Preview. Below screenshot is for your reference

@v-atulyadav I have completed the changes as suggested above. Thanks
Can you please proceed with the PR approval related process?

Hi @jayeshprajapaticrest, can you please fix the validations?

Hi @jayeshprajapaticrest, can you please fix the validations?

@v-rbajaj Done with the fixing of validations.
Can you please proceed it?

@v-atulyadav We have fixed the validation issues. So can you please proceed with the merging the PR as early as possible from your end so we can get our solution publicly available.

Hello @jayeshprajapaticrest looking into this

@v-prasadboke @v-atulyadav
We are done with the all the changes and the validation fixings.
So can you please expediate the process so we can get the solution available in the azure marketplace as early as we can.

Hi @jayeshprajapaticrest, thanks for your response we will expediate the process.

hello @jayeshprajapaticrest the tables dont exist by their name after ingesting the sample data,

Had to rewrite it as
BitSightGraphData_CL, But still it doesnt retrieve the data

same is the case with BitSightFindingData

@v-prasadboke
We have provided the sample data in the path below.
Azure-Sentinel/Sample Data/Custom/BitSight/
You can create the table name as Graph_data_CL from the sample data provided at above path. And to use can configure the custom parser with the name as BitSightGraphData which refers the custom table name as Graph_data_CL which we created above from the provided sample data.
And same for the BitSightFindingData as well.
Note: We have created the sample data files with the custom table names which further referenced in the Custom Parsers as well.
Let me know if we need to update the sample data file name or the parser or may be the table name referenced in the custom parser.
Thanks.
Cc: @v-atulyadav

@v-prasadboke Let me know if the above works or if we need to do any changes so we will do it and expediate this process.
Thanks.
Cc: @v-atulyadav

@v-prasadboke We have provided the sample data in the path below. Azure-Sentinel/Sample Data/Custom/BitSight/ You can create the table name as Graph_data_CL from the sample data provided at above path. And to use you can configure the custom parser with the name as BitSightGraphData which refers the custom table name as Graph_data_CL which is created from above provided sample data.
And same for the BitSightFindingData as well.
Note: We have created the sample data files with the custom table names which further referenced in the Custom Parsers as well. Let me know if we need to update the sample data file name or the parser or may be the table name referenced in the custom parser. Thanks.
Cc: @v-atulyadav

Ok @jayeshprajapaticrest let me go through this

Ok @jayeshprajapaticrest going through this

Ok @jayeshprajapaticrest going through this

@v-prasadboke Is there any update on this?

Sorry @jayeshprapajaticrest for the late reply, still working on this

Hello @jayeshprajapaticrest sorry for taking to much time, I was facing problem with sample data ingestion.
But now the sample data ingestion is working fine.
Wont take much time to test the content of the solution

Hello @jayeshprajapaticrest sorry for taking to much time, I was facing problem with sample data ingestion. But now the sample data ingestion is working fine. Wont take much time to test the content of the solution

@v-prasadboke
OK Understood. Thanks

Hello @jayeshprajapaticrest Diligence_statistics_CL,
Findings_data_CL, Breaches_data_CL  data ingetion for this 3 sample data were unsuccessfull. Due to which with some of the analytic rule and parser I'm facing some issues.
While testing parser query it was failing, but if instructions removed from the query it was running good, is this the same case with you or its with me only.
Thank you, Prasad`

@v-prasadboke
I have deployed the parser function of bitsight findings in our environment and it would deployed as success without having any error.

Thanks

Hello @devikamehra can you please review and approve the analytic rules from the PR

Hello @jayeshprajapaticrest Have you recently removed any extra commas ( , ) from the parser, If yes then please repackage the solution.
That is what was causing the parser not to run properly.
Any changes made to content of the solution should reflect in maintemplate as well.
Which takes place after when you make changes and repackage the solution.
And the maintemplate & createui inside the zip package and in the package folder should be identical.
Thanks Prasad

Hello @jayeshprajapaticrest Have you recently removed any extra commas ( , ) from the parser, If yes then please repackage the solution. That is what was causing the parser not to run properly.
Any changes made to content of the solution should reflect in maintemplate as well. Which takes place after when you make changes and repackage the solution.
And the maintemplate & createui inside the zip package and in the package folder should be identical. Thanks Prasad

@v-prasadboke
We checked the parser and fixed the issue related with it.
Can you please again deploy and confirm that its working or not?
Thanks.
Let me know if any other changes required.

Ok @jayeshprajapaticrest looking in it

Ok @jayeshprajapaticrest looking in it

@v-prasadboke Is there any update?

Hello @jayeshprajapaticrest facing issue with parsers

Hello @jayeshprajapaticrest facing issue with parsers

Can we take some time this week to connect on MS team or Zoom and resolve it as soon as possible to expediate the process?

Hello @jayeshprajapaticrest facing issue with parsers

Can we take some time this week to connect on MS team or Zoom and resolve it as soon as possible to expediate the process?

sure it would be very helpfull for the proress, can you share your email id.
Thank you.

Hello @jayeshprajapaticrest facing issue with parsers

Can we take some time this week to connect on MS team or Zoom and resolve it as soon as possible to expediate the process?

sure it would be very helpful for the Solution, can you share your email id so that i can setup a meet. Mine's -<EMAIL_ADDRESS>Thank you.

My MailID<EMAIL_ADDRESS>Can you please share an invite for the same?

Hello @jayeshprajapaticrest any reason for closing this PR.

Hello @jayeshprajapaticrest any reason for closing this PR.
@v-prasadboke
I just trying to resolve the conflicts but don't know why it gets automatically closed.
Wait I will do some changes in this PR and then reopen this.

Hello @devikamehra can you please review and approve for the analytic rules

@devikamehra @v-prasadboke
Is there any update in this PR for merge?

Hello @devikamehra waiting for your approval

This changes were asked earlier but were not committed, I request you to work on these changes.

Hello @jayeshprajapaticrest please respond to comments of Devikamehra

Hello @jayeshprajapaticrest please respond to the comments of Devika

@v-prasadboke @devikamehra
I have done with the changes of Entity Mapping. Please confirm and proceed with the merging.
Thanks

Hello @devikamehra please review and confirm once

Hello @devikamehra a validation check is failing for analytic rule, can you please check

Hello @jayeshprajapaticrest please make sure offer id and solution id of Solution, should be in lowercase everywhere in the solution

Hello @jayeshprajapaticrest please add template id of all the analytic rules to this skipvalidation file
.script/tests/KqlvalidationsTests/SkipValidationsTemplates.json

And as per latest guidelines issued by Microsoft Sentinel, please repackage the solution using V3 tool
Please go through this readme file on how to use the V3 tool

Hello @jayeshprajapaticrest you can continue with current package version

Hello @jayeshprajapaticrest you can continue with current package version
@v-prasadboke
Means with V2 tool right?
Working on to fix the validation error of Analytics rule.

Yes, Thank you @jayeshprajapaticrest

Hello @jayeshprajapaticrest please add template id of all the analytic rules to this skipvalidation file .script/tests/KqlvalidationsTests/SkipValidationsTemplates.json

@v-prasadboke
Done as suggested.

Hello @jayeshprajapaticrest please make sure offer id and solution id of Solution, should be in lowercase everywhere in the solution

@v-prasadboke
Done as suggested.

@v-prasadboke Can you proceed with the merging this PR process as early as possible?

Hello @jayeshprajapaticrest please add template id of all the analytic rules to this skipvalidation file .script/tests/KqlvalidationsTests/SkipValidationsTemplates.json

@v-prasadboke We did as above still validation error for Analytics rule exist. Can you please help us out with this?

Sure @jayeshprajapaticrest, I have scheduled a call for 2:30 PM (IST) for 28 Jul 2023.
You Would have received an invite for the same

Hello @jayeshprajapaticrest thank you for committing the changes, but still validation check is failing for this PR.
Will be examining and updating you shortly before 20 Jul 2023

@v-prasadboke
I am done with all the changes and there are no validation errors, So can you please proceed with merging of PR?

@v-prasadboke Any update on this PR merging?

Hello @jayeshprajapaticrest, Thank you for the commits.
Will be examining this PR and will update you before 26 Jul 2023

Hello @jayeshprajapaticrest, Thank you for the commits. Will be examining this PR and will update you before 26 Jul 2023

@v-prasadboke Is it possible to take it on priority. As this PR has almost around 5 month.

Hello @jayeshprajapaticrest sorry for the delay in PR review, Will take this on priority and will update you ASAP.

Hello @jayeshprajapaticrest are you available

Hello @jayeshprajapaticrest are you available

@v-prasadboke Yes

Will send you an invitation link for a call, can you join

https://teams.microsoft.com/l/meetup-join/19%3Ameeting_MjIwOGQyZWEtNjlhZC00NjQxLTk5Y2YtODc3MmU3Zjc4NmU3%40thread.v2/0?context={"Tid"%3A"72f988bf-86f1-41af-91ab-2d7cd011db47"%2C"Oid"%3A"28263f0a-981b-4a56-a4c9-1e91e9ea44fb"}

@v-prasadboke Joined to above link.

Hello @jayeshprajapaticrest please can you confirm on the changes

Hello @jayeshprajapaticrest please can you confirm on the changes

There is one discrepancy found in your comment. You forgot reverted solution id of Proofpoint after testing.

Can you please correct it? Rest looks OK.
Thanks

Sorry @jayeshprajapaticrest, and thanks for pointing it out.

Sorry @jayeshprajapaticrest, and thanks for pointing it out.

@v-prasadboke Thanks for your support and finally approving and merging this PR after long time.


Consider using semantic elements wording (point, line, polygon, relation)

iD currently mixes elements wording (node, way, area, relation) and semantic elements wording (point, line, polygon, relation).
The culprit is area, which is used to add buildings and areas, which may confuse new users. Since both are polygons, and multipolygons are best defined as multiple polygons (as opposed to multiple areas), it makes sense to rename area to polygon.

This would also avoid the possible confusion in the walkthrough.
Here, "Area" is used to refer to two different things:

iD currently mixes elements wording (node, way, area, relation) and semantic elements wording (point, line, polygon, relation).
The culprit is area, which is used to add buildings and areas, which may confuse new users. Since both are polygons, and multipolygons are best defined as multiple polygons (as opposed to multiple areas), it makes sense to rename area to polygon.

Sorry, but we wouldn't rename something like "Area" to "Polygon".
We try very hard to make iD as approachable as possible for beginners.  When we worked on the walkthrough overhaul (#3921) last year, I did a bunch of focused testing with first time mappers, and I found that jargon words like node and way were extremely off-putting.
This probably sounds silly to someone who is very familiar with OpenStreetMap or with mathematical language, but we'd actually have people get angry at their computer at the step saying "place some nodes around the edge of the playground."  We have to ease them into the idea of "nodes".  So renaming "Area" to "Polygon" would be a huge step backwards for iD's approachability.

This would also avoid the possible confusion in the walkthrough.
Here, "Area" is used to refer to two different things:

Sure!  "Area" is used to refer to many things. We list out a few of them in the walkthrough, and we encourage users to explore the map and see what kinds of things can be mapped as "areas", and no one I tested this with was confused by this concept.  And we are very consistent in how we render area vs linear features.
Anyway thanks for your suggestion, but sorry I have to close it.  I do encourage you to attend some mapathons with first time users, and even show iD to neighbors or people in your family who have never tried editing a map before or heard of OpenStreetMap, and see what concepts they struggle with.
Aside: the current biggest thing I see new users struggle with at mapathons is choosing the best background imagery.  They've asked me "how do I know which one to use" and I don't have a great answer for them.  Beginners are confused by, not just having several choices, but making that informed choice based on recency, shadows, off nadir angles, offsets, resolution, etc.. This is a hard problem to explain to people, and we don't talk about it at all in the walkthrough.


Roiz in the Lazyman Neovim Configuration Manager

I've created a Neovim Configuration Manager that supports easy installation and initialization of multiple Neovim configurations using the NVIM_APPNAME environment variable in Neovim 0.9.  I call it Lazyman and include support for Roiz as one of the "Personal" Neovim configurations installed and initialized by lazyman.
See https://github.com/doctorfree/nvim-lazyman for info on Lazyman.
I'm contacting the maintainers of the Lazyman supported Neovim configurations to seek any feedback on the description, installation, and initialization of their config in Lazyman. Please feel free to let me know what I'm doing wrong or how I could improve the incorporation of Roiz in Lazyman. If you feel there is a need to modify the way Roiz is used in Lazyman then open an issue at https://github.com/doctorfree/nvim-lazyman/issues
This isn't really an issue with your Neovim configuration, it is just a heads up and request for feedback.
The Roiz configuration  is very cool. Thanks!

Wow, looks great! I'll check it out, thank you so much, I appreciate it!


What about 1.0?

It looks like there are two tags about 1.0 version but no releases.

i think the v1.x.x are very old and not sure exactly where they came from, the version tags also arent 100% up to date. the latest version is  0.2.1 and its published on npm.


Commercial goods?

Hi,
First my english is bad,
I want to know if I can use Twemoji for commercial goods (physical) or it's only for online?
If I can use it, I understand I need to write an attribution in an 'About' section. I checked example of CC but it look like if it's only for image use. If I made a product for Twemoji image can I write an attribution like this?:
(1)-My products name, designs by Twemoji, graphics are licensed under the CC-BY 4.0-
(2)-This work, my products names, is a derivative of "Twemoji designs", used under CC-BY 4.0.-
If my right, which one is the best? And if im not right can you help me with the mention.
Thanks!

Similarly, is it sufficient to place the attribution in the product description where a product is sold? I am curious for things like stickers, t-shirts, etc which may feature the images prominently but do not have a good location for attribution.
If not, is it possible to license the images in a different manner for those types of uses?

@Jagjeet
For clothing, I would imagine the attribution to be on the tag/care label. Even then, not all clothing has care label.
If I see a product with twemoji and it doesn't mention "Twitter" at all, I know it's not an official product of Twitter. Almost all products have a web page nowadays. Personally, if I'm a creator, I would request the user to at least print the product's URL (shorten if needed) on the product. The page would shows the product description and the necessary attribution.

Thanks! Yeah, I am trying to do some hoodies and t-shirts printed on demand with a design using a few emojis. On the t-shirts, the print companies make it is pretty easy to do an inner label for that where adding attribution or a URL is easy enough. Legally in the US at least to my understanding, you have to do a care/sizing label as well, but it should be quick enough to design. For the hoodies, the print on demand options for inner labels seems more limited. That said, still evaluating if it would just be easier to design my own emoji-ish svgs for the few that I need to save on costs in the long term.

Hi @youdly further question on licensing, in the hypothetical scenario where we want to use an emoji on a physical (purchased) postcard created via a mobile app (imagine a postcard template within an app where the user can write text which could contain emoji) would the attribution be sufficient in the app under the postcard template itself or would you require it on the printed material as well? Asking mainly because the Postcard is full-paper/print and quite inflexible so trying to understand options.
Thank you very much for your input in advance.


Allow Godot To Make Animation Values Use Integers Only

I want to create a NES style game that uses only integer values for all transformations (position, rotation, scale, tweening). I would also  like this to be represented in the GUI as well. Is this on Godot's roadmap?

Something different than discrete mode for animation track? https://i.imgur.com/7IDzLLU.png

I have be able to animate frame by frame by keying the frame I want to display.  have never used the animation modes before. I am guessing Discrete/Continuous modes are for motion curves during animation transformations.
I want the actual values calculated to not produce decimal/floating point values at all. I believe I have been able to do this using GDScript but for some reason, in the GUI, still appears as a decimal/floating point number. Which makes me believe it wasn’t actually converted to an integer.

As far as I know you should just use discrete mode to achieve what you want.

I’ll check it out today and let you know if it does what I want it to do. To clarify, in the NES days, no animation was done using flosting point values. My goal is to replicate that look.

... Actually it's almost 5 am where I am, but I decided to have a quick look. No, discrete does not do what I want. I want to be able to benefit from transformation interpolation, but I want the interpolated frames to be only integer based and fall on a whole pixel. continuous mode allows for some pixels to not fall on a whole pixel.
I want to make my game pixel-perfect. I have seen games that don't do what I am asking and it creates a high resolution look that does not match the NES-like games that I want to create.

What about pixel snap? It makes float positions irrelevant.

Another ghosted issue 👻👻
If someone still wants this, make a new proposal on the official proposals repository.


(GH-190) Remove username/password usage

Description
This PR addresses #190.
Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Codecov Report

Merging #274 into develop will increase coverage by 0.13%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #274      +/-   ##
===========================================
+ Coverage    77.20%   77.34%   +0.13%
===========================================
  Files           54       54
  Lines         1132     1130       -2
  Branches       135      135
===========================================
  Hits           874      874
+ Misses         237      235       -2
  Partials        21       21

Impacted Files
Coverage Δ

...itReleaseManager.Core/Options/BaseVcsSubOptions.cs
66.66% <ø> (+26.66%)
:arrow_up:

Continue to review full report at Codecov.

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

@akordowski thanks for getting this done!  Great work on getting the docs updated as well!


[terra-tabs] Update uncontrolled responsive-element to controlled responsive-element

Summary
resolves #969

Changed to tech-only since we've treated the other responsive-element PRs as tech only.


Peptide omega failing for PDBe entry 5TIG

The validation plot for the PDBe entry 5TIG does not show pept. omega values. We are getting the following error after running mc.peptide_omega_analysis:
EXCEPTION RAISED IN peptide_omega_analysis, RuntimeError: index out of bounds

This happens when loading the cif file but not the pdb file.

Fixed in 1f2ee51ade2ce6b5ad013183644a6bfbd9aacbd0


Ingest API returns 200 even though doc mapper parse error occurred in Quickwit Instance

Describe the bug
The Ingest API returns status_code=200 and  num_docs_for_processing, even though no document was actually ingested.
The Quickwit Instance log shows that a doc mapper parse error occurred because there was no timestamp in the data. However from the client's side we get status_code=200 along with num_docs_for_processing so we are led to believe that the documents were successfully ingested.
Steps to reproduce (if applicable)
Steps to reproduce the behavior:

Call Ingest API
Example: Python code

response = requests.post(
                "<IP_ADDRESS>:7280/api/v1/test_index/ingest?commit=force",
                headers={"content-type": "application/json"},
                data=data
            )

print(response.status_code) # 200
print(response.text) # { "num_docs_for_processing": 22 }

Check Quickwit Instance running on <IP_ADDRESS>:7280

...
2024-08-28T09:39:37.929Z  WARN quickwit_indexing::actors::doc_processor: doc mapper parse error: the document must contain field "timestamp field is required" index_id="code-meta" source_id="_ingest-api-source"
...
2024-08-28T09:39:37.936Z  INFO index-doc-batches{index_id=code-meta source_id=_ingest-api-source pipeline_uid=01J6BRSCJ843ANR9RKF941KT0N workbench_id=01J6C5NQTAJY6DV91TB5PFHAHK}:publisher{split_update=SplitsUpdate { index_id: "code-meta", new_splits: "", checkpoint_delta: Some(_ingest-api-source:∆(ingest_partition_01J6BRQBP10KVEQMK5RHTY7F2F:(00000000000000000124..00000000000000000147])) }}: quickwit_indexing::actors::publisher: publish-new-splits new_splits=[] checkpoint_delta=Some(_ingest-api-source:∆(ingest_partition_01J6BRQBP10KVEQMK5RHTY7F2F:(00000000000000000124..00000000000000000147]))

Expected behavior
From the Quickwit instance log you can see that no splits were created. However the client is unaware of the fact.
If no documents were ingested due to an error from the Quickwit instance, the status_code should be something like 500.
Configuration:
Please provide:

Output of quickwit --version
Quickwit 0.8.1 (x86_64-unknown-linux-gnu 2024-03-29T14:09:41Z e6c5396)
The index_config.yaml

# ============================ Node Configuration ==============================
#
# Website: https://quickwit.io
# Docs: https://quickwit.io/docs/configuration/node-config
#
# Configure AWS credentials: https://quickwit.io/docs/guides/aws-setup#aws-credentials
#
# -------------------------------- General settings --------------------------------
#
# Config file format version.
#
version: 0.7

cluster_id: ${QW_CLUSTER_ID}
#
# Node ID. Must be unique within a cluster. If not set, a random node ID is generated on each startup.
#
# node_id: node-1
#
# Quickwit opens three sockets.
# - for its HTTP server, hosting the UI and the REST API (TCP)
# - for its gRPC service (TCP)
# - for its Gossip cluster membership service (UDP)
#
# All three services are bound to the same host and a different port. The host can be an IP address or a hostname.
#
# Default HTTP server host is `<IP_ADDRESS>` and default HTTP port is 7280.
# The default host value was chosen to avoid exposing the node to the open-world without users' explicit consent.
# This allows for testing Quickwit in single-node mode or with multiple nodes running on the same host and listening
# on different ports. However, in cluster mode, using this value is never appropriate because it causes the node to
# ignore incoming traffic.
# There are two options to set up a node in cluster mode:
#   1. specify the node's hostname or IP
#   2. pass `<IP_ADDRESS>` and let Quickwit do its best to discover the node's IP (see `advertise_address`)
#
listen_address: ${QW_LISTEN_ADDRESS}
#
# rest:
#   listen_port: 7280
#   cors_allow_origins:
#     - "http://localhost:3000"
#   extra_headers:
#     x-header-1: header-value-1
#     x-header-2: header-value-2
#
# grpc:
#   max_message_size: 10 MiB
#
# IP address advertised by the node, i.e. the IP address that peer nodes should use to connect to the node for RPCs.
# The environment variable `QW_ADVERTISE_ADDRESS` can also be used to override this value.
# The default advertise address is `listen_address`. If `listen_address` is unspecified (`<IP_ADDRESS>`),
# Quickwit attempts to sniff the node's IP by scanning the available network interfaces.
# advertise_address: <IP_ADDRESS>
#
# In order to join a cluster, one needs to specify a list of
# seeds to connect to. If no port is specified, Quickwit will assume
# the seeds are using the same port as the current node gossip port.
# By default, the peer seed list is empty.
#
# peer_seeds:
#   - quickwit-searcher-0.local
#   - quickwit-searcher-1.local:10000
#
# Path to directory where temporary data (caches, intermediate indexing data structures)
# is stored. Defaults to `./qwdata`.
#
# data_dir: /path/to/data/dir
#
# Metastore URI. Defaults to `data_dir/indexes#polling_interval=30s`,
# which is a file-backed metastore and mostly convenient for testing. A cluster would
# require a metastore backed by Amzon S3 or PostgreSQL.
#
# metastore_uri: s3://your-bucket/indexes
metastore_uri: s3://${MY_BUCKET}/qw_indexes
# metastore_uri: postgres://username:password@host:port/db
#
# When using a file-backed metastore, the state of the metastore will be cached forever.
# If you are indexing and searching from different processes, it is possible to periodically
# refresh the state of the metastore on the searcher using the `polling_interval` hashtag.
#
# metastore_uri: s3://your-bucket/indexes#polling_interval=30s
#
# Default index root URI, which defines where index data (splits) is stored,
# following the scheme `{default_index_root_uri}/{index-id}`. Defaults to `{data_dir}/indexes`.
#
# default_index_root_uri: s3://your-bucket/indexes
default_index_root_uri: s3://${MY_BUCKET}/qw_indexes
#
# -------------------------------- Storage settings --------------------------------
#
# Hardcoding credentials into configuration files is not secure and strongly
# discouraged. Prefer the alternative authentication methods that your storage
# backend may provide.
#
# storage:
#   azure:
#     account: ${QW_AZURE_STORAGE_ACCOUNT}
#     access_key: ${QW_AZURE_STORAGE_ACCESS_KEY}
#
  # s3:
#     access_key_id: ${AWS_ACCESS_KEY_ID}
#     secret_access_key: ${AWS_SECRET_ACCESS_KEY}
    # region: ${AWS_REGION}
#     endpoint: ${QW_S3_ENDPOINT}
#     force_path_style_access: ${QW_S3_FORCE_PATH_STYLE_ACCESS:-false}
#     disable_multi_object_delete: false
#     disable_multipart_upload: false
#
# -------------------------------- Metastore settings --------------------------------
#
# metastore:
#   postgres:
#     min_connections: 0
#     max_connections: 10
#     acquire_connection_timeout: 10s
#     idle_connection_timeout: 10min
#     max_connection_lifetime: 30min
#
# -------------------------------- Indexer settings --------------------------------

indexer:
  enable_otlp_endpoint: ${QW_ENABLE_OTLP_ENDPOINT:-true}
#   split_store_max_num_bytes: 100G
#   split_store_max_num_splits: 1000
#   max_concurrent_split_uploads: 12
#
#
# -------------------------------- Ingest API settings ------------------------------
#
# ingest_api:
#   max_queue_memory_usage: 2GiB
#   max_queue_disk_usage: 4GiB
#
# -------------------------------- Searcher settings --------------------------------
#
# searcher:
#   fast_field_cache_capacity: 1G
#   split_footer_cache_capacity: 500M
#   max_num_concurrent_split_streams: 100
#   partial_request_cache_capacity: 64M
#   max_num_concurrent_split_searches: 100
#
# -------------------------------- Jaeger settings --------------------------------

jaeger:
  enable_endpoint: ${QW_ENABLE_JAEGER_ENDPOINT:-true}

Hi, @dkim94, thanks for the report.
The quickwit 0.8 ingest REST API does not validate documents. We have been working on a new ingest REST API called ingest V2, which allows Quickwit to validate documents.
If you want to try it, check the internal docs, and use the elasticsearch bulk API. If some documents are invalid, Quickwit will return a 200 response with errors per document.

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

hum, for missing timestamps it won't return an error just yet, see https://github.com/quickwit-oss/quickwit/issues/5164

Hi, @dkim94, thanks for the report.
The quickwit 0.8 ingest REST API does not validate documents. We have been working on a new ingest REST API called ingest V2, which allows Quickwit to validate documents.
If you want to try it, check the internal docs, and use the elasticsearch bulk API. If some documents are invalid, Quickwit will return a 200 response with errors per document.

Thanks for the reply. I was also looking for the ES compatiple API, guess I got lucky. Thanks!

hum, for missing timestamps it won't return an error just yet, see #5164

Yes the API doesn't return an error. The Quckwit instance also does not return an error, just a warning. However the logged message show that an error has occurred. I believe we are on the same page with this.


Cask request: Framer Modules

Cask details
Name: Framer Modules
Homepage: https://www.framermodules.com/
Download URL: https://github.com/kysely/framer-modules/releases/latest
Description: Community-driven modules registry and manager for Framer

https://github.com/caskroom/homebrew-cask/pull/38890


Browser ONLY support for Broadcast votes?

So, your broadcast example is listed along with all the browser only requests which I have the requests working well in my javascript app.  However, I can't use the broadcast command:

var steem = require('steem');
var wif = steem.auth.toWif(username, password, 'posting');
steem.broadcast.vote(wif, voter, author, permlink, weight, function(err, result) {
console.log(err, result);
});

I just get the following error.  Which looks like a timeout, but not really sure what might be the problem.  Are these broadcasts able to run in the browser in JS directly with SteemJS or is it requiring server side with node.js or something?  This isn't clear to me, since everything else is client side?  Any help would be great.

Error: 10 assert_exception: Assert Exception
now < trx.expiration:
{"now":"2016-12-13T06:44:18","trx.exp":"2016-12-13T06:43:52"}
th_a  database.cpp:3267 _apply_transaction

Thanks.

You can rather use Steem.js on browser or service side, you don't need server side to broadcast vote if you don't want to. The vote should work, this error come from the blockchain, my guess is that you are voting for a post too old. Can you show me the params you are using?

The error message means that the expiration time of the transaction was already passed by the time it was broadcas,t, so it was rejected by the blockchain. Could be an issue with your local clock being out of sync for example.

Thanks for the ideas guys.  This is using on recent posts, so don't think it too old.  My clock is in sync with an online time service so not sure how that could cause it either.  Either way, Here is my function for this vote, still get the same error response.

$scope.vote = function() {
var wif = steem.auth.toWif('unipsycho', PRIVATE_POSTING_KEY, 'posting');
steem.broadcast.vote(PRIVATE_POSTING_KEY, 'unipsycho', 'countryinspired', 'steemit-photo-challenge-entry-1-reflections', 10000, function(err, result) {
console.log(err, result);
});
}

Can you check on your console network when the vote is broadcasted if the "expiration" time is UTC?

Looks like the expiration time is in UTC, yes, but the now going out is still before the expiration.  I set my local clock back a couple minutes and tried in UTC as well, but the now (shown in the console) is still going out a couple minutes before the expiration for some reason.

OK, so playing around more with this, I set to use a time server to auto sync my clock and timezone then I tried again, got a voting power error instead.  I dropped the voting power and voila, the vote went through, so not sure why the clock is so critical to this, but its working with this, so thanks for the help guys in figuring this out, I hope it gives you a closer idea what went wrong as well.  now I can get back to coding.  haha


Update play-silhouette, ... to 7.0.6

Updates

io.github.honeycomb-cheesecake:play-silhouette
io.github.honeycomb-cheesecake:play-silhouette-crypto-jca
io.github.honeycomb-cheesecake:play-silhouette-password-bcrypt
io.github.honeycomb-cheesecake:play-silhouette-persistence

from 7.0.4 to 7.0.6.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.github.honeycomb-cheesecake" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #71.


use non extractable CryptoKey

https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/generateKey#Parameters
This way even if some script manages to steal refresh token #4 it will not be able to get the private key bound to that token.

Seems legit.


Error message "Unsupported map pattern in the rule left-hand side" reported for definitions not using maps

The compilation of the module
module TST

  syntax Edge ::= Int "-->" Int
  syntax SetOfEdges ::= "{" Set "}"

// the set of vertices of a graph

  syntax Set ::= vertices(SetOfEdges) [function]

  rule vertices({ SetItem(I:Int --> J:Int) G:Set }) => (SetItem(I) SetItem(J) vertices({ G }))

endmodule

reports the following error:
$ kompile tst.k
[Error] Critical: Unsupported map pattern in the rule left-hand side
	Source: File:
/Users/dlucanu/Documents/cursuri/pa/2015/seminar-special/03mar2015/clasa/xxx/././tst.k
	Location: (10,3,10,94)

but the definition does not use maps.
Version of the kompile tool:
$ kompile --version
K framework version 3.6-SNAPSHOT
Git revision: 4023860
Git branch: master
Build date: Tue Mar 03 16:11:32 EET 2015

Improving the error message only partially solves the issue. Remains the problem how to write a function that traverses a list/set/map.

the problem with this rule is that it is nondeterministic and requires associative matching. You are essentially saying that you can match any single element in the set as long as it matches a particular pattern. But the only way to do this is to try and match every element in the set and see if it matches, which in particular leads to (n^2)*k running time, where k is the complexity of the matching algorithm. I believe what you would like to do is simply to iterate through each element in the set and perform a particular transformation on that element, but that's not really what you're doing here. Try the following construct:
rule vertices({ SetItem(E:Edge) G:Set }) => vertices(E) vertices({G})
rule vertices(I:Int --> J:Int) => SetItem(I) SetItem(J)

I see the point: the AC matching is triggered by the fact I mentioned the pattern I:Int --> J:Int in the argument of the rule. Only patterns of the form SetItem(X) S, where X and S are variables, can be done as arguments of sort Set. Correct?
Thanks.

Correct.

Thanks.


Session Catalog Name support modification

Session Catalog Name support modification

Mind keeping the PR description template (https://github.com/apache/spark/blob/master/.github/PULL_REQUEST_TEMPLATE) and filing a JIRA?


Backport:Monitoring Query fails periodically.

https://github.com/rancher/rancher/issues/19564

Can be tested with rc7

Version: v2.2.3-rc7
I still observe that when we load the cluster dashboard page we make 2 query requests to clustermonitorgraphs but now, we no longer get 503 errors. The queries only start when monitoring is ready. I have tested this several times in order too try to reproduce the issue but no longer can. I can also disable monitoring, watch this page, and still avoid 503 or other errors upon the query. I can re-enable again, still watching the dashboard page and not observe and HTTP errors.
Note, there are more details around this here: #19564 but the core issue reported is resolved. We do not get HTTP 503 with clustermonitorgraphs any longer based on my tests.
It's possible the issue may stay open as we might test with a many-node cluster later.

Reopened. There is a question in the v2.3 issue asking about how we still see 2 query requests upon initial load of the cluster dashboard.

@davidnuzik thanks
It should be only one request. Submited a PR to fix it

Thanks Logan.
Version: v2.2.4-rc1
I can now confirm upon initial load of the page we only see one query rather than two.
I was never successful in reproducing the issue. We believe this is because we need a 500-1000 node cluster to do this. (The 503 errors were never observed).
Since I can confirm that we have removed the duplicate query (and smoke tested monitoring and found it to be working fine) I am going to close this v2.2.4 issue.
As for the originating issue in master (v2.3) I will leave this open as in that version we might try to test with a large 500-1000 node cluster at some point. This is yet to be determined.


Option to disable reader interface while reading

Describe your suggested feature
My suggestion is to add a button that will hide the settings panel interface while reading and so that when you accidentally click on the screen, the interface that covers the top and bottom of the screen does not appear, but instead a small button appears in the corner of the screen after clicking on which the interface appears again
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.16.5.
[X] I will fill out all of the requested information in this form.

I like the concept but not the way you're approaching it. Got some alternatives?

@AntsyLich What part of this idea needs to be changed or does everything need to be changed? but if you don't like the alternative suggested below, I think it would be better to suggest to the community in discord so that they can suggest their ideas on this matter
Instead of a separate button that will hide the interface, you can make it so that when you long press the screen with two fingers, the interface hides and appears again when you repeat these actions, or instead of long pressing with two fingers, you can make it so that when you double-press with two fingers, the interface hides and appears again when you repeat these actions

@AntsyLich Or you can swipe to the side with two fingers to hide the interface


Sending and receiving heartbeat messages

Many Websocket applications implements heartbeat messages, called PING/PONG, to keep websocket connection alive.
It will be great if DVWS has an option to add heartbeat messages. That will help testing manual established websocket connections from proxies like ZAP. In order to achieve that, we could use some parameters at ws-socket.php. An example:
ws-socket.php --heartbeat--intervel <ms> --heartbeat-time <ms>

I have being trying to implement that but i am not so familiar with javascript/php.
Thank you :)

Interesting point. I am glad to know that you want to contribute to this project. If you already have a sample code please share a link to it. I will also try to make it work ASAP.

Was there ever example source provided or are there any plans to implement this change?  I do think it would be helpful.

Example code was shared/posted. I agree this is a very helpful change but time and sample code will help implement it faster. I am open to receiving PR for this change and merge it upon review. Sadly, I have not been able to get this done till now. But will look into it now. If you have sample code, please do share.

It seems the change required is to add the below mentioned code after line 95 of ws-socket.php
$router->enableKeepAlive($server->loop, 30);
where, 30 will be accepted from user as a command-line parameter.
I will test this change and if found working will merge it with master.

Yes, it should be that simple and the syntax woks where the time between would just be a variable but if for some reason it doesn't work like that, just let me know.  I have some time and I could get a working script for you then email it over so you can integrate it.

$router->enableKeepAlive($server->loop, 30); does not work and gives PHP fatal error Call to undefined method Ratchet\Http\Router::enableKeepAlive().
This is because enableKeepAlive has to be called on WsServer and not Router. I could not get it done due to my limited knowledge of Ratchet and its RouteCollection. See if you know how to add enableKeepAlive in ws-socket.php. I will keep digging more for now.
Also, composer and react+mysql needs to be upgraded to enableKeepAlive to work. So composer.json should look like this now:
{
    "require": {
        "cboden/ratchet": "*",
        "react/mysql": "*"
    }
}

After that from the location of composer.json run the following command to install it: composer install

I have a lot of work to do tomorrow but Wed I have some extra time, I will see if with the changes you made to .json I can get a functional script working to send over.

Sure. I have created a dev branch with the updated composer.json. Have to clone the dev branch and run the following command to get the latest version of dependencies installed in DVWS: composer install

Heartbeat has been implemented. Refer commit: https://github.com/interference-security/DVWS/commit/6eb1227b19ce6faa3c2f96baf4b5be080cf8140a


[5.1 Compatibility library] Add missing #include

(cherry picked from commit 833d2cd9d395f8669e280e731bbf66424753812d)

Explanation:
The 5.1 compatibility library is failing to build, because it's missing the header #include <cassert>.
Risk: Low
Resolves rdar://63195373
Reviewed by @DougGregor

@swift-ci Please nominate

@swift-ci test


Implement in-memory only mode usefull for testing

Support for in-memory mode to facilitate unit tests, similar to how Realm does it. See MemoryTests.swift for example usage.

Awesome @litso, this sets the stage for a better-than-JSON warehouse option as well. Thanks! I'll review and merge this in the next day or two.

@nickoneill Sounds good! Also cleaned up the project file a bit import the framework instead of just compiling the sources

Merged with some new optional tests and pulled in. Thanks for this!

@nickoneill happy to help out!


24 example fails to compile

is this project abandoned? can we get ci?
error[E0491]: in type &mut QueryTable<'me, Q, <Q as AsyncQueryFunction<'_, 'me>>::SendDb>, reference has a longer lifetime than the data it references
--> /Users/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/gluon-salsa-0.15.2/src/lib.rs:696:28
|
696 |     pub async fn get_async(&mut self, key: Q::Key) -> Q::Value {
|                            ^^^^^^^^^
|
note: the pointer is valid for the anonymous lifetime defined here
--> /Users/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/gluon-salsa-0.15.2/src/lib.rs:696:28
|
696 |     pub async fn get_async(&mut self, key: Q::Key) -> Q::Value {
|                            ^^^^^^^^^
note: but the referenced data is only valid for the lifetime 'me as defined here
--> /Users/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/gluon-salsa-0.15.2/src/lib.rs:684:6
|
684 | impl<'me, Q> QueryTable<'me, Q, <Q as QueryDb<'me>>::Db>
|      ^^^
error[E0491]: in type &mut QueryTable<'me, Q, <Q as AsyncQueryFunction<'_, 'me>>::SendDb>, reference has a longer lifetime than the data it references
--> /Users/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/gluon-salsa-0.15.2/src/lib.rs:703:9
|
703 |         &mut self,
|         ^^^^^^^^^
|
note: the pointer is valid for the anonymous lifetime defined here
--> /Users/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/gluon-salsa-0.15.2/src/lib.rs:703:9
|
703 |         &mut self,
|         ^^^^^^^^^
note: but the referenced data is only valid for the lifetime 'me as defined here
--> /Users/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/gluon-salsa-0.15.2/src/lib.rs:684:6
|
684 | impl<'me, Q> QueryTable<'me, Q, <Q as QueryDb<'me>>::Db>
|      ^^^
error[E0491]: in type &QueryTable<'me, Q, <Q as AsyncQueryFunction<'_, 'me>>::SendDb>, reference has a longer lifetime than the data it references
--> /Users/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/gluon-salsa-0.15.2/src/lib.rs:714:18
|
714 |     pub fn purge(&self)
|                  ^^^^^
|
note: the pointer is valid for the anonymous lifetime defined here
--> /Users/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/gluon-salsa-0.15.2/src/lib.rs:714:18
|
714 |     pub fn purge(&self)
|                  ^^^^^
note: but the referenced data is only valid for the lifetime 'me as defined here
--> /Users/username/.cargo/registry/src/index.crates.io-6f17d22bba15001f/gluon-salsa-0.15.2/src/lib.rs:684:6
|
684 | impl<'me, Q> QueryTable<'me, Q, <Q as QueryDb<'me>>::Db>
|      ^^^
For more information about this error, try rustc --explain E0491.
error: could not compile gluon-salsa (lib) due to 3 previous errors

Closing as a duplicate of https://docs.rs/redis/latest/redis/aio/struct.MultiplexedConnection.html (error is a bug in rustc on newer compilers).
The project is not actively being developed anymore though, though I do try to keep it working.


kubepug is not finding deprecated APIs

@rikatz With implementing #82 we're not able to see deprecations anymore. Thinking about the implementation I was wondering how is kubepug able to identify deprecations as in my mind the Kube API will return whatever object you're requesting but not the original source, is that assumption correct?
I was wondering if you could read from metadata.annotations."kubectl.kubernetes.io/last-applied-configuration" instead and use this as the source for analysis.
Thoughts?

Yep, I'm taking a look at it.
A simple test I'm making is create a Ingress object in k8s 1.14 (which have this as preferred in extensions/v1beta1) and then running pug with swagger from master and the object is not being found.
Will see what's going on

@rikatz I wrote a little helper script to work around the issue. I don't think it's possible to directly retrieve the resource that was applied. As far as I understand Kubernetes keeps an internal state and the Kubernetes API will return that internal state based on what you're requesting, e.g. extensions/v1beta1 or apps/v1. The only way I have found to retrieve what was applied is through the annotation kubectl.kubernetes.io/last-applied-configuration.
I'm still using kubepug with the --input-file feature :)
#!/usr/bin/env bash

namespaces=$(kubectl get namespaces -o=jsonpath="{.items[*].metadata.name}")
apiresources=$(kubectl api-resources -oname --namespaced=true | grep -v bindings | grep -v pod)
kubeversion=v1.16.10
hashmapdir=/tmp/deprecation

rm -rf $hashmapdir

echo "namespace,apiresource,resource,instance" > results.csv
for namespace in $namespaces; do
    for apiresource in $apiresources; do
        resources=$(kubectl get $apiresource -n $namespace -o=jsonpath="{.items[*].metadata.name}")

        for resource in $resources; do
            echo "$namespace $apiresource $resource $instance"
            lastapplied=$(kubectl apply view-last-applied -ojson -n $namespace $apiresource $resource)

            deprecation=$(echo $lastapplied | kubectl deprecations --k8s-version $kubeversion --error-on-deleted --error-on-deprecated --format plain --input-file /dev/stdin 2>&1)
            deprecated=$?

            instance=$(echo $lastapplied | jq -r '.metadata.labels."app.kubernetes.io/instance"')

            if [ "$deprecated" -ne 0 ]; then
                echo "$namespace,$apiresource,$resource,$instance" >> results.csv

                mkdir -p $hashmapdir/$instance
                echo $deprecation > $hashmapdir/$instance/$apiresource.$resource
            fi
        done
    done
done

@estahn Tks for helping in this :)
Yeap, the problem is that annotations, IMO are not a trusted source of information, as they might be changed and masquerade some real information. As far as I remember, those are also added with kubectl apply but maybe not created with kubectl create so this might be a problem.
I'm sorry about taking so long to take a look at this, but thinks at job are in a rush and I'm having not enough time to take care of this, but I'll try to correct this weekend the behavior.
Thank you again for the help :)

I'll write here so I wont forget :)
I'm using now a method called ServerPreferredResources from client-go that finds each preferred API GroupVersion for each object, but it seems that while some are returned well, others aren't. As an example:
extensions/v1beta1
        Deployment --- deployments
extensions/v1beta1
        Ingress --- ingresses
apps/v1
        Deployment --- deployments
networking.k8s.io/v1beta1
        Ingress --- ingresses

This is weird and in the same time, it makes sense as the API needs to keep the compability. Maybe one way is to index the whole group/version/kind instead of just the kind, but this might lead to some undesired behavior. I'm not pretty sure when upgrading from v1.14 to v1.16, as an example the objects get converted or not and also if the program needs, in this case to check only for future deleted api groups. I'll make some further reflections on this.


keyboardShouldPersistTaps={true} Deprecated

Hi!
I'm just reporting a small issue! :)
@mmazzarolo you should change the keyboardShouldPersistTaps={true} to keyboardShouldPersistTaps="always".
'Cause it's deprecated on the console :)
Thx a lot for you lib! :)

Hi @davidroman0O, I'm probably missing something react-native-modal-datetime-picker is not using any ScrollView/ListView/keyboardShouldPersistTaps prop 🤔

Aaaand https://facebook.github.io/react-native/docs/scrollview.html#keyboardshouldpersisttaps
In fact, it's in the ScrollView ! :p

I guess I missed a scrollview on my side...

@mmazzarolo It's not your fault.
It's the react-native-modal-picker i use on my side.
Sorry!! :p

@davidroman0O no worries :)


Using keys as standard value

We use the english (base) translation as the keys in our project. Which means our Localizable.strings files look something like this:
en: "Hello" = "Hello"
es: "Hello" = "Hola"
de: "Hello" = "Hallo"
When we develop, we just write something like NSLocalizableString("Hello", comment: ""), and this automatically makes the "Hello" string appear (since the key is the fallback).
However, when bartycrouch update -x gets executed, translations of the type:  "Hello" = "" are generated, setting the empty string as the fallback for all strings.
Is there a way to tell bartyCrouch to use the Keys as the default value when updating?

Nevermind, just found it.
defaultToKeys = true


Use bosh2 in CI, documentation

Updates example manifest to use take advantage of BOSH 2.0. The example manifest is also used in CI for validation.
Fixes #125, #174

This change is

@johnsonj README.md 285-286 also needs changing

thank you @cholick ! I'll get that updated as well


Using bert unfused zero padding

Looking at code make me a little confused on how zero padding is handled by Bert fp32 implementation (as an example).
After calculating sequence offset tensor, the padding is removed by invokeRemovePadding called in Bert.cc:371.
Then the unfusedAttentionLayer forward is called with the zero padded input, it first call is to cublas GEMM (UnfusedAttentionLayer.cc:100) .
My question is how can it work? Does the input for this GEMM has padding removed or I missed something?
If it does, how can the same GEMM work with zero padded and with padded input?
P.S
I tested by padding  input with zeros, according to sequence length, and check execution results with removed padding feature and without. Results were not the same!

In UnfusedAttentionLayer, we will rebuild padding before running batched gemm.

In UnfusedAttentionLayer, we will rebuild padding before running batched gemm.

I followed the flow of  UnfusedAttentionLayer, in gdb  for the first entry.
The "if_batch_QKV" in line 70 is false, so it go first to GEMM in line 100 (and not the batch GEMM).
The input for this GEMM is derived from  "bert_input_ptr" in Bert.cc:456 as for the first layer (l=0).
The "bert_input_ptr" is compressed (zero pad) by invokeRemovePadding  in Bert.cc:371
So it seems zero pad data is input  to cublas GEMM. Is this a bug?

For normal cublas, we can use normal GEMM.

For normal cublas, we can use normal GEMM.

Yes, but for the first iteration (l=0) this GEMM is receiving compressed zero pad input. It seems it would not result correct output.

For normal GEMM with zero data, we can use cublas.

For normal GEMM with zero data, we can use cublas.

The input for the Gemm is compressed (pad removed). How can a normal GEMM give correct results in this case? Please elaborate.

For padded input, the input shape is [bs, seq_len, hidden]. For zero pad input, the input shape is [token_num, hidden]. For GEMM view, there are no difference except the number of rows.

For padded input, the input shape is [bs, seq_len, hidden]. For zero pad input, the input shape is [token_num, hidden]. For GEMM view, there are no difference except the number of rows.

Thank you for this explanation


AQCU-756: Fixed an issue where the Secondary Y-Axis label wouldn't always render

Coverage remained the same at 86.82% when pulling e510ea82212ad4695083dcb56df5cb8c475eebfd on zmoore-usgs:master into 8c68974081860645c923be596bab9ae93f96c3b0 on USGS-R:master.


Fail early if h5io won't be able to re-instantiate a node

Closes #196

In the long run, it makes sense to me to offload this responsibility onto the storage code itself. But it needs to happen recursively within the state tree, and the real fallback is something like cloudpickle rather than crashing so I don't want to try jamming it into h5io or tinybase -- it's an actual bug right now so let's patch it here and then move the same power somewhere more elegant on a more relaxed timescale.


No such file or directory error thrown when pushing a .c extension file with a 'newline at the end'.

Description
I am not sure if this is a linting error or a different error or my lack of understanding but Please guide me out of this problem.
Encountered an error when adding a newline at the end of c files and pushing it to the Repository, while contributing to some feature changes.

Please take a look at this and help me sort this out.
Thank You!!
Related Issues
None
Questions
No.
Demo
No response
Reproduction
- Select any function say math/base/special
- Change the .c files to contain a newline at the end.
- Push the commit to the repo

Expected Results
No errors are to be expected.

Actual Results
Error is thrown, shown in the screenshot

Version
current version
Environments
Node.js
Browser Version
No response
Node.js / npm Version
No response
Platform
No response
Checklist

[X] Read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.

I was facing this similar error with math/base/special/min package, but after this commit, it was fixed. A similar kind of change is also needed in the math/base/special/max package also.

@kgryte PRs whose all tests have not been passed have been merged. I think we are getting these errors due to this reason.

I was facing this similar error with math/base/special/min package, but after this commit, it was fixed. A similar kind of change is also needed in the math/base/special/max package also.

Mine all tests passed as soon as I removed the extra newlines so I took that way out of this problem.

Everything works well for me, @Shashankss1205 you will have to add #include <stdlib.h> header in example.c created by you.

Everything works well for me, @Shashankss1205 you will have to add #include <stdlib.h> header in example.c created by you.

Okay thanks, I will add the header file and check the code once.

Hello @Pranavchiku , can you please guide me onto how can I remove the error:

I got inactive because I couldn't figure out how to remove this error as it peeked in each and every time.
Please help so that I can again start contributing.

@Shashankss1205 Can you provide a reproducible example? Showing screenshots is not enough to help us debug. We need to be able to actually see the code you are trying to push. If you need to bypass Git hooks, append --no-verify when attempting git push.

@kgryte thank you for your response, I have finally debugged this problem and it wasn't actually a problem of the package but mine personal execution problem.
Thank you for your valuable feedback.

@Shashankss1205 Thanks for the update. I'll go ahead and close this then.


Docker exports/diff/commits are racy

Currently when you do e.gl "docker diff" or "docker commit" the docker daemon reads the live filesystem that the container controls. This is risky since the content there is under the control of the container.
For instance, a container could create a directory /foo, and then after the daemon has started reading the directory switch it out for a symlink with an absolute filename and have the daemon start reading files outside the container. You can also cause the daemon to loop when traversing the filesystem in the same way.
Its also generally risky to have an operation like "docker commit" rely on non-atomic operations like a recursive tar, as its possible that the filesystem changes during the operation.
One solution is to be very careful in all file operations on a live container, using openat() & co rather that path concatenation when recursing in a filesystem. This doesn't solve the atomic commit issue, and unfortunately the go filepath.Walk() call doesn't use openat().
Another solution for btrfs and the lvm backend is to take a snapshot of the container image before doing the diff operation. This would make fs traversion safe and atomic. However, this doesn't work on aufs, (or other union fs:es like overlayfs).

Seems like this one can be closed?

we now freeze I believe during commit https://github.com/docker/docker/pull/6787


Fix the garbage collection for orquesta workflow executions (v3.1)

Cherry pick from https://github.com/StackStorm/st2/pull/4733
Fix logic in identifying orphaned workflow executions which causes long running workflow executions to be canceled. Disable this garbage collection feature for orphaned workflow executions by default.

Merging, to have new packages deployed ASAP


EDA + initial text analysis for MSE

Description
This PR adds scripts to perform EDA (exploratory data analysis) and initial text analysis (looking at top words and ngrams) for Money Saving Expert data.
Closes #1
Closes #5
Instructions for Reviewer
Setup
In order to test the code in this PR you need to:

clone this repo: git clone git@github.com:nestauk/asf_public_discourse_home_decarbonisation.git
checkout to the correct branch: git checkout 01_initial_analysis_mse
Run make install;
Run direnv allow;
Activate the conda enviroment: conda activate asf_public_discourse_web_scraping;

Review
Hey @helloaidank and @lizgzil, thanks a lot for taking the time to review this PR. @crispy-wonton, I've also tagged you as you said you'd like to take a look - feel free to take as much or a little time to look at this, but really appreciate you taking the time.
Scripts to be reviewed:
There are a couple of scripts to be reviewed in this PR.

Getters:

Useful getter utils: asf_public_discourse_home_decarbonisation/getters/getter_utils.py
MSE specific getters: asf_public_discourse_home_decarbonisation/getters/mse_getters.py

Utils:

Plotting utils: asf_public_discourse_home_decarbonisation/utils/plotting_utils.py
Text processing utils: asf_public_discourse_home_decarbonisation/utils/text_processing_utils.py

Analysis scripts:

EDA: asf_public_discourse_home_decarbonisation/analysis/mse/eda_mse_category_data.py
Initial text analysis: asf_public_discourse_home_decarbonisation/analysis/mse/initial_text_analysis_category_data.py

Note that the two files in notebooks/ do not need to be reviewed. They serve only as a helper: you can open the notebooks and run them if any of the steps in analysis scripts does not make sense and you want to take a look at them. To open the files as a notebooks follow the instructions below (also present at the top of the notebook files):
- Run jupytext --to notebook asf_public_discourse_home_decarbonisation/notebooks/mse/name_of_notebook.py
- If the correct kernel does not come up (asf_public_discourse_home_decarbonisation), please run the following in your terminal:  python -m ipykernel install --user --name=asf_public_discourse_home_decarbonisation
Code to run
Could you also please run:

python asf_public_discourse_home_decarbonisation/analysis/mse/eda_mse_category_data.py
python asf_public_discourse_home_decarbonisation/analysis/mse/initial_text_analysis_category_data.py
and let me know if it runs smoothly.

Things to pay special attention to:

The code runs well when we use one of the smallest categories, but when running for the "energy" category, the code might break. What can we do to optimise the steps? Especially, the lemmatising/tokenising steps? Shall I use SpaCy instead of NLTK? The code is much faster since I started using np.vectorize() - but is there anything else I can do? @lizgzil if you don't have much time to look at the PR, it would be great if you could just take a look at this.
Anything in the logic does not make sense?
Should any part of the codebase live somewhere else in the cookiecutter structure? These small pieces of analysis still are the weirdest to organise/refactor for me.

Note that

The results I presented at the project sprint review contained an extended analysis which will follow in a 2nd PR;
I've not yet implemented Liz's suggestion to not lemmatise all words, and to leave out low frequency words.
I think the data needs some extra cleaning - if you have any tips or functions you have implemented in past projects, do let me know.

Thanks a lot in advance!
Checklist:

[x] I have refactored my code out from notebooks/
[x] I have checked the code runs
[ ] I have tested the code
[x] I have run pre-commit and addressed any issues not automatically fixed
[ ] I have merged any new changes from dev
[x] I have documented the code

[x] Major functions have docstrings
[ ] Appropriate information has been added to READMEs

[x] I have explained this PR above
[x] I have requested a code review

@helloaidank , @crispy-wonton and @lizgzil - thanks a lot for your very detailed reviews, they were super helpful! ⭐
As mentioned in the project review meeting this morning, I've created a metaflow pipeline to process the text data - this allows for lemmatisation to happen in chunks and in parallel. @helloaidank I've added a folder called data_processing_flows under pipeline. It has 3 scripts: the flow, utils and requirements - the usual scripts to run a metaflow flow. @helloaidank feel free to have a look before you go on AL, if you have the time. It's not all sorted yet, but the pipeline should run fine.
In test mode:
python asf_public_discourse_home_decarbonisation/pipeline/data_processing_flows/processing_text_data.py --datastore=s3 --package-suffixes=.txt run --max-num-splits 2000 --max-workers 100 --test True
Production mode:
python asf_public_discourse_home_decarbonisation/pipeline/data_processing_flows/processing_text_data.py --datastore=s3 --package-suffixes=.txt run --max-num-splits 2000 --max-workers 100
As usual, you can change the category by passing the mse_category argument.
I'm now going to focus on changing the remaining scripts to reflect these changes.


merges source code from VSO/releases/prod into GitHub repo

Merges source code from VSO/releases/prod into GitHub repo.
npm package version - 0.3.3.

Hi @ignatvilesov, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Vilesov Ignat (Akvelon)). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;