Responsive prop feature does not work with version 5.

Describe the bug
Responsive props are broken in styled-system 5 (Tested with space and color).
To Reproduce

Create a component with some responsive props and use it:

const Text = styled("div")(color, space);
...
      <Text p={[0, 1, 2]} color={["primary", "secondary", "neutral.1"]}>
        Colored Breakpoints
      </Text>

I created a little project where we can reproduce the issue: https://github.com/xgbuils/responsive-styled-system-issue:

In branch master<EMAIL_ADDRESS>playing with viewport size, colors and paddings change.
In branch ss5 (same code with<EMAIL_ADDRESS>version) colors and paddings does not change when the viewport size changes.

Steps to reproduce the behavior (include versions of relevant packages):
Steps defined on the README of the project.
Dependencies:
    "@emotion/styled": "^10.0.27",
    "emotion-theming": "^10.0.27",
    "react": "^16.13.1",
    "react-dom": "^16.13.1",

Use codesandbox to create a reproduction:
<EMAIL_ADDRESS>https://codesandbox.io/s/styled-system-breakpoints-scale-and-aliases-6qlgs?from-embed
<EMAIL_ADDRESS>https://codesandbox.io/s/styled-system-breakpoints-scale-and-aliases-p95go?from-embed
Expected behavior
I expect the same behavior (padding and colors changing) because change log does not notice about any change related to responsive props behavior.
Screenshots
The README of my issue repo has screenshots.
Additional context
browsers I tested it:

Chrome 83
Firefox 75

I found out the problem. This is the theme I specified:
const theme = {
  breakpoints: [512, 768, 1024],
  colors: {
    primary: "blue",
    secondary: "red",
    neutrals: ["#333", "#888"]
  },
  space: [0, 40, 80]
};

and in changelog I can find:

No longer converts numbers to px strings

I replaced numbers by px stringss and media queries are working now.
Cheers.


cannot build under ubuntu 20.04 - ithub/nvui/build/nvui_autogen/UVLADIE3JM/../../../src/cursor.hpp:8:10: fatal error: span: No such file or directory

I am trying to get nvui to compile in Ubuntu 20.04 but I am hitting this build error:
ithub/nvui/build/nvui_autogen/UVLADIE3JM/../../../src/cursor.hpp:8:10: fatal error: span: No such file or directory

the cmake process completedd without error (both with and without vcpkg).
any ideas?

<span> is a c++20 header file, so you would probably need to update your c++ version.


Ingress - allow custom ports

Istio ingress should allow specifying custom ports for HTTP/HTTPS.
Voyager ingress is HAproxy ingress that allows it.
https://appscode.com/products/voyager/6.0.0/guides/ingress/http/custom-http-port/

We already have this support implemented.. in Istio gateway (https://github.com/istio/api/blob/master/networking/v1alpha3/gateway.proto).. and it should be available in 0.8


MI - REFERENCE section (Custom Inbound)

Complete the reference content for [1].
[1] https://github.com/wso2/docs-ei/blob/master/en/micro-integrator/docs/references/inbound_endpoints/custom-Inbound-endpoint.md

The original page is removed. Content is separated into 'Creating Custom INbound Endpiont'[1] and 'Properties'[2].
[1] https://github.com/wso2/docs-ei/blob/master/en/micro-integrator/docs/references/customizations/creating-custom-Inbound-endpoint.md
[2] https://github.com/wso2/docs-ei/blob/master/en/micro-integrator/docs/references/synapse-properties/inbound-endpoint-properties.md

Creating Custom Inbound doc[1] done.
[1] https://github.com/wso2/docs-ei/blob/master/en/micro-integrator/docs/develop/creating-artifacts/customizations/creating-custom-Inbound-endpoint.md


chore: brought in @codecademy/eslint-config for ESLint 8

Overview

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

🚀 Styleguide deploy preview ready!https://618c00f881faa90079a8d4e4--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://618c069853410f00ac5d97cb--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://618c1b2002d27f1a030f2d4b--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.13-alpha.6bb587.0@codecademy/gamut-labs@28.0.8-alpha.6bb587.0@codecademy/gamut@40.2.1-alpha.6bb587.0@codecademy/monaco@0.5.10-alpha.6bb587.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://618c1e4353410f16625d9bed--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.23-alpha.9e27d8.0@codecademy/gamut-labs@28.1.3-alpha.9e27d8.0@codecademy/gamut@40.5.2-alpha.9e27d8.0@codecademy/monaco@0.5.18-alpha.9e27d8.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61a6590e6d849745ce47ad36--gamut-preview.netlify.appDeploy Logs


IsVisible binding without a path is not applied

Describe the bug
A binding without a property path applied to IsVisible will not be evaluated. The control will remain visible when it should be hidden.
Adding a path of $self.DataContext works around the issue.
To Reproduce
Start Sandbox with this window XAML:
<Window xmlns="https://github.com/avaloniaui"
        xmlns:x='http://schemas.microsoft.com/winfx/2006/xaml'
        x:Class="Sandbox.MainWindow" x:CompileBindings="False">
  <StackPanel>
    <Border IsVisible="{Binding, Converter={x:Static ObjectConverters.IsNotNull}}" Height="19" Background="Red" />
    <Border IsVisible="{Binding $self.DataContext, Converter={x:Static ObjectConverters.IsNotNull}}" Height="19" Background="Green" />
  </StackPanel>
</Window>

You will see this:

Expected behavior
The Border with the red background should not be visible.
Avalonia version
11.2.1
OS
Windows
Additional context
Not reproducible in 11.1.x

AFAIK, objects can't notify for themselves, only their properties. Hence INotifyPropertyChanged. When you use {Binding} which has no path to a property, then you should think of this as a get-only property fetched only when the View itself demands it (ie. on object initialization for a Control or on command execution for CommandParameter). The binding system doesn't have access to a parent object and therefore won't be aware of when it changes.

Note that Avalonia has had a long-standing issue with changing DataContexts. I have several places in code where I needed to set a DataContext first to null then to the new view model instance. That is loosely related to the discussion above and I wonder if it might be fixed at the same time.


Add an additional workaround for QNAP + ZFS

Per my own investigation and workaround discovery, this appears to be a common bug for both Steam & games that try to query disk space and get back too-large numbers for free space.

@yostinso thank you for the PR! LGTM 🚢


Some problem about your re-impletation

GOOD WORK. But I have some Questions to ask you. First, I used your what you have said in the comment to train a new model, but I still found that the results are noisy.  Second I found that you just subtracted 120 per image, why did not subtract the mean value that VGG provided?

Yeah. I have the same question to ask.

@DavieHR @littlekobe  I think that doesn't make a lot of diference. This VGG mean is just around 120.

Excuse me, I found that both y and xc are subtracted by 120, but the style imge is not. Is there anything wrong when calculate L_style with feature_hat(subtracted by 120) and feature_s(not subtracted)?
@austingg @DavieHR

@yanhn you subtract 120 just before you feed it to VGG network. For the style it's subtracted by vgg.preprocess method :)

@cryptexis Thank you. Yes，you're right. My bad, I didn't read code carefully.


Performance Profile Results Interference and Incorrect Graphs in Meshery When Accessing Multiple Tests Simultaneously

Current Behavior
In meshery performance profile when multiple profile results are shown parallelly and try to access the selected performance test at once the other performance tests of the other profile are also selected simultaneously. and the comparison graphs are shown shame for the profile.
video reference:
https://layer5io.slack.com/files/U032JHR57EY/F05N9G141KK/screen_recording_2023-08-15_at_10.59.57_pm.mov
Expected Behavior
The Expected behavior is to show graphs for only selected tests and the other results of the performance should not be selected simultaneously.
Screenshots/Logs

Environment

Host OS: Mac Linux Windows
Platform: Docker or Kubernetes
Meshery Server Version: stable-v
Meshery Client Version: stable-v

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

pleasr assign me this issue

pleasr assign me this issue

Here you go @EraKin575

Hey @EraKin575, do we have any update on this issue ?


Additional features

Set an encoder for payload:
I got an error having too many badchars with Shikata Ga Nai:

Using alpha_mixed solved it:

Insert badchars as copied from Mona log + Auto-remove adjacent badchars

Insert ESP address as copied in Mona log

Support non-vulnerable inputs to send in advance (see brainstorm box for istance)

Using the modified script I was able to solve all the BOF boxes in:

Buffer Overflow Prep
Brainstorm
Gatekeeper
Brainpan 1

Apologize me for the bad code, I'm not a Python guru. Eventually feel free to refactor it

It would be helpful if you could provide selectable options for the encoders instead of writing the encoder names, as this could reduce the chances of user error.

That's correct, I'll manage to do it in the next days


fix(test): perf tests

This fixes the performance tests and runs them automatically in our travis build.

Noice.

uh wait, I think the tests are not green...

will look into the fix, seems to "works on my machine" :dancers:

Fixed in https://github.com/skatejs/build/pull/2 and ce0360f.


Remove filesystem imports

Remove Filesystem Imports
Attention: This is a breaking change! (Search below for the term API-CHange).
This MR changes the way miniflask imports modules.
Previously, miniflask would overwrite the python import-routine to allow module repositories in the whole filesystem.
This however, leads to a variety of problems, for instance harder to track errors in testing environments, instantiations of objects for relative imports compared to instantiations given through miniflask-routines, etc.
The solution to all this is to let miniflask determine the import paths that python would use for all module imports and use those for importing.
With this in place, renaming module-base directories internally, or, allowing filesystem-wide imports is not possible anymore.
Nevertheless I strongly believe that making miniflask mimic python's behavior for module naming is more natural and surely more future-proof with regards to understanding the internal behavior as a user and also for debugging for later developments.
*Note: Merging this PR closes #115 and closes #97.
Example
Consider the following directory-structure:
myproject (main project directory)
├── main.py
├── __init__.py
├── subpackage
│   ├── __init__.py
│   ├── usingminiflask.py (first file that uses miniflask)
│   ├── modules
│   │   ├── __init__.py
│   │   ├── module1/ (contents omitted)
│   │   ├── otherdir
│   │   │   ├── __init__.py
│   │   │   ├── module2/ (contents omitted)
....

Note that usingminiflask.py sits itself in a python package named subpackage. This is the actual file that calls mf.init in a way.
Considering usingminiflask.py, the accessible modules are called modules.module1 and modules.otherdir.module2.
Previously, the have been included by overwriting the python-internal importlib-spec objects as the packages modules.module1 and modules.otherdir.module2.
With this PR in place, their internal importnames are myproject.subpackage.modules.module1 and myproject.subpackage.modules.otherdir.module2, as myproject.subpackage is the actual python-prefix for all modules.
I am free to discuss whether these prefixes (myproject.subpackage) should be also added to the miniflask-ids, however, the current design decision is not to do that. In theory, such a change should be doable without breaking to much, however I am not yet sure to be honest. In theory some users might be depending on absolute paths to work. If for instance those do not rely on state.all, everything should be fine, though.

Things done in this MR
The core commit for this MR is probably 83f69641, where the true python import name of each module specification is determined and used to import a module.
There are other things that needed to be done to make this a complete function. Here in more detail:

API-Change: As filesystem-wide imports and renamings are not possible anymore, this MR removes the possibility to give mf.init a dict for initialization.
API-Change: We have allowed module names with a .. This is not possible anymore due to the requirement of being also python-import-compatible.
Refactored the module_spec["importname"] to be exactly the same as python's import-name for the respective modules, also for miniflask's pre-shipped modules.
Fixed a minor bug, where base-directory-modules would end with a ..
To make the tests work with pytest on every level, all tests needs to be a python-packages themselves.
I used the opportunity to normalize the folder-structure a bit.
Added some tests to show how to choose only some modules from a module repository.

Check all before creating this PR:

[x] Documentation adapted
[x] unit tests adapted / created

Pushes fix linter errors.
(For future da-h: Never think, it'll be ok).

For my comprehension: Does removing the filesystem imports completely removes the use of the deprecated load_module functionality?

Hey there, I have a slightly new take on this based on our discussion.
However, as it still feels to be hacky due to the requirement of getting the absolute identifier of the callees package, I have pushed this to a seperate branch, https://github.com/da-h/miniflask/tree/remove_filesystem_imports_new
Removing the hacky part i.e. emoving the relative import capability of modules is also possible, though it induces problems in all test scenarios.
Reason is that pytest adds the respective paths automatically to sys.path, effectively disabling a similar directory structure in different test-cases. To solve this without the "hack" one would have to add the package-prefix to the respetive tests to all test cases which would however disable the possibility to start just a subset of the tests using pytest.

Rebased onto v5-dev + replaced with the branch remove_filesystem_imports_new mentioned above.


Refactor/replace black flake8 with ruff

Issue
https://github.com/equinor/fmu-sumo/issues/358
Short description

[x] Enable Linting and formatting
[x] Perform Linting and formatting
[x] Create workflow for linting and formatting
[x] Set up pre-commit with hooks

Pre-review checklist

[x] Read through all changes. No redundant print() statements, commented-out code, or other remnants from the development. 👀
[x] Make sure tests pass after every commit. ✅
[x] New/refactored code is following same conventions as the rest of the code base. 🧬
[x] New/refactored code is tested. ⚙
[x] Documentation has been updated 🧾

Pre-merge checklist

[x] Commit history is consistent and clean. 👌

LGTM, but the change from Filters to filters in docs/explorer.rst are wrong, and should be reverted.

pep-8 recommends the use of snake_case for module names.
Since the naming of all the other files in the same folder is using snake_case I'll maintain that convention by renaming the file to filters.py


please push latest version to npm

please push the latest version to npm that uses array injection.

Done!


Add systemRequirements to workflow stage desc

In general, could you associate a Jira ticket with each PR? It makes it easier to know which feature/bug the change is related to. @jdidion


Add github.com/fxamacker/cbor in bench comparison

cbor encoding and decoding functions pass bench check.
cbor encoding and decoding benchmarks support ti (testUseIoEncDec)
and tc (testCanonical) flags.
BenchmarkXSuite, BenchmarkCodecXSuite, and BenchmarkCodecXGenSuite
include new benchmarks.
BenchmarkCodecAllCborSuite compares cbor encoding and decoding.

Sorry - just seeing this after I made some updates.
Can you please re-sync and resolve submit a new PR?
Thanks much for your contribution.

Hi,
Thanks for your response.
After I re-synced my repository, I ran into an import path checking error and reported it in issue #5.
I will submit a new pull request when the issue is closed.


Add support to print unsigned integers

Else numbers between INT_MAX and UINT_MAX will be printed using double format

Looks good, thanks!
This also fixes one of the issues from https://github.com/kgabis/parson/issues/53


[BEAM-2484] Add Python mobile gaming streaming examples

Hi @aaltay,
This adds leader_board.py and game_stats.py for streaming examples in the mobile game series.
It also removes the BigQuery output for both user_score.py and hourly_team_score.py to remove the GCP dependency as well as simplify the examples.

Coverage decreased (-0.03%) to 70.85% when pulling 1797c9dc78f2b955cac8cd2b79b9af911e546b95 on davidcavazos:python-streaming-examples into f75dfe711b357800762a93dc5059d9a19da9ee61 on apache:master.

Coverage decreased (-0.2%) to 70.691% when pulling 95d457e2ad40bb613cb8abda68903ad026f0cccd on davidcavazos:python-streaming-examples into f75dfe711b357800762a93dc5059d9a19da9ee61 on apache:master.

@davidcavazos is this ready for review again?

Not yet, I was still working on some changes, but I've been working in other samples for migration guides too. I'll make some time for this today and hopefully have it for review shortly.

I ended up removing the common module in favor of having every example self-contained. After reviewing for best practices in code samples, we discussed the following options:

Having each example completely self contained in one file
Having a "common" package and make this the standard way of including new files

Here's Jon Wayne's response:

Go with (1) with a separate sample for how to include custom packages. Code duplication is actually not a bad thing in samples, it re-enforces learning.
You can read about about my philosophy on samples https://github.com/GoogleCloudPlatform/python-docs-samples/blob/master/AUTHORING_GUIDE.md#the-sample-format

The juliaset sample already demonstrates how to create a custom import package.

Coverage decreased (-0.7%) to 70.155% when pulling 53a7649f7125df070b99d3a1f849aa8e9ca56542 on davidcavazos:python-streaming-examples into f75dfe711b357800762a93dc5059d9a19da9ee61 on apache:master.

@davidcavazos is this ready for review?

I still have to do more testing, but it shouldn't be too different from this. This is now ready for review (sorry for the delay)

This change generally looks good to me. I have not reviewed https://github.com/apache/beam/pull/3728 yet. If you want to remove the dependency we can test and try to merge this in. Otherwise it will happen after the review of the other PR.

This should now be ready

There is a linter error:
************* Module apache_beam.examples.complete.game.game_stats
C:224, 0: Wrong hanging indentation (remove 4 spaces).
            .as_singleton_view())
        |   ^ (bad-continuation)

You can run linter locally by running tox -e lint

Thanks, fixed it :)

Coverage increased (+0.003%) to 69.971% when pulling c14f86faea681260d8aced26a87d0774467047ed on davidcavazos:python-streaming-examples into d338b4412b9d7f26509afc293047dbdf85e17e61 on apache:master.

LGTM. I will merge this.
Please add unit tests for the 2 newly added examples, and update unit tests for the 2 existing examples. I will file a JIRA for you to track that.

Thank you again @davidcavazos
Please address https://issues.apache.org/jira/browse/BEAM-2797 as soon as possible for adding the unit tests.


Feature/issue 1036 fixed header

Closes https://github.com/gregnb/mui-datatables/issues/1036.
Add new options for fixed header
fixedHeaderOptions: { xAxis: boolean, yAxis: boolean }

allowing fine-grained control over which axes are fixed. Also deprecate the old option and update documentation accordingly.

Coverage decreased (-0.3%) to 77.021% when pulling dc705d9506090a065d9b238f81fa454f514a46b9 on feature/issue-1036-fixed-header into 2d37c383beeebb039fae2b6e0b531ddb7959e2ce on master.


Add Trackers from Details

Implement the Add Tracker in torrent details

Code implemented, but it was disabled from the action menu until fixing the dialog that is not working in torrent detail fragment


Compilation fails with current Makefile

Hi,
Wanted to report that with current versions of sedlex (at least on my machine) compilation will not work unless the Makefile line is changed from:
OCAMLBUILD_FLAGS = -j 4 -cflags -w,+a-4-27-29-50,"-warn-error +a" -lib unix -use-ocamlfind -pkg menhirLib -pkg sedlex

to
OCAMLBUILD_FLAGS = -j 4 -cflags -w,+a-4-27-29-50,"-warn-error +a" -lib unix -use-ocamlfind -pkg menhirLib -pkg sedlex.ppx

Yeah, I know of the problem, it's causing trouble in a couple of other repositories. I am still looking for a stable solution. Do you know which versio of sedlex switched from sedlex to sedlex.ppx?

Sadly no. Was just trying to compile your implementation and eventually found the fix.


disp_prop_was_rw is getting raw_prop

vm1b will have some workarounds for now

the bug is that v4l_control_scroll implemented raw_prop_write() instead of _raw_prop_write. names are a bit confusing maybe should change them

fixed


extra examples + script suite + reorg folders

@ElliotFriedman I am having trouble setting the bytecode through etch. Do you have any idea why the hash output its different from the one I set?
	address multisig = suite.addresses().getAddress("DEV_MULTISIG");
	console.log("Multisig bytecode beforing doing etch:");
	bytes32 bytecodeHash = getByteCodeHash(multisig);
	console.logBytes32(bytecodeHash);
	vm.etch(multisig, hex"b89c1b3bdf2cf8827818646bce9a8f6e372885f8c55e5c07acbd307cb133b000");

Multisig bytecode beforing doing etch:
  0x0000000000000000000000000000000000000000000000000000000000000000
  Multisig bytecode after doing etch:
  0xd37f85a776fb3981f4db9d01f44920e3b008ce5bd34587f9f9699fc7bff23f24

@ElliotFriedman, for some reason, the hash generated from the bytecode from etherscan doesn't match the hash you put here. Will keep investigating tomorrow
    function getGnosisSafeByteCode() public returns(bytes memory) {
	string memory bytecode = "0x608060405273ffffffffffffffffffffffffffffffffffffffff600054167fa619486e0000000000000000000000000000000000000000000000000000000060003514156050578060005260206000f35b3660008037600080366000845af43d6000803e60008114156070573d6000fd5b3d6000f3fea2646970667358221220d1429297349653a4918076d650332de1a1068c5f3e07c5c82360c277770b955264736f6c63430007060033";

	return bytes(bytecode);
    }

	bytes32 bytecodeHash = getByteCodeHash(multisig);
	console.logBytes32(bytecodeHash);
	vm.etch(multisig, getGnosisSafeByteCode());

Multisig bytecode beforing doing etch:
0x0000000000000000000000000000000000000000000000000000000000000000
Multisig bytecode after doing etch:
0x9f3881b66dc519f01e1bda292342742c64e352b8bc913e409e99a3c259473474

@ElliotFriedman, we can't use Safe execTransaction as it requires signatures. So what I did was to call multicall directly after pranking multisig address (see last commit). Do you think the library should still validate the bytecode hash now that we are no longer using Safe to simulate the transaction?

@ElliotFriedman, if we check that the address that is supposed to be a multisig is a gnosis safe, we won't be able to test multiple proposals simultaneously. This is because after the first proposal, the multisig bytecode changes to the multicall due to the etch inside _simulateActions.


User-Role mapping in security should be case-insensitive for usernames

Current behavior - User - Role mapping is case sensitive. If I map user test1 with role all_access
Then is user Test1 login which is same user as test1 but since the user - role mapping is for user test1 instead of Test1 it doesn't get the access.
Expected behavior - User - Role mapping becomes case insensitive.

This is as per design, We will treat username with different case as unique.


Trace: Flat Profile

adds flat profile functionality for specified inc/exc metrics

We can make it more complex later by allowing flat profile per process and not doing the second group by.


Translation: German

Repository: https://github.com/jens1o/de-opensource.guide
Preview: https://jens1o.github.io/de-opensource.guide/
Locale: de-DE
On the gh-pages branch of your fork:

[X] Merge the i18n branch into gh-pages and push the branch to your fork. This should build the website and it should be visible at the preview url above.
[x] Update title, description, and locale in _config.yml
[x] Copy _data/locale/en-US.yml to a new file with the name of your locale and translate the strings
[ ] Create a new directory in _articles/ for your locale and translate each guide:

[ ] best-practices.md
[ ] building-community.md
[ ] code-of-conduct.md
[ ] finding-users.md
[ ] getting-paid.md
[ ] how-to-contribute.md
[ ] leadership-and-governance.md
[ ] legal.md
[ ] metrics.md
[ ] starting-a-project.md

[ ] ??? TODO - other steps here
[ ] Update CNAME to include your locale (e.g. de.opensource.guide)

Once a translation is completed:

[ ] Open a Pull Request on the upstream repository to add your fork to translations in _config.yml

I have a tiny problem:
When I push changes, I can see them on GitHub, but they won't be shown on the website...

Hi @jens1o, thanks for getting started on a German translation! I'll defer to @bkeepers to tackle your qs.

Thanks. :) I fixed the problem by remove the _articles/en-US folder with its content, now it works. :)

nope ;)
I just lack of time unfortunately :/

https://github.com/jens1o/de-opensource.guide/commit/afda47d62661acf81032a173258b81118cff7306
Best-Practices is finished!

Starting a project is finished, too

@jens1o Apologies this issue has been neglected for so long. I've merged the first translation to this repository (Spanish) and updated the documentation on the latest translations approach (https://github.com/github/opensource.guide/blob/gh-pages/docs/translations.md). Please submit a pull request when you have translated all articles and checked ./script/test passes and I'll get it merged in ASAP. Thanks!

@MikeMcQuaid Alright, thanks.

Hi @jens1o! I wanted to start translating according to the new site structure as well. Do you still have the repo so I can contribute there? Or shall I invite you to mine? Or @MikeMcQuaid can we both get write access to a de branch here?

@katrinleinweber Could you invite me to yours please? I've deleted mine, since it was out-of-date.

People don't want backup, people want restore ;-)
No worries! I pushed a draft translation of best-practices. Please feel free to rewrite it and force-push to remove the WIP in the commit message. But only there, please ;-)
I will also stop force-pushing now.
Once I am finished with metrics, how about we start indicating which article we are working on by starting a branch named de-filename and a PR against de in my repo, so #577 grows whenever a new file is complete?

Sounds good :)

People don't want backup, people want restore ;-)
No worries! I pushed a draft translation of best-practices. Please feel free to rewrite it and force-push to remove the WIP in the commit message. But only there, please ;-) I too will stop force-pushing now.
Once I am finished with metrics, how about we start indicating which article we are working on by starting a branch named de-filename and a PR against de in my repo, so #577 grows whenever a new file is complete?


fix: modal visibility on safari 15.3

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


Unify formatting via clang-format

clang-format is a promising tool, since it's based on a real compiler infrastructure. It will grow and options will change, but it's already usable in its form already. I'd suggest the style in a commit and will reformat everything after some time if no objections come up. git clang-format can be used later as a pre-commit hook

no need for that at the moment


Add tool to scrap and mirror and existing website structure

Out of scope for this project at the moment.


Register and unregister fcm Tokens on sign in and sign out

Describe your changes
I implemented the feature to register and unregister FCM tokens upon login and sign out.
Changes:

Used the firebase messaging dependency and connect to our firebase fireapp project using flutter firebase CLI
Created token class payload
Some code to initialise the firebase class on start up in main.dart
The rest all the logic code to handle register and unregister code on log in and sign out

Hi @BenMMcLean, it seems like the build process just failed because I added new dependencies: Firebase Messaging and Firebase Core. I did include them in the pubspec.yaml, and it works on my local machine, but it may not be working here. Could you give me some advice on what I should do about this? Thank you!

Hi @BenMMcLean,
I have implemented the changes you requested. I apologise for the earlier mistakes. I tend to have a bad habit of reformatting code after writing it.
I have tested both the sign-in and sign-out functionalities. The sign-in works well, but when I try to sign out, the backend receives the DELETE HTTP request but responds with an unauthorized (401) status. I’m currently investigating this issue, but it’s quite challenging. If you have any insights, please let me know!
Thank you so much!

@TaiHaDev I cannot provide advice because it appears that you have failed to push a significant chunk of your files, most notably in this case, the SettingViewModel. I do suspect your problems with DELETE are caused by a common mistake, but I would prefer not to speculate and mislead you. Please push all your work and I'll advise from there.

I am so sorry for the inconvenience. Somehow, it wasn't automatically added to version control. I have pushed all the necessary files. Thank you!

I created a new exception folder because I couldn't find an existing one. I am also trying to research how to implement navigation using the LoginViewModel.

Hi Ben, I have updated the class and variable names to follow the convention. it looks better now. Thank you!

Hi @BenMMcLean, I tried to merge and push, but it didn't pass the pipeline. I realized this happened because I didn't push the firebase_options.dart file. I didn't push it initially because it is generated by the FlutterFire CLI and contains the API key and related information to connect to our Firebase project.
I read some Git issues, and they mentioned that it's generally okay to push it since it's not considered vulnerable, so I pushed it to pass the pipeline. Please let me know if this is not okay. Thanks a lot!

❌ loading /home/runner/work/mobile/mobile/fireapp/test/presentation/login/login_viewmodel_test.dart (failed)
There's an error like this within the unit test pipeline. I don't think there's a file like that yet so it failed.

I really appreciate all of your feedback on this pull request. I learned a lot from it, especially about git versioning, and I realized how careless I have been with these changes due to my lack of experience. Thank you so much for your patience and help 🙏


use links instead of plain text

Pull Request
What does this PR do?

changes text urls into valid javadoc urls (makes them clickable, within javadoc and IDE, like Intellij)

@singlyfy thanks for the PR
Can you fix the tests (linter and integration/unit tests)? cf the CI

bors try

Hi @singlyfy can you check this conflicts?

Closing for lack of activity


Remove ImportError if sys.platform is not Linux.

I would like to use the distro module for a more abstract use-case by sub-classing the LinuxDistribution and replacing the _get_*_release_info() methods with my own custom methods. However there is currently a check against sys.platform at the top of the file which prevents this abstract code from running in a non-Linux platform, which is required for the project that I am currently working on.
I would really prefer to not vendor the module and make changes myself to make sure that future improvements do not require me to re-implement my vendored module. Plus it will make any improvements I would like in the module to be done in upstream rather than my own in-project fork. :)
Is there any way this error could be removed? I realize this would probably require a major version tick which is a shame. :/
It's fine to close this issue if it's something you won't do, I understand. :) I will still contribute back any improvements I make to this repository.

I'll have to think this through. Just wondering. Can't you just do something like
try:
    current_platform = sys.platform
    sys.platform = 'linux'
    import distro
finally:
    sys.platform = current_platform

Let's think about an implementation together that will allow people to do what you're looking to do but not require removing this (probably by allowing people to ignore this check, which will still be done by default.)

That's true I can do something like that. :) I'll stick with that for now.
I'm fine with keeping the module as-is, figured I'd just quickly ask before doing a little hack haha :)

Alright. I'll close this. If it's still an issue for some reason, i'll reopen it.


Fix #23: Make the creation of Strategy's also be autoloadable

by running the filter underscoreToCamelCase on the tablename before creating the class and saving it.

Just merged your PR. Sorry for the delay.


Panic when running hello-cube example

Hi. I'm running into the following issue on the current master (47fa1a9a42aaea442d8b359ae80de4a991fd41f5).
➜  harmony git:(master) cargo run --example hello-cube
   Compiling harmony v0.1.0 (/home/marek/dev/harmony)
    Finished dev [unoptimized + debuginfo] target(s) in 11.36s
     Running `target/debug/examples/hello-cube`
[2020-04-26T11:04:11Z WARN  gfx_backend_vulkan] Unable to find extension: VK_KHR_wayland_surface
[2020-04-26T11:04:11Z WARN  gfx_backend_vulkan] Unable to find layer: VK_LAYER_LUNARG_standard_validation
[2020-04-26T11:04:11Z WARN  wgpu_core::device] Requested size 1024x768 is outside of the supported range: Extent2D { width: 1914, height: 1151 }..=Extent2D { width: 1914, height: 1151 }
[2020-04-26T11:04:19Z WARN  gfx_memory::heaps] Unable to allocate 134217728 with Linear: TooManyObjects
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `Extent { width: 1024, height: 768, depth: 1 }`,
 right: `Extent { width: 1914, height: 1151, depth: 1 }`', <::std::macros::panic macros>:5:6
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Removing the resize method from hello-cube.rs fixes the panic and I can see a nice example with rotating cube.

Hi, thanks for the issue report. Looks like it might be either an issue with how I am using DPI settings on resize or something internal to wgpu:
https://github.com/gfx-rs/wgpu-rs/issues/24

        let mut camera_data = CameraData::new_perspective(
            70.0,
            actual_window_size.width,

Maybe not directly related: The new_perspective fn actually wants Radians. We need to convert .to_radians() before passing it.  Perhaps you changed the fov and it crashed?

Thanks for the hints, both of you, I'll try debugging this later today.
Btw, yes, I am on Linux. Would posting some additional traces help?

The issue goes away on the latest master (84969b8aa61d9b40bd18afee29e33dcc324637e0).
So I guess it was a wgpu bug.

Closing this as it appears to be fixed.


overpass font

Added TTF files for Overpass font (with license), imported them to the panel SCAD file, and changed the default text to Overpass Bold.

This looks good. Thanks!


Some of these drivers are on 🔥

Hi,
I was introduced to this project yesterday and began some tests to see how they perform against Windows Defender Application Control policies and Microsoft Defender, here are my findings:
Part 1: Malicious files
One of the main problems is using the phrase Living Off The Land, which are supposed to be legitimate non-malicious files that can be misused to circumvent security solutions, but what I'm seeing is straight up malware that Microsoft Defender already detects and blocks.
So, to prevent redundancy, I suggest removing those files from the driver package and instead let default security solution take care of them.
For the rest of the files, there is automatic sample submission and the global MAPS and ISG networks that get notified about these files every time they are run.
Part 2: Non-Malicious files
These are another story. I couldn't find a clear reason for each file as to why it's labeled as LOLDriver.
The questions I'd have in mind (and most likely businesses/enterprises too) about each file is:

What role does it play in circumventing security measures?
Does it help bypass WDAC? (If so, it should be reported to Microsoft as well to be added to the official recommended block rules)
Is there a PoC for it bypassing security measures?
Does Smart App Control (that uses Intelligent Secure Graph) block them?
Are some of these drivers also included in Microsoft recommended driver block rules? (to prevent duplication when merging with a WDAC policy)

Microsoft Defender results after running all of the driver files, these are the ones I was referring to that are redundant:
RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 27
DidThreatExecute : False
IsActive         : True
Resources        :
RollupStatus     : 1
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 1
ThreatID         : 226944
ThreatName       : PUA:Win32/Kuping
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 27
DidThreatExecute : False
IsActive         : True
Resources        :
RollupStatus     : 1
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 1
ThreatID         : 227008
ThreatName       : PUA:Win32/GameBox
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 27
DidThreatExecute : False
IsActive         : True
Resources        :
RollupStatus     : 1
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 1
ThreatID         : 242420
ThreatName       : PUA:Win32/Presenoker
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 27
DidThreatExecute : False
IsActive         : True
Resources        :
RollupStatus     : 1
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 1
ThreatID         : 311991
ThreatName       : PUADlManager:Win32/InstallCore
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 34
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 65
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : VirTool:WinNT/Rootkitdrv.HK
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 34
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 65
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : VirTool:WinNT/Exforel.A
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 8
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 65
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : Trojan:Win32/Ditertag.A
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 34
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 65
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 4
ThreatID         :<PHONE_NUMBER>
ThreatName       : HackTool:Win64/CapRoot.A
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 8
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 65
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : Trojan:Win32/Wacatac.B!ml
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 8
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 65
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : Trojan:Win32/RootkitDrv!MSR
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 8
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 65
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : Trojan:Win32/Rootkit!MSR
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 8
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 97
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : Trojan:Win32/Tnega!MSR
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 8
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 65
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : Trojan:Win64/Tnega!MSR
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 8
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 97
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : Trojan:Win64/RootkitDrv!MSR
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 8
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 65
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : Trojan:Win64/Rootkit!MSR
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 8
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 97
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : Trojan:Win32/Wacatac.H!ml
TypeID           : 0

RunspaceId       : bca4d8af-c8df-4bf6-b486-9cfc82918041
CategoryID       : 8
DidThreatExecute : True
IsActive         : False
Resources        :
RollupStatus     : 65
SchemaVersion    : <IP_ADDRESS>
SeverityID       : 5
ThreatID         :<PHONE_NUMBER>
ThreatName       : Trojan:Win64/BlackLotus!MSR
TypeID           : 0

The following drivers are blocked when Default Windows WDAC policy is deployed, A total of 431 drivers:
Download file: 👇👇
Blocked by Default Windows Policy.md

The script i used to automate the tests
Execution
$i = 0
(Get-ChildItem "C:\Users\Admin\Desktop\drivers").FullName | ForEach-Object {
New-Service -BinaryPathName $_ -Name "DriverTest$i" -Description $_ -StartupType Manual
Start-Service -Name "DriverTest$i" -ErrorAction SilentlyContinue
$i++
}

Increase Code Integrity Operational log size
$logName = 'Microsoft-Windows-CodeIntegrity/Operational'
$log = New-Object System.Diagnostics.Eventing.Reader.EventLogConfiguration $logName
$log.MaximumSizeInBytes = '50000000'
$log.IsEnabled = $true
$log.SaveChanges()

Logs gathering
$ScriptBlock = {
# Event Viewer Code Integrity logs scan
foreach ($event in Get-WinEvent -FilterHashtable @{LogName = 'Microsoft-Windows-CodeIntegrity/Operational'; ID = 3077 } -ErrorAction SilentlyContinue ) {
    $xml = [xml]$event.toxml()
    $xml.event.eventdata.data | ForEach-Object { $hash = @{} } { $hash[$_.name] = $_.'#text' } { [pscustomobject]$hash } |
    Select-Object -Property 'SHA256 Hash' , 'File Name', 'OriginalFileName', 'ProductName', 'InternalName', 'FileDescription', 'FileVersion', 'SHA1 Hash', 'USN'
}
}
$Results = Invoke-Command -ScriptBlock $ScriptBlock
$Results
$Results | clip
Write-Host "A total of $($results.count) drivers have been blocked"

Thank you for this @HotCakeX ! I'm going to close this, but that does not mean it is irrelevant. Really appreciate the share.


Dendron Open Log

Please select the area your Bug applys to. (Multiple selections are Possible)

[ ] UI
[x] Workbench
[ ] Publishing
[ ] Pods
[ ] Markdown
[ ] Hierarchy
[ ] Graph
[ ] Misc (Choose this if your not sure)

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

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information)

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
Dendron Log file
Please attach the output of >Dev:Dendron: Open Logs here

Did you have any particular issue in mind?

After I install Dendron, when i want to initalize dendron workspace, an error shows up saying this:
something went wrong. please submit a bug report to https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=bug_report.md&title= with the output of Dendron: Open Log

@Erza123 - could you run the Dendron: Open Log command and attach the output to this issue? You should be able to get it via the VS Code command bar (Cmd/Ctrl + Shift + P) and then typing in "Dendron: Open Log".


install package only if service is down

Install package only if specific service is down in Linux
Describe the problem
Using chef, I would like to install a package only if a specific service is down and here is my code block:
package 'Install my pkg' do
      package_name 'my-pkg'
      action :install
      not_if "sudo systemctl is-active -q <service-name>
end

The return code when service is down is 3, and 0 when it is up.
Using the logic, the package is not getting installed even though the service is down.
Software Version
Chef version: 12.22.5

solved it myself.


Sort parent taxons before selecting the first

This commit makes sure parent taxons are sorted alphabetically by title
before we select the first one to use. This is for consistency reasons
until we have a way of modelling parent taxons.
Trello: https://trello.com/c/RLWfiG6N/481-make-breadcrumb-use-1st-alphabetic-topic

LGTM 🚢


Crashed with beta4 and beta6

Crashed with beta4 and beta6.
Example of request:
let requestOptions = PHImageRequestOptions()
requestOptions.sd_targetSize = targetSize
requestOptions.sd_contentMode = .aspectFill
requestOptions.isNetworkAccessAllowed = true

if let url = NSURL.sd_URL(with: asset) as URL? {
sd_setImage(with: url,
         placeholderImage: nil,
         context: [.photosImageRequestOptions: requestOptions,
                        .customManager: SDWebImagePhotosLoader.shared])
} else {
    sd_cancelCurrentImageLoad()
    image = nil
}

Get this crash:

@brightsider The reproduce rate ? Always or some special use case cause the problem ? I'll try to investigate and provide a fix

Seems a usage issue....
.customManager: SDWebImagePhotosLoader.shared])

Don't do this. The customManager is a SDWebImageManager class instance. It's not a SDImageLoaderProtocol....
You should write code like this:
let manager = SDWebImageManager(cache: SDImageCache.shared loader:SDImagePhotosLoader.shared) // Here !

sd_setImage(with: url,
         placeholderImage: nil,
         context: [.photosImageRequestOptions: requestOptions,
                        .customManager: SDWebImagePhotosLoader.shared])

I guess, maybe this because of the SDWebImageManager and id<SDImageLoader> have the same Selector naming, cause a misunderstanding. I'll try to ask to rename this and to avoid the developer mistake about this.
// This is `SDWebImageManager` instance method
- (nullable id<SDWebImageOperation>)loadImageWithURL:(nullable NSURL *)url
                                             options:(SDWebImageOptions)options
                                             context:(nullable SDWebImageContext *)context
                                            progress:(nullable SDImageLoaderProgressBlock)progressBlock
                                           completed:(nullable SDImageLoaderCompletedBlock)completedBlock;

// This is `SDImageLoader` protocol method, looks same on selector, but not the same args
- (nullable SDWebImageCombinedOperation *)loadImageWithURL:(nullable NSURL *)url
                                                   options:(SDWebImageOptions)options
                                                   context:(nullable SDWebImageContext *)context
                                                  progress:(nullable SDImageLoaderProgressBlock)progressBlock
                                                 completed:(nonnull SDInternalCompletionBlock)completedBlock;

Reproduce always.
In AppDelegate I'm setting up this:
SDImageLoadersManager.shared.loaders = [SDWebImageDownloader.shared, SDWebImagePhotosLoader.shared]
SDWebImageManager.defaultImageLoader = SDImageLoadersManager.shared

@brightsider If you already setup to use the code above. Actually, you don't need any customManager args.
SDImageLoadersManager.shared.loaders = [SDWebImageDownloader.shared, SDWebImagePhotosLoader.shared]
SDWebImageManager.defaultImageLoader = SDImageLoadersManager.shared

@dreampiggy removed customManager and crashes stopped. Thanks!


Adding Flask cheatsheet to compliment Python Web Framework resources

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Corrected spacing between subheading and resource link

Found the space I was missing and this is ready for merge. Thanks!

Go team


Unhandled exception when using an icon as a resource

Describe the bug
When setting an FontIcon or SymbolIcon as resource in App.xaml and using it, on an AppBarButton for example, I get an unhandled exception
Steps to reproduce the bug
<FontIcon x:Key="MyIcon"
          Glyph=""/>

<AppBarButton Height="50"
              Width="50"
              Icon="{StaticResource MyIcon}"/>

Expected behavior
I'm not sure if this is intended or a bug. It does feel like we should be able to do this.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.5.2: 1.5.240404000
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

Documented as not supported:
https://learn.microsoft.com/en-us/windows/apps/design/style/xaml-resource-dictionary#xaml-resources-must-be-shareable

XAML resources must be shareable
For an object to exist in a ResourceDictionary, that object must be shareable.

Being shareable is required because, when the object tree of an app is constructed and used at run time, objects cannot exist at multiple locations in the tree. Internally, the resource system creates copies of resource values to use in the object graph of your app when each XAML resource is requested.

A ResourceDictionary and Windows Runtime XAML in general supports these objects for shareable usage:

Styles and templates (Style and classes derived from FrameworkTemplate)
Brushes and colors (classes derived from Brush, and Color values)
Animation types including Storyboard
Transforms (classes derived from GeneralTransform)
Matrix and Matrix3D
Point values
Certain other UI-related structures such as Thickness and CornerRadius
XAML intrinsic data types

That's unfortunate. Thanks for the link!


Support newer versions of React than 0.12.x

Update the peerDependencies to support any version of React greater than 0.12.0

I'll have a look into this to see what changes are needed to get it working with 0.13.

Thanks for looking into this @ultrafez

Hey it turns out jsdom stopped supporting node.js so I'm using 3.x in devDependencies in afb4495afff921d752d8d05d8fea4151740c452e.

Ah, it was a simple fix! Great stuff - look forward to using this in a project I'm currently working on :)

Would you consider publishing a new version of react-highlighter with the 0.13.x support, so I can pull it down from npm instead of directly from GitHub?

@ultrafez just published<EMAIL_ADDRESS>– should have done this a week ago, sorry!


Add some jupyter examples to the docs

We probably want two sets of jupyter examples showing off some of the convenience functions, one without girder and one with.
The one without girder would show off some convenience methods:
!pip install large_image[sources] --find-links=https://girder.github.io/large_image_wheels
!curl "https://data.kitware.com/api/v1/file/5fdcf3dd2fa25629b99e0a9e/download" -o sample.svs
import large_image
ts = large_image.open('sample.svs')
ts
ts.metadata
ts.getThumbnail()[0]
large_image.tilesource.jupyter.IPyLeafletMixin.JUPYTER_PROXY = True
ts

And one with girder:
import girder_client, large_image, numpy as np, pickle
gc = girder_client.GirderClient(apiUrl='https://<server>/api/v1')
resource = '/collection/TCGA/single/TCGA-DX-A6BG-01Z-00-DX2.34763958-0613-4069-9ACC-13D6633FE415.svs'
itemId = gc.get('resource/lookup', parameters={'path': resource})['_id']
metadata = gc.get(f'item/{itemId}/tiles')
metadata
tileUrl = gc.urlBase + f'item/{itemId}/tiles' + '/zxy/{z}/{x}/{y}'
regionUrl = gc.urlBase + f'item/{itemId}/tiles/region?encoding=pickle'
thumbUrl = gc.urlBase + f'item/{itemId}/tiles/thumbnail?encoding=pickle'
pickle.loads(requests.get(thumbUrl).content)
# TODO: get thumbnail image, get actual region, show ipyleaflet layer

We can't use colab to render the first item fully, since the proxy doesn't work in colab.

Added in #1281.


chore(deps): update node.js to version 10.4.1

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines

Description of change

https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.4.1

backported to rel-5-1-patches as 96a7f089d43c01babd97b982cbe6a31b732902fe


issue with phalanges orientations

could come from the aimconst of the guides or the jointorients or the ctrls rotations value

solved by using the same normalConstraint method used on the leg script


Consider switching to testdouble.js for mocking

testdouble.js has a nicer API and is more stable and plays more nicely with newer JS developments. Sinon has also been working on 2.0.0 for 10 months now, and this morning our build was broken because we depend on the 2.0.0 prerelease version and a breaking change was made overnight.

http://blog.testdouble.com/posts/2016-03-13-testdouble-vs-sinon.html

They have an article on testdouble versus sinon.

hehe

Related: https://github.com/linode/manager/issues/1677


Timeout is too short on WALA-VERIFY-HOSTNAME-CHANGE

https://github.com/microsoft/lisa/blob/b2e814376e62b20f2bbb69078a3d27beacce9162/Testscripts/Linux/WALA-VERIFY-HOSTNAME-CHANGE.py#L69
Recent test failed because the operation took 50 milliseconds longer than the timeout, I'd like to increase this to 300 or poll a few times to give it a longer timeout without increasing the test duration.

opened PR https://github.com/microsoft/lisa/pull/1480

merged PR, closing issue


Vulnerability roundup 76: libvorbis-1.3.6: 1 advisory

search, files

[ ] CVE-2018-10393 (nixos-19.09)

Scanned versions: nixos-19.09: e34ac949d1b. May contain false positives.

I think this is a dup of CVE-2017-14160 which we already have patched. I've requested clarification on upstream's bug tracker.

CVE-2018-10393: Upstream developer Ralph Giles has confirmed that this is a duplicate of CVE-2017-14160.
Fixed upstream at 018ca26d, released as version 1.3.7.
Patched by nixpkgs at 15b14324, included in nixos-20.03, nixos-20.09 and nixos-unstable.
See also a follow-up upstream commit a9eb99a5.

Sounds good, so we can consider this specific one as done. Updating libvorbis to 1.3.7 on master anyway.
@omasanori Thank you again for your super-accurate analysis. This is really helpful.


Question: Costs for downloading items from cloud storage?

The information on network pricing suggests, that outgoing network traffic costs (for NA-NA, EU-Eu as an example) ~0.1$ per GiB.
I'm wondering if that also applies to downloading from cloud storage via the official library?
I intend to use cloud run to render videos created by users (via ffmpeg and pupeteer).
These videos can contain custom assets, like further videos, from my current understanding I would have to download all of these assets on each render call, even if only minimal changes where made. This could become extremely costly, especially since cloud run instances only offer 2gb memory at most.
Is my understanding correct, and is compute engine a viable alternative?

https://cloud.google.com/run/pricing is the place to look. No ingress charges for Cloud Run as far as I can tell. We are working on more flexible Cloud Run runtimes (cpu/memory) so stay tuned.

Hm, well I looked at https://cloud.google.com/run/pricing, and it refers to the the premium pricing page, which states that outgoing traffic consts ~0.1$ per GiB.
I don't quite understand what you mean by 'ingress chargs for cloud run', do you refer to the costs of booting the instances up (installing dependencies etc)?

Ingress and egress are usually well-established in hosting or cloud industry.

ingress costs: what your app downloads
egress costs: traffic your app serves to users (upload)

Usually ingress isn’t charged, as most apps rely on serving traffic to users. Hope this helps.

Thanks for the detailed answer, it really helps a lot!
Thinking about it, it would be quite ridiculous to charge for ingress costs, as event the most basic webserver has to download loads ob mb in dependencies.


Bootstrap navbar?

Why doesn't the site use Bootstrap's navbar? It's nice and responsive. It makes it easy to fix it to the top, which I think would be nice since many of the pages under /docs are rather long.
I'm sure we can style it to look like the current custom navbar.

The reason is historical. Initially, not all apps were using bootstrap. We started with a common navbar between all apps and sites (cukes.info, cucumber.pro, legacy app, modern, etc.) and couldn't use bootstrap at that time. Now that all pages are based on bootstrap 3, we can switch to its navbar.
TL;DR: +1.

The switch has been made! 146d2f3


[LMS-113] LMS Data Store initialization

Changes

Replaces "FIZZ" with "LMS" or "LMS Toolkit" as appropriate throughout the repository.
Automates installation of User and staging-User tables in both PostgreSQL and SQL Server. NOTE: I did not use either YoYo or Alembic, two Python libraries for database migrations, because they were too heavyweight for our needs and/or do not have good SQL Server support.
Modified the command line interface to align with other applications.
And made a few modifications in preparation for publishing.
Readme updates.
Removed the lms-ds-installer package, which is no longer needed as a separate utility.

Problems

The upload of a 50,000-student user file crashes. I will create a separate ticket to deal with that.
I will also create tickets for publishing and for additional refactoring to match current coding and testing standards.

I see the readme for lms-ds-loader less detailed than the ones for the extractors, which in some way makes sense, because of this is probably not going to be consumed by a BA...

While I made some updates to the readme, I didn't try to tackle it completely in this ticket as I was trying to keep the scope of work constrained. It does need continuous improvement as we work on other tickets - which means we should "improvement of readme" to several tickets' acceptance criteria.

Should we make a distinction? I mean, even when only the extractors are going to be consumed by BA, this lms-ds-loader directory is in the same folder, so it could be a confussion for the non-developer visitors, who could get to this readme and think that the instructions are not user friendly...
My sugestion would be to separate non-extractor projects in a separated folder, or at least make sure that the general readme specifies that there are some projects intended for BA and other for devs.

I understand where you are coming from, but I don't make any distinction between them. The Jupyter notebooks should be the primary source for helping a BA get up and running. Which reminds me that I have been meaning to create a ticket around that. Thus I would prefer to keep them all together, and continue improving the documentation in the repository and in Tech Docs (a BA - as opposed to a developer - might spend more time in Tech Docs initially).


error when deploy on production env

Issue description

version #4.8.0
components: Modal
i dont know why, on development env it ok, but on production is not

Steps to reproduce issue

goto my link and click to CTA button: https://beta.jamja.vn/khuyen-mai/bedding-gallery-0/thu-sms-moi-config-0
login modal will open but it dont add show class

Personal website references are not helpful. You can create a jsbin/webpackbin with exact source code that shows the problem in detail. Most likely, if it's working in development, but not production, the error is on your side.  Close/non-issue.

It appears that you are using react-transition-group 2.x (based on inspecting the compiled code) which is currently not supported.
Depending on how you create your production assets, you may have react-transition-group 1.x locally but react-transition-group 2.x gets installed on your build server when creating the production assets.
What does your package.json have for react-transition-group and what version do you have locally (npm info react-transition-group version)?

@TheSharpieOne thank you


Close calendar when clicking on date

The previous version closed the calendar automatically after picking a date.  The new version (2.0.0-beta) has a Cancel and Done menu selection which you have to click on to close the calendar.
Is there an option to close the calendar immediately upon clicking on the selected date (instead of having to choose "Done")?

https://github.com/HsuanXyz/ion2-calendar/releases/tag/2.0.0-beta.3

Very good...thank you for adding this functionality back in!

thanks, very welcome. would be good to add the autoDone option to the API documentation


Create 0000-01-02-Laerozzo.md

created a branch, created a file and made a commit, and opened a pull request


Keeping pressing F5 will get debugging unusable at some point

Fix ready on my local.

Related to #97 ?


Account for errors in statistics calculation (Issue #3).

Description
Fix issue #3
Todos

[ ] Account for errors in experimental and predicted samples when calculating the statistics

Questions

[ ] Bootstrap not based on perturbations (edges) but on ligands (nodes). Is this done already correctly?

Status

[ ] Ready to go

This looks good to me.
I see what you mean about bootstrapping based on edges, rather than nodes. The way this is currently done is correct for the plot_all_DDGs but not plot_DDGs. This function should do the same irrespective of the plot --- just take x, y, xerr and yerr.
I can make this change today!


SG updated to v4.0.41 && PeptideShaker updated to v2.0.33

PeptideShaker bugfix managing searchgui files with different parameter name than the previously fixed one.
Last updates on SG application and Conda package have fixed diverse errors running DirectTag, MsAmanda, Myrimatch and OMSSA.
Many other minor updates.
Last MsAmanda versions are based on .NET Core, and some issues generating bundles with .NET Core 5 for macosx have caused errors leading to remove it from the Conda package for macosx until .NET Core 6 has been released.

@CarlosHorro should we wait for you other package?

@CarlosHorro should we wait for you other package?

Hi @bgruening , well, the metamorpheus test was failing because of an internal exception in current metamorpheus executable in the Conda package. I am still working on the last PR of the bioconda package, which already contains the bugfix, but I want to include there the MSAmanda bugfix too. When that Conda package is released and this tool uses it, we can merge this PR...

Wuhu!!!! Thanks for this amazing effort!


extending simple ABCI tests

Proposed changes
We had no catch up behaviour test for the simple ABCI skill. Currently I am debugging the Tendermint issue we have with catchup behaviour, for which this test is useful as opposed to having to run a more complicated application.
I have also implemented tests with multiple agents restarting, and who's restart can be delayed. Outside of further testing the robustness of the system these will be useful to test shutdown of the ABCIApplication that we are about to implement.
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

still no good
2022-07-05T20:46:00.9611020Z FAILED tests/test_agents/test_oracle_abci.py::TestAgentCatchup::test_run[4]
2022-07-05T20:46:00.9611315Z FAILED tests/test_agents/test_register_reset_abci.py::TestTendermintResetInterruptNoRejoin::test_run[4]
2022-07-05T20:46:00.9611576Z FAILED tests/test_agents/test_register_reset_abci.py::TestTendermintResetInterrupt::test_run[4]
2022-07-05T20:46:00.9611810Z FAILED tests/test_agents/test_register_reset_abci.py::TestTendermintReset::test_run[4]


python3.5 support and @ operator with  matmul  method

Are there any plans to include Python3.5 support (incl. binaries) and dedicated matmul @ operator?

Our python3 binaries should work with python3.5 (although currently the wheels require renaming), and adding matmul seems innocuous enough. However nobody is working on that now, it's likely a feature we'll accept if someone writes it.

I think we'd want to do this at the same time as supporting broadcasting for matmul in https://github.com/tensorflow/tensorflow/issues/216, otherwise the semantics might be confusing.

Yes, we need to merge matmul and batch_matmul before doing this, and someone decided to give them different sets of attributes (I can't imagine why).

@girving: By merging, do you mean unifying the two ops, or providing a Python wrapper that switches between them intelligently?
Is the difference in attributes (transpose vs adjoint) something you would want to keep for backwards compatibility, or would you plan to adjust one of the ops to match the other one?

@ibab: I mean unifying the two ops.  The Python wrapper is problematic since we don't necessarily know which to use at graph construction time, so tf.cond would be necessary.  The difference in attributes is pretty frustrating; @rmlarsen: did we have a nice conclusion as to which attributes we want?

In order to implement the semantics of @ properly, we should use an op that exactly matches the behaviour of numpy.matmul: http://docs.scipy.org/doc/numpy-1.10.0/reference/generated/numpy.matmul.html#numpy.matmul
Otherwise things would get very confusing when users assume that the tensorflow @ will work like the numpy one.
Here's a copy of the behaviour described in the docs:

If both arguments are 2-D they are multiplied like conventional matrices.
If either argument is N-D, N > 2, it is treated as a stack of matrices residing in the last two indexes and broadcast accordingly.
If the first argument is 1-D, it is promoted to a matrix by prepending a 1 to its dimensions. After matrix multiplication the prepended 1 is removed.
If the second argument is 1-D, it is promoted to a matrix by appending a 1 to its dimensions. After matrix multiplication the appended 1 is removed.
Multiplication by a scalar is not allowed, use * instead. Note that multiplying a stack of matrices with a vector will result in a stack of vectors, but matmul will not recognize it as such.

So there would need to be some extra work on top of unifying the two ops.

@ibab I believe all of those semantics are backwards compatible with what we currently have, but @rmlarsen can correct me if I'm wrong.

+1 for this issue (general tensordot). I ran into wall on something I was implementing that would really benefit from this.

@rmlarsen matmul and batch_matmul are merged, right?  That was the major issue blocking this in the past, so I think it would be straightforward to add.  I believe we would need to extend our matmul to handle 1-D tensors on either side, but this would be a welcome change at least to me.
Cc @aselle since this is related to numpy compatibility.

About 60 lines of tests, 4 lines of documentation, and 3 lines of "actual" code.  ;-)

A sneak preview:
>>> import tensorflow as tf
>>> import numpy as np
>>> a = [[1., 2.]]
>>> b = [[3., 4., 5.], [6., 7., 8.]]
>>> np_a = np.array(a)
>>> np_b = np.array(b)
>>> np_dot = np_a @ np_b
>>> tf_a = tf.constant(a)
>>> tf_b = tf.constant(b)
>>> tf_dot = tf_a @ tf_b
>>> tfpy_dot = tf_a @ b
>>> pytf_dot = a @ tf_b
>>> tfnp_dot = tf_a @ np_b
>>> nptf_dot = np_a @ tf_b
>>> with tf.Session():
...   print(tf_dot.eval())
...   print(tfpy_dot.eval())
...   print(pytf_dot.eval())
...   print(tfnp_dot.eval())
...   print(nptf_dot.eval())
...   print(np_dot)
...
[[ 15.  18.  21.]]
[[ 15.  18.  21.]]
[[ 15.  18.  21.]]
[[ 15.  18.  21.]]
[[ 15.  18.  21.]]
[[ 15.  18.  21.]]

Note that although NumPy arrays support the @ operator, they play nice with unknown types: when the rhs is not a NumPy array and it has an __rmatmul__() method, they return NotImplemented so that python calls that method instead.  This is why np_a @ tf.b works like a charm, thanks to NumPy.  I think I will open a feature request to make tensors behave the same way, returning NotImplemented rather than raising an exception when any magic function (e.g., __add__()) is called with an unsupported object type, and that object has an __r*__ method.

@ageron The problem with that is that "unsupported object" type means anything not convertible to a numpy array or Tensor.  It's hard to tell what those things are without trying to the conversion, and in Python the conversion can be a lossy operator (I hate this bit of Python).

@girving I opened #8051 to discuss this issue. I proposed a solution inspired from NumPy's __array_priority__ scheme.


Cow: Watch vk-spam-master.com

Cow requests the watch of the watch_keyword vk-spam-master\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

vk-spam-master\.com has been seen in 1 true positive, 1 false positive, and 0 NAAs.

Approved by Ollie in Charcoal HQ


About/contact page

We need a page with clear instructions on how to get in contact with us. Could be nice with a generic SWEET-Cat email.

Do we need anything else than what is visible at https://sweetercat.herokuapp.com/about/?

Do we need an IA mention/logo/link?

Don't know. Do you know @sousasag?


Floating base

This doesnt do anything, just testing all contributors bot so do NOT merge

@all-contributors please add @kawotwi for design


Suggestions

Im loving the updated version so far.
I had a few suggestions/enchancements. Forgive if i may over stretch,

Is there a possiblity to create a Burp Suite extension which detects and builds a GraphQL schema from proxy traffic (and emulation of introspection query responses)
The next is related to the tool. The possiblity to only bruteforce a specific query or mutation like user or users.

Is there a possiblity to create a Burp Suite extension which detects and builds a GraphQL schema from proxy traffic (and emulation of introspection query responses)
Cf. our discord, you can open an MR on the main project.
The next is related to the tool. The possiblity to only bruteforce a specific query or mutation like user or users.
I think you already can do that with a custom wordlist. But the software is not untended to stop until the schema is complete...


Load ELF DYN(.so file) cause Segmentation fault

As the README says, "It can load static and dynamically linked ELF EXEC and DYN (pie) binaries.". If I understand correctly, ELF DYN means a .so file.
However, when I try to load a easy test so file, the program causes crash.
The attachment is the source code of test so file, and the compiled so file, when I call ./loader /path/to/libtestso.so, it causes crash.
Does the project support to load a so file, or it is indeed a bug?
Thank you.

Seems my understanding is mistake, if a executable is compiled with -fPIC, it will also be Identified as ET_DYN.
After I read the source code, seems the project can only load executable file but not .so file.

As the README says, "It can load static and dynamically linked ELF EXEC and DYN (pie) binaries.". If I understand correctly, ELF DYN means a .so file.

DYN means the type of ELF, you can get DYN with -pie and -pic options, for loader there is no difference how the binary was compiled and it can load both. .so file has garbage entry point (since there is no entry point in shared library, actually you can specify it but you should bootstrap libc manually or you entry should be lightweight) that causes segfault at calling entry point from ELF header.


Review suggestions

Opening my branch with suggested changes as a pull-request (see https://github.com/docker/cli/pull/2708#pullrequestreview-591079988)

remove fields from cpWithProgress that were not used
only wrap cpWithProgress when printing progress
rename cpWithProgress to copyProgressReader
use aec for terminal control sequences
print progress to STDERR instead of STDOUT
don't use terminal detection to set the default, and instead perform
it if no value was set. This prevents confusion when doing, e.g.:
docker cp --help | grep ...
return early if "quiet", to simplify multiple "if" statements

First of all, thanks for your comments and PR. I'll check all the points.

@maximillianfx updated; PTAL

Great, I'll made some tests here to see if breaks something.


Homepage shows JSONError at made_for_you part

Describe the bug
Psst shows the following error instead of the "Made for you" section on the homepage
Error: Failed to read JSON: unknown variant `NotFound`, expected one of `Podcast`, `Playlist`, `Artist`, `Album` at line 1 column 10791

To Reproduce
Open psst-gui
Expected behavior
I expect to see a made for you section.
Screenshots

Environment

OS: 6.10.10-arch1-1
Version: 4dfa43d-modified (installed using AUR)

Additional context
The problem seems to be that NotFound is one of the types in the JSON response. It's a response of the following request:
GET https://api-partner.spotify.com/pathfinder/v1/query?operationName=homeSection&variables=<variables>
A snippet of the relevant JSON:
{
  "data": {
    "homeSections": {
      "__typename": "HomeSectionCollection",
      "sections": [
        {
          "__typename": "HomeSection",
          "data": {
            "__typename": "HomeGenericSectionData",
            "subtitle": {
              "text": ""
            },
            "title": {
              "originalLabel": {
                "textAttributes": {
                  "textFormatArguments": [
                    {
                      "uri": null
                    }
                  ]
                }
              },
              "text": "Made For ossyrial"
            }
          },
          "sectionItems": {
            "items": [
            {...},
              {
                "data": null,
                "content": {
                  "__typename": "PlaylistResponseWrapper",
                  "data": {
                    "__typename": "NotFound"
                  }
                },
                "uri": "spotify:playlist:37i9dQZF1EYkqdzj48dyYq"
              },
              {...},
            ],
            "pagingInfo": {
              "nextOffset": null
            },
            "totalCount": 9
          },
          "uri": "spotify:section:0JQ5DAUnp4wcj0bCb3wh3S"
        }
      ]
    }
  },
  "extensions": {}
}

If I visit the playlist with that uri via the webinterface (/playlist/37i9dQZF1EYkqdzj48dyYq), I get the following error popup:
.

My bad, I was using the version installed by AUR. I saw that the previous commit actually fixed this, and when building from master, it is fixed as well! Thanks!


Test::Quattor set_service_variant support reload and additional actions

LGTM

@ned21 this needs rereviewing and https://github.com/quattor/CAF/pull/118

@stdweird test failing :crying_cat_face:

@jrha also the ones from ncm-postgres fail, i have to investigate

@jrha i might have forgotten to push the last commit . i also need new build tools with this PR in to pass the postgres tests

@jrha comment reworded per your suggestion, thx


[FEATURE] Save dataset_train.reader.class_to_idx inside the model and load it by default during inference and validation

Is your feature request related to a problem? Please describe.
I'm not using imagenet, but during inference it loads the imagenet class_map by default.
Describe the solution you'd like
Instead, the class_to_idx from the dataset_train.reader.class_to_idx should just be saved somewhere inside the model, and be loaded into class_map during inference by default. and of course, if someone still wants to override the class_map for whatever reason, they could still do so.
I'd make a PR myself, but y'all probably have other consideration for exactly where to save/load it, so here's a sample solution.
Sample solution:
  # load
  if args.class_map == ''
    ckpt = torch.load(args.checkpoint, map_location='cpu')
    args.class_map = ckpt.get('class_to_idx', '')

  # save
  output_dir = Path(output_dir)
  best_model = list(output_dir.rglob("*best*"))[0]
  ckpt = torch.load(best_model, map_location='cpu')
  ckpt["class_to_idx"] = class_to_idx
  torch.save(ckpt, best_model)

Describe alternatives you've considered
We could save the class_to_idx into a class map file and ship it along side the model, but that's cumbersome and tedious. The proposed solution just works by default.
Additional context
The same should probably be done with the args.yaml file. There are a ton of timm models on hugging face with pretrained weights, but no args.yaml file with them which makes it near impossible to reproduce their results.

@JustinMBrown it's a reasonable idea, only issue is that it ends up being a big change, ALL pretrained checkpoints right now are bare state_dict with no extra layer in the dict, every key is a param/buffer and every value a tensor>. The train checkpoints (which do have extra keys ) are stripped of everything but the state dict before being published. I followed torchvision and other 'original' libs when this decision was made long ago.
The timm load functions would support stripping this automatically (and could be modified to extract other specific keys like class maps, but it would break anyone trying to just use torch.load() which works right now... https://github.com/huggingface/pytorch-image-models/blob/main/timm/models/_helpers.py#L31
I think I should stash the args in the train state dict regardless though, I've though about this as I've had numerous instances where I toasted the original train folders in disk cleanup and have only the checkpoint left and lost the hparams :/
Although I will point out, I've had multiple occasions where people have been provided with exact hparams, and I get an angry 'it doesn't work' because they don't understand things change when you change the global batch size, use a different dataset, etc the highest value is seeing templates and building an intuition for how to adapt different recipe templates in different uses ...
I will ponder this some more. FYI if you publish the weights to the HF hub, the pretrained_cfg has fields for labels, https://github.com/huggingface/pytorch-image-models/blob/main/timm/models/_pretrained.py#L41-L42 ... so for inference script and any side-loading it'd make sense to serialize/deserialize a pretraind_cfg instance w/ the weights.. the timm inference widget for Hub does this https://github.com/huggingface/api-inference-community/blob/main/docker_images/timm/app/pipelines/image_classification.py#L25-L42

Thanks @rwightman for the detailes, I am also intrested in the labels of the classes. I did try the code that you suggsetd:
model_id = 'timm/resnetrs350.tf_in1k'

model = timm.create_model(f"hf_hub:{model_id}", pretrained=True)

model.eval()

dataset_info = None
label_names = model.pretrained_cfg.get("label_names", None)
label_descriptions = model.pretrained_cfg.get("label_descriptions", None)
print(label_names,label_descriptions)

But I get None, None any idea how to get the label per index ?
Thank you


Add jenkins master pod annotations

What this PR does / why we need it:
Adds the ability to set annotations on the pod spec in the master deployment.
Specific use case: we use kube2iam and pod annotations to assign AWS IAM roles to pods. This makes it possible to set annotations on the jenkins master pod.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): no issue
Special notes for your reviewer:
@lachie83 @viglesiasce

/assign @viglesiasce

/ok-to-test

/lgtm


Show the position of the panorama closest to the mouse

User story

As a user
I want to see where it´s possible to go
So that I can make more precise movements.

HINT: a Nearest-Neighbor classifier might be helpful, e.g. https://github.com/mljs/knn .
Acceptance criteria

locations of possible panoramas are drawn as a cross on the floor.
only the location of the closest panorama to the mouse is displayed (the panorama, which would be selected, if the user double clicked at this mouse position)
when the mouse is around a certain panorama, the location of this panorama is displayed on the ground the ground with a 'cross' (like in google maps)
instead of a 'cross', it´s fine to use different shape as marker, like a red ball

Definition of done

Code has been peer reviewed
Documentation has been updated
Code has been included into the release (candidate)
No syntax / runtime errors
Code is well structured and formatted

The current development incudes a cross in the clossest position ot the mouse before but the spehere shows

[ x ]  only the location of the closest panorama to the mouse is displayed (the panorama, which would be selected, if the user double clicked at this mouse position)
[ x ]    when the mouse is around a certain panorama, the location of this panorama is displayed on the ground the ground with a 'cross' (like in google maps)
[  ] Not whow a cross if is there is a wall @clairebb1005 @Mm24


dashboard: never report unreliable bisections

Currently the dashboard does not report unreliable bisections
themselves, but there was a way in which they could still leak. The
recently detected case is when the bisection was done using a syz repro,
no reporting was made, but with a message about a newly found C repro
syzbot included bisection info and Cc'd bisection-sourced emails.
Fix this behavior and introduce the corresponding reporting test.

Let's close it and then try to open again.


BUG: reproducibility-supplement renders temp filepaths in scripts

When dumping metadata to the reproducibility supplement, the supplement scripts should reference the relative file path of that dumped (and zipped) metadata.
Instead, it references the temporary location where the  file was stored pre-compression.

I just ran into this today. Here's an example, just so we have it recorded here:
# The following command may have received additional metadata .tsv files. To
# confirm you have covered your metadata needs adequately, review the
# original metadata, saved at '/var/folders/jp/_7s6840d2gdf_gkg1291p7x00000g
# n/T/tmpucauzn2j/recorded_metadata/taxa_barplot_0'

The command I ran was:
replay supplement --i-in-fp analysis-results --o-out-fp supplement.zip

So given the output zip file name, the path in this case should be supplement\recorded_metadata/taxa_barplot_0.

@wasimsandhu reached out and said he's not going to be able to work on this after all, so this one is unassigned again.
Thanks again for letting me know @wasimsandhu - reach out if you want to get involved in the future!


add chocolatey_package to core chef

Adds chocolatey_package as a core-chef resource
Does not conflict with the chocolatey provider in the cookbook
Uses the semantics of the core-chef package resource instead of chocolately (:remove instead of :uninstall)
Implements multipackage install/remove/upgrade to the extent possible

Bonus is that it adds features to the core package provider to make it much easier to write multipackage-enabled subclasses.
One difference between this provider and the chocolatey provider in the cookbook is that we only take a string of options not a hash, again for consistency with the base package provider code in core chef.

Awesome to see this. I think you want to move the provider under providers/windows alongside of MSI and add logic to https://github.com/chef/chef/blob/master/lib/chef/provider/package/windows.rb#L66 to determine when to use chocolatey.

One thing we will definitely want to do either in this PR or a subsequent iteration is support the source attribute. Many host their chocolatey feeds either on a network share or some other privately hosted URL. This is key for enterprise scenarios.

Does the existing chocolatey provider support source or similar functionality?  I mostly copied what I found there.

@mwrock this is not written as a windows_package installer_type :chocolatey kind of package, it is its own chocolatey_package resource on the DSL
the reason for that is that the pattern for the core chef packages now works pretty well -- there's 1:1 mappings from resource-to-provider for yum_package, apt_package, dpkg_package, rpm_package, etc.  we no longer have the situation where you get a generic package resource wrapping a yum_package provider and the yum-specific validation is broken.  or like in the service resource where every time we add a new option to one of the providers then we have to add that option to the service resource itself and now we have options validation issues on every other service provider which will happily accept those options.
the N providers for 1 resource pattern broke pretty badly, and its not sustainable and does not end well and you can't ever get the validation right for it.
so this is written in the 1:1 resource-to-provider model, which is the way we should be using going forwards.  the windows_package installer_type is yet another bad example of that pattern, which if anything we need to pull out resources like msi_package rather than continue trying to make one fascade try to do even more work.

@lamont-granquist thanks for the explanation on why we are not going windows_package style.
Re source, the existing provider does support it: https://github.com/chocolatey/chocolatey-cookbook/blob/master/providers/default.rb#L73

interesting.  we've got the ability to inject arbitrary args via options and i think i dropped that to simply the overall shape of the API.
i'll have to check tomorrow to see if choco's semantics for source matches the way the other package providers use source.  want to make sure we don't wind up with another attributes (node) vs attributes (resources) semantic mixup...

@chef/client-core @chef/client-windows i think this is ready for final review and shipping.

cc @ferventcoder @guilhem

Tested this today. It may be tha tchocolatey is haveing perf issues or that I am on the road with flakey internet but the available_packages call is consistently dog slow. I played with filtering it to package name which was a big improvement but still took several seconds.
I think we'd be better off not trying to resolve candidate versions against the chocolatey feed. If a user provides a bogus version that is unfortunate but the cost here seems exorbitant.

I think we're going to find that we need at least a filtered version of available_packages in order to do good idempotency checks.  The check for upgradable? in the chocolatey cookbook also seems fairly bad since it just calls upgrade with --noop which seems like it'd be equally as expensive, if not worse.
We want to have an idempotency check in order to check the current_resource.version against the candidate_version.  If we set candidate_version to nil then we always upgrade on every CCR and that's a guaranteed bug report against this provider since the resource will never not be updated.
What other providers (yum, apt, gem) do is to get the index and then cache it for the lifetime of the CCR so that future providers don't have to go across the wire, and i'm working on making the gem provider only cache partial results (#3856).

What other providers (yum, apt, gem) do is to get the index and then cache it for the lifetime of the CCR so that future providers don't have to go across the wire

Right, package indexes are what we have yet to put into Choco, but it's on the list and super important to do.

Just did a little testing and list git -r produces a lot of output, looks like its searching against much more than just the program name index and is probably pulling out substrings?
I think I'm seeing why the existing cookbook does an upgrade --noop but that's kind of a messy solution, it'd be nice to get a better API to query here.
Not sure what to do about this provider in the meantime, I need to think about it a bit...

Yeah, I'm a bit stalled on this now.  The Chef::Provider::Package superclass really expects subclasses to behave this way.  We could probably hack it all up, but it'd be a massive violation of Liskov Substitution part of SOLID and while we /could/ do it, we probably /shouldn't/ do it.

Yeah I can see the dilemma. I do think that list <package> -r is a step in the right direction but not perfect. The git example I think may be more egregious than the average package in terms of number of results returned, but I don't have good data to back that up with. Even git returns 274(331ms) results compared to the current 2875 (38570msec) which is a significant (but not ideal) improvement.
I think adding the package filter would be reasonable to release as long as we do not risk taking down @ferventcoder 's chocolatey database with the queries.

I think adding the package filter would be reasonable to release as long as we do not risk taking down @ferventcoder 's chocolatey database with the queries.

Not risk taking down Chocolatey.org with queries. It seems to do pretty well for the most part.

One thing that I'll throw out there is that the /universe endpoint on supermarket.chef.io delivers a lot more than that.   It returns 3.2MB of rendered JSON with 12579 cookbook versions in it.  It can do that because it caches the rendered JSON and mostly just serves that up.  Every 60 seconds or so it'll get hit by a request which will decide the JSON is too stale, and it'll asynchronously start a single thread that does the full table scan of the database and regenerates the JSON--cant remember what we do for the first request after a restart when there's no cached JSON (you can either send back a 4xx retriable code or else block and queue).
And that endpoint gets pounded both by client side use of berkshelf and by berkshelf-api mirrors.
We actually 'should' be supporting an API more like rubygems where bundler will make a query with the list of gems to depsolve against, and rubygems replies with only a slice of the universe.  The API calls that gem install chef --verbose makes looks like:
HEAD https://api.rubygems.org/api/v1/dependencies
200 OK
GET https://api.rubygems.org/api/v1/dependencies?gems=chef
200 OK
GET https://api.rubygems.org/api/v1/dependencies?gems=chef-config,chef-zero,diff-lcs,erubis,ffi-yajl,highline,mixlib-authentication,mixlib-cli,mixlib-log,mixlib-shellout,net-ssh,net-ssh-multi,ohai,plist,pry,rspec-core,rspec-expectations,rspec-mocks,rspec_junit_formatter,serverspec,specinfra,syslog-logger
200 OK
GET https://api.rubygems.org/api/v1/dependencies?gems=builder,coderay,ffi,hashie,ipaddress,libyajl2,method_source,mime-types,mixlib-config,multi_json,net-scp,net-ssh-gateway,net-telnet,rack,rake,rspec,rspec-its,rspec-support,sfl,slop,systemu,uuidtools,wmi-lite
200 OK

That's closer to the 'right' way to do this kind of thing, but we haven't had the need (yet) to start filtering /universe results.

One thing that I'll throw out there is that the /universe endpoint on supermarket.chef.io delivers a lot more than that. It returns 3.2MB of rendered JSON with 12579 cookbook versions in it. It can do that because it caches the rendered JSON and mostly just serves that up. Every 60 seconds or so it'll get hit by a request which will decide the JSON is too stale, and it'll asynchronously start a single thread that does the full table scan of the database and regenerates the JSON (meanwhile threads continue to serve the old JSON until the new JSON is available)--cant remember what we do for the first request after a restart when there's no cached JSON (you can either send back a 4xx retriable code or else block and queue).

Yep, I've started down a similar path with caching. I inherited the inner workings of the Chocolatey Gallery (Chocolatey.org) by starting with the NuGet Gallery and working from there. It wasn't the most optimized thing at the time I forked the codebase and while I've made things better it is still not complete yet. We are doing a total rewrite of the web site, although I had to put bits and pieces over into it over the month of October because traffic was very high, plus the database had some very fragmented indexes that caused everything to get worse.  I wrote it all up in our recent newsletter.

Heh, cool, victim of your own success.
So I think I'm going to put this on pause until chocolatey.org get the API+caching improvements, and I'll cherry-pick the commit that adds better multipackage support into core and try building out the Zypper provider on top of that one...

So I think I'm going to put this on pause until chocolatey.org get the API+caching improvements

This is already done. Now we are just fixing up small things related to the changes.

So what API should I use?  The whole list or the pruned down list?

Pruned.

okay probably need to give this a spin, should be using the pruned down list -r

@chef/client-core this is ready for review

Other than that :+1:

:+1:

Here's the draft reference page for 12.7: https://docs.chef.io/release/12-7/resource_chocolatey_package.html

@jamescott looks like you mostly just need to add the remaining actions, and add some multipackage examples.


Update repositories.json

Adds https://raw.githubusercontent.com/diosadentro/Hubitat/main/repository.json to the list of repositories.

manually merged