Deadlock with many simultaneous  connections creations

We have a code which creates many connections in same time by multiply threads. The threads are then wait in synchronized block to create one more connection. We set the max connection with enough number to ensure the deadlock never happens however we observed the deadlock happens sometimes. Below is a simple code which produces the issue.
// Begin coding
volatile boolean doneSharedConnect = false;
final HikariConfig config = new HikariConfig();
/// setup config with connection parameters
config.setMinimumIdle(0;
config.setMaximumPoolSize(40); // This should be enough to prevent the deadlock
HikariDataSource hikariDataSource = new HikariDataSource(hikariConfig);
CompletableFuture<Void>[]  myThreads = new CompletableFuture[13];
       for (int i = 0; i < 13; ++i) { // we have only 13 threads and pool size is 40
            CompletableFuture.runAsync(() -> {
                         Connection threadConn =  hikariDataSource.getConnection(); // connection for every thread
                         if (!doneSharedConnection) {
                          synchronized(this) {
                              if(!doneSharedConnection) {// double check technique
                                   Connection sharedConn = hikariDataSource.getConnection(); // Deadlock happens here
                                   doneSharedConnection = true;
                                }
                           }
                         }
          });
        }
// Wait for all threads
CompletableFuture.allOf(myThreads).join();

// End coding

It is interesting that we set max pool to 40 and thread count = 13 but still we get the dead lock.
Env:
HiakriCP version: 3.4.2
Container: AWS Lambda
Any help for this issue?

@mabdelazim I do not understand your code at all.  You declare an array of CompletableFutures myThreads with size 13, but you never assign any of the CompletableFuture objects returned by CompletableFuture.runAsync() to elements of that array. And then you try to do CompletableFuture.allOf(myThreads).join();. It makes no sense, as all of the elements of myArray are not CompleteableFuture instances, they are still null.
Furthermore, you have declared a volatile variable, doneSharedConnect, outside of the lambda. This makes doneSharedConnect effectively final. So, I am suprised if that code even compiles, as the assignment of doneSharedConnection = true should fail to compile with the error: "Local variable i defined in an enclosing scope must be final or effectively final". You cannot assign a value to a final or effectively final field.
Can you provide actually working code?
For example, in your code above you create connections and assign them to threadConn, but that is a local variable that never survives the block, and so will be garbage collected, and therefore never closed. Therefore, if you run this lambda more than once, then you will exhaust all RDS connections, and the code will block (not deadlock). It is not until RDS times out the connections that you will be able to connect again.
None of these issues have anything to do with HikariCP.  The line that you indicate as a "deadlock" is merely a call that is blocking due to the inability to create new connections. Because you exhausted them in prior runs.

@brettwooldridge Sorry for providing incomplete code in the beginning.  In our application we use HikraiCP integrated with JOOQ library and the code is spanned among different functions and classes. I wanted here to simplify and abstract the code under concern to make it is easier for HikraiCp contributors to help me. I fixed the code now by handling your comments.
I appreciate you open the issue again unless you are highly confident it is not HikrariCP.issue.
My replay to your comments are:

doneSharedConnection is class member so it compiles and can be altered.
I assigned the myThreads objects correctly now.
I closed the connections after usage now.

Please also note in our usage with JOOQ, the connection is closed automatically in every Jooq statement execution


[BUG] Missing disconnect button if channel name string is too long.

Please describe the issue in detail and how to reproduce it, (preferably with screenshots).
Hey is me again :), i'm loving all about this theme and i wanted to give you some feedback about a bug that i found today while switching between some channels on my discord server.
The thing is that when you enter a channel with a long name, the button to disconnect from that channel will disappear because of the offset.
https://imgur.com/a/ByXnwon
I know a little about programming so i think a quick fix for this would be to verify the len of the channel name string and shorten it when is surpasses a certain amount of characters
Please include as much information as possible:

Which version of T1 do you have? (Themes tab and bottom of the user settings sidebar)
T1 v0.7.3

Which Discord client are you using? (Stable, PTB, Canary, ..)
Stable

Which platform are you on? (Windows, Mac, Linux, ...)
Windows

Which Discord Mod are you using? (BetterDiscord, Powercord, Vizality, ...)
BT

Do you have any other additional Themes or Plugins enabled?
BDFDB v1.8.4
PluginRepo v2.2.6
ShowHiddenChannels v3.0.2
ThemeRepo v2.2.7
ZeresPluginLibrary v1.2.32

Should be fixed now.
Thanks again


olm: 3.1.5 -> 3.2.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/olm/versions.
meta.description for olm is: "Implements double cryptographic ratchet and Megolm ratchet"
meta.homepage for olm is: "https://gitlab.matrix.org/matrix-org/olm"
meta.changelog for olm is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.2.1 with grep in /nix/store/nc03g9ngimdnp2s6qrrnff2m1jf25cn2-olm-3.2.1

directory tree listing: https://gist.github.com/664e3f41af2755881da4ec1ead39d6e9

du listing: https://gist.github.com/0a89b48f667cfe95c67f8b9780d6ea6c

Rebuild report (if merged into master) (click to expand)

67 total rebuild path(s)

17 package rebuild(s)

17 x86_64-linux rebuild(s)
17 i686-linux rebuild(s)
16 x86_64-darwin rebuild(s)
17 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
gomuks
matrixcli
mautrix-whatsapp
mirage-im
mtxclient
nheko
olm
pantalaimon
purple-matrix
python27Packages.python-olm
python37Packages.matrix-nio
python37Packages.python-olm
python38Packages.matrix-nio
python38Packages.python-olm
spectral
weechatScripts.weechat-matrix
weechatScripts.weechat-matrix-bridge

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nc03g9ngimdnp2s6qrrnff2m1jf25cn2-olm-3.2.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A olm https://github.com/r-ryantm/nixpkgs/archive/fd12c2efcdb6f7a83cecd864eeb9ad133915da16.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nc03g9ngimdnp2s6qrrnff2m1jf25cn2-olm-3.2.1
ls -la /nix/store/nc03g9ngimdnp2s6qrrnff2m1jf25cn2-olm-3.2.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

17 packages built:

gomuks
matrique (spectral)
matrixcli
mautrix-whatsapp
mirage-im
mtxclient
nheko
olm
pantalaimon
purple-matrix
python27Packages.python-olm
python37Packages.matrix-nio
python37Packages.python-olm
python38Packages.matrix-nio
python38Packages.python-olm
weechat-matrix-bridge (weechatScripts.weechat-matrix-bridge)
weechatScripts.weechat-matrix

Maintainer pings

Nheko works. I assume no incompatible api changes.

Result of nixpkgs-review pr 102667 run on x86_64-darwin 1

3 packages marked as broken and skipped:

mtxclient
nheko
weechatScripts.weechat-matrix-bridge

2 packages failed to build:

mirage-im
spectral

11 packages built:

gomuks
mautrix-whatsapp
olm
pantalaimon
purple-matrix
python27Packages.python-olm
python37Packages.matrix-nio
python37Packages.python-olm
python38Packages.matrix-nio
python38Packages.python-olm
weechatScripts.weechat-matrix


Get face representation of crop image

Hi,
How can I get a representation of a pre-cut image?
i.e to get a representation of the image without using any detector?
Thanks!

pass skip key to the detector_backend argument

Thank you for the quick reply!
Is there a way to align the image without using detector?
i.e pass the model the crop image without detector but use alignment?


fix for statusses

fix for statusses as discussed here
https://github.com/Mosibi/Midea-heat-pump-ESPHome/issues/35
Tested with "heating" only
for now I left zone 2 for what is it as I assume It's different per device.

Hi @bkbartk. I tested your code and it seems fine. I merged it, so that issue #35 is fixed. Thanks!


Build failure: step-cli

Steps To Reproduce
Steps to reproduce the behavior:

build step-cli

Build log
$ nix build github:NixOS/nixpkgs?rev=f95383724b9f736ff986c848a82b8f220ce1406f#step-cli --verbose
these 3 derivations will be built:
  /nix/store/w00x7fj5zmcmvpa8zcg4wrwcr2a9abh6-source.drv
  /nix/store/bbir65jdlw1xklrgzyc0jriynz2my07b-step-cli-0.27.2-go-modules.drv
  /nix/store/dlph1gwfz8ilwwmw3z4gmx06kfz0ay1r-step-cli-0.27.2.drv
building '/nix/store/w00x7fj5zmcmvpa8zcg4wrwcr2a9abh6-source.drv'...
error: hash mismatch in fixed-output derivation '/nix/store/w00x7fj5zmcmvpa8zcg4wrwcr2a9abh6-source.drv':
         specified: sha256-lM42KlTgOch6AwQIzvjQNH1wVfFikVI9rVgH2/2KyJE=
            got:    sha256-9w7rUtlLa1kl9oVboWZWj4eoZh+pPdGsEEQDWYdEMns=
error: 1 dependencies of derivation '/nix/store/dlph1gwfz8ilwwmw3z4gmx06kfz0ay1r-step-cli-0.27.2.drv' failed to build

Additional context
Not sure what happened. Did upstream force-push update the tag?
Notify maintainers

@isabelroses
@NickCao
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.36, NixOS, 24.11 (Vicuna), 24.11.20240723.2874fc4`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.5`
 - nixpkgs: `/nix/store/3azana74br85nvlq2zrcbc29rq8hsmxw-source`

Add a :+1: reaction to issues you find important.

seems to have built fine for me on latest, being 996ec7cce165075f1c1e6d9550630264a5773deb.
nix build -L github:nixos/nixpkgs/996ec7cce165075f1c1e6d9550630264a5773deb#step-cli


C# Input object creation explosion

Godot version
4.0.2
System information
Win10
Issue description
This was only tested in the .NET version.
It seems that the C# backend is creating an insane amount of objects when handling input events.
Moving the joy sticks for a few seconds makes the objects count (and the associated memory) go higher than it probably needs to.
It also spikes using keyboard or mouse input events, but it is more noticable with gamepads.
Steps to reproduce

Create a node and attached to it a C# script.
That script needs to override the _Input methods
Using an input controller (gamepad preferably, keyboard or mouse also acceptable)
Notice in the Debugger panel, under Monitor tab that the Objects count will spike quickly
Notice as well that the Memory increases significantly as well

Minimal reproduction project
The project contains a scene; the scene contains a Node3D and a C# script attached to it.
The script overrides the _Input methods.
InputObjects.zip

IIRC it was already reported and is due to how input is implemented, and GC

Duplicate of:

https://github.com/godotengine/godot/issues/75269
https://github.com/godotengine/godot/issues/72776

It is not clear from the linked issues if

this is something Godot can improve on
is it a known limitation of the .NET environment?
can these input events be reused instead of creating an new object?

Is there any actual issue caused by this behavior, beyond that number goes up and then it goes down again?
This is the expected behavior of any garbage collected system when creating and then no longer referencing a whole bunch of objects
No, because the handler could keep a reference to the input event after _Input returns.
Also creating the managed wrappers is really cheap, so caching them make no sense and the expensive underlying native objects have to be created anyways.

No issue as far as I can see. Only a consern of maximum efficiency/performance .


Update standard "development" version indicator to use 0xFF

Checklist (Please check before submitting)

[x] I reviewed the Contributing Guide.
[x] I reviewed the cFS README.md file to see if the feature is in the major future work.
[x] I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.

Is your feature request related to a problem? Please describe.
Historically, setting the Revision number to "99" indicates that the source code in question is a "development" version and thus hasn't been fully tested.
In https://github.com/nasa/osal/pull/824, we put this information in the Mission_Rev instead and set it to "0xFF". This pattern has a couple of problems:

It is not standard, cFE documentation needs to be updated
If a user changes the MISSION_REV while building on top of a development version, there is no way to know what the original version was by looking at source code. (eg x.y.z.99 is changed by a user to x.y.z.100) kudos to @skliper for this observation
Older telemetry or "ground" systems may be used to the two-character legacy number of "99" instead of "0xFF" and convert the value into a two-character string thereby cutting off the value.

Describe the solution you'd like

Revert to using the Revision number
Move from 99 to 0xff
Communicate the change to users

Describe alternatives you've considered
Keep Revision = 99
Additional context
Need to open related Issues in other cFS component repositories
Requester Info
Gerardo Cruz-Ortiz, NASA

This was discussed in today's CCB, and also in discussion on https://github.com/nasa/cFE/commit/e5be0612ad6bf9db09ddf640306a65292abce2d5
My concern is that all three numeric version numbers (major, minor, revision) are important for identification of what the real software baseline is, and important to keep this accurate within HK TLM, even for development versions.
Even if that baseline information may exist in the form of a string, this is not ideal because that string doesn't follow a strict format, nor is it easily possible to compare a string and determine simple things like "is this version newer than that one"?  Strings are OK for humans to read, but not so good for scripts.  For example, a feature/command may have been added in one version of the software, and a test script may need to know what version is running to decide whether or not to send a particular command.  So it is beneficial to make the version number meaningful for scripts and tools, not just humans, and strings don't work well in that regard.
Problem Context
Originally when versioning was discussed during the Bootes versioning cycle, the following was accepted as truth:

end-users should only deploy "official release" versions to their flight products as a baseline
software needed to self-report whether it was in fact an "official release" (deployable to flight products) or a "development" version (modified from that official release, including versions pulled from main branch on github at any given time).  In the latter case, it should self-report the official version it is based on.
end-users (and only end-users) should bump the "mission rev" value whenever they modify the software from its original form, to track the fact that it no longer matches the official release.

Because of rule (1) and (2) above it meant that use of MISSION_REV and the "development version" status became exclusive of each other.  That is, development versions would never change MISSION_REV, and conversely, those who might need to update MISSION_REV do not use development versions.  So it was a good fit to reserve the value 0xFF as a flag to indicate this status, since (it seemed like) this would never interfere with the original intent of this value.
However, as discussed at 2022-03-23 CCB, this is no longer the case, really.  Due to the release process timeline far exceeding most real project schedules and deadlines, it is not practical for end-users to wait for official release status.  As a result, use of MISSION_REV is now not as clean-cut - even tagged versions still need to report themselves as "development" - and users may need to use the MISSION_REV to track the fact that they've made a change, even when this field is already set to 0xFF.
In most open source projects, versions numbers are bumped up at the discretion of the development team, once milestones were met.  However, due procedures and policies unique to CFS, historically the development team has not been able to update the version number, because a version number update implied "official release" which in turn implied that the full release cycle was done, but this takes years.
Possible Solution
If the policies and procedures permit, the "official release" implication/designation could be associated with something other than the numeric version.  This would free the dev team up to bump the self-reported version numbers whenever meaningful functionality has been achieved and acceptance testing has passed, much like every other project manages version numbers.
The advantage is:

With much more frequent releases, end-users would be less compelled to use a mainline version for actual deployment (they actually can wait for a real version bump)
The major/minor/revision numbers being reported in TLM actually become meaningful again (since every version of CFE would not need to report itself as "6.7.0" anymore)
Could also adopt a versioning scheme where odd-numbered revisions indicate mainline development, and even-numbered revisions indicate stable points (i.e. where the full suite of acceptance testing was done, and all documentation was updated, etc).

In short, decoupling the notion of "what went through the complete/official SRA legal review process" and "what software is stable and high-quality such that end-users can deploy it and expect it to work" would do a lot of good, both for internal and external users.


What is DataOps and Why Data Engineers need it

NOTE: All 1st-time contributors should know Topic approval and PR submission does NOT guarantee your Topic/Article will be published. Our team of Peer Reviewers and Content Moderators will review all PRs that come in to make sure they adhere to the standard of quality we expect from the EngEd community.
We expect all community memebers to go through provided examples, resources, and previously published material before submitting content. As a rule of thumb, please only submit articles (pull requests) that are complete, formatted correctly, and include a fully polished article (ready to be published and error free).
All revisions and edits should be completed on your own forked repo (as to not take up room in the queue). Any PR that is submitted incomplete (meaning not ready to be published as is) will be closed. A PR being closed does NOT mean the article can not be published (or fixed) it simply means that the edits, revisions, and fixes will happen outside of the queue.
Topic Suggestion
What is DataOps and Why Data Engineers need it
Pre-submission advice
By following all our pre-submission advice and reviewing our Resources folder, you will maximise your chances of your topic being approved.
We ask that you please be patient as our team works through approving and publishing all articles/tutorials in a timely manner.
Allow 1-3 days for a topic to be reviewed and/or approved - allow 3-7 days for an articles to be reviewed and/or published (subject to vary depending on volume and/or backlog of articles).
Be sure to visit our Resources Page for tools, resources, and example articles that will help you propose and write a successful article.
Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
Writing sample(s):
Include any links or writing samples - to help our team better gauge your writing quality.
Proposal Submission
Proposed title of article
What is DataOps and Why Data Engineers need it
Use keyword research to improve your article's SEO.
Proposed article introduction
DataOps (Data Operations) is the practice of data analysts, data scientists, developers, and operations participating together in the entire lifecycle from data collection to design, development, and production support. It brings together DevOps teams with data engineers and data scientists to provide the tools, processes, and organizational structures to support the data-focused enterprise.
The purpose of DataOps in the enterprise is to increase analytic velocity and create analytical outcomes for data consumers.
DataOps aims to streamline application design, development, and maintenance based on data and data analysis. The goal is to improve the management of data and products created and align these improvements with the business's goals.
This article will first look at the challenges for which we need DataOps, and dig deeper on what is DataOps and why data engineers need it.
Key takeaways

Overview of DataOps
Who is a DataOps engineer
DevOps vs DataOps
DataOps best practices
Implementing DataOps
Why data engineers need DataOps

Article quality
This is a more detailed article about DataOps as the demand for data products and access to data assets is growing exponentially.  It will look at the benefits of DataOps, the steps to implementing a successful DataOps practice, and give insights into why data engineers need DataOps. This article will be understandable at a beginner level and provide unique and quality content.
References
Please list links to any published content/research that you intend to use to support/guide this article.
Conclusion
Finally, remove the Pre-Submission advice section and all our blockquoted notes as you fill in the form before you submit.
We look forwarding to reviewing your topic suggestion.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

good topic @essy258  - approved. Thanks for submitting your article and we look forward to reviewing and hopefully publishing it. I’m sure our readers will enjoy and find your article very beneficial.
Also, in future suggestions please remove the Pre-submission advice as stipulated in the conclusion. This will allow the CMs get your content easily.


changed path to karma bin: solve ENOENT error

I had this error which prevented client unit tests to run:
W20141217-10:16:53.161(-5)? (STDERR) events.js:72
W20141217-10:16:53.162(-5)? (STDERR) throw er; // Unhandled 'error' event
W20141217-10:16:53.162(-5)? (STDERR) ^
W20141217-10:16:53.166(-5)? (STDERR) Error: spawn ENOENT
W20141217-10:16:53.167(-5)? (STDERR) at errnoException (child_process.js:1000:11)
W20141217-10:16:53.167(-5)? (STDERR) at Process.ChildProcess._handle.onexit (child_process.js:791:34)

What operation system do you use and what Meteor version? On Mac OS X it's still a : for me. Maybe it's inconsistent.

Ok, in the devel version of Meteor Core, I also get the error.

Right, I should have mentionned that. I'm on linux 64 and I use the 1.0.4
release of Meteor.
Le sam. 14 mars 2015 à 02:31, Jonas Aschenbrenner<EMAIL_ADDRESS>a écrit :

Ok, in the devel version of Meteor Core, I also get the error.
—
Reply to this email directly or view it on GitHub
https://github.com/Sanjo/meteor-karma/pull/6#issuecomment-79653238.

Fixed via https://github.com/Sanjo/meteor-karma/commit/c2835c71d169295956c37caaf0bb714c3cf18a90.


Update the help docs index to still point to 1.9

After 1.10 is officially released we will change this index again. For now, 1.9 docs are still considered the latest stable.

This update doesn't seem necessary anymore with the new docs. I still see the docs pointing to release-1.9 as the latest release.
@galexrt How will we mark the 1.10 docs as the latest release when we are ready?

@travisn You should be able to just update the urls in this repo for the getting started and docs button each.


Npm build in local seem has some problem

I want to disable the lint feature, so I remove the source code below in QueryEditor.js:
lint: {
   schema: this.props.schema
},

and
this.editor.options.lint.schema = this.props.schema;

Then I builded my package : npm run build.
After that I found the code of graphiql.css in the root path is quit different with the version which I installed from npm(0.9.3).
The different is shown in the online-compare link: https://www.diffchecker.com/aUsmRSFo
And I inited the source path with a yarn command.
What is the problem lead to the case?

@bakso whoa, I have no clue - @wincent are you familiar with this maybe?

Somewhat familiar. I know we disabled source maps in https://github.com/graphql/graphiql/commit/99d926e5e5245c80f67ee5fbdd1235fd3fcb2c16 which accounts for some of the discrepancies. The other thing is it is normal to expect that a build from master will often deviate from the last-released version, given to changes made in commits after the release. @bakso: were you comparing the CSS from the released 0.9.3 package and a local Git checkout of tag v0.9.3?

Also I forgot to ask at the time, but does this actually lead to any rendering issues?
I'm going to close this for now due to inactivity - thanks for the report though! Feel free to go ahead and reopen the issue if there is any issues.


289 Canvas-Info service is filled with endpoints retrieved in DependentAPI Operator

GitHub Issue #289 : DependentAPI Operator adds discovered service endpoints info the Service-Inventory accessible under info.canvas.svc.cluster.local.
GitHub Issue #338 : Executing and publishing Unit-Tests in Docker build is now possible.

I have tested this locally by:

Deploying a ProductCatalog component to act as the downstream ProductCatalog with name wholesale-catalog
Deploying a second ProductCatalog component with name federated-catalog. This declares a dependency for a downstreamproductcatalog.
The tmforumodacanvas/dependentapi-simple-operator:0.2.3-issue289b microservice successfully created a Canvas Info record in the Service Inventory at http://info.canvas.svc.cluster.local/tmf-api/serviceInventoryManagement/v5. I manually checked this by querying the Service Inventory. It also updated the DependentAPI record to show this dependency had been met.
I added a catalog record to the wholesale-catalog and then queried the 'catalog' API on the federated-catalog component - the API call successfully returned the  catalog record from the wholesale-catalog.

So the base scenario works :)

the Service Inventory at http://info.canvas.svc.cluster.local/tmf-api/serviceInventoryManagement/v5
I wanted to change this to http://info.canvas.svc.cluster.local without any path. So the service functions are then available as http://info.canvas.svc.cluster.local/service

There is a complimentary reference component that integrates with this Canvas.Info service:
https://github.com/tmforum-oda/reference-example-components/releases/tag/productcatalog-1.2.2


moved eventtypes & created app_event

@BenDenger after removing the generic layer i would suggest to just keep the event dtos when #428  is merged


pedestrian config

Hi, thanks for your great work, but could you please share your pedestrian config for training, as I only got 42.22 % 	35.14 % 	32.92% accuracy.
I just wonder how you achieve 54.64 % 	44.27 % 	40.23 % results on KITTI.
Many thanks for your help.

Hi, thanks for your great work, but could you please share your pedestrian config for training, as I only got 42.22 % 35.14 % 32.92% accuracy.
I just wonder how you achieve 54.64 % 44.27 % 40.23 % results on KITTI.
Many thanks for your help.

Hello, I am a beginner and I am not very familiar with deep learning knowledge. Can you provide me with a pedestrian model? Thanks a lot

Hi, thanks for your great work, but could you please share your pedestrian config for training, as I only got 42.22 % 35.14 % 32.92% accuracy.
I just wonder how you achieve 54.64 % 44.27 % 40.23 % results on KITTI.
Many thanks for your help.

Hello, I am a beginner and I am not very familiar with deep learning knowledge. Can you provide me with a pedestrian model? Thanks a lot

Hello @FrankCAN , how did you train the model to get pedestrian results and for how many iterations/epochs ?
I get these results with same training iterations as in configuration
Pedesterian: 55.44% 	51.58% 	47.78%

Hello @FrankCAN , how did you train the model to get pedestrian results and for how many iterations/epochs ?
I get these results with same training iterations as in configuration
Pedesterian: 55.44% 	51.58% 	47.78%


Rewrite the GREL parser with a parser generator

The code to parse GREL expressions is was written manually and not using any parser generator.
We could consider rewriting it using a parser generator, such as javacc. This involves writing a grammar for the language and using a code-generation tool to generate the parser out of the grammar. This is widely regarded a best practice to write parsers for programming languages.
Among the benefits this would bring, I can think of:

ensure correctness of the parsing code more easily, avoiding bugs such as #2507, #3328 or #6364
use this opportunity to document the grammar of the language and offer it in a human-readable form to our users
make it easier to introduce new syntactic constructs, such as for #6384
remove a big chunk of rather complex code from our code base

Among the downsides, I can think of:

the introduction of a new dependency (probably compile-time only, so the packaged artifacts should not get bigger for our users)
probably a slightly longer build

Tagging @tfmorris who has been working in this area recently. Do you see this as a worthwhile pursuit? Assuming we want to do it, I think it would make for a good GSoC topic.

I wonder if this would or could open up options for supporting GREL syntax highlighting and/or help in the UI? See https://github.com/OpenRefine/OpenRefine/issues/153

Good point! Having a clear definition of the grammar would likely make syntax highlighting easier, and perhaps auto-completion too. Assuming we can use the same sort of grammar definition within JS libraries which would implement a client-side parser (which I haven't looked into).

p.s. in the context of GSoC, it could be positioned as an exploratory investigation / prototyping exercise, rather than something which is intended to produce production code in one go.

Thanks for the feedback!
I agree it's not just about codifying the existing behavior. From my perspective I think it would totally be expected that the new parser would differ from the existing one in certain ways, but those ways should be clear improvements or bug fixes over the existing one.
The Language Server Protocol looks like an interesting standard. I like the idea and the fact that it is language independent would intuitively make it a good candidate to enable features for all our expression languages in a unified way. But implementing it would likely require a lot more work as it seems to be much more ambitious in the features it exposes. Some of them, such as enabling refactoring actions, would probably be of marginal interest for an expression editor.

I had a closer look at this and the parser isn't that complicated. I think there would be more value in generating the lexer (that we call "Scanner") than the parser itself, probably.
Anyway since it's not really clear it's worth the trouble, I haven't added it to the GSoC projects list.


MarathonSchedulerService cannot be shutdown when Zookeeper dies.

How to re-produce
see also #146
This issue can reproduce in standalone environment.

startup zookeeper
start marathon instance.
after marathon started completely(registration completed), stop zookeeper
marathon don't stop and keep output zookeeper connection error ( this outputs may be produced by mesos' ZooKeeperState).

MESOS_NATIVE_LIBRARY is not set. Searching in /usr/lib /usr/local/lib.
MESOS_NATIVE_LIBRARY is set to /usr/local/lib/libmesos.so
Apr 05, 2014 6:39:52 AM mesosphere.marathon.Main$delayedInit$body apply
INFO: Starting Marathon 0.5.0-SNAPSHOT
Apr 05, 2014 6:39:54 AM mesosphere.marathon.MarathonModule provideCandidate
... bunch of marathon startup logs ...
INFO: Binding mesosphere.marathon.api.v2.AppsResource to GuiceManagedComponentProvider with the scope "Singleton"
Apr 05, 2014 6:39:56 AM com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory getComponentProvider
INFO: Binding mesosphere.marathon.api.v2.TasksResource to GuiceManagedComponentProvider with the scope "Singleton"
Apr 05, 2014 6:39:56 AM com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory getComponentProvider
INFO: Binding mesosphere.marathon.api.v2.EventSubscriptionsResource to GuiceManagedComponentProvider with the scope "Singleton"
Apr 05, 2014 6:39:56 AM org.eclipse.jetty.server.AbstractConnector doStart
INFO: Started SelectChannelConnector@<IP_ADDRESS>:8080  // <--- startup completed
2014-04-05 06:40:15,000:4625(0x7f84f1ffb700):ZOO_ERROR@handle_socket_error_msg@1721: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=112(Host is down): failed while receiving a server response // <-- detected zookeeper's death
I0405 06:40:15.001369  4645 group.cpp:400] Lost connection to ZooKeeper, attempting to reconnect ...
2014-04-05 06:40:15,001:4625(0x7f84f2ffd700):ZOO_ERROR@handle_socket_error_msg@1721: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=112(Host is down): failed while receiving a server response
2014-04-05 06:40:18,337:4625(0x7f84f1ffb700):ZOO_WARN@zookeeper_interest@1557: Exceeded deadline by 3264ms
2014-04-05 06:40:18,338:4625(0x7f84f2ffd700):ZOO_WARN@zookeeper_interest@1557: Exceeded deadline by 3259ms
2014-04-05 06:40:18,338:4625(0x7f84f1ffb700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:18,338:4625(0x7f84f2ffd700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:21,672:4625(0x7f84f1ffb700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:21,672:4625(0x7f84f2ffd700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
W0405 06:40:25.003258  4640 group.cpp:435] Timed out waiting to reconnect to ZooKeeper (sessionId=145309cebf40005)
I0405 06:40:25.003525  4641 detector.cpp:134] Detected a new leader: None
Apr 05, 2014 6:40:25 AM mesosphere.marathon.MarathonScheduler disconnected
WARNING: Disconnected
Apr 05, 2014 6:40:25 AM mesosphere.marathon.MarathonScheduler suicide
SEVERE: Committing suicide  // <-- shutdown sequence is started at this point.
_env@712: Client environment:zookeeper.version=zookeeper C client 3.4.5
2014-04-05 06:40:25,006:4625(0x7f84faffd700):ZOO_INFO@log_env@716: Client environment:host.name=mesos
2014-04-05 06:40:25,006:4625(0x7f84faffd700):ZOO_INFO@log_env@723: Client environment:os.name=Linux
2014-04-05 06:40:25,010:4625(0x7f84faffd700):ZOO_INFO@log_env@724: Client environment:os.arch=3.8.0-35-generic
2014-04-05 06:40:25,010:4625(0x7f84faffd700):ZOO_INFO@log_env@725: Client environment:os.version=#50-Ubuntu SMP Tue Dec 3 01:24:59 UTC 2013
2014-04-05 06:40:25,011:4625(0x7f84faffd700):ZOO_INFO@log_env@733: Client environment:user.name=vagrant
2014-04-05 06:40:25,012:4625(0x7f84faffd700):ZOO_INFO@log_env@741: Client environment:user.home=/home/vagrant
2014-04-05 06:40:25,013:4625(0x7f84faffd700):ZOO_INFO@log_env@753: Client environment:user.dir=/marathon
2014-04-05 06:40:25,013:4625(0x7f84faffd700):ZOO_INFO@zookeeper_init@786: Initiating client connection, host=localhost:2181 sessionTimeout=10000 watcher=0x7f85292b5400 sessionId=0 sessionPasswd=<null> context=0x1a8e9d0 flags=0
2014-04-05 06:40:25,010:4625(0x7f84f2ffd700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:25,014:4625(0x7f84f17fa700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:28,351:4625(0x7f84f2ffd700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:28,351:4625(0x7f84f17fa700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:31,688:4625(0x7f84f17fa700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:31,688:4625(0x7f84f2ffd700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:35,022:4625(0x7f84f17fa700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:35,024:4625(0x7f84f2ffd700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:38,360:4625(0x7f84f17fa700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2014-04-05 06:40:38,360:4625(0x7f84f2ffd700):ZOO_ERROR@handle_socket_error_msg@1697: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
... continue identical outputs ...

2 Causes
Cause 1: com.twitter.common.zookeeper.Group.cancel() never ends
When scala.sys.exit(_) is called (e.g. suicide), MarathonSchedulerService.triggerShutdown() will be called via Chaos (see code 1, code 2).  triggerShutdown is shutdown-hook of AbstractExecutionThreadService in guava.
And, abdicateCmd.map(_.execute) is called in MarathonSchedulerService.triggerShutdown() (see code).  abdicateCmd is an instance of Option[ExceptionalCommand[JoinException]] which is passed to the service when the marathon instance was elected as leader via onElected(ExceptionalCommand[JoinException]) (see code)
Then, This abdicateCmd.map(_.execute) causes com.twitter.common.zookeeper.Group.ActiveMembership.cancel()(note that this is private) in the end.  Although the method keeps retrying to delete sequence node guided by com.twitter.common.util.BackoffHelper (see code), backoffHelper instance of Group never ends when Zookeeper connection is lost (see belows).

Group is instantiated with Candidate in MarathonModule. (see code)
backoffHelper is set in constructor of Group. (see [code] (https://github.com/twitter/commons/blob/master/src/java/com/twitter/common/zookeeper/Group.java#L100))
the backoffHelper is actually an instance of TruncatedBinaryBackoff . (see code)
Unfortunately, constructed instance's stopAtMax  flag is false. (see code)
Consequently, this backoff retry never ends even if back off intervals reached max intervals.

You might think we can modify this backoff instance by making pull-req to twitter's commons.  However, the backoff instance is also used not only in memership cancel but also in other operations in group membership maintenance. So, this is not good way I think.
Cause 2: mesos' ZooKeeperState is needed to be finalized. But we can't.
For now, even if abicateCmd could be shutdowned successfully, mesos' ZookeeperState keeps trying to connect Zookeeper forever.  So, mesos' ZookeeperState would be required to be finalized.   However, unfortunately, ZooKeeperState.finalize() is protected method (see code)...
Related Issues

#146
#180
maybe #204

Please note this issue contains another problem of inconsistency between app state in zookeeper and actual task status.

Question
I'm not sure how to fix this issue, I mean, I can't figure out the best.  I would be happy if I would hear from other contributors' about how to fix it.

Wow, very old issue. We seem to have just lost our marathon on our cluster due to this error (I think):
Jul 18 16:34:34 p-mesos-master-5 marathon[555]: 2016-07-18 16:34:34,200:555(0x7f897618e700):ZOO_ERROR@handle_socket_error_msg@1721: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=112(Host is down): failed while receiving a server response

In this case the error was logged for the master and one other node  (with 5 master nodes). The result was no marathon master. Furthermore, all 5 marathon instances on all 5 nodes did not respond to /ping.

Did this happen on a recent version of Marathon? If so, which one?
On Mon, Jul 18, 2016 at 1:06 PM, Barry Kaplan<EMAIL_ADDRESS>wrote:

Wow, very old issue. We seem to have just lost our marathon on our cluster
due to this error (I think):
Jul 18 16:34:34 p-mesos-master-5 marathon[555]: 2016-07-18 16:34:34,200:555(0x7f897618e700):ZOO_ERROR@handle_socket_error_msg@1721: Socket [<IP_ADDRESS>:2181] zk retcode=-4, errno=112(Host is down): failed while receiving a server response
In this case the error was logged for the master and one other node (with
5 master nodes). The result was no marathon master. Furthermore, all 5
marathon instances on all 5 nodes did not respond to /ping.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mesosphere/marathon/issues/212#issuecomment-233392394,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACPVLFNnoFtXiENxC32hPXpQ7PJaGE1rks5qW7KzgaJpZM4Bv7zw
.

Yes, the latest I believe: 1.1.0


Provide OpenDDS and CMake?

There are packages like cmake that can provide prebuilt binaries. Maybe it's possible to provide OpenDDS libraries and binaries using a Python wheel, in pyopendds itself or maybe better in a separate opendds package. Also maybe cmake should be added to the dependencies so the user doesn't have to worry about having it.
If PyOpenDDS provides OpenDDS and CMake it should be easy or even automatic detected to not use ones from the Python packages.

CMake, along with Ninja, is now provided as it's a dependency of cmake-build-extension.

Related: #58
This is more of a infrastructure of getting prebuilt OpenDDS, while the other is solvable within PyOpenDDS once the proper CMake support for OpenDDS  is in place.


Corrected Code URL - Currently Invalid

Lines - 35 & 41
Change in URL to reflect name change from WVD to AVD (037-WindowsVirtualDesktop is now 037-AzureVirtualDesktop)

This fix was already addressed and approved in PR #282.  Closing this one as it is redundant.


getting "libpython3.8.so.1.0 cannot open shared object file: No such file or directory" error while running deepstream.py

deepstream.py", line 13, in <module>
    import pyds
ImportError: libpython3.8.so.1.0: cannot open shared object file: No such file or directory

can you please help me solve this issue! I have python 3.10 install and i dont know why its trying to find python 3.8

thanks! I uninstall and reinstall pyds using "pip install pyds" command and im getting this error:
Traceback (most recent call last):
  File "/opt/nvidia/deepstream/deepstream-6.4/sources/apps/sample_apps/deepstream-face/DeepStream-Yolo-Face-master/deepstream.py", line 401, in <module>
    sys.exit(main())
  File "/opt/nvidia/deepstream/deepstream-6.4/sources/apps/sample_apps/deepstream-face/DeepStream-Yolo-Face-master/deepstream.py", line 309, in main
    osd.set_property('process-mode', int(pyds.MODE_GPU))
AttributeError: module 'pyds' has no attribute 'MODE_GPU'

What is your DeepStream version?

It's 6.4

Are you using the correct exporter file in the utils folder (from this repo)?

no sorry! let me check that..

Hi @marcoslucianops!! Thanks a lot for your help all along the way you're really awesome! I'm able to run it now and detect faces.
I had a few questions if you could please tell me regarding this:

will I be able to run this on multiple streams parallelly?
can I recognise individual faces with labels/names separately?


Create Selinium application flowcharts using mermaid.live

Assigned to @CalebLuce

Through research I have installed Mermaid Preview onto VSCode, understand the basic language of mermaid.live and can surely say that I will be able to make a class diagram. As a dependency, I will need to observe the code created by the coding team once it has been mostly completed, and will have to draft and create the entire diagram from scratch. As far as issues go currently, I cannot quite yet test and learn or be certain of how mermaid works with GitHub as a recognized language. To be able to do so, I will have to attempt posting the class diagram and observing manually how it is read by GitHub. If we have individuals who have learned Markdown and can explain how it is understood by GitHub, I will have a better time understanding the link for mermaid to GitHub. As things currently stand, I have a solid standing point on where to progress as we continue.

Well lets test it shall we.
This is the sample digram when loading mermaid.live, and then copied here by using the copy markdown button.

@CalebLuce What I need from you is an abstract, general, not-about-our-code diagram or set of diagrams of the Document Object Model to go along with Robert's text about that subject.

I was hoping for a diagram of our web app code but this is on hold for now.


Decode emoji when using HTML entities

@vincentritter Here's a pull request with my experiment in decoding HTML entities using DOMParser. I forgot I'm actually using something similar to this in Epilogue. It's another dependency but it's really useful for doing stuff with HTML.
It works well for the emoji. I did notice a console warning with some unknown HTML tags, but haven't debugged that yet.

Cool, I've merged the conflicts and moved the parser to a global variable… I think. Let me know if this is what you had in mind because I'm still wrapping my head around how the project is structured.

Also, I can't test this at the moment because running into Xcode build problems this morning. 🙁 Give it a run-through when you have time and lemme know if anything needs to change.


Add missing parameters to current PR request

What has been done

Add missing parameters to current PR request

How to test

Merge PR
Leave a dry run merge comment on PR and make sure current PR object is printed to logs

/robin merge --dry-run

/robin merge --dry-run


Oracle protection on dex

The goal here is to build a halting mechanism if the price of the dex is to far off the Oracle price
Percentages to be determined before commencing work.
Acceptance Criteria

Generated by Zenhub AI

[ ] Scenario: Oracle protection on dex
Given the dex price is within a certain percentage of the oracle price
When the dex price deviates too far from the oracle price
Then a halting mechanism should be triggered to prevent further transactions
And an alert should be displayed to the user informing them of the issue

SetOracleProtection(BigInteger pid, BigInteger percentage)
Where precentage is in points, 0 means no protections
Should verify that both symbols have a price on the orcale


Some HAL links show a double encoding

Describe the bug
Due to the current implementation of the org.dspace.app.rest.link.HalLinkFactory.buildLink(String, T) some HAL link can present double encoding issue. This is actually the case for the discover endpoint when the query contains characters that must be url encoded such as :
This was noted working on https://github.com/DSpace/DSpace/pull/8238/commits/11767f5d3744224621edcc220014ce4d7d2d0bbd
Unfortunately, the proper fix proposed in the PR above introduce templated link that are actually not supported/managed on the angular side
To Reproduce
Steps to reproduce the behavior:

Try this API call https://api7.dspace.org/server/api/discover/search/objects?sort=score,DESC&page=0&size=10&configuration=default&query=author:sengupta&embed=thumbnail
check the result, you will note that the self link is

"self": {
"href": "https://api7.dspace.org/server/api/discover/search/objects?query=author%25253Asengupta&configuration=default"
}

Expected behavior
The self link should be "self": {
"href": "https://api7.dspace.org/server/api/discover/search/objects?query=author%3Asengupta&configuration=default"
}
Related work
Discovered/discussed in  https://github.com/DSpace/DSpace/pull/8238#discussion_r891767434

NOTE: as discussed in review of #8238... if the fix to this ticket requires the introduction of templated links, then we would need to also provide an update to the UI code so that it can handle templated links.  Currently several areas of the UI will break (especially all search/browse) when templated links are encountered.  See this comment for examples: https://github.com/DSpace/DSpace/pull/8238#pullrequestreview-992169349


nip46 error should not be null

It is possible for Amber to send a response like:
{"error":null,"id":"23af55b0-698c-4150-a56a-9a508c658ce3","result":"ack"}

This causes my serializer to crash:
error: Uncaught (in promise) ZodError: [
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "null",
    "path": [
      "error"
    ],
    "message": "Expected string, received null"
  }
]

The result should look like this (error is omitted):
{"id":"23af55b0-698c-4150-a56a-9a508c658ce3","result":"ack"}

Fixed by 518a610c92d6bc61bdc8a0ea106b9215aba1f0f2
@greenart7c3 Can you do a release please? Thank you for fixing these! :clap:

Sure, i'll make a release later


Malformed type: "cannot resolve class 'Logger' from 'SassBuilder'"

I reported this issue (https://github.com/dart-lang/build/issues/1181) over in build, but maybe it's a change in the latest Dart SDK that sass_builder needs to account for?
Dart: 2.0.0-dev.39.0
OS: macOS 10.13.4 beta (17E182a)
Browser: N/A
pubspec.yaml:
dependencies:
  angular: ^5.0.0-alpha+8
  angular_components: ^0.9.0-alpha+7
  angular_forms: ^2.0.0-alpha
  angular_router: ^2.0.0-alpha+8
  firebase: ^4.4.0
  pwa: ^0.1.9+1

dev_dependencies:
  angular_ast: ^0.4.4
  angular_compiler: ^0.4.0-alpha+8
  angular_test: ^2.0.0-alpha+6
  build_runner: ^0.8.0
  build_web_compilers: ^0.3.4+1
  sass_builder: ^1.1.4
  test: ^0.12.32+1

dependency_overrides:
  angular: ^5.0.0-alpha+8
  angular_forms: ^2.0.0-alpha

Error output:
[INFO] Generating build script completed, took 377ms

You have hit a bug in build_runner
Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues

'package:sass_builder/sass_builder.dart': malformed type: line 34 pos 20: cannot resolve class 'Logger' from 'SassBuilder'
  final _log = new Logger('sass_builder');
                   ^

dart:core                                                          _TypeError._throwNew
package:sass_builder/sass_builder.dart 34:20                       new SassBuilder
package:angular_components/builder.dart 9:9                        scssBuilder
package:build_runner/src/package_graph/apply_builders.dart 150:37  new BuilderApplication.forBuilder.<fn>.<fn>
package:build_runner/src/package_graph/apply_builders.dart 261:27  _createBuildPhasesForBuilderInCycle.<fn>.<fn>
dart:core                                                          List.addAll
package:build_runner/src/package_graph/apply_builders.dart 215:7   createBuildPhases
package:build_runner/src/generate/build_impl.dart 93:13            build
package:build_runner/src/generate/build.dart 66:5                  build
package:build_runner/src/entrypoint/options.dart 266:24            _BuildCommand.run
package:args/command_runner.dart 194:27                            CommandRunner.runCommand
package:args/command_runner.dart 109:29                            CommandRunner.run.<fn>
dart:async                                                         new Future.sync
package:args/command_runner.dart 109:11                            CommandRunner.run
package:build_runner/src/entrypoint/run.dart 15:24                 run
.dart_tool/build/entrypoint/build.dart 49:22                       main

same problem with me here since using dart 2.0.0-dev.38.0 and the problem also occurs in dart 2.0.0-dev.39.0. I have tried using dart 1.24.3, the problem is still there.

Same issue in docker image google/dart, have tried latest, 1.25.0-dev.11.0, 1.24

Same issue in here with docker image google/dar and dart 1.25.0-dev.11.0, 1.24.

Same issue with Dart 2.0.0-dev.39 on Ubuntu 17.10 and this pubspec.yaml:
dependencies:
  angular: ^4.0.0
  angular_components: ^0.8.0
  angular_forms: ^1.0.0
  angular_router: ^1.0.2
  github: ^3.0.2
  http: ^0.11.3
  ngx_core: ^0.6.0
  usage: ^3.3.0

dev_dependencies:
  grinder: ^0.8.1
  package_resolver: ^1.0.2
  sass: ^1.0.0-rc.1
  sass_builder: ^1.1.4
  yaml: ^2.1.13

transformers:
- sass_builder
- angular:
    entry_points: web/js/main.dart
- $dart2js:
    commandLineOptions: [--use-old-frontend]

Editing the SassBuilder class in the pub cache as suggested by the StackOverflow answer fixed the issue.

@4cm4k1 @alfinbi @muzuro @ltackmann @cedx
Are you all using build_runner v0.8.0?

@matanlurey yes. 🙂

I dont have line with build_runner`
Here is my pubspec.yaml:
name: app
description: web app
version: 0.0.1

environment:
  sdk: '>=1.24.0 <2.0.0'

dependencies:
  angular: ^4.0.0+2
  angular_components: ^0.8.0
  angular_forms: ^1.0.0
  angular_router: ^1.0.2
  http: "^0.11.3+16"

dev_dependencies:
  angular_test: ^1.0.1
  browser: ^0.10.0
  dart_to_js_script_rewriter: ^1.0.1
  test: ^0.12.0
  sass_builder: ^1.1.4

transformers:
- sass_builder
- angular:
    entry_points:
      - public/main.dart
      - test/**_test.dart
- test/pub_serve:
    $include: test/**_test.dart
- $dart2js:
    sourceMaps: true
- dart_to_js_script_rewriter

Here is error stack:
Loading angular, sass_builder, test/pub_serve and dart_to_js_script_rewriter transformers...
Error on line 26, column 5 of /root/.pub-cache/hosted/pub.dartlang.org/angular_components-0.8.0/pubspec.yaml: Error loading transformer: 'package:sass_builder/sass_builder.dart': malformed type: line 34 pos 20: cannot resolve class 'Logger' from 'SassBuilder'
  final _log = new Logger('sass_builder');
                   ^

    outputExtension: .scss.css
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error on line 25, column 3 of pubspec.yaml: Error loading transformer: 'package:sass_builder/sass_builder.dart': malformed type: line 34 pos 20: cannot resolve class 'Logger' from 'SassBuilder'
  final _log = new Logger('sass_builder');
                   ^

- sass_builder
  ^^^^^^^^^^^^

Same as @muzuro : no. Just tried 2.0.0-dev.39 with a project still based on pub, angular 4.0.0 and angular_components 0.8.0.
I've tried with another Angular 4 project, but using ng_bootstrap 0.9.2 instead of Angular Components: no issue.

I am not using build_runner, but the problem resolved after following [https://stackoverflow.com/questions/49334361/dart-sassbuilder-cannot-find-logger#answer-49336090](stack overflow answer)

@alfinbi It seems like just workaround, not correct fix

Also have this issue using build_runner, angular 5.
Work around is enough to get me to compile.
Anyone know what the issue is exactly?

Yup. I'm sending a PR out now.

@matanlurey great news! Could you prompt when fix will be available at https://pub.dartlang.org/packages/sass_builder#-versions-tab-

@muzuro The version 1.1.5 is released!
Thanks @matanlurey


[BUG] With gitlab plugin, when i review with Diff, it dispaly uncorrectly

Which Glance version and IDEA version?
Glance version: 1.8.2, Pycharm Community Edition: 2023.3.5

Can you show the complete config page picture and minimap picture?

What is the file type used and provide text or an example of the issue that occurred?
.py

What steps will reproduce the issue?
Show Diff by GitLab plugin

Is this the official plugin?

Also happening with github code reviews. Official plugin, 2024.1 (241.14494.240)

This seems to be a strange behavior of the official plugin, which has a scrollbar but cannot be used, causing minimap to fail to run

And the scroll bar used by the plugin is the one inside, so this issue cannot be fixed temporarily


TST: interpolate: test integrating periodic b-splines against ppoly

A follow-up to https://github.com/scipy/scipy/pull/7185
Periodicity makes integrating polynomials and splines fairly convoluted and error-prone; these routines took quite a bit of effort to iron out, mostly Nikolay's and Aman's. This PR adds a smoke test to make sure these routines stay in sync.
cc @amanp10

Indeed, its a good idea to test it along side PPoly.

@amanp10 Not sure. ISTM the coverage is adequate as is. Do you see any specific holes in coverage?

I can't think of any right now. Maybe @nmayorov can say something.


Group features in VoiceOver

Currently when using VoiceOver, each item within a feature (the image, title and description) are read separately. They should be treated as one unit.

Looks good to me 👍
Great addition! I will let you know when the changes are available with a new version.


m93 branch-heads/4577.

I have passed the iOS/macOS full platform and full architecture compilation, we need to confirm the Android platform, and can be merged after the test is correct

I tried to compile on windows, android, macOS,  and android, everything seems to be ok.

Great!! yes we should check if our previously applied android patches are still relevant (required).
(I think recent versions of WebRTC already does some better null checking related to simulcast)
Could you take a look @davidliu ? 🙏

Looks like https://github.com/webrtc-sdk/webrtc/pull/11 is still required for NPE handling. IIRC, the patch I pulled that from was fairly recent (Oct 2021ish) so probably isn't in m93.

Looks like #11 is still required for NPE handling. IIRC, the patch I pulled that from was fairly recent (Oct 2021ish) so probably isn't in m93.

I believe they are included in this branch (as this is a diff from chrome M93 to main). @davidliu could you confirm this is working as expected for Android? Then we can merge & release.

Yeah, looked at the branch's code, the appropriate NPE handling is missing (it reverted back to the old non NPE handling code).

Yeah, looked at the branch's code, the appropriate NPE handling is missing (it reverted back to the old non NPE handling code).

ah I understand now. @cloudwebrtc could you re-apply #11? Are other patches kept in this PR?

@davidzhao @davidliu  I think the patch has not been lost and should continue to be effective.
https://github.com/webrtc-sdk/webrtc/blob/upgrade-to-m93/media/engine/simulcast_encoder_adapter.cc#L717

@cloudwebrtc @davidliu The problem seems to be more complicated than expected, Some patches are indeed covered
https://github.com/webrtc-sdk/webrtc/pull/11
https://github.com/webrtc-sdk/webrtc/pull/7

This way of maintaining repo does not seem to be perfect. Once the new upstream is merged, the patches we have done will be overwritten without prompting.

#11 isn't covered.
https://github.com/webrtc-sdk/webrtc/blob/upgrade-to-m93/media/engine/simulcast_encoder_adapter.cc#L717
It's changed since M92, but it still doesn't cover the case where the primary encoder is null.

@davidliu I tried to re-add the difference in #11 to this branch, can you review and confirm its correctness?
https://github.com/webrtc-sdk/webrtc/pull/14/commits/8bbc6bd2f4fae3200f3fbd56a2a156ae344e15cd

Checked out the new commit, LGTM.

This way of maintaining repo does not seem to be perfect. Once the new upstream is merged, the patches we have done will be overwritten without prompting.

That's a good point.. the other two options are

Merge & rebase:

have an upstream branch that is always updated to Google's M releases
have our changes in main
for each release, merge from upstream and rebase our changes on top

Patch files:

similar to Shiguredo's approach of keeping .patch files and updating them

@hiroshihorie https://github.com/webrtc-sdk/webrtc/pull/7 This PR also seems to be covered. We need to confirm whether it affects iOS


Support other database backends?

BigchainDB currently works with RethinkDB as its "database backend." We're investigating and considering having BigchainDB work with other database backends. The goal of this project is to support at least one other database backend.

@ttmc is https://github.com/bigchaindb/bigchaindb/blob/master/bigchaindb/db/utils.py the home of most of the DB related code?
It seems that Apache CouchDB (and it's kin: pouchdb-server, Cloudant, etc) could fit the bill. I'd be happy to chat through a mapping / integration. @tilgovi might also be persuaded / interested in helping out. 😁

@BigBlueHat As noted in our recent blog post:

"It’s important to note that we chose RethinkDB as a starting point, but BigchainDB code is designed to be agnostic to the underlying database and portable to other database substrates. One of our main goals has always been to help blockchain-ify other popular databases."

Also, from the BigchainDB Whitepaper:

There are several things that would have to be done to support another database backend:

Add one or more new configuration settings to BigchainDB Server
Change the code to setup the database, its tables, its indexes, etc.
Change all code that does database queries
Change all "changefeed" code. This is tricky because other databases do this quite differently, if at all
Change deployment and operations configurations, scripts, optimizations, etc.

Some of the database-calling code could be abstracted behind a standard interface; some refactoring would be required to support that.
I'm not sure how much I should say about this, because I'm not in marketing or management... Let's just say that we mean it when we say we plan to support other database backends, so there should be no surprise if we make some formal announcement along those lines, and code like the above starts to get pushed to this repository. Then it would be easier for you (and others) to see what it would take to support whatever database backend.

Work has begun on this project. For example, see pull request #754.

Even more details: see pull request #788

MongoDB integration is underway, with the merging of #942 and additional implementation steps being documented under the milestone.

Can we close this?

My view: yes

Closing as we now support both MongoDB and RethinkDB, and the necessary infrastructure to support other backends is in place.


No license listed for QuickPermissions-Kotlin

Please add a license file to QuickPermissions-Kotlin? I assume it's Apache 2 like QuickPermissions.

Hi! Can you please accept the pull request to resolve this issue? I'd love to use this library but cannot unless it has an explicit license. Thanks!

https://github.com/QuickPermissions/QuickPermissions-Kotlin/pull/13
Merge request accepted

Thanks much!


Convert Front End

Todo:

convert all css to tailwind
convert view html to react components
separate functionality according to MVC

[ ] convert all css to tailwind
[ ] convert view html to react components
[ ] separate functionality according to MVC

[ ] convert view html to react components

[ ] flesh out front end with react-router dom
[ ] connect to api with react-query
[ ] facilitate form handling with react-hook-form
[ ] convert react to material ui components


chore: only allow creation of v2 connections (no more v1 connections can be created)

Test Plan
[Describe test plan here]
Deployment instructions
[Add any special deployment instructions here]

i'll wait to merge this until migrations are done


Pulsar cluster slow to recover from a failed bookkeeper node

Expected behavior
I am trying to replace bookkeeper nodes in the cluster. I have a 3 nodes bookkeeper cluster. I added 3 new bookkeeper nodes to the cluster. Shutdown one of the nodes and initiated decommissionbookie process to move ledger to other healthy nodes. There were total 13k ledgers. the process is going but it's been 3 weeks and i still have around 6k ledgers to recover.
First 6k ledgers were completed within 2 days but since then it's very slow to recover the ledgers.
Actual behavior
The cluster has been slow to transfer data to other healthy nodes. In the logs we have been seeing following exceptions:

ERROR org.apache.bookkeeper.client.LedgerFragmentReplicator - BK error reading ledger entry:
Error: Bookie handle is not available while reading (All 5 bookies are operational)
Error: Too many requests to the same Bookie while reading

Steps to reproduce
Stop bookkeeper on one of the nodes and initiate decommissionbookie to replicate data to rest of the cluster.
System configuration
Pulsar version: 2.3
Operating system: Amazon linux 2
Java version: openjdk version "1.8.0_222"

@pushkar-engagio Why was this issue closed?

I'm hitting the same problem right now on a production cluster of 5 bookie node.
Is there a way to speed up the rereplicatation process?

decommissionbookie command log

$ docker exec -it pulsar_bookkeeper bin/bookkeeper shell decommissionbookie -bookieid 'myoldbookienode1:3181'
....

07:50:23.151 [main-SendThread(mybookienode5:2181)] INFO  org.apache.zookeeper.ClientCnxn - Opening socket connection to server mybookienode5/<IP_ADDRESS>:2181. Will not attempt to authenticate using SASL (unknown error)
07:50:23.160 [main-SendThread(mybookienode5:2181)] INFO  org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /<IP_ADDRESS>:49356, server: mybookienode5/<IP_ADDRESS>:2181
07:50:23.233 [main-SendThread(mybookienode5:2181)] INFO  org.apache.zookeeper.ClientCnxn - Session establishment complete on server mybookienode5/<IP_ADDRESS>:2181, sessionid = 0x5017fae8c900878, negotiated timeout = 30000
07:50:23.237 [main-EventThread] INFO  org.apache.bookkeeper.zookeeper.ZooKeeperWatcherBase - ZooKeeper client is connected now.
07:50:23.611 [main] ERROR org.apache.bookkeeper.client.RackawareEnsemblePlacementPolicyImpl - Failed to initialize DNS Resolver org.apache.bookkeeper.net.ScriptBasedMapping, used default subnet resolver : java.lang.RuntimeException: No network topology script is found when using script based DNS resolver.
07:50:23.662 [main] INFO  org.apache.bookkeeper.client.RackawareEnsemblePlacementPolicyImpl - Initialize rackaware ensemble placement policy @ <Bookie:<IP_ADDRESS>:0> @ /default-rack : org.apache.bookkeeper.client.TopologyAwareEnsemblePlacementPolicy$DefaultResolver.
07:50:23.662 [main] INFO  org.apache.bookkeeper.client.RackawareEnsemblePlacementPolicyImpl - Not weighted
07:50:23.668 [main] INFO  org.apache.bookkeeper.client.BookKeeper - Weighted ledger placement is not enabled
07:50:23.719 [BookKeeperClientScheduler-OrderedScheduler-0-0] INFO  org.apache.bookkeeper.net.NetworkTopologyImpl - Adding a new node: /default-rack/mybookienode3:3181
07:50:23.720 [BookKeeperClientScheduler-OrderedScheduler-0-0] INFO  org.apache.bookkeeper.net.NetworkTopologyImpl - Adding a new node: /default-rack/mybookienode1:3181
07:50:23.720 [BookKeeperClientScheduler-OrderedScheduler-0-0] INFO  org.apache.bookkeeper.net.NetworkTopologyImpl - Adding a new node: /default-rack/mybookienode2:3181
07:50:23.720 [BookKeeperClientScheduler-OrderedScheduler-0-0] INFO  org.apache.bookkeeper.net.NetworkTopologyImpl - Adding a new node: /default-rack/mybookienode5:3181
07:50:24.146 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Resetting LostBookieRecoveryDelay value: 0, to kickstart audit task
07:51:28.159 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 144366
08:48:56.814 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 144217
09:33:14.303 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143970
10:28:59.324 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143713
10:43:45.331 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143517
10:55:02.345 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143456
11:06:15.621 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143416
11:17:31.914 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143367
11:28:46.275 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143308
11:40:01.941 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143246
11:51:15.598 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143187
12:02:28.513 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143131
12:13:44.562 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 143066
12:19:25.577 [BookKeeperClientScheduler-OrderedScheduler-0-0] INFO  org.apache.bookkeeper.net.NetworkTopologyImpl - Removing a node: /default-rack/mybookienode2:3181
12:21:01.745 [BookKeeperClientScheduler-OrderedScheduler-0-0] INFO  org.apache.bookkeeper.net.NetworkTopologyImpl - Adding a new node: /default-rack/mybookienode2:3181
13:08:53.974 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 142926
14:10:06.933 [main] INFO  org.apache.bookkeeper.client.BookKeeperAdmin - Count of Ledgers which need to be rereplicated: 142640

a bookie log

14:28:03.608 [BookKeeperClientWorker-OrderedExecutor-23-0] INFO  org.apache.bookkeeper.client.PendingReadOp - Error: Bookie handle is not available while reading L51031 E18397 from bookie: myoldbookienode1:3181

14:28:03.682 [bookkeeper-io-46-31] ERROR org.apache.bookkeeper.proto.PerChannelBookieClient - Could not connect to bookie: [id: 0xf237a093, L:/<IP_ADDRESS>:10898]/myoldbookienode1:3181, current state CONNECTING :
io.netty.channel.AbstractChannel$AnnotatedConnectException: finishConnect(..) failed: Connection refused: myoldbookienode1/<IP_ADDRESS>:3181
Caused by: java.net.ConnectException: finishConnect(..) failed: Connection refused
	at io.netty.channel.unix.Errors.throwConnectException(Errors.java:124) ~[io.netty-netty-transport-native-unix-common-4.1.48.Final-linux-x86_64.jar:4.1.48.Final]
	at io.netty.channel.unix.Socket.finishConnect(Socket.java:243) ~[io.netty-netty-transport-native-unix-common-4.1.48.Final-linux-x86_64.jar:4.1.48.Final]
	at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.doFinishConnect(AbstractEpollChannel.java:672) [io.netty-netty-transport-native-epoll-4.1.48.Final-linux-x86_64.jar:4.1.48.Final]
	at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.finishConnect(AbstractEpollChannel.java:649) [io.netty-netty-transport-native-epoll-4.1.48.Final-linux-x86_64.jar:4.1.48.Final]
	at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.epollOutReady(AbstractEpollChannel.java:529) [io.netty-netty-transport-native-epoll-4.1.48.Final-linux-x86_64.jar:4.1.48.Final]
	at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:465) [io.netty-netty-transport-native-epoll-4.1.48.Final-linux-x86_64.jar:4.1.48.Final]
	at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:378) [io.netty-netty-transport-native-epoll-4.1.48.Final-linux-x86_64.jar:4.1.48.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [io.netty-netty-common-4.1.48.Final.jar:4.1.48.Final]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [io.netty-netty-common-4.1.48.Final.jar:4.1.48.Final]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [io.netty-netty-common-4.1.48.Final.jar:4.1.48.Final]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]

Pulsar docker image version: apachepulsar/pulsar-all:2.5.2
BookKeeper docker image version: apachepulsar/pulsar-all:2.5.2

I got the same problem, and I'm using docker image streamnative/pulsar-all:<IP_ADDRESS>. Decommission command seems stuck at Count of Ledgers which need to be rereplicated: ... forever even that there is only few ledgers remaining.
Can you reopen this issue @pushkar-engagio

@truong-hua

Closed as stale. Please create a new issue if it's still relevant to the maintained versions.


Add Makefile for generating tutorial pages

I'm not entirely sure how to want to handle the tutorial generation stuff, but here is the Makefile I've been using.

This has now been subsumed by https://github.com/tarides/irmin.io/pull/4, avoiding the dependency on mdBook, and so can now be closed.


Print 'ok' when a test passes

Reverts #449
May fix the timeout in DefinitelyTyped/DefinitelyTyped#25269

Can you print a dot with no new lines to avoid long build logs?

I think the real problem is the many duplicate packages -- see #451. We should invest some effort into genuinely cleaning up DT rather than trying to hide the problems...

@andy-ms we can use travis folding APIs and generated fordable sections around that. most ppl do not have to see them this way.
we use them in TS build, see https://github.com/Microsoft/TypeScript/blob/master/Jakefile.js#L636-L643


ReferenceError: tab is not defined

I'm receiving the error "ReferenceError: tab is not defined" when trying to clear the chat log.
I've disabled my modules and identified it as an issue in relation with the Tabbed Chatlog module. When Damage Log and Tabbed Chatlog are active it's not possible to clear the entire chat log, it is possible to delete each entry individually however.
Thanks for the help and all of the great work you do for the Foundry community (much respect for the pull request you did for TorchLight to get it to 0.8).

1927ce8393d0fca32bbf09e72fff6f3e8bd94f78

Fixed in v1.6.2


OSS-Fuzz: OSS-Fuzz fuzzing integration

Hello! Would you be open to setting up fuzzing for the ttf-parser module with OSS-Fuzz?
Fuzzing can be a helpful way to uncover bugs through stress-testing, and Google’s OSS-Fuzz offers a free, continuous fuzzing service for open-source projects, which could help catch any potential memory issues in ttf-parser.
I noticed there are three cargo-afl fuzzers in the directory. Since OSS-Fuzz works with cargo-fuzz, I’ve converted these fuzzers to cargo-fuzz compatibility and added four more, hoping to expand the fuzzing scope and improve code coverage. In combination with an initial attempt in OSS-Fuzz (https://github.com/google/oss-fuzz/pull/12663), this setup also enables OSS-Fuzz to fuzz the ttf-parser module while keeping the fuzzers upstream for further modification and expansion. If you’d be interested in moving forward with this integration and storing the fuzzers upstream, please let me know—I’d be happy to share more details if needed. Any feedback or suggestions would be truly appreciated.
The only requirement at this stage is a Google-linked email for receiving bug notifications.
Thank you very much!

Thanks for the PR, unfortunately ttf-parser is currently in a semi-abandoned state. This PR should be put on hold until I find a new maintainer.


BBCode with Text Letter Speed

I'm having an issue with implementing BBCode into my dialogue.  It seems that whenever I add any form of [] tags into the text that aren't exclusive to Dialogic, there's a kind of lag with the reveal speed.  While the tags don't necessarily display, the text crawl still acts like they have been, with new sentences beginning with several characters being revealed on input before the individual reveal begins, and auto-pauses running on the wrong characters accordingly with the delay.
Steps to reproduce the behavior:

Create a new timeline and text box.
Implement autopauses from Settings > Text > AutoPause
Type a sentence using BBCode tags and characters used in autopause.
Click "Play Timeline"

I would simply like to be able to use BBCode in my text without any timing delays.
System:

OS: Linux, 6.1.62-1-MANJARO (64-bit)
Godot Version: v 4.1.3.stable.official
Dialogic Version: 2.0-Alpha-11 (Godot 4.1+)

Hey @KBrooke19, sorry for the long delay.
I'm currently trying to recreate this problem, but it seems to work fine for me.
Can you give us a specific text that had this problem?

@Jowan-Spooner I was able to reproduce. It happens if you change the default text speed from 0.01 to something like 0.03 in settings>Text>Default letter speed, otherwise it is not noticeable.
There wasn't any editing in the recording, it is this abrupt when skipping to the next line:

It seems like the text "keeps revealing itself" but you make it visible only when you press the input key.


xmlparser / roxmltree xml entity support

xmlparser https://github.com/RazrFalcon/xmlparser/releases/tag/v0.13.4 removed support for predefined entities. This then causes roxmltree to break. Currently pinning to v0.13.3

v0.13.4 was yanked


x/text/language: fails to parse valid BCP47 -t extension string; mistakes field for a region

What did you do?
package main

import (
	"fmt"

	"golang.org/x/text/language"
)

func main() {
	t, err := language.Parse("en-t-en-m0-ungegn")
	fmt.Printf("got %s, err %s\n", t, err)
}

What did you expect to see?
got en-t-en-m0-ungegn, err nil

What did you see instead?
got en-t-en, err language: tag is not well-formed

Cause
In /x/text/internal/language, this error happens whenever parseExtension calls parseTag to parse language, script, region and variants if they appear after "-t".
(e.g. "en-t-m0-ungegn" is fine and does not trigger this error, but "en-t-en-m0-..." does.)
rfc6497 gives another example, und-Cyrl-t-und-latn-m0-ungegn-2007, which Go also fails to parse for the same reason.
"The field separator subtags, such as 'm0', were chosen because they are short, visually distinctive, and cannot occur in a language subtag". But parseTag believes "m0" is part of the (language, script, region, variants). It thinks "m0" is like the "GB" in "en-GB".
Note also that a language code like "en-001" is a valid part of the language/script/region/variants, so we have to be very specific that Go is parsing the tag incorrectly only when the subtag is exactly two characters long and contains a digit.
 Passes all existing tests, adds one new test case.

Can I get a second reviewer on this? Thanks

Reviewing the RFC-level aspect for now: this format uses the T (transform content) extension in RFC6497, which is only informational, and does not have to be implemented, although it's still nice for us to do.

Reviewing the RFC-level aspect for now: this format uses the T (transform content) extension in RFC6497, which is only informational, and does not have to be implemented, although it's still nice for us to do.

This is true, but the problem is it is implemented, just incorrectly. Following "-t" it parses a language tag (short on time so forgive me if I use Go terminology rather than RFC terminology here). At least to my recollection.
The two solutions are either consume the whole -t-.... until the next single-letter extension, without parsing it, or to fix the language tag parsing that follows -t. Honestly either are fine, as long as a valid locale string doesn't error.

@thanm pinging to see if you can get a 2nd reviewer as I am cognisant there is a release freeze coming up. Many thanks

Happy to recruit other Googlers to +1, but for +2 we need someone familiar with the x/text repo.


Android enroll page shows cloud doc links - Need to handle for both cases

https://localhost:9443/devicemgt/device/android/enroll

PR can be found here - https://github.com/wso2/carbon-device-mgt-plugins/pull/619

This PR has been merged hence closing the issue


Update package index with latest published versions

Update package index with latest published versions

/azp run azure-sdk - ci


🌐 Add Korean Translation for docs/ko/docs/advanced/response-cookies.md

Add translation to docs/ko/docs/advanced/response-cookies.md

hi i left some comment for PR.
please check it when you are not busy

Thanks! @kim-sangah :tada:
And thanks for the reviews @sodaMelon @JaeHyuckSa :nerd_face:


Feature request - Connect to the host HA when not in local network (using a notebook outside your local network)

Hello! Thanks for creating this great app, this is just amazing work!
I was wondering if it would be possible to type both a local IP and remote IP address and have Hass Agent know when it is not connected to the local network and use the secondary IP to connect to the host HA?
This would be great when I use notebook outside my local network and could still connect to the HA instance outside my home, over the internet. Since I've already set up my DDNS and opened the correct ports, this would be a great feature to have.
Thanks again, have a great day!

Sorry, wrong section.


Qt/spinner: reduce cpu usage from 12% to 9%

continue #21495.

do not fill background, use WA_OpaquePaintEvent to paint all in paintEvent (cpu recuded from 12% to 9%)
set fps to 20, But the angle of rotation at each step is the same as 30fps.  (cpu recuded from 9% to 6%)

done


Design new CLI experience

See Notion

Designing the CLI will require product design work and scoping.  This is not a high enough priority to consider for the immediate future and I have removed it from version 14.

We now have an initial design here and will be tracking the implementation here.


Fix staticcheck reported issues

The tool is started with the "-ignore" flag to ignore warning SA2002
which corresponds to invoking t.Fatalf (and the like) in a go routine.
Calling t.Fatalf in a go routine may produce a race condition.
The rationale for ignoring this warning is that if a test executes
the t.Fatalf() line it is that we have a problem either with test
or code that should be fixed.

Coverage remained the same at 94.762% when pulling 43dd8139c1dd0c6b4c52904da1810858eb16493a on fix_staticcheck_reports into 61923ed1eaf8398000991fbbee2ef11ab5a5be0d on master.


Implement an easy to use transform API which mimics the current entity Transform API, but for internally stored matrices.

We should be able to manipulate a 4x4 matrix using a Transform object without directly affecting an entity and its caches.
This standalone type would take a reference to a Matrix object and affect it as operations are performed. We could then have a derived class which stores data internally as well, allowing for implicit conversion to Matrix, copies of the transform, etc.
The entity-based Transform type could have an assignment operator which takes this new type as an input.

Tagging with Refactor as this will involve reworking the existing Transform type a decent bit.
Tagging with C++ Script API as this is mainly for simplifying operations in C++ scripts.


.mailmap: Add entry for Quentin's email

Commit 0bdd298182d3 reverted to my defunct email in AUTHORS for some reason. Let's revert back, and add a .mailmap entry for my email.

/test


Cutts off

Hi.
I've just installed this plugin and I see that when sprites are generated, you can also see in the preview that icons are cutts off (bottom) - moved in viewbox. You can see how it's moved on first icon. Any idea why?

Thanks

Here is example if I sprite only two svg icons

There is example if I sprite around 20 svg icons.

See the difference between first two., also the rest are just cuts off.


Fix image cache cronJobs

This patch fixes the way cronJobs are created.
With a particular focus to the image-cache feature, the goal is to perform a cronJob creation passing the right glance-image-cache PVC generated by a given StatefulSet.
Each GlanceAPI instance (either a replica or a dedicated API) needs an associated cronJob when the ImageCache is defined.
A dedicated cronJob is needed because the glance-{cleaner,pruner} tools act against a path (/var/lib/glance/image-cache) created by the StatefulSet as VolumeClaimTemplate.
TODO:

[x] Rebase on top of https://github.com/openstack-k8s-operators/glance-operator/pull/436
[x] Expose ImageCacheSchedule parameter(s) through the main API
[x] Fix kuttl tests
[x] Cleanup GlanceAPI and remove the cronJob debug option

/retest


Add support for Docker/Compose --x-networking

With --links being deprecated and the move to using --x-networking the commenting out everything in /etc/resolv.conf means that the inter-container communication bridge is lost.

@kenjones-cisco Could you explain a bit more about the implications of docker new networking and resolv.conf? Also, it should be just the nameservers that are overwritten in

When using --x-networking with docker-compose, it will create a private bridge network and only containers on that network bridge can communicate with each other.
An entry is placed in /etc/hosts with each containers:
<ip address> <container name>
<ip address> <container name>.<project name>

And /etc/resolv.conf is given a namesever entry to the ip that from the same subnet as the underlying host ip.
When running go-dnsmasq as follows:
exec go-dnsmasq --default-resolver --hostsfile=/etc/hosts

I see the following:
consul | Dec  7 18:39:58 2ad410dc4cc2 syslog.info syslogd started: BusyBox v1.23.2
consul | ==> WARNING: Bootstrap mode enabled! Do not enable unless necessary
consul | ==> Starting raft data migration...
consul | ==> Starting Consul agent...
consul | ==> Starting Consul agent RPC...
consul | ==> Consul agent running!
consul |          Node name: '2ad410dc4cc2'
consul |         Datacenter: 'dc1'
consul |             Server: true (bootstrap: true)
consul |        Client Addr: <IP_ADDRESS> (HTTP: 8500, HTTPS: -1, DNS: 8600, RPC: 8400)
consul |       Cluster Addr: <IP_ADDRESS> (LAN: 8301, WAN: 8302)
consul |     Gossip encrypt: false, RPC-TLS: false, TLS-Incoming: false
consul |              Atlas: <disabled>
consul |
consul | ==> Log data will now stream in as it occurs:
consul |
consul |     2015/12/07 18:39:58 [INFO] raft: Node at <IP_ADDRESS>:8300 [Follower] entering Follower state
consul |     2015/12/07 18:39:58 [INFO] serf: EventMemberJoin: 2ad410dc4cc2 <IP_ADDRESS>
consul |     2015/12/07 18:39:58 [INFO] consul: adding server 2ad410dc4cc2 (Addr: <IP_ADDRESS>:8300) (DC: dc1)
consul |     2015/12/07 18:39:58 [INFO] serf: EventMemberJoin: 2ad410dc4cc2.dc1 <IP_ADDRESS>
consul |     2015/12/07 18:39:58 [INFO] consul: adding server 2ad410dc4cc2.dc1 (Addr: <IP_ADDRESS>:8300) (DC: dc1)
consul |     2015/12/07 18:39:58 [ERR] agent: failed to sync remote state: No cluster leader
consul | level=info msg="Starting go-dnsmasq server 0.9.8 ..."
consul | level=info msg="Ready for queries on tcp://<IP_ADDRESS>:53 [rcache 0] Nameservers: [<IP_ADDRESS>:53]"
consul | level=info msg="Ready for queries on udp://<IP_ADDRESS>:53 [rcache 0] Nameservers: [<IP_ADDRESS>:53]"
consul |     2015/12/07 18:40:00 [WARN] raft: Heartbeat timeout reached, starting election
consul |     2015/12/07 18:40:00 [INFO] raft: Node at <IP_ADDRESS>:8300 [Candidate] entering Candidate state
consul |     2015/12/07 18:40:00 [INFO] raft: Election won. Tally: 1
consul |     2015/12/07 18:40:00 [INFO] raft: Node at <IP_ADDRESS>:8300 [Leader] entering Leader state
consul |     2015/12/07 18:40:00 [INFO] consul: cluster leadership acquired
consul |     2015/12/07 18:40:00 [INFO] consul: New leader elected: 2ad410dc4cc2
consul |     2015/12/07 18:40:00 [INFO] raft: Disabling EnableSingleNode (bootstrap)
consul |     2015/12/07 18:40:00 [INFO] consul: member '2ad410dc4cc2' joined, marking health alive
consul |     2015/12/07 18:40:00 [INFO] agent: Synced service 'consul'
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:38060-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:38060-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:34722-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:34722-><IP_ADDRESS>:53: i/o timeout\""
consul | ==> Failed to check for updates: Get https://checkpoint-api.hashicorp.com/v1/check/consul?arch=amd64&os=linux&signature=aec356cc-d0eb-286e-c64f-587d42ae754b&version=0.5.2: dial tcp: lookup checkpoint-api.hashicorp.com: Try again
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:50805-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:50805-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:42736-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:42736-><IP_ADDRESS>:53: i/o timeout\""
consul |     2015/12/07 18:40:33 [INFO] serf: EventMemberJoin: 7bb6d15c924c <IP_ADDRESS>
consul |     2015/12/07 18:40:33 [INFO] consul: member '7bb6d15c924c' joined, marking health alive

When removing the option --default-resolver and just append nameserver <IP_ADDRESS> # added by go-dnsmasq to /etc/resolv.conf:
consul | Dec  7 18:28:02 8868ec877b4c syslog.info syslogd started: BusyBox v1.23.2
consul | ==> WARNING: Bootstrap mode enabled! Do not enable unless necessary
consul | ==> Starting raft data migration...
consul | ==> Starting Consul agent...
consul | ==> Starting Consul agent RPC...
consul | ==> Consul agent running!
consul |          Node name: '8868ec877b4c'
consul |         Datacenter: 'dc1'
consul |             Server: true (bootstrap: true)
consul |        Client Addr: <IP_ADDRESS> (HTTP: 8500, HTTPS: -1, DNS: 8600, RPC: 8400)
consul |       Cluster Addr: <IP_ADDRESS> (LAN: 8301, WAN: 8302)
consul |     Gossip encrypt: false, RPC-TLS: false, TLS-Incoming: false
consul |              Atlas: <disabled>
consul |
consul | ==> Log data will now stream in as it occurs:
consul |
consul |     2015/12/07 18:28:02 [INFO] serf: EventMemberJoin: 8868ec877b4c <IP_ADDRESS>
consul |     2015/12/07 18:28:02 [INFO] raft: Node at <IP_ADDRESS>:8300 [Follower] entering Follower state
consul |     2015/12/07 18:28:02 [INFO] consul: adding server 8868ec877b4c (Addr: <IP_ADDRESS>:8300) (DC: dc1)
consul |     2015/12/07 18:28:02 [INFO] serf: EventMemberJoin: 8868ec877b4c.dc1 <IP_ADDRESS>
consul |     2015/12/07 18:28:02 [INFO] consul: adding server 8868ec877b4c.dc1 (Addr: <IP_ADDRESS>:8300) (DC: dc1)
consul |     2015/12/07 18:28:02 [ERR] agent: failed to sync remote state: No cluster leader
consul | level=info msg="Starting go-dnsmasq server 0.9.8 ..."
consul | level=info msg="Ready for queries on tcp://<IP_ADDRESS>:53 [rcache 0] Nameservers: [<IP_ADDRESS>:53 <IP_ADDRESS>:53]"
consul | level=info msg="Ready for queries on udp://<IP_ADDRESS>:53 [rcache 0] Nameservers: [<IP_ADDRESS>:53 <IP_ADDRESS>:53]"
consul |     2015/12/07 18:28:04 [WARN] raft: Heartbeat timeout reached, starting election
consul |     2015/12/07 18:28:04 [INFO] raft: Node at <IP_ADDRESS>:8300 [Candidate] entering Candidate state
consul |     2015/12/07 18:28:04 [INFO] raft: Election won. Tally: 1
consul |     2015/12/07 18:28:04 [INFO] raft: Node at <IP_ADDRESS>:8300 [Leader] entering Leader state
consul |     2015/12/07 18:28:04 [INFO] consul: cluster leadership acquired
consul |     2015/12/07 18:28:04 [INFO] consul: New leader elected: 8868ec877b4c
consul |     2015/12/07 18:28:04 [INFO] raft: Disabling EnableSingleNode (bootstrap)
consul |     2015/12/07 18:28:04 [INFO] consul: member '8868ec877b4c' joined, marking health alive
consul |     2015/12/07 18:28:04 [INFO] agent: Synced service 'consul'
consul | ==> Failed to check for updates: Get https://checkpoint-api.hashicorp.com/v1/check/consul?arch=amd64&os=linux&signature=77ab184f-e3f7-8504-0eb4-420fc4b11ae1&version=0.5.2: dial tcp: lookup checkpoint-api.hashicorp.com: Try again
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:59951-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:59951-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:51915-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:51915-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:49315-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:38433-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:33482-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:53296-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:59192-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:38497-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:51750-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:34601-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:40930-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:45618-><IP_ADDRESS>:53: i/o timeout\""
consul |     2015/12/07 18:28:37 [INFO] serf: EventMemberJoin: db021fd1d568 <IP_ADDRESS>
consul |     2015/12/07 18:28:37 [INFO] consul: member 'db021fd1d568' joined, marking health alive
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:53729-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:38096-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:59322-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:35417-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:38237-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:58757-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:53054-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:53005-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:55966-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:34741-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:57910-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:42923-><IP_ADDRESS>:53: i/o timeout\""
consul | level=error msg="Failure forwarding request \"read udp <IP_ADDRESS>:57127-><IP_ADDRESS>:53: i/o timeout\""

The errors just keep on going.
As the base image is alpine:3.2, I wanted to resolve the problem where I was seeing issues like:
consul | ==> Failed to check for updates: Get https://checkpoint-api.hashicorp.com/v1/check/consul?arch=amd64&os=linux&signature=de5d9136-692b-4c94-941c-56d9c1b3399b&version=0.5.2: dial tcp: lookup checkpoint-api.hashicorp.com: Try again
Just wanting to get around the DNS problems that exist with alpine, and still leverage the latest docker networking features that avoid having to specify which container will talk to each ahead of time and without dealing with the complexities of dnsmasq.

ah i see now what you were saying , thanks

When using --x-networking with docker-compose, it will create a private bridge network and only containers on that network bridge can communicate with each other.
And /etc/resolv.conf is given a namesever entry to the ip that from the same subnet as the underlying host ip.

I think thats the problem here: The namesever <IP_ADDRESS>:53 is in the host's network. But the container is in it's own private bridge network. There is simply no route/connectivity from the container to the nameserver as can be observed in this line:

Failure forwarding request "read udp <IP_ADDRESS>:38060-><IP_ADDRESS>:53: i/o timeout\

It looks like others are having this problem as well using consul and docker 1.9 multi-host networking: https://github.com/docker/libnetwork/issues/644
Basically you need to fix connectivity to the Consul DNS server from your containers. Go-dnsmasq can't do nothing about it. Since go-dnsmasq is in fact compatible with Docker 1.9 bridge networking i am closing this issue.

Consul can do DNS, but I'm not using Consul for DNS, it is the KV store.
Maybe the root of the issue is the Consul does do DNS and introducing go-dnsmasq is causing things to get confused. Thanks for your feedback.

@kenjones-cisco Just curious: Can you ping <IP_ADDRESS> from within the container?

yes, the ping to <IP_ADDRESS> works.


Get a second opinion on tonemapping quality

I don't think the tone mapping is quite right yet. But I may also be mistaken. Double check that everything is correct here.

Fixed!