New JSON serializer

We may want to evaluate jfc JSON serializer. It looks really nice, and many times nicer that poor Play JSON support.

Well, we don't use "poor Play JSON support". We use upickle: https://github.com/codingteam/loglist/blame/master/project/Build.scala#L105
And you are the one who introduced this dependency. Can that jfc work both on JVM and JavaScript?

Oh, if we are going to use TypeScript + Finch, jfc doesn't need to work on JavaScript platform. Anyway, is it really better than upickle?

Disregard that, we still use Play poor JSON support: https://github.com/codingteam/loglist/blob/2e53256a5cf90e069235102d323ab626d1cebd1e/scalajvm/app/helpers/ReCaptcha.scala#L21

But okay, we'll need to discuss further our migration to Finch / whatever. I'll close that for now.


runtime(menu): define shortcut for File->Open Tab

Seems missing as noted by Antonio Giovanni Colombo. So add it and use the 'T' as shortcut, which does not seem to be used in the File dialog.
Verified on Windows.

@chrisbra I think this needs to update all the localization files. I filed #12993 to reference this.


Track the Apple hardware string

Device model in the mobile context currently captures only the product name (e.g. iPhone), not the actual model. It would be useful if we could track the hardware string or identifier also (e.g. iPad6,3 or iPhone9,2):

https://www.theiphonewiki.com/wiki/Models
https://www.npmjs.com/package/apple-model-names

Closing due to duplicate ticket, #444 .


Feature: Dynamically apply aria-current to active page

Currently, aria-current is hardcoded and is only applied to the Home page link. The navigation would need retooling so aria-current is applied to the currently viewed page.

Ah yes, nicely spotted @djmtype! I'll add this functionality in a future update, along with two extra demo pages as an example for how aria-current works 🙂

@markteekman This is a cheap example that works:

Home

About

<-- etc.  -->

But maybe there's a way that integrates better with your setup.
Otherwise, splitting out the Navigation items into a JSON file might be better for client management with Netlify CMS, for example, then loop through the list.

Thanks for the suggestion @djmtype! I like the creativity of this solution 🙂 I think I'll ultimately use a click event listener on the
 element and change the aria-current attribute depending on which link is clicked. Nevertheless, that idea about setting the items in a JSON file is a really good one too! Maybe one for a future update, as I'm thinking of moving the Navigation.astro component to the accessible-astro-components package eventually.

Added in https://github.com/markteekman/accessible-astro-starter/releases/tag/v1.2.4, thanks again for the suggestion @djmtype 🙂


Fail to receive messages completely at the high publishing rate [5762]

Hi, I'm studying on this ROS2(rclcpp) issue https://github.com/ros2/rclcpp/issues/755. I found that this bug is not likely to be happened on the other DDS vendor(OpenSplice). So, I tried to reproduce this situation using FastRTPS's native API. The following codes are some modifications of FastRTPS example(HelloWorldExample).
First, I made HelloWorldPublisher to publish rapidly(100 microseconds).
void HelloWorldPublisher::runThread(uint32_t samples, uint32_t sleep)
{
    if (samples == 0)
    {
        while(!stop)
        {
            if(publish(false))
            {
                std::cout << "Message: "<<m_Hello.message()<< " with index: "<< m_Hello.index()<< " SENT"<<std::endl;
            }
            // eClock::my_sleep(sleep);
            usleep(100);
        }
    }
    else
    {
        for(uint32_t i = 0;i<samples;++i)
        {
            if(!publish())
                --i;
            else
            {
                std::cout << "Message: "<<m_Hello.message()<< " with index: "<< m_Hello.index()<< " SENT"<<std::endl;
            }
            //eClock::my_sleep(sleep);
            usleep(100);
        }
    }
}

Second, print out the number of received message and the index of the latest received message after HelloWorldSubscriber::run().
void HelloWorldSubscriber::run()
{
    std::cout << "Subscriber running. Please press enter to stop the Subscriber" << std::endl;
    std::cin.ignore();
    std::cout << "Subscribed count : " << this->m_listener.n_samples <<std::endl;
    std::cout << "Subscribed latest index : "  << this->m_listener.m_Hello.index() << std::endl;
}

Also, I give enough QoS resources to both of them.
Rparam.topic.historyQos.depth = 5000;
Rparam.topic.resourceLimitsQos.max_samples = 10000;
Rparam.topic.resourceLimitsQos.allocated_samples = 5000;

Lastly, I run HelloWorldPublisher before HelloWorldSubscriber.
Terminal 1
HelloWorldExample publisher 2000

Terminal 2
HelloWorldExample subscriber

Then, the output is following.
Terminal 1
...
Message: HelloWorld with index: 1998 SENT
Message: HelloWorld with index: 1999 SENT
Message: HelloWorld with index: 2000 SENT

Terminal 2
...
Message HelloWorld 254 RECEIVED
Message HelloWorld 255 RECEIVED
Message HelloWorld 256 RECEIVED
Subscriber unmatched
(Enter key pressed)
Subscribed count : 256
Subscribed latest index : 256

I guess the expected output should be Subscribed latest index : 2000 although Subscribed count < 2000. Is this right?

@clalancette In case of switching from "reliable" to "Best Effort" QoS,
HelloWorldPublisher.cpp
Wparam.qos.m_reliability.kind = BEST_EFFORT_RELIABILITY_QOS;

HelloWorldSubscriber.cpp
Rparam.qos.m_reliability.kind = BEST_EFFORT_RELIABILITY_QOS;

The output is following.
Terminal 1
...
Message: HelloWorld with index: 1998 SENT
Message: HelloWorld with index: 1999 SENT
Message: HelloWorld with index: 2000 SENT

Terminal 2
Message HelloWorld 1998 RECEIVED
Message HelloWorld 1999 RECEIVED
Message HelloWorld 2000 RECEIVED
Subscriber unmatched
(Enter key pressed)
Subscribed count : 1463
Subscribed latest index : 2000

Hi @vinnamkim,
That's because the publisher ends its execution before the subscriber receives all the samples since the publisher doesn't wait for them to be acknowledged.
This problem can be solved reducing the heartbeat period. For instance, you can use the following values:
Wparam.times.heartbeatPeriod.seconds = 0;
Wparam.times.heartbeatPeriod.nanosec = 1000*1000;

Or using the Publisher function wait_for_all_acked() after sending the samples, so that the publisher has to wait until all the samples are received and acknowledged by the subscriber.
If you implement any of those two alternatives the output will be the following:
Publisher Terminal
...
Message: HelloWorld with index: 1996 SENT
Message: HelloWorld with index: 1997 SENT
Message: HelloWorld with index: 1998 SENT
Message: HelloWorld with index: 1999 SENT
Message: HelloWorld with index: 2000 SENT

Subscriber Terminal
...
Message HelloWorld 1996 RECEIVED
Message HelloWorld 1997 RECEIVED
Message HelloWorld 1998 RECEIVED
Message HelloWorld 1999 RECEIVED
Message HelloWorld 2000 RECEIVED
Subscriber unmatched

Subscriber count : 2000
Subscriber latest index : 2000

I hope this helps you.

As this was answered and no comments were received, we close the issue. Feel free to reopen it if the problem persists.


feat: allow http keep alive

For server side usage it would be nice to keep alive http connection.
E.g here:
https://github.com/warp-contracts/warp/blob/c1bfb2f58518a4369c044c84fabcb7d070d4e092/src/contract/HandlerBasedContract.ts#L293
or here:
https://github.com/warp-contracts/warp/blob/c1bfb2f58518a4369c044c84fabcb7d070d4e092/src/contract/deploy/impl/DefaultCreateContract.ts#L117
(since some users create contracts dynamically)
Is it possible with current api? Could we externalize fetch options to e.g. use custom configuration of http agent?

Hey, nope, it's not possible with current api. I'm thinking about adding an option to register in warp instance some function (x: RequestInfo | URL) -> {} - that would take the original request data as parameter and return object with options, that should be attached to the fetch.
We could probably use here the new plugin API - https://github.com/warp-contracts/warp/blob/rc/evm-signature/src/core/WarpPlugin.ts - the plugin would take RequestInfo | URL as an input and return Partial<RequestInit>.
It could be then registered with
warp.forMainnet().use(new FetchOptionsPlugin())

Last but not least - the SDK will need to verify whether such plugin was registered - and if so, call it to determine the options and attach them to fetch.
@asiaziola , such a great task for you!

Hi @asiaziola, 👏👏👏
this is great!
For server side keep-alive usecase the plugin impl uses:
fetchOptions = {
   agent: new http.Agent({
     keepAlive: true
   })
};

Debugging SSL shows:
HTTPS 97208: createConnection [Object: null prototype] {
protocol: 'https:',
slashes: true,
auth: null,
host: 'd1o5nlqr4okus2.cloudfront.net',
port: 443,
hostname: 'd1o5nlqr4okus2.cloudfront.net',
hash: null,
search: '?contractId=ECzhNQQBwAf3TV0r4rDyr6zglCzWha57VoFyNmqMnsQ&from=000001081630%2C1671580571027%2C3005273068d18d0699e446a9c12dfbc28a786c5012f2e1c8e6680423043c3efd&page=1&fromSdk=true&confirmationStatus=not_corrupted',
query: 'contractId=ECzhNQQBwAf3TV0r4rDyr6zglCzWha57VoFyNmqMnsQ&from=000001081630%2C1671580571027%2C3005273068d18d0699e446a9c12dfbc28a786c5012f2e1c8e6680423043c3efd&page=1&fromSdk=true&confirmationStatus=not_corrupted',
pathname: '/gateway/v2/interactions-sort-key',
path: null,
href: 'https://d1o5nlqr4okus2.cloudfront.net/gateway/v2/interactions-sort-key?contractId=ECzhNQQBwAf3TV0r4rDyr6zglCzWha57VoFyNmqMnsQ&from=000001081630%2C1671580571027%2C3005273068d18d0699e446a9c12dfbc28a786c5012f2e1c8e6680423043c3efd&page=1&fromSdk=true&confirmationStatus=not_corrupted',
method: 'GET',
headers: [Object: null prototype] {
Accept: [ '/' ],
'User-Agent': [ 'node-fetch/1.0 (+https://github.com/bitinn/node-fetch)' ],
'Accept-Encoding': [ 'gzip,deflate' ]
},
agent: Agent {
_events: [Object: null prototype] {
free: [Function (anonymous)],
newListener: [Function: maybeEnableKeylog]
},
_eventsCount: 2,
_maxListeners: undefined,
defaultPort: 443,
protocol: 'https:',
options: [Object: null prototype] { keepAlive: true, path: null },
requests: [Object: null prototype] {},
sockets: [Object: null prototype] {
'd1o5nlqr4okus2.cloudfront.net:443:::::::::::::::::::::': []
},
freeSockets: [Object: null prototype] {},
keepAliveMsecs: 1000,
keepAlive: true,
maxSockets: Infinity,
...
}


missing bundle when trying to run?

When trying to use new file of the examples
sketch Version 3.5.1 (25234).

Did you use the installer, or did you double click the .sketchplugin file to install?

hey John - i just loaded the plugin CSSketch.sketchplugin.  Is there something else that needs installing from the zip? Thanks, D.

Could you try installing from the release https://github.com/JohnCoates/CSSketch/releases/latest
I've just switched CSSketch over to the SketchKit framework, and it requires that be installed as well, so I wrote a little installer.

that installer has done it! Thanks and looking forward to trying it out...

Hi, I have used Sketch Toolbox to install the plugin, followed by manual install. In all the cases I keep getting a missing bundle error.
I've tried to install on two separate machines one running ElCapitan and the other Sierra...

I got same issue

Same issue here


转换tflite的模型文件为MindSpore的量化模型时报配置文件的错误

命令行：
./converter_lite --fmk=TFLITE --modelFile=0918_mv2_0.35_FP32.tflite --outputFile=/home/vinbert/data/mindspore-lite-1.3.0-linux-x64/tools/converter/converter/mv2_int8.ms
--configFile=/home/vinbert/data/mindspore-lite-1.3.0-linux-x64/tools/converter/converter/full_quant.cfg
full_quant.cfg配置文件如下:
[common_quant_param]
Supports WEIGHT_QUANT or FULL_QUANT
quant_type=FULL_QUANT
Weight quantization support the number of bits [0,16], Set to 0 is mixed bit quantization, otherwise it is fixed bit quantization
Full quantization support the number of bits [1,8]
bit_num=8
Layers with size of weights exceeds threshold min_quant_weight_size will be quantized.
min_quant_weight_size=0
Layers with channel size of weights exceeds threshold min_quant_weight_channel will be quantized.
min_quant_weight_channel=16
[data_preprocess_param]
Calibration dataset path, the format is input_name_1:input_1_dir,input_name_2:input_2_dir
Full quantification must provide correction dataset
calibrate_path=input_1:/home/vinbert/data/mindspore-lite-1.3.0-linux-x64/tools/converter/converter/int8_data
Calibration data size
calibrate_size=100
Input type supports IMAGE or BIN
When set to IMAGE, the image data will be read
When set to BIN, the .bin binary file will be read
input_type=IMAGE
The output format of the preprocessed image
Supports RGB or GRAY or BGR
image_to_format=RGB
Image normalization
dst = (src - mean) / std
normalize_mean=[1.0, 1.0, 1.0]
normalize_std=[127.5, 127.5, 127.5]
Image resize
resize_width=192
resize_height=192
Resize method supports LINEAR or NEAREST or CUBIC
resize_method=LINEAR
[full_quant_param]
Activation quantized method supports MAX_MIN or KL or REMOVAL_OUTLIER
activation_quant_method=MAX_MIN
Whether to correct the quantization error. Recommended to set to true.
bias_correction=true
运行报错：
WARNING: Logging before InitGoogleLogging() is written to STDERR
[ERROR] LITE(1957,7f7c37fc7f00,converter_lite):2021-09-24-13:42:05.871.489 [mindspore/lite/tools/converter/converter_flags.cc:452] GetStrFromConfigFile] the config file is invalid, can not find '=', please check
[ERROR] LITE(1957,7f7c37fc7f00,converter_lite):2021-09-24-13:42:05.871.602 [mindspore/lite/tools/converter/converter_flags.cc:452] GetStrFromConfigFile] the config file is invalid, can not find '=', please check
[ERROR] LITE(1957,7f7c37fc7f00,converter_lite):2021-09-24-13:42:05.871.620 [mindspore/lite/tools/converter/converter_flags.cc:452] GetStrFromConfigFile] the config file is invalid, can not find '=', please check
CONVERT RESULT SUCCESS:0

请问一下转换工具的版本是多少？


Calling requque from a task with async generator dependency treats as dependency error

Python version: Python 3.12.2
Taskiq version: 0.11.6
Reproducer

import asyncio
from typing import Annotated

from taskiq import (
    Context,
    TaskiqDepends,
    InMemoryBroker,
)

broker = InMemoryBroker()

async def stub_dependency():
    yield None

@broker.task
async def some_task(
        context: Annotated[Context, TaskiqDepends()],
        _: Annotated[None, TaskiqDepends(stub_dependency)],
):
    await asyncio.sleep(1)
    await context.requeue()

async def main():
    task = await some_task.kiq()
    await task.wait_result(timeout=10)

if __name__ == '__main__':
    asyncio.run(main())

It was expected that the dependency would not change the behavior of the task, but it does.
And, please, add NoReturn typehint to requeue method. Thank you for the project!

I've figured out that this is more design question than a bug. There is a way to disable error propagation through dependencies. And Receiver.task_run method's code explicitly defines that error propagation treats requeue in the same way as other exceptions. This code works properly for me if pass kwarg propagate_exceptions=False to InMemoryBroker.


V2 - CLA Not Signed - Identify CLA Manager designee - CLA Manager Designee role is assigned for both Foundation and child projects when CLA Group is at foundation level

Prerequisite

Create a CLA group with CCLA enabled (I tried the flow where CLA Group is at foundation level and there is only 1 subproject for the foundation)
Add github repository for the CLA group

Steps to Follow

Login to Github as corporate contributor
Navigate to the repository used in prerequisite
Create PR
CLA check fails
Click on CLA NOT SIGNED
Contributor is redirected to Contributor Console
Click on Proceed as a Corporate Contributor
Select Company that has not signed CLA for the project
Click Proceed
Click No
Enter name and email of user who has LFID and is associated with the selected company
Observed that CLA Manager desginee role is assigned for both foundation and child

Issue is still reproducible

Verified that the issue is fixed

Verified that the issue is fixed


New site support request

Hello,
I like this program!
Please support the following sites too; flashx.tv - streamin.to
Non-adult samples: http://www.flashx.tv/e1ojx8ly5d08.html - http://streamin.to/avrajusgufp5
Thanks!
bye

The two sites contains lots of copyright-violation videos (see [1][2]), so youtube-dl cannot support it.
[1] https://www.google.com/transparencyreport/removals/copyright/domains/flashx.tv/
[2] https://www.google.com/transparencyreport/removals/copyright/domains/streamin.to/


python37Packages.pgspecial: 1.11.3 -> 1.11.5

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.7-pgspecial/versions.
meta.description for python37Packages.pgspecial is: '"Meta-commands handler for Postgres Database"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.11.5 with grep in /nix/store/dwn17ffjsn3bgcf4hvgzkh1wl8g2simn-python3.7-pgspecial-1.11.5

directory tree listing: https://gist.github.com/0d65487392e607ee231f35a9ec343271

du listing: https://gist.github.com/90cd29e1c183abb6a59951e2394a1acb

Rebuild report (if merged into master) (click to expand)

12 total rebuild path(s)
3 package rebuild(s)
3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
3 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
pgcli
python27Packages.pgspecial
python37Packages.pgspecial

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dwn17ffjsn3bgcf4hvgzkh1wl8g2simn-python3.7-pgspecial-1.11.5 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python37Packages.pgspecial https://github.com/r-ryantm/nixpkgs/archive/b4490e057a1f817f63a9e8a17faf502b9108e28b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dwn17ffjsn3bgcf4hvgzkh1wl8g2simn-python3.7-pgspecial-1.11.5
ls -la /nix/store/dwn17ffjsn3bgcf4hvgzkh1wl8g2simn-python3.7-pgspecial-1.11.5/bin

@GrahamcOfBorg build pgcli python27Packages.pgspecial

Changelog: https://github.com/dbcli/pgspecial/blob/master/changelog.rst


Replace Normal distribution with Normal with lower bound 0.

As per Nelson (2013), the examination activity uses a Normal distribution with mean 16.   During experimentation this mean may be lowered. In some cases a negative value may be sampled.   The normal distribution should be replaced with a normal distribution with a lower truncation at zero.
Reference of distributions used is here: https://pythonhealthdatascience.github.io/stars-simpy-example-docs/content/03_stress/03_data.html

Note: that sim-tools implements a normal distribution that can resample if sample  < 0.    All dists could be replaced with sim-tool dependency.

Fixed in version 2.0.0


Doesn't take AFK players into sleep required count anymore

@ifvictr thoughts on this based on the previous converstation?

when i first added this, i kinda wanted to discourage afk servers, where everyone just hops on to afk instead of actually playing

looks good to me.
i think this is beyond the scope of the pr but this may introduce a situation in which one person sleeps and the other people on the server (who are not really afk) type /afk and the server sleeps.

I agree with @ifvictr to an extent, because while we don't want to make the server an AFK server, it also severely inconveniences active players when they're trying to skip the night.

severely inconveniences active players when they're trying to skip the night.

it definitely does inconvenience people

Another thing to Nick's point: people already leave the game to speed up the night; why not make it easier to do that with the /afk?


Add configurable event storage

Objective

Fix #2071
Adoption of #2073

Solution

Add an associated type on Event for the storage type to use
Add a derive macro for Event that sets that associated type

Changelog

Added the ability to let events be stored in a SmallVec
Removed the blanket impl for Event

Migration Guide

Add #[derive(Event)] to all types used as an Event. Third-party types used as events should be wrapped in a newtype.

Thinking a bit harder on this, I want us to have quantifiable metrics via #7731 for this. The extra branch on the configuration (if we can't eliminate it) is a constant cost regardless of whether we use smallvec or not. If the memory saving benefits are more than worth the CPU cost, I'd say we should still merge.


gnark/std needs some love

gnark/std started as ad-hoc proof of concepts to validate gnark design choices and use cases like rollups.
Needs a re-visit to ensure the packages under gnark/std:

are rock solid
have coherent APIs names and patterns
are well documented

Hi, please see #103

Comment; gnark/std is tested using Groth16 on some curves only.
Need to use backend.Implemented() and  ecc.Implemented() to ensure good test coverage across backends en curves.


[ML-11959]  Create docs

Create docs by sphinx.

We may want to remove references to MLR 5.0 in the docs since it's outdated.


Padding of a hollow button should be corrected by the border-width

Two buttons next to each other won't have the same height if one of them is hollow.
Hollow button receives a 1px border, but because the padding is not corrected by the border's width the button is two pixels higher than solid button.

We've seen this - though it's a tough one unless you add a border to the regular button. Because border-box puts the border on the outside this happens.
Can you think of a better way to do it?

@rafibomb I was thinking you could adjust the padding to account for the 1 px border, however, this is a bit complicated by how foundation uses the button padding
$button-padding: 0.85em 1em !default;

%button {
   padding: $button-padding;
   ...
}

The $button-padding variable allows css shorthand format to be used, thus the value must be parsed to figure out exactly what padding the user has configured for each side.  I found an example of how css shorthand can be parsed in SASS: https://gist.github.com/pixelwhip/8428447
Once the individual padding values are known for each side, the calc() method can be used to adjust the padding by 1px.
@mixin button-style(...) {
  @if $style == hollow {
    border: 1px solid $background;
    padding-top: calc(#{$button-padding-top} - 1px);
    padding-right: calc(#{$button-padding-right} - 1px);
    padding-bottom: calc(#{$button-padding-bottom} - 1px);
    padding-left: calc(#{$button-padding-left} - 1px);
    ...
}

Perhaps I should have just scrolled a bit lower in the file before writing my comment.  Seems there already exists a method for getting the value for a specific side get-side($padding, right)

@MiguelMike @rafibomb fixed!


Bump Kubernetes version to v1.4.6+coreos.0

resolves #57

Current coverage is 54.72% (diff: 100%)

Merging #74 into master will not change coverage

@@             master        #74   diff @@
==========================================
  Files             4          4
  Lines          1038       1038
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            568        568
  Misses          388        388
  Partials         82         82

Powered by Codecov. Last update e1df46d...61d3891


Update Travis CI job(s) to include vcsim and govc Docker builds

As govmomi progresses, we should think about updating travis jobs to keep the images and deployments in sync with govmomi, e.g. when new (event) types are added that we can support.
Note: This issue might be resolved when govmomi automatically builds and ships Docker images.

https://github.com/vmware/govmomi/pull/1375


[release-1.16] [TF] add retry to default service account patch command

This is an automated cherry-pick of #43894

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-multicluster

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-multicluster

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-multicluster

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-multicluster

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-multicluster

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-multicluster

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

integ-pilot_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

integ-pilot_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

integ-pilot_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

integ-pilot_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote-mc

integ-telemetry_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

integ-pilot_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote-mc

integ-telemetry_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry

integ-security_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

integ-pilot_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote-mc

integ-telemetry_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry

integ-security_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-security

integ-telemetry-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

integ-pilot_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote-mc

integ-telemetry_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry

integ-security_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-security

integ-telemetry-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry-istiodremote

integ-ds_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-ds

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

integ-pilot_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote-mc

integ-telemetry_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry

integ-security_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-security

integ-telemetry-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry-istiodremote

integ-ds_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-ds

integ-ipv6_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-ipv6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

integ-pilot_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote-mc

integ-telemetry_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry

integ-security_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-security

integ-telemetry-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry-istiodremote

integ-ds_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-ds

integ-ipv6_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-ipv6

integ-telemetry-mc_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote

integ-distroless_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-distroless

integ-cni_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-cni

integ-pilot_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot

integ-pilot-multicluster_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-pilot-istiodremote-mc

integ-telemetry_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry

integ-security_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-security

integ-telemetry-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry-istiodremote

integ-ds_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-ds

integ-ipv6_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-ipv6

integ-telemetry-mc_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-telemetry-mc

integ-security-istiodremote_istio_release-1.16
9e0f8b691915e070cd78f93c3f4116c3a12b1e48
link
unknown
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Surface Allowance issue number and name

Aggregating some feedback from KZ on this issue.
Right now, inside the allocator's pages, the Allowance ID numbers listed don't mean much (e.g: 7458).
It's better to know which application is each allocation and just have the link to github. For example, (#3)/name (Mongo2store - common crawl). And even Github ID (e.g. amughal).

Heya @willscot!
Do you know if GH issues for Datacap Applications like https://github.com/cryptowhizzard/Fil-A-2/issues/1 or https://github.com/Destore2023/MetaPathways-Bookkeeping/issues/3 are being indexed by anyone?
Would be great to ingest that information and surface it in a couple of places and was wondering if anyone is doing it to avoid reinventing the wheel!

https://allocator.tech/

Thanks @clriesco! Do you know if there is an offifical API for Allocator.tech?
I see it's doing GET requests to https://fp-core-prod.dp04sa0tdc6pk.us-east-1.cs.amazonlightsail.com and I can replicate those but wanted to check before in case there is a better endpoint!

Please, just use github issues. The application is not open for api requests
El El mié, 1 may 2024 a las 10:20, David Gasquez @.***>
escribió:

Thanks @clriesco https://github.com/clriesco! Do you know if there is
an offifical API for Allocator.tech?
I see it's doing GET requests to
https://fp-core-prod.dp04sa0tdc6pk.us-east-1.cs.amazonlightsail.com and I
can replicate those but wanted to check before in case there is a better
endpoint!
—
Reply to this email directly, view it on GitHub
https://github.com/davidgasquez/filecoin-data-portal/issues/31#issuecomment-2088141146,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AILR7H6EPX47EWAG7QCBBPDZACQUNAVCNFSM6AAAAABGWVY3Y2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBYGE2DCMJUGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Chatted with Charly and got the :+1: to use the internal API (/applications, /allocators).

We don't need to rely on the previous API endpoints. We can go straight to the repositories and ingest the standarized JSONs (e.g: f15lqbrrx6cmkg5o56awnysvqodoalddzpnkildfq application).


Restapi Api Key Authorization

This PR adds authorization for the REST API.
I used this module for this.
Now every request to the REST API has to have an Authorization header in the format
Authorization: Api-Key <API_KEY>

This can be disabled by setting DEBUG=True in the backend/backend/.env file.
Unfortunately the browsable API won't work with this.
API KEYs can be added or removed via the CLI.
The key itself is not stored in the database, just the hash value.
I made changes and added the documentation for the CLI, the frontend and the restapi.
I changed the frontend to use an API KEY if it is set in a new .env file in the frontend/ folder like this:
VITE_BACKEND_API_KEY = '<API_KEY>'

This resolves #136
How to test:
To not use any API KEYs start the backend with DEBUG=True and confirm that everything works like before.
To use API KEYs set DEBUG=False in the .env file for the backend, add an API KEY with the CLI, add it to the .env file for the frontend and test the frontend.
To manually test the REST API you can use curl like this:
curl -H "Authorization: Api-Key <API_KEY>" localhost:8000/restapi/missions/

to make other requests than GET you can use for example the option -X DELETE to make a DELETE request.

to fix the test of the frontend run with npm test. I had to mock the call of import.meta.env which is used to access environmental variables (and variables in .env).
To do this I installed the packet ts-jest-mock-import-meta and added configuration in jest.config.cjs.

Was an error by me, fixed it.

You also need to run
python manage.py migrate


update createImageSqs.py to create pairs with 4 dates preceding image date

Currently script creates interferogram pair jobs using the 4 latest images excluding the image specified by the argument. This means that the script cannot be used to queue old image jobs because it will create pairs using the most recent images rather than the 4 image dates preceding the image date under consideration.

Done


sentinel-3 product_types update

for sobloo:
some sentinel-3 product_types existed but have been removed in v2.0b1 as they were not valid any more. New ones are available and should be added to provider conf

for all providers:
choose a product type pattern between official OL_2_LFR___ or current EODAG mode S3_OLCI_L2LFR (SENTINEL3 OLCI Level-2 Land Full Resolution)

most Sentinel-3 products are now available and configured on several providers


[Refactor] overrideWithUserProperties feature

It is possible to launch TESTAR through CLI and configure the settings by adding pairs of setting=value.
Example: testar ShowVisualSettingsDialogOnStartup=false
An old implementation in TESTAR allows configuring a few settings as JVM arguments.
Example: -DShowVisualSettingsDialogOnStartup=false testar
https://github.com/TESTARtool/TESTAR_dev/blob/6007a958999dca3ec724771b6157c119786c691c/testar/src/org/testar/monkey/Main.java#L662
Not all settings are implemented in this overrideWithUserProperties method, and it seems they need to be maintained manually.

Extend the overrideWithUserProperties method to include all settings
Delete this old overrideWithUserProperties implementation

This old implementation was finally removed in #375
As the first comment says: It is possible to launch TESTAR through CLI and configure the settings by adding pairs of setting=value


Add "Publish a Raster Dataset" section to Exercise 5 Maps

@krishnaglodha We miss a "Publish a raster dataset" section `here,  that shows how to publish raster data using the MapServer MapScript core backend.
More information can be found here: https://docs.pygeoapi.io/en/latest/data-publishing/ogcapi-maps.html#providers

I was able to make setup in pygeoapi to spit data out as MAP format, are you asking me to use mapserver mapscript as client to visualise it ?

PS : This is the config I have used
providers:
            - type: map
              name: MapScript
              data: /data/airport/airport.shp
              options:
                  type: MS_LAYER_POINT
                  layer: airport
                  style: /data/airp.sld
              format:
                  name: png
                  mimetype: image/png

@krishnaglodha No, this is exactly what I meant :-) To use MapScript as a backend provider.
Can you add this exercise to a section "MapScript" inside the "pygeoapi section" here?

I think this will also get resolved in https://github.com/geopython/diving-into-pygeoapi/pull/118


Cannot create issue with title and description

I don't seem to be able to create an issue with a title and a description. All my attempts simply resulted in an issue that has a title but no description. This might be related to #677
➜  m2 git:(master) ✗ hub --version
git version 2.19.1
hub version 2.5.1

(The changelog for 2.6 doesn't indicate any title/description/newline related fixes)
➜  m2 git:(master) ✗ env | grep SHELL=
SHELL=/bin/zsh
➜  m2 git:(master) ✗ echo "Foo\nBar"
Foo
Bar
➜  m2 git:(master) ✗ hub issue create -m "Foo\nBar"

Results in issue with title: "Foo\nBar"
➜  m2 git:(master) ✗ bash
$ echo "Foo"$'\n'"Bar"
Foo
Bar
$ hub issue create -m "Foo"$'\n'"Bar"

Results in issue with title: "Foo Bar"
I would expect in both cases that the issue would have the title Foo and Bar as description.

Hello thank you for reporting. I'm afraid you may have stumbled on misleading documentation.
This behavior is as expected, but the documenation says that only the "first line" is the title. That's not true: the entire first block (or paragraph) of text is taken as a title until a blank line (\n\n) is encountered. This is for compatibility with git commit -m.
I'm fixing the documentation as we speak. You can also use this (at least in bash, not sure about zsh):
hub issue create -F - <<<"hello my
very long title

this is issue description"


Fixed Issue #2

Resolves Issue #2
Change changelog

Good job Renz, please work on the next assigned issue


unify all of RedPRL under sexpr notation (?)

Having a uniform notation for all of RedPRL's sublanguages would be really nice; RedPRL-style sexprs seem a natural choice, because they are easy to parse and easy to print, and (excitingly) it is well-known how to provide excellent editor support for sexprs (e.g. paredit, etc.). Furthermore, it is probably one of the only notations which can be completely accurately highlighted in most editors without compiler-support.
There's a few questions that would need to be addressed:

How to differentiated between raw program terms and analogous tactics? For instance, right now we have program terms like (lam [x] M) and tactic expression lam x. t. One way to deal with the issue is to use different names for the operator, but this may get out of hand.

How to avoid tactic scripts getting too deep w/ parentheses; sometimes it can be stressful to edit a very deep point in a large sexpr... Sequential scripts that involve fresh x -> ... may become fairly gnarly, for instance. Perhaps this doesn't matter.

I'm sure there are other questions too. I wonder if @favonia has any thoughts about this.
I'm still not completely certain that we should do this; for instance, when we work on the new metalanguage (if that ever gets done), will we adopt a traditional ML-style notation, or will we use sexprs there?

For the first one, how about separately having (intro [x y z] ...) as the tactic?

@favonia That's not too  bad, I'm open to it.

How to differentiated between raw program terms and analogous tactics? For instance, right now we have program terms like (lam [x] M) and tactic expression lam x. t. One way to deal with the issue is to use different names for the operator, but this may get out of hand.

Couldn't you use some sort of special quasiquotation mechanism for this?

@freebroccolo

Couldn't you use some sort of special quasiquotation mechanism for this?

The idea makes sense, but there is an asymmetry between between those tactic-terms and the real terms—the former follow essentially the syntax of sequent calculus, whereas the latter are more like natural deduction. So, for introduction forms they basically coincide, but elimination forms tend to differ.

 It's a little hard to read, but not too horrible.

@jonsterling I think it's not too bad. I wonder how (fresh ...) should be written (which should apply to the cases in (match) as well).

@favonia I'm not sure about the fresh thing either. What I did in the example notation was that I made seq a binding form in its n+1th arguments (hence the [x y]), but it's a little ugly.
As for match, I think it is orthogonal, because match is its own binding for and doesn't use that fresh machinery.

What I meant is that
(match goal [ a | (true %a) => (blah %a)])))
can be thought as, in some sense,
(match goal [a] (true a) [a] (blah a))
and you can see that it has the same issue of fresh which talks about binding structures across subexpressions.

@favonia Ah, I'm still not sure I follow what you mean about binding across subexpressions; fresh x -> t1; t2 could be written (fresh t1 [x] t2), binding only in the second argument. The actual structure of match is that it takes a bunch of "clause" arguments, binding a bunch of pattern variables in each of them; a clause is formed by a pattern and a tactic, and the pattern variables is bound in the whole clause.
I'm not certain about the best concrete notation for match clauses; ideally we wouldn't even mention the names of the pattern variables, and would actually regard them in the notation as being bound "by" the pattern itself. I'm just not sure how to make that work.

@jonsterling Well, fresh x -> t1; t2 can not be understood as (fresh t1 [x] t2) because, at least in the current implementation, x could potentially be used within t1. Does the new scope checker rule this out?

@favonia No, x cannot be used in t1; it is a syntax error to write, for instance, fresh x -> use x; .... The operator in the abstract syntax that fresh corresponds to is actually MTAC_SEQ.

Actually, now thinking about it, given the number of people who have learned JavaScript (?!), perhaps (lam [x] blah) for both tactics and expressions are not so bad in practice after all?

Some food for inspiration: https://common-lisp.net/project/cl-monad-macros/monad-macros.htm


Excessive logging

I'm sees 1000's of these messages in the logs using 1.3.0-8.
W/Router: Cannot add Content-Type header because getResHeader() returned null

I think debugging log message remains with incorrect Log level. I will fix by 1.3.0 release. Thank you.

This is a regression from the incorrect if check.
https://github.com/couchbase/couchbase-lite-java-core/commit/b8d11b40083ce6ec3d717fbfd4669e1cf304ed82#diff-34d6c6091cbd2b4d22c6e2c5a274f76cR741

I will fix the issue today.


Convert to .conda as part of the pip install?

Wondering if there's a net positive in using whl2conda for this. The rough logic would be to:

Run the dependency analysis to get the conda and PyPI packages as we are doing now.
Instead of running pip install --no-deps ... directly, convert to .conda beforehand with whl2conda and then install that with conda --no-deps.
We would cache these converted wheels in the pkgs cache as usual.

Benefits:

More integration in the conda environment (proper conda-meta/ files, clobbering detection, taken into account in the solves, etc).
A mature project that has gone through the usual edge cases already so it should be more robust than this early attempt

Cons:

One more dependency
Delegated complexity to a 3rd party
We could be introducing problems in the solves

I am also interested in this idea n.b. https://github.com/conda/grayskull/pull/541 and https://github.com/conda/conda-build/pull/5380

I guess we would only cache the stuff that comes from PyPI, not the editable installs or dynamic references from Github.

Can conda install a .conda without leaving it in pkgs/cache?

I don't think there's an option for that. We would have to inject a temporary location for the pkgs_dirs setting and maybe discard it afterwards?

What about creating an entry in the environment's conda-meta directory for each pip installed package? The information for the file can likely be derived from the METADATA file in the dist-info directory of the pip installed package with a bit of conversion.
The benefit of this approach is that conda would then be able to manage these packages directly.


confusion about versions, coming changes, so on

I've searched for a while and am still very confused, sorry if this has been answered well somewhere.
The code in the README on the master branch doesn't seem to work if you use npm install redux-simple-router --save. There are currently two branches, master and another-cycles-idea, and it's not clear to me which one is the more updated version and which API I should be using.
For example, I'm currently using dispatch(pushPath('/url'))  but should I be using dispatch(routeActions.push('/foo')) instead as in the readme? Various different boilerplates I've found that use redux-simple-router also use different versions and it's very confusing.
Furthermore, my understanding is that redux-simple-router is the 'officially' recommended one to use with redux, as it's been moved to the rackt repo on github, but the Real World example on http://rackt.org/redux/docs/introduction/Examples.html uses redux-router.
Can someone please clarify what people who want redux-simple-router today should use?

You just hit the bleeding edge. redux-simple-router in its current form has been released yesterday in version 2.0.1 and today again as 2.0.2. The transition to rackt has been made within the last month.
Before that redux-router was the only routing solution for redux (at least the only one I know of). Unfortunately redux-router is not so actively maintained. You can find the relevant discussion here.
So you are confrontend with a transition phase, which should explain why many examples still refer to redux-router. You should find up-to-date examples in the readme of this project. See here

I have downloaded 2.0.3 version, navigated to examples/basic and executed npm install and npm start but it failed with compilation error
Module build failed: SyntaxError: <path>/src/index.js: Unexpected token (41:11)

After I removed "extra lines" from webpack config, webpack started but browser complained about missing function listenForReplays.
What can be wrong?

I just nuked that other branch. It was something James was exploring, but we went with another option for 2.0.
The current docs line up with the current version. If they're not matching up, then you have the wrong version installed or cached or something.
The redux example needs to be updated. Since 2.0 is out, now is a good time to do that. A PR would be really appreciated over there! :smile:


weekday names incorrectly centered when using week numbers

weekday names in the table head (mon, tue ...) are incorrectly centred above their columns when using week numbers. should be easy to patch.

Hello,
Looks okay on the demo page.
Show me your screenshot / demo where it isn't centered properly.
Thank you

le voila

MS Edge btw

With flex updates, should be fixed in the latest version.
Feel free to reopen if the problem persists


Update notebooks READMEs

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Rails 5 deprecation warning

DEPRECATION WARNING: otp_secret is not an attribute known to Active Record. This behavior is deprecated and will be removed in the next version of Rails. If you'd like otp_secret to be managed by Active Record, add `attribute :otp_secret to your class....

I get this as well as the following error:
[13] pry(main)> u.otp_secret = User.generate_otp_secret
DEPRECATION WARNING: otp_secret is not an attribute known to Active Record. This behavior is deprecated and will be removed in the next version of Rails. If you'd like otp_secret to be managed by Active Record, add attribute :otp_secret to your class. (called from __pry__ at (pry):13) ArgumentError: must specify a key from ruby-2.4.2@gems/encryptor-3.0.0/lib/encryptor.rb:56:in crypt'

Is it possible that a future release of devise-two-factor will handle this itself?

Looks like no one wants to fix it :(
ArgumentError in RailsAdmin::MainController#edit
key must be 32 bytes

I think this is an issue with how the attr_encrypted gem sets up the virtual attribute, and that there's a fix for this in the master branch: https://github.com/attr-encrypted/attr_encrypted/commit/00da7c96beebff5ec4f2b3c9361c92e84afafe7f
I added the master branch to my Gemfile and do not see those deprecation warnings anymore. Other deprecation warnings pop up from attr_encrypted, though.
Anyway: I don't think the problem is devise-two-factor itself, and if we are to get this fixed the target should be the attr_encrypted gem.

A new version of the attr_encrypted gem (3.1.0) was released 19 days ago. Upgrading got rid of this warning for me.

@mediafinger is this issue can be closed with the #139 ?
remind: https://github.com/tinfoil/devise-two-factor/pull/139#issuecomment-517281287

The requested attr_encrypted version is possible to pin to within the current gemspec requirements, so you should be able to use that without any devise-two-factor updates.


CMake Error during catkin build

Description:
Command:
cd kimera_ws
source devel/setup.bash
catkin build

Console output:

Starting  >>> mesh_rviz_plugins
Starting  >>> opencv3_catkin
Starting  >>> opengv_catkin
Starting  >>> pose_graph_tools
Finished  <<< cmake_external_project_catkin                [ 0.8 seconds ]
Finished  <<< disparity_image_proc                         [ 2.8 seconds ]
Finished  <<< gflags_catkin                                [ 0.9 seconds ]
Finished  <<< opengv_catkin                                [ 1.3 seconds ]
Finished  <<< dbow2_catkin                                 [ 0.7 seconds ]
Finished  <<< pose_graph_tools                             [ 4.2 seconds ]
Finished  <<< kimera_rviz_markers                          [ 4.7 seconds ]
Finished  <<< image_undistort                              [ 8.3 seconds ]
Finished  <<< mesh_rviz_plugins                            [ 7.9 seconds ]
___________________________________________________________________________________________________________________________________________________________________________________________________________
Errors     << opencv3_catkin:make /home/srujan/kimera_ws/logs/opencv3_catkin/build.make.007.log
CMake Warning at /home/srujan/kimera_ws/build/opencv3_catkin/opencv3_contrib_src/modules/matlab/CMakeLists.txt:54 (message):
  A required dependency of the matlab module (Python Jinja2 package) was not
  found (installation command: "pip install jinja2").  Disabling Matlab
  bindings...

CMake Error at /usr/lib/x86_64-linux-gnu/cmake/gflags/gflags-targets.cmake:37 (message):
  Some (but not all) targets in this export set were already defined.

  Targets Defined: gflags_shared;gflags_nothreads_shared

  Targets not yet defined: gflags_static;gflags_nothreads_static

Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/gflags/gflags-config.cmake:10 (include)
  /usr/lib/cmake/Ceres/FindGflags.cmake:327 (find_package)
  /usr/lib/cmake/Ceres/CeresConfig.cmake:308 (find_package)
  /home/srujan/kimera_ws/build/opencv3_catkin/opencv3_contrib_src/modules/sfm/CMakeLists.txt:8 (find_package)

make[2]: *** [opencv3_src-prefix/src/opencv3_src-stamp/opencv3_src-configure] Error 1
make[1]: *** [CMakeFiles/opencv3_src.dir/all] Error 2
make: *** [all] Error 2
cd /home/srujan/kimera_ws/build/opencv3_catkin; catkin build --get-env opencv3_catkin | catkin env -si  /usr/bin/make --jobserver-fds=6,7 -j; cd -
...........................................................................................................................................................................................................
Failed     << opencv3_catkin:make                          [ Exited with code 2 ]
Failed    <<< opencv3_catkin                               [ 24.2 seconds ]
Abandoned <<< glog_catkin                                  [ Unrelated job failed ]
Abandoned <<< kimera_rpgo                                  [ Unrelated job failed ]
Abandoned <<< kimera_vio                                   [ Unrelated job failed ]
Abandoned <<< kimera_vio_ros                               [ Unrelated job failed ]
^C[build] Interrupted by user!
[build] Summary: 10 of 16 packages succeeded.
[build]   Ignored:   None.
[build]   Warnings:  None.
[build]   Abandoned: 5 packages were abandoned.
[build]   Failed:    1 packages failed.
[build] Runtime: 33.4 seconds total.

Additional files:
Please attach all the files needed to reproduce the error.
Please give also the following information:

SparkVio branch, tag or commit used : Don't know what this is
GTSAM version used: development branch
OpenGV version used: Latest avalable
OpenCV version used: type 3.2.0
Operating system and version : Ubuntu 18.04, ROS-melodic
Did you change the source code? (yes / no): No

Hi, I kind of fixed building gtsam and glog_catkin, but the opencv3_catkin still doesn't build. Here the catkin build output
Console Output
___________________________________________________________________________________________________________________________________________________________________________________________________________
Errors     << opencv3_catkin:make /home/srujan/kimera_ws/logs/opencv3_catkin/build.make.011.log
CMake Warning at /home/srujan/kimera_ws/build/opencv3_catkin/opencv3_contrib_src/modules/matlab/CMakeLists.txt:54 (message):
  A required dependency of the matlab module (Python Jinja2 package) was not
  found (installation command: "pip install jinja2").  Disabling Matlab
  bindings...

CMake Error at /usr/lib/x86_64-linux-gnu/cmake/gflags/gflags-targets.cmake:37 (message):
  Some (but not all) targets in this export set were already defined.

  Targets Defined: gflags_shared;gflags_nothreads_shared

  Targets not yet defined: gflags_static;gflags_nothreads_static

Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/gflags/gflags-config.cmake:10 (include)
  /usr/lib/cmake/Ceres/FindGflags.cmake:327 (find_package)
  /usr/lib/cmake/Ceres/CeresConfig.cmake:308 (find_package)
  /home/srujan/kimera_ws/build/opencv3_catkin/opencv3_contrib_src/modules/sfm/CMakeLists.txt:8 (find_package)

make[2]: *** [opencv3_src-prefix/src/opencv3_src-stamp/opencv3_src-configure] Error 1
make[1]: *** [CMakeFiles/opencv3_src.dir/all] Error 2
make: *** [all] Error 2
cd /home/srujan/kimera_ws/build/opencv3_catkin; catkin build --get-env opencv3_catkin | catkin env -si  /usr/bin/make --jobserver-fds=6,7 -j; cd -
...........................................................................................................................................................................................................
Failed     << opencv3_catkin:make                          [ Exited with code 2 ]
Failed    <<< opencv3_catkin                               [ 2.6 seconds ]
Abandoned <<< kimera_rpgo                                  [ Unrelated job failed ]
Abandoned <<< kimera_vio                                   [ Unrelated job failed ]
Abandoned <<< kimera_vio_ros                               [ Unrelated job failed ]
Finished  <<< gtsam                                        [ 4.1 seconds ]
Finished  <<< glog_catkin                                  [ 0.1 seconds ]
[build] Summary: 12 of 16 packages succeeded.
[build]   Ignored:   None.
[build]   Warnings:  None.
[build]   Abandoned: 3 packages were abandoned.
[build]   Failed:    1 packages failed.
[build] Runtime: 5.2 seconds total.

did you solve this problem? I have exactly same problem with you

did you solve this problem? I have exactly same problem with you

I found some solutions. If you uninstall glogs & gflags already installed by apt install command, it works
refer this: https://github.com/alibaba/euler/issues/158#issuecomment-585010067

did you solve this problem? I have exactly same problem with you

I found some solutions. If you uninstall glogs & gflags already installed by apt install command, it works
refer this: alibaba/euler#158 (comment)

hey, could you provide the exact lines you were using, please? having the same issue here.

Hey, in my case removing libgflags libraries helped:
sudo apt-get remove libgflags*
Found it in this discussion.


Three GAN papers

Generating Images with Perceptual Similarity Metrics based on Deep Networks. Maybe call it "DeePSiM" based on the paper?
DEEP MULTI-SCALE VIDEO PREDICTION BEYOND MEAN SQUARE ERROR. I can't come up with a proper abbreviation. : )
UNSUPERVISED LEARNING OF VISUAL STRUCTURE USING PREDICTIVE GENERATIVE NETWORKS. Maybe call it "PGN"?

Hello! Sorry for such late reply. Thanks for the paper links and suggestions. Currently, we've been adding papers that have named the GANs themselves rather than us naming them and adding to the list. So, we can wait for the original authors to name them :)
I'll close the issue until then and we can reopen when needed.


issue #199-Added side menu for react admin

Signed-off-by: Juan Feliz<EMAIL_ADDRESS>Contributes to #199
What did you do?
created the side menu for react admin.
Why did you do it?
it was needed to more easily route to pages
How have you tested it?
tested available routes.  I have not created test for it yet.
Were docs updated if needed?

[ ] No
[ ] Yes
[x] N/A

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new console logs
[ ] Fixes entire issue
[x] Partial fix for issue

I moved the BrowserRouter into the index.js so that the side menu can close when routing to a new location i hope thats alright

This looks great. I'd like to get this on main so we have the functionality, but first I'm hoping @ed-snodgrass has a chance to look in particular to make sure he agrees with the BrowserRouter rearranging. So we don't go back and forth on something like that (unless back and forth good iterations).  I don't see a problem with it.

@markstur I'm curious if we could simplify the side menu a bit and just have the links to the individual components? The table components themselves have the add/edit options.
Something like:

This looks great. I'd like to get this on main so we have the functionality, but first I'm hoping @ed-snodgrass has a chance to look in particular to make sure he agrees with the BrowserRouter rearranging. So we don't go back and forth on something like that (unless back and forth good iterations). I don't see a problem with it.

I'm not real sure that I have an opinion on the moving of the BrowserRouter. I'm good with pulling it in, even if you do want to keep the expanded menu items with the separate list and add/edit views.

@markstur I'm curious if we could simplify the side menu a bit and just have the links to the individual components? The table components themselves have the add/edit options.
Something like:

Yes. I had the same thought when looking at this PR. I probably only had them separate because that is how the thing evolved and then just kept it to show me it was complete (or maybe just because I already had expandable items in the menu?).  For usability, it sounds like you and I agree that it'd be better to just have the entities in the sidebar and go straight to the list view which already has the add button.

See Ed's comments.  For the simplified sidebar, that could be a separate PR if you want to address these things first. Up to you.


(feat) Build with CMAKE

This is the framework that helps transition to using CMAKE, however it ties-in to the build_ext. Initially, it wasn't lear CMake could be used for all, so I maintained both CMake and Makefile, thus the use of 2 classes.
Continuous Development is quite hard, it is not clear how for example this type of transition can be made incrementally, at some point, a jump from Makefile to CMake would need to be made, , this is a learning op for me if you have any comment/suggestion or else
Like, do you prefer that I try to make lots of PRs with each 'feat' I think of, or just let you review all the changes bundled in #141?

@ofek this should be cleaner than #141 I know why it is currently failin and fixed itg, but I am trying to resolve a related issue locally, I'll update when it looks good

I don't understand why setuptools>=61 is not available, #141 uses the same workflow

It's building Python 3.6 https://github.com/ofek/coincurve/actions/runs/8072129335/job/22053309535?pr=150#step:3:293

I don't want to admit that I can no longer read these tiny fonts ... sob. Though, why? setup.py still has the python_requires, #141 has it in its pyproject.toml. This PR is trying to deviate the least from master, do you undestand why this happens?

Appears to be building the correct versions now and failing with a different error

Right, I was too eager. I changed the location of the library because it was getting included in the wheel, but then that broke the shared build that needs the library included in the package

@ofek, we seem to be getting close. From a coincurve stand-point this is ready (since coincurve uses STATIC only).
The SHARED is a optional feature, that you could decide to switch to, so I want to have all wheels tested
For conda, we need the SHARED build to work without building the lib, I have yet to add the wheel test, it is a bit trickier since conda has to be installed on the docker host used by cibuildwheel (I was only able to test on windows so far). I will add it if all the SHARED pass

If you can find a way to extract the building & linking of the underlying library outside of setuptools/setup.py I would much prefer that if it's easier. Then we could switch to a different backend like Hatchling which I wrote and maintain.
Offering in case it happens to be easier to just run some commands straight up.

@ofek Thanks, actually all the builds look fine, both with static and shared library using cibuildwheels, thus native on windows and macos-14 (native ARM).
The last problem I seem to have is that somehow I cannot set the _has_system_lib to True, it is always False - I am forcing the build to fail in this case by giving a non-existing REF, otherwise it would pass and I would have to go see in the log if it was built instead of using the conda library
I was hoping to avoid all these debugging commits, but it is windows again so I have to push.

@ofek I don't know how Hatchling works, but build/install of libsecp256k1 is in fact done outside of setuptools since in this PR, we use cmake, and specify everything like install location.
Actually, we could add a CMakeList.txt to build _libsecp256k1 along with libsecp256k1 ... I did not think of that

@ofek Okay, I got it! ... little issue of path definitions ... too bad it took me so many useless commits to get there. One day maybe I will be a cleaner commit-er ... though not in the coming few centuries :,(

Keep thinking I am so close, no point closing the PR, that was 20 push ago

No luck?

It's progressing slowly since I am very bad at windows stuff, I am very close. I added a detection of shared vs static, since pkg-config does not tell as much, but it's tricky with windows, I actually kept the -2 in the conda lib, so it kept failing because of that
I finally got it cornered:
Running command Getting requirements to build wheel
    WARNING:root:DBG: C:/Miniconda/envs/test/Library\bin
    WARNING:root:DBG: secp256k1*.dll
    WARNING:root:[...', 'libsecp256k1-2.dll', ...]

Next push might be the one ... or not, little steps

OMG, I can't believe my eyes, all green (on my fork). Aftre digging down the rabbit hole and seeing no trace of Dorothy, it turned out that the primary issue was a apparent conflict between environments, namely the venv of cibuildwheel and the conda (needed for creating an installed libsecp256k1) ... dang, what a struggle


Add support for a border around some text

Hey there, I was wondering if there was a nice way to get a border for a highlight area in a StyleClassedTextArea. And if not I would like to make a feature request : D.
Something similar to what I'm looking for is the name change indicator in IntelliJ.

Specifically what I was looking to do is highlight locations in a text file based on user inputted row, column and lengths. For most of the use cases just having a colored background is fine. However, in the event that the user inputs a zero length location, there is nothing to highlight. With a border around a zero width selection, there would be feedback for the user.
In IntelliJ, it looks like this:

Thanks for the help!

I was wondering if there was a nice way to get a border for a highlight area in a StyleClassedTextArea. And if not I would like to make a feature request : D.

Currently, there is not a way to do that. Something similar was already asked in #337 (see the comments after the initial issue).

Aaah sorry about that, thanks for the info!

@NavalOrange This is possible with #455, but it still wouldn't be the best way to do it.

This is slightly outside the scope of this issue, but I've been wondering whether the entire style handling for rich text should be completely refactored. As pointed out here and originally here, there is a white (or same color as background) line that appears when two texts share the same background color but not the same style, resulting in 2+ background shapes being used for that background color.
By following the same approach we are currently using (each Text segment gets its own background shape), this break continues to occur now and will show up when the border text feature is implemented.
So, I'm wondering whether we could apply styles in a different ways. For example, style that apply only to the text (its size, its fill color, etc.) should be extracted from the style object and applied to that text. However, styles that apply to things behind/around the text (background color, underline, border around the text) should be handled separately by ParagraphText (or perhaps TextFlowExt).
In other words, only one background shape would be created for 4 text segments that all share the same background, even if they share different fill styles. However, this approach would need to factor in the possibility of a text segment spanning across multiple lines (in the case of line wrap being on). In other words, the code would need to:

Calculate the span of shared background-like styles
Split these spans into line-specific spans (if wrapText is true)
Create a background shape object for each line-specific span and set it behind a line's text.

The border text feature would need to add an additional step to the above. In situations where a border spans multiple lines, the first line should not have a closing right side:
// line 1
---------
| text     (no right bound)
---------
// line 2
---------
 text     (no right/left bound, only top/bottom)
---------
// line 3
---------
 text   | (no left bound)
---------


add ability for https://tdwg.org to work

Page(s) where issue occurs

https://tdwg.org

Issue description

only works if you use https://www.tdwg.org

I wasn't really paying attention, but in automating the certificate renewal I fixed this last week.


importError: No module named core

while running the Azure ML tutorial i am getting the following error. I am using 3.6 version as mentioned in the tutorial (notebooks.azure.com)
ImportErrorTraceback (most recent call last)
 in ()
----> 1 import  azureml.core
ImportError: No module named core

@vinod1976 Please help with the link of document on which above document feedback request is created.
Under this repository we want to make sure any issue is linked to a doc so we can help others that may be having the same issue.

https://docs.microsoft.com/en-us/learn/modules/intro-to-azure-machine-learning-service/6-train-model

@AshokPeddakotla-MSFT  https://docs.microsoft.com/en-us/learn/modules/intro-to-azure-machine-learning-service/6-train-model

@vinod1976 Thanks for the link, The link seems to be from the Microsoft learn site and any issues related to this course can be submitted to the team using the reporting an issue link at the bottom of that page.

We would recommend to raise an issue directly from learn site for faster responses in the future.
This GIT forum is used for issues related to documentation of Azure services.
For the issue you are facing it looks like the SDK is not installed in your python environment using bash. You can install it from the notebook shell before proceeding further using this command.
# Install the base SDK
!pip install azureml-sdk[notebooks]

@vinod1976 As suggested, If the above suggestions doesn't help, you can report this by following the steps mentioned in the doc.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Add branch for SurfaceSteps

In the Mu2e Offline we now have SurfaceSteps, which aggreage information from StepPointMCs at specific surfaces: virtual detectors in the detector region, the inner proton absorber, and the stopping target disks. A branch for these should be added to the ntuple and can replace the demmcvd, demmc_ssi_protonabsorber etc. branches.
This would be a good first issue for someone first looking at the art module.

Implemented in #197


git rename lower-cased folders

https://stackoverflow.com/questions/13201906/issue-with-renaming-a-directory-in-git-to-lowercase-while-ignorelowercase-true

I think this is done where needed.


Seed maps and heroes

This adds Rails seeds so that we have Overwatch's maps and heroes loaded into the database for developing with. This is based on implement-data-model #5.
Here's the output of running bin/rake db:seed:
Creating support heroes: Mercy, Zenyatta, Ana, Lúcio, and Symmetra
Creating tank heroes: D.Va, Winston, Reinhardt, Orisa, Roadhog, and Zarya
Creating offense heroes: McCree, Pharah, Genji, Tracer, Sombra, Soldier: 76, and Reaper
Creating defense heroes: Hanzo, Widowmaker, Torbjörn, Bastion, Mei, and Junkrat
Creating assault maps: Hanamura, Temple of Anubis, and Volskaya Industries
Creating escort maps: Dorado, Route 66, and Watchpoint: Gibraltar
Creating hybrid maps: Eichenwalde, Hollywood, King's Row, and Numbani
Creating control maps: Ilios, Lijiang Tower, Nepal, and Oasis
Creating arcade maps: Ecopoint: Antarctica
Creating segments for map Hanamura: Attacking: First Point, Attacking: Second Point, Defending: First Point, and Defending: Second Point
Creating segments for map Temple of Anubis: Attacking: First Point, Attacking: Second Point, Defending: First Point, and Defending: Second Point
Creating segments for map Volskaya Industries: Attacking: First Point, Attacking: Second Point, Defending: First Point, and Defending: Second Point
Creating segments for map Ilios: Well, Ruins, and Lighthouse
Creating segments for map Lijiang Tower: Night Market, Control Center, and Garden
Creating segments for map Nepal: Village, Shrine, and Sanctum
Creating segments for map Oasis: City Center, Gardens, and University
Creating segments for map Hollywood: Attacking: Capture Point 1, Attacking: Payload 1, Attacking: Payload 2, Defending: Capture Point 1, Defending: Payload 1, and Defending: Payload 2
Creating segments for map Dorado: Attacking: Payload 1, Attacking: Payload 2, Attacking: Payload 3, Defending: Payload 1, Defending: Payload 2, and Defending: Payload 3
Creating segments for map King's Row: Attacking: Capture Point 1, Attacking: Payload 1, Attacking: Payload 2, Defending: Capture Point 1, Defending: Payload 1, and Defending: Payload 2
Creating segments for map Numbani: Attacking: Capture Point 1, Attacking: Payload 1, Attacking: Payload 2, Defending: Capture Point 1, Defending: Payload 1, and Defending: Payload 2
Creating segments for map Route 66: Attacking: Payload 1, Attacking: Payload 2, Attacking: Payload 3, Defending: Payload 1, Defending: Payload 2, and Defending: Payload 3
Creating segments for map Watchpoint: Gibraltar: Attacking: Payload 1, Attacking: Payload 2, Attacking: Payload 3, Defending: Payload 1, Defending: Payload 2, and Defending: Payload 3
Creating segments for map Eichenwalde: Attacking: Capture Point 1, Attacking: Payload 1, Attacking: Payload 2, Defending: Capture Point 1, Defending: Payload 1, and Defending: Payload 2
Creating segments for map Ecopoint: Antarctica: Attack

/cc @RobThePM for input on more map segments to add

sorry, i saw this late. my only super nit picky suggestion would be to add the colon (:) in soldier 76's name so that it's soldier: 76, since we do it for the map names. unless that somehow messes with the code.

Colon added! I also fleshed out the rest of the map segments.

I forgot to include Eichenwalde, thanks for remembering!
(my Google sheet was leveraged from Season 1 and 2, when Eichenwalde didn't exist)

Awesome! 🎉


Beit why no k bias in attention?

The k bias is always zero in code. Is there any reason for this?  This is different from the normal implement.
https://github.com/microsoft/unilm/blob/421cffe163e474189c410ee06dad48dbfdcbc135/beit/modeling_finetune.py#L124
In my test.  when finetune, k bias has little affect on performance.  But I do not have a test on pretrain.

Both (i.e., with or without key.bias) are equivalent in terms of calculation results. They are canceled by the softmax function.
Softmax(q,k) = exp(q.weight * key.weight + q.bias * key.weight + q.weight * key.bias + q.bias * key.bias) / Z
Because the query is the same over all the keys, so the term (q.weight * key.bias + q.bias * key.bias) remains the same across all the keys, which in turn can be cancelled without affecting the softmax results.
exp(a)/(exp(a)+ exp(b)) == exp(a+C)/(exp(a+C)+ exp(b+C))


math mode symbol fallback

simply using the name of the symbol to output the symbol is very neat feature, but I think the forced space to imply multiplication is quite uncomfortable for me at least, while many times I found my self trying to write two indices only to get a undefined variable error,
that is sane expression $a_(ij)$ will produce an error,
however I think if we can fallback to normal symbol output for single char if the symbol or function is not found, it would solve the problem beautifully.

I think that would make it very hard to catch typos where you misspell some intended function (think foral instead of forall, etc.) and get a random product of variables instead of an error.

I belive most people will check their pdf output, especially with the incremental compilation of typst, this random product will be spotted very easily,  in my experience, I notice something went wrong only when I didn't see the expected output result of pdf, not because I see typst -w file.typ  background task gives an error.

If you insist: #let ij = $i j$
I do believe we should make the typographically-bad option difficult by default. I've for countless number of times seen people typing Pr instead of \Pr, or gcd instead of \gcd, or log instead of \log in LaTeX.

That would make it impossible to make backwards-compatible symbol additions.

could there be a switch to turn this options on? it would really be handy and maintain backwards-compatibility.

If you insist: #let ij = $i j$

however one might use ik, jk, mc^2 and the list goes on...

I do believe we should make the typographically-bad option difficult by default. I've for countless number of times seen people typing Pr instead of \Pr, or gcd instead of \gcd, or log instead of \log in LaTeX.

yes I agree with this, but make the a switch to toggle different behavior and keep it off by default should reduce errors above and make writing typst document more efficient.

If you try hard enough you can always use a custom build of a fork of Typst.
Although maybe I would only agree to it if documents produced by this option will have a watermark like "Draft version" on it, then they would need to turn it off and manually fix the error later.


1.10 requires react 18.2 as a peerDependency.

What platform is your computer?
MacOS
How did you attempt to install or upgrade?
$ npm install

What do you see instead?
npm WARN ERESOLVE overriding peer dependency
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@kubb/swagger-client/node_modules/@kubb/react-template
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@kubb/swagger-client
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@kubb/swagger-client
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@kubb/swagger-client
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/alfred/.npm/_logs/2023-10-10T09_29_55_379Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /Users/alfred/.npm/_logs/2023-10-10T09_29_55_379Z-debug-0.log

Additional information
I'm using react 17, no problem with kubb 1.9, but with 1.10 I'm getting an error that it conflicts with react 18 peerDependency.
I can use the --force or --legacy-peer-deps option, but this will also disable other peerDependency checks, so if possible, I would like kubb to not have react 18 as a peerDependency. Why does kubb use react 18 as a peerDependency? Is it possible to remove react 18 as a peerDependency?

@b6pzeusbc54tvhw5jgpyw8pwz2x6gs For an upcoming feature(@kubb/react-template) I started using React to make it possible to override the templates that are getting used to create the client/axios, React-Query, Vue-Query,.. files.
But indeed that should not be as part of a peerDependency.   Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142

However, the generate command throws an error.
> kubb generate --config kubb-configs/kubb.config.ts

✔ 💾 Config loaded(kubb-configs/kubb.config.ts)
✖ Something went wrong

  PluginError: Cannot read properties of undefined (reading 'isBatchingLegacy') (plugin: swagger-client, hook: buildStart)

  Plugins:      0 failed, 3 total
Generated:      41 files
     Time:      0.258s
   Output:      /Users/alfred/***/***/server/generated-api/***

Reinstall react to 18 and run it and it should work.
npm uninstall react
npm install react
kubb generate --config kubb-configs/kubb.config.ts

> kubb generate --config kubb-configs/kubb.config.ts

✔ 💾 Config loaded(kubb-configs/kubb.config.ts)
✔ 🚀 Build completed

  Plugins:      4 successful, 4 total
Generated:      91 files
     Time:      0.363s
   Output:      /Users/alfred/***/***/server/generated-api/***


val.replace is not a function

I tried testing my flutterwave integration with the test cards, and I keep getting this error
"We could not charge this card. Reason: val.replace is not a function".
I looked up solutions online, I've passed the amount as a string but this error still persists.

Hello Olusoladeboy,
Sincere apologies for the late response,
This is most likely due to the data you have passed to the meta property.
Please ensure that the data in the meta props, only contains basic data type, like string and numbers.
Please see sample below:
meta: {
customerName: 'Test Name',    //String, this is okay
items: ['test']   //Array, this wont work
}
Please let us know if this fixes the issue for you.


Fix SaveAsActivityTest

This test currently does not actually test anything. Probably forgotten since the early days. A complete rewrite is probably the best route.

Closing, tests in general should be rewritten.


[AutoPR cdn/resource-manager] add premium_chinaCdn to CDN sku

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5897

This PR has been merged into https://github.com/Azure/azure-sdk-for-java/pull/3281


Is it possible to have Maccy pop-up at the selected text area?

It's not possible due to App Sandbox limitations.


WireGuard Mode: Spoof ICMP echo replies

Some apps check network connectivity by sending ICMP pings. ICMP traffic is currently swallowed by mitmproxy_rs, which makes them believe that there is no network connectivity.
Correctly forwarding ICMP in both directions is tricky, so a cheap mitigation that probably covers the majority of use cases would be to simply fake ICMP echo replies somewhere around here.

Hey @mhils I am interested in issue, can you assign this to me?

@chiragbiradar: if you read up on how ICMP "pings" work, the description above should make sense.

@mhils is this issue intentionally left open? Looks like it's already resolved by https://github.com/mitmproxy/mitmproxy_rs/pull/28

Nope, thanks! :)


Parameters and Type Parameters Missing from TOC Pages for Delegates

API pages for delegates with parameters are missing Parameters and Type Parameters.
Example:
Compare the .NET Core API pages for Action<T1, T2> Delegate with the corresponding page on the .NET Framework Class Library
https://docs.microsoft.com/en-us/dotnet/core/api/system.action-2
https://msdn.microsoft.com/en-us/library/bb549311(v=vs.110).aspx
/cc @blackdwarf @chenkennt @pengbian

@chenkennt @superyyrrzz this is still an issue at docs.microsoft.com

This still repros. Opened internal bug to track this: 983076

This is resolved now.


In section Virtual members a miscopy error (wrong text of code)

In section Virtual members the second example is wrong - it fully repeat previous example from this section (i think it's a miscopy error).

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

ID: d1ebd197-8f01-b8d7-45d6-1a7afba572b4
Version Independent ID: 0790b314-a794-6ce3-15f0-37281faa00a6
Content: Polymorphism - C# Programming Guide
Content Source: docs/csharp/programming-guide/classes-and-structs/polymorphism.md
Product: dotnet-csharp
Technology: csharp-fundamentals
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for writing this @DSivtsov I've opened #18856 to address this.


S3:PutObject with no key is mis-interpreted as PutBucket

This is really minor, but if you do not set the key on a PutObject request, it is the same URI as a PutBucket request (bucketname.s3.amazonaws.com/)
The most likely result is a MalformedXML exception which may be difficult for some people to debug. Should the S3 model be modified to mark key as required on this operation?

Same thing would happen with GetObject if the key is empty (it would look like a ListBucket to AWS).
This happens because the URI,  the bucket and the key are simply concatenated without checking.
Maybe the SDK should fail with "invalid argument" if the key is empty.

I've added an issue to investigate this into our backlog.

https://github.com/aws/aws-sdk-cpp/commit/fad59fe4037d659b858c9dafe9022144130eccb1


Fix ES004 governor address

Fixes the governor address in the deploy scripts for ES004.

Yeah the issue was that the governor was different in the tests vs the deploy scripts - I think as a followup it might be good to define the target governor in the proposal itself to avoid this (maybe the gov token too?)