Fixing typo in ToastAndroid.android.js

Fixing typo in ToastAndroid.android.js
Test Plan
There is no test plan for this typo fix

@facebook-github-bot shipit

@gedeagas Thanks for the contribution and keep them coming. There is a similar PR that is already in the pipeline. I'm going to close this one in favor of https://github.com/facebook/react-native/pull/15802


Accounts and Test Suites in GitHub Action

Adds accounts and test suites to the github action

still need to create the test suite so the CI passes


Sweetalert not working in UC Browser (Android)

In UC Browser blank window is shown instead of sweetalert2 popup.

UC Browser mobile*

Thanks for reporting this issue @cooberr !
I will add the UC Browser support. It has a huge market share in countries like India, China, Indonesia and I personally care about those users.
Currently I can confirm that everything works fine both in iOS UC Browser and Windows UC Browser. These days I will find an Android device and test in it.
Meanwhile, could you please specify the device and Android version you're using?

ASUS Zenfone 2, Android 5, also tried on samsung.
If it will help you - I added https://cdnjs.cloudflare.com/ajax/libs/core-js/2.4.1/core.js in head and popup has appeared, but its width is incorrect (also only in UC Browser on Android)

One more thing - first version of sweetalert doesn`t have this problem.

Allright, the main issue is fixed by adding a polyfill for ES6 Promises. I added the note about that to docs, thanks for the useful feedback!
About the second issue with the modal width - could you please try our demos (https://limonte.github.io/sweetalert2/) with the same device (ASUS Zenfone 2, Android 5) and tell if there's the same issue with all other examples or it's the issue specific to your project.
Thanks!

yes, absolutely the same situation with incorrect width as on screenshot above:

Looks like an issue for me. Since it's different from the original one, I separated it to https://github.com/limonte/sweetalert2/issues/514
Once again, thanks for help!

sweetalert not work some mobile phones (exp: samsung galaxy s3) what is the problem? Most phones do not work on some phones while I am working without problems. Butona does not react when touched. It's a strange problem.

Most phones do not work on some phones while I am working without problems.

Hahah sorry for my bad English bro. In summery, some phones have no problem. But there are problems with some phones. Android phone Galaxy S3 does not do anything when the button is touched on the devices. How to fix this problem?


Add untriage gh workflow

Changes
Please provide a brief description of the changes here.
Merge Requirements
For new features contributions please make sure you have completed the following
essential items:

[ ] CHANGELOG.md updated to document new feature additions
[ ] Appropriate documentation updates in the docs
[ ] Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

@YANG-DB, thanks for the PR. But, I dont see the option to create an issue on this repo. Is this expected?


langchain.llms.Databricks does not save necessary params (e.g. endpoint_name, cluster_driver_port, etc.) to recover from its config

System Info
I used langchain=0.0.246 on Databricks, but this bug is due to the lack of implementation of Databricks._identifying_params(), so system info should not impact.
Who can help?
I see that @nfcampos contributed to most of the Databricks model serving wrapper, so tagging you here.
@hwchase17 @agola11
Information

[X] The official example notebooks/scripts
[X] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[X] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
llm = Databricks(host=databricks_host_name, endpoint_name=model_endpoint_name)

llm_chain = LLMChain(
    llm=llm,
    prompt=PromptTemplate.from_template(prompt_template),
    verbose=True

llm_chain.save("path/to/llm_chain.json")

The serialized file will only have {'_type': 'databricks'} for llm and therefore the below code
llm_chain_loaded = load_chain("path/to/llm_chain.json")

will complain that ValidationError: 1 validation error for Databricks cluster_driver_port   Must set cluster_driver_port to connect to a cluster driver. (type=value_error).
This is because llm_chain.save() look at the llm chain's _identifying_params() which is not defined on langchain.llms.Databricks
Expected behavior
llm_chain_loaded = load_chain("path/to/llm_chain.json") should recover the langchain.llms.Databricks instance correctly.
All fields on langchain.llms.Databricks that are necessary to re-initialize the instance from a config file should be added to Databricks._identifying_params()

@cjcjameson Sorry for the confusion! Dosu can't create PRs (yet). We've updated it so it should no longer say that.
Is this issue still relevant?

yes it is, I'm getting the same error.


My application executes a lot of small Go scripts programmatically. These scripts reference the standard library.
My goal is to precompile the standard library (std) so that it is never compiled again until I update the Go version. That would help me speed up the small scripts execution.
However when I do go install std or go build std, the compilation results are placed into GOCACHE folder. So essentially, the std gets cached rather then precompiled. And with time this cache expires and I have to run go install std again.
I believe it should be possible to precompile the std library in Go as in all other compiled languages that I'm familiar with. However I failed to find a way to do it in the documentation, github issues or SO threads. Please, help me to see what I'm missing here.
What did you see happen?

Std library is cached in GOCACHE folder, and this cache expires with time even if Go version remains the same.

What did you expect to see?
Std library is precompiled and saved in GOPATH/pkg or elsewhere, where it won't be compiled ever again until I update the Go version.

The standard library was intentionally moved to the cache in order to reduce distribution size (see #47257), but note that even before then the object files in the cache were sometimes not used (for example, due to the use of different build flags that affect the compiled code).
Also note that any standard-library packages you actually use should have their access times updated (and should therefore not be remove from the cache when it is trimmed).
At any rate: you can get the old behavior by setting GODEBUG=installgoroot=all in your environment.


MuiSpeedDial

MuiSpeedDial

MuiSpeedDial @manikandanmohan10 please merge the code to the main branch

MuiSpeedDial @manikandanmohan10 please merge the code to the main branch

Done @Antony-M1


[Feature][Framework] Enforce errors.Error interface usage throughout backend code

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
#2134 introduced a new error interface with an extended API. The existing function signatures however use the native golang error interface. Replace them all with errors.Error. This way the code becomes more self-documenting and forces developers to use the new error API.
Use case
Use errors.Error in the API signatures.
Related issues
#2134
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

tip: Using this Regex/Replace will take care of transforming most if not all function signatures (except lambdas):
regex: (^(func|)\s+?((.?)|)\s[A-Z][A-Za-z_0-9]+?(.).?)(error)([\s|,|)].*$)
sub: $1errors.Error$5

PR: #2941


Document scipy and tkinter dependencies

Hi marl0ny,
Thank you for making this simulation. I had enjoyed interacting with it.
On my machine, I was not able to run the software initially: I encountered a scipy 0.16+ is required for linear algebra error and (after installing scipy) I got a ModuleNotFoundError: No module named 'tkinter' error.
This pull request mentions scipy and tkinter in the README and suggests a way for users to install TKinter which works on Ubuntu.

Thank you for your contribution a-robu
The Scipy dependency is definitely an issue with Numba. I confirmed this by setting up a Python virtual environment and installed only Numpy, Matplotlib, and Sympy using pip (Tkinter was already installed) and made sure that Scipy was not present. I was able to use the program without issue. I then installed Numba and attempted to launch the program but instead I got the same error. Also I previously believed that Tkinter was installed by default with Python but this is not the case. I will address these points in a future commit.

Nice 👌


Update testnet repo

+r

LGTM

The build is good and I'm seeing 1 +1s from the following folks:

wilsonianb

As such, I'll attempt to merge and close this pull request.


BUG: MemoryError Not enough memory to perform factorization.

Describe your issue.
I have a  matrix norm_adj representing a simple undirect bipartite graph, the matrix size is (29809,40764), I want to get the smaller eigenvectors of A1, A1 was a 2 x 2 block symmetric matrix composed of R and the size of A1 is (70573,70573), but this code suffers a memory error, how should I do to fix it?
Reproducing Code Example
# the size of norm_adj is (29809,40764)
# the size of A1 is (70573,70573)

import scipy.sparse as sp
from scipy.sparse.linalg import eigsh
u2u = norm_adj @ norm_adj.T
l2l = norm_adj.T @ norm_adj
u2l = norm_adj
A1 = sp.bmat([[u2u, u2l], [u2l.T, l2l]])
A1 = sp.eye(A1.shape[0]) - A1
vals, vecs = eigsh(A1, k=10, sigma=-1, which='LM', tol=1E-3)

Error message
python(45746,0x106622e00) malloc: can't allocate region
:*** mach_vm_map(size=18446744056529682432, flags: 100) failed (error code=3)
python(45746,0x106622e00) malloc: *** set a breakpoint in malloc_error_break to debug
python(45746,0x106622e00) malloc: can't allocate region
:*** mach_vm_map(size=18446744056529682432, flags: 100) failed (error code=3)
python(45746,0x106622e00) malloc: *** set a breakpoint in malloc_error_break to debug
python(45746,0x106622e00) malloc: can't allocate region
:*** mach_vm_map(size=18446744065119617024, flags: 100) failed (error code=3)
python(45746,0x106622e00) malloc: *** set a breakpoint in malloc_error_break to debug
Not enough memory to perform factorization.
Traceback (most recent call last):
  File "test.py", line 132, in <module>
    vals2, vecs2 = eigsh(A1, k=10, sigma=-1, which='LM', tol=1E-3)
  File "/Users/chf/opt/anaconda3/lib/python3.8/site-packages/scipy/sparse/linalg/eigen/arpack/arpack.py", line 1641, in eigsh
    Minv_matvec = get_OPinv_matvec(A, M, sigma,
  File "/Users/chf/opt/anaconda3/lib/python3.8/site-packages/scipy/sparse/linalg/eigen/arpack/arpack.py", line 1074, in get_OPinv_matvec
    return SpLuInv(A).matvec
  File "/Users/chf/opt/anaconda3/lib/python3.8/site-packages/scipy/sparse/linalg/eigen/arpack/arpack.py", line 914, in __init__
    self.M_lu = splu(M)
  File "/Users/chf/opt/anaconda3/lib/python3.8/site-packages/scipy/sparse/linalg/dsolve/linsolve.py", line 337, in splu
    return _superlu.gstrf(N, A.nnz, A.data, A.indices, A.indptr,
MemoryError

SciPy/NumPy/Python version and system information
lapack_mkl_info:
    libraries = ['mkl_rt', 'pthread']
    library_dirs = ['/Users/chf/opt/anaconda3/lib']
    define_macros = [('SCIPY_MKL_H', None), ('HAVE_CBLAS', None)]
    include_dirs = ['/Users/chf/opt/anaconda3/include']
lapack_opt_info:
    libraries = ['mkl_rt', 'pthread']
    library_dirs = ['/Users/chf/opt/anaconda3/lib']
    define_macros = [('SCIPY_MKL_H', None), ('HAVE_CBLAS', None)]
    include_dirs = ['/Users/chf/opt/anaconda3/include']
blas_mkl_info:
    libraries = ['mkl_rt', 'pthread']
    library_dirs = ['/Users/chf/opt/anaconda3/lib']
    define_macros = [('SCIPY_MKL_H', None), ('HAVE_CBLAS', None)]
    include_dirs = ['/Users/chf/opt/anaconda3/include']
blas_opt_info:
    libraries = ['mkl_rt', 'pthread']
    library_dirs = ['/Users/chf/opt/anaconda3/lib']
    define_macros = [('SCIPY_MKL_H', None), ('HAVE_CBLAS', None)]
    include_dirs = ['/Users/chf/opt/anaconda3/include']

Note that this code isn't really reproducing since norm_adj is only described rather than i.e., constructed programmatically.
If I do something like this on top of the example:
rng = np.random.default_rng(123)
norm_adj = rng.random((29809, 40764))

I can see the memory climb up to > 60 % on a machine with 128 GB RAM, so it does indeed get a pretty substantial footprint.

This isn't really a bug, right? Factorizing a large matrix requires a lot of memory.

@chfhf the simplest solution here is to use a computer with more memory. You may save a bit of memory by deleting temporary arrays before calling eigsh, such as u2u, l2l and u2l, but large arrays will always be heavy in memory:
u2u = norm_adj @ norm_adj.T
l2l = norm_adj.T @ norm_adj
u2l = norm_adj
A1 = sp.bmat([[u2u, u2l], [u2l.T, l2l]])
A1 = sp.eye(A1.shape[0]) - A1
del u2u, l2l, u2l
vals, vecs = eigsh(A1, k=10, sigma=-1, which='LM', tol=1E-3)

Just calling del may not be enough to recover the memory, you may also define a specific function just to construct A1 to call the garbage collector before calling eigsh.
I think this can be closed as there is nothing to be done for scipy.


Make filter validate Authorize response code

Make Filter::onSuccess() validate the HTTP response code returned by
the Authorize endpoint prior to parsing the response body.

@yuval-k, please review.


Initial controller implementation

Changes included in this PR:

Initial controller implementation for a simplified JobSet API, which only includes the Jobs list and network configuration.
controller checks status of active jobs owned by JobSet, and deletes up any old failed jobs (later we can add failure policy for restarting all jobs etc.)
controller creates any jobs which do not exist yet or have failed

Testing:

Tested manually with JobSet for distributed PyTorch training job
Unit tests for util functions
I have a simple integration test ready to add in the next PR.

Note: I looked into adding unit tests for the JobSetReconciler methods themselves, but it seems I would need to possibly fake/mock a Manager to use for creating a unit-testable JobSetReconciler, and I noticed in Kueue there are no reconciler specific unit tests (see here), and the reconciler testing is in the integration tests, so I am planning on doing the same. @ahg-g let me know if you have any thoughts on this.

@ahg-g Thanks for the review, and yes I'll submit a PR for some basic integration tests next, then configure a presubmit to run the integration tests.

/label tide/merge-method-squash

/lgtm


Shutters do not work & port error

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
I added Hacs and the Selve library
Additionally, i added the
selve:
port: /dev/ttyUSB0
config.yaml file
--> If this is not added the suhtter functions are greyed out
After that some shutters appear, if iwant to use them, does not work... Logfile says:
Shutter wurde geschlossen ausgelöst durch Dienst cover.close_cover
Shutter was closed via the cover.close_cover
If i want to add the selve port via Integrations via the port setup i get the error attached. The port i use is 100% correct.
I tried even 2 options:
#Selve integration
selve:
port: /dev/ttyUSB0
#Selve 2
selve:
port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DM01F9DD-if00-port0

to happen.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser Chrome
Version

Additional context
Add any other context about the problem here.

Hey,
Thanks! I´ll have a look into it.
The addon should work if you put this in your configuration.yaml though:
selve:   port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DM01F9DD-if00-port0

Should be fixed now, please try it out

Wow! Perfect and fast support from your side! Thanks a lot! Now its working fine again! Thx thx!


Fix chromium's pepper flash

This is a bit of a fragile fix, but I don't know enough nix to fix it more robustly.
This reorders the allowedVars so that flashVersion is replaced before flash to avoid the buggy behavior.
CC: @vcunat

Addresses #12710.

I guess this fixes why the bbc website tells me I need to install flash. :+1:


Updated Usage with Create React App - avoiding #71

Using<EMAIL_ADDRESS>with Create React App is causing "TypeError: expect.addSnapshotSerializer is not a function" error.
This is happening because<EMAIL_ADDRESS>depends on<EMAIL_ADDRESS>while Create React App is currently using<EMAIL_ADDRESS>Added README warning - pending to be modified when Create React App updates their Jest dependency.
See also #71.

Thanks for this!

Please send a PR to CRA in this cases too 😉
Otherwise our docs turn out to be misleading.
https://github.com/facebookincubator/create-react-app/issues/1957


Add About us page

Hey, I could work on this!

please check the readme and get an idea of the website, then add the About Us page.
If u need any assistance, I'm here to help
Go ahead!

Thank you for your contribution @rstfari


Hunters and Minions are still fighting each other.

Fixed for real this time... probably.


Added remote router and remote vpn labels to bridge stats metrics

This PR extends the metrics for Bridge Statistics with 2 additional labels.
Besides the name of the bridge, labels for the remote router name and the remote vpn name are added.
In our case, the label bridge_name is created automatically when extending the event mesh to something generic like #cluster:292ee3fa43f5000a62458e2d00000003
With the additional labels remote_vpn_name and remote_router_name the metrics are more useful and understandable.
Usage example:
We would like to use the following Grafana Plugin to visualize dataflow in our mesh.
https://grafana.com/grafana/plugins/novatec-sdg-panel/
For this to work, we need to have a properly named source and target label in our metrics.

Sounds good. Would you mind to share the dashboard with us?

Would you merge and I provide some examples afterwards once we've got the new exporter version up and running?

release done: https://github.com/solacecommunity/solace-prometheus-exporter/releases/tag/v1.4.8
Please dont forget the dashboards


Remove data.transformer package

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (bc5cebe) to head (b82b272).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #343   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          100        96    -4
  Lines         2421      2358   -63
  Branches       191       189    -2
=========================================
- Hits          2421      2358   -63

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


keep compatibility with lease API

Signed-off-by: liuwei<EMAIL_ADDRESS>

/assign @qiujian16

/lgtm


gnomAD population plots aren't displaying for me

I'm not seeing any errors, but no plots appear for me. For example, on HTT locus page https://strchive.netlify.app/loci/hd_htt/#gnom-ad:

Update, it appears that the X-linked ones are working. So maybe it's something to do with handling that which is suppressing the others?

Fixed in https://github.com/dashnowlab/STRchive/commit/6d11e4542e0234c25fae107f0ee1522e924120b4


Identifying the author of the document

It would be useful to identify the comments of author of the document (or, if it is difficult to do it per document, per website) which is commented, by looking at the email and the username for instance, with a chosen color for the background of the comments for example (and maybe some indication next to the username and some enhancement for the avatar).

.

Closing in favour of discussion in #321.
Especially https://github.com/posativ/isso/pull/321#issuecomment-382148195 is a nice solution.

Re-opening until someone adds the proposed CSS solution to the docs.

I think a badge next to the author's name plus a different name color would be better than a message background. I think it's easier than trying to deal with trying to make the background fit in with the visual style.

As a first step to allow better styling, the author hash should be inserted into the .isso-comment div, not only as the has to the svg.
@BBaoVanC would you like to work on something like this?

As a first step to allow better styling, the author hash should be inserted into the .isso-comment div, not only as the hash to the svg.
@BBaoVanC would you like to work on something like this?

I'll try and see what I can do. I haven't ever done much with JS so for that part of the client I might need help. I'll make a draft PR if I can figure something out.

That's what I mean:
diff --git a/isso/js/app/templates/comment.js b/isso/js/app/templates/comment.js
index d0daf99..53738b2 100644
--- a/isso/js/app/templates/comment.js
+++ b/isso/js/app/templates/comment.js
@@ -9,7 +9,7 @@ var html = function (globals) {
   var author = comment.author ? comment.author : i18n('comment-anonymous');

   return "" +
-"
"
+"
"
 + (conf.gravatar ? "

" : '')
 + (conf.avatar ? "
<svg data-hash='" + comment.hash + "'</svg>
" : '')
 + "
"

You could then use .isso-comments[data-hash="0bb73c4f5196"] as a style selector, or e.g. .isso-comments[data-hash="0bb73c4f5196"] > .isso-author for styling only the author's name.

Tracked in #844


Release 2.0.0

Version 2.0.0
New features

Supports FlowConfig feature to set images / transformation to process / provide processed image
Position to crop image can be received by external event
Provide version of module via 'OnNewStatusModuleVersion'
Function 'getParameters' to provide PersistentData parameters
Check if features of module can be used on device and provide this via 'OnNewStatusModuleIsActive' event / 'getStatusModuleActive' function
Function to 'resetModule' to default setup

Improvements

New UI design available (e.g. selectable via CSK_Module_PersistentData v4.1.0 or higher), see 'OnNewStatusCSKStyle'
check if instance exists if selected
'loadParameters' returns its success
'sendParameters' can control if sent data should be saved directly by CSK_Module_PersistentData
Added UI icon and browser tab information

Following tasks were checked

[x] Module is coded and structured according to the "Developing guideline for modules" described within the CSK documentation
[x] All functions/events/parameters are documented within the manifest documentation
[x] The manifest description of the main CROWN includes main information about the purpose of the module and how to use it in general
[x] API docu based on the manifest was created and stored within the "docu"-folder of the repository
[x] Internal LUA code documentation exists for variables and non served functions
[x] All relevant infos are logged via the SharedLogger 'ModuleLogger'
[x] Module supports persistent data feature based on 'CSK_Module_PersistentData'
[x] Module supports user management based on 'CSK_Module_UserManagement'
[x] No open "ToDos" within the code or at least clearly explained comments why they exist...
[x] "Version" key in app manifest was updated following semantic versioning (and use '0.x.y' for test / experimental modules which are not yet ready to be officially released)
[x] Meaningful IDs used for UI elements
[x] Module was tested on an AppSpace device (at least on SICK AppEngine) with no error message
[x] README.md is up to date (incl. info of device + firmware the module was tested with)
[x] CHANGELOG.md is up to date

Issues should be fixed.
Thx for the review!


Couldn't pass 200 request / second

Description of issue
I tried to increase concurrent user to 100,000 and decrease min wait time to 1ms, and max wait time 2ms.
I couldn't pass 200 request / second, after increasing concurrent user and decreasing wait time.
Expected behavior
I could achive hundred thousand request / second
Actual behavior
I couldn't pass 200 request / second
Environment settings (for bug reports)

OS: Ubuntu 14.04
Python version: 2.7
Locust version: 0.8.1

What happens when you do this? Do you get errors? Have you increased the OS limit on the max number of open files? How much CPU does the locust/python process use?

I could achieve hundred thousand request / second

without knowing specifics of your environment and tests, it's impossible to say if this is feasible.  It depends on your machine specs, network topology, configuration, number of slaves running, and many other factors.  You need to monitor all resources to figure out where your bottleneck is.
btw, I hope you are running in distributed mode with many slave machines. You'll never get even close to 100,000 concurrent users from a single load generator.

I don't really see anything actionable here. Any expectation that a single Locust node can produce hundreds of thousands of requests per second really isn't realistic.


Issue 132 correct git eol character

Fixes current LF files that do not match the given CRLF format desired. Prevents the problem in future for people with git configured to use remote LF (which is a git best practice).

These files already have CRLF eols. Something weird going on?


Use Maturin to ship the Rust CLI in the Python package

This needs testing.

@reyammer Do we want to also do an sdist wheel?


[Feature] Code First

Hello, I would like to be able not to use the proto files if all parts of the project are written in a Dart. Do you have any plans for this?
For example:
protobuf-net
MagicOnion

Interesting suggestion.
You can look into https://github.com/google/built_value.dart/blob/master/built_value/lib/built_value.dart , It allows you to do declare the fields on abstract classes and get the concrete classes generated. However only with support for serializing to json (but perhaps it could be extended to proto-serialization if that is needed).
I think this is outside the scope of the current project, and we don't currently have the capacity to take on something like this. Therefore I will close this issue for now.


No 'allow trusted Microsoft services to bypass this firewall' option

Step 3.b doesn't seem to exist in the UI.

Also looks like there is a little typo in the title:

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

ID: 4bc6f969-fc86-782a-0a8d-b7e4958ad656
Version Independent ID: e4d468da-21c3-f209-cf4c-37dfa60ef929
Content: Congigure IP firewall for Azure Relay namespace - Azure Relay
Content Source: articles/azure-relay/ip-firewall-virtual-networks.md
Service: service-bus-relay
GitHub Login: @spelluru
Microsoft Alias: spelluru

@Tiberriver256, Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

@Tiberriver256 - Thank you. I will remove that step. This feature was enabled for Service Bus and Event Hubs, not for Relay yet.

Fixed the article. #please-close

Thank you!

Looks like the title still has a typo in it @spelluru

Will fix it now. Thanks @Tiberriver256


do not throw during history constructor

This https://github.com/rackt/react-router/blob/master/modules/History.js#L22 makes it hard to use history object in something like stampit.
How about instead add the methods to History that throw if not implemented by those that inherit from History.

History objects are gone.


WIP: fix: logical size limit is broken during PS restart

fixes https://github.com/neondatabase/neon/issues/5963
On top of https://github.com/neondatabase/neon/pull/6000
Will ship this in a release after #6000
The significant behavior change here is that we're making walreceiver wait for exact logical size to be available before establishing a connection.
As a reminder, there is the background task that does the initial logical size calculation.
Before this PR, there was no caller that needed to wait for initial logical size calculation to finish so they could return an Exact value.
Now there is, i.e., get_current_logical_size_exact_wait.
So, we switch from the priority-boosting mechanism introduced in #6000 to using tokio::sync::OnceCell.
Both the background task and get_current_logical_size_exact_wait use it to coalesce on computations.
If background task is first, get_current_logical_size_exact_wait gets an exact result.
If get_current_logical_size_exact_wait is first, background task observes that and exits.

This implements "Design Idea 2" in the associated issue https://github.com/neondatabase/neon/issues/5963
However, we decided to go with "Design Idea 1" https://github.com/neondatabase/neon/issues/5963#issuecomment-2179003680


Disentangle LedDevice/LinearColorSmoothing, Bug Fixes & Test support

1. Tell us something about your changes.
While decoupling ColorSmoorthing from LedDevice, I am coming across various bugs/challenges, as well as added additional capabilities to support testing during development.
a) Fix MultiColorAdjustment coredump (see comment for TestScenario)
b) LedFileDevice: Add time delta between two writes (to validate update/write intervals)
c) LedDevice: Add method to write Led values to stdout
d) Add "Led Test" effect to have well defined switches between RGBWB to validate intervals and smoothing
e) Disentangle LedDevice and LinearColorSmoothing

LedDevices now refresh themselves independently from LinearColorSmoothing
LedDevices are now disabled by default and only after successful initialisation enabled
LedDevices do not update(write), if not ready
LedDevices write "Black", if switched-off (unless switch-off by LED hardware is supported)
LedDevices, clear separation between threads of LedDeviceWrapper and LedDevices using signals and considering QT's thread affinity rules.
LedDevices, new close() slot with BlockingQueuedConnection to ensure proper shutdown of devices before hyperion ends
LedDevices, removal of throwing exceptions which are not caught properly between QT-Threads.
New error() method allowing to set a device in error and not being ready for usage.

To have proper thread alignment sequence per device should be as per original documentation
a. constructor  - without calling init()
b. start()
b.1 open()
b.1.1 init()
b.1.1.1 LedDevice::init()
b.2 setEnable(true), if init() was successful
....
c close()
c.1 LedDevice::close()

LedDevices, LedDevice, LedDeviceFile, LedDeviceNanoleaf and ProviderUDP were updated and aligned. Note: Updates to other devices are pending

Fixed, Effect configuration updates (effect configurations were appended and not updated)

Fixed, Hyperion - Removed visiblePriorityChanged->update connection, as it results in double write()s

Update, changed Framebuffer timer to "precise" rather than using a "coarse" timer per default

Open topics/issues: LinearColorSmoothing as not been fully reviewed and updated yet.
Disentangling of ColorSmoothing and Effects is required. Testing effects does not make use of the correct smoothing configuration, but the default one (0 record).

Not sure why all already merged commits still show up in the list...
Everything after the last merge is new.

In case I come across further issues/bugs, do you prefer to have individual issues capture, one collection issue created or no issues at all?
Not sure what is best practice here? Please advise.

Da fehlt bestimmt ein #include <chrono> ???

Da fehlt bestimmt ein #include <chrono> ???
Interessant, lokal wird ohne Fehler kompiliert.
Nichtsdestotrotz, Danke für den Hinweis!

@Lord-Gray
Fehlt noch was bei deinem PR? Kann ich mergen oder helfen?

Alles klar. Sag bescheid wenn du soweit bist. :+1:

@Paulchen-Panther OK. Nach einem Refactoring Marathon von 66 Files können wir starten.

@All I had to update all LedDevice code files aligning them to QT's thread affinity rules.
May I ask you a favour?
Would you test the updated code against your LedDevices, please?
You may use my repository or the master, when Paulchen-Panther merged the PR.
Could you after testing comment on the test results providing the information per device tested?
Device Type:
Test (OK/NOK):
Smoothing (On/Off):
Rewrite (on/Off):
That may also help me going forward, knowing whom I can approach for testing support going forward...
Thanks for your support!

For now, I  reverted the change "Remove Connect (PriorityMuxer::visiblePriorityChanged -> Hyperion::update) due to double writes"  to keep existing behaviour and not limit merging the PR (see commit)

@Paulchen-Panther Hi, wie sieht es aus, willst Du mal mergen?
 Wenn ich den neuen PR von brindosch sehe, kommt da ja noch ein "dicker Bocken".
Fixes können wir ja dann über kleinere PRs integrieren.

@brindosch Thank you! Fingers crossed that not too many issues are popping up....

Regarding test i mean writing test for all classes where we expect a specific result. We are often caught in regressions due to things you can't see. Often a test "framework" is involved for simple code writing.
This can be for example the API class: "Test all methods to provide an access denied when not authorized".

Regarding test i mean writing test for all classes where we expect a specific result. We are often caught in regressions due to things you can't see. Often a test "framework" is involved for simple code writing.

That is understood and the way how are things done today.I only wanted to confirm that my understanding was right. We are on the same page.


Improve UpgradeDependencyVersion to update dependency version whose value is defined via a property from the parent POM.

What's changed?
Improve UpgradeDependencyVersion to update dependency version whose value is defined via a property from the parent POM.
What's your motivation?

https://github.com/openrewrite/rewrite/issues/4193

Anything in particular you'd like reviewers to focus on?

Anyone you would like to review specifically?
@timtebeek
Have you considered any alternatives or workarounds?

Any additional context

Checklist

[x] I've added unit tests to cover both positive and negative cases
[x] I've read and applied the recipe conventions and best practices
[ ] I've used the IntelliJ IDEA auto-formatter on affected files

Sure. Thanks!

@timtebeek just wanted to check if you have an ETA for a full review of this PR? Thanks!

Apologies @nguyenhoan ! Travel & catching up to what I've missed is taking a little longer than I had hoped; I plan to revisit this Monday. At first glance it's quality work; I just want to make sure there's no regressions given how often this recipe is used, and I'll have to update downstream use in tandem. Appreciate your patience & persistence in seeing this through!

Thanks @timtebeek! Please let me know if you need anything from me. Look forward to the release of this enhancement.

@timtebeek just a gentle ping on when this can be merged. Thanks!

Thank you for helping with this important enhancement and bringing it to the destination!
Could you please let me know when the relevant changes to other modules such as org.openrewrite.java.dependencies.UpgradeDependencyVersion in rewrite-java-dependencies are also merged and the new releases in tandem happen? Thanks!

I've just opened a PR for rewrite-java-dependencies

https://github.com/openrewrite/rewrite-java-dependencies/pull/103

We release snapshot versions every day, and new releases of all openrewrite recipe modules typically every two weeks. We previous release was last week; so then likely by next week there should be a release containing this improvement.

Awesome! Thanks!

Yay! Thank you!


An error occurs when copying and executing the command at the time of setting up CodeQL CLI

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/ja/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system#
What part(s) of the article would you like to see updated?
I typed the command according to the documentation but I got the following error:
$ wget https://github.com/github/codeql-action/releases/latest/download/codeql-bundle-linux64.tar.gz
$ tar -xvzf ../codeql-bundle-linux64.tar.gz
tar (child): ../codeql-bundle-linux64.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

This problem is simple.
This is because the file specified in the argument of the tar command refers to ../ and the directory one level higher.
The location to put the file downloaded with the wget command is the current directory.
The command can be copied and used as is by specifying a file in the current directory as follows:
$ wget https://github.com/github/codeql-action/releases/latest/download/codeql-bundle-linux64.tar.gz
$ tar -xvzf ./codeql-bundle-linux64.tar.gz

Additional information
No response

@soartec-lab
Thanks so much for opening an issue! I'll triage this for the team to review :eyes:

@soartec-lab - many thanks for raising this issue. I've just confirmed your diagnosis on my machine.


Add new command to get device status

API reference: https://github.com/banzalik/homebridge-winix-c545/blob/master/index.js

@hftsai256 This looks great and thank you for the feature! The only thing I can see is that it needs code reformatting on it. If you just run make fmt (alternatively: pip install black && black winix) that should do it.
Once you do that I will merge and cut a release to pip.
I will look at Github Actions and see if I can have that run that check so it's more obvious next time.
Thank you again!

@hftsai256 I've added a linting check. Can you rebase from master and then run make fmt to reformat the code?
I've left the master branch in a failing state so that you won't have to resolve conflicts. Once you merge your formatted PR this should be fixed.
Thanks again for the contribution!

I've done the format with black. This is a really interesting integration infrastructure I haven't seen before, and I feel I should introduce it into my other projects. Thanks man

It's my first time using Github Actions and I think I did not set it up correctly, as I believe it should have shown the CI status on this PR page after you rebased your PR. 🤷 I'll have to look into it.
Thanks again @hftsai256 for your contribution! I've released it as 0.2.1 and you can install it via pip with pip install winix==0.2.1.
https://pypi.org/project/winix/0.2.1/


GDAL No such file or directory when using unzipped SAFE file

Currently, rtc_s1.py fails with a GDAL No such file or directory error if the input Sentinel-1 data is unzipped.
This can be recreated by processing the Los Angeles sample data hosted on zenodo, unzipping the provide SAFE file, then running rtc_s1.py with this configuration file.
This error occurs because calling s1reader's Sentinel1BurstSlc.slc_to_vrt_file() method writes a VRT representing the burst SLC data with a relative path to the parent geotiff that assumes the VRT is in the same directory as the SAFE file. However, in RTC this VRT is written to a temporary subdirectory with this structure:
input_dir
└── S1_SLC.SAFE
scratch_dir
└── temp_*
   └── temp_*
      └── BURST_ID
         └── slc_VV.vrt

Thus, GDAL is not able to locate the parent geotiff using the information in the VRT.
I can think of two ways to remedy this:

Modify Sentinel1BurstSlc.slc_to_vrt_file() so that it uses absolute file paths
Force RTC to write burst VRTs into the same directory as the input SAFE file

Personally, I prefer option 1 because it fixes the problem for other projects as well, and requires fewer code changes.
error.txt

My vote was also for (1) when I opened that issue here https://github.com/isce-framework/s1-reader/issues/96

Yep, I'd prefer option 1 as well. Thanks for pointing me towards the s1-reader issue!

Thank you, @forrestfwilliams , for reporting this issue. I agree with you and @scottstanie , that would be better to fix s1-reader. Thank you, @scottstanie , for creating the issue https://github.com/isce-framework/s1-reader/issues/96 in that repository.


Analyzer mismatch with dart_style

When using dart_style & flutter_navigation_generator it is not possible to resolve.
Resolving dependencies...
Because no versions of flutter_navigation_generator match >1.0.3 <2.0.0 and flutter_navigation_generator 1.0.3 depends on analyzer ^5.0.0, flutter_navigation_generator ^1.0.3 requires analyzer ^5.0.0.
And because dart_style >=2.3.3 depends on analyzer ^6.2.0, flutter_navigation_generator ^1.0.3 is incompatible with dart_style >=2.3.3.
So, because my_app depends on both dart_style ^2.3.4 and flutter_navigation_generator ^1.0.3, version solving failed.

Now it also fails with injectable_generator
Because injectable_generator >=2.5.0 depends on analyzer ^6.4.1 and every version of flutter_navigation_generator depends on analyzer ^5.0.0, injectable_generator >=2.5.0 is incompatible with flutter_navigation_generator.
So, because flutter_template depends on both flutter_navigation_generator ^1.0.4+1 and injectable_generator ^2.6.0, version solving failed.

You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on injectable_generator: flutter pub add dev:injectable_generator:^2.4.1

Feel free to open a PR :sweat_smile:

This should be fixed, please let me know if you still encounter this


Integration tests

Description
Checklist:

[ ] Code follows the style guidelines
[ ] Code commented in relevant places
[ ] Changes to necessary documentation made
[ ] Has test cases for code.

Tests Performed:

[ ] Upload data to Datastore
[ ] Retreive data from Datastore
[ ] Map Visualization
[ ] Network Map Visualization
[ ] List other manual test cases performed

@arunk054 I found a way to run integration tests after the build. Let me know if you think this way is better, I also wrote it as a servlet call before discovering firesafe testing.


Feature/pyleco directors

closes #34

@BenediktBurger could you check this PR is fine for using pyleco? I did some tests but maybe not widespread...


Polls/elections: problem with default value analog

Description: If a user changes the default value of voting type for polls or elections to analog in the settings, votes didn't work anymore. (Also an error message appears in the console.) Even if the value is switched back to other voting types, it's not possible to reactivate the voting function.
Affected setting - voting type of ballots (elections)

Affected setting - voting type of motions

error message during vote creation - motions

error message during ballot creation:

Reproduction:

open a meeting
open settings > motions > default voting type > change to analog
open settings > elections > default voting type > change to analog
open motions > create a motion > change status to a state were voting is possible > create a vote
open elections > create a new election > add candidates > create a new ballot
Try to switch back the default voting type for motions and perform step again -> won't work -> voting is not possible anymore

What should happen:
Changing default voting types for elections and/or motions to analog shouldn't lead to a fatal error of the whole voting system.

Regression from #2963


Fixed Index implementations as a result of rust upgrade

As the index function in the index trait accepts values instead of references now, I've updated the implementation to take this into consideration.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

Dupe of #85, but thanks!

Oh, I don't know how I missed that. Sorry!

No worries!


not able to install the plugin

I'm not able to install the plugin in LimeSurvey 5.6.18.
It seems to read the XML file because it shows me the description, version... but after clicking on the installation button it tells me it's impossible to analyze the config.xml file.

My guess is that you have a wrong file structure. You cannot install thebzip file directly downloaded from GitHub.
Make sure you follow the instructions exactly.
"Theme manager (4.x - 5.x) - Extract the download, compress (zip) the Searchable-Dropdown folder and import via the theme manager."

Thank's for your answer. I'm sorry I didn't understand that all the tools offered in the limestore were not installed via the plugin manager. It's work!


Amplify Console is blank all of a sudden

I have a few projects all running fine on Amplify, but for one of them, about a week ago, the main console view started showing a blank page.
All of the other projects work completely fine.
All of the sub-pages on the problem project also work fine (General, Domain Management, Previews etc) if I navigate to them directly, but they do also break depending on what sequence of pages I go through. There are also console errors showing (displayed below). Sometimes it even crashes to the point that I have to restart the page.

After further investigation, it turns out that the problem was caused by the YAML file uploaded to the "build settings" section, which had a duplicated section. This happened because when doing Cmd+a in the editor, and then "paste", "delete" or really anything else, it doesn't actually delete the selected content, it just ignores it.
This highlights 2 things:

Having an error with the YAML file should actually be highlighted in the UI, not just in the console.
The Amplify Console itself should not just crash, without feedback to the user.

@dragosiordachioaia we're working on fixing this.

I saw this error today as well.  deleted the yaml from the build settings. project has a amplify.yaml in the code.  This resolved the blank console error
🙏🏼

Deleting the file is not the solution, catching the validation error and handling it appropriately is.

agree...   just sharing that this thread was helpful

Hello all, thank you for your patience. We have deployed a fix for this, so it should no longer be an issue. Feel free to re-open this ticket if you continue to face this or related issues. Thank you!


Enhancement: make postgres and mysql SSL option names consistent

What
The names of the SSL configuration options are inconsistent between postgres and mysql.
postgres:

mysql:

Why
This inconsistency can easily lead to confusion (e.g. if copy pasting the postgres config when writing the mysql config).

In general we adhere to the parameter names of the underlying sources.
For Postgres: https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION

For MySQL: https://dev.mysql.com/doc/refman/8.4/en/connection-options.html#option_general_ssl-mode

This is also why the names of the parameters are different (mysql_sslmode vs pg_sslmode)


When textfield is autofocused, I can not paste content

Steps to Reproduce

Create a Textfield

TextField(
  autocorrect: false,
  autofocus: true,
);

try to paste content into the textfield.

flutter doctor -v
Flutter (Channel stable, v1.7.8+hotfix.3, on Mac OS X 10.14.5 18F203, locale en-AU)
• Flutter version 1.7.8+hotfix.3
• Framework revision b712a172f9 (2 days ago), 2019-07-09 13:14:38 -0700
• Engine revision 54ad777fd2
• Dart version 2.4.0

Thanks actually, I was trying to figure out why it couldnt be pasted at all.

I think we should call _handleSelectionChanged when calling FocusScope.of(context).requestFocus(_focusNode).

We're experiencing this issue as well and was about to open another issue.
Any chance it gets prioritized? It's highly annoying to end-users.

Good news I have checked the dev branch , seems it will be fixed there. But
it’s not in current stable channel
On Sat, 3 Aug 2019 at 1:01 am, Joel Hernández<EMAIL_ADDRESS>wrote:

We're experiencing this issue as well and was about to open another issue.
Any chance it gets prioritized? It's highly annoying to end-users.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/36034?email_source=notifications&email_token=AFCP4YYUQMYWBQUTT36J23TQCRD4TA5CNFSM4IB57XN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3N7WBY#issuecomment-517733127,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFCP4Y2P3ZA7FPHRV2KEYDTQCRD4TANCNFSM4IB57XNQ
.

--
Adrian Wang
Developer
Student Services Australia Pty Limited
56 Meagher Street
Chippendale NSW 2008
+612 9698 4999 <+61%202%209698%204999>

Can someone from the team confirm this please?

I think there's more to it than autofocus.
Having turned off autofocus in a TextField, I am able to get the paste menu up, however if I paste something, then delete the pasted text, the paste menu will not appear on another long press.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.


GIT extension not working

After upgrading to 1.53.0 on folders with git repository Source Control tab displays  "The folder currently open doesn't have a git repository".
Expected behavior, Source Control tab shows status of the git repository (updated files, allows to commit and push etc)
Another issue with version 1.53.0. The Issue Reporter does not work. When selecting menu item HELP->Report Issue the Issue Reporting window is not opened.
My operating system is RedHat 7.9.
After downgrading to Code 1.52.1 it works as expected.

I'm not able to reproduce your Issue Reporter problem in Insider's. Can you try Insider's?

@janispinkis Can you press F12 when you open the issue reporter and check if there is anything in the console there?

@RMacfarlane see https://github.com/microsoft/vscode/issues/115784#issuecomment-775273645 in case @janispinkis is suffering from the same underlying issue, or if it's even RedHat7 related at all.

@janispinkis Can you press F12 when you open the issue reporter and check if there is anything in the console there?

F12 isn't working at all. When opening the terminal I'm getting the error mentioned by gjsjohnmurray

Confirmation at https://github.com/microsoft/vscode/issues/115784#issuecomment-775307222 that the Report Issue problem is caused by the RedHat7 incompatibility problem. Maybe the git problem is too.

How can we provide more information to you? On RHEL 7.8 both v1.53.0 and v1.53.1, the git repositories are not recognised as janispinkis describes above. We've downgraded all our people to v1.52.


feat: add otel to main

Overview

Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Failed knuu ci test run - could you please fix it? 🙏

otel_test.go:18: GRAFANA_ENDPOINT env var must be set

I guess fixing this error in this test and we are good to go 🖖

@smuu needs to fix this


Docker task cannot find dockerfile in staging directory,

Environment
VSTS: provisioinsights / spectre, Build: InitialProcessor / Build 20171014.6
Agent: Hosted VS2017
Issue Description
Docker task cannot find dockerfile in staging directory,
Tasks

Copy files: including **\Dockerfile-Publish to $(build.artifactstagingdirectory)
Docker: Action: build image, Docker file: $(build.artifactstagingdirectory)\**\Dockerfile-Publish

Error
No Docker file matching d:\a\1\a**\Dockerfile-Publish was found.
Copy files task logs show that the file is indeed copied and I can also see the Dockerfile-Publish in artifacts. Is the docker task trying to find this pattern inside the source directory?
Logs
Copy files task
    2017-10-14T03:46:06.6232438Z Copying d:\a\1\s\src\Spectre.InitialProcessor.TestConsole\Dockerfile-Publish to d:\a\1\a\src\Spectre.InitialProcessor.TestConsole\Dockerfile-Publish

Docker task
2017-10-14T03:46:06.6392417Z ##[debug]Evaluating condition for step: 'Build an image'
2017-10-14T03:46:06.6392417Z ##[debug]Evaluating: succeeded()
2017-10-14T03:46:06.6392417Z ##[debug]Evaluating succeeded:
2017-10-14T03:46:06.6392417Z ##[debug]=> (Boolean) True
2017-10-14T03:46:06.6392417Z ##[debug]Expanded: True
2017-10-14T03:46:06.6392417Z ##[debug]Result: True
2017-10-14T03:46:06.6392417Z ##[section]Starting: Build an image
2017-10-14T03:46:06.6392417Z ==============================================================================
2017-10-14T03:46:06.6392417Z Task         : Docker
2017-10-14T03:46:06.6392417Z Description  : Build, tag, push, or run Docker images, or run a Docker command. Task can be used with Docker or Azure Container registry.
2017-10-14T03:46:06.6392417Z Version      : 0.3.1
2017-10-14T03:46:06.6392417Z Author       : Microsoft Corporation
2017-10-14T03:46:06.6392417Z Help         : [More Information](https://go.microsoft.com/fwlink/?linkid=848006)
2017-10-14T03:46:06.6392417Z ==============================================================================
2017-10-14T03:46:06.8472320Z ##[debug]agent.workFolder=d:\a
2017-10-14T03:46:06.8502325Z ##[debug]loading inputs and endpoints
2017-10-14T03:46:06.8522325Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2017-10-14T03:46:06.8522325Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2017-10-14T03:46:06.8522325Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2017-10-14T03:46:06.8532323Z ##[debug]loading INPUT_ACTION
2017-10-14T03:46:06.8532323Z ##[debug]loading INPUT_CONTAINERREGISTRYTYPE
2017-10-14T03:46:06.8532323Z ##[debug]loading INPUT_CONTEXT
2017-10-14T03:46:06.8532323Z ##[debug]loading INPUT_CWD
2017-10-14T03:46:06.8532323Z ##[debug]loading INPUT_DEFAULTCONTEXT
2017-10-14T03:46:06.8532323Z ##[debug]loading INPUT_DETACHED
2017-10-14T03:46:06.8532323Z ##[debug]loading INPUT_DOCKERFILE
2017-10-14T03:46:06.8662318Z ##[debug]loading INPUT_IMAGEDIGESTFILE
2017-10-14T03:46:06.8662318Z ##[debug]loading INPUT_IMAGENAME
2017-10-14T03:46:06.8662318Z ##[debug]loading INPUT_IMAGENAMESPATH
2017-10-14T03:46:06.8662318Z ##[debug]loading INPUT_INCLUDELATESTTAG
2017-10-14T03:46:06.8662318Z ##[debug]loading INPUT_INCLUDESOURCETAGS
2017-10-14T03:46:06.8662318Z ##[debug]loading INPUT_QUALIFYIMAGENAME
2017-10-14T03:46:06.8662318Z ##[debug]loading INPUT_RESTARTPOLICY
2017-10-14T03:46:06.8662318Z ##[debug]loaded 17
2017-10-14T03:46:06.9012299Z ##[debug]check path : d:\a\_tasks\Docker_e28912f1-0114-4464-802a-a3a35437fd16\0.3.1\task.json
2017-10-14T03:46:06.9012299Z ##[debug]set resource file to: d:\a\_tasks\Docker_e28912f1-0114-4464-802a-a3a35437fd16\0.3.1\task.json
2017-10-14T03:46:06.9012299Z ##[debug]system.culture=en-US
2017-10-14T03:46:06.9042294Z ##[debug]cwd=d:\a\1\s
2017-10-14T03:46:06.9052308Z ##[debug]containerregistrytype=Container Registry
2017-10-14T03:46:06.9062298Z ##[debug]dockerRegistryEndpoint=null
2017-10-14T03:46:06.9062298Z ##[debug]Absolute path for pathSegments: d:\a\_tool\NuGet\4.3.0\x64/docker = d:\a\_tool\NuGet\4.3.0\x64\docker
2017-10-14T03:46:06.9072411Z ##[debug]Absolute path for pathSegments: C:\LR\mms\Services\Mms\Provisioner\TaskAgent\agents\2.123.0\externals\git\cmd/docker = C:\LR\mms\Services\Mms\Provisioner\TaskAgent\agents\2.123.0\externals\git\cmd\docker
2017-10-14T03:46:06.9072411Z ##[debug]Absolute path for pathSegments: C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin/docker = C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\docker
2017-10-14T03:46:06.9072411Z ##[debug]Absolute path for pathSegments: C:\Program Files\Microsoft MPI\Bin\/docker = C:\Program Files\Microsoft MPI\Bin\docker
2017-10-14T03:46:06.9072411Z ##[debug]Absolute path for pathSegments: C:\Program Files (x86)\Python36-32\Scripts\/docker = C:\Program Files (x86)\Python36-32\Scripts\docker
2017-10-14T03:46:06.9072411Z ##[debug]Absolute path for pathSegments: C:\Program Files (x86)\Python36-32\/docker = C:\Program Files (x86)\Python36-32\docker
2017-10-14T03:46:06.9082294Z ##[debug]Absolute path for pathSegments: C:\Windows\system32/docker = C:\Windows\system32\docker
2017-10-14T03:46:06.9082294Z ##[debug]Absolute path for pathSegments: C:\Windows/docker = C:\Windows\docker
2017-10-14T03:46:06.9082294Z ##[debug]Absolute path for pathSegments: C:\Windows\System32\Wbem/docker = C:\Windows\System32\Wbem\docker
2017-10-14T03:46:06.9082294Z ##[debug]Absolute path for pathSegments: C:\Windows\System32\WindowsPowerShell\v1.0\/docker = C:\Windows\System32\WindowsPowerShell\v1.0\docker
2017-10-14T03:46:06.9082294Z ##[debug]Absolute path for pathSegments: C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\/docker = C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\docker
2017-10-14T03:46:06.9082294Z ##[debug]Absolute path for pathSegments: C:\Program Files\Microsoft SQL Server\130\Tools\Binn\/docker = C:\Program Files\Microsoft SQL Server\130\Tools\Binn\docker
2017-10-14T03:46:06.9082294Z ##[debug]Absolute path for pathSegments: C:\Program Files (x86)\GtkSharp\2.12\bin/docker = C:\Program Files (x86)\GtkSharp\2.12\bin\docker
2017-10-14T03:46:06.9082294Z ##[debug]Absolute path for pathSegments: C:\Program Files\Microsoft\Web Platform Installer\/docker = C:\Program Files\Microsoft\Web Platform Installer\docker
2017-10-14T03:46:06.9092296Z ##[debug]Absolute path for pathSegments: C:\Program Files\nodejs\/docker = C:\Program Files\nodejs\docker
2017-10-14T03:46:06.9092296Z ##[debug]Absolute path for pathSegments: C:\Users\VssAdministrator\AppData\Local\Microsoft\WindowsApps/docker = C:\Users\VssAdministrator\AppData\Local\Microsoft\WindowsApps\docker
2017-10-14T03:46:06.9092296Z ##[debug]Absolute path for pathSegments: C:\NPM\Modules/docker = C:\NPM\Modules\docker
2017-10-14T03:46:06.9092296Z ##[debug]Absolute path for pathSegments: C:\Program Files\Git LFS/docker = C:\Program Files\Git LFS\docker
2017-10-14T03:46:06.9092296Z ##[debug]Absolute path for pathSegments: C:\Program Files\CMake\bin/docker = C:\Program Files\CMake\bin\docker
2017-10-14T03:46:06.9092296Z ##[debug]Absolute path for pathSegments: C:\java\ant\apache-ant-1.9.7\bin/docker = C:\java\ant\apache-ant-1.9.7\bin\docker
2017-10-14T03:46:06.9092296Z ##[debug]Absolute path for pathSegments: C:\java\maven\apache-maven-3.2.2\bin/docker = C:\java\maven\apache-maven-3.2.2\bin\docker
2017-10-14T03:46:06.9102300Z ##[debug]Absolute path for pathSegments: C:\Program Files\Java\jdk1.8.0_112\bin/docker = C:\Program Files\Java\jdk1.8.0_112\bin\docker
2017-10-14T03:46:06.9102300Z ##[debug]Absolute path for pathSegments: C:\Program Files\dotnet\/docker = C:\Program Files\dotnet\docker
2017-10-14T03:46:06.9102300Z ##[debug]Absolute path for pathSegments: C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code/docker = C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code\docker
2017-10-14T03:46:06.9102300Z ##[debug]Absolute path for pathSegments: C:\Program Files\Microsoft SDKs\Service Fabric\Tools\ServiceFabricLocalClusterManager/docker = C:\Program Files\Microsoft SDKs\Service Fabric\Tools\ServiceFabricLocalClusterManager\docker
2017-10-14T03:46:06.9102300Z ##[debug]Absolute path for pathSegments: C:\Users\testusername\AppData\Local\Microsoft\WindowsApps/docker = C:\Users\testusername\AppData\Local\Microsoft\WindowsApps\docker
2017-10-14T03:46:06.9102300Z ##[debug]Absolute path for pathSegments: \Docker/docker = d:\Docker\docker
2017-10-14T03:46:06.9102300Z ##[debug]Absolute path for pathSegments: C:\Users\MMSImgGenVM2017\AppData\Local\Microsoft\WindowsApps/docker = C:\Users\MMSImgGenVM2017\AppData\Local\Microsoft\WindowsApps\docker
2017-10-14T03:46:06.9112304Z ##[debug]Absolute path for pathSegments: C:\Program Files\Python36/docker = C:\Program Files\Python36\docker
2017-10-14T03:46:06.9112304Z ##[debug]Absolute path for pathSegments: C:\Users\MMSImgGenVM2017\AppData\Local\Microsoft\WindowsApps/docker = C:\Users\MMSImgGenVM2017\AppData\Local\Microsoft\WindowsApps\docker
2017-10-14T03:46:06.9112304Z ##[debug]Absolute path for pathSegments: C:\Users\MMSImgGenVM2017\AppData\Local\Microsoft\WindowsApps/docker = C:\Users\MMSImgGenVM2017\AppData\Local\Microsoft\WindowsApps\docker
2017-10-14T03:46:06.9112304Z ##[debug]Absolute path for pathSegments: C:\Program Files\Docker/docker = C:\Program Files\Docker\docker
2017-10-14T03:46:06.9112304Z ##[debug]check path : C:\Program Files\Docker\docker.exe
2017-10-14T03:46:06.9112304Z ##[debug]docker=C:\Program Files\Docker\docker.exe
2017-10-14T03:46:06.9112304Z ##[debug]dockerHostEndpoint=null
2017-10-14T03:46:06.9122301Z ##[debug]action=Build an image
2017-10-14T03:46:06.9152292Z ##[debug]C:\Program Files\Docker\docker.exe arg: build
2017-10-14T03:46:06.9162302Z ##[debug]dockerFile=d:\a\1\a\**\Dockerfile-Publish
2017-10-14T03:46:06.9182294Z ##[debug]Pattern found in docker filepath parameter
2017-10-14T03:46:06.9182294Z ##[debug]System.DefaultWorkingDirectory=d:\a\1\s
2017-10-14T03:46:06.9182294Z ##[debug]findPath: 'd:\a\1\s'
2017-10-14T03:46:06.9182294Z ##[debug]findOptions.followSpecifiedSymbolicLink: 'true'
2017-10-14T03:46:06.9182294Z ##[debug]findOptions.followSymbolicLinks: 'true'
2017-10-14T03:46:06.9202298Z ##[debug]  d:\a\1\s (directory)
2017-10-14T03:46:06.9202298Z ##[debug]  d:\a\1\s\.git (directory)
2017-10-14T03:46:06.9202298Z ##[debug]  d:\a\1\s\.git\config (file)
2017-10-14T03:46:06.9202298Z ##[debug]  d:\a\1\s\.git\description (file)
2017-10-14T03:46:06.9202298Z ##[debug]  d:\a\1\s\.git\FETCH_HEAD (file)
2017-10-14T03:46:06.9202298Z ##[debug]  d:\a\1\s\.git\HEAD (file)
2017-10-14T03:46:06.9202298Z ##[debug]  d:\a\1\s\.git\hooks (directory)
2017-10-14T03:46:06.9292283Z ##[debug]  d:\a\1\s\.gitignore (file)
[truncated]
2017-10-14T03:46:06.9292283Z ##[debug]  d:\a\1\s\nuget.config (file)
2017-10-14T03:46:06.9292283Z ##[debug]  d:\a\1\s\README.md (file)
2017-10-14T03:46:06.9292283Z ##[debug]  d:\a\1\s\src (directory)
2017-10-14T03:46:06.9302295Z ##[debug]  d:\a\1\s\src\docker-compose.ci.build.yml (file)
2017-10-14T03:46:06.9302295Z ##[debug]  d:\a\1\s\src\docker-compose.dcproj (file)
2017-10-14T03:46:06.9302295Z ##[debug]  d:\a\1\s\src\docker-compose.override.yml (file)
2017-10-14T03:46:06.9302295Z ##[debug]  d:\a\1\s\src\docker-compose.yml (file)
2017-10-14T03:46:06.9302295Z ##[debug]  d:\a\1\s\src\InitialProcessor.sln (file)
2017-10-14T03:46:06.9302295Z ##[debug]  d:\a\1\s\src\Spectre.Configuration (directory)
2017-10-14T03:46:06.9312287Z ##[debug]  d:\a\1\s\src\Spectre.Configuration\bin (directory)
2017-10-14T03:46:06.9312287Z ##[debug]  d:\a\1\s\src\Spectre.Configuration\bin\release (directory)
2017-10-14T03:46:06.9312287Z ##[debug]  d:\a\1\s\src\Spectre.Configuration\bin\release\netstandard2.0 (directory)
2017-10-14T03:46:06.9322287Z ##[debug]  d:\a\1\s\src\Spectre.Configuration\bin\release\netstandard2.0\publish (directory)
[truncated]
2017-10-14T03:46:07.0212244Z ##[debug]  d:\a\1\s\src\Spectre.InitialProcessor.TestConsole\Dockerfile (file)
2017-10-14T03:46:07.0212244Z ##[debug]  d:\a\1\s\src\Spectre.InitialProcessor.TestConsole\Dockerfile-Publish (file)
[truncated]
2017-10-14T03:46:07.0222242Z ##[debug]  d:\a\1\s\src\Spectre.InitialProcessor.TestConsole\Program.cs (file)
2017-10-14T03:46:07.0222242Z ##[debug]  d:\a\1\s\src\Spectre.InitialProcessor.TestConsole\Spectre.InitialProcessor.TestConsole.csproj (file)
2017-10-14T03:46:07.0222242Z ##[debug]389 results
2017-10-14T03:46:07.0222242Z ##[debug]patternRoot: 'd:\a\1\s'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.debug: 'undefined'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.nobrace: 'undefined'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.noglobstar: 'undefined'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.dot: 'undefined'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.noext: 'undefined'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.nocase: 'undefined'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.nonull: 'undefined'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.matchBase: 'true'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.nocomment: 'undefined'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.nonegate: 'undefined'
2017-10-14T03:46:07.0222242Z ##[debug]matchOptions.flipNegate: 'undefined'
2017-10-14T03:46:07.0222242Z ##[debug]pattern: 'd:\a\1\a\**\Dockerfile-Publish'
2017-10-14T03:46:07.0222242Z ##[debug]expanding braces
2017-10-14T03:46:07.0222242Z ##[debug]pattern: 'd:/a/1/a/**/Dockerfile-Publish'
2017-10-14T03:46:07.0222242Z ##[debug]applying include pattern against original list
2017-10-14T03:46:07.0222242Z ##[debug]0 matches
2017-10-14T03:46:07.0222242Z ##[debug]0 final results
2017-10-14T03:46:07.0222242Z ##[debug]task result: Failed
2017-10-14T03:46:07.0222242Z ##[error]Unhandled: No Docker file matching  d:\a\1\a\**\Dockerfile-Publish  was found.
2017-10-14T03:46:07.0222242Z ##[debug]Processed: ##vso[task.issue type=error;]Unhandled: No Docker file matching  d:\a\1\a\**\Dockerfile-Publish  was found.
2017-10-14T03:46:07.0222242Z ##[debug]Processed: ##vso[task.complete result=Failed;]Unhandled: No Docker file matching  d:\a\1\a\**\Dockerfile-Publish  was found.
2017-10-14T03:46:07.0312247Z ##[section]Finishing: Build an image

Is the docker task trying to find this pattern inside the source directory?

That's correct. It is trying to find it in the default working directory which is source directory.
2017-10-14T03:46:06.9182294Z ##[debug]System.DefaultWorkingDirectory=d:\a\1\s

I am having a very similar problem. I created a small .NET Core Docker App for Linux and published and tested it. Then I configured CI in the Azure Portal. First just Docker Container CI, which didn't seem to work at all. Then I configured regular CI. Attached is the .zip file with all of the logs from the failed build.
logs_3.ziVSTS_DockerBuildLogs.zip

Mike, Can you please run the build with System.Debug as true (see this link and share the debug logs so that they contain more details?

Mike can u check if the docker file input is **\Dockerfile, For linux i think it should be **/Dockerfile.

We had to delete everything yesterday after a few attempts to fix it. Unfortunately, I'm now running into a different problem. We re-published the app as a new Linux App Service with a new container registry entry and got it all working. (The VS dialog for publishing to Linux has a lot of issues, but that's another story for another day.) This time, I did not go into the Docker Container blade in the App Service, I just went into the Continuous Delivery (Preview) blade and set it up. When I try to create the build definition I get this error, "Failed to configure Continuous Delivery. Error: Setup Continuous Delivery job call failed with error TFS.WebApi.Exception: The Image field is required. Parameter name: provisioningConfiguration.Source.BuildConfiguration.Image." Sounds easy enough to fix, however the image box is read-only. I've attached a photo. I also tried to change the '' to a '/' as mentioned above, but this dialog does not like the forward slash and gives me an error. I can try editing the slash later if I can get the build created again.

@aydey can you look at it

Mike, it might be the case because the "linuxFxVersion" is not set for the web app, which might be an issue with old web app. Azure recently made a change following which the image and tag value gets stored in a different property, namely “linuxFxVersion”.
Can you try using a new web app, or can you try to shuffling the docker container type in Docker Container blade for the existing web-app. If it still doesn't work out can you please open the Resource Explorer blade, follow the link and then update the “linuxFxVersion” property under config->web to the a value in the format “DOCKER|<image_name>:

Deepak,
No luck with the work-arounds so I re-created the app service and tried again. I think that the original issue is fixed. I am still getting this error:
Starting: Build an image

==============================================================================
Task         : Docker
Description  : Build, tag, push, or run Docker images, or run a Docker command. Task can be used with Docker or Azure Container registry.
Version      : 0.3.2
Author       : Microsoft Corporation
Help         : More Information
7c6439c8-6a44-407f-a42c-958cf72e93cd exists true
Unhandled: No Docker file matching /opt/vsts/work/1/s/**\Dockerfile was found.
I’ve attached the full set of logs.
I think that has to do with having a Solution that has 2 service projects where the source code is in the same Git repository. I’ve been told that doesn’t work. For now I’m manually publishing each service from Visual Studio to the same service plan.
I suppose I could create a Git repository for each service and put each service in its own Solution to get around this. Please let me know if multiple projects CI is supported at some point.
Thanks,
Mike Yeager
CEO and Senior Developer
EPS Software & CODE Consulting
My Biohttp://codemag.com/People/bio/Mike.Yeager
Seen our videos? CODE Consultinghttp://codemag.com/videos/play/consulting and CODE Staffinghttp://codemag.com/videos/play/staffing
From: Deepak Sattiraju<EMAIL_ADDRESS>Sent: Tuesday, November 21, 2017 6:55 AM
To: Microsoft/vsts-tasks<EMAIL_ADDRESS>Cc: Mike Yeager<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Microsoft/vsts-tasks] Docker task cannot find dockerfile in staging directory, (#5641)
Mike, it might be the case because the "linuxFxVersion" is not set for the web app, which might be an issue with old web app. Azure recently made a change following which the image and tag value gets stored in a different property, namely “linuxFxVersion”.
Can you try using a new web app, or can you try to shuffling the docker container type in Docker Container blade for the existing web-app. If it still doesn't work out can you please open the Resource Explorer blade, follow the link and then update the “linuxFxVersion” property under config->web to the a value in the format “DOCKER|<image_name>:
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vsts-tasks/issues/5641#issuecomment-346018182, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGvJBV2U4xhYiFj9KJ6MZgDZMFdmUsDyks5s4sg2gaJpZM4P5QCw.

@MikeYeager, we ask for the path to the Dockerfile. So you can have multiple Dockerfiles one per service project; and you can provide the path to the Dockerfile when configuring the Continuous Delivery. I think the  current failure is due to the fact that the pattern was not found in the repo, it could be related to the forward vs backward slash. Can you try with the **/Dockerfile or the exact path to the docker file.

@sachinma, thanks for your reply. I've been told that CD does not support multiple Docker Projects in a solution since the source code is all in the same repository. A check-in would have to trigger deployment of all service projects. As for the forward vs back slash issue, I have tried it both ways with the same result.

You cannot configure multiple services in a single go with CD experience in Azure since that is pivoted around a single App Service. However, you can try by providing the full path to the Dockerfile of the service that you want to deploy on a given app service - that should work. Let me know if you get any error with that.

I am closing this issue. Reopen once you try it again and still run into this issue.

I had the same issue. The docker compose file was not checked in for my solution which caused this error. Adding the file back solved it for me.

In my case, the problem was case sensitivity.  The agent was unix based which is case sensitive.  [Dockerfile].

For those who are struggling with single solution multi project build setup in Azure pipeline for Docker. I had exactly the same issue, and if you look into the command line that the build server gives out you can see that it tries, by default, to make a build in the project directory.
So to fix this, you most likely need to add a buildContext: $(Build.SourcesDirectory) to the actual build file. This forces the Docker context to e.g. Solution level (because the Dockerfile copy commands are based on the solution level directory).
Probably worth adding to somewhere in the comments or smth.

For those who are struggling with single solution multi project build setup in Azure pipeline for Docker. I had exactly the same issue, and if you look into the command line that the build server gives out you can see that it tries, by default, to make a build in the project directory.
So to fix this, you most likely need to add a buildContext: $(Build.SourcesDirectory) to the actual build file. This forces the Docker context to e.g. Solution level (because the Dockerfile copy commands are based on the solution level directory).
Probably worth adding to somewhere in the comments or smth.

I faced the same issue and it got fixed by changing the "Task version" in the build pipeline to "2.*". By default it was 0.

For those who are struggling with single solution multi project build setup in Azure pipeline for Docker. I had exactly the same issue, and if you look into the command line that the build server gives out you can see that it tries, by default, to make a build in the project directory.
So to fix this, you most likely need to add a buildContext: $(Build.SourcesDirectory) to the actual build file. This forces the Docker context to e.g. Solution level (because the Dockerfile copy commands are based on the solution level directory).
Probably worth adding to somewhere in the comments or smth.

It works, thank you so much for help!!!


Scraping data from multiple domains

Do we have the feature to scrape website content from multiple domains which has same design in a spider? If so, How to do that?
Or else any code need to be added to Portia spider source while running spider in order to scrape multiple domains?

Just add the other domain as a start url

If we have n number if domains, do we need to add all n domain as start urls?


Fix tp mem cache

Nanotron seems to consume disproportionately more memory on its activations compared to megatron. This is due to at least the following factors:

The glu activation, which is not fused, allocate two tensors: the activation and the element-wise multiplication. Fusing this operation provides (relatively small) memory gains.
During the differentiable operations (specifically, the DifferentiableAllGather and DifferentiableReduceScatterSum) a new tensor is allocated via torch.empty. This tensor is cached through the entire forward pass until the backward pass. However, this cache is unnecessary as these tensors are not used at all during the backward. Getting rid of these allocations provide significant memory gains. To fix this, this PR introduces a global memory buffer (MemoryBuffer singleton) that recycles the allocated spaces, similar to megatron.

Attached: Memory traces of the default nanotron implementation (which OOMs), the current PR implementation and megatron. The memory traces represent the first rank of a tp8 pp4 dp1 llama70b 5 iteration run (sequence length 8k, microbatch size of 1, accumulation=4, synchronous tp and reduc_scatter mode).

I think these changes are important, as it allows training larger models with significantly less memory requirements.
Let me know if you have any suggestions, and I'd be happy to make adjustments to upstream this feature! :)

Thanks for the comments! I have one question regarding the requires_grad. In principle we shouldn't require gradient on the gathered tensors, right? The custom backward handles the gradient computation for the parameters anyway. At least training runs seamlessly without setting gradient to those tensors.

Yeah I think we can set it to False here (seems like Megatron does the same as well here)

Hi,
Thanks for the PR, it's really nice! I tested your PR by training 100 steps on the Tiny Story dataset and compared the loss with our code. I found an abnormal difference. Could you observe the same thing on your side? This is my config file, you may have to change it a little bit, but the idea is to compare the loss before and after the change with the same hyperparameters. Thanks a lot for the work.
checkpoints:
  checkpoint_interval: 1000
  checkpoints_path: null
  checkpoints_path_is_shared_file_system: false
  resume_checkpoint_path: null
  save_initial_state: false

data_stages:
- data:
    dataset:
      dataset_overwrite_cache: false
      dataset_processing_num_proc_per_process: 1
      hf_dataset_config_name: null
      hf_dataset_or_datasets: roneneldan/TinyStories
      hf_dataset_splits: train
      text_column_name: text
    num_loading_workers: 0
    seed: 42
  name: Stable Training Stage
  start_training_step: 1

general:
  benchmark_csv_path: null
  consumed_train_samples: null
  ignore_sanity_checks: true
  project: ring-attention
  run: Llama3-128k-lr-1e-5-5000
  seed: 42
  step: null

lighteval: null
logging:
  iteration_step_info_interval: 1
  log_level: info
  log_level_replica: info

model:
  ddp_bucket_cap_mb: 25
  dtype: bfloat16
  init_method:
    std: 0.025
  make_vocab_size_divisible_by: 1
  model_config:
    bos_token_id: 1
    eos_token_id: 2
    hidden_act: silu
    hidden_size: 768
    initializer_range: 0.02
    intermediate_size: 3072
    is_llama_config: true
    max_position_embeddings: 512
    num_attention_heads: 16
    num_hidden_layers: 12
    num_key_value_heads: 16
    pad_token_id: null
    pretraining_tp: 1
    rms_norm_eps: 1.0e-05
    rope_theta: 1000000.0
    rope_interleaved: false
    rope_scaling: null
    tie_word_embeddings: true
    use_cache: true
    vocab_size: 50272

optimizer:
  accumulate_grad_in_fp32: true
  clip_grad: 1.0
  learning_rate_scheduler:
    learning_rate: 0.0003
    lr_decay_starting_step: null
    lr_decay_steps: 198
    lr_decay_style: cosine
    lr_warmup_steps: 2
    lr_warmup_style: linear
    min_decay_lr: 1.0e-05
  optimizer_factory:
    adam_beta1: 0.9
    adam_beta2: 0.95
    adam_eps: 1.0e-08
    name: adamW
    torch_adam_is_fused: true
  weight_decay: 0.01
  zero_stage: 0

tokenizer:
  tokenizer_max_length: null
  tokenizer_name_or_path: gpt2
  tokenizer_revision: null

parallelism:
  dp: 1
  expert_parallel_size: 1
  pp: 1
  pp_engine: 1f1b
  tp: 4
  tp_linear_async_communication: false
  tp_mode: REDUCE_SCATTER
profiler: null

tokens:
  batch_accumulation_per_replica: 2
  limit_test_batches: 0
  limit_val_batches: 0
  micro_batch_size: 64
  sequence_length: 512
  train_steps: 100
  val_check_interval: -1

s3_upload: null
experiment_logger: null

That's interesting. Thanks for letting me know, I will investigate further and come back with some results soon :)

I was able to reproduce the error. To fix the issue, I followed megatron's design and fused the all gather and linear operation in a single module. The loss progression now matches with the main branch.
I added two configurations of the optimization. Given that the all-gather and linear are in the same module, we can control whether to recompute or not (and cache it instead) the all-gather during the backward. As expected, recomputing yields larger memory savings at the cost of throughput (but still, both methods are more memory-efficient than the current implementation, and both provide at least comparable tok/sec than the current main). The configuration is parallelism.tp_recompute_allgather. I chose to set it to true as default because it provides a net benefit without trade off, but it is probably advised to set it to false in order to scale better larger models.
I attach wandb logs of four runs on two different configurations that validate the claims. On both, blue is the baseline (main branch) implementation, red is the wrong first version of this PR, green is the no-recompute mode (moderate memory savings and slightly faster than baseline) and purple is the recompute mode (large memory savings and on average as fast as the baseline). The first plots correspond to the tiny llama configuration you shared before. The second plot corresponds to a llama8b run. Except for the wrong plot, all lines are pretty much identical in the lm_loss graph.

Let me know if you have any suggestions.

I chose to set it to true as default because it provides the best trade-off, but it is probably advised to set it to true if memory is not a concern.

Hello, very nice PR ! I left some comments as well before merging
I was able to reproduce the results but found out that the version with recompute_all_gather is faster than the baseline (TP of main branch). So I am okay with setting it to True by default as well.

Updated the PR with the suggestions mentioned! Let me know if I'm missing something.

all points were addressed, LGTM !


Getting System.IO.IOException: The file exists when running tests in an Azure DevOps Services pipeline

Hi
Description
We are getting the following error when running tesks via the vstest task on a self hosted build agent. We have ran the pipeline on other agents and get no issues so it is specific to the machine.
Unhandled exception ocurred: System.IO.IOException: The file exists.

Steps to reproduce
We can only duplicate this on one of our self hosted agents. Just running a pipeline with the vstest task produces the error.
Expected behavior
Vstest should execute correctly.
Actual behavior
The following error is thrown:

DtaExecutionHost version 17.157.29222.1.
Starting TestExecution Model...
##[error]Unhandled exception ocurred: System.IO.IOException: The file exists.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.Path.InternalGetTempFileName(Boolean checkHost)
   at System.IO.Abstractions.PathWrapper.GetTempFileName()
   at MS.VS.TestService.VstestConsoleAdapter.VstestConsoleRunContext.CreateRunContext()
   at MS.VS.TestService.VstestConsoleAdapter.VstestConsoleRunContext.get_Instance()
   at Microsoft.VisualStudio.TestService.AgentExecutionHost.LocalTestRunHost.Execute(Boolean debugLogs)
   at Microsoft.VisualStudio.TestService.AgentExecutionHost.Program.Main(String[] args)

Unhandled Exception: System.IO.IOException: The file exists.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.Path.InternalGetTempFileName(Boolean checkHost)
   at System.IO.Abstractions.PathWrapper.GetTempFileName()
   at MS.VS.TestService.VstestConsoleAdapter.VstestConsoleRunContext.CreateRunContext()
   at MS.VS.TestService.VstestConsoleAdapter.VstestConsoleRunContext.get_Instance()
   at Microsoft.VisualStudio.TestService.AgentExecutionHost.LocalTestRunHost.Execute(Boolean debugLogs)
   at Microsoft.VisualStudio.TestService.AgentExecutionHost.Program.Main(String[] args)

Diagnostic logs
Will provide via email as they contain private information.
Environment
Windows Server 2016 Datacenter 1607, build 14393.3204
Vstest 2.157.3 installed using the vstest installer task

I can send you the debug logs if someone let's me know an email address to send them to. Thanks.

@tomaustin700
We use this dotnet api (https://docs.microsoft.com/en-us/dotnet/api/system.io.path.gettempfilename?view=netframework-4.8) to get a temp file name System.IO.Abstractions.PathWrapper.GetTempFileName() and if your temp folder already has all the possible temp file names this method can generate then it throws.
Ideally the task uses the agent temp folder for generating all these temp files, in case you are using an old vsts-agent then it used to use the os.temp-dir where you can run into this issue.
Can you please try updating your agent to the latest version and this issue should go away? Other wise clearing your system temp folder should also work.

@ShreyasRmsft Hi! I have updated the agent to 2.158.0 but I'm still getting it. What is the path to the temp directory and I will try clearing it? Thanks.

@ShreyasRmsft Clearing down %TEMP% sorted the issue. Seems that GetTempFileName throws IOException where there are more than 65535 files in temp. Thanks for your help.


Container option: Exit devMode when user types q

Currently there is a bug when you use the container option and you type q to exit dev mode. Maven stops the container but it fails to exit the keyboard reader and so the user needs to type ctrl-c to exit.

The problem was in ci.common's DevUtil.java checkServerStopped() called from watchFiles(). It just returned whereas it needed to throw a plugin exception to exit dev mode.

Solved by pull request https://github.com/OpenLiberty/ci.common/pull/143


Pupeteer & Playwright [BUG]

Describe the bug
I can use Cheerio easily with any website. Pupeteer and Playwright are not working.
To Reproduce
Create any workflow with Cheerio Webscraper.
Test with Cheerio.
Then replace cheerio with Playwright

Expected behavior
The same website should work and pass results to the pinecone db and then the chatbot.
ERROR Message - TypeError: (intermediate value) is not iterable (cannot read property undefined).
Screenshots
N/A
Setup
-Docker

latest Flowise release - downloaded yesterday on render

I am also facing the same issue

Same, P & P don't work. But Apify does work.

I have the same issue (1.6.0) with Cheerio:
│ 2024-03-08 10:01:34 [INFO]: ⬆ POST /api/v1/vector/internal-upsert/10ca0d6d-42c2-4e51-93b6-b5d8a0c8847d                                                                         │
│ 2024-03-08 10:01:44 [ERROR]: (intermediate value) is not iterable (cannot read property undefined)                                                                             │
│ TypeError: (intermediate value) is not iterable (cannot read property undefined)                                                                                │
│     at Cheerio_DocumentLoaders.init (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/documentloaders/Cheerio/Cheerio.js:130:22)                 │
│     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)                                                                                │
│     at async buildFlow (/usr/local/lib/node_modules/flowise/dist/utils/index.js:290:36)                                                                                │
│     at async App.upsertVector (/usr/local/lib/node_modules/flowise/dist/index.js:1503:13)                                                                                │
│     at async /usr/local/lib/node_modules/flowise/dist/index.js:1112:13                                                                                │
│ 2024-03-08 10:01:44 [ERROR]: [server]: Error: TypeError: (intermediate value) is not iterable (cannot read property undefined)                                                 │
│ Error: TypeError: (intermediate value) is not iterable (cannot read property undefined)                                                                                │
│     at buildFlow (/usr/local/lib/node_modules/flowise/dist/utils/index.js:333:19)                                                                                │
│     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)                                                                                │
│     at async App.upsertVector (/usr/local/lib/node_modules/flowise/dist/index.js:1503:13)                                                                                │
│     at async /usr/local/lib/node_modules/flowise/dist/index.js:1112:13

I have the same issue. Ive tried lowering the Page numbers and at 300 pages it startet working.


Map Editor: Move Points to concrete value

The original App offers the possibility to edit a point by it's values. This is helpfull if you have maps with same areas and you want to edit both to the same shape. Can this be realized in Cassandra?
For me this would be extremely helpfull because I have a map where I can only use some of the contained areas to avoid having the mower drive throug the pool or similar (see #38). So I need different Maps for different tasks.

I don't know the feature, how does it work exactly?
Should we focus on the problem of why the robot wants to drive through the pool? I looked at the issue again, it doesn't look right. The map looks quite complex. Can you draw the path the robot should have taken?

The idea is: You click a point, press some key and can edit it coordinates in a popup or something like that (I'm not an UI guy). This would be nice.
The other problem:
Yes, it's a complex map. It's a complex garden. This is why I use GPS based navigation. I have a second map without the part on the upper left and the small corridor to this part. On that map, the mower does not want to go through the pool. It takes this way (it's not perfect - I still would like to tell the mower where he should go - the idea with the extra marks for transfer between or to tasks - bit it's much better):

Could it be, that small passage is blocked by obstacle an fw doing some crazy stuff?

In this case, yes. Could be. But not in the other case.

But normally the obstacle should be erased after the next mowpoint.

Sure, but if the next mow point is never reached obstacles won't be erased

But not in the other case.

In other case, there was also an obstacle in front of your mower

BTW: Sometimes the old obstacles do not disappear on a new job. They stay on the map.

No. Not in https://github.com/EinEinfach/CaSSAndRA/issues/38. There is no obstacle whatsoever. See screenshot. The robot was not near the passage before the wrong route appeared.

That looks realy as an issue of cassandra, but since that I did some changes on path planner you have to check if the issue still present

BTW: In Cassandra sometimes the old obstacles do not disappear on a new job. They stay on the map. That was the case on image no 1 on this issue.

It's not a bug it's feature, you can remove obstacles by clicking cancel button

Ok. I did not know that (deleting obstacles).. But picture 1 is not really an issue. It should only explain the "normal" route.
I will try on the specific map (pathplanner).
But back to topic. Nevertheless: It's not important, but editing the mowpoints by hand would be nice.


Leverage only the CVE db from the walker in responses to CRDA for now.

bombastic s3 failure; not mine?

bombastic s3 failure; not mine?

passes for me locally. i can't tell from the logs why it failed.

original log was...DNS related.  :shrug:


zrot_copies ignores cp.z

include<BOSL2/std.scad>
$fn = 32;

zrot_copies(n = 10, cp = [0,0,120], r = 25) color("blue") sphere(2);

I think this is the correct answer.  cp is specifying the location of the axis to rotate around and that axis doesn't depend on cp.z

This is also exactly what I would expect. What do you think should happen?

OK.  But in that case  I'm not clear as to why the cp is specified as a [x,y,z] rather than just [x,y].    Consistency with rot_copies, xrot_copies, and yrot_copies maybe.  But in the example, it is in fact rotating around [0,0,0], not [0,0,120].  Should the docs clarify that it's not rotating around a point, but about an axis located at [cp.x,cp.y]?

You don't have to give cp.z, that is, giving just x,y is fine.   A zrot() operation is rotating around a line, not a point.  There's no meaningful sense in which it is "in fact rotating around [0,0,0]".  It's rotating around the line parallel to the Z axis that passes through [0,0,0].  You can the same line if you give a different cp.z value.   Or, to turn this around, what would you expect zrot() to do "around the point [0,0,120]"?

for what I was trying to do it would negate the need to prefix the rotate_sweep() with an up(120).    But this late in the game, changing it would just cause backward compatibility problems.   Although I would change the docs so it says it's rotating around a z-oriented axis at x,y, instead of saying explicitly (in this case) that it's rotating around a point 120 units above it.  If it's ok with you and Revar I can make those changes.

There is nowhere in the docs where it says you have to give a 3-vector as cp.  If you give cp=[3,4] that works fine.  The only thing that suggests that cp should be 3d is the listed default of [0,0,0].
Sure, go fix the docs.  Presumably you need to change all three rotation distributors to clarify how the axis is determined from cp, and you can note the optionality of cp.z for specifying the axis to zrot_copies.  Not optional for the other ones, though.

I've added it to my to-do list right after the Bezier and texturing with images tutorials.


Xo update

Issues
Fixes #
Reviewer Suggestions
Where should the reviewer start?
Additional Comments
Anything else?

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


Added the Swiftwater Series

Three series (two are finite, one is ongoing) on various aspects of the Swift Programming Language.

Hi Chris
I presume these are all tags on your blog? I actually can't find the blog the home page of your site, is there an index page somewhere?
I think rather than add three separate feeds, it might be appropriate just to add one that contains everything. Would that be appropriate in your opinion? The only thing I wanted to check was that these categories were not mixed in with a whole load of non-iOS content, but from the look of the other content on the site, I don't think that's going to be a problem.
Thanks!
Dave

Hi Dave,
I hope that this finds you in good health, and good spirits.
It isn’t a blog site. It’s a corporate site, but my blogging section is “Miscellany.”
https://littlegreenviper.com/miscellany/
This includes general software development topics, as well as topics related to Swift/Apple development. I have a few series, and also a number of individual posts; several of which are reflected on Medium (https://medium.com/chrismarshallny).
I just submitted three series that I thought might be of interest.
The only ongoing one is Swiftwater. The other two are “finite” series. The Bluetooth one seemed to be fairly popular.
I use WordPress, so there are feeds. I don’t really have it set up in the default WordPress structure.
Yours Most Sincerely,
Chris Marshall

On Jul 27, 2020, at 4:14 AM, Dave Verwer<EMAIL_ADDRESS>wrote:

Hi Chris
I presume these are all tags on your blog? I actually can't find the blog the home page of your site, is there an index page somewhere?
I think rather than add three separate feeds, it might be appropriate just to add one that contains everything. Would that be appropriate in your opinion? The only thing I wanted to check was that these categories were not mixed in with a whole load of non-iOS content, but from the look of the other content on the site, I don't think that's going to be a problem.
Thanks!
Dave
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hey Chris
I understand, thanks so much for the detailed explanation. I appreciate it.
I think your site would fit well with the site, but in the "Company Blogs" section and just with one entry with the "main" RSS feed that captures everything in the Miscellany section, is that possible?
Thanks
Dave

I’ll see if that is possible. It probably should be, but it will need to wait until I get home.
Chris Marshall
Geek
Email<EMAIL_ADDRESS>Web Site: http://cmarshall.com
Sent from my iPhone

On Jul 27, 2020, at 5:06 PM, Dave Verwer<EMAIL_ADDRESS>wrote:

Hey Chris
I understand, thanks so much for the detailed explanation. I appreciate it.
I think your site would fit well with the site, but in the "Company Blogs" section and just with one entry with the "main" RSS feed that captures everything in the Miscellany section, is that possible?
Thanks
Dave
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Dave, I don't think that will work.
It's fine. Not that big a deal. The only thing that would qualify as a "blog," is the Swiftwater series. That's an ongoing series that I update when the mood hits me.
Otherwise, I have customized the site so much, that "Miscellany" isn't a semantically-addressable place.
Chris Marshall
ChrisMarshallNY https://www.google.com/search?q=ChrisMarshallNY
<EMAIL_ADDRESS><EMAIL_ADDRESS>chrismarshallny.com https://chrismarshallny.com/

On Jul 27, 2020, at 5:06 PM, Dave Verwer<EMAIL_ADDRESS>wrote:
Hey Chris
I understand, thanks so much for the detailed explanation. I appreciate it.
I think your site would fit well with the site, but in the "Company Blogs" section and just with one entry with the "main" RSS feed that captures everything in the Miscellany section, is that possible?
Thanks
Dave
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/daveverwer/iOSDevDirectory/pull/419#issuecomment-664638425, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMHKATM7UOEK2SCSG3E7CIDR5XT45ANCNFSM4PIG64TQ.

Hey Chris. Thanks for that. Let's do this:

Add your company blog with the RSS feed for the Swiftwater series in the company blogs section.
Add your Medium to the personal blogs section. (I meant to say this along with my last reply, but forgot!)

Thanks Chris! Sorry it took so long to get this sorted out, thanks for your patience.
Dave

No prob. Thanks for YOUR patience.

On Jul 28, 2020, at 5:45 PM, Dave Verwer<EMAIL_ADDRESS>wrote:

Thanks Chris! Sorry it took so long to get this sorted out, thanks for your patience.
Dave
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Updating VSO build script to create setver.cmd

@jasonsandlin,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot