[Dev] Console Warning: TRenderEngineProvider: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @c3024
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1726072125690969
Action Performed:

Visit the login page on Android App

Expected Result:
No console warning
Actual Result:
Console Warning
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub
Issue OwnerCurrent Issue Owner: @paultsimura

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

Proposal
Please re-state the problem that we are trying to solve in this issue.
Console Warning: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
What is the root cause of that problem?
This problem happens after RN 0.74 when you use the old component's defaultProps:

What changes do you think we should make in order to solve the problem?

I see in the latest code base, the stopped using defaultProps here but it has not been released yet.
In the meantime, we can apply a patch as suggested in this thread to solve the issue, not only in TRenderEngineProvider but also in other components.

@lakchote @paultsimura They found a new maintainer, potentially we can wait for it to be fixed upstream

@lakchote @paultsimura They found a new maintainer, potentially we can wait for it to be fixed upstream

Alright, let's wait for it to be fixed directly from the upstream.

Not overdue

@muttmuure could we demote this to weekly while we're holding for the upstream PR? Or add a HOLD label, please.

@muttmuure is on parental leave. I've demoted this to weekly.

Is this done?

No, we're holding for an upstream fix. However, it had no movement in a month already. Maybe we should go back to considering a patch?

Yes, there are no movements whatsoever. Let's go the patch route. I'm reopening https://github.com/Expensify/App/pull/52917

Update: I started investigating the issue that caused the revert today.

Update:
I spend a lot of time debugging this today, and I concluded that TRenderEngineProvider.tsx patch is the exact part of it that breaks the parts of the app. I found out that this bug is probably happening because along with the .defaultProps and propTypes that were removed from TRenderEngineProvider.tsx in that patch, we also removed the actual default props that were applied to the component.  While I haven’t fully resolved it yet, I’m confident we’re on the right track.


Know Your Community pipelines

@angelarafiles-lacityorg: The 2 scripts to test are on the kyc branch. requirements.txt updates some of the ibis packages to make sure it works with BigQuery. I tested it with my ArcGIS online account to make sure it can overwrite successfully, and it can.
Ref: #4

@alexistome09 updated 311 table in BigQuery
@prestinomills KYC 311 to ESRI script works: src/kyc_311_to_esri.py

To Do:

Update permit data connection in BigQuery
Test src/kyc_permits_to_esri.py


Add InvalidParameters option to Style/OptionHash

This adds the Blacklist option to Style/OptionHash. To override, just specify the array of names.
Style/OptionHash:
Enabled: true
InvalidParameters:
- options
- opts
- args
- params
- parameters

@bbatsov this is ready for review again when you get a chance - thanks!

@wli ping

Do you have a sense of how the transition will be if anyone has opted in on RuboCop 0.33? It might be helpful to notice if the cop is enabled, but the list is not present, and print some warning? If I'm imagining it properly, what will happen to those people is that the cop will not register any offenses because no list is found.
(I mention it because from 0.32 to 0.33, some options were renamed in the Rails Timezone cops, and if you were using the old options and upgraded, RuboCop would fail on those cops, and I kind of wished it had done something more graceful)

@maxjacobson there is a default list and it will use that if the param is not specified. The main/only user-facing change is that certain lines will no longer be errors (if the arguments are not part of the SuspiciousParamsList). No new errors will be introduced by this change.

The code looks good, but the commit message title has to be updated to reflect the new config option name and to refer to the original issue.

@bbatsov I think i fixed all the places (aside from the branch name) to be consistent with the updated naming.


📖 Fix custom analytics doc

According to #901 , update custom analytics providers doc.

Thanks @xwjdsh


E/AudioRecord: start() status -38

E/AudioRecord: start() status -38
i get this error how can i solve this error

@ramesh123456 Could be that your app tries to open microphone while it is already reserved by some other process/object.
Could you please share information how your app uses Speech SDK?

Closing as missing information from customer


[FEATURE] share daily (week day only) jobs on twitter

we used to have legacy twitter api but this no longer works as the API have changed
we need to re-implement the same logic as /x/task/twitter-jobs-scheduler as a new handler and use the new twitter api
twitter docs https://developer.twitter.com/en/docs/twitter-api/tweets/manage-tweets/quick-start
only need to implement share tweet logic
tweets shared once a day (2 jobs per day) and week days only

/bounty $100

@dm161 I can interested to work on this, Can you assign it to me?


Remove redundant wheel dep from pyproject.toml

Remove the redundant wheel dependency, as it is added by the backend automatically.  Listing it explicitly in the documentation was a historical mistake and has been fixed since, see: https://github.com/pypa/setuptools/commit/f7d30a9529378cf69054b5176249e5457aaf640a

Oh, thank you! I am almost certain, that I have the same issue in StringZilla and USearch. Feel free to open PRs 🤗

Oh, thank you! I am almost certain, that I have the same issue in StringZilla and USearch. Feel free to open PRs 🤗

Could you just do it yourself? It feels quite wasteful to fork all these repos to do a trivial fix everywhere.


Added tests for web errors when trying to retrieve image

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
adds a test

What is the current behavior? (You can also link to an open issue here)
no tests for when getting an image results in a 404

What is the new behavior (if this is a feature change)?
a test for when getting an image results in a 4xx or 5xx

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Have unit tests been run against this PR? (Has there also been any additional testing?)
Manual testing - checked against a non existent image

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)

unit tests: https://github.com/marqo-ai/marqo/actions/runs/4463973937

Rerunning unit tests: https://github.com/marqo-ai/marqo/actions/runs/4558166909

unit tests: https://github.com/marqo-ai/marqo/actions/runs/4625139527

unit tests: https://github.com/marqo-ai/marqo/actions/runs/4684662639


Second attempt to fix 28820 with another workaround

Summary of the Pull Request
Checks to see if there is a flyout menu open and tries to hide it before closing the window.

PR Checklist

[X] Closes: #28820
[X] Communication: I've discussed this with other via past forum posts.

Detailed Description of the Pull Request / Additional comments
As the app is closing, after all the "save the windows size" coding is run, the app checks to see if there is a context menu open.  If it is currently showing, and the app closes, the app crashes.  To get around this, the app attempts to close the menu (which sometimes works) and then hides the window, which forces the menu to close.

Validation Steps Performed

Confirmed that the new call to hide the window is only called when there is a context menu showing.
Confirmed that the app actually closes.
Confirmed that the size/position code is not impacted by the call to hide the window.

Thanks for checking.  There's nothing more I can do with this, as the app isn't doing anything wrong and the last two code changes are workarounds, trying to get the context menu closed before the app closes:

First attempt was to add a bit of code to the app closing method, that checks to see if the Context Menu is open and dismiss it before the app closes.  That worked for me, when I was testing it in Debug and Release mode while I had the PR open.  0.7.5 dropped and it started crashing again, this time with a new call stack (I think.)
This attempt is to hide the window when it is told to close, as that would also force the context menu to close; tested this one even more because I didn't want the window to disappear and mess up the save-sizing-on close, but it worked OK in Debug and Release mode, but it still sounds like it's crashing.

Nothing else was done for the context menu, so if that's failing to open for some reason, it's a separate bug, which I believe is also in the WinUI 3 layers.

I'm abandoning this.  While it should add an extra layer of protection against the crash, with little risk to the existing functionality, I don't think anyone wants to take it without it being 100% effective.


Unexpected token 'export' - After upgrading to v4

I will take a look this evening, thanks for the report


WFLY-14249 Ensure java.time/sql.* ProtoStream marshallers generate valid protobuf messages

https://issues.redhat.com/browse/WFLY-14249
Additionally, the native protostream marshallers introduced in this PR result in smaller payload sizes for typical values, see jira for specifics.
Requires https://github.com/wildfly/wildfly/pull/13948

@rhusar Please review.


Improve MaxMinInfo and fix SetMaxSize

See wailsapp/wails#1094

@stffabi - Do you think this has more to go on it now #1094 is confirmed working?

I think we are good to go.

Thanks for merging.


fix: support uninitialized resource transfer

This adds support for uninitialized resource table transfer. In rare edge cases where the target table is not otherwise referenced by any bindgen code and the resource is never dropped, it is possible for the target table in transfer to not otherwise be initialized by the component bindgen.
I don't want to land this without creating a simple test, and fully understanding what mechanisms can lead to this though, because it seems very odd to have an undroppable resource.

On further thought, strictly speaking components under these semantics are valid and execute under Wasmtime, therefore we should ensure the same for Jco.


The getter 'bodyText1' isn't defined for the class 'TextTheme'

Hi,
Context Menu is failing to upgrade to latest version.

Hi,
Context Menu is failing to upgrade to latest version.

Just opened a PR for that, just got to wait for the maintainer to see and merge.

https://github.com/gskinnerTeam/flutter-context-menu/pull/18

(take into account this haven't been updated for at least 2 years)

Hi @esDotDev , could you please update the pub.dev package when you get a chance? Thanks a lot!


more fixes for overview.dd

A second pass through overview.dd

This could really use the attention of a better writer than I am.

Small nitpicks to fix and then LGTM.

@AndrejMitrovic could you please implement yours as a subsequent pass? Let's empty @WalterBright 's plate a bit...


fix: Add QRCode to Settings page

Idea for walkthrough #210

No longer actual. We no longer have these steps in the walkthrough.
CC @wei-lee


When the screen size changes, the current page should be refreshed. In my opinion.

When the screen size changes, the current page should be refreshed. For example, the drawing area of the screen changes with split screen mode enabled or with virtual keys enabled.

To create a widget that's rebuilt when it's size constraints change you can use LayoutBuilder: https://api.flutter.dev/flutter/widgets/LayoutBuilder-class.html
Or you can use MediaQuery (https://api.flutter.dev/flutter/widgets/MediaQuery-class.html) that provide the actual size of the screen containing your Flutter app.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you

I don't agree with.
You don't understand.

Hi @qcks
Can you fill a new issue with a detailed information about the issue/proposal?
This is closed for a few days now and would be better to have a new issue with detailed and precise information about you proposal.


Automated cherry pick of #7643: fix: aovid truncated data

Cherry pick of #7643 on release/3.4.
#7643: fix: aovid truncated data

/lgtm
/approve


UNMET PEER DEPENDENCIES

Hi,
These are the versions for my react native application
"react": "16.0.0-alpha.6",
"react-native": "0.44.0",
"react-native-vector-icons": "^4.0.1"
While installing<EMAIL_ADDRESS>i ran into this issues:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^0.14.0 || ^15.0.0 but none was installed.
Please i need an advice on how i can install native-base to work with my current versions or do i have to downgrade to a lower version of react-native that supports<EMAIL_ADDRESS>

same problem

Same problem:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

Same shoutem issues, but trying to use RN 0.43.0, not 0.44.0.

Fixed with 2.1.4

@SupriyaKalghatgi Has this fix been verified by anyone above or on the GeekyAnts team? ( @emekalites, @yogeshmoradiya121, @iegik or @a-shark)? I'm still seeing this issue.
How I'm installing nativebase: npm install<EMAIL_ADDRESS>-S
A portion of my package.json
  "dependencies": {
    "native-base": "^2.1.4",
    "react": "16.0.0-alpha.6",
    "react-native": "0.44.2"
  },
  "devDependencies": {
    "babel-jest": "20.0.3",
    "babel-preset-react-native": "1.9.2",
    "eslint": "^3.19.0",
    "eslint-plugin-react": "^7.0.1",
    "eslint-plugin-react-native": "^2.3.2",
    "jest": "20.0.4",
    "react-test-renderer": "16.0.0-alpha.6"
  }

├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>│ │ ├─┬<EMAIL_ADDRESS>│ │ │ └──<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └─┬<EMAIL_ADDRESS>│ │   └──<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

@SupriyaKalghatgi this issue hasnt been fixed at all

Hi, apart from the warning, are you facing any problems using the library?

@sankhadeeproy007<EMAIL_ADDRESS><EMAIL_ADDRESS>with<EMAIL_ADDRESS>works well. Using anything higher than the said versions of RN and react is the issue.

Okay, thanks for the info, will be fixed tomorrow in the new patch :)

Check NativeBase 2.1.5

├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └─┬<EMAIL_ADDRESS>│ │   └─┬<EMAIL_ADDRESS>│ │     └──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>

2.1.5 craches my app in several places!
2.1.4
        return color(this.toolbarDefaultBg).darken(0.2).hexString();

->
2.1.5
        return color(this.toolbarDefaultBg).darken(0.2).hex();

changing .hexString() to .hex() everywhere worked for me

https://github.com/GeekyAnts/NativeBase/issues/937

https://github.com/GeekyAnts/NativeBase/pull/939

`
"dependencies": {
"native-base": "^2.1.4",
 "react": "16.0.0-alpha.12",

 "react-native": "0.46.1"

}
`

Acked: with fresh react-native init then native-base install I got outdated dependency
...
warning: "<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>...
package.json:
"native-base": "2.2.1"
"react": "16.0.0-alpha.12"
"react-native": "0.46.1"

same problem

Why does we need to to this? https://github.com/GeekyAnts/NativeBase/issues/806#issuecomment-307763607

@nonameolsson Thats because of the version upgrade of color package. With version 1.x of color, the use case had changed a bit

<EMAIL_ADDRESS>requires print-message
npm install<EMAIL_ADDRESS>--save
npm i<EMAIL_ADDRESS>--save


Inotify: allow to watch paths containing spaces

Before the fix, one would get an error message if the path to be watch contains a space.
This is now handeled properly.

thanks ♥


Upgrade to asm 6.0

Context
Previously we used asm 6.0 ALPHA and BETA. This PR upgrade it to 6.0
Gradle Core Team Checklist

[x] Verify design and implementation
[x] Verify test coverage and CI build status
[x] Verify documentation
[x] Recognize contributor in release notes

@blindpirate We should make sure this makes it into 4.5-RC1. Could you fix the merge conflict and merge asap?

@bmuschko Sure, will do it today.


First buffer open after this commit doesnt show color formatting

Hi 👋
Every time i open the first buffer after the alpha screen it shows without color highlighting and then all other buffers are OK.
Any idea why/where to look?

Getting the same thing here.


Refreshing achievements for Hades on Epic Games giving an error

When trying to refresh Hades for Epic Games Achievements it is showing an error. I was able to successfully refresh data for Alan Wake Remastered and could see those achievements within Playnite
Have attached my extensions.log. The error is at the very bottom of the log
extensions.log

I get the same error for Hades on EGS. "Unterminated string... position 4365."
My only other EGS game with achievements is PC Building Simulator and that works fine.


OS X is now called macOS since Sierra (version 10.12) was released

As the title says, platform.js recognizes "macOS" as "Mac OS X"
reference

Great, I wasnt aware you are working on v2


Consistency between CubeList and list of Cubes

Try to ensure consistency between cubelists and lists of cubes, taking into account sensible variable names (e.g: cubelist and cubes) - only use cubelist when it is actually required to be a CubeList.

@LaurenceBeard do you think it's still important to have this ticket? We don't think it's essential. Can we close it?

If you are happy with the current use of lists of cubes and cubelists, I'm happy to close this, it was ported over from the CLI tidyup work.

This might be easier to address after #1448 is merged. That PR adds type annotations to function and method signatures, removes types from docstrings, and adds mypy static type checking to GitHub Actions (without failing the CI if mypy returns errors: it does).
I was planning on raising an issue to address the mypy errors after that PR is merged. Part of that work could be to clean up CubeList vs List[Cube] types.


Imagine you have untracked changes. These would show up in red with "git status". Now, if you run "git commit", then the presubmit is running against your untracked changes rather than what's about to be committed. This could pose a problem:
$ vim foo.py # Edit foo.py
$ git add foo.py
$ git commit
...oops, the test failed, so the commit didn't happen.
$ vim foo.py # Edit foo.py to fix test
$ git commit  # Oops, didn't re-add foo.py!
...test passes, broken version of foo.py committed
Some possible ways to fix the commit script to blow up when there are untracked changes:
http://stackoverflow.com/questions/3878624/how-do-i-programmatically-determine-if-there-are-uncommited-changes
http://stackoverflow.com/questions/2657935/checking-for-a-dirty-index-or-untracked-files-with-git

Note: I fell prey to this last night (look for a pull request with "Whoops" in the title), so it's worth fixing.

Jeez what a PITA. This is harder than I thought.


Is Proxy is being replaced by Gateway? And what is the limit of total number of gateway in APIM (Premium) ?

A few days Back I have checked the APIM and its on Premium version. But I am not able to add the Proxy but I see there is a new one called Gateway, And I am not able to add more than one Gateway in APIM.

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

ID: d02a5991-da24-06a2-0c24-d012d2e07399
Version Independent ID: 64acd893-43bb-81af-d14d-0b7553e93daf
Content: Configure a custom domain name for your Azure API Management instance
Content Source: articles/api-management/configure-custom-domain.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

Hi @GauravLad12 - Thank you for your feedback! We will review and update as appropriate.

@GauravLad12 gateway what you are looking for. Premium supports multiple custom domain names for the gateway. If the problem persists, please open a support case. #please-close


No error message for SBOL Term missing underscore

Describe the bug
When there is no "underscore" in the SBOL term, an exception should be thrown with an error message
To Reproduce
Steps to reproduce the behavior:

Go to 'SBOL Term'
Enter an SBOL Term with no underscore
Run converter.py on sheet with SBOL Terms with missing underscore
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Traceback (most recent call last):
File "C:\Users\saisa\Excel-to-SBOL\excel2sbol\excel2sbol\converter.py", line 7, in
e2s(file_path_in, file_path_out, sbol_version=2)
File "C:\Users\saisa\Excel-to-SBOL\venv\lib\site-packages\excel2sbol\converter.py", line 23, in converter
e2s.column_parse(to_convert, compiled_sheets, sht_convert_dict,
File "C:\Users\saisa\Excel-to-SBOL\venv\lib\site-packages\excel2sbol\compiler_test.py", line 294, in column_parse
col_meth.switch(col_convert_df['SBOL Term'].values[0])
File "C:\Users\saisa\Excel-to-SBOL\venv\lib\site-packages\excel2sbol\comp_column_functions.py", line 63, in switch
self.sbol_term_suf = sbol_term.split("_", 1)[1]
IndexError: list index out of range

@JMante1 for visibility


REFACTOR - Rename project

This project can do more than make a clone of vf-eleventy, so we should consider renaming it... perhaps: create-vf-boilerplate

Or create-vf-project


Ideas for Push API recipes

[ ] Registration (Google Cloud Console, manifest file, need to register from document first, sending data to their server)
[ ] Sending a simple message (Perhaps a very simple back-end example for sending something to GCM, similar to what Matt is using)
[ ] Receiving a message (The "onpush" event, why no payload, using fetch())
[ ] Displaying a notification (Why? Good practices for engaging users (icon + title + body), store data in IDB, maybe "tag" hack?)
[ ] Handling a notificationclick even (focusing or opening windows)

These are following a sync with Peter a week or so ago. We've since opted to ship a single larger sample in #79, but these could still be useful to explore when time allows.

I'm lost as to what you are looking for in this?
John Mellor has literally ripped apart so much code for this that the demo is going to get updated to cover some of this.
1.) Registration - we do this don't we apart from sending data to the server - and for that I imagine the developer will need a user id before it becomes useful.
2.) Sending simple push message - are you asking for samples for the major server languages or something else? Why is this not a GCM sample request?
3.) We receive a message and the H5R article will have an example of a fetch request in the onpush event
4.) Displaying a notification - I've avoided showing how to do this in the article because Jeff wasn't comfortable with using an IDB library that wasn't official
5.) John has basically added this code - it complicates things and I'm not sure how useful it is - I largely hate it as it makes a tone of assumptions - but hey - it is useful for this one use case.

For registration - I have push API working fantastically in FireFox but it does not work in Chrome on Android (I use CentOS 7, I don't have access to Chrome on Desktop, Google Chrome has chosen not to support CentOS 7)
I read that what I was missing was a manifest.json file - even though the W3C API never mentions one - so I created one according to the specifications at MDN. Still won't work in Chrome for Android.
I looked at the manifest.json used in samples/push-messaging-and-notification/ and saw that it contains a Google provided API key.
Is that really required, and if so, why? That greatly reduces the anonymity of push messages.
I'm here because I'm trying to find out why my push API works in FireFox and not Chrome and I really hope that isn't the reason.
As more and more browsers implement Push API, the last thing I was is half a dozen different API keys that have to be in the JS or manifest or wherever, that seems counter to the whole purpose of a web standard.

Okay for anyone else reading this, I added an API key to my manifest.json and it instantly started working. Well, I haven't tried sending to that subscription yet but I'm sure the rest is downhill.
I'm not happy that an API key is needed to implement a W3C standard in Chrome for Android, Google seriously might want to reconsider that if they aren't already.

Routing this to @beverloo as they are editing the Push API; perhaps the current sample covers these use cases already?


Progressive append

Fixes #132.
Compress small trees when appending to an existing revision
Appending a small volume of data to an existing qbeast table is likely to create many small files, as shown in #132. To tackle the issue we can recursively group and send sibling payloads to their parent cubes as long as the resulting size is under a certain threshold, resulting in fewer and larger blocks to write.
The process is called COMPRESSION and is done after the cubeColumnName is created and before repartitioning data by cubes.
The process is only triggered when appending data to an existing revision, for it is of our interest for the initial tree to have a natural depth. On top of that, the appended data has to be small (<= MAX_SIZE_FOR_APPEND_COMPRESSION) otherwise blocks are already large. Compressing a large tree is expensive.
MAX_SIZE_FOR_APPEND_COMPRESSION is configurable through spark.qbeast.index.maxAppendCompressionSize, default value is set to 0.
Influence on cube maxWeights
Cube maxWeights from the parallel implementation increase monotonically from top to bottom on any branch. We need to make sure the proposed compression won't alter this behavior - when moving cube elements to their ancestors, both parent and child maxWeights are left intact, in fact, the append won't even affect the maxWeight of the child cube since no elements are written, and the ancestor cube will have maxWeight reduced by the update.
Influence on online sampling and querying
The compression doesn't modify the maxWeights assigned during estimation. Branch maxWeights are left monotonically increasing so it won't affect the correctness of our sampling. The efficiency, however, may drop for blocks now have more elements than that reflected by their maxWeight; the excess elements are later filtered in memory.

[x] Add/update documentation
[x] New feature / bug fix has been committed following the Contribution guide.
[x] Add comments to the code (make it easier for the community!).
[x] Add tests.
[x] Your branch is updated to the main branch (dependent changes have been merged).

Tests:

Make sure the compressed tree has fewer cubes than the original
Make sure adding a compressed tree doesn't change the fact that maxWeights increase monotonically in any branch
Make sure that inline sampling is not corrupted by adding a compressed tree

Test Configuration:

Spark Version: 3.2.2
Hadoop Version: 3.3.1
Cluster or local? Local

TODO:

[x] Compute cube sizes from delta and existing cube weights in order to avoid collect
[x] Perform compression through roll-up and use the resulting map during indexing
[x] Consider cube state during compression
[ ] Update tests

Closing this PR for now. We can still use Compaction to solve the problem of Small Files or add a Roll-up command as stated in #147 . 😃


[request] External Data Visualization

Hi,
I think it would be very useful to have access to the visualization data outside of Rviz. In my case I will be using OpenPTrack's data in TouchDesigner and would love to include the 3D visualization in this environment.
Keep on the good work !

Dage

Hi Dage,
Thank you so much
What type of visualization data were you interested in accessing?
Simeon

Information on using the tracking data (including in TouchDesigner) can be found here.


grunt babel configuration does not work

Test environment

OS : windows 7
"grunt": "^0.4.5",
-
"grunt-babel": "^5.0.3",

 Test

My configuration were like the below, which is the same in README.md

module.exports = function (paths) {
    'use strict';
    var src_jsx = paths.src_jsx;
    var dest = paths.dest;
return {
    babel: {
        options: {
            sourceMap: true
        },
        dist: {
            files: {
                'dist/app.js': 'src/app.js'
            }
        }
}

so, I  debugged.(But, I'm kind of newbie of nodejs)
I figured out that the babel.js has a bug

c:\<project>\node_modules\grunt-babel\tasks\babel.js

My Fix

I fixed it like the below, and also fix the configuration for babel

this.files.forEach --> this.data.files.forEach
files configuration

module.exports = function (grunt) {
grunt.registerMultiTask('babel', 'Transpile ES6 to ES5', function () {
	var options = this.options();

           // this.files --> this.data.files
	this.data.files.forEach(function (el) {
		delete options.filename;
		delete options.filenameRelative;

		options.sourceFileName = path.relative(path.dirname(el.dest), el.src[0]);
		if (process.platform === 'win32') {
			options.sourceFileName = options.sourceFileName.replace(/\\/g, '/');
		}
		options.sourceMapTarget = path.basename(el.dest);

		var res = babel.transformFileSync(el.src[0], options);

		var sourceMappingURL = '';
		if (res.map) {
			sourceMappingURL = '\n//# sourceMappingURL=' + path.basename(el.dest) + '.map';
		}

		grunt.file.write(el.dest, res.code + sourceMappingURL + '\n');

		if (res.map) {
			grunt.file.write(el.dest + '.map', JSON.stringify(res.map));
		}
	});
});

};

module.exports = function (paths) {
    'use strict';
    var src_jsx = paths.src_jsx;
    var dest = paths.dest;
return {
    babel: {

        options: {
            sourceMap: true,
        },

        files : [{
            src: ["src/spikeview.js"],
            dest: 'src/ddd.js',

        }],
    }
}

}

Now it works.

I have seen many blogs who set the configuration of babel differently and works. So, I can't sure whether this is the really issue or not.

Anyhow, I hope this issue will be fixed for Windows which is my main OS :)

gulp-babel is working as intended. You're probably just using it incorrectly. I would suggest reading the grunt docs. Support questions are better asked on Stack Overflow.

Sorry, this is my mistake.
I configured my babel config again, then it works ok.
sorry for bothering you.
take care

@i5on9i how did you do that?


Adopt sslib keygen interface encryption changes

Blocks on https://github.com/secure-systems-lab/securesystemslib/pull/288 + release
Fixes # -
Description of the changes being introduced by the pull request:
secure-systems-lab/securesystemslib#288 changes the key generation interface functions to no longer auto-prompt for an encryption password if no password is passed, in order to not suprise the caller with a blocking prompt.
The downside of this change is that the keys are stored in plain text per default, which may be mitigated by recommending encryption in the docs.
This PR updates related TUF documentation.
NOTE: The securesystemslib private key import functions do not auto-prompt for decryption passwords either, however TUF only exposes custom wrappers (see repository_lib) that do auto-prompt.
Please verify and check that the pull request fulfills the following
requirements:

[ ] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Would it be better to have an option to decide how to do this?  If you want the caller to not encrypt the file on disk, we should make them pass in some scary flag, I think.

Would it be better to have an option to decide how to do this? If you want the caller to not encrypt the file on disk, we should make them pass in some scary flag, I think.

I agree. Storing keys unencrypted by default is a sort of a backwards-incompatible change, and not a great one.

@JustinCappos, @trishankatdatadog, I agree with you but there also seems to be a consensus that a default prompt in an interface function is a bad idea (see https://github.com/secure-systems-lab/securesystemslib/pull/288#discussion_r511420534 for the related discussion).

@JustinCappos, @trishankatdatadog, I agree with you but there also seems to be a consensus that a default prompt in an interface function is a bad idea (see secure-systems-lab/securesystemslib#288 (comment) for the related discussion).

Makes sense. If that is the case, then perhaps we need to make a backwards-incompatible change, and split the function into two: one for generating unencrypted keys, and one for encrypted keys (no prompt, because the passphrase must be explicitly specified by the caller). This should follow the principle of least surprise to users. What do you think?

@JustinCappos, @trishankatdatadog, I agree with you but there also seems to be a consensus that a default prompt in an interface function is a bad idea (see secure-systems-lab/securesystemslib#288 (comment) for the related discussion).

Makes sense. If that is the case, then perhaps we need to make a backwards-incompatible change, and split the function into two: one for generating unencrypted keys, and one for encrypted keys (no prompt, because the passphrase must be explicitly specified by the caller). This should follow the principle of least surprise to users. What do you think?

I think Trishank's suggestion is a good way to do what I was trying to suggest.

@trishankatdatadog and @JustinCappos, I posted a recap of the discussion at https://github.com/secure-systems-lab/securesystemslib/pull/288#issuecomment-718831595. Let's discuss there what makes sense most.

The issue of non-default encryption has been resolved in #288 and adopted here. May I kindly ask for a re-review?

Note that tests fail, because the changes in sslib have not yet been released. The with-sslib-master should pass though...

Closes #1204


Msc studyright / populations megaticket

Cases found this far (studentnumbers in issues)

[x] #2745 (oodi-oodikone fakap)
[x] #2748
[ ] #2749
[x] #2750
[ ] #2771 (oodi-oodikone fakap)
[ ] #2772 (oodi-oodikone fakap)
[x] #2773
[ ] #2781

probably better to handle this without megaticket as index, closing this


Jetton to TON swap not working

I want to make a Jetton to TON swap, but the example (dex-swap-with-ton.ts) is only the TON to Jetton swap. I see a comment saying "reverse transaction is just a regular swap transaction where askJettonAddress is a ProxyTon address".
so, I run the code like this, but got the "709" exit code.
  const JETTON0 = 'EQA2kCVNwVsil2EM2mB0SkXytxCqQjS4mttjDpnXmwG9T6bO'; // STON
  const PROXY_TON = 'EQCM3B12QK1e4yZSf8GtBRT0aLMNyEsBc_DhVfRRtOEffLez'; // ProxyTON

  const router = new Router(provider, {
    revision: ROUTER_REVISION.V1,
    address: ROUTER_REVISION_ADDRESS.V1,
  });

  // transaction to swap 1.0 JETTON0 to PROXY_TON but not less than 1 nano PROXY_TON
  const swapTxParams = await router.buildSwapJettonTxParams({
    // address of the wallet that holds offerJetton you want to swap
    userWalletAddress: WALLET_ADDRESS,
    // address of the jetton you want to swap
    offerJettonAddress: JETTON0,
    // amount of the jetton you want to swap
    offerAmount: new TonWeb.utils.BN('400000000'),
    // address of the jetton you want to receive
    askJettonAddress: PROXY_TON,
    // minimal amount of the jetton you want to receive as a result of the swap.
    // If the amount of the jetton you want to receive is less than minAskAmount
    // the transaction will bounce
    minAskAmount: new TonWeb.utils.BN(1),
    // query id to identify your transaction in the blockchain (optional)
    queryId: 12345,
    // address of the wallet to receive the referral fee (optional)
    referralAddress: undefined,
  });

  console.log({
    to: swapTxParams.to,
    amount: swapTxParams.gasAmount,
    payload: swapTxParams.payload,
  });

  const seqno = await wallet.methods.seqno().call();
  if(seqno !== undefined) {
    const transfer = await wallet.methods.transfer({
      secretKey: keys.secretKey,
      toAddress: swapTxParams.to,
      amount: swapTxParams.gasAmount,
      seqno: seqno,
      payload: swapTxParams.payload,
      sendMode: 3,
  });

    const transferSended = await transfer.send();  // send transfer query to blockchain
  }

Could you tell me the correct usage, thanks.

In the last SDK release the default gas constants was updated, so you no longer need to use override. JFYI


Better documentation

The documentation is pretty well out of date. Update it to include recent changes.

Moving to stevenjack/cfndsl#257


Weird font issue

One day, I hopped on Visual Studio Code and this happened:

I haven't touched any settings that have to do with the font family.
Side note: I reinstalled and same issue.
Side note 2: I reinstalled and removed ~/Library/Application Support/Code and it fixed the font issue.

VSCode Version: 1.16.1
OS Version: macOS 10.12.6

Steps to Reproduce:
I don't know how this occured.

Reproduces without extensions: Yes

What happens if you set the font family in your user settings to the default one:
"editor.fontFamily": "Consolas, 'Courier New', monospace"
Then it should be without serifs.

@PKief I have already reinstalled Visual Studio Code which seemed to fix the issue. Thanks though.

@PassTheMayo By deleting ~/Library/Application Support/Code you have removed your user settings.json where you probably had configured a certain font family. Perhaps there was a typo in the editor.fontFamily you had configured. Please let me know if you remember what settings you had in there that led to this font situation...


Make push/pop methods return Views

Returning the provided layout id is probably useless, especially for push.
If we return a View from the push methods, we can use that reference to initialize the next View with any data -- for example, a master-detail flow where the master View provides the detail View with data.
I can't think of a good use case for pop, but it's probably best to keep it consistent with push.

https://github.com/mattlogan/Pancakes/commit/075b78c25a1238109a757798e5a135bf25cfe176


The library keeps to add default scopes when I'm requesting for a one

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.22.1
Wrapper Library
Not Applicable
Wrapper Library Version
None
Description
For a logged in user to my application, I'd like to ask him later for some additional permission (User.ReadBasic.All) to be able to perform some operations. My code looks like:
const loginRedirectParams = {
   scopes: ['User.ReadBasic.All']
};
this.authContext.loginRedirect(loginRedirectParams);

It works as expected and redirect user to a login page when he needs to accepts new permissions list. The problem is, except the permission I requested, there are three more scopes:
&scope=User.ReadBasic.All%20openid%20profile%20offline_access
Why is that? How can I force the MSAL library to stop adding some extra scopes?
MSAL Configuration
{
   auth:
   authority: "https://login.microsoftonline.com/xxx"
   clientId: "xxx"
   navigateToLoginRequestUrl: true
   postLogoutRedirectUri: "xxx"
   redirectUri: "xxx"
   cache: {
      cacheLocation: "localStorage"
      storeAuthStateInCookie: false
   }
}

Relevant Code Snippets
No response
Identity Provider
Azure AD / MSA
Source
External (Customer)

@samuelkubai Thanks for the answer. I'd like to ask for a single scope for an extra call in API (it receives basics scopes after first user login), which needs User.ReadBasic.All in order to get all users from a tenant. It doesn't need additional scopes and I'd like to not ask user for them in a login prompt. I can do that by generating URL by myself in a frontend code (and it works), but for obvious reason it'd be better to use the MSAL library for this action.

@samuelkubai Thanks


question about backend

Thank you very much for your contribution!
I download your code from github, and test on my computer.
When I run "python yolo3_one_file_to_detect_them_all.py -w yolo3.weights -i dog.jpg",the problem occured:
Traceback (most recent call last):
File "train.py", line 101, in
main(args)
File "train.py", line 70, in main
anchors             = config['model']['anchors'])
x = LeakyReLU(alpha=0.1)(x)
File "/usr/local/lib/python2.7/dist-packages/keras/engine/base_layer.py", line 454, in call
output = self.call(inputs, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/keras/layers/advanced_activations.py", line 46, in call
return K.relu(inputs, alpha=self.alpha)
File "/usr/local/lib/python2.7/dist-packages/keras/backend/tensorflow_backend.py", line 2933, in relu
x = tf.nn.leaky_relu(x, alpha)
AttributeError: 'module' object has no attribute 'leaky_relu'
I don't know why. I also run yolo2 on my computer, and I can train on my own dataset, but after this error occured, yolo2 can't run,too. And has the same problem. Do you have any idea?

I change keras from 2.1.6 to 2.1.2 and solve the problem.

change you TF edition to 1.4.0   CUDA8    cuDNN6

Change your TF edition to 1.4.0 (CUDA8 cuDNN6).TF 1.2.0 has no attribute 'leaky_relu'.


Documentation points to old website structure

Some of the links in api.dartlang.org follow the structure of the website (www.dartlang.org) from before the latest revamp.
In particular, in "If you've never written a web app before, try our tutorials—A Game of Darts." the link for "A Game of Darts" is https://www.dartlang.org/docs/tutorials which has actually moved to https://www.dartlang.org/tutorials.
Also, the link for "Dart Editor" on the same page seems to point to https://www.dartlang.org/#get-started, while the "Get Started" button on the home page points to https://www.dartlang.org/guides/get-started.
Others might be out of date too.

@smanilov do you have a link to the page that has these old links? All the links on https://api.dartlang.org/stable/1.19.1/index.html seem to work for me...

Duplicate of https://github.com/dart-lang/sdk/issues/32304


Show actual parse error in debug message when failing to parse content

Thanks dude!

I just cut a patch release for this.


Resprestsnippets

The first commit contains the actual modified code.
The second commit only contains the baseline file changes.

A few nits, but generally looks good. Would strongly suggest making the change to transform the using directives before adding in the blank line, but everything else is optional.

Thanks, I've made the suggested changes, and will merge if travis passes


HttpContext.GetRequestedApiVersion is null on Asp.Net Core 2.2

I have the following Asp.Net core 2.2 controller:
[ApiVersion("1.0", Deprecated = false), Route("v{apiVersion}")]
public class FileController : Controller {

    protected ApiVersion RequestedApiVersion => HttpContext.GetRequestedApiVersion();

   [HttpGet("files/{fileId}")]
   public IActionResult GetContentByFileId2(Int32 fileId) {

    }

}

And on Startup I have:
  services.AddApiVersioning(x => {
    x.ApiVersionSelector = new CurrentImplementationApiVersionSelector(x);
    x.AssumeDefaultVersionWhenUnspecified = true;
    x.DefaultApiVersion = new ApiVersion(1, 0);
    x.ReportApiVersions = true;
  });

When I access the path "v1.0/files/1" the RequestedApiVersion is null.
Any idea why?

@commonsensesoftware
I have a similar issue where inside OnActionExecuted(ActionExecutedContext context), context.HttpContext.GetRequestedApiVersion() seems to be null.
Do you know what is missing? Thank you.

@cvjlooc I'm afraid I need some more context (setup, config, etc). GetRequestedApiVersion() will return null if no API version was requested or the value is invalid. It would be unexpected in user code, but it is also possible to simply, explicitly set it to null as well (which I don't think you did).
If OnActionExecuted is called, that would suggest that the action was matched and called. The only scenario I can think of where this would happen is if the action is version-neutral and no API version was specified. Even if you allowed a version to be assumed for backward compatibility, it would be explicitly set to that version by this point in the pipeline.
If you can share some additional details or a repro, I can provide more context. GetRequestedApiVersion() is just a shortcut for HttpContext.Features.Get<IApiVersioningFeature>().RequestedApiVersion. There is also RawRequestedApiVersion (e.g. string) that will indicate if anything was picked up. That might be useful.
Which library version is this? Is this still ASP.NET Core 2.2? I might need to jump start the Delorean to remember what I was doing 😆.

@commonsensesoftware
Oh I'm sorry I didn't say that I'm using .NET 5!
I'm assuming that OnActionExecuted is being called and that GetRequestedApiVersion() is returning null since I'm not seeing the intended effects of the code inside OnActionExecuted. I still didn't figure how to add a logger inside OnActionExcecuted.
The custom ActionFilterAttribute is applied to a number of Controller classes.
This is what I have in Startup.cs:
services.AddApiVersioning(                 options => options.ApiVersionReader = new QueryStringApiVersionReader("api-version"));
What kind of other details are you looking for?
I read your code here  about RawRequestedApiVersion but my gut feeling is that it might not work too :(

Using a logger depends on how your attribute is instantiated. If you're applying as a normal attribute, you can resolve it from the action context. Something like context.HttpContext.RequestServices.GetRequiredService<ILogger<MyAttribute>>().
Based on this configuration, I would expect a request such as values?api-version=1.0. That should parse just fine. It sounds like you're not 100% sure if GetRequestedApiVersion() is returning null or not. You should be able to test by setting a breakpoint in OnActionExecuted or within the controller by calling GetRequestedApiVersion(). ApiVersion also has a model binder so you can add a parameter for it in your controller action as well.

I did set a breakpoint in onActionExecuted in the past but context.HttpContext.GetRequestedApiVersion() returned null but that could be because when I ran things, our tests don't build the full context. In any case, I added HttpContext.GetRequestedApiVersion() to a controller and ran a local integration test and it still returned null probably because of the same reason as the above.

Do you have something else in your setup you can share or a repro? There's something more going on here that I'm not seeing.

@commonsensesoftware  I'm facing a similar issue (HttpContext.GetRequestedApiVersion() returns null) but in testing.
Here's my question with more details on SO.
Do you know why GetRequestedApiVersion() returns null? Thank you

@watchloop There is several possibilities. The most obvious would be that the provided API version string is invalid. If that value fails to parse, then the result will yield null. It will not otherwise fail or throw an exception - by design. This is almost certainly the cause as I would missing things, such as not calling AddApiVersioning(), would result in a runtime exception from some something not being configured. In most cases, there should be a graceful fallback path that should always work when setting things up to version by query string parameter since it's the default.


Reduce pod repo update invocations on iOS updater

@samtstern can you merge this PR? I don't have write access.


fix advanced example in README

I'm also not sure if it's me making a mistake somewhere,
but the following line of code doesn't seem to work for me:
const findIndex = (c, d) => c - destringifyOffset.first().value;

Seems the first function is returning pretty much the same as what destringifyOffset
already gives me at that point. The following does work for me:
const findIndex = (c, d) => c - destringifyOffset.nodes[0].value;

Didn't modify that in the README example in this PR yet, as I do not know if it's a bug, desired or something I'm simply doing wrong.

Hello everyone,
it is always discouraging when examples of something that is new to you doesn't work as expected.
I fixed advanced example to work for me like follows
``
const { refactor } = require('shift-refactor');
const Shift = require('shift-ast');
const { commonMethods } = require('refactor-plugin-common');
// Obfuscated source
const src = var a=['\x74\x61\x72\x67\x65\x74','\x73\x65\x74\x54\x61\x72\x67\x65\x74','\x77\x6f\x72\x6c\x64','\x67\x72\x65\x65\x74','\x72\x65\x61\x64\x65\x72'];var b=function(c,d){c=c-0x0;var e=a[c];return e;};(function(){class c{constructor(d){this[b('0x0')]=d;}['\x67\x72\x65\x65\x74'](){console['\x6c\x6f\x67']('\x48\x65\x6c\x6c\x6f\x20'+this[b('0x0')]);}[b('0x1')](e){this['\x74\x61\x72\x67\x65\x74']=e;}}const f=new c(b('0x2'));f[b('0x3')]();f[b('0x1')](b('0x4'));f[b('0x3')]();}());;
const $script = refactor(src, commonMethods);
const strings = $script(Script > :first-child ArrayExpression > .elements);
const destringifyDeclarator = $script(VariableDeclarator[binding.name="b"][init.params.items.length=2]);
destringifyDeclarator.rename('destringify');
const destringifyOffset = destringifyDeclarator.$(BinaryExpression > LiteralNumericExpression);
const findIndex = (c, d) => c - destringifyOffset.nodes[0].value;
$script(CallExpression[callee.name="destringify"]).replace(
node => {
return new Shift.LiteralStringExpression({
value: strings.get(findIndex(node.arguments[0].value)).value
})
}
)
$script([binding.name="a"]).delete();
$script([binding.name="destringify"]).delete();
$script.convertComputedToStatic();
console.log($script.print());
``
there were 2 issues:

with .first() which i think is a bug
convertComputedToStatic() method were moved to separate library

Thanks!


UI: The "Up to date" button is misleading

By clicking the "Up to date" button for an infrastructure stack, it's possible to change the behavior of the existing stack, for example changing Kubernetes settings. I would argue that this button has a misleading name, and the "up to date/upgrade available" should be moved to a separate ui element (label) so that the button itself could be renamed to something more fitting, like "change stack configuration" or whatever. It feels very counter-intuitive that clicking a button that says "up to date" actually allows me to change aspects of my environment.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


fixing typos in mjcf readme

I get the following errors while following the documentation.
ValueError: Expect keyword to be one of ['radian', 'degree'] but got: radians
This PR updates the readme file.

Submitted as f11982b. I'm not sure why this PR wasn't automatically updated.
Thanks!


Check that all used definitions are actually defined in the Haskell code

@flupe mentioned to me that it would be a good idea to check that all defined symbols that are used in the generated Haskell code are also actually defined in the Haskell code. This would require some kind of "foreign" pragma for annotating a function that is already defined in the Haskell code.

Alternatively we could use the following criterion for which functions are allowed to appear in compiled Haskell code:

has a COMPILE AGDA2HS pragma,
OR is a builtin function of agda2hs,
OR is defined in a module starting with Haskell.Prim

If we have the full set of allowed functions, we could also make a call to dontReduceDefs allowedFunctions (normalise v) to try to make the disallowed functions disappear. If that doesn't work, we should throw an error.


Gen 2 VM on Azure already supports ASR

Hi Expert,
In the documentation, Gen2 VM on Azure support for ASR is not supported, but it seems that it is already supported as long as you review the following Knowledge Base.

Update Rollup 42 for Azure Site Recovery
https://support.microsoft.com/en-us/help/4531426

In addition, I actually set ASR for Gen 2 VM on Azure, but confirmed that replication and test failover were successfully performed.
So please correct the documentation if possible.
Best regards,

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

ID: 9145de07-94e5-05bc-d00b-e05723db9163
Version Independent ID: c5d9a3c6-6fc2-837a-8291-2f4b82550d85
Content: Azure support for generation 2 VMs
Content Source: articles/virtual-machines/windows/generation-2.md
Service: virtual-machines-windows
GitHub Login: @laurenhughes
Microsoft Alias: lahugh

@kogesaka
Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@laurenhughes please take care of this issue

@kogesaka Thanks for the feedback! The documentation has been updated to reflect that ASR is supported on Gen2 VMs.
#please-close


Typing error

Issue SUPPORTER is written instad SUPPORTERS
File path /www_mapod4d_it/index.html
Row 195

The issue has been corrected in local repo. Closed #33


Dockerfile: wrong output location for server binary?

Component
server
Describe the bug
When building locally on macOS via
make build
make release-server

the output location of the binaries go to dist/server/${TARGETOS}_${TARGETARCH}/woodpecker-server.
However, docker/Dockerfile.server.alpine.multiarch expects the binary at
https://github.com/woodpecker-ci/woodpecker/blob/435f5ae207dac02c90dd5f02dbc18aecc9972132/docker/Dockerfile.server.alpine.multiarch#L12
Is this a bug or a local deviation on macOS? I had to adjust the Dockerfile manually to be able to build the images.
System Info
macOS 13.3.1

Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

Can't say as make build currently fails for me with
/opt/homebrew/Cellar/go/1.21.3/libexec/pkg/tool/darwin_arm64/link: running cc failed: exit status 1
ld: library not found for -lcrt0.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)

👀


Memory Pool exceed

LocalAI version:
Latest
Environment, CPU architecture, OS, and Version:
Darwin macbook-2.local 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:41 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T8103 arm64 (M1 Macbook Air)
Describe the bug
Trying to use Llama_Index to construct a vector index of a document (pdf in my case), to use it as a query engine. I'm getting the error from LocalAI: ggml_bert_new_tensor_impl: not enough space in the context's memory pool (needed 271388624, available 260703040)
To Reproduce

Enable embeddings
Query (a lot) with a lot of text from pdf
Profit

Expected behavior

Logs
Too long to be in the issue, here is a link to the txt: https://hastebin.com/share/ukuvaranaw.rust
Additional context
I have 16gb of RAM. Is there a way to not get this error, while not having to wait 30min to finish the embeddings ?
This is my Python code:
import os
from pathlib import Path

from langchain.chat_models import ChatOpenAI
from llama_index import (Document, GPTVectorStoreIndex, LLMPredictor,
                         PromptHelper, ServiceContext, SimpleDirectoryReader,
                         StorageContext, download_loader,
                         load_index_from_storage)
from llama_index.langchain_helpers.agents import (IndexToolConfig,
                                                  LlamaIndexTool)

os.environ['OPENAI_API_KEY'] = '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'

# Downloading the model
PDFReader = download_loader("PDFReader")

# Configure prompt parameters and initialise helper
max_input_size = 400
num_output = 400
max_chunk_overlap = 30

prompt_helper = PromptHelper(max_input_size, num_output, max_chunk_overlap)

llm_predictor = LLMPredictor(llm=ChatOpenAI(temperature=0, model_name="gpt-3.5-turbo", openai_api_base="http://localhost:8080/v1"))

loader = PDFReader()

# Loading from a directory
documents = loader.load_data(file=Path('./data/convention.pdf'))

service_context = ServiceContext.from_defaults(llm_predictor=llm_predictor, prompt_helper=prompt_helper)

# Construct a simple vector index
index = GPTVectorStoreIndex.from_documents(documents, service_context=service_context)

# rebuild storage context
#storage_context = StorageContext.from_defaults(persist_dir='./storage')
#index = load_index_from_storage(storage_context,    service_context=service_context)

# Save the index to disk
index.storage_context.persist()

query_engine = index.as_query_engine()

response = query_engine.query('Est-ce que je suis imposable sur les revenus de ma société qui réside à Dubai en étant résident fiscal français et ayant que des clients français?')

@obito Did you just post your openai key here?

@obito Did you just post your openai key here?

It has been deleted for a very long time.


intial refactor using reportError method from window

What does this change?
This is an initial draft PR to demonstrate refactoring of reportError function, gettign it from the window instead of Raven lib.
Why?
The refactoring of uaing the Sentry reportError method which is on the window accepts 2 arguments (as in DCR) and at times commercial reporting passes 3-4 arguments.

I think this could be easier to review if you exported the window reportError from the old module report-error.ts, then not so many files would need to be updated (and reviewed)!
  export const reportError = window.guardian.modules.sentry.reportError;

I think this could be easier to review if you exported the window reportError from the old module report-error.ts, then not so many files would need to be updated (and reviewed)!
  export const reportError = window.guardian.modules.sentry.reportError;

Sure thing 👍

Still need to add the tags back to the error reports? Now that you've added support for them to the DCR reportError function

Still need to add the tags back to the error reports? Now that you've added support for them to the DCR reportError function

done 👍

Thanks for your work on this @dskamiotis ✨


Execute server attack tests

Tasks
さくらVPSのWAFは使える？
最も"攻撃力"が高い負荷試験ツールは...?

[ ] Execute server attack tests
[ ] Install WAF ModSecurity

https://k-jun.hateblo.jp/entry/2022/03/13/174528
Writing the Issue

[ ] Write each task for this issue using checkboxes
[ ] Write all verbal instructions as tasks
[ ] Add labels and assignees

Before Working on the Issue

[ ] Assign yourself
[ ] Share your screen on Discord
[ ] Write which issue you are starting on Slack
[ ] Git: Fetch the latest main
[ ] Git: Create a branch with the name of the issue

Pre-PR Checks

[ ] Insure that changes include only what is necessary for this PR
[ ] Implement necessary Unit tests
[ ] Implement necessary E2E tests
[ ] Perform functionality checks

brew install wrk


(PUP-5571) Document the /puppet/v3/environment/:environment endpoint

Once the typo is fixed, this looks fine to me.

Made all the suggested changes - please merge

The travis failure can be ignored. (We were briefly pointing travis at ruby-head in the run-up to the 2.3.0 release. But ruby-head is now pointing at 2.4.0-dev ruby, which we aren't yet tracking, so that fail is expected.)
Merging.


Allow --keystore flag in account import process

Which component is your feature related to?
Cast
Feature Request
While importing account we should be able to pass --keystore flag in order to to create a corresponding keystore file.
Ref: https://foundry-rs.github.io/starknet-foundry/starknet/account.html?highlight=keystore#creating-an-account-with-starkli-style-keystore

Blocked by https://github.com/foundry-rs/starknet-foundry/issues/2221


Change PreferredTokenSigningKeyThumbprint to nullable

When working on implementing a resource to set the PreferredTokenSigningKeyThumbprint, it was found that this field needs to be able to be set to null if the field is empty.
This is required to remove a preferred token if desired.

@manicminer - found this bug when working on the new resource. Seems this is needed to allow the field to be set to null.
Thanks!


bug:  insight page cards not updating between 30d and 3m

@jpmcb I was under the impression that those cards should be showing numbers based on the selected filter (7 days, 30, 3mo).

Ok, digging into this a little further. Looks like contribs changes for 7 and 30, but not for 3mo. Nothing else seems to change though. And the tooltips say that it's over the selected time period.

https://github.com/open-sauced/app/assets/34313413/1586efaa-fe04-4bc2-b9da-b680c80131b6
Originally posted by @BekahHW in https://github.com/open-sauced/app/issues/2781#issuecomment-1969880371

We should investigate why the cards aren't updating between 30d and 3m (but they are in 7d). Here's another example:
30 days:

3 months:

I wonder if this is a caching problem introduced by: https://github.com/open-sauced/api/pull/579
When I have caching disabled through my developer console in my browser, it updates the numbers correctly. Is there a way client side to ignore http caches for certain cases? Or should the API be more deterministic in how it hands out cache headers?

I wonder if this is a caching problem introduced by: open-sauced/api#579
When I have caching disabled through my developer console in my browser, it updates the numbers correctly. Is there a way client side to ignore http caches for certain cases? Or should the API be more deterministic in how it hands out cache headers?

I haven't tested it, but if we pass these headers in the fetch request, pragma: no-cache and cache-control: no-cache, it should bypass the caching.


Fix LTP failures on newer distros

LTp installation was failing during make on newer distro due to regression in the LTP version. Updated LTP version which fixed the issue

@LiliDeng Let's merge #2374 before merging this PR. I ran it on few newer distros and it passes the installation steps but the overall testcase fails due to copy back issue. Once #2374 is merged, I will ensure the tests are passing end to end.

@somil55 #2374 has been merged, please rebase the code, and do some testing.


[Relationship] Enable node connection via some intermediary node

Notes for Reviewers

Supports enabling connection between two entity via third entity, e.g Pod to PV via PVC
Added the schema support as well

This PR fixes #
Signed commits

[x] Yes, I signed my commits.

While we're not taking this specific approach, @MUzairS15 @Abhishek-kumar09 this is still an open concern.


Add support for gzip content-encoding

Resolves https://github.com/prometheus/client_python/issues/775
If an Accept-Encoding:gzip header is present, will compress the output and set the correct Content-Encoding header in the response. Added tests for both the wsgi and asgi implementations.

One thing to note, the golang client allows disabling compression as part of the options passed to the handler. I am wondering if we should do something similar here? The reason being, in some cases the cpu usage required to compress a large response can slow everything down too much.

Yeah, definitely, this makes sense. What would be the preferred semantic? GZIP compression enabled or disabled by default? I am conscious that if we enable it by default, some existing users of the client might see unexpected CPU spikes when using the new version of the client, so maybe we should require enabling GZIP compression explicitly?


#164694224 Users should comment on articles

Description of tasks to be completed
Have the following endpoints working
POST api/articles/<slug>/comments
GET api/articles/<slug>/comments
GET api/articles/comment/<pk>
PATCH api/articles/comment/<pk>
DELETE api/articles/comment/<pk>
POST api/articles/<slug>/comments
GET api/articles/comment-replies/<comment_id>
GET api/articles/comment-replies/<comment_id>
PATCH api/articles/replies/<pk>
DELETE api/articles/replies/<pk>
How should this be manually tested

clone the repo and cd into the directory then create a virtualenv and activate
install all the requirements using command 'pip install -r requirements.txt'
ensure to set all the environment variables in the .env file and the run the server using command 'python manage.py runserver'
open postman or your favorite client and test out all the endpoints listed above
use this data format in the body {"comment_body":"value",} for comment
use this data format in the body {"body":"value",} for reply

Alternatively

You can test out the above endpoints using a link provided by the review app with the same data format

What are the relevant pivotal tracker stories
#164694224

Coverage decreased (-5.5%) to 89.303% when pulling 98e4a005ab55d8beed2b062a80ef998de62cf4a9 on ft-add-comment-article-164694224 into dfbf2d4e7182cc1eff6bd0c9eac5a3864730217d on develop.

* use this data format in the body {"comment":{"comment_body":"value",}} for comment

* use this data format in the body {"reply":{"body":"value",}} for reply

@sebbss could you please update the example request body to match the request data format defined in the article views.py

Nice work @sebbss, however you should consider to use status code of 200 for delete

@sebbss , nice work so far.
However, I have some feedback that I need you to implement

@sebbss , fix the code climate issues


[ome] Just erase the destructure rather than trying to get rid of dea…

…d instructions due to simplifyInstruction.
This ensures that we do not run into any iterator invalidation issues. It does
worsen the passes output slightly, but avoiding the complexity is worth it and
other later passes will clean up the dead code.
rdar://55811732

@swift-ci test

@eeckstein I do! Sorry I didn't add it to the PR! Thanks for catching that!

@swift-ci smoke test


flash attention forward vs forward full?

I don't quite understand the difference between forward_flashattn and forward_flashattn_full in your script. It seems that the full version did not do any shift attention, am I right? Then, why you did not use forward_flashattn for supervised fine tuning or in other word, did not do any shift attention for supervised fine tuning?

does this mean for inference, using both are fine? will there be any performance gap between them?

During inference, full attention would be better. Shift short attention is designed for training. The gap will not large.

I will close this issue as it has been inactive for several days. Please feel free to re-open it if there are any other things to discuss.

Hi @fahadh4ilyas,
I provide a new version implementation of S2 Attn in https://github.com/dvlab-research/LongLoRA/blob/61d469085de348b53e480125ca6fb43f19dc0ed9/llama_attn_replace_sft.py#L24
It supports supervised fine-tuning. Please git clone again and try this new sft code. I have tested it on a 7B model and it works well.
Regards,
Yukang Chen


Tests with PHP 8

Coverage remained the same at 96.383% when pulling 27f98aeaa615b12b848f1c954bf274f4c6e9bd26 on fix/php-8 into 2280c4c54e171bac711473ae0df673193e32a546 on master.


Rspec version and Test Errors

Is it possible to bump Rspec dependency to the latest version? I am currently packaging ice_cube for debian and while running the tests, I got this error
IceCube::TimeUtil
in America/Anchorage
should be able to calculate end of dates without active_support (PENDING: around hook at ./spec/spec_helper.rb:24 did not execute the example)
should be able to calculate beginning of dates without active_support (PENDING: around hook at ./spec/spec_helper.rb:24 did not execute the example)
should serialize to hash without error (PENDING: around hook at ./spec/spec_helper.rb:24 did not execute the example)
in Europe/London
should be able to calculate end of dates without active_support (PENDING: around hook at ./spec/spec_helper.rb:24 did not execute the example)
should be able to calculate beginning of dates without active_support (PENDING: around hook at ./spec/spec_helper.rb:24 did not execute the example)
should serialize to hash without error (PENDING: around hook at ./spec/spec_helper.rb:24 did not execute the example)
in Pacific/Auckland
should be able to calculate end of dates without active_support (PENDING: around hook at ./spec/spec_helper.rb:24 did not execute the example)
should be able to calculate beginning of dates without active_support (PENDING: around hook at ./spec/spec_helper.rb:24 did not execute the example)
should serialize to hash without error (PENDING: around hook at ./spec/spec_helper.rb:24 did not execute the example)
IceCube::Schedule using ActiveSupport
An error occurred in an around(:example) hook
NoMethodError: undefined method reset_all' for nil:NilClass     occurred at /usr/lib/ruby/vendor_ruby/rspec/mocks.rb:22:inteardown'
works with a single recurrence time starting from a TimeWithZone (FAILED - 1)
An error occurred in an around(:example) hook
NoMethodError: undefined method reset_all' for nil:NilClass     occurred at /usr/lib/ruby/vendor_ruby/rspec/mocks.rb:22:inteardown'
works with a monthly recurrence rule starting from a TimeWithZone (FAILED - 2)
Any idea how to fix this

RSpec should only be a development dependency, and not needed for packaging, but we'll try to get it updated for RSpec 3 anyway.

RSpec was updated. Closing!


Verify an error messages in tests

Coverage remained the same at 90.262% when pulling baf4fb900a64210663f7bbec10f321f6e4d97d6c on verify_test_messages into da72d9c2fc6bea035ff9e320f50ab64e62fadb6b on code_style.


Update test_hdf.py

[ ] Tests added / passed
[ ] Passes black dask / flake8 dask

Incorporating the suggestions from gforsyth and preventing re-using the same file handler when writing and reading

Changed default mode to 'r' instead of 'w' to imitate pandas API more closely in this pull request, but required changing the use of file handlers
https://github.com/dask/dask/pull/7039#issuecomment-756283657

Changed default mode to 'r' instead of 'w' to imitate pandas API more closely in this pull request, but required changing the use of file handlers
https://github.com/dask/dask/pull/7039#issuecomment-756283657


motionProperties is not assignable to type 'Partial for useSpring

System info

Operating System: Windows_NT
Node Version:     v20.16.0
Nuxt Version:     3.13.0
CLI Version:      3.13.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      compatibilityDate, devtools, css, modules
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Reproduction
import { useMotionProperties, useSpring } from '@vueuse/motion'

const balloon = ref<HTMLDivElement>()
const { motionProperties } = useMotionProperties(balloon, {
  x: 0,
  y: 0,
})
const { set } = useSpring(motionProperties)

Describe the bug

Additional context

Logs
No response

Having the same issue here. @JianJroh did you find any solution?


Timed out waiting to flush EmbeddedEngine offsets to storage

Currently I am facing the issue: "Timed out waiting to flush EmbeddedEngine offsets to storage" while syncing a table more than 1M records.
ERROR io.debezium.embedded.EmbeddedEngine  - Timed out waiting to flush EmbeddedEngine{id=company} offsets to storage
This is my config:
offset.flush.interval.ms: 10000
offset.flush.timeout.ms: 60000

Can you please help me? What should I do now?

Hi @congvmit ,
Can you please provide more information, does it only happen with 1M records.
Also are you replicating from MySQL or PostgreSQL?
Im assuming you updated the clickhouse username/password fields in the config.
offset.storage.jdbc.url: "jdbc:clickhouse://clickhouse:8123/altinity_sink_connector"
offset.storage.jdbc.user: "root"
offset.storage.jdbc.password: "root"

schema.history.internal.jdbc.url: "jdbc:clickhouse://clickhouse:8123/altinity_sink_connector"
schema.history.internal.jdbc.user: "root"
schema.history.internal.jdbc.password: "root"


API Log Integrity

Added support for persistent usernames (if user model object is deleted). Added support for the log to be read-only in Django admin. Defaults are configured for full legacy support.
These are two "security" related patches that I find myself constantly backloading into projects with this package. Figured I would clean it up into something that others might find useful.

Tests fail across the board due to PyYAML having dropped support for Python 3 < 3.5.0.

@cyclops26 : if you would like to submit this PR into https://github.com/lingster/drf-api-tracking I can merge and deploy this for you as I've just taken up the challenge to maintain this project.

@lingster Let me rebase to your fork and I will send a PR.


Obsolete FixedArrayAttribute

FixedArrayAttribute doesn't seem to be used anywhere and I fell into the trap of using it instead of FixedSizeArrayAttribute.

I..honestly can't remember why this is here.


[TF-TRT] Improvements of the TRTConverterV2 summary

Minor improvements of the TRTConverterV2.summary() method with detailed=True

@bixia1 for review

@bixia1 what is holding back this PR from being merged ? It's approved


ItemList tooltip does not update when Itemlist scrolls

Operating system or device - Godot version:
Godot Master ( 16/9/2016 )
Issue description (what happened, and what was expected):
When mousing over a ItemList element, a tooltip will display.  If the arrow keys are used to change the selection until the ItemList scrolls, the tooltip remains static while the item under the mouse cursor stays the same.  Expected behavior is for the tooltip to change either on any key input or when the ItemList scrolls.
Steps to reproduce:
Create an ItemList.
Population ItemList with more elements than can be displayed.
Click an item to give the ItemList focus and select that item.
From here, do not touch mouse.
Observe the tooltip.
Press up/down arrows until the ItemList scrolls.
Tooltip remains static even though mousedover element does not match tooltip. Unexpected Behavior
Link to minimal example project (optional but very welcome):
https://www.dropbox.com/s/mz1gb2k0oyq0cxf/Godot 2.1 ItemListScrolling bug demo.zip?dl=0

On looking through item_list.cpp, get_tooltip is not ever called.  Nor is it called in control.cpp.  This appears to be a wider issue overall with anything that uses tooltips.

Researching this issue further, it seems related to viewport.cpp . If a control mode moves for whatever reason, it never gets the mouseexit signal which would lead to the tooltip expiring.

First of all thank you for your report and sorry for the delay.
We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.
We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about it here?
For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.
Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.
Thanks in advance.
Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

I tested this in Godot 3.0.2.  Scrolling via the arrow keys still causes this bug to occur.

Scrolling via the mouse wheel causes the tool tip to disappear, but the new one does not appear as expected.

I don't understand this issue and the demo project does not work

Closing as I am not sure this is even a bug. Please feel free to reopen with a demo project attached if something is found


Update shellcheck.yml

FIX shellcheck YAML configuration

I rebased the branch shellcheck-issue-18 on master after merging the PR #30 and now the check "shellcheck / lint" pass \o/
Good job and thanks for both PR @phe-sto


Allow Ktile vis server to work when Jupyter notebook is run on arbitrary port

Previously, it was required to specify a url in the [ktile] section of the geonotebook.ini file, which essentially set the port number that the Ktile vis server would look for the Jupyter notebook instance on. This meant that notebook instances launched with a --port that did not match that in the url would fail to display layer data.  This affected any notebook instance launched from JupyterHub.
To determine the port on which the Tornado webapp was running, I used of a ZeroMQ socket plugged into the Tornado event loop. Now, it is possible to make queries on port 14253 to determine the port number of the running process.
Along the way, I used this 0MQ system to eliminate the use of Python's requests library in the ktile server. This ought to allow for a simplified handler structure in the webapp, and should remove a layer of indirection.
On the downside, this mod won't allow multiple users on the same system to run concurrently due to contention for the port that 0MQ is listening on.

There is a question about whether it is worthwhile to eliminate the handlers that exist, as far as I can tell, in order to register and delete layers and kernels.  There is a simplified version of this PR that can be made which only communicates port information.  I have yet to remove the handlers in question, so I'm not entirely sure if their existence is superfluous in the presence of this change, or if their GET methods are being called from other places in the code aside from the vis server.

@jpolchlo Thanks for this PR,  it looks like a really great start.  I haven't had a chance to pull this down and play around with it but I will in the next day or two.

Just for context, I did what I could figure to get the POST method to work, but operating within a JupyterHub environment requires an XSRF token to accompany the POST.  That token should be acquired via a call to jupyterhub token <username>, which fails inside start_kernel, as I believe the kernel needs to be established before the call will succeed.  I'm likely missing something, so I'll take suggestions.
At any rate, the fact that these tokens are required or not depending on how Jupyter was launched (hub or non) gives me the willies.  It makes the 0MQ solution seem less like overengineering.
If it works out, then I wonder if all but the KtileTileHandler should be eliminated?

@jpolchlo This is looking really good to me.  It seems like i neglected to turn on CI builds for forked repos,  and it doesn't look like there is a way i can trigger the build now that i've turned it on. Can you push a trivial change just so we can run this through the CI testing? Thanks!

@jpolchlo I am seeing a slightly strange issue and i'm wondering if you can see if you can replicate.  When I build the docker container on this branch and run the tests in tests/integration/add_layer.ipynb  I am seeing some weird javascript zindex behavior.  Adding a layer works (i.e. if you look in the network tab you can see the correct tiles being added),  but the zindex is placing the tiles under the OSM base tiles.
If you could just build the docker container,  mount tests/integration:/notebooks inside the container,   run tests/integration/get_test_data.sh and see if you're seeing the same behavior? Thanks!

I do observe that behavior in the container, but not, oddly, on my local machine.  The comm request which adds the layer (the new replacement for the old requests mechanism), shows that the add_layer command is triggered with the same options:
{
  'action': 'add_layer',
  'json': {
    'provider': {
      'class': 'geonotebook.vis.ktile.provider:MapnikPythonProvider',
      'kwargs': {
        'attribution': None,
        'bands': (1, 2, 3),
        'colormap': [],
        'dtype': 'float32',
        'gamma': 1.0,
        'interval': None,
        'layer_type': None,
        'name': 'WELD_8701612853329736007',
        'nodata': -9999.0,
        'opacity': 1.0,
        'path': '/home/jpolchlopek/work/geonotebook/tests/integration/data/WELD.tif',
        'projection': 'EPSG:3857',
        'raster_x_size': 7243,
        'raster_y_size': 1900,
        'transform': (-123.06229313641593, 0.0007517610843588367, 0.0, 48.571429239198785, 0.0, -0.0007517610843588367),
        'zIndex': 0
      }
    }
  },
  'kernel_id': 'dad2b4ef-fff7-4022-9fca-02e4722979ee',
  'layer_name': 'WELD_8701612853329736007'
}

Only the name field is slightly different, as expected.
pip freeze in the two containers reports the following (asterisks call out version differences):
  DOCKER CONTAINER                          LOCAL MACHINE
  ----------------                          -------------
  affine==2.1.0                             affine==2.1.0
  ansible==<IP_ADDRESS>                          ansible==<IP_ADDRESS>
* asn1crypto==0.23.0                        asn1crypto==0.22.0
                                            astroid==1.5.3
  backports-abc==0.5                        backports-abc==0.5
  backports.shutil-get-terminal-size==1.0.0
  bcrypt==3.1.3                             bcrypt==3.1.3
  beautifulsoup4==4.4.1
* bleach==2.1.1                             bleach==2.0.0
                                            boost==0.1
* certifi==2<IP_ADDRESS>                      certifi==2017.4.17
* cffi==1.11.0                              cffi==1.10.0
* chardet==2.3.0                            chardet==3.0.4
  click==6.7                                click==6.7
  click-plugins==1.0.3                      click-plugins==1.0.3
  cligj==0.4.0                              cligj==0.4.0
  configparser==3.5.0
* cryptography==2.0.3                       cryptography==2.0.2
  cvxopt==1.1.4
  cycler==0.10.0                            cycler==0.10.0
  Cython==0.23.4
                                            dateutils==0.6.6
  decorator==4.1.2                          decorator==4.1.2
  entrypoints==0.2.3                        entrypoints==0.2.3
  enum34==1.1.6
  Fiona==1.7.1                              Fiona==1.7.1
                                            Flask==0.12.2
  functools32==3.2.3.post2
  futures==3.0.5                            futures==3.0.5
  GDAL==2.1.0                               GDAL==2.1.0
* geonotebook==0.0.0                        e git+git@github.com:jpolchlo/geonotebook.git@151563bb91a1f9339f698ba2781d772f07542c06#egg=geonotebook
                                            geopyspark==0.2.0rc5
                                            gevent==1.2.2
                                            greenlet==0.4.12
* html5lib==1.0b10                          html5lib==0.999999999
* idna==2.6                                 idna==2.5
  ipaddress==1.0.18
* ipykernel==4.5.2                          ipykernel==4.6.1
* ipython==5.5.0                            ipython==6.1.0
  ipython-genutils==0.2.0                   ipython-genutils==0.2.0
* ipywidgets==7.0.1                         ipywidgets==7.0.0
                                            isort==4.2.15
                                            itsdangerous==0.24
  jdcal==1.0
                                            jedi==0.10.2
  Jinja2==2.9.6                             Jinja2==2.9.6
  joblib==0.9.4
  jsonschema==2.6.0                         jsonschema==2.6.0
  jupyter==1.0.0
  jupyter-client==5.1.0                     jupyter-client==5.1.0
  jupyter-console==5.2.0
  jupyter-core==4.3.0                       jupyter-core==4.3.0
                                            lazy-object-proxy==1.3.1
* lxml==4.0.0                               lxml==3.8.0
  mapnik==0.1                               mapnik==0.1
  MarkupSafe==1.0                           MarkupSafe==1.0
                                            Mastodon.py==1.0.8
  matplotlib==2.0.2                         matplotlib==2.0.2
                                            mccabe==0.6.1
  mistune==0.7.4                            mistune==0.7.4
  ModestMaps==1.4.7                         ModestMaps==1.4.7
  munch==2.2.0                              munch==2.2.0
* nbconvert==5.3.1                          nbconvert==5.2.1
* nbformat==4.4.0                           nbformat==4.3.0
                                            ndg-httpsclient==0.4.2
  networkx==2.0
  nose==1.3.7
* notebook==5.1.0                           notebook==5.0.0
                                            npm==0.1.1
  numexpr==2.4.3
* numpy==1.13.3                             numpy==1.11.1
  olefile==0.44                             olefile==0.44
  openpyxl==2.3.0
                                            optional-django==0.1.0
  pandas==0.20.3                            pandas==0.20.3
  pandocfilters==1.4.2                      pandocfilters==1.4.2
* paramiko==2.3.1                           paramiko==2.2.1
  pathlib2==2.3.0
  patsy==0.4.1
  pexpect==4.2.1                            pexpect==4.2.1
  pickleshare==0.7.4                        pickleshare==0.7.4
* Pillow==4.3.0                             Pillow==4.1.1
  ply==3.7
  promise==0.4.2                            promise==0.4.2
  prompt-toolkit==1.0.15                    prompt-toolkit==1.0.15
* protobuf==3.1.0                           protobuf==3.3.0
  ptyprocess==0.5.2                         ptyprocess==0.5.2
* py==1.4.31                                py==1.4.34
* pyasn1==0.3.6                             pyasn1==0.3.1
* pycparser==2.18                           pycparser==2.17
  pycrypto==2.6.1                           pycrypto==2.6.1
  Pygments==2.2.0                           Pygments==2.2.0
                                            pylint==1.7.2
  PyNaCl==1.1.2                             PyNaCl==1.1.2
* pyOpenSSL==17.3.0                         pyOpenSSL==17.2.0
  pyparsing==2.2.0                          pyparsing==2.2.0
  pyproj==<IP_ADDRESS>                           pyproj==<IP_ADDRESS>
* pytest==2.8.7                             pytest==3.1.3
  python-dateutil==2.6.1                    python-dateutil==2.6.1
                                            python-pam==1.8.2
  pytz==2017.2                              pytz==2017.2
  PyWavelets==0.5.2
  PyYAML==3.12                              PyYAML==3.12
  pyzmq==16.0.2                             pyzmq==16.0.2
  qtconsole==4.3.1                          qtconsole==4.3.1
  rasterio==0.36.0                          rasterio==0.36.0
  requests==2.11.1                          requests==2.11.1
  scandir==1.6
  scikit-image==0.13.1
  scikit-learn==0.17
  scipy==0.19.1                             scipy==0.19.1
  seaborn==0.6.0
* Shapely==1.5.17                           Shapely==1.6b4
  simplegeneric==0.8.1                      simplegeneric==0.8.1
* simplejson==3.8.1                         simplejson==3.10.0
  singledispatch==<IP_ADDRESS>
  six==1.10.0                               six==1.10.0
  snuggs==1.4.1                             snuggs==1.4.1
                                            SQLAlchemy==1.1.11
  statsmodels==0.6.1
  subprocess32==3.2.7
  tables==3.2.2
  terminado==0.6                            terminado==0.6
  testpath==0.3.1                           testpath==0.3.1
  TileStache==1.51.6                        TileStache==1.51.6
* tornado==4.5.2                            tornado==4.5.1
  traitlets==4.3.2                          traitlets==4.3.2
                                            typing==3.6.2
                                            urllib3==1.21.1
  wcwidth==0.1.7                            wcwidth==0.1.7
  webencodings==0.5.1                       webencodings==0.5.1
* Werkzeug==0.11.13                         Werkzeug==0.12.2
* widgetsnbextension==3.0.3                 widgetsnbextension==3.0.2
                                            wrapt==1.10.11
  xlrd==0.9.4
  xlwt==0.7.5

Surely there is other information that might be useful.  Let me know what you'd like to see.

@jpolchlo can we close this issue?


Mast: Watch (?-i:66ee4434d7a0d89bcd6f94c236eb7397)(?#apnews.com)

Mast requests the watch of the watch_keyword (?-i:66ee4434d7a0d89bcd6f94c236eb7397)(?#apnews.com). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

(?-i:66ee4434d7a0d89bcd6f94c236eb7397)(?#apnews.com) has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Raise minimum required TS version to 4.1

TS 4.1 will have a lot of new and interesting power for complex type expressions. We should lock in that requirement for Nexus before hitting 1.0. This way we can start to roll out features after without requiring to hit this breaking change after 1.0 so soon.
There might not be any immediate end-user benefits by raising the TS bar to 4.1 however improved internal typings and typegen will be indirectly important to project health and momentum.

Can't wait to turn on noUncheckedIndexedAccess and see how much guarding we need to do in the existing code. Hopefully won't be too bad, but just tried it out for the first time on some projects and it was 😬


Support Versioned Docs

Currently, docs runs on the main branch. Docs should be versioned, where the default version is the latest supported version, e.g. v0.2.0.

I will work on this in v0.3.0-rc1.