samba-ad-dc: unclear usage

it isn't clear how to use the samba-ad-dc image. I tried provisioning a domain and while it works, on restarts it reprovisions because it's part of the command line.
I ended up trying with volumes for /etc and /var which I used during the provisioning phase and then running another container without the provisioning command but with the same volumes and while it does skip the provisioning part and logs the same as the provisioning container does after provisioning (daemon 'samba': starting process, : /usr/sbin/krb5kdc: Stash file (null) uses DEPRECATED enctype !, WERR_DNS_ERROR_RECORD_ALREADY_EXISTS which all also appear after provisioning is done), it still doesn't work, setting a windows computer's DNS to the IP address of my openSUSE microos installation where I'm running the container and trying to join fails with windows not finding the domain

seems I had to provision with --net=host because it would use a random hostname and point the records to internal unresolvable 10...* IP address. I think both --net=host and --cap-add SYS_ADMIN should be on the README.md AND on entrypoint.sh's usage. maybe not --net=host if there's a better working way


Fixing bug with getSessionAndUser using an incorrect sk value.

This PR fixes a bug where getSessionAndUser on both DynamoDBAdapter1 and DynamoDBAdapter2 are not successfully retrieving the user. Following is an explanation.
The setSession methods are doing this
[this.pk]: `USER#${databaseSession.userId}`,
[this.sk]: `SESSION#${databaseSession.id}`,

However in the getSessionAndUser function, when retrieving the user, the following is used
[this.pk]: { S: `USER#${session.userId}` },
[this.sk]: { S: `USER#${session.userId}` },

when it should be using
[this.pk]: { S: `USER#${session.userId}` },
[this.sk]: { S: `SESSION#${session.id}` },

Hi @erikrj , I believe this is not a bug: say a user has an id of alice and a session has an id of 1, then the primary keys are:
For the user:
{
  pk: 'USER#alice',
  sk: 'USER#alice'
}

For the session:
{
  pk: 'USER#alice',
  sk: 'SESSION#1'
}

Users and the sessions that belong to them have the same pk values, so that all sessions for a certain user can be easily read (this is very useful for the getUserSessions method).
If using
[this.pk]: { S: `USER#${session.userId}` },
[this.sk]: { S: `SESSION#${session.id}` },

for the primary key, you will get the session record, which does not necessary contain the user's information.
PS: you can run the tests to verify this. If you have docker desktop available, you can run the tests with docker compose run --rm app npm run test.
I'm really glad to see your feedback. Please let me know your thoughts.

Thanks. I misunderstood how users were being retrieved with Lucia.


Fixed parsing of ARRAY literals in PostgreSQL simple query mode

Summary of the changes / Why this improves CrateDB
When using the simple query mode with the pg protocol, array literals are passed to the server as string literals, e.g. '{"1", "2"}'. This commit adds special logic for the simple query mode, it tries to parse any string literal using PGArrayParser first.
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

@mfussenegger I've forgot to push the CHANGES entry, done now.


Split test files

Coverage increased (+0.0007%) to 99.594% when pulling a301f4949aa7b1613467bd6e4fa2d10563eefc45 on split-test-files into 88a55f38beadd817f39e0ab2ef2be861bf38f6c4 on master.


feat(code): add custom validators for account configs

Added logic to add custom validators for configuration tab.
This PR fixes #520 issue.

Updated the docs and smoke tests as well.

I tried the change on the one of the recent add-ons that I worked upon.


Drop util.dot in favor of np.dot

This change requires numba >=0.23 and fixes #89.

This new feature does not work on Python 3.3. Time to drop it! :wave:

Current coverage is 83.13%

Merging #100 into master will decrease coverage by -0.20% as of bc9e9a9

@@            master    #100   diff @@
======================================
  Files           19      19
  Stmts          696     688     -8
  Branches        57      56     -1
  Methods          0       0
======================================
- Hit            580     572     -8
  Partial         18      18
  Missed          98      98

Review entire Coverage Diff as of bc9e9a9

Powered by Codecov. Updated on successful CI builds.


Fix CVE-2018-16489

Caused by a deprecated dev-dependency Istanbul

Coverage remained the same at 100.0% when pulling 6bc6b0d6ea1feb3aa350c3c5f64e54938f062d2f on Fix-CVE-2018-16489 into 36c3ff130d98a75179be46a505b1486a0cc468ca on master.

Coverage remained the same at 100.0% when pulling 6bc6b0d6ea1feb3aa350c3c5f64e54938f062d2f on Fix-CVE-2018-16489 into 36c3ff130d98a75179be46a505b1486a0cc468ca on master.

Coverage remained the same at 100.0% when pulling 6bc6b0d6ea1feb3aa350c3c5f64e54938f062d2f on Fix-CVE-2018-16489 into 36c3ff130d98a75179be46a505b1486a0cc468ca on master.

Coverage remained the same at 100.0% when pulling 6bc6b0d6ea1feb3aa350c3c5f64e54938f062d2f on Fix-CVE-2018-16489 into 36c3ff130d98a75179be46a505b1486a0cc468ca on master.

Coverage remained the same at 100.0% when pulling 6bc6b0d6ea1feb3aa350c3c5f64e54938f062d2f on Fix-CVE-2018-16489 into 36c3ff130d98a75179be46a505b1486a0cc468ca on master.


The mkdocs renderer doesn't like two spaces for second level bullets.

Coverage remained the same at 100.0% when pulling 6212a959f46dc222dce29c16d5fff65788388768 on jeremiahsmall:documentation into 051dfcc89635a36785e0c28c24b3f21842c437f1 on DASPRiD:master.

Coverage remained the same at 100.0% when pulling 7ea2652501bb47af5a59d7428e7565e1b4068057 on jeremiahsmall:documentation into 051dfcc89635a36785e0c28c24b3f21842c437f1 on DASPRiD:master.


cannot read year of null in DateTime.calcMinMax

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
On Android 5 when I'm trying to open datepicker I see:
TypeError: Cannot read property year of null DateTime.calcMinMax

Expected behavior:
No exception. datepicker is shown
Steps to reproduce:
pass non-empty non date value in max input of ion-datetime component
Other information:
date time util sometimes can return null (https://github.com/driftyco/ionic/blob/master/src/util/datetime-util.ts#L197) but DateTime doesn't handle this https://github.com/driftyco/ionic/blob/master/src/components/datetime/datetime.ts#L761
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.3
Ionic CLI Version: 2.1.18
Ionic App Lib Version: 2.1.9
ios-deploy version: 1.9.0
ios-sim version: 5.0.8
OS: OS X El Capitan
Node Version: v6.2.1
Xcode version: Xcode 8.2.1 Build version 8C1002

Hi there. Can you please provide some example code for use to test against? Something we can copy/paste and get the error. thanks

@mhartington the simplest reproduction is when somebody accidentaly pass date object into max or min inputs: http://plnkr.co/edit/qlWl7J?p=preview

In that example, you're using a javascript Date, but looking at the datetime docs, it needs an ISO formate date.
http://ionicframework.com/docs/v2/api/components/datetime/DateTime/#datetime-data
http://plnkr.co/edit/WQF3VyEL3nIQbdcNt2xf?p=preview
You're feeding it something that it is not designed handle.

Shouldn't it tell me where I'm wrong instead of failing with runtime exception? The logic may be a bit more complicated and min/max can be determined in runtime as well

max format YYYY/MM/DD fixed issue for me ex. max="2020-10-31" see http://ionicframework.com/docs/api/components/datetime/DateTime/#datetime-data

i fixed the issue by this method (for restricting the date that can be selectable to todays date)
wrote the below code in constructor
this.date=new Date();
this.maxSelectabledate=this.formatDate(this.date);
code for format date
formatDate(date) {
var d = new Date(date),
month = '' + (d.getMonth() + 1),
day = '' + d.getDate(),
year = d.getFullYear();
        if (month.length < 2) month = '0' + month;
        if (day.length < 2) day = '0' + day;

        return [year, month, day].join('-');
    }

in the html
use displayFormat="YYYY-MM-DD"  [max]="maxSelectabledate" in the

Yes, worked for me but why ionic has made it so hard to use simple date picker?


Allow to change verbosity level of the langserver

We can't specify if we want a quit, v, vv or vvv mode for the phpactor client. We should probably see how it can be done.

Can you elaborate? How is this relating to the coc-phpactor extension?

It is related because coc-phpactor is responsible to launch the phpactor langserver (through the command phpactor language-server), so adding an argument or option (here -vvv for example) should be done on coc-phpactor extension side.
It is useful when the langserver crashes, as having <date> INFO (pid:<pid>) [language-client-index] - Language server "phpactor" started with <pid> in :CocInfo isn't quite useful after a coc error phpactor server crashed 5 times in the last 3 minutes. The server will not be restarted, don't you think ? It could allow us to have more details when looking up what went wrong.

Agree increased verbosity can be useful for seeing the stack trace etc, so happy to include a verbosity setting.
But Phpactor would show the error at least when it crasehs. Does CocCommand workspace.showOutput give the same output as :CocInfo ?

I wasn't the one on who that crashed (just converted someone to phpactor :tada:). will keep that in mind next time. :}
(His problem was that indexing the vendor directory took too much memory, as he has a memory_limit on his php cli config...)

develop improves that a bit - it now shows how much memory is being consumed in the indexing progress notification.

Also if the kernel is killing the process, there's nothing interesting to see

Wouldn't we have at least a "tried to allocate ..." on the indexing ?

oh maybe - I've just been seeing loits of Process killed messages recently due to memory :smile:


Support Python 3

What does this PR do?
Add support for Python 3 to zookeeper integration
Motivation
Efforts to support both Python2 and 3 for all integrations.
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[ ] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
[ ] If PR adds a configuration option, it has been added to the configuration file.

Additional Notes
Anything else we should know when reviewing?

Codecov Report

Merging #2781 into master will decrease coverage by 3.32%.
The diff coverage is 90.9%.

@@            Coverage Diff             @@
##           master    #2781      +/-   ##
==========================================
- Coverage   84.67%   81.35%   -3.33%
==========================================
  Files         655        5     -650
  Lines       37469      295   -37174
  Branches     4518       42    -4476
==========================================
- Hits        31728      240   -31488
+ Misses       4417       36    -4381
+ Partials     1324       19    -1305


Binary Files cannot be uploaded to S3 if using AWS authentication

Expected Behavior
Binary files should be uploadable to S3
Actual Behavior
AWS authentication not supported for provided body type comes as a response in preview
Reproduction Steps

New Request
Enter the URL with the file you want to upload like: https://<endpoint>/<bucket>/<filename>
In the file section/dropdown, select Binary File inside Other and select the file you want to upload (anything non-text, example JAR, JKS, EXE)
In the Auth section/dropdown, select AWS and enter your AWS related details (access, secret keys etc)
Change request type to PUT
Hit Send

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
Binary files should be uploadable to S3, because other REST Clients like Postman and Thunder Client Extension in VSCode allow to upload binary files without any issue
Insomnia Version
2023.2.2
What operating system are you using?
macOS
Operating System Version
Ventura
Installation method
Website
Last Known Working Insomnia version
No response

I ran into the same issue. Any ideas how to solve this?

No, unfortunately not.
It doesn't seem like the Insomnia team are actively looking at any issues on this repo..

Same issue!

I get the "AWS authentication not supported for provided body type" error even if I want to upload a text file with content-type "text/plain". The same content can be uploaded when I copy it into the body field in Insomnia as "Plain Text".


Where is actual source code of ghidra?

I don't found actual source code of ghidra.
Where I can see?

Check out https://github.com/NationalSecurityAgency/ghidra/wiki/Frequently-asked-questions#where-is-the-complete-ghidra-source-code

See also: https://github.com/kelseyhightower/nocode (sorry can't resist).


Image Warp function may return incorrect results.

See https://community.leapmotion.com/t/orion-image-warp-in-c-giving-wrong-results/5211

Does the LeapC code not match the code that is being used for the C++ plugin?
I recall also having issues with the values that warp function was outputting a few months ago
Is this a front-end team issue?

LeapC doesn't do the wrapping and the code in the C++ uses data that isn't, as far as I know, available from LeapC. The LeapC# code used by Unity does bilinear interpolation, so it is a different algorithm. The results should be equivalent, though not pixel-per-pixel the same.
If warping the entire image, you would want to use a shader, but for stereo-triangulating a few points per frame, warp() should work.
So yes, it is a front-end-team issue.

This is addressed in platform PR #6161
The warp() function used the left distortion map for both images (it was never updated when we changed to a stacked image/distortion buffer format). I also changed it so that the function took a ray input like it did in the other language bindings and added a WarpPixel function that takes a pixel coordinate.


Server return 400 error

I get "Server return 400 error" when trying to download a workshop item on Ubuntu 16.04
Running the command: ./workshop.py 680631864

Hi @Mooticus sorry for the late answer.
The reason you get the 400 error is that 680631864 is not a collection but an addon.
As said in the readme of the script:
"
Add only a plugin
No, you can't and I don't want to implement it. Create a collection, your players will thank you if you have more than one plugin. If you only have one plugin, one day you will use many so create a collection.
"
Anyway, the curl command to download you plugin is :
curl -0 http://images.akamai.steamusercontent.com/ugc/48734286214157446/89FF0DBC6563745F6CD70EB0FE548A9F265FA641/ > 313949717.vpk


fix(backend): allow excluding soft-deleted entities in relationship-queries; exclude soft-deleted members of groups

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Summary by CodeRabbit

New Features

Enhanced GraphQL API to include an includeSoftDelete parameter for filtering relationships, allowing users to specify if soft-deleted entities should be included in query results.
Updated input structure for relationship queries to support more nuanced data retrieval.

Bug Fixes

Improved the filtering logic for entity existence checks to be case-insensitive, ensuring greater robustness in the identification of entities.

Tests

Added comprehensive unit tests to validate the behavior of the EntityRelationshipsResultResolver and the exists method, enhancing overall test coverage.

Also, can you add the same parameter and apply the same filter to the EntityWithLineage.lineage graphql query. So that means adding includeSoftDelete to LineageInput and updating EntityLineageResultResolver to apply the same filter. Thanks!

@anshbansal can we schedule work for the above changes? (request from John)


Made LibLog PCL compatible. Related to issue #9.

Thanks for the great work on this project! I've found it really useful.
I needed PCL compatibility for a project at work. I've made a few changes for this.

#define PORTABLE omits the GetCurrentClassLogger() method from the PCL version because this uses StackFrame, which is not available. This is commented out by default.
No longer references System.Diagnostics.TraceEventType directly. Uses reflection instead.
No longer references System.Console directly. Uses reflection instead.
No longer references System.ConsoleColor directly. Uses reflection instead.

Please let me know if you think this is a sensible method of achieving PCL support.
It could make it smoother for nuget consumers if there were two versions of the file in the package.

One with #define PORTABLE included for portable targets
One with #define PORTABLE omitted for .NET targets

This is beyond what I needed though!

Merged, thank you @ZachBray

this also needs to change https://github.com/damianh/LibLog/blob/master/src/LibLog/LibLog.nuspec#L31

Will look at that next...

@ZachBray Which PCL profile for which your changes worked for you?

We're using it with Profile 344.

Profile 344 (.NET 4.5, Windows 8.0, Windows Phone Silverlight 8.0, Silverlight 5, Windows Phone 8.1)
-- http://danrigby.com/2014/04/16/xamarin-pcl-profile-notes/

I have the nuspec setup as thus: https://github.com/damianh/LibLog/blob/master/src/LibLog/LibLog.nuspec#L33
But for some reason the file is not being transformed and added to the PCL project.
Any ideas?

I seem to fixed it by dropping the platform target altogether.
3.0.0 beta 3 is on nuget. Would appreciate if you took it for a spin.
One minor change, instead of uncommenting // #define PORTABLE my guidance will to be add LIBLOG_PORTABLE to your project's conditional compilation symbols. Modifying files added via a source package will result in complications when upgrading.


Deployment never ends if explicitly specified lambda role doesn't exist

Deployment never ends if there is a lambda role specified in up.json and that role doesn't exist. There is no indication what it's doing unless verbose mode is enabled. Verbose mode produces never ending stream of DEBU waiting for role to be created messages. It should fail immediately in such cases.

ah the creation is eventually consistent so that can be an issue, but it should at least time out

I think that if role is specified then deployment should fail immediately since up is not going to create it anyway, so nothing to wait.

Yeah that sounds reasonable to me


--version is unrecognized in az 2.0.41

Running this command:
az vm image list -l eastus --publisher "RedHat" --offer "RHEL" --sku "7.3" --version "7.3.2017090105" --all
I get this response:
az: error: unrecognized arguments: --version 7.3.2017090105

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

ID: 90dfc804-87d6-913a-27fe-a9446a04eb13
Version Independent ID: bfcb97df-2055-9eca-7a93-60811136d8cd
Content: az vm image
Content Source: src/command_modules/azure-cli-vm/azure/cli/command_modules/vm/_help.py
Service: virtual-machines
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

--version is not an argument for that command. I don't see anything in the docs referenced that suggest that it is. Were you following a blog or other document?

I just figured out that it was supposed to be "show" not "list":
az vm image show -l eastus --publisher "RedHat" --offer "RHEL" --sku "7.3" --version "7.3.2017090105"
Sorry about that. Thanks for the quick response.


Unexpose secret key

Obtain secret key from a heroku config var.
Use the current one as a default for local installs.
Update deployment in readme.

Fixed in 2c413a919e88fc3139f82096717c8f82f95d320c


KAFKA-4345: Run decktape test for each pull request

As of now the ducktape tests that we have for kafka are not run for pull request. We can run these test using travis-ci. Here is a sample run:
https://travis-ci.org/raghavgautam/kafka/builds/170574293

Requesting @harshach to review.

Thanks @raghavgautam . I'll go over it.

@raghavgautam does all of the tests pass and do we need to ask for any infra changes for this to run?

@harshach
We can run these tests in two way, locally on the laptop and on travis-ci.

On my laptop I was able to get 138 out of 149 to pass
On travis-ci I was able to run only 124 tests(timeout issues) out of these 88 passed. The failures seem to be timing related.
https://travis-ci.org/raghavgautam/kafka/builds/171502069
For the enabling travis-ci, we need community consensus and I will start a discussion for this.

I have disabled failing splits.
https://travis-ci.org/raghavgautam/kafka/builds/174369515

+1.

@raghavgautam can you upmerge this patch. I'll merge it in today.

@harshach I have rebased my pull request

Thanks @raghavgautam . Merged into trunk. Did you open a infra ticket for this.

I think it's great to be able to run the system tests in Travis. However, I don't understand why we added the gradle wrapper? It's the wrong version (we are using Gradle 3.2) and it was an intentional decision to remove it some time ago. Also, the system test renames are a bit arbitrary and they make it harder to use in the normal case, which is a point that Ewen had raised in the mailing list discussion.

Cc @ewencp

tests/cluster_file.json should also probably be under tests/travis/ since it is highly specific to that configuration. It'd also generally be a good idea to run a test using the existing implementation when there's this much movement under these tests to make sure everything still works (and that there are the expected number of tests -- one of the easiest things to break when moving things around is that some things get lost in directories without proper __init__.py files and become unimportable).

Also, trunk doesn't build since we're missing various licenses in files that don't pass the rat check...
:rat
Unknown license: /Users/ewencp/kafka.git/gradle/wrapper/gradle-wrapper.properties
Unknown license: /Users/ewencp/kafka.git/tests/kafkatest/tests/client1/__init__.py
Unknown license: /Users/ewencp/kafka.git/tests/kafkatest/tests/core1/__init__.py
Unknown license: /Users/ewencp/kafka.git/tests/kafkatest/tests/mirror_maker/__init__.py
Unknown license: /Users/ewencp/kafka.git/tests/kafkatest/tests/replication/__init__.py
Unknown license: /Users/ewencp/kafka.git/tests/kafkatest/tests/security1/__init__.py
Unknown license: /Users/ewencp/kafka.git/tests/kafkatest/tests/security2/__init__.py
Unknown license: /Users/ewencp/kafka.git/tests/kafkatest/tests/upgrade/__init__.py
Unknown license: /Users/ewencp/kafka.git/tests/travis/ssh/id_rsa
Unknown license: /Users/ewencp/kafka.git/tests/travis/ssh/id_rsa.pub

@ewencp I will open a pull request for the rat issue asap and will open jira's for rest of the issues.

@raghavgautam Sorry, should have posted here, I filed https://github.com/apache/kafka/pull/2172 already, which also removes the gradle wrapper and gets things setup in Travis via the travis.yml. See discussion there about whether we want to incrementally sort this out or just back out the change and re-file the PR so we can work on it until we've addressed the concerns previously mentioned.

@ewencp I too filed https://issues.apache.org/jira/browse/KAFKA-4448 and started working on it.

@harshach Thoughts on reverting this given some of the issues raised vs trying to clean things up with follow up commits?


1485 footer link active state

Summary of the changes
This ticket fixes the footer link active state, it was previously quickly flashing a border when active- this behaviour was different to the IcLink. Now the IcFooterLink is aligned with the IcLink.
Related issue
#1485
Checklist

[ ] Relevant unit tests and visual regression tests added.
[ ] Visual testing against Figma component specification completed.
[ ] All acceptance criteria reviewed and met.
[ ] Accessibility Insights FastPass performed.
[ ] A11y unit test added and yields no issues.
[ ] A11y plug-in on Storybook yields no issues.
[ ] Manual screen reader testing performed using NVDA and VoiceOver.
[ ] Page can be zoomed to 400% with no loss of content.
[ ] Screen magnifier used with no issues.
[ ] Text resized to 200% with no loss of content.
[ ] Text spacing increased as per the WCAG 1.4.12 success criterion with no loss of content.
[ ] Browser setting 'prefers reduced motion' tested. No animations or motion visible whilst this setting is on.
[ ] Windows High Contrast mode tested with no loss of content.
[ ] System light and dark mode tested with no loss of content.
[ ] Manual keyboard testing for keyboard controls and logical focus order.
[ ] Min/max content examples tested with no loss of content or overflow.
[ ] Browser support tested (Chrome, Safari, Firefox and Edge).
[ ] Correct roles used and ARIA attributes used correctly where required.
[ ] Logical heading structure is maintained, and the HTML elements used for headings can be changed to fit within the wider page structure.
[ ] All prop combinations work without issue.
[ ] Changes to docs package checked and committed.
[ ] Tested for FOUC (Flash of Unstyled Content) in both SSR (Server-Side Rendering) and SSG (Static Site Generation) settings.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.9 out of 10 committers have signed the CLA.:white_check_mark: GCHQ-Developer-741:white_check_mark: ad9242:white_check_mark: gd2910:white_check_mark: MI6-255:white_check_mark: GCHQ-Developer-112:white_check_mark: GCHQ-Developer-299:white_check_mark: GCHQ-Developer-530:white_check_mark: jd239:white_check_mark: zxh722:x: mmb675You have signed the CLA already but the status is still pending? Let us recheck it.


Comparison to twox-hash?

Would be helpful to mention in readme how this is different from twox-hash. Is it faster? Is it easier to use? Or just an alternative implementation?

I didn't do proper benchmarks, only some for my own reference.
twox-hash uses older implementation as basis so it lacks proper xxh3 implementation.
In addition to that it doesn't provide one-shot version of hashing algorithm which tends to be times faster than streaming one.
In general xxhash-rust closely matches to original C implementation in terms of performance, although there can be some minor performance degradations which I didn't really investigate.
So to answer concrete questions:

Is it faster?

Generally speaking yes (albeit in streaming variants of xxh64 you only gain marginal improvement)

Is it easier to use?

Hashing functions are pretty trivial to use in general.
xxhash-rust provides more options though as I implemented one-shot algorithm which is just single function call instead of using Hash trait

Or just an alternative implementation?

It is just implementation of xxhash algorithm.
But it is not just alternative because it provides you with const fn variants of all algorithms

it doesn't provide one-shot version of hashing algorithm

Looks like it does:
https://github.com/shepmaster/twox-hash/blob/b312df680851a11be7d77ecd07615b9f86cd383c/src/xxh3.rs#L44

Ah my bad, for some reason I thought it doesn't.
Well then there is that

I'm interested in comparison benchmarks between the two crates.

@firasuke The only algorithm that is worth benchmarking is xxh3, which is not available in its latest version for twox-hash so there is really not much to benchmark

@DoumanAsh Thanks for the reply, and no worries!
I already switched to xxhash-rust as it felt more minimal and had XXH3_128bits working like a charm.

The only algorithm that is worth benchmarking is xxh3,

I'm not super familiar with xxh3 (or xxhash in general). I want a good hashing function for data integrity - potentially to replace CRC32. Why xxh3?

In first place CRC32 is not intended as general purpose hashing function so I can only suggest to use xxhash if you need non-cryptographic hashing function.
xxh3 should be your choice due to improved performance comparing to older hashing functions in xxh family.
you might consider xxh32 on platforms where you lack 64bit integers or even 32bit integers

Yeah; I'm just throwing a checksum at the end of a new binary file format (for CRDTs) for the sake of detecting silent data corruption. CRC32c is probably fine, but if xxhash would be a better choice, then nows the time to make that decision. xxh3 looks good on paper, but I'm also targetting wasm where code size matters. And xxh32 adds much less code size compared to xxh3. A 32 bit checksum is plenty for what I'm using it for.
But if xxh3 is "the future" then I'm worried that xxh32 might stay niche and not be widely implemented going forward? Stability & portability is very important. O_o I have no idea what the best call is here.

xxh32/xxh64 are good for code size I suppose, but if you want something akin to checksum you need to reduce potential for collisions
Only xxh3 with 128bit variant allows it (128bit is wide enough for collisions to be non-existing in case of xxh3 while 64bit variant has some small chance of collision), I do not think xxh3 code is all that big honestly, not to mention I specifically designed library to enable/disable specific algorithms.
Considering your purpose is to use hash as checksum, I believe xxh3 with 128bit variant is the best option.
Hash is not inherently designed to be used as checksum, but as long as collisions are non-existing it should work for your case
See wiki of xxhash original implementation
https://github.com/Cyan4973/xxHash/wiki/Collision-ratio-comparison#testing-128-bit-hashes-=

Thanks! I've spent a lot of time tweaking compilation flags. My CRDT library is ~250kb, and I'm keeping a careful eye on it because I want it to get smaller, not bigger.
In theory TCP / filesystems should keep data consistent anyway. The checksum is really mostly there out of paranoia. Years ago I read that checksums fail in practice (even in situations they shouldn't) much more often than you expect. So I'm a bit curious to see if / when my checksums start failing.
CRDT patches get tiny sometimes since we send one patch per keystroke. A 128 bit hash would make sense for a 1mb file or something, but when I'm sending 20 bytes of patch content, adding 16 bytes of 128-bit xxh3 hash seems excessive.
I'll stick with crc32c for now. Thanks for humoring me! I really appreciate it!

Ah I understand, in this case yeah the best is to choose between xxh32 and crc32.
Unfortunately I'm not really familiar with their collision rates, both should have problem like that due to 32bit not being enough for perfect hash, but which is worse.... that's unclear to me.
So yeah sticking to crc32 is probably fine since it was designed for checksums rather than general purpose hashes


Handling SQL IP address issue

I have a customer who is facing issue with SQL instances without IP addresses, trying to handle this unusual case.

Thanks for your feedback, your solution is cleaner!
I updated the PR.


Is there no easy way of editing a template that saves forever?

Going to the json files and adding the text doesn't work? You need to fully close both explorer and Powershell

Found this way to "edit" a template and "saving" it forever

Thank you Cyber! That is a bummer that it doesn't re-fill it. Perhaps caching is too hard? When I get some time, ill try to see if this can be persisted.


[8.0] Remove Utils::defaultCaBundle

Depends on #2700. Follow-up to #2562.

Whoops, all my PRs seem to have become detached after I accidentally deleted my fork instead of a different one. I still have all my code locally, but it looks like I will need to re-create all the PRs. 😆


OAuth Token authentication

Looks good overall. Can you squash the commits to just one?

done

Some test coverage so you can merge this with some confidence

👍


Update http_authenticator.py

Error calling variables. They are prefixed with "auth" while they are not created with that prefix.

This was probably intriduced here #12 : cd7aae1
Thanks for fixing it!


Create a Calendar

Create the default template for the calendar so we can view it on the skeleton website and add to it later. Maybe a weekly view or a monthly view.

Tutorial on how to make a calendar for the website https://derrickotte.medium.com/how-to-create-a-calendar-from-scratch-in-react-1f2db197454d


TypeScript: Go to definition fails to work in Visual Studio 2015

This issue was logged on the TypeScript project: Microsoft/TypeScript#1210.
But turns out to be an NTVS issue. See https://github.com/Microsoft/TypeScript/issues/1210#issuecomment-67249740

Thanks, I'll close the duplicate Codeplex issue. We're focusing on VS2015 for our next milestone, so this issue will definitely make the cut :-)

According to the linked thread, this only occurs when you are working with two projects, and there is a dot in the filepath.
The problem isn't exactly in the open document code, but rather that the VS item id is not set properly in this scenario unless the document is opened first.
Is this the only time F12 is not working?

@mousetraps, yes, the F12 fails when there's a dot in the file path, but works correctly otherwise.
The F12 only fails to work in NTVS projects. We also have plain TypeScript project, and they don't have this problem.

Working together with TS team to resolve this sometime after BUILD. The issue occurs in the OpenDocument code, but it is the arguments passed in that are problematic, not the code itself. One possibility is that TS is making some assumptions about the Project System that do not apply to NTVS, which results in OpenItem being passed an invalid projectHierarchy and vsitemid.

@mousetraps, is this included in the May release?

It is not - still investigating, and we pushed it back to the July milestone because it appeared to be a very isolated scenario that would take a lot of time to root cause the first time I played around with it. I may have found a simpler repro now, though, so we'll see...

@mousetraps, thanks for looking into it.

@mousetraps,

it appeared to be a very isolated scenario that would take a lot of time to root cause

We've been working without F12 on NTVS projects for quite a while now and I feel rather aggrieved that nothing is being done about this.

Just verified that this is fixed in the latest version of TypeScript 1.5 and NodeTools 1.1 RC, both of which should be released around VS 2015 RTM.

This looks to be fixed. Thanks!

changing the tabs option from "keep tabs" to "insert spaces" solves the issue. Why?!

@Daskul Did you reply to the right issue? Can you clarify?

Yup. I got the solution from this link. https://social.msdn.microsoft.com/Forums/vstudio/en-US/3a331ad9-4217-480b-a299-62587d22b1db/visual-studio-2015-go-to-definition-is-not-working-on-referenced-assemblies?forum=visualstudiogeneral

@Daskul that issue doesn't seem related to the node tools. It seems to be limited to C#/VB and reference assemblies.

Oops sorry!  :) I'll just delete my comments

How do i remove typescript from visual studio 2015 as it is driving me crazy with this cannot navigate to caret issue. I do not use typescript and just want it off so I can continue working productively.

@Taztoons  unfortunately you cannot remove TypeScript, however if you don't use TypeScript is shouldn't interfere with your work. What is this 'navigate to caret' issue you mention? Can you open a new bug to explain your issue?


Disable TLS certificate checking in "execAPI"

Attempting to use your reddit package, I was running into "certificate has unknown CA" errors, which led me here. This implements the suggestion linked by @snoyberg in the first response.
Possibly not wise to make this change directly, as I'm sure many users are quite happy having their certificates checked, but it ought to be an option somewhere along the line -- e.g. via an execAPI', maybe taking a ManagerSettings argument rather than simply asserting a default.

reddit now has a runRedditWith function that takes a set of options and runs the action with those settings


Add read/subscribe event function for darwin

This change adds "read/subscribe event" function for darwin.
Problem
darwin matter framework is supporting API to subscribe all events but there is no way to read/subscribe only some selected events. Controller needs read/subscribe methods for the selected events to avoid performance issues happening when it subscribe all events.
Changes

read-event-by-id/subscribe-event-by-id commands are added in darwin-framework-tool for test:

./darwin-framework-tool interactive start
>>> doorlock read-event-by-id 1 1 1
>>> switch subscribe-event-by-id 4 1 100 1 1

readEventsWithEndpointID and subscribeToEventsWithEndpointID APIs are added in MTRBaseDevice.h of matter framework for app development:

(void)readEventsWithEndpointID:(NSNumber * _Nullable)endpointID
                     clusterID:(NSNumber * _Nullable)clusterID
                       eventID:(NSNumber * _Nullable)eventID
                        params:(MTRReadParams * _Nullable)params
                         queue:(dispatch_queue_t)queue
                    completion:(MTRDeviceResponseHandler)completion

(void)subscribeToEventsWithEndpointID:(NSNumber * _Nullable)endpointID
                            clusterID:(NSNumber * _Nullable)clusterID
                              eventID:(NSNumber * _Nullable)eventID
                               params:(MTRSubscribeParams * _Nullable)params
                                queue:(dispatch_queue_t)queue
                        reportHandler:(MTRDeviceResponseHandler)reportHandler
              subscriptionEstablished:(MTRSubscriptionEstablishedHandler _Nullable)subscriptionEstablished

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

Also, note the memory leaks this is introducing (hence some of the CI failures).

I removed all discovery and ethernet pairing changes because they are useful for test but not a mandatory feature for Matter certification. I updated the commit and description to focus on "read event" function needed for Matter Certification of controller app.

@seokhee-lee You should probably also fix the restyle issues, so this will request reviews more widely...

@seokhee-lee If you check restyle, you can use below script.
./scripts/helpers/restyle-diff.sh

@seokhee-lee
If you look at your modifications, the zap file modifications are included.
In this case, the item "ZAP/ZAP templates generation (pull_request)" will not fail until the zap file is recreated.

@seokhee-lee If you look at your modifications, the zap file modifications are included. In this case, the item "ZAP/ZAP templates generation (pull_request)" will not fail until the zap file is recreated.

@joonhaengHeo I will commit Commands.h generated by the changed zapt file after fixing restyle error of it. Could you guide how to generate file with zapt without restyle error? I fixed the restyle errors except the auto-generated file and the restyling tool is not working for the file for now because it seems to have too many changes.

@seokhee-lee Don't you check the restyle for files created using zap?

@joonhaengHeo I uploaded the generated file after restyling. There is no restyling error but zap templates generation error does not disappear. Could you let me know what I should do more?

@joonhaengHeo I uploaded the generated file after restyling. There is no restyling error but zap templates generation error does not disappear. Could you let me know what I should do more?

I fixed the zap-related issue. I did not know that the output location of zap-cli affects the generated file's formate.

@ready2die4u I am sorry I did not get to this review yet...  I will make sure I do that on Tuesday (Monday is a holiday in the US).

@ready2die4u @joonhaengHeo I feel bad asking you to hurry after it took me so long to get to the review, but if we can iron out the final few bits and get this merged in the next few days that would make it much more likely that it appears in a system Matter.framework in the near future.
One thing that I suspect we do need here that I still don't see, by the way, is tests for the new code...

@ready2die4u @joonhaengHeo I feel bad asking you to hurry after it took me so long to get to the review, but if we can iron out the final few bits and get this merged in the next few days that would make it much more likely that it appears in a system Matter.framework in the near future.
One thing that I suspect we do need here that I still don't see, by the way, is tests for the new code...

@bzbarsky-apple , I thank you for the reviews and sorry for the late reply because there was big holiday (New Year's Day in lunar calendar) in Korea. We will update the patches by tomorrow according to your reviews. We are testing the codes with darwin-framework-tool described in the commit message and our controller iOS app. In addition, all commands of darwin-framework-tool are being tested to guarantee that our codes do not cause any side effects to the existing codes. If we need more works to verify our code changes, please let me know.

@seokhee-lee I totally understand about the holiday!
In addition to the manual tests, these APIs need automated tests (see existing tests in MTRDeviceTests.m for examples).   That can be a follow-up PR as long as it happens.

I'm sorry for delay. I have changed it as shown below:

Modified the documents about API and renamed the property
Modified the allocator of SubscribeEvent class for 'Any' cluster to  add subscribe-event-by-id to commands.

I will prepare a follow-up PR for automated tests.

Fast-tracking platform-specific change with platform owner review.

@joonhaengHeo @ready2die4u Thank you again for your patience, and sorry this took so long!
I filed https://github.com/project-chip/connectedhomeip/issues/24666 to track adding automated tests for these APIs.

@joonhaengHeo @ready2die4u Thank you again for your patience, and sorry this took so long!
I filed #24666 to track adding automated tests for these APIs.

@bzbarsky-apple I thank you for your effort to review and merge the changes. I will commit the automated test patches soon.


Removed typing imports for standard collections

Refer to https://github.com/mrexodia/dumpulator/pull/47#issuecomment-1442835660

After discussing the change, we decided not to make these changes until Python 3.9's end of life is reached (scheduled for October 2025).


How can I present new data for training?

Hi, I was analyzing the data under  PhaseNet/dataset/waveform_train
For that purpose I just focus my attention to the file data_reader.py and I used the class DataReader_train.
So my first step was open the npz files under the dataset folder and I want to see how the event looks like.
Then when I use the DataReader_train class and I want to see how you class interact with the data I saw this.

So, anyone knows how can I present new data for training?

Hi, you can prepare new training data using the numpy.savez command. And you can follow the same format as the demo npz data. SeisBench also has more tutorials on model training: https://colab.research.google.com/github/seisbench/seisbench/blob/main/examples/03a_training_phasenet.ipynb


Run time very long for large data set

I tested a larger 16S/18S data set and it was taking a very long time to run even the first PCA replicate (hadn't finished after about an hour). The original 16S data set was 7K observations of 131 variables and 18S was 10K observations, while this new set was about 67K observations with 473 variables (25K observations for 18S).
Is there any way to add a multithreading option at least for the PCA calculations?

For clarity: the PCA itself took over an hour to run?
The base PCA function (prcomp()) doesn't have multithreading capabilities. I'm not certain there are parallelizable components of a PCA. If this is really an issue, we may have to find another solution like subsampling for the PCA.
How was the data set larger? More ASVs, samples, or both?

I tried again and took a closer look; it seems like it's the Bayesian model that is actually taking a long time, not the PCA itself (see attached screnshot).

The larger data sets had more of both: 67K ASVs in 473 samples for 16S (vs 7K ASVs in 131 samples) and 25K ASVs vs 10K ASVs for 18S.

Phew! That's expected.
I'm working on a different project, parts of which have similar Bayesian model components to this one. They both use the Bernoulli (0/1) switches which I couldn't find a way to code in STAN which is considerably faster. Luckily, I've found someone who knows how to do it and he'll be walking me through that soon. Once I learn how to do that, I'll recode this in STAN as well and it should make a big difference.

Sounds good! I'll leave this issue open for now.


[HUDI-1693] Add document about HUDI Flink integration

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html 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.

I want to collapse these two items but don't know how to, can someone give some help here ?


Fixing typo from "tpics" to "topics"

Quick edit to fix typo.

@rossbalsillie : Thanks for your contribution! The author, @mikejo5000, has been notified to review your proposed change.

@rossbalsillie Thanks for the fix!

#sign-off


Fix Reading logs in real time example

ContainersCreatePostBody::setNames() does not exist. Set name unique name with containerCreate()

Thanks


Incoming and outgoing aliases in JSON

Python version: 3.7.3
Pydantic version: 1.1

Hello,
I've been struggling with getting this to work "my way".
I have the below model which takes data from a source that I have no control over.
My use case is that I need to have this model returned as JSON but with camel cased output.
import pydantic

class Video(BaseModel):
    secure_video_url: str = Field(None, alias="video:secure_url")

v = Video(**{"video:secure_url": "http://example.com/video=123"})

First, getting it into the field is easy secure_video_url = Field(None, alias="video:secure_url") and getting it out from the alias is also easy v.json(by_alias=True).
What I find myself struggling with is how to do v.json() and get something along the lines of {"secureVideoUrl": "http://example.com/video=123"}.
I have read the following issues and PRs but have failed to get the output I need

https://github.com/samuelcolvin/pydantic/issues/159
https://github.com/samuelcolvin/pydantic/issues/1056

My understanding is that you can only have 1 alias per field and that has left me thinking that either I should use a custom JSON encoder that transforms it (I would love not to) or write some logic around those aliases that have special case names and store that in the Config class of a base class.

I think this is covered by #624, if that doesn't work, please let us know on the issue how you would like it to work.

Yes, those options would work for me, but I am assuming (since I cant find it in the docs or code) that it's implemented yet, right?

It's not implemented yet, I will work on it soon.
Unless someone else wants to submit a PR?


Old pretrained models are not available!

Hi, how can i get old pretrained models?
Provided link in your github repository for old pretraining models is not working (not applicable).
Please, check that issue. I would like to download old pretrained models.
Thank you

I'm sorry. I confirmed the problem and fixed it!


Windows installation

I'd like to share my experience with installing TensorFlow on Windows, which was actually a piece of cake since the 1.0 release. I thought about making a pull-request, but maybe you have your reasons for not elaborating.
Probably the most important part for any Windows user is to download a Python distribution which already has built-in support for the scientific Python stack. I used Anaconda, but there are WinPython and Enthought Canopy (for Python 3). From there, it's just following the instructions at TensorFlow's page.
In short, given Anaconda is installed and in the user's path (happens by default):
C:\> conda create -n tf python=3.5
...
C:\> activate tf
(tf) C:\> pip install --ignore-installed --upgrade https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-1.2.1-cp35-cp35m-win_amd64.whl
...
(tf) C:\> conda install jupyter matplotlib (etc.)

To use TF with a GPU, the headache is more from the CUDA side, but not too much:

Install Visual Studio Community 2015, making sure C++ is part of the installation.
Install CUDA 8
Download cuDNN 5.1 (which isn't the latest version) and drop the files from the zip into where you installed CUDA.
Same instructions as above, but use https://storage.googleapis.com/tensorflow/windows/gpu/tensorflow_gpu-1.2.1-cp35-cp35m-win_amd64.whl instead.

Hope this helps :smiley:

This is tremendously helpful, @beneyal -- thank you! Please feel free to make a pull request to integrate these Windows instructions with my existing ones.

@beneyal has resolved the issue he raised :1st_place_medal:

Shouldn't it be the other way round? If you install a specific tf package using pip within anaconda and then install keras (with its dependencies), the specific tf package will be overwritten. Or do I have a wring perception of this?

Hi @anderl80, installing Keras does not overwrite your installation of TensorFlow.

Hi @jonkron unfortunatly my Anaconda did overwrite. I used the GUI installation but I think calling conda install from CLI will resolve the same dependencies. Anyhow did work in the endet. Looking forward for the live sessions!!

Oh, I see, @anderl80. That is news to me -- good to know! Looking forward to having you in class this week 😃


Lauren QA - Mobile

Our Products Page Mobile
Can we check the text over the image, looks bad. IPhone 8 +

The "Friends" Logos on both pages took awhile to load then were blurry. Not sure why.

Our Products:
When I was scrolling down, the page was blinking and showing this screen and what you are meant to see. Not sure if we can just double check this. I can try to take a video later if needed.

All issues mentioned on comments above already added / fixed, please check on the demo website.


Chevronous text inline prop

the inline-block class applied to the outer element here https://github.com/mapbox/mr-ui/blob/master/src/components/chevronous-text/chevronous-text.js#L44 makes migrating from mapbox react components difficult. If we could add an inline prop (defaulting to true to avoid shipping a breaking change) to toggle this class on and off, that'd be awesome.

@lshig why did you add the inline-block class in the first place?

inline-block may be a unnecessary leftover artifact from when I thought the chevron arrow was meant to be a fixed size no matter what the text size was. We can probably remove it.


Use DateTimeImmutable

No need to make assumptions about formatting, leave that to the developer.

Codecov Report

Merging #3 into master will increase coverage by -0.37%.

@@             Coverage Diff              @@
##             master       #3      +/-   ##
============================================
- Coverage     79.82%   79.46%   -0.37%
  Complexity       50       50
============================================
  Files             7        7
  Lines           114      112       -2
============================================
- Hits             91       89       -2
  Misses           23       23

Impacted Files
Coverage Δ
Complexity Δ

src/Token.php
100% <100%> (ø)
18 <ø> (ø)
:x:

Continue to review full report at Codecov.

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


Expression serialization on subqueries

It would be great if expression serialization also works on subqueries or CTE-queries. At the moment it looks like that it's not going to work because the serializer expects an  incompatible BaseQueryBuilder:
java.lang.ClassCastException: class com.blazebit.persistence.impl.FullSelectCTECriteriaBuilderImpl cannot be cast to class com.blazebit.persistence.BaseQueryBuilder (com.blazebit.persistence.impl.FullSelectCTECriteriaBuilderImpl and com.blazebit.persistence.BaseQueryBuilder are in unnamed module of loader 'app')
	at com.blazebit.expression.declarative.view.ManagedViewTypeCollection.add(ManagedViewTypeCollection.java:62)

if doing something like
cteBuilder = fullCriteraBuilder.fromSubquery(MyCte.class);
ExpressionSerializer<WhereBuilder> serializer = expressionService.createSerializer(WhereBuilder.class);
serializer.serializeTo(serializerContext, predicate, cteBuilder);

This will require to raise the required minimum version of Blaze-Persistence to 1.6.8 after https://github.com/Blazebit/blaze-persistence/issues/1537 is fixed, but should be fine.


Question: How to downgrade mongodb extension version

I am using this image wodby/drupal-php:7.4-4.37.0
I need to connect to mongodb, but will this error
reports wire version 5, but this version of libmongoc requires at least 6 (MongoDB 3.6)

This look like. i need the mongodb version 1.9.1
I add the below  line in the Dockerfile,
RUN pecl uninstall mongodb
RUN pecl install mongodb-1.9.1

But fail with error
... ...
 => [14/30] RUN pecl uninstall mongodb                                                                                4.9s
 => ERROR [15/30] RUN pecl install mongodb-1.9.1                                                                                40.9s
------
 > [15/30] RUN pecl install mongodb-1.9.1:
#0 0.340 PHP Warning:  PHP Startup: Unable to load dynamic library 'mongodb' (tried: /usr/local/lib/php/extensions/no-debug-non-zts-20190902/mongodb (Error loading shared library /usr/local/lib/php/extensions/no-debug-non-zts-20190902/mongodb: No such file or directory), /usr/local/lib/php/extensions/no-debug-non-zts-20190902/mongodb.so (Error loading shared library /usr/local/lib/php/extensions/no-debug-non-zts-20190902/mongodb.so: No such file or directory)) in Unknown on line 0
#0 5.966 downloading mongodb-1.9.1.tgz ...
#0 5.967 Starting to download mongodb-1.9.1.tgz (1,285,984 bytes)
#0 6.272 ..............................................................................................................................................................................................................................................................done: 1,285,984 bytes
#0 38.61 586 source files, building
#0 38.66 running: phpize
#0 38.67 Configuring for:
#0 38.67 PHP Api Version:         20190902
#0 38.67 Zend Module Api No:      20190902
#0 38.67 Zend Extension Api No:   320190902
#0 39.34 configure.ac:18: warning: $as_echo is obsolete; use AS_ECHO(["message"]) instead
#0 39.34 build/php.m4:2110: PHP_CONFIG_NICE is expanded from...
#0 39.34 configure.ac:18: the top level
#0 39.34 scripts/autotools/CheckCompiler.m4:63: warning: The macro `AC_TRY_COMPILE' is obsolete.
#0 39.34 scripts/autotools/CheckCompiler.m4:63: You should run autoupdate.
#0 39.34 ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:120: AX_PROTOTYPE is expanded from...
#0 39.34 scripts/autotools/CheckCompiler.m4:63: the top level
#0 39.34 scripts/autotools/CheckCompiler.m4:63: warning: The macro `AC_TRY_COMPILE' is obsolete.
#0 39.34 scripts/autotools/CheckCompiler.m4:63: You should run autoupdate.
#0 39.34 ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:120: AX_PROTOTYPE is expanded from...
#0 39.34 scripts/autotools/CheckCompiler.m4:63: the top level
#0 39.34 scripts/autotools/CheckCompiler.m4:63: warning: The macro `AC_TRY_COMPILE' is obsolete.
#0 39.34 scripts/autotools/CheckCompiler.m4:63: You should run autoupdate.
#0 39.34 ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:120: AX_PROTOTYPE is expanded from...
#0 39.34 scripts/autotools/CheckCompiler.m4:63: the top level
#0 39.34 scripts/autotools/CheckCompiler.m4:63: warning: The macro `AC_TRY_COMPILE' is obsolete.
#0 39.34 scripts/autotools/CheckCompiler.m4:63: You should run autoupdate.
#0 39.34 ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.34 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:120: AX_PROTOTYPE is expanded from...
#0 39.35 scripts/autotools/CheckCompiler.m4:63: the top level
#0 39.35 scripts/autotools/CheckCompiler.m4:63: warning: The macro `AC_TRY_COMPILE' is obsolete.
#0 39.35 scripts/autotools/CheckCompiler.m4:63: You should run autoupdate.
#0 39.35 ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:120: AX_PROTOTYPE is expanded from...
#0 39.35 scripts/autotools/CheckCompiler.m4:63: the top level
#0 39.35 scripts/autotools/CheckCompiler.m4:63: warning: The macro `AC_TRY_COMPILE' is obsolete.
#0 39.35 scripts/autotools/CheckCompiler.m4:63: You should run autoupdate.
#0 39.35 ./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:190: AX_PROTOTYPE_EACH is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:208: AX_PROTOTYPE_LOOP is expanded from...
#0 39.35 scripts/autotools/m4/ax_prototype.m4:120: AX_PROTOTYPE is expanded from...
#0 39.35 scripts/autotools/CheckCompiler.m4:63: the top level
#0 39.35 configure.ac:161: warning: The macro `AC_LANG_C' is obsolete.
#0 39.35 configure.ac:161: You should run autoupdate.
#0 39.36 ./lib/autoconf/c.m4:72: AC_LANG_C is expanded from...
#0 39.36 build/libtool.m4:2727: _LT_AC_LANG_C_CONFIG is expanded from...
#0 39.36 build/libtool.m4:2726: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
#0 39.36 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.36 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.36 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.36 configure.ac:161: the top level
#0 39.36 configure.ac:161: warning: The macro `AC_LANG_C' is obsolete.
#0 39.36 configure.ac:161: You should run autoupdate.
#0 39.36 ./lib/autoconf/c.m4:72: AC_LANG_C is expanded from...
#0 39.36 lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
#0 39.36 lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
#0 39.36 ./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
#0 39.36 ./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
#0 39.36 build/libtool.m4:561: _LT_AC_LOCK is expanded from...
#0 39.36 build/libtool.m4:1184: AC_LIBTOOL_SYS_HARD_LINK_LOCKS is expanded from...
#0 39.36 build/libtool.m4:2727: _LT_AC_LANG_C_CONFIG is expanded from...
#0 39.36 build/libtool.m4:2726: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
#0 39.36 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.36 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.36 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.36 configure.ac:161: the top level
#0 39.36 configure.ac:161: warning: The macro `AC_TRY_LINK' is obsolete.
#0 39.36 configure.ac:161: You should run autoupdate.
#0 39.36 ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
#0 39.36 lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
#0 39.36 lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
#0 39.36 ./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
#0 39.36 ./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
#0 39.36 build/libtool.m4:561: _LT_AC_LOCK is expanded from...
#0 39.36 build/libtool.m4:1184: AC_LIBTOOL_SYS_HARD_LINK_LOCKS is expanded from...
#0 39.36 build/libtool.m4:2727: _LT_AC_LANG_C_CONFIG is expanded from...
#0 39.36 build/libtool.m4:2726: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
#0 39.36 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.36 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.36 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.36 configure.ac:161: the top level
#0 39.36 configure.ac:161: warning: back quotes and double quotes must not be escaped in: $as_me:${as_lineno-$LINENO}: WARNING: \`$CC' does not support \`-c -o', so \`make -j' may be unsafe
#0 39.36 build/libtool.m4:1184: AC_LIBTOOL_SYS_HARD_LINK_LOCKS is expanded from...
#0 39.36 build/libtool.m4:2727: _LT_AC_LANG_C_CONFIG is expanded from...
#0 39.36 build/libtool.m4:2726: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
#0 39.36 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.36 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.36 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.36 configure.ac:161: the top level
#0 39.36 configure.ac:161: warning: back quotes and double quotes must not be escaped in: $as_me: WARNING: \`$CC' does not support \`-c -o', so \`make -j' may be unsafe
#0 39.36 build/libtool.m4:1184: AC_LIBTOOL_SYS_HARD_LINK_LOCKS is expanded from...
#0 39.36 build/libtool.m4:2727: _LT_AC_LANG_C_CONFIG is expanded from...
#0 39.36 build/libtool.m4:2726: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
#0 39.36 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.37 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.37 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.37 configure.ac:161: the top level
#0 39.37 configure.ac:161: warning: back quotes and double quotes must not be escaped in: $as_me:${as_lineno-$LINENO}: WARNING: output file \`$ofile' does not exist
#0 39.37 build/libtool.m4:1917: _LT_AC_TAGCONFIG is expanded from...
#0 39.37 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.37 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.37 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.37 configure.ac:161: the top level
#0 39.37 configure.ac:161: warning: back quotes and double quotes must not be escaped in: $as_me: WARNING: output file \`$ofile' does not exist
#0 39.37 build/libtool.m4:1917: _LT_AC_TAGCONFIG is expanded from...
#0 39.37 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.37 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.37 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.37 configure.ac:161: the top level
#0 39.37 configure.ac:161: warning: back quotes and double quotes must not be escaped in: $as_me:${as_lineno-$LINENO}: WARNING: output file \`$ofile' does not look like a libtool script
#0 39.37 build/libtool.m4:1917: _LT_AC_TAGCONFIG is expanded from...
#0 39.37 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.37 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.37 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.37 configure.ac:161: the top level
#0 39.37 configure.ac:161: warning: back quotes and double quotes must not be escaped in: $as_me: WARNING: output file \`$ofile' does not look like a libtool script
#0 39.37 build/libtool.m4:1917: _LT_AC_TAGCONFIG is expanded from...
#0 39.37 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.37 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.37 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.37 configure.ac:161: the top level
#0 39.37 configure.ac:161: warning: back quotes and double quotes must not be escaped in: $as_me:${as_lineno-$LINENO}: WARNING: using \`LTCC=$LTCC', extracted from \`$ofile'
#0 39.37 build/libtool.m4:1917: _LT_AC_TAGCONFIG is expanded from...
#0 39.37 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.37 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.37 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.37 configure.ac:161: the top level
#0 39.37 configure.ac:161: warning: back quotes and double quotes must not be escaped in: $as_me: WARNING: using \`LTCC=$LTCC', extracted from \`$ofile'
#0 39.37 build/libtool.m4:1917: _LT_AC_TAGCONFIG is expanded from...
#0 39.37 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.37 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.37 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.37 configure.ac:161: the top level
#0 39.38 configure.ac:161: warning: back quotes and double quotes must not be escaped in: tag name \"$tagname\" already exists
#0 39.38 build/libtool.m4:1917: _LT_AC_TAGCONFIG is expanded from...
#0 39.38 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.38 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.38 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.38 configure.ac:161: the top level
#0 39.38 configure.ac:161: warning: The macro `AC_LANG_CPLUSPLUS' is obsolete.
#0 39.38 configure.ac:161: You should run autoupdate.
#0 39.38 ./lib/autoconf/c.m4:262: AC_LANG_CPLUSPLUS is expanded from...
#0 39.38 build/libtool.m4:2809: _LT_AC_LANG_CXX_CONFIG is expanded from...
#0 39.38 build/libtool.m4:2808: AC_LIBTOOL_LANG_CXX_CONFIG is expanded from...
#0 39.38 build/libtool.m4:1917: _LT_AC_TAGCONFIG is expanded from...
#0 39.38 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.38 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.38 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.38 configure.ac:161: the top level
#0 39.38 configure.ac:161: warning: back quotes and double quotes must not be escaped in: $as_me:${as_lineno-$LINENO}: WARNING: \`$CC' does not support \`-c -o', so \`make -j' may be unsafe
#0 39.38 build/libtool.m4:1184: AC_LIBTOOL_SYS_HARD_LINK_LOCKS is expanded from...
#0 39.38 build/libtool.m4:2809: _LT_AC_LANG_CXX_CONFIG is expanded from...
#0 39.38 build/libtool.m4:2808: AC_LIBTOOL_LANG_CXX_CONFIG is expanded from...
#0 39.38 build/libtool.m4:1917: _LT_AC_TAGCONFIG is expanded from...
#0 39.38 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.38 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.38 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.38 configure.ac:161: the top level
#0 39.38 configure.ac:161: warning: back quotes and double quotes must not be escaped in: $as_me: WARNING: \`$CC' does not support \`-c -o', so \`make -j' may be unsafe
#0 39.38 build/libtool.m4:1184: AC_LIBTOOL_SYS_HARD_LINK_LOCKS is expanded from...
#0 39.38 build/libtool.m4:2809: _LT_AC_LANG_CXX_CONFIG is expanded from...
#0 39.38 build/libtool.m4:2808: AC_LIBTOOL_LANG_CXX_CONFIG is expanded from...
#0 39.38 build/libtool.m4:1917: _LT_AC_TAGCONFIG is expanded from...
#0 39.38 build/libtool.m4:70: AC_LIBTOOL_SETUP is expanded from...
#0 39.38 build/libtool.m4:52: _AC_PROG_LIBTOOL is expanded from...
#0 39.38 build/libtool.m4:39: AC_PROG_LIBTOOL is expanded from...
#0 39.38 configure.ac:161: the top level
#0 40.39 building in /tmp/pear/temp/pear-build-defaultuserdDhfHj/mongodb-1.9.1
#0 40.40 running: /tmp/pear/temp/mongodb/configure --with-php-config=/usr/local/bin/php-config
#0 40.51 checking for grep that handles long lines and -e... /bin/grep
#0 40.51 checking for egrep... /bin/grep -E
#0 40.51 checking for a sed that does not truncate output... /bin/sed
#0 40.52 checking for pkg-config... /usr/bin/pkg-config
#0 40.52 checking pkg-config is at least version 0.9.0... yes
#0 40.52 checking for cc... no
#0 40.52 checking for gcc... no
#0 40.52 configure: error: in `/tmp/pear/temp/pear-build-defaultuserdDhfHj/mongodb-1.9.1':
#0 40.52 configure: error: no acceptable C compiler found in $PATH
#0 40.52 See `config.log' for more details
#0 40.66 ERROR: `/tmp/pear/temp/mongodb/configure --with-php-config=/usr/local/bin/php-config' failed
------
failed to solve: executor failed running [/bin/sh -c pecl install mongodb-1.9.1]: exit code: 1

Any recommend way to install  mongodb 1.9.1?
Thanks

The error says:
#0 40.52 configure: error: no acceptable C compiler found in $PATH

you didn't install compilation tools, also you probably need to extract php source, the archive is available in the dev version of images

Finially this work for me.
RUN rm -f /usr/local/lib/php/extensions/no-debug-non-zts-20190902/mongodb.so
RUN apk --update add --virtual build-dependencies build-base openssl-dev autoconf \
  && pecl install -f "mongodb-1.9.1"\
  && docker-php-ext-enable mongodb \
  && apk del build-dependencies build-base openssl-dev autoconf \
  && rm -rf /var/cache/apk/*

Thanks.


fixes #497 and #524

use Math.log10 transform on predicted numbers of infections by lineage to improve distribution for colour palette
added predicted number of infections (tip.infections) to lineage CSV output
tweaked infections legend label in all four languages

Checking the following:

[x] Search

[x] Search by accession number
[x] Search by lineage
[x] Search by country
[x] Search by country (with date filter)

[x] Tree filtering
[x] Download Time-scaled tree (nwk)
[x] Download Time-scaled tree (csv)
[x] Download Beadplot (svg)
[x] Download Beadplot (nwk)
[x] Download mutation list (csv)
[x] Beadplot cutoff slider
[x] Expanding Beadplot
[x] Translated pages
[x] Changing the colour of the tree based on divergence, collection date, etc.
[x] Left/Right arrow key to move between beads
[x] Tooltips
[x] Countries/Samples/Mutations tabs are populating the correct information
[x] Build front-end database without issues
[ ] Port front-end change to epicov branch


Precision of position data

There was a remark from Jens that uploaded data from Sweden do not have the nedded precision of the position which is needed for processing.
What is the reason and could it be changed?

I have recorded data for 10 seconds from the A50 in three formats:

raw_actisense which I can read with the actisense ebl-Reader
output of the canboat actisense-serial
json data , extracted by canboat analyzer from the actisense-serial

This a line right from the end of the json-file: {"timestamp":"2013-10-17-19:40:04.333","prio":"3","src":"160","dst":"255","pgn":"129029","description":"GNSS Position Data","fields":{"SID":"165","Date":"2013.10.17", "Time": "19:40:03.08580","Latitude":"51.4427608","Longitude":"06.9606460","GNSS type":"GPS","Method":"GNSS fix","Integrity":"No integrity checking","Number of SVs":"5","HDOP":"2.20","PDOP":"-0.01","Geoidal Separation":"-0.01","Reference Station ID":"15"}}
The times differ, the timestamp is made from the raspberry time. Time comes from the gps.
The elb-reader can open and display the raw file. Line 174 tells: Raw BST Data: 0x93,0x36,0x03,0x05,0xF8,0x01,0xFF,0xA0,0x49,0x8E,0x07,0x00,0x2B,0xA5,0x7B,0x3E,0xB4,0xCF,0x33,0x2A,0x00,0x70,0x7E,0x15,0x2F,0x9D,0x23,0x07,0x00,0x58,0x5F,0xE2,0xB4,0x4A,0xF7,0x00,0xE0,0xC1,0x08,0x05,0x00,0x00,0x00,0x00,0x10,0xFC,0x05,0xDC,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x00,0x34, Basic Message PGN: 129029 (0x1F805), SRC = 160, DST = 255, Priority = 3, Len = 43, Data = A5 7B 3E B4 CF 33 2A 00 70 7E 15 2F 9D 23 07 00 58 5F E2 B4 4A F7 00 E0 C1 08 05 00 00 00 00 10 FC 05 DC 00 FF FF FF FF FF FF 00
Full decoded Message NMEA 2000 PGN: 129029 (0x1F805) Name: GNSS Position Data Source = 160, Destination = 255 Priority = 3, Length = 43 Number Of Fields = 18 Field 1: SID = 165 Field 2: Position date = 17/10/2013 Field 3: Position time = 19:40:03.858 Field 4: Latitude = 51° 26.565648' N (51.4427608000000000°) Field 5: Longitude = 06° 57.638760' E (6.9606460000000000°) Field 6: Altitude = 84.460000 Metres Field 7: Type of System = 0 (GPS) Field 8: Method, GNSS = 1 (GNSS Fix) Field 9: Integrity = 0 Field 10: Reserved field Field 11: Number of SVs = 5 Field 12: HDOP = 2.20 Ratio Field 13: PDOP = -0.01 Ratio Field 14: Geoidal Separation = -0.01 Metres Field 15: Number of Reference Stations = 0
I see no difference in the resolution of the json and the ebl-Data. "Latitude":"51.4427608","Longitude":"06.9606460"
If I convert to a RMC messsage with my software I put out LAT=51° 26.565' N, LON =06° 57.638' E. This format is equivalent to the nmea0183 on the serial port. Is there a difference in the resolution with nmea2000 or nmea0183?
Am 17.10.2013 01:31, schrieb cleanerx:

depends on what is most easily debugable.
If I had the actisense data I would replay it through my software and
halt the debugger at the parts of the code where the position is analyzed.
—
Reply to this email directly or view it on GitHub
#25 (comment).

Hi,
How it's possible to convert this:
A57B3EB4CF332A00707E152F9D230700585FE2B44AF700E0C108050000000010FC05DC00FFFFFFFFFFFF00
To this  ?
{
"SID":"165"
"Date":"2013.10.17"
"Time":"19:40:03.08580"
"Latitude":"51.4427608"
"Longitude":"06.9606460"
"GNSStype":"GPS"
"Method":"GNSS fix"
"Integrity":"No integritychecking"
"Number of SVs":"5"
"HDOP":"2.20"
"PDOP":"-0.01"
"GeoidalSeparation":"-0.01"
"Reference Station ID":"15"
}
A5 hex > 165 dec
But the others?
Based on NMEA is 8 bytes + 16 (date) + 32 (time) + 64 (lat), + 64 (lon)..
But it's impossible to convert... Ca you help me ?


[Docs]: Table Widget

Is there an existing issue for this?

[X] I have searched the existing issues

Documentation Link
https://docs.appsmith.com/reference/widgets/table
https://docs.appsmith.com/reference/widgets/table/column-settings
Discord/slack/intercom Link
No response
Describe the problem
Rehaul the below docs:

Table - Landing Page
Column Settings](https://docs.appsmith.com/reference/widgets/table/column-settings)

Describe the improvement
Rehaul the docs
To analyze if https://docs.appsmith.com/core-concepts/data-access-and-binding/displaying-data-read/display-data-tables page data can be added to table widget.

PR available here for review

Related
https://github.com/appsmithorg/appsmith/issues/5426
https://github.com/appsmithorg/appsmith/issues/8210


Ensure site works when site.baseurl is non-empty

Jekyll makes this a bit annoying to do, IMO, but we should make sure the site works properly when site.baseurl is non-empty. This means prepending  site.baseurl to intra-site links, for the most part, i.e. not assuming that / is the root of the site.
Ordinarily this might not be a big deal, but because federalist's branch builds do set site.baseurl to a non-empty value, we need to make sure this works--otherwise federalist branch builds will be useless!

Also, a good way to test this locally is to temporarily set baseurl in _config.yml to something like /boop, then run the Jekyll server and visit http://localhost:4000/boop/ and make sure everything works.

This is currently breaking URLs on some PDF downloads. :-( The "history and mission" page, for instance. I haven't had time to look at the codebase, so I don't know if just prepending the baseurl would fix it.

I'm gonna say this was fixed by #85. The remaining 404s will be resolved once we fix #83.


Feature/mask shapely

closes #62
closes #22

Codecov Report

Merging #72 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #72      +/-   ##
=========================================
+ Coverage   99.08%   99.1%   +0.01%
=========================================
  Files          18      18
  Lines        1427    1459      +32
=========================================
+ Hits         1414    1446      +32
  Misses         13      13

Impacted Files
Coverage Δ

regionmask/test/test_mask.py
100% <100%> (ø)
:arrow_up:

regionmask/core/mask.py
99.31% <100%> (+0.11%)
:arrow_up:

Continue to review full report at Codecov.

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


@Getter on Boolean field

Hi there,
it looks like using @Getter on a Boolean (with a capital B) field creates a method that starts with get not with is.
  If you want to be conform, than use it as is.

I guess if that's the spec, then that's the spec.
It meant that my method names changed when I moved from boolean to Boolean. On the upside, it meant the compiler told me about I all places where I had to check for the new option of a null value. So perhaps it was for the better.


Feature/exceptions

@ggsdc this should solve the issue you had. I made a handler for all exceptions (not only InvalidUsage). Until now, the exceptions that were not InvalidUsage were only handled when in dev or test environments, and the other used flask default error handlers

Should I merge or wait for the other PR?

You can merge it now


Docusaurus v2.0 update

In reference to issue https://github.com/accordproject/techdocs/issues/160, please see my comment at https://github.com/accordproject/techdocs/issues/160#issuecomment-725095044.

Thanks for your hard work @prakharsr.
I suggest that we create a development branch ready for v2 release so that we can support multiple contributions until we're ready to make it the master branch. I've created the branch (https://github.com/accordproject/techdocs/tree/docusaurus-v2), so you should retarget your PR to that.
That will also mean that you can promote your v2-website directory to the top-level and we can remove the old content.
We can then create separate issues for specific issues and ask others for help.
Finally, are you able to fix the DCO sign-off, please? Let me know if you need help with this.

Hi, @mttrbrts . Thanks for helping, I have rebased my branch from master to docusaurus-v2 and fixed the DCO signoff issue.
The features/ components which are incomplete and need fixing are:

Fixing the index page and footer and make it look the same as in v1 (I am facing hurdles here as I don't know much react).

Fixing background colors and snippets color highlighting.

Migrating syntax highlighting to Prism (not yet completed).

I was unable to build the website due to (undefined) Error: Minified React error #152, leading to unable deploy the static website at github pages. A development version is currently being deployed by me at https://accordproject-znyzg7zhdq-uc.a.run.app/ where a preview of the migrated site can be seen.

Thanks @prakharsr.
There's a lot of files here for us to review, so please bear with us while we do that.
There are two things that would be really helpful for the reviewers:

Please delete the existing website folder, then rename v2-website to website. We will use branches to manage concurrent versions instead. This will mean that you can remove all changes to docs and config that just deal with directory changes.
Please add .docusarus to .gitignore and delete the existing `.docusaurus1 directory. This content is dynamic and doesn't need to be checked into the repo.

Looks like the error is something with webpack?
11:33:58 PM: > docusaurus build
11:33:58 PM: /opt/build/repo/website/node_modules/copy-webpack-plugin/node_modules/p-limit/index.js:30
11:33:58 PM: 		} catch {}
11:33:58 PM: 		        ^
11:33:58 PM: SyntaxError: Unexpected token {
11:33:58 PM:     at createScript (vm.js:80:10)
11:33:58 PM:     at Object.runInThisContext (vm.js:139:10)
11:33:58 PM:     at Module._compile (module.js:617:28)
11:33:58 PM:     at Object.Module._extensions..js (module.js:664:10)
11:33:58 PM:     at Module.load (module.js:566:32)
11:33:58 PM:     at tryModuleLoad (module.js:506:12)
11:33:58 PM:     at Function.Module._load (module.js:498:3)
11:33:58 PM:     at Module.require (module.js:597:17)
11:33:58 PM:     at require (internal/module.js:11:18)
11:33:58 PM:     at Object.<anonymous> (/opt/build/repo/website/node_modules/copy-webpack-plugin/dist/index.js:18:38)
11:33:58 PM: npm
11:33:58 PM:  ERR! code
11:33:58 PM:  ELIFECYCLE
11:33:58 PM: npm
11:33:58 PM: ERR! errno 1
11:33:58 PM: npm
11:33:58 PM:  ERR!
11:33:58 PM:  @ build: `docusaurus build`
11:33:58 PM: npm
11:33:58 PM:  ERR! Exit status 1
11:33:58 PM: npm
11:33:58 PM:  ERR!
11:33:58 PM: npm
11:33:58 PM:  ERR!
11:33:58 PM:  Failed at the @ build script.
11:33:58 PM: npm
11:33:58 PM:  ERR! This is probably not a problem with npm. There is likely additional logging output above.
11:33:58 PM: npm
11:33:58 PM: ERR! A complete log of this run can be found in:
11:33:58 PM: npm
11:33:58 PM: ERR!     /opt/buildhome/.npm/_logs/2020-12-02T04_33_58_583Z-debug.log
11:33:58 PM: Skipping functions preparation step: no functions directory set

Yeah, probably, though I got a different error message.`^C22:17:36|prakhar@hp-ay503tx|website$ npm run build

@ build /home/prakhar/projects/techdocs_og/techdocs/website
docusaurus build

Creating an optimized production build...
The docs plugin option homePageId=accordproject is deprecated. To make a doc the "home", prefer frontmatter: "slug: /"
✔ Client
Compiled successfully in 3.74m
✖ Server
Compiled with some errors in 4.19m
Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
(undefined) Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Za (main:69598:465)
at d (main:69600:55)
at $a (main:69602:16)
at a.b.render (main:69607:476)
at a.b.read (main:69607:18)
at Object.renderToString (main:69617:364)
at serverEntry_render (main:96653:664)
(undefined) Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Za (main:69598:465)
at d (main:69600:55)
at $a (main:69602:16)
at a.b.render (main:69607:476)
at a.b.read (main:69607:18)
at Object.renderToString (main:69617:364)
at serverEntry_render (main:96653:664)
(undefined) Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Za (main:69598:465)
at d (main:69600:55)
at $a (main:69602:16)
at a.b.render (main:69607:476)
at a.b.read (main:69607:18)
at Object.renderToString (main:69617:364)
at serverEntry_render (main:96653:664)
(undefined) Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Za (main:69598:465)
at d (main:69600:55)
at $a (main:69602:16)
at a.b.render (main:69607:476)
at a.b.read (main:69607:18)
at Object.renderToString (main:69617:364)
at serverEntry_render (main:96653:664)
(undefined) Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Za (main:69598:465)
at d (main:69600:55)
at $a (main:69602:16)
at a.b.render (main:69607:476)
at a.b.read (main:69607:18)
at Object.renderToString (main:69617:364)
at serverEntry_render (main:96653:664)
(undefined) Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Za (main:69598:465)
at d (main:69600:55)
at $a (main:69602:16)
at a.b.render (main:69607:476)
at a.b.read (main:69607:18)
at Object.renderToString (main:69617:364)
at serverEntry_render (main:96653:664)
(undefined) Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Za (main:69598:465)
at d (main:69600:55)
at $a (main:69602:16)
at a.b.render (main:69607:476)
at a.b.read (main:69607:18)
at Object.renderToString (main:69617:364)
at serverEntry_render (main:96653:664)
(undefined) Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Za (main:69598:465)
at d (main:69600:55)
at $a (main:69602:16)
at a.b.render (main:69607:476)
at a.b.read (main:69607:18)
at Object.renderToString (main:69617:364)
at serverEntry_render (main:96653:664)
(undefined) Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=code for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at Za (main:69598:465)
at d (main:69600:55)
at $a (main:69602:16)
at a.b.render (main:69607:476)
at a.b.read (main:69607:18)
at Object.renderToString (main:69617:364)
at serverEntry_render (main:96653:664)
Error: Failed to compile with errors.
at /home/prakhar/projects/techdocs_og/techdocs/website/node_modules/@docusaurus/core/lib/webpack/utils.js:163:24
at finalCallback (/home/prakhar/projects/techdocs_og/techdocs/website/node_modules/webpack/lib/MultiCompiler.js:254:12)
at /home/prakhar/projects/techdocs_og/techdocs/website/node_modules/webpack/lib/MultiCompiler.js:277:6
at done (/home/prakhar/projects/techdocs_og/techdocs/website/node_modules/neo-async/async.js:2931:13)
at runCompilers (/home/prakhar/projects/techdocs_og/techdocs/website/node_modules/webpack/lib/MultiCompiler.js:181:48)
at /home/prakhar/projects/techdocs_og/techdocs/website/node_modules/webpack/lib/MultiCompiler.js:188:7
at /home/prakhar/projects/techdocs_og/techdocs/website/node_modules/webpack/lib/MultiCompiler.js:270:7
at finalCallback (/home/prakhar/projects/techdocs_og/techdocs/website/node_modules/webpack/lib/Compiler.js:257:39)
at /home/prakhar/projects/techdocs_og/techdocs/website/node_modules/webpack/lib/Compiler.js:273:13
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/prakhar/projects/techdocs_og/techdocs/website/node_modules/tapable/lib/HookCodeFactory.js:33:10), :42:1)
at AsyncSeriesHook.lazyCompileHook (/home/prakhar/projects/techdocs_og/techdocs/website/node_modules/tapable/lib/Hook.js:154:20)
at onCompiled (/home/prakhar/projects/techdocs_og/techdocs/website/node_modules/webpack/lib/Compiler.js:271:21)
at /home/prakhar/projects/techdocs_og/techdocs/website/node_modules/webpack/lib/Compiler.js:681:15
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/prakhar/projects/techdocs_og/techdocs/website/node_modules/tapable/lib/HookCodeFactory.js:33:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/home/prakhar/projects/techdocs_og/techdocs/website/node_modules/tapable/lib/Hook.js:154:20)
at /home/prakhar/projects/techdocs_og/techdocs/website/node_modules/webpack/lib/Compiler.js:678:31
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ build: docusaurus build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/prakhar/.npm/_logs/2020-12-02T16_52_03_768Z-debug.log`

@prakharsr Adding a link to a short discussion about this PR in a request community working group call, https://vimeo.com/489140290

@prakharsr Also, I found the problem that is causing the build to fail...
The MDX render is failing on an empty code block in several places. To fix, you should replace  with   (Notice the space between the elements).
There is probably a better way to fix this, and we'll need a way to do this automatically because several of the files that have this problem are auto-generated. However, this will let us preview your build on Netlify and get your PR merged so that we can start work on the other issues.
Once I fixed this issue locally, I started seeing this error:
Error: You are trying to create client-side redirections to paths that do not exist:
- /*

To fix that, I had to change the plugins entry in docusaurus.config.js to
  "plugins": [
    [
      "@docusaurus/plugin-client-redirects",
      {
        "fromExtensions": [
          "html"
        ]
      }
    ]
  ],

@mttrbrts

I fixed the build according to your instructions in d4e94acded16a3a8c7afd9d91ad4fb5d8ed83438 and it works! I setup my own netlify deploy for this project at url https://ecstatic-lewin-144d0e.netlify.app/ and added the netlify deploy status badge in this project's https://github.com/prakharsr/techdocs README.md. [![Netlify Status](https://api.netlify.com/api/v1/badges/b6de7e93-88c3-4684-8424-298ed99b6931/deploy-status)](https://app.netlify.com/sites/ecstatic-lewin-144d0e/deploys). The current netlify automatically running for this project uses an old node version, that seems to be the issue why its build is failing.
There is a file missing website/static/docs/assets/advanced/late10b.png which is references in all versions in file advanced-latedelivery.md and in versions 0.20 & 0.21 in file tutorial-latedelivery.md. As a temporary workaround, I created a duplicate of the file late10.png and renamed it as late10b.png.

@jesswang-dev


[Blocked on #1435] Support proptest arbitrary generation for bool and tuple

Description of changes:
Added support for arbitrary generation trait, and implemented it for booleans and tuples.
Resolved issues:
Resolves: #1363, PR 2/3
Call-outs:

This requires #1435 to merge first. This is PR 2/3 to implement support for primitive types in proptest.
As of now, the diff looks large. However, once the above PR merges, the size of the PR should be around 10 files.
Since only primitives and tuples of them are supported, the test cases is only 1 file. Tthis test case is designed to test both tuples and booleans at once.

Testing:

How is this change tested? tests/cargo-kani/proptest/src/arbitrary_boolean.rs

Is this a refactor change? No

Checklist

[x] Each commit message has a non-empty body, explaining why the change was made
[x] Methods or procedures are documented
[x] Regression or unit tests are included, or existing tests cover the modified code
[x] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Closing pull request in favor of merging to features/proptest.


Stochastic using solver (4 PRs)

Makes rulenode2expr compatible with any AbstractRuleNode. In particular, StateFixedShapedHoles (renamed to: StateHole) can now be converted to an expression.

Waiting on HerbCore.jl#17 and the version 0.3.0 release

Rebased on top of dev and cleaned up commit history. Tested locally with all other dev branches.


chore(Algebra/Operations): golf a proof

Golf the proof of Submodule.smul_singleton and rename it to Submodule.singleton_smul.

I think singleton_smul makes more sense. For instance:
https://leanprover-community.github.io/mathlib4_docs/Mathlib/Data/Set/Pointwise/SMul.html#Set.singleton_smul
https://leanprover-community.github.io/mathlib4_docs/Mathlib/Data/Set/Pointwise/SMul.html#Set.smul_singleton

Thanks!
bors merge