VSCode suggests downloading unusuable version (x64 on non-x64 machine)

Issue Type: Bug

Download and install VSCode x86-32 on an ARM64 machine (Asus NovaGo, HP Envy x2, Lenovo Yoga C630, etc.)
Run VSCode.
Note the following message:

The link on the word "here" leads to: https://code.visualstudio.com/updates/v1_15#_windows-64-bit
The downloads there are x86-64 however rather than ARM64. This message is wrong or at least very misleading. Please remove it.
You don't yet support ARM64 as requested in #33620? Fine. (Actually not so fine since it seems to be possible now that much work on Chromium and Electron ARM64 has been done. See: https://github.com/ljsabc/Code-OSS-Win32-arm64)
But before telling me to go and download another version, please make sure it can actually run on my machine. Instead of just checking bitness, check the platform too. See the IsWow64Process2 function (in contrast with IsWow64Process) for example.
When you finally support ARM64 you could bring the message back, and point the link to the correct (future) blog post.
VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:35:35.387Z)
OS version: Windows_NT ia32 10.0.18990

System Info

Item
Value

CPUs
Snapdragon(TM) 835 (8 x 1555)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: unavailable_offprotected_video_decode: unavailable_offrasterization: unavailable_offskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
5.68GB (0.67GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:
Support ARM64 build for Windows (#33620)

Experiment failed.

Verification: just code review, everything was removed


Support Generics style PHPDoc @return typing

When returning a Collection, you can annotate the @return type like:
/**
 * @return Article[]
 */
#[GraphQLite\Field]
public function getArticles(): Collection;

However, this doesn't tell many static analyzers that the return type is a Collection.  Maybe some smarter analyzers will check the actual return type, if typed, and use both combined.  I'm unsure about that.  But, there is value in using the Generics syntax for those that don't.
/**
 * @return Collection<Article>
 */
#[GraphQLite\Field]
public function getArticles(): Collection;

This syntax is quickly becoming somewhat of a standard at this point.  It's supported by Psalm, Phan, PHPStan and I'm sure others.  It was implemented by PHPStorm.
Many of you are probably familiar with this syntax and probably use it.  For compatibility reasons, we should support both of these syntaxes when evaluating an @return annotation for the sake of generating GraphQL Types.  Currently, an error is thrown as it tries to create a Type definition out of Collection

wouldn't #321 fix this?

@Lappihuan yes, probably so - we need tests there to confirm.

Generics support was added with #468 and released with version 6.0


[Defect] Help - Load Keyboard : sections of types of keyboard does not change translation with locale change

Fixed


Sof 1571/deleteRundown Expose Endpoint to Delete Rundown

Creating the PR, so people can begin to see which changes i have made.
Going to hold of on settings it to a full on review, until after #254 has been merged, and last few tests have been created/run.
My reasoning behind this is, that i want/need to make some tests for the MongoRundownRepository, which @RasmusAlbrektsen  has added a package to help test, that i want to use.
I could chose to add the same package myself, but might end up causing merge conflics, so waiting abit to avoid that, isn't going to be the end of the world.

Codecov Report

Merging #255 (9ac31c8) into Q3RefactorDemo (afcc78f) will increase coverage by 6.86%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@                Coverage Diff                 @@
##           Q3RefactorDemo     #255      +/-   ##
==================================================
+ Coverage           68.17%   75.04%   +6.86%
==================================================
  Files                 288       23     -265
  Lines               34336     4968   -29368
  Branches             4718      492    -4226
==================================================
- Hits                23410     3728   -19682
+ Misses              10448     1238    -9210
+ Partials              478        2     -476

see 267 files with indirect coverage changes

Ready for Review.
I have added a handfull of TODO comments, some i'd like to possibly do in this PR, but need to learn some more about how the MongoDB driver works to do. Any input/help on these is very welcome.
There are also some that mention pulling out pieces of code to a file under model layer for reuse accross tests, which are waiting on the file created for this by Lindved.


Adding to suppression definition

added a bit more about what a suppression does at the beginning
Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @lweinig,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Support for environment variables substitution

Now user can put environment variables in docker-compose file and it will be read by kompose from environment
Fixes #56

The code in this PR is from https://github.com/docker/libcompose/blob/master/docker/project.go#L25
So I needed some discussion around this PR, so I checked the code in kompose here, it is similar to code in libcompose here. So I was hoping we can use the function NewProject from libcompose which is under docker package not under project package.
So the downside of using docker package's NewProject is it returns project.APIProject and I would like to have a method in project.APIProject that returns internal data structure of type *Project and we don't need to repeat the code. So I will be working with libcompose to get this done. If that works out this PR will change!

@surajssd I see you are changing libcompose code in /vendor. Is it possible to just work on kompose code base and keep libcompose as a dependency ?

@ngtuna I did godep save to get latest code from libcompose. Is it not the right way to do it?

@surajssd Ah okay you changed libcompose revision to HEAD. OK let me check it.

@ngtuna @kadel How can I convert a APIProject interface object type to Project type? Is there a way to do it?

@surajssd  The reason I didn't use NewProject function because I don't want kompose to be constrained by libcompose. Basically we only need its parsing function in order to parse docker compose file into komposeObject, nothing more. Otherwise, we have to follow libcompose's constraints such as it's required to have a docker-compose.yml file handy at the same folder.
Did you check whether your changes in cli/app/app.go still works with the current libcompose revision at HEAD master? If yes then I suggest to keep the vendoring stable and just apply your changes in app.go. I can't check it now but will do tomorrow morning.

@ngtuna I checked with the vendored libcompose available I am not able to build, because I need https://github.com/skippbox/kompose/pull/67/files#diff-41d801ef80f1858d5e8e9695667e4dafR749 and it is not in the vendored libcompose

Checked! Thanks @surajssd . Please go ahead to merge upstream.

@ngtuna thank you :)


elasticsearch::plugin proxy_host, and proxy_port have no effect

Module version: 0.13.2
Puppet version: 4.6.2
OS and version: CentOS 7

Bug description
elasticsearch::plugin proxy_host, and proxy_port have no effect because the elasticsearch plugin wrapper (/usr/share/elasticsearch/bin/plugin) doesn't use the ES_JAVA_OPTS environment variable

Duplicate of #695, fixed in #717, fix will go out in the next release.


[Bug]: change the calculation of: - Amount (17) in G/L Entry (17)  - Base (8) and Amount (9) in VAT Entry (254)  when posting an invoice in foreign currency.

Describe the issue
When posting a sales invoice in a foreign currency, the G/L Entry are created:
to the G/L account specified in General Posting Setup (252) - in field Sales Account (10) - the VAT base amount is calculated in the LCY
to the account specified in VAT Posting Setup (325) - in field Sales VAT Account (7) - the VAT amount is calculated in the LCY
+
VAT Entry (254) is created, in which Base (8)= the VAT base amount is calculated in the LCY and Amount (9)=the VAT amount is calculated in the LCY
Expected behavior
Current:
The VAT base amount in the LCY is calculated as the VAT base amount in foreign currency multiplied by the exchange rate
The VAT amount in LCY is calculated as the difference between the (Amount Including VAT - Amount Excluding VAT) multiplied by the exchange rate
Should be:
The VAT base amount in the LCY should be calculated as Amount Including VAT (LCY)/ (1+VAT%/100)
The VAT amount in LCY should be calculated as Amount Including VAT (LCY) - Amount Excluding VAT (LCY)
Additional context
This is necessary to because in some cases the amount of the calculated VAT base amount (LCY) + VAT amount (LCY) is not equal to the Amount Including VAT(LCY), also the Amount Excluding VAT (LCY)* VAT%/100 is NOT equal to the VAT amount (LCY).
Steps to reproduce
When posting a sales invoice in a foreign currency, the G/L Entry are created:
to the G/L account specified in General Posting Setup (252) - in field Sales Account (10) - the VAT base amount is calculated in the LCY
to the account specified in VAT Posting Setup (325) - in field Sales VAT Account (7) - the VAT amount is calculated in the LCY
+
VAT Entry (254) is created, in which Base (8)= the VAT base amount is calculated in the LCY and Amount (9)=the VAT amount is calculated in the LCY
Additional context
For example
Amount Excluding VAT= 1573,11
VAT%=20%
Amount Including VAT=1887,73
VAT amount=314,62
exchange rate=42,2079
Now we receive on the posting
Amount Excluding VAT(LCY)= 1573,1142,2079=66397,67
Amount Including VAT(LCY)=1887,7342,2079= 79677,12
VAT amount(LCY)=314,62*42,2079=13279,45
but it should be
Amount Excluding VAT(LCY)=79677,12/(1+20/100)=66397,6
VAT amount(LCY)=79677,12-66397,6=13279,52
I will provide a fix for a bug

[ ] I will provide a fix for a bug

Probably, it is not a bug. Every legislation has a different way to calculate VAT. This standard calculation is from W1, I asume.
You did not specified a country version of BC which you expect the behaviour for.

Also, this isn't an issue related to extensibility. If you'd like to create a support request, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using. Here's a link to Collaborate: https://developer.microsoft.com/en-us/dashboard/collaborate/engagements/1173/feedback/wits/Bugs/create.


Unable to read csv if a row has empty columns

Describe the bug
I have installed csv-parse version: 4.8.5
Unable to read csv if a row has empty columns, throwing below exception
CODE: "CSV_RECORD_DONT_MATCH_COLUMNS_LENGTH"
message: "Invalid Record Length: columns length is 12, got 10 on line 4"
To Reproduce
Upload a csv which has 12 columns. Provide data for each cell in first 2 data rows, and leave last two columns of last (3rd) row empty. Hope below attachment would help in reproduce the issue.
upload_file_col.zip

Same comment as #277, please, provide a minimal example with a minimal dataset, no zip file.

Hi @wdavidw
Please find the details below to reproduce the issue
Code that throwing an exception
/* csv upload. */
router.post('/import', upload.single('csv'), upload.single('csv'), function (req, res, next) {
try {
console.log('importing document..')
const buffer = req.file.buffer;
const options = {
columns: true
};
let parser = CSVParse(buffer, options);
} catch (err) {
//throw err;
res.status(500).send({
errInfo: err,
mssage: err.message
});
}
});
Exception message

Find the attachment which has example application and a csv file uploaded.
req_data.zip
I hope this information helps you in reproducing the issue

See my comment in #277

@madhav-vl have you read about the relax_column_count option?

Closing, no answer being provided to the last question.


Ensure log writes only to os.Stderr for env and config command

This fixes some issue where if you run eval $(docker-machine env default) and it needs to regenerate the certs it was dumping output to STDOUT and messing up the subshell
cc @jeffdm FYI
Signed-off-by: Nathan LeClaire<EMAIL_ADDRESS>

LGTM


image_picker shows an html input file button on web browser

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Easy to reproduce:

Download the repository where I reproduced the bug ( https://github.com/sebat94/flutter_image_picker_bug )
Once the application is started, select an image by clicking the grey circle and then click on the link below that navigates to the next page.
On the next page you will see the bug.

I am debugging my flutter app with chrome version: '<IP_ADDRESS>'
Note: This bug was reported some time ago but was not resolved due to lack of evidence. ( 109782 )
Expected results
You will see an html input file

Actual results
When I select an image and redirect to a new page, an html input file appears on the new page.
I also tried a "pushReplacement"  just in case removing the previous Page from the stack made any difference, but that didn't work either.
Interesting fact: The input file appears in my web browser but does not exist in my widget tree.

Code sample
https://github.com/sebat94/flutter_image_picker_bug
Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/15348083/70b3683c-ddbc-4e0d-9abc-40ac7901ddb3

Logs
No response
Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.13.8, on Microsoft Windows [Versi¢n 10.0.22621.2715], locale es-ES)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.7.5)
[√] Android Studio (version 2022.3)
[√] VS Code (version 1.84.2)
[√] Connected device (3 available)
[√] Network resources

• No issues found!

The image picker package creates the file input but never removes it (see here if anyone is interested in tackling this 🙂)

I see that the issue has been closed but the release couldn't be done due to an error on the tests.
Can you take a look at it? @Amir-P @ditman @mdebbar
Thank you for your outstanding work, much appreciated.

the release couldn't be done due to an error on the tests.

@sebat94 it got released a few hours later! thanks for letting us know! https://pub.dev/packages/image_picker_for_web/changelog#302

the release couldn't be done due to an error on the tests.

@sebat94 it got released a few hours later! thanks for letting us know! https://pub.dev/packages/image_picker_for_web/changelog#302

Just one last question @ditman ,
will this fix be mirrored into the "image_picker" package?
I see that you provided that functionality some time ago:

It would be great to have this fix mirrored also in the "image_picker" package so we don't need to switch between the "image_picker" package and the "image_picker_for_web" package if our app can run in both, mobile and web environments.
Thanks.

@sebat94 image_picker depends on image_picker_web. You should get the fix without any changes on your end. Just remember to do a flutter pub upgrade to ensure that you get the latest version of image_picker_web!

@sebat94 image_picker depends on image_picker_web. You should get the fix without any changes on your end. Just remember to do a flutter pub upgrade to ensure that you get the latest version of image_picker_web!

Brilliant! Thanks for clarifying it for me.
Works like a charm 🔥
Thank you for your efforts and keep up the good work!

You're welcome @sebat94! Also, thanks for your contribution, keep them coming!! 🙏


fix(routes/config.js): fix error text noticed in testing

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

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


Investigate scarb cairo-run issues related to gas handling

See this conversation: https://discord.com/channels/793094838509764618/1123235645083631626/1131497581147607092

To summarize the conversation:
While using this repository, an error was encountered when running the command scarb cairo-run --available-gas<PHONE_NUMBER>9999999 to perform inference. The error message returned was:
mnist_nn % scarb cairo-run --available-gas<PHONE_NUMBER>9999999
running mnist_nn ...
Error: Failed calculating gas usage, it is likely a call for `gas::withdraw_gas` is missing.
error: process did not exit successfully: exit status: 1

However, when not using scarb and directly running cairo-run . --available-gas<PHONE_NUMBER>9999999, the operation works as expected. This scenario requires all the code from dependencies to be located in the same directory as it is not using scarb here.

Awesome, thanks @maciektr 🙏

Closing as superseded by #510


ARROW-16110: [C++] GcsFileSystem::Make ignores IOContext

This is to resolve ARROW-16110.

LGTM

Yeah, nice catch.

CI issues seem unrelated.


Docs: Fix the broken link for Appium NuGet

Fix the broken link for Appium NuGet

Thanks for correcting the link!


DASHBUILDE-70: Incorrect text alignment in data set configuration wizard

Notice this PR only contains UI tweaks so unit tests does not apply in this case.

+1

Thanks.
master: 8287fd70362c0c9e7de8c4a10e8ea2a1ce13d307


Joining between a GroupBy and a Select translates to inefficient SQL

Query:
            var results = (from o in db.Orders
                           group o by o.CustomerID into g
                           join c in db.Customers on g.Key equals c.ID
                           select new
                           {
                               CustomerID = c.ID,
                               Count = g.Count(),
                           }).ToList();

SQL:
SELECT
[Distinct1].[CustomerID] AS [CustomerID],
[Extent2].[ID] AS [ID],
(SELECT
    COUNT(1) AS [A1]
    FROM [dbo].[Orders] AS [Extent3]
    WHERE [Distinct1].[CustomerID] = [Extent3].[CustomerID]) AS [C1]
FROM   (SELECT DISTINCT
    [Extent1].[CustomerID] AS [CustomerID]
    FROM [dbo].[Orders] AS [Extent1] ) AS [Distinct1]
INNER JOIN [dbo].[Customers] AS [Extent2] ON [Distinct1].[CustomerID] = [Extent2].[ID]

Model:
public class Customer
{
    public int ID { get; set; }
    public string Name { get; set; }
    public bool? HasFreeShipping { get; set; }

    public virtual IList<Order> Orders { get; set; }
}

public class Order
{
    public int ID { get; set; }
    public int CustomerID { get; set; }
    public Customer Customer { get; set; }
    public DateTime CreateDateTime { get; set; }
}

Note, that the GroupBy is being computed twice: Once from the real GroupBy that's in the query and then as a computed subquery column. This seems unnecessary. EF seems to be unable to move the aggregation in the Select back into the GROUP BY.
The following test case reproduces this as well:
            var results = (from o in db.Orders
                           group o by o.CustomerID into g
                           let someVal = g.Key + 1 //unused column
                           select new
                           {
                               CustomerID = g.Key,
                               Count = g.Count(),
                               someVal //you can comment this in or out. fails both times
                           }).ToList();

SELECT
[Distinct1].[CustomerID] AS [CustomerID],
(SELECT
    COUNT(1) AS [A1]
    FROM [dbo].[Orders] AS [Extent2]
    WHERE [Distinct1].[CustomerID] = [Extent2].[CustomerID]) AS [C1]
FROM ( SELECT DISTINCT
    [Extent1].[CustomerID] AS [CustomerID]
    FROM [dbo].[Orders] AS [Extent1]
)  AS [Distinct1]

This seems like a significant problem because failing to move all aggregations into the GROUP BY can lead to exploding query runtime.

Hey,
This issue relates to EF6, which is managed in a separate repo (currently on CodePlex, but we are considering moving it to GitHub). We have taken a note on #2341 to consider this scenario and the SQL you suggested when we work on GroupBy translation in EF7.
Regarding this scenario in EF6, give that we are going to improve this in EF7 and the relative complexity/risk of adjusting the query pipeline in EF6 we aren't planning to address this in EF6. We would consider accepting a pull request though if someone outside our team wanted to contribute the change.
~Rowan


Darren Dashboards

Uploaded dashbaords

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

Thanks @WarHouseAngel
Two commments

Can you change the directory names to remove the space, and replace it with a "-"
Can you remove the .DS_Store files?

Thanks @kidk updated the request

Gracias @WarHouseAngel


IPv6 support

EC2 will soon support IPv6! We should make oversight.garden support IPv6 when support hits us-east-1. (watch https://console.aws.amazon.com/vpc/home?region=us-east-1#vpcs:)

[ ] Assign IPv6 CIDR block to VPC
[ ] Make sure official Ubuntu AMIs are dual-stack
[ ] Update aws-sdk Ruby gem (v2.6.31 or newer)
[ ] Update AWS rake tasks to set AAAA DNS records in addition to A
[ ] Make sure nginx configuration is set up to listen on both IPv4 and IPv6 addresses
[ ] Test out over LTE

The game is afoot! https://aws.amazon.com/blogs/aws/aws-ipv6-update-global-support-spanning-15-regions-multiple-aws-services/

I've manually associated IPv6 subnets with the VPC and all subnets, assigned IPv6 addresses to the running instances, and added AAAA records in Route 53 for staging.oversight.garden. Next: testing

That didn't work. In addition to updating the Rake tasks, I also need to add listen [::]:80;/listen [::]:443; to the nginx configuration.

It turns out this and #175 are blocked on EC2 Autoscaling Groups. Right now, you can only specify in launch configurations that instances are automatically assigned IPv4 addresses, and when you spin it up, instances don't get assigned IPv6 addresses.
I have half a mind to ditch the autoscaling group setup, and just use a regular instance for the web server. We aren't reaping any benefits from this, it's a pain to deal with the API differences between EC2 and EC2 ASG, and we don't actually have an ELB in front of the whole group, just a DNS record that's updated at provision time. But that's all for another day. Maybe this could be my first Terraform project?

Maybe this could be my first Terraform project?

I haven't done a ton with it myself, but my colleagues have and it's supposed to be pretty damn straightforward.


Update to latest version of 3.04

Hello,
tesseract-ocr code moved to https://github.com/tesseract-ocr/ and we are coming very close to 3.04 release.
Can you please test the code with your project and if needed sent pull request with fixes?

Updated 3.03 dev branch (now for 3.04 work) in commit 1d11b34cc761813451d116d0946ab61f2c117401

I can confirm all my tests are passing in the latest version of 3.04.


Adding api-inference-community to huggingface_hub.

The idea is to make all external contributions centralized.
Moved the quality checks (could make them uniform later)
api-inference-community should be relatively independant from huggingface_hub still.

Thanks! Looks good to me but adding @LysandreJik and @n1t0 to the party

Does the CI take a long time? If it does, maybe we'll want to restrict the Inference-API's CI to changes to that folder.

Not sure how easy to run conditional actions but if it's easy then yes let's do it !
Otherwise the CI is super fast as we only run the package CI, everything else is considered "slow" as it would require model downloads (and I don't want to force users to test against dummy models as it is a bit more complex to do).
Before deployment, we run the test_dockers slow CI which actually build the container + run the test suite on those with a live model. We can do that framework per framework making it livable (running tests against all frameworks all the time seems a bit like a waste since we're relying on docker to make sure no unforeseen change happens within the API)
Conditional full docker tests would be the best so that PR creators can be alerted early if something doesn't fit.

Hi @julien-c do you think the changes made are OK?
I added a simple docker test only for allennlp (afaik, I would need one for each framework, because we can't have multiple on clauses in a single yaml file).
Also I am not 100% sure about this docker because it does not seem to run on this PR, is that normal ? I though GH actions should run on current PR, but maybe I'm wrong.

not sure why the CI suite doesn't run, maybe it will after we merge this first PR? or maybe add a pull_request: event clause with the same paths?


Issue with parsing double from CSV

Hi,
I faced an issue while working with library functionality
conn.import_from_file(file_obj, update_table_name)
if we have double value in CSV file like "0.0272" it will become 0.027200000000000002 in exasol.
I can't see ability to setup format for CSV like that: (1..57,58 format='999999999999999.999999', 59..93)
To query, that was produced by library:
IMPORT INTO tmp_transactions_7220673 FROM CSV
AT 'http://<IP_ADDRESS>:46363' FILE '000.gz'

Hello,
Please note, this behaviour is not related to PyEXASOL import, but to DOUBLE PRECISION implementation and storage in general.
Please try to run the following basic example:
stmt = C.execute("SELECT CAST('0.0272' AS DOUBLE PRECISION)")
print(stmt.fetchall())

The debug + response is following:
2020-05-26 12:38:10.350 [WebSocket request #4]
{
    "command": "execute",
    "sqlText": "SELECT CAST('0.0272' AS DOUBLE PRECISION)"
}
2020-05-26 12:38:10.384 [WebSocket response #4]
{
    "status": "ok",
    "responseData": {
        "results": [
            {
                "resultType": "resultSet",
                "resultSet": {
                    "numColumns": 1,
                    "numRows": 1,
                    "numRowsInMessage": 1,
                    "columns": [
                        {
                            "name": "CAST('0.0272' AS DOUBLE)",
                            "dataType": {
                                "type": "DOUBLE"
                            }
                        }
                    ],
                    "data": [
                        [
                            0.027200000000000002
                        ]
                    ]
                }
            }
        ],
        "numResults": 1
    }
}
[(0.027200000000000002,)]

If you wish to avoid the non-precision calculation, you may simply use DECIMAL datatype of appropriate size.
For example:
stmt = C.execute("SELECT CAST('0.0272' AS DECIMAL(10,4))")

Will give you:
2020-05-26 12:41:12.993 [WebSocket request #4]
{
    "command": "execute",
    "sqlText": "SELECT CAST('0.0272' AS DECIMAL(10,4))"
}
2020-05-26 12:41:13.025 [WebSocket response #4]
{
    "status": "ok",
    "responseData": {
        "results": [
            {
                "resultType": "resultSet",
                "resultSet": {
                    "numColumns": 1,
                    "numRows": 1,
                    "numRowsInMessage": 1,
                    "columns": [
                        {
                            "name": "CAST('0.0272' AS DECIMAL(10,4))",
                            "dataType": {
                                "type": "DECIMAL",
                                "precision": 10,
                                "scale": 4
                            }
                        }
                    ],
                    "data": [
                        [
                            "0.0272"
                        ]
                    ]
                }
            }
        ],
        "numResults": 1
    }
}
[('0.0272',)]

Hope it helps!

Yes, I should have mentioned that I'm speaking only about import statement that generated by pyexasol
select cast('0.0272' as double) from dual;
0.027200000000000002
select cast(0.0272 as double) from dual;
0.0272
The idea is to help exasol to determine that field shouldn't be interpreted as a string by explicit a number format in import statement. It can be done manually by calling statement like that:
IMPORT INTO table FROM LOCAL CSV FILE 'table_path' (1..2,3 format='999999999.999');
https://docs.exasol.com/loading_data/file_formats.htm ( Numbers part of page)
https://docs.exasol.com/sql_references/formatmodels.htm#DateTimeFormat (Numeric Format Model part of page)
Is that a way to add this part (1..2,3 format='999999999.999') to import query generated by library?

Ok, it's a very interesting case. I've managed to reproduce it.
I'll raise a ticket for Exasol support. I suspect string to double conversion is not performed correctly, but it is not so obvious in other SQL clients (e.g. ExaPlus).
We'll try to find a more generic solution or fix the default behaviour.

About the "format" block in IMPORT SQL. It's not supported at this moment, since this syntax is not very flexible and generally leads to other unintended consequences. It is possible to implement, but it may lead to more problems down the road.

In the meantime, can you use one of following workarounds?

Switch to DECIMAL datatype for target table.
Import into "staging" table first with DECIMAL datatype, but move data into target table with DOUBLE datatype.
Apply UPDATE in the same transaction after IMPORT, normalising DOUBLES to required format.

I'll come back to you when I have more info.
Thank you for finding this!

The workarounds are working, but I'm looking for more generic solution for double and pyexasol library without additional step.
Thank you very much for investigating that. Will wait for answer from exasol support as well.

I just want to give a quick update on this.
Exasol support is still investigating the issue. It is not connected with PyEXASOL specifically, but with treatment of VARCHAR -> DOUBLE conversion in general. If developers decide to fix it at source, it might break some backwards compatibility.
I'll keep you updated.

Yeah, I can see it by running simple queries in exasol.
select cast('0.0272' as double) from dual;
0.027200000000000002
select cast(0.0272 as double) from dual;
0.0272

Can we do something with this:
About the "format" block in IMPORT SQL. It's not supported at this moment, since this syntax is not very flexible and generally leads to other unintended consequences. It is possible to implement, but it may lead to more problems down the road.
may I can create PR or something?

PR is definitely possible, but:

csv_cols option is generally quite ugly and not very flexible. We normally recommend users to create their own proper data transformation and layer and send "clean" and pre-formatted data to Exasol. It won't work in this case, but it will work in most of other common use cases.

Syntax of csv_cols is complex. We have individual column numbers, ranges and mixed formats. If we just pass a string directly to SQL, it will lead to SQL-injection. If we create a query builder, it will be complex as well.

This problems affects all kinds of IMPORT, not only PyEXASOL. So even if we provide an obscure way to fix it here, 99% of people will not be aware of the problem. And some people who will be aware, they'll have to write a complex code and provide number formatting for every DOUBLE column manually.

So I'd rather give a chance for Exasol support to come out with their vision of general fix for this problem. It can be some sort of global SQL changing session parameter, or command line parameter, or just a fix in the ETL process code.
Let's see how it goes. It should not take long, I expect some feedback early next week.

Ok, so here is the response from support, which is quite interesting:

This is a disadvantage when using double values.  Those inaccuracies are not unexpected when dealing with DOUBLEs. As DOUBLE is an approximative data type, some values cannot be stored exactly. Double is based on a number representation of base 2 compared to base 10 for our exact numeric types. This means that even the same exact numeric number might get a different double representation when converting to double, as you can see for the following example where always the same number 0.0272 (and for comparison 0.272) is casted to double from different Decimal(X,X)-types:

create or replace table t(d5 decimal(5,5), d6 decimal(6,6), d7 decimal(7,7), d8 decimal(8,8), d9 decimal(9,9), d10 decimal(10,10), d11 decimal(11,11), d12 decimal(12,12), d13 decimal(13,13), d14 decimal(14,14), d15 decimal(15,15), d16 decimal(16,16), d17 decimal(17,17), d18 decimal(18,18), d19 decimal(19,19), d20 decimal(20,20), d21 decimal(21,21), d22 decimal(22,22), d23 decimal(23,23), d24 decimal(24,24), d25 decimal(25,25), d26 decimal(26,26), d27 decimal(27,27), d28 decimal(28,28), d29 decimal(29,29), d30 decimal(30,30), d31 decimal(31,31), d32 decimal(32,32), d33 decimal(33,33), d34 decimal(34,34), d35 decimal(35,35), d36 decimal(36,36));
insert into t values (0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272, 0.272);
insert into t values (0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272, 0.0272);
select cast(d5 as double) doub5, cast(d6 as double) doub6, cast(d7 as double) doub7, cast(d8 as double) doub8, cast(d9 as double) doub9, cast(d10 as double) doub10, cast(d11 as double) doub11, cast(d12 as double) doub12, cast(d13 as double) doub13, cast(d14 as double) doub14, cast(d15 as double) doub15, cast(d16 as double) doub16, cast(d17 as double) doub17, cast(d18 as double) doub18, cast(d19 as double) doub19, cast(d20 as double) doub20, cast(d21 as double) doub21, cast(d22 as double) doub22, cast(d23 as double) doub23, cast(d24 as double) doub24, cast(d25 as double) doub25, cast(d26 as double) doub26, cast(d27 as double) doub27, cast(d28 as double) doub28, cast(d29 as double) doub29, cast(d30 as double) doub30, cast(d31 as double) doub31, cast(d32 as double) doub32, cast(d33 as double) doub33, cast(d34 as double) doub34, cast(d35 as double) doub35, cast(d36 as double) doub36 from t;

If you look at a string representation we have to use an internal decimal type as an intermediate type, e.g. the smallest one who could hold the number. There is a difference between importing into a double column and importing into a decimal column (which uses the same decimal place for all values) and then converting to double.
For exact numeric conversions, we recommend to use Double Precision (comment: probably a mistake, should be Decimal instead) data type.
For little bit more information see:
https://www.exasol.com/support/browse/SOL-102
https://docs.exasol.com/sql_references/data_types/datatypedetails.htm

Here is the result of SQL above:
'[{"DOUB5": 0.272, "DOUB6": 0.272, "DOUB7": 0.272, "DOUB8": 0.272, "DOUB9": 0.272, "DOUB10": 0.272, "DOUB11": 0.272, "DOUB12": 0.272, "DOUB13": 0.272, "DOUB14": 0.272, "DOUB15": 0.272, "DOUB16": 0.272, "DOUB17": 0.272, "DOUB18": 0.272, "DOUB19": 0.272, "DOUB20": 0.272, "DOUB21": 0.272, "DOUB22": 0.272, "DOUB23": 0.272, "DOUB24": 0.272, "DOUB25": 0.27199999999999996, "DOUB26": 0.27199999999999996, "DOUB27": 0.27199999999999996, "DOUB28": 0.272, "DOUB29": 0.272, "DOUB30": 0.272, "DOUB31": 0.272, "DOUB32": 0.272, "DOUB33": 0.272, "DOUB34": 0.272, "DOUB35": 0.272, "DOUB36": 0.27199999999999996}, {"DOUB5": 0.0272, "DOUB6": 0.0272, "DOUB7": 0.0272, "DOUB8": 0.0272, "DOUB9": 0.0272, "DOUB10": 0.0272, "DOUB11": 0.0272, "DOUB12": 0.0272, "DOUB13": 0.0272, "DOUB14": 0.0272, "DOUB15": 0.0272, "DOUB16": 0.0272, "DOUB17": 0.0272, "DOUB18": 0.0272, "DOUB19": 0.0272, "DOUB20": 0.0272, "DOUB21": 0.0272, "DOUB22": 0.0272, "DOUB23": 0.027200000000000002, "DOUB24": 0.027200000000000002, "DOUB25": 0.0272, "DOUB26": 0.0272, "DOUB27": 0.0272, "DOUB28": 0.0272, "DOUB29": 0.027200000000000005, "DOUB30": 0.0272, "DOUB31": 0.027200000000000002, "DOUB32": 0.0272, "DOUB33": 0.027200000000000002, "DOUB34": 0.0272, "DOUB35": 0.0272, "DOUB36": 0.0272}]'

I guess, the best option here is to avoid dealing with conversion of DOUBLE values altogether and go with DECIMAL instead.
Anyway, I'll look into some basic implementation of csv_cols with validation via REGEXP.

@RomantsovArtur , please update to version 0.13.0 and try the following syntax:
import_params = {
    'csv_cols': ["1..57", "58 FORMAT='999999999999999.999999'", "59..93"]
}

conn.import_from_file(file_obj, update_table_name, import_params)

Please let me know if it works for you :)

Thank you very much for this. I will check it today or early tomorrow

Works as it should. Great !


Add .app.src as Erlang extension.

*.app.src is a convention that modern build tools use as input to describe an Erlang application.
In-the-wild search doesn't pull up any results, I think due to the period in the extension, but it should be popular among Erlang projects.

A few thousands can be found with the following search: https://github.com/search?p=1&q=filename%3A.app.src+extension%3Asrc&ref=searchresults&type=Code&utf8=✓

Thanks for this contribution @thwg :zap:. This will be live in the next release of Linguist (likely sometime in the next week).


bitrise-step-firebase-app-distribution 0.8.0

What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.

[x] I will not move an already shared step version's tag to another commit
[x] I read the Step Development Guideline
[x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

New Step
Thank you for the new Step share! The CI check might will fail due to our extended validation engine. Nothing to worry about yet, we will get back to you shortly.

I'm sorry, but this fails with the same issue, could you open the branch and PR without the bitrise-step prefix please?

opened a new one #2675


[6.0.0-beta.6] Project '$$proj0' could not be found in workspace when trying to build/serve

Versions
Angular CLI: 6.0.0-beta.6
Node: 8.10.0
OS: win32 x64
Angular: 6.0.0-beta.8
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker

@angular/cli: 6.0.0-beta.6
@angular-devkit/architect: 0.0.7
@angular-devkit/build-optimizer: 0.4.6
@angular-devkit/build-webpack: 0.0.7
@angular-devkit/core: 0.4.6
@angular-devkit/schematics: 0.4.6
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 6.0.0-beta.6
@schematics/angular: 0.4.6
@schematics/package-update: 0.4.6
typescript: 2.7.2
webpack: 4.1.1

Repro steps

Clone this repo.
npm i
Run ng build or ng build --prod

Observed behavior
Project '$$proj0' could not be found in workspace.
Error: Project '$$proj0' could not be found in workspace.
    at Architect.getTarget (D:\www\_github\_mrcroft\ng6-cli6-app-shell\node_modules\@angular-devkit\architect\src\architect.js:101:19)
    at MergeMapSubscriber.architect.loadWorkspaceFromJson.pipe.operators_1.concatMap [as project] (D:\www\_github\_mrcroft\ng6-cli6-app-shell\node_modules\@angular\cli\models\architect-command.js:56:45)
    at MergeMapSubscriber._tryNext (D:\www\_github\_mrcroft\ng6-cli6-app-shell\node_modules\rxjs\operators\mergeMap.js:122:27)
    at MergeMapSubscriber._next (D:\www\_github\_mrcroft\ng6-cli6-app-shell\node_modules\rxjs\operators\mergeMap.js:112:18)
    at MergeMapSubscriber.Subscriber.next (D:\www\_github\_mrcroft\ng6-cli6-app-shell\node_modules\rxjs\Subscriber.js:90:18)
    at MergeMapSubscriber.notifyNext (D:\www\_github\_mrcroft\ng6-cli6-app-shell\node_modules\rxjs\operators\mergeMap.js:145:30)
    at InnerSubscriber._next (D:\www\_github\_mrcroft\ng6-cli6-app-shell\node_modules\rxjs\InnerSubscriber.js:23:21)
    at InnerSubscriber.Subscriber.next (D:\www\_github\_mrcroft\ng6-cli6-app-shell\node_modules\rxjs\Subscriber.js:90:18)
    at Object.subscribeToResult (D:\www\_github\_mrcroft\ng6-cli6-app-shell\node_modules\rxjs\util\subscribeToResult.js:17:25)
    at MergeMapSubscriber._innerSub (D:\www\_github\_mrcroft\ng6-cli6-app-shell\node_modules\rxjs\operators\mergeMap.js:132:38)

Mention any other details that might be useful (optional)
The app in the repo was generated with 6.0.0-beta.6, --skip-install and updated Angular to 6.0.0-beta.8 + TypeScript to required >=2.7.2
But I've also tried with Angular 5.2.9 and it behaves the same.
It has SW + AppShell because that's what I was planing on testing, but removing the app shell and the universal app doesn't change anything, so they're not the issue.

I have the same issue. I have this only only with<EMAIL_ADDRESS>Beta 5 works properly.

same here after "ng  update --next" to go on angular@rc0

Temporary workaround: reducing the number of Angular CLI apps in .angular-cli.json to one, and remove its "name" property. So it obviously has to do with using multiple Angular CLI apps.

That's funny, since I added "name" to all apps because in beta.5 there was a bug that you couldn't build by id. Anyway, unfortunately if you use SSR and/or AppShell you can't actually remove them. But it's just a beta, it's only out there for us to test and file issues.

+1

Retested in 6.0.0-beta.7 and 6.0.0-beta.8:
$ ng build --app foo --prod --sourcemaps
Cannot read property 'host' of null
TypeError: Cannot read property 'host' of null
    at Architect._loadJsonFile (../node_modules/@angular-devkit/architect/src/architect.js:200:32)

This problem has apparently come back in @angular/cli": "~6.1.1. And I have also just tried 6.1.0, the same problem.
I had never got such problem in previous production releases. Now I have to reverse back to 6.0.8 which is working fine.

I had just tried 6.1.3, and the problem remains. Now I have to reverse back to 6.0.8 again which is working fine.

I had just tried 6.1.4, and the problem remains. Now I have to reverse back to 6.0.8 again and again which is working fine.


[FLINK-15408][table-planner-blink]Interval join supports no equal condition

What is the purpose of the change
Interval join supports no equal condition
Brief change log
Remove restrictions that do not allow equivalent join in StreamExecIntervalJoinRule
Verifying this change
This change added tests and can be verified as follows:

IntervalJoinITCase#testRowTimeInnerJoinWithoutEqualCondition

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): ( no)
The serializers: (no )
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

it's better you can rebase the latest master

@godfreyhe Thanks for your reviewing. I have add a plan test and rebased the master.

+1 to merge


is not a pointer

hi
im trying to return slices of a model as an attribute of another model.
func (r *userResolver) Roles() *[]*model.Role {
	// var roles []*model.Role
	roles := make([]*model.Role, 0)

	return &roles
}

there were no error in the code, except im receiving panic indicating:
panic: field "Roles": model.Role is not a pointer

What does the user resolver look like?

I think problem in struct model.Role methods:
They all should be like func (r *model.Role) A(...)... and not func (r model.Role) ...)
So that mean, they all should be with pointer receiver

User struct look like this:

type User struct {
	UID               string `json:"uid"`
	Email             string `json:"email" db:"email"`
	Username          string `json:"username" db:"username"`
	Password          string `json:"password"`
	EncryptedPassword string `json:"encrypted_password"`
	First_name        string `json:"first_name" db:"first_name"`
	Last_name         string `json:"last_name" db:"last_name"`
	IPAddress string    `json:"ip_address" db:"ip_address`
	CreatedAt time.Time `json:"created_at"`
	UpdatedAt time.Time `json:"updated_at"`
	Roles     *[]*Role  `json:"roles"`
}

I think problem in struct model.Role methods:
They all should be like func (r *model.Role) A(...)... and not func (r model.Role) ...)
So that mean, they all should be with pointer receiver
@u007

Hi @vetcher , where did you see me using
func (r model.Role) ...) ?

does your userResolver look like this:
type UserResolver struct { 	*User }

nvm, i resolved to use [Role!] and it works.
make sense that slice returned could be nil, but the Role should be a valid role
type userResolver struct {
	u                *model.User
}

func (r *userResolver) Roles() *[]roleResolver {
	var roles []roleResolver
	if r.u.Roles == nil {
		return &roles
	}

	userRoles := *r.u.Roles
	for i := range *r.u.Roles {
		roles[i] = roleResolver{
			role: userRoles[i],
		}
	}
	return &roles
}

nvm, i resolved to use [Role!] and it works.

Makes sense, a nullable graphql field should be defined as pointer, because those can be nil too.


Make sure the proper branch / tag of docs is being used from github.

Some general cleanup of properties
Fixes spring-cloud/spring-cloud-dataflow-server-cloudfoundry/issues/181

Looks like on a conceptual level use of branched/tagged version will not work.

html will link directly to github with used address in asciidoc.
pdf/epub will download images and embed those is a created doc.

As looking build log for a release at https://build.spring.io/download/SCD-CFBMASTER-JOB1/build_logs/SCD-CFBMASTER-JOB1-204.log
build	25-Aug-2016 18:22:27	[INFO] Deploying artifact: https://repo.spring.io/libs-staging-local/org/springframework/cloud/spring-cloud-dataflow-server-cloudfoundry-docs/1.0.0.RELEASE/spring-cloud-dataflow-server-cloudfoundry-docs-1.0.0.RELEASE.zip;zip.type=docs;zip.deployed=false
build	25-Aug-2016 18:22:28	[INFO] Artifactory Build Info Recorder: Deploying build info ...
build	25-Aug-2016 18:22:28	[INFO] Deploying build descriptor to: https://repo.spring.io/api/build
build	25-Aug-2016 18:22:30	[INFO] Build successfully deployed. Browse it in Artifactory under https://repo.spring.io/webapp/builds/Spring%20Cloud%20Data%20Flow%20-%20Server%20-%20Cloud%20Foundry%20-%20Master%20-%20Build%20Spring%20Cloud%20Data%20Admin%20CF/204
build	25-Aug-2016 18:22:30	[INFO] ------------------------------------------------------------------------
build	25-Aug-2016 18:22:30	[INFO] Reactor Summary:
build	25-Aug-2016 18:22:30	[INFO]
build	25-Aug-2016 18:22:30	[INFO] spring-cloud-dataflow-server-cloudfoundry-parent .. SUCCESS [2.567s]
build	25-Aug-2016 18:22:30	[INFO] spring-cloud-starter-dataflow-server-cloudfoundry . SUCCESS [6.241s]
build	25-Aug-2016 18:22:30	[INFO] spring-cloud-dataflow-server-cloudfoundry ......... SUCCESS [4.734s]
build	25-Aug-2016 18:22:30	[INFO] spring-cloud-dataflow-server-cloudfoundry-docs .... SUCCESS [40.782s]
build	25-Aug-2016 18:22:30	[INFO] ------------------------------------------------------------------------
build	25-Aug-2016 18:22:30	[INFO] BUILD SUCCESS
build	25-Aug-2016 18:22:30	[INFO] ------------------------------------------------------------------------
build	25-Aug-2016 18:22:30	[INFO] Total time: 1:10.676s
build	25-Aug-2016 18:22:30	[INFO] Finished at: Thu Aug 25 18:22:30 UTC 2016
build	25-Aug-2016 18:22:30	[INFO] Final Memory: 162M/1354M
build	25-Aug-2016 18:22:30	[INFO] ------------------------------------------------------------------------
...
simple	25-Aug-2016 18:22:31	[RELEASE] Committing release version on branch 'master'
simple	25-Aug-2016 18:22:31	[RELEASE] Pushing tag: v1.0.0.RELEASE to url https://github.com/spring-cloud/spring-cloud-dataflow-admin-cloudfoundry.git
simple	25-Aug-2016 18:22:32	[RELEASE] This repository moved. Please use the new location:  https://github.com/spring-cloud/spring-cloud-dataflow-server-cloudfoundry.git
...

This build didn't use release branch but that would be pushed to github just before pushing a tag. What this means is that branch/tag doesn't exist in github when release build is done.
We'd get away from it for html(is it's just linked and branch/tag will become available later) but pdf would fail to import those images. Also for html we should not use github as a CDN for images in a docs anyway.

Note that this is for server-cf which references scdf-core, so at the time we release server-cf, scdf-core has already been released, so the tag DOES exist. Or am I missing something?
I'm just automating things we're already doing. That being said, I agree we tend to abuse over-http includes and github cdn...

well yes, sabby asked to comment on a generic level. we'd have this issue if cf docs would have their own images, or if we do this same dance in a dataflow core(imported asciidocs from there still point to master).

Looks good, merging.


preview-docs page refresh breaks with pagination section or item

Describe the bug
When the reference docs config has:
referenceDocs:
  pagination: section
  # or pagination: item

And you browse to an operation...
Then refresh the browser and voila!
To Reproduce
Steps to reproduce the behavior:

Given this .redocly.yaml file excerpt above (You can use rebilly/api-definitions core API)
And this OpenAPI file(s) (Use rebilly/api-definitions core API)
Run this command with these arguments... openapi preview-docs core
Browse to Customers > Create a customer.
Refresh the browser.
See error.

Expected behavior
It should work.
Logs
n/a
openapi-cli Version(s)
Latest as of Oct 28, 2021.
Node.js Version(s)
14 LTS.

@adamaltman rebilly's core api seems too heavy to run locally. In very rare cases I get page initially loaded but when I reload browser I see the loading spinner forever. Is this a problem you're talking about or it's something different?
P.S. I was trying to run preview-docs for storefront api and browser reloading works good there.

I was able to reproduce it. I ran it using reference-docs and when I reload the page I get: 404 Not Found

Located the problem: https://github.com/Redocly/openapi-cli/blob/master/packages/cli/src/commands/preview-docs/preview-server/preview-server.ts#L108
NOTE this problem exists only with pagination set to item or section


How about custom UI plugins?

Hey!
I've been working on a file explorer app for some time now and wanted to make the preview components of files pluggable. So  I could easily add new preview windows for file types. I was wondering on how I would go about adding the necessary UI code to pluggable-electron. How would such an interaction look like? How would plugins return their UI to the main app so I can call their render logic when I want to show a file preview?
Currently I am using VueJS :)

Sorry for the late response, I didn't get a notification from Github somehow. In any case, this is a good question and one that I will look in to because I also plan to use this with VueJS.
The main complexity that I see here is that a plugin needs to be able to access and provide vue components without direct access to the base app's code or the vue framework. I expect this can be solved in 2 steps

Execute an extension point when a preview is requested, passing in the file extension to the extension point. Any plugin should then return a Vue component if it can provide it for the given file type. const previewComp = await pe.extensionPoints.execute( 'file_preview', fileType ). The component can then be insterted in to the app using the <component> component.
The plugin should be built as a Vue library. This would up to the plugin developer to do so should be described in the plugin developer documentation.

But at this stage this is still a high level and unproven concept. It is already on my to do list to create a proof of concept but I'm not sure yet when I'll get around to this. I will let you know once I have more info or a usable example. Or if you figure this out in the meantime please let me know 😁.

Version 0.2.0 has now been released and this supports importing Pluggable Electron into ES modules on the front end. Note that this version requires a significantly different setup to support the ES modules. As such, please see the readme before updating. There are also some catches to using a pre-compiled framework like Vue or React and I'll be documenting these when I have the time.

I have now also created a demo project with Vue. See https://github.com/dutchigor/pluggable-electron-demo/tree/with-vue. Let me know if you still have any questions. Otherwise I will close this ticket.


Angular 2.0 Support

When is it planned to get angular 2.0 support with ngmodules? The biggest problem is using third party libraries which already support this (like ngtranslate..)
Regards

The upcoming beta.12 will include it and it will be here "soon" according to the team's comments I've seen in the issues.

Hello all! Beta.12 is running on Angular 2.0 final and i can now say that it will be here not just "soon" but extremely soon 😉 . Thanks for using Ionic!

Wooo! Great news !

Awesome! Can't wait for this!


Add Snowplow build context

Currently we include is_dev_build in the Snowplow environment context, which generally indicates whether the events being fired is from a build of Meltano taken from PyPI, or a build built directly off of the Meltano repository.
We could extend this idea creating a Snowplow build context. When Meltano is built, a custom build tool which wraps poetry.core.masonry.api (as described in #3401) could collect info about the build. The data collected could include:

The date and time the build was performed
The timezone the build was performed in
An equivalent to is_dev_build from the environment context
Something like is_ci_environment from the environment context, but now for whether the build occurred in CI, as opposed to the execution of Meltano
Whether pipx was used (by inspecting the process tree)
More info about the build tools used and their versions
The git commit built off of
Whether the git repository was clean when the build was performed
etc.

The custom build tool would collect all of the desired information, and store it in a JSON file in the wheel or sdist it builds. Then when events are fired by Meltano, this info could be included in a context just like how we include the environment context.
@aaronsteers @pnadolny13 @pandemicsyn

@WillDaSilva I'm not super in tune with the build process or the things we care about in the process but what are the use cases for this data? What behaviors are we trying to understand with this context?
My initial thought is that from the data/reporting side of things the build context isnt all that interesting but I might just might not understand the use cases. Wouldnt most of these built contexts be the same since the majority of users are pip installing? Are we trying to see if users are building their own package?

Are we trying to see if users are building their own package?

@pnadolny13 Yes. In particular we want to know if the package was built using pipx. As @aaronsteers noted, the is_dev_build value from the environment context does not properly account for this.
This context would also be helpful in determining if users are building Meltano for themselves more generally, and if they're doing so with modifications.

@pnadolny13 @aaronsteers I think it is time to revisit this idea. The current plan for exposing Meltano Cloud alpha/beta CLI features is to do so in a feature branch, and have the users install Meltano using pip install git+https://github.com/meltano/meltano@cloud (or some other branch/tag instead of cloud). The telemetry will consider these to be dev builds, which I believe will cause their data to be filtered out after we collect it.
To avoid that, we can introduce the build context as proposed above. It will contain information gathered within scripts/build.py, which is run when the wheel is built. With this we can solve the above problem by including the git branch/tag found when scripts/build.py runs. I've tested this out, and it works as expected - pip clones the repository, then builds the wheel within it, so we can run git branch --show-current in addition to collecting other information that might help us down the line.
Then when we're processing the collected data we can avoid filtering out data based on is_dev_build if that build was done on the cloud branch.

@WillDaSilva for context - as of today we dont filter based on the is_dev_build attribute. That's something we could look into doing if it would accurately filter out devs vs real users. It felt too risky to me originally to use it for any low level filtering because I dont know all the ways people can install the package so wouldnt want to accidentally over filter with an attribute I dont fully understand.

@pnadolny13 Thanks for letting me know. That makes this unnecessary in light of the recent build changes, and the proposed Meltano Cloud alpha/beta installation method, which is convenient. I'll keep this issue open in case we ever decide that we're interested in gathering this information, but for now I'll unassigned myself.


Fix to make signal on payment change actually be registered

I think that https://github.com/mirumee/saleor/commit/413ec31a1280b677da37a5ae8d6cb1080ffe302e has introduced a problem in which the status_changed signal is not processed, because order_status_change() is not registered as a received, because the code in signals.py is not loaded / referenced.
I've added an import of order_status_change() to the models.py file; I'm not sure is the best way to achieve the need, but it does cause the signal receiver registration to occur.

Should be resolved by #1724.


[BUG] No files are generated

Describe the bug
I copy+pasted the action into my Git-repo and I try to run the docs.kiplot.yaml. It runs DRC and ERC and also prints its results into the files but the pdf and svg are not generated.
To Reproduce
Steps to reproduce the behavior:
You can find the dedicated branch here: https://github.com/Informaticore/SuperPower/tree/testing_github_action
Expected behavior
After running the action it uploads pdf and svg files as zip into the artifacts
Additional context
It seems that it is not really running the generation part, only the checks for DRC and ERC

I can see several commits running the action and generating all files like expected.
eg 117d10a seems fine.
Do you need any more support?

hey - sorry I just figured out afterwards, that I have to give the explicite path to the .sch and pcb file. Is there a way to make it every file in the project no matter where it is? I tried **/*.sch but it was not working.
Should it generate the board even if it is empty? Because it can not find the layers (but as I said the pcb file is still empty currently.

as you have several *.sch files you have to specify which one to use. otherwise it should pick 'alphabetical first .sch found in current dir' but there is still a little bug I was not able to get rid off... and you are using a subdir anyway
If you specify your main schematic file all subsheets should be created.
I have never tried it with an empty board file before, it fails for me too.
If you add at least the Edge cuts it works.

perfect! thank you! I will try it out later - very nice github action anyway! Exactly what we are looking for.
Thanks a lot.


Fix ld warning

When building the SwiftXCTest target in Xcode 9 beta 4, ld reports the following warning:
Ld /Users/ipartrid/Library/Developer/Xcode/DerivedData/Foundation-dlbuoxyagtlausbjtyopapynebeb/Build/Products/Debug/SwiftXCTest.framework/Versions/A/SwiftXCTest normal x86_64
    cd /Users/ipartrid/swift-corelibs-xctest
    export MACOSX_DEPLOYMENT_TARGET=10.11
    /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch x86_64 -dynamiclib -isysroot /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk -L/Users/ipartrid/Library/Developer/Xcode/DerivedData/Foundation-dlbuoxyagtlausbjtyopapynebeb/Build/Products/Debug -F/Users/ipartrid/Library/Developer/Xcode/DerivedData/Foundation-dlbuoxyagtlausbjtyopapynebeb/Build/Products/Debug -F../swift-corelibs-foundation/build/Debug -filelist /Users/ipartrid/Library/Developer/Xcode/DerivedData/Foundation-dlbuoxyagtlausbjtyopapynebeb/Build/Intermediates.noindex/XCTest.build/Debug/SwiftXCTest.build/Objects-normal/x86_64/SwiftXCTest.LinkFileList -install_name @rpath/SwiftXCTest.framework/Versions/A/SwiftXCTest -Xlinker -rpath -Xlinker @executable_path/../Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -mmacosx-version-min=10.11 -Xlinker -object_path_lto -Xlinker /Users/ipartrid/Library/Developer/Xcode/DerivedData/Foundation-dlbuoxyagtlausbjtyopapynebeb/Build/Intermediates.noindex/XCTest.build/Debug/SwiftXCTest.build/Objects-normal/x86_64/SwiftXCTest_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -fobjc-link-runtime -L/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx -Xlinker -add_ast_path -Xlinker /Users/ipartrid/Library/Developer/Xcode/DerivedData/Foundation-dlbuoxyagtlausbjtyopapynebeb/Build/Intermediates.noindex/XCTest.build/Debug/SwiftXCTest.build/Objects-normal/x86_64/SwiftXCTest.swiftmodule -framework SwiftFoundation -single_module -Xlinker -dependency_info -Xlinker /Users/ipartrid/Library/Developer/Xcode/DerivedData/Foundation-dlbuoxyagtlausbjtyopapynebeb/Build/Intermediates.noindex/XCTest.build/Debug/SwiftXCTest.build/Objects-normal/x86_64/SwiftXCTest_dependency_info.dat -o /Users/ipartrid/Library/Developer/Xcode/DerivedData/Foundation-dlbuoxyagtlausbjtyopapynebeb/Build/Products/Debug/SwiftXCTest.framework/Versions/A/SwiftXCTest

ld: warning: directory not found for option '-F../swift-corelibs-foundation/build/Debug'

As far as I can tell, this directory is just not used by the build system and I'm not sure why it's been added to the Framework Search Paths for that target.
This PR removes the references, and hence the warning.

@swift-ci please test

It looks like this was intentionally added in #192. Maybe @spevans would have a better idea whether it's still necessary?

Ah, thanks I hadn't found #192. Maybe this PR is wrong then.

I think as long as you can open XCTest.xcworkspace and run the test on TestFoundation ok then this is fine. Also the same for Foundation.workspace for https://github.com/apple/swift-corelibs-foundation/pull/1139 (which worked ok for me)

Btw, I think the tests for the XCTest PRs actually build using Xcode on the CI server so if the Swift Test OSX Platform comes back ok then I think we are good. Although I think it does a Debug build of swift hence why it seems to take 2.5 hours!

Thanks @spevans hopefully we are good with this one then.

I could imagine the projects building to that directory if you opened the xcodeproj directly and had Xcode configured to use a custom build directory. Nonetheless with the workspace and the usual configuration, Foundation and XCTest should build to the shared DerivedData without extra search paths being needed.
The CI checks passed, so I think we're good. Thanks @ianpartridge!


[Feature request] Add ability to jump directly to numbered pane

We already have
nmap <leader>1 <Plug>AirlineSelectTab1

to switch the current pane to the numbered buffer.  But there are many times I don't want to change the pane, I want to move TO another pane.
The standard way is ctrl-w hjkl to move one pane at a time.  If I have 4 buffers open in vertical splits, it takes ctrl-w l ctrl-w l ctrl-w l ctrl-w l to move from first to last pane.  Can shorten that to ctrl-w 4 l but that means looking and counting.
It would be nice to have a direct way to jump.  Something like
<leader>a1 <Plug>AirlineSelectDirectTab1

to move cursor/active to pane 1.

We don't switch panes. We switch windows or tabs.
That is something for a buffer/window management plugin, not a fancy statusline plugin.

Yeah I get it :)  I figured I'd ask since the AirlineSelectTab1 was already there

yeah sorry for being a bit direct. It's a thin line but I don't want airline to gain functionality that clearly does not belong into a statusline plugin.


Regenerate APIs

Hi @sqrrrl,
I need the google-api-ruby-client gem to be regenerated and include the client for the Key Management Service.
Thanks!

Available in release 0.9.26

Thank you!


Add pseudo field support for it to act as a "recurring" upsell checkbox

Add support to allow for a pseudo checkbox to act as a "recurring" toggle.

Markup Example

			<input class="en__field__input en__field__input--checkbox" id="en__field_supporter_monthly_upsell_checkbox" name="supporter.monthly_upsell_checkbox" type="checkbox" value="Y">

				Make this a monthly recurring gift! Recurring gifts help us act faster on urgent issues.

I have some code ( https://pastebin.com/raw/QM4sxnuA ) that can be dropped into this example page ( https://act.ran.org/page/29393/donate/1?mode=DEMO ) that will select/deselect the Monthly Frequency when the upsell checkbox is checked/unchecked ( https://d.pr/v/NPABHU ).
The above solution will get the job done, but it's not perfect and does leave a couple of improvements outstanding. The two things that could be improved is that it could visually update the giving amounts so they have "/mo" labels on them. And it could update the submit button label so it has the "Monthly" label on it. Right now it can't do either.
Once done, add to the ENGrid 2021 documentation ( https://docs.google.com/document/d/1zF-86Iq8tCRk4HCv-JaJYZulkC273x-_QODUed9F0Pw/edit ).
REF: https://app.productive.io/2650-4site-interactive-studios-inc/tasks/1641942

This is done


Undefined ocaml_terminal_get_sigwinch on macos

The newest progress version fails at link time with the following error:
Undefined symbols for architecture x86_64:
  "_ocaml_terminal_get_sigwinch", referenced from:
      _camlTerminal__entry in terminal.a(terminal.o)
      _camlTerminal__gc_roots in terminal.a(terminal.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Thanks. I suspect the configure step just needs to use the POSIX-compatible bindings on MacOS, but hadn't been able to test it.
By a weird coincidence, I'm currently setting up an M1 Mac, so will fix this shortly!

Note that this occured using an intel macbook pro.
On Mon, Jun 28, 2021, 18:43 Craig Ferguson @.***> wrote:

Thanks. I suspect the configure step just needs to use the
POSIX-compatible bindings on MacOS, but hadn't been able to test it.
By a weird coincidence, I'm currently setting up an M1 Mac, so will fix
this shortly!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CraigFe/progress/issues/12#issuecomment-869838676,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACG3B6CBCSLGL5L2W6CLNNTTVCRB7ANCNFSM47NZRTZA
.


Cli: Stop containers

Coverage decreased (-0.1%) to 86.083% when pulling 346118f843e681f42d98f8edc9e8c5c6374d87f6 on cenouralm:stop_local_fixed into be044390ac01df8335d8127acf86a5435b253d6d on inveniosoftware:master.

Coverage decreased (-0.1%) to 86.083% when pulling 346118f843e681f42d98f8edc9e8c5c6374d87f6 on cenouralm:stop_local_fixed into be044390ac01df8335d8127acf86a5435b253d6d on inveniosoftware:master.

Works as expected:
(stats) ~/Workspace/inveniosw/test/my-site docker ps -a
CONTAINER ID        IMAGE                                                     COMMAND                  CREATED             STATUS                          PORTS                                                                                NAMES
b3e31a5988e3        my-site-frontend                                          "/docker-entrypoint.…"   3 minutes ago       Up 3 minutes                    <IP_ADDRESS>:80->80/tcp, <IP_ADDRESS>:443->443/tcp, <IP_ADDRESS>:32771->80/tcp, <IP_ADDRESS>:32770->443/tcp                       my-site_frontend_1
b8e6fe52760f        my-site                                                   "bash -c 'celery wor…"   3 minutes ago       Restarting (2) 13 seconds ago                                                                                my-site_worker_1
3551e2ded03d        my-site                                                   "bash -c 'uwsgi /opt…"   3 minutes ago       Up 3 minutes                    <IP_ADDRESS>:32769->5000/tcp                                                                                my-site_web-ui_1
934105194ab3        my-site                                                   "bash -c 'uwsgi /opt…"   3 minutes ago       Up 3 minutes                    <IP_ADDRESS>:32768->5000/tcp                                                                                my-site_web-api_1
6ec5ed0695b2        rabbitmq:3-management                                     "docker-entrypoint.s…"   3 minutes ago       Up 3 minutes                    4369/tcp, 5671/tcp, <IP_ADDRESS>:5672->5672/tcp, 15671/tcp, 15691-15692/tcp, 25672/tcp, <IP_ADDRESS>:15672->15672/tcp   my-site_mq_1
2d3227ad4c40        docker.elastic.co/elasticsearch/elasticsearch-oss:7.2.0   "/usr/local/bin/dock…"   3 minutes ago       Up 3 minutes (healthy)          <IP_ADDRESS>:9200->9200/tcp, <IP_ADDRESS>:9300->9300/tcp                                                                my-site_es_1
ca19a22b2733        redis                                                     "docker-entrypoint.s…"   3 minutes ago       Up 3 minutes                    <IP_ADDRESS>:6379->6379/tcp                                                                                my-site_cache_1
02e42c13b9ff        postgres:9.6                                              "docker-entrypoint.s…"   3 minutes ago       Up 3 minutes                    <IP_ADDRESS>:5432->5432/tcp                                                                                my-site_db_1
(stats) ~/Workspace/inveniosw/test/my-site invenio-cli stop
Stopping containers...
   3 minutes ago       Exited (0) 9 seconds ago                         my-site_frontend_1
b8e6fe52760f        my-site                                                   "bash -c 'celery wor…"   3 minutes ago       Exited (2) 35 seconds ago                        my-site_worker_1
3551e2ded03d        my-site                                                   "bash -c 'uwsgi /opt…"   3 minutes ago       Exited (0) 8 seconds ago                         my-site_web-ui_1
934105194ab3        my-site                                                   "bash -c 'uwsgi /opt…"   3 minutes ago       Exited (0) 8 seconds ago                         my-site_web-api_1
6ec5ed0695b2        rabbitmq:3-management                                     "docker-entrypoint.s…"   3 minutes ago       Exited (0) 3 seconds ago                         my-site_mq_1
2d3227ad4c40        docker.elastic.co/elasticsearch/elasticsearch-oss:7.2.0   "/usr/local/bin/dock…"   3 minutes ago       Exited (143) 7 seconds ago                       my-site_es_1
ca19a22b2733        redis                                                     "docker-entrypoint.s…"   3 minutes ago       Exited (0) 7 seconds ago                         my-site_cache_1
02e42c13b9ff        postgres:9.6                                              "docker-entrypoint.s…"   3 minutes ago       Exited (0) 7 seconds ago                         my-site_db_1


Good öan

New issue checklist

[x] I have reviewed the README and documentation
[x] I have searched existing issues and this is not a duplicate
[x] I have attempted to reproduce the issue and include an example project.

General information

IGListKit version:
iOS version(s):
CocoaPods/Carthage version:
Xcode version:
Devices/Simulators affected:
Reproducible in the demo project? (Yes/No):
Related issues:

Debug information
# Please include debug logs using the following lldb command:
po [IGListDebugger dump]

Goos

Good job man nice

Good job nice


[AutoPR imagebuilder/resource-manager] [Hub Generated] Review request for Microsoft.VirtualMachineImages to add version preview/2019-05-01-preview

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

(message created by the CI based on PR content)


2017-09-05. Merged in translations from Transifex.

Final localization push for 1.16.

I've removed the translations for the "azure-account" extension because that extension is no longer part of the release.

@weinand did you merge the commit into master as well (e.g. cherry picked)

@dbaeumer sure, I cherrypicked both the translations and my commit with the removal of the "azure-account" translations.


Update Composer dependencies (2023-05-20-00-09)

Visual regression test passed!
View the visual regression test report


Include python version numbers in hooks

Some hooks (at least lfs-large-files and enforce-action-comments) have syntax errors when run in Python 3, and so users who had that set to their default were experiencing issues

LGTM, merge when ready


Expose service shutdown api to workers

This PR exposes a new api to the workers, that enable workers to trigger a shutdown of the service.

In master.js:207 we describe reload function as "* reload the service with new code".
Why "new code"? We just kill current workers and create new ones to substitute them, don't we?

In master.js:207 we describe reload function as "* reload the service with new code".
Why "new code"? We just kill current workers and create new ones to substitute them, don't we?

because this is used for zero downtime updates, when you want to deploy a new version of the service. You will do

Replace deployment folder with new version.
Run npm run reload => which will trigger the api you mentioned.
We reload all the workers, which picks up new version (or new code).

Ah yes, through  worker.js:3 var service = require('../../../app/app.js');
Ok, then.

Shouldn't be the documentation of the options of workerCount in qcommand readme too?
I have only found them in qumramapi.
I am talking about "* workerCount was either be a number(1,2,3,4) or system core count (max), or number relative of system core count (max-1, max-2, max+1, max+2)"

worker.js:3 var service = require('../../../app/app.js'); looks really ugly. Meaning that it is very tightly coupled to a concrete way of using (deploying) the qservice.
I do not know how, but it seems there should be a way to make it more configurable.

Shouldn't be the documentation of the options of workerCount in qcommand readme too?
I have only found them in qumramapi.
I am talking about "* workerCount was either be a number(1,2,3,4) or system core count (max), or number relative of system core count (max-1, max-2, max+1, max+2)"

All the public npm packages we have currently lacks documentation, a reason for this maybe that it is not customer or configuration facing components. They need to improve, if you would like to work on that feel free to.
Also the organisation and management of the public npm modules is not done well, something we will have to fix in future.

worker.js:3 var service = require('../../../app/app.js'); looks really ugly. Meaning that it is very tightly coupled to a concrete way of using (deploying) the qservice.
I do not know how, but it seems there should be a way to make it more configurable.

This is a convention, if you need to use qservice on a project, then you have to expose the service starting file as app/app.js. I see no point in making this configurable. What would be the use case ?

In places like master.js:246 where we resurrect dead workers, shouldn't we log it so professional services can have some feedback info in case of problems?

In places like master.js:246 where we resurrect dead workers, shouldn't we log it so professional services can have some feedback info in case of problems?

Yes we should, but logging is application specific, and we need to spec out, how qservice can have access to the application logger to log this, or atleast access to configuration to have its own logger. it is something to be done.

@jmasramon we have some conceptual and philosophical answering in some comments, lets have a voice call tomorrow, to come to common understanding about those.

in master.js:136 _ if (listening === 2) {_ why we wait till we have entered 2 times before killing the old one? Shouldn't one be enough?

@jmasramon

in master.js:136 _ if (listening === 2) {_ why we wait till we have entered 2 times before killing the old one? Shouldn't one be enough?

Very good question, this is because we want to wait till the worker listens on http and https, before killing the old one, however this is prone to error, as now in configuration it is possible to say i only want to listen on http or https instead of both were this would fail. Should create an issue on JIRA for this, to decide what to do.


Node.js 14 (node:15731) Warning: Accessing non-existent property of module exports inside circular dependency (Use node --trace-warnings ... to show where the warning was created)

Running the build command displays multiple warnings.
(node:15731) Warning: Accessing non-existent property 'cat' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:15731) Warning: Accessing non-existent property 'cd' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'chmod' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'cp' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'dirs' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'pushd' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'popd' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'echo' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'tempdir' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'pwd' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'exec' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'ls' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'find' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'grep' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'head' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'ln' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'mkdir' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'rm' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'mv' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'sed' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'set' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'sort' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'tail' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'test' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'to' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'toEnd' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'touch' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'uniq' of module exports inside circular dependency
(node:15731) Warning: Accessing non-existent property 'which' of module exports inside circular dependency

my npm script looks like this:
{
"build": "npx tsdx build --name infoBox --format=cjs,esm,umd",
}

Environment - node 14.13.1
webpack 5.2.0

@JustFly1984 I'm not sure why you removed the issue template this time, but please don't do that, it's there for a reason

Environment - node 14.13.1
webpack 5.2.0

In particular, there's a specific command that is asked for all bug reports to use which gives all the required versions (TS, TSDX, etc). You used it in #900.
Webpack is also unrelated to TSDX so I'm not sure what you meant with that.

Running the build command displays multiple warnings.

This looks to be specific to Node 14, but not quite specific to TSDX. Similar to your #900 this seems to be a lockfile issue as this is coming from shelljs and should be fixed in the latest version of shelljs, which is not pinned by TSDX.
I did a search for this exact warning and the first result pointed to a Node issue, https://github.com/nodejs/node/issues/32987. There is a mention of shelljs, which is what exports all those shell-sounding names, in a comment there: https://github.com/nodejs/node/issues/32987#issuecomment-635726114 . That points to https://github.com/shelljs/shelljs/pull/973 and says it should be solved by upgrading to shelljs v0.8.4.
It's pinned to v0.8.3 in your yarn.lock, so you can just change it there.
Please recognize that filing an issue is asking a volunteer to respond. Please try to debug and search whatever problem you're having before filing an issue as both this and #900 were problems upstream and are specific to your lockfile. If you do file an issue, please make sure to fill out the issue template, search existing issues for duplicates, and try to narrow down why this is an issue in TSDX specifically and not elsewhere. Other maintainers could close such issues outright for not providing this information as we don't have the resources / capacity to debug every users' issues
Internal Repro
This also affects internal tests. I looked through the CI logs and saw this happens on Node 14 tests as well because the internal yarn.lock (which does not affect TSDX users and is not published) also has shelljs v0.8.3 pinned.


Learn about the new React DevTools

Link to video: https://www.youtube.com/watch?v=vfm4018YBEY&feature=youtu.be
How to get it working:
Install React:

Clone the repo: git clone git@github.com:facebook/react.git
Install dependencies: yarn
Build for node: yarn build core,dom,interaction-tracking --type=NODE
Link builds with frontity:

cd build/node_modules/react && yarn link && cd ../../..
cd build/node_modules/react-dom && yarn link && cd ../../..
cd build/node_modules/interaction-tracking && yarn link && cd ../../..
Go to frontity and run yarn link react react-dom interaction-tracking

Known issues:
Rollup might complain about Java. Install this version: http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
Install React Devtools:

Clone the repo: git clone git@github.com:facebook/react-devtools.git
Install dependencies: yarn
Build extension for Chrome: yarn build:extension:chrome
In Chrome go to: chrome://extension
Deactivate the release version of react-devtools.
Activate developer mode on the top-right corner:

Click on load unpacked on the top-left corner:

Select the react-devtools/shells/chrome/build/unpacked folder.

Known issues:
You need to use Node v8.4.11 LTS: https://nodejs.org/dist/v8.11.4/node-v8.11.4.pkg
Finally:
Now open a new tab in Chrome (https://demo.worona.org) and  react's tab in Chrome devtools should be working.
This makes Profiler and track to work by themselves, but the integration between both is in another branch (https://github.com/bvaughn/react/tree/interaction-tracking-profiler-integration), and when we change to that branch, react-devtools stops working.

I wouldn't spend more time on this until the feature is at least in beta.


Fixed bug in restrictToOwner

See issue #175.

This looks like a good fix but npm test is failing for that hook now.

Thanks for the PR @thosakwe! Unfortunately I don't think it's the right fix. Currently the hook assumes hook.id is present. Only changing the error check will just cause the hook to fail later on by returning a 404.
I actually think it is very valid that is throws an error on mass deletion. If you want to support mass deletion then I think there are 3 different options:

you should use a custom hook
use the restrictToRoles hook and set a user role that has access to do mass deletions
we should support an optional callback to determine when the hook should execute, like we do in the other bundled hooks (see here)

In order to determine whether you have access to items you want to modify you need to look them up first, this could be incredibly expensive if you did a blank find on all items for the service. So in reality, I think what you are looking for is to conditionally disable or enable this hook based on some condition.

Ah, I see.
And on second though, my fix might have been a bit ill-advised, too. Not sure if it would be a good to tell feathers-seeder users, "Hey! To use this plug-in, you have to remove this security feature from your application."

@thosakwe well, like I said you can just change your hooks or put in the readme for feathers-seeder that you do need to change the hook.
It sounds like the more ideal solution is to allow conditional running of the hooks.

I'm going to close this as I think we should support conditionally running hooks. I've created #210 to track that.

I agree about the fix, but this hook isn't returning the proper error.
It should handle both case, when you are on the wrong hook method, and when the id is missing. Otherwise, you can loose some time trying to figure out why feathers tells you you're using the hook on the wrong method, while it isn't the case.

I don't know if it's related, but I'm receiving an error saying The 'restrictToOwner' hook should only be used on the 'get', 'update', 'patch' and 'remove' service methods.. This error ocurs when I try to search for a user by id inside a middleware funcion:
app.get('/notificacoes/email/alteracao-de-senha/:idUsuario/:idSolicitacao', notificacoes.processeSolicitacaoDeAlteracaoDeSenha);
servicoDeUsuarios.get(idUsuario)
.then(usuario => {
// code here is not run
});
catch(error => {
// code enters inside this error handler with the above said message.
});
What is wrong with this code, please?


SAP Systems list revamp

SAP Systems list revamp, now we only list the application sap systems and the related application instances
Still missing: Health container & filters (under discussion), tags
A new viewmodel sap systems table was created to simplify the KV store data processing.


Questionable URL in CONTRIBUTING.MD

The CONTRIBUTING.MD instructions include instructions to issue the following command:
git remote add upstream https://github.com/OfficeDev/microsoft-graph-docs.git

The OfficeDev URL above seems questionable for this project.   Is stale information from another project?

Thanks for catching this. That section doesn't even apply to code sample contributions, so I removed it.


Can't validate input when length is > 500

Describe the bug
I realized that a user can't make an input of more than 500 characters without getting an error. I want to validate the input before so the user doesn't get an error but a friendly message but it doesnt seem to work.
this is the error:

this is the validation rule:

It gives the same error in Teams as in the emulator
Version
V1.3.0
Browser
OS

[ ] macOS
Windows
[ ] Ubuntu

Expected behavior
I would like for the bot composer to validate the input and give a friendly response when the input is larger than 500 characters

Hi @ysnoek2 Can you make sure that you are selecting write an expression? When doing so, it should prompt to put an equal sign = at the beginning. You should then have:
=length(string(this.value)) <= 500
For clarity; I am running v2.0.0 version of Composer. Here's what the dialog snippet looks like:
        {
          "$kind": "Microsoft.TextInput",
          "$designer": {
            "id": "65j1eJ"
          },
          "disabled": false,
          "maxTurnCount": 3,
          "alwaysPrompt": false,
          "allowInterruptions": false,
          "prompt": "${TextInput_Prompt_65j1eJ()}",
          "unrecognizedPrompt": "",
          "invalidPrompt": "${TextInput_InvalidPrompt_65j1eJ()}",
          "property": "user.largetext",
          "validations": [
            "=length(string(this.value)) <= 500"
          ]
        },

@ysnoek2 I'm going to assume this is resolved as it works for me with the above expression. If not; please comment and let us know if it behaved any differently.

@dmvtech sorry for the late reply! I tried it but still get the same errormessage:

And i updated to 2.0.0 btw but still the same

@ysnoek2 Do you see any error traces when reproducing in Emulator? Can you please share that if so?

@dmvtech I only see the messages i provided above

@ysnoek2 Are you able to share your bot to see if I can reproduce the issue with it?

@dmvtech Yes, i gave you access to the repository

Thank you. I was able to confirm this is a known bug and being tracked here:
https://github.com/microsoft/botbuilder-dotnet/issues/5757
I am closing this as the issue is identified. Please keep an eye out on the bug linked for resolution.


Support creating tags from custom properties

Custom properties are another way (in addition to game properties) to add arbitrary information to objects. With the game engine being removed in 2.80, custom properties will become the only way to get custom data to export as tags. Custom properties also exist in 2.7x, so support can be added in anticipation of 2.8x support.

The link above seems to be broken; does the following link describe what you're referring to?
https://docs.blender.org/manual/en/dev/files/data_blocks.html#custom-properties


Bootstrap-wysihtml5 no longer maintained

I have problem with warning in console:
'Range.detach' is now a no-op, as per DOM (http://dom.spec.whatwg.org/#dom-range-detach). wysihtml5.js:175
"Bootsy is a WYSIWYG editor for Rails based on Bootstrap-wysihtml5.."
I think for this fix is using based on bootstrap3-wysiwyg, check README of repo Bootstrap-wysihtml5:
This repo is no longer maintained. bootstrap3-wysiwyg is much better

Yeah, I receive complaints about that almost every week lol
I'll change it to a modern alternative in a near future. Stay tuned for new releases soon!

Good news, I just moved Bootsy to Bootstrap3-wysithml5 on master! Could you please give it a try? I'm planning to release a new version soon.


Implement parquetio for Go SDK

The naive approach would be reading the whole parquet file into memory, because processing parquet files requires io.Seeker
Or implement filesystem.go Interface to return io.ReadSeekCloser, but it would not be trivial for gcs
Imported from Jira BEAM-14304. Original Jira may contain additional context.
Reported by: nguyennk92.

Is it done given the #17347?

Not technically. That implementation reads an entire file into memory first, which can be very hard to work with.
This issue talks about working with Parquet and Google Cloud Storage.
https://github.com/googleapis/google-cloud-go/issues/1124
The CDK also punted on adding a wrapper itself, pointing out that it's also problematic for both S3 and Azure storage.
https://github.com/google/go-cloud/issues/3142#issuecomment-1174483410
It is interesting that it doesn't seem that difficult to make something compatible, but it is very direct. See https://github.com/xitongsys/parquet-go-source which demonstrates convenience wrappers for each of GCS, AWS, and Azure.
(The parquet io uses parquet-go/source, on a fully-read in blob of bytes).

Basically, with the existing ParquetIO it wouldn't be hard to swap the internals with the https://github.com/xitongsys/parquet-go-source package, which is Apache 2.0 liscenced, which is handy for enabling uses. It does sort of prevent the division of labour we have.

The main issue with the existing Parquet IO is that it's not a splitting source, and like most of the filesinks in the SDK, not very compatible with streaming/windowing etc.
So, it can't naturally split a large file, and it can't gracefully write out windowed data as an output.

The main issue with the existing Parquet IO is that it's not a splitting source, and like most of the filesinks in the SDK, not very compatible with streaming/windowing etc.
So, it can't naturally split a large file, and it can't gracefully write out windowed data as an output.

Hmmm. I still have a branch where I implemented a custom Parquet IO driver with Restrictions implemented, which was, IIRC, enough for Dataflow to read them fairly quickly.
I needed to convert a 1TiB full of Parquet files to CSVs on GCS, and it worked fairly well for the job. That said, it did an fs.OpenRead() and io.ReadAll() on GCS, so it wouldn't satisfy the OP, understandably. 🥲 I didn't put effort into that because our files where fairly small to fit into worker memory – those were AWS Aurora snapshot Parquet files, there are many of them, but they are not large.

Oh that's exciting! We do welcome contributions. PRs get more attention due to the automatic reviewer assignment, but do tag me for Go issues that need consultation.
Reading files all into memory isn't wrong BTW, it just needs to be a documented behavior for users to be able to reason about and plan for.


Spin the Web Spinner

A web spinner interpeters and renders WBDL. It is a web server. It also includes an API for managing WBDL.

Build API for managing WBDL

Each node in WBDL has a unique URI, a slash (/) separated list of slugs making up the path to reach the node. Repositioning a node redefines the URI.