Unable to download fasta files from private genome-zip file empty.

This is true in both production and on beta.  I go to the download tool and select protein fasta (I'm trying to build trees).  It downloads an empty zip file from each site.  Public genomes work okay, though.

I thought I would be able to select all the CDS features and download them as fasta from the genome page, but I couldn't do that either.  Totally stuck, and very unhappy.

For the first part of your ticket, this is known.  The download comes from the FTP site.  We cannot put the private genomes on the ftp site, so therefore the private genomes dont' work via this method just as they don't on production.  However since they were private genomes you uploaded, all of the generated files should be available in your workspace in the Job Result.  It is ultimately planned to make this work, but requires serializers for each data type to be written and that hasn't been done yet.
The second part of your ticket is because the selection is >5k rows.  I don't remember where the 5000 number came from, the download limit there can probably be increased to 10k.

Thanks!
----- Original Message -----
From: "Dustin Machi"<EMAIL_ADDRESS>To: "PATRIC3"<EMAIL_ADDRESS>Cc: "Rebecca Wattam"<EMAIL_ADDRESS>"Author"<EMAIL_ADDRESS>Sent: Sunday, November 27, 2016 3:39:09 PM
Subject: Re: [PATRIC3/patric3_website] Unable to download fasta files from private genome-zip file empty. (#1299)
For the first part of your ticket, this is known.  The download comes from the FTP site.  We cannot put the private genomes on the ftp site, so therefore the private genomes dont' work via this method just as they don't on production.  However since they were private genomes you uploaded, all of the generated files should be available in your workspace in the Job Result.  It is ultimately planned to make this work, but requires serializers for each data type to be written and that hasn't been done yet.
The second part of your ticket is because the selection is >5k rows.  I don't remember where the 5000 number came from, the download limit there can probably be increased to 10k.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/PATRIC3/patric3_website/issues/1299#issuecomment-263145945

download limit has been increased to 10k.


Use named provisioners for Ansible.

Allows the use of:
vagrant provision - Runs the default provisioning.
vagrant provision  --provision-with ansible-galaxy - Runs only the galaxy role installation
vagrant provision  --provision-with ansible-playbook - Skips downloading the roles via galaxy.

Adding note from @joestewart in #753:
Will work in Vagrantfile.local.
To skip downloading roles, add the following in Vagrantfile.local:
# vagrant provision  --provision-with ansible-galaxy
config.vm.provision 'ansible-galaxy', type: 'ansible' do |ansible|
  ansible.playbook = "#{host_drupalvm_dir}/provisioning/playbook.yml"
  ansible.galaxy_role_file = "#{host_drupalvm_dir}/provisioning/requirements.yml"
  ansible.raw_arguments = "--syntax-check"
end

# vagrant provision  --provision-with ansible-playbook
config.vm.provision 'ansible-playbook', type: 'ansible' do |ansible|
  ansible.playbook = "#{host_drupalvm_dir}/provisioning/playbook.yml"
  ansible.extra_vars = {
    config_dir: host_config_dir
  }
end

...and run vagrant provision  --provision-with ansible-playbook
See more: https://gist.github.com/joestewart/f22d854591a909461f031f262f35bc6d

I'm not sure if I'll necessarily merge in the PR as-is... the main thing is I want vagrant up and vagrant provision to work exactly as they do now. It would be ideal if the new code would add the ability to do something like vagrant provision --no-galaxy to skip the galaxy install, or something along those lines.

Hi, the comment is unclear to me.  If it is easier, ping me on IRC.
"the main thing is I want vagrant up and vagrant provision to work exactly as they do now"
What behavior change with this?
vagrant up or vagrant provision is used normally.
"It would be ideal if the new code would add the ability to do something like vagrant provision --no-galaxy to skip the galaxy install"
I didn't find a way with syntax that simple, so used the named provisioners like:
vagrant provision  --provision-with ansible-playbook
I understand if you rather this be used in Vagrantfile.local instead.

Since 3.2.0 (I think that was the version), the roles are included in the repo, so this feature is no longer necessary. Thanks for the work on this, and I'll definitely have to refer back to it for some other projects where I won't include roles...


Fix _config.yml for Jekyll 3

I had issues getting this to work with Jekyll 3, so I updated the highlighter and removed the paginate requirement. (It should be installed by default right?)

thanks @plingampally , that was solved with another fix


merge/use gopacket for marshal/unmarshal ofp messages and decode PacketIn

i'm watching for you project and sometimes ago use ogo for openflow controller...
Also i'm contribute to gopacket, what do you think about moving marshal/unmarshal code to gopacket and use it to decode PacketIn messages?

Thank you comment @vtolstov
It is embarrassing but I didn't know gopacket until see your comment, and so I can't answer immediately.
I need time to consider that gopacket is suitable for gofc or not.
Originally, I start to write gofc as part of my Golang study, so I wrote all marshal/unmarshal code by myself.
This is just a general theory but, It is one way to use great library and stop own implementation.


Feature/增加解析wxml能力

添加了分析以来过程中解析wxml能力,将依赖的wxs加入

Codecov Report

Merging #18 (9cc5ce3) into master (2425394) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
+ Coverage   98.50%   98.52%   +0.02%
==========================================
  Files           9        9
  Lines         401      407       +6
  Branches      112      114       +2
==========================================
+ Hits          395      401       +6
  Misses          6        6

Flag
Coverage Δ

macos-latest
?

ubuntu-latest
98.52% <100.00%> (+0.02%)
:arrow_up:

windows-latest
?

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

Impacted Files
Coverage Δ

lib/lookupDependencies.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2425394...9cc5ce3. Read the comment docs.

这里能辛苦加一些针对wxs解析的测试用例吗

Codecov Report

Merging #18 (9cc5ce3) into master (2425394) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
+ Coverage   98.50%   98.52%   +0.02%
==========================================
  Files           9        9
  Lines         401      407       +6
  Branches      112      114       +2
==========================================
+ Hits          395      401       +6
  Misses          6        6

Flag
Coverage Δ

macos-latest
98.52% <100.00%> (+0.02%)
:arrow_up:

ubuntu-latest
98.52% <100.00%> (+0.02%)
:arrow_up:

windows-latest
?

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

Impacted Files
Coverage Δ

lib/lookupDependencies.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2425394...9cc5ce3. Read the comment docs.

Codecov Report

Merging #18 (9cc5ce3) into master (2425394) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
+ Coverage   98.50%   98.52%   +0.02%
==========================================
  Files           9        9
  Lines         401      407       +6
  Branches      112      114       +2
==========================================
+ Hits          395      401       +6
  Misses          6        6

Flag
Coverage Δ

macos-latest
98.52% <100.00%> (+0.02%)
:arrow_up:

ubuntu-latest
98.52% <100.00%> (+0.02%)
:arrow_up:

windows-latest
98.52% <100.00%> (+0.02%)
:arrow_up:

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

Impacted Files
Coverage Δ

lib/lookupDependencies.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2425394...9cc5ce3. Read the comment docs.

👍该特性已发布<EMAIL_ADDRESS>


0.2.0 version on npmjs is broken

$ npm install react-native-loading-spinner-overlay
$ ls node_modules/react-native-loading-spinner-overlay
LICENSE      Readme.md    package.json

See 0.2.1 https://github.com/niftylettuce/react-native-loading-spinner-overlay/pull/18

See https://github.com/niftylettuce/react-native-loading-spinner-overlay/issues/20#issuecomment-231388519


How to change connection from read only to write permission

Hey all,
I've been using this beautiful project for quite a while and as a total beginner in Swift I got my app running completely based on an sqlite table with sqlite.swift. So far for the good news... ;-)
I'm trying to use an existing database (dragged and dropped to the project navigator). Connection succeeded, queries work perfectly but writing to a field in a row give me the error "attempt to write a readonly database (code: 8)"
This means I wasn't able yet to get the connection to a write permission. All the documented things seem to be targeting a "to be created" database but not an existing one.
Here's my connection from an example out of a little movie quiz app. The connection is triggered when the user guesses the right movie:
let database = try! Connection(Bundle.main.path(forResource: "movies", ofType: "sqlite3")!)

      let rowID = movies.filter(movieId == "\(random)") //random is an arc4Random from the number of movies
      do {
      try database.run(rowID.update(solved <- "1"))
      try database.run(rowID.update(score <- "\(highscore)"))
      try database.run(rowID.update(hints <- "\(hintCounter)"))
      try database.run(rowID.update(guesses <- "\(guessedCounter)"))
      } catch {
          print(error)
      }

In the documentation there's an example code for connections with write permission but I think because of my database being an existing one this doesn't work.
Can you help me to correct the connection to lead to write permission?
Thanks a lot and keep up this great work!
Sorry if this is naive or "nooby" in a way but I just didn't get any further and this is the last thing to be solved :-/
Patrick

Just leave the beginners alone and they'll come to the conclusion that you cannot manipulate files in a bundle... ;-)
I've come along this great function which was all I needed. Everything else is working fine with Sqlite.Swift from there.


Enable Musl 1.2.5's new malloc

It's supposedly faster, but issues were encountered with this enabled during upgrade to 1.2.5. See discussion in #2251.

To test with new malloc, remove "--with-malloc=oldmalloc" from:
https://github.com/includeos/IncludeOS/blob/v0.16.0-release/deps/musl/default.nix#L37
and
https://github.com/includeos/IncludeOS/blob/v0.16.0-release/deps/musl-unpatched/default.nix#L20
With malloc-ng, the kernel currently seems to enter a reboot cycle in libc init, here: https://github.com/includeos/IncludeOS/blob/master/src/platform/x86_pc/init_libc.cpp#L178
Control never comes back to kernel_main.


Using only the one dataset

Its really awesome project. So due to the large amount of dataset size, Can i Use only one dataset(AVCeleb) to train the model?

Hi!
Thank you very much! :)
Yes - it is possible to use only one of the available datasets, however this will likely result in the less generalized models, as FakeAVCeleb contains only one type of spoofing method.


Change modes in intellij

Is there a way to change to development mode when building a project with Intellij?
I've been able to change to development mode when using the sbt console with environment variables or sbt commands but this doesn't work when doing Build > Build Project from the intellij UI.
It would be nice to be able to do this to not have to worry about unused variables or imports when developing.

Hi @petern-sc!
I've transferred this to sbt-tpolecat because scalac-options does not know about modes, so it belongs here.
It's an interesting question - I don't believe that IntelliJ uses sbt for builds unless you specifically configure it to delegate build actions to sbt.
As a result, it can't pick up scalac options that depend on sbt configuration.
If you are delegating build actions to sbt, then you need to find a way to pass environment variables to sbt when building in IntelliJ.
I'm not an IntelliJ user so it's hard for me to advise how to go about doing that!

I must have gone to my wrong open tab 😅. Thanks for transferring this over


Release version 0.2.0

@johno I left a comment in issue #30 - I wasn’t able to publish the release. Can you please take a look?


Backchannel js samples?

Having trouble finding any code examples in the repo for Backchannel usage, specifically around using postactivity -- triggering events (I'm using ReactWebChat).
The goal is to trigger a pro-active message via Backchannel to the user as a welcome (using Directline).
This may be sames as #1441
Do any such examples exist? Thanks!

@robbiew can you check this PR #1286?
We are still drafting this. Since it touch pretty much every saga (a.k.a. business logic) on the production code, it's pending a thorough test.
The reason we need a production code change is to make the sample simpler and more intuitive. You can look at the proposed sample here.

Hi @compulim,
I am testing the above code, and though the event seems to be fired, I see nothing on the bot.
Using dev <script src="https://cdn.botframework.com/botframework-webchat/master/webchat.js"></script> ...
And this client code ...
                      (async function () {
                            const store = window.WebChat.createStore({}, ({ dispatch }) => next => action => {
                            if (action.type === 'DIRECT_LINE/CONNECT_FULFILLED') {
                                console.log("Sending activity ...")
                                dispatch({
                                type: 'WEB_CHAT/SEND_EVENT',
                                payload: {
                                    name: 'webchat/join',
                                    value: { language: window.navigator.language }
                                }
                                });
                            }
                            return next(action);
                            });
                            window.WebChat.renderWebChat({
                                userID: params['userid'],
                                directLine: window.WebChat.createDirectLine({
                                    token: params['directLineToken']
                                }),
                                store
                            }, document.getElementById('botChat'));
                            document.querySelector('#botChat > *').focus();
                        })().catch(err => console.error(err));

Browser console shows "Sending activity ...", but nothing arrives at the bot as far as I can tell, where my bot is defined ...
// Listen for incoming activities and route them to your bot main dialog.
server.post('/api/messages', (req, res) => {
    // Route received a request to adapter for processing
    adapter.processActivity(req, res, async (turnContext) => {
        // route to bot activity handler.
        await bot.onTurn(turnContext);
    });
});

And ....
async onTurn(turnContext) {

        console.log("STUFF2: " + JSON.stringify(turnContext))
}

Is there something I'm doing wrong please?
thanks,
Matt

We are seeing the same problem - any updates on a fix?


Sanitize user input for ResourceLocation, RootNamespace, etc

Localization should check/sanitize input from sources like "ResourceLocationAttribute", "RootNamespaceAttribute", etc. to make sure that they A) fail early if they're illegal for some reason B) get trimmed of "extra" characters like / or . on the beginning/end.

We're closing this as we don't want to have validation logic which is applicable to one scenario and applies to all the cases.


Licence missing in the rubygems version and in the gemspec

The "unicode_utils" gem seems not to have a license at all. Unless a license that specifies otherwise is included, nobody else can use, copy, distribute, or modify that library without being at risk of take-downs, shake-downs, or litigation.
I know, that this gem has a license on github, however it's missing one at rubygems and in a gemspec.

@lang can you add the license and release a new version?

#16 resolves this.

<3 - is there a chance for a release with this update to get it "fully" done?
ref https://rubygems.org/gems/unicode_utils


Enhanced file explorer perspective #2437

Add drag and drop in the file tree and from the file system
Add F3 shortcut to open selected file
Add Show/Hide hidden files and folders
Add copy name/path in context menu
Delete or rename a file don't need a full refresh
Update some icons

awesome work!


how to update the ttf

now i try to update a new fonts file new.ttf, and when update finish always old.ttf..
plase help me!!

pod cache clean Iconic


Invalid replacement token

Whenever /broadcast  is used ingame, either by a player or the server console, it returns "Invalid replacement token".

Hmm, that is not a message sent by my plugin. This means that you have conflicting broadcast plugins. However, I recently released an update which changes the command to /autobroadcast (abc). This should resolve all conflicts.


fix: mark existing_kms_instance_crn as required instead of existing_kms_key_crn in the DA

Description

mark existing_kms_instance_crn as required instead of existing_kms_key_crn in the DA because when a value is passed for existing_kms_instance_crn it will create the root key if no value is passed for existing_kms_key_crn.
Updated some of the KMS variable descriptions in the DA

Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

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

GitHub release
v1.23.5

Your semantic-release bot :package::rocket:


Smithy-generated Dafny interface allows custom implementations of non-@extendable resources

Found this while working on SQSExtended in #666.
I neglected to add @extendable to my resource, but was able to write a successful Dafny test of the local service. Then I tried a Java equivalent, and it threw an IllegalArgumentException saying custom implementations are not supported. I'm glad Java correctly respected the Smithy model, but it would have saved a fair bit of time if Dafny did in the first place.
Bonus marks if we can encode this as a requires clause somewhere so Dafny code that tries to provide a custom implementation doesn't even verify. :)

When you say the Dafny does not prevent this,
do you mean you can write Dafny source code that
extends non-extendable resources?
If so...
I am not certain this impacts Smithy-Dafny consumers very much,
if those consumers are like Crypto Tools.
i.e: I have a hard time imagining a Crypto Tools customer writing a Dafny implemention of the MPL's Key Store.


How to use lora finetune moe model

hi @Minami-su
You can use LoRA to train any nn.Linear layer. If you MoE has Linear layers you just need to pass the names of the modules you want to train into target_modules. What MoE architecture would you like to train using peft?


Print ticket by Point of Sale

In your Ticket custom 2, you put the Name of the res.partner directly, but in case we have several pos points and with diferent stock locations, here is an idea. But i will like to know your proposal
<t t-extend="PosTicket">
        <t t-jquery="div.pos-sale-ticket" t-operation="prepend">
            <t t-if="widget.pos.shop.partner_id">

                    Printed in:

                    <t t-set="shop_address" t-value="widget.pos.db.get_partner_by_id(widget.pos.shop.partner_id[0])"/>
                    <t t-esc="shop_address.name or 'Not Working'"/>

              </t>
         </t>
</t>

You are welcome to make PR, that makes module more flexible


Add support for Utf8View to crypto functions

Is your feature request related to a problem or challenge?
Currently none of the crypto functions does not directly support Utf8View type but rather casts it to Utf8. It would be good to support Utf8View directly
Describe the solution you'd like
crypto functions supports Utf8View directly without casts.
Describe alternatives you've considered
Leave as is
Additional context
No response

take


Return an error object inline with the JSON RPC spec.

We were previously just returning an error message, which breaks the rpc spec and web3.

I kept your changes in case we prefer this behaviour but opted to just pass the error on instead - if this is a problem lets discuss

I don't think that's up to spec. According to the JSON RPC spec, you return an object with an error property. Web3 is angry if anything else is returned.

that makes sense.
though angry is good, its an error after all.
in development ive wanted it to fail as early as possible, makes debugging easier
hmmm i wonder if we are caching error responses...

Let me rephrase. Web3 says "Invalid JSON RPC response" instead of showing the actual error. So without this PR, we're effectively squashing errors.

ok thats a big deal
havent been testing against web3

published as 4.0.1


fix typo in Oxford comma

Fixed minor typo. Many thanks for making this great material available!

thanks!

thanks!


Condense python-imaging rules for Fedora

The last differing rule was for Fedora 18 (spherical), which went EOL in early 2014.
The same package provides both subpackages referenced here:
https://apps.fedoraproject.org/packages/python-pillow

I believe that this check is failing because of our dear friend schrödinger’s. Fortunately, this change removes it.

Wasn't that problem fixed by https://github.com/ros/rosdistro/pull/6989 ?  Did we regress somehow?

I'm fairly sure this was regressed by #18374.

I'm fairly sure this was regressed by #18374.

Right.  So the question essentially boils down to whether we care to keep the tests working with Python 2.  If we do, then we should probably fix the regression.  If we don't, then we should probably disable the Python 2 jobs in Travis.  Thoughts?

So the question essentially boils down to whether we care to keep the tests working with Python 2.

:+1: retiring the python2 test runs. We have other parts of our infrastructure that are python3-required at this point and I don't see a strong value in running these tests on both.

So I dug into this, and the regression was also caused by #6741. According to the documentation [1], the cStringIO implementation "is not able to accept Unicode strings that cannot be encoded as plain ASCII strings."
The reason we're even using cStringIO appears to trace back to here: http://wiki.ros.org/python_2_and_3_compatible_code#StringIO. I tried simply switching to io.StringIO, and everything worked fine.
I have no preference as to whether or not we run tests on Python 2.
[1] https://docs.python.org/2/library/stringio.html#cStringIO.StringIO

I tried simply switching to io.StringIO, and everything worked fine.

I say PR the fix and that will unblock the issue. If I'm feeling sinister I'll open a separate PR to turn off the python2 testing.

Done. See #20304.


fix: slog.Handler log error messages rather than {}

When used as an slog.Handler, error objects may be specified as slog.Attr attributes. In general attributes are converted into lager.Data{} maps, but there's a feature of logging lager.Data{} maps which is that error objects (and potentially other objects) are rendered as {} rather than a more useful representation. This adds a special case for errors so that they are now converted to strings before being placed in a lager.Data{} map.

[x] Read the Contributing document.

Summary
Fixes an issue where errors were being logged as {} when they originated from an slog.Attr
Backward Compatibility
Breaking Change? No

Fixed via #127. Thanks for the nudge on this isue though!


Correct APY

On the DEX liquidity page the APY was wrong we should probably correct this or strip out the code in vega-lp-staking that does the incorrect calculation.
In order to correct the values we would need to calculate the value of SLP/VEGA which can be done with a contract e.g.
X SLP = Y VEGA + Z OTHER (based on reserves)
A OTHER = B VEGA (swap rate)

apply basic algebra to figure out SLP/VEGA exchange rate and adjust the existing calculation in vega-lp-staking.

This is closed and it doesn't look like it's coming back, closing


Turn charon into a subcommand

We want to be able to run cargo charon

It's pretty easy: if there is cargo-charon in the PATH, cargo charon will call it. The difficulty is how to get our users to install the binary in the right spot. Maybe cargo install does what we want.


Default ToggleSwitch behavior for initial IsChecked=null is weird

Describe the bug
ToggleSwitch.IsChecked  property is of type bool?, hence can have 3 states, one being null.
The problem is - by default its visual behavior is unintuitive when the bound value is null:

It shows no On or Off label
Apart from 1., there's no visual indication, that it is null.
There's no Unset label to set.
Its looks Off by default (which might be OK default, but maybe should have separate property for the default).
Important: upon clicking, it switches from null to Off, which is very confusing for the user, as they would expect it now become On.

To Reproduce
Steps to reproduce the behavior:

Add ToggleSwitch
Bind IsChecked to any bool? property with initial value null
Observe there's no label at all, and switch looks Off
Click on the switch

Expected behavior

There's a special label for null, or Off is displayed, or whatever is set as default is displayed
Upon click on the switch, it should turn to On if it looked Off before

Environment(please complete the following information):

MahApps.Metro version v1.6.4
OS: Win10 1803
Visual Studio 2017 15.7.4
.NET Framework 4.7.1

I modified the template and the code behind to enable null-values. Unfortunatally i am not familar with changing the code here and make a pull-request. But if someone wants to implement this feature i can post the code here.
I also implemented a contentpresenter which you can use to have a custom content shown based on the state of the switch.

I am currently working on a PR to implement a different behaviour there. But as this will be a breaking change i don't know if it will be implemented or not.
@punker76 There are currently two very similar controls. What do you think,  can we drop one of these controls or make one based on the other to avoid dublicated code?


Implement UsortVerifyMultiplicityBody hint

Resolves https://github.com/NethermindEth/cairo-vm-go/issues/235

lgtm

For some reason the tests are not passing, make sure to run make unit and resolve the problems. Thanks!

For some reason the tests are not passing, make sure to run make unit and resolve the problems. Thanks!

@MaksymMalicki My apologies
Something was wrong with the environment
I dockerized it to make sure it does not happen again

I did fix the test and made a small change reading the current_pos from the scope instead of using the one from positions to calculate the value of next_item_index and last_pos

@MaksymMalicki I just fixed conflicts after rebasing with main branch


python310Packages.persim: disable failing test

Description of changes
Fix build (https://hydra.nixos.org/build/209213064)

Things done

Built on platform(s)

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 218197 run on x86_64-linux 1

2 packages failed to build:

python310Packages.scikit-tda
python311Packages.ripser

3 packages built:

python310Packages.persim
python310Packages.ripser
python311Packages.persim

Result of nixpkgs-review pr 218197 run on x86_64-linux 1

1 package failed to build:

python310Packages.scikit-tda

4 packages built:

python310Packages.persim
python310Packages.ripser
python311Packages.persim
python311Packages.ripser


Fixes and Documentation updates

Description
fix: https://github.com/terraform-ibm-modules/terraform-ibm-base-ocp-vpc/issues/374
Cleanup: https://github.com/terraform-ibm-modules/terraform-ibm-base-ocp-vpc/issues/378

Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline


Add kubeadm 1.9 upgrade docs

Provides explicit instructions on how to upgrade to 1.9. Much of this was copy pasta'd from our 1.8 docs, so if there's a better way to document this I'm open to alternatives.
/cc @luxas

This change is

Thanks for the review @zacharysarah, changes have been pushed.
@luxas ping for tech review

@jamiehannaford 👋

I changed the base to release-1.9 because docs has a different relationship with master and feature branches.
Bumping for updates to review feedback from @luxas (thanks!).

@jamiehannaford 👋 Bumping for a response to review feedback. Deadline for completion is tomorrow, Friday, December 8th.
/cc @idvoretskyi

@zacharysarah @luxas All changes incorporated. The only one I didn't have time for is adding a section for downgrades. Is this a blocker or can we add in a PR after the docs freeze? We have most of the content here. I don't mind either way.

@jamiehannaford I'm fine with making an update after release. 👍


[AutoPR] applicationinsights/data-plane

Created to accumulate context: applicationinsights/data-plane

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2778   +/-   ##
=======================================
  Coverage   56.01%   56.01%
=======================================
  Files        7365     7365
  Lines      154340   154340
=======================================
  Hits        86459    86459
  Misses      67881    67881

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af49340...9906c2b. Read the comment docs.

See See https://github.com/Azure/azure-sdk-for-python/pull/2767


[CLI] Add command for proxy start/stop

Given that there are no Compute Engine client lib commands equivalent to the start/stop proxy command (gcloud ssh), this has been put back on the user. If they have configsync enabled, they're prompted to open a tab and start the proxy before the CLI create finishes. If configsync isn't enabled, the bastion command is in the Terraform output.


llama2-7b gives error in terraform apply (Azure)

Input to deploy-aks.sh
Model to deploy: llama2-7b or falcon7b (default: falcon7b): llama2-7b
Plan: 9 to add, 0 to change, 0 to destroy.
╷
│ Error: Invalid index
│
│   on main.tf line 297, in resource "kubernetes_deployment" "rag_server":
│  297:             value = "http://${kubernetes_service.falcon7b_service[0].status[0].load_balancer[0].ingress[0].ip}"
│     ├────────────────
│     │ kubernetes_service.falcon7b_service is empty tuple
│
│ The given key does not identify an element in this collection value: the collection has no elements.
The apply searched for falcon7b service where as it wont be applicable for llama-2.
Did any one else try this?

I had the same issue but instead decided to ignore llama2 option and try to use falcon7b just to try and get it running.


Add except option for RequireCapitalizedComments

Hello again!
This is a suggested feature to allow for certain exclusions to this rule, e.g:
"requireCapitalizedComments": {
    "allExcept": ["istanbul", "jshint", "jscs"]
}

istanbul | jshint - see Inline Configuration section | jscs
This allows hint comments to be ignored.
What do you think?

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

Great catch @ashclarke! We should totally do this.
Would you like to give this a go?

Shall I make jscs and jshint default exceptions?

I reported this feature in the past https://github.com/jscs-dev/node-jscs/issues/837, but completely forgot about it :-/
I am against making jscs and jshint (or any other values) default exceptions. Why? Because I don't want use inline comments for these two tools and want to get notified, when I do.

@alawatthe I'd say no. It's a kind of sugar, atm we almost done #109 about presets, and I believe that it could helps a lot with sugar making in common. At other hand, I'm agree with @alawatthe about discouraging defaults.

@zxqfox I am probably not seeing something obvious, but what has this bug to do with presets?

I'd say no.

"No" to what? I'm a bit confused :-/

I have created a PR with the change. This is one of my first contributions to an established repository, so please offer suggestions and advice if it is A) terrible or B) lacking something!

@alawatthe It was a message to @ashclarke sorry. ;-)
I'm talking about defaults, and presets can help with that.

@zxqfox Ah, now I get it. No problem :-D


NTR: Papadam

NTR: Poppadom
Parent Term/Class:
Open for discussion as I would like to put it under flour product,

flour food product
cultural food product

Definition:
A {requested parent term} {which/during which} is either fried or cooked with dry heat (flipped over an open flame) until crunchy
Definition Source:
Papadam}
Synonym(s):
Exact Synonym(s):
Poppadom
Additional Comments (not an annotation):
As this can be made from many flours I don't think this can go any lower in the flour hierarchy. It is also of Indian origin if there is a way to connecting it to that part of the ontology.

This is already in foodon as http://purl.obolibrary.org/obo/FOODON_03307020 Poppadum with synonym you gave. Now currently we have it under "bread food product" but that ties it too closely to wheat.  We will discuss at next foodon curation meeting.

Ah. I was using the search via https://www.ebi.ac.uk/ols/search?q=poppadom&ontology=foodon and it didn't find it. Found it now, thanks.
Yeah it feels more flour food rather than bread.

A delay in this but now resolved in upcoming FoodOn draft.  Bread food product is no longer committed to having wheat as ingredient.


Send calls without a AuthHandler hang

Since we enable ZAP by default, when no zap handler is running, send calls will hang forever.
There are 2 possible solutions I can think off:

Create a ZAP handler for every context.
Check for ZAP related events before sending to detect when a auth attempt failed. Maybe make connect calls blocking?

I think creating a ZAP handler per contex is the better approach.

Spawning the ZAP handler for each ctx does the trick. But now we got another issue.


waitForDomChange Implementation

What:
waitForDomChange is implemented along with tests, documentation, and types.
waitForElement is changed to require a callback function
Why:
Resolves issue number #111
How:
I copied much of what was in waitForElement. They are very similar
Checklist:

[x] Documentation
[x] Tests
[x] Ready to be merged
[x] Added myself to contributors table

Yep, I’m happy to do these things! This is a great learning experience for me! I look forward to revisit everything and seeing what is conducive to good tests and nicely written code.
Per the formatting. I installed doctoc and thought that would format everything in the read me correctly. I will use kcd-scripts format now.
..........................................................
Alex Wendte
Senior, Kansas State University
College of Engineering, Computer Science
<EMAIL_ADDRESS>
On Oct 9, 2018, at 9:32 PM, Kent C. Dodds<EMAIL_ADDRESS>wrote:
@kentcdodds commented on this pull request.
Thanks! A few comments/questions/requests :)
In README.md:

fireEvent

fireEvent[eventName]

getNodeText
Yep, let's remove one of the # from getNodeText 👍 Do you mind doing that @themostcolm?

In README.md:

@@ -989,13 +1021,12 @@ Thanks goes to these people ([emoji key][emojis]):

-
Kent C. Dodds💻 📖 🚇 ⚠
Ryan Castner📖
Daniel Sandiego💻
Paweł Mikołajczyk💻
Alejandro Ñáñez Ortiz📖
Matt Parrish🐛 💻 📖 ⚠
Justin Hall📦

-
Anto Aravinth💻 ⚠ 📖
Jonah Moses📖
Łukasz Gandecki💻 ⚠ 📖
Ivan Babak🐛 🤔 💻 📖
Jesse Day💻
Ernesto García💬 💻 📖
Josef Maxx Blake💻 📖 ⚠

-
Alex Cook📖 💡
Daniel Cook💻 📖 ⚠
Thomas Chia🐛 💻
Tim Deschryver💻 ⚠
Alex Krolick💻
Maddi Joyce💻
Peter Kamps🐛 💻 ⚠

-
Jonathan Stoye📖
Sanghyeon Lee💡
Justice Mba 💻 📖 🤔
Wayne Crouch💻
Ben Elliott💻
Ruben Costa💻
Robert Smith🐛 🤔 📖

-
dadamssg💻
Neil Kistner💻
Ben Chauvette💻
Jeff Baumgardt💻 📖
Matan Kushner💻 📖 🤔 ⚠

+| Kent C. Dodds💻 📖 🚇 ⚠ | Ryan Castner📖                                                                                | Daniel Sandiego💻                                                                                | Paweł Mikołajczyk💻                                                                                | Alejandro Ñáñez Ortiz📖                                                                                | Matt Parrish🐛 💻 📖 ⚠ | Justin Hall📦                                                                                |
I think your editor messed some stuff up here... Could you make sure that the precommit hooks run so prettier will automatically format this properly?
You could also run npx kcd-scripts format before committing to be sure.
In src/tests/wait-for-dom-change.js:

@@ -0,0 +1,172 @@
+import {waitForDomChange} from '../'
+// adds special assertions like toBeTruthy
+import 'jest-dom/extend-expect'
+import {render} from './helpers/test-utils'

The code below could be simplified:
const skipSomeTime = (delayMs) => new Promise(resolve => setTimeout(resolve, delayMs))
// Using setTimeout >30ms instead of wait here
// because mutationobserver-shim uses setTimeout ~30ms.
const skipSomeTimeForMutationObserver = (delayMs = 50) => skipSomeTime(delayMs)
In src/tests/wait-for-dom-change.js:

const errorHandler = jest.fn().mockName('errorHandler')

const promise = waitForDomChange().then(successHandler, errorHandler)

// Promise callbacks are always asynchronous.
expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)

await skipSomeTimeForMutationObserver()

// No more expected calls without DOM mutations.
expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)

document.body.appendChild(document.createElement('div'))
expect(document.body).toMatchSnapshot()
I don't think the snapshots are necessary.

In src/tests/wait-for-dom-change.js:

await skipSomeTimeForMutationObserver()

// No more expected calls without DOM mutations.
expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)

document.body.appendChild(document.createElement('div'))
expect(document.body).toMatchSnapshot()

await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(1)
expect(successHandler).toHaveBeenCalledWith(true)
expect(errorHandler).toHaveBeenCalledTimes(0)
expect(document.body).toMatchSnapshot()
This one isn't necessary either.

In src/tests/wait-for-dom-change.js:

// No more expected calls without DOM mutations.
expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)

document.body.appendChild(document.createElement('div'))
expect(document.body).toMatchSnapshot()

await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(1)
expect(successHandler).toHaveBeenCalledWith(true)
expect(errorHandler).toHaveBeenCalledTimes(0)
expect(document.body).toMatchSnapshot()

return promise
We don't need to return this promise. Please remove this.

In src/tests/wait-for-dom-change.js:

+import {render} from './helpers/test-utils'

+async function skipSomeTime(delayMs) {

await new Promise(resolve => setTimeout(resolve, delayMs))
+}

+async function skipSomeTimeForMutationObserver(delayMs = 50) {

// Using setTimeout >30ms instead of wait here because mutationobserver-shim uses setTimeout ~30ms.
await skipSomeTime(delayMs, 50)
+}

+test('it waits for the next DOM mutation', async () => {

const successHandler = jest.fn().mockName('successHandler')
const errorHandler = jest.fn().mockName('errorHandler')

const promise = waitForDomChange().then(successHandler, errorHandler)
We don't need access to this promise, please remove the variable assignment.

In src/tests/wait-for-dom-change.js:

+test('it waits characterData mutation', async () => {

const {container} = render(
initial text
)

const successHandler = jest.fn().mockName('successHandler')
const errorHandler = jest.fn().mockName('errorHandler')

const promise = waitForDomChange({container}).then(
successHandler,
errorHandler,
)

// Promise callbacks are always asynchronous.
expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)
expect(container).toMatchSnapshot()
Remove this

In src/tests/wait-for-dom-change.js:

// Promise callbacks are always asynchronous.

expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)
expect(container).toMatchSnapshot()

await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)

container.querySelector('div').innerHTML = 'new text'
await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(1)
expect(errorHandler).toHaveBeenCalledTimes(0)
expect(container).toMatchSnapshot()
Remove this

In src/tests/wait-for-dom-change.js:

expect(errorHandler).toHaveBeenCalledTimes(0)

expect(container).toMatchSnapshot()

await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)

container.querySelector('div').innerHTML = 'new text'
await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(1)
expect(errorHandler).toHaveBeenCalledTimes(0)
expect(container).toMatchSnapshot()

return promise
Remove this

In src/tests/wait-for-dom-change.js:

container,

}).then(successHandler, errorHandler)

expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)

await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)

container.setAttribute('data-test-attribute', 'PASSED')
await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(1)
expect(successHandler).toHaveBeenCalledWith(true)
Agreed, that's a good question. Why don't we have the success handler be called with the mutationsList which the mutation observer will give our callback?

In src/tests/wait-for-dom-change.js:

expect(successHandler).toHaveBeenCalledTimes(0)

expect(errorHandler).toHaveBeenCalledTimes(0)

await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)

container.setAttribute('data-test-attribute', 'PASSED')
await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(1)
expect(successHandler).toHaveBeenCalledWith(true)
expect(errorHandler).toHaveBeenCalledTimes(0)

return promise
Remove this

In src/tests/wait-for-dom-change.js:

await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(0)

container.setAttribute('data-test-attribute', 'PASSED')
await skipSomeTimeForMutationObserver()

expect(successHandler).toHaveBeenCalledTimes(1)
expect(successHandler).toHaveBeenCalledWith(true)
expect(errorHandler).toHaveBeenCalledTimes(0)

return promise
+})

+test('it throws if timeout is exceeded', async () => {
I feel like this test could be simplified without losing any amount of confidence:
test('it throws if timeout is exceeded', async () => {
const {container} = render('')
const successHandler = jest.fn().mockName('successHandler')
const errorHandler = jest.fn().mockName('errorHandler')
waitForDomChange({timeout: 70}).then(successHandler, errorHandler)
await skipSomeTimeForMutationObserver(100)
expect(successHandler).toHaveBeenCalledTimes(0)
expect(errorHandler).toHaveBeenCalledTimes(1)
expect(errorHandler.mock.calls[0]).toMatchInlineSnapshot() // <-- this'll get updated by jest inline when you run the tests. It's pretty cool 👍
})
In src/wait-for-dom-change.js:

 setImmediate(() => observer.disconnect())

 if (error) {

   reject(error)

 } else {

   resolve(result)

 }

}
function onMutation() {

 onDone(null, true)

}
function onTimeout() {

 onDone(lastError || new Error('Timed out in waitForDomChange.'), null)

}
timer = setTimeout(onTimeout, timeout)
observer = new window.MutationObserver(onMutation)
observer.observe(container, mutationObserverOptions)
I'd prefer if we could reuse the code 👍

In src/wait-for-dom-change.js:

@@ -0,0 +1,37 @@
+import 'mutationobserver-shim'

+function waitForDomChange({

container = document,
timeout = 4500,
mutationObserverOptions = {
subtree: true,
childList: true,
attributes: true,
characterData: true,
},
+} = {}) {
return new Promise((resolve, reject) => {
// Disabling eslint prefer-const below: either prefer-const or no-use-before-define triggers.
let lastError, observer, timer // eslint-disable-line prefer-const
I'm pretty sure that if you remove observer and timer from here and use a const declaration below you should be fine :)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

You may need to run npx kcd-scripts contributors generate first to get the table fixed up, and then run npx kcd-scripts format 👍

It would be nice to see some tests around this in react-testing-library. Do all mutations fire at the same time each render or could there be race conditions if you are expecting a mutation deeper in the tree?

This does not look to be taking care of removing this functionality from waitForElement (and hence the problematic callback-less waitForElement form). Just checking. If it's going to be taken care of in a separate PR, that's fine too.

Good point @gnapse.
@themostcolm, could you please do that as well. It's technically breaking a use case that we never expected/recommended so I'm not going to make it a major version bump.

I was worried that it would be a breaking change if people were relying on waitForElement with a callback to test for dom changes. The new change would make it so waitForElement without a callback would do nothing correct? Or maybe I am not understanding correctly.

Absolutely!

Would you like me to update the branch and then squash everything into one commit, or do you would prefer separate commits?

Nope, we're good. Thanks @alexwendte!

Thanks so much for your help! I've added you as a collaborator on the project. Please make sure that you review the other/MAINTAINING.md and CONTRIBUTING.md files (specifically the bit about the commit messages and the git hooks) and familiarize yourself with the code of conduct (we're using the contributor covenant). You might also want to watch the repo to be notified when someone files an issue/PR. Please continue to make PRs as you feel the need (you can make your branches directly on the repo rather than your fork if you want). Thanks! And welcome to the team :)

Awesome, thanks so much Kent, I appreciate it! I’ve already learned a ton because of your generosity with recording workshops. I absolutely love the way you code, so I’m looking forward to getting to help out with what you’re working on!
..........................................................
Alex Wendte
Senior, Kansas State University
College of Engineering, Computer Science
<EMAIL_ADDRESS>
On Oct 11, 2018, at 11:07 AM, Kent C. Dodds<EMAIL_ADDRESS>wrote:
Thanks so much for your help! I've added you as a collaborator on the project. Please make sure that you review the other/MAINTAINING.md and CONTRIBUTING.md files (specifically the bit about the commit messages and the git hooks) and familiarize yourself with the code of conduct (we're using the contributor covenant). You might also want to watch the repo to be notified when someone files an issue/PR. Please continue to make PRs as you feel the need (you can make your branches directly on the repo rather than your fork if you want). Thanks! And welcome to the team :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


UpdateStatistics option INDEX on selected objects

Description of the issue
UpdateStatistics option 'ALL' and 'INDEX' don't generate UPDATE STATISTICS on INDEX with selected objects ('ALL' and 'COLUMNS' work fine for column statistics)
ALL option, used when rebuilding a whole db, no objects selected, work fine and produced UPDATE STATISTICS for columns and indexes
the statement UPDATE STATISTICS [DB_Check].[dbo].[DB_Remote_Instance] [PK_DB_Remote_Instance] is missing in the command result below
SQL Server version and edition
All versions
Version of the script
The latest (I guess all)
What command are you executing?
EXECUTE [dbo].[IndexOptimize]
@Databases = '[DB_Check]',
@Indexes = '[DB_Check].[dbo].[DB_Remote_Instance].[PK_DB_Remote_Instance]',
@MinNumberOfPages = 0,
@MaxDOP = 4,
@FragmentationLevel1 = 5,
@FragmentationLevel2 = 30,
@FragmentationLow = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
@FragmentationMedium = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
@FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
@UpdateStatistics = 'INDEX',
@OnlyModifiedStatistics = 'N',
@SortInTempdb = 'Y',
@FillFactor = 80,
@WaitAtLowPriorityMaxDuration = 60,
@WaitAtLowPriorityAbortAfterWait = 'SELF',
@LogToTable = 'Y',
@Execute = 'Y'
What output are you getting?
Date and time: 2020-06-05 12:16:52
Server: CHLU1W6VSQL02\DBA01
Version: 15.0.2000.5
Edition: Enterprise Edition: Core-based Licensing (64-bit)
Platform: Windows
Procedure: [master].[dbo].[IndexOptimize]
Parameters: @Databases = '[DB_Check]', @FragmentationLow = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationMedium = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationLevel1 = 5, @FragmentationLevel2 = 30, @MinNumberOfPages = 0, @MaxNumberOfPages = NULL, @SortInTempdb = 'Y', @MaxDOP = 4, @FillFactor = 80, @PadIndex = NULL, @LOBCompaction = 'Y', @UpdateStatistics = 'INDEX', @OnlyModifiedStatistics = 'N', @StatisticsModificationLevel = NULL, @StatisticsSample = NULL, @StatisticsResample = 'N', @PartitionLevel = 'Y', @MSShippedObjects = 'N', @Indexes = '[DB_Check].[dbo].[DB_Remote_Instance].[PK_DB_Remote_Instance]', @TimeLimit = NULL, @Delay = NULL, @WaitAtLowPriorityMaxDuration = 60, @WaitAtLowPriorityAbortAfterWait = 'SELF', @Resumable = 'N', @AvailabilityGroups = NULL, @LockTimeout = NULL, @LockMessageSeverity = 16, @StringDelimiter = ',', @DatabaseOrder = NULL, @DatabasesInParallel = 'N', @LogToTable = 'Y', @Execute = 'Y'
Version: 2020-01-26 14:06:53
Source: https://ola.hallengren.com
Date and time: 2020-06-05 12:16:52
Database: [DB_Check]
State: ONLINE
Standby: No
Updateability: READ_WRITE
User access: MULTI_USER
Recovery model: SIMPLE
Is accessible: Yes
Date and time: 2020-06-05 12:16:52
Database context: [DB_Check]
Command: ALTER INDEX [PK_DB_Remote_Instance] ON [dbo].[DB_Remote_Instance] REBUILD WITH (SORT_IN_TEMPDB = ON, ONLINE = ON (WAIT_AT_LOW_PRIORITY (MAX_DURATION = 60, ABORT_AFTER_WAIT = SELF)), MAXDOP = 4, FILLFACTOR = 80, RESUMABLE = OFF)
Comment: ObjectType: Table, IndexType: Clustered, ImageText: No, NewLOB: No, FileStream: No, ColumnStore: No, AllowPageLocks: Yes, PageCount: N/A, Fragmentation: N/A
Outcome: Succeeded
Duration: 00:00:00
Date and time: 2020-06-05 12:16:52
Date and time: 2020-06-05 12:16:52
Completion time: 2020-06-05T12:16:52.4296454+02:00

I found a workaround without altering the code, the ALL and INDEX option for selected objects issue the UPDATE STATISTICS for the  indexes when the  IndexOptimize is called for statistics only, so with options:
@FragmentationLow = NULL,
@FragmentationMedium = NULL,
@FragmentationHigh = NULL,
However, that misbehaviour can cause problems with execution plans, I had to prepare a job for a set of tables that change very often for a db of an eCommerce portal, and we noticed the bug because it was rebuilding correctly, but from time to time it wasn't helping in speeding certain queries

I found out that, since with the parameters I was forcing a REBUILD, the index statistics are computed with the REBUILD, that's why the statement is not issued, sorry for bothering


fix: expand the clickable area of the remove button in the Upload

Types of changes

[ ] New feature
[x] Bug fix
[ ] Documentation change
[ ] Coding style change
[ ] Component style change
[ ] Refactoring
[ ] Performance improvement
[ ] Test cases
[ ] Continuous integration
[ ] Typescript definition change
[ ] Breaking change
[ ] Others

Background and context

Solution

How is the change tested?

Changelog

Component
Changelog(CN)
Changelog(EN)
Related issues

Checklist:

[ ] Test suite passes (npm run test)
[ ] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[ ] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others should be submitted to main branch)

Other information

fix: #456


js promises

Does Postman support javascript promises? I would like to download schema used by Tiny Validator and run tests. Something like below:
.success(function(response){
        var schema = reponse.data;
        var user = JSON.parse(responseBody);
        tests["Valid user"] = tv4.validate(user, schema);
    })```

But there is an issue that Postman doesn't execute such tests if there is longer GET delay.

https://github.com/a85/POSTMan-Chrome-Extension/issues/719


Add application name for docs tracking

part of https://cockroachlabs.atlassian.net/browse/DOC-4617
need to test to make sure this shows up correctly, not sure how

need to test to make sure this shows up correctly, not sure how

Did some searching, apologies if this is stuff you already found / know:
Hibernate docs don't show connection.application_name but say

hibernate.connection.*
All such setting names (except the predefined ones) will have the hibernate.connection. prefix stripped. The remaining name and the original value will be passed to the driver as a JDBC connection property

As you may have already seen in our docs

Note: For Java JDBC, use ApplicationName.

Since Hibernate docs say they just pass the value through to JDBC, I think the XML property should probably be called hibernate.connection.ApplicationName.
Re: testing that, I'd have the team monitoring these connection strings try some end to end testing once this PR merges and see what happens.

tftr!


Enhancement: Handle headers in BedrockError

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503
It is recommended that a 503 error contain a Retry-After header.  It would be good if one could specify headers when throwing a BedrockError that would be handled here.

BedrockError hasn't grown a formal way to do things like this.  An issue is that right now it just has a plain details field.  But no way to easily say some fields (like httpStatusCode) are special.  We could add more ad-hoc fields that this module knows how to handle.  A httpRetryAfter could work, but we'd have to check for 503, 429, etc before adding.  More flexible would just be httpHeaders.  There are probably sanity and security issues of arbitrary modules changing headers by just throwing an error.  Scanning a cause chain for this might be an issue too, but the httpStatusCode code has worked so far.


BIDBOT_DEAL_DATA_DIRECTORY doesn't always work

When running bidbot, sometimes new data downloads are put in the directory I specify in the env variable, and other times it just puts them in the default .bidbot/deal_data folder.

Looks like this was caused by a problem on my end with the env variables.


Entry exist event state transition #12

here is finally my pull request base on the issue #12
I made a change for the constructor of the FSM, in that case we are sure to call the same constructor from other constructor, I need to trigger the first onEntry for the initial state
I test the build with netBeans 8.2, maybe I need to write some test for that ?
let me know what do I need to change

@developer-x any review done ?
or nobody work on it anymore ?

I'm still working on it when I can.  I've been heads down on my new venture.  Hope to get to this soon.

@developer-x, any update with such issue, hope it could be merged and it's better that statefulj could take scxml standard into action as statefulj lacks the support for standard.

Still haven't had a chance to look into it.  Hadn't heard of the scxml
effort - would be interested in looking into it's compliance.  I hope to
get to this soon.

Anderw

On Sun, Jul 2, 2017 at 6:18 AM, bwzhang2012<EMAIL_ADDRESS>wrote:

@developer-x https://github.com/developer-x, any update with such
issue, hope it could be merged and it's better that statefulj could take
scxml standard into action as statefulj lacks the support for standard.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/statefulj/statefulj/pull/30#issuecomment-312491410,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADAYk82amK-GX05GLZJukb__qMcfaS3Eks5sJ5imgaJpZM4NhbTu
.

@developer-x, thanks for view and here came some suggestion from scxml:

scxml standard: https://www.w3.org/TR/scxml/
scxml apache commons: https://github.com/apache/commons-scxml
scxml java: https://github.com/carlos-verdes/scxml-java
as scxml standard seems more open with a lot of languages support and also scxml gui tool, I think long term that statefulj could take it into consideration. by the way, hope the onEntry and onExit could be merged once formed.

@bwzhang2011 you should do a fork of this project I think, looks like nobody care about this issue. you can grab my pull request if you need

I'm going to close it since nobody got back at me...


[KiField Bug] Kifield not compatible with Kicad 7

Describe the bug
A clear and concise description of what the bug is.
Although I was able to read from the V7 library file (.kicad_sym) into an excel sheet the write back was unsuccessful.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error
See output from Kifield below

Expected behavior
A clear and concise description of what you expected to happen.
Normal execution
Screenshots
If applicable, add screenshots to help explain your problem.
Traceback (most recent call last):
File "C:\Users\mlindsey\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 196, in _run_module_as_main
return run_code(code, main_globals, None,
File "C:\Users\mlindsey\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 86, in run_code
exec(code, run_globals)
File "C:\Users\mlindsey\PycharmProjects\pythonProject\venv\Scripts\kifield.exe_main.py", line 7, in
File "C:\Users\mlindsey\PycharmProjects\pythonProject\venv\lib\site-packages\kifield_main.py", line 149, in main
kifield(
File "C:\Users\mlindsey\PycharmProjects\pythonProject\venv\lib\site-packages\kifield\kifield.py", line 1554, in kifield
insert_part_fields(
File "C:\Users\mlindsey\PycharmProjects\pythonProject\venv\lib\site-packages\kifield\kifield.py", line 1518, in insert_part_fields
insertion_function(
File "C:\Users\mlindsey\PycharmProjects\pythonProject\venv\lib\site-packages\kifield\kifield.py", line 1407, in insert_part_fields_into_lib_V6
component.copy_field("Reference", field_name)
File "C:\Users\mlindsey\PycharmProjects\pythonProject\venv\lib\site-packages\kifield\schlib.py", line 568, in copy_field
id = find_by_key("id", dst_field["prop"])[0]
IndexError: list index out of range
Desktop (please complete the following information):

OS [type & version] windows10
Python version
-Python 3.10.7 (tags/v3.10.7:6cc6b13, Sep  5 2022, 14:08:36) [MSC v.1933 64 bit (AMD64)] on win32
KiField version [e.g. 0.1.22]
1.0.0
KiCad version
7.0.0
Additional context
Add any other context about the problem here.
This program is very useful! The structure of the library files has been changed for V7, it looks simpler

Any update on this? I just spend a couple hours crafting a merged BOM spreadsheet into the KiField-generated exported spreadsheet, only to find I couldn't reimport it back again. Apparently because I'm using KiCad 7.  Any workarounds in the meantime?

I updated this program last year when KiCad 6 appeared with new file formats. Now they've updated file formats (or something) and broken things again. I guess it will remain broken until I run out of more interesting things to do.

I did some digging around, and confirmed my suspicion that the schematic format was updated in v6. I'm not aware of changes in v7. Also, I'm not sure my error messages were exactly the same as @dilydaly1 reported. Let me re-run and see if the messages give any clues

Similar, but not identical errors. Here is the error message running in Windows. Looks like @dilydaly1 was updating a library file, while I was trying to update a schematic file.
C:\files\projs\hybo\eda\robot-interface-mini>kifield -x fields.xlsx -i robot-interface-mini.kicad_sch -w
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Users\owner\.pyenv\pyenv-win\versions\3.11.4\Scripts\kifield.exe\__main__.py", line 7, in <module>
  File "C:\Users\owner\.pyenv\pyenv-win\versions\3.11.4\Lib\site-packages\kifield\__main__.py", line 149, in main
    kifield(
  File "C:\Users\owner\.pyenv\pyenv-win\versions\3.11.4\Lib\site-packages\kifield\kifield.py", line 1554, in kifield
    insert_part_fields(
  File "C:\Users\owner\.pyenv\pyenv-win\versions\3.11.4\Lib\site-packages\kifield\kifield.py", line 1518, in insert_part_fields
    insertion_function(
  File "C:\Users\owner\.pyenv\pyenv-win\versions\3.11.4\Lib\site-packages\kifield\kifield.py", line 1209, in insert_part_fields_into_sch_V6
    component.copy_field("Reference", field_name)
  File "C:\Users\owner\.pyenv\pyenv-win\versions\3.11.4\Lib\site-packages\kifield\sch.py", line 497, in copy_field
    id = find_by_key("id", dst_field["prop"])[0]
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^
IndexError: list index out of range

And here is the error when running in WSL / Ubuntu
rclott@stumbler robot-interface-mini$ kifield -x fields.xlsx -i robot-interface-mini.kicad_sch -w
Traceback (most recent call last):
  File "/home/rclott/.pyenv/versions/3.10.10/bin/kifield", line 33, in <module>
    sys.exit(load_entry_point('kifield==1.0.0', 'console_scripts', 'kifield')())
  File "/home/rclott/.pyenv/versions/3.10.10/lib/python3.10/site-packages/kifield/__main__.py", line 149, in main
    kifield(
  File "/home/rclott/.pyenv/versions/3.10.10/lib/python3.10/site-packages/kifield/kifield.py", line 1554, in kifield
    insert_part_fields(
  File "/home/rclott/.pyenv/versions/3.10.10/lib/python3.10/site-packages/kifield/kifield.py", line 1518, in insert_part_fields
    insertion_function(
  File "/home/rclott/.pyenv/versions/3.10.10/lib/python3.10/site-packages/kifield/kifield.py", line 1209, in insert_part_fields_into_sch_V6
    component.copy_field("Reference", field_name)
  File "/home/rclott/.pyenv/versions/3.10.10/lib/python3.10/site-packages/kifield/sch.py", line 497, in copy_field
    id = find_by_key("id", dst_field["prop"])[0]
IndexError: list index out of range

I think I have a release candidate that solves the KiCad7 problems. You can install it like this:
pip install git+https://github.com/devbisme/KiField

If you find errors, I'll try to fix them. If not, I'll prepare a release on PyPi.


Enable disabled question

Added the methods to ask the job if it is enabled? or disabled?

If you fix y comments I will merge it.

Done, I am using always the explicit return way, because I like to see always what a method returns.
But if it is best practice in this project I don't mind.
Thx for merging.

How is it now?


Fix several indentation problems, following ruby best practices guide

'New' hash syntax
Blank Spaces
Repeated code

@marceloboeira Thanks for the initiative, but chances are we aren't going to be able to accept this PR as switching to the new hash syntax causes the library to stop working in ruby 1.8.7.

@joncalhoun well, you shouldn't just stop improving your code just because you would not support old ruby versions... You really should explore the possibility of keeping the legacy code on a 1.x version/branch, and a 2.x version with support and future improvements...

:clap:

@marceloboeira We are still improving the code. We are just opting to use the 1.8.7 style hashes so that the improvements also work for older ruby versions without having to manage two gem versions.

:disappointed:


[✨] Finished Settings application

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update package/cosmos api usage in integration tests

High Level Description
This is the same as https://github.com/dcos/dcos/pull/1833 (PR to master)
I had the interface wrong on the dcos_api_session.cosmos endpoint in dcos-test-utils, where install didn't take all of the options, and install and uninstall had some options as required when only the packageName is required.
Related Issues
This is all ultimately to support the tweeter integration test
https://github.com/mesosphere/dcos-enterprise/pull/1303
Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review

@mellenburg Can you review this please? The corresponding branch has already been merged into master.

@mesosphere-mergebot bump-ee


Update README.md

fixed some typos

@pidator the upsnutwrapper script got updated to version 1.9 with a lot more commands. just in case you wanna update.


New official Pytorch EMA gives RunTimeError when using Lightning with DDP

Bug description
Hi, I'm trying to use the official PyTorch EMA (new feature: https://pytorch.org/docs/main/optim.html#weight-averaging-swa-and-ema) in Lightning in DDP. To do this I've done:
self.ema_model = torch.optim.swa_utils.AveragedModel(self.model, multi_avg_fn = torch.optim.swa_utils.get_ema_multi_avg_fn(ema_rate))

And then I update the EMA model after the optimizer steps, using the LightningModule hook:
def on_before_zero_grad(self, optimizer):
    if self.ema_model is not None:
        self.ema_model.update_parameters(self.model)

And then at the end of training update the BN params and replace the 'normal' model with the EMA model:
def on_train_end(self):
    # Our final validation will use the ema model, as it replaces our normal model
    if self.ema_model is not None:
        logger.info("Updating the EMA model's BatchNormal layers...")
        torch.optim.swa_utils.update_bn(self.trainer.train_dataloader, self.ema_model)
        logger.info("Replacing the standard model with the EMA model for last validation run")
        self.model = self.ema_model

The issue is I get an error because Lightning tries to DDP the self.ema_model in the LightningModule, and because it doesn't have any gradients, Pytorch throws an error:
RuntimeError: DistributedDataParallel is not needed when a module doesn't have any parameter that requires a gradient.

Do you know if I can/should just keep the  self.ema_model on rank0, and stop it being distributed, like self.model?
What version are you seeing the problem on?
v2.0
How to reproduce the bug
As above
Error messages and logs
RuntimeError: DistributedDataParallel is not needed when a module doesn't have any parameter that requires a gradient.

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response
cc @justusschock @awaelchli

I think what is also missing is the on_after_optimizer_step hook.

Have you tried to run the EMA update in the optimizer_step?
I am asking because I am not 100 percent sure yet when this step is called and the model parameters it effects.
My code is such
    def optimizer_step(self, epoch: int,
        batch_idx: int,
        optimizer,
        optimizer_closure):
        optimizer.step(closure=optimizer_closure)
        self._update_ema()

My followup question is also, when the DDP training is done and checkpointing occurs, how is the EMA model going to be saved? Like if I have 4 nodes/1 device per node
how is the EMA model combined at the end to produce one model in the state dict


Use poetry-core in pyproject.toml

This makes strip-ansi buildable with modern poetry installations, following the guidelines on
https://python-poetry.org/docs/basic-usage/

thx!


Can not start: Runtime.executionContextCreated has invalid 'cont ext'

yesterday I could not start wechaty under win32 in sudden.
the log is: WebDriverError: unknown error: Runtime.executionContextCreated has invalid 'cont ext': {"auxData":{"frameId" isDefault":true} ...
after hours digging, I found out that I was using a out dated chromedriver, which can not work any more after I upgrade chrome to v54.
https://github.com/SeleniumHQ/selenium/issues/2614#issuecomment-255293479

I am still unable to run tests in chrome though I have the latest chrome drivers. please read the comments here: SeleniumHQ/selenium#2614 (comment)

@faminram sorry I have no idea of that after look your issue.
my issue was solved after I deleted the old driver, and specific the node_modules/... driver inside my code.
you can have a look inside my commit, that solve my issue perfectly.
good luck.


Typescript: Object function properties are auto completed differently depending on notation used in type definition

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

Version: 1.86.1 (user setup)
Commit: 31c37ee8f63491495ac49e43b8544550fbae4533
Date: 2024-02-07T09:08:20.941Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
Steps to Reproduce:
Define type as following and auto complete for that property when used with typeof and bracket property access will autocomplete differently for function properties depending on the notation used:
const foo = {
    // object property defined with function property notation
    property: (a: string, b: number, c: boolean) => void,
    // object property defined with method notation
    method(a: string, b: number, c: boolean): void;
}

type PropertyArgs = Parameters<typeof foo['']> // ✅ auto completes property just name correctly

type MethodArgs = Parameters<typeof foo['']> // ❌ auto completes property name with arguments

Demo:

Expectation
Auto complete should only complete property names when used with typeof as above, regardless of how property types are defined.

Only happens when "typescript.suggest.completeFunctionCalls": true is enabled


Problem with writing video

Whenever I try to specify the where I want the data to be recorded I get this error:
"Could not load file or assembly 'AForge.Video, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cbfb6e07d173c401' or one of its dependencies. The system cannot find the file specified."
Are you familiar with this? Am I doing something wrong?

I get the same error... any update on this issue?
Thanks

Same error here.


GPU widget

Dev Home version
<IP_ADDRESS>
Windows build number
10.0.23486.1000
Other software
OS Build Version: 10.0.23486.1000.amd64fre.ni_prerelease.230616-1447
.NET Version: .NET 6.0.16
Steps to reproduce the bug
GPU widget sees both of my GPUs but only shows activity for my intel GPU when I switch to my NVidia GPU I get no readings. Task manager shows activity for both GPUs
Expected result
Fix the GPU widget, the built-in task manager has no trouble showing utilization and temperature
Actual result
unsure what this means
Included System Information
Physical Memory: 31.67GB (15.87GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome_<IP_ADDRESS>_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_<IP_ADDRESS>_x64__8wekyb3d8bbwe

Temperature issue tracked by #739


chore: add a docker compose file for standalone mode

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
add a docker-compose file for standalone mode. Will update the docs.
resolve #12538
Documentation

[x] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Thanks!

LGTM
Actually, I think we can go one step further and use standalone mode in Docker by default. That is, instead of adding a new docker-compose-standalone.yaml, I think we can place the existing docker-compose.yaml, because that a user preferring docker-compose than k8s must want to deploy RW in a single machine.
But this may involve some modifications to test pipeline as well. Since the v1.4 is coming soon, we may do it later.

@lmatz Was this PR included in v1.4? I don't see it in the comparison list (1.3-rc - 1.4-rc). And I assume using the standalone mode in Docker by default is not done yet. Correct? Thanks.

LGTM
Actually, I think we can go one step further and use standalone mode in Docker by default. That is, instead of adding a new docker-compose-standalone.yaml, I think we can place the existing docker-compose.yaml, because that a user preferring docker-compose than k8s must want to deploy RW in a single machine.
But this may involve some modifications to test pipeline as well. Since the v1.4 is coming soon, we may do it later.

@lmatz Was this PR included in v1.4? I don't see it in the comparison list (1.3-rc - 1.4-rc). And I assume using the standalone mode in Docker by default is not done yet. Correct? Thanks.

Hi @hengm3467,
It is not ready yet, and not included in v1.4. The default deployment of docker compose is still non-standalone mode.
We will need to do some tests first, details in
https://github.com/risingwavelabs/risingwave-docs/issues/1187


Update log ingestion articles

Purpose of this pull request
This pull request (PR) updates articles about log ingestion.
Issue number: #3206

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[x] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

Thanks, @stacykor!


After installing using the "cat method", installing any chart results in Error: Error response from daemon: invalid 'CapAdd: unknown capability: "CAP_OVERRIDE"'

What happend: Installed multus-cni using recommended git clone + cat method. Had a network attachment defined, but removed it, and problem persisted
What you expected to happen: helm install would still work.
How to reproduce it (as minimally and precisely as possible): Unknown what root cause is. Grep of code does not reveal CAP_OVERRIDE string. Possibly coming from weave (original default CNS).
Anything else we need to know?:
Environment:
RTIFACTORY_DOCKER_REPO_URL=http://docker-virtual-shrinkray.artifactorylbj.it.keysight.com/
ARTIFACTORY_JFROG_CLI_KEY=AKCp8igrFUgPTL7NwDHKS5TKFe9oyqcCaKQaUVNKQ9WKTAwV1nbEPTSbWi4ppaJCNKqeu14Xv
ARTIFACTORY_JFROG_CLI_USER=lythomps
BASH=/bin/bash
BASHOPTS=checkwinsize:cmdhist:complete_fullquote:expand_aliases:extquote:force_fignore:hostcomplete:interactive_comments:login_shell:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=()
BASH_ARGV=()
BASH_CMDS=()
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="4" [1]="4" [2]="20" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu")
BASH_VERSION='4.4.20(1)-release'
COLUMNS=163
DIRSTACK=()
ESCDELAY=25
EUID=0
GROUPS=()
HISTFILE=/root/.bash_history
HISTFILESIZE=500
HISTSIZE=500
HOME=/root
HOSTNAME=shrinkray5
HOSTTYPE=x86_64
IFS=$' \t\n'
LANG=C.UTF-8
LINES=34
LOGNAME=root
MACHTYPE=x86_64-pc-linux-gnu
MAIL=/var/mail/root
MAILCHECK=60
OLDPWD=/etc/cni
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
PIPESTATUS=([0]="0" [1]="0")
PPID=5257
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w$ '
PS2='> '
PS4='+ '
PWD=/opt/cni
SHELL=/bin/bash
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
SHLVL=1
SSH_CLIENT='<IP_ADDRESS> 50046 9022'
SSH_CONNECTION='<IP_ADDRESS> 50046 <IP_ADDRESS> 9022'
SSH_TTY=/dev/pts/0
TERM=xterm-256color
UID=0
USER=root
XDG_RUNTIME_DIR=/run/user/0
XDG_SESSION_ID=3

Multus version
image path and image ID (from 'docker images')
nfvpe/multus                                                                   stable                             9b13777edc63        7 months ago        277MB
nfvpe/multus                                                                   v3.4                               7cf8e2d1b733        14 months ago       312MB

Kubernetes version (use kubectl version):

Primary CNI for Kubernetes cluster: weave

OS (e.g. from /etc/os-release): Ubuntu 18.04.5 LTS

File of '/etc/cni/net.d/'

-rw------- 1 root root  349 Feb 19 02:06 00-multus.conf
-rw-r--r-- 1 root root  318 Oct 21 21:51 10-weave.conflist

File of '/etc/cni/multus/net.d'
-rw------- 1 root root 2607 Feb 19 02:06 multus.kubeconfig

NetworkAttachment info (use kubectl get net-attach-def -o yaml)
apiVersion: v1
items: []
kind: List
metadata:
resourceVersion: ""
selfLink: ""

Target pod yaml info (with annotation, use kubectl get pod <podname> -o yaml)
apiVersion: v1
kind: Pod
metadata:
annotations:
k8s.v1.cni.cncf.io/network-status: |-
[{
"name": "",
"ips": [
"<IP_ADDRESS>"
],
"default": true,
"dns": {}
}]
k8s.v1.cni.cncf.io/networks-status: |-
[{
"name": "",
"ips": [
"<IP_ADDRESS>"
],
"default": true,
"dns": {}
}]
creationTimestamp: "2021-02-19T02:27:28Z"
generateName: shrinkray-athena-controller-svc-6fc76696b5-
labels:
app.kubernetes.io/instance: shrinkray-athena-svc
app.kubernetes.io/name: shrinkray-athena-svc
pod-template-hash: 6fc76696b5
name: shrinkray-athena-controller-svc-6fc76696b5-2k4cm
namespace: shrinkray
ownerReferences:

apiVersion: apps/v1
blockOwnerDeletion: true
controller: true
kind: ReplicaSet
name: shrinkray-athena-controller-svc-6fc76696b5
uid: d55f1f84-b0ec-43d3-9ae7-7105d95532a0
resourceVersion: "33363737"
selfLink: /api/v1/namespaces/shrinkray/pods/shrinkray-athena-controller-svc-6fc76696b5-2k4cm
uid: 3548f985-104d-4f1e-90a9-948431345b54
spec:
containers:
args:

./bin/apiserver
image: docker-remote-athena-cos.artifactorylbj.it.keysight.com/controller:0.0.1-720
imagePullPolicy: IfNotPresent
livenessProbe:
failureThreshold: 3
httpGet:
path: /
port: http
scheme: HTTP
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
name: shrinkray-athena-controller-svc
ports:
containerPort: 8080
name: http
protocol: TCP
readinessProbe:
failureThreshold: 3
httpGet:
path: /
port: http
scheme: HTTP
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
resources: {}
securityContext:
capabilities:
add:

NET_ADMIN
SYS_ADMIN
SYS_RAWIO
NET_RAW
CHOWN
OVERRIDE
DAC_READ_SEARCH
FOWNER
FSETID
CAP_KILL
CAP_SETGID
CAP_SETUID
CAP_LINUX_IMMUTABLE
CAP_NET_BIND_SERVICE
CAP_NET_BROADCAST
CAP_NET_RAW
CAP_IPC_LOCK
CAP_IPC_OWNER
CAP_SYS_MODULE
CAP_SYS_RAWIO
CAP_SYS_CHROOT
CAP_SYS_PTRACE
CAP_SYS_PACCT
CAP_SYS_ADMIN
CAP_SYS_BOOT
CAP_SYS_NICE
CAP_SYS_RESOURCE
CAP_SYS_TIME
CAP_SYS_TTY_CONFIG
CAP_MKNOD
CAP_LEASE
CAP_AUDIT_WRITE
CAP_AUDIT_CONTROL
CAP_SETFCAP
CAP_MAC_OVERRIDE
CAP_MAC_ADMIN
CAP_SYSLOG
CAP_WAKE_ALARM
CAP_BLOCK_SUSPEND
CAP_AUDIT_READ
CAP_PERFMON
CAP_BPF
CAP_CHECKPOINT_RESTORE
privileged: true
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:

mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: shrinkray-athena-svc-token-56bf5
readOnly: true
dnsPolicy: ClusterFirst
enableServiceLinks: true
nodeName: master.kcos
priority: 0
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
serviceAccount: shrinkray-athena-svc
serviceAccountName: shrinkray-athena-svc
terminationGracePeriodSeconds: 30
tolerations:

effect: NoExecute
key: node.kubernetes.io/not-ready
operator: Exists
tolerationSeconds: 300
effect: NoExecute
key: node.kubernetes.io/unreachable
operator: Exists
tolerationSeconds: 300
volumes:
name: shrinkray-athena-svc-token-56bf5
secret:
defaultMode: 420
secretName: shrinkray-athena-svc-token-56bf5
status:
conditions:
lastProbeTime: null
lastTransitionTime: "2021-02-19T02:27:28Z"
status: "True"
type: Initialized
lastProbeTime: null
lastTransitionTime: "2021-02-19T02:27:28Z"
message: 'containers with unready status: [shrinkray-athena-controller-svc]'
reason: ContainersNotReady
status: "False"
type: Ready
lastProbeTime: null
lastTransitionTime: "2021-02-19T02:27:28Z"
message: 'containers with unready status: [shrinkray-athena-controller-svc]'
reason: ContainersNotReady
status: "False"
type: ContainersReady
lastProbeTime: null
lastTransitionTime: "2021-02-19T02:27:28Z"
status: "True"
type: PodScheduled
containerStatuses:
image: docker-remote-athena-cos.artifactorylbj.it.keysight.com/controller:0.0.1-720
imageID: ""
lastState: {}
name: shrinkray-athena-controller-svc
ready: false
restartCount: 0
started: false
state:
waiting:
message: 'Error response from daemon: invalid CapAdd: unknown capability:
"CAP_OVERRIDE"'
reason: CreateContainerError
hostIP: <IP_ADDRESS>
phase: Pending
podIP: <IP_ADDRESS>
podIPs:
ip: <IP_ADDRESS>
qosClass: BestEffort
startTime: "2021-02-19T02:27:28Z"

Other log outputs (if you use multus logging)

On further investigation, removing the long list of capabilities fixes the issue. Helm didn't complain about it, but I noticed it doesn't complain about unknown capabilities. Perhaps that is the issue. A better error statement would be appreciated.

message: 'Error response from daemon: invalid CapAdd: unknown capability:"CAP_OVERRIDE"' seems not to be sent from multus-cni. If multus send error message, the pod should not be created. It might be from container runtime. As k8s.v1.cni.cncf.io/networks-status output, multus seems to finish interface creation and quit successfully and the error message is shonw after multus process. As you know, after CNI plugin Kubernetes do more process to create the pod. I guess that these process causes the error above.
This issue is not multus issue, hence close it.


Connection Refused () with load balancers

This is probably user error so apologies in advance;
Im trying out Cyanite and want to duplicate our current production traffic to it, sending TCP directly to it i have no issues (echo & netcat) however when trying to load balance the TCP over it i get connection refused. I have tried; HAProxy / carbon-c-relay / carbon-relay-ng all to no avail.
My config;
logging:
level: info
console: true
files:
- "/var/log/cyanite/cyanite.log"
inputs:
- type: "carbon"
port: 2013
- type: "pickle"
port: 2014
store:
type: "cassandra-v2"
cluster: "<IP_ADDRESS>"
index:
type: "memory"
api:
port: 8080
engine:
rules:
default:
- "5s:1h"
Am i missing something simple here?
If not...
Id like to scale this over a few cyanite instances as it will have to handle 2M + metrics per min, so if anyone would be kind enough to share a working carbon-relay-ng config i would be very thankful.

cyanite also seems to ignore any parameters in the config;
i changed the ports around to test somethings, and also the bind address from <IP_ADDRESS> to <IP_ADDRESS> as per this config;
logging:
level: info
console: true
files:
\ - "/var/log/cyanite/cyanite.log"
inputs:
- type: "carbon"
port: 2004
host: <IP_ADDRESS>
store:
type: "cassandra-v2"
cluster: "<IP_ADDRESS>"
index:
type: "memory"
api:
port: 8080
engine:
rules:
default:
- "5s:1h"
however looking at netstat, its still bound to 2003/<IP_ADDRESS>, even after ensuring all prev processes were killed.

so further to my port testing;
if i netcat to
localhost = ok
127.0.01 = ok
<IP_ADDRESS> = ok
IP addr = fail
this would explain why the LB cant connect to it, however as mentioned above its ignoring my config to bind to <IP_ADDRESS>,

further to this, none of the arguments under
- input
are taken, however the rest seem to apply.

ok the issue with it not picking up the config was
inputs
should be input
http://cyanite.io/quickstart.html#requirements has the config as inputs and i had copy/pasted that. :)

thanks for spotting the error @gmlwall


volume group is not empty

The template below is mostly useful for bug reports and support questions.
Feel free to remove anything which doesn't apply to you and add more information where it makes sense.
Required information

Distribution: Ubuntu
Distribution version: 16.04.2 LTS
The output of "lxc info" or if that fails:
% lxc info
config:
core.https_address: '[::]'
core.trust_password: true
api_extensions:

storage_zfs_remove_snapshots

container_host_shutdown_timeout

container_syscall_filtering

auth_pki

container_last_used_at

etag

patch

usb_devices

https_allowed_credentials

image_compression_algorithm

directory_manipulation

container_cpu_time

storage_zfs_use_refquota

storage_lvm_mount_options

network

profile_usedby

container_push

container_exec_recording

certificate_update

container_exec_signal_handling

gpu_devices

container_image_properties

migration_progress

id_map

network_firewall_filtering

network_routes

storage

file_delete

file_append

network_dhcp_expiry

storage_lvm_vg_rename

storage_lvm_thinpool_rename

network_vlan

image_create_aliases

container_stateless_copy

container_only_migration

storage_zfs_clone_copy

unix_device_rename

storage_lvm_use_thinpool

storage_rsync_bwlimit

network_vxlan_interface

storage_btrfs_mount_options

entity_description

image_force_refresh

storage_lvm_lv_resizing
api_status: stable
api_version: "1.0"
auth: trusted
public: false
environment:
addresses:

<IP_ADDRESS>:8443
architectures:
x86_64
i686
certificate: |
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----
certificate_fingerprint: ...
driver: lxc
driver_version: 2.0.8
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.4.0-81-generic
server: lxd
server_pid: 8028
server_version: "2.14"
storage: ""
storage_version: ""

Storage backend in use: lvm

After upgrade to 2.14 version, lxd can't create storage pool on lvm:
/usr/bin/lxc storage create lxdpool lvm source=vg0
error: volume group "vg0" is not empty

Is there any way to make this possible?

Can you show vgdisplay vg0?

% sudo vgdisplay vg0
  --- Volume group ---
  VG Name               vg0
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  11
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                5
  Open LV               5
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               892,29 GiB
  PE Size               4,00 MiB
  Total PE              228427
  Alloc PE / Size       2196 / 8,58 GiB
  Free  PE / Size       226231 / 883,71 GiB
  VG UUID               Vj1nXQ-y5A0-22Z1-3aPl-CdLc-SjAL-zEHdxX

% sudo lvs
  LV     VG   Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  home   vg0  -wi-ao---- 976,00m
  root   vg0  -wi-ao---- 976,00m
  swap_1 vg0  -wi-ao---- 976,00m
  usr    vg0  -wi-ao----   1,91g
  var    vg0  -wi-ao----   3,81g

Yeah, so LXD will not use any volume groups that have existing logical volumes in them. This is a safety measure. LXD will assume it has full control over the pool and it might tear it down when you delete the pool via LXD. If you want to use an existing VG you need to give LXD an empty one. This should also be documented in the storage documentation in this repo.

It's bad. Why you don't want use full control of thinpool instead of volume group? For creating new volume group I need additional physical volume. It's very hard to add on already configured server.

If you have a volume group that only has a thinpool in it then you can pass the name of the volume group and the name of the thinpool to LXD and it will use it. It will however, still refuse it if there's any other logical volume besides the thinpool in the volume group.

I'm agree with nnovikov, I'd like to provide a thinpool to lxd, even in group with other logical volumes, but not the whole volume group.

This makes lvm backend useless for me. This is very sad.

So your exact use-case is an already existing volume group with a pre-existing thinpool and some other logical volumes?

I sent a PR that allows you to use an already existing non-empty volume groups iff the requested thinpool does already exist. If it does not exist we'd need to start guessing sizes which is not something we want to do.

Yes, pre-existing thinpool is a good solution. Guessing sizes is not required. I think in this case you must stop creating storage with error message..

What are related lxc command to use existing vg?
LV thinpool has been pre-created.
I try to do with these command, but it fail with confusing message:
sudo lvcreate -v -L 200G --thinpool lxdlvm xcont2-vg
sudo lvs
  LV     VG        Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  lxdlvm xcont2-vg twi-a-tz-- 200.00g             0.00   0.23
  root   xcont2-vg -wi-ao---- 433.70g
  swap_1 xcont2-vg -wi-ao----  31.96g
  zfslxd xcont2-vg -wi-ao---- 200.00g

lxc storage create pool2 lvm lvm.thinpool_name=lxdlvm lvm.vg_name=xcont2-vg
error: LXD already uses volume group "xcont2-vg" for pool "pool2"

@brauner that error looks a bit confusing? :)
@sehari24jam what does "lxc storage list" show you right now?

It looks like the storage driver thinks that LXD already used this volume group so yeah, I'd need to see the output of lxc storage list.

Is there a similar restriction for using zfs?


Replies ping the incorrect user

Kernel: 5.15.11-gentoo-x86_64
libc: sys-libs/glibc-2.34-r4
Go: dev-lang/go-1.17.5
Terminal: st
I didn't use the username/password login, I put my token in discordo.toml
Reproduction:

click a message with the mouse that you want to reply to
press r
The input box will indicate that you are replying to the correct user.
Type a message and press enter
The message is sent as replying to the wrong user.

Also, after doing the reproduction steps once, there is no crash. But if I try the same thing again, discordo crashes.

This is the error I get for the crash:
panic: runtime error: index out of range [-1] [recovered]
	panic: runtime error: index out of range [-1]

goroutine 1 [running]:
github.com/rivo/tview.(*Application).Run.func1()
	github.com/rivo/tview@v0.0.0-20211029090357-1d641bd56588/application.go:243 +0x4d
panic({0x7af9e0, 0xc000318888})
	runtime/panic.go:1038 +0x215
main.onMessageInputFieldInputCapture(0xc00023fc30)
	github.com/ayntgl/discordo/ui.go:295 +0x55f
github.com/rivo/tview.(*Box).WrapInputHandler.func1(0xc000036180, 0xc00023fc70)
	github.com/rivo/tview@v0.0.0-20211029090357-1d641bd56588/box.go:158 +0x3a
github.com/rivo/tview.(*Flex).InputHandler.func1(0xc00023fcb0, 0x6f5adf)
	github.com/rivo/tview@v0.0.0-20211029090357-1d641bd56588/flex.go:237 +0xd9
github.com/rivo/tview.(*Box).WrapInputHandler.func1(0xc0000bbcb0, 0x10)
	github.com/rivo/tview@v0.0.0-20211029090357-1d641bd56588/box.go:161 +0x53
github.com/rivo/tview.(*Flex).InputHandler.func1(0x40e9c7, 0x10)
	github.com/rivo/tview@v0.0.0-20211029090357-1d641bd56588/flex.go:237 +0xd9
github.com/rivo/tview.(*Box).WrapInputHandler.func1(0xc0000bbd40, 0xc00023fdb8)
	github.com/rivo/tview@v0.0.0-20211029090357-1d641bd56588/box.go:161 +0x53
github.com/rivo/tview.(*Application).Run(0xc000202000)
	github.com/rivo/tview@v0.0.0-20211029090357-1d641bd56588/application.go:335 +0x886
main.main()
	github.com/ayntgl/discordo/main.go:102 +0xb94

After further testing, I have concluded that it always replies to the earliest message in the loaded message history.

Now after experimenting a bit, I believe this happens because selecting a message with the mouse fails to set the selectedMessage variable correctly. No matter which message you click, it's always 0. When selecting and replying to messages with hotkeys instead of the mouse, there is no bug.

Replacing the line
m := selectedChannel.Messages[selectedMessage]

with
_, m := util.FindMessageByID(selectedChannel.Messages, messagesTextView.GetHighlights()[0])

in the function onMessageInputFieldInputCapture in ui.go solves the issue. There is probably a preferred way to do this, but this was the way I was able to figure out.

I am currently rewriting Discordo in the rewrite branch, this issue will be fixed when the rewrite branch is merged.


[Event Request] Codeunit 7307 Whse.-Activity-Register - OnBeforeRegisterWhseJnlLine

Hi,
We need to implement additional business logic on registering warehouse journal line.
The following publisher is needed to be added (before registering warehouse journal line):
Codeunit 7307 Whse.-Activity-Register - Function RegisterWhseJnlLine() -
OnBeforeRegisterWhseJnlLine(WhseActivLine : Record "Warehouse Activity Line";VAR WhseJnlLine : Record "Warehouse Journal Line")

@JesperSchulz ,
Any news about this issue?

The mentioned publisher is already added.

The request will be closed.


Timeline recording doesn't work

I love Toggl and use it daily to track my projects. I'd also love to track my application usage, but I haven't been able to get timeline recording working.
I've had "Record timeline" selected on both my Windows and MacOS desktop apps for the past month. I've restarted the app and machines multiple times, but haven't seen any timeline data show up on toggl.com/app/timer
Regular project time recording has been working and syncing fine.

Hi! Can you email us at support(at)toggl(dot)com with the emailed associated with your Toggl account? We can finish the Timeline setup process there.

Issue should now be fixed, responded in email :)