tensorflow.python.framework.errors_impl.UnknownError : Input/output error

there is a error when i run trainer code , it troubled me many days , is there anyone meet the same problem? hope someone can help me. thank you!!
Traceback (most recent call last):
File "avod/experiments/run_training.py", line 88, in
tf.app.run()
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/platform/app.py", line 48, in run
_sys.exit(main(_sys.argv[:1] + flags_passthrough))
File "avod/experiments/run_training.py", line 84, in main
train(model_config, train_config, dataset_config)
File "avod/experiments/run_training.py", line 41, in train
trainer.train(model, train_config)
File "/mnt/data/yanjuan/avod-master/avod/core/trainer.py", line 123, in train
sess.graph)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/summary/writer/writer.py", line 336, in init
filename_suffix)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/summary/writer/event_file_writer.py", line 67, in init
gfile.MakeDirs(self._logdir)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/lib/io/file_io.py", line 367, in recursive_create_dir
pywrap_tensorflow.RecursivelyCreateDir(compat.as_bytes(dirname), status)
File "/usr/lib/python3.5/contextlib.py", line 66, in exit
next(self.gen)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/errors_impl.py", line 466, in raise_exception_on_not_ok_status
pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.UnknownError: /mnt/data/yanjuan/avod-master/avod/data/outputs/avod_cars_example/logs/train/2018-08-25 16:33:48.655024; Input/output error.
wait for your answer!

isn't there anyone meet the same problem?If you have a solution to this problem ,please give me some advice! i am very appreciate to you...

i have settled the question, for me ,it is the error in avod/avod/core/trainer.py which the variable named datetime_str  can not  combination to generate a file because it has the character which is not alphabet .


The project MUST apply at least one dynamic analysis tool

The project MUST apply at least one dynamic analysis tool to any proposed major production release of the software produced by the project before its release.
A dynamic analysis tool examines the software by executing it with specific inputs. For example, the project MAY use a fuzzing tool (e.g., American Fuzzy Lop) or a web application scanner (e.g., OWASP ZAP or w3af). In some cases the OSS-Fuzz project may be willing to apply fuzz testing to your project. For purposes of this criterion the dynamic analysis tool needs to vary the inputs in some way to look for various kinds of problems or be an automated test suite with at least 80% branch coverage. The Wikipedia page on dynamic analysis and the OWASP page on fuzzing identify some dynamic analysis tools. The analysis tool(s) MAY be focused on looking for security vulnerabilities, but this is not required.

@drewroengoogle @sealesj Hey guys feel free to reprioritize this issue.


Progress bar without active class

Hi,
I'm trying to use the ui-progress component but I don't want my progress bar to have the active class applied. I'm displaying it as a static indicator and don't want the animation (or at least it should be optional). Since the active class is added by default, I can't find an option to remove it.
Something like this would solve my problem:
{{#ui-progress percent=myPercent class="tiny" active=false}}

or...
{{#ui-progress percent=myPercent class="tiny" active=isActive}}

What's the recommended way?
Thanks!

Solved it! Figured out to do this:
{{#ui-progress percent=myPercent class="tiny" showActivity=false}}


OrderbookSync does not reconnect when socket connection is lost

When the socket connection is lost, OrderbookSync ends up in a stale state (it does not attempt to re-connect and thus also stops updating the underlying orderbook).
I have "solved" this issue in my app by re-connecting the orderbook whenever the last update is older than few minutes. However, it would be better if this was fixed in the master branch.

  constructor(this._client) {
    this._client.on("close", data => this.onStateChange());
  }

  private onStateChange = () => {
    if (!this._client.socket) setTimeout(() => this._client.connect(), 5000);
  };

@ctubio Mind opening a PR?

why this issue([bug]) is open ?

Closing this due to inactivity. Please open a new Issue and/or PR (possibly referencing this issue) if further action is deemed necessary.


What is the difference between matchLines in previewOptions and surroundingContext?

Testing #223154
export interface FindTextInFilesOptionsNew {
		...
		/**
		 * Options to specify the size of the result text preview.
		 */
		previewOptions?: {
			/**
			 * The maximum number of lines in the preview.
			 * Only search providers that support multiline search will ever return more than one line in the match.
			 */
			matchLines?: number;
...
		};

		/**
		 * Number of lines of context to include before and after each match.
		 */
		surroundingContext?: number;
	}

I don't understand the difference by reading the API doc. previewOptions sounds like it should be about the preview, not the match, but then it has a property called matchLines.

I could maybe name it better. It says The maximum number of lines in the preview., but I guess matchLines sounds like it should be the number of lines to match.


Adding support for Qwen model

A working colab notebook

Can you clear the outputs of the Colab and show the outputs files and some of its contents?

Can you clear the outputs of the Colab and show the outputs files and some of its contents?

I am trying to create a smaller webdataset to iterate faster and showcase results. In case you already have something like that, would you like to share?


CI robot-testien korjaus

Codecov Report

Merging #37 (cd57e34) into main (c49e560) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #37   +/-   ##
=======================================
  Coverage   93.84%   93.84%
=======================================
  Files           5        5
  Lines         130      130
  Branches       14       14
=======================================
  Hits          122      122
  Misses          8        8

Continue to review full report at Codecov.

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


[1pt] Update PR template

Simple update to the PULL_REQUEST_TEMPLATE.md to remove unnecessary/outdated boilerplate items,  add octothorpe (#) in front of Additions, Changes, Removals to mirror CHANGELOG.md format, and clean up the PR Checklist.
Changes

docs/

PULL_REQUEST_TEMPLATE.md

Testing
n/a
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] Informative and human-readable title, using the format: [_pt] PR: <description>.
[x] Links are provided if this PR resolves an issue, or depends on another other PR.
[x] Changes are limited to a single goal (no scope creep).
[x] Code can be automatically merged (no conflicts).
[x] Changes adhere to style guidelines.
[x] Any change in functionality is tested.
[ ] Passes all unit tests locally (Inside interactive docker container, within project root, run: pytest unit_tests/).
[x] New functions are documented (with a description, list of inputs, and expected output).
[x] Placeholder code is flagged / future todos are captured in comments.
[x] Project documentation has been updated (CHANGELOG and/or README).
[x] Reviewers requested with the Reviewers tool.

@mluck thanks for your review and suggestions. I appreciate it. I addressed each one. Please let me know if you'd like to see modifications to the checklist, after the updates I made.

Thanks, Rob. Nice work. This is a big improvement WRT standardizing our process.
I agree with Matt's comment about adding "PR:" to title of this Pull Request.

Looks like there are unresolved conflicts in the Changelog


Flutter web framework raised an exception on hot restart

Steps to Reproduce

Hot restart flutter web app when the app is running on Chrome (Using Idea Intellij, press Command + R on Mac OS)
Exception raised

Expected results:
No exception
Actual results:
The page cannot be rendered.

Logs

======== Exception caught by widgets library =======================================================
The following assertion was thrown building Builder:
Assertion failed: file:///Users/li9s/Github/frameworks/flutter/packages/flutter/lib/src/widgets/navigator.dart:3598:18
!keyReservation.contains(key)
is not true

The relevant error-causing widget was:
  MaterialApp file:///Users/li9s/Github/flutter_projects/rop_admin_cli/lib/main.dart:30:24
When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 236:49  throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 29:3    assertFailed
packages/flutter/src/widgets/navigator.dart 3598:46                           <fn>
packages/flutter/src/widgets/navigator.dart 3602:14                           [_debugCheckDuplicatedPageKeys]
packages/flutter/src/widgets/navigator.dart 3638:7                            <fn>
...
====================================================================================================

======== Exception caught by scheduler library =====================================================
The following assertion was thrown during a scheduler callback:
Assertion failed: file:///Users/li9s/Github/frameworks/flutter/packages/flutter/lib/src/rendering/object.dart:2388:12
attached
is not true

When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 236:49  throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 29:3    assertFailed
packages/flutter/src/rendering/object.dart 2388:12                            getTransformTo
packages/flutter/src/widgets/editable_text.dart 2424:48                       [_updateSizeAndTransform]
packages/flutter/src/widgets/editable_text.dart 2427:49                       <fn>
...
====================================================================================================

======== Exception caught by scheduler library =====================================================
Assertion failed: file:///Users/li9s/Github/frameworks/flutter/packages/flutter/lib/src/rendering/object.dart:2388:12
attached
is not true
====================================================================================================

   info • The library 'package:integration_test/integration_test_driver.dart' is legacy, and should not be imported into a null safe library • integration_test/driver.dart:6:8 •
          import_of_legacy_library_into_null_safe
   info • Don't import implementation files from another package • lib/generated_plugin_registrant.dart:7:8 • implementation_imports
   info • The library 'package:qlevar_router/qlevar_router.dart' is legacy, and should not be imported into a null safe library • lib/main.dart:2:8 •
          import_of_legacy_library_into_null_safe
   info • The library 'package:dio/dio.dart' is legacy, and should not be imported into a null safe library • lib/network/requests.dart:4:8 •
          import_of_legacy_library_into_null_safe
   info • The library 'package:qlevar_router/qlevar_router.dart' is legacy, and should not be imported into a null safe library • lib/pages/page_app_dashboard.dart:2:8 •
          import_of_legacy_library_into_null_safe
   info • Unused import: 'package:rop_admin_cli/data/global_state.dart' • lib/pages/page_app_dashboard.dart:3:8 • unused_import
   info • The library 'package:qlevar_router/qlevar_router.dart' is legacy, and should not be imported into a null safe library • lib/pages/page_app_edit.dart:2:8 •
          import_of_legacy_library_into_null_safe
   info • The library 'package:qlevar_router/qlevar_router.dart' is legacy, and should not be imported into a null safe library • lib/pages/page_app_manage.dart:2:8 •
          import_of_legacy_library_into_null_safe
   info • The library 'package:qlevar_router/qlevar_router.dart' is legacy, and should not be imported into a null safe library • lib/pages/page_login.dart:2:8 •
          import_of_legacy_library_into_null_safe
   info • The library 'package:qlevar_router/qlevar_router.dart' is legacy, and should not be imported into a null safe library • lib/pages/page_main.dart:2:8 •
          import_of_legacy_library_into_null_safe
   info • The library 'package:qlevar_router/qlevar_router.dart' is legacy, and should not be imported into a null safe library • lib/router/routes.dart:2:8 •
          import_of_legacy_library_into_null_safe
   info • The library 'package:qlevar_router/qlevar_router.dart' is legacy, and should not be imported into a null safe library • lib/widgets/widget_app_combobox.dart:2:8 •
          import_of_legacy_library_into_null_safe
   info • The library 'package:qlevar_router/qlevar_router.dart' is legacy, and should not be imported into a null safe library • lib/widgets/widget_drawer.dart:2:8 •
          import_of_legacy_library_into_null_safe
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature was
          deprecated after v1.25.0-8.1.pre. • lib/widgets/widget_logo.dart:10:12 • deprecated_member_use
   info • The library 'package:qlevar_router/qlevar_router.dart' is legacy, and should not be imported into a null safe library • lib/widgets/widget_nav_header.dart:2:8 •
          import_of_legacy_library_into_null_safe

[✓] Flutter (Channel beta, 1.26.0-17.4.pre, on Mac OS X 10.13.6 17G65 darwin-x64, locale zh-Hans-CN)
    • Flutter version 1.26.0-17.4.pre at /Users/li9s/Github/frameworks/flutter
    • Framework revision 48c9d3e0e1 (4 days ago), 2021-02-10 11:46:09 -0800
    • Engine revision 2c527d6c7e
    • Dart version 2.12.0 (build 2.12.0-259.8.beta)
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/li9s/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • ANDROID_SDK_ROOT = /Users/li9s/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    ✗ Xcode 9.4.1 out of date (12.0.1 is recommended).
      Download the latest version or update via the Mac App Store.
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] IntelliJ IDEA Ultimate Edition (version 2020.3.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 53.1.5
    • Dart plugin version 203.6912

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 88.0.4324.150

! Doctor found issues in 2 categories.

Hi @rockingdice
I see there's an open issue addressing the case you described. https://github.com/flutter/flutter/issues/75630
Please follow up on that issue, I'm closing the current one as a duplicate.
If you disagree, please write in the comments and I will reopen it.
Thank you

Sorry, I can't even reproduce myself, it's a rare case.
Do you mean hot-restart multiple times at once? If I recall correctly I did just once.
My app is busy navigating on hot-restart (3-4 times in a short time, like redirecting)

HI @rockingdice
It could be navigation and hot-restart bug, together reproducing this
Can you please create a minimal code sample to reproduce this behavior?
Thank you

Sorry, I can't make one right now.

Hi @rockingdice
Please provide the reproducible code sample to better address the issue.
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


[Stepper] Export useStepContext

Exports the StepContext so it's possible to use it while creating custom Stepper components.
Closes #30900.

Added a short description. Should be enough, considering I exported the type of the context, so it'll be easy for developers to find out how to use it.


Device status not updated during camera triggers

Hi again, sorry for constantly nagging about supporting my strange laptop hot-plugging setup, but noticed some issues in the implementation of #3. Really appreciate the work, and you have already done more than enough to support my use-cases, so don't sweat it if it is hard to find the time to handle these cases in the way I was hoping. Just thought to report in case it was something you happened to overlook in the implementation.
Anyways, it appears as if the device status is not updated when the camera is turned on or off. This causes a couple of unexpected behaviours:
Connecting light after startup

Disconnect lights
Start litra-autotoggle
Connect lights
Start camera
Light does not turn on

This produces the following log output
% litra-autotoggle
No Litra devices found
Starting `log` process to listen for video device events...
Listening for video device events...
// Connect light to computer
Detected that a video device has been turned on, attempting to turn on Litra device...
No Litra devices found

Would have expected litra-autotoggle to scan for new devices when it detects that the camera has turned on, and then turn on the newly connected devices.
Disconnecting light after startup

Connect lights
Start litra-autotoggle
Disconnect lights
Start camera
Light does not turn on, and litra-autotoggle process crashes

% litra-autotoggle
Found Litra Glow device (serial number: 2141FE000P88)
Starting `log` process to listen for video device events...
Listening for video device events...
// Disconnect light
Detected that a video device has been turned on, attempting to turn on Litra device...
HID error occurred: hidapi error: hid_open_path: device mach entry not found with the given path

Would expect the process to keep running even though the devices are not available anymore and treat the situation as if no devices are connected.
Environment

litra-autotoggle version: 0.3.0
Operating system: macOS 15.0.1
Device: Litra Glow

What you describe is what should be happening 😓 I will take a look when I have some time!

Can you run litra-autotoggle --version, just to double check for any version surprises? 😓

Okay, so I'm not a Rust developer, but I think I managed to trace the issue. It goes something like this:

When litra-autotoggle notices a change in camera status, it fetches the list of supported devices using the litra-rs library at https://github.com/timrogers/litra-autotoggle/blob/v0.4.0/src/main.rs#L108
In the litra-rs library, this fetches the list of devices using HidApi at https://github.com/timrogers/litra-rs/blob/v2.1.0/src/lib.rs#L61
The device_list method in HidApi seems to use cached results as there are no calls to refresh_devices, and the same instance of HidApi that was created on litra-autotoggle start is reused.

So I think the solution would be to at some point after a camera change is identified force the HidApi to refresh the internal list of devices before attempting to turn the lights on or off.
Sorry if my terminology is not consistent with Rust developer community conventions. I hope the message is understandable nonetheless.

Totally makes sense! I am travelling at the moment without my Litra, so it's hard for me to fix this, but I will pick it up when I get back.

This should be fixed in v0.4.1! Can you give it another go?

Yes, works flawlessly now! Thanks for taking the time to fix it.


How to use two or more templates?

Hi, doing a couple of tutorials I've found you have a template for Actions on Google, and another for Alexa Dialog, and another for unit testing and so on. Say I want to start a project by combining two or more of these templates. How would I go about this?

Hey, unfortunately, there's no functionality to combine templates on installation (or after).
Create a new project with the largest overlap of features you need and copy and paste the other functionality from the templates or example projects (https://github.com/jovotech/jovo-framework/tree/master/examples)
Hope this helps

Hey, unfortunately, there's no functionality to combine templates on installation (or after).
Create a new project with the largest overlap of features you need and copy and paste the other functionality from the templates or example projects (https://github.com/jovotech/jovo-framework/tree/master/examples)
Hope this helps


Add Open Hardware

Awesome Open Hardware
The awesome Open Hardware list is made for people wanting to learn more about open source hardware (projects). On the one hand it has the most awesome example project for people to get inspired. On the other hand it has more in depth papers and background information about the topic.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.

I reviewed #2265
and #2257

You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

unicorn

Thank you @IAmCoder for the proposed fix, I like it!

The contributing.md explains how to add something to awesome itself. It should rather explain the rules and process you propose for your list. For inspiration see here: https://github.com/collective/awesome-plone/blob/main/contributing.md

Thanks Philip!
I liked your example and made something similar :)

Tweet: https://twitter.com/awesome__re/status/1533406968089522176

Ayzat

It was crying to request I have a computer in mind and there’s an app that
can access it next-door and I want it to stop that’s what I was trying to
request some type of security so they can no longer access wires access to
my mind and my private thoughts yes the capability is there now and the
medical community here knows it it’s on read me MD & I don’t know if they
don’t realize that there’s anything to make it stop with it can’t be
stopped but it’s there now and it’s a program that anyone can access I
think it’s for free and that puts me at risk trying to find a human rights
organization to help me stop this.
On Sat, Jun 11, 2022 at 9:14 PM, Тажымаматов Жениш @.***>
wrote:

Ayzat
—
Reply to this email directly, view it on GitHub
https://github.com/sindresorhus/awesome/pull/2266#issuecomment-1153047988,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASQ44362Z63XWYIQ34QZ6Q3VOVB2FANCNFSM5WOT4Y3A
.
You are receiving this because you commented.Message ID:
@.***>


Badge information

This PR implements a rework of the attendee registration. The main changes are:

attendees are now only created after clicking a link in a confirmation mail
attendee badge data is requested and a badge preview image is shown

I added full test coverage for all changed and added model, form, admin and view classes.

Pull Request Test Coverage Report for Build 596

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

Totals

Change from base Build 590:
0.02%

Covered Lines:
3635

Relevant Lines:
3635

💛  - Coveralls


Algolia is not working on Nuxt

Version
@nuxtjs/algolia: 1.4.0
nuxt: 3.0.0
Reproduction Link

Hey,
have you followed this docs https://algolia.nuxtjs.org/advanced/vue-instantsearch?

Hey,
have you followed this docs https://algolia.nuxtjs.org/advanced/vue-instantsearch?

Yeah did that all even install that vueinstant search package as it was not download by algolia

Could you paste here your configuration of the module and how do you use it in the Vue component?

Could you paste here your configuration of the module and how do you use it in the Vue component?

nuxt.config.ts
export default defineNuxtConfig({
  modules: [
    '@nuxtjs/algolia'
  ]
  algolia: {
          apiKey: 'M91b29bc3b270e50cd3d549xxxxxxx,
          applicationId: 'W0FRE10Z7J',
          lite: true,
          cache: true,
          instantSearch: {
              theme: 'algolia'
          }
      }
})

DashHeader.vue (Component)
<ais-instant-search :index-name="indexName" :search-client="algolia">
       <ais-search-box />
       <ais-hits />
</ais-instant-search>

This is really strange. I have just copied the code into example nuxt 3 project and it works:
Component:
<template>

    <ais-instant-search :index-name="indexName" :search-client="algolia">
      <ais-search-box />
      <ais-hits />
    </ais-instant-search>

</template>

Configuration:
export default defineNuxtConfig({
  modules: [
    [
      "@nuxtjs/algolia",
      {
        apiKey: process.env.ALGOLIA_SEARCH_API_KEY,
        applicationId: process.env.ALGOLIA_APP_ID,
        instantSearch:{
          theme: 'algolia'
        }
      },
    ],
  ],
});

Result in the browser:

Could you try to just copy/paste my code and see if it works for you that way? Maybe some typo somewhere? If it wont work, could you provide a reproduction link? I would be happy to investigate it more once I will have a reproducible project :)

This is really strange. I have just copied the code into example nuxt 3 project and it works:
Component:
<template>

    <ais-instant-search :index-name="indexName" :search-client="algolia">
      <ais-search-box />
      <ais-hits />
    </ais-instant-search>

</template>

Configuration:
export default defineNuxtConfig({
  modules: [
    [
      "@nuxtjs/algolia",
      {
        apiKey: process.env.ALGOLIA_SEARCH_API_KEY,
        applicationId: process.env.ALGOLIA_APP_ID,
        instantSearch:{
          theme: 'algolia'
        }
      },
    ],
  ],
});

Result in the browser:

Could you try to just copy/paste my code and see if it works for you that way? Maybe some typo somewhere? If it wont work, could you provide a reproduction link? I would be happy to investigate it more once I will have a reproducible project :)

Sure i will try your code tomorrow and see and will also try to reinstall the algolia package once again and also if that doesn't work will share a stackblitz link. Btw I am assuming the index name can be anything right?

It should be the name of the index in Algolia Dashboard.
Let me know about the results so that I can help you resolve these issues 🙂

This is really strange. I have just copied the code into example nuxt 3 project and it works:
Component:
<template>

    <ais-instant-search :index-name="indexName" :search-client="algolia">
      <ais-search-box />
      <ais-hits />
    </ais-instant-search>

</template>

Configuration:
export default defineNuxtConfig({
  modules: [
    [
      "@nuxtjs/algolia",
      {
        apiKey: process.env.ALGOLIA_SEARCH_API_KEY,
        applicationId: process.env.ALGOLIA_APP_ID,
        instantSearch:{
          theme: 'algolia'
        }
      },
    ],
  ],
});

Result in the browser:
Could you try to just copy/paste my code and see if it works for you that way? Maybe some typo somewhere? If it wont work, could you provide a reproduction link? I would be happy to investigate it more once I will have a reproducible project :)

Here is the reproduction link: https://stackblitz.com/edit/nuxt-starter-azgjp4?file=nuxt.config.ts

I know where the problem is.
In your example, you are not using a script setup approach which will automatically register components. So, in your case you need to register them as following:
<template>

    <ais-instant-search :index-name="indexName" :search-client="algolia">
      <ais-search-box />
      <ais-hits />
    </ais-instant-search>

</template>

If you do so, you will have following result in stackblitz and your project:

Let me know if that worked for you.

I know where the problem is.
In your example, you are not using a script setup approach which will automatically register components. So, in your case you need to register them as following:
<template>

    <ais-instant-search :index-name="indexName" :search-client="algolia">
      <ais-search-box />
      <ais-hits />
    </ais-instant-search>

</template>

If you do so, you will have following result in stackblitz and your project:
Let me know if that worked for you.

Thanks a lot that worked perfectly

Ok cool, closing the issue then.


Consider running tap output into a target in CI

In #93 I decided to run the tap thru a simple target target-sqlite to see if the new streams I added worked.
By doing this, I instantly found mistyped fields in the Events stream.
Example error:
CRITICAL '20730626430' is not of type 'integer', 'null'
CRITICAL
CRITICAL Failed validating 'type' in schema['properties']['id']:
CRITICAL     {'type': ['integer', 'null']}
CRITICAL
CRITICAL On instance['id']:
CRITICAL     '20730626430'

I think this would be a great testing method to ensure our schemas are correctly typed.
Possibly a new step that runs:
poetry run tap-github --config c.json --catalog ca.json | poetry run target-sqlite -c sq.json and crashes if the exit code is non-zero.
Thoughts on implementing this?

Hi, @laurentS and @Ry-DS. I agree running a test to include landing in target-sqlite or even target-jsonl is probably helpful for catching JSON Schema typing issues.
There are SDK-based solutions as well, such as including an option for JSON Schema type validations against reach record when testing in pytest.


Push key configuration documentation for ElasticBeanstalk

Request for additional documentation about best practices for push key installation and permissions when using ElasticBeanstalk.
For example, I'm not sure if I am placing the .p12 files in the correct location with the correct permissions for parse-server to use them. For security, it wouldn't be a good idea to bundle the keys with the application or even key locations in index.js. What I have done is create environment variables for the key locations
    ios: [
      {
        pfx: process.env.MYAPP_PUSH_KEY_PATH_DEV, // Dev PFX or P12
        bundleId: process.env.MYAPP_PUSH_BUNDLEID,
        production: false // Dev
      },
      {
        pfx: process.env.MYAPP_PUSH_KEY_PATH_PROD, // Prod PFX or P12
        bundleId: process.env.MYAPP_PUSH_BUNDLEID,
        production: true // Prod
      }
    ]
  }```

Where the paths are set in the ElasticBeanstalk environment properties:

MYAPP_PUSH_KEY_PATH_DEV   /home/ec2-user/.ssh/myapp_push_key_dev.p12
MYAPP_PUSH_KEY_PATH_PROD   /home/ec2-user/.ssh/myapp_push_key_disb.p12
MYAPP_PUSH_BUNDLEID   com.foo.myapp

However, when I attempt to send a push notification, I am seeing a permission denied error in the npm-debug.log:

> npm ERR! Linux 4.4.8-20.46.amzn1.x86_64
> npm ERR! argv "/opt/elasticbeanstalk/node-install/node-v4.4.3-linux-x64/bin/node" "/opt/elasticbeanstalk/node-install/node-v4.4.3-linux-x64/bin/npm" "start"
> npm ERR! node v4.4.3
> npm ERR! npm  v2.15.1
> npm ERR! code ELIFECYCLE
> npm ERR<EMAIL_ADDRESS>start: `node index.js`
> npm ERR! Exit status 7
> npm ERR!
> npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node index.js'.
> npm ERR! This is most likely a problem with the petfetch-server package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     node index.js
> npm ERR! You can get information on how to open an issue for this project with:
> npm ERR!     npm bugs petfetch-server
> npm ERR! Or if that isn't available, you can get their info via:
> npm ERR!
> npm ERR!     npm owner ls petfetch-server
> npm ERR! There is likely additional logging output above.
>
> npm ERR! Please include the following file with any support request:
> npm ERR!     /var/app/current/npm-debug.log
>
> ><EMAIL_ADDRESS>start /var/app/current
> > node index.js
>
> parse-server-example running on port 8081.
> /var/app/current/node_modules/parse-server/lib/ParseServer.js:339
>             throw err;
>             ^
>
> Error: EACCES: permission denied, open '/home/ec2-user/.ssh/myapp_push_key_disb.p12'
>     at Error (native)

I have tried giving the .p12 files 400, 644, and even 777 permissions but always get the access denied error.

Seems to be a generic user access issue. I moved the keys and made the nodejs user owner and the permission error went away.


Fixed typo

Added "i" in mispelled "Audiokit" link in frameworks readme.
Ready to send us a pull request? Please make sure your request is based on the develop branch of the repository as master only holds stable releases.

Hi Scott, I love getting PRs but there are conflicts and the instructions are going to need a full overhaul anyway, so unless you want to resolve the conflicts, I might got close this PR and rewrite the document when we are closer to releasing v5.

Actually if its just the "I" I'll get It on develop shortly.

Okay, thanks! I don't normally do those type of commits just thought for
branding it's good to have your name spelled properly
On Tue, Sep 1, 2020 at 8:46 AM Aurelius Prochazka<EMAIL_ADDRESS>wrote:

Actually if its just the "I" I'll get It on develop shortly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AudioKit/AudioKit/pull/2240#issuecomment-684105626,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOWJGNC6B5MJBZDH5GS2RVDSDQY3XANCNFSM4QQHHQVA
.


Weighted Rules

What about making weighted Rules?
During an observation, a Slot would look at its neighbors and rank the Module placement options based on its neighbors' desires (weights of Rules).

Could you expand on this? Weighted rules globally? Per-slot? What is it you'd like to achieve here?
In any case, this is so different from how it works today, I'd probably be experimenting with it in a completely new codebase.

From the user point of view, Monoceros (and our implementation of WFC) operates on local relations, rather than global ones. Setting a weight of a Module within a Slot is a static top-down approach - the designer needs to know where to place certain Modules. That is quite okay for certain use cases (such as the informed space heatmaps).
That being said, the user cares (and should care) more about local relations, in other words, which module should appear next to another, regardless where is such couple located within the envelope. That may result in different weights of a module not based on the global location but rather on the context around it. It is also very easy to use: "if this, then prefer that".
I'd start with globally weighted Rules, as distributing rule weights throughout the envelope (per-slot) would be too difficult to design (although I can imagine that as well).
Not sure about this WFC core, but MonocerosPro is fairly ready for such feature. Therefore I cannot tell if a new codebase would be needed.


Softlock when nothing is drawn

Specifically, if I have Citro render the top screen render target, but I don't draw anything, it will go through two cycles before soft locking. Removing this rendertarget stuff in aptMainLoop fixes this (which broke my FPS timer :P)
Emulation on Citra
Apparently the solution is to fool the render targets by applying a completely transparent texture at all times--something I'd rather not do. I've tested both builds on my 3DS and they behave as shown on Citra.

If you don't draw anything to a target, why do you bind it?

Well I'm unsure how to check if the end user will be drawing anything immediately. They could be writing their draw function into the script to set up for later. Add other evens like keypressing and it doesn't work because of the softlock. If there's a way to fix this issue that I'm unaware of (if it's on my end), please let me know.

Why don't you let the end users bind the targets themselves?

The reason is because it's meant to be a game framework (i.e. Love Potion), but I'm rewriting it to use Citro rather than sf2dlib. The end users shouldn't need to know how to bind a rendertarget on the Lua side, that's just ugly and makes no sense. /shrug

It does make sense. Allowing the end user to control rendertargets allows for fun stuff to happen, such as caching a piece of drawing to a texture and using that multiple times when drawing to a screen.

Right, I know. The issue, however, is that this is basically Love2D for 3DS. I'm following how it's done through the official code and tweaking where needed (such as font loading and filesystem access). The code looks like this on the Lua script:
function love.load()
	print("Press 'start' to quit")

	--print("Loading font!")
	timer = 1
end

function love.update(dt)
	timer = timer - dt
	if timer < 0 then
		print("FPS: " .. love.timer.getFPS())
		timer = 1
	end
end

function love.draw()
	love.graphics.print("Adrian.. FACE REVEAL WEN?!?!?!", 120, 120)
end

function love.keypressed(key)
	if key == "start" then
		love.quit()
	end
end

The way it works is all I care about is knowing I can draw whenever. It doesn't need to be immediate. If I throw the program on the 3DS or Citra it should run without needing to draw something or having people familiar (or new) with this framework require knowledge about behind-the-scenes stuff.

You could try lazily starting the frame. Invoke love.draw(), and as soon as that method tries to use any drawing commands, start the frame. If after invoking said method a frame has been started, end it. Otherwise use C3D_FrameSync() to synchronize with the screens & keep it "60fps". You could also use the same idea to throw an error if the user script tries to use drawing commands outside love.draw().

Where would I FrameSync()? I thought Citro does that already. I'm also not sure if I can really 'detect' if the user tries to invoke a drawing command. I'll take a poke at it I guess.

citro3d does that automatically, but only if you actually use C3D_FrameBegin/C3D_FrameEnd. Otherwise you're going to have to sync manually. Where do you invoke love.draw()?

I invoke it during the aptMainLoop:
while (aptMainLoop())
	{
		if (LOVE_QUIT)
			break;

		if (!LUA_ERROR)
		{
			loveScan(L);

			if (luaL_dostring(L, "love.timer.step()"))
				console->ThrowError(L);

			for (int i = 0; i < streams.size(); i++)
				streams[i]->Update();

			if(luaL_dostring(L, "if love.update then love.update(love.timer.getDelta()) end"))
				console->ThrowError(L);

			if (CLOSE_KEYBOARD)
			{
				luaL_dostring(L, "love.keyboard.setTextInput(false)");
				CLOSE_KEYBOARD =  false;
			}

			love::Graphics::Instance()->Render(GFX_TOP);

			if (luaL_dostring(L, "if love.draw then love.draw() end"))
				console->ThrowError(L);

			/*love::Graphics::Instance()->Render(GFX_BOTTOM);

			if (luaL_dostring(L, "if love.draw then love.draw() end"))
				console->ThrowError(L);
			*/
			love::Graphics::Instance()->SwapBuffers();

			love::Timer::Instance()->Tick();
		}
		else
		{
			hidScanInput();
			u32 kTempDown = hidKeysDown();
			if (kTempDown & KEY_START)
				break;
		}
	}

Sorry for the spacing :P

Ok so you basically need to lazily call love::Graphics::Instance()->Render(GFX_TOP); the first time love.draw issues a drawing command.  SwapBuffers() (which I imagine does the FrameEnd call) should detect whether the frame has actually started - if it has, then end it; if it hasn't, use FrameSync.

I think I have the right way to do it, but my issue is most likely detecting if the frame really started. The render for GFX_TOP happens before love.draw executes. This allows for Citro to render images, primitive shapes, etc. Then it ends the frame. I don't have a way to definitely check if the user put in some rendering code.

No. I meant deferring the Render() call until love.draw actually calls drawing commands. You ought to have those drawing commands implemented in C, right? That's where you need to detect if Render() needs to be called.

Yeah the draw commands are in C. If I have to flag a Boolean in each one it's kind of hacky, tbh. I'll keep trying I guess. I was hoping there'd be a better fix.

I just had this same problem with my homebrew game, and I think I have something that works.
Before noticing this issue was here, I was looking through the commit log to see if I could find the cause. Along the way, I stumbled upon this commit.
C3D_RenderTargetSetClear is still supported, however it's unofficially
deprecated (it's performed after drawing/transferring instead of before
drawing, which is pretty counter-intuitive)

So, just to keep my code clean, I removed all uses of C3D_RenderTargetSetClear, and instead did it directly as part of my render function:
void Backend_Graphics_DrawFrame(void)
{
	aptMainLoop();		// Do this once per frame so sleeping doesn't crash
	C3D_FrameBegin(C3D_FRAME_SYNCDRAW);

		C3D_FrameDrawOn(render_target_left);
		drawing_right_eye = false;

		C3D_FrameBufClear(&render_target_left->frameBuf, C3D_CLEAR_ALL, CLEAR_COLOR, 0);	// Added line

		DrawObjects();

		C3D_TexBind(0, level_texture);
		DrawLevel();

		if (osGet3DSliderState())
		{
			C3D_FrameDrawOn(render_target_right);
			drawing_right_eye = true;

			C3D_FrameBufClear(&render_target_right->frameBuf, C3D_CLEAR_ALL, CLEAR_COLOR, 0);	// Added line

			DrawObjects();

			C3D_TexBind(0, level_texture);
			DrawLevel();
		}

	C3D_FrameEnd(0);
}

To my surprise, the crashes stopped happening.

Might as well add that calling C3D_FrameSplit() is necessary before doing any kind of external operation to a rendertarget's framebuffer if (and only if) you have previously drawn anything to it in the current frame. In the code posted above this call isn't necessary since the framebuffer is cleared before it is being drawn to.

So just basically clear the FrameBuffer rather than SetClear?

I'm being bitten by this right now too, FYI. Not all code is as simple and straightforward as you assume and telling someone "well just refactor it to make it more straightforward" is not exactly a solution.

I agree with @endrift since there shouldn't be a reason it softlocks using this function if nothing is there. Regardless, just using FrameBufClear works and doesn't cause a soft lock before drawing, but the color format to clear is different than expected.

Just experienced this issue for myself. Render a frame, draw nothing, GPU crash (no crash handler, just hang). The context was me trying to clear the framebuffer to prevent issues with APT_DoApplicationJump (In which it gets weird and renders your last frame but in a funky way while jumping). Simply drawing a black rectangle does what I need (clearing the framebuffer would work too), but just keep in mind that more people are going to run in to this.


Maya: fix the bug of not being able to find ocio_path in extract look

Changelog Description
fix the bug of not being able to find ocio_path in extract look and errors out in the extractor
Additional info
n/a
Testing notes:

Create Look Instance
Disable Color Management in preference setting and swtich maketx setting on
Publish it

@moonyuet is this still valid with https://github.com/ynput/OpenPype/pull/4711 merged?

@moonyuet is this still valid with #4711 merged?

No, #4711 is the updated version so I will close it now.


via remote driver creates one network: admin, start a container with network admin, but got two IP, one is from admin, other is from a bridge which is automatically created

as title, i create a network: admin via remote driver, and start a container(docker run --rm -ti --net=admin busybox sh) with network admin, but got two IP, one is from admin, other is from a bridge which is automatically created by system. in fact, i want to get only one IP which should be from admin, how can avoid this?
============================
~ # ifconfig
eth0      Link encap:Ethernet  HWaddr FA:16:3E:A7:D6:70
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: fe80::f816:3eff:fea7:d670/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1038 (1.0 KiB)  TX bytes:858 (858.0 B)
eth1      Link encap:Ethernet  HWaddr 02:42:AC:12:00:02
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: fe80::42:acff:fe12:2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1170 (1.1 KiB)  TX bytes:648 (648.0 B)
lo        Link encap:Local Loopback
inet addr:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Libnetwork is about to providing an DisableGatewayService option in JoinResponse to disable default gateway bridge network, you can take at https://github.com/docker/libnetwork/pull/778

cool


Maintaining

@RRMoelker Are you interested in maintaining this package? I (and @alexhayes) made some small additions and improvements which could benefit others as well.
I don't really want to push a fork to PyPi, so I would be glad to take over maintenance of your package.

Hey, I'm on holiday right now. I'll look into it later this week.
On Jul 31, 2017 23:28, "Erwin Matijsen"<EMAIL_ADDRESS>wrote:
@RRMoelker https://github.com/rrmoelker Are you interested in maintaining
this package? I (and @alexhayes https://github.com/alexhayes) made some
small additions and improvements which could benefit others as well.
I don't really want to push a fork to PyPi, so I would be glad to take over
maintenance of your package.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RRMoelker/django-markdownify/issues/3, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAMiDoeI7XrgMJCq9qP425Qnpj0FjuDOks5sTkbfgaJpZM4Oo80Q
.

Ok, thanks. I made a PR, so you can see the differences.

Nice PR. I'm no longer using Django, so I'm happy to hand over maintenance. Can you message me your Pypi account? I'll try to pass package control over to you, @erwinmatijsen.
As for the GitHub repo. I'm not sure what the best approach is. Either I redirect people to your fork or I add you as collaborator. I'm guessing my repo will be the first hit in Google. So shall I simply add you as admin?

Thanks. I'm evosites on Pypi. I think me collaborating on this repo would be best.

Alright, you should have access. If you need anything else please ask.
Bedankt en succes ;)

Haha, bedankt!


signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) pthread_mutex_lock sqlite3_finalize

Xamarin Android App that we released about 2 months ago.  We have been working through crashes and fixing them and now we are down to this one:
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
pthread_mutex_lock

backtrace:
  #00  pc<PHONE_NUMBER>047a06  /system/lib/libc.so (pthread_mutex_lock+1)
  #01  pc<PHONE_NUMBER>010087  /data/app/com.myapp-2/lib/arm/libe_sqlite3.so (sqlite3_finalize+26)
  #02  pc<PHONE_NUMBER>033794  <anonymous>

Any ideas what is going on here or how to track this down?  We are on sqlite-net-pcl 1.5.166-beta.

You are using a beta version. Consider using a stable version instead ?

@jwidmer I am getting exactly the same crash
#00 pc 00048576  /system/lib/libc.so (pthread_mutex_lock+1)
#01 pc 00010087  /data/app/com.myapp.droid-1/lib/arm/libe_sqlite3.so (sqlite3_finalize+26)
#02 pc 0000ccac  <anonymous:ccd2e000>

@Weldryn What beta version are you referring to?
I am using sqlite-net-pcl v1.4.118

The next release is going to bump SQLitePCLRaw to 1.1.11 - it handles the low-level access to the database and will hopefully fix your code.
Would you try updating those packages and report if you have the same problem?

Recently we have been considering updating our app to Entity Framework Core 2.1 (Microsoft.EntityFrameworkCore.Sqlite).  EntityFrameworkCore.Sqlite also uses SQLitePCLRaw 1.1.11.  How confident are you that the issue was related to the version of SQLitePCLRaw?  I would like to recommend to just update to latest of SQLite-net-pcl (and therefore SQLitePCLRaw 1.1.11) but everyone else wants to move to EntityFrameworkCore.  If we can get this issue fixed by just updating to latest of SQLite-net-pcl then I am pretty sure we will just do that.  Any opinion?


Add is_soundbar property and support all soundbars

Fix support for Playbar, and add for Playbase and Beam.
Fix #633

+1 :+1:
I really like the extracted property, removing that quadruplicate code.

One minor nitpicky suggestion: I'd move SOUNDBARS to the bottom, together with NS and PLAY_MODES.

@ghcs27 great suggestion. I hadn't noticed that there was a section for constant definition in the file. I've moved it, and also changed the detection to endswith() instead of in to avoid the possibility that some future product has e.g. the word "beam" elsewhere in it.

doh! broke tests. working on that now.

Tests (hopefully) fixed

Great work! If there are no objections, I will merge this next week.

Thanks for taking a look!

Merged! Thank you for your contribution, @pmac!
Please do not forget to add a summary of the changes to the release notes in #629!

Please do not forget to add a summary of the changes to the release notes in #629!

Done. Thanks again!


Add inspect tool

Start of a lower-level file inspection tool.  This currently dumps
summary statistics for the shards, index and WAL that can be used to
understand the shape of the data is in the local shards.  This util
operates on the shards itself and not through the server and is intended
more for debugging/troubleshooting.
Sample output after run influx_stress:
Shards: 1, Indexes: 1, Databases: 1, Disk Size: 536870912, Series: 100000

DB           Measurement  Tags [#K/#V]   Fields [Name:Type]  Series
stress       cpu          2/100001       1 [value:float64]   100000

:heart:

Any reason not to merge this today?  +1

@jwilder I'd love to get an overview or even a tech talk for the support team so that we understand what we can do with this tool. Or is it too low level to provide useful data for us?

It will be useful for support in the future but there is not much to it yet.  Just run inspect or inspect -h to see the (one) option.  The idea is to add support for the other file types we store to aid in troubleshooting storage related issues.  It might also be useful as a step for logging issues so that we can get more consistent data around DB size, cardinality, OS, versions, etc.. when issues are logged. (i.e someone could just run inspect -p /var/lib/influxdb and attach that to the issue to help us out).


Allow private classifier

On https://pypi.org/classifiers/ it says to mark a package with a Private :: classifier to prevent it from being uploaded to PyPI.
Unfortunately that makes pyroma complain about it:
Some of your classifiers are not standard classifiers:
Private :: Do Not Upload

Would it be possible to ignore classifiers that start with Private :: ? 🍀

Yup, that should be easily doable.

Please see PR https://github.com/regebro/pyroma/pull/106.


[Windows] Add 10 21H2

Dates from here: https://docs.microsoft.com/en-us/windows/release-health/release-information

@BiNZGi
Could you add missing parts for W and E ?
I mean out (E) doesnt have Pro Education also our (W) doesnt have "and IoT Enterprise " parts

@usta good hint, thx, I'll add it...

If i am not wrong SAC doesnt exist any more ( they moved it to Annual channel like w11 ) , could you check those and if i am right we need to remove all SAC part in information

If i am not wrong SAC doesnt exist any more ( they moved it to Annual channel like w11 ) , could you check those and if i am right we need to remove all SAC part in information

You are right, I just checked and removed it from file.

LGTM. merging


Is this project alive?

Hi,
This project has not had any activity for more than two years and links redirects to other pages.

there are 3 Frameworks as i knew based on fasthttp (atreugo/fiber/gearbox) ,
They are homogenous and almost the same in many aspects . you can choose the other two


fix: Windows Ruby 3.1 Native Extensions Installs

A change in<EMAIL_ADDRESS>rubygems, and/or<EMAIL_ADDRESS>is preventing native extensions both sqlite3 and nokogiri on Windows.
I tried a few different incantations to force bundler to load platform specific versions of x64-mingw-ucrt, however all attempts fell short in some way.
Locking the bundler version to 2.3.22 was the only way I could get the native extensions to install.
This is a temporary fix until we can figure out what changed in the bundler ecosystem to cause this issue.
cc: @johnnyshields

@arielvalentin can you point me to the original test run that's failing and the error you are seeing?

@deivid-rodriguez

@johnnyshields @deivid-rodriguez Here are some examples:
https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/3214758698/jobs/5255371768
https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/3214758698/jobs/5255371805
https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/3214758698/jobs/5255371859
https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/3214758698/jobs/5255371939

@arielvalentin recommend you to raise an issue with Rubygems.

Hi, it has already been raised several times, I kept this one opened: https://github.com/rubygems/rubygems/issues/5970. There's already a fix proposed at https://github.com/rubygems/rubygems/pull/5975. I recommend to stick to 2.3.22 until I release that.


#147 Update Swift 2.3 and Xcode8

Status
READY
Migrations
NO
Description
The PR provides support for Swift 2.3 and Xcode 8.
Changes to the project have been made and code adjusted to Swift 2.3.
Todos

[ ] Remove ++ from Unit Tests as it's deprecated and it will be removed on Swift 3

Not sure why it says checks passed as the tests failed since it's running on Xcode 7.1 Updating .travis.yml now


fix(CodeBlock): Load synchronously

The async Prism implementation grants a smaller bundle size upfront, but it also seems to defer rendering of our code block container styling. This manifests as ugly pop in which is not present when using the sync version.

Example of aforementioned pop-in on https://developer.seek.com/auth/partner-tokens:


added type check test

Description
Fix for bug introduced in #3507

Processing this pull request

Pull request rejected by merge tool. The tests for this branch did not succeed.

Merged into branches master in 9fa73976cbf2b80ca7da9e73cc354d4685f629a9

Processing #3509.


New: added tests for banners

This PR contains nala tests for renew banners.
Test cases are defined here: Banners test cases

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.58%. Comparing base (bcc585e) to head (a37f0e6).

Additional details and impacted files
@@            Coverage Diff             @@
##            stage      #49      +/-   ##
==========================================
+ Coverage   78.54%   78.58%   +0.03%
==========================================
  Files          10       10
  Lines        3086     3086
==========================================
+ Hits         2424     2425       +1
+ Misses        662      661       -1

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


Update generate_images_with_stable_diffusion.py

Right now the padding is one character short of being a nice table.

@fchollet done


appveyor is installing gofish 0.2.0 instead of the canary release

We need a way to inject the desired version into the install script.

closing as intended. We want to make sure we're testing against the latest stable release of gofish rather than the canaries.


Can't play web development leve's

I can't play those levels, I've tried it with a lot of browsers. That the error I get:

Hi @AldairReis, this is a really frustrating issue, and I have been looking into it. This screenshot is really useful for finding the issue!
It is specifically for connections from Brazil. Until this has been resolved, you can get around it by using a VPN. You can use a VPN to set your country to a different country than Brazil, and then the connection would work.
We are working on a fix so using a VPN is not necessary. I'll report back here once the issue has been fixed 👍

I've made some code changes in our various repositories that should fix this. It's not live yet, but it will be deployed sometime later this week (probably sometime on Tuesday). After that goes up, there should be no more issues for web development in Brazil.


No error for incompatible neovim versions

Silently discards align_csv commands from incompatible neovim client versions.

Yes, you're absolutly right, a proper error message would be more appropriate. Unfortunately that's not what we currently have, the error is something like "wrong virt_text_pos argument".

If you make a pr to display an error message for older versions when the function is invoked i'd merge it

Now this should do the trick

ah, i would put the check only in one place, two max. maybe the setup call, but since it's optional, also in the align function. you're not going to call directly next/previous column or unalign, you're gonna call align beforehand. probably you agree?

Ok,fixed, only checking in setup and align_csv.


Wrong floating text

Issue description

Expected result: What were you expecting to happen? That the /p buy does not appear if the plot is not for sale by another player
Actual result: What actually happened? If the player claims a plot in this new version, another player enters and it will appear that he can buy it (without the other player having put it up for sale)

Steps to reproduce the issue

Update MyPlot to the latest version
A player buys a plot
If another player enters inside, it will appear that he can buy it
(This is only visual, if the player puts the command / p buy the following message will appear "You can't buy a plot from yourself" (The message is also wrong because the plot is not from that player)

OS and versions

Plugin Version: Dev #655
PocketMine-MP: 3.15.2
PHP: 7.3
Game version: PE/Win10

Other Plugins

If you remove all other plugins, does the issue still occur? I dont know
If the issue is not reproducible without other plugins:

Have you asked for help in the community discord before creating an issue? No
Can you provide sample, minimal reproducing code for the issue? If so, paste it in the bottom section.

Console error, backtrace or other files

Same problem

fixed in 2d8adaffe983dcee4c96c0157a81073ed4a31bb9

Tomorrow I test it, I'm going to sleep

The parcels that were purchased in the past version still have the visual error.
The plots that are bought new work correctly and put the correct message.
#Dev658
@jasonwynn10

Please clarify what you mean

Plots that have been purchased with version # 655 # 656 and # 657 have the wrong text when you enter.
But those that are purchased now in version # 658 work correctly

Ok so it is resolved then 👍


No way to document parameters

New django-rest-swagger versions have deprecated YAML docstrings. There's no documentation demonstrating how to document request fields anymore.
There's some things you can do by changing the filter_backends on ViewSets, for example, but it just doesn't feel right.
I still haven't found a way to do this on function based views.

It also seems that coreapi is less descriptive than openapi so the openapi schema will be incomplete since we generate from rest_frameworks coreapi document (via https://github.com/core-api/python-openapi-codec). I need the ability to specify response codes and bodies.  IIUC the old way to get around this was with YAML docstrings but those are deprecated.

I still do not know how to document parameters.
Hope there will be an example in the tutorial app.

I write a custom schemagenerator to deal with parameter:
class SchemaGenerator(schemas.SchemaGenerator):
    def get_link(self, path, method, callback, view):
        """Custom the coreapi using the func.__doc__ .

        if __doc__ of the function exsit, use the __doc__ building the coreapi. else use the default serializer.

        __doc__ in yaml format, eg:

        desc: the desc of this api.
        ret: when success invoked, return xxxx
        err: when error occured, return xxxx
        input:
        - name: mobile
          desc: the mobile number
          type: string
          required: true
          location: form
        - name: promotion
          desc: the activity id
          type: int
          required: true
          location: form
        """
        fields = self.get_path_fields(path, method, callback, view)
        yaml_doc = None
        func = getattr(view, view.action) if getattr(view, 'action', None) else None
        if func and func.__doc__:
            try:
                yaml_doc = yaml.load(func.__doc__)
            except:
                yaml_doc = None
        if yaml_doc and 'desc' in yaml_doc:
            desc = yaml_doc.get('desc', '')
            ret = yaml_doc.get('ret', '')
            err = yaml_doc.get('err', '')
            _method_desc = desc + '
' + 'return: ' + ret + '
' + 'error: ' + err
            params = yaml_doc.get('input', [])
            for i in params:
                _name = i.get('name')
                _desc = i.get('desc')
                _required = i.get('required', True)
                _type = i.get('type', 'string')
                _location = i.get('location', 'form')
                field = coreapi.Field(
                    name=_name,
                    location=_location,
                    required=_required,
                    description=_desc,
                    type=_type
                )
                fields.append(field)
        else:
            _method_desc = func.__doc__ if func and func.__doc__ else ''
            fields += self.get_serializer_fields(path, method, callback, view)
        fields += self.get_pagination_fields(path, method, callback, view)
        fields += self.get_filter_fields(path, method, callback, view)

        if fields and any([field.location in ('form', 'body') for field in fields]):
            encoding = self.get_encoding(path, method, callback, view)
        else:
            encoding = None

        if self.url and path.startswith('/'):
            path = path[1:]

        return coreapi.Link(
            url=urlparse.urljoin(self.url, path),
            action=method.lower(),
            encoding=encoding,
            fields=fields,
            description=_method_desc
        )

@daimon99, on list routes, you can set the filter_backends property on the ViewSet to correctly generate the schema, still it feels a little hacky.

just wait rest framework 3.5. tomchristie  said: "Gothca, understand the issue now! Yes, this has been an issue in how we generate the schema for swagger UI. It's resolved as part of the upcoming 3.5 release."

https://github.com/tomchristie/django-rest-framework/issues/4241.

So no updates yet regarding this issue??

Given that the 3.5 release is out, has this ticket been handled?

Maybe mentioning @tomchristie ?

There's some level of support for this, but it's a little patchy.
You'd need to look at the implementation of get_link() to see how the fields are built up. The description attribute on fields can then be pulled out by the swagger UI renderer...

Serializer fields (request body/form) have the help_text attribute pulled into the description.
Filter fields and pagination fields (query params) have whatever get_schema_fields returns (currently won't populate any field descriptions, tho you could override this)
URL path fields have no way of setting a description.

Does CoreAPI even support custom type definition? I know you can specify anything in the field.type.
I think you would need to change rest_framework_swagger.renderers.OpenAPICodec so that the returned Swagger object would be extended with definitions:.
Those definitions could be somehow pushed to coreapi.document.Document with SchemaGenerator maybe.
The coreapi.document.Document seem to be accepting any data.
class Document(itypes.Dict):
    # ...
    self._data = {key: _to_immutable(value) for key, value in content.items()}

@slykar - I think you're mixing up different concerns in that comment. (What datatypes can be included in a Document, vs. how do we describe parameter help text and parameter types.
I'm currently working on a documentation generator to tie in with Core API, which is helping tease out some of the docs related requirements. I'd suggest we hold further discussion until we can use that as a starting point.
Aside: Also worth re-iterating that I want to see any spec changes to Core API be driven by very explicit tooling requirements. Eg. "Adding X to Core API will allow me to do Y".

@tomchristie - To give some background. What I was trying to achieve was a documentation of profile parameter on my endpoint, which is an embedded document with it's own schema. SchemaGenerator specifies the type as 'object', where it should be a type on it's own, like 'UserProfile'.
When using OpenAPI, you can document such field by setting custom type. In OpenAPI this type is defined by definitions section. This is something you can not do with CoreAPI as far as I know, even tough the CoreAPI Field.type takes arbitrary string and you could put 'UserProfile' there.
The spec mismatch makes it hard to properly document endpoint parameters, utilizing OpenAPI type definitions. This is something I require, otherwise the generated OpenAPI spec is worthless for me.
Right now I'm back to writing the OpenAPI spec file by hand.

Gotcha. And yes, we may well move towards allowing for annotation information about more complex types. Out of interest what tooling are you using to document the API - Swagger UI, or something else?

@tomchristie I'm using Swagger UI, tough, when writing spec by hand I write it using API Blueprint (IMO easier to write and read than OpenAPI), then convert it to OpenAPI spec for Swagger UI.

Hey guys any update on this issue?

Yeah upcoming version of REST framework is working towards improving this.

look forward to the new version of REST framework!
for the time being i'm using this class decorator:
https://github.com/ministryofjustice/moj-product-dashboard/blob/develop/dashboard/libs/swagger_tools.py#L5
use case:
https://github.com/ministryofjustice/moj-product-dashboard/blob/develop/dashboard/apps/dashboard/views.py#L106

@cliffxuan Interesting solution.
@tomchristie What are your plans for the next version? Would you consider extending the override methods like get_path_fields and get_filter_fields currently on the schema generator onto APIView?

@cliffxuan  https://github.com/marcgibbons/django-rest-swagger/issues/549#issuecomment-276993383
Your solution works fine for list action. what if we want to customize that at action level, i.e i want a specific query param for retrieve method or update or create method for that matter. How are we going to do that. can we modify your decorator to support at method level?

@gjain0 my decorator works only for list view. i don't have a use case for yours yet. feel free to modify it.

Has this issue been addressed in any way over the past 8 months?  It appears that currently there is no concise readable way to specify parameters for API endpoints, which effectively renders Swagger as useless.

@FilmCoder  I'm using @daimon99 solution. modified for my use case.
It's working perfect.
here is the complete code
https://gist.github.com/gjain0/f536d3988eb61e693ea306305c441bb7

It really is mind boggling that this issue remains open after all this time.

Using help_text on Serializer works great for parameters - but I'm still missing a way to add a description to the Path parameters.
Would be great if that could be implemented!

If all you care about is showing parameter types, is required or optional, and help_text, the "Model" view on the swagger page is an easy alternative, as described here: http://idratherbewriting.com/2015/12/10/ten-realizations-using-swagger-and-swagger-ui/
Pros: Can be implemented with just Serializers and isn't a hack.
Cons: Bad at displaying request data's nested objects and lists.

@bwmello , this is about documenting input parameters and (more importantly) the ability to enter parameter content within swagger. Your page suggests using markdown, but this ability was removed when the software went to coreAPI, without any viable replacement. This thread is not related to documenting the output parameters, which is what your page also describes.

Hi,
Any update on this issue ?

Bizarre that a documentation tool for an API, doesn't- wait for it- allow you to document parameters. Kinda like a car that doesn't drive, or a plane that doesn't fly. Can I have the past hour of googling in disbelief back?
Here's my workaround, param_schema.py --
from rest_framework.compat import coreapi, coreschema
from rest_framework.filters import BaseFilterBackend

class ParamSchemaFilter(BaseFilterBackend):
    def get_schema_fields(self, view):
        assert coreapi is not None, 'coreapi must be installed to use `get_schema_fields()`'
        assert coreschema is not None, 'coreschema must be installed to use `get_schema_fields()`'
        fields = super().get_schema_fields(view)
        if hasattr(view, 'get_param_fields'):
            print(view)
            fields += view.get_param_fields(view)
        return fields

And in your settings --
REST_FRAMEWORK = {
    ...
    'DEFAULT_FILTER_BACKENDS': (
        ...
        'param_schema.ParamSchemaFilter',
    ),

And in your view/viewset --
class MyAwesomeView(viewsets.GenericViewSet):

    def get_param_fields(self, view):
        fields = [
            coreapi.Field(
                name='my_field',
                required=True,
                location='query',
                schema=coreschema.String(
                    title='My awesome field',
                    description='This is my really awesome field right here, so awesome'
                )
            ),
        ]
        return fields

Seems like things are moving forward: https://github.com/encode/django-rest-framework/issues/4502

Hi all, I have recently integrated Django Rest Swagger 2 into an existing project, I faced alot of issues, and resolved them by finding solutions at different forums. Now I have documented all the required steps here: https://github.com/m-haziq/django-rest-swagger-docs  with all possible issues I could face and their solutions.

This is the way to go: https://github.com/axnsan12/drf-yasg

There are currently two decent Swagger schema generators that I could find for django-rest-framework:
django-rest-swagger
drf-openapi
Out of the two, django-rest-swagger is just a wrapper around DRF 3.7 schema generation with an added UI, and thus presents the same problems. drf-openapi is a bit more involved and implements some custom handling for response schemas, but ultimately still falls short in code generation because the responses are plain of lacking support for named schemas.

Is anyone currently working on this?

@gregorypease280  yes I am. Try reading  https://github.com/m-haziq/django-rest-swagger-docs

For people interested by making swagger work with the last version of django rest framework (3.7.7), you'll notice the tweak gave by @daimon99  in this comment https://github.com/marcgibbons/django-rest-swagger/issues/549#issuecomment-250145712 which I used is no longer working.
I've just ported the new code for making it work with django rest framework 3.7.7 and django rest swagger 2.1.1
Create a file schema_view.py:
from django.utils.six.moves.urllib import parse as urlparse
from rest_framework.schemas import AutoSchema
import yaml
import coreapi
from rest_framework_swagger.views import get_swagger_view

class CustomSchema(AutoSchema):
    def get_link(self, path, method, base_url):

        view = self.view
        method_name = getattr(view, 'action', method.lower())
        method_docstring = getattr(view, method_name, None).__doc__
        _method_desc = ''

        fields = self.get_path_fields(path, method)

        try:
            a = method_docstring.split('---')
        except:
            fields += self.get_serializer_fields(path, method)
        else:
            yaml_doc = None
            if method_docstring:
                try:
                    yaml_doc = yaml.load(a[1])
                except:
                    yaml_doc = None

            # Extract schema information from yaml

            if yaml_doc and type(yaml_doc) != str:
                _desc = yaml_doc.get('desc', '')
                _ret = yaml_doc.get('ret', '')
                _err = yaml_doc.get('err', '')
                _method_desc = _desc + '\n
' + 'return: ' + _ret + '
' + 'error: ' + _err
                params = yaml_doc.get('input', [])

                for i in params:
                    _name = i.get('name')
                    _desc = i.get('desc')
                    _required = i.get('required', False)
                    _type = i.get('type', 'string')
                    _location = i.get('location', 'form')
                    field = coreapi.Field(
                        name=_name,
                        location=_location,
                        required=_required,
                        description=_desc,
                        type=_type
                    )
                    fields.append(field)
            else:
                _method_desc = a[0]
                fields += self.get_serializer_fields(path, method)

        fields += self.get_pagination_fields(path, method)
        fields += self.get_filter_fields(path, method)

        manual_fields = self.get_manual_fields(path, method)
        fields = self.update_fields(fields, manual_fields)

        if fields and any([field.location in ('form', 'body') for field in fields]):
            encoding = self.get_encoding(path, method)
        else:
            encoding = None

        if base_url and path.startswith('/'):
            path = path[1:]

        return coreapi.Link(
            url=urlparse.urljoin(base_url, path),
            action=method.lower(),
            encoding=encoding,
            fields=fields,
            description=_method_desc
        )

schema_view = get_swagger_view(title='Product Testing API')

Your urls.py file references it like:
from .schema_view import schema_view

urlpatterns = [
    url(r'^v1/api/', include([
        url(r'^doc/', schema_view),
    ])),

No the sad part is that you have to override all your APIView or ModelViewSet with
schema = CustomSchema()

as described in the 3.7.7 release : http://www.django-rest-framework.org/api-guide/schemas/#per-view-schema-customisation
@m-haziq Hope it will help for making the migration in your README file ;)

There are also problems with adding parameters to function-based views, like this:
def register(request):
    #read parameter "code" and check it
    response_data = {'code': 'success.', 'token': 'sometoken'}
    return Response(response_data, status = status.HTTP_201_CREATED)

how to add "code" from here to swagger I can't find. Unfortunately, don't have enough time to work on it and post an answer, so maybe someone else will post the answer here.

@GuillaumeCisco Great. Thanks for sharing it, I will definitely take some time out of my routine to add this update to my documentation sometimes soon!

@Swich1987 Please read this part of doc. You can document FBVs smoothly: https://github.com/m-haziq/django-rest-swagger-docs#advance-usage


⚠ Bofrost.de has degraded performance

In 79b27ce, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1390 ms

Resolved: Bofrost.de performance has improved in e3b9e1f.


fix the table cell line-wrapping problem in the docs

pretty easy one, just needs a little fiddling with a css file really

marking as done


Throws Unknown key for unique nbt.

This is not limited to ActiveEffects, but all unique NBT tags (eg ArmorItems, Inventory, Duration, etc.).

It requires a lot of work to fix this bug permanently; I'd like to just downgrade the severity of this diagnostic from warning (yellow line) to hint (short gray line)

:tada: This issue has been resolved in version 2.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Reopen for now, in case I want to fix this thoroughly in the future

:tada: This issue has been resolved in version 2.1.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Better labels

Our labels are somewhat unspecific and sad.  If we can break things up into more component-wise labels and have priority labels, and use a labelling scheme like Hyper's, I think it'd be much easier to label issues.

idc enough so I'm gonna leave this to you

Closing because I finished this.  I'm totally open for further suggestions as far as this labelling scheme should go; my only qualms about it have to do with searchability and conciseness, but I think that having thing split up by prefix (e.g. Concerns:, Is:) helps with this and helps make the labels more easy to understand.

And for future references, here's the philosophy behind each of these labels and the groupings I created for them.  I will copy-paste this into the Issue body so that we have this, and we could put this in CONTRIBUTING.md or some other file.
Concerns
The Concerns set of labels is used for demarcating the scope of the Issue or Pull Request to which they are assigned.

Concerns: Dot

For Issues concerning the project as a whole

Concerns: Emacs Configuration

For Issues concerning the Emacs Configuration as a whole (but not the entire project, Dot.)

Concerns: Emacs/tree/behavior

For Issues concerning stuff in the behavior tree of the Emacs configuration

Concerns: Emacs/tree/code

For Issues concerning stuff in the code tree of the Emacs configuration

Concerns: Emacs/tree/file

For Issues concerning stuff in the file tree of the Emacs configuration

Concerns: Emacs/tree/package

For Issues concerning stuff in the package tree of the Emacs configuration

Concerns: Emacs/tree/user

For Issues concerning stuff in the user tree of the Emacs configuration

Concerns: Emacs/tree/visual

For Issues concerning stuff in the visual tree of the Emacs configuration

Is
The Is set of labels is used to describe the status or quality of the Issue or Pull Request to which they are assigned.

Is: Blocked

For Issues or Pull Requests that cannot be continued until another Issue or Pull Request is resolved

Is: Deferred

For Issues or Pull Requests that are side-lined until further notice (see: Is: On Hold for another option)

Is: Duplicate

For Issues or Pull Requests whose scope and concerns match an extant Issue or Pull Request that has not yet been resolved

Is: Invalid

For Issues or Pull Requests that are poorly-written or otherwise deemed invalid

Is: Not Fixable

For Issues which cannot be fixed

Is: On Hold

For Issues or Pull Requests that are side-lined but may be resumed soon (see: Is: Deferred for another option)

Is: Question

For Issues that are formulated as questions and are not direct requests

A Question label might be used for something hypothetical, but a separate issue should be opened once a decision is reached to specifically track the progress towards resolving the decision.

Note: This is not a label of the Type set because that set is specifically designated for

Needs
The Needs set of labels is used to describe is used to describe those Issues or Pull Requests which need further action in order to proceed.

Needs: Discussion

For Issues or Pull Requests that need discussion in order to proceed

Needs: Implementation

For Issues or Pull Requests that need (further) implementation to take place in order to proceed

Needs: Investigation

For Issues or Pull Requests that need (further) investigation to take place in order to proceed

Needs: Refactoring

For Issues or Pull Requests that need (further) refactoring to take place in order to proceed

Needs: Research

For Issues or Pull Requests that need (further) research to take place in order to proceed

Priority
The Priority set of labels is used to describe the approximate priority of the Issue or Pull Request to which they are assigned.

Priority: Critical

For Issues or Pull Requests considered to be at extremely high priority

e.g. Issues or Pull Requests where direct action is required to solve problems

Priority: High

For Issues or Pull Requests considered to be at high priority

e.g. Issues or Pull Requests where direct action is strongly preferred over other Issues or Pull Requests

Priority: Medium

For Issues or Pull Requests considered to be at medium priority

e.g. Issues or Pull Requests where direct action is weakly preferred over other Issues or Pull Requests

Priority: Low

For Issues or Pull Requests considered to be at low priority

e.g. Issues or Pull Requests where direct action is not preferred over other Issues or Pull Requests

Type
The Type set of labels is used to describe the type of thing that is concerned by the Issue or Pull Request to which they are assigned.

Type: Bad Code Style

For Issues concerning bad code style

Type: Bad Feature

For Issues concerning bad features (see: Type: Bug for another option)

e.g. Issues or Pull Requests where existing code improperly uses the system

Type: Bad Implementation

For Issues concerning bad implementation of a feature

Type: Bad Performance

For Issues concerning bad performance

Type: Bug

For Issues concerning bugs (see: Type: Bad Feature for another option)

e.g. Issues or Pull Requests where the system influences bad behavior in the codebase

Ungrouped
These labels are specifically ungrouped so that they can be searchable by API bots.

Help Wanted

Anything where outside help is wanted

goddamn

tbh probably bouta tag everything wrong bear with me

Just look at the descriptions here if you're confused at any point. Hopefully this will be a bit more semantic


MAINT: backports for 1.3.3

Backports:
#11034
1.3.3 will aim to fix the Python 3.8/Windows multiprocessing issues in the test suite & the DLL problem fixed in wheels repo: https://github.com/MacPython/scipy-wheels/pull/59
@ilayn @rgommers

Do release notes look "ok" for this single PR backport/release?
The merge conflicts were pretty brutal, so do skim over (the noise from apparent whitespace changes isn't helpful here either)

==================================== ERRORS ====================================
_ ERROR collecting build/testenv/lib/python3.6/site-packages/scipy/_lib/tests/test__util.py _
scipy/_lib/tests/test__util.py:77: in <module>
    @pytest.mark.skipif(get_start_method() != 'fork',
E   NameError: name 'pytest' is not defined
_ ERROR collecting build/testenv/lib/python3.6/site-packages/scipy/_lib/tests/test__util.py _
scipy/_lib/tests/test__util.py:77: in <module>
    @pytest.mark.skipif(get_start_method() != 'fork',
E   NameError: name 'pytest' is not defined

something got lost here

Release notes LGTM

Reproduced/fixed locally---we'll see if CI agrees..

Backport CI is all green, so in it goes.
I remain slightly paranoid that the fix may be affected by merge conflict complications, but the skips are in there it seems.


Django remote forms syntax correction

So, my context is the following: I was implementing the django-remote-forms on a Django project and the library ended up crashing several times, until I considered doing some code updates to the own library.
This pull request basically contains some simple syntax changes that helped me with the code.

Why hasn't this been merged?


Material with the same name don't convert correctly.

We got a gltf with 3 meshes, each uses a different material.
Those 3 materials have the same name in the glTF file. (As per the spec, the material name can be the same or even omitted)
The USDZ generated uses the same material for all 3 meshes.

@sayduck-daniel I just merged a fix which appends the index to the material names: https://github.com/kcoley/gltf2usd/pull/148


Remove "illegal" UnsafePointer casts from the stdlib.

This replaces:
https://github.com/apple/swift/pull/3824
Update for SE-0107: UnsafeRawPointer
This adds a "mutating" initialize to UnsafePointer to make
Immutable -> Mutable conversions explicit.
These are quick fixes to stdlib, overlays, and test cases that are necessary
in order to remove arbitrary UnsafePointer conversions.
Many cases can be expressed better up by reworking the surrounding
code, but we first need a working starting point.

I'm putting this up for another review.
This still needs to be updated for the linux build. I'll fix that.
Also, RaceTest and AnyHashable are failing due to String initializers. I'm not sure if that's related to my changes.

Also, RaceTest and AnyHashable are failing due to String initializers. I'm not sure if that's related to my changes.

@CodaFi was working on those.

Changes LGTM, thank you!

@swift-ci Please smoke test.

@gribozavr Please merge (so I can move on with another PR before the next commit conflicts).
I don't know what the problem is with this package manager test:
swift-package-tests :: swift-package-init-lib.md
TEST 'swift-package-tests :: swift-package-init-lib.md'

@atrick That issue is now taken care of (Thanks @abertelrud!). So in the future, you should no thave this issue.

If there are no conflicts (there weren't any an hour ago), then this should be merged. There's no point clogging the build queue any further.


LiteralField and LabelField do not have padding when inline editing

If you have an element which uses a LiteralField or LabelField, that field is rendered without any padding during inline-editing, causing it to site hard against the left of the container.

Using ->addExtraClass('form__field-label') on the field gives the container (or label) a class with the padding to match the rest of the form, but I'm not sure if this is an expected behaviour for these field types.

Hmm, this could be a core issue. Let me investigate.

Yeah I've had a look at this. Definitely an elemental issue. We apply the "row" class (that adds negative margins) too early from the looks of things. We apply it to the whole form where-as it is applied on the form group level in other parts of the CMS. Elemental then zero's out the margin on form groups.
Probably needs to rebalance where we apply margins.

Partial revert of https://github.com/dnadesign/silverstripe-elemental/pull/489 fixes this, PR at https://github.com/dnadesign/silverstripe-elemental/pull/694

Fixed in 4.1.x (#694)