backgroundPosition(align, [align])

The current implementation of backgroundPosition looks like this:
let backgroundPosition = (x, y) =>
  d("backgroundPosition", string_of_length(x) ++ " " ++ string_of_length(y));

Unfortunately, this prevents things like backgroundPosition: center;. Is it possible to support string_of_align() here as well?

backgroundPosition(center) is a shorthand  for backgroundPosition(pct(50.), pct(50.))


'Rhino.Security\Properties\AssemblyInfo.cs' could not be opened 	Rhino.Security-vs2008

Apparently Rhino.Security/Properties/assemblyinfo.cs is missing in the latest version. I do not know whether it is required or not, but building this in vs2008 fails.

Hi all!
I've the same problem. I followed the steps in Howtobuild.txt but AssemblyInfo.cs don't exist. When i run the command: psake.ps1 default.ps1 don't have errors messages (but not sucessful).


Failing to setup cluster with ansible

fatal: [localhost]: FAILED! => changed=false
msg: cephadm is the new official installer. Please, consider migrating. See https://docs.ceph.com/en/latest/cephadm/install for new deployments or https://docs.ceph.com/en/latest/cephadm/adoption for migrating existing deployments.

I'm not sure what you are reporting exactly. That message seems pretty self-explanatory.
By the way, it means you are using the development branch of ceph-ansible. If you know what you are doing you can still pass -e yes_i_know=true to discard this warning.


chore(doc): fix npm link in README

Signed-off-by: Brian Gleeson<EMAIL_ADDRESS>PR summary

PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Improve errror reporting for Neuropixels V1f

It would be helpful to know which probe is not seated properly, if possible.

This would help because probe seating in this headstage is finicky.
Usually some readjustment is needed due to the way these probes sit in the zif connector (not all the way to the end):

This was easier to test and re-adjust in the old library because it had an indicator of which probe was not communicating, as seen here.


Files to include/exclude to display auto-suggestions as we type in

The folders/files in, the relative path to be auto-suggested (from the open folders in the workspace) or the absolute path to be auto-suggested (similar to the windows search) as we type in few characters.

You can get to history at least with the up/down arrow keys.


[TNS 3.0 rc] - xcrun: error: unable to find utility "PackageApplication"

XCode 8.3 deprecated this tool however even when installing 3.0 rc and creating new project it appears it's still trying to use this. Steps to repo:

tns create MyApp --template tns-template-hello-world-ts@rc
cd MyApp
Plug it an actual iPhone, tns devices to get it's id
tns run ios --device <device id>

xcrun: error: unable to find utility "PackageApplication", not a developer tool or in PATH

This issue was moved to NativeScript/nativescript-cli#2725


Optional wrap step

Removed "optional" tag from step title.
Added "skip" button if user has enough balance

how come the builder design seems to have reverted on this build?


[HOLD for payment 2023-08-01] [$1000] Login - The FAB menu is not open when entering the correct magic code on second try

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Navigate to staging.new.expensify.com
On the login screen enter any email account and click Continue
Enter a incorrect magic code
Enter the correct magic code

Expected Result:
The FAB menu in the LHN view should be opened
Actual Result:
The FAB menu is not opened when entering the correct magic code on second try
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] Windows / Chrome
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/67104f6e-59a9-4822-8dae-20bd6d8617f9
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01a7019e80367e460c
Upwork Job ID:<PHONE_NUMBER>757542400
Last Price Increase: 2023-07-12

I am not able to reproduce.

I would able to successfully reproduce using these reproduction steps.

Navigate to staging.new.expensify.com
On the login screen enter a any email account and click Continue
Enter an incorrect magic code
Enter the correct magic code

I am not able to reproduce

Proposal
Please re-state the problem that we are trying to solve in this issue.
While logging in with a new user account, If the magic code is entered twice once with wrong code and then the right one, in the following case when the home page loads up, the fab menu doesn’t open automatically.
What is the root cause of that problem?
For the following case, In the src/libs/actions/Welcome.js file initially "isLoadingReportData" is true due to which when checkOnReady() is invoked on callback of NVP_IS_FIRST_TIME_NEW_EXPENSIFY_USER it return’s without invoking resolveIsReadyPromise() as at this state "isFirstTimeNewExpensifyUser" is true and "isLoadingReportData" is true which satisfies the return condition. After this when checkOnReady() is invoked on callback of IS_LOADING_REPORT_DATA, again it returns without invoking resolveIsReadyPromise() as at this state, value of "isFirstTimeNewExpensifyUser" is changed to false in show() and "isLoadingReportData" is false which again satisfies the return condition.
What changes do you think we should make in order to solve the problem?
Add a if statement in show() function before changing value of "isFirstTimeNewExpensifyUser" to false, to check whether "isLoadingReportData" is false.
if (!isLoadingReportData) {
isFirstTimeNewExpensifyUser = false;
}

Summary of pay outs once we get to the end of the regression period.

Issue reporter: N/A
Contributor: @tienifr $1,000 (no bonus)
Contributor+: @allroundexperts $1,000 (no bonus)

Upwork job is here.

Ah yep, you are right. It looks like the automation failed but I checked the PR to confirm.

Circling back for payments. @tienifr has been paid via Upwork. @allroundexperts I'll check to see if you've submitted via NewDot, but if not, please do that and then I can close this issue once approved there. Last up, I agree on your point about not needing a regression.

Great thanks! This is approved for payment on NewDot so I'm closing this one.


Fix No way to link external jar files to single bal files

Purpose
Fixes https://github.com/ballerina-platform/ballerina-lang/issues/20309

Codecov Report

Merging #20371 into release-stage will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release-stage   #20371   +/-   ##
==============================================
  Coverage          15.21%   15.21%
==============================================
  Files                 50       50
  Lines               1341     1341
  Branches             208      208
==============================================
  Hits                 204      204
  Misses              1121     1121
  Partials              16       16

Continue to review full report at Codecov.

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

Fixes #20362 as well


:find incorrectly searches parent directory of path

Describe the bug
:find and similar functions incorrectly searches the parent directory of a relative path.
To Reproduce

Create the following directory structure so that dir2 is the working directory

dir1
├── dir2
│   └── base.txt
└── file.txt

Run vim --clean -c 'set path=../include' base.txt
execute :find file.txt
file.txt is loaded, even though the path points to the nonexistent ../include directory.

Expected behavior
An error such as the following should be produced
E447: Can't find file "file.txt" in path
Environment (please complete the following information):
Reproducible on an ubuntu 20.04 machine with vim 8.1 patches 1-2269.
The correct behavior is observed wtih vim 7.4 patches 1-160

The new behavior was introduced in 7.4.885.

Hm, Vim checks, whether the directory given by the path option does exist, and if not, it starts adding the beginning of the path option to the path to start looking for, which means, vim will search in /path/to/dir1/dir2/... This seems to be done on purpose, so not sure why this is done.
Here is a simple patch to fix this behaviour, not sure it works correctly:
diff --git a/src/findfile.c b/src/findfile.c
index a72fe45ad..c335f4198 100644
--- a/src/findfile.c
+++ b/src/findfile.c
@@ -579,6 +579,12 @@ vim_findfile_init(
            if (p > search_ctx->ffsc_fix_path)
            {
                len = (int)(p - search_ctx->ffsc_fix_path) - 1;
+               // do not add '..' to the path and start upwards searching
+               if (STRNCMP(search_ctx->ffsc_fix_path, "..", 2) == 0)
+               {
+                   vim_free(buf);
+                   goto error_return;
+               }
                STRNCAT(ff_expand_buffer, search_ctx->ffsc_fix_path, len);
                add_pathsep(ff_expand_buffer);
            }

(let's see if this breaks anything)

hm, perhaps it also needs to check that stopdirs is null.


Additional PHP 8 fixes

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
-

@yiisoft/core-developers, @yiisoft/reviewers need fresh pair of eyes. Seems I've made a mistake with all the effort somewhere and can't see where it is :(


Good job, but what with the options to scrapper posts , like, comments and more.. as logged user?

As name shows this only gets pages visible for not logged in user. I am currently scraping posts, comments and similar data, but by web socket. I suggest to use
Chrome Extension TypeScript Starter

https://github.com/chibat/chrome-extension-typescript-starter


AddGradleWrapper should support custom distributions urls

The AddGradleWrapper  recipe should allow users to customize the distributionUrl

--gradle-distribution-url
The full URL pointing to Gradle distribution ZIP file. Using this option makes --gradle-version and --distribution-type obsolete as the URL already contains this information. This option is extremely valuable if you want to host the Gradle distribution inside your company’s network.

This is critical for Enterprise environments where https\://services.gradle.org/distributions is usually blocked
As stated in the official documentation, If given, the version and distribution parameters are not needed/ignored as --gradle-distribution-url is an absolute url (they are currently mandatory in our recipe)

I like this suggestion; particularly because it would offer a clear path for organizations that do not yet use a custom distribution url internally to adopt one with ease. It's on the backlog for now, but it seems manageable for a community contribution at first glance.

It should be noted that the behavior here should act in the same manner as that of the gradle wrapper command. If distributionUrl is present, then it should be taken as is with all other options being ignored.

@timtebeek, I'm not sure that I agree with this one being a good first issue. The initial change is relatively straight forward, but it's going to leak into the GradleWrapper utility class for validating the distribution and has some side effects that the requested distributionUrl must be reachable and valid. It's unfortunate, but the gradle wrapper jar only exists within another jar that exists within the full Gradle distribution. You can see some of this madness happening in the GradleWrapperJar utility class.
I'd appreciate your feedback as well if you think that scope creep kind of pulls it out of the good first issue category.

One more thing that I noticed is that we call https://services.gradle.org/versions to discover versions.  While this endpoint is very convenient for us,  this is probably not available in an Enterprise environment and we should consider parsing the raw output of https://services.gradle.org/distributions/  instead

@yeikel, I think the json data format is a lot more consumable for usage. While it's possible to use the HTML data format, we also haven't had any reports of that particular issue.
The short of it is that I think once this feature has been implemented as described, it'll satisfy those strictest of enterprise environments anyway. It's probably more likely the case that in those environments they are packaging their own private distributions. With the handling of an exact distributionUrl, it should completely bypass all version resolution logic and just add the exact Gradle wrapper specified. So in this case, no parsing would be necessary, but the user will have to always specify the exact full url to their desired distribution. This is the same behavior as what Gradle expects for end users to have to deal with.

@yeikel, I think the json data format is a lot more consumable for usage. While it's possible to use the HTML data format, we also haven't had any reports of that particular issue.
The short of it is that I think once this feature has been implemented as described, it'll satisfy those strictest of enterprise environments anyway. It's probably more likely the case that in those environments they are packaging their own private distributions. With the handling of an exact distributionUrl, it should completely bypass all version resolution logic and just add the exact Gradle wrapper specified. So in this case, no parsing would be necessary, but the user will have to always specify the exact full url to their desired distribution. This is the same behavior as what Gradle expects for end users to have to deal with.

I agree that users could hardcode the full URL as you mentioned for the initial generation, but the Update feature discussed in #2650 would not be available under that condition. In that sense, the update feature will also need to also take a full URL

@yeikel, yes, you are correct. The UpdateGradleWrapper would need a very similar mechanism to what we've discussed here.

I've addressed this issue in this commit:
https://github.com/openrewrite/rewrite/commit/07685db42c5476cba8a146ae7c2fab662e806d38


DwC Export, new fields, refactor etc.

DO NOT PULL

Codecov Report

Merging #2300 (83082a4) into development (34c0558) will decrease coverage by 16.45%.
The diff coverage is 64.37%.

@@               Coverage Diff                @@
##           development    #2300       +/-   ##
================================================
- Coverage        87.82%   71.36%   -16.46%
================================================
  Files             1802     1412      -390
  Lines            62038    39712    -22326
================================================
- Hits             54482    28342    -26140
- Misses            7556    11370     +3814

Impacted Files
Coverage Δ

...ntrollers/tasks/exports/nomenclature_controller.rb
50.00% <ø> (ø)

app/controllers/users_controller.rb
96.05% <ø> (ø)

app/models/controlled_vocabulary_term.rb
96.42% <ø> (-3.58%)
:arrow_down:

app/models/geographic_item.rb
46.09% <0.00%> (-36.83%)
:arrow_down:

app/models/geographic_item/point.rb
78.57% <ø> (-14.29%)
:arrow_down:

app/models/identifier/global/orcid.rb
22.22% <ø> (-77.78%)
:arrow_down:

...al_rank/icn/higher_classification_group/kingdom.rb
57.14% <0.00%> (-42.86%)
:arrow_down:

app/models/taxon_name.rb
66.61% <ø> (-22.26%)
:arrow_down:

lib/catalog/collection_object.rb
9.52% <0.00%> (ø)

app/models/georeference/google_map.rb
30.00% <12.50%> (-70.00%)
:arrow_down:

... and 885 more

Continue to review full report at Codecov.

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

Can we synchronize this with the development branch?

Will do today.
On Fri, Aug 20, 2021, 7:11 AM Dash @.***> wrote:

Can we synchronize this with the development branch?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SpeciesFileGroup/taxonworks/pull/2300#issuecomment-902647684,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAFQSCL7YX7ELHUUARZNQDT5ZBAPANCNFSM46GVURWA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Historical problem but could produced data filename extension be .tsv or .txt? Currently it is .csv and Ruby's csv module is involved in the process, but columns separator is set to \t which no longer makes it coma-separated.

The active jobs this PR introduced need to change the amount of work done per job. Processing entire scopes will block the worker until done. This is more noticeable on sandboxes which run without replicas, but in production it could also become problematic after 5 jobs are running concurrently.
The importer does this when running asynchronously when importing (maybe not when staging but in general it is not a too lengthy operation).
We may also consider alter our production deployment to have workers dedicated to specific queues, but even with this it is not a good idea to have very long running jobs.

Historical problem but could produced data filename extension be .tsv or .txt? Currently it is .csv and Ruby's csv module is involved in the process, but columns separator is set to \t which no longer makes it coma-separated.

"c" for "character"  I think, though many (most?) treat it as comma - https://www.ibm.com/docs/en/mufz/4.1?topic=files-character-separated-value-csv-reports

The active jobs this PR introduced need to change the amount of work done per job. Processing entire scopes will block the worker until done. This is more noticeable on sandboxes which run without replicas, but in production it could also become problematic after 5 jobs are running concurrently.

Are you thinking of both job types, or one in particular? I'm not sure of the best way forward here.

In theory the download can be much much faster if we write faster empty column detection and add a couple more tweaks (it's just downloading a single table).  I started to work on this but didn't resolve in it in SQL instead of Ruby.  We could also shell out and manipulate the file that way if needed.  There are other things we can do as well, but download generation in general shouldn't be an issue once indexing is done in the background.
I'm not sure how we'd go about composing the download in small jobs.  I suppose we could break composition into 2k records at a time, and know the job is done when totals add up.
We could limit the re-index capabilities greatly.  We'll re-index the whole dataset in the background after deploying version updates, so these aren't going to be super important, they are more just to transition us for small sets of records.  We could limit them to small runs.  Not sure if this what you're getting at.
We can speed re-indexing for large shapes by 3/4 at least I think.  Though this won't result in short times for large-re-indexing, but it's something we know we can do.

I pressed [10K] there more than an hour ago and also yesterday (sandwich sandbox). I also uploaded a dataset and still not staging. Does the indexer have a way to tell when refresh is needed or it always redoes everything?
Download generation is probably fine, I think it always completed relatively fast.

Does the indexer have a way to tell when refresh is needed or it always redoes everything?

It does the all again, those buttons were largely for testing purposes.  We'll isolate them I think, and limit the re-indexing to datasets smaller than some filter size.
It takes 0.5-8s to re-index a record.  Not much has been done to optimize.  The big changes, as noted, will be deciding to use centroids on large areas or not.


Refresh of Angular app on every mouse move (the pointermove event)

Hello! Seems like adding a ngx-leaflet to the application makes the application to update every mousemove.
Way to recreate:

Deploy any boilerplate, for example, the https://github.com/haoliangyu/ngx-leaflet-starter

Create and register the following component

import {Component} from "@angular/core";

@Component({
    selector: "test",
    template: `<h1>{{componentValue}}</h1>`
})
export class TestComponent {
    _componentValue: String = 'lalala';
    constructor() { }
    set componentValue(value) {}
    get componentValue() {
        console.log('Somebody is getting the value');
        return this._componentValue;
    }
}

Add it somewhere in the application layout near the actual map component

Load the app and see that on every mouse move the TestComponent is redrawn (the get componentValue() of TestComponent is called)

If the map is removed, then such behavior can not be observed

So, it seems like Leaflet makes the entire Angular app to update in reply to pointermove (mousemove) event.

I'm looking at this now. I'm not sure what's causing it but I did reproduce it. At first I was expecting this because the layers binding is using DoCheck and IterableDiffers for change detection, but that shouldn't cause everything to do a dirty check on mouse move. Thanks for bringing this up!

The root cause of the issue is that Zone.js monkey patches a lot of stuff (including mouse events) so that Angular can trigger change detection based on them. Leaflet registers a bunch of those events, so Angular is doing change detection in response.
Zone.js provides a way to get around this by running code outside of angular (https://blog.thoughtram.io/angular/2017/02/21/using-zones-in-angular-for-better-performance.html) which does seem to be the right solution for this situation. I'll implement it and make sure it doesn't cause any other issues and if all goes well I'll roll it into the plugin as a minor release.

@reblace Thank you very much, looking forward to it!

I released a new minor version that should address it. v2.6.0. Please check it out and let me know if you have any issues with it. I did a fair bit of testing to make sure there weren't unintended side effects, but it's hard to cover all potential use cases.

My project is young and therefore my usage of ngx-leaflet is reasonably trivial so far but I just wanted to confirm that at least for me (using Angular 5) the upgrade was seamless and everything has continued to work. Thank you for the time you have put into this project.

@reblace Thank you very much for the fix! The pointermove event is not fired now indeed, but I've noticed that the pointerdown still fires the Angular update (I guess as well as pointerup and pointercancel). As I see this situation - if the Leaflet in intergrated into the Angular application without ngx-leaflet, then it becomes a hell to work with. However, using the ngx-leaflet can provide pain-free work with Lealfet in Angular, as it constraints all the raw-Leafet side-effects.

I don't see any of the events triggering dirty checks. Is your example still exactly the same as the first one you shared?
Also, I rolled an ng5 update into this 2.6 release, which I just realized isn't actually backward compatible. So, I'm going to re-release 2.6 as 3.0 and then release a 2.6.1 that downgrades back to ng4.

Just for some context about my decisions - there is a bit of a balancing act here. If I push too much stuff out of the angular zone, it puts more of a burden on developers to trigger change detection when they are using any of the events in Leaflet. With the more advanced topics like zones, change detection, and differs, I try to avoid forcing them on the casual user cause it leads to a lot of issues being submitted and questions on stack overflow.
My priority with your specific issue was to eliminate the change detection triggering on mousemove since that's way too excessive and crushes performance even when users aren't interacting with anything. I'm willing to accept change detection on click/mouseup/mousedown/window resize since those interactions trigger change detection normally in Angular components.
My long-term plan to help mitigate some of these issues is to expose a lot of the events using EventEmitters and @Output, that way I can internally trigger change detection on those events specifically. But in the interim, I'll probably leave it like it is now (and I'm gonna close this issue).
Thank you for pointing out this issue though, as I didn't even realize how zones worked until I dug into this issue. If you have any other issues, feel free to open new issues or add a comment to this one.


[codespaces] icons of terminals are not preserved on reload

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.56.2
OS Version: MacOSX, Chrome

Steps to Reproduce:

In Codespaces, open a new terminal and switch on Show tabs
Change icon / title of the terminal
Reload the browser tab
-> the tabs show as empty tree items, without icon and title

My suspicion: The IShellLaunchConfigDto lacks the icon property from IShellLaunchConfig, such that the remote backend cannot remember it. In addition, terminals with a config that has an undefined icon are shown as completely blank.

This works in main


Update Superclosure

Just wanted to ask if there was any reason illuminate/support was still requiring superclosure 1.0 instead of 2.0, since we don't need the 5.3 support anyway on 4.2? This is causing conflicts on a project which require Psysh, the latter causing a conflict with it

(Conflict being that Superclosure 1 requires php-parser 0.9 while Psysh and Superclosure 2 use 1.0)

Just wanted to ask if there was any reason illuminate/support was still requiring superclosure 0.9 instead of 1.0

It's not. We're requiring ~1.0.1 in Laravel 4.2.

Yes made a typo, edited my post

And ~2.0 in 5.0. This is disused on my L5 pulls. :)

Yes I know L5 uses 2.0 but I'm talking about 4.2

@Anahkiasen We NEVER update dependencies my major versions in patch releases. That will screw someone over who's relying on the old version.

Oh well, ok

We've done this same thing with a few other dependencies too. Like phpeanstalk and predis.

No yeah thought I'd ask since it's more of an internal dependency and the functionality doesn't change, just the API – since it's all uniformized through the SerializableClosure class. Was worth a shot.

Closures serialized with 1.0.x won't be correctly unserialized with 2.0. So that's another reason we can't do it in a patch release because people's queued jobs may start failing.


More explanation that sign-in is required

'Post' button should be replaced with sign in options to make it clearer to user that sign-in is required. Else they could write a long comment before realising authentication is required, and then give up - annoying.

ysfhfdh


The docker container suddenly stops running and I don't know how to fix it.

Hello,
The error is as below.
Any solution?
Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: error adding seccomp filter rule for syscall clone3: permission denied: unknown.
Thank you.

Hi @leeyunhome, can you try either of these fixes?

https://github.com/dusty-nv/jetson-containers/issues/108#issuecomment-995090398
https://github.com/dusty-nv/jetson-containers/issues/108#issuecomment-962597353


doctrine/form Integration bundle

I was (or actually still am) searching for a nice uploading process within a symfony project. I tried this bundle and thought the implementations are awesome, especially the orphanage. But I miss a lot of other aspects which is fine, this bundle does 1 thing really well instead of all the things only partially.
I see 4 areas necessary for a seamless file handling in a symfony multipage application:

A form type that can add/remove/show one or multiple files
Handling of asynchronous uploads (this is what this bundle does) because input type file feels massively outdated
Attaching files to existing data like doctrine entities
Cleanup after entity deletion

This bundle is really good at 2. but does not touch 1, 3 or 4, that's all left to the individual project.
the VichUploader Bundle handles 3 and 4 but both not really elegant as it is really verbose in entity handling and cleanup only works when entities are deleted directly. There is no check to delete files of which the entity is removed. The Vich uploader bundle also relies on the symfony FileType for uploads which isn't great.
what am I suggesting?
I would like to have a doctrine and a form integration based around this uploader bundle.
doctrine integration
My idea is to create a FileReference doctrine entity that simply has 2 fields.

The mapping name
The file identifier

When the entity is persisted/flushed, then the file must be moved from the orphanage to the actual storage. When the entity is deleted, the file must be deleted as well. There also needs to be a cleanup process to delete files that are no longer referenced.
Building a model like this allows to add one or many file references to any entity simply by using a relation. No magic mapping required.
form integration
Now this is heavily related to the doctrine integration. Simply plopping something like a DropzoneType into any form that uploads one or multiple files to the orphanage and adds FileReference's into a Model would be awesome.
The html part woud just add the identifiers into the form and a data mapper would map those to the correct uploader mapping. The doctrine bundle would move the files into the real storage.
By heavily using mapping of this uploader bundle, this could be entirely storage agnostic.
why am I bringing this up?
What I describe here is a lot of work and those are just ideas i had while researching. So I thought I share those ideas here to discuss. Who knows, maybe everything i described is already possible with other bundles I just haven't found.
Maybe we can even collaborate here.

Hey Marco
Thank you for your contribution!
We do like the idea but our time to work on this is quite limited at the moment 🙈
We'll keep an eye on this and as soon as we had time to look closer, we can discuss our points further over here.
Feel free to add more comments or adapt parts if you need.


BLE cordio status inside MaxIDE 32666FTHR

I am evaluating your MAX32666FTHR platform and IDE.
Could you answer:

Which version of Mbed OS is this built from?
Which version of the ARM PacketCraft cordio BLE is bundled? 2019 seems very old?
Do you support the C++ API, I didn't understand why your BLE demos such as BLE_dats use C rather than C++?
Why are there so many include files in the BLE_dats .c files, and also you seem to include header files from directories in the cordio stack that are not public API's (and paths are missing from the include paths as such). Many includes are from a path ending /include but there are some that are from non /include folders, and seem to be accessing internal code directly from the /sources folders, which seems to break the API abstraction.
The BLE_dats example is terribly complex, and doesn't seem to match up to any of the documentation I have found on the ARM MBED OS/cordio website. Do you have a set of simpler examples with many less include files and much less complex 'knitting' code, that just uses the API directly? All we want to do is send and receive a few bytes of data to a mobile phone, this set of examples look terribly complicated?

A lot to absorb here. Note we are at evaluation stage; if evaluation indicates additional pre-work is required to repackage examples into more useful starting points, that work can sometimes be rolled into future development plans. But it would be nicer if your examples were simpler :-)
I think a useful signpost at this point might be whether there are other simpler examples, whether there are C and C++ examples, and whether there are any plans to take the existing BLE_dats and other BLE examples and wrap them in helpers and surface a 'simple get going quick' API we can all build forward from.
The simplest API for me would be to include ble.h, call an init() function with the node advertisement name, perhaps call a register_attrs() function with a reference to an application specific attribute table that points to attribute variables, and call a tick() function that provides any necessary BLE stack processing. An app can then update attribute variables directly with very low coupling to everything else, and focus on doing what the app is designed to do, rather than getting sucked into understanding what all the moving parts of the BLE cordio stack does.
It might also simplify includes and paths, if our apps only have to include a single header file.
For the majority of cases, that allows anyone evaluating and developing production code, to build a system based on GATT attributes super quickly.
The points about mbed os and cordio version numbering becomes super important if we need to dig into all those moving parts, as we need to make sure we are using the correct version of the docs for the BLE stack that is bundled (as cordio seems to be moving regularly and quite quickly!). If the getting started example is super simple and allows the 80% of simple apps to be built really fast, doc versioning is less important I think.

Thanks for the feedback. It's a delicate balance to keep things simple and flexible at the same time. The BLE_periph is a better example to get started with.
The Cordio library that we use is forked from this repo.
https://github.com/packetcraft-inc/stacks

Thanks @kevin-gillespie and @Jake-Carter I will take a look at the BLE_periph example.
FWIW, I am finding the API's for all the on chip peripherals excellently written and really easy to integrate with, I particularly like the fact that you have provided low level, transactional, sync and async and DMA services for all the ones I have used already.


Layouts

We are going to need layouts for each class and MVC.
If I'm not mistaken, we only have activity_login.xml as our layout and it has the default layout on creation.

I just added some new layouts, fragment layouts,  as well as the new android action bar layout. Can you guys take a look and give some feedback?
For whatever reason I chose to make it a dark theme, but changing it to light is as easy as changing two hex values in the colors.xml file. But you know... if you don't like my design choices I'll probably be heart-broken.


Unsupported SPIR-V version

I was following this guide: https://github.com/intel-analytics/ipex-llm/blob/main/docs/mddocs/Quickstart/install_windows_gpu.md and everything worked as intented until I tried to follow the last example. When I try to compile it, I get the following error:

Also tried with this guide https://github.com/intel-analytics/ipex-llm/blob/main/docs/mddocs/Quickstart/llama_cpp_quickstart.md and happened exactly the same. Im new on this, so if there's a solution I ask to be very specific on how to implement it.

Hi @Pablou2902,
Would you mind running our env check scripts and pasting the output here, as well as providing us with your GPU device name & GPU driver version, to give us more information so that we could better reproduce your problem? :)

Hi,
Here you have the output you requested:
output.txt
About the GPU, I'm currently testing Integrated Graphics performance while trying to run LLM's.
-Device Name: Intel(R) Iris(R) Xe Graphics
-Driver version: <IP_ADDRESS>11

Hi @Pablou2902,.
It seems like your GPU driver version is too old. You could update your GPU driver to the latest one and have a try again :)
Please let us know for any further problems.

Yeah, this definetely worked. Thank you so much for your help!


fix recursive calls for patching

Fixes #579 by making sure recursive calls to the function are stopped

Released as 5.3.4


Extra closing tag being created

If I type
 I expect

Instead I get

Thanks for reporting, I've gotten tons of these already :) Gonna leave this open in hopes of stopping further reports, but I doubt it will.

PS. To fix, just restart Atom and it will go away. It's related to events getting double bound after a version upgrade

@mattberkowitz  restart Atom works fine! :P


Avoid shuffles when merging with Pandas objects

Previously dask.dataframe would convert all Pandas objects into
dask.dataframe objects.  In some cases this causes unnecessary shuffles.
In particular when you join a non-index column of a large dask.dataframe
against a small pandas table the right thing to do is to just move the
small pandas dataframe to all tasks, turning the computation into an
embarrassingly parallel one.
This isn't very clean.  Review welcome.
cc @sinhrks

OK, this has been cleaned up a bit now.  I've extended the embarrassingly parallel approach to cases when we have a dask dataframe with a single partition.


[BUG] localstorage multi-window sessions are broken again.

When you open multiple windows of dive desktop, you get a new session in every one.  Notice how, even if you close the "new version" notification banner, it appears again on next launch.
https://github.com/Kitware/dive/blob/main/client/platform/desktop/background.ts#L34 is not working as intended.

@subdavis, how serious is this bug? How much does it impact users at the moment? And how hard to fix?

Medium serious.
It could really confuse anyone who manages to launch more than one annotator.  Which we know has happened.
It's probably quite a lot of effort to fix.  Not "hard", but 4+ hours at a minimum.


Fix the signature of JNINativeInterface::ToReflectedField

Fixes the signature of JNINativeInterface::ToReflectedField. (The method returned a java.lang.reflect.Method instead of a java.lang.reflect.Field.)
Also removes an unnecessary semicolon in the LibC mac template.

Thanks!


Remove unused Microseconds from System::Clock

Problem
System::Clock has microsecond-resolution code, but nothing actually
uses it.
Change overview
Remove it.
Testing
CI; no change to functionality.
Microsecond unit tests removed.

/rebase


build: update image with deps upgrade

Signed-off-by: Lizan Zhou<EMAIL_ADDRESS>

/retest

seems this is reliably failing with

ragel/Makefile.am:2: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
WARNING: 'automake-1.15' is probably too old.
         You should only need it if you modified 'Makefile.am' or
         'configure.ac' or m4 files included by 'configure.ac'.
         The 'automake' program is part of the GNU Automake package:
         <[http://www.gnu.org/software/automake>](http://www.gnu.org/software/automake%3E)
         It also requires GNU Autoconf, GNU m4 and Perl in order to run:
         <[http://www.gnu.org/software/autoconf>](http://www.gnu.org/software/autoconf%3E)
         <[http://www.gnu.org/software/m4/>](http://www.gnu.org/software/m4/%3E)
         <[http://www.perl.org/>](http://www.perl.org/%3E)
Makefile:343: recipe for target '/b/f/w/external/net_colm_open_source_ragel/Makefile.in' failed


On-premises SOAR end-of-life release note

PLEASE READ
Following a recent back-end update, all contributors with a local clone or fork of our repository are required to run yarn install. This does not apply to direct page edits.

[x] Yes, I've run yarn install
[ ] No, does not apply to me

Purpose of this pull request
This pull request adds a release note announcing end-of-life for the SOAR on-premises solution. We'll place the release note here: https://help.sumologic.com/release-notes-csoar/
Issue: Asana ticket "Write release note for SOAR on-premises end-of-life"

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[x] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

@stacykor, this PR is in draft until I get your feedback.

This PR is now ready for review.

Good suggestions, @kimsauce!

@kimsauce, could you approve this PR?

Thanks, @kimsauce!


[BUG] Numerous application crashes

Your Rocket.Chat.Android version: 2.6.0 beta
Mobile device model: Xiaomi Redmi 3
OS version: MIUI 9.6 (<IP_ADDRESS>) , Global Stable
Your Rocket.Chat Server version: 0.69.0
The application crashes:

When i trying to create a channel,
When i try to view the version of the program in the settings,
When i try to view information about the user in the list of users.

Thanks for informing us @Pitstopper !
Does your application for the FOSS or did you download it from the Play Store?

Hi! I downloaded it in Google Play.

Hi! 2.6.0 beta 2 fixed this issue. Thanks!

@Pitstopper Thanks for informing us too!


Create shared component repository to support both the Devsite and OSS Site

Acceptance Criteria

Setup a repo that houses the UI components that are to be shared across the various docs sites.
Add a first component to the repo, publish it and consume it from the developer site.

Assumptions

Developer site, open source site and the general docs site will have UI that is intended to stay aesthetically and functionally consistent across the sites but with content variations. Some of those components are listed here.
A pleasant and consistent experience across these subdomains of docs is valuable to New Relic users and to the New Relic brand.
The shared components will help prevent a building up tech debt where modifying all the sites requires shotgun surgery across three “same” but in actuality different components in three different repos.

Duplicate of:

https://github.com/newrelic/opensource-website/issues/543
https://github.com/newrelic/opensource-website/issues/544
https://github.com/newrelic/developer-website/issues/438
https://github.com/newrelic/developer-website/issues/439


Question with how to do this on SPA apps

Hi,
I was reading through the docs, and I see that for business transactions, you say that you can keep track of the lock version on the page.
But in your controller, I guess, you need to do the following?
class SomeController {
    public function update(Request $request, SomeModel $model) {

        // since $model is retrieved from the database, it will have the most recent lock...
        // am I right in thinking that we need to manually set the lock version here always?
        $model->lock_version = $request->get('lock_version');

        // This will then throw an exception when the lock version of the database differs from what I got from the $request
        $model->save();
    }
}

Is this correct, or is there a more intelligent way to pass this on?

Yes it true.  the client should always have and send the lock version, and the controller or any client request processor should always specify the version it is mutating just in any possible way like the one you mentioned. Or you can define new decorate methods like saveWithVersion($version...); or override the original save method and send the version through the $options save method signature accepts in eloquent.


PNG are twice bigger than with imageMagick

The PNG output of gulp-responsive are twice bigger than what I get from grunt-responsive (which is using imageMagick).
152x174 image > 3.5KB with imageMagick, 7KB with gulp responsive
With these settings it's a little bit better at 6.7KB
progressive: true,
compressionLevel: 9,
errorOnUnusedConfig: false,
errorOnUnusedImage: false,
errorOnEnlargement: false

Duplicate #34


[libraw] Add 'd' debug postfix

This PR adds a 'd' postfix to the libraw libraries to allow the two versions to be distinguished more easily

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

Thanks!
I bumped the revision of libraw.


Supporting multiple sources for line list data

Canada data set has multiple sources that are linked to a single line list row. Need to support ability to link multiple sources to 1 line list entry.
There can be 1 primary source and multiple secondary sources
Sample set of Canada data:https://docs.google.com/spreadsheets/d/1VCKn28KbJ8-iiZ8ZFIQ8pPnBWefMoA2YMrxaZZDjQDo/edit#gid=0

I can take a look at this on Friday. This is trivial to support for bulk upload, but we'll need to figure out how to integrate this in the single entry form.
@sratcliffe118 / @shroothless -- thoughts on rough UX? From the data side, we represent this concept with a single primary source that must be registered in the DB, and an optional repeated field of "additional sources" with just URLs. Perhaps we should have a UI field that appears, or becomes enabled, allowing adding multiple URL strings after the primary source is selected with the existing form component?

Perhaps we should have a UI field that appears, or becomes enabled, allowing adding multiple URL strings after the primary source is selected with the existing form component?
Agree, product wise i like this approach
@shroothless wdyt?

Sorry for the delay here. That sounds good.
How about something like this:

I think the most salient question is whether these follow-on sources are registered in our database (and, consequently, autocompleted with the same search-style bar). CMIIW, @sratcliffe118, but I think the current plan is merely to accept the URL for these additional sources (and not register these sources/require anything aside from URL).
If that's indeed the plan, perhaps we should style the additional source box distinct from the primary source search-style input?

I think we should be treating all sources in the same way regardless of it there are primary or secondary. So the input approach should be same, and we should require the name of the secondary or tertiary source to also be provided. This will mean we have a consistent database of sources with the same information and structure.
The principle of the source used to create the line list being primary remains
@shroothless @axmb WDYT to this approach?

I think the UX mocks I shared support this approach. Similar to how we will
handle multiple locations for travel.
On Thu, Jul 16, 2020 at 5:42 AM Stephen Ratcliffe<EMAIL_ADDRESS>wrote:

I think we should be treating all sources in the same way regardless of it
there are primary or secondary. So the input approach should be same, and
we should require the name of the secondary or tertiary source to also be
provided. This will mean we have a consistent database of sources with the
same information and structure.
The principle of the source used to create the line list being primary
remains
@shroothless https://github.com/shroothless @axmb
https://github.com/axmb WDYT to this approach?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/open-covid-data/healthmap-gdo-temp/issues/447#issuecomment-659300101,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQCTZTFAYFYM2M5LJIFVS63R33DQVANCNFSM4ORTKIIQ
.

--
Shruti Chandra
UX Manager
<EMAIL_ADDRESS>212-565-3818

Sorry for the delay -- let this one backburner for a bit. I don't think we want to register these sources explicitly in our database for bulk/automated ingestion. For those mechanisms, we have many secondary sources listed, and those will often list their sources themselves. As an example, consider this entry from the India data:
                {
			"agebracket": "",
			"contractedfromwhichpatientsuspected": "",
			"currentstatus": "Hospitalized",
			"dateannounced": "23/07/2020",
			"detectedcity": "",
			"detecteddistrict": "Champhai",
			"detectedstate": "Mizoram",
			"entryid": "196659",
                        [...],
			"source1": "https://twitter.com/dipr_mizoram/status/1286114571321659392",
			"source2": "https://twitter.com/dipr_mizoram/status/1286114595673788417",
			[...]
		},

So we'd end up with thousands of sources in our DB, each effectively used once and containing only the URL.
I think it'd be fine to register additional sources entered manually, but not through bulk/automated ingestion. It'd make the data model a little weaker (as compared to asserting that an additional source contains an official registered UUID), but we can do it if we want additional sources registered for individually entered data.

@axmb
As long as we are storing the raw data source I am fine with this approach for MVP.
If we find the secondary source is a prominent use case we need to store for ADI then we can reassess down the road
Approach SGTM

Updating the state here: this is implemented and in-use for ADI.
It isn't implemented for manual entry (single or bulk), though it'd be quick to add for the latter.

Given the reliance on ADI/backfills with the current data set, which fully supports this, I think it's reasonable to categorize this as a P2. I'll shuffle those labels.


hi, i'm confused of the timestamp of tim5XX in ROS2.0

the published topic laserscan in ros include header.timestmp, but i'm confused that the header.timestmp is the timestamp of the first point or the last point? ,so i can  calculate for every point . thanks.

It is the timestamp for the first point of the published point cloud.


Add Flagging Tags to Filters

Problem
This issue is dependent on #91 . Users will be able to flag cases (See #91 ), and tag unresolved issues to the UI. These flags might include Urgent, Wrong Location, Wrong Incident, Upset Client, and Complaint. Users need a quick way to identify cases with these tags.
Describe the solution
Add tags to the list of standard filters so that users can quickly identify cases that need special attention. Tags should be implemented using a boolean OR logic. E.g. Clicking "Urgent" and "Wrong Location"

Approved.


Some Exception

This feature is implemented using reflection. If you see this exception, something in your setup is not standard.

device: Lenovo Lenovo L19041, API 28

method: carbon.widget.EditText.setCursorColor(...)
cause: java.lang.NoSuchFieldException: No field mCursorDrawable in class Landroid/widget/Editor; (declaration of 'android.widget.Editor' appears in /system/framework/framework.jar!classes2.dex) at getDeclaredField(Class.java:-2)

This method was removed from Carbon a long time ago. You seem to be using the version that is still available on Maven. I recommend just building the master branch of this repository either manually or with JitPack - it's stable and contains plenty of fixes.

Duplicate of #424


Line Chart disable extra values!

Hello, I'm currently using your lib. But would you like to know if you have to remove the extra numbers that the LineChart chart leaves ?, I just wanted it to have the numbers I pass on the date.
I would like to remove the ones that are in red in the image:

There isn't an API for that right now, but I would welcome a PR.

Well, first sorry for my English, I'm using a translator because I'm Brazilian and I do not speak native English.
I wonder, what is this PR?
I would also like to know if the library uses an external api to create these statistics or not ?, because if everything is created inside the library, I have enough interest in trying to create this method of hiding these values. Well, I'm sure a lot of people are probably going to have this same need that I have, and I'd really like to try to help with this.

Sounds great. PR is pull request. It's a way for you to send me any changes you make to your clone of this library.

@leommh  Just to confirm, the new api will hide every middle values except the highest and the lowest. Hope this is what you want.
Please confirm so that I can submit a PR.

@simransinghkataria In fact I wanted it to only display the values I passed to the chart, but I saw that these values that stay in the middle are required for when you have many values in the chart. So I ended up helping develop an onPress in points to display the excerpt value of each point. In my case that solved.
Thanks for your time, I believe this option to hide the middle values will be useful for some situations, so I think it would be a good addition.


You guys better remove this minimum fixed width it is getting in my progress when working with my projects. :(

VSCode Version:
OS Version:

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

/needsMoreInfo

@AidenWebsploit do you happen to be using a multimonitor setup?


Piranha Embedded - redundant initialization

Hi,
i was playing with Piranha embedded (20.7.0) and i stumbled upon a problem while trying your example.
EmbeddedPiranha piranha = new EmbeddedPiranhaBuilder()
    .servlet("SnoopServlet", SnoopServlet.class.getName())
    .servletMapping("SnoopServlet", "/SnoopServlet")
    .build()
    .initialize()
    .start();

.initialize() step contains redundant calls to many methods already executed in .build() step, breaks on status check where it expects SETUP value. After build step, app is already in INITIALIZED status.
I would create PR but i am not sure what the desired behaviour is just by looking at Piranha api.  My guess would be that build and initialize steps are not balanced well in this case.

Thank you for trying out the example ... unfortunately it did not get updated ... the initialize method call is no longer necessary as the build method call already takes care of it ..


Segmented control tend to be different when landscape mode.

Hi, the fluid in selectedIndex when in portrait mode and landscape mode are not the same.

I have the same problem. Was able to workaround it by observing rotation changes (UIDeviceOrientationDidChange) and doing this when change detected:
segControl.reloadData()
let idx = segControl.currentSegment
segControl.setCurrentSegmentIndex(1, animated: false)
segControl.setCurrentSegmentIndex(idx, animated: true)
It's a dirty workaround, but it does the trick for now.


Question about Ansible

Hi Adam
I was looking at your homelab diagram. Impressive.
I have a question: what do you use Ansible for? Is that the first VM you set up, and from there using playbooks to spin up the rest of the virtual machines?
I am considering to first install AWX on a Debian machine, and then use that to build up the entire network, including setting up Proxmox. What do you think?

Hello Jan! Thank you very much! I have setup pretty much all the VMs manually before I bumped into AWX. Doing it the way you described it would be a lot more elegant. My ansible setup is an afterthought and I am yet to find a really good use case for it. With that said, I am planning to automate the configuration management of the telegraf agents with it at some point.
I have also added Omada SDN components and a third cluster node since the last update, I will update the documentation when it is fully configured. :)

Sorry for bumping this way... But I have a question about glusterFs performance and SSD wearness...
For many reasons I can't use SFP cards. I do not plan any  much data consuming implementatkons in my lab, but i have found many different opinions about glusterFS speed and performence, especally on 1GBit lines. In my old hardware planned for servrs i have only 2x 1Gbit cards...
can you share with me your experience from your lab functionality?
Thank you so much

Hello @polachz!
SSD wear never caused any operational issues on my gluster volume. With that said, my consumer grade SSDs started to show their age after 3-4 years of use.
1Gbit may work with a very light use case, but it will be a serious bottleneck if you add more than a few VMs. My 2.5GBit USB adapters worked surprisingly well, consistently pushing data around 1.8-2Gbits, with occasional peaks around the advertised speed. Bonding two gigabit links may also help, but it never worked well on my setup. I have used the additional 1Gbit links to facilitate cluster and VM traffic instead. This was my sweetspot:

2.5 Gbit link dedicated to gluster storage.
1 Gbit intel nic dedicated to VM traffic.
1 Gbit realtek nic dedicated to PVE and other management traffic.

I hope this helps. :)

I'm also closing this issue, as Ansible never became a core part of this setup.


Media

Media tab is a generic feature in spurtcms currently placed under channels,but if we could create it as new tab that would be accessed throughout the application, will be excellent

Hello @cms-coder, As a developer, I agree that creating a new Media tab accessible throughout the application would be an excellent feature. This would allow users to easily access and manage media assets across different parts of the application, improving the overall user experience.
We will implement this feature shortly.

This suggestion was implemented. The media tab was made as a generic tab.

Thank you


Error

after running the code it only prints me the number of vehicles and the time taken, it does not give me the path of the nodes it runs. Do you have a solution?

Paths of vehicles are not printed in the teminal but stored in the files that are generated after certain amount of time. For example, after 1 minute of runtime program will generate a file called res-1-instance.txt which will contain best found paths for each vehicle in the format described on that last page of problem description document.


Issue with hyperlink in first wrap-up quiz

To be fixed on the jupyter-book: https://inria.github.io/scikit-learn-mooc/predictive_modeling_pipeline/wrap_up_quiz.html
The markdown syntax is wrong regarding an hyperlink.

As well here, as noted by laurence: https://inria.github.io/scikit-learn-mooc/overfit/overfit_wrap_up_quiz.html


Unable to use custom rpcs with chopsticks

Description
We are currently try to integrate chopsticks in our dev flow an need to implement these custom  rpcs. As we current use 0.9.36 version of the sdk , we compile the node and use the wasm overide flag as advised here.
Unfortunately , chopsticks crashes.
Steps to Reproduce

clone this repo.
build the wasm target , `cargo build --release --features "runtime-benchmarks"
run chopsticks with the following commands : node packages/chopsticks/chopsticks.cjs --config=configs/bittensor.yml --wasm-override=../subtensor/target/release/wbuild/node-subtensor-runtime/node_subtensor_runtime.compact.wasm
execute this script

const { ApiPromise, WsProvider } = require('@polkadot/api');
const { decodeAddress, encodeAddress } = require('@polkadot/util-crypto');
const {Address} = require('@polkadot/types/interfaces');

// const provider = new WsProvider('wss://dev.chain.opentensor.ai:443');

const provider = new WsProvider('ws://<IP_ADDRESS>:8000');
const customConfig = {
  provider,
  types: {
    Balance: 'u64',
    DelegateInfo: {
      delegate_ss58: 'AccountId',
      take: 'Compact<u16>',
      nominators: 'Vec<(AccountId, Compact<u64>)>',
      owner_ss58: 'AccountId',
      registrations: 'Vec<Compact<u16>>',
      validator_permits: 'Vec<Compact<u16>>',
      return_per_1000: 'Compact<u64>',
      total_daily_return: 'Compact<u64>',
    },
    SubnetStakeInfo: {
      hotkey: 'AccountId',
      netuid: 'u16',
      stake: 'Compact<u64>',
    },
  },
  rpc: {
    delegateInfo: {
      getDelegates: {
        description: 'Get delegates info',
        params: [],
        type: 'Vec<u8>',
      },
    },
    subnetInfo: {
      getAllStakeInfoForColdKey: {
        description: 'Get all stake info for a given coldkey',
        params: [
          {
            name: 'coldkeyAccountVec',
            type: 'Vec<u8>'
          },
          {
            name: 'at',
            type: 'Option<BlockHash>',
            isOptional: true
          }
        ],
        type: 'Vec<u8>',
      },
    getTotalSubnetStake: {
      description: 'Get total subnet stake',
      params: [
        {
          name: 'netuid',
          type: 'u16'
        },
        {
          name: 'at',
          type: 'Option<BlockHash>',
          isOptional: true
        }
      ],
      type: 'Vec<u8>',
    },
  },
}
};

async function main() {

    const serializedData = await api.rpc.delegateInfo.getDelegates();

    const delegateInfos = api.registry.createType('Vec<DelegateInfo>', serializedData);

    console.log(delegateInfos.toJSON());

}

main()
  .then(() => process.exit(0))
  .catch(error => {
    console.error(error);
    process.exit(1);
  });

bitsensor.yml
endpoint:
 - wss://entrypoint-finney.opentensor.ai
 - wss://archive.chain.opentensor.ai
  # - wss://dev.chain.opentensor.ai:443
mock-signature-host: true
block: ${env.BITTENSOR_BLOCK_NUMBER}
db: ./db.sqlite
runtime-log-level: 5

import-storage:
  Sudo:
    Key: 5GpzQgpiAKHMWNSH3RN4GLf96GVTDct9QxYEFAY7LWcVzTbx
  System:
    Account:
      -
        -
          - 5GpzQgpiAKHMWNSH3RN4GLf96GVTDct9QxYEFAY7LWcVzTbx
        - providers: 1
          data:
            free:<PHONE_NUMBER>00
        -
          - 5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY // Alice
        - providers: 1
          data:
            free:<PHONE_NUMBER>00

Actual Behaviour
[12:48:40.794] INFO: Bittensor RPC listening on port 8000
    app: "chopsticks"
panicked at src/task.rs:144:10:
called `Result::unwrap()` on an `Err` value: (VirtualMachine(FunctionNotFound), HostVmPrototype)

Stack:

Error
    at imports.wbg.__wbg_new_abda76e883ba8a5f (/Users/samueldare/code/samtvlabs/bittensor/chopsticks/executor/dist/cjs/chopsticks_executor.js:751:19)
    at wasm://wasm/00b1d246:wasm-function[1106]:0x1907d4
    at wasm://wasm/00b1d246:wasm-function[1335]:0x19913c
    at wasm://wasm/00b1d246:wasm-function[1221]:0x1960bf
    at wasm://wasm/00b1d246:wasm-function[115]:0xc4bf5
    at wasm://wasm/00b1d246:wasm-function[633]:0x16aeae
    at wasm://wasm/00b1d246:wasm-function[1479]:0x19a85e
    at __wbg_adapter_48 (/Users/samueldare/code/samtvlabs/bittensor/chopsticks/executor/dist/cjs/chopsticks_executor.js:419:10)
    at real (bittensor/chopsticks/executor/dist/cjs/chopsticks_executor.js:401:22)
    at node:internal/process/task_queues:140:7

node:internal/event_target:1100
  process.nextTick(() => { throw err; });
                           ^
Error [RuntimeError]: unreachable
    at wasm://wasm/00b1d246:wasm-function[1106]:0x1908ea
    at wasm://wasm/00b1d246:wasm-function[1335]:0x19913c
    at wasm://wasm/00b1d246:wasm-function[1221]:0x1960bf
    at wasm://wasm/00b1d246:wasm-function[115]:0xc4bf5
    at wasm://wasm/00b1d246:wasm-function[633]:0x16aeae
    at wasm://wasm/00b1d246:wasm-function[1479]:0x19a85e
    at __wbg_adapter_48 (/Users/samueldare/code/samtvlabs/bittensor/chopsticks/executor/dist/cjs/chopsticks_executor.js:419:10)
    at real (/bittensor/chopsticks/executor/dist/cjs/chopsticks_executor.js:401:22)
    at node:internal/process/task_queues:140:7
    at AsyncResource.runInAsyncScope (node:async_hooks:206:9)
Emitted 'error' event on Worker instance at:
    at [kOnErrorMessage] (node:internal/worker:326:10)
    at [kOnMessage] (node:internal/worker:337:37)
    at MessagePort.<anonymous> (node:internal/worker:232:57)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:826:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)

Node.js v20.11.1

Excepted Behaviour
Calls succeeds.

you can't use runtime with benchmarking feature. it will have benchmark host functions (unresolved method)

Also your custom rpcs are part of your client and not runtime. You can't use them with chopsticks. Chopsticks itself implements only the base rpcs. You can only use runtime apis from chopsticks.


Images missing in examples since migration

See https://code.google.com/p/gmaps-api-issues/issues/detail?id=9743

It's not just the examples, actually. The code itself attempts to load images from Google Code:
MarkerClusterer.prototype.MARKER_CLUSTER_IMAGE_PATH_ =
'http://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer/' +
'images/m';
on line 195 of https://github.com/googlemaps/v3-utility-library/blob/master/markerclusterer/src/markerclusterer.js

I've created a pull request to fix this issue: https://github.com/googlemaps/v3-utility-library/pull/345

You don't need to update MARKER_CLUSTER_IMAGE_PATH_, you can just set the imagePath option to the path of the local images.

@PeterTheOne - does that work for you? Seems there is no longer such an option so I used MARKER_CLUSTER_IMAGE_PATH_.

@richardpenman Yes and there still is:
var mc = new MarkerClusterer(map, makers, {imagePath: 'images/m'});

fixed in d2cf3a584f90829859629e210d76944287c4d741


[gha] better status reporting.

Motivation
Make sure lbt skips are presented as skipped jobs.
Have you read the [Contributing Guidelines on pull requests]
Yes
Test Plan
Canary
Related PRs
None.
If targeting a release branch, please fill the below out as well

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

/canary

:sunny: Canary successful


fix(pci.projects.storage): check if backup is installed before deletion

See : MSB-133
issue : when customer is trying to delete an instance snapshot, if the snapshot is installed the api call fails so the delete button should be disabled
fix: display a warning message and disable the delete button if the backup is installed on an instance

Update : add to do some rework on this PR to match QC requirements (displaying instance name in error message)

CDS Report telecom-task#3147.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report test-manager_2#3147.0 ■

Stage 1

e2e ■
lint ✔

CDS Report overthebox#3147.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report pci#3147.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report test-manager_2#3147.0 ■

Stage 1

e2e ■
lint ✔

CDS Report telecom-dashboard#3147.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report sms#3147.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report freefax#3147.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report layout-ovh#3147.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report vrack#3147.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report public-cloud#3147.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report test-manager_2#3147.0 ■

Stage 1

e2e ■
lint ✔

CDS Report installation#3162.0 ✘

Stage 1

Install ✘


[bug] Level 8.0.0 throws error "db.createValueStream is not a function"

System Information

Aedes: 0.46.3
NodeJS: 16.14.2
OS: Debian GNU/Linux 11 (bullseye)
Arch: x86_64

Describe the bug
After upgrading to  level to 8.0.0 aedes-persistence-level throws: TypeError: db.createValueStream is not a function
To Reproduce
import { Level } from "level";
import aedesPersistencelevel from "aedes-persistence-level";
const db = aedesPersistencelevel(new Level("./data"));

Expected behavior
No error :-)
Additional context
Level 8.0.0 UPGRADING.md mentions this as a breaking change for 8.0.0.:

Streams have moved
Node.js readable streams must now be created with a new standalone module called level-read-stream rather than database methods like db.createReadStream(). For browsers you might prefer level-web-stream which does not require bundling the buffer or readable-stream shims. Both level-read-stream and level-web-stream can be used in Node.js and browsers. The former is significantly faster (also compared to level@7, thanks to a new nextv() method on iterators). The latter is a step towards a standard library for JavaScript across Node.js, Deno and browsers.
To offer an alternative to db.createKeyStream() and db.createValueStream(), two new types of iterators have been added: db.keys() and db.values().

PR?

Happy to, but how do you want to move forward ?
E.g. Move to aedes-persistence-level version 8 that is only compatible with Level version 8, or some auto detection logic ?
Also do you want to modernize to iterators as well or do you want to stay on level-read-stream/level-web-stream ?
https://github.com/moscajs/aedes-persistence-level/blob/8600507ebb33e8088b51a95e49b5d1cd1d20b9b2/persistence.js#L29
Could still return a stream if required but based on iterators ;-)
Quick scan seems to show that  Aedes does not seem to use createValueStream therefore we could also switch all the internals from streams to iterators.
And if it will be a semver major, do you also want to move to classes like level did ?
So the question is: how far do you want to go in refurbishing this module ;-)
Kind regards,
Hans

Minimum Node.js version 14 ? (12 is EOL by the end of this month ;-))

Yep it's ok for me 👍🏼  Remember to update ci workflows

Remember to update ci workflows
Ok, will look into those as well :-)

Small update:
I got a working version that supports Level versions: 6.0.1, 7.0.1, 8.0.0
(6.0.1 being the version used in CI for the current version of aedes-persistence-level)
In the mean time I learned quite a lot including:

level.createReadStream in 6.0.1 and 7.0.1 does not create an iterable stream (its absent in 8.0.0)
level.iterator in 6.0.1 creates an iterator that is not standard
'utf8' encoding in 6.0.1 and 7.0.1 did not touch buffers, in 8.0.0 it does so now all db.get and db.put calls have correct encoding

Currently I'm working to move the streams to the edge of the interface using generators and iterables.
This should also reduce the number of dependencies.
Cheers,
Hans

Open a PR so I can follow the changes

Fixed by #28


Document:  The necessity of videojs.ima.scss in ES6 Imports ?

Request for help
Please add some explanations about videojs.ima.scss in README, as I only saw <link rel="stylesheet" href="path/to/videojs.ima.css" /> is mentioned in Alternative Setup, while it's necessary for us to import the css/scss file in certain situations...
Motivation
Follow by the instructions of ES6 imports, I've found a bug that ima-ad-container will be rendered right below the player.

How to reproduce the bug

Using ES6 imports way to get started
Specify player option aspectRatio as "16:9"

How to fix it
Add import 'videojs-ima/dist/videojs.ima.scss';, then ads container will cover the original video content, and the IMA player controls will be rendered (see the red box in screenshot).

Also see my CodeSandbox:  Please comment / uncomment the import 'videojs-ima/dist/videojs.ima.scss'; to see the difference.
Package versions

video.js: 7.6.6
videojs-contrib-ads: 6.6.5
videojs-ima: 1.7.4

Close the issue wrt. #884


PR to update github actions and yaml files

Context

Describe the changes made and why they were made.
Provide links to any issues or designs for this change.

Were any new external packages added?

List external packages added and why they were added

Merge now to test the actions


Preview activity bar icon reordering during drag operation (and let me be sloppy)

Testing #16326
To reorder icons in the activity bar, I have to drag and drop the icon directly on the position I would like it to occupy.  I can't drop it between two icons and have it position between them.
This is generally OK, but when I want to put an icon at the bottom of the list I really just want to be sloppy and drag it to the bottom/empty area of the activity bar. I don't want to have to be accurate and drop it in the last position (the horror of having to be accurate!!)

It would be ideal if when i dragged the icon up or down you could see the other icons move around and almost preview what the activity bar will look like when it is dropped.

Yup, sean filed a similar request.

Actually it was Greg, closing as duplicate: https://github.com/Microsoft/vscode/issues/16541


Support skipping resources diff

Closes #257

@r3nic1e maybe consider also ignorinb helm v2 annotations?
https://helm.sh/docs/topics/chart_tests/
Note that until Helm v3, the job definition needed to contain one of these helm test hook annotations: helm.sh/hook: test-success or helm.sh/hook: test-failure. helm.sh/hook: test-success is still accepted as a backwards-compatible alternative to helm.sh/hook: test.

@derbeneviv I don't think so - we have helm v3 embedded. So the second version of helm chart schema is implied

@r3nic1e as i see in docs - HookEvent.Hooktest matches only test string

I can confirm that all tests are now hidden for both helm3 and helm2 variants


cache: Add .Set and .Add methods to cache clients

What this PR does:
This change adds a synchronous version of .Set to Memcached and Redis clients as well as the various Cache wrapper implementations. This allows callers to set a key and be sure it exists in the cache. This change also adds an .Add method which conditionally adds an item to the cache only if it does not already exist.
Which issue(s) this PR fixes:
This change is a prerequisite for grafana/mimir#9386
Checklist

[x] Tests updated
[x] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

nice one, I'm not sure about the 30d TTL, otherwise LGTM

When you give Memcached a TTL longer than 30d, it treats the number of seconds as a Unix timestamp. E.g. if you give it a 31d TTL your item will expire on February 1st 1970 -- immediately.


Issue3004 performance

Fixes #3004 Performance fix

Pull request #3873 supercedes this one by rebasing over the reworked dev branch.


fix #3 error when exporting non-string literals

Fixes #3
I'm not sure if it's intentional that the transform applies to all exported values, but I could see a scenario where someone is relying on that behavior. For example, if they are exporting file paths as strings. So, I opted to keep that functionality and added a test for it.
Totally open to suggestions if there's a better way to handle this.

@jRiest Thanks for the PR, with tests! I'd like to move the fix from the transformer into the import-declaration-transform.
If you update https://github.com/jurassix/refactoring-codemods/blob/master/src/transformers/import-declaration-transform.js#L30 these lines to the following we have a cleaner filtering. Only named exports with from keyword will be added to exportDeclarations.
OLD
  const exportDeclarations = root
    .find(j.ExportNamedDeclaration)
    .find(j.Literal);

NEW
  const exportDeclarations = root
    .find(j.ExportNamedDeclaration)
    .filter((path) => path.value.source !== null)
    .find(j.Literal);

Sounds good. I made that change in all of the transforms and updated the test cases.

@jRiest great work! Thanks for reporting, fixing, and testing! I'll release this now and also release the upstream dep https://github.com/jurassix/atom-javascript-refactor.

Published to npm as<EMAIL_ADDRESS>

oops borked that release 🎱
Published to npm as<EMAIL_ADDRESS>


TLS Connections

Will there be support for TLS Connections in the future?

Sure it will.
I've been building a proper dev environment for me (it was so outdated) and definitely is something i will start looking to implement ASAP.

Wonderful


Nil-value of ReplaceAttr leads to crash

Thanks for a very nice handler and a nice blog post describing it.
I just tried it out and ran into a crash that took me some time to debug.
I followed your example:
prettyHandler = prettylog.NewHandler(&slog.HandlerOptions{
    Level:       slog.LevelInfo,
    AddSource:   false,
    ReplaceAttr: nil,
})
logger := slog.New(prettyHandler)

and the code crashed on line 88 in prettylog.go
https://github.com/dusted-go/logging/blob/d9463cd16bc29441d9ec08d75fc49c5508cdb6df/prettylog/prettylog.go#L88
What I needed to do was to set ReplaceAttr to a trivial function that propagates the levelAttr, but I think it would be better that one has a check in the code whether h.r == nil and then skip the mapping, so that one can leave the ReplaceAttr function empty.

@tobbee - do you have that trivial function that propagates the levelAttr

replacer := func(groups []string, a slog.Attr) slog.Attr {
	if a.Key == slog.SourceKey {
		source := a.Value.Any().(*slog.Source)
		source.File = filepath.Base(source.File)
	}
	return a
}

var prettyHandler = prettylog.NewHandler(&slog.HandlerOptions{
Level:       slog.LevelInfo,
AddSource:   true,
ReplaceAttr: replacer,
})
logger := slog.New(prettyHandler)
logger.Info(
"incoming request",
"method", "GET",
"time_taken_ms", 158,
"path", "/hello/world?q=search",
"status", 200,
"user_agent", "Googlebot/2.1 (+http://www.google.com/bot.html)",
)

This is what I used f := func(groups []string, a slog.Attr) slog.Attr { return a }
https://github.com/Dash-Industry-Forum/livesim2/blob/53093cba4d3032d9b6072f7034fd6361cfcd0f1c/pkg/logging/init.go#L29C1-L29C65

oh amazing, thanks for raising the issue. I'll try to fix this later today!

Thanks again, this should be fixed now!


Yet another cdr-atom weirdness

The following
(= (f $_ $x) $x)
!(cdr-atom (A $x $y $z))

outputs
[$z]

instead of
[($x $y $z)]

Adding an extra variable, as in
(= (f $_ $x) $x)
!(cdr-atom (A $x $y $z $w))

outputs
[$z, $w]

It should be noted however that
(= (f $_ $x) $x)
!(cdr-atom (A $x $y))

outputs the expected result
[($x $y)]

Also, in the absence of (= (f $_ $x) $x), it all works as expected.

The problem is actually harder to reproduce.  Let me close that for now.

It is indeed a duplicate of #242.  I am closing and we can move the discussion there.

Let me evaluate if I can work around it, since I now understand it's origin, in order to evaluate if it is still a blocker.


KAFKA-8325: Remove batch from in-flight requests when handling MESSAG…

…E_TOO_LARGE error
This patch fixes a bug in the handling of MESSAGE_TOO_LARGE errors. The large batch is split, the smaller batches are re-added to the accumulator, and the batch is deallocated, but it was not removed from the list of in-flight batches. When the batch was eventually expired from the in-flight batches, the producer would try to deallocate it a second time, causing an error. This patch changes the behavior to correctly remove the batch from the list of in-flight requests.
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

retest this please


Add helloworld tests with grpc

This PR add an integration test in order to test a simple grpc helloworld with traefik.
Grpc use http2 protocol and as we use an http reverse proxy, and that golang supports only http2 on https, we can't use directly the code from the helloworld of grpc, we need to start a server with tls certificate.

👍
Last question: What's the number suffix in simple.toml155394643 for?

@timoreimann
The number suffix is because this is a temp file I have wrongly added :wink:

@dtomcej  oups, I really need to update my global gitignore

Sorry for the delay in review!
LGTM!


Compiled release?

I can't seem to be able to compile this  (I'm a complete noob when it comes to this) but I'm looking for a compiled Windows version just to use. If you can upload it here it'd be greatly appreciated.

You need MSYS2  to compile and run Juci.
More details here: Windows with MSYS2

I'm getting multiple errors right now but is there a pre built executable that you can give me?

Hi @chuckysprojects, thank you for your interest in this project!
Unfortunately, prebuilt binaries aren't available on any supported platform yet...
If you have specific build issues we would gladly help out if you post your terminal output.
The build is currently succeeding on Windows.
These are the commands that run to update, install dependencies and compile juCi++ on Windows:
pacman --noconfirm --sync --refresh --refresh --sysupgrade --sysupgrade
pacman --noconfirm --sync --refresh --refresh pacman
pacman --noconfirm --sync --refresh --refresh git
export arch=x86_64
pacman -S --noconfirm git mingw-w64-${arch}-cmake make mingw-w64-${arch}-toolchain mingw-w64-${arch}-clang mingw-w64-${arch}-gtkmm3 mingw-w64-${arch}-gtksourceviewmm3 mingw-w64-${arch}-boost mingw-w64-${arch}-aspell mingw-w64-${arch}-aspell-en mingw-w64-${arch}-libgit2
git clone https://github.com/cppit/jucipp
cd jucipp
git submodule update --init --recursive
mkdir -p build
cd build
cmake -G"MSYS Makefiles" -DCMAKE_INSTALL_PREFIX=/mingw64 .. #notice the two dots
make

After installing MSYS2 and juCi++ it is also important to recompile and reinstall gtksourceviewmm3. Please follow the install instructions, the steps are described there.
If someone is interested in creating an MSYS2 package for juCi++, feel free to do so, and others can then install this package using pacman in MSYS2. For this to be accepted by the MSYS2 project, it needs to be based on the latest juCi++ release, that is, not a -git package like the one that already exists in MSYS2 (jucipp-git). Others have created such packages, for instance for arch linux (in AUR) and FreeBSD.

@eidheim Well after complaining about not having numerous .dll files - this happened.
 I guess I'm still not compiling / building it correctly :/

Make sure you run juci from the MinGW-w64 shell after installation (assuming you are on 64-bit architecture).

Closing this with the assumption that the issuer made it work.


Feature/reenable tests on windows

Proposed changes
reenable fuzz tests on windows
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

depends on https://github.com/valory-xyz/open-aea/pull/563


Update soil param variable names

Small updates to config file readme. It seems that soil parameter values are specified as soil_params.<x> in the config file, however they are specified using only their qualifying name (e.g. b, quartz) if they are being calibrated. Can you verify this, @ajkhattak?
b -> soil_params.b
https://github.com/NOAA-OWP/SoilFreezeThaw/blob/14610e3f0c69cbfb62564b19b8f5762e7c6aef63/src/soil_freeze_thaw.cxx#L181
quartz -> soil_params.quartz
https://github.com/NOAA-OWP/SoilFreezeThaw/blob/14610e3f0c69cbfb62564b19b8f5762e7c6aef63/src/soil_freeze_thaw.cxx#L188
satpsi -> soil_params.satpsi
https://github.com/NOAA-OWP/SoilFreezeThaw/blob/14610e3f0c69cbfb62564b19b8f5762e7c6aef63/src/soil_freeze_thaw.cxx#L194
smcmax -> soil_params.smcmax
https://github.com/NOAA-OWP/SoilFreezeThaw/blob/14610e3f0c69cbfb62564b19b8f5762e7c6aef63/src/soil_freeze_thaw.cxx#L176

@ajkhattak, if it is the case that you use soil_params.<x> in the config file, but only for example b for calibration (so in a ngen realization config), what are your thoughts on deprecating the use of just b in the calibration case, and forcing the use of soil_params.b when calibrating just for consistency? I've come across soil_params.<x> in several modules you all have produced, so it seems like there would be less friction to deprecate usage of only b for example.

@aaraney This is a good point and this inconsistency is there in most of our soil models, including cfe, other than LGAR. If you want to go ahead a fix them please do so, or I can fix them

@ajkhattak, i'm happy to fix them. I am not a huge fan that this will be a breaking change, but i think given where the project is at that is still okay. We will just need to do our best to let anyone that we know of who is using these modules know about the changes.

Okay, I think I like the idea of providing support for both options b and soil_params.b in the config file, that will make it consistent with CFE too. should be pretty straightforward...


Lookup of ICAO hex to symbol

A certain regular local flight stopped broadcasting a callsign, but we could still ID it, and others, by its ICAO code rather than its callsign

No need for this I think, we still get the tail number for that flight as a callsign and can set symbol and operator for that by pretending its a prefix

Not currently working as intended, will need to do this after all


Create snowfakery-recipe.md

Issues Closed
Closes #36
Helps us move forward on #88

@acrosman is this what you were expecting? I think the easiest way to test this is probably just to commit it to main and make changes once we see whether it works... I can't figure out how to test it outside of main.


[SUPPORT] Help with Hudi Cli Savepoint and restore Hudi Table (Blocker)

Describe the problem you faced
We have been running Hudi Delta streamer on emr-5.31.0 (details below) for more than a year in production and the dataset has 45 TB of data.The data set was out of sync for almost entire month of Feb (Last commit was Feb 1 19:05 UTC).So to restore it back to present day we decided to write 15 days worth of data in 1 run.
But the job taking a long time (4 hrs) and I decided to kill the job and start a new EMR with more executors.After restarting the job I found that the job resumes from the Feb 1 19:05 UTC checkpoint but immediately stops all the executors.The job also has an commit.requested and inflight present in the .hoodie folder.I tried deleting both commit.requested and inflight files but I still get the same behavior.
Is it possible to use the Hudi Cli to restore the Hudi table back to the last successful commit and start from that checkpoint ?
This would be desirable as currently our job is blocked because of this issue
To Reproduce
Steps to reproduce the behavior:

Run the hudi deltasteamer on emr-5.31.0 on 1 Master and 4 core both m5.4xlarge with 12 executors with 5g memory
and spark.executor.cores as 4 and spark.task.cpus: 1. - I can provide more details if needed but this configuration has been
tested and has been running efficiently for a 1 year.The number of executors was very low
Read 178,536 files of size 1000.7 GB and write to hudi table (Files 571,478) 45.0 TB
Kill the job in 4 hours
Restart hudi deltastreamer with 28 executors same configuration as Step 1

Expected behavior
I expected the hudi deltastreamer will rollback previous inflight commit and start from Feb 1 checkpoint and write all 1000.7 GB files successfully
Environment Description
Hudi version : 0.6.0
Spark version : 2.4.6
Hive version : 2.3.7
Hadoop version : Amazon 2.10.0
Storage (HDFS/S3/GCS..) : S3
Running on Docker? (yes/no) : no
Additional context
I did see this issue [https://github.com/apache/hudi/issues/2072|https://github.com/apache/hudi/issues/2072] which refers to
using Hudi Cli to create a save-point and reset it back to that point.Is that possible
Stacktrace
I did not see any exception in log.

I have added documentation in this patch https://github.com/apache/hudi/pull/4715. should help you with adding a savepoint and restoring to one of the savepointed commit.

Actually we were able to get the job running again.When we started with a small volume of data and it was able to rollback the previous commit and catch up to current time.I am closing this issue.Thanks for sending the Savepoint documentation @nsivabalan


Child of #1277: Error loading relative file when logicalFilePath is set (Breaks migration from 3.x to 4.x)

Environment
Liquibase Version: 4.4.3 (and all 4.x, not in 3.x)
Liquibase Integration & Version: any
Liquibase Extension(s) & Version:  liquibase-core
Database Vendor & Version: H2 (and all others)
Operating System Type & Version: Windows 10 (and all others)
Description
In https://github.com/liquibase/liquibase/issues/1277 @darkcamper reported an error about loading sql scripts relative to a change log file whicht has a 'logicalFilePath' set.
This has been fixed in https://github.com/liquibase/liquibase/pull/1798 but it has been overlooked that the same error is present in

LoadDataChange,
CreateProcedureChange and
CreateViewChange

A PR to fix this can be found here: https://github.com/liquibase/liquibase/pull/2073
Steps To Reproduce
See https://github.com/liquibase/liquibase/pull/2073
Actual Behavior
See https://github.com/liquibase/liquibase/pull/2073
Expected/Desired Behavior
See https://github.com/liquibase/liquibase/pull/2073

Hi @smainz Thanks for creating this issue.  We will add this and the PR to the list of issues we are processing.


sasboot or viya_admin for sitedefault file

Please could you confirm if
the site default file creates admin as viya_admin as unable to logon with sasboot and the defined password in the vdm/file/sitedefault.yaml
pasword has not been updated in the file
stable
2021.1.6
Thx

Yes by default if you use the OpenLDAP included, it sets up viya_admin and it's password.  If you're not able to login you need to check your system something else is a miss. I'd check your pods and ensure they are running correctly especially the sas-logon pod.

i am able to logon with viya_admin..
So if im reading this correctly sasboot is not setup when using the sitedefault.yaml file instead its setup as viya_admin with OpenLDAP.
is this only with 2021.1.6, as i only changed the cadence in the main.yaml file from 2021.1.5 to 2021.1.6..
in the previous version  2021.1.5 sasboot was setup and i was able to logon with the password in the file sitedefault.yaml
Just need some clarification on deployments and sasboot using the deployment files.
currently only viya_admin works not sasboot
Thx

If you're using the IAC/Deployment repos this has been in place since day one. If you're looking for answers on sasboot this is not the place.

Ok.. Not sure how sasboot started working then in 2021.1.5.. if it was meant to be viya_admin that only worked using IAC files


Troubleshooting and instance directory updates

Is there a related issue for this PR?
Issue number: https://github.com/zowe/docs-site/issues/1127
Issue number: https://github.com/zowe/docs-site/issues/1128
Developer's Certificate of Origin (DCO)
Signed-off-by: Joe<EMAIL_ADDRESS>

@nannanli - these updates could go into master as well as docs-staging, as they are corrections and updates that apply to 1.10 (and in fact 1.9), but they aren't urgent so they could stay in docs-staging if it's work to get them live.  Not sure how much effort is involved pushing changes to the live site versus waiting for a release.

Thank you @nannanli


[W07H02] Changed the invalid depiction to valid in the FinishPost

Change the depiction from "green/yellow/red/blue" to "chequered" in finishpost.

Can you please check your indentation, that seems different from the original file which leads to "extreme" changes.


Need proper sync for buffer

The buffer is not thread safe. It might result in generating broken frame. Better use queue for buffer.
https://github.com/hzwer/arXiv2020-RIFE/blob/da21de1c813ab1c91de091026706429f3cd89424/inference_video_parallel.py#L53
https://github.com/hzwer/arXiv2020-RIFE/blob/da21de1c813ab1c91de091026706429f3cd89424/inference_video_parallel.py#L125-L128

+1
I keep getting glitched frames because the buffer is not in sync.

Done.


Add w40-droptroops.catpkg.yml

Hope I'm doing this properly! Happy to edit anything I missed.

There's a warning when you click Files changed tab (agreed, it should be more visible, we'll see what can be done).
You should add that topic ;)


fix Roaring64Bitmap toArray bug

@caoxiaoyuan7242  after complete the left comments ,please squash your commits into one commit.  So LGTM , +1 from me. Thanks for your work.


Notification emails for review requests not being sent to Admins

A user (org admin) reported that they had not been getting emails notifying them of DMP review requests.  They reported it for a plan on November 20th, and then repro'd it with a test on November 25.
I tested myself requesting feedback from UCOP, which should go to the DMP Email, and also did not get an email about a feedback requests, though I see the request in my list of notifications in UCOP.

Just based on timing, it could be related to our Rails upgrade but no idea for sure.

Turned out to be a missing SSM parameter (the name changed from do_not_reply_email to organization_do_not_reply_email). Updated on both prd and stg and restarted the system.


fix Agg stats bug in new stats

Proposed changes
the data structure of new stats is changed, bug Agg-estimation is not changed
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.64 seconds
load time: 448 seconds
storage size:<PHONE_NUMBER>3 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221114022128_clickbench_pr_45276.html


fix(ci): publish docs

This PR successfully updates probot.io with this build.
Take a look at my comment below to see what I believe was causing the previous docs-publish failure.

I can think of two reasons why the previous build had failed:

The REPO variable from the publish-docs script was not being updated with the value of GH_TOKEN because of a POSIX error.
The the GH_TOKEN did not have enough permissions, leading to authentication errors.

I would recommend merging this branch to see if docs will publish successfully because of switching to /bin/bash.
If that still does not work and we still get authentication errors, we may have to look at GH_TOKEN.

It worked: https://travis-ci.org/probot/probot/jobs/632063003?utm_medium=notification&utm_source=github_status Great work Maxim!

It failed again I'm afraid, could you look into it?
https://travis-ci.org/probot/probot/jobs/632974293

It looks like because changes were pushed to master, but no commits to create a release. As a result, the publish-docs script is trying to publish an already published version (tag).
The easiest solution would be to add the --force option when pushing.
But, I could add a check in the script to abort publishing docs if the latest tag in probot/probot already exists in probot/probot.github.io

Hmm there should always be commits that triggered the release, as it's automated that way using semantic-release. I wouldn't want to use --force when pushing to the master branch.
Which command is it that fails exactly? git push --tags origin master at the end? Should the "Update docs for v$VERSION" commit work?

The error looks like the problem is that the release already exists? So I guess the --tags is the problem?

I agree it's failing here: https://github.com/probot/probot/blob/4fdcde33a1548c045919390da8509fc66c3dbab1/script/publish-docs#L50
I'll just add a quick check to only continue with the script if the tag https://github.com/MaximDevoir/probot/blob/c6169a5c5df12f01d149c290286b313a97c91528/script/publish-docs#L7
doesn't already exist in probot/probot.github.io

We still need to be able to update the docs without there being a new release. Would that still happen with your change?

I did not think of that. How about: only add the --tags when $VERSION is not present in the probot/probot.github.io repo?

yeah that woudl work. Or do one push without --tags and a 2nd with --tags, then allow the 2nd push with --tags to fail.
On the other side, do we need to push tags to the probot.github.io repo at all?

Tagging doesn't seem to be essential to the CI process for probot.github.io.
Tagging was added in this commit, but tagging itself doesn't seem pertinent.

I've left you with two options #1104 and #1105.


It only works when ejecting player using F8

Hi, I'm testing this tutorial. But it doesn't work for me.
This is before I push play button.

This is after I push play button.

But it works after I push ejectting player button using F8

I think this happens because output of previous tick is used for input of next style transfer tick.
Anyone knows the reason?

I'm having the same problem. I wonder if you solved it?


Create a endpoint to receive search query and return similar timeseries

The basic API is: http://localhost:3000/stat/v1/timeseries-sim-search?q1=<>&q2=<>

Continue the work with  issue #11