CI: add Flake8 and Mypy checks

What isn't checked automatically isn't worth the effort.

Flake8 is being run in the pre-commit task which is part of the CI. Mypy isn't enabled until it passes.

Oh, I totally missed the pre-commit hook, I'll remove Flake8 then. If you want, I can reopen the pull request against the feature/make-mypy-happy so that you merge that one once the check passes.

The feature branch is badly outdated and probably just needs to be redone completely, unfortunately. It was also a bad attempt at fixing it.

Do you want me to give a second try at fixing all the type annotations? Also, why was it a bad attempt?

I was adding more classes to fix typing issues, @tetov did a second run in some of his own branches which was better AFAIK.


Bug: dummify drops all the columns

When having data with both numerical and categorical features, dummify seems to drop every column when refitted on data. I suspect it is because the columns do not exactly match.
This happens only when you do
dummify = tml.Dummify(drop_first=True)
dummify.fit_transform(some_data)

dummify.fit(other_data)

not when you do
dummify = tml.Dummify(drop_first=True)
dummify.fit_transform(some_data)

dummify = tml.Dummify(drop_first=True)
dummify.fit(other_data)

to test:

if drop_first is the issue
if match_cols is the issue
how the data are different
if the wrapper is the issue

In the base class, there is self.is_fit_, while the check in the Dummydf class is on self.is_fit. When calling fit the second time, match_cols is called first, but at that stage self.columns is empty and thus match_cols drops everything


Official support for multi-instance WSL

Is your feature request related to a problem? Please describe.
I'm always frustrated when I need to uninstall and re-install wsl for change development environement, because I use Windows as my daily-use and WSL as development-use
I maintain some application with some conflicts (differenet JDK version, Python 2 vs Python 3 etc...) , but those all setup on Ubuntu 1804.
Now when I want to update something on app01 (which use JDK8 and Python 2), I must uninstall current wsl (current setup with JDK 14 and Python 3)
Describe the solution you'd like
Official support for multi-instance wsl.
Describe alternatives you've considered
N/A
Additional context
Currently, I'm doing some hack on registry to archive multi-instance-wsl, but an official support for multi-instance wsl is much better.
ref: https://stackoverflow.com/questions/51584765/how-do-you-install-multiple-separate-instances-of-ubuntu-in-wsl

What's the problem with the answer in that Stackoverflow link? It already explains the import and export commands.

You can have multiple instances of the same distro installed. You can manage them from PowerShell.
You can start with a base image you have configured, --export it, then --import it under a different name and now you have two.
You can have different Ubuntu releases installed, including 18.04 or 20.04, or --import a wsl image for all the older and interim releases from http://cloud-images.ubuntu.com.
https://wiki.ubuntu.com/WSL#Ubuntu_on_WSL
https://docs.microsoft.com/en-us/windows/wsl/wsl-config#managing-multiple-linux-distributions

Hi!
I have exported a Ubuntu-18.04 guest with all the base system configuration I need
I have then imported this as a different distribution name
when I run it with
wsl --distribution Ubuntu-18.04-Project-A
It starts at the following prompt
/mnt/c/WINDOWS/system32
df -h shows
df: /proc/sys/fs/binfmt_misc: Too many levels of symbolic links
Filesystem Size Used Avail Use% Mounted on
/dev/sdd 251G 7.0G 232G 3% /
tools 1.9T 1.4T 528G 72% /init
none 2.9G 0 2.9G 0% /dev
tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup
none 2.9G 456K 2.9G 1% /run
none 2.9G 0 2.9G 0% /run/lock
none 2.9G 0 2.9G 0% /run/shm
none 2.9G 0 2.9G 0% /run/user
drivers 1.9T 1.4T 528G 72% /usr/lib/wsl/drivers
lib 1.9T 1.4T 528G 72% /usr/lib/wsl/lib
none 2.9G 0 2.9G 0% /mnt/wsl
/dev/sdc 251G 5.8G 233G 3% /mnt/wsl/docker-desktop-data/isocache
none 2.9G 12K 2.9G 1% /mnt/wsl/docker-desktop/shared-sockets/host-services
/dev/sdb 251G 122M 239G 1% /mnt/wsl/docker-desktop/docker-desktop-proxy
/dev/loop0 355M 355M 0 100% /mnt/wsl/docker-desktop/cli-tools
drvfsa 1.9T 1.4T 528G 72% /mnt/c
drvfsa 549M 34M 516M 7% /mnt/d
drvfsa 920G 484G 437G 53% /mnt/h
I am struggling to understand how further configuration of this new "Application Level VM" is kept separate from other copies of Ubuntu-18.04 and from the windows host system and from other linux system guests.
I was expecting it to be contained in a vhd file, but this does not appear to be the case!
A detailed explination would be greatly appreciated since I have a lot ridding on getting this to work with NVIDIA/CUDA/DOCKER for different projects that I want to spin up and spin down several times a day and keep as isolated from one another as much as possible.
Also is it possible to use NVIDIA in more than one container at a time or do I have to shutdown one and then start the next?

Yeah, I'm confused about the expected use of WSL? Why is there no easy  copy/delete/rename?
wsl --copy ubuntu ubuntu2
wsl --delete ubuntu2
wsl --rename ubuntu2 dev-ubuntu

Yeah, I'm confused about the expected use of WSL? Why is there no easy copy/delete/rename?
wsl --copy ubuntu ubuntu2
wsl --delete ubuntu2
wsl --rename ubuntu2 dev-ubuntu

yes, this is what I need


RFC: Improve the Scalability of TSO Service

Signed-off-by: JmPotato<EMAIL_ADDRESS>The RFC for https://github.com/tikv/pd/issues/3149.

/cc @HunDunDM @disksing @rleungx PTAL

Do you have a benchmark tool that can do micro bench on Tso performance?

Do you have a benchmark tool that can do micro bench on Tso performance?

Yes, you can use https://github.com/tikv/pd/tree/master/tools/pd-tso-bench to do the TSO benchmark.


undefined method `force_encoding' for nil:NilClass when reloading match with buffers kafka2 to forward

Describe the bug
When reloading configurations from kafka2 to the forward plugin and using persistent buffers.
The error is:
2023-04-06 13:25:47 +0000 [warn]: #0 [out_forward_tenant] got unrecoverable error in primary and no secondary error_class=NoMethodError error="undefined method `force_encoding' for nil:NilClass\n\n        tag = tag.dup.force_encoding(Encoding::UTF_8)\n                     ^^^^^^^^^^^^^^^"
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward.rb:660:in `send_data_actual'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward.rb:678:in `block in send_data'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward/connection_manager.rb:54:in `connect'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward.rb:807:in `connect'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward.rb:676:in `send_data'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward.rb:365:in `block in write'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward/load_balancer.rb:46:in `block in select_healthy_node'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward/load_balancer.rb:37:in `times'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward/load_balancer.rb:37:in `select_healthy_node'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin_helper/service_discovery/manager.rb:108:in `select_service'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin_helper/service_discovery.rb:82:in `service_discovery_select_service'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward.rb:365:in `write'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/output.rb:1180:in `try_flush'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/out_forward.rb:353:in `try_flush'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/output.rb:1501:in `flush_thread_run'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin/output.rb:501:in `block (2 levels) in start'
2023-04-06 13:25:47 +0000 [warn]: #0 /opt/td-agent/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin_helper/thread.rb:78:in `block in thread_create'
2023-04-06 13:25:47 +0000 [warn]: #0 [out_forward_store] bad chunk is moved to /tmp/fluent/backup/worker0/out_forward_store/5f8aad5016762550f1de6f57acd3211c.log

the configuration is changed from kafka2 to forward.
The logsinks are fully functional and and should flush correctly on reloading (no errors on flushing).
To Reproduce
kafka2 configuration it starts out with:
 <match kubernetes.pods.tenant-**>
  @type kafka2
  @id out_kafka_tenant
  brokers kafka01.kafka-qa.domain:9093,kafka02.kafka-qa.domain:9093,kafka03.kafka-qa.domain:9093
  ssl_ca_certs_from_system true
  default_topic "topic"
  max_send_limit_bytes 1000000
  <inject>
    tag_key "tag"
    time_key "time"
  </inject>
  <format>
    @type "json"
  </format>
  <buffer>
    @type "file"
    path "/var/lib/fluentd/buffer-tenant"
    overflow_action block
    flush_thread_count 4
    chunk_limit_size 524288
    retry_max_interval 3600
  </buffer>
</match>

reloaded to:
  <match kubernetes.pods.tenant-**>
    @type forward
    @id out_forward_applogstore_tenant
    send_timeout 120s
    connect_timeout 5s
    expire_dns_cache 60s
    ignore_network_errors_at_startup true
    recover_wait 10s
    hard_timeout 120s
    heartbeat_type none
    keepalive false
    tls_verify_hostname false
    time_as_integer false
    transport tls
    <server>
      host "host.domain"
      port 13414
      weight 90
    </server>
    <buffer>
      @type "file"
      path "/var/lib/fluentd/buffer-tenant"
      total_limit_size 512MB
      chunk_limit_size 32MB
      chunk_full_threshold 0.50
      flush_thread_count 2
      flush_at_shutdown true
      flush_mode interval
      flush_interval 30s
      overflow_action drop_oldest_chunk
      retry_max_interval 120s
    </buffer>
  </match>

Expected behavior
Changing out match should work without errors at least after they have properly flushed.
Your Environment
- Fluentd version: 1.15.3
- TD Agent version: 4.4.2-1
- Operating system: flatcar linux stable
- Kernel version: 5.15

kafka2 version 0.18.1

Your Configuration
see above

Your Error Log
see above

Additional context
The issue is also reproducable with td-agent 4.3.1-1/fluentd 1.14

@juliantaylor Could you please tell me how you reload?
Somehow the metadata of the chunk seems to be broken.
https://github.com/fluent/fluentd/blob/e89092ce1132a933c12bb23fe8c9323c07ca81f5/lib/fluent/plugin/out_forward.rb#L374-L375
https://github.com/fluent/fluentd/blob/e89092ce1132a933c12bb23fe8c9323c07ca81f5/lib/fluent/plugin/out_forward.rb#L660

reload is done by calling api/config.reload

Thanks.
Isn't it possible that out_forward got an error trying to process the buffer file of out_kafka2 remaining?
api/config.reload seems not to flush file buffers.

https://docs.fluentd.org/deployment/rpc#http-endpoints
https://docs.fluentd.org/deployment/signals#sighup

so buffers are not supposed to be compatible between different plugins?
mentioning that on the reload documentation would be good.

I don't think there is any mention of it being compatible or not compatible.
So I think it is natural to assume that compatibility is not guaranteed.
In this case, the remained data wil not be sent in the correct format (MessagePack) since it is formatted as JSON in the previous setting.
  <format>
    @type "json"
  </format>

However, I am concerned about how the error appears.
I will look into this a bit.

For now, I suggest setting flush_at_shutdown true and stopping Fluentd once to clear the buffer.

Or use the different buffer path.

ah yes flush_at_shutdown was what I was missing to have a clean switch path, thanks Ill try that and if thats not enough a second path should works fine.

Sorry for the delay.

I don't think there is any mention of it being compatible or not compatible. So I think it is natural to assume that compatibility is not guaranteed.
In this case, the remained data wil not be sent in the correct format (MessagePack) since it is formatted as JSON in the previous setting.
  <format>
    @type "json"
  </format>

However, I am concerned about how the error appears. I will look into this a bit.

I have checked this.
As expected, data stored in JSON format will be corrupted as out_forward tries to read it as MessagePack format.
However, the error message says tag data is nil.
That is strange because it is kept as metadata in a consistent format separate from the record data itself.
I could not find the cause of this error.
Anyway, it is for sure not possible to share the buffer with different pluings.
So please try the followings.

using the different buffer path.

setting flush_at_shutdown true and stopping Fluentd once to clear the buffer.

If you have any more problems, please reopen this.


Fix regression in assume role caching

This pulls in https://github.com/boto/botocore/pull/961 and adds tests for the change.
Right now you get an error:
$ aws ec2 describe-instances --profile some-role
Value cannot be cached, must be JSON serializable: {u'AssumedRole...

This was from a recent addition to botocore that added the HTTP headers into the response metadata returned from client calls.
I agree with the original change from @bashtoni to fix this in the parser.  We've had an implicit contract that you can JSON dump response metadata so while we could fix this in the assume role cacher, it's possible customer code could be relying on this property, in which case we would not be able to fix.
cc @kyleknap @JordonPhillips

[Current coverage][cc-pull] is 97.31%

Merging [#962][cc-pull] into [develop][cc-base-branch] will not change coverage

@@            develop       #962   diff @@
==========================================
  Files            43         43
  Lines          7014       7014
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           6826       6826
  Misses          188        188
  Partials          0          0

Powered by Codecov. Last updated by [fac5529...2f151ae][cc-compare]
[cc-base-branch]: https://codecov.io/gh/boto/botocore/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/boto/botocore/compare/fac55296d06b840155bc90b3499a2cda1d5bad09...2f151ae9d52d5f48e7a0213aa7313024c20ee029
[cc-pull]: https://codecov.io/gh/boto/botocore/pull/962?src=pr

--    .-""-.
   ) (     )
  (   )   (
     /     )
    (_    _)                     0_,-.__
      (_  )_                     |_.-._/
       (    )                    |_--..\
        (__)                     |__--_/
     |''   ``\                   |
     |        \                  |      /b.
     |         \  ,,,---===?A`\  |  ,==y'
   ___,,,,,---==""\        |M] \ | ;|\ |>
           _   _   \   ___,|H,,---==""""bno,
    o  O  (_) (_)   \ /          _     AWAW/
                     /         _(+)_  dMM/
      \@_,,,,,,---=="   \      \\|//  MW/
--''''"                         ===  d/
                                    //
                                    ,'__________________________
   \    \    \     \               ,/~~~~~~~~~~~~~~~~~~~~~~~~~~~
                         _____    ,'  ~~~   .-""-.~~~~~~  .-""-.
      .-""-.           ///==---   /`-._ ..-'      -.__..-'
            `-.__..-' =====\\\\\\ V/  .---\.
                      ~~~~~~~~~~~~, _',--/_.\  .-""-.
                            .-""-.___` --  \|         -.__..-

:ship:


feat: support ubuntu 22.04 lts (jammy)

#361

Build now locally works. will revert the branch ci change when this build is done.


Added missing space

A space is missing between "he" and "she".

Hi Jim,
This typo is now corrected.
Thanks!
Maite
From: Jim Liu @.>
Sent: Wednesday, March 24, 2021 9:12 AM
To: MicrosoftDocs/microsoft-style-guide @.>
Cc: Subscribed @.***>
Subject: [MicrosoftDocs/microsoft-style-guide] Added missing space (#219)
A space is missing between "he" and "she".

You can view, comment on, or merge this pull request online at:
https://github.com/MicrosoftDocs/microsoft-style-guide/pull/219https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fpull%2F219&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137856965|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=hd4DKN%2BpivZOswfLNirZDAptiReiKiR2R6RP%2Beha86w%3D&reserved=0
Commit Summary

Added missing space

File Changes

M styleguide/grammar/nouns-pronouns.mdhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fpull%2F219%2Ffiles%23diff-7bcd8fd4f8d61b78586ff29deddefb44dd3406ba32a5ca07e80a491b79045f5a&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137856965|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=7DL2gQTa4n%2BsSMSt6MN2rdl%2BEUKIkAA1wZY58sYP%2FUE%3D&reserved=0 (2)

Patch Links:

https://github.com/MicrosoftDocs/microsoft-style-guide/pull/219.patchhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fpull%2F219.patch&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137866930|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=tmTaEwo78456cfOTz7eK%2BntTN3kNWAbgqSW%2FBMMu6Uk%3D&reserved=0
https://github.com/MicrosoftDocs/microsoft-style-guide/pull/219.diffhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fpull%2F219.diff&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137866930|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dbNgyQf1ntkK%2B4vfoc9wbEb09cTLZCVo8IbznHHZ0gs%3D&reserved=0

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fpull%2F219&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137876883|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=qHDGfJ31m8tdAP%2B87w1melRD5KqsCPImI25u21ux2pU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASXUAR27RF5ZPCA6Y3KII3TTFGNEHANCNFSM4ZWX2BFA&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137876883|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=O%2B3XFkkuuA0KuPwa2Z1DB2wKYUXvAK8%2Fad8QYG%2F76eE%3D&reserved=0.


youtube

https://python.langchain.com/docs/integrations/document_loaders/youtube_audio
https://python.langchain.com/docs/integrations/tools/youtube

Youtube works fine for me, including on gpt.h2o.ai etc.  I can close this issue.  Thanks for PR, will look!

@cherrerajobs If youtube ingestion doesn't work, feel free to make a bug issue.  Note that it does take about 1s per 10s of video with whisper large v3.  One can use distil whisper v2 for much faster and reasonable behavior.

@cherrerajobs I noticed some issue with numpy version that breaks librosa/soundfile due to TTS pinning old numpy.  I changed linux_install.sh .
You can fix by doing:
pip install numpy==1.23.0 --no-deps --upgrade


Azure Servicebus Topics support

To suggest an idea or inquire about a new Message Broker supporting feature or any other enhancement, please follow this template:
Is your feature request related to a problem? Please describe.
Provide a clear and concise description of the problem you've encountered. For example: "I'm always frustrated when..."
Backend I'm working on is deployed to Azure. We use FastAPI extensively and often our endpoints are dispatching messages to various Azure Service Bus queues and topics. We would like to adapt FastStream in our backend, because it has nice and simple API and docs generation, but Azure SB is the only thing we use and without broker/connector for that we're stuck with Azure SDK and our own layers for more simpler API.
Describe the solution you'd like
Add Azure Service Bus broker as a subscriber and publisher.
Feature code example
To help others understand the proposed feature, illustrate it with a FastStream code example:
from faststream import FastStream
from faststream.azure import AzureServiceBusBroker

broker = AzureServiceBusBroker("sb://path.to.azure")

@broker.subscriber("in")
@broker.publisher("out")
async def handle_msg(data: User) -> str:
    return f"User: {data.user} - {data.user_id} registered"

...

Describe alternatives you've considered
Use SB SDK and hope that actual events are in sync with written documentation.
Additional context
I know that Azure Service Bus SDK was using uamqp lib under the hood and now they changed that their own implementation of pyamqp (turns out there are at least 3 implementations under this name). This could imply that sb protocol is somewhat similar to amqp, but I'm not sure.
This is kind of interesting project and topic to me and would love to learn more about it from you guys.
In the future this may extend to Event Grid or Event Hub - those I'm not familiar with.

Thanks for you feature request! Unfortunatelly, Redis and SQS is a prior tasks for now, cuz they are widely used, but sure, we'll add the Azure SB support in a few months (I hope so). You can help us by share links on Azure SB and SDK you are using to help deep into details.

@macieyng

In the future this may extend to Event Grid or Event Hub

Implementation with Azure Event Hub is already possible by using the Kafkabroker with Eventhub :-)
However, I would also love to see an Azure Service Bus implementation. I am using the Kafkabroker on Eventhub for now, but it does not fit all our use cases perfectly. I can see that SQS is a prio, but just wanted to leave my support for this feature request here, thank you very much!

Grid + Bus would sure be nice.


Issue

Issue without proper information won't be answered
Expected Behavior
I want bot to START
Actual Behavior
$-MacBook-Pro:pokemongo-bot$ ./run.sh
Traceback (most recent call last):
File "pokecli.py", line 41, in
from pokemongo_bot import PokemonGoBot, TreeConfigBuilder
File "/Users/$/PokemonGo-Bot/pokemongo_bot/init.py", line 19, in
import cell_workers
File "/Users/$/PokemonGo-Bot/pokemongo_bot/cell_workers/init.py", line 3, in
from catch_lured_pokemon import CatchLuredPokemon
File "/Users/$/PokemonGo-Bot/pokemongo_bot/cell_workers/catch_lured_pokemon.py", line 8, in
from pokemongo_bot.cell_workers.pokemon_catch_worker import PokemonCatchWorker
File "/Users/$/PokemonGo-Bot/pokemongo_bot/cell_workers/pokemon_catch_worker.py", line 306
<<<<<<< HEAD
^
SyntaxError: invalid syntax
Thu Aug 11 18:18:10 PDT 2016 Pokebot Stopped.
Press any button or wait 20 seconds to continue.
Steps to Reproduce
./run.sh
Information
OS Yosemite 10.10.5
Git commit ( to get git commit run git log -1 --format="%H")
Python V: Python 2.7.10

Wow, bad merge
I don't want to be that guy, but the one vital piece of information that would have been able to help us help you is the Information -> Git commit section that you omitted. If you could provide this info, and what branch you're on, we can sort this out relatively quickly.

Sorry how do i find this?

**
Git commit ( to get git commit run git log -1 --format="%H")
**

b8af467f8e694adf3e2353876e27159d4f16daee

Ok well no one else is reporting this issue, so it doesn't look like a bad commit
Have you made changes to PokemonGo-Bot/pokemongo_bot/cell_workers/pokemon_catch_worker.py ? If not can you open the file and scroll to line 306 and see if you can see <<<<<<< HEAD anywhere around there

Hi,
i have the same issue today... And yes, it is <<<<<<< HEAD in line 306

Hmmmm the plot thickens.....
@lifesound7 what commit are you on? is it the same as @thorowwasdf ? also can you post your details, ie OS, branch, commit etc

OS: OS X El capitan
Git Commit: 44d7b39
Python Version: Python 2.7.10
I guess an issue was with bot files, because It works after I have deleted files and reinstalled.

@thorowwasdf can you try the same please, that was my next step before @lifesound7 said they had the same issue. Can you try a fresh install (remember to keep your config)

It looks like it is not completed git merge.
Try:
git reset --hard
git pull origin dev

Or if you use master branch replace dev to master in the second line.

@ogalababa - https://github.com/PokemonGoF/PokemonGo-Bot/issues/3679#issuecomment-239498095

@cmezh  thanks for the tip but it didnt work

@thorowwasdf As this is not a bot issue, i'm going to close this issue. I'd suggest (like before) a fresh install (remember to keep your config)


Verify that debuggers are reset after TDML tests are run

Current behavior in Daffodil is to automatically disable debugging after a call to runOneTest, which helps to avoid errors where enabling debugging in one test might cause failures in another test.
This updates a test to use the latest TDML API and confirm that this behavior actually happens. Note that the schema that originally found the issue with long-lived debugger state is no longer valid in Daffodil, so it needed some tweaks. This also simplifies the custom debugger to avoid storing strings that are never needed.
DAFFODIL-790

Do I understand that the InteractiveDebugger class here does not mean that you interact with a live interactive debugger command line, rather, it lets you supply a callback "listener" class which can trace parts of Daffodil execution and print or accumulate data to help you debug a problem?

Yep. There's a number of commands that the interactive debugger understands (e.g. "break", "step", "continue", "eval"). The "listener" or "debugger runner" is what provides the commands to run and receives the results to display. The name "interactive" is probably not the best since it really doesn't need to have user interaction at all (e.g the TraceDebuggerRunner just uses a list of predetermined commands). But I think it originally did require user input, but was eventually generalized and the name stuck.


Docs link in navbar dropdowns are completely broken

🐛 Bug Report
Prerequisites

[x] I'm using the latest version of Docusaurus.
[ ] I have tried the npm run clear or yarn clear command.
[ ] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[x] I have tried creating a repro with https://new.docusaurus.io
[x] I have read the console error message carefully (if applicable)

Note: This was done on a completely new project so rest are non-applicable
Description
Docs link in navbar dropdowns don't work at all.
Have you read the Contributing Guidelines on issues?
Yes.
Steps to reproduce
Use https://new.docusaurus.io to create a CodeSandbox reproducible demo of the bug.
(Write your steps here:)

Create a new site with classic template, following these steps
Update the themeConfig as follows:

    themeConfig: {
      items: [
        {
          position: 'left',
          label: 'Docs',
          items: [
            {
              type: 'doc',
              docId: 'intro',
              label: 'Tutorial',
            }
          ]
        },
        {
          type: 'doc',
          docId: 'intro',
          label: 'Tutorial',
        },
        // ...
    },
    // ...
  },

Notice how the top-level navbar link works but the dropdown one doesn't

Expected behavior

Navigate properly
No errors in conole

Actual behavior

It does not navigate to the docs page.
Screenshot:

Error from console
Warning: React does not recognize the `docId` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `docid` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
a
Link@webpack-internal:///./node_modules/@docusaurus/core/lib/client/exports/Link.js:24:73
NavLink@webpack-internal:///./node_modules/@docusaurus/theme-classic/lib-next/theme/NavbarItem/DefaultNavbarItem.js:19:75
li
ul
div
NavItemDesktop@webpack-internal:///./node_modules/@docusaurus/theme-classic/lib-next/theme/NavbarItem/DefaultNavbarItem.js:21:1287
DefaultNavbarItem@webpack-internal:///./node_modules/@docusaurus/theme-classic/lib-next/theme/NavbarItem/DefaultNavbarItem.js:22:2366
NavbarItem@webpack-internal:///./node_modules/@docusaurus/theme-classic/lib-next/theme/NavbarItem/index.js:19:363
div
div
nav
Navbar@webpack-internal:///./node_modules/@docusaurus/theme-classic/lib-next/theme/Navbar/index.js:27:423
DocsPreferredVersionContextProviderUnsafe@webpack-internal:///./node_modules/@docusaurus/theme-common/lib/utils/docsPreferredVersion/DocsPreferredVersionProvider.js:26:875
DocsPreferredVersionContextProvider@webpack-internal:///./node_modules/@docusaurus/theme-common/lib/utils/docsPreferredVersion/DocsPreferredVersionProvider.js:26:488
UserPreferencesProvider@webpack-internal:///./node_modules/@docusaurus/theme-classic/lib-next/theme/UserPreferencesProvider/index.js:13:157
AnnouncementBarProvider@webpack-internal:///./node_modules/@docusaurus/theme-common/lib/utils/announcementBarUtils.js:21:483
ThemeProvider@webpack-internal:///./node_modules/@docusaurus/theme-classic/lib-next/theme/ThemeProvider/index.js:13:142
LayoutProviders@webpack-internal:///./node_modules/@docusaurus/theme-classic/lib-next/theme/LayoutProviders/index.js:14:28
Layout@webpack-internal:///./node_modules/@docusaurus/theme-classic/lib-next/theme/Layout/index.js:21:83
Home@webpack-internal:///./src/pages/index.tsx:12:1142
LoadableComponent@webpack-internal:///./node_modules/@docusaurus/react-loadable/lib/index.js:1:2843
Route@webpack-internal:///./node_modules/react-router/esm/react-router.js:464:29
Switch@webpack-internal:///./node_modules/react-router/esm/react-router.js:670:29
Route@webpack-internal:///./node_modules/react-router/esm/react-router.js:464:29
PendingNavigation@webpack-internal:///./node_modules/@docusaurus/core/lib/client/PendingNavigation.js:18:180
C@webpack-internal:///./node_modules/react-router/esm/react-router.js:725:31
Root@webpack-internal:///./node_modules/@docusaurus/core/lib/client/theme-fallback/Root/index.js:18:14
App@webpack-internal:///./node_modules/@docusaurus/core/lib/client/App.js:23:94
Router@webpack-internal:///./node_modules/react-router/esm/react-router.js:93:30
BrowserRouter@webpack-internal:///./node_modules/react-router-dom/esm/react-router-dom.js:59:35 index.js:1

Your environment

Docusaurus version used: 2.0.0-beta.2 (from package.json)
Environment name and version: Firefox 89.0.1, Node.js: v14.17.0
Operating system and version: Arch Linux

Reproducible demo
https://codesandbox.io/s/gifted-tree-tpiv3

Exact docusaurus.config.js, after updates (rest is same as classic template)
const lightCodeTheme = require('prism-react-renderer/themes/github');
const darkCodeTheme = require('prism-react-renderer/themes/dracula');

/** @type {import('@docusaurus/types').DocusaurusConfig} */
module.exports = {
  title: 'My Site',
  tagline: 'Dinosaurs are cool',
  url: 'https://your-docusaurus-test-site.com',
  baseUrl: '/',
  onBrokenLinks: 'throw',
  onBrokenMarkdownLinks: 'warn',
  favicon: 'img/favicon.ico',
  organizationName: 'facebook', // Usually your GitHub org/user name.
  projectName: 'docusaurus', // Usually your repo name.
  themeConfig: {
    navbar: {
      title: 'My Site',
      logo: {
        alt: 'My Site Logo',
        src: 'img/logo.svg',
      },
      items: [
        {
          position: 'left',
          label: 'Docs',
          items: [
            {
              type: 'doc',
              docId: 'intro',
              label: 'Tutorial',
            }
          ]
        },
        {
          type: 'doc',
          docId: 'intro',
          label: 'Tutorial',
        },
        {to: '/blog', label: 'Blog', position: 'left'},
        {
          href: 'https://github.com/facebook/docusaurus',
          label: 'GitHub',
          position: 'right',
        },
      ],
    },
    footer: {
      style: 'dark',
      links: [
        {
          title: 'Docs',
          items: [
            {
              label: 'Tutorial',
              to: '/docs/intro',
            },
          ],
        },
        {
          title: 'Community',
          items: [
            {
              label: 'Stack Overflow',
              href: 'https://stackoverflow.com/questions/tagged/docusaurus',
            },
            {
              label: 'Discord',
              href: 'https://discordapp.com/invite/docusaurus',
            },
            {
              label: 'Twitter',
              href: 'https://twitter.com/docusaurus',
            },
          ],
        },
        {
          title: 'More',
          items: [
            {
              label: 'Blog',
              to: '/blog',
            },
            {
              label: 'GitHub',
              href: 'https://github.com/facebook/docusaurus',
            },
          ],
        },
      ],
      copyright: `Copyright © ${new Date().getFullYear()} My Project, Inc. Built with Docusaurus.`,
    },
    prism: {
      theme: lightCodeTheme,
      darkTheme: darkCodeTheme,
    },
  },
  presets: [
    [
      '@docusaurus/preset-classic',
      {
        docs: {
          sidebarPath: require.resolve('./sidebars.js'),
          // Please change this to your repo.
          editUrl:
            'https://github.com/facebook/docusaurus/edit/master/website/',
        },
        blog: {
          showReadingTime: true,
          // Please change this to your repo.
          editUrl:
            'https://github.com/facebook/docusaurus/edit/master/website/blog/',
        },
        theme: {
          customCss: require.resolve('./src/css/custom.css'),
        },
      },
    ],
  ],
};

Additional Context
Discord Discussion: https://discord.com/channels/398180168688074762/398180168688074765/858716139394826240

The cause is this:
https://github.com/facebook/docusaurus/blob/3fe7389ee2989dca713d20a82bc26f7e91254377/packages/docusaurus-theme-classic/src/theme/NavbarItem/DefaultNavbarItem.tsx#L135-L159
I think the Navbar dropdown should always treat its child items as NavbarItem recursively.
I'd like to take this issue since I've been recently working on a refactor of the NavbarItem codebase by making them more elegantly polymorphic 👀

items: [
            {
              type: 'doc',
              docId: 'intro',
              label: 'Tutorial',
            }
          ]

We don't support type doc inside a navbar dropdown yet.
Closing: duplicate of feature request https://github.com/facebook/docusaurus/issues/4996

The Navbar dropdown treats the child items as NavLink instead of as NavbarItem recursively.

@Josh-Cena I'd be happy to improve but keep in mind that showing a dropdown inside a dropdown does not really make sense: only "simple items" should be nested.
Our current validation is not very good regarding navbar item elements, would like to improve that


Global MS gate in circuit library

just creates a new entry under generalized_gates. does not deprecate old one yet.

@jaygambetta citations, equation and test added. I called it GMS (global molmer sorensen) after ref [2].


setup timezones('Asia/Tokyo', 'America/New_York', 'Europe/London'

This pull request enhances the end-to-end tests for the learn.microsoft.com Update Checker by adding support for testing across multiple timezones. The changes include updating the test descriptions, adding a list of timezones, and ensuring the tests run in each timezone.
Enhancements to timezone testing:

tests/e2e/content.e2e.test.js: Added a list of timezones (timezones) and modified the test cases to loop through each timezone, emulating it during the tests. [1] [2] [3] [4] [5]

ref #21


Correctly bind Touchable.js setTimeout

Fixes https://github.com/facebook/react-native/issues/5337
this.setTimeout is undefined and the scope wasn't being passed through causing a RedBox error.

thanks

@facebook-github-bot shipit

This should use this.setTimeout still, don't you think @ide? The rest is fine but not sure why this.setTimeout was changed to setTimeout

@brentvatne you're right. this.setTimeout please

this.setTimeout was undefined. That was the initial error I was getting,
then once I changed it the next error was the scope not being passed into
the function.
On 19 Jan 2016 7:08 a.m., "James Ide"<EMAIL_ADDRESS>wrote:

@brentvatne https://github.com/brentvatne you're right. this.setTimeout
please
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/pull/5376#issuecomment-172760416
.

Good point, it seems like there was some coupling introduced here between TimerMixin and TouchableMixin at some point, and this PR removes that. Timeout is properly cleared in componentWillUnmount so this looks good to me. Thanks!

@facebook-github-bot shipit


我常驻池有两个金，但是说我只有一个金

Can you please report the issue in English? Some contributors cannot speak Chinese, so we appreciate it if you could. :)

Sorry cannot see the screenshot

He said he got two 5-stars in standard wish, but only one appeared in wish counter.


Invalid field name(s) for model CustomUser: 'username'  while trying to pull new  data from stripe

Invalid field name(s) for model CustomUser: 'username'

python manage.py update_stripe_customers

Updated Stripe Customer cus_LSr9w7FB2J7r9U
Updated Stripe Customer cus_LSN6YXRJULxYv2
Updated Stripe Customer cus_LSLsozLd7PpiAJ
Updated Stripe Customer cus_LSLoxRY2x62iqT
Updated Stripe Customer cus_LSBn1ocYarYb8I
Updated Stripe Customer cus_LSBMjVw45wQLc9
Updated Stripe Customer cus_LS8UsIDLMRgQL9
Traceback (most recent call last):
File "C:\backend\env\lib\site-packages\django\db\models\query.py", line 581, in get_or_create
return self.get(**kwargs), False
File "C:\backend\env\lib\site-packages\django\db\models\query.py", line 435, in get
raise self.model.DoesNotExist(
accounts.models.CustomUser.DoesNotExist: CustomUser matching query does not exist.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\backend\mrbackend\manage.py", line 22, in
main()
File "C:\backend\mrbackend\manage.py", line 18, in main
execute_from_command_line(sys.argv)
File "C:\backend\env\lib\site-packages\django\core\management_init_.py", line 419, in execute_from_command_line
utility.execute()
File "C:\backend\env\lib\site-packages\django\core\management_init_.py", line 413, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "C:\backend\env\lib\site-packages\django\core\management\base.py", line 354, in run_from_argv
self.execute(*args, **cmd_options)
File "C:\backend\env\lib\site-packages\django\core\management\base.py", line 398, in execute
output = self.handle(*args, **options)
File "C:\backend\env\lib\site-packages\drf_stripe\management\commands\update_stripe_customers.py", line 14, in handle
stripe_api_update_customers(limit=kwargs.get('limit'), starting_after=kwargs.get('starting_after'))
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.3312.0_x64__qbz5n2kfra8p0\lib\contextlib.py", line 79, in inner
return func(*args, **kwds)
File "C:\backend\env\lib\site-packages\drf_stripe\stripe_api\customers.py", line 159, in stripe_api_update_customers
user, user_created = get_user_model().objects.get_or_create(
File "C:\backend\env\lib\site-packages\django\db\models\manager.py", line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "C:\backend\env\lib\site-packages\django\db\models\query.py", line 583, in get_or_create
params = self._extract_model_params(defaults, **kwargs)
File "C:\backend\env\lib\site-packages\django\db\models\query.py", line 634, in _extract_model_params
raise exceptions.FieldError(
django.core.exceptions.FieldError: Invalid field name(s) for model CustomUser: 'username'.
my customuser model:
class CustomUser(AbstractUser):
username = None
email = models.EmailField(_('email address'), unique=True)
bio = models.TextField()
gender = models.CharField(
max_length=140,
null=True,
choices=(
('Male', 'Male'),
('Female', 'Female'),
('Other', 'Other')
)
)
birth_date = models.DateField(null=True, blank=True)
id = models.UUIDField(primary_key=True, default=uuid.uuid4, editable=False)
Please help me resolve the issue.ASAP

Are you using a customized user model with different model attributes?

yes...heere is my custom model
class CustomUser(AbstractUser):
"""
A User model that uses email as it's default identifier instead of
username.
"""
class Types(models.TextChoices):
CANDIDATE = "CANDIDATE", "Candidate"
EMPLOYER = "EMPLOYER", "Employer"
base_type = Types.CANDIDATE
type = models.CharField(
    _("Type"), max_length=50, choices=Types.choices, default=base_type
)

username=None # THIS CODE IS GIVING ISSUE
email = models.EmailField(_('email address'), unique=True)
bio = models.TextField()
gender = models.CharField(
max_length=140,
null=True,
choices=(
('Male', 'Male'),
('Female', 'Female'),
('Other', 'Other')
)
)
birth_date = models.DateField(null=True, blank=True)
id = models.UUIDField(primary_key=True, default=uuid.uuid4, editable=
False)
USERNAME_FIELD = 'email'
REQUIRED_FIELDS = []

objects = managers.CustomUserManager()

def __str__(self):
    return self.email

class CandidateManager(models.Manager):
def get_queryset(self, *args, **kwargs):
return super().get_queryset(*args, **kwargs).filter(type=CustomUser.
Types.CANDIDATE)
class EmployerManager(models.Manager):
def get_queryset(self, *args, **kwargs):
return super().get_queryset(*args, **kwargs).filter(type=CustomUser.
Types.EMPLOYER)
class Candidate(CustomUser):
base_type = CustomUser.Types.CANDIDATE
objects = CandidateManager()
class Meta:
    proxy = True

class Employer(CustomUser):
base_type = CustomUser.Types.EMPLOYER
objects = EmployerManager()
On Thu, 7 Apr 2022 at 19:29, Oscar Y Chen @.***> wrote:

Are you using a customized user model with different model attributes?
—
Reply to this email directly, view it on GitHub
https://github.com/oscarychen/drf-stripe-subscription/issues/18#issuecomment-1091775380,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBYTATQ4OBQEMDL6XVO4GLVD3S4PANCNFSM5SZNZM6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Please  let me know the solution.I need it asap please.
On Thu, 7 Apr 2022 at 21:51, Anirban Chakraborty <
@.***> wrote:

yes...heere is my custom model
class CustomUser(AbstractUser):
"""
A User model that uses email as it's default identifier instead of
username.
"""
class Types(models.TextChoices):
CANDIDATE = "CANDIDATE", "Candidate"
EMPLOYER = "EMPLOYER", "Employer"
base_type = Types.CANDIDATE
type = models.CharField(
    _("Type"), max_length=50, choices=Types.choices, default=base_type
)

username=None # THIS CODE IS GIVING ISSUE
email = models.EmailField(_('email address'), unique=True)
bio = models.TextField()
gender = models.CharField(
max_length=140,
null=True,
choices=(
('Male', 'Male'),
('Female', 'Female'),
('Other', 'Other')
)
)
birth_date = models.DateField(null=True, blank=True)
id = models.UUIDField(primary_key=True, default=uuid.uuid4, editable=
False)
USERNAME_FIELD = 'email'
REQUIRED_FIELDS = []

objects = managers.CustomUserManager()

def __str__(self):
    return self.email

class CandidateManager(models.Manager):
def get_queryset(self, *args, **kwargs):
return super().get_queryset(*args, **kwargs).filter(type=
CustomUser.Types.CANDIDATE)
class EmployerManager(models.Manager):
def get_queryset(self, *args, **kwargs):
return super().get_queryset(*args, **kwargs).filter(type=
CustomUser.Types.EMPLOYER)
class Candidate(CustomUser):
base_type = CustomUser.Types.CANDIDATE
objects = CandidateManager()
class Meta:
    proxy = True

class Employer(CustomUser):
base_type = CustomUser.Types.EMPLOYER
objects = EmployerManager()
On Thu, 7 Apr 2022 at 19:29, Oscar Y Chen @.***>
wrote:

Are you using a customized user model with different model attributes?
—
Reply to this email directly, view it on GitHub
https://github.com/oscarychen/drf-stripe-subscription/issues/18#issuecomment-1091775380,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBYTATQ4OBQEMDL6XVO4GLVD3S4PANCNFSM5SZNZM6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

@anirbanchakraborty123 V1.1.11 added support for custom Django User, it should work for your use case.

Hey Oscar, First of  all Thank you for the wonderful library, Secondly, Can
you please do it as early as possible because I need to launch it live
before the weekend.Otherwise client will get frustrated.
Thank you.
On Thu, 7 Apr 2022 at 22:53, Oscar Y Chen @.***> wrote:

Can you wait till the weekend?
I need to add a setting so that you can specify a custom field to use to
reference the user model instead of the default username, in which case you
can use email or another field.
—
Reply to this email directly, view it on GitHub
https://github.com/oscarychen/drf-stripe-subscription/issues/18#issuecomment-1092004572,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBYTATLFNRIQFDHWLB3SN3VD4KXTANCNFSM5SZNZM6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

@anirbanchakraborty123 is this not it? https://github.com/oscarychen/drf-stripe-subscription/releases/tag/1.1.11


etcdserver: prevExist=true + condition is compareAndSwap

PrevExist indicates the key should exist. Condition compares with
an existing key. So PrevExist+condition = CompareAndSwap not Update.

/cc @yichengq @barakmich

lgtm


WIP:💄(layout) improve styling images and CKEditor usage

Purpose
Some configuration is missing to allow controlling the positioning
of images and image element (img and figure) behaviors are not
correct.
Related to issue #567
Proposal
Here we add some basic image element styles so image have correct
basic behaviors on its alignments and with its container. Also we
disable some useless CKEditor features and fixed alignment buttons.

@sampaccoud this is not ready yet since for CKEditor button alignment fix i need to add a CSS file (dedicated to CKEditor in its iframe):
/*
CSS for CKEditor content
*/

/*
 * Add alignment classes required for alignment buttons to work right according
 * to CKEditor configuration option "justifyClasses" */
.text-left {
  text-align: left;
}

.text-right {
  text-align: right;
}

.text-center {
  text-align: center;
}

But CSS file are ignored from GIT, so it have to be a Sass file to build but so we need to modify sass action from richie/frontend/package.json since it is configured to build _main.scss only.

Image elements behaviors sample
With this structure

Get this render


[23.11] ansible_2_15: 2.15.5 -> 2.15.9

Description of changes
Fixes CVE-2023-5764.
https://github.com/ansible/ansible/blob/v2.15.9/changelogs/CHANGELOG-v2.15.rst

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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 287886 run on x86_64-linux 1

38 packages built:

ansible (python311Packages.ansible-core)
ansible-later
ansible-later.dist
ansible-lint
ansible-lint.dist
ansible.dist (python311Packages.ansible-core.dist)
kargo
kargo.dist
molecule (python311Packages.molecule)
molecule.dist (python311Packages.molecule.dist)
python310Packages.ansible-compat
python310Packages.ansible-compat.dist
python310Packages.ansible-core
python310Packages.ansible-core.dist
python310Packages.ansible-kernel
python310Packages.ansible-kernel.dist
python310Packages.ansible-runner
python310Packages.ansible-runner.dist
python310Packages.ansible-vault-rw
python310Packages.ansible-vault-rw.dist
python310Packages.molecule
python310Packages.molecule.dist
python310Packages.pytest-ansible
python310Packages.pytest-ansible.dist
python310Packages.pytest-testinfra
python310Packages.pytest-testinfra.dist
python311Packages.ansible-compat
python311Packages.ansible-compat.dist
python311Packages.ansible-kernel
python311Packages.ansible-kernel.dist
python311Packages.ansible-runner
python311Packages.ansible-runner.dist
python311Packages.ansible-vault-rw
python311Packages.ansible-vault-rw.dist
python311Packages.pytest-ansible
python311Packages.pytest-ansible.dist
python311Packages.pytest-testinfra
python311Packages.pytest-testinfra.dist

<!--
To help with the large amounts of pull requests, we would appreciate your
reviews of other pull requests, especially simple package updates. Just leave a
comment describing what you have tested in the relevant package/service.
Reviewing helps to reduce the average time-to-merge for everyone.
Thanks a lot if you do!
<p>List of open PRs: https://github.com/NixOS/nixpkgs/pulls
Reviewing guidelines: https://nixos.org/manual/nixpkgs/unstable/#chap-reviewing-contributions
-->

Add a :+1: reaction to pull requests you find important.

Why not git cherry-pick -x?

On master ansible_2_15 is defined in all-packages.nix, cherry picking it would have required to deal with the conflict resolution to end up with a change that is entirely managed manually like I did here. Also ansible_2_15 is the default ansible on 23.11, it is not the case on master, more things are likely to be impacted by the bump.
I can still add the cherry pick info if you feel it would be best.


add mobilenetv2 pretrained models

Description
Add mobilenetv2 pretrained models
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[X] Changes are complete (i.e. I finished coding on this PR)
[X] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Thanks, @hetong007 it's really useful :)


⚠ Bofrost.be has degraded performance

In bc651fd, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1451 ms

Resolved: Bofrost.be performance has improved in 2882efc.


tests: perf: perf script exits with 242

Flaky failure. See https://github.com/Granulate/gprofiler/actions/runs/3143140870/jobs/5107875745.
gprofiler.exceptions.CalledProcessError: Command \'[\'/tmp/_MEIr5GIYw/gprofiler/resources/perf\', \'script\', \'-F\', \'+pid\', \'-i\', \'/tmp/gprofiler_tmp/tmpjf1r20_b/perf.dwarf.2022092811554505\']\' returned non-zero exit status 242. \nstdout: ...

This is stderr:
b\'addr2line_init failed for /usr/lib/x86_64-linux-gnu/libc-2.31.so\\naddr2line_init failed for /usr/lib/x86_64-linux-gnu/libc-2.31.so\\naddr2line_init failed for /usr/lib/x86_64-linux-gnu/libc-2.31.so\\naddr2line_init failed for /usr/lib/x86_64-linux-gnu/libc-2.31.so\\naddr2line_init failed for /usr/lib/x86_64-linux-gnu/libc-2.31.so\\naddr2line_init failed for /usr/lib/x86_64-linux-gnu/libc-2.31.so\\naddr2line_init failed for /usr/lib/x86_64-linux-gnu/libc-2.31.so\\naddr2line_init failed for /usr/lib/x86_64-linux-gnu/libc-2.31.so\\naddr2line_init failed for /usr/lib/x86_64-linux-gnu/libc-2.31.so\\naddr2line_init failed for /usr/lib/x86_64-linux-gnu/libc-2.31.so\\naddr2line_init failed for /usr/lib/x86_64-linux-gnu/libpthread-2.31.so\\n0x7f5e38 [0x78]: failed to process type: 17 [Bad address]\\n\'\n'

Saw this is real deployments: stderr: b'0x209018 [0x80]: failed to process type: 17 [Bad address]\n'. Possibly a perf bug? We'll need to look into it.

This is the relevant code
		pr_err("%#" PRIx64 " [%#x]: failed to process type: %d [%s]\n",
		       file_offset + head, event->header.size,
		       event->header.type, strerror(-skip));

in reader__process_events.


tf.contrib.data: tf-slim training pipeline gets stuck

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux leto28 3.16.0-4-amd64 1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
VERSION_ID="8"
VERSION="8 (jessie)"

TensorFlow installed from (source or binary):
Binary

TensorFlow version (use command below):
tf.VERSION = 1.2.0-rc2
tf.GIT_VERSION = v1.2.0-rc1-24-gce1d6ec
tf.COMPILER_VERSION = v1.2.0-rc1-24-gce1d6ec

Bazel version (if compiling from source):
None

CUDA/cuDNN version:
8.0/5.1

GPU model and memory:
TITAN X (Pascal), 12189MiB

Exact command to reproduce:
python ./mwe.py

Describe the problem
I recently ported my dataset handling to the new dataset API from tf.contrib.data. Now it seems that the tf-slim training pipeline stalls if I request just 1 or 2 CPUs for my job (it used to work just fine with the dataset API provided by tf-slim). I does work if I grab 4 CPUs. I tried to come up with a MWE (see below). The interesting thing is that it is not getting stuck if I remove one of the tf.summary.scalars or .map() at line 39. I suspect this issue is related to #10369.
Source code / logs
import os
import tensorflow as tf
import tensorflow.contrib.data as tcd
import tensorflow.contrib.slim as slim

from tensorflow.contrib.data.python.ops.dataset_ops import _get_file_names

DATASET_DIR = '/path_to_the_dataset'
FILE_PATTERN = 'shapes_{}_*.tfrecord'
IMAGE_SHAPE = [48, 48, 3]

def _parse_function(example_proto):
    features = {
        "image/encoded": tf.FixedLenFeature(
            (), tf.string, default_value=""),
        'image/annotation/color': tf.FixedLenFeature(
            (), tf.int64, default_value=0),
        'image/annotation/shape': tf.FixedLenFeature(
            (), tf.int64, default_value=0),
    }
    parsed_features = tf.parse_single_example(example_proto, features)
    image_decoded = tf.image.decode_image(parsed_features["image/encoded"])
    color = parsed_features['image/annotation/color']
    shape = parsed_features['image/annotation/shape']

    return image_decoded, color, shape

def get_batch(batch_size=32, group_size=3, split_name='train'):
    file_pattern = os.path.join(
        DATASET_DIR, FILE_PATTERN.format(split_name))

    file_names = _get_file_names(file_pattern, randomize_input=True)

    dataset = tcd.TFRecordDataset(file_names)
    dataset = dataset.map(_parse_function)

    dataset = dataset.map(lambda image, color, shape: image)
    dataset = dataset.shuffle(buffer_size=10000)
    dataset = dataset.repeat().batch(group_size * batch_size)

    iterator = dataset.make_one_shot_iterator()
    images = iterator.get_next()

    images = tf.split(images, group_size, axis=0)
    images = [tf.reshape(x, [batch_size] + IMAGE_SHAPE) for x in images]

    return images

if __name__ == "__main__":
    with tf.Graph().as_default():
        x_1, x_2, x_3 = get_batch(batch_size=32,
                                  group_size=3)

        val = tf.reduce_sum(tf.add_n([x_1, x_2, x_3]))
        val = tf.Print(val, [tf.constant(0)], "I'm alive! ")

        global_step = slim.get_or_create_global_step()
        with tf.control_dependencies([val]):
            update_global_step_op = tf.assign_add(global_step, 1)

        train_op = update_global_step_op

        tf.summary.scalar('Summary 1', val)
        tf.summary.scalar('Summary 2', train_op)

        logdir = 'mwe_logdir'
        slim.learning.train(
            train_op=train_op,
            logdir=logdir,
            number_of_steps=1000000)

Thanks for reporting this... it definitely looks like a bug. I think I've tracked it down to the "OneShotIterator" op, which internally blocks on this line while a function executes to build the dataset:
https://github.com/tensorflow/tensorflow/blob/91cb809bd6bc885458c583d46f4a322c30fa12cf/tensorflow/core/kernels/iterator_ops.cc#L248
That will block one of the inter-op thread pool threads for the (typically short) execution time of the dataset construction function. The number of CPUs determines the default number of threads in that thread pool: when you have only 1 CPU, the system will deadlock as soon as you hit that line (because no more thread pool threads are available to run the function that will unblock it). When you have 2 CPUs, it can work, but slim.learning.train() uses tf.train.Supervisor, which asynchronously runs a background thread... that runs the same "OneShotIterator" op. To ensure that the op only initializes once, the initialization runs under a lock, acquired here:
https://github.com/tensorflow/tensorflow/blob/91cb809bd6bc885458c583d46f4a322c30fa12cf/tensorflow/core/kernels/iterator_ops.cc#L194
The problem is probably starting to become clear: two concurrent executions of the same "OneShotIterator" kernel will potentially block two inter-op thread pool threads, leading to deadlock in a 2-CPU system, because there are no more threads available to run the function that will unblock them.
Anyway, mea culpa, and thanks again for finding the bug. I'll be working on a fix, although it might not make it into the final 1.2 release. In the mean time, there are a couple of workarounds:

Increase the number of threads to more than 2 in the inter-op thread pool. You can do this by passing session_config=tf.ConfigProto(inter_op_parallelism_threads=3) to slim.learning.train().

Use dataset.make_initializable_iterator() instead of dataset.make_one_shot_iterator(). This comes with the additional requirement that you have to run iterator.initializer, which is not completely trivial with slim.learning.train() because you don't have access to the tf.Session. One possibility is to pass local_init_op=tf.group(tf.local_variables_initializer(), tf.tables_initializer(), iterator.initializer) to slim.learning.train().

Wow, thanks for the swift response! The first workaround seems to be working perfectly.
On a side note, I'm quite happy with the tf.contrib.data. My code has become way cleaner.


Run command/script after stack startup?

Using the stack GET parameter it is possible to let play with docker launch a stack automatically.
Is it also possible to run a command after the stack has been launched that executes commands inside the containers using docker-compose exec?

Right  now not automatically. But this is something we want to add soon!
On Sun, Jun 11, 2017, 20:23 strarsis<EMAIL_ADDRESS>wrote:

Using the stack GET parameter it is possible to let play with docker
launch a stack automatically.
Is it also possible to run a command after the stack has been launched
that executes commands inside the containers using docker-compose exec?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/play-with-docker/play-with-docker/issues/154, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIhp7uRFRLtXaB3dd2esimgl-K5jBAKks5sDHbngaJpZM4N2iwB
.

And an additional request which is also related:
Sometimes an app has to be configured to expect the right hostname + port (e.g. a WordPress site for a demo). Because the docker container itself knows only its own internal hostname, configuration from inside wouldn't work correctly - the actual publicly reachable hostname has to be determined from inside the PWD/shell on which the stack has been started. - A situation where running a command for setting things up also comes in handy.

Yes. We thought about injecting this to the container as an environment
variable.
On Sun, Jun 11, 2017, 20:36 strarsis<EMAIL_ADDRESS>wrote:

And an additional request which is also related:
Sometimes an app has to be configured to expect the right hostname + port
(e.g. a WordPress site for a demo). Because the docker container itself
knows only its own internal hostname, configuration from inside wouldn't
work correctly - the actual publicly reachable hostname has to be
determined from inside the PWD/shell on which the stack has been started. -
A situation where running a command for setting things up also comes in
handy.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/play-with-docker/play-with-docker/issues/154#issuecomment-307664460,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIhp14Tc_sQzZce5GB9JZJovtvmMvBXks5sDHnxgaJpZM4N2iwB
.

PWD_IP_ADDRESS is already set in the d-in-d shells.
(not sure if this is set in the stack auto-exec environments)
unfortunately, docker stacks don't allow you to reoplace characters like this ${PWD_IP_ADDRESS//./-}
:(
(throws a syntax error in validation)
I propose whichever ENV execs the docker deploy should have these vars:
PWD_IP_ADDRESS="<IP_ADDRESS>"
PWD_FQDN_IP_PREFIX="pwd10-0-82-3-"
PWD_FQDN_HOST_SUFFIX=".host1.labs.play-with-docker.com"

This would allow you to interpolate http://pwd10-0-82-3-8080.host1.labs.play-with-docker.com into the auto-stack files like this:
version: '3.1'
services:
  my-app:
    image: alpine
    ports:
    - 8080:80
    environment:
      web_host: http://${PWD_FQDN_IP_PREFIX}8080${PWD_FQDN_HOST_SUFFIX}/
    entrypoint: echo ${web_host}

Probably best to leave container's environments alone unless the stack specifies the configuration.
(sorry for scope creep on this issue -- we might want to move this somewhere)

Probably best to leave container's environments alone unless the stack specifies the configuration.

We're not parsing the stack file actually, so we don't know if it containers any env variables. Injecting the variables in the running container actually makes a lot of sense

@marcosnils you can interpolate env vars into a stack file 👍
no need for custom parsing.

@stealthybox: Is there an example? I want to interpolate the stdout of hostname command so I can use the docker hostname inside the containers.

Sure, here's a quick example of host shell variable interpolation:
https://github.com/adamcaron/flip/blob/master/dev-stack.yml#L6
That repo uses a shell script and a env/source file to parameterize the dev-workflow with the stack
You'll probably want to use the shellvar version of hostname instead of the command:
${HOSTNAME} vs $(hostname)
If you're trying to use container specific variables, you actually don't want to docker host's variable interpolation.
A good place to set options with container specific shellvars would be in the entrypoint.
You can escape the stackfile interpolation by using a double dollar sign: $$HOSTNAME <-- this will be $HOSTNAME inside of the container if used within a shell script in the entrypoint:
  lb:
    image: someloadbalancer
    entrypoint:
    - sh
    - -c
    - server-binary --fqdn=$$HOSTNAME

See my docker-in-docker example.
It uses some useful nested interpolation for the $token value:
https://github.com/stealthybox/docker-demo/blob/master/swarm/docker-compose.yaml#L13-L29

@strarsis ^ lmk if that's helpful
back on topic:
these interpolation features can be useful for generic, declarative configuration of Play-with-docker stacks, because we can load the values of the interface in the execution environment for the stack.

After setting up an HTTP server, how to access the node normally with a web browser?
Prepend the $HOSTNAME to something? It would be nice to have the URL shown per node.

@marcosnils you can interpolate env vars into a stack file

@stealthybox yup, I'm aware about this. Some time in the conversation I forgot that we were talking about stacks. You can actually use interpolation variables there as well as the stack gets executed in the same container that gets created after that.

@marcosnils, @xetorthio, @stealthybox: Any news on this? :)

@strarsis the env variabe thing has been added already. Regarding the specific functionally which this issue refers we're not sure how the API would look regarding executing a command once compose finishes. Why not creating another service with restart-condition: none like swarm-exec does?.

So I want to use the hostname + port as docker-compose env so e.g. a WordPress site will correctly adjust the URLs - without the visitor would be redirected to an incorrect URL, the site won't work at all then.
With this new feature added, can I now do this or emulate this somehow?

@marcosnils I'm not sure it's the right approach but you can use extension objects with Docker Compose v3.4 now:
https://github.com/docker/cli/pull/452
x-pwd-post-deploy:
  command:
    - echo
    - $${HOSTNAME}

I think your solution of specifying a one-shot service with restart-condition: none is a good one.
One thing I did notice is that the PWD_IP_ADDRESS environment variable is no longer injected into the d-in-d.
I think this is the relevant module:
https://github.com/play-with-docker/play-with-docker/blob/master/docker/docker.go#L303
There's still remnants of it in other places:

https://github.com/play-with-docker/play-with-docker/blob/master/pwd/types/session.go#L20
https://github.com/play-with-docker/play-with-docker/blob/master/dockerfiles/dind/Dockerfile.dind#L53
^ this one is interesting because it's no longer in the daemon.json

@stealthybox: This new feature (which I can use for injecting outside environment variables into container as I intended?) - is the Docker (CLI/Composer) version supporting it used by current live play-with-docker?

@marcosnils I'm not sure it's the right approach but you can use extension objects with Docker Compose v3.4 now:
docker/cli#452

@stealthybox yeah, I've seen this approach but that'd require to use some custom features that only work in newer versions of compose. I'd prefer to avoid doing things like that.

I think your solution of specifying a one-shot service with restart-condition: none is a good one.

Yup, I think that's the way that everyone does it currently.

One thing I did notice is that the PWD_IP_ADDRESS environment variable is no longer injected into the d-in-d.
I think this is the relevant module:

That PWD_IP_ADDRESS wasn't the container address but the IP of the PWD container in the session because we used things like internal DNS to resolve things. We've decided to remove that as it's not necessary anymore that's why we removed it. We can't inject the IP address of the container as an env variable because there's no way of knowing it before the container is created.

So I want to use the hostname + port as docker-compose env so e.g. a WordPress site will correctly adjust the URLs - without the visitor would be redirected to an incorrect URL, the site won't work at all then.
With this new feature added, can I now do this or emulate this somehow?

Can you please provide a stack example of what you're trying to achieve so I can better understand if it can be sorted out with what's already there?. I believe the "Exec commands after stack is up" objective is already covered with the swarm-exec strategy I've described before.

@marcosnils:
So the docker-compose setup is upped, then a setup.sh script should be executed inside the container which sets up WordPress. Very important for the WordPress setup is the host and port for the proper base URL - otherwise the WordPress site will not work at all.

@strarsis I don't quite understand what you mean. We've deployed wordpress in PWD successfully before without having to specify any host. Have you tried this?. http://play-with-docker.com/?stack=/wordpress/latest/stack.yml

@marcosnils: wp core install requires --url parameter, it doesn't seem to be optional like in the interactive WordPress setup which seems to autodiscover it correctly.

@marcosnils: I just have discussed this issue in wp-cli/core-command#52:

$_SERVER['HTTP_HOST'] is only present in web requests, so you'll always need to specify --url= for CLI installation requests.

So for automatically setting up a WordPress installation one requires the host + port in the setup.sh script so it can pass it using the --url parameter.

@strarsis in that case you'll have to do some bash magic to send that flag in the command line
PWD Url's are composed as follows: http://ip-<session_id>-.direct.labs.play-with-docker.com (i.e: http://ip-2-135-3-b8ir6vbg5vr00095iil0-8080.direct.labs.play-with-docker.com).
The session_id can be obtained from the SESSION_ID env variable. So it's basically getting the ip address of the eth0 interface and replacing dots for hyphens

@marcosnils: Thanks!
Are there examples about how to use swarm-exec with play-with-docker?
Do I have to add a swarm-exec field to the docker-compose.yml of the project?

@marcosnils:
https://github.com/docker/compose/issues/5049

@strarsis ???.

ERROR: The Compose file './docker-compose.yml' is invalid because:                                                                     Unsupported config option for services.wordpress: 'x-pwd-post-deploy'

@strarsis you need to set
version:

at the top of your compose yaml >= '3.4' in order to use extensions
I don't know why you linked that other issue.
It seems very unrelated.

@stealthybox: docker-compose uses version: '3.5' now, but still the same error.


Implement History Command and the Shell Expansion Partially.

Well, I kind of implemented #10 myself.
Here's what can be further improved:

the alignment

!-n and string operations mentioned in the man page
Record → Array<string> conversion is somewhat hackish.
the code since I'm fairly new to TypeScript

Great stuff - thank you for contributing! I'll leave this open for now and review it once I have more time.


fix(system_monitor): multithreading support for boost::process (#1714)

Signed-off-by: v-nakayama7440-esol<EMAIL_ADDRESS>This PR is a backport for v0.3.11.
Exactly the same content as https://github.com/autowarefoundation/autoware.universe/pull/1714 .
Description
boost::process::pipe internally creates file descriptor. However, this file descriptor does not support multithreading because O_CLOEXEC is not set. Because of this, when each thread of SystemMontor uses boost::process to create a child process, the file descriptors of boost::process::pipe conflict between child processes. As a result, the child process waits for the file descriptor to be released.
In this PR, the SystemMonitor application creates file descriptor with O_CLOEXEC set and passes it to boost::process::pipe to eliminate the wait for child process to release file descriptor.
Related links

The issue https://github.com/autowarefoundation/autoware.universe/issues/939 was still observed after the fix https://github.com/autowarefoundation/autoware.universe/pull/948.
This is related to the boost::process issue and to apply the workaround described in https://github.com/boostorg/process/issues/169#issuecomment-679170651.

Tests performed
Since it is an independent component and we do not anticipate any adverse effects from being an older version of the software, we have determined that new verification through backporting is unnecessary.
Notes for reviewers

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

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

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

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

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

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

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (beta/v0.3.11@8556745). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@              Coverage Diff               @@
##             beta/v0.3.11    #170   +/-   ##
==============================================
  Coverage                ?   0.00%
==============================================
  Files                   ?      20
  Lines                   ?    1719
  Branches                ?       0
==============================================
  Hits                    ?       0
  Misses                  ?    1719
  Partials                ?       0

Flag
Coverage Δ

differential
0.00% <0.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 at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fixed initial heading getting overwritten in Initial and Continuous tracking modes on Android

In my testing, when ARSceneView is configured with NorthAlign set to true and tracking mode set to Initial or Continuous then aligning using compass doesn't work properly on Android.
OrientationHelper_OrientationChanged gets called first setting OriginCamera with initial heading, then LocationDataSource_LocationChanged gets called, overwriting initial heading with zero.
In this pull request I propose a simple fix to this problem. I'm not entirely sure this is the best solution, maybe some kind of boolean flag and lock preventing initial heading from overwriting would do better.
Tested on POCO X3 NFC phone, running Android 11.

The change looks good to me. I can't comment on the existence of the issue on native android unfortunately.

So, if you approve my changes, @dotMorten @nCastle1, can you merge this pull request?
I'm interested in building and using toolkit straight from repository main branch and merge would make this easier for me.

@kamszyc Thank you for the PR!


Fixed typo in docs/ref/models/querysets.txt.

Fixed formatting that rendered code with double ticks when it should have been rendered as bold

@ryancheley Thanks :+1:


Create pattern45.py

##Patter45
write a Python program to print the below pattern

@20a31a05e8 You raise an issue stating the details which are asked, I will assign the issue and then make a pr and so I am closing this pr.


it feels like impossible to merge

I am trying to merge master branch with openxc/uds-c I keep on getting conflict error
both modified:   deps/isotp-c
I do not understand how to resolve this. how do you update your sources?

I don't know what commands you're running or what your conflicts are, but isotp-c is a submodule for uds-c so you will need to work with Git submodules: https://git-scm.com/book/en/v2/Git-Tools-Submodules.

Sorry for not updating here, My submodule master diverged (I don't know how) from origin/master which made it fail to merge. I fixed it. Sorry to bother.


ocamlPackages.csexp: use Dune 2

Motivation for this change
Prepare for OCaml 4.12.
Things done

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

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

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

@GrahamcOfBorg build acgtk dot-merlin-reader dune-release eff framac google-drive-ocamlfuse jackline liquidsoap ocaml-crunch ocamlformat ocamlformat_0_14_3 ocamlformat_0_15_0 opa orpie patdiff satysfi

@GrahamcOfBorg build acgtk dot-merlin-reader dune-release eff framac google-drive-ocamlfuse jackline liquidsoap ocaml-crunch ocamlformat ocamlformat_0_14_3 ocamlformat_0_15_0 opa orpie patdiff satysfi


Make the mailing list signup form more prominent

I noticed that the current button takes you to a URL with an HTTPS warning.
I think having the form inline in the page would be better.

I've just fixed that HTTP/HTTPS problem. ;-)

Covered by #127.


Support CSV with serializer

Source/destination types
  public record RootGetResponse(
    [property: JsonProperty("data")] ServerCsvData Data
  );

  [Delimiter(",")]
  public record class ServerCsvData
  (
    [property: Name("Header001")] string Header001,
    [property: Name("Header002")] string Header002,
    [property: Name("Header003")] int Header003
  );

Source/destination JSON
{"data":"\"Header001\",\"Header002\",\"Header003\"\n\"Value001\",\"Value002\",\"3\""}

Expected behavior
Interoperability with CSV parser from CSVHelper.
Actual behavior
Newtonsoft.Json.JsonSerializationException "Error converting value"
Steps to reproduce
var response = httpClient.GetAsync("api/getData");
response.EnsureSuccessStatusCode();
RootGetResponse rootGetResponse = await response.Content.ReadAsAsync<RootGetResponse>();

A JSON serializer is not a CSV serializer, and in my honest opinion it seems to be rather outlandish to expect or ask for a JSON serializer to be able to deserialize CSV data that has been haphazardly "packaged" into a JSON string. (Disclaimer: I am not affiliated in any way or form with the Newtonsoft.Json project nor any of its maintainers.)
If you got a string in your json data that is basically CSV data, you will need to process that CSV text after the JSON deserialization. One way to do this could be a custom JsonConverter (which you will have to write, if you can't find one offered ready for use) applied to those properties of your C# models which contain CSV text strings in the respective JSON properties. The custom JsonConverter's task (specifically that of its ReadJson method) is then basically to read the string value, process it as CSV in whatever way you need/want, and create an object instance of the appropriate type and return it.

A JSON serializer is not a CSV serializer

But XML is part of a JSON serializer?

But XML is part of a JSON serializer?

FYI: Newtonsoft.Json, does not de/serialize XML, neither standalone XML nor XML text put into JSON strings. All Newtonsoft.Json supports is conversion between JObject and XElement/XmlElement. (The latter two being types from the BCL.)

But XML is part of a JSON serializer?

It's not what you seem to assume. All Newtonsoft.Json supports is JSON de/serialization of XElement/XmlElement object instances. Newtonsoft.Json does not de/serializize standalone XML text nor XML text embedded as strings in JSON data.


TypeError: init() missing 2 required positional arguments: 'confidence' and 'class_id'

detections = sv.Detections(xyxy=xyxy),confidence?class_id? Do you have this error?

I encountered the same problem, did you solve it?

I still can't run this py file

Hello, could you help to debug whether it's due to the lack of proper language prompt setting that the corresponding object is not detected, or maybe the GPU machine is set up incorrectly? Because currently, the deformable-attention operator encounters problems when set to 'cuda:1'.

This error could be caused by "supervison" version.
I check supervison by pip list : supervison 0.3.1
I update supervison to 0.8.0 and problem solved.
pip uninstall supervision pip install supervision==0.8.0


Docker quickstart not working. Container doesn't seem to successfully start.

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Run sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher
Result:
https://localhost never seems to work, shows ERR_CONNECTION_REFUSED.
Other details that may be helpful:
Looking in the docker logs >
rancher.log it seems to get stuck and repeat..
E0514 15:16:15.527602       8 memcache.go:134] couldn't get resource list for management.cattle.io/v3: the server could not find the requested resource
E0514 15:16:15.527931       8 memcache.go:134] couldn't get resource list for project.cattle.io/v3: the server could not find the requested resource
E0514 15:16:15.534570       8 memcache.go:134] couldn't get resource list for management.cattle.io/v3: the server could not find the requested resource
E0514 15:16:15.534884       8 memcache.go:134] couldn't get resource list for project.cattle.io/v3: the server could not find the requested resource

Environment information
rancher/rancher                  latest              1d6627a9e2de        11 hours ago        508MB

Docker version (use docker version):

Client:
 Version:           18.09.0
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        4d60db4
 Built:             Wed Nov  7 00:48:57 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.0
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.4
  Git commit:       4d60db4
  Built:            Wed Nov  7 00:16:44 2018
  OS/Arch:          linux/amd64
  Experimental:     false

The log attached does not contain the log lines you showed in the issue. Does this still occur? Where are you running the container, and what specifications does the machine have?
Let me know so I can reopen if needed


Microstrain inertial driver update from 2.6.0 to 3.0.0 no longer allows to hit 200Hz on 3DMGX5-AHRS

Fairly simple issue (I hope)
Our team had been using version 2.6.0 of the Microstrain Inertial Driver to collect imu data. Our custom config file set the imu_data_rate field to 200.
The method of measuring the actual rate is by inspecting a rosbag where we bag all of the data on the topic /imu/data, count the messages received, and divide by the length of the rosbag.
Upon updating to version 3.0.0 (installed from apt) we cannot hit this rate using the same configuration file. We are seeing numbers in the range 150-190 now.
Has anyone else seen rate problems after updating the driver version?
Maintainers, please let me know what else is needed for an issue diagnosis...

@pjmara, thank you for bringing this to our attention. This was a problem with how the data gets batched when using USB.
#45 should Resolve this.
As a side note, it is important to note that 200 is technically not a valid data rate for the IMU data on a GX5-AHRS. When configuring any of the _data_rate fields what you are really setting is the decimation we set on the sensor. Since the base data rate of the IMU data on a GX5-AHRS is 500hz, and 200hz is not evenly divisible, we can not set a decimation to acheive that data rate. As such, if you set the data rate to 200, you will actually receive the data at 250 hertz. The driver should log a warning in these cases

#45 should Resolve this.
To me it seems like this PR is about fixing decimation rate and messaging surrounding decimation rate. At least that is what the PR says. Our behavior is an inconsistent data rate ranging all over the place between roughly 150-190 hz... I guess I don't see how that fix helps us? Unless you are saying we have a bad decimation rate which is giving undefined behavior

As a side note, it is important to note that 200 is technically not a valid data rate for the IMU data on a GX5-AHRS.
Perhaps I gave you the wrong spec? Our IMU is this imu and that model number 3DMGX5-AHRS at the top of the page I assumed was a one-to-one mapping.
The spec says that you can get raw imu measurements up to 1khz, so I thought that was our base rate? (evenly divisible, 1000/5)

To me it seems like this PR is about fixing decimation rate and messaging surrounding decimation rate. At least that is what the PR says. Our behavior is an inconsistent data rate ranging all over the place between roughly 150-190 hz... I guess I don't see how that fix helps us? Unless you are saying we have a bad decimation rate which is giving undefined behavior

I was able to recreate the behavior you were seeing. It was due to the fact that we would only publish after all data packets for a cycle were processed, but when we process a data packet, we override existing data in the message buffer. So when more than one packet arrived in a cycle which happens sometimes with high data rates, especially with USB buffering, we would override some data and only publish the most recent packet's data.
There are also some additional changes in there having to do with checking decimation and making sure we are spinning at the right rate to be able to handle data properly, apologies for the confusion.
The main fix related to this issue is that we publish here after every data packet, instead of here after all data packets per cycle

Perhaps I gave you the wrong spec? Our IMU is this imu and that model number 3DMGX5-AHRS at the top of the page I assumed was a one-to-one mapping.
The spec says that you can get raw imu measurements up to 1khz, so I thought that was our base rate? (evenly divisible, 1000/5)

You gave me the right spec, it was me who looked at the wrong device, apologies for the confusion again

@pjmara I could get this pushed through and released if that is the only way you are able to test this as I am fairly confident this is the fix for this particular issue, but are you able to test on this branch to verify that the issue is gone? We have documentation on building from source here

Can confirm building from source fixed! I would definitely love to get it into the version in apt at some point so that when we have new devices we can just install from apt...our current solution is building a .deb ourselves and installing it on our hardware

Should be fixed in 3.0.1

How long (roughly) until this will be available on the apt install? Trying to figure out if fighting through these bloom-generate errors is worth my time :(

There doesn't appear to be a set time for when the ROS maintainers do package syncs. The maintainers approved my PRs, so it should be available in the next sync.
If you don't want to wait for that, you could use the TestingRepository until then, which has it available right now, but comes with all the risks of the testing repository


Debugging...

Hi,
I have tried to set it up, but apparently it's not scanning. I don't know if that is a problem in the plugin or the connection to clamd (which is in a remote docker container - i have changed the settings to tcp).
Any hints how to get more visibility?
Peter

@logopk How's your digging? Have you found something?

Is everything ok now? Can we close this issue?

Yes Thanks!
(I promise to RTFM next time :-) )


Feature Request: Upgrade swagger2markup version to v1.0.0

Is there any plan to upgrade swagger2markup version from 0.9.2 to 1.0.0?
Swagger 2.0 added operationId to uniquely identify an API operation, which is also supported in swagger2markup-1.0.0. Currently the latest version of springfox-staticdocs (v2.4.0) only supports swagger2markup-0.9.2. It would be nice to have the latest features of swagger2markup supported as well.

We welcome PRs! :)

@RobWin looks like a lot has changed since s2m went 1.0 😕   Could point me in the right direction? (or perhaps upgrade the library)
        Swagger2MarkupConverter
                .fromString(swaggerJson)
                .withMarkupLanguage(markupLanguage)
                .withExamples(examplesFolderPath).build() //< -- whats the equivalent of this?
                .intoFolder(outputDir);

This requires JDK 8 so pushing this out

Closing as a duplicate of #1497


SW-5335 Updated date time format

#2604  👈
main

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

Join @tommylau523 and the rest of your teammates on  Graphite

Merge activity

May 10, 12:26 PM EDT: @tommylau523 started a stack merge that includes this pull request via Graphite.

@tommylau523 please update the date format in the comment above the function modified in this PR and the entry in this confluence doc 🙏 Thanks!

@tommylau523 please update the date format in the comment above the function modified in this PR and the entry in this confluence doc 🙏 Thanks!

Yes!! Sorry about that! I just pushed a new PR and updated the confluence.


Async/await missing in current documentation/handbook

The online handbook is really fantastic. However I noticed it is missing a section concerning async/await functionality.
https://www.typescriptlang.org/docs/tutorial.html

Thanks for reporting! Going to move this to the handbook repo.

This issue was moved to Microsoft/TypeScript-Handbook#400


Can add comment in feature file

StepDefinition should contains // if feature file contains #

feature/comment-from-feature-to-stepdefinition


chore: stop capturing initialize errors

This is to address the new errors appearing on sentry related to project initialization. I just realized that our logger creates error entries when we call the .error method. I replaced existing logging related to project initialization from error calls to info, to avoid this.

Codecov Report

Merging #474 (418caa4) into development (ada125e) will decrease coverage by 0.23%.
The diff coverage is n/a.

:exclamation: Current head 418caa4 differs from pull request most recent head f207672. Consider uploading reports for the commit f207672 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
@@               Coverage Diff               @@
##           development     #474      +/-   ##
===============================================
- Coverage        53.65%   53.42%   -0.23%
===============================================
  Files              187      187
  Lines             4799     4799
  Branches           790      790
===============================================
- Hits              2575     2564      -11
- Misses            1991     1998       +7
- Partials           233      237       +4

see 4 files with indirect coverage changes


Fix #1589: Compiler crash on switch-match with 2 guards for the same value.

Review by @gzm0

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1565/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2029/
Test PASSed.

LGTM. Did you move this around on Waffle.io?

What's Waffle.io? :confused:

Hahaha, a board for your GitHub issues. It seems pretty nice, but is way too intrusive IMO.


Fix handling of VLAN packets with stripped VLAN header

This PR fixed the handling of packets with stripped VLAN headers by forwarding also frames to the virtual interface with TCI set by the driver.
It also sets the priority of a packet based on the PCP field of the VLAN header.
I tested this with my tricore port and an enhanced dwmac driver.

I think we need a test case for testing this, could you add one (to tests/net/vlan)?

I think we need a test case for testing this, could you add one (to tests/net/vlan)?

It seams to be difficult to test incoming packets with the current test setup. This would mean a major rewrite of the tests or did I miss something?

It seams to be difficult to test incoming packets with the current test setup. This would mean a major rewrite of the tests or did I miss something?

Yes, it is a bit tricky. It is easy to set the stripped bit for the simulated Ethernet interface, but then we would need "receive" a packet with stripped VLAN interface and then feed it to network stack and then verify that everything works ok.
I am certain you have tested the stripped vlan tag case with your Ethernet driver, but how well you tested the case without the stripping bit set. Also is everything working if you have two Ethernet interfaces in the system with one interface stripping enabled, and one not. Probably in this case it is quite difficult find hw for it. I do not have such hardware that would support tag stripping, so just trying to make sure all the things are working.

@go2sh do you plan to return to this PR?


Example for a newer .NET framework?

The current .NET example is written for a very old framework. There are also naming issues in the code (class cert) which do not serve to increase my trust in the code being secure. Could we get a sample for e.g. ASP.NET Core 3.x?

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

ID: eb440603-950a-c224-f6c9-222ca502d5a5
Version Independent ID: 0b5c4944-0327-91fc-2b0b-c19a1b873b64
Content: Configure TLS mutual authentication - Azure App Service
Content Source: articles/app-service/app-service-web-configure-tls-mutual-auth.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@juunas11 , Thanks for brining this to our attention. We will investigate it further and update you shortly.

@juunas11, I'm going to assign this to the document author so they can update the document accordingly.

@juunas11 Thanks for your insightful feedback. I've fixed the code issue you mentioned and it should be published sometime today. But the code is mainly there to show how one would perform the verification of client cert manually, not for lift-and-shift into their code. We currently don't have the resourcing to provide additional code samples for this doc, but if you're interested in contributing to it, it would be very appreciated. The Node.js sample was actually provided by a community contributor.
I will close this issue for now. #please-close

@cephalin - Thank you for fixing the doc.
@juunas11 - Thanks again for bringing this to our attention.  If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

It looks like the single character type was fixed, but the main issue, including a .NET Core sample, was not?

@cocowalla That's correct. Per my note above, the sample is meant to show you how one would make use of the client cert that's provided in the header. It's really up to the webdev how exactly they want to verify the client cert. Unfortunately we currently don't have the resources to create and maintain additional code samples for this doc.

Sure, I didn't mean for examples of how to verify the cert, only for how to access it using ASP.NET MVC Core; using a string header seems a bit "crude", where I would assume there is some "ASP.NET MVC Core way" to do it.
Given ASP.NET is legacy, and default HTTP-triggered function app template defaults to having a HttpRequest argument, I thought it reasonable to at least include an example of how to access the client certificate from a HttpRequest (maybe via ITlsConnectionFeature?) 🤷♂