Add documentation

[ ] Add doc strings to individual functions.
[ ] Add instructions how to run the GUI (what needs to be installed in advance)
[ ] Add documentation how to run pre-processing functions on new files outside of the GUI (when one needs to preprocess more data: you can set it up as a script with arguments)
[ ] Add documentation how to run an existing model on new files outside of a notebook (the notebook is great to investigate)
[ ] For preprocessing save example when it works or it does not depending on the parameters
[ ] code and documentation for the dataset generation for spleeter training and evaluation
[ ] improve messages for github commits

I will add all the required documentation if this project starts with the development phase.
count me in


Actually check the check digit + fixed bug in dob check

I'm not sure if the dummy id number generation should be in separate file.

@bevanmw I think the dummy ID generation can go in a modules called dummy.py. What do you think?


Fix hostap build issues

While working on hostap tests in #79973 I noticed compile issues. The tests might take long time to finalize, so creating a separate PR for build errors found so far.

These will be fixed as part of https://github.com/zephyrproject-rtos/zephyr/pull/79973 so closing this PR.


Quickemu: Init at 2.2.5

Motivation for this change
Quickemu is an amazing abstraction of QEMU, which I believe other Nix users would love to use.
Things done
Added pkgs/development/quickemu/' 'pkgs/development/quickemu/default.nix and modified pkgs/top-level/all-packages.nix to call quickemu.

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

I was getting ready to do so. Thanks!


Power State is "flickering" on pre 2016 AVR

Hi,
whenever my AVR-X2300W is on, Home Assistant sometimes displays it as being off for a brief moment (see screenshot).
I traced the issue back to potentially being in denonavr.py#L413.
The comment says On timeout and connection error, the device is probably off, but I'd argue that connection errors or timeouts can also be due to the bad WiFi capabilities of the AVR, so at least in my case the state probably hasn't changed.
I don't know the original reasoning behind the choice of setting the state to POWER_OFF on connection errors and timeouts, but I'd propose that it should only change the state if self._power == None and not blindly set it to POWER_OFF, but rather keep the current state if it is not None.
What do you think of that?

Screenshot in the Home Assistant History view displaying a timespan of 1 day:

Hello @ffittschen,
initially the library did not change the power status on connection errors. It turned out, that some receivers are not responding to requests on their network interface, when they are switched off. Those devices could not get to the offline state and that's why I changed the behavior.
Did you try to increase the timeout for denonavr in HA? Its default is set to 2 seconds.

Ahh I see, and that behavior doesn't surprise me at all... All of the official networking parts (website, app, OTA updates) of my receiver feel so hacky..
No I didn't try it because I thought 2 seconds would be more than enough on a local network. I increased it to 15 seconds now and the state seems to be more stable.
Thanks!


No Longer Maintained

It's been a year and there has been no updates or mergers from other repositories that have been maintaining their own fork of this repository. Use: https://github.com/Perfare/UnityStudio instead! Don't post your issues here!

Please stop spamming my project.
I don't know what your problem is, or why your replies seem to be so negative, but you're not helping anyone.
It's no secret that I have stopped maintaining this project a long time ago, but that doesn't mean I should just throw it away.
I posted the code here to help others understand the format and inner-workings of Unity files. No other project or extractor came even close to the level of detail you will find here.
If you want to be helpful, take the information you find here or in my Max script, which has been distributed many years ago, and build a better tool.
Don't forget to mention where you found the information. Writing tools with "nice error code" is one thing, reverse engineering an entire suite of unknown formats is a whole different animal.

@RaduMC I'm not spamming your project, but it looks like everyone else is. If you maintained this project, then there probably wouldn't be so much spam on the Issues page. People keep posting their issues here and they won't get support, so it only makes sense to redirect them to a place where they can get support. There is no information here, but the code, which is available at another fork that no one knows about. This version of Unity Studio comes up on Google, not the maintained version, so don't tell me what to do and how to act. People don't have to credit you on GitHub when it's forked or cloned, there is a reference to this repository when doing so. You're not the only one that has reverse engineered Unity's proprietary formats, there are several other projects that may or may not be based on your code.  I never said you should delete this repository, you should disable the "Issues" and "Wiki" pages and redirect people to the maintained repository.

First of all I asked you politely, and I believe I even said "please";
So there's no need to throw a tantrum about me telling you what to do. Start behaving like a civilized person
"People don't have to credit you on GitHub when it's forked or cloned, there is a reference to this repository when doing so."

Closing the Issues and Wiki pages will not help people find other forks any better.
You have wasted enough of the little time I have. Go mind your own please.

Oh and one more thing. This "version" comes up first on Google for a reason. Think hard.
You are welcome to help maintain it and submit pull requests if your intent is to HELP. If not... well I already told you what to do.


Removes basic Text component demo

this is kind of a nitpick / dumb suggestion but when i look at this top "Text" and see the serif-style font for the first example, i can't help but think "font rendering is broken on the web" lol
i would consider replacing Text with "Basic Serif Font" or moving it to the bottom to suggest that the font is properly loading

Let's just remove from the demo

Removed!


#513: Precompiled views tool and shape tag helpers.

Fixes #513
Shape tag helpers are created at runtime when we run our app but not when we run the tool.

I needed to create a shell context, service scope, and a fake HttpContext with the required services.

The _asyncLazyShellDescriptor is to fix an issue when the tool compile view through a parallel foreach and where shape tag helpers are resolved. Maybe it can't happen in the real world, but here i needed it.

When we init orchard through the tool the precompiled views assembly is still loaded (if it already exists), then the tool can't overwrite it. So we need to delete this assembly before re-running the tool. Or, as it is intended to be used, through a post-publish script. Let me know if it is worth to do it by code.

Finally, before running the tool we need to enable in the default tenant (used through the tool) each module which defines shapes which are used as tag helpers in some views we want to use.

For the above, maybe better to use an AllFeaturesShellDescriptorManager. But this service is registered during orchard initialization and i can only retrieve the scope provider which is not a services collection. So i didn't find a simple way to replace this service implementation. Let me know if it is worth to search.

Best.

Just re-tried and used an sql profiler.
Indeed, right now the only db accesses are for shell descripors, so, if i find a way to force the use of AllFeaturesShellDescriptorManager which doesn't use any sql query, i think it would be ok.
Moreover, this way all shape tag helpers would be resolved before views precompilation.

Don't try too hard on this one. To be clearer "I am reconsidering the current implementation of shape tag helpers" so it doesn't rely on a shell context.
I will probably introduce a way to describe specific tag helpers with their properties and intellisense, and not discovering them. They would just be like other tag helpers, so please keep this branch here in case I change my mind, but don't spend more time on this since we have discovered an issue with it.

Ok, anyway i learnt a lot about shell context composition.
So, here i will just push the last solution i've done.

There are some solutions whith custom shell context compositions, but maybe too complex.

So, here i use a regular shell context creation and i only detect if we are running through the view compilation tool. If so we register AllFeaturesShellDescriptorManager which doesn't use any db query.

The only little drawback is that now the tool can't overwrite the *.PrecompiledViews.dll. So, we need to remove it (if already exists) before re-running the tool, manually or e.g through a post-publish script. But can be easily done by code before the shell context creation.

Best.

So to close my work on this one.

See my previous comment but seems to work, you can check it.

Now, the generated assembly is auto-removed before re-runing views pre-compilation.

As you asked, i've reverted the fix of Orchard.Demo/Views/Content/Display.cshtml. So, if you want to test the tool you would need to delete or apply the right fix to this razor view.

No more useful with the next staticmodular implementation.


void* where it should be IntPtr

PostMessage 's parameters, wParam and lParam, are not pointers but additional message-specific information.
It feels incorrect to have to mark your project as unsafe, in addition to casting an integral type (e.g. UInt32) to a pointer to be able to call PostMessage's P/Invoke method.
This also applies to the SetWindowLong family methods' dwNewLong parameter and return type.
I have not read/searched the whole source code to find additional methods where void* is used instead of IntPtr.

In C++ LPARAM and WPARAM are both pointer types (UINT_PTR and ULONG_PTR respectively). So it would be incorrect if we represented them in C# as UInt32 since that's always 32 bits but it must be 64 bits in a 64-bit process.
So pointers are "correct" in the sense that they are the right length and are sometimes the value that folks intend to use. To appeal better to folks who have values that aren't pointers, we also provide an IntPtr overload (as we always do for pointer methods). Folks with an Int32 value can use new IntPtr(int) to construct what they need to call this method.
So I think we're correct here.

As I mentioned in my e-mail exchange with you earlier, and failed again to clarify here, is that they should be changed to IntPtr.
Forcing people to generate unsafe code to send numbers with PostMessage is wrong.
If they need to send pointers, they can go down that path and cast a void* to an IntPtr.
Those parameters are documented as additional data and as I already communicated, a lot of messages do not use any pointer,
Also, UINT_PTR and ULONG_PTR are not pointers. They're just _int64 or int depending on the bitness of the OS.
In C++, you still need to reinterpret_casrt<WARAM>(aPointer) if you want to pass the pointer.
I'll do a PR with the related changes and you'll decide if it's worthwhile or not. Thanks for the discussion!
#if defined(_WIN64)
    typedef __int64 INT_PTR, *PINT_PTR;
    typedef unsigned __int64 UINT_PTR, *PUINT_PTR;

    typedef __int64 LONG_PTR, *PLONG_PTR;
    typedef unsigned __int64 ULONG_PTR, *PULONG_PTR;

    #define __int3264   __int64
#else
    typedef _W64 int INT_PTR, *PINT_PTR;
    typedef _W64 unsigned int UINT_PTR, *PUINT_PTR;

    typedef _W64 long LONG_PTR, *PLONG_PTR;
    typedef _W64 unsigned long ULONG_PTR, *PULONG_PTR;

    #define __int3264   __int32
#endif

Forcing people to generate unsafe code to send numbers with PostMessage is wrong.

I suspect you're only looking at our source code to make this assertion. We are not forcing anyone to use unsafe code. An IntPtr overload is offered too, so folks can choose whether to use the IntPtr overload or the void* overload.

Thanks Andrew.
Yes I am. I saw that in src\User32\PublicAPI.Shipped.txt but was wondering. How/when/where is this generated as it's nowhere to be found in the source code?
Using that method marked as unsafe, you still need to allow unsafe build though, don't you?

How/when/where is this generated as it's nowhere to be found in the source code?

Code generation happens during the build. We inspect our own public API and then add to it;
https://github.com/AArnott/pinvoke/blob/3d19670578f9940781e09a005954337c0ca21844/src/CodeGeneration/OfferFriendlyOverloadsGenerator.cs#L19-L20

Using that method marked as unsafe, you still need to allow unsafe build though, don't you?

No, unsafe on a method signature does not require that callers also allow unsafe code. It's easy to think that, I agree, but we tested it to make sure.

That CodeGeneration's source code is pretty interesting.
Thanks for your patience Andrew.


Support gitlab as a SCM provider

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


feat: typeorm instrumentation

Short description of the changes
Adds the typeorm instrumentation created by Aspecto.
Only contains minor changes: upgraded to the latest SDK and semantic conventions package, modified the tests to use assert, changed the hook type signature.

Thank you for working on this 🙏🎉
Left few comments and suggestions
The original instrumentation had a test-all-versions setup. I wonder if it was left out on purpose or just overlooked.

Overlooked, going to re-add it, thanks!

Briefly messed up a commit and GitHub actions added various tags, shouldn't be a problem

Should've addressed all the feedback nwo

@blumamir Anything else to resolve here?

@blumamir Up, could you review I could also help with that as I am waiting for proper typeorm instrumentation.


nc: unix connect failed: Permission denied

From the docker logs...
It seems like nc isn't being allowed from some reason? I tried nc and the script manually and it worked just fine.
nc: unix connect failed: Permission denied
Cannot find the name of docker container '82735a68dc95b947a43edfe3c4cad03d5b6d563e88033c36b83de1063ada5a2c'
/etc/netdata/overrides/cgroup-name.sh: cgroup 'docker_82735a68dc95b947a43edfe3c4cad03d5b6d563e88033c36b83de1063ada5a2c' is called '82735a68dc95'
Running API command: /containers/cd1bbb3d665ae5028467efeea36190793694b8cfd954220af5e2d8869340206e/json
nc: unix connect failed: Permission denied
Cannot find the name of docker container 'cd1bbb3d665ae5028467efeea36190793694b8cfd954220af5e2d8869340206e'
/etc/netdata/overrides/cgroup-name.sh: cgroup 'docker_cd1bbb3d665ae5028467efeea36190793694b8cfd954220af5e2d8869340206e' is called 'cd1bbb3d665a'
Running API command: /containers/e405a61d3c58ca53c25f629bc824302c8ce7fcabb68ab27ef64f93489a483151/json
nc: unix connect failed: Permission denied
Cannot find the name of docker container 'e405a61d3c58ca53c25f629bc824302c8ce7fcabb68ab27ef64f93489a483151'
/etc/netdata/overrides/cgroup-name.sh: cgroup 'docker_e405a61d3c58ca53c25f629bc824302c8ce7fcabb68ab27ef64f93489a483151' is called 'e405a61d3c58'
Running API command: /containers/f74e5cea16b691067ff260dc39eba254285cde758f95d16230b69715fc489825/json
nc: unix connect failed: Permission denied
Cannot find the name of docker container 'f74e5cea16b691067ff260dc39eba254285cde758f95d16230b69715fc489825'
/etc/netdata/overrides/cgroup-name.sh: cgroup 'docker_f74e5cea16b691067ff260dc39eba254285cde758f95d16230b69715fc489825' is called 'f74e5cea16b6'

Actually I think it's related to this issue, as my script is modified slightly and uses root as the user...
https://github.com/docker/docker/issues/2259

can reproduce by:
su -c "/etc/netdata/overrides/cgroup-name.sh docker_7ced9b865453692bc3a71fff5913b9215057c7089d70f5446f8e08629c1c5638" -s /bin/bash netdata
Running API command: /containers/7ced9b865453692bc3a71fff5913b9215057c7089d70f5446f8e08629c1c5638/json
nc: unix connect failed: Permission denied
Cannot find the name of docker container '7ced9b865453692bc3a71fff5913b9215057c7089d70f5446f8e08629c1c5638'
/etc/netdata/overrides/cgroup-name.sh: cgroup 'docker_7ced9b865453692bc3a71fff5913b9215057c7089d70f5446f8e08629c1c5638' is called '7ced9b865453'
7ced9b865453

So it looks like this is caused by /var/run/docker.sock being owned by root

Changing the netdata.conf file by modifying the setting:
[global]
 	run as user = root

Resolved the issue. Though I believe the sysadmin gods would banish me for that, it works.
I think the docs should be updated a bit, but docker-proxy-acl probably should be advertised as a requirement. Ideally docker-proxy-acl would expose a new socket that could be used in containers.
https://github.com/titpetric/docker-proxy-acl

I built a docker container for docker-proxy-acl that is a little easier to set up here: https://github.com/kmlucy/docker-proxy-acl

It would actually make sense for netdata to run as root in the container. @ktsaou, is there perhaps a runtime option argument available for this (-u root?).

like you said: -u root. It can also be set in netdata.conf: run as user setting.

@ktsaou Thank you, it's easier for me to add -u root so I've just gone ahead and did that. Marking issue as closed.

Mine though is different:
# ls -l /var/run/docker.sock
srw-rw---- 1 root docker 0 Sep 25 16:20 /var/run/docker.sock

If you added user netdata to the docker group, it will work. netdata-installer.sh already does this: https://github.com/firehol/netdata/blob/a413b46d1abff0d78aaa104d14951c94ee580c18/netdata-installer.sh#L561-L577

netdata-installer.sh already does this

it does it only when the docker group exists of course...

@ktsaou - true, it's a permissions issue. But as netdata is running in a container, there's no reasonable restriction why it shouldn't run as root in the first place, as UID mapping will take place with Docker in due time. The use of docker-proxy-acl is still recommended to provide a "safe" docker.sock file, which is another way to touch the fishy in this case.

The use of docker-proxy-acl is still recommended to provide a "safe" docker.sock file, which is another way to touch the fishy in this case

why don't we use it then?
what needs to be done?

@ktsaou it's optional, we can't enforce use beyond documentation.

Just wanted to come back and say thanks @titpetric @kmlucy for fixing this issue so quickly! I'm already using it!


Refactor /parse, remove validation, support batch

WARNING: Do not merge!  Grasshopper geocoder is not yet compatible with the change.  The PR is purely for review at this point.  Also, this PR does not yet include updates to the docs.  I will add them once I confirm this change plays nice with the geocoder.
This PR does a few things:

Removes /standardize resource.
Refactor's /parse resource.

Response JSON has been refactored to an array of address parts, rather than explicit key/values.
Supports POST of up to 5000 address for batch parsing.
Removes validation code that was causing heartache within the geocoder.

Note: Some form of validation will likely return in the future...

Adds more tests.

Looks like one of the tests is failing in Travis:

https://travis-ci.org/cfpb/grasshopper-parser/jobs/90343252#L156

Works on my machine.  I'll look into it.

We'll this is interesting.  One of the new tests checks that the failed array is populated when an unparsable address string is passed in.  This works fine when run using nosetests, but when run via tox (which itself calls nose), the test fails because the address parsing works.
I'm using the bad address we saw during the demo last week:
5 Arapahoe Plaza El Paso TX 88530

...which parses to:
{u'input': u'5 Arapahoe Plaza El Paso TX 88530',
  u'parts': [
    {u'type': u'BuildingName', u'value': u'5 Arapahoe Plaza El'},
    {u'type': u'PlaceName', u'value': u'Paso'},
    {u'type': u'StateName', u'value': u'TX'},
    {u'type': u'ZipCode', u'value': u'88530'}]}

It clearly doesn't parse well, but it does parse.  So, the question is, why?  I'm guessing I have newer version of usaddress in my local virtualenv, probably from the unmerged https://github.com/cfpb/grasshopper-parser/pull/26.  I'm going to merge that PR into this one and see if it fixes it.

@awolfe76, thanks for the merge of #26.  It seems to have fixed both the failing unit test and the Coveralls integration!

That's great! Glad that worked.

This PR's sister PR https://github.com/cfpb/grasshopper/pull/195 is now ready for review.  They'll need to be merged at the same time, otherwise we'll have a broken geocoder.
I do still need to add docs for how the API has changed.  I will take care of that as soon as I'm back on Monday.

@jmarin, the failing test sounds very similar to the issues described above.  You probably just need to get the latest Python packages introduced on #26.  If you haven't done so already, pip install and try it again:
pip install -r requirements.txt
pip install -r tests/requirements.txt

...and also from #26, you may have watch out for:

Warning: The upgrade from Coverage 3.x to 4.x breaks compatibility with the .coverage file format.  If you have a .coverage file in your project root, you'll need to delete it before running coverage or tox.

I've converted the "type" field to "code" to get around the type keyword ugliness on the Scala side.  I also fixed all of the flake8 recommendations.  This should be good to go.


Driver Failed to Connect due to Exception casting issue

Trying to do Test Connection using this driver from Jasper Server to KSQLDB (both working separately).
27-May-2020 10:51:07.225 SEVERE [http-nio-8080-exec-6] org.glassfish.jersey.server.ServerRuntime$Responder.mapException An exception has been thrown from an exception mapper class com.jaspersoft.jasperserver.jaxrs.common.GenericRemoteExceptionMapper.
java.lang.ClassCastException: java.lang.NoClassDefFoundError cannot be cast to java.lang.Exception
at com.jaspersoft.jasperserver.jaxrs.common.GenericRemoteExceptionMapper.toResponse(GenericRemoteExceptionMapper.java:66)
at com.jaspersoft.jasperserver.jaxrs.common.GenericRemoteExceptionMapper.toResponse(GenericRemoteExceptionMapper.java:45)

Do you have the fat jar or all required deps properly set in the classpath?

Thanks for your reply
Regarding Jasper Server, I try to register both thin and fat driver in the way all other JDBC drivers we use (Postgres, MySQL, Snowflake, using Jasper DataSource web interface) and in both cases the mentioned error appears (happens for both Jasper Server version 7.1 and 7.5, both commercial and community version).
As mentioned in another issue, simple Java console app I tried also is not able to use driver successfully, as tested on Ubuntu 16.04 (OpenJDK Runtime Environment AdoptOpenJDK, build 11.0.3+7) and Mac OS (OpenJDK Runtime Environment, build 13.0.1+9), simple test code and cmd line attached below (also fails for both thin and fat driver jar), for working ksqldb
(docker ps:
f4e52853fcd4        confluentinc/ksqldb-server:0.9.0         "/usr/bin/docker/run"    27 hours ago        Up 27 hours         <IP_ADDRESS>:8088->8088/tcp )
I appreciate your work, but would appreciate working reference sample, that can probably help many users, as simple integration doesn't seem to work... Thanks
// KSQLSample.java
import java.sql.*;
public class KSQLSample {
static final String JDBC_DRIVER = "com.github.mmolimar.ksql.jdbc.KsqlDriver";
static final String DB_URL = "jdbc:ksql://localhost:8088";  // ksql db demo here works
public static void main(String[] args) {
Connection conn = null;
Statement stmt = null;
try {
Class.forName(JDBC_DRIVER );
conn = DriverManager.getConnection(DB_URL);  //error here
} catch(SQLException se) {
se.printStackTrace();
} catch(Exception e) {
e.printStackTrace();
}
}
java -cp ".:./seed-project-assembly-1.2.0.jar" KSQLSample
java.sql.SQLException: No suitable driver found for jdbc:ksql://localhost:8088
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:702)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:251)
at KSQLSample.main(KSQLSample.java:18)

Have you tried in Squirrel SQL and change the JDK to Oracle JDK8?

Thanks, I tried Oracle Java as suggested:
Java(TM) SE Runtime Environment (build 14.0.1+7)
on another Ubuntu (18.04) box got the same error:
java.sql.SQLException: No suitable driver found for jdbc:ksql://localhost:8088
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:702)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:251)
at KSQLSample.main(KSQLSample.java:11)
I also tried Squirrel-SQL, which registers Driver OK (same as Jasper, OpenJDK and Oracle JDK), and displays STREAM, TABLE and UDT node, but displays error messages on access (double-click any of these) as below:
Driver class com.github.mmolimar.ksql.jdbc.KsqlDriver successfully registered for driver definition: ksql
Please try out the Tools popup by hitting ctrl+t in the SQL Editor. Do it three times to stop this message.
Error: STREAM: io.confluent.ksql.rest.client.KsqlRestClientException: Error issuing POST to KSQL server. path:/ksql
KSQLDB that I try to access is just a basic sample setup from: https://ksqldb.io/quickstart.html that works OK from prompt.
More help would be appreciated.

Also, not sure if this might be related, but while I was able to build driver jars in OpenJDK 13 on Mac, the same build fails with Oracle JDK 14 on Ubuntu 18.04, with errors as below. It would be helpful if you can post a binary zip (with compiled version of the jar that works for you in Squirrel-SQL)?! Thanks
[info] Resolved  dependencies
[warn]
[warn]  Note: Unresolved dependencies path:
[error] sbt.librarymanagement.ResolveException: Error downloading org.openjfx:javafx.base:11.0.0-SNAPSHOT
[error]   not found: /home/miomir/.ivy2/local/org.openjfx/javafx.base/11.0.0-SNAPSHOT/ivys/ivy.xml
[error]   not found: https://repo1.maven.org/maven2/org/openjfx/javafx.base/11.0.0-SNAPSHOT/javafx.base-11.0.0-SNAPSHOT.pom

The driver is tested with JDK8 and, on the other hand, each version of the driver is linked to a KSQL version, do they match?

I tried OracleJDK 8 (Java(TM) SE Runtime Environment (build 1.8.0_251-b08)

I was able to build driver with suggested Oracle JDK8 version (while build fails with Oracle JDK14). However when running simple Java code above (in either Oracle JDK8, 14 or OpenJDK11 and 13), trying to connect to SQLDB with new built driver, I still see the same error java.sql.SQLException: No suitable driver found at DriverManager.java:689), as with old driver (built with OpenJDK 13).
I do not quite understand your suggestion to match KSQL versions. What I see in driver built.sbt is
val ksqlVersion = "5.4.0", but no ksqldb version.
There is no matching settings in the reference confluent docker compose file, only:
image: confluentinc/ksqldb-server:0.9.0
Some more help would be appreciated.


Backdoor in Solana's Web3.js npm Library

According to this discussion in solana's repository, a publish-access account was compromised such that a malicious version of solana was pushed in npm.
Hence, I would assign it to AV-602 Take-over Legitimate Account below AV-504 Distribute as Package Maintainer

@henrikplate


Update about us second

Pull Request Test Coverage Report for Build 105

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.811%

Totals

Change from base Build 102:
0.0%

Covered Lines:
1433

Relevant Lines:
1544

💛  - Coveralls


BUG: Song reset on pause -> back -> resume

Ideal behavior is to retain paused progress.

Added FLAG in startOrContinue() to check if MusicPlayer has been paused. Continue playing if paused.


Can't print cyrillic text

Hi! I can't print cyrilic symbols
it's code
final Ticket ticket = Ticket(PaperSize.mm80); ticket.text('ЙЦУКЕНГШЩЗХЪХЭЖДЛОРПАВЫФЯЧСМИТЬБЮ.', styles: PosStyles(           codeTable: PosCodeTable.pc866,           fontType: PosFontType.fontA,         ));     ticket.cut();     return ticket;
it's exception
E/flutter ( 8146): #6      _MyHomePageState.build.<anonymous closure>.<anonymous closure>  package:blue/main.dart:148 E/flutter ( 8146): #7      _InkResponseState._handleTap  package:flutter/…/material/ink_well.dart:706 E/flutter ( 8146): #8      _InkResponseState.build.<anonymous closure>  package:flutter/…/material/ink_well.dart:789 E/flutter ( 8146): #9      GestureRecognizer.invokeCallback  package:flutter/…/gestures/recognizer.dart:182 E/flutter ( 8146): #10     TapGestureRecognizer.handleTapUp  package:flutter/…/gestures/tap.dart:486 E/flutter ( 8146): #11     BaseTapGestureRecognizer._checkUp  package:flutter/…/gestures/tap.dart:264 E/flutter ( 8146): #12     BaseTapGestureRecognizer.acceptGesture  package:flutter/…/gestures/tap.dart:236 E/flutter ( 8146): #13     GestureArenaManager.sweep  package:flutter/…/gestures/arena.dart:156 E/flutter ( 8146): #14     GestureBinding.handleEvent  package:flutter/…/gestures/binding.dart:222 E/flutter ( 8146): #15     GestureBinding.dispatchEvent  package:flutter/…/gestures/binding.dart:198 E/flutter ( 8146): #16     GestureBinding._handlePointerEvent  package:flutter/…/gestures/binding.dart:156 E/flutter ( 8146): #17     GestureBinding._flushPointerEventQueue  package:flutter/…/gestures/binding.dart:102 E/flutter ( 8146): #18     GestureBinding._handlePointerDataPacket  package:flutter/…/gestures/binding.dart:86 E/flutter ( 8146): #19     _rootRunUnary  (dart:async/zone.dart:1138:13) E/flutter ( 8146): #20     _CustomZone.runUnary  (dart:async/zone.dart:1031:19) E/flutter ( 8146): #21     _CustomZone.runUnaryGuarded  (dart:async/zone.dart:933:7) E/flutter ( 8146): #22     _invoke1  (dart:ui/hooks.dart:273:10) E/flutter ( 8146): #23     _dispatchPointerDataPacket  (dart:ui/hooks.dart:182:5)
Can you help me with this?

Hi,
It should be possible to print Cyrillic symbols, here are some examples (including printing Cyrillic):
https://github.com/andrey-ushakov/esc_pos_printer#using-code-tables
Feel free to reopen the issue if you have any further questions


🎨 Move Brig mappings to a common class for Paper and Commodore

This doesn't break anything on Paper, but in my testing of this it didn't work for Commodore. On top of that it seems like Commodore is kind of borked in general. Valid commands get shown as invalid and suggestions are messed up when commodore is active (with or without the changes in this PR)

This needs to be tested with the new commodore changes. That should hopefully fix the commodore related issues. If there are still issues, this can still be merged but we need to note which issues that are still around so they can be fixed separately.
So essentially, test and open issues if necessary. When done, this can be merged :+1:

Commodore issues seem fixed with the new changes. Updated the PR with your suggestions. I found out that Commodore wasn't mapping namespaced commands but fixed it in #35

Alright then we should be good to. I'm going to do more testing later on but I want to get these PRs merged sooner rather than later to prevent more merge confllicts :p


Exclude mjs extension from file-loader

I excluded .mjs files from file-loader.
This should fix https://github.com/facebook/create-react-app/issues/5234

Hmm, we need to think about this more because .mjs files currently aren't being processed via the same pipeline as .js, which means they're not being transformed via Babel, etc.
Is there a way to tell webpack to pretend .mjs files have the .js extension earlier up in the chain?

A couple things we need to be careful of:

mjs can not be permitted to work under src/. This import should fail and give you the URL.
mjs must be transformed via Babel.

Free Gift form all Nigerians
Click ---> (http://www.wowapp.com/w/mkoonline/mubarak-olanrewaju)
On Oct 2, 2018 2:29 PM, "Joe Haddad"<EMAIL_ADDRESS>wrote:

Hmm, we need to think about this more because .mjs files currently aren't
being processed via the same pipeline as .js, which means they're not
being transformed via Babel, etc.
Is there a way to tell webpack to pretend .mjs files have the .js
extension earlier up in the chain?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/pull/5235#issuecomment-426273386,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfNAM7X7iSbfpLVIyD5Eq0OFzQf4RBHFks5ug2pPgaJpZM4XDvCe
.

On 2018-10-02 3:29 PM, "Joe Haddad"<EMAIL_ADDRESS>wrote:

Hmm, we need to think about this more because .mjs files currently aren't
being processed via the same pipeline as .js, which means they're not
being transformed via Babel, etc.
Is there a way to tell webpack to pretend .mjs files have the .js
extension earlier up in the chain?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/pull/5235#issuecomment-426273386,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATut0aalFcszMMgrMQYvbhansQ5umuffks5ug2pBgaJpZM4XDvCe
.


es2020 as target/libs in tsconfig.json?

Hi. I wanted to use Promise.allSettled in my plugin, but Typescript said:

Property 'allSettled' does not exist on type 'PromiseConstructor'. Do you need to change your target library? Try changing the 'lib' compiler option to 'es2020' or later.ts(2550)

Are there any obstacles preventing Obsidian plugins to switch to es2020 from es2015? I think Electron apps like Obsidian use modern Chromium under the hood which should support es2020. Simple test in Obsidian dev console shows me that Obsidian knows about this method:

With navigator.userAgent I can see the Chrome version of my current Obsidian 0.12.3 is 87.0.4280.88.
CanIUse tells me all es2020 features are supported, and I guess earlier features are supported too.

Plugins don't always run on Electron. If you're ok that your plugin only runs in the desktop app, then targeting ES2020 is fine, but keep in mind that Obsidian will run perfectly fine on some older Android and iOS devices that aren't able to get the latest webview update, but your plugin will not function given its reliance on latest tech.

Thanks for the explanation @lishid. I completely forgot about the mobile app.


The modsecurity log is output to the nginx error log instead of /var/log/modsec_audit.log

I set the input log to /var/log/modsec_audit.log in the modsecurity configuration file, why doesn't it take effect?
the config is

Hi @Hello-Linux ,
Logging is impacted by several different settings.
First, What code branch are you talking about?  (I think you've looked at 3.1-experimental in the context of other issues)  Or should I assume that you are using ModSecurity v3.0.4 or the current v3/master.
Also:

what rule is being logged to the server's error log, but that is not being logged to the audit_log?
what disruptive actions (e.g. block/deny) are relevant (both in the rule itself and in any default actions)?
what logging actions do you have set in each (log,noauditlog, etc.)
are you using error redirects or anything similar?  Or just a basic nginx configuration?
are you never able to see anything in the audit_log or is it only for some transactions?

No feedback from the user, closing the issue.


Use BadRequest for bad requests in postgres example

There were the following issues with your Pull Request

Commit:<PHONE_NUMBER>7908d280825198c4708617c7979dd3
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/rustless/rustless

This message was auto-generated by https://gitcop.com

@globin thanks for your PR! Nice catch! Could you please update your commit message according to https://github.com/rustless/rustless/blob/master/CONTRIBUTING.md? If you have no time, just say and I do it myself manually.

There were the following issues with your Pull Request

Commit: 2fd90c0cde11417736fb1d4d3ff8000bc2211096
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/rustless/rustless/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Updated

Thanks!


zooming using Axis3!

Hi !
I'm trying to zoom and move on a 3D plot using the default campixel!, on this example:
using GLMakie
xs = LinRange(0, 10, 100)
ys = LinRange(0, 15, 100)
zs = [cos(x)*sin(y) for x ∈ xs, y ∈ ys]

fig, ax, plt = fap = surface(xs, ys, zs, axis=(type=Axis3, perspectiveness=0.))

display(fig)

The only workaround I found to having no controls on this camera is the following patch, which feels a bit like a hack:
--- a/AbstractPlotting/M8Nlv/src/makielayout/layoutables/axis3d.jl  2021-07-13 01:30:01.217360709 +0200
+++ b/AbstractPlotting/M8Nlv/src/makielayout/layoutables/axis3d.jl  2021-07-13 01:21:49.427690065 +0200
@@ -148,6 +148,8 @@
         :dragrotate,
         DragRotate())

+    register_interaction!(ax, :dragpan, DragPan(Ref{Any}(nothing), Ref{Any}(0), Ref{Any}(0), 0.2))
+    register_interaction!(ax, :scrollzoom, ScrollZoom(0.1, Ref{Any}(nothing), Ref{Any}(0), Ref{Any}(0), 0.2))

     # in case the user set limits already
     notify(attrs.limits)

--- a/AbstractPlotting/M8Nlv/src/makielayout/interactions.jl     2021-07-13 01:30:01.217360709 +0200
+++ b/AbstractPlotting/M8Nlv/src/makielayout/interactions.jl     2021-07-13 01:23:04.185775306 +0200
@@ -374,4 +374,35 @@
     ax3d.elevation[] = clamp(ax3d.elevation[] - dpx[2] * 0.01, -pi/2 + 0.001, pi/2 - 0.001)

     return nothing
+end
+
+function process_interaction(s::ScrollZoom, event::ScrollEvent, ax3d::Axis3)
+    zoom = event.y
+    if zoom != 0
+        z = max(.1f0, 1f0 - (abs(zoom) * s.speed))
+        if zoom < 0; z = 1 / z end
+
+        r = ax3d.finallimits[]
+        mini, maxi = extrema(r)
+        w = maxi - mini
+
+        ax3d.finallimits[] = typeof(r)(mini + .5(1 - z) * w, z * w)
+    end
+    return
+end
+
+function process_interaction(dp::DragPan, event::MouseEvent, ax3d::Axis3)
+    if event.type !== MouseEventTypes.rightdrag
+        return
+    end
+
+    pdpx = prod(event.px - event.prev_px)
+    if pdpx != 0
+        r = ax3d.finallimits[]
+        mini, maxi = extrema(r)
+        w = maxi - mini
+
+        ax3d.finallimits[] = typeof(r)(mini + sign(pdpx) * .05w, w)
+    end
+    return
 end
\ No newline at end of file

Is there a better way of achieving this ?

This doesn't have to do anything with AbstractPlotting, nor campixel! ;)
Yeah, Axis3 doesn't support zooming. You can use the standard axis instead, if you need zooming

Thank for the answer, I got it working (preserving Orthographic projection and apparent unit box aspect ration) by using:
import AbstractPlotting as AP
using GLMakie

ar(a) = 1 / only(diff(collect(extrema(a))))

target_aspect = collect(ar.((xs, ys, zs)))
target_aspect ./= sum(target_aspect) / length(target_aspect)
@show target_aspect

fig, ax, plt = fap = surface(xs, ys, zs)
scale!(ax.scene, target_aspect...)

cam3d!(ax.scene, projectiontype=AP.Orthographic)

@SimonDanisch, is this worth going in the docs in lscene, faq or maybe axis ?

Btw, AbstractPlotting is deprecated: https://github.com/JuliaPlots/AbstractPlotting.jl
So, you must be on a fairly old version that behaves a bit different then what's described in the current Makie docs.
Current Makie master has a few more docs about the camera, since @ffreyer did a pretty big refactor:
http://makie.juliaplots.org/dev/cameras.html

Damn, things got messed up. I'll refactor.

So here is the update example with<EMAIL_ADDRESS>using GLMakie

main() = begin
  xs = LinRange(0, 10, 100)
  ys = LinRange(0, 15, 100)
  zs = [cos(x)*sin(y) for x ∈ xs, y ∈ ys]

  fig, ax, plt = fap = surface(xs, ys, zs)

  ax3d = ax.scene[1]
  ax3d[:names, :textsize] = 20
  ax3d[:ticks, :textsize] = 20

  target_aspect = 1 ./ widths(Makie.data_limits(ax.scene))
  target_aspect /= sum(target_aspect) / length(target_aspect)
  @show target_aspect

  scale!(ax.scene, target_aspect...)
  cam3d!(ax.scene, projectiontype=Makie.Orthographic)

  save("out.png", fap)
  display(fap)
end

main()

Producing the following (with ability to zoom and drag, and orthographic projection):


How create default admin user

How I can create local admin user for self-hosted install?

You need to run this command in CLI:
bin/console repman:create:admin <email>
Description:
Description:
  Create admin user

Usage:
  repman:create:admin <email> [<password>]

Arguments:
  email                 e-mail used to log in
  password              plain password, if you don't provide it, you'll be asked for it

@karniv00l we need to add this to docs


Diagnostic: extend from_env function

Implements major part of #51.
This pr adds error type for from_env() and returns possibility to check if fds refer to pipe as optional feature.

Thanks for review, I'll wait other's comments.

Given how low-level this crate is I don't think that the Cargo feature added here will be all that useful since if it's in use it's buried so deep and will be difficult to configure.
Can you explain a bit more what the error handling around pipe detection is doing? Why is fcntl not sufficient and what is fstat catching otherwise? Is that catching real issues happening in the wild and allowing callers to recover?

I don't think that the Cargo feature added here will be all that useful

+1

Can you explain a bit more what the error handling around pipe detection is doing? Why is fcntl not sufficient and what is fstat catching otherwise?

The pipe check is the same thing that jobserver-rs did before https://github.com/alexcrichton/jobserver-rs/pull/6.

Is that catching real issues happening in the wild and allowing callers to recover?

It catches a real issue that happens in the wild.
The caller won't be able to recover, but it will be able to report a useful error that will allow the "second order caller" (build engineer) to fix the build environment.

If this is reverting back, is the use case in https://github.com/alexcrichton/jobserver-rs/pull/6 no longer valid?
For "catching things in the wild" I meant moreso the new logic to detect a valid file descriptor, less so "should this return errors at all" because that's naturally a "sure this should happen when the effort is put in".


Internal Error : Failed to fill whole buffer

Describe the bug
Hello,
I got this errors when indexing with Meillisearch v0.25.2
{"uid":2865,"indexUid":"immobilier","status":"failed","type":"documentAddition","details":{"receivedDocuments":18112,"indexedDocuments":0},"error":{"message":"failed to fill whole buffer","code":"internal","type":"internal","link":"https://docs.meilisearch.com/errors#internal"},"duration":"PT1559.222072714S","enqueuedAt":"2022-08-12T23:02:18.444815872Z","startedAt":"2022-08-13T03:17:56.964523522Z","finishedAt":"2022-08-13T03:43:56.186596236Z"}

To Reproduce
This is the first time i use Meilisearch so i don't know how to reproduce, i just checked the Meilisearch documentation to see the Error code and open this issue.
Pls help me to resolve this bug.
Meilisearch version: [v0.25.2]

Hello @leottk
Again, sorry for the inconvenience and thank you for using Meilisearch! While the error message appears to be different it seems it's also related to #2871  due to the fact that you are not able to successfully index your data to Meilisearch. Once again, I'd like to confirm if the format of your dataset is a valid JSON, CSV, or NDJSON.
Looking forward to your response. Thanks 🙂

I close this issue due to a lack of answers. Nothing is definitive of course, feel free to ask to re-open if needed 😊


[GSoC2024] Fix Proposal for Issue #7375 : (Related images are not included when exporting 3D datasets)

Issue Addressed
I resolved issue #7375, which pertained to the omission of related images from archives when exporting tasks in the Datumaro 3D format. This problem was pinpointed to the Datumaro framework's specific handling of the media parameter during the export process. When this parameter is specified, related_images were not being considered, leading to their absence in the export results and, consequently, to incomplete dataset exports.
To overcome this limitation and guarantee the inclusion of related images in the export outcomes, I have integrated the related images into the export process via the PointCloud object.
Solution Implemented
Further analysis revealed that the PointCloud constructor is specifically designed to accept an extra_images argument, aimed at encapsulating related images. However, simply passing the related images as string paths directly was inadequate because the extra_images argument requires a list of objects that possess a .path attribute—namely,Image objects. This mismatch between the expected input format and the provided string paths called for a crucial modification in the handling of related images.
To address this, I converted the related images, represented by string paths (dm_image[1]), into Image objects prior to passing them to the PointCloud constructor. This change ensures that the extra_images parameter is supplied with data in the correct format, thus enabling the successful inclusion of related images in the dataset export process.
Testing Methodology
To verify the effectiveness of this solution, I conducted a test using the test_canvas3d.zip archive found in the cvat/apps/engine/tests/assets directory of the CVAT repository. After creating a task with this archive and exporting it in the Datumaro 3D format, I confirmed that the related images, previously missing, were present in the resulting archive. This outcome affirms the resolution of the issue.
Checklist

[x] I submit my changes into the develop branch
[ ] I have created a changelog fragment
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Hi, thank you for the PR! Please add tests and make sure the paths are relative to the dataset root (not absolute). You can borrow some bits from this PR.

Hi, any updates on this PR?

will add tests by EOD

Added in cvat/apps/engine/tests/test_rest_api_3D.py . Pls take a look

Please add a changelog entry following the guide.

I can fix the Datumaro issue. However, the Sly format is not exporting related_images, which is why the error occurs, since we set related_files = True this time.

I can fix the Datumaro issue. However, the Sly format is not exporting related_images, which is why the error occurs, since we set related_files = True this time.

What do you mean by this? I can clearly see related images in the archive, but they have slightly different names.

Got it. Will change asap

Done. Pls take a look

Hi @bargav-bunny
Do you have any plans regarding the pull request?

Please, let us know if you are ready to finish the pull request. I will reopen it.


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1285

Questions ?
Please refer to the Backport tool documentation


Not determenistic behaviour of flann on android smartphone

I'm using the HierarchicalClusteringIndex from the flann module for image recognition. The image features are computed with ORB.
On my Linux computer (Ubuntu 14.04) everything works fine. On my Android smartphone (Galaxy Nexus, Android 4.3) the knnSearch via "findNeighbors" yields to different results after each restart of the application.
This case occurs both with OpenCV 2.4.X and OpenCV 3.0.
Here are parts of the code to reproduce:
	// init flann index
	LOGI("Initialize flann index");
	cvflann::Matrix<unsigned char> m_features(words.data, words.rows, words.cols);
	Ptr<cvflann::HierarchicalClusteringIndex<cvflann::Hamming<unsigned char> > > kdIndex =
			new cvflann::HierarchicalClusteringIndex<cvflann::Hamming<unsigned char> >
				(m_features,cvflann::HierarchicalClusteringIndexParams(10));
	kdIndex->buildIndex();

	// prepare knn-queries
	LOGI("Prepare query");
	vector<int> indices(1);
	vector<int> dists(1);

	cvflann::KNNResultSet<int> m_indices(1);
	m_indices.init(indices.data(),dists.data());

	LOGI("Perform query");
	for(int i = 0; i < query.rows; ++i){
		Mat row = query.row(i);
		// perform knn-query
		kdIndex->findNeighbors(m_indices, row.ptr<unsigned char>(0), cvflann::SearchParams(8));
		LOGD("row %i: index %i, distance %i",i,indices[0],dists[0]);
	}

where words is an Mat-object with 100 000 rows and 32 columns and type CV_8U. It is used as visual vocabulary. query is Mat-object that consists of image descriptors computed with ORB.

I get different results on Android as well every time calling findNeighbors(), what could cause this?


Initial history

This is all the original history from the dyladan/component-owners repository

@yurishkuro any idea why there is no CLA check happening on this PR?

@lizthegrey @bogdandrutu please configure EasyCLA for this repo
@dyladan please configure this repo per https://github.com/open-telemetry/community/blob/8b0922c1c9f2cbb67f2d4178f4438192e0ff7922/docs/how-to-configure-new-repository.md

Getting an infinite spinny from easycla trying to update our repos :/

https://github.com/communitybridge/easycla/issues/3145 -- filed ticket, got us on easycla v2, now it'll automatically be enabled on every new repo.

/easycla


Grouping: Various alternative hierarchies

Overview
In addition to allowing the user to generate outputs using hierarchies derived from LOINC (e.g. primary & supplementary part models), we also want to allow the option to derive hierarchies based on mappings to sources.
General approach
For hierarchies derived from external sources, these hierarchies won't include all terms from the source. The general approach is to start with the mapped terms, and create trees based on all ancestors.
Sub-issues

[ ] LOINC: primary part model
[ ] LOINC: supplementary part model
[ ] ChEBI
[ ] SNOMED

Closing in favor of:

#54

Closing because all that remains is:

#108


Add linguist-language git attribute for GitHub's sake

Otherwise, our Jenkinsfiles are rendered badly.

Compare
https://github.com/docker-library/meta-scripts/blob/676ab32f3fe9075dc35c4cc78962c3aa1ba065fd/Jenkinsfile.build
to
https://github.com/infosiftr/doi-meta-scripts/blob/cd19b51e2b1f33c67e310a568f417eb80e5a5747/Jenkinsfile.build

(it's even worse for Jenkinsfile.trigger that looks like it's rendering sanely ... until it doesn't, because it's rendering as "Apex")

CI failure is noted/described/tracked in https://github.com/docker-library/meta-scripts/issues/25 now :+1:


velodyne: 1.4.0-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository velodyne to 1.4.0-0:

upstream repository: https://github.com/ros-drivers/velodyne.git
release repository: https://github.com/ros-drivers-gbp/velodyne-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.6.6
previous version for package: 1.3.0-0

velodyne
* Merge pull request #160 <https://github.com/ros-drivers/velodyne/issues/160> from ros-drivers/maint/updating_package_xml_to_v2
* Updated all package.xmls to ver 2. Cleaned up catkin_lint errors.
  All package.xml files are now compatible with version 2 of the
  package.xml specification in REP 140. Removed some unnecessary
  execute permissions on a few files. Fixed a missing test_depend.
* Contributors: Andre Volk, Joshua Whitley

velodyne_driver
* Merge pull request #178 <https://github.com/ros-drivers/velodyne/issues/178> from sts-thm/bugfix_issue_`#174 <https://github.com/ros-drivers/velodyne/issues/174>`_
  Bugfix issue #174 <https://github.com/ros-drivers/velodyne/issues/174>
* Removed debug outputs
* Changes fixing deadlock for specific cut_angle values.
* Merge pull request #135 <https://github.com/ros-drivers/velodyne/issues/135> from cfneuhaus/bugfix
  Bugfix: when no device ip is set, we still want to filter by udp port.
* Merge pull request #170 <https://github.com/ros-drivers/velodyne/issues/170> from ros-drivers/maint/move_header_files
  Moving header files to traditional location inside include folders.
* Merge pull request #160 <https://github.com/ros-drivers/velodyne/issues/160> from ros-drivers/maint/updating_package_xml_to_v2
* Updated all package.xmls to ver 2. Cleaned up catkin_lint errors.
  All package.xml files are now compatible with version 2 of the
  package.xml specification in REP 140. Removed some unnecessary
  execute permissions on a few files. Fixed a missing test_depend.
* Merge pull request #151 <https://github.com/ros-drivers/velodyne/issues/151> from Axel13fr/feature/No_Communication_Diag_Update
* Fix packet rate for the Velodyne 32C
* Conventions: adding name for unused method parameter.
* Added a periodic update of the diagnostics so that when no data is received at all from the Velodyne, a diagnostic information will be published. The previous implementation would publish diagnostics only on packet reception.
* Merge pull request #139 <https://github.com/ros-drivers/velodyne/issues/139> from ASDeveloper00/vlp32
  Adding support for VLP-32C.
* Merge pull request #138 <https://github.com/ros-drivers/velodyne/issues/138> from volkandre/cut_at_specified_angle_feature
* cut_angle parameter is now in rad according to REP 103
* Fixed timestamp related bug found by @cfneuhaus, which was described here: https://github.com/ros-drivers/velodyne/pull/126#discussion_r154137793
* bugfix: when no device ip is set, we still want to filter by udp port.
* Contributors: Andre Volk, CNR, Denis Dillenberger, Frank Neuhaus, Jack O'Quin, Joshua Whitley, Sammy Pfeiffer, Tobias Athmer, axd, kennouni

velodyne_laserscan
* Merge pull request #170 <https://github.com/ros-drivers/velodyne/issues/170> from ros-drivers/maint/move_header_files
* Moving header files to traditional location inside include folders.
* Merge pull request #160 <https://github.com/ros-drivers/velodyne/issues/160> from ros-drivers/maint/updating_package_xml_to_v2
* Updated all package.xmls to ver 2. Cleaned up catkin_lint errors.
  All package.xml files are now compatible with version 2 of the
  package.xml specification in REP 140. Removed some unnecessary
  execute permissions on a few files. Fixed a missing test_depend.
* Merge pull request #146 <https://github.com/ros-drivers/velodyne/issues/146> from stsundermann/patch-2
  Use std::abs instead of fabsf
* Merge pull request #150 <https://github.com/ros-drivers/velodyne/issues/150> from ros-drivers/mikaelarguedas-patch-1
* update to use non deprecated pluginlib macro
* Use std::abs instead of fabsf
  cfg_.resolution is double but fabsf takes a float which may cause truncation of value.
* Contributors: Andre Volk, CNR, Joshua Whitley, Mikael Arguedas, Stephan Sundermann

velodyne_msgs
* Updated all package.xmls to ver 2. Cleaned up catkin_lint errors.
  All package.xml files are now compatible with version 2 of the
  package.xml specification in REP 140. Removed some unnecessary
  execute permissions on a few files. Fixed a missing test_depend.
* Updated cut_at_specified_angle_feature with latest master version.
* Contributors: Andre Volk, Joshua Whitley

velodyne_pointcloud
* Merge pull request #178 <https://github.com/ros-drivers/velodyne/issues/178> from sts-thm/bugfix_issue_`#174 <https://github.com/ros-drivers/velodyne/issues/174>`_
  Bugfix issue #174 <https://github.com/ros-drivers/velodyne/issues/174>
* Merge pull request #177 <https://github.com/ros-drivers/velodyne/issues/177> from C-NR/feature/WrapPointcloudData
  Feature/wrap pointcloud data
* Changes fixing deadlock for specific cut_angle values.
* moved definition of VPoint and VPointCloud back to namespace rawdata in rawdata.h
* put a wrapper around pointcloud data including a generic setter method to enable the use of arbitrary data structures  (pcl pointcloud, depth image, octomaps and so on) to be filled by just using RawData::unpack method with the wrapper object as parameter
* Merge pull request #170 <https://github.com/ros-drivers/velodyne/issues/170> from ros-drivers/maint/move_header_files
  Moving header files to traditional location inside include folders.
* Merge pull request #160 <https://github.com/ros-drivers/velodyne/issues/160> from ros-drivers/maint/updating_package_xml_to_v2
* Updated all package.xmls to ver 2. Cleaned up catkin_lint errors.
  All package.xml files are now compatible with version 2 of the
  package.xml specification in REP 140. Removed some unnecessary
  execute permissions on a few files. Fixed a missing test_depend.
* Merge pull request #136 <https://github.com/ros-drivers/velodyne/issues/136> from stsundermann/patch-1
  Use std::abs instead of abs
* Adding missing 32C configuration file.
* Merge pull request #139 <https://github.com/ros-drivers/velodyne/issues/139> from ASDeveloper00/vlp32
  Adding support for VLP-32C.
* Merge pull request #138 <https://github.com/ros-drivers/velodyne/issues/138> from volkandre/cut_at_specified_angle_feature
  Cut at specified angle feature
* Updated default cut_angle parameters in launch files after switching from deg to rad.
* Use std::abs instead of abs
  abs is the c version which returns an integer. This is probably not intended here, so use the templated std::abs function.
* Contributors: Andre Volk, Autonomoustuff Developer, CNR, Joshua Whitley, Kyle Rector, Stephan Sundermann, Tobias Athmer, kennouni

Holding for Kinetic sync.


support mixed xml reference config and annotation dubbo config

What is the purpose of the change
support mixed xml reference config and annotation dubbo config
Brief changelog

DubboConfigBindingBeanPostProcessor

For the Issue requirements

[ ] I have searched the issues of this repository and believe that this is not a duplicate.
[ ] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.6.5
Operating System version: mac os 10.13.1
Java version: 1.8

Steps to reproduce this issue
It is easy to reproduce this problem

following is my config(here use the multiple config, but it does not cause the problem, it is same with single config)

dubbo.applications.my-application.logger=slf4j
dubbo.protocols.protocol.accesslog=true
dubbo.protocols.protocol.id=dubbo
dubbo.protocols.protocol.name=dubbo

dubbo.registries.unitRegistry.id=unitRegistry
dubbo.registries.unitRegistry.address=zookeeper://<IP_ADDRESS>:2181
dubbo.registries.baseRegistry.id=baseRegistry
dubbo.registries.baseRegistry.address=zookeeper://<IP_ADDRESS>:2285
dubbo.registries.commonRegistry.id=commonRegistry
dubbo.registries.commonRegistry.address=zookeeper://<IP_ADDRESS>:2185

server.port=13164
dubbo.applications.my-application.id=xxx-service
dubbo.applications.my-application.name=xxx-service
dubbo.applications.my-application.qosPort=13166
dubbo.protocols.protocol.port=13165

with the config before, then load reference config in xml, it cause exception

Expected Result
start normally.
Actual Result
cannot start application and throws exception:
Caused by: java.lang.IllegalStateException: ApplicationConfig.application == null
  at com.alibaba.dubbo.config.AbstractConfig.appendParameters(AbstractConfig.java:222) ~[dubbo-2.6.5.jar:2.6.5]
  at com.alibaba.dubbo.config.AbstractConfig.appendParameters(AbstractConfig.java:172) ~[dubbo-2.6.5.jar:2.6.5]
  at com.alibaba.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:303) ~[dubbo-2.6.5.jar:2.6.5]
  at com.alibaba.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:163) ~[dubbo-2.6.5.jar:2.6.5]
  at com.alibaba.dubbo.config.spring.beans.factory.annotation.ReferenceAnnotationBeanPostProcessor$ReferenceBeanInvocationHandler.init(ReferenceAnnotationBeanPostProcessor.java:163) ~[dubbo-2.6.5.jar:2.6.5]
  at com.alibaba.dubbo.config.spring.beans.factory.annotation.ReferenceAnnotationBeanPostProcessor$ReferenceBeanInvocationHandler.access$100(ReferenceAnnotationBeanPostProcessor.java:147) ~[dubbo-2.6.5.jar:2.6.5]
  at com.alibaba.dubbo.config.spring.beans.factory.annotation.ReferenceAnnotationBeanPostProcessor.buildInvocationHandler(ReferenceAnnotationBeanPostProcessor.java:141) ~[dubbo-2.6.5.jar:2.6.5]
  at com.alibaba.dubbo.config.spring.beans.factory.annotation.ReferenceAnnotationBeanPostProcessor.buildProxy(ReferenceAnnotationBeanPostProcessor.java:123) ~[dubbo-2.6.5.jar:2.6.5]
  at com.alibaba.dubbo.config.spring.beans.factory.annotation.ReferenceAnnotationBeanPostProcessor.doGetInjectedBean(ReferenceAnnotationBeanPostProcessor.java:117) ~[dubbo-2.6.5.jar:2.6.5]
  at com.alibaba.dubbo.config.spring.beans.factory.annotation.ReferenceAnnotationBeanPostProcessor.doGetInjectedBean(ReferenceAnnotationBeanPostProcessor.java:50) ~[dubbo-2.6.5.jar:2.6.5]
  at com.alibaba.spring.beans.factory.annotation.AnnotationInjectedBeanPostProcessor.getInjectedObject(AnnotationInjectedBeanPostProcessor.java:340) ~[spring-context-support-1.0.2.jar:?]
  at com.alibaba.spring.beans.factory.annotation.AnnotationInjectedBeanPostProcessor$AnnotatedFieldElement.inject(AnnotationInjectedBeanPostProcessor.java:520) ~[spring-context-support-1.0.2.jar:?]
  at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:88) ~[spring-beans-4.3.2.RELEASE.jar:4.3.2.RELEASE]
  at com.alibaba.spring.beans.factory.annotation.AnnotationInjectedBeanPostProcessor.postProcessPropertyValues(AnnotationInjectedBeanPostProcessor.java:128) ~[spring-context-support-1.0.2.jar:?]
  ... 15 more

what cause this problem
for (String beanName : beanNames) {
    registerDubboConfigBean(beanName, configClass, registry);
    registerDubboConfigBindingBeanPostProcessor(prefix, beanName, multiple, registry);
}

dubbo 2.6.5 register a DubboConfigBindingBeanPostProcessor for each DubboConfigBean to binding properties with the config. But config reference in xml may cause the ApplicationConfig or other config initialize before DubboConfigBindingBeanPostProcessor register. So the DubboConfigBean have no chance to binding properties.
And I try to give the most priority to the DubboConfigBindingBeanPostProcessor. But it is also failed. Because of the afterPropertiesSet method: applicationContext.getBean(DubboConfigBinder.class) this will cause the beanDefinitions traverse and the ReferenceBean will initialize. So cause the same problem.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

In your demo, the configuration is configured in application.properties but not in dubbo.properties.

ok. Change filename to dubbo.properties, it seems work well.
But I think it is not the actual problem i am talking about.
I want to use the feature of the dubbo-externalized-configuration, by using DubboConfigBindingRegistrar to register dubbo application/registry from the properties from the enviroment in spring.

Please consider using apache/dubbo-spring-boot-project if you want to put configs in application.properties. Pure Dubbo only support read properties from dubbo.properties.
Feel free to reopen if necessary.


HTML Element with 2 types of functions

It's possible to combine two functions of "MaterializeDirectives" on one HTML element?
eg:
Open Modal

or
Open Modal

Interesting idea. Not sure how the materializeParams would correspond to each of them, though.
How about you try the new materializeActions feature?
Here's the relevant piece from the README:
Another useful option is emitting actions on an element. You may want to do that for calling Materialize functions, like closing a modal dialog or triggering a toast. You can do that by setting the materializeActions attribute, which accepts an EventEmitter :

Modal Header

A bunch of text

    Close

  actions = new EventEmitter<string>();
  closeModel() {
    this.actions.emit("closeModal");
  }


Running haddock with "--hyperlinked-source" just creates / pollutes src directory

See https://github.com/commercialhaskell/stack/issues/2429 .  The issue is that stack has been using haddock --hyperlinked-source to detect if haddock supports hyperlinked source.  When haddock --hyperlinked-source runs, nothing happens but style.css and highlight.js get put into a src dir.

Dupe of #536

Ah, I should have searched!


Monitoring a Microsoft SQL Server database using Solar Winds Database Performance Analyzer

Article checklist
Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #2938

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

@srishilesh This is the new PR. I believe it is now looking okay

@srishilesh This is the new PR. I believe it is now looking okay

@ruphus-muita
This looks perfect

Duplicate if #3471

Could you fix the minor issues highlighted in this plagiarism report. Thanks
Monitoring a Microsoft SQL Server database using Solar Winds Database Performance Analyzer #3523.pdf

Could you fix the minor issues highlighted in this plagiarism report. Thanks
Monitoring a Microsoft SQL Server database using Solar Winds Database Performance Analyzer #3523.pdf

@WanjaMIKE  This done. Please check. Thanks

@ruphus-muita
Thanks for the change.
I'll complete my next round of review by tomorrow.

@ruphus-muita
Thanks for the change.
I'll complete my next round of review by tomorrow.

Are you done?

@srishilesh All done

@srishilesh are we done with this PR?

@srishilesh are we done with this PR?

@ruphus-muita
The final round of review by me, is in progress. Please wait patiently.

@ruphus-muita could you perform more analyses using the tool. I found that most of the article focused on the installation part which seems more straight-forward. Thanks

@WanjaMIKE Kindly clarify on what you mean by more analyses.

I mean use the tool to conduct further tests and then explain them in the article. Thanks

I mean use the tool to conduct further tests and then explain them in the article. Thanks

@WanjaMIKE This is done. Kindly confirm

Overall nice job gents 👍


Updating nbsite and adding grabcut link

This PR:

Adds link to grabcut
Uses latest version of nbsite
Updates copyright year

Once this is green I'll merge it, tag a dev release and then tag a real release.

Links to earthsim. Looks like:


net/http: client.Do should mask EOF as ErrUnexpectedEOF

func Test(t *testing.T) {
	server := httptest.NewServer(
		http.HandlerFunc(
			func(w http.ResponseWriter, r *http.Request) {
				rwc, _, _ := w.(http.Hijacker).Hijack()
				defer rwc.Close()
			},
		),
	)
	defer server.Close()

	_, err := http.Get(server.URL)
	if err != nil {
		t.Fatalf("GET returned error: %v", err)
	}
}

The preceding test prints GET returned error: EOF, which is strange since io.EOF is often an "error" signaling normal termination of some stream. Instead, Do should mask the error as io.ErrUnexpectedEOF, which is more indicative of an abrupt termination.

We tried to fix this once and had to revert it. There's a testing locking in this behavior. :-/
But maybe we can revisit.

@bradfitz Can you link the old fix for reference?

@ibrasho, you can probably find it in git history as quickly as I could. (which might not be super quick)


Fixes #153

Credit card number lengths are extended for VISA and DISCOVER. This PR also fixes #153.
Source: https://en.wikipedia.org/wiki/Payment_card_number

Thanks, @mkorkmaz


Error 404

Hi.
I get error 404 in page site.com/try, faq and etc. in production. But in local site.com/try, faq and other work.
How to fix its problem?
Thank you.

Well, can you give me a bit more information?

How have you deployed the application?

Did you run composer install and npm install on your production server?

What web server are you using?

Is your webroot correctly set up?

I have project in Mac OS (Local). All page work.
For deploy to server i just make archive from my laptop.
Yes i have npm install and composer install
My webroot in production server.

server {
server_name screener.space www.screener.space;
ssl_certificate "/var/www/httpd-cert/www-root/screener.space.crt";
ssl_certificate_key "/var/www/httpd-cert/www-root/screener.space.key";
ssl_ciphers EECDH:+AES256:-3DES:RSA+AES:!NULL:!RC4;
ssl_prefer_server_ciphers on;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_dhparam /etc/ssl/certs/dhparam4096.pem;
charset off;
index index.php index.html;
disable_symlinks if_not_owner from=$root_path;
include /etc/nginx/vhosts-includes/.conf;
include /etc/nginx/vhosts-resources/screener.space/.conf;
access_log /var/www/httpd-logs/screener.space.access.log;
error_log /var/www/httpd-logs/screener.space.error.log notice;
ssi on;
set $root_path /var/www/www-root/data/www/screener.space/public;
root $root_path;
listen <IP_ADDRESS>:443 ssl;
location / {
location ~ [^/].ph(p\d*|tml)$ {
try_files /does_not_exists @php;
}
}
location @php {
fastcgi_index index.php;
fastcgi_param PHP_ADMIN_VALUE "sendmail_path = /usr/sbin/sendmail -t -i -f<EMAIL_ADDRESS>fastcgi_pass unix:/var/www/php-fpm/www-root.sock;
fastcgi_split_path_info ^((?U).+.ph(?:p\d*|tml))(/?.+)$;
try_files $uri =404;
include fastcgi_params;
}
}

Why i get error in production? In local in my laptop all work.

set $root_path /var/www/www-root/data/www/name.space/public;

Maybe this has to be updated to the actual folder path, where you've uploaded the project?
This is the NGINX configuration, I'm currently using for hosting screeenly.com. (I'm using Laravel Forge)
# FORGE CONFIG (DOT NOT REMOVE!)
include forge-conf/screeenly.com/before/*;

server {
    listen 80;
    listen [::]:80;
    server_name screeenly.com;
    root /home/forge/screeenly.com/public;

    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA:!3DES';
    ssl_prefer_server_ciphers on;
    ssl_dhparam /etc/nginx/dhparams.pem;

    add_header X-Frame-Options "SAMEORIGIN";
    add_header X-XSS-Protection "1; mode=block";
    add_header X-Content-Type-Options "nosniff";

    index index.html index.htm index.php;

    charset utf-8;

    # FORGE CONFIG (DOT NOT REMOVE!)
    include forge-conf/screeenly.com/server/*;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }

    access_log off;
    error_log  /var/log/nginx/screeenly.com-error.log error;

    error_page 404 /index.php;

    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
        fastcgi_index index.php;
        include fastcgi_params;
    }

    location ~ /\.(?!well-known).* {
        deny all;
    }
}

# FORGE CONFIG (DOT NOT REMOVE!)
include forge-conf/screeenly.com/after/*;

Could you also please check the Installation Guide from Laravel and see if your server supports everything Laravel needs?

set $root_path /var/www/www-root/data/www/name.space/public;

Maybe this has to be updated to the actual folder path, where you've uploaded the project?
This is the NGINX configuration, I'm currently using for hosting screeenly.com. (I'm using Laravel Forge)
# FORGE CONFIG (DOT NOT REMOVE!)
include forge-conf/screeenly.com/before/*;

server {
    listen 80;
    listen [::]:80;
    server_name screeenly.com;
    root /home/forge/screeenly.com/public;

    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA:!3DES';
    ssl_prefer_server_ciphers on;
    ssl_dhparam /etc/nginx/dhparams.pem;

    add_header X-Frame-Options "SAMEORIGIN";
    add_header X-XSS-Protection "1; mode=block";
    add_header X-Content-Type-Options "nosniff";

    index index.html index.htm index.php;

    charset utf-8;

    # FORGE CONFIG (DOT NOT REMOVE!)
    include forge-conf/screeenly.com/server/*;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }

    access_log off;
    error_log  /var/log/nginx/screeenly.com-error.log error;

    error_page 404 /index.php;

    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
        fastcgi_index index.php;
        include fastcgi_params;
    }

    location ~ /\.(?!well-known).* {
        deny all;
    }
}

# FORGE CONFIG (DOT NOT REMOVE!)
include forge-conf/screeenly.com/after/*;

Could you also please check the Installation Guide from Laravel and see if your server supports everything Laravel needs?

Its work now. Thank you.
But when i want make Screenshot
I get error:
Something went wrong capturing this website. Is it a Javascript heavy site or loads lots of external content? If you think this is an error contact us.
Why i get its error?

I assume you're using the /try URL? The error usually comes from the fact the Google Chrome has not been properly installed.
Screeenly uses Google Chrome to take Screenshots.
The wiki has a description on how you can install Google Chrome on an Ubuntu server. The underlying package screeenly uses has more information about this: Link
I'm closing this issue now, as the original error has been fixed.


Fails to parse edge sensitive path in specify

Steps to reproduce the issue
module top(input clk, d, output q);
specify
  // Fails:
  (posedge clk => (q +: d)) = (3,1);
  (/*posedge*/ clk => (q +: d)) = (3,1);
  (posedge clk *> (q +: d)) = (3,1);
  (/*posedge*/ clk *> (q +: d)) = (3,1);

  // Works:
  (/*posedge*/ clk => q) = (3,1);
  (/*posedge*/ clk *> q) = (3,1);
endspecify
endmodule

From: http://verilog.renerta.com/source/vrg00014.htm

Note: This is in non-specify mode. read_verilog -specify can parse this just fine.

(/*posedge*/ clk => (q +: d)) = (3,1);
(/*posedge*/ clk *> (q +: d)) = (3,1);

That's not valid specify syntax afaict. (q +: d) requires an edge. #1147 will fix fix the rest.
(Yes, read_verilog -specify parses this invalid syntax. I was more concerned about parsing legal code than rejecting illegal code when I wrote read_verilog -specify.)


[UBS Courier tab UI] Names and order of services under "Послуги" do not correspond to mockup

Environment: macOS High Sierra 10.13.6, Google Chrome, version 91.0.4472.114 (Official Build) (x86_64).
Reproducible: always.
Build found: June 26, 2021.
Preconditions

Log into Figma as an existing user.
Log into GreenCity as an existing user.

Steps to reproduce

Go to https://ita-social-projects.github.io/GreenCityClient/#/
Click on 'Увійти'
Log in as a registered user
Click on 'UBS кур'єр' tab
In a new browser tab, go to https://www.figma.com/file/092AhCGadc1Hq8nAysxmYB/ITA-Greencity-УБС?node-id=13739%3A210
Refer to Final Version mockups

Actual result
Services names and their order is listed as follows (screenshot attached):

Expected result
Services names and their order should be listed according to the mockup (screenshot attached):

User story and test case links
#2196 #2379
Test case GC-1935
Labels to be added
"Bug", "UBS Courier", "UBS", "Change Request", "GreenCityUBS", Priority ("pri: low"), Severity ("severity: trivial"), Type ("UI").

The issue is not relevant.


Implement SSH key management for user and portal keys

Implement the necessary endpoints and access controls for managing user and portal SSH key(pair)(s)

Addressed on #25
In order to migrate the database schema you need to alter fabric_people table:
postgres=# alter table fabric_people add column bastion_login character varying;
postgres=# alter table fabric_people add constraint uniq_uuid UNIQUE (uuid);

There are basically 6 new API endpoints.  Because we want to stay compatible with how Comanage stores keys, in the above structure the first part is referred to as ‘name’ (ssh-rsa or ssh-ecdsa or other). It is actually more of a key type, but they call it a name. The middle part is base64-encoded public key (referred to as ‘public_key’ in various structures below) and the last part is called ‘comment’.
GET /keylist – it is for bastion hosts to call to retrieve changed keys (added or expired/deactivated).
GET /sshkeys/{keytype}/{uuid} – this one gets a list of available keys of type ‘bastion’ or ‘sliver’ for user with uuid ‘uuid’. What is returned is a list of SshKeyShort structures (you should be able to see in Swagger. The only thing is ‘public_key’ field will not be returned in this case. Only currently active keys are returned.
POST /sshkeys/{keytype}/{uuid} – upload a public key (entire public key as a single string in standard OpenSSH format) to UIS. UIS internally will break it up into ‘name’, ‘public_key’ and ‘comment’ fields and validate that the key is either RSA of 3072 bits or longer or ECDSA of 256 bits or longer. Other key types (DSA) or shorter lengths will be rejected with an error.
PUT  /sshkeys/{keytype}/{uuid} – generates and returns a keypair as two separate fields ‘private_openssh’ (in PEM format) and ‘public_openssh’ in the standard OpenSSH format where name, public_key and comment are concatenated over spaces. These can basically be saved into files as is (one as private key, other as public) by the user. In the background UIS saves the public key.
GET /sshkeys/{keytype}/{uuid}/{keyid} – retrieves a full entry of the key including the full public_key string, fingerprint, its status (active or not) and reason for deactivation (auto-expired or removed by user using DELETE call below).
DELETE /sshkeys/{keytype}/{uuid}/{keyid} – deactivate a given key – doesn’t actualy delete, but it will no longer be returned by the GET /sshkeys/{keytype}/{uuid}. It can still be retrieved by the GET /sshkeys/{keytype}/{uuid}/{keyid} but it wil be marked as deactivated.
In this version keys expire after 5 minutes and are permanently deleted after 10 minutes. So upon upload the key is active, 5 minutes later it because inactive (auto-expires) and after 5 more minutes gets permanently deleted.

Addressed on #25


Replace undici with native https.request

Refs: https://github.com/RafaelGSS/is-my-node-vulnerable/issues/19
Before
Warning is shown about Node.js undici on npm audit
$ npm audit | grep undici
undici  <=5.28.3
CRLF Injection in Nodejs ‘undici’ via host - https://github.com/advisories/GHSA-5r9g-qh6m-jxff
node_modules/undici

After
No warning shown about undici, as the dependency doesn't exist
$ npm audit | grep undici

The Node.js native fetch, which is implemented from undici, if available without --experimental-fetch flag since Node.js 18.x
The undici dependency can be replaced with Node.js native fetch instead of https.request after https://github.com/RafaelGSS/is-my-node-vulnerable/pull/23 is merged.

Considering we are now targeting really old Node.js versions, I believe https should be better as fetch isn't supported on EOL versions.


Add transactions list on the Dapp Store screen.

Add transactions list on the Dapp Store screen.
https://zpl.io/2v3yMy7
https://zpl.io/aNxBwBD

the list should show only contract transactions

the list should be foldable (default state - folded)

the list should unfold only for a part of the screen (30% of the screen)

Add transactions list in every Dapp where needed
https://zpl.io/29mN0BY
https://zpl.io/aR4mpyg
https://zpl.io/br3m1lW

the list should show only transactions of chosen contract
the "Source" column should be hidden
Transactions details should have "DAPP name", "Application Shader ID" and "Description fields".

the list should be foldable (default state - folded)
the list should unfold only for a part of the screen (30% of the screen)

Please change from 'Shader Id' to "Application Shader ID"

Make the entire zone clickable (highlighted in red), now only in the middle(highlighted in green)

Change the direction of the arrow, as the table opens up and closes down.

Is correct now, it is Shader ID. Application shaders do not have ID.

checked


v0.15.3 tag is missing

It looks like you forgot to tag 0.15.3 when you released it.

The missing tag was added in the meanwhile.


Where are the Requirements (specific billing) for Solution template?

The Hyperlink for Requirements: Azure Marketplace: Transact: Azure apps: Solution template (i.e. https://docs.microsoft.com/en-us/azure/marketplace/listing-type-requirements#requirements:-azure-marketplace:-transact:-azure-apps:-solution-template) Doesn't seem to take me to where I was expecting.

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

ID: aaa68fda-a8cc-848c-6e7f-dc5a6c55001a
Version Independent ID: 2de2fccc-02a4-9893-7be6-7f2f667347e1
Content: Requirements by Listing Type
Content Source: articles/marketplace/listing-type-requirements.md
Service: marketplace
GitHub Login: @jm-aditi-ms
Microsoft Alias: ellacroi

Hi Nastassia,
Thank you for the notification,
This will be added to the next update for the marketplace pages.
Thank you, Joe Martin
Joe Martin
Tech. Writer 2  |  P+SE  |  C+A  |  Aditi at Microsoft
<EMAIL_ADDRESS>|  +1.206.883.6164
From: Nastassia<EMAIL_ADDRESS>Sent: Wednesday, June 13, 2018 4:48 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Joe Martin (Aditi Staffing LLC<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [MicrosoftDocs/azure-docs] Where are the Requirements (specific billing) for Solution template? (#10178)
The Hyperlink for Requirements: Azure Marketplace: Transact: Azure apps: Solution template (i.e. https://docs.microsoft.com/en-us/azure/marketplace/listing-type-requirements#requirements:-azure-marketplace:-transact:-azure-apps:-solution-templatehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fmarketplace%2Flisting-type-requirements%23requirements%3A-azure-marketplace%3A-transact%3A-azure-apps%3A-solution-template&data=02|01|v-josepm%40microsoft.com|f23ad000db934d9f0e2408d5d188086e|72f988bf86f141af91ab2d7cd011db47|1|0|636645304545835920&sdata=Vyki96%2BImHHRXPvzIDMWwweIcBWrJudpe9lvwg5XeBE%3D&reserved=0) Doesn't seem to take me to where I was expecting.

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

ID: aaa68fda-a8cc-848c-6e7f-dc5a6c55001a
Version Independent ID: 2de2fccc-02a4-9893-7be6-7f2f667347e1
Content: Requirements by Listing Typehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fmarketplace%2Flisting-type-requirements%23requirements%3A-azure-marketplace%3A-transact%3A-azure-apps%3A-solution-template&data=02|01|v-josepm%40microsoft.com|f23ad000db934d9f0e2408d5d188086e|72f988bf86f141af91ab2d7cd011db47|1|0|636645304545845928&sdata=qq21IUoh4duEHTWITYe4qzMjnlqGOx5qTDom3tOY8Yg%3D&reserved=0
Content Source: articles/marketplace/listing-type-requirements.mdhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fazure-docs%2Fblob%2Fmaster%2Farticles%2Fmarketplace%2Flisting-type-requirements.md&data=02|01|v-josepm%40microsoft.com|f23ad000db934d9f0e2408d5d188086e|72f988bf86f141af91ab2d7cd011db47|1|0|636645304545855941&sdata=hgPeFUvUasXvvLXpUKqR3QZoSjyIlkwH%2BNw0bE6evbY%3D&reserved=0
Service: marketplace
GitHub Login: @jm-aditi-mshttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjm-aditi-ms&data=02|01|v-josepm%40microsoft.com|f23ad000db934d9f0e2408d5d188086e|72f988bf86f141af91ab2d7cd011db47|1|0|636645304545855941&sdata=dOM%2FAF4gfkxjeN9meEd%2BMxqVoPP5o1PWpvd2ZxozKPo%3D&reserved=0
Microsoft Alias: ellacroi

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F10178&data=02|01|v-josepm%40microsoft.com|f23ad000db934d9f0e2408d5d188086e|72f988bf86f141af91ab2d7cd011db47|1|0|636645304545865945&sdata=L8FuHDEnlSJ9zDpzsQ9kZUGlRPiAPB1fGeQiimoqwoE%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAkUN9HFBVsXzIPw4EXWPox9K94ftjm_Fks5t8aSUgaJpZM4UnGuC&data=02|01|v-josepm%40microsoft.com|f23ad000db934d9f0e2408d5d188086e|72f988bf86f141af91ab2d7cd011db47|1|0|636645304545865945&sdata=0Fy%2Fsg0ZnbzuaoqSi0Q69Wr7hCeDm0mFf6hXEc0yGFs%3D&reserved=0.

#please-close addressed in a separate PR


[FeatureRequest]: update the docs with newer links

Contact Details
No response
Is your feature request related to a problem? Please describe
the docs are linking e.g. https://cloud.google.com/ai-platform/training/docs/using-hyperparameter-tuning which is deprecated, would be nice to update it
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

Done as part of https://github.com/avast/wanna-ml/pull/122