Initial VCPkg integration

This change introduces the VCPkg builder integrating the vcpkg system (http://vcpkg.io) for acquiring and building 3rd party C/C++ libraries. This enables an SConstruct file to say, for example, "env.VCPkg('openjpeg')", and then vcpkg will handle downloading the source code and building it. The VCPkg() builder further ensures that the vcpkg include directory gets added to CPPPATH, and that its static lib directory gets added to LIBPATH.
One notable quirk of the VCPkg builder is that it does the actual package build during the initial execution of the SConstruct file, rather than occurring later, during SCons's normal build phase. While undesirable, this ensures that the VCPkg builder is able to accurately compute the set of files produced by building the package (as of this writing, vcpkg does not support any means to predict the files generated by building a package). I hope to improve this in the future.
Contributor Checklist:

[X] I have created a new test or updated the unit tests to cover the new/changed functionality.
[X] I have updated CHANGES.txt (and read the README.rst)
[X] I have updated the appropriate documentation

Adding a reference to #4101 for tracking purposes.

@mwichmann @bdbaddog what are the expectations regarding code coverage? If I'm reading this correctly, my unit tests only exercise 41% of the lines of code. There are certainly more tests that could be written (I've left a TODO in the test file listing scenarios that I think would be reasonable to test), but 100% code coverage is not feasible.

@mwichmann @bdbaddog what are the expectations regarding code coverage? If I'm reading this correctly, my unit tests only exercise 41% of the lines of code. There are certainly more tests that could be written (I've left a TODO in the test file listing scenarios that I think would be reasonable to test), but 100% code coverage is not feasible.

We don't have hard requirements on code coverage.  That said if you can reasonable add more tests to cover the major code branches, please do.

Probably worth addressing all the side complaints.

Sigh.  The doc build failure is one I started to run into as well.  I was able to stave it off by backing out an example - that was the thing that triggered it, but there was nothing wrong with my snippets, it just someone was one piece too much for lxml (see #4235). In other words, it's going to be tricky to figure out what's going wrong here and in that PR.

Bummer. Also, on a related note, I noticed that the SconsDoc stuff tries to load lxml, and if that fails, tries to fall back to a different implementation, but that implementation apparently doesn't support XSD schema validation? In any case, it falls down pretty hard, with no clue on how to fix it. I finally figured out I needed to "pip install lxml". IMO, we should rip out the fallback XML parser and instead have a friendly failure message to the person running SconsDoc that they need to install lxml. I'll log an issue on this.

Bummer. Also, on a related note, I noticed that the SconsDoc stuff tries to load lxml, and if that fails, tries to fall back to a different implementation, but that implementation apparently doesn't support XSD schema validation? In any case, it falls down pretty hard, with no clue on how to fix it. I finally figured out I needed to "pip install lxml". IMO, we should rip out the fallback XML parser and instead have a friendly failure message to the person running SconsDoc that they need to install lxml. I'll log an issue on this.

The "new issue" text tells me to raise this on Discord or the mailing list first. Should I log this issue?

Bummer. Also, on a related note, I noticed that the SconsDoc stuff tries to load lxml, and if that fails, tries to fall back to a different implementation, but that implementation apparently doesn't support XSD schema validation? In any case, it falls down pretty hard, with no clue on how to fix it. I finally figured out I needed to "pip install lxml". IMO, we should rip out the fallback XML parser and instead have a friendly failure message to the person running SconsDoc that they need to install lxml. I'll log an issue on this.

The "new issue" text tells me to raise this on Discord or the mailing list first. Should I log this issue?

Please bring it to the users mailing list or the discord server.. :)

So, yes, there was a transitional phase... lxml was the "second choice" in the Python 2 days, but the other approach hasn't been supported for a while, and doesn't wotk on Py3.  Not everything relating to "the old days" has been ripped out completely, just because... we're (somewhat) human, I guess.  There's a script to set up for development (bin/scons_dev_master.py) which is documented somewhere, and which also has an error in it, so it will blow up after installing the deps - just found that the other day.  Meanwhile, in the current source tree (not in any released version) there are now three requirements files: the base one for running scons, requirements-dev.txt which adds the stuff you need basically to run the full test suite, and requirements-pkg.txt, which is "everything" - basically adding the stuff needed to build the docs.  lxml is in the requirements-dev.txt since it's used by some of the docbook and xml tests.

Oh - and scons_dev_master is only set up for Debian-ish systems.

Hmmm...so maybe add this to an "else if posix" clause at the end of the "if hpux...else if aix...else if darwin..." structure?
Sent from ProtonMail mobile
-------- Original Message --------
On Sep 18, 2022, 9:19 AM, Mats Wichmann wrote:

@mwichmann commented on this pull request.

In SCons/Tool/init.py:

@@ -809,6 +809,8 @@ def tool_list(platform, env):
'tar', 'zip',
# File builders (text)
'textfile',

   # Package management

   'vcpkg',

Ummm...how do I detect "linux"? It seems like tools such as m4 and rpm are being added simply based on "not win32". Is there a positive test I can do to detect a linux system?

Eh, that's a little complex. Depending on where you're asking... a simple way is to check sys.platform for linux. However, the name of the Platform module is actually posix, which is shared with some of the other choices (that originally comes from the value of os.name).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Sigh. The doc build failure is one I started to run into as well. I was able to stave it off by backing out an example - that was the thing that triggered it, but there was nothing wrong with my snippets, it just someone was one piece too much for lxml (see #4235). In other words, it's going to be tricky to figure out what's going wrong here and in that PR.

Hi @mwichmann . I'm finally getting back to this project. Since the doc generation is blocking the PR, I think I might take a stab at fixing that problem. Have you done any investigation on this issue yet? My suspicion is that this might be an out-of-memory issue, either in Python or in FOP (a Java tool, IIRC). I'm wondering if it might be as simple as allocating more "max" heap memory to the JVM that runs FOP. Also, have you been able to get a local repro for this issue? I tried to repro it myself on my Ubuntu WSL virtual machine back in October, but as I recall, I was not able to hit this, at least not on the few attempts I've made.

The doc build part appears to be a built-in limit that turns out to now be tunable thanks to someone's efforts about six months ago.  I bumped the limit again for #4263, as those changes pushed me into the "trouble" area, but that has not been merged yet.  Whether it triggers does seem to be situational.  In any case, if you want, you can try the same bit:
diff --git a/SCons/Tool/docbook/__init__.py b/SCons/Tool/docbook/__init__.py
index 5cf5e6198..52e291144 100644
--- a/SCons/Tool/docbook/__init__.py
+++ b/SCons/Tool/docbook/__init__.py
@@ -69,7 +69,7 @@ re_refname = re.compile(r"<refname>([^<]*)</refname>")
 # lxml etree XSLT global max traversal depth
 #

-lmxl_xslt_global_max_depth = 3100
+lmxl_xslt_global_max_depth = 3600

 if has_lxml and lmxl_xslt_global_max_depth:
     def __lxml_xslt_set_global_max_depth(max_depth):

Bummer. Also, on a related note, I noticed that the SconsDoc stuff tries to load lxml, and if that fails, tries to fall back to a different implementation, but that implementation apparently doesn't support XSD schema validation? In any case, it falls down pretty hard, with no clue on how to fix it. I finally figured out I needed to "pip install lxml". IMO, we should rip out the fallback XML parser and instead have a friendly failure message to the person running SconsDoc that they need to install lxml. I'll log an issue on this.

FWIW, there's now a straightforward way to get all the deps in place if you intend to "build scons", which includes building the doc set:
pip install -r requirements-pkg.txt

The doc build part appears to be a built-in limit that turns out to now be tunable thanks to someone's efforts about six months ago. I bumped the limit again for #4263, as those changes pushed me into the "trouble" area, but that has not been merged yet. Whether it triggers does seem to be situational. In any case, if you want, you can try the same bit:
diff --git a/SCons/Tool/docbook/__init__.py b/SCons/Tool/docbook/__init__.py
index 5cf5e6198..52e291144 100644
--- a/SCons/Tool/docbook/__init__.py
+++ b/SCons/Tool/docbook/__init__.py
@@ -69,7 +69,7 @@ re_refname = re.compile(r"<refname>([^<]*)</refname>")
 # lxml etree XSLT global max traversal depth
 #

-lmxl_xslt_global_max_depth = 3100
+lmxl_xslt_global_max_depth = 3600

 if has_lxml and lmxl_xslt_global_max_depth:
     def __lxml_xslt_set_global_max_depth(max_depth):

OK! I've added this change (I upped it to 4000 for good measure, and that seems to have fixed the issue for me. Thank you!

@jediry - Sorry for the delay. Finally got a big chunk of time to review this and read up on vcpkg and (hopefully) better understand.
Let me ask you a fundamental question about the goal of this functionality.
Is it really:

Check and see if this package is already installed, and if not install it and configure scons to be able to use it's libraries and header files (and binaries)?
Build this package as part of my build?

I'm thinking it's really #1?

I'm thinking it's really #1?

Correct. Though, if the specified package is not currently installed, its binaries will be built as part of the install process, so #2 kind of applies as well.


Jitter between markers?

I am wondering how can I change the jitter / space between marker? Or how can I make the un-clustered markers leg longer because my markers are kind of big and it is still overlapping on each other after un-clustering.

You may want to look at this:var PruneClusterLeafletSpiderfier = (L.Layer ? L.Layer : L.Class).extend({    _2PI: Math.PI * 2,    _circleFootSeparation: 25,    _circleStartAngle: Math.PI / 6,    _spiralFootSeparation: 28,    _spiralLengthStart: 11,    _spiralLengthFactor: 5,    _spiralCountTrigger: 8,    spiderfyDistanceMultiplier: 1,    initialize: function (cluster) {        this._cluster = cluster;        this._currentMarkers = [];        this._multiLines = !!L.multiPolyline;        this._lines = this._multiLines ?            L.multiPolyline([], { weight: 1.5, color: '#222' }) :            L.polyline([], { weight: 1.5, color: '#222' });    }Increase spiderfyDistanceMultiplier: to 2 or more and you will see the different.-------- Originalnachricht --------Betreff: [SINTEF-9012/PruneCluster] Jitter between markers? (#166)Von: tenznhok An: SINTEF-9012/PruneCluster Cc: Subscribed I am wondering how can I change the jitter / space between marker? Or how can I make the un-clustered markers leg longer because my markers are kind of big and it is still overlapping on each other after un-clustering.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/SINTEF-9012/PruneCluster","title":"SINTEF-9012/PruneCluster","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/SINTEF-9012/PruneCluster"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Jitter between markers? (#166)"}],"action":{"name":"View Issue","url":"https://github.com/SINTEF-9012/PruneCluster/issues/166"}}}

You may want to look at this:
var PruneClusterLeafletSpiderfier = (L.Layer ? L.Layer : L.Class).extend({
_2PI: Math.PI * 2,
_circleFootSeparation: 25,
_circleStartAngle: Math.PI / 6,
_spiralFootSeparation: 28,
_spiralLengthStart: 11,
_spiralLengthFactor: 5,
_spiralCountTrigger: 8,
spiderfyDistanceMultiplier: 1,
initialize: function (cluster) {
this._cluster = cluster;
this._currentMarkers = [];
this._multiLines = !!L.multiPolyline;
this._lines = this._multiLines ?
L.multiPolyline([], { weight: 1.5, color: '#222' }) :
L.polyline([], { weight: 1.5, color: '#222' });
},
Change it to 2 or 3 and you will see the different.


Exclude injector.cpp in other OS except windows

At this moment, If we try to install node-dll-injector in Mac or Linux, it just fails.
This PR fixes that.

Happy to accept the PR since yes, it will fail to build on a non-Windows OS.
Also though this package does absolutely nothing on a non-Windows platform since its entire functionality is to access Win32 APIs.
(Also I'm actually somewhat unhappy with this injector implementation, in practice I've found it handles errors poorly. I've reimplemented it but also switched away from Node)

Thanks for merging the PR. Can you share the details the new DLL injector ?

I switched away from Node, but the implementation is here: https://github.com/mcoot/TribesLauncherSharp/blob/master/InjectorLauncher.cs


Parent run status is always "completed" even if submitted child runs failed.

[Enter feedback here]
I was following this documentation and found that the parent run status was always "completed" even if submitted child runs failed. Is it correct behavior ? If yes, is there a way to propagate child runs status to parent runs ?

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

ID: 889f9925-878f-e2a0-262a-240e1611bce2
Version Independent ID: 9349cb37-8107-3d5a-98d1-9a45419c64de
Content: Start, monitor, and cancel training runs in Python - Azure Machine Learning
Content Source: articles/machine-learning/how-to-manage-runs.md
Service: machine-learning
Sub-service: core
GitHub Login: @rastala
Microsoft Alias: roastala

@chengyu-liu-cs Thank you for the feedback. We are actively investigating and will get back to you soon.

@chengyu-liu-cs , thanks for the feedback!
That is the intended functionality. However, you bring up a great point about how child runs can be a confusing subject. I've created a document work item to track improvement to clarify guidance around child runs and run organization, and assigned it to one of our writers. https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1780225
Our doc team will prioritize work items and include this story in our planning. I'll proceed to #please-close this issue.


New licensed hardware

Is there any plan to add more hardware in the LICENSED-HARDWARE list?
It was said to be more coming soon, but there has not been an update sin April 2021. I'm planning o a new HW design and that would be a great information to know.
Kind regards,

We don't have any new partners/hardware yet. What MCUs are you considering?

Thanks for your response Scott. We are testing some ARM from NXP. We are
actually working with the IMX8MPlus eval kit. But we could use some other
ARM as long as it has PCIExpress ports.
Kind regards,
Fernando Gallego Vilaltella
Operations and Innovation Manager
M  (+34) 654 93 41 54
T  (+34) 932 98 86 50
E  fernan.gallego @ lanaccess. com
LANACCESS https://www.lanaccess.com/ | + segura + inteligente + rentable
On Thu, 19 Jan 2023 at 20:05, Scott @.***> wrote:

We don't have any new partners/hardware yet. What MCUs are you considering?
—
Reply to this email directly, view it on GitHub
https://github.com/azure-rtos/threadx/issues/223#issuecomment-1397469369,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWNQPBYDEOD5VS4XWQULMKTWTGF7TANCNFSM6AAAAAAT4RR2TY
.
You are receiving this because you authored the thread.Message ID:
@.***>

I suggest you reach out to NXP to see if they are considering adding the iMX8 to the licensed hardware list. Offhand, I don't know what currently licensed hardware has PCIE ports.


Prevent making useless symbols.

Groups are concatenated with ':' in Bundler::Settings#without=,
and splited by ':' in Bundler::Settings#without. So

to_sym in Bundler::CLI#install is useless
:-separated list is also allowed.

why don't you just remove the useless map to_sym?


Introduce FlowLayout

Components should be scaled and positioned according to flex layout rules.

Done in a previous commit


Permission problem in a view

Hi @driesvints
I used Laravel 5, version 0.2 of the package and array as driver.
I created an alias to manage the crud, in lock.php
    'permissions' => function (Manager $manager, Lock $caller) {
        $manager->alias('manage', ['create', 'read', 'update', 'delete']);

I set the privilege of the alias for a resource
$manager->role('reseller')->allow('manage',   'users');

I denied one of the actions for that resource
$manager->role('reseller')->deny('create', 'users');

If I try with dd, the action is properly denied :heavy_check_mark:
If I try from view, the action is permitted :interrobang:
Is my mistake or a bug?

I'm just gonna be honest with you. I don't have the time atm to look into this and probably won't have for the upcoming weeks. If anyone can take the time to figure this out, that'd be great :confused:


Add prop for fixed selection dot and fadeout starting point.

Update C++ standard to c++17
Update Cocoapods version to latest stable
Add selectionDotValueX prop for a fixed position of the selection dot
Add fadeouValueX prop for a fixed starting point for the fade out

https://github.com/margelo/react-native-graph/assets/39256258/e97f6e42-9701-4de5-b297-1dcc57d190bc

@mrousavy would you be interested in merging this?

Hey - yep, I am! I'm just waiting for @chrispader to get back from vacation, as he's the main responsible maintainer for RN Graph nowadays :)

thanks for your PR on this!!

Cool! Thanks for letting me know. Will continue any further discussion and ideas with him

I have been using this, as well as @gabimoncha 's forked CustomIndicator component PR would be good to get these merged

@chrispader let me know if you need any help to streamline this :D

@theblondealex @chrispader - I have another one where I pass the index of the data point to onPointSelected in case you want to use it for additional visualisation in a larger dataset object 😅

i'm gonna look into this tmrw! sorry for the delay...

@theblondealex @chrispader - I have another one where I pass the index of the data point to onPointSelected in case you want to use it for additional visualisation in a larger dataset object 😅

@gabimoncha could you provide me a link to that?

@chrispader - here
Each branch is a different feature for the app. The ones I told you on discord too

Custom starting point for selection dot. this PR
Custom Indicator - same props as SelectionDot.
Passing the index in onPointSelected, if needed to link data point to a bigger data set

@chrispader any updates on this PR?


Reducing noise in NewRelic reporting...

...by stripping individual resource IDs from resource URIs for New Relic reporting
Currently SavoryPie logs every resource ID as its own request. This is a problem in systems that do mass-sequential GETs, DELETEs, and/or PUTs to resources because it causes NewRelic to be flooded with an excessive amount of data.
This PR changes the default behavior to strip off the trailing ID if there is one.
For example:
'bars/foo' => 'bars/foo'
'bars/bar/9' => 'bars/bar'
'bars/19229' => 'bars'
'bars/magic8ball' => 'bars/magic8ball'

This will allow NewRelic to see all PUTs to a given resource, for example, as the same action over and over again so that the data can be properly analyzed.

:+1:

:+1:

Not familiar with savory pie, but the code looks good :+1:


Speed up TopoSort by 2.5-3x.

The main implementation in TopoSort::sort_worker is 11-12x faster. Overall, the complete sequence of building the graph and sorting is about 2.5-3x faster for the circuit I am working on. The overall impact in e.g. the replace_const_cells optimization pass is a ~25% speedup. End-to-end impact on our synthesis flow is about 3%.
[Note: I ran clang-format --style=${YOSYS}/.clang_format on the mostly rewritten utils.h file, and fixed a few minor compiler warnings in the process.]
Flame graph, zoomed on replace_const_cells, before:

Flame graph, zoomed on replace_const_cells, after:

Topdown view before:

Topdown view after:

What are your thoughts on this PR? I could back out the unrelated formatting changes in utils.h, if so desired.

OK, I got rid of the needless formatting changes in kernel/utils.h.  PTAL.

It looks like one of the xilinx tests fail. Investingating.

Fixed. BTW: I realized that this code is brittle, since the sort order in map and set for some uses of TopoSort depend on the sort order of pointers. This is generally a bad code smell, since it tends to make code non-deterministic.

OK, It finally passed.  :-)  PTAL.

 Speeds everything up by another 10%.

In case you're wondering what's blocking this and #3975, I'd like somebody else to look over and approve it before I merge it, because I'm unfamiliar with the RTLIL internals; perhaps @mmicko?

In case you're wondering what's blocking this and #3975, I'd like somebody else to look over and approve it before I merge it, because I'm unfamiliar with the RTLIL internals; perhaps @mmicko?

Yeah, no worries. It's always good to have more eyes on it.

We could opt for a non-recursive algorithm (a code example I have at hand), but that might not be producing the sort order code users expect, especially if they supply the C template argument.


64-bit SHA-3 assembly changes violate ABI for int parameter

#21511 introduced an int parameter to a bunch of assembly functions. int is 32-bit, even on 64-bit architectures.
Taking a 32-bit parameter in 64-bit assembly is a little subtle. Many 64-bit calling conventions say that 32-bit parameters, when passed in registers, leave the upper half of the register unspecified. This means assembly functions cannot rely on them being any particular value, like zero. Reading the upper half of the register can then, depending on how the compiler happens to emit code, generate the wrong value.
For example, clause C.9 in AAPCS64 only promises the least significant bits of the register are filled in.
https://github.com/ARM-software/abi-aa/blob/main/aapcs64/aapcs64.rst#parameter-passing-rules
You can see this in action here. Observe how Clang does not do anything to mask off the upper half of the register here.
https://godbolt.org/z/ao3WxMfr7
When I last looked at this years ago, I was unable to find a citation that officially said x86_64 calling conventions (SysV or Windows) did this too, but I was able to observe compiler output which implied this was the case. No idea about ppc64.
The assembly added in #21511 seems to access the values as 64-bit. That means, on architectures with the above calling convention, they can get the wrong value, depending on how the compiler chooses to generate code.

No idea about ppc64.

Looks like this is what past me wrote about ppc64.
  // ELFv2, section <IP_ADDRESS> says the parameter save area sign- or zero-extends
  // parameters passed in memory. Section 2.2.3 is unclear on how to handle
  // register parameters, but section <IP_ADDRESS> additionally says that the memory
  // copy of a parameter is identical to the register one.

So I think that means accessing the 64-bit register on ppc64 is fine? But you all might want to double-check that.

@slontis FYI

Would you recommend setting the type to a uint64_t ?
looking at aes_platform.h there are quite a few int params being used in there.
'bits' and 'enc'.

I would prefer properly accessing the arguments as 32 bit and not changing the type. I'll add that to  #22750

@davidben Note that I havent forgotten about your ABI testing comments.


wasi-nn: refactor to allow preview2 access

This change refactors the wasmtime-wasi-nn crate to allow access from both preview1 and preview2 ABIs. Though the wasi-nn specification has included a WIT description for some time, here we use some in-tree files until https://github.com/WebAssembly/wasi-nn/pull/38 is landed. The preview2 code is not exercised anywhere yet: ideally this would be wired up once component model resources are fully implemented in Wasmtime.

One part of this is that it defines a hierarchy of types and then provides conversion of WIT and WITX-generated types into this hierarchy of types. That's reasonable for this crate since the set of types is quite small, but for something like wasi-common I'm not sure if that would work well (or larger proposals). In that sense it might make more sense to unconditionally generate WIT bindings (e.g. not a compile time feature) and always use the WIT types generated? That way there'd only be one conversion necessary which is WITX-to-WIT.
Also one thing to consider is that this has impl WasiNnTrait for WasiNnCtx which means that it's not going to be easily usable from embedders. Currently with bindgen! we're using something that looks like impl<T> WasiNnTrait for T where T: WasiNnView so that way if WasiNnCtx is embedded in a store somewhere the WasiNnView defines how to access it.
Also as a final thing, it looks like the implementation bodies of WIT and WITX are duplicated? Would it be possible for one to delegate to the other?

In that sense it might make more sense to unconditionally generate WIT bindings (e.g. not a compile time feature) and always use the WIT types generated

Yeah, I would prefer that. Is it fine if wasmtime-wasi-nn enables the component-model feature, though, forcing every user of this (e.g., the CLI) to do so too?

impl<T> WasiNnTrait for T where T: WasiNnView

I saw this over in wasi or wasi-common and didn't really "get" it. Let me look into it a bit more.

Also as a final thing, it looks like the implementation bodies of WIT and WITX are duplicated? Would it be possible for one to delegate to the other?

They are duplicated in essence but not all the details are the same; e.g., anywhere we need a slice in witx.rs we do the Wiggle GuestSlice dance. I'll look into this a bit more...

@alexcrichton: one more thought about your comments is that perhaps some of these improvements could be done as a separate PR. There is clearly more work that needs to be done here (e.g., replace all these temporary WIT files with their upstream versions, implement named models, etc.) so perhaps some of the refactorings you suggest could fit into some of those PRs.


mount.nfs requested NFS version or transport protocol is not supported

Debian10
Vagrant 2.2.18
Most recent sandbox
Expected Behaviour

cd sandbox/deploy/vagrant vagrant up provisioner - starts the sandbox

Current Behaviour

==> provisioner: Mounting NFS shared folders...
==> provisioner: Pruning invalid NFS exports. Administrator privileges will be required...
==> provisioner: Removing domain...
==> provisioner: Deleting the machine folder
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=4,rw,vers=4,tcp <IP_ADDRESS>:/home/banner/Documents/Lib/Tinkerbell/deploy /vagrant

Stdout from the command:

Stderr from the command:

mount.nfs: requested NFS version or transport protocol is not supported

Possible Solution

Steps to Reproduce (for bugs)

Install debian10
install vagrant
install kvm-libvirt
run vagrant up

Context

Your Environment

Operating System and version (e.g. Linux, Windows, MacOS):

How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details:
Vagrant + Libvirt

I tried this on two separate servers, both debian10. Both incurred the same error.
vagrant plugin list
vagrant-docker-compose (1.5.1, global)
vagrant-libvirt (0.5.3, global)

It's late, I could have very easily overlooked something dumb, but I haven't gone out of my way to do crazy things here. Just pulled the repo and run vagrant up.

Hey @MikePadge, thanks for reporting this. I've opened PR #98 that should fix this.

Welp, I feel dumb, but that did the trick. Thank you kindly.

Actually @jacobweinstock this completely breaks the docker-compose setups inside the vagrant containers, probably something to do with the extreme finicky of docker and nfs.
I can get away with nfsd, I was just looking in the wrong place, thinking I needed a vagrant nfs plugin or something I couldn't find.

Hey @MikePadge, sorry I'm not following. The PR #98 breaks the docker-compose? That PR doesn't use NFS anymore.


Help page for OORT command line

Not to complain too much, but the page https://github.com/owlcollab/owltools/wiki/Oort-Command-Line does not actually provide any instructions on how to run OORT on the command sweetie. The help file alone (at owltools -h) is not sufficient for me to know how to run the ontology release manager.
I installed OWLtools from the jars on Jenkins, and tried to use "ontology-release-runner -h", but I got the message "command not found".
I also tried "owltools ontology-release-runner -h" but got "could not parse:ontology-release-runner" followed by a long error message.
I know the wiki is in transition. Is there any old documentation  you can point me to to get started? I saw this (https://github.com/owlcollab/owltools/wiki/Command-Line-Examples) page, but it was a bit high level.
Do I need to download "ontology-release-runner" from Jenkins as well?

I made some progress by downloading ontology-release-runner and owltools-oort-all.jar and placing them both in /bin. I can now see the OORT help file.

Yes, the OORT documentation, is out-dated and incomplete. It is on my TODO list to update that.

We're not planning to spend too much time updating the OORT docs as this will be superseded by ROBOT (Robot is an OBO Tool) being developed by @jamesaoverton https://github.com/ontodev/owltools2-experimental
...but we want to make sure people aren't completely flummoxed in the interim, so yes we at least need better info on getting started

I think what would really help is a few command line examples of how to do a release. Even though the help file says to use:
"bin/ontology-release-runner [OPTIONAL OPTIONS] ONTOLOGIES-FILES"
and lists the options, in my 20 minutes of playing around with it, I couldn't find a functional syntax.

If it helps, you could try the graphical user interface (GUI) for OORT: Download the ontology-release-runner-gui script. This script uses also the owltools-oort-all.jar.

I did think of that and download that script, but two problems:

(very simple) I can't figure out what command to use to open the GUI (I am a java novice)
In the current (older) version of the GUI I have, I cannot figure out how to use the force release option to let me include equivalent classes in my release (nor do I particularly understand why that is an error). Maybe it is obvious in the new version.

Actually, I remember that I couldn't find some perl scripts used by the Makefile provided, to generate, e.g., the diffs between releases. I think I found them on an obscure repository belonging to Chris. Providing all the perl scripts would help (or at least, pointing to their location).

The ontology-release-runner-gui script is a simple bash script wrapping the java command. You can just open it in a text editor to see the details.  To run the script, you might need to make it executable using the chmod command:
chmod 755 ontology-release-runner-gui

And you are right, the current OORT GUI does not have a flag to force the release. In theory you can add that flag during the startup of the GUI  --force. That would just look like:
./ontology-release-runner-gui --force

They are here:
https://github.com/cmungall/obo-scripts
They are concentrated pure evil. Don't touch them.
I warned you....
Seriously whilst there are various Makefiles kicking around that use these their use should be phased out

Yes, that flag for force release worked, Heiko. Thanks! Also, I didn't realize I had to be in the same directory to get the GUI to run. Thought I had it in my PATH, but it doesn't seem respond the same way as ontology-release-runner (which I can run from wherever).

Haha Chris, these scripts are evil, but very useful! What do you currently use for releasing ontologies, if not these scripts?

Most ontologies use only Makefile-driven owltools or oort.

https://github.com/obophenotype/cephalopod-ontology/blob/master/src/ontology/Makefile
https://github.com/obophenotype/porifiera-ontology/blob/master/src/ontology/Makefile
https://github.com/EnvironmentOntology/envo/blob/master/src/envo/Makefile
http://viewvc.geneontology.org/viewvc/GO-SVN/trunk/ontology/extensions/Makefile?view=markup

Some like GO have an extra layer of checks that happen downstream with hacky perl scripts like this:
http://viewvc.geneontology.org/viewvc/GO-SVN/trunk/software/utilities/check-obo-for-standard-release.pl?view=markup
Uberon is a big mix, but we hope to standardize with ROBOT


chore: bdd-spring-1587536627 to 0.0.1

chore: Promote bdd-spring-1587536627 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


vFile plugin: volume create/rm stuck forever when ETCD is broken

What happened:
When the ETCD cluster went to unhealthy mode due to reasons like quorum loss, docker volume create and docker volume rm with vFile driver will stuck forever.
What you expected to happen:
vFile plugin should return error with proper message indicating the status of ETCD or swarm cluster is unhealthy.

Fixed by https://github.com/vmware/docker-volume-vsphere/pull/1850


update to TorchSharp code

I will continue to update

@uxmal
FYI: use case ChatGPT

Please indicate when the PR is ready to be merged.

Please indicate when the PR is ready to be merged.

Merged


Feature request: "Top P" in Advanced AI settings

I like to set my "Top P" to 0.5 alongside my temperature of 0.5 for programming questions with GPT-4. Could this be added to Advanced AI settings?

For sure, easy to do. Just out of curiosity: what does it do to the generation? (Asking for subjective experience) and would it be worth to do it by default on the Developer profile?

For sure, easy to do. Just out of curiosity: what does it do to the generation? (Asking for subjective experience) and would it be worth to do it by default on the Developer profile?

It makes it less creative and more accurate. For each generation, GPT has a list of tokens and probabilities. At 1.0 it can choose any of them. At 0.5 it can only choose the top half. However, open AI recommends that you only set either temperature or top P but not both. To be honest, I don't have a great feel for how they change the results yet. I'm still fiddling with the parameters. It would be nice to have a formal benchmark of how they affect accuracy in programming.

(I think this means that Open AI is suggesting that if one of them is reduced, leave the other one at 1.0)

I achieve the same with the "temperature" - when I want it to be more creative/explorative (and maybe have errors :) I set a temperature closer to 1. With a temperature of 0, it will always be the most obvious and fitting code.
I wonder how to convey in the UI to change top_p OR temperature. It's very deep down in the details for people.

@enricoros That's tricky.. maybe a selector between Top P and Temperature, and a slider to set the one selected. Feels a little awkward though.

It's actually a great idea.


A second connection watching a tube hangs reserve-with-timeout

When using reserve with timeout from multiple connections on the same tube, only the last one receives "TIMED_OUT".  The other connections hang indefinitely.  This is occurs with the trunk codebase.
More specifically:

connection A watches tube 'foo' then issues a reserve-with-timeout N seconds
connection B watches tube 'foo' within the N seconds period
connection A is never issued a "TIMED_OUT" response

The issue seems to stem from the existing connection being removed from srv->conns when the most recent connection issues the watch foo command.  I'm still digging into the code to understand why that is happening.

Confirmed, thanks. If there's anything I can do to help you
track this down, let me know!

Cool, I think I'm pretty close.  I'll be off the internets for a few days but I hope to emerge from the woods with a patch.

Cool, I didn't mean to close this just now.  Anyway, I think I'm pretty close and I hope to have a patch by Monday.

Ok, I have a one-line fix but developing a unit test for the bug will be trickier because the current unit test framework does not appear to support multiple concurrent connections.  I'll look to see if I figure something out this evening.

Hey, even if it's not totally finished, can you push the fix for this
in a branch somewhere? I'd like to take a look at it.
It shouldn't be too hard to copy testsrv in integ-test.c to a new
function and edit it to make two concurrent connections.

I just wrote a test for this.

Great!  I saw your message about adding the test and was going to check my fix (which we've been running in production since October) but it looks like I'm too late.  I had slightly changed the logic in srvscheconn in srv.c but your fix is better.

I'm still seeing exactly this behavior on 1.5


Help with off device symbolication

How do i do off device symbolication with KSCrash reports? Seems the report format is not compatible with symbolicatecrash provided by xcode.

If you rename the .txt file generated to .crash, you should be able to use symbolicatecrash. Maybe you're using a formatter other than KSCrashReportFilterAppleFmt? If so, you can get apple-style reports like so:
[installation setReportStyle:KSCrashEmailReportStyleApple useDefaultFilenameFormat:YES];

There is additional info in step 4 of the setup section of the README

I tried using symbolicatecrash to process the crash file and it errored out as all of the necessary preamble to decipher the contents of the file is missing. I will check to see if we are setting any specific report style.


Adds sample painless script to extract n-grams

Thank you for the review @joshdevins !
Have modified according to the changes you requested.


⚠ Bofrost.at has degraded performance

In 3c76eea, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2757 ms

Resolved: Bofrost.at performance has improved in 20d9d9d after 8 minutes.


fix(nasdaq): fetch index only based on weekdays (#22)

Resolve bug when you could not fetch index from NASDAQ on weekends, because there is no information on weekends when the market is closed. Now we check if its a weekend and in that case offsets back two days to a day where we know there is data.

Codecov Report
All modified lines are covered by tests :white_check_mark:

Files
Coverage Δ

finq/datasets/custom.py
100.00% <100.00%> (ø)

finq/datautil/nasdaq_requests.py
97.61% <100.00%> (+0.18%)
:arrow_up:

tests/datasets/custom.py
100.00% <100.00%> (ø)

:loudspeaker: Thoughts on this report? Let us know!.

I'll close this PR because #23 has better implementation.


ionic plugin add eats stdin

Sounds like we're not piping stdin to cordova plugin add:
https://github.com/driftyco/ionic/issues/4429

Thanks for opening the issue. It seems that issue has been resolved. I am going to close this issue but please feel free to reopen another issue if this occurs again.


Added symlink dereferencing in fast packaging and tests

TL;DR
Adds a switch to enable dereferencing symlinks during fast packaging in pyflyte serialize fast workflows.
cc @wild-endeavor
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[x] Unit tests added
[x] Code documentation added --- added documentation for click switch
[ ] Any pending items have an associated Issue

Complete description
Added a click switch to pyflyte serialize fast workflows that enables/disables dereferencing any symlinks encountered during packaging. This only applies to fast_package.
Tracking Issue
NA
No issue associated with this -- this is part of a request from Stripe. Our use case for this is as follows:
Our workflows often import code from utils files that are in sibling directories -- this makes the current pyflyte package not quite work for us. Our workaround is to use our bazel build target, which generates a runfiles directory that contains all the source code and dependencies, and then serialize from that folder. Some symlinks are generated during the build, so we needed to add dereference=True when opening the tar file so that the actual target contents are loaded and downloaded during execution.
This change should not effect any of the current DataPersistence plugins that are used since they are all remote and would require dereferencing symlinks anyways if they wanted to use the contents.
Follow-up issue
NA

This change looks good. Can you also make sure that new flag is added to the other places where fast_package is used?

Thanks for catching that! There was one place that I missed.

What about https://github.com/flyteorg/flytekit/blob/3137609c6d838a92077b7be27fc92cef78144066/flytekit/tools/repo.py#L98 ?

Ah my bad, missed that.

@eapolinario
Any idea on when this would be released? We see that there are monthly releases usually and one hasn't happened yet for september.


Allow positional include args for FilterTransforms in Adapter

The following call will raise a confusing error:
a = bf.Adapter()
a.standardize("x")
>>> TypeError: Adapter.standardize() takes 1 positional argument but 2 were given

However, the intent is very clear: we only want to standardize x. The current way to do this is via an include list which is given as an explicit keyword argument:
a.standardize(include="x")

However, this seems a little bit ugly. We could allow users to pass this as a positional argument as well. So long as none of the keyword-only arguments are defined, we default to turning the positional argument into the include list.

I agree. makes sense to me.


Allow the Config object to specify the locale

When installing Habari or running it generally, it would be useful if the locale could be controlled by a setting in the config file.
Currently, the installer uses the global $locale value (if it is set and uncommented) from the default config.php (if it exists).  This is only used by the installer (which then writes it to the database), and not by Habari in-use (which reads the value from the database).
The installer should read the value from a Config setting, ala:
Config::set( 'locale', '{$locale}' );
Habari in-use should also check this Config value for the current locale, and override any value set in the database.  (This last bit may be a topic of discussion -- please discuss.)

What do you see as the advantage of the config overriding the DB? My initial concern is user frustration when changing the locale through the admin and having it not appear to change, having defined and forgotten the config value.

Actually, my inclination would be to store the locale entirely in the config, rather than in the database at all.

Which would make it difficult to change the locale through the admin, no?
Let me put the question another way. Beyond having a localised installer, what is the advantage of having the locale defined in the config?

Defining the locale in the config would allow a locale to be set for an automated installation.
If the setting is in the database, a user may have difficulty navigating the admin to choose the correct option.  It may be easier to direct a user to the config file to alter the setting.
I should clarify my comment from earlier: My inclination is to remove the ability to set the locale from the admin, and to put it as a hard-coded option in the config file instead.

After some thought, I wouldn't object to this change. Some of those thoughts ...
On install, if there's a config file with a locale defined, we use that for the installer. If there's none, we use en-us for the installer, but the user can chose a different locale from the dropdown (it would be nice if we reloaded the installer in that language, if we don't do that already). It's also interesting to think about how this might work when locales are installed from an addon directory using hpm rather than bundled.
This would put locale on the same level as database credentials.

Related: #251


[10.x] Add assertActingIs in TestResponse

Assert acting user.
$user  = User::factory()->create(['name' => 'milwad']);
$user2 = User::factory()->create(['name' => 'taylor']);

$response = $this->actingAs($user)->get('/');

$response->assertActingAs($user); // pass ✅
$response->assertActingAs($user2); // fail ❌

If merged, I will add related tests.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Issues configuring message limit

We are using the latest postal version and adding the following isn't still helping us increase the message size limit to 25MB.
smtp_server:
max_message_size: 25
We are seeing the following error.
552 Message too large (maximum size 14MB)
I have restarted postal after making the change and it still isn't working.

Can you share your postal.yml, redacted as much as you need?

`web:
The host that the management interface will be available on
host: mail.example.com
The protocol that requests to the management interface should happen on
protocol: https
fast_server:
This can be enabled to enable click & open tracking on emails. It is disabled by
default as it requires a separate static IP address on your server.
enabled: false
bind_address:
general:
This can be changed to allow messages to be sent from multiple IP addresses
use_ip_pools: false
main_db:
Specify the connection details for your MySQL database
host: <IP_ADDRESS>
username: postal
password: password
database: postal
message_db:
Specify the connection details for your MySQL server that will be house the
message databases for mail servers.
host: <IP_ADDRESS>
username: postal
password: password
prefix: postal
rabbitmq:
Specify the connection details for your RabbitMQ server.
host: <IP_ADDRESS>
username: postal
password: password
vhost: /postal
smtp_server:
max_message_size: 25
dns:
Specifies the DNS record that you have configured. Refer to the documentation at
https://github.com/atech/postal/wiki/Domains-&-DNS-Configuration for further
information about these.
mx_records:
- mail.example.com
smtp_server_hostname: mail.example.com
spf_include: spf.mail.example.com
return_path: rp.mail.example.com
route_domain: routes.mail.example.com
track_domain: track.mail.example.com
smtp:
Specify an SMTP server that can be used to send messages from the Postal management
system to users. You can configure this to use a Postal mail server once the
your installation has been set up.
host: <IP_ADDRESS>
port: 2525
username: # Complete when Postal is running and you can
password: # generate the credentials within the interface.
from_name: Postal
from_address<EMAIL_ADDRESS>workers:
quantity: 10
rails:
This is generated automatically by the config initialization. It should be a random
string unique to your installation.
secret_key: {{secret_key}}`

web:

The host that the management interface will be available on
host: mail.example.com
The protocol that requests to the management interface should happen on
protocol: https
fast_server:
This can be enabled to enable click & open tracking on emails. It is disabled by
default as it requires a separate static IP address on your server.
enabled: false
bind_address:
general:
This can be changed to allow messages to be sent from multiple IP addresses
use_ip_pools: false
main_db:
Specify the connection details for your MySQL database
host: <IP_ADDRESS>
username: postal
password: password
database: postal
message_db:
Specify the connection details for your MySQL server that will be house the
message databases for mail servers.
host: <IP_ADDRESS>
username: postal
password: password
prefix: postal
rabbitmq:
Specify the connection details for your RabbitMQ server.
host: <IP_ADDRESS>
username: postal
password: password
vhost: /postal
smtp_server:
max_message_size: 25
dns:
Specifies the DNS record that you have configured. Refer to the documentation at
https://github.com/atech/postal/wiki/Domains-&-DNS-Configuration for further
information about these.
mx_records:
- mail.example.com
smtp_server_hostname: mail.example.com
spf_include: spf.mail.example.com
return_path: rp.mail.example.com
route_domain: routes.mail.example.com
track_domain: track.mail.example.com
smtp:
Specify an SMTP server that can be used to send messages from the Postal management
system to users. You can configure this to use a Postal mail server once the
your installation has been set up.
host: <IP_ADDRESS>
port: 2525
username: # Complete when Postal is running and you can
password: # generate the credentials within the interface.
from_name: Postal
from_address<EMAIL_ADDRESS>workers:
quantity: 10
rails:
This is generated automatically by the config initialization. It should be a random
string unique to your installation.
secret_key: {{secret_key}}

postal.txt

Is that definitely /opt/postal/config/postal.yml?
Also you could try putting newlines before dns: and rails: for consistency.

Yes, that is the default postal.yml on which, I ended up changing the credentials etc, replaced it with dummy values and pasted it here. The only change apart from those credentials etc is the section to add the message size.
smtp_server:
max_message_size: 25
Added new lines before dns: and rails: and restarted postal to ensure the yml is consistent.

I mean /opt/postal/config/postal.yml instead of /opt/postal/app/config/postal.example.yml or something else in the app folder.
Have you tried restarting the whole server? There might be an issue when you're restarting that isn't letting the processes update.

Yes, I did try restarting the server and nothing helps. How do we overcome this?

I'm assuming you're on the latest Postal, you can check with postal auto-upgrade.
If you're running the latest Postal and you've definitely edited /opt/postal/config/postal.yml and Postal has definitely been restarted, the setting should apply.

I did attempt the postal auto-upgrade and it did some git pull, and then restarted postal. Still the same issue.
Attaching the upgrade logs. If the upgrade is run again, it is doing the same process again. I'm not sure how to prove you that I have restarted postal, and the config file provided is the one available on the server, and still the issue remains.
output.txt

I have the same problem. Changing the max_message_size doesn't actually work and I still get 14mb limit error.
I'm not sure how the auto-upgrade works but since https://postal.atech.media/packages/ hasn't been updated since 1st November 2017, neither on stable nor beta branch, I'm not sure if the update actually contains the latest code.

That is a great spot @arashm and I've verified that is exactly the case with our development server.
@catphish are you able to make an up to date build?
In the meantime, you could make the changes to the ruby file and database yourself to enable you to keep using Postal.

@willpower232 What does this mean with regards to the issue am facing? Any workaround or solution for us to go live with an increased message limit?

In the meantime, you could make the changes to the ruby file and database yourself to enable you to keep using Postal.

Updating the code is only one line of code to change but you will also need to change the type of database field to guarantee it can store your attachments.

@willpower232 Can you help us with that change? I'm not sure where and what to change.

You would have to make the changes from the pull request where you originally commented (https://github.com/atech/postal/pull/383).
If you make the changes outlined in the "Files Changed" tab and then restart Postal, you should find your message limit increased.

@willpower232 We are able to resolve this issue now. Future upgrades will override this issue?

Hopefully, the next update should include the changes but that relies on a new build being made.
If you run the update command and it resets your code, your current code copy should be automatically backed up in a new folder for you to restore from.

I hope it will include fbl

Is there any way I could help so the release happens faster? Is there any roadmap? Left issue or something?

I believe it is a process internal to atech so requires their attention primarily

@willpower232 just spotted this issue, few mails failed due to attachment size issue and can see that the code is not updated as mentioned in the pull request which is merged: https://github.com/atech/postal/pull/383 . We just did an auto-upgrade and can see that the smtp_server/client.rb file is not updated to match the change. @adamcooke and @catphish will this be updated in upcoming release?


Suggestion

Use slash commands and buttons instead of reactions in discord.

Maybe you can let us type the Login text on screen like tellraw and title command.

I'm sorry I don't answer at this time, but I barely have time in my life to live outside of work and studies.
When I have time, I will try to find out this topic. I know that slash commands are more useful and showy.

Slash commands are avaiable on the beta.


Add capacity to read-in gridded forcings when executed in standalone

Purpose
This PR adds capacity to read-in gridded forcings when executed in standalone (i.e., outside of NextGen).
Additions

This PR adds two type-bound subroutines in ReadForcings and SetForcings. These subroutines were added to forcinggrid_type in ForcingGridType.f90.
The ReadForcings subroutine finds/opens/reads the forcing file for an argument date. The forcings are read-into newly added 'read' arrays (e.g., forcingsgrid_type%read_pcprate holds read-in values for precipitate forcings).
The SetForcings subroutine transfers forcing values from the added 'read' arrays to the forcinggrid_type arrays that hold forcings for the current time step (e.g., values in forcingsgrid_type%read_pcprate are transferred to forcingsgrid_type%PRCP).

Changes

Before this PR, domaingrid_type%nowdate was calculated within a call to UtilitiesMain via solve_noahowp. domaingrid_type%nowdate was therefore recalculated for every grid cell. After this PR, domaingrid_type%nowdate is calculated with a call to advance_in_time (in RunModule.f90), which facilitates passing domaingrid_type%nowdate as an argument to the newly added ReadForcings and SetForcings subroutines and prevent the unnecessary recalculation of domaingrid_type%nowdate with every grid cell.

Testing

Hourly AORC forcings were obtained for the North Fork (WY) test basin from Jason
A py script was created to aggregate the hourly forcings into daily, monthly, and yearly forcing files

Please contact @GreyEvenson-NOAA for these forcings as they are too big to upload to GitHub

The PR modified code was tested once for each of the forcing aggregation time steps (i.e., hourly, daily, monthly, yearly)

This PR is an optimization that reduces the number of times that a call that advances the model simulation time is invoked.

Compiled and executed: run/noah_owp_modular.exe
test/noahowp_test.exe ../run/namelist.input > output_test
No errors were detected. The results of the test output were not posted on Github for comparison with the output generated from this test.


[Release] Release FR Preview 4 Package

Work through Release Checklist

Package released https://www.nuget.org/packages/Azure.AI.FormRecognizer


Ignore  tags inside mdx

🚀 Feature
I'm trying to have some tabs that show code blocks inside them.
Tabs
  defaultValue="apple"
  values={[
    {label: 'Go', value: 'golang'},
  ]}>

  <TabItem value="golang">

Text

package main

import (
  "context"
  "encoding/json"
  "fmt"

)

func main() {
  configuration := package.NewConfiguration()
}

  <TabItem>

The page in question fails to display because := is an unexpected token, so it package.
Basically a lot of keywords prevent the page from being displayed.
It would be great to provide a way to ignore certain HTML code from being interpreted by the MDX parser.
Have you read the Contributing Guidelines on issues?
yes
Motivation
 tags might often create problems inside MDX.
Pitch
Maybe there could be a class provided by docusaurus, or a preset?
ignore_html_tags = ["code"]

I'm not versed enough in React to propose a solution.

If you use the  jsx element through MDX, you'd rather pass the source code directly as a string instead of using JSX text elements.
But writing a js string element this way might be annoying, so you'd rather use the mdx interleaving feature.
For this to work, you have to add line breaks around the interleaved MDX (this is  a limitation of current mdx implementation, I think it will be better in 2.0).

It would be great to provide a way to ignore certain HTML code from being interpreted by the MDX parser.

If you want MDX to be improved, you'd rather open an issue on MDX repo directly. We don't plan to add support for fancy features on top of it.


LUCENE-10164: lucene/replicator should only have jetty as a test dependency

The main code only needs to compile against the servlet api, but should work in any servlet.
Jetty is just the one used by the current tests.

for the record, it is just an improvement in the current build. i looked at the ant build and it was never a "test-only" dependency there (not sure it supported such things).


Issue on NP++ 6.2.2

After selecting the theme and restarting I see the following:

Also Global Styles Style panel is empty

Hi @nikolay-borzov, thanks for trying out the theme and apologies for such a late reply.
I tried reproducing your issue but I've been unable to so far.
One suggestion that I can give, based on my experience with Notepad++ themes, is, in the Style Configurator (Alt+S) try changing the theme to something different and then back to your desired theme.
Hope this helps, please let me know if you still face the issue.

I gave up after few attempts to fix the theme. Then I found an alternative theme

Apologies for not being able to help.
Good that you found something that works for you.

I'm seeing the same issue with 32bit Notepad++ v7.4.1, but not in 64bit v7.5.1. Could this be version related? The alternative theme listed by nikolay-borzov works fine on both versions, but the latest Material  Theme works only on the v7.5.1 64bit version.
It looks like the Material theme background color isn't respected by Notepad++ v7.4.1, it uses the background of the last theme used.
Material Theme selected after the default theme

Material Theme selected after the VS2012-Dark

Hi @mrantanen, thanks for trying out the theme and for giving time to the issue.
It does seem that this is a problem with older versions of Notepad++. I'll look into what's causing the issue and get back soon.


[Hudi 4065] create FileBasedLockProvider

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@hudi-bot run azure

@fengjian428 Left some comments you can consider. BTW, did you try to verify this lock mechanism for the insert override partition scene?

not yet. I think our users have used this for upsert, insert and drop partition
I can also test this for insert override partition scene


the example basic-example-button-view.component doesn't work

Hello,
I tried to make this example work:
https://github.com/akveo/ng2-smart-table/blob/master/src/app/pages/examples/custom-edit-view/basic-example-button-view.component.ts
But the function is not called, no console.log etc
renderComponent: ButtonViewComponent,
        onComponentInitFunction(instance) {
          console.log('call')
          instance.save.subscribe(row => {
            alert(`${row.name} saved!`)
          });
        }

how did you solve this issue?

@dario30186 I just think I upgraded ng2-smart-table


Use of np.round in computing biomass density

In the current code there are a lot of use of np.round in computing biomass density. Below are couple instances:
https://github.com/uw-echospace/EchoPro/blob/689ba79220353e5e994e533b6b816d6071da5a0a/EchoPro/compute_biomass_density/compute_biomass_density.py#L800-L802
https://github.com/uw-echospace/EchoPro/blob/689ba79220353e5e994e533b6b816d6071da5a0a/EchoPro/compute_biomass_density/compute_biomass_density.py#L617-L619
It is not clear to @b-reyes and @leewujung why these numbers are rounded to integers.

I'll close this one since we're no longer aiming for one to one match with Matlab code, due to other bugs.


Textarea content is white on white in dark mode

input fields have a darker color:
html.dark-mode .gh-content input {
    color: #303a3e;
}

But it doesn't seem to target textarea, which causes white on white text.

Something I noticed is that when Casper is manually switched from light to dark, a dark-mode class is available so that we can target the textarea with a CSS injection on the page to temporarily fix this, however if the theme is in auto mode (and it's currently dark), there's a auto-color class.
Is there a way the light/dark mode can be targeted with a CSS code injection when it's in this auto mode?

Hey @ryansechrest, the auto dark mode can be targeted with a CSS media query like below.
@media (prefers-color-scheme: dark) {
    html.auto-color ... {

    }
}

This is now fixed in 5.4.7 though. Thanks for the report :)


minor performance optimization

Just add cache for input.length * 32 expressions in loop.

Thanks, @Connormiha !


refactor(ui): Add a warning when an image fails to load containing th…

…e error
Helps to diagnose https://github.com/jorenn92/Maintainerr/issues/583

:tada: This PR is included in version 1.6.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Try to ensure we try to bind the elements of BindParam constraints le…

…ft-to-right.
If we allow the right-hand type to be bound first, it can artificially
limit the options for the left-hand side, so attempt to delay binding of
the right-hand side types until after we've chosen something for the
left-hand side.
The test here will not fail without this change, but will fail without
this change if the ConstraintGraph.cpp changes from @xedin's edge
contraction patch (https://github.com/apple/swift/pull/11118) are
applied.

@swift-ci Please smoke test

@swift-ci Please test source compatibility


sst start: child process started by Lambda function are orphaned

Observed by Dax:

Prisma spawns an rust executable to do connection management with the db.  Right now every time a function is invoked it spawns another one.  This shouldn't  be a problem but for some reason when the node process exits the rust binary sticks around.  Restarting sst kills them all and I have to do this periodically as my db connections get exhausted.  Wonder why it's not exiting with the node process

Closing for now some of the work in #672 will address this


Direct readers to the Google Genomics Cookbook

Also added --help and updated --numWorkers since the default machine type is now n1-standard-4.

@mbookman this goes a long with https://github.com/googlegenomics/start-here/pull/21

Coverage remained the same at 26.11% when pulling a76f0c80f602722af4da3e0945a49fbcd697848a on deflaux:master into 9dc348b4bd74550b7a929d51649a0bb5ddccdd36 on googlegenomics:master.

Coverage remained the same at 26.11% when pulling d04deaf46c2052a73600e079f5c4faf05cebc5cd on deflaux:master into 9dc348b4bd74550b7a929d51649a0bb5ddccdd36 on googlegenomics:master.

Coverage remained the same at 26.11% when pulling d04deaf46c2052a73600e079f5c4faf05cebc5cd on deflaux:master into 9dc348b4bd74550b7a929d51649a0bb5ddccdd36 on googlegenomics:master.

Coverage remained the same at 26.11% when pulling 451f4d91fc2916285a4181084fef668e0d7233ce on deflaux:master into 9dc348b4bd74550b7a929d51649a0bb5ddccdd36 on googlegenomics:master.


Small refactoring

Some small code refactoring + adds package.json.

I reverted the getMinMaxDate to getLatestDate.
Other changes remain


webpack externals config is ignored

In the worker dependencies, modules defined as externals are not found.

this is highly problematic for me. would love to hear more on this issue, in the mean time I will do more searching

@ducret201 @PendletonJones Guys, how do you cosider to use externals with isolated worker environment?

I have lodash as one of my externals and want to use it in the isolated worker. Hope that pr #42 can be merged ASAP.

@vamcc You mean lodash is a global variable?

@TrySound Yes, lodash is a global variable in my project.

@vamcc As you said worker is isolated. This means you can't access to window from workers. So you can't use externals.

@TrySound So, will it work if externals are in a UMD mode?

Nope. Dependencies should be bundled with worker and be loaded via importScript.

@TrySound Worker-loader won't support externals?

@vamcc WebWorkers won't support window global variables. Parallel processes can't share non-functional code. Processes should be independent.

@TrySound Ok, thank you.


Lagging (Not Internet lag or something else)

Lagging where when we play its not smooth just gameside, like everything moves 1 pixel per second and idk why, people say slowmotion to this but I am not sure about that.
How I fix that.

First check the st or status command and see what your update time is. 30+ is going to be noticed by players. Also, what modifications have you made to your server and how long has it been running?

Honestly under 1 is the best for the smoothest gameplay. I've noticed 15 does also cause a bit of stutter too. Anything over 10 isn't the best. I get 0.655 on my PC and right at 9.721 on my server after it's been running non stop for around 24 hours with bots and players active.

mine just crashed.
2016-09-05 19:57 GMT+02:00 Makan Dey<EMAIL_ADDRESS>
Honestly under 1 is the best for the smoothest gameplay. I've noticed 15
does also cause a bit of stutter too. Anything over 10 isn't the best. I
get 0.655 on my PC and right at 9.721 on my server after it's been running
non stop for around 24 hours with bots and players active.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Barbosik/MultiOgar/issues/329#issuecomment-244793145,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALWOX0rbbOKRwqoWvNCfZrxfXGIO9Qa9ks5qnFgmgaJpZM4J1MP7
.


VS2015 compile error -- conversion from netdb_errors to std::err_code

Enviroment:
Windows 7 Professional Service Pack 1 -- 64 bit operating system
VS2015 Version 14.0.24720.00 Update 1
Compiling under Debug Win32 and Debug x64
Boost 1.60               -- into directory Boost_1_60_0
cpp-netlib v0.11.2    -- into directory CPP_NetLib_012
I copied Boost to its own directory.  Within Boost_1_60_0/boost there was not a network directory; so I copied from CPP_NetLib_012/boost/network to Boost_1_60_0/boost
also copied mime.hpp and network.hpp into Boost_1_60_0/boost.
Here is the source code for the client, pretty much out of the example:
#include "stdafx.h"
#include <boost/network/protocol/http/client.hpp>
#include
int main(int argc, char *argv[])
{
using namespace boost::network;
if (argc != 2)
{
	std::cout << "Usage: " << argv[0] << " [url]" << std::endl;
	return 1;
}

http::client client;
http::client::request request(argv[1]);
request << header("Connection", "close");
http::client::response response = client.get(request);
std::cout << body(response) << std::endl;

return 0;

}
I get a tonne of warnings, that are all the same:
C4348	'boost::spirit::terminalboost::spirit::tag::ascii::char_::result_helper': redefinition of default parameter: parameter 3	Client_Netter	c:\blablabla\boost_1_60_0\boost\spirit\home\support\terminal.hpp	264
C4348	'boost::spirit::terminalboost::spirit::tag::ascii::char_::result_helper': redefinition of default parameter: parameter 4	Client_Netter	c:\blablabla\boost_1_60_0\boost\spirit\home\support\terminal.hpp	264
This is the error message:
Error	C2446	':': no conversion from 'boost::asio::error::netdb_errors' to 'const std::error_code'	Client_Netter	c:\blablabla\boost_1_60_0\boost\network\protocol\http\client\connection\async_normal.hpp	158
Async_normal.hpp looks like this:
} else {
set_errors(ec ? ec : asio::error::host_not_found);
boost::iterator_range<const char*> range;
if (callback) callback(range, ec);
}
Any insight would be appreciated.

You also need to build the libraries -- they're in libs/network/src.
I recommend you build/install with CMake as how we've documented it. You can generate a VS project and depend on cpp-netlib that way.

I just would like to add that I have the exact same problems when I try to build the libraries using CMake and Visual Studio.
Furthermore, msbuild throws tons of LNk2019 errors, complaining about unresolved SSL functions, i.e. "_SSL_CTX_get_ex_data".
I assume that CMake does not properly create the Visual Studio solution files and that the SSL libraries have to be added somewhere. Of course this could also be related to the windows OpenSSL distribution that I chose since I have no idea which is the correct one for cpp-netlib, as this is not discussed in the documentation.

philippludwig, your problem is not the same as the first post in this ticket. However, I do have some experience with your problem; it is a very common issue for tools relying on OpenSSL on Windows.
My preferred solution (there may be others):

Download the latest "non-Light" version of OpenSSL for Win32 from https://slproweb.com/products/Win32OpenSSL.html.
Download the latest "non-Light" version of OpenSSL for Win64 from the same site.
Install them both to different folders (I think the defaults are fine - one folder is named OpenSSL-Win32 and the other is named OpenSSL-Win64).
Add their 'includes' and 'libs' directories to your PATH (or to your Visual Studio defaults or whatever your preferred method is).

I currently am having the same issue as @stevenawright , installing the OpenSSL binaries did not help at all. It fails on building server_request_parsers_impl.cpp

So cpp-netlib 0.11.2 isn't built by default with C++11 -- you will have to build Boost and cpp-netlib in C++11 mode.

I had the same issue when #include "boost/network/protocol/http.hpp" in my code. I was referencing a successful build of cpp-netlib 0.12 by the way. I wonder do we have a solution yet? Thanks.

I don't get this -- the code should work just fine. I suspect since the project is being built with C++11 mode, it's trying to look for the conversion from an ASIO error code to a standard error code. The only way this will happen with Boost is if you build it in C++11 mode (and install it in C++11 mode). Now 0.11.2 doesn't default to being built with C++11 turned on, so you'd need to fix that when you build the cpp-netlib library. I don't know how to do this with MSVC, but it may need to be set when doing '-DCMAKE_CXX_FLAGS=' on the command-line when running CMake to generate the project.
If there's a flag similar to '-std=c++11' when building Boost or your project, you'd need to set it for all -- Boost, cpp-netlib, and your project. If you don't want C++11 features, you're going to need to explicitly disable C++11 mode from all these projects (or your whole solution).
Does that help?

I think this is caused by the project not including the files from the built-in asio library. It is looking for those asio files in boost, and it isn't going to find the ones it wants.
Make sure you are including 'cpp-netlib\deps\asio\asio\include' or something similar in your VC++ includes directory paths. Note that this path is not properly set by the CMake configuration right now.

@deanberris  It seems that MSVC (Visual Studio 15) doesn't need a flag to turn C++11 on. It is always in C++11 mode (well, welcome to MSVC...) see link here https://msdn.microsoft.com/en-us/library/fwkeyyhe.aspx
On the other hand, building with the -std=c++11 flag on Linux always works like a charm.
@MMOSimca  you are right. Actually, it darned on me that I could take a look at the example project (for instance http_client) that comes with the source to figure out the appropriate include and link directories. Indeed, the http_client project generated by cmake has 'cpp-netlib\deps\asio\asio\include among the project's include directories.
Anyway, I ended up including that director. The previous error about cannot convert errors went away, but now I got other conversion errors:
Error	C2664	'void std::_Func_class<_Ret,const boost::iterator_range<const boost::network::uri::uri::value_type *> &,const std::error_code &>::operator ()(const boost::iterator_range<const boost::network::uri::uri::value_type *> &,const std::error_code &) const': *cannot convert argument 1 from 'boost::iterator_range<std::_Array_const_iterator<_Ty,1024>>' to 'const boost::iterator_range<const boost::network::uri::uri::value_type > &'	hello_world_client
C:\foo\bar\cpp-netlib-0.12.0-final\boost\network\protocol\http\client\connection\async_normal.hpp	351
Building the http_client example gave me the same errors.
Any help is appreciated!

I am also facing same error mentioned in the above comment while building the the http_client example.
some other, related errors.
Error	C2664	'void std::_Func_class<_Ret,const boost::iterator_range<const boost::network::uri::uri::value_type *> &,const std::error_code &>::operator ()(const boost::iterator_range<const boost::network::uri::uri::value_type *> &,const std::error_code &) const': cannot convert argument 1 from 'boost::iterator_range<std::_Array_const_iterator<_Ty,1024>>' to 'const boost::iterator_range<const boost::network::uri::uri::value_type *> &'
Error	C2664	'std::basic_string<char,std::char_traits,std::allocator> &std::basic_string<char,std::char_traits,std::allocator>::append(std::_String_const_iterator<std::_String_val<std::_Simple_types>>,std::_String_const_iterator<std::_String_val<std::_Simple_types>>)': cannot convert argument 1 from 'std::_Array_iterator<_Ty,1024>' to 'const std::basic_string<char,std::char_traits,std::allocator> &'
Please help in resolving it.

@TapanGIT  FYI, I ended up using 0.11 version, which compiled just fine. I suspected it was because the MSVC's implementation of std library that caused the problem.

@ytong3 Could you please provide the information regarding the boost library version that has been used for compilation ?

@TapanGIT the latest boost_1_60_0 it was.

@ytong3 Thanks

Error while compiling rss_reader, Boost 1_60_0:
Error	C2664	'void std::_Func_class<_Ret,const boost::iterator_range<const boost::network::uri::uri::value_type *> &,const std::error_code &>::operator ()(const boost::iterator_range<const boost::network::uri::uri::value_type *> &,const std::error_code &) const': cannot convert argument 1 from 'boost::iterator_range<std::_Array_const_iterator<_Ty,1024>>' to 'const boost::iterator_range<const boost::network::uri::uri::value_type *> &'	rss_reader

I think I see what is happening here: the iterator type of the buffers we use internally don't match with those specified in the callback interface. VS2015 seems to be stricter here than all the other compilers we test with. It should be relatively straightforward to fix, but I don't have access to the VS2015 compiler.
Would anyone be willing to take this on, and to send in a PR?

@glynos https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ and https://www.visualstudio.com/en-us/downloads/download-visual-studio-vs.aspx

Thanks, @kiwidoggie. I am aware of it's availability, but I use Linux as my development environment.

I mean I can test a PR for you, but I also am on Linux (currently) and used the VM's for x-compiling with msvc.

@kiwidoggie -- can you try making a fix for this?

I'm having these exact same problems. cpp-netlib-0.12.0. Boost 1_60_0.
@glynos You can get VS2015 for free on Microsoft's page. It's right here: https://www.visualstudio.com/en-us/products/visual-studio-express-vs.aspx (I clicked on Download under "Express for Desktop").

@ytong3
Strange... Including that directory didn't help with the conversion error...

Forcefully converting boost::asio::error::netdb_errors to std::error_code
template<typename TEnum>
  std::error_code error(TEnum const& ec) {
      return std::make_error_code((std::errc)ec);
  }

seems to have fixed the type conversion error (which, admittedly, doesn't seem right) but new 12 errors came up complaining about the lack of operator== for std::error_category and boost::system_error_category, std::error_code and boost::asio::error::***_errors.
Would love to be able to use cpp-netlib on VS2015......

The changes involved to make this work I think are going to be really invasive.
FWIW, @glynos has made the latest in the master branch use the Boost.Asio library again (the experiment with stand-alone ASIO didn't quite work out in 0.12.0).
@JamesAMD -- if you can try using the latest in master, and work perhaps with @glynos to get some changes to make the library work in Windows, I would very much appreciate this. As it stands, I have no access to a Windows machine and I don't think I will have enough time to try and set one up just for cpp-netlib development.
That being said, I'd be happy to review pull requests to fix this.

What is the current status of this? Does the 0.13-release branch work?

cpp-netlib 0.13-release builds and tests succeed on MSVC 2015, so I will close this.


Add trace logging to List

This logging should help narrow down where time is being spent when doing list calls and a performance issue is being seen.

https://github.com/rancher/rancher/issues/28042