use Buffer.from rather than new Buffer []

get all tests passing, and increase the in-browser test set

This is because new Buffer [1,2,3] is deprecated in node 6+.

In Firefox :(

It looks like there is a number of new Buffer still there:
e.g.
https://github.com/keybase/kbpgp/blob/44a0e554f01143f4c788f021b526916cdfdb8045/src/keybase/hilev.iced
Documentation seems to say that all uses of new Buffer are deprecated https://nodejs.org/api/buffer.html
Do we leave the "non-obvious" ones for now?

I don't think Firefox should ever see this, since it's being polyfilled by Browserify, no? Can you try make test-browser in Firefox?

This was from make test-browser, sorry for not mentioning it.

Weird, I can't repro. Works fine for me on Firefox. Btw, in Chrome debugging, Buffer.from doesn't work either
Those remnant new Buffer are not using an array as an argument. They are either using an integer (for size of buffer to allocate) or are using string initialization.  I think both of those modes of operation are not deprecated.

(I'm running 46.0.1)

@zapu can you post a stack trace from your Firefox failure?

I had to leave for a while, sorry. It was failing in curve oid definitions IIRC. I'll try it some more when I get back, maybe it didn't buils correctly.
Dnia 11.04.2017 o godz. 15:23 Maxwell Krohn<EMAIL_ADDRESS>napisał(a):

@zapu can you post a stack trace from your Firefox failure?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Looks like it was old browserify version, sorry for that.

no worries
On Tue, Apr 11, 2017 at 12:23 PM, Michał Zochniak<EMAIL_ADDRESS>wrote:

Looks like it was old browserify version, sorry for that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/kbpgp/pull/147#issuecomment-293317522, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA05_3DVvgdgWspoewFPqkYIoCeoUS4lks5ru6kQgaJpZM4M4zul
.

otherwise looks good, I'm only worried that they are deprecating all of the constructors so we might have to do more refactoring later.

Whoops, you're right, I didn't see that at first.  I should go back and fix the rest.

i'll fix it!

See #181


Intermittent Hangs on Registry Push

Environment
Device and OS: AMD64 / Ubuntu 22.04
App version: 0.25.2
Kubernetes distro being used: K3D K3S v1.25.7+k3s1
Other: Big Bang 1.57.1
Steps to reproduce

zarf package deploy zarf-package-big-bang-example-amd64-1.57.1.tar.zst --confirm --log-level=trace
Occasionally the process gets hung up "Updating image ..."

Expected result
That things wouldn't get hung up, and continue along.
Actual Result
Things get hung up and/or sometimes fail / timeout.
Visual Proof (screenshots, videos, text, etc)

  DEBUG   2023-04-06T20:20:34Z  -  crane.Push() /tmp/zarf-1329914535/images:registry1.dso.mil/ironbank/fluxcd/kustomize-controller:v0.34.0 -> <IP_ADDRESS>:34857/ironbank/fluxcd/kustomize-controller:v0.34.0)
└ (/home/runner/work/zarf/zarf/src/pkg/packager/deploy.go:403)
  ⠦  Updating image registry1.dso.mil/ironbank/fluxcd/kustomize-controller:v0.34.0 (2m5s))
  ⠧  Updating image registry1.dso.mil/ironbank/fluxcd/kustomize-controller:v0.34.0 (2m5s)
  DEBUG   2023-04-06T20:22:44Z  -  "msg"="error creating error stream for port 34857 -> 5000: Timeout occurred\n" "error"=null
└ (/home/runner/go/pkg/mod/github.com/go-logr/logr@v1.2.4/funcr/funcr.go:183)
  DEBUG   2023-04-06T20:24:01Z  -  "msg"="error creating error stream for port 34857 -> 5000: Timeout occurred\n" "error"=null
└ (/home/runner/go/pkg/mod/github.com/go-logr/logr@v1.2.4/funcr/funcr.go:183)
  DEBUG   2023-04-06T20:24:03Z  -  "msg"="error creating error stream for port 34857 -> 5000: Timeout occurred\n" "error"=null
└ (/home/runner/go/pkg/mod/github.com/go-logr/logr@v1.2.4/funcr/funcr.go:183)
  DEBUG   2023-04-06T20:33:33Z  -  "msg"="lost connection to pod\n" "error"=null.0 (13m13s)
└ (/home/runner/go/pkg/mod/github.com/go-logr/logr@v1.2.4/funcr/funcr.go:183)

Full logs:
full-logs.txt
Severity/Priority
There is a workaround, by keeping retrying until the process succeeds.
Additional Context

I don't believe this is specifically related to the bigbang component.
I have seen this happen on zarf init as well, specifically when pushes are happening to the registry.
I tested to see if the tunnel was still active and it was during the time of the error.

Interesting piece of information I think, when connected to the console (using either SSM or SSH) of an EC2 instance is when we see this issue.  When running this locally from pointed to the same K8S cluster, I have no issues.

I think this may have something to do with using k3d.  I'm not seeing the intermittent issues with k3s.

@dgershman have you gotten a chance to try v0.26.0 and are you seeing any issues with that and k3d?

Still having issues with K3D and tried with v0.26.1.  It times out on the registry push step.  This is the latest response:
     ERROR:  Failed to deploy package: unable to deploy all components in this Zarf Package: unable to deploy
             component bigbang: unable to push images to the registry: Head
             "http://<IP_ADDRESS>:46657/v2/ironbank/opensource/kubernetes/kubectl/blobs/sha256:b4f2e7ad23124dea1bfd0a239be05aaa5c7ddad088a5039b7cf799eddcfa278a":
             dial tcp <IP_ADDRESS>:46657: connect: connection refused
     ERROR:  Failed to deploy package: unable to deploy all components in this Zarf Package: unable to deploy
             component bigbang: unable to push images to the registry: Head
             "http://<IP_ADDRESS>:46657/v2/ironbank/opensource/kubernetes/kubectl/blobs/sha256:b4f2e7ad23124dea1bfd0a239be05aaa5c7ddad088a5039b7cf799eddcfa278a":
             dial tcp <IP_ADDRESS>:46657: connect: connection refused
     ERROR:  Failed to deploy package: unable to deploy all components in this Zarf Package: unable to deploy
             component bigbang: unable to push images to the registry: Head
             "http://<IP_ADDRESS>:46657/v2/ironbank/opensource/kubernetes/kubectl/blobs/sha256:b4f2e7ad23124dea1bfd0a239be05aaa5c7ddad088a5039b7cf799eddcfa278a":
             dial tcp <IP_ADDRESS>:46657: connect: connection refused
     ERROR:  Failed to deploy package: unable to deploy all components in this Zarf Package: unable to deploy
             component bigbang: unable to push images to the registry: Head
             "http://<IP_ADDRESS>:46657/v2/ironbank/opensource/kubernetes/kubectl/blobs/sha256:b4f2e7ad23124dea1bfd0a239be05aaa5c7ddad088a5039b7cf799eddcfa278a":
             dial tcp <IP_ADDRESS>:46657: connect: connection refused

Thanks for the update @dgershman the SSH note might be an interesting / good lead to look into as well - some but not all had reported that this was happening on EC2 VMs over SSH - I had thought it was bad networking and tested with that locally but potentially there is something more going on with driving image uploads from an SSH session.  I'll see if I can keep digging

@dgershman doing some more testing on this, but if you get a chance does the code in https://github.com/defenseunicorns/zarf/pull/1721 solve the hanging for you? (note that parts of the push/pull of OCI Zarf packages are broken on that PR - not sure if that is in your flow though - won't affect local Zarf packages)

@dgershman doing some more testing on this, but if you get a chance does the code in #1721 solve the hanging for you? (note that parts of the push/pull of OCI Zarf packages are broken on that PR - not sure if that is in your flow though - won't affect local Zarf packages)

Putting this on my todo list for today.

I ran one test so far that looked good.  Will do two more tomorrow.

@dgershman doing some more testing on this, but if you get a chance does the code in #1721 solve the hanging for you? (note that parts of the push/pull of OCI Zarf packages are broken on that PR - not sure if that is in your flow though - won't affect local Zarf packages)

Putting this on my todo list for today.

I ran one test so far that looked good. Will do two more tomorrow.

I think we are good!

Ok going to clean up the PR and then rollback one change we made that didn't fix anything (and at this point only serves to slow down image pushes).  Will leave this open though in case this doesn't fully solve the issue - the main thought is that the multithreaded jobs in crane are either overwhelming the resource limits of the registry pod and or they are stepping on each other and resulting in a stuck state.

Moving this back a milestone to give the fixes in v0.27.0 some time to bake with the community to see if this is truly fixed.

Closing as fixed for now - we can reopen if it presents itself again

We are still seeing this issue in zarf version 0.29.2. We have a multi-node cluster on AWS EC2 running RKE2 v1.26.9+rke2r1. Our package size is about 2.9G, the "zarf package deploy..." command stalls and hangs about 80% of the time or so. A retry usually works fine.
Here are a few things that we noticed after some extensive testing:

this issue is not seen on a single EC2 node RKE2 cluster, it seems to only occur on multi-node clusters.
our zarf docker registry is backed by S3. The issue is always seen in this case, but only if a multi-node cluster.
if we back the registry with the default PVC (instead of S3), the issue is not seen at all. Since data transfer to S3 is slower than to the EBS backed PVC, maybe this extra time causes the problem to appear?
disabling or enabling the zarf docker registry HPA doesn't seem to matter either ways.

Debug logs from our gitlab runner job output are attached. Can you please re-open this issue, else let me know if I should create a new issue? Thanks.
job.txt


Umbraco 10 error: Could not load type Umbraco.Deploy.Core.IDiskEntityService

I'm trying to upgrade an Umbraco Cloud site to v10, using this documentation
https://our.umbraco.com/documentation/Umbraco-Cloud/Upgrades/Upgrading-from-9-to-10/
The last thing in step 3 is to build and run locally, build is fine, but when running it, I get a WSOD with the following message
An error occurred while starting the application.
AggregateException: Some services are not able to be constructed (Error while validating the service descriptor 'ServiceType: Vendr.Deploy.Composing.VendrDeployComponent Lifetime: Singleton ImplementationType: Vendr.Deploy.Composing.VendrDeployComponent': Could not load type 'Umbraco.Deploy.Core.IDiskEntityService' from assembly 'Umbraco.Deploy.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.)

Looks like IDiskEntityService has been moved from Umbraco.Deploy.Core to Umbraco.Deploy.Infrastructure.Disk.
https://our.umbraco.com/documentation/Add-ons/Umbraco-Deploy/Upgrades/version-specific#code
Umbraco.Cms 10.0.0
Umbraco.Deploy.Cloud 10.0.1
Umbraco.Deploy.Contrib 10.0.0
Vendr 2.3.1
Vendr.Deploy 2.0.1
The raw exception details:
System.AggregateException: Some services are not able to be constructed (Error while validating the service descriptor 'ServiceType: Vendr.Deploy.Composing.VendrDeployComponent Lifetime: Singleton ImplementationType: Vendr.Deploy.Composing.VendrDeployComponent': Could not load type 'Umbraco.Deploy.Core.IDiskEntityService' from assembly 'Umbraco.Deploy.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.)
     ---> System.InvalidOperationException: Error while validating the service descriptor 'ServiceType: Vendr.Deploy.Composing.VendrDeployComponent Lifetime: Singleton ImplementationType: Vendr.Deploy.Composing.VendrDeployComponent': Could not load type 'Umbraco.Deploy.Core.IDiskEntityService' from assembly 'Umbraco.Deploy.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
     ---> System.TypeLoadException: Could not load type 'Umbraco.Deploy.Core.IDiskEntityService' from assembly 'Umbraco.Deploy.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
       at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
       at System.Reflection.RuntimeConstructorInfo.<get_Signature>g__LazyCreateSignature|19_0()
       at System.Reflection.RuntimeConstructorInfo.GetParametersNoCopy()
       at System.Reflection.RuntimeConstructorInfo.GetParameters()
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.CreateConstructorCallSite(ResultCache lifetime, Type serviceType, Type implementationType, CallSiteChain callSiteChain)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.TryCreateExact(ServiceDescriptor descriptor, Type serviceType, CallSiteChain callSiteChain, Int32 slot)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.GetCallSite(ServiceDescriptor serviceDescriptor, CallSiteChain callSiteChain)
       at Microsoft.Extensions.DependencyInjection.ServiceProvider.ValidateService(ServiceDescriptor descriptor)
       --- End of inner exception stack trace ---
       at Microsoft.Extensions.DependencyInjection.ServiceProvider.ValidateService(ServiceDescriptor descriptor)
       at Microsoft.Extensions.DependencyInjection.ServiceProvider..ctor(ICollection`1 serviceDescriptors, ServiceProviderOptions options)
       --- End of inner exception stack trace ---
       at Microsoft.Extensions.DependencyInjection.ServiceProvider..ctor(ICollection`1 serviceDescriptors, ServiceProviderOptions options)
       at Microsoft.Extensions.DependencyInjection.ServiceCollectionContainerBuilderExtensions.BuildServiceProvider(IServiceCollection services, ServiceProviderOptions options)
       at Microsoft.Extensions.DependencyInjection.DefaultServiceProviderFactory.CreateServiceProvider(IServiceCollection containerBuilder)
       at Microsoft.Extensions.Hosting.Internal.ServiceFactoryAdapter`1.CreateServiceProvider(Object containerBuilder)
       at Microsoft.Extensions.Hosting.HostBuilder.CreateServiceProvider()
       at Microsoft.Extensions.Hosting.HostBuilder.Build()
       at Umbraco.Cms.Web.Common.Hosting.UmbracoHostBuilderDecorator.Build()
       at Program.Main(String[] args) in C:\Work\SolutionName\src\ProjectName\Program.cs:line 9

Well that was awefully kind of them to move the interface without deprication 🤦♂
I guess we won't be changing much for the v8/v9 builds so I'll have to release a new version compiled against v10

@MichaelNielsenDK there should be a v3 rc5 on the unstable feed shortly with it's dependencies updated. If you want to give that a try and see if it resolves things for you that would be great.


Allow test descriptions longer than 140 characters

Allow tests to have descriptions longer than 140 characters. This configures lint to ignore lines that start with 0 or more white space and then one of:

it(
describe(
unroll(
fit(
fdescribe(

Test descriptions are harder to read when they are:
it('should do something with an incredibly ' +
    'long description that has to be split among multiple lines', () => {...});

Codecov Report

Merging #534 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #534   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          54     54
  Lines        1737   1737
  Branches      262    262
=====================================
  Hits         1737   1737

Flag
Coverage Δ

#builder
100% <ø> (ø)
:arrow_up:

#runtime
100% <ø> (ø)
:arrow_up:

#srcapp
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Style

Please look over this and make sure all of my variable name changes are helping to make the code more readable. I will have one more follow up commit to fix line length, but wanted feedback so that I could add other changes while doing that.

This looks great, thanks for going to the effort of understanding my needlessly terse variable names! I completely agree with the spirit of this, and I accept that single letter variables are over used. I still like them, and I think it's quite a Pythonic thing to do, but we should probably only use single letter variables within a very limited range (say 5 lines), so one can easily look back to see how the variable is defined.
I agree with pretty much all the changes you've made though.
In general, all of this code needs a cleanup, as there is lots of shared code between the VariantSet subclasses and in other places. These are beyond the scope of this PR though I think.
Would it be possible to separate out the commits for just this PR please? It's confusing to see the commits for other PRs included.

+1 modulo nits and Jerome's comments; you're being slightly more verbose than I would, but not absurdly so.

Is this ready to merge?

Not yet, one more round of discussion and a follow-up commit are needed.
Thanks!
Kerry
On Tue, Jan 6, 2015 at 10:53 AM, skeenan<EMAIL_ADDRESS>wrote:

Is this ready to merge?
—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/server/pull/57#issuecomment-68883377.

Not to rush you, but I'm waiting on this to land before adding a new
backend for htslib VCF/BCF.
-Kevin
On Tue, Jan 6, 2015 at 11:23 AM, Kerry Donny-Clark<EMAIL_ADDRESS>
wrote:

Not yet, one more round of discussion and a follow-up commit are needed.
Thanks!
Kerry
On Tue, Jan 6, 2015 at 10:53 AM, skeenan<EMAIL_ADDRESS>wrote:

Is this ready to merge?
—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/server/pull/57#issuecomment-68883377.

—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/server/pull/57#issuecomment-68888334.

Sure, I'll try to get this wrapped up tonight/tomorrow AM.
On Tue, Jan 6, 2015 at 2:54 PM, Kevin Jacobs<EMAIL_ADDRESS>wrote:

Not to rush you, but I'm waiting on this to land before adding a new
backend for htslib VCF/BCF.
-Kevin
On Tue, Jan 6, 2015 at 11:23 AM, Kerry Donny-Clark <
<EMAIL_ADDRESS>
wrote:

Not yet, one more round of discussion and a follow-up commit are needed.
Thanks!
Kerry
On Tue, Jan 6, 2015 at 10:53 AM, skeenan<EMAIL_ADDRESS>wrote:

Is this ready to merge?
—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/server/pull/57#issuecomment-68883377.

—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/server/pull/57#issuecomment-68888334.

—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/server/pull/57#issuecomment-68923076.

I'm +1 to merge whenever @kerrydc is happy with this. (I'm not sure how much I'll be able to check in over the next few days.)

I'll also +1 this, though it looks like your changes from Flaskify are on this branch as well @kerrydc. It would be better if they were not when the merge occurs.

Sorry for the late comments here - I've only just had a chance to look through the latest version. It looks to me like there is a bug in searchVariants method of the TabixBackend --- there is no test coverage here, which is why it didn't show up.
I think we should fix this, and clear up our policy on breaking lines with \ (which to me should be done only as a last resort) before merging.

Now all comments addressed, tests pass, calls made to both backends using cli for variants-search and variantsets-search methods.

+1
On Wed, Jan 7, 2015 at 4:49 PM Kerry Donny-Clark<EMAIL_ADDRESS>wrote:

Now all comments addressed, tests pass, calls made to both backends using
cli for variants-search and variantsets-search methods.
—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/server/pull/57#issuecomment-69098357.

+1. Some print() calls have appeared in the TabixBackend class which I wouldn't like to see ordinarily, but since these classes need a fairly hefty refactoring (and the tabix backend needs quite a lot of work to get to the same point as the wormtable backend), I don't think it's worth blocking the merge now.
Since we've got two +1s on the latest changes and a lot of previous positive votes I'm merging.
Thanks again for this @kerrydc, this has been a very fruitful and positive process. I think we can iterate very quickly towards a style that we all agree on. I'll work on a cleanup for the test cases soon, which will give us another opportunity to discuss these issues.


add basic Chat Images module

Embeds images in the chat. Closable!
TODO:

[ ] Proxy.
[ ] support non-(png|jpe?g|gif) links from some major websites
[ ] Remove offscreen images (Optional, might help with large gifs?)
[ ] Scroll properly

Random Thoughts™: Can probably call plug.dj's autoscroll. Don't want to abuse plug.dj's own chat images impl, because it is sub-only, and it's not nice to use sub-only code for non-sub features.


add Schedule syntax

resolves #44
I also moved all syntax to a syntax object
/cc @ioleo

@iravid pinging you as I need more help with naming here :)

_ suffixes are (in Cats, ZIO and Haskell) used to denote a variant of a combinator that discards the results, usually resulting in an F[Unit] result rather than F[A]. This is probably not the case here.

... but unfortunately I don't have a better variant to suggest. I think that in this case too we should rename the *Env methods in ZIO and use those names here. The variants in ZIO are so painful and clunky that they would be very rarely used.

_ suffixes are (in Cats, ZIO and Haskell) used to denote a variant of a combinator that discards the results, usually resulting in an F[Unit] result rather than F[A]. This is probably not the case here.

True, that creates the wrong intuition.

_ suffixes are (in Cats, ZIO and Haskell) used to denote a variant of a combinator that discards the results, usually resulting in an F[Unit] result rather than F[A]. This is probably not the case here.

You are right, this creates the wrong intuition.

... but unfortunately I don't have a better variant to suggest. I think that in this case too we should rename the *Env methods in ZIO and use those names here. The variants in ZIO are so painful and clunky that they would be very rarely used.

We could do that.
What do you think about having names like jittered$ for our variants?

$?? Hehe that's a bit exotic for my tastes. What's your intuition for that? "jittered Apply"?

$?? Hehe that's a bit exotic for my tastes. What's your intuition for that? "jittered Apply"?

Not really, I was thinking that $ has no conventional meaning in scala as far as I'm aware and would lead to concise syntax here. Might be confusing for people that are aware of haskell though.
I'm really just bouncing ideas. If we can't come up with anything nice I propose we do the *Env naming you suggested

Let's get this merged for now and maybe iterate separately over naming


Update Dropdown component

Following the new designs, update the bitstyles Phoenix dropdown component.

Done in https://github.com/bitcrowd/bitstyles_phoenix/pull/127


Upgrade from 1.4.3 to 1.5.2 fails (PostgreSQL 10.5)

Gitea version (or commit ref): 1.4.3 / 1.5.2
Git version: 2.19.0
Operating system: Arch Linux ARM
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist: https://gist.github.com/barthalion/65736b06046acde0284b0d65883f9f64

Description
I am trying to upgrade my personal 1.4.3 instance to 1.5.2, unfortunately migrations fail as shown in the log gist above. The server runs Postgresql 10.5; I couldn't find any similar issue here (although I admit I could have missed it.)
Let me know if I can provide anything more to help with debugging.

It worked, thank you!

Is this still a problem?

Upgrade from 1.5.x to 1.6 worked fine, no idea about 1.4 → 1.6.


Fix WIDTH warnings in dmidpi module

During parsing of dmispi.sv module the following warnings are occurring:
%Warning-WIDTH: Operator ASSIGN expects 1 bits on the Assign RHS, but Assign RHS's FUNCREF 'dmidpi_create' generates 64 bits.
                        : ... In instance dmidpi
                ... Use "/* verilator lint_off WIDTH */" and lint_on around source to disable this message.
%Warning-WIDTH: Operator TASKREF 'dmidpi_close' expects 64 bits on the Function Argument, but Function Argument's VARREF 'ctx' generates 1 bits.
                        : ... In instance dmidpi
%Warning-WIDTH: Operator TASKREF 'dmidpi_tick' expects 64 bits on the Function Argument, but Function Argument's VARREF 'ctx' generates 1 bits.
                        : ... In instance dmidpi
%Warning-WIDTH: Operator TASKREF 'dmidpi_tick' expects 7 bits on the Function Argument, but Function Argument's VARREF 'dmi_req_addr' generates 1 bits.
                        : ... In instance dmidpi
%Warning-WIDTH: Operator TASKREF 'dmidpi_tick' expects 2 bits on the Function Argument, but Function Argument's VARREF 'dmi_req_op' generates 1 bits.
                        : ... In instance dmidpi
%Warning-WIDTH: Operator TASKREF 'dmidpi_tick' expects 32 bits on the Function Argument, but Function Argument's VARREF 'dmi_req_data' generates 1 bits.
                        : ... In instance dmidpi
%Warning-WIDTH: Operator TASKREF 'dmidpi_tick' expects 32 bits on the Function Argument, but Function Argument's VARREF 'dmi_rsp_data' generates 1 bits.
                        : ... In instance dmidpi
%Warning-WIDTH: Operator TASKREF 'dmidpi_tick' expects 2 bits on the Function Argument, but Function Argument's VARREF 'dmi_rsp_resp' generates 1 bits.
                        : ... In instance dmidpi

That problem also causes errors in case of output arguments ( https://github.com/alainmarcel/uhdm-integration/issues/312)

I think that it happens because sometimes Surelog change bit var type to logic net. I created the issue: https://github.com/alainmarcel/Surelog/issues/1235

It wasn't bug, but I found that ranges in module fields are not parsed: https://github.com/alainmarcel/Surelog/issues/1237

https://github.com/alainmarcel/Surelog/pull/1290 fixes the first warning.

https://github.com/antmicro/verilator/pull/246 should fix the other errors.


BadImageFormatException when running integration tests for x86 projects (runner is a x86 process)

I have a .net core 2.1.1 project that must run as an x86 process and is targeting the .net 462 framework, because it has dependencies on a few libraries targeting that framework and must run in a 32 bits process. Everything runs fine.
I have a project with the similar settings where I put integration tests. I am using the TestServer in there. I am trying to call the API methods from the main project, using the TestClient.
All of my integration tests fail as they're unable to load one of the dependent libraries, giving me a bad image format. Which usually happens when attempting to load a 32 bit library into a 64 bit process etc.
Please see below the stack trace:

Failed   Insight.MarketDataService.Host.IntegrationTests.HistoricalSpotFxRateTests.ShouldReturnNotFoundForCurrencyCodesWithoutConversions(ccFrom: "GBP", ccTo: "BAD")
Error Message:
 System.TypeInitializationException : The type initializer for 'Insight.MarketDataService.Host.IntegrationTests.TestClientFactory' threw an exception.
---- System.BadImageFormatException : Could not load file or assembly 'FSGDateTimeLibraryNative.dll' or one of its dependencies. The module was expected to contain an assembly manifest.
-------- System.BadImageFormatException : Could not load file or assembly 'FSGDateTimeLibraryNative.dll' or one of its dependencies. The module was expected tocontain an assembly manifest.
Stack Trace:
   at Insight.MarketDataService.Host.IntegrationTests.TestClientFactory.get_HttpClient()
   at Insight.MarketDataService.Host.IntegrationTests.HistoricalSpotFxRateTests.<ShouldReturnNotFoundForCurrencyCodesWithoutConversions>d__2.MoveNext() in C:\work\src\market-data-service\src\Insight.MarketDataService.Host.IntegrationTests\HistoricalSpotFxRateTests.cs:line 49
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
----- Inner Stack Trace -----
   at System.Reflection.AssemblyName.nGetFileInformation(String s)
   at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)
   at App.Metrics.Health.Extensions.DependencyInjection.Internal.HealthAssemblyDiscoveryProvider.<>c.<GetCandidateAssemblies>b__2_3(<>f__AnonymousType0`2 <>h__TransparentIdentifier0) in C:\projects\microsoftextensions\src\App.Metrics.Health.Extensions.DependencyInjection\Internal\HealthAssemblyDiscoveryProvider.cs:line 41
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at App.Metrics.Health.Extensions.DependencyInjection.Internal.HealthAssemblyDiscoveryProvider.GetCandidateAssemblies(DependencyContext dependencyContext) inC:\projects\microsoftextensions\src\App.Metrics.Health.Extensions.DependencyInjection\Internal\HealthAssemblyDiscoveryProvider.cs:line 38
   at Microsoft.AspNetCore.Hosting.HealthAspNetWebHostBuilderExtensions.<>c__DisplayClass5_0.<ConfigureHealth>b__0(WebHostBuilderContext context, IServiceCollection services) in C:\projects\aspnetcorehealth\src\App.Metrics.AspNetCore.Health.Hosting\HealthAspNetWebHostBuilderExtensions.cs:line 111
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors)
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
   at Microsoft.AspNetCore.TestHost.TestServer..ctor(IWebHostBuilder builder, IFeatureCollection featureCollection)
   at Microsoft.AspNetCore.TestHost.TestServer..ctor(IWebHostBuilder builder)
   at Insight.MarketDataService.Host.IntegrationTests.TestClientFactory..cctor() in C:\work\src\market-data-service\src\Insight.MarketDataService.Host.IntegrationTests\TestClientFactory.cs:line 17
----- Inner Stack Trace -----

I have used process monitor to check that all of the processes spun up by running tests are 32 bits and they are.
I have tried different ways of starting the tests, using the xunit.console.x86.exe, the Visual Studio test runner with .runsettings etc. Process Monitor claims things run as 32 bits processes so there must be something else going on?
Things run fine in the main project where I am not using TestServer.

Even further info, the dll in question:
---- System.BadImageFormatException : Could not load file or assembly 'FSGDateTimeLibraryNative.dll' or one of its dependencies. The module was expected to contain an assembly manifest.

uses some C++ code.
I have tried to look at the fuslogvw output but there's nothing for this one in particular (I get entries for almost everything else), so not sure what to do about the assembly manifest. Any pointers?

@luminescent what package does FSGDateTimeLibraryNative.dl come from? Could you check that package to see if it has 32-bit versions of the whatever native binaries it has?

Yes that is a 32 bit library. All runs fine as an ASP. NET Core self hosted
process (32 bits again), it is only when using the TestServer that it's
tripping.
I don't think this is related to the bitness, as I said I have looked at
this with Process Monitor and all of the processes spun up during
standalone run and integration test run are 32 bit.
On Fri, 1 Mar 2019, 16:51 Murat Girgin<EMAIL_ADDRESS>wrote:

@luminescent https://github.com/luminescent what package does
FSGDateTimeLibraryNative.dl come from? Could you check that package to
see if it has 32-bit versions of the whatever native binaries it has?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/AspNetCore/issues/8068#issuecomment-468731946,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJljmLsPZPN8AepB7BLxCgBjIInPCn2ks5vSVqYgaJpZM4bYuSa
.


Fix typo in docs

Description
Fix documentation typo. I could not get FerretDB to connect to the Postgres server, the fix was what I changed in the docs.

Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration/compatibility tests.
[ ] I added/updated comments and checked rendering.
[ ] I made spot refactorings.
[x] I updated user documentation.
[ ] I ran task all, and it passed.
[ ] I ensured that PR title is good enough for the changelog.
[ ] (for maintainers only) I set Reviewers (@FerretDB/core), Assignee, Labels, Project and project's Sprint fields.
[ ] I marked all done items in this checklist.

 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.


🐛 fix(bottom-navigation): Bottom navigation respects the iOS safe-area

Currently, the bottom navigation does not respects the iOS safari safe area. Implemented from: https://webkit.org/blog/7929/designing-websites-for-iphone-x/

Thank you!


User manual

Pull the documentation from the nickel repo (from the manual directory) and automatically render it in a dedicated page.

Closed by #44


dp_aux_messages.v

line227 ~line285
Bit 4:3 = PRE-EMPHASIS_SET,your code set Bit 5:4 = PRE-EMPHASIS_SET

Hi! Sorry about the bugs you are finding.
I don't have easy access to my test setup any more, but if you send me a pull request I'll merge them in.
Thanks
Mike

OKay  I will learn how to pull request O(∩_∩)O

OKay  I will learn how to pull request O(∩_∩)O

OKay  I will learn how to pull request O(∩_∩)O


Fix fast array array hole initialization

This patch eliminates the valgrind error: "Conditional jump or move depends on uninitialised value(s)".
JerryScript-DCO-1.0-Signed-off-by: Robert Fancsik<EMAIL_ADDRESS>

The CI passed but the check status is still pending (probably a glitch).


changed node-sass version

tests pass

^3.4.2 includes 3.10.1
https://github.com/npm/node-semver#caret-ranges-123-025-004

But the last release is only 2.3.2 how can I get 3.4.2?

Please forgive me!


cycle/dom stream library specific typings

As discussed in point (4) of #307 regarding Typescript typings, @cycle/dom's (RC) DOMSource.events() returns any. This is done intentionally, as cycle's future is to be stream library agnostic, i.e. it should be able to be used with xstream, RxJS, most, etc.
However from an application developer's point of view, DOMSource.events() would ideally return the type appropriate to the stream library (in xstream's case Stream<Event>), as this will help with compile time and edit time error checking and intellisense.
This issue is not specific to @cycle/dom. Any cyclejs driver which is stream library agnostic would have a similar problem. Solving this issue for @cycle/dom would set a common approach for all cyclejs drivers.
On approach would be to create a set of typings specific to each stream library. For example, for @cycle/dom, I have a simplified set of typings in my application's custom-typings directory:
import { IDOMSource, EventsFnOptions } from '@cycle/dom';
import { Stream } from 'xstream';

declare module '@cycle/dom' {
    export class DOMSource {
        select(selector: string): DOMSource;
        events(eventType: string, options?: EventsFnOptions): Stream<Event>;
    }
}

This issue is to discuss the best and most convenient options for solving this typings issue for cyclejs drivers.

@wmaurer You should be able to just use type casting, no?
import {Stream} from 'xstream'
...
const click$: Stream<Event> = <Stream<Event>> sources.DOM.select('.foo').events('click')

Of course ;-)
But the point is that becomes rather tiresome when one has to do it repetitively. My goal is to not have such untyped return values. Correct typings help with intellisense, code navigation and API exploration. I rarely have to use casts if the typings are good.
I have a solution that works for me. I'd like to see other Typescript / cyclejs profit from it or ideally from a better solution.

We can't seem to find how to automagically make DOMSource know which stream library type it is returning via events(). That would be the ideal case, but he are hitting the limits of TypeScript. So which of these two options seems the least worst?
(1) DOMSource is a generic and you need to tell what are the types it returns when calling events() and elements: DOMSource<Stream<Event>, Stream<Element>>. This would need to be typed anywhere we have a function that expects a DOMSource.
(2) A custom typings file similar to what you made, but it would have to be imported separately and included via typings for instance. After that, everything works automagically.

Would option 1 allow for type conversions but option 2 not?

What exactly do you mean by type conversions?

My initial reaction was (1) in order to avoid the cycle community having to maintain many typings files.
However the more I think about it, the more I think (1) could end up being a nightmare.
The fact is that this is not a @cycle/dom specific problem. It will be a problem for Typescript users for all cyclejs drivers. Imagine we had a driver which makes an XYZSource available, which has many methods returning many different stream types. Then it would be XYZSource<<Stream<A>, Stream<B>, Stream<C>, ... etc >. Having to repeat this throughout the application would be very tiresome.
Therefore I think that (2) is the least worst option.

Erhm, I think I misread your proposal. Let me try to re-formulate. Option 1 lets us directly specify the return types, whereas option 2 doesn’t (except from a typings file). Thus, option 1 would, in theory, allow for different DOMSource return types across an app (though that may possibly never be needed in an app).

@Frikki you can always cast, as an escape hatch, but casting is too verbose in a large project.
@wmaurer I'm starting to agree with you here that (2) is the least worst. The API for Cycle DOM's DOMSource shouldn't actually change much anymore.

Currently I'd favor (1) any time as I don't like to manage additional typings with tsd or typings or other tools. However this may change in TypeScript 2.0. You'll probably manage additional typings with npm and TypeScript alone (see this comment). Maybe we should wait for TS 2.0 to make a decision?

@donaldpipowitch I'm not sure how I understand how Typescript 2.0's method of managing typings will solve this problem.
As I see it Typescript 2.0's method of managing typings will simply change where typings are hosted (npm), instead of via typings/github.
The core problem of @cycle/dom being stream-library independent, and thus needing additional typings does not change. With Typescript 2.0, the additional typings will simply be differently managed.

Funny that most votes went for (1), because I started feeling like (2) will be nicer. Curious if anyone has strong opinions for (1)? Using typings is IMHO quite easy, specially if we have good docs around that, e.g. "if you want xstream-specific type defs for Cycle DOM, do this and that". Not importing those typings is still an option, then people need to cast.

I found a third option, and quite a decent one:
(3) DOMSource will be anyway an interface. We can separately import the type defs for DOMSource + stream library, for instance:
import {div, span, makeDOMDriver} from '@cycle/dom';
import {DOMSource} from '@cycle/dom/xstream-typings';

No need for managing/installing the typings, and no verbose generic interface. How does that sound?

@donaldpipowitch I'm not sure how I understand how Typescript 2.0's method of managing typings will solve this problem.

For me it is a nicer DX and DX is important for me. I personally don't want (2) because of the way tsd and typings work (IMHO they are not so easy to use 😄).
(3) is okay.
Another opinion for (1): I guess it is more idiomatic? DOMSource<Stream<Event>, Stream<Element>> is very similar how we handle things like Promise<Foo> in TypeScript, right?

I dont use Typescript at all,  so take  my 2c with a grain of salt :)
While typing is nice, by now i have gotten used to plain JS with ES6, and a lot of typing of type checks can also be done in JS without the need for another transpailer.
Having TrueType as in integral part of a lib ,might reduce the number of potential contributors , when compared to ES 6

Having TrueType as in integral part of a lib ,might reduce the number of potential contributors , when compared to ES 6

TrueType? You mean TypeScript, right? Cycle already uses TypeScript internally so it isn't a question about "Should Cycle use TypeScript internally or not" in this issue.
"plain JS with ES6" is nice. I guess you use Babel? Well, TypeScript is basically "plain JS with ES6 and types". It can be learned in some hours (if not minutes). If you willing to use the build step necessary for Babel it is basically the same investment for TypeScript. You should try it once :)

@staltz thanks, I think (3) is very sensible and will work in this case
There is the possibility that it could cause problems in other cases, i.e. if a function (fn) you import from @cycle/dom were to return a DOMSource, then in the client app, Typescript will not use the DOMSource from xstream-typings, it will use the DOMSource from @cycle/dom. This would be solved by also redefining fn in xstream-typings and importing from there. This could be a source of confusion for users if they import fn from the wrong place, but that can be solved by good guidance and documentation.
As far as DX is concerned, I think this option (3) is the best, as typings is the pretty much standard way of managing definitions right now, and if Typescript 2.0 provides another mechanism, then the xstream-typings approach is still valid, the source of the type definitions simply changes.

Yeah, spot on. The only case for fn so far is mockDOMSource. makeDOMDriver and makeHTMLDriver are not affected because the drivers are called internally in Cycle.run, so writing main(sources: {DOM: DOMSource}) simply means "the main expects this".

I believe this issue is now solved with
    "@cycle/dom": "10.0.0-rc30",
    "@cycle/http": "9.0.0-rc8",

Check out these examples:

Thanks @staltz, this works well for me.
BTW, if anybody is using webpack, for some reason at the time of writing, awesome-typescript-loader doesn't seem to want to find @cycle/dom/xstream-typings, but ts-loader does. I'm unable to track down the reason right now, but this info might save you some time.

@wmaurer You could try putting .d.ts after xstream-typings


Finish GridArray migration

GridArray is now a special case of Vol. Stop using the GridArray type alias, or come up with a rule for when we should still be using it.

Completed in c5faf070fe9611bf8db0ef44672e655d52a8bcb5.


Why remove container command is not defined

$ docker ps -a
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                           PORTS               NAMES
96bbfe60adc9        dd64161e9554        "/bin/sh -c '/usr/bin"   2 hours ago         Exited (137) About an hour ago                       96bbfe60adc9_dockerapp_mysql_1
$ docker rm 96bbfe60adc9
flag provided but not defined: -i
See 'docker rm --help'.
$ docker rm --help
flag provided but not defined: -i
See 'docker rm --help'.
docker version
Client:
Version:      1.11.1
API version:  1.23
Go version:   go1.5.4
Git commit:   5604cbe
Built:        Tue Apr 26 23:11:07 2016
OS/Arch:      linux/amd64
Server:
Version:      1.11.1
API version:  1.23
Go version:   go1.5.4
Git commit:   5604cbe
Built:        Tue Apr 26 23:11:07 2016
OS/Arch:      linux/amd64

Sounds like you have an alias or something wrapping your docker command.
Can you provide the output of command -V docker?

yes, looks like environment related

I'll go ahead and close this, because this doesn't look like a bug in docker, but feel free to continue the discussion

Only supported -v, not support  -V
$git:(master*) docker -V
flag provided but not defined: -V
See 'docker --help'.
$git:(master*) docker -v
Docker version 1.11.1, build 5604cbe

Not docker -V, command -V docker

May be  zsh can't support this,  but bash is ok

Untill today,  docker version 1.12.3, it can't support zsh. :)  so this problem still exists.

@penhauer-xiao docker works perfectly with zsh, but as @phemmer tried to explain above, it looks like there's an alias installed on your system. What is the output of command -V docker on your system? It should show something like;
command -V docker

docker is /usr/local/bin/docker

@thaJeztah  Oh, Not docker -V,  like docker -v is ok;   but this issue is still exists, as following is my trace info:
$ docker -v
Docker version 1.12.3, build 6b644ec
$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                    NAMES
5afb994baf78        anwar/redis:1.1     "/bin/sh -c 'supervis"   21 hours ago        Up About an hour    <IP_ADDRESS>:4379->6379/tcp   redis
$ docker rm 5afb994baf78
unknown shorthand flag: 'i' in -i
See 'docker rm --help'.
$ docker rm --help
unknown shorthand flag: 'i' in -i
See 'docker rm --help'.

So, it looks like there's an alias set for docker rm, so each time you run docker rm, an alias that does (e.g.) docker rm -i is executed instead.
http://zsh.sourceforge.net/Intro/intro_8.html

@thaJeztah
I couldn't  config alias of docker,   My zsh config as following:
export UPDATE_ZSH_DAYS=30
Path to your oh-my-zsh configuration.
ZSH=$HOME/.oh-my-zsh
export ZSH=$HOME/.oh-my-zsh
Set name of the theme to load.
Look in ~/.oh-my-zsh/themes/
Optionally, if you set this to "random", it'll load a random theme each
time that oh-my-zsh is loaded.
export ZSH_THEME="xiong-chiamiov-plus"
export ZSH_THEME="anwar"
Set to this to use case-sensitive completion
CASE_SENSITIVE="true"
Comment this out to disable weekly auto-update checks
DISABLE_AUTO_UPDATE="true"
Uncomment following line if you want to disable colors in ls
DISABLE_LS_COLORS="true"
Uncomment following line if you want to disable autosetting terminal title.
DISABLE_AUTO_TITLE="true"
Uncomment following line if you want disable red dots displayed while waiting for completion
DISABLE_COMPLETION_WAITING_DOTS="true"
Which plugins would you like to load? (plugins can be found in ~/.oh-my-zsh/plugins/*)
Example format: plugins=(rails git textmate ruby lighthouse)
plugins=(git autojump sudo last-working-dir docker docker-compose encode64 urltools  extract)
source $ZSH/oh-my-zsh.sh
Customize to your needs...
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
#***********************************
export GOROOT="/mnt/shared/go"
export GOARCH="amd64"
export GOOS="linux"
export GOBIN="$GOROOT/bin"
export GOTOOLS=$GOROOT/pkg/tool/linux_amd64
export GOPATH="/mnt/shared/go-T"
export GOPKGBIN="$GOPATH/bin"
export PATH=$GOBIN:$GOPKGBIN:$GOTOOLS:$PATH
#***********************************
setopt INC_APPEND_HISTORY SHARE_HISTORY
setopt APPEND_HISTORY	# If this is set, zsh sessions will append their history list to the history file, rather than overwrite it.
unsetopt BG_NICE 			# Run all background jobs at a lower priority. This option is set by default.
setopt MENUCOMPLETE   # Very good to select option for commands,etc. ls -
Set/unset  shell options
setopt   autoresume histignoredups pushdsilent
setopt   autopushd pushdminus extendedglob rcquotes mailwarning
unsetopt bgnice autoparamslash
Autoload zsh modules when they are referenced
zmodload -a zsh/stat stat
zmodload -a zsh/zpty zpty
zmodload -a zsh/zprof zprof
zmodload -ap zsh/mapfile mapfile
alias ll='ls -l --color=auto'
alias ls='ls --color=auto'
alias lla='ls -al --color=auto'
alias f=finger
alias -g cp='cp -i'
alias -g mv='mv -i'
alias -g rm='rm -i'
alias -g grep='grep --color=auto'
alias -g tmc='source $ZSH/themes/simple.zsh-theme'
alias -g tmn='tmux new -d -s'
alias -g tml='tmux ls'
alias -g tma='tmux attach -t'
alias -g tmk='tmux kill-session -t'
alias -g rtm='retmux '
alias -g py='bpython'
alias -g uterm='/usr/bin/rxvt-unicode'
alias -g mterm='/usr/local/bin/mlterm'
alias man="pinfo -m"
alias -g gt='gnome-terminal'
alias -g pcz='proxychains'
#alias go=colorgo
sudo-command-line() {
[[ -z $BUFFER ]] && zle up-history
[[ $BUFFER != sudo\ * ]] && BUFFER="sudo $BUFFER"
zle end-of-line
}
zle -N sudo-command-line
bindkey "\e\e" sudo-command-line
#}}}
setopt HIST_IGNORE_DUPS
zstyle ':completion::ping:' hosts <IP_ADDRESS>{38,} www.g.cn
192.168.{1,0}.1{{7..9},}
my_accounts=(
{r00t,root}@{<IP_ADDRESS>,<IP_ADDRESS>}
<EMAIL_ADDRESS><EMAIL_ADDRESS>)
zstyle ':completion:*:my-accounts' users-hosts $my_accounts
#}}}
eval "dircolors ~/.dircolors"
ulimit -c unlimited
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

Sorry, it really is an alias problem, this line:  alias -g rm='rm -i'  affect the docker

Thanks @thaJeztah


Unit tests of SelectionBase are failing

Due to #104 previous errors in the unit tests have not been discovered.
These errors can be seen here:
https://github.com/kbabioch/python-luxtronik/actions/runs/5523604044/jobs/10074758302#step:5:1
They have been introduced with #96 and is related to the usage of @classmethods.

Fixed with #108


gzip: stdin: not in gzip format

remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Java app detected
remote: -----> Installing JDK... (downloading...)
remote: gzip: stdin: not in gzip format
remote: tar: Child returned status 1
remote: tar: Error is not recoverable: exiting now
remote:  !     Push rejected, failed to compile Java app.
remote:
remote:  !     Push failed

I follow the instructions on the readme and I get this error.

Maybe this is happening because the link to get the oracle jdk has changed


[Mirror] SetFileAttributes/SetFileTime while copying a file.

When doing a file copy in Windows Explorer on Windows 10, the function SetFileAttributes is called while the file is open. The Mirror.cs calls File.SetAttributes which fails with a FileNotFoundException due to the file being in copy. Since the file does not exist. SetFileTime is not called at all. This results in a copied file without its original attributes (e.g. read-only or hidden) and with the current time, rather than the original file creation / access / modified time. What would be the correct way to handle this?

Hi @Deathspike ,
This seems to be duplicate with https://github.com/dokan-dev/dokan-dotnet/issues/136
Is that the case ?

Possibly. But since SetFileAttributes happens earlier, SetTime is not called at all. It might be a little different.
I'll look into a PR then.


img2sixel not truncating output file

img2sixel  -o out.sxl foo.jpg
works good, then...
img2sixel -e -i  -o out.sxl foo.jpg
results in a file with the mono image followed by lots of garbage
(this makes a mono output, so smaller), but the file 'out.sxl' remains the same size, and cat'ing this file
to a terminal (or printer) results in lots of garbage at the end from the first conversion? Things work
as expected if you remove the 'out.sxl' file in between. I am not sure how this is happening, because
a casual glance at the source looked like correct use of fopen(), but an strace shows an open without
truncation. Using version 1.7.2

Can you try v1.7.3? I had received similar report at half a year ago. It fixed by 9c77782.
Can you attach the sample sixel file  'out.xsl' ?
Please tell me, what is your terminal?

rm -f out-1.sxl out-2.sxl
img2sixel -o out-1.sxl logo.jpg
ls -lh out-1.sxl
-rw------- 1 set set 60K 2017.02.25 10:25:19 pm out-1.sxl
(img looks good in mlterm)
img2sixel -e -i -o out-1.sxl logo.jpg
ls -lh out-1.sxl
-rw------- 1 set set 60K 2017.02.25 10:25:19 pm out-1.sxl
(img should be smaller, garbage follows image in mlterm)
img2sixel -e -i -o out-2.sxl logo.jpg
ls -lh out-2.sxl
-rw------- 1 set set 3.9K 2017.02.25 10:26:05 pm out-2.sxl
out-2.sxl looks as expected in mlterm
Attached (corrupt) out-1.sxl, out-2.sxl, logo.jpg in zip
Using libsixel-1.7.3
files.zip

Unfortunately, I can't reproduce it in my environment. Additional information is needed.
Can you attach the config.log created by ./configure in your build directory?

src/encoder.c.orig  2017-02-27 23:05:52.962405054 -0500
+++ src/encoder.c       2017-02-27 23:06:16.000204738 -0500
@@ -1275,7 +1275,7 @@
close(encoder->outfd);
}
encoder->outfd = open(value,

                             O_RDWR|O_CREAT,

                             O_RDWR|O_CREAT|O_TRUNC,
                             S_IREAD|S_IWRITE);
   }
   break;

img2sixel parses the option and calls encoder.c:sixel_encoder_setopt() where the
file is opened without truncation. This patch fixes the bad behaviour I see. No idea if
the encoder might actually want to seek around in an output file, or why this is how the
output file opened.
But this is the code that gets executed in my example, and fails to truncate the output file,
such that writing to the same file again with a smaller size leaves behind the original output
as garbage.
hmmm. that preview looks messed up but the patch just adds O_TRUNC to the open function
at line 1275 in src/encoder.c

@set135 Finally I can reproduce it. libsixel-1.8 includes the fix for this issue(c121c9b).


Got error of MicrosoftPassword incorrect for the new provisioned web app bot. (both creation from script and portal)

Describe the bug

create an echo bot
run provision script
deploy the bot. deployment will success.
query the bot from the azure portal, there is no response.
query it from the emulator, got an error: The bot's Microsoft App Password is incorrect.
The publish profile provisioned before works well.
I tried to create a new azure web bot in azure portal, and query it from the emulator and got the same error.

Version

Browser

[ ] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Additional context

Got this error in the webchat

Lu, thanks for reporting this. In addition to this, I got this error as well.

This is an internal only problem, by design due to compliance. Please see my email on this subject. Thanks for reporting!


Update web-sites-integrate-with-vnet.md

put in a comment about not supporting integration with a coexistence gateway

Hi @ChrisCompy, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (ccompy). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@ChrisCompy : Thanks for your contribution to the Azure documentation! The author, @ccompy, has been notified to review your proposed change.

Authors of articles need to work in the private repo, please. Could you pull this over to private and submit so that you get the required validation, staging, and Acrolinx passes --- Thx


where can I see the source code in UE4 Editor?

Hello,I have not seen the source code in UE4 Editor,where can I see the source code in UE4 Editor?

Hi @yumianhuli2, make sure you have the following active

thanks，help me a lot！

Glad it worked!


Color code file tabs by folder

VSCode Version: 1.16.0-insider

As a developer who loves the new ability to support multiple folders in a single workspace and who often has many files open from many folders, it would be nice to have a visual queue to identify which of my many open files come from which folders so I can more easily spot the files I'm interested in working on.
Acceptance criteria

For example, I'd like my AuthService folder as have a light green background, and the tabs of files opened from the AuthService folder should also be light green.
The color would ideally be set in workspace settings or user settings.
The color would ideally take a theme color or a manual hex or rgba color.  Setting transparency level (rgba) might be especially nice for this feature.

https://github.com/Microsoft/vscode/issues/31308


unable to install

atom 196
ubuntu 12.04.5
apm  0.164.0
npm  2.5.1
node 0.10.35
python 2.7.3
git <IP_ADDRESS>
npm ERR! Linux 3.14.0
npm ERR! argv "/usr/share/atom/resources/app/apm/bin/node" "/usr/share/atom/resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/home/mark/.atom/.apm/.apmrc" "--userconfig" "/home/mark/.atom/.apmrc" "install" "/tmp/d-11543-13509-13wejrl/package.tgz" "--target=0.22.0" "--arch=x64"
npm ERR! node v0.10.35
npm ERR! npm  v2.5.1
npm ERR! code ETARGET

npm ERR! notarget No compatible version found<EMAIL_ADDRESS><1.4.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.7.0","0.8.0","0.9.0","0.10.0","0.11.0","0.12.0","0.13.0","0.14.0","1.0.0","1.0.1","1.0.2"]
npm ERR! notarget

Same here on OS X

just update the new one...can you check now

Works now.

@mark-hahn ---> Looking for feedback if  you can

I'm also having trouble installing.  If I go into Atom and go to the Settings tab and search for browser-plus, I don't see anything.  Am I missing something?


Device Error while training custom dataset

InvalidArgumentError (see above for traceback): Cannot assign a device for operation 'training/Adam/gradients/filtered_detections/map/while/embedding_lookup_3_grad/Reshape_1/f_acc': Could not satisfy explicit device specification '' because the node was colocated with a group of nodes that required incompatible device '/job:localhost/replica:0/task:0/device:GPU:0'

I think I've seen this error before, I seem to remember updating tensorflow fixed this issue. Could you give that a shot? What version are you using at the moment?

@hgaiser Thanks for the reply. Anyways, just after posting the issue, I realized the combination CUDA 9, CUDNN 7, tensorflow 1.4 and tensorflow-gpu 1.8 solves it.


Change text for IDs updated via taxon change

See https://forum.inaturalist.org/t/improve-wording-of-ids-created-by-taxon-changes/3705
Currently if a user adds an ID and that ID's taxon gets updated by a taxon change, iNaturalist says "[username] suggested an ID" on the new, updated ID, eg

This isn't totally true, as the user perhaps didn't intend to ID it as that taxonomic concept. The text could be replaced with something more accurate like "iNaturalist updated [username’s] suggested ID." Or if the possessive doesn't translate well, "iNaturalist updated the suggested ID by [username]".

Would retroactively updating instances of the original namesake as part of the internal ("inaturalist updated") pipeline not resolve? It appears the majority of issue arises from pushing a new instance of ID... is there a need for retention of specimen ID history (at the single observation level) outside of crediting observations (looks like we already have a "this was changed in the system" banner)?
Sorry for contention but I see this issue goes way back, and there appears to be many angles that may re-appear in later updates (NP-Complete style problem).
Please advise,


Genesis Port calorie count doesn't advance from 1 with beta build 94

Build 93 and 94 brought in the Stages SB20 (#234) and Yesoul S3 (#259) support. Both of which transmit multiple type of data packets, different scheme than the app have seen before, but still FTMS compatible. This required a significant refactor at the core of the app: the BLE data interpretation routine. That routine consists of a custom throttling algorithm which can:

Throw away invalid / invaluable packets right away without them counting towards the rate limit
Able to wait together multiple feature type packets to merge together and form a more complete packet which communicated up-level.
There more complete packets can be still incomplete, so Stages have speed, distance and a 3rd packet which carries the rest (watts, cadence, calories). It can happen that only two of these gathered during the throttle period, in which case I'd need borrow values from last known positive values.
Similarly to the previous point I also had to split the starting value recognization code to three portions for each cumulative measurement: distance, calories, time (elapsed or moving).

Possibly this latter might cause problem with Genesis Port (#73). According to the tester the workout stuck at 1 calories for the whole workout.

Might be related to #111 ?

Attila reported that the calories work now


Defaults file ignores instance datadir

Module version: 6.3.1
Puppet version: 4.8.1
OS and version: CentOS 7.4.1708

Bug description
Init defaults files for instances seem to ignore $elasticsearch::datadir and $elasticsearch::datadir_instance_directories; specifically, they're not using the calculated $elasticsearch::instance::instance_datadir.
Perhaps this is unimportant, as path.data seems to get set correctly in elasticsearch.yml, but it's a concerning change when updating to use the latest version of the Puppet module.  I'm not certain what impact a discrepancy between DATA_DIR in the defaults file and path.data in elasticsearch.yml has.

@mrbanzai the defaults file is intended to set values for what it sounds like: defaults that get applied in the absence of other values. The module will always set path.data to the value calculated from parameters set for instances, so this default value for data directories shouldn't(?) ever be encountered, in either case. Is there a specific bug you're running into, or is this more of a general concern about how that value behaves?

It was more of a general concern, as our configs have been managed by this Puppet module since inception and this latest update (from 5.1.0 to 6.3.1) generated a delta in the defaults files for the instances.    As I mentioned, the path.data gets set correctly in the configuration so it doesn't seem to have an impact, but the delta definitely concerned us in testing.

If this behavior was desired / expected, feel free to close :)

I think for now, this is probably benign. DATA_DIR is mostly kept for consistency with the base package install so it'll be set if the path.data setting is never set, but this module sets it pretty rigidly so there's not much chance it'll ever fall through to DATA_DIR anyway. I'll close this for now, but if you do run into any problematic behavior, please feel free to raise it in the future. 👍


Remove feature/iot_pnp branch

Now that feature/iot_pnp branch has been merged into main, we should remove feature/iot_pnp branch.
We'll need to make sure customers we know of are successfully migrated before we do this.  We'll may need help from Azure SDK repo admin since the branch is locked.

Before deleting it, we should consider updating the release notes for the 1.1.0 release and update the link to the release tag (or remove it all together):
https://github.com/Azure/azure-sdk-for-c/releases/tag/1.1.0
cc @danieljurek, @weshaggard

Before deleting it, we should consider updating the release notes for the 1.1.0 release and update the link to the release tag (or remove it all together): https://github.com/Azure/azure-sdk-for-c/releases/tag/1.1.0
cc @danieljurek, @weshaggard

@danieljurek, we have removed that feature branch, so the link in the release notes now 404s. It isn't crucial, but is there any way to retroactively fix-up the release notes for the 1.1.0 release to remove the link (on GitHub at least, if not the published doxygen or release blogs)? We have shipped this feature in 1.2.0 now.
Maybe something like this:
- These will ship in a future release and will continue to be available as beta from this feature branch.
+ These will ship in a future release.

@ahsonkhan are you talking about the release notes at https://github.com/Azure/azure-sdk/pull/3723?


Node-pre-gyp dependency hard-coded to single version causing dedupe issues

Any Reason that the dependency is listed as
"node-pre-gyp": "https://github.com/mongodb-js/node-pre-gyp/archive/v0.6.5-appveyor.tar.gz"
rather than a regular version number like other packages?
I understand if it has to be a specific version, but it's causing me headaches deduping long node package paths on windows currently...

not using node-pre-gyp anymore


error connecting to pool.ntp.org

hi, trying to get this to work but everthing i have tried leaves me with this.
ezTime debug level set to INFO
Waiting for WiFi ... Querying pool.ntp.org ... ERROR: No network
connected
Waiting for time sync
Querying pool.ntp.org ... ERROR: Timeout
Querying pool.ntp.org ... ERROR: Timeout

You'll have to tell me a bit more about your setup, and how you are connecting to Wifi.
On first glance it looks like you can connect to Wifi but not reach pool.ntp.org.

hi, I am using nodeMCU as a basis and was testing this to see if I could get the time to output to a database as a timestamp, I'm connected to a wifi network but can't connect to pool.ntp.org. the time I wish to use is GMT as I live in the UK and have tried connecting to the uk.pool.ntp.org server but I get the same error

I had same issue.
I didn't have DNS server configured for my WiFi connection (I used static IP).
Maybe that's your case?

I am getting the same error, but only  about half the time:
ezTime debug level set to DEBUG
Waiting for time sync
Querying pool.ntp.org ... ERROR: Timeout
Set event (#1) to trigger on: Thursday, 01-Jan-1970 00:00:27 UTC

The other times, it connects just fine.

@callumjackson have you checked if you're connected? Can you ping ntp.pool with your computer?
      Serial.println();
      Serial.printf("Connection status: %d\n", WiFi.status());
      Serial.print("Connected to    : ");
      Serial.println(WiFi.SSID());
      Serial.print("IP address      : ");
      Serial.println(WiFi.localIP());
      Serial.print("MAC Address     : ");
      Serial.println(WiFi.macAddress());
      Serial.print("Signal strength : ");
      Serial.println(WiFi.RSSI());

It is connected in both cases:
Connection status: 3
Connected to    : CenturyLink6487
IP address      : <IP_ADDRESS>
MAC Address     : 5C:CF:7F:8B:24:39
Signal strength : -74

ezTime debug level set to DEBUG
Waiting for time sync
Querying pool.ntp.org ... ERROR: Timeout
Set event (#1) to trigger on: Thursday, 01-Jan-1970 00:00:31 UTC

Connection status: 3
Connected to    : CenturyLink6487
IP address      : <IP_ADDRESS>
MAC Address     : 5C:CF:7F:8B:24:39
Signal strength : -75

ezTime debug level set to DEBUG
Waiting for time sync
Querying pool.ntp.org ... Received data:
0: 24, 2, 9, E9,
4: 0, 0, 0, 5B,
8: 0, 0, B, AE,
12: D8, DA, FE, CA,
16: E1, 72, EF, 4E,
20: 67, 8D, 60, D7,
24: 0, 0, 0, 0,
28: 0, 0, 0, 0,
32: E1, 72, F6, EC,
36: 74, A3, AC, 73,
40: E1, 72, F6, EC,
44: 74, B1, C3, 83,
success (round trip 64 ms)
Received time: Sunday, 10-Nov-19 20:51:56.489 UTC
Set event (#1) to trigger on: Sunday, 10-Nov-2019 21:21:57 UTC
Time is in sync

Same issue here - even with the direct IP address or any other ntp server it's the same problem. Sometimes(tm) it works, but often it's not.

Maybe the timeout is too tight? Any of you on particularly slow links? (cellphone tether? Satellite?) Could you edit ezTime.h and on line 145 change the #define NTP_TIMEOUT from 1500 to 3000 ?

Maybe the timeout is too tight? Any of you on particularly slow links? (cellphone tether? Satellite?) Could you edit ezTime.h and on line 145 change the #define NTP_TIMEOUT from 1500 to 3000 ?

I did that, no change. However, I observed that when I use a locally setup NTP server it works fine. So that workaround does the trick for me.

Hmmmmm... 🤔
My code has no way of knowing what is local or not, it just sends and receives UDP packets. If it's not the round-trip time I would almost suspect something is wrong with the DNS setup, or something else is causing UDP (or all IP) to be flaky.

It might well be related to problems some people are experiencing with ESP-32s more broadly. (Such as this one, but there's many other issues.)
Can you compile with debugging info on? The underlying ESP software might then actually say things on the serial port like [E][WiFiGeneric.cpp:658] hostByName(): DNS Failed if it's a DNS problem. Or something else useful, who knows...

There does not seems to be a DNS issue.  Here is Debug info:
Waiting for time sync
Querying pool.ntp.org ... [hostByName] request IP for: pool.ntp.org
[hostByName] Host: pool.ntp.org IP: <IP_ADDRESS>

It always resolves the host name to IP address.  There seems to be myriad of IP addresses.  Some of them connect all the time, some always time out. And some connect half the time and time out the rest.
I tried to add a loop:
while (!waitForSync(6))
  {
   Serial.println("Retrying timeSync");
  }

But it does not really loops.  When it calls waitForSync() second time, it just hangs.

Hmmm. I'd have to look at the code to see why it would hang if called a second time.
pool.ntp.org indeed returns one of many IP addresses. It could be that some just barely  time out on a slow link and some don't.
 Any of you on particularly slow links? (cellphone tether? Satellite?) Could you edit ezTime.h and on line 145 change the #define NTP_TIMEOUT from 1500 to 3000 ?

For some reason many NTP servers are giving me slow responses quite often. I solved this by setting:
setServer("time.cloudflare.com");
Works incredibly well compared to good old pool.ntp.
If you are not close to one of their pool ntp servers or live in an obscure country like me then you might also get some random timeouts. :)
https://blog.cloudflare.com/secure-time/

For some reason many NTP servers are giving me slow responses quite often. I solved this by setting:
setServer("time.cloudflare.com");
Works incredibly well compared to good old pool.ntp.
If you are not close to one of their pool ntp servers or live in an obscure country like me then you might also get some random timeouts. :)
https://blog.cloudflare.com/secure-time/

This worked for me, thank you!
I was getting intermittent connection issues, now it connects immediately.

Hi!

Hi!

Hi.
I'm using ESP8266WiFi and ezTime.
With DHCP everything works fine !
When I use static IP, also with same IP address I've got from DHCP, I get timeout from pool.ntp.org
and other NTP servers with error code  :
[hostByName] request IP for: time.cloudflare.com
[hostByName] Host: time.cloudflare.com lookup error: -6!
In both cases network itself works without problems.
Any idea ?
Erik

Hi.
I'm using ESP8266WiFi and ezTime.
With DHCP everything works fine !
When I use static IP, also with same IP address I've got from DHCP, I get timeout from pool.ntp.org
and other NTP servers with error code  :
[hostByName] request IP for: time.cloudflare.com
[hostByName] Host: time.cloudflare.com lookup error: -6!
In both cases network itself works without problems.
Any idea ?
Erik

Hi.
I'm using ESP8266WiFi and ezTime.
With DHCP everything works fine !
When I use static IP, also with same IP address I've got from DHCP, I get timeout from pool.ntp.org
and other NTP servers with error code :
[hostByName] request IP for: time.cloudflare.com [hostByName] Host: time.cloudflare.com lookup error: -6!
In both cases network itself works without problems.
Any idea ?
Erik

What code are you using to set the static IP address? It seems the DNS is not being set correctly so it can't resolve an IP for that hostname.

Hi.
I'm using ESP8266WiFi and ezTime.
With DHCP everything works fine !
When I use static IP, also with same IP address I've got from DHCP, I get timeout from pool.ntp.org
and other NTP servers with error code :
[hostByName] request IP for: time.cloudflare.com [hostByName] Host: time.cloudflare.com lookup error: -6!
In both cases network itself works without problems.
Any idea ?
Erik

What code are you using to set the static IP address? It seems the DNS is not being set correctly so it can't resolve an IP for that hostname.

Hi.
I'm using ESP8266WiFi and ezTime.
With DHCP everything works fine !
When I use static IP, also with same IP address I've got from DHCP, I get timeout from pool.ntp.org
and other NTP servers with error code :
[hostByName] request IP for: time.cloudflare.com [hostByName] Host: time.cloudflare.com lookup error: -6!
In both cases network itself works without problems.
Any idea ?
Erik

What code are you using to set the static IP address? It seems the DNS is not being set correctly so it can't resolve an IP for that hostname.

Thx, Monarchit.
That was my idea too, but I don't find right procedure for DNS setting...
I tested meanwhile "WiFi.hostByName(ntpServerName, timeServer)" but without success
Erik

Try to follow the instructions on this link to set a fixed IP address and the rest of the options. The example shows:
IPAddress local_IP(192, 168, 1, 184);
IPAddress gateway(192, 168, 1, 1);

IPAddress subnet(255, 255, 0, 0);
IPAddress primaryDNS(8, 8, 8, 8);
IPAddress secondaryDNS(8, 8, 4, 4);

Based on this you can either use your router's IP address as a primary DNS or Google's public DNS listed in the example. I believe you are missing the rest of the configuration.

Hi.
I'm using ESP8266WiFi and ezTime.
With DHCP everything works fine !
When I use static IP, also with same IP address I've got from DHCP, I get timeout from pool.ntp.org
and other NTP servers with error code :
[hostByName] request IP for: time.cloudflare.com [hostByName] Host: time.cloudflare.com lookup error: -6!
In both cases network itself works without problems.
Any idea ?
Erik

What code are you using to set the static IP address? It seems the DNS is not being set correctly so it can't resolve an IP for that hostname.

Thx, Monarchit.
That was my idea too, but I don't find right procedure for DNS setting...
I tested meanwhile "WiFi.hostByName(ntpServerName, timeServer)" but without success
Erik

Try to follow the instructions on this link to set a fixed IP address and the rest of the options. The example shows:
IPAddress local_IP(192, 168, 1, 184);
IPAddress gateway(192, 168, 1, 1);

IPAddress subnet(255, 255, 0, 0);
IPAddress primaryDNS(8, 8, 8, 8);
IPAddress secondaryDNS(8, 8, 4, 4);

Based on this you can either use your router's IP address as a primary DNS or Google's public DNS listed in the example. I believe you are missing the rest of the configuration.

Hi.
I'm using ESP8266WiFi and ezTime.
With DHCP everything works fine !
When I use static IP, also with same IP address I've got from DHCP, I get timeout from pool.ntp.org
and other NTP servers with error code :
[hostByName] request IP for: time.cloudflare.com [hostByName] Host: time.cloudflare.com lookup error: -6!
In both cases network itself works without problems.
Any idea ?
Erik

What code are you using to set the static IP address? It seems the DNS is not being set correctly so it can't resolve an IP for that hostname.

Thx, Monarchit.
That was my idea too, but I don't find right procedure for DNS setting...
I tested meanwhile "WiFi.hostByName(ntpServerName, timeServer)" but without success
Erik

Try to follow the instructions on this link to set a fixed IP address and the rest of the options. The example shows:
IPAddress local_IP(192, 168, 1, 184);
IPAddress gateway(192, 168, 1, 1);

IPAddress subnet(255, 255, 0, 0);
IPAddress primaryDNS(8, 8, 8, 8);
IPAddress secondaryDNS(8, 8, 4, 4);

Based on this you can either use your router's IP address as a primary DNS or Google's public DNS listed in the example. I believe you are missing the rest of the configuration.

WOW !
I forgot to extend the config call ...
WiFi.config(ip, gateway, subnet, primaryDNS, secondaryDNS);
Not seen in any example...
Because the eztime needs a secondaryDNS I was running into another problem.
Now it works :
18:21:40.976 -> [hostByName] request IP for: pool.ntp.org
18:21:40.976 -> [hostByName] Host: pool.ntp.org IP: <IP_ADDRESS>
18:21:41.120 -> [hostByName] request IP for: timezoned.rop.nl
18:21:41.163 -> [hostByName] Host: timezoned.rop.nl IP: <IP_ADDRESS>
Thx a lot !
Erik

Hi.
I'm using ESP8266WiFi and ezTime.
With DHCP everything works fine !
When I use static IP, also with same IP address I've got from DHCP, I get timeout from pool.ntp.org
and other NTP servers with error code :
[hostByName] request IP for: time.cloudflare.com [hostByName] Host: time.cloudflare.com lookup error: -6!
In both cases network itself works without problems.
Any idea ?
Erik

What code are you using to set the static IP address? It seems the DNS is not being set correctly so it can't resolve an IP for that hostname.

Thx, Monarchit.
That was my idea too, but I don't find right procedure for DNS setting...
I tested meanwhile "WiFi.hostByName(ntpServerName, timeServer)" but without success
Erik

Try to follow the instructions on this link to set a fixed IP address and the rest of the options. The example shows:
IPAddress local_IP(192, 168, 1, 184);
IPAddress gateway(192, 168, 1, 1);

IPAddress subnet(255, 255, 0, 0);
IPAddress primaryDNS(8, 8, 8, 8);
IPAddress secondaryDNS(8, 8, 4, 4);

Based on this you can either use your router's IP address as a primary DNS or Google's public DNS listed in the example. I believe you are missing the rest of the configuration.

WOW !
I forgot to extend the config call ...
WiFi.config(ip, gateway, subnet, primaryDNS, secondaryDNS);
Not seen in any example...
Because the eztime needs a secondaryDNS I was running into another problem.
Now it works :
18:21:40.976 -> [hostByName] request IP for: pool.ntp.org
18:21:40.976 -> [hostByName] Host: pool.ntp.org IP: <IP_ADDRESS>
18:21:41.120 -> [hostByName] request IP for: timezoned.rop.nl
18:21:41.163 -> [hostByName] Host: timezoned.rop.nl IP: <IP_ADDRESS>
Thx a lot !
Erik

Hi.
I'm using ESP8266WiFi and ezTime.
With DHCP everything works fine !
When I use static IP, also with same IP address I've got from DHCP, I get timeout from pool.ntp.org
and other NTP servers with error code :
[hostByName] request IP for: time.cloudflare.com [hostByName] Host: time.cloudflare.com lookup error: -6!
In both cases network itself works without problems.
Any idea ?
Erik

What code are you using to set the static IP address? It seems the DNS is not being set correctly so it can't resolve an IP for that hostname.

Thx, Monarchit.
That was my idea too, but I don't find right procedure for DNS setting...
I tested meanwhile "WiFi.hostByName(ntpServerName, timeServer)" but without success
Erik

Try to follow the instructions on this link to set a fixed IP address and the rest of the options. The example shows:
IPAddress local_IP(192, 168, 1, 184);
IPAddress gateway(192, 168, 1, 1);

IPAddress subnet(255, 255, 0, 0);
IPAddress primaryDNS(8, 8, 8, 8);
IPAddress secondaryDNS(8, 8, 4, 4);

Based on this you can either use your router's IP address as a primary DNS or Google's public DNS listed in the example. I believe you are missing the rest of the configuration.

WOW ! I forgot to extend the config call ...
WiFi.config(ip, gateway, subnet, primaryDNS, secondaryDNS);
Not seen in any example... Because the eztime needs a secondaryDNS I was running into another problem.
Now it works : 18:21:40.976 -> [hostByName] request IP for: pool.ntp.org 18:21:40.976 -> [hostByName] Host: pool.ntp.org IP: <IP_ADDRESS> 18:21:41.120 -> [hostByName] request IP for: timezoned.rop.nl 18:21:41.163 -> [hostByName] Host: timezoned.rop.nl IP: <IP_ADDRESS>
Thx a lot !
Erik

Hi!
This solved my problem too. ezTime needs primary and secondary DNS the works fine in case when useing WiFi.Config() function. In my sketch it looks: WiFi.config(IPAddress(192, 168, 1, 130), IPAddress(192, 168, 1, 1), IPAddress(255, 255, 255, 0), IPAddress(8, 8, 8, 8), IPAddress(8, 8, 4, 4));
And after this for me started working the NTC library (NTPClient.h) as well.
G.


error handling, pep8 compliance, and unit tests

there's a lot going on here.. in some cases there are typos, or inconsistencies.. in other cases i have rewritten the exceptions handling so it is to a specific piece of code instead of the entirety of a method. the unittests are in a separate dir (although i think it's better if it's combined.. makes for easier imports)
i also tried to get the code to be pep8 compliant.
pls review first.. it's quiet a bit of work and i may have missed something
have fun!

i'm doing a full re-write of this and it has changed quiet a bit so i'll be creating a new one once i'm done.


add support for fast & small trace outputs

Today, we output JSON files.
For big traces, this is a memory and I/O bottleneck.
We'll consider adding support for fast & small trace outputs with efficient serialization such as protobuff.

We use jackson now, which is much faster at serialising and deserialising than gson. Source: https://github.com/fabienrenaud/java-json-benchmark.

cc/ @Deee92 @I-Al-Istannen


Toothpick: Mark  bluetoothBackend preference as optional.

Description
A previous extension update introduced the option to choose between AppleScript and blueutil as a backend. While there's nothing wrong with the option itself being present, we generally try to avoid adding required preferences to an already-published extension. The reasoning behind that is: it can be jarring when, as a previous user of the extension, I want to run a command, only to seemingly out-of-the-blue (I might not know the extension was updated) be asked to choose between two backends, one of them marked as experimental.
Since AppleScript was already marked as default in the manifest file, this PR updates the manifest so that bluetoothBackend is optional instead of required. Hope that's fine! 😺

As Per said, this completely makes sense. Thanks for your contribution!


set Charset for deserialize in CqlTransformFilter

set Charset for deserialize in CqlTransformFilter,as the same as cql
Signed-off-by: xxxxs<EMAIL_ADDRESS>

Thanks for fixing this, could you update the PR with just the first commit so we don't mix in the table metadata changes?

start a new PR from a other branch


Pie 'teleports' itself.

When clicking on a slice to open a subpie, the current pie vanishes and another one with the intended subpie opens on another side of the screen. Only then gnome-pie starts behaving as explained on the announcement (http://www.simonschneegans.de/?p=633).

You’re right.. I’ll look into it.

Has been fixed! Checkout the new release, 0.5.1!

Works like a charm :)


[Request] Add volume slider for Controller "effects"

I apologize if this is the wrong place to ask, but would it be possible to get a way to adjust the overall volume of the... Controller "easter egg" mode's volume?  I don't want to write anything particularly spoiler-y for those who haven't experience it.
I looked through the settings/configs and I don't see a way to tweak this, and I would appreciate a volume setting for the associated mode/sfx -- they're quite a bit louder than everything else in my version of Lethal at the moment.
(For what it's worth, this was an amazing surprise.  Fantastic work)
Thanks for the consideration

Will probably be added in 1.1.1

Is added for 1.1.1

thank you for the quick response/update
can you point me in the direction of the volume control for this?  I don't see it in the in-game menus (admittedly may have missed it) and a check of the configs didn't turn up anything
thanks again

Sorry for the confusion, I think you're referring to the general music slider?
"Added music volume slider to settings"

But I was asking for a specific way to configure the volume levels for the Controller item
   because the DOOM mode is significantly louder than anything else in my game


header: Exchange interface implements Getter

This PR changes Exchange interface to just implement Getter as they are performing the same functions just with different names.

Codecov Report

Merging #842 (02287af) into main (643749f) will decrease coverage by 0.10%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##             main     #842      +/-   ##
==========================================
- Coverage   54.00%   53.90%   -0.11%
==========================================
  Files         122      122
  Lines        6979     6979
==========================================
- Hits         3769     3762       -7
- Misses       2823     2828       +5
- Partials      387      389       +2

Impacted Files
Coverage Δ

header/local/exchange.go
68.42% <75.00%> (ø)

header/core/exchange.go
50.00% <80.00%> (ø)

header/p2p/exchange.go
62.22% <100.00%> (ø)

header/store/init.go
100.00% <100.00%> (ø)

header/sync/sync.go
65.34% <100.00%> (ø)

fraud/bad_encoding.go
40.59% <0.00%> (-2.98%)
:arrow_down:

das/daser.go
73.68% <0.00%> (-2.64%)
:arrow_down:

Continue to review full report at Codecov.

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


seccomp.json moved to @seccomp/containers-golang

Signed-off-by: Lokesh Mandvekar<EMAIL_ADDRESS>@baude @mheon @rhatdan

/assign @umohnani8

Can you elaborate on why this change is needed? I feel rather strongly against this change for a multitude of reasons:

Removing the file here will certainly break package builds of at least openSUSE and SUSE. Those packages would then be forced to add yet another source to the package just to fetch the seccomp.json.

Why do we need to rely on an github.com/containers external project for such an important config?

The two seccomp.json files are different.

Compiling libpod from scratch is becoming rediculously hard. I don't think it's user or even developer friendly to force them to fetch configs and files from 3+ projects inside and outside of github.com/containers.

If this change is really desired, I really want to know why and request to document this somewhere (and to highlight it in the changelogs for the next release).

* Removing the file here will certainly break package builds of at least openSUSE and SUSE. Those packages would then be forced to add yet another source to the package just to fetch the seccomp.json.

Ack, Fedora includes that file in the dist-git source itself. I'd really like 1 canonical location for that file, wherever that may be.

* Why do we need to rely on an github.com/containers external project for such an important config?

@rhatdan can we move @seccomp/containers-golang to @containers?

* The two seccomp.json files are different.

Ack. They're being installed to the same location so maybe we should work on making these consistent?

* Compiling libpod from scratch is becoming rediculously hard. I don't think it's user or even developer friendly to force them to fetch configs and files from 3+ projects inside and outside of github.com/containers.

Ack, see question above about moving the repo here.

If this change is really desired, I really want to know why and request to document this somewhere (and to highlight it in the changelogs for the next release).

Will do, I can add this if we decide to go ahead with this.

Is there a way to handle this via github?  Subpackages?  I agree with both of you @lsm5 and @giuseppe,

Is there a way to handle this via github? Subpackages? I agree with both of you @lsm5 and @giuseppe,

I guess you meant @vrothberg :) . How about vendoring like we did for registries.conf in skopeo?

I am still seeking for an answer to why this change is needed :^)
It's already very complex to know which packages/dependencies in which version is used/required where. The packaging efforts for Debian keep revealing more and more issues and I am worried that this change will increase the complexity.
To be fair, it's not a huge thing but I would rather go in the opposite direction and make the projects more self-contained. Especially the configs are important. Imagine the seccomp.json config has a bug. We first had to update the go-seccomp version, then revendor into the tools. How do we handle issues for stable versions where upstream keeps diverging? Do we need to patch a config in the vendor folder?  It really doesn't feel right.
I am sorry to hijack this PR, @lsm5. My concerns are more of a general nature then being specific to the proposed change.

@rhatdan @mrunalp so I see that seccomp.json is being installed to /usr/share/containers in libpod's Makefile and to /etc/crio/ in cri-o's Makefile. If those are the final locations for both, then I'm fine with closing this PR.

Well I would prefer to have them all share the same location.  I don't like the fact that CRI-O has this in a different location.  The more the configurations are shared the easier it is for an admin to manage.

Well I would prefer to have them all share the same location. I don't like the fact that CRI-O has this in a different location. The more the configurations are shared the easier it is for an admin to manage.

I don't see how this change is achieving it. libpod is already required as a package source now for containers-common (or libcontainers-common on openSUSE) because of the oci-hooks manpage and the seccomp.json. CRI-O could just use the seccomp.conf from libpod.

I'd really like to deprecate CRI-O's /etc/crio location - it should default to the same paths Podman and Buildah do, so config changes affect the whole system.
@vrothberg While I agree that this causes packaging concerns, config files like this don't really belong to any one project. In your Seccomp profile bug case, right now, we have to fix it in at least two locations (CRI-O and Podman repos). I think that's just as bad for packaging complexity.
I don't know is containers-seccomp is the best place for the config - maybe we should have a github.com/containers/configs to store the default mounts.conf, storage.conf, etc files, and then submodule that into our projects?

@vrothberg While I agree that this causes packaging concerns, config files like this don't really belong to any one project. In your Seccomp profile bug case, right now, we have to fix it in at least two locations (CRI-O and Podman repos). I think that's just as bad for packaging complexity.

The config file has been in libpod since I know it. Removing it breaks downstream packages. Currently, CRI-O ships it's own seccomp.json but there are plans to change that. Executing the current plan means work for everybody, upstream and downstream. I don't think that's necessary.

Can we move this to containers common and then vendor it into podman and cri-o.

@lsm5 Any update on this?

@lsm5 Any update on this?

I guess we gotta have everyone agree on a single seccomp.json before we can proceed with this.

Also, if we're moving to go mod on this, I don't know how that'd affect this file if it's in seccomp/containers-golang.

@vrothberg @lsm5 Where do we stand with this one?

As @lsm5 mentioned, as soon as we move to use go modules, we cannot use such files from the ./vendor directory anymore. I am okay with any solution that does not rely on ./vendor but we need to be verbose in the changelogs to avoid breaking packages for other distros.

@lsm5, can you rebase?
LGTM

Needs a rebase

Ping @lsm5

@lsm5 is this needed anymore?

@lsm5 Whats the scoop on this one?


Error while connecting to device

Hey, just giving this a shot, I'm not really sure if it's working right - seems to be having issues connecting? I pulled the latest docker image and using go-chromecast master branch:
2021-04-27T21:27:26.403933Z   INFO - castblock.chromecast: Found go-chromecast at /usr/bin/go-chromecast.
2021-04-27T21:27:26.403988Z   INFO - castblock.chromecast: Starting the go-chromecast server.
2021-04-27T21:27:29.940638Z   INFO - castblock.blocker: New device found -- name: "Omar's Chromecast Ultra", uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:27:29.940679Z   INFO - castblock.blocker: New device found -- name: "Stephen's Chromecast", uuid: "13f02e0618d0873d544b5f67730678e0"
2021-04-27T21:27:29.940780Z   INFO - castblock.chromecast: Connect to device -- uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:27:29.940929Z   INFO - castblock.chromecast: Connect to device -- uuid: "13f02e0618d0873d544b5f67730678e0"
2021-04-27T21:27:32.942727Z  ERROR - castblock.chromecast: Error while connecting to device -- uuid: "ff932669642aa7737e04e61f0070e3fa", status_code: 400, error: "'port' and 'addr' missing from query params and uuid device lookup returned no results"
2021-04-27T21:27:35.943665Z  ERROR - castblock.chromecast: Error while connecting to device -- uuid: "13f02e0618d0873d544b5f67730678e0", status_code: 400, error: "'port' and 'addr' missing from query params and uuid device lookup returned no results"
2021-04-27T21:28:02.945807Z   INFO - castblock.blocker: New device found -- name: "Stephen's Chromecast", uuid: "13f02e0618d0873d544b5f67730678e0"
2021-04-27T21:28:02.945812Z   INFO - castblock.blocker: New device found -- name: "Omar's Chromecast Ultra", uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:28:02.945939Z   INFO - castblock.chromecast: Connect to device -- uuid: "13f02e0618d0873d544b5f67730678e0"
2021-04-27T21:28:02.946075Z   INFO - castblock.chromecast: Connect to device -- uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:28:05.988120Z   INFO - castblock.chromecast: Starting go-chromecast watcher -- uuid: "13f02e0618d0873d544b5f67730678e0"
2021-04-27T21:28:08.989710Z  ERROR - castblock.chromecast: Error while connecting to device -- uuid: "ff932669642aa7737e04e61f0070e3fa", status_code: 400, error: "'port' and 'addr' missing from query params and uuid device lookup returned no results"
2021-04-27T21:28:35.947497Z   INFO - castblock.blocker: New device found -- name: "Omar's Chromecast Ultra", uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:28:35.947543Z   INFO - castblock.chromecast: Connect to device -- uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:28:39.065064Z   INFO - castblock.chromecast: Starting go-chromecast watcher -- uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:29:08.949026Z   INFO - castblock.blocker: A device is gone -- name: "Omar's Chromecast Ultra", uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:29:41.949551Z   INFO - castblock.blocker: New device found -- name: "Omar's Chromecast Ultra", uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:29:41.949594Z   INFO - castblock.chromecast: Connect to device -- uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:29:41.949944Z   INFO - castblock.chromecast: Starting go-chromecast watcher -- uuid: "ff932669642aa7737e04e61f0070e3fa"
2021-04-27T21:30:47.953607Z   INFO - castblock.blocker: A device is gone -- name: "Stephen's Chromecast", uuid: "13f02e0618d0873d544b5f67730678e0"
2021-04-27T21:31:53.960576Z   INFO - castblock.blocker: New device found -- name: "Stephen's Chromecast", uuid: "13f02e0618d0873d544b5f67730678e0"
2021-04-27T21:31:53.960627Z   INFO - castblock.chromecast: Connect to device -- uuid: "13f02e0618d0873d544b5f67730678e0"
2021-04-27T21:31:53.961066Z   INFO - castblock.chromecast: Starting go-chromecast watcher -- uuid: "13f02e0618d0873d544b5f67730678e0"

I currently have something playing on Omars chromecast - I glanced through the code and it seems like it should print out something about the playing video?

Wait just kidding, I think my go-chromecast was out of date

great to see you fixed it :)
I should maybe check for the go-chromecast version :thinking:


Tritium does not produce power

Description
Despite being a radioactive gas, tritium will not interact with radiation collectors to make power
Reproduction
Step 1: fill room with trit
Step 2: Place power monitoring console, SMES and radiation collecor
Step 3: open power monitoring UI
Screenshots

Additional note
This also seem to hold true for radiation artifacts
apparently artifacts do produce power, but doesn't show on the power monitoring console

This would be an interesting feature. I see a possibility for a map, where engineers will cooperate with atmos to produce power.

Tritium gas is only weakly radiative, it could be handwaved that it isn't strong enough to power the radiation collectors on its own

This would honestly be super cool to see


Display it to Webserver

i tried using this library and display it to website. But i dont know which one from the script that make summon the QR Code.
Can you help me ?
If i cant put it to website, can you give me an explain how to make the QR Code save to Micro SD as BMP / PNG
Thank you

Did you found any solution?


Change directionality of node connections

Fixes #1 based on The Mikado Method text.

This doesn't appear to be working as of d678c45. Specifically:
MikadoGraph::Generator.define do
  state("State A").with_prerequisites do
    state("State B").with_prerequisites do
      state("State D")
      state("State E")
    end
    state("State C").with_prerequisites do
      state("State F")
      state("State G")
    end
  end
end.generate format: 'png', path: 'foo.png'

still results in:

and acking the code base didn't turn up any obvious keywords for specifying the leaf-to-node flow. Am I missing something non-obvious, or is this a bug?

Hey @CodeGnome. I'm seeing the generated image that you pasted as correct. Maybe its a caching issue on your end? Here is what I see:

Can I also see what version of the gem you have installed? This is how I checked mine through my terminal by launching irb:
2.4.0 :001 > require 'mikado_graph'
 => true
2.4.0 :002 > MikadoGraph::VERSION
 => "0.4.0"
2.4.0 :003 >

0.4.0 has the fix


Virtual Chassis and Search filter (Rack group,...)

Issue type
[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

Python version: 2.xx
NetBox version: 2.3.1

Description
Poor Search filter in Virtual Chassis section.
No Rack group, no Manufacturer, ...

Thank you for your interest in NetBox. It looks like your feature request is missing some information. Per the contributing guidelines, please ensure that you have provided all of the following:

A detailed description of the proposed functionality
A use case for the feature; who would use it and what value it would add to NetBox
A rough description of changes necessary to the database schema (if applicable)
Any third-party libraries or other resources which would be involved

Please update the issue so that it meets all of  these requirements. If no response is received within a week, this issue will be closed. Thanks!

No Rack group, no Manufacturer.

And one more thing.
I do global search, got list needed devices but can not select them to create Virtual Chassis


Adds task to create user custom fields

Closes #137
N.B. the POST to /configurations/entries will be done in the step rake load_all_configurations. The value USERS needs to be added to all config/settings yaml files.
Also, there is not a schema to validate against so the test just checks the number of custom fields in the json. 🤷
Also also, see the issue comment about the PUT taking a long time but it did eventually complete.

Oh, I forgot to add the special header.