Why is the training not starting when using my own dataset?

Hello, I have modified the training.yaml file to run on my own dataset. The modifications are as follows:
`name: "my_training_pipeline"
model:
target: ragfoundry.models.hf.HFTrain
model_name_or_path: "microsoft/Phi-3-mini-128k-instruct"
load_in_4bit: false
load_in_8bit: true
torch_dtype:  # Can be set to "float16" or "bfloat16", if needed
device_map: "auto"  # Automatically assign devices, or specify specific devices
trust_remote_code: true
lora:
bias: none
fan_in_fan_out: false
layers_pattern:
layers_to_transform:
lora_alpha: 16
lora_dropout: 0.1
peft_type: LORA
r: 16
target_modules:
- qkv_proj
task_type: CAUSAL_LM
use_rslora: true
completion_start:
instruction_in_prompt:
max_sequence_len: 4000
train:
output_dir: ./rag/RAGFoundry-main/models/finetuned_model
bf16: false
fp16: false
gradient_accumulation_steps: 4
group_by_length: false  # Enable length grouping if needed
learning_rate: 2e-5
logging_steps: 10
lr_scheduler_type: cosine
max_steps: -1  # -1 means using num_train_epochs
num_train_epochs: 3
per_device_train_batch_size: 8
per_device_eval_batch_size: 8  # Batch size for validation set
optim: adamw_torch_fused
remove_unused_columns: true
save_steps: 20000
save_total_limit: 2
warmup_ratio: 0.03
weight_decay: 0.001
report_to: wandb  # Use wandb for logging if needed
validation:
data_file: mypath/procedure_dev.jsonl
eval_steps: 1000  # Evaluate every 1000 steps
max_eval_samples: 1000  # Maximum number of validation samples
instruction: ragfoundry/processing/prompts/prompt_instructions/qa.txt
template:                       # specify a template file or use chatML format with tokenizer's chat template
data_file: mypath/procedure_train.jsonl
input_key: text1  # Assuming the input key in the data is text1
output_key: labels  # Assuming the output key in the data is labels
resume_checkpoint:
limit:
shuffle: true  # Shuffle the dataset
use_wandb: false  # Set to false if not using wandb
hfhub_tag:
experiment: phi-training
wandb_entity:
logging:
level: DEBUG  # Ensure all logs are captured
handlers:
- stream  # Output to console only
My dataset is formatted as follows:{"text1": "FIN6 has used Windows Credential Editor for credential dumping.", "labels": ["T1003.001"]}
{"text1": "Ke3chang has dumped credentials, including by using Mimikatz.", "labels": ["T1003.001"]}
When I run the command python processing.py -cp configs/path -cn train, the output is:input_key: text1
output_key: labels
resume_checkpoint: null
limit: null
shuffle: true
use_wandb: false
hfhub_tag: null
experiment: phi-training
wandb_entity: null
logging:
level: DEBUG
handlers:

stream
[2024-08-11 23:11:47,629][root][INFO] - Caching state: True
0it [00:00, ?it/s]
`
It seems like the training did not start.

If you want training, you need the training.py module, not processing.py.

Thank you very much, I'll give it a try.


remove the Django>=1.7 dependency in setup.py

Obviously only if the package actually works with Django 1.6.
The reason being that we maintain a package that still supports Django 1.6 (django-cms 3.2.x). So for 1.7+ we add a dependency to django-formtools. Unfortunately it is not possible to conditionally install a dependency, only if a certain version of a other package is present. So even if our package is used in a Django 1.6.x Project we still have to install django-formtools. This is especially a problem with strict dependency checkers like pip-tools.
Thus we'd like to use django-formtools for Django 1.6.x, even if we could also use the builtin version.

Sorry, but I don't think we're going to spend any time testing the package with Django 1.6 which is obsolete by now.


The getter 'articles' was called on null.

There is a relatively low probability that this error will occur.

Solution, maybe you can try to add a simple judgment.

@tenSunFree Thank you, I'll check that.

@tenSunFree
Thank you 😃


fix(react): ImageCard captions and sizes

Pull Request Test Coverage Report for Build 413246312

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 73.106%

Totals

Change from base Build 412710177:
0.03%

Covered Lines:
1597

Relevant Lines:
1983

💛  - Coveralls


"Chiclet" space

The following changes should be made to the search terms part of the display
[ ] We need to have a title above the chicklets so the user knows what they are looking at.  I suggest something like "Current Attribute Filter Terms" or something like that.  The font of this should be consistent with other header fonts on the page.
[ ] The "Reset Search" button should be moved to be by the chiclets and taken out of the sidebar

I currently have the title as "Selected Attributes" and wrapped with a <h3>. Not sure if this considered consistent with other header fonts, but I made it an h3 in the hopes that the larger size will grab users' attentions more quickly and differentiate it from the surrounding text. @crisaless can weigh in?

I don't think it needs to be that attention-getting. A <4> tag might be sufficient.  I also think it should be called "Selected by:"

Okay here's "Selected by" in h4

I think this looks good.
I like the “Save Search” button.
Carl
On Oct 5, 2015, at 3:10 PM, Jessie Wong <notifications<EMAIL_ADDRESS>wrote:
Okay here's "Selected by" in h4
[screen shot 2015-10-05 at 3 09 35 pm]https://cloud.githubusercontent.com/assets/4585431/10295113/200a20b8-6b73-11e5-9276-2855ea9a4029.png
—
Reply to this email directly or view it on GitHubhttps://github.com/informatics-isi-edu/chaise/issues/98#issuecomment-145684349.

It still looks too big. I think it should look like 'Search within' - but at this point, let me fool around with it. I might need to add a style.

Good point.  That would be better.
Are we happy with the way the clear attributes button looks and placement?
Carl
On Oct 5, 2015, at 3:14 PM, Cris Williams <notifications<EMAIL_ADDRESS>wrote:
It still looks too big. I think it should look like 'Search within' - but at this point, let me fool around with it. I might need to add a style.
—
Reply to this email directly or view it on GitHubhttps://github.com/informatics-isi-edu/chaise/issues/98#issuecomment-145685097.

Jessie, try using this p tag for Selected by:

Carl, In my head I was thinking the Clear All could have a background color the same as the close icon (#fc868d) and white font - but it's a long button to use such an imperative color. Maybe if you shorten the text to just say "Clear All"
Another way to go is to make the "Clear..." text italicized...

github scrubbed the markup. I was going to suggest using a p tag with the class "filter-item-field" for the "Selected by:" heading.

@crisaless Here's "Selected by" with .filter-item-field. Doesn't it look a little too subtle?

Here it is surrounded by <strong> tags:

@crisaless Also, to make GitHub not scrub out your code, you can try surrounding your code with a pair of ` (that accent mark thing)


Git icons to find them easilly

I usually have 5+ git repos open on the sidebar and it can be a bit hard to find what I want. It's not really hard but if it was able to add some color or icon to mark repos it might be easier to find them. Something like color -> yellow, etc would place a yellow circle left to the name.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Update drag-and-drop.md

iOS 15 now support cross-app drag and drop.
Reference to the change
https://developer.apple.com/documentation/uikit/drag_and_drop

@carlh98 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Export point clouds from nerfacto in the real size of the objects

Is it possible to export point clouds from NeRfs which where trained with the nerfacto method in the real size of the objects?
I want to use the point clouds to compare a digital model and the real object by comparing their point clouds via ICP-algorithms. At the moment the exported point clouds haven´t the real size of the objects which makes a comparison of the models difficult. If I scale the exported point cloud from the NeRF manually it get´s too inaccurate for a comparison with the digital model.

I think they should be. Is there any way to check it?
The problem appears when I use COLMAP for the camera pose estimation and also with polycam and an Ipad pro with LIDAR-Scanner. Also the sizes of the trained NeRfs is different each time and there is no constant scale I have to apply to get the real measurements of the objects.

Yes it is better to use the polycam app with depth data. Okay so, the problem with COLMAP is that it will never give you metrically correct poses, they are only relatively correct up to a scaling factor. So they are not in the same coordinate system as your captured object and hence the scale will be off. But I think if you use polycam, it will use the depth data so solve for the scale ambiquity and the poses will be metrically correct. Problem now is that when you use nerfacto, it will squeeze all your poses to a -1,1 unit box due to various reasons. After training the nerf and exporting the pointcloud, you need to invert this transformation on your poses. The transformation matrix is stored in a file called "dataparse_transforms.json" and is found in the same folder as your model config.yml file is. So just apply the inverse of this transform to your point cloud and it should be metrically back to the coordinate frame of you poses, that is, if your poses are in the correct scale to begin with. Many similar issues have been made regarding this topic here, and here.


[coc.nvim] a lot of nvim process is created when using the autocompletion of coc.nvim

Problems summary
A lot of nvim process is created when using the autocompletion of coc.nvim. These processes are not terminated even after quiting neovim. Have to run something like killall -9 nvim to terminate.
Environment Information

OS: macOS Mojave 10.14.6

neovim :version output:

NVIM v0.4.0-dev
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/mac/super/clang -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNDEBUG -DMIN_LOG_LEVEL=3
-Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallth
rough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -
DNVIM_UNIBI_HAS_VAR_FROM -I/tmp/neovim-20190817-9852-m0h2e8/build/config -I/tmp/neovim-20190817-9852-m0h2e8/src -I/usr/local/include -I/t
mp/neovim-20190817-9852-m0h2e8/deps-build/include -I/usr/local/opt/gettext/include -I/Users/nasen/Applications/Xcode-beta.app/Contents/De
veloper/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include -I/tmp/neovim-20190817-9852-m0h2e8/build/src/nvim/auto -I/tm
p/neovim-20190817-9852-m0h2e8/build/include
编译者 nasen@overwatch

Features: +acl +iconv +tui
See ":help feature-compile"

     系统 vimrc 文件: "$VIM/sysinit.vim"
         $VIM 预设值: "/usr/local/Cellar/neovim/HEAD-e56f62e/share/nvim"

:checkhealth or :CheckHealth result(neovim only):

health#coc#check
========================================================================
  - OK: Environment check passed

  - OK: Javascript bundle found
  - OK: Service started

health#coc#check
========================================================================
  - OK: Environment check passed

  - OK: Javascript bundle found
  - OK: Service started

health#coc#check
========================================================================
  - OK: Environment check passed

  - OK: Javascript bundle found
  - OK: Service started

health#coc#check
========================================================================
  - OK: Environment check passed

  - OK: Javascript bundle found
  - OK: Service started

health#coc#check
========================================================================
  - OK: Environment check passed

  - OK: Javascript bundle found
  - OK: Service started

health#mkdp#check
========================================================================
  - INFO: Platform: macos
  - INFO: Nvim Version: NVIM v0.4.0-dev
  - INFO: Pre build: /Users/nasen/.cache/vim/dein/repos/github.com/iamcco/markdown-preview.nvim/app/bin/markdown-preview-macos
  - INFO: Pre build version: 0.0.9
  - OK: Using pre build

health#nvim#check
========================================================================
## Configuration
  - OK: no issues found

## Performance
  - OK: Build type: Release

## Remote Plugins
  - OK: Up to date

## terminal
  - INFO: key_backspace (kbs) terminfo entry: key_backspace=^H
  - INFO: key_dc (kdch1) terminfo entry: key_dc=\E[3~
  - INFO: $TERM_PROGRAM='iTerm.app'
  - INFO: $COLORTERM='truecolor'

health#provider#check
========================================================================
## Clipboard (optional)
  - OK: Clipboard tool found: macOS-clipboard

## Python 2 provider (optional)
  - WARNING: No Python executable found that can `import neovim`. Using the first available executable for diagnostics.
  - ERROR: Python provider error:
    - ADVICE:
      - provider/pythonx: Could not load Python 2:
          /usr/local/bin/python2 does not have the "neovim" module. :help |provider-python|
          /usr/local/bin/python2.7 does not have the "neovim" module. :help |provider-python|
          python2.6 not found in search path or not executable.
          /usr/local/bin/python does not have the "neovim" module. :help |provider-python|
  - INFO: Executable: Not found

## Python 3 provider (optional)
  - INFO: `g:python3_host_prog` is not set.  Searching for python3 in the environment.
  - INFO: Executable: /usr/local/bin/python3
  - INFO: Python version: 3.7.4
  - INFO: pynvim version: 0.3.2
  - OK: Latest pynvim is installed.

## Ruby provider (optional)
  - INFO: Ruby: ruby 2.3.7p456 (2018-03-28 revision 63024) [universal.x86_64-darwin18]
  - WARNING: `neovim-ruby-host` not found.
    - ADVICE:
      - Run `gem install neovim` to ensure the neovim RubyGem is installed.
      - Run `gem environment` to ensure the gem bin directory is in $PATH.
      - If you are using rvm/rbenv/chruby, try "rehashing".
      - See :help |g:ruby_host_prog| for non-standard gem installations.

## Node.js provider (optional)
  - INFO: Node.js: v12.8.1
  - WARNING: Missing "neovim" npm (or yarn) package.
    - ADVICE:
      - Run in shell: npm install -g neovim
      - Run in shell (if you use yarn): yarn global add neovim

How to reproduce the problem from neovim startup (Required!)
Open neovim and activity monitor. In the empty buffer, type something that would trigger the autocompletion of coc.nvim, hit enter. You will see several nvim process is created.
Screenshot (if possible)

I haven't quite figure out why, but I think it's related to etc#init().

thanks for your report. i want know the issue is problem with coc or thinkvim? if the minial config cant reproduce,maybe something broken in latest thinkvim。

@nasen23  fixed


Seperate starting Airflow scheduler from starting Airflow UI in homepage example

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2040
Originally created by @DouweM on 2020-05-15 19:32:16

View 2 previous comments from the original issue on GitLab


Fix description and screenshot in README [skip-ci]

This change is

Pull Request Test Coverage Report for Build 49

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.333%

Totals

Change from base Build 47:
0.0%

Covered Lines:
11

Relevant Lines:
11

💛  - Coveralls


stm32h7 i2s support

Currently I2S is supported for some STM32:s but not for H7.
I figured the difference between F4 and H7 can't be THAT significant, so I considered porting it but with my somewhat limited experience with the low-level ST HAL, it's proven difficult.
From what I can tell, there are some differences that makes the current driver incompatible. After hacking in the (hopefully correct) clock source, I was left with:
undefined reference to `LL_I2S_DisableIT_ERR'
undefined reference to `LL_I2S_EnableIT_ERR'
undefined reference to `LL_SPI_DMA_GetRegAddr'
undefined reference to `LL_RCC_PLL_GetMainSource'
undefined reference to `LL_RCC_SetI2SClockSource'

DisableIT_ERR seems to not be implemented, despite a macro being available (__HAL_I2S_DISABLE_IT(__HANDLE__, __INTERRUPT__)  from stm32h7xx_hal_i2s.h)
GetRegAddr seems to not exist because there are now separate buffers for RX and TX (if I'm reading the HAL headers correctly)
The RCC stuff seems to be due to clock being configured slightly differently

All in all, it seems hard to imagine that support for H7 would be all that tricky... I'd absolutely be willing to give it a try, but I wanted to throw the question out there first - is anyone else working on this? Are there any pitfalls to know about (I recall reading something about certain restrictions on which RAM regions that are usable for DMA for instance)? Any helpful advice in general? :D

About providing series abstraction, you can look at what was done on spi_stm32, which is somewhat close to I2S:
https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/spi/spi_ll_stm32.h#L130-145
About the RCC stuff, I suggest to first convert i2s driver to use new device tree alternate clock source to simplify the source clk selection: https://github.com/zephyrproject-rtos/zephyr/pull/45053

I have done this and it works great, however very sadly I'm not able to contribute to Zephyr about this or share any code because employment policy states all code I produce on the clock belongs to the company. But I can share a few insights I made. Please note my diff I'm looking at is quite outdated so maybe the current state of the existing driver is slightly different

You have to use DCACHE, for me the existing outcommented macro definitions for __DCACHE_PRESENT=1 worked
LL_RCC_SetI2SClockSource is LL_RCC_SetSPIClockSource
I didn't use the CONFIG_I2S_STM32_USE_PLLI2S_ENABLE, you can and need to get the in clock frequency from HAL_RCCEx_GetPeriphCLKFreq
instead of LL_SPI_DMA_GetRegAddr use &(cfg->i2s->TXDR)
in i2s_stm32_isr you have to explicitly clear the UDR flag using if (LL_I2S_IsActiveFlag_UDR) and corresponding clear function
LL_I2S_EnableIT_ERR doesn't exist, just enable the errors OVR, UDR and FRE using their respectively clear functions
Above also for disable
I don't remember why but in the config struct there's .i2s_clk_sel, which I hard-coded to LL_RCC_SPI123_CLKSOURCE_PLL1Q

In addition, the DMA works differently, a DMAMUX1 and DMA1 must be instantiated and a reference to the DMAMUX1 must be inserted into the "dmas" property of the i2s1 node in the dts with appropriate line numbers. Also note that in your code that feeds the i2s api (i2s_write and such) you have to clean the dcache buffer of the samples and align them to the MCU's dcache boundary.
I think I got all of it, good luck and please ask questions if you run into problems.

Hello,
Is there any update on this? I am looking to use the i2s on stm32h753. I am getting the same errors as mentioned by @endian-benjamin. Any pointers will be very helpful.
Thanks


Update batching dimension comment.

What does this PR do?
Clarify description in line with tensors documentation style.
Checklist

[x] This PR fixes a minor issue (e.g.: typo or small bug) or improves the docs (you can dismiss the other
checks if that's the case).
[ ] This change is discussed in a Github issue/
discussion (please add a
link).
[ ] The documentation and docstrings adhere to the
documentation guidelines.
[ ] This change includes necessary high-coverage tests.
(No quality testing = no merge!)

Codecov Report

Merging #1775 (2ccc44d) into main (fb4f2a4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1775   +/-   ##
=======================================
  Coverage   83.38%   83.38%
=======================================
  Files          69       69
  Lines        5928     5928
=======================================
  Hits         4943     4943
  Misses        985      985

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 fb4f2a4...2ccc44d. Read the comment docs.

@melissatan - this is marked as a "draft" PR - is there anything else you want to add to it?

apologies, i'd created it while testing out the PR functionality on the github UI and didn't know all the maintainers would be notified :) it's still a draft intentionally. i don't mind sending it through as-is, but since i'm still unfamiliar with the github workflow, i'll come back to this next week when i have the dedicated time, if that's ok?
but if it's clogging up some pipeline then i'll deal with it immediately, please let me know :) thanks!

@melissatan  - no worries!  Just take your name, it's no trouble at all to leave it open until you're ready - I was just checking.


Deprecate SPI related to internal compactions

Functionality related to internal compactions will be removed.  The methods and types related to this in the SPI could be deprecated in 3.0 after its know what will be removed from the SPI

As part of this work, the configuration of the default planner will need to be updated as mentioned in a comment on #3460

Also need to remove the concept of internal compactions from the SPI in elasticity branch.

@keith-turner I can work on this as prep step for #3565 and #3547 as it would cleanup the remaining code that needs to be modified.


Easier variable debugging?

For debugging purposes, I want to be able to echo every defined just variable. Is there an easier/saner way than manually writing a long sequence of @echo FOO={{FOO}} for each variable?
It would be nice if there were a flag or something for printing all variable assignments.

oops. I just saw the --evaluate flag


Encoding of variable length fields in structs.

See:
https://stackblitz.com/edit/typescript-nypqgy?file=index.ts

:thinking: I'm pretty sure that there is nothing wrong with the encoding of dynamic fields on tuples/structs.
There are different kinds of tests that ensure that this is working correctly, according to the specs. I know that b/c this wasn't always the case and I had to make a couple of fixes in the past :sweat_smile: .
But then: what's the deal with the stackblitz example? Well, those 2 snippets of code are not equivalent. These are.
Can you notice that on the AbiCoder.prototype.encode function of ethers, the second argument must always be an Array? That's because that function implicitly wraps everything on a tuple. Why would they choose to do that is beyond me, but the thing is that what it's being actually encoded/decoded is in fact: tuple(tuple(address base, address quote, uint openQuantity, address spender, address dex, bytes swapBytes)).
Perhaps there is a bug in the solidity-bindings package, b/c there is some magic that it's done in there in order to encode/decode parameters on function arguments, so that the user doesn't have to define explicit tuples on every function... So, I'm not saying that there isn't a bug related to dynamic fields. I'm just saying that this is not a bug on the encoders.


QPack: Incorrect mapping of relative indices to absolute indices in field line representations

Relative dynamic table entry indices in field line representations are mapped to absolute indices values according to the following statement from RFC 9204 Section 3.2.5 "Relative Indexing":

In a field line representation, a relative index of 0 refers to the entry with absolute index equal to Base - 1.

The usages of QpackDecoderDynamicTable::getEntryRelativeEncodedField in QpackDecoder need to be fixed to use the correct index mapping, eg calculate absolute index with base - idx - 1 instead of base - idx.
Same issue needs to be fixed on the QpackEncoder side, when encoding indexed field lines, and literal field lines with name reference.

@AlekseiEfimov want to do a PR ? Good catch!

@AlekseiEfimov ping

@normanmaurer
Sorry for not getting back to you sooner. Regarding the PR: I'm not planning to work on it - just wanted to report the issue.

@AlekseiEfimov can you have a look at https://github.com/netty/netty-incubator-codec-http3/pull/250 ? I think this should fix it.

The fix looks right to me.


WIP: Bundle CCCL v2.1.0

Close #6700.
As per @jrhemstad we expect CCCL v2.2.0 to be tagged soon-ish, but it's not a blocker for this migration 🙂 For now I manually assemble the cupy/cccl directory with the three components (thrust/cub/libcudacxx) at v2.1.0, and it'd be easy to update the git submodules later once v2.2.0 is out.

/test mini

TODO: Modify include paths fed to NVRTC at run time.

Working on a CUB patch so that it's NVRTC-compilable: https://github.com/NVIDIA/cccl/pull/412

/test all

@kmaehashi Am I actually waiting in the CI queue, or somehow I don't have permission to launch all jobs? 🤔

:eyes: https://github.com/cupy/cupy/actions/runs/6123693803/job/16622120429#step:6:1
To launch all tests, you need to say:
/test full

ahhh silly me... thanks!

/test full

I am clueless why the Windows CIs would fail at build time...
copying cupy\_core\include\cupy\cccl\libcudacxx\libcxx\test\std\experimental\memory\memory.polymorphic.allocator.class\memory.polymorphic.allocator.mem\construct_pair_const_lvalue_pair.pass.cpp -> build\lib.win-amd64-cpython-39\cupy\_core\include\cupy\cccl\libcudacxx\libcxx\test\std\experimental\memory\memory.polymorphic.allocator.class\memory.polymorphic.allocator.mem
error: could not create 'build\lib.win-amd64-cpython-39\cupy\_core\include\cupy\cccl\libcudacxx\libcxx\test\std\experimental\memory\memory.polymorphic.allocator.class\memory.polymorphic.allocator.mem\construct_pair_const_lvalue_pair.pass.cpp': No such file or directory

It's copying a file from:
C:\Windows\TEMP\flexci\run-00292523\work\src\cupy\_core\include\cupy\cccl\libcudacxx\libcxx\test\std\experimental\memory\memory.polymorphic.allocator.class\memory.polymorphic.allocator.mem\construct_pair_const_lvalue_pair.pass.cpp

to:
C:\Windows\TEMP\flexci\run-00292523\work\src\build\lib.win-amd64-cpython-39\cupy\_core\include\cupy\cccl\libcudacxx\libcxx\test\std\experimental\memory\memory.polymorphic.allocator.class\memory.polymorphic.allocator.mem\construct_pair_const_lvalue_pair.pass.cpp

and the latter exceeds Windows's MAX_PATH (260) chars. I'll try updating the registry key to workaroud the issue.

/test full

/test cuda112

/test cuda122

/test windows,cuda112

(so the tags are taken as a union, not an intersection 😂)

Working on a CUB patch so that it's NVRTC-compilable: NVIDIA/cccl#412

Update: this is merged and I updated the submodule to point to the latest CCCL head that includes this patch. A question in discussion internally is whether we'd release CCCL v2.2.x, if so I'd ask for backporting this patch.

/test cuda112

/test cuda112

@kmaehashi what's the right way of addressing CI timeout? Just retry until the cache is populated?

The failing CI cupy.win.cuda112 seems to be a real error rather than timeout?
00:10:42.750065 STDERR 1048]	  c:\windows\temp\flexci\run-00293065\work\src\cupy\_core\include\cupy\cccl\libcudacxx\include\cuda\std\detail\libcxx\include\__utility/unreachable.h(28): error: identifier "__builtin_unreachable" is undefined

Yes that one I'd have to address later, don't know what happens, but I think the rest is working.

Now that #7775 got merged, the cache started to grow. It should be fully cashed after some more runs in the main branch.

/test full

It should be fully cached after some more runs in the main branch.

@kmaehashi sorry I may have misunderstood: Do you mean that the cache would only be populated after merged into main, not in PRs? If so I should stop retrying and instead focus on fixing Win + cuda112.

All CI (except for win.cuda112) failed due to timeout.

/test cuda112

/test full

win.cuda112 has quite some test failures, but because the CI timed out, the error log was truncated and I could not see the detail, not sure what to do... 😅

It should be hopefully fixed by commit ecb6270, which I planned to do in #7869. It seems we got #4383 fixed for free by ensuring that NVRTC sees a consistent set of CCCL headers.

This is ready!

Do you mean that the cache would only be populated after merged into main, not in PRs?

Sorry I dropped the ball. Yes, the cache is updated only in the branch CI to avoid pollution.

I see. Is there a way we can temporarily increase the timeout limit? I'd prefer to see all CIs green before merging (though if not possible I can always send follow-up PRs to fix them) 🙂

Could you try extending the timeout here (the overall timeout - including cache download + build + pytest) and here (pytest timeout - 18000 sec)?

/test full

it seems we still hit timeout on windows?

@kmaehashi any suggestion? 🙂

00:20:12.284651 STDERR 2628]	RunWithTimeout : Cannot validate argument on parameter 'Timeout'. The 36000
00:20:12.284651 STDERR 2628]	argument is greater than the maximum allowed range of 32767. Supply an
00:20:12.284651 STDERR 2628]	argument that is less than or equal to 32767 and then try the command again.

So the maximum timeout on Windows seems 32767 seconds... 😞

So the maximum timeout on Windows seems 32767 seconds... 😞

@kmaehashi so should I revert or modify commit https://github.com/cupy/cupy/pull/7851/commits/fd00150534c0aef3f803487c7a09262d31dcc124?

Could you try replacing 36000 with 32767 (9.1 hours) in this line?
    $test_retval = RunWithTimeout -timeout 36000 -output ../cupy_test_log.txt -- python -m pytest -rfEX @pytest_opts .

If this attempt fails, probably we need to remove the timeout...

/test windows

@kmaehashi it seems windows is all green (including cuda122!)


Submitting Canges for KDE

I am still waiting for the above recommendation to be dealt with.

I am still waiting on the request to be done before merging this.

I am still waiting for those requests to be done.
Last call. I will be closing this PR by the end of the day.
I can have the KDE version of GhostBSD if requests are not promptly completed.


MAP-1547 - remove productId from helm values

to investigate whether productId is causing login to remain in pending state followed by timeout

Removing product_id will not affect login to app


Node Crash

Great library! Exactly what I was going to build myself but thankfully I didn't have to.  I've been testing out certain scenarios to see if it's appropriate for my use case.  Currently I'm testing with two nodes on my local machine, when I kill one the started processes don't seem to transfer over.  Calls to the process fail with no connection to node@localhost. When I restart the crashed node everything seems to fine
Is there something I'm missing? Thanks

Never mind I was using an old version from the docs that was way outdated.  All good on latest

Enabled debugging and I see this message 16:05:40.970 [debug] (swarm) cannot handoff, restarting however it seems the process is not actually restarted.

Sorry @dax0, I've been on the road the past two days. I'll take a look ASAP!

Thanks!

Same here.
iex(916324837a68@916324837a68)1> Bleve.register_worker "foo"
12:51:47.863 [debug] (swarm) tracking name "foo"
{:ok, #PID<14532.163.0>}

iex(916324837a68@916324837a68)2>
12:52:00.422 [debug] (swarm) nodedown: :"4847e97e5d69@4847e97e5d69"
12:52:00.422 [debug] (swarm) redistributing across [:"916324837a68@916324837a68"]
12:52:00.502 [debug] (swarm) cannot handoff, restarting "foo"
12:52:00.503 [debug] (swarm) synchronizing with [:"916324837a68@916324837a68"]
12:52:00.503 [debug] (swarm) synchronized with :"916324837a68@916324837a68"

iex(916324837a68@916324837a68)3> pid = Swarm.whereis_name "foo"
#PID<14532.163.0>

iex(916324837a68@916324837a68)4> :sys.get_status pid
** (exit) exited in: :sys.get_status(#PID<14532.163.0>)
    ** (EXIT) no connection to 4847e97e5d69@4847e97e5d69
    (stdlib) sys.erl:303: :sys.send_system_msg/2

Beyond this error, the library works really great! 👏 👏 👏
I've started a swarm of ~10-20 nodes with docker (starting each container manually), everything (but the above problem) worked as excepted including redistribution and handoffs.
Here's the Dockerfile is use for my project in case you want to try out:
# 1) git archive -o bleve.tar.gz HEAD
# 2) docker network create elixir
# 3) docker build -t bleve .
# 4) docker run -it --net elixir --rm bleve

FROM elixir
RUN mkdir /app
WORKDIR /app
ADD bleve.tar.gz .
RUN mix local.hex --force
RUN mix deps.get
RUN mix compile
CMD iex --sname $(hostname) --cookie monster -S mix

Any updates on this?

Looking into this today, I'll report back with my findings.

Hey guys, just an update, I've been working on some largish changes to the internals all day, and this issue is one that should be resolved by them. I will update here as soon as I have a production-ready branch/release available, should be very soon!

@dax0 @almightycouch I'm getting ready to merge my changes into master and release them, but would like to have you guys test in your environments first before I do so. Could you swap out your dependency with {:swarm, github: "bitwalker/swarm", branch: "pubsub"} and give it a shot? If you have any problems with it please report them as new issues so I can track them separately, but I think it should be much more stable now.
Just as an FYI there are some knobs to tweak which I haven't documented yet, but I'll wait to see how the defaults do first. Also, the autojoin config setting is no longer present, and neither is Swarm.join! for manually joining the cluster. Other than that, it should be a drop-in replacement.

Will give this a shot tonight, thanks!

Still seeing the same issue.  If I start two nodes and then take down one of them, the processes aren't restarted on the surviving node.

@dax0 I have unit tests which verify that they do get restarted, could you push a repo which I can use to reproduce and fix the issue?
I just pushed a fix for the register_name issue :)

I'm now seeing: ** (UndefinedFunctionError) function Swarm.Tracker.whereis/1 is undefined (module Swarm.Tracker is not available)

Oops, should be fixed now!

Still seeing the same issue. If I start two nodes and then take down one of them, the processes aren't restarted on the surviving node.

Same here. Using the pubsub branch.
Note that I'm starting my nodes directly with
iex --sname $(hostname) --cookie monster -S mix

Instead of turning a non-distributed node into a distributed node via Node.start/3.
When I start my IEx session in non-distributed mode and use Node.start/3, Node.set_cookie/2 and Node.ping/1 to turn it into a distributed node and join the cluster, Node.stop/0 will shutdown the node correctly and restart my agents across the cluster (like your unit-test):
iex(n1@macbook-pro)4> Node.stop
:ok

12:57:08.307 [debug] (swarm on nonode@nohost) node removed from ring: n2@macbook-pro
12:57:08.311 [debug] (swarm on nonode@nohost) node removed from ring: n1@macbook-pro
12:57:08.311 [debug] (swarm on nonode@nohost) restarting "foo" on nonode@nohost: connection to previous node n1@macbook-pro was lost
12:57:08.311 [debug] shutting down #PID<0.183.0>
12:57:08.311 [debug] (swarm on nonode@nohost) restarting "foo" on nonode@nohost: connection to previous node n1@macbook-pro was lost
12:57:08.311 [debug] (swarm on nonode@nohost) duplicate registration for "foo" (#PID<0.190.0>), resolving..
12:57:08.311 [debug] shutting down #PID<0.190.0>

But this is not the case when I

kill the agent
Swarm.where_is_name("foo") |> Process.exit(:kill)

kill the BEAM process (closing terminal for example).

cause a network partition.

I've uploaded a small application example: :bleve. To reproduce you can clone the repository and follow the steps in the Dockerfile.

Build the image and start a few containers with:

docker run -it --net elixir --rm bleve

On one node, register the alphabet:

Bleve.register_alphabet

Make some topology changes (killing and starting Docker instances for example)

On one node, check the alphabet:

reg = Bleve.register_alphabet
length reg # should be 26

Thanks so much for the detailed feedback!
I do want to point out that Swarm will make no attempt to restart processes if they exit themselves, or are killed by another process, they are only restarted if they need to be moved (due to cluster topology changes), or restarted (due to network partitions or cluster topology changes where nodes are removed from the cluster). So that part of it is working as expected.
I am surprised that processes aren't being restarted due to network partitions, as that's precisely what the current test simulates. Perhaps they are being killed after being restarted? It may be worth while to add logging to the start_link and terminate callbacks for the processes you are managing via Swarm to see how things are converging (I did that in my tests when I'm checking things out, and it's definitely helpful).
If nodes go down uncleanly, then it may take some time for Erlang's distribution to recognize that the node is no longer available and broadcast the nodedown event, I'm not sure what that timeout value is by default.
I'm exploring some other approaches now, as I'm not satisfied with the performance of the pubsub branch, it just seems like phoenix_pubsub is not intended for this particular use case, I basically have to hack around the Phoenix.Tracker API to prevent timeouts when registering thousands of processes and then partitioning/healing the network, due to the flood of events, and I can't get the nodes to converge remotely fast enough for my needs after re-joining the partitions. However the branch did give me some good ideas that I'm carrying forward, so bear with me while I sort out the kinks!

I do want to point out that Swarm will make no attempt to restart processes if they exit themselves, or are killed by another process, they are only restarted if they need to be moved (due to cluster topology changes), or restarted (due to network partitions or cluster topology changes where nodes are removed from the cluster). So that part of it is working as expected.

Yes, it makes sense. Is there a way to gracefully leave the cluster and force handoffs before the node goes down? If I understand correctly, handoffs only occur when a new node joins the cluster and not the other way around.

If nodes go down uncleanly, then it may take some time for Erlang's distribution to recognize that the node is no longer available and broadcast the nodedown event, I'm not sure what that timeout value is by default.

I found out that shutting down a node with System.halt/0 works properly, redistributing the processes across the ring:
18:40:46.200 [debug] (swarm on bd98f542121e@bd98f542121e) node removed from ring: d0c38c3b5aec@d0c38c3b5aec
18:40:46.203 [debug] (swarm on bd98f542121e@bd98f542121e) restarting "a" on bd98f542121e@bd98f542121e: connection to previous node d0c38c3b5aec@d0c38c3b5aec was lost
18:40:46.204 [debug] (swarm on bd98f542121e@bd98f542121e) restarting "f" on bd98f542121e@bd98f542121e: connection to previous node d0c38c3b5aec@d0c38c3b5aec was lost
18:40:46.204 [debug] (swarm on bd98f542121e@bd98f542121e) restarting "g" on bd98f542121e@bd98f542121e: connection to previous node d0c38c3b5aec@d0c38c3b5aec was lost
18:40:46.204 [debug] (swarm on bd98f542121e@bd98f542121e) restarting "h" on bd98f542121e@bd98f542121e: connection to previous node d0c38c3b5aec@d0c38c3b5aec was lost
...

When shutting down a node uncleanly (using ^C^C from IEx for example), it looks like the Swarm.Ring is detecting the node going down almost instantly:
8:30:52.999 [debug] (swarm on 3d9f66130dff@3d9f66130dff) node removed from ring: d43a8500c8b5@d43a8500c8b5

But Swarm.Registry.redistribute!/0 does not restart the processes correctly.

I'm getting close to having a new implementation of the registry/tracker completed which should do a better job of this. I've literally re-written Swarm like 4 times now trying different approaches haha. It's tough to find the best way to do all of the following:

is multi-master
supports dynamic cluster membership
is fast
is (eventually) consistent in a way that's useful, in other words, you'd expect all nodes in the cluster to converge on a correct view of the registry in as short a time as possible, the longer it takes, the less useful it is
resolves conflicts correctly/intuitively
only require moving a small subset of processes when cluster topology changes

The initial version of Swarm works, albeit with some bugs, but it is a naive approach that is not correct. The version built on phoenix_pubsub was too slow, and didn't have a great mechanism for resolving conflicts. I built a version on mnesia, but it can't support dynamic cluster membership, so that was abandoned. The version I'm building now is based on a push-based, log-transfer optimistic replication algorithm with interval tree clocks as the conflict resolution data structure, and should be a balance between all of the points above, but it remains to be seen how fast it will be - I'm finishing it up today, so we'll see.
Sorry about the churn, but I'm using this in production and I want it to be correct (and useful), so I'm iterating until I find the right combination of tools to solve the problem.

I've pushed my latest work to the rewrite branch. It's missing process groups at the moment, and there are a few edge cases around conflict resolution I need to polish up (though to hit them would be rare indeed), but I'd love to hear how it works for you. If things are looking good for other people, I'll tie up the loose ends and push a new release.

After playing around with it for a while, the latest implementation seems really impressive 😍.
Well done! The logs are very explicit and helpful to understand what's going on.
On my machine, processes are successfully restarted when a Node goes down.

@almightycouch Thanks for the feedback! It's great to hear it's working for more than just my projects :). Just FYI, I cut a new release with the latest implementation, 1.0, in case you are pointing at master or another branch.
I'm looking into some other improvements at the moment as well. Namely a better way to handle supervised tasks which are registered via Swarm, but can still be shifted/restarted based on cluster topology changes. This would be implemented via a new supervisor module, where one defines a child specification, like you would with :simple_one_for_one supervisors, then you start children with Swarm.Supervisor.start_child, and Swarm will pass ownership of that process back to that supervisor after it's started, leaving restarts up to the supervisor to execute, based on the child specification.
Today, if you start a child via a supervisor, you should set it's restart type to :temporary to prevent issues with Swarm - for example, if the process dies unexpectedly, it will be restarted by the supervisor, but it will no longer be registered via Swarm. Swarm itself could in theory supervise processes it starts, but I think it's more ergonomic to have a normal supervisor definition that feels familiar.
P.S. If you want an even more detailed view into the running Swarm process, run :sys.trace(Swarm.Tracker) ;)

FYI, I'm going to close this issue for now, as it should have been resolved in the latest release. If it reoccurs, please open a new issue so I can track it separately :)


Initial implementation

This is an initial PoC of deleting environments from codefresh and k8s once they get stale.

I found this documentation: https://codefresh-io.github.io/cli/environments/delete-environment/
Can't we use the codefresh cli?

@rodrigo-findhotel no, because we can't list using the cli. It doesn't work. So, we have to use the API.
Also, for now I'm deleting the k8s resources one by one, but this will be better once we move to helm.


[SR-16096] Set filter crashes on iOS 15.3 (5.5) when compiled against iOS 15.4 (5.6)

Previous ID
SR-16096

Radar
None

Original Reporter
racer1988 (JIRA User)

Type
Bug

Attachment: Download

Additional Detail from JIRA

Votes
0

Component/s
Compiler, Foundation, swift

Labels
Bug, 5.0Regression, CompilerCrash, OptimizedOnly, RunTimeCrash, Runtime

Assignee
None

Priority
Medium

md5: 767dafbdc16229adfc2b6eb7f9357f2a

Issue Description:
Compiling Code like:
{{let newOnClient: Set<Hashable> = filteredClientObjects.filter }}{ (syncObject) -> Bool in return syncObject.syncIdentifier == nil && syncObject.status != .deleted }
with Swift 5.6 and executing it on 5.5 Crashes at runtime.
Note: it does not crash while debugging, only on Release optimized builds
No details on the crash content:
Thread 22 Crashed:
0 — ? 0x0 ?
CC matthiaskmt (JIRA User)

This probably shouldn't have been transferred out of the swift repository. Please re-open there if this is still an issue.


Safari Module:  Adds 'Open Web Pages Container' to Actions prefs

Just noticed this, a bit strange.
If you go to Prefs > Actions > By Type there's a 'Open Web Pages Container' type with no actions for it. Any way to remove this?

Hmmm. I can see that I registered that type in Info.plist, but there’s no real need. It was probably just to define the icon, but that should be possible in other ways.

I’ll go ahead and close this. It’s fixed in an upcoming pull request that I don’t expect to be controversial.


Function app is not listing when i used the Service connection type "Publish profile based authentication"

I have created a Service connection of type "Publish profile based authentication" for deploying my App into Function app.
When adding the task into my pilne, it no more list the App name  when i select this connection type.
I am able to get the app listed when i use the service connection type "Azurerm resource manager with service principle based". Does this plugin has any such limitations due to which the app is not listed with the service connection type "Publish profile based"? Please advise

@anoopk-kr : Service connection of type "Publish profile based authentication" does not have enough permissions to be able to list out the App names. That was primarily meant to be used in a YAML based work flow.
You can either choose to use a service connection of type"AzureRM resource manager" (or) switch to YAML based pipeline if you intend to use service connection of type "Publish profile based authentication".


Update proxy-idp-adfs.md

Typo: Microosoft->Microsoft

Learn Build status updates of commit 46039bb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

CloudAppSecurityDocs/proxy-idp-adfs.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Looks good; thanks, @ccmsft


[BUG] Nightly Upgrade Test:  test_recurring_job_kubernetes_status failed

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Install Longhorn v0.7.0
Upgrade Longhorn to v0.8.0
Run test_recurring_job_kubernetes_status test

Expected behavior
test should pass
Log
client = <longhorn.Client object at 0x7f523b6b2110>
core_api = <kubernetes.client.apis.core_v1_api.CoreV1Api object at 0x7f523b706550>
volume_name = 'longhorn-testvol-9b2hh2'

    @pytest.mark.csi
    @pytest.mark.recurring_job
    def test_recurring_job_kubernetes_status(client, core_api, volume_name):  # NOQA
        """
        Test that a RecurringJob properly backs up the KubernetesStatus of a
        Volume.
        """
        set_random_backupstore(client)
        host_id = get_self_host_id()
        client.create_volume(name=volume_name, size=SIZE,
                             numberOfReplicas=2)
        volume = common.wait_for_volume_detached(client, volume_name)

        pv_name = "pv-" + volume_name
        create_pv_for_volume(client, core_api, volume, pv_name)
        ks = {
            'pvName': pv_name,
            'pvStatus': 'Available',
            'namespace': '',
            'pvcName': '',
            'lastPVCRefAt': '',
            'lastPodRefAt': '',
        }
        wait_volume_kubernetes_status(client, volume_name, ks)

        # Simple Backup Job that runs every 2 minutes, retains 1.
        jobs = [
            {
                "name": RECURRING_JOB_NAME,
                "cron": "*/2 * * * *",
                "task": "backup",
                "retain": 1
            }
        ]
        volume.recurringUpdate(jobs=jobs)
        volume.attach(hostId=host_id)
        volume = common.wait_for_volume_healthy(client, volume_name)

        # 5 minutes
        time.sleep(300)
        snapshots = volume.snapshotList()
        count = 0
        for snapshot in snapshots:
            if snapshot.removed is False:
                count += 1
        # 1 from Backup, 1 from Volume Head.
        assert count == 2

        # Verify the Labels on the actual Backup.
        bv = client.by_id_backupVolume(volume_name)
        backups = bv.backupList().data
>       assert len(backups) == 1
E       assert 2 == 1
E         -2
E         +1

test_recurring_job.py:269: AssertionError

Environment:

Longhorn version: 0.8.0
Kubernetes version: v1.17.2
Node OS type and version: Ubuntu 18.04

Additional context
Jenkins build num: longhorn-upgrade-tests/12

Test also failed in nightly test
logs:
client = <longhorn.Client object at 0x7feb86f29bd0>
core_api = <kubernetes.client.apis.core_v1_api.CoreV1Api object at 0x7feb872dfe90>
storage_class = {'allowVolumeExpansion': True, 'apiVersion': 'storage.k8s.io/v1', 'kind': 'StorageClass', 'metadata': {'name': 'longhorn-test'}, ...}
statefulset = {'apiVersion': 'apps/v1', 'kind': 'StatefulSet', 'metadata': {'name': 'recurring-job-in-storageclass-test'}, 'spec': {...ge': 'busybox', 'imagePullPolicy': 'IfNotPresent', 'name': 'sleep', ...}], 'terminationGracePeriodSeconds': 10}}, ...}}

    @pytest.mark.recurring_job  # NOQA
    def test_recurring_job_in_storageclass(client, core_api, storage_class, statefulset):  # NOQA
        set_random_backupstore(client)
        statefulset_name = 'recurring-job-in-storageclass-test'
        update_statefulset_manifests(statefulset, storage_class, statefulset_name)
        storage_class["parameters"]["recurringJobs"] = json.dumps(create_jobs1())

        create_storage_class(storage_class)
        create_and_wait_statefulset(statefulset)

        pod_info = get_statefulset_pod_info(core_api, statefulset)
        volume_info = [p['pv_name'] for p in pod_info]

        # 5 minutes
        time.sleep(300)
        for volume_name in volume_info:  # NOQA
            volume = client.by_id_volume(volume_name)
>           check_jobs1_result(volume)

test_recurring_job.py:155:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

volume = {'backupStatus': [{'backupURL': 's3://backupbucket@us-east-1/backupstore?backup=backup-390494779af54a3e&volume=pvc-1d3...5472', 'staleReplicaTimeout': 30, 'standby': False, 'state': 'attached', 'timestamp': '2020-03-17T10:42:11.463801388Z'}

    def check_jobs1_result(volume):
        snapshots = volume.snapshotList()
        count = 0
        for snapshot in snapshots:
            if snapshot.removed is False:
                count += 1
        # 2 snapshots, 1 backup, 1 volume-head
>       assert count == 4
E       assert 5 == 4
E         -5
E         +4

test_recurring_job.py:39: AssertionError

Additional context:
Jenkins build num: longhorn-tests/344

Test Also failed on nightly test
client = <longhorn.Client object at 0x7ffba4cca4d0>
core_api = <kubernetes.client.apis.core_v1_api.CoreV1Api object at 0x7ffba4925c10>
volume_name = 'longhorn-testvol-2o981n'

    @pytest.mark.csi
    @pytest.mark.recurring_job
    def test_recurring_job_kubernetes_status(client, core_api, volume_name):  # NOQA
        """
        Test that a RecurringJob properly backs up the KubernetesStatus of a
        Volume.
        """
        set_random_backupstore(client)
        host_id = get_self_host_id()
        client.create_volume(name=volume_name, size=SIZE,
                             numberOfReplicas=2)
        volume = common.wait_for_volume_detached(client, volume_name)

        pv_name = "pv-" + volume_name
        create_pv_for_volume(client, core_api, volume, pv_name)
        ks = {
            'pvName': pv_name,
            'pvStatus': 'Available',
            'namespace': '',
            'pvcName': '',
            'lastPVCRefAt': '',
            'lastPodRefAt': '',
        }
        wait_volume_kubernetes_status(client, volume_name, ks)

        # Simple Backup Job that runs every 2 minutes, retains 1.
        jobs = [
            {
                "name": RECURRING_JOB_NAME,
                "cron": "*/2 * * * *",
                "task": "backup",
                "retain": 1
            }
        ]
        volume.recurringUpdate(jobs=jobs)
        volume.attach(hostId=host_id)
        volume = common.wait_for_volume_healthy(client, volume_name)

        # 5 minutes
        time.sleep(300)
        snapshots = volume.snapshotList()
        count = 0
        for snapshot in snapshots:
            if snapshot.removed is False:
                count += 1
        # 1 from Backup, 1 from Volume Head.
        assert count == 2

        # Verify the Labels on the actual Backup.
        bv = client.by_id_backupVolume(volume_name)
        backups = bv.backupList().data
>       assert len(backups) == 1
E       assert 2 == 1
E         -2
E         +1

test_recurring_job.py:269: AssertionError

Additional context:
longhorn-tests/370

failed again on longhorn-upgrade-tests/48


Line chart - dots showing instead of lines. Set connectgap defaults to true

Description
I'm plotting a line chart on datetime (up to second level) split by members. The lines becomes dots.

However, if I filter the members, it's a connected line.

I set connectgaps to true in the plotly configuration:
 "plotly": {
		"data": {
			"commonTraceOverride": {
				"connectgaps": true
			}
		}
	}

The lines are now joined as expected:

Would it be better to set connectgaps to true?

Hi @HuifangYeo,
Could you share a notebook with this issue? I'm unable to reproduce it on my side.
Thanks!

Hi @mtadams007,
I'll sorry I've overlooked this issue. You can look at the last chart in the notebook.
wine-modeling.zip

Issue is still here in 0.6.4


---Location b--- Snapper rework

Yep, totally a branch that touches red-nosed snapper, and only red-nosed snapper, without ever going on a rampant series of edits on another section <.< ... ... ...
...
...
...
...
Ok...
Ya got me...
Rampant series of edits... <.<
Complete rework of the snapper tile. Now shows phylums based on your assumed needs, and shows the phylum tracked and in current location.
Adds a warning if you're bringing the snapper and its phylum tracking is undoing a banish.
Rework of the appearance_rates_adjusted function (used in the location bar and to calculate the average turns a task will take, like bounties), which now relies more confidently on mafia's data.
(Somewhat smaller) Rework of the location bar:
Having copies of a monster, form olfaction or olfaction-likes, stops monsters from being shown as simply "banished" (btw, plz report more locations in which banishes are impossible).
Also stops only displaying a "?" for meat and drop chance when underwater.
Also also, fixes what caused the partial blurring of the left side of the base drop % of monsters' items in the location bar popup.

self-reminder: the changes in misc items.ash and red nosed snapper.ash will need to be compliant to the Minimize "new standards"

included in "minimize"


[5.5] Simplify contracts

Let \Illuminate\Contracts\Notifications\Factory extend \Illuminate\Contracts\Notifications\Dispatcher
Let \Illuminate\Contracts\Console\Kernel extend \Illuminate\Contracts\Console\Application

Hmm, I dunno, I don't want to mingle these contracts. They aren't necessarily the same entities.


Index command fails on Gradle multi-module project using Java toolchains inside allprojects

To reproduce
git clone https://github.com/olafurpg/gradle-example
cd gradle-example
git checkout 4f92b5d80c029f528873d666175553291e36f8c0
cs launch lsif-java:0.4.0 --contrib -- index
...
info: /Users/olafurpg/dev/olafurpg/gradle-example/gradlew --init-script /var/folders/mb/88qbygqj169byvv_68bw4fn80000gn/T/lsif-java5214645091470507619/java-toolchains.gradle lsifDetectJavaToolchains

BUILD SUCCESSFUL in 906ms
3 actionable tasks: 3 executed
info: /Users/olafurpg/dev/olafurpg/gradle-example/gradlew --init-script /var/folders/mb/88qbygqj169byvv_68bw4fn80000gn/T/lsif-java5214645091470507619/init-script.gradle -Porg.gradle.java.installations.auto-detect=false -Porg.gradle.java.installations.auto-download=false -Porg.gradle.java.installations.paths=/var/folders/mb/88qbygqj169byvv_68bw4fn80000gn/T/lsif-java5214645091470507619/1.8 --no-daemon clean compileTestJava
To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/6.7/userguide/gradle_daemon.html.
Daemon will be stopped at the end of the build stopping after processing

BUILD SUCCESSFUL in 5s
7 actionable tasks: 6 executed, 1 up-to-date

We see "BUILD SUCCESSFUL" but no dump.lsif file is created.

Fixed in #168


Update project

This adds some updates to the project.
It includes breaking changes. I wouldn't add a deprecation period as the wrapper is hard to use atm. and there might be more breaking changes required. Throwing things into cold water might help to get it to a better state and ready quicker, for the upcoming 2.4.0 upstream release.

Window methods
// Current
webui.Bind(my_window, "CheckPassword", Check)

// Change
my_window.Bind("CheckPassword", Check)

Event.Data to go types (quickfix) - should be eventually superseded with a proper webui_return_int, webui_return_int and webui_return_string implementation that is currently missing.
func myFunctionInteger(e webui.Event) string {
	response := e.Data.Int()
	fmt.Printf("myFunctionInteger: %d\n", response) // 123456789
	return ""
}

Adds a call_go_from_js.go example

Edit:

Further, the bind callbacks return type was changed from string to any and encoding of JS returns into JSON was added. An even more dynamic return type specification for improved type checking can be added as development progresses.
// before
func myFunctionWithResponse(e webui.Event) string {
	number := e.Data.Int() * 2
	return strconv.Itoa(number)
}

// after
func myFunctionWithResponse(e webui.Event) any {
	number := e.Data.Int() * 2
	return number
}

It became pretty much of a re-write in the end, the single commits are structured to make following the changes per commit as easy as possible.

Further changed the bind callback return type to any and added dynamic encoding to json. Dynamic return type specification can be added as development progresses.
// before
func myFunctionWithResponse(e webui.Event) string {
	number := e.Data.Int() * 2
	return strconv.Itoa(number)
}

// after
func myFunctionWithResponse(e webui.Event) any {
	number := e.Data.Int() * 2
	return number
}

That's look interesting, and thank you for call_go_from_js.go.

I further looked into Gos generics. They don't allow a lot of things yet (they are fairly young (1.18)).
The ability the changes would add here, to return all types, while needing to declare the return type of the bind callback function to any is a good enough improvement for now I think.
@hassandraga if you had the chance to test the changes and nothing is blocking, I would merge this PR here as it has lots of improvements.

I just test it and I got an error:
go build minimal.go
# command-line-arguments
.\minimal.go:7:4: w.Show undefined (type uint has no field or method Show)

I like the changes you did. The wrapper is now more Go philo friendly.
Thank you 👍

Thank you @hassandraga.
I'm about to take a little vacation and plan to do further improvements for the go wrapper, like implementing the webui_get functions if they are still open after that 👍.
Best regards

Doing a last quick test on the updated main, the wrapper version might need a bump if the examples should work with the default go get github.com/webui-dev/go-webui/v2. Currently, it might be necessary to specify the commit as version
go get github.com/webui-dev/go-webui/v2@315b510c1762ff9ebf9a71b13905a874cc438be6.


Application matchers should support an array

https://github.com/laravel-streams/streams-core/commit/824eb7f2b6abbd1a1c339277d813cac196c5a290


Add missing go.sum

Run go mod tidy on the module and add the resulting go.sum file.

Friendly ping @davecheney @luna-duclos

Closing in favor of #34 which contains this fix as well.


Logs are created

This system is meant to be transient and meant to go as fast as possible.  Therefore, Ceph's default logs are not required as they will be more verbose than how this system plans to run in production.

A simple solution is provided in the sudoers_file pull request, removing the log file from the system. However, this doesn't get over the issue that CPU usage is being wasted in creating logs that are ultimately deleted.


openssl-windows[core] build failure

Host Environment

OS: Windows 10
Compiler: VS 16.4

To Reproduce
Steps to reproduce the behavior:
./vcpkg install openssl-windows[core]:x86-windows
Failure logs
PS D:\dev\vcpkg> .\vcpkg.exe install openssl-windows[core]:x86-windows
Computing installation plan...
The following packages will be built and installed:
    openssl-windows[core]:x86-windows
A suitable version of powershell-core was not found (required v6.2.1). Downloading portable powershell-core v6.2.1...
Downloading powershell-core...
  https://github.com/PowerShell/PowerShell/releases/download/v6.2.1/PowerShell-6.2.1-win-x86.zip -> D:\dev\vcpkg\downloads\PowerShell-6.2.1-win-x86.zip
Extracting powershell-core...
A suitable version of 7zip was not found (required v18.1.0). Downloading portable 7zip v18.1.0...
Downloading 7zip...
  https://www.nuget.org/api/v2/package/7-Zip.CommandLine/18.1.0 -> D:\dev\vcpkg\downloads\7-zip.commandline.18.1.0.nupkg
Extracting 7zip...
A suitable version of nuget was not found (required v4.6.2). Downloading portable nuget v4.6.2...
Downloading nuget...
  https://dist.nuget.org/win-x86-commandline/v4.6.2/nuget.exe -> D:\dev\vcpkg\downloads\nuget.exe
Starting package 1/1: openssl-windows:x86-windows
Building package openssl-windows[core]:x86-windows...
A suitable version of git was not found (required v2.25.1). Downloading portable git v2.25.1...
Downloading git...
  https://github.com/git-for-windows/git/releases/download/v2.25.1.windows.1/PortableGit-2.25.1-32-bit.7z.exe -> D:\dev\vcpkg\downloads\PortableGit-2.25.1-32-bit.7z.exe
Extracting git...
-- Downloading https://www.openssl.org/source/openssl-1.1.1d.tar.gz...
-- Extracting source D:/dev/vcpkg/downloads/openssl-1.1.1d.tar.gz
-- Using source at D:/dev/vcpkg/buildtrees/openssl-windows/src/openssl-1-b1f8ae3e6c
-- Downloading http://www.nasm.us/pub/nasm/releasebuilds/2.14.02/win32/nasm-2.14.02-win32.zip...
-- Downloading http://download.qt.io/official_releases/jom/jom_1_1_3.zip...
-- Copying openssl release source files...
-- Copying openssl release source files... done
-- Configure x86-windows-rel
      0 [main] perl 1540 child_info_fork::abort: address space needed by 'Cwd.dll' (0x1F0000) is already occupied
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: D:/dev/vcpkg/downloads/tools/git-2.25.1-1-windows/usr/bin/perl.exe Configure enable-static-engine enable-capieng no-ssl2 -utf-8 shared VC-WIN32 --prefix=D:/dev/vcpkg/packages/openssl-windows_x86-windows --openssldir=D:/dev/vcpkg/packages/openssl-windows_x86-windows -FS
    Working Directory: D:/dev/vcpkg/buildtrees/openssl-windows/x86-windows-rel
    Error code: 127
    See logs for more information:
      D:\dev\vcpkg\buildtrees\openssl-windows\configure-perl-x86-windows--rel-out.log
      D:\dev\vcpkg\buildtrees\openssl-windows\configure-perl-x86-windows--rel-err.log

Call Stack (most recent call first):
  ports/openssl-windows/portfile.cmake:77 (vcpkg_execute_required_process)
  scripts/ports.cmake:90 (include)

Error: Building package openssl-windows:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: openssl-windows:x86-windows
  Vcpkg version: 2020.02.04-nohash-external

Additionally, attach any relevant sections from the log files above.

PS D:\dev\vcpkg> cat D:\dev\vcpkg\buildtrees\openssl-windows\configure-perl-x86-windows--rel-err.log
      0 [main] perl 1540 child_info_fork::abort: address space needed by 'Cwd.dll' (0x1F0000) is already occupied

******************************************************************************
This perl implementation doesn't produce Windows like paths (with backward
slash directory separators).  Please use an implementation that matches your
building platform.

This Perl version: 5.26.2 for i686-msys-thread-multi-64int
******************************************************************************

Additional context
Tried using PowerShell, gitbash and cygwin. Same result.

@christophe-calmejane Thanks for reporting this issue. I can't reproduce this issue in my side.
I think you could see https://github.com/git-for-windows/git/wiki/32-bit-issues#solutions for some workarounds that might help.

Ok so hum, I probably forgot to report that I used the master branch (as of yesterday), but I added the 3 commits from this PR. If I remove the first one, openssl-windows is compiling perfectly again.
I'll inform the PR that there is an issue with the code. Thanks


Prisma 3.9.0

Motivation for this change
Changelog: https://github.com/prisma/prisma/releases/tag/3.9.0
The PR is against staging due to the prisma-engines package needing Rust 1.58.0 minimum. Tested compiling the whole pipeline and works fine.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@pimeys I think it would be best to use 3.9.1

If the cli or engines changed, yes. Otherwise the user can use 3.9.0 core and 3.9.1 client.

Yes one patch was about the CLI (db pull)

Making a new PR when master has rust 1.58.0.


More proper way for displaying function pointers in structures in linear view

I've opened a general issue for this before as #3540 and I mentioned this problem in my second message in it. But I frequently get into trouble with this spesific example, so I want to open an seperate issue for it in order to make people find it more easy.
struct cc_handler_vft cc_handler_vftl =
{
    void (* handle_cc_command)(struct cc_handler* this, int32_t a2, void (*** lpAddress)(void*, int32_t)) = handle_cc_command
    int32_t (* cc_handler_destroy)(struct cc_handler* this) = cc_handler_destroy
}

As you can see, it makes it very hard to see members of vft. Especially if there are a lot of them with longer prototypes and I open two BN side-by-side.

Just to make sure I'm following, the members here are handle_cc_command and cc_handler_destroy, which are both function pointers, right? And what you're looking for, from the other issue, is to just display:
struct cc_handler_vft cc_handler_vftl =
{
   handle_cc_command
   cc_handler_destroy
}

...because the names of the assignments match the members they're being assigned to, and you would prefer to have the types hidden?
Can you elaborate on this a little bit for me? I think I'm specifically having a hard time understanding wanting the assignment to go away. I can understanding wanting to hide the big function prototypes, since that pushes the assignment way out to the right, which is hard to read.


.

@wei Can you close this issue? This must've been opened by accident.
@NoLnote if you can close it yourself, even better.


mean-cli install fail :(

Hi @zohar  @zlokomatic   @bjornkri   @OriPekelman  @AlmogBaku  @brownman
Can you help me!!
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.10.x","npm":"2.1.x"} (current: {"node":"0.10.33","npm":"2.6.0"})

<EMAIL_ADDRESS>preinstall /root/.nvm/v0.10.33/lib/node_modules/mean-cli
node ./scripts/preinstall

sh: node: command not found
npm ERR! Linux 3.2.0-4-amd64
npm ERR! argv "node" "/root/.nvm/v0.10.33/bin/npm" "install" "-g" "mean-cli"
npm ERR! node v0.10.33
npm ERR! npm  v2.6.0
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>preinstall: node ./scripts/preinstall
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>preinstall script 'node ./scripts/preinstall'.
npm ERR! This is most likely a problem with the mean-cli package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./scripts/preinstall
npm ERR! You can get their info via:
npm ERR!     npm owner ls mean-cli
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /share/project/npm-debug.log

You don't have node (which is part of the prerequisites) installed.


Improved API and SDK consistency

Fixes issue 1, Internal issue Product Backlog Item 3713:[Cashier API][SDK] Update SDK with latest changes on the server BACKLOG-2917

Incomplete code changes


Multiple tutorials per repo

[x] support path to load any markdown file in repo
[x] automatically pick up localized version of file
[x] add refernce to tutorial repo if it contains code

I think the cloud (gh proxy) might support more than one package per repo, need to check...

Having multiple files is actually easier to handle when editing.

just FYI the cloud api allows for subfolders, like here: https://pxt.io/api/gh/microsoft/pxt-microbit/master/libs/hello or https://pxt.io/api/gh/microsoft/pxt-common-packages/master/libs/color-sensor


Add a package with Zig, C, and C++ project templates

Given how small project files using the Zig SDK are, I'm not actually convinced that there's much value here for the amount of work that would be needed.


Update material-ui import paths

I actually haven't had much luck copying these into an app, but tests seem to be passing locally. Let's see what travis does.
Fixes #2240

Let's go with #2255 instead, more activity over there.


Fix build_and_push.sh

The >& syntax isn't supported in sh
Related Issue or Background Info

This tiny syntax error was introduced in #1422

Huh. Sorry about that! Filed under "how did that work in the first place?" 😕


Travis CI: Test on Node.js v4.x.x and v5.x.x

Same as https://github.com/sindresorhus/atom-linter-xo/pull/13#issuecomment-167800724 No point in changing it when it only targets stable as it does it for a reason.


babel-node is not recommended for production

I just saw that babeljs docs advice against using babel-node on production like we are doing in https://github.com/cloverfield-tools/universal-react-boilerplate/blob/master/package.json#L7
ref. https://babeljs.io/docs/usage/cli/#babel-node
So should it be compiled to a bin/ dir and point the start script there?

Yes, we should compile for prod. I typically compile to a build directory.

What do you think of running it with PM2 after transpiling with babel?

That's fine. =)

I'm open to a PR to document production use, if you'd like to contribute. =)

I'm trying to run the server but don't get anything served.
npm run build
npm run start # or npm run server

The app logs in the console that the server is running, but there is nothing served on the browser when I hit localhost:3000
Is that still work in progress?

Probably. There is an outstanding PR request that adds more features here. Have you looked at that?

At any rate, I'd love to accept a PR that displays the parsed README from the markdown for the homepage. =)

Yeah I have seen the outstanding PR. I think I'll debounce my work on this issue until we get the app served to the browser.

I'm trying to run the server but don't get anything served.

Interesting. I see "Your App" when I run it. =) Don't you?

ah, for some reason it doesn't work from my vagrant. I tried it in my local and it works thanksf

Interesting... old version of Node?

it is old.. 0.12.7
but it works if I curl inside vagrant. But not from outside. It only happens with this app. The other apps I can curl them from outside the vagrant box without problems. I'll keep digging into this.

odd. Sounds like a vagrant thing. =)

found it. It was the 'localhost', in https://github.com/cloverfield-tools/universal-react-boilerplate/blob/master/source/server/index.js#L18
Since I was using the IP of my vagrant box instead of localhost:3000
eg. http://<IP_ADDRESS>:3000/

Want to PR, or is your problem solved? =)

Yeah I can PR. I just wonder why was that 'localhost' there

I don't think it's there for any particular reason.

Host fixed by 7b80d37

@nkbt this issue is related to running the app with node instead of babel-node. Nothing to do with the host

I thought we compile for prod, sorry


V0.4.3+

Summary
A couple of small fixes to help with migration from older version of ArchiveBox (v0.3.x).
Changes these areas

[X] Bugfixes
[ ] Feature behavior
[ ] Command line interface
[ ] Configuration options
[ ] Internal architecture
[ ] Archived data layout on disk

Thanks! We should also add dateutil as a dependency in the Pipfile.


Fix focus/blur event handler not firing bug

Description
Please include a summary of the change. Please also include relevant motivation and context. List any dependencies that are required for this change.
Also

Add any other relevant change made on this PR.

Notes

Describe your changes

Tests Added / Updated?

YES or NO. If not, why?

Screenshots

Current dependencies on/for this PR:

main

PR #58   👈

This comment was auto-generated by Graphite.


feat(radiocomponent): create radio component

What does this PR do
This PR creates radio components
Description of Task to be completed
Create a reusable radio component according to the style guide.
How should this be manually tested
By opening up storybook and viewing the textBox component.
Storybook can be run with the command npm run storybook
What are the relevant issues this PR belongs to
#19
Any background context you want to add
N/A

I am having errors in the storybook @BolajiAyodeji @BolajiOlajide could you please look into this for me, I am probably doing something wrong, I don't seem to figure it out.

I am having errors in the storybook @BolajiAyodeji @BolajiOlajide could you please look into this for me, I am probably doing something wrong,tried multiple things before now it still had that error so I just took out the additional things I added and pushed this, I don't seem to figure it out

@BolajiOlajide's response should have fixed your issue already, please respond to the thread if you have any more isses.


Added missing options to PoolingConnectionFactoryProvider

I need to customize some options, so I added them to PoolingConnectionFactoryProvider:

maxLifeTime
maxIdleTime
maxAcquireTime
maxCreateConnectionTime

These options expect a Duration type, so I created an utility class to parse them. It only supports the ISO-8601 format for now, but if you want, I can implement support for other formats like DurationStyle from Spring Boot conversion service.

Thanks for the pull request. We currently default in R2DBC to the Duration ISO-8601 format where durations are parsed. Introducing a specific format parser in each project leads to code duplication across all drivers. While a more user-friendly format is desirable, a parser should be provided ideally by the Java runtime itself.

Thank you for your contribution. That's merged, polished, and backported now.


Use as middleware/skip routing?

Is there a way to have openapi-backend handle everything except the routing?
For my needs it would be excellent, if the validation and security could be handled as a middleware and the routing could be handled by express in traditional fashion. That would make it much easier to integrate with existing code.

@openreply-dleinhaeuser Not sure I understand completely.
You would like to pass the operationId directly to OpenAPIBackend.handleRequest to skip the routing part?

Closing due to no activity


Runcontainer efficiency

change RunContainer.intersects(BitmapContainer) to check if the bitmap intersects with the range
change RunContainer.andCardinality(BitmapContainer) to add the cardinality in the range of the run
some miscellaneous test coverage enhancements

Hi, @richardstartin I have a few questions to get some context. What is the reason that
this method 'boolean intersects(int minimum, int supremum)' cannot be reused in place of 'boolean isNonEmptyInRange(int start, int end)' in BitmapContainer ?
I see that those methods differently calculate last word, are both correct ?
boolean intersects(int minimum, int supremum):
'int end = supremum >>> 6;'
boolean isNonEmptyInRange(int start, int end):
'int endword = (end - 1) >>> 6;'

Yes good point, thanks, this is a WIP PR.

Coverage increased (+0.1%) to 91.786% when pulling 1b29f5078cb6158cbd2622e27191bcfc9eafeabb on richardstartin:runcontainer-efficiency into 8c4b1ab8c1c7c7728c3276ce7f98f4f89a26002a on RoaringBitmap:master.

@lemire what do you want to do about this LGTM failure? It fails because
[2020-04-20 10:20:28] [autobuild] > Could not resolve all files for configuration ':jmh:jmh'.
[2020-04-20 10:20:28] [autobuild]    > Could not find it.uniroma3.mat:extendedset:1.3.4.
[2020-04-20 10:20:28] [autobuild]      Searched in the following locations:
[2020-04-20 10:20:28] [autobuild]        - https://jcenter.bintray.com/it/uniroma3/mat/extendedset/1.3.4/extendedset-1.3.4.pom
[2020-04-20 10:20:28] [autobuild]        - https://metamx.artifactoryonline.com/metamx/pub-libs-releases-local/it/uniroma3/mat/extendedset/1.3.4/extendedset-1.3.4.pom
[2020-04-20 10:20:28] [autobuild]      Required by:
[2020-04-20 10:20:28] [autobuild]          project :jmh

Should this be com.n3twork.druid:extendedset:1.3.4 instead?

I am asking for a rerun. It looks like the tests failed.

@lemire the tests pass, but LGTM breaks looking for dependencies.

In build logs we can find that both urls which should point to extendedset pom, returns 404 not found error. I would suggest to try changing url in build.gradle.kts file:
instead of
line 12: url = URI("https://metamx.artifactoryonline.com/metamx/pub-libs-releases-local")
try use this /
url = URI("https://metamx.artifactoryonline.com/artifactory/pub-libs-releases-local")

@Cheappie
I will try to change the URI name on top of Richard's work. Should be harmless enough.

Oh. It is a bit complicated because it is a foreign PR.

@Cheappie

please revert package to 'it.uniroma3.mat'

Why should he revert? I don't understand why he made the change, but I don't care too much that he reverts it back. As far as I can tell, this is an old package that has not received much love over the years... while others have been updating it... so I feel totally warranted to update the dependency if it is somehow useful... I just think we should know why @richardstartin wants to do so.

@lemire I thought we aim to repair finding that dependency, but if there is any better alternative then ofc let's use it

Ok. Let us wait for @richardstartin  to ping us back.

@lemire @richardstartin
Would it be possible to make new release to maven central, after this change is merged ? I am asking because it significantly improves performance of zero-gc cardinality calculations between run and bitmap containers

@lemire there's a lot more low hanging fruit for run vs bitmap. Do you want to merge now or batch in some more improvements?

Let's fix LGTM another time (I couldn't care less).

This has been merged and released.

@richardstartin I missed your comment about low-hanging fruits. Can you elaborate?


Corrected interface for webhookhandler

Converted type of deliveryMethod to enum instead of enum value
This is to avoid the typescript error in the typescript express app
Minor change

I think this is not the right thing to do - we actually want those types to be specific to the DeliveryMethod because the fields the API accepts for each type are different.
Thank you for contributing, but I think the type safety is actually better the way it is now because it encourages apps to use the right fields for each method.
We look forward to your contributions in the future!


Feat/reblog stats

What does this PR?
In this PR, I added reblog stats that shows a list of users who reblogged a post.
Users can see number of reblogs a post has and a list icon that when clicked shows a list of users who reblogged the particular post.
Github issue
https://github.com/ecency/ecency-vision/assets/88087890/3b5a1a3a-bed0-4372-a280-d11aeedc94f3
Video/ Screenshot

@Adesojisouljay PR description and video missing.

@Adesojisouljay PR description and video missing.

Need to add couple changes, i'll add video and description
Thanks

@Adesojisouljay you can add number next to existing reblog button. No need extra icon, only when logged in user reblogs, icon changes the color, that's it. Otherwise, we can always show number of reblogs and reblogged people on Post page.

Okay, noted, we should just show number of reblogs. What about those lists, should we show them when number is clicked or we look for some on page to list those who reblogged a post?

@Adesojisouljay Yes clicking on number should show list, clicking on icon should (un)reblog

@Adesojisouljay Yes clicking on number should show list, clicking on icon should (un)reblog

Alright, that's noted.
Thanks


services / factories, what is going on?

I am not sure if the angular team had mixed ideas about services and factories. But the code and ideas mentioned in the services section don't add up, not even on angular's site. If service registration takes a constructor function as the second argument, and its suppose to be invoked as a constructor would, with the new keyword, then why can't I treat it as a true constructor passing in parameters?
Service
(function () {
    angular
        .module("App")
        .service("Person", Person);

    //angular wants my parameters to be injectables.
    function Person(name, age) {
        this.name = name;
        this.age = age;
    }
})();

Controller
(function () {
    angular
        .module("App")
        .controller("DemoController", DemoController);

    DemoController.$inject = ["Person"];

    function DemoController(Person) {
        var a = new Person("rafael", 22);// ERROR

        var Demo = this;

        Demo.title = "Demo";
    }
})();

Factories
As for factories, your documentation states that, as well as other books, that factories should return service / class instances. However, this code contradicts. No instances were created and returned by the factory.
 var batchModule = angular.module('batchModule', []);

/**
 * The `batchLog` service allows for messages to be queued in memory and flushed
 * to the console.log every 50 seconds.
 *
 * @param {*} message Message to be logged.
 */
batchModule.factory('batchLog', ['$interval', '$log', function($interval, $log) {
  var messageQueue = [];

  function log() {
    if (messageQueue.length) {
      $log.log('batchLog messages: ', messageQueue);
      messageQueue = [];
    }
  }

  // start periodic checking
  $interval(log, 50000);

  return function(message) {
    messageQueue.push(message);
  }
}]);

I am not sure what part of the docs doesn't add up (although admittedly the multitude of ways to create Angular services (hereafter "services") has been a common source of confusion).
There are numerous resources on that subject, but in brief (quoting from the docs):

Angular services are substitutable objects that are wired together using dependency injection (DI). You can use services to organize and share code across your app.

So, services are "things" that you can inject into other parts/components, such as directives, controllers, filters, other services etc. Angular's Inversion Of Control container is in charge of creating the service instances (one per injector), supplying the necessary "ingredients" (dependent values) as arguments and handing them to whoever requests them (through Dependency Injection).
The "recipe" for how a service will de created is defined using one of the available methods: .provider(), .service(), .factory(), .value(), .constant()
Basically, .provider() is the most flexible but verbose, so Agular provides the other methods as syntactic sugar (more or less) for some of the most common usecases.
--

The service factory function generates the single object or function that represents the service to the rest of the application.

That is exactly what it does. Using .factory(), you can specify a (factory) function, that will be invoked by the injector (when it needs an instance of the service), and it is expected to return the service instance (i.e. the "thing" that will be passed to whoever requests the corresponding service).
--

value: Register a value service with the $injector, such as a string, a number, an array, an object or a function.

For you usecase, you might want to just use the .value() shortcut.
--
Regarding the following:

[...] factories should return service / class instances. However, this code contradicts. No instances were created and returned by the factory.

Note that instance doesn't necessarily mean "something that was the result of calling the new operator on a constructor function / class". The new operator is one of the many possible ways of creating an instance of something. The example code returns a new function, which is an instance of Function (which is an instance of Object).
But the main point is that whatever the factory function returns, is the "instance of the service" in the sense that it is the "concrete thing" that will be passed to anyone that requests it (through DI). And because services as (per injector) singletons, the exact same "thing" will be passed everytime.

Afaict, everything works (and adds up) properly. BUT we always welcome suggestions (or better yet pull requests) with docs improvements, so by all means do come forward if you have ideas on how we can do a better job explaining these concepts.
I am going to close this, since it is not actionable in its current form, but feel free continue the discussion below.

@gkalpak I have long felt that the key point, of confusion around the service / factory issue, and which the documentation completely fails to address, is the difference in their use cases, or rather the lack thereof.
.service and .factory essentially have the exact same capabilities but cater to different programming styles. If the documentation would simply remark that .service should be used when you want to write in a classical style, and .factory should be used otherwise.

Additionally, I have seen some highly skilled angular developers write code which reflects a misunderstanding of arbitrarity of this distinction. For example, I have seen this:
(function () {
    Function MyService ($http) {
        this.$http = $http;
    }
    MyService.prototype.getById = function (id) {
        return this.$http('/whatever?id=' + id);
    };

    angular.module('app', [])
        .factory('MyService', ['$http', function($http) {
        return new MyService($http);
    }]);
}());

Why didn't they write this? I believe it was because the documentation failed to adequitely explain the similarity and redundancy of the concepts.
(function () {
    Function MyService ($http) {
        this.$http = $http;
    }
    MyService.prototype.getById = function (id) {
        return this.$http('/whatever?id=' + id);
    };

    angular.module('app', [])
        .service('MyService', ['$http', MyService]);
}());

Maybe they know the difference and they intentionally use it this way. Note that @johnpapa's styleguide suggests using .factory even where .service would be enough, for the sake of consistency/fewer concepts. (Some agree, some don't - there is no right or wrong.)
--

.service and .factory essentially have the exact same capabilities

This is not 100% true, unless you use a constructor function as a factory, havig a return value (which is neither a good idea, nor necessary). .service has a more limited scope but requires less boilerplate. .factory is a little more flexible, but is more verbose.
--
Like I said, if you have an idea of how the docs could be improved, please submit a PR and we'll be more than happy to discuss :wink:

The whole point of .service() is that you are supplying a constructor function that Angular's $injector will instantiate (with new) when it needs to create an instance of the service. It is not a way to "store" constructor functions that will be passed to the user to instantiate. And yes, arguments of constructor functions passed to .service() (and used to create service instances) are resolved through DI - that is the whole point of having a IoC container.
Again, for your usecase (where you don't need anything from DI), you could (and should) use .value():
(function () {

angular.
  module('App').
  value('Form', Form);

function Form() {
  this.roles = [];
  this.name = '';
}
Form.prototype.addRole = function addRole() {
  this.roles.push('');
}

})();

Using .value() could work but the docs say that it should take a service instance object as the second parameter. A constructor function is not a service instance object or is it to angular? The reason for the large confusion in the community is the numerous ways of using these methods and the lack of a concrete definition.

the docs say that it should take a service instance object as the second parameter

This means that it should take the "thing" (whatever that is), that will be returned from the $injector whenever someone requests the service (in this case 'Form').

A constructor function is not a service instance object or is it to angular?

In JavaScript there are no "services", so when we are talking about "services" in this context, we are referring to Angular services" (a.k.a. "substitutable objects that are wired together using dependency injection (DI)"). So, a constructor function (which is essentially just a function, which is essentially an Object) can be used as a service instance (i.e. as the "thing" that will be returned when someone requests for the service instance).
I think much of the confusion comes from the fact that in JavaScript, functions are first class citizens and are objects themselves (everything is an object :grin:).
--
This is (more or less) how I like to think about it:
// Assuming:
$provide.
  service('FOO', FooService).
  factory('BAR', barFactory).
  value('BAZ', bazValue).
  provider('QUX', quxProvider);

...I imagine the following "dialogs" taking place inside the app:
someone: Hey, $injector, I need my 'FOO'.
$injector: Sure thing.
$injector: (To itself: They need 'FOO'. I don't have a 'FOO' yet, let's create one. How do I create 'FOO'? Aha, I just var foo = new FooService(/* any arguments are resolved through DI */).)
$injector: There is your 'FOO', sir. Have a nice day!
$injector: (Passing foo to someone.)
sometwo: Hey, Mr. $injector, could I get some 'BAR' here?
$injector: Sure thing.
$injector: (To itself: They need 'BAR'. I don't have a 'BAR' yet, let's create one. How do I create 'BAR'? Aha, I just var bar = barFactory(/* any arguments are resolved through DI */).)
$injector: There is your 'BAR', sir. Have a nice day!
$injector: (Passing bar to sometwo.)
somethree: Yo, $injector dude, gimme some 'BAZ'?
$injector: Sure thing.
$injector: (To itself: They need 'BAZ'. I don't have a 'BAZ' yet, let's create one. How do I create 'BAZ'? Aha, I just var baz = bazValue.)
$injector: There is your 'BAZ', sir. Have a nice day!
$injector: (Passing baz to somethree.)
somefour: Could I get some QUX, please?
$injector: Sure thing.
$injector: (To itself: They need 'QUX'. I don't have a 'QUX' yet, let's create one. How do I create 'QUX'? Aha, I just var qux = /* some stuff that are outside the scope of this comment */.)
$injector: There is your 'QUX', sir. Have a nice day!
$injector: (Passing qux to somefour.)
somefive: So, $injector, my old friend, here's the thing: I need some 'FOO', some 'BAR', some 'BAZ' and some 'QUX'.
$injector: Sure thing.
$injector: (To itself: They need 'FOO', 'BAR', 'BAZ' and 'QUX'. Hey, I already have all of them - how convenient.)
$injector: There is your 'FOO', your 'BAR', your 'BAZ' and your 'QUX', sir. Have a nice day!
$injector: (Passing foo, bar, baz and qux to somefive.)
(Yes, Angular components do speak to each other like this :grin:)


Fix parsing of descriptions

Fixes #315.

@tonyghita Can you take look at this. It is fairly trivial and would fix our docs issues.

Thank you for your contribution!


Fixed Some 301 redirects

Fixed some 301 Redirects by replacing with url suggested in travis

Closed due to PR #844  Fixed all 503 and 404, that fixes even more issues


Request code example for using this widget with ModelAdmin

Thanks in advance.

Define your form first:
from taggit_labels.widgets import LabelWidget

class ContentForm(forms.ModelForm):
    tags = TagField(required=False, widget=LabelWidget)
    class Meta:
        model = Content

And then use this form in your ModelAdmin class.

@bennylope appreciated for your reply.


Add capture/3 to do partial capture

Example
Stripe.Charge.capture("xxx", amount: 30000, [])

Not only for partial capture, but also take the data into account.


Fix incompatibilities with upcoming Bazel 6.x

@bazel_tools//platforms was soft-deprecated, but in Bazel 6.0.0 it's now hard-deprecated (results in a build error, saying to migrate to @platforms). It appears @platforms is supported at least as far back as 3.0.0, maybe earlier, so I figured it's probably not worth supporting earlier versions.
JDK8_JVM_OPTS will be removed in Bazel 6.x. I replaced it with the latest flag value as of Bazel 5.3.1. Not exactly sure if this is the right approach, but it at least unbreaks the build that I tested in our BuildBuddy repo. Need to test with a Java action before submitting.

Fixes https://github.com/buildbuddy-io/buildbuddy-toolchain/issues/5


FF 65: break-* now available

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/65#CSS

The break-* properties have been implemented, and the legacy page-break-* properties have been aliased to them (bug 775618):

break-before is now an alias for page-break-before.
break-after is now an alias for page-break-after.
break-inside is now an alias for page-break-inside.

https://bugzilla.mozilla.org/show_bug.cgi?id=775618

Thanks!


is not escaped

simply add - to the regex match string will resolve this

https://github.com/sindresorhus/escape-string-regexp/issues/9


Backport 2.1: Renaming "new" variable

Description
Backport of #1783 to mbedtls-2.1.
Renames a variable called new to new_cert to avoid using a C++ keyword.
Fixes issue #1782.
Status
READY
Todos

[ ] Tests
[ ] Documentation
[ ] Changelog updated
[ ] Backported

retest


adding nyc picking demo

Demo that highlights individual buildings from the NYC tileset on hover, and selects them on click.
Is this what you were looking for @lilleyse ?
Code based on @mramato 's NYC demo.

Yup this is great! I'm going to merge this into a new 3d-tiles-demos branch.


Update README.md with testing instructions

This change is

I wasn't sure whether or not if we wanted to put the environment variables directly into the readme given the public nature of their contents.


Do TVLQR and MPC on pendulum with Bilinear controller

[ ] Solve pendulum swing-up with ALTRO
[ ] Track pendulum swing-up with bilinear TVLQR
[x] Track pendulum swing-up with bilinear MPC

Test Trajectories

Comments
These were obtained by running a handful of ALTRO trajectories with different parameters to get a variety of different trajectories.

Training trajectories: 400
Trajectory discretization: dt = 0.05, tf = 4.0 sec (81 knot points)
Basis functions: state, sine, cosine, chebyshev(4)
Regression: L2 regularization with weight of 1.1 (solved using a sparse Cholesky decomp)
Train error: 0.00756 (error is average L2 error between nonlinear and bilinear dynamics)
Test error: 0.0673
MPC horizon: 2 seconds (41 knot points)
Solved using OSQP
Have to update the constraint matrix for each solve, since the linearization changes


Improve Developer Experience when debugging

We have a guide for debugging issues here https://github.com/styled-components/vscode-styled-components/blob/master/CONTRIBUTING.md
A launch file should help with this so contributors can just hit launch with it being set up.
I don't know why lib is hidden but I've had to look at it sometimes to see what's going on, I don't see what the benefit of hiding it. VSCode will grey it out.

Support sourceMaps in tsconfig.json
Don't package .map files into final NPM package
Support launch file for debugging
Show lib directory
Start the watcher automatically when debugging.
Fix broken github actions badge

@mjbvz this is ready for review