using initTLSSecret still provides the self-signed certificate

Trying to deploy a custom / official certificate
initTLSSecret:
  enabled: true
  secret: openldap-tls-secret

resource "kubernetes_secret" "cert" {
  metadata {
    name      = local.tls_secret_name
    namespace = module.hardened_namespace.namespace.id
  }
  binary_data = {
    "ca.crt" = "base64 censored"
    "tls.crt"  = "base64 censored"
    "tls.key" = var.tls_key
  }
}

It is deployed, checking the values looks good too

After re-deploying (fresh deployment) the chart, i still get greeted with the self-signed certifate.

Rubber ducked myself .. sorry, after tripple checking for this issue if found out its
initTLSSecret:
  tls_enabled: true
  secret: openldap-tls-secret

not
initTLSSecret:
  enabled: true
  secret: openldap-tls-secret

even though tls_enabled is fairly suprising (compared to all the others), still it is well documented - so my own fault for sure.


[INFRASTRUCTURE] - Testing Libraries

Can we use

Shouldly or FluentAssertions for assertion? It gives us a much cleaner and readability.   var expected = "expected";
   var actual = RunBusinessLogic();
   actual.ShouldBe(expected);

Faker for real-looking test data and AutoFixture for randomly generated data   var expected = Faker.Name.FirstName;

NSubstitute as a mocking library. Very easy to use for beginners.   var dependentService = Substitute.For<IService>();
   dependentService
         .SomeMethod()
         .ReturnsForAnyArgs("b");
   dependentService
         .SomeMethod2("abc")
         .Returns("b");
   dependentService
          .ReceivedWithAnyArgs(1)
          .SomeMethod3();
   dependentService
          .Received(1)
          .SomeMethod4("abc");

Personal preference

FluentAssertions
Moq

AutoFixture is great just tried it out in my tests. Saves alot of time rather than manually creating random objects. @StefH been using wiremock.net 💯. Great work. Autofixture + witemock makes simple acceptance tests. Couple of lines of code.

At this point of the project we will be using Moq and WireMock with FluentAssertions
We also use ObjectFiller - but I will research Faker with The Standard Community for future projects.
Closing this issue.


WebGL 2: 3D objects appear black

Godot version:
v3.1.alpha.official
OS/device including version:
Windows 10 64bit
AMD Radeon RX 580
Driver Packaging Version <IP_ADDRESS>-181010a-334550E-RadeonSoftwareAdrenalin
Issue description:
The shader breaks in exported html5 3D projects. It only displays black with the sky background. I didn't change any default settings except project name and starting scenes. The model was created in blender and exported with better collada. . Sprite3Ds also fail to show at all, but are completely transparent.
Everything seems to display correctly for a 2d scene
Here's an image of what I'm seeing.

The Chrome console outputs:

ERROR: SceneShaderGLES3: Fragment Program Compilation Failed:
put_char @ pbjs.js:7
pbjs.js:7 ERROR: 0:1555: '>' : wrong operand types - no operation '>' exists that takes a left-hand operand of type 'uniform highp float' and a right operand of type 'const int' (or there is no acceptable conversion)
put_char @ pbjs.js:7
pbjs.js:7
put_char @ pbjs.js:7
pbjs.js:7    At: drivers/gles3/shader_gles3.cpp:173:_display_error_with_code() - SceneShaderGLES3: Fragment Program Compilation Failed:
put_char @ pbjs.js:7
pbjs.js:7 ERROR: 0:1555: '>' : wrong operand types - no operation '>' exists that takes a left-hand operand of type 'uniform highp float' and a right operand of type 'const int' (or there is no acceptable conversion)
put_char @ pbjs.js:7
pbjs.js:7
put_char @ pbjs.js:7
pbjs.js:7 ERROR: SceneShaderGLES3: Fragment Program Compilation Failed:
put_char @ pbjs.js:7
pbjs.js:7 ERROR: 0:1555: '>' : wrong operand types - no operation '>' exists that takes a left-hand operand of type 'uniform highp float' and a right operand of type 'const int' (or there is no acceptable conversion)
put_char @ pbjs.js:7
pbjs.js:7
put_char @ pbjs.js:7
pbjs.js:7    At: drivers/gles3/shader_gles3.cpp:438:get_current_version() - SceneShaderGLES3: Fragment Program Compilation Failed:
put_char @ pbjs.js:7
pbjs.js:7 ERROR: 0:1555: '>' : wrong operand types - no operation '>' exists that takes a left-hand operand of type 'uniform highp float' and a right operand of type 'const int' (or there is no acceptable conversion)
put_char @ pbjs.js:7
pbjs.js:7
put_char @ pbjs.js:7
pbjs.js:7 ERROR: Method/Function Failed, returning: 0L
put_char @ pbjs.js:7
pbjs.js:7    At: drivers/gles3/shader_gles3.cpp:446:get_current_version() - Method/Function Failed, returning: 0L
put_char @ pbjs.js:7
pbjs.js:7 ERROR: Condition ' !version ' is true. returned: false
put_char @ pbjs.js:7
pbjs.js:7    At: drivers/gles3/shader_gles3.cpp:123:bind() - Condition ' !version ' is true. returned: false
put_char @ pbjs.js:7
pbjs.js:7 ERROR: Condition ' !version ' is true. returned: -1
put_char @ pbjs.js:7
pbjs.js:7    At: drivers/gles3/shader_gles3.h:380:_get_uniform() - Condition ' !version ' is true. returned: -1
put_char @ pbjs.js:7
pbjs.html:1 [.WebGL-00000215EA9D20C0]GL ERROR :GL_INVALID_OPERATION : glDrawElements: uniform buffers : no buffer bound at index 4
128WebGL: INVALID_OPERATION: drawElements: no valid shader program in use
127WebGL: INVALID_OPERATION: drawArrays: no valid shader program in use
pbjs.js:7 WebGL: too many errors, no more errors will be reported to the console for this context.

Steps to reproduce:
Just export any 3d scene with an OmniLight and a model in it exported with the Better Collada exporter
Minimal reproduction project:
pbjs.zip

Some materials/textures work and some don't;  panel.material displays while floor.material is full dark.
3DCube.zip
GLES2 and Firefox v62.0 64bit
Godot version:
Godot v3.1 Beta3
Lighting is odd, the side opposite the directional light vector is overly dark. Multiple directional or omni lights do affect the other dark sides. Ambient seems to have no effect.

With a rotating directional light

Seems the spatial mat for gles2 doesn't like Krita's PNG, all black, (tried different color profiles),  seems ok with Inkscape's PNG and Krita's TGA, lighting is still too dark.

This is working now, closing.


data-aos-delay greater than 3000

Hi there!
Just wanted to combine a sequence of animation but i can set a delay greater than 3000ms.
There is a way to set this values/limit heigher?
Thanks in advance.

Hey, you can generate all the needed delays based on this https://github.com/michalsnik/aos/blob/master/src/sass/_core.scss
By default I'm generating delays up to 3000ms in order to not make the styles too long, but you are free to extend it however you like :)

Thank you @michalsnik

To be very honest, I've faced the need to have larger number and not too much happy about the default setup too :(


BUG: Fixes issue with clang.

I encountered this while building SciPy with Spack using the Clang compiler.
scipy/special/_faddeeva.cxx:133:17: error: call to 'isnan' is ambiguous
            if (isnan(x))
                ^~~~~
/usr/include/bits/mathcalls.h:235:19: note: candidate function
__MATHDECL_1 (int,isnan,, (_Mdouble_ __value)) __attribute__ ((__const__));
                  ^
/usr/tce/packages/gcc/gcc-4.9.3/lib64/gcc/x86_64-unknown-linux-gnu/4.9.3/../../../../include/c++/4.9.3/cmath:622:3: note: candidate function
  isnan(double __x)

Thanks @corbett5 @person142


PHP Fatal Error – yii\base\ErrorException

What steps will reproduce the problem?
What is the expected result?
What do you get instead?
Additional info

Q
A

Yii version
2.0.9

PHP version
5.5

Operating system
centos

Call to undefined function yii\base\fnmatch()
in /path/to/vendor/yiisoft/yii2/base/ActionFilter.php
protected function isActive($action)
{
$id = $this->getActionId($action);
    if (empty($this->only)) {
        $onlyMatch = true;
    } else {
        $onlyMatch = false;
        foreach ($this->only as $pattern) {
            if (fnmatch($pattern, $id)) {
                $onlyMatch = true;
                break;
            }
        }
    }

I get the message from php document for fnmatch function :
For now, this function is not available on non-POSIX compliant systems except Windows.

centos

centos is not posix compliant? looks like its something wrong with your PHP setup.
See

https://github.com/yiisoft/yii2/issues/12408#issuecomment-243721437
http://unix.stackexchange.com/questions/305639/centos-6-7-and-fnmatch-in-php

i suggest to change  fnmatch to an anonymous like this
        foreach ($this->only as $pattern) {
			if (instanceof of \Closure) {
				$onlyMatch = call_user_func($pattern, $id);
				if ($onlyMatch) {
					break;
				}
			} else if ($pattern == $id){
				$onlyMatch = true;
				break;
			}
        }

and i think fnmatch should be replaced by other functions as it probably can lead to some errors, what do you think?

Hmm... based on what's written following @cebe links, it seems standard CentOS is OK.

If you are able to compile PHP yourself you seem to have enough permisson to configure the server yourself.


aiyprojects.withgoogle.com does not handle responsiveness correctly - hidden text

https://aiyprojects.withgoogle.com/voice/#google-assistant
I'm using this on Chrome 65.0.3325.181 on macOS 10.13.4.
When viewing this page under about 1690px wide text starts to get cut off - for example
/home/pi/AIY-projects-python/checkpoints/check_audio.py

I noticed this while doing the setup on my AIY Voice Kit.
Other text appears to wrap correctly when resizing the browser window.
It looks like this is probably due to the <pre> take used to wrap the <code> tag for styling - I don't have to tell you, since you're Google, but pre ignores CSS.

Removing the tag via browser inspector rendered the text exactly the same but with responsiveness.

Awesome! THank you so much for reporting this. Will fix soon


Add highlighting groups and udpate border chars

This looks very promising. I am using your fork branch for now - working exactly as expected:
local colors = {
  darkgray = "#3D3D3D",
}

vim.cmd(string.format("hi LazygitBorder guifg=%s guibg=none", colors.darkgray))

@kdheepak Do you mind giving a kind review, please?

Thanks for pinging! I’ll look at this this weekend!

Thanks for the PR!
I changed the option name to lazygit_floating_window_border_chars and added a deprecation for the old option. Otherwise it looks great!


[Authoring] Tags addition

Tags to be added for homepage, about-us, terms and condition, privacy policy so that it is trackable in search animation

Tags list:
Recipe tags are as follow:

Breakfast
Lunch
Dinner
Snacks
Dessert

Product tags:

Milk Powder
UHT Milk
Yoghurt
CalciYum

Tags are reflecting fine.


Lazy-load ActionView via ActiveSupport.on_load hook

Before this change, if awesome_print gem was bundled onto a Rails app, this line triggers all the ActionView related initialization process even in situations that ActionView is not actually needed (e.g. booting up the Rails console, executing a model test, running a Rake task, etc.) because referencing ActionView::Base constant immediately kicks :action_view load_hooks.
With this change,

In case of a non-Rails app that does not use ActiveSupport
Nothing happens.

An application that uses ActiveSupport but does not use ActionView
The registered :action_view on_load hook will never be executed.

An application that uses ActionView but doesn't have ActiveSupport constant
This never happens. actionview gem depends on activesupport gem.

A Rails app with ActionView
:action_view on_load hook will just be executed only when ActionView::Base is loaded by someone.

@imajes Awesome! Thanks :)


Added Typescript definition file

For importing and using in Typescript  / Angular / angular (2)

Not finished yet needs cleaning and some more actions to work out of the box


Select option list data-drop-height

In select option data-drop-height if we give a large number in some screens the list does not appear as accepted, it shows a small half line on top of the select control. You can test as data-drop-height=400 and change the zoom of the browser. It happens in Chrome or Android phones.

I can't influence how the browser zooms the page in any way


particle.io site rebrand

I couldn't find the Launch link on particle.io. The Build link seems to work though.

Yup. I'll need to go fix all the old Spark mentions. Thanks! :+1:


Adding statistical functions

Thank you for the fixes!

Added .stddev() and split stats.rs into mean.rs and stddev.rs for clarity.

Changes to stddev.rs for pooled SD. General cleanup.

Changes to stddev.rs for pooled SD. General cleanup.

Changes to stddev.rs for pooled SD. General cleanup.

Changes to stddev.rs for pooled SD. General cleanup.

Changes to stddev.rs for pooled SD. General cleanup.


error factory exceptions for generic errors

It would be nice to include generic exceptions, else users can only conditionally use exceptions classes on the basis of their existence without any clear guidance outside of trying each manually, and will accumulate as multiple error handling styles in a codebase.
>>> import boto3
>>> client = boto3.client('s3')
>>> client.exceptions.AccessDenied
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/kapilt/projects/cloud-custodian/lib/python3.6/site-packages/botocore/errorfactory.py", line 53, in __getattr__
    self, name, ', '.join(exception_cls_names)))
AttributeError: <botocore.errorfactory.S3Exceptions object at 0x108f2efd0> object has no attribute 'AccessDenied'. Valid exceptions are: BucketAlreadyExists, BucketAlreadyOwnedByYou, NoSuchBucket, NoSuchKey, NoSuchUpload, ObjectAlreadyInActiveTierError, ObjectNotInActiveTierError

as an easy alternative, exposing error factory off the client and allowing users to create/retrieve exceptions by code would be nice.

something like
except client.exceptions.for_code('AccessDenied'):
    pass

which would do a from_code for class cache lookup before constructing & caching.

Yeah I think something like that would be great! The downfall of what we have now is it is based off of the service models, which don't always define every exception. A solution like for_code would be cool.

Question, if AccessDenied is returned by S3, why isn't it part of the service definition?


Clarify use of phone and email from desktop client

In #18945 it was pointed out that information on how keybase uses phone numbers was lacking, or at least too difficult to find.  This was partially addressed by https://book.keybase.io/docs/chat/phones-and-emails, although that page is still too hard to find, given that

there are broken links to it (see https://github.com/keybase/book-content/issues/52),
it's buried in appendix D of the Book (which is confusingly named "Docs" - huh? isn't the Book the docs?)
it's not linked from the desktop client AFAICS:

Given that privacy is such a critical element of keybase, there should be a (How do we use your phone number?) link or similar right next to the text.

Oh this is interesting - I see a (broken) link from the client in Settings > Your account:

Filed as #24263.
Other than that, the main issue is that it's not linked from the notification in the People section as shown in the previous screenshot above.


Can't run tests

Hi,
I tried running pytest on Mac and Linux but on both I get this error :
==================================== ERRORS ====================================
__________________ ERROR collecting tests/test_trustchain.py ___________________
tests/test_trustchain.py:4: in
from src.trustchain import *
src/trustchain/init.py:1: in
from trustchain import *
src/trustchain/trustchain.py:1: in
import libnacl
/usr/local/lib/python2.7/dist-packages/libnacl/init.py:83: in
nacl = _get_nacl()
/usr/local/lib/python2.7/dist-packages/libnacl/init.py:81: in _get_nacl
raise OSError(msg)
E   OSError: Could not locate nacl lib, searched for libsodium.so, libsodium.so.18, libsodium.so.17, libsodium.so.13, libsodium.so.10, libsodium.so.5, libsodium.so.4,
!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!
=========================== 1 error in 0.41 seconds ============================
Have you an idea how to solve this issue ?
Best Regards,

Hi, you need to libsodium https://download.libsodium.org/doc/installation/, the crypto library in C. Most distributions should have it packaged.
On 15 February 2018 00:01:23 CET, KevinTAN52<EMAIL_ADDRESS>wrote:

Hi,
I tried running pytest on Mac and Linux but on both I get this error :
==================================== ERRORS
__________________ ERROR collecting tests/test_trustchain.py

tests/test_trustchain.py:4: in
from src.trustchain import *
src/trustchain/init.py:1: in
from trustchain import *
src/trustchain/trustchain.py:1: in
import libnacl
/usr/local/lib/python2.7/dist-packages/libnacl/init.py:83: in

nacl = _get_nacl()
/usr/local/lib/python2.7/dist-packages/libnacl/init.py:81: in
_get_nacl
raise OSError(msg)
E   OSError: Could not locate nacl lib, searched for libsodium.so,
libsodium.so.18, libsodium.so.17, libsodium.so.13, libsodium.so.10,
libsodium.so.5, libsodium.so.4,
!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection
!!!!!!!!!!!!!!!!!!!!
=========================== 1 error in 0.41 seconds
Have you an idea how to solve this issue ?
Best Regards,
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kc1212/checo/issues/10

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

It worked thanks !


Refactor: Move phase fractions to separate table (one line)

Could create some screen shots locally and show to PO for feedback.
One suggestion is to put it above the "MoleTable"

Suggestions:

Think that is fine. Perhaps a small spacer between the two tables?
Anyway ask if PO like it :)


metaprofile stop codon peak

Hello,
first of all I would like to say that the riboWaltz is a great package for ribo-seq and I really enjoy using it. I just want to clarify some features in metaprofile plot, specifically the stop codon part. Does the "0" on the plot corresponds to the last nucleotide of stop codon like on the attached picture? And the red line represents end of the CDS including the STOP codon?

Usually the stop codon is not considered as part of the CDS so it's a little bit confusing as the the "stop" peak is really strong in my data and it's "far" from the "stop" red line. As for the translation termination the p-site should not reach the stop codon I would expect the peak to be on the second codon to the last one, the last one to be STOP codon. In the manual you write that the p-sites are plotted on the leftmost position so it would make sense for me be as it is on the picture.
Thanks in advance!

Hi,
thank you for using riboWaltz.
You are right, the 0 correspond to (the beginning of) the last nucleotide of CDSs. This means the red line is the very end of the CDSs. I know the it might result a bit confusing, but I choose this notation and visualization for convenience in the writing of the code and for sake of consistency with the notation and visualization adopted for the start codon.
This means the peak above is on the second to last codon, the one before the stop codon. I'm not sure I fully understood your comments about what you would expect to see in the metaprofile: do we agree that if the 0 is the stop codon (and, as I said, it is) so the peak you observe is in the correct position? By the way, this is the reason why the psite function allows to use as reference codon the start codon or the second to last codon.
Please let me know if I answer to your question properly, dispelling your doubts. If not, I'll try to better explain this point.
Bests,
Fabio

Hi Fabio,
thanks for the prompt response. I got it now and it is exactly as I thought. Thanks for doing great work in this topic! I have other questions related to other functions of riboWaltz but I will submit it later as a new issue.
Thanks!
Best,
Jaro


support custom ca chain

In some deployments a self signed root CA is used to verify eg the certificate of S3. There are multiple ways to make ocis aware of one or more custom root CAs:

build a custom container to include the correct CA chain
set the SSL_CERT_DIR=/etc/ssl/certs env var and mount a certificate chain to eg. /etc/ssl/certs/custom.pem.

SSL_CERT_DIR will cause golang to read all certificates in that dir.

CA chain is already partly supported for eg. LDAP.
we need a clear strategy how to deal with this:

HTTP clients
Store / Caches
Message Bus
Office Integrations / WOPI
Email Server
Tika

So far we only have a option to switch of certificat validation.
Related:

https://github.com/owncloud/ocis-charts/issues/109

Workaround in https://github.com/owncloud/ocis-charts/issues/420#issue-1976482355

SSL_CERT_DIR is read by golang to pick up custom certificates. We can use it to make every pod containing a golang binary read a a custom CA.

@d7oc we need to prioritize this, because it is blocking currently @b1schumacher

@b1schumacher does @butonic - solution not work?
https://github.com/owncloud/ocis-charts/issues/420#issue-1976482355
If not, may I ask you to create a pull request to overcome this limitation?

The problem we are facing now, is that this is not just a S3 Problem but rather a global problem. We need the chain in every pod that needs to communicate with a service that is secured by the custom ca chain.

So basically all service definitions need to be extended by these 10 lines?

There are common templates for all services. There might be one which can be used so just the template is enhanced and you get all for free.

There are common templates for all services. There might be one which can be used so just the template is enhanced and you get all for free.

Does that mean we have a even faster implementation?

How do other Helm Charts solve this challenge? I'd always prefer to stick to practices that are also used by charts like bitnami / grafana.

Seems like Bitnami charts have something like this:
## TLS configuration
##
tls:
  ## @param tls.enabled Enable TLS traffic
  ##
  enabled: false
  ## @param tls.authClients Require clients to authenticate
  ##
  authClients: true
  ## @param tls.autoGenerated Enable autogenerated certificates
  ##
  autoGenerated: false
  ## @param tls.existingSecret The name of the existing secret that contains the TLS certificates
  ##
  existingSecret: ""
  ## @param tls.certificatesSecret DEPRECATED. Use existingSecret instead.
  ##
  certificatesSecret: ""
  ## @param tls.certFilename Certificate filename
  ##
  certFilename: ""
  ## @param tls.certKeyFilename Certificate Key filename
  ##
  certKeyFilename: ""
  ## @param tls.certCAFilename CA Certificate filename
  ##
  certCAFilename: ""
  ## @param tls.dhParamsFilename File containing DH params (in order to support DH based ciphers)
  ##
  dhParamsFilename: ""

(taken from Bitnami Redis Chart values.yaml)

My question is also if we will have on CA or allow to have multiple, since there might be systems managed by different parts of a organisation:

HTTP clients
Store / Caches
Message Bus
Office Integrations / WOPI
Email Server
Tika

(from https://github.com/owncloud/ocis-charts/issues/403#issuecomment-1754685982)

@wkloucek @d7oc
I made a pull request.
It is possible to add multiple ca chains to the secret and with that add them all to the deployments. This will also solve the problem with different chains for different services.

It is possible to add multiple ca chains to the secret and with that add them all to the deployments. This will also solve the problem with different chains for different services.

Will it continue to use the CA certificates shipped by the OS in the container?

Good point.
Right now this would overwrite the certificates, as all of them are already in /etc/ssl/certs
So there are to options.

Add another dir to SSL_CERT_DIR with the default /etc/ssl/certs, but would break with changed default paths from the container
Mount the CA chain as file, but then the key would have to be configured and only one would be possible

I owuld prefer option 2 with a good documentation and in future a option for multiple CA chains

I saw that one can provide multiple paths separated by :, see also ttps://golang.org/issue/35325

I implemented now a second path with the custom certificate and added the custom chain ca there. So now it should use both directories.

was solved in https://github.com/owncloud/ocis-charts/pull/599


playpen: clone: Operation not permitted

Using playpen on a Fedora Linux 24 system, I get playpen: clone: Operation not permitted when running repos/playpen/playpen -l -S ./torbrowser-syscalls .tor-home /dev/null

According to the documentation playpen must be run as root so I will close this ticket.


Cannot get Projects - is the Projects API implemented?

More info here:
http://stackoverflow.com/questions/42836937/github-api-octokat-js-cannot-get-projects

Dekuji za odeslani tohoto problemu!
The project API has not been added yet (maybe because it is a Preview API). If you were interested in adding it by submitting a Pull Request, it would require adding entries to these 3 files:

tree-options.js which allows you to type the .projects part of repo.projects.fetchAll()
url-validator.coffee validates the URL before making the request
preview-headers.coffee sends the proper preview header (application/vnd.github.inertia-preview+json) based on when the URL matches a certain regular expression

It seems that to fully implement the Project API these URLs would need to be matched in the 3 files listed above:

/projects/:id
/orgs/:org/projects
/repos/:owner/:repo/projects

Haha, now you got me confused: Are you Czech? 🤔
Anyway, there's also columns and cards that'd need to be implemented.


Fix bug running individual tests on master

References
Bug was discovered by @abollini in #2720 in this comment: https://github.com/DSpace/DSpace/pull/2720#pullrequestreview-399901564
Description
Currently, individual test classes (unit or integration tests) cannot be run as documented in our README.  They all throw the error:
[ERROR] Failed to execute goal on project dspace: Could not resolve dependencies for project org.dspace:dspace:pom:7.0-beta3-SNAPSHOT: Failure to find org.dspace:dspace-rest:jar:classes:7.0-beta3-SNAPSHOT

I've fixed the bug (which was related to the disabled, optional dspace-rest module) and updated our README instructions (which were also outdated)
Instructions for Reviewers
See updates to the README in this PR for how to run various individual tests.
One quick example is to try:
mvn test -Dtest=org.dspace.app.rest.AuthorityRestRepositoryIT -Dmaven.test.skip=false -DskipITs=false -DfailIfNoTests=false

@abollini : When you get a chance (next week is fine), could you give this a quick look?  It fixes the testing bug you mentioned in my other PR, and it should be very quick to test/review.


fix mujoco_v5 observation_space constructor typing issue

Description
fixes a type hint oversight
Type of change

[X] Type hint only change
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[ ] I have run the pre-commit checks with pre-commit run --all-files (see CONTRIBUTING.md instructions to set it up)
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Ok, let me elaborate on what happens,
with MuJoCo-v4 and older environments, the observation space was predefined in the environment class
but with MuJoCo-v5 the observation space is set based on the model used (which may be different from the default because of the xml_file argument), which in computed after the model is loaded
https://github.com/Farama-Foundation/Gymnasium/blob/219d1242e8eade5385d2ff909e9d7fe2028375c5/gymnasium/envs/mujoco/ant_v5.py#L303-L327


Class PostFormFields not found

UPDATE: The error below does NOT appear when installing Canvas through composer create-project cnvs/canvas. The error popped up for me when doing a git clone .... Perhaps this has to do with not releasing a tag for it yet?
When running the initial composer install in Canvas, the following error comes up:

Please run composer update instead.
composer install installs packages from composer.lock. easel is new, so lock file is outdated.
composer update reads the composer.json, downloads the latest packages according to requirements, and updates composer.lock.

Fixed with a5c7967b


Install within Docker & PNPM

Possible install-time or require-time problem
Should be install-time, but errors appears only after deployment.

[x] I have read and understood all of the documentation relating to installation.
[x] I have searched for known bugs relating to this problem in my choice of package manager.

You must confirm both of these before continuing.
Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of sharp that is not the latest,
please open an issue against that package instead.

[x] I am using Node.js with a version that satisfies ^18.17.0 || ^20.3.0 || >=21.0.0
[ ] I am using Deno
[ ] I am using Bun

If you cannot confirm any of these,
please upgrade to the latest version
and try again before opening an issue.
Are you using a supported package manager and installing optional dependencies?

[ ] I am using npm >= 9.6.5 with --include=optional
[ ] I am using yarn >= 3.2.0
[ ] I am using pnpm >= 7.1.0 with --no-optional=false
[ ] I am using Deno
[ ] I am using Bun

If you cannot confirm any of these, please upgrade to the latest version of your chosen package manager
and ensure you are allowing the installation of optional or multi-platform dependencies before opening an issue.
What is the complete error message, including the full stack trace?
Could not load the "sharp" module using the linuxmusl-x64 runtime
What is the complete output of running npm install --verbose --foreground-scripts sharp in an empty directory?
Haven't run, because it's in a server docker, not in a local machine.

Haven't run, because it's in a server docker, not in a local machine.
What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
Haven't run, because it's in a server docker, not in a local machine.
My question is: How can I use sharp within the Docker container and using pnpm package manager, but I do want to use -no-optional flag, so no other packages won't install any of theirs optional packages, but since Sharp require one of those, my application fails. How can I install correct binnary for sharp separately?
Either I should add correct binnary to the dependencies or I should install it globally?
Hope for your help.

I do want to use -no-optional flag, so no other packages won't install any of theirs optional packages

If you do not allow installation of optional dependences, you can add the @img/sharp-linux... package appropriate for your runtime environment as an explicit dependency in your own package.json file.
https://github.com/lovell/sharp/blob/55466f122cee94e97e94a114b8107e48a2cd13b5/package.json#L154-L159
You'll probably also want to pin to a specific version that matches the version of sharp.

You'll probably also want to pin to a specific version that matches the version of sharp.

That's what I thought, ok, Thank you for a quick response!

See also https://github.com/pnpm/pnpm/issues/7231


tools/seg_scannet200.py

Hi，thanks  for your great work. When I run the command:
python tools/seg_scannet200.py --run process_scannet --path_in <scannet_folder>  \        --path_out data/scanet200.npz  --align_axis  --scannet200
It seems that there is no seg_scannet200.py file. I guess it  should be " tools/seg_scannet.py " in the command.

Thank you so much for pointing out this issue. I have fixed it.


[Feature](schema change) Lightweight schema change of modify column with varchar length

Proposed changes
Issue Number: close #xxx
Problem summary
The original varchar schema change is to perform directly schema change when the length of varchar is inconsistent.

Because fe only allows users to increase varchar length, and increasing the length of varchar will not modify the format of the data, so only the metadata of the data file needs to be modified.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.41 seconds
stream load tsv:          477 seconds loaded<PHONE_NUMBER>9 Bytes, about 149 MB/s
stream load json:         38 seconds loaded<PHONE_NUMBER> Bytes, about 59 MB/s
stream load orc:          68 seconds loaded<PHONE_NUMBER> Bytes, about 15 MB/s
stream load parquet:          27 seconds loaded 861443392 Bytes, about 30 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230302144512_clickbench_pr_107453.html

run buildall

run p0

run buildall

run p0

run p0

run buildall

run buildall

run buildall

run buildall

run feut


[WFLY-16075] Upgrade WildFly Preview to Mojarra 3.0.2.SP01

https://issues.redhat.com/browse/WFLY-16075
Update jsf-impl version to 3.0.2.SP01

@jasondlee Could you add a revert of the test exclusions in b16d77a to this PR? That will validate the upgrade does what's expected.

I can do that. I believe that's how it was in 3.0.0.SP, so I left it as is. Have things regarding that changed recently? (Still trying to understand the current state of things ;)

The test exclusions I linked were a workaround to https://issues.redhat.com/browse/WFLY-16061 problem, but the fix I did that should be in 3.0.0.SP2 should remove the need for that workaround.

The test exclusions I linked were a workaround to https://issues.redhat.com/browse/WFLY-16061 problem, but the fix I did that should be in 3.0.0.SP2 should remove the need for that workaround.

Changes pushed.

Thanks, @jasondlee


ci: Bump lvh-kind ssh-startup-wait-retries

Recently, we frequently see the CI failure with lvh-kind startup failure with exit code 41. This indicates the timeout of the task waiting for the SSH startup. Bump the timeout (retry) to 600 (10min) as a workaround.
Fixes: #31336
ci: Bump lvh-kind ssh-startup-wait-retries

/test

Conformance Cluster Mesh: https://github.com/cilium/cilium/issues/30901


Support JSON in addition to YAML

Some people have hate in their hearts for YAML. It's really cheap for us to support JSON as well as YAML, since YAML can be converted to YAML. https://github.com/aaubry/YamlDotNet/wiki/Samples.ConvertYamlToJson
Additionally, JSON has better support for schema/intellisense
We could do this by making JSON the source of truth and then converting YAML to JSON (always)

since YAML can be converted to YAML.

I think you ment "since YAML can be converted to JSON".
And yes, would love json as the source of truth. But it's now 6 weeks after this issue, so i'm guessing this boat has sailed ... ⛵

No boats have sailed here! This project is just starting, and the last 6 weeks we honestly have been mostly working on documentation and paper cuts that people are running into, no major feature work besides core fundamentals (ex service discovery).

woot! and cheers @spboyer for the PR. Respect, mate 👍
Respect to the entire team, actually 👍

@rynowak @jkotalik - can we close? Did a spike on this with #355 and we didn't merge as YAML was the better choice moving forward.

I think @davidfowl will be really happy to see this closed.

😄

Ok - so summary/answer is: YAML config only. No JSON config support.
yes?


docs: add guide to use with Docker

This PR adds a Dockerfile and docs update to use docker image, which is up for public grab in docker hub (url) (didn't have time to make a README over there)
Tell me if you want write permissions on the Docker repo, or even moving it to GHCR in this repo

Supplement: This looks like another way to solve https://github.com/slidevjs/slidev/issues/63 (For peoples who already have the docker on theirs machine), and have the least code influence. By putting all dependencies in to the docker image, It seems that I can quickly start to write slides with only a single Markdown file by this command (But I still think install Slidev globally is better :D):
docker run -d -v /path/to/slides.md:/WORKING_DIR/slides.md -p  slidev@latest

Adding the docs / guides for using Docker would be good to have, thank you. However, I don't want to turn into this repo into a docker image source at this moment as I will not be able to maintain them either way. So maybe let's leave Dockerfile and entrypoint.sh for now and do the documentation only. Also kinda feel it's better to use npm to create the docker image as the main branch are not always stable. I wouldn't mind to point your repo and images in the docs atm. WDYT? Thanks.

Also kinda feel it's better to use npm to create the docker image as the main branch are not always stable

It already uses only npm to build, I even have a warning in the docs about this
This has never been what the Docker image is made for

I will not be able to maintain them either way

I will be able to maintain it without issue, I have a script running which uses gitpunch to auto rebuild at each releases on npm and push the docker image to hub

However, I don't want to turn this repo into a docker image source at this moment

Some people want to build their Docker images from source..., like i said I will be able to maintain it build-side.
And the files won't need any changes in the future (only maybe a version bump) it can stay "frozen" on this repo, everything happens build-side

Did a bit rephrasing. Thanks a lot on this!

I created a new docker image for dev & deploy slidev pages
Slidev Docker image
Work with Slidev. Just run following command in your work folder:
docker run --name slidev --rm -it \
    --user node \
    -v ${PWD}:/slidev \
    -p 3030:3030 \
    tangramor/slidev:latest

If your work folder is empty, it will generate an template slides.md and other related files under your work folder, and launch the server on port 3030.
You can access your slides from http://localhost:3030/
Build deployable image
Or you can create your own slidev project to a docker image with Dockerfile:
FROM tangramor/slidev:latest

ADD . /slidev

Create the docker image: docker build -t myppt .
And run the container: docker run --name myslides --rm --user node -p 3030:3030 myppt
You can visit your slids from http://localhost:3030/
Build hostable SPA (Single Page Application)
Run command docker exec -i slidev npx slidev build on the runing container slidev. It will generate static HTML files under dist folder.
You can host dist in a static web site such as Github pages or Gitlab pages. You can also host it by your self:
docker run --name myslides --rm -p 80:80 -v ${PWD}/dist:/usr/share/nginx/html nginx:alpine

Or create a static image with following Dockerfile:
FROM nginx:alpine

COPY dist /usr/share/nginx/html

Create the docker image: docker build -t mystaticppt .
And run the container: docker run --name myslides --rm -p 80:80 mystaticppt
You can visit your slids from http://localhost/


Relocate repository

We are ready to move this repository into the ESCOMP GitHub organization, as discussed previously. Let's do this when there are no open pull requests.

i'm ready to do this. How do we proceed?

Closing this, let's return to the actual work.


Editing message command is sent when it shouldn't be

Add an if statement to check if the messages are actually different

Fixed in v1.1.1


@tool annotation requires project reopen to start working

Godot version
4.0 master
System information
Windows 11
Issue description
The @tool annotation doesn't appear to take effect until the project is reopened.
Steps to reproduce
func _process(_delta):
  print("@tool working")

Create a Node
Attach above script
Add @tool annotation to script and save
Notice nothing happens
Close and reopen project
Notice flood of @tool working messages in output

Minimal reproduction project
N/A

You don't need to reopen project, reloading the scene should be enough.
Also the reason why this happens is that set_process() is called when node is ready, which happens only once. Hence reloading is needed. You could try with something that doesn't need enabling, e.g. NOTIFICATION_VISIBILITY_CHANGED.


Feat fingerprinting viewport

Two changes:

Changing viewPort to use innerWidth and innerHeight. When testing with this setup before the changes it was seen that the final outerWidth had this frameBorder applied twice resulting in a window size that was larger then the actual screen.
Adding a new dom override to also set available screen on window.screen, so it matches the behaviour of normal browsers.

Before:

After:

Good stuff. Thanks for contributing!!


Final Setup

Although not closely looked into the commits, overall looked great!!! have tested and worked like a charm!
Also had a look at your documentation, it's very comprehensive. Thanks @rnou112 !!
@PrasadBabarendaGamage, should we just merge this PR if you are happy too?


detect active form element more accurately

Note that I also moved the form element detection into a function for better readability and extension.

Oh, and I fixed the test case so that simulant loads correctly.

And finally, I added the event to the deck parent instead of each individually slide. This seems to be sufficient to override the event handler set by bespoke-keys.


Encode all path whether or not hasQueryParam

The prev pr only encoded paths with query parameters. But that was not nice because it confused us as whether a proxy created repo is encoded or not. This fix treat all proxy generated repo as base64 encoded.

LGTM.


Improve error message when virt-freezer fails on paused VM

What this PR does / why we need it:
As discussed in https://issues.redhat.com/browse/CNV-21659, this Pull Request updates the error message when virt-freezer fails on paused VMs so it's more descriptive.
Which issue(s) this PR fixes:
Fixes #
Release note:

NONE

/retest-required

/lgtm
Thanks :)

/retest-required

/retest-required

/lgtm

/approve

/retest-required

Backporting since this is a follow-up of a 4.13 tech-debt PR
/cherrypick release-0.59


Is this repo dead?

Been a long time now since any releases or changes. Anyone got a solid fork that's up to date and has all the PR'd fixes?

Doesn't seem worth wasting much more time on. Documentation is horrible. Good luck.

Hi @lcoursey  and @kaseychakos , sorry for the late reply. This repo hasn't been updated for few months due to shortage of resources. We have a plan to update this library this year including overhauling the documentation. Will keep you posted and sorry for the inconvenience.


Custom theme fixes

Replacement for #514 (whoops)
Few styling tweaks for the custom themes. Explicit warning icons, playlist subscription icons & text, slider buttons on the settings pages. Applied to dark-cyan and Rdiant where applicable.
Not sure how many of these are new from Google's recent update, and how many are lingering issues that haven't been noticed before now.

:+1: :shipit:


Add DEC/IDEC tensorflow implemenetation

This commit adds our re-implementation of DEC/IDEC on the MNIST dataset.

Forgot to add
if __name__ == "__main__":
    main()

to autoencoder.py; added


Cloud Firestore Support

All right, I've done the initial import of my experimental Cloud Firestore work. I also added an analysis.json as per the new rules for making iron-component-page work (not sure if that's the right way to go). Docs should show up properly on webcomponents.org, so that's nice.
@tjmonsi this is probably as far as I'm going to have time to take this in the immediate future. I'd be grateful for your help fleshing it out further.
Todo

[ ] Figure out if this can be ported to a behavior that is backwards compat with Polymer 1
[ ] Flesh out the demo to actually demonstrate some of the cool things about the implementation
[ ] Write tests

Fixes #274

Ok will work on it this coming week :)

@mbleigh @tjmonsi Any progress on this? Would love to see the final implementation in Polymerfire, the Firestore branch looks good so far!

@stemuk sorry, was just finished doing an event last weekend and was just finishing some backlogs I accumulated. Will work on this once I am free (hopefully this weekend)

@tjmonsi there are couple of issues I'd like to work on, especially:

Eliminating the initial lag caused by the use of get()  method when persistence is enabled (it always tries to get the latest data from the server). The best solution would be to make online-only behavior optional.
Updating only changed documents in collections instead of replacing entire arrays (eventually we could think of deep-diffing documents to notify only changed paths).
Fixing the bug in the implementation of an initial binding (properties might have their values assigned before connectedCallback is called)

I'd like to avoid wasting my or your's time on fixing the same issues twice, shall we split these ones or do you have sth else in mind to work on over the weekend?

@merlinnot I am still doing some backlogs so please do whatever you can. I think I am going to merge someone else's PR to the firestore branch. If it's alright, can you create an issue about the bugs that you have stated so that it's connected to the PR that you will merge to this.
My plans for this one is review the current version on how it plays with firestore and create a behavior for backwards comp, and elements firestore-query and firestore-document (still deciding). I would be changing the name of this one as well to be firestore-mixin so that it is more appropriate. Hopefully I can merge them all by the end of next week.

At the moment the firestore-mixin is a one-way-binding with firestore. Is it for firestore technically also possible to implement two-way-binding (just like firebase-document)?

@arcodebonte It is technically possible, but it is generally discouraged to do so. It's a nice feature to show off, but it's most often an anti-pattern.

@merlinnot thanks for setting up the issues :)

@merlinnot thanks for you response! Nice to hear that also the two-way-binding is possible. I agree that this binding must be used thoughful.
In some cases however I think this binding is useful. I use the two-way-binding in firebase-document for example to let the users adjust their settings. For this purpose the two-way-binding works good and it helps to keep the code clean and simple.

@arcodebonte Let us see what's the best way to do it.

On two-way binding -- I'm pretty against it, honestly. Firestore charges
based on doc reads and doc writes, whereas the Realtime Database charged
only based on transferred bandwidth. So updating one field at a time wasn't
a big deal in RTDB, but is in Firestore as you're triggering multiple
writes.
I'd be more interested in seeing demos of, for example, a "debounced save"
where changes are tracked and persisted after 500ms of inactivity, for
example.
On Fri, Oct 20, 2017 at 2:29 AM Toni-Jan Keith Monserrat <
<EMAIL_ADDRESS>wrote:

@arcodebonte https://github.com/arcodebonte Let us see what's the best
way to do it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/polymerfire/pull/278#issuecomment-338155786,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAD_ncQiKPRd_s7TM2z7jeQTOAQ0GtLks5suGf2gaJpZM4PxKeQ
.

@mbleigh I see your point as well. The auto 2-way binding will have bad consequences on every minuscule update. I also like your idea about a debounce of 500ms but I don't know 500ms enough. That would mean every short type burst of here and there would still create a significant number of writes instead of one good write.
It might take like a really complicated solution (like caching all edits first and then until a threshold has been reached (either by time that is longer or a change in location, then it auto-saves... but that's also too general)

Any chance we'll see a merge/release on these features sometime soon?

It might take like a really complicated solution (like caching all edits first and then until a threshold has been reached (either by time that is longer or a change in location, then it auto-saves... but that's also too general)

Has there been any progress on this question?
Using Polymer with the RTDB seemed to be the perfect fit for data binding that Polymer is facilitating - only we were missing querying functionalities. Now we gain querying but due to pricing we might need to implement some non-binding async save method.
Is there any chance of a general solution? So far I can only think of app specific ones. E.g. in my app the user can edit cards (it was supposed to be collaborative). I could think of saving if a card looses focus (or the browser window). Meaning for other users I have to disable the card for editing. But this will be totally different from other usecases.
Or will it mean to always have a mix? Like in my case, cardsets for live editing will be in Firebase RTDB and Firestore only used as parent database...
But then again, Firebase RTDB won't give support of chosing server regions (as demanded by many clients in Europe) as it is promised for Firestore. Still a bit lost with decisions here...

Hi @derhuebiii, welcome onboard, nice to see someone interested in this PR :)
There is actually some support for this. Given
static get properties() {
  return {
    someProp: {
      type: Array,
      collection: 'someFirestoreCollection',
    },
  };
}

a property named somePropRef is created which is a reference to the collection you've defined (literally the same one that is being used in the mixin). Tiny example:
async addSomeStuffToTheCollection() {
  return this.somePropRef.add({someStuff: true});
}

Both docs and collections have these properties, the Ref (note the capital letter) suffix is appended to the name of a property.

Thanks @merlinnot ! I will play around with this. Also thanks for creating this branch!
Might make sense to add this to the documentation. I am not so familiar with participating on github but after playing around, I might try to suggest some edit.

Actually it's not me who created this branch, it's @mbleigh.
Documentatio is a part of this PR, see https://github.com/firebase/polymerfire/pull/278/files#diff-ed26b76bc80e40b84633288e109db714R90

I'm finishing it up soon. You can see the progress here: https://github.com/firebase/polymerfire/issues/346


add a mongoose cheatsheet

I want to add a mongoose cheatsheet to this repo.
This cheatsheet would be helpful to all developers using MongoDB.

Sure go ahead


adds typescript def-file

In order to use the package with typescript, I added a typescript definition file.

Hi 👋
I released a new version of this module: 3.2.0. This change is there.
Thank you for your contribution ❤

Hi,
that's great. Do you need any other help with our lib?

@aFINKndreas Thanks for asking 👍
For now I think we are good :)


Scheduled transaction body missing

        TransferTransaction transaction = new TransferTransaction()
                .addHbarTransfer(newAccountId, Hbar.fromTinybars(-1))
                .addHbarTransfer(myAccountId, Hbar.fromTinybars(1));

        //Create a scheduled transaction
        ScheduleCreateTransaction scheduledTransaction = new ScheduleCreateTransaction()
                .setScheduledTransaction(transaction);
        System.out.println("The schedule transaction is " + scheduledTransaction);

output:
The scheduled transaction is # com.hedera.hashgraph.sdk.proto.TransactionBody. <--
transaction_fee: 500000000
transaction_valid_duration {
seconds: 120
}

You have to freeze the transaction, as that builds the body.

I have to freeze which transaction? The ScheduleCreateTransaction?

Hijacking issue, we should support printing the transaction even if it's not frozen.

Create Scheduled Transaction now supports printing even if it's not frozen.


ADB-Dedicated QA changes

ADB-Dedicated QA changes
Add here your WMS ID
11046, 11048, 11047
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[ ] All filenames are lower case (including folders, images, files, etc.)
[ ] Filenames are descriptive
[ ] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[ ] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[ ] Image references in markdown contain an alternate text

@klazarz Corrected GutHub URLS and LiveLabs URL in index.html.

@tejuscs - Could you update the PR with the WMS ID of the workshop?


ROS publisher for 3D Lidar

Hi, thanks for sharing the project. The TurtleBot Test sample works very well. A 2D lidar is used in the sample. I'd like to know the way to use the 3D lidar. I couldn't find the ROS publisher for the 3D lidar. Could you advise on this, please?
Thank you!

@nsrj we have not yet implemented a publisher for 3D LIDAR yet. When we do what would you consider to be the preferred ROS message for 3D LIDAR? PointCloud or PointCloud2?

@micahpearlman, thanks a lot for the reply. PointCloud2 is preferred. But PointCloud is also fine. I just need to do a conversion on my own.
Would you have a timeline for implementing the publisher for 3D lidar? I am looking forward to it.
Thank you again.

@nsrj I just implemented a first version of the PointCloud2 Publisher that will publish the XYZ components of the 3D LIDAR.  You can see an example in a new test scene: Scenes/ROSPointCloud2Publish_test.unity
NOTE:  Updating the ZeroSim package is not automagic in Unity for whatever reason.  You will want to do the: Go into the package manager, select "+" button, and then select Add Package From Git URL... and enter git@github.com:fsstudio-team/ZeroSimROSUnity.git again.  And the re-import the ZeroSim samples to get the above mentioned test scene.  The package version should be 0.1.9

@micahpearlman thanks a lot for your quick reply and updates on the project. I have run the ROSPointCloud2Publish_test.unity, the point cloud looks very good. Thank you for the great work!
I have a follow-up question. Would it be possible to launch rosbridge_tcp.launch natively on the command line instead of launching it in Docker? Could you advise on this, please? Thank you again.

@nsrj take a look at issue #3 regarding ROS Bridge.  Attached is the ZeroSIm ROS docker build file.
Dockerfile.txt

Reproducing catkin_ws can be some of the trickiest things about ROS and is why we have released a Docker. We have not gotten around to open sourcing the docker build files, but will do so soon. In the meantime see attached docker files. Probably the part that will fix your roslaunch rosbridge_server issue is that there is an issue with the latest ROS Bridge Suite. The creation of the ROS bridge module for ROS is done via:

# install ROS bridge from source
# NOTE:  there seems to be issues with ROS bridge > 1.11.10 so we use the specific branch
RUN git clone -b 0.11.10 --single-branch https://github.com/RobotWebTools/rosbridge_suite.git
RUN cp -R ./rosbridge_suite/rosbridge_suite $CATKIN_WS/src
RUN cp -R ./rosbridge_suite/rosbridge_library $CATKIN_WS/src
RUN cp -R ./rosbridge_suite/rosbridge_server $CATKIN_WS/src
RUN cp -R ./rosbridge_suite/rosbridge_msgs $CATKIN_WS/src
RUN cp -R ./rosbridge_suite/rosapi $CATKIN_WS/src
RUN rm -rf ./rosbridge_suite

Also, the launch files can be browsed in the ZeroSim docker via opneing a bash script and browsing through the /catkin_ws/src directory: docker exec -it my_zerosim_vnc_docker \ bash -c "source devel/setup.bash ; rosrun turtlebot3_teleop turtlebot3_teleop_key". Attached is the basic Unity editor launch file.

@micahpearlman, thank you for your reply.
I have 0.11.13 installed on my machine. By following your instruction, I downloaded 0.11.10 in the local workspace and catkin_make the package. After running "roslaunch rosbridge_server rosbridge_tcp.launch bson_only_mode:=true" on a terminal, and running "rostopic list" on another terminal, I could not see any topics from Unity. I have Ubuntu 20.04 and ROS-Noetic installed on the machine. I wonder if this is the problem.
Thanks a lot for your help!

ROS installation issue are notoriously difficult to debug. My only guess is somehow the wrong version of ROS Bridge is being used or there is a Noetic specific issue?  For ROS I always highly recommend using Dockers otherwise you can chase your tail. You may want to reach out to the person who reported #3 and see how they solved this issue? If you do find a solution please report back here!


Add a Footer with Social Media Links, Contact Information, and Terms and Conditions

As a part of improving the user experience and the overall design of the CabRental website, we need to add a footer section. This footer should include links to our social media profiles, contact information, and a link to our terms and conditions page.
Requirements:
Social Media Links:
Add icons/links for popular social media platforms (e.g., Facebook, Twitter, Instagram).
Ensure the links open in a new tab.
Contact Information:
Include an email address and a phone number for customer support.
Add a physical address if applicable.
Terms and Conditions:
Provide a link to the terms and conditions page.
Ensure the link is clearly labeled and easily accessible.
Design Specifications:
The footer should have a consistent design that aligns with the overall aesthetic of the website.
Use appropriate icons for social media links.
Ensure the footer is responsive and looks good on all devices.
Implementation Steps:
Create a new  element at the bottom of the main HTML file.
Add a container for the social media links using  tags and icon images.
Include a section for contact information using  tags.
Add a link to the terms and conditions page using an  tag.
Style the footer using CSS to match the website's design.
This enhancement will improve the website's usability by providing essential information and easy access to our social media profiles.

check the deployed project, this has already been worked upon


Renaming a linux machine does not change their "orb.local" name

Describe the bug
When a linux machine is renamed, the new name is not reflected in the orb.local domain, despite being shown in the orb GUI.
To Reproduce

Create a machine, you can use the name + orb.local to access it directly:

❯ orb create ubuntu:mantic
❯ ping ubuntu.orb.local
PING ubuntu.orb.local (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=64 time=0.663 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.979 ms
^C
--- ubuntu.orb.local ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.663/0.821/0.979/0.158 ms

After renaming, the new name does not work, but the old name still works:

❯ orb rename ubuntu mantic
❯ ping mantic.orb.local
^C
❯ ping ubuntu.orb.local
PING ubuntu.orb.local (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=64 time=1.087 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=1.059 ms

In the GUI, the new name is even shown:

Expected behavior
No response
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.5.1
Commit: 4cfac15e1080617c70eb163966e1cb2009dac1c2 (v1.5.1)
System info:
macOS: 14.3.1 (23D60)
CPU: arm64, 12 cores
CPU model: Apple M3 Pro
Model: Mac15,6
Memory: 18 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-04-09T17-26-09.184186Z.zip

Screenshots and additional context (optional)
Related to this is this feature request: https://github.com/orbstack/orbstack/issues/1121

Fixed for the next version.

Restarting the machine will fix it for now.

Released in v1.6.0 Canary 1.
To update to Canary: Settings > Update channel

Released in v1.6.0.
New: Truly fast container filesystems on macOS: 2–10x faster, within 75-95% of native


Physi cs

This pull request implements the PhysiCS protocol, which can now selected from the antidote config file.
The changes include:

making antidote's code more modular for being able to run all these protocols.
implemented writes and reads in parallel for the new interface (read_objects, update_objects). Before, there were only parallel reads for static transactions, i.e., when running the "clocksi_execute_tx" function of the old interface.

The changes in the code are significant, I can go through the changes with the reviewer to help.

My main suggestion is to be careful for duplicated code where you do the "if protocol type".  It seems that in many of these cases a lot of the code is duplicated, and sometimes it is just because of a minor structural difference.  Maybe try to unify the structures, or use new ones.  In the places where there are big differences it might help to separate out the code into different methods and add some comments about the differences to help the readability.
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-cf224960a5452d2886845b108ffa2a14R349
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-4389c408eafb563cc5be6435fa123ad1R644
Maybe make a define for this line since it is used a lot
Protocol when ((Protocol == gr) or (Protocol == clocksi))
The perform single item update was removed.  I guess this is ok since it wasn't very clean, but maybe it is worth creating an issue where you describe what is missing in terms of "non-transactional" operations and how/where they could be implemented cleanly.
There are some places where you removed comments about what the code was doing, I know the commenting isn't good as it is, but as we go we should try to improve them:
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-478fd85134cec43d44f0115a26d7a118L351
There are several removed tests:
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-2afce300e6253387a488fb922191614dL71
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-bf06b660c0c38ec49b7df377c5ad545bL37
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-11695bdc58f3891c1f98ae9153b08c9eL70

On Oct 10, 2016, at 05:22, tcrain<EMAIL_ADDRESS>wrote:
My main suggestion is to be careful for duplicated code where you do the "if protocol type". It seems that in many of these cases a lot of the code is duplicated, and sometimes it is just because of a minor structural difference. Maybe try to unify the structures, or use new ones. In the places where there are big differences it might help to separate out the code into different methods and add some comments about the differences to help the readability.
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-cf224960a5452d2886845b108ffa2a14R349 https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-cf224960a5452d2886845b108ffa2a14R349
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-4389c408eafb563cc5be6435fa123ad1R644 https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-4389c408eafb563cc5be6435fa123ad1R644sounds good, working on it.
Maybe make a define for this line since it is used a lot
Protocol when ((Protocol == gr) or (Protocol == clocksi))

Good idea, but can’t seem to find a way to do it. Do you know how?

The perform single item update was removed. I guess this is ok since it wasn't very clean, but maybe it is worth creating an issue where you describe what is missing in terms of "non-transactional" operations and how/where they could be implemented cleanly.
There are some places where you removed comments about what the code was doing, I know the commenting isn't good as it is, but as we go we should try to improve them:
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-478fd85134cec43d44f0115a26d7a118L351 https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-478fd85134cec43d44f0115a26d7a118L351This wasn’t on purpose. I made long iterations of changes on that part of the code, and maybe removed them by mistake. will re-add them. thanks for noticing.

There are several removed tests:
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-2afce300e6253387a488fb922191614dL71 https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-2afce300e6253387a488fb922191614dL71
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-bf06b660c0c38ec49b7df377c5ad545bL37 https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-bf06b660c0c38ec49b7df377c5ad545bL37
https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-11695bdc58f3891c1f98ae9153b08c9eL70 https://github.com/SyncFree/antidote/pull/223/files?diff=split#diff-11695bdc58f3891c1f98ae9153b08c9eL70Same here. Will look at these.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SyncFree/antidote/pull/223#issuecomment-252532661, or mute the thread https://github.com/notifications/unsubscribe-auth/ACdPQlOlTxQCafQP2Nrlr797U1f812qvks5qya-PgaJpZM4KPwDi.

Tests are failing on Travis:
multiple_dcs_SUITE:'-replicated_set_test/1-fun-13-' failed on line 401
Reason: assertEqual
physics_SUITE:'-physics_test_prepare/1-fun-7-' failed on line 323
Reason: assertEqual

Sorry, I can't make this code review. My laptop is totally overloaded with 3.000 lines of changes, it cannot display the review mode.
You have to split this commit in smaller subcommits.
Alternatively, you can try to convince @cmeiklejohn that this pull request is mergeable.
Not sure what works better for you.

Dialyzer does not pass:
_build/default/lib/antidote/src/clocksi_interactive_tx_coord_fsm.erl
127: Function init/1 has no local return
157: Function start_tx/2 has no local return
160: Function start_tx_internal/4 has no local return
167: Function create_transaction_record/6 has no local return
188: Record construction #transaction{transactional_protocol::'physics',server_pid::'undefined',txn_id::#tx_id{local_start_time::non_neg_integer(),server_pid::pid()},physics_read_metadata::#physics_read_metadata{}} violates the declared type of field server_pid::pid()
209: Record construction #transaction{snapshot_clock::non_neg_integer(),transactional_protocol::'clocksi' | 'gr',server_pid::'undefined',txn_id::#tx_id{local_start_time::non_neg_integer(),server_pid::pid()},physics_read_metadata::'undefined'} violates the declared type of field server_pid::pid() and physics_read_metadata::#physics_read_metadata{}
221: Function perform_singleitem_read/2 has no local return
_build/default/lib/antidote/src/clocksi_static_tx_coord_fsm.erl
101: Function init/1 has no local return
109: Function start_tx/2 has no local return
112: Function start_tx_internal/5 has no local return
_build/default/lib/antidote/src/clocksi_vnode.erl
730: Function filter_updates_per_key_clocksi_test/0 has no local return
741: Record construction #transaction{transactional_protocol::'clocksi',server_pid::'undefined',txn_id::'undefined',physics_read_metadata::'undefined'} violates the declared type of field server_pid::pid() and txn_id::'no_txn_inserting_from_log' | #tx_id{local_start_time::non_neg_integer(),server_pid::pid()} and physics_read_metadata::#physics_read_metadata{}
747: Function filter_updates_per_key_physics_test/0 has no local return
758: Record construction #transaction{transactional_protocol::'clocksi',server_pid::'undefined',txn_id::'undefined',physics_read_metadata::'undefined'} violates the declared type of field server_pid::pid() and txn_id::'no_txn_inserting_from_log' | #tx_id{local_start_time::non_neg_integer(),server_pid::pid()} and physics_read_metadata::#physics_read_metadata{}
build/default/lib/antidote/src/inter_dc_dep_vnode.erl
146: Record construction #transaction{server_pid::'undefined',txn_id::'undefined',physics_read_metadata::'undefined'} violates the declared type of field server_pid::pid() and txn_id::'no_txn_inserting_from_log' | #tx_id{local_start_time::non_neg_integer(),server_pid::pid()} and physics_read_metadata::#physics_read_metadata{}
148: The created fun has no local return
234: The created fun has no local return
236: Record construction #operation_payload{type::atom(),op_param::{'merge',} | {'update',_},dc_and_commit_time::{'undefined' | {atom(),tuple()},non_neg_integer()},txid::'undefined'} violates the declared type of field txid::#tx_id{local_start_time::non_neg_integer(),server_pid::pid()}
_build/default/lib/antidote/src/materializer_vnode.erl
728: Record construction #transaction{server_pid::'undefined',txn_id::'no_txn_inserting_from_log',physics_read_metadata::'undefined'} violates the declared type of field server_pid::pid() and physics_read_metadata::#physics_read_metadata{}

fixed.

On Oct 10, 2016, at 23:09, Annette Bieniusa<EMAIL_ADDRESS>wrote:
Dialyzer does not pass:
_build/default/lib/antidote/src/clocksi_interactive_tx_coord_fsm.erl
127: Function init/1 has no local return
157: Function start_tx/2 has no local return
160: Function start_tx_internal/4 has no local return
167: Function create_transaction_record/6 has no local return
188: Record construction #transaction{transactional_protocol::'physics',server_pid::'undefined',txn_id::#tx_id{local_start_time::non_neg_integer(),server_pid::pid()},physics_read_metadata::#physics_read_metadata{}} violates the declared type of field server_pid::pid()
209: Record construction #transaction{snapshot_clock::non_neg_integer(),transactional_protocol::'clocksi' | 'gr',server_pid::'undefined',txn_id::#tx_id{local_start_time::non_neg_integer(),server_pid::pid()},physics_read_metadata::'undefined'} violates the declared type of field server_pid::pid() and physics_read_metadata::#physics_read_metadata{}
221: Function perform_singleitem_read/2 has no local return
_build/default/lib/antidote/src/clocksi_static_tx_coord_fsm.erl
101: Function init/1 has no local return
109: Function start_tx/2 has no local return
112: Function start_tx_internal/5 has no local return
_build/default/lib/antidote/src/clocksi_vnode.erl
730: Function filter_updates_per_key_clocksi_test/0 has no local return
741: Record construction #transaction{transactional_protocol::'clocksi',server_pid::'undefined',txn_id::'undefined',physics_read_metadata::'undefined'} violates the declared type of field server_pid::pid() and txn_id::'no_txn_inserting_from_log' | #tx_id{local_start_time::non_neg_integer(),server_pid::pid()} and physics_read_metadata::#physics_read_metadata{}
747: Function filter_updates_per_key_physics_test/0 has no local return
758: Record construction #transaction{transactional_protocol::'clocksi',server_pid::'undefined',txn_id::'undefined',physics_read_metadata::'undefined'} violates the declared type of field server_pid::pid() and txn_id::'no_txn_inserting_from_log' | #tx_id{local_start_time::non_neg_integer(),server_pid::pid()} and physics_read_metadata::#physics_read_metadata{}
build/default/lib/antidote/src/inter_dc_dep_vnode.erl
146: Record construction #transaction{server_pid::'undefined',txn_id::'undefined',physics_read_metadata::'undefined'} violates the declared type of field server_pid::pid() and txn_id::'no_txn_inserting_from_log' | #tx_id{local_start_time::non_neg_integer(),server_pid::pid()} and physics_read_metadata::#physics_read_metadata{}
148: The created fun has no local return
234: The created fun has no local return
236: Record construction #operation_payload{type::atom(),op_param::{'merge',} | {'update',_},dc_and_commit_time::{'undefined' | {atom(),tuple()},non_neg_integer()},txid::'undefined'} violates the declared type of field txid::#tx_id{local_start_time::non_neg_integer(),server_pid::pid()}
_build/default/lib/antidote/src/materializer_vnode.erl
728: Record construction #transaction{server_pid::'undefined',txn_id::'no_txn_inserting_from_log',physics_read_metadata::'undefined'} violates the declared type of field server_pid::pid() and physics_read_metadata::#physics_read_metadata{}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SyncFree/antidote/pull/223#issuecomment-252746949, or mute the thread https://github.com/notifications/unsubscribe-auth/ACdPQvEfy8nHmDV4YEK3vPpG51M7LkTuks5qyqlygaJpZM4KPwDi.

On Oct 10, 2016, at 22:44, Annette Bieniusa<EMAIL_ADDRESS>wrote:
Sorry, I can't make this code review. My laptop is totally overloaded with 3.000 lines of changes, it cannot display the review mode.
You have to split this commit in smaller subcommits.
Alternatively, you can try to convince @cmeiklejohn https://github.com/cmeiklejohn that this pull request is mergeable.
Not sure what works better for you.

Hi, I agree the changes are too big. Here is what I propose:
I will make a full pass on the changes to:
-minimize the changes with master.
-add docs and comments.
-create more detailed issues and relate to them in the pr.
Then, we can arrange a skype to go through the chances together, so I explain your doubts while you review.
I think that would simplify things.
Do you think that would work?
Sorry again for the super large changes.

added explanation.

On Oct 10, 2016, at 22:40, Annette Bieniusa<EMAIL_ADDRESS>wrote:
@bieniusa commented on this pull request.
In include/antidote.hrl https://github.com/SyncFree/antidote/pull/223#pullrequestreview-3569918:

@@ -78,6 +79,9 @@
%% Frequency at which manager requests remote resources.
-define(TRANSFER_FREQ, 100). %in Milliseconds

+%% threshold time for physics static reads, in microseconds
This comment is not descriptive. What kind of threshold is this about??
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SyncFree/antidote/pull/223#pullrequestreview-3569918, or mute the thread https://github.com/notifications/unsubscribe-auth/ACdPQrUhxGEbqP5ipQREUo3tGM-AbOTgks5qyqK1gaJpZM4KPwDi.

added explanation.

On Oct 10, 2016, at 22:39, Annette Bieniusa<EMAIL_ADDRESS>wrote:
@bieniusa commented on this pull request.
In include/antidote.hrl https://github.com/SyncFree/antidote/pull/223#pullrequestreview-3569750:

@@ -15,6 +15,7 @@
-define(ZMQ_TIMEOUT, 5000).
-define(NUM_W, 2).
-define(NUM_R, 2).
+-define(GLOBAL_BUCKET, antidote_bucket).
What is this needed for? Comments please!

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SyncFree/antidote/pull/223#pullrequestreview-3569750, or mute the thread https://github.com/notifications/unsubscribe-auth/ACdPQu9p1OusiAg4UF2uFo3-H8t5LoDlks5qyqJ1gaJpZM4KPwDi.

Am 11.10.2016 um 11:59 schrieb Alejandro Zlatko Tomsic<EMAIL_ADDRESS>
On Oct 10, 2016, at 22:44, Annette Bieniusa<EMAIL_ADDRESS>wrote:
Sorry, I can't make this code review. My laptop is totally overloaded with 3.000 lines of changes, it cannot display the review mode.
You have to split this commit in smaller subcommits.
Alternatively, you can try to convince @cmeiklejohn https://github.com/cmeiklejohn that this pull request is mergeable.
Not sure what works better for you.

Hi, I agree the changes are too big. Here is what I propose:
I will make a full pass on the changes to:
-minimize the changes with master.
-add docs and comments.
-create more detailed issues and relate to them in the pr.
Then, we can arrange a skype to go through the chances together, so I explain your doubts while you review.
I think that would simplify things.
Do you think that would work?
Sorry again for the super large changes.

I cannot inspect the changes because my browser is overloaded when I open the github page which displays the code changes.
Can you please spit issues?
I would like to have one pull request for the renaming that is not related to Physics.
Then, for each other improvement (bug fix) a separate one.
Then one that is cleaning up (white space, comments).
Then one on the Physics protocol.
Besides, you should check the result of Travis - it still fails your branch.
Make sure that the changes you commit do not break the build, also reducing the number of commits might be helpful - you are currently flooding my mailbox, and it is difficult to understand which commits are addressing which issue.

This pull request is too difficult to merge and we can't do it.
There's a few problems here:

Your protocol is mixed in with existing improvements to the structure of the application.  That makes it very difficult to evaluate your protocol along with changes to the existing system.
It's still unclear how to properly test these changes.

I suggest the only way we can merge this is to reapply your changes to a fresh copy of master and break them down into protocol improvements, structural improvements, and introduction of the new PhysiCS protocol.

Ok, will do that.
Should I “delete” the existing PR?

On Oct 11, 2016, at 14:43, Christopher S. Meiklejohn<EMAIL_ADDRESS>wrote:
This pull request is too difficult to merge and we can't do it.
There's a few problems here:
Your protocol is mixed in with existing improvements to the structure of the application. That makes it very difficult to evaluate your protocol along with changes to the existing system.
It's still unclear how to properly test these changes.
I suggest the only way we can merge this is to reapply your changes to a fresh copy of master and break them down into protocol improvements, structural improvements, and introduction of the new PhysiCS protocol.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SyncFree/antidote/pull/223#issuecomment-252905891, or mute the thread https://github.com/notifications/unsubscribe-auth/ACdPQqiU0pYsr_Iy20Ewu7W67Z0WUZQnks5qy4RugaJpZM4KPwDi.

I've closed the pull request, will open smaller ones in the future.

The doc/ folder (that contains the doc/sample_test.erl file) is in the .gitignore file in master.
That’s why in my PR it seems like I removed it, while what happens is that its not being tracked.
I guess we need to keep it (and remove the folder from gitignore, right?

On Oct 11, 2016, at 15:17, Alejandro Z. Tomsic<EMAIL_ADDRESS>wrote:
Ok, will do that.
Should I “delete” the existing PR?

On Oct 11, 2016, at 14:43, Christopher S. Meiklejohn<EMAIL_ADDRESS>wrote:
This pull request is too difficult to merge and we can't do it.
There's a few problems here:
• Your protocol is mixed in with existing improvements to the structure of the application. That makes it very difficult to evaluate your protocol along with changes to the existing system.
• It's still unclear how to properly test these changes.
I suggest the only way we can merge this is to reapply your changes to a fresh copy of master and break them down into protocol improvements, structural improvements, and introduction of the new PhysiCS protocol.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Does anybody need this sample test? what is it good for?


[GSSOC'21] Find nodes at a distance k from root in Binary tree

Hi! I'm a GSSOC participant and would like to work on this using C++ .

I am a GSSOC'21 participant and I would really like to contribute to this algorithm in C++ with added comments ,test cases and time and space complexity . Looking forward to the contribution.

@OjusWiZard I have create a PR, please do take a look !


Fixed Console aware module doc (PSR-2)

@jessertaylor Thanks for the contribution!
We've separated documentation into the individual components at this time. Could you re-do this against the zend-mvc repository instead, please?

I had a look through that but I eventually found the corssponding documentation in zend-console
Looks like it has already been fixed.
Thanks @weierophinney


startDate and endDate not on a month boundary?

Hi there,
For my current project I'm using endDate as Date() (i.e. whatever today is - currently April 1), and startDate as 2 weeks before endDate. I'm noticing that the calendar getting generated starts on March 1 even though startDate is somewhere in mid-March and generateInDates is set to .off. Wondering if this is expected behavior? Are startDate and endDate intended to be month boundaries, or is it possible to generate a calendar that starts mid-month?
Below is my configureCalendar function:
func configureCalendar(_ calendar: JTAppleCalendarView) -> ConfigurationParameters {
        let endDate = Date()
        let startDate = endDate.subtract(2.weeks)

        let parameters = ConfigurationParameters(startDate: startDate,
              endDate: endDate,
             numberOfRows: 2,
            calendar: Calendar.current,
            generateInDates: .off,
            generateOutDates: .tillEndOfGrid,
            firstDayOfWeek: .sunday)

        return parameters
    }

Yes, it is meant to be month boundaries.
If you want to restrict boundaries you can check the visibility of the cell you do not wish to cross, and then simply scroll back.

Thanks for the reply. Can I ask what you mean by "check the visibility of the cell you do not wish to cross, and then simply scroll back"? Do you mean to hide the cells (e.g. isHidden = true or alpha = 0)? I'm confused about the "scroll back" part.

You know when you make a mental note to respond, and then forget to respond?
My bad.
I'll will provide an example for how you can do this over this weekend.

Much appreciated!

Here is an example of implementing a boundary on a 6-row calendar.
With this code, the user is not allowed to cross the month of august.
Override this function in your viewController
func scrollDidEndDecelerating(for calendar: JTAppleCalendarView) {
    let visibleDates = calendarView.visibleDates()
    let dateWeShouldNotCross = formatter.date(from: "2017 08 07")!
    let dateToScrollBackTo = formatter.date(from: "2017 07 03")!
    if visibleDates.monthDates.contains (where: {$0 >= dateWeShouldNotCross}) {
        calendarView.scrollToDate(dateToScrollBackTo)
        return
    }
}

Cool, thank you!

I have error:

Binary operator '>=' cannot be applied to operands of type '(date: Date, indexPath: IndexPath)' and 'Date'

@zhanswift what did you do to get that error?

@zhanswift ok. which version of the calendar are you using?

Thank you. Already solved.