clean up names in Excel file for 'unified parameters'

In order to exchange data between tabs, we will define physical groupings (bunch, laser pulse, etc.) and we will define parameter names and conventions for each. These choices are documented in the Excel file  .../radtrack/docs/physParams/UnifiedParameters.xlsx   which will change over time, and will be parsed to generate the necessary data holding classes.
The Excel file needs some initial cleanup and some variable name choices need to be finalized.
A longer term issue is how to handle secondary parameters and differing conventions for variable name/units/normalization, etc.

The first worksheet of the following spreadsheet shows my effort at a semi-complete beam description.
https://github.com/radiasoft/radtrack/blob/master/radtrack/util/unified_parameters.xlsx


WP 8.1 : clear notification and fire event when clicking on toast or tile notification message

I'm currently developping an mobile application based on Cordova (version 4.0.0) for Windows Phone 8.1. I'm using the cordova plugin "phonegap-plugin-push" (version 1.5.2).
I finished to implement the windows phone notifications on server and front side. It's works like a charm. I'm using WNS platform to send notifications windows from my server.
I encounter two problems about the interaction between fire event notification and mobile application.
For example, I send a tile and badge notification and I receive them on the start screen of windows phone . When I click on it, I'll go to inside in my mobile application. When I go back to my start screen, I always see the tile and badge notification.
How can I clear this tile and badge notification windows ? This is possible with your plugin ?
My second problem is about the click event on notification message. When I click on toast or tile notification, my app, running in background, opens and the notification callback is not triggered and I can't display a specific badge on start screen from my app.
If I'm not mistaken, the following method to fire this event is :
  push.on('notification', function(data) {
    console.log("notification event");
    console.log(JSON.stringify(data));
    //I would like display a specific badge
    push.finish(function () {
        console.log('finish successfully called');
    });
 });

This event method only works when I'm inside on my app (running in foreground).
Do you have an idea about how to fix it ?
Be careful, unlike the issue #526, my windows phone app is deploy as Windows Phone Universal and not as Windows Phone 8.

@charpin: Presently the notification event is only fired when the app is in the foreground. This issue is already created to integrate the support for background notifications for windows, but it is yet to be worked on.
To answer your first question, the notification which appears in the notification shade is triggered by the OS, and the display in the app is handled by the user. Clicking on the notification fires a launch event which can be handled by your application. You could look at this for more details.

I'm sorry not to have been able to get back to you sooner. Firstly, thank you for your useful answer.
Secondly, about the background notifications for Windows Phone, I have seen this issue after your answer but now, I know that you're working on it. I'm eager to get the next version of this plugin !
At least, about your answer to handle notifications, your link helped me a lot. However, I can handle a tile notification fired but not a toast notification, it's weird for now. But it's not your problem and it's not about this plugin, so you did well to close this issue.


The farm coordinates extracted from the workflow output (tif file) do not match those provided as actual input for the same farm.

Dear Farmvibes Team,
In "timelapse_visualization.ipynb" notebook the workflow executed successfully but the coordinates generated by the workflow output differ from those provided as input for the same farm.
For Eg.: Actual co-ordinates of farm for which I run the workfow are (-117.04856344591778 47.037513931531834, -117.04505728312543 47.03760951215952 ...) but when I extract the co-ordinates from tif file (which is generated as workflow output) I get (5210605.0 496315.0, 5210605.0 496325.0 ...) which is different from actual input coordinates of the same farm.
Attached to this issue, you will find the following files for your reference:

farm.wkt file containing polygonal co-ordinates of farm which is given as input to the workflow.
Screenshot of the coordinates extracted from output tif file.
Timelapse.ipynb notebook I used, to run the workflow and extract co-ordinates from tif file.

Attached_files.zip

Hi, @click2cloud-sagarB. Thank you for raising this question and providing the files.
The rasters downloaded with FarmVibes.AI workflows retain their original CRS. That is why you are seeing those range of coordinates.
From the screenshot that you shared, you were printing the lat/lon coordinates for each pixel position. If you want a map between both sets of coordinates, you can calculate the transform between both CRS's.
import rasterio
from rasterio.warp import calculate_default_transform

input_crs = "epsg:4326" # CRS of your input geometry

# x and y are coordinates in the raster (I'm using one example from your message)
x = 496315.0
y = 5210605.0

with rasterio.open(run.output["s2_raster"][0].raster_asset.url) as src:
    # Calculate the transform from the raster CRS to the input geometry CRS
    dst_transform, dst_width, dst_height = calculate_default_transform(src.crs, input_crs, src.width, src.height, *src.bounds)

    # Calculate the pixel position in the raster (with inverse transform)
    pxl_x, pxl_y = ~src.transform * (x, y)

    # Calculate coordinates in the input geometry CRS given pixel position
    lon, lat = dst_transform * (pxl_x, pxl_y)
    print(lon, lat)

Thanks, @rafaspadilha. The snippet you shared reolved the issue, also when I used the pyproj package to solve the above mentioned problem, it too worked perfectly.


DOM Node Leak for modal & nav push / pop

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[X] 3.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Nodes always seem to increase with modal open and dismiss even after garbage collection..
Expected behavior:
nodes count would fall when modal dismissed.
Steps to reproduce:
run ionic conference app
https://github.com/ionic-team/ionic-conference-app
skip the intro. repeatedly open and close the filter settings modal.
(https://monosnap.com/file/xg1mpk9aaHaCoMbSIUIt53WifB55p8) button at the top right.
Monitor using performance tab on chrome developer tools -- shows the nodes increasing every time modal is opened
https://monosnap.com/file/xIFbiboFMyAXdIyBNCBUWVNpGStI11
Related code:
Other information:
in the middle, i pressed the button for garbage collection - nodes only went  down a tiny bit.. seems to add about 250 nodes every time the modal opens.
i pressed model open and closed 10 times, then garbage collection, then open and close another 10 times. at the end there are close to 6000 nodes....
In other apps, also seems to happen when i use navctrl push and pop on other apps.  nodes do not appear to be released, even in --prod mode. on iOS compiled apps, for example, will cause the device to freeze after a few cycles of this, depending on the machine.
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
global packages:

    Cordova CLI : 7.0.1

local packages:

    @ionic/app-scripts : 2.1.3
    Cordova Platforms  : none
    Ionic Framework    : ionic-angular 3.6.0

System:

    Node       : v7.10.0
    OS         : macOS Sierra
    Xcode      : Xcode 8.3.3 Build version 8E3004b
    ios-deploy : 1.9.1
    ios-sim    : 6.0.0
    npm        : 5.3.0

Hello, thanks for using Ionic! Unfortunately, I am not seeing the same issue when i trace this.

 This is in the latest chrome with the conference app.

thanks for checking - looks like you launched the modal window 3 times.

Any further info on this?

Are you experiencing it too? maybe let the team know.
I removed "on iOS compiled apps, for example, will cause the device to freeze after a few cycles of this, depending on the machine." from my original description as that was due having a click event on an ion-item (a bug, but a different one)

Can you elaborate on the other bug?

#12737

Hello! Thank you for opening an issue with us! Would you be able to provide a sample application via GitHub that demonstrates the issue you are having?
That would greatly help however picks up this issue.
Thanks for using Ionic!

Hi @kensodemann
https://github.com/jbgomez21/modal-memory-leak
Regards

src/components/modal/modal-component.ts
ionViewPreLoad() {
    // ******** DOM WRITE ****************
    const componentRef = this._viewport.createComponent(componentFactory, this._viewport.length, this._viewport.parentInjector, []);
}

The componentRef in the code above should be saved somewhere and destroyed with modal component.
I have tried to implement something like this and component used in modal disappeared from heap snapshot.

Very nice find. Hopefully this can get sorted out quite quickly.
It would be great for other areas in the framework to be looked at for similar memory leaks.

It seems to be related with this
https://github.com/angular/angular/issues/22155

it also seems related to this: Browser Memory isn't released when destroying components #13725
I'm experiencing the same problem.

I don't know about known angular memory leak issues, but I just stumble upon this particular one due to handleOrientationChange handler not released.
The problem is the use of .bind(this) when binding to 'orientationchange' event. When using .bind(this) a new reference is returned each time which differs from the previous .bind(this) (see this little fiddle I have created https://jsfiddle.net/2tzj9o0L/8/).
So when calling removeEventListener in the destroy callback, the handler is not the same as the one passed to the addEventListener.
Using the registerListener utils of the Platform class or keeping the reference this._bindHandler = this.handleOrientationChange.bind(this) for example solved the issue and DOM Nodes are collected.
I didn't check if there are others .bind(this) issue like this one. Might be a good idea to make a little review.

Having the same issue with a long running Ionic-Application here.
Any chance to get a Bugfix version of Ionic 3 with this fix?
What would be the easiest way to get this changes into my project using Ionic 3.9.2?
Every hint is welcome :)

@meisterlampe
I just ran into this on ionic-angular 3.9.2. I just put a postinstall script in my package.json that replaces /node_modules/ionic-angular/navigation/view-controller.js with @jrmlt's patched file above.
Not the most elegant solution, but it'll work until (if) 3.9.x is patched.

Thanks for sharing. I guess I'll go this way too :)

Any update on this?

Just realized as per @jrmlt that no more new features will be merged in to v3. Does anyone know if this has been patched in v4? Before I attempt to migrate my app, wondering if anyone has tried this :)


[Android] Customizable dialog for shared mode

Implement the interface for customizing how the dialog would be
displayed when initializing Crosswalk Project runtime.
BUG=XWALK-5211

@wuhengzhi @xzhan96 @fujunwei @axinging Please help to review


Api for saving screenshots and animations

Hello!
It would be great if there was a way to log a pointcloud or mesh to rerun, specify a camera pose, and programmatically save a "screenshot" of that object from that specified pose. It would be very useful for evaluating and comparing different things, and for publishing purposes.
An extension of this would be to provide a list of camera poses, and use it to generate multiple screenshots that can be then stitched together to make a video or gif.
From looking at the docs, it seems this functionality is not there yet, is it?
Thank you in advance for the help!

Hey @chisarie! Thanks for the question / feature request. Screenshots from the command line actually just landed (#2293). The ability to construct the Rerun Viewer from a declarative spec is not there yet, but under way (see PR with RFC here: https://github.com/rerun-io/rerun/pull/2302). Once that lands with the ability to also set a 3D view's eye I believe most of what you want should be there

Sounds great! One small thing to note which is different than https://github.com/rerun-io/rerun/pull/2293 is that I'd like to have a "screenshot" of a viewport alone, without all the gui around it. Looking forward to it :)

Maybe screenshot is not the right word for this, what I mean is more like an offscreen renderer, similar to Open3d's and Pyrender's ones:
http://www.open3d.org/docs/latest/python_api/open3d.visualization.rendering.OffscreenRenderer.html,
https://pyrender.readthedocs.io/en/latest/examples/offscreen.html

Sure thing. We have the pieces in place to screenshot single views without UI surroundings as well. I'm not familiar enough with the offscreen render in Open3D to know how that works exactly but if you also need the rendering to run headless that would be a bit further off with Rerun.
Would you mind sharing a bit more background around how and why you would intend to use a feature like that?

Mainly to generate comparison pictures to use on publications paper and website. For example to compare the outputs of different methods. If I have to take all screenshots manually it would be very time consuming and also not precise (camera position should always be the same to compare properly). To use rerun for this, another important feature would also be to be able to set a white background, see https://github.com/rerun-io/rerun/issues/754

Thanks @chisarie, that makes a lot of sense!


README.md: Add WebHorizon

First off, awesome work with the project; have lots of small OpenVZ boxes that I was considering cancelling since I couldn't run NixOS on them but not anymore.
This change adds WebHorizon to the tested providers list, tested on current main (8dfcfe23bbc67ec82a16ac8870a9771a9bf12976). Works out of the box on a 256MB NAT OpenVZ7 machine from, no extra config needed just the one from README.md.

Thank you!


Problem in linking with retrieveCollisionGeometry

Should we not have an inline for retrieveCollisionGeometry ?
https://github.com/stack-of-tasks/pinocchio/blob/db8fe0add7d10ea31ff13aa677e30fcc3b569e42/src/parsers/urdf/geometry.hxx#L98

Solved by #728


\x1b[?1001r sequence resets cursor to the beginning

Reproducer: mouse.sh.gz
Output should look like this:
line a----------
line b----------
line c----------
line d 123
line e

Example Recording: https://asciinema.org/a/HlH7tRw4wAqGeFvbl7z6Mx2mN
When playing the .cast file in the terminal, it looks fine.
Unfortunately, this currently breaks all recordings created with radare2

This has been fixed in develop, will be released in v3.0.0-beta.3 very soon.

Thanks!


Feature request: Gotify notification support

I tried making a fork to add support for Gotify notifications but there is no comments on the code, that made dificult to code above the existing one, i tried making some changes. IDK if you`re interested on Gotify notification support.

The code is poorly structured at the moment. I am doing a refactor on the feat/web branch. The notifications service will be easily extensible in the future. Let us come back to this then. I'll try to add comments too but no promises!

Hehehe, Nice!!!! In the moment i`m using N8N as a middle software to get the webhooks and convert to gotify notifications.


build(deps): bump typescript from 4.2.2 to 4.3.5

[x] You have followed our contributing guidelines
[x] Double-check your branch is based on dev and targets dev
[ ] Pull request has tests (we are going for 100% coverage!)
[ ] Code is well-commented, linted and follows project conventions
[ ] Documentation is updated (if necessary)
[ ] Internal code generators and templates are updated (if necessary)
[ ] Description explains the issue/use-case resolved and auto-closes related issues

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
249

Relevant Lines:
249

💛  - Coveralls

This is ABSOLUTELY no go. You can't bump things to versions released only 5 hours ago. Dependency management is an extremely hard task. CRA doesn't support recent versions of typescript on top of it. You need to read every changelog and bump one by one checking if they break something. It takes hours when I do version bumps ;)
I can understand your motivation but slow down with PR, please. It's not always good to update and aggressively fix things. Maybe open an issue if you want to suggest something and we can talk before you implement it.
Read this maybe: https://github.com/react-boilerplate/react-boilerplate-cra-template/issues/131

@Can-Sahin thanks for your feedback.
I understand your position, it has a place to be. Maybe you can make a clear list of criteria for upgrading a package to a new version? I spent several hours updating packages, reading their changelog and running tests...
I also ask for additional information regarding the typescript version. When I install the official CRA with the typescript, the latest version 4.3.5 is installed, which is valid for the specified pattern "^4.1.2". Where can I find information about the invalidity of this version you are writing about?

ok then cool. Most people think it's easy to just bump the version. I should write a list of what to verify manually even though the tests are passing. There are some checks as well, tests cannot cover everything. It has to wait a bit because I am quite busy in august. I also did a version bump commit lately. It's not super important to keep up-to-date always.
I don't remember where it's written but I remember seeing 'using ts version xxx and cra supports yyy' when you 'yarn start'. And typescript is quite problematic with CRA. Had so many issues in the past. I decided to run keep at least 3 months for typescript and core libraries like redux, react, react-dom, etc.  I have been in react and the boilerplate world for 4 years and I believe it's best for the majority. Anybody can update after installation anyway.

I am opening it back again just as a reminder to me. But for the next couple weeks, I don't have time for this repo sorry.


Rethinking the Karma Test Adapter

When I initially implemented the Karma Test Adapter I made the assumption, that it would be possible to statically analyze test files to discover tests by parsing them.
Since then I have learned:
There is no (easy) way to discover tests without running them!
In this simple example it would be hard to determine test names just by parsing:
describe("Suite", function() {
    for (var i = 0; i < 10; i++) {
        it("sould not fail - " + i, function() {
        });
    }
});

A test adapter for the Visual Studio test explorer has three phases:

Discovery of test containers.
In our case this would be karma.conf.js or karma-vs-reporter.json.

Discovery of tests for each test container.
This is where the current version of the Karma Test Adapter parses the test files to discover tests. As I have learned, this is very fragile, and can easily fail.

Run the tests discovered
The current version of the Karma Test Adapter "tells" Karma to run the tests.

Based on this I am working on a rewrite of the Karma Test Adapter. The new adapter will:

Always run Karma in the background

If karma.conf.js or karma-vs-reporter.json change karma in the background will be restarted using the changed settings.

In karma-vs-reporter.json it will be possible to turn off the adapter.

When Visual Studio wants to discover tests the background Karma process will be asked to run them. Test files will no longer be parsed to discover tests.

When Visual Studio wants to run tests the background Karma process  will be asked to return the result of the latest test run.

The fact that test files will no longer be parsed to find tests leads to the following:

The file name and line number of each test will not be available from parsing of test files. My plan is to instrument the jasmine functions describe and it to include this information in the test results using a stack trace.

I have now made a prerelease of the next version of the karma test adapter.
There are some major changes:

The node package karma-vs-reporter is no longer used, and is deprecated.

The optional settings file is now called KarmaTestAdapter.json, not karma-vs-reporter.json.

Temporary files are no longer used to communicate between different parts of the adapter. This means that it no longer makes sense to have an OutputDirectory option in KarmaTestAdapter.json.

Karma is always run in "server" mode, and the port to use is generated automatically. This means that options ServerMode and ServerPort are no longer available in KarmaTestAdapter.json.

It is possible to disable the adapter using the Disabled option in KarmaTestAdapter.json.

The adapter no longer watches for changes in files (except for karma.conf.js and KarmaTestAdapter.json). This is handled by Karma. This means that option TestFiles is no longer available in KarmaTestAdapter.json.

Tests are run immediately when any file, that Karma watches, is changed.

Before I publish this version, I would really appreciate it if some of the users of the adapter could test
it. The vsix file can be found here: v1.0.0-alpha.1.

Based on your comments, would another adapter extension of this sort have to be written in order to support running Protractor-based (Jasmine) tests from Visual Studio?  I would imagine there would be a fair amount of code overlap...would it make more sense for something like that to be a fork of this project, or a separate project?
I'll test your alpha.

@jitterbox I must admit that I have not looked a Protractor before now. My initial feeling is that the Karma Test Adapter is currently quite closely coupled to Karma. So I would think that another adapter should be written for Protractor.
It might be possible to refactor the Karma Test Adapter so code overlap could be avoided. However, I think it would take a bit of work. :smile:
Thank you very much for testing the alpha (now: v1.0.0-alpha.3), it is greatly appreciated!

As described in karma-runner/karma#1213 Karma sometimes fails when files it watches are changed. Therefore, as of v1.0.0-alpha.4, the adapter will restart Karma if it fails.

I have now published version 1.0.0 of the adapter.
Please create new issues for any problems with the new adapter.


Add cross-platform VSYNC estimator based on Blur Busters open source

@ad8e - we just released this today:
https://github.com/blurbusters/RefreshRateCalculator
Although your algorithm is good, there are some things RefreshRateCalculator.js does in a more cross-platform way (using generic time-offsets between VSYNC's to avoid the need for platform specific raster polls such as D3DKMTGetScanLine).  Our algorithm could become the fallback default when the specific platform is not detected (e.g. Windows or Linux).
We released as Apache 2.0 so you may use it in your other projects that requires a vsync estimator.  If you create a C++ version of RefreshRateCalculator.js please give us a pull request to add additional platforms.

If it works, go ahead. I also tried using presentation time to get vsync
times, but it always produced an extra frame of latency - on my Windows 8
system, vsync on apparently means "wait a whole extra frame for no reason".
So rendering starts at the beginning of the frame, you submit the frame
after 0.2 frames, and then the system presents it 1.8 frames later.
Maybe it'll be more sensible on other systems, or on Windows 11.
OpenGL has severe issues with multithreaded rendering, so blocking
rendering by waiting for frame presentation would be crazy for non-indie
games. Vulkan is said to work properly with multi-threaded rendering.
You could also use GPU timer objects to try to get frame presentation
times, though I didn't see in my brief exploration of them how to sync them
with CPU times.
On Wed, Jul 12, 2023 at 6:21 PM Mark Rejhon @.***>
wrote:

We just released this today:
https://github.com/blurbusters/RefreshRateCalculator
Although your algorithm is good, there are some things
RefreshRateCalculator.js does in a more cross-platform way (using generic
time-offsets between VSYNC's to avoid the need for platform specific raster
polls such as D3DKMTGetScanLine). Our algorithm could become the fallback
default when the specific platform is not detected (e.g. Windows or Linux).
—
Reply to this email directly, view it on GitHub
https://github.com/ad8e/vsync_blurbusters/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEWTJKOIJIESEBTQFV7H6IDXP5ETFANCNFSM6AAAAAA2IHIO3A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

It works in VSYNC OFF, if you use a separate thread for the timestamps.
You can use VSYNC OFF and instead use this approach:

APIs for zero-graphics timestamps (e.g. independent/separate thread) include Windows D3DKMTWaitForVerticalBlankEvent()

Even that has timing jitter, and the dejitterer improves that even further, and ignores missed vsync's (e.g. from computer freezes).

Oh -- and something I discovered.  Some platforms let you create two graphics contexts; e.g. an offscreen VSYNC ON frame buffer (sometimes it's sync'd to display Hz) while your visible frame buffer is VSYNC OFF.  You feed the offscreen VSYNC ON to this module, which generates cross platform raster estimates for this VSYNC OFF.
This is not always reliable, but it's another hack/technique to have simultaneous VSYNC ON and VSYNC OFF.

In that case, the chain for D3DKMTWaitForVerticalBlankEvent() was already implemented. You can toggle it on by going to https://github.com/ad8e/vsync_blurbusters/blob/main/platform_vsync_windows.cpp and reading the comments at the top. The math side is in vsync.cpp, which outperforms the linear regression and filter methods. It does a clever thing with pivot points to handle the unique noise distribution of waiting.
I took a look at the filter in RefreshRateCalculator.js; an exponentially-weighted linear regression would do better. It's the same as Jongerius's old algorithm, or the one in validate(), just with farther back points decreased in weight. If you really want to use a filter, might as well use a delay line instead of 4 1-unit delays, or an IIR filter, although it won't matter much.

It's not for Windows version (yours is good) -- but for other platforms if additionals are implemented (e.g. Android, iOS, different Linux graphics frameworks, Mac, etc).  There's a listener available for MacOS.
The filtering most certainly can be improved, so commits are welcome.  The RefreshRateCalculator is identical to Jongerius' old algorithm, and Jongerius' code was easier to port to a standalone JavaScript module for TestUFO needs.   So this was the least-effort open source release.
Now that being said, it's likely your vsync.cpp algorithm is better -- just more work to port C++ to JavaScript, than JavaScript-to-JavaScript
I'll add an issue tracking, to consider implementing the vsync.cpp algorithm into JavaScript and benchmark the two algorithms together!  Would be fun (although I'm too busy right now to do that -- I just released a mostly unmodified module that's been closed-source for ages)

The vsync scheduler of Chromium browser works perfectly for me, although it doesn't work as expected on secondary monitor when using two-monitor two-GPU setup.
the RefreshRateCalculator reports 60.02Hz while Windows reports 60.02Hz.
A vsync scheduler can also be used to buffer HID input messages as coalesced pointer events / wheel events, not only to schedule render loop.
Below listed are some related references:

BeginFrame / VSync Design Diagram
https://github.com/chromium/chromium/blob/main/ui/gl/vsync_thread_win.cc
Life of a frame

**fuweichin ** commented Aug 16, 2024 •

Nice observations and links!
Coalesced pointer events that are accurately grouped are an excellent use case.
FYI -- for those reading -- VSYNC estimators like RefreshRateCalculator.js (and ad8e's project) doesn't have to rely on Chromiums' VSYNC generator -- any VSYNC generator can be used as a feed, and it will de-noise, de-jitter, and ignore (and smooth over) any dropped VSYNC events.   Estimators like ad8e's and mine, are designed to accept a noisy VSYNC generator and output precise dejittered VSYNC timestamps.


[v0.9] Investigate coordinator failure for faulty provider

Backport of https://github.com/api3dao/airnode/issues/1581

Hi @Siegrift, I've tested the issue.
Steps: Deploy Airnode with a faulty provider URL (a Beeceptor URL with a 1000s delay before a response)
Expected result: Coordinator keeps functioning but displays an error message
Actual result: Matches expected result
I tested this on snapshots of v0.9.2 pre-release packages but wiped the logs by accident. I can retest this if you want a screenshot.

No need. Thanks.


Created intake subsystem for simple testing

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #24

PR #26   👈
PR #23

PR #25

This stack of pull requests is managed by Graphite.


Bitbucket Snippets support

Add Bitbucket Snippets support.
Link here

Any progress on this?

Not at all.


linux-39 is getting temperature issue.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
linux-39 is getting temperature issue.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Room temperature in devicelab is over heating, AC is not working.  Opened ticket for facility to look into issue.
https://gutsv3.corp.google.com/#ticket/225326177

More machines over heating.

AC on the roof was broken, notified Building facility to check and fix AC on the roof.  AC is back online and temperature back normal.


Feature/PreAggMetrics.Master

Hi folks,
This is the Merge PR for Metrics Pre-Aggregation. We have worked on the architecture and APIs previously.
E.g.: https://github.com/Microsoft/ApplicationInsights-dotnet/issues/643
The amount of code so substantial that making it fit the folder structure and other conventions may take a couple of iterations. I want to start early and obtain early feedback. I'll be reaching out to people directly for specific feedback questions.

@SergeyKanzhelev ,  @Dmitry-Matveev ,  @zakimaksyutov
I just sent you an email about this, but Sergey asked to also put a comment here and mention you all:
I have refactored the code to follow the repo rules. It builds cleanly. Basically, everything is ready for review. There are additional details in the email.
Thank you!

Why you committed src/Metrics.Extensions/Materials/StdDev Test Tool.xlsx ?

Nother naming issue: test files should not use underscore in names like: Foo_Tests.cs

Also fix the build

Seems impossible to respond to a comment within the context of that comment if the comment is not tight to a code line. :( So doing it here..

[ @SergeyKanzhelev ] Why you committed src/Metrics.Extensions/Materials/StdDev Test Tool.xlsx ?

This is an essential tool when calculating the correct values for testing aggregators. Thanks for pointing that out. As I move the tests into the right directory, I will place this file next to them.

[ @SergeyKanzhelev ] Nother naming issue: test files should not use underscore in names like: Foo_Tests.cs

Can you please clarify what you mean> I looked and only found files with underscores under
src\Microsoft.ApplicationInsights\Extensibility\Implementation\External
which is not part of this PR.

[ @SergeyKanzhelev ] I reviewed the form of code, not semantics. I'm really missing PublicAPI changes update and documentation for public methods to make sense of this code.

I will add the PublicAPI changes update as the next step. As discussed offline, I wanted to get this moving while i was still working on it. In terms of docs - a part is already completed, but there will not be time to describe every single API this week. Especially, it seems that we should focus on docs after we have closed on all API shape discussions.

@macrogreg it is nearly impossible to review public API without comments and even a list of how API looks like. Especially in 120 files PR that GitHub keep "optimizing" by hiding files and making them non-searcheable.

For the renaming - few clicks on refactor/rename and than merge back to this PR from develop doesn't sounds like time-consuming tasks. But it may save more time for reviewers that you've spent on implementing it.

@SergeyKanzhelev  I have pushed a change that re-enables PublicApiAnalyzer and lists the APIs in the right files.

Hi @Dmitry-Matveev  & @SergeyKanzhelev ,
I have critically evaluated the new API surface.
A one of the features offered by the library is to allow customers to plug in their own aggregator into the system and have it magically take effect.
For example I plan to ship a separate optional nuget (the aforementioned Metrics.Extensions) package that uses this feature to provide Accumulation and Distinct Count aggregators.
However, if we hold off on releasing this feature in the first beta, we can significantly reduce the size of the public API surface.
We can manage the size of the public change by doing this. However, I would like to re-enable the respective APIs in a future beta.
If you are OK with this plan, I will make change the corresponding APIs from public to internal for this beta release.
Are you OK with this plan?

I have pushed a change that reduces the public surface significantly, as discussed in my previous comments. Please note that there is still a significant number of lines in the PublicAPI.Unshipped.txt files, but a lot of them are overloads of the same methods.
Heads-up: @SergeyKanzhelev   @Dmitry-Matveev

Thank you, @Dmitry-Matveev , for the review.

Please coordinate with Sergey on TrackMetric() API. There are still concerns about it being obsolete with this PR.

@SergeyKanzhelev : You have asked some questions to which I all replied. Here is a link to that conversation for your convenience:
https://github.com/Microsoft/ApplicationInsights-dotnet/pull/735/files/1f151e21907f4408a8eb783fc0c1a05553fff20e#diff-a4553125b36a87ff02a1256a752265fc
Do you have any follow-up questions?
Thanks!


Create ru-ru.yml

Thanks a bunch -- are you planning on doing the rest of the locales, or should I merge this as-is? :)

Thanks a bunch -- are you planning on doing the rest of the locales, or should I merge this as-is? :)

Since there is i think

Closing as stale


[Feature] - Reintroduce service-name config for OTLP Exporters

Is your feature request related to a problem? Please describe.
Prior to version 2.0, all exporters had a tag service-name with which a constant tag could be added to the data indicating the service the data is send from. This feature should also be available for the new exporters introduced in version 2.0

The service-name tag was removed from the exporter in v2.0.0 as it is not supported by OTEL.
With OTEL, we can have one service name per agent, not per exporter.
Please use the global inspectit.service-name property.
see also documentation: https://inspectit.github.io/inspectit-ocelot/docs/tracing/trace-exporters

A little bit more documentation, how to use this tag will be helpfull.
Solved on our site like this:
inspectit.service-name: '${inspectit.tags.extra.application:undefined_application}'


XGBRegressor does not work with HyperbandSearchCV

!-- Please include a self-contained copy-pastable example that generates the issue if possible.
Please be concise with code posted. See guidelines below on how to provide a good bug report:

Craft Minimal Bug Reports http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports
Minimal Complete Verifiable Examples https://stackoverflow.com/help/mcve

Bug reports that follow these guidelines are easier to diagnose, and so are often handled much more quickly.
-->
What happened:
Got an error from XGBoost: "XGBoostError: need to call fit or load_model beforehand"
What you expected to happen:
I want to use  dask_ml.xgboost.XGBRegressor with  dask_ml.model_selection.HyperbandSearchCV.
Minimal Complete Verifiable Example:
import dask
import dask.dataframe as dd
from distributed import Client
from dask_ml.model_selection import train_test_split
from dask_ml.xgboost import XGBRegressor
from dask_ml.model_selection import HyperbandSearchCV
from dask_ml import datasets

client = Client('<IP_ADDRESS>:8786')

X, y = datasets.make_classification(chunks=50)
param_space = {
    'n_estimators': range(100, 200, 50),
    'max_depth': range(3, 6, 2),
    'booster': ('gbtree', 'dart'),
}

model = XGBRegressor()
search = HyperbandSearchCV(model, param_space, random_state=0, patience=True, verbose=True, test_size=0.05)
search.fit(X, y)

Anything else we need to know?:
Here the full error message:
_opt/conda/lib/python3.8/site-packages/sklearn/model_selection/_search.py:285: UserWarning: The total space of parameters 8 is smaller than n_iter=81. Running 8 iterations. For exhaustive searches, use GridSearchCV.
warnings.warn(
/opt/conda/lib/python3.8/site-packages/sklearn/model_selection/_search.py:285: UserWarning: The total space of parameters 8 is smaller than n_iter=34. Running 8 iterations. For exhaustive searches, use GridSearchCV.
warnings.warn(
/opt/conda/lib/python3.8/site-packages/sklearn/model_selection/_search.py:285: UserWarning: The total space of parameters 8 is smaller than n_iter=15. Running 8 iterations. For exhaustive searches, use GridSearchCV.
warnings.warn(

XGBoostError                              Traceback (most recent call last)
 in
11 search = HyperbandSearchCV(model, param_space, random_state=0, patience=True, verbose=True, test_size=0.05)
12
---> 13 search.fit(X, y)
/opt/conda/lib/python3.8/site-packages/dask_ml/model_selection/_incremental.py in fit(self, X, y, **fit_params)
715         client = default_client()
716         if not client.asynchronous:
--> 717             return client.sync(self._fit, X, y, **fit_params)
718         return self._fit(X, y, **fit_params)
719
/opt/conda/lib/python3.8/site-packages/distributed/client.py in sync(self, func, asynchronous, callback_timeout, *args, **kwargs)
849             return future
850         else:
--> 851             return sync(
852                 self.loop, func, *args, callback_timeout=callback_timeout, **kwargs
853             )
/opt/conda/lib/python3.8/site-packages/distributed/utils.py in sync(loop, func, callback_timeout, *args, **kwargs)
352     if error[0]:
353         typ, exc, tb = error[0]
--> 354         raise exc.with_traceback(tb)
355     else:
356         return result[0]
/opt/conda/lib/python3.8/site-packages/distributed/utils.py in f()
335             if callback_timeout is not None:
336                 future = asyncio.wait_for(future, callback_timeout)
--> 337             result[0] = yield future
338         except Exception as exc:
339             error[0] = sys.exc_info()
/opt/conda/lib/python3.8/site-packages/tornado/gen.py in run(self)
760
761                     try:
--> 762                         value = future.result()
763                     except Exception:
764                         exc_info = sys.exc_info()
/opt/conda/lib/python3.8/site-packages/dask_ml/model_selection/_hyperband.py in _fit(self, X, y, **fit_params)
399         _brackets_ids = list(reversed(sorted(SHAs)))
400
--> 401         _SHAs = await asyncio.gather(
402             *[SHAs[b]._fit(X, y, **fit_params) for b in _brackets_ids]
403         )
/opt/conda/lib/python3.8/site-packages/dask_ml/model_selection/_incremental.py in _fit(self, X, y, **fit_params)
661
662         with context:
--> 663             results = await fit(
664                 self.estimator,
665                 self._get_params(),
/opt/conda/lib/python3.8/site-packages/dask_ml/model_selection/_incremental.py in fit(model, params, X_train, y_train, X_test, y_test, additional_calls, fit_params, scorer, random_state, verbose, prefix)
475         A history of all models scores over time
476     """
--> 477     return await _fit(
478         model,
479         params,
/opt/conda/lib/python3.8/site-packages/dask_ml/model_selection/_incremental.py in _fit(model, params, X_train, y_train, X_test, y_test, additional_calls, fit_params, scorer, random_state, verbose, prefix)
169     logger.info("[CV%s] creating %d models", prefix, len(params))
170     for ident, param in enumerate(params):
--> 171         model = client.submit(_create_model, original_model, ident, **param)
172         info[ident] = []
173         models[ident] = model
/opt/conda/lib/python3.8/site-packages/distributed/client.py in submit(self, func, key, workers, resources, retries, priority, fifo_timeout, allow_other_workers, actor, actors, pure, *args, **kwargs)
1571         if key is None:
1572             if pure:
-> 1573                 key = funcname(func) + "-" + tokenize(func, kwargs, *args)
1574             else:
1575                 key = funcname(func) + "-" + str(uuid.uuid4())
/opt/conda/lib/python3.8/site-packages/dask/base.py in tokenize(*args, **kwargs)
793     if kwargs:
794         args = args + (kwargs,)
--> 795     return md5(str(tuple(map(normalize_token, args))).encode()).hexdigest()
796
797
/opt/conda/lib/python3.8/site-packages/dask/utils.py in call(self, arg, *args, **kwargs)
510         """
511         meth = self.dispatch(type(arg))
--> 512         return meth(arg, *args, **kwargs)
513
514     @property
/opt/conda/lib/python3.8/site-packages/dask_ml/model_selection/_normalize.py in normalize_estimator(est)
36                 continue
37             try:
---> 38                 val = getattr(est, attr)
39             except (sklearn.exceptions.NotFittedError, AttributeError):
40                 continue
/opt/conda/lib/python3.8/site-packages/xgboost/sklearn.py in feature_importances_(self)
540             raise AttributeError('Feature importance is not defined for Booster type {}'
541                                  .format(self.booster))
--> 542         b = self.get_booster()
543         score = b.get_score(importance_type=self.importance_type)
544         all_features = [score.get(f, 0.) for f in b.feature_names]
/opt/conda/lib/python3.8/site-packages/xgboost/sklearn.py in get_booster(self)
191         """
192         if self._Booster is None:
--> 193             raise XGBoostError('need to call fit or load_model beforehand')
194         return self._Booster
195
XGBoostError: need to call fit or load_model beforehand_
Environment:

Dask version: daskdev/dask:2021.5.0 Docker image
Python version: 3.8
Operating System: Linux (Ubuntu)
Install method (conda, pip, source): Kubernetes Helm Chart. I'm running the script from the Jupyter pod in the K8 cluster.

Thanks for the minimal example; I can reproduce.
I'm not sure Dask-ML's XGBRegressor and XGBoost's XGBRegressor should work with HyperbandSearchCV; they don't have the partial_fit function, a requirement for using incremental hyperparameter optimization.
It might be possible to jerry-rig XGBoost into supporting partial_fit; good references are https://github.com/dmlc/xgboost/issues/3055 and this SO question.

Thanks,
I think that Dask and XGBoost make a great couple. At the moment it seems to be that more suited for situations where data fits in memory. I'm starting to use HyperbandSearchCV and it's very useful (fast and performant), I think that getting this integration would draw more people to adopt Dask for tabular data problems that where the dataset is bigger than the system memory.
Should I close the issue based on the fact that the functionality I was expecting to use actually is not implemented?

I don't think so; I've filed #840 to make the error more clear.


Bookmark view not syncing sort order

If a chart is bookmarked, and then sorted differently in the main view, when user goes to the bookmark view, the sorting order will be out-of-sync.
Observed in Voyager-II user study

Oh crap, the root cause is https://github.com/uwdata/compassql/issues/172

This should not be a bug in the new rebuild.


update_dcos-kafka_kafka-mesos.jar_to_latest

Hey,
I've just updated dcos-kafka to 0.2.0 and kafka-mesos.jar to <IP_ADDRESS>.
Please merge.

The command-line fails on uninstall... details below:
dcos package uninstall kafka
Error while fetching [http://ken-69059-elasticl-ce2322x3nt4a-1645660120.us-west-2.elb.amazonaws.com/mesos/master/shutdown]: HTTP 404: Not Found

@dmitrypekar sorry for the delay... there looks to be a few things to resolve.

while you are at it... either rebase or remove the index.json.gz file

@kensipe
I've rebased PR and fixed following items:

removed app.id, used framework-name instead;
added app.instances config param;
fixed tags;
retested using local mesos cluster and dcos cli;

Please merge.

awesome!  thx... LGTM merging!


[HOLD #21932] Dev: Web - Console error Error parsing URLs: TypeError: Failed to construct 'URL': Invalid URL in public rooms

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:

Open the website
Click the + icon from LHN
Click Save the world
Click I know a teacher
Create a teacher unit
See that there is a console error

Expected Result:
Should not show any console error
Actual Result:
Shows console error - Url.js:46 Error parsing URLs: TypeError: Failed to construct 'URL': Invalid URL
Workaround:
Unknown
Platforms:

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

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

Version Number: Dev <IP_ADDRESS>
Reproducible in staging?: no
Reproducible in production?: no
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/93399543/dd9ee496-4025-4587-a282-919b8bd04eb2
Expensify/Expensify Issue URL:
Issue reported by: ~@narzullome~ @Natnael-Guchima reported earlier
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693374389112709
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~010fdcd111103dab09
Upwork Job ID:<PHONE_NUMBER>193559552
Last Price Increase: 2023-09-13

Proposal
Please state again the problem we are trying to solve in this issue.
Web - Console error on #teachers-unite page
What is the cause of this issue?
If we join #teachers-unite page, there is a Concierge wispher message as below.

The hyperlink in here is /settings/profile/display-name, and this is an invalid url.
So when rendering hyperlink, the following code catch an error, and then display an error on console.
https://github.com/Expensify/App/blob/6b1a6679042c4fa9bb628360e028f93a5f27b2f2/src/libs/Url.js#L19-L28
https://github.com/Expensify/App/blob/6b1a6679042c4fa9bb628360e028f93a5f27b2f2/src/libs/Url.js#L36-L48
What changes do you think we should make to solve the problem?
We can remove console.error in this line and this line.
What alternative solutions have you investigated? (Optional)
None.

Will take a look and see if I can reproduce this on dev tomorrow

Not super high priority since this is only on dev and the FAB -> Save the World option has been temporarily removed until we're ready to launch.
Tried to reproduce this on dev today but I think I need some additional setup to be able to call the ReferTeachersUniteVolunteer API command successfully.

OK, so do you think we can close this for the moment and revisit once we're ready for the STW launch @MariaHCD?

Chatting with @marcochavezf and this might be reproducible with any public room (assuming the error is produced by the link contained in the lurking whisper message). Going to test!

Okay, reproduced the console error when I created a public room in dev:

let's fix it!

Hey Guys, I have reported an issue with similar root cause earlier here. I reported this issue on Aug 23, and this issue was reported on August 30.
Cc: @bfitzexpensify

Thanks, @bernhardoj! Agreed that this will likely be fixed by https://github.com/Expensify/App/issues/21932
Going to put this on hold until we have the internal fix.

Hey Guys, I have reported an issue with similar root cause earlier here. I reported the similar issue on Aug 23, and this issue was reported on August 30.

I was assigned to the other issue, @Natnael-Guchima is correct, I've updated the OP to reflect

vs

Closing other issue since this one has more progress on it.

Not overdue, still on hold for https://github.com/Expensify/App/issues/21932

We're still on hold

Still held

still no progress

https://github.com/Expensify/App/issues/21932 is now resolved. @MariaHCD this was a dev error, can you still reproduce it?

No longer reproducible on dev when creating a public room:
https://github.com/Expensify/App/assets/12268372/ba331e39-fac9-4137-af4a-eaab9f6df523
@Natnael-Guchima can you retest and check if this is still an issue?

Bump @Natnael-Guchima, if you can also confirm this is no longer reproducible. Then I believe we can proceed with the payment for reporting.

It is fixed. Sorry for my late reply @MariaHCD

A link to video
https://drive.google.com/file/d/1ZKtCQMMf5C2GDvwfxk5VdI4qXLYmQmla/view?usp=sharing

Great! I believe we can now move forward with the payment for reporting, @bfitzexpensify

Thanks for confirming @Natnael-Guchima. Offer has been sent for reporting.

Accepted the offer. Thanks, @bfitzexpensify.

Great. All paid out - let's close this out.

Reopening per comment https://expensify.slack.com/archives/C049HHMV9SM/p1699551645734819

Ah, okay, there was a BE fix for this as part of this issue. I believe whisper messages that were sent prior to the BE fix will still have invalid URLs. So looks like this console error will show up for those older messages. It shouldn't happen for newer whisper messages sent for public rooms or when referring a teacher. Closing the issue for now, fixing those older messages wouldn't be worth the effort imo.

@allroundexperts noticed that this is reproducible if any chat message has an invalid URL: https://expensify.slack.com/archives/C049HHMV9SM/p1699915690734349?thread_ts=1699551645.734819&cid=C049HHMV9SM
Updated the title and OP to reflect this and reopening this issue so we can fix it.

@MariaHCD Is this issue opened for external? If so can we make the issue daily?
Not sure on the path forward from my end

@abdulrahuman5196 yes, this open for external proposals. I think @allroundexperts might already have an idea in mind based off our slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1699915706610939?thread_ts=1699551645.734819&cid=C049HHMV9SM

Got it let me check the conversation

I am not seeing this issue. Am I missing something?
https://github.com/Expensify/App/assets/46707890/61894715-81d8-452b-8ac5-2a3017a74fe6

@kbecciv / @bfitzexpensify Kindly check on the above question? I am not seeing this issue.

@abdulrahuman5196 I'm able to see the issue once the report is reopened:
https://github.com/Expensify/App/assets/12268372/390be0b1-2900-4555-bc8d-274244d67a7f
Let me know if you're still not able to see the issue.

@MariaHCD I am still getting this same response - https://github.com/Expensify/App/issues/26614#issuecomment-1819335038
When I edit the link, i don't get back a url when saving the edit.
But more-ever, even if the said comes true, should we even consider this an issue? Seems to be a super edge case to have a specific url format to repro the issue?

That's fair. I'm actually not able to reproduce the issue anymore.
https://github.com/Expensify/App/assets/12268372/d65d1ad5-e7a4-4691-a6cb-a912e1d79c4b
I do agree that it's an edge case so I think we can close for now.


Fix typo from drc to src

What kind of changes does this PR include?

Minor content fixes (broken links, typos, etc.)

Description
Fixes the typo in section https://docs.astro.build/de/guides/images/#remove-astrojsimage for langauges:

English
Spanish
Chinese Simplified
Japanese

I checked all languages and these are my findings:

Language
Code
Status

English
en
original typo

Deutsch
de
no translation, inherited from EN

Portuguese
pt-br
fixed by the pt-br contributor

Spanish
es
translated but inherited the typo

Chinese Simplified
zh-cn
translated but inherited the typo

Taiwanese Mandarin
zh-tw
no translation, inherited from EN

French
fr
no translation, inherited from EN

Hindi
hi
no translation, inherited from EN

Arabic
ar
no translation, inherited from EN

Japanese
jp
translated but inherited the typo

Korean
ko
no translation, inherited from EN

Polish
pl
no translation, inherited from EN

Russian
ru
no translation, inherited from EN

Italian
it
no translation, inherited from EN

Related Issue / Implementation PR
Implemented in this PR https://github.com/withastro/docs/pull/4724. No issues opened.

Thanks for catching this! Let's get this merged :tada:


Added a new link under Photography

Added a new link under Photography
Line 72. Shutterstock and its url link

Shutterstock is already under the paid resources section.


build: ensure compatible numpy ABI

Hi zfp team,
I've been encountering some compatibility issues with older versions of numpy.
import zfpy
"zfpy.pyx", line 1, in init zfpy
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

This can happen when a binary is compiled against a newer numpy which may have a different ABI. Numpy guarantees forwards but not backwards ABI compatibility. Compiling against the oldest supported numpy will fix this issue.
Thanks so much for all your work.
Will

Oops should have targeted the master branch. I'll close and remake the PR.

Thanks for your PR.  Please do target develop for your PRs--see CONTRIBUTING.md.
One of us will look this over in the coming days.

My bad, thanks for taking a look!
On Sun, Sep 25, 2022 at 7:12 PM Peter Lindstrom @.***>
wrote:

Thanks for your PR. Please do target develop for your PRs--see
CONTRIBUTING.md https://github.com/LLNL/zfp/blob/develop/CONTRIBUTING.md
.
One of us will look this over in the coming days.
—
Reply to this email directly, view it on GitHub
https://github.com/LLNL/zfp/pull/182#issuecomment-1257301312, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AATGQSLQPKA7TPPCYGGHNJDWADL7RANCNFSM6AAAAAAQVGLDLM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


feat: Run tests against dockerized app

Issue number
Relevant issue number

Resolves #534

Please check the following

[ ] Do the tests still pass? (see Run the Tests)
[ ] Is the code formatted properly? (see Linting (Formatting))
For New Features:

[ ] Have tests been added to cover any new features or fixes?
[ ] Has the documentation been updated accordingly?

Please describe additional details for testing this change

Closing this as it isn't a priority atm


Custom policies

Description of changes

This is a new feature to provide high-level method for adding custom policies to functions and API containers. Customers can add custom policies by editing the file custom-iam-policy-documents.json. The format of resources and action customers entered, will be validated first then merge to corresponding CFN template.
Issue #, if available

Description of how you validated changes
Checklist

[x] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #7965 (f425323) into master (3f8bb3f) will decrease coverage by 0.09%.
The diff coverage is 16.90%.

@@            Coverage Diff             @@
##           master    #7965      +/-   ##
==========================================
- Coverage   53.69%   53.60%   -0.10%
==========================================
  Files         563      563
  Lines       28555    28622      +67
  Branches     5541     5556      +15
==========================================
+ Hits        15334    15342       +8
- Misses      12224    12283      +59
  Partials      997      997

Impacted Files
Coverage Δ

...on/src/pre-push-cfn-processor/cfn-pre-processor.ts
30.35% <11.36%> (-69.65%)
:arrow_down:

...amplify-cli-core/src/state-manager/stateManager.ts
35.88% <14.28%> (-3.86%)
:arrow_down:

.../amplify-cli-core/src/state-manager/pathManager.ts
67.74% <50.00%> (-0.39%)
:arrow_down:

...y-provider-awscloudformation/src/push-resources.ts
9.78% <50.00%> (-0.02%)
:arrow_down:

packages/amplify-cli-core/src/errors/index.ts
84.61% <100.00%> (+0.61%)
:arrow_up:

packages/amplify-cli-core/src/index.ts
96.29% <100.00%> (+0.14%)
:arrow_up:

Continue to review full report at Codecov.

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


Update Laravel to v5.7

This adds support for the packages of Laravel 5.7, so this library can be installed for apps running Laravel 5.7.

Hello, when can you approve the pull request?  I need to download the file and modify the composer.json to add |5.7 manually.
thank you.

See #33


Bump jinjava version

Hi @terefang,
I'm using this Maven plugin in my java-iban project. I ran into a problem there: the 2.4.8 version of hubspot jinjava is incompatible with Java 11; there's some kind of bytecode issue.
I worked around it by pinning the plugin execution to the current 2.5.6 release of jinjava, but of course an upstream fix would be more convenient.
I can make a PR if you want, but merging that is hardly less work than updating the reference. LMK if you'd appreciate one.
Thanks,
Barend

hello
you should see 2021.4.28 with jinjava 2.5.6 on jitpack maven
good to know that this maven-plugin is useful for others too.
thx and enjoy.

Works as intended. Thanks!


Automatically execute a program or script when opening a new terminal

Everytime when I open a new terminal in vscode (v1.13.1), I would have to manually run a program or script to do some setup.  Is it possible to configure vscode such that whenever a terminal is newly opened, it will auto trigger a specified program or script ?

Another way of saying would be, is it possible  that upon opening a new terminal, a batch of custom commands (containing one or more commands) would be automatically entered into the terminal and executed

I have answered myself with the below code
{
"terminal.integrated.shellArgs.windows": ["-ExecutionPolicy","Bypass","-NoLogo","-NoProfile","-NoExit", "-Command", "D:\setPath.ps1"]
}


Server closing after reload finishes

When I do the /reload command in mc 1.13 with a plugin configured to use your api (as per your README), the server correctly reloads, but after it is done with the reload, it acts as if the /stop command is issued.
[21:59:03 INFO]: CC007 issued server command: /reload
[21:59:03 INFO]: CC007: Please note that this command is not supported and may cause issues when using some plugins.
[21:59:03 INFO]: CC007: If you encounter any issues please use the /stop command to restart your server.
[21:59:03 INFO]: Debug logging is disabled
[21:59:03 INFO]: Server Ping Player Sample Count: 12
[21:59:03 INFO]: Using 4 threads for Netty based IO
[21:59:03 INFO]: -------- World Settings For [world] --------

...

[21:59:06 INFO]: Loaded 524 recipes
[21:59:08 INFO]: [HeadsPluginAPI] Loading HeadsPluginAPI v2.0.0-SNAPSHOT
[21:59:08 INFO]: [HeadsPluginAPI] Enabling HeadsPluginAPI v2.0.0-SNAPSHOT
[21:59:08 INFO]: 21:59:08.681 [Server thread] DEBUG org.springframework.core.env.StandardEnvironment - Activating profiles []

[21:59:08 INFO]:   .   ____          _            __ _ _
[21:59:08 INFO]:  /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
[21:59:08 INFO]: ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
[21:59:08 INFO]:  \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
[21:59:08 INFO]:   '  |____| .__|_| |_|_| |_\__, | / / / /
[21:59:08 INFO]:  =========|_|==============|___/=/_/_/_/
[21:59:08 INFO]:  :: Spring Boot ::

...

[21:59:09 INFO]: 21:59:09.499 [Server thread] INFO org.springframework.boot.SpringApplication - Started application in 0.912 seconds (JVM running for 608.745)

[21:59:09 INFO]: Server permissions file permissions.yml is empty, ignoring it
[21:59:09 INFO]: CC007: Reload complete.
[21:59:09 INFO]: Stopping server
[21:59:09 INFO]: [HeadsPluginAPI] Disabling HeadsPluginAPI v2.0.0-SNAPSHOT
[21:59:09 INFO]: 21:59:09.534 [Server thread] DEBUG org.springframework.context.annotation.AnnotationConfigApplicationContext - Closing org.springframework.context.annotation.AnnotationConfigApplicationContext@1c173391, started on Sat May 18 21:59:08 CEST 2019

[21:59:09 INFO]: Saving players
[21:59:09 INFO]: CC007 lost connection: Server closed
[21:59:09 INFO]: CC007 left the game
[21:59:09 INFO]: Saving worlds
[21:59:09 INFO]: Saving chunks for level 'world'/overworld
[21:59:09 INFO]: Saving chunks for level 'world_nether'/the_nether
[21:59:09 INFO]: Saving chunks for level 'world_the_end'/the_end
>Press any key to continue . . .

I have not implemented anything more than the required things (maven dependency, SpringBootApplication annotated class, and the JavaPlugin class with onEnable and onDisable)

Also confirmed with 1.13.2

Hello, this behavior is caused by Spring trying to dispose the Server bean, which causes it to shutdown. It was fixed in 0.10.1.
Thanks for reporting!


"extends" keyword generates compile error

example:
extends ./layout.jade
generates the error message:
the "filename" Option is required to use "extends" with "relative" paths.

Please try the latest version.

Thank you. The "extends" keyword works perfectly.

:smiley:


Command sendpin fails on Trezor One where passphrase is required

On Trezor One devices where the togglepassphrase command has been used to require keyboard passphrase entry, the sendpin command fails:
❯ ./hwi.py --device-path "webusb:xxxxxx" --device-type "trezor" sendpin 12345678
{"error": "get_passphrase() got an unexpected keyword argument 'available_on_device'", "code": -13}

The device does however display 'Please enter your passphrase using the computer's keyboard.', so it appears the pin entry was successful. Firmware version is 1.9.4.

I think this was already fixed via https://github.com/bitcoin-core/HWI/pull/481

The testing was done with HEAD (changes from #481 included).

Confirmed using a Windows build of latest master as well. I've had user reports that the Trezor T is also affected (I don't have one to test with).


protocols vs concrete types

Basically we have two kinds of types in S4.
Data types:
Types that simply hold information in a structured manner. For example, a collection of bytes, URI, HTTP response, etc.
Behaviour types:
Types that manipulate information based on a pre-defined behaviour. For example, streams, http servers, routers, etc.
I think we all agree that behaviour types should definitely be protocols. But I'm not sure about data types.
Data types could be either protocols or concrete types. I think it's very important to discuss the advantages and disadvantages of both approaches, as this will guide a lot of decisions we take regarding S4 types.

I think protocols give the end users of S4 the most freedom.
For example, if an implementation conforming to S4 wants reference semantics on their Requests, they would have to convert their instance of Request class into an S4.Request Struct instead of being able to simply pass their Request in.
Protocols give the implementer the freedom to do whatever they want and whatever makes sense for their library. And it's what I think Swift intended protocols for.

One of the perceived disadvantages of using protocols instead of concrete types is that protocols can't conform to other protocols. While that's true, protocols can provide implementations for other protocols in where clauses and if it's especially important that a data type implement other protocols we can always use protocol inheritance. I'd like to see some examples where either using protocol extensions or protocol inheritance would be undesirable. For now I'm leaning towards protocols.

In fact I'm leaning towards making nearly everything a protocol. Zewo can write its implementation and Vapor its own with their preferences for value types vs. reference types.

While that's true, protocols can provide implementations for other protocols in where clauses.

That wouldn't work.
Say we have this in S4:
public protocol HTTPRequest: HTTPMessage {
    var method: HTTPMethod { get set }
    var uri: URI { get set }
}

public protocol HTTPResponse: HTTPMessage {
    var status: HTTPStatus { get }
}

And we have a LogMiddleware package with this:
import S4

extension HTTPRequest where Self: CustomStringConvertible {
    var description: String {
        return "\(method) \(uri)"
    }
}

extension HTTPResponse where Self: CustomStringConvertible {
    var description: String {
        return "\(status.statusCode) \(status.reasonPhrase)"
    }
}

public struct LogMiddleware: HTTPMiddleware {
    public func respond(request: HTTPRequest, chain: HTTPResponder) throws -> HTTPResponse {
        let response = try chain.respond(request)
        print(request.description)
        print(response.description)
        return response
    }
}

That outputs:
error: type 'HTTPRequest' does not conform to protocol 'CustomStringConvertible'
        message += "\(request.description)\n"
error: type 'HTTPResponse' does not conform to protocol 'CustomStringConvertible'
        message += "\(response.description)\n"

If we make the protocol itself inherit from CustomStringConvertible:
Say we have this in S4:
public protocol HTTPRequest: HTTPMessage, CustomStringConvertible {
    var method: HTTPMethod { get set }
    var uri: URI { get set }
}

public protocol HTTPResponse: HTTPMessage, CustomStringConvertible {
    var status: HTTPStatus { get }
}

And we have a LogMiddleware package with this:
import S4

public struct LogMiddleware: HTTPMiddleware {
    public func respond(request: HTTPRequest, chain: HTTPResponder) throws -> HTTPResponse {
        let response = try chain.respond(request)
        print(request.description)
        print(response.description)
        return response
    }
}

That would work, but that's not flexible, cause S4 would have to define the protocols HTTPRequest and HTTPResponse protocols inherit from. So in this regard protocols are not flexible.

Now if we use concrete types ( struct or a class)
public struct HTTPRequest: HTTPMessage {
    public var method: HTTPMethod
    public var uri: URI
    public var version: HTTPVersion
    public var headers: HTTPHeaders
    public var body: HTTPBody
    public var storage: Storage = [:]
}

public struct HTTPResponse: HTTPMessage {
    public var version: HTTPVersion
    public var status: HTTPStatus
    public var headers: HTTPHeaders
    public var body: HTTPBody
    public var storage: Storage = [:]
}

And we have a LogMiddleware package with this:
import S4

extension HTTPRequest: CustomStringConvertible {
    public var description: String {
        return "\(method) \(uri)"
    }
}

extension HTTPResponse: CustomStringConvertible {
    public var description: String {
        return "\(status.statusCode) \(status.reasonPhrase)"
    }
}

public struct LogMiddleware: HTTPMiddleware {
    public func respond(request: HTTPRequest, chain: HTTPResponder) throws -> HTTPResponse {
        let response = try chain.respond(request)
        print(request.description)
        print(response.description)
        return response
    }
}

This would work. So concrete types are more flexible than protocols in regard to protocol conformance in extensions.

Now about safety. What makes protocols look more flexible for data types, is that they allow the type implementation to be a value type or a reference type. IMO this is a disadvantage cause this duality could be a big source of bugs, as one implementation could expect a reference type and another one a value type. So this two kinds of implementations are incompatible. We're looking for a standard here. So having code that adheres to a standard and is not compatible with code that also adheres to the same standard simply doesn't make sense.
Say we have this in S4:
public protocol HTTPRequest: HTTPMessage {
    var method: HTTPMethod { get set }
    var uri: URI { get set }
}

public protocol HTTPResponse: HTTPMessage {
    var status: HTTPStatus { get }
}

And we have a ContentNegotiationMiddleware package with this:
import S4

public struct LogMiddleware: HTTPMiddleware {
    public func respond(request: HTTPRequest, chain: HTTPResponder) throws -> HTTPResponse {
        var response = try chain.proceed(request)

        if let content = response.content {
            let mediaTypes = request.accept.count > 0 ? request.accept : self.mediaTypes
            let (mediaType, body) = try serialize(content, mediaTypes: mediaTypes)
            response.contentType = mediaType
            response.body = body
        }

        return response
    }
}
```

This implementation expects request to have value type semantics. So if the request has reference type semantics, when you pass the request along the chain:

```swift
var response = try chain.proceed(request)
```

Some other element in the chain could modify the request, for example changing the `accept` header. So this line:

```swift
let mediaTypes = request.accept.count > 0 ? request.accept : self.mediaTypes

Could not (and probably won't) reflect the request as it reached ContentNegotiationMiddleware.
We could protect ourselves from this by doing:
import S4

public struct LogMiddleware: HTTPMiddleware {
    public func respond(request: HTTPRequest, chain: HTTPResponder) throws -> HTTPResponse {
        let requestCopy = request.copy()
        var response = try chain.proceed(request)

        if let content = response.content {
            let mediaTypes = requestCopy.accept.count > 0 ? requestCopy.accept : self.mediaTypes
            let (mediaType, body) = try serialize(content, mediaTypes: mediaTypes)
            response.contentType = mediaType
            response.body = body
        }

        return response
    }
}
```

This would copy the request as it got to `ContentNegotiationMiddleware`:

```swift
let requestCopy = request.copy()
```

But for this to be possible all implementations of `HTTPRequest` would have to implement the `copy()` function. Even `structs` which are already copy-by-value. So in the end we're adding more code and more complexity everywhere and getting no flexibility, cause we would have to protect from value type semantics or reference type semantics, which would only be more confusing and make compatibility a nightmare. If we chose a concrete type for **data types** all of this could be avoided. Now if we go for value type semantics or reference type semantics is a whole other issue. My point here is we should go for concrete type instead of protocols for **data types**.

That's true, it would require type-casting the protocol to check for conformance at the use site, which would be less than ideal. However, that being said, Zewo, Vapor and others that write their own implementations of the standards, they could have their own protocols that can incorporate their framework types:
import S4

protocol Middleware : S4.Middleware {

    func respond(request: Zewo.Request, chain: Zewo.Responder) throws -> Zewo.Response
    func respond(standardRequest standardRequest: S4.Request, chain: S4.Responder) throws -> S4.Response

}

extension Middleware {

    func respond(request: S4.Request, chain: S4.Responder) throws -> S4.Response {
        guard let request = request as? Zewo.Request, chain = chain as? Zewo.Responder else {
            return try respond(standardRequest: request, chain: chain)
        }
        return try respond(request, chain: chain)
    }

}

I agree though that that is a strong argument for concrete types, but it could be managed.

So in the end we're adding more code and more complexity everywhere and getting no flexibility, cause we would have to protect from value type semantics or reference type semantics, which would only be more confusing and make compatibility a nightmare. If we chose a concrete type for data types all of this could be avoided.
Another strong argument for concrete types.

There's also the issue that protocols can't be keys to dictionaries. Yes we could add more code to make that possible. But that goes with what I said before about adding more code and more complexity to solve this issue.

I think I'm siding with Paulo now, but we should get more input from Logan and Tanner.

Actually we should get more input from the world haha. What do we need to go public?

For this:
public protocol HTTPRequest: HTTPMessage, CustomStringConvertible {
    var method: HTTPMethod { get set }
    var uri: URI { get set }
}

public protocol HTTPResponse: HTTPMessage, CustomStringConvertible {
    var status: HTTPStatus { get }
}

We could easily add:
extension HTTPResponse {
    var description: String {
        return "asdf"
    }
}

Which seems to accomplish the same thing as an enforced concrete ype

If you make S4.Response a struct then the only way Vapor would implement that is having something like
extension Vapor.Response {
    func toS4Response() -> S4.Response {
         //create S4.Response here
    }
}

Because Vapor, and I'm sure any other framework, would not want to do the major refactoring it would take to do Vapor.Request: S4.Request.
So if we're okay with people needing to do that then why not have an S4.ResponseConvertible protocol that would make it more standard. Then we're back to having a protocol.

Concrete types w/ Convertible protocols seems to be the current consensus


Section title on the left sidebar

Tiddlers tagged with $:/tags/SideBar are displayed on the left sidebar. If they do not have a non-empty caption field, the section appears on the left sidebar with empty title. See below screenshot.

You can use the below solution which has a fallback if there is no caption
<$view field=caption>
   <$view field=title/>
</$view>

Furthermore if the caption content is a CamelCase (link) then it is hidden as the link color and section header color are the same.

Furthermore if the caption content is a CamelCase (link) then it is hidden as the link color and section header color are the same.

Thanks for reporting this @kookma.

Thanks for reporting this @kookma.

@kookma I'll go for a slightly different fix using $transclude and setting tv-wikilinks to no, so that transclusion of the caption field still works.

@kookma I'll go for a slightly different fix using $transclude and setting tv-wikilinks to no, so that transclusion of the caption field still works.


Automerge does not work for AWS apigateway

What happened?
This PR had to be manually merged:
https://github.com/pulumi/registry/pull/1229
Steps to reproduce
This has been true for all previous apigateway docs publications.
Expected Behavior
Automerge should get set by pulumi-bot, as per internal automerge GH Action.
Actual Behavior
Automerge did not get set.
Versions used
n/a
Additional context
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Per https://github.com/pulumi/registry/blob/bffa152260518abeff4795756ce5120680f53c05/community-packages/package-list.json#L36, this is listed as a community package and hence does not fall under automerge.
Apologies for the noise.


update dependencies and toolchain

 Update Backend

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

435 of 448 (97.1%)  changed or added relevant lines in 36 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 84.179%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

datatypes/src/primitives/feature_data.rs
13
15
86.67%

operators/src/source/ogr_source/mod.rs
9
12
75.0%

datatypes/src/collections/feature_collection_builder.rs
16
24
66.67%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
35138

Relevant Lines:
41742

💛  - Coveralls

bors merge


Investigate restoring timer based SysTime

For #760, we simplified the SysTime implementation to just rely on DateTime.UtcNow.
The original idea behind SysTime was for controlling real world devices where any automatic wallclock adjustments could cause problems.  I never really implemented/tested this on Linux/OSX/mobile and we ended up simplifying this in #760.
This should be OK because we're not controlling devices at this time but it may be worth revisiting this in the future.
Putting this on the backlog as low priority.

CLOSING: we haven't needed this in over three years


add rel="me" attribute to mastodon links

When you add your website to your Mastodon account's profile metadata, it suggests you add a link back to the mastodon profile on the webpage with the rel="me" attribute. This allows mastodon to verify the website is affiliated with the account and displays a little flair along with it letting users know as such.
This theme already includes links back to the mastodon profile when configured (both at the top on the header, as well as on the footer), but the links don't include the rel="me" attribute. This should be a trivial change and I'm happy to PR it, but my last PR doesn't even seem to have been looked at yet, so I thought I would start with creating an issue.

This would be really great!

Using rel=me is important, inter alia, for verification on Mastodon. That's becoming very mainstream now for obvious reasons.
The original idea https://microformats.org/wiki/rel-me was that this would be a bidirectional relationship, which implies the rel=me should ideally be only on the canonical about page or mainpage (example: https://github.com/publiccodenet/jekyll-theme/pull/101/files ), but that's not too strict.


chore: correct pre upgrade pod name

Correct pre-upgrade job pod name.
Ref: longhorn/longhorn#5131, https://github.com/longhorn/longhorn/pull/5567

@mantissahz forgot to ask. Did you regenerate the deploy.yaml?

@mantissahz forgot to ask. Did you regenerate the deploy.yaml?

Yes, run ./scripts/generate-longhorn-yaml.sh and no change.


Fix types for cache functions with all optional arguments

cache functions with all optional arguments are currently casted to (...args: never[]) => T as [] apparently extends tuples with all optional values. This fixes that by doing the [] extends comparison against the argument list with optionality removed. This should be fine since the only important part of that check is whether there are >0 arguments, we don't really care about the types.

I don't know better but I trust you.


Q6.2b & 6.2C

When the user selects a species, show the question text for 6.2c and checkboxes for seedling and propagule.
If a use selects either checkbox, show a dropdown for source and a numeric input for count.
N.B. The options in the Source dropdown are different for seedling and propagule

3-10 days (of time, not billed hours, buffered for gotchas etc)

@alanjleonard do you know what are all the options are in the drop down for source?


Geometry differences between web-ifc demo page and OBC.IfcLoader

Describe the bug 📝
Hi @agviegas  and @HoyosJuan, could you please take a look at the issue disscused at https://github.com/ThatOpen/engine_web-ifc/issues/1057 ? We got different results after uploading ifc files to web-ifc demo page(https://thatopen.github.io/engine_web-ifc/demo) and engine-components viewer using OBC.IfcLoader<EMAIL_ADDRESS>and "@thatopen/components-front": "2.2.2",
"@thatopen/components": "2.2.11"). Web-ifc demo page all ifc files shows correctly - when using components - geometry errors appear. There are sample screenshots and ifc files.
Reproduction ▶
No response
Steps to reproduce 🔢
Load ifc in newer components
System Info 💻
@thatopen/components-front": "2.2.2",
@thatopen/components": "2.2.11"

Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Community.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hey @robertbiskup! That's beacuse we haven't update the web ifc dependency in components yet. Will be donee for release 2.3.0 coming this week.

@HoyosJuan Thank you for the quick answer! This is crucial information, I thought that setting the "wasm" parameter was enough, so we are waiting for the update! ;)

Hey @robertbiskup can you try with 1.3.0 and let us know how it goes?

Hi @agviegas I have tried with 2.3.0 "@thatopen/components-front": "2.3.0",
"@thatopen/components": "2.3.0") but there are still some diffrences with openings as the screenshots below show:
web-ifc demo:

components:

I will send you this test file in the private message in openers chat. If you could check whether the problem also occurs in your version of components, I would be grateful.

Hey @robertbiskup did you also update the web-ifc dependency in your project to be the latest?

@agviegas, after "npm install" I have version 0.0.59 of web-ifc in the "node_modules" folder (and "@thatopen/components-front": "2.3.0", "@thatopen/components": "2.3.0"), I use the rollup to build the bundle.js file and there I have the code to load ifc:

Hey @robertbiskup you are right, I could reproduce this. It turns out there have been some very recent improvements in web-ifc that are not included in .59 (published 2 weeks ago). We'll publish them soon and update components :)

Updated the latest changes of web-ifc in<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Hey @agviegas, I updated libraries to  "@thatopen/components-front": "2.4.2",
"@thatopen/components": "2.4.2",
"@thatopen/fragments" : "2.4.0",
"web-ifc": "0.0.66", and there are still a few errors (lesst han before) on the components side that are not present on the web-ifc demo page, I'll send you fragment of this model in private message to check


Problem when generating docker container

Collecting YoBit==<IP_ADDRESS> (from -r requirements.txt (line 20))
  Downloading https://files.pythonhosted.org/packages/97/84/4ae53f246d394203cba164dd7930c6c07c90771836af3a84631eae0057fd/YoBit-<IP_ADDRESS>.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-WabWW7/YoBit/setup.py", line 15, in <module>
        exec(f.read(), about)
      File "<string>", line 1, in <module>
      File "YoBit/__init__.py", line 15, in <module>
        import requests
    ImportError: No module named requests

https://github.com/Mambix/yobit/pull/3

Is this project not developing anymore?

I believe it's not


⚠ Moncai has degraded performance

In f5e3198, Moncai (https://moncai.com.au) experienced degraded performance:

HTTP code: 200
Response time: 12906 ms

Resolved: Moncai performance has improved in 3aed5a1.


feat: cowswap get trade quote method implementation

This implements getCowSwapTradeQuote method (closes https://github.com/shapeshift/lib/issues/724)
This also changes the getCowSwapMinMax method to match what is possible to do on cowSwap api.
Using a similar way of fetching gasPrice / estimateGas as to what has been done for thorchain (with slight differences).
This can be verified in unit test.
It can also be tested with swapcli (with a wallet with erc20 on it), code at the end can help.
It can be called in packages/swapper with following line :
yarn swapcli eip155:1/erc20:0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 eip155:1/erc20:0xc770eefad204b5180df6a14ee197d99d808ee52d 1
Example output :

const cowSwapperDeps = {
    apiUrl: 'https://api.cow.fi/mainnet/api/',
    web3,
    adapter: ethChainAdapter
  }

  const manager = new SwapperManager()
  const zrxSwapper = new ZrxSwapper(zrxSwapperDeps)
  console.log(zrxSwapper.getType())
  const cowSwapper = new CowSwapper(cowSwapperDeps)
  manager.addSwapper(SwapperType.CowSwap, cowSwapper)
  //manager.addSwapper(SwapperType.Zrx, zrxSwapper)
  const swapper = await manager.getBestSwapper({
    sellAssetId: 'eip155:1/erc20:0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2',
    buyAssetId: 'eip155:1/erc20:0xc770eefad204b5180df6a14ee197d99d808ee52d'
  })

@elmutt I have been able to play with it with web for the first time. I was able to get some quotes value out of this. I found potentially a couple things to fix / improve (not necessarily related to this PR), that I can bring in my next PR hopefully.

@elmutt @DaoDev44 Fixed a couple issues after being able to integrate this into web, that could warrant another review ...
Some screen of a quote displayed in console in web : (buildTrade not yet implemented)

@chxash we might want to just pass WETH to avoid initializing an entire asset service. This could be passed as the feeAsset or something like that.

A bunch of non-blocking comments to be tackled in the follow-up PR but otherwise LGTM 🍬

Linked your review comments so they are tackled in follow-up PR ! thank you


During packaging, assert json reports an error

vue3  + vite
node version ：v16.17.1
@iconify-json/ep : v1.1.11
Unexpected token (Note that you need plugins to import files that are not JavaScript)

1: import icons from './icons.json' assert { type: 'json' };
                                    ^
2: import info from './info.json' assert { type: 'json' };
error during build:
Error: Unexpected token (Note that you need plugins to import files that are not JavaScript)

You need to update node

您需要更新节点

@cyberalien
I have reverted the version of the @iconify-json/ep package to 1.1.8.
Of course, I also noticed the suggestion to update the node version to 17 or higher.
Thank you for your response

That works too.
Unfortunately there is no way to support both old and new versions of node. Old version cannot handle assert, new version doesn't work without `assert

That also works.
Sure, I'll translate the text for you. Please provide the text you would like me to translate
Unfortunately, there is no way to provide support for both older and newer versions of Node. The older version is unable to handle the assert function, while the newer version cannot function properly without it.
Yes, unfortunately. This will cause inconvenience for both users and warehouse maintenance personnel


how to use env variables in SW for Workbox 5

Library Affected:
const { InjectManifest }        = require('workbox-webpack-plugin');.
Browser & Platform:

Google Chrome Latest.*

Issue or Feature Request Description:
I am using workbox-webpack-plugin 5.0.0
Question 1)
Now,  In my project, I have a index.js file looking like this:
module.exports = Object.freeze({
    app: require('./app'),
    company: require('./company'),
    api: require('./api'),
    locales: require('./locales'),
    services: require('./services'),
});

and let's take a look of one of the files app: require('./app')
module.exports = {
    url: process.env.API_URL
};

what I now need is to use those variables in my service worker file. I can't import index.js file since I don't copy/paste it via copy-webpack-plugin.  What other ideas do you have on your mind, Jeff ?  I tried:
webpackCompilationPlugins:[
                new DotEnvWebpack({ systemvars: true })
            ],

but when I console process.env in service-worker, It's an empty object.
What do I do ? @jeffposnick
Question 2)
In my sw.js, I have this:
importScripts('/js/indexedDb/idb.min.js')
importScripts('/js/indexedDb/utility.js')

I am thinking about a new way of including these in my sw.js. idb.min.js is already compiled which is great, but my utility.js is not compiled which makes me worried. Is there any way I don't import those scripts, but somehow by using injectmanifest plugin, i can still compile and include it somehow in my final bundled sw.js?

My understanding is that webpack child compilers (which the workbox-webpack-plugin uses) don't inherit the plugins specified in the main config, which means that any plugins you use there will not be applied to your final service worker file.
@jeffposnick, can you confirm? If so, would it be possible to add an option to workbox-webpack-plugin to pass in child-compiler config overrides?
@novaknole, another option you can do now would be to compile your service worker separately from the rest of your app. There's some guidance on how to do that here: https://developers.google.com/web/tools/workbox/guides/using-bundlers

I have injectManifest working for other cases. i can't just change the whole logic of bundling service worker. There should be some way to somehow pass env variables to service worker through InjectManifest.  Nobody has needed this before?
@jeffposnick shoot some ideas .
Thanks both of you.

Regarding question 1, as soon as https://github.com/GoogleChrome/workbox/pull/2400 is deployed in the next Workbox release, using webpackCompilationPlugins should work.
(I am working on fixes for https://github.com/GoogleChrome/workbox/issues/2383 and https://github.com/GoogleChrome/workbox/issues/2399 that I'd also like to ship in the next release, but if that ends up taking too long, maybe we could ship v5.0.1 with just #2400 included. This has all been delayed in general due to changing work conditions.)
Regarding question 2, if you write your utility.js as an ES module with exports, you can switch from using importScripts() and instead write something that consumes the module exports, and gets compiled into a single final swDest file by webpack:
// In your src/utility.js:

export default {
  myFirstFunction: () => {...},
  mySecondFunction: () => {...},
};

// In your swSrc:

import idbUtils from 'src/utility.js';

// Do something with idbUtils.myFirstFunction(), etc.

This works exactly the same as consuming the Workbox runtime modules works in v5.

(Also, before #2400 ships, you should be able to put your environment variables into a dedicated chunk that is compiled by the main webpack compilation, and then consume that chunk in your swSrc file via the same mechanism that you would refer to a chunk into any other source file that's compiled by webpack.)

Hey @jeffposnick , do you have an approximate timeframe for when #2400 will be released as this will determine what solution I will implement now based on whether or not i should wait or not.

This is now available in the v5.1.1 release: https://github.com/GoogleChrome/workbox/releases/tag/v5.1.1


Ncbi-genome-download

Hi, I was trying to download the genome for NCBI using ncbi-genome-download, When I ran the anvi-script-process-genbank-metadata script, I got the genomes, but they are not the same size as those in the database. I wanted to know why there is a difference in size. Can you help?

Hi @manik-123, if you can provide a reproducible set of commands we may be able to look into this and comment further. Apart from that, if the genomes you get differs from the one on the NCBI, it is likely a question for the ncbi-genome-download project.
Sorry for not being able to help more here.

Plus, you sent this issue to the merenlab.org repository :) If you would like to get back to this with more info, please use the anvi'o GitHub.


Wiki page 'JavaScript Language Service in Visual Studio' has broken link

Inside wiki page JavaScript Language Service in Visual Studio there is the following fragment:

For example, JavaScript IntelliSense can be provided for values declared in a .d.ts file (more info)

Where more info is a broken link pointing to https://github.com/Microsoft/TypeScript-Handbook/blob/master/pages/Writing Definition Files.md

PRs accepted at https://github.com/Microsoft/TypeScript-wiki

@DanielRosenwasser Addressed in https://github.com/Microsoft/TypeScript-wiki/pull/192

This was addressed


fix: update release rules to assume style is patch

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix/suppress current eslint warnings

This also raises import/no-unresolved and import/extensions to error level
everywhere except docs.
I didn't touch the warning about lacking tests for addons/notes so that it keeps reminding that they still have to be written.
It would be nice if we could find a way to know if some new warnings are introduced with a PR (like it's done with code coverage). Does anyone know how to get this metric from CircleCI?

Thinking out loud - can we maybe create a separate CI job for the linting that will be run with the error level for every rule. This job will not prevent anything from merging, but just illustrate the worst picture of the PR.

a separate CI job for the linting that will be run with the error level for every rule

The problem is it would be red for all subsequent PRs even if they don't introduce new warnings, so it wouldn't really give much value


Fix iperf-related issues

With these changes, the project should compile and run on an actual device

Review ok


Position should be sticked when scrolling UITableView.

I have a UITableView with 2 section and 5 rows in each sections.
I have added floating button in viewDidLoad method.
Output showing button at end of view, but not on the tableView's end of row.

Hello, @Rashesh-Bosamiya
KCFAB's default position is bottom-right of superview.
If you want KCFAB's position set to tableView's end of row, you should calculate position.


fix env

Fix pip install error:
Could not find a version that satisfies the requirement opencv_contrib_python==[<IP_ADDRESS>]

Version <IP_ADDRESS> is no longer found on the pip source.

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


Jenkins CI builds

It'd be nice to have for testing development versions https://github.com/jenkinsci
Unfortunately, I know nothing about mobile development, but maybe someone could add support for it

We have added GitHub Actions CI now, the main branch produces signed builds.


Find best uptime monitoring tool combination

Seems like this problem is tougher than I though. Right now I see several option

[ ] go as devin uptime robot and local hearthbeat deployed bot on k8s
[ ] uptime kuma on k8s (I don't like this)
[ ] stay rock64 just for uptime kuma (I dont' like this)
[x] deploy uptima kuma on eunomia or cloud instance (problem that when I have outage everything goes blank
[ ] deploy health check for external serices ( router public ip and blog)
[ ] use prometheus for monitoring using blackbox exporter
[ ] deploy some light tool inside the lxc conatiner (or it's possible to install uptime kuma without docker)
[ ] external monitroing https://healthchecks.io/

Current setup is efficient enough. For home lab it's enough. Only problem is that those checks are through VPN.

I am unhappy with current solution. I am seriously thinking to migrate to gatus. But 10$ per month 💸

Waiting for https://github.com/axeII/home-ops/issues/839


Folder help

Navigate to /Nintendo 3DS/(32 Character ID)/(32 Character ID)/extdata/00000000/ on your SD card
EUR Region: Delete 00000098
JPN Region: Delete 00000082
USA Region: Delete 0000008f
KOR Region: Delete 000000A9
TWN Region: Delete 000000B1
I am on this step of downgrading, my system is on 9.2 now. I took out the sd card and put it in my computer to delete USA region :000008f. Put it back in my 3ds and it reconfigured home menu for some reason so I reput it in my computer to check if it put the folder back and it did. Is that folder suppose to be permenently deleted?

Nevermind! I am almost done, restoring NAND after 2.1 firmware

That step is just do delete menuhax. So it's normal the console creates that folder again.


[Event Hubs] format source files with prettier

This PR formats the @azure/event-hubs package by running the format NPM script found inside its package.json.

Woohoo! Now lets rebase/merge the code in the other PRs