Send lastModified with the UpdateWorkspaceCustomUnit and UpdateWorkspaceCustomUnitRate commands

HELD on: https://github.com/Expensify/Web-Expensify/pull/35328
Fixed Issues
Related to fixing the following offline QA tests
https://github.com/Expensify/Expensify/issues/232202
https://github.com/Expensify/Expensify/issues/232404
https://user-images.githubusercontent.com/31285285/198397825-0bcc95c6-1e13-4c64-8fc0-75c621657f31.mov
NOTE: the custom unit value being different after we come back online is a separate issue, most likely related to https://github.com/Expensify/Expensify/issues/229696
Tests and QA
Custom Unit

Navigate to any existing workspace on deviceA > Reimburse expenses. Go offline.
Switch to deviceB. Sign into the same account, and navigate to the same workspace > Reimburse expenses.
Edit the Unit dropdown (with options Miles/Kilometers)
Observe it shows in the pending state
Switch back to deviceA. Make sure you're still offline. Edit the same unit field.
Go back online on deviceA
Observe the unit field fails to update because the workspace was modified while you were offline, displaying the RBR and error message

Attempt to update the rate field again while online. Verify that you are able to modify the field and that no errors show.

Custom Unit Rate

Navigate to any existing workspace on deviceA > Reimburse expenses. Go offline.
Switch to deviceB. Sign into the same account, and navigate to the same workspace > Reimburse expenses.
Edit the Rate input
Observe it shows in the pending state
Switch back to deviceA. Make sure you're still offline. Edit the same rate field.
Go back online on deviceA
Observe the unit field fails to update because the workspace was modified while you were offline, displaying the RBR and error message

Attempt to update the rate field again while online. Verify that you are able to modify the field and that no errors show.

PR Review Checklist

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

@youssef-lr requesting you for review since you were PullerBeared on the associated Web-E PR, thanks in advance for your review!

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Now that Web-E #35328 has hit production, removing the hold. Let's get this one merged!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @jasperhuangg in version: 1.2.23-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @Julesssss in version: 1.2.23-9 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Numero instagram

Before sending your pull-request 💌 make sure :

[ ] The tests are up-to-date and your code is tested

We have a problem on ios but not on Android:
android:

ios:

It's good on Iphone


Support serve files without extension

Author should do the followings, if applicable
[x] Add tests
[x] Run tests
[x] yarn denoify to generate files for Deno
News

Add support to serve static files without extension.
This is because I need certbot validate the domain and it generate files without extension.

Hi @arucard17
Thanks for the PR. But, your problem may be solved in PR #2260. This is not merged into the main, but will be merged soon. So, we have to close the PR, though we appreciate it.

Closing the PR. Thanks!


lib: Add RPi4 Unipi Neuron support to testbot

Change-type: patch
Signed-off-by: Florin Sarbu<EMAIL_ADDRESS>

@balena-ci I self-certify!


Del: Remove duplicate functions

📌 Checklist before creating the PR

[x] I have created an issue for this PR for traceability
[ ] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
[ ] I have added relevant tags if possible for us to better distinguish different PRs

🚨 Issue number

Link this PR to your issue with words like fixed to automatically close the linked issue upon merge
proposal#3624

📝 What does this PR do?
Remove duplicate functions that exist within ppo.py
💥 Checklist before requesting a review

[x] I have linked my PR to an issue (instruction)
[x] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
[x] I have performed a self-review of my code
[ ] I have added thorough tests.
[ ] I have added docstrings for all the functions/methods I implemented

⭐ Do you enjoy contributing to Colossal-AI?

[ ] 🌝 Yes, I do.
[ ] 🌚 No, I don't.

Tell us more if you don't enjoy contributing to Colossal-AI.

Hi @ddobokki Thanks so much for your contribution!


Nuget Install error

seriousness code explain project file that 's ok Disable display status
error Cannot install package 'jsonpath. Net 0.1.12'. You are trying to install this package into a project targeting ". Net framework, version = v4.7.2", but the package does not contain any assembly references or content files compatible with the framework. For more information, contact the package author.

Since .Net Standard 2.1 not supported in any .Net Framework you should update to .Net 5.

It's not so easy to update a Framework application to Core or .Net 5.
But @LordXaosa is correct.  This library requires .Net Standard 2.1 features, specifically Span<T> and Range.  You'll need to update to a version of .Net that supports Standard 2.1 packages.  You can see the list here.  Unfortunately, no version of Framework supports it.

@careylipu did you have any further questions here?


Awkward Harbor login flow: Schema is mandatory.

I don't think the schema should be mandatory.
 ./harbor login demo.goharbor.io -u admin -p Harbor12345
Error: login failed, please check your credentials: Get "https://localhost/demo.goharbor.io/users/current": dial tcp <IP_ADDRESS>:443: connect: connection refused
Usage:

[ ] Use HTTPS by default. (secure by design)
[ ] Use only HTTP if explicitly specified.
[ ] Add option to ignore errors in self signed certs. eg. (--inecure) like in curl

I faced the same issue! Let me see how I can fix it

This has been fixed. @Vad1mo, we can close this issue. is there anything else you'd like to add? if there you can reopen this issue.


Implement Singly Linked List in C++

Hi @Aman83770 Linked list in C++ is already implemented, so I would have to invalidate this PR. You can, however, work on any other algo/ds just make sure to create an issue for it so that a maintainer can assign it to you. 😄


connection.close always cause Connection reset by peer

During call of await connection.close() in finally block of the example, I always getting Connection reset by peer exception generated by LDAP stream transformer.
I thought maybe I need to close stream prior to closing connection, but even without any search queries, with only one explicit connection.bind() behaviour stays the same...
FINE: 2018-11-10 22:26:13.422664: close
FINEST: 2018-11-10 22:26:13.423224: close: started
FINEST: 2018-11-10 22:26:13.425320: wait for message stream to be done
SEVERE: 2018-11-10 22:26:13.469022: LDAP stream transformer: error=SocketException: OS Error: Connection reset by peer, errno = 54, address = dc.mydomain.com, port = 50844
FINER: 2018-11-10 22:26:13.469475: listen: onError
FINEST: 2018-11-10 22:26:13.470519: LDAP stream transformer: byte stream done

I'm not sure if it's correct, but if I change _socket.close() to _socket.destroy() in connection_manager.dart, everything completes with no error. But I don't know if it is good to do this way or not.

From reading  https://api.dartlang.org/stable/2.0.0/dart-io/Socket/destroy.html
I think destroy is what we want - since it kills the socket for read and write.
I'll make that change and incorporate into the next release.
Thanks for the bug report!!

Thanks for a quick response, now it works without exceptions!
By the way, Socket.destroy() is not asynchronous, so it doesn't need await. I'm not sure it's really important, probably it's more about cleaning a code, because it's working with and without it :)


Feature Request: base url

be able to set a base url (sub path) so that you can host at, for example:
https://example.com/jellystat
instead of
https://jellystat.example.com
ideally, let this be set by an env var like:
BASE_PATH=foo
yielding responses at:
$scheme:$domain/foo

Hi @ftc2 , can you perhaps share a sample config and what reverse proxy you are using? I'm not sure how this would affect accessibility. If I can replicate it maybe I can develop a work around.
What error do you get when accessing the URL based on a this configuration aswell.

i haven't actually tested it, i just assumed it wouldn't work. i've had very bad luck with projects using node frameworks supporting this feature.
will confirm it doesn't "just work" later today and share a sample config :)

Hi @ftc2, sorry i completely missed this comment, yes please do, i will test and see if i can replicate the behavior you described

@CyferShepard
no worries, here you go. made you this to play with:
https://github.com/ftc2/jellystat-nginx
includes production-ish settings for postgres in the docker compose.
in the nginx config, i show you two common options for subpath aka basepath config. i am not optimistic, though. in my limited experience with node framework type projects, if basepath is supported at all, it's not supported as something that can be set at runtime lol. idk what the deal is.
something i wanted to point out 'early' though because it's a very frequently requested feature in the automated media app ecosystem.

So I managed to replicate the issue. This is really one confusing scenario, thanks for pointing it out but. I did some research and I'm so happy this was pointed out so early in development as the fix for it seems to be very time consuming as il need to rework some of the api endpoints in the react part of things.

Would be awesome to have that feature, I'd want to run my jellystat intance behind an nginx proxy at http://<domain>.io/stats/


Use correct env vars for CI

ghprbPullId is no longer being passed to our CI scripts. This PR changes to use the new ones as implemented in https://github.com/kubernetes/test-infra/pull/1204. This PR can be merged before that PR as we are currently in a broken state either way.

cc @prydonius @lachie83

W1129 19:34:19.065] ./test/e2e.sh: line 26: PULL_NUMBER: unbound variable
@viglesiasce is it not available yet?

Correct. Keep an eye on the PR listed:
kubernetes/test-infra#1204

LGTM

@k8s-bot e2e test this


[DNM] Upgrade RocksDB to 6.4.x

Upgrade RocksDB to 6.4.x.
Signed-off-by: Yi Wu<EMAIL_ADDRESS>

/run-all-tests


Update the Marot downloading instructions in README.md

Simplify the Marot downloading instructions to point to just marot-lite.html instead of all the component files. This simplified description will also not become obsolete as we add mode code files to Marot (such as marot-utils.js getting added soon).

Ping


Update and rename EN.xaml to FR.xaml

hope this helps

Why did you delete the whole EN.xaml? :D And you forgot to translate the main localisation file: https://github.com/Sophia-Community/SophiApp#translating


Can't enable namespace disabled by notThis

Usecase:
set DEBUG=knex:query && node file.js
const DebugModule = require('debug')

//temporary disable logging
let x = DebugModule.disable()
DebugModule.enable(x+ ',-knex:query');  // almost OK: knex:query,-knex:query

//and try re-enable
x = DebugModule.disable()
DebugModule.enable(x+ ',knex:query') // Don't work: knex:query,knex:query,-knex:query

I think that namespaces with identic name should be filtered before adding. (eg knex:*,-knex:*, not knex:query,-knex:*)
This is needed for temporary blocking and unlock namespaces eg by REST API.

This is a known issue and is listed to be fixed via #425.
Going to close as a duplicate.


Add doc for prometheus

/cc @kunmingg
/cc @jlewi

This change is

/assign @kunmingg
Kunming please review this when you can.

I think we should keep the Stackdriver part as some GCP users might not want to deploy prometheus.

https://github.com/kubeflow/kubeflow/issues/1635
PTAL

/lgtm
/approve


PDF files in private repository are 404

When I tap to open a PDF file in my private repositories, the app shows GitHub’s 404 page. It seems this does not happen in public repositories.
The app’s version is 1.27.2<PHONE_NUMBER>).

Bug Report Dump (Auto-generated)

Version 1.27.2<PHONE_NUMBER>)
Device: iPad7,11 (iOS 13.3)
TestFlight: false

https://github.com/GitHawkApp/GitHawk/issues/2889#issue-558503307


use venv for TensileCreateLibraryFiles on Linux (#2022)

use venv if vars set TensileCreateLibraryFiles on Linux to match Windows

(cherry picked from commit 7dbd7234068a3ee82b86b4571da5f3d0e3629707)

All valid CI runs passed, cherry pick of what is in develop


Auto Zoom + Pan on HOver

It would be great to have an option to zoom on hover (say to 300%) and follow the mouse.  Similar to how Amazon shows detailed images on hover.

@villanus Well, that is beyond the scope of this library. Instead, it could be another library using this one as dependency. All the needed methods are exported (setPosition, zoom). :sparkle:

how can i use this library on a complete SVG without creating elements by JQ ?


Build R-001 Parser

Is your feature request related to a problem? Please describe.
As a user, I want only the information associated with my warehouse.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Parts and document history are currently parsed nightly.


Chore/update docs

Update docs to describe usage of the component testing helper

Old, addressed in a different PR


Error when build (gulp build)

Hello
I'm trying to build the sdk and I get an error when I use the gulp build command.
[18:22:42] Using gulpfile ~/Dropbox/Public/TYPEUNSAFE-SITE/streamdataio-js-sdk/gulpfile.js
[18:22:42] Starting 'build'...
[18:22:42] Starting 'clean'...
[18:22:42] Starting 'clean:dist'...
[18:22:42] Finished 'clean:dist' after 11 ms
[18:22:42] Starting 'clean:tmp'...
[18:22:42] Finished 'clean:tmp' after 1.25 ms
[18:22:42] Starting 'clean:doc'...
[18:22:42] Finished 'clean:doc' after 272 μs
[18:22:42] Finished 'clean' after 15 ms
[18:22:42] Starting 'buildScript'...
[18:22:42] gulp-debug: src/Exporter.js
[18:22:42] gulp-debug: src/Logger.js
[18:22:42] gulp-debug: src/Preconditions.js
[18:22:42] gulp-debug: src/Listeners.js
[18:22:42] gulp-debug: src/StreamdataEventSource.js
[18:22:42] gulp-debug: src/StreamdataError.js
[18:22:42] gulp-debug: src/Streamdata.js
[18:22:42] gulp-debug: 7 items
[18:22:42] Finished 'buildScript' after 86 ms
[18:22:42] Starting 'minify'...
[18:22:42] gulp-debug: 0 items

/Users/k33g_org/Dropbox/Public/TYPEUNSAFE-SITE/streamdataio-js-sdk/node_modules/gulp-closurecompiler/gulp-closurecompiler.js:48
              base: firstFile.base,
                             ^
TypeError: Cannot read property 'base' of undefined
    at Stream.<anonymous> (/Users/k33g_org/Dropbox/Public/TYPEUNSAFE-SITE/streamdataio-js-sdk/node_modules/gulp-closurecompiler/gulp-closurecompiler.js:48:23)
    at /Users/k33g_org/Dropbox/Public/TYPEUNSAFE-SITE/streamdataio-js-sdk/node_modules/gulp-closurecompiler/node_modules/closurecompiler/ClosureCompiler.js:281:21
    at ChildProcess.<anonymous> (/Users/k33g_org/Dropbox/Public/TYPEUNSAFE-SITE/streamdataio-js-sdk/node_modules/gulp-closurecompiler/node_modules/closurecompiler/ClosureCompiler.js:273:15)
    at ChildProcess.EventEmitter.emit (events.js:98:17)
    at Process.ChildProcess._handle.onexit (child_process.js:789:12)

I've tried with node v0.10.9, v0.10.13, v0.11.16, v4.0.0 and v4.1.1

Hello,
Unfortunately, we cannot manage to reproduce the issue with the node versions provided.
The issue seems to be linked to the node module gulp-closurecompiler.
Can you provide the version number fetched by npm in your project for the following modules in package.json :

gulp-closurecompiler
gulp-closure-compiler

Thank you.

Hi,
"gulp-closure-compiler": "^0.2.16",
"gulp-closurecompiler": "^0.1.0",

Hello,
Actually, I'm talking about the modules fetched by npm, in the folder node_modules :-).
These versions are available at the following path :

node_modules/gulp-closure-compiler/package.json
node_modules/gulp-closurecompiler/package.json

Thank you.

"name": "gulp-closure-compiler",
"version": "0.2.20",
and
"name": "gulp-closurecompiler",
"version": "0.1.0",

Hello,
Thanks for the informations.
You have the same modules version than the one we have on our desktop.
We spotted that you might be on Mac system.
As we did tests on linux OS, let us try on Mac.
We keep you informed.

Hello,
The issue you are facing is actually not linked to operating system.
We have managed to reproduce the issue by removing the folder bower_components before doing the command "gulp build".
Can you please double check that the command "bower update" is working fine ?
You must have the following files in the project :
ls -l bower_components/eventsource-polyfill/
total 16
-rw-rw-r-- 1 dominique dominique  647 nov.  17 09:37 bower.json
drwxrwxr-x 2 dominique dominique 4096 nov.  17 09:37 dist
-rw-rw-r-- 1 dominique dominique 1072 nov.  17 09:37 LICENSE
-rw-rw-r-- 1 dominique dominique 1973 nov.  17 09:37 README.md
In folder dist, there are 3 javascript files : browserify-eventsource.js, eventsource.js, eventsource.min.js.
Keep us informed.

Hi @dominiquemongelli
bower update works fine
I've got the 3 files in the dist folder
but I've got the same error
as soon as possible, I'll try with an other Mac laptop
Regards

Hello,
Just for information here is the trace when gulp build command is OK :
[11:51:10] Using gulpfile ~/streamdataio-js-sdk/gulpfile.js
[11:51:10] Starting 'build'...
[11:51:10] Starting 'clean'...
[11:51:10] Starting 'clean:dist'...
[11:51:10] Finished 'clean:dist' after 63 ms
[11:51:10] Starting 'clean:tmp'...
[11:51:10] Finished 'clean:tmp' after 1.77 ms
[11:51:10] Starting 'clean:doc'...
[11:51:10] Finished 'clean:doc' after 28 ms
[11:51:10] Finished 'clean' after 99 ms
[11:51:10] Starting 'buildScript'...
[11:51:10] gulp-debug: bower_components/eventsource-polyfill/dist/eventsource.js
[11:51:10] gulp-debug: src/Exporter.js
[11:51:10] gulp-debug: src/Logger.js
[11:51:10] gulp-debug: src/Preconditions.js
[11:51:10] gulp-debug: src/Listeners.js
[11:51:10] gulp-debug: src/StreamdataEventSource.js
[11:51:10] gulp-debug: src/StreamdataError.js
[11:51:10] gulp-debug: src/Streamdata.js
[11:51:10] gulp-debug: 8 items
[11:51:10] Finished 'buildScript' after 160 ms
[11:51:10] Starting 'minify'...
[11:51:10] gulp-debug: bower_components/eventsource-polyfill/dist/eventsource.js
[11:51:10] gulp-debug: 1 items
[11:51:12] Finished 'minify' after 2.01 s
[11:51:12] Starting 'obfuscate'...
[11:51:12] gulp-debug: dist/libs.js
[11:51:12] gulp-debug: src/Exporter.js
[11:51:12] gulp-debug: src/Logger.js
[11:51:12] gulp-debug: src/Preconditions.js
[11:51:12] gulp-debug: src/Listeners.js
[11:51:12] gulp-debug: src/StreamdataEventSource.js
[11:51:13] gulp-debug: src/StreamdataError.js
[11:51:13] gulp-debug: src/Streamdata.js
[11:51:13] gulp-debug: 8 items
[11:51:18] Finished 'obfuscate' after 5.73 s
[11:51:18] Starting 'doc'...
[11:51:19] gulp-debug: src/api.js
[11:51:19] gulp-debug: README.md
[11:51:19] gulp-debug: 2 items
[11:51:19] Finished 'doc' after 855 ms
[11:51:19] Finished 'build' after 8.87 s
See that eventsource.js is used within the compilation process.
Keep us informed once you'll try with another laptop.
Regards

build successful with node v0.11.16 and v4.0.0 :+1:  :clap:

A last update :  the root cause of the issue is due to the configuration of bower.
Indeed, the target directory for bower update must put dependencies in PROJECT_FOLDER/bower_components.
If it's not the case, you can update the bower configuration in your .bowerrc file in the root folder of the project via the following conf :
{
"directory": "bower_components"
}


Decomposed with non-uniform scale?

Hi,
while using cgmath::Decomposed I saw that the scale field is V::Scalar which is just an amount.
What is the reason for that?
I think most CG related programs need non uniform scaling at some point.
-siebencorgie

I mean it shouldn't be too complicated to implement it as V instead of V::Scalar or am I missing something?


Added final touches to UI

-background animation
-button design

Please resolve the conflicts in this branch with the main branch @aastha01chauhan


-in  operators

Hi Guys !!
-in operator and here variant  are great but it perform only in list and its  checks only for membership:
PS C:\> 'b' -in 'a','b','c'
True

but its great to support  to checks for substrings and to keys in dictionnary:
### substring:
PS> "shell" -in "powershell"
True

PS> "b" -in "earth"
False

PS> "shell" -notin "powershell"
False

### checks keys in dictionnary:

PS> 'b' -in @{a=5; b=2}
True # actually it return False

I don't think reusing the operator in this way makes sense; it creates ambiguity for something like $a -in $b -- you have no way of knowing if $b is a string or an array, or a hashtable, without going to find both variables to see what's going on.
Also, why would it only be used to target keys in dictionaries rather than values? The usage in that case has an extra layer of ambiguity.

Language working group:
We agree with @vexx32's comment above, and will close this issue.


314 Setup eslint extending airbnb and prettierjs

from https://github.com/Terrastories/terrastories/issues/314

[x] Setup ESLint
[x] Configure ESLint
[x] Add documentation for developers to integrate with text editor

@kalimar Can you point me to a documentation page to which the developer integration notes to be added? Perhaps another section here -> https://github.com/Terrastories/terrastories/blob/master/SETUP.md

@mirandawang @MxOliver @kalimar Can you point me to a documentation page to which the developer integration notes to be added? Perhaps another section here -> https://github.com/Terrastories/terrastories/blob/master/SETUP.md

@midhunkrishna that's the right place for a new section. Perhaps Setting up your Development Environment?

@kalimar Documentation added.
Review pls @MxOliver @mirandawang

I'm wary to merge this in before we have any linting tests. I wouldn't want a bunch of unlinted code in our repo to fall upon one person to fix once we add the tests. How do you feel about adding some linting tests here? I can always open a separate issue for this work too, btw! @midhunkrishna
Thanks for the contribution, this is great!! (: It will definitely help with the maintainability of quality in this code.

@mirandawang Can you elaborate on what you meant by linting tests?

@mirandawang ping

@mirandawang ping cc: @MxOliver @kalimar

So I'm not entirely sure if this is what @mirandawang meant, but linting tests would be tests written to ensure that code passes whatever linting configuration we are choosing. I found this which might be helpful https://api.rubyonrails.org/classes/ActiveModel/Lint/Tests.html

https://github.com/Terrastories/terrastories/issues/371

@MxOliver I still am confused about what the expectation is. In this PR, I have linter configured with airbnb defaults, with a lint script in package.json which runs on every precommit, that way, commits will fail when the code that is written is not properly linted.
PR also has documentation for integrating eslint with code editors.
Before any work from #371 is merged, please check:
a) Eslint Config
b) package.json modifications
c) Pre Commit Hook

@MxOliver @mirandawang ping

@midhunkrishna Sorry for the late reply! Life + work got a little crazy.
And sorry for the confusion. Meant to ask about the linting script when I said tests.
Thanks for the helpful links! It looks like you already added everything we need. So we should be all good to merge :)


ScreenContext is stale when nested actions are used

Describe the bug
When two actions are used in nested fashion, the second action is unable to access properties exposed by first action
To Reproduce
Steps to reproduce the behavior:
# Not working (potential cause: id of pickFiles hasn't yet registered when uploadFiles is using it)
Column:
  children:
    - Button:
        label: Upload Files
        onTap:
          pickFiles:
            id: myFiles
            allowMultiple: true
            allowedExtensions:
              - jpg
              - png
              - mov
            onComplete:
              uploadFiles:
                id: myUploader
                files: ${myFiles.files}
                uploadApi: uploadFile
                onComplete:
                  executeCode: console.log(myUploader.body)
                onError:
                  executeCode: console.log('Upload error')

Expected behavior
To be able to use myFiles.files in uploadFiles action, and similarly, myUploader.body in onComplete action

The issue is that the callback is on the stack before the state is resolved since setState and callback are within the same function.
Two options to solve this:

Execute callbacks in a useEffect hook after all component state has been resolved to guarantee screenContext is up to date.
Greedily set state by either passing in additional context to the callback or setting widget state in context directly


Miniature mask not visible with black SVG background

Is there a way to change the miniature mask color (not the miniature background). Currently the mask is not clearly visible with an SVG with black background.

Not yet, but you can create your miniature component and inject it using the customMiniature prop.


Change template to view

In 3.0 template is deprecated (source) so the generated code should use view instead.

@mjstahl are you still planning to land this change?

The change to the code is done in this PR, but there are some tests that need to be updated: https://github.com/donejs/done-component/pull/21

Fixed by https://github.com/donejs/done-component/pull/21


Remove the "keep_master_clean" setting.

I don't like it. I feel that half of my PRs I want to "extract"
them to the PR branch so that they don't pollute the branch I am
working on, but the other half I want to keep on my current branch,
because I want to continue building commits on top of them.
So I propose to make it a command line flag instead. Spent a while
debating what the right word would be but I think "extract" makes sense ?

@gabrielreid do you use keep_master_clean ?
What do you think about this ?

I feel that half of my PRs I want to "extract"
them to the PR branch so that they don't pollute the branch I am
working on, but the other half I want to keep on my current branch,
because I want to continue building commits on top of them.

I am considering this PR.
I could also keep both the setting and the command line flag but I feel nothing else in opp does this, and maybe it's not worth the complexity ?

I'm somewhat ashamed to admit that I haven't been using keep_master_clean in my day-to-day work, but it's purely because of laziness to go and set it up all over the place in the opp config files 😬
I'm totally on-board with dropping the config and having a flag though, because I'm in the same boat as you: sometimes I want one behavior, and sometimes I want the other, so a flag looks like the way to go.


Release apks

It would be nice to have release apk's on GH release tags info.

i'm not sure i understand your request. the .apk's are for each version are in the "Recent Builds" folder (https://github.com/theksmith/CarBusInterface/tree/master/Recent Builds).
are you wanting non-debug compiled versions or ?

Oh, I see. Usually on GitHub, people let their builds out of the git folders and place them on each release tag.
I'm anxiously waiting for my ELM327 to arrive for testing this up. :D


docker-compose can not start docker image anymore

Hi,
first of all thaks for fixing the docker image. Unfortunately I am not able to get the docker image running anymore.
I tried to merge my docker-compose.yml file with yours, as yours has changed a lot. Maybe I am missing some part and you could give me a hint :-)
version: "3"

services:
  app:
    image: powerdns-admin:latest
    container_name: powerdns_admin
    ports:
      - "9191:9191"
      - "9393:9393"
    #volumes:
    #  # Code
    #  - .:/powerdns-admin/
    #  - "./configs/${ENVIRONMENT}.py:/powerdns-admin/config.py"
    #  # Assets dir volume
    #  - powerdns-admin-assets:/powerdns-admin/app/static
    #  - powerdns-admin-assets2:/powerdns-admin/node_modules
    #  - powerdns-admin-assets3:/powerdns-admin/logs
    #  - ./app/static/custom:/powerdns-admin/app/static/custom
    logging:
      driver: json-file
      options:
        max-size: 50m
    networks:
      - pda_default
    environment:
      - SQLALCHEMY_DATABASE_URI=mysql://${PDA_DB_USER}:${PDA_DB_PASSWORD}@${PDA_DB_HOST}/${PDA_DB_NAME}
      - GUINCORN_TIMEOUT=60
      - GUNICORN_WORKERS=2
      - GUNICORN_LOGLEVEL=DEBUG
      - PDNS_HOST=${PDNS_HOST}
      - PDNS_API_KEY=${PDNS_API_KEY}
    restart: unless-stopped

networks:
  pda_default:
    driver: bridge
    driver_opts:
      com.docker.network.bridge.name: pda0
    ipam:
      driver: default
      config:
        - subnet: <IP_ADDRESS>/24

#volumes:
#  powerdns-admin-assets:
#  powerdns-admin-assets2:
#  powerdns-admin-assets3:

I have an dot-env file looking like this:
PDA_DB_HOST=<IP_ADDRESS>
PDA_DB_NAME=pda
PDA_DB_USER=pda
PDA_DB_PASSWORD=***password*removed***
PDA_DB_PORT=3306

PDNS_HOST=<IP_ADDRESS>
PDNS_API_KEY=***password*removed***
PDNS_WEBSERVER_ALLOW_FROM=<IP_ADDRESS>

When trying to start the container like this:
root@ns1 src/PowerDNS-Admin (rns-1 *%) » docker-compose up -d; docker-compose logs -f

I get errors like this:
Creating network "powerdns-admin_pda_default" with driver "bridge"
Creating powerdns_admin ... done
Attaching to powerdns_admin
powerdns_admin |  * Tip: There are .env or .flaskenv files present. Do "pip install python-dotenv" to use them.
powerdns_admin | INFO  [alembic.runtime.migration] Context impl MySQLImpl.
powerdns_admin | INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
powerdns_admin | ERROR [root] Error: Multiple head revisions are present for given argument 'head'; please specify a specific target revision, '<branchname>@head' to narrow to a specific head, or 'heads' for all heads
root@ns1 src/PowerDNS-Admin (rns-1 *%) »

Unfortunately I have no idea what to do here :-) Do you think, you could provide a very little README for the docker stuff inside the docker folder? I have no idea where to define the API key stuff for powerdns now. You docker-compose.yml does not have variables for this. I am a little bit stuck and would be very happy to have powerdns-admin running again.
Best wishes
Christian

Hi @croessner ,
I see you are having this error
powerdns_admin | ERROR [root] Error: Multiple head revisions are present for given argument 'head'; please specify a specific target revision, '<branchname>@head' to narrow to a specific head, or 'heads' for all heads

It looks like your migration scripts are broken somehow. Are you using the latest source code to build the Docker image? You can also try with my image from Docker hub to see if it fixes your issue.
Regarding pdns API key stuff, it is stored in the PDA DB, so you will able to configure it after you login as admin in Settings > PDNS menu.

I found an article here that can explain to you about that error in case you are interested in fixing it.

Thanks for your answer. Unfortunately that did not help.
I have removed the source folder and git cloned it newly. Then I put back my saved docker-compose.yml file and tried again. This time with your docker image. But it produces the same error. I have no idea what to do right now.
docker-compose up -d; docker-compose logs -f
Creating network "powerdns-admin_pda_default" with driver "bridge"
Creating powerdns_admin ... done
Attaching to powerdns_admin
powerdns_admin | INFO  [alembic.runtime.migration] Context impl MySQLImpl.
powerdns_admin | INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
powerdns_admin | ERROR [root] Error: Can't locate revision identified by 'bf5e40f2dedc'

docker-compose.yml without dot-env file:
version: "3"

services:
  app:
    image: ngoduykhanh/powerdns-admin:latest
    container_name: powerdns_admin
    ports:
      - "9191:9191"
    logging:
      driver: json-file
      options:
        max-size: 5m
    networks:
      - pda_default
    environment:
      -<EMAIL_ADDRESS>      - GUINCORN_TIMEOUT=60
      - GUNICORN_WORKERS=2
      - GUNICORN_LOGLEVEL=DEBUG
    restart: unless-stopped

networks:
  pda_default:
    driver: bridge
    driver_opts:
      com.docker.network.bridge.name: pda0
    ipam:
      driver: default
      config:
        - subnet: <IP_ADDRESS>/24

Oh, I se this time it is a different error message...

I dived deeper into this. I have made a backup from all my pda tables, dropped the database and created it again. Then I started pda once. After stopping it again, I filled all the tables again with the back-uped content. So far that worked. After starting pda again, I can see the login window now. But neither local nor LDAP login works anymore:
name 'Setting' is not defined

I have no ide, what this error is telling me. I have really checked all the tables descriptions before re-inserting content. Only the user table has dropped the avatar field. I also have not been able to insert history records.
Can you please give me a hint? I really do not want to recreate all templates, users, ... again. That was so much work. :-(

Hi @croessner ,
Thanks for raising that issue. It was my mistake during code refactoring. Fixed it on master branch now. New docker image will be built in a few minutes

Thank you very much 😊 Now everything is working again.

Is this typo intended?
GUINCORN_TIMEOUT instead of GUNICORN_TIMEOUT?


Correct Json marshaling for labels of issues

Labels for issues should be marshalled to a list of strings instead of single (comma-seperated) string. This is according to https://docs.gitlab.com/ee/api/issues.html (22-11-2023)

Why was Description field from CreateMergeRequestOptions changed to *LabelOptions?

Thats a mistake... Thanks for spotting it, will change it in a bit!

Fixed in v0.95.1


Discussion: Should we allow user to make calls without being authenticated properly?

If the backend allows to do that then it is a problem in the backend.


Make sure ECMWF ascending

Detailed Description
it looks like in live the ECMWF lat n lon are not ascedning
Context

training data must be same as live inference data

Possible Implementation

check in training data
and re order if necessary

Below is training data, this is the same as live


First draft of ruby generator

Patch notes for May: https://developer.avalara.com/blog/2017/04/25/AvaTax-17-5-patch-notes


Automatically symlink when proxying unix domain sockets under /var/run

The proxy currently generates a warning when you attempt to proxy sockets whose immediate parent is /var/run, due to the issue with mount namespaces capturing network namespaces. Users are advised to make a symlink of the target socket in a subdirectory and supply that instead; this advice should be automated.

The idea here is that it avoids the obscure warning we currently issue.
Perhaps we should create a symlink for any domain socket, except /var/run/weave/weave.sock? That way we can just always mount /var/run/weave.

Doing a symlink for any domain socket sounds cleaner. But, in order for the volumes to get unmounted (in case they are /var/run), we need the symlink-creating container to exit. To do that we could either:

Special-case /var/run, mount it into the exec_remote container, and only do the symlink dance for sockets in /var/run.

Have the proxy launch another temporary container with the dirs mounted, and have that create the symlinks.

Parse the proxy flags locally, mounting the socket dirs into the exec_remote container, and create the symlinks from there.

Of those, 1, or 2 sound the cleanest, to me.

Favouring option 1, as it will run faster (less container creates/destroys), and be less code than launching containers from the proxy.

Have realised that option1 won't work because the proxy won't know what address to return for weave env, so we are stuck with option 2.


PerceptronTagger hangs

From today's demo at KDD 2017 - wether running
tagger = metapy.sequence.PerceptronTagger("perceptron-tagger/")
either inside Jupyter or via command-line python, the above line of code appears to hang - no error is output, but never completed. Others said that killing the kernel and restarting worked - but didn't work for me.
As an FYI, here's what Python I'm running on macOS Sierra 10.12.6:
python --version
Python 3.6.1 :: Anaconda custom (x86_64)
python --version
Python 2.7.13 :: Continuum Analytics, Inc.

Thanks for the report. I was just able to reproduce this; it looks like it is a deadlock contention for the python GIL to print loading progress output if metapy.log_to_stderr() was called first.
This has been fixed in meta-toolkit/metapy@23bd3c0 and should be available once the build jobs for v0.2.6 finish and I can upload the new library version to PyPI.

Thanks for the quick look and resolution.
On Wed, Aug 16, 2017 at 2:57 PM, Chase Geigle<EMAIL_ADDRESS>wrote:

Thanks for the report. I was just able to reproduce this; it looks like it
is a deadlock contention for the python GIL to print loading progress
output if metapy.log_to_stderr() was called first.
This has been fixed in meta-toolkit/metapy@23bd3c0
https://github.com/meta-toolkit/metapy/commit/23bd3c0 and should be
available once the build jobs for v0.2.6 finish and I can upload the new
library version to PyPI.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/meta-toolkit/meta/issues/188#issuecomment-322850684,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI8R-FTubhUIlfbv37sAIXOnjiIXmOm6ks5sYy2kgaJpZM4O5DVw
.

The new version has just finished deployment, so you should be able to grab the latest version with the fix with:
pip install --upgrade metapy

Just wanted to let you know that I've confirmed this is resolved as well.


Add CONTRIBUTING

Hey, I just made a Pull Request!
First iteration of the contributing guidelines.
Closes https://github.com/spotify/backstage/issues/224.

:heavy_check_mark: Checklist

[x] Relevant documentation updated

@OrkoHunter thanks for giving me the little nudge I needed 😄


DTLS session timeout

Leshan Version : M12
I have question on DTLS session timeout . Default timeout set is 24h which i can see in code but I did not see the usage of it .
SECURE_SESSION_TIMEOUT -> This parameter is there in Californium.properties file . I changed the value and tried testing it . Session did not expire after this timeout . Please tell me when the session information is removed from lwm2m server or there is no expire for this. What is the current behavior?
DTLS session full handshake is expected after 24h?

SECURE_SESSION_TIMEOUT in californium is only used by the experimental CoAPs over TCP.
There is a long discussion about adding this to californium for CoAPs over UDP.
See https://github.com/eclipse/californium/issues/617.
Currently there is no easy way to set the session lifetime, but now there is tools to do your own clean.
See on DTLSconnector:

startDropConnectionsForPrincipal
startTerminateConnectionsForPrincipal
startForEach

(@boaks  just in case you want to add something)

OK . Thank you for your inputs.
When Connection state is removed from server cache? Is it removed after receiving de-register request from device(peer)?

Connection is in a LRU cache and are removed when cache is full and new connection must be added. (the oldest one is removed)
(I'm not so sure but I also think Connection is removed when foreign peer send a "CLOSE_NOTIFY")

Connection is in a LRU cache and are removed when cache is full and new connection must be added. (the oldest one is removed) -> This behavior is same with M10 version of leshan?

AFIAK, yes.

What is the LRU cache size now?

If I remember well the default is something like 150_000.
You can change it via NetworkConfig and LeshanServerBuilder.setCoapConfig.
(The key is MAX_ACTIVE_PEERS)
(if fact the real parameter is in DtlsConnectorConfig but by default in Leshan both value are the same)

Ok . Thank you for information .


Installation: Clarify Python 3 on CentOS

CentOS 7 has Python 3.6 in the official repositories since some time.
This allows us to get an almost modern Python interpreter onto the
system without fiddling with PATH environment varible like SCL does.

Description
This PR just updates the installation instructions for CentOS. Since they have now Python 3.6 in the base repo, we can simply rely on that instead of adding another repo. While I'm not against more repos, SCL in particular can get a bit tricky because of their setup.
Related Issues

Motivation and Context
Make SCL optional
Tests
Since this is just a docs change, I didn't touch any tests. Of course I tried this locally an can confirm that the base repo ships python3.6 and that hyperglass works with that.

Hello,
The current CentOS installation docs reflect changes recommended by #31, #62, some Gitter/Telegram chats from CentOS users, as well as my own (later) tests with CentOS 7. Now, I'm not a frequent CentOS user as you can probably tell, so I'm not 100% certain which packages are required under which circumstances. I do want the docs to be easy and accurate, though.

Since they have now Python 3.6 in the base repo, we can simply rely on that instead of adding another repo.

Does this mean that there was a recent-ish change to the CentOS repositories, perhaps after the docs changes in #31/#62, which means we can update the docs? Just want to make sure I fully understand.
Thanks!
Matt

If I remember it correctly, back in the days when CentOS 7 was released, it had no python 3 version. Python 3.4 was available via EPEL. Later Python 3.6 was introduced (to EPEL I think, and later moved to base). However, the package python3 is available in the base repository (which is enabled by default and not a 3rd party one). This package currently brings Python 3.6.8. You can see the changelog here: https://centos.pkgs.org/7/centos-x86_64/python3-3.6.8-13.el7.x86_64.rpm.html
It's available since march 2019. It's just not installed by default and the /usr/bin/python symlink always points to python 2 on CentOS 7. That might confuse people.

I did some digging into the old centos 7 releases. their 7.5.1804 release did not contain python3 in the main repos: http://vault.centos.org/7.5.1804/cr/x86_64/Packages/
after that it got moved from epel to the base repo and is available since 7.6.1810: http://vault.centos.org/7.6.1810/cr/x86_64/Packages/

closed and reopened to retrigger travis


decouple sequence_equal from observable

Decoupled sequence_equal from observable.
Please review.
FYI:
Here I ported std::negation from C++17 and used it for overload selection. If that is not OK and should be done in a different way, let me know.
Thank you,
Grigoriy.

Negation is perfect, thanks!


audit container script file ownership

We have a pattern of doing stuff like
chown -R $USER:root $SCRIPT_DIR
chmod -R ug+rwX $SCRIPT_DIR
chmod ug+x ${ARTIFACTS_DIR}/opt/jboss/container/(something)

Consequently, many of the container executable scripts are owned by and writable by the running user, but that is not actually necessary for operation: furthermore, it isn't desirable because it increases an attack surface area.

All of /opt/jboss/container is owned by the running user and probably shouldn't be

https://issues.redhat.com/browse/OPENJDK-2814


TSM-based features for EPIC-100

Hello, thanks for your hard work! It really provides great convenience for reimplementation.
Meanwhile, I would like to know if the TSM-based features for EPIC-100 will be available for download as those of Epic-Kitchens do? Thanks a lot.

We did not use TSM features for our experiments. But you can extract them by following the feature extraction procedure in RU-LSTM repo and instead of using bninception backbone for TSN use the TSM backbone provided by the EPIC-100 here.


Lacking Documentation

Does this setup look right to you?
VaultEndpoint vaultEndpoint = VaultEndpoint.create("my-vault.my-domain.com", 8200);

RestTemplate restTemplate = VaultClients.createRestTemplate(vaultEndpoint, new SimpleClientHttpRequestFactory());
ClientAuthentication clientAuthentication = new AwsEc2Authentication(restTemplate);

VaultTemplate vaultTemplate = new VaultTemplate(vaultEndpoint, clientAuthentication);

VaultResponse writeResponse = vaultTemplate.write("secret/foo/bar", ImmutableMap.of("foo-secret-key", "bar-secret"));

VaultResponseSupport<Map> readResponse = vaultTemplate.read("secret/foo/bar", Map.class);

This kind of questions rather belongs to StackOverflow. Your setup looks correct. In doubt check out AbstractVaultConfiguration.

Thank you 👍


race condition when writing error data to results panel

Error data is processed in the background. Multiple threads may attempt to write the results panel at the same time. There is no synchronization mechanism to prevent race conditions. In fact, they happen quite often and cause error navigation via F4 to function erratically.

Fixed by https://github.com/guillermooo/dart-sublime-bundle/pull/481


Expired token exception after upgrade to 11.2.0.jre11

Versions
Driver version: JDBC driver version: 11.2.0.jre11
(com.microsoft.sqlserver:mssql-jdbc:11.2.0.jre11)
SQL Server version: Microsoft SQL Azure (RTM) - 12.0.2000.8
Aug 10 2022 15:14:09
Copyright (C) 2022 Microsoft Corporation
Client Operating System: Linux on Azure App Service, single instance
Docker base image: eclipse-temurin:11-jre-alpine
JAVA/JVM version: Java 11
Java Spring: 2.7.2
JDBC connection string: jdbc:sqlserver://<db-server-name>.database.windows.net:1433;database=<db-name>;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=30;Authentication=ActiveDirectoryMSI;
Problem description
Since we upgraded from 9.4.1.jre11 to 11.2.0.jre11 some days ago, we get failures periodically.
We updated 4 Microservices and all of them show the new bevhaviour: They are mostly working normally, but after some time (sometimes around a day), the one or more connection from the pool fail for around an hour (which generates around 80 exceptions in that time).
For example, we had the behaviour twice for the last 3 days (only a single service shown):

Exception

org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms.
at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:83)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:330)
...
Caused by: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms.
at com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:696)
at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:197)
at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:162)
at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:128)
at org.springframework.jdbc.datasource.DataSourceUtils.fetchConnection(DataSourceUtils.java:159)
at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:117)
at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:80)
... 119 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user '<token-identified principal>'. Token is expired. ClientConnectionId:<uuid>
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:265)
at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:300)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:133)
...

We think the JDBC token renewal process was changed with the newer version, but we don't know what exactly causes the exception. We read somewhere that Azure does a health check on active connections every now and then (10 hours?) but we do not see why this should now fail when it was working before.

Hi @akleemans,
This seems to be very similar to another ongoing issue of ours, also with Hikari. Can you send us the configuration used in Hikari? I think 'maximum-pool-size' is what we're most concerned with now, but all the information you can send will be helpful. Additionally, is your application taking advantage of Idle Connection Resiliency? Finally, can you please try running with these custom jars, and sending us the resulting logs. They have custom logging that should provide more insight around token expiry. If this is a token issue, this may help as well.
Custom_Logging_Jars.zip

Some background info on tokens within the driver. The driver doesn't cache the token, so we do not renew it. Every time a login is performed we fetch a fresh token through MSAL. If a token expiry does occur it's likely a configuration issue.
What's the the lifetime of a connection within the connection pool? By default tokens have a lifetime of 1 hour, so if the lifetime of a connection within the pool is > 1 hour then I could see an expiry happening.

Hi @Jeffery-Wasty
Thanks for the quick reply!
We use the provided standard values for Hikari. We use spring-data-jpa:2.7.2. with spring-jdbc.
We checked and maximum-pool-size is at default of 10. About the Idle Connection Resiliency, we don't configure it explicitly so I guess the default values are applied.
Thanks also for the Jars, we're currently checking what the easiest way is to recreate the issue on our environment with the custom jars included.

Hi @akleemans,
Reading a bit more into this, this seems to be a common problem with HikariCP. Recommended advice is checking the number of active connections at point of failure, to confirm whether the connections are being returned to the pool correctly. If not, this will need to be implemented. As well, if you're not using version 5.0.0, it is recommended you do, as that resolved an error where connections were not correctly being returned to the pool. Finally, as a temporary fix, you can simply increase the size of the pool, granting more connections. This is not a fix of course, but should reduce the number of exceptions while work is being done resolving the issue.

Hi @akleemans,
Just wanted to check in and see whether the issue persists, and whether you have tried any of the solutions described above. If there is no further reply, we'll mark the issue as closed. Thanks!


Test Request: Kong Gateway EE version <IP_ADDRESS>-rc1

What component needs testing with KIC?
Kong Gateway EE
Container image
kong/kong-gateway-dev:<IP_ADDRESS>-rc1
Additional information
No response

@randmonkey Should we close this issue given the tests haven't passed?


Server for MicroPython

Is it possible to have a simple OSC send/receive server running on MicroPython?
Maybe a simple example.
thanks.

Yes, it is possible, but you would need to employ either multi-threading (available on esp32 or stm32) or asyncio for that. Sorry, I don't have an exact example for that, but there is an asyncio server examples in the examples folder, which you could look at and use as a starting point.

thanks. its probably easier to start from scratch than use that example as it uses many things not available in MicroPython.

There's now an updated server example using uasyncio (v3) (27c7204, 8e9c359). I added all needed extra libraries to the examples folder, but its easy to adapt the examples so that they don't need these extra modules. The uosc package should now only need standard micropython modules.


GPU implementation of the Mean Squared Error loss function

This PR, along with the one in the etl-gpu-blas repository, adds a GPU implementation for the Mean Squared Error function.
I am unsure about some of the parameters used, I will soon add some comments on this PR to clarify what I mean.
This PR also contains ETL code, not sure if this is the best way or if I should open a separate one on the ETL repository.

Thanks for the feedback. Now I understand the scaling factor, will fix it.

You will have to update etl again to master for this to work. I won't be able to merge before.

I did a git checkout upstream/master on ETL and then re-committed the etl submodule. Not sure if that's right though.

I reopened it in another PR and was able to squash and merge it. I have no idea why I could not merge this one.


Issues with videos from v.reddit.com

Some videos from v.reddit.com have a black thumbnail and load to a black screen with audio.  Seeking back to the beginning of the video fixes the issue for the duration of the video.
I’m experiencing the issue on an iPad Mini with 2 column view. I was unable to reproduce on my iPhone 11 Pro.  Tried clearing cache and restarting Slide.
This is one video with the issue; I’ve noticed it on several others. https://reddit.com/r/aviation/comments/dwkse7/british_airways_a380_enters_hong_kong/

I actually believe this is a Reddit issue, unfortunately. Looking at the JSON and trying to view the preview image results in a broken link

I should’ve posted this earlier - sorry for the delay!
Shortly after submitting the issue I rebooted my iPad and the problem went away. Not sure if the issue was related to Slide or iOS, but all is good now.

Thanks for the update! If it comes back, please post again


Buttons overflow

When exceeding the amount of buttons after the window width, buttons will overflow onto a new row in horizontal mode (see screenshot):

Buttons that exceed the window height in vertical mode, even disappear (see screenshot):

Possible solutions:

Increase ToolBar width/height.
Inherit from ScrollView instead of View to make the ToolBar scrollable.

I would vote for adding another row/column of buttons when they don't fit by adjusting the width/height

So I thought this would be easy, but it isn't for some reason :disappointed:
The following code adds another row on the toolbar for position top and bottom:
  display: flex;
  flex-direction: row;
  flex-wrap: wrap;
  justify-content: flex-start;
  align-items: stretch;
  align-content: flex-start;

When changing to left and right position however it does something weird. In above code I changed the flex-direction to column, but still the toolbar won't stretch to allow buttons to overflow to the right (screenshot 1). Adding width: 100%; to the parent atom-panel allows the buttons to overflow but with more width then is necessary (screenshot 2). The extra width seems to come from the minimum size is needed for all buttons to fit when minimizing the window. Why?...

no width
width: 100%;

@simurai I was hoping you could chip in :blush:

Online demo if anyone wants to help: http://output.jsbin.com/vimihurelo/1

Hmmm.. yeah, somehow the width of the flexbox stays like there would be no wrapping. Probably a bug.. maybe same as this inline flexbox bug: https://code.google.com/p/chromium/issues/detail?id=247963
Maybe in the meantime it could wrap top/bottom, but overflow-scroll when left/right? Like https://github.com/jerone/tool-bar/pull/1

@jerone You live in Haarlem? Damn.. I lived there a few years. Super nice town.

@simurai commented on 26 mei 2015 07:21 CEST:

Hmmm.. yeah, somehow the width of the flexbox stays like there would be no wrapping. Probably a bug.. maybe same as this inline flexbox bug: https://code.google.com/p/chromium/issues/detail?id=247963

Looks like the same bug. Weird that both Chrome and Firefox do it 'wrong', while IE expands the container correctly. Anyways, subscribing to that issue...

Maybe in the meantime it could wrap top/bottom, but overflow-scroll when left/right? Like https://github.com/jerone/tool-bar/pull/1

Making left/right scrollable was my fallback too, and as it stands will be a good solution. I'll have a look at your PR tonight. Thank you very much for checking.

@jerone You live in Haarlem? Damn.. I lived there a few years. Super nice town.

Yeah, born and raised, in North, near the ice skating rink. "Waarom heb je in Haarlem gewoond? Vanwege werk?".

@jerone Yes, was working in Amsterdam for a few years. But I liked Haarlem more. Less tourists and more relaxed. :smile:

@simurai Same situation. Way relaxer, and closer to the beach :P


Reduce the amount of burn damage from touching lights

About the PR
Lights now deal 60% less burn damage than they did previously. Exterior lights have been affected by only 20% because a brighter light is hotter.

Exterior lights now deal 4 damage (from 5)
Standard lights now deal 2 damage (from 5)
LED lights now deal 1 damage (from 2.5)

I also gave exterior lights their own suffix while I was in the file because them sharing a suffix with blue lights was annoying.
Why / Balance
5 damage seems like a bit much for misclicking or forgetting to wear insuls. I also want to kill lightbulb cauterization even more than I already aimed to with https://github.com/space-wizards/space-station-14/pull/27726. It just makes no sense.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

tweak: Active lights now deal significantly less burn damage when touched.

Thank you. It was extremely strange seeing people touch light-bulbs mid fight to stop bleeding.

I think I'd rather increase the amount of burn damage needed to cauterize than decreasing thhe damage to such a pitiful amount.


:

I simply cannot install dependencies using pip.
Also tried but now I don't know what to do:
ImportError: The 'mitsuba' native modules could not be imported. you're likely to use Mitsuba within a python bi...

I am using Blender 3.5 on Windows 10

There has been a breaking change in blender 3.5 with Windows for this addon regarding importing mitsuba, which i haven't tracked down yet. Please se my answer here. I will close this issue as it is a duplicate of #61

okay , well thanks but how can I lunch blender using this --python-use-system-env flag? I'm using win 10

Find the path to your blender executable, open a windows command prompt, and run <path_to_blender.exe> --python-use-system-env-flag>


TaskCanceledException while WaitForSidecarAsync

Expected Behavior
With the release of SDK 1.7, when adding a secret store, my component should wait for the sidecar to be able to accept request from my component, and then use the actual api to retrieve the secret store.
I'm thinking also that the root cause can be a timing problem, in this case how can I set the maximum time to wait for the sidecar?
Actual Behavior
I'm registering an exception of type TaskCanceledException in the WaitForSidecarAsync method of dapr sdk

unfortunately it is not always occurring, but when happens only solution I found is to restart the kubernetes deployment
Steps to Reproduce the Problem
With a .Net microservice load secret store from an Azure key vault component
Release Note
RELEASE NOTE:
Thanks,
Simone

I'm seeing in the code that SidecarWaitTimeout exists and is passed imperatively. Since I have many services can I pass this parameter in a declarative way   (i.e. annotation, configmap, whatever)?
Thanks

@Banchio - Thanks for opening this issue!
You have to add the timeout by adding it to the method call. Choose any of the calls with the TimeSpan sidecarWaitTimeout.
https://github.com/dapr/dotnet-sdk/blob/master/src/Dapr.Extensions.Configuration/DaprSecretStoreConfigurationExtensions.cs#L66


puppet-jira -- Upgrade howto & addons management questions

Hello,
I'm a new user of this Puppet-JIRA module.
Making a quick overview of this module, find below my question about it :

How do you proceed with all addons contained in JIRA.
How do you proceed for any upgrade from one existing JIRA instance not managed by Puppet to a new one managed by puppet.
How do you manage further Jira upgrade.

Thanks by advance for any feedback on above point !
Fred

This issue is a bit old, and I'm not sure if the questions here are something that directly relate to this Puppet module.
But in summary:

This module doesn't concern itself with JIRA addons, they're out-of-scope.
Taking over "old" installations with Puppet is generally something you need to plan on a case-by-case basis.
Once you have JIRA managed by Puppet, upgrades are pretty simple.


Error while creating release definition when creating new terraform project

Creating a new Terraform project and installing these two required extensions
Replace Tokens - License Terms
Terraform - License Terms
caused this error
Error while creating release definition: Tasks with versions 'Replace tokens in terraform file:3., Terraform : init:0., Terraform : plan:0., Terraform : apply -auto-approve:0.' are not valid for deploy job 'Agent job' in stage Dev.
The project was created however but this is shown in the diagnostics

ac

actually this is only an issue when you dont install the plugins prior to clicking create project. Creating a second project after the plugins were already installed completed successfully


pre load installer

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run go fmt ./... to check that my code is properly formatted
[ ] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #455 (9e460c7) into main (631a94f) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #455   +/-   ##
=======================================
  Coverage   31.61%   31.61%
=======================================
  Files          31       31
  Lines        3169     3169
=======================================
  Hits         1002     1002
  Misses       2072     2072
  Partials       95       95

Impacted Files
Coverage Δ

pkg/routes/imagesets.go
38.23% <100.00%> (ø)

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 631a94f...9e460c7. Read the comment docs.

@biancarosa validating it, also think is from image! I'll let you know soon


Updated name

Web API Controller does not exist.

Thank you for your input @K232  and @ktoliver. This may be a difference between VS Mac and VS 2019. The steps were based on VS Mac and the original reference to the Web API Controller Class is correct in this environment. There may be a broader work item to ensure the steps can be followed more easily in both VS Mac and VS 2019.

Thanks for the feedback @K232. I've adapted and combined it with other feedback into a single commit.

We'll close the PR. Thanks!


POST /2/tweets requires the media ID to be a String type instead of Long Type

upload media returns media ID as Long
but using it with createTweet will not work , as the API from Twitter requires that the media ID array to be of type String

thanks.


Update external docker images

This commit updates hubble-ui envoy proxy to v1.20.2 and clustermesh's etcd to v3.5.2

/test

All tests were successful. Unit test failed because of documentation. This is the diff that was applied:
diff --git a/Documentation/helm-values.rst b/Documentation/helm-values.rst
index 9bae795111..a18048766f 100644
--- a/Documentation/helm-values.rst
+++ b/Documentation/helm-values.rst
@@ -152,7 +152,7 @@
    * - clustermesh.apiserver.etcd.image
      - Clustermesh API server etcd image.
      - object
-     - ``{"override":null,"pullPolicy":"Always","repository":"quay.io/coreos/etcd","tag":"v3.4.13"}``
+     - ``{"override":null,"pullPolicy":"Always","repository":"quay.io/coreos/etcd","tag":"v3.5.2@sha256:70fe70b6cdaea99fa9e99d3a16483954eb084c3b32a2475abea4e709a793636c"}``
    * - clustermesh.apiserver.extraEnv
      - Additional clustermesh-apiserver environment variables.
      - list
@@ -932,7 +932,7 @@
    * - hubble.ui.proxy.image
      - Hubble-ui ingress proxy image.
      - object
-     - ``{"override":null,"pullPolicy":"Always","repository":"docker.io/envoyproxy/envoy","tag":"v1.18.4@sha256:e5c2bb2870d0e59ce917a5100311813b4ede96ce4eb0c6bfa879e3fbe3e83935"}``
+     - ``{"override":null,"pullPolicy":"Always","repository":"docker.io/envoyproxy/envoy","tag":"v1.20.2@sha256:eb7d88d5186648049f0a80062120bd45e7557bdff3f6a30e1fc92cbb50916868"}``
    * - hubble.ui.proxy.resources
      - Resource requests and limits for the 'proxy' container of the 'hubble-ui' deployment.
      - object


Releasing version 2.4.2

Version 2.4.2 Contains the following fixes:

https://github.com/shanalikhan/code-settings-sync/issues/168 : Covering All the Files and Folders Inside User Directory
https://github.com/shanalikhan/code-settings-sync/issues/167 : Changing Extension Name to Settings Sync
https://github.com/shanalikhan/code-settings-sync/issues/161 : Cannot Upload Settings First Time
https://github.com/shanalikhan/code-settings-sync/issues/144 : Share Settings Needs to Confirm Reset GIST and than Upload Settings
https://github.com/shanalikhan/code-settings-sync/issues/111 : Store non-confidential settings in the standard way
https://github.com/shanalikhan/code-settings-sync/issues/180 : Supporting Anonymous Gists

Released for all users Version 2.4.2
https://github.com/shanalikhan/code-settings-sync/releases/tag/v2.4.2


MediaElement.js - Media title show on screen

I'm having a problem with MediaElement.js. I want to have the channel name displayed on the screen when any item is clicked on the channel list. Is this possible ?

Yes you can, how ever I think it needs some TLC. But you can create a plugin for ME.js and read the media title and display it on a screen....

$("#channel-2").remove(); var item = $("

" + channel-title + "

"); $('.mejs__layers').append(item);
That's how I provided the simplest solution.
It automatically disappears when the channel starts playing :)

I'm closing the issue because the problem seems to be solved. Thanks @sweetngx for the solution.


C++ demo memory release problem

For bugs or installation issues, please provide the following information.
The more information you provide, the more likely people will be able to help you.
Environment info
Operating System: windows
Compiler:VS2015
MXNet version:0.9.5
Steps to reproduce
or if you are running standard examples, please provide the commands you have run that lead to the error.

run image-classification-predict.cc
2.MXPredFree(pred_hnd) don't release memory in GPU or CPU mode

same problem, exe can't exit normally and cpu gpu memory didn't release.
Operating System: Windows 7 x64
Compiler: VS2015
MXNET version: 0.10.0 and 0.11.0

@lx75249

@piiswrong  This is the raw API demo.. not the demo in c++ package.

@lx75249  MXNotifyShutdown() can't resolve it yet

I create a std::thread to run the demo, the memory release a big part, but left a small part before exit exe but thread end.
I try the release function MXNotifyShutdown(), MXPredFree(pred_hnd) both, absolutely didn't work. I believe it was a bug.
code as follow:
int f()
{
std::string test_file = "G:/标识牌-9~17.jpg";
//test_file = std::string(argv[1]);

// Models path for your model, you have to modify it
std::string json_file = "VGG_VOC0712Plus_SSD_512x_16w.json";
std::string param_file = "VGG_VOC0712Plus_SSD_512x_16w.params";
std::string synset_file = "model/Inception/synset.txt";
std::string nd_file = "model/Inception/mean_224.nd";

BufferFile json_data(json_file);
BufferFile param_data(param_file);
//system("pause");
// Parameters
int dev_type = 2;  // 1: cpu, 2: gpu
int dev_id = 0;  // arbitrary.
mx_uint num_input_nodes = 1;  // 1 for feedforward
const char* input_key[1] = { "data" };
const char** input_keys = input_key;

// Image size and channels
int width = 512;
int height = 512;
int channels = 3;

const mx_uint input_shape_indptr[2] = { 0, 4 };
const mx_uint input_shape_data[4] = { 1,
	static_cast<mx_uint>(channels),
	static_cast<mx_uint>(height),
	static_cast<mx_uint>(width) };
PredictorHandle pred_hnd = 0;

if (json_data.GetLength() == 0 ||
	param_data.GetLength() == 0) {
	return -1;
}

// Create Predictor
MXPredCreate((const char*)json_data.GetBuffer(),
	(const char*)param_data.GetBuffer(),
	static_cast<size_t>(param_data.GetLength()),
	dev_type,
	dev_id,
	num_input_nodes,
	input_keys,
	input_shape_indptr,
	input_shape_data,
	&pred_hnd);
assert(pred_hnd);

int image_size = width * height * channels;

// Read Mean Data
const mx_float* nd_data = NULL;
NDListHandle nd_hnd = 0;
BufferFile nd_buf(nd_file);

if (nd_buf.GetLength() > 0) {
	mx_uint nd_index = 0;
	mx_uint nd_len;
	const mx_uint* nd_shape = 0;
	const char* nd_key = 0;
	mx_uint nd_ndim = 0;

	MXNDListCreate((const char*)nd_buf.GetBuffer(),
		nd_buf.GetLength(),
		&nd_hnd, &nd_len);

	MXNDListGet(nd_hnd, nd_index, &nd_key, &nd_data, &nd_shape, &nd_ndim);
}

// Read Image Data
std::vector<mx_float> image_data = std::vector<mx_float>(image_size);

GetImageFile(test_file, image_data.data(),
	channels, cv::Size(width, height), nd_data);

// Set Input Image
MXPredSetInput(pred_hnd, "data", image_data.data(), image_size);

// Do Predict Forward
MXPredForward(pred_hnd);

mx_uint output_index = 0;

mx_uint *shape = 0;
mx_uint shape_len;

// Get Output Result
MXPredGetOutputShape(pred_hnd, output_index, &shape, &shape_len);

size_t size = 1;
for (mx_uint i = 0; i < shape_len; ++i) size *= shape[i];

std::vector<float> data(size);

MXPredGetOutput(pred_hnd, output_index, &(data[0]), size);

// Release NDList
if (nd_hnd)
	MXNDListFree(nd_hnd);

// Release Predictor
MXPredFree(pred_hnd);
MXNotifyShutdown();

// Synset path for your model, you have to modify it
std::vector<std::string> synset = LoadSynset(synset_file);

// Print Output Data
//PrintOutputResult(data, synset);
return 0;

}
#include
int main(int argc, char* argv[]) {
std::thread t1(f);
t1.detach();
//f();
}

Win10 is ok.

what interface you call？@kimivital

I run the example file(image-classification-predict.cc) with other model.

I run it on win10, memory leak in GPU or CPU mode.

@apache/mxnet-committers: This issue has been inactive for the past 90 days. It has no label and needs triage.
For general "how-to" questions, our user forum (and Chinese version) is a good place to get help.

@junxigauss  is this still an issue on mxnet v1.2?

I have the same issue on Arch Linux in master branch

@junxigauss - It would be very helpful for all users if you can do a PR for the code change?  Or, Can you please provide more details on the fix you made?

@junxigauss Can you elaborate what have you done to solve it?

@mxnet-label-bot add [Pending Requester Info]

@junxigauss Requesting an explanation on the solution, it would help all users , if they run across a similar issue.

@junxigauss : Would you be able to share the solution? As mentioned above, this could be very useful for others as well.

This issue is not related to C++ Front End API. Removing the C++ Label.

@mxnet-label-bot remove [C++]

@mxnet-label-bot add [C API]

This doesn't seem to an issue anymore. I would recommend closing this issue.
@lanking520

@junxigauss Please feel free to reopen this issue if problem persist. Close it for now


CLI export command

Adds a basic documentation for the CLI export command.

Thanks for adding some docs
looks good
merging


Improve use of Enum as widget choices and fix types

There are two modules using Enum for choices. I have enhanced both and resolved the type warnings along the way. The most significant changes include:
class RescaleType(Enum):
    NEAREST = (0, "Nearest")
    LINEAR = (1, "Linear")
    BILINEAR = (2, "Bilinear")

    def __init__(self, int_val, str_val):
        self.int_val = int_val
        self.str_val = str_val

    @classmethod
    def to_choices(cls):
        return [(mode.str_val, mode.int_val) for mode in cls]

class RescaleModes(Enum):
    FROM_FACTOR = "From factor"
    TO_LAYER_VOXEL_SIZE = "To layer voxel size"
    TO_LAYER_SHAPE = "To layer shape"
    TO_MODEL_VOXEL_SIZE = "To model voxel size"
    TO_VOXEL_SIZE = "To voxel size"
    SET_SHAPE = "To shape"
    SET_VOXEL_SIZE = "Set voxel size"

    @classmethod
    def to_choices(cls):
        return [(mode.value, mode) for mode in RescaleModes]

This approach provides an elegant solution for managing lists of string choices and their corresponding values.

This PR originally attempts to fix the type warnings from #249


Incorrect averageBytesPerRecord Causes OOM

Historically I see an issue that has been closed at: https://github.com/apache/incubator-hudi/issues/270.
I am not sure what the fix was for the above issue.
I have hit the issue today. Lets say there are about thousands of records but none get written (which may happen in my case as we want to selectively write records. And I am not sure if this is supposed to happen in the case when this issue was hit). This results total records written to 0 leading to avgSize going to Infinity.
scala> val l = Math.ceil( 1.0 / 0 )
l: Double = Infinity

scala> val l = Math.ceil( 1.0 / 0 ).toLong
l: Long =<PHONE_NUMBER>854775807

This causes OOM.
    protected long averageBytesPerRecord() {
      long avgSize = 0L;
      HoodieTimeline commitTimeline = metaClient.getActiveTimeline().getCommitTimeline()
          .filterCompletedInstants();
      try {
        if (!commitTimeline.empty()) {
          HoodieInstant latestCommitTime = commitTimeline.lastInstant().get();
          HoodieCommitMetadata commitMetadata = HoodieCommitMetadata
              .fromBytes(commitTimeline.getInstantDetails(latestCommitTime).get(), HoodieCommitMetadata.class);
          avgSize = (long) Math.ceil(
              (1.0 * commitMetadata.fetchTotalBytesWritten()) / commitMetadata
                  .fetchTotalRecordsWritten());
        }
      } catch (Throwable t) {
        // make this fail safe.
        logger.error("Error trying to compute average bytes/record ", t);
      }
      return avgSize <= 0L ? config.getCopyOnWriteRecordSizeEstimate() : avgSize;
    }

I have now managed to work around it by editing the last line in the code as below.
return (avgSize <= 0L  | avgSize >= Integer.MAX_VALUE) ? config.getCopyOnWriteRecordSizeEstimate() : avgSize;

But I believe someone more knowledgeable about this should take a look at it.

Closing in favor of JIRA HUDI-164


[1.7.10] Research page conflicts!!! (emergency)

There is a problem with the pages of the Magic Guidebook. Because the expanded modules cause them to overlap, but I don't want to delete the expanded modules. What should I do to prevent the research from overlapping? I am from Taiwan. My English is not good. Sorry.

https://www.curseforge.com/minecraft/mc-mods/notenoughthaumcrafttabs
Use this.


Fix colormap for facet grid plots

Fixes #592
Added test to check that all subplots in facet grid have same data range and colormap.
This fixes two issues present in the existing code:

colormap was being selected for each subplot
range was being selected for each subplot and colorbar was the result of only the last subplot

Some sample code:
data = (np.random.random(size=(20, 25, 12)) + np.linspace(-3, 3, 12)) # range is ~ -3 to 4
da = xray.DataArray(data, dims=['x', 'y', 'time'], name='data')
fg = da.plot.pcolormesh(col='time', col_wrap=4)

previously yielded this plot:

and now yields this plot:

@shoyer - This seems to do the trick.  You may want to play around it to make sure everything looks correct.

@shoyer - This seems to do the trick.  You may want to play around with it to make sure everything looks correct.


Update the speeddating related documentation

Tim Pope's speeddating plugin has replaced "decrement" with "increment", which is now waiting for an argument.
see: https://github.com/tpope/vim-speeddating/blob/fe98cfa/plugin/speeddating.vim#L43-L44

Thanks for the fix :)


fix: GRPCAction with sync to async variable conflict

No unit test was failing before ? Can we add one ?


Preserve selection when changing collections

Attempt to resolve #193
There will be a little refactor needed if #249 is merged first.
I'm not sure about one or two lines (you'll notice which ones, I guess ;p) but I couldn't find any bugs while testing it on a small example app.
This PR introduces a little change to the way selections are handled, so feel free to point out anything you think is not clear!

@mpiechocki indeed I merged #249 first, I hadn't seen this one, my bad :) Could you check to fix the remaining conflict? You'll probably be faster than me.
Cheers !

After a quick check, this should do the work, but please click through it before merging - It's been almost 3 months and I'm not 100% sure why this confilt happened :/

@mpiechocki thank you so much! Taking a look now :)

Ok the single image selection was broken but it's an easy fix :) The selection preservation across folders is one of the big awaited features so thank you so much for tackling this 🍾 !!!!

I'm glad I could help ;) happy new year! :)


Spread operator with minimal amount of work

Spread operator assigns all properties from source object to the destination.
Is there a syntax to assign only relevant properties according to the type ?
Sample:
type B = { x:number; y: number; }

const a = {x:1,y:2,z:3};

const  b: B = {...a}; // b.z is also copied

// Ask to copy only 'B' properties
const b2: B = B{...a};
// Translates to
const b2 = { x:a.x, y:a.y }; // b.z is undefined

No, we don't do type-based emit. See the design goals. You'll have to define a pick function.
export function pick<T, K extends keyof T>(obj: T, keys: ReadonlyArray<K>): Pick<T, K> {
    const out: Pick<T, K> = {} as any;
    for (const key of keys) {
        out[key] = obj[key];
    }
    return out;
}

@andy-ms I can try with mapped types. The question was about language feature. Thanks.


sendResources sending resources from random cities

Bug explanation
I had placed a sendResources process to send crystal from 2 cities (slots 2 and 7 respectively) into one (slot 6), the 2 origin cities being to the next island over. I left it overnight and in the morning I found my ships transporting crystal from a completely different town from very far away (city slot 1). After further investigating, I found out that not only ikabot had transported from this far-away town, but I found out that it had also transported from slots 5, 9 and 7 during the night. Transports from slot 2 had stopped right after the first transports from when I started the process. I had also set ships to manually send resources from slot 2 just before starting the process to slightly speed up the transportation.
Also, before this the sendResources process had frozen somehow. Resources were not moving for an hour while ships were standing in the harbor. Ikabot menu showed the process still active. Ended the process and restarted it, then the above happened lol.
Note: I had also placed a sellResources process right before the sendResources process, in case they interfere with each other in some way.
Note: This doesn't occur often or regularly. I also haven't worked on the resource transportation function(s) nor helpers in any way.
Operating System
Windows
Ikabot installation
I built Ikabot from sources
Ikabot version
Latest
Python version
Python 3.11

I suspect that this issue happens when two processes have calculated the arrival time of the same ships and one process "snatches" them off the other process. But since the other process doesn't actually end due to this, maybe it gets an invalid waiting time for ships?

After further analyzing the issue, I have discovered that latency issues raises the probability of occurance. I checked the planRoutes send function through and noticed how the town selection happened in the beginning of the script while the actual send code was in the end, causing potential latency between the two requests.
Those who are encountering the issue often, here is a potential fix. But since the issue does not occur often on good connections, it's hard to test whether it works or not. So anyone who has this issue persistently, try this out and post here whether it works so it can be made into a PR.

After a long while, it seems that this rarely occuring bug can be fixed using the above solution. But it seems to only happen when the network connection is extremely slow or if there's a lot of packetloss.
Nevertheless, this can be closed. But in case this problem reoccurs in the future, the above solution can be pushed into the main project as it has been confirmed to work.


Is it possible to remove the separator when generating the file name?

Hi.
In my case, the test goes in two stages - the first collection of actual snapshots of pages. The second is to compare them with pages from the test environment.
The problem is that cypress.json has a parameter to rerun the test if
"retries" fails: {
    "runMode": 2}

In my case, during the first stage of testing, the files are named filename # 0.png, but problems are observed in the second stage. If there are differences, then cypress restarts the test and the file name becomes filename # 1.png and for the plugin it becomes the reference thus the test is considered successful, although it is not.

Should be fixed by #169