What is the minimux CUDA Version Support?

My GPU is GeForce GTX 760 and the highest CUDA support version is 11.4
the readme fille metion the lowest GPU should be RTX 1060, but I don't know what it is, I had search from internet but nothing
When i run with GPU Conversion(in any METHOD).it report that. Seems is because my GPU not support.
`Last Error Received:
Process: Ensemble Mode
If this error persists, please contact the developers with the error details.
Raw Error Details:
RuntimeError: "cuFFT error: CUFFT_INVALID_DEVICE"
Traceback Error: "
File "/home/fkt/Projects/ultimatevocalremovergui-master/UVR.py", line 4716, in process_start
seperator.seperate()
File "/home/fkt/Projects/ultimatevocalremovergui-master/separate.py", line 287, in seperate
source = self.demix_base(mix, is_ckpt=self.is_mdx_ckpt)[0]
File "/home/fkt/Projects/ultimatevocalremovergui-master/separate.py", line 366, in demix_base
tar_waves = self.run_model(mix_wave, is_ckpt=is_ckpt, is_match_mix=is_match_mix)
File "/home/fkt/Projects/ultimatevocalremovergui-master/separate.py", line 380, in run_model
spek = self.stft(mix.to(self.device))*self.adjust
File "/home/fkt/Projects/ultimatevocalremovergui-master/separate.py", line 395, in stft
x = torch.stft(x, n_fft=self.n_fft, hop_length=self.hop, window=self.window, center=True,return_complex=True)
File "/home/fkt/Projects/ultimatevocalremovergui-master/lib64/python3.9/site-packages/torch/functional.py", line 632, in stft
return _VF.stft(input, n_fft, hop_length, win_length, window,  # type: ignore[attr-defined]
"
Error Time Stamp [2024-03-24 22:25:15]
Full Application Settings:
vr_model: UVR-DeNoise
aggression_setting: 10
window_size: 320
batch_size: Default
crop_size: 256
is_tta: False
is_output_image: False
is_post_process: False
is_high_end_process: False
post_process_threshold: 0.2
vr_voc_inst_secondary_model: No Model Selected
vr_other_secondary_model: No Model Selected
vr_bass_secondary_model: No Model Selected
vr_drums_secondary_model: No Model Selected
vr_is_secondary_model_activate: False
vr_voc_inst_secondary_model_scale: 0.9
vr_other_secondary_model_scale: 0.7
vr_bass_secondary_model_scale: 0.5
vr_drums_secondary_model_scale: 0.5
demucs_model: v3 | UVR_Model_1
segment: Default
overlap: 0.25
shifts: 2
chunks_demucs: Auto
margin_demucs: 44100
is_chunk_demucs: False
is_chunk_mdxnet: False
is_primary_stem_only_Demucs: False
is_secondary_stem_only_Demucs: False
is_split_mode: True
is_demucs_combine_stems: True
demucs_voc_inst_secondary_model: No Model Selected
demucs_other_secondary_model: No Model Selected
demucs_bass_secondary_model: No Model Selected
demucs_drums_secondary_model: No Model Selected
demucs_is_secondary_model_activate: False
demucs_voc_inst_secondary_model_scale: 0.9
demucs_other_secondary_model_scale: 0.7
demucs_bass_secondary_model_scale: 0.5
demucs_drums_secondary_model_scale: 0.5
demucs_pre_proc_model: No Model Selected
is_demucs_pre_proc_model_activate: False
is_demucs_pre_proc_model_inst_mix: False
mdx_net_model: Choose Model
chunks: Auto
margin: 44100
compensate: Auto
is_denoise: False
is_invert_spec: False
is_mixer_mode: False
mdx_batch_size: Default
mdx_voc_inst_secondary_model: No Model Selected
mdx_other_secondary_model: No Model Selected
mdx_bass_secondary_model: No Model Selected
mdx_drums_secondary_model: No Model Selected
mdx_is_secondary_model_activate: False
mdx_voc_inst_secondary_model_scale: 0.9
mdx_other_secondary_model_scale: 0.7
mdx_bass_secondary_model_scale: 0.5
mdx_drums_secondary_model_scale: 0.5
is_save_all_outputs_ensemble: True
is_append_ensemble_name: False
chosen_audio_tool: Manual Ensemble
choose_algorithm: Min Spec
time_stretch_rate: 2.0
pitch_rate: 2.0
is_gpu_conversion: True
is_primary_stem_only: False
is_secondary_stem_only: False
is_testing_audio: False
is_add_model_name: False
is_accept_any_input: False
is_task_complete: False
is_normalization: False
is_create_model_folder: False
mp3_bit_set: 320k
save_format: WAV
wav_type_set: PCM_16
help_hints_var: False
model_sample_mode: False
model_sample_mode_duration: 30
demucs_stems: All Stems`

Hi, from my own experiments I can confirm that the 760 is not supported and never will since the CUDA-support is too low. The 1060 is probably the smallest card that works, but I doubt that it has enough resources so that you would gain a real speed increase compared to CPU processing.


Samples inAndroid via menu + upgrade 8.1

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


Inconsistent state on startup

When controllers start they can potentially have inconsistent state based on the other controllers they rely on for their data.
This affects at least Wrangler and Norman.

[ ] Wrangler PR

[ ] Norman PR

Norman: https://github.com/rancher/norman/pull/340
Wrangler: https://github.com/rancher/wrangler/pull/61

rancher/rancher:master-head ad9c7118
Regression test via automation

Automation for provisioning all cluster types
Smoke & long running tests
No unexpected results


Shortcut

Update Alt to Ctrl
Show no match when result is in the find text field itself
WIP: Shortcut guide

Can't wait! Merged and release ASAP!

Can't wait! Merged and release ASAP!

No problem, I'll create another PR for the shortcut guide.


How to open a new tab when I cmd + click?

VSCode Version: 1.7.1
OS Version: MacOS Sierra 10.12.1

Steps to Reproduce:
There is two file 'a.js' and 'b.js' in my directory. 'b.js' is empty and this is my 'a.js'.

when I move cursor to './b.js' and 'cmd + click' to see 'b.js'. It doesn't open 'b.js' in the new tab.

What I want to do is to open 'b.js' in a new tab so that I can switch between 'a.js' and 'b.js'. How do I do that?

@Larry850806 try setting "workbench.editor.enablePreview": false in settings to always force keeping a file as tab.

I love preview mode, but not the case when I command + [click] or using quick open, it would be much more convenient if there're more specific options for this behavior.


Import guide line in README.md

I think it is the best to add a line on how to import this module:
import { IonAffixModule} from 'ion-affix'

it solved my problem, thanks


Show version of rust being installed

Fixes #1007
I haven't updated the tests yet in case we want to change how it's displayed.

Example output:
info: syncing channel updates for 'nightly-x86_64-pc-windows-msvc'
info: latest update on 2015-01-02, rust version 1.3.0
info: downloading component 'rust-std'
info: downloading component 'rustc'
info: downloading component 'cargo'
info: downloading component 'rust-docs'
info: installing component 'rust-std'
info: installing component 'rustc'
info: installing component 'cargo'
info: installing component 'rust-docs'
info: default toolchain set to 'nightly-x86_64-pc-windows-msvc'

Patch looks good to me, but failures are legit. r=me when fixed.

:pushpin: Commit edd013c has been approved by brson

@bors r=brson

:hourglass: Testing commit edd013c with merge ef63df3...

:broken_heart: Test failed - status-appveyor

@bors retry

:hourglass: Testing commit edd013c with merge c26a45b...

:sunny: Test successful - status-appveyor, status-travis
Approved by: brson
Pushing c26a45bc79b4c54d84dcb3edaf91cc08e6ad8c6a to master...


Patch 1.5.2

Link
Type
1.5.x
Comment

#2475
Build
✅

#2461
Bug
✅

#2454
Clarification
✅

#2452
Doc
✅

#2392
Build
✅

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 4 committers have signed the CLA.:white_check_mark: Transurgeon:white_check_mark: timkpaine:white_check_mark: cjerdonek:x: sven-oxionicsYou have signed the CLA already but the status is still pending? Let us recheck it.

I think we should also add #2392 to fix all the build errors.

Thanks @Transurgeon! It would be best to also back port the updates to the CI to make sure the release goes smoothly.

Thanks @Transurgeon! It would be best to also back port the updates to the CI to make sure the release goes smoothly.

Could you clarify what you mean by CI updates? Does that include all the bumps that the bot is doing?
Thanks!

@Transurgeon yes, exactly. All the merged PRs opened by Dependabot. It's not guaranteed that we would need those minor updates, but we observed in the past that outdated CI versions caused issues during deployment.

@phschiele Done.


Added a plugin to prevent accidental app submissions using unsigned Xcode

This patch will automagically install xGhostPreventer after grating Xcode to remind people that distributing apps through an unsigned Xcode is a really bad idea :)

This fixes #4
Thanks for your contribution 💙


Implement Reset for MySQL

I will work on enabling eventsV2 test after this PR: https://github.com/uber/cadence/issues/1686


Bug: Middy, should IdempotencyAlreadyInProgressError return a 409?

Expected Behavior
IdempotencyAlreadyInProgressError has a config option to be handled, like the the responseHook such as onErrorResponseHook or the error by default triggers a 409 as we make a positive assumption that as a transaction is in progress this request can be considered already processed at this point in time.
Current Behavior
If IdempotencyAlreadyInProgressError  is triggered due to a parallel request by default an unhandled 500 error is thrown.
Code snippet
export const handle = middy(handler)
  .use(makeHandlerIdempotent({ persistenceStore, config: idempotencyConfig }))

Steps to Reproduce

Setup a lambda with middy makeHandlerIdempotent middleware
Create a parallel request to trigger a IdempotencyAlreadyInProgressError
See error in response There is already an execution in progress with idempotency key: x with status 500

Possible Solution
As above we make a positive assumption the in progress transaction is because a request is likely already processed and should return a 409 or functionality is provided to handle the error directly from the middleware.
I may be completely off in this report but it seems like 500 from something that is probable seems a bit of a harsh default?
Powertools for AWS Lambda (TypeScript) version
latest
AWS Lambda function runtime
22.x
Packaging format used
npm
Execution logs

Hi @andrewdavidcostello, thank you for opening the issue.
The Idempotency middleware is designed to do one of two things:

Return the response from your function, either by running it (new requests) or by returning the stored result (when idempotent)
Throw one of few errors depending on what the idempotency state is

When an error is thrown and it's not handled by your code, AWS Lambda interprets this as an unhandled exception or a server error.
By itself Lambda is just a compute environment, it doesn't inherently act as an API. Because of this, there's no HTTP code attached to these errors, you can check the codebase.
By reading both this issue, and the other one you opened, it seems that you're running an API with Lambda acting as the "server".
If this is the case, any unhandled error thrown by the function handler is interpreted by API Gateway as a 500 error, since from the caller perspective (API Gateway) the server (Lambda) just throws an error.
To customize what your API returns when certain errors occur, you'll have to either refactor your code to handle the error and return the status code you want, or work on the API side to transform the request.

Again thanks for the quick reply on this, much appreciated.
No worries, I guess the intent here is not to be overly opinionated which makes a lot of sense, we will update our error handler to handle these scenarios.
Just wanted to also be sure this was the intended behaviour.

It's ok, it's a fair question, the problem is we don't have a way of influencing which HTTP error code is returned since we are not specifying one in the first place.
From the Idempotency middleware perspective, we purposefully don't want to have an opinion on how you handle the error since not all use cases will be APIs. But then again, even if we had an opinion, we still don't return a response with a status code in it, so we can't do much about this.
For this specific case, you can either write a custom Middy.js middleware similar to this:
import { IdempotencyAlreadyInProgressError } from '@aws-lambda-powertools/idempotency';

const idempotentErrorHandler = () => {
  const onError = async (request) => {
    if (request.error && request.error.name instanceof IdempotencyAlreadyInProgressError) {
      return {
        statusCode: 409,
        message: 'foo'
      }
    }
  };

  return {
    onError,
  };
};

or refactor the function code to make only a portion of your code idempotent, rather than the entire request. This way you'd be able to wrap the idempotent part within a try/catch and return the error code you want.

Thanks, yeah the error handling that bubbles up to looks very similar to that just now so will stick with that.
If you don't mind a slight tangential query?
Is the Idempotency middleware meant to be able to prevent request spamming, as we observed for example sending 50 of the same request in quick succession that then ran against multiple lambda instances allowed multiple of the same requests to be created.

as we observed for example sending 50 of the same request in quick succession that then ran against multiple lambda instances allowed multiple of the same requests to be created.

No, this should not be the case - but if it has happened, we'd appreciate it if you could share a reproduction example that we can test. This way, if valid, we can try fixing the bug and prevent this from happening.


to add food recipe bot

Aim
To add the food recipe bot
Details

this bot will tell the recipe of particular food dishes

Go Ahead @Owais24code

@avinashkranjan thankyou sir , for assign this issue to me .

@avinashkranjan Sir, i would like to work on it and contribute under GSSoC'23 program.
So, please assign this task to me.
/assign


added login form with social media sign in buttons

@sahilit Awesome Work.
Note

Create a readme.md file inside folder you have created.
Put your Email address or name inside readme.md.
You can also provide other information about you in readme.md.

Read this before making your PR.

Sure ill add the required changes
Thanks & Regards
Tushar Chand Kapoor
https://www.tusharck.com

On Oct 12, 2019, at 12:21 AM, Raavan<EMAIL_ADDRESS>wrote:
@sahilit https://github.com/sahilit Awesome Work.
Note
Create a readme.md file inside folder you have created.
Put your Email address or name inside readme.md.
You can also provide other information about you in readme.md.
Read this https://shravanmeena.github.io/RaavanHack/ before making your PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ShravanMeena/RaavanHack/pull/40?email_source=notifications&email_token=AB77KUQEL3WQNTTZXIHJXATQOF3GZA5CNFSM4JAAX53KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBBYH3I#issuecomment-541295597, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB77KUXOG35ULZJT22PYUYDQOF3GZANCNFSM4JAAX53A.

@tusharck  create a readme.md inside folder you have created.


Devoncarew saucelabs

Not yet for review - an in-progress PR to get testing working with saucelabs.

sauce_connect now working locally


Send data to CC platform

Sending data added to the application, APK  created for testing. Closing as done. If needed new tickets will be opened.


Add methods FileHelper::findDirectories() and FileHelper::findFiles() + fix unlink broken symlinks in windows

Q
A

Is bugfix?
✔

New feature?
✔

Breaks BC?
✔

Fixed issues
#13

Add FileHelper::findDirectories()
Add FileHelper::findFiles()
FileHelper::unlink() is void function
Fixed: in windows throws error on remove symlink to not exists dir via FileHelper::unlink().
Improve readme and changelog

"Make recursive filtering really recursive" (#13) implemented in findDirectories(), but not in copyDirectory. I think this is right: if I except parent directory, then not need copy children files and directories.

Awesome!


Error on Install - Unable to determine GEOS version

I'm getting an error when installing using miniconda on macOSX (10.14.6 Mojave).
I've installed using miniconda (v 4.8.3) and that part ran without error.
But when I try to install ESMValTool using:
 pip install -e '.[develop]'
I get the following error:
Collecting cartopy
  Downloading Cartopy-0.17.0.tar.gz (8.9 MB)
     |████████████████████████████████| 8.9 MB 2.4 MB/s
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  ERROR: Command errored out with exit status 1:
   command: /opt/miniconda3/bin/python /opt/miniconda3/lib/python3.7/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /var/folders/j7/dlfj35251j1fyb2kf0rmnf504xpdt4/T/tmpzaloyg9b
       cwd: /private/var/folders/j7/dlfj35251j1fyb2kf0rmnf504xpdt4/T/pip-install-ol6z8v2c/cartopy
  Complete output (3 lines):
  setup.py:171: UserWarning: Unable to determine GEOS version. Ensure you have 3.3.3 or later installed, or installation may fail.
    '.'.join(str(v) for v in GEOS_MIN_VERSION), ))
  Proj 4.9.0 must be installed.
  ----------------------------------------
ERROR: Command errored out with exit status 1: /opt/miniconda3/bin/python /opt/miniconda3/lib/python3.7/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /var/folders/j7/dlfj35251j1fyb2kf0rmnf504xpdt4/T/tmpzaloyg9b Check the logs for full command output.

When I look into this, it appears that its installed.
e.g.,
/opt/miniconda3/envs/esmvaltool/lib/libgeos-3.7.2.dylib
is present.

it's not geos the problem but proj4 https://anaconda.org/conda-forge/proj4 - looking at your trace I can see you are not working in a pre-built esmvaltool environment - have you created it and conda activate it? Since if either of these steps have not been performed then proj4 will not be in the installation path, can you pls post the following output:
which python
conda env list
conda list geos
conda list proj4

cheers :beer:

I finally got it to build. I'm not 100% sure, but might have been I didn't activate first.

cool! good to know it still works fine on OSX (I haven't tested that in a while), cheers for the heads up :beer:

@valeriupredoi What would be helpful, in the installation page, for non-python folks like myself, is to change the wording "You can activate the environment using the command:" to something such as "You should then activate the environment using the command:".

good call, cheers, will put that in the doc :beer:

https://github.com/ESMValGroup/ESMValTool/pull/1634

Useful info in the PR. Looked like this change wasn't there yet...
"You can activate the environment using the command:" ->
"You must then activate the environment using the command:"
(Maybe also put on its own line.)

just tagged you in the PR at the line that changed :grin:


Switched from Node v16 to v20

Current dependencies on/for this PR:

main

PR #338   👈

This comment was auto-generated by Graphite.


Remove upper bound on globalize version

as there is a version 5 now.

Does it work with version 5?

Good question ;) (checks)

CI will tell us.

looks like an (unrelated) dependency issue with minitest and rails 4.2 (requires newer minitest version)

(looking into it)

@courtenay I'm trying this also https://github.com/globalize/globalize-versioning/pull/9.

@courtenay thanks for taking this on the air! I fixe this in #9. 0.1.0 will be release in minute.


new bug after https://github.com/bobiverse/docxplate/pull/18

@nightmorning one more bug emerged after https://github.com/bobiverse/docxplate/pull/18
go test

--- FAIL: TestPlaceholders (0.00s)
panic: runtime error: slice bounds out of range [20:2] [recovered]
	panic: runtime error: slice bounds out of range [20:2]

I was quick to approve your PR, but why did you want to match {A}} and {{B} ?

Ok this is deeper problem and added some time ago. I'll check in near future :)

I'm just trying to fix this issue, it seems like there are still some issues that haven't been considered yet

@nightmorning one more bug emerged after #18
go test

--- FAIL: TestPlaceholders (0.00s)
panic: runtime error: slice bounds out of range [20:2] [recovered]
	panic: runtime error: slice bounds out of range [20:2]

There will be errors when using {{A} in my template

The result I want is not to replace the placeholders, so that users can discover errors on their own

I think we will move to remove this quick-fix at all. And thanks for fixing bugs you ecountered :)

thanks👍🏻


Memorizing last window position and size

I'm running yakyak on Ubuntu 17.10 with vanilla gnome on Xorg.
Since I have a multi monitor setup in 99% of the time the yakyak window appears on the splitting line of two monitors leaving it part on one and part on the other.
An option maybe to make it remember its last position and size would be very good.

I have a related issue.  When switching from one multi-monitor to another, the window position is remembered, but off the screen.
In Windows 10, using Cascade windows, Show windows stacked or Show windows side by side didn't reveal the YakYak window.  Right-clicking while holding down shift doesn't bring up the menu with 'Move' in it.
In the end, the only way I was able to retrieve the window was using Alt + Space + M to move it in to view.


Why was group-based middleware support removed?

I currently have a use-case where I have an api.domain not /api setup. And I do not want to have to open up my entire application just to support the api requests.
Is there a way to support this currently, perhaps by filtering by domain somehow? If not, I'm really curious why group-based middleware support was removed =\ It would have handled my use-case perfectly.

I concur.
We have multiple different sites poking our API endpoints. A series of middleware must run in sequence (configured as a group of middlewares), that detects the site, amongst other things. Only after some middlewares run that HandleCors should run, as it requires context to, for instance, dynamically set the allowed_origins.
What is the alternative, if any ?

Hey @barryvdh, any plan to reinstate support for group-based middleware any time soon ? Thanks for the package btw ;)

Would appreciate feedback @barryvdh

I think it would work in a group, but you want different options?

I think it would work in a group, but you want different options?

What kind of options? This used to be part of group middleware, which allows you to group routes together nicely for CORS support, which we can no longer do.

Any progress here @barryvdh ?

I had the same issue, and according to https://github.com/fruitcake/laravel-cors/pull/514 you can do something like
'paths' => [
    'api.domain' => ['*']
]

in the config/cors.php.
tested and working for me

It definitely doesn't work at the group level. @barryvdh would be good to get some clarification on this.

yeah you still need to put it in global but why do you need to apply it on a group if you can filter by domain with the "hack" ?


Fixing the issue #390

Have you read the Contributing Guidelines ?
Yes
Description
(Write your answer here.)
Fixes #390

Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

@Photon149 Check !!


Feat req: Ability to download from private repos

Please?

@corysimmons does https://github.com/phated/github-download-directory/commit/f53a426f4e71b733f04754f47dd4313768b4dc23 work?

Just published 2.0.0 which switched to using octokit. It required a changing API, so check out the README usage examples or tests for that.
You can pass any octokit client configuration as { github: {} } to the Downloader constructor.

Very cool thank you.


Improve the error message of ReadTestCert's panic

The error from x509.ParseCertificate was not being included within the panic.Debugging is easier if this information is retained.

Thanks for the merge, Zakir.


Fix the link to run_e2e_workflow.py script

Coverage remained the same at 96.512% when pulling 712524e292ba7462f116e595f3cb74164b65955a on terrytangyuan-patch-1 into a74b423b1bb040771f447a8564fe4cd6fd1f63e0 on master.

/assign @gaocegege @johnugeorge

/approve


chore: update version link in go.mod

https://github.com/taikoxyz/taiko-mono/blob/5bff52f6d830dddaee16a3959f71feba2355043c/go.mod#L34
The data is outdated, a new version v2 has been released. The correct link will look like: gopkg.in/go-playground/assert.v2 v2.2.0

Thanks for the reminder, We can update dependence by using the command go mod tidy.

Also, recommend using "github.com/stretchr/testify".


feat: add clawback cli and tests

Description
This PR adds cli for clawback vesting account, tests and test suites for the added cli as well.

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] followed the guidelines for building modules
[ ] included the necessary unit and integration tests
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

Merging #207 (718540a) into mattverse/clawback (3e2d807) will increase coverage by 0.10%.
The diff coverage is 86.89%.

@@                  Coverage Diff                   @@
##           mattverse/clawback     #207      +/-   ##
======================================================
+ Coverage               60.99%   61.10%   +0.10%
======================================================
  Files                     591      591
  Lines                   54431    54789     +358
======================================================
+ Hits                    33202    33478     +276
- Misses                  19190    19260      +70
- Partials                 2039     2051      +12

Impacted Files
Coverage Δ

x/auth/vesting/client/cli/tx.go
46.36% <64.34%> (ø)

x/auth/vesting/client/testutil/suite.go
100.00% <100.00%> (ø)

x/staking/keeper/msg_server.go
16.27% <0.00%> (-2.12%)
:arrow_down:

x/staking/types/params.go
37.30% <0.00%> (-1.11%)
:arrow_down:

x/staking/module.go
62.50% <0.00%> (-0.52%)
:arrow_down:

x/staking/client/testutil/suite.go
99.43% <0.00%> (-0.01%)
:arrow_down:

x/staking/keeper/params.go
100.00% <0.00%> (ø)

x/staking/legacy/v046/store.go

x/staking/keeper/migrations.go
50.00% <0.00%> (+16.66%)
:arrow_up:


Implement idle snapshot autounmount

I had to split iml-api-utils to prevent leakage of unwanted dependencies into iml-gui.
Signed-off-by: Michael Pankov<EMAIL_ADDRESS>

This change is

I had to split iml-api-utils to prevent leakage of unwanted dependencies into iml-gui.

I had to split iml-api-utils to prevent leakage of unwanted dependencies into iml-gui.

It should to get a meaningful name :)

Maybe it is possible to add an optional submodule instead.

I tried that, it still causes a cycle to appear, because extract_id has to be used in iml-wire-types which are used by everything else. I think splitting is lesser evil.
Renamed the crate too.

I had to split iml-api-utils to prevent leakage of unwanted dependencies into iml-gui.

How did that cause leakage into the GUI?

How did that cause leakage into the GUI?

@jgrund It depends on iml-wire-types that depends on iml-api-utils which would depend on tokio with wait_for_cmds implemented.

It seems like instead of duplicating wait_for_command etc and removing the term bits we should use conditional compilation.
There could be a wasm / browser feature  that disabled the bits entirely. There could also be a cli feature that would enable the bits that print to the console.

I've deduplicated the code using a feature. One feature is enough it seems.

Nevermind, I've abstracted everything away. Please see the final version of code.

It stopped working correctly :( Testing and fixing again

There's something weird going on. 2 times of 3, iml server add stopped after
[1/4]   ✔ Validation host configuration mds1.local successful
[1/4]   ✔ Validation host configuration mds1.local successful
[2/4]   ✔ Validation host configuration mds2.local successful
[3/4]   ✔ Validation host configuration oss1.local successful
[4/4]   ✔ Validation host configuration oss2.local successful

w/o any errors with exit code 101.
Third time it continued to deploy agents as it should do usually.

@mkpankov Can you review / rebase on #2251? It separates out the command polling logic and should be easy to integrate into this change.

I've rebased.

This has conflicts on latest master

A few other nits in the issue, up to you if you'd like to change them.

Good suggestions, I've implemented them


chore(deps): Upgrade uuid to v11 and TypeScript to v8

Rationale
The purpose of this PR is to enhanceour dependency stack by incorporating the latest major versions of uuid and TypeScript.
Overview of Changes

Upgraded the uuid library to version 11
Elevated TypeScript and its associated packages to version 8 (major release)

I only see uuid in there


Add a comment to build.sh on why the external_ images are pulled first

rather than docker-compose build --pull used

Thank you :)
On Fri, Apr 13, 2018 at 11:40 AM Kieren Evans<EMAIL_ADDRESS>wrote:

@kierenevans approved this pull request.
👍
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/continuouspipe/dockerfiles/pull/474#pullrequestreview-111962674,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAxHEYASa_0NOatp6o2PEjT3jgYqgqzWks5toICBgaJpZM4TTO1m
.


Update to v0.3.2

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Closing this as a new version of jupyterlab-blockly will be released with the needed fixes. The _version.py file was reading the package.json file and extracing the version from it, which was causing the error as the package.json file wasn't shipped alongside the python code.


Scheduling

Schedule week two and week three meetings by end of January 22nd

Update meeting scheduled for February 4 at 9:30am. Need to discuss additional availability for the report meeting.

Report meeting scheduled for February 10 at 3:00-3:15pm


synchronization is not working

build this example of a very simple rest API with two endpoints, one '/' that returns ok and the other that displays the '/metrics' counter, it turns out that if I make a simultaneous access with the command xargs -I % -P 8 curl "http://<IP_ADDRESS>:3161/" < <(printf '%s\n' {1..4}) this counter was supposed to have a value of 400 but instead it gives me different values for each execution
import 'dart:convert';
import 'dart:io';
import 'dart:isolate';
import 'package:shared_map/shared_map.dart';
//run with: xargs -I % -P 8 curl "http://<IP_ADDRESS>:3161/" < <(printf '%s\n' {1..4})

void main(List<String> args) async {
  final store1 = SharedStore('t1');
  final counter = await store1.getSharedMap<int, int>('m1');
  final counterReference = counter!.sharedReference();
  counter.put(0, 1);

  final args = ['<IP_ADDRESS>', 3161];
  final concurrency = 2;
  for (var i = 0; i < concurrency - 1; i++) {
    await Isolate.spawn(startIsolate, [i, ...args, counterReference]);
  }
  startIsolate([concurrency - 1, ...args, counterReference]);
}

void startIsolate(List args) async {
  final id = args[0] as int;
  final address = args[1] as String;
  final port = args[2] as int;
  final counterReference = args[3] as SharedMapReference;
  final server = await HttpServer.bind(address, port, shared: true);
  server.listen((req) {
    log(req, id);
    handler(req, req.response, counterReference);
  });
  print('server $id ${server.address.address}:${server.port}');
}

void handler(
    HttpRequest req, HttpResponse res, SharedMapReference counterR) async {
  final counter = SharedMap<int, int>.fromSharedReference(counterR);

  if (req.uri.path != '/metrics') {
    // increment
    counter.put(0, (await counter.get(0))! + 1);
  }
  switch (req.uri.path) {
    case '/':
      res.withString('ok');
      break;
    case '/metrics':
      res.withString('count ${(await counter.get(0))!}');
      break;
    default:
      res.notFound();
  }
}

void log(HttpRequest req, int id) {
  print('$id ${req.method} ${req.uri.path}');
}

extension HttpResponseExtension on HttpResponse {
  void withJson(Object? object) {
    this.statusCode = 200;
    this.writeln(jsonEncode(object));
    this.close();
  }

  void withString(String str) {
    this.statusCode = 200;
    this.writeln(str);
    this.close();
  }

  void ok() {
    this.statusCode = 200;
    this.close();
  }

  void notFound() {
    this.statusCode = 404;
    this.close();
  }
}

I do it with a pointer and the native_synchronization package works correctly
import 'dart:convert';
import 'dart:ffi';
import 'dart:io';
import 'dart:isolate';

import 'package:ffi/ffi.dart';
import 'package:native_synchronization/primitives.dart';
import 'package:native_synchronization/sendable.dart';

//run with: xargs -I % -P 8 curl "http://<IP_ADDRESS>:3161/" < <(printf '%s\n' {1..4})

void main(List<String> args) async {
  final counter = calloc<Uint64>();
  final mutex = Mutex();

  final args = ['<IP_ADDRESS>', 3161];
  final concurrency = 2;
  for (var i = 0; i < concurrency - 1; i++) {
    await Isolate.spawn(
        startIsolate, [i, ...args, counter.address, mutex.asSendable]);
  }
  startIsolate([concurrency - 1, ...args, counter.address, mutex.asSendable]);
}

void startIsolate(List args) async {
  final id = args[0] as int;
  final address = args[1] as String;
  final port = args[2] as int;
  final counterAddress = args[3] as int;
  final sendableMutex = args[4] as Sendable<Mutex>;

  final server = await HttpServer.bind(address, port, shared: true);
  server.listen((req) {
    log(req, id);
    handler(req, req.response, counterAddress, sendableMutex);
  });
  print('server $id ${server.address.address}:${server.port}');
}

void handler(HttpRequest req, HttpResponse res, int counterAddress,
    Sendable<Mutex> sendableMutex) async {
  final counter = Pointer<Uint64>.fromAddress(counterAddress);
  final mutex = sendableMutex.materialize();

  if (req.uri.path != '/metrics') {
    // increment
    mutex.runLocked(() {
      counter.value = counter.value + 1;
    });
  }

  switch (req.uri.path) {
    case '/':
      res.withString('ok');
      break;
    case '/metrics':
      res.withString('count ${counter.value}');
      break;
    default:
      res.notFound();
  }
}

void log(HttpRequest req, int id) {
  print('$id ${req.method} ${req.uri.path}');
}

extension HttpResponseExtension on HttpResponse {
  void withJson(Object? object) {
    this.statusCode = 200;
    this.writeln(jsonEncode(object));
    this.close();
  }

  void withString(String str) {
    this.statusCode = 200;
    this.writeln(str);
    this.close();
  }

  void ok() {
    this.statusCode = 200;
    this.close();
  }

  void notFound() {
    this.statusCode = 404;
    this.close();
  }
}

I have made some adjustment on your original example:
import 'dart:convert';
import 'dart:io';
import 'dart:isolate';

import 'package:shared_map/shared_map.dart';
//run with: xargs -I % -P 8 curl "http://<IP_ADDRESS>:3161/" < <(printf '%s\n' {1..4})

void main(List<String> args) async {
  final store1 = SharedStore('t1');
  final counter = await store1.getSharedMap<int, int>('m1');
  final counterReference = counter!.sharedReference();
  counter.put(0, 1);

  final args = ['<IP_ADDRESS>', 3161];
  final concurrency = 2;

  for (var i = 0; i < concurrency - 1; i++) {
    await Isolate.spawn(startIsolate, [i, ...args, counterReference]);
  }

  startIsolate([concurrency - 1, ...args, counterReference]);
}

void startIsolate(List args) async {
  final id = args[0] as int;
  final address = args[1] as String;
  final port = args[2] as int;
  final counterReference = args[3] as SharedMapReference;
  final server = await HttpServer.bind(address, port, shared: true);

  final counter = SharedMap<int, int>.fromSharedReference(counterReference);

  server.listen((req) {
    log(req, id);
    handler(req, req.response, counter);
  });

  print('server $id ${server.address.address}:${server.port}');
}

void handler(
    HttpRequest req, HttpResponse res, SharedMap<int, int> counter) async {
  final path = req.uri.path;

  var count = await counter.get(0);

  switch (path) {
    case '/':
      var count2 = await counter.put(0, count! + 1);
      res.withString('ok (count: $count -> $count2)');
      break;
    case '/metrics':
      res.withString('count $count');
      break;
    default:
      res.notFound();
  }
}

void log(HttpRequest req, int id) {
  print('$id ${req.method} ${req.uri.path}');
}

extension HttpResponseExtension on HttpResponse {
  void withJson(Object? object) {
    statusCode = 200;
    writeln(jsonEncode(object));
    close();
  }

  void withString(String str) {
    statusCode = 200;
    writeln(str);
    close();
  }

  void ok() {
    statusCode = 200;
    close();
  }

  void notFound() {
    statusCode = 404;
    close();
  }
}

Request outputs:
 xargs -I % -P 8 curl "http://<IP_ADDRESS>:3161/" < <(printf '%s\n' {1..4})
ok (count: 1 -> 2)
ok (count: 2 -> 3)
ok (count: 3 -> 4)
ok (count: 3 -> 4)

Since the "increment" computation is not made inside the main Isolate, there's no "synchronization", this is why it's possible to get duplicated/missed counts.

Take a look into this branch:
https://github.com/gmpassos/shared_map/pull/12
Best regards.

See the new version, with the method SharedMap.update:
shared_map: ^1.1.6

Here's your code using the new update method (shared_map: ^1.1.6):
import 'dart:convert';
import 'dart:io';
import 'dart:isolate';

import 'package:shared_map/shared_map.dart';
//run with: xargs -I % -P 8 curl "http://<IP_ADDRESS>:3161/" < <(printf '%s\n' {1..4})

void main(List<String> args) async {
  final store1 = SharedStore('t1');
  final counter = await store1.getSharedMap<int, int>('m1');
  final counterReference = counter!.sharedReference();
  counter.put(0, 1);

  final args = ['<IP_ADDRESS>', 3161];
  final concurrency = 2;

  for (var i = 0; i < concurrency - 1; i++) {
    await Isolate.spawn(startIsolate, [i, ...args, counterReference]);
  }

  startIsolate([concurrency - 1, ...args, counterReference]);
}

void startIsolate(List args) async {
  final id = args[0] as int;
  final address = args[1] as String;
  final port = args[2] as int;
  final counterReference = args[3] as SharedMapReference;
  final server = await HttpServer.bind(address, port, shared: true);

  final counter = SharedMap<int, int>.fromSharedReference(counterReference);

  server.listen((req) {
    log(req, id);
    handler(req, req.response, counter);
  });

  print('server $id ${server.address.address}:${server.port}');
}

void handler(
    HttpRequest req, HttpResponse res, SharedMap<int, int> counter) async {
  final path = req.uri.path;

  var count = await counter.get(0);

  switch (path) {
    case '/':
      // Un-synchronized computation:
      //var count2 = await counter.put(0, count! + 1);

      // Synchronized computation:
      var count2 = await counter.update(0, _increment);

      res.withString('ok (count: $count -> $count2)');
      break;
    case '/metrics':
      res.withString('count $count');
      break;
    default:
      res.notFound();
  }
}

int _increment(int k, int? v) => (v ?? 0) + 1;

void log(HttpRequest req, int id) {
  print('$id ${req.method} ${req.uri.path}');
}

extension HttpResponseExtension on HttpResponse {
  void withJson(Object? object) {
    statusCode = 200;
    writeln(jsonEncode(object));
    close();
  }

  void withString(String str) {
    statusCode = 200;
    writeln(str);
    close();
  }

  void ok() {
    statusCode = 200;
    close();
  }

  void notFound() {
    statusCode = 404;
    close();
  }
}

With the use of the update method it is now working correctly, what synchronization logic are you using? I didn't look at your source code but I saw that you are not using the native_synchronization package so I think you are not using Mutex right?
xargs -I % -P 8 curl "http://<IP_ADDRESS>:3161/" < <(printf '%s\n' {1..4000})
...
ok (count: 3993 -> 3994)
ok (count: 3994 -> 3995)
ok (count: 3995 -> 3996)
ok (count: 3996 -> 3997)
ok (count: 3997 -> 3998)
ok (count: 3998 -> 3999)
ok (count: 3999 -> 4000)

what synchronization logic are you using?
...
I saw that you are not using the native_synchronization package

I believe this is the most crucial point. When attempting to establish parallelism without multi-threading memory manipulation, we can't apply the same paradigms/techniques of data manipulation and synchronization. Therefore, using a "native" mutex in the Dart SDK (similar to the JDK) is not the ideal approach.
What we need is not a MUTEX but a "critical section" or a "safe" region for manipulating the data. Therefore, what I've done is to ensure that the updater lambda/anonymous/closure function you pass to the SharedMap.update method is executed in a safe region, in this case, within the main SharedMap instance (main/original Isolate).
In other words, the updater lambda/anonymous/closure function is passed as a parameter to the main Isolate (supported since Dart 2.15). Subsequently, the updater code is executed in the main Isolate in a thread-safe manner.

You can read more about in this Medium article:
https://medium.com/@gracilianomp/using-shared-map-for-concurrency-in-dart-d15eafcb715a


Can't change card background anymore

I think that cardStyle prop for StackNavigator has some problems, since before recent update this code worked:
var AppNavigator = StackNavigator({
    ...
}, {
    headerMode: 'screen',
    cardStyle: {
        backgroundColor: 'white'
    }
});

and now I don't know how to change the background of all screens to white.
I see that at line 169 of https://github.com/react-community/react-navigation/blob/master/src/views/CardStackTransitioner.js cardStyle prop isn't passed to CardStack component.

Yeah, that is a regression from our recent big update. Thanks for catching it. PR is already waiting.

+1

@gsaandy fix is in master now, i tried and it works.

tried and working fine with master 👍


ETL Subscription should never expire.

This PR is fixing a 'mystery of deleted subscriptions'.
By default inactive subscriptions are removed after 31 days and we do not want that.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.15%. Comparing base (9009296) to head (774ba7e).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #759   +/-   ##
=======================================
  Coverage   77.15%   77.15%
=======================================
  Files         157      157
  Lines       12950    12950
=======================================
  Hits         9991     9991
  Misses       2959     2959

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


After v7s Release, v6 is looking for v7's css

Using v6?
v6 is now considered feature complete to its current abilities and limitations. We are not actively working to fix any issues for v6 any more. We will, however, merge any non-breaking pull requests submitted to fix anything in v6.
Using v7?
Thanks for using the beta version of React Table v7! We're very excited about it.
Describe the bug
Using "react-table": "^6.10.3", I did try changing it to "react-table": "6.10.3", and no dice there either
GET<EMAIL_ADDRESS>net::ERR_ABORTED 404
To Reproduce
Steps to reproduce the behavior:

Go to '.https://www.doingthingsmedia.com/dashboard'
Click on 'Inspect Element'
Check out the console.
See error

Expected behavior
v6 should not be looking for v7's css
Codesandbox!
Use a new react-table codesandbox to reproduce the issue.
Screenshots
https://dtm-app-test.s3.us-east-2.amazonaws.com/Screen+Shot+2019-12-02+at+10.54.03+AM.png
Desktop (please complete the following information):

OS: 10.15.1

Browser Chrome

Version Version 78.0.3904.108
Smartphone (please complete the following information):

Device: [e.g. iPhone6]

OS: [e.g. iOS8.1]

Browser [e.g. stock browser, safari]

Version [e.g. 22]

Additional context
Add any other context about the problem here.

Also having this problem. Error in console leads to a link displaying:
"Cannot find "/react-table.css" in<EMAIL_ADDRESS>

Yeah, I'm seeing this issue as well in production code, returning 404 on<EMAIL_ADDRESS>

This is an issue with the css included in the index.html file. The latest version no longer has the css file, so you need to specify the version in the stylesheet url.
It is the public/index.html file
<link rel="stylesheet"<EMAIL_ADDRESS>This is in there, pointing to the latest release, which no longer seems to have the css file
Change it to:
<link rel="stylesheet"<EMAIL_ADDRESS>

Yep, v7 no longer comes with css (the examples have the bare minimum to get you to a working table with decent layout.
If you are still using v6, you should be locking your version to the ^6 tag at the very least and not the @latest tag.


Allow --test expression to declare file dependencies

Would it make sense to allow the Haskell expression passed in with the --test option to somehow declare what non-Haskell files it ended up depending on, so that they can be added to the watch list.
This would allow a tighter integration with any workflow that involves external files. Application configurations, test inputs/outputs or, in my case, DB migrations would be useful to watch this way.
I guess one can also organize the project file structure so that all interesting files live under predetermined folders so one can pass those folders to --reload, but being able to declare these dynamically might allow richer workflows.
Another alternative could be to use a --test expression that keeps running after doing what it's supposed to do and then it starts watching the files itself and repeats what it does when any of them change. This avoids the need for any cooperation from ghcid, but I think this is a clunkier solution.
As for how this ticket might work; Would it be possible to let the --test expression to produce a result of some special type that ghcid interprets specially. Maybe a record that contains a field externalDependencies :: [FilePath]. Or maybe ghcid just shows the output of the expression as usual and just interprets the string looking for some special forms, similar to how --allow-eval looks for -- $> comments to evaluate.

I think having test figure out new dependencies would be possible, but I wonder if the ability to do so dynamically is worth the hassle? Are the things being read hard to figure out in advance (or at least an approximation thereof) and put in --reload? I'm not sure this feature would be that heavily used.

I agree, it would be unusual to have use cases that can't be addressed with --reload. In my case, I'm trying to set up an unusual workflow involving a Haskell eDSL and some external files and the audience for this workflow isn't Haskell experts. I think it makes conceptual sense for --test to declare dependencies, since the result of the expression is allowed to depend on arbitrary files.
That said, unless this would be useful to others, I think I can also just start a thread and watch these files myself and touch a file watched by ghcid whenever any of these external files change, triggering a reload.

The thread touching a file seems like a reasonable way to go for now, until we find other people with similar use cases.


Add reportField menu items in the Expense Report View

https://docs.google.com/document/d/1LXGXwWsei-Zx2wJMaYBmVe_M8NH7AHJZ5bIqwSec4uo/edit?disco=AAAA83rYsHk

Hello, Sir.
I can help you with your problem and please contact me.

Not overdue Melv. Working on the PR!

Updating today!

PR: https://github.com/Expensify/App/pull/33392

PR still in review!

Damn sorry for missing this, I filter issues where the payment date is more than 2 days in the past, but always get notified about Overdue. Obv I wasn't assigned then. I'll handle the Upwork job now.

Payment Summary:

@getusha paid $500 here C+
@allroundexperts requires payment through NewDot Manual Requests $500 (Contributor this time)

@twisterdotcom accepted the offer, could you please close it?

$500 approved for @allroundexperts


Force Oculus Touch to right-handedness

The left hand of the Touch appears first in the list detected by the browser. This forces the ray to the right hand of the Oculus Touch.

Closing due to inactivity.


Failed building a windows desktop template on linux (mingw-w64 segfault)

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Linux
Ubuntu 17.04
Intel(R) Core(TM) i7-4702HQ
Using the default mingw-w64 package in the repos.
Issue description:

I tried to build a windows template from source with:
scons platform=windows tools=no target=release bits=64
It fails on the last compiling scene/3d/audio_stream_player_3d.cpp
scons: Reading SConscript files ... Checking for C header file mntent.h... (cached) no scons: done reading SConscript files. scons: Building targets ... [100%] Compiling ==> scene/3d/audio_stream_player_3d.cpp scene/3d/audio_stream_player_3d.cpp: In member function 'void AudioStreamPlayer3D::_notification(int)': scene/3d/audio_stream_player_3d.cpp:195:6: internal compiler error: Segmentation fault  void AudioStreamPlayer3D::_notification(int p_what) {       ^~~~~~~~~~~~~~~~~~~ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. scons: *** [scene/3d/audio_stream_player_3d.windows.opt.64.o] Error 1 scons: building terminated because of errors.
Steps to reproduce:
Everytime I build it does.
Link to minimal example project:

Does this happen when cross-compiling other C++ programs? Also, can you try cross-compiling Godot on another Linux distribution (such as Fedora) in a chroot/systemd container or virtual machine?

Just tried with a simple hello world and it seemed to work. Although wine says its a bad EXE, it still produced it.

@vopi181 what do you use for mingw64?
http://docs.godotengine.org/en/stable/development/compiling/compiling_for_windows.html#cross-compiling-for-windows-from-other-operating-systems
this document says using export MINGW64_PREFIX="/path/to/i686-w64-mingw32-" for compiling 64bit windows template, but I had an issue exported game crashes.
so I'm using this instead, and no problem anymore.
export MINGW64_PREFIX=/usr/bin/x86_64-w64-mingw32-

@Calinou I'm not expert on this and found solution on internet. maybe should document be updated?

@volzhs That doc is outdated (and wrong):
export MINGW32_PREFIX="/path/to/i586-mingw32msvc-"    // that's the old 32-bit only MinGW which we don't support
export MINGW64_PREFIX="/path/to/i686-w64-mingw32-"    // that's the 32-bit version (i686) or the new MinGW-w64 (w64)

So it should be:
export MINGW32_PREFIX="/path/to/i686-w64-mingw32-"
export MINGW64_PREFIX="/path/to/x86_64-w64-mingw32-"

But even then, this is completely unnecessary if mingw is in your PATH already.

i was able to fix this on ubuntu zesty by
adding "artful" repos in "/etc/apt/sources.list" :
deb http://cz.archive.ubuntu.com/ubuntu artful main universe
creating apt pinning file "/etc/apt/preferences.d/artful":
  Package: *
  Pin: release a=artful
  Pin-Priority: 100

updateing repos:
  apt update
and installing:
 apt install -t artful g++-mingw-w64-i686

Closing, as this seems to be fixed with the comment above. If this is still a problem with the current master, please ping us so we can reopen.


Adding own bosh-releases to MicroPCF, and e.g.: diego-release?

How do I add my own bosh-releases to MicroPCF?
Would be handy for sharing internal development environments around, and updating CF to the latest development (or stable, e.g.: v231) version.
Thanks for all suggestions
PS: Yes I have seen https://github.com/pivotal-cf/micropcf/blob/master/DEVELOP.md

I was about to ask the same question before I stumbled upon this. I would like to know about this too

Hi @SamuelMarks,
You cannot build an official version of PCF Dev (that includes services brokers) using this repo. However, you can fork this repo and modify its contents to build a version of PCF Dev that includes the Elastic Runtime along with your own BOSH-deployed components.
@mdelillo, could you explain what changes are now necessary to add new BOSH releases?

Hi @mdelillo , @sclevine ,
First off, I must say pcf-dev is really cool thing for developers.
Can you please share the steps to add new BOSH releases to pcf-dev?
Thanks

@SamuelMarks @abhikco the bosh releases used by PCF Dev are specified in the versions.json file in the root of the repo. We compile each bosh release and provide a URL to the resulting tgz on S3. If you want to add a release that exists on your local filesystem, you can use path instead of url. For example:
[
  {
    "name" : "cf",
    "url" : "s3://pcfdev/compiled-releases/cf-v235-1-ge9635da.tgz"
  },
  ...
  {
    "name" : "my-bosh-release",
    "path" : "/path/to/my-bosh-release"
  }
]

You then need to edit images/manifest.yml. Add your new release to the releases array, your release jobs to jobs.templates, and your job properties to properties. Then you should be able to build PCF Dev using images/build.

@mdelillo Hmm, so is there any real advantage to this approach, when compared with adding bosh-releases to the relevant files within bosh-lite/packer?

The advantage to our approach is that you don't need to spin up a BOSH director on the VM and deploy all the CF services to individual containers at runtime. (That's what people use BOSH-lite for.)
While it might be possible to do a BOSH deploy of CF to a BOSH-lite VM and packer-ize the result, the added complexity and resource consumption of that approach was less than ideal when I tried it. There's no reason to think that it wouldn't be possible to do this, but it's not the approach we're taking.


[SPARK-31744][R][INFRA] Remove Hive dependency in AppVeyor build temporarily

What changes were proposed in this pull request?
This PR targets to remove Hive profile in SparkR build at AppVeyor in order to:

Speed up the build. Currently, SparkR build is reaching the time limit.
Clean up the build profile.

Why are the changes needed?
We're hitting a time limit issue again and this PR could reduce the build time.
Seems like we're already skipping Hive related tests in SparkR for some reasons, see below:
test_sparkSQL.R:307: skip: create DataFrame from RDD
Reason: Hive is not build with SparkSQL, skipped
test_sparkSQL.R:1341: skip: test HiveContext
Reason: Hive is not build with SparkSQL, skipped
test_sparkSQL.R:2813: skip: read/write ORC files
Reason: Hive is not build with SparkSQL, skipped
test_sparkSQL.R:2834: skip: read/write ORC files - compression option
Reason: Hive is not build with SparkSQL, skipped
test_sparkSQL.R:3727: skip: enableHiveSupport on SparkSession
Reason: Hive is not build with SparkSQL, skipped

Although we build with Hive profile. So, the Hive profile is useless here.
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
AppVeyor will test it out.

Test build #122774 has started for PR 28564 at commit f12464e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27426/
Test PASSed.

Test build #122774 has finished for PR 28564 at commit f12464e.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/122774/
Test FAILed.

AppVeyor tests passed. The skipped tests are same:
test_sparkSQL.R:307: skip: create DataFrame from RDD
Reason: Hive is not build with SparkSQL, skipped
test_sparkSQL.R:1341: skip: test HiveContext
Reason: Hive is not build with SparkSQL, skipped
test_sparkSQL.R:2813: skip: read/write ORC files
Reason: Hive is not build with SparkSQL, skipped
test_sparkSQL.R:2834: skip: read/write ORC files - compression option
Reason: Hive is not build with SparkSQL, skipped
test_sparkSQL.R:3727: skip: enableHiveSupport on SparkSession
Reason: Hive is not build with SparkSQL, skipped

and given this run it speeded up to 10 ~ 20 mins roughly.

@dongjoon-hyun can you take a quick look please?

@dongjoon-hyun, I will just merge this. I am 100% sure this is a clean and right fix.

Thank you!


Only comment things that have business logic complexity section sample is not correct

I consider the good sample as a bad sample. Here is the actual sample code
public string hashIt(string data)
{
  var hash = 0;
  const length = data.length;

  for (var i = 0; i < length; i++)
  {
    const char = data.charCodeAt(i);
    hash = ((hash << 5) - hash) + char;

    // Convert to 32-bit integer
    hash &= hash;
  }
}

Aside the typos (function name, const without type, ...) the comment (Convert to 32-bit integer) can be avoided with another function so that you do not need a comment anymore. According to me, a comment would be useful to explain why we choose this hashing algorythm. I'd like to propose you this version of the code:
public int Hash(string data)
{
    var hash = 0;
    var length = data.Length;

    for (var i = 0; i < length; i++)
    {
        var character = data[i];
        // use of djb2 hash algorithm as it has a good compromise
        // between speed and low collision with a very simple implementation
        hash = ((hash << 5) - hash) + character;

        hash = ConvertTo32bitInt(hash);
    }
    return hash;
}

private int ConvertTo32bitInt(int value)
{
    return value & value;
}

Here is my philosophy about comments in code:
If a comment explain WHAT the code is doing, it is probably a bad comment and can be implemented with a well named variable or function. However it is hard to express by code WHY you implemented something that way. In my sample, it would be hard to express by code why the code is using djb2 instead of a sha-1 or another algorithm so a comment is acceptable.

Closed it because we will work on #41


A proposed fix for issue #26 fixes #26

This would be the functionality I was suggesting.
If you are happy with the changes and property names I'll do up some unit tests.

I see I've made an invalid assumption in my pull request that the Property Source named 'bootstrap' actually contains the properties from bootstrap.properties or bootstrap.yml.
I also see that this issue was previously requested - https://github.com/spring-cloud/spring-cloud-config/issues/57 and marked as Closed but I don't see how this would allow me to set the bootstrapped propertysources as the last PropertySources.
Just for some background I'm not using the ConfigServer but a custom property source that delegates to ZooKeeper for properties but we want the ability to specify the overrides locally.


update v2 creation docs to use built-in jq

Current dependencies on/for this PR:

main

PR #5474   👈

This comment was auto-generated by Graphite.


Update build configuration

The build configuration of this project is outdated and may no longer work.
This pull request will be merged automatically if there are no conflicts.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Issues after enabling Connection pooling, java.net.SocketException: Broken pipe and Connection closed by remote

We use batch-module:1.1.2 and the below properties for connection pooling,
simplejavamail.defaults.connectionpool.coresize=2
simplejavamail.defaults.connectionpool.maxsize=5
simplejavamail.defaults.connectionpool.claimtimeout.millis=60000
simplejavamail.defaults.connectionpool.expireafter.millis=900000
when is there more load on the server we see the below error's,
java.net.SocketException: Broken pipe
java.net.SocketException: Connection closed by remote
@bbottema - Could you please suggest if can tune our connection pooling propeties in any other way.
We connect to to a single SMTP server, which has max consurrent connections from single IP as 300

With these settings, you would have a maximum of 5 concurrent connections at any time, correct? Perhaps your server isn't too happy about long running connections, in which case you could reduce the expireafter to keep the connections fresh. Also not that it should be an issue, but that's a very long claimtimeout, implying sending emails could take up to a minute before giving the connection to the next thread trying to claim it.


Improve certain regexes

The othernode value here is bogus, it contains node address, and a start and a stop. All of this is registered under a single tag.

Here's a short list:

RANGE_RSP message received from /<IP_ADDRESS>:7000
RANGE_REQ message received from /<IP_ADDRESS>:7000
Submitted 1 concurrent range requests
Submitting range requests on 769 ranges with a concurrency of 320 (0.3 rows per range expected)
Executing seq scan across 1 sstables for (min(-9223372036854775808), min(-9223372036854775808)]


[ci] Fix quotes in CI script

Codecov Report

Merging #1036 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1036   +/-   ##
=======================================
  Coverage   91.97%   91.97%
=======================================
  Files          81       81
  Lines       10937    10937
=======================================
  Hits        10059    10059
  Misses        878      878

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 5a71caf...3174621. Read the comment docs.

I am going to revert this. For some strange reason the quotes are not needed.


Add "node_unselected" signal for GraphEdit [3.2]

There was a minor conflict with the 3.2 branch so I resolved it to make cherrypicking easier.
Same as https://github.com/godotengine/godot/pull/37773

Thanks!

Thank you as well!


OneHotEncoder with option handle_missing='error' throws "ValueError: The truth value of a Series is ambiguous" when there is more than one categorical column

When trying to use OneHotEncoder with handle_missing="error", I get the following exception: "ValueError: The truth value of a Series is ambiguous. Use a.empty, a.bool(), a.item(), a.any() or a.all()." This seems to happen only if there is more than one categorical column being encoded.
Minimal example to recreate the problem:
import pandas as pd
from category_encoders.one_hot import OneHotEncoder

df_ok = pd.DataFrame([
        [0, 'm', 1],
        [2, 'n', 5],
        [4, 'm', 4],
        [6, 'p', 2],
    ], columns=['col1', 'col2', 'col3'])

df_problematic = pd.DataFrame([
        [0, 'm', 1, 'a'],
        [2, 'n', 5, 'a'],
        [4, 'm', 4, 'b'],
        [6, 'p', 2, 'd'],
    ], columns=['col1', 'col2', 'col3', 'col4'])

# This runs
encoder_obj = OneHotEncoder(use_cat_names=True,
                            handle_missing='error',
                            handle_unknown='value')
encoder_obj.fit(df_ok)
df_transformed = encoder_obj.transform(df_ok)
encoder_obj.fit(df_ok)
print(df_transformed)

# This throws ValueError: The truth value of a Series is ambiguous. Use a.empty, a.bool(), a.item(), a.any() or a.all().
encoder_obj2 = OneHotEncoder(use_cat_names=True,
                            handle_missing='error',
                            handle_unknown='value')
encoder_obj2.fit(df_problematic)
df_transformed2 = encoder_obj2.transform(df_problematic)

# With handle_missing anything other than "error", the problem disappears
encoder_obj3 = OneHotEncoder(use_cat_names=True,
                            handle_missing='value',
                            handle_unknown='value'
                            )
encoder_obj3.fit(df_problematic)
df_transformed3 = encoder_obj3.transform(df_problematic)
print(df_transformed3)

It seems to me that the problem is in category_encoders\one_hot.py, lines 141-143:
        if self.handle_missing == 'error':
            if X[self.cols].isnull().any().bool():
                raise ValueError('Columns to be encoded can not contain null')

Could changing line 142 to:
            if X[self.cols].isnull().any().any():

solve it?
I'm using category_encoders 2.0.0 and pandas  0.22.0.

Thank you for a nice bug report.
The bug was present in the other encoders as well. But it is now fixed in the master branch.


Tweaked nginx port

I ran into conflicts with default 3000 port.. I have other stuff running on a stack of other containers that is using 3000 already. Ideally it would be nice to expose  this as a envar in docker compose and/or .env  but for now re-hardcoding.

sorry I meant to open this against my own repo .. my bad.


Haven‘t odascore and odas.cfg

I did
sudo apt-get install libfftw3-dev libconfig-dev libasound2-dev libgconf-2-4 sudo apt-get install cmake git clone https://github.com/introlab/odas.git mkdir odas/build cd odas/build cmake .. make
But I haven't found odascore and odas.cfg in the /odas/bin. There just two files, odaslive and odasserver.

I just did what the previous issue did.
The error is:
Sink pots: Invalid interface and/or format.

I read some issues.
My arecord -l shows:
card 1: ArrayUAC10 [ReSpeaker 4 Mic Array (UAC1.0)], device 0: USB Audio [USB Audio]   Subdevices: 1/1   Subdevice #0: subdevice #0
I change the nBits = 32.
But it still shows
Source hops: Cannot set sample format: Invalid argument

This is my respeaker_4_mic_array.cfg
新建文本文档 (2).txt
My local ip is <IP_ADDRESS>.
I am using Respeaker Mic Array v2.0

I did
sudo apt-get install libfftw3-dev libconfig-dev libasound2-dev libgconf-2-4 sudo apt-get install cmake git clone https://github.com/introlab/odas.git mkdir odas/build cd odas/build cmake .. make
But I haven't found odascore and odas.cfg in the /odas/bin. There just two files, odaslive and odasserver.

You need to use odaslive.

I just did what the previous issue did.
The error is:
Sink pots: Invalid interface and/or format.

That means that the sink part of your potential sources interface is wrong. Please configure according to ODAS Studio documentation.

I read some issues.
My arecord -l shows:
card 1: ArrayUAC10 [ReSpeaker 4 Mic Array (UAC1.0)], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
I change the nBits = 32.
But it still shows
Source hops: Cannot set sample format: Invalid argument

This means the specified raw format is not supported by your soundcard. Please seek ODAS repository for help. I think a sample configuration file for this sound card is provided.

Where to configure IP as I want to run this studio in local. I mean whether sst, ssl or sss, blackhole or socket?

As stated in the Configure ODAS section of ODAS Studio Documentation, you need to set the IP in each subsection of your config file: SSP, SST, SSL and SSS.
The sink type should be socket and the format JSON.

Did you find odascore and ODAS.cfg？I‘m didn't find it either,plz reply quickly,thx

老哥救命啊，我试了好多方法也是没有找到，不知道是不是什么步骤出错了，领导现在催项目了

@7IIIIIIIE are you later able to solve it, I am currently getting "cannot open audio device hw:1,0


No such package "uboot_rpi_arm64" in pkgs

error: attribute 'uboot_rpi_arm64' missing
┃        at /nix/store/xr38jsjfs9mxinx6b5jizm4g9yzhw6lx-source/rpi/default.nix:100:26:
┃            99|                 TMPFILE="$TARGET_FIRMWARE_DIR/tmp"
┃           100|                 UBOOT="${pkgs.uboot_rpi_arm64}/u-boot.bin"
┃              |                          ^
┃           101|                 KERNEL="${kernel-pkgs.rpi-kernels.latest.kernel}/Image"
┣━━━
┗━ ∑ ⚠ Exited with 1 errors reported by nix at 00:08:22 after 6s

Turns out having:
specialArgs = { inherit pkgs lib; };

in the flake causes this to behave like this and overwrites the overlays it seems.
Now I'm getting a libcamera error with pybind11 not found:
libcamera> The Meson build system
libcamera> Version: 1.2.3
libcamera> Source dir: /tmp/nix-build-libcamera-0.1.0.drv-0/source
libcamera> Build dir: /tmp/nix-build-libcamera-0.1.0.drv-0/source/build
libcamera> Build type: native build
libcamera> Project name: libcamera
libcamera> Project version: 0.2.0
libcamera> C compiler for the host machine: gcc (gcc 12.3.0 "gcc (GCC) 12.3.0")
libcamera> C linker for the host machine: gcc ld.bfd 2.40
libcamera> C++ compiler for the host machine: g++ (gcc 12.3.0 "g++ (GCC) 12.3.0")
libcamera> C++ linker for the host machine: g++ ld.bfd 2.40
libcamera> Host machine cpu family: aarch64
libcamera> Host machine cpu: aarch64
libcamera> Header "unistd.h" has symbol "issetugid" : NO
libcamera> Header "locale.h" has symbol "locale_t" : YES
libcamera> Header "stdlib.h" has symbol "secure_getenv" : YES
libcamera> Compiler for C supports arguments -Wno-c99-designator: NO
libcamera> Found pkg-config: /nix/store/abanpwji07p5535gvdkylzw8kssqkfka-pkg-config-wrapper-0.29.2/bin/pkg-config (0.29.2)
libcamera> Run-time dependency lttng-ust found: YES 2.13.6
libcamera> Program ./parser.py found: YES (/tmp/nix-build-libcamera-0.1.0.drv-0/source/utils/ipc/./parser.py)
libcamera> Program ./generate.py found: YES (/tmp/nix-build-libcamera-0.1.0.drv-0/source/utils/ipc/./generate.py)
libcamera> Program ./extract-docs.py found: YES (/tmp/nix-build-libcamera-0.1.0.drv-0/source/utils/ipc/./extract-docs.py)
libcamera> Program ./gen-tp-header.py found: YES (/tmp/nix-build-libcamera-0.1.0.drv-0/source/utils/tracepoints/./gen-tp-header.py)
libcamera> Configuring version.h using configuration
libcamera> Program openssl found: YES (/nix/store/gjc315c1n94aanl0ahy5ar08swpzxh3k-openssl-3.0.13-bin/bin/openssl)
libcamera> Library atomic found: YES
libcamera> Run-time dependency threads found: YES
libcamera> Did not find CMake 'cmake'
libcamera> Found CMake: NO
libcamera> Run-time dependency libdw found: NO (tried pkgconfig and cmake)
libcamera> Run-time dependency libunwind found: NO (tried pkgconfig and cmake)
libcamera> Header "execinfo.h" has symbol "backtrace" : YES
libcamera> Library rt found: YES
libcamera> Run-time dependency libpisp found: YES 1.0.5
libcamera> Checking for function "dlopen" : YES
libcamera> Run-time dependency libudev found: YES 254
libcamera> Run-time dependency yaml-0.1 found: YES 0.2.5
libcamera> Run-time dependency gnutls found: NO (tried pkgconfig and cmake)
libcamera> Run-time dependency libcrypto found: YES 3.0.13
libcamera> Dependency libexif skipped: feature android disabled
libcamera> Dependency libjpeg skipped: feature android disabled
libcamera> Run-time dependency libevent_pthreads found: YES 2.1.12-stable
libcamera> Run-time dependency libtiff-4 found: NO (tried pkgconfig and cmake)
libcamera> Dependency gtest skipped: feature lc-compliance disabled
libcamera> Run-time dependency libdrm found: YES 2.4.118
libcamera> Run-time dependency libjpeg found: NO (tried pkgconfig and cmake)
libcamera> sdl2-config found: NO
libcamera> Run-time dependency sdl2 found: NO (tried pkgconfig, config-tool and cmake)
libcamera> Dependency qt5 (modules: Core, Gui, Widgets) skipped: feature qcam disabled
libcamera> Run-time dependency glib-2.0 found: YES 2.78.4
libcamera> Run-time dependency gstreamer-video-1.0 found: YES 1.22.8
libcamera> Run-time dependency gstreamer-allocators-1.0 found: YES 1.22.8
libcamera> Run-time dependency python3 found: YES 3.11
libcamera> pybind11-config found: NO
libcamera> Run-time dependency pybind11 found: NO (tried pkgconfig and config-tool)
libcamera>
libcamera> src/py/libcamera/meson.build:10:15: ERROR: Dependency "pybind11" not found, tried pkgconfig and config-tool
libcamera>
libcamera> A full log can be found at /tmp/nix-build-libcamera-0.1.0.drv-0/source/build/meson-logs/meson-log.txt
error: builder for '/nix/store/na42rz0zqmqil2ciy1b5sf72hrrba3bv-libcamera-0.1.0.drv' failed with exit code 1
error: 1 dependencies of derivation '/nix/store/ghsq9l3j0fd47qh8ak31l26npr2cgwf9-pipewire-1.0.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/akdsvzykq2c1h4wicyvva5f3q9na6rg8-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/rg5nr2qhhcgb15qi42wcvdjj1daniig4-nixos-system-box-8-24.05.drv' failed to build
python3-3.11.8-env> building '/nix/store/rbys9yqhar66bsiv32fdlgx38v3rmpx1-python3-3.11.8-env.drv'
error: 1 dependencies of derivation '/nix/store/j3pkrxbvh344k28y2vlg2qyc1gc7zxqx-ext4-fs.img.zst.drv' failed to build
error: 1 dependencies of derivation '/nix/store/sicfx4r1hbc5i10dxcnra18iapi7c9p9-nixos-sd-image-24.05-aarch64-linux.img.drv' failed to build


Drop ingress NetworkPolicy rule from seed-prometheus for shoot components

How to categorize this PR?

/area networking security
/kind cleanup
What this PR does / why we need it:
Today, seed-prometheus is allowed to scrape shoot control plane components labeled with networking.gardener.cloud/from-prometheus=allowed. However, there is no scrape target in shoot namespaces for the seed-prometheus. Hence, this rule can be dropped.
Only the aggregate-prometheus talks to Prometheis in shoot namespaces via https://github.com/gardener/gardener/blob/f47324ffb76cd9d923ac172c0959857fa7e85624/charts/seed-bootstrap/templates/aggregate-prometheus/config.yaml#L39-L60
Which issue(s) this PR fixes:
Part of #7352
Special notes for your reviewer:
/cc @istvanballok @rickardsjp
Release note:

NONE

/approve

/test pull-gardener-e2e-kind

/test pull-gardener-e2e-kind


Vet clinic database: add "join table" for visits

Hi there, 👋
In this branch, I added some many-to-many relationships and wrote more complex queries to use them to answer questions.
Here there are the project requirements:

Create a table named vets with the following columns:

id: integer (set it as autoincremented PRIMARY KEY).
name: string.
age: integer.
date_of_graduation: date.

There is a many-to-many relationship between the tables species and vets: a vet can specialize in multiple species, and a species can have multiple vets specialized in it. Create a "join table" called specializations to handle this relationship.

There is a many-to-many relationship between the tables animals and vets: an animal can visit multiple vets and one vet can be visited by multiple animals. Create a "join table" called visits to handle this relationship, it should also keep track of the date of the visit.

Insert the following data for vets:

Vet William Tatcher is 45 years old and graduated Apr 23rd, 2000.
Vet Maisy Smith is 26 years old and graduated Jan 17th, 2019.
Vet Stephanie Mendez is 64 years old and graduated May 4th, 1981.
Vet Jack Harkness is 38 years old and graduated Jun 8th, 2008.

Insert the following data for specialties:

Vet William Tatcher is specialized in Pokemon.
Vet Stephanie Mendez is specialized in Digimon and Pokemon.
Vet Jack Harkness is specialized in Digimon.

Insert the following data for visits:

Agumon visited William Tatcher on May 24th, 2020.
Agumon visited Stephanie Mendez on Jul 22th, 2020.
Gabumon visited Jack Harkness on Feb 2nd, 2021.
Pikachu visited Maisy Smith on Jan 5th, 2020.
Pikachu visited Maisy Smith on Mar 8th, 2020.
Pikachu visited Maisy Smith on May 14th, 2020.
Devimon visited Stephanie Mendez on May 4th, 2021.
Charmander visited Jack Harkness on Feb 24th, 2021.
Plantmon visited Maisy Smith on Dec 21st, 2019.
Plantmon visited William Tatcher on Aug 10th, 2020.
Plantmon visited Maisy Smith on Apr 7th, 2021.
Squirtle visited Stephanie Mendez on Sep 29th, 2019.
Angemon visited Jack Harkness on Oct 3rd, 2020.
Angemon visited Jack Harkness on Nov 4th, 2020.
Boarmon visited Maisy Smith on Jan 24th, 2019.
Boarmon visited Maisy Smith on May 15th, 2019.
Boarmon visited Maisy Smith on Feb 27th, 2020.
Boarmon visited Maisy Smith on Aug 3rd, 2020.
Blossom visited Stephanie Mendez on May 24th, 2020.
Blossom visited William Tatcher on Jan 11th, 2021.

Write queries to answer the following:

Who was the last animal seen by William Tatcher?
How many different animals did Stephanie Mendez see?
List all vets and their specialties, including vets with no specialties.
List all animals that visited Stephanie Mendez between April 1st and August 30th, 2020.
What animal has the most visits to vets?
Who was Maisy Smith's first visit?
Details for most recent visit: animal information, vet information, and date of visit.
How many visits were with a vet that did not specialize in that animal's species?
What specialty should Maisy Smith consider getting? Look for the species she gets the most.

Take a screenshot of the results of your queries.

Thanks for your kind review 👏

Thanks @Omar-Muhamad !


Specify data being presented: what part of the pop-up window is a rate?? Change pop-ups for clarifcation.

After selecting a county, the pop-up window pulls up too much information, and is generally confusing. What is the difference between the Value and the Age-Adj Count? Which number represents the rate? As I look through, it seems that the Value reflects the true rate, so it may be as easy as getting rid of the Age-adj Count label... Example below.

We do not need to include the FIPS number anywhere; this can be removed from the pop-up.

I do like your example where we don't have a county label, so let's move forward with that!
The number currently being presented with the "Value" label is the CORRECT number we want to display. So something like this...
Gunnison County
Incidence (Age-adj per 100k): 109.5
That's all we need to include. The 17 value you have is a count (how many new cases of cancer) vs. the 109.5 is age-adjusted (taking into account the population of that county over a period of time). We only need to include the age-adjusted rate and can get rid of the count altogether. Hope this makes sense.
Thanks!

Summary from meeting on tooltip for cancer stats for counties:
Chaffee County
Rate: 382.4
Avg. Annual Count: 121

For tracts, display "Census Tract ".
For the value field, stats that aren't cancer-related, remain "Value".
Map scale should use incidence rate ("value" internally).


IPv6 address returned from $location.host() does not include the brackets in IE/Edge

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] other

Current behavior:

For example, when the URL is https://[fd12:3456:789a:74::27], $location.host() returns fd12:3456:789a:74::27 in IE/Edge.
This is because host and hostname of a tag element returns the address without bracket, when we use urlParsingNode, and we use it in urlResolve directly:
https://github.com/angular/angular.js/blob/eb0ccc625f27e6ae550f8c5e0186bd99f986e80b/src/ng/urlUtils.js#L75-L86
Expected / new behavior:

$location.host() should return the IPv6 address with the brackets. i.e. [fd12:3456:789a:74::27]
Minimal reproduction of the problem with instructions:

Call $location.host() at a IPv6 address using IE/Edge
AngularJS version: 1.7.4

Browser: [ Edge 42.17134.1.0 | IE 11.228.17134.0 ]

Anything else:

I suggest that we can check if the address is in IPv6 format, and add brackets to it if it doesn't exist. Not necessary to check if it's IE/Edge.

Thanks for the report, I confirm the issue. This is an IE/Edge bug, EdgeHTML 17 still has it but it's fixed in the Edge preview (future 18), see https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16476907/

PR: #16715

great!


Prevent duplicate routes in compile time

Fixes #135 . I haven't figured out how to write the test though, any help?

@Abogical looks good to me. It also does seem like you got a test. I'm happy to merge if you are (still have WIP in the title).

The test just doesn't work that's why I'm putting it in WIP. testing it outside the crate with impl_web! macro works, but directly calling the function expand_derive_resource doesn't. I'm not familiar with the codebase as you are. What am I missing?

Also travis doesn't test the macros, I've opened a new issue. (#197)

Test is fixed now. You can merge.

Was this technically a breaking change?

unsure... the original behavior was not defined.

Undefined as in UB, or undefined as in "happened to pick one of the handlers"? If the latter, it sounds like a breaking change, not that I have anything against it.

happened to pick one of the handlers.
I did not consider the breaking change aspect. At this point, i would leave it unless there is a report.


Annotated default-returning methods

Allow @DefaultValue to apply to methods, in which case the method will produce a default value. Flexible signatures can be supported with the new annotated method system.
This would be merged after #598.
@DefaultValue("name")
public @NonNull ArgumentParseResult<YourValue> defaultValue(
  final @NonNull CommandContext<YourSenderType> context
) {
  // logic...
  return theValue;
}

then in the method, @DefaultValue(provider = "name")
We'd have to make the value of @DefaultValue default to "", which should be fine. We need a small class for housing the name-provider mappings.

Should probably also get the "context" of what parameter this is for, so in something like:
@CommandMethod("/stuff [a]")
public void doStuff(@DefaultValue("name") @Default("A") Something a) {...}

@CommandMethod("/stuff2 [b]")
public void doStuff(@DefaultValue("name") @Default("B") Something b) {...}

you'd be able to check for the default annotation value and do stuff different based on which is used, or maybe custom annotations too

I think a better implementation of this would be to have the method return a DefaultValue instance, as this means that you can then choose to map annotations to parsed default values, constants or dynamic values. The method will have access to the parameter that it's creating the instance for, alongside the annotations.


remove check that prohibits frames being ranked and range enabled

Overview
I don't think there is any reason for frames not have both a ranked cache, and range fields.
Having this ability makes generic ingest a bit easier to implement.
Fixes #
Pull request checklist

[ ] I have read the contributing guide.
[ ] I have agreed to the Contributor License Agreement.
[ ] I have updated the documentation.
[ ] I have resolved any merge conflicts.
[ ] I have included tests that cover my changes.
[ ] All new and existing tests pass.

Code review checklist
This is the checklist that the reviewer will follow while reviewing your pull request. You do not need to do anything with this checklist, but be aware of what the reviewer will be looking for.

[ ] Ensure that any changes to external docs have been included in this pull request.
[ ] If the changes require that minor/major versions need to be updated, tag the PR appropriately.
[ ] Ensure the new code is properly commented and follows Idiomatic Go.
[ ] Check that tests have been written and that they cover the new functionality.
[ ] Run tests and ensure they pass.
[ ] Build and run the code, performing any applicable integration testing.

@jaffee I didn't realize you had done this and I implemented this change on the cluster-resize branch. Currently, it's in this commit in a PR for that branch.
In addition to your changes, I also prevented the view from writing a cache file for Field views.
I can approve this PR if you need this on master now, just let me know.

I also adjusted the test to match yours: https://github.com/pilosa/pilosa/pull/935/commits/fee1b5583888263d2a990b1ba84a947c4b1c879a

well, I'm hoping to get approval to merge the PDK PR in the next day or two, so if cluster-resize is further out than that, it would be helpful to get this merged ahead of it

this is in the cluster resize branch, so closing in favor of that


Update documents related to crd and post_check

What this PR does / why we need it:
Special notes for your reviewer:
Does this PR introduce a user-facing change?

LGTM


Automate helm chart artifacts reference publish on release

Is this the right place to submit this?

[X] This is not a question about how to use the sail-operator

Feature Description
As per now, Sail Operator helm charts could be installed by using helm repo add helm-sail-operator https://istio-ecosystem.github.io/sail-operator/ flow without a need to clone the repository.
In gh-pages branch, an "index.yaml" file holds a reference to the helm artifact attached to a release asset.
The next step is to automate "index.yaml" file update during each release, so it will always contain the reference to the new helm artifact version.
Additional Information
No response

@dgn @bmangoen
Hi Daniel, Brian,
Could you share your opinion on the following, please?
Please, read the issue description for the context.
I would like to add an automation flow to release github action, so the "index.yaml" file will be updated with each new helm artifact release.
Since, we would like to keep the identical sha hash of the helm artifact archive, I thought to add the following flow:

Once the gh release is published, download the artifact from the release assets.
Run helm command to update the "index.yaml" file, which will generate a metadata and provide a link to the assets archive of helm artifact.
Push the "index.yaml" file to gh-pages branch to update it.

Everything sound pretty simple.
But there is one issue that could complex it.
I saw that the release workflow has, by default, a parameter of "draft", which performs the release as draft and not publishing it until manual approval.
The problem with it comes with the artifact link which is temporary and unusable.
For example:
Release assets link for helm artifact looks like that:
https://github.com/istio-ecosystem/sail-operator/releases/download/0.1.0/sail-operator-0.1.0.tgz
But a link of the draft release, looks like that:
https://github.com/istio-ecosystem/sail-operator/releases/download/untagged-f0cb177e5849ddd3fa8f/sail-operator-0.1.1.tgz
So, it means that until the release will not be published, I can't really know or presume the assets link, so I can't use it for both download the assets artifact or reference it within the "index.yaml" file.
Of course I can do the workflow separate from the release workflow, but I would like to find a way to make less manual work, by triggering two separate workflows.
So, my questions are:

Are we planning to create each release as draft release first?
Maybe we could create some condition that waits for the release to be published and then it will move to publish the helm artifact.
Or maybe you're ok with having two separate workflows?

Appreciate your thoughts on that.
Thanks.

Hey,
I think we made the draft release the default to avoid creating releases accidentally.
I guess we only manually promoted from a draft to a release for the first release Sail Operator 0.1.0-rc.1 but the next ones shouldn't be released as a draft.
@dgn how did you do for Sail Operator 0.1.0 ?

Or maybe you're ok with having two separate workflows?

I'm not against having another workflow which could be triggered when a release is published.

If we can have a workflow that is triggered by the actual creation of publishing of a release, which then goes and updates the index.yaml, that'll work for me. It might make sense to create a PR with the change instead of pushing directly, which would e.g. give us the option to later add a test (which e.g. verifies that all URLs in index.yaml are indeed reachable). Even if we create a PR, we can configure CI so that it's merged automatically after all tests have passed.

@bmangoen @dgn
Thanks for your response.

If we can have a workflow that is triggered by the actual creation and publishing of a release, which then goes and updates the index.yaml, that'll work for me.

As I mentioned above, that will work if the release will be published right away and not created as draft.
Otherwise, it will not be able to fetch the url for the artifact.
Let's do the following.
I'll start working on a separate workflow to update the index.yaml file according to the published release.
And once we will see that our release is stable and do not need to be created as draft, I'll merge that new workflow into the release workflow.
Will it work for you?

Yeah, I think a separate workflow is fine. IIUC, we can have it be triggered by the publishing of the release, no need to change the existing workflow.

That's a good idea, to trigger by publish.
Will check it.
Thanks.


TypeError when parsing JSON, caused by httplib2/Python3 returning 'bytes' object instead of a string.

Hi.
I'm now trying to develop software on top of hp3pardata API, and noticed it won't work with Python3.
Even the following simplest code fails with a TypeError:
#!/usr/bin/python
# -*- coding: utf-8 -*-
import hp3parclient
from hp3parclient.client import *
cl = HP3ParClient("http://<IP_ADDRESS>:8008/api/v1")

The root cause was that httplib2.request() method now returns a 'bytes' object instead of a 'string' due to a change in Python3 (I'm using Python 3.3). This broke JSON parser when 'bytes' object is passed.
Quick fix is to turn HTTP response body back into string as I posted in https://github.com/hp-storage/python-3parclient/pull/11 .
Best Regards,

Your fix has been merged in bdf337a8509f9d4f672a401119b4079399e37c4b
Thank you.


Calling https but getting http schema

Hi,
I've a strange issue running Kestrel with HTTPS.
It seems the schema is always http also if I call the endpoint using https.

Any hint?
For reference: https://github.com/IdentityServer/IdentityServer3/issues/2357

Are you hitting Kestrel directly or are you running behind a reverse proxy?? Maybe using IISPlatformHandler?

Running directly from VS2015 Update1.
app.UseIISPlatformHandler(); is comment out

Running directly from VS2015 Update1.

Does that mean using IIS Express?

Nope, running web command from play button in VS.
Same problem using command line (dnx web)

Fixed in RC2: https://github.com/aspnet/KestrelHttpServer/issues/365

Thx,
I'll use this workaround in the meanwhile


Proxy support

Based on discussions int he internal ALM Champs channels:
It would be lovely if the SDK and the Agent would work together to expose web proxy information that is important for that agent. This allows task developers to correctly pass that information to the tools they execute or set the required environment variables.
My idea would be that it'd be possible to configure a Service Endpoint with the proxy URL and credentials. Then have the ability to set the default proxy endpoint at the agent level in the UI or in the agent when installing it. The VSTS-Task-Lib could then give us access to the endpoint through a well known service endpont (akin to the VSSServiceEndpoint, like VSSProxyEndpoint).
I understand this must go hand-in hand with the agent itself, so I'll post a similar issues in both repositories.
Related VSTS-Task-Lib issue: https://github.com/Microsoft/vsts-agent/issues/1078

We already started support in the lib.
https://github.com/Microsoft/vsts-task-lib/pull/268
It's not going to be a service endpoint.  It's configured via agent config as it's an agent concern.

Proxy support is complete.  As mentioned above, it's an agent config option.  If you use the task lib, there's methods to get the configured proxy info if you need to pass it on to other tools


Expand on the impartiality of the response team

This edit extracts and improves on impartiality clause as recommended in #31.
It would be nice if wording and construction of the sentence could be reviewed by a native English speaker.

Resonably and concicely addresses my isuue. I'm in favour.
I see no issues with the wording, it is professional and to the point.


sgx: stop using local source hooks for EPC registration

Fixes: #1380

Codecov Report

Merging #1392 (df37ec0) into main (3744e09) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head df37ec0 differs from pull request most recent head 2034b9d. Consider uploading reports for the commit 2034b9d to get more accurate results

@@           Coverage Diff           @@
##             main    #1392   +/-   ##
=======================================
  Coverage   50.89%   50.89%
=======================================
  Files          44       44
  Lines        4985     4985
=======================================
  Hits         2537     2537
  Misses       2302     2302
  Partials      146      146

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

Should we keep building the initcontainer?

initcontainer can also be used without NFD so that needs to stay. I'm also keeping the existing behaviour in the operator if someone wants it.

@hj-johannes-lee PTAL and merge if ok


Feature: Add lottery factor pill to OG image for a repository page

As a user of OpenSauced, I want to enhance the shareable OG image with the lottery factor pill so that I can quickly indicate in my shared link the lottery factor of that particular repository for the given day range.

Not much to design here probably @isabensusan, just curious about the placement of the lottery factor pill.


kubernete ingress support header rule annotation

Do you want to request a feature or report a bug?
Feature
I can't found any annotation to set header rule , please add  header rule annotation to allow header rule route.
What did you expect to see?
the annotation could be like  ingress.kubernetes.io/rule-header: Content-Type, application/json

Hello @xuzhiop,
Unfortunately the kubenetes ingress spec does not have any allowance for custom header based routing.
https://kubernetes.io/docs/concepts/services-networking/ingress/#the-ingress-resource
If you require header based routing, you can do so using the file provider, and use service IPs as backend URLs. Note that this will  incurr an extra hop, as the service IP will be routed.
If you feel that header based routing should be part of the ingress spec, You would have to open a feature request with kubernetes, as that has to come from upstream.
You are not alone in wanting that feature as seen here (https://github.com/kubernetes/ingress-nginx/issues/2419).
If header based routing does become part of the ingress spec, we will support it completely.
Thanks!

Hello @dtomcej
Thanks for your reply
But I don't think  ingress spec can block my request.  why not set header rule by ingress annotation (not ingress spec)
Scenario is below:
We deploy two deployments for one application , One for production , one for gray test . In my idea, we want to rout request to application (both two deployments ) based on  host, and route to deployment based on header (we can set a special header to label gray user ) . In real network, it should be two  route, one to production deployment, one to gray deployment . And both routes should have header rule and host rule . If traefik can support header based routing with ingress annotation like  "traefik.ingress.kubernetes.io/rule-header: grayTag, gray" ,  I can carry out my idea convinently.

+1

The feature is published as part of version 0.21.0: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#canary
I've written a blog post https://www.elvinefendi.com/2018/11/25/canary-deployment-with-ingress-nginx.html showing how to use it with examples.

https://github.com/kubernetes/ingress-nginx/issues/2419#issuecomment-441613125

+1 on this, would be great to have support for header rules as annotations

If I use JavaScript to send an AJAX request to the backend server.
There is no Host Header in this AJAX request,
How do I route this AJAX request to the right microservice in my K8S cluster?


Import/qualify trait Deref suggesting lazy_static::__Deref instead of std::ops::Deref

The code action to import/qualify a trait suggests lazy_static::__Deref instead of std::ops::Deref for just the name Deref.
To reproduce:

Add lazy_static v1.4.0 to the Cargo.toml (Not sure if this happens on other versions)
Create an impl block impl Deref for Foo.
Press alt-period or whatever code action shortcut is set up while the cursor is over the Deref in the impl Deref for Foo block.
lazy_static::__Deref is suggested instead of std::ops::Deref.

Information:
IDE: VSCode
Plugin: matklad.rust-analyzer v0.2.621
rust-analyzer version: rust-analyzer 28e32fe40 2021-05-31 stable
Rust: 1.52.1

CC #9113

The problem here is that lazy_static reexports Deref with a doc hidden. We should ideally honor the #[doc(hidden)] attribute unless its hidden in the same crate we are importing from.
Minimal test case for autoimport that imports __Deref:
//- /main.rs crate:main deps:std,lazy_static
impl Deref$0 for () {}
//- /lazy_static.rs crate:lazy_static deps:core
#[doc(hidden)]
pub use core::ops::Deref as __Deref;
//- /std.rs crate:std deps:core
pub use core::ops;
//- /core.rs crate:core
pub mod ops {
    pub trait Deref {}
}