Unknown log opt 'syslog-tag' for syslog log driver

My environment:

OSX 10.11.6
Docker version 1.12.0-rc4, build e4a0dbc, experimental

Docker info:
Ismars-iMac:~ ismarslomic$ docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 61
Server Version: 1.12.0-rc4
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 47
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.15-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.788 GiB
Name: moby
ID: 6KZS:ZCKP:VICU:BVCX:UBPK:GYBT:5UPI:G5QY:4LCZ:4RV6:EMJB:R5ON
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 16
 Goroutines: 28
 System Time: 2016-07-23T12:23:09.78445108Z
 EventsListeners: 1
No Proxy: *.local, 169.254/16
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8

Steps to reproduce error:

git clone https://github.com/Accenture/adop-docker-compose
./quickstart.sh -t local -m adop-machine -u ismar -p slomic

Error displayed in console (after pulling Docker images is done):
ERROR: for sensu-rabbitmq  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for sensu-client  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for nexus  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for gerrit-mysql  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for gerrit  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for jenkins-slave  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for sensu-api  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for sonar  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for selenium-hub  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for sensu-redis  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for selenium-node-chrome  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for proxy  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for ldap  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for selenium-node-firefox  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for sensu-uchiwa  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for jenkins  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for sonar-mysql  unknown log opt 'syslog-tag' for syslog log driver

ERROR: for sensu-server  unknown log opt 'syslog-tag' for syslog log driver
ERROR: Encountered errors while bringing up the project.

Renaming log-opt option from syslog-tag to tag in /etc/logging/syslog/default.yml resolves this issue. I guess this is because Im running later version of Docker then this project? If so, README shall state which Docker version shall be installed as prerequisite!

@ismarslomic you are right about replace the syslog-tag with tag as of docker version 1.12 syslog-tag has been deprecated - https://docs.docker.com/engine/deprecated/#/driver-specific-log-tags.
Tag seems to be introduced in v1.12 so maybe it will not work for older versions of docker - https://docs.docker.com/engine/admin/logging/log_tags/?

@mihail-dev: Im not sure if there are any solutions to make sure logs tags can be backward compatible. However, my point is that documentation shall state which Docker version must be installed and that is supported by the platform. Otherwise you will run in similar issues in upcoming releases of Docker.

I agree with this, maybe you can submit a PR?
Another way we can solve this is to create a second file like this one with the tag option instead of syslog-tag - https://github.com/Accenture/adop-docker-compose/blob/master/etc/logging/syslog/default.yml. Then depending on the docker version call the right file from here - https://github.com/Accenture/adop-docker-compose/blob/master/cmd/compose#L309.

In an ideal world Docker would stop introducing changes that weren't backwards compatible!

@nickdgriffin good point, however, you should expect backward and non-backward compatible changes from Docker team as Docker is heavily under development in these days. This has of course challenges, but hopefully they are simplifying then complicating new ways of solving things. :)

@ismarslomic I always expect non-backward compatible changes, seeing as whenever Docker do anything major they always break something from a previous version. For example Compose v2 completely broke having multiple compose files with custom networks and logging drivers for v1, and didn't implement them fully in v2 (initially) so an upgrade wasn't immediately possible. It's tricky when they do stuff like this particular issue because if we update the etc/logging/syslog/default.yml it'll break it for everyone who isn't on 1.12 yet.
1.12 is probably the next version we'll end up sticking to though I expect because of the introduction of Swarm mode.


Add a --params flag

In GitLab by @isd on Apr 11, 2021, 02:50
Per #45; this just does the bare-bones option of accepting a JSON object.
Per discussion with @fare on discord, gerbil's getopt package doesn't currently support flags being specified multiple times, which makes it hard to implement --param foo=bar --param baz=quux as discussed, but perhaps we can revisit that if that feature gets pushed upstream; we can talk about if/when we want to shave that yak.
I will likely also add a --participants flag as Fare suggested.

Merged: https://github.com/Glow-Lang/glow/commit/b54dc7cab940dd806ee8155879871ac02e7bb2e0


Remove mention of abandoned project Flask-Uploads from docs

I would love to see this project updated, but it seems to have been abandoned by its creator. Still doesn't support Python 3 and hasn't given any love to PyPI for almost 4 years. It seems impossible to get in contact with the creator. This PR removes the reference of Flask-Uploads from the docs. Another option would be to have a NOTE about it being abandoned. I think it also makes sense to remove it from the Flask extensions list (where's the repo for that?)
Here's a 2 year old ticket on Bitbucket that fixes Python 3 support. No reply what-so-ever from @leafstorm. His last public activity on Bitbucket was three years ago.
I'll e-mail him with a reference to this ticket to see if we can get a reply. Perhaps with this ticket we can get the project owner's attention.
The best alternative would of course be to get development going on the project again, perhaps by adding more contributors to the project. Let me know how you feel about all of this. :blush:

Hello @jmagnusson I'd prefer a solution which gives Flask-Uploads a new maintainer. It would be a long time before this PR would make it into a stable release, so I'm not sure if it's even useful as a temporary solution.

@unittaker I agree, if we can get hold of him and solve it that way that would be great.

That guy seems to be fairly active on his Twitter site, pinged him there: https://twitter.com/untitaker/status/608677168269398016

That's great!

Yeah, all my Flask extensions are pretty much abandoned. I wrote them for fun back in high school when I had loads of free time, and now that I have a full-time non-programming job, maintaining extensions for a framework that I don't really use anymore is pretty low on my priority list.
If someone would like to fork my extensions and start maintaining them again, I would be more than happy to turn over the PyPI admin rights.

Perhaps @mattupstate would be willing? Considering that he wrote the Py3 pull request mentioned above. (Which works great btw!)

I'd be up for maintaining Flask-Uploads. @leafstorm I dropped you an email.

I don't think that removing Flask-Uploads from the docs is warranted, even if it doesn't get a new maintainer soon (which it looks like it will, @jeffwidman good on you for putting your hand up):

Despite it having received no love in years, it actually still works "pretty well" (for a few projects of mine, at least... with Flask 0.10 and Python 2.7)
It handles a very common use case
What's the alternative?

Perhaps just add a note to the docs, indicating that it hasn't been maintained for a long time, and / or that it's in the process of receiving a new maintainer.

FWIW, I've emailed @leafstorm several times and haven't heard a thing back.

Sorry, @jeffwidman. I'm staying pretty busy with work, and my downtime is not usually the time I have an unread email from you in my inbox. :-P
If you create a GitHub fork and get everything ready for a release, send me an email or mention me on GitHub and I can give you release access on PyPI. I'll also sign off on a PR to the Flask Web site changing the Flask-Uploads entry to have your name as the maintainer - the file you'll need to change is https://github.com/mitsuhiko/flask-website/blob/master/flask_website/listings/extensions.py.
Besides the PyPI admin rights and recognition as maintainer by @mitsuhiko, I don't think there's anything else I have that you would need in order to get set up. But let me know if anything I have control over is blocking you from taking over.
And if anyone's interested in maintaining Flask-CouchDB, Flask-Login, Flask-Themes, or Flask-XML-RPC, the same offer applies.

@jaza Not to toot my own horn, but I've been working on a library that does most of what uploads does and then some.
https://github.com/justanr/Flask-Transfer

@justanr No problem - since you're doing it, I might as well toot my horn too - not exactly a replacement for Flask-Uploads, but I've written some libraries for uploading to an S3 bucket. Example of how to use these packages together is here:
https://github.com/Jaza/flask-s3-save-example

Guys, Do we have a new maintainer of flask-upload?

@Jdash99 thanks for the reminder.
I just did a test migration of the code/issues over to Github.
While everything went relatively smoothly, for simplicity I think a migration will be a little cleaner if I first deal with the backlog of tasks in the Bitbucket repo--merge the PRs, close out the issues fixed by the PRs, etc. That way there's no issues with folks who did the hard work on PRs not being credited, etc... Once that's done, I'll migrate it over to Github, and then add a few niceties like Travis, migrate the docs to RTD, etc.
@leafstorm can you give me admin access on the bitbucket repo? My bitbucket username is 'jeffwidman': https://github.com/leafstorm/flask-uploads/admin/access
Once I migrate to Github I will update the BB repo with links to the Github repo, similar to the way pytest handled their migration.

@jeffwidman Sure - thanks for doing the preliminaries!

Alright, cleaned out the old PRs and some of the issues, and then migrated to https://github.com/jeffwidman/flask-uploads
@leafstorm can you also give me pypi access rights? I'm 'jeffwidman' there too.
I still want to do a little more checking on Python3 compatibility before I feel comfortable pushing a new release with the changes, but I think we're on the right track and rather get all the access transferred now so I'm not waiting for it later...

Quick update:
I fixed the issue that broke Python 3 compatibility. Someone tried it on Python 3 and confirmed it's working perfectly.
I've also swapped from using Flask module references (which Flask deprecated quite a while ago) to operating as a normal Flask extension using blueprints. @mattupstate did a lot of the heavy lifting there in a pull request back in 2013 that just hadn't been merged in, and I tidied up a few last bits.
At this point, I think everything is ready for a new release to be cut, I just don't have commit rights to Pypi.
Until then, you can install directly from github using Pip:
pip install<EMAIL_ADDRESS>

@jeffwidman Thanks for putting in the hard work! The Travis testing is beautiful.
...This is kind of awkward, but I don't appear to have admin rights to the package on PyPI anymore. I think @maxcountryman may need to grant you access.

Thanks for the kind words.
Last night I emailed @maxcountryman and @rduplain when I noticed they were collaborators on the Bitbucket repo, linking to this thread and asking if they wanted to be collaborators on the new repo. I was a bit surprised, as I had no idea anyone other than you were a collaborator until you gave me access to the BB repo. Ron said he was too busy, which is understandable.
Max replied this morning basically saying thanks for the hard work but he had commit rights on PyPI and he isn't willing to transfer them. Instead since there was so much interest he was planning to migrate the project to his own github repo and suggested I contribute the fixes there.
He said he wished I'd tried to contact him sooner, which made no sense because multiple people have left comments on that bitbucket repo over the past few years asking if it was abandoned, with no reply. There was also that beautiful pull request from @mattupstate modernizing things that sat ignored. That's why we're even discussing this issue in the first place.
I don't mind contributing to other people's projects when they're actively participating, but it does leave a bad taste in my mouth that I spent the better portion of a day fixing stuff up only to have a collaborator who's been absent from the project for years decide he's going to take control by strong arming PyPI rights.
I'd be curious to hear Max expound on his thinking more here, maybe I'm missing something.

FWIW, I'm sorry about the delay in getting the changes integrated and released. I didn't even remember that I'd relinquished my PyPI access. (I also don't remember who's maintaining Flask-CouchDB, -Themes, or -XML-RPC right now...I should probably check on that. I still at least have PyPI ownership of the latter three.)
I'd also like to hear @maxcountryman's plans for the project - since Jeff has already done the work of migrating it over to GitHub and merging a bunch of PR's, I don't think it makes sense to migrate from scratch to his account at this point. Either Jeff could transfer the repo to Max, Max could transfer the PyPI admin rights to Jeff, or Max and Jeff could share the admin rights to the repo and PyPI.

No worries @leafstorm . I appreciate you being willing to let others continue with the project.
I'm still confused why someone who isn't the project repo owner, never made any commits to the project, or commented on any issues decides he's unwilling to handover Pypi rights to the project, despite completely ignoring the project for years.
What am I missing here?

Unfortunately, we (Flask) can't control the ownership of PyPI names.  Since it seems to have a maintainer for now, I'm closing this, although discussion can continue.  @maxcountryman please consider working with @jeffwidman either by adding him as a maintainer or getting his work merged in for a new release.

Perhaps Jeff would like to share with everyone the fact that he approached me some months ago asking if I was still maintaining the project and wondered if I would be willing to introduce some new updates. When I said yes, he apparently decided that was not the answer he was looking for (I guess he was hoping I would say no and give the project to him) and decided to go on a holy mission to make the project his. I have to say, we as a community should not tolerate this kind of nonsense.
Shall we all just engage in a coup d'é·tat every time a project maintainer doesn't hand us the reigns? Surely not.
I don't have the time or interest to participate in this kind of puerile bullshit. Jeff, grow up man, I don't know what your problem is, but you have no right to misrepresent the situation and lie about what actually happened--I responded to your inquiries, I answered your questions, you decided you could go over my head and get permission from Matthew when I didn't give you the answers you wanted to hear.
If the community wants to see updates to the project, I've already cleaned it up quite a bit and published a new release some weeks ago--this includes unreleased work from the BitBucket repo. I'm happy to continue to do so. However, I'm not happy to reward Jeff's behavior by handing it over to him--I don't think that sets a good precedent for the community.
Finally, I'm busy, this kind of nonsense is distracting and a massive waste of everyone's time. I'd appreciate it if I not be contacted again about this--please don't mention me in this thread. Thanks for your understanding! :smile:

I know this is old, but stumbled across it googling something else.
It calls my integrity into question, so thought I should respond.

Perhaps Jeff would like to share with everyone the fact that he approached me some months ago asking if I was still maintaining the project and wondered if I would be willing to introduce some new updates

I have no idea what he's talking about--I never emailed him months before and had no clue he was even involved with the project until after @leafstorm (project owner) said he was transferring maintenance to me and I'd gone in and cleaned up a bunch of old issues/PRs.
Then I noticed Max was a collaborator on BitBucket--up to that point, I had no idea he was involved in the project, as he had no public activity of any kind on the repo, no commits, no issue comments, etc. I assumed he had no interest in the project, but just in case I emailed him saying "Hey, I'm taking over maintenance since leafstorm doesn't have time, I just noticed you're listed as a collaborator on BitBucket, do you still want to help with the project?" (as documented here).
At this point, it's clear there's a disagreement and we have both given our depiction of events (see also the comment history further up this thread). I don't plan to comment further on this thread.


Make logging optional

If i start the consuming, the console is flooded with the debug-infos.
Could that be an optional function to configure in zenstruck_messenger_monitor.yaml?
symfony console messenger:consume async -vv
 [cache] Lock acquired, now computing item "zenstruck_messenger_monitor.worker.119254" ["key" => "zenstruck_messenger_monitor.worker.119254"]

I noticed that as well... I don't think there's anything we can/should do in this bundle. I think you'd need to configure your console log handler to exclude cache logs: https://github.com/symfony/recipes/blob/11095f4c8f6c1cdbca00c9649e2628f1c0c1d338/symfony/monolog-bundle/3.7/config/packages/monolog.yaml#L24


Diagnostic Values are 0

Describe the issue
Most of the sensors are reporting properly but all diagnostics (CPU Usage, Memory usage, Temperature...) are 0.
It seems not to be an individual case as you can see in the latest posts at https://community.home-assistant.io/t/truenas-integration/410431
How to reproduce the issue
Check the TrueNAS integration page in HA
Expected behavior
All diagnostic sensors should report the current values
Screenshots

Software versions

Home Assistant version:  HA 2024.2.0
TrueNAS integration version: v1.2.5
TrueNAS version: TrueNAS-SCALE-<IP_ADDRESS>

yes, cobia is not supported yes. its in the same thread
duplicate #102


Reconnect is acting upon sequences it should not when replaying data

Repro:

Enable terminal bell setting
Ring terminal bell
Reload, the bell rings

Alt repro:

Load pwsh on Windows
Run a command
Reload, several ;nR sequences will show

Easier repro:

Run echo -e '\x1b[6n'
Reload, the prompt shouldn't change


Zoom level increases by 2x every time a Terminal is opened.

Description of your problem
If zoom level is non-zero, zoom level is multiplied by factor of 2 every time a Terminal tab is opened.
What steps will reproduce the problem?

Change zoom level (either in or out)
Open a new Terminal tab
Zoom level is enhanced by factor of two. This is also reflected in the plugins/terminal/spyder.ini file.

What is the expected output? What do you see instead?
No change in zoom level when a new Terminal is opened
Please provide any additional information below
It seems the offending code is widgets.terminalgui.TerminalWidget.apply_zoom and widgets.terminalgui.TermView.increase_font. Every time the zoom is applied, it calls increase_font a "zoom" number of times and increase_font updates the zoom configuration level. Hence, the zoom configuration is doubled.
This may be related to #301.
Versions and main components

Terminal Version: 1.2.0
Spyder Version: 5.2.1
Python Version: 3.9.9
Operating system: macOS 11.6.2

Hi @mrclary,
We decided to store the zoom in/out that the people does, so when they open new terminals they don't have to perform the action again. When I tried it in a big resolution screen, it helped a lot because you don't have to do 8 or 10 zooms every time a terminal is open.
I'm not sure if it will be helpful to indicate the level of zoom somewhere, or even to make this functionality optional in the preferences tab of the terminal. What do you think about that?

@steff456, thanks for your hard work on this plugin. I think it will be useful for me and many of my colleagues that use Spyder.

We decided to store the zoom in/out that the people does, so when they open new terminals they don't have to perform the action again. When I tried it in a big resolution screen, it helped a lot because you don't have to do 8 or 10 zooms every time a terminal is open.

For sure.

I'm not sure if it will be helpful to indicate the level of zoom somewhere, or even to make this functionality optional in the preferences tab of the terminal. What do you think about that?

That's a good idea, but it is not important to me to see the zoom level.

But I do see the bug in the zoom level, I'll update that in our next release.

That was my only concern at present.


Reinforcement Learning: TD3 with HalfCheetah-v3 Gymnasium Environment

Description:
This PR adds an example to the reinforcement learning examples set
TD3 on HalfCheetah-v3:

The training was performed for 150,000 steps.

The video for the result can be found in my GSoC final report

Do you have the model file as well?

Do you have the model file as well?

Unfortunately, I didn't save the model while training.
The file I used for training is in the PR.


Update repositories.txt

I have changed github username

Hello @fabianoriccardi. The requested change is now in progress.
Unlike submissions, this type of request is still handled manually. The Library Manager index's maintainer occasionally comes through to clear all the outstanding requests and closes those issues/PRs when that is done. So you can get a notification if you're following the linked issue/PR:
https://github.com/arduino/library-registry/pull/130
After that, you can monitor the indexing of the library via its logs web page:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager


question about initial f value in camera estimation

Could you tell me why do you choose 1600 as initial f for camera intrinsics? Does this value influence the result importantly? I would really appreciate your response

Sorry for the late response. This is a manually selected value by try-and-error. For bundle adjustment to work it needs to have a relatively good initialization. But it's not that strict. The focal length after bundle adjustment is around 1500, which means ~100 error is tolerable.


Robots: Robots without a state are not shown

We are only displaying robot's with known state, so a robot that lost connection to rmf will then disappear from the dashboard. The robot's state also does not contain all the info that we need, for example, a robot's footprint is only available from the trajectory so we have to use a hardcoded value now.

Seems like fleet manager is handling all the states of the robots. Can I assume that all robots returned by the resource manager will be at the same level? Or there is no need to display the icon but just display the robot in the omni-panel accordian, like the dispensers?

afaik, the robot resources only contains the icons, they do not list all the known robots in a map. I am not aware of any rmf interfaces that provides that atm.

I see, so it differs from dispensers in that the location of all known dispensers is hardcoded in the json resource files due to rmf limitations whereas the known robots will be handled by rmf instead.
So for the case of robots, some sort of cache to store all known robots, and then referencing them later if they are disconnected would be more appropriate.

Closing this as another development should be addressing this.


Changed README.md

Simply replaced simplemud.py with MuddySwamp.py in the README.md.

Wrong repo, sorry, still learning git for Hactoberfest.


Generic TypeValidator fallback

when we infer type hints, we currently fail if we don't handle a specific type. We can be a bit more aggressive and check the type of that object.
We should make sure that special kinds of types are not accidentally handled. For instance:

TypeVars
Protocols
Other?

Need to determine correct behavior with NewType

Done.


Update http4s-blaze-client, ... to 0.21.18

Updates

org.http4s:http4s-blaze-client
org.http4s:http4s-blaze-server
org.http4s:http4s-circe
org.http4s:http4s-dsl

from 0.21.9 to 0.21.18.
GitHub Release Notes - Version Diff
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch

Superseded by #470.


fix(QUI-51): use 30-second restart interval to prevent restart limits

Systemd by default will stop restarting a service if it restarts too
quickly. By increasing the restart interval, we can prevent the service
from triggering the limit, which allows it to continue restarting until
it stays up.
Closes QUI-51

#37
#36  👈
main

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

Join @L8D and the rest of your teammates on  Graphite

Merge activity

Oct 5, 1:38 PM EDT: @L8D merged this pull request with Graphite.


Track the user information who changes a key-value

Hi, I tried to look up the user information from the audit events, but the event schema doesn't contain that information (on who modified the key etc.) https://docs.microsoft.com/en-us/azure/azure-app-configuration/concept-app-configuration-event
Can I obtain the information about the user who modified the key?

@pavithrakarthik Every change in App Configuration must be authenticated (either HMAC or AAD). However, App Configuration does not track/log who made the change today. Depending on customer demands, this is something for future consideration.

This is needed for SOX applications.

Yes, we need to follow who changed key-values for audit, if we have an incident in Production.

We are working on this now. We will make auditing logs available to users. The logs will include the user object id if the user is authenticated using AAD when making changes.

Great to see that you are working on this @zhenlan. Will the logs include a way to tie the log back to a key-value pair via an e-tag or something? When will this be ready for customers to use?

It's available now. As part of the 'RequestURI' in the log, you can tell which key is related.
https://docs.microsoft.com/en-us/azure/azure-app-configuration/monitor-app-configuration?tabs=portal

The auditing logs with user information are also available. Follow the doc below to enable auditing logs.
https://docs.microsoft.com/en-us/azure/azure-app-configuration/monitor-app-configuration
Note that, the user identity information is only available when the change request is authenticated with Azure AD (AAD). You can enforce AAD authentication of an App Configuration store by disabling Access keys (under your App Configuration store in Azure portal, go to Access keys, and then toggle off Enable access keys under Authentication type at the bottom of the page).

Hi , Can you please let me know where can I find the object Id of the user in logs?

@margasat please see the reference for audit logs
https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/aacaudit

When I look at events in the Activity Log it says: "Change History is not applicable to this type of activity log"
How can I see the audit of the change that was made to the store?  Like UserA changed this specific KV from valueA to valueB.

@spatelGDOT you can follow the instructions to enable the audit log (not activity log)
https://learn.microsoft.com/en-us/azure/azure-app-configuration/monitor-app-configuration


Add Assigner field to issues_events

I've not updated the comment:

   //     assigned, unassigned
   //       The Actor assigned the issue to or removed the assignment from the Assignee.

to keep it consistent with Github documentation even though it is clearly incorrect.

Can you provide a reference for why this field should be added. Either a link to GitHub API docs that shows it, or if it's not documented, then a sample API query and response that contains it?
Also, I don't quite understand what you mean by this:

I've not updated the comment:

   //     assigned, unassigned
   //       The Actor assigned the issue to or removed the assignment from the Assignee.

to keep it consistent with Github documentation even though it is clearly incorrect.

Can you please elaborate? https://developer.github.com/v3/issues/events/ is a large page, what exactly are you referring to there?

Sure, it's described there: https://developer.github.com/v3/issues/events/#attributes
Inconsistency in the documentation:

Attributes:

assigner
The User object that performed the assignment (or unassignment) for this Issue. Only provided for 'assigned' and 'unassigned' events.

Events

assigned
The issue was assigned to the actor.
unassigned
The actor was unassigned from the issue.

It sounds like "the actor" refers to the actor attribute, but that's not correct.
I'll send an email. Thanks.

It sounds like "the actor" refers to the actor attribute, but that's not correct.

I tried reading it multiple times, but I still don't quite see what you're referring to. Maybe it'd help if you showed what a potential patch would look like?
I can merge this PR which adds a missing field now. If there are additional doc enhancements possible, please feel free to follow up with another PR or issue.


sync chains singing secret with argocd

include chains signing secret

I was thinking it would be better to put the secret hook in its own separate file, e.g. components/build/tekton-chains/chains-signing-secret.yaml rather than lumping it in with the certs. They are pretty different things.
Or, if there are good benefits of having them in a single file, how about naming it more generically components/build/tekton-chains/chains-certs-and-signing-secret.yaml or omponents/build/tekton-chains/chains-post-sync-hooks.yaml

I was thinking it would be better to put the secret hook in its own separate file, e.g. components/build/tekton-chains/chains-signing-secret.yaml rather than lumping it in with the certs. They are pretty different things.

The job I created depends on the service account and role/bindings, so I added it to the same file.

Or, if there are good benefits of having them in a single file, how about naming it more generically components/build/tekton-chains/chains-certs-and-signing-secret.yaml or components/build/tekton-chains/chains-post-sync-hooks.yaml , omponents/build/tekton-chains/chains-post-sync-config.yaml

How about chains-secrets-config.yaml since each resource is created to modify or create a secret?

LGTM, let's merge.


Integration books section

Is your feature request related to a problem? Please describe.
We have a collection of books at https://innersourcecommons.org/resources/books/ that would be great to get ported to the new site.
Describe the solution you'd like
The place in the new site for this seems to be https://innersourcecommons.net/learn/books/?
I would suggest to use the cover images of the books on the overview page. That way we show all books side-by-side, much like in a bookshelf. Will be really pretty :)

@dicortazar any suggestion for a cover image that we could use for the "Managing InnerSource Projects",  even if just as a temporary solution?

Just noticed that the "Getting Started With InnerSource" book that used to be available at http://www.oreilly.com/programming/free/getting-started-with-innersource.csp cannot be reached through that URL any more. Does anybody know what might have happened there?

Available here: https://innersourcecommons.net/learn/books/


search() gets stuck on infinite "while loop" if the search term has zero results

https://github.com/Nv7-GitHub/googlesearch/blob/be88ef64de65529e5d42f14b4f2cd3f675ae4adf/googlesearch/__init__.py#L42-L62
Code cannot exit the while loop if the value of start never goes up, and the value of start only ever goes up if a valid result is yielded.
For search terms that have zero results, this results on the code getting stuck trying to find something forever.

Any chance this can get merged in and released?

This has been fixed.


Unable to modify rounded_border_tv.xml

I am trying to modify  rounded_border_tv.xml so as to have custom border style for the text container ( the thing with border and close button ( image ) to display text on image in edit mode ). I have tried everything but am unable to modify it. It is still showing the original rounder border. Is it hard coded somewhere else too ?
[ NOTE : I am using your demo app and have also tried modifying rounder_border_text_view.xml but to no avail ]

@ShivanshAnand in app/build.gradle comment
implementation 'ja.burhanrashid52:photoeditor:1.0.0'
and uncomment
implementation project(':photoeditor')
Sample app just using the version from bintray)

@a-zasypalov approach will work. Closing this issue/


Update background-color for column

Update background-color to white for columns when it's specified in metadata
Description

Related Issue
https://jira.corp.adobe.com/browse/DEVSITE-856

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Can we create a matching css class instead? it seems unnecessary to programmatically assign styles with js based on a css class when css should handle it. @louisachu am I missing something here? 😅


Add column user_data in the table aws_ec2_launch_template_version Closes #1791

Integration test logs

Logs
No env file present for the current environment:  staging
 Falling back to .env config
No env file present for the current environment:  staging
customEnv TURBOT_TEST_EXPECTED_TIMEOUT undefined

SETUP: tests/aws_ec2_launch_template_version []

PRETEST: tests/aws_ec2_launch_template_version

TEST: tests/aws_ec2_launch_template_version
Running terraform
data.aws_region.alternate: Reading...
data.aws_region.primary: Reading...
data.aws_partition.current: Reading...
data.aws_caller_identity.current: Reading...
data.aws_region.alternate: Read complete after 0s [id=us-east-2]
data.aws_partition.current: Read complete after 0s [id=aws]
data.aws_region.primary: Read complete after 0s [id=us-east-1]
data.aws_caller_identity.current: Read complete after 2s [id=222222222222]
data.null_data_source.resource: Reading...
data.null_data_source.resource: Read complete after 0s [id=static]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_launch_template.named_test_resource will be created
  + resource "aws_launch_template" "named_test_resource" {
      + arn                                  = (known after apply)
      + default_version                      = (known after apply)
      + disable_api_stop                     = true
      + disable_api_termination              = true
      + ebs_optimized                        = "true"
      + id                                   = (known after apply)
      + instance_initiated_shutdown_behavior = "terminate"
      + instance_type                        = "t2.micro"
      + latest_version                       = (known after apply)
      + name                                 = "turbottest22059"
      + name_prefix                          = (known after apply)
      + tags                                 = {
          + "Name" = "turbottest22059"
        }
      + tags_all                             = {
          + "Name" = "turbottest22059"
        }

      + block_device_mappings {
          + device_name = "/dev/sda1"

          + ebs {
              + iops        = (known after apply)
              + throughput  = (known after apply)
              + volume_size = 20
              + volume_type = (known after apply)
            }
        }

      + capacity_reservation_specification {
          + capacity_reservation_preference = "open"
        }

      + cpu_options {
          + core_count       = 4
          + threads_per_core = 2
        }

      + credit_specification {
          + cpu_credits = "standard"
        }

      + elastic_gpu_specifications {
          + type = "test"
        }

      + elastic_inference_accelerator {
          + type = "eia1.medium"
        }

      + instance_market_options {
          + market_type = "spot"
        }

      + license_specification {
          + license_configuration_arn = (known after apply)
        }

      + metadata_options {
          + http_endpoint               = "enabled"
          + http_protocol_ipv6          = (known after apply)
          + http_put_response_hop_limit = 1
          + http_tokens                 = "required"
          + instance_metadata_tags      = "enabled"
        }

      + monitoring {
          + enabled = true
        }

      + network_interfaces {
          + associate_public_ip_address = "true"
        }

      + placement {
          + availability_zone = "us-west-2a"
        }

      + tag_specifications {
          + resource_type = "instance"
          + tags          = {
              + "Name" = "turbottest22059"
            }
        }
    }

  # aws_licensemanager_license_configuration.named_test_resource will be created
  + resource "aws_licensemanager_license_configuration" "named_test_resource" {
      + arn                      = (known after apply)
      + description              = "Testing"
      + id                       = (known after apply)
      + license_count            = 10
      + license_count_hard_limit = true
      + license_counting_type    = "Socket"
      + license_rules            = [
          + "#minimumSockets=2",
        ]
      + name                     = "turbottest22059"
      + owner_account_id         = (known after apply)
      + tags_all                 = (known after apply)
    }

Plan: 2 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  + account_id    = "222222222222"
  + aws_partition = "aws"
  + resource_aka  = (known after apply)
  + resource_id   = (known after apply)
  + resource_name = "turbottest22059"
aws_licensemanager_license_configuration.named_test_resource: Creating...
aws_licensemanager_license_configuration.named_test_resource: Creation complete after 2s [id=arn:aws:license-manager:us-east-1:222222222222:license-configuration:lic-c6c4715ccafa29b5473068b906dcdd87]
aws_launch_template.named_test_resource: Creating...
aws_launch_template.named_test_resource: Creation complete after 4s [id=lt-06bc3d6c8c19a19c7]

Warning: Deprecated

  with data.null_data_source.resource,
  on variables.tf line 43, in data "null_data_source" "resource":
  43: data "null_data_source" "resource" {

The null_data_source was historically used to construct intermediate values
to re-use elsewhere in configuration, the same can now be achieved using
locals

(and one more similar warning elsewhere)

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Outputs:

account_id = "222222222222"
aws_partition = "aws"
resource_aka = "arn:aws:ec2:us-east-1:222222222222:launch-template/lt-06bc3d6c8c19a19c7"
resource_id = "lt-06bc3d6c8c19a19c7"
resource_name = "turbottest22059"

Running SQL query: test-get-query.sql
[
  {
    "launch_template_id": "lt-06bc3d6c8c19a19c7",
    "launch_template_name": "turbottest22059",
    "version_number": 1
  }
]
✔ PASSED

Running SQL query: test-list-query.sql
[
  {
    "launch_template_name": "turbottest22059",
    "version_number": 1
  }
]
✔ PASSED

POSTTEST: tests/aws_ec2_launch_template_version

TEARDOWN: tests/aws_ec2_launch_template_version

SUMMARY:

1/1 passed.

Example query results

Results
> select launch_template_name, user_data from aws_ec2_launch_template_version
+-------------------------+------------------+
| launch_template_name    | user_data        |
+-------------------------+------------------+
| test                    |                  |
| test                    | echo "hello...." |
| test-launch-template    |                  |
| test                    |                  |
| test                    |                  |
| sp-flow-launch-template |                  |
+-------------------------+------------------+

@ParthaI are there other important columns that we have missed to add?


Recognition of Pelazoneuron as a segregate of Christella (Thelypteridoideae; Thelypteridaceae) [PASSED]

Author(s) of proposal
Susan Fawcett and Alan R. Smith
Name of taxon
Pelazoneuron
Rank of taxon
Genus
Approximate number of species affected
16
Description of change
Pelazoneuron (Holttum) A.R. Sm. & S.E. Fawc. is recognized at genus rank for a monophyletic clade of 16 North and South American species previously recognized as Christella, but distantly related to the type species of Christella (Smith 1971). Pelazoneuron was named as a section of Christella by Holttum (1974), based on the type species Holttum designated, and which we recognize as Pelazoneuron patens.
Reason for change
Christella as recognized by PPG I is non-monophyletic, with its species resolving in four distinct clades (see also proposal #56). The clade corresponding to Pelazoneuron is distantly related to Christella s.s.
For keys and morphological descriptions, see Fawcett & Smith 2021. For phylogenetic analyses, see Fawcett et al. 2021.
Fawcett_Smith_2021.pdf
Fawcett_2021_GlobalPhylogeny.pdf
Fawcett, S. and A. R. Smith. 2021. A Generic Classification of the Thelypteridaceae. Sida, Botanical Miscellany 59. Fort Worth: Botanical Research Institute of Texas Press.
Fawcett, S., Smith, A.R., Sundue, M., Burleigh, J.G., Sessa, E.B., Kuo, L.Y., Chen, C.W., Testo, W.L., Kessler, M. and Barrington, D.S., 2021. A global phylogenomic study of the Thelypteridaceae. Systematic Botany, 46(4), pp.891-915.
Fawcett, S., A. R. Smith, M. Sundue, J. G. Burleigh, E. B. Sessa, L.-Y. Kuo, C.-W. Chen, W. L. Testo, and M. Kessler. GoFlag Consortium, and D. S. Barrington. 2021. Data from: A global phylogenomic study of the Thelypteridaceae. Dryad Digital Repository. https: doi.org/10. 5061/dryad.gxd2547j4.
Holttum, R.E., 1974. Thelypteridaceae of Africa and adjacent islands. Journal of South African Botany.
Holttum, R. E. 1977. The family Thelypteridaceae in the Pacific and Australasia. Allertonia 1: 169–234.
Holttum, R. E. 1982. Thelypteridaceae. Flora Malesiana, ser. II 1: 334–560.
Smith, A. R. 1971. Systematics of the neotropical species of Thelypteris section Cyclosorus. University of California Publications in Botany 59: 1–143.
Reference(s) for publication of the name
Fawcett_Smith_2021.pdf
List the numbers of any related issues
56
Code of Conduct

[X] I agree to follow the PPG Code of Conduct

This proposal was voted on during PPG Ballot 7 (voting period January 2024). A total of 74 votes were cast. There were 74 'Yes' votes (100%) and 0 'No' votes (0%). The proposal passes.


Demonstrate local development of project depended on from source dependencies

Just like binary dependencies where developers can develop both project side-by-side in the same multi-project, source dependencies should be able to achieve the same outcome. The sample should demonstrate how to substitute a source dependency with an included build.

Show how we step between binary dependencies, source dependencies and composite builds through some script/steps.


Rename github repos to include "origin"

Our current primary repos are named:

bridge-server
origin-js
mobile-app
demo-dapp
company-website
docs
identity-playground

When a user clones or forks one of our repos, they will have a directory of this name on their computer (if cloned) or repo appear on their github profile (for forks).
Thus divorced from the context of our github account, our repo names become generic and unidentifiable. In a folder full of dozens of projects, "mobile-app" won't mean much of anything. Likewise for "company-website".
Other projects follow the convention of prefixing generic-sounding repos with their name. See truffle for example:

On the other side, can you spot the origin repos in this folder? :)

And here is how our repos appear on a github profile. Again, out of context names like "company-website" or "mobile-app" mean very little.

People are, of course, free to rename their local folders if we get tired of typing "origin" all the time.
I would propose:

origin-bridge-server
origin-js
origin-mobile-app
origin-demo-dapp
origin-company-website
origin-docs
identity-playground (maybe leave this as its not specific to origin?)

(I've got an origin folder, and everything happily lives there.)

I solved this by using a parent Origin folder that contains all my Origin repos. Curious what other people are doing.

My concern is not for our comfort, but for open source contributors who are not part of the Origin team. They are the ones who will have a random "Repos" folders where they clone all the things they're playing around with. When they come back in a month, will they even remember what "company-website" is?  They are the ones whose friends will look at their github profile and ask, "What is this 'mobile-app' thing you're working on? Not very descriptive!"
For us who live and breath these repos, it's easy enough to rename them to shorter names for our origin folders if we like.

I agree with @wanderingstan and @tyleryasaka that forking 'demo-dapp' to nick/demo-dapp then cloning to a local 'demo-dapp' directory is not as descriptive as origin-demo-dapp when looking at forks and local project dirs. Keeping everything in a parent 'origin' dir works if you are a well organized person, which I'm not ;-)
Perhaps we could even take the opportunity to simplify some repo names:

origin-bridge
origin-js
origin-mobile
origin-dapp
origin-website
origin-docs

Okay, I'm convinced. I like @nick's proposal of using shorter names though.

I also like @nick's shorter names. Super sleek and concise.

@joshfraser , I believe as repo owner you're going to have to be the one do this one.

Done


Add const to some functions.

It just make some ::new() function to be const.
allowing it to be call on const definitions like this:
// Old
const SIZE: TilemapSize = TilemapSize{ x: 256, y: 256 };

// New
const SIZE: TilemapSize = TilemapSize::new(256, 256);

And some compile time optimizations.

I fixed the clippy issue elsewhere. I'll merge this. :+1:


Bug when using .concatenated

While developing https://github.com/tensorflow/swift-apis/pull/946 I found out a bug when using Tensor.concatenated method.
Here is the code to reproduce the error in swift colab: https://colab.research.google.com/drive/11fZldGxz1O5LUfoT2WhzusuPQFyA4HdX?usp=sharing
If you use the mode "concat", it will fail on:
Precondition failed: Axis must be in -rank..<rank when calling split(sizes:alongAxis:) (rank: 0, axis: -1): file /swift-base/tensorflow-swift-apis/Sources/TensorFlow/Operators/Basic.swift, line 142
If you switch to "sum" mode, output will be:
30.0
[[[1.0, 1.0, 1.0]], 0.0, [[1.0, 1.0, 1.0]]]

And here is the Python version: https://colab.research.google.com/drive/1joRHIfFOSmRVWC3kLii4sY31vya1sdGx?usp=sharing
In Python, both "concat" and "sum" produces the output:
tf.Tensor(30.0, shape=(), dtype=float32)
[[<tf.Tensor: shape=(1, 3), dtype=float32, numpy=array([[1., 1., 1.]], dtype=float32)>, None, <tf.Tensor: shape=(1, 3), dtype=float32, numpy=array([[1., 1., 1.]], dtype=float32)>]]

The reason is that when it's trying to compute derivatives of 'concatenated' for first values.count - 1 elements of 'values', the back-propagated derivatives are scalar zeros. Ideally they should be zero tensors in the desired shape. We are working on a longer-term fix here https://bugs.swift.org/browse/TF-1005. But for now I'd recommend this workaround. In your func test, if mode == 'concat' do this:
if mode == "concat" {
let concat = inputs[index].concatenated(with: inputs[reversedIndex], alongAxis: -1)
values.append(concat.withDerivative { [shape = concat.shape] in
if $0 == Tensor(0) { $0 = Tensor(zeros: shape) }
})
}

Closing this issue as TF-1005 is the underlying fix, and the above workaround should work. Thanks @xihui-wu  and @kongzii !


8.0.28

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Supersedes https://github.com/conda-forge/mysql-feedstock/pull/62

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thank you for rebasing the 2 patches :)


Get stashcp tests working with Pelican

The pelican-osdf-compat RPM doesn't provide the stashcache-client virtual dependency; it's a very old name (used for the Python version of stashcp) so check for the osdf-client virtual dependency instead when deciding whether to skip the stashcp test or not

Pelican uses STASH_TOPOLOGY_NAMESPACE_URL instead of STASH_NAMESPACE_URL for the URL to the namespaces JSON; set both in the environment so old and new versions of stashcp work as expected

Better detect if we're using a Go version of stashcp (and should pass --cache instead of editing caches.json)

Tests here: https://osg-sw-submit.chtc.wisc.edu/tests/20231110-1829/packages.html
The "23 Testing + Upcoming Testing" tests used Pelican stashcp.


Mcknight/fix test store test

resolves #
docs dbt-labs/docs.getdbt.com/#

Problem
test_store_test_failures tests leave hanging artifacts due to change in schema name, need to add a teardown method to make sure we drop alt schema to stop build up of unnecessary schemas in ci/cd database overtime.

Solution

Checklist

[x] I have read the contributing guide and understand what's expected of me
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

todo create backports as needed


Plugin can't be loaded from Logstash 1.5.4 and 2.0

It seems the loading of the rabbitmq output plugin broke in Logstash 1.5.4 when the plugin was stepped to 1.1.0 (including a step-up of march_hare from 2.5.1 to 2.11.0), a problem that doesn't appear to be fixed in the Logstash 2.0 beta. Not sure if this is a problem with the plugin or with the Logstash's packaging of it.
$ for i in logstash_{1.5.3,1.5.4,2.0}*.deb ; do
> sudo dpkg -i $i > /dev/null 2>&1
> echo =============================
> /opt/logstash/bin/logstash --version
> /opt/logstash/bin/plugin list | grep logstash-output-rabbitmq
> /opt/logstash/bin/logstash --configtest -e 'output { rabbitmq { host => "localhost" exchange => "test" exchange_type => "topic" } }'
> done
=============================
logstash 1.5.3
logstash-output-rabbitmq
Configuration OK
=============================
logstash 1.5.4
logstash-output-rabbitmq
The error reported is:
  Couldn't find any output plugin named 'rabbitmq'. Are you sure this is correct? Trying to load the rabbitmq output plugin resulted in this error: no such file to load -- ext/rabbitmq-client
=============================
logstash 2.0.0-rc1
logstash-output-rabbitmq
The error reported is:
  Couldn't find any output plugin named 'rabbitmq'. Are you sure this is correct? Trying to load the rabbitmq output plugin resulted in this error: no such file to load -- ext/rabbitmq-client

When downloading the tarball and running Logstash from there the problem is still there but the error message is different:
$ logstash-2.0.0-rc1/bin/logstash -e 'output { rabbitmq { host => "localhost" exchange => "test" exchange_type => "topic" } }'
The error reported is:
  Couldn't find any output plugin named 'rabbitmq'. Are you sure this is correct? Trying to load the rabbitmq output plugin resulted in this error: NameError

This is on a Debian 7.9 (wheezy) system with Oracle Java 8u60

Thanks a lot for your report, will investigate.

@magnusbaeck thanks for reporting this. I don't have the error on 1.5.4 (OSX + Downloaded zip), but I do have it on the latest 2.0RC. I'll be investigating this today:
~/D/logstash-1.5.4 $ bin/logstash -e "input { generator { count => 50 } } output { rabbitmq { exchange => foo exchange_type => topic host => localhost } }"
Logstash startup completed
Logstash shutdown completed
~/D/logstash-1.5.4 $ cd ../logstash-2.0.0-rc1/
~/D/logstash-2.0.0-rc1 $ bin/logstash -e "input { generator { count => 50 } } output { rabbitmq { exchange => foo exchange_type => topic host => localhost } }"
The error reported is:
  Couldn't find any output plugin named 'rabbitmq'. Are you sure this is correct? Trying to load the rabbitmq output plugin resulted in this error: NameError

@magnusbaeck this has just been fixed and pushed as 3.0.5 from PR #31. Thanks for finding this bug!

Thanks for the quick correction! Close the issue?

$ /opt/logstash/bin/logstash --version
logstash 2.0.0

$ /opt/logstash/bin/plugin list --verbose rabbitmq
logstash-input-rabbitmq (3.0.3)
logstash-output-rabbitmq (3.0.5)

$ /opt/logstash/bin/logstash -t -e 'input { generator { count => 10 } } output { rabbitmq { host => localhost exchange => logstash_test } }'
The error reported is:
  Couldn't find any output plugin named 'rabbitmq'. Are you sure this is correct? Trying to load the rabbitmq output plugin resulted in this error: no such file to load -- ext/rabbitmq-client

I'm facing the same issue in output plugin version 3.0.5. Can you please let me know if I'm missing something here? This is on Ubuntu 14.04.3.

Exactly the same issue also here:
$ cat /etc/issue
Ubuntu 14.04.3 LTS

$ /opt/logstash/bin/logstash --version
logstash 2.1.0

$ /opt/logstash/bin/plugin list --verbose rabbitmq
logstash-input-rabbitmq (3.1.1)
logstash-output-rabbitmq (3.0.6)

/opt/logstash/bin/logstash -t -e 'input { generator { count => 10 } } output { rabbitmq { host => localhost exchange => logstash_test } }'
The error reported is:
  Couldn't find any output plugin named 'rabbitmq'. Are you sure this is correct? Trying to load the rabbitmq output plugin resulted in this error: no such file to load -- ext/rabbitmq-client

In Logstash 2.1.1, things are working for me:
% bin/plugin list --verbose | grep rabbitmq
logstash-input-rabbitmq (3.1.1)
logstash-output-rabbitmq (3.0.6)

% bin/logstash --version
logstash 2.1.1

% bin/logstash -t -e 'input { generator { count => 10 } } output { rabbitmq { host => localhost exchange => logstash_test } }'
Missing a required setting for the rabbitmq output plugin:
...

^^ is the rabbitmq output being loaded successfully and failing config validation because of a missing  setting. Looks OK to me.
Can you try with Logstash 2.1.1?

I think I found the problem:
$ /opt/logstash/bin/logstash -t -e 'input { generator { count => 10 } } output { rabbitmq { host => localhost exchange => logstash_test } }'
The error reported is:
  Couldn't find any output plugin named 'rabbitmq'. Are you sure this is correct? Trying to load the rabbitmq output plugin resulted in this error: no such file to load -- ext/rabbitmq-client

But:
$ sudo /opt/logstash/bin/logstash -t -e 'input { generator { count => 10 } } output { rabbitmq { host => localhost exchange => logstash_test } }'
Missing a required setting for the rabbitmq output plugin:
...

So I should run it as root.
Thank you for your advice.

That's an interesting observation, but it should of course work for non-root users as well.

This seems like a weird file permissions error. @mezzomondo @magnusbaeck can you ls -lthe rabbitmq plugin files?
Running this inside your plugin dir should give the correct output:
find vendor/ | grep rabbitmq | xargs stat
It looks to me that the issue is here: 16777220 30549407 -rw-r----- 1 andrewvc staff 0 417376 "Nov 26 06:48:58 2015" "Nov 24 06:42:21 2015" "Nov 26 06:49:00 2015" "Nov 24 06:42:21 2015" 4096 816 0 vendor//bundle/jruby/1.9/gems/march_hare-2.11.0-java/lib/ext/rabbitmq-client.jar
I'm going to release an updated version of these logstash plugins to fix this issue, as well as bumping to the latest march_hare version.

I've got a fix in here. https://github.com/logstash-plugins/logstash-mixin-rabbitmq_connection/pull/13 will update this thread when we release a new gem today.

@andrewvc same permissions here.

I've released a new gem that should fix this @magnusbaeck @mezzomondo


Cotire does not honor CMAKE_lang_VISIBILITY_PRESET and CMAKE_VISIBILITY_INLINES_HIDDEN variables

When using one of this option, precompiled header is compiled without them which results into the following error on OSX:
error: value symbol visibility differs in PCH file vs. current file

Steps to reproduce:

Download test project from https://github.com/zapolnov/cotire_bug_report
Invoke cmake
Invoke make

Fixed in cotire 1.7.5. Thanks for providing the handy project to reproduce the bug.


Image to text solver

Could this be used to solve the captcha on the registration page of chess.com

If there is a text captcha that can be downloaded, then yes


Dropdown position is off when using semantic grid markup

The new additions to dropdown in 5.5 are calculating the position of the dropdown incorrectly if you're not using row / column naming and are instead using semantic grid markup.
A dropdown which would correctly show with arrow on the left side of the anchor text and open to the right, now shows on the right side of the anchor text and opens to the left - as it would if it was pressed up against the right side browser window.
5.5 on top, and 5.4 below:

In testing, using default row and column classes works, but semantic row and column classes don't.
It could be the calculation for actualMarginWidth if their are no 'row' classnames found (foundation.dropdown.js around row 250).  This is part of the js additions to 5.5 for dropdown (see https://github.com/zurb/foundation/pull/5986/files ).

Thanks for this, unfortunately pull request 6160 is being held up because of merge conflicts. Can't understand why this issue isn't more  of an issue, easy to see on the foundation docs site dropdown page.

Thanks! We'll close in favor of https://github.com/zurb/foundation/pull/6160. Sure the merge conflicts are no problem.


CLI does not work properly if the password contains "-", tested on release-2.9.0

Could be a BUG:

Cloudbreak version 2.9.0
Host platform: AWS/ amazon linux 2
If the password contains a "-", (e.g., "aa-bbbbb1234" ) Cli will just give a error message said

ERROR: status code: 400, message: The length of the password has to be in range of 5 to 100

The specific shell command likes

cb cluster create --cli-input-json createcluster.json ...

Hi @yuliu-sn!
Currently there are two fields, which has a size-validation like this. Could you tell us, was the field cluster/ambari/ambariSecurityMasterKey filled?
Because if ambariSecurityMasterKey fields's value is not null and the length of it is invalid, that could also cause an error like that you mentioned.

Hi @horadla23,
sorry for my late reply.
where is the file/field that you mentioned cluster/ambari/ambariSecurityMasterKey?
Is it the one set when creating the cluster using CB?
I created the cluster successfully using the web console  but CLI does not work appropriately when I tried to recreate the cluster.

Hi @yuliu-sn!
You can download the CLI json from UI: https://docs.hortonworks.com/HDPDocuments/Cloudbreak/Cloudbreak-2.9.0/install-cli/content/cb_obtain-cluster-json-template-from-the-ui.html
With this you can compare the json of your cluster successfully created on UI and your json which you are using during cluster creation with CLI.

Thanks, yes, I did it exactly as you said before as posted. The json was downloaded from web ui (otherwise I don't even know how to write a complete one for a complicated cluster...).

@yuliu-sn Cool, if it is working, then please close this issue. Thanks in advance!

@horadla23 ... the cli failed, so that I described it here: link to above

Sorry, I misunderstood, in this case you should check the json, because when you download it from UI, the sensitive fields like passwords are cleared out due security reasons, so you need to check those field and fill them.

@horadla23 oh, yes it works now, thank you! the json is so long that couldn't find the empty password ... It would be great the UI can give some hints on this...
Anyway, I don't have a problem anymore.  Thanks!


Different viewcontroller for different index ?

In example HomeViewController.swift, there is
    override func segementSlideContentViewController(at index: Int) -> SegementSlideContentScrollViewDelegate? {
        let viewController = ContentViewController()
        viewController.refreshHandler = { [weak self] in
            guard let self = self else { return }
            self.badges[index] = BadgeType.random
            self.reloadBadgeInSwitcher()
        }
        return viewController
    }

we seem to use same ContentViewController for all tabs / switchers, can we use different controller for differnet tabs/indices ?
say, sth like this
    override func segementSlideContentViewController(at index: Int) -> SegementSlideContentScrollViewDelegate? {
       if index == 0 {
            let viewController = ContentViewController()
            viewController.refreshHandler = { [weak self] in
                guard let self = self else { return }
                self.badges[index] = BadgeType.random
                self.reloadBadgeInSwitcher()
            }
            return viewController
       } else if indes == 1 {
          let vc = SomeOtherContentViewController()
          return vc
       }
    }

tried this, it does not seem to work ? any working example ?

nvm, looks like the weird issue was because I did not return any view controller when index was at 1 (returned nil). and the slide switcher behaves in a weird way (when slide to index 1, the switcher does not update, etc)
after returnning peoper view controller for index 1, it seems working fine

Whether SomeOtherContentViewController realize SegementSlideContentScrollViewDelegate ?

it did, but just was not assigned. So we end up have first index pointed to
an vc and second being nil (my bad)
The the weird behavior popped up. But once second index got assigned(
returned) an actually vc (yes, implementing the delegate), it then works
fine
so it all seems Ike there is some internal checks did not handle a corner
case well. But it eventually worked for me as is
On Wed, Sep 2, 2020 at 10:55 PM Jiar<EMAIL_ADDRESS>wrote:

Whether SomeOtherContentViewController realize
SegementSlideContentScrollViewDelegate ?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Jiar/SegementSlide/issues/53#issuecomment-686218461,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACTVSANUJVL66SGUWPMODJTSD4ASFANCNFSM4ORHIECA
.

It's weird, but I can't judge now. Can you provid a demo project?


Finish migrating to ContextObj

Description
This PR finishes the migration to ContextObj. It does two things:

convert the remaining code to use ContextObj instead of dict access.
remove dict-like support from ContextObj.

Interesting trivia
Interestingly this pointed out harmless typing errors, for example:
if not scan.success or not isinstance(scan, IaCScanResult):
    handle_scan_error(client, scan)
    return None

pyright complained because the 2nd argument of handle_scan_error() expects a Detail instance, but pyright thought it could be a IaCScanResult. From a typing perspective, it could happen if scan.success was False but isinstance(scan, IaCScanResult) was True. In practice it cannot happen because scan is always a Detail when scan.success is False.
I wondered why it did not complain before, and I realized it's because client was previously defined as client = ctx.obj["client"], so pyright had no idea what type it was. And also had no idea what the return type of client.iac_directory_scan() was.
Now that client is defined as client.ctx_obj.client, pyright knows it's a GGClient instance and thus knows the return type of client.iac_directory_scan().

Codecov Report
Attention: 11 lines in your changes are missing coverage. Please review.

Comparison is base (5801d88) 91.61% compared to head (90f582f) 91.58%.

Files
Patch %
Lines

ggshield/cmd/iac/scan/ci.py
0.00%
4 Missing :warning:

ggshield/cmd/iac/scan/precommit.py
25.00%
3 Missing :warning:

ggshield/cmd/secret/ignore.py
0.00%
3 Missing :warning:

ggshield/cmd/iac/scan/prereceive.py
50.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #826      +/-   ##
==========================================
- Coverage   91.61%   91.58%   -0.04%
==========================================
  Files         168      168
  Lines        6919     6928       +9
==========================================
+ Hits         6339     6345       +6
- Misses        580      583       +3

Flag
Coverage Δ

unittests
91.58% <73.80%> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Bump framework version

Purpose
Bump framework version

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/9493771780

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/9493771780
Status: success


[improve][client] Remove default 30s ackTimeout when setting DLQ policy on java consumer

Fixes #19134

Motivation
The java client automatically sets a 30s ackTimeout when a deadLetterPolicy is configured. This behavior was added before there was any ability to negativeAcknowledge. Now that negativeAcknowledge exists, it is unnecessary. Furthermore, it is confusing and inconsistent - more details in the issue.
Modifications
Removed setting ackTimeoutMillis in java ConsumerBuilder when a deadLetterPolicy is set.
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as ConsumerBuilderImplTest.
Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[x] doc
[ ] doc-required
[ ] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

/pulsarbot run-failure-checks

ConsumerBuilder still has the following javadoc
By default, the acknowledgment timeout is disabled (set to `0`, which means infinite). When a consumer with an infinite acknowledgment timeout terminates, any unacknowledged messages that it receives are re-delivered to another consumer.
Since 2.3.0, when a dead letter policy is specified and no ackTimeoutMillis is specified, the acknowledgment timeout is set to 30 seconds.

I presume this is no longer applicable given these changes, so should be removed as well.
Can this be confirmed before I write a ticket/PR.

@GerMoranOverstock - yes, that Javadoc should be updated in light of this PR. Are you interested in contributing the PR to remove those lines?

@GerMoranOverstock - yes, that Javadoc should be updated in light of this PR. Are you interested in contributing the PR to remove those lines?

Can do.


How do I get the bounding boxes for my new dataset of images from an existing pretrained model?

I want to use a pretrained resnet model trained on Imagenet to get the extract the bounding boxes for my new dataset. In the current pipeline, I am able to extract them for pascal_voc or coco or imagenet. But how can I extract it for new set of images?

@jainshobhit please refer to demo.py


[MANX-434][StyleCop] Fix all the warnings in Dutch Parsers

Reorder fields, properties, methods and constructors
Add and remove spaces when needed
Remove unnecessary parenthesis
Reorder using statements

Replaced by #1446


Multi-input transaction doubt

Hi everyone,
I have a doubt related to multi-input transactions. Where the transaction is signed, the index of the input to be signed is requested in the function call:
sign(tx, i, private_key)
I don't figure out what it's used for. Is not the whole tx signed (or at least all the inputs and outputs) in order to avoid that any input or output could be modified after signing it?
Thank you.

I've figured out for what is needed at the end.
The signature is stored in the SigsScript field of each tx.


Error Full Screen Mode

Error : exit Full Screen Mode
problems->IDE Visual Studio Code
[os-linux-debian-parrot.]

Which version of VS Code is this? Please include a screenshot of the error.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


v0.5.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/61487
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.5.0 -m "<description of version>" 0988d49370615ace59211635b481cd42d407f524
git push origin v0.5.0


Clarify the role of esoteric programming languages

Esoteric languages are a popular enough idea to warrant their own list.  I propose that this list touch upon the idea, but ultimately link to this or similar when it's ready.  Also, I added Brainfuck because you're not allowed to say "esolang" without mentioning it in the same sentence.
What does this project do?
No project (unless you count me adding Brainfuck to the list); this clarifies the scope of the list.
Why is that entertaining?
Esolangs are great
So great, they would drown this list
It's for your safety
How hard did you laugh? Was it just a silent giggle or was it full blown laughing and howling and screaming "OH MY GOD! EVERYONE! OH MY GOD! THIS IS THE FUNNIEST THING EVER! YOU'VE GOT TO SEE THIS!!!"
Not all that relevant here.  I giggled a bit with that haiku, I guess.

I'm not sure if a section description is really needed.
First reason being that all the other sections are already without descriptions so to keep it consistent Languages section should also be without one. Second reason because I really hope that people realise not to use this in production since it is after all a fun list 😃
Perhaps just change the name of the section to Esotheric languages but without the description? That should be enough for people to get the basic idea what these languages are 😁

@JesseTG could you please comment on my suggestion? 🤠

Crap, didn't notice the ping, sorry.
The description itself isn't important; moreso is leaving the bulk of information about esolangs to a dedicated list, since the subculture around them is vast and capable of drowning out this one.

Imagine a hypothetical awesome-ubuntu list.  There are many Linux resources out there, and the vast majority of them are relevant for Ubuntu.  But would you really need to list them all?  Why not stuff them in a dedicated awesome-linux list?

I'm in favor of the separate esolangs list because it has so much of its own content (and useful subsections). However, maybe it would be best to remove the description until that list is ready, and just add Brainfuck here for now (since it's a classic esolang and deserves mention).

@JesseTG I agree that we are not trying to collect esoteric languages here. There already is an awesome list of esoteric langauges.
We just sometimes pop a few in that are funny and somewhat current 😄

@JesseTG I agree that we are not trying to collect esoteric languages here.
Okay, glad we're on the same page.

There already is an awesome list of esoteric langauges.
Yep, I just didn't want to be specific until it was finalized.  I imagine by the time we finish this conversation that list will be ready, anyway.

We just sometimes pop a few in that are funny and somewhat current :smile:
I can get behind that if it's limited to absolute star players.  I wouldn't consider the three currently listed as such, though.


Kraken2 classification % goes down after adding more genomes

Hi there,
I've got the db-update functionality of the pipeline working, and I recently added about 4,000 genomes from JGI GOLD to the pre-made GTDB_release207 custom database. My issue is that the database is now classifying a smaller percentage of sample reads than it did before. Initially, I thought that the issue might be that my sample TSV's taxonomy column only had genus and species names, but I've repeated the process after expanding the taxonomy to mirror that of the metadata used for GTDB_release207, and I haven't seen any change. Any guesses about why this might be? I'll attach my sample TSV here as a .txt file
JGI_downloads_data_distinct_name_acc_premade_filter_tax_fixed.txt

How much overlap is there between the 4k genomes that you added and the existing genomes in the database? Particularly, was is the taxonomic and ANI distance between your new genomes and the existing genomes?

We don't have those distances calculated yet, but the genomes that we're adding in our sample TSV are all soil-associated genomes with NCBI taxIDs that weren't in the pre-built GTDB. We selected them from the JGI GOLD repository with the goal of maximizing the ecosystem-specific diversity of the database. Ostensibly, there shouldn't be all that much overlap

It would be best to check. The simplest explanation is that you have too many highly similar references, which is reducing the ability of Kraken2 to classify down to the most finely resolved taxonomic levels

Much appreciated! I'll start taking steps to prepare to incorporate that analysis. My supervisor on this project and I are discussing whether we might be able to use the fastANI package to investigate that possibility, but we have a couple of reasons for thinking that low genomic distance between our existing database and the genomes in the sample TSV may not be a problem in our dataset. I'm going to get my notes together (as well as some data and a couple of files) and try to present the issue with more detail in a follow-up issue soon. Thanks in advance!


Extending the number of system parameters

What problem does this solve or what need does it fill?
Currently, Bevy has a hard cap on how many queries and resources a specific system can access. Whether this is on purpose or just an arbitrary limit I don't fully know. I've been getting around this limit by splitting large systems into several smaller ones, though for a specific setup system I have created it's pretty difficult to be able to do that. Raising the cap by even 5 more queries / resources would help me significantly in having complex setups.
What solution would you like?
Either raising the limit on Bevy systems, or maybe making a way to query several unrelated resources at once.
What alternative(s) have you considered?
I know that breaking my systems into smaller systems is usually the way to go, it just becomes difficult with increasingly complex setups.
Additional context
Any other information you would like to add such as related previous work,
screenshots, benchmarks, etc.

Using #[derive(SystemParam)] helps with that. It enables putting several parameters in a single struct. Though I'm not sure it works in 0.5 :V

Tuples of system parameters are considered as system parameters, so you can have as many parameters by nesting them in tuples.

Fundamentally, this is caused by rust's lack of variadic tuples, and this limitation causes problems elsewhere as well, such as Clone only being implemented for only up to 16-tuples. Luckily, there are various ways around this limitation:

Using #[derive(SystemParam)] you can implement the SystemParam trait for your structs. Example:

#[derive(SystemParam)]
struct MySystemParam<'w, 's> {
    res: Res<'w, SomeResource>,
    query: Query<'w, 's, &SomeComponent>,
}

fn my_system(params: MySystemParam, alternate_res: Res<SomeOtherRes>) {}

You can put an unlimited amount of system parameters in the struct.

Using nested systemparam tuples: all tuples up to 16-tuples where all fields are system parameters are also valid system parameters, and coincidentally you can put tuples inside other tuples, getting an arbitrary number of system parameters:

fn my_system(params: (Res<Something>, (Query<&Stuff>, (/* and here you can just keep going*/)))) {}

Thank you, should I close this?

We could run the macros on tuples to a higher number behind a feature flag, like diesel does for large number of columns. Keeping the default at 16 but allowing users to have more at the cost of increased compile time

Closing this issue for now, we could open a separate issue for having such a feature flag later on.

Good call. I think making this configurable might even be an anti-feature. Better to have everyone working around the same constraints than having a free for all in the ecosystem.


Updates

Hi Thank you for this GREAT package.
It works great on iOS simulator, unlike Connectivity_plus package which doesn't work properly on it.
Could you please update it to Dart 3, and maintain this package in the future please.
I've been using your package for my projects for the past 6months and will intend to continue doing so.
Kind regards
Chris

Hi Thank you for this GREAT package.

Thanks for using this package

Could you please update it to Dart 3

I believe the package is already Dart 3 compatible and doesn't have anything to update

maintain this package in the future please.

I'm planning to change the working of the package and upload a breaking change version (major version).
I'll try to maintain the package time to time. PRs are always welcomed tho.


HMR on service worker

Describe the bug
I'm trying to add HMR to a service worker, I don't know if I can do that, right now it is failing.
The sw code:

The client error:

The failing code:

Reproduction
Here the branch on my repo: https://github.com/userquin/vite-plugin-pwa/tree/feat/add-development-support
pnpm installed globally required and node 12+, I'm testing with node 15 via nvm: once cloned and checkout feat/add-development-support  execute pnpm install && pnpm run build from root folder.
To run the sw example on dev, execute, also from root folder, pnpm run example:dev:sw.
Open the app in Chrome, it is registered with type: 'module'.
If you remove the import.meta.hot from examples/vue-basic-inject-manifest/src/sw.ts, the service worker will work.
The logic for the plugin can be found on src/index.ts, search last plugin (name: 'vite-plugin-pwa:dev-sw'), the internal logic on src/dev.ts: the example on examples/vue-basic-inject-manifest.
System Info
System:
    OS: Windows 10 10.0.19042
    CPU: (16) x64 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
    Memory: 49.51 GB / 63.95 GB
  Binaries:
    Node: 15.11.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - C:\Program Files\nodejs\yarn.CMD
    npm: 7.6.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 95.0.4638.54
    Edge: Spartan (44.19041.1266.0), Chromium (94.0.992.50)
    Internet Explorer: 11.0.19041.1202

Used Package Manager
pnpm
Logs
Since it is on client, here the logs on dev tools (see screenshots):
Uncaught ReferenceError: HTMLElement is not defined
    at overlay.ts:118

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

https://github.com/lencx/vite-plugin-rsw/issues/25#issuecomment-1049274571

Related:  https://github.com/vitejs/vite/issues/7163 and  https://github.com/vitejs/vite/issues/2248

PR https://github.com/vitejs/vite/pull/9064 fixed for me the HTMLElement is not defined error with HMR on web workers. Perhaps that would also fix the issue on service workers?

PR #9064 fixed for me the HTMLElement is not defined error with HMR on web workers. Perhaps that would also fix the issue on service workers?

window is not defined in WebWorkers  https://github.com/vitejs/vite-plugin-react-swc/issues/163 still happens

I am now hitting the issue with $RefreshReg$ as well, after updating Vite to fix the one with overlay.ts
trans-utils.tsx:5 Uncaught ReferenceError: $RefreshReg$ is not defined

My stack trace is on a random (the first in the dependency graph maybe?) bit of JSX.
Has anyone come up with a solution?

The way to solve this is by adding a side-effectful module that you import before any other modules in your worker.
See initializeWorker.tsx and the example usage in a worker.

PR #9064 fixed for me the HTMLElement is not defined error with HMR on web workers. Perhaps that would also fix the issue on service workers?

The issue is now with react-refresh (I think?)
@react-refresh:367 Uncaught ReferenceError: window is not defined
    at @react-refresh:367:1

which is this line

I am still having this issue, after trying to migrate from rewired version of react create app.
The fix by @cpojer alone did not work, I also had to disable the react plugin... which makes vite painful to use while developing a large project.
How can Vite be so popular without having this right?!
It seems to be due to random imports (which do not use jsx) which then, for whatever reason, bundles react-refresh with them.
No HMR is sort of a dealbreaker on a large project like ours.

The issue is now with react-refresh (I think?)
@react-refresh:367 Uncaught ReferenceError: window is not defined
    at @react-refresh:367:1

@ashleyww93 Running into the same issue with a new SharedWorker I'm working on. Was worried it was due to some transitive import, which sounds likely. Also wondering if rolling back Vite a few versions would have any effect.

The issue is now with react-refresh (I think?)
@react-refresh:367 Uncaught ReferenceError: window is not defined
    at @react-refresh:367:1

@ashleyww93 Running into the same issue with a new SharedWorker I'm working on. Was worried it was due to some transitive import, which sounds likely. Also wondering if rolling back Vite a few versions would have any effect.

We couldn’t find the import that causes this for us.
We are importing this as a side effect and it’s now working well.
https://gist.github.com/ashleyww93/12f8350ecc552c1d29ce93271147f325

We couldn’t find the import that causes this for us.
We are importing this as a side effect and it’s now working well.
https://gist.github.com/ashleyww93/12f8350ecc552c1d29ce93271147f325

Interesting, it's defined now, but thinks it's being loaded twice due to the presence of $RefreshReg$
if (window.$RefreshReg$) {
  throw new Error(
    "React refresh runtime was loaded twice. Maybe you forgot the base path?"
  );
}

Assuming you aren't hitting that issue? I'm going to just try setting it to undefined or something falsey.


Compiled ejb-app does not start

I've built ejb-app using this instructions. Even more I tried to rebuild it with mvn clean install with no luck.
When I try to launch my ejb-app, it throws:
dyld: Library not loaded: @rpath/libstd-03b901326ae24853.dylib
  Referenced from: /Users/User/.cargo/bin/ejb-app
  Reason: image not found
[1]    32738 abort      /Users/User/.cargo/bin/ejb-app

otool -l /Users/User/.cargo/bin/ejb-app showed that the path with required libstd-03b901326ae24853.dylib was not included into rpath. I could fix it with:
install_name_tool -add_rpath /Users/User/.rustup/toolchains/stable-x86_64-apple-darwin/lib/ /Users/User/.cargo/bin/ejb-app, but after that another error appears:
dyld: Symbol not found: __ZN10serde_json2de5POW1017hb458eff36f998f95E
  Referenced from: /Users/User/.cargo/bin/ejb-app
  Expected in: /Users/User/Desktop/exonum/exonum-java-binding/exonum-java-binding-core/rust/target/debug/libjava_bindings.dylib
 in /Users/User/.cargo/bin/ejb-app
[1]    32834 abort      ejb-app

Inspecting all available libjava_bindings.dylib (nm -gU /Users/User/Desktop/exonum/exonum-java-binding/exonum-java-binding-core/rust/target/debug/deps/libjava_bindings.dylib.dSYM/Contents/Resources/DWARF/libjava_bindings.dylib) I could find the one which has required symbol __ZN10serde_json2de5POW1017hb458eff36f998f95E, but unfortunately it's impossible to link ejb-app with this library (install_name_tool -add_rpath /Users/User/Desktop/exonum/exonum-java-binding/exonum-java-binding-core/rust/target/debug/deps/libjava_bindings.dylib.dSYM/Contents/Resources/DWARF/ /Users/User/.cargo/bin/ejb-app):
dyld: Library not loaded: @rpath/libjava_bindings.dylib
  Referenced from: /Users/User/.cargo/bin/ejb-app
  Reason: no suitable image found.  Did find:
	/Users/User/Desktop/exonum/exonum-java-binding/exonum-java-binding-core/rust/target/debug/deps/libjava_bindings.dylib.dSYM/Contents/Resources/DWARF/libjava_bindings.dylib: mach-o, but wrong filetype
[1]    33001 abort      ejb-app

What am I doing wrong? Any suggestions?

Hi. It looks like you've built the ejb-app with toolchain other than 1.26.2. I'd suggest specifying the exact toolchain version in the build command, smth like cargo +1.26.2 install --debug --force. And you can check it by executing ./start_cryptocurrency_node.sh (within the same exonum-java-binding-core/rust/ejb-appdir) which prepares all required environment variables and starts cryptocurrency demo based on ejb-app.

It also seems that LD_LIBRARY_PATH must be set to launch the application, the instructions for v0.3 are available here: https://github.com/exonum/exonum-java-binding/blob/v0.3/exonum-java-binding-core/rust/ejb-app/TUTORIAL.md#step-1-configure-environment

It works with specific toolchain version provided in the build command, thanks!

Great, feel free to ask if you have more questions.


add option to use new debian repo

Another PR ss part of grand debian repo improvment plan:
notion.so/o1labs/Enterprise-debian-repository-118e79b1f91080cc98cddb337347413a
In order to leverage security and robustness of our debian repository we should split it into three new repos:

unstable for packages that are still under tests. For example when we are running release pipeline package should be uploaded to unstable debian repository.
stable - target repo for promotion. After we are sure our packages in unstable repo are ready for community and partners, we will transfer them to stable repository. Thanks to that separation, none unstable package uploaded from personal branch or nightly can make conflict with stable one.
nightly - repo for packages built by nightlies pipeline. Those packages can be pickup up by anyone who wishes to experiment with newest state of our code

Introducing above separation is a lesson learnt from situation where unstable package could create conflict with stable package by version conflict (which can be set based on tag). Also we learn that frequent uploads from CI can cause deadlocks which
a) blocks entire repository from uploading
b) can create conflict in Release file checksum and only manual intervention can heal it.
Note that this PR only introduces new repositories but it is still backward compatible with old process

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-nightly-me

!ci-build-me

!ci-build-me

!ci-build-me

Nightlies are green:
https://buildkite.com/o-1-labs-2/mina-end-to-end-nightlies/builds/3079


Is Search still supported in praw 4.4?

I saw the snippet below on stackoverflow:

import praw
r = praw.Reddit(user_agent='Getting the data!!')
r.login("username","password",disable_warning=True)
results=r.search('whatever', subreddit=None, sort=None, syntax=None, period=None)
for x in results:
    print x

It seems that this snippet is outdated. Because I can't find the search function in praw 4.4.0.. I didn't find the search-related API in the document of praw..
Is this feature still supported?

Looks like you'll want to use the search method of a Subreddit object. To search all subreddits, you can just use reddit.subreddit('all'), as shown in the example.

Got it, thanks!

Thanks for responding @leviroth. You're awesome.


Uncaught Exception

How do we catch this error ?
I need a way to avoid this crashing the nodejs application when there is network issues or the stun/turn server is restarted.
channel.onerror is not triggered, so must be something else
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^
TransactionFailed [Error]
at Transaction.value [as responseReceived] (/mnt/data/vscode/config/workspace/code/jupyter-agent/node_modules/werift/lib/ice/src/stun/transaction.js:79:47)
at TurnClient.handleSTUNMessage (/mnt/data/vscode/config/workspace/code/jupyter-agent/node_modules/werift/lib/ice/src/turn/protocol.js:259:33)
at TurnClient.datagramReceived (/mnt/data/vscode/config/workspace/code/jupyter-agent/node_modules/werift/lib/ice/src/turn/protocol.js:278:18)
at transport.onData (/mnt/data/vscode/config/workspace/code/jupyter-agent/node_modules/werift/lib/ice/src/turn/protocol.js:240:18)
at Socket. (/mnt/data/vscode/config/workspace/code/jupyter-agent/node_modules/werift/lib/ice/src/transport.js:80:22)
at Socket.emit (node:events:514:28)
at UDP.onMessage [as onmessage] (node:dgram:933:8)
at UDP.callbackTrampoline (node:internal/async_hooks:130:17) {

duplicate https://github.com/shinyoshiaki/werift-webrtc/issues/364


Response not being set properly

[SwaggerResponse("200", typeof(GroupDto), Description = "heaaalloooo")]
public Task<HttpResponseMessage> GetGroup(string groupId)

"/groups/{groupId}": {
      "get": {
        "tags": [
          "Groups"
        ],
        "summary": "Returns a Group object associated with the specified group identifier.",
        "operationId": "Groups_GetGroup",
        "parameters": [
          {
            "type": "string",
            "name": "groupId",
            "in": "path",
            "required": true,
            "x-nullable": false,
            "description": "The identity of the group that is being retrieved."
          }
        ],
        "responses": {
          "200": {
            "description": "heaaalloooo",
            "schema": {},
            "x-nullable": true
          },
          "404": {
            "description": "No group could be found with the specified identifier.",
            "schema": {},
            "x-nullable": true
          }
        }
      },

then under definitions...
"groupDto": {
      "type": "object",
      "title": "GroupDto",
      "additionalProperties": false,
      "properties": {
        "members": {
          "type": [
            "array",
            "null"
          ],
          "items": {}
        },
        "location": {
          "type": [
            "null",
            "string"
          ]
        },
        "jobTitle": {
          "type": [
            "null",
            "string"
          ]
        }
      }

Any idea why I'm not getting any schema reference to the groupDto definition?

Debugging shows that within OperationResponseProcessor it gets to line 109:
response.Schema = await context.SwaggerGenerator.GenerateAndAppendSchemaFromTypeAsync(returnType, typeDescription.IsNullable, null).ConfigureAwait(false);
response.Schema does not contain the GroupDto definition, but response.Schema.ReferenceSchema does. I'm very clueless how the serialization process works.

In fact, after debugging more thoroughly, all the ActualResponseSchema values are correct when going through my DocumentProcessor. But it somehow doesn't serialize the reference

I didn't realize I needed to call the .ToJson() on the SwaggerDocument. Assumed it would know how to serialize itself or have a custom converter.


Error alert when activiting a new theme

When I upload a new theme it will show error like this

But actually, there's no {{@blog}} in files.

More information:

Ghost Version: 2.23.1

Environment development

Node Version: v10.13.0

Browser/OS: Firefox 67.0 / Chrome 74.0.3729.169 (Official Build) (64-bit)

Database: sqlite3

@hzb {{@blog}} itself is never used as it's a holder for other properties such as<EMAIL_ADDRESS>you can see the full list here https://docs.ghost.org/api/handlebars-themes/helpers/site/. You should adjust your search to look for {{@blog instead. Also if you click on the error you will get more information such as which files are failing the deprecation check.
Closing as this is not a bug. If you feel the error message is too confusing feel free to open an issue to that effect on the theme-validation project https://github.com/TryGhost/gscan 🙂


Transport service

Description
To avoid passing the object of extensionRunner in ExtensionsRunner main function, move all of the required methods and variables to NettyTransport file
Address comment from previous PR.
Issues Resolved
https://github.com/opensearch-project/opensearch-sdk-java/pull/166
https://github.com/opensearch-project/opensearch-sdk-java/issues/116
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #170 (42f5281) into main (8fbcc6e) will increase coverage by 0.43%.
The diff coverage is 80.00%.

@@             Coverage Diff              @@
##               main     #170      +/-   ##
============================================
+ Coverage     66.00%   66.44%   +0.43%
  Complexity       96       96
============================================
  Files            25       25
  Lines           456      456
  Branches         13       12       -1
============================================
+ Hits            301      303       +2
+ Misses          147      146       -1
+ Partials          8        7       -1

Impacted Files
Coverage Δ

...main/java/org/opensearch/sdk/ExtensionsRunner.java
63.23% <50.00%> (ø)

...c/main/java/org/opensearch/sdk/NettyTransport.java
100.00% <100.00%> (+7.14%)
:arrow_up:

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

That method should take a threadPool parameter too

I can't access the branch with the changes for some reason.  The only branch I see on @mloufra 's fork is main.

I can't access the branch with the changes for some reason. The only branch I see on @mloufra 's fork is main.

I fork our sdk repo again this morning. That's why only main branch in my fork repo.

I fork our sdk repo again this morning. That's why only main branch in my fork repo.
@mloufra you should close this PR and raise again with the new fork repo as you won't be able to access transportService branch anymore on your fork.

I fork our sdk repo again this morning. That's why only main branch in my fork repo.

@mloufra you should close this PR and raise again with the new fork repo as you won't be able to access transportService branch anymore on your fork.

Thanks.


Error in checking node status

Excuse me, in the operation of oasis node control status - a UNIX / node / data of run a non validator node = = > checking node status/ internal.sock  When the command is executed, an error is reported: failed to query entities "error = RPC error: code = unavailable desc = connection error: desc = \ " transport: error while dialing dial UNIX / serverdir / node/ internal.sock : connect: no such file or Directory, where is the problem?

I think this means that the socket is not there (e.g. wrong path or node is not up). Can you post a full example?

Thank you, it has been solved, but I did not remove the parenthesis when Adding the address of the seed node


Add superenv for Linuxbrew [WIP]

@Linuxbrew/core As the title says. In this version, I've copied Library/Homebrew/shims/linux/super/cc from the Mac version and modified it just enough to get it up and running. It'll require much more work to bring it up to pace with --env=std in Linuxbrew.

My last commit makes --env=std the default on Linuxbrew, so --env=super is opt-in. With that change, we should be able to merge this PR now, and work on improving superenv together.

Succeeded on Linux. Unrelated (I think) error on Mac:
Error:
Satisfy Dependencies and Requirements::depends_on macos#test_0001_understands depends_on macos: <array>:
Hbc::CaskError: It seems there is already an App at '/tmp/homebrew-tests-20170215-10426-1fzztn2/prefix/appdir-1487198972-634/Caffeine.app'.

https://travis-ci.org/Linuxbrew/brew/jobs/202017165#L469