Pressure readings inaccurate

When using this library with the Sparkfun Qwiic BME280 module on the Raspberry Pi, the values for barometric pressure are not accurate. To validate this claim, I used the same module on the Arduino with the Sparkfun BME280 library then compare it to when used with this library in Python - the results differed. I then used a BME280 library from another vendor to test and got similar results to the Arduino sketch using the Sparkfun library. Thus, this library is not calculating the pressure correctly.
The following are samples when run on the Raspberry Pi with this library and the BME280 Qwiic module (converting to hPa):
Pressure: 1364.32 hPa
Pressure: 1364.52 hPa
Pressure: 1362.56 hPa
Switching to the Arduino and using the same module and the Sparkfun library, I get values like this:
Pressure: 1019.44 hPa
Pressure: 1019.56 hPa
Pressure: 1019.47 hPa
To further confirm this observation, I can used a different BME280 library for Python but the same BME280 module andgot values like this:
Pressure: 1019.82 hPa
Pressure: 1019.86 hPa
Pressure: 1019.81 hPa
Clearly, the calculation for barometric pressure is inaccurate. Some variation is expected given the module was handled and the sensor isn't intended to be scientific-grade accuracy, but the difference in readings is too far off.
And, yes, I did use the correct value for sea level pressure in my area in all tests. I experimented several of the overscan methods, but nothing made a significant difference in the readings.
I can investigate further if you'd like, but there's something wonky in the code.

I’ve had the same experience. The qwic_bme280_py pressure values are simply wrong. Sea level atmospheric pressures of 1300mb are not even possible.  1019mb is very reasonable. Because of this, I have to throw away the pressure measurement. Sparkfun should fix this.

I’ve had the same experience. The qwic_bme280_py pressure values are simply wrong. Sea level atmospheric pressures of 1300mb are not even possible.  1019mb is very reasonable. Because of this, I have to throw away the pressure measurement. Sparkfun should fix this.

Have submitted a PR which should hopefully close this issue. In the meantime, you can try cloning the forked repo with the fix.

Code to clone and install
git clone https://github.com/georgePadolsey/Qwiic_BME280_Py.git --branch fix/1#issue-782894620

cd Qwiic_BME280_Py

pip install .

Hope this helps :)

@georgePadolsey, thank you! I was pulling my hair out trying to figure out what was wrong with my sensor readings. With your PR mine now lines up with local weather stations.
One other note: while debugging I saw that self.t_fine (which the pressure method uses) is only set from the sensor in get_dewpoint_celsius. This means that you probably need to read the temperature first and then immediately read the pressure to get an accurate value. On my board I do see a big difference between measuring temp and pressure and just measuring temp (IE not having t_fine set). I was planning to open a separate issue on this.


Do not merge: Aug23 top tech

This branch should contain the most up-to-date code from both the demo and the new design ModelArrayRef.
This pull request was created to force test workflows to execute.

We need to get everything that's in this PR into the develop branch before continuing onto milestone 2.

We need to get everything that's in this PR into the develop branch before continuing onto milestone 2.

I don't disagree, but merging this will cover most of Milestone 2, at least on my side.

Closing this, as it is becoming a conflict-filled mess as the changes it encapsulates are merged into develop.


Add a MockBukkitExtension for use with JUnit

Description
Creating MockBukkitExtension that you can use to automatically call MockBukkit.mock() before each test and MockBukkit.unmock() after each test. For examples, I've also converted some test classes to use it.
PR opened as a draft because I'm wondering if we want to support other functionality that MockitoExtension has, like a) constructor parameters or b) initializing a ServerMock field so you don't have to call MockBukkit.getMock().
For example, b) refers to the possibility of doing something like this:
@ExtendWith(MockBukkitExtension.class)
class ExampleTest
{
    @MockBukkitServer
    private ServerMock serverMock;

    @Test
    void testStuff()
    {
        serverMock.addPlayer();
        // ...
    }
}

If we're okay with the existing level of functionality for now, then I can mark the PR as ready for review.
Checklist
The following items should be checked before the pull request can be merged.

[ ] Unit tests added.
[ ] Code follows existing code format.

Info on creating a pull request

Make sure that unit tests are added which test the relevant changes.
Make sure that the changes follow the existing code format.

For maintainer
When a PR is approved, the maintainer should label this PR with release/*.

If the PR fixes a bug in MockBukkit, update the patch version. (if the current version is 0.4.1, the new version should be 0.4.2)
If the PR adds a new feature to MockBukkit, update minor version. (if the current version is 0.4.1, the new version should be 0.5.0)

Note that a PR that fixes an UnimplementedOperationException should be considered a new version and not a bugfix.

Would it be possible to store the Server Instance created in the Extension and provide Accessors for it?

Would it be possible to store the Server Instance created in the Extension and provide Accessors for it?

I don't know (my guess is no), but I'm going to take a swing at implementing field injection using an attribute. (Here's how that looks with MockitoExtension: https://stackoverflow.com/a/40962941)

I've managed to get parameter resolution working but don't quite have it for fields just yet. I pushed a commit showing how the former works and how the latter would ideally work.

I gotta say this is a very nice and useful addition to this project, thanks a lot! <3
I will have a look at the code later

I gotta say this is a very nice and useful addition to this project, thanks a lot! <3 I will have a look at the code later

No problem and sounds good!

I've added field injection but there's still more testing/verification I want to do before marking the PR as ready for review

Also please fix that Code Smell

@TheBusyBiscuit Do you still want any changes on this, or can this be merged?


Migrate to HTTP 0.16.7, use BasicAuthSlice

Migrate to HTTP 0.16.7, use BasicAuthSlice instead of deprecated SliceAuth and Identities

You @olegmoz/z need to have one of these roles in order to do "Request order start": ARC, PO; I'm sorry to say this, but at the moment you've got no roles in this project

Job gh:artipie/rpm-adapter#368 is not assigned, can't get performer

@rultor release, tag=1.2.2

@rultor release, tag=1.2.2

@olegmoz Thanks for your request. @g4s8 Please confirm this.

@rultor release, tag=1.2.2

@rultor release, tag=1.2.2

@olenagerasimova OK, I will release it now. Please check the progress here

@rultor release, tag=1.2.2

@olenagerasimova Done! FYI, the full log is here (took me 9min)


global: cleanup

Removes dependency on Babel.

Removes unused templates.

Installs entry points for extensions.

Changes to pytest-runner and pydocstyle.

Adds console logging configuration.

Fixes FileSystem and Raven logging configuration.

Signed-off-by: Lars Holm Nielsen<EMAIL_ADDRESS>

Coverage increased (+19.8%) to 100.0% when pulling bdb3cf8aefc4def33434266419206619bd48cde9 on lnielsen:fixes into f92952c63fae7d8f8c14ca010193fb7452695b8f on inveniosoftware:master.

LGTM

Coverage increased (+19.8%) to 100.0% when pulling bdb3cf8aefc4def33434266419206619bd48cde9 on lnielsen:fixes into f92952c63fae7d8f8c14ca010193fb7452695b8f on inveniosoftware:master.


bugfix(shared/event): Infinite recursion

Before submitting a pull request, please make sure the following is done...

[x] Ensure the pull request title and commit message follow the Commit Specific in English.
[x] Fork the repo and create your branch from main.
[ ] If you've added code that should be tested, add tests!
[ ] If you've changed APIs, update the documentation.
[ ] Ensure the test suite passes (npm test).
[x] Make sure your code lints (npm run lint) - we've done our best to make sure these rules match our internal linting guidelines.

 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.qiaoyuwen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

CLA麻烦签一下

CLA麻烦签一下

已签


Fixes bug#15. Added to Request ObjectMapper ACCEPT_SINGLE_VALUE_AS_ARRAY

Any chance this can get reviewed/merged? This is a much needed fix for our project!

@kunal546 , do we have an estimate on when you can review and merge this?


Fix wooden slabs not being efficiently broken by axes

I think you'll want to target the following method in ToolBase:
`    public float getStrengthOnBlock(ItemInstance arg, BlockBase arg2) {
for(int var3 = 0; var3 < this.effectiveBlocksBase.length; ++var3) {
if (this.effectiveBlocksBase[var3] == arg2) {
return this.field_2713;
}
}
    return 1.0F;
}`

Issue determined to be too difficult to fix.
Requirements for solution:
Need to be able to get the metadata of the block the player is currently looking at.


feat(Neo4J): Neo4J Driver Support Added

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@026ced0). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             master        #2   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?         6
  Lines             ?        42
  Branches          ?         2
==========================================
  Hits              ?        42
  Misses            ?         0
  Partials          ?         0

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 026ced0...8ebaa8e. Read the comment docs.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Convert indicator MOVE lines to free form EVAL

For situations where the items are of a known type just by looking at the source line please convert them.
Please convert MOVE      *OFF          *IN98 type of statements into *IN98 = *OFF;
Please convert MOVE      *OFF          INEMP_NOTZERO type of statements into INEMP_NOTZERO = *OFF;

Previously fixed.  Working in 0.0.34 based on test case C/022-move_ind


Why is biasAccOmegaInt so large?

Full disclosure I haven't actually tried out Kimera yet (nice work btw). But I was interested in understanding why here https://github.com/MIT-SPARK/Kimera-VIO/blob/d677a3dedad2da605c84a4b7f51154cd7e38a98d/src/imu-frontend/ImuFrontEnd.cpp#L200
biasAccOmegaInt is set to such a large value when in the gtsam example it is set to 1e-5. So I've read that it models the covariance of the bias used during preintegration which would mean that you really don't trust the biases you are estimating on your IMU? Why is that?

Good catch! We are actually not using the Combined IMU factor, but I'll take a note on that:
https://github.com/MIT-SPARK/Kimera-VIO/blob/a5109c7157482bb1203918512ef6593e226507f7/params/Euroc/ImuParams.yaml#L5
We allowed using either the ImuFactor or the CombinedImuFactor from gtsam, I didn't notice any significant difference at the time though, I might as well try again with a lower biasAccOmegaInt.

Thanks for the quick reply, as a side note it says on bitbucket that if you set biasAccOmegaInt to 0 it will be the same.


Generated clientset error for plural, should default to not have plural

Generated clientset error for plural, should default to not have plural.
Normal reconcile is ok, but if trying watch from generated clientset. it got following error.
E0420 18:17:10.044194 3110413 reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.6/tools/cache/reflector.go:125: Failed to list *v1alpha1.LrMpls: the server could not find the requested resource

I0420 18:23:21.633302 3092208 httplog.go:90] verb="GET" URI="/apis/core.cable.vnop.io/v1alpha1/lrmplses?limit=500&resourceVersion=0" latency=805.925µs resp=404 UserAgent="main/v0.0.0 (linux/amd64) kubernetes/$Format" srcIP="<IP_ADDRESS>:44524":

not sure if this flag helps, it seems generated lrmpls_types.go have no difference with this flag.
I'd say make it default to not have plural for object kind with s suffix.
--resource string             optional name of the API resource, defaults to the plural name of the lowercase kind

Version
$ apiserver-boot version
I0420 18:43:44.947930 3174574 version.go:57] Version: version.Version{ApiserverBuilderVersion:"v1.18.0", KubernetesVendor:"kubernetes-1.18.4", GitCommit:"d5fdf8c1b65a7c6068806b540998889ec5114c36", BuildDate:"2020-06-24-19:15:49", GoOs:"linux", GoArch:"amd64"}

create issue here, in case someone encounter the same issue.

using controller-runtime's client, not have this issue, closing.


Should always makedirs as 0755

Volumes being created with 0644 are not writable by users, since they
are not allowed to search through them.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>
- What I did
- How I did it
- How to verify it
- Description for the changelog

/test all

/test kata-containers

/retest

/test e2e

LGTM

/retest

/test e2e_fedora
/test kata-containers


Replace TizenDlogReader with ForwardingLogReader

Potentially fixes https://github.com/flutter-tizen/flutter-tizen/issues/260.

Create ForwardingLogReader according to the embedder side change https://github.com/flutter-tizen/engine/pull/203 and remove TizenDlogReader. The tool doesn't rely on the device dlog any more and uses the forwarding logger only.
Remove trailing newlines from engine arguments (flutter_app.cc).
Unsupport commands attach and logs. (The logging port can be only passed on app launch.)

Depends on https://github.com/flutter-tizen/engine/pull/203.

Rebased upon master.


allow tiffs with npages not dividing pageCount to be loaded

Currently if npages did not divide pageCount a value error was raised.
This PR changes the behaviour of fromtiff such that now all the data apart from the last few remaining pages will be loaded. These remaining pages are ignored.

But will it raise a warning?
We had this happen to us, and we used it as an indication that something went wrong with the acquisition.

Currently it does not raise a warning - I can amend the PR such that it does.
Alternatively we could keep the default behaviour the same and add some form of keyword argument that tells you to discard the remaining frames if you want.
Thoughts? Curious what @freeman-lab thinks is best too

Thinking about at, I am still not sure what would happen if there is a missing volume in the middle of an acquisition, would the keys skip that time point?
I think it would be helpful to have a keyword argument to discard the frames, but in a way that we would know what happened.
Maybe for each dropped volume a warning would display (In file xxx.tif dropped y frames) or the key would be skipped.


trigger posix tests

Signed-off-by: Dimitris Karnikis<EMAIL_ADDRESS>

@angelhof @nvasilakis @mgree I think the CI is ok. I will try to add some log functionality for posix tests

To view the posix logs:
# fetch the last 50 requests
curl -s "ctrl.pash.ndr.md/job=fetch_runs&count=50" > dat.json`
# find the hash we are interested in
cat dat.json | jq -r '.rows | .[] | select(.commit=="3e44744f") | .tests' | jq . | jq -r '.[].posix_log'

And it will print a dump of text :)
@angelhof

To view the posix logs:
# fetch the last 50 requests
curl -s "ctrl.pash.ndr.md/job=fetch_runs&count=50" > dat.json`
# find the hash we are interested in
cat dat.json | jq -r '.rows | .[] | select(.commit=="3e44744f") | .tests' | jq . | jq -r '.[].posix_log'

And it will print a dump of text :)

Great!

I don't know how GH actions does it, but can we store the resulting journal (or its summary) as a workflow artifact?

I don't know how GH actions does it, but can we store the resulting journal (or its summary) as a workflow artifact?

I can totally try that. This CI (running all the tests including posix), runs on every commit (on a PR).
I think this might be an issue since a new artifact will be generated every time we push something on a branch.
Moreover, all the CI logs (of posix tests) are stored in a postgres database, thus we could fetch every single one of the stored entries (including commit hash/message/branch/date and journal log) using curl requests as shown in my previous message. What do you think about that?

That's fine, I suppose. An advantage of the artifacts is (a) backup on GH servers and (b) easy browsability. Postgres seems nice in that it'd be great to generate charts of conformance over time. I'm easy.

The latest update builds and uploads a zip containing the execution logs(journal) of posix tests + the results of correctness tests.
The artifact is available when clicking on:

POSIX-CI / issue-jobs (pull_request_target)
Summary (on bottom)

OR by visiting the Actions Tab and finding the requested workflow

This is awesome, thank you for working it out!


  I have to run babel-node local on the project and can't find a good way to get this done without installing babel globally.  Being able to execute npm scripts would give much more flexibility.

@trainerbill I do not understand how npm scripts should be used to replace the need for the debugger to find the node.js executable? can you please elaborate?

I switched to VS code and really don't remember why this didn't work.


staging-next 2024-03-01

Helpful links

workflow docs: https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#staging
important jobs:
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
jobsets:
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
nix-review reports: https://malob.github.io/nix-review-tools-reports/
previous staging-next: https://github.com/NixOS/nixpkgs/pull/289734

Mass breakages

[x] libbacktrace is failing since xz: 5.4.6 -> 5.6.0; https://github.com/ianlancetaylor/libbacktrace/issues/118;

(will be edited based on progress)

There's an inconsequential pkgs/by-name check failure with this PR, here's a PR to fix it though: https://github.com/NixOS/nixpkgs/pull/292674

I suspect that would say to install everything into $dev, which wouldn't be what we want.

[ ] python3Packages.debugpy tests hang
https://hydra.nixos.org/build/252462132
Looks like a reproducible regression against nixpkgs master, for both linuxes and both pythons
maintainer: @kira-bruneau

A regularly complaint about debugpy tests: https://github.com/NixOS/nixpkgs/issues/262000

Oh OK, let me disable them for now: e0008b48c915

Overall I don't expect large improvements within days, so let's merge.


TypeScript types are not reloaded in editors

When changing the schema and regenerating the client, VSCode and other editors don't pick up the change in the TypeScript types.
This is not necessarily a bug in Prisma, but it significantly affects the developer experience.
Reproduction
mkdir repro
cd repro
npx @timsuchanek/auto prisma
// open vscode and open main.ts
// edit schema.prisma
// run prisma generate
// types are not updated
// try to trigger reload by hand like so:
rm -rf node_modules && yarn
// now PrismaClient is even typed `any`

@timsuchanek is that a duplicate of https://github.com/prisma/prisma/issues/2771 ?

@Jolg42 no, this is an actionable specific issue with a reproduction that can be closed, while #2771 is a more general issue.

This issue is fixed by https://github.com/prisma/language-tools/pull/357 for VSCode.

Any way to fix it in Webstorm? I'm having the exact same issue, and I have to delete node_modules and install again

I think this is a workaround for Webstorm: https://github.com/prisma/prisma/issues/2359#issuecomment-739921212

I am going to close this as this no longer happens in VSCode. If this is happening for your editor, please open a new issue about that.

@pantharshit00 I think this still happens with VS Code but is solved by using the Prisma extension:
https://marketplace.visualstudio.com/items?itemName=Prisma.prisma


Update hash for emcpy; fix mapscatter syntax

Description
This PR closes issue #77
@EdwardSafford-NOAA found that there is a syntax issue with EMCpy now if using a more recent version in EVA. This PR bring EVA up to date with EMCpy.
Dependencies
None
Impact
Tagging @danholdaway as he may want to use a new EVA tag for SWELL soon...

@EdwardSafford-NOAA I can't make you a reviewer because I don't have admin privileges and you aren't added to this repo 'officially'. But could you test and report results back here?

@CoryMartin-NOAA With these changes test/testIodaObsSpaceAmsuaN19.yaml runs to completion.
As you pointed out earlier the change that was made to map_scatter.py also needs to be made to map_gridded.py.   I may have overlooked it but I haven't found a test case that uses map_gridded.py, so I don't think there is an easy way to test that.

I've merged to get things working again. But I thought we were referring to a specific commit of EMCpy. How could that commit being referenced change and the eva tests have passed in whatever PR did that?

I am not sure, but I noticed the issue on Orion. Perhaps when you pip install it doesn't update the commit automatically if it already is installed?

@danholdaway actually seems the more likely scenario is "user error" aka me, I think I installed the update eva first, then installed emcpy, which defaulted to develop in the virtual environment...

OK. Thanks for the info.


interesting chat bot application in education

From @weAllWeGot on March 30, 2017 3:58
https://medium.com/@reachfund/why-we-invested-in-admithub-466801acbe99
Copied from original issue: weAllWeGot/kbai_chat_bot3#57

https://www.class-central.com/mooc/648/coursera-new-models-of-business-in-society#course-all-reviews
wonder if there is a way to get this raw data


Conflicting information on AllowAdHocSubscriptions

The article states (emphasis mine):

Flow and PowerApps trial sign-ups are not controlled by the AllowAdHocSubscriptions setting. For more information, see the following articles:
 How can I prevent my existing users from starting to use Power BI?

The referenced article however states:

To disable automatic license distribution for existing users: Set-MsolCompanySettings -AllowAdHocSubscriptions $false

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

ID: 06c24fd7-43ce-1445-b734-ffd28410911f
Version Independent ID: b835d64a-a78a-95d9-11a7-8b93a23944c8
Content: Self-service sign-up for email-verified users - Azure AD
Content Source: articles/active-directory/users-groups-roles/directory-self-service-signup.md
Service: active-directory
Sub-service: users-groups-roles
GitHub Login: @curtand
Microsoft Alias: curtand

@Jared-Harrington-Gibbs , thanks for the question. We're investigating this and will get back to you shortly.

Hi @Jared-Harrington-Gibbs
You're right. Those are old references. I removed the explicit mention of Flow not working with the cmdlets but left the link to Flow and how it works in the article. the update will be published this afternoon, live by 4 PM PDT.
Thanks for your input! Good catch.
@HarshitaSingh-MSFT
#please-close.

Thanks @curtand for providing updates from PG. This helps.
CC: @Jared-Harrington-Gibbs


Add http clients to test proxy

Fixes two bugs:

Use the default HTTP client for record/playback. This should eliminate many header mismatch errors.
Prevent getting record/playback objects in LIVE mode. At least some tests have been adding a record policy to anything that was not PLAYBACK. In the old record path this was a no-op. In the new path even if we made the recording step a no-op there would still be lots of work starting up the proxy, etc. Arguably tests that were doing this have a bug: there's no reason to have added a record policy to LIVE, so I'm preventing it.

See the wiki for details about this and other potential issues.
This does not yet enable using more than one HTTP client for playback/record. That's a feature request we'll do in the future.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-core-test


Not adding new contacts in ChatsFragment

If a user remains online in the chats list and gets a message from a user who didn't send a message before, a message will not add to ChatsAdapter most of the time.
I checked, and the server has sent new sub information with WebSocket, but the android version of the project didn't work.
How to test?
Create two users, get them online and send from one of them to another for the first time when the second is online.

I cannot reproduce. Could you please send me step by step instructions how to reproduce the issue reliably or send client-side logs.


[WIP] Replace weak refs by explicit cycle breaking where possible.

Throughout the codebase, we were liberally using weak references to
break all possible ref cycles, even those that are temporary and should
be broken explicitly. Other weak refs are there just for no good reason,
just to signify that we don't expect an object to lose all other
references to it before our reference is lost.
This by itself results in brittle code. The default should be strong,
which ensures a reference won't disappear before you expected. In other
cases, a more explicit handling of the reference lifecycle (e. g.
explicitly calling a "close" or "cancel" method) makes things clearer.
This PR removes all weak references except those where there's a stable
cycle and the ownership relationship between the objects in the cycle
is clear; for example, ARTRealtime clearly "owns" ARTRest, insofar their
lifetimes are entangled: ARTRealtime initializes ARTRest, and when the
ARTRealtime is released, so should be its ARTRest, which should have no
other references to it. All those cases have been documented.
In some places, we relied on weak references to implicitly invalidate
timers, enqueued operations and things like that. The pattern looks like
this:
__weak MyClass *weakSelf = self;
scheduleBlockToBeCalledLater(^{
    [weakSelf someMethod];
});

The intent here is to cancel scheduled operations on the object if we
stop being interested in the object. And this "interest" is expressed
as holding a reference to the object somewhere.
This way we're forcing the user to hold on to their reference to (say)
ARTRealtime even if they're not going to use it anymore. That's not
what one would expect in a garbage-collected language, in which other
client libraries are written. In those, you would explicitly call
realtime.close if you want it to stop operating.
So this change makes this behavior uniform with other client libraries,
but now we're forced to explicitly unschedule the operations on close.
For this, a little helper class called ARTFlusher to register things
that should be "flushed" (cancelled, emptied, etc.) once we call "close"
or similar on the object they operate on. We flush this way event
listeners, timers, enqueued messages, etc. related to a realtime or
realtime channel instance.

I'm closing this because Realtime.close isn't really the "cleanup everything" method I assumed it is. Event emitters, channels, etc. shouldn't be "flushed" on a close, they should be flushed once the Realtime object is really done with, but a Realtime can be reused after a close.
So if we shouldn't use Realtime.close, what should we use instead?
After #882, there will be a hard barrier between user-referenced objects and internally-referenced objects. In particular, if user code drop all references to a (Public)Realtime object, since internal code won't hold any references to it, it will be deallocated. This is in contrast to now, when internal code may be referencing the same object as user code, preventing a deallocation.
So we should leverage this by breaking the cycles when the (Public)Realtime object is deallocated, ie. call the equivalent of [_flushOnClose flush] on the (Public)Realtime.dealloc method, since the user dropping all references to Ably objects is what means "cleanup everything" (except timers, which still need to be released with Realtime.close), as it does in client libraries for garbage-collected languages.
So this PR should be revived, if at all, after #882 is done.

Yes, if this was C++ I'd be expecting to release resources (other than those associated with the connection itself) in delete.

Actually, the whole flush thing is misguided. The flushed things that may hold reference cycles are either timed operations that will eventually execute or be cancelled, so it's OK for them to be strong, or indefinitely-lived event listeners that after #882 should go back to weak references, since either the user or the transport will prevent referenced objects (Rest, Realtime, or an owned child) to be released before the event listener that reference them is executed.
So this PR should then be adapted to just remove unnecessary weak refs, ie. weak refs that resolve no cycle at all or that resolve cycles that are solved in some other way anyway.


[SMALLFIX] Fix test with -PhdfsTest

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15301/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15302/
Test FAILed.

Jenkins, test this please.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15303/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15304/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15305/
Test PASSed.


Send undefined query

const qs = { a: undefined, b: 1 };
request.get('my-url').query(qs).end();
// version 4.1.0
send my-url?b=1
// version 5.0.2
send my-url?a=undefined&b=1
I tested it on chrome 73.0.3683.103

Can we get a confirmation on whether or not this is a bug or expected behavior?
This can have all sorts of downstream consequences, so we have pinned this package to 4.x for now. I'm trying to decide if this is the responsibility of the caller, in which case we'll need to address it across our services, or if we should wait for a fix.
One data point is that this new behavior does not have parity with JSON.stringify:
const qs = { a: undefined, b: 1 };
JSON.stringify(qs); // "{"b":1}"

Note that the result has the key whose value is undefined omitted rather than set to the string literal "undefined" (tested in Chrome and Node v10.9.0).

The current behaviour in Node and browsers is different. +1 for retaining backward compatible(omit undefined fields).

The node implement uses qs to encode queryString. qs omits undefined properties entirely: https://github.com/ljharb/qs/blame/b84acbab2c414658f15339c9e61cf9941d9d391f/README.md#L392-L396
qs.stringify({ a: null, b: undefined }) //=> 'a='

The browser implement(v4) behaves exactly the same with qs:
function pushEncodedKeyValuePair(pairs, key, val) {
  if (val != null) {
    // push value to paires
  } else if (val === null) {
    pairs.push(encodeURIComponent(key));
  }
}

v5 changes the first condition:
function pushEncodedKeyValuePair(pairs, key, val) {
- if (val != null) {
+ if (val !== null) {
    // push value to paires
  } else if (val === null) {
    pairs.push(encodeURIComponent(key));
  }
}

It looks like a unintentional change(to conform with eslint maybe) to me.

This is preventing me from upgrading to v5, sticking with v4 for now.


Differ alpha analysis

Currenlty, name changes are reported as braking compat. This should not be.
However reporting name changes would be good to keep.
The best option would be to:

[x] fix compat analysis
[ ] add a new renaming analysis

The compat logic has been updated in 87a50f7.

What was mentioned a renaming could be covered by a new signature analysis.


[RfR] Disable create account btn after submission [OSF-5816]

Purpose
Prevent registration of the same account multiple times.
Changes
Disable create account when the form is submitted
Side effects
None
Ticket
https://openscience.atlassian.net/browse/OSF-5816
[OSF-5816]

Looks good @barbour-em! As an additional level of precaution, in the submit function, can you show an error message if the user already hit submit?

@samanehsan added in bb20b1e. Hopefully the unrelated tests will pass this time.

Pass complete @barbour-em! 🌴

@samanehsan, I missed this comment at first. Changes made.

Thanks for making those changes @barbour-em! This is good to merge! :octocat:


[gardening] Standardize SILBasicBlock successor/predecessor methods that deal with blocks rather than the full successor data structure to have the suffix 'Block'.

[gardening] Standardize SILBasicBlock successor/predecessor methods that deal with blocks rather than the full successor data structure to have the suffix 'Block'.
This was already done for getSuccessorBlocks() to distinguish getting successor
blocks from getting the full list of SILSuccessors via getSuccessors(). This
commit just makes all of the successor/predecessor code follow that naming
convention.
Some examples:
getSingleSuccessor() => getSingleSuccessorBlock().
isSuccessor() => isSuccessorBlock().
getPreds() => getPredecessorBlocks().
Really, IMO, we should consider renaming SILSuccessor to a more verbose name so
that it is clear that it is more of an internal detail of SILBasicBlock's
implementation rather than something that one should consider as apart of one's
mental model of the IR when one really wants to be thinking about predecessor
and successor blocks. But that is not what this commit is trying to change, it
is just trying to eliminate a bit of technical debt by making the naming
conventions here consistent.

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 274c3013550788560f4fb9b0659460255d303f36
Test requested by - @gottesmm

The linux failure is a type checker issue. I do not know why it is failing with this commit which only affects SIL. I am going to try one more time to see if it is non-deterministic and then I am going to wait to see if the Linux builders hit this.

@swift-ci Please test linux platform

Ah ok, it is non-determinstic. CodeFi is fixing it in dfa372300d2f47845f2aac7c137ac793a74f1aee.

I rebased ontop of his commit. Lets do this again...

@swift-ci Please test and merge

@swift-ci Please test and merge

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 274c3013550788560f4fb9b0659460255d303f36
Test requested by - @gottesmm

@gottesmm Anything that can be done about the LLDB test that has been failing in the full test for a while now?

@swift-ci Please smoke test linux platform

@CodaFi I imagine that it should be disabled until the LLDB team has time to look at it.
@llvm-beanz @tfiala thoughts?

@swift-ci Please smoke test linux platform


Crash on bad ZIP code

There were 2 wrong ZIP codes in our case (swapped City name and ZIP code). Module stopped at https://github.com/MonkeyData/php-opencart-xml-feed-generator/blob/master/admin/XmlGenerator/Model/XmlModel.php#L207
and produced incomplete XML.

Thank you for your feedback, we already fixed it. MD


you can generate json schema with non-unique keys

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
following code does not throw an exception, although else alias is used two times.
jsonschema does not accept generated schema.
Example Code
class Eval(BaseModel):
    stage: Literal["eval"]
    evals: Optional[Dict[str, List["Stage"]]] = Field(validation_alias=AliasChoices("else"))
    elist: Optional[List["Eval"]] = Field(validation_alias=AliasChoices("list"))
    eelse: Optional[List["Stage"]] = Field(validation_alias=AliasChoices("else"))

Python, Pydantic & OS Version
pydantic version: 2.3.0
        pydantic-core version: 2.6.3
          pydantic-core build: profile=release pgo=false
                 install path: C:\Data\Projects\pyenv\Lib\site-packages\pydantic
               python version: 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)]
                     platform: Windows-10-10.0.19045-SP0
     optional deps. installed: ['typing-extensions']

Hi @Pymann,
Thanks for reporting this. The only issue that I see with the generated json schema is that there are duplicates in the required list of fields.
What specifically are you expecting to happen here - do you want an error to be raised, or the json schema to be different in some way?
Happy to help once we get some more info 😄.

@Pymann,
Thanks again for reporting. Any update on what you'd expect to happen here?

@Pymann closing for now due to inactivity. Happy to reopen if you have a suggestion / request for alternate behavior.


Builds all the files in source\samples

If main.cpp has a function "void onButtonA( MicroBitEvent e) { }" it won't build because of a clash with source/samples/ButtonTest.cpp.

yep - we should declare the tests as static...


Add integration testing for get_block_number syscall.

Codecov Report

Merging #123 (458e203) into main (6aba66b) will increase coverage by 3.72%.
The diff coverage is 72.34%.

@@            Coverage Diff             @@
##             main     #123      +/-   ##
==========================================
+ Coverage   64.57%   68.29%   +3.72%
==========================================
  Files          30       32       +2
  Lines        1575     1820     +245
==========================================
+ Hits         1017     1243     +226
- Misses        558      577      +19

Impacted Files
Coverage Δ

src/business_logic/execution/gas_usage.rs
97.43% <ø> (ø)

src/business_logic/execution/os_usage.rs
0.00% <ø> (ø)

src/business_logic/fact_state/state.rs
8.23% <0.00%> (+0.62%)
:arrow_up:

src/business_logic/state/contract_storage_state.rs
92.85% <ø> (ø)

src/business_logic/state/state_cache.rs
97.67% <ø> (ø)

src/business_logic/state/update_tracker_state.rs
0.00% <0.00%> (ø)

src/business_logic/transaction/internal_objects.rs
0.00% <0.00%> (ø)

src/business_logic/transaction/state_objects.rs
0.00% <ø> (ø)

src/core/block_hash/starknet_block_hash.rs
88.23% <ø> (ø)

src/core/syscalls/syscall_info.rs
100.00% <ø> (ø)

... and 20 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Depends on #130.


add build.zig

Added a build.zig which enables building cross-compiling to/from any major platform (i.e. windows/linux/macos).  For example, with this I was able to build and run this on MacOS, and cross compile it to windows from macos.
In general, the benefit of using build.zig is that your project has only 1 build-time dependency, zig, which is about an 80 MB download.  This is in contrast to other toolchains which typically require hundreds of packages or complex fragile installations (Visual Studio) that have many tentacles into your system.  Zig's only dependencies are contained within the archive it deploys.

Oh yeah! Thank you for reminding me about https://github.com/tsoding/nobuild I should definitely use it here!

Thanks! Worked great -- easy for me to build on macos.

I really like the idea of nobuild.  It's going to take alot of work to support all the platforms/compilers/etc on the level Zig is currently at, but I think it's a worthy endeavor.  One thing to note is that this build.zig file automatically downloads raylib via https, I'm guessing nobuild isn't going to try to include a TLS implementation to be able to do the same?

I personally don't particularly like this trend of populating Open Source projects with as many building options as possible. CMake, zig, nix, etc, etc. Do we really have to add every single new shiny thing that got upvoted on that old orange website?
I believe a project should provide one official build option and all the unofficial ones should be kept somewhere else. Similar to how Gentoo organizes Portage or something. My official stance is: Do whatever you want, but somewhere else, okay? Good!

Really cool that you were able to add multi-platform support with nob.h, I look forward to see how it progresses!


Use proper attribute types when delegating to accumulator in drawDisplayList

see: https://github.com/flutter/engine/pull/37435#discussion_r1017117593

The use of kDrawDisplayListFlags here is problematic as it isn't clear if the attributes assigned to an entire display list apply to each individual rectangle.

For now, we don't apply any attributes, but in the future we might apply attributes and they can't necessarily be distributed like that. So, this works presently, but is a potential logic time bomb. Minimally a comment should be added to mention this discrepancy.

see: https://github.com/flutter/engine/pull/37451


fix: set header keys to be lowercase for consistency

Depending on your clients, sometimes headers are sent as either "Authorization" or "authorization", either capitalized or all lower case. Because of this, would be good to not have to make that mistake. So by default we always lowercase the header keys.

I would love to see this PR merged!  I‘ve seen several codebase comments referencing this issue like:
    // TODO: Once https://github.com/sst/sst/pull/2838 is merged,
    // then we should no longer need to check both casing for the header.

  // WebSocket may also set the token in the protocol header
  // TODO: Once https://github.com/sst/sst/pull/2838 is merged,
  // then we should no longer need to check both casing for the header.

Plus, I’m checking for both header casings in my personal sites too.

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


Starting to change parts to MIT license

I want to put parts of advancedfx repository under the MIT license.
Thus I am starting to split advancedfx repository into modules.
@YaLTeR @nkoep @Snaacky - please tell me if you agree putting your contributions under the MIT license (you will be mentioned in the LINCENSE file of the modules that have source code you contributed to as Copyright holder, the year will be the one of your last contribution)
If you don't reply or say no, I will have to rewrite or remove code (I'd like to avoid that if possible).

I agree with my contributions being relicensed under the MIT license.

I also am asking Mirvin_Monkey btw, the original MDT (old name of HLAE) author back in 2007, but I didn't mention him above, since he doesn't have a GitHub account I know off.
Not sure what he will say though and if he will agree or not.

Mirvin_Monkey told me by email he is fine with having his contributions under an MIT license (and him being mentioned as copyright holder), the only problem is that some of them are taken from some examples and only adjusted by him, so I need to take some care in regards to those code snippets.

No objections from my side


apt-get

https://github.com/JDAI-CV/fast-reid/blob/10a5f38aaa0d4e86b542dfad954d15eab8d5c6de/docker/Dockerfile#L8
I enter the docker and command "apt-get install htop"
But the system  say permission denied.
How can I do with apt-get install

So, it can use the sudo in the docker?


getting java.lang.NoSuchMethodError on saveAsBigQueryTable

Hi,
I'm using the 0.2.5 version and getting an error:

any ideas?
I do able to DML...

i also see this warning:


ECMAScript 6

Not sure the best set-up for syntastic and ES6 and whether the older issues are out of date?

Not sure the best set-up for syntastic and ES6

At the time of this writing syntastic is a one-man show.  As such, it doesn't offer recipes for the various languages, much less advise of the "best of" kind.  Please read the manual and make sure you're running the checkers you want, with the options you want.  When you're done write a blog post about your setup if you have time to spare.

whether the older issues are out of date

If you find an issue with the current master HEAD please feel free to report it.  Make sure to explain what did you do, what did you expect to happen, and what happened instead.

JSHInt and
{
  "esversion": 6
}

in ~/.jshintrc seems to work and is suggested on stackoverflow.


Use PyShiny, not py-shiny or for installation packages.  Hyphens in object names is not Pythonic

Please use the name PyShiny, not py-shiny or anything else for the names of installation packages.  This is a bad naming practice for Python packages.  Putting hyphens in the middle of a string or object name is not Pythonic, because "-" can be interpreted as a "minus sign".  Please use good Python engineering practices.  See PEP8 for more details:  https://peps.python.org/pep-0008/

Thanks for the feedback. The package name is just shiny. Only the GitHub repo is py-shiny.


The wallet shows only the Near logo and footer before the account state is loaded

At this moment Near logo and footer are showing immediately after the page loaded, and then we wait for the account state to be loaded before the rest of UI is shown. This is because we want to be sure if the Landing page (no account) or Dashboard should be shown.
The idea is to improve this process, by:

First check if there is info about the account in the localStorage, and if so, we can show menu options and some other basic UI, before the account state is loaded.
If there is no info about the account in localStorage, we show the Landing page.

What is the issue from the user's point of view?

What is the issue from the user's point of view?

The user needs to wait 1-2 seconds (or longer if the network is slow) before anything other than the logo and footer is shown.

Thanks, added a priority 2, as the absence of this feature can generate an unnecessarily high number of tickets if the RPC is temporarily slow or unresponsive.
Also, it's possible that in certain geographic areas this delay is higher anyway.
This issue reminds me of similar sync/async issues, such as the "name is unavailable" in #634 and #1506

@jimmy3dita I suggest we put it as P1 as the issue is pretty bad if you aren't on excellent network or RPC is slow, e.g. @ilblackdragon is totally frustrated with it in China.
This is something that lies on a critical path to success (like paying for something using NEAR).


Remove redundant code, since managed object has been saved already.

Minor fix.

Good catch, thanks!


chore: replace Berry Pool references, update licence to Apache 2.0

Replace MIT licence with Apache 2.0, aligning with IOG standards
Fix link to repository in package.json
Update docs to indicate IOG as new maintainers

README looks good 👍 thanks @rhyslbw


701 update C++-14 branch changelog as preparation of a v3.6.2 release

Brought changelog up-to-date with merged set of changes from v3.7.4 plus the ones only merged to c++14-compliant as preparation of a v3.6.2 release.
This is based on https://github.com/CppMicroServices/CppMicroServices/blob/master/CHANGELOG.rst#v374-2022-10-12, but I added all the major PRs that I merged, compared to the statement there that half of the merged PRs were not included in the release. I am a bit confused about that statement and still wondering whether the 3.7.4 entry in the master changelog is correct or not.
Are there any additional PRs that you would recommend to be merged from current development to still be merged on top of this for a v3.6.2, or do you think it is better to closely follow the main versions?
This also contains the same whitespace cleanup as PR #812, which somehow was missing from PR #809.

Brought changelog up-to-date with merged set of changes from v3.7.4 plus the ones only merged to c++14-compliant as preparation of a v3.6.2 release.
This is based on https://github.com/CppMicroServices/CppMicroServices/blob/master/CHANGELOG.rst#v374-2022-10-12, but I added all the major PRs that I merged, compared to the statement there that half of the merged PRs were not included in the release. I am a bit confused about that statement and still wondering whether the 3.7.4 entry in the master changelog is correct or not.

the master branch changelog does look correct. The main branch is overdue for a new release from development. I'm planning on updating the main branch to the latest from development next week.

Are there any additional PRs that you would recommend to be merged from current development to still be merged on top of this for a v3.6.2, or do you think it is better to closely follow the main versions?
This also contains the same whitespace cleanup as PR #812, which somehow was missing from PR #809.

I would recommend everything up through https://github.com/CppMicroServices/CppMicroServices/commit/b2030d260e58b9128ce3a7a36fa617fad60a50b2. I'm planning on updating the main branch and releasing next week up through this commit.
I think it is probably safest to follow the main branch even though we do keep the development branch in a near production ready state. There have been a couple occasions where we've had to roll a commit back due to an unforeseen issue integrating CppMicroServices into our larger code base at MathWorks.
Generally we take the development branch at different points in time and integrate into the larger MathWorks code base, do qualifications and if the code passes the quality checks, we then release the development branch into the main branch.

Brought changelog up-to-date with merged set of changes from v3.7.4 plus the ones only merged to c++14-compliant as preparation of a v3.6.2 release.
This is based on https://github.com/CppMicroServices/CppMicroServices/blob/master/CHANGELOG.rst#v374-2022-10-12, but I added all the major PRs that I merged, compared to the statement there that half of the merged PRs were not included in the release. I am a bit confused about that statement and still wondering whether the 3.7.4 entry in the master changelog is correct or not.

the master branch changelog does look correct. The main branch is overdue for a new release from development. I'm planning on updating the main branch to the latest from development next week.

@jeffdiclemente: just for my understanding:
I've explicitly looked at the difference between the v3.7.4 tag and the v3.7.2 one (https://github.com/CppMicroServices/CppMicroServices/compare/v3.7.2...v3.7.4) for collecting the PRs I would want to merge. A large chunk of those is listed as "not included in the release" in the v3.7.4 changelog entry.
Does that mean that the v3.7.4 release and the v3.7.4 tag have different content?
because I can see that those PRs are part of the v3.7.4 tag - so the "not included in the release" statement in the v3.7.4 release notes on master really confuses me.

Brought changelog up-to-date with merged set of changes from v3.7.4 plus the ones only merged to c++14-compliant as preparation of a v3.6.2 release.
This is based on https://github.com/CppMicroServices/CppMicroServices/blob/master/CHANGELOG.rst#v374-2022-10-12, but I added all the major PRs that I merged, compared to the statement there that half of the merged PRs were not included in the release. I am a bit confused about that statement and still wondering whether the 3.7.4 entry in the master changelog is correct or not.

the master branch changelog does look correct. The main branch is overdue for a new release from development. I'm planning on updating the main branch to the latest from development next week.

@jeffdiclemente: just for my understanding: I've explicitly looked at the difference between the v3.7.4 tag and the v3.7.2 one (v3.7.2...v3.7.4) for collecting the PRs I would want to merge. A large chunk of those is listed as "not included in the release" in the v3.7.4 changelog entry. Does that mean that the v3.7.4 release and the v3.7.4 tag have different content?
because I can see that those PRs are part of the v3.7.4 tag - so the "not included in the release" statement in the v3.7.4 release notes on master really confuses me.

It looks like the v3.7.4 tag was incorrectly created from the development branch instead of master. That would explain the skew between the tag and the changelong on master. I'll fix this up next week. Regardless, the PRs you've already pulled into v3.6.2 are well tested and stable.

@jeffdiclemente: just for my understanding: I've explicitly looked at the difference between the v3.7.4 tag and the v3.7.2 one (v3.7.2...v3.7.4) for collecting the PRs I would want to merge. A large chunk of those is listed as "not included in the release" in the v3.7.4 changelog entry. Does that mean that the v3.7.4 release and the v3.7.4 tag have different content?
because I can see that those PRs are part of the v3.7.4 tag - so the "not included in the release" statement in the v3.7.4 release notes on master really confuses me.

It looks like the v3.7.4 tag was incorrectly created from the development branch instead of master. That would explain the skew between the tag and the changelong on master. I'll fix this up next week. Regardless, the PRs you've already pulled into v3.6.2 are well tested and stable.

Ok, so potentially only the description in the 3.6.2 changelog needs to be updated, as I then seem to have not added the real 3.7.4 content, but a bit more. Interestingly, the only difference between master and the v3.7.2 tag is the changelog entry, so the tag couldn't have been created from master.


Apply new naming

Applied new naming for the main module.

@SaeedRe please redo this on top of master:
https://github.com/Kynetics/uf-service-api-reference-implementation


fix(bridge-ui): show instant feedback when insufficient balance

Before:
We currently disable the transfer bridge button, but the user might not realize the reason why the button remains disabled...
After:
Shows instant warning whenever user types balance is lower than what's intended to be transferred (including estimated fees).

@jscriptcoder could you please take a look at this?

@jscriptcoder could you please take a look at this?

Yeah, left a comment yesterday. We could merge it and then I take care of the change or @deepaksing might want to take a look.

@jscriptcoder could you please take a look at this?

Yeah, left a comment yesterday. We could merge it and then I take care of the change or @deepaksing might want to take a look.

If it is a small change, we can change it?

@jscriptcoder could you please take a look at this?

Yeah, left a comment yesterday. We could merge it and then I take care of the change or @deepaksing might want to take a look.

ya, i can work on the required changes.

@jscriptcoder could you please take a look at this?

Yeah, left a comment yesterday. We could merge it and then I take care of the change or @deepaksing might want to take a look.

ya, i can work on the required changes.

Any update or ETA?

Can we hold off this PR until we have devnet to test?
cc: @deepaksing @dantaik


NCBI taxids not matching

Hi
Firstly I have found the documentation and usage of mmseqs2 for taxonomic assignment to be extremely good and easy to follow!
However, just a quick point that some of the ncbi taxids given do not match the LCA scientific name.
Below is the output from createtsv from some of my assignments. From previous sequencing I am pretty sure the LCA scientific name (taxa here) is correct, but the ncbi taxa ID do not link to the correct name. For example, there is no tax id for 19759 according to my search here.

tax_id
taxonomic_level
taxa
tax_id_all

58962
species
Achromobacter veterisilvae
2;3;4;46;62;468;58962

2
superkingdom
Bacteria
2

6620
species
Ochrobactrum B soli
2;3;79;91;92;6619;6620

92
family
Rhizobiaceae A
2;3;79;91;92

76
genus
Pseudomonas E
2;3;4;29;30;76

180
genus
Stenotrophomonas
2;3;4;127;128;180

19759
species
Variovorax sp003019815
2;3;4;46;62;2887;19759

I met the same question,
taxid:3177
taxon_name: species Ruminococcus E sp003526955
3177 can't found in the NCBI taxonomy databse.
@milot-mirdita


🐛 FlutterFire_UI 3rd party transitive dependencies causing build to fail

Bug report
Describe the bug
Ever since I installed flutterfire_UI I'm getting warnings and errors for 3rd party social plugins. like flutter_facebook_auth and sign_in_with_apple and its causing errors in my app now
FAILURE: Build failed with an exception.

* What went wrong:
The Android Gradle plugin supports only Kotlin Gradle plugin version 1.5.20 and higher.
The following dependencies do not satisfy the required version:
project ':sign_in_with_apple' -> org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.50

Steps to reproduce
Steps to reproduce the behavior:
Install flutterfire_ui while NOT using any 3rd party social plugins like facebook, apple or google
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
I dont want to, nor do I plan to use any 3rd party logins but firestores basic authentication. How do I remove or disable these references so I can build my app

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, 3.4.0-19.0.pre.118, on Microsoft Windows [Version 10.0.19044.1889], locale en-CA)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc1)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2022 17.1.0)
[√] Android Studio (version 2021.2)
[√] Connected device (5 available)
[√] HTTP Host Availability

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.19.0-171.0.dev
Flutter SDK 3.4.0-19.0.pre.118

dependencies:
- animated_splash_screen 1.3.0 [flutter page_transition]
- animations 2.0.4 [flutter]
- audio_waveforms 0.1.4 [flutter]
- avatar_glow 2.0.2 [flutter]
- awesome_dialog 3.0.0 [flutter rive]
- camera 0.9.4+2 [camera_platform_interface camera_web flutter pedantic quiver flutter_plugin_android_lifecycle]
- cloud_firestore 3.4.6 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- connectivity_plus 2.3.6+1 [flutter connectivity_plus_platform_interface connectivity_plus_linux connectivity_plus_macos connectivity_plus_web connectivity_plus_windows]
- convex_bottom_bar 3.0.0 [flutter]
- elliptic_text 1.0.1+9 [flutter]
- file_picker 5.0.1 [flutter flutter_web_plugins flutter_plugin_android_lifecycle plugin_platform_interface ffi path win32]
- firebase_analytics 9.3.3 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 3.7.0 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.21.1 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_messaging 13.0.0 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_storage 10.3.7 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- flutter_advanced_networkimage_2 2.0.1 [flutter http path_provider path flutter_svg pool async]
- flutter_inset_box_shadow 1.0.8 [flutter]
- flutter_local_notifications 9.9.1 [clock flutter flutter_local_notifications_linux flutter_local_notifications_platform_interface timezone]
- flutter_markdown 0.6.10+5 [flutter markdown meta path]
- flutter_screenutil 5.5.4 [flutter]
- flutter_secure_storage 6.0.0 [flutter flutter_secure_storage_linux flutter_secure_storage_macos flutter_secure_storage_platform_interface flutter_secure_storage_web flutter_secure_storage_windows meta]
- flutter_svg 1.1.4 [flutter meta path_drawing vector_math xml]
- flutter_zoom_drawer 3.0.3 [flutter]
- flutterfire_ui 0.4.3+7 [cloud_firestore collection crypto desktop_webview_auth email_validator firebase_auth firebase_core firebase_database firebase_dynamic_links flutter flutter_facebook_auth flutter_localizations flutter_svg google_sign_in sign_in_with_apple twitter_login]
- font_awesome_flutter 10.1.0 [flutter]
- gallery_saver 2.3.2 [flutter path_provider http path]
- get 4.6.5 [flutter]
- hive 2.2.3 [meta crypto]
- hive_flutter 1.1.0 [flutter hive path_provider path]
- intl 0.17.0 [clock path]
- intl_phone_field 3.1.0 [flutter]
- overlay_support 2.0.1 [flutter async]
- page_transition 2.0.9 [flutter]
- path 1.8.2
- path_provider 2.0.11 [flutter path_provider_android path_provider_ios path_provider_linux path_provider_macos path_provider_platform_interface path_provider_windows]
- permission_handler 10.0.0 [flutter meta permission_handler_android permission_handler_apple permission_handler_windows permission_handler_platform_interface]- shimmer_animation 2.1.0+1 [flutter]
- sliding_up_panel 2.0.0+1 [flutter]
- video_compress 3.1.1 [flutter]
- video_player 2.4.7 [flutter html video_player_android video_player_avfoundation video_player_platform_interface video_player_web]

dev dependencies:
- build_runner 2.2.0 [args async analyzer build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_launcher_icons 0.10.0 [args checked_yaml cli_util image json_annotation path yaml]
- flutter_lints 2.0.1 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters collection matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]
- hive_generator 1.1.3 [build source_gen hive analyzer source_helper]

transitive dependencies:
- _fe_analyzer_shared 47.0.0 [meta]
- analyzer 4.7.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.3.1 [crypto path]
- args 2.3.1
- async 2.9.0 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- build 2.3.0 [analyzer async convert crypto glob logging meta path]
- build_config 1.1.0 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 3.1.0 [built_collection built_value http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.0.9 [analyzer async build crypto graphs logging path package_config pool pub_semver stream_transform yaml]
- build_runner_core 7.2.3 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta path package_config pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.4.1 [built_collection collection fixnum meta]
- camera_platform_interface 2.2.0 [cross_file flutter plugin_platform_interface stream_transform]
- camera_web 0.2.1+6 [camera_platform_interface flutter flutter_web_plugins stream_transform]
- characters 1.2.1
- charcode 1.3.1
- checked_yaml 2.0.1 [json_annotation source_span yaml]
- cli_util 0.3.5 [meta path]
- clock 1.1.1
- cloud_firestore_platform_interface 5.7.3 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 2.8.6 [cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- code_builder 4.2.0 [built_collection built_value collection matcher meta]
- collection 1.16.0
- connectivity_plus_linux 1.3.1 [flutter connectivity_plus_platform_interface meta nm]
- connectivity_plus_macos 1.2.4 [connectivity_plus_platform_interface flutter]
- connectivity_plus_platform_interface 1.2.1 [flutter meta plugin_platform_interface]
- connectivity_plus_web 1.2.3 [connectivity_plus_platform_interface flutter_web_plugins flutter]
- connectivity_plus_windows 1.2.2 [connectivity_plus_platform_interface flutter]
- convert 3.0.2 [typed_data]
- cross_file 0.3.3+1 [js meta]
- crypto 3.0.2 [typed_data]
- csslib 0.17.2 [source_span]
- dart_style 2.2.3 [analyzer args path pub_semver source_span]
- dbus 0.7.8 [args ffi meta xml]
- desktop_webview_auth 0.0.9 [crypto flutter http]
- email_validator 2.1.17
- fake_async 1.3.1 [clock collection]
- ffi 2.0.1
- file 6.1.4 [meta path]
- firebase_analytics_platform_interface 3.3.3 [firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.4.2+3 [firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 6.6.0 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 4.3.0 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.5.1 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 1.7.2 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_database 9.1.3 [firebase_core firebase_core_platform_interface firebase_database_platform_interface firebase_database_web flutter]
- firebase_database_platform_interface 0.2.2+3 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_database_web 0.2.1+5 [firebase_core firebase_core_web firebase_database_platform_interface flutter flutter_web_plugins js]
- firebase_dynamic_links 4.3.6 [firebase_core firebase_core_platform_interface firebase_dynamic_links_platform_interface flutter meta plugin_platform_interface]
- firebase_dynamic_links_platform_interface 0.2.3+11 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 4.1.3 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.1.3 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_storage_platform_interface 4.1.15 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.3.5 [async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- fixnum 1.0.1
- flutter_facebook_auth 4.4.1 [flutter flutter_facebook_auth_platform_interface flutter_facebook_auth_web]
- flutter_facebook_auth_platform_interface 3.2.0 [flutter plugin_platform_interface]
- flutter_facebook_auth_web 3.2.0 [flutter flutter_web_plugins js flutter_facebook_auth_platform_interface]
- flutter_local_notifications_linux 0.5.1 [flutter flutter_local_notifications_platform_interface dbus path xdg_directories]
- flutter_local_notifications_platform_interface 5.0.0 [flutter plugin_platform_interface]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math]
- flutter_plugin_android_lifecycle 2.0.7 [flutter]
- flutter_secure_storage_linux 1.1.1 [flutter flutter_secure_storage_platform_interface]
- flutter_secure_storage_macos 1.1.1 [flutter flutter_secure_storage_platform_interface]
- flutter_secure_storage_platform_interface 1.0.0 [flutter plugin_platform_interface]
- flutter_secure_storage_web 1.0.2 [flutter flutter_web_plugins flutter_secure_storage_platform_interface js]
- flutter_secure_storage_windows 1.1.2 [flutter flutter_secure_storage_platform_interface]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- frontend_server_client 2.1.3 [async path]
- glob 2.1.0 [async collection file path string_scanner]
- google_sign_in 5.4.1 [flutter google_sign_in_android google_sign_in_ios google_sign_in_platform_interface google_sign_in_web]
- google_sign_in_android 6.1.0 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.5.0 [flutter google_sign_in_platform_interface]
- google_sign_in_platform_interface 2.3.0 [flutter plugin_platform_interface quiver]
- google_sign_in_web 0.10.2 [flutter flutter_web_plugins google_sign_in_platform_interface js]
- graphs 2.1.0 [collection]
- html 0.15.0 [csslib source_span]
- http 0.13.5 [async http_parser meta path]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.1 [collection source_span string_scanner typed_data]
- image 3.2.0 [archive meta xml]
- io 1.0.3 [meta path string_scanner]
- js 0.6.4
- json_annotation 4.6.0 [meta]
- lints 2.0.0
- logging 1.0.2
- markdown 5.0.0 [args charcode meta]
- matcher 0.12.12 [stack_trace]
- material_color_utilities 0.2.0
- meta 1.8.0
- mime 1.0.2
- nm 0.5.0 [dbus]
- package_config 2.1.0 [path]
- path_drawing 1.0.1 [vector_math meta path_parsing flutter]
- path_parsing 1.0.1 [vector_math meta]
- path_provider_android 2.0.20 [flutter path_provider_platform_interface]
- path_provider_ios 2.0.11 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.7 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_macos 2.0.6 [flutter path_provider_platform_interface]
- path_provider_platform_interface 2.0.4 [flutter platform plugin_platform_interface]
- path_provider_windows 2.1.3 [ffi flutter path path_provider_platform_interface win32]
- pedantic 1.11.1
- permission_handler_android 10.0.0 [flutter permission_handler_platform_interface]
- permission_handler_apple 9.0.4 [flutter permission_handler_platform_interface]
- permission_handler_platform_interface 3.7.0 [flutter meta plugin_platform_interface]
- permission_handler_windows 0.1.0 [flutter permission_handler_platform_interface]
- petitparser 5.0.0 [meta]
- platform 3.1.0
- plugin_platform_interface 2.1.2 [meta]
- pool 1.5.1 [async stack_trace]
- process 4.2.4 [file path platform]
- pub_semver 2.1.1 [collection meta]
- pubspec_parse 1.2.1 [checked_yaml collection json_annotation pub_semver yaml]
- quiver 3.1.0 [matcher]
- rive 0.9.1 [collection flutter graphs http meta]
- shelf 1.3.2 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.2 [shelf stream_channel web_socket_channel]
- sign_in_with_apple 3.3.0 [flutter meta sign_in_with_apple_platform_interface sign_in_with_apple_web]
- sign_in_with_apple_platform_interface 1.0.0 [flutter plugin_platform_interface meta]
- sign_in_with_apple_web 1.0.1 [flutter flutter_web_plugins sign_in_with_apple_platform_interface js]
- sky_engine 0.0.99
- source_gen 1.2.2 [analyzer async build dart_style glob meta path source_span yaml]
- source_helper 1.3.2 [analyzer collection source_gen]
- source_span 1.9.1 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.0
- string_scanner 1.1.1 [source_span]
- term_glyph 1.2.1
- test_api 0.4.13 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timezone 0.8.0 [path]
- timing 1.0.0 [json_annotation]
- twitter_login 4.2.3 [flutter crypto http]
- typed_data 1.3.1 [collection]
- vector_math 2.1.3
- video_player_android 2.3.9 [flutter video_player_platform_interface]
- video_player_avfoundation 2.3.5 [flutter video_player_platform_interface]
- video_player_platform_interface 5.1.4 [flutter plugin_platform_interface]
- video_player_web 2.0.12 [flutter flutter_web_plugins video_player_platform_interface]
- watcher 1.0.1 [async path]
- web_socket_channel 2.2.0 [async crypto stream_channel]
- win32 2.7.0 [ffi]
- xdg_directories 0.2.0+2 [meta path process]
- xml 6.1.0 [collection meta petitparser]
- yaml 3.1.1 [collection source_span string_scanner]

@Technorocker
This is similar to https://github.com/firebase/flutterfire/issues/8091, so I suggest you to follow-up in it for further updates.
Closing this as a duplicate.

ah ok thanks, I'll check it out. I tried to search for something similar before I created an issue but didn't come across anything


ImproveOSM service deprecated

Description
The ImproveOSM project has been phased out. Consequently, the URLs for the publicly accessible ImproveOSM services are no longer active:

Missing Geometry Service: previously available at https://community.improveosm.org/missingGeoService/
Direction of Flow Service: previously available at https://community.improveosm.org/directionOfFlowService/
Turn Restriction Service: previously available at https://community.improveosm.org/directionOfFlowService/

We kindly request the removal of ImproveOSM issues map data from the iD editor.
Thank you.
Screenshots
No response

Note the following information after reaching out to them: In a nutshell, ImproveOSM continues, but only in the SEA region. So, keeping ImproveOSM support in iD might still be useful for mappers in this region, I don't know, so, just FYI:

Hello Tobias,
You can access the Oneway ImproveOSM data dumps at this link. This data, updated nightly, contains data from the SEA area. In addition to one-way data, we also publish information on:

2w/4w accessibility
Street names
Speed limits
Turn restrictions

For other regions (USA, EU, etc.), we have older data available at this link. Please note that this data will no longer be updated as we deprecated the corresponding services and JOSM plugins at the end of June.
Feel free to reach out if you have any further questions.
Best regards, Beata.

Just to clarify, at the end of June, we discontinued the ImproveOSM services mentioned in this ticket. The data associated with these services was outdated, and client components were minimally used.
The ImproveOSM project will continue only in the format of data dumps, available at: https://dumps.improveosm.org/?prefix=AdditionalNewDumps/.

Just to clarify, we discontinued the ImproveOSM services mentioned in this ticket at the end of June. The data associated with these services was outdated, and client components were minimally used.
The ImproveOSM project will continue only in the format of data dumps, available at: https://dumps.improveosm.org/?prefix=AdditionalNewDumps/.

Just need to confirm, the data dumps license is same as KartaView license, that editors can freely refer to the database to edit on OSM right?


Spooling via flyway can't be used for code generation because it is pretty printed

Which version and edition of Flyway are you using?
Enterprise edition 8.5.5
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Maven plugin
Which database are you using? (Type & version)
Oracle XE 18c
Which operating system are you using?
Linux
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
We use the SQL*Plus Spool-command to generate some code that is later meant to be migrated:
Set ServerOutput On Size 1000000
Set Linesize 105
Set Echo Off
Set Heading Off
Set Feedback Off
Set Verify Off

Spool "db-grant-all.sql"

Select 'Grant Select, Insert, Delete, Update On '||
       Object_Name||' To '||'some_user''||';'
From   User_Objects
Where  Object_Type = 'TABLE';

Spool off

Configuration is:
                        <configuration>
                            <driver>oracle.jdbc.OracleDriver</driver>
                            <url>${env.FLYWAY_URL}</url>
                            <user>DBADM</user>
                            <password>${env.FLYWAY_PASSWORD}</password>
                            <locations>
                                <location>filesystem:2_DBADM</location>
                            </locations>
                            <validateMigrationNaming>false</validateMigrationNaming>
                            <connectRetries>5</connectRetries>
                            <oracleSqlplus>true</oracleSqlplus>
                        </configuration>

What did you expect to see?
  Grant Select, Insert, Delete, Update On flyway_schema_history To some_user;

What did you see instead?
+-----------------------------------------------------------------------------+
| Grant Select, Insert, Delete, Update On flyway_schema_history To some_user; |
+-----------------------------------------------------------------------------+

+-----------------------------------------------+
| No rows returned                              |
+-----------------------------------------------+

+------------------------------------------------+
| No rows returned                               |
+------------------------------------------------+

Edit: Added the boxes with No rows returned. I originally attributed those to the SQL script but realize that this is also added by flyway and should not have been part of the output.

From looking at the decompiled code, it seems that the problem is in org.flywaydb.core.internal.database.oracle.OracleSqlScriptExecutor.outputQueryResult(Result result). Here the result is wrapped in an org.flywaydb.core.internal.util.AsciiTable before it's passed on to org.flywaydb.core.internal.database.oracle.log(String output) which writes the actual spooling data.
Unfortunately I see no way to disable the AsciiTable-functionality, so this is a blocker for us.

I just realized that the current implementation also adds feedback info at the end of the spool file, even though we've disabled this using the set feedback off command in our script. I updated the initial description to include this output as well. I initially left that part out since I assumed this was our fault. After looking closer, I believe this is also a bug in Flyway.

The last two rows are a result of SELECT statements returning empty results, as opposed to being feedback rows

I agree with your last assessment. There are a elects returning empty results in our scripts.

Thanks for being honest. I guess we’re back to running SQL*Plus directly.


Allow optional cancellation tokens to be provided for async operations.

@praeclarum Roslyn would like to be able to use your library as our way to persist data we store in the language service and out of process host.
Right now one of the issues that we've seen is that the async work is non-cancellable, leading to large threadpool saturation, even for tasks that we no longer have any need to run.
This PR makes it so that the async operations in this API can take an optional cancellation token as well.
Note: this approach should be source compatible with existing code, but will not be binary compatible.  My feeling was that that was likely ok as users who pulled a new version of your library would be recompiling against it, and would be ok.
If this binary change is not ok, i'm happy to change the PR to use overloads instead.  i.e. instead of:
public Task<int> DropTableAsync<T> (CancellationToken cancellationToken = default(CancellationToken))

We would instead have:
public Task<int> DropTableAsync<T> ()
{
    return DropTableAsync<T>(CancellationToken.None);
}

public Task<int> DropTableAsync<T> (CancellationToken cancellationToken)
{
...
}

This will be non-breaking, at the cost of a lot of overloads.
Please let me know if either of these approaches would work for you.  We'd really like to use your library, but this is a definite issue for us.
Thanks!

@praeclarum Would this be something you're willing to take?  Thanks!

This is great! Can you please rebase to not include the \n changes?

Hi guys, but this change was never merged to master?


WSL: Inliner doesn't allow double-negation

Migrated from https://bugs.webkit.org/show_bug.cgi?id=176440:
At 2017-09-06T05:23:08Z<EMAIL_ADDRESS>wrote:
doPrep() fails with "bool foo(bool x) { return !!x; }"

At 2017-09-06T18:34:47Z<EMAIL_ADDRESS>wrote:
Created attachment 320043
the patch

At 2017-09-27T19:35:16Z<EMAIL_ADDRESS>wrote:
rdar://problem/34693538

At 2017-09-06T20:04:17Z<EMAIL_ADDRESS>wrote:
Landed in https://trac.webkit.org/changeset/221692/webkit

At 2017-09-06T18:53:06Z<EMAIL_ADDRESS>wrote:
Comment on attachment 320043
the patch
View in context: https://bugs.webkit.org/attachment.cgi?id=320043&action=review

Tools/WebGPUShadingLanguageRI/Parse.js:-649

       result.origin = operatorToken.origin;

Thanks

Tools/WebGPUShadingLanguageRI/VisitingSet.js:36

       print("item: " + item + " (" + item.constructor.name + ")");

Print


Mixpanel integration

This adds the integration with Mixpanel. It works exactly the same as the amplitude one.
Tested and working fine. :)

Bro actually, I found that Mixpanel doesn't need integration with this. My company is using Mixpanel, and connecting it as a destination in the segment dashboard is enough. CMIIW

@MarcinusX is this still needed after @ariefwijaya answer?

I mean, according to documentation it is needed so I don't know...

We need to clarify this, it may be needed when users need to use device mode instead of cloud mode. But in my case, we can use cloud mode and how to use cloud mode is to connect our source to mixpanel destination in the segment admin dashboard.
So, the conclusion is it may be needed but it is not required like another provider, for e.g : Moengage.

Wdyt ? @danielgomezrico

Whats the difference between each approach?

Whats the difference between each approach?

We can refer to the official docs from Segment for more
Cloud Mode vs Device Mode

Whats the difference between each approach?

We can refer to the official docs from Segment for more Cloud Mode vs Device Mode

https://segment.com/docs/connections/destinations/#connection-modes


Add support for ZFSoL

What problems are there with this script and ZFSoL?
I am not a linux user, but if you can point out some errors or suggest changes, I'd be happy to accept them

I am going to test this out today on my CentOS 6.5 host, see if any updates
need to be made.  Was putting this in as a placeholder to help certify it.
On Jan 2, 2015 12:41 PM, "Allan Jude"<EMAIL_ADDRESS>wrote:

What problems are there with this script and ZFSoL?
I am not a linux user, but if you can point out some errors or suggest
changes, I'd be happy to accept them
—
Reply to this email directly or view it on GitHub
https://github.com/allanjude/zxfer/issues/10#issuecomment-68545419.

I'm testing zxfer on my two VMs running CentOS 7.2.  I got this error when trying replicate a pool:
[root@zfslive ~]# zxfer -dFkPv -T<EMAIL_ADDRESS>-R tank pool/zfslive
/usr/local/sbin/zxfer: line 693: syntax error near unexpected token fi' /usr/local/sbin/zxfer: line 693:   fi'

I thought I fixed that. What version do you have? Make sure it is 1.1.6

it is the master branch that has this problem.  1.1.6 works fine.

I forgot to push master after creating the tag. Master is correct as of 2 hours ago


Add chore issue template

Is your feature request related to a problem? Please describe.
Addition of Chore template for changes in documentation-workflow-dependency related code changes.
This will increase the clarity of issue type.
Describe the solution you'd like
Adding a separate issue template.
Describe alternatives you've considered
Making further issue template changes as required by code reviewers.

@jingtang10 @deepankarb I would like to implement this feature.

I'm not sure "chore" is the language I would use here. I think there're the following issue types that might be worth adding:

research: there're lots of research tasks we need to create and manage. things to write include background, goal, methodology
code health: refactoring, improving testing infrastructure, documentation can probably fall into this category
process: builds and releases, communications, templates (e.g. this issue itself)

@jingtang10 I have updated the issue templates as instructed.
Please have a look and let me know if further changes are required.


Time of day filter field

Add new acquisition date time of day filter.
Use case: find all rasters acquired between 8am and 4pm for all days in the acquired date range (i.e. only daytime imagery)

This would essentially be implemented by adding a new field on SpatialEntryFilter in django-rgd/rgd/filters.py
Hopefully we can use: https://django-filter.readthedocs.io/en/stable/ref/filters.html#timefilter
    time_of_day = filters.TimeFilter(
        help_text='The minimum/maximum times during the day the records were aqcuired.',
        label='Time of Day',
        method='filter_time_of_day',
    )

then implement the filter_time_of_day method. This would require annotating the times on the queryset then filter on the annotation. Something along the lines of
    def filter_time_of_day(self, queryset, name, value):
        if value is not None:
            queryset = queryset.annotate(
                time_of_day=F('acquisition_date__time')
            )
            if value.start is not None:
                queryset = queryset.filter(time_of_day__gte=value.start)
            if value.stop is not None:
                queryset = queryset.filter(time_of_day__lte=value.stop)

@venkatabhishek, could you help on this?