Migrating to PML 2.3.0/3.0.0

@pml-lang, I've now started a new dev branch for the package migration to PML 2.3.0/3.0.0:
https://github.com/tajmone/Sublime-PML/tree/pml-2.3.0-3.0.0
This branch basically picks up from the previous migration work to PML 2.3.0 but (as discussed via email) I will be dropping many features since the braking changes of the new PML 2 parsing system are better dealt with a fresh rewrite of the package.
PML 3.0.0 ETA?
You didn't provide me with an ETA for the upcoming PML 3 release, but in any case I think the best approach right now is to focus on quickly migrating the package to support PML 2.3.0, and then deal with the breaking changes of PML 3 when it's finally out (so I can actually use it while working on the package).
That said, it's worth keeping track of the breaking changes of PML 3, and simply drop any elements that would require too much adaptation.
Migration Roadmap
I was hoping to have the new package ready and released by the weekend, although I don't have a clear picture of how much work there's left toward this goal.
In any case, these are the repository documents that I'm using to track the migration work:

SYNTAX_STATUS.md — the current migration-status document.
SYNTAX_STATUS_OLD.md — the old package status from the latest public version (PML 1.5.0).
PMLv2_MIGRATION.md — the previous PML 2.3.0 migration dev notes, listing the done and pending changes (the TODOs might no longer apply now that I'm planning dropping features).

Right now the motto driving the update is "Less is more" — in the past, I've ended up being trapped in a loop of ever-changing features, where before I could manage to update the package to the latest PML release a new release with breaking changes came about, invalidating my previous work.
One way or the other, this package ended up being stuck to PML 1.5.0; so if we want to catch up with the latest PML evolution, the best approach is to disentangle the package by dropping out any features which are preventing the update, and simply re-implement them later on (having a lesser package is better than having no usable package at all).
Support Needed
I'd like to use this Issue thread to consult you and discuss any decision regarding the best strategies for the migration work — which nodes are worth keeping and which ones to drop, and so on.
Likewise, if you have any suggestions in that direction, please do bring them forth — your tips are important since you have the full vision of where PML 3 is going.

I've now started a new dev branch for the package migration to PML 2.3.0/3.0.0

Great!

ETA for the upcoming PML 3 release

Version 3 will probably be published next month.

migrating the package to support PML 2.3.0, and then deal with the breaking changes of PML 3

As mentioned already in an email, there are just very minor syntax changes from version 2.3.0 to 3.0.0. They are documented in the Changelog and pml_tags.json I sent you by email. Please let me know if you need any other information.

"Less is more" ... having a lesser package is better than having no usable package at all

👍

If you want I can send you a link to a standalone executable (pmlc.exe) for a version 3.0.0_beta on Windows (not the final version that will be published).
I've tested this version with all nodes and different PML documents, and there are just two minor bugs (whitespace handling) I'm aware of.

If you want I can send you a link to a standalone executable (pmlc.exe) for a version 3.0.0_beta on Windows (not the final version that will be published).

That would be great, just to have a better idea of what's awaiting next.
Also, once the ST PML package is fixed I want to start work on the PML GUI, which I've been already looking into. Since PML introduces some command line changes, it would be great to have a prototype to work with, so I might even have the GUI tool ready when it comes out, since it would only require minor last-minute fixes (if any).

FYI: I've sent you an email with a link to PMLC 3 beta.

I want to start work on the PML GUI

Great!
Please note: I would like to first discuss an idea with you. Will send you a message in the coming days.

Almost There!
@pml-lang, I've actually managed to salvage all the existing nodes and convert them to the new (..) attributes notation, and while doing so I'm also managing to automatically implement the id and HTML-Attributes attributes on those node that support them, since now attributes definitions are shared-context.
Of course, the current migration doesn't take into account lenient parsing rules for attributes (that's another story altogether, an headhake that I'll have to work on later one). But still, it's good to see that all the previous work can be salvaged in the migration process, so the syntax package won't feel like a bare-bones features.
Now I only have to mechanically apply the same changes to a few node that are still using the old notation, but it's merely a matter of applying the same pattern as for other nodes, so it's just a matter of time.
I think that by tonight the syntax should be fully migrated, as I had foreseen, but unfortunately this doesn't yet make the package ready for release since there's a lot of polishing work, updating of documents and package/repository settings that need to be dealt with before I can squash into main and create the first tagged release. These all require double checking, especially the documentation.
Due to the extreme heat here, I can't over work at the PC as long as planned. During the day, especially the afternoon, it's hard to work, but at night it's much more comfortable (unless excessively fatigued by the heat during the day).
So, maybe still a few days before the package is publicly available, but then it will be possible to install it from within the ST editor (provided one has Git installed) and it will self-update henceforth, which is the other major improvement, since before it had to be manually updated via Git.
After all then, the PML 3 release will coincide with a PML editor package being available for end user, and although it's not fir a free editor it's still better than nothing (if we had invested energy on Atom, as I suggested, it would have been a waste of time now that Atom has reached its end-of-life).
So, be ready for the imminent installation of Sublime-PML! You'll then soon be able to use it in production and provide me feedback on how to improve it.

Great !!!

Package Published
@pml-lang, I've just created the first public release of Sublime PML.
If you could please try to install it following the new instructions provided here and let me know how it went (if you had installed a previous version via Git, you need to remove it by deleting its folder):
https://github.com/tajmone/Sublime-PML/blob/main/README.md#installation-instructions
Once I'll publish a package update, you should finally be able to confirm that self-updating works as expected. In the meantime, enjoy the updated package, and the tons of features that I had implemented but you never saw due to its self-updating failure in the past!

First Package Update
@pml-lang, I've just released Sublime PML 0.7.1, the first package update.
If you could please confirm the following:

When you launch ST the package is automatically updated.
After updating Sublime PML, a message about the new release is shown (i.e. a markdown document listing changes and new features).

Just wanted to make sure that package updates work correctly after following the (new) instructions on the main README.

When you launch ST the package is automatically updated.

Yes, the package was updated, because v2022-08-03 is displayed under Package control: List packages. This is also the date of file AppData\Roaming\Sublime Text 3\Installed Packages\Sublime-PML.sublime-package on my PC.

After updating Sublime PML, a message about the new release is shown (i.e. a markdown document listing changes and new features).

No message was shown. However, this might be because when I started ST, it re-started to install a new version of itself, and displayed a message related to changes in ST.

Yes, the package was updated

Great! Thanks for the confirmation and the time you took to verify via dates details,

No message was shown. However, this might be because when I started ST, it re-started to install a new version of itself, and displayed a message related to changes in ST.

Maybe that, or maybe it's just because it's not being installed via the PackageControl official channel. Although Sublime PML is installed using PackageControl, the fact that it's being updated via Git might be the cause these update messages are ignored; and if that's the case then it's probably ignoring Git release tags and just pulling the main branch at each update check.
Unfortunately the PackageControl documentation is not very clear on the differences about packages installed via Git (the docs are sort of fragmented and very terse). But we could do a simple test to verify this: next time I update main branch without creating a new release, I could insert a small change that can be detected from within the package, so you could tell me whether you're seeing that change (i.e. if it was updated regardless of release tags).
If these update messages are not shown to end users, there's no point for me to keep writing them — i.e. until the package is not added to the official channel. But I also need to known whether ST is just pulling the repository each time, because if that's the case then I need to be careful about what changes I apply to main (right now, I've been working on the assumption that the package gets updated only when there's a new release, but now I feat this might not be the case).

I could insert a small change that can be detected from within the package, so you could tell me whether you're seeing that change

Ok. Good idea.

Update Tests Results
Today I've spent some time setting up a portable version of ST in order to test how the installation of Sublime PML via Git works in detail.
So far, all my tests seem to confirm that the package installation and updates process is not tied to tag releases but simply Git pulling the main branch head.
These were my tests so far:

Installed Sublime PML and created a backup of the Sublime-PML.sublime-package installed package.
Added to the repository a commit on main (6363db313a) that tweaked the README.md file, then (manually) checked for package updates:

PackageControl listed an available update for Sublime PML, showing the commit timestamps of the installed version and that of the update.
After updating I extracted the README file from the local package and diff-compared it with that of my previous backup: the changes from the latest commit on main were present if without a tagged release.

Because I've updated the package manually, I can't confirm 100% that the ST will auto-update the package without intervention.
Update Message?

No message was shown. However, this might be because when I started ST, it re-started to install a new version of itself, and displayed a message related to changes in ST.

Usually Sublime Text preserves all open files when it restarts, including unsaved ones, so I think that if the update message for 0.7.1 had been shown you would have seen it on restart.
Unfortunately, I won't be able to test this without creating a new tagged release.
I can confirm that I get the Sublime PML installation message when install it, but I didn't get that of 0.7.1, which I believe should also have been shown (appended to the install message), but I'm not 100%.
But, in general, I think that tagged-releases might not be working with the Git repository installation, or maybe they are not working because I've omitted some configuration files in the repository. Hard to tell, the documentation is very vague when it comes to this type of installation. I should probably contact the author of Package Control for some help.
At this point, I need to know whether I should keep updating these update messages or not, because if they are not shown there's no point wasting time on them.
On Tagged Releases
For the next package update (which is basically ready, but I wanted to carry out these tests before releasing it) I'll still create a tagged release and package message. But then, if we don't get to see the update message, I'll have to decide whether to drop just package messages or tagged release altogether — if the package is being updated based on main HEAD, what's the point of creating all these tagged releases during the Alpha stage?
I could simply update the package without creating releases; for end users, it would make no difference since they don't even known when the package is being updated or not, and need to refer to the repository to learn about new features.
If I stop using tagged releases (and delete the current ones) during the Alpha (and maybe even the Beta) stage, I would work much faster and the package would grow quicker (since I have limited free time). I doubt end users even care about releases and the CHANGELOG, and it's not as if there are many users right now. So, focusing on production speed might be best right now, and if tagged releases are not needed for ST updates, I should just drop them, so I don't have to update the CHANGELOG, tags, etc, and can work much faster: whenever a feature is ready, I merge it into main, and the package is updated.
I only need further confirmation that the updates work based on main (see following sections).
Help Confirming Tagged Release Update
But maybe you can help me here, since you installed Sublime PML when it was first released (i.e. 0.7.0), you might confirm to me whether the package was automatically updated to the newer 0.7.1 release by checking and confirming if these new features are available to you:

Title Sub-nodes — any inline nodes within a document or chapter title should be properly highlighted in Sublime PML >=0.7.1. So, if you could check form me in ST whether the following lines are properly highlighted in a PML document, it would confirm whether the package self-updated or not:
[ch [title Font Test [b Bold ] Text]

If the [b tag is not colourized, then it means you're still using the initial Sublime PML release (0.7.1)

Help Confirming main Branch Update
If the package is indeed updated, you could further check whether ST has updated it to the latest main commit, and not just the latest tagged release. To do that, you'd need to peek inside the installed Sublime PML package — the Sublime-PML.sublime-package file, which is just a zipped archive stored in ST <data_path>/Installed Packages/ (See Packages).
Under Windows, that folder should be located at:
%APPDATA%\Sublime Text 3\Installed Packages\

Once you've located the Sublime-PML.sublime-package file, open it with a Zip tool and extract the main README.md to check if the latest changes of commit 6363db313a are present or not — namely, line 62 should contain the ⌘ entity instead of cmd (among other changes):
Open the Command Palette by pressing Ctrl+Shift+P (Windows and Linux) or ⌘+Shift+P (Mac).

That would really help understand how ST is handling package updates. If you can find the above change in your local Sublime PML, then it means it was auto-updated to the latest main HEAD.

Results of my test:
There was no Sublime-PML update message when I opened ST.

If the [b tag is not colourized

The [b tag is colorized:

Hence, the package was updated.
Moreover the date of file
AppData\Roaming\Sublime Text 3\Installed Packages\Sublime-PML.sublime-package
shows 2022-08-11

line 62 should contain the ⌘

Yes, this line 62 in README.md:
1. Open the Command Palette by pressing Ctrl+Shift+P (Windows and Linux) or ⌘+Shift+P (Mac).

Results of my test:

Thanks a lot for taking the time and confirm these tests! (and the screenshots too, very cool).
This really helped me out. Now that I now that the package is updated whenever main branch is, I can take an entirely different approach to its development:

Delete previous tags/releases — might re-introduce them when the package reaches v1.0.0, if we decide to submit it to the official Package Control channel.
Delete package update messages (just keep the installation message) and no longer care about having to document each update under a specific version bump.
Create a CHANGELOG file where I simply list changes by date, so end users can consult it to see what was added since they last used the package and read its documentation. Since package updates can't show messages with the version info, and updates occur silently in the background, providing a CHANGELOG is the only way to keep users informed about new features.

Add a new menu to quickly access the CHANGELOG:
Tools > PML >  What's New?

The new development/update strategy changes entirely, becoming slimmer and easier to handle.
From now on, the main branch will only be updated when new commits on dev constitute a full changeset: each new feature is added as a single commit, and before merging all the documentation (Manual, README, CHANGELOG, etc.) is updated in order to ensure that all changes are properly mentioned and covered.
This ensures that package updates are delivered as meaningful change-sets — i.e. since the package is updated every time there are new commits on master we should avoid updates that contain only changes to internal docs or other repo files that don't affect the final package (i.e. are export-excluded or irrelevant to its practical use), and also avoid that new features are introduced without being documented.
Ultimately, instead of relying on tags/releases for updates we rely on merge operations on main instead. Each merge results in a package update, regardless of the number of new commits. This means that any time we're happy with the status of the dev branch we simply have to merge it and its changes will be delivered to end users, which is not bad at all at the current Alpha stage, where versioning makes little sense.
Ok, now I'll start working on updating the repo docs, explaining how the (new) package updates system works, and getting rid of the tags/releases and update messages, then I'll add the new syntax updates that are ready and queued.

New Update System Done!
Ok, I've updated the repository according to the new package update policy, as discussed above. See the CHANGELOG for the details.
Next time you launch ST, you should get an update to Sublime PML that will result in a new menu to open the Changelog:

Tools > PML > Sublime PML Changelog

This menu will help users keep track of new features, since we can't notify them about via package messages.

Next time you launch ST, you should get an update to Sublime PML that will result in a new menu to open the Changelog

Yes, I confirm.

Migrated to PML 3.0.0!
@pml-lang, Sublime PML has already been updated to PML 3 now.
The new changes only affected the build systems, i.e. tweaking the command line invocation of PMLC. The rest was just bumping-up all references to PML version from 2.3.0 to 3.0.0.

Sublime PML has already been updated to PML 3 now.

Wow! That was fast!


[Impeller] ColorBurn not work with CustomPaint.

Steps to reproduce

Just run the sample code.
The image should be a black circle in the center
With Impeller on stable channel, the colorBurn has no effect.
With Impeller on master channel, the colorBurn makes whole screen black.
With Skia on stable channel, the colorBurn render a black circle, but with a purple outline.

Would you please create some test for all these blend mode on Impeller?
Here are the issues I have filed before: #134930 #141160 #145442 #130059
Flutter is great and I use CustomPaint to create some visual effects in App.
It seems the Skia backend will be removed in the next release. But I still cannot enable Impeller because of render issues with blend mode.
Expected results
This the effect rendered from Figma

Actual results

3.19.5 with Impeller
master with Impeller
3.19.5 with Skia

Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: Scaffold(
          body: SizedBox.expand(
        child: CustomPaint(
          painter: DodgePainter(),
        ),
      )),
    );
  }
}

class DodgePainter extends CustomPainter {
  const DodgePainter();

  @override
  void paint(Canvas canvas, Size size) {
    final radius = size.width / 5;
    final blur = Paint()
      ..color = Colors.black
      ..maskFilter = const MaskFilter.blur(BlurStyle.normal, 40);
    final center = size.center(Offset.zero);
    canvas.drawCircle(center, radius, blur);

    final dodge = Paint()
      ..color = Colors.grey
      ..blendMode = BlendMode.colorDodge;
    canvas.drawPaint(dodge);

    final colorBurn = Paint()
      ..color = Colors.black
      ..blendMode = BlendMode.colorBurn;
    canvas.drawPaint(colorBurn);
  }

  @override
  bool shouldRepaint(DodgePainter oldDelegate) {
    return true;
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.19.5, on macOS 13.6 22G120 darwin-arm64, locale zh-Hans-CN)
    • Flutter version 3.19.5 on channel stable at /Users/zhx/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 300451adae (4 weeks ago), 2024-03-27 21:54:07 -0500
    • Engine revision e76c956498
    • Dart version 3.3.3
    • DevTools version 2.31.1
    • 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 34.0.0)
    • Android SDK at /Users/zhx/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
    • Xcode at /Applications/Xcode_15.2.app/Contents/Developer
    • Build 15C500b
    • CocoaPods version 1.15.2

[✓] Android Studio (version 2023.2)
    • 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 17.0.9+0-17.0.9b1087.7-11185874)

[✓] VS Code (version 1.88.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.87.20240402

[✓] Connected device (1 available)
    • iPhone11 (mobile) • 00008030-000xxxxxxxxxxxx • ios • iOS 16.5.1 20F75
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Here is the trace:
Runner.gputrace.zip
1) rrect shadow

2) framebuffer advanced blend filter

3) framebuffer advanced blend filter

According to https://www.w3.org/TR/compositing-1/#blendingcolorburn, applying a ColorBurn of black, the result should equal black.  Here is the definition:
if(Cb == 1)
    B(Cb, Cs) = 1
else if(Cs == 0)
    B(Cb, Cs) = 0
else
    B(Cb, Cs) = 1 - min(1, (1 - Cb) / Cs)

In our case Cs is the src, Cb is the dst.
I audited our ColorBurn math and it seems to match that definition.  So, it should result in a complete black drawing, skia is incorrect in this case.  Impeller is correct.
For the red burn above we should be getting outside the blur, in the red channel:
B(1, 1) = 1, which is correct
green:
B(1, 0) = 0, which is correct.
blue:
B(1, 0) = 0, which is correct.
Again, impeller is correct and skia is wrong in my estimation.

@bdero would you mind spotting me, that drawing black in this case is the correct behavior? See https://github.com/flutter/flutter/issues/147207#issuecomment-2078267796

WAI.  I'm going to close this because the behavior of impeller on the main channel is the correct behavior.  I know that's a pain, but we aren't going to reproduce incorrect math for continuity's sake.

Thank you for your response. I have checked color burn on Photoshop, It was black indeed. So the Figma and Skia is special.
Anyway, I changed the black color to Color(0xff010101), and it solve the problem.


Is img_segment_ids used for evaluation?

Hi @e-bug Is this useful information for the model?
https://github.com/marvl-challenge/marvl-code/blob/master/volta/volta/datasets/marvl_dataset.py#L163
I saw you not using it

Hi!
We did not use it for training either [here].
But indeed, I agree this info might be useful for the model.

@e-bug  thanks!


[C-Api] function to check hw availability

Add new function to check hw availability with custom option string.
Signed-off-by: Jaeyun<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #90. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/90-202108201553430.030359983444214-9e0a06fb480a2021baf0dd4b31c3f0de7a5fd5de/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/90-202108231714300.17807292938232-b701fca7a57cdf12c4b6d92871a08d93cf18611f/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/90-202108232030220.53542995452881-c9c970542c7daf876d1d20b5bed72f17c4d37ca0/.

need https://github.com/nnstreamer/nnstreamer/pull/3463 to fix build error.
Prepare group SR, force-merge.


Unsupported Term Meta

Hi All, quite new to the project.
Looking to use Timber with the native TermMeta as implemented with WordPress 4.4.  A quick look around the codebase make me believe that the current TermMeta implementation relies on ACF being used rather than the builtin API?
Any plans on getting the Native API supported?

+1 hightly needed
Getting meta on post types works perfectly fine. custompost.meta('key') return values form wp_postmeta table.
But getting meta for term don't working. term.meta('key') return empty string.

Please check if I'm right. I made edits in my Term.php
`
/**
* @internal
* @param string $field_name
* @return string
*/
public function get_meta_field( $field_name ) {
if ( !isset($this->$field_name) ) {
$field_value = '';
$field_value = apply_filters('timber_term_get_meta_field', $field_value, $this->ID, $field_name, $this);
$field_value = apply_filters('timber/term/meta/field', $field_value, $this->ID, $field_name, $this);
$field_value = get_term_meta($this->ID, $field_name, true);
$this->$field_name = $field_value;
}
	return $this->$field_name;
}`

`add_filter('timber/term/meta/field', 'fix_damn_timber_bug', 10, 4);
function fix_damn_timber_bug ($field_value, $id, $field_name, $term) {
return $field_value = get_term_meta($id, $field_name, true);
}`

So what needs to be done to get this merged into Timber core? Do we need a new method on the Term object that does the standard term meta lookup introduced in 4.4? I'd be happy to take a look at it over the next week or two if I have some time.

#1238 should address this, lemme know if anyone runs into issues


rustfmt fails to wrap long lines with arrays

mkpankov@mkpankov-ThinkPad-x240 ~/rust [core-fmt *]
± % ➜  rustfmt src/libcore/num/flt2dec/strategy/dragon.rs                                                                                !3033
Rustfmt failed at src/libcore/num/flt2dec/strategy/dragon.rs:27: line exceeded maximum length (sorry)
Rustfmt failed at src/libcore/num/flt2dec/strategy/dragon.rs:28: line exceeded maximum length (sorry)

Lines it failed at are:
static POW10: [Digit; 10] = [1, 10, 100, 1000, 10000, 100000, 1000000, 10000000, 100000000,<PHONE_NUMBER>];
static TWOPOW10: [Digit; 10] = [2, 20, 200, 2000, 20000, 200000, 2000000, 20000000, 200000000,<PHONE_NUMBER>];

This is a known issue: https://github.com/nrc/rustfmt/issues/431.

Oh, tried to search for the error message and didn't find it. Closing then


wUST transfer from Solana to Ethereum stuck Wormhole v1

I tried moving wUST from Solana to Ethereum on Wormhole v1. The transaction went through on Solana but it's stuck on Executing Solana Transaction (see attached screenshot).
I need this on Ethereum ASAP. Help.

Used interstellar.tk as suggested on another thread and it worked.


Humble bundle not showing in boilr

I have no idea how I can add my humble bundles games into my steam library at this point.

@ppyporpeem not sure if BoilR has support for humble bundle.... you may have to do it manually

This is neither an issue with NonSteamLaunchers nor BoilR as the launcher is not on SteamGridDB, just the website. This means you'll need to use an alternative method to provide assets or manually launch BoilR and tell it to use the website assets

@DanHolli123 will be parsing Humble Games Launcher in the new future now that the login is fixed


Changelog v1.13.0-RC1

as title

rc1

Codecov Report

Merging #13142 into master will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #13142      +/-   ##
==========================================
- Coverage   42.09%   42.02%   -0.07%
==========================================
  Files         678      678
  Lines       75029    75029
==========================================
- Hits        31580    31534      -46
- Misses      38298    38369      +71
+ Partials     5151     5126      -25

Impacted Files
Coverage Δ

modules/notification/ui/ui.go
72.22% <0.00%> (-8.34%)
:arrow_down:

models/issue_comment.go
45.71% <0.00%> (-7.22%)
:arrow_down:

modules/notification/mail/mail.go
28.73% <0.00%> (-5.75%)
:arrow_down:

modules/git/commit.go
50.00% <0.00%> (-4.06%)
:arrow_down:

modules/notification/base/null.go
68.57% <0.00%> (-2.86%)
:arrow_down:

modules/notification/notification.go
78.57% <0.00%> (-2.68%)
:arrow_down:

services/mailer/mail.go
54.83% <0.00%> (-1.08%)
:arrow_down:

services/pull/pull.go
40.29% <0.00%> (-0.99%)
:arrow_down:

models/error.go
34.39% <0.00%> (+0.50%)
:arrow_up:

modules/git/repo.go
46.70% <0.00%> (+0.50%)
:arrow_up:

... and 9 more

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 e70df67...dd9e7b2. Read the comment docs.

@zeripath moved 12689,13056,13058 into sec topic - still ok?

yeah fine


max_line_length-guide is broken

..since the usage of the wrap-guide element has changed, and the wrap-guide instance isn't part of the DOM-element anymore.

Okaydo - i fiddled around a lot and we're not able to intercept the wrap-guide anymore. I will implement a custom max-line-length element to the package. This will land hopefully this week.
As always help is welcome and i'd be thankful if anybody would try to create it.

Any news on this? I was just trying out the max_line_length and didn't notice any difference. Then I found this issue.

If, by "broken", you mean Atom does not respect the max_line_length setting to adjust the long line guide accordingly I still have that problem. Not sure if it ever worked but I left the Preferred Line Length setting in Atom untouched (defaults to 80) and usually set max_line_length in my .editorconfig to 100 but the guide is still at 80.
Is it because I don't have soft wrap enabled or does anybody have an idea how I can move the guide to that 100 mark?

the guide is still at 80

Here's the answer:

we're not able to intercept the wrap-guide anymore

My question was i.r.t. this statement:

I will implement a custom max-line-length element to the package. This will land hopefully this week.

Hi @ameenross, @manuelbieh - thanks for getting in touch. I started rewriting the package in order to fix this issue. Unfortunately i'm currently not making much progress since the lack of time. I'd like to give you news on this but it seems like you'll still have some patience until the package picks up to the current release of Atom again.

I decided to drop maintenance. Sorry.
See https://github.com/sindresorhus/atom-editorconfig/issues/231

This should have been fixed by 021d0ea. See related issues #232 and #226.
Gonna close this as resolved; if any of you experience this again, don't hesitate to open a new issue. 👍

Thanks for taking over this project! What version of Atom do we need for this to work? I'm not seeing it yet.

@ameenross I tested this with the latest Atom Nightly (1.37.0-nightly0) as well as stable (1.34.0). Could you provide a list of which packages you have installed/activated?
Wouldn't hurt to grab what system you're running too (and the version/distro, if possible).
At a glance, can't see any packages there that look like they'd be troublemakers. 😕

Ubuntu 18.04, Atom 1.34.0
Also, disabling all community packages except editorconfig did not make the wrap guide work, it stays at 80 chars

Alright, few questions about the workspace:

Is the root folder of the project a Git repository?
What file are you testing this with when you say the wrap-guide isn't working?
What are the rules stored in your .editorconfig file(s)?

The project is a git repo, editing a PHP file with these rules:
# top-most EditorConfig file
root = true

# Unix-style newlines with a newline ending every file and 4-space indentation.
[*]
end_of_line = lf
insert_final_newline = true
indent_style = space
indent_size = 4
trim_trailing_whitespace = true
insert_final_newline = true

[*.php]
max_line_length = 120

Alright, what about the file's physical path? Does it reside within one of the project folders, or is it located outside the root directory?
Also, are you seeing this in an editor you had open when the editor was launched? There's currently some bugginess with editors which are open at startup... try closing the file and reopening it. Does that help?

FWIW, the other properties do work, like indent_size. Just changed it to 6 to test.
It's in the root of the project.
I'm working right now, so opening and closing PHP files regularly. Don't see it.

Reopening this, as there's (obviously) still an issue here.
Does a max_line_length of less than 80 (e.g., ~30-40) make a difference? Trying to gauge if this issue is connected to atom/wrap-guide#56, which I had to kludge a fix for to stop breakage in nightly releases (#232).
The fix I applied isn't perfect because it doesn't consider multiple guides when updating the position of the wrap-guide. Should open a new issue about that, actually...

No difference.
Also tried moving ~/.atom for a fresh profile, installing editorconfig and nothing else, still no go.

@issuehunt has funded $40.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

I must admit that I recently saw the length guide working. Maybe a month ago or so.
Might have been version 2.4.0, I'm not sure.

Closing as Atom is abandoned.


swapd: removing nesting

Codecov Report

Merging #558 (8c4a251) into main (50e8991) will increase coverage by 0.0%.
The diff coverage is 0.0%.

@@          Coverage Diff          @@
##            main    #558   +/-   ##
=====================================
  Coverage   12.1%   12.1%
=====================================
  Files         34      34
  Lines      10573   10569    -4
=====================================
  Hits        1277    1277
+ Misses      9296    9292    -4

Impacted Files
Coverage Δ

src/swapd/runtime.rs
0.0% <0.0%> (ø)

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 50e8991...8c4a251. Read the comment docs.


Improve VKCapabilitiesDevice and VKCapabilitiesInstance documentation

#809 was opened because VKCapabilitiesDevice and VKCapabilitiesInstance was insufficient at indicating its purpose. This makes clear what those classes are and what the public fields are and mean.

Hey @SWinxy, I cleaned it up a bit and removed comments/documentation for non-public stuff.
Thanks!


Updated README for Paypal SDK 1.3.0 for Laravel 4

Yes, I know about it. A big change is Address Class, Paypal allows only Phone Number properties in Address Class, all customer contact related fields are removed. Please check it out.

yes you're right I just noticed that here https://github.com/paypal/PayPal-PHP-SDK/blob/master/lib/PayPal/Api/Address.php

You're right, I didn't see this carefully. Sorry, my mistake :)

ok no worries I have fixed the doc

Thank you! =)


Allow errors to set HTTP status codes

Discussed in https://github.com/strawberry-graphql/strawberry/discussions/2304

Originally posted by ShourovRoy November  2, 2022
Apollo Graphql has a function to modify status code on error that can be overridden which plays an important role for implementing refresh token. Is there any way to do that here?
Apollo server allows errors to change the status code, maybe we can do the same:
import { GraphQLError } from 'graphql';

const resolvers = {
  Query: {
    someField() {
      throw new GraphQLError('the error message', {
        extensions: {
          code: 'SOMETHING_BAD_HAPPENED',
          http: {
            status: 404,
            headers: new Map([
              ['some-header', 'it was bad'],
              ['another-header', 'seriously'],
            ]),
          },
        },
      });
    },
  },
};

https://www.apollographql.com/docs/apollo-server/data/errors/#setting-http-status-code-and-headers

I'm somewhat critical of setting the http status right in the base GraphQL error, as the Schema is transport-agnostic. Maybe we can create a new Http or StatusCode GraphQLError with a middleware for the HTTP/Websocket/(in the future SSE) views that injects the code based on the new Error class.


bots: add skeleton for stalebot

title:
bots: add skeleton for stalebot
Description:
This probot app integration will mark stale issues and PRs after 7
days. It should then close them after another 7 days. The help wanted
label will be ignored for now.
Risk Level: Low | Medium | High
Medium: Has power to close PRs/Issues , but should be ingnoring help wanted label

Note: It isn’t expected to do all
forms of testing, please use your best judgement or ask for guidance
if you are unsure. A good rule of thumb is the riskier the change, the
more comprehensive the testing should be.

Docs Changes:
N/A
Related #2797

Anymore comments on this?

@mattklein123 I think we just need to add the bot through the GH apps page. If you visit https://github.com/apps/stale this should allow you to point it at the envoyorg.

OK I installed the stale bot. Let's see what happens. cc @envoyproxy/maintainers


Localise mirror page, terms of use

A couple of other pages that sit outside the normal workflow:

warehouse/static/html/mirror.html
policies/terms.md

are these within scope for localisation @ewdurbin ?

ping @brainwane - any idea on the above? thanks

Decided it's okay to leave these out for now. Thanks @nlhkabu.

(That is, it's outside the milestone.)

@ewdurbin could this be addressed along with #6631?


Handle trader rep reqs

The API now handles trader reputation requirements in addition to level requirements for tasks. This PR handles that change.

.deploy


refactor: get rewards based on spendable epoch field

Description
Adapts rewards query to get account balance according to the new db schema.
Test
Tests will pass when the new db snapshot is provided

Closed at #403


Transient popup menus become persistent after displaying plot in MacOS

Transient user interface popups, eg for "interpolation" menu or the "input order" menus become persistent on the screen when running on macOS.  Does not happen on windows.   Probably a Qt or naperi issue?

Does this issue show up when the plugin is not running? If yes we should move this issue somewhere else. If no please comment

Do you know of an alternative plugin that pops up a plot window to test the problem?  I agree that it is unlikely to be a napari-sim-processor issue.

Found the problem/fix.  Multiple phase plots would not appear at the same time on a Mac either so I set plt.show(block=False).  Now all plots appear and the transient pop-ups do not appear when they shouldn't.  Gui behaviour is unchanged in Windows.  The fix is in anglesandphases branch and can be merged to main along with the other changes there. I will close this issue.


Cannot make CodeCompletionProvider for 'javascript'

VSCode Version: 1.1
OS Version: Linux | OS X

Quick example:
vscode.languages.registerCompletionItemProvider('javascript', {
  provideCompletionItems() {
    console.log("I'm here")
    return []
  }
}, '.')

For new languages and for plain text it's works, but for 'javascript' you will see not see this console.log. In some strange actions (like many times pressing on Backspace inside some string) you will see this console.log, but if you will provide CompletionList or CompletionItem it's also will be ignored.
I know about score, but I'm not sure how to increase it, selectors like { language: 'javascript', scheme: 'file' } doesn't works.
I'm working on next Flow extension https://github.com/Kr0na/flow-for-vscode but for now the only way to implement code completion is to make 'Flow' language that doesn't provide a power of IntelliSense and user should manually select it to use Flow completion

I've also investigate to source code of VSCode and found this:
https://github.com/Microsoft/vscode/blob/master/src/vs/editor/common/modes/languageSelector.ts
So when I just put 'javascript' the score is 10, when { language: 'javascript', scheme: 'file' } it will be 20
After this I look at the typescript extension and found registration of Code Completion for javascript:
https://github.com/Microsoft/vscode/blob/master/extensions/typescript/src/typescriptMain.ts#L134
So score for javascript in this case only 10
20 > 10 So { language: 'javascript', scheme: 'file' } should be called before wildcard 'javascript'

Good feedback. The behaviour when multiple provider contribute to a language feature is described in the registerXYZProvider-methods. For suggestion it is this:

Multiple providers can be registered for a language. In that case providers are sorted
by their score and groups of equal score are sequentially asked for
completion items. The process stops when one or many providers of a group return a
result. A failing provider (rejected promise or exception) will not fail the whole
operation.

This is a little special and different to the commonly used strategy of just merging all results. We made that decision to always have a reasonable small list of completions. I can see how that bites you now and we should revise.
Having  said that, the selector { language: 'javascript', scheme: 'file' } should be equal to the one VS Code uses, therefore be in the same group, and consulted when completions are requested

I think we should change the scoring wrt document filters. It should not be the sum but the max of each attribute whereas each value must be greater than zero.

The effect of this change will introduce a small semantic change. Take two document selector

{ language: 'javascript', scheme: 'file' }
{ language: 'javascript' }

and a javascript file on disk which matches for both selectors. Today the scoring will favour the former selector cos it matches on language and scheme. The conclusion is that this doesn't make much sense and only the opposite should be true (the former should not match on an untitled buffer).
This affects only completion provider cos other providers use a merging strategy. @egamma pls speak up if you think this is semantic api breakage.

@jrieken I'm not sure that this fix is finally correct. Because seems that if I use this selector in code:
{ language: 'javascript', scheme: 'file' }
It will have score 10 even if:

All Documents that have scheme 'file' (this includes css files, bin files, etc)
All Documents with language 'javascipt' (for both file and in-memory)
So this commit change LanguageSelector from "and"(use as much as possible) to "or"(any of condition is true).

Ok. Thanks

It there perhaps a way to decrease a score? In order for the extension to indicate that it wants its suggestions to be displayed after all the other providers? (use case here)

displayed after all the other

You mean sorting or only iff no other extensions as suggestions?

I mean the ability for extension developers to express the fact that "my suggestions are usually less important than suggestions provided by other providers with the same document selector and there for I'd like vscode to display them on the bottom of the autosuggestions popup".

Ok - for that you can use the sortText property

Thank you very much!
BTW, the link above seems to be to a private repository, here's a public one.

ops - I am working on a PR that I have pushed yet


Image Upload

Does plemmy support this? I did a cursory peek in the issues and through docs/examples but didn't see this, so was curious if I missed something

No it does not support image upload.

Implemented it, it is now possible to upload images with plemmy 0.4.5.
Its probably late, but its done now :)


After confirm an action, it should not allow people to confirm again while Metamask is still opening

Describe the bug
In some scenarios, like "Bid" or "Cancel Bid", after confirming the action and switching to Metamask for signing the request, these buttons are still available for clicking
To Reproduce

Place a bid or Cancel a bid
Checking the "Waiting pop up on the main screen"

Expected behavior
Buttons should not click-able
Screenshots
Place a bid:

Cancel a bid:

Resolved in 36eac0184f08b7884c1c3d4b80fb0bab752ab1b3

Close in favor of #36


Client auth integ fix

Description of changes:
My goal is to get the client auth tests successfully running all their test cases. Improvements to the framework to try to prevent these problems in the future will be made in later PRs.

Fix the client auth integ tests so that they actually test ECDSA certs.
Use the same ProviderOptions fields for both client and server certs. This makes the logic easier to follow.

Testing:
How is this change tested (unit tests, fuzz tests, etc.)?
I visually inspected the integ test output to make sure it looked sane.
I made sure the tests that I expected to fail before the last few bug fixes actually did fail when I reverted those bug fixes.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2454 (f331947) into main (d408f27) will decrease coverage by 0.01%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main    #2454      +/-   ##
==========================================
- Coverage   82.02%   82.00%   -0.02%
==========================================
  Files         271      271
  Lines       18727    18727
==========================================
- Hits        15360    15357       -3
- Misses       3367     3370       +3

Is there a plan to save the results between runs to check for regression? ECDSA was most certainly working at some point in the past. It was most likely lost in the code checking if each test is valid. That could easily happen again.

I've got a couple ideas for catching tests incorrectly marked invalid, but they're out of the scope of this PR. This is only intended to get Client Auth tests working again.


update: citation file

Description
Updated Citation file to match JOSS paper: https://raw.githubusercontent.com/AutoResearch/autora-paper/refs/heads/main/paper.md

Hi @musslick thanks for doing this. Is it possible to change my given name to the more official "Sida"? Thanks.

Hi @musslick thanks for doing this. Is it possible to change my given name to the more official "Sida"? Thanks.

@listar2000 Done! Thanks for checking.


Set default PostgresQL version for FreeBSD

FreeBSD uses Postgresql 12 by default
Ref: https://svnweb.freebsd.org/ports/branches/2021Q1/Mk/bsd.default-versions.mk?revision=560000&view=markup#l100

Codecov Report

Merging #1227 (9b66c16) into main (08e3a51) will increase coverage by 0.37%.
The diff coverage is 37.50%.

@@            Coverage Diff             @@
##             main    #1227      +/-   ##
==========================================
+ Coverage   65.81%   66.18%   +0.37%
==========================================
  Files          14       14
  Lines         351      349       -2
==========================================
  Hits          231      231
+ Misses        120      118       -2

Impacted Files
Coverage Δ

...ns/postgresql/postgresql_acls_to_resources_hash.rb
0.00% <0.00%> (ø)

...b/puppet/functions/postgresql/postgresql_escape.rb
0.00% <0.00%> (ø)

lib/puppet/util/postgresql_validator.rb
90.90% <0.00%> (ø)

lib/puppet/type/postgresql_psql.rb
90.14% <66.66%> (ø)

...uppet/provider/postgresql_replication_slot/ruby.rb
75.86% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #1227 (9b66c16) into main (08e3a51) will increase coverage by 0.37%.
The diff coverage is 37.50%.

@@            Coverage Diff             @@
##             main    #1227      +/-   ##
==========================================
+ Coverage   65.81%   66.18%   +0.37%
==========================================
  Files          14       14
  Lines         351      349       -2
==========================================
  Hits          231      231
+ Misses        120      118       -2

Impacted Files
Coverage Δ

...ns/postgresql/postgresql_acls_to_resources_hash.rb
0.00% <0.00%> (ø)

...b/puppet/functions/postgresql/postgresql_escape.rb
0.00% <0.00%> (ø)

lib/puppet/util/postgresql_validator.rb
90.90% <0.00%> (ø)

lib/puppet/type/postgresql_psql.rb
90.14% <66.66%> (ø)

...uppet/provider/postgresql_replication_slot/ruby.rb
75.86% <100.00%> (ø)

Continue to review full report at Codecov.

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


Modus Table: Fixed issue with manual pagination

Description
The @watch decorator in the manualPaginationOptions property was not setting the pagination state correctly.
References #1984
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

How Has This Been Tested?
Tested manually using these code:

      <modus-table density="relaxed" sort="false" full-width="true"></modus-table>

Checklist

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[X] I have checked my code and corrected any misspellings

This PR remains open as I wait for a reproduction using only the modus-web-components.  Please provide a reproduction.

@cjwinsor - This issue seems to arise when manual pagination is used.  The paginationChange event that gets triggered the first time the pagination control is clicked defaults to show a pageSize of the lowest value in the pageSizeList.
I was able to replicate this issue in the modus project (stencil-workspace\src\index.html).  When you have the opportunity, please test with the following code and review the first console.log output.
Thanks!

      <modus-table density="relaxed" sort="false" full-width="true"></modus-table>

@dnarey I was able to reproduce the issue, however I was also able to reproduce it on this branch.  Can we confirm the PR as submitted corrects the issue?

@cjwinsor Ready for review


ROS bridge performance issue testing with LGSVL simulator.

Hi Autoware teams,
I use LGSVL Simulator to connect with Autoware. When use_sim_time is set to true, the CPU usage of the
ros bridge will exceed 100%. In this case, the timestamp of the /clock topic on the Autoware side will slow down, which will
affect Lidar's data and cause localization errors.
In addition, I see the message "ROS time moved backwards" in the log. I would like to ask if there is a solution
to this problem in rosbridge or Autoware in the above question, or if there are any adjustable settings to
eliminate this problem.
Thanks.

Per our support guidelines, please submit support questions to ROS Answers.


chisel doesn't display the return value from a function call unless assigned to a variable

Component
Chisel
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (6e09b4e 2023-07-24T00:24:06.799680000Z)
What command(s) is the bug in?
chisel
Operating System
macOS (Apple Silicon)
Describe the bug
chisel doesn't display the return value from a function call unless assigned to a variable.
Example:
➜ MerkleProof.processProof(proof, leaf)
➜ bytes32 output = MerkleProof.processProof(proof, leaf)
➜ output
Type: bytes32
└ Data: 0xe90b7bceb6e7df5418fb78d8ee546e97c83a08bbccc01a0644d599ccd2a7c2e0

It'd be nice if the first ➜ had the same output as the third ➜.
If that's not possible for some technical reason, it'd be helpful to document this behavior in the docs. (I see an example with an assignment like that here but it's not clear that assignments are mandatory!)
PS: I also tried console.logBytes32(MerkleProof.processProof(proof, leaf)); but that also displayed nothing (unless !traces was enabled).

this should be straightforward to fix @Evalir


add missing function Pose.with_transform() to fix Pose.interpolate()

Pose.with_transform() was missing so I created one (and added intorpolate() tests)
Or maybe it's better to inline the functionality in intorpolate() instead of creating a new one time use function?

Awesome, Thanks!


fix(build): update to go 1.15

Updated Dockerfile, go.mod for Go 1.15
Removed go reference in Jenkinsfile so it defaults to CI/CD pipeline default
Fixes: #58
Signed-off-by: Jim White<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://wiki.edgexfoundry.org/display/FA/Contributor's+Guide
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

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

What is the current behavior?

n/a
Issue Number: #58
What is the new behavior?
none
Does this PR introduce a breaking change?

[ ] Yes
[x ] No

Are there any new imports or modules? If so, what are they used for and why?
Are there any specific instructions or things that should be known prior to reviewing?
Other information

recheck


[feature] add versioning to GSI file to be able to reference changes between files

no version or v1
"Dota 2 Coach Configuration"
{
    "uri"               "SERVER_URL/gsi"
    "timeout"           "10.0"
    "buffer"            "0.0"
    "throttle"          "0.5"
    "heartbeat"         "30.0"
    "data"
    {
        "abilities"     "1"
        "buildings"     "0"
        "couriers"      "0"
        "draft"         "0"
        "events"        "1"
        "items"         "1"
        "hero"          "1"
        "league"        "0"
        "map"           "1"
        "minimap"       "0"
        "neutralitems"  "0"
        "player"        "1"
        "provider"      "1"
        "roshan"        "0"
        "wearables"     "0"
    }
    "auth"
    {
        "token" "STUDENT_ID"
    }
}

v2 adds building 1 and the versioning string appended to the auth token

v3 adds minimap 1.
Note: need to update the fly.toml file for deployment.


Update code example for step 18 of pyramid project

Describe the Issue
We are getting a lot of confusion on the forum about step 18.
The confusion stems from not know how to log the rows array to the console.
So we should update the code example in the description to log the example array.
That should help with what is expected to do.
updated description
Arrays are special in that they are considered <dfn>mutable</dfn>. This means you can change the value at an index directly.

For example, this code would assign the number `25` to the second element in the array:

```js
let array = [1, 2, 3];
array[1] = 25;
console.log(array); // prints [1, 25, 3]
```

Update the **third** element of your `rows` array to be the number `10`. Then print the `rows` array to your console.

Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-introductory-javascript-by-building-a-pyramid-generator/step-18
Your code
see explanation above
Expected behavior
see explanation above
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum
Files that need to be changed
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/15-javascript-algorithms-and-data-structures-22/learn-introductory-javascript-by-building-a-pyramid-generator/660f07d231941bc11719f664.md
Happy coding


Master branch, dtunnel will became freeze after a while

Master branch, dtunnel will became freeze after a while
or if a few minutes non active , the session will dead.

这个原因是这样：lite版本，两端会有心跳来检查是否连接正常，master版本，两个client之间没有心跳，客户端和服务端之间有心跳，所以udp通道失效的时候不会及时反应，之后会修正这个问题。

I tested the udp version also. the udp protocol not stable.
after a while, the udp packages can not reach other side .
So i tested the tcp protocol. it seems working well  and more stable than udp protocol

udp的数据相比tcp来说更容易被gfw，如果gfw怀疑你的流量有问题，会阻断udp的单向或者双向通讯，所以不是说udp不稳定，而是因为通讯数据已经不可达了

Yep. so the much more stable solutions , is socks5 over ssh, this is slowly, but more stable. (GFW not blocked SSH now)

ssh也会封的，目前dtunnel_lite的tcp模式还是比较稳定的，不过网络差的情况下表现不如udp好

UDP will be blocked by GFW  (If GFW sniffer your traffic not normal), so this is not a problem we can resolve. i will close this issue.


Bump identity.inbound.auth.saml.version

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2115309235

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2115309235
Status: cancelled

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2115811243

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2115811243
Status: success


[PTRun] Sort order for previously selected not always working

Summary of the Pull Request
Some items in the list will appear before previously selected/clicked items. Previously selected items should always be before never-selected items. We need to do this because the "Score" is not uniform (across plugins) and thus it might require a lot more clicks to put something at the top of the list.
We might want to also put a time box on the amount of time it can be considered "clicked". For instance, if it's last click was a long time ago, use the current "Score * 5" system, else use the new system.
E.g.:
Search results have this makeup.
Item 1: Score 900
Item 2: Score 200
Item 3: Score 100
Item 4: Score 3
Here, "Item 4" has to be clicked "a lot" and it's an unknown (to the user) why it's not at the top. Because we're using (Score + (ClickedCount * 5)). We need to click "Item 4" 182 times to get it to the top.

PR Checklist

[X] Closes: #18958
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments
To fix this we can store the number of times clicked separately and order by number of times clicked and then by "Score". We can also age out clicked items if wanted. We can ignore clicked items, if we clicked them "a long time ago".
Unless there is some unified score model, what else can be done?
Also, I don't know if this will affect PT Run "utilities" like calculator and such, and we might want to omit them from "clicked count if they are not already?"
Validation Steps Performed

Ideally, this AND PR #18957 are needed.

This is not good enough.


docs: Add toggle for dark mode

Signed-off-by: William Van Hevelingen<EMAIL_ADDRESS>closes #7129
Don't bother creating a PR until you've done this:

[x] Run make pre-commit -B to fix codegen, lint, and commit message problems.

Create your PR as a draft.

Your PR needs to pass the required checks before it can be approved. If the check is not required (e.g. E2E tests) it
does not need to pass.
Once required tests have passed, you can make it "Ready for review".
Say how you tested your changes. If you changed the UI, attach screenshots.

Tips:

If changes were requested, and you've made them, then dismiss the review to get it looked at again.
Add you organization to USERS.md if you like.
You can ask for help!

Default

Dark Mode

@alexec We will need someone to verify google analytics is still working after merge.


Remove index.html

Is the file index.html needed in branch master?

Definitely not, it was put there to be easy to check the library when cloning the repo, but a demo is now available online on the github.io page.
Further checks/tests should be done with automated testing, so this index.html is not serving any purpose now.


Allow logos of any width

It makes sense for us to suggest (and possibly even enforce) the logo height since it will appear in the navbar, but we should lift the restriction of the required width as well.

From Skype:
[7/13/15, 10:16:10 AM] Sam Reid: Something else I think we’ll need to do for the icons is to stop prescribing width+height and just prescribe the height (and support any width of button, for logos that happen to be wider or thinner).
[7/13/15, 10:17:24 AM] Chris Malley: which icons?
[7/13/15, 10:17:34 AM] Sam Reid: the logo
[7/13/15, 10:17:35 AM] Chris Malley: phet logos?
[7/13/15, 10:17:37 AM] Sam Reid: y
[7/13/15, 10:17:48 AM] Chris Malley: is that confined to PhetButton?
[7/13/15, 10:18:01 AM] Sam Reid: it may impact the navbar layout code if it is assuming the phetButton is a specific size
[7/13/15, 10:18:12 AM] Chris Malley: no such assumptions in navbar.
[7/13/15, 10:18:16 AM] Sam Reid: hooray!
[7/13/15, 10:18:54 AM] Chris Malley: PhetButton shouldn't care either - but unfortunately does.  Sizing the PhetButton should be the responsibility of the NavBar.
[7/13/15, 10:19:24 AM] Chris Malley: PhetButton should be able to take any icon and put the horizontal bars to the left of it.

I added code to scale the image so that it matches the PhET logo height.  Any width is accommodated as long as there is enough space in the navbar (otherwise assertion error) and negative layout numbers.
Anyone want to review?

Assigned to @pixelzoom since I recall he worked on navbar layout recently.

I should note I tested this with a new fake company logo I made up with dimensions 1000x200 and it worked well in the requirejs mode and built mode.  I also tested the phet logos and didn't see anything amiss.

I would probably factor out magic numbers like this:
var PHET_LOGO_HEIGHT = 108;  // height of the PhET logo, brand/phet/images/logo.png
var PHET_LOGO_SCALE = 0.28; // scale applied to the PhET logo
// Scale to the same height as the PhET logo, so that layout code works correctly.
var DEFAULT_LOGO_SCALE = PHET_LOGO_SCALE / logo[ 0 ].height * PHET_LOGO_HEIGHT;

function PhetButton( ... ) {

  options = _.extend( {
     logoScale: DEFAULT_LOGO_SCALE
  }, options );

}

This also makes me wonder why logoScale is an option.  I don't see it used anywhere, and setting it to something other than DEFAULT_LOGO_SCALE will may break layout.  Should we remove it?

Good thought, I'll remove it.

In the commit above:

Factored out constants, renamed vars, removed logoScale option

Tested by running ABS in requirejs mode with default brand.  No problems noted.  @pixelzoom anything else to do here?

:+1: Closing.


Implement AxialPoint::from_real

We need to convert world coordinates to axial coordinates to be able to figure out the player position (or any object's position) in pillar/chunk coordinates to implement things like #55, so this has very high priority at least for world gen.
http://www.redblobgames.com/grids/hexagons/#pixel-to-hex
pub fn from_real(real: Point2f) -> Self
(this doesn't have much to do with world gen, but I tagged it S-gen-world anyways because it's basically blocked on this)

I would like to work on this issue ;)


how to enable output streaming ?

By default the API returns the whole message if its done processing which takes a while depending on length.
the chatGPT interface outputs the message in a stream which is possible in the api by proving the stream: true parameter in the body. I tried to add the parameter but the app breaks.
Any quick way to switch to streaming output ?

Sorry I missed this issue, but I don't think it's supported right now. The site just does a normal fetch and plops the response in the UI. I'm not exactly sure what would be needed to support streamed responses the app.


print log not working

When I use print() it would not show up on the terminal. It stopped working once I updated to the latest version.
[✓] Flutter (Channel stable, v1.9.1+hotfix.5, on Mac OS X 10.14.6 18G84, locale en-US)
    • Flutter version 1.9.1+hotfix.5 at /Users/boldpalette/Applications/flutter
    • Framework revision 1aedbb1835 (2 days ago), 2019-10-17 08:37:27 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/boldpalette/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • 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)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.1, Build version 11A1027
    • CocoaPods version 1.7.5

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 40.2.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[!] IntelliJ IDEA Ultimate Edition (version 2019.2.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[✓] VS Code (version 1.30.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.25.1

Which platform have you been building for?
This has been a known issue on iOS13 devices https://github.com/flutter/flutter/issues/41133.
You can open the Observatory manually in the mean time https://github.com/flutter/flutter/issues/41133#issuecomment-539441286

Hi @praven07
I see there are several issues open addressing the case you described
1 , 2 , 3
plus the one suggested above (thank you @vagrantrobbie)
Please follow up on that issue,
I'm closing the current one as duplicate.
If you disagree please write in the comments
and I will reopen it.
Thank you


Implement SGID login, account merging

SGID login was removed when we switched from next-auth to iron-session package in #21. Reimplement if we want to allow admins to log in with SGID. A little more complex and requires account linking, and/or users to update their profiles to match email domain whitelist before allowing them into the application. May require some semblance of user roles too.

SGID login completed in #105. Account merging probably not, but will update app to allow changing of emails


Add localisations

English
Russian
Polish

https://istudent.kpi.ua supports following languages:

English
Ukrainian
Turkish
Chinese
French
Russian

Added:

English
Ukrainian
Russian

Turkish is added (6c6d017)


Add a transport socket match in cluster.

Signed-off-by: Jianfei Hu<EMAIL_ADDRESS>API for https://github.com/envoyproxy/envoy/issues/8016
Context
Customers adopting service mesh likes mTLS ability. However, rolling it out without breaking existing traffic is hard. This is because mTLS is configured on per cluster basis. In reality, a service consists of multiple endpoints, mixed with having Envoy sidecar and without-sidecar endpoints. Client envoy can't send mTLS traffic until all server migrated to having Envoy sidecar.
This API tries to solve the issue by allowing mTLS/transport socket to configured at finer granularity, e.g. endpoint level. The endpoint has metadata label information, which will be used to decide which transport socket configuration to use from a map specified in the cluster.
So the outcome is that, xDS management server is able to configure client envoy talks to endpoints with sidecar in mTLS and plain text to endpoints without sidecar, for a single cluster.
Description:
Risk Level: N/A (API change only)
Release Notes: Cluster API change to use different transport socket based on endpoint label.

/cc @lizan @rshriram @PiotrSikora

I'm generally opposed to using unstructured metadata for this purpose. If we are going to go down this path (see above comment about needing to understand design rationale and motivation), then we need to add an explicit label field to EDS endpoints.

@incfly FYI, for changes to Envoy's APIs, you should tag @envoyproxy/api-shepherds on any design review.

So @htuch , how about this:
cluster:
  tlsContextMap:
    mtls: …, default
    plaintext: …
  endpoints:
    <IP_ADDRESS>, tlsContext-to-use: mtls
    <IP_ADDRESS> tlsContext-to-use: plaintext

effectively, we ship a bunch of named TLS contexts to the cluster and then in the EDS, we can ship the TLS context to use for a given endpoint. This has the same effect of using label selectors in the TLS context.

@rshriram lets iterate on the doc a bit more, I like labels more for its flexibility, a tlscontextmap (or transport socket map) potentially explodes when you have multiple factor to select. (supports mTLS/TLS/cleartext)

@lizan not sure if I get it.
The value of the endpoint.transport_socket_selector (single hardcoded name) is used to retrieve entries from the map. So this is selection based on single factor, and deterministically, right?
By label do you refer to actual endpoint.metadata or it does not matter, can be a field in message Endpoint as well?

PR has been modified to match the proposal, using actual fields in endpoints plus match semantics for transport socket.  @htuch  @lizan
PTAL, thanks.

ping. any updates? Its been two weeks.

Test are now all passing. PTAL, thanks.

/retest

All tests passed now, PTAL, thanks.

@htuch Could you take a look to see anything else we need to update before merging?


New functionality for merging streams and inferring iloci

Description pending

[ ] Full test coverage? Any additional tests that could easily be added?
[ ] API documentation up-to-date? Docstring examples?
[ ] Is the CHANGELOG up-to-date?

Codecov Report

Merging #66 into master will decrease coverage by 2.89%.
The diff coverage is 29.78%.

@@           Coverage Diff            @@
##           master     #66     +/-   ##
========================================
- Coverage     100%   97.1%   -2.9%
========================================
  Files          18      20      +2
  Lines        1091    1138     +47
  Branches      254     262      +8
========================================
+ Hits         1091    1105     +14
- Misses          0      33     +33

Impacted Files
Coverage Δ

tag/__init__.py
100% <100%> (ø)
:arrow_up:

tag/locus.py
20.68% <20.68%> (ø)

tag/select.py
89.36% <37.5%> (-10.64%)
:arrow_down:

tag/merge.py
44.44% <44.44%> (ø)

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 86ca8bf...1c0c402. Read the comment docs.

Superseded by #68 and #71.


How to implement Early-Stopping in MXnet?

Hi,
I want to do some scheduling in the training process:

halve the learning rate when the validation accuracy doesn't increase
stop the training when the learning rate is small enough

So I need to get the accuracy and learning rate history, but I can not find something like a monitor holding these information. Can anyone help?

You can add a batchend callback

Hello, @wsstriving @piiswrong. As I've seen quite a few issues for this topic, I'm planning to implement an EarlyStopping class in mxnet.callback (just like what Speedometer does) for stopping the training process for Python when the performance metric is not improving for a bit rounds (with a patience parameter for the control). That will be using the epoch_end_callback.
It will need to modify both mxnet.callback.py and a little bit of base_module.py for the process to return.
Do you think this is necessary?

Its better to write the training loop yourself. Its actually pretty simple

Hello @piiswrong, thank you for the reply and your nice job for this framework. Sure, I agree that implementing a function for early stopping is not quite difficult.
However, my feeling is that early-stopping is a common feature in lots of other deep learning frameworks, and we even have that in R.  So this will be nice if we can have something similar that can make python users' life easier, too. Except for this, beginners who used other frameworks may find this more friendly. I've tried to make the new class multi-functional that can accept few useful parameters and should also be able to handle built-in metrics automatically.
Except for this, the other question we are facing now is that you can use callback functions for saving checkpoints of the model for early stopping, however, these callback functions cannot stop the fitting function without some minor modifications in base_module.py. This is also something that has also been covered in #6304 .

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


feat: update visibility

This adds in a few more comments than intended due to odd rebasing. Ah well.
Anyways, this adds in visibility changes which allows for someone to set the visibility of the tilemap which then gets set for all chunks.

Tests are broken but are fixed post botched rebases.


Vs2017 Build

I had issues building to the VS2017.
I added some more instruction that helped me build in VS2017.

This should all work automatically now thanks to some premake magic.


Issue/stautdef not initialized

removed constraint that state variables must be initialized.
ensured that TorXakis will not crashed when a variable is used before be assigned a value.

The tests for ANY are failing, could you check that @pjljvandelaar?

I propose to squash and merge.
Make a TODO / issue of using right!


[Debugging Report]: #![feature int_roundings] may not be used on the stable release channel

System Info
System:
OS: macOS 13.2.1
CPU: (10) arm64 Apple M1 Pro
Memory: 198.03 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.16.0 - ~/Library/Caches/fnm_multishells/3220_1678612243488/bin/node
npm: 8.11.0 - ~/Library/Caches/fnm_multishells/3220_1678612243488/bin/npm
Browsers:
Chrome: 110.0.5481.177
Safari: 16.3
Safari Technology Preview: 16.4
npmPackages:
@rspack/cli: workspace:* => 0.1.0
Details
cargo build throw error:

rustup toolchain list show:
❯ rustup toolchain list
stable-aarch64-apple-darwin
nightly-2022-12-15-aarch64-apple-darwin (default) (override)
nightly-aarch64-apple-darwin

Reproduce link
No response
Reproduce Steps

run cargo clean && cargo build

we don't use stable channel please check your rustup show result to see whether you use the right nightly version

@ycjcl868 can you check if you have RUSTC_WRAPPER env set to a stable rustc?

Fixed by brew uninstall rust, because there is a conflict between the brew install rustand rustup install.


get a Minimum unirest-java

i want to remove dependency get a minimum library

com.konghq
unirest-java
3.8.00

com.google.code.gson
gson

org.apache.httpcomponents
httpasyncclient

when i exclude gson replace my custom json lib(like jackson, fastjson....)  i get err
java.lang.NoClassDefFoundError: com/google/gson/Gson
now the library default and Strong binding gson
feature:

support interface for ObjectMapper?
support asObject(Type responseType)?

public interface ObjectMapper {
 T readValue(String value, Class valueType);
//replace     readValue(String value, GenericType genericType)
 T readValue(String value, Type valueType);
//default  T readValue(String value, GenericType genericType){
//	throw new UnirestException("Please implement me");
//}
String writeValue(Object value);
}

You have to implement an alternative ObjectMapper and add it to the configuration in order to use a different JSON implementation, I'll look into being able to exclude it although some things (like .asJson) is it's own implementation that leverages GSON and cannot be replaced. So excluding gson will break that

I've made the default object mapper lazy in 3.8.06, but you will still need gson on the path in order to work with the asJson methods as they do not use any other implementation


Direct Messages

As editor
I would like to send direct messages to my local experts to ask questions to individuals.

And contributors must be able to send direct messages to the system as well @tillprochaska @drjakob

closed via #167


Bump Santa Tracker and re-enable smoke tests

This upgrades Spotless underneath Santa Tracker that caused a configuration caching issue previously.

@bot-gradle test RfM please.

OK, I've already triggered ReadyForMerge build for you.


Read Raw data withouth smoothing.

Hi,
Is there a way to read raw data from the sensor (without smoothing)?
Thanks!

Hi!
There is no function for this at the moment, but its on my "todo" list.

Great! That would be a great way to know if a load cell has the red cable broken, since values are changing so much you can not really see that with the smoothing.
Thanks!


[Publishing] Create Gcloud commands and rest API for below templates. Redshift, Snowflake to Target GCS

Java - RedshiftToGCS
Python - RedshiftToGCS
Java - SnowflakeToGCS
Python - SnowflakeToGCS
Add the commands in : go/go/dataproc-gcp-documentation-internal document also contains commands for reference from other templates

Added to Document

Commands added to document. Open to review.

Commands added. Review is left


cache: false, and renderer first column issue

Ok i have about 8 columns, all of them have renderers that set color and return some data etc. this works fine but whenever i change my first column
form
 { id: 'name', header: 'Sector', align: 'left', width: 75 }
to
  { id: 'name', header: 'Sector', align: 'left', width: 75 , cache: false, renderer: function (tb, data, draw) {
       if (draw) { tb.pdf.fillColor('black'); return data.name }
       return ``
}}

All the lines of data end up on 1 line overlapping, if i swap back it renders correctly, i worked around the issue by adding a blank column at the end of each row that has 0 width and just sets tb.pdf.fillColor('black') return '', that way the color is correct for the next line ... but this seems hacky and the fact when i do the above it breaks the layout seems bad

Could you provide a complete script with datas? I tried with the table in the README.md, setting cache: false and your renderer on the first column and everything works as expected. Thanks


Collection+JSON self link behavior

It seems we were having some issues with acceptance tests not actually working as intended. I'm working on a PR that fixes that. It seems we had some CJ behavior that's in conflict with some of the acceptance examples but that wasn't caught before, and that I think we have to revisit.
The question is how to treat "self" links. CJ has a generic "links" collection on each resource, but also a "href". At the moment we render a self link at the top level as a generic self link, and at lower levels as href. I think both of these are wrong.
@mamund clarifies here: https://groups.google.com/d/msg/collectionjson/RHcw72kHUno/hzF3WSbn-ZsJ

yes, the top link SHOULD be the collection URL, which will not always be the self URL.

In Collection+JSON a singular resource is represented as a collection of one. So the way I interpret this is: If we're rendering a "real" collection (a Yaks::CollectionResource), then render a self link as "href", and not under "links". If we render a singular resource (Yaks::Resource), render it as a self link under "links", and not as "href".
Does that make sense? @carlesjove @mamund any input you can give on this? Thanks!

if i understand the Q here...
the top link SHOULD always be the collection link (collection.href). that is because rendering a "single resource" in Cj is actually a Cj collection with a single item
the self link SHOULD always appear in the links array (collection.links[{rel:"self",...},...]).
does that clarify things?

That does help somewhat. In Yaks we do make a distinction between serializing a single object or serializing a collection. In either case we first build up an intermediate "resource object", and then output formats (e.g. CJ) can work with that to the best of their ability.
So suppose I'm outputting a single object, and I have configured both a self and a collection link on it.
Yaks::Resource.new(
  links: [
    Yaks::Link.new(rel: :self, href: "/foo/15"),
    Yaks::Link.new(rel: :collection, href: "/foo")
  ]
)

this could be rendered with
  "href": "/foo",
  "links": {"rel": "self", "href": "/foo/15"}

whereas a collection
Yaks::CollectionResource.new(
  links: [
    Yaks::Link.new(rel: :self, href: "/foo")
  ]
)

would be
  "href": "/foo",
  "links": {"rel": "self", "href": "/foo"}

Does that look good?
What if a single resource does not have a collection URI? Should we consider it an error to try to output that to Collection+JSON? Or do we omit the "href"? (same for a collection without a self link).

first, the examples for single and collection look good to me. this is the same output i produce in my own examples.
also, it is valid for a representation to not have a collection.href property -- this happens when the collection is read-only. you would still emit a "self" link in the collection.links[] array, tho. this is true whether you are rendering a "single-item" collection (your Yaks::Resource) or a "multi-item" collection (your Yaks::CollectionResource).
make sense?

Yeah that makes sense. Not sure how we would expose that distinction in our existing API, but I understand the rationale.

cool. feel free to ping me for these kinds of clarification -- it reminds me that the Cj docs are lacking and working through this w/ you helps me quite a bit.
i understand about the challenge of supporting all these details -- esp. across media type designs. i really love the work you're doing here.

I'll have a look at this and the full discussion tonight. I'm into daddy
mode at the moment!
On Friday, May 8, 2015, Mike Amundsen<EMAIL_ADDRESS>wrote:

first, the examples for single and collection look good to me. this is the
same output i produce in my own examples.
also, it is valid for a representation to not have a collection.href
property -- this happens when the collection is read-only. you would
still emit a "self" link in the collection.links[] array, tho. this is
true whether you are rendering a "single-item" collection (your
Yaks::Resource) or a "multi-item" collection (your
Yaks::CollectionResource).
make sense?
—
Reply to this email directly or view it on GitHub
https://github.com/plexus/yaks/issues/87#issuecomment-100275423.

@carlesjove
thanks. hopefully, i've articulated the media type details well. you may need to scan the actual implementation details to make sure i've not missed something very imp. regarding Yaks itself.
BTW - was great to spend time w/ you this week in Barcelona for APIDays, thanks.

Well, this whole issue is really tricky, because it can be dealt in many ways. The thing here is that Cj isn't very imperative (even when it's very structured), so a bunch of responses can be valid Cj.
For the situation at hand, this one example is not to passing:
{
  "collection": {
    "version": "1.0",
    "href": "http://www.youtypeitwepostit.com/api/",
    "items": []

The reason is because a CollectionMapperthat sets a self link expects a links object:
class CollectionMapper < Yaks::CollectionMapper
  link :self, 'http://www.youtypeitwepostit.com/api/'

{
  "collection": {
    "version": "1.0",
    "href": "http://www.youtypeitwepostit.com/api/",
    "links": [
      {"href": "http://www.youtypeitwepostit.com/api/", "rel": "self"}
    ]
    "items": []

I think both responses are valid Cj, so we can either:

Expect the second case, and not refactor any code
Refactor code so the response is like on the first case

If we look at another shared example, the Plants collection, we're expecting the second case:
{
  "collection": {
    "version": "1.0",
    "href": "http://api.example.com/plants",
    "items": [...],
    "links": [
      { "href": "http://api.example.com/plants", "rel": "self" },
      { "href": "http://api.example.com/doc/plant_collection", "rel": "profile" }
    ]
  }
}

So well, why not leave it as it is, for now, and just change the expectation? That's consistent with what we are already expecting for the Plans collection and implies zero refactoring.

Sure, we can leave everything as is, or we can make it better :) The current implementation will render a self link at the top level under "links", but will skip self links in lower levels. That's already inconsistent.
Also, while what we generate is structurally valid CJ, it's not always semantically valid. When rendering a singular resource, its self link should not be used to populate "href", because "href" is reserved for the URL of the collection.
I've been thinking we could add metadata to links to differentiate between links that are simply used as identifiers, and others that can actually be looked up. I'm just not sure what to call it. resolvable or dereferentiable both seem a bit wordy :)
class FooMapper < Yaks::Mapper
  link :self, '/api/foo', resolvable: false # indicates that GET /api/foo will *not* work

If the link to the collection is not "resolvable" it should not be used as collection.href

yes, i'd like to take best advantage of the library here and improve as much as possible.
the collection.href property is always a URL (locator, resolvable), not a URI (identifier, not-always-resolvable). it appears in responses to tell clients which URL is valid for POST-ing a new item to the collection. for this reason it SHOULD always appear in responses. the only exception is when the collection is read-only.
to be clear the self link indicates the URL of the current response and, while not a REQUIRED element, it MAY appear in the collection.links array. As a rule, i always include the selflink in that array. it would be absolutely fine if Yaks always emitted a self URL in the collection.links array.


sched/mqueue: remove sched_lock to improve performance

Summary
sched/mqueue: remove sched_lock to improve performance
remove the sched_lock/unlock to improve the performance by 18%
mq_send Flow                        Cycle Count
mq_send                         Origin  Optimized
|
 ->nxmq_send                       24         24
   |
    ->file_mq_send                209        209
      |
      |->sched_lock               243        N/A  <-
      |->nxmq_do_send             391        348
      |  |
      |  |->sched_lock            434        N/A  <-
      |  |->up_unblock_task       545        459
      |   ->sched_unlock          675        N/A  <-
      |
       ->sched_unlock             684        N/A  <-
         |
          ->up_release_pending    701        N/A
            |
             ->arm_switchcontext  856        610

mq_receive
|
 ->arm_fullcontextrestore        1375       1133
   |
    ->up_block_task              1375       1133
      |
       ->nxmq_wait_receive       1530       1288
         |
          ->file_mq_receive      1606       1310
            |
             ->nxmq_receive      1616       1320
               |
                ->mq_receive     1628       1332  - 18%

Signed-off-by: chao.an<EMAIL_ADDRESS>Impact
message queue
Testing
message queue test

@anchao
Did you confirm that this PR works in SMP mode without any side effects?

Is it tested with multiple threads trying to receive data from same mqueue? I mean the concurrent environment test

Is it tested with multiple threads trying to receive data from same mqueue? I mean the concurrent environment test

Yes, I conducted a local concurrency test on the same mqueue, with 4 threads (2 threads recv / 2 threads send)

@anchao
You have just pushed several new commits which are not sched_lock-related changes.
What is your intention for the commits?

@anchao
You have just pushed several new commits which are not sched_lock-related changes. What is your intention for the commits?

Other patches have some minor code tuning of message queue, mainly to improve the performance further，maybe I should create a new PR to track ?

Other patches have some minor code tuning of message queue, mainly to improve the performance further，maybe I should create a new PR to track ?

@anchao
I prefer to create a new PR for it.

@anchao Did you confirm that this PR works in SMP mode without any side effects?

sched_lock/sched_unlock can't protect the resource in SMP mode. All code which depend on sched_lock/sched_unlock to protect the resource must be change to the critical section, spinlock or semaphore as soon as we can.

As long as I look into the code, the code seems to be protected by critical sections.
However, we need more testing.


Extend the api client for usage with other requests library

This change extends the api client to use with requests libraries such as requests-oauthlib, which can be passed to the client object as a parameter upon creation. Additionally, I've added a number of other request types (e.g. PUT/POST) and refactored the client module accordingly.

I built the bdist_wheel and uploaded client version 0.2.0-dev0 to pypi for this change. Ran unit tests and a simple integration test with the dedupe_enrollments feed using the new client version. Worked like a charm, this is ready to review and merge post-review.

Thanks!


Event Hooks

It would be super cool if webnews had support for triggering events. Things like new posts, canceling, sticky-ing, etc could fire off events. Not sure what would work better, but two options I see are to handle events in the backend, or have webhooks like what github.

Cleaning up old feature requests since this project is now unmaintained.


x/tools/gopls: revisit line directive support

Following our removal of line directive support from the core of gopls, we should re-evaluate whether or not there are selected areas where we can / should expand positions to related positions (e.g. duplicating or re-mapping diagnostics, handling jump-to-definition requests, etc.).

@pjweinb should we close this now that #59124 is fixes?


Create Neural Network- Documentation

@aanchalsethi can you add references? this looks good to me @geekquad

Yes sure for more i will video links in it. Thankyou sir.

Sir there is no folder for neural networks yet.


Adding and fixing support for host-model migration in heterogeneous cluster

What this PR does / why we need it:

Vmi can't migrate back to older nodes (only to nodes with the same or more features than the current one) with host-model cpu
vmi with host-model can't migrate if the target node does't have the same host model even if the target node support the host-model of the source node and has all the required features.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
For instance:

if vmi start with hosmodel-cpu in node01 that doesn't have feature A and than migrate to node02 that has feature A we won't be able to migrate back to node01 because in the case virt-launcher will be schedule with nodeSelector for feature A even due it
can run on node01 witout any problem.
if vmi start with host-model cpuModel in node01 that has host-model A try to migrate to node02 with host-model B that has all the required features and support host-model A cpuModel the migration fails(that should not happen).
Fixes #
Added new field to know if the vmi already migrated and if it did use the old node selectors(of the initial node).
Special notes for your reviewer:
I noticed that there are more bugs related to host-model cpuModel for instance:
vmi with host-model can't migrate if the target node does't have the same host model even if the target node support the host-model of the source node and has all the required features.
I will publish more PRs soon.
Release note:

NONE

/cc @vladikr @iholder-redhat @davidvossel

/retest-required

/retest-required

/retest-required

/retest-required

/retest-required

/approve

/retest-required

/retest-required

/lgtm
Awesome, thanks a lot!

/retest-required

/retest-required

/cherry-pick release0.44

/cherry-pick release0-.44

/cherry-pick release-0.44

/cherrypick release-0.44
/cherrypick release-0.45
/cherrypick release-0.46
/cherrypick release-0.47
/cherrypick release-0.48
/cherrypick release-0.49
/cherrypick release-0.50
/cherrypick release-0.51
/cherrypick release-0.52
/cherrypick release-0.53

/cherrypick release-0.53

/cherrypick release-0.52