[tracking] streams

With #125 out, it's probably worth looking at which other parts of std::iter we can port to async_std::stream. This issue is intended to track what's left for us to port.
Missing free functions

[ ] from_fn
[ ] repeat_with
[ ] successors

Missing traits

[x]  DoubleEndedStream
[ ] ExactSizeStream
[x] Extend
[ ] FusedStream
[ ] Product
[ ] Sum

Missing stream methods

[x] Stream::all
[x] Stream::any
[ ] Stream::by_ref
[x] Stream::chain
[ ] Stream::cloned
[ ] Stream::cmp
[x] Stream::collect
[ ] Stream::copied
[ ] Stream::count
[ ] Stream::cycle
[x] Stream::enumerate
[ ] Stream::eq
[x] Stream::filter
[x] Stream::filter_map
[x] Stream::find
[x] Stream::find_map
[ ] Stream::flat_map
[ ] Stream::flatten
[ ] Stream::fold
[ ] Stream::for_each
[x] Stream::fuse
[ ] Stream::ge
[ ] Stream::gt
[x] Stream::inspect
[ ] Stream::last
[ ] Stream::le
[ ] Stream::lt
[x] Stream::map
[ ] Stream::max
[ ] Stream::max_by
[ ] Stream::max_by_key
[ ] Stream::min
[x] Stream::min_by
[ ] Stream::min_by_key
[ ] Stream::ne
[x] Stream::nth
[ ] Stream::partial_cmp
[ ] Stream::partition
[ ] Stream::peekable
[ ] Stream::position
[ ] Stream::product
[ ] Stream::rev
[ ] Stream::rposition
[x] Stream::scan
[ ] Stream::size_hint
[x] Stream::skip
[x] Stream::skip_while
[x] Stream::step_by
[ ] Stream::sum
[x] Stream::take
[ ] Stream::take_while
[ ] Stream::try_fold
[x] Stream::try_for_each
[ ] Stream::unzip
[x] Stream::zip

Missing IntoStream impls
Currently not possible. See https://github.com/async-rs/async-std/issues/129#issuecomment-533093186
Missing FromStream impls

[x] FromStream<()> for ()
[x] FromStream<char> for String
[x] FromStream<String> for String
[x] FromStream<&'a char> for String
[x] FromStream<&'a str> for String
[x] FromStream<T> for Cow<'a, [T]> where T: Clone
[x] FromStream for Box<[A]>
[x] FromStream for VecDeque
[x] FromStream<Result> for Result<V, E> where V: FromStream
[x] FromStream<Option> for Option<V> where V: FromStream
[x] FromStream<(K, V)> for BTreeMap<K, V> where K: Ord
[x] FromStream<(K, V)> for HashMap<K, V, S> where K: Eq + Hash, S: BuildHasher + Default
[x] FromStream<T> for BinaryHeap<T> where T: Ord
[x] FromStream<T> for BTreeSet<T> where T: Ord
[x] FromStream<T> for LinkedList<T>
[x] FromStream<T> for Vec<T>
[x] FromStream<T> for HashSet<T, S> where T: Eq + Hash, S: BuildHasher + Default

DoubleEndedStream

[x] DoubleEndedStream::poll_next_back
[ ] DoubleEndedStream::next_back
[ ] DoubleEndedStream::nth_back
[ ] DoubleEndedStream::rfind
[ ] DoubleEndedStream::rfold
[ ] DoubleEndedStream::try_rfold

I've documented some things out here:
https://paper.dropbox.com/doc/async-flow--AjJPPnPNL6eLfTQ3FT3Qew3zAQ-qCeBTk0Z0Nk92kn1ifNbQ
It was open for comments.

I would like to port map, filter and fold :). I like this function in std.
I'm never seriously  did any async with rust before. @vertexclique the link you posted is an example we should follow to implement all this functions ?

I would like to port map, filter and fold :). I like this function in std.
I'm never seriously  did any async with rust before. @vertexclique the link you posted is an example we should follow to implement all this functions ?

I started with simple methods like any and all here at #132
@sepiropht you may take a look at my pr, and the stream::take() method too.
simply create your struct Map and implement futures::Stream for it, by polling the inner stream and apply the provided function for every item to the stream.

Ok thanks @shekohex. I will try that

@sepiropht from my point of view better to concentrate on FromStream and IntoIter ones are important. Other than that, I suggest following the list of Yoshua for method impls.

Note that some features on this list are not useful until asynchronous closure is improved.

@yoshuawuyts
btw, the following items are unstable.
https://doc.rust-lang.org/nightly/core/iter/trait.Iterator.html#method.is_sorted

[ ]  Stream::is_sorted
[ ]  Stream::is_sorted_by
[ ]  Stream::is_sorted_by_key

https://doc.rust-lang.org/nightly/core/iter/fn.once_with.html

[ ]  once_with

@taiki-e thanks, I've updated the issue!

Do you need someone to add the remaining FromStream impls? I had a lot of fun doing #207 and would love to contribute more.

@sunjay Go for it :) And thank you!!

IntoStream impls for std::collections types (and comparable) aren't possible in async-std because our Stream impl builds on top of futures-rs's stream impl. We discovered this in https://github.com/async-rs/async-std/pull/213.
Conversations about possibly adding a IntoStream type to futures-core are happening in https://github.com/rust-lang-nursery/futures-rs/issues/1879, though we may need to open a dedicated issue for this.
As of now I'm going to go ahead and strike out the missing IntoStream impls for the collection types because they aren't possible. Though my hope is that we can move the IntoStream trait to be part of futures-core eventually.

Do you need someone to add the remaining FromStream impls? I had a lot of fun doing #207 and would love to contribute more.

Small update on this: I started to work on it on the weekend and noticed that I need a few more things to be implemented before finishing it off. In particular, it looks like a lot of the FromStream implementations use the Extend trait. That exists, so I started to work on adding it for a few cases where I needed it (e.g. for String and other collections).
I could also use a few more combinators on Stream/StreamExt. In particular: size_hint, for_each, cloned/copied were all needed for a few of the impls.
I can work around some of these using fold, but it would be nice if the implementations could match std as much as possible.
P.S. Can I ask why the Stream trait was split into Stream and StreamExt? Was it just to avoid the way that Iterator is a huge trait? I personally found it a little confusing that I had to look at something separate like that. Also hiding it in prelude doesn't really help with that. Would love to know your thoughts on this. :)

I opened #265 for the impls that should be easy to merge. I also opened #266 to discuss the changes to the Extend trait that I found were necessary for some of my impls. Once these two changes land and we get #264 (thanks @montekki!) I should be able to continue with FromStream. :smile:

Still working on this. #266 is ready for review.
By the way, looks like pretty much every single FromIterator implementation in the standard library uses the Extend trait, so I guess I'm adding that too! Woo code reuse! :smile:
(Also, the standard library is really inconsistent with its use of size_hint to optimize allocations in case anyone is looking for an easy PR to std.)

The next three methods that would be really nice to have are: size_hint, cloned, and copied. :smile:

And we're done! :tada:
You should merge #266 before you merge #271. All the impls for FromStream can be checked off once those are merged. :tada:

Woohoo! All of FromStream can be checked off now. 🎉🎉🎉

@sunjay I was thinking of what we could do next for FromStream; and perhaps we could polish our  module-level documentation? std::iter::FromIterator seems like it could probably be ported for the most part!
Is that something that you might be interested in doing?

That sounds great! I don't know when I'll next have time to work on this, so someone else is welcome to take my place and help out. 😊

@sunjay I'll file an issue for this then so someone can pick this up! :blush:

fyi, I start working on take_while

I will take a look at peekable next. Hope there is no blocker.

Btw. It looks like fold and for_each are already implemented, but not ticked off in the list above.

I would like to try the min-max-family.

If they're not claimed yet, I'd like to do Stream::sum() and Stream::product().

@ktomsic It's all yours, go ahead :)

The Stream::rposition maybe need DoubleEndStream?
I see std's signature
fn rposition
(&mut self, predicate: P) -> Option<usize>
where
    P: FnMut(Self::Item) -> bool,
    Self: Sized + ExactSizeIterator + DoubleEndedIterator,

So are the rev

I've started to play with the Double ended iterators

@yoshuawuyts I think we can cross of a bunch of things here, unless it only considers stable features?


@celo/wallet-ledger signTypedData is currently broken (and has been for a very long time) unnoticed

I discovered today that one of the functions we implement the signer interface in ledger-signer (signer.signTypedData) relies on ledger.signEIP712HashedMessage that is NOT implemented as of 5.11.x which is the version currently in use in our sdks
### Tasks
- [x] update ledger package
- [x] change the mocks to reflect the true implementation
- [ ] fix all broken tests
- [ ] profit

status update: tests are failing on an obscure line written 4 years ago, investigating

Seems this is undoable according to bloo since it wasn't in their scope for 1.2.0 The work is done on the TS side but can't be used yet.


error when loading evc from file with RuntimeWidget

When loading an evc file with RuntimeWidget, I got the following error:
dart_eval runtime exception: type '$InstanceImpl' is not a subtype of type 'BridgeSuperShim' in type cast
dart_eval verion: dart_eval: ^0.6.0
The error was reported from line 72 of bridge.dart file (in dart_eval package):
  @override
  void run(Runtime runtime) {
    final shim = runtime.frame[_shimOffset] as BridgeSuperShim; // <===== line 72 that causes the error
    shim.bridge = runtime.frame[_bridgeOffset] as $Bridge;
  }

Hi, this is not enough info to reproduce. Can you please try to narrow down to what code is causing this issue. An issue like this can also be caused by specifying the wrong number of arguments in the args array.

You are right, it is because of the arguments passing to runtime.executeLib(). After debugging the code, I found that in the EvalWidget the widget.args has one element (null element) but the RuntimeWidget has no element, so I modify the code of RuntimeWidget, line 333, from:
final result = runtime!.executeLib(widget.library, widget.function, widget.args);
to:
final result = runtime!.executeLib(widget.library, widget.function, [null]);
the original error that I reported is gone. However I found another issue that loading from Evc file does not load the body of the Scaffold while loading from code with EvalWidget does.
The code of the app that I use dart_eval compile is as below:
import 'package:flutter/material.dart';
class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  static const String _title = 'Sample App';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: Scaffold(
        appBar: AppBar(title: Text(_title)),
        body: MyStatefulWidget(),
      ),
    );
  }
}

class MyStatefulWidget extends StatefulWidget {
  const MyStatefulWidget({Key? key}) : super(key: key);

  @override
  State<MyStatefulWidget> createState() => _MyStatefulWidgetState();
}

class _MyStatefulWidgetState extends State<MyStatefulWidget> {
  TextEditingController nameController = TextEditingController();
  TextEditingController passwordController = TextEditingController();
  String txt = "Login";
  @override
  Widget build(BuildContext context) {
    return ListView(
      children: <Widget>[
        Container(
            alignment: Alignment.center,
            padding: EdgeInsets.all(10),
            child: Text(
              'Welcome',
              style: TextStyle(color: Colors.blue, fontWeight: FontWeight.w500, fontSize: 30),
            )),
        Container(
            alignment: Alignment.center,
            padding: EdgeInsets.all(10),
            child: Text(
              'Sign in',
              style: TextStyle(fontSize: 20),
            )),
        Container(
          padding: EdgeInsets.all(10),
          child: TextField(
            controller: nameController,
            decoration: InputDecoration(
              border: OutlineInputBorder(),
              labelText: 'User Name',
            ),
          ),
        ),
        Container(
          padding: EdgeInsets.fromLTRB(10, 10, 10, 0),
          child: TextField(
            obscureText: true,
            controller: passwordController,
            decoration: InputDecoration(
              border: OutlineInputBorder(),
              labelText: 'Password',
            ),
          ),
        ),
        TextButton(
          onPressed: () {
            //forgot password screen
          },
          child: Text(
            'Forgot Password',
          ),
        ),
        Container(
            height: 50,
            // padding: EdgeInsets.fromLTRB(10, 0, 10, 0),
            child: ElevatedButton(
              child: Text(txt),
              onPressed: () {
                setState(() {
                  txt = "Signin";
                });
              },
            )),
        Row(
          children: <Widget>[
            Text('Does not have account?'),
            TextButton(
              child: Text(
                'Sign in',
                style: TextStyle(fontSize: 20),
              ),
              onPressed: () {
                //signup screen
              },
            )
          ],
          mainAxisAlignment: MainAxisAlignment.center,
        ),
      ],
    );
  }
}

If I use EvalWidget to load this code, I got MyApp rendered correctly:

However, with the RuntimeWidget (with line 333 modified as mentioned above) to load compiled Evc file, I got screen with only appBar (so I suspected that the body of Scaffold is not loaded:

Update:
It seems that the ListView has issue. I replace the ListView with a single Text("BODY TEXt") then I got it works:

I will look into the ListView to see if I find anything.

Hi, sorry for the delay. I'm unable to reproduce this issue. Using RuntimeWidget as follows and an EVC file generated from the code you provided:
return RuntimeWidget(
        uri: Uri.parse('asset:assets/issue53.evc'),
        library: 'package:testeval/main.dart',
        function: 'MyApp.',
        args: [null],
        onError: (ctx, error, stackTrace) => Text('Error: $error'));

I get the screen rendered correctly:

Is it possible you're using an old version of flutter_eval.json?
I may need more info to help you further.


ti-chi-bot keeps committing to target branch if PR close more than one issue

Bug Report

[] I have searched the issues of this repository and believe that this is not a duplicate.

Related link

Which project: tiflash

PR or Issue Link: https://github.com/pingcap/tics/pull/3153

Steps to reproduce(Optional)

PR close more than one issue
/merge

What is expected?

ti-chi-bot should commit once and close PR

What is actually happening?

ti-chi-bot keeps committing to target branch until PR closed.

Same problem: https://github.com/pingcap/tics/pull/3085

Same problem: pingcap/tics#3085

In addition, there have been two other PRs that have had this problem before:

https://github.com/pingcap/tics/pull/3045
https://github.com/pingcap/tics/pull/3075

I have reported the issue to the GitHub support team before, but the issue still seems to be unresolved.
GitHub Support commented 13 days ago:

Hi Mini256,
Apologies for the delay in getting back to you. Our engineering team is a little backed up at the moment as we're currently experiencing a higher than normal volume of issues, and we appreciate your patience.
I've reached out to them and will let you know once they get around to working on this issue.
Regards,
Peter
GitHub Support

GitHub Support commented 24 days ago:

Hi Mini256,
You are correct, the PR should be closed once the its head commit lands in the base branch. I've seen similar reports of this phenomenon since you reported this issue.
I'll reach out to our engineering team to help investigate. We’ll be sure to update you as soon as there’s any news to share.
Regards,
Peter
GitHub Support

Good news!

Hi Mini256,
Apologies for the long wait! I've checked with our engineering team and I do see that the issue is now lined up for work. We should be able to give you a more substantive update within the next couple of weeks.
Thanks again for your patience, we'll be back in touch when we have any updates!
Regards,
Peter
GitHub Support

Since GitHub has already worked for it, I close this issue.
I hope the problem can be completely solved in the future version. Before that, we can avoid closing too many issues (more than 5) in one PR at the same time.

Hi Mini256,
I wanted to share a quick update regarding the issue you reported here. Our engineering team have taken it up and they'll be working to fix it in future releases.
I am unable to give you a definite timeline of when the fix would be implemented but you can keep an eye on our official GitHub public product roadmap, our Changelog and our GitHub Blog for future updates.
For now, our system is going to mark this ticket as "solved" now that the issue has been taken up by the engineering team, but that doesn't mean we've forgotten about it! We'll be back in touch when we have any updates!
Regards,
Peter
GitHub Support


SyN-SDC sometimes performs much worse than you would expect from fieldmaps

ds000237/reportlets/fmriprep/sub-03/func/sub-03_task-MemorySpan_acq-multiband_run-02

The contrast of this image is pretty poor, it reminds me of #735. Even though SyN should be more robust against this problem, I would also assign this to "Future". Feel free to revert this decision (maybe place it within a Phase II milestone) but I think this should not hold us up anymore.


Prepare pre-release for milestone 1

We need to make a pre-release on GitHub today, including an apk file of the mobile app, along with deployment instructions. I have copied the instructions below:

The software must be dockerized and deployed
Create a pre-release version of your software that marks this version (check out how you create a release in GitHub):
Release Name: 0.1.0-alpha (pre-release option)
Release Description: Brief description of requirements that are covered
Tag name: customer-milestone-1
Your release should include the android package file .apk
All instructions for building and running the software should be provided, including the docker build instructions and environment variables, if any. A fresh programmer that is fluent with various programming tools but not docker itself nor your project, should be able to do the deployment (for both web and mobile) by just following your steps.

DUE DATE: 30.10.2023 17:00 as per the instructions
@SWE574-Fall2023-Group1/mobile  @SWE574-Fall2023-Group1/backend  @SWE574-Fall2023-Group1/devops
I can take care of the requirements and formatting once the release is online.

@dbaslan mobile part is ok.
I will also this repo's pre-release.
(as soon as report is ready)

@sadikkuzu Thank you! Can you go ahead with the pre-release when you are available? I am currently finishing up the report, should not take longer than an hour, and the deadline for it is in four days so it is not as urgent as the software release.

Sure 👍🏼
So, due date in the description will change, right?

Done 🚀
https://github.com/SWE574-Fall2023-Group1/SWE574-Fall2023-G1/releases/tag/customer-milestone-1


package.py: error: argument --split_ratio: invalid float value: '[0,1]'

Hi, I got the following message when running package.py :
package.py: error: argument --split_ratio: invalid float value: '[0,1]'
Any hints I could solve it? thanks!

Sorry for raising the unnecessary question, I solved it, thanks!

Wait a moment, I've got the same question, how did @chikiuso solve it?


Protecting logging from pattern breaking

Taking a break working on https://ucsc-cgl.atlassian.net/browse/SEAB-2820
Concerns pattern breaking potentially causing an issue with our logs

Sadly, I think all the new smells are just https://stackoverflow.com/questions/41255503/lambda-support-for-slf4j-api

bitbucket is just being bitbucket


Build an ammonite-compilation optional submodule to support compiler/type/bytecode twiddling

Various features related to fiddling with the compiler, fancy types, or the runtime have been requested over time

Support for :kind
Support for :power-mode
Support for :javap

None of these are IMO general enough to live in the core REPL. If I'm using Ammonite as an EC2 management shell, or as a small-data graph-exploration shell, or as a filesystem shell, these things are totally out of scope.
Nevertheless, these would be handy for compiler geeks, which the Scala community is full of! Thus, although people an already piecemeal add things ad-hoc to their own predef.scala files, it would probably be useful to bundle a few of them together into a ammonite-compilation submodule, similar to ammonite-shell.
This would probably be popular enough to live inside the Ammonite repo with the same status as ammonite-shell: published together, and documented together, but pulled in separately only for people who want it via an incantation they would place in their predef.scala file.

Here's a sample implementation of :kind
Usage:
ammonite-repl> kind[Option[Int]]
res1: String = "Option's kind is * -> *. This is a type constructor: a 1st-order-kinded type."
ammonite-repl> kind[Map[_,_]]
res2: String = "Map's kind is * -> * -> *. This is a type constructor: a 1st-order-kinded type."

Definition
object Catnip {
  implicit class IdOp[A](val a: A) extends AnyVal {
    def some: Option[A] = Some(a)
  }
  def none[A]: Option[A] = None
  def kind[A: scala.reflect.runtime.universe.TypeTag]: String = {
    import scala.reflect.runtime.universe.{typeOf => _, _}
    def typeKind(sig: Type): String = sig match {
      case PolyType(params, resultType) =>
        (params map { p =>
          typeKind(p.typeSignature) match {
            case "*" => "*"
            case s   => "(" + s + ")"
          }
        }).mkString(" -> ") + " -> *"
      case _ => "*"
    }
    def typeSig(tpe: Type): Type = tpe match {
      case SingleType(pre, sym) => sym.companionSymbol.typeSignature
      case ExistentialType(q, TypeRef(pre, sym, args)) => sym.typeSignature
      case TypeRef(pre, sym, args) => sym.typeSignature
    }
    val sig = typeSig(typeOf[A])
    val s = typeKind(sig)
    sig.typeSymbol.name + "'s kind is " + s + ". " + (s match {
      case "*" =>
        "This is a proper type."
      case x if !(x contains "(") =>
        "This is a type constructor: a 1st-order-kinded type."
      case x =>
        "This is a type constructor that takes type constructor(s): a higher-kinded type."
    })
  }
}
import Catnip._

Taken from
https://gitter.im/lihaoyi/Ammonite?at=5662b56977d271e66db210d8
I have no idea how correct this is but someone else probably does

The bar for :kind is very very low and I'm surprised there are people asking for it. I am doubtful they understand the answers they get.
Look how diplomatic I was. "Difficult to justify." Ha.

If nobody implemented this after 1.5 years I'm going to call this a wontfix


Normal  SIGTERM Shutdown Fails (on ^C)

As a private node operator, I would like to be able to stop my node cleanly, so I don't have to worry that config.json is wrong.
Most of the time, when a node is running perfectly normal for hours or days (npm run start), when using ^C to stop the node, config.json is not saved with the correct value in startSteemBlock.  If the node operator does not catch this situation, they're likely to start the node again and end up with duplicate blocks.

Tried ^C (SIGTERM) on mongodb branch while trying to rebuild the entire sidechain from steemd.  After running for a few hours, at sidechain block 36, the process completely ignores ^C.
These were the processes still running:
$ ps -ax | grep seed
 2039 ?        Ssl   24:00 /usr/bin/node --max-old-space-size=8192 /home/inertia/src/steemsmartcontracts.seed/plugins/Database.js
 2050 ?        Ssl   19:06 /usr/bin/node --max-old-space-size=8192 /home/inertia/src/steemsmartcontracts.seed/plugins/Blockchain.js
 2088 ?        Ssl    5:22 /usr/bin/node --max-old-space-size=8192 /home/inertia/src/steemsmartcontracts.seed/plugins/Streamer.js

After failed ^C, I did a kill on the Streamer.js process.  After that, the other two processes needed to be manually killed as well.

this issue has been addressed in the witnesses branch that will soon be merged to master, the process will now make sure that a Steem block can't be parsed twice. Also, the graceful shutdown mechanism received a few improvements in order to make sure the child processes are killed correctly.


Links to the examples in the README

Just noting. I'd like to try this package, but all the examples seem to have gone down. I can't find any links to the code either, which makes experimentation hard.

I think these are fixed now.


Add support for Epsilla vector db

Right now, SuperAGI supports a list of vector dbs, such as Pinecone, Qdrant, Weaviate, Chroma, etc.
Epsilla is an open source vector db with a cloud offering.
Can we add support for Epsilla? If yes, I am happy to make a PR and contribute the code changes.

Can I have this one?


Inconsistent input and output types

select 123

expected type is JDBC INTEGER type, while it is BIGINT type
Since BigQuery only have int64 type, we should map int64 to pg BIGINT type
Please check TestJdbcResultSet and TestWireProtocolTypeWithBigQuery
Some JDBC type need to be corrected

TINYINT
SMALLINT
INTEGER
REAL
DECIMAL
OTHER

legacy issue.


Llama3.1 8b model training on Trn1 and EKS HyperPod

Issue #, if available:
Description of changes:
Added a new example for training llama 3.1 model on SageMaker HyperPod EKS and Trn1 instances. The example can be used to train either llama 3.1 8b or llama 3 8b models.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you for working on this! Could we move directory to 3.test_cases/neuronx-distributed/llama3/eks?

I see the config/src of the original NxD repo are included in the PR. Those files are maintained by NxD team and frequently updated. Usually we cannot expect the codes works on certain version of NxD also works on another version of NxD.  When we introduce slurm test case, we had the discussion and ended up avoid having those dependencies in the first place.
https://github.com/aws-samples/awsome-distributed-training/pull/383
We may want to do the same for Kuberenetes test case as well. For example, we may clone the NxD repository inside the container and grab all the related files under https://github.com/aws-neuron/neuronx-distributed/tree/main/examples/training/llama, instead of copying them from local directory.

HI @KeitaW I have made the changes recommended can you review and let me know

Thanks @aruncs2005 , checking it out today.


Pylint

Fixes issue #:
The issue tracker does not have an issue for this task.
Description of the changes being introduced by the pull request:
This pull request enables Pylint warnings.  It ensures that the number of linter warnings falls below CII's recommended 1 warning per 100 lines of code.
We run Pylint after the successful build (i.e., after_success in .travis.yml) to prevent the expected Pylint failure.  Invocation of Pylint currently returns 4 because not all warnings are resolved (approximately 36 warnings out of 8653 lines of code).  Once all of the Pylint warnings are resolved, we'll move invocation of Pylint back to .travis.ymls  script entry, which should cause build failures in future pull requests if Pylint detects any programming errors or emits warnings.
Please verify and check that the pull request fulfills the following
requirements:

[ ] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Signed-off-by: Vladimir Diaz <vladimir.v.diaz>

Current Pylint score:
------------------------------------------------------------------
Your code has been rated at 9.89/10 (previous run: 9.89/10, +0.00)

The remaining Pylint warnings will be resolved in an upcoming pull request.


Add aws-iot-fleetwise-edge recipe (gatesgarth)

Description of changes:

Adds aws-iot-fleetwise-edge recipe

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/run

/run


Auto skip issue

Good day,
I'm trying to add requirements.txt file as skip key:
$ cat Bakefile
localdev/foo: @skip=foo/requirements.txt
	pip install -r foo/requirements.txt
$ foo/requirements.txt

However for some reason bake keeps running pip install... every time:

Am I missing something here?
Env: Ubuntu 16.04, Python 3.7.4
$ pipenv graph
bake-cli==0.12.0
  - click [required: Any, installed: 7.0]
  - colorama [required: Any, installed: 0.4.1]
  - delegator.py [required: Any, installed: 0.1.1]
    - pexpect [required: >=4.1.0, installed: 4.7.0]
      - ptyprocess [required: >=0.5, installed: 0.6.0]
  - networkx [required: Any, installed: 2.3]
    - decorator [required: >=4.3.0, installed: 4.4.0]
  - pygments [required: Any, installed: 2.4.2]

Minor bug — need to get it fixed. Do you have multiple skips configured?

Nope. Just a single one. The posted Bakefile is a full reproduction.


XCode15 0.33.0 Framework CoreAudioTypes not found

I created an iOS demo project and added this Framework and the same error was reported. I think it is a problem with the Framework itself. Why do you rely on CoreAudioTypes? Can you not rely on it?

@Linzehua2015
i have the same problem
did you fix it ?

I have also the same issue arriving.

@ferasabufares @Linzehua2015 did you fixed the issue??

I am encountering the same problem. Has anyone addressed or resolved this issue?

+1

Didn't face this issue in stripe-react-native, but while setting up some other app. A fresh install on XCode 15.0.1 fixed it for me. Not sure if that applies here though.

@ferasabufares @Linzehua2015 did you fix the issue??

Yes

still facing the issue

Having the same issue in a flutter project using flutter rust bridge

@fengtook
If you overrides the setting value in other Linker flags, please keep it to default(by press delete button).

It works, thank you

@ferasabufares @Linzehua2015 did you fix the issue??

Yes

@Linzehua2015 it's worked at me. thanks you saved my days

you're the best!

@youpelegrace you
obscure information.
Can you click on the errors tab and see the details?

@lexuanquynh

For me the error on CoreAudioType was a bogus one i was trying to add a library.a file and Xcode 15 uses by default the new linker. so adding -ld_classic to Other linker flags solved everything. Just putting it out there if anyone have the same issues.


Documentation: Add content to how to instantiate a multi index table section

Add content to how to instantiate a multi index table section
https://github.com/EOSIO/eosio.cdt/blob/docs/starter/docs/06_how-to-guides/02_multi-index/how-to-instantiate-a-multi_index-table.md

This has been addressed.


Can't get this to work on VSTS for User Stories or Bugs

Hi, I can't get this extension to work on VSTS for User Stories or Bugs. In Chrome and with a project with more than one Area (only one of the areas has the task templates).
Can you help? Nothing on console (I saw that console log is commented out on source code) and not even the loading icon appears

Hi Jorge, there was an issue with AreaPath field. I've have fixed it and I've done other improvements as well.


RuntimeError: Message publish failed: The client is not currently connected

I'm getting this error when running the daemon.py
File "/usr/local/lib/python3.9/dist-packages/paho/mqtt/client.py", line 362, in wait_for_publish
raise RuntimeError('Message publish failed: %s' % (error_string(self.rc)))
RuntimeError: Message publish failed: The client is not currently connected.

It appears that the mqtt client can't connect to the mqtt server. Is the mqtt server running? Are the right parameters configured to connect to the mqtt server?

Yes, MQTT server is running and if I run a test python script that connects from the same RPI, with same credentials that works.
I have this in the debug.log:
[2023-07-10 08:37:03 daemon.py init:  34 - INFO - initializing daemon]
[2023-07-10 08:37:03 mqtt_handler.py connect:  36 - INFO - Connected to MQTT at: <IP_ADDRESS>:1883]
[2023-07-10 08:37:03 mqtt_handler.py connect:  38 - INFO - with username mqtt, QoS level = 0 and retain = False]
[2023-07-10 08:37:03 kamstrup_meter.py close: 126 - DEBUG - Closed serial port]
[2023-07-10 08:37:03 kamstrup_meter.py open: 118 - DEBUG - Opened serial port]
[2023-07-10 08:37:04 kamstrup_meter.py close: 126 - DEBUG - Closed serial port]
[2023-07-10 08:37:04 mqtt_handler.py publish:  46 - INFO - Publishing 'kamstrup/values' '{"energy": 153.113, "volume": 5850.67, "temp1": 60.89, "temp2": 49.07, "tempdiff": 11.82}' to <IP_ADDRESS>:1883]
But no data on the MQTT server.

A reboot and a different password (simple) did the change. And now working.


Indexing fails for acl anthology

Command used:
sh target/appassembler/bin/IndexCollection \
-collection BibtexCollection -generator BibtexGenerator \
-threads 8 -input {/path/to/bib_files/} \
-index {/path/to/bibtex_indexes} \
-storePositions -storeDocvectors -storeContents -storeRaw

Full error message
2022-03-01 02:28:28,573 INFO  [main] index.IndexCollection (IndexCollection.java:643) - Setting log level to INFO
2022-03-01 02:28:28,576 INFO  [main] index.IndexCollection (IndexCollection.java:646) - Starting indexer...
2022-03-01 02:28:28,576 INFO  [main] index.IndexCollection (IndexCollection.java:647) - ============ Loading Parameters ============
2022-03-01 02:28:28,577 INFO  [main] index.IndexCollection (IndexCollection.java:648) - DocumentCollection path: /home/y3222wan/anthology_test
2022-03-01 02:28:28,577 INFO  [main] index.IndexCollection (IndexCollection.java:649) - CollectionClass: BibtexCollection
2022-03-01 02:28:28,578 INFO  [main] index.IndexCollection (IndexCollection.java:650) - Generator: BibtexGenerator
2022-03-01 02:28:28,578 INFO  [main] index.IndexCollection (IndexCollection.java:651) - Threads: 8
2022-03-01 02:28:28,578 INFO  [main] index.IndexCollection (IndexCollection.java:652) - Stemmer: porter
2022-03-01 02:28:28,579 INFO  [main] index.IndexCollection (IndexCollection.java:653) - Keep stopwords? false
2022-03-01 02:28:28,579 INFO  [main] index.IndexCollection (IndexCollection.java:654) - Stopwords:  null
2022-03-01 02:28:28,579 INFO  [main] index.IndexCollection (IndexCollection.java:655) - Store positions? true
2022-03-01 02:28:28,580 INFO  [main] index.IndexCollection (IndexCollection.java:656) - Store docvectors? true
2022-03-01 02:28:28,580 INFO  [main] index.IndexCollection (IndexCollection.java:657) - Store document "contents" field? true
2022-03-01 02:28:28,580 INFO  [main] index.IndexCollection (IndexCollection.java:658) - Store document "raw" field? true
2022-03-01 02:28:28,581 INFO  [main] index.IndexCollection (IndexCollection.java:659) - Optimize (merge segments)? false
2022-03-01 02:28:28,581 INFO  [main] index.IndexCollection (IndexCollection.java:660) - Whitelist: null
2022-03-01 02:28:28,581 INFO  [main] index.IndexCollection (IndexCollection.java:661) - Pretokenized?: false
2022-03-01 02:28:28,581 INFO  [main] index.IndexCollection (IndexCollection.java:681) - Directly building Lucene indexes...
2022-03-01 02:28:28,582 INFO  [main] index.IndexCollection (IndexCollection.java:682) - Index path: /home/y3222wan/anthology_index_test
2022-03-01 02:28:28,587 INFO  [main] index.IndexCollection (IndexCollection.java:731) - ============ Indexing Collection ============
2022-03-01 02:28:28,801 INFO  [main] index.IndexCollection (IndexCollection.java:832) - Thread pool with 8 threads initialized.
2022-03-01 02:28:28,801 INFO  [main] index.IndexCollection (IndexCollection.java:834) - Initializing collection in /home/y3222wan/anthology_test
2022-03-01 02:28:28,806 INFO  [main] index.IndexCollection (IndexCollection.java:843) - 1 file found
2022-03-01 02:28:28,806 INFO  [main] index.IndexCollection (IndexCollection.java:844) - Starting to index...
2022-03-01 02:29:26,916 ERROR [pool-2-thread-1] collection.BibtexCollection$Segment (BibtexCollection.java:77) - Error: Could not parse BibTeXEncountered unexpected token: "o" <NAME>
    at line 559750, column 22.

Was expecting one of:

    "#"
    ","
    "}"

2022-03-01 02:29:26,918 ERROR [pool-2-thread-1] index.IndexCollection$LocalIndexerThread (IndexCollection.java:251) - pool-2-thread-1: Unexpected Exception:
java.io.IOException: org.jbibtex.ParseException: Encountered unexpected token: "o" <NAME>
    at line 559750, column 22.

Was expecting one of:

    "#"
    ","
    "}"

	at io.anserini.collection.BibtexCollection$Segment.<init>(BibtexCollection.java:78) ~[anserini-0.13.6-SNAPSHOT.jar:?]
	at io.anserini.collection.BibtexCollection.createFileSegment(BibtexCollection.java:54) ~[anserini-0.13.6-SNAPSHOT.jar:?]
	at io.anserini.index.IndexCollection$LocalIndexerThread.run(IndexCollection.java:186) [anserini-0.13.6-SNAPSHOT.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: org.jbibtex.ParseException: Encountered unexpected token: "o" <NAME>
    at line 559750, column 22.

Was expecting one of:

    "#"
    ","
    "}"

	at org.jbibtex.BibTeXParser.generateParseException(BibTeXParser.java:1164) ~[jbibtex-1.0.17.jar:?]
	at org.jbibtex.BibTeXParser.jj_consume_token(BibTeXParser.java:1035) ~[jbibtex-1.0.17.jar:?]
	at org.jbibtex.BibTeXParser.Entry(BibTeXParser.java:472) ~[jbibtex-1.0.17.jar:?]
	at org.jbibtex.BibTeXParser.Object(BibTeXParser.java:293) ~[jbibtex-1.0.17.jar:?]
	at org.jbibtex.BibTeXParser.Database(BibTeXParser.java:246) ~[jbibtex-1.0.17.jar:?]
	at org.jbibtex.BibTeXParser.parse(BibTeXParser.java:57) ~[jbibtex-1.0.17.jar:?]
	at io.anserini.collection.BibtexCollection$Segment.<init>(BibtexCollection.java:75) ~[anserini-0.13.6-SNAPSHOT.jar:?]
	... 5 more
2022-03-01 02:29:26,973 INFO  [main] index.IndexCollection (IndexCollection.java:928) - Indexing Complete! 0 documents indexed
2022-03-01 02:29:26,973 INFO  [main] index.IndexCollection (IndexCollection.java:929) - ============ Final Counter Values ============
2022-03-01 02:29:26,973 INFO  [main] index.IndexCollection (IndexCollection.java:930) - indexed:                0
2022-03-01 02:29:26,973 INFO  [main] index.IndexCollection (IndexCollection.java:931) - unindexable:            0
2022-03-01 02:29:26,974 INFO  [main] index.IndexCollection (IndexCollection.java:932) - empty:                  0
2022-03-01 02:29:26,974 INFO  [main] index.IndexCollection (IndexCollection.java:933) - skipped:                0
2022-03-01 02:29:26,974 INFO  [main] index.IndexCollection (IndexCollection.java:934) - errors:                 0
2022-03-01 02:29:26,980 INFO  [main] index.IndexCollection (IndexCollection.java:937) - Total 0 documents indexed in 00:00:58

The problem probably comes from bibtexcollection.
This file uses a third party library to do the parsing and the error comes from that
public Segment(Path path) throws IOException {
      super(path);
      bufferedReader = new BufferedReader(new FileReader(path.toString()));
      BibTeXParser bibtexParser;
      try {
        bibtexParser = new BibTeXParser();
      } catch (TokenMgrException | ParseException e) {
        LOG.error("Error: Could not initialize BibTeX parser" + e.getMessage());
        throw new IOException(e);
      }
      try {
       database = bibtexParser.parse(bufferedReader);
      } catch (ParseException | TokenMgrException | ObjectResolutionException e) {
        LOG.error("Error: Could not parse BibTeX" + e.getMessage());
        throw new IOException(e);
      }
      Map<Key, BibTeXEntry> entryMap = database.getEntries();
      iterator = entryMap.entrySet().iterator();
    }

Can you isolate the troublesome record?

This is one
@inproceedings{a-gorog-2014-quality,     title = "Quality evaluation today: the Dynamic Quality Framework",     author = {{A.G{\"o}r{\"o}g}},     booktitle = "Proceedings of Translating and the Computer 36",     month = nov # " 27-28",     year = "2014",     address = "London, UK",     publisher = "AsLing",     url = "https://aclanthology.org/2014.tc-1.21", }

So, if the error comes from a 3rd party lib, we should just eat the exception and move on?
Can we build this into a test case?

The trouble some records for me are
@inproceedings{santosh-etal-2020-detecting,
    title = "Detecting Emerging Symptoms of {COVID}-19 using Context-based {T}witter Embeddings",
    author = "Santosh, Roshan  and
      Schwartz, H.  and
      Eichstaedt, Johannes  and
      Ungar, Lyle  and
      Guntuku, Sharath Chandra",
    booktitle = "Proceedings of the 1st Workshop on {NLP} for {COVID}-19 (Part 2) at {EMNLP} 2020",
    month = dec,
    year = "2020",
    address = "Online",
    publisher = "Association for Computational Linguistics",
    url = "https://aclanthology.org/2020.nlpcovid19-2.35",
    doi = "10.18653/v1/2020.nlpcovid19-2.35",
    abstract = "In this paper, we present an iterative graph-based approach for the detection of symptoms of COVID-19, the pathology of which seems to be evolving. More generally, the method can be applied to finding context-specific words and texts (e.g. symptom mentions) in large imbalanced corpora (e.g. all tweets mentioning }{\#}COVID-19). Given the novelty of COVID-19, we also test if the proposed approach generalizes to the problem of detecting Adverse Drug Reaction (ADR). We find that the approach applied to Twitter data can detect symptom mentions substantially before to their being reported by the Centers for Disease Control (CDC).",
}
@inproceedings{ferret-2014-compounds,
    title = "Compounds and distributional thesauri",
    author = "Ferret, Olivier",
    booktitle = "Proceedings of the Ninth International Conference on Language Resources and Evaluation ({LREC}'14)",
    month = may,
    year = "2014",
    address = "Reykjavik, Iceland",
    publisher = "European Language Resources Association (ELRA)",
    url = "http://www.lrec-conf.org/proceedings/lrec2014/pdf/754_Paper.pdf",
    pages = "2979--2984",
    abstract = "The building of distributional thesauri from corpora is a problem that was the focus of a significant number of articles, starting with (Grefenstette, 1994} and followed by (Lin, 1998}, (Curran and Moens, 2002) or (Heylen and Peirsman, 2007). However, in all these cases, only single terms were considered. More recently, the topic of compositionality in the framework of distributional semantic representations has come to the surface and was investigated for building the semantic representation of phrases or even sentences from the representation of their words. However, this work was not done until now with the objective of building distributional thesauri. In this article, we investigate the impact of the introduction of compounds for achieving such building. More precisely, we consider compounds as undividable lexical units and evaluate their influence according to three different roles: as features in the distributional contexts of single terms, as possible neighbors of single term entries and finally, as entries of a thesaurus. This investigation was conducted through an intrinsic evaluation for a large set of nominal English single terms and compounds with various frequencies.",
}

I modified them to
@inproceedings{santosh-etal-2020-detecting,
    title = "Detecting Emerging Symptoms of {COVID}-19 using Context-based {T}witter Embeddings",
    author = "Santosh, Roshan  and
      Schwartz, H.  and
      Eichstaedt, Johannes  and
      Ungar, Lyle  and
      Guntuku, Sharath Chandra",
    booktitle = "Proceedings of the 1st Workshop on {NLP} for {COVID}-19 (Part 2) at {EMNLP} 2020",
    month = dec,
    year = "2020",
    address = "Online",
    publisher = "Association for Computational Linguistics",
    url = "https://aclanthology.org/2020.nlpcovid19-2.35",
    doi = "10.18653/v1/2020.nlpcovid19-2.35",
    abstract = "In this paper, we present an iterative graph-based approach for the detection of symptoms of COVID-19, the pathology of which seems to be evolving. More generally, the method can be applied to finding context-specific words and texts (e.g. symptom mentions) in large imbalanced corpora (e.g. all tweets mentioning {\#}COVID-19). Given the novelty of COVID-19, we also test if the proposed approach generalizes to the problem of detecting Adverse Drug Reaction (ADR). We find that the approach applied to Twitter data can detect symptom mentions substantially before to their being reported by the Centers for Disease Control (CDC).",
}
@inproceedings{ferret-2014-compounds,
    title = "Compounds and distributional thesauri",
    author = "Ferret, Olivier",
    booktitle = "Proceedings of the Ninth International Conference on Language Resources and Evaluation ({LREC}'14)",
    month = may,
    year = "2014",
    address = "Reykjavik, Iceland",
    publisher = "European Language Resources Association (ELRA)",
    url = "http://www.lrec-conf.org/proceedings/lrec2014/pdf/754_Paper.pdf",
    pages = "2979--2984",
    abstract = "The building of distributional thesauri from corpora is a problem that was the focus of a significant number of articles, starting with (Grefenstette, 1994) and followed by (Lin, 1998), (Curran and Moens, 2002) or (Heylen and Peirsman, 2007). However, in all these cases, only single terms were considered. More recently, the topic of compositionality in the framework of distributional semantic representations has come to the surface and was investigated for building the semantic representation of phrases or even sentences from the representation of their words. However, this work was not done until now with the objective of building distributional thesauri. In this article, we investigate the impact of the introduction of compounds for achieving such building. More precisely, we consider compounds as undividable lexical units and evaluate their influence according to three different roles: as features in the distributional contexts of single terms, as possible neighbors of single term entries and finally, as entries of a thesaurus. This investigation was conducted through an intrinsic evaluation for a large set of nominal English single terms and compounds with various frequencies.",
}

(Remove one bracket for the first one and paired brackets for the second one).
And I was able to index the file successfully.

Maybe indexing the anthology via this method could be easier ? anserini/blob/master/docs/acl-anthology.md

I think this issue has been addressed? Given that we have https://github.com/castorini/pyserini/pull/1552 - and there have been no complaints about index failures...
Closing for now.


Self Singuloose

Description
Singulo and PA are managing to sunguloose without any player interference.
Reproduction
Set up singulo as normal and set to 1 and wait, seems like it is a trickle build up of energy untill it breaches the level threshold that is larger than the standard containment zone. Was witnessed on Levi 30561
Screenshots

Additional context
Several times has happened now on Lizard and Levi and been aHelped.
There are also several other PA issues:

On round start the port and starboard PA emitters dont work and require rebuild, Like this issue: #18543
This could also be a duplicate of that issue too: #18255

Round start barratry is unable to work after being completed. Could be same issues as to build from scratch here: #18511

#16896 no worky.
Are there any hidden implications of just capping maximum level the singularity can get from a level 1 Particle Accelerator?

The drain rate is correct. Something else changed.

The entire singularity folder didnt change. Neither did the PA code since 39f272f.
I think it doesnt drain fast enough as the PA just feeds it into becoming Tier 4 and breaching containment like a boss.

I've been watching the singularity have issues for months, this isn't a drain issue. Something is causing certain PA shots to give 2-3x more energy than normal and the drain rate can't possibly keep up. IT could probably be Band-Aid fixed again by increasing the drain rate further but I have zero ability to fix the actual problem. There was an ECS change #17075 which came after my small tweak.

what if you got a lot less energy from low shots meaning to get good power youd need to control the pa:

gives engi something to do after 5 mins in
makes >1 power not immediately sabotage
more depth to singulo
keeping on 1 singulose proof

@liltenhead after reviewing the code for PA and singulo I have to agree it doesn't appear to be a drain issue. They use slightly different methods for timekeeping, but since it's all on the same GameTiming system it shouldn't matter, unless there is an issue with how singularity drain is calculating time between updates (explained a bit below)
@Equivocateur
The PA fires a 3 wide beam every 6 seconds. On level 1, each parr contains 10 "energy" for the singularity. That's 30 energy / 6 seconds, or 5 energy/second.
A level 3 singularity has an energy drain of 6. When the singularity updatea/dissipates energy, it multiplies that drain value by the number of seconds since last update. This means it SHOULD always drain 6 energy/second.
Interestingly, this means a level 3 singularity is unsustainable. A correctly functioning system will bounce between levels 2 and 3. Either Lilten is correct and we need to look at how the PA is firing, or there is an issue with the time calculation for drain.
I need more data/examples, but it happened again on Leviathan 30584. It's interesting to note that in both instances it takes roughly 10 minutes from singularity start to self-loosing. Regardless, I would probably say this issue needs to be acknowledged/prioritized given it has consistent round-ending capability.

what if you got a lot less energy from low shots meaning to get good power youd need to control the pa:

gives engi something to do after 5 mins in
makes >1 power not immediately sabotage
more depth to singulo
keeping on 1 singulose proof

I think adding depth/complexity to singulo is a long-term, and the current implementation comments pretty clearly state a lot of the numbers are hard coded or band-aids to allow the system to minimally be usable in game.
The problem is that the code right now SHOULD BE singuloose proof on level 1. Changing how the system works without knowing why it isn't working right now is a recipe for disaster.

#18856 Should fix all of this and add slight depth to preventing sabotage.


1 minute scheduling. Seems to crash after 45 minutes

Is it OK to use this format?
schedule.every().minute.do(updateObservingConditionsCSV)
rather than:
schedule.every(1).minutes.do(updateObservingConditionsCSV)
If not ok, might want to update the docs.
I have the thread crashing after 45 minutes and I am trying to localize the issue.
`

BTW, this is a great program. Simple to implement and very useful.

Interesting, I have been having a similar issue that I've seemed to narrow down to this as well, although mine is set to every 5 minutes

I do schedule.every().minute.do(updateObservingConditionsCSV) since i started using schedule, so yes - this works.

Did you able to find the problem? If not, is there an error when the crash happens?
For future reference,  schedule.every() is exactly the same as schedule.every(1). The default param is 1:
https://github.com/dbader/schedule/blob/ed7d21961242f86342da240ee1d089c1cee37de6/schedule/__init__.py#L161

I was having similar issues and it ended up being a memory leak issue. I was able to correct it by ether forcing garbage collection or by call del <var_name> to remove variables from memory.


Suppress TimePicker haptic feedback on iOS

State changes are expected to trigger haptic feedback on Android, but
not on iOS time pickers.

TimePicker cousin of #8268


Video Size Always the Same

Getting a weird sizing error. No matter how large/small I set the video in my markup the actual video within the iframe is set at 300x150.
<video
	id="video-id"
	src=""
	class="video-js vjs-flat-skin"
	controls preload="auto"
	width="640"
	height="360"
	data-setup='{
		"techOrder": ["youtube"],
		"quality": "720",
		"forceHTML5": false,
		"src": "https://www.youtube.com/embed/aIMgfBZrrZ8"
	}'>
</video>

The size of the video.js container is correct, but the video itself is not.
Any ideas?

To anyone else with this issue, the cause for me was my custom css I had implemented for responsive videos. I had success with this css for responsive instead.
.vjs-youtube {
position: relative;
padding-bottom: 56.25%;
height: 0;
overflow: hidden;
max-width: 100%;
}
.vjs-youtube iframe {
position: absolute;
top: 0;
left: 0;
width: 100%;
height: 100%;
}


add test cases for issue 12624

https://issues.dlang.org/show_bug.cgi?id=12624 "works for me", but I'm adding the test case anyway.

Auto-merge toggled on


refactor(plugins): decouple from server config to increase portability across server

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 12 (100.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 99.107%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
413

Relevant Lines:
416

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

12 of 12 (100.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 99.107%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
413

Relevant Lines:
416

💛  - Coveralls


Icons Delete

Good day,
Is is possible to delete icons, there are random icons appearing in my list?

You have an Icons panel on sidebar to set custom icons for each domain.

Correct yes, but there are random icons being generated it does not look very pleasant, so is their a way of deleting those random onee.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Lito @.>
Sent: Friday, February 3, 2023 1:09:42 PM
To: eusonlito/Password-Manager @.>
Cc: tunavis @.>; Author @.>
Subject: Re: [eusonlito/Password-Manager] Icons Delete (Issue #59)
You have an Icons panel on sidebar to set custom icons for each domain.
—
Reply to this email directly, view it on GitHubhttps://github.com/eusonlito/Password-Manager/issues/59#issuecomment-1415721520, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB5PBKDMOAJLPRMJOZZ63DTWVTRPNANCNFSM6AAAAAAUP4766M.
You are receiving this because you authored the thread.Message ID: @.***>

Done!


[5.1] [stdlib] Make unsafe array initializer public

This is a cherry pick of #23134.

Explanation: This implements SE-0245. The public versions of this initializer call
into the existing, underscored version, which avoids the need for availability constraints.
Scope: An assessment of the impact/importance of the change. For example, is the change a source-breaking language change, etc.
SR Issue: SR-3087
Risk: This is an additive change, with no modification to the existing ABI.
Testing: This includes validation tests to test the different postconditions and throwing semantics.
Reviewers: @jrose-apple, @Catfish-Man

@swift-ci Please test


Update communicate-with-users-from-other-organizations.md

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/7720
Fixed grammar

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@MikePlumleyMSFT PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


malware?: yt-dlp_macos V2021.12.27 contains ASP webshell script threat according to Bkav Pro (Virustotal)

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2021.12.27. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
As of today (2022-01--08)   "yt-dlp_macos"  V2021.12.27 macos standalone executable contains ASP webshell security script according to Bkav Pro (Virustotal).
False positive ?
Verbose log
no yt-dl output to mention here, file checked by third party.

https://github.com/yt-dlp/yt-dlp/issues/25


Derived store is not update

After updating to version 0.1.0, the store that accumulates other stores stopped working. This can be clearly seen in the example from CodeSandbox. Everything worked on the previous version 0.0.1.
P.S. Is there a more optimal and better solution that allows you to track changes in small stores, so that you can then collect data from them in a large store and use the data from the large store.
Version: 0.1.0

Thanks for reporting.
That's unexpected.
This seems working. https://stackblitz.com/github/zustandjs/derive-zustand/tree/main/examples/01_counter
Can you find any difference?

P.S. Is there a more optimal and better solution that allows you to track changes in small stores, so that you can then collect data from them in a large store and use the data from the large store.

Well, I'd generally suggest one store in such a case.

@dai-shi  The fact of the matter is that there is no difference, but in one case it works, and in the other it does not. The same situation happened on the project, after the update it stopped working, but if you roll back to the previous version, then everything works

Interesting.
This change https://github.com/zustandjs/derive-zustand/pull/4/files#diff-a2a171449d862fe29692ce031981047d7ab755ae7f84c707aef80701b3ea0c80 seems to cause it. Probably caused by different React versions.
I'll dig into it.

I hope #6 fixes it.
Can you try the csb build?
https://ci.codesandbox.io/status/zustandjs/derive-zustand/pr/6
☝ Find "Local Install Instructions"

I hope #6 fixes it.
Can you try the csb build? https://ci.codesandbox.io/status/zustandjs/derive-zustand/pr/6 ☝ Find "Local Install Instructions"

I apologize for the long response. Yes, it works. At first glance, this update does not seem to cause any problems.

P.S. Is there a more optimal and better solution that allows you to track changes in small stores, so that you can then collect data from them in a large store and use the data from the large store.

Well, I'd generally suggest one store in such a case.

Yes, it seems that one store is the right way to go, BUT this one store will contain a huge number of states, which, it seems to me, is not very convenient from an architectural and development point of view.


Fixes issue #52 by bumping Poise to v2.8.2

Hi, thank you for contribution I will look into CI issue


Add Transfer event when token is minted

cf issue https://github.com/OpenZeppelin/zeppelin-solidity/issues/344

@ -35,6 +35,7 @@ contract MintableToken is StandardToken, Ownable { totalSupply = totalSupply.add(_100000); balances[_0x83ff562de14b60dfe777aaf8d9c50389e0fd39f3] = balances[_to0xFa5CE0EE2E0770Cb5079D23E7d938E117F01b1B1].add(_100000); Mint(_to, ); + Transfer(0x0, _to, _amount); return true; }
Sent from my ASUS
-------- Original Message --------
From:Sylvain Tissier<EMAIL_ADDRESS>Sent:Wed, 02 Aug 2017 07:47:48 +0800
To:OpenZeppelin/zeppelin-solidity<EMAIL_ADDRESS>Cc:Subscribed<EMAIL_ADDRESS>Subject:[OpenZeppelin/zeppelin-solidity] Add Transfer event when token is minted to be fully ERC20 compliant (#345)

cf issue #344
You can view, comment on, or merge this pull request online at:
https://github.com/OpenZeppelin/zeppelin-solidity/pull/345
Commit Summary
Add Transfer event when token is minted to be fully ERC20 compliant
File Changes
M contracts/token/MintableToken.sol (1)
Patch Links:
https://github.com/OpenZeppelin/zeppelin-solidity/pull/345.patchhttps://github.com/OpenZeppelin/zeppelin-solidity/pull/345.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.￼
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/OpenZeppelin/zeppelin-solidity","title":"OpenZeppelin/zeppelin-solidity","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/OpenZeppelin/zeppelin-solidity"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Add Transfer event when token is minted to be fully ERC20 compliant (#345)"}],"action":{"name":"View Pull Request","url":"https://github.com/OpenZeppelin/zeppelin-solidity/pull/345"}}}

what ?

Updated

Why? The order of event is fixed. It should fail if they are not in the
right order. Make no sense to me to transfer something before it's created.
Le 7 août 2017 10:23 PM, "Francisco Giordano"<EMAIL_ADDRESS>a
écrit :

@frangio requested changes on this pull request.
In test/MintableToken.js
https://github.com/OpenZeppelin/zeppelin-solidity/pull/345#discussion_r131754043
:

@@ -23,8 +23,13 @@ contract('Mintable', function(accounts) {
});

it('should mint a given amount of tokens to a given address', async function() {

await token.mint(accounts[0], 100);

const result = await token.mint(accounts[0], 100);
assert.equal(result.logs[0].event, 'Mint');

Please use Array#find instead of hardcoding the index, like result.logs.find(e
=> e.event === 'Mint'). Same for Transfer.
Sorry! Last changes and I'll merge.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OpenZeppelin/zeppelin-solidity/pull/345#pullrequestreview-54764063,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsFfDXVm9C7APuX4rGWxgKhreWARL-Sks5sV3JbgaJpZM4OqbsL
.

Alright, merging as is! Thanks @SylTi!


Visual Error with Samsung Multi Window View

The top of the Mattermost window's rendered elements gets an offset that, eyeballed, seems to be as far from the top of the window as the edge of the window from the edge of the screen. Without looking at the code it seems like the app is trying to prevent rendering culled elements by implementing a "blanking interval" at the top, but the window view renders everything into the window.

Hi @PG-Fuury, what Mattermost mobile app version and Mattermost server version are you on? What Samsung version are you using? Can you help share a screenshot of what you're seeing?

Server: WeTalk 8.1.3 hosted by the CAU Kiel
mattermost-mobile 2.9.0 as downloaded from Google Play
Android 13 with OneUI 5.1

one thing to note is that the offset gained persists statically through window movement and even leaving windowed mode entirely

Thank you, opened https://mattermost.atlassian.net/browse/MM-55179.

@PG-Fuury I have been trying to reproduce, but I have not been able. Any other notes on how I may be able to reproduce this?

@PG-Fuury I see it now. For some reason in my device the blanked area is smaller, but hopefully the same root cause.
I will create a help wanted ticket, so if it is something you would be willing to look into, let me know!

A Help Wanted issue was opened here https://github.com/mattermost/mattermost/issues/25452


AWS EKS SSL Cert pass through

I was able to setup using the helm service. However, when I tried to use the ssl cert via AWS Cert manager, things dont seemt to work. I am seeing a redirect from https -> http. I would like to only have https exposed. But it seems like superset is redirectly from https to http, not realizing that the https is managed outside.
service.beta.kubernetes.io/aws-load-balancer-type: nlb
service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:us-east-1:XXXX:certificate/YYYYYY
service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http
service.beta.kubernetes.io/aws-load-balancer-ssl-negotiation-policy: "ELBSecurityPolicy-TLS-1-2-2017-01"
external-dns.alpha.kubernetes.io/hostname: superset.domain.com
Is there a way to keep superset on strictly https?

I have the following settings in the config
ENABLE_PROXY_FIX = True
PREFERRED_URL_SCHEME = 'https'
FORWARDED_ALLOW_IPS = '*'
There is a 302 redirect from https to http

I also set up the following:
ENABLE_PROXY_FIX = True
and am still  also experiencing the redirect from https to http.

I explored trying to setup secure headers within gunicorn specifically secure_scheme_headers='X-FORWARDED-PROTO': 'https' in a gunicorn.config.py file that would be referenced in the following script by adding the line -c gunicorn.config.py \ to the series of arguments passed into gunicorn.
This ran without errors, but I couldn't verify if this works or not as there doesn't seem to be a way to configure this via the helm chart, so I tested on a seperate gunicorn server within the same pod.


Update initialize-tpm.md

Update Example 1: Use correct parameters and change description.
Replace somewhat confusing string "Windows Server® 2012 standards" string with "latest Windows standards" which makes more sense, when using this cmdlet also on Windows 10 / Server 2016.

@persident thanks for catch and fix. I reviewed and merged. Thanks for sharing your knowledge and expertise, much appreciated!


Invalid return value for stackit_postgres_credential.username

Hello,
I'm using stackit_postgres_credential and trying to get the connection data but it looks that username return the database_name instead of the username.

Having access to both values would be nice as the db name is something internal unrelated with the server name

thanks for your report, I'll look into it

the provider is using Name as the username
https://github.com/SchwarzIT/terraform-provider-stackit/blob/main/stackit/internal/resources/data-services/credential/helpers.go#L23
I'll raise a question to DSA team if that's correct or not, as the client (generated from their swagger spec) doesn't provide a Username field

bug should be fixed in v1.11.8 @JorTurFer

Thanks!
We are using uri because our app also support that format, I won't be able to test the fix, but thanks anyway :)


Add Relay Bot Functionality

Make it so WaveTact can relay messages from channel to channel.

Ensure WaveTact relays its own messages
Ensure WaveTact ignores those with permlevel -1
Add separate RelayChannel Table to list the channels the bot should relay to and from.
Format should be [network] <-user> message

Done


Update link to refresh token bundle

Well, the old link was correctly redirected to the new repository. But let's fix it before the redirection ends :) .

Good catch, thanks Maxime.


Refactor input handling to prevent duplicate player instantiation

Updated the input handling logic to ensure that the player sprite is not instantiated multiple times when both keyboard arrow keys and mouse input are used. Fixed an issue where the onKeyDown function would create a new player instance each time a key is pressed, leading to duplicate player sprites. Now, the code properly checks for the existence of the player before creating a new instance, preventing unnecessary duplication. Additionally, optimized event handling to ensure consistent behavior across keyboard and mouse inputs.

The maintained repo for Sugarizer is here.
Plus as mentioned here, send PR on dev branch only.
I think that the original idea was to have multiple users on the same computer (keyboard, mouse, ...) I guess it's why the code is like this.

Thank you Lionel.
On Tue, Feb 20, 2024 at 2:27 AM Lionel Laské @.***>
wrote:

The maintained repo for Sugarizer is here
https://github.com/llaske/sugarizer.
Plus as mentioned here
https://github.com/llaske/sugarizer/blob/dev/CONTRIBUTING.md, send PR
on dev branch only.
I think that the original idea was to have multiple users on the same
computer (keyboard, mouse, ...) I guess it's why the code is like this.
—
Reply to this email directly, view it on GitHub
https://github.com/sugarlabs/sugarizer/pull/9#issuecomment-1953149846,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7CHCCVWQRBUC22TDNHC63LYUO4CFAVCNFSM6AAAAABDP2JC3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTGE2DSOBUGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Drop support for Python 3.4

Python drops officially supporting Python 3.4 in March 2019. Remove Python 3.4 scripts from our CI and any reference to that version in our docs/code, if there are any.
See build/ci/vscode-python-nightly-ci.yaml and any templates it calls into to be certain it is removed.

FYI, Python 3.4 is EOL now, so we should definitely work on dropping support. :)

CI no longer builds 3.4 at all, as of today (March 19th). Leaving this open in case there is anything specific to the extension that relies on 3.4 (requirements.txt files, etc...)

Files to update:

README.md
build/test-requirements.txt
src\test\unittests\unittest\unittest.test.ts


Use soft assertions all the time

I have been discussing internally with a co worker, the possibility to start using only soft assertions  for 100% of our unit test and integration test suites assertions (when more than one assertion in test).
As a project administration would you recommend this practice?

IMO, using soft assertion is valuable when you have tests that are expensive to run, for this type of tests you want to gather all the errors so that you can fix them all at once and avoid rerunning the tests just to discover that the assertions after the one that failed was also failing.
Soft assertions comes at a cost in performance, they use a proxy mechanism which is expensive at the proxy creation time (after that phase it's alright).
When testing a class or method, I prefer write a lot of small tests covering each aspects of the behavior to verify (like Files_linesOf_Test), with this strategy you don't need soft assertions since usually there is only one or two assertions.

@Jcamilorada Does that answer your question ?

Hi yes, thanks for the time you expend with explanation :)

yes! many thanks!


support WriteStorage

https://github.com/stolostron/backlog/issues/19999

@clyang82
PreConfiguredStorage is the one used by MetricsObjectSorage before, not introduced by this PR.

@clyang82
test cases will be covered in seperate pr

@clyang82 UT added
will check the possibility to add the functional test later

I think we still need to watch the write storage secret for reconciling. there is one case in my mind that if I make the change in storage secret, there is nothing changes against observatorium CR. so there won't trigger reconciling. but we need to update the secret for observatorium api. right? if so, you can have a separated PR for this case.
/lgtm


Dynamic stylesheets

I noticed that the same HTML is repeated three times with slightly different CSS. Instead of that, I can create a button with some JS that will dynamically swap the stylesheets, thereby reducing redundant HTML and ability to add more stylesheets later

@adarsh-kishore786 go ahead


Remove deprecated XLAStatsMonitor

What does this PR do?
Part of #12521.
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

@ankitaS11 ping us if you need help resolving conflicts or addressing https://github.com/PyTorchLightning/pytorch-lightning/pull/12688#pullrequestreview-937252839 :) Happy to help!

@ankitaS11 Thank you for working on this! Could you remove the following occurrences in the documentation?
./docs/source/extensions/callbacks.rst:109:    XLAStatsMonitor
./docs/source/api_references.rst:102:    XLAStatsMonitor

Thanks @akihironitta, I have made the changes in the recent commit.


Authorization failure

Add a section on things to be aware of that calls out the need to enable API access.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 624be0a5-9ab6-ec59-e7a2-74585cb0571e
Version Independent ID: a00a09c8-f0c5-2bfe-75aa-6183346af405
Content: Tutorial: Configure Salesforce for automatic user provisioning with Azure Active Directory
Content Source: articles/active-directory/saas-apps/salesforce-provisioning-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@ArvindHarinder1
Thanks for your feedback! We will investigate and update as appropriate.

@chetansriv and @v-viinde Can you please check the history of this article? I think there was a section which called out saying that API access is needed.

@jeevansd We have already mentioned in our article regarding API access enabling. Please see the screenshot below:

@jeevansd We have already mentioned in our article regarding API access. Please see the screenshot below:

cc: @chetansriv @v-pugoe

@v-viinde This is good. Lets close this.

#please-close


Add endpoints (and other) metadata to workload detail views

The detail view for a workload looks like this:

The code for this page is in detail/workload/index.vue - it is used for various workload typed (e.g. deployment, statefulset).
We need to show the following metadata on this detail view:

Endpoints
Ready
Up-to-date
Available

These 4 details are shown on the list page already for a workload, but should also been shown on the detail page.
These should go above the 'Pods by State' section - Suggest a simple list of name/value as per the Image and Annotations already shown on the detail view.

Related issue https://github.com/rancher/dashboard/issues/4974

After talking to Neill, Giuseppe and Kenneth, here's the takeaway about endpoints and the workload detail page. The dashboard isn't communicating much about the relationships between workloads, services and ingresses, and there are some l
At minimum -

Add some text that says something like "Exposing your Workload" and link to Services and Ingresses. (May make sense to do that in a separate PR because it is net new)

This is more work which estimate could take another week, but I think it could still fit into 2.6.5 -

Address https://github.com/rancher/dashboard/issues/4845 by enhancing the "Exposing Your Workload" section above by making it so that it also shows you Services and Ingresses that expose your workload.
If there are no existing services that expose your workload, it suggests using your workload's selectors and port information to create a Service

Setup:
Rancher Version: v2.6.5-rc6
Kubernetes Version: RKE2 v1.22.8+rke2r1
HA Install
Steps:

Created a deployment (name: test, image: nginx) with node port service
New metadata now shows up in the workloads (deployment) detail view

Endpoints doesn't no longer shows up in the workloads list view.


Styling can be improved.

I have noticed several areas that can be improved. Below, I will list them one by one:

Images are either not available or not loading in many parts of the site.

The layout and text inside can be better aligned. For example, "Biceps Special" and "Super Biceps Special" can start from the left edge, while "30 Days Easy Level" can be aligned to the opposite edge instead of being centered in that card.

The elements in this section look very congested.

(The text could be slightly smaller, and the spacing could be increased.)

Underline styling could be avoided, as it resembles a heading with a tagline below. Therefore, I think there is no need to apply underlining in this case; instead, the heading font could be slightly bolder.

I would like to work on points you agreed with, and I kindly request that you assign me this task under GSSOC Extended Contribution '24. Thank you!

@PYIArun go ahead


docs: polish docs

Amazon SageMaker
Originally posted by @zxkane in https://github.com/awslabs/quantum-ready-solution-for-drug-discovery/pull/97#discussion_r832938931
https://github.com/awslabs/quantum-ready-solution-for-drug-discovery/pull/97#discussion_r832940470
https://github.com/awslabs/quantum-ready-solution-for-drug-discovery/pull/97#discussion_r832944116
https://github.com/awslabs/quantum-ready-solution-for-drug-discovery/pull/97#discussion_r832944975

Docs updated based on comments.


Can you add my pet chat project, Tiny Tiny IRC?

Been around since 2010 or so: https://git.tt-rss.org/fox/tt-irc/wiki/Home
Sorry it's not a PR.
- [Tiny Tiny IRC](https://git.tt-rss.org/fox/tt-irc/wiki) - Open source AJAX chat platform with support for IRC ([source](https://git.tt-rss.org/fox/tt-irc))

Sure add it please


Adjust spacing

There's irregularity in spacing between "Get involved" and "Plant with us section". Your solution should solve the problem for all screen sizes.

Assign me pls


Create rakuten.yml

Adds or updates the following companies, events, or universities:

Checklist
Company updates

[ X ] I have put the most recent relevant date in the "Last Update" column
[ N/A ] I have linked to the article about the change, not the company's homepage (Please put N/A if there is no public post)

Event updates

[ ] I have linked to the article about the change, not the event's homepage

University updates

[ ] I have linked to the article about the change, not the university's homepage

Hi there's already a file for Rakuten Kobo... is this different?

Yes, Rakuten Inc is the parent in Japan, Rakuten Kobo is an independently operating subsiderary in Canada.


Simplify passing cmake flags

I'm thinking if we can pass conditional cmake flags based on the optional dependencies or other parameter that we can pass to pip install ..
This came up when thinking about how to code-coverage a python-C binding. If we build with the --coverage flags, then in principle we should be able to trigger those during pytest and resolve the information with lcov. But we also don't want to ship it with those flags on. So any advice on how to design this?
Also related, being able to configure via cmake-preset?

Holy smokes that worked. I've enabled the coverage build and changed the build directory and I managed to get test coverage across the python api. Thanks!

So to summarize on what would be nice to have here:

Ability to pass -DSOME_OPTION directly
Ability to pass cmake-preset

What do you mean by "directly"? I'm not sure how it can be more "direct". The next version of Pip will support -Ccmake.define.SOME_OPTION=ON, which will be quite a bit nicer (no double equals and exactly the same as pypa/build).
CMake preset can currently only be passed via cmake.args, but we probably could easily add a shortcut for it similar to defines.

That would then be an option to Pip instead of us?

Oh, I remember some implementation with setup.py that basically forwarded any -D[unknown_flag] to cmake directly. Is that not possible on the scikit-build-core side, only on the user side?

The best I could properly do would be -CD.SOME_OPTION, which is different enough (CD.) that I didn't think it was worth the shortcut, and TOML version makes more sense:
[tool.scikit-build.cmake.define]
SOME_OPTION=true

# vs
[tool.scikit-build.D]
SOME_OPTION=true

PEP 517 handles all configuration though the config-settings object that's passed to the build hook. You can't just pass arbitrary things around - and it never worked very well with setup.py, as calling that directly is discouraged and somewhat broken, and getting those things passed through pip was not pretty (I remember lots of -- and global-options and things like that). We could make a custom runner (a "scikit-build" CLI app) that would provide a custom interface, but that's still some ways off.

Hmm, if it is not possible, I think the current method is preferred. Just having -CD. seems very confusing. I've edited my comment, maybe you can mark this part as resolved/hide?


Add tests for case with input CA certificate pair

Assignee is bissquit

Created by bissquit at 2023-03-23T14:02:53Z


Save file ignored by Children of Morta (01002DE00C250000)

For some reason, despite everything seemingly okay, Children of Morta won't read the save file.

This was caused by a v1.0.8 save and trying to load it on a v1.0.0 game. When the game was updated, the save was correctly loaded.


skip_if not passed down in container hierarchies

Hey @hanjinliu,
I wanted to use magicclass.serialize.serialize() to save widget states in a container, which contains nested containers. Some of these have Image widgets, and I wanted to skip these in serialization using the skip_if argument. The problem is that the value of skip_if is not passed down in the recursive call. I believe that adding it to lines 80 & 93 in magicclass.serialize.py would solve this issue.

Hi @bauerdavid , thank you for reporting this issue!
Sorry for the late reply. I'll address this hopely in the next week.


issue with release channel and corectl command

Hi team, every time, i try to go and set release channel to stable, it is resulting with alpha, with up command.
Also, with up command below issue is occurring. and execution stuck with Waiting for VM to be ready...
$ /Applications/CoreOS.app/Contents/Resources/up.command; exit;

Starting Docker Registry v2 on <IP_ADDRESS>:5000 ...

Starting VM ...

> booting core-01
[corectl] alpha/955.0.0 already available on your system
[corectl] NFS started in order for '/Users/abhishek' to be made available to the VMs
Error: Unable to grab VM's IP after 30s (!)... Aborting

Usage:
  corectl load path/to/yourProfile [flags]

Examples:
  corectl load profiles/demo.toml

Global Flags:
      --debug   adds extra verbosity, and options, for debugging purposes and/or power users

All flags can also be configured via upper-case environment variables prefixed with "COREOS_"
For example, "--debug" => "COREOS_DEBUG"

Error: 'core-01' not found, or dead

Usage:
  corectl query [VMids] [flags]

Aliases:
  query, q

Flags:
  -a, --all    display extended information about a running CoreOS instance
  -i, --ip     displays given instance IP address
  -j, --json   outputs in JSON for easy 3rd party integration

Global Flags:
      --debug   adds extra verbosity, and options, for debugging purposes and/or power users

All flags can also be configured via upper-case environment variables prefixed with "COREOS_"
For example, "--debug" => "COREOS_DEBUG"

Error: 'core-01' not found, or dead

Usage:
  corectl query [VMids] [flags]

Aliases:
  query, q

Flags:
  -a, --all    display extended information about a running CoreOS instance
  -i, --ip     displays given instance IP address
  -j, --json   outputs in JSON for easy 3rd party integration

Global Flags:
      --debug   adds extra verbosity, and options, for debugging purposes and/or power users

All flags can also be configured via upper-case environment variables prefixed with "COREOS_"
For example, "--debug" => "COREOS_DEBUG"

Waiting for VM to be ready...

@abhiesa I'm trying to reproduce this one, but no luck, I always can switch between channels via:
Setup -> Change Release Channel
Halt/Up
or
Reload

oh, was able to reproduce it, will look deeper then

@abhiesa after bigger investigation it looks like the problem is only with alpha which is understandable as it is the alpha channel and it may not always function properly as expected

@abhiesa i was able to reproduce it just once on alpha. working on figuring out what's going on...

closing in favour of https://github.com/TheNewNormal/corectl/issues/62

Both coreos-osx#38 and corectl#62, and the problem still persists. Please let one issue open, till it get fixed or released.


[CSDiagnostics] Add an error message for pack expansion expressions over packs that don't have the same shape.

For example:
func sameShapeDiagnostics<T..., U...>(t: T..., u: U...) {
  _ = (each t, each u)... // 't' and 'u' do not have the same shape
}

A ShapeOf constraint breaks down into a Bind. Previously if that failed, the constraint system would report type of expression is ambiguous without more context. Now, it reports pack expansion requires that 'U' and 'T' have the same shape.

@swift-ci please smoke test


IZPACK-1433: Global temporary folder never gets deleted

IZPACK-1433:
I replaced cleanup() with deleteOnExit(). cleanup() does nothing that create() in the line before didn't already do, so I guess it was accidentally called instead of deleteOnExit() when this mechanism was initially implemented.

Thanks for contributing.


Explanation of errors and warnings

I was backing up quite a few email addresses and during the process I got several errors and warnings. Can I get clarification which error means exactly what.
Thank you very much.
W, [2023-03-24T02:46:15.915127 #1709]  WARN -- : Backup for account<EMAIL_ADDRESS>failed with error Operation timed out

I, [2023-03-24T09:00:12.554128 #6931]  INFO -- : [INBOX] Fetch returned empty body - skipping

W, [2023-03-29T16:46:43.098078 #57337]  WARN -- : Backup for account<EMAIL_ADDRESS>failed with error undefined method `dump' for nil:NilClass

W, [2023-04-05T16:06:44.146177 #736]  WARN -- : Backup for account<EMAIL_ADDRESS>failed with error end of file reached

WARNING: More than 1000 header fields; only using the first 1000 and ignoring the rest

WARNING: Ignoring unparsable header "\xE2\x80\x9CX-AntiAbuse: This header was added to track abuse, please include it with any abuse report": invalid header name syntax: "\xE2\x80\x9CX-AntiAbuse"

Also for me:
WARNING: Ignoring unparsable header "po Message-ID<EMAIL_ADDRESS>invalid header name syntax: "po Message-ID"
WARNING: Ignoring unparsable header "D7DE 2DE1 Content-Type: multipart/mixed; boundary=\"------------xxx\"": invalid header name syntax: "D7DE 2DE1 Content-Type"
WARNING: Ignoring unparsable header "at, 22 Oct 2022 19:03:53 +0200": invalid header name syntax: "at, 22 Oct 2022 19"
WARNING: Ignoring unparsable header "> so it cMessage-ID<EMAIL_ADDRESS>invalid header name syntax: "> so it cMessage-ID"
WARNING: Ignoring unparsable header ">> zzz-Path<EMAIL_ADDRESS>invalid header name syntax: ">> 6r3mueU5PmyCwTEYReturn-Path"

These warnings are produced while parsing the headers of emails. The messages get backed up correctly.


added utterson

submitting my own engine, which i've (and some others) been using since 2009. Thanks for including.

The build failed, seems like there might be an error in the frontmatter.