Wrong bash terminal loaded on startup

When (and only when) I start VSCode a bash terminal is loaded, that is not the default one, nor existent in the terminal profiles. If I open my default bash terminal after startup, everything works out fine.
I use the following setup

VSCode (v.1.66.2) on Windows 10 connected via the "Remote - SSH" Plugin to an Linux Server
My bash has a specific setup defined in .bash_profile -> "args":["-l"] ensures the setup is called

Here´s settings.json:
{
  "terminal.integrated.profiles.linux": {
      "bash": {
        "path": "/usr/bin/bash",
        "icon": "terminal-bash",
        "args": [
          "-l"
        ]
      },
     // ...
    },
    "r.rpath.linux": "/opt/R/4.1.1/lib64/R/bin/R",
    "terminal.integrated.customGlyphs": false,
    "terminal.integrated.defaultProfile.linux": "bash",
    // ...
}

On startup I see this Terminal (see icon & bash appearance):

When opening my default bash afterwards I get this:

icon as defined in settings.json
my bash setup from .bash_profile is loaded correctly

A weird thing I´ve observed are the Integrated > Default Profile: Linux settings. In settings.json bash is only defined once - here I see two options.

it seems bash (2) is loaded at startup as "args":["-l"] is missing there...

<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can

/duplicate #142425

It works for terminal #2 and beyond, correct?

@meganrogge thanks for pointing out the existing issue 👏. Seems to be the same problem here - wasn´t able to find it among the few other ones 😉.


stdenv/linux: apply default compiler errors from GCC 14

Let’s make sure both OSes get an adequate amount of compiler fun this cycle! This is a version of alyssais’s https://github.com/NixOS/nixpkgs/pull/344239 that applies to the Linux standard environment’s compiler wrapping rather than the versioned GCC packages themselves.
This is purely a transition mechanism to help us prepare for the GCC 14 update while GCC 14 itself is not yet ready for wide deployment; it will be reverted before 25.05, whether because it becomes obsolete thanks to an upgrade to GCC 14 or because we give up on GCC 14 and deicde to stick with GCC 13 with the vanilla flags.
This approach means that the standard gcc will be wrapped correctly, unlike with the previous PR, achieving the primary goal of the change, but gcc13 will remain as it was before. Currently, I believe the difference between the two is just bootstrapping stage stuff; it’s a bit weird to me to diverge, especially since there is a definition of gcc in all-packages.nix that looks like it ought to make them equivalent, but it may have the nice property that we can pin especially stubborn packages to GCC 13 without them getting the errors (though I am not sure if this is actually true or not, since I’m not sure how gcc13Stdenv actually works).
One downside is that this only applies to Linux, but since this is essentially meant to be a forcing function to get us to deal with the errors early, that seems fine.
Source: https://gcc.gnu.org/gcc-14/porting_to.html
I’ve bootstrapped an earlier version of this but will compile again with the current commits tomorrow.
cc @trofi for review of my sloppily‐modified GCC patches :) I hope Init(-1) rather than Init(0) is correct!

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Two problems:
Firstly, It seems like this breaks the gcc13 build itself, so we’d have to backport patches for that too, or disable these warnings when compiling GCC. Thankfully it seems like just a couple of declarations in one file, so it probably wouldn’t be too invasive. I’m not sure what’s going on here, really, since we ought to have run into it when trying the GCC 14 bump originally.
Secondly, since I’m not sure if we have a flags file specifically for C, all C++ compilation gives these warnings:
cc1plus: warning: '-Werror=' argument '-Werror=implicit-int' is not valid for C++
cc1plus: warning: '-Werror=' argument '-Werror=implicit-function-declaration' is not valid for C++
cc1plus: warning: '-Werror=' argument '-Werror=declaration-missing-parameter-type' is not valid for C++
cc1plus: warning: '-Werror=' argument '-Werror=return-mismatch' is not valid for C++
cc1plus: warning: '-Werror=' argument '-Werror=int-conversion' is not valid for C++
cc1plus: warning: '-Werror=' argument '-Werror=incompatible-pointer-types' is not valid for C++

This seems tricky to fix if we don’t want to suppress such warnings in any case where vanilla GCC 13 would be producing them.
@alyssais I’m starting to lean towards just updating to the GCC 14 release branch HEAD instead. It seems like all the known AArch64 issues we ran into were already fixed there weeks ago when we ran into them, and Arch (and IIRC another distro?) are shipping it so it seems like it shouldn’t be too bad to do on unstable. What do you think?

SGTM. We can always roll back.

Closing in favour of https://github.com/NixOS/nixpkgs/pull/356812.


doc(BasicTutorial): Broken link

fixes a broken link in the basic tutorial and closes #1578

Thanks!


DBZ-5477: Remove SQL Server connector SourceTimestampMode

See DBZ-5477.

The SqlServerConnectorIT#useLongTableNamesForColumnMapper failure looks irrelevant. The test passes locally.

Applied to main (=2.0).


Conjur Jenkins Credential Provider using JWT

Changes to policy and setup to allow Jenkins Conjur plugin to work using JWT authenticator.

Hi Jason,
i used the policies which you provided, it is showing the error, invalid claim path.
jenkins_name: test-pipeline (i have created)

@ManithejaCyberark, test-pipeline needs to be both the Conjur Host id as well as the job. Also, please try recreating Conjur after you've updated the Jenkins job.

As Jenkins state is not captured here, it's going to be quit challenging to offer guidance without visibility into your Jenkins setup. Please include screen shots of your pipeline setup (and ideally, JWT token).

Yes Jason Here's the jwt token:

Conjur Appliance set up:

Jwt Authenticator:


PR: Autocomplete only left part of selected word.

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[x] Added unit test(s) covering the changes (if testable)

[ ] Included a screenshot or animation (if affecting the UI, see Licecap)

Sometimes I want to autocomplete a word while I have something on the right of it:
import math

value = angle / 2

In this example, I want to take the sin of this angle:
import math

value = math.s|angle / 2

If I press <tab>, nothing will happen. But I want  math.sin|angle.
Issue(s) Resolved

Fixes #
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

This is a very good addition, thanks!
@andfoy, please review this one.

@impact27 Thanks for this addition, from my side, I don't see any problems

Thanks @andfoy!


doppler: 3.19.0 -> 3.21.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dopplerhq/cli/releases.
meta.description for doppler is: "The official CLI for interacting with your Doppler Enclave secrets and configuation"
meta.homepage for doppler is: "https://doppler.com"
meta.changelog for doppler is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.21.0 with grep in /nix/store/d3xl6lfg7kknvn3f7xaij2vp7v9f2r8a-doppler-3.21.0

directory tree listing: https://gist.github.com/42f9281f89e9121c9cd6964df60a0bc0

du listing: https://gist.github.com/7bc0d50a1ba1936e73b072206f9608e0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
doppler

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d3xl6lfg7kknvn3f7xaij2vp7v9f2r8a-doppler-3.21.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A doppler https://github.com/r-ryantm/nixpkgs/archive/35d5f2ebed996d8d3b3bedb7b4dfebcbab87f95a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d3xl6lfg7kknvn3f7xaij2vp7v9f2r8a-doppler-3.21.0
ls -la /nix/store/d3xl6lfg7kknvn3f7xaij2vp7v9f2r8a-doppler-3.21.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

doppler

Maintainer pings
cc @lucperkins @kalbasit for testing.

3.21.0
42f57cb Support downloading secrets in 'env-no-quotes' format

3.20.2
f2813e5 Fix keyring access panicking on certain WSL environments

3.20.1
fab88cc Add --forward-signals flag to always forward to subprocess
c13efb0 Forward signals to 'run' process when no TTY is allocated

3.20.0
879ca93 Ignore repo config when project/config are already specified
1336801 Stop publishing node, ruby, and python docker images
6501884 Support downloading secrets in docker-specific format

3.21.0
42f57cb Support downloading secrets in 'env-no-quotes' format

3.20.2
f2813e5 Fix keyring access panicking on certain WSL environments

3.20.1
fab88cc Add --forward-signals flag to always forward to subprocess
c13efb0 Forward signals to 'run' process when no TTY is allocated

3.20.0
879ca93 Ignore repo config when project/config are already specified
1336801 Stop publishing node, ruby, and python docker images
6501884 Support downloading secrets in docker-specific format


swift-api-checker: allow the script to take additional flags to pass down to the executable

@swift-ci please smoke test

@swift-ci please smoke test


Modified newtons method

My proposed solution which resolves #1067.
I added an option to Newton Minimizer which forces the Hessian to be positive definite by reversing negative eigenvalues. This method is described in
Philip E. Gill, Walter Murray, and Margaret H. Wright, Practical Optimization, 1981, 107–8.
I also added a unit test, FindMinimum_SixHumpCamel_IndefiniteHessian(), to demonstrate the benefit of this modification. If the optional argument is changed to HessianModifiers.None then the test fails.
Please see the issue for further illustration of the use case.
I made the optional argument an enum because this method of forcing positive definiteness can be improved upon in terms of efficiency and this gives some future developer the hooks to be able to do so.
Regards,
Mikhail

@cdrnet, Would it be possible to get this pull request reviewed?

@jvangael, @jkalias, @JohanLarsson, I think you are also listed as member of the Math.Net team. Would any of you be willing to consider this pull request?

@strMikhailPotapenko I would be more than happy to. The problem is that I can only merge PRs for the MathNet.Spatial project, for the Numerics only @cdrnet has the relevant rights to.

@jkalias Ah I didn't know that, sorry about that and thank you for the response.
Just looking at open issues and pull requests it does seem like there isn't a lot of activity with this repo, which is too bad because I have been using this library quite often lately and have been pretty satisfied with it. Do you happen to have any information on the plans of @cdrnet as far as actively maintaining this repo or any way to request that information from him?

@strMikhailPotapenko nothing to be sorry about :)
I have no information on whether/when @cdrnet will continue to actively maintain this repo. On the other hand, it's an open source project, so there is no obligation to do so, and rightfully so.

@jkalias Very true!


Drawn status item

Draw the status item in code. Todo: invert colours for dark menu bar setting

Oh, it doesn't look exactly like the original - feel free to change the font to something more funky / to your taste

Thanks a lot for the assistance so far, really appreciate it.
Just got around to testing this and it works very nicely! I'll have a play around with the styling, but looks great so far.


two-bucket:  add new complexity bonus test case

this will force the reader to an optimal solution

Sorry, without any context I've no idea what problem this PR is trying to solve. Is it intended to eliminate a solution which passes the existing test cases, but is pathologically non-performant? If so, what?

@bitfield  I think I can try to answer then, with the existing set of test cases even using a brute force approach or using a solution with exponential complexity can give a solution in a fraction of a second, the test I have proposed can be solved by a retail computer in around a second in case the solution used have O(mn) complexity where m is the size of the first bucket and n the size of the second bucket
solution proposed ( looks more performant than the example one )
O(nm) using dynamic programming
https://exercism.io/tracks/go/exercises/two-bucket/solutions/af03104f53464c14b9e7f97a540f5887

Forgive me for asking the obvious question, but if even a brute-force solution gives the correct answer in a fraction of a second, then what's the problem with a brute-force solution?

The point is, how can the reader be pushed to optimize the code of a not monitored exercise if any complexity solution make him feel he/or she (likely a male, gender gap its still there) like he/she have solved it?

It sounds like what you're saying is that without additional tests, it's possible to solve this exercise using an algorithm which is of sub-optimal complexity, and thus wouldn't scale to more demanding test cases (this is what I meant by 'pathologically non-performant' in my previous comment). Is that right?
An example from another exercise would be implementing 'Difference of Squares' with loops. Compared to using a formula, the performance is egregiously bad. An analogous test case for that exercise would be very large N inputs.
Assuming I'm understanding what this is about, how does the proposed test case solve this problem? I mean, if it takes a long time to run the tests, but they pass, how does the student know that their solution is unacceptable? And if the tests time out, how does the student know that their inefficient algorithm is the cause?

answering the last question, we have already set the expectations in students to have their test solved in a few seconds on the average computer, we can add a note in the problem question that if the test execution it's taking more than few seconds they have to think more carefully at the complexity of it.
This expectation comes from the actual habit we have shown them with all the other tests, I thought to suggest complexity checks was an easier battle

The reason I'm asking such hard questions is not because I think it's a bad idea to encourage students towards efficient solutions. I'm completely in favour of that. What I'm not sure about is whether test cases are necessarily the best way to achieve it.
If we had a test that would fail an inefficient solution with a message like this:
Looks like your solution would eventually pass this test, but it's not as efficient as it could be. Would you like to explore an alternative solution which scales much more effectively to larger inputs?

that would be ideal. Unfortunately, it's really hard to write such tests. The best way I know of to guide students down this road is with mentor feedback. I could give you examples from practically every exercise on the core track of solutions which pass the tests, but are nevertheless far from optimal, and if I could have written test cases which would make them so, I certainly would have!
My suspicion, based on experience, is that if the tests take a long time to run, students will either simply ignore this fact, or say that the tests appear to be broken. So do you think there is a way to detect an inefficient solution at the test level and issue a suitably helpful message?

I am closing all PRs that are over a year old. Please reopen if you are still working on this.


Add surface+related concepts fix #1074

Summary of the discussion
This is a partial replacement of PR #1209 . Changes done in #1209 where cherry-picked and selectively added.
The other parts will be addressed in other PRs whichs numbers will be listed here as soon as they are available.
Type of change (see CHANGELOG.md)
Added

class surface
class solar radiation receiving surface
class tangential proper part

Workflow checklist
Automation
⚠: Related issues will be closed manually as soon as all PRs are done.
PR-Assignee

[x] An agreement has been reached
[x] 🐙 Add yourself as Assignee
[x] 🐙 Create a draft pull request
[x] 📝 Update the CHANGELOG.md
[x] 📙 Add # to term tracker item
[x] 🐙 All unit tests pass
[x] 🐙 Publish pull request
[x] 🐙 Add someone or a group (oeo-dev) as Reviewer

PR-Reviewer

[ ] 📙 Class name fits the concept
[ ] 📙 The classification according to the BFO is correct
[ ] 📙 Axioms have been added and reflect the definition
[ ] 📙 Spelling and grammar in the definition text are correct
[ ] 📙 All changes are in the correct OEO module
[ ] 📙 Update of changelog has been done
[ ] 📙 Correct entries in term tracker item
[ ] 🐙 Provide feedback and show sufficient appreciation for the work done

PR-Assignee

[ ] 🐙 Show recognition for the review performed
[ ] 🐙 Merge pull request
[ ] 🐙 Delete branch
[ ] 🐙 Close issue

Just to understand: This PR implies that #1209 will finally be closed without merging, right?

@l-emele I requested you as you were the original reviewer.
@stap-m I requested you as you can check whether the 3 classes which I cherry-picked reflect the originally intended changes.
⚠: The axioms added in the adjacent commits of the original PR will be covered in a differnet follow-up PR.
I did not overlooked them ;)

Just to understand: This PR implies that https://github.com/OpenEnergyPlatform/ontology/pull/1209 will finally be closed without merging, right?

Yes, that's right. I'm going to comment on that PR, too, and note this down.
I'll take care of the adjacent commits now, so please do not delete the branch yet as I need it for cherry-picking :)

Just noticed that the changes are listed in wrong CHANGELOG.md-section.
Will fix it.

I merged this that we can review now the other PR


refactor: reorganize instance metadata patch procedure

Closes #2207

/test limit=local

this PR poses a risk and should be triple checked

Huh, merge conflict because of a recent ticket

test: replace metadata E2E test with a unit test (#2214)
commit e146fd7954e4d8c48be9d7981defc3bcc0585071

which added the fake Kubernetes reconciler. This is valuable and we should not lose it.
Will handle the conflict with more time or send back to Armando

/test

/ok-to-merge


Now webpack 2 is out of beta status! Could happypack official support for it?

I'm looking forward to，thank you!

I've just read the release notes but I still have to study the source code changes.
From what I gathered, this section regarding "complex options" may not be supported by happypack since we can't distribute cyclic JS objects across processes:

webpack 1 only support JSON.stringify-able options for loaders. webpack 2 now supports any JS object as loader options.

Other than that, I'll be looking at this over the weekend.

So? how was your weekend?:)

Rather busy actually!! :laughing:
So it seems that making happypack accept the loader options from the new options option as well as query makes it work for the babel loader. I hit other issues related to CSS (less-loader and extract-text v2) which I couldn't fix yet. The fact that my main projects are not using webpack2 yet isn't helping so maybe you can help by providing example repositories with broken things.
I can push up an RC with that options fix.

Looking forward to help beta test this @amireh

I'm planning to work with an engineer from Canvas LMS to get happypack to work with their webpack 2 build today, that should hopefully move this forward and we'll be seeing a PR in the coming few days.

Amazing @amireh! We're running webpack + react + typescript and our builds are 2,5 minutes long. It's hurtful. We have about 1200 modules)

That's nothing ;)
We are at around 2.5k modules, 4.5 minutes (started at about 9 and after tones of tweaks and optimisation we got it at around 4.5).

Wow @phaistonian ... That's crippling,

So, just as an update, we didn't come across any issue beyond https://github.com/amireh/happypack/commit/05225b58f36bffcc61bcc657badb26320b66b5be to get happypack working with webpack2 in a build that uses babel-loader, handlebars-loader, coffee-loader, and a bunch of home-grown ones specific to Canvas. Hence, no PR mentioned earlier.
I will be making a release soon that incorporates that patch though.

That's awesome @amireh.
ETA for the new release ?

That's so awesome @amireh!

@amireh Great! Looking forward to the release.

Version 3.0.3 can be found now on NPM which incorporates the mentioned change along with another webpack2 related fix so I'll be closing this issue now.
If you guys come across other webpack2 related problems, please report with concrete details.

@amireh I have already integrated it with development and production - everything works correct, thank you!

Thank you @amireh  :)


API on unix domain socket

As i understand, python wrapper communicate with webkot over tcp. Is it possible to use unix socket for this? So we not busy port, and it can be usefull with multiple instances

The problem here is that this would prevent webkit-server from running on Windows. I like the idea though, this is something I have considered as well.

I think it can be optional, or for example default on unix (on win default can be random open port like in phantomjs webdriver)


Have a default config file.

We should have a default config file so that the people that want to contribute don't have to constantly switch between their editor/IDE to discord just to get the id's of the channels or roles. The information in the config file would be accessible across the entire project. The config file could either be json or yaml. We would initialize the information stored in the config in constants.py, and we would import those information across the project.

Well this is just a idea, when the bot starts in a particular server it will create a config.json or config.py file in the root directory containing the emojis and its ids, the roles and its ids and same for the channels. And we could just copy paste these in our python code.

What do you mean?
The bot should be configured in such a way that it would fulfill the needs of the Gurkult server.

we could have the file generate when the bot is run, or should we add it manually?

Why would we want to generate a file?
We should just have a default config file on the repo, which would be initialized in constants.py.

To avoid the work of getting all ids of roles/emojis/channels

we could have the file generate when the bot is run(dynamic), or should we add it to the repo(static)?

Dynamically when bot is run.

Why though?
The bot is configured for the Gurkult server and the default-config would just be the one in the repo.
The bot would interact with config.json

That could also be done...
We have 1 default json config which updates when bot is run :+1:
(I was talking of generation, since ppl might use this in other servers)

Yeah just like vyvy said

Are u saying that we create such a configuration that when people would run the bot in their servers that it would get the required channel and role ids and replace the once in config-default.json.
And for the bot in the Gurkult server, the config file would be constantly be updated.

Yes

I guess we can do that. Let's see what others have to say.'

I like the idea of having some default config. Maybe we could include a file that defaults to the bot test server, so it's easy to get started with contributing.
Regarding scalability, I think we should have a setup wizard command for servers in the future, but that's nothing we should think about right now imo. For now, I think a config file would be fine, that you duplicate (and change the name of to something predefined, like constants.py) and put your own values in. When the bot start, it first looks for constants.py and if it doesn't find it, it defaults to default-constants.py.

I like the idea of having some default config. Maybe we could include a file that defaults to the bot test server, so it's easy to get started with contributing.
Regarding scalability, I think we should have a setup wizard command for servers in the future, but that's nothing we should think about right now imo. For now, I think a config file would be fine, that you duplicate (and change the name of to something predefined, like constants.py) and put your own values in. When the bot start, it first looks for constants.py and if it doesn't find it, it defaults to default-constants.py.

Ye, but we could also make it so that they wouldn't have to go through the hassle of getting the ids of channels and roles.
The bot could just get it for them and create the config.yaml or config.json file. This should also only work on servers that have the same channels and roles as the test server, and for the actual bot we should have a config file that would be updated  when some changes made in the server, an example of this would be a channel being deleted.
We wouldn't want things in the config file that take up unnecessary space.

Ye, but we could also make it so that they wouldn't have to go through the hassle of getting the ids of channels and roles.
The bot could just get it for them and create the config.yaml or config.json file. This should also only work on servers that have the same channels and roles as the test server, and for the actual bot we should have a config file that would be updated  when some changes made in the server, an example of this would be a channel being deleted.
We wouldn't want things in the config file that take up unnecessary space.

That would require having the exact same channel names?

That would require having the exact same channel names?

Yes it would as it would indicate that they are configuring the bot to contribute to Gurkult.

Yes it would as it would indicate that they are configuring the bot to contribute to Gurkult.

Why wouldn't they just join the server and the test server? If they really want to do it on their own, they could possibly just enter the IDs imo.

Why wouldn't they just join the server and the test server? If they really want to do it on their own, they could possibly just enter the IDs imo.

By having this, the people that don't want to test in our test server, wouldn't have to go through the hassle of getting the ids of all the channels and roles.
I mean not everyone would want to test in the test server.

By having this, the people that don't want to test in our test server, wouldn't have to go through the hassle of getting the ids of all the channels and roles.
I mean not everyone would want to test in the test server.

perhaps we could make a setup.py file, to make the config.json file(it can be run, when using the bot for the first time)
imho, keeping it customisable according to contributors/users(since, this is oss), for testing in their own servers, if they want..
Moreover, if we don't make a config file or something like that, we might have to add extra guidelines in the readme on how to change the values etc...

perhaps we could make a setup.py file, to make the config.json file(it can be run, when using the bot for the first time)
imho, keeping it customisable according to contributors/users(since, this is oss), for testing in their own servers, if they want..
Moreover, if we don't make a config file or something like that, we might have to add extra guidelines in the readme on how to change the values etc...

Well that is something I was working in, and it is a time taking process and Python Discord is already building a smart config, so either we what till. March for that or you gives me sometime to come with a way to do that.

Well that is something I was working in, and it is a time taking process and Python Discord is already building a smart config, so either we what till. March for that or you gives me sometime to come with a way to do that.

Well that is something I was working in, and it is a time taking process and Python Discord is already building a smart config, so either we what till. March for that or you gives me sometime to come with a way to do that.

Well that is something I was working in, and it is a time taking process and Python Discord is already building a smart config, so either we what till. March for that or you gives me sometime to come with a way to do that.

so either we what till. March for that
Why would we have to wait?
We could just make a config that suits our needs rather.
The only thing that this config is supposed to do is store the ids of roles and channels in config.(yaml or json).

so either we what till. March for that
Why would we have to wait?
We could just make a config that suits our needs rather.
The only thing that this config is supposed to do is store the ids of roles and channels in config.(yaml or json).

perhaps we could make a setup.py file, to make the config.json file(it can be run, when using the bot for the first time)
imho, keeping it customisable according to contributors/users(since, this is oss), for testing in their own servers, if they want..
Moreover, if we don't make a config file or something like that, we might have to add extra guidelines in the readme on how to change the values etc...

I like the general idea but I'm unsure as to whether we should wait for Smart Config to be developed or make something of our own in the mean time.
Just a small note, we shouldn't call it setup.py since that's meant for metadata about the project and for pip to manage dependencies, etc. . It's never directly run, too.
We can make a .py script of an appropriate name in /scripts. I have consulted with people and running the script with pipenv seems to be a clean option.

perhaps we could make a setup.py file, to make the config.json file(it can be run, when using the bot for the first time)
imho, keeping it customisable according to contributors/users(since, this is oss), for testing in their own servers, if they want..
Moreover, if we don't make a config file or something like that, we might have to add extra guidelines in the readme on how to change the values etc...

I like the general idea but I'm unsure as to whether we should wait for Smart Config to be developed or make something of our own in the mean time.
Just a small note, we shouldn't call it setup.py since that's meant for metadata about the project and for pip to manage dependencies, etc. . It's never directly run, too.
We can make a .py script of an appropriate name in /scripts. I have consulted with people and running the script with pipenv seems to be a clean option.

Right, but that's not the purpose of this issue though.
For this issue, what I am suggesting is that

Have a default-config.(JSON or YAML) file.
The bot will get the ids of roles and channels and create a new file called config. (JSON or YAML) with the all the retrieved.
When there are changes made in the server such as creating a role, channel, etc, or deleting it, the bot would update the config. (JSON or YAML) file, which wouldn't be on the repo. -And for constants.py we should use collections.namedupleto access the information inconfig. (JSON or YAML)`.

Right, but that's not the purpose of this issue though.
For this issue, what I am suggesting is that

Have a default-config.(JSON or YAML) file.
The bot will get the ids of roles and channels and create a new file called config. (JSON or YAML) with the all the retrieved.
When there are changes made in the server such as creating a role, channel, etc, or deleting it, the bot would update the config. (JSON or YAML) file, which wouldn't be on the repo. -And for constants.py we should use collections.namedupleto access the information inconfig. (JSON or YAML)`.

For testing purposes, this could possibly work great. We could probably make sure that the user just runs it through enabling a DEV flag or something. This means we could add something to automatically create categories and roles that don't yet exist, through checking which ones already exist in the server. This would allow the bot to update the server to match the default config easily, on first startup and after pulling new versions, which would be quite fantastic for a testing server.

For testing purposes, this could possibly work great. We could probably make sure that the user just runs it through enabling a DEV flag or something. This means we could add something to automatically create categories and roles that don't yet exist, through checking which ones already exist in the server. This would allow the bot to update the server to match the default config easily, on first startup and after pulling new versions, which would be quite fantastic for a testing server.

I think you misunderstood my third bullet point.
What I meant was when the bot would be running on the server, we wouldn't want to have roles and channels that are already deleted or have been edited, so we should listen for those events through the bot and the bot would change the information in config. (JSON or YAML).

I think you misunderstood my third bullet point.
What I meant was when the bot would be running on the server, we wouldn't want to have roles and channels that are already deleted or have been edited, so we should listen for those events through the bot and the bot would change the information in config. (JSON or YAML).

So, the user could have a test server that doesn't have all of the required roles?

So, the user could have a test server that doesn't have all of the required roles?

Well we could create the roles that are missing as u stated.

Well we could create the roles that are missing as u stated.

This is what I'm proposing that the bot does when the script is run (could be configured to run automatically on every git pull)

Check what roles and channels exist
Update IDs in config file to match the ones on the server
Create the ones that don't exist and store IDs

The user could also choose to run it manually whenever they think it's needed, using something like pipenv run sync-ids.

This is what I'm proposing that the bot does when the script is run (could be configured to run automatically on every git pull)

Check what roles and channels exist
Update IDs in config file to match the ones on the server
Create the ones that don't exist and store IDs

The user could also choose to run it manually whenever they think it's needed, using something like pipenv run sync-ids.

Why would we want to update it only when ran?
Why not immediately after the changes made?

Why would we want to update it only when ran?
Why not immediately after the changes made?

Well, here are the times that I think we should run it:

On git pull, if configured to do so
When running it directly through a command

Do we also want it to run every time the bot starts? Nah, that's probably overkill, or what do you think?

Well, here are the times that I think we should run it:

On git pull, if configured to do so
When running it directly through a command

Do we also want it to run every time the bot starts? Nah, that's probably overkill, or what do you think?

Run what may I ask

Run what may I ask

The script that updates the config file to match the server.

The script that updates the config file to match the server.

It wouldn't be a script, it would just be a cog that listens for events in the server and update the config file accordingly.

It wouldn't be a script, it would just be a cog that listens for events in the server and update the config file accordingly.

So here is the plan.

We would have a syncer.py in the backends folder which would sync the changes made in the server to the config file.

We would have a check_required_keys function in our constaints.py file which would check if the required keys exist or not.

We would use the check_required_keys function in the syncer.py file to check if the server has the needed roles and channels. When there are changes made in the server we would check if those changes were made to the required keys and if they were then we would try to recreate those keys if we can't then we would dm the server owner asking them to create the required roles and channels.

So here is the plan.

We would have a syncer.py in the backends folder which would sync the changes made in the server to the config file.

We would have a check_required_keys function in our constaints.py file which would check if the required keys exist or not.

We would use the check_required_keys function in the syncer.py file to check if the server has the needed roles and channels. When there are changes made in the server we would check if those changes were made to the required keys and if they were then we would try to recreate those keys if we can't then we would dm the server owner asking them to create the required roles and channels.

Why do you want a sync that goes the SERVER => CONFIG direction? If people create a bunch of roles, they should not be added automatically to the config files. Instead, the user should add it manually, if they make changes.
Especially in test servers, there are often sudo or testers roles, made to let people test freely on the server. If all roles were added to the config automatically, this would be a total mess.

Why do you want a sync that goes the SERVER => CONFIG direction? If people create a bunch of roles, they should not be added automatically to the config files. Instead, the user should add it manually, if they make changes.
Especially in test servers, there are often sudo or testers roles, made to let people test freely on the server. If all roles were added to the config automatically, this would be a total mess.

Ye that does make sense.
So..., we would have a script that creates a config file containing all the required information in the server, if some of the required information is not present in the server then the bot would create it, and add it to the config file?
Also, when would the bot check if the roles and ids exist or they have been deleted?

Ye that does make sense.
So..., we would have a script that creates a config file containing all the required information in the server, if some of the required information is not present in the server then the bot would create it, and add it to the config file?
Also, when would the bot check if the roles and ids exist or they have been deleted?

Basically, yeah. These are the two files that I think should exist, where both should have either a JSON or YAML format. The names can be changed.

server-config — auto-generated config file with the correct IDs from the server.
server-config-list — the parts of the server config that should be present in the server-config file. This is a bit like "requirements.txt", where we list the things that should exist in the server, including channels, roles, Webhooks and whatever else we want to include. All items in this file should have an attribute for if it's required or not. For example, you may not require an advent of code channel, while you require a devlog

In order to create server-config, we need a script. This would be a python script that has a few flags available, though these could be added as we go along, if we want to. We should also be able to set this up to run on at least startup, pulls and to be run manually from the command line:

auto-config.py

This script would be a bit more complex, but the goal of it is to have valid IDs in server-config, synced from the names of the channels that server-config-list specifies should exist.

Basically, yeah. These are the two files that I think should exist, where both should have either a JSON or YAML format. The names can be changed.

server-config — auto-generated config file with the correct IDs from the server.
server-config-list — the parts of the server config that should be present in the server-config file. This is a bit like "requirements.txt", where we list the things that should exist in the server, including channels, roles, Webhooks and whatever else we want to include. All items in this file should have an attribute for if it's required or not. For example, you may not require an advent of code channel, while you require a devlog

In order to create server-config, we need a script. This would be a python script that has a few flags available, though these could be added as we go along, if we want to. We should also be able to set this up to run on at least startup, pulls and to be run manually from the command line:

auto-config.py

This script would be a bit more complex, but the goal of it is to have valid IDs in server-config, synced from the names of the channels that server-config-list specifies should exist.

Sounds good. Now we need to agree on the type of file that needs to be used.

Sounds good. Now we need to agree on the type of file that needs to be used.


how to get one page data list and total count from database with knex.js?

Environment
Knex version: 0.15.2
Database + version: pgsql 10.1
OS: windows
Tried the following:
var model = knex.table('users').where('status',1).where('online', 1)
var totalCount = await model.count();
var data = await model.offset(0).limit(10).select()
return {
    totalCount: totalCount[0]['count']
    data: data
}

but get { "totalCount": "11", "data": [ { "count": "11" } ] }
how can I get dataList without write where twice?
stackoverflow link:
https://stackoverflow.com/questions/52775863/how-to-get-one-page-data-list-and-total-count-from-database-with-knex-js
thank you :)

The problem here is that you're reusing the builder for two different type of queries; Count & Select.
This is the builder:
var model = knex.table('users').where('status',1).where('online', 1)
This makes the builder a 'Count' query:
var totalCount = await model.count();
This only appends an offset and limit to the same builder from totalCount:
var data = await model.offset(0).limit(10).select()
What you need to do is not use the same builder twice. There are plenty of ways to go around this. Some examples:
var model = knex.table('users').where('status',1).where('online', 1)
var totalCount = await model.clone().count();
var data = await model.clone().offset(0).limit(10).select()
return {
    totalCount: totalCount[0]['count']
    data: data
}

var getModel = () => knex.table('users').where('status',1).where('online', 1)
var totalCount = await getModel().count();
var data = await getModel().offset(0).limit(10).select()
return {
    totalCount: totalCount[0]['count']
    data: data
}

And more...

@wubzz thank you !


Timestamp issues

Fix issues with native timestamps, to reduce log cruft in CI

Closes https://github.com/inventree/InvenTree/issues/6834

This has significantly reduced the output of the CI logs

Very nice!


Update and cleanup

Update rust deps
Cleanup rust code to avoid unsafe code and additional overhead

bench before
base-x-native (master) ✗ node benchmark/

Seed: aabe04df97f2d26055ced6ba8ca35e75
  2 tests completed.

  rust_encode x 98,869 ops/sec ±1.28% (9 runs sampled)
  js_encode   x 96,920 ops/sec ±1.95% (8 runs sampled)

  2 tests completed.

  js_decode   x 217,634 ops/sec ±0.92% (8 runs sampled)
  rust_decode x 106,053 ops/sec ±11.27% (9 runs sampled)

after
base-x-native (update-deps) ✔ node benchmark

Seed: db76c819a61743b64cb4260afc56552d
  2 tests completed.

  rust_encode x 75,889 ops/sec ±1.82% (9 runs sampled)
  js_encode   x 58,472 ops/sec ±3.17% (9 runs sampled)

  2 tests completed.

  js_decode   x  78,575 ops/sec ±26.41% (8 runs sampled)
  rust_decode x 122,758 ops/sec ±3.01% (9 runs sampled)

Thanks, this is awesome!


Affix doesn't recheck position on touchmove

affix.js works on tablets but only when scroll ends.
Please add touchmove .on('touchmove.bs.affix.data-api', $.proxy(this.checkPosition, this)) around line 20

It happends on one of the latest apple tablet, I've tried it with Chrome and Safari. And it might be a bug on their side but I guess a touchmove isn't that bad to add as a fallback for scroll.

Bootstrap 3 is no longer being officially developed or supported.
All work has moved onto our next major release, v4. As such, this issue or pull request is being closed as a "won't fix." For additional help and support, we recommend utilizing our community resources. Thanks for your understanding, and see you on the other side of v4!
<3,
@mdo and team


how do you train the DB or your face recognition system

how do you train the DB or your face recognition system to know the names for images as i would like to add some more myself

Have you looked at the docs and examples yet?

In code, it's a simple as this: https://github.com/ageitgey/face_recognition/blob/master/examples/facerec_from_webcam_faster.py#L17-L32
If you are using the command-line tool instead of writing code, then you just pass in a folder containing one image of each known person.


Movement commands not being processed

Hey, I've been developing with the ar-drone library for the past 10 months and got an amazing application for my dissertation at university. One week before the presentation and the software is behaving odd.
It started a few days ago when I noticed the drone was not responding to the joystick controls. I've checked my framework and the signals are definitely getting to the drone. Take off, land, ftrim and other functions seem to be fine but when I try send a directional command, it is not responsive.
A basic test would be to connect to the drone, take off, attempt movement commands and then land the drone before it decided to launch off into the air. The demo data being returned shows that the controlState has the following changes during test:
controlState: CTRL_LANDED, flyState: FLYING_OK
controlState: CTRL_TRANS_GOTOFIX, flyState: FLYING_OK
controlState: CTRL_HOVERING, flyState: FLYING_COMBINED_YAW
controlState: CTRL_FLYING, flyState: FLYING_ALT_OUT_ZONE
controlState: CTRL_TRANS_LOOPING, flyState: FLYING_OK
controlState: CTRL_LANDED, flyState: FLYING_OK
If anyone can shed light on what these state changes are doing and why it is causing an issue with sending the movement commands.
Any help would be greatly appreciated as I seriously need to fix this issue ASAP! My degree depends on it!!
Thanks

Leslie, I don't know offhand what the problem could be, so I only have some general recommendations (in order by which things I would try first):

Do you have another drone you can try, in case it's a problem with your specific vehicle?
Can you reproduce the problem with a small program that just commands the drone to take off, move around a little (without joystick input), and then land?  If you can reproduce the issue with a small program, I'll try running it on my drone and see if I get different results.
Try using tcpdump or wireshark to sniff the network messages sent between your computer and the drone to confirm that the AT commands are being sent correctly.
Is it possible the firmware was upgraded recently?  If nothing else seems to be working, it might be risky but you may consider trying to downgrade the firmware: http://drone-apps.com/support/ar-drone-firmware/

Hi Wiseman,
Thanks for the response.
I purchased a second drone that arrived today that gave the same result.
The simplest test of setting up a client.createRepl() displays the issues. I send a take off command and it returns true. I then send a clockwise(0.5) command and nothing happens. The back two lights go red whilst the front two remain green.
The drone just wants to carry on gaining altitude. I've sent a configuration command to limit the maximum altitude to 500mm to stop the upward thrust but this seems to do nothing.
This was all working recently. :(
Since the take off and land commands are processed as expected, I'm fairly certain that the AT commands are being sent correctly. I've tried this test with several versions of ar-drone and with two separate drones.
I'm using a wireless dongle to connect to the drone and wonder if it is failing or placing restrictions on how fast or how much data can be bouncing between my computer and drone. As for the firmware, I've tried this on two drones (one fresh out the box) and still facing the same issues.
I really appreciate all the effort in responding and helping me resolve this!! Thanks again :)

So this morning I set up a createRepl file on a laptop to check if it was a wireless fault happening sporadically. Using the ar-drone library, I could takeoff, land and flat trim but it would not accept ANY movement commands.
@wiseman, would you be able to run a check on your hardware/software with a createRepl to see what behaviour occurs. The only movement I get from the drone is through the AR.FreeFlight app now. Other applications such as Webflight have stopped working for me too.
Thanks

Sure, I can check that later today.
I'm just curious what could have changed.  As mentioned in another issue recently, it's been about 2 years since the last commit to this code.  That leads me to think that the problems are related to a change in your environment, of which the most likely might be an updated drone firmware.  Just so I can compare, what firmware version are your drones running? (See http://www.dronezon.com/diy-drone-repair-videos/parrot-drones/how-to-upgrade-the-firmware-on-your-parrot-ar-2-0-drone/ for instructions on checking your version.)
Doing network-level sniffing using tcpdump or Wireshark should be a good way of (relatively) definitively seeing what is different between the FreeFlight app, which works, and using node-ar-drone, which doesn't.  It's labor intensive, but it's a method I've used successfully before (using Wireshark).
Basically, you look at the packets being sent to the drone on TCP port 5556, which will contain all the AT commands being sent.  Wireshark has a feature where you can select one packet, tell it to follow that stream, and it will show you all the traffic to/from that port.  You do that while running software that works with the drone, then do it again with node-ar-drone, and look for differences.

That would be a great help!
As regards to the firmware, both drones are up to date according to the AR.FreeFlight application.
AR Drone Hardware: 2.2
AR Drone Software: 2.4.8
Inertial Hardware: 2.3
Inertial Software: 5.34
I will look at doing the packet sniffing this evening and see how I get on. I've not used Wireshark before but I hope with a bit of fiddling around, I can get some data that explains the differences between the applications.
An old version of my software was tested earlier today and I found I could get the commands to work with the drone after resetting the drone prior to loading the software. This worked on both drones but didn't feel smooth. It feels like all commands are being pummelled across to the drone at once and it just wants to keep gaining altitude. I put the altitude down to the bottom sensor disliking carpet so now I have a hard surface offering a better read out on the altitude.
I've gone back to the core basics in the application to minimise any interference and using that as a test bed. I'll write another update this evening to let you know how I get on!
Thanks :)

Just FYI I used createRepl to takeoff() and clockwise(0.5) and everything worked fine.  I have the same versions of everything except AR.Drone Hardware is 2.1.

Thanks for the test.
I've looked at the packets to trace the AT commands and can confirm that both my application and AR.FreeFlight are sending fine. The yaw left command was sent to both applications but only the AR.FreeFlight had an effect on the drone.
Wireshark for the pc application: https://gyazo.com/a507d64baf1d8f50973c7f60213a17c9
Packet Capture for AR.FreeFlight: https://gyazo.com/ee30590584e88cd91da45d7579a94e6f
My last test tonight will be to analyse all the data packets and see if there is something abundantly wrong. I'm starting to lose faith in a solution appearing now! Maybe I should just implement what I can and plead with my supervisors that is "was" working. If you have any further suggestions, that would be amazing!
Thanks :)

I'm closing this for now since I can't reproduce, but if you have any new information feel free to reopen.

@LeslieNock did you fix your Problem? I am currently experiencing a similar Problem: I can rotate, raise and lower the drone via the node module, but not tilt in any direction. It was also working ~half year ago, but now it doesn't for some reason.

@LeslieNock @TheOssi  Do you still have this problem? I had a similar problem where the drone worked but after a few weeks it would not respond to motor controls.
I did some researching and found that you could reset the drone and that may work to solve the problem.
When I reset my drone by pushing the reset button with the battery in, the drone responded normally to my commands.
FYI: I also have drone hardware 2.2

@TheOssi @BCaven Hi both, sorry about the delay in replying! Unsure if you are still experiencing these issues but the root of my issue was the application I built was not closing the session to the drone correctly. This meant that after resetting the drone, it would work fine on the first flight but the second one would not respond correctly. I had to trigger a safe disconnect from the drone and my software to avoid this problem again.
Another issue that resulted in some sporadic changes in if the drone was accepting movement commands was a bottleneck on the Web sockets. It transpired that I was sending the movement commands to frequently and triggering more than three asynchronous functions that fired off movement commands resulted in no commands getting through.
If I this doesn't solve your problem, please be sure to reply as I will actively try to respond.
Looking to pick up my old application and improve the GUI. Then... I guess I could release it on Git. I'll keep you informed on that front :)

Do you remember the code to trigger a safe disconnect?


More detail in content/first-order-logic/syntax-and-semantics/satisfaction.tex

content/first-order-logic/syntax-and-semantics/satisfaction.tex should probably be split into two sections.
The definition of satisfaction needs an example or two.
The proposition prop:satindep needs more detail, esp. regarding free & bound variables of B vs those of A (ie why the IH applies).
The main reason why this is proved is that it shows that if no variables are free, variable assignments don't make a difference. Ie this justifies the definition that follows it, but this should be explained!

Made progress in https://github.com/OpenLogicProject/OpenLogic/commit/dd271c3554157ede14324a9899abb423ffc876f1#diff-894db9c70cc63e1572377dd88efb3557


Error for image pull for [sig-cli] test-Kubectl client Kubectl copy within kubectl-1634 namespace

What steps did you take and what happened:
Getting Error: ErrImagePull for tests performed with --focus=[sig-cli]
Test = [sig-cli] Kubectl client Kubectl copy
The test was performed in airgap environment and all the required images were pre-pulled and pushed to the private registry.
command used :
sonobuoy run --plugin e2e --e2e-repo-config custom-image-config --mode=certified-conformance --sonobuoy-image <IP_ADDRESS>:5000/sonobuoy:v0.20.0  --kube-conformance-image <IP_ADDRESS>:5000/conformance:v1.18.6  --e2e-focus="\[sig-cli\]"
image repo was provided to sonobuoy via config - custom-image-config
[root@bootstrap sonobuoy]# cat custom-image-config
buildImageRegistry: <IP_ADDRESS>:5000
dockerGluster: <IP_ADDRESS>:5000
dockerLibraryRegistry: <IP_ADDRESS>:5000
e2eRegistry: <IP_ADDRESS>:5000
e2eVolumeRegistry: <IP_ADDRESS>:5000
gcRegistry: <IP_ADDRESS>:5000
promoterE2eRegistry: <IP_ADDRESS>:5000
sigStorageRegistry: <IP_ADDRESS>:5000

ERROR
  Warning  Failed          3m14s                  kubelet            Failed to pull image "busybox": rpc error: code = Unknown desc = failed to pull and unpack
 image "docker.io/library/busybox:latest": failed to resolve reference "docker.io/library/busybox:latest": failed to do request: Head https://registry-1.docker
.io/v2/library/busybox/manifests/latest: dial tcp: lookup registry-1.docker.io on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:57273-><IP_ADDRESS>:53: i/o timeout

What did you expect to happen:
The image was not mentioned during the sonobuoy image pull, for busybox:latest version.
Also, the test doesn't seem to look for the required image in cursom registry.
Environment:

Sonobuoy version: v0.20.0
Kubernetes version: (use kubectl version): v1.18.6

Thanks for the issue report! We will definitely look into this; we've gotten a similar complaint recently and have other upstream issues with certain tests not respecting those values or properly listing their required images.

Hm; so something is off since I see the "latest" tag and I know busy box is in general defined in the test image stuff: https://github.com/kubernetes/kubernetes/blob/v1.18.6/test/utils/image/manifest.go#L211
You can see the test at your k8s version here just uses a hardcoded yaml file, which uses busybox if you check:
/Users/jschnake/go/src/github.com/kubernetes/kubernetes/test/e2e/kubectl/kubectl.go
This was fixed in this commit: https://github.com/kubernetes/kubernetes/commit/aaa90476cbd30e0e71bf6967a947472f79e8b042
So unfortunately you've just hit one of the cases that show the point that upstream tests are a bit messy and multiple folks are working around these issues at the same time.
Thank you for reporting this though and please continue to report issues you have like this, if I hadn't seen it as already fixed upstream I would have done so.


Ogre background loader thread blocks main thread.

When running async thread loading, the main thread blocks on several occasions to wait for the asset loader thread. This causes performance issues at 100ms-1000ms scale while assets are being loaded.
The blocking occurs on this mutex https://bitbucket.org/sinbad/ogre/src/2ba0595e05fb/RenderSystems/Direct3D9/include/OgreD3D9HardwarePixelBuffer.h#cl-78 . Interestingly, the OpenGL Render System implementation on Ogre does not contain this kind of global system-wide mutex.
Possible workarounds:

The EC_Mesh raycast code causes Ogre to acquire the mutex in the main thread. Specify the selection layer as 0 for all placeables which do not need to be clicked on, so that the raycast code is not executed that often (mostly for static unclickable geometry)
The Hydrax component causes the main thread to acquire the mutex each frame. Remove Hydrax components from the scene, and use a WaterPlane component instead.
Creating resources (like materials, or other overlays) in the main thread will probably cause the Ogre to acquire the mutex. Don't do this while assets are being loaded asynchronously.
Switch to OpenGL. This might not help much, unless Ogre implements the use of wglShareLists (see http://www.opengl.org/wiki/OpenGL_and_multithreading )

Possible fixes:

Implement manual asynchronous asset loading code which loads in assets without resorting to code that acquires a system-wide mutex.
Implement a shadow local copy of the geometry data in Mesh assets to avoid having to use Ogre system-wide mutexes. Ogre allows a shadow copy for hardware buffers, but this is not available if Ogre mesh manager load functions are used.
Additionally rewrite all other parts of the main thread which utilize Ogre calls that acquire the Ogre system mutex. E.g. for Hydrax which streams in dynamic GPU data per-frame, this can be difficult.
Fix Ogre to not to resort to system-wide mutexes.

Have you been thinking how to make the custom ogre threaded loading? I read the ogre forums about this and many people seem to have the exact same mutex lock problem we are having, even with queued loading it blocks rendering and biggest issue for people is textures (that are understandably heavy to decode etc.).
How can we do threaded loading and access Ogre from it without its mutexes? Or is this a matter of doing some prep work, like getting .mesh file data to buffers or unpacking encoded textures to raw pixel data, before accessing/passing this data to Ogre? Are there some DirectX APIs that we could leverage to upload stuff to the gpu asynch and then telling Ogre about it after the fact?

OpenGL indeed does not have the OGRE_STATIC_MUTEX_INSTANCE(D3D9HardwarePixelBuffer::msDeviceAccessMutex) and OGRE_STATIC_MUTEX_INSTANCE(D3D9Resource::msDeviceAccessMutex) objects. Although the necessity of those mutexes is questionable.


Add a .unitypackage for MRTK's TestUtilities

The TestUtility refactor that @CDiaz-MS did a while back added some cool NuGet package for the MRTK test infrastructure. This has been used internally by a few teams to build out their test infra, and up until now we haven't had a .unitypackage equivalent.
This PR publishes the core set of test infrastructure that the MRTK itself uses to write integration tests, things like:

Show hand there.
Pinch
Move hand over there.
Release

This lets you write automated tests that interact with things in your scene, so that instead of having to do manual test passes, you can have automated (i.e. CI-time) coverage of core/common things. The tests that we've written have helped us avoid regressions in components and to prove functionality, and it's like that consumers will also be able to benefit from this.
Note that there is an initial investment to writing any set of tests, but the payoff is usually worth it (it has been worth it for us)

/azp run

I'd recommend moving the test utilities into the tools folder / package rather than creating a new package. this is where the upm package proposal is considering placing it.

@davidkline-ms this is consistent with the current set of nuget packages, so I'd rather keep this as-is.
Also, I don't believe that this is a "Tool" (i.e. it's not a UI/Editor tool). We should separately figure out what the long term packages are and then do a one time pass to bring things along.

More generally, to reduce complexity/overhead we should have the same set of packages regardless of distribution method (i.e. what we group up is the same, HOW we package them can be different i.e. UPM/.unitypackage, etc)

/azp run mrtk_docs

/azp run mrtk_docs

More generally, to reduce complexity/overhead we should have the same set of packages regardless of distribution method (i.e. what we group up is the same, HOW we package them can be different i.e. UPM/.unitypackage, etc)

Agreed.


Add Redux To The Project

Deliverable:

[ ] Implement redux in frontend

assign this issue to me @Kajol-Kumari

assign this issue to me @Kajol-Kumari

Please go ahead :)


implement filters on queries

Current SDK Version

Use-cases
IONOS API allows for filtering results (late apply) on resource dependant queries (see https://devops.ionos.com/api/cloud/v5/, Custom Response Filters. Hope link to old SDK doc still works).
This is very useful to get specific resources or requests, e.g. requests being in status QUEUED.
Proposal
Implement filters for every resource. These are available in CloudAPI but not in ionosctl. They must be implemented in ionosctl too.
References

Hello,
Thank you for suggesting this enhancement. This was implemented in the latest version of ionosctl v6.
Ana


Add the new image implementation for a more stable sending of images

What the bot will do now if a image is being sent:
--> Detect if a image is sent, if so, download it locally:
if message.attachments:
       for attachment in message.attachments:
                await attachment.save("image.jpeg")

--> On the process of channel.send, check if a downloaded image exists, if so, send a embed WITH the image and delete the image from the local disk, otherwise send a embed WITHOUT the image:
xy_file = Path('image.jpeg')
async def send_message(channel, embed):
    try:
        await channel.send(embed=embed)
        if xy_file.is_file():
          try:
             file = nextcord.File("image.jpeg")
             embed.set_image(url="attachment://image.jpeg")
             await channel.send(embed=embed, file=file)
             os.remove("image.jpeg")
          except:
             await channel.send("An error occured while sending your image. Please try again.")
        else:
          await channel.send(embed=embed)

    (Take a look at the tab "Files changed" for differences between the code versions)

Thankyou!

New changes:
--> Add GIF and MP4 format support (not more than 150 frames, otherwise the bot will start laggin')

Closing for now, solution is not efficient enough.

Feel free to re-open at any time


build: downgrade python to 3.8, consistently use focal across images and documentation

Description
The codebase contains references to Ubuntu 18.04 (bionic), which has surpassed its EoSS* in May 2023 (source), mostly in Dash-specific CI and Gitian, which was being sunset around the time period Ubuntu 14.04 (trusty) was still being deployed (source).
https://github.com/dashpay/dash/pull/4717 bumped the reported minimum Python version to 3.10, a version not available on focal as of this writing (source). focal does optionally offer the ability to use 3.9 (source) but not 3.10 (source, error page).
The bumping to 3.10 did not include the addition of alias detection for current releases, which would be available through rolling release distros, or itself, as python3.10. In light of that, it was reverted and pull requests related to Python being bumped have been backported.
Bitcoin currently asserts the minimum Python version as 3.8, which is the same version offered by default on focal and so this pull request doesn't assert the minimum version as 3.10. Should Dash choose to move its base distribution to Ubuntu 22.04 (jammy), then the minimum version can be set to 3.10.
* - EoSS is not EoL, bionic's EoL is in 2028 as its currently within its extended support cycle
Additional Notes
References to Debian Stretch (which reached EoL in June 2022, source) will be replaced with Buster with backports like https://github.com/bitcoin/bitcoin/pull/27029 and so have been left untouched here for now.
https://github.com/bitcoin/bitcoin/pull/18705 needed to be backported as its a) no longer support trusty and b) it interferes with the scripted-diff verification script (see build)

I was pretty concerned about this, but actually it seems this version is supported on m1 macs now. 👍 however, tbh I'm thinking we should update everything to jammy

Currently the emphasis of this PR is to harmonize references to current running base image. I'm not against moving to jammy but focal's EoSS is in April 2025 (source), which means it's still actively deployed and should be tested against.

Currently the emphasis of this PR is to harmonize references to current running base image. I'm not against moving to jammy but focal's EoSS is in April 2025 (source), which means it's still actively deployed and should be tested against, at least till the end of 2024.

Well, I'm not sure I agree with that fully: that we HAVE to test against focal as well. I think it would be fine if we just moved everything over to jammy. We should definitely maintain binary support for it, but we don't really need to retain development support for it.


help me with this,

I can not enter synctrayzor because I get this message

How can I correct it? It's urgent.

Something has corrupted the file C:\Users\Lenovo\AppData\Roaming\SyncTrayzor\config.xml. If you want a quick fix, delete this file. You will lose all settings which you set inside the SyncTrayzor UI (in the File -> Settings menu, for example) but not any of the Syncthing configuration (which includes your folder and device configuration).


We can hide this better by using this attribute

All the obsoletes should have that too.  I did that in my PR to move them all to a partial classes file, but haven't done it to the live files.

Feel free to PR that, its a good idea. I'm gonna leave this PR alone with just this though.

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


:bug: Fix release-0.5 nightlies

LGTM, but we need use exisitng operator tag (so rc, https://github.com/konveyor/ci/pull/59/files#r1695524498)

This is to track GA release so keeping this in


youtube-dl: 2020.12.22 -> 2020.12.26

https://github.com/ytdl-org/youtube-dl/releases/tag/2020.12.26

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

20.09: https://github.com/NixOS/nixpkgs/commit/0c81b9a4f170f734bd7e587a39e56470c59733e7


gen2 record/replay

This functionality (both recording and replaying) will be moved to depthai/depthai_demo.py script in the future.

added record.py/replay.py scripts. Also added /data/ to gitignore.
TODO:

Optionally save depth as well and when replaying, use saved depth instead of mono frames & stereo node
Add readme
Add demo video/gif

Replaying recorded set: https://www.youtube.com/watch?v=J4ifV3nqRwY

This will be so nice to have in depthai_demo.py.  And I really like the idea that was brought up internally of adding some kind of "dataset sharing" functionality, so community (and we) could prepare some common use case datasets (like driving) and whole community could easily use it by just specifying the name into the depthai_demo argument.  That will be so awesome for folks to be able to replicate work.

https://github.com/luxonis/depthai-experiments/blob/gen2-replay/gen2-replay/README.md#replay-usage
Just a suggestion, the -p comment could be changed to Path of the stored data to avoid confusion with the record.py path comment. :)
This script is really useful btw!!

you are totally right, we will keep that in mind when migrating this functionality into depthai_demo, thanks :)

a (very) late update: we have merged this functionality in a separate PR: https://github.com/luxonis/depthai-experiments/pull/202


RadzenPanelMenu - we need a flag that shows where the click was -> on the Text or submenu arrow

Hi!
Please add on
MenuItemEventArgs args
flags:

args.IsTextClicked - shows that there was a click on Text
args.IsSubmenuArrowClicked  - shows that there was a click on tex on submenu arrow

void OnParentClicked(MenuItemEventArgs args)
{
if( args.IsTextClicked) ....
if(args.IsSubmenuArrowClicked ....
console.Log($"{args.Text} clicked from parent");
}
Thanks.

Clicking expand/collapse icon will update Expanded property which can be bound - if you do not want to use binding you can simply use ExpandedChanged event of the item.


Ruby: Operator methods not highlighted correctly

(Original issue 1033 created by tknerr on 2014-09-21T08:29:05.574264+00:00)
When using operators in method-style notation they are not highlighted correctly, e.g.:
x.== 4
y.<< 'bar'

The == and << should be highlighted as methods (as they are) when being prefixed with a .
See demo here:
http://pygments.org/demo/677425/

(Original issue 1033 last updated on 2014-10-07T22:58:11.672457+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by tknerr on 2014-09-21T11:14:55.415729+00:00)
added screenshot

(Original comment by tshatch on 2014-10-07T03:13:58.139210+00:00)
RubyLexer: Highlight operator methods better.
Fixes #1033
→ <>

(Original comment by tshatch on 2014-10-07T03:14:26.267060+00:00)
I put in a rough fix for this -- can you verify that it works from tip now (and, how bad the fix in that rev above is).

(Original comment by tknerr on 2014-10-07T22:58:11.669392+00:00)
Thanks @tshatch - works perfectly :-)
Btw: I double-checked with my other code snippets and the fixes for #1033 and #1031 were the only differences :thumbsup:


Settings panel

Need to create a place where you can adjust some settings.
For example;

the directory where coverage files are
colours used in the margins for covered / not covered
more stuff to come for sure

Added in v1.16

resolved with https://github.com/ppumkin/PrestoCoverage/pull/18


Add k3sup

https://github.com/aquaproj/aqua-registry/issues/858

Duplicated https://github.com/aquaproj/aqua-registry/issues/875


fix: severe lack of rice

where rice

Related: WieeRd/ricefield#9

HWAT

In Elysian fields where rice plants gleam,
Golden waves dance in a twilight dream.
Config files rustle like whispering leaves,
As Linux skies compile new eaves.
I 'sudo' serenity in this sacred place,
Ricing my soul with a terminal grace.

ChatGPT O1 preview -


Mark result as finished/non-finished in hubstorage

Mark hubstorage reduce result items as not finished while running, and
mark them as finished once the job is finished

LGTM

@eliasdorneles Changed :)

Looks great, thanks @Youwotma !


LogReader: live_logreader helpers

ideally, all the OP tools should be able to take a route or pull from live easily

This broke the useradmin build: https://github.com/commaai/xx/actions/runs/7892658023/job/21539641441.
We currently don't need to build openpilot for any of the chffr stuff, and I'd like to keep it that way unless there's a good reason not to. Can you fix it?

I'll move it to it's own file

Let's also add a test that LogReader can be used without building openpilot.


Fix layout warnings

Fixes #127
The below warnings were ignored

Attribute android:foreground has no effect on API levels lower than 23 (current min is 16)

This warning is not solvable due to a bug which is existing since API 23 [1]

Overlapping items in RelativeLayout

Fixing this requires using margins which will change the layout majorly and the changes are it visually pleasing either

Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with ./gradlew check to make sure you didn't break anything

[x] If you have multiple commits please combine them into one commit by squashing them.

@ashwinkey04 The app has been redesigned.


Moving recognition of contributors to one line

Thanks @lindy65, can we please also remove the bullet point, so it would look like:
/platform
lindy65, esethna ...

Thanks @lindy65 !


Fastnlight: Watch +91)(78-45-17-15-32

Fastnlight requests the watch of the watch_number +91)(78-45-17-15-32. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Jeff Schaller in Charcoal HQ


--build-server-no-success-messages is ignored

I just checked v0.7.0 from command line and it seems to work - no success TeamCity message. End of console output is like this:
...
##teamcity[testIgnored name='SolutionCop.TreatWarningsAsErrors']
INFO: Analyzing projects using rule WarningLevel
##teamcity[testIgnored name='SolutionCop.WarningLevel']
##teamcity[testSuiteFinished name='SolutionCop']
INFO: Analysis finished!
INFO: No errors found!

Without flag it is:
...
##teamcity[testIgnored name='SolutionCop.TreatWarningsAsErrors']
INFO: Analyzing projects using rule WarningLevel
##teamcity[testIgnored name='SolutionCop.WarningLevel']
##teamcity[testSuiteFinished name='SolutionCop']
INFO: Analysis finished!
INFO: No errors found!
##teamcity[progressMessage text='PASSED - SolutionCop.xml']

@Litee , what Team City thinks:

First test arrived: stop displaying status messages (such as "Building project XXX", etc)
TeamCity shows only like "4 tests passed" (for 4 SC rules)
After Unit Test session start (e.g. after building) TeamCity starts to increment tests counter

What I think we should to improve:

All rules ignoration should be written to console without TeamCity mark
All passed tests info should be written to console without TeamCity mark
All errors are written with TeamCity mark

Sounds like one more strategy for console output. Let us do the following - I just have pushed re-factored command-lines parameters processing. You can raise PR with alternative strategy into ReportFormatType enum  + processing. IMO it will be faster ;)


⚠ RPC server - Astar has degraded performance

In 3dcd0c1, RPC server - Astar ($ASTAR_RPC_URL) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: RPC server - Astar performance has improved in 6c64c8e.


iOS examples bunch

What's the use case for the sample?

Multi-index search
Autocomplete with Voice search
Categories with Hits
Query Suggestions
Query Suggestions with recent searches
Query Suggestions with Hits
Query Suggestions with Categories

What's the programming language?
Swift
Author Information:

Author name: Vladislav Fitc
Author GitHub Handle: github.com/vladislavfitz
Organization name: Algolia
Organization GitHub URL: github.com/algolia

Dependencies:

InstantSearch iOS
SDWebImage
Voice Overlay iOS

Checklist:

[x] My sample application is open source and has a permissive license such as MIT or Apache-2
[x] There are no known security vulnerabilities and I'm following security best practices
[x] I've read Algolia's best practices coding guidelines for my sample
[x] I agree and adhere to the Code of Conduct
[x] The sample has been authored by me / or my organization and will be kept up-to-date. If the sample will not longer be maintained, I'll notify this project.

Submissions have been added to CodeX.

Submissions have been added to CodeX.


mv chart to chart repository

mv csi driver chart to chart repository & update doc

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5e66625). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #268   +/-   ##
=========================================
  Coverage          ?   77.04%
=========================================
  Files             ?       19
  Lines             ?     1612
  Branches          ?        0
=========================================
  Hits              ?     1242
  Misses            ?      328
  Partials          ?       42

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 5e66625...88cf226. Read the comment docs.


fix(CI): Hold back flake8 version

flake8 3.4 was recently released and broke support for ignoring multiple
items on a line.

[x] This contribution adheres to CONTRIBUTING.md.
[x] New tests have been created for any new features or regression tests for bugfixes.
[x] tox successfully runs, including unit tests and style checks (see CONTRIBUTING.md).

Coverage remained the same at 64.24% when pulling 7f044f756ff5b8c39ca8ddaf73580fc0e0a9754b on epage:lock into 13a2757da86665d8e22112c22b93162d27aa3468 on ni:master.


Run test-migration test against a DB with data in it

I would like to take whatever the DB looks like right now and fill in some carefully handcrafted data into the tables before running the tests. Whenever a migration is done to the DB that adds a table, the author should then provide handcrafted rows for that table. Only a few are sufficient. This is NOT needed for performance but for migration tests.
The integration tests MUST run against an empty database or else we cannot test list actions for resources that haven't been created yet.

@kwk This was addressed by my changes to the migration tests. In this case, we have an incremental database whose data is being updating according to the migrations.
I'll close this issue but feel free to open it.


Use ruff for linter and formatter checks

This replaces pylint and black with ruff for linter and formatter checks of the Python code. The examples and deephyper directories are the focus of the changes. The GitHub Actions workflow is also changed to use ruff instead of pylint and black.

@Deathn0t The tests are not passing but I don't think it is caused by the changes in this pull request. It looks like the develop branch is failing so I think something was changed on that branch to cause the test failures in this branch.


[FLINK-7772][blob] fix test instability in BlobCacheDeleteTest

What is the purpose of the change
BlobCacheDeleteTest did not account for the server executing the delete call of a transient BLOB after acknowledging the request. This resulted in the testDeleteTransientLocalFails* tests failing.
Brief change log

use verifyDeletedEventually instead due to the asynchronous delete call

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Thanks for fixing this, merging...


Restore examples [ECR-4140]

This PR restores examples for ListProof and transaction declaration / signing / sending.
See: https://jira.bf.local/browse/ECR-4140

Coverage remained the same at 93.21% when pulling 7aff0536a7630c9e4a934ed631597feb8f383791 on slowli:restore-examples into 31bffba27c1a4794e765111e836b4cd33a3e2c90 on exonum:master.


Notification settings not working properly

When turn on the switch for "Enable notifications for this device", it appears to stay on as if the setting took effect, but if you go back to the main Messages screen, then back into Settings, the setting is disabled again. Whichever device I am signed into at the moment is also missing from the Notification Targets area near the bottom of the page.

This issue was triggering with an official ROM.
The GCM or server registration does not display an error or a spinner.
The behaviour will be updated

Would it be possible to send a bug report ("Send Bug Report" item in the slider menu)?
As you mentioned, "turn on the switch for "Enable notifications for this device"", and then send the bug report please.
It would permit to figure out what is going wrong from this point on..

A bug report has been sent after toggling the settings.

Looks like there is a network error...

06-26 21:40:23.173 18487 18487 E GcmRegistrationManager: registerPusher onNetworkError failed to connect to home.rdash.in/<IP_ADDRESS> (port 8448) after 15000ms: isConnected failed: EHOSTUNREACH (No route to host)
06-26 21:40:23.173 18487 18487 E GcmRegistrationManager: fail to register @eaburdick3:home.rdash.in (failed to connect to home.rdash.in/<IP_ADDRESS> (port 8448) after 15000ms: isConnected failed: EHOSTUNREACH (No route to host))
06-26 21:40:23.173 18487 18487 D GcmRegistrationManager: registerSessions : onSessionRegistrationFailed @eaburdick3:home.rdash.in

Do you have some connection issues on your server ?
But, we have something to improve.

Not that I'm aware of... my phone and computer are connected to Matrix all day and night without issue that I can tell... the only thing I remember having downtime for in the past 2 days is I upgraded synapse the other night, but I wouldn't think that would be causing that many errors?

do you have any trace on server side ?
The android developpers cannot help you to fix this issue if it is a server issue.
Do you have some traces on server to investigate if the GCM registration was done ? you have the date & time in the logs we posted here.

I failed to think about this before filling this report, but this was happening with synapse v0.16.0-rc1 at the time. Last night I upgraded to master v0.16.1, and as of right this minute, it seems to be working fine... I'll keep messing around with it a bit and close it if I find its fixed.

Assume this issue can be fixed because we didn't get any news from the last 2 weeks.


Implement websocket server example

You can give it a try! There's a server for testing the client in codec/websocket/test_main.go: https://github.com/talostrading/sonic/blob/master/codec/websocket/test_main.go#L16.
You'll essentially need to implement the server side of the websocket handshake, as coded above to then boostrap a Stream.


Remove unnecessary comments

Motivation
Now that we know Prometheus better, these comments are not needed anymore
Proposal
Remove comments
Test Plan
CI

Current dependencies on/for this PR:

main

PR #1212

PR #1216   👈
PR #1215

This stack of pull requests is managed by Graphite.


Additionally:

further configuration cleanup
more flexibility in building EurekaDeployment with extension modules
supporting configuration override in EurekaDeployment builder

NetflixOSS » eureka » eureka-pull-requests #353 SUCCESS
This pull request looks good


[BUG] Mod can be used to dupe items

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
There is still no new release to fix the dupe bug in all crafting grids. (https://github.com/Team-EnderIO/EnderIO/issues/555)
This affects many mod packs. Should I rather report ender IO to each of those, which would make them remove it?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- OS:
- Java version:
- Minecraft version:
- Version:

Anything else?
No response

This was definitely released, could you check and see that it's the latest version. If it isn't can you share a quick gif of you causing the dupe so we can catch it. Thanks

This affects many mod packs. Should I rather report ender IO to each of those, which would make them remove it?

It was said at the time of release that EnderIO is still in alpha, and should ideally not be included in modpacks yet, as there could be breaking changes, or breaking bugs at any moment

My bad, I forgot to check alpha releases on forge.
But AFAIK the version with the exploit is still in the packs Inclusive Reborn and All The Mods 9, to name two very popular ones. They're VERY regularily updated and didn't seem to have gotten any info about this problem. I don't know how the communication here normally works but I think you should somehow express the importance of this update, possibly even actively notify related packs. Maybe alpha sub versions aren't noticable enough, idk...

It was announced with the very first alpha release that it is not recommended to be used for anything other than testing, and definitely not in modpacks. The users who used the mod or added to their packs used them even after our warning, and thus are responsible for keeping up with the proper fixes.
Users are free to ask modpack devs to update their packs, but we take no responsibility for other people shipping alpha software even after multiple warnings (some of which were forcibly removed by pack authors against our wishes)


Add Konnect specific instructions for Adding Certificate Authorities

Where is the problem?
https://docs.konghq.com/hub/kong-inc/mtls-auth/#adding-certificate-authorities
What happened?
The provided curl example will not work with Konnect instances since the Control Plane is not accessible directly.
What did you expect to happen?
Should include either screenshots or directions to add certificates via

UI (Shared Config > Certificates > New Certificate)
curl command that works with the Konnect admin such as:

curl -sX POST https:konnect.konghq.com/api/control_planes/[Konnect-id]/ca_certificates -F<EMAIL_ADDRESS>--cookie '[generated access cookie]'

Code of Conduct and Community Expectations

[X] I agree to follow this project's Code of Conduct
[X] I agree to abide by the Community Expectations

Happy to make a PR, but not sure how best add the info. Maybe a navtab for konnect specific?

Hey @eshih ! Thanks for catching this. For this specific topic, since using mtls and using certs is important for Konnect, you're welcome to edit it. I agree - a navtabs element would be the way to go.
Unfortunately, this is also a symptom of a much bigger issue - none of the plugin docs provide Konnect API examples, and there are a lot of them.  We have an overhaul of the plugin hub planned for next year, so I'm adding the issue of tackling further Konnect examples to the list.

Sorry for the delay @lena-larionova I wasn't getting my email notifications in so I didn't see your comment. I've put in a PR to try to update the page!

Completed with PR #3495


feat: Add semver range support to all cmd & pkg

Use "github.com/Masterminds/semver/v3" to validate, honor, and use the semver constraints listed in shared deps everywhere.
Which right now means:

hypper lint CHART: semver constraint is now a must (we will ERROR if not present).
hyper shared-dep list CHART:  filter against the constraint correctly, now outputting status: out-of-range if the installed dep doesn't satisfy what is needed.
hypper install CHART: pull correct chart that satisfies the needed semver constraint. Error if the repository/cache doesn't contain a version that can satisfy it.

In addition,

Add related tests. For that, add new pkg/chart/{Mock(),MockChartOptions()} functions, since tests for dependencies need releases with charts that contain specific Chart.Metadata.Version. I suppose these functions will grow in the future, and we should think about upstreaming them.
Fix a bug with ns when hypper shared-dep list -n foo.

Closes: https://github.com/rancher-sandbox/hypper/issues/90

I haven't updated docs/ with the slightly different ouputs.
(also, it may be a good idea to review the PR stepping through commits, instead of by files).

merging! thanks :)


Unable to see the companion tab in Homework: Programming Assignment 1.5

In Homework: Programming Assignment 1.5, I can't unable to see the companion tab that has the instructons for the Homework: Programming Assignment. I refresh the companion tab, and I get the same result of the companion tab, not able to see the companion tab. I did all the steps in the pdf file with this troubleshoot issue, and I get the same result; the companion tab is not responding. I change browsers, and the companion tab does not show the instructions and the submit button as well. My question is: Can GitHub fix this issue, and for all homework: Programming Assignments?
Version: 1.85.2
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

/question
Please raise this with your course support channel.

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!