Transition's t.isOutro

Description:
I believe that we should have a isOutro property to be checked during transitions.
It used to be that simply checking !t.isIntro was fine, but since 0.8 we can manually trigger transitions using ractive.transition(transition, node, options), thus adding a third case.
if (t.isIntro) {
  // intro
} else if (t.isOutro) {
  // outro
} else {
  // ractive.transition(..)
}

In the meantime, you can technically check for outros with t.isIntro === false, but it's not that intuitive.
if (t.isIntro === true) {
  // intro
} else if (t.isIntro === false) {
  // outro
} else {
  // ractive.transition(..)
}

Versions affected:
0.8 and above

That makes a lot of sense and is a tiny change, so it's in edge now.


Add new cluster resource args

Add new cluster resource args
Update flux example

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1510  👈 (View in Graphite)
#1507 : 1 other dependent PR (#1508 )
#1506
#1505
main

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

Merge activity

Dec 3, 9:34 AM EST: A user started a stack merge that includes this pull request via Graphite.


@everyone @here @role exploit #2

Hey! I noticed there was the exact same exploit previously "fixed". However I have found that changing your nickname to: @everyone @here or <@&ROLEID> or <@!USERID> will mention successfully. This is excitable and I have no way to fix the issue. I love your npm but cannot use it in my bot as a result of this exploit!

I hope its fixable 🤞🤞🤞

I hope its fixable 🤞🤞🤞

Hello, sorry for that very annoying abuse glitch.
I have already worked on that issue here : #20, so now all messages will not contain any mention except for real users.
Check my commit about it here: 11d507fbceec9178135d322ce12db413ed99d8e0
A new release will be out soon with that fix!

Oh my bad! I thought that was a different bug which got fixed, thanks for the reply 🙂 cannot wait for the fix

Result with the latest development build:

There is no more member mention in the "versus" message.
Note that the bot is mentionning the real user here, not @everyone.

nice, your probably already aware however: I can bypass this addition by changing my name to `@everyone , which will simply close the formatting and pull the mention outside of it. I guess if you havent already you'll have to make the bot remove all ```` characters before sending a msg

Same applies if its mentioning discord tags rather then nicknames too

that does not work I think, here is the result with ``@everyone`:

Try 3 ``` in your nickname
Try:
```_ _@everyone

Or Text```_ _ @everyone

Try 3 ``` in your nickname
Try:
```_ _@everyone

No problem with that username on my Discord server..

Theres always a way!

I am using single quotes to escape the nickname, not triple ones so it should be good. Your examples do not create bugs with my bot. But if you are worried about that, I can use a Discord.js method called escapeMarkdown to be sure that the glitch will not appear.
More info here: https://discord.js.org/#/docs/main/stable/class/Util?scrollTo=s-escapeMarkdown

ook.. this does not work with method escapeMarkdown..

Rip

You could try somehow replacing all username text characters with a font such as this:
𝗔𝗕𝗖𝗗𝗘𝗙𝗚𝗛𝗜𝗝𝗞𝗟𝗠𝗡𝗢𝗣𝗤𝗥𝗦𝗧𝗨𝗩𝗪𝗫𝗬𝗭
𝗔𝗯𝗰𝗱𝗲𝗳𝗴𝗵𝗜𝗷𝗸𝗹𝗺𝗻𝗼𝗽𝗾𝗿𝘀𝘁𝘂𝘃𝘄𝘅𝘆𝘇
This font is almost the same as discord bold and will remove mentions and prevent tagging of @everyone and roles,
just an idea

It's a rather complex way of doing things I think.. also with the current language file (latest development version) it does not seem to have nickname problems. Maybe you can try with this language file? I can't reproduce your problems by using single quotes around nicknames.
https://github.com/utarwyn/discord-tictactoe/blob/11d507fbceec9178135d322ce12db413ed99d8e0/config/locales/en.json#L1-L20

Ok giving it a go rn!

I have just released 2.0.8 to fix the issue! :smile:
https://github.com/utarwyn/discord-tictactoe/releases/tag/v2.0.8


[1707] Expose recruitment cycle year on v2 api

Context
Recruitment cycle year
Changes proposed in this pull request
Expose Recruitment cycle year on v2 API
Guidance to review
Courses endpoint with sites included
Checklist

[x] Make sure all information from the Trello card is in here
[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

 Expose recruitment year on API V2

just courses and sites? no provider for the v2?


fix(file index): handle cases where no files are found or passed in

Also shortened the remove_duplicate_indexes call.
No need to pipe to uniq
I left the build numbers as they were.
This addresses issue #119.

Thanks! Released in 1.15.1 🎉


allo.google.com

@adguard-bot commented on Mon Apr 23 2018
Issue URL (Incorrect Blocking)
https://allo.google.com/web
Comment
Username: @altokarev

Screenshots

Screenshot 1

System configuration

Information
value

Platform:
Mac

AdGuard version:
1.5.6

Browser:
Chrome

Filters:
Russian,English,Spyware,Social media,Filter unblocking search ads and self-promotion,Annoyances

@Alex-302 commented on Tue Apr 24 2018
what is wrong?

@ameshkov commented on Fri Jun 08 2018
Does not work with AG for Mac enabled. Seems to a bug.

It's bug in the CoreLibs.
Workaround: Excluding an application from ad blocking.

Wrong ticket?

@sfionov Sorry, confused tasks.

cannot reproduce on the current version


Remove VGS Alias formats from StarLarky

https://github.com/verygoodsecurity/starlarky/commit/ea0adcf80548c42e15d41e815d4237040d956fe9#diff-cf5faff91ae9cd74b7b9d2504673969166da7d94e0b519c53f7b0dfaa2fd856f
This seems like a misplaced validation.  The StarLarky repo should not care about the names of VGS alias formats.  It should just have an interface that handles exceptions in case the runtime determines that the alias format is not supported.
Having to update StarLarky every time a new Alias format is created does not seem like an appropriate workflow.

Are you planning on exposing to customers the alias formats via Larky? If so, can it be an enum that you can override by passing in a string until larky is updated?


Initial Audio Rendering missing samples....

Apple Feedback Assistant ID: MISSING
DESCRIBE THE BUG:
I have an Storyline with audio only.  It needs to seemlessly repeat an audio sample many times. I have 1 frame of silence to set the zero point.  The audio renders differently if that first frame is turn on or off, when it shouldn't.
This glitch in exporting audio happens when rendering video with it as well.  Having a built in fade doesn't help and is affected by this.   Manual fading is affected by this too.

TO REPRODUCE:
In Audacity, Generate a "silence" Flac file of 1 second.
IIn Audacity Generate a "tone" Flac file of a minute or ten.  It just needs to be constant sound for the whole file.
In FCPX, Drop in the silence and make it 1 frame long and "Create a Storyline" on it.
Drop in the tone file into the storyline after the silence frame.
Export the Audio only as WAV.
Turn off the 1 frame of silence.
Export the Audio only as WAV again.
Compare the two audio exports in Audacity.

EXPECTED BEHAVIOUR:
Turning on and off the 1 frame of silence should not have any effect on the test tone audio rendering.

SCREENSHOTS:
Here is what it looks like with the 1 frame of silence.  this is correct.
  This produces an audible click, and is an error.
Here are the combined images scaled properly.

there are missing samples at the very beginning.
The silence and audio test tone was 96khz- 24bit flac.
The project is 48 kHz audio, and 24 FPS.  I've seen this audio bug with other sample rates.
As you can see, the silence is mono.  the 40 hz Harmonics is stereo.
and there is nothing extending or strange with the Audio Component/expansion.  Everything is lined up correctly.

SPECS:

2021 16-inch MacBook Pro (M1 Max, 32GB RAM, 2TB SSD)
macOS Sonoma 14.6.1
Final Cut Pro 10.8.1

ADDITIONAL COMMENTS:
I have extensively run tests on the audio rendering algorithm testing the test tone in a storyline without the 1 frame of silence.  All the audio export algorithms were tested, here are the results.
🪳 AIFF has file size limitations that are not warned about.  If you try rendering a file larger than it can handle, it will try but get cut off.  No warning.  All the stuff the file can't handle (due to file size limitations) is rendered and promptly ignored.
WAV and CAF holds a properly rendered file.  The test tone shows up in the very first sample without missing samples, and is the exact length it should be to the sample.
AAC, AC3, and MP3 had weird things going on with being too short, or slightly longer than the total video length.  They also added silence at the beginning (~9ms, ~9ms, and ~43ms, respectively), but I think that's the format rather than the audio rendering.  This needs confirmation though.  My initial tests were rudimentary.
The fact that there was several frames of audio missing at the end in some lossy formats was disturbing.
Apple has not VALIDATED their audio rendering for lossy encoding formats.  I suspect it's a regression issue....  they didn't do regression they should have done.

I'm testing this in FCPXI right now.
..... or is it FCP11?   Or are we just retaining FCPX?

This is 100% still a bug in FCP11.  I tested it with 60 fps.   The tone started at exactly 1 frame after the silence exactly as expected.
The silence being turned off auto-destructed those exact same ~5ms of audio in the tone,  even with a new 60 fps project.


ampmake build-cli doesn't generate amp binary on mac anymore

ampmake clean build-cli

amp -> .../dev/go/src/github.com/appcelerator/amp/bin/darwin/amd64/amp: No such file or directory

make clean build-cli generate it

I believe this happens because ampmake runs the amptools container so when the $GOOS command is run it fetches amptools os rather than the systems os. The make clean build-cli command doesn't use ampmake and the buildall-cli is called in ampmake check rather than build-cli.

This is not a bug. As mentioned in https://github.com/appcelerator/amp/pull/926, if you build in a container environment (using ampmake), you need to use buildall-cli right now to build all cross-compiled versions of the cli.
The build-cli rule is specifically dedicated right now as an optimization for working on cli commands. You can run make build-cli (assuming you have the go and make installed locally, and it will build a version correctly for your platform. When you run make inside of the amptools container, then $GOOS will be the OS that the amptools container uses (it's currently based on an ubuntu image).
We could add a few more specific cross-compilation target rules (eg, build-cli-darwin) that would be guaranteed to work from ampmake -- so $GOOS would be specified instead of determined from the environment. But we don't have time at the moment, so please use ampmake build|buildall|buildall-cli|check) when you want to guarantee the cross-compiled versions are built. When you're hacking on the CLI itself, just run make build-cli as a quick way of building until you're ready to run ampmake check and submit your PR.

@JosephGJ Your analysis is correct!

ok, thanks Tony, i close this issue


External Boost and ASIO library support for using with Conan package manager

It would be nice to support Boost include dirs override. For example:
if (HZ_EXTERNAL_BOOST)
    find_package(Boost REQUIRED)
    include_directories(${Boost_INCLUDE_DIRS})
else ()
    include_directories(SYSTEM ${PROJECT_SOURCE_DIR}/external/include/)
endif(HZ_EXTERNAL_BOOST)

Hello, it can be done. Did current version caused any problems like version compatibility, etc?

@ihsandemir I'm using hazelcast cpp client as conan package (with many others packages depending on Boost). I can easily override Boost version with any new/old one, same with asio, so all of my dependencies would be compiled with same Boost version.

Did current version caused any problems like version compatibility, etc?

Can't provide such info, but I had some compatibility problems with shared_ptr (compiled one module with 1.66.0, another with 1.5X.0, the system one).

Ok, I see. I think we can do this since there is a need for it.
Did you package Hazelcast for conan? Are there any code changes you needed to make the conan package?

Ok, I see. I think we can do this since there is a need for it.

Thank you!

Did you package Hazelcast for conan? Are there any code changes you needed to make the conan package?

Not really. I've written the basic recipe for hazelcast-cpp-client, but didn't polish it enough nor covered all possible cmake options there.

Oops, not quite. With HZ_BUILD_WITH_SSL option turned on, some includes for asio/asio/include/asio/ssl/* get activated. So if I override asio path, compilation fails.

I just merged the PR to master. Can you please try and let me know?

Ok, I see. I think we can do this since there is a need for it.
Not really. I've written the basic recipe for hazelcast-cpp-client, but didn't polish it enough nor covered all possible cmake options there.

Does this recipe handle Windows and MAC OS builds at all? Windows library names are totally different.

@SX91 Were you able to try the master branch with your setup and verify that the fix actually works for you? I am eager to hear on the result.

I am closing this issue since I did not get  feedback for a while, please feel free to reopen if the problem still exists.

@ihsandemir Hello! Sorry for the delay.
Looked through the changes. Yes, options are fixed now, but can't see external boost library support there.

Yes, you are correct, I forgot to add the options to cmake file. I will send a PR for that. Thanks.

@ihsandemir the fix at #490 looks good! Thank you!

@ihsandemir hello!
Latest release (3.11.0) doesn't include ASIO in archive (the directory at external/include/asio is empty).
external/include directory structure is too error-prone. You've introduced new dependency easylogging++ and placed it under external/include directory, but that directory is included only if HZ_FIND_EXTERNAL_BOOST is set to OFF.
Maybe the better structure would be external/<DEP_NAME>/include/<...>?

hello @SX91 we now have the conan integration PR almost ready to be merged to conan center https://github.com/conan-io/conan-center-index/pull/4452


[Bug] Elasticsearch experiences Bulk write of deprecation logs encountered some failures

Is there an existing issue for this?

[X] I have searched the existing issues

What product(s) are you seeing the problem on?
OpenChallenges
Current behavior

openchallenges-build-images
nx serve-detach openchallenges-organization-service

The three ES instances fail to start. The 2nd and 3rd nodes fail because the first node fails. The logs of the first node end with:
{"type": "server", "timestamp": "2023-09-05T01:10:35,197Z", "level": "ERROR", "component": "o.e.x.d.l.DeprecationIndexingComponent", "cluster.name": "openchallenges-elasticsearch", "node.name": "openchallenges-elasticsearch", "message": "Bulk write of deprecation logs encountered some failures: [[aAnjYooBlfoVQw1-QYdS UnavailableShardsException[[.ds-.logs-deprecation.elasticsearch-default-2023.09.05-000001][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[.ds-.logs-deprecation.elasticsearch-default-2023.09.05-000001][0]] containing [index {[.logs-deprecation.elasticsearch-default][_doc][aAnjYooBlfoVQw1-QYdS], source[{\"event.dataset\": \"deprecation.elasticsearch\", \"@timestamp\": \"2023-09-05T01:09:33,754Z\", \"log.level\": \"CRITICAL\", \"log.logger\": \"org.elasticsearch.deprecation.xpack.security.support.SecurityStatusChangeListener\", \"elasticsearch.cluster.name\": \"openchallenges-elasticsearch\", \"elasticsearch.cluster.uuid\": \"\", \"elasticsearch.node.id\": \"\", \"elasticsearch.node.name\": \"openchallenges-elasticsearch\", \"trace.id\": \"\", \"message\": \"The default behavior of disabling security on basic licenses is deprecated. In a later version of Elasticsearch, the value of [xpack.security.enabled] will default to \\\"true\\\" , regardless of the license level. See https://www.elastic.co/guide/en/elasticsearch/reference/7.17/security-minimal-setup.html to enable security, or explicitly disable security by setting [xpack.security.enabled] to false in elasticsearch.yml\", \"data_stream.type\": \"logs\", \"data_stream.dataset\": \"deprecation.elasticsearch\", \"data_stream.namespace\": \"default\", \"ecs.version\": \"1.7\", \"elasticsearch.event.category\": \"security\", \"event.code\": \"security_implicitly_disabled\", \"elasticsearch.http.request.x_opaque_id\": \"\" }\n]}]]]]]", "cluster.uuid": "wZ2xG9a6SgaKDagsEcmNQg", "node.id": "ZtDSIXS0SUik_RGVJUdPWA"  }

Expected behavior
No response
Anything else?
Experienced when working on #2079
Commit ID
No response
Are you developing inside the dev container?

[X] I am using the dev container

Code of Conduct

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

There is almost no space left on the EC2 instance:
vscode@7047b27f8ebb:/workspaces/sage-monorepo$ df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay          80G   74G  6.1G  93% /

Conclusion
After making some space, the OC stack started successfully, including the Elasticsearch nodes.


Chore/remove latest address balance materialized view

Removed the need for latest_stake_address_balance materialized view. The query runs nearly as fast as the original one based on the MV. The MV latest_stake_address_balanceis (as far as I know) not needed any more at all in the explorer services. In another PR in consumer schedules I will remove it there as well.
What I did:

Implemented StakeAddressBalanceRepository incl. the query to get StakeQuantityByAddress
Removed latestStakeBalance
Changed tests to fit the new functionality

Outdated due to branch 1.5.0


MSGraphClient get...then does not return essential error details (Retry-After header)

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
Be able to use the graph client in a promise design pattern fully.
Observed Behavior
When using the graph client in a promise pattern, we do not give  the "get" call a handler function as parameter. instead we append a "then" and "catch" handlers to the return value of the "get" call.
In the event of a throttling error, as described here:
https://developer.microsoft.com/en-us/graph/docs/concepts/throttling
The server will return an indication that our request was throttled - so far so good.
But, it will also return a "Retry-After" response header that will indicate how many seconds the app should wait before making any more requests to the server.
There is no way to get this parameter when using a get.then.catch pattern, since it is coming back in the response header, which we do not have access to in the promise results.
So, anyone who wants to be aware and handle a throttling scenario CANNOT currently use the promise patterns. Even if you are making a single simple request, another component might be provoking a throttle issue that might affect you so everyone should handle this scenario.
Steps to Reproduce
Make a lot of requests to the graph API to trigger a throttling error.
Try to get the "retry after" value using the promise pattern.
In my humble opinion:
A good solution would be to give us this value in the "catch" of the promise.
A best solution would be if the graph client would handle this silently and wait for the suggested duration and retry our request automatically...
Please let me know if this makes sense... a bit hard to explain I think, but I did my best.

Actually, if anyone is looking into this... getting this header value is not possible even with the callback pattern.
Gettign the rawResponse object in the callback, we cannot access the "Retry-After" header in Javascript.
it comes back from the server, I can see it in the network monitoring tool, but not in code.
calling:
rawResponse.xhr.getResponseHeader("Retry-After")
will produce an error:
VM13198:1 Refused to get unsafe header "Retry-After"
Using google chrome, latest version.


⚠ ClamAV has degraded performance

In ed431bd, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 95 ms

Resolved: ClamAV performance has improved in 3facbb4.


[Chore]: authorization.InfoParser should return NotAuthenticatedError only

Background
In order to match the CF API behaviour as closely as possible we should make the following distinction:

return a NotAuthenticatedError (maps to 401 Unauthorized) under the following circumstances:

no credentials are passed in
the credentials are malformed
the credentials are not valid (for example a token or cert by an untrusted issuer)
the credentials have expired

return a InvalidAuthError (maps to 403 Forbidden) when the credentials are valid, but the user does not have permission to perform the requested operation.

Action to take
Change the authorization.InfoParser to conform to the above convention. As of today it does return InvalidAuthError un a couple of places.
Impact
We are consistent with the CF API
Dev Notes
No response

Addressed by #288


ExpressionProperties model change doesn't trigger modelChange event

I am building the form and having the validation and synchronization between them in the form config via expressionProperties. Noticed, when model updated via this option, the event is not fired.
Example: https://stackblitz.com/edit/angular-xm4ucn-uiden7

we may end into in circular calls :thinking: :
1- model-changes fired execute expressions (step 2)
2- expressions fire model-changes (step 1)

This issue has been fixed and released as part of 5.10.23 release.
Please let us know, in case you are still encountering a similar issue/problem.
Thank you!


Running Docker network driver plugin as a Docker container

Does Docker support running a Docker network driver plugin as a container?
I am running a networking plugin as a container within Docker.  I'm using etcd as a cluster store.  With containers running and networked with my plugin, I end up running into an issue when I stop and restart the Docker daemon.
With Docker running, I start my network plugin, then I run the following:
$ docker network create --driver calico --subnet=<IP_ADDRESS>/24 my_net
1542184fac9c6b7753452ca2342eb25c8e7f8f2246f840ec5c7537922e45f368
$ docker run --net my_net --name test_container -tid busybox
5f5789cd58ac897bd5d92301427d66745f8515d99f9ef95d6c1885faf2ae1e3c

When I stop the Docker daemon:

All Docker containers stop (as expected)
The endpoint information for each container is not released/cleaned up (unexpected?)

Since the network plugin container is stopped, the plugin cannot clean up endpoint data. The etcd datastore still contains endpoints under /docker as well (possibly because Docker cannot communicate with the network plugin and just stops endpoint cleanup upon finding this?)
When I restart the Docker daemon:

The endpoint information for each container is not released/cleaned up
Starting a previously running Docker container fails with error:

$ docker start test_container
Error response from daemon: service endpoint with name test_container already exists
Error: failed to start containers: test_container

Is there a way to run the Docker daemon with any additional parameters to specify a containerized network plugin?  Will Docker support this at some point if not?

BUG REPORT INFORMATION
Output of docker version:
Client:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:40:36 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:40:36 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 5
 Running: 2
 Paused: 0
 Stopped: 3
Images: 3
Server Version: 1.11.0
Storage Driver: devicemapper
 Pool Name: docker-253:0-525078-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 296.4 MB
 Data Space Total: 107.4 GB
 Data Space Available: 38.3 GB
 Metadata Space Used: 987.1 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.146 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2015-12-01)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host bridge null calico
Kernel Version: 3.10.0-327.10.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.797 GiB
Name: calico-mesos-02
ID: FTZU:V6XJ:RPIJ:I77H:KOZN:YO3A:BVNB:GSWD:OWPE:W2YH:KW6V:Z7V2
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Cluster store: etcd://<IP_ADDRESS>:2379

Steps to reproduce the issue:

Run Docker
Start networking plugin as Docker container
Create network
Create container

uname output:
Linux calico-mesos-02 3.10.0-327.10.1.el7.x86_64 #1 SMP Tue Feb 16 17:03:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Ping @anusha-ragunathan @tiborvass (cc @mavenugo).

@TrimBiggs we added a workaround for such issues via the docker network disconnect -f {network} {container_name}. In this case, docker network disconnect -f my_net test_container. If you start the container after the forced disconnect, the container must come up fine.
Docker daemon tries its best to perform the stale endpoints (left in the kv-store due to ungraceful daemon shutdown) when the daemon starts. But if the kv-store & plugins are containerized, it could so happen that during the bootup, these containers were not up and that will prevent the daemon to perform full cleanup of these stale endpoints.
Such issues will ideally be addressed when these plugin containers are treated special (as system containers) and brought up sooner than other containers.
Can you try the forced disconnect option and let us know if that works ?

See also https://github.com/docker/libnetwork/issues/882

@mavenugo is there a new proposal for "system containers"?  #18724 was closed.

@mavenugo I tried the following:

Create test_con on network test_net
Create test_con2 on network test_net2

I wasn't sure when to disconnect either from the network, so I:

Disconnected test_con from the test_net
Restarted docker
Disconnected test_con2 from test_net2

Results below:
$ docker network disconnect -f test_net test_con

$ sudo systemctl stop docker
$ sudo systemctl start docker

$ docker ps         # libnetwork plugin driver is running
CONTAINER ID        IMAGE                           COMMAND               CREATED             STATUS              PORTS               NAMES
b73c019c2948        calico/node-libnetwork:latest   "./start.sh"          10 minutes ago      Up 25 seconds                           calico-libnetwork
bc94ae8b3069        calico/node:latest              "/sbin/start_runit"   10 minutes ago      Up 25 seconds                           calico-node

$ docker start test_con
Error response from daemon: rpc error: code = 2 desc = "oci runtime error: exit status 1: time=\"2016-04-22T12:20:36-04:00\" level=fatal msg=\"no sandbox present for 86cbbc1689b92831383572d5f19bec20e844490c4260d76d49dc2bffd799d13f\" \n"
Error: failed to start containers: test_con

$ docker start test_con2        # (expected to fail given original issue)
Error response from daemon: service endpoint with name test_con2 already exists
Error: failed to start containers: test_con2

$ docker network disconnect -f test_net2 test_con2
$ docker start test_con2
Error response from daemon: rpc error: code = 2 desc = "oci runtime error: exit status 1: time=\"2016-04-22T12:20:49-04:00\" level=fatal msg=\"no sandbox present for fa87ae4579bbc45fc39034c1ef615b458acd2452be26417e525b05980b559436\" \n"
Error: failed to start containers: test_con2

I think it is expected to have at least one of the two containers start normally after having disconnected each from their networks.
I then removed the containers entirely and restarted each:
$ docker rm -f test_con2
test_con2
$ docker run --net test_net2 --name test_con2 -tid busybox
75858d9b00464f4273cacca0c00e176f2c7951c3cba2854bbbc5c1e6f411b03f
docker: Error response from daemon: service endpoint with name test_con2 already exists.

$ docker rm -f test_con
test_con
$ docker run --net test_net --name test_con -tid busybox
7095a495e544b55d785e2fe86fa9e306ab6fb779f9db297db22ce568a7f03133

Looks like I was able to create a new test_con container (disconnected before stopping docker), but I could not create a new test_con2.  I don't think either of these is actually "right" since I think I should have been able to just start the containers after disconnecting the networks above instead of recreating them, but I think this is still useful info.

I've been thinking about this a bit more.
The workaround isn't really that useful:

This action would have to be run on every container in the cluster
You have to know the name/id of every container as well as the name of the network of that container

I think one of the following options could be a better solution, alongside or before system containers are implemented:

Docker daemon could periodically sync with the driver in the container (check if it's running and resync)
Provide a docker command to resync with the network plugin
Provide an API into Docker from the remote network driver plugin to allow the plugin to resync with docker at the request of the driver

What do you think?

Referencing #20363 which talks about some other requirements to support plugins inside containers.

Any more thoughts on this? Is anything in the works to improve network plugin support?

@TrimBiggs Yes, see #20363 as @bboreham mentioned.

Yes, I had also commented on that issue, but I have not seen any PR or work in progress for the change, so I wanted to check in. Thanks for the note.

Plugin support for network plugins has been added in docker 1.13, see https://github.com/docker/docker/blob/master/docs/extend/index.md. I don't think the calico driver has been updated for the new plugin infrastructure yet though
I'll close this issue because this is now supported, but feel free to comment

That page says nothing about network plugins.

Network plugins are supported in Pluginv2. A sample network plugin (albeit being a mock plugin) is available at https://hub.docker.com/r/tiborvass/test-docker-netplugin. Basic integration test available at https://github.com/docker/docker/blob/master/integration-cli/docker_cli_network_unix_test.go#L773


[Docs] Improve testing for example ORMs

Background: https://airtable.com/tblD3oZPLJgGhCmch/viw1DKmbKhg2MIECH/recMTtPYZv1Q9Wcuc
Description: CockroachDB will replace the examples ORMs code with MovR. This will include a full test suite for Movr than can be run via an API for each language.
Team: Andrew Woods, Rafi Shamim, Eric Harmeling, Richard Loveland

Dup of https://github.com/cockroachdb/docs/issues/6259.


logging system is needed?

There is room for improvement in the way qiskit prints debugging info.
In the current situation some API calls have a silent argument (eg. QuantumProgram.compile ) and some other calls have a verbose argument (eg. _mapping.swap_mapper), with opposite meaning.
Debugging is already painful enough :) A better logging system would also make easier to get debug infor for bug reports. Something like logging is probably the way to go.

Hi Luciano, I already have filed an issue (#88) about this. You are right, it's a low priority bug and we think it's a good candidate for new contributors.


Fix a few PHP warnings - Reloaded

Continuation of #3117
I'll add fixes to this pull request as soon as I find them, feel free to merge this PR when you want :wink:

https://github.com/mlocati/concrete5/commit/7b342d50ec6b876dbdf7cd2f9ff0d6333351bc11 is a bugfix

Thanks –  but this pull request is too large to verify. Can we keep these smaller? Normally this wouldn't matter but there have been times in the past where some seemingly minor code change made for purity or stylistic reasons has broken something.

I made a lot of separated commits to let you understand everything.
"PSR" commits have been generated automatically with php-cs-fixer without any manual changes (eg I didn't replaced any self with static like I did in an old PR that caused problems), so they are really safe.
If BTW you prefer to review one pull request at a time instead of reviewing one commit of this PR at a time, I can split this PR...

I splitted this pull request in there pull requests:
#3163
#3164
#3165
#3166
#3167
#3168
#3169
#3170
#3171
#3172
#3173
#3174
#3175
#3176
#3177
#3178
#3179
#3180
#3181
#3182
#3183
#3184


Update package.json: changed pattern "./" to "./*"

On Angular when executes command 'ng build --prod':

Generating browser application bundles...(node:16716) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at {{APP_PATH}}\node_modules\tslib\package.json.
Update this package.json to use a subpath pattern like "./*".
(Use node --trace-deprecation ... to show where the warning was created)

I sent this change to fix the deprecation on new apps, this is a minor change. I don't undestand why test CI for 14.x failed.

On Angular 11 + Node v15

On Angular when executes command 'ng build --prod':

Generating browser application bundles...(node:16716) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at {{APP_PATH}}\node_modules\tslib\package.json.
Update this package.json to use a subpath pattern like "./*".
(Use node --trace-deprecation ... to show where the warning was created)

Any update on this ? @Neizan-93 Can you rebase on master and after can we merge this. I having this warning with node 15.

I just closed #139 as a duplicate of this. In #139, the author points to postcss/postcss#1455, which tried to solve the deprecation in the same way. From the linked PR it sounds like this breaks NodeJS 12.x and there are still issues with it:

https://github.com/postcss/postcss/issues/1455#issuecomment-722502548 (indicates errors in NodeJS 12, suggests adding both mappings)
https://github.com/postcss/postcss/issues/1455#issuecomment-724793283 (seems to indicate using both mappings may reintroduce the warning in NodeJS 15)

@weswigham any thoughts?

I just closed #139 as a duplicate of this. In #139, the author points to postcss/postcss#1455, which tried to solve the deprecation in the same way. From the linked PR it sounds like this breaks NodeJS 12.x and there are still issues with it:

https://github.com/postcss/postcss/issues/1455#issuecomment-722502548 (indicates errors in NodeJS 12, suggests adding both mappings)
https://github.com/postcss/postcss/issues/1455#issuecomment-724793283 (seems to indicate using both mappings may reintroduce the warning in NodeJS 15)

@weswigham any thoughts?

@orta We are skipping esm node modules for NodeJS 12, so we're not seeing a possible error due to the fact NodeJS 12 supports subpath exports but not subpath patterns.

@orta We are skipping esm node modules for NodeJS 12, so we're not seeing a possible error due to the fact NodeJS 12 supports subpath exports but not subpath patterns.

I've done some research and cannot verify the issue mentioned in https://github.com/postcss/postcss/issues/1455#issuecomment-722502548. With "./*": "./*", NodeJS 12.7 seems to work just fine (as long as --experimental-modules are passed to NodeJS).
The test case I used was:
// index.mjs
async function main() {
    // (a)
    try {
        const tslib1 = await import("tslib");
        console.log("default" in tslib1 ? "CommonJS" : "ESM");
    }
    catch (e) {
        console.error(e.name, e.message);
    }

    // (b)
    try {
        const tslib2 = await import("tslib/tslib.js");
        console.log("default" in tslib2 ? "CommonJS" : "ESM");
    }
    catch (e) {
        console.error(e.name, e.message);
    }

    // (c)
    try {
        const tslib3 = await import("tslib/tslib.es6.js");
        console.log("default" in tslib3 ? "CommonJS" : "ESM");
    }
    catch (e) {
        console.error(e.name, e.message);
    }

    // (d)
    try {
        const tslibpkg = await import("tslib/package.json");
        if (tslibpkg.default.name !== "tslib") throw new Error ("Unexpected result");
        console.log("ok");
    }
    catch (e) {
        console.error(e.name, e.message);
    }
}

main();

Results:

Version
Mapping
(a)
(b)
(c)
(d)
Note

12.7.0
"./"
CommonJS
CommonJS
SyntaxError (1)
ok

12.7.0
"./*""
CommonJS
CommonJS
SyntaxError (1)
ok

12.18.3
"./"
ESM
CommonJS
SyntaxError (1)
TypeError (2)
without --experimental-json-modules

12.18.3
"./"
ESM
CommonJS
SyntaxError (1)
ok
with --experimental-json-modules

12.18.3
"./*"
ESM
Error (3)
Error (3)
Error (3)
without --experimental-json-modules

12.18.3
"./*"
ESM
Error (3)
Error (3)
Error (3)
with --experimental-json-modules

15.4.0
"./*"
ESM
CommonJS
SyntaxError (1)
TypeError (2)
without --experimental-json-modules

15.4.0
"./*"
ESM
CommonJS
SyntaxError (1)
ok
with --experimental-json-modules

NOTES:

SyntaxError Unexpected token export - Loader tried to load ESM module as CommonJS
TypeError Unknown file extension ".json" - Loader won't load .json without --experimental-modules
Error Package subpath '?' is not defined by "exports" - Loader won't load any subpath.

The most common use case for tslib is to just import the default export: Playground link. That means:

12.7.0 - Fails in both cases because its importing the CommonJS file, and thus all the exports are actually on the default export.
12.18.3 - Succeeds in both cases
15.4.0 - Succeeds in both cases

However, subpath exports are trickier:

12.7.0 - Only loads as CommonJS in both cases
12.18.3

"./" - Only loads subpath exports as CommonJS (fails for tslib/tslib.es.js, probably due to file extension)
"./*" - Doesn't work at all.

15.4.0

"./" - Only loads subpath exports as CommonJS (fails for tslib/tslib.es.js, probably due to file extension), shows deprecation warning
"./*" - Only loads subpath exports as CommonJS (fails for tslib/tslib.es.js, probably due to file extension)

The only consistency between 12.18 and 15.4 is "./", switching to "./*" would break anyone still using Node12 and subpath exports. At this time I'm not sure how impactful that break would be.

I've done some research and cannot verify the issue mentioned in https://github.com/postcss/postcss/issues/1455#issuecomment-722502548. With "./*": "./*", NodeJS 12.7 seems to work just fine (as long as --experimental-modules are passed to NodeJS).
The test case I used was:
// index.mjs
async function main() {
    // (a)
    try {
        const tslib1 = await import("tslib");
        console.log("default" in tslib1 ? "CommonJS" : "ESM");
    }
    catch (e) {
        console.error(e.name, e.message);
    }

    // (b)
    try {
        const tslib2 = await import("tslib/tslib.js");
        console.log("default" in tslib2 ? "CommonJS" : "ESM");
    }
    catch (e) {
        console.error(e.name, e.message);
    }

    // (c)
    try {
        const tslib3 = await import("tslib/tslib.es6.js");
        console.log("default" in tslib3 ? "CommonJS" : "ESM");
    }
    catch (e) {
        console.error(e.name, e.message);
    }

    // (d)
    try {
        const tslibpkg = await import("tslib/package.json");
        if (tslibpkg.default.name !== "tslib") throw new Error ("Unexpected result");
        console.log("ok");
    }
    catch (e) {
        console.error(e.name, e.message);
    }
}

main();

Results:

Version
Mapping
(a)
(b)
(c)
(d)
Note

12.7.0
"./"
CommonJS
CommonJS
SyntaxError (1)
ok

12.7.0
"./*""
CommonJS
CommonJS
SyntaxError (1)
ok

12.18.3
"./"
ESM
CommonJS
SyntaxError (1)
TypeError (2)
without --experimental-json-modules

12.18.3
"./"
ESM
CommonJS
SyntaxError (1)
ok
with --experimental-json-modules

12.18.3
"./*"
ESM
Error (3)
Error (3)
Error (3)
without --experimental-json-modules

12.18.3
"./*"
ESM
Error (3)
Error (3)
Error (3)
with --experimental-json-modules

15.4.0
"./*"
ESM
CommonJS
SyntaxError (1)
TypeError (2)
without --experimental-json-modules

15.4.0
"./*"
ESM
CommonJS
SyntaxError (1)
ok
with --experimental-json-modules

NOTES:

SyntaxError Unexpected token export - Loader tried to load ESM module as CommonJS
TypeError Unknown file extension ".json" - Loader won't load .json without --experimental-modules
Error Package subpath '?' is not defined by "exports" - Loader won't load any subpath.

The most common use case for tslib is to just import the default export: Playground link. That means:

12.7.0 - Fails in both cases because its importing the CommonJS file, and thus all the exports are actually on the default export.
12.18.3 - Succeeds in both cases
15.4.0 - Succeeds in both cases

However, subpath exports are trickier:

12.7.0 - Only loads as CommonJS in both cases
12.18.3

"./" - Only loads subpath exports as CommonJS (fails for tslib/tslib.es.js, probably due to file extension)
"./*" - Doesn't work at all.

15.4.0

"./" - Only loads subpath exports as CommonJS (fails for tslib/tslib.es.js, probably due to file extension), shows deprecation warning
"./*" - Only loads subpath exports as CommonJS (fails for tslib/tslib.es.js, probably due to file extension)

The only consistency between 12.18 and 15.4 is "./", switching to "./*" would break anyone still using Node12 and subpath exports. At this time I'm not sure how impactful that break would be.

@orta We are skipping esm node modules for NodeJS 12,

Interesting, I didn't know it was supported in 12 TBH.
I think it's pretty reasonable to assume here that the 12.18.x versions had a bug and we can add release notes stating they can update to a later version of 12.x to fix issues?

@orta We are skipping esm node modules for NodeJS 12,

Interesting, I didn't know it was supported in 12 TBH.
I think it's pretty reasonable to assume here that the 12.18.x versions had a bug and we can add release notes stating they can update to a later version of 12.x to fix issues?

It was experimental in 12. I think this change is fine.

It was experimental in 12. I think this change is fine.

This really needs to be merged if possible @JonSenpai, there are quite a few dependencies that rely on tslib, and currently I'm facing a series of deprecation warnings during every build. I can just suppress it but it's not ideal :(

This PR should solve #152. Is there anything still blocking this from being merged?
Sidenote: Why is the ./* export even needed? All .js files in this repository are already being referenced by the conditional exports in the . path. Is there some other file that dependencies require from tslib?

@csvn interesting approach using both syntaxes or only package.json.
Running the test script that @rbuckton on the current node version (17):

Version
Mapping
(a)
(b)
(c)
(d)

17.0.0
"./package.json": "./package.json"
ESM
Error⁵
Error ⁵
TypeError ²

17.0.0
none
ESM
Error⁵
Error ⁵
TypeError ²

17.0.0
"./*": "./*"
ESM
CommonJS
SyntaxError ¹
TypeError ²

@rbuckton do we know when the next release will be? It seems the last one was in August.

Current code is:
"./*": "./*", "./": "./"
VS Code seems to still compain, saying "Property ./ is not allowed."
Maybe should just be ``"./": "./"` ?? ie. delete the last line https://github.com/microsoft/tslib/blob/c827964226e85118e2fd35b1cc68d4a5ad867f39/package.json#L36 (and the preceeding comma)

./ is for old node, it's deprecated in new node, and thus not allowed by the json schema. It's safe to ignore. (New node will always match the * containing case first and so should never hit the deprecation warning for still having ./).

./ is for old node, it's deprecated in new node, and thus not allowed by the json schema. It's safe to ignore. (New node will always match the * containing case first and so should never hit the deprecation warning for still having ./).

Ah yes, now I get it. It's for backwards compatability. I'll ignore the VS Code warning. Thanks. Please ignore me :)


[WIP] Resolving Brakeman vulnerabilities

This follows on from #72 and fixes the vulnerabilities that were identified by the Brakeman gem.
Additionally, build will continue to fail until all vulnerabilities (both errors and warnings) are resolved.


Byte size of generated address inconsistent in test

Setup

elixir 1.7.3
Mac os
Erlang/OTP 21

Bug (?)
Sometimes when I test I get this:

How to reproduce
I can't reproduce it consistently. I have tried with the seed with which the test fails, but then it passes. My guess is that it is how byte_size counts the bytes in a low level way, because every other test passes perfectly.
Just wanted to open up the discussion to see if someone else can reproduce this.

Wrong repo, my bad


Direct Link to Package

Hi - is there a direct link to install the package?  The deploy tool is not working for me.  Keep getting Oauth errors, even after removing all Oauth settings for Github.  Can you please provide the direct link to install?
Thanks!

LT

There you go : https://appexchange.salesforce.com/listingDetail?listingId=a0N3A00000EiRUnUAN


Question - Is It Safe To Remove This Custom Integration?

@perdue - thanks for all your help with this.
I noticed your changes are finally integrated into HA 2023.7.0
Have you tried this yet? Is it now safe to remove your custom integration?
Thanks in advance for your input.

Thanks for letting me know!
I have been waiting for my commit to make it into a release because I am using the save recent clips service.  So I didn't update my Home Assistant server with any of the June releases.
The 2023.7.0 includes this service, so I believe you can safely remove the custom integration.  If you are not using the "save recent clips" service, then any of the June releases would have worked for you since they included the blinkpy updates already.

Thanks for getting back to me. I guess I just delete the custom folder and restart?

That will remove the custom integration.  You will still need to update to the 2023.7.0 version of core though.

I've already updated to that version. I'll rename the folder and restart to play it safe.
I'll let you know shortly how it goes.

Was it a good outcome?  No surprises?

Sorry for the late response. We're in the middle of major thunderstorms here and I was waiting for a break to test this since my camera is outside.
I just did the restart and while it missed the first clip, after waiting a bit it seems to be working again with the custom folder renamed so I think all is properly integrated now.
Thanks again for your work on this.

I just removed my custom integration and deployed the most recent HA release.  All looks good.


Update Actvities.bookingUrl to a component type that supports the modal

Create a component type named booking under singltype category and link it to Actvities.booking. To support the above modal data. Actvities.bookingUrl should be removed.

@gautamkrishnar Singletype always can have only one way relation. Also is the link constant.

@akhilmhdh I meant to create component type not single type

closed by #6


WIP: Hyperspace Port

This PR contains a few changes necessary to get Beaker to work with the upcoming Hyperspace release.

[x]  Connects to an external server
[x] Launches a Beaker-managed server
[x] The peers backend is updated to use RemoteNetworker peers
[x] The peersockets backend is updated to the use Peersockets 1.0 + handles peer aliasing
[ ] Hyperdrive errors propagate correctly (No update available errors suppressed)
[ ] Temporary --no-migrate flag has been removed

Merged via a separate rebased branch


Travis CI: Configure HOWIS_BASIC_AUTH et al

HOWIS_BASIC_AUTH is missing, the tests complain.

As discovered in #236, at some point Travis CI added new security restrictions for pull requests.
While these security restrictions make sense, they do make it significantly more difficult to test pull requests, because only pull requests made from the same repo have access to encrypted environment variables.
In #237, I made it so that the exceptions are thrown when the environment variables are used, not at the start, so it at least shows proper results for some tests.
The two environment variables used are HOWIS_BASIC_AUTH and HOWIS_GITHUB_TOKEN. Note that issue #241 (Refactor Sources::Github.basic_auth) may affect the environment variables.

Short term, that approach (or something very similar) seems like the best option.
Long term, I'm not sure how I want to approach. Doing that means there are two different sets of tests ran depending on the environment, despite all used environment variables being required for the program to function correctly. And that makes this approach feel like a kludge.


code new

Contains
Brief description of what the PR does like "Fixes #12345"
How to test
Brief description of how to test / confirm this PR before merging
Outstanding before merging
If anything. You can use neat checkboxes! Feel free to delete if not needed

[ ] Need to consider use case x
[ ] Still have to adjust the wiki doc
[ ] Will need translation work
ram.txt

Low-effort Hacktoberfest attempt at last time, from the looks of it.


Clippy will now chase the ball

CC @marcduiker

@marcduiker It would be a nice improvement to change metallic_run_8fps.gif so that clippy were "leaning into" the run a bit more instead of just hopping sideways. If you're not too busy ofc.
For this PR, its just a copy of metallic_walk_fast

@marcduiker It would be a nice improvement to change metallic_run_8fps.gif so that clippy were "leaning into" the run a bit more instead of just hopping sideways. If you're not too busy ofc.
For this PR, its just a copy of metallic_walk_fast

Yes, I agree, I'll work on a real running version later this week 😊.


question regarding the dimensions of the 3D model and the detected objects

Hi,
I wasn't quite sure where to post a question so apologies for posting it here. If there is a dedicated forum/site where I can ask a question please to let me know and I will ask there in the future.
I was wondering if the 3D model and the detected object(s) must have exactly the same dimensions or if the 3D model would be "deformed" to fit the detected object(s)?
Thank you very much!

If I understand you correctly, you're wondering if the scale of the model needs to match that of the physical object. If that is the case then the answer is yes, . See our documentation here on that very subject, which says:

An app should always use a 1:1 object model for detection. The estimated scale should be close to 1 ideally within 1% error. An app could set ObjectQuery.MaxScaleChange to 0 or 0.1 to disable or enable scale estimation, and qualitatively evaluate the instance pose.

If I understand you correctly, you're wondering if the scale of the model needs to match that of the physical object. If that is the case then the answer is yes, . See our documentation here on that very subject, which says:

An app should always use a 1:1 object model for detection. The estimated scale should be close to 1 ideally within 1% error. An app could set ObjectQuery.MaxScaleChange to 0 or 0.1 to disable or enable scale estimation, and qualitatively evaluate the instance pose.

Amazing, this was exactly what I was asking. Thank you very much!


Release v0.1.0

Codecov Report

Merging #21 into master will decrease coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   65.41%   65.25%   -0.17%
==========================================
  Files          26       26
  Lines         613      613
  Branches       26       26
==========================================
- Hits          401      400       -1
- Misses        206      207       +1
  Partials        6        6

Impacted Files
Coverage Δ

...selection/package-table/package-table.component.ts
58.9% <0%> (-1.37%)
:arrow_down:

Continue to review full report at Codecov.

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


Create yaml for raku-asdf

Thanks @m-dango ! 😄
Just heads up - the yaml has been deprecated in favor of new feature-definition.json
you can see the list of them here
and the new generator instructions here
I have converted the yaml to the new json  in this PR   #239


Please add a suitable license

Thanks for the blog-post. The blog-post looks interesting, but before I can try out the code, will you please add a license to the repo

Done!


Bugfix

This is a bugfix for https://github.com/SammyK/LaravelFacebookSdk/issues/62
It will allow you to add something like:
protected static $graph_node_field_aliases = [
'location.name' => 'fb_location',
'location.id' => 'fb_location_id',
];

Thanks for the contribution @melhakim!
I recently added this feature to 1.3 branch but I did it in a slightly different way. Yours is more "Laravely". :)
Let me figure out a strategy for this and I'll probably merge this in. :)

Sorry this took so long to merge @melhakim! It'll be showing up in the next tag when I tweak a few other things. :)


Discuss if IAsyncBuffer should also implement IDisposable

As we found out: IAsyncEnumerable does not.

As IAsyncBuffer is mostly a wrapper around an IAsyncEnumerator (which only implements IAsyncDisposable) we think it's enough for IAsyncBuffer to implement IAsyncDisposable.


Allow a config file anywhere in the file tree

not really happy with the unit test, but didn't know how to do it better :/
not really happy with useDefaultConfigFile implementation either actually, but the obvious other way (do { ... } while (strlen($searchPath = dirname($searchPath)) > 1);) would skip /

from what I read in the doc it should work on windows too

Perhaps this commit resolve your problem.

Ah, the implementation in e51c588385caead5be1b8e84217c49e472fbde81 was going to be my next try. Will try to be faster next time ;)


New multisite strategy

Currently if you want to install multiple Drupal sites inside the VM, you have to edit a couple things, e.g.:
vagrant_synced_folders:
  - local_path: ~/Sites/drupal
    destination: /drupal
    excluded_paths: [".git/"]
    id: drupal
    type: rsync

apache_vhosts:
  - {servername: "{{ drupal_domain }}", documentroot: "{{ drupal_core_path }}"}

...also, the VM installs the site defined in drupal.make.yml by default, with no option to disable. It would be much more flexible and simple if there was a way to define multiple Drupal sites, and use a deployment_strategy per site (or something like that) to deploy it inside the VM.
That way, I could maybe have one site located at ~/Sites/my-site which has a .make.yml file to install, another site at ~/Sites/company-site which has a full Drupal codebase and would just need to be synced inside the VM...
I'm trying to think through the best syntax for this that would be the least complex, most flexible, and also not a pain to maintain inside Ansible and Vagrant (e.g. dynamically creating the apache_vhosts and vagrant_synced_folders variables).
Maybe something like the following:
drupal_sites:

  - servername: drupaltest.dev
    local_path: ~/Sites/my-site
    dest_path: /var/www/my-site
    deployment_strategy: drush_make
    makefile: drupal.make.yml
    sync_method: rsync

  - servername: drupaltest.dev
    local_path: ~/Sites/company-site
    dest_path: /var/www/company-site
    deployment_strategy: full_repository
    sync_method: nfs

Another potential advantage here is that we might be able to fabricate a Drush alias file for the entire VM from within the Ansible playbook, and either place it in the right place locally/automatically, or stick it inside the VM somewhere and let the user grab it if so desired.
I'd like the default configuration/example still to just install the latest version of Drupal core with a makefile (since that's my preferred method of site development/deployment these days anyways), but if it were this easy to have multiple sites inside one VM, I would be able to use the drupal-dev-vm for almost all my Drupal sites (at least all the ones that don't rely on exotic configurations or specific versions of software...).

isn't this re-inventing Aegir?
why not use Aegir 2.x + Hosting Git Platform ?
same result

Aegir, last time I checked, seems to be a large Drupal hosting system that requires a hosted website, some Drupal integrations, etc.
This dev VM is basically a VM with a bunch of software configured to make local Drupal development easier, and works with one or many drupal 6/7/8 sites at a time. I want to make the configuration for this VM simple and easy (mostly because I use it for most of my Drupal site dev work), and I'd hope someone could pick it up and bootstrap an entire Drupal development environment within 10-20 minutes of starting the README file.

I recommend you look at Aegir 2.x + Hosting Platform GIt extension and secondly Devshop
https://www.drupal.org/project/devshop
both are Aegir based solutions and do very much the thing you are trying to do

DevShop (and the entire platform that's being supported by ThinkDrop et all) is an interesting platform, but I think it's still far from what this VM (and the many others like it) are targeting—this is intended solely for efficient local development, and is not meant to give any kind of UI to that process.
In a way, I'd compare it to using a Git client (e.g. Tower) vs. using the Git cli (git * commands), but even that analogy isn't that relevant, since this VM is not intended in any way to be part of a larger universe of infrastructure orchestration.
I'm not going to discuss comparisons further in this issue—this issue is solely intended to look into making multiple Drupal site provisioning within drupal-dev-vm to be easier than it is currently, nothing more, nothing less.

We are about to convert our project to Ansible: https://github.com/GetValkyrie/valkyrie. We've got it to where when you generate sites in Aegir you get automatic drush aliases that go through an ssh tunnel into the VM amongst a bunch of other goodies. We should get with Vlad and you and all join forces...

@MatthewHager - Definitely! If nothing else, we should at least talk about sharing common roles for the most common setup tasks, since we're all using Ansible now.

Fixed with the above commit and the addition of a new build_from_makefile variable in config.yml.
I'm now using drupal-vm for all my local development—at least for all the sites where I don't have a separate Ansible playbook that deploys the exact same config/server build to local that is in production (e.g. all the servers I manage myself), and I'm trying to make this setup as simple and painless as possible.
Still a few documentation bits that need updating, and maybe I'll add a longer documentation example in the README, but that'll be in a new issue.


MavenAuthenticate@0 task is throwing error "cp: dest file already exists: /root/.m2/_settings.xml"

Note
The MavenAuthenticate@0 task is throwing  "cp: dest file already exists: /root/.m2/_settings.xml" while running the pipeline task on the Linux OS agent. The same task use to work until today morning without any errors.
Here is the complete error description from the task.
Starting: Maven Authenticate
Task         : Maven Authenticate
Description  : Provides credentials for Azure Artifacts feeds and external maven repositories
Version      : 0.175.1
Author       : Microsoft Corporation
Help         : https://go.microsoft.com/fwlink/?linkid=2099968
cp: dest file already exists: /root/.m2/_settings.xml
##[error]Failed cp: cp: dest file already exists: /root/.m2/_settings.xml
Finishing: Maven Authenticate
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: MavenAuthenticate@0
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment

Server - Azure Pipelines or TFS on-premises?

If using TFS on-premises, provide the version:

If using Azure Pipelines, provide the account name, team project name, build definition name/build number: Ingramcontent

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name: lvick8sd-dind-ado-build-agent-2

If using private agent, provide the OS of the machine running the agent and the agent version:

Issue Description
The MavenAuthenticate@0 task is throwing  "cp: dest file already exists: /root/.m2/_settings.xml" while running the pipeline task on the Linux OS agent. The same task use to work until today morning without any errors.
Task logs
Here is the complete error description from the task.
Starting: Maven Authenticate
Task         : Maven Authenticate
Description  : Provides credentials for Azure Artifacts feeds and external maven repositories
Version      : 0.175.1
Author       : Microsoft Corporation
Help         : https://go.microsoft.com/fwlink/?linkid=2099968
cp: dest file already exists: /root/.m2/_settings.xml
##[error]Failed cp: cp: dest file already exists: /root/.m2/_settings.xml
Finishing: Maven Authenticate
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
Here is the complete error description from the task.
Starting: Maven Authenticate
Task         : Maven Authenticate
Description  : Provides credentials for Azure Artifacts feeds and external maven repositories
Version      : 0.175.1
Author       : Microsoft Corporation
Help         : https://go.microsoft.com/fwlink/?linkid=2099968
cp: dest file already exists: /root/.m2/_settings.xml
##[error]Failed cp: cp: dest file already exists: /root/.m2/_settings.xml
Finishing: Maven Authenticate

Hey,
We just sent a fix for this issue. Is it currently resolved?

Thank you for the fix. The mavenAuthenticate task seems to be working fine.

Has this been deployed to Production?

Hi @sheikahamedali thanks, I'm closing it since it's resolved

Was this fix pushed to production? We are on version 0.177.1 of this task and seeing this exact issue intermittently in our pipeline.

@anatolybolshakov following up on my previous comment on this.
We were able to track this down to a race condition where multiple pipelines were running the maven authenticate task at the same time. Because this file is written to the %USERPROFILE%\.m2\settings.xml location (on Windows) this task can only be in active execution by one agent on a server a time. We host 5 agents per server in our organization.
Is it possible to write this file to the agent directory instead of a global location like the user profile? This would allow the settings file to be contained to the agent that is running it.
It may also be possible to add in a delay and a retry, with a failure occurring if the error happens again. It won't completely negate the issue, but it can avoid needing to jiggle the handle on the pipeline when it may succeed on re-run.

@Cadacious i can see the pull request on the above link is still open. Is there an estimated time of availability for this?
For me this also happens intermittently when more than 1 job is running parallel, because the settings.xml is in a shared linux folder.
I am getting the same error:
##[error]Failed cp: cp: dest file already exists: $HOME/.m2/_settings.xml
On some occasions the settings.xml was completely deleted after the pipeline run.

Please approve the PR of @Cadacious as the race condition is still happening from time to time, meaning we cannot run multiple agents on one host without issues.

The issue is closed but it is not merged back to master, the pull request related to this issue is still open. So closing this issue means the Azure Pipelines team is aware of the issue but do not wish to fix it?

I guess the comment of omokoh made them think the issue was resolved?
However, we are still getting these errors, so they are not...

@anatolybolshakov please reopen this issue because it is not resolved. Please merge the pull request above so we can use Maven Authenticate task.

@BalintKorcsmar629 i jumped the gun on submitting the PR and did not have permission from my employer to sign the document as this was discovered and developed in the course of my work. Someone else may need to submit the PR while I work through the red-tape.
However, upon further review of this after submitting the PR I was unsure if changing this file location would actually change the behavior of Maven to consume this file from the new location [$(Agent.TempDirectory)] instead of the default location.
@anatolybolshakov per your comment on the PR, does this need to be a customizable value? What scenarios would a user be bringing their own settings.xml when using the Maven Authenticate task?

@Cadacious could it make sense to add some switch input to allow turn on/off this behavior instead? The main concern here from our side is just to avoid unexpected behavior changes for existing logic, since some users can rely on this.

@anatolybolshakov I can definitely add that in to the PR. I am going through the approval process within my company to get permission to move forward.
I would have to see how other tasks implemented this kind of configuration option, but I would think a checkbox that is defaulted to unchecked that says "Use agent temp directory for settings.xml" or something along those lines would suffice here. That way the new behavior is opt-in and doesn't cause a breaking change.

@anatolybolshakov I can definitely add an input field to toggle this behavior. Would adding a group to contain this setting be needed or can it be visible by default (but not selected by default) with the currently available settings?
I would also use a MarkdownHelp value of "Utilizes $(Agent.TempDirectory) to avoid race condition when running multiple Maven Authenticate tasks on agents running as the same user on the same server" to give an indication to users why this may be needed.

@Cadacious I think it could make sense to put it to advanced group also - since useAgentTempDir input is already in this group.

Bump - is anyone still actively working on this one?

Any chance of someone picking this up?


Adding MoMs to main

What type of PR is this?
Add one of the following kinds:

subproject management

What this PR does / why we need it:
merge MoMs into main
Which issue(s) this PR fixes:
Special notes for reviewers:
Changelog input
Additional documentation

@bigludo7 can you please review this PR, so we can close it?
Thx!


Enable debug log for heat services

... so that we can check behavior of heat services more closely in CI. This also removes the default value for customServiceConfig following the other operators.

This file also needs to be updated: https://github.com/openstack-k8s-operators/heat-operator/blob/main/tests/kuttl/common/assert-sample-deployment.yaml


Version Update

Since there are some changes above v2.1.2 and version hasn't updated for months, is it the right time to make a new version and publish it on npm?

Closing the issue due to inactivity.


Flag to disable the counter total output

First of all, thanks for your library. It's nice & convenient to use
I have some change request regarding what the title says. Basically, I have a case where I want to show progress bars with an unknown total value. Currently, it's handled by outputting "?" as the total value on the counter:

I think it would be nice to have a flag to set the total to be "unbounded".

merged


_N is a macro on some platforms (e.g. ESP-IDF)

Hi again.  I'm now compiling GeographicLib on all of the embedded platforms we need to support.  One of these is ESP-IDF.
Unfortunately, in their toolchain, _N is defined as a macro in ctype.h:

...and hence DST.hpp fails to compile:
geographiclib/include/GeographicLib/DST.hpp:66:9: error: expected unqualified-id before numeric constant
   66 |     int _N;
      |         ^~

...as it has a private member variable named _N:
.
Would you consider changing this to something more name-spaced?

Or maybe just switch to lower case _n?

Argggh...  I've run into this problem (_[A-Z].* is reserved) already.  I'll push a fix on the devel branch and this will be in the next release.  (The fix will be _N -> _nN and _R -> _rR.)

Excellent: when is the next release due?

The changes are in commit b3bfff21.  No plans for a new release at this point.  I might make a minor release (to 2.3.1) if nothing else triggers the need for a release.

That's fine, we'll hang off devel for now then.
Many thanks for the swift response, closing this issue.

I recommend you take the diff for the latest commit to devel and apply this to the release branch.  The devel and main branches require slightly more complete "stuff" to build (e.g., tools to create the man pages).


(data-)Migration strategy for future updates

Is your feature request related to a problem?
Currently we have no way to migrate data if a new version comes out.
In this case we would always need to check within the code what exists and handle it and with this support old code/data-structures.
Describe the solution you'd like
We would need a migration strategy for things involving data stored in the users browser. I.e.

DexieDB
https://dexie.org/docs/Version/Version.upgrade()
Settings
...

Describe alternatives you've considered
Nothing. Currently we just have minor workarounds within the codes to i.e. handle string and number-types while this mostly should be only one of these.
Additional context
None
Are you working on this?
No

To back up this data, should  back up account-related information or transaction-related information ？

Closing as migrations are possible by now.


Implement the PCErr Message/object

Packet format

https://tex2e.github.io/rfc-translater/html/rfc5440.html

This feature was added in #66


For loop error in tour

Context: https://tour.golang.org/flowcontrol/1
the code has error => prog.go:7:7: syntax error: unexpected comma, expecting )
package main

import "fmt"

func main() {
	t := []string{"g", "h", "i"}
	for(_,file) in files {
		fmt.Println(file)
	}
}

That's not the code I see on flowcontrol/1. This is the code on that slide:
package main

import "fmt"

func main() {
	sum := 0
	for i := 0; i < 10; i++ {
		sum += i
	}
	fmt.Println(sum)
}

you (or something using the same computer and browser) changed the code. The playground (used in the tour) caches modification of the code examples. Clear the cache or use the tour reset button to restore the original code.
Closing here, since that's not a bug.


Distance and Direction WAB widget: uses same icon as the "My Location" widget

Widget
Distance and Direction
Version of widget
Bug or Enhancement
Repo Steps or Enhancement details
The Distance and Direction widget uses the same icon as the "My Location" widget. Recommend using a different icon that would make more sense for this widget and wouldn't confuse the user.

@elinz
Fixed please verify

@adgiles Verified fixed in build 17 Jan 2017 05:11. Closing issue.


Fix a bug in the template serving.

PR #880 introduced a bug in the template rendering for the notebook
UI where the name of the template was wrong (notebook instead of
nb).
This change fixes that.

LGTM


vivos (Vietnamese speech corpus) dataset not accessible

Describe the bug
VIVOS data is not accessible anymore, neither of these links work (at least from France):

https://ailab.hcmus.edu.vn/assets/vivos.tar.gz (data)
https://ailab.hcmus.edu.vn/vivos (dataset page)

Therefore load_dataset doesn't work.
Steps to reproduce the bug
ds = load_dataset("vivos")

Expected results
dataset loaded
Actual results
ConnectionError: Couldn't reach https://ailab.hcmus.edu.vn/assets/vivos.tar.gz (ConnectionError(MaxRetryError("HTTPSConnectionPool(host='ailab.hcmus.edu.vn', port=443): Max retries exceeded with url: /assets/vivos.tar.gz (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f9d8a27d190>: Failed to establish a new connection: [Errno -5] No address associated with hostname'))")))

Will try to contact the authors, as we wanted to use Vivos as an example in documentation on how to create scripts for audio datasets (https://github.com/huggingface/datasets/pull/4872), because it's small and straightforward and uses tar archives.

If you need an example of a small audio datasets, I just created few hours ago a speech dataset with only 300MB of compressed audio files https://huggingface.co/datasets/indonesian-nlp/librivox-indonesia. It works also with streaming (@albertvillanova helped me adding this functionality) :-)

@cahya-wirawan omg this is awesome!! thank you!

We have contacted the authors to ask them.


Resolve #869

Rework the documentation page
Fix the docs as described by the discussion in #869

Hey @pBouillon thanks for handing in that nice PR.
Just a side note from my side. It seems that you branched off from main and not stable. That is why we see some merge commits and additional changes.
Would it be possible to branch of ffrom stable?  Please do this only if you are confident with git.

Hey @linkdotnet!
Thanks for the hint, I misunderstood the issue and thought that I should target stable but didn't get that it implied starting from it too, I'll fix that 😄

I did not felt confident enough with the git commands you suggested so I did a separate PR to change the source and target branches on #877
I'll be closing this PR to avoid duplicates, let me know if I have to change anything else!


Update google-cloud-pubsub to 1.125.9

About this PR
📦 Updates com.google.cloud:google-cloud-pubsub from 1.107.0 to 1.125.9
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-pubsub" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.cloud", artifactId = "google-cloud-pubsub" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #372.


Upgrade cost go up

too small, you could think up some formula that would make costs go up exponentialy (some quadric equation or smth just not too steep or its not fun) also add multiple tiers of upgrades and track their cost and increase separately


Zoom In and Out shortcuts on macOS are not working (command + and command -)

Describe the bug
Zoom In and Out shortcuts on macOS are not working (command + and command -)
To Reproduce
Steps to reproduce the behavior:

Open Lens on Apple Macbook (I have a MacBook Pro 15" 2017 with macOS Big Sur 11.1)
Select 'command & +' or 'command and -) to zoom in/out

You will notice that nothing happens!
Expected behaviour
I would expect the UI to zoom in and out
Workaround
Steps to workaround the behaviour:

Select the 'view' menu
Select the 'Zoom in' or 'Zoom out' menu

Environment (please complete the following information):

Lens Version: 4.0.6
OS: macOS Big Sur 11.1
Installation method (e.g. snap or AppImage in Linux): dmg download.

You may need to hold shift down as well

You may need to hold shift down as well

@jim-docker Yes, that seems to have done the trick.  With all apps that I have worked with it seems that a simple command and + or - zooms in and out respectively.  However I have just come across this on the Apple website.
https://support.apple.com/en-gb/HT201236
Shift-Command-Minus sign (-): Decrease the size of the selected item.
Shift-Command-Plus sign (+): Increase the size of the selected item. Command-Equals sign (=) performs the same function.
For zooming out using the above command does not work, only 'Command and -' works.
So there are some issues/discrepancies with shortcut commands on macOS machines.

@jim-docker Yes, that seems to have done the trick.  With all apps that I have worked with it seems that a simple command and + or - zooms in and out respectively.  However I have just come across this on the Apple website.
https://support.apple.com/en-gb/HT201236
Shift-Command-Minus sign (-): Decrease the size of the selected item.
Shift-Command-Plus sign (+): Increase the size of the selected item. Command-Equals sign (=) performs the same function.
For zooming out using the above command does not work, only 'Command and -' works.
So there are some issues/discrepancies with shortcut commands on macOS machines.

Thanks, Command-+ is a bit ambiguous since to enter '+' you must shift the key. We'll consider supporting Command-Equals, like many other apps seem to do.

Thanks, Command-+ is a bit ambiguous since to enter '+' you must shift the key. We'll consider supporting Command-Equals, like many other apps seem to do.


Chat is not closing for other user if one user logout

Description
If two users has logged in anonymously for chat let us say X and Y, if X logout without closing the chat, the chat is not closing automatically for Y and they will never know if the X has logged out.
Ideally if the X has logged out it should close the chat for Y also, if the login is anonymously.
Screenshots
No response
Additional information
No response
🥦 Browser
Google Chrome
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

Hi, I'd like to work on this issue can you please assign this to me

well give it a go @afeefuddin, make sure you follow the rules 👉🏽here👈🏽, else your PR will not be accepted and will be closed. Good Luck

@Dun-sin Thanks for assigning the issue, I will follow all the guidelines.


Exception in Rimworld 1.4 in options menu

On opening mod options menu in 1.4 this message is spammed to log:
Exception filling window for RimWorld.Dialog_ModSettings: System.MissingMethodException: void Verse.Listing_Standard.CheckboxLabeled(string,bool&,string)
  at EnhancedDevelopment.EnhancedOptions.Mod_EnhancedOptions.DoSettingsWindowContents (UnityEngine.Rect inRect) [0x00000] in <b8e19ab4d64748a199bfa228c277e920>:0
  at RimWorld.Dialog_ModSettings.DoWindowContents (UnityEngine.Rect inRect) [0x00073] in <8c412d4a16f94d4cb337e846f2dee469>:0
  at Verse.Window.InnerWindowOnGUI (System.Int32 x) [0x001d3] in <8c412d4a16f94d4cb337e846f2dee469>:0
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

The mod options menu is then blank.

I have fixed this in my fork. It also supports v1.5.


fix: extracting and storing only the hostname from http.url

@ankitnayan You missed updating: https://github.com/SigNoz/opentelemetry-collector-contrib/blob/9fd36aac9939128c279e4cff974f4af03d708f32/exporter/clickhouseexporter/clickhouse_exporter.go#L141

@ankitnayan You missed updating:
https://github.com/SigNoz/opentelemetry-collector-contrib/blob/9fd36aac9939128c279e4cff974f4af03d708f32/exporter/clickhouseexporter/clickhouse_exporter.go#L141

thinking of keeping http.url intact but changing only for externalUrl which is used to plot metrics.

Filtering http.url would help reduce query time and also fix UI of trace filter page

for trace filtering page...but for trace detail page the complete url is helpful..we need to find a better solution here

@makeavish create-metrics is the latest branch right?

Yes

@ankitnayan Tag Value suggestion changes along with clickhouse v2 is in https://github.com/SigNoz/opentelemetry-collector-contrib/tree/signoz-v0.43.0
We have to update this PR changes to https://github.com/SigNoz/opentelemetry-collector-contrib/tree/signoz-v0.43.0 branch too


Output Format Tweaks

->trans info called from auditchannel now shows seconds and ms in the bid info. I also noticed and fixed the date format from d/m/y to m/d/y
->cardinfo now rounds cards' average rating to two decimal places.
One of these commits says "claim update" but that was an accident and was "rolled back" (overwritten by uploading the correct file versions, because I couldn't find any "revert to commit" button on the github website >_>;)

fixed the date format from d/m/y to m/d/y
d/m/y is better
This has a bunch of old PRs


fix the SBG namespaces

The lack of trailing slash broke view.commonwl.org

Thanks @mr-c. I am working on the dev branch only at the moment and I've also started to tidy up those sevenbridges schema references. Depending on how far I got I might pull your PR in or not.

Done on dev already. I will merge dev into master soonish. @mr-c @hmenager

Thanks!