another program has changed the wallet.

another program has changed the wallet.private keys can't export，all about private stoped updates
.and i can't send bitcoins

MultiBit keeps track of  the size and creation date of the wallet and wallet info file to check that it is the only process changing these files. If you try editting these files or sharing them on a network drive it won't like it.
You can restart your copy of MultiBit and it will clear this condition. It will still keep checking the size and creation date though.

How to solve。it is show i have bitcoins ,but i don't send to any one.my private key have password.so i can't import to blockchain.info.There are other ways to get back my bitcoins?

check private key.also show stoped updates.

This may have been closed in error by @taacboy. Re-opening...

Update stuck

Has been updated for a day

Still have to wait.？

 i restart now like this

We cannot read Chinese so Chinese screenshots don't tell us much. Sorry !
If you are not connecting and syncing successfully try:

checking your computer date is correct. If it is wrong you won't sync fully
check your network/ router is ok and port 8333 is connecting to the Bitcoin network ok

Closing due to inactivity.


emacs: allow disabling compressed install

Description of changes
See https://github.com/syl20bnr/spacemacs/issues/11585 and
https://mail.gnu.org/archive/html/emacs-devel/2022-08/msg00234.html
for motivation.
It's common for Emacs configs to have a line such as
(setq file-name-handler-alist nil), which optimizes early loading of packages,
until a further point where the variable is restored. Both Spacemacs and Doom
Emacs do this. However, it means anything other than plain text (e. g. compressed
.el.gz files) cannot be understood by Emacs until the value is reset. It used to
due to a bug where compressed files where treated differently regardless of
file-name-alist, but that's recently been fixed, breaking compressed install
such as nix's with a cryptic (void-variable \233) error. This not an issue for
the Emacs 28 present in this repo, but emacs-overlay has been broken for quite
a while now.
This allows the user to opt out of compression, making the optimization work again.
It should probably be mentioned in the manual or emacs-overlay as well.
Things done

Built on platform(s)

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

[ ] 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.11 Release Notes (or backporting 22.05 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.

@LuigiPiucco This was done in https://github.com/NixOS/nixpkgs/pull/267946 so I guess this can be closed now.


chore: don't use deprecated docker funcs

Codecov Report
Patch coverage has no change and project coverage change: -48.01% :warning:

Comparison is base (ecb02cc) 60.14% compared to head (53b78c2) 12.13%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #802       +/-   ##
===========================================
- Coverage   60.14%   12.13%   -48.01%
===========================================
  Files          48       48
  Lines        3914     3914
===========================================
- Hits         2354      475     -1879
- Misses       1267     3368     +2101
+ Partials      293       71      -222

Flag
Coverage Δ

integration-test
12.13% <0.00%> (-48.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

pkg/utils/docker/command.go
0.00% <0.00%> (-60.00%)
:arrow_down:

pkg/utils/docker/copy.go
0.00% <0.00%> (-50.00%)
:arrow_down:

pkg/utils/docker/docker.go
0.00% <0.00%> (-50.00%)
:arrow_down:

... and 37 files with indirect coverage changes

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


Problem in the Russian Lessons Javascript Internal

In the Javascript First Steps on Russian bad link to second Lesson "The first Splash into Javascript",
because she send to first Lesson "What is Javascript". Сertainly, i'm understand how open the Lesson, you just need to change language to English, open necessary lesson and change to Russian conversely, but other begginers may don't know about it and miss important knowledge part.
Please, change with link in Russian part. Thank you!

OK, this is now fixed!


Make it easier to debug log parsing

c.f. http://stackoverflow.com/questions/42653362/sematext-logagent-debugging-patterns

To debug patterns you could use the logagent cli:
e.g.
cat test.log | logagent --stdin -n radius.log -f /etc/sematext/patterns.yml
There are some more options for logagent that might help, like --verbose.
https://github.com/sematext/logagent-js/blob/master/docs/cli-parameters.md
e.g.
cat sample.log | logagent -c /etc/sematext/logagent.conf --stdin -n 2017-05-23.log --verbose

Setting 'debug: true' in patterns.yml prints detailed info about matched patterns.
https://github.com/sematext/logagent-js/blob/master/patterns.yml#L36

Prints to console or some log?

Prints to the console (stderr, so It does not interfere with UNIX pipe for stdin/stdout).

I couldn't find any info about this in the docs.  Should we add it to http://sematext.com/docs/logagent/config-file/ ?
Maybe also to http://sematext.com/docs/logagent/parser/ ?
And maybe this could be the beginning of http://sematext.com/docs/logagent/faq which doesn't exist yet?

Available in  http://sematext.com/docs/logagent/faq


Build error

Hi,
I've tried to compile the source, the result is:
# make
g++ -I .  -Wall -Werror -O3 -c -o ServerArgsBase.o ServerArgsBase.cpp
g++ -I .  -Wall -Werror -O3 -c -o xthread.o xthread.cpp
g++ -I .  -Wall -Werror -O3 -c -o shared_data.o shared_data.cpp
In file included from udp_proxy.h:3:0,
                 from shared_data.h:5,
                 from shared_data.cpp:1:
buffer.h: In member function ‘global::Buffer::operator bool() const’:
buffer.h:89:11: error: cannot convert ‘const boost::shared_array<unsigned char>’ to ‘bool’ in return
    return buf;
           ^~~
Makefile:44: recipe for target 'shared_data.o' failed
make: *** [shared_data.o] Error 1

What would be the problem?
Thanks,
a.

Fixes :)
In buffer.h:89:
return (bool) buf_size;
In Makefile change -lpthread to just -pthread. Changing -O3 to -Ofast gave me about 1-2ms less latency, probably it's about Boost heavyweight approach when dealing with vectors :(

Thanks for the fixing, and I've updated the code. This tool is out of maintenance for years(sry...) and it was based on relatively old g++ and boost lib, hope it works well :)


What is your version of pytorch

What is your version of pytorch

torch 1.0.0
Is there anything wrong with other versions?

torch 1.0.1
torchtext 0.2.3
I have preprocessed the data successfully. But when I train the model, I got this error:

You can try torchtext 0.4.0.

Thanks, that worked! When I train it, I set the batch_size to 1, knl_seq_length_trunc to 200, but I still got a RuntimeError: CUDA error: out of memory (Tried to allocate 97.75 MiB (GPU 0; 10.91 GiB total capacity; 1.64 GiB already allocated; 67.38 MiB free; 125.27 MiB cached) Is this a matter of code, or GPU size?

Thanks, that worked! When I train it, I set the batch_size to 1, knl_seq_length_trunc to 200, but I still got a RuntimeError: CUDA error: out of memory (Tried to allocate 97.75 MiB (GPU 0; 10.91 GiB total capacity; 1.64 GiB already allocated; 67.38 MiB free; 125.27 MiB cached) Is this a matter of code, or GPU size?

You can set batch_size to 1024 and accum_count to 32 if you use 1 GPU. It's ok on one GTX2080ti GPU with a memory of 11GB.

I also get OOM, but setting batch_size to 1024 and accum_count to 32 also doesn't  work.
My GPU is GTX2080ti GPU (single). Is there any other way without affecting the effect?

OOM occurs every time the verification set is read. Training does not.

OOM occurs every time the verification set is read. Training does not.

Can you try batch_size 512 and accum_count 64?

When training, I was stuck in this point for a very long time and I don't know the reason, could you please help me?

When training, I was stuck at this point for a very long time and I don't know the reason...

When training, I was stuck at this point for a very long time and I don't know the reason...

What's your config?

batch size 32
accum_count 16
data: cmu_movie

batch size 32
accum_count 16
data: cmu_movie

How about report_every and valid_steps?

100, 1000, respectively
All other configuration are as same as the original one.

100, 1000, respectively
All other configuration are as same as the original one.

Please don't set batch_size too small. Note that the batch_type in the config file is tokens (not sents).

I have updated the configs. Add the valid_batch_size: 8. The default valid_batch_size is 32. That's why there is an OOM during validation.

Thanks for the reply, now I have no OOM error but I'm still stuck here with this warning

Thanks for the reply, now I have no OOM error but I'm still stuck here with this warning

You can try the newly updated config. The warning is inessential.

Thanks, it was training very slow and I didn't see any logs, which made me wonder if it's stuck... One step takes maybe a few minutes.
The size of my training data is around 80000, if I set batch size 4096, it will take no more than 20 steps to run one epoch. I see the default training steps is 20000, I'm wondering how many epochs will it take before the model converges?

Thanks, it was training very slow and I didn't see any logs, which made me wonder if it's stuck... One step takes maybe a few minutes.
The size of my training data is around 80000, if I set batch size 4096, it will take no more than 20 steps to run one epoch. I see the default training steps is 20000, I'm wondering how many epochs will it take before the model converges?

The batch_type in the config file is tokens (not sents).


Adding GPUImageView on OSX crashes

Hey All,
In the past I have made several iOS GPUImage projects. This is my first OSX GPUImage project. Currently I am modeling my project after the SimpleVideoFIlter project. Any time I add a GPUImageView to my ViewControllers view, programmatically or via the storyboard, the app crashes. The app is constantly crashing on line 30 of runSynchronouslyOnVideoProcessingQueue with the error below.
2015-04-26 23:04:25.858 Duckhunt[10537:680723] *** Assertion failure in -[GPUImageView lockFocus], /SourceCache/AppKit/AppKit-1344.72/AppKit.subproj/NSView.m:7612
2015-04-26 23:04:25.867 Duckhunt[10537:680723] An uncaught exception was raised
2015-04-26 23:04:25.867 Duckhunt[10537:680723] -[GPUImageView(0x100709310) lockFocus] failed with window=0x6000001e0400, windowNumber=-1, [self isHiddenOrHasHiddenAncestor]=0

My desired view hierarchy is RootEntry->NSWindow->NSViewController->NSView->GPUImageView
UPDATE - WORKAROUND:
I have stopped trying to add the GPUImageView via the storyboard.
Calling initWithFrame on the GPUImageView causes the crash above, but calling init does not.
For now I am using the code below and the GPUImageView is behaving nicely:
// Causes Crash
//self.cameraView = [[GPUImageView alloc] initWithFrame:CGRectMake(0, 0, 200, 200)];

// Weird but works
self.cameraView = [[GPUImageView alloc] init];
[self.view addSubview:self.cameraView];
[self.cameraView setFrame:CGRectMake(0, 0, 200, 200)];

Thanks in advance,
Joe

When I use a separate window to house the GPUImageView only, everything works fine. The crash only happens when I try to add the GPUImageView to my apps main window's view.

The iPhone 4s and maybe perhaps some iPad devices will crash if your scheme in Xcode has GPU Logging turned on, the default behavior. This logs fps and other things. It's an apple xcode bug, so just turn it off when using this device.


changes of issue titles are hidden

If an issue is renamed, the normal GitHub UI displays the change chronologically within the issue's main (timeline) view.  However enabling refined-github will cause that change to vanish.  For example, viewing this issue with refined-github disabled:

and then after enabling it and reloading:

@aspiers yup its intended #643

Thanks for the quick reply!
Well this is definitely undesirable behaviour for my usage, so IMHO it needs to be configurable at least.  Also is it documented anywhere?  I couldn't find it.

You can show them again by adding this as Custom CSS in the plugin options:
.discussion-item-renamed {
    display: block !important;
}

Thanks a lot @jdreesen!  But again this needs to be documented - both the default behaviour and the way to disable it.

@aspiers all features have pr's and most can be configured vis the CSS or JS disable.
Please see https://github.com/sindresorhus/refined-github#customization

@yakov116 I'm sorry but I really don't think it makes sense to expect users to search the whole PR database in order to find out that a feature exists, and then expect them to spend time writing CSS or JS to disable it.  That's way too much work for a good UX.
Also, why should this feature remain undocumented when all (or at least a lot of) other features are documented (fantastically well, I might add - I've rarely seen such great documentation complete with animated gifs!) ?  That seems inconsistent to me.
The fix is trivial here: just adding the feature to the readme.md and also how to disable it (this could be put elsewhere and linked to, if it was considered too much bloat for the readme.md.  So I'm struggling to see any good reason not to do that.

@aspiers I am only responding since I would like other users to see this.
While I was on the same page as you when I started using this extension (I needed the renames just like you do). After looking around you will see that it is impossible to satisfy everyone and to document every little thing.
However please read the Readme Selection I have linked.

We're happy to receive suggestions and contributions, but be aware this is a highly opinionated project. There's a very high bar for adding options. Users will always disagree with something. That being said, we're open to discussing things. If something doesn't make the cut, you can build your customized Refined GitHub locally, rather than installing it from the Chrome Store.

It does not take much and you can compile yourself customizing the way you would like it

@yakov116 commented on 9 Aug 2018, 13:26 BST:

While I was on the same page as you when I started using this extension (I needed the renames just like you do). After looking around you will see that it is impossible to satisfy everyone and to document every little thing. (You found the rename however you don't even realize how many other things are hidden. Just take a look at the Css file)

Sure, but I wasn't asking for every single tiny little thing to be documented, just one feature which is a significant change in behaviour.  And you can see from #1473 that my request was so small that the fix is only a single line.

However please read the Readme Selection I have linked.

We're happy to receive suggestions and contributions, but be aware this is a highly opinionated project. There's a very high bar for adding options. Users will always disagree with something. That being said, we're open to discussing things. If something doesn't make the cut, you can build your customized Refined GitHub locally, rather than installing it from the Chrome Store.

It does not take much and you can compile yourself customizing the way you would like it

Sorry, but this is somewhat missing the point.  I'm not trying to say that my preference for having title renames visible is better than other people's preference for hiding renames, and that keeping them visible should be the default.  I'm not even saying that there needs to be a button to disable this feature, or any other changes to the code!  I'm simply saying:

The feature should be documented, to avoid violating the Principle of Least Surprise.
It should also be documented how to disable the feature.

Given that I have already proposed the solution to these in #1473, and given that the solution merely requires adding a single line to readme.md, hopefully merging this will be a no-brainer and we can end this discussion here.

I think we could add a section for the more opinionated features with a quick link to the PR, way to disable and why it was added. Please send a PR for the title renames to be added in the readme and we could discuss the actual approach of how to structure in the readme based on your PR! Thank you!

@hkdobrev I already did that, as mentioned in my last comment 😜

Hiding changes to issue titles has been reverted in 5a55661e2513f21c3f96ca704c5490743f81e562 so this is no longer needed.


SSH port 22: Resource temporarily unavailable

Windows Version

Windows 10 Education
Version: 1708
Build: 16299.64

Windows Store Ubuntu Version

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial

What 's happening:  Similar to #2278 but with a twist. Upon opening a fresh terminal, initial attempt at connecting to remote server via SSH will be successful. Any further requests to any other remote server via SSH (no matter if same or different server), will fail with error
Resource temporarily unavailable

Open a new ubuntu shell
SSH connect w/ keyfile initially  - Okay
Disconnect
SSH connect via any method, any server - Fails

SSH works each time when wrapped in strace command. I discovered this while creating the strace gist.
Example Output Gist
STRACE output

What's wrong / what should be happening instead: It should connect

As a test, I've tried running the ssh commands through different tmux windows, and when doing that, they never work, not even the first try.
This is really hindering the usefulness of WSL with very flaky ssh


Optimize multi-column full sort

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] others

Optimization
The major optimization is changing multi-column sorting algorithm from LSD Algorithm to Incremental Sorting.
As LSD Sorting:

Given column a, b, c
Sort c first, then stable sort b, then a
The whole cost is M * N(log(N)), M is column numbers, N is row numbers
This is very expensive when sorting multiple columns

Incremental Column Sorting:

Given column a, b, c
Sort column a, and equal values are grouped together, which is called they have tie
Then sorting column b, need only sort rows that are equal on column a, so algorithm complexity is much reduced
Then sorting column c

The correctness is very easy to understand, so next we will focus on the performance.
How to efficient record equal ranges for the next column?
A basic approach is just record ranges in a vector, and pass it to the next column sorting. But which could cost much more memory than the column itself when many fragmented ranges exist.
So we could simply record the equality between consecutive rows, using 0, 1, 1, 0, 1, 0 like representation. The 0 means it's not equal with previous row, and 1 means it's equal with previous row. This representation is so called tie.
As a result, only N bytes even bits is needed to record the equality of column. Then the equal range could be calculated through iterate continuous 1s. And this procedure is very fast when SIMD optimization is employed.
How to sort a single column?
At first, we employ the permutation approach to sort data out-of-place, instead of in-place.
Permutation is just pointers to data items, and sorting is just rearrange permutation without disturbing the data.
For memory efficiency, we introduced InlinePermutation representation, which inline the short value into the permutation item, such as int32, int64, varchar. As a result, the sorting procedure don't need to redirectly access memory through permutation.
How to inline the comparator?
The dominated bottleneck of sorting procedure is data comparing. If using a plain virtual function to compare data in Column, the bottleneck will concentrate on the virtual/non-virtual function call.
So we employ the templated comparator approach, which could be easily inlined into the sorting procedure.
The sorting procedures likes: ChunksSorter -> Column::sort_and_tie() -> sorter_and_tie_helper()

Column::sort_and_tie is just a virtual function, construct the comparator and call the workhorse
sort_and_tie_helper is a template function, inline the comparator

Experimental Result

Test variables: num chunks(64 to 4096, each chunk has 1024 rows), num columns(1 to 8), data type(int and varchar)
In chart, x-seris is num_chunks/num_columns, y-seris is sorting speed, higher is better
The first chart is sorting integers, and the second is sorting short strings
The blue line represents Incremental Column Sort, the green line represents LSD Column-wise Sort
As result shows, in all scenarios, the Incremental Column Sort could beat the original implementation
(Row-wise sorting is ignored, which is too slow)

Future work

Further test this optimization, and remove deprecated RowWise and ColumnWise sorting implementation
Optimize memtable sorting, which is all-most identical with ChunksSorterFullSorter

run starrocks_clang-format

run starrocks_be_unittest

run starrocks_clang-format


improve automation of routine tasks during PRs

Usually to create the change log, information is gleaned by reading through each pull request with a certain milestone, and filling in the change log excel spreadsheet. It would be useful to automate this process more by having the reviewer write a description for each log entry on the pull request (or simply using the pull request title) and having the rest of the information autofilled into a table - like format that could be copied easily over to the excel sheet. From there, we may need to still read through and do some editing, but hopefully much less.
Edit: adding other steps that would be helpful to automated as part of the PR process:

Change log creation
opening doc, r4ss, and/or SSI issues resulting from the PR
Linking the PR to a milestone
Linking the PR to an issues using github's dropdown menu

I think improving automation of routine tasks could occur in 2 github actions. The next step would be mocking this up in a sandbox repo.

Upon opening a PR:

Link to the issue as provided within the template.  (this means that upon merging in the PR, the issue will be closed; this is usually, but not always appropriate, so we may need to consider carefully).

Upon merging a PR:

Open issues in doc, SSI, and r4ss repos, as the PR's first comment indicates.
Adds the change log info into the excel change log, as the PR's first comment indicates
Add the PR to the milestone we are currently working on

Working on mocking up the steps here: https://github.com/k-doering-NOAA/test_github_site/blob/main/.github/workflows/test-link-issue.yml
It's taking a little while because I'm having a hard time finding examples of exactly what I want to do, so figuring out the specification of the script through trial and error, but making progress. The most helpful links so far are: documentation to the github api and readme for this github-script action

https://github.com/nmfs-stock-synthesis/stock-synthesis/pull/345 opens a pull request with a workflow that will automatically open issues. Still to add on to this:

[ ] Automatically adding a milestone to issues
[ ] Automatically closing issues
[ ] Automatically adding a milestone to the PR
[ ] Updating the change log

Closing this since the work to automatically open issues was merged in and newer, more specific issues that could be worked one at a time were created.

@k-doering-NOAA, it was a pleasure to see the new github action automatically create an issue: https://github.com/r4ss/r4ss/issues/713 upon merging this PR: https://github.com/nmfs-stock-synthesis/stock-synthesis/pull/349.
You noted in https://github.com/nmfs-stock-synthesis/stock-synthesis/issues/348#issuecomment-1184849578 "The issues are created when the pull request is merged in rather than when it is created".
I wonder if it would be even more useful to create the issue in the other repo when the PR is first created, rather than when it's merged? The issue wouldn't necessarily need to be resolved in the other repository before the PR gets merged, but it could be useful to have an issue where discussion of the necessary changes could take place before the SS3 issue is completed.

Yes, we could change it if that seems better! The reason I did it on merge was that sometimes features change after the PR is opened, and I was thinking maybe the options of what needs to be updated may change...
However, I'm open to modifying the build trigger to be when the workflow is created, as I see what you mean!

I reopened this issue in July to propose a refinement (opening issues in other repos like r4ss upon creation of the Pull Request that impacts them rather than after it gets merged). That refinement was added shortly thereafter but as usual I forgot to circle back to close the associated issue.


Add option to dynamically specify a list of labels to be added to created PRs

I see adding labels is possible by using the config file but it would be neat to be able to specify labels at runtime with a parameter.
It might also be good to have two modes to do this, one for replacing the label list (eg only using the provided list) and another for providing additional labels to any already defined in the config file.

This is now mostly possible after https://github.com/sqren/backport/pull/115 has been merged.
You can do
backport --branch 6.0 --upstream elastic/elasticsearch --labels myLabel

Note: this will replace any labels specified in .backportrc.json config file. I can probably add an option like --append-label - or would it be better if --labels appended automatically instead of overwriting?


Create github and homebrew releases using the deploy queue

The deploy-legacy queue is deprecated, and we're slowly moving steps off it.
This moves the final two release steps off the deploy-legacy:

creating a release on github, using our github-release binary
updating https://github.com/buildkite/homebrew-buildkite with the new version

Both steps are relatively straight-forward. All the required tools are in the deploytools image and they both require the same credential (a github API  token), so I've migrated them at the same time.
I've tested them both in dry-run mode and I'm fairly confident they'll run successfully on the new agents. However, it's hard to be 100% sure until we're ready for a real release.

/cc @pda @chloeruka


Visibility condition on address question no functioning

Describe the bug
A draft form has a visibility condition set on a previous address question. The visibility condition should hid a static text question later in the form if both conditions are met. This is not functioning properly.
There are two drafts of the Homewise Weatherization program. The problem described in this issue is in V2 as shown in the program admin note.
Here is an image of the visibility condition.

To Reproduce
Step 1: Applicant must answer a series of four questions before arriving at the address question. In this example I use the address for Seattle City Hall.

Step 2: After three more question the applicant is asked to enter their heating type. In this example, I select "gas".

The expected behavior at this point is to let the applicant continue with the application. The static text message after this series of answers should be hidden.
However, the static text is shown incorrectly telling the applicant they are not eligible for the program.

Expected behavior
Static text should be hidden with the current visibility condition.

We had gated eligibility off, and we enabled it. @Miguel-314 if this is still a program re-open the issue.


The pre-trained model on google drive is damaged

I downloaded the pretrained model but it can't be opened.
Could you fixed the problem?
Thank you!

I can't turn on the pretrained model.
Sorry.
But I try to download the ResNet101 in Pytorch official website.
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年1月10日(星期五) 下午3:39
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS>主题: [jfzhang95/pytorch-deeplab-xception] The pre-trained model on google drive is damaged (#153)
I downloaded the pretrained model but it can't be opened.
Could you fixed the problem?
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Could someone provide the pretrained model that can be decompressed normally?

Just run mv deeplab-resnet.pth.tar deeplab-resnet.pth to remove the .tar extension in the file name. The file is not even a tar file at all, just a simple PyTorch checkpoint file.

but the deeplab-resnet.pth cannot be loaded.there is a error

I confirm I can load the .tar with torch.load (1.6)


ContentType.resetEntryEditor not available in type definitions

Expected Behavior
ContentType should have the type definition for resetEntryEditor as per https://github.com/contentful/contentful-migration/blob/master/src/lib/migration-steps/index.ts#L452.
Actual Behavior
Get the typescript error "Property 'resetEntryEditor' does not exist on type 'ContentType'.ts(2339)".
Possible Solution
Add type information for function.
Steps to Reproduce

Create a migration script which creates or edits a ContentType
Call resetEntryEeditor on that ContentType reference
Try to compile with tsc

Context
Environment

Node Version: v14.19.3
Package Manager Version: yarn 1.18.0
Operating System: Arch Linux
Package Version: 4.8.1

This ticket has been closed due to inactivity. If you still need help resolving your issue, please reach out through our community Slack, or contact Contentful support directly.


How can I take a few items?

Hi, how can I take a few items? Tried so, but take one item:
foreach ($itemsPlayer as $item) {
    $trade->addOtherItem(730, 2, $item);
}

Try hardcoding to test it:
$trade->addOtherItem(730, 2, 'ASSET_ID_HERE');
$trade->addOtherItem(730, 2, 'ANOTHER_ASSET_ID_HERE');
$trade->addOtherItem(730, 2, 'YET_ANOTHER_ASSET_ID_HERE');


Load "linked" contract in repl

With the current repl command, is easy to start the repl and load a contract given its address and ABI:
eth repl erc20@0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359
# or
eth repl
> .loadc erc20@0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359

But sometimes a contract has a related address which can be obtained with a state variable or method. In that case you have to load the first contract, consult the related address, and load the second contract (this can be done inside the repl with loadc, or you have to close the repl and open it again with the second contract).
It would be nice to have a easier way to do this.
Option 1: Extend the repl command syntax
This would work like this:
eth repl<EMAIL_ADDRESS><EMAIL_ADDRESS>
That is: the first contract has a variable (or view method without parameters) called other that returns an address, and myOtherContract is the ABI for that related contract.
While this could work, I have some concerns:

I've been wanting to extend this "syntax" for a while, to allow the user to name the loaded contract. Something like eth repl erc20@0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359:dai. This potential new syntax and the one for related contracts are compatible, but I'm not sure about converting this into a sort of DSL.
Sometimes the related address needs an argument. The obvious example is when you have an array with addresses. And while you could do something like eth repl<EMAIL_ADDRESS>myOtherContract@myContract.others(0), I think that's going too far into the weird zone.

Option 2: Make .loadc accept promises
My first alternative was something like (inside the repl):
.loadc myOtherContract myContract.methods.other().call()

This would solve the problem when the method that returns the address has parameters. The problem is that it's not arrow-up-able (a word I just made up and that means "you can't reuse the shell history easily"). Also, the .loadc syntax, like the one for repl, uses @, but I actually don't like that, so I'd be fine with using a plain whitespace instead.
Option 3: Improve conf
This is not solving the described problem, but maybe it resolves the underlying problem: not wanting to remember and/or copy and paste a lot of addresses. If conf could be used for saving contracts addresses (and perhaps even address/ABI pairs, think eth repl dai), maybe that would be enough.
Option 4: Save repl state
Alternatively, add a command that you can use to preserve variables between repl sessions. This would be useful for other things too, but I'm afraid that you couldn't really save contract instances because they are not serializable.

I think a combination of 3 and 1 would be the best solution, if that is not possible I vote for 3 or 1.


It is possible to provide a dist version ?

Hi,
React, React-Router, Redux, Redux-Logger and more libraries have a compiled version under the dist folder.
It is possible to provide us a redux-connect.js and a redux-connect.min.js under the dist folder ?
This would be very useful !
Thanks you !
Nicolas

@nicolashemonic could you elaborate more on your use-case?

It should be nice to have an optimized and ready to use version.
I close this issue and let you add this feature in the future if it is very demanded.

I dont see a lot of demand for it, but a pull request is welcome. I would this to be a part of build script, so that it can be created automatically and committed only to tagged versions and not main source code (otherwise it's too hard to read diffs)
Thanks for bringing this up


[placement] Add table endpoint

Description
Add the tables endpoint to get placement tables to the health check http server(the sidecar metadata endpoint is also added to the health check server).
As this behavior has not been discussed, I'll backfill tests if acceptable.
Issue reference

Please reference the issue this PR will close: #6033
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

That is a fine solution. I would have an environment variable to disable that endpoint for users that think it exposes information in an unauthenticated endpoint.

@Taction LGTM, but:

Looks like there's a linter issue 🥲
Just want confirmation from a maintainer on what the endpoint should be

That is a fine solution. I would have an environment variable to disable that endpoint for users that think it exposes information in an unauthenticated endpoint.

Add metadata-enable command line flag and DAPR_PLACEMENT_METADATA_ENABLED env to define if expose this endpoint(flags take priority over env variables).


should we add hdc nodes to 8routers and 3routers topologies?

Hi @cscarpitta, good question!
I would not waste time with 3 routers topologies, while I think it is good to add hdc nodes to 8 routers topologies... so we can show some hosts that are capable to ping each other from the start (with no need to create the tunnels)


Replace SYNTH_DRIVING_CELL with size 2 inverters

As it stands, the size 1 inverters are the SYNTH_DRIVING_CELL for all SCLs. Problem is, they're also on the no synth list.
See https://github.com/The-OpenROAD-Project/OpenLane/issues/692

Pulled and merged.


enable whisper batch for long sequences

long batch inference works now

"whisper refactor 2" is a pr title with very little information and that makes it less likely for someone to review and merge
it's a big diff with very little test changes (not even run in CI). is this pr the minimal to make test work? mixing refactor and behavior change is hard to review and time consuming

I understand what you mean. I do also think this pr is a clear win since it reduces lines while providing better functionality

i rolled back some small refactors to reduce diff

tested locally and test passed and will merge this one. i think it would be nice to make the tests work in CI too


Smooth existing solutions

We frequently find greedy solutions from imperfect states. In AV2, these are like: "go to spot, deploy drone, go to other spot, recall drone, go to third spot" or "do long deploy action to move to spot, get map visited item, recall drone, (do other stuff...), do long deploy action again".
We ought to be able to examine such a string of history and reach a subsequent state faster than the original discovered, but the regular search has not obviated that solution yet. Our current version of this is to just insert into the queue the intermediate states, but this doesn't work very well if the states are never picked up. This would help us find better solutions earlier on.

Oops, I just realized that the optimized sequence of states still has the skips of each location, so of course adding them to the queue just results in a ton of dead-ends.

We might revisit this later when a game graph is more complete, but for now having a route defined accomplishes the same original goal of having a good solution to start from (and use as a time limit).


Replace build system

What is the context of this PR?
This replaces the webpack build system with a simpler gulp one which:

Is easier to read and maintain.
Incorporates a custom dev server for fast previewing of edits to stylesheets, scripts, and templates.

How to review
Try out all of the yarn/npm scripts and compare against the behavour of the webpack build system.
More information
No alternative has been added for the webpack bundle analyzer plugin.

Closing and re-opening PR to see if GitHub detects the other checks.


Update webhook registration example following resource name change

https://github.com/hookdeck/terraform-provider-hookdeck/blob/main/examples/resources/webhook_registration/resource.tf

Fixed in https://github.com/hookdeck/terraform-provider-hookdeck/pull/41


Latest Docker Image does not work with CLI

Steps to repro:

flow emulator
docker run ghcr.io/onflow/fcl-dev-wallet:latest

The docker run seems to work fine, and yields : ready - started pm server <IP_ADDRESS>:8701, url: http://localhost:8701
But running curl http://localhost:8701, yields not found.
Our only suspicion for why this is the case, is because we believe that the keys that our emulator-account is using are different than the keys that are in the config files in the latest image. But, this is surprising because running the docker command above gives a successful "ready" result.
We would greatly appreciate some help with getting this working!

hey @samwise2, I think you need to expose port with docker.
https://docs.docker.com/config/containers/container-networking/

Awesome, thanks @bluesign that worked! Can we get the README updated with:
docker run -p -p 8701:8701 ghcr.io/onflow/fcl-dev-wallet:latest so that people don't run into this in the future?

Or at least some comment on this

@samwise2 sure I think Flow Team will see the issue and they will update. Just incase I am tagging @10thfloor

Great, thanks

Looks like this has been addressed.


Terminal: Zsh history on up arrow press not functioning as expected

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.61.1
OS Version: macOS 11.6.0

So part of my normal workflow is typing "ya" and then pressing up arrow for yarn commands, "ga" for gatsby, etc etc. A very useful Z shell feature. But today after updating to 1.61.1, this no longer works as expected and just works like normal bash history. This is still working as normal outside of VS Code.
Steps to Reproduce:

Open a terminal.
Start typing a command you have used before.
Press up arrow key on keyboard.
Expected zsh behavior (history-beginning-search-backward, or history-beginning-search-forward for down arrow key) not occuring. Instead of showing only the history matching what I have typed already, it just shows the previous command run.

Turns out it is actually not happening just on VS Code ... my bad.


⚠ Bofrost.nl has degraded performance

In 2ed422b, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 914 ms

Resolved: Bofrost.nl performance has improved in e87910f.


[1.21.1] Wrong required minecraft version number

required minecraft version in fabric.mod.json in FancyHealthBar-1.1.1.jar currently is 1.21, which is supposed to be 1.21.1

Latest version of the mod is supposed to be for only 1.21, looks like I forgot to remove 1.21.1 from version list while releasing the new version. I'll release a 1.21.1 port in a few minutes


HIP draft - Helium Hub

Rendered View:
https://github.com/anthonyra/HIP/blob/ara/helium-hub/0062-helium-hub.md

This HIP draft has been numbered and merged for discussion as HIP 63.
Please direct future questions & comments to the new tracking issue: #423
If you are one of the named authors, please include #423 in future pull requests to have them automatically merged.


Take over the original Vibrant.js project?

Hey, as there's no way to contact you @akfish (I can't find your email address), I figured I'd just file a issue here.
Your version of vibrant is obviously superior to the original, so I wondered if you'd be interested in taking over the project and maintaining it.
You can either take over the repo as it is (I'd add you as a maintainer and you'd redirect from node-vibrant to my repo or something), or I could just add a large warning that I'm abandoning it and people should use yours instead, your call.
Hope you will consider it! I still have a lot of people filing issues in mine, but I just can't be bothered, knowing your far better version exists (which is why I'm abandoning mine).

@jariz and I just discussed this over email. We decided to deprecate vibrant.js. Future development and maintenance will be happening.
I'll keep this great project started by @jariz alive.😀


update the setup instructions

The readme had laughable setup instructions. Laughable as in how funny it was that the gradle instructions were incorrect/incomplete :-)
This pr adds proper build.gradle configurations
close #196

@sav007 updated with feedback, thanks!

+1, thanks :)


Update text in boxes on homepage

Please update the text in the boxes for "Learn about the source" and "Get directed". Text pasted below for ease.
Learn about the source
Each source comes with information to help you understand what fields are part of the datasets and if it includes documents.
We have also included information on any known data quality issues and advice on how to access the data.
Get directed
Through the Data Registry, whole OCDS datasets are available to download in bulk.
Data can be downloaded in JSON, Excel or CSV.

We have also included information on any known data quality issues and advice on how to access the data.

Rather than changing the past tense to the past perfect tense, I think it reads better to use the present tense:
We include information on any known data quality issues and advice on how to access the data

Get directed

This heading doesn't make sense to me. The current heading is "Get direct access to the source data", which is clear.

Through the Data Registry, whole OCDS datasets are available to download in bulk. Data can be downloaded in JSON, Excel or CSV.

"Through the Data Registry" is obvious. I'd go with:
Whole OCDS datasets are available to download in bulk, in JSON, Excel and CSV formats.

From https://github.com/open-contracting/data-registry/issues/246#issue-1383141958:

In the " Learn about the source" box, it says, "We also included any known data quality issues and advice on how to access the data."
I think we are not providing advice on how to access the data.
In " Get direct access to the source data": "You can also customize the data fields you need for a more manageable dataset."
That is not true at the moment.

I agree that "advice on how to access the data" is not quite right/clear. Anyhow, that part is covered in the last box, so we can maybe just delete it.

FYI that the registry home page still says 'You can also customize the data fields you need for a more manageable dataset', but as far as I can see that functionality isn't actually available.

Get direct access to the source data

The whole purpose of the registry is providing indirect access to the source data (because direct access involves slow servers etc.), so I've changed to "Get instant access to data"

Original: Information about each data source is provided to help you to understand what fields are available or if there are any documents.

Proposed: Each source comes with information to help you understand what fields are part of the datasets and if it includes documents.

Meta description (for context): Learn about the data source's coverage, features and quality issues.

The proposed text is a bit clumsy (sources don't "come with information"), there's a grammatical issue viz number agreement (source -> datasets), and the use of dataset vs source is confusing. I'll go with:

For each dataset, we describe its source and coverage, at both an administrative level (public bodies, systems and procedures covered) and technical level (fields covered and linked documents).


Unquote path and revision when copying parquet files

close https://github.com/huggingface/datasets-server/issues/1433

Codecov Report
Patch coverage: 100.00% and project coverage change: +1.44 :tada:

Comparison is base (64e84e7) 90.12% compared to head (7c0c37e) 91.56%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1434      +/-   ##
==========================================
+ Coverage   90.12%   91.56%   +1.44%
==========================================
  Files         189       73     -116
  Lines       11190     4589    -6601
==========================================
- Hits        10085     4202    -5883
+ Misses       1105      387     -718

Flag
Coverage Δ

jobs_cache_maintenance
?

jobs_mongodb_migration
?

libs_libcommon
?

services_admin
?

services_api
?

services_worker
91.56% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

.../src/worker/job_runners/config/parquet_and_info.py
77.71% <100.00%> (+0.13%)
:arrow_up:

... and 116 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

nice! Do you think we could have the same bug in other parts of the code? In particular when we write on the disk (assets, etc.)

Do you think we could have the same bug in other parts of the code? In particular when we write on the disk (assets, etc.)

No it happens only when we get the file name out of the URL of the file and we only do it here afaik


SyndicationFeed still contains references to JSPUI and XMLUI

Bug Description
In org.dspace.app.util.SyndicationFeed some references to JSPUI and XMLUI are still present.
Furthermore, OpenSearchController has a reference to SyndicationFeed.UITYPE_JSPUI in
labelMap.put(SyndicationFeed.MSG_UITYPE, SyndicationFeed.UITYPE_JSPUI);

@tdonohue , I can try to fix this problem but I'm not sure if MSG_UITYPE is completely obsolete in DS 7 and can be safely removed from SyndicationFeed? I can confirm that old (DS5) RSS feed URLs do not contain any reference to the UI mode.

@saschaszott : Yes, it appears to me that MSG_UITYPE may be no longer necessary and likely should be entirely removed.

Claiming this as I had time to look into it.  It's a quick fix & necessary to patch soon.  The RSS/Atom feeds are returning invalid URLs for bitstreams (e.g. community/collection logos).  I'll create the PR today.


weave-net-w8fdk and kube-proxy-2mc6t failed to run/restart in kubemaster-01

[this is the status of the pods which are displayed after running the kubemaster-01]
some of the proxy and weave fails to start..and get connected.
kubectl get pods --all-namespaces
NAMESPACE     NAME                                    READY     STATUS              RESTARTS   AGE
default       hello-world                             1/1       Unknown             0          9h
kube-system   dummy-2088944543-qphfc                  1/1       Running             4          13h
kube-system   etcd-kubemaster-01                      1/1       Running             4          13h
kube-system   kube-apiserver-kubemaster-01            1/1       Running             4          13h
kube-system   kube-controller-manager-kubemaster-01   1/1       Running             4          13h
kube-system   kube-discovery-1769846148-1zxv9         0/1       MatchNodeSelector   0          10h
kube-system   kube-discovery-1769846148-7zpvc         1/1       Running             1          9h
kube-system   kube-discovery-1769846148-w1pfb         0/1       MatchNodeSelector   0          13h
kube-system   kube-dns-2924299975-mbzbn               4/4       Running             16         13h
kube-system   kube-proxy-2mc6t                        1/1       NodeLost            2          13h
kube-system   kube-proxy-xrr45                        1/1       Running             4          13h
kube-system   kube-scheduler-kubemaster-01            1/1       Running             4          13h
kube-system   weave-net-cd2k4                         2/2       Running             8          13h
kube-system   weave-net-w8fdk                         2/2       NodeLost            4          13h

It looks like the kubeminon is down? Did you check the status for "kubectl get nodes"
Please re-open the issue in case weave and proxy are not running, after the minion node is up.


Remote Debugging for Isolated mode

The goal is to enable VS to supprto remote debugging for isolated apps
cc: @fabiocav @soninaren

Once all changes are deployed, we can close this item and follow up with VS. I will validate the feature and work on the documentation.

The API work for this was all done. We need to confirm a few final things with the VS folks. This may already be done.

Closing this as the worker/host work has been completed.

Confirmed it's working in latest version of VS and a .NET 7 isolated function.


Read RECORDING Status

Hi,
Is there any way to read RECORDING status from the camera?
I need to turn on an LED based on camera's recording status.

According to http://www.boehmel.de/lanc there is. Feel free to issue a PR that adds this functionality.

Closing as the author seems to have lost interest


[5.6] Use 403 status code for InvalidSignatureException

401 usually refers to authentication, no authorization — so 403 is more appropriate in this case.
This means that the InvalidSignatureException would automatically render the resources/views/errors/403.blade.php template.

In depth discussion on 401 vs 403
RFC2616

This is breaking change btw. Clients behave on status code all the time.


Remanufatered vision module

Here is my idea for the modules Images and Image. Changes:
Image:

Grouped metadata in info dictionary.
Reduced lines in the constructor.

Images:

Grouped metadata in info_image and info_labels dictionaries.
Added iterator to add labels by default when labels=None.
Reduce lines in _process method.

image_test:

Modified tests (42, 44, 78, 79, 172, 173, 174) to validate labels when labels=None or nofile.jpg.
Added fake images to files folder to evaluate two options:

image file doesn't exist in directory. it will raise an error.
image file is corrupted. it will be appended to _errors.

updated module img_tools.py with proper docstring comments and added getters and setter to the module.

I did the pull accept. I suggest do a git pull to be uptodate and then run the image_test again. You may also want to run the vision tutorial notebooks,.


Cannot assign hot keys to specific buttons

OS: Windows 10, Ubuntu 16.04
Issue Descriptions: Can't assign hot keys to "back" and "forward" buttons on Microsoft Ergonomic 4000 keyboard (key codes are 166 and 167).
Steps to Reproduce: Open desktop settings/hot keys. Try to assign any hot key to "back" or "forward" buttons.
Thanks.

These are claimed at an OS level by our application to trigger forward and back navigation inside the app.  We don't allow you to reassign them


Update migrate.md

We're adding the information "A rollback to the old environment will not be possible." at the end of the FAQ question: "What happens to my old App Service Environment?"

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

@auolivei. For future reference, note that Microsoft contributors should generally make updates to content through the private repository so the updates can be staged and validated by the validation rules. See this article for more information.

@seligj95,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. Thanks.
#label:"aq-pr-triaged"

#sign-off


[flake8-type-checking] Adds implementation for TC006

Now that TCH has been renamed to TC and the redirect from TCH006 to TCH010 can no longer bite us, I've added an implementation for this very simple rule.
Summary
TC006 checks for non-string literal arguments to typing.cast which adds unnecessary runtime overhead, since the function doesn't do anything at runtime.
This PR has a very tiny overlap with my other PR for TCH007/TCH008 in flake8_type_checking/helpers.rs for adding the quote_type_expression function, but the two changes don't really depend on one another, so they can be merged in any order.
Test Plan
cargo nextest run

The extra hits for most of the other rules make sense to me, since fixing TC006 can result in subsequent TC001-003 errors.
I have no idea what the extra SIM115 violation is about though.

Thanks for contributing this rule. The code changes look good to me.
I want to wait for updated ecosystem checks. I don't see why this PR should result in any new diagnostics other than TC006.

I'm a bit confused by the ecosystem checks. I understand that we run ruff exactly once and don't apply any fixes. That makes it unclear to me why there would be any changed diagnostics other than for TC006.

I'm a bit confused by the ecosystem checks. I understand that we run ruff exactly once and don't apply any fixes. That makes it unclear to me why there would be any changed diagnostics other than for TC006.

The only way this output makes sense to me is if it does in fact repeatedly apply fixes until it runs out fixes and uses the output from whatever the last iteration was for the ecosystem results. It's also a little sus that there's no +/- on the count of fixes, since these are definitely all auto-fixable. Maybe this was changed at some point without anyone noticing? Because the fixes count was always zero on my other PRs as well, even though they definitely included some new fixes.

Something's definitely broken. Running the two ruff binaries without the ecosystem wrapper script gives me zero changes for pandas.

Something's definitely broken. Running the two ruff binaries without the ecosystem wrapper script gives me zero changes for pandas.

Indeed, I double checked, there's not even any type aliases defined in the first file in pandas. Maybe it's the result of broken caching on the CI side?

I can reproduce the ecosystem differences locally....

I can reproduce the ecosystem differences locally....  So it actually still makes sense. If you apply the fix for TC006, you will get the TC001 errors afterwards, because the file uses from __future__ import annotations, so the only runtime use of those _typing imports happened inside cast statements, so if you quote them, there are none left and TC001-003 triggers.
So I still think ecosystem script applies fixes repeatedly and uses either the state where it can no longer fix things or the state just before it fixed everything for the results.

Ohhhhh.... pandas sets fix = true

I see, ecosystem should probably force that to false then. Although I would see some value in checking for fix circularity issues in ecosystem, but that would require a larger restructure of how ruff is invoked and the results are interpreted.


bug: The clear search button (search page) does not work anymore

@jblom
Issue for labo-components projects solved in branch:
issue/#401-clear-search-btn-doesnt-work
Pull request
https://github.com/beeldengeluid/labo-components/pull/403

@avlisodraude I merged this one, works fine.


Nowpaying command is not working?

General Troubleshooting
Please check off these steps before suggesting a feature or reporting a bug:

[ ✓] I am running the latest version:
[ ✓] I have followed all instructions on the setup page (and if applicable, Raspberry Pi)
[ ✓] I have read through the planned and suggested features

Issue
Issue Type

[ ✓] Bug Report
[ ] Feature Request

Description
I was on a server and i was a staff member but now i am not and when i type in nowpaying it say
But it works on my own server fine why is this happend?

#59

Does the bot have the Embed Links permission in the channel you're running the command in?

yes

Can you see if this is fixed as of the latest release, 0.1.3

Closing as this has been untouched for months and the latest release overhauls a lot of the now-playing logic.


HBASE-28484 Allow replication to different target table

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m  0s
master passed

+1 :green_heart:
compile
6m 26s
master passed

+1 :green_heart:
checkstyle
1m 32s
master passed

+1 :green_heart:
spotless
1m  4s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
7m 30s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 37s
the patch passed

+1 :green_heart:
compile
6m 44s
the patch passed

+1 :green_heart:
cc
6m 44s
the patch passed

+1 :green_heart:
javac
6m 44s
the patch passed

+1 :green_heart:
checkstyle
1m 26s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
7m 47s
Patch does not cause any errors with Hadoop 3.3.6.

+1 :green_heart:
hbaseprotoc
2m  3s
the patch passed

+1 :green_heart:
spotless
1m  8s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
8m  5s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 42s
The patch does not generate ASF License warnings.

66m  9s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5819/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5819

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile cc hbaseprotoc prototool

uname
Linux 2b9ea8acb78c 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / adc79a0a9c

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
82 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5819/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 38s
master passed

+1 :green_heart:
compile
1m 34s
master passed

+1 :green_heart:
shadedjars
5m  9s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 52s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 28s
the patch passed

+1 :green_heart:
compile
1m 32s
the patch passed

+1 :green_heart:
javac
1m 32s
the patch passed

+1 :green_heart:
shadedjars
5m  7s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 51s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 32s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
1m 16s
hbase-client in the patch passed.

+1 :green_heart:
unit
237m 11s
hbase-server in the patch passed.

265m 24s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5819/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5819

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux c7e9eb69499f 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / adc79a0a9c

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5819/1/testReport/

Max. process+thread count
5107 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5819/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 49s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 48s
master passed

+1 :green_heart:
compile
1m 58s
master passed

+1 :green_heart:
shadedjars
6m  5s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  7s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 13s
the patch passed

+1 :green_heart:
compile
2m 16s
the patch passed

+1 :green_heart:
javac
2m 16s
the patch passed

+1 :green_heart:
shadedjars
6m 22s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  0s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 46s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
1m 54s
hbase-client in the patch passed.

+1 :green_heart:
unit
294m 39s
hbase-server in the patch passed.

330m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5819/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5819

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 13bbb20f3af2 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / adc79a0a9c

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5819/1/testReport/

Max. process+thread count
4614 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5819/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

I think we may have more patterns when replication...
For example, we want to replicate a whole namespace and change the target namespace name, we want to replicate all the tables on the cluster but adding a prefix to all the table names, etc.
I do not mean we should support them all in the first place, but we'd better list all the requirements first, and then see whether there is a general enough solution to support them all. So in the future, if we want to add more supports, we do not need to change bunch of existing code, as it is a big pain if we want to change existing data structures...
Thanks.


Display time in logs in password-manager

Password manager does have API logs along with the status code returned, but for further helping in debugging, it would make sense to add the time when the log was generated (in the local time zone of course).

Pushed to master.


Review conventional-changelog and friends

We should consider adding a process that uses these tools to our projects and guidelines.
https://github.com/conventional-changelog/standard-version - Automatic version and CHANGELOG management
https://github.com/bcoe/conventional-changelog-standard/blob/master/convention.md - Commit standards that make CHANGELOG management easily automated
https://github.com/conventional-changelog/conventional-changelog-cli - Generate a CHANGELOG from git metadata (e.g. the standards noted above)

https://www.npmjs.com/package/test-ccsv
Tested our npm script with the correct github user npm init -y.
Also tested the conventional-changelog.
Currently I have only one concern:
Our npm script is creating version 0.0.1, and when we run standard-version, it bump to 1.0.0.
But is working really fine, changelog generated:
https://github.com/panther-js/test-ccsv/blob/master/CHANGELOG.md
More informations about version numbers
https://github.com/conventional-changelog/standard-version/issues/132
https://github.com/conventional-changelog/standard-version/issues/131
Also, according my understanding, it will force us to always fork the projects due squash/merge option on github.

npm-init
https://github.com/bucharest-gold/entente/blob/master/npm-init.js#L55
https://github.com/bucharest-gold/entente/blob/master/npm-init.js#L81
https://github.com/bucharest-gold/entente/blob/master/GUIDELINES.md#release-with-automatic-changelog-generation

@lance this can be closed ?

Integrated to recommendations and npm-init.js here https://github.com/bucharest-gold/entente/commit/b975728004a2359ceb81c97f88e6dcc7108ed04a


contributing steps for building docs result in file not found: my_file.grib.5b7b6.idx

What happened?
I went through the steps in https://docs.xarray.dev/en/stable/contributing.html#how-to-build-the-xarray-documentation
conda env create -f ci/requirements/doc.yml
conda activate xarray-docs
pip install -e .
cd doc
make html

and when I ran make html partway through I get this error. the build still finishes.
updating environment: [new config] 1468 added, 0 changed, 0 removed
Can't create file 'my_file.grib.5b7b6.idx'
Traceback (most recent call last):
  File "/home/rave/miniforge3/envs/xarray-docs/lib/python3.12/site-packages/cfgrib/messages.py", line 538, in from_indexpath_or_filestream
    self = cls.from_fieldset(filestream, index_keys, computed_keys)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/rave/miniforge3/envs/xarray-docs/lib/python3.12/site-packages/cfgrib/messages.py", line 378, in from_fieldset
    return cls.from_fieldset_and_iteritems(fieldset, iteritems, index_keys, computed_keys)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/rave/miniforge3/envs/xarray-docs/lib/python3.12/site-packages/cfgrib/messages.py", line 391, in from_fieldset_and_iteritems
    for field_id, raw_field in iteritems:
                               ^^^^^^^^^
  File "/home/rave/miniforge3/envs/xarray-docs/lib/python3.12/site-packages/cfgrib/messages.py", line 291, in __iter__
    for message in self.itervalues():
                   ^^^^^^^^^^^^^^^^^
  File "/home/rave/miniforge3/envs/xarray-docs/lib/python3.12/site-packages/cfgrib/messages.py", line 267, in itervalues
    with open(self.filestream.path, "rb") as file:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: 'my_file.grib'
Can't read index file 'my_file.grib.5b7b6.idx'
Traceback (most recent call last):
  File "/home/rave/miniforge3/envs/xarray-docs/lib/python3.12/site-packages/cfgrib/messages.py", line 547, in from_indexpath_or_filestream
    index_mtime = os.path.getmtime(indexpath)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen genericpath>", line 67, in getmtime
FileNotFoundError: [Errno 2] No such file or directory: 'my_file.grib.5b7b6.idx'
/home/rave/miniforge3/envs/xarray-docs/lib/python3.12/site-packages/cartopy/io/__init__.py:241: DownloadWarning: Downloading: https://naturalearth.s3.amazonaws.com/50m_physical/ne_50m_coastline.zip

What did you expect to happen?
no errors during make html
Minimal Complete Verifiable Example
# after a fresh clone

conda env create -f ci/requirements/doc.yml
conda activate xarray-docs
pip install -e .
cd doc
make html

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.
[X] Recent environment — the issue occurs with the latest version of xarray and its dependencies.

Relevant log output
No response
Anything else we need to know?
No response
Environment

INSTALLED VERSIONS
commit: de3fce8b9e6926994a52617a8976fe3e29ce2fd8
python: 3.12.7 | packaged by conda-forge | (main, Oct  4 2024, 16:05:46) [GCC 13.3.0]
python-bits: 64
OS: Linux
OS-release: 6.8.0-45-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: ('en_US', 'UTF-8')
libhdf5: 1.14.3
libnetcdf: 4.9.2
xarray: 2024.9.1.dev69+gde3fce8b
pandas: 2.2.3
numpy: 2.0.2
scipy: 1.14.1
netCDF4: 1.7.1
pydap: None
h5netcdf: 1.4.0
h5py: 3.12.1
zarr: 2.18.3
cftime: 1.6.4
nc_time_axis: None
iris: 3.9.0
bottleneck: 1.4.1
dask: 2024.9.1
distributed: None
matplotlib: 3.9.2
cartopy: 0.24.0
seaborn: 0.13.2
numbagg: None
fsspec: 2024.9.0
cupy: None
pint: None
sparse: 0.15.4
flox: None
numpy_groupies: None
setuptools: 75.1.0
pip: 24.2
conda: None
pytest: None
mypy: None
IPython: 8.28.0
sphinx: 5.3.0

I also see this when building the docs locally. I can't tell from the message if this is our fault or the fault of cfgrib upstream?

The error is also raised in RTD. The issue is something along the lines of #6512. We could check if any of the suggested solutions would help.

Discussion in cfgrib: https://github.com/ecmwf/cfgrib/issues/275


[BUG] Old Username Displayed

So I first started using roPresence around the first release but then I forgot about it and just started using it again today and I noticed that it has my old username. Is there any way to logout of Roblox then login again or?

You need to reverify on https://verify.eryn.io


[Question] MorphMany issue

Hi! How can i use polymorph with backpack ?
I have 2 models: ticket and todo
And i have 1 model "image" that have relations with "ticket" and "todo"
"ticket" have relation with "Image":
public function images()
    {
        return $this->morphMany('App\Models\Image', 'imageable');
    }

"Image" have relation with "ticket":

public function imageable()
    {
        return $this->morphTo();
    }

I created Image model table:
Schema::create('images', function (Blueprint $table){
            $table->increments('id');
            $table->string('url');
            $table->integer('imageable_id');
            $table->string('imageable_type');
            $table->timestamps();
        });

When i try to use CRUD in TicketCrudController (I got Exception that array needed, but string sent):
$this->crud->addField([    // Image
            'label' => 'ticket Image',
            'type' => 'image',
            'name' => 'images',
            'entity' => 'images',
            'attribute' => 'filename',
            'model' => "App\Models\Image",
            'upload' => true,
            'disk' => 'uploads',
            'morph' => true,
        ]);

i am getting error
Property [images] does not exist on this collection instance.
any one please help me how i can use it

i am also getting issue
Call to undefined method Illuminate\Database\Eloquent\Relations\MorphMany::sync()

@umarakber i had the same problem.
The issue sits in the src/PanelTraits/Create.php where on line 138 it tries to sync a
morphMany (hasMany in essence) and that does not allow syncing.
Replace
$values = $data[$field['name']];
$model->{$field['name']}()->sync($values);

with
$model->save($data);
works like a charm.
No idea if its the right way to do it though.

similiar issue here...
unitl i get rid of this line...
 $this->createRelations($item, $data);

my way is to override the store method without changing the vendor file...
    public function store()
    {
        $request = CRUD::getRequest();
        $request->request->set('user_id', backpack_user()->id);

        $this->crud->hasAccessOrFail('create');

        // execute the FormRequest authorization and validation, if one is required
        $request = $this->crud->validateRequest();

        // insert item in the db
        $data = $this->crud->getStrippedSaveRequest();
        $data = $this->crud->decodeJsonCastedAttributes($data);
        $data = $this->crud->compactFakeFields($data);

        // omit the n-n relationships when updating the eloquent item
        $model = new \App\Models\SomeModel();
        $nn_relationships = Arr::pluck($this->crud->getRelationFieldsWithPivot(), 'name');
        $item = $model->create(Arr::except($data, $nn_relationships));

        // if there are any relationships available, also sync those
        // $this->createRelations($item, $data);  <------- this line causing the issue
        $this->data['entry'] = $this->crud->entry = $item;

        // show a success message
        \Alert::success(trans('backpack::crud.insert_success'))->flash();

        // save the redirect choice for next time
        $this->crud->setSaveAction();

        $response = $this->crud->performSaveAction($item->getKey());

        return $response;
    }

This is fixed in #3410
It's not merged yet, still in review and polish phase, but is pretty much working, and some people are already using it.
If you guys happen to give a try to the PR before it gets merged, please leave there a comment about your experience. If you find any bug it would be good to know before we merge it 😄
I am going to close this. So far the best method to store those relations is by overriding the saving process in the CRUD. We hope to change that with the PR I mentioned.
That said I am going to close this, if you have any additional info in this regard please report on the PR thread.
Thanks for your patience,
Pedro


Webpack issue

Hello! Trying to add LavaMoat to an angular project with webpack. Do you have any guidance on what I'm doing wrong?
LavaMoat - Error evaluating module "src/main.ts" from package "<root>"
SyntaxError: Cannot use import statement outside a module
  at Object.eval (eval at makeEvaluateFactory (LavaMoat/node/kernel), <anonymous>:8:30)
  at performEval (LavaMoat/node/kernel:4075:14)
  at Compartment.evaluate (LavaMoat/node/kernel:5434:14)
  at prepareModuleInitializer (LavaMoat/core/kernel:572:54)
  at Object.internalRequire (LavaMoat/core/kernel:443:48)

I modified index.js to point to main.ts
const entryId = path.resolve(cwd, 'src/main.ts')

Webpack config:
const webpack = require('webpack');
const LavaMoatPlugin = require('lavamoat/src');

module.exports = (config, options, targetOptions) => {
  config.plugins.push(new webpack.NormalModuleReplacementPlugin(/^crypto$/, 'crypto-browserify'));
  config.plugins.push(new webpack.NormalModuleReplacementPlugin(/^stream$/, 'readable-stream'));
  config.plugins.push(new LavaMoatPlugin({ writeAutoConfig: true }));

  return config;
};

Using custom webpack builder: https://github.com/just-jeb/angular-builders/tree/master/packages/custom-webpack
Let me know if you'd like me to eject and provide a full webpack configuration or other information.
Thanks in advance!

hi @maebeam
sorry the webpack plugin currently does not work. but we will prioritize it based on demain. what version of webpack are you using?
in the mean time you can still get setup with @lavamoat/allow-scripts and nodejs runtime lavamoat

sorry, i realized this was not clear in the documentation -- ive added a note/warning about that


Make UnderlineInputBorder consistent

This was easy to implement. I like the result, I think borderRadius.zero -> borderRadius.circular makes a nice transition, and many places (like macOS) use an effect similar to this PR, while Google doesn't use anywhere (yet). I'm curious if it is going to break goldens or google testing.

What do you think? cc @HansMuller @gspencergoog. Is this something you want, should I ask the community, or do you prefer the current one?
Side effects:

This makes strokeAlign work with UnderlineInputBorder (TODO: fix drawLine when borderRadius is zero).
This is faster than the current implementation (clip is slow on Skia). 🚀
We could just call BoxBorder._paintNonUniformBorder (if it weren't private). Single LOC implementation.

I don't see any Google test failures.

Spoke with @bernaferrari, he says this is blocked on https://github.com/flutter/flutter/pull/124417

Yes, thanks! I forgot to write this here lol

@bernaferrari Ok let's try landing it!


Couldn't install the Python extension

Had a confusing bad experience trying to get vscode set up for a new user at the PyCon booth.

Installed vscode on a Windows laptop
Find the Python extension, click "Install". It said "Installing" for at least 5 minutes. We thought it could be slow convention center wifi, although extensions at the booth installed very quickly. Eventually, we reloaded the window
Clicked "Install" on the Python extension, and it would flash to "Installing" and immediately go back to "Install". Clicked several times with the same result. Reloaded the window again, same result. I didn't check for errors, I was just trying to get it to work.
Opened ~/.vscode/extensions and deleted everything inside. I think that vscode installs extensions somewhere else then copies them over to that folder. I didn't know where that temp folder is, so I couldn't clear that out. Reloaded and tried to install the extension again, but got the same result.
Then I tried to install the pre-release version of the Python extension as a test, and that worked. Left it there.

Dunno if this is useful without logs or a user who can repro, but do you have any idea?

Hmm very weird. Logs would be helpful to understand what happened. Were you on remote (ssh/wsl) or on local window? We download VSIXs in <user-data-dir>/CachedExtensionVSIXs and extract them into ~/.vscode/extensions folder with the dot at the beginning of the name and rename it to by removing the dot. If you have the set up, we can get the logs from the <user-data-dir>/Logs folder?

I at least know that the extension was not there with the dot. There must have been something wrong with the vsix in CachedExtensionVSIXs? I don't have any way to talk to the customer or get logs. So if there isn't anything you can do with this info, feel free to close it.

Sorry that I can't do anything with the given info. If you encounter this again please try to provide me the shared process logs.


[RFE] Rancher can get all images from a non-Docker registry

Is your feature request related to a problem? Please describe.
Need to be able to set the registry that all images are pulled from in a way that does not interfere with the user environment variable of CATTLE_SYSTEM_DEFAULT_REGISTY.
Describe the solution you'd like
To add a new environment variable that is the default, instead of "", for CATTLE_SYSTEM_DEFAULT_REGISTY
Describe alternatives you've considered
Two alternatives have been looked at:

Using CATTLE_SYSTEM_DEFAULT_REGISTRY. The impact of using this is larger as charts will need to be updated to make sure it's default value doesn't overwrite one set in an image. This is a user set flag and we're looking for a SUSE set one.
Setting the registry at build time. This already happens with settings. The problem with this is that every registry change would require a new build.

Additional context
SURE-5046

Reopening for QA validations

Can we validated when 2.7.0-rc1 is available

after speaking with Matt offline, we will move this ticket to blocked. The PR above allows a registry to be set upon building the rancher image. So QA will need that image built, targeting the trusted registry, before being able to test it.

Technically this is able to be tested from an end to end work flow since both of these issues are merged and available to test, but this is not the final locations of where the server helm chart will be or where the rancher/rancher image will be.
@slickwarren Would you like to do a preliminary smoke test or wait until the final updates regarding where this chart and image would be available?

I would prefer to wait until we have all updates regarding chart and image are available before testing this feature. Otherwise, it puts some unnecessary setup on QA that would otherwise be addressed by the aforementioned updates.

this ticket was validated using 2.7.0-rc3 in both a docker and rke install of rancher using a non-docker registry


There is no at least 2 connected peers in a bin which is shallower than depth

Kademlia topology for multiple nodes (in a 50 node cluster) has nodes with less than 2 connected peers in a bin which is shallower than a depth.
Branch: https://github.com/ethersphere/bee/tree/debugapi-topology-content-type
Example for node 5 (bin 4) can be seen on link https://bee-5-debug.svetomir.core.internal/topology
{ baseAddr: "120f58bb00520fe155e1e677946e7d96993b788fdc3ea71c7aa7ebb266291ee8", population: 49, connected: 39, timestamp: "2020-05-26T15:31:52.768484274Z", nnLowWatermark: 2, depth: 5, bins: { bin_0: { population: 24, connected: 15, disconnectedPeers: [ "c95e0bcf4d27b0f1004a95d1cbf246d8e780aff3e5c106ac2f7650b682bf817b", "d8a569a9e9fe37bf394fd45f4bdbd024bdaa5966880faa87d8e2e14552fb7cf3", "fa4343f457efea327cd63dfb1fdeda9aae683d6e3dab4cdbfee6e619a127bc51", "f0f04b613ae02bdaf48094863476f0882c1c81894a0652fee12a38fe1bf85e2e", "da8a42846a0af4f2f469a37060720e126546439f975a2a227036ac01b3ccd335", "8b008aac0395048381513ef67201e009c1339a1443e9ca4dd3de97ff9fa45711", "95168ce06e6c61b4e15221a0f73146d9fcfd4f045a1627198dff8eb2e00bee0e", "86e2311817f63722a6df74a211448463370878850aa0f68701058b15d659b126", "fb5904b853457734d5a0f08bce6e45ecbbf6d6aff3a62ef0e95dc0690522b4b1" ], connectedPeers: [ "abde2b5ad434dfdbcce2bf0d29cc86a2adaaaf08f9aa3905b57370e74afc4c6f", "b321dd23a8e9982d88e14ba52a79c2e7f1195777ceb4aa568fdc4454d2bbc0e9", "f0a89d6bda3f86bd099e4e9abe52fde9bf6aba491d1b0a5a38347868f284022a", "bad1b2ab6bdbe4a799dfc482ec0bea3d954038954d7d00ec093240aedf2ef06f", "cea4b8a60304073e42650fb4d6ed237599dedbac86630f9bd90a5c5921ccbced", "830b066a9a38837a00fb1ef7f69aa3e2838482efec2f4dec3cc384cafce248a4", "b26e2e61be78cc1e3e1adfbf5d14e1466678b0e2d8df304c5c911eb1798c1449", "81501514d76848d19edb16a3ad740d31b883a721260775bac553c06363c4095c", "ce557ad5ac43065a24dc00111d9e983aae9652bacef3351cbc9321f4b8942019", "8192e3641ed045f10891151462b5809fd0bf47e4f9f1b75cd63e8e7a77af01ef", "c38f807718be6f2eea930aebfcabc058b5ef59777bedeba0c08db2dcc5d4d1e0", "f6068d55ef05597fb5f0c01c31699bf7501c5fe00d1d0353332e7eb0003db2bc", "fd4dbcf76025afa442b02d35190c87c3d92f6b32a84b8eacfc6ebc3e822463dd", "e91bcca7d761768232b8acab319ae9b86bd3d42c67f04e791d6c85be5b3bed5f", "e2faaaa6984d4919b1b4f9bd914da563aa3cf2de4d8cb2dece5c22bc999f1938" ] }, bin_1: { population: 15, connected: 15, disconnectedPeers: null, connectedPeers: [ "791c7131de09fa01ff8478ed1e219501842a1c5211f9521783754b113f7ff34e", "716cd3cb58f4ffd238f6f49a6201f9c2ef1d242042312677643ffdde8cd149f2", "76642beda4b98b367f3d95db6be587345c8029f9cdac335aa0281d99f067fbe1", "4a8e6665ecdbbfcccea195bc8c6bb35aadcebcc609d69141faf8e4145e8667a4", "4e9012f52056c5162f54658214e0bb940eaaa3bc11553b1ee4585da355a11a8a", "4c969c9ccc5e866abbddda4cb71ecdac783d98f7c4b87f83753ab6efad8442f6", "6332a8d7ba900969a3914dfcbd8cbe4ee50f730936d51e74993fa11938bfd75c", "6c11a823120257219614e2f589a1af1fc99a20359f75568261e8e6e81555762c", "53a5b6c065f016530d2f467889790b7a91e866d532ecebcfac80abe781189624", "41254bac986b19fdd88fcf9d2f2456d1af8d89a038e1a89e54bd885c95b64a5d", "6c0b3929f5faec0b228a1b48ed67b204f7efbf25b623d1d7a7abe65b9894b138", "46ba6d6f36613f2ef6fefee2a7da7a1f30cac276e7be1f3a4e55b31cc253dd9b", "4cde4679b4a18df016cab8aa83893f4f2753ab6872f850fb250e3812c96214d5", "76397868fb77c49ad78059164a794c574de990aa73b9ba3d33523beacabdb848", "5a9564128c1dcac5c147b246116f2501d53e002d39503e927dce47861c861769" ] }, bin_2: { population: 4, connected: 3, disconnectedPeers: [ "2067461a682ad84758c1b2743fdc9854f0668ad40932dcaa990c941228fdbd5d" ], connectedPeers: [ "3876c4146f00bd6d8fcc304cfe1fb558ae6f8d0dd47b4d508177afeff0a9a1b4", "3f12cf04485c10048fe593ba59f48f6cfb71551931fc65502612eb438f71c115", "2021e16344eab03646edd161fbc7ddcfdad8070c2a6f5233b5178d0affc9ab2d" ] }, bin_3: { population: 2, connected: 2, disconnectedPeers: null, connectedPeers: [ "0c38fec0aabd3c5fcc184274f736457cb008ed15b8b522d68cc54e15e1b05157", "00c2867ec8073bcd6cb1ddeb206ace54b8f338bc39d2c3fd1872a7f3090f6407" ] }, bin_4: { population: 1, connected: 1, disconnectedPeers: null, connectedPeers: [ "18dbb139e7e15d5a911643450a52119034d7ff6a82d9eb651fd276f0ebbd88b0" ] }, bin_5: { population: 2, connected: 2, disconnectedPeers: null, connectedPeers: [ "15b74e76fccb3be5318b5bd3d440420cabfec96013029a0a66d40d385fd5b585", "1735b4a281bd4645f4fbd5457bf2c7d59cc36909c7de7fb34414ae94c7102ac4" ] }, bin_6: { population: 1, connected: 1, disconnectedPeers: null, connectedPeers: [ "10bae4ed636322e61bbde05ab3650d4214379f0677c25bc91a1dbfb2c17a1799" ] }, bin_7: { population: 0, connected: 0, disconnectedPeers: null, connectedPeers: null }, bin_8: { population: 0, connected: 0, disconnectedPeers: null, connectedPeers: null }, bin_9: { population: 0, connected: 0, disconnectedPeers: null, connectedPeers: null }, bin_10: { population: 0, connected: 0, disconnectedPeers: null, connectedPeers: null }, bin_11: { population: 0, connected: 0, disconnectedPeers: null, connectedPeers: null }, bin_12: { population: 0, connected: 0, disconnectedPeers: null, connectedPeers: null }, bin_13: { population: 0, connected: 0, disconnectedPeers: null, connectedPeers: null }, bin_14: { population: 0, connected: 0, disconnectedPeers: null, connectedPeers: null }, bin_15: { population: 0, connected: 0, disconnectedPeers: null, connectedPeers: null } } }
NOTE: I left cluster up and running in case you need more detailed inspection.

In the example that you sent for node 5, bin 4 has the population of 1, so it can only connect to one peer in that bin as it is not aware of any other nodes that are at that proximity. As the total population known by node 5 is 49, meaning that it is complete, connected number of peers in bin 4 is at its maximum possible for this cluster.

Closing this issue based on:
https://github.com/ethersphere/bee/issues/198#issuecomment-638928333


feat(desktop & deck): Added XIV Launcher to list of available games

Hi Team!
Here is my PR! This adds the flatpak in the list of available games. This fixes https://github.com/ublue-os/bazzite/issues/380
Thanks,
Noel Miller

This is great, thank you so much!

We generate our change log from commit names, if you'd like this to appear in the change log you could append feat:  to your commit title.

I'm fairly new to git, is there an easy way to change a commit name?

I'm fairly new to git, is there an easy way to change a commit name?

Bit of a pain, editing is simple but then you need to force push, I'll merge and change on my end

Awesome! I did find the answer! https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message
I'll make sure to be better about names in the future! This is the first public project I've ever committed to, so the process is still a bit new.


Require node.js >= 4.0.

The issue with this is I wanted to match the node version that it will be running on in Heroku. I'm not oppose to this change, but can we also include 5 when running on Travis.

So Heroku runs 5? Can we make it use 4?

Probably, I'll look it.

Yes, here... https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
I can make the update, do you have a specific version of 4.x you want to use?

I'd say the latest LTS, 4.4.7 at the moment. Can't this process be automated to keep using the latest LTS at the time?

From that doc...

You can also specify a semver range (4.x). This is not recommended in production, where runtime versions should not float.

That said, I'm cool with using 4.x. We'd have to update when the next LTS major version is bumped.

I think that is the whole idea of LTS.

@XhmikosR made the change

worked
jmervine@laptop:~$ heroku run -a bootstrapcdn-dev node --version
Running node --version on ⬢ bootstrapcdn-dev... up, run.8560
v4.4.7


Use Mesos version 1.4.0-rc1

Confirmed Kafka with this dcos-commons build and I've been running DSE with rc1 for two days.


UI for command, cluster and application pages

Initial code to get the remaining pages working
Fixes minor UI bugs

Coverage remained the same at 89.359% when pulling 1a34d4bc27185b387e9743523c53d0ca0f741160 on cabhishek:develop into f61ada2bb2dd0588359be28822b1e78017a9e4ad on Netflix:develop.

Part of #164


Artifacts cannot be stored in object-lock enabled S3 buckets

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
Artifacts cannot be stored into AWS S3 buckets with Object Lock enabled.
I believe this may be fixed by https://github.com/minio/minio/pull/15433
Version
3.4.7 and latest (and probably others)
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  annotations:
    iam.amazonaws.com/role: AWSIAMROLENAME
    workflows.argoproj.io/pod-name-format: v1
  name: wf-artifact-test
spec:
  entrypoint: wf-artifact-test
  templates:
  - name: wf-artifact-test
    metadata:
      annotations:
        iam.amazonaws.com/role: '{{workflow.annotations.iam.amazonaws.com/role}}'
    podSpecPatch: |
      containers:
      - name: wait
        image: argoproj/argoexec:latest
    container:
      name: wf-artifact-test
      image: busybox
      command:
      - /bin/sh
      - -c
      - |
        echo '{}' > /out/test.json
        sleep 1
        cat /out/test.json
      resources:
        requests:
          cpu: 100m
          memory: &memory 300Mi
        limits:
          memory: *memory
      volumeMounts:
      - name: out
        mountPath: /out
    volumes:
    - name: out
      emptyDir: {}
    outputs:
      artifacts:
      - archive:
          none: {}
        name: test-artifact
        path: /out/test.json
        s3:
          bucket: object-lock-enabled-bucket
          endpoint: s3.amazonaws.com
          key: test/test-artifact.json

Logs from the workflow controller
(none)

Logs from in your workflow's wait container
time="2023-06-05T20:02:44.014Z" level=warning msg="Non-transient error: Content-MD5 OR x-amz-checksum- HTTP header is required for Put Object requests with Object Lock parameters"
time="2023-06-05T20:02:44.014Z" level=error msg="executor error: failed to put file: Content-MD5 OR x-amz-checksum- HTTP header is required for Put Object requests with Object Lock parameters"
time="2023-06-05T20:02:44.114Z" level=fatal msg="failed to put file: Content-MD5 OR x-amz-checksum- HTTP header is required for Put Object requests with Object Lock parameters"

It looks like dependabot keeps minio up to date (see commit 760299ff9bb44feddae89d43dc600b1ba27b994d).  I tried using argoproj/argoexec@sha256:e237c40aadcfd5d3d6b8325d4eba79e53fd7085cccd8dc6eefd48049966d873c and it still fails.  Perhaps Argo Workflows is using one of the cases that minio doesn't handle correctly.
https://github.com/minio/minio/issues/16480 seems related as well.

It looks like dependabot keeps minio up to date (see commit 760299f). I tried using argoproj/argoexec@sha256:e237c40aadcfd5d3d6b8325d4eba79e53fd7085cccd8dc6eefd48049966d873c and it still fails. Perhaps Argo Workflows is using one of the cases that minio doesn't handle correctly.
minio/minio#16480 seems related as well.

thanks for checking

Client must set Content-MD5 in this case and the problem is solved for all S3 providers. Is there a specific reason argo-cd is trying to look for the exact error returned in this case?

This is what mc does if set the content-md5 if the bucket has ObjectLockEnabled.

would u like to raise PR @harshavardhana @akloss-cibo ?


[scripts] Update Bazel to 6.1.2

The current version, 4.2.2 (dated December 2nd, 2021), is significantly outdated and does not support VS2022.

Thanks for the update!

Sorry, I just realized I messed this up like 3 seconds after pushing the merge button. All current users of Bazel should be getting it through the vcpkg-tool-bazel port, and we should be considering the vcpkg_find_acquire_program copy as locked in ice forever. Bazel is highly incompatible between versions so that really needs to be version controllable by the end user in case they are installing things that need older Bazel.
I note that both things that use Bazel in our tree, ryu and tensorflow, already use vcpkg-tool-bazel.
(I'm sorry I don't have a way to reopen the PR after the merge-and-panic-revert :/)


refactor(newsletter): sharded @daffodil/newsletter library

PR Checklist
Please check if your PR fulfills the following requirements:

[ x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Fixes: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[x ] Yes
[ ] No

Other information

build is failing

build is failing

The was completed in another PR: https://github.com/graycoreio/daffodil/pull/1385