feat(brokers/nats-jetstream): allow passing an existing nats connection

This PR allows to pass an existing connection, so we don't have to open multiple connections from the same service.

Remark: If a breaking API change is considered, I would even go so far as to remove the URL parameter completely and also remove the WithConnectionOpts. IMO the nats connection should always be handled on the outside to allow proper separation of concerns.
This would also solve edge cases like calling WithConnectionOpts multiple times, which would, at the moment, create multiple connections of which only the last one is closed.

@lerenn Our services are going to use this library a lot for multiple async docs. Therefore we are in the need to reuse the NATS connection so that we don't open multiple connections from the same service for different subscriber and/or publisher. Can you please have a look at this PR?
Thanks in advance! 🙏

Hello @aksdb and @stefanmeschke ! Looks good to me !
Thanks for contributing ☺
I'll merge it right away :)

Just fixed the lint, other jobs where good so I'll merge it :)

Hello @aksdb and @stefanmeschke ! Looks good to me !
Thanks for contributing ☺
I'll merge it right away :)

Awesome! Thank you! 🙏


[Typo] Extra word "the" between paragraphs

Extra "the" in this docs: https://docs.microsoft.com/en-us/SharePoint/administration/configure-usage-and-health-data-collection?redirectedfrom=MSDN#configure-usage-and-health-data-collection-by-using-central-administration

https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/blob/live/SharePoint/SharePointServer/administration/configure-usage-and-health-data-collection.md

Missing a left bracket leads to wrong markdown syntax.

Strange render effect that only the single word "where" is listed in a code block:

Consider to change the correspond markdown here:

Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

thanks for your feedback! @ZCplayground


Only scroll web console to the bottom if previously at the bottom

This allows the user to scroll back and read the console at their leisure, even if the console keeps getting new “Requesting content.” messages. If the user scrolls back to the bottom, the console will once again keep itself at the bottom when new messages are added.
I haven’t tested this change on the actual page. The only testing I did was playing around with the scrollTop, scrollHeight and clientHeight properties in the Web Console to figure out how to implement isScrolledToTheBottom.

@roryokane - Wow, thanks for your contribution!
The patch didn't quite work as-is: your function calls like isScrolledToTheBottom() needed to be this.isScrolledToTheBottom(), but I fixed those up and merged it in.
It's now deployed live, feel free to check it out! (The SHA-256 hash of the page doesn't change because only the submitted content is hashed, not the layout "frame" the content sits in.)


Tag "Fix error message of missing value with prefix" release

Hey,
sorry to bother you again @sethvargo, but this did not work https://github.com/sethvargo/go-envconfig/issues/30
You tagged the commit just one before the relevant one.
The correct commit to tag is https://github.com/sethvargo/go-envconfig/commit/aa9aceaee7ca3acc6620b01b3172be2d06990e16
Thanks

Thank you, that works.


shairport-sync: set sysconfdir to /etc/

since 2.8.5, shairport-sync uses the directory path sysconfdir to
determine where to place the configuration file shairport-sync.conf.
This led to shairport-sync complaining at startup:

configuration file name "/nix/store/i8gb0hsb2zczdl8g1h73pbcb952585l9-shairport-sync-3.2.2/etc/shairport-sync.conf" can not be resolved.

Looking for a configuration file there doesn't make much sense, as we'd
have to include configuration in the shairport-sync derivation itself.
By setting sysconfdir to /etc/, shairport-sync will try to read its
configuration from /etc/shairport-sync.conf, which is a more sane
default.
Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

shouldn't hurt to backport this to 19.03 either ;-)

backported to 19.03 in f70e66cccd5ac6e39f6de595b5f770b35601cf55.


cargo doc --open broken on Windows due to rustup proxy

The cargo doc --open command is currently broken on nightly Cargo on Windows. The implementation of this command recently changed in Cargo. This new implementation is affected by a bug in rustup's job object code on Windows.  The existing job object code was copied from Cargo. I recently fixed the job code in Cargo, which was also causing issues.
I intended on sending a pull request to rustup to apply the same fix, but I ran into a problem: The fix relies on a destructor to run when rustup exits, but rustup uses std::process::exit, which doesn't run destructors. I can think of two solutions; either move the std::process::exit call(s) outwards so that the calls can run after the destructors, or use a mechanism other than a destructor to run the necessary code.
Links
My branch with the fixed job code: https://github.com/Seeker14491/rustup.rs/tree/job
Line in rustup where the object whose destructor needs to run is created: https://github.com/rust-lang-nursery/rustup.rs/blob/22b6cdb8b000f9217af1dd5dd4e73ce032bdb25d/src/rustup-cli/proxy_mode.rs#L14

Sorry for the delay here @Seeker14491 are you still interested in working on this? Moving the calls to exit outwards seems like the best solution to me! https://github.com/rust-lang/cargo/issues/6029 is indeed a worrying issue and would be great to fix soon!

Sure, I'll give it a shot.


Translation ideas.

Source: Languages used on the Internet -> Content languages for websites (2017.07.16).
Note: Source does not distinguish between dialect variants, regional L10N, etc (for example, with Chinese, I would assume that the statistics includes both simplified and traditional writing variants, or with Portuguese, including both Portugal and Brazil variants alike).
For the purpose of this issue, I'm only listing the top 10 languages mentioned by the source page (there are 38 mentioned by the source list in total, plus a secondary list on the source page; because this issue is only intended to float some general ideas and doesn't concern any concrete goals or plans, being excessive isn't necessary).

Rank
Language
Percentage
Translation Coverage

1
English
51.6%
Original document language.

2
Russian
6.6%
Completed (thanks @tsybenko).

3
Japanese
5.6%
In progress Completed (thanks @arinco and @iogi).

4
German
5.6%
Not translated. Completed (thanks @kloener).

5
Spanish
5.1%
Not translated. Completed (thanks @marc-gr).

6
French
4.1%
Completed (thanks @flibustier and @Sinequanonh).

7
Portuguese
2.6%
Completed (thanks @marcossffilho).

8
Italian
2.3%
Not translated. Completed (thanks @matteocrippa).

9
Chinese
2.0%
Completed (thanks @GrayLand119 and @j-gao).

10
Polish
1.7%
Not translated.

The purpose of this issue is to suggest possible targets for future language translations, for anyone that might be interested in introducing new translations to the repository. This repository (at this time, currently) is being watched by 205 GitHub users and has 422 forks, and so, maybe this might be useful for someone looking for possible target languages. The logic/rationale here is to hopefully encourage translation of the repository to those languages perceived as being most widely used on the internet (and thus, within the realm of the relevant scope of this repository). Using alternative sources may yield very different results.
Based on the above-mentioned information, these could be good possible target languages for translation at this time:

German. (translation added 2017.07.20).
Spanish. (translation added 2017.07.17).
Italian. (translation added 2017.07.18).
Polish.

Also worth mentioning that because this repository is very young and is still a living document, the possibility of data between translations becoming out-of-sync is quite high. There should be no urgency here.

@Maikuolan just made a PR for italian

Awesome! Cheers. :-)

@Maikuolan hey, I create PL translation :)
https://github.com/shieldfy/API-Security-Checklist/pull/95

Awesome! Thanks for the help, @pilotpirxie. :+1: 😊

Of course, continued translations are always welcome, but due to that all the translations specifically suggested by this issue have now been completed as of this most recent PR, thus meaning there aren't any more "to-do" items here, I'll mark this issue as closed,


deps: update hashbrown to 0.12.1

This will need a new version (minor since hashbrown is used in the public interface)


Update basic auth connections link to configs

Fixes #1462
I could not find any doc relating to scraping configs. Hence I linked the http config section under alerting configs.

@brian-brazil please have a look and let me know any changes that should be done.

That doesn't seem to do it: https://deploy-preview-1463--prometheus-docs.netlify.com/docs/guides/basic-auth/

Thanks!


Tantivy FTS support at the Rust level

One idea I had during my experiments was that there's clearly some level of blocking by the Python GIL going on when passing a LanceDB FTS query down to the FTS index layer via tantivy-py. This will always make concurrency an issue when issuing FTS queries at the LanceDB level.
Feature request
I think it makes sense to add a feature request here: In a future version, perhaps it makes sense to incorporate tantivy's Rust crate with LanceDB instead of tantivy-py? And expose a Rust API that allows users at the LanceDB level (regardless of whether they use Python or JS) to run FTS queries with true concurrency via Rust tantivy. This would massively improve FTS query performance in a way that blows Elasticsearch/Opensearch out of the water.

Work ongoing upstream in https://github.com/lancedb/lance/issues/1195


[Documentation]: from llama_index.readers.github import GithubRepositoryReader is not in 0.10.6, where is it?

Documentation Issue Description
This docs page suggests that I can get the GithubRepositoryReader class from
from llama_index.readers.github import GithubRepositoryReader
But does not appear to be the case in 0.10.6.
This is the pip freeze of my llama deps
llama-hub==0.0.79.post1
llama-index==0.10.6
llama-index-agent-openai==0.1.1
llama-index-core==0.10.6.post1
llama-index-embeddings-openai==0.1.1
llama-index-legacy==0.9.48
llama-index-llms-openai==0.1.2
llama-index-multi-modal-llms-openai==0.1.1
llama-index-program-openai==0.1.2
llama-index-question-gen-openai==0.1.1
llama-index-readers-file==0.1.3
llamaindex-py-client==0.1.12

looking at llama_index structure inside of Lib/site-packages I see
llama_index/readers/file/*
but github is not there either. I would suggest a fix to the docs but I am not sure where that class lives now...
Documentation Link
https://docs.llamaindex.ai/en/stable/examples/data_connectors/GithubRepositoryReaderDemo.html

@aaronjolson I believe tbh at the first line of the notebook/doc indicates that llama-index-readers-github package needs to be installed.

Yea, @nerdai is correct 👀
pip install llama-index-readers-github
v0.10.x separated integrations into packages.
In case you missed the updates, here's a few helpful links below
A full package registry is here
https://pretty-sodium-5e0.notion.site/ce81b247649a44e4b6b35dfb24af28a6?v=53b3c2ced7bb4c9996b81b83c9f01139
The migration guide also includes tips on a helpful CLI tool to help migrate your older code and identify imports
https://pretty-sodium-5e0.notion.site/v0-10-0-Migration-Guide-6ede431dcb8841b09ea171e7f133bd77

@logan-markewich - I see that now, thank you!
One of the big selling points of llama-index is all of the available integrations. Going forward, if these are all going to be broken out into their own packages, how will discoverability be addressed? How do developers find all of the available integrations? We can no longer just read the source code from llama-hub to find all of the available integrations...


remove np.datetime64 from S1, make adding two TimestampSeries fail

Turns out that it is not possible to have a Series containing np.datetime64 types - they get converted to Timestamp.  Discovered this with some experiments that showed we were allowing two Series of Timestamp to be added, which is not possible, so fixed that as well.

Thanks @Dr-Irv


Steps update sdk

Error was:
Failed to clone step (https://github.com/guitcastro/steps-update-sdk.git): Commit hash doesn't match the one specified for the version tag. (version tag: 1.0.0) (expected commit hash: 141c81917e966d8674904c042b0e5029c8880152) (got: edce6ca14cda2286ce2465248560cb4815255c0a)

Can you please:

delete the PR
delete the branch from your forked bitrise-steplib
re-share the step
create a new 1.0.0 / 1.0.1 release of your step (you don't have to start with 1.0.0)

This should solve the issue.


API updated to atom v1.02 compatible

fixed:

#2 #3 (use highlights)
#4 #5 #6
#7 #8 (atom.ScrollView is deprecated, i use atom-space-pen-views)

@yhsiang ping...

@jhen0409 1 month and no response. :-/ Time for an official fork?

@chrisvfritz ok :/
I published new package "ls-compile". In order to continue to use. :)


Is this still maintained ?

Since the last commit is from 4.April 2019 ?

I don't think anybody is maintaining this (per similar unanswered questions in #33 and #56).

I advise taking a look at this similar project: https://github.com/nodesecurity/eslint-plugin-security/issues/56#issuecomment-575181090

Note also, the last ~15 commits are not published to NPM, while the last commit is about 3 years old, the latest release is about 5 years old now.

It is now. See #71


how to install .net 6 in centos 8?

how to install .net 6 in centos 8 please?
"*CentOS 8 will reach an early End Of Life (EOL) on December 31st, 2021. For more information, see the official CentOS Linux EOL page. Because of this, .NET 6 won't be supported on CentOS Linux 8."
https://docs.microsoft.com/en-us/dotnet/core/install/linux-centos#centos-8-

The CentOS distribution is being discontinued, and as such new releases of .NET won't be supporting it. cc @Thraka @leecow

Thank you!

FWIW, .NET 6 is available as a part of RHEL 8 repositories, so it's possible that the CentOS 8 maintainers will build .NET 6 and include it too, when they update CentOS to match the RHEL 8.5 release.

@eiriktsarpalis My understanding of CentOS 8 is not that they are discontinuing it, but rather changing it's distribution model. CentOS 8 stream is the replacement distribution, and is still CentOS 8 no? Also it gives it extended support till 2024. Why drop the support all together for the OS, when it still will be supported for so long?

CentOS 8 Stream is very much supported. Is there a way to install the .NET 6 on CentOS 8?

Since Centos, Alma, Rocky, etc... are red hat(Enterprise Linux) binary compatible, why not just produce a Enterprise Linux install?
The .net that comes via the red hat repos is usually not always at the current released version. We need a repo that we can install from for Enterprise Linux compliant distros that contains current released version. Especially when there is security updates.

In general, .NET packages are included with CentOS Stream 8 (eg, sudo dnf isntall dotnet-sdk-3.1 should work out of the box)
We have been having some trouble with .NET 6, though. The CentOS 8 maintainers pinged me a few weeks ago about a bug building .NET 6 on CentOS 8, and I couldn't reproduce it. I just narrowed it down to https://github.com/dotnet/source-build/issues/2731 and we are still trying to understand what the issue is and how to fix it.
@goforgold In the meantime, try a manual install: https://docs.microsoft.com/en-us/dotnet/core/install/linux-scripted-manual


I think VS Code deleted my Git history after a file rename

Issue Type: Bug
I can't reproduce it but here is what happened:
After a few weeks of inactivity on a local Git repository, I opened VS Code on 3/20/18, updated to the latest release and renamed my index.html and style.css files to indexold.html and styleold.css respectively. I also edited the HTML file to point to the same CSS file with the new name. Then I reconsidered and named it back to the original name.
I made no commits, branches or any Git changes at this point.
Next day, I open VS Code and wanted to create a new branch. I click on the branch button on the bottom-left corner and I see there are no branches to checkout.
Not realizing this means the branch is blank, I clicked on Create new branch and named it "Cleaner". Then I go to Git Checkout again looking for the master branch. Now I see it's not there and I realize everything was lost. I tried to run git reflog and other online suggestions but only got fatal errors.
The Git repository is blank after a few weeks of inactivity and only changing file names with VS Code.
VS Code version: Code 1.21.1 (79b44aa704ce542d8ca4a3cc44cfca566e7720f1, 2018-03-14T14:46:47.128Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
AMD A8-4500M APU with Radeon(tm) HD Graphics    (4 x 1896)

Memory (System)
3.46GB (0.64GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe D:\Documents\Coding\Portfolio.code-workspace

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

LiveServer
rit
3.2.1

Reproduces only with extensions

Without reproducible steps, I find it hard to keep this issue open. Code won't simply delete your data.
Let me know if it happens again.


Add matrix-multiplication functionality

Implement the logic to handle addition operations when a POST request is made to the /math/matrixmultiplication endpoint. Additionally, write appropriate test cases within the test/test_app.pyfile to validate this functionality.

I want to contribute to this task...
Please assign this to me.

Hello ,@AimenYaseen I have assigned the issue to you .Please stick with the contribution guidelines and update me with the progress.


Refactor/llm client template methods pattern

Adding anthropic_client.py
Separate the work content of different AIs to openai_client.py and anthropic_client.py
Implement LLMClientTemplate
seperate ai_respond()  to:
1.extract_search_keywords
2.generate_summary
3.evaluate_relevance
also Implement LLMClientTemplate on three functions above
Add test_news_summary_with_custom_model
update new test in test_news_endpoint.py to test refactored code

Your CI didn't pass!


xRFC TP3: Error Propagation

Proposal for the xDS error propagation which allows xDS management servers to provide additional information to the clients in case of errors like permission errors or resource being missing.
cc: @markdroth, @adisuissa, @htuch

This looks great!
Please fix CI, so that we can get this merged. Thanks!

@markdroth This should now be fixed!


firebase-auth interrupts

 doesn't finish authentication pocess.
If I use signInWithPopup() - the popup disappears immediately.
On signInWithRedirect() - it starts neverending chain of redirects forth and back without authentication.
I use Polymer 2.0 and polymerfire#2.0-preview

I've something similar at login as well. Sometimes works and others I'm getting:
code: "auth/network-request-failed"message: "A network error (such as timeout, interrupted connection or unreachable host) has occurred."__proto__: Error
(anonymous) @ firebase-auth.js:39

Not sure what it is yet.


chore(deps): update common-dev-assets digest to 1b62a74

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
e4ce78d -> 1b62a74

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

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

GitHub release
v5.3.0

Your semantic-release bot :package::rocket:


Bug Report: Pico Crash

I am using the 1.6.2 release of the kade engine and whenever I test week 3, I can get past the first song, but after that the game would crash. I have checked this multiple times and always get the same outcome.

this happened to me, i have to do all songs in freeplay because if i don't complete week 3, other weeks won't unlock, and with the first song crashing all the time, it doesn't register anything, not even my score, about crashing, after the week end kade engine crashes with the only exception being week 2

@davimandel check this solution for locked weeks by joelwindows, it works like a beauty and saves you loads of time: https://gamebanana.com/questions/14816

thanks
Em dom., 22 de ago. de 2021 às 02:55, Behnja @.***>
escreveu:

@davimandel https://github.com/davimandel check this solution for
locked weeks by joelwindows, it works like a beauty and saves you loads of
time: https://gamebanana.com/questions/14816
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KadeDev/Kade-Engine/issues/1860#issuecomment-903218143,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVJNCMNA6AVZLAU4ZCW77T3T6CGOZANCNFSM5CRGR3KA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


request response route buffering

Required for https://github.com/Kong/kubernetes-ingress-controller/issues/924.

chore: add codegen info to README.md
feat: add req/resp route buffering options

 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.

 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.


 This resulted in an (infinite?) loop and hanged my application.
The minimal example below reproduces this. This example uses an in-memory database, but it occurs with a database file as well.
Version: v1.14.7
db, err := sql.Open("sqlite3", ":memory:")
if err != nil {
	panic(err)
}
defer db.Close()

stmt, err := db.Prepare("") // empty query
if err != nil {
	panic(err)
}
defer stmt.Close()

rows, err := stmt.Query()
if err != nil {
	panic(err)
}
defer rows.Close()

count := 0
for rows.Next() {
	var dummy string
	rows.Scan(&dummy) // this can be omitted

	log.Printf("%d: [%+v]\n", count, dummy)
	count++
}

Results in:
0: []
1: []
2: []
3: []
4: []
...

 Maybe return an error?

The source of the bug is that sqlite3_prepare_v2 produces a null *sqlite3_stmt with no error when you do this. But this library does not check for that. https://github.com/mattn/go-sqlite3/blob/d33341ff0d20a3b46047dba17ad897b40705c563/sqlite3.go#L1749-L1752
Compounding the issue, each call to sqlite3_step will fail with SQLITE_MISUSE, but it gets dropped because of this:
https://github.com/mattn/go-sqlite3/blob/d33341ff0d20a3b46047dba17ad897b40705c563/sqlite3.go#L2105-L2111
Basically, sqlite3_reset always vacuously succeeds when giving a null statement, so we end up returning null from each call to Next(). Thus the loop never terminates.
Thus there are two bugs in play:

If sqlite3_prepare_v2 yields SQLITE_OK with a null prepared statement it should be treated as an error.
If sqlite3_reset yields SQLITE_OK after sqlite3_step fails we should still return an error. (Note: We can't just call lastError() in a situation like this since it might not be set properly. Maybe just convert to an ErrNo?)

@rittneje Shouldn't simply returning io.EOF instead of nil in the no rows nextSyncLocked check resolve the issue?

Considering that there a few bugs in this library that are due to sqlite3_prepare_v2 not being used properly (https://github.com/mattn/go-sqlite3/issues/1161 comes to mind) and that there might be existing user programs that rely on said broken behavior has there been any discussion of creating a v2 branch that resolves these issues without maintaining backwards compatibility for programs that rely on the current (and sometimes broken) behavior?


Only require sign-off on PRS

Whoops! Follow-up to #598
Hopefully fixes the problem seen in https://github.com/matrix-org/complement/actions/runs/4108255185

(completely untested)


Proposal: to new way to make FAQ page

description
I create a new way to build a FAQ page, it's more simple and prevent bug when we remove link questions.

Use map to render our questions and add a <CodeArea ... /> inside a faq json.
Use a REMOVE_QUESTIONS_FOR_LIST variable to say how much questions we need to remove on render.
Create a new example code file to question Why is the first keystroke not working? before this code is inline on project.

Bug fix.
This new implementation  fix a issue on FAQ page on production. We have a question that doesn’ t appear on sidebar menu.  Now the sidebar menu and questions is linked if appear on menu appear on question view.

@bluebill1049 I closed the last PR and create this new.

@bluebill1049 I updated a node version on lighthouse pipeline, they required a node 14.x and we use 12.x

Oh wow nice 😊 thank you so much for the fix and contribution!

Thank's @bluebill1049


Trying to compile for fedora

I have finally figure out what files I needed to compile. I have not been able to execute the code. its giving me location issues missing .so.1 files etc...  trying to compile for Fedora 29

It seems that by default the LD_LIBRARY_PATH environment variable is empty.
Try doing export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/ just before running EzGraverUI.
Also, if you're using Wayland, you will have add another one. this works for me:
export QT_QPA_PLATFORM=wayland; ./EzGraverUi/EzGraverUi

or copy all lib to elf program and run
LD_LIBRARY_PATH=. ./EzGraverUi


[Feature Request]: Update cibuildwheel to latest version for building wheels

What would you like to happen?
RIght now, the beam python sdk uses cibuildwheel==1.11.0 that use get-pip.py to install the PyPI dependencies. There has been some issues related to get-pip.py, setuptools>=60.0 and distutils, which causes the RC wheels build to fail.
As of now, the workaround has been added at  https://github.com/apache/beam/pull/22636  and https://github.com/apache/beam/pull/22635 by introducing the environment variable SETUPTOOLS_USE_DISTUTILS=stdlib. This can be removed once the cibuildwheel gets updated to a latest version.
cibuildwheel is not updated as part of the solution because it was taking so much time to build the aarch wheels and it causes time outs while building the RC wheels.
Issue Priority
Priority: 2
Issue Component
Component: sdk-py-core

related PRs: https://github.com/apache/beam/pull/22635, https://github.com/apache/beam/pull/22635

Is this completed?

.close-issue


Subscribe depth@100ms, return empty content

Changed subscribed stream at context.py, trade.rs and chat.rs
In demo.py:
sub = session.subscribe("dogefdusd", "depth@100ms")
return:
Datetime: 2024-06-24 01:19:22.493000+08:00, Symbol: dogefdusd
Best Bid Price: 0.0, Best Bid Quantity: 0.0
Best Ask Price: 0.12294, Best Ask Quantity: 46397.0
Datetime: 2024-06-24 01:19:22.793000+08:00, Symbol: dogefdusd
Best Bid Price: 0.0, Best Bid Quantity: 0.0
Best Ask Price: 0.12293, Best Ask Quantity: 51631.0
Datetime: 2024-06-24 01:19:22.893000+08:00, Symbol: dogefdusd
Best Bid Price: 0.12287, Best Bid Quantity: 35245.0
Best Ask Price: 0.12292, Best Ask Quantity: 21617.0
Datetime: 2024-06-24 01:19:22.993000+08:00, Symbol: dogefdusd
Best Bid Price: 0.0, Best Bid Quantity: 0.0
Best Ask Price: 0.12292, Best Ask Quantity: 23650.0
Datetime: 2024-06-24 01:19:23.093000+08:00, Symbol: dogefdusd
Best Bid Price: 0.0, Best Bid Quantity: 0.0
Best Ask Price: 0.0, Best Ask Quantity: 0.0

depth@100ms is not supported currently, but I will implement it

bbo,depth:100ms is avaliable now, please pull the lastest code and rebuild xcrypto, pyalgo. market stream details can be found in README.md. best wishes for your trading


tests: net: dns_addremove: increase main stack size

We need to increase the stack size of the main thread, to
avoid stack overflow, when executing the tests on various
platforms.
Signed-off-by: Ioannis Glaropoulos<EMAIL_ADDRESS>

Seen currently on sam_e70_xplained only (passed on frdm_k64f)


Error when trying to build binaries  for ubuntu when following the readme.md

Greetings,
I have made a few minor changes to labelImg and I want to build a standalone application for Ubuntu.
I followed the instructions in build-tools/readme but it fails when running sh build-ubuntu-binary.sh.
By the way I don't understand why we'd need to run a docker container on the side to build the binary (this is performed by run-in-container.sh).
Here is the error that I get when running sh build-ubuntu-binary.sh :
(xxii-labelimg) arno@Arno-Ubuntu:~/Workspace/LabellingTools/xxii-labelimg/build-tools$ sh build-ubuntu-binary.sh
HEAD est maintenant sur e98b70e7 Finished release 3.2.
83 INFO: PyInstaller: 3.2
84 INFO: Python: 3.6.14
84 INFO: Platform: Linux-5.8.0-59-generic-x86_64-with-Ubuntu-20.04-focal
84 INFO: wrote /home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/labelImg.spec
86 INFO: UPX is not available.
87 INFO: Extending PYTHONPATH with paths
['/home/arno/Workspace/LabellingTools',
 '/home/arno/Workspace/LabellingTools/xxii-labelimg/libs',
 '/home/arno/Workspace/LabellingTools/xxii-labelimg',
 '/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools']
87 INFO: checking Analysis
87 INFO: Building Analysis because out00-Analysis.toc is non existent
87 INFO: Initializing module dependency graph...
88 INFO: Initializing module graph hooks...
89 INFO: Analyzing base_library.zip ...
Traceback (most recent call last):
  File "pyinstaller/pyinstaller.py", line 15, in <module>
    run()
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/__main__.py", line 90, in run
    run_build(pyi_config, spec_file, **vars(args))
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/__main__.py", line 46, in run_build
    PyInstaller.building.build_main.main(pyi_config, spec_file, **kwargs)
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/building/build_main.py", line 788, in main
    build(specfile, kw.get('distpath'), kw.get('workpath'), kw.get('clean_build'))
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/building/build_main.py", line 734, in build
    exec(text, spec_namespace)
  File "<string>", line 16, in <module>
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/building/build_main.py", line 212, in __init__
    self.__postinit__()
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/building/datastruct.py", line 178, in __postinit__
    self.assemble()
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/building/build_main.py", line 317, in assemble
    excludes=self.excludes, user_hook_dirs=self.hookspath)
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/depend/analysis.py", line 560, in initialize_modgraph
    graph.import_hook(m)
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/lib/modulegraph/modulegraph.py", line 906, in import_hook
    q, tail = self._find_head_package(parent, name, level)
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/lib/modulegraph/modulegraph.py", line 990, in _find_head_package
    q = self._safe_import_module(head, qname, parent)
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/depend/analysis.py", line 209, in _safe_import_module
    module_basename, module_name, parent_package)
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/lib/modulegraph/modulegraph.py", line 1211, in _safe_import_module
    module_name, file_handle, pathname, metadata)
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/lib/modulegraph/modulegraph.py", line 1295, in _load_module
    self._scan_code(m, co, co_ast)
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/lib/modulegraph/modulegraph.py", line 1460, in _scan_code
    self._scan_bytecode_stores(co, m)
  File "/home/arno/Workspace/LabellingTools/xxii-labelimg/build-tools/pyinstaller/PyInstaller/lib/modulegraph/modulegraph.py", line 1505, in _scan_bytecode_stores
    name = co.co_names[oparg]
IndexError: tuple index out of range
cp: impossible d'évaluer 'dist/labelImg': Aucun fichier ou dossier de ce type
updating: linux_defaultLabelError/ (stored 0%)
updating: linux_defaultLabelError/data/ (stored 0%)
updating: linux_defaultLabelError/data/tags.yaml (deflated 13%)
updating: linux_defaultLabelError/data/predefined_classes.txt (stored 0%)

I have never used pyinstaller before, I'm watching tutorials at the moment but for now I have now idea what to try in order to make this work.
Thanks in advance, any suggestion would be appreciated.

OS:Ubuntu 20.04
PyQt version:5.15.4

I fixed this by making a build script from scratch, and I can now successfuly compile a clickable executable for Ubuntu.
I removed everything in the build-tools directory and instead put my own shell script in this directory.

I execute this from a Pipenv, here is the related Pipfile:
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
lxml = "==4.6.3"
PyQt5 = "==5.15.4"
pyqtchart = "==5.15.4"
pyyaml = "==5.4.1"

[dev-packages]
pyinstaller = "==4.5.1"

[requires]
python_version = "3.6"

Don't forget to install the pipenv with pipenv install --dev to install pyinstaller as well.
Cheers !


Scrolling all the way up in terminal accessible buffer cuts off text

Testing #174625

I haven't had reports of this being an issue for screen reader users, thus closing


Filter (blur) seem not to work on canvas

I'm checking out some of the examples on the pixijs examples page and at least 15b and 15c seem not to work. None of the filters on 15c work and there's no blur on 15b
I'm checking it out on a laptop which doesn't support webgl

Hi, it would be very handy if the docs had a note about the support. Thank you

Good shout @zumek! Would be ace if you could submit a PR for that 👍


Getting input event consistency errors

On api level 19 I'm constantly getting
InputEventConsistencyVerifier: TouchEvent: ACTION_DOWN but pointers are already down.  Probably missing ACTION_UP from previous gesture.
  in android.view.GestureDetector@ad008e20

this causes some onDawn events not to register, so screen does not respond.

on emulator? I will try

I changed line 191 from SampleActivity:
        if (event.getAction() == MotionEvent.ACTION_UP) {             mPageFlipView.onFingerUp(event.getX(), event.getY());             return true;         }
to:
        if (event.getAction() == MotionEvent.ACTION_UP) {             mPageFlipView.onFingerUp(event.getX(), event.getY());             return mGestureDetector.onTouchEvent(event);         }
Seems to have solved the problem.

Good catch, I will take a look, thanks!


Couchbase-config-tweak

@benfrank241 has this PR be replaced by a more recent one? If so, can we close?


problem about ”sh compile_wrappers.sh ”

(kpconv) czh@dirac:~/project/KPConv/cpp_wrappers$ sh compile_wrappers.sh
running build_ext
building 'grid_subsampling' extension
Warning: Can't read registry to find the necessary compiler setting
Make sure that Python modules winreg, win32api or win32con are installed.
C compiler: gcc -pthread -B /farm/czh/anaconda3/envs/kpconv/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC
creating build
creating build/temp.linux-x86_64-3.6
creating build/temp.linux-x86_64-3.6/cpp_wrappers
creating build/temp.linux-x86_64-3.6/cpp_wrappers/cpp_utils
creating build/temp.linux-x86_64-3.6/cpp_wrappers/cpp_utils/cloud
creating build/temp.linux-x86_64-3.6/grid_subsampling
compile options: '-I/farm/czh/anaconda3/envs/kpconv/lib/python3.6/site-packages/numpy/core/include -I/farm/czh/anaconda3/envs/kpconv/include/python3.6m -c'
extra options: '-std=c++11 -D_GLIBCXX_USE_CXX11_ABI=0'
gcc: ../cpp_utils/cloud/cloud.cpp
gcc: grid_subsampling/grid_subsampling.cpp
gcc: wrapper.cpp
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
In file included from /farm/czh/anaconda3/envs/kpconv/lib/python3.6/site-packages/numpy/core/include/numpy/ndarraytypes.h:1830:0,
from /farm/czh/anaconda3/envs/kpconv/lib/python3.6/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /farm/czh/anaconda3/envs/kpconv/lib/python3.6/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from wrapper.cpp:2:
/farm/czh/anaconda3/envs/kpconv/lib/python3.6/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
#warning "Using deprecated NumPy API, disable it with "
^~~~~~~
grid_subsampling/grid_subsampling.cpp: In function ‘void grid_subsampling(std::vector&, std::vector&, std::vector&, std::vector&, std::vector&, std::vector&, float, int)’:
grid_subsampling/grid_subsampling.cpp:99:25: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < ldim; i++)
^~~~
wrapper.cpp: In function ‘PyObject* grid_subsampling_compute(PyObject*, PyObject*, PyObject*)’:
wrapper.cpp:70:98: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
static char kwlist[] = {"points", "features", "classes", "sampleDl", "method", "verbose", NULL };
^
wrapper.cpp:70:98: warning: ISO C++ forbids converting a string constant to ‘char’ [-Wwrite-strings]
wrapper.cpp:70:98: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
wrapper.cpp:70:98: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
wrapper.cpp:70:98: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
wrapper.cpp:70:98: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
g++ -pthread -shared -B /farm/czh/anaconda3/envs/kpconv/compiler_compat -L/farm/czh/anaconda3/envs/kpconv/lib -Wl,-rpath=/farm/czh/anaconda3/envs/kpconv/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.6/cpp_wrappers/cpp_utils/cloud/cloud.o build/temp.linux-x86_64-3.6/grid_subsampling/grid_subsampling.o build/temp.linux-x86_64-3.6/wrapper.o -o /farm/czh/project/KPConv/cpp_wrappers/cpp_subsampling/grid_subsampling.cpython-36m-x86_64-linux-gnu.so

Hello @Codeczh,
If you only post a log without any explanation, I won't be able to help you. I don't even see an error in the log you printed, only warnings.
Could you elaborate more on your problem?

@HuguesTHOMAS  Thank you for your reply. I just find the reason that my sever installed cuda10, not supported as the readme said.

I'm also having similar errors. I am using a conda enviorment with tensorflow 1.10.0(tried 1.12.0 and still had an error). I'm using ubuntu 18.04, but have switched to different gcc versions, so that's not the problem. I also have cuda 9.0 and cudnn 7.4.5 installed.
I fixed these errors:
ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
static char kwlist[] = {"points", "features", "classes", "sampleDl", "method", "verbose", NULL };
and
\comparison between signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < ldim; i++)
but the compile_wrappers is still not compiling.

I fixed it. You set CC to where gcc is and CXX to where g++ is


[SPARK-37243][SQL][DOC] Fix the format of the document

What changes were proposed in this pull request?
This PR proposes fix the format of the document in sql-ref-syntax-dml-insert-overwrite-table.md
Currently, the format is :

It should be normal like other parts
Why are the changes needed?
A minor format problem
Does this PR introduce any user-facing change?
yes
How was this patch tested?
manual test

Can one of the admins verify this patch?

cc @yaooqinn Could you take a look when you have a time?

Test build #145001 has started for PR 34521 at commit d96ddf6.

Test build #145001 has finished for PR 34521 at commit d96ddf6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49473/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145001/

Any other fixes like this?

No other similar problems have been found for the time being

Merged to master. Looks like it might not be needed in 3.2 as it doesn't cherry-pick

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49473/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49473/


Step is not working using value from scope

Hello,
This one works
<rzslider
rz-slider-step="10"
rz-slider-floor="priceSlider.floor"
rz-slider-ceil="priceSlider.ceil"
rz-slider-model="priceSlider.min"

This one doesn't
<rzslider
 rz-slider-step="priceSlider.step"
rz-slider-floor="priceSlider.floor"
rz-slider-ceil="priceSlider.ceil"
rz-slider-model="priceSlider.min"

Given
$scope.priceSlider = {
min: 100,
max: 180,
ceil: 500,
floor: 0,
step:10
};
Thanks for the great plugin

Fix it myself :
Line 1029
rzSliderStep: '@',
=>
  rzSliderStep: '=?',

Yes it doesn't work. Values become NaN and the slider gets stuck.

Could you please provide a JSFiddle showing the issue?

hey folks, I already gave the fix , didn't I. See the 2nd post.
Open the source file,
Line 1029
rzSliderStep: '@',
=>
rzSliderStep: '=?',
Thanks

I think setting the rzSliderStep as a string attribute was on purpose because it was not supposed to be changed. Maybe for performance reason, the author didn't want to use Two-way model binding.
Changing it may break existing applications using the slider so it has to been think twice...
For now, you can simply use {{}} to interpolate your value like this:
<rzslider
 rz-slider-step="{{ priceSlider.step }}"
rz-slider-floor="priceSlider.floor"
rz-slider-ceil="priceSlider.ceil"
rz-slider-model="priceSlider.min"

Live saved. Been banging my head against this issue for a day!

With #158, this problem will be gone.


Closes Immediately

I need help, i dont know how to solve following errors:

Added python-dotenv to requirements.txt. You can create a virtual environment and install packages in requirements.txt
pip install -r requirements.txt


feat(jest) update Jest builder to use jest-preset-angular v7

This PR replaces the deprecated setupTestFrameworkScriptFile with the new setupFilesAfterEnv option. I also updated the schema.json with the new option and details per the Jest documentation.
This closes #239 and potentially #193
This is my first PR on your project, so feel free to let me know if things should be done differently, or if I should follow a different naming convention.

I see the build failed, but I'm not sure it's related to this code.
Here's the error from Travis:
Failed: "Zone is needed for the async() test helper but could not be found. Please make sure that your environment includes zone.js/dist/zone.js"

First of all thanks for your contribution! The error is related to your change.
The failing part is the e2e test for this builder. It fails because the version of Jest it uses won't recognize setupFilesAfterEnv option. The fix for this is to change the Jest version the corresponding example application depends on.
Another thing to consider here is that the builder uses Jest as peerDependency, therefore it should support both options (old and new) depending on the installed version of Jest in host application.
It would be also cool to add an e2e test that actually tests that both user-specified and builder-defined setup files are executed.

First of all thanks for your contribution! The error is related to your change.
The failing part is the e2e test for this builder. It fails because the version of Jest it uses won't recognize setupFilesAfterEnv option. The fix for this is to change the Jest version in the corresponding example application.
Another thing to consider here is that the builder uses Jest as peerDependency, therefore it should support both options (old and new) depending on the installed version of Jest in host application.
It would be also cool to add an e2e test that actually tests that both user-specified and builder-defined setup files are executed.

Thanks, I will take a look at the e2e test.

The node 10 build failed, but looks like due to timeout. Can you confirm? The node 8 build did succeed.

I restarted the node 10 build. Look like timeout error indeed. However even if it passes I can't merge this PR yet. As I mentioned, both versions shall be supported and the correct one should be applied depending on host Jest version.
Jest team are deprecating it gradually (showing a deprecation warning), I think we should do the same.

I restarted the node 10 build. Looks like timeout error indeed. However even if it passes I can't merge this PR yet. As I mentioned, both versions shall be supported and the correct one should be applied depending on host Jest version.
Jest team are deprecating it gradually (showing a deprecation warning), I think we should do the same.

I'm not exactly sure how to accomplish checking the installed Jest version, but I will dig in and let you know what I find!
Thanks.

@wesleygrimes Gave it a second thought. Seems that it's not possible to support both versions of Jest in a single version of the builder, because the builder is tied to a specific version of jest-preset-angular which, in turn, works with specific version of Jest.
Btw, I've just noticed that in this PR you've changed the version of Jest for the builders project, instead of changing the versions of preset in Jest builder package.
Check out this issue for the proper changes.

Thanks! I will take a look and get this PR updated.
-Wes

On Mar 11, 2019, at 6:32 PM, Evgeny Barabanov<EMAIL_ADDRESS>wrote:
@wesleygrimes Gave it a second thought. Seems that it's not possible to support both versions of Jest in a single version of the builder, because the builder is tied to a specific version of jest-preset-angular which, in turn, works with specific version of Jest.
Btw, I've just noticed that in this PR you've changed the version of Jest for the builders project, instead of changing the versions of preset in Jest builder package.
Check out this issue for the proper changes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@meltedspark I've updated this PR with insight from #266
Do you want me to also include the changes from #266 that update the default-config.resolver.ts and  default-config.resolver.spec.ts? I don't think these changes are necessary as it's just the underlying config file that changes.
I am open to your thoughts.
Thanks!
Wes

@enten @meltedspark
I have incorporated @enten changes from #266, but it is now failing in the mutliple-app and single-app tests. I have to step away for a while, but welcome any feedback and assistance in getting these to pass.
Thanks!

@wesleygrimes
I tried to investigate why multiple-app and single-app tests failed.
Unfortunately, I don't found how to fix them.
I didn't succeed to compile AppComponent during test because its template html file can't be load. I encountered next error: Failed: "Failed to load app.component.html".
I wondered if zone-patch works well because beforeEach function doesn't seem to succeed. Eventually due to a silent error (about template html which can't be load).

Yeah same here. Maybe @meltedspark can point us in the right direction?
-Wes

On Mar 13, 2019, at 5:17 PM, Steven Enten<EMAIL_ADDRESS>wrote:
@wesleygrimes
I tried to investigate why multiple-app and single-app tests failed.
Unfortunately, I don't found how to fix them.
I didn't succeed to compile AppComponent during test because its template html file can't be load. I encountered next error: Failed: "Failed to load app.component.html".
I wondered if zone-patch works well because beforeEach function doesn't seem to succeed. Eventually due to a silent error (about template html which can't be load).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

The projects use lock files (yarn lock), so it's not enough to change the dependency version in package.json. In order to apply it correctly you have to run yarn add [-D] dep@dep-version.

Oh duh! That makes sense! Thanks. I will run yarn when I get to my desk this morning and push a new commit.
Is there a contributing readme somewhere? If not maybe we can put one together and put down some notes on how to pull down the repo and test, etc..
Thanks!
-Wes

On Mar 14, 2019, at 4:11 AM, JeB<EMAIL_ADDRESS>wrote:
The projects use lock files (yarn lock), so it's not enough to change the dependency version in package.json. In order to apply it correctly you have to run yarn add [-D] dep@dep-version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Is there a contributing readme somewhere? If not maybe we can put one together and put down some notes on how to pull down the repo and test, etc..

That's a great idea, definitely need to have one!

The projects use lock files (yarn lock), so it's not enough to change the dependency version in package.json. In order to apply it correctly you have to run yarn add [-D] dep@dep-version.
Also, I saw that you removed completely the transform property. Why is that?

@enten can you speak to why we removed the transform property? Was this a compatibility issue with jest-preset-angular?

@wesleygrimes @meltedspark
It's important to note that jest-preset-angular/preprocessor.js doesn't exist anymore (since jest-preset-angular v7.0.0-alpha.0).
Previously we override transform to set absolute path to the preprocessor. Now jest-preset-angular uses ts-node directly for ^.+\\.(ts|js|html)$ files.
According to jest-preset-angular v7.0.1 migration guide:

If transform was overridden, remove the entry pointing at preprocessor.js and add "^.+\\.(ts|js|html)$": "ts-jest" to the transform-object.

Initially, I thought that we don't need to override transform property. So we removed the transform property.
Finally, after that @meltedspart reminded me the purpose of Jest builder, I think that we need to override transform property to ensure that a jest custom config forget to declare "^.+\\.(ts|js|html)$": "ts-jest" again (in case where transform property is overridden).
--- a/packages/jest/src/default-config.resolver.ts
+++ b/packages/jest/src/default-config.resolver.ts
@@ -12,6 +12,9 @@ export class DefaultConfigResolver {
   resolveGlobal(workspaceRoot: Path): any {
     const jestPresetFullPath = join(workspaceRoot, jestPresetRootPath);
     return {...defaultConfig,
+      transform: {
+        '^.+\\.(ts|js|html)$': 'ts-jest'
+      },
       snapshotSerializers: [
         getSystemPath(join(jestPresetFullPath, snapshotSerializer)),
         getSystemPath(join(jestPresetFullPath, htmlCommentSerializer))

--
On another side, I wonder if our issue may is related to the preprocessor. Because it was responsive to fix templateUrl and styleUrls properties before process source with ts-node:

it replace templateUrl property by template and wrap value with require() instruction (which resolves html source as string) ;
it replace styleUrls property by styles with an empty array (which is unecessery for unit tests).

Now ts-node stringifyContentPathRegex is used to export html content and ts-node astTransformers is used to declare an AST Transformer which is responsive to fix templateUrl and styleUrls properties.
Conclusion: we need to investigate to ensure that the ast transformer works as expected.

Hi guys. Thanks for your efforts. I almost forgot, but there actually is a version of builder that incorporates the necessary changes (it existed when the preset was alpha).
It is available in this branch with all the necessary changes. Should have brought it up at the very beginning, but completely forgot about it.
I think it should solve you the mystery.

Related issue: #182

I created a pull request for you to highlight the changes that should be made.

@wesleygrimes @meltedspark
Great! Thanks for fixing the issue sirs.
May we can close this PR (#246) and merge PR #269?

I'd rather merge this PR and delete the other for a few reasons:

Keep the work you've done
The other PR is created from a branch that wasn't meant to be merged to master but released as an alpha (it also depends on alpha version of the preset).
On the other hand this PR is supposed to be more mature and handle all the stuff like updating the tests dependencies etc.

I created the other PR for a reference to make things in this PR work.
So you guys can make the necessary changes and we'll merge this PR. Or I'll make the changes when I have time.

I haven't had time, but I hope to look at this, this week and get this PR
updated. Anyone else is free to jump in and update this as well if you have
time.
Thanks,
Wes
On Sun, Mar 17, 2019 at 6:07 AM JeB<EMAIL_ADDRESS>wrote:

I'd rather merge this PR and delete the other for a few reasons:

Keep the work you've done
The other PR is created from a branch that wasn't meant to be merged
to master but released as an alpha (it also depends on alpha version of the
preset).
On the other hand this PR is supposed to be more mature and handle all
the stuff like updating the tests dependencies etc.

I created the other PR for a reference to make things in this PR work.
So you guys can make the necessary changes and we'll merge this PR. Or
I'll make the changes when I have time.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/meltedspark/angular-builders/pull/246#issuecomment-473651223,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATy1IVi4zOEgDCD7R_jHKEqkdKsMbpVks5vXhPRgaJpZM4bCCHo
.

--
Thanks,
Wes

OK best I could tell from the PR #269 the only thing needing changed was updating packages\jest\src\jest-config\default-config.ts to add the globals property. Is that correct? If so, I have pushed a new commit to reflect that.

@meltedspark looks like the build passed this time. Want to have a look and see if we can get this merged?

Looks like we're almost there, the only thing that is missing (according to this comment) is adding
 transform: {
       '^.+\\.(ts|js|html)$': 'ts-jest'
 },

to the config. Since it doesn't involve any path calculation it can be added right to the default config (packages\jest\src\jest-config\default-config.ts).
Also, looks like packages/jest/yarn.lock is not updated (it should be). It shouldn't matter for the final version as yarn.lock is not is not published, but for the local development it is better to be in sync.

Looks like we're almost there, the only thing that is missing (according to this comment) is adding
 transform: {
       '^.+\\.(ts|js|html)$': 'ts-jest'
 },

to the config. Since it doesn't involve any path calculation it can be added right to the default config (packages\jest\src\jest-config\default-config.ts).
Also, looks like packages/jest/yarn.lock is not updated (it should be). It shouldn't matter for the final version as yarn.lock is not is not published, but for the local development it is better to be in sync.

Pushed a commit adding the transform property
Regarding the yarn.lock file, this should have been updated previously when I updated the package.json to jest-preset-angular 7.0.0 ? I normally just use npm so I am not as familiar with updating yarn files. Can you help me with next steps on that?

Thanks,
Wes

Sure, in order to update "yarn.lock" you have to run "yarn add -D
jest-preset-angular" (D for dev).
On Wed, Mar 20, 2019, 17:30 Wes Grimes<EMAIL_ADDRESS>wrote:

Looks like we're almost there, the only thing that is missing (according
to this comment
https://github.com/meltedspark/angular-builders/pull/246#issuecomment-472998081)
is adding
transform: {
'^.+\.(ts|js|html)$': 'ts-jest'
},
to the config. Since it doesn't involve any path calculation it can be
added right to the default config (
packages\jest\src\jest-config\default-config.ts).
Also, looks like packages/jest/yarn.lock is not updated (it should be).
It shouldn't matter for the final version as yarn.lock is not is not
published, but for the local development it is better to be in sync.

Pushed a commit adding the transform property
Regarding the yarn.lock file, this should have been updated
previously when I updated the package.json to jest-preset-angular 7.0.0
? I normally just use npm so I am not as familiar with updating yarn
files. Can you help me with next steps on that?

Thanks,
Wes
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/meltedspark/angular-builders/pull/246#issuecomment-474886065,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJXjb1hsG5pVK6_rFyubNeskZtNuw8Piks5vYlQegaJpZM4bCCHo
.

Sure, in order to update "yarn.lock" you have to run "yarn add -D jest-preset-angular" (D for dev).
…
On Wed, Mar 20, 2019, 17:30 Wes Grimes @.***> wrote: Looks like we're almost there, the only thing that is missing (according to this comment <#246 (comment)>) is adding transform: { '^.+\.(ts|js|html)$': 'ts-jest' }, to the config. Since it doesn't involve any path calculation it can be added right to the default config ( packages\jest\src\jest-config\default-config.ts). Also, looks like packages/jest/yarn.lock is not updated (it should be). It shouldn't matter for the final version as yarn.lock is not is not published, but for the local development it is better to be in sync. - Pushed a commit adding the transform property - Regarding the yarn.lock file, this should have been updated previously when I updated the package.json to jest-preset-angular 7.0.0 ? I normally just use npm so I am not as familiar with updating yarn files. Can you help me with next steps on that? Thanks, Wes — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#246 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AJXjb1hsG5pVK6_rFyubNeskZtNuw8Piks5vYlQegaJpZM4bCCHo .

Ok, all set, it did update jest-preset-angular to 7.0.1. Hopefully that's ok.

@all-contributors please add @wesleygrimes for code


deal with -Xfatal-warnings for Scala 2.12.2 release, and after

once https://github.com/scala/scala/pull/5402 is merged, some projects in the community build that have -Xfatal-warnings will start failing — we've already seen that in the test runs on that PR.
What I have time to do right now (meaning in time for 2.12.2) is flip a big switch and temporarily disable -Xfatal-warnings community-build wide. At least, I think I can fairly-easily do that in dbuild.
We'll eventually want to flip that switch back, but hopefully the project maintainers will fix their projects themselves if we notify them via @-mention once 2.12.2 is released, and so that after a month or two has passed, flipping the switch back will be easy.
cc @lrytz @som-snytt

it looks like #521 will be sufficient here, no big hammer needed

When everything looks like a big nail, one always reaches for a big hammer.

btw I'm working on fixing the warnings in scala-partest

I have a fix for partest, since I was also touching another partest fix.

you snooze you lose https://github.com/scala/scala-partest/pull/83

Gah, conflicts.


I owe you a :beer:

Where can I send it? :) Love the plugin!!

Agreed. I've been wanting something like this for a loooong time.


Fix inconsistent result after apply in SKE cluster node pool taint value

Fixes an inconsistent result after apply in SKE cluster node pool taint value
Error occured when a stackit_ske_cluster.nodepool[x].taints[x].value was left empty in the config, since the API returns "" in this case (instead of not providing the field in the response)
Making the field Computed is enough to fix the issue

Relates to #602


Category "OTHER" is not calculated using the selected agg function for OVERVIEWS

Related #628 #625
This was fixed for the non-overviews dataviews but is not working as intended for overviews dataviews

As @rochoa has commented we may have to reconsider how this is implemented, but for now I think we could review the state of possible dataviews/overviews inconstancies and fix the problems in  #634 and #625 together with any other we detect in the review.
Maybe we should rename this ticket to take care of it all here, what do you think?


Appstudio update test-component-pac-hrnu

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-hrnu-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
35 seconds
build-container

✅ Succeeded
15 seconds
inspect-image

✅ Succeeded
15 seconds
deprecated-base-image-check

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
37 seconds
clamav-scan

✅ Succeeded
8 seconds
sbom-json-check

✅ Succeeded
17 seconds
label-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
7 seconds
show-summary


Improve FT_Transformer for uni-modal tabular data in AutoMM

Issue #, if available:
Description of changes:
Support calling fusion_model for uni-modal tabular data.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@sxjscience

Job PR-1816-9 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1816/9/index.html


Missing quote on connectionString

In the section "Edit the application configuration file"
The code:

<add name="Connect"
      connectionString="Url=https://yourorg.api.crm.dynamics.com;Username=yourname@yourorg.onmicrosoft.com;Password=y0urp455w0rd; />

is missing " at the end, it should be:
    <add name="Connect"
         connectionString="Url=https://yourorg.api.crm.dynamics.com;Username=yourname@yourorg.onmicrosoft.com;Password=y0urp455w0rd;" />

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

ID: 6da4c6b5-4ca0-0138-ea99-47e40feaf908
Version Independent ID: 6bd64a3c-bdf4-a8dd-a6d0-a607a444a30f
Content: Enhanced quick Start(Common Data Service) - Power Apps
Content Source: powerapps-docs/developer/common-data-service/webapi/enhanced-quick-start.md
Service: powerapps
GitHub Login: @JimDaly
Microsoft Alias: jdaly

@phecke Can you fix please?

@ajvg94 @JimDaly Fixed. Will be published by end of day.
Thanks for catching that.


MC >= 1.20.2

MC 1.20.2 has been out for some time now, however I have not had any time to work on development due to my college classes. If anyone is reading this and wants 1.20.2 support, please leave a comment below and I will work on it when I can. Until then, I am freezing development until further notice.

After a hiatus, I am back.


Forward Vector

We need a function to calculate the forward vector. It is daily bread when you want to move some object in the direction its facing. Like this:
https://docs.unity3d.com/ScriptReference/Transform-forward.html
https://docs.unrealengine.com/en-US/BlueprintAPI/Utilities/Transformation/GetForwardVector/index.html
It will be handle to also implement up and right.

[ ] transform.forward()
[ ] transform.up()
[ ] transform.right()

Perhaps I am misunderstanding this but isn't this just forward in local space but translated to world space? Can't this computed trivially with the object transform matrix and some units vectors?

The only complication I could see would be if we had a parenting system. In which case we would have to transverse up the tree to learn the combined world matrix.
Where would we want such a transform.forward() to reside? Part of the Transform component?
Should we implement it now or wait until we have Parent components?
If we add a parent component I would except you would need read access to World so that we could look up the transforms and parents components recursivly.

I was thinking about parenting. I see it using a new Parent component that will contain EntityId of a parent. For Parent entity itself it must present as well. The worst thing that may happen is if we will have to iterate over these entities twice in parenting system.

I was thinking of implementing my own Parent component but I couldn't seem to find a method in ecs that lets me grab the component if I know the Entity. The only way to grab comonents seemed to be with query did I miss something?


[FLINK-30493][table-api] Introduce TableChange to SET/RESET options

What is the purpose of the change
Introduce TableChange to represent ALTER TABLE SET/RESET syntax
Brief change log

Introduce TableChange API
Add Catalog method to alter table with table changes.
Use AlterTableChangeOperation to represents set/reset

Verifying this change
Add change in SqlToOperationConverter to make sure the Operation contains the expected changes.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

@flinkbot run azure

Hi @fsk119, thanks for the contribution; it looks good in general. I have one question about AlterTableOptionsOption. Is it deprecated now? I sawHiveParserDDLSemanticAnalyzer#convertAlterTableProps still refer to it.

Is it deprecated now?

Yes. I think the AlterTableOptionsOperation  is deprecated. Considering it's totally internal, we may remove this directly? WDYT?

I sawHiveParserDDLSemanticAnalyzer#convertAlterTableProps still refer to it.

Thanks for pointing it out, I will add a commit to remove the usage.


FIX: Stop Member->write() being called two times unnecessarily during login

Prior to this patch, Member->afterMemberLoggedIn() did the following things:

Called registerSuccessfulLogin() which called ->write()
Called regenerateTempID() which called ->write()
Directly called ->write() itself

This means that every time a Member is considered 'logged in', the member ends up being written to the database 3 times, when only once is necessary.
This wouldn't normally be a particular problem as it normally only happens explicitly when a member logs in via the login form (or at worst, on some random page via the auto-login cookie). However for a site that is protected by Basic Auth (e.g. with BasicAuthMiddleware), every single page loads re-authenticates the Member and therefore requires 3 additional writes.
This PR doesn't fix the underlying issue of basicauth re-authenticating every page load (which is a bigger patch), but it does remove two unnecessary ->write() calls on the Member object.
I couldn't think of a cleaner way to do this that didn't involve changing method signatures, except for perhaps setting some private $do_not_write flag or similar on the Member instance. As far as I understand it, this isn't a BC-breaking change as the default for these methods is still to write the Member object (unchanged behaviour), but I'm not sure if any change to a method signature is considered BC breaking.
I've raised the PR against 4, but let me know if it should be targeted elsewhere.

@madmatt Thanks for the PR :-)
but I'm not sure if any change to a method signature is considered BC breaking. < adding optional arguments is not considered BC breaking
Couple of questions:

Have you applied this to the project that you're working on and done some regression testing?
Do you have any recommendations for things we should look out for when regression testing this ourselves?

Thanks @ScopeyNZ, I missed that :)
@emteknetnz I have tested it on a real-world project and am running it currently with no issues. I did a search of the entire codebase for our project (incorporating recipe-cms: 4.5, so that includes cms, asset-admin etc as well), and the only calls to this method don't pass in any other arguments or have any legacy issues, so I think this shouldn't be a problem. Nowhere else calls ->regenerateTempID(), and only one other place calls ->registerSuccessfulLogin() (that's MemberAuthenticator->authenticateMember() - I have left this as-is as it should write the member object (it's not written again afterwards).
The main concern I have with this PR is more around method signature bloat (adding another argument to two public methods), I'm not sure if we have specific rules for/against this.

adding optional arguments is not considered BC breaking

It still might be - if someone has extended Member and overridden these methods, this change would trigger warnings for them.
I think this is acceptable anyway though. Extending Member is very rare, and definitely an anti-pattern. Even in the unlikely event someone has done that, it’s even more unlikely still that they’ve overridden the two affected methods.

The main concern I have with this PR is more around method signature bloat (adding another argument to two public methods), I'm not sure if we have specific rules for/against this.

No specific rules, but I agree it’s not ideal.

// Member::afterMemberLoggedIn()
DataObject::whileSkippingWrites(function() {
    $this->registerSuccessfulLogin();
    $this->LockedOutUntil = null;
    $this->regenerateTempID();
});
$this->write();

// DataObject.php
public function write(...)
{
    if (static::$skip_all_writes) {
        return;
    }
    ...
}

public static function whileSkippingWrites($closure)
{
    static::$skip_all_writes = true;
    $closure();
    static::$skip_all_writes = false;
}

Interestingly, Symfony considers this a breaking change for the reason you mentioned @kinglozzer:
https://symfony.com/doc/current/contributing/code/bc.html#changing-interfaces

Also, I personally hate the idea of static state controlling writes. I'd prefer the arguments and potential BC break. The non-breaking way would be to introduce a new method. You would be welcome to extract the logic from the existing methods and use that in the existing methods. That's non-breaking. This has the worse (imo) problem of adding method bloat though.
The things we do for SemVer.

@madmatt
    private $doWrite = true;

    public function afterMemberLoggedIn()
    {
        $this->doWrite = false;
        // Clear the incorrect log-in count
        $this->registerSuccessfulLogin();

        $this->LockedOutUntil = null;

        $this->regenerateTempID();
        $this->doWrite = true;

        $this->write();
}

... (inside registerSuccessfulLogin() and regenerateTempID() )
        if ($this->doWrite) {
            $this->write();
        }
...

would this work?  you could do this as a patch release then

Hey @emteknetnz, I like this much better than the other options (static state or duplicating methods).
Does anyone else have any other thoughts, before I adjust my PR to @emteknetnz's suggestion?

If you go with that suggestion I think it would create a confusing property as you'd have the expectation that doWrite would stop writes for the object entirely not just in two methods.
I feel as though the breaking change is cleaner as it's more explicit as to what you're doing

Yeah good point about the $this->doWrite being potentially confusing, could possibly name it to something more specific such as private $doWriteDuringOnAfterMemberLoggedIn = true;
This is a good bugfix.  I'd much prefer something that's BC and can be done as a patch release so that we're able to roll this out to other users much quicker, and it also means Matt will be able to remove the fork that's currently in use sot hat will make future upgrades much smoother

Yeah @emteknetnz’s solution is much nicer, happy to roll with that 👍

So everyone okay if I update this to set a private $disableWritesDuringLogin so it's a bit clearer, and I'll just document it a whole bunch so it's clear what it's for and where it's used?
I'll try get to that this week.

Is there any need for this change? Don't the internals of SS check if the record has actually changed before hitting the DB with a write?

@dhensby Correct, except that in between each of the 3 calls to write() there is a state change in the Member object:

registerSuccessfulLogin() sets FailedLoginCount and LockedOutUntil then calls ->write()
regenerateTempID() sets TempIDHash and TempIDExpired then calls ->write()
afterMemberLoggedIn() then calls ->write() itself without changing state, but in my case this still caused a write and I'm not entirely sure why (AFAIK it shouldn't but I didn't dig deep into the changedFields to see why it thought it needed to write again.

The current implementation in this PR is unambiguously considered a BC break these days, and considering how long this has been here it seems there isn't much appetite for rushing a less-than-ideal fix through and cleaning it up in the next major.
As such, I've raised https://github.com/silverstripe/silverstripe-framework/issues/10968 to track this, along with another possible solution to the problem. I've added that issue to the CMS 6 milestone.
I'm going to close this PR to avoid it being accidentally merged into the wrong branch in the meantime. It's linked from the issue, so when we're ready to work on it for CMS 6 we can refer to it and revive it if we like this approach.


Fixed #121 Add toolbar and toolbar back button on explorer

@garg-anuj and @danielpassos

I have added toolbar and toolbar back button on explorer. I have used the existing toolbar layout and added that in the InventoryExplorerActivity. Please review it and let me know if some more fixes are required.

@pg301 Run mvn license:format for correcting license headers
mvn clean install to check if license and checkstyle are satisfied

@garg-anuj Yeah! I am doing that now. Will keep you posted.

👍

Landed at https://github.com/hawkular/hawkular-android-client/commit/04506be571310b5923f64eac95674ac489c3eb77

Thank you @danielpassos  :)


Blank Charts on Visualforce Page containing apex:form tag and Salesforce1

I have implemented c3 charts with visualforce page(Salesforce). But facing some issues from new release of Salesforce.
here is the scenarios.
If there will be one apex:form tag in Visualforce page,  the charts are displaying as blank.
Also it doesn't work on the Salesforce1 App
for more details:
https://devinthecloud.wordpress.com/2015/10/23/winter-16-the-curious-incident-of-the-chart-in-the-form-tag/
I would like to appreciated the help, If this can be fixed as earlier; will help my app to release with c3js.

+1 on this, we did try removing the apex:form tag also, but no luck. The charts are rendered in a component, not sure if thats a reason too.

I have honestly no experience with anything Salesforce or Visualforce, though seems like there's been some investigation at here. Seems the issue is that Salesforce includes Sizzle globally, which D3 picks up and makes it choke. It's really more a D3 + Sizzle issue than anything.

If one of y'all could create a test case in a jsFiddle or something, that would help everyone tremendously.

Troubleshooting this a bit further, the issue is with c3_chart_internal_fn.getTextRect. The line creating the dummy element is null when jQuery is included before D3, have no idea why.

Okay, more investigation. It seems if you remove the clip-path on the main .c3-chart object, all the lines suddenly reappear... So, it's something to do with how Sizzle is creating the clip path.

I appreciate your help.
Thanks for your investigation and support towards this.
I will try to find out the solution and update the PR.

here is my work around, it could be a hack,but making this as the solution for the time being.
first of all thanks to @aendrew for showing lights into this issue. also to @impatient ( #1189 ).

after the release of Winter 16, visualforce page is loading with some extra js libraries which conflicting with c3Js and unable to form the  tag with proper width and height.

which is causing blank graphs.
I was trying to dig into the c3js library codes, but unable to find the "rect" formation section.
thought of to update above  with width and height after the DOM loads. it worked.
Add these lines of code on your page:
window.onload = function () {
$(document).find('svg').each(function(){
var svgHeight = $(this).attr("height"); var svgWidth = $(this).attr("width");
$(this).find("rect").each( function() { $(this).attr('width',svgHeight).attr('height','266'); return false;});
});
};


feature: setup homebrew cask

📝 Provide a description of the new feature
Configure homebrew cask for macOS installation
➕ Additional Information
Follow the cask definition used by Gitify - see https://github.com/Homebrew/homebrew-cask/blob/master/Casks/g/gitify.rb

Feedback from Homebrew Maintainers
> Hi. Thanks for the PR. We have notability requirements for inclusion in homebrew-cask (<30 forks, <30 watchers and <75 stars), which unfortunately this software does not meet. Please consider hosting this in your own Homebrew tap instead.

Created at https://github.com/setchy/homebrew-atlassify


Build local link - no directory

In the buildLocalLink method there should be a check if the $dir variable is empty or not. If it is, the asset shouldn't be changed. Example:
if ($package === false)
    return empty($dir) ? $asset : $dir . '/' . $asset;

I build my links using Laravel's Elixir & gulp which are already ok when they come to this point (so the dir options in config are set to empty strings), but with how it is now, this function prepends another slash to the beginning and breaks everything.

I'm afraid not able to reproduce your problem. I quote from the docs:

Note all local assets filenames are considered to be relative to you assets directory (configurable via css_dir and js_dir options).

So if your css_dir and js_dir options are empty it means you have no assets directory and therefore all your assets are relative to your webroot. In that scenario, if you add do Assets::add('foo.css') the link the library will generate will be
<link href="/foo.css" type="text/css" rel="stylesheet" />

which is correct. It's true it prepends a slash but that doesn't break anything since it's pointing to an asset in your webroot and your config options say your assets directory is the webroot.
Can you please elaborate to help me to understand where the problem is?. For instance provide the full absolute path of one of the conflicting assets and your current library configuration options (public_dir, css_dir and js_dir )and I'll try to figure out what is the proper way to load that asset.

Try this:
Assets::add('/foo.css');

Laravel's elixir function already puts a slash at the beginning of my asset's URL any the buildLocalLink adds another.

I'm not familiar with Laravel Elixir so I'm not able to help with that. If you provide the details I asked for I may be able to help

Well, I provided all the details you need. Look at my last example. The problem is the slash being prepended at the front which can't be disabled in any way. I also provided you with the exact line which needs to be fixed and with the exact code which fixes it.
If you want me to be a bit broader, sure. Here is my exact configuration.
So, this is from my gulpfile.js:
var elixir = require('laravel-elixir');
elixir(function (mix) {
    mix.scripts([
        'node_modules/angular/angular.js',
        'node_modules/angular-sanitize/angular-sanitize.js',
        'node_modules/jquery/dist/jquery.js',
        'node_modules/bootstrap/dist/js/bootstrap.js',
        'node_modules/d3/d3.js',
        'node_modules/d3-tip/index.js',
        'resources/assets/js/core/app.js',
        'resources/assets/js/core/common.js',
        'resources/assets/js/core/messages.js',
        'resources/assets/js/core/spinner.js',
        'resources/assets/js/core/urls.js',
        'resources/assets/js/navbar/navbar.js'
    ], 'public/js/base.js', __dirname);

    mix.version([
        'public/js/base.js'
    ]);
});

When I run gulp in the shell, Javascript files get compiled and versioned. The resulting file is stored, for example like this: /public/build/js/base-51dcaaf9.js.
And then, in PHP, when i call elixir('js/base.js'), the output is the whole path to the built file, so this: /build/js/base-51dcaaf9.js. And this is great, but then I need to manually write the script tag in html templates to use it and I don't want to do that. Instead, I want to do this: Assets::addJs(elixir('js/base.js')) and then in the template simply do {!! Assets::js() !!}, but I can't do this because another slash gets prepended to my asset.
I'm also a bit surprised you're not familiar with Elixir since you mention Laravel 5 in your documentation and Elixir is the default asset management system of Laravel. With the current implementation of this plugin I don't see a way of using it together with Elixir, and the change required for them to be compatible is a 1-liner, as I see it.

This is framework agnostic package. The library is working as it is designed to work. You seem to have a problem with the elixir() function. I don't see the reason for adding a workaround for a framework specific function to a perfectly working framework agnostic library.
Since the problem is the format of the string generated by the elixir() function, the solution is easy:
Instead of reworking the library to be compatible with the format of the string returned by the elixir() function (which the library is totally unaware of), what you have to do is convert the format of the string returned by the elixir() function to the format expected by the library.
A simple string search and replace should do the trick.

Ok, no matter, don't worry, I'll implement what I need myself.

Unfortunately I've have to change the same line, so I build my own ServiceProvider to Override/Extend the method.


Adding an display offset

Would be great to have the option to display the view controller at an offset - I'm trying to have it closer to the bottom of the screen.  Thanks!

Not going to support "display offset", but provides STPopupStyleBottomSheet in release 1.3.0


feat(qa): Update midstream index images to use build 1.0.0-529

Description
Update midstream iibs to rhacs-operator-bundle-container-1.0.0-529

/test powervs-qa-e2e-tests

/test ocp-4-13-qa-e2e-tests
/test powervs-qa-e2e-tests

/test powervs-qa-e2e-tests

/test ocp-4-13-qa-e2e-tests

/test powervs-qa-e2e-tests

/test ibmcloudz-qa-e2e-tests

/test ocp-4-13-qa-e2e-tests
/test ocp-4-13-operator-e2e-tests
/test ocp-4-13-ebpf-qa-e2e-tests

/test ocp-4-13-ebpf-qa-e2e-tests

All intended QA tests passed on P/Z.
Note:
Failures observed in AdmissionControllerTest, ComplianceTest and NetworkFlowTest are flaky on P/Z and would be tracked separately.

hi @gavin-stackrox @robbycochran kindly review & approve the PR.

/test ocp-4-13-ebpf-qa-e2e-tests

Thanks Robby for the approval.

ALl required CI checks have passed ✅ on X and intended tests passed on P/Z.
Note:

ocp-4-13-ebpf-qa-e2e-tests check on X seems to have broken and has no dependency with changes made in this PR, hence skipping the failure for now.
Failures observed in AdmissionControllerTest, ComplianceTest and NetworkFlowTest are flaky on P/Z and would be tracked separately.

Merging the PR.


Zoom animation for multiple TileLayer overlays is not synchrone on IE and Edge

I created a map with two different TileLayer overlays:

    var map = L.map("map").setView([51, 9], 13);
    var layer1 = L.tileLayer("",   //<- URL1
        {
            maxZoom: 18
        }).addTo(map);
    var layer2 = L.tileLayer("",  // <- URL2
        {
            maxZoom: 18
        }).addTo(map);

When I zoom the map the zoom animation for the first TileLayer works like expected. The animation for the second TileLayer playes lagged.
It seems that this problem relates only to IE (Version 11) and Microsoft Edge (Version 42). Also tested with Google Chrome (Version 59), here works everything fine...
No special options or any stylesheet modifications.

Closing this issue as we have decided to drop support for Internet Explorer in a future version of Leaflet (see #6136).


Is it possible for gradle to be like maven and not depend on a specific jdk version

Expected Behavior
Is it possible for gradle to be like maven and not depend on a specific jdk version
Current Behavior
developers need to download a new gradle every time when update Jdk
Context

A number of libraries used by Gradle require updates when new JDK versions appear.
So indeed to leverage the latest JDK you often need to upgrade Gradle.
This is not going to change though we want to improve this. One solution is to rely on toolchains to decouple the JDK running Gradle from the one compiling / testing your code.


Update documentation

This Pull Request updates the HTML that documents the API according to the current most recent version.

Thanks @antonio-ramadas. I'll update the docs with next release!


how to make hyperlink at exist string?

Good evening,
I have two document files and I need to make the first document file hyperlink to the other one from the text I extracted from the table cell
wordDoc = Document(r'testfile.docx')

for table in wordDoc.tables:
    for row in table.rows:
        for cell in row.cells:
            if cell.text == "page" or cell.text == "subject":
                pass
            else:
                if cell.text.isdigit():
                   # i need to add hyperlink to this cell text to that file
                   # cell text will be like 3
                    add_hyperlink(cell.text, "test2.docx#3")
                    wordDoc.save('demo.docx')

Not at present, but this is an interesting use-case. A couple of the challenges I can see off the top of my head would be:

identifying the text in the paragraph you wanted to turn into a hyperlink. I suppose this would be with start and stop indices.
isolating the text into its own run.
inserting the hyperlink element at the correct (start) position and moving the text run down into the hyperlink element as a child.

I'm going to make this a feature request, but if I wanted it myself I'd be looking at how to do it with the underlying lxml objects, writing a function something like:
def insert_hyperlink(
    paragraph: Paragraph, address: str, start: int, stop: Optional[int] = None, text: Optional[str] = None
) -> Hyperlink:
    """Insert Hyperlink object at position `start` in `paragraph`.

    When `stop` is provided, the text between start and stop is made the text of the hyperlink. When `text` is
    provided, it becomes the text of the hyperlink. If both `stop` and `text` are provided, `text` is appended
    to the text between start and stop.

    The hyperlink text is placed into a single run formatted with the built-in `Hyperlink` character-style.
    ```
    ...


Updates godocs for trustedCA field of proxy api type

Updates proxy trustedCA field godocs to provide additional explanation.
/assign @bparees @abhinavdahiya

@bparees I addressed your comments in my latest commit.

/lgtm


Tutorial: "anonymous functions" paragraph is rendered badly on the website (as a table).

https://anydsl.github.io/Tutorial.html#functions and scroll a bit. This is apparently because vertical bar is treated as a syntax for table by the renderer used on the website (it's rendered as such by e.g. Github's rendered). Supposedly, as way to fix might be to use "preformatted" style, i.e. wrap vertical bars in backquotes.

Also, if you ask me, the following example is not very clear. It kinda shows that body of a lambda can be a single expression, which kinda leads to a question if it indeed must be, Python-style. It might be better to just show a block as elsewhere in the tutorial, or add explicit text that body can be an expression or a block (which is of course itself an expression).

Similar issue: https://anydsl.github.io/Infix-Expression.html


custom voc label provider

Description
Solving issue causing problem in reading filename for images.
In order to solve this issue, I just created a new class of VocLabelProvider, and modify some code based on the original code in dl4j library.

In InputSplit class, locations of files are stored in URI format which " " is an invalid character, a common practice is replacing all the spaces with "%20". Therefore causing error while retrieving it to string. We could replace it back easily, but after some consideration, I decided to keep it. Reason being, there will still be some unstable condition when someone purposely provide file with name containing "%20". Rather we can enforce not to put space during file naming, as that is the good practice in the programming world. Not Solve

previously image filename is just extracted by removing the last 4 characters. Now it replaced by finding the last '.' in the filename and remove all characters after that.
Original code

@kenghooi-teoh thanks for pointing out this issue...
I realized what I modified was the decompiled one, that's why so much weird stuff...
changes have been made accordingly...
sorry for troubling you...


Implement the Revert of timesOutReservations

-Drops will get value "Reservation-Timeout": seconds between drop & where reservation has to be bought
-on "drop" the timeout is set to be X seconds after blocktime
-externally function (to be called by front/backend) triggers check for TimedOut Reservations and reverts reservation to the state, as if they had never been "dropped"
-Without checking "Optimization" for only certain number of exectutions of functions ( couple of thousands ) wouldnt compile due to 24kb contract size limit.
-Doesnt Verify at least partly due to said reason.

I think that should be fine - I will test it tomorrow.
But haven't we decided to use a list + counter starting from 0 instead of the _drophash hashmap ?
Syntactically the code should work in both cases, but the naming would be irritating


Update tut-integration-ui.md

Fixing wrong code example

Status
Ready/In Progress/In Hold (Reason for hold)
Related Issues
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Screenshots
Paste here any images that will help the reviewer

@julieschwartz18 Doc review completed.


2.0 Handling of non-existent variables in timelines

Running a Condition with a non-existent variable seems to automatically evaluate as "true". This might be intentional, I didn't look because working on something else, but seems weird to me.

I think the current behaviour is the most logical we can make it. It won't crash, but report the problem to the debugger.


Create intep.txt

Add Instituto de Educación Técnica Profesional with domain 'intep.edu.co' https://www.intep.edu.co/Es/

@Woker2003 First stage of verification passed, official domain for Instituto de Educación Técnica Profesional de Roldanillo, Valle - INTEP is intep.edu.co as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@Woker2003 Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


CODE RUB: FailedServerImageGenerationException Class Update v2.10.1

Updated FailedServerImageGenerationException class by removing constructors in which the error message was hard coded in. Updated all relevant service files to include message.

Closed Pull Request. Resolving in PR #553.


iOS: Display dark status bar content when underStatusBar is true

If a route is taggeg with underStatusBar: true this causes iOS to use the light-content style for the status bar.
The "public/" tab in Folders uses a light background while also setting underStatusBar to true which results an unreadable status bar.
This PR adds a showStatusBarDarkContent tag that allows routes to explicitly override the underStatusBar behaviour when on iOS.
Befor:

After:

@beaucollins Oh cool, I think you're our first external mobile PR submitter! ✊
Thanks! Tagging @keybase/react-hackers for review.


Feature Request: Variable timing

I love this module, but my one request is the option to set a custom amount of time for the number to stay on screen.

Came here to make the same request. I don't need the numbers to stay on screen as long as they do, especially since it seems like only two characters can have numbers showing on them at a time.

Good idea, this is now available in the latest version, v1.1.0.


Implementation of importing of classes with composite names perhaps needs better consideration

First of all, I shall mention that this issue is based upon incomplete information collected while working on rakudo/rakudo#3075.
Let's start with a simple case of two modules defining two classes:
lib/A/B/C/D1.pm6
class A::B::C::D1 { ... }

lib/A/B/C/D2.pm6
class A::B::C::D2 { ... }

and a script which requires them in the following way:
for <D1 D2> {
    require ::("A::B::C::$_");
}

Now, if one would introspect ::("A") inside the loop, he would discover that package A is different package for A::B::C::D1 and A::B::C::D2. Makes sense because they're defined separately in different compunits.
But what happens if we introduce the class A?

If it's used out of the loop then packages A from the classes override it for dynamic lookup with ::("A") but it is still available with static referencing via it's name. I.e. ::("A").new fails because it's a package, but A.new works as expected. A's Stash is then untouched.

If classes A::B::C::D1 and A::B::C::D2 are used together together with use A they will be installed into A's stash.

But if they're used in an enclosed lexical scope they're still getting installed into A's stash and remain visibile outside of the block:
use A;
if True {
    use A::B::C::D1;
    use A::B::C::D2;
}
A::B::C::D1.new; # Doesn't fail

Commenting out use A in the above snippet results in an error in the last line due missing A::B::C::D1 symbol.
NB I thought that this behavior was introduced by my commit 3d356629a718349190d9cb74ac350d4d29750cd3, but testing with previous rakudo releases reveals that it was behaving this way at least since 2018.12.

And the worst part of the whole thing is that under certain circumstances deserialization of such classes results in quiet replacement of the topmost package object for second loaded class. Unfortunately, I can't golf it down from what's reported in rakudo/rakudo#3075. But the pieces of information I managed to collect so far lead me to thinking that deserialization restores package A created by A::B::C::D1 with it's Stash for A::B::C::D2. So that when the latter is imported with require the actual A::B::C::D2 symbol cannot be found because the Stash object of A contains only A::B::C::D1.
I don't know if this is legitimate MoarVM behavior or a bug, but in either case it looks like better management of nested packages by the compiler is required.
I also consider this issue a serious one because it would certainly sooner or latter affect any big enough application possibly blocking an attempt to use Raku in production. The obscure nature of this bug with no easy workaround is definitely could serve as a blocker for such attempt.

I'm also sorry for rather messy posing. It's a result of the mess of collected information.

Need to sort it out better.