Add Secure cookie flag option to session cookie

The session cookie needs the ability to have the 'Secure' flag set.  This PR adds support for always use secure flag, never use secure flag and use secure flag only if initial request is SSL.
Included unit tests for Secure flag as well as HTTPOnly flag.

Hi @SteveArr, I'm your friendly neighborhood Microsoft Open Technologies, Inc. Pull Request Bot (You can call me MSOTBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.msopentech.com.

TTYL, MSOTBOT;

@SteveArr, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSOTBOT;

@blowdart can you have a look?

My usual naming issues appear
Https != Secure (We should look at CookieOptions as well to fix this)
There's no other problem aside from that.

 I don't consider this a bad thing, other opinions may vary.

This would probably be better addressed as part of abstractions, where there is already an open issue on the topic. https://github.com/aspnet/HttpAbstractions/issues/42

After reading your comments, here is the change I propose:
Take CookieSecureOption.cs and move it up into Aspnet/HttpAbstractions like @blowdart is recommending.  Update code comments appropriately.
Update this pull request to use that relocated CookieSecureOption.cs
Update Aspnet/Security/Microsoft.AspNet.Authentication.Cookies to also use the newly located CookieSecureOption.cs to reduce code duplication.
Question:  I am unfamiliar with the process for updating code in three different projects.  Do I have to submit a PR to HTTPAbstractions first and let that get in before making the changes to Session and Security?

You can submit concurrent PRs in multiple repos, just and links to each related PR in the comments.
Do you know how to use the global.json file to compile multiple repos locally?

@Tratcher ,  I am unaware of how to use the global.json file to compile multiple repos locally.  Can you forward me some information or pointers?

In Session modify the global.json add a relative reference to HttpAbstractions. This way your local changes will be used rather than the nuget packages.
{
    "projects": [ "src", "..\\HttpAbstractions\\src" ]
}

Do not check in this change, it is only for local development.

Got it.  I will work on this tonight when I get home.

Hi @SteveArr, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@Tratcher Could you look at this one (and the corresponding HttpAbstractions one)?

@SteveArr Can you update your CLA as described above?

@SteveArr Are you still looking into this one?

Closing this one, we'll do https://github.com/aspnet/httpAbstractions/issues/42 instead.


Push spontaneously disabled itself

Apparently at 11:24am today sygnal tried to send APNS to my Vector but Apple rejected it with invalid token, which causes sygnal to give up on trying to push the device.  Who knows why; possibly to do with switching back & forth from testflight builds.
To mitigate this, surely the app should try to re-enable push every time the app is launched (if it's enabled in prefs), in case Apple have randomly cancelled push from behind one's back...

see https://github.com/vector-im/vector-ios/issues/333


Merged dependency updates from dependabot recommendations

Remaining dependabot proposals batched for efficiency
Tested notebooks, UI
Signed-off-by: Nigel Jones<EMAIL_ADDRESS>

Thought we agreed in this morning's call that we'd only merge these in the mornings? 👀


Fix null value return by the getFlavor() method in release

Fix null value return by the getFlavor() method by adding a proguard rule to keep the BuildConfig file when obfuscating the code

Nice. Thanks!


Project title disappears in dark mode

When we switch to dark mode in the project, the title disappears.

Salam @AhsanAyaz Bhai,
Could you please confirm that this is also happening at your end?


How is it possible to export magnetic field Values Bx, By for every (x,y) meshelement in Maxwell2DAdd ...

Description of the feature
i tried to use the functions export_mesh_obj() and export_field_file_on_grid() with some options but i did not get a result. Result is always None
Example code:
import pyaedt as ed
app = ed.Maxwell2d(specified_version=specified_version, projectname=name_of_project, designname=name_of_design)
mesh = app.post.export_mesh_obj(setup_name="Setup1", intrinsic_dict=None)
Steps for implementing the feature
No response
Useful links and references
No response

Hi @briewo,
Have you tried using export_field_plot?
m2d.post.export_field_plot(plot_name, file_path)
This return the exported file path.
This file (which can be an .aedtplot or .case) contains all the information about mesh data and field data.
Hope this helps!
Giulia

@briewo
Another way to do it is using the plot_field() which creates a plot using Pyvista (if you are interested more in the visualization of your results). This creates an object through which you can access PyVista functionalities + creates an .aedtplot file and exports the field plot as an image.
Please look at this example to see how it is used: https://aedt.docs.pyansys.com/version/stable/examples/03-Maxwell/Maxwell2D_DCConduction.html

Hi @briewo,
Does this solve your issue?
if it does I'll close this issue.
Please do let us know!
Giulia


Upgrade CI config to use new GitHub Checks API

Based on their release date, my previous CI upgrades lasted literally one day before going obsolete
https://blog.travis-ci.com/2018-05-07-announcing-support-for-github-checks-api-on-travis-ci-com
https://docs.travis-ci.com/user/open-source-on-travis-ci-com/#Existing-Open-Source-Repositories-on-travis-ci.org

Not only that, we're using Actions


Migrate to new padding rule

Describe your changes
Change the padding rule for RPO so that it uses the one in the xHash paper.
Checklist before requesting a review

Repo forked and branch created from next according to naming convention.
Commit messages and codestyle follow conventions.
Relevant issues are linked in the PR description.
Tests added for new functionality.
Documentation/comments updated according to changes.

@Fumuran - could you merge the latest next into this branch?

@Fumuran could you update this branch to use miden-crypto v0.11.0 (I just published it to crates.io) and also merge next into this branch to make sure we don't have any merge conflicts?

@Fumuran - this is basically done, right?
If so, before merging this, let's create a parallel PR in miden-base to migrate to the to this branch. I'm expecting that PR to be quite a bit of work because of the padding rule changes.

@bobbinth Should I prioritize migrating miden-base to the new padding rule over this issue (https://github.com/0xPolygonMiden/miden-base/issues/836)?


Add allow failures for WPCS dev-develop

This is an attempt to fix the failing builds based on comment.
I'm not an expert with travis, so not 100% sure the allow_failures is correct.
The WPCS_BRANCH is set to dev-master so that it's stable (develop is in the works currently).

Oh and you may also want to have a look at WPCS PR https://github.com/WordPress/WordPress-Coding-Standards/pull/1906 to see how to get the nightly builds working again.

@jrfnl I've added the lines but it still fails on if [[ ${TRAVIS_PHP_VERSION:0:3} > "7.1" ]]; then for PHP versions 7.0 and 7.1. I'm missing something. Also, I think the 7c3b58f commit and e4b2e96 where I've put the nightly out of if/elseif/else conditional are the same (both failed on the same thing).

@dingo-d Just had a look at the error Travis is showing. This has to do with the change from trusty to xenial. Basically, a number of Travis PHP images ship with incompatible PHPUnit versions (yeah, the stupidest thing ever, but why would they care... ).
For the images where this previously happened on trusty, we had the condition you refer to in place to get round it.
Now the builds are using xenial, we either need to investigate which images are problematic and adjust the condition based on that, or better yet; stop relying on the PHPUnit version shipped with Travis and for all test builds do a full composer install and run the tests via vendor/bin/phpunit or composer run-tests.
Does that help ?

Nightly
As for the builds against PHP  nightly, as PHPUnit 7.x is not officially supported on PHP 8.0, you'll need to do a composer install with --ignore-platform-reqs to get PHPUnit 7.x to run on PHP 8.
Once that's done, the tests should run fine on PHPUnit 7.x as the test suite doesn't use the mocking framework.
The tests will probably fail on PHP 8.0, but that will be mostly solved once TRTCS moves to PHPCSUtils/with a newer minimal PHPCS version (unreleased as of yet).
Most failures are to do with some BC-breaks in PHP 8, which have so far, partially been mitigated by me in PHPCS itself, though most fixes are not yet included in a released version. For most things, PHPCSUtils already works around them in a cross-version way.
WPCS dev-develop
As for WPCS dev-develop, as PHPCSUtils is regarded (for now) as "unstable", you either need to add the minimum-stability setting to composer.json, but that affects all packages, while we only really want it for the one build, so better yet, you can adjust this in the . travis.yml script with something like the below above the composer require command:
  - |
    if [[ ${WPCS_BRANCH} == "dev-develop" ]]; then
      composer config minimum-stability dev
    fi

@dingo-d Let me know if you want me to finish this off.

The xenial issue is super frustrating 😣
I'll give this another go and then let you do your magic 😄

The xenial issue is super frustrating

Only the first time you run into it. After that you know what's going on ;-)
If Travis caching for the composer downloads is setup properly, you're basically better off not relying on the Travis images for dependencies and just doing a composer install. Once this repo switches over to using PHPCSUtils, you'd need that anyway, so may as well get it over with now.

Now I'm getting

The command "phpenv global 5.5" failed and exited with 1 during .

For PHP 5.5 and 5.4. Can you check what I missed?

For PHP 5.5 and 5.4. Can you check what I missed?

You put them back in the php key, which is what won't work anymore on xenial. Those are failing.
The ones you put in the jobs key with the dist key are installing fine, but those are incomplete as you now test them only against the "low" settings, not the "high" settings.

@jrfnl The builds are passing, is this ok now? 😂
I suck at travis, GH actions are a lot easier to understand.

Well, if the same can be done with GH Actions, you can always change the CI setup ;-)

Well, if the same can be done with GH Actions, you can always change the CI setup ;-)

I'll try to play with it :+1:

@jrfnl This seems to pass. Can you give it another look? Thanks!

Closing as superseded by the now merged PR #261.


[Question] Why is gym master required?

Hello,
I was wondering why is gym master required and not a more specific version like gym >= 0.22 for instance?
This prevents other projects from limiting the gym robotics version in case there are breaking changes in newer gym versions.

This was a mistake, we'll cut a new release fixing it


[FLINK-8599] Improve the failure behavior of the FileInputFormat for …

What is the purpose of the change
This pull request is intent to improve the failure behavior of the ContinuousFileReader, currently if a bad file (for example, a different schema been dropped in this folder) came to the path and flink will do several retries.
However, since the file path persist in the checkpoint, when people tried to resume from external checkpoint, it threw the following error on no file been found and the process cannot move forward.
java.io.IOException: Error opening the Input Split s3a://myfile [0,904]: No such file or directory: s3a://myfile
The change is to check if the path exist before open the file, if error occurs and bad file removed, flink should resume the process and continue.
Brief change log

*Add a file exist check before open the file *

Verifying this change

Manually verified the change by introduce a bad file while continuously monitoring the folder, after remove the bad file, the process continued.

Does this pull request potentially affect one of the following parts:

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

Documentation

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

This is very inefficient against an object store, potentially adding a few hundred millis and $0.01 per file.  I would simply catch FileNotFoundExceptions raised in the open() call and treat them specially
See How long does FileSystem.exists() take against S3?

Thanks @steveloughran for your feedbacks, I updated based on your suggestions.

@steveloughran Updated.

@ChengzhiZhao I think that we should handle the "bad" splits better.
@StephanEwen You are right that we should give the user the option to fail the job or ignore them.

@StephanEwen @kl0u Thanks for you feedback, I will put an option for user to choose

The approach here does not work (there is also no test, otherwise that would have been caught).
Flink does not magically load configs like Hadoop, Flink passes configs explicitly.
Aside from that, we first should actually decide whether this should be

@StephanEwen, thanks for your feedbacks. for our use case we'd like to take the bad file out to continue process instead of fixing the bad file to be able to continue. I think it can be more as job/application specific so we won't have it globally, it will give people flexibility. If that is the decision here, we can do as a connector parameter not via config which affect all the jobs. Please suggest.

Hi @ChengzhiZhao , would you like to keep on working on the issue? The PR does not seem to have many conflicts with the master branch and with a bit of work it can get in.
If you want to work on this the missing bits are:

testing
remove the ConfigOption and add a connector parameter

If you do not want to work on the issue, please close the PR.
If you do not reply I will close it in the next couple of days.

Hi @kl0u, thanks for your feedback. Yes, I'd like to keep working on it. I'd try adding the missing parts and more testing for it.

Thanks a lot @ChengzhiZhao !

@kl0u, In your comment add a connector parameter, do you mean add an additional parameter, for example continueOnFileNotFound on call of createFileInput
https://github.com/apache/flink/blob/15a7f978a2e591451c194c41408a12e64d04e9ba/flink-streaming-java/src/main/java/org/apache/flink/streaming/api/environment/StreamExecutionEnvironment.java#L1352-L1356

I was thinking something like the FileProcessingMode in the readFile method.

Hey @kl0u, I made changes with the suggestions, please let me know your feedbacks. Thanks!

@kl0u , please let me know your feedbacks if we can merge the PR.

I'm closing this as "Abandoned", since there is no more activity and the code base has moved on quite a bit. Please re-open this if you feel otherwise and work should continue.


perf: change scalar index to return RowIdTreeMap instead of u64 array

The filtering paths that use scalar indices are all built to use RowIdTreeMap.  Scalar indices were built to use UInt64Array.  This means we have to copy from one to the other (an O(N log(N)) operation.  When we just had btree indices this was a fairly cheap operation since the indices shouldn't be returning large #'s of rows anyways.  Now that we have BITMAP and LABEL_LIST we can have indices that return very large #'s of rows and this copy was expensive.  By changing the scalar indices to use RowIdTreeMap directly we skip the conversion.
NOTE: any LABEL_LIST or BITMAP index that was previously created will be invalid and will need to be recreated.  Since we haven't had an official release of these index types I am not considering this a breaking change.

Codecov Report
Attention: Patch coverage is 87.58621% with 18 lines in your changes missing coverage. Please review.

Project coverage is 79.91%. Comparing base (a237fca) to head (e0ef6a9).

Files
Patch %
Lines

rust/lance-core/src/utils/mask.rs
66.66%
6 Missing :warning:

rust/lance-index/src/scalar/bitmap.rs
83.87%
5 Missing :warning:

rust/lance-index/src/scalar/label_list.rs
85.18%
1 Missing and 3 partials :warning:

rust/lance-index/src/scalar/lance_format.rs
95.74%
0 Missing and 2 partials :warning:

rust/lance-index/src/scalar/flat.rs
83.33%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2587      +/-   ##
==========================================
- Coverage   79.93%   79.91%   -0.02%
==========================================
  Files         212      212
  Lines       61660    61639      -21
  Branches    61660    61639      -21
==========================================
- Hits        49285    49256      -29
- Misses       9420     9445      +25
+ Partials     2955     2938      -17

Flag
Coverage Δ

unittests
79.91% <87.58%> (-0.02%)
:arrow_down:

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

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


UTOPIA-1308: (backend) add new status

Description
This PR includes the following proposed change(s):

CPO can now move a PIA from 'Pending completion' => 'Complete'

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Updating Testing Framework(s)
[ ] Version change

How Has This Been Tested?
Move a new Delegated PIA from 'Incomplete' => 'Complete'
Development Dependency Working Agreement

[x] My code DOES NOT include the importing of new dependencies into the DPIA ecosystem
[ ] My code DOES include the importing of new dependencies into the DPIA ecosystem
If new dependencies are being introduced to the DPIA ecosystem:
[ ] The functionality of the dependency drastically reduces code complexity and makes my changes more easily maintainable and readible
[ ] The dependency being introduced does not contain multiple layers of nested dependencies introducing maintainability complexity to the DPIA ecosystem

Frontend Development Changes

[ ] N/A
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to project documentation or diagrams that reflect my changes
[ ] New and existing unit tests pass locally with my changes
[ ] My code follows Airbnb React Style Guidelines

API Development Changes

[x] N/A
[ ] I have performed a self-review of my own code
[ ] My code follows standards and practices outlined in the BC Government API Development Guidelines
[ ] New and existing unit tests pass locally with my changes
[ ] My changes includes Swagger documentation updates that reflect the changes I am introducing

Definition of Done

do you want to add unit test in a different PR or will add the ut later?


Update references from 3.0.3 to 3.1.0

Basic search and replace. Would appreciate reviews.
Signed-off-by: Mike Ralphson<EMAIL_ADDRESS>

A bit late to the party, but I approve of these changes!
For the record, I asked if there was some kind of URL to point to the latest release and I was told that whenever there was a new release this global search & replace would be conducted 😀


nixos/switch-to-configuration: Improve socket handling

We are now restarting sockets as well so things like permission or owner
changes are properly applied when they are changed.
We also stop the service before reloading systemd and restart the socket
instead of the service if serviceConfig.stopIfChanged is not set.

Motivation for this change
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Related:


[Bug]: Automatic dependency guard update allows skipping checks

Is there an existing issue for this?

[X] I have searched the existing issues

Is there a StackOverflow question about this issue?

[X] I have searched StackOverflow

What happened?
The CI action to automatically update the dependency guard baseline doesn't result in CI running again for the new changes. This allows a PR to merge without passing CI, like what happened in #material
Relevant logcat output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This issue is more global than just dependencyGuard. It is also triggered by automated screenshot updates.
I've reported it last year 🙈:

https://github.com/android/nowinandroid/issues/1045


Add problem type (Fixes #248)

Adds support for different problem types (i.e., multi label classification) in the text classification pipeline.
Python:
from transformers import pipeline
classifier = pipeline('text-classification', 'unitary/toxic-bert')
classifier('I like you. I love you')
# [{'label': 'toxic', 'score': 0.0007729075732640922}]

JavaScript
import { pipeline } from '@xenova/transformers';
const classifier = await pipeline('text-classification', 'Xenova/toxic-bert', {quantized: false});
const output = await classifier('I like you. I love you');
// [{label: 'toxic', score: 0.0007729064091108739}]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


feat: add prettier badge

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


Invalid syntax error caused by parameter *input_size in Python 2.7 .

Hello,
Was really pleased to find this repo to help visualize my neural networks.  No errors encountered in python 3.6. However, I get the following error in python 2.7 .
Failing environment:
Ubuntu 16.04
python 2.7 (anaconda)
$ pip install torchsummary
Running the demo code provided by this repo gives:
Traceback:
Traceback (most recent call last):
  File "/home/dl/code/dljy-densepose/print_resnet.py", line 13, in <module>
    from torchsummary import summary
  File "/home/dl/anaconda3/envs/torch_py27/lib/python2.7/site-packages/torchsummary/__init__.py", line 1, in <module>
    from .torchsummary import summary
  File "/home/dl/anaconda3/envs/torch_py27/lib/python2.7/site-packages/torchsummary/torchsummary.py", line 9
    def summary(model, *input_size, batch_size=-1, device="cuda"):
                                             ^
SyntaxError: invalid syntax

A remedy:
# Remove astericks from *input_size in function signature:
def summary(model, input_size, batch_size=-1, device="cuda"):

     ... omitted code ...

     #model(*x)   # change this also.
     x = torch.rand(input_size)
     model(x)

Thank you for the suggestions.  The code runs correctly on Python2 now.


[jqLight] Prepend method freezes browser

jqLight's prepend method freezes browser completely. Here is a plunker. Append method works fine.

Duplicate of #11217 (e.g. see https://github.com/angular/angular.js/issues/11217#issuecomment-76715981).
Because of how the Angular compiler works, you can't prepend elements to the element you are compiling during the compilation phase.


fix typo in port_example.h

@googlebot I signed it!

@googlebot I signed it!

The CLA check failed. This needs to pass in order for us to consider merging this.

The CLA check failed. This needs to pass in order for us to consider merging this.

Resigned CLA just now. PTAL~

Looks great, thank you!


inputToolbar is not visible

The input bar is never visible.I have been playing with the DemoMessagesViewController class and quite frankly still trying to wrap my head around it. I did some basic commenting-
out but surely not enough to make the input bar invisible. What am I missing?
#import "DemoMessagesViewController.h"
@implementation DemoMessagesViewController
#pragma mark - View lifecycle
/**

Override point for customization.

Customize your view.
Look at the properties on JSQMessagesViewController and JSQMessagesCollectionView to see what is possible.

Customize your layout.
Look at the properties on JSQMessagesCollectionViewFlowLayout to see what is possible.
*/

(void)viewDidLoad
{
[super viewDidLoad];
self.title = @"JSQMessages";
/**

You MUST set your senderId and display name
*/
self.senderId = kJSQDemoAvatarIdSquires;
self.senderDisplayName = kJSQDemoAvatarDisplayNameSquires;

/**

Load up our fake data for the demo
*/
self.demoData = [[DemoModelData alloc] init];

/**

You can set custom avatar sizes
*/
self.collectionView.collectionViewLayout.incomingAvatarViewSize = CGSizeZero;
self.collectionView.collectionViewLayout.outgoingAvatarViewSize = CGSizeZero;

self.showLoadEarlierMessagesHeader = YES;
self.navigationItem.rightBarButtonItem = [[UIBarButtonItem alloc] initWithImage:[UIImage jsq_defaultTypingIndicatorImage]
style:UIBarButtonItemStylePlain
target:self action:@selector(receiveMessagePressed:)];
/**

Register custom menu actions for cells.
*/
[JSQMessagesCollectionViewCell registerMenuAction:@selector(customAction:)];
[UIMenuController sharedMenuController].menuItems = @[ [[UIMenuItem alloc] initWithTitle:@"Custom Action" action:@selector(customAction:)] ];

//self.inputToolbar.contentView.leftBarButtonItem = custom button or nil to remove
//self.inputToolbar.contentView.rightBarButtonItem = custom button or nil to remove
// self.inputToolbar.maximumHeight = 150;

}
......

see the following issues about JSQMessages + UITabbar:
https://github.com/jessesquires/JSQMessagesViewController/issues?q=is%3Aissue+tabbar+is%3Aclosed


Cannot use ContainerEngine as a shared static container

Describe the bug
It is not possible to share and reuse the same ContainerEngine instance for multiple tests at the moment, as we close the engine between each tests. This means it's only usable with a single test.
To Reproduce
@Testcontainers
final class MyTest {
  @Container
  private static final ContainerEngine ENGINE =
      ContainerEngine.builder()
          .withIdlePeriod(Duration.ofSeconds(2))
          .build();

  @Test
  void shouldAssertFoo() {
    assertThat(BpmnAssert.getRecordStream().deploymentRecords()).hasSize(3);
  }

  @Test
  void shouldAssertBar() {
    assertThat(BpmnAssert.getRecordStream().deploymentRecords()).hasSize(3);
  }
}

Expected behavior
Instances ContainerEngine can be used with the built-in Testcontainers extension like any other container.
Log/Stacktrace
If possible add the full stacktrace or Zeebe log which contains the issue.

Full Stacktrace

java.lang.IllegalStateException: stream has already been operated upon or closed
at java.base/java.util.stream.AbstractPipeline.spliterator(AbstractPipeline.java:346)
at java.base/java.util.stream.ReferencePipeline.iterator(ReferencePipeline.java:143)
at org.assertj.core.presentation.StandardRepresentation.format(StandardRepresentation.java:603)
at org.assertj.core.presentation.StandardRepresentation.singleLineFormat(StandardRepresentation.java:544)
at org.assertj.core.presentation.StandardRepresentation.smartFormat(StandardRepresentation.java:558)
at org.assertj.core.presentation.StandardRepresentation.toStringOf(StandardRepresentation.java:246)
at org.assertj.core.presentation.CompositeRepresentation.toStringOf(CompositeRepresentation.java:40)
at org.assertj.core.error.MessageFormatter.asText(MessageFormatter.java:78)
at org.assertj.core.error.MessageFormatter.format(MessageFormatter.java:69)
at org.assertj.core.error.MessageFormatter.format(MessageFormatter.java:62)
at org.assertj.core.error.BasicErrorMessageFactory.create(BasicErrorMessageFactory.java:107)
at org.assertj.core.internal.Failures.assertionErrorMessage(Failures.java:144)
at org.assertj.core.internal.Failures.failure(Failures.java:125)
at org.assertj.core.internal.Iterables.assertAllSatisfy(Iterables.java:1162)
at org.assertj.core.api.AbstractIterableAssert.internalAllSatisfy(AbstractIterableAssert.java:3735)
at org.assertj.core.api.AbstractIterableAssert.allSatisfy(AbstractIterableAssert.java:3731)

False positive, this is an issue with zeebe-process-test.


Migrate msal-common tests to Jest

Migrates msal-common tests to Jest
Also removes input params from error constructors for Empty Scopes errors. (If the error is thrown there's only one value it could be)

Coverage increased (+12.2%) to 96.024% when pulling b43af493ba52d692a7de383ffc4c6a9387b99264 on migrate-to-jest into 0bf4bfc4b8c7ac6ea11b43eceaf406308418c231 on dev.


Update default project.json TFMs

When manually creating a new project.json file, opening IntelliSense, and selecting Default project.json, the default project.json file is created with old DNX target framework monikers. Since DNX is dead, this PR updates the default project.json to use the same TFMs used by the ASP.NET Core project templates in VS 2015.

Thanks @scottaddie !


Addng Grunt with JSHint

We can add more tasks to Grunt.
Run sudo npm install
This will install all packages declared in package.json.
After that, run: grunt.
Our next step is put jasmine with phantomJS and another tasks.

@diegoeis Please, update this PR, in files changed show 4,095 files edited, this is correct?

@Wylkon this PR was moved to #1388.
Now, that contains just the right commits.


WHARF_DB_PORT collides with one provided by Kubernetes

Since wharf-api v4.2.0 it changed the environment variable names. One of those are WHARF_DB_PORT, which was previously DBPORT.
Not sure how kubernetes populates this, but it adds more than just WHARF_DB_PORT, but it also has values that collides with how wharf-api parses these values. Such as:
WHARF_DB_PORT_5432_TCP_ADDR=<IP_ADDRESS>
WHARF_DB_PORT_5432_TCP_PORT=5432
WHARF_DB_PORT_5432_TCP_PROTO=tcp
WHARF_DB_PORT_5432_TCP=tcp://<IP_ADDRESS>:5432
WHARF_DB_PORT=tcp://<IP_ADDRESS>:5432
WHARF_DB_SERVICE_PORT=5432
WHARF_DB_SERVICE_PORT_TCP_POSTGRESQL=5432

And lots lots more.

If the deployment already specifies an environment variable for WHARF_DB_PORT, then that will override the value provided by Kubernetes.
For backward compatibility, we should still provide the old DBPORT values as well.

Found a temporary workaround to edit the Kubernetes Deployment of wharf-api and add another environment variable for WHARF_DB_PORT=5432. That resolves it until we get a patch up


improve japanese translations

Thank you for your great product.
I am a Japanese software engineer. Please let me suggest a more natural Japanese label.

@ggordonhall Thanks for the merge.


Add an rbl whitelist file #570688#note-10

file: /etc/postfix/rbl_sender_override
format:
some.net OK

I'd think we would still have to create the /etc/postfix/rbl_sender_override file it it doesn't exist yet. A simple touch /etc/postfix/rbl_sender_override before the editconf call might be enough here.

Done.

Merged. Thanks!


refactor: use vitest for tests

Swaps out custom test utilities for Vitest typechecking.

Adds GitHub Action workflow for test, build, typecheck
Deps: Adds Vitest, removes Jest, switches to pnpm (happy to switch back to npm, just lmk)

@gvergnaud let me know if you want to head in this direction and I can resolve the conflicts.
If not, feel free to close this PR so it doesn’t grow too stale and I can stop watching it.

I see you use  assertType<X>(Y) to assert the type, any particular reason?
assertType is ok for checking runtime value type, but not great to compare 2 types
for example you can do something like this

and it will not error
because for runtime value, all we care is whether we can assign a value to something(to variable, argument, property etc)
which mean as long as the value type is sub type of the required type, then it is ok. They dont need to be exactly the same type
which is why assertType<number>(2 as const) does not trigger any error, because 2 is sub type of number
But type level programming is about creating all kind of utility types, we need to make sure the output are exactly the same type as the expected type, so it is better to use type equality check here
I also saw you use expectTypeOf<X>().toEqualTypeOf<Y>(), this is ok, but it is a bit lengthy
or is there anything I don't know about?


to json -r serializes datetime without spaces

ls | to json -r
{"name":".git","type":"dir","size":480,"modified":"2021-12-2302:09:48.927406137+00:00"}

versus
ls | to json
  {
    "name": ".git",
    "type": "dir",
    "size": 480,
    "modified": "2021-12-23 02:09:48.927406137 +00:00"
  },

note that there are no spaced between date and time and between time and timezone.
it looks like this is squeezing out all the whitespaces
https://github.com/nushell/engine-q/blob/ef59b4aa5124974ec1b0ec9d48e3a81d1fd22271/crates/nu-json/src/ser.rs#L1036
I think the values should be unchanged, right?
/cc @stormasm

@fdncred yes you are right this is not what we want --- let me figure out the next step on how to fix this --- basically we want to retain all of the white space inside the strings of the keys and values ---- but get rid of the white space everywhere else...  Good catch, I was so focused on my table syntax example that I obviously completely missed this ---- let me do some work ---- and then run it by you...

@fdncred so my PR #596 I think fixed this issue...
After you confirm this works the way you think it should we can close this issue (hopefully) or figure out the next step...  Thanks...

hey @stormasm, everything seems to work now. here's my test one-liner that I was breaking it with earlier. ls | to json -r | from json | update size {|s| $s.size | into filesize} | update modified {|d| $d.modified | into datetime}.
good work. closing.

@fdncred thank you for reviewing !  glad that it is working...


On the iOS platform, no request for changing the MTU size is provided.

Hello, everyone. I'm working on a Comose multiplatform project. Can somebody in this group tell me how to request a change in the MTU size on the iOS platform? I notice we have an option for doing it on Android, but not iOS.

iOS (Core Bluetooth) does not allow setting the MTU size (from the central). Your peripheral can set the MTU (within limits) and Core Bluetooth should honor it.
https://stackoverflow.com/a/68389331


Remove all max redirects functionality

Places needed to remove:

in synthetics-sdk-api (proto and ts generated proto)
in broken-links

user facing interface
all default option handling
actual navigation logic

Clarifying comment. We follow ALL redirects, as is the default behavior of Chrome. The customers will no longer be able to specify the maximum number of redirects they want per link.


Rename harness .c sources to .cpp where necessary

Remove hacks from harness CMakeLists.txt to force language.
Contributes to KhronosGroup/OpenCL-CTS#25

Thanks. I was holding off on fixing this until we merge cl12_trunk into master as this makes diff'ing between the branches harder. @jrprice Is this an immediate problem for you? Can you wait until we are done with the merge?

I can work around this locally for now, and certainly don't want to slow down the 1.2 merge, so I'm happy to wait.

@jrprice cl12_trunk has now been merged into master, feel free to rebase this.

feel free to rebase this.

Done, PTAL.

Thanks!


Add modules versions when saving models

Codecov Report

Merging #504 (f4865d2) into main (6866dea) will decrease coverage by 0.04%.
The diff coverage is 87.75%.

:exclamation: Current head f4865d2 differs from pull request most recent head 618f948. Consider uploading reports for the commit 618f948 to get more accurate results

@@            Coverage Diff             @@
##             main     #504      +/-   ##
==========================================
- Coverage   91.03%   90.98%   -0.05%
==========================================
  Files          77       77
  Lines        4304     4349      +45
  Branches      805      813       +8
==========================================
+ Hits         3918     3957      +39
- Misses        214      217       +3
- Partials      172      175       +3

Flag
Coverage Δ

unittests
90.82% <87.75%> (-0.05%)
:arrow_down:

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

Impacted Files
Coverage Δ

...ummingbird/ml/containers/sklearn/tvm_containers.py
94.36% <75.00%> (-1.85%)
:arrow_down:

hummingbird/ml/_utils.py
88.07% <83.33%> (-0.65%)
:arrow_down:

...mmingbird/ml/containers/sklearn/onnx_containers.py
91.20% <100.00%> (+0.60%)
:arrow_up:

...ngbird/ml/containers/sklearn/pytorch_containers.py
84.75% <100.00%> (+0.78%)
:arrow_up:

hummingbird/ml/operator_converters/constants.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Error when building on CentOS

I'm getting an error when I attempt to build the project on CentOS, the same issues happen on Ubuntu too.
/home/osheak/pathfinding/src/math/compare.cpp: In static member function ‘static bool pathfinder::Compare::isAlmostEqual(double, double)’:
/home/osheak/pathfinding/src/math/compare.cpp:36:35: error: ‘abs’ was not declared in this scope
         else if (abs(value1-value2) < std::numeric_limits<double>::epsilon())
                                   ^
gmake[2]: *** [CMakeFiles/pathfinding.dir/src/math/compare.cpp.o] Error 1
gmake[2]: *** Waiting for unfinished jobs....
gmake[1]: *** [CMakeFiles/pathfinding.dir/all] Error 2
gmake: *** [all] Error 2

Fixed by you. Thanks Keiron!


Update data-import-export-job.md for parallel task configuration

Adding the note on parallel import task configuration. Adding too many tasks will cause the resource capacity usage to hit 100%.

Closing this PR in the Public repo and replacing it with this PR in the private repo: https://github.com/MicrosoftDocs/Dynamics-365-Operations/pull/19052


ENH lazy load modules in the root init

#824 requires modifying __getattr__ and __dir__ on the module level (available from py3.7: https://peps.python.org/pep-0562/)
This PR makes loading modules on the root __init__ of the repo to be lazy loaded, which also gives us a nice intro to implementing our own __getattr__ and __dir__ for futher changes.
As a side effect, this makes import huggingface_hub much faster:
on main:
$ time python -c "import huggingface_hub"
python -c "import huggingface_hub"  1.98s user 0.19s system 98% cpu 2.206 total

this PR:
$ time python -c "import huggingface_hub"
python -c "import huggingface_hub"  0.04s user 0.02s system 98% cpu 0.063 total

For more info: https://scientific-python.org/specs/spec-0001/
cc @LysandreJik @osanseviero @nateraw
also closes #875

I updated as you suggested @LysandreJik , but in general I would be more in favor of not changing them since it makes it harder for us to copy new versions from upstream.
This should be ready for merge then :) I'm excited for the next steps.

I understand that changing them leads to more friction when wanting to update. Do you expect this code to evolve over time? I would prefer that all code in the codebase is formatted the same and documented the same, but I understand the pushback.

@LysandreJik the point of marking verdored code to me is to also make it clear that it's not our code, therefore it doesn't follow our standards or style, and it should not be exposed publicly.
Saying this, I now realize we're exposing this on the top level as a public function, I'll submit a PR making it private.


Fix: Reflect Updated Service Notes Immediately in Asset Details without page reload

Proposed Changes

Fixes #9225
Updated the AssetServiceEditModal component to include a refetch call for refreshing the service details data after editing notes.
Ensured that the "Service Details" section dynamically reflects the updated notes without requiring a page reload.

Before

After

@ohcnetwork/care-fe-code-reviewers
Merge Checklist

[ ] Add specs that demonstrate bug / test a new feature.
[ ] Update product documentation.
[ ] Ensure that UI text is kept in I18n files.
[ ] Prep screenshot or demo video for changelog entry, and attach it to issue.
[ ] Request for Peer Reviews
[ ] Completion of QA

Summary by CodeRabbit

New Features

Enhanced the AssetManage component to support dynamic data refreshing with a new refetch function.
Integrated refetch functionality into the AssetServiceEditModal to ensure up-to-date asset data after modifications.

Bug Fixes

Improved responsiveness of the UI by ensuring the latest asset data is available post-update.

@rithviknishad Done the changes


ScrollController should be Listenable

...so you can find out when the ScrollPosition is available or goes away.

We talked about just having a callback that gets called when one it added or removed.

Adam had a further idea, the ScrollController should subscribe to the ScrollPosition when it has just one, and forward any notifications from that, so that you can just use the controller as a proxy for the position without risking null derefs or having to subscribe/unsubscribe.

https://github.com/flutter/flutter/pull/8768


[Runtime] Add "TVM_DLL" to NDArray cache load func

The NDArrayCacheMetadata::Load function lacks the TVM_DLL attribute which leads to build failure on Windows. This PR fixes the issue.

@tvm-bot rerun

@tvm-bot rerun


Long playback stall after failed to get next segment reference

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.0.6
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Yes
Are you using the demo app or your own custom app?
Demo app
If custom app, can you reproduce the issue using our demo app?
N/A
What browser and OS are you using?
Chrome 87.0.4280.88, Windows 10
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
N/A
What are the manifest and license server URIs?

N/A
What did you do?

Start playback
What did you expect to happen?
Playback smoothly
What actually happened?

Sometimes when streaming_engine failed to get next segment reference, streaming_engine would fail to advance to next segment forever unless there was an interruption (eg. bitrate change)
The following is the log when this issue happed:
simple_abr_manager.js:279 Calling switch_(), bandwidth=4845 kbps
player.js:4829 switch_
streaming_engine.js:431 switch: switching to Stream (video:4)
streaming_engine.js:414 switch: Stream (audio:10) already active
streaming_engine.js:1104 (video:4) cannot find segment endTime: 49700.617633999995
dash_parser.js:1040 Updating manifest...
(Updating manifest... continues forever)

The error is located at getSegmentReferenceNeeded_ of streaming_engine
When mediaState.lastSegmentReference exists and mediaState.segmentIterator is null, a new segmentIterator will be created by segmentIndex.getIteratorForTime:
https://github.com/google/shaka-player/blob/master/lib/media/streaming_engine.js#L1100
In getIteratorForTime of segment_index, no index could be found unfortunately
A new SegmentIterator is created with index = -1
After that, the query of next segment iterator (https://github.com/google/shaka-player/blob/master/lib/media/streaming_engine.js#L1101)
makes currentPosition_ of SegmentIterator increment from -1 to 0 (https://github.com/google/shaka-player/blob/master/lib/media/segment_index.js#L517)
A null segment reference is returned from mediaState.segmentIterator.next().value and a warning is fired:
https://github.com/google/shaka-player/blob/master/lib/media/streaming_engine.js#L1103
In the next update, getSegmentReferenceNeeded_ is called again
This time mediaState.segmentIterator is no longer null and mediaState.segmentIterator.current() is returned. (which is null)
getSegmentReferenceNeeded_ will then always return null segment reference, unless mediaState.segmentIterator is set to null and segmentIndex.getIteratorForTime is called again
To workaround, we have inserted mediaState.segmentIterator = null after line:
https://github.com/google/shaka-player/blob/master/lib/media/streaming_engine.js#L1103
https://github.com/google/shaka-player/blob/master/lib/media/streaming_engine.js#L1135
but not sure if it is the proper fix

I believe this was fixed in v3.0.7.  Can you please try that release?

I believe this was fixed in v3.0.7.  Can you please try that release?

Tried v3.0.7 and latest master branch (v3.1.0-pre), long playback stall is still reproducible.
I have sent the manifest URI to<EMAIL_ADDRESS>

Tried v3.0.7 and latest master branch (v3.1.0-pre), long playback stall is still reproducible.
I have sent the manifest URI to<EMAIL_ADDRESS>

Hi, recently we encountered this issue in two scenario:

Switch Bitrate
When switch bitrate, mediaState.segmentIterator is created again.
The time passed to segmentIndex.getIteratorForTime equals to the last segment reference's end time.
No segment reference found and mediaState.segmentIterator position was reset to 0, resulting playback stall.

Jump to gap
There is a small gap in the buffer:

0: {start: 21485.901929, end: 21509.816596}
1: {start: 21509.937263, end: 21515.93104}

gap_jump_controller detected the gap and performed a jump:
Jumping forward 0.12066699999923003 seconds because of gap starting at 21509.816596 and ending at 21509.937263
(all): seeked: buffered seek: presentationTime=21509.937263

Unfortunately, 21509.937263 was in gap position for audio segment reference
{index: 4528, start: 21507.939263499997, end: 21509.9250413, uri: "Segment-280442222.m4a"}
{index: 4529, start: 21509.9372635, end: 21511.9425969, uri: "Segment-122222.m4a"}

No segment reference found and mediaState.segmentIterator position was reset to 0, resulting playback stall.

I think that issue was in #3191, which has been fixed in 01ce0f4b76f360db86e2a375f10af5f34509885d.  Please try again with v3.0.10.

Closing due to inactivity. If this is still an issue for you or if you have further questions, you can ask us to reopen or have the bot reopen it by including @shaka-bot reopen in a comment.

I haven't been able to reproduce, but having getIteratorForTime return an index of -1 would be invalid.

Closing as a duplicate of #3393, which has the same problem and is easier to reproduce.


stackPages view use router.back({force:true})

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Framework7 Version: 2.2.5

Framework7-Vue Version: 2.2.5

Platform and Target: mac osx chrome 66

When I put some pages in a view
<f7-view url="/" main class="ios-edges"   :stackPages="true" :preloadPreviousPage="false" :iosSwipeBack="false" ></f7-view>

page stack looks like '/' -> '/page1' -> 'page2'
when call $f7router.back({force:true}) in page2, page1 not reload. If I use $f7router.navigate('/page1', {reloadPrevious: true}), 'page1' reload but 'page2' still stacked. What should I do if just

unmount page2
navigate to page1
page1 reload

http://forum.framework7.io/t/f7-vue-2-2-5-stackpages-view-use-router-back-force-true/3614


Bug: requestUrl throws net::ERR_SSL_CLIENT_AUTH_CERT_NEEDED

Some users of ReadItLater plugin reported issues with fetching websites with same error net::ERR_SSL_CLIENT_AUTH_CERT_NEEDED. This error occurs only on desktop apps on all platforms and since it happens in Electron layer I'm unable to debug it properly.
We use requestUrl function and request is sent as basic GET.
https://github.com/DominikPieper/obsidian-ReadItLater/blob/210d016b1038783e4f44615c4b1f0e24c9a2f19f/src/parsers/WebsiteParser.ts#L33
I found only limited amount of resources about this error. Some blames the server configuration other suggests to test if certificate-error or select-client-certificate events are emitted.
Affected URLs:

https://www.thehindu.com/sci-tech/science/attophysics-new-tools-to-fathom-the-world-of-electrons-explained/article67393728.ece
https://midway-auth.amazon.com/login?next=%2F

This sounds like it's coming from Chromium within Electron, and is probably related to some weird SSL configuration on the servers, or root certs on the user's machine. Unfortunately this isn't something I can debug and I couldn't find much about it in search results either.

I'm getting the same error. Even just going to the Obsidian Developer tools console and running
await requestUrl({url: `https://api.first.org/data/v1/epss?cve=CVE-2019-0708`});

throws
Uncaught Error: net::ERR_SSL_CLIENT_AUTH_CERT_NEEDED
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:49935)
    at SimpleURLLoaderWrapper.emit (node:events:513:28)

This occurs both on my work MacBook Pro and my home MacBook Pro, which seems to indicate that it's server-side or in a default root cert.
I can run curl https://api.first.org/data/v1/epss?cve=CVE-2019-0708 successfully from a terminal which suggests that it's something not machine-wide for my machines.
Is there anything I can share that might make this easier to figure out what's going on?

requestUrl on desktop/Electron uses net.request (https://www.electronjs.org/docs/latest/api/net#netrequestoptions). Unfortunately that means this kind of errors are not something we know how to fix.
I suggest looking to see if you can use Electron Fiddle to reproduce the same issue and submit a bug report to Electron.
Will close the issue for now - but feel free to link to it and continue discussions.


Cannot run media cluster tests against casting video player using test harness

From chip-certification-tool-backend created by chrisdecenzo: CHIP-Specifications/chip-certification-tool-backend#343
The test harness does not currently work for testing a TV which is not commissionable (for a casting video player, being commissionable is optional). For the media cluster tests, the test plan states that you can use chip-tool when commissionable and tv-casting-app when not commissionable. The tv-casting-app is not currently part of the cert tool.
According to Xiaolei : the Test harness creates ChipTool docker container at runtime. But the files needed for docker container (executable and dockerfile) is committed into TH repo. So we need to create the same thing for tv-casting-app. In our case, we need to write a dockerfile that creates a docker image.
According to @kean-apple, The YAML files are used to generate c++ test code, which is then compiled into the chip-tool. So to make this work for tv-casting-app you would need to code-gen the testing code, so it can be compiled into tv-casting-app.
I am not sure what that takes.
@Vivien Nicolas
and
@Joshua Villasenor [Apple]
, are the ones I know worked on it.
The chip-tool code-gen from YAML is using zap and the project is defined here:
https://github.com/project-chip/connectedhomeip/blob/master/examples/chip-tool/templates/templates.json

Hello @chrisdecenzo, I am not sure which test plan indicates using chip-tool, but there is a tv-casting-app for linux in connectedhomeip/examples/tv-casting-app/linux and connectedhomeip_fork/examples/tv-app/linux. I was able to perform commissioning using tv-app with the tv-casting-app. Depending on which side is being tested either the casting app or the tv-app can be used.

please assign this to Xiaolei

@chrisdecenzo Could you please help us in resolving this issue? We are currently trying to scrub through pending issues/bugs and would like to move this to a closure.


Truncated tweets after API update

twitter-archiver returns truncated tweets after an API update. See https://developer.twitter.com/en/docs/tweets/tweet-updates and https://stackoverflow.com/a/40454382/912307 .
The following diff seems to fix it for twitter-archiver. I have no idea if it breaks anything else.
diff --git a/twitter/archiver.py b/twitter/archiver.py
index ef2dc1f..ae60380 100644
--- a/twitter/archiver.py
+++ b/twitter/archiver.py
@@ -190,7 +190,7 @@ def statuses_resolve_uids(twitter, tl):

 def statuses_portion(twitter, screen_name, max_id=None, mentions=False, favorites=False, received_dms=None, isoformat=False):
     """Get a portion of the statuses of a screen name."""
-    kwargs = dict(count=200, include_rts=1, screen_name=screen_name)
+    kwargs = dict(count=200, include_rts=1, screen_name=screen_name, tweet_mode='extended')
     if max_id:
         kwargs['max_id'] = max_id

@@ -217,10 +217,10 @@ def statuses_portion(twitter, screen_name, max_id=None, mentions=False, favorite
     else:
       newtl = tl
     for t in newtl:
-        text = t['text']
+        text = t['full_text']
         rt = t.get('retweeted_status')
         if rt:
-            text = "RT @%s: %s" % (rt['user']['screen_name'], rt['text'])
+            text = "RT @%s: %s" % (rt['user']['screen_name'], rt['full_text'])
         # DMs don't include mentions by default, so in order to show who
         # the recipient was, we synthesise a mention. If we're not
         # operating on DMs, behave as normal

That's the way to go, can you propose it as a Pull Request? Thx

Here's a PR: https://github.com/sixohsix/twitter/pull/371.
Any tips how to use 280 characters with streaming using from twitter.stream import TwitterStream?

@hugovk there's no extra option to add to stream api calls, but you need to collect new full text fields from the new "extended_tweet" field for each tweet. See for instance : https://github.com/medialab/gazouilloire/commit/f350380dbff71efaf9f7931eb181964e008b9f07#diff-a5580cc12ad805c63543d907a4931255

Aha, there it is, thanks!


add driver maxresult size in config

operations like topandas() sometimes fail with collect data exceeding spark.driver.maxresultsize limit (default 1g)
added this in the config to give us the flexibility to increase this if needed.

Codecov Report

Merging #77 (b5e397b) into master (8065524) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #77      +/-   ##
==========================================
+ Coverage   54.33%   54.36%   +0.03%
==========================================
  Files          21       21
  Lines        1351     1352       +1
==========================================
+ Hits          734      735       +1
  Misses        617      617

Impacted Files
Coverage Δ

data_processing/common/sparksession.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #77 (b5e397b) into master (8065524) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #77      +/-   ##
==========================================
+ Coverage   54.33%   54.36%   +0.03%
==========================================
  Files          21       21
  Lines        1351     1352       +1
==========================================
+ Hits          734      735       +1
  Misses        617      617

Impacted Files
Coverage Δ

data_processing/common/sparksession.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


[FRG] - Unable to use "Print dynamic data" to print variables

Whenever I try to use the Print dynamic data option to print a variable, I end up with an error when I try to click the Save action.

Cannot read property '_parseElement' of undefined

Inside of the _parseSection(), "print" block, it falls all the way through to
printElement._parseElement(data);

I'm assuming it's not being caught on a } else if (data.variable) {, on line 1616.
data is

type: "print"
settings: {align: 0}
variable: undefined

This is fixed in the current version.


 It caused some crashed and misbehaviors in app.
std::vector.erase will return the next iterator, and just compare it with vector.end(), and will be right.

Yep. All the iterators after the removed element becomes invalid. We should hold there return value

Sorry, you prior to the submission of pull request, we have modified the code.

@9miao but you didn't push the changes to your repo.

Yes, we are in today released the 1.0.2 version of push。


not able to find libcudnn.so.7

System information
Operating System: 20.04.4 LTS
TensorFlow version: 2.3.1
Python version: 3.7.4
GCC/Compiler: 7.3.0
CUDA: 10.1.243
cuDNN: 8.0.4
GPU model and memory: GeForce GTX 960m, 4 Gb
NVIDIA-SMI: 450.80.02

TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

2020-10-15 13:01:11.746116: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
v2.3.0-54-gfcc4b966f1 2.3.1

import tensorflow as tf

2020-10-15 12:44:04.961178: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1

tf.config.list_physical_devices("GPU")
2020-10-15 12:44:11.883542: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcuda.so.1
2020-10-15 12:44:11.915652: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-15 12:44:11.916045: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1716] Found device 0 with properties:
pciBusID: 0000:02:00.0 name: GeForce GTX 960M computeCapability: 5.0
coreClock: 1.176GHz coreCount: 5 deviceMemorySize: 3.95GiB deviceMemoryBandwidth: 74.65GiB/s
2020-10-15 12:44:11.916111: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2020-10-15 12:44:11.918107: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.10
2020-10-15 12:44:11.919968: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcufft.so.10
2020-10-15 12:44:11.920310: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcurand.so.10
2020-10-15 12:44:11.922495: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusolver.so.10
2020-10-15 12:44:11.923927: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusparse.so.10
2020-10-15 12:44:11.924102: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'libcudnn.so.7'; dlerror: libcudnn.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/lib/cuda/include:/usr/lib/cuda/lib64:/home/nitin/catkin_ws/devel/lib:/usr/lib/cuda/include:/usr/lib/cuda/lib64
2020-10-15 12:44:11.924120: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1753] Cannot dlopen some GPU libraries.
Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
[]

@nitin7999
Please, see tested build configurations from here.
Refer the issue comment, link and see if it helps you. Thanks!

ok how should i go about to change the cudnn installation alone. i guess cudnn 8.0.4 is not supported.

What to do for this?

tf.test.is_gpu_available(cuda_only=False, min_cuda_compute_capability=None)
WARNING:tensorflow:From :1: is_gpu_available (from tensorflow.python.framework.test_util) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.config.list_physical_devices('GPU') instead.
2020-10-15 22:07:08.142338: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN)to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2020-10-15 22:07:08.411314: I tensorflow/core/platform/profile_utils/cpu_utils.cc:104] CPU Frequency:<PHONE_NUMBER> Hz
2020-10-15 22:07:08.412772: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x561ebe611de0 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-10-15 22:07:08.412847: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-10-15 22:07:08.663373: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-15 22:07:08.664875: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x561ebe6a5fe0 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2020-10-15 22:07:08.664954: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): GeForce GTX 960M, Compute Capability 5.0
2020-10-15 22:07:08.683250: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-15 22:07:08.684234: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1716] Found device 0 with properties:
pciBusID: 0000:02:00.0 name: GeForce GTX 960M computeCapability: 5.0
coreClock: 1.176GHz coreCount: 5 deviceMemorySize: 3.95GiB deviceMemoryBandwidth: 74.65GiB/s
2020-10-15 22:07:08.684358: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2020-10-15 22:07:08.684445: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.10
2020-10-15 22:07:08.684507: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcufft.so.10
2020-10-15 22:07:08.684569: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcurand.so.10
2020-10-15 22:07:08.684626: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusolver.so.10
2020-10-15 22:07:08.684702: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusparse.so.10
2020-10-15 22:07:08.684780: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudnn.so.7
2020-10-15 22:07:08.685009: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-15 22:07:08.685986: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-10-15 22:07:08.686827: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1858] Adding visible gpu devices: 0
2020-10-15 22:07:08.700697: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
Traceback (most recent call last):
File "", line 1, in
File "/home/nitin/anaconda3/lib/python3.7/site-packages/tensorflow/python/util/deprecation.py", line 324, in new_func
return func(*args, **kwargs)
File "/home/nitin/anaconda3/lib/python3.7/site-packages/tensorflow/python/framework/test_util.py", line 1563, in is_gpu_available
for local_device in device_lib.list_local_devices():
File "/home/nitin/anaconda3/lib/python3.7/site-packages/tensorflow/python/client/device_lib.py", line 43, in list_local_devices
_convert(s) for s in _pywrap_device_lib.list_devices(serialized_config)
RuntimeError: CUDA runtime implicit initialization on GPU:0 failed. Status: device kernel image is invalid

@nitin7999
cuDNN 8 is not supported. Please try installing cuDNN 7.6 and check if you are facing the same issue?
Thanks!

that is the resuilt shown after installing cuDNN 7.6

@nitin7999 Apologies for the delay in response. I see you are using GeForce GTX 960M which has 5.0 cuda compute capability.
See https://developer.nvidia.com/cuda-gpus
As of now we have TensorFlow pip pre built packages that support CUDA® architectures 3.5, 3.7, 5.2, 6.0, 6.1, 7.0 and higher than 7.0
Unfortunately your gpu is not among the supported pip packages.
See https://www.tensorflow.org/install/gpu#hardware_requirements
Solution here will be to build a pip package from source that supports your gpu architecture.
Thanks!


Crash in     @objc public func registerDeviceToken(_ deviceToken: Data, completion: @escaping () -> Void = {}) {

What?
App crashed:
Thread 9: EXC_BREAKPOINT (code=1, subcode=0x103e0fdf0)
Method: registerDeviceToken
Line: strongSelf.preIISOperationQueue.resume()
Xcode was running a build on a device and this happened during startup, twice now.
Environment

PusherChatkit version: 1.3.0
**Xcode version:**Version 10.1 (10B61)
Swift version: 4.2.1
**Platform(s) running PusherChatkit:**iOS

Demo Project (if you have one; it helps a lot!)

CC @hamchapman

I also face this issue

chatkit is flake (er) in debug fyi

Since this relates to an older version of the SDK and because we haven't heard anything further in some time I am going to close this issue. Please re-open with more details if this is still an issue on the latest version.
Dedicated support is always available at https://support.pusher.com and<EMAIL_ADDRESS>


fix pressure plate tracking

#216

Fixed pressure plate tracking, door opening. But open doors are still causing some pathfinding issues it seems.
{t:90}


"No suitable workers for model instance" after click "deploy model".

Describe the bug

After starting gpustack, it seems  gpustack did not recognize my gpu, my gpu is nvidia 4090, see environment part below (nvidia-driver and cuda were installed).

when deploy model,  log says "No suitable workers for model instance".

2024-08-07T11:40:25+08:00 - gpustack.scheduler.scheduler - DEBUG - Scheduling model instance llama3.1-71sW4
2024-08-07T11:40:25+08:00 - gpustack.scheduler.calculator - INFO - Calculated resource claim for model instance phi3-S5H6t, least: memoryEstimate(offloadLayers=0, uma=memoryResource(ram=3261403296, vram=0), nonUMA=memoryResource(ram=3418689696, vram=414916096)), most: memoryEstimate(offloadLayers=33, uma=memoryResource(ram=40177824, vram=3221225472), nonUMA=memoryResource(ram=197464224, vram=5547908992))
2024-08-07T11:40:25+08:00 - gpustack.scheduler.policy - DEBUG - Worker localhost.localdomain reserved memory:<PHONE_NUMBER>, reserved gpu memory:<PHONE_NUMBER>, allocatable memory:<PHONE_NUMBER>936, allocatable gpu memory: {0: -1073741824}
2024-08-07T11:40:25+08:00 - gpustack.scheduler.scheduler - DEBUG - No suitable workers for model instance llama3.1-71sW4

Steps to reproduce

Click  'deploy model'
Add llama 3.1 model from ollama library

Result

The  state of the "deploy model" is always pending.
logs:

2024-08-07T11:40:25+08:00 - gpustack.scheduler.scheduler - DEBUG - Scheduling model instance llama3.1-71sW4
2024-08-07T11:40:25+08:00 - gpustack.scheduler.calculator - INFO - Calculated resource claim for model instance phi3-S5H6t, least: memoryEstimate(offloadLayers=0, uma=memoryResource(ram=3261403296, vram=0), nonUMA=memoryResource(ram=3418689696, vram=414916096)), most: memoryEstimate(offloadLayers=33, uma=memoryResource(ram=40177824, vram=3221225472), nonUMA=memoryResource(ram=197464224, vram=5547908992))
2024-08-07T11:40:25+08:00 - gpustack.scheduler.policy - DEBUG - Worker localhost.localdomain reserved memory:<PHONE_NUMBER>, reserved gpu memory:<PHONE_NUMBER>, allocatable memory:<PHONE_NUMBER>936, allocatable gpu memory: {0: -1073741824}
2024-08-07T11:40:25+08:00 - gpustack.scheduler.scheduler - DEBUG - No suitable workers for model instance llama3.1-71sW4

Expected behavior

model being downloaded

Environment

GPUStack version: 0.1.0 (908a6c7)

OS

cat /etc/os-release
NAME="Rocky Linux"
VERSION="9.3 (Blue Onyx)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.3"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Rocky Linux 9.3 (Blue Onyx)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:9::baseos"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2032-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-9"
ROCKY_SUPPORT_PRODUCT_VERSION="9.3"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.3"

GPU:

nvidia-smi
Wed Aug  7 11:44:07 2024
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.104.05             Driver Version: 535.104.05   CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce RTX 4090        Off | 00000000:01:00.0 Off |                  Off |
| 47%   40C    P0              72W / 450W |      2MiB / 24564MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
|   1  NVIDIA GeForce RTX 4090        Off | 00000000:24:00.0 Off |                  Off |
| 47%   39C    P0              66W / 450W |      2MiB / 24564MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
|   2  NVIDIA GeForce RTX 4090        Off | 00000000:41:00.0 Off |                  Off |
| 47%   40C    P0              74W / 450W |      2MiB / 24564MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
|   3  NVIDIA GeForce RTX 4090        Off | 00000000:61:00.0 Off |                  Off |
| 47%   41C    P0              73W / 450W |      2MiB / 24564MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
|   4  NVIDIA GeForce RTX 4090        Off | 00000000:81:00.0 Off |                  Off |
| 46%   40C    P0              72W / 450W |      2MiB / 24564MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
|   5  NVIDIA GeForce RTX 4090        Off | 00000000:A1:00.0 Off |                  Off |
| 42%   40C    P0              65W / 450W |      2MiB / 24564MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
|   6  NVIDIA GeForce RTX 4090        Off | 00000000:C1:00.0 Off |                  Off |
| 37%   41C    P0              72W / 450W |      2MiB / 24564MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
|   7  NVIDIA GeForce RTX 4090        Off | 00000000:E1:00.0 Off |                  Off |
| 33%   38C    P0              60W / 450W |      2MiB / 24564MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|  No running processes found                                                           |
+---------------------------------------------------------------------------------------+

/usr/local/cuda-12.2/bin/nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Tue_Aug_15_22:02:13_PDT_2023
Cuda compilation tools, release 12.2, V12.2.140
Build cuda_12.2.r12.2/compiler.33191640_0

Additional context
Add any other context about the problem here.

Hi.
Could you please help confirm if your environment involves the use of remote desktop or virtual machines? This information is important because it can impact how the GPU is detected and utilized.
The use of remote desktop tools or virtual machines can affect GPU detection for several reasons. In virtual environments, the GPU might be virtualized or not fully exposed to the operating system. Additionally, remote desktop protocols like RDP may use virtual graphics adapters instead of the physical GPU, leading to potential discrepancies in how the GPU is detected and used.
Could you provide the result of the detected PCI device lspci -vvv -k -xxxx -b -D -PP -nn. Understanding your environment helps us address any potential issues more effectively. Thank you.

Hi. Could you please help confirm if your environment involves the use of remote desktop or virtual machines? This information is important because it can impact how the GPU is detected and utilized.
The use of remote desktop tools or virtual machines can affect GPU detection for several reasons. In virtual environments, the GPU might be virtualized or not fully exposed to the operating system. Additionally, remote desktop protocols like RDP may use virtual graphics adapters instead of the physical GPU, leading to potential discrepancies in how the GPU is detected and used.
Could you provide the result of the detected PCI device lspci -vvv -k -xxxx -b -D -PP -nn. Understanding your environment helps us address any potential issues more effectively. Thank you.

Based on your information, we have attempted to simulate your environment. However, we were unable to reproduce the issue due to the challenges of precisely replicating your specific environment. To assist in troubleshooting, we have developed a preliminary script for the Linux x86 architecture to help check for problems during the GPU detection. Please run the following command:
sudo ./detect_gpus.sh >> detect_gpus.log

After running the command, check if the detect_gpus.log contains any "Found GPU" logs and whether the GPU part in fastfetch_output.log can detect the GPU correctly. Please upload the detect_gpus.log, fastfetch_output.log, and /var/log/gpustack.log to the issue so that we can jointly review if our GPU detection has overlooked any scenarios relevant to your environment.
detect_gpus.sh.zip

Hi, we had fixed a similar issue in GPUStack 0.2.x https://github.com/gpustack/gpustack/issues/212, which is because nvidia_drm kernel mode is not loaded. Could you try 0.2.x in your environment to see if it can resolve the problem or not? Thanks.


feat: add environment options (DTAP)

Added ability to generate common environments architecture for deploy.
D development : environment.ts (already by default)
T testing: environment.testing.ts (script generated)
A acceptance: environment.acceptance.ts (script generated)
P production: environment.prod.ts (already by default)
We can choose via script prompt if add or not those environments (default to ### NO)

Cordially
Fabio

Thanks @fabiomartino for this propsition!
Though I'm not sure this is something we want to push in the main generator, as this is something that gets very different depending of the team/project from my own experience. Sometimes you only want an additional staging environment, sometimes the environment have different names, sometines DTAP is completely disregarded as an outdated approach.
That said, I'm not necessarily against merging this, but I would love what other folks thinks about this? @creal73 @captaincaius  @bursauxa any opinions?
Also if we're going to merge this, I think we should later group this question with other "architecture" related questions like lazy-loading & PWA to reduce the total number of prompts.

I do agree with you @sinedied.
What about creating it as an addon instead ?

I had already to do that in another project, because when you work, for example with firebase/ firebase-functions, you need at least 3 environments.
environment.ts -> local firebase emulator (development)
environment.qa.ts -> firebase config to test the entire app in the cloud.(QA)
environment.prod.ts -> firebase config production. (Prod)

local

QA

Prod

This would solve a major pain point for us as our release cycle has the DTAP setup. Currently, our build script that modifies the environment.ts file before deployment to each environment. This would remove the need for that work around.

@ToFab you can always add as many environments as you need in a project, there's no need for such a script: https://angular.io/guide/build#configuring-application-environments
To be clear, this PR would do this by default for new project, but you always had the option to add more environments after the project is generated.


Generate grafana crd documentation

Adding explanation to the grafana CRDs to make the operator usage clearer.
I also update the make api-docs command to point on the more detailed CRD definition.
This definition enables our online documentation to become more detailed.
Sadly these docs won't be shown in the k8s api, due to how big the grafana crd is due to all the default resources.
So for example
k explain grafana.spec.config
KIND:     Grafana
VERSION:  grafana.integreatly.org/v1beta1

DESCRIPTION:
     <empty>

Will keep on looking like this even after my change.

I need to come up with a way to tell whitespace checker to ignore specific generated files. Else I will remove it.


Reference links are lost between dollar signs

This is an issue with the following markdown:
$ [foo][] $

[foo]: http://example.org

Note that $ is not an active character in standard Markdown, although it may be used by extensions. The document above is valid Markdown and [foo][] is interpreted as a link (as in this gist or the CommonMark dingus), but markdownlint produces this error:
MD053/link-image-reference-definitions Link and image reference definitions should be needed [Unused link or image reference definition: "foo"] [Context: "[foo]: http://example.org"]

As a workaround, you can add a \ before the first $.

While wrapping text with dollar signs like you show is not part of the CommonMark specification, it is commonly used in Markdown to provide math/equation support. Commonly enough, in fact, that issues get filed against this project when people expect math behavior and don't get it. Therefore, math syntax is enabled by default for parts of the pipeline. As you note, math syntax does not apply if the leading dollar sign is escaped and that is what I would recommend if you find yourself needing to use the syntax above.
https://github.com/micromark/micromark-extension-math

I think it's highly unexpected behavior to diverge from the specification and the actual behavior of GitHub here. But regardless, it would be valuable to be able to control which non-standard extensions this parser assumed to exist through the configuration file.

I get where you are coming from, but GitHub does actually support math syntax by default. Here is their documentation: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions
So far I have had double digit number of requests to add support for math and a couple of other common-ish extensions whereas this issue may be the first one asking to remove such support. Given how easy it is to escape one's way out of this problem, I am inclined not to make it configurable just yet.
I could do a better job documenting which extensions are enabled, though things are in a bit of flux at the moment while I am busy migrating parsers in the background.

Github does not use $ as delimiter but $` and `$

Quoting the GitHub documentation I linked to:

You can either surround the expression with dollar symbols ($), or start the expression with $[backtick] and end it with [backtick]$.

You can also verify this experimentally.

When using $ as delimiters, Github still requires the start and end delimiters to be on the same line. They won't consider them delimiters when there is a LF between them, while your linter does. and it also requires that the start delimiter is not followed by spaces (the end delimiter can be preceded by spaces).

Because there is no standard here, implementations may vary. I have generally found the micromark implementation (as used here) to be representative of real-world use and consistent with the specification when available. If you'd like to open a micromark issue for any behaviors you disagree with, I've found that team to be very responsive to input.
For the purpose of this issue, I think the underlying topic is whether it's reasonable for markdownlint to recognize math syntax by default and whether it's necessary to provide a way to opt out of that. I've stated my current position above and remain open to feedback.


Set order for default (debug) welcomeView content

The debug welcome view registers some default content to be shown:
https://github.com/microsoft/vscode/blob/277ffee01fdcf7fbb235ecfb40798bc3fd2fc128/src/vs/workbench/contrib/debug/browser/welcomeView.ts#L108
Most of these pieces of contents do not set an order, meaning they will be shown in the order they are defined.
There is also an API to specify new pieces of content from within an extension: https://code.visualstudio.com/api/references/contribution-points#contributes.viewsWelcome
Which allows you to provide order by passing it in with the group string, separated by an @:
https://github.com/microsoft/vscode/blob/277ffee01fdcf7fbb235ecfb40798bc3fd2fc128/src/vs/workbench/contrib/welcomeViews/common/viewsWelcomeContribution.ts#L69-L88
We at Google would like to be able to add a new button ("Attach and Debug") below "Run and Debug", but currently we cannot because "Run and Debug" and all others do not set order, they are all assumed to have order=5, meaning we can only place a new button before all others, or after all.
I am proposing to set order for each registered content, allowing extensions to defined where their custom content should be placed.
Thank you for your time.

I will send a PR setting it only for the one button we need right now, as that is the smaller change that may be easier to merge.
If there is interest, it might be worthwhile to instead of defaulting to 5, defaulting to the registration order. That would then automatically ensure extensions can insert where they see fit on all welcome views, without having to remember to always pass order.

Adding @connor4312 for input on the debug UI

I think the order we added is fine, but I don't think there is a general need for other extensions to insert content at any given spot. I'm going to leave the rest without an order.


Implement client-side ability to chose between multiple contracts in the contract json interface

Monitor now receives a 5th argument: contract name; facilities for receiving the contract name manually (from json interface list contracts and make the user chose one);
Approximately, line 100 when monitor function is used at: server/index.js

No longer applicable to the current architecture.


Enhancing User Experience: Adding Enter Key Functionality to the Search Bar of Food Recipe

Hey @Sulagna-Dutta-Roy
This feature enables users to press the Enter key after typing in the search bar to initiate their search, enhancing the efficiency and convenience of the search process. By implementing this functionality, users can seamlessly navigate application, improving overall usability and user satisfaction.
Is your feature request related to a problem? Please describe.
Currently, users are unable to use the Enter key to submit their search query in the search bar, which can be inconvenient and frustrating. Adding this functionality would improve the user experience by providing a more intuitive and efficient way to search.
Describe the solution you'd like
The solution involves adding JavaScript code to listen for the Enter key press event in the search bar. When the Enter key is pressed, the code should trigger the search functionality, similar to clicking the search button. This will allow users to press Enter to submit their search query, improving the usability of the search bar.
Additional context
Before adding the functionality:
https://github.com/Sulagna-Dutta-Roy/GGExtensions/assets/159511364/a58ca577-3f07-45ce-a08e-100a6e4d4275
After adding the functionality:
https://github.com/Sulagna-Dutta-Roy/GGExtensions/assets/159511364/c2185136-54ad-495a-9acd-bf805eba76d8
Please add the gssoc labels and I would like to work on it under GSSOC'24. Thank you!!

I see that food recipe is available on youtube.
Can you please check this: https://youtu.be/opikz5x_1ak?si=bG76t3z5wvxe2Qsh
Copy pasting from online resources is not acceptable as per the guidelines.

@Sulagna-Dutta-Roy , It was not created by me and I  created the issue to enable the enter button like when the user press enter button also the items will be appear rather than just using search button

Thanks for clearing this. Assigning it

@Sulagna-Dutta-Roy , Thank you for assigning and I didn't know that it is already existed in YouTube and when I saw that application in the project, I thought of adding that functionality. That's it.


🐛 [firebase_core] A compilation issue that started in xcode 13 beta

Bug report
Describe the bug
A compilation issue that started in xcode 13 beta, see below.
Steps to reproduce
Steps to reproduce the behavior:

Compile firebase_core using xcode 13 beta.
You get the compile error for FLTFirebaseCorePlugin.h 'TARGET_OS_OSX' is not defined, evaluates to 0

Expected behavior
To compile without an issue
Sample project
I don't have one I can share.

Additional context
A simple solution will be to add #import <Foundation/Foundation.h>to FLTFirebaseCorePlugin.m

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
PASTE OUTPUT INSIDE HERE

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
PASTE OUTPUT INSIDE HERE

Hey @assaf000, thanks for raising the issue. I'm currently using Xcode 13.2.1, & I have not encountered this compilation error.


bump github.com/containers/{storage,buildah}

Bump github.com/containers/storage to 4822c60538402940cb8044c96659a46ffbab3bd1, between v1.15.2 and v1.15.3, to pick up a fix for a race in the library.
Bump github.com/containers/buildah to 8d6869bccee02f73f0e26e739c9f8712578b3f32, modifying how we unmount the container's rootfs when using chroot isolation so that we just detach the whole thing rather than trying to detach each submount in order, which isn't necessary.
This is https://bugzilla.redhat.com/show_bug.cgi?id=1772179, but for 4.4/master.

This will obsolete #113.

/retitle Bug 1772179: bump github.com/containers/{storage,buildah}


google analytics

It doesn't like cloudflare is catching everything.
UA-75597006-1

resolved by PR #34


Create a strong_type module

This is a place holder for creating a module from the strong_type source.
Some initial thoughts
This should probably be done following the same model as the MSVC standard library. This is on the grounds that if it works for that it will probably work for strong_type.

The intent would be to allow users to consume either a module as in import strong_type; or to continue using headers.
Existing header users should not be affected in any way, so no exiting code should fail to compile etc...
Ideally it should be orthogonal if users choose to use import std; when they include strong type headers.
Ideally vcpkg, and similar, users should be able to consume the module, there should be an example of how to do this

The main change in the source code is to optionally add the export keyword to all entities that should be exported. This is optional because include users still have to work. This can be done via a a macro like STRONG_TYPE_MODULE_EXPORT that evalutes to export or by default empty.  The MSVC standard library uses _EXPORT_STD  for this.
The module can be built using import std; however the module should use just import std; not export import std;. This allows users to use the strong_type module but still carry on using #include <meow> for the standard library.
I would suggest that an initial PR is created that just adds the  STRONG_TYPE_MODULE_EXPORT macro to the large number of places it is needed and does nothing else. This is because this is by far the bulk of the changes and doing them in a separate PR makes it easier to review but is pretty low risk as the default value of  STRONG_TYPE_MODULE_EXPORT is empty.
Note an alternative to adding export to every exported entity would be  export namespace strong_type { ... } or export namspace { }.
However these tend to make code brittle to future change as people move code around and can accidentally export stuff that isn't meant to be or visa versa.

Oh this does raise the question of code format
STRONG_TYPE_MODULE_EXPORT
template <typename T>
struct Foo {
}

or
STRONG_TYPE_MODULE_EXPORT template <typename T>
struct Foo {
}

The former is maybe easier to review, the later is one less line. I'm happy with whatever you want.
BTW I noticed code like
template <typename D>
template <typename T, typename Tag, typename ... M>
class affine_point<D>::modifier<::strong::type<T, Tag, M...>>
{

I have never seen that before is it the same as
template <typename D, typename T, typename Tag, typename ... M>

Also what does the following do?
template<typename M, typename T>
using modifier = typename M::template modifier<T>;

Got sick at the conference. Bleah....
On code formatting, I have over the years come to prefer easily "diffable" formats, so a format that makes a change local to one line is preferable to one that spreads over several. It's a judgement call, though, as you really don't want the extreme of one syntactic element per line. I used to vaguely prefer this, but then I briefly worked for a company whose coding style made it a challenge to understand what even the smallest change actually changed.
The one in the middle. I wish they were the same, but the language disagrees. https://godbolt.org/z/KGE7W9jaK
For the last one, as far as I remember, that is a work around a compiler bug.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1495

Questions ?
Please refer to the Backport tool documentation


第 1 章：简介 翻译存在的问题

英文原文章节

1.3.1. A Brief History of FreeBSD
386BSD was Bill Jolitz’s operating system, which had been up to that point suffering rather severely from almost a year’s worth of neglect. As the patchkit swelled ever more uncomfortably with each passing day, they decided to assist Bill by providing this interim "cleanup" snapshot. Those plans came to a rude halt when Bill Jolitz suddenly decided to withdraw his sanction from the project without any clear indication of what would be done instead.

Deepl 机器翻译章节结果或现有章节内容

386BSD是Bill Jolitz的操作系统，到那时为止，它已经被忽视了一年之久，受到了相当严重的影响。随着补丁包一天天地膨胀，他们决定通过提供这个临时的 "清理 "快照来帮助比尔。当比尔-乔利茨突然决定从该项目中撤回他的批准时，这些计划戛然而止，而没有任何明确的迹象表明会做什么。

存在哪些问题？

撤回他的批准时   是什么意思？

英文原文章节

1.3.1. A Brief History of FreeBSD
Around this time, some rather unexpected storm clouds formed on the horizon as Novell and U.C. Berkeley settled their long-running lawsuit over the legal status of the Berkeley Net/2 tape. A condition of that settlement was U.C. Berkeley’s concession that large parts of Net/2 were "encumbered" code and the property of Novell, who had in turn acquired it from AT&T some time previously. What Berkeley got in return was Novell’s "blessing" that the 4.4BSD-Lite release, when it was finally released, would be declared unencumbered and all existing Net/2 users would be strongly encouraged to switch. This included FreeBSD, and the project was given until the end of July 1994 to stop shipping its own Net/2 based product. Under the terms of that agreement, the project was allowed one last release before the deadline, that release being FreeBSD <IP_ADDRESS>.

Deepl 机器翻译章节结果或现有章节内容

大约在这个时候，由于Novell和U.C. Berkeley就Berkeley Net/2磁带的法律地位解决了他们长期以来的诉讼，一些相当意外的风暴云在地平线上形成。和解的一个条件是U.C. Berkeley让步，即Net/2的大部分是 "担保 "代码，是Novell的财产，而Novell又在一段时间前从AT&T那里收购了它。Berkeley得到的回报是Novell的 "祝福"，当4.4BSD-Lite版本最终发布时，将被宣布为无担保代码，并强烈鼓励所有现有的Net/2用户转换。这包括FreeBSD，该项目被给予在1994年7月底之前停止运送它自己的基于Net/2的产品。根据协议的条款，该项目被允许在最后期限前发布最后一个版本，这个版本就是 FreeBSD <IP_ADDRESS>。

存在哪些问题？

encumbered blessing 担保 与 祝福？

1.3.3. FreeBSD 的开发模式
The committers are the people who have push access to the Git repository, and are authorized to make modifications to the FreeBSD source (the term "committer" comes from commit, the source control command which is used to bring new changes into the repository). Anyone can submit a bug to the Bug Database. Before submitting a bug report, the FreeBSD mailing lists, IRC channels, or forums can be used to help verify that an issue is actually a bug.

committer 如何翻译？
提交者？委员？不翻译？


[BACKLOG-10097]Default data services connections to the Pentaho Server

http://jira.pentaho.com/browse/BACKLOG-10097

See also: https://github.com/pentaho/pdi-dataservice-plugin/pull/75

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f dbdialog/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f dbdialog/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  dbdialog/src/org/pentaho/ui/database/event/DataHandler.java

Newly Broken Tests:
org.pentaho.ui.database.event.DataHandlerTest.testPushPopCache:
:red_circle: org.mockito.exceptions.verification.junit.ArgumentsAreDifferent
Argument(s) are different! Wanted:
xulTextbox.setValue("pentaho-di");
-> at org.pentaho.ui.database.event.DataHandlerTest.testPushPopCache(DataHandlerTest.java:258)
Actual invocation has different arguments:
xulTextbox.setValue("pentaho");
-> at org.pentaho.ui.database.event.DataHandler.setConnectionSpecificInfo(DataHandler.java:1371)

	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.pentaho.ui.database.event.DataHandlerTest.testPushPopCache(DataHandlerTest.java:258)

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f dbdialog/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f dbdialog/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  dbdialog/src/org/pentaho/ui/database/event/DataHandler.java
  dbdialog/test-src/org/pentaho/ui/database/event/DataHandlerTest.java


Enabling colors in CLI (Golang)

Closes #349.
Implemented in a pair-programming session together with @maschleg :)

:+1:


Fix a collectionView.selectItem crash

@mikaoj
I faced a crash at follows. ( Xcode15)
collectionView.selectItem(at: indexPath, animated: false, scrollPosition: [])

https://github.com/mikaoj/BSImagePicker/blob/master/Sources/Scene/Assets/AssetsViewController.swift#L115C13-L115C90
The error I faced is as follows.
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Attempted to modify the selection of an out-of-bounds item (2) when there are only 0 items in section 0. Collection view:

I fixed this issue by adding guard.
Thank you for maintaining the very useful package!

Thank you for maintaining the very useful package!

I haven't done very much maintenance for a long time now.
But thanks for contributing! :)