Same URL different state not pushed (only replaced)

Hi!
I have popup-like components (i.e. tabs, off-canvas). I don't want them to show in the URL or as hashes, as I consider them to be transient state with regards to linkable "friendly" URLs. So I tried to use history PUSH with the same URL, but with a state where the popup is open or not. The problem is that since the URL is the same, I always get a REPLACE and never a PUSH.
This seems to be a feature of PR https://github.com/rackt/history/pull/43 I also noticed that you have already started fixing the consequences of it, such as issue https://github.com/rackt/history/issues/166
What do you think about my case? Why should you not be able to push only state changes? Could you comment this? I also don't quite understand the comment in code "treat PUSH to current path like REPLACE to be consistent with browsers".
Thanks!

Okay, to clarify, you're doing something like history.pushState(state, path), where you change state but not the path, and you're seeing that your PUSH gets changed to a REPLACE?
If that's the problem, that sounds like it could be reasonable for us to fix. @mjackson @taurose thoughts?

Yes, correct. I created a sample PR https://github.com/rackt/history/pull/179 that fixes my problem by comparing states also.

I'm not sure you always want it to behave like that though. How about adding something like shouldReplace(prevLocation, nextLocation): bool to opts instead?

@taurose To my mind, PUSH-ing with state is like POSTing a form. It seems like it should result in a new history entry.

For clarity, I use history.push() when I want to PUSH, and history.replace() when I want to REPLACE. Why does transitionTo(), which handles both cases internally, change a PUSH to same URL as REPLACE, in the first place?

@Macroz It's because browsers don't create multiple history entries when clicking a link multiple times on a static website either. On top of that, we can't push the same URL twice for hash history unless they're decorated with a unique query key.
I agree it's a bit confusing though now that the public API uses the word push instead of the more general router.transitionTo.
@taion I'd say generally it's about passing any data to the next page that you don't want to be contained within the path/URL. Another example could be referral information.
The way you describe POST requests sounds like you'd need to do nextLocation.state != null instead of deepEquals(prev.state, next.state).

@taurose Thanks for the clarification!
I feel like the browser behavior is sane for static sites, but now we're talking about a programmatic API to history. I don't see why the programmer can't decide here, which part of the state is in the bookmarkable URL and which part is in the state object. It's the age of the SPA, right? The programmer defines how that action is implemented with regard to the browser history.
Sounds like if the state is different, the query key should not be the same either?

Sounds like if the state is different, the query key should not be the same either?

Yes, when using state there should always be a query key. But when not using state/query key (which looks like it may be the default soon), pushing the current URL will be a no-op. So the back button as well as links to the current page would behave differently depending on whether you use hash or browser history, which is something we should try to avoid imo.

I don't see why the programmer can't decide here, which part of the state is in the bookmarkable URL and which part is in the state object.

Yeah, I want you to be able to decide what's best for yourself, which is why I proposed a more flexible shouldReplace option.

I feel like the browser behavior is sane for static sites, but now we're talking about a programmatic API to history. [...] It's the age of the SPA, right?

I agree, but I think generally we should also consider the end users which are accustomed to the way static websites work and provide that behavior as a reasonable default.
I guess there's an argument to be made that that should be the responsibility of the router and not the history abstraction though. So I'd also be okay with reverting the PR and baking this into the router somehow. But then we'd have to find a solution for #163 that doesn't run into https://github.com/rackt/history/blob/master/modules/createHashHistory.js#L114 . I just don't see much benefit in the approach of #179

That we have it in transitionTo is neither here nor there, BTW, because transitionTo isn't (fully?) a public API.
@taurose If you care about the referrer, doesn't that imply that you want something like a PUSH rather than a REPLACE? It's tricky - I think we will need something like shouldReplace, but I think a better default would be to not change the PUSH to the REPLACE when state is in play.

I was referring to the 0.x router.transitionTo(..).

If you care about the referrer, doesn't that imply that you want something like a PUSH rather than a REPLACE

Not necessarily I think. I guess I would tend towards pushing if the page looks vastly different like in the pinterest example. If the difference is minor (eg. video content is being autoplayed since the user navigated from a link in another video that was playing) or even unnoticable (eg. when using referral data for analytics) I'd prefer to use REPLACE.
Just to be clear, you'd prefer createPath(prev) === createPath(next) && next.state != null over #179?

Yeah, I want you to be able to decide what's best for yourself, which is why I proposed a more flexible shouldReplace option.

Don't we have a push and replace in the public API to differ what the user wants to do?

@hannesj Are you suggesting that we move this upstream into <Link> in React Router? That might be a sensible way to go.

@taion, that sounds a sensible approach to me. history, is(?) just a thin wrapper around the different history implementations and <Link> would be the component making sure that the navigation acts similar to traditional <a/> tags

@taurose What do you think?

I agree that the router appears to be a better place for it. I'm not sure about putting it into <Link> because then users can't easily get the behavior without it or switch between custom <button> and <Link> for navigation.

Tricky there - I don't think we want to make router.push not just be history.push. Maybe just abstract out the link click handler into a utility function?

Yeah, I don't like changing the router.push behavior either. Do you mean extracting just the logic for deciding push or replace? How would that look like?
Another idea would be to have something like a router.transitionTo alongside router.push and router.replace to make it clear that it's not necessarily a push (or replace) and that the router will take care of that decision, while still allowing people to force a push (or replace). This could also at some point be useful for using replace while another async transition is in process (alternative to using listenBefore).

Pretty much just pull https://github.com/rackt/react-router/blob/v1.0.2/modules/Link.js#L42 into a function.  For example, I do this right now in React-Router-Bootstrap: https://github.com/react-bootstrap/react-router-bootstrap/blob/v0.19.3/src/LinkContainer.js#L23.

Well, I guess that could help rebuilding <Link> behavior, but I was more looking for a programmatic equivalent of the transition behavior, not tied to React or DOM events.

Well, maybe something like you had above... { force: true } on the location descriptor or something.

Bump, any update on this?

No. If you want to move this forward, I'd submit a PR.

I think #179 is on the right track. Let's follow up there.


Remove the rdma_subnetwork_name_prefix output from rdma-vpc module

About the Change
The subnetwork names generated are known after terraform apply.
That means, the gke-cluster module for its kubectl-apply operations needs to depend on the static prefix to avoid running into the issues like.
Error: Invalid count argument

  on modules/embedded/modules/management/kubectl-apply/kubectl/main.tf line 50, in data "kubectl_path_documents" "yamls":
  50:   count   = local.directory != null ? 1 : 0

Alternatively, we could rely on local.template_subnetworks[idx].subnet_name and obviate the output subnetwork_name_prefix altogether. That avoids making assumptions about the names of the subnetworks generated by the rdma-vpc module.
Submission Checklist
NOTE: Community submissions can take up to 2 weeks to be reviewed.
Please take the following actions before submitting this pull request.

Fork your PR branch from the Toolkit "develop" branch (not main)
Test all changes with pre-commit in a local branch #
Confirm that "make tests" passes all tests
Add or modify unit tests to cover code changes
Ensure that unit test coverage remains above 80%
Update all applicable documentation
Follow Cluster Toolkit Contribution guidelines #

I assume you're already aware of this, but there are 2 IT failures

I assume you're already aware of this, but there are 2 IT failures

I am not sure trying to run the integration tests against this branch is a good idea. Two reasons:

It is not up-to-date with the develop
Uses google-private provider.


Fixed issue of process.binding() method in node and NPM.

I had fixed issue stdio process.binding() method for new and lated versions.
Console ask to user for enter authorization code.

ok after many years of reviewing your code I'm committing it


Update Tutorial.rst

Updating some parts that give errors in:
https://cgat-core.readthedocs.io/en/latest/defining_workflow/Tutorial.html#tutorial-start
For the yml file to be copied across it needs to be in a configuration directory for example.

Looked good to me, thanks for updates


Update sprint-process.md

Added changes to the Sprint Process based on the new updated event calendar and the addition of prioritization

we've got two approvals I'll go ahead and merge thanks again @Rosi-D


⚠ Bofrost.hr has degraded performance

In c6aa8c7, Bofrost.hr (https://www.bofrost.hr) experienced degraded performance:

HTTP code: 200
Response time: 4545 ms

Resolved: Bofrost.hr performance has improved in 9c0ae37.


http(metrics): disallow auto HTTP/2 enablement

disallow HTTP/2 for the metrics server, as it's not required.

/retest


SMR batch payload size limit in MB

Introduce a configuration parameter limiting the size of the transaction payload (in megabytes) in a single batch.
This might be necessary to guard against exploding state.

This needs to be coordinated with #343 and #344 as the state could explode when fetching multiple batches.


[FEATURE] kill operation

We have stop, but it has a default timeout. We could add a customizable timeout, but it's sometimes useful to instant-kill a process to see how the system behaves, or if you know it is wedged.
Additionally, it may be useful to send arbitrary unix signals to processes.
See docker-compose's support here:
$ docker-compose kill --help
Force stop service containers.

Options:
    -s SIGNAL         SIGNAL to send to the container.
                      Default signal is SIGKILL.

I'm going to implement this quickly because I'm messing with some example that uses SIGHUP and it would be convenient to have this.

implemented by #239


Updates GitHub workflow for documentation build

Change looks harmless, but I don't understand it 🤔

The DOCS_DEPLOY_KEY is the legacy key and must be replaced:
# check values
remote_repo=""
if [ -n "${DEPLOY_TOKEN}" ]; then
    remote_repo_setup remote_repo "${DEPLOY_TOKEN}"
else
    if [ -n "${DOCS_DEPLOY_KEY}" ]; then
        remote_repo_setup_legacy remote_repo "${DOCS_DEPLOY_KEY}"
    else
        print_error "Neither DEPLOY_TOKEN nor DOCS_DEPLOY_KEY found; please provide one or the other in your workflow env"
        kill -s KILL $TOP_PID
    fi
fi

https://github.com/laminas/documentation-theme/blob/c9c95a899460735dc06ccff05ec47d1c4f95e8ba/github-actions/docs/entrypoint.sh#L64-L75

@froschdesign thanks! As a note for future changes, try putting this sort of reasoning in commits, when not too cumbersome 😁


The  argument of /particle should be an integer instead of a float

Reported by AOOAcat right here.

:tada: This issue has been resolved in version 3.0.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fixed long text contentful

Good work here! Just make sure everyone understands the fix and how it works incase you are asked about it in your demo! :)


Support additional transports

From<EMAIL_ADDRESS>on December 14, 2012 18:54:33
This library is pretty cool. I only wish it was usable in unit tests that take advantage of vm transports. For example, CXF allows rest services to be exposed over a local transport.
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=211

From<EMAIL_ADDRESS>on December 17, 2012 03:30:32
What do you mean by other transports? Do you mean for example VM pipes etc?

From<EMAIL_ADDRESS>on December 17, 2012 06:46:32
I mean providing a means to handle different transport protocols vs the message contents. I specifically referenced CXF which has a pluggable transport system ( http://cxf.apache.org/docs/custom-transport.html ). One of which is a local VM transport that aids testing without having to spin up an HTTP server. Many/most ESBs also provide various protocols for moving messages around.
The crux of this issue, IMHO, is that rest-assured relies on Apache's HTTP components. Correct me if I'm wrong, I didn't do a deep dive on the code. Therefore, it is tied to HTTP. Abstracting this bit might expand the use cases that rest-assured could be applied to. The rest-assured DSL is terrifically readable. It would be great to be able to handle multiple protocols using it.
It is certainly true that HTTP over TCP/IP is almost always the protocol for rest messages. ESBs, CXF, as well as other frameworks provide message agnostic, pluggable, protocols for rest messages to travel over. While I do not assume that it is the responsibility of the rest-assured project to implement a CXF-local transport specific implementation, it would be phenomenal to abstract the transport details so that others (myself included) could provide means to connect to VM, JMS, etc. endpoints using REST messages.

From<EMAIL_ADDRESS>on December 17, 2012 07:09:21
While this is a good idea it'll require a massive rewrite and I can't see myself finding the time needed to do so in a foreseeable future. If you want to help out with this please feel free to do so and I'll assist you in anyway I can. REST Assured was designed for HTTP only (which IS misleading I know).

From<EMAIL_ADDRESS>on January 22, 2014 02:00:48
Status: WontFix

Hi,
Is there a workarround? I also like to use the local scheme to test my endpoints with RestAssured.

What do you mean by local scheme?

I want to use the scheme local instead of http. (local:///service/endpoint)
I've got it working up until when com.jayway.restassured.internal.RequestSpecificationImpl determine the request is not localhost (hasAuthorityEqualToLocalhost(uri)) and adds the port number, which messes up de uri.
If this could be changed or somehow be configurable, i think it would work.

Is this supported by Apache HTTP Client?

I'll try it and let you know

Thanks.


PEP 518 / Poetry / pyproject.toml

From black docs:
What on Earth is a pyproject.toml file?

PEP 518 defines pyproject.toml as a configuration file to store build system requirements for Python projects. With the help of tools like Poetry or Flit it can fully replace the need for setup.py and setup.cfg files.

PEP 518: https://www.python.org/dev/peps/pep-0518/
Poetry: https://poetry.eustace.io/
Consider setting up something like this? Especially since we have black running?

Currently I don't think we need or want this.

We have exactly one dependency. There's not much of a chance for conflicts or solving that issue.
Poetry complicates .travis.yml slightly
Poetry takes a lot longer to install dependencies than just pip
Breaks the "clone the repo and python setup.py install" install workflow instructed in the README.
Don't think black should in any way be involved in this discussion, it just happens to use the same file for configuration.

Overall I think we don't have a problem that poetry would solve in this project, and setup.py is the most compatible way to set up a library today.

Yeah, while it seems like poetry may help out for projects with complex dependencies, ours are simple so we best go with the standard. In truth I had never heard of it till reading through black docs --- I just figured since we at this repo are black fanboys we might like to consider this ;) Happy to close

Haha, true we are huge black fanboys, and personally am also a poetry fanboy. But despite it being a great tool, don't think it's the correct tool for this project.


SyntaxError: invalid syntax when running midea-discover

Hi @mac-zhou
I get the following error when I try and run midea-discover:
Traceback (most recent call last):
  File "/usr/local/bin/midea-discover", line 7, in <module>
    from msmart.cli import discover
  File "/usr/local/lib/python3.5/dist-packages/msmart/cli.py", line 3, in <module>
    import click
  File "/usr/local/lib/python3.5/dist-packages/click/__init__.py", line 7, in <module>
    from .core import Argument as Argument
  File "/usr/local/lib/python3.5/dist-packages/click/core.py", line 95
    f"{hint}. Command {base_command.name!r} is set to chain and"
                                                               ^
SyntaxError: invalid syntax

This is running as root on Ubuntu 16.04.7 LTS with Python 3.5.2, installed using pip3 install msmart.
Please can you advise?

upgrade pip3 install click==7.1.2 and try again

Hi @mac-zhou - this fixed the issue, many thanks ♥


no module named "socketIO_client_nexus"

I'm getting the following error upon installation and startup:
File "/Users/colinarmstrong/src/memoryvue2/node_modules/spacy-nlp/src/client.py", line 13, in <module
    from socketIO_client_nexus import SocketIO, WebsocketTransport
ModuleNotFoundError: No module named 'socketIO_client_nexus'

Changing socketIO_client_nexus to socketIO_client fixes this.

Actually, changing to socketIO_client caused other issues. The actual fix is related to the install instructions: rather than python3 -m pip install -U socketIO-client you need to python3 -m pip install -U socketIO-client-nexus

I created a pull request to fix this (FYI @kengz) : https://github.com/kengz/spacy-nlp/pull/30

Merged the PR mentioned above


Enabling HTTP 2 for upstream server, the response time of concurrent requests is forming a waterfall model adding up the time of other concurrent request

We have Envoy acting as a reverse proxy for upstream services. One of the upstream services is NGINX which serves the static resources for the UI. We have enabled HTTP2 on Envoy without SSL.
For Envoy static resources are configured as below
connect_timeout: 1s
type: static
lb_policy: round_robin
http2_protocol_options: {}
load_assignment:
cluster_name: myservice
endpoints:
- lb_endpoints:
- endpoint:
address:
socket_address:
address: <IP_ADDRESS>
port_value: 3221
Observation

Concurrent requests are hitting the NGINX at the same time and NGINX is taking almost 0 ms to response back (based on NGINX logs)
In Evnoy access logs

First requests take a few milliseconds (61 in the attached image) showing 0 for upstream service
Second request onward takes much longer showing approx same time as earlier request for upstream service response time.  (for 2nd request upstream service time is 61 ms )
Due to this the overall response time of second requests onwards starts building up and shows like waterfall times.

Changing the msx_concurrent_streams to 1 reduces the upstream service time to near 0. So is it that envoy is handling the http2 response sequentially? Isn't this a bug ?
http2_protocol_options:
max_concurrent_streams: 1

Envoy definitely handles HTTP/2 requests in parallel - not sure what the cause of the latency here is but I suggest some time with envoy logs and wireshark.

Envoy logs clearly show that upstream response processing is done sequentially.  If the concurrent streams per connection is set as 1 then the requests are processed in parallel. Upstream server response time is 0 ms as it's on the same VM and serving static files. So some bug with Envoy ?


Unable to use any augmentation layer within tf.data with XLA enabled, in MultiWorkerMirroredStrategy

Click to expand!
Issue Type
Bug
Source
binary
Tensorflow Version
v2.11.0-rc2-17-gd5b57ca93e5 2.11.0
Custom Code
Yes
OS Platform and Distribution
Linux Ubuntu 20.04
Mobile device
No response
Python version
3.8
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
CUDA 11.8, cuDNN 8.7
GPU model and memory
RTX 3090, 24GB
Current Behaviour?
Data Augmentation is generally offloaded to CPU to enable parallelism using tf.data.Dataset.map(...) operation.
This works as expected, with XLA enabled, on single-node training. But using MultiWorkerMirroredStrategy(), with XLA enabled, GraphExecutionError occurs.
With XLA disabled, tf.data based augmentation works fine.
Standalone code to reproduce the issue
# NCCL AllReduce is being used.
strategy = tf.distribute.MultiWorkerMirroredStrategy(...)  # Fails with `jit_compile=True` below
strategy = tf.distribute.OneDeviceStrategy('/gpu:0')  # Works with `jit_compile=True`
(raw_train_ds, raw_test_ds), ds_info = tfds.load(...)

"""Build model in distributed scope"""
with strategy.scope():
  augmentation = tf.keras.Sequential([
    layers.RandomFlip(),
    layers.RandomZoom(0.1),
    layers.RandomTranslation(0.2, 0.2),
  ])

  backbone = tf.keras.applications.ResNet50V2(
    weights=None,
    include_top=False,
    input_shape=(*IMG_SIZE, 3),
    pooling='max'
  )
  backbone.trainable = True
  model = tf.keras.Sequential([
    layers.Input((*IMG_SIZE, 3)),
    backbone,
    layers.Dense(ds_info.features['label'].num_classes,
  ])
  optimizer = tf.optimizers.SGD(
    learning_rate=LR * strategy.num_replicas_in_sync,
    momentum=0.9,
    weight_decay=1e-4)

  model.compile(
      loss=tf.losses.SparseCategoricalCrossentropy(from_logits=True),
      optimizer=optimizer,
      metrics=['accuracy'],
      jit_compile=True)

  if WORKER_RANK == 0: model.summary()
train_ds = (raw_train_ds.shard(WORLD_SIZE, WORKER_RANK)
                          .shuffle(8192)
                          .map(decode_example(IMG_SIZE), tf.data.AUTOTUNE)
                          .map(lambda x, y: (augmentation(x, training=True), y), tf.data.AUTOTUNE)
                          .batch(global_batch_size)
                          .prefetch(tf.data.AUTOTUNE))
test_ds = (raw_test_ds.shard(WORLD_SIZE, WORKER_RANK)
                        .map(decode_example(IMG_SIZE), tf.data.AUTOTUNE)
                        .batch(global_batch_size)
                        .prefetch(tf.data.AUTOTUNE))
model.fit(train_ds,
            epochs=100,
            validation_data=test_ds)

Relevant log output
Error log (you may see duplication of lines, since this is the output of 2 nodes running the same code via MPI):

2022-12-20 21:55:47.039610: I tensorflow/compiler/jit/xla_compilation_cache.cc:477] Compiled cluster using XLA!  This line is logged at most once for the lifetime of the process.
2022-12-20 21:55:54.181560: I tensorflow/compiler/jit/xla_compilation_cache.cc:477] Compiled cluster using XLA!  This line is logged at most once for the lifetime of the process.
Traceback (most recent call last):
  File "main.py", line 167, in <module>
    main()
  File "main.py", line 160, in main
    model.fit(train_ds,
  File "/home/mpiuser/.local/lib/python3.8/site-packages/keras/utils/traceback_utils.py", line 70, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/home/mpiuser/.local/lib/python3.8/site-packages/tensorflow/python/eager/execute.py", line 52, in quick_execute
    tensors = pywrap_tfe.TFE_Py_Execute(ctx._handle, device_name, op_name,
tensorflow.python.framework.errors_impl.InternalError: Graph execution error:

Detected at node 'StatefulPartitionedCall' defined at (most recent call last):
    File "/usr/lib/python3.8/threading.py", line 890, in _bootstrap
      self._bootstrap_inner()
    File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
      self.run()
Node: 'StatefulPartitionedCall'
Detected at node 'StatefulPartitionedCall' defined at (most recent call last):
    File "/usr/lib/python3.8/threading.py", line 890, in _bootstrap
      self._bootstrap_inner()
    File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
      self.run()
Node: 'StatefulPartitionedCall'
2 root error(s) found.
  (0) INTERNAL:  tensorflow/compiler/xla/service/gpu/nccl_utils.cc:266: NCCL operation ncclCommInitRank(comm.get(), nranks, id, rank) failed: remote process exited or there was a network error
         [[{{node StatefulPartitionedCall}}]]
         [[Reshape_6/_62]]
  (1) INTERNAL:  tensorflow/compiler/xla/service/gpu/nccl_utils.cc:266: NCCL operation ncclCommInitRank(comm.get(), nranks, id, rank) failed: remote process exited or there was a network error
         [[{{node StatefulPartitionedCall}}]]
0 successful operations.
0 derived errors ignored. [Op:__inference_train_function_35379]
Traceback (most recent call last):
  File "main.py", line 167, in <module>
    main()
  File "main.py", line 160, in main
    model.fit(train_ds,
  File "/home/mpiuser/.local/lib/python3.8/site-packages/keras/utils/traceback_utils.py", line 70, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/home/mpiuser/.local/lib/python3.8/site-packages/tensorflow/python/eager/execute.py", line 52, in quick_execute
    tensors = pywrap_tfe.TFE_Py_Execute(ctx._handle, device_name, op_name,
tensorflow.python.framework.errors_impl.InternalError: Graph execution error:

Detected at node 'StatefulPartitionedCall' defined at (most recent call last):
    File "/usr/lib/python3.8/threading.py", line 890, in _bootstrap
      self._bootstrap_inner()
    File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
      self.run()
Node: 'StatefulPartitionedCall'
Detected at node 'StatefulPartitionedCall' defined at (most recent call last):
    File "/usr/lib/python3.8/threading.py", line 890, in _bootstrap
      self._bootstrap_inner()
    File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
      self.run()
Node: 'StatefulPartitionedCall'
2 root error(s) found.
  (0) INTERNAL:  tensorflow/compiler/xla/service/gpu/nccl_utils.cc:266: NCCL operation ncclCommInitRank(comm.get(), nranks, id, rank) failed: remote process exited or there was a network error
         [[{{node StatefulPartitionedCall}}]]
         [[Reshape_6/_62]]
  (1) INTERNAL:  tensorflow/compiler/xla/service/gpu/nccl_utils.cc:266: NCCL operation ncclCommInitRank(comm.get(), nranks, id, rank) failed: remote process exited or there was a network error
         [[{{node StatefulPartitionedCall}}]]
0 successful operations.
0 derived errors ignored. [Op:__inference_train_function_34897]

@SuryanarayanaY,
There is already a PR #10845 raised for the similar issue mentioned that it is the bug of tf.distribute and xla. Could you please take a look at this issue. Thank you!

Hi @MasterSkepticista ,
have you referred the attached demo for Multi worker training ? Can you refer it and confirm whether it is useful for your case?
To replicate and check the issue we need more details like cluster _resolver you used in tf.distribute.MultiWorkerMirroredStrategy(), the dataset you have used in tfds.load(), TF_CONFIG details you used and variables like IMG_SIZE, WORLD_SIZE, WORKER_RANK etc.
Please provide all those details to replicate and check the issue.
Thankyou!

It seems jit_compile is incompatible with AllReduce across workers, as is the case in MultiWorkerMirroredStrategy, mentioned here. I went with the suggestion to compile specific steps while leaving the remainder to XLA autoclustering.
Closing this issue for now.


popup.html can be removed

Remove the html page and let the extension work as soon as the extension is loaded.
Need to look into the possibility of DOM not being rendered when the extension loads, so this might throw errors.

Have setup the html page to be only an info page. The extension works as soon as it is turned ON for the browser.


Include Awesome AWS in the list

https://github.com/donnemartin/awesome-aws

Please read the instructions for creating a new list, contributing guidelines and the awesome manifest.
Especially this part:

Wait at least a couple of weeks after creating a list before submitting to give it a chance to mature.

Looks very comprehensive and high quality, so happy to include it at that point. Just submit a PR then.
// @donnemartin

@sindresorhus thanks for the feedback, I was going to wait until 2 week mark before submitting the PR :)

I know the delay might seem annoying, but it has successfully filtered out a lot of hit'n'run lists.

No problem Sindre.
And thanks for the mention @swaroopch.


test: Run with React 18

Adjusted the tests to work with React 18. Some tests are still failing but it's unclear from an outside perspective whether this is a testing issue or implementation issue. Failing tests are skipped and annotated with FIXME(react18).
renderHook from @testing-library/react replacing @testing-library/react-hooks is not final.
Most of the adjustments are batching adjustments:
Before:
act(() => {
   keydown(); // updates are batched
   runTimers(); // this will not contain timers from upates of keydown
})

Fixed:
keydown(); // already wrapped in act by testing-library
act(() => {
   runTimers();
})

You've got plenty of "cannot update a component while rendering another" (e.g. "Cannot update a component (PopoverTrigger) while rendering a different component (ForwardRef(Dialog))"). This is likely an implementation issue.
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
yarn test
🧢 Your Project:

Hey! thanks for taking a look at this. We've done some work around React 18 in this previous PR https://github.com/adobe/react-spectrum/pull/2142
We closed it to wait for more progress from React towards a stable release. I'm not sure of our timeline for when we were going to pick that back up again. I'll check with the team.

gah, so sorry about all the extra commits, I was not expecting that.
I promise I'll clean it up Monday at the latest.


Creating multiple engines crashes on Windows

I did some refactoring to make the Windows runner template not be so specific to a single engine+window; in theory it should be possible to make any number of windows in a process, each with their own engine. In practice, doing so very quickly crashes. From just a bit of initial investigation:

The Flutter view window class registration always uses the same name, and it's done in each instance. We should either use a unique name (e.g., include the pointer value), or use a class name registrar as I did in the runner.
Even with that fixed, there was quickly a crash deep in ANGLE code. I assume it's probably a configuration error at the embedding level, assuming code will only run once, rather than an ANGLE bug, but it'll need investigation.

/cc @clarkezone FYI. (Not a priority at the moment, but something we'll need to fix if it still happens post surface restructuring.)

@clarkezone Is AngleSurfaceManager multi-instance safe? I'm not sufficiently familiar with the GL code, but there's some code that seems suspicious (e.g., all instances using the default display, and each of them destroying the display in their destructors--that wouldn't explain this crash since it happens before closing any window, but maybe the whole pipeline is incorrectly sharing things?).

I'm going to take this off the alpha list; it's obviously something we need to fix, but since it seems very likely to be related to the creation of the surface, which is internal to the engine, I think it's very unlikely that fixing this will require any API changes.

I didn't specifically test that scenario so likely not.

/cc @gw280

https://github.com/stuartmorgan/engine/commit/e48ce683a53a56d5cb5ada9373a9b547ac550000 should fix the first issue; I haven't turned it into a PR yet since I was hoping to get it working end-to-end first. It could be landed separately though.

I suspect having multiple render threads interacting with ANGLE may be the issue here; I'll try a custom task runner setup with a shared render thread and see if that prevents the crash.

I suspect having multiple render threads interacting with ANGLE may be the issue here; I'll try a custom task runner setup with a shared render thread and see if that prevents the crash.

I've verified that using a shared render thread fixes this. As expected it then crashes when closing one of the windows, due to some incorrect destructor code (like that referenced above, but also I believe some in the ANGLE manager as well), but that should be straightforward to fix.

I've verified that using a shared render thread fixes this. As expected it then crashes when closing one of the windows, due to some incorrect destructor code (like that referenced above, but also I believe some in the ANGLE manager as well), but that should be straightforward to fix.

@knopp How feasible is fully separating the ANGLE state? That may be simpler than a custom renderer task runner, depending.

@knopp How feasible is fully separating the ANGLE state? That may be simpler than a custom renderer task runner, depending.

Shared render thread doesn't completely fix this, because make_resource_current is invoked from I/O thread and if frame render is in progress it will crash it. Possible solution is to ensure that angle creates separate egl display for each instance, so there is no shared state.

Shared render thread doesn't completely fix this, because make_resource_current is invoked from I/O thread and if frame render is in progress it will crash it. Possible solution is to ensure that angle creates separate egl display for each instance, so there is no shared state.

I'll push PR in few minutes.

I'll push PR in few minutes.

Awesome! I'll set you as the assignee then, since you're actively working on it. I'm happy to have someone with actual expertise here take over 🙂

Awesome! I'll set you as the assignee then, since you're actively working on it. I'm happy to have someone with actual expertise here take over 🙂

(Presumably that will also fix the issue mentioned above where the surface manager is currently tearing down global state in its destructor.)

(Presumably that will also fix the issue mentioned above where the surface manager is currently tearing down global state in its destructor.)

Not sure if I'd call it expertise :), but I do have multi window prototype up and running an so far no issues during clean-up if there is no shared state.

So, I did get stuck here a bit. The reason why multiple engine crash, is that when calling eglGetPlatformDisplayEXT, Angle reuses existing display if any exists, which results in shared non thread safe state.
To the best of my knowledge, the only way to prevent Angle reusing display is right now to use EGL_PLATFORM_ANGLE_ANGLE when creating display with custom created d3d11 device. The major issue here, other than duplicating code already present in Angle is that as far as I can tell there is no way to create display from a D3D9 device.
So if we go with the custom device approach, multiple engines will crash as soon as flutter falls back to d9d device. If fixing this in Angle (i.e. adding flag to explicitly request not to reuse existing display) something that can be considered?
Another approach would be to move all rasterization to single thread, but that doesn't solve egl_resource_context (AngleSurfaceManager::MakeResourceCurrent) which is invoked from I/O thread.
@stuartmorgan, @clarkezone, any ideas?

Actually, I can't reproduce the crash anymore after this landed in Angle. So I'm guessing multiple contexts in different threads were actually supposed to work and it was a bug in the end.

I don't think the window class registration is a big issue, duplicate registrations just (silently) fail and class won't get unregistered while any windows of such class exist. The Angle crash got fixed. Perhaps this can be closed?

and class won't get unregistered while any windows of such class exist.

Oops, I missed that in the doc, and assumed it would lead to issues. There are a few things that should still potentially be salvaged from that PR (using a fixed class name instead of basing it on the window title, using the DLL rather than the exe as the module)—@cbraken to decide if you want to follow up on those—but if the crash no longer happens we should in fact close it.


Add support for chat.update

There's already support for updating messages, but updateMessage() only allows updating the text of the message. There doesn't seem to be any way to update the attachments of that message, for example.
This would be the proper way to handle message updates instead: https://api.slack.com/methods/chat.update

I added a PR implementing these changes: #267


Vendor TSC as a local package

This will make it much easier to maintain TSC.

@swift-ci smoke test


Feature/propagate node

While creating a parse tree, it would be nice to propagate the current node to the user's control methods, (e.g. start, success, failure).
This way the user has additional control over handling the nodes of the tree.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (dffdff0) 99.69% compared to head (f30f625) 99.69%.

:exclamation: Current head f30f625 differs from pull request most recent head fd8f999. Consider uploading reports for the commit fd8f999 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #343   +/-   ##
=======================================
  Coverage   99.69%   99.69%
=======================================
  Files         259      259
  Lines        5202     5205    +3
=======================================
+ Hits         5186     5189    +3
  Misses         16       16

Impacted Files
Coverage Δ

include/tao/pegtl/contrib/parse_tree.hpp
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Allow users to specify path to LSP

After scratching my head a little I finally managed to figure out why this plugin isn't working with my lapce setup.
I make use of ASDF to manage different versions of various languages. This means the path to the binary is in a non standard location. Although that location is added to my path (see below) if I start lapce via launchpad the plugin fails to work

However, if I start lapce from the CLI everything works as expected:

I've managed to work around this limitation for JavaScript as the lapce plugin allows you to define the location of the LSP. Do you think you could add that (I see it was previously an option)?

I kind of thought it should, though I haven't tried it in a long time: https://github.com/superlou/lapce-python/blob/819f9b016efb136f127500e928e59ce092af51f5/src/main.rs#L40
How does the JavaScript plugin let you specify the LSP location?

Is that the version that is released? Is it not the volt branch? I can configure the path via the UI:

The UI options (I believe) are added by updating the volt file with:
[config."volt.serverPath"]
default = ""
description = "Path to typescript-language-server"

[config."volt.serverArgs"]
default = ["--stdio"]
description = "LSP server arguments to pass when launching"

...whoops. It's been a long time since I've looked at this. It's definitely the volt branch and it looks like I hard coded for some reason:
https://github.com/superlou/lapce-python/blob/c06b31b73d6558a41440f100dbc0cf51ec93731c/src/main.rs#L41
I have a vague memory of there being some limitation in specifying URN paths via the config file, but that doesn't sound right.
I'm happy to accept a PR to add this; otherwise, it might take me a bit to get to.

I have zero rust knowledge so I'm not confident I will be able to fix this but I can give it a go...

@superlou I've opened a PR that adds the ability to do this and works as expected :) you might need to touch things up as this was pretty much a copy paste to make it work

Merged #18 and published the plugin. It looks like it worked, but please double-check that it loads from the plugin host. Thanks!

I tried it and it didn't work :( I did notice that the size of the WASM file was bigger than the one I locally built. If I replace that with the one from my local build it works fine

lapce-python.wasm.zip
If it helps

Crud, it's because I think the file didn't copy. You're right that it's the
wrong one. As soon as I can get to my computer I'll fix it.
On Thu, Mar 28, 2024, 6:06 AM Ash Sykes @.***> wrote:

lapce-python.wasm.zip
https://github.com/superlou/lapce-python/files/14787578/lapce-python.wasm.zip
If it helps
—
Reply to this email directly, view it on GitHub
https://github.com/superlou/lapce-python/issues/17#issuecomment-2024828255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFNIP7CEWTIBUEO3E5ROSDY2PMQJAVCNFSM6AAAAABFKVWQUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUHAZDQMRVGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Try now, please. Should be published as 0.3.4 (and actually built for release).

💥 that did it!

Sorry about that. Thanks for your patience and great contribution!


Add json response to failed login and lockout response

Is this considered breaking?

Holding off on this for now.


Introduce new script routing in apache/dubbo-spi-extensions.

The script routing provided in the repo has been out of date for several releases. We can consider introducing a new script routing mechanism for more convenient and flexible traffic routing support.
For security considerations, we can move the implementation to apache/dubbo-spi-extensions.

The script routing provided in the repo has been out of date for several releases. We can consider introducing a new script routing mechanism for more convenient and flexible traffic routing support.
For security considerations, we can move the implementation to apache/dubbo-spi-extensions.

assign  me,thanks

I recommend removing the script router from 3.3.

@xixingya PATL


Backchannel

Was try to get backchannel working with go2rtc, noticed that the camera doesn't advertise that capability.
in go2rtc 1.9.2, the info link shows the following json for yi-hack-allwinner-v2
{
  "producers": [
    {
      "type": "RTSP active producer",
      "url": "rtsp://<IP_ADDRESS>/ch0_0.h264/",
      "remote_addr": "<IP_ADDRESS>:554",
      "user_agent": "go2rtc/1.9.2",
      "sdp": "...",
      "medias": [
        "video, recvonly, H.264 High 3.2",
        "audio, recvonly, MPEG4-GENERIC/16000"
      ],
      "receivers": [
        "96 H264, bytes=51545563, senders=1",
        "97 MPEG4-GENERIC/16000, bytes=2645133, senders=1"
      ],
      "recv": 54874236
    }
  ],

My other camera which has backchannel support has an additional entry audio, sendonly, PCMU/8000 in producers.medias

There is a type with G711 that I need to fix.
Try with AAC and let me know if it works.

It's already set to AAC.

This is my output:
{
  "producers": [
    {
      "id": 2,
      "format_name": "rtsp",
      "protocol": "rtsp+tcp",
      "remote_addr": "<IP_ADDRESS>:554",
      "url": "rtsp://<IP_ADDRESS>/ch0_0.h264",
      "sdp": "...",
      "user_agent": "go2rtc/1.9.4",
      "medias": [
        "video, recvonly, H264",
        "audio, recvonly, PCMU/8000",
        "audio, sendonly, MPEG4-GENERIC/16000"
      ],
...

Check the configuration.

Yes I am on 0.3.2
Firmware Version | 0.3.2
Base Version | <IP_ADDRESS>_202103291039
Model Suffix | y29ga

I noticed that you're on go2rtc 1.9.4 so I upgraded just to make sure, now my json is like this:
{
  "producers": [
    {
      "id": 43,
      "format_name": "rtsp",
      "protocol": "rtsp+tcp",
      "remote_addr": "<IP_ADDRESS>:554",
      "url": "rtsp://<IP_ADDRESS>/ch0_0.h264",
      "sdp": "...",
      "user_agent": "go2rtc/1.9.4",
      "medias": [
        "video, recvonly, H264",
        "audio, recvonly, MPEG4-GENERIC/16000",
        "audio, recvonly, MPEG4-GENERIC/16000"
      ],

I have non-alt rtsp server, onvif on, rtsp audio set to aac, onvif discovery on, onvif high, backchannel aac

Better, but the 3rd media should be sendonly.
Do you have another cam that works with go2rtc?
I need to check the messages between the cam and the software.
Check this issue too:
https://github.com/roleoroleo/onvif_simple_server/issues/10#issuecomment-2249893385

my other camera (not a allwinner-v2) that has a backchannel looks like this:
{
  "producers": [
    {
      "id": 5822,
      "format_name": "rtsp",
      "protocol": "rtsp+tcp",
      "remote_addr": "<IP_ADDRESS>:554",
      "url": "rtsp://<IP_ADDRESS>/Preview_01_sub",
      "sdp": "...",
      "user_agent": "go2rtc/1.9.4",
      "medias": [
        "video, recvonly, H264",
        "audio, recvonly, MPEG4-GENERIC/16000",
        "audio, sendonly, PCMU/8000"
      ]

Apart from the codec, it's the same ouput I receive from my rtsp.

Good news. I'd love to report that with yi-hack-Allwinner-v2 0.3.3, backchannel works!
I paired it with go2rtc (1.9.4) backchannel support and sound picked up on my laptop mic would come out from the yi-hack speaker!

Could you post your configuration for other users?
Thanks.

Of course!
In yi-hack-Allwinner-v2 0.3.3

Configurations / RTSP server = standard
Configurations / ONVIF / ONVIF audio decoder (backchannel) = G711
Reboot to apply the settings

In go2rtc 1.9.4, goto :1984 web ui, click links on your yi-hack-Allwinner-v2 0.3.3 camera

Scroll the the bottom and find WebRTC Magic section
Select video+audio+microphone = two way audio from camera
Click webrtc.html local WebRTC viewer

https connection to go2rtc is required.

Of course!
In yi-hack-Allwinner-v2 0.3.3
Configurations / RTSP server = standard
Configurations / ONVIF / ONVIF audio decoder (backchannel) = G711
Reboot to apply the settings
In go2rtc 1.9.4, goto :1984 web ui, click links on your yi-hack-Allwinner-v2 0.3.3 camera
Scroll the the bottom and find WebRTC Magic section
Select video+audio+microphone = two way audio from camera
Click webrtc.html local WebRTC viewer
https connection to go2rtc is required.

Sorry, I mean go2rtc configuratrion.

Oh, on the go2rtc side, no specific config is required for backchannel other than a RTSP camera.
The yi-hack side config are more important as AAC didn't work
streams:
  living:
  - rtsp://<IP_ADDRESS>/ch0_0.h264


When I try to start a new run with all hints vague, the run does not start

I have tested a little bit and the only thing I have intentionally changed is how many hints are vague.

But it works with other settings?

Seems to, works with the starting setting and the mostly vague setting

Doesn't work with all precise either

Alright, I'll check it out when I get home, probably a typo somewhere. Thanks for the heads up.

It doesn't work for all vague or all precise, but it works for all the others

Also thanks for making the mod, seems like a great way to randomize Outer wilds!

Fixed in 0.9.4


Detected Entities Report - Add support for EUM MOBILE Applications

Network Requests list
Network Requests performance

Fixed by d26c4d64bb1dfb895a110ecf182ac7340e877d72


Build tiller image for various architectures

Helm already supports cross-compiling and the parent image alpine:3.7 is multi-arch. Therefore, building the tiller image for other architectures rather than x86_64 is straightforward. The docker images can be builti by using make docker-build-images
I also generalized the building process of a single docker image. The default target architecture remains amd64. However, another architecture could be set as the target. For example
$ make GO_ARCH=s390x docker-build

For reference, this is how we build and push the release assets today on a merge to master: https://github.com/kubernetes/helm/blob/4e5139b67c53bc87271e456cbd658c9f448f19d7/.circleci/deploy.sh#L53-L64

Sure. Update deploy.sh to accept an arg for arch. Then update .circleci.yaml to pass the $arch string at the deploy step (not sure how you do that with circle specifically though). On its own this change won't change the current process but it at least allows for the option. If CNCF decides to host the builds elsewhere they just update deploy.sh? Just my two cents.

@bacongobbler I didn't think to add into circleci. But that also depends how now you want to call your images. With kubernetes style you could append the architecture at the end of the image name or another possibility could be to create a multi-arch image. The advantage of the second approach would be that you do not have to change the name of the tiller image. Would you pack everything in a PR or better a second one?
I'm traveling this week and then I will take some vacation. Therefore, the discussion will be a bit slow down.

After doing a little research, there appears to be some new work available where we can distribute arch-specific images (talks at DockerCon 2017) and then create a manifest list that points to these individual images. That way, docker run gcr.io/kubernetes-helm/tiller will pull the right architecture required for the OS running the image. That looks like a good approach in the long run to me! :)
The first part would be the easiest to tackle: we start by releasing arch-specific images of tiller like gcr.io/kubernetes-helm/tiller-arm. The second part would be tricky, as we would basically need to replace gcr.io/kubernetes-helm/tiller with a manifest list, and that might break stuff if it's still an experimental feature.
I think taking the approach where we distribute images with the architecture being appended to the end of the image name would be a good first step, and then once the latter features become more stable we can start adding support for that. How do you feel about that approach?

yes it sounds reasonable. I haven't tried the docker manifest command yet. I know that the Docker developers used the manifest-tool to create the multi-arch image. But I understand that you want to wait for the manifest command.
Do you want that I include the modifications at helm/.circleci/deploy.sh in this PR?

hi, I just realized that the PR is actually wrong, sorry. It actually cross-compiles the binaries for the different images, but the parent image remains x86


Switches are not responsive enough on zooming in/out the window

I just came across with one UI issue with bootstrap switches.
We can reproduce the issue by zooming in the page and then hitting refresh button.It actually happens when zooming to 90% and then reloading the page.

There appears to be a fix documented in #469


podman create POD

Why no podman create POD for parity with podman rm POD?
Or is it waiting for https://github.com/containers/podman-compose to specify a file?

the parity is podman pod create and podman pod rm

Oops. Fixed.

are you talking about assigning a name to the pod?

Yes.

do you object to the use of --name?

For scripts it doesn't matter, but for command line I forget about it.

@rhatdan so why no podman pod create NAME?

podman container create uses --name
podman volume create
podman network create
Work the way you want, so I guess we could/should do Pods the same way.  Interested in opening a PR for this?

@rhatdan seems easy. Takes time to setup dev env though. Are there plans for podman pod create to use templates like kubernetes?

We use podman play kube for that.  It reads a kubernetes yaml file and creates the pod.

Wow. I didn't even know that.

Are there any simple formats planned for defining pods? I've got a feeling that Kubernetes artillery is too heavy for startups, and docker-compose model is too limited to a single node to be followed 1 to 1.

Podman goal is not to be an orchestrator, only to work with orchestrators, If community wants to add podman play compose, we would listen.  There is also a podman-compose project.
Podman 2.0 has implemented the APIV2 which should be able to support Docker-compose and other docker-py based libraries.
When it comes to orchestrators we plan to push people towards Kubernetes, because we believe this is the future.


How to Set Animation Loop?

Hello, I want to know how to set animation loop?

If you take a look at the file ContinuousAnimations.cs You can see a fairly complex one, which is the mouse hover animations in the example.
A more simple example would be to use something like the following:
// -- This would be put somewhere in your editor/inspector hierarchy
myVisualElement.schedule.Execute(AnimationToLoop).Every(10).StartingIn(0);

// -- This would go somewhere in your editor/inspector as well
public void AnimationToLoop(()
{
	// -- My animation goes here
}

This takes the element you want to animate (myVisualElement) and then creates a scheduler on it using the Every() function, which would then continually loop. If you want to be able to control it, though, you will need to keep track of the scheduler via a IVisualElementScheduledItem myScheduledItem; like this:

private IVisualElementScheduledItem myScheduledItem;

// -- elsewhere
myScheduledItem = myVisualElement.schedule.Execute(AnimationToLoop).Every(10).StartingIn(0);

// -- This will then let you call things such as:
myScheduledItem.Pause();
myScheduledItem.Resume();

Thanks,
-id


Restore logic for tests skipped in merge queue

The logic for faking tests that are required for but do not run when testing a PR in the merge queue was broken in #129.
This PR restores the logic that was used prior to that PR.
CI runs:

Merge queue run before this PR on Mbed-TLS/mbedtls#8328
Merge queue run with this PR on Mbed-TLS/mbedtls#7959

(The test commit in Mbed-TLS/mbedtls#7959 states that it introduces a conflict with the base branch, but to expedite testing this PR it was repurposed and the conflict was removed from the base branch. The expected result for its merge queue run is SUCCESS.)

https://jenkins-mbedtls.oss.arm.com/job/mbed-tls-pr-ci-testing/job/gh-readonly-queue%252Fdev%252Fbensze01%252Fmerge-queue-test%252Fpr-7959-e7ebec6723b61bd54800f649b1391e980edf2fbd/2/flowGraphTable/ isn't finished but has passed the relevant stage. This is very high priority since the current code is faking successes on pr-head runs. Merging.


Dead link in https://docs.docker.com/install/linux/docker-ce/debian/

Problem description
The page https://docs.docker.com/install/linux/docker-ce/debian/ contains a link to
https://docs.docker.com/install/linux/docker-ce/#install-using-the-repository, but that page doesn't seem to exist:

Sorry, we can't find that page
[a picture]
Please file an issue at https://github.com/docker/docker.github.io.

Hi There,
We can't find the link you're referring to on the Debian installation page. Do you still see the issue?

Hi, the link seems to have changed to https://docs.docker.com/install/linux/docker-ce/debian/#install-using-the-repository, which works.
So no more issue. I'll close.


Remove key option for createOptions

With #58 the key option remains as a small convenience (it replaces typing format: value=>value[key]). But it does result in some complexity internally and also potential surprises - e.g. using defaultFormat externally will not give the same result as when it is called by default because internally there is also processing of the key option if supplied.
Consider removing key to keep things simpler long term.

In 44423cfc69890188b2e294c050fe36b37829be57, found a reasonable approach for keeping the key and maintaining consistency / avoiding surprises. So will not pursue this issue now.


python311Packages.distutils-extra: rename from distutils_extra

Description of changes
part of #245383

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 260573 run on x86_64-linux 1

4 packages built:

python310Packages.distutils-extra
python310Packages.distutils-extra.dist
python311Packages.distutils-extra
python311Packages.distutils-extra.dist


Fix: update bluebanquise github link

Is it expected to mix 2 unrelated commits in this PR?

Hello
Well not really. I did this part too fast. I will split :-)
Thanks for raising that !


Creating a text editor and adding it to active pane with a long text results in a tab without a scrollbar

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
This bug occurs when using Atom's API programmatically, not by using it normally.
Using setText on a TextEditor with text exceeding window height results in a text editor without a scrollbar with no way to access off-screen contents (unless you select off-screen text and deselect it causing the buffer to jump to it.
Steps to Reproduce

Try the following snippet in your init script:

let pane = atom.workspace.getActivePane();
let fileEditor = atom.workspace.buildTextEditor();
let item = pane.addItem(fileEditor);
pane.activateItem(item);
fileEditor.setText(content);

Where content is some very long string.
Expected behavior:
The created text editor that's added to the pane should come with a scrollbar.
Actual behavior:
It has no scrollbar, as described above.
Reproduces how often:
Always
Versions
Atom    : 1.24.0
Electron: 1.6.16
Chrome  : 56.0.2924.87
Node    : 7.4.0
OS: Mint 18
Additional Information
N/A

Thanks for the report!  I can reproduce but I thinks this is a duplicate of https://github.com/atom/atom/issues/14811?  See https://github.com/atom/atom/issues/14811#issuecomment-309467775 and the summary in https://github.com/atom/atom/issues/14811#issuecomment-311849256.
As mentioned in that comment, this can be fixed with:
fileEditor = atom.workspace.buildTextEditor({autoHeight: false});

If I mis-understood anything let me know.

Yeah that fixes the issue.


fading

Is ite possible to fadeIn and fadeOut the items when showing and hiding them ?

But can´t var oldDisplay = len > 0 ? lis[0].style.display : "block";
be changed to have a fadeIn()  ?
Is it possible for me to alter the code a liitle bit ?

You're more than welcome to fork it, but the change isn't quite that simple (though it isn't too difficult): you'd just need to change all portions that reference li.style.display into something else, maybe li.fadeIn() or $(li).fadeIn() (not sure which, you'd have to test it)

This is probably the change you'd need:
=== modified file 'jquery.fastLiveFilter.js'
--- jquery.fastLiveFilter.js	2011-11-07 22:06:24 +0000
+++ jquery.fastLiveFilter.js	2011-11-08 18:18:55 +0000
@@ -32,12 +32,14 @@
 			li = lis[i];
 			if ((li.textContent || "").toLowerCase().indexOf(filter) >= 0) {
 				if (li.style.display == "none") {
-					li.style.display = oldDisplay;
+					$(li).fadeIn();
 				}
 				numShown++;
 			} else {
 				if (li.style.display != "none") {
-					li.style.display = "none";
+					$(li).fadeOut();
 				}
 			}
 		}

It might be faster to use jQuery's .each() instead of $(li) inside the loop.  For small data sets, it may not matter much.

Thank you.
This worked.
What did you mean with using each() instead of $(li) ?
Is it like this ? $li.each().fadeOut();

No, it'd be more like the examples in the jQuery each() API, but after glancing at it I don't think it'd be any faster.

ok. thnak you.
Nice work.

No problem! Glad I could help.


Make manual merge autodetection optional and add manual merge as merge method

as title, Before this pr, we use same way with GH to check manually merge.It good, but in some special cases, misjudgments can occur. and it's hard to fix this bug. So I add option to allow repo manager block "auto check manual merge" function, Then it will have same style like gitlab(allow empty pr). and to compensate for not being able to detect the pr merge automatically, I added a manual approach.
example view:

Codecov Report

Merging #12543 into master will decrease coverage by 0.08%.
The diff coverage is 15.00%.

@@            Coverage Diff             @@
##           master   #12543      +/-   ##
==========================================
- Coverage   43.49%   43.40%   -0.09%
==========================================
  Files         642      642
  Lines       71013    71123     +110
==========================================
- Hits        30889    30873      -16
- Misses      35117    35249     +132
+ Partials     5007     5001       -6

Impacted Files
Coverage Δ

modules/auth/repo_form.go
42.34% <ø> (ø)

modules/structs/repo.go
54.54% <ø> (ø)

routers/api/v1/repo/pull.go
23.25% <0.00%> (-1.80%)
:arrow_down:

routers/repo/pull.go
32.14% <0.00%> (-1.56%)
:arrow_down:

routers/repo/setting.go
14.80% <0.00%> (-0.05%)
:arrow_down:

routers/api/v1/repo/repo.go
61.68% <33.33%> (-0.47%)
:arrow_down:

services/pull/check.go
22.14% <40.00%> (-25.55%)
:arrow_down:

routers/repo/issue.go
37.68% <60.00%> (+0.08%)
:arrow_up:

routers/repo/compare.go
40.90% <66.66%> (+0.35%)
:arrow_up:

models/pull.go
54.82% <100.00%> (-0.35%)
:arrow_down:

... and 12 more

Continue to review full report at Codecov.

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

I've fixed the tests and improved the reporting of manual merge not allowed in the API

@zeripath Thanks for your help. I found these codes are marked as "red" in the codecove report, I wonder the reason, Maybe it still have some bug?

link: https://codecov.io/gh/go-gitea/gitea/src/5d1b12c1ba4e462aeefe1edd5b388b0d3a4076c4/services/pull/merge.go

Need more work about test code :(

🚀


Revert "Remove debug tile layer in rendering test"

Reverts openlayers/openlayers#16329
The test was failing in #16327 because it was setting a UTM projection extent which resulted in a different tile grid for projection being used when the debug tiles were reprojected from EPSG:3857 to UTM.  Since there should have been no attempt to make any transforms before the view was set I do not think that code should have been called so soon,  It is setting a projection extent even if the projection is already defined in proj4.
The debug tiles were there to show the COG is corrected positioned when rotated.

Since there should have been no attempt to make any transforms before the view was set I do not think that code should have been called so soon, It is setting a projection extent even if the projection is already defined in proj4.

I'm not sure I understand this. Here is what I see:
In the GeoTIFF source, we read the metadata and try to create a projection instance.  https://github.com/openlayers/openlayers/blob/4e35e39f60843021b7b13e25a7076c39f9dec3f2/src/ol/source/GeoTIFF.js#L727-L729
This is where the OpenLayers built-in UTM support is used in #16327.
After that, in your rendering test code, you register proj4. https://github.com/openlayers/openlayers/blob/4e35e39f60843021b7b13e25a7076c39f9dec3f2/test/rendering/cases/cog-rotation/main.js#L27-L34
Since you are not using any information from the resolved viewConfig, I think it would make sense to move the proj4.defs() and register() calls to the top.

Actually, it looks like register doesn't use the proj4 transforms if there already is one available.
https://github.com/openlayers/openlayers/blob/4e35e39f60843021b7b13e25a7076c39f9dec3f2/src/ol/proj/proj4.js#L52-L66
This was surprising to me. It would be nice if there was a way to say you prefer to use proj4.

Actually, it looks like register doesn't use the proj4 transforms if there already is one available.

I updated this code in #16327 so that register will use the proj4 transforms if a projection has not been added with addProjection already.


Update create_dataset.mdx

modified , as AudioFolder and ImageFolder not in Dataset Library.
from datasets import AudioFolder  and from datasets import ImageFolder  to from datasets import load_dataset
cannot import name 'AudioFolder' from 'datasets' (/home/eswardivi/miniconda3/envs/Hugformers/lib/python3.10/site-packages/datasets/__init__.py)

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


Termux

The 2.2.2 version is working perfectly back in the days but not anymore and the problem with 3.0 it can't work with termux

V3 uses multiprocessing. Multiprocessing isn't supported on android. You can write up a script using spotdl as a library but its be much slower.


Add body text and link

Added informational content on combinations and permutations calculators as well as their respective (brief) explanations and links to the corresponding Wikipedia articles and calculator implementation

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Sending a more explicit header when doing a scan/query from Smoothie

What

Sending a more explicit header when doing a scan/query from Smoothie

At the moment the log looks like this:
xxxx - - [10/Jun/2022:15:02:48 +0200] "POST /cgi/display.pl?api/v0/product/8059070744132.json HTTP/1.0" 200 20617 "-" "Dart/2.17 (dart:io)" 0/54837

When a scan it could say Open Food Facts vXXX - Scan
When a search it could say Open Food Facts vXXX - Search

Please also add the platform ios / android

Can we use User-Agent? @teolemon
Or the uuid like we wanted to do in the Android native app?
https://github.com/openfoodfacts/openfoodfacts-androidapp/issues/4438

https://github.com/openfoodfacts/openfoodfacts-dart/pull/213/files

You're already supposed to see something like that, isn't that the case?
  UserAgent(
    name: 'Smoothie - ${packageInfo.appName}',
    version: '${packageInfo.version}+${packageInfo.buildNumber}',
    system: Platform.operatingSystemVersion,
    url: 'https://world.openfoodfacts.org/',
  );

Regarding using the user agent for a distinction between scan and search, it would mean changing the user agent for each query (ok, we have the technology for that) while it's supposed to be kind of static.

Correction: the "user agent" parameters are supposed to appear as get/post parameters (cf. HttpHelper)
      map['app_name'] = OpenFoodAPIConfiguration.userAgent!.name!;
      map['app_version'] = OpenFoodAPIConfiguration.userAgent!.version!;
      map['app_uuid'] = OpenFoodAPIConfiguration.uuid!;

@teolemon Actually looking back at the OP we don't call /cgi/display.pl from off-dart; maybe it's a redirection done on the server where we unfortunately dismiss the POST parameters.

@monsieurtanuki is that ok for @cli1005 to work on this ? As we get Dart info in the logs, I believe it's a client side issue (eg Smoothie)

@cli1005 Indeed. We should probably add something like app_system (e.g. 'android 12). Beyond that, a more generic optional commentwould make sense (e.g.scan). Or specific to barcode search, a sourceparameter (e.g.scan/search). Don't know which would be the best solution as I don't see the full picture, but a generic dev_comment` would be versatile.

app_platform and comment have been added into UserAgentParameters (https://github.com/openfoodfacts/openfoodfacts-dart/issues/482).
As monsieurtanuki mentioned, we do not call display.pl in OFF API, among all perl called, we do not sent UserAgentParameters for only 4 following PL:

test.pl
product_image_upload.pl  (is it normal? why?)
user.pl
reset_password.pl

I could add Scan/ Search in parameter comment will sending in Smoothie, but it might be better to do it in OFF API...

Regarding using the user agent for a distinction between scan and search, it would mean changing the user agent for each query (ok, we have the technology for that) while it's supposed to be kind of static.

Hi @monsieurtanuki, having the app name + platform + source of query (scan, or search, or list) in the UserAgent is very useful server side as we get the UserAgent in the nginx + Apache logs directly, before we interpret GET or POST parameters.
This is used currently to get scan statistics from our app for products: we just parse nginx logs.

@stephanegigandet Ok then. We go a little beyond the normal use of User Agent, fair enough. A little problem is that the User Agent is static: that made sense to use a static field for characteristics that don't change often (e.g. device or app version), that's a bit lousy for something that is supposed to be changed at every request (e.g. 2 requests in parallel and the second request overwrites the first one's user agent). I guess we can live with that, it's not like one user scans two products at the very same time. With @cli1005's #484. now we have a "comment" field in user agent, so we are ok I guess:
  const UserAgent({
    this.name,
    this.version,
    this.system,
    this.url,
    this.comment,
  });


How to stop it?

Thanks for the project.
But when I want to stop it and restore MAC's defaults, what should I do?
Just
sudo bclm write 100  ???

Exactly, that's the default value. Nothing else to do if you simply want to turn it off and not uninstall.


fix typo volumes.md

close PR https://github.com/kubernetes/website/pull/28771
@kamyar thanks for finding a typo

/lgtm

/kind cleanup

/approve


Chapter 4: Early Stopping

In the book is not mentioned to use the method ravel in the y_train, but if I don't use it the code crushes. The variables X_train, x_val, y_train and y_val, I created them with the method split.
X_train, X_val, y_train, y_val = train_test_split(X, y, test_size=0.2)
for epoch in range(1000):
sgd_reg.fit(X_train_poly_scaled, y_train.ravel()) # continues where it left off
y_val_predict = sgd_reg.predict(X_val_poly_scaled)
val_error = mean_squared_error(y_val, y_val_predict)
if val_error < minimum_val_error:
minimum_val_error = val_error
best_epoch = epoch
best_model = deepcopy(sgd_reg)
If I'm doing something wrong please can anyone tell me what I'm doing wrong!!

Hi saguillo2000
The problem is that the two X_train_poly_scaled and y_train dont have the same length
I suspect the problem originates ahead of what you've written. Try to review your data preparation code lines especially
poly_scaler = …,
X_train_poly_scaled = …,
or the determination of
sgd_reg = …


Controller duplication

Address duplication in the create, update, and destroy methods in the vendors and products controller by consolidating error checking and redirection in a single method. Currently, those two controllers still have very similar code, so I can look into refactoring that as well if you guys think it's worth it.

This looks good, but it might be good to include documentation/comments to better explain the role of ControllerVerification and the flow of program logic.


tests had invalid storage offset

Problem
offsets in the index have to be 8 byte aligned since append vecs always stored on 8 byte aligned boundaries. This has not been important before now. Changes coming soon expose these offsets as sloppy and cause failures.
Summary of Changes
Set offsets to be 8 byte aligned.
Fixes #

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

Project coverage is 81.8%. Comparing base (033bcfc) to head (241b9c2).

Additional details and impacted files
@@            Coverage Diff            @@
##           master     #874     +/-   ##
=========================================
- Coverage    81.8%    81.8%   -0.1%
=========================================
  Files         851      851
  Lines      231475   231475
=========================================
- Hits       189504   189466     -38
- Misses      41971    42009     +38


🔉 📖 Add API for Creating Sounds from Readers

resolves #10
There are other ways you could do this so let me know what you're preferred API is, but here's something that works well enough. 🙂

looks good, thank you!

you're ok with your contribution being MIT licensed, right? i'm just asking because i just realized you're the creator of the Katharos license, and I don't have a notice about contributions being licensed a certain way in the readme

Yep. You're good. :+1: I contributed willingly under the terms of the current license of this repo. 🙂


🔧 Allow superproject to provide dependencies with add_subdirectory()

This lets a superproject vendor cpp-yyjson along with these dependencies, doing something like:
add_subdirectory(yyjson)
add_subdirectory(fmt)
add_subdirectory(nameof)
add_subdirectory(cpp-yyjson)

and cpp-yyjson will use the dependencies provided by the parent Cmake project, without trying to find them installed.

Merged, thanks!

Thanks! And thanks for the second pass, I overlooked the versioning checks.


Cannot brew update anymore

Please follow the general troubleshooting steps first:

[X] Ran brew update and retried your prior step?
[X] Ran brew doctor, fixed as many issues as possible and retried your prior step?
[X] If you're seeing permission errors tried running sudo chown -R $(whoami) $(brew --prefix)?

You can erase any parts of this template not applicable to your Issue.
Bug reports:
Seeing the following error when trying to update brew:
Checking out v1.0.0 in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core...
To checkout master in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core run:
  'cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core && git checkout master
fatal: Cannot update paths and switch to branch 'v1.0.0' at the same time.
Did you intend to checkout 'refs/tags/1.0.0' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/1.0.0

Failing since there is no v1.0.0 in homebrew-core (actually, no tags at all!). I updated brew yesterday successfully (including migration to the Homebrew subdirectory).
Shouldn't the Taps be tracking master at all times anyway? brew itself is at v1.0.0.

Ack! Nevermind. I just saw v1.0.1 come down that fixes this. Sorry for the noise.

Sorry for the trouble.

No problem. But, should this be reopened? I had to manually update to 1.0.1 as brew would not go from 1.0.0 to 1.0.1 automatically.

I haven't been following this round of issues closely due to work at hand but I think the discussions are mainly happening in the PR that introduced updating to tags: #998.

That's it. Thanks!


This is not working on Google Colab

System Info
Google Colab - T4
Reproduction
!python -m bitsandbytes
===================================BUG REPORT===================================
Welcome to bitsandbytes. For bug reports, please run
python -m bitsandbytes
and submit this information together with your error trace to: https://github.com/TimDettmers/bitsandbytes/issues
False
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:147: UserWarning: /usr/lib64-nvidia did not contain ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] as expected! Searching further paths...
warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:147: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/sys/fs/cgroup/memory.events /var/colab/cgroup/jupyter-children/memory.events')}
warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:147: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('//<IP_ADDRESS>'), PosixPath('http'), PosixPath('8013')}
warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:147: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('//colab.research.google.com/tun/m/cc48301118ce562b961b3c22d803539adc1e0c19/gpu-t4-s-jinqj9x2q0e4 --tunnel_background_save_delay=10s --tunnel_periodic_background_save_frequency=30m0s --enable_output_coalescing=true --output_coalescing_required=true'), PosixPath('--logtostderr --listen_host=<IP_ADDRESS> --target_host=<IP_ADDRESS> --tunnel_background_save_url=https')}
warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:147: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/datalab/web/pyright/typeshed-fallback/stdlib,/usr/local/lib/python3.10/dist-packages')}
warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:147: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/env/python')}
warn(msg)
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py:147: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('//ipykernel.pylab.backend_inline'), PosixPath('module')}
warn(msg)
CUDA_SETUP: WARNING! libcudart.so not found in any environmental path. Searching in backup paths...
CUDA SETUP: CUDA runtime path found: /usr/local/cuda/lib64/libcudart.so
CUDA SETUP: Highest compute capability among GPUs detected: 7.5
CUDA SETUP: Detected CUDA version 122
CUDA SETUP: Required library version not found: libbitsandbytes_cuda122.so. Maybe you need to compile it from source?
CUDA SETUP: Defaulting to libbitsandbytes_cpu.so...
================================================ERROR=====================================
CUDA SETUP: CUDA detection failed! Possible reasons:

CUDA driver not installed
CUDA not installed
You have multiple conflicting CUDA libraries
Required library not pre-compiled for this bitsandbytes release!
CUDA SETUP: If you compiled from source, try again with make CUDA_VERSION=DETECTED_CUDA_VERSION for example, make CUDA_VERSION=113.
CUDA SETUP: The CUDA version for the compile might depend on your conda install. Inspect CUDA version via conda list | grep cuda.
================================================================================

CUDA SETUP: Something unexpected happened. Please compile from source:
git clone git@github.com:TimDettmers/bitsandbytes.git
cd bitsandbytes
CUDA_VERSION=122
python setup.py install
CUDA SETUP: Setup Failed!
Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 187, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/usr/lib/python3.10/runpy.py", line 146, in _get_module_details
return _get_module_details(pkg_main_name, error)
File "/usr/lib/python3.10/runpy.py", line 110, in _get_module_details
import(pkg_name)
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/init.py", line 6, in
from . import cuda_setup, utils, research
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/research/init.py", line 1, in
from . import nn
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/research/nn/init.py", line 1, in
from .modules import LinearFP8Mixed, LinearFP8Global
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/research/nn/modules.py", line 8, in
from bitsandbytes.optim import GlobalOptimManager
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/optim/init.py", line 6, in
from bitsandbytes.cextension import COMPILED_WITH_CUDA
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/cextension.py", line 20, in
raise RuntimeError('''
RuntimeError:
CUDA Setup failed despite GPU being available. Please run the following command to get more information:
    python -m bitsandbytes

    Inspect the output of the command and see if you can locate CUDA libraries. You might need to add them
    to your LD_LIBRARY_PATH. If you suspect a bug, please take the information from python -m bitsandbytes
    and open an issue at: https://github.com/TimDettmers/bitsandbytes/issues

Expected behavior
That it should have detected the GPU and worked on it.

@gauravjoshi2034 What version of bitsandbytes are you trying this with? It looks to me like it might be <=0.38.0. I just tried on a T4 Colab and it works for me with the latest 0.42.0 release. If you can upgrade to >=0.40.0 then that should solve your issue.

@gauravjoshi2034 is your problem solved or no longer an issue? it would be good to close this issue if it no longer requires attention of others. Thank you.


Bot only works on Emulator. Other channels are displaying 'There was an error sending this message to your bot: HTTP status code GatewayTimeout' error

Bot Info

Bot handle: Medibot_medibuddy
App ID: dcda60fe-72d4-4796-a728-de8fa3aef2a5
SDK Platform: Node.js
SDK Version: Latest
Active Channels: WebChat, Facebook, Skype
Deployment Environment: Azure App Service

Issue Description
Our bot (Medibot, https://medibotmb.azurewebsites.net) has suddenly stopped working on all channels including WebChat. It works perfectly on Emulator though. We've been trying to debug this issue since days and have not been successful with any solutions/suggestions online. I've tried using Log stream and debug console to catch exceptions but there aren't any. Kindly expedite.

Code Example
The code is hosted in https://github.com/nirmalrayan/medibot
Reproduction Steps

Visit medibotmb.azurewebsites.net. This should ideally open WebChat channel's index.html document.
The page tries to load for a long time and throws HTTP status: 500, HTTP subStatus: 1001, HTTP Reason: Internal Server Errror.
Bot framework displays the error message 'There was an error sending this message to your bot: HTTP status code GatewayTimeout' for Facebook and Web Chat channels.

Expected Behavior

Render index.html page with Web Chat iframe.
After the user sends first message, the bot welcomes with a hero card.

Actual Results
Nothing happens. The page does not get rendered. No exception in thrown in log stream while testing. Even botframework 'Test' does not throw any error in Azure app service log stream. Please assist at the earliest.
node.js

duplicate of https://stackoverflow.com/questions/46564927/why-botframework-bot-only-works-only-on-emulator-and-none-of-the-other-channels

closing as duplicate.
Please don't double-post on GitHub and StackOverflow. We monitor both forums.

This issue has come back to the same bot. I destroyed the entire resource group from Azure and re-created everything, the issue still persists. Currently my bot credentials are:
Bot handle: medibot_4ttx4fdwLSX
App ID: e3c69ebc-068b-4fa6-a18e-b42b8311adeb
SDK Platform: Node.js
SDK Version: Latest
Active Channels: WebChat, Skype
Deployment Environment: Azure App Service

Are you able to post your complete bot code so we can try to reproduce?

@JasonSowers : The code is hosted here https://github.com/nirmalrayan/medibot
There is a change in the URL https://medibot.azurewebsites.net/

@nirmalrayan
When I checked the new URL, the server returned the following errors:

iisnode encountered an error when processing the request.
HRESULT: 0x2
HTTP status: 500
HTTP subStatus: 1001
HTTP reason: Internal Server Error
You are receiving this HTTP 200 response because system.webServer/iisnode/@devErrorsEnabled configuration setting is 'true'.
In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem.
The node.exe process has not written any information to stderr or iisnode was unable to capture this information. Frequent reason is that the iisnode module is unable to create a log file to capture stdout and stderr output from node.exe. Please check that the identity of the IIS application pool running the node.js application has read and write access permissions to the directory on the server where the node.js application is located. Alternatively you can disable logging by setting system.webServer/iisnode/@loggingEnabled element of web.config to 'false'.
It looks like there is a problem with the bot deployment.

Hi Nils,
My code is available at nirmalrayan/medibot. It seems to execute without any errors. I've attached screenshot for reference.
|
|
|
|  |  |
|
|
|
|  |
nirmalrayan/medibot
medibot - Conversation Bot for Medi Assist and MediBuddy using Microsoft Bot Framework
|
|
|
Regards,
Nirmal Rayan
M.Tech (Computer Science & Engg.), B.E
+91 99163 68334
On Friday, December 8, 2017, 10:39:32 PM GMT+5:30, Nils<EMAIL_ADDRESS>wrote:

@nirmalrayan
When I checked the new URL, the server returned the following errors:
iisnode encountered an error when processing the request.
HRESULT: 0x2
HTTP status: 500
HTTP subStatus: 1001
HTTP reason: Internal Server Error
You are receiving this HTTP 200 response because system.webServer/iisnode/@deverrorsenabled configuration setting is 'true'.
In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem.
The node.exe process has not written any information to stderr or iisnode was unable to capture this information. Frequent reason is that the iisnode module is unable to create a log file to capture stdout and stderr output from node.exe. Please check that the identity of the IIS application pool running the node.js application has read and write access permissions to the directory on the server where the node.js application is located. Alternatively you can disable logging by setting system.webServer/iisnode/@loggingenabled element of web.config to 'false'.
It looks like there is a problem with the bot deployment.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

The only document missing in my code will be the .env file. I could share the file with you if you want to reproduce the issue at your end. Kindly expedite.
Regards,
Nirmal Rayan
M.Tech (Computer Science & Engg.), B.E
+91 99163 68334
On Friday, December 8, 2017, 10:45:14 PM GMT+5:30, Nirmal Rayan<EMAIL_ADDRESS>wrote:

Hi Nils,
My code is available at nirmalrayan/medibot. It seems to execute without any errors. I've attached screenshot for reference.
|
|
|
|  |  |
|
|
|
|  |
nirmalrayan/medibot
medibot - Conversation Bot for Medi Assist and MediBuddy using Microsoft Bot Framework
|
|
|
Regards,
Nirmal Rayan
M.Tech (Computer Science & Engg.), B.E
+91 99163 68334
On Friday, December 8, 2017, 10:39:32 PM GMT+5:30, Nils<EMAIL_ADDRESS>wrote:

@nirmalrayan
When I checked the new URL, the server returned the following errors:
iisnode encountered an error when processing the request.
HRESULT: 0x2
HTTP status: 500
HTTP subStatus: 1001
HTTP reason: Internal Server Error
You are receiving this HTTP 200 response because system.webServer/iisnode/@deverrorsenabled configuration setting is 'true'.
In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem.
The node.exe process has not written any information to stderr or iisnode was unable to capture this information. Frequent reason is that the iisnode module is unable to create a log file to capture stdout and stderr output from node.exe. Please check that the identity of the IIS application pool running the node.js application has read and write access permissions to the directory on the server where the node.js application is located. Alternatively you can disable logging by setting system.webServer/iisnode/@loggingenabled element of web.config to 'false'.
It looks like there is a problem with the bot deployment.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Fixed it! Turns out that I had defined TCP port in Azure Application Settings (of my app service) which is in straight violation because Azure uses NamedPipes within IIS. So, if you've defined PORT = <> in your application settings, remove it and restart your app service. This problem should be resolved.


Support for SpaceToDepth operator

Implement the SpaceToDepth operator. The operator outputs a copy of the input tensor where values from the height and width dimensions are moved to the depth dimension. The attr blocksize indicates the input block size.

blocks of size blocksize x blocksize are rearranged into the depth dimension
The new depth is blocksize * blocksize * depth
The input tensor's height and width must be divisible by block_size.

Given input tensor [N,C,H,W] the output tensor has shape  [N, C * blocksize * blocksize, H/blocksize, W/blocksize].
The transformation can be seen as a sequence of a reshape + transpose + reshape operations:
   NC  = C * (blocksize * blocksize)
   NH = H / blocksize
   NW = W / blocksize

   tmp1 = reshape(input, [N, C, NH, blocksize, NH, blocksize])
   # new axis: [num, ch, scale_factor, scale_factor, new_height, new_width]
   tmp2 = transpose(tmp1, [0, 1, 3, 5, 2, 4])
   out = tensor.reshape(tmp2, [N, NC, NH, NW])

PRs are being reviewed and merged

PR #921 is not merged so I prefer to keep this work item open until then.


fix: cant get the valid shape form node

node 的 shape 和 dtype 可能为 None

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.caowengang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Force trusted setup if circuits have been modified

What does this implement/fix? Explain your changes.
The goal of this pr is to check if there have been any changes to the circuits and if so, go to force a trusted setup.
To do this is kept within the /output/circuithash.txt (in the worker), the list of all circuits with their hash.
So it checks if the hash of the current circuit differs, or is not in the file, and in case a trusted setup is forced
Does this close any currently open issues?
Resolves #989

in case new circuits were added:
-if the hash is present in the file but does not match the one just calculated, the hash contained in the file is updated and the trusted setup is generated.
-if, on the other hand, the hash is not present in the file, it is added to the file and the trusted setup is generated


Update to graphite version 1.1.3

The latest version is 1.1.3 - the pip package list
is derived from a 'pip freeze' in a virtualenv with
the graphite-web, carbon and whisper packages
installed in it. This ensures that the packages and
everything they depend on is always the same when
deploying.

It looks like the test prep script is broken. :/

@nsg It would appear that the failures in CI have something to do with the image setup. Do you have any ideas what's going wrong and how it may be fixed?

@odyssey4me I will see what I can do. I will try to track down the problem tomorrow (in about 24 hours from now, in my timezone).

FYI: I finally fixed the test images

Great, thanks @nsg - will figure that bit out and add another commit.

OK, it looks like there are some legitimate failures going on now - I'll try and replicate them when I have some time to do so and see what needs fixing.

@nsg This is odd. In the test we fail for CentOS and Ubuntu Trusty, yet when I execute the test myself on a test host, I get a failure for both Debian but the others all pass. If you have a little time could you take a look and give me some pointers?

My test fails with:

file: not found: The command file is not found.

The travis test fails with:

The process carbon-cache is not running, and we have a few errors in the logs.

Abandoning this for now. I may return back to it when I have some time to figure it out.


nix tag 0.20.0 not available on github

For some reason the git tag for nix 0.20.0 (the latest release) is not available in the nix github repo. (cargo will pick up nix 0.20.0 though).
Was wondering why we don't have the tag in this repo...

That was just an oversight.  Fixed now.


refactor: rework aged authentication config interface

Fixes #
Description
Part of #224
How was this change tested?

Unit tests
E2E

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[X] No

Release Note

- Deprecate `ARM_USE_CREDENTIAL_FROM_ENVIRONMENT` and `ARM_USE_MANAGED_IDENTITY_EXTENSION` in favor of newly introduced `ARM_AUTH_METHOD`
- Rename `ARM_USER_ASSIGNED_IDENTITY_ID` to `ARM_KUBELET_IDENTITY_CLIENT_ID` for accuracy to its purpose/use

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

49 of 56 (87.5%)  changed or added relevant lines in 7 files are covered.
7 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.1%) to 97.917%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/auth/autorest_auth.go
0
7
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/auth/autorest_auth.go
1
0.0%

pkg/auth/util.go
2
0.0%

pkg/auth/config.go
4
78.13%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
36240

Relevant Lines:
37011

💛  - Coveralls


Build docker images for all nodes

This PR attempts to add the docker images described in the workshop. For now it is only a polkadot image.

I've merged this work into #7, so I'm closing this one.


Document Key Vault libraries at package level

This reorganizes Key Vault libraries such that all modules are private or in a private subpackage, and everything we want to document publicly is exposed at the package level. I focused on organizational changes here, some docstrings still need content revision.

Can one of the admins verify this patch?


Reconcile algorithm overuses the Doppler API

We have been swapping out an in-house k8s reloading/secret handling solution to this official operator solution. Previously we used Doppler Webhooks for reloading, and an init script at container startup to load the current secrets.
What we have noticed since migrating is that we gets lots of these errors in the pod logs:
Doppler Error: Exceeded rate limit of 240 secret read requests within 60 seconds. Retry in 1 seconds. Upgrade to the Enterprise plan to increase your limit

We have many DopplerSecret custom resources (but many of them reference the same Doppler Config actually). Despite there being many, they rarely ever change (on the frequency level of 1-2 changes per week), so we should not exceed the API rate limits.
It doesn't make any sense to me that the operator needs to HTTP-GET all secrets every N seconds from the Doppler API. It should be able to use a functionality similar to the Webhooks to do push-based reconciliation instead of polling Doppler. Doing so would drastically reduce the API load on Doppler.
I would propose one of two solutions:

Stick to polling, rely on ETag and If-None-Match headers to decrease load on Doppler API (looks like Etag is already implemented) but increase the API rate limit specifically for HTTP-304 responses since they should be less expensive for Doppler than HTTP-200 reponses.
Use a functionality similar to the Webhooks to do push-based reconciliation instead of polling. For example, I would be okay with exposing the operator via an ingress so it could receive notifications from Doppler. Then the polling-based solution could be kept as a fallback with its frequency significantly decreased.

Hi, 2 questions:

I did not check the code, but is the operator bursting the API (eg.: 50 secret crds with 120 retrySeconds -> 50 requests in quick burst, then silence for the rest of 120s) or spreading the requests out somehow over the resync period? Because if it's the former, increasing resync may not help too much (unless API rate limit is credit-based and accumulates) - because then every 2 minutes the same burst would happen, no?
increasing resyncSeconds will increase the time it takes for (the very occasional) changes to be propagated, right?

Short term, I think it'd be cool if the operator had an optional Service endpoint that was capable of receiving doppler's own POST webhooks (and marking appropriate doppler secrets for resync) - the ingress and network infra setup to make it reachable from doppler doesn't need to be included in the charts/manifests, that is easy to handle internally (and the webhooks are already authenticated with HMAC I believe).


No error when logging in with the incorrect credentials.

The app does not provide any feedback when you try to login with incorrect credentials.
It seems that the 422 server response is ignored in the login form.
Encountered on commit: 80fff806980fb9876af7aac8acfd0f990d4c1107

If the credentials are wrong, the server responds with status 422 and the response is:
{"errors":{"email or password":["is invalid"]}}

This case is not part of the errorsDecoder cases in Login.elm.
I will create a quick pull request to solve the issue.

Fixed by https://github.com/rtfeldman/elm-spa-example/pull/10 - thanks!