Could not load file or assembly System.Linq.Expressions <IP_ADDRESS>

I already published to file folder, completed path for referenced assemblies,
thanks for your time

Can you provide a sample project?

Hi @oqp
Can you try with the latest CI build of NSwag (v11)?
I worked on the assembly loader and for my projects it seems to work... but there are many edge cases/usage of old dlls/etc. which may fail in the assembly loader.
https://ci.appveyor.com/project/rsuter/nswag-25x6o/build/artifacts

<EMAIL_ADDRESS>Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Rico<EMAIL_ADDRESS>Sent: Sunday, June 4, 2017 9:14 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [NSwag/NSwag] Could not load file or assembly System.Linq.Expressions <IP_ADDRESS> (#762)
Hi @oqphttps://github.com/oqp
Can you try with the latest CI build of NSwag (v11)?
I worked on the assembly loader and for my projects it seems to work... but there are many edge cases/usage of old dlls/etc. which may fail in the assembly loader.
https://ci.appveyor.com/project/rsuter/nswag-25x6o/build/artifacts
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/NSwag/NSwag/issues/762#issuecomment-306042557, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANE8q9af1gBjsn1kTURomiOpZ-nv61fEks5sAru9gaJpZM4NX_oL.

?

I did what you said.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Rico Suter<EMAIL_ADDRESS>Sent: Monday, June 5, 2017 2:33:15 PM
To: NSwag/NSwag
Cc: oqp; Mention
Subject: Re: [NSwag/NSwag] Could not load file or assembly System.Linq.Expressions <IP_ADDRESS> (#762)
?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/NSwag/NSwag/issues/762#issuecomment-306280483, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANE8q19GXOcghPzF1Zeh5iHt8jKCoG5oks5sBFf7gaJpZM4NX_oL.

And what are your findings?

It shows the same error, that's why I sent you the capture.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Rico Suter<EMAIL_ADDRESS>Sent: Monday, June 5, 2017 2:51:22 PM
To: NSwag/NSwag
Cc: oqp; Mention
Subject: Re: [NSwag/NSwag] Could not load file or assembly System.Linq.Expressions <IP_ADDRESS> (#762)
And what are your findings?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/NSwag/NSwag/issues/762#issuecomment-306284932, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANE8qx9z6s6ut5wddmYh5eipWaYpYJ0Oks5sBFw6gaJpZM4NX_oL.

The image is missing. Can you provide a sample project? (Dlls)

https://github.com/NSwag/NSwag/commit/1348698596d6c066c052ad002923685665990ba1

Can you retry with the latest ci artifacts?


embeeded survey is not showing up in android

Embedded SurveySparrow component comes fine in iOS but on android, it is just plain white, and nothing loads.

@Saad-Bashar , Can you share more details about this along with the code and output with us?. So it will be easier for us to check it out and get back to you!

Here is the snippet which is working fine for iOS but on android nothing loads, I mean the survey does not show up.

@Saad-Bashar do you get any error in metro when loading in android ?

@Saad-Bashar can you add style props to the SurveySparrow component with the height and width that you want for example :
<SurveySparrow
styles={{
width: '100%',
height: 500,
}}
config={{
domain: 'socarmy.surveysparrow.com',
token: 'tt-446ec5',
surveyType: 'classic',
}}
onSurveyComplete={data => {
console.log('survey response from embed survey is', data);
}}
/>

No error :( I tried to set the styling as well but still the same.

Hey I just tried again with styles and its working! Thanks!


implement basic resource and first example

Coverage remained the same at 100.0% when pulling d7243d8a944b4caa6ae6bd87a4f606ec97b40214 on basic-resource into 0b9db7f93e84de89fb206d0f173fb91c9efca236 on master.

Coverage decreased (-100.0%) to 0.0% when pulling d3a6897d14623f24be154e1b290d12dc1a6eb86f on basic-resource into 0b9db7f93e84de89fb206d0f173fb91c9efca236 on master.

Coverage decreased (-100.0%) to 0.0% when pulling 14ec9e49cf247dc13089a41f1f5384f2a3befd06 on basic-resource into 0b9db7f93e84de89fb206d0f173fb91c9efca236 on master.

Coverage remained the same at 100.0% when pulling c39d36b5a37d6f44b226b502b04197b4eff12195 on basic-resource into 0b9db7f93e84de89fb206d0f173fb91c9efca236 on master.

Coverage remained the same at 100.0% when pulling 6144293cf04a559bf40e0a7e291439c9ed05f476 on basic-resource into 0b9db7f93e84de89fb206d0f173fb91c9efca236 on master.


Can we change the formatter to async function?

Question
Can we change the formatter to async function?
Description
I have a REST API that returns an image when I request with the url + (plus) file name and I want to display it in the image column in a table.
My Question on stackoverflow
codesandbox
https://codesandbox.io/embed/nifty-sinoussi-l08kk?fontsize=14&hidenavigation=1&theme=dark
Error

Error: Objects are not valid as a React child (found: [object Promise]). If you meant to render a collection of children, use an array instead.

I ask above because I have a case that asks I use await from the async function. I want to retrieve a Base64 decoded string for me to display as an image with the <img src = {Base64String} /> tag in a column in the table.
I have tried to use the async function in the formatter and it cannot, it always get an error like this:

Error: Objects are not valid as a React child (found: [object Promise]). If you meant to render a collection of children, use an array instead.

but I still get Base64 string that I want in the console and I began to think that it is not possible to place the async function in the formatter. I have tried to apply the formatExtraData, but in my opinion it does not suit my case. is there any alternative? if there is i will be very thankful ..
@AllenFang

HI @adamcanray I'm sorry I will not consider to implement this feature. For you case, you have to implement a custom component to display an image, like ImageURI component and render it when calling the formatter.  So in this custom component, you can do anything you like, for example: fetching the data and only render <img /> element when data is availabe.
That's why I reject your requirement. because this is all are able to control by you.
Please open another issue if you still have any question or any issues, thanks boss


FlightSQL example is broken

Describe the bug

FlightSQL example (arrow-flight/examples/flight_sql_server.rs) is broken. Running cargo test -p arrow-flight  --features=flight-sql-experimental --examples got compilation error:
error[E0433]: failed to resolve: use of undeclared crate or module `fs`
   --> arrow-flight/examples/flight_sql_server.rs:504:17
    |
504 |         let _ = fs::remove_file(path.clone());
    |                 ^^ use of undeclared crate or module `fs`

error[E0412]: cannot find type `FlightSqlServiceClient` in this scope
   --> arrow-flight/examples/flight_sql_server.rs:490:47
    |
490 |     async fn client_with_uds(path: String) -> FlightSqlServiceClient {
    |                                               ^^^^^^^^^^^^^^^^^^^^^^
    |
...

To Reproduce

Expected behavior

cargo test -p arrow-flight  --features=flight-sql-experimental --examples

   Compiling arrow-flight v29.0.0 (/arrow-rs/arrow-flight)
    Finished test [unoptimized + debuginfo] target(s) in 1.76s
     Running unittests examples/flight_sql_server.rs (target/debug/examples/flight_sql_server-609b62f910a8643f)

running 1 test
test tests::test_select_1 ... ok

Additional context

label_issue.py automatically added labels {'arrow-flight'} from #3387


Fixed pan move responder and added bounds for it

#Cannot close menu by pan gesture...
gif

fixed version

I know. it was fixed, but why we give ability to pan frontview in out of range(right bound for left menu...)?

Already fixed


Reactive components prototype

Objective

Initial prototype for reactivity in Bevy

Solution

A new ReactiveComponent type that automatically inserts and updates a component of type Output on the same entity whenever the source entity's component of type Input changes (as detected by change detection ticks)

Implementation issues

There's a single place where reactive components get updated (the Last schedule). Ideally it would be an immediate reaction like how observers work.
The update_reactive_components driver system loops over every single expression any time an expression changes. It would be ideal if we could track affected components, and only re-run expressions that would be affected. But for the initial prototype, performance isn't too important anyways.

Not implemented/tested

ReactiveComponents that can add/remove the component, instead of just modifying the value.
Chaining reactions
Expressions that depend on multiple components from an entity
Expressions that depend on multiple entities
Expressions that depend on resources
Expressions that depend on queries or other complicated sources of data
Reactive entity tree structures (e.g. a reactive version of WithChildren/WithChild, using the Name component as a key)

I think template + diffing approaches are the better move here. Change detection is too difficult to get working well I feel.


(HAL-16) MOVETH SIGNATURE REPLAY // CRITICAL

(HAL-16) MOVETH SIGNATURE REPLAY
Auditor: Halborn
Severity: Critical
Description
The transfer_from function is vulnerable to signature replay attacks. It uses the account's sequence number as a nonce, which is insufficient to prevent replay attacks: an attacker can reuse a valid signature to execute multiple unauthorized transfers, potentially draining a user's account.
The function uses account::get_sequence_number(from) as a nonce, which doesn't change after a transfer, allowing the same signature to be reused.
The scenario exploiting the vulnerability could be:

Alice signs a transfer approval for Bob to transfer 100 tokens.
Bob executes the transfer using Alice's signature.
Bob can replay the same signature to transfer another 100 tokens without Alice's consent.

Proof of Concept
The following test in MOVETH_tests.move passes, which demonstrates the vulnerability, reusing the permit multiple times:

BVSS
AO:A/AC:L/AX:L/R:N/S:U/C:N/A:N/I:N/D:C/Y:N (10.0)

Recommendation
It is recommended to implement a real nonce for the signed permit. As a reference, the OpenZeppelin's ERC20Permit implements a nonce tracking each permit utilisation.

@0xmovses @musitdev do we even need the transfer_from function? It's not used in any of the bridge modules.

I don't know. Every SC calls are done?

Correct @andygolay Moveth::transfer_from is not called anywhere inside atomic_bridge_initiator and atomic_bridge_counterparty, however if we were to remove it. It would no longer be a Fungible Asset. Let's add the nonce or sequence number solution suggested, so that a signature is explicitly tied to a specific nonce or sequence number.

What makes MOVETH a fungible asset is this code in init_module:
        // Create the stablecoin with primary store support.
        let constructor_ref = &object::create_named_object(resource_account, ASSET_SYMBOL);
        primary_fungible_store::create_primary_store_enabled_fungible_asset(
            constructor_ref,
            option::none(),
            utf8(ASSET_SYMBOL), /* name */
            utf8(ASSET_SYMBOL), /* symbol */
            8, /* decimals */
            utf8(b"http://example.com/favicon.ico"), /* icon */
            utf8(b"http://example.com"), /* project */
        );

in particular the create_primary_store_enabled_fungible_asset step.
If you look at the MOVETH test you can see how the transfer is done:
        // transfer from minter to receiver, check balance
        let minter_store = primary_fungible_store::ensure_primary_store_exists(minter_address, asset);
        let receiver_store = primary_fungible_store::ensure_primary_store_exists(receiver_address, asset);
        dispatchable_fungible_asset::transfer(minter, minter_store, receiver_store, 10);

In this case with minter being the "user" signing to approve the transfer.
From what I can tell, transfer_from appears to attempt to mimic how transferFrom is used in ERC-20 / Solidity.
In Move, it would be more typical to use dispatchable_fungible_asset::transfer for user-signed transfers.
If there's some special usecase for a spender to transfer tokens from someone else's account, then it might make sense for transfer_from to stay in the contract. But the bridge does not use that function and therefore, the transfer_from function appears to be unnecessary and therefore should be removed imo.

The transfer_from call is going to be removed because of @andygolay refactoring of all that code to use native gas token.

This PR removes the function https://github.com/movementlabsxyz/movement/pull/797


Test run is not added to the configured plan

Test run is not added to configured plan in TestRail. Invalid test plan_ids are being ignored, valid test plan_ids result in no post at all.
[TESTRUN]
project_id = 41
suite_id = 582
plan_id = 4235
description = 'This is test run from abcd'

[TESTCASE]
custom_comment = 'This is a custom comment'

To Reproduce
Steps to reproduce the behavior:

Configure library as shown above
Execute pytest using:  python -m pytest <path_to_testfile.py> --testrail
Observe console output

Expected behavior
Test is appears in testrail in specified testplan.
Env

TestRail: <IP_ADDRESS>7
PyTest:  pytest-6.2.1
OS: Linux

In my testing,  plan_id  and  run_id  are used for updating existing test_runs (run_id) or all test_runs within a plan (plan_id)
We need something like a --tr-testrun-milestone and --tr-testrun-plan  that will create a test run under a milestone or plan.
Or, the logic is broken and simply needs fixed.

This is a duplicate issues of https://github.com/allankp/pytest-testrail/issues/91


Incorrect description of aws.route53.Record type input

File: themes/default/content/docs/reference/pkg/aws/route53/record.md
In the Inputs section, type is defined as:

PRIMARY or SECONDARY. A PRIMARY record will be served if its healthcheck is passing, otherwise the SECONDARY will be served. See http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-configuring-options.html#dns-failover-failover-rrsets

however in the first example, we have
const www = new aws.route53.Record("www", {
    zoneId: aws_route53_zone.primary.zone_id,
    name: "www.example.com",
    type: "A", // <- Neither PRIMARY noor SECONDARY
    ttl: "300",
    records: [aws_eip.lb.public_ip],
});

My understanding is that type should be one of A, AAAA, CAA, CNAME, DS, MX, NAPTR, NS, PTR, SOA, SPF, SRV and TXT.
(from https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#type)

Hi @pierlucg-xs
I need to apologise for not getting back to this issue sooner! We need to do better here :/
I am going to close this out as a duplicate of #1315 and tell you that the underlying issue for this in https://github.com/pulumi/pulumi-terraform-bridge/issues/529 is currently being worked on


Fix markdown format.

First off, thanks for the great work on this!
Minor markdown formatting fix. I was reading through the documentation and noticed that the numbered list was not formatted correctly. Also my editor trimmed some whitespace. I would be happy to rollback the whitespace changes if you'd like.

Thanks for the fix!


Overhaul of metadata fields

The current implementation of metadata is illustrative only. Some unknowns:

Where does the list of fields come from?
Which fields are optional and which are mandatory?
What validation, if any, should be enforced?
Which fields should be filled out by the barcode reader?

Suggestions from Ben Price:
Metadata fields:

Follow Darwin Core, allow import of additional fields as needed (from CSV file or tickboxes):

Load some fields using predefined list (eg from emu export) consisting of a tabbed excel or multiple CSV files

tab/file 1 = project location and corresponding IRNs
tab/file 2 = project taxonomy and corresponding IRNs

Enable the addition of terms to the lists on the fly

"Specimen Number" should probably include term "UID" to make it more generally applicable

Location

easy for pinned specimens, 1 drawer = 1 image
harder for slides where multiple slide trays may be imaged in one big jig (needs input from Vlad)
load from image filename, part of imaging workflow already for pinned
load from predefined list for slides
include (hidden) EMu/database location IRN which is exported to CSV on final segmentation.

Taxonomic group

change to "Taxon"
load from predefined list exported in our case from EMu
include (hidden) EMu/database location IRN which is exported to CSV on final segmentation.

Additional metadata fields (check darwin format for correct annotation):

locality-country (using ISO lookup list)
locality-place (verbatim)
latitude (DD,MM,SS or DD.DDDD)
longitude (DD,MM,SS or DD.DDDD)
date collected (DD/MM/YYYY)

Simple Darwin Core terms supported, together with basic validation.

Fields are shown in groups:

Basic validation is done on some fields:

Occurrence

Individual count - a whole number greater than zero

Event

Event date - a date
Event time - a time
Year - a four-digit number
Month - a one or two digit number
Day - a one or two digit number

Location

Minimum elevation in meters - a number greater than zero
Maximum elevation in meters - a number greater than zero
Minimum depth in meters - a number greater than zero
Maximum depth in meters - a number greater than zero
Minimum distance above surface in meters - a number greater than zero
Maximum distance above surface in meters - a number greater than zero
Decimal latitude - DD MM SS N/S form or a a number between -90 and 90
Decimal longitude - DD MM SS E/W form or a a number between -180 and 180
Coordinate uncertainty - a number greater than zero
Coordinate precision - a number greater than zero
Georeferenced date - a date

Identification

Date identified - a date

Taxon

Name published in year - a four-digit number

Record level / Language is a drop-down list of two-letter language codes and names.
Location / Country code is a drop-down list of two-letter country codes and names.

User should be able to configure:

The field(s) to be displayed above the boxes in the grid. Currently (v0.1.6) the 'Material sample ID' field is shown
The field(s) to be populated by the "Read barcodes".  Currently (v0.1.6) the 'Catalog number' field (#88)
The field(s) to be used for the filenames of the cropped specimen images (#112)

Inselect should show objects that do not pass metadata validation, such as
* no barcode values
* barcode value that does not meet expected format (e.g. exactly ten digits)
Raised in slide scanner project meeting.

Substantial work for handling metadata has been done on metadata fields on the iss116 branch - the branch for this issue. Much of this work is, and will continue to be, specific to NHM projects.
User-defined metadata (and a host of other things) will be implemented as part of #156.


Things to explain in the docs

Based on questions people asked when I announced scriv, these things need explaining:

"Do you have a demo of how fragment categories are selected?"

Also:
2) The docs mention the ability to write change notes for different audiences. How is this achieved? Do I understand correctly that I can write the same text twice but with different accents: for example, one for devs (like private API and/or implementation changes), and the other for end-users (or lib users, like public API changes)

There's this problem that surfaced with towncrier: we've changed the template to include category names and since they were missing, and now only new releases will use that template so we have to find a way to retrospectively extract the fragments to reconstruct the changelog with a new template (https://github.com/pypa/setuptools/pull/2399#issuecomment-711014643). What if I change the template in scriv and want to update how the changelog looks? Is there any recommended/suppoprted way of doing that? I noticed there's --keep but the docs don't exactly describe what will happen if I keep the fragments in the tree.


Add OpenCPN.app v4.4.0

[X] Checked there aren’t open pull requests for the same cask.
[X] Checked there aren’t closed issues where that cask was already refused.
[X] When naming the cask, followed the token reference.
[X] Commit message includes cask’s name.
[X] brew cask audit --download {{cask_file}} is error-free.
[X] brew cask style --fix {{cask_file}} left no offenses.
[X] brew cask install {{cask_file}} worked successfully.
[X] brew cask uninstall {{cask_file}} worked successfully.

Thank you for the contribution. It was merged directly as 292d4a16a1c58ce98b46db6d97fb28af919ac431 to keep commit history cleaner. Your contribution is still credited to you.


chore: add force flag to login command

Closes TURBO-2355

main

#7378   👈

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Zertsov and the rest of your teammates on  Graphite

Nope, meant to make this a draft PR but hit the wrong button  🙃

Merge activity

Feb 16, 4:01 PM EST: @Zertsov merged this pull request with Graphite.


How to disable date header component

Is there a way to disable date header component completely? I'm including message time inside a custom message bubble and I would like to disable the date component completely.

This repo is a bit behind the flutter version, and there we have a custom header render, if we don't have it here (I guess possible to just return null) it will be added when I will be soon reviving this repo bringing all things we added in the flutter version.

@demchenkoalex Thanks for your answer and help, looking at the documentation the only prop I can customize is customDateHeaderText, which returns a string, not a component. Returning "null" inside this prop actually hides the string but not the component itself, which leaves unwanted space between bubbles :-( Is there any other prop tu customize the actual dateHeader component that I'm missing?

@demchenkoalex thank you for your effort. Is there any updates on this request or any ways to create custom Date component

I wouldn't wait for that


[TODO]: Assure GHA pipelines produce an extension artifact

Many proposed changes do require effective local testing and it would be very useful to publish the extension artifact on them so we can easily install it and test the proposed change locally.

I fixed that some time ago and forget to close it. Our builds to have attached artifacts now.


zookeeper: change image and add some params

This PR:

use official zookeeper image
bumps to zk version 3.4.14
add few parameters necessary to tune the size/capacity of the zk cluster
place necessary bootstrap/healthcheck scripts as CM
bumps zk operator version to 0.2.0 for future release
use rolling logs limited to the size of 10MB and max 10 files to avoid any overflow on disk caused by logs

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: zmalik
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [zmalik]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@zmalik: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

test-kubernetes-1.13
296df3b2eac50208776f00a9d9770819b0c22f80
link
/test test-kubernetes-1.13

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 test-kubernetes-1.13

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alenkacz, zmalik
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [alenkacz,zmalik]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alenkacz, kensipe, zmalik
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [alenkacz,kensipe,zmalik]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


lambda modify.

Pull Request Test Coverage Report for Build 10605

8 of 8 (100.0%)  changed or added relevant lines in 4 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 57.766%

Files with Coverage Reduction
New Missed Lines
%

sharding-orchestration/sharding-orchestration-core/sharding-orchestration-core-registrycenter/src/main/java/org/apache/shardingsphere/orchestration/core/registrycenter/util/IpUtils.java
3
76.0%

Totals

Change from base Build 1177:
-0.04%

Covered Lines:
11827

Relevant Lines:
20474

💛  - Coveralls


curl was not found in the path

Hello,
The cUrl upload which has been working fine for the past 2 weeks has suddenly started failing causinng my release management process to fail. I get the following error messages.
##[error]curl was not found in the path.
##[error]Task cURLUploader failed. This caused the job to fail.
I am using the cUrl task to upload the web.config file after replacing tokens. This was working fine for the past 2 weeks. The same failure has happened on 2 different team projects.
Thanks.

This should be fixed now.  Please reactivate if you continue to have issues.

Thanks!


Mixitup pagination impossible to import

Hello,
I'm following the documentation to call the plugin programmatically:
import mixitup from 'mixitup'
import mixitupPagination from '../mixitup-pagination'
mixitup.use(mixitupPagination)

But I always get this error in the console:
 Uncaught Error: [MixItUp Pagination] MixItUp core not found
This is not happening when using Mixitup alone.

You should only see this error if you include the extension via a <script> tag in your document. If you are building a modular project, you should not have any libraries being loaded via

Yes I'm using webpack no using script tag

Thanks - do you know which version of webpack you're using? I'll try to see if I can reproduce the error.

"webpack": "^3.8"

Have you been able to reproduce it?

Have just had a chance to test this and all is working as expected for me.
Firstly, here's my package.json:
{
    "name": "webpack-test",
    "version": "0.0.0",
    "private": true,
    "scripts": {
        "build": "./node_modules/.bin/webpack"
    },
    "devDependencies": {
        "webpack": "^3.8.0",
        "mixitup": "3.2.2",
        "babel-core": "^6.25.0",
        "babel-loader": "^7.1.1",
        "babel-preset-env": "1.6.1"
    }
}

Secondly, here's my webpack.config.js:
const path = require('path');

module.exports = {
    entry: './src/main.js',
    output: {
        filename: 'app.js',
        path: path.resolve(__dirname, 'dist')
    },
    devtool: 'source-map',
    module: {
        rules: [
            {
                test: /\.js$/,
                exclude: /(node_modules)/,
                use: {
                    loader: 'babel-loader'
                }
            }
        ]
    }
};

This takes the following input of /src/main.js:
import mixitup from 'mixitup';
import mixitupPagination from './mixitup-pagination';

mixitup.use(mixitupPagination);

console.log(mixitup);

And outputs a bundle to /dist/app.js, which console logs a reference to the mixitup factory function with the pagination extension successfully integrated.
Finally I have the following index.html page which loads the working bundle.
<html>
    <head>
        <title>Webpack Test</title>
    </head>
    <body>
        <script src="./dist/app.js"></script>
    </body>
</html>

On loading this page, the console log appears as expected with no errors, and I can successfully create instances of mixitup with pagination enabled.
I hope that is helpful. I would double check that you are definitely not including anything other than your app bundle via a script tag in your HTML.

Ok thank you for your help, I finally found the problem.
It was coming from my .babelrc:
{
  "presets": [
    [
      "@babel/preset-env",
      {
        "modules": false
      }
    ]
  ]
}

Passing modules to true fix it!
The doc from babel that help me for people having the same issue:
https://github.com/babel/babel/tree/master/packages/babel-preset-env#modules

Oh glad you figured it out.
Out of interest, what was the reason you had modules set to false? Would be be good for me to understand what circumstances people would use that configuration option.

Set modules to false ensure that import statements are left as is (opposed to transpiling them to require). Doing this give Webpack the ability to statically analyze the code to produce more efficient bundles...

Further reading: https://github.com/babel/babel/tree/master/packages/babel-preset-env

I don't know why pagination plugin isn't compatible with this option.
It's the only import I use that cause this problem.

Ah ok, I understand. Unfortunately, the MixItUp source code doesn't use a standard module loading system internally, so I can see why that would happen. I'll see if I can make some changes to the UMD declaration to get around this, as sounds like a useful optimisation for the rest of your project.

That would be awesome :)

That made me think to this issue: https://github.com/meandmax/lory/blob/master/dist/lory.js
Looks like this libs use some automatic building method from webpack (probably an additional plugin) to create a UMD declaration.
And this is working with the modules option of babel 😎

One more reason to make the move to webpack don't you think?
Plus es6, uglify-es, stylelint, UMD, optimisations... didn't you dream about it? 😛

Plus the webpack is already done, it's simple as a copy past for you:
https://github.com/meandmax/lory

Hey @patrickkunka any update about this?

Hi Jim. I'm afraid I don't have any plans to address this until the next major version where I will probably MixItUp rewrite in TypeScript. I can't give any particular ETA on this as I don't have a lot of time for side-projects at the moment.

With latest version of babel the above fix doesn't work anymore...
It could be nice if you could make a quick fix.
It's now impossible to load your plugin with bundler.

I've try to export mixitup pagination like by modifying source code but it just don't work.
I need you help.

Hi Jim
Apologies for the delay in response. I'm afraid I've been busy with my newborn daughter and day job over the last 6 months and mixitup is in maintenance mode only, meaning that I'm not able to invest time in significant refactoring, which is what I suspected this issue required.
However, I've just tried to recreate the issues you're seeing using the latest babel, babel-preset-env, module:false, and webpack, and everything is working fine for me.
I've created a repo here to demonstrate a working setup:
https://github.com/patrickkunka/mixitup-babel-test
If you build it and load up the index.html with a webserver, you'll see a functioning pagination demo, built with webpack and babel.
Please tell me what's different about your babel/webpack configuration.
P.S. I'd be more than happy to give you a refund for whatever licenses or extensions you've purchased, but I want to note that it is clearly stated on the website that support is not included or guaranteed.

Hi Patrick,
Congratulation for newborn daughter and thank you for your message.
I really appreciate your transparency and the solutions you offer.
Let me try your test and run a few test to check what you're saying.
I'm coming back to you asap.
Best.

Thanks for understanding!
I'm hoping that the issues you're seeing might not be related to MixItUp but something else in your environment – but if you can help me figure out how we can tweak the repo above in order to recreate the errors you're seeing then that will be a good start.

Hey @patrickkunka,
unfortunately, we get the same errors as above. Has there been any work done on this issue or any new recomendations?

Hi there - were you able to test in the example repo I provided? If you could highlight any differences in integration that cause yours to fail I'd be more than happy to look into this.

I didn't test the example repo. My webpack config for the babel-loader looks like
{
  test: /\.jsx?$/,
  loader: 'babel-loader',
  exclude: /node_modules\/(?!(dom7|swiper)\/).*/,
  options:
  {
    presets: [
      ['@babel/env',
      {
        targets:
        {
          browsers: ["> 0.5%", "last 2 versions", "Firefox ESR", "IE >= 11", "safari >= 7"]
        },
        useBuiltIns: 'usage',
        corejs: 3,
        exclude: ['transform-regenerator'],
        modules: false
      }]
    ],
    plugins: ['@babel/plugin-syntax-dynamic-import']
  }
}

yeah pretty classic config, I got the almost same one. (I just don't exclude transform-regenerator)

Hi @montagmorgens - thanks so much for sharing your config.
I was finally able to fully recreate the issue. It seems that previously, my .babelrc was being ignored by webpack and babel loader, so moving the preset config to the webpack config itself was the key.
So, the fix is actually very simple, we just need to ensure that the directory containing our MixItUp extensions is excluded, just as we exclude node_modules.
Here's my webpack.config.js now (i've removed anything that isn't relevant to the issue):
const path = require('path');

module.exports = {
    entry: './src/index.js',
    output: {
        filename: 'bundle.js',
        path: path.resolve(__dirname, 'dist')
    },
    mode: "development",
    devtool: 'source-map',
    module: {
        rules: [
            {
                test: /\.js$/,
                // NB: the directory containing your mixitup extensions
                // must be excluded from transpilation
                exclude: /(node_modules|vendor)/,
                use: {
                    loader: 'babel-loader',
                    options: {
                        presets: [
                            [
                                '@babel/env',
                                {
                                    useBuiltIns: 'usage',
                                    corejs: 3,
                                    modules: false
                                }
                            ]
                        ]
                    }
                }
            }
        ]
    }
};

I've also updated the reproduction project, so you can test it there and see it working (or failing by removing the extra vendor exclude.
https://github.com/patrickkunka/mixitup-babel-test
Please let me know if this works for you (if you're still interested in using MixItUp extensions with ES modules).

Have also updated the docs:
https://www.kunkalabs.com/mixitup-multifilter/docs/get-started/
https://www.kunkalabs.com/mixitup-pagination/docs/get-started/


Expose senza errors to lizzy-client

Fixes #123
Seems like we just need to expose all senza errors to the client then it can handle properly showing the error to the users in form of command output. If I understand correctly removing the server-side senza commands errors handing and letting it go to the client should be enough.

I am just not sure about it all being 500. Those are going to be indeed senza errors caused by bad parameters, etc. Not an error of lizzy that is why I think it should be 400. Do you think I could change that?

Coverage decreased (-0.9%) to 89.25% when pulling d7fc52d84d1785f78cae6a7583507a60d80c53b5 on rafaelcaricio:make-lizzy-output-closer-to-senza into e568f94d56cf41e6156b6461402ca715579dbeab on zalando:release2.0.

:+1:


Feat add rax abc config

Add rax build config

https://github.com/ice-lab/iceworks/issues/66

Codecov Report

Merging #68 into release/0.1.0 will decrease coverage by 0.30%.
The diff coverage is 12.50%.

@@                Coverage Diff                @@
##           release/0.1.0      #68      +/-   ##
=================================================
- Coverage          79.18%   78.88%   -0.31%
=================================================
  Files                 26       26
  Lines                961      966       +5
  Branches             196      198       +2
=================================================
+ Hits                 761      762       +1
- Misses               196      200       +4
  Partials               4        4

Impacted Files
Coverage Δ

packages/generate-project/src/fommatProject.ts
83.05% <12.50%> (-5.84%)
:arrow_down:

Continue to review full report at Codecov.

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


fix(schedules): hide auxiliary class assignments if circuit overseer visit

:tada: This PR is included in version 2.22.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Excerpt has no indication that post continues

When making an excerpt to the blog post list, Empower theme doesn't seem to make any kind of marking that the article continues, like "click here to continue reading" etc.
Am I missing something and is it intentional ?

That's by design. You can add a "read more" link to loop.dust if you want:
{! Excerpt !}

  {@excerpt paragraphs="2"/}
  Read more

The default theme is really just an example of how to theme Postleaf, so feel free to customize away.


Add id term to featuresearch.g4

Fix #786. Add a search atom id to the parser. id searches for features whose feature identifier matches the search value exactly.
Also a drive-by change for the Snapshot_termContext switch case in visit().

Note to reviewers: the lint errors in CI aren't related to this change, but Will be addressed in a follow-up PR

@jcscottiii On a related note, given that func (v *FeaturesSearchVisitor) Visit(tree antlr.ParseTree) any  magically worked without case *parser.Snapshot_termContext:, should it return nil instead of return tree.Accept(v)?

Great question! I had to break out the debugger to see what was going on while running the test.
tree.Accept(v) calls the accept method for the generated BaseFeatureSearchVisitor. It looks like it indeed knows how to call our Visit_xx methods. So we could simplify Visit to this instead:
func (v *FeaturesSearchVisitor) Visit(tree antlr.ParseTree) any {
	return tree.Accept(v)
}

(you can get rid of the comment on top of Visit too now.)


extend options to aggregate ranks across batches for HVG selection

I would like to get an opinion from @gokceneraslan, @adamgayoso (who implemented this originally), or someone else more familiar in hvg selection here.
I feel like we should probably have multiple methods for this, which we expose via a kwarg. I'm not confident median rank makes sense as a value here. I think there are assumptions about what kinds of values a rank can have that get broken by taking the median.
Is the method for aggregating hvgs from multiple batches here reasonable? For reference, a similar code block can be found in _highly_variable_genes_seurat_v3, which says this is the method used in SelectIntegrationFeatures from Seurat.
Originally posted by @ivirshup in https://github.com/theislab/scanpy/pull/1715#discussion_r736690390
@jlause commented:
I agree that exposing multiple options could make sense here. Any opinion @gokceneraslan and @adamgayoso which ones we should implement / which one should be the default?
I just copied this part from the seurat_v3 batch integration, so I don't have an expert opinion - but if I remember correctly, the other flavors use dispersions_norm to break ties instead of using the median rank. If I read the code correctly, this is the within-batch dispersion averaged over batches.
We could also do something similar here: Compute residual variance within each batch, take the average across batches, and use that to break ties instead of using median rank.

Is the method for aggregating hvgs from multiple batches here reasonable?

It may not actually be the intended, see #2088


App crash on app launch.

In android device, app is crashing while try to launch the app.

@cakesoft-swati - I think this can be closed


Multiple bots

Can you please provide an example for a bot for 2 facebook pages?
On the README,

Where do we put the ExampleProvider class?
Where do we put the multiple ACCESS_TOKEN, APP_SECRET, and VERIFY_TOKEN for each pages?
How does the bot differentiate which page the message originated?

Starting to get the hang of it. Your gem is amazing, @jgorset !
On #3,
I have 2 pages. For example, the page IDs from developers.facebook.com are:<PHONE_NUMBER>11111 and<PHONE_NUMBER>22222. When the bot receives a message from Bot.on :message do |message|, I could get the page ID where it originated by message.recipient['id'] then reply accordingly.
Am I doing this right so far?

Hi @edos4, and thank you! Glad it's helpful to you!
I guess you've already figured out that you need to implement your own configuration provider that doesn't use those default environment variables (ACCESS_TOKEN, APP_SECRET and VERIFY_TOKEN), but some other method that allows you to authenticate with different credentials for different pages. I've written a little about it under "Make a configuration provider" in the README. I hope that put you on the right track, and otherwise please make a pull request that improves upon it for the next person.

I have 2 pages. For example, the page IDs from developers.facebook.com are:<PHONE_NUMBER>11111 and<PHONE_NUMBER>22222. When the bot receives a message from Bot.on :message do |message|, I could get the page ID where it originated by message.recipient['id'] then reply accordingly.

That's exactly right, but if you're replying immediately (with message.reply inside a Bot.on block), the gem will already figure all of that out for you! If you look at the code for message.reply, you'll find that it gets around to calling access_token and app_secret_proof, which in turn calls the app_secret_for(id) and app_secret_proof_for(id) methods of -- you guessed it -- your configuration provider!
If you are sending messages that aren't a direct response to a message that you receive (with Bot.deliver), though, you will need to specify access_token and app_secret_proof as arguments, because the gem needs to know which page you want to send the message from.

I got around to #259 now, so if you want to use just page_id instead of messing around with access tokens outside of your configuration provider, now you can!
It's a backwards incompatible change, so I released it with version 2.0.0.

The 1.x way:
Bot.deliver({
  recipient: {
    id: '45123'
  },
  message: {
    text: 'Human?'
  },
  messaging_type: Facebook::Messenger::Bot::MessagingType::UPDATE
}, access_token: ENV['ACCESS_TOKEN'], app_secret_proof: app_secret_proof)

The 2.x way:
Bot.deliver({
  recipient: {
    id: '45123'
  },
  message: {
    text: 'Human?'
  },
  messaging_type: Facebook::Messenger::Bot::MessagingType::UPDATE
}, page_id: YOUR_PAGE_ID)


Add Saturday memorial of the Blessed Virgin Mary

I believe I have raised this issue somewhere, but I could not find the issue.
We should add the Saturday memorial of the Blessed Virgin Mary on each Saturday of the Ordinary Time where there is either feria only, or one or more optional memorials. This should be done in the general.ts or the celebrations.ts, as this Memorial can be celebrated throughout the whole Church.

Just a note with localisations of the celebration name:

cs: Sobotní památka Panny Marie.

Could be related in some points to https://github.com/romcal/romcal/issues/135.

Could be related in some points to #135.

We your issue (#135) better worded with some specific solutions.
In my opinion, when implemented, we could create something that would solve:

the Saturday Memorial of BVM;
the recurring celebrations (as you suggested in #135);
celebration of a celebration multiple times in one year at specific dates (even on dates defined as on 33rd Sunday in the OT; see #259 (comment)).

We could close this issue in favour of #135 if you think so. :wink:

We could close this issue in favour of #135 if you think so. 😉

Yes. Just provide use cases in #135 is enough.


Fix/hf

Change

This PR encompasses two changes:

Update the trigger creation logic, so that the triggers actually get created.
Register huggingface datasets under their private identifier, instead of the public one which is subject to change (#385)

To accommodate the last change, there is also a script migrate_hf.py which checks huggingface datasets already present in the database and 1. removes them if their identifier is no longer valid and 2. updates their identifiers otherwise.
How to Test

Setting up an old database and verifying the wrong behavior
A bit of a doozy with so much going on. First, let's create a version of an "old" style database:
docker compose --profile "*" down
git checkout develop
./scripts/clean.sh
docker compose --env-file=.env --env-file=override.env --profile "huggingface-datasets" up -d

That will start populating the develop database with huggingface entries, old-style.
Keep track of progress with
docker exec -it sqlserver mysql -uroot -pok --database=aiod -e "select platform_resource_identifier, name from dataset where name in ('fka/awesome-chatgpt-prompts', 'PleIAs/common_corpus');"
docker exec -it sqlserver mysql -uroot -pok --database=aiod -e "select COUNT(*) from dataset; select COUNT(*) from ai_asset; select count(*) from ai_resource;"

and make sure some (>10) datasets are uploaded, and the first query shows both the fka/awesome-chatgpt-prompts and PleIAs/common_corpus datasets, since we will use them later.
Also note that no AIoD triggers are created:
docker exec -it sqlserver mysql -uroot -pok --database=information_schema -e 'select TRIGGER_NAME from TRIGGERS;'

Let's stop harvesting (assuming you have enough datasets):
docker container stop huggingface-dataset-connector

To really make sure no triggers happen, let's delete a dataset. Because the trigger listens for hard-deletes, and datasets are deleted "softly" by default, we briefly need to disable this behavior.  Change the expression in
thisif statement to always be True.
Then visit localhost, log in with the test user, and delete a dataset (pick any identifier >=10 to avoid deleting one of the two datasets we need later). The dataset will be deleted successfully, but their relations remain:
docker exec -it sqlserver mysql -uroot -pok --database=aiod -e "select COUNT(*) from dataset; select COUNT(*) from ai_asset; select count(*) from ai_resource;"

Undo your change you made to the resource connector:
git checkout .

and shut down the services:
docker compose --profile "*" down

Verifying new behavior
Start the services again on the new branch (this may take a little longer):
git checkout fix/hf-id
docker compose --env-file=.env --env-file=override.env up -d

verify no data has changed, but delete triggers have been added:
docker exec -it sqlserver mysql -uroot -pok --database=information_schema -e 'select TRIGGER_NAME from TRIGGERS;'
docker exec -it sqlserver mysql -uroot -pok --database=aiod -e "select COUNT(*) from dataset; select COUNT(*) from ai_asset; select count(*) from ai_resource;"

(since the database cannot retroactively use the trigger, there will remain one fewer dataset than ai asset)
Now we modify some data to simulate the situation where a HF user has changed their account name (see also #385):
docker exec -it sqlserver mysql -uroot -pok --database=aiod -e "update dataset set platform_resource_identifier='NaiveDev/coco-2017-instance', name='NaiveDev/coco-2017-instance' where platform_resource_identifier='fka/awesome-chatgpt-prompts';
update dataset set platform_resource_identifier='aha-org/coco-2017-instance', name='aha-org/coco-2017-instance' where platform_resource_identifier='PleIAs/common_corpus';"

The user aha-org changed their name to NaiveDev, and so we now modify two dataset entries to simulate being an old and new version of the indexed data. This is the behavior the HF connector would have if encountered a renamed dataset, since uniqueness is only enforced with user/dataset.
Let's run our migration script:
docker run -it -v $(pwd):/all --network='AIOD-rest-api_default' --entrypoint=/bin/bash aiod_metadata_catalogue -c 'python /all/scripts/migrate_hf.py'

and let's verify that our HF entries are updated accordingly:
docker exec -it sqlserver mysql -uroot -pok --database=aiod -e "select platform_resource_identifier, name from dataset where name in ('aha-org/coco-2017-instance', 'NaiveDev/coco-2017-instance');"
docker exec -it sqlserver mysql -uroot -pok --database=aiod -e "select platform_resource_identifier, name from dataset; select COUNT(*) from dataset;"

We see the aha-org dataset was removed, along with its linked resources, and the NaiveDev had assigned their new id correctly. Moreover, the related ai resource and ai asset entry that related to the aha-org dataset are also deleted through their triggers. Poke around in the database some more to check everything is OK, if needed.
Now let's spin up the HF connector:
docker compose --env-file=.env --env-file=override.env --profile "huggingface-datasets" up -d

and after a while verify that new entries have the correct platform_resource_identifier associated (i.e. a hex string).
Checklist

[x] Tests have been added or updated to reflect the changes, or their absence is explicitly explained.
[x] Documentation has been added or updated to reflect the changes, or their absence is explicitly explained.
[x] A self-review has been conducted checking:

No unintended changes have been committed.
The changes in isolation seem reasonable.
Anything that may be odd or unintuitive is provided with a GitHub comment explaining it (but consider if this should not be a code comment or in the documentation instead).

[x] All CI checks pass before pinging a reviewer, or provide an explanation if they do not.

Related Issues

For posterity; no response in HF forum w.r.t. usage of "_id" (https://discuss.huggingface.co/t/are-dataset-id-safe-to-use/122309)


odb: optimize exists_prefix and disallow short_oid of size <=2

Also changed the implementation of exists to call is_file() instead of exists().
The previous implementation was using odb.all() which goes through all the files in the cache which coupled to path_to_oid was very slow.

Looks like this is not used anywhere except in cli tools.

Yeah, only used in CLI for now. I noticed it was terribly slow for even a small cache filled only with mnist dataset.


[docs] Document MultitenantAdminMixin multitenant_shared_relations and parent

MultitenantAdminMixin has two attributes:

multitenant_shared_relations: the description is totally unclear
parent this is not documented, I added this to allow having multi-tenancy for models which don't have directly an organization field, but have a parent model which does have the field

@nemesisdesign Can I work on this issue? :)


udemy business downloader

hey how you guys doing, sorry to bother u guys but i have this problem.i can access to udemy busniess account through udeler.but when i try to download  a course it shows bulding course data and nothing happens.i know this usually it takes little time to build course data.but in this case nothing happens.so do you guys have any solution for this?

@iam-malithmax I see you have closed this issue. I too am facing the same one since yesterday now. Tried everything I can think of - restarting the application multiple time with and without company VPN being connected before/after starting the application, etc. but nothing has helped. Can you please help elaborate on what worked for you? :)

Hey @PratikRJoshi sorry to hear that.im afraid i can't help you.i still have the same problem too.i closed that only because there are multiple threads about the same issue and i thought its unnessary to ask the same question agian and agian.joing the other threads about this issue, i think there will be a solution soon.


Editor displays deno-lint-ignore comments as spelling errors

I don't know if this is a problem solvable by this Deno extension or not, but the Nova editor displays deno-lint-ignore (e.g. // deno-lint-ignore no-cond-assign) comments as spelling errors. It would be nice if this extension could automatically ignore for spelling deno-lint-ignore and all of the Deno lint rule names.
In the mean time, users can right-click on the false-positive spelling errors and manually ignore them as they come up.

This is something that's always bugged me too, it happens with comments like // eslint-ignore-next-line too. I think to do this I'd have to create a custom syntax to include with this extension, which is a bit much right now.
In the meantime, another option is to uncheck Edit -> Spelling and Grammar -> Check Spelling While Typing.


How to specify columns when updating a table range?

I want to update data in a table with the API. Docs say the URL is like below.
PATCH /me/drive/items/{id}/workbook/tables/{id|name}/columns/{id|name}/range
What goes into the columns/{id|name} section when I want to update multiple columns or all columns? Is it a numeric 0-based index range like "0:12"? Or can I only update one column at a time? Do I specify the row indices anywhere, or must I send data for all rows of the table every time? None if this is explained anywhere that I could find.

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

ID: 2e621007-b67f-9b43-a215-34346262a307
Version Independent ID: 5f103903-d402-281a-aaa9-38cfe1ce9d00
Content: Update range - Microsoft Graph v1.0
Content Source: api-reference/v1.0/api/range-update.md
Product: excel
Technology: microsoft-graph
GitHub Login: @lumine2008
Microsoft Alias: MSGraphDocsVteam

This is about documentation. The docs don't answer any of the questions I
presented.
On Fri, Mar 15, 2024, 12:44 PM microsoft-github-policy-service[bot] <
@.***> wrote:

Closed #581
https://github.com/microsoftgraph/microsoft-graph-docs-contrib/issues/581
as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoftgraph/microsoft-graph-docs-contrib/issues/581#event-12134921198,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHOP3Y73XL5LFNLKPRSGLKDYYMXORAVCNFSM6AAAAAA3IQSSGWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGEZTIOJSGEYTSOA
.
You are receiving this because you authored the thread.Message ID:
<microsoftgraph/microsoft-graph-docs-contrib/issue/581/issue_event/12134921198
@github.com>


feat(mission_planner)!: support ad api

Signed-off-by: Takagi, Isamu<EMAIL_ADDRESS>Description
Introduce AD API for routing. This PR is the mission planner part of the diagram.
Here are the changes for each package:

component_interface_specs: Add the internal routing interface definitions.
tier4_planning_launch: remove redundant launch file.
mission_planner: change mission planner to support AD API.

Related links
https://github.com/autowarefoundation/autoware.universe/pull/1494
https://github.com/autowarefoundation/autoware_msgs/pull/33
Tests performed

Launch the planning simulation.
Check the routing state is UNSET.
Call the set_route_points API (refer to notes).
Check the routing state is SET.
Call the set_route_points API and check if it fails.
Start vehicle driving.
When vehicle goals, check the routing state is ARRIVED.
Call the clear_route API.
Call the set_route API (refer to notes)..

Notes for reviewers
Sample Routes are from this position.

Sample1 (SetRoutePoints)
ros2 service call /planning/routing/set_route_points  autoware_ad_api_msgs/srv/SetRoutePoints "
header: {stamp: {sec:<PHONE_NUMBER>, nanosec: 893215051}, frame_id: map}
goal:
  position: {x: 3835.50, y: 73765.91, z: 0.0}
  orientation: {x: 0.0, y: 0.0, z: -0.52530, w: 0.85091}"

Sample2 (SetRoutePoints)
ros2 service call /planning/routing/set_route_points  autoware_ad_api_msgs/srv/SetRoutePoints "
header: {stamp: {sec:<PHONE_NUMBER>, nanosec: 893215051}, frame_id: map}
goal:
  position: {x: 3835.50, y: 73765.91, z: 0.0}
  orientation: {x: 0.0, y: 0.0, z: -0.52530, w: 0.85091}
waypoints:
 - position: {x: 3774.31, y: 73802.53, z: 0.0}
   orientation: {x: 0.0, y: 0.0, z: 0.22214, w: 0.97501}"

Sample1 (SetRoute)
ros2 service call /planning/routing/set_route  autoware_ad_api_msgs/srv/SetRoute "
header: {stamp: {sec:<PHONE_NUMBER>, nanosec: 893215051}, frame_id: map}
goal:
  position: {x: 3835.50, y: 73765.91, z: 0.0}
  orientation: {x: 0.0, y: 0.0, z: -0.52530, w: 0.85091}
segments:
- {preferred: {id: 34976, type: lane}, alternatives: []}
- {preferred: {id: 34981, type: lane}, alternatives: []}
- {preferred: {id: 34585, type: lane}, alternatives: []}
- {preferred: {id: 34579, type: lane}, alternatives: []}
- {preferred: {id: 34780, type: lane}, alternatives: []}
- {preferred: {id: 34675, type: lane}, alternatives: []}"

Sample2 (SetRoute)
ros2 service call /planning/routing/set_route  autoware_ad_api_msgs/srv/SetRoute "
header: {stamp: {sec:<PHONE_NUMBER>, nanosec: 893215051}, frame_id: map}
goal:
  position: {x: 3835.50, y: 73765.91, z: 0.0}
  orientation: {x: 0.0, y: 0.0, z: -0.52530, w: 0.85091}
segments:
- {preferred: {id: 34976, type: lane}, alternatives: []}
- {preferred: {id: 34981, type: lane}, alternatives: []}
- {preferred: {id: 34636, type: lane}, alternatives: []}
- {preferred: {id: 34564, type: lane}, alternatives: []}
- {preferred: {id: 34495, type: lane}, alternatives: []}
- {preferred: {id: 34507, type: lane}, alternatives: []}
- {preferred: {id: 34795, type: lane}, alternatives: []}
- {preferred: {id: 34606, type: lane}, alternatives: []}
- {preferred: {id: 34672, type: lane}, alternatives: []}
- {preferred: {id: 34675, type: lane}, alternatives: []}"

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@kenji-miyake @yukkysaito @mitsudome-r
In this PR, we changed the root topic name to /planning/mission_planning/route (original name is /planning/routing/route). However, an error has occurred because the name is already used to distribute the HAD map route internally. So I'll change it to /planning/mission_planning/api_route. Or any other suggestions?

@isamu-takagi I was thinking that we'll replace the existing topic. Would it be possible for you to explain the problem a bit more concretely? :bow:

@kenji-miyake The existing topic is an implementation-dependent message type HADMapRoute. The new topic is an implementation-independent API message type Route. So it cannot be replaced without forcing the internal implementation nodes to use the API type.

Waiting for https://github.com/autowarefoundation/autoware_msgs/pull/33.

When I launch the autoware with this PR merged, it failed with the following error:
[component_container-43] [ERROR<PHONE_NUMBER>.014441264] [planning.mission_planning.mission_planning_container] OnLoadNode(): Failed to find class with the requested plugin name 'mission_planner::MissionPlannerLanelet2' in the loaded library:(L219)

@TakaHoribe
Are you using TIER IV's meta-repository? Then, I'll sync it.

Are you using TIER IV's meta-repository? I'll sync it.

Yes. Would you make a PR for the autoware_launch?

Yes. Would you make a PR for the autoware_launch?

@TakaHoribe https://github.com/tier4/autoware_launch/pull/520


Project Summary - Completed Projects sorted by date

In the Project Summary the Completed Projects list is collapsable or expanded. When expanded it shows all the projects completed over time. We would like to be able to select all projects or projects for a given year, similar to what is done with the Vetting section for Approved Application. The date used to sort by should be Project Start Date

Added ability to filter by year for completed & changed the start date display to the proper time zone.


Feature: add Arbitrary. Allow proptest!(..) to omit strategy when T : Arbitrary

Notes
This issue is a more long-term issue and may, to be really useful, depend on landing procedural macros in Rust stable, or provide a nightly only side-crate for some parts (3.).
Edit: Apparently procedural macros already allow for custom derive in stable
Motivation
In a lot of cases, there's a canonical way to generate an object of type T.
In such cases, you could simply encode the canonical strategy for such a T in the standard quickcheck Arbitrary trait.
The benefits of doing this are:
1.
Increased familiarity for quickcheck users by bridging the gap.
2.
The creation of the Strategy in proptest! can be omitted, and
proptest! {
    #[test]
    fn i64_abs_is_never_negative(a in prop::num::i64::ANY) {
        assert!(a.abs() >= 0);
    }
}

can be turned into:
proptest! {
    #[test]
    fn i64_abs_is_never_negative(a: i64) {
        assert!(a.abs() >= 0);
    }
}

or even the more standard in quickcheck:
proptest! {
    #[test]
    fn i64_abs_is_never_negative(a: i64) -> bool { a.abs() >= 0 }
}

3.
Custom "deriving" Arbitrary, by macro (to decouple testing from main logic), or by standalone derive if Rust ever gets that, becomes possible in a lot of cases.
Rules for deriving by induction:

All unit types are Arbitrary by simply always returning the unit.
All product types are Arbitrary if their factors are Arbitrary.
All sum types are Arbitrary if each product type in each variant in a sum type is Arbitrary. Variants with no inner product are just unit types.

Ergonomics
It is considerably more ergonomic to use a macro to generate strategies compared to simply re-iterating the variants in the enum.
The trait
The trait could look like:
/// `Arbitrary` determines a canonical `Strategy` for the implementing type.
///
/// It provides one function to, yield strategies for generating `Self`.
pub trait Arbitrary
where
    Self: Sized + Debug
{
    /// The type of `ValueTree` used for `Self`'s `Strategy`.
    type ValueTree: ValueTree<Value = Self>;

    /// The type of `Strategy` used to generate values of type `Self`.
    type Strategy: Strategy<Value = Self::ValueTree>;

    /// Yields a `Strategy` for generating values of type `Self`.
    fn arbitrary() -> Self::Strategy;
}

Or, in a future Rust version:
/// `Arbitrary` determines a canonical `Strategy` for the implementing type.
///
/// It provides one function to, yield strategies for generating `Self`.
pub trait Arbitrary
where
    Self: Sized + Debug
{
    /// Yields a `Strategy` for generating values of type `Self`.
    fn arbitrary() -> impl Strategy<Value = impl ValueTree<Value = Self>>;
}

I will start work on the Arbitrary trait and a procedural macro for custom derive of it for now. So, let's see how that goes first and I'll report on my progress.

There's a lot of facets here; hopefully I cover all of them.

In a lot of cases, there's a canonical way to generate an object of type T.

I don't by any means disagree with this, but it would be nice to have some data for how often this applies in real code using things like Hypothesis/proptest.
For what it's worth, here's some info for what I've worked on:

ensync: Generally holds, though arb_fs() almost certainly wouldn't be covered by the proposal here since it's recursive. It's worth noting though that this was originally adapted from quickcheck, so it's strongly biased in that direction.

hexeline: I don't think it ever applies, but admittedly hexeline is unusual in a lot of ways.

Some proprietary code I worked on used fj's quickcheck and in the majority of cases had exactly one Arbitrary per type, but part of this is due to how excruciating making new Arbitrarys in Java 7 was.

Arbitrary

Maybe DefaultStrategy since the implementation essentially just provides a Strategy?
I'll keep calling it Arbitrary below for now for consistency.

a in prop::num::i64::ANY … can be turned into … a: i64

I can't say I particularly care for this; I think maintaining the clarity that a Strategy is just a normal value that can be passed around is important. Having two forms like that would also give an awkward speed-bump when needing to transition between them when there are multiple arguments.
I'd also question how useful it is to do this for things like integers; I'm not sure how many cases there are where testing with literally arbitrary integers is useful. IIRC, quickcheck defaults to the range 0..100.

Custom "deriving" Arbitrary

This sounds like a very good idea, and would particularly eliminate a lot of boilerplate in ensync.

Rules for deriving by induction

The rules don't take into account recursive types (e.g., En), which ideally would be handled in a way more graceful than aborting at runtime by overflowing the stack.
I think any custom derive would also need a way to override the strategy for a particular field, since the type will often have its own constraints on internal state. Something akin to #[serde(serialize_with = "..")] might work. This would also relieve that field of needing to be Arbitrary.

re-iterating the variants in the enum

IMO this is the single biggest weakness in proptest right now; the compiler can't help you if you forget a variant when defining the strategy.

The trait

I don't have anything to say about this as it pertains to the original proposal that I haven't already voiced.

Overall, this is something I feel reasonably positively about. My biggest concern is that Arbitrary is all-or-nothing, so the moment you need even a single parameter for constructing the strategy, you're back to what we have today. It would be nice if there were some way to pass parameters through and still use the code generation.
I'm not sure how practical this would be, but to illustrate:
pub trait Arbitrary where Self : Sized + Debug {
    // Parameters that can be passed to the implementation. The custom derive
    // could default this to `()`.
    type Parameters : Default;
    // As in the issue description.
    type ValueTree: ValueTree<Value = Self>;
    type Strategy: Strategy<Value = Self::ValueTree>;

    fn arbitrary(parameters: Self::Parameters) -> Self::Strategy;
}

// Simple use of auto-derive
#[derive(Debug, Arbitrary)]
struct SimpleStruct {
    string: String,
    int: i64,
}

// Generated impl
impl Arbitrary for SimpleStruct {
    type Parameters = ();
    type ValueTree = /* big type */;
    type Strategy = /* big type */;

    fn arbitrary(parameters: ()) -> Self::Strategy {
        // NB This won't compile because the type is not nameable
        (String::arbitrary(String::Parameters::default()),
         i64::arbitrary(i64::Parameters::default()))
            .prop_map(|string, int| SimpleStruct { string, int })
    }
}

// Use custom parameters
#[derive(Debug, Arbitrary)]
#[proptest(paremeters = ComplexParms)]
struct ComplexStruct {
    // Embedding Rust code in string literals is probably a bad idea, but
    // doing it here for conciseness.
    #[proptest(strategy = "parameters.string")]
    string: String,
    #[proptest(strategy = "0..parameters.int_max")]
    int: i64,
}

struct ComplexParms {
    string: &'static str,
    int_max: i64,
}

impl Default for ComplexParms {
    fn default() -> Self {
        ComplexParms {
            string: "[0-9]{4}",
            int_max: 42,
        }
    }
}

// Generated impl
impl Arbitrary for ComplexStruct {
    type Parameters = ComplexParms;
    type ValueTree = /* big type */;
    type Strategy = /* big type */;

    fn arbitrary(parameters: ()) -> Self::Strategy {
        (parameters.string, 0..parameters.int_max)
            .prop_map(|string, int| ComplexStruct { string, int })
    }
}

In any case, thanks for being willing to take a stab at this yourself. I look forward to seeing what you come up with!

I don't by any means disagree with this, but it would be nice to have some data for how often this applies in real code using things like Hypothesis/proptest.

I think it's not an all or nothing proposition - some types will be canonical, and some won't. For simpler types, I think this is more true, and since they are a pain point, it's nice to get rid of them.
In my use case, I have a lexer and parser I'm testing for read/show identity.

Maybe DefaultStrategy since the implementation essentially just provides a Strategy?

I think Arbitrary is better since it will be familiar to QuickCheck uses. In fact, proptests Strategy is more of a Gen of the original Haskell QuickCheck than the Gen of the quickcheck since it is also a monad and functor. So the potential Arbitrary of proptest is much more like arbitrary :: Arbitrary x => Gen x.

I can't say I particularly care for this; I think maintaining the clarity that a Strategy is just a normal value that can be passed around is important. Having two forms like that would also give an awkward speed-bump when needing to transition between them when there are multiple arguments.

I think stylistic choice is good here - I've so far added a function any which you can use as: any::<bool>() to be explicit about what values you want.

I'd also question how useful it is to do this for things like integers; I'm not sure how many cases there are where testing with literally arbitrary integers is useful. IIRC, quickcheck defaults to the range 0..100.

You can always use newtypes which is really a good idea if your data type really only handles a specific range - but sure, some types in the middle of deriving you'd want to customize it to use a different Strategy.

The rules don't take into account recursive types (e.g., En), which ideally would be handled in a way more graceful than aborting at runtime by overflowing the stack.

You could use sane defaults and allow depth and such to be customized with fields. Perhaps a LeafArbitrary type could be used when you only want an arbitrary value of the type but no recursion.

I think any custom derive would also need a way to override the strategy for a particular field, since the type will often have its own constraints on internal state. Something akin to #[serde(serialize_with = "..")] might work. This would also relieve that field of needing to be Arbitrary.

I agree completely. I thought of this a few hours ago but forgot to update the issue =) Tho, I'm not sure if it is currently possible to custom derive and have custom attributes as well in stable Rust - if not, perhaps it should be done when possible...?

IMO this is the single biggest weakness in proptest right now; the compiler can't help you if you forget a variant when defining the strategy.

Right =) This was the main impetus of this issue and the drive for the trait and custom derive proc macro.

Overall, this is something I feel reasonably positively about. My biggest concern is that Arbitrary is all-or-nothing, so the moment you need even a single parameter for constructing the strategy, you're back to what we have today. It would be nice if there were some way to pass parameters through and still use the code generation. [...]

That's a nice idea! I'll try this idea out and see how it works with type inference, etc. I think it should work out fine.

I think stylistic choice is good here - I've so far added a function any which you can use as: any::() to be explicit about what values you want.

That would be really useful! Currently I don't have a solid understanding of where to place strategies for my types, especially because I can't mirror prop::type::ANY pattern because my strategies are boxed. If, on the call site, I could write any::<u32> the same as any::<MyType>, then this question would become irrelevant, because the actual strategy would not be a part of public API.

@matklad =) I've done some initial work at the temporary crate proptest_arbitrary with implementations for most of the standard library (save for non-owned types which proptest doesn't support (yet)), but it's not tested yet or ready for prime time. But I'm working diligently on it atm ;)

Looks like I forgot to close this. This feature became available in 0.5.0.


Add support for federated authentication with provided access token when prelogin doesnt return preloginFEDAUTHREQUIRED

This situation occurs with AWS RDS Proxy for MS SQL server as an example but may occur elsewhere.
The solution is to bypass the error message if we are not going through an ADAL workflow.
This resolves #84

@microsoft-github-policy-service agree

thx for adding the example!

i repushed with go.{mod|sum} files so hopefully it passes integration tests.

I need to figure out why this test is unreliable. TestMessageQueueWithErrors


Request.

I do not know another way to message you.
I am working on creating a blender template for all the aircraft and would like to create a script that, once you are done editing you can run the script and everything will magically be done for you.
I would like to include either your code or application into this.
Figured I would reach out and ask permission., instead of just doing it.
Here is one of the templates I am working on.
Also will take any thoughts or feedback that you may have.

These templates are a great idea! Feel free to use the application or code, whichever you prefer.
I'm also on Reddit, Twitter, and Discord (#2596) with the same username if you need to contact me further.


Documentation Example - Nested form-inlines

Hello,
As a jr developer I relay heavily on your documentation for code examples. I would like to ask if you could create some examples on how to create forms like this where you have grouped form-groups inline.

Thanks for your consideration.

Cannot help you without a JS Bin to reproduce the problem.

Sure. So this is how I would create a form with several 'inline-form' http://codepen.io/imcodingideas/full/jVZjRe/ but I don't ever really know if I'm doing it the 'bootstrap way' as bootstraps documentation really teaches us how to use it the way its intended and I think some 'checkout' form or 'registration' form example would benefit a lot of people.

@imcodingideas Your example doesn't use .form-inline anywhere...
But generally speaking, to accomplish complex form layouts, using the grid system is The Right Way to do it.

I know it doesn't use .form-inline because it doesn't get padding/margin right. I'm not this great front end developer so like I said in my proposal that maybe an example registration form or checkout form would be beneficial for some developers.

@imcodingideas - You are looking for an example ( codepen ), so here you go
--> http://codepen.io/IamManchanda/pen/KNBgmo
But even i will also say that grid system is the right way to achieve form layouts.

I agree with others here that your best best is using the grid system. There's not much we'll do here to document this differently than our existing grid and form docs.


Does not open with strict HTTPS policies

Hi, I have tried to access your website with Brave Browser, which enforces strict HTTPS policies.
And it does not work for users with this feature on.
That's what it says: ERR_SSL_PROTOCOL_ERROR

https gives some protection over personal data. since this app does not require any sort of login or user inputs you can use it without having a https connection on google chrome or firefox. i will configure it with a ssl certificate.

You can use HTTP http://www.githubstats.com and HTTPS on https://githubstats-com.herokuapp.com/


vscode rust devcontainer: cargo build resulting in "failed to link or copy

Problem
Im not sure if should be reaching out here or vscode for help on this...but i will start here and let  me know if im int he wrong location..
i have built a vs code devcontainer based on mcr.microsoft.com/devcontainers/rust:1-1-bullseye, running under Docker Desktop on windows 11.  I am able to run a basic example using this without any dependencies
i have the following structure (Note: the target and Cargo.lock do not exist until after i attempt a cargo build:

My toml looks like this:
[package]
name = "aipg_client"
version = "0.1.0"
edition = "2021"

#[dependencies]
#tokio-postgres = "0.7.10"

when i do Cargo build or run from command line, i see this:
vscode ➜ /workspaces/aipg_client $ cargo clean
     Removed 19 files, 3.7MiB total
vscode ➜ /workspaces/aipg_client $ cargo build
   Compiling aipg_client v0.1.0 (/workspaces/aipg_client)
warning: error copying object file `/workspaces/aipg_client/target/debug/deps/aipg_client-29a466bd116893b1.2wavitxjlghb5boo.rcgu.o` to incremental directory as `/workspaces/aipg_client/target/debug/incremental/aipg_client-cn2ostj37iq8/s-gw2y4x6qjv-d1xpw0-working/2wavitxjlghb5boo.o`: Operation not permitted (os error 1)

warning: error copying object file `/workspaces/aipg_client/target/debug/deps/aipg_client-29a466bd116893b1.340xt2kclbcozwj5.rcgu.o` to incremental directory as `/workspaces/aipg_client/target/debug/incremental/aipg_client-cn2ostj37iq8/s-gw2y4x6qjv-d1xpw0-working/340xt2kclbcozwj5.o`: Operation not permitted (os error 1)

warning: error copying object file `/workspaces/aipg_client/target/debug/deps/aipg_client-29a466bd116893b1.3nlg3iffbximniu8.rcgu.o` to incremental directory as `/workspaces/aipg_client/target/debug/incremental/aipg_client-cn2ostj37iq8/s-gw2y4x6qjv-d1xpw0-working/3nlg3iffbximniu8.o`: Operation not permitted (os error 1)

warning: error copying object file `/workspaces/aipg_client/target/debug/deps/aipg_client-29a466bd116893b1.57xak5150to06626.rcgu.o` to incremental directory as `/workspaces/aipg_client/target/debug/incremental/aipg_client-cn2ostj37iq8/s-gw2y4x6qjv-d1xpw0-working/57xak5150to06626.o`: Operation not permitted (os error 1)

warning: error copying object file `/workspaces/aipg_client/target/debug/deps/aipg_client-29a466bd116893b1.ele9p2lo4vgyfma.rcgu.o` to incremental directory as `/workspaces/aipg_client/target/debug/incremental/aipg_client-cn2ostj37iq8/s-gw2y4x6qjv-d1xpw0-working/ele9p2lo4vgyfma.o`: Operation not permitted (os error 1)

warning: error copying object file `/workspaces/aipg_client/target/debug/deps/aipg_client-29a466bd116893b1.eyyxtxgek58rknf.rcgu.o` to incremental directory as `/workspaces/aipg_client/target/debug/incremental/aipg_client-cn2ostj37iq8/s-gw2y4x6qjv-d1xpw0-working/eyyxtxgek58rknf.o`: Operation not permitted (os error 1)

warning: `aipg_client` (bin "aipg_client") generated 6 warnings
error: failed to link or copy `/workspaces/aipg_client/target/debug/deps/aipg_client-29a466bd116893b1` to `/workspaces/aipg_client/target/debug/aipg_client`

Caused by:
  Operation not permitted (os error 1)

i checked these folders and they are all r/w.
What am i doing wrong?
Steps

Create a vscode dev container:  CTRL+SHIFT+P -> devcontainer:new -> rust
Note: i jused a Dockerfile + Docker Compose along with .devcontainer.json. but the issue is reproducible with just a .devcontainer.json file
Install rust analyzer extension in the container
run cargo build twice

Possible Solution(s)
I dont know yet
Notes
No response
Version
rustc 1.78.0 (9b00956e5 2024-04-29)
cargo 1.78.0 (54d8815d0 2024-03-26)
rustc 1.78.0 (9b00956e5 2024-04-29)
vscode ➜ /workspaces/aipg_client $ cat /etc/debian_version
11.9
docker desktop v4.29.0
No response

Could you fill in each section of the issue template? A clear minimal reproducible example helps debugging. Also, please provide the output of cargo -vV which is the version info.

though i dont know if its relevant here i are my docker file and docker-compose:
docker file:
FROM mcr.microsoft.com/devcontainers/rust:1-1-bullseye as aipg_client_base
ENV TZ=America/New_York

ARG ENV
ARG USER_ID
ARG GROUP_ID
ARG USER_NAME
ARG APP_HOME="/apps/aipg_client_base"
RUN echo "env: $ENV, user: $USER_NAME, user_id: $USER_ID, app_home: $APP_HOME"

RUN apt-get update && apt-get -y install acl iputils-ping less libpq-dev nano postgresql-client sudo

RUN groupadd -g $GROUP_ID -o $USER_NAME
RUN useradd -m -s /bin/bash -u $USER_ID -g $GROUP_ID $USER_NAME

FROM aipg_client_base as aipg_client_local

#attempt at handling this target folder issue...
RUN mkdir -p /workspaces/aipg_client/target
RUN chown -R vscode:vscode /workspaces/aipg_client/target
RUN chmod -R 777 /workspaces/aipg_client/target

docker-compose:
networks:
  aipg_client_net:
    driver: bridge

services:
  aipg_client:
    container_name: aipg_client_${ENV}
    image: "aipg_client:${VERSION}"
    build:
      context: ..
      dockerfile: .devcontainer/Dockerfile
      target: aipg_client_local
      args:
        ENV: ${ENV:-local}
        USER_ID: ${USER_ID:-1000}
        GROUP_ID: ${GROUP_ID:-1000}
        USER_NAME: ${USER_NAME}
      shm_size: '2gb'
    env_file:
      - ./.env
    volumes:
      - ../..:/workspaces
      - ~/.ssh:/home/${USER_NAME}/.ssh
      - //var/run/docker.sock:/var/run/docker.sock
    command: sleep infinity
    shm_size: 0.94gb
    ports:
      - "${SVC_PORT}:5000"
    networks:
      - aipg_client_net

.env file:
VERSION=local
ENV=local
USER_ID=197609
#USER_ID=1001
GROUP_ID=1000
USER_NAME=user1
SVC_PORT=6000

Could you fill in each section of the issue template? A clear minimal reproducible example helps debugging. Also, please provide the output of cargo -vV which is the version info.

done..let me know what else is needed. ive also added the dockerfile and docker-compose file im using.

As per this discussion: https://stackoverflow.com/questions/72448053/rust-incremental-build-not-working-in-vscode-devcontainer
if i add a .cargo/config.toml with the target anywhere outside my project workspace, it seems to work fine
[build]
target-dir = "/tmp/target"

But why?

Anyone with any advice on how to go about resolving this?

As per this discussion: https://stackoverflow.com/questions/72448053/rust-incremental-build-not-working-in-vscode-devcontainer
if i add a .cargo/config.toml with the target anywhere outside my project workspace, it seems to work fine
[build]
target-dir = "/tmp/target"

But why? this of course isn't helpful given that that path outside the workspace is ephemeral storage

I had the same problem and I thought it was the problem of build dependencies until I saw this post.
It did resolve my issue too...
I am also very curious about what caused this.


Pin project dependencies during hatch build

I have done a diff on the wheel from 1.2.0 as as built by this branch. I have noticed some minor difference we should discuss tomorrow, but essentially this looks good as far as I can tell. So it seems like we could reasonably move forward with this approach. In that spirit, I'm now leaving some fine-grained comments on the PR so this improvement can stand the test of time.

So as far as I can tell this looks great, modulo some minor feedback. Some reflections. I think this means the pyproject.toml for the tagged release in github will vary from what's used to make 'METADATA' in the wheel. So if you were installing from a tagged github release (for some reason) you could get different versions to an sdist or wheel install from pypi. I find it hard to imagine that this would actually matter, but maybe it should be thought about a little. Thank you so much for identifying this approach and putting up this PR, I wouldn't have known how to do this without a lot of painstaking research.

I will also undertake some additional manual testing tomorrow.


kic: add Gateway API HTTPRoute traffic splitting

Summary
This adds info about traffic splitting using Gateway API HTTPRoute.
This PR also makes the "Using Gateway API" page only visible in KIC versions >= 2.2.x since that's the version that initial implementation was released in: https://github.com/Kong/kubernetes-ingress-controller/blob/main/CHANGELOG.md#220
Reason
#4157

Thanks @cloudjumpercat for the review 🙇
Do you have any feedback on using the URLs to examples? I've raised this in slack already: https://kongstrong.slack.com/archives/CDSTDSG9J/p1666947640410469?thread_ts=1666777758.809319&cid=CDSTDSG9J and I'm worries this is not ideal experience to get 404s locally and in PRs for code that hasn't reached docs.konghq.com

Do you have any feedback on using the URLs to examples? I've raised this in slack already: https://kongstrong.slack.com/archives/CDSTDSG9J/p1666947640410469?thread_ts=1666777758.809319&cid=CDSTDSG9J and I'm worries this is not ideal experience to get 404s locally and in PRs for code that hasn't reached docs.konghq.com

@pmalek Hmmm, good question. This is a bit out of my area, but @fabianrbz might know.


Issue75 rebased

This change is

I was able to test and run different tier ratios, the code changes look good.

@byrnedj could you please look one more time? I fixed one failing test (took a little bit different approach to calculating ratios: reverted to how Victoria did it on her PR), just rebased to upstream patch


Some images not rendering on Mattermost servers using subpath

This issue was originally brought up in https://github.com/mattermost/mattermost-server/issues/19656. Some plugins, including this plugin, may need to be updated to support servers hosted on a subpath.
Making sure we take into account the server's SiteURL will make sure we use the correct path. Please see this PR for a similar fix https://github.com/mattermost/mattermost-plugin-github/pull/459

Thanks for the report.
The linked PR is not wholly pertinent, as it's frontend and the Gif plugin is completely on the backend side.
I'm having trouble reproducing the issue - I'm not familiar with Nginx and I think I messed up my configuration with docker/docker-compose (which I use to start Ngxinx+Mattermost-preview) because I can't even load the plugin package via the redirected url, only with the direct localhost:8065 url.
I think the fix would be to replace https://github.com/moussetc/mattermost-plugin-giphy/blob/a81cdfc0202ab66427976652fb163a2b1bf37939/server/plugin.go#L44
by
        rootURL := ""
	if siteURL := p.API.GetConfig().ServiceSettings.SiteURL; siteURL != nil {
		rootURL = strings.TrimSuffix(*siteURL, "/")
	}
	p.rootURL = fmt.Sprintf("%s/plugins/%s", rootURL, manifest.Manifest.Id)

but I can't test it...

@moussetc What's more important than using nginx for testing here is using Mattermost with a subpath https://developers.mattermost.com/blog/subpath/#using-subpaths-in-development. That should be enough to test the issue.

@mickmister  Thank you for the link. However I don't use the mattermost-webapp repo to test my plugins, I use the Mattermost Docker preview image, which is why I was trying to go the docker/nginx route. I honestly don't have the motivation to setup the actual Mattermost developer environment (I tried a few years back, lost more than a few hours, didn't manage to get it working and ended up choosing the Docker Preview).
I'll be releasing a new version of the plugin at some point in the future, which will contain the suggested fix above, and hopefully, it'll solve the issue.
Note: seeing as the previous version 2.1.1 is still stuck waiting for review for the official Marketplace publication, I'm not sure that this fix (if it works) will ever get publishedto the Marketplace ,so watch out for Github releases.

The new 2.1.2 release  of the plugin now uses the SiteURL setting when generating the Giphy attribution picture URL (all other URLs handled by the plugin are Giphy URLs, not impacted by this setting).


ChoicesByURL not working in drop-downs within MatrixDynamic questions from release 0.12.6 onwards

Are you requesting a feature, reporting a bug or ask a question?
Reporting a bug.
What is the current behaviour?
When the drop-down is hooked up to a working URL (via Choices from Web) that returns the following JSON results, the drop down list is initially filled with the correct items, I choose one of the items and the drop-down field is blanked out (my choice is gone), if I then add another row and try and choose another item from the drop-down list, the list contains nothing...
Here is the JSON being returned to the drop-down from the API:
{   "results": [     {       "id": "1",       "value": "Site 1"     },     {       "id": "2",       "value": "Site 2"     },     {       "id": "3",       "value": "Site 3"     }   ] }
And here is the JSON config of the question (API URL replaced to protect the innocent):
{ 	type: "matrixdynamic", 	addRowText: "Add site", 	columns: [ 		{ 			name: "site", 			title: "Site", 			cellType: "dropdown", 			choicesByUrl: { 				url: "<<API URL>>", 				path: "results", 				valueName: "id", 				titleName: "value" 			} 		} 	], 	indent: 1, 	isRequired: true, 	name: "question-site", 	removeRowText: "Remove site", 	rowCount: "0", 	title: "Which sites?" }
What is the expected behaviour?
The drop-down should list the items from the JSON and when I choose one of the items it should be shown in the drop-down field.
How would you reproduce the current behaviour (if this is a bug)?
Running my application and referring to the survey CDN for release 0.12.5 produces a correctly behaving drop-down list, if I increase the CDN version the bug presents itself.
Provide the test code and the tested page URL (if applicable)
Difficult to provide the URL as the API is running locally inside my organisation.
Specify your

browser: Chrome
browser version: 57.0.2987.133 (64-bit)
surveyjs platform (angular or react or jquery or knockout or vue): jquery
surveyjs version: 0.12.6 onward

I have also now tested this using the URL "http://services.groupkt.com/country/get/all" from the "Dropdown + restfull" example and it doesn't work either when the dropdown is inside a MatrixDynamic question.
However, a question that is just a Dropdown question type, works fine.
The problem seems to be related to the dropdown when it is part of a MatrixDynamic question type since release 0.12.6.

@bjdani There is another issue. When we are using restful API for matrix dropdown, we send a lot of requests to the server. The requests are the same. We should cache the result during a survey running.
Thank you,
Andrew

@bjdani I have fixed the issue. Adding the cache on restful requests fix the issue.
Thank you,
Andrew

Nice timing, I just bumped into the same issue. What is the quickest way to get the fix?; I am now running https://surveyjs.azureedge.net/0.12.9/survey.jquery.min.js.

@gnimmelf I have updated the dev build.
You may use https://surveyjs.azureedge.net/dev/survey.jquery.min.js for a while.
Thank you,
Andrew

Thank you Andrew for quickly addressing this issue. I can confirm that it is working for me when I use the dev build. Any estimate on when 0.12.12 will be released?
Thanks again,
Bruce

@bjdani We've scheduled the next minor on May 2 or May 3.
Thank you,
Andrew

Thanks again Andrew!


Balloon Deployer

I want to do a save with Balloon deployer, but everytime when im loading a save, balloon deployer just disapear and showing me error.
1.Spawn Balloon deployer
2.Save map
3.Load map
3.Balloon Deployer disapear
[Wiremod] lua/entities/sent_deployableballoons.lua:46: attempt to index local 'pl' (a nil value)

CreateEntityFromTable - lua/entities/sent_deployableballoons.lua:46
unknown - lua/includes/modules/duplicator.lua:720
3. ProtectedCall - [C]:-1
4. Paste - lua/includes/modules/duplicator.lua:720
5. unknown - lua/includes/gmsave.lua:58

plz fix it i really need this

I was able to reproduce the error.
A bit more detailed steps for repro:

Start new game.
Spawn a Wire Balloon Deployer (Using Spawn menu, assuming default key-bindings: Hold down Q key, go to Entities tab, choose Wiremod category and click on Wire Balloon Deployer. Or by using console command: gm_spawnsent sent_deployableballoons;).
Save current game (Using Spawn menu, assuming default key-bindings: Hold down Q key, go to Saves tab, click Save Game under My Saves category. Or by using console command: save "savegame_name_here".)
Clean up everything (or undo or restart game).
Load the saved game (Using Spawn menu, assuming default key-bindings: Hold down Q key, go to Saves tab, click Load on the saved game under My Saves category. Or by using console command: load "savegame_name_here".)

Causes a server-side error with stack-trace:
[ERROR] addons/wire/lua/entities/sent_deployableballoons.lua:46: attempt to index local 'pl' (a nil value)
  1. CreateEntityFromTable - addons/wire/lua/entities/sent_deployableballoons.lua:46
   2. unknown - lua/includes/modules/duplicator.lua:720
    3. ProtectedCall - [C]:-1
     4. Paste - lua/includes/modules/duplicator.lua:720
      5. unknown - lua/includes/gmsave.lua:58


unable to map type JSON() to metadata schema

Describe the bug
JSON datatype causing ingestion error.
To Reproduce
Steps to reproduce the behavior:

Ingest mysql 8.0 table with json() column
See error in ingestion logs
also see unknown type in metadata view within datahub front end.

Expected behavior
JSON datatypes should be first class citizens in schemas.
'dev_db_3gtbpq.User': ['unable to map type JSON() to metadata schema'],
              'dev_db_3gtbpq.audit': ['unable to map type JSON() to metadata schema'],
              'dev_db_3gtbpq.facility': ['unable to map type JSON() to metadata schema'],

Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Thanks for reporting ! Agree this is a bug we should address in ingestion. @shirshanka @chinmay-bhat


New "autolinked community module" sample (react-native-camera is being deprecated)

Suggestion
Right now, we use react-native-camera in the CameraDemo sample to verify that autolinking of a community module works, however it looks like that module might not be worked on in the future.
Specifically, it looks like react-native-camera is is being deprecated for react-native-vision-camera: https://github.com/react-native-camera/react-native-camera/issues/2942
Since the new react-native-vision-camera doesn't have (and might not get) RNW support, we may want an entirely new sample to test this scenario.
Platforms
Windows
Sample code
No response

We would need to find another module that we can rely on as a good example of autolinking working across versions.


Handling bid/ask (and so spread) with BarEvent

Hello,
When backtesting with only bar data, price handler put BarEvent into event queue.
Here are some properties of a BarEvent
- ticker
- time
- period
- open_price
- high_price
- low_price
- close_price
- volume
- adj_close_price

Backtesting using bar data can be useful with CFD (or any other derivatives) with bid/ask price (and so spread).
Metatrader 4, for example, display candle of bid price (but an optional ask line can be drawn).
http://www.metatrader4.com/fr/trading-platform/help/setup/setup_charts
Historical data only have bid price and backtest assume fixed spread ( http://www.forexfactory.com/showthread.php?p=5082986 )
I wonder how we can handle this nicely ?
Kind regards

Might depend a little bit on what the proposed "out-of-box" (presuming IB) historic data provider gives?

This is probably indicative of a wider conversation on transaction cost handling. I myself will be utilising specific models for transaction costs in order to test strategy sensitivity to various costs.
Once we have gitter/Slack we can have a good chat about it!

A strategy might be aware of spread (especially when it's not equal to 0).
For example your strategy can enter only when spread is low (and never enter when spread is high)


Fix fake backend not to use deprecated arguments in NoiseModel construction

Summary
Update fake backend not to use deprecated arguments, standard_gates and warnings, in the construction of a noise model for simulation.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 85.279%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
67252

Relevant Lines:
78861

💛  - Coveralls


Fix AWS event mappings

https://bugzilla.redhat.com/show_bug.cgi?id=1207865

Quoted from GM's comment in the BZ:

This is because when this event is received from the provider the VM object does not exist yet in our database and there is no object to raise the event against.  Instead we raise the vm_create event as part of the post-creation processing for VM objects.